Cisco Nexus 1000V - Recovering Management and Control Connectivity of a Host When a VSM Is Running on a VEM

7-12
Cisco Nexus 1000V Troubleshooting Guide, Release 5.2(1)SV3(1.1)
OL-31593-01
Chapter 7 VSM and VEM Modules
Problems with the VSM
• Otherwise, continue with the next step.
Step 7 On the VSM, enter the following commands to verify that the VSM MAC appears in the control and
packet VLANs.
a. config t
b. module vem module_number execute vemcmd show l2 control_vlan_id
c. module vem module_number execute vemcmd show l2 packet_vlan_id
The VSM eth0 and eth1 MAC addresses should display in the host control and packet VLANs.
Example:
switch# config t
switch(config)# module vem 3 execute vemcmd show l2 3002
Bridge domain 3002 brtmax 100, brtcnt 3, timeout 120
Dynamic MAC 00:50:56:be:7c:a7 LTL 16 pvlan 0 timeout 110
Dynamic MAC 00:02:3d:40:0b:0c LTL 10 pvlan 0 timeout 110
switch(config)# module vem 3 execute vemcmd show l2 3003
Bridge domain 3002 brtmax 100, brtcnt 3, timeout 120
Dynamic MAC 00:50:56:be:7c:a7 LTL 16 pvlan 0 timeout 110
Dynamic MAC 00:02:3d:20:0b:0c LTL 10 pvlan 0 timeout 110
Step 8 Do one of the following:
• If the MAC address of the VSM does not appear in the output of Step 7, check the VEM
configuration as explained in “Checking the VEM Configuration” section on page 7-14.
• Otherwise, you have completed this procedure.
Recovering Management and Control Connectivity of a Host When a VSM is
Running on a VEM
When the VSM is running on a VEM that it manages, but the VSM ports are not configured with system
port profiles, the control and management connectivity of the VSM can be lost after a host reboot or
similar event. To recover from the loss, you can run the VEM connect script locally in the ESX host
where the VEM is running, and then go to the VSM and configure the system VLANs in the port profile
used for management.
Using the VEM Connect Script
The VEM connect script sets a given VLAN as a system VLAN on the VTEP that has the given IP
address and also sets the VLAN on all the required uplinks.
If no uplink is carrying this VLAN, you also need to specify the uplink (vmnicN) on which this VLAN
needs to be applied. The uplink can be a single port or a port-channel member. If it is the latter, then the
script applies the VLANs as a system VLAN to all member uplinks of that port channel.
vem-connect -i ip_address -v vlan [ -p vmnicN ]
The -p parameter to the script is optional. If you run the script without the -p parameter, it tries to locate
an uplink that carries this VLAN. If no such uplink exists, it reports this as an error. You need to specify
the -p parameter and rerun the script.
You can recover management and control connectivity of a host when a VSM is running on a VEM.