Applies To:

Show Versions Show Versions

Manual Chapter: Migrating vCMP Virtual Disks to B2000 Series Blades
Manual Chapter
Table of Contents   |   << Previous Chapter

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 .

Important: Do not attempt virtual disk migration on a chassis that is currently in a production environment.

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.

  1. Verify that you are connected to slot 1 through a serial console to the advanced (bash) shell.
    Important: To minimize the chance that an interruption in network connectivity will preempt virtual disk migration, always perform these steps using the serial console of the blade instead of the Secure Shell (SSH) protocol.
  2. Collect all virtual disks from slot 3:
    chassisVdiskMigrate.pm collect --pull-from slot3 --destined-for slot1
    This command initially reports the virtual disks on the blade in slot 3 that the system will collect and then asks for confirmation. For example:
                                  
    ############################################ 
    #STEP 5: Confirm list of vdisks to collect 
    ############################################
                        
    ############################################ 
      The following vdisks will be collected:
    ############################################
            test-guest1.img     (20.64 GiB)
            test-guest3.img     (3.89 GiB)
    Continue? (y/n) y
                               
    
  3. When prompted to continue, type y.
    The script continues, copying the virtual disks from the original blade in slot 3 to the new blade in slot 1 for later migration to slot 1.
                                  
    ############################################ 
    #STEP 6: Pulling vdisk test-guest1.img from slot 3
    ############################################
    
    ############################################ 
    #  Successfully pulled vdisk test-guest1.img.
    ############################################
    
    ############################################ 
    #STEP 7: Pulling vdisk test-guest3.img from slot 3
    ############################################
    
    ############################################ 
    #  Successfully pulled vdisk test-guest3.img.  
    ############################################
    
    ############################################ 
    #  Successfully collected 2 vdisks from slot 3!
    ############################################
                               
    
  4. Collect all virtual disks from slot 2.
    chassisVdiskMigrate.pm collect --pull-from slot2 --destined-for slot2
    This command initially reports the virtual disks on the blade in slot 2 that the system will collect and then asks for confirmation.
  5. When prompted to continue, type y.
    The script continues, copying the virtual disks from the original blade in slot 2 to the new blade in slot 1, for later migration to slot 2.
  6. Remove the original blades from slots 2 and 3.
  7. Insert the new blade into slot 2 and wait a few minutes.
    This causes the system to initialize the new blade, including copying the host configuration from the new primary blade in slot 1 to the other new blade and provisioning the vCMP feature. During this process, one or more reboots occur.
  8. Verify that the vCMP feature is provisioned.
    tmsh show sys provision
  9. Push the collected virtual disks to the new slots.
    chassisVdiskMigrate.pm push
    The script initially shows a list of all collected virtual disks that the script will push to the new blades.
                                  
    ############################################ 
    #STEP 5: Confirm list of vdisks to push 
    ############################################
                        
    ############################################ 
      The following vdisks will be pushed:
    ############################################
            test-guest1.img     (20.64 GiB)
            test-guest3.img     (3.89 GiB)
            test-guest2.img     (2.53 GiB)
            test-guest3.img     (2.24 GiB)
    Continue? (y/n) y
                               
    
  10. Type y.
    The script pushes the collected virtual disks from the new blade in slot 1 to the blades in slots 1 and 2.
                                  
    ############################################ 
    #STEP 7: Push vdisk test-guest1.img to slot 1
    ############################################
    
    ############################################ 
    #STEP 8: Push vdisk test-guest3.img to slot 1
    ############################################
    
    ############################################ 
    #Step 9: Push vdisk test-guest2.img to slot 2
    ############################################
                        
    ############################################ 
    #Step 10: Push vdisk test-guest3.img to slot 2
    ############################################
    This may take several minutes; please be patient.
                               
    
  11. Verify that all virtual disks were migrated successfully.
    chassisVdiskMigrate.pm list

    You should see this information:

    ############################################ 
    #        UNCOLLECTED VDISKS                #          
    ############################################
                No uncollected vdisks.
    
    ############################################ 
    #        UNPUSHED VDISKS                   #
    ############################################  
                No unpushed vdisks.
                        
  12. Set one or more guests to the Deployed state.
    tmsh modify vcmp guest all state deployed
    This step is optional.
  13. Delete all virtual disks and metadata created by the collect and push operations.
    chassisVdiskMigrate.pm delete-and-reset-all
    This command deletes unnecessary .img files that can consume disk space on the primary blade.
