Skip to content

Add Arista prefix limits and tidy prefix limit documentation#122

Open
jwbensley wants to merge 2 commits intodenog:mainfrom
jwbensley:arista-prefix-limit
Open

Add Arista prefix limits and tidy prefix limit documentation#122
jwbensley wants to merge 2 commits intodenog:mainfrom
jwbensley:arista-prefix-limit

Conversation

@jwbensley
Copy link
Copy Markdown
Contributor

  • Add config examples for maximum prefix limits or Arista
  • Tidy up the description of maximum prefix limits:
    • Remove the potentially dangerous recommendation Set it at least to ten times the normal number of prefixes your peer announces
    • Mention that leaving the session shutdown is also an option
    • Mention that leaving the session up is also an option

@netlify
Copy link
Copy Markdown

netlify bot commented Apr 1, 2026

Deploy Preview for phenomenal-arithmetic-53717b ready!

Name Link
🔨 Latest commit 108fa47
🔍 Latest deploy log https://app.netlify.com/projects/phenomenal-arithmetic-53717b/deploys/69ce2b79ad225c0008df0115
😎 Deploy Preview https://deploy-preview-122--phenomenal-arithmetic-53717b.netlify.app
📱 Preview on mobile
Toggle QR Code...

QR Code

Use your smartphone camera to open QR code link.

To edit notification comments on pull requests, go to your Netlify project configuration.

Copy link
Copy Markdown
Member

@felbinger felbinger left a comment

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

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.
Copy link
Copy Markdown
Member

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

I know you didn't change this but "simplest and easiest" is kinda redundant. Maybe we can improve this.

Copy link
Copy Markdown
Contributor Author

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Should be fixed now @felbinger

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.
Copy link
Copy Markdown
Member

@felbinger felbinger Apr 1, 2026

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

(in the case the peer has reduced the number of prefixes they are advertising)

Sounds wrong. How about:

in case the peer has reduced

Copy link
Copy Markdown
Contributor Author

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Should be fixed now @felbinger

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Projects

None yet

Development

Successfully merging this pull request may close these issues.

2 participants