If you are using VIPRION B2100 (original) blades in your VIPRION 2000 Series chassis and would like to upgrade to B2150 or B2250 (replacement) blades, you can use a chassis upgrade script to pull the user configuration set (UCS) from an old blade, and then copy and load the configuration to a new blade. The chassis upgrade script is automated, but requires user input.
To view help options for the script, type: chassisConfigUpgrade.pm --help.
Before you run the chassis upgrade script, check for these conditions:
|Chassis must not be in a production environment.||Divert your application traffic to another chassis.|
|Original blade must be running BIG-IP version 11.4.1 HF1 or later.||If the original blade is running an earlier version, you must upgrade the blade software.|
|vCMP guests on original blades should not be in a Deployed or Provisioned state.||You must put the guests into the Configured state.
Note: If vCMP is provisioned on your system, read the section, Migrating vCMP Virtual Disks on B2000 Series Blades.
|License must not be expired.||You must activate the license before you can upgrade your VIPRION system.|
These examples illustrate how to migrate a configuration from a VIPRION B2100 (original) blade to a B2150/B2250 (new) blade using an automated script. The script requires user input, so you must run it from the serial console of the new blade.
Your original blade configuration is now running on your new blade (which is now the primary blade in the system), and on any additional blades that you installed in the system.
After successful completion of the migration, you will need to delete any volumes with software versions older than BIG-IP 11.4.1 installed on them.