Cisco Bug: CSCvt79906 - Secondary IP address is used for a BGP session even after the fault- F3488
Aug 27, 2020
- Cisco Application Policy Infrastructure Controller (APIC)
Known Affected Releases
Symptom: After creating a BGP-peer connectivity profile with the loopback option (no presence loopback on L3Out node) in a vPC setup, the BGP session is getting established with a secondary IP address. Conditions: 1. A vPC with a secondary IP address. 2. No loopback on the L3Out nodes. However, creating a BGP-peer connectivity profile using looback as source.
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