Philip Smith's Internet Development Site

User Tools

Site Tools

Trace:
peering-toolbox:hardware

Differences

This shows you the differences between two versions of the page.

Link to this comparison view

Both sides previous revisionPrevious revision
Next revision		Previous revision
peering-toolbox:hardware [2023/03/27 11:38] – [BGP] philippeering-toolbox:hardware [2023/03/27 11:57] (current) – [BGP] philip
Line 122: Line 122:
  
 ==== BGP ==== ==== BGP ====
 +
 +(UPDATED)
  
 BGP will be required for any peering connection, in which case the peering router has to fully support BGP. BGP will be required for any peering connection, in which case the peering router has to fully support BGP.
Line 128: Line 130:
  
 The BGP configuration used on a private peering connection is discussed in the [[single_upstream_private_peer|Single Upstream and Private Peer]] section of the Toolbox. The BGP configuration used on a private peering connection is discussed in the [[single_upstream_private_peer|Single Upstream and Private Peer]] section of the Toolbox.
 +
 +The control plane needs of the router (the processor to handle BGP and other routing protocols) are not significant where there are just a few BGP peers and only a few routes are being handled as in this case.
  
 ==== Packet Filtering ==== ==== Packet Filtering ====
Line 169: Line 173:
  
 ==== BGP ==== ==== BGP ====
 +
 +(UPDATED)
  
 The discussion about BGP support for the router used in the [[hardware#bgp1|Private Peering Link]] fully applies here too. The discussion about BGP support for the router used in the [[hardware#bgp1|Private Peering Link]] fully applies here too.
  
 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. Most standard router hardware has sufficient control plane capability to handle this.
 +
 +Larger IXPs will likely have dozens of members, with the largest IXPs today approaching one thousand members. This has significant control plane demands on the peering router, and it is important that one with 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. Note the usual caveat between vendor marketing claims and real world experience of network operators.
 +
  
 ==== Packet Filtering ==== ==== Packet Filtering ====
peering-toolbox/hardware.1679877507.txt.gz · Last modified: 2023/03/27 11:38 by philip