After you perform this task, the chassis is populated with two new blades. Both new blades contain the BIG-IP® configuration data from the original blades, as well as any virtual disks for the relevant vCMP guests.

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.

  1. Verify that you are connected to slot 1 through a serial console to the advanced (bash) shell.
    Important: To minimize the chance that an interruption in network connectivity will preempt virtual disk migration, always perform these steps using the serial console of the blade instead of the Secure Shell (SSH) protocol.
  2. Collect all virtual disks from slot 2.
    chassisVdiskMigrate.pm collect --pull-from slot2 --destined-for slot2
    The script initially reports the virtual disks on the blade in slot 2 that the system will collect and then asks for confirmation. For example:
                                  
    ############################################ 
    #STEP 5: Confirm list of vdisks to collect 
    ############################################
                        
    ############################################ 
      The following vdisks will be collected:
    ############################################
            test-guest1.img     (20.64 GiB)
            test-guest3.img     (3.89 GiB)
    Continue? (y/n) y
                               
    
  3. When prompted to continue, type y.
    The script continues, copying the virtual disks from the original blade in slot 2 to the new blade in slot 1 for later migration to slot 2.
                                  
    ############################################ 
    #STEP 6: Pulling vdisk test-guest1.img from slot 2
    ############################################
    
    ############################################ 
    #  Successfully pulled vdisk test-guest1.img.
    ############################################
    
    ############################################ 
    #STEP 7: Pulling vdisk test-guest3.img from slot 2
    ############################################
    
    ############################################ 
    #  Successfully pulled vdisk test-guest3.img.  
    ############################################
    
    ############################################ 
    #  Successfully collected 2 vdisks from slot 2!
    ############################################
                               
    
  4. Collect all virtual disks from slot 3.
    chassisVdiskMigrate.pm collect --pull-from slot3 --destined-for slot3
    The script initially reports the virtual disks on the blade in slot 3 that the system will collect and then asks for confirmation.
  5. When prompted to continue, type y.
    The script continues, copying the virtual disks from the original blade in slot 3 to the new blade in slot 1, for later migration to slot 3.
  6. Collect all virtual disks from slot 4.
    chassisVdiskMigrate.pm collect --pull-from slot4 --destined-for slot4
    The script initially reports the virtual disks on the blade in slot 4 that the system will collect and then asks for confirmation.
  7. When prompted to continue, type y.
    The script continues, copying the virtual disks from the original blade in slot 4 to the new blade in slot 1, for later migration to slot 4.
  8. Remove the original blades from slots 2, 3, and 4.
  9. Insert the original blade from slot 1 into slot 2 and wait one or two minutes.
    The blade powers up. When this process is finished, you can proceed to the next step.
  10. Collect all virtual disks from slot 2.
    chassisVdiskMigrate.pm collect --pull-from slot2 --destined-for slot1
    The script initially reports the virtual disks on the blade in slot 2 that the system will collect and then asks for confirmation.
  11. When prompted to continue, type y.
    The script continues, copying the virtual disks from the original blade in slot 2 to the new blade in slot 1, for later migration to slot 1.
  12. Remove the original blade in slot 2.
  13. Insert the remaining new blades into slots 2, 3, and 4 and wait a few minutes per blade.
    This causes the system to initialize each new blade, including copying the host configuration from the new primary blade in slot 1 to the other new blades and provisioning the vCMP feature. During this process, one or more reboots occur.
  14. Verify that the vCMP feature is provisioned.
    tmsh show sys provision
  15. Push the collected virtual disks to the new slots.
    chassisVdiskMigrate.pm push
    This command initially lists all of the collected virtual disks that the script will push to the new blades.
  16. When prompted to continue, type y.
    The script pushes the collected virtual disks from the new blade in slot 1 to the new blades.
  17. Verify that all virtual disks were migrated successfully.
    chassisVdiskMigrate.pm list

    You should see this information:

    ############################################ 
    #        UNCOLLECTED VDISKS                #          
    ############################################
                No uncollected vdisks.
    
    ############################################ 
    #        UNPUSHED VDISKS                   #
    ############################################  
                No unpushed vdisks.
                        
  18. Set one or more guests to the Deployed state.
    tmsh modify vcmp guest all state deployed
    This step is optional.
  19. Delete all virtual disks and metadata created by the collect and push operations.
    chassisVdiskMigrate.pm delete-and-reset-all
    This command deletes unnecessary .img files that can consume disk space on the primary blade.
