OPERATIONAL DEFECT DATABASE
...
...
- For Nexus we see broken VLAN 2251 with static HSRP MAC configured, after reload HSRP gets stuck in "Initial" state, but should move to next states as seen for working VLAN 2250. N3K-C3172PQ-2# show run int vlan 2250-2251 !Command: show running-config interface Vlan2250-2251 !Running configuration last done at: Sat Aug 1 10:23:49 2020 !Time: Sat Aug 1 10:47:27 2020 version 7.0(3)I7(6) Bios:version 5.3.1 interface Vlan2250 no shutdown ip address 10.1.1.3/24 hsrp version 2 hsrp 2250 preempt priority 120 ip 10.1.1.1 interface Vlan2251 no shutdown ip address 10.231.240.2/29 hsrp version 2 hsrp 2251 mac-address 0000.0C9F.0014 preempt priority 120 ip 10.231.240.1 - Reload both switches (Broken VLAN 2251 doesn't come up, Working VLAN 2250 does come up): - Expectation is for both VLANs to come up: N3K-C3172PQ-1# show hsrp brief *:IPv6 group #:group belongs to a bundle P indicates configured to preempt. | Interface Grp Prio P State Active addr Standby addr Group addr Vlan2250 2250 100 Listen unknown 10.1.1.3 10.1.1.1 (conf) <--- This is expected. Vlan2251 2251 100 Initial unknown unknown 10.231.240.1 (conf) <--- This is unexpected. N3K-C3172PQ-2# show hsrp brief *:IPv6 group #:group belongs to a bundle P indicates configured to preempt. | Interface Grp Prio P State Active addr Standby addr Group addr Vlan2250 2250 120 P Active local 10.1.1.2 10.1.1.1 (conf) <--- This is expected. Vlan2251 2251 120 P Initial unknown unknown 10.231.240.1 (conf) <--- This is unexpected.
-HSRP configuration may work initially but fails after a reload and will disruption as HSRP VIP never comes up. -The defect is present in NXOS and not on the platform so the issue is present on all switches which run NXOS.
-Shutdown/no shutdown SVI VLAN 2251 (or impacted HSRP VLAN) will move the HSRP state out of "Initial" and continue to next state eventually transitioning to Standby or Active as expected. -Temporary fix would be to use any MAC not in this range 0000.0C9F.xxxx. However, HSRP MAC range is 0000.0C9F.Fxxx which we anyway cannot configure statically for a group.
-In future releases, we will be able to statically configure MAC in this range 0000.0C9F.xxxx but it would still won't allow you to use reserve range 0000.0C9F.Fxxx as it is used by protocols internally.
Click on a version to see all relevant bugs
Cisco Integration
Learn more about where this data comes from
Bug Scrub Advisor
Streamline upgrades with automated vendor bug scrubs
BugZero Enterprise
Wish you caught this bug sooner? Get proactive today.
