Cisco Bug: CSCvt13978 - vPC created prior to 2.2(2e) may result new VIP after ID recovery
Oct 03, 2020
- Cisco Application Policy Infrastructure Controller (APIC)
Known Affected Releases
Symptom: VPC protection created in prior to the 2.2(2e) release may not to recover the original virtual IP address after fabric ID recovery. Instead, some of vPC groups get a new vIP allocated, which does not get pushed to the leaf switch. The impact to the dataplane does not come until the leaf switch had a clean reboot/upgrade, because the rebooted leaf switch gets a new virtual IP that is not matched with a vPC peer. As a result, both sides bring down the virtual port channels, then the hosts behind the vPC become unreachable. Conditions: The following conditions must be met: 1) The fabric was originally brought up prior to the 2.2(2e) release and vPCs were created and deployed from that point on. 2) When the fabric is upgraded to the 2.2(2e) release or later, fabric ID recovery is initiated due to an unrecoverable reason in the database.
Bug details contain sensitive information and therefore require a Cisco.com account to be viewed.
Bug Details Include
- Full Description (including symptoms, conditions and workarounds)
- Known Fixed Releases
- Related Community Discussions
- Number of Related Support Cases