peering-toolbox:hardware
Differences
This shows you the differences between two versions of the page.
| Both sides previous revisionPrevious revision | Last revisionBoth sides next revision | ||
| peering-toolbox:hardware [2023/03/27 11:38] – [BGP] philip | peering-toolbox:hardware [2023/03/27 11:43] – [BGP] philip | ||
|---|---|---|---|
| Line 173: | Line 173: | ||
| ==== BGP ==== | ==== BGP ==== | ||
| + | |||
| + | (UPDATED) | ||
| The discussion about BGP support for the router used in the [[hardware# | The discussion about BGP support for the router used in the [[hardware# | ||
| The BGP configuration used on a public peering connection is discussed in the [[single_upstream_ixp|Single Upstream and IXP]] section of the Toolbox. | The BGP configuration used on a public peering connection is discussed in the [[single_upstream_ixp|Single Upstream and IXP]] section of the Toolbox. | ||
| + | |||
| + | The control plane needs of the router (the processor to handle BGP and other routing protocols) in this case can be quite significant and care is needed when selecting suitable hardware. | ||
| + | |||
| + | Small IXPs will have only a few peers so there it a likelihood that only a few thousand routes will be received by the new member. | ||
| + | |||
| + | Larger IXPs will likely have over one hundred members, with the largest IXPs today approaching one thousand members. This has significant control plane needs on the peering router, and it is important that a powerful control plane CPU is chosen, especially one that is proven to handle several hundred peers and tens of thousands of routes with ease. In this case it can be helpful to consult with existing IXP members seeking suggestions or recommendations. | ||
| ==== Packet Filtering ==== | ==== Packet Filtering ==== | ||
peering-toolbox/hardware.txt · Last modified: 2023/03/27 11:57 by philip