EasyManua.ls Logo

Cisco Nexus 1000V - Page 80

Cisco Nexus 1000V
280 pages
To Next Page IconTo Next Page
To Next Page IconTo Next Page
To Previous Page IconTo Previous Page
To Previous Page IconTo Previous Page
Loading...
6-4
Cisco Nexus 1000V Troubleshooting Guide, Release 5.2(1)SV3(1.1)
OL-31593-01
Chapter 6 High Availability
Problems with High Availability
The standby VSM reboots
periodically.
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.
Check the control VLAN connectivity
between the primary and the secondary
VSMs.
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
.
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.
Active-Active detected and
resolved
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.
1. Once the system detects
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.
2. To see any configuration changes
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.
VSM Role Collision 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.
If the problems exist, do the following:
1. Enter the show system
redundancy status command on
the VSM console.
2. Identify the VSM(s) that owns the
MAC addresses that are displayed
in the output of the show system
redundancy status command.
3. Move the identified VSM(s) out of
the system to stop role collision.
Symptom Possible Causes Solution

Table of Contents

Other manuals for Cisco Nexus 1000V

Related product manuals