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 Virtual Supervisor Module (VSM) to the Cisco Nexus Cloud Services Platform product family and includes the following sections:
After you have installed the Cisco Nexus Cloud Services Platform, you can move or migrate your VSMs from Virtual Machines (VMs) to the Cisco Nexus Cloud Services Platform.
Figure 5-1 shows the process for migrating a VSM to the Cisco Nexus Cloud Services Platform.
Note The hypervisor server represents one of the following hypervisors:
Note Figure 5-1 assumes that the standby state VSM on the hypervisor server is also assigned the secondary HA role. If your standby state VSM is assigned the primary role, you must reverse the roles in the flow chart.
Figure 5-1 Migrating a VSM to the Cisco Nexus Cloud Services Platform
You can move or migrate a VSM to the Cisco Nexus Cloud Services Platform without a service interruption.
Note This procedure explains the migration of a VSM from ESXi to the Cisco Nexus Cloud Service Platform using the ESX vSphere Client.
Before beginning this procedure, you must know or do the following:
– For information about installing the software, see the Cisco Nexus 1000V Software Installation and Upgrade Guide, Release 4.2(1)SV2(2.1) .
– For information about upgrading, see the Cisco Nexus 1000V Software Installation and Upgrade Guide, Release 4.2(1)SV2(2.1)
Step 1 From the ESX vSphere client, right-click the standby VSM and from the drop-down list, choose power off . The standby VSM is powered off.
Step 2 From the ESX vSphere client, right-click the standby VSM and from the drop-down list, choose delete from disk .
The standby VSM is removed from the hypervisor server. Only the primary VSM is active on the hypervisor server with modules attached.
Step 3 From the CLI of the active Cisco Nexus Cloud Services Platform, create a primary virtual service for the VSM that you want to migrate. Use the same information that you used to create the secondary VSM.
Step 4 Verify that the configuration is complete.
After you create the virtual service on the primary Cisco Nexus Cloud Services Platform, an HA pair forms between the secondary VSM on the hypervisor server and the primary virtual service on the Cisco Nexus Cloud Services Platform.
Step 5 From the CLI of the secondary VSM on the hypervisor, verify the redundancy status of the VSMs.
If the output indicates the following, you can proceed with a system switchover.
Redundancy mode
---------------
administrative: HA
operational: HA
Step 6 From the CLI of the secondary VSM on the hypervisor server, initiate a manual switchover to the standby virtual service on the Cisco Nexus Cloud Services Platform.
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:
The primary virtual service on the Cisco Nexus Cloud Services Platform is now the active VSM.
Step 7 From the ESX vCenter client, right-click the standby VSM and from the drop-down list, choose power off .
The standby VSM is powered off.
Step 8 From the ESX vCenter client, right-click the standby VSM and from the drop-down list, choose delete from disk .
The standby VSM is removed from the hypervisor server.
Step 9 From the CLI of the active Cisco Nexus Cloud Services Platform, 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 the commands that are shown in the output, the Cisco Nexus Cloud Services Platform prompts you for additional information.
Once you create the secondary virtual service on the active Cisco Nexus Cloud Services Platform, an HA pair is formed between the primary virtual service and the secondary virtual service on the Cisco Nexus Cloud Services Platform.
Step 10 Verify that the configuration is complete.
You have completed this procedure.
The VSM is migrated from the ESX host to the Cisco Nexus Cloud Services Platform.
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. See Example 5-1 on page 5-7 . |
|
Displays the redundancy state (active or standby) and the redundancy role (primary or secondary) for the Cisco Nexus Cloud Services Platforms. See Example 5-2 on page 5-7 . |
Example 5-1 Virtual Service Blade Configuration
Example 5-2 System Configuration
Redundancy mode
---------------
administrative: HA
operational: HA
You can move or migrate a Cisco Nexus 1000V Virtual Supervisor module (VSM) from the Cisco Nexus Cloud Services Platform to an hypervisor server.
Note This procedure explains the migration of a VSM from ESXi to the Cisco Nexus Cloud Service Platform using the ESX vSphere Client.
Before beginning this procedure, you must know or do the following:
Step 1 From the CLI of the secondary VSM on the Cisco Nexus Cloud Services Platform, shut down the secondary standby VSM on the Cisco Nexus Cloud Services Platform.
Step 2 Create the secondary VSM on the hypervisor server. The release number of the VSM that is installed on the hypervisor server should be the same as that of the VSM already installed on the Cisco Nexus Cloud Services Platform.
See the Cisco Nexus 1000V Software Installation and Upgrade Guide, Release 4.2(1)SV2(2.1) , for more information about installing the software on the hypervisor server.
Step 3 When creating the secondary VSM on an hypervisor server, use the same information that you used for creating the primary VSM on the Cisco Nexus Cloud Services Platform for the following:
Step 4 When creating the secondary VSM, use the same information that you used for the VSM on the Cisco Nexus Cloud Services Platform for the following:
Step 5 From the ESX vSphere Client, right-click the secondary VSM and from the drop-down list, choose power on. Ensure that there is HA communication between the primary VSM on the Cisco Nexus Cloud Services Platform and the secondary VSM on the hypervisor server.
Step 6 Designate the secondary VSM on the hypervisor server as active.
Step 7 From the CLI of the primary Cisco Nexus Cloud Services Platform, use the following commands to shut down the primary VSM on the Cisco Nexus Cloud Services Platform.
Step 8 Create the primary VSM on ESX using the same parameters used in this procedure for creating the secondary VSM.
Step 9 From the ESX vSphere Client, right-click the primary VSM and from the drop-down list, choose power on.
The primary VSM is powered on.
Step 10 From the CLI of the Cisco Nexus Cloud Services Platform, use the following commands to remove the VSM.
The VSM is migrated from the Cisco Nexus Cloud Services Platform to the hypervisor server.
You have completed this procedure.
For additional information related to migrating a VSM, see the following sections:
|
|
---|---|
Cisco Nexus Cloud Services Platform Software Installation and Upgrade Guide |
|
Cisco Nexus Cloud Services Platform Hardware Installation Guide |
|
This section provides the migration feature release history.
|
|
|
---|---|---|