After you perform this task, the chassis is populated with four new blades. All new blades contain the BIG-IP® configuration data from the original blades, as well as any virtual disks for the relevant vCMP guests.

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.

  1. Verify that you are connected to slot 1 through a serial console to the advanced (bash) shell.
    Important: To minimize the chance that an interruption in network connectivity will preempt virtual disk migration, always perform these steps using the serial console of the blade instead of the Secure Shell (SSH) protocol.
  2. Collect all virtual disks from slot 2.
    chassisVdiskMigrate.pm collect --pull-from slot2 --destined-for slot2
    The script initially reports the virtual disks on the blade in slot 2 that the system will collect and then asks for confirmation. For example:
                                  
    ############################################ 
    #STEP 5: Confirm list of vdisks to collect 
    ############################################
                        
    ############################################ 
      The following vdisks will be collected:
    ############################################
            test-guest1.img     (20.64 GiB)
            test-guest3.img     (3.89 GiB)
    Continue? (y/n) y
                               
    
  3. When prompted to continue, type y.
    The script continues, copying the virtual disks from the original blade in slot 2 to the new blade in slot 1 for later migration to slot 2.
                                  
    ############################################ 
    #STEP 6: Pulling vdisk test-guest1.img from slot 2
    ############################################
    
    ############################################ 
    #  Successfully pulled vdisk test-guest1.img.
    ############################################
    
    ############################################ 
    #STEP 7: Pulling vdisk test-guest3.img from slot 2
    ############################################
    
    ############################################ 
    #  Successfully pulled vdisk test-guest3.img.  
    ############################################
    
    ############################################ 
    #  Successfully collected 2 vdisks from slot 2!
    ############################################
                               
    
  4. Collect all virtual disks from slot 3.
    chassisVdiskMigrate.pm collect --pull-from slot3 --destined-for slot1
    The script initially reports the virtual disks on the blade in slot 3 that the system will collect and then asks for confirmation.
  5. When prompted to continue, type y.
    The script continues, copying the virtual disks from the original blade in slot 3 to the new blade in slot 1, for later migration to slot 1.
  6. Collect all virtual disks from slot 4.
    chassisVdiskMigrate.pm collect --pull-from slot4 --destined-for slot2
    This command initially reports the virtual disks on the blade in slot 4 that the system will collect and then asks for confirmation.
  7. When prompted to continue, type y.
    The script continues, copying the virtual disks from the original blade in slot 4 to the new blade in slot 1, for later migration to slot 2.
  8. Remove the original blades from slots 2, 3, and 4.
  9. Insert the original blade from slot 1 into slot 2.
    The blade powers up. You must wait one or two minutes after inserting the blade. When this process is finished, you can proceed to the next step.
  10. Collect all virtual disks from slot 2.
    chassisVdiskMigrate.pm collect --pull-from slot2 --destined-for slot1
    This command initially reports the virtual disks on the blade in slot 2 that the system will collect and then asks for confirmation.
  11. When prompted to continue, type y.
    The script continues, copying the virtual disks from the original blade in slot 2 to the new blade in slot 1, for later migration to slot 1.
  12. Remove the original blade in slot 2.
  13. Insert the remaining new blade into slot 2 and wait a few minutes.
    This causes the system to initialize the new blade, including copying the host configuration from the new primary blade in slot 1 to the other new blade and provisioning the vCMP feature. During this process, one or more reboots occur.
  14. Verify that the vCMP feature is provisioned.
    tmsh show sys provision
  15. Push all virtual disks to the new blades.
    chassisVdiskMigrate.pm push
    The script initially lists all of the collected virtual disks that the script will push to the new blades.
  16. When prompted to continue, type y.
    The script pushes the collected virtual disks from the new blade in slot 1 to the new blades.
  17. Verify that all virtual disks were migrated successfully.
    chassisVdiskMigrate.pm list

    You should see this information:

    ############################################ 
    #        UNCOLLECTED VDISKS                #          
    ############################################
                No uncollected vdisks.
    
    ############################################ 
    #        UNPUSHED VDISKS                   #
    ############################################  
                No unpushed vdisks.
                        
  18. Set one or more guests to the Deployed state.
    tmsh modify vcmp guest all state deployed
    This step is optional.
  19. Delete all virtual disks and metadata created by the collect and push operations.
    chassisVdiskMigrate.pm delete-and-reset-all
    This command deletes unnecessary .img files that can consume disk space on the primary blade.
