Always back up your Management Center configuration before upgrading or downgrading. Then, store the backup off-box. This ensures that you can restore your configuration if you experience problems with upgrading or downgrading.
Important Considerations for Management Center 2.1 Software Image Installation
Due to some major changes to the underlying systems Management Center relies on, there are several points to note:
All backups are erased on upgrade to 2.x.
Backups are not compatible, transferable, or preserved on upgrade between 1.x and 2.x. This is because backups created in version 1.x are not compatible with 2.0 or later for the following reasons:
Downgrades from 2.x to 1.x are not supported.
Backup export encryption changed.
Backups are not compatible or transferable between FIPS and Non-FIPS mode, for the following reasons:
Encryption differences between FIPS/Non-FIPS mode.
Non-FIPS backup cannot be restored to FIPS appliance without omitting certain backup portions.
Starting with Management Center 220.127.116.11, the password used for the admin account is the same for both the CLI and user interface (UI). This means you cannot log into the UI as "admin user" unless you use the CLI admin account password.
Upon upgrade from a 1.x release to 2.x, the enable password will be set to the same password previously set for the admin account in the CLI. Immediately after upgrading, change this password from the (config)# mode with the command # authentication enable-password.
Upon upgrading from 1.x you may not be able to connect to the MC user interface using HTTPS. If this occurs, you will need to regenerate the default and bluecoat-appliance certificates.
If you have SSL mutual authentication enabled prior to upgrading, you will need to reconfigure it.
The new system will generate a new, unique public SSH RSA key.
The initial upgrade will take up to ten minutes to complete. Wait for upgrade to complete - any interruption in the upgrade process may result in instability.