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 Supervisor Modules (VSMs) from virtual machines (VMs) to the Cisco Nexus Cloud Services Platform.
The hypervisor server represents one of the following hypervisors:
The following figure assumes that the standby state VSM VM on the hypervisor server is also assigned the secondary HA role. If your standby state VSM VM is assigned the primary role, you must reverse the roles in the flowchart.
You can move or migrate VSMs to the Cisco Nexus Cloud Services Platform without a service interruption.
This procedure describes the migration of a VSM from ESXi to the Cisco Nexus Cloud Services Platform using the ESX vSphere Client.
You have installed a primary and secondary Cisco Nexus Cloud Services Platform in HA mode.
Log in to the CLI of the Cisco Nexus Cloud Services Platform in EXEC mode.
Know the name of the VSM that you want to move or migrate from the hypervisor server.
The Cisco Nexus 1000V software must already be installed and upgraded to Release 5.2(1)SP1(7.1) on the hypervisor server.
When you are creating the secondary virtual service, use the same information that you used for the primary VSM for the following:
Caution | If you use a value that results in a mismatch with the hypervisor, the synchronization between the hypervisor and the Cisco Nexus Cloud Services Platform overwrites your configuration on the Cisco Nexus Cloud Services Platform. |
When you are creating the secondary virtual service, use the same information that you used for the VSM VM for the following:
Designate the secondary VSM as active. If the primary VSM is active, change it to make the secondary VSM active.
Use the commands in the following table to verify the migration.
Command | Purpose |
---|---|
show virtual-service-blade summary |
Displays a summary of the VSB status. |
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. |
This example shows how to display the virtual service blade summary:
switch# show virtual-service-blade summary ------------------------------------------------------------------------------- Name HA-Role HA-Status Status Location ------------------------------------------------------------------------------- NEW PRIMARY NONE VSB NOT PRESENT PRIMARY NEW SECONDARY NONE VSB NOT PRESENT SECONDARY CY_MTU PRIMARY ACTIVE VSB POWERED ON PRIMARY CY_MTU SECONDARY STANDBY VSB POWERED ON SECONDARY switch#
This example shows how to display the system redundancy status:
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
You can move or migrate a Cisco Nexus 1000V VSM from the Cisco Nexus Cloud Services Platform to a hypervisor server.
Note | This procedure describes the migration of a VSM from the Cisco Nexus Cloud Services Platform to ESXi using the ESX vSphere Client. |
Install a primary and secondary Cisco Nexus Cloud Services Platform in HA mode.
Designate the primary VSM as active and the secondary VSM as standby.
Log in to the CLI of the Cisco Nexus Cloud Services Platform in EXEC mode.
Know the name of the VSM that you want to move or migrate to the hypervisor server.
This section provides the migration feature release history.
Feature Name |
Releases |
Feature Information |
---|---|---|
VSM Migration |
4.0(4)SP1(1) |
This feature was introduced. |