After you perform this task, the chassis is populated with two new blades. Both blades contain the BIG-IP® configuration data from the original blades, as well as any virtual disks for the relevant vCMP guests.
Optionally, to avoid unexpected results, you can reconfigure the guests to ensure that all slots on which they are allowed to run are populated with blades.

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.

  1. Verify that you are connected to slot 1 through a serial console to the advanced (bash) shell.
    Important: To minimize the chance that an interruption in network connectivity will preempt virtual disk migration, always perform these steps using the serial console of the blade instead of the Secure Shell (SSH) protocol.
  2. Collect all virtual disks from slot 2.
    chassisVdiskMigrate.pm collect --pull-from slot2 --destined-for slot2
    The script initially reports the virtual disks on the blade in slot 2 that the system will collect and then asks for confirmation. For example:
                                  
    ############################################ 
    #STEP 5: Confirm list of vdisks to collect 
    ############################################
                        
    ############################################ 
      The following vdisks will be collected:
    ############################################
            test-guest1.img     (20.64 GiB)
            test-guest3.img     (3.89 GiB)
    Continue? (y/n) y
                               
    
  3. When prompted to continue, type y.
    The script continues, copying the virtual disks from the original blade in slot 2 to the new blade in slot 1 for later migration to slot 2.
                                  
    ############################################ 
    #STEP 6: Pulling vdisk test-guest1.img from slot 2
    ############################################
    
    ############################################ 
    #  Successfully pulled vdisk test-guest1.img.
    ############################################
    
    ############################################ 
    #STEP 7: Pulling vdisk test-guest3.img from slot 2
    ############################################
    
    ############################################ 
    #  Successfully pulled vdisk test-guest3.img.  
    ############################################
    
    ############################################ 
    #  Successfully collected 2 vdisks from slot 2!
    ############################################
                               
    
  4. Collect all virtual disks from slot 4.
    chassisVdiskMigrate.pm collect --pull-from slot4 --destined-for slot1
    This command initially reports the virtual disks on the blade in slot 4 that the system will collect and then asks for confirmation.
  5. When prompted to continue, type y.
    The script continues, copying the virtual disks from the original blade in slot 4 to the new blade in slot 1.
  6. Collect virtual disk test-guestA.img from slot 3.
    chassisVdiskMigrate.pm collect --pull-from slot3 --destined-for slot1 test-guestA.img
    The script initially reports the virtual disk that the system will collect and then asks for confirmation.
  7. When prompted to continue, type y.
    The script continues, copying the virtual disk test-guestA.img from the original blade in slot 3 to the new blade in slot 1, for later migration to slot 1.
  8. Collect the virtual disk test-guestB.img from slot 3.
    chassisVdiskMigrate.pm collect --pull-from slot3 --destined-for slot2 test-guestB.img
    The script initially reports the virtual disk that the system will collect and then asks for confirmation.
  9. When prompted to continue, type y.
    The script continues, copying the virtual disk test-guestB.img from the original blade in slot 3 to the new blade in slot 1, for later migration to slot 2.
  10. Verify that all virtual disks were collected.
    chassisVdiskMigrate.pm list

    You should see this information:

    ############################################ 
    #        UNCOLLECTED VDISKS                #          
    ############################################
                No uncollected vdisks.
    
    ############################################ 
    #        UNPUSHED VDISKS                   #
    ############################################  
                No unpushed vdisks.
                        
  11. Remove the original blades from slots 2, 3, and 4.
  12. Insert the remaining new blade into slot 2 and wait a few minutes.
    This causes the system to initialize the new blade, including copying the host configuration from the new primary blade in slot 1 to the other new blade and provisioning the vCMP feature. During this process, one or more reboots occur.
  13. Verify that the vCMP feature is provisioned.
    tmsh show sys provision
  14. Push all virtual disks to the new blades.
    chassisVdiskMigrate.pm push
    The script initially lists all of the collected virtual disks that the script will push to the new blades.
  15. When prompted to continue, type y.
    The script pushes the collected virtual disks from the new blade in slot 1 to the new blades.
  16. Verify that all virtual disks were migrated successfully.
    chassisVdiskMigrate.pm list

    You should see this information:

    ############################################ 
    #        UNCOLLECTED VDISKS                #          
    ############################################
                No uncollected vdisks.
    
    ############################################ 
    #        UNPUSHED VDISKS                   #
    ############################################  
                No unpushed vdisks.
                        
  17. Set one or more guests to the Deployed state.
    tmsh modify vcmp guest all state deployed
    This step is optional.
  18. Delete all virtual disks and metadata created by the collect and push operations.
    chassisVdiskMigrate.pm delete-and-reset-all
    This command deletes unnecessary .img files that can consume disk space on the primary blade.
