Skip to main content
  • Place orders quickly and easily
  • View orders and track your shipping status
  • Enjoy members-only rewards and discounts
  • Create and access a list of your products

Dell OpenManage Enterprise-Modular Edition Version 2.00.00 for PowerEdge MX7000 Chassis User's Guide

Restoring chassis

You can restore the configuration of a chassis using a backup file. You must have the chassis administrator role with device configuration privilege to restore the chassis.

Catalogs and associated baselines cannot be restored when the downloads.dell.com is not reachable. Catalogs with proxy settings cannot be restored on a different chassis as the proxy password is not restored on a different chassis. This action causes downloads.dell.com not reachable. Configure proxy password manually and then rerun all catalog and baseline jobs to complete the restore process. If the source of a catalog is a validated firmware, re-create the catalog and all baselines that are associated with the catalog manually to complete the restoration.

Based on the HTTPS network share configuration, the catalogs for HTTPs are restored with or without password after the backup file excluding sensitive data is restored. If entering the username and password for the HTTPS share is not mandatory, the catalog is restored, else the catalog is restored with job status "failed". Enter the username and password manually after the restore task for the status to display as "completed".

The restore process is not supported if chassis role during backup does not match with the chassis role while restoring. The following table displays the chassis role prerequisites for the restore process.

NOTE: The chassis backup and restore feature is supported only if the OME-Modular firmware version in the backup file and the chassis during the restore process are identical. The restore functionality is not supported if the OME-Modular versions do not match.
Table 1. Chassis role prerequisites for restore processThe below table displays the supported chassis roles for the restore process:
During backup Before restore After restore Action required
Standalone Standalone Standalone Chassis restore is supported.
Standalone Member (Group A) Not supported Transition the chassis to a Standalone state before initiating the restore process.
Standalone Lead (Group A) Not supported Transition the chassis to a Standalone state before initiating the restore process.
Lead (Group A) Lead (Group A) Lead (Group A) Chassis restore is supported.

Onboard all the available chassis that were originally present in the group.

Lead (Group A) Standalone Lead (Group A) Chassis restore is supported.

Standalone chassis is converted to a Lead and Onboard all the available chassis that were originally present in the group.

Lead (Group A) Lead (Group B) Not supported Transition the chassis to a Standalone or Lead of the same group before initiating the restore process.
Lead (Group A) Member (Group A) Not supported Transition the chassis to a Standalone or Lead of the same group before initiating the restore process.
Lead (Group A) Member (Group B) Not supported Transition the chassis to a Standalone or Lead of the same group before initiating the restore process.
Use case scenarios

You can perform restore chassis operation in the following scenarios.

Restoring on the same chassis is supported:

  • If management data is corrupt after a successful configuration and deployment of a chassis.
  • If you run into a downgrade situation resulting in loss of management configuration.
    NOTE: OME-Modular does not support configuration restore on firmware downgrade scenarios.
  • If you run into an issue where OME-Modular has to reset to default.

Restoring on a different chassis is supported:

  • In disaster recovery situations, where the chassis and all its components are damaged or lost due to a catastrophic event.
  • If you purchase a new chassis with the same hardware configuration.
Important notes
  • When you take backup on a lead chassis with the backup lead assigned, you must assign the backup lead after the restore process, manually.
  • During the restore process, you must not perform any management configurations using remote or local interfaces. Backup or restore process cannot be initiated if there are any other tasks running simultaneously.
  • The member chassis that was not part of backup is automatically off-boarded from the lead chassis.
  • The member chassis that was part of the lead chassis while taking backup, and later moved to another group is not restored.
  • The backup and restore feature is not intended for cloning purposes as there are system-specific attributes.
  • Catalogs that are created using CIFS or HTTPS network share are not restored if the backup is taken with password and restored after any of the following operations:

    • racadm racresetcfg
    • racadm racresetcfg -f
    • Change FIPS mode on the web interface.

    The tasks that are mentioned above regenerate the encryption key that is used for password encryption in the backup file. When the encryption key changes, these passwords cannot be decrypted with the changed key. Hence, the passwords cannot be restored automatically.

  • Templates, profiles, I/O identities or VLANs restore can cause data path disruptions if there is a collision in VLANs between the pre-restore and backup VLANs. Manually fix dependent fabrics, if any, to address the VLAN issues.
  • Catalogs and associated baselines cannot be restored when downloads.dell.com is unreachable as OME-Modular cannot get the catalog file name and path. Hence, the catalogs are not created.
  • If the backup is taken including password and is restored on different chassis after all settings are restored successfully, you must enter the password manually for configurations that require passwords for the feature to function. Examples for configurations that require password include SMTP and proxy with authentication.
  • When you reenter the SNMP agent v3 user credentials to complete the restore task, reenter the other network services settings too.

