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 contains the following sections:
After you have installed the Cisco Nexus Cloud Services Platform, you can move or migrate your virtual service blades (VSBs) from the Cisco Nexus 1010 series to the Cisco Nexus 1110 series. For more information, see Information About Virtual Service Blades.
The Cisco Nexus Cloud Services Platform has the following guidelines and limitations for migrating a VSB from the Cisco Nexus 1010 series to the Cisco Nexus 1110 series:
You cannot form an HA pair with a Cisco Nexus 1110-S and a Cisco Nexus 1110-X. An HA pair can only be formed with the same hardware.
You must use the same management VLAN for both the Cisco Nexus 1010 series and the Cisco Nexus 1110 series.
You must use the same RAM size and disk size for the new VSB on the Cisco Nexus Cloud Services Platform that you used for migrating the VSB on the Cisco Nexus 1110 series.
Step 1 | Verify that the Cisco Nexus 1010 series has the VSBs configured that need to be migrated to the Cisco Nexus 1110 series. |
Step 2 | Set up the Cisco
Nexus 1110 series in a redundant HA pair.
See the Cisco Nexus Cloud Services Platform Software Installation and Upgrade Guide. |
Step 3 | Migrate the HA
VSBs such as the VSM and Cisco VSG to the Cisco Nexus 1110.
See Migrating an HA Virtual Service Blade to the Cisco Nexus 1110 Series. |
Step 4 | Migrate the non-HA VSBs such as the Cisco NAM to the Cisco Nexus 1110. |
You have installed a primary and secondary Cisco Nexus 1110 in HA mode.
Log in to the CLI of the Cisco Nexus 1110 in EXEC mode.
Know the name of the VSB that you want to move or migrate from the Cisco Nexus 1010.
When you are creating the secondary virtual service, use the same information that you used for the primary VSB for the following:
ISO filename
Management IP address
Domain ID
Hostname
Default gateway
Control and packet VLAN IDs
Note | If you use a value that results in a mismatch with the Cisco Nexus 1110, the synchronization between the Cisco Nexus 1110 and the Cisco Nexus 1010 overwrites your configuration on the Cisco Nexus 1010. |
When you are creating the secondary virtual service, use the same information that you used for the VSB for the following:
Designate the secondary VSM as active. If the primary VSM is active, change it to make the secondary VSM active.
This example shows how to create a primary virtual service for the VSB that you want to migrate:
switch# configure terminal switch(config)# virtual-service-blade VB-1 switch(config-vsb-config)# virtual-service-blade-type new dcos_vsm.iso switch(config-vsb-config)# interface control vlan 1322 switch(config-vsb-config)# interface packet vlan 1323 switch(config-vsb-config)# enable primary Enter domain id[1-4095]: 1322 Management IP version [V4/V6]: [V4] Enter Management IP address: 10.78.109.67 Enter Management subnet mask: 255.255.255.224 IPv4 address of the default gateway: 10.78.109.65 Enter HostName: switch Enter the password for 'admin': xz35vb1zx switch(config-vsb-config)#
This example shows how to verify the configuration:
switch(config-vsb-config)# show virtual-service-blade summary ------------------------------------------------------------------------------- Name Role State Nexus1010-Module ------------------------------------------------------------------------------- VB-1 PRIMARY VSB DEPLOY IN PROGRESS Nexus1010-PRIMARY VB-1 SECONDARY VSB NOT PRESENT Nexus1010-SECONDARY
This example shows how to check the redundancy status of the VSBs:
switch#show system redundancy status Redundancy role --------------- administrative: primary operational: primary Redundancy mode --------------- administrative: HA operational: HA This supervisor (sup-1) ----------------------- Redundancy state: Standby Supervisor state: HA standby Internal state: HA standby Other supervisor (sup-2) ------------------------ Redundancy state: Active Supervisor state: Active Internal state: Active with HA standby
This example shows how to initiate a manual switchover to the standby virtual service:
switch# system switchover ---------------------------- 2009 Mar 31 04:21:56 n1000v %$ VDC-1 %$ %SYSMGR-2-HASWITCHOVER_PRE_START: This supervisor is becoming active (pre-start phase). 2009 Mar 31 04:21:56 n1000v %$ VDC-1 %$ %SYSMGR-2-HASWITCHOVER_START: This supervisor is becoming active. 2009 Mar 31 04:21:57 n1000v %$ VDC-1 %$ %SYSMGR-2-SWITCHOVER_OVER: Switchover completed. 2009 Mar 31 04:22:03 n1000v %$ VDC-1 %$ %PLATFORM-2-MOD_REMOVE: Module 1 removed (Serial number ) switch#
This example shows how to create a secondary virtual service:
switch# configure terminal switch(config)# virtual-service-blade VB-1 switch(config-vsb-config)# enable secondary Enter vsb image: [dcos_vsm.iso] Enter domain id[1-4095]: 1322 Management IP version [V4/V6]: [V4] Enter Management IP address: 10.78.109.67 Enter Management subnet mask length: 27 IPv4 address of the default gateway: 10.78.109.65 Enter HostName: switch Enter the password for 'admin': xz35vb1zx
This examples shows the VSB summary after you create a secondary virtual service.
Example: switch(config-vsb-config)# show virtual-service-blade summary ------------------------------------------------------------------------------- Name Role State Nexus1010-Module ------------------------------------------------------------------------------- VB-1 PRIMARY VSB POWERED ON Nexus1010-PRIMARY VB-1 SECONDARY VSB DEPLOY IN PROGRESS Nexus1010-SECONDARY
Step 1 | From the CLI of the Cisco Nexus Cloud Services Platform, power off the non-HA VSB on the Cisco Nexus Cloud Services Platform. |
Step 2 | Export the non-HA VSB to the Cisco Nexus Cloud Services Platform. See Exporting a Virtual Service Blade Backup File. |
Step 3 | Copy a VSB configuration file to external storage location. See Copying the Exported Virtual Service Blade to an External Storage Location. |
Step 4 | Import the non-HA VSB to the Cisco Nexus 1110. See Importing a Virtual Service Blade. |
Step 5 | From the CLI of the Cisco Nexus 1110, power on the imported non-HA VSB on the Cisco Nexus 1110. |
This example shows how to migrate a non-HA VSB to the Cisco Nexus 1110:
switch# configure terminal switch(config)# virtual-service-blade NAM switch(config-vsb-config)# shut switch(config-vsb-config)# export Note: export started.. Note: please be patient.. ... Note: export completed... switch(config-vsb-config)# copy bootflash:export-import/1/ ftp: Enter the source filename: Vdisk1.img.tar.00 Enter vrf (If no input, current vrf 'default' is considered): Enter hostname for the ftp server: 10.78.109.51 Enter username: administrator Password: ***** Transfer of file Completed Successfully ***** On Cisco Nexus 1110 Series CLI: switch# configure terminal switch(config)# copy ftp: bootflash:export-import Enter source filename: Vdisk1.img.tar.00 Enter vrf (If no input, current vrf 'default' is considered): Enter hostname for the ftp server: 10.78.109.51 Enter username: administrator Password: ***** Transfer of file Completed Successfully ***** switch#configure terminal switch(config)# virtual-service-blade NAM switch(config-vsb-config)# import primary Vdisk1.img.tar.00 Note: import started.. Note: please be patient.. ... Note: Import cli returns check VSB status for completion switch(config-vsb-config)# no shutdown
You can export an OVA from ESX and import it into the Cisco Nexus Cloud Services Platform as a VSB. You must run the migration tool script on the OVA and then take the generated tar file and use it for importing into the Cisco Nexus Cloud Services Platform.
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 migration tool supports the version number of the VSB, enter the following command: ./migration.sh <ova-filename> <vsb_type> <cookie> <ha-role> <vmware-vdiskmanager_location> [-v vsb_version]
If the migration tool does not support the version number of the VSB, enter the following command: ./migration.sh <ova-filename> <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 | Use the tar file to import the VSB to the Cisco Nexus Cloud Services Platform. See Importing a Virtual Service Blade. |
Step 5 | Configure the interface VLAN values and power on the VSB. |
This example shows how to run the migration script if the migration tool supports the VSB version number:
./migration.sh VSM.ova VSM 123456 primary /usr/bin/ -v 5.2(1)SP1(7.1)
This example shows how to run the migration script if the migration tool does not support the VSB version number:
./migration.sh VSM.ova VSM 678910 secondary /usr/bin/ -f /tmp/ovf_vbtype.xml
To verify the migration, use the following commands
Command | Purpose |
---|---|
show virtual-service-blade summary |
Displays the redundancy state (active or standby) and the redundancy role (primary or secondary) for each virtual service. |
show system redundancy status |
Displays the redundancy state (active or standby) and the redundancy role (primary or secondary) for the Cisco Nexus Cloud Services Platform. |
switch(config-vsb-config)# show virtual-service-blade summary ------------------------------------------------------------------------------- Name Role State Nexus1010-Module ------------------------------------------------------------------------------- VB-1 PRIMARY VSB NOT PRESENT Nexus1010-PRIMARY VB-1 SECONDARY VSB DEPLOY IN PROGRESS Nexus1010-SECONDARY switch(config-vsb-config)# show virtual-service-blade summary ------------------------------------------------------------------------------- Name Role State Nexus1010-Module ------------------------------------------------------------------------------- VB-1 PRIMARY VSB NOT PRESENT Nexus1010-PRIMARY VB-1 SECONDARY VSB POWERED ON Nexus1010-SECONDARY
switch# show system redundancy status Redundancy role --------------- administrative: primary operational: primary Redundancy mode --------------- administrative: HA operational: HA This supervisor (sup-1) ----------------------- Redundancy state: Standby Supervisor state: HA standby Internal state: HA standby Other supervisor (sup-2) ------------------------ Redundancy state: Active Supervisor state: Active Internal state: Active with HA standby
This section provides the migration feature release history.
Feature Name |
Releases |
Feature Information |
---|---|---|
VSB Migration |
4.0(4)SP1(3) |
This feature was introduced. |