Virtual Redundancy Groups (VRRP/HSRP) are out of sync across vPC cluster members for Cisco Nexus

Vendor

Cisco

Description

Indeni will identify when two devices are part of a cluster and alert if the redundancy group configuration is different.

Remediation Steps

1.Configure the same FHRP groups, using the same VLAN ID, group ID and virtual IP for the configured FHRP on both peer switches.2.For more information please review the next HSRP & VRRP configuration guides:
http://www.cisco.com/c/en/us/support/docs/switches/nexus-7000-series-switches/113002-nexus-hsrp-00.html
http://www.cisco.com/c/en/us/td/docs/switches/datacenter/sw/4_2/nx-os/unicast/configuration/guide/l3_cli_nxos/l3_vrrp.html

How does this work?

This script logs into the Cisco Nexus switch using SSH and retrieves the HSRP state using the "show hsrp" command. The output includes a complete report of the HSRP state across all configure interfaces.

Why is this important?

Check if the HSRP (Hot Standby Router Protocol) groups are synchronized across a vPC cluster. It is expected that all HSRP groups would be the same across 2 vPC peers. The HSRP groups should use the same virtual IP, VLAN and group number.

Without Indeni how would you find this?

Correlating all the HSRP groups across both vPC members can only be done manually, comparing the HSRP configuration.

View Source Code
single