Cisco Nexus 1000V, Troubleshooting Manual, Page: 219 / 280

C H A P T E R
22-1
Cisco Nexus 1000V Troubleshooting Guide, Release 5.2(1)SV3(1.1)
OL-31593-01
22
System
This chapter describes how to identify and resolve problems related to the Nexus 1000V system.
This chapter includes the following sections:
• Information About the System, page 22-1
•
General Restrictions for vCenter Server, page 22-2
• Recovering a DVS, page 22-2
•
Problems Related to VSM and vCenter Server Connectivity, page 22-5
• Connection Failure After ESX Reboot, page 22-6
•
VSM Creation, page 22-9
• Port Profiles, page 22-9
•
Problems with Hosts, page 22-10
• Problems with VM Traffic, page 22-10
•
VEM Troubleshooting Commands, page 22-11
• VEM Log Commands, page 22-12
•
Error Messages, page 22-12
Information About the System
Cisco Nexus 1000V provides Layer 2 switching functions in a virtualized server environment. Nexus
1000V replaces virtual switches within ESX servers and allows users to configure and monitor the
virtual switch using the Cisco NX-OS command line interface. Nexus 1000V also gives you visibility
into the networking components of the ESX servers and access to the virtual switches within the
network.
The Nexus 1000V manages a data center defined by the vCenter Server. Each server in the Datacenter
is represented as a linecard in Nexus 1000V and can be managed as if it were a line card in a physical
Cisco switch. The Nexus 1000V implementation has two components:
•
Virtual supervisor module (VSM) – This is the control software of the Nexus 1000V distributed
virtual switch. It runs on a virtual machine (VM) and is based on NX-OS.
• Virtual Ethernet module (VEM) – This is the part of Cisco Nexus 1000V that actually switches data
traffic. It runs on a VMware ESX 4.0 host. Several VEMs are controlled by one VSM. All the VEMs
that form a switch domain should be in the same virtual Datacenter as defined by VMware vCenter
Server.