Applies To:
Show VersionsBIG-IP APM
- 15.0.0, 14.1.0, 14.0.0, 13.1.1, 13.1.0, 13.0.1, 13.0.0, 12.1.4, 12.1.3, 12.1.2, 12.1.1, 12.1.0, 11.6.4, 11.6.3, 11.6.2, 11.6.1, 11.5.9, 11.5.8, 11.5.7, 11.5.6, 11.5.5, 11.5.4, 11.5.3, 11.5.2, 11.5.1
BIG-IP GTM
- 11.6.4, 11.6.3, 11.6.2, 11.6.1, 11.5.9, 11.5.8, 11.5.7, 11.5.6, 11.5.5, 11.5.4, 11.5.3, 11.5.2, 11.5.1
BIG-IP LTM
- 15.0.1, 15.0.0, 14.1.0, 14.0.0, 13.1.1, 13.1.0, 13.0.1, 13.0.0, 12.1.4, 12.1.3, 12.1.2, 12.1.1, 12.1.0, 11.6.4, 11.6.3, 11.6.2, 11.6.1, 11.5.9, 11.5.8, 11.5.7, 11.5.6, 11.5.5, 11.5.4, 11.5.3, 11.5.2, 11.5.1
BIG-IP DNS
- 15.0.0, 14.1.0, 14.0.0, 13.1.1, 13.1.0, 13.0.1, 13.0.0, 12.1.4, 12.1.3, 12.1.2, 12.1.1, 12.1.0
BIG-IP ASM
- 15.0.0, 14.1.0, 14.0.0, 13.1.1, 13.1.0, 13.0.1, 13.0.0, 12.1.4, 12.1.3, 12.1.2, 12.1.1, 12.1.0, 11.6.4, 11.6.3, 11.6.2, 11.6.1, 11.5.9, 11.5.8, 11.5.7, 11.5.6, 11.5.5, 11.5.4, 11.5.3, 11.5.2, 11.5.1
Migrating vCMP Virtual Disks to B2000 Series Blades
Overview: Virtual disk migration on B2000 Series blades
If you have a VIPRION® system that is provisioned for the virtual clustered multi-processing (vCMP®) feature, and you are replacing B2100 blades with new B2150 or B2250 blades, you can migrate the virtual disks for the guests to the new blades. You do this after you have run the script chassisConfigUpgrade to copy the vCMP host configuration, in the form of a user configuration set (UCS), from an original blade to a new blade.
You can migrate guest configurations to the new blades in either of these ways:
- Run a data collection script named chassisVdiskMigrate.pm (recommended method). This script first collects (copies) all virtual disks from the original blades onto the new primary blade. When you subsequently install the remaining new blades, the chassisVdiskMigrate.pm script pushes the virtual disks back onto their respective new blades. When using this script, you can verify that all virtual disks were successfully collected from the original blades and pushed to the new blades.
- Create and export a UCS for each guest's BIG-IP® configuration, as well as a UCS for the vCMP host configuration. The host configuration contains the definitions of all guests. After installing the new blades, you will need to recreate the guests and import the relevant guest UCS back to each guest. If the guests were running an older version of the BIG-IP software than the BIG-IP version on the new blades, you will need to upload appropriate ISOs and, if necessary, update each guest configuration to specify an initial image.
This section describes how to use the chassisVdiskMigrate.pm script to migrate virtual disks to new blades. To assist you in this process, the secion provides several examples of migration tasks, where each task differs in the number of original blades and new blades.
You can view help options for the chassisVdiskMigrate.pm script at any time by typing the command chassisVdiskMigrate.pm --help .
About prerequisites for running the virtual disk migration script
Before you begin the virtual disk migration, you should take the following actions.
Action | Explanation |
---|---|
Verify that you have run the chassisConfigUpgrade.pm script. | The blade on which this script was run should now be the primary, active blade. This blade should have the same vCMP® host and guest configuration as that of the original cluster. |
Verify that the primary, active blade is running BIG-IP® version 11.4.1 HF1 or later. | You can do this at the system prompt by typing watch tmsh show sys software status. |
Label all original blades in the chassis as well as the new replacement blades. | These labels are physical notes that you attach to each blade (original and new) to indicate the blade's current or target slot, as well as the blade serial number. |
Verify that you have access to the advanced (bash) shell. | If you do not have access, a system administrator must modify your user account to grant you access to the advanced shell. |
Verify that the vCMP feature is provisioned. | You can do this at the system prompt by typing tmsh show sys provision. |
Verify that all guests are in the Configured state. | You can do this at the system prompt by typing tmsh show vcmp guest status. |
Ensure that the new blade on which you will run the chassisVdiskMigrate.pm script has enough disk space to store all collected virtual disks. | You can do this at the system prompt by typing tmsh show sys disk application-volume. |
Verify that the chassis from which you will run the chassisVdiskMigrate.pm script is not in a production environment. | vCMP guests cannot process production traffic while the script is collecting or pushing virtual disks. |
Allow adequate time for the chassisVdiskMigrate.pm script to run. | For each virtual disk on a blade, you should expect to wait a minimum of 15 minutes for the collect operation and 15 minutes for the push operation. |
About sample virtual disk migration tasks
These examples illustrate multiple ways to migrate a virtual disk migration. You can use the example that most closely matches your VIPRION® cluster configuration.
Example 1: Replacing two blades
Before using this sample task, note that the task is based on these conditions:
- Slot 1 contains a new blade and is the primary slot in the cluster.
- Slot 2 contains an original blade.
- Slot 3 contains the original blade taken from slot 1.
When the VIPRION® system is provisioned for vCMP® and you need to migrate virtual disks from two B2100 blades to two new B2150 or B2250 blades, you can use this sample task. To perform this task, you use the chassisVdiskMigrate.pm script.
Example 2: Replacing four blades
Before using this sample task, note that the task is based on these conditions:
- Slot 1 contains a new blade and is the primary slot in the cluster.
- Slots 2, 3, and 4 contain original blades.
When the VIPRION® system is provisioned for vCMP® and you need to migrate virtual disks from four B2100 blades in the chassis to four new B2150 or B2250 blades, you can use this sample task. To perform this task, you use the chassisVdiskMigrate.pm script.
Example 3: Consolidating four blades to two blades
Before using this sample task, note that the task is based on these conditions:
- Slot 1 contains a new blade and is the primary slot in the cluster.
- Slots 2, 3, and 4 contain original blades.
When the VIPRION® system is provisioned for vCMP® and you need to migrate virtual disks from four B2100 blades to two new B2150 or B2250 blades, you can use this sample task. To perform this task, you use the chassisVdiskMigrate.pm script.
Example 4: Consolidating three blades to two blades
Before using this sample task, note that the task is based on these conditions:
- Slot 1 contains a new blade and is the primary slot in the cluster.
- Slots 2 and 3 contain original blades.
- Slot 4 contains the original blade taken from slot 1.
When the VIPRION® system is provisioned for vCMP® and you need to migrate virtual disks from three B2100 blades to two new B2150 or B2250 blades, you can use this sample task. In this example, the system distributes the virtual disks from slot 3 to multiple new slots (slots 1 and 2). To perform this task, you use the chassisVdiskMigrate.pm script.
Example 5: Replacing a single blade
Before using this sample task, note that the task is based on these conditions:
- Slot 1 contains the original blade.
- Slot 2 contains the new blade and is the primary slot in the cluster.
When the VIPRION® system is provisioned for vCMP® and you are replacing one B2100 blade in the chassis with a new B2150 or B2250 blade, you can use this sample task to migrate all virtual disks from the original blade to the new blade. To perform this task, you use the chassisVdiskMigrate.pm script.
Example 6: Migrating large virtual disks
Before using this sample task, note that the task is based on these conditions:
- Slot 1 contains a new blade and is the primary slot in the cluster.
- Slots 2 and 3 contain original blades.
When the VIPRION® system is provisioned for vCMP® and you need to migrate large virtual disks, you can use this task. This task migrates large virtual disks from three B2100 blades to two new B2150 or B2250 blades. To perform this task, you use the chassisVdiskMigrate.pm script.
Migration result
After using the chassisVdisksMigrate.pm script on a vCMP® system, you have a chassis containing one or more new blades, with no original blades. The new blades contain vCMP host configuration data, as well as the virtual disks for the guests.
You can verify that all virtual disks reside on the new blades by typing the command tmsh show vcmp.
This table shows sample output:
Name | Slot ID | OS | Status | Disk use (bytes) |
---|---|---|---|---|
test-guest1.img | 1 | tmos | ready | 19.4G |
test-guest2.img | 2 | tmos | ready | 2.7G |
test-guest3.img | 1 | tmos | ready | 2.6G |
test-guest3.img | 2 | tmos | ready | 2.5G |
Chassis virtual disk migration command reference
The vCMP® virtual disk migration script includes these actions and options.
Action | Description |
---|---|
collect | Copies virtual disks from the specified blade and stores them on the local blade. |
push | Pushes virtual disks from the local blade to the specified destination blade. |
list | Shows the status of virtual disks being migrated to new blades in the chassis. |
delete-pushed-img-files | Deletes all .img files on the local blade. |
delete-and-reset-all | Deletes all .img files and metadata on the local blade. |
Option | Description |
---|---|
--no-op | Does not run the script, but displays what would have been done. |
--verbose | Enables debug logging. |
-h or --help | Displays all options. |
--pull-from slotX | Identifies the slot to pull from. This option is valid with the collect action only, and is required. |
--destined-for slotX | Identifies the slot to push to. This option is valid with the collect action only. If this option is omitted, the destination is the slot specified with the --pull-from slotX option. |