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 VSM to the Cisco Nexus Virtual Services Appliance product family, and includes the following sections:
After you have installed the Cisco Nexus Virtual Services Appliance, you can move, or migrate, your VSMs from virtual machines to the Cisco Nexus Virtual Services Appliance.
Figure 5-1 shows the process for migrating a VSM to the Cisco Nexus Virtual Services Appliance.
NoteFigure 5-1 assumes that the standby state VSM on the ESX is also assigned the secondary HA role. If your standby state VSM is assigned the primary role, then reverse the roles in the flow chart.
Figure 5-1 Migrating a VSM to the Cisco Nexus Virtual Services Appliance
Follow these guidelines and limitations when moving or migrating a VSM from a virtual machine to the Cisco Nexus Virtual Services Appliance:
Use this procedure to move, or migrate, a VSM to the Cisco Nexus Virtual Services Appliance without service interruption.
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)SV1(5.2) .
– For information about upgrading see the Cisco Nexus 1000V Software Installation and Upgrade Guide, Release 4.2(1)SV1(5.2)
Note If you use a value that results in a mismatch with the ESX, then the synchronization between the ESX and the Cisco Nexus Virtual Services Appliance overwrites your configuration on the Cisco Nexus Virtual Services Appliance.
Step 1 From the ESX vSphere client, right-click the standby VSM and choose power off from the popup menu.
The standby VSM is powered off.
Step 2 From the ESX vSphere client, right-click the standby VSM and choose delete from disk from the popup menu.
The standby VSM is removed from the ESX server. Only the primary VSM is active on the ESX server with modules attached.
Step 3 From the CLI of the active Cisco Nexus Virtual Services Appliance, use the following commands to 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.
virtual-service-blade-type new new iso filename
Step 4 Verify that the configuration is complete.
show virtual-service-blade summary
Once you have created the virtual service on the primary Cisco Nexus Virtual Services Appliance, an HA pair forms between the secondary VSM on the ESX and the primary virtual service on the Cisco Nexus Virtual Services Appliance.
Step 5 From the CLI of the secondary VSM on the ESX, use the following command to verify the redundancy status of the VSMs.
If the output indicates the following, then you can proceed with a system switchover.
Redundancy mode
---------------
administrative: HA
operational: HA
Step 6 From the CLI of the secondary VSM on the ESX server, use the following command to initiate a manual switchover to the standby virtual service on the Cisco Nexus Virtual Services Appliance.
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 Virtual Services Appliance is now the active VSM.
Step 7 From the ESX vCenter client, right-click the standby VSM and choose power off from the popup menu.
The standby VSM is powered off.
Step 8 From the ESX vCenter client, right-click the standby VSM and choose delete from disk from the popup menu.
The standby VSM is removed from the ESX server.
Step 9 From the CLI of the active Cisco Nexus Virtual Services Appliance, 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 Virtual Services Appliance prompts you for additional information.
Once you have created the secondary virtual service on the active Cisco Nexus Virtual Services Appliance, an HA pair is formed between the primary virtual service and the secondary virtual service on the Cisco Nexus Virtual Services Appliance.
Step 10 Verify that the configuration is complete.
show virtual-service-blade summary
Step 11 You have completed this procedure.
The VSM is migrated from the ESX host to the Cisco Nexus Virtual Services Appliance.
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 5-2 on page 5-7 . |
Example 5-1 Virtual Service Blade Configuration
These examples show how to display and verify virtual service blades during and after migration:
Example 5-2 System Configuration
This example shows how to display and verify the system configuration during migration:
Redundancy mode
---------------
administrative: HA
operational: HA
Use this procedure to move, or migrate, a Cisco Nexus 1000V Virtual Supervisor module (VSM) from the Cisco Nexus Virtual Services Appliance to ESX server.
Before beginning this procedure, you must know or do the following:
Step 1 From the CLI of the secondary VSM on the Cisco Nexus Virtual Services Appliance, use the following commands to shut down the secondary standby VSM on the Cisco Nexus Virtual Services Appliance.
Step 2 Create the secondary VSM on the ESX server. The release number of the VSM installed on the ESX server should be the same as th at of the VSM already installed on the Cisco Nexus Virtual Services Appliance.
See the Cisco Nexus 1000V Software Installation and Upgrade Guide, Release 4.2(1)SV1(5.2) for more information about installating the software on the ESX server.
Step 3 When creating the secondary VSM on the ESX server, use the same information that you used for creating the the primary VSM on the Cisco Nexus Virtual Services Appliance for the following:
Step 4 When creating the secondary VSM, use the same information used for the VSM on the Cisco Nexus Virtual Services Appliance for the following:
Step 5 From the ESX vSphere Client, right-click the secondary VSM and choose power on from the popup menu. Ensure that there is proper HA communication between the primary VSM on the Cisco Nexus Virtual Services Appliance and the secondary VSM on the ESX server.
Step 6 Designate the secondary VSM on the ESX server as active.
Step 7 From the CLI of the primary Cisco Nexus Virtual Services Appliance, use the following commands to to shut down the primary VSM on the Cisco Nexus Virtual Services Appliance.
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 choose power on from the popup menu.
The primary VSM is powered on.
Step 10 From the CLI of the Cisco Nexus Virtual Services Appliance, use the following commands to remove the VSM.
Step 11 You have completed this procedure.
The VSM is migrated from the Cisco Nexus Virtual Services Appliance to the ESX server.
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.
|
|
|
---|---|---|