CHAPTER
7-1
Cisco Nexus 1000V Troubleshooting Guide, Release 5.2(1)SV3(1.1)
OL-31593-01
7
VSM and VEM Modules
This chapter describes how to identify and resolve problems that relate to modules and includes the
following sections:
• Information About Modules, page 7-1
• Troubleshooting a Module Not Coming Up on the VSM, page 7-1
• Problems with the VSM, page 7-4
• VSM and VEM Troubleshooting Commands, page 7-17
Information About Modules
The Cisco Nexus 1000V manages a data center defined by a VirtualCenter. Each server in the data center
is represented as a module in the Cisco Nexus 1000V and can be managed as if it were a module in a
physical Cisco switch.
The Cisco Nexus 1000V implementation has two parts:
• Virtual Supervisor Module (VSM)—Control software of the Cisco Nexus 1000V distributed virtual
switch. It runs on a virtual machine (VM) and is based on NX-OS software.
• Virtual Ethernet Module (VEM)—Part of the Cisco Nexus 1000V that actually switches data traffic.
It runs on a VMware ESX host. Several VEMs are controlled by one VSM. All the VEMs that form
a switch domain should be in the same virtual data center as defined by VMware VirtualCenter.
Troubleshooting a Module Not Coming Up on the VSM
This section includes the following topics:
• Guidelines for Troubleshooting Modules, page 7-2
• Flowchart for Troubleshooting Modules, page 7-3
• Verifying the VSM Is Connected to vCenter Server, page 7-6
• Verifying the VSM Is Configured Correctly, page 7-7
• Checking the vCenter Server Configuration, page 7-10
• Checking Network Connectivity Between the VSM and the VEM, page 7-10
• Recovering Management and Control Connectivity of a Host When a VSM is Running on a VEM,
page 7-12