System-Level High Availability; Network-Level High Availability; Problems With High Availability - Cisco Nexus 1000V Troubleshooting Manual

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 .

System-Level High Availability

The Cisco Nexus 1000V supports redundant VSM virtual machines — a primary and a secondary —
running as an HA pair. Dual VSMs operate in an active/standby capacity in which only one of the VSMs
is active at any given time, while the other acts as a standby backup. The state and configuration remain
constantly synchronized between the two VSMs to provide a statefu1 switchover if the active VSM fails

Network-Level High Availability

The Cisco Nexus 1000V HA at the network level includes port channels and Link Aggregation Control
Protocol (LACP). A port channel bundles physical links into a channel group to create a single logical
link that provides the aggregate bandwidth of up to eight physical links. If a member port within a port
channel fails, the traffic previously carried over the failed link switches to the remaining member ports
within the port channel.
Additionally, LACP lets you configure up to 16 interfaces into a port channel. A maximum of eight
interfaces can be active, and a maximum of eight interfaces can be placed in a standby state.
For additional information about port channels and LACP, see the Cisco Nexus 1000V Layer 2 Switching
Configuration Guide, Release 4.0.
Problems with High Availability
Symptom
The active VSM does not see
the standby VSM.
Cisco Nexus 1000V Troubleshooting Guide, Release 4.2(1)SV2(2.1)
6-2
Possible Causes
Roles are not configured
properly.
Check the role of the two
•
VSMs using the show
system redundancy
status command.
Network connectivity
problems.
Check the control and
•
management VLAN
connectivity between
VSM at the upstream and
virtual switches.
Chapter 6 High Availability
Solution
Confirm that the roles are the
1.
primary and secondary role,
respectively.
If needed, use the system
2.
redundancy role command to
correct the situation.
Save the configuration if roles are
3.
changed.
If network problems exist:
From the vSphere client, shut
1.
down the VSM, which should be in
standby mode.
2. From the vSphere client, bring up
the standby VSM after network
connectivity is restored.
OL-28795-01