High Availability Troubleshooting Commands - Cisco Nexus 1000V Troubleshooting Manual

Chapter 6 High Availability
Symptom
Both VSMs are in active
mode.

High Availability Troubleshooting Commands

This section lists commands that can be used troubleshoot problems related to high availability.
Command
attach module
reload module
show cores
show processes [pid pid]
show system internal active-active
OL-31593-01
Possible Causes
Network connectivity
problems.
• Check for control and
management VLAN
connectivity between the
VSM at the upstream and
virtual switches.
When the VSM cannot
•
communicate through any
of these two interfaces,
they will both try to
become active.
Different domain IDs in the
two VSMs
Check the domain value by
using show system internal
redundancy info command.
Description
See Example 6-9attach module Command,
page 6-10
See Example 6-8reload module Command,
page 6-10
Use to list process logs and cores.
See Example 6-1show cores Command, page 6-6
See Example 6-2show processes log [pid pid]
Command, page 6-6
See Example 6-7show system internal
active-active remote accounting logs Command,
page 6-10
Cisco Nexus 1000V Troubleshooting Guide, Release 5.2(1)SV3(1.1)
High Availability Troubleshooting Commands
Solution
If network problems exist, do the
following:
1. From vSphere Client, shut down
the VSM, which should be in
standby mode.
From vSphere Client, bring up the
2.
standby VSM after network
connectivity is restored.
If needed, update the domain ID and
save it to the startup configuration.
Upgrading the domain ID in a dual
•
VSM system must be done as
follows:
Isolate the VSM with the
–
incorrect domain ID so that it
cannot communicate with the
other VSM.
Change the domain ID in the
–
isolated VSM, save the
configuration, and power off
the VSM.
Reconnect the isolated VSM
–
and power it on.
6-5