Cisco Nexus 1000V Troubleshooting Manual page 76
Hide thumbs
Also See for Nexus 1000V:
- Troubleshooting manual (280 pages) ,
- Configuration manual (96 pages) ,
- Deployment manual (49 pages)
Table of Contents
Advertisement
Problems with High Availability
S e n d d o c u m e n t c o m m e n t s t o n e x u s 1 k - d o c f e e d b a c k @ c i s c o . c o m .
Symptom
Active-Active detected and
resolved
VSM Role Collision
Cisco Nexus 1000V Troubleshooting Guide, Release 4.2(1)SV2(2.1)
6-4
Possible Causes
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
1.
Once the system detects
active-active VSMs, one of the
VSM is automatically reloaded
based on various parameters like
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, execute show system
internal active-active remote
accounting logs CLI command on
the active VSM.
If the problems exist:
Execute show system
1.
redundancy status command on
the VSM console.
2.
Identify the VSM(s) that owns the
MAC addresses that are displayed
in the output of show system
redundancy status command.
Move the identified VSM(s) out of
3.
the system to stop role collision.
OL-28795-01
Advertisement
Table of Contents
Troubleshooting
