Add Arista prefix limits and tidy prefix limit documentation#122
Merged
Conversation
✅ Deploy Preview for phenomenal-arithmetic-53717b ready!
To edit notification comments on pull requests, go to your Netlify project configuration. |
felbinger
approved these changes
Apr 1, 2026
felbinger
left a comment
felbinger
left a comment
Member
There was a problem hiding this comment.
Text looks good, just some nitpicks.
Didn't check config snippets.
| @@ -10,16 +9,16 @@ tags: | |||
|
|
|||
| This parameter is configured for each eBGP session and is the simplest and easiest security measure you can use. Unfortunately, many stop here. Please do not. | |||
Member
There was a problem hiding this comment.
I know you didn't change this but "simplest and easiest" is kinda redundant. Maybe we can improve this.
| This parameter is configured for each eBGP session and is the simplest and easiest security measure you can use. Unfortunately, many stop here. Please do not. | ||
|
|
||
| Maximum prefix defines a limit for the number of prefixes you accept from an eBGP peer. If the peer sends more, the eBGP session is shut down. Usually, routers keep the session down for some time, then it is automatically re-enabled. If the peer still sends more prefixes than allowed, it is shut down again. | ||
| Maximum prefixes defines a limit for the number of prefixes you accept from an eBGP peer. If the peer sends more, the eBGP session can be shut down or it can remain active but stop accepting new prefixes beyond the configured limit. Usually, routers keep the session down for some time and then it can be automatically re-enabled (in the case the peer has reduced the number of prefix they're advertising). If the peer still sends more prefixes than allowed, the session is automatically shut down again. If the timer to reactivate the BGP session is too low, the session continuously flaps, which is not good for network stability. Therefore some networks prefer to configure their devices not to automatically re-enable the session, but to require manual intervention. |
Member
There was a problem hiding this comment.
(in the case the peer has reduced the number of prefixes they are advertising)
Sounds wrong. How about:
in case the peer has reduced
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
2 participants
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
Set it at least to ten times the normal number of prefixes your peer announces