Details
-
Bug
-
Status: Resolved
-
Medium
-
Resolution: Done
-
None
-
None
Description
During the session establishment phase, if a peer doesn't advertise ipv4-unicast, controller automatically adds ipv4-unicast as supported family for the session to support classic BGP sessions. Currently, we are adding Ipv4 family in the BGPPeer but not updating AdjRibInWriter which causes the BGP session to not recover from session flap.
Patch fixes this issue by adding ipv4 support before updating AdjRibInWriter.
Attachments
| # | Subject | Branch | Project | Status | CR | V |
|---|---|---|---|---|---|---|
| 90847,1 | Non ipv4 advertising peer causes BGP session flaps | master | bgpcep | Status: ABANDONED | 0 | 0 |
| 90849,6 | Non ipv4 advertising peer causes BGP session flaps | master | bgpcep | Status: MERGED | +2 | +1 |
| 90924,14 | Additional Tests related to the address families | master | integration/test | Status: MERGED | +2 | +1 |
| 91733,1 | Non ipv4 advertising peer causes BGP session flaps | stable/sodium | bgpcep | Status: MERGED | +2 | +1 |
| 91734,1 | Non ipv4 advertising peer causes BGP session flaps | stable/magnesium | bgpcep | Status: MERGED | +2 | +1 |
