The documentation set for this product strives to use bias-free language. For the purposes of this documentation set, bias-free is defined as language that does not imply discrimination based on age, disability, gender, racial identity, ethnic identity, sexual orientation, socioeconomic status, and intersectionality. Exceptions may be present in the documentation due to language that is hardcoded in the user interfaces of the product software, language used based on RFP documentation, or language that is used by a referenced third-party product. Learn more about how Cisco is using Inclusive Language.
This chapter describes how to move or migrate a VSB to from Cisco Nexus 1010 series to Cisco Nexus 1110 Series and includes the following sections:
After you have installed the Cisco Nexus Virtual Services Appliance, you can move, or migrate your VSBs from Cisco Nexus 1010 series to the Cisco Nexus 1110 Series. For information on VSB, see Information About Virtual Service Blades.
Follow these guidelines and limitations when moving or migrating a VSB from from Cisco Nexus 1010 series to the Cisco Nexus 1110 Series:
Use this procedure to move, or migrate, a VSB to the Cisco Nexus 1110 Series without service interruption. The migration involves the following steps:
Step 1 Verify that the Cisco Nexus 1010 series has the VSBs configured that need to be migrated to Cisco Nexus 1110 Series.
Step 2 Set up Cisco Nexus 1110 Series in a redundant HA pair. See Cisco Nexus Virtual Services Appliance Software Installation and Upgrade Guide, Release 4.2(1)SP1(5.1) .
Step 3 Migrate the HA VSBs like VSM and VSG to Cisco Nexus 1110 Series. See Migrating HA VSB to Cisco Nexus 1110 Series.
Step 4 Migrate the non HA VSBs like NAM to Cisco Nexus 1110 Series. See Migrating Non HA VSB to Cisco Nexus 1110 Series.
Before beginning this procedure, you must know or do the following:
Note If you use a value that results in a mismatch with the Cisco Nexus 1110 Series, then the synchronization between theCisco Nexus 1110 Series and the Cisco Nexus 1010 series overwrites your configuration on the Cisco Nexus 1010 series.
Step 1 From the CLI of the primary VSB on Cisco Nexus 1010, use the following command to initiate a manual switchover, and then shutdown the primary VSB.
login virtual-service-blade name primary
After logging into the VSB, use the following command to initiate a manual switchover.
When the switchover completes and the CLI returns to the Cisco Nexus 1010 , use the following command to shut the primary VSB.
Step 2 From the CLI of the active Cisco Nexus 1110 Series, use the following commands to create a primary virtual service for the VSB that you want to migrate. Use the same information that you used to create the VSB on Cisco Nexus 1010.
virtual-service-blade-type new iso filename
Step 3 Verify that the configuration is complete.
show virtual-service-blade summary
Once you have created the virtual service on the primary Cisco Nexus 1110 Series, an HA pair forms between the secondary VSB on the Cisco Nexus 1010 series and the primary virtual service on the Cisco Nexus 1110 Series.
Step 4 From the CLI of the primary VSB on the Cisco Nexus 1110 Series, use the following command to verify the redundancy status of the VSBs.
If the output indicates the following, then you can proceed with a system switchover.
Redundancy mode
---------------
administrative: HA
operational: HA
Step 5 From the CLI of the secondary VSB on the Cisco Nexus 1010, use the following command to initiate a manual switchover to the standby virtual service on the Cisco Nexus 1110 Series.
login virtual-service-blade name secondary
After logging into the VSB, use the following command to nictitate a manual switchover.
When the switchover completes and the CLI returns to the Cisco Nexus 1010 , use the following command to shut the secondary VSB.
Before continuing with the next step, wait until the switchover completes and the standby supervisor becomes active. The following occurs when the switchover is complete:
Step 6 From the CLI of the active Cisco Nexus 1110 Series, use the following commands to create a new secondary virtual service. Use the same information that you used to create the primary virtual service.
After you enter these commands, the Cisco Nexus 1110 Series prompts you for additional information. Once you have created the secondary virtual service on the active Cisco Nexus 1110 Series, an HA pair is formed between the primary virtual service and the secondary virtual service on the Cisco Nexus 1110 Series.
Step 7 Verify that the configuration is complete.
show virtual-service-blade summary
Step 8 You have completed this procedure.
The VSB is migrated from the Cisco Nexus 1010 series to the Cisco Nexus 1110 Series
Migrating a non HA VSB involves the following steps:
Step 1 From the CLI of Cisco Nexus Virtual Services Appliance, use the following commands to power off the non HA VSB on Cisco Nexus Virtual Services Appliance.
Step 2 Export non HA VSB to Cisco Nexus Virtual Services Appliance. See Creating a VSB Backup File.
Step 3 Copy a VSB configuration file to external storage. See Copying the VSB Backup File to External Storage.
Step 4 Import non HA VSB to Cisco Nexus 1110 Series. See Importing a VSB Backup File.
Step 5 From the CLI of Cisco Nexus 1110 Series, use the following commands to power on the imported non HA VSB on Cisco Nexus 1110 Series.
Example 7-1 Example for Migrating non HA VSB to Cisco Nexus 1110 Series
These examples show how to migrate non HA VSB to Cisco Nexus 1110 Series:
You can use this procedure to export an OVA from ESX and import it into Cisco Nexus Virtual Services Appliance product family as a VSB. This procedure involves running the migration tool script on the OVA, and then taking the generated tar file and use it for importing into Cisco Nexus Virtual Services Appliance product family.
Before beginning this procedure, you must know or do the following:
Migrating an OVA file to Cisco Nexus Virtual Services Appliance involves the following steps:
Step 1 Export the VSB to ESX and then copy the exported OVA into the esx_migration_tool/ directory.
Step 2 Run the migration tool script on the OVA.
If the version number of the VSB is supported by the migration tool, then use the following command to run the migration script.
./migration.sh <OVA file name > <vsb_type> <cookie> <ha-role> <vmware-vdiskmanager_location> [-v vsb_version ]
If the version number of the VSB is not supported by the migration tool, then use the following command to run the migration script.
./migration.sh <OVA file name > <vsb_type> <cookie> <ha-role> <vmware-vdiskmanager_location> [-f vbtype_xml_file_path]
Step 3 After the script executes, locate the split tar files in the esx_migration_tool/ directory.
Step 4 Import the VSB to the Cisco Nexus Virtual Services Appliance using the tar file. See Importing a VSB Backup File.
Step 5 Configure the interface VLAN values then power on the VSB.
To verify the migration, use the following commands:
|
|
---|---|
Displays the redundancy state (active or standby) and the redundancy role (primary or secondary) for each virtual service. |
|
Displays the redundancy state (active or standby) and the redundancy role (primary or secondary) for the Cisco Nexus Virtual Services Appliances. See Example 7-3 on page 7-9 . |
Example 7-2 Virtual Service Blade Configuration
These examples show how to display and verify virtual service blades during and after migration:
Example 7-3 System Configuration
This example shows how to display and verify the system configuration during migration:
Redundancy mode
---------------
administrative: HA
operational: HA
For additional information related to implementing system-level HA features, see the following sections:
|
|
---|---|
No new or modified standards are supported by this feature, and support for existing standards has not been modified by this feature. |
|
|
---|---|
|
|
---|---|
This section provides the migration feature release history.
|
|
|
---|---|---|