Problems With Port Profiles; Problems With Hosts; Problems With Vm Traffic - Cisco Nexus 1000V Troubleshooting Manual

Problems with Hosts

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 .

Problems with Port Profiles

Symptom
You receive an error message
"Possible failure in
communication with vCenter
Server."
Port profile or port groups do
not appear on the vCenter
Server.
Problems with Hosts
Symptom
You receive an error message, DVS
Operation failed for one or more members."
The host is visible on the vCenter Server, but
not the VSM.
A module flap occurs.

Problems with VM Traffic

When troubleshooting problems with intra-host VM traffic, follow these guidelines:
Cisco Nexus 1000V Troubleshooting Guide, Release 4.2(1)SV2(2.1)
21-10
Possible Causes
The VSM is not connected to
the vCenter Server.
The port group name is not
unique.
—
Solution
Issue the vem status -v command to verify if the
VEM is running on the host.
Issue the vem unload command to unload the VEM.
In the vSphere Client, remove the stale DVS:
Go to the Host tab
1.
Networking->Configuration->
Distributed Virtual Switch
Click Remove.
2.
Issue the vemcmd show trunk command to verify
that there is an uplink carrying the control VLAN.
The profile applied to the uplink must be a system
profile with a control VLAN as a system VLAN.
Verify the control VLAN in the upstream switch port
and the path to the VSM VM. Make sure that one
uplink at most carries the control VLAN, or that all
uplinks and upstream ports carrying the control
VLAN are in port channels.
The VSM may be overloaded. Make sure that you
have 1 GB of memory and CPU shares for the VSM
VM on the vCenter Server.
Chapter 21
Solution
Issue the svs connection vc command
to connect to the vCenter Server.
Port group names must be unique
within a vCenter Server Datacenter.
Make sure you have issued the
vmware port-group command and
state enable command.
System
OL-28795-01