To restore a chassis:

  1. On the chassis Overview page, click More Actions > Restore.
    The Restore Chassis window is displayed.
  2. On the Introduction section, read the process and click Next.
    NOTE: Click Learn More to see more information about the Ethernet switch restore.
    SmartFabric restore operation is not supported if:
    • It is restored on a different chassis.
    • There is any difference between the current setup of the IOM hardware and the backup file.

    The maximum time to complete the chassis restore with Smart Fabric is five hours approximately.

    NOTE: Ethernet switch settings that are part of Startup.xml should be restored on all the IOMs before starting appliance restore task on the OME-M.
    OS10# copy scp://username:password@hostip/<IOM_SERVICETAG>.xml config://startup.xml 
    NOTE: All the IOMs reload during SmartFabric restore.
    The Upload File section is displayed.
  3. Under Restore File Location, select the Share Type where the configuration backup file is located.
    NOTE: If the current MM link configuration setup is different from the backup file, you must match the Top of Rack (TOR) connection to the MM link configuration before the restore operation.
    NOTE: During the SmartFabric restore, all the IOMs are converted in to the operating mode as in the backup file.
    NOTE: All the IOMs which go through the fabric restore are reloaded. The IOMs are reloaded twice if there is any difference in the mode of backup file and the current IOM.
  4. Enter the Network Share Address, and Network Share Filepath where the backup file is stored.
  5. Enter the name of the Backup File and Extension.
  6. If the Share Type is CIFS, enter the Domain, Username, and Password to access shared location. Else, go to step 9.
  7. Click Test Now, if the network connection is not tested.
  8. If the Share Type is HTTPS, Certificate Verification option is displayed. Select the checkbox to check the web server certificate authentication.
  9. In the Restore File Password section, enter the Encryption Password to open the encrypted backup file.
    NOTE: The password must be 8 to 32 characters long and must be a combination of an uppercase, a lowercase, a special character (+, &, ?, >, -, }, |, ., !, (, ', ,, _, [, ", @, #, ), *, ;, $, ], /, §, %, =, <, :, {, I) , and a number.
    NOTE: If the restore operation is done excluding passwords or on a different chassis with proxy settings, the proxy dependent tasks, such as repository task, try to connect to the external share. Rerun the tasks after configuring the proxy password.
  10. Click Validate to upload and validate the chassis configuration.
    The Optional Component section is displayed.
  11. From the Optional components, you can choose to restore files on the selected components .
    • Restore File Validation Status—Displays the validation status of the restore files.
      NOTE: The Ok indicates that the restore file validation status is successful. If the validation is not successful, an error message is displayed with the recommended action.
    • Optional Components—Displays the components that you can select for the restore operation. The possible options are:
      • Templates, Profiles, Identity Pools, and VLAN Configurations
      • Application and Chassis Settings
      • Certificates
        NOTE: The chassis certificate restore fails if you perform racresetcfg in the chassis and try to restore the backup file.
      • Catalogs and Baselines
        NOTE: You can restore only the latest validated catalog. If you want to restore the earlier validated catalogs, you must delete the previous catalogs and re-create them manually.
      • Alert Policies
      • SmartFabric Settings
        NOTE: Restoring fabrics may impact the data path.
      NOTE: The list of Optional Components is based on the backup chassis settings. The components that are not part of chassis backup is listed under Unavailable Components section below.
    • Mandatory Components—Displays the mandatory components for the restore operation.
    • Unavailable Components—Displays the components that are unavailable for the restore operation.
  12. Click Restore to restore the chassis.
    A message is displayed indicating that the chassis restore job is initiated successfully. You can check the status and details of the restore process on the Montitoring > Jobs page.

Rate this content

Accurate
Useful
Easy to understand
Was this article helpful?
0/3000 characters
  Please provide ratings (1-5 stars).
  Please provide ratings (1-5 stars).
  Please provide ratings (1-5 stars).
  Please select whether the article was helpful or not.
  Comments cannot contain these special characters: <>()\