OPERATIONAL DEFECT DATABASE
...
...
Repro scenario: S1 and S2 in VPC domain configured with below: vpc domain 101 delay restore 240 auto-recovery reload-delay 60 delay restore interface-vlan 120 1 - S1 and S2 are both on and vPC is formed correctly with peer-link and peer-keepalive on, S1 is vPC Primary. 2 - Both S1 and S2 power off simultaneously. 3 - Now only one switch is able to power on. For example, S2 is the only switch which powers on. 4 - Once back online, S2 waits for the vPC auto-recovery timeout (60 sec). 5 - Once S2 auto-recovery timer expires, S2 will wait delay restore int vlan timer (120 sec) 6 - Once S2 delay restore int vlan timer expires, S2 will wait delay restore timer (240 sec) In this scenario, the vPC peer-link never comes up as S1 remained down so there is no need for 'delay restore' or 'delay restore interface-vlan' timer to be used as they only extend vpc recover time. This is an enhancement request to expedite vpc restoration by suppressing the delay restore timers in scenarios where vPC peer-link remains down, so that vpc legs are brought up right after auto-recovery timer expires.
n/a
n/a
n/a
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.
