Cisco Nexus 1000V User Manual

7-2
Cisco Nexus 1000V Troubleshooting Guide, Release 5.2(1)SV3(1.1)
OL-31593-01
Chapter 7 VSM and VEM Modules
Troubleshooting a Module Not Coming Up on the VSM
• Checking the VEM Configuration, page 7-14
• Collecting Logs, page 7-16
• Troubleshooting L3Sec, page 8-1
Guidelines for Troubleshooting Modules
Follow these guidelines when troubleshooting a module controlled by the VSM.
• You must have a VSM VM and a VEM up and running.
• Make sure that you are running compatible versions of vCenter Server and VSM.
For more information, see the Cisco Nexus 1000V Compatibility Information.
• To verify network connectivity between the VSM and vCenter Server, ping the IP address of vCenter
Server. If you are using a domain name service (DNS) name, use the DNS name in the ping. If a ping
to vCenter Server fails, check to see if you can ping the gateway. Otherwise, check the mgmt0
interface configuration settings.
• In the Cisco Nexus1000V Distributed Virtual Switch (DVS), we support only one vmknic with
"capability l3control". If a second vmknic is added with the same capability then the host connected
as VEM modules on VSM in L3 mode will go offline. To recover from this scenario, we need to
remove both the vmknics from Cisco Nexus1000V DVS or migrate them back to vSwitch/VMware
DVS. Once you migrate or removed, you can recreate one vmknic on Cisco Nexus1000V DVS or
migrate one of the vmknic from vswitch/VMware DVS back to Cisco Nexus1000V DVS.
• Make sure that the firewall settings are OFF on the vCenter Server. If you want the firewall settings,
and check to see if these ports are open:
– Port 80
– Port 443
• If you see the following error, verify that the VSM extension was created from vCenter Server:
– ERROR: [VMware vCenter Server 4.0.0 build-150489]
Extension key was not registered before its use
To verity that the extension or plugin was created, see the “Finding the Extension Key on the Cisco
Nexus 1000V” section on page 3-7.
For more information about extension keys or plugins, see the “Managing Extension Keys” section
on page 3-6.
• If you see the following error, see the “Checking the vCenter Server Configuration” section on
page 7-10.
– ERROR: Datacenter not found
• For a list of terms used with the Cisco Nexus 1000V, see the Cisco Nexus 1000V Getting Started
Guide.

Cisco Nexus 1000V Specifications

General

Type	Virtual Switch
Manageable	Yes
NetFlow	Yes
SPAN	Yes
ERSPAN	Yes
Operating System	Cisco NX-OS
Form Factor	Virtual
Hypervisor Support	VMware ESXi
Features	VXLAN
Security Features	Port Security, Private VLANs, ACLs