After you perform this task, the chassis is populated with two new blades. All new blades contain the BIG-IP® configuration data from the original blades, as well as any virtual disks for the relevant vCMP guests.
Optionally, to avoid unexpected results, you can reconfigure the guests to ensure that all slots on which they are allowed to run are populated with blades.

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.

  1. Verify that you are connected to slot 2 through a serial console to the advanced (Bash) shell.
    Important: To minimize the chance that an interruption in network connectivity will preempt virtual disk migration, always perform these steps using the serial console of the blade instead of the Secure Shell (SSH) protocol.
  2. Collect all virtual disks from slot 1:
    chassisVdiskMigrate.pm collect --pull-from slot1 --destined-for slot2
    This command initially reports the virtual disks on the blade in slot 1 that the system will collect and then asks for confirmation. For example:
                                  
    ############################################ 
    #STEP 5: Confirm list of vdisks to collect 
    ############################################
                        
    ############################################ 
      The following vdisks will be collected:
    ############################################
            test-guest1.img     (20.64 GiB)
            test-guest3.img     (3.89 GiB)
    Continue? (y/n) y
                               
    
  3. When prompted to continue, type y.
    The script continues, copying the virtual disks from the original blade in slot 1 to the new blade in slot 2.
                                  
    ############################################ 
    #STEP 6: Pulling vdisk test-guest1.img from slot 1
    ############################################
    
    ############################################ 
    #  Successfully pulled vdisk test-guest1.img.
    ############################################
    
    ############################################ 
    #STEP 7: Pulling vdisk test-guest3.img from slot 1
    ############################################
    
    ############################################ 
    #  Successfully pulled vdisk test-guest3.img.  
    ############################################
    
    ############################################ 
    #  Successfully collected 2 vdisks from slot 1!
    ############################################
                               
    
  4. Remove the original blade from slot 1.
  5. Verify that the vCMP feature is provisioned.
    tmsh show sys provision
  6. Push the collected virtual disks to the new blade in slot 2, that is, the same blade on which the virtual disks are collected.
    chassisVdiskMigrate.pm push
    This command initially shows a list of all collected virtual disks that the script will push.
                                  
    ############################################ 
    #STEP 5: Confirm list of vdisks to push 
    ############################################
                        
    ############################################ 
      The following vdisks will be pushed:
    ############################################
            test-guest1.img     (20.64 GiB)
            test-guest3.img     (3.89 GiB)
    Continue? (y/n) y
                               
    
  7. Type y.
    The script pushes the collected virtual disks to slot 2.
                                  
    ############################################ 
    #STEP 7: Push vdisk test-guest1.img to slot 2
    ############################################
    
    ############################################ 
    #STEP 8: Push vdisk test-guest3.img to slot 2
    ############################################
    
    This may take several minutes; please be patient.
                               
    
  8. Verify that all virtual disks were migrated successfully.
    chassisVdiskMigrate.pm list

    You should see this information:

    ############################################ 
    #        UNCOLLECTED VDISKS                #          
    ############################################
                No uncollected vdisks.
    
    ############################################ 
    #        UNPUSHED VDISKS                   #
    ############################################  
                No unpushed vdisks.
                        
  9. If you want the new blade to reside in slot 1, remove the blade from slot 2 and insert it into slot 1.
    This step is optional.
  10. Set one or more guests to the Deployed state.
    tmsh modify vcmp guest all state deployed
    This step is optional.
  11. Delete all virtual disks and metadata created by the collect and push operations.
    chassisVdiskMigrate.pm delete-and-reset-all
    This command deletes unnecessary .img files that can consume disk space on the primary blade.
