Cisco Nexus 1000V Troubleshooting Manual page 79

Chapter 6 High Availability
Symptom
The active VSM does not see
the standby VSM.
The active VSM does not
complete synchronization
with the standby VSM.
OL-31593-01
Possible Causes
Roles are not configured
properly.
• Check the role of the two
VSMs by using the show
system redundancy
status command.
Network connectivity
problems.
Check that the control and
•
management VLAN
connectivity between the
VSM at the upstream and
virtual switches.
Version mismatch between
VSMs.
Check that the primary
•
and secondary VSMs are
using the same image
version by using the show
version command.
Fatal errors during gsync
process.
Check the gsyncctrl log
•
using the show system
internal log sysmgr
gsyncctrl command and
look for fatal errors.
The VSM has
•
connectivity only through
the management
interface.
Check the output of the
•
show system internal
redundancy info
command and verify if the
degraded_mode flag is set
to true.
Cisco Nexus 1000V Troubleshooting Guide, Release 5.2(1)SV3(1.1)
Problems with High Availability
Solution
1. Confirm that the roles are the
primary and secondary role,
respectively.
If needed, use the system
2.
redundancy role command to
correct the situation.
Save the configuration if roles are
3.
changed.
If network problems exist, do the
following:
From vSphere Client, shut down
1.
the VSM, which should be in
standby mode.
2. From vSphere Client, bring up the
standby VSM after network
connectivity is restored.
If the active and the standby VSM
software versions differ, reinstall the
secondary VSM with the same version
used in the primary.
Reload the standby VSM using the
reload module module-number
command, where module-number is
the module number for the standby
VSM.
Check control VLAN connectivity
between the primary and the secondary
VSMs.
6-3