a1365b44c3
Why I did it BGP service has always been starting after interface-config. However, recently we discovered an issue where some BGP sessions are unable to establish due to BGP daemon not able to read the interface IP. This issue was clearly observed after upgrading to FRR 8.2.2. See more details in #12380. How I did it Delaying starting BGP seems to be a workaround for this issue. However, caution is that this delay might impact warm reboot timing and other timing sequences. This workaround is reducing the probability of hitting the issue by close to 100X. However, this workaround is not bulletproof as test shows. It is still preferrable to have a proper FRR fix and revert this change in the future. How to verify it Continuously issuing config reload and check BGP session status afterwards. Signed-off-by: Ying Xie <ying.xie@microsoft.com> |
||
|---|---|---|
| .. | ||
| bgp.service.j2 | ||
| database.service.j2 | ||
| gbsyncd.service.j2 | ||
| lldp.service.j2 | ||
| lldp.timer.j2 | ||
| macsec.service.j2 | ||
| swss.service.j2 | ||
| syncd.service.j2 | ||
| teamd.service.j2 | ||