Checking The Vem Configuration - Cisco Nexus 1000V Troubleshooting Manual

Problems with the VSM
S e n d d o c u m e n t c o m m e n t s t o n e x u s 1 k - d o c f e e d b a c k @ c i s c o . c o m .
305
Enter the following command to recover connectivity:
Step 3
vem-connect -i <ip_address> -v <vlan> [ -pnic <vmnicN> ]
Example:
~ # vem-connect -i 172.23.232.67 -v 232 -p vmnic3
ltl 50 and veth Veth10 vmk1
Uplink port Po2 carries vlan 232
Set System Vlan 232 port Po2 305
Uplink port Eth9/2 carries vlan 232
Set System Vlan 232 port Eth9/2 18
Uplink port Eth9/4 carries vlan 232
Set System Vlan 232 port Eth9/4 20
Set System 232 for vmk
Step 4 Enter the following command to confirm management connectivity:
vemcmd show port vlans system
Example:
~ # vemcmd show port vlans system
LTL
10
11
12
13
14
15
16
18
20
49
50
305

Checking the VEM Configuration

You can use the following procedure to verify that the ESX host received the VEM configuration and
setup.
Step 1 On the ESX host, use the following command to confirm that the VEM Agent is running, and that the
correct host uplinks are added to the DVS.
vem status
Example:
~ # vem status
VEM modules are loaded
Switch Name
vSwitch0
Cisco Nexus 1000V Troubleshooting Guide, Release 4.2(1)SV2(2.1)
7-14
Po2 T
Native
VSM Port Mode VLAN/
SegID
6 Internal A
8 Internal A
9 Internal A
Internal A
Internal A
Internal A
Internal A
Internal A
Internal A
Internal A
Eth9/2 T
Eth9/4 T
Veth1 A
Veth10 A
Po2 T
Num Ports
64
1 FWD 210-211
VLAN Allowed
State Vlans/SegID
1 FWD 1
3969 FWD 3969
3969 FWD 3969
210 FWD 210
3968 FWD 3968
211 FWD 211
1 BLK 1
3971 FWD 3971
3971 FWD 3971
1 FWD 1
1 FWD 210-211,232
1 FWD 210-211,232
1 FWD 1
232 FWD 232
1 FWD 210-211,232
Used Ports Configured Ports
3 64
Chapter 7 VSM and VEM Modules
MTU Uplinks
1500 vmnic0
OL-28795-01