Skip to content

Commit 33c7f5a

Browse files
committed
docs: T9200: distinguish blast radius of the two RA workarounds
remote-as re-add only affects the one neighbor; a bgpd/frr restart clears every BGP session on the router. The note listed them as equivalent options - reframe the restart as a maintenance-window fallback instead. Flagged by CodeRabbit review on PR #2195.
1 parent 35f826d commit 33c7f5a

1 file changed

Lines changed: 4 additions & 2 deletions

File tree

  • docs/configuration/protocols

docs/configuration/protocols/bgp.md

Lines changed: 4 additions & 2 deletions
Original file line numberDiff line numberDiff line change
@@ -720,8 +720,10 @@ This only prevents router advertisements from starting on sessions
720720
established *after* the setting takes effect. It does not stop router
721721
advertisements already active on an established session - neither a soft
722722
nor a hard `clear`/`reset bgp` on the neighbor will stop them. To silence
723-
an already-active session, remove and re-add `remote-as` on that
724-
neighbor, or restart the `bgpd`/`frr` process.
723+
one already-active neighbor, remove and re-add `remote-as` on that
724+
neighbor. Restarting the `bgpd`/`frr` process also clears it, but drops
725+
every BGP session on the router, not just the affected one - reserve
726+
that for a planned maintenance window rather than a routine fix.
725727
:::
726728
```
727729

0 commit comments

Comments
 (0)