After you perform this task, slot 2 is populated with one new blade, and all other slots are empty. The new blade contains the BIG-IP® configuration data from the original blade, as well as any virtual disks for the relevant vCMP guests.

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.

  1. Verify that you are connected to slot 1 through a serial console to the advanced (bash) shell.
    Important: To minimize the chance that an interruption in network connectivity will preempt virtual disk migration, always perform these steps using the serial console of the blade instead of the Secure Shell (SSH) protocol.
  2. Collect all virtual disks from slot 2.
    chassisVdiskMigrate.pm collect --pull-from slot2 --destined-for slot2
    The script initially reports the virtual disks on the blade in slot 2 that the system will collect and then asks for confirmation. For example:
                                  
    ############################################ 
    #STEP 5: Confirm list of vdisks to collect 
    ############################################
                        
    ############################################ 
      The following vdisks will be collected:
    ############################################
            test-guest1.img     (20.64 GiB)
            test-guest3.img     (3.89 GiB)
    Continue? (y/n) y
                               
    
  3. When prompted to continue, type y.
    The script continues, copying the virtual disks from the original blade in slot 2 to the new blade in slot 1 for later migration to slot 2.
                                  
    ############################################ 
    #STEP 6: Pulling vdisk test-guest1.img from slot 2
    ############################################
    
    ############################################ 
    #  Successfully pulled vdisk test-guest1.img.
    ############################################
    
    ############################################ 
    #STEP 7: Pulling vdisk test-guest3.img from slot 2
    ############################################
    
    ############################################ 
    #  Successfully pulled vdisk test-guest3.img.  
    ############################################
    
    ############################################ 
    #  Successfully collected 2 vdisks from slot 2!
    ############################################
                               
    
  4. Remove the original blade in slot 2.
  5. Insert a new blade into slot 2 and wait a few minutes.
    This causes the system to initialize the new blade, including copying the host configuration from the new primary blade in slot 1 to the other new blade and provisioning the vCMP feature. During this process, one or more reboots occur.
  6. Push the collected virtual disks to the new slot.
    chassisVdiskMigrate.pm push
    The script initially shows a list of all collected virtual disks that the script will push to the new blade.
                                  
    ############################################ 
    #STEP 5: Confirm list of vdisks to push 
    ############################################
                        
    ############################################ 
      The following vdisks will be pushed:
    ############################################
            test-guest1.img     (20.64 GiB)
            test-guest3.img     (3.89 GiB)
    Continue? (y/n) y
                               
    
  7. Type y.
    The script pushes the collected virtual disks from the new blade in slot 1 to the blade in slot 2.
                                  
    ############################################ 
    #STEP 7: Push vdisk test-guest1.img to slot 2
    ############################################
    
    ############################################ 
    #STEP 8: Push vdisk test-guest3.img to slot 2
    ############################################
    
    This may take several minutes; please be patient.
                               
    
  8. Delete all collected virtual disks from the blade in slot 1.
    chassisVdiskMigrate.pm delete-pushed-img-files
  9. Collect all virtual disks from slot 3.
    chassisVdiskMigrate.pm collect --pull-from slot3 --destined-for slot1
    The script initially reports the virtual disks on the blade in slot 3 that the system will collect and then asks for confirmation.
  10. When prompted to continue, type y.
    The script continues, copying the virtual disks from the original blade in slot 3 to the new blade in slot 1, for later migration to slot 1.
  11. Remove the original blade in slot 3.
  12. Push the collected virtual disks to slot 1.
    chassisVdiskMigrate.pm push
    This command initially lists all of the collected virtual disks that the script will push to slot 1.
  13. When prompted to continue, type y.
    The script pushes the collected virtual disks from the new blade in slot 1 to slot 1.
  14. Delete all collected virtual disks from the blade in slot 1.
    chassisVdiskMigrate.pm delete-pushed-img-files
  15. Verify that the vCMP feature is provisioned.
    tmsh show sys provision
  16. Verify that all virtual disks were migrated successfully.
    chassisVdiskMigrate.pm list

    You should see this information:

    ############################################ 
    #        UNCOLLECTED VDISKS                #          
    ############################################
                No uncollected vdisks.
    
    ############################################ 
    #        UNPUSHED VDISKS                   #
    ############################################  
                No unpushed vdisks.
                        
  17. Set one or more guests to the Deployed state.
    tmsh modify vcmp guest all state deployed
    This step is optional.
  18. Delete all virtual disks and metadata created by the collect and push operations.
    chassisVdiskMigrate.pm delete-and-reset-all
    This command deletes unnecessary .img files that can consume disk space on the primary blade.
After you perform this task, the chassis is populated with two new blades. The blades contain the BIG-IP® configuration data from the original blades, as well as any virtual disks for the relevant vCMP guests.
Optionally, to avoid unexpected results, you can reconfigure the guests to ensure that all slots on which they are allowed to run are populated with blades.

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
Note: The reported size of a virtual disk after migration sometimes differs from the original size; this is a normal condition. To ensure virtual disk integrity, the chassisVdiskMigrate.pm script performs a checksum on the virtual disk files.

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.
Table of Contents   |   << Previous Chapter

Was this resource helpful in solving your issue?




NOTE: Please do not provide personal information.



Incorrect answer. Please try again: Please enter the words to the right: Please enter the numbers you hear:

Additional Comments (optional)