Cisco Nexus 1000V Troubleshooting Manual page 80

Switch for vmware vsphere. release 5.2(1)sv3(1.1)
Hide thumbs Also See for Nexus 1000V:
Table of Contents

Advertisement

Problems with High Availability
Symptom
The standby VSM reboots
periodically.
Active-Active detected and
resolved
VSM Role Collision
Cisco Nexus 1000V Troubleshooting Guide, Release 5.2(1)SV3(1.1)
6-4
Possible Causes
The VSM has connectivity
only through the management
interface.
Check the output of the
show system internal
redundancy info
command and verify that
the degraded_mode flag
is set to true.
The VSMs have different
versions.
Enter the debug system
internal sysmgr all command
and look for the active_verctrl
entry that indicates a version
mismatch, as the following
output shows:
2009 May
5
08:34:15.721920 sysmgr:
active_verctrl: Stdby
running diff version-
force download the standby
.
sup
When control and
management connectivity
between the active and the
standby goes down for 6
seconds, the standby VSM
transitions to the active state.
Upon restoration of control
and management connectivity,
both VSMs detect an
active-active condition.
If another VSM is
configured/provisioned with
the same role (primary or
secondary) in the system, the
new VSM collides with the
existing VSM.
The show system
redundancy info command
displays the MAC addresses
of the VSM(s) that collide
with the working VSM.
Chapter 6
High Availability
Solution
Check the control VLAN connectivity
between the primary and the secondary
VSMs.
Isolate the standby VSM and boot it.
Use the show version command to
check the software version in both
VSMs.
Install the image matching the active
VSM on the standby.
Once the system detects
1.
active-active VSMs, one VSM is
automatically reloaded based on
various parameters such as VEMs
attached, vCenter connectivity,
last configuration time, and last
active time.
To see any configuration changes
2.
that are performed on the rebooted
VSM during the active-active
condition, enter the show system
internal active-active remote
accounting logs CLI command on
the active VSM.
If the problems exist, do the following:
Enter the show system
1.
redundancy status command on
the VSM console.
Identify the VSM(s) that owns the
2.
MAC addresses that are displayed
in the output of the show system
redundancy status command.
Move the identified VSM(s) out of
3.
the system to stop role collision.
OL-31593-01

Advertisement

Table of Contents
loading

Table of Contents