7-5
Cisco Nexus 1000V Troubleshooting Guide, Release 5.2(1)SV3(1.1)
OL-31593-01
Chapter 7 VSM and VEM Modules
Problems with the VSM
After boot, VSM is reconfigured. Startup configuration is deleted. 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:
Setting Up the Software
After boot, VSM is stopped at
“Loader Loading.”
Corrupt boot menu file.
1. Boot the VSM from the CD ROM.
2. From the CD Boot menu,
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:
Setting Up the Software
After boot, the secondary VSM
reboots continuously.
Control VLAN or control
interface down
Check control connectivity between the active
and the standby VSM.
Active and standby VSMs fail to
synchronize.
From the active VSM, check system manager
errors to identify which application caused the
failure.
show system internal sysmgr
event-history errors
show logging
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.
The VSM is running on a VEM
that it manages, but the VSM
ports are not configured with
system port profiles.
Run the VEM connect script locally in the ESX
host where the VEM is running. Go to the VSM
and configure the system VLAN 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
Symptom Possible Causes Solution
To Next Page
Loading...
