Cisco Nexus Virtual Services Appliance Software Configuration Guide, Release 4.2(1)SP1(5.1)
Migrating a VSM
Downloads: This chapterpdf (PDF - 272.0KB) The complete bookPDF (PDF - 4.22MB) | Feedback

Table of Contents

Migrating a VSM

Information About Migrating a VSM

Guidelines and Limitations

Migrating a VSM to the

Verifying the Migration

Migrating a Virtual Supervisor Module from to ESX Server

Additional References

Related Documents

Standards

MIBs

RFCs

Feature History for Migration

Information About Migrating a VSM

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.


Note Figure 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

 

 

Guidelines and Limitations

Follow these guidelines and limitations when moving or migrating a VSM from a virtual machine to the Cisco Nexus Virtual Services Appliance:

• You must use the same management VLAN for both the VSM that you are migrating and the Cisco Nexus Virtual Services Appliance.

  • You must use the same RAM size and disk size for the virtual service as those used for the VSM virtual machine.

Migrating a VSM 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 YOU BEGIN

Before beginning this procedure, you must know or do the following:

  • You have installed a primary and secondary Cisco Nexus Virtual Services Appliance in HA mode.
  • You are logged in to the CLI of the Cisco Nexus Virtual Services Appliance in EXEC mode.
  • You know the name of the VSM that you want to move or migrate from the ESX.
  • The Cisco Nexus 1000V software must already be installed and upgraded to Release 4.2(1)SV1(5.2) on the ESX server.

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)

  • When creating the secondary virtual service, use the same information that you used for the primary VSM 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 ESX, then the synchronization between the ESX and the Cisco Nexus Virtual Services Appliance overwrites your configuration on the Cisco Nexus Virtual Services Appliance.


  • When creating the secondary virtual service, use the same information used for the VSM VM for the following:

RAM size

Disk size

  • Designate the secondary VSM as active. If primary VSM is active, then change it to make the secondary VSM active

DETAILED STEPS


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.

config t

virtual service blade name

ram

virtual-service-blade-type new new iso filename

enable primary

Example:
switch# config t
switch(config)# virtual-service-blade VB-1
switch(config-vsb-config)# virtual-service-blade-type new new dcos_vsm.iso
switch(config-vsb-config)# ramsize 2048
switch(config-vsb-config)# disksize 4
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)#
 

Step 4 Verify that the configuration is complete.

show virtual-service-blade summary

 
Example:
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
 
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 NOT PRESENT Nexus1010-SECONDARY
 

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.

show system redundancy status

If the output indicates the following, then you can proceed with a system switchover.

  • The presence of an active VSM
  • The presence of a standby VSM in the HA standby redundancy state
Example:
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
 

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.

system switchover

Example:
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#
 

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 VSM on the ESX reboots.
  • The virtual service configuration on the Cisco Nexus Virtual Services Appliance is overwritten to match what is on the VSM on the ESX.

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.

config t

virtual service blade name

enable secondary

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.

Example:
switch# config t
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
 

Step 10 Verify that the configuration is complete.

show virtual-service-blade summary

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
 
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 POWERED ON Nexus1010-SECONDARY
 

Step 11 You have completed this procedure.

The VSM is migrated from the ESX host to the Cisco Nexus Virtual Services Appliance.


 

Verifying the Migration

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 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:

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
 

Example 5-2 System Configuration

This example shows how to display and verify the system configuration during migration:

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

Migrating a Virtual Supervisor Module from Cisco Nexus Virtual Services Appliance to ESX Server

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 YOU BEGIN

Before beginning this procedure, you must know or do the following:

  • You have installed a primary and secondary Cisco Nexus Virtual Services Appliance in HA mode.
  • Designate the primary VSM as active and the secondary VSM as standby.
  • Make sure that on the ESX server, uplink allows the control, management, and packet VLANs of the VSM to be migrated.
  • You are logged in to the CLI of the Cisco Nexus Virtual Services Appliance in EXEC mode.
  • You know the name of the VSM that you want to move or migrate to ESX server.

DETAILED STEPS


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.

config terminal

virtual service blade name

shutdown secondary

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:

ISO filename

Management IP address

Management VLAN ID

Domain ID

Hostname

Default gateway

Control and packet VLAN IDs

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:

RAM size

Disk size

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.

config terminal

virtual service blade name

shut primary

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.

config terminal

no virtual service blade name

Step 11 You have completed this procedure.

The VSM is migrated from the Cisco Nexus Virtual Services Appliance to the ESX server.

Additional References

For additional information related to implementing system-level HA features, see the following sections:

Related Documents

 

Related Topic
Document Title

Software setup configuration

Cisco Nexus Virtual Services Appliance Software Installation and Upgrade Guide, Release 4.2(1)SP1(5.1)

Virtual service configuration

Configuring Virtual Service Blades

Cisco Nexus Virtual Services Appliance installation

Cisco Nexus Virtual Services Appliance Hardware Installation Guide

Cisco Nexus Virtual Services Appliance commands

Cisco Nexus Virtual Services Appliance Command Reference, Release 4.2(1)SP1(5.1)

Standards

 

Standards
Title

No new or modified standards are supported by this feature, and support for existing standards has not been modified by this feature.

MIBs

MIBs
MIBs Link

No MIBs are supported by this feature

RFCs

RFCs
Title

No RFCs are supported by this feature

Feature History for Migration

This section provides the migration feature release history.

 

Feature Name
Releases
Feature Information

VSM migration

4.0(4)SP1(1)

This feature was introduced.