Cisco Nexus 1000V, Руководство по устранению неисправностей, Страница: 79 / 280

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