Cisco Nexus 1000V Troubleshooting Manual page 87

Chapter 7 VSM and VEM Modules
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 .
Table 7-1 Problems with the VSM (continued)
Symptom
After boot, VSM re-configured.
After boot, VSM stopped at "Loader
Loading."
After boot, secondary VSM reboots
continuously.
After a host reboot, the absence of a
VLAN, or the wrong system VLAN
on the VSM management port
profile, the control and management
connectivity of the VSM is lost.
OL-28795-01
Possible Causes
Startup configuration is deleted. Do one of the following:
Corrupt boot menu file.
Control VLAN or control
interface down
Active and standby VSMs fail to
synchronize.
The VSM is running on a VEM
that it manages, but the VSM
ports are not configured with
system port profiles.
Cisco Nexus 1000V Troubleshooting Guide, Release 4.2(1)SV2(2.1)
Solution
• If you have a saved backup copy of your
configuration file, restore the configuration
on the VSM.
copy source filesystem: filename
system:running-config
If not, reconfigure the VSM using the
•
following section in the Cisco Nexus 1000V
Getting Started Guide, Release
4.2(1)SV1(5.1):
Setting Up the Software
Boot the VSM from the CD ROM.
1.
From the CD Boot menu,
2.
choose Option 3, Install Nexus1000v only
if the disk unformatted and bring up new
image.
3. Do one of the following:
• If you have a saved backup copy of your
configuration file, restore the configuration
on the VSM.
copy source filesystem: filename
system:running-config
If not, reconfigure the VSM using the
•
following section in the Cisco Nexus 1000V
Getting Started Guide, Release
4.2(1)SV1(5.1):
Setting Up the Software
Check control connectivity between the active
and standby VSM.
From active VSM, check gsyncstats to identify
which application caused the failure.
show logging
Run the VEM connect script locally in the ESX
host where the VEM is running. Then go to the
VSM and configure the system VLANs in the
port profile used for management.
"Recovering Management and Control
Connectivity of a Host when a VSM is Running
on a VEM" section on page 7-12
Problems with the VSM
7-5