Skip to main content
Sign Out

Welcome to Dell

My Account
  • Place orders quickly and easily
  • View orders and track your shipping status
  • Create and access a list of your products
  • Manage your Dell EMC sites, products, and product-level contacts using Company Administration.
Sign In Create an Account Premier Sign In Partner Program Sign In
Contact Us

Dell Chassis Management Controller Version 3.10 for Dell EMC PowerEdge VRTX User's Guide

PDF

Restoring Chassis Configuration Profile

You can restore the configuration of a chassis by importing the backup file ( .xml or .bak) on the local management station or the network share to which the chassis configurations were saved. The configurations include all the properties available through the CMC web interface, RACADM commands, and settings.

To restore the chassis configuration, perform the following tasks:

  1. Go to the Chassis Configuration Profiles page. In the Restore Configuration > Restore Chassis Configuration section, click Browse and select the backup file to import the saved chassis configuration.
  2. Click Restore Configuration to upload an encrypted backup file ( .bak) or a .xml stored profile file to the CMC. The CMC web interface returns to the login page after a successful restore operation.
  • NOTE: If the backup files (.bak) of the earlier versions of CMC, are loaded on the latest version of CMC where FIPS is enabled, reconfigure all the 16 CMC local user passwords. However, the password of the first user is reset to "calvin".
  • NOTE: When a chassis configuration profile is imported from a CMC, which does not support the FIPS feature, to a CMC where FIPS is enabled, the FIPS remains enabled in the CMC.
  • NOTE: If you change the FIPS mode in the chassis configuration profile, the DefaultCredentialMitigation is enabled.

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: <>()\