Public
Child pages
  • BGP Route Servers

Versions Compared

Old Version 17

changes.mady.by.user Graham Beneke

Saved on

compared with

New Version 18

changes.mady.by.user Graham Beneke

Saved on

Key

  • This line was added.
  • This line was removed.
  • Formatting was changed.

There are two BGP route servers on each peering LAN. It is recommended to always peer with both servers at a location since either server may be taken down for maintenance from time to time. Connections to both servers ensure that there is no disruption.

Note
titleBi-lateral peering is considered best practice !

It is strongly recommended that, in addition to any sessions you plan to establish with the BGP Route Servers, you still maintain direct bi-lateral peering sessions with peers that you feel are important to your network! BGP Route Servers should be used to pickup smaller peers only, and not as a replacement for your discrete peering policy!

INXASNTypeIPv4IPv6
JINX37700-196.223.14.12001:43f8:1f0::1
BIRD196.223.14.22001:43f8:1f0::2
CINX37701BIRD196.223.22.12001:43f8:1f1::1
BIRD196.223.22.22001:43f8:1f1::2
DINX37699BIRD196.223.30.12001:43f8:1f2::1
BIRD196.223.30.22001:43f8:1f2::2

BGP Communities for policy control

A simple set of BGP communities are made available for rudimentary policy control.  These will be expanded on, as the BGP Route Server service is improved. 

Tip
titleBGP next-as
Ensure that if you do plan on peering with the BGP Route Servers that you implement "no bgp enforce-next-as" (or similar) for your platform.
CommunityActionExplanation
37700:65281add no-exportadds the well known no-export community to all routes sent to peers
37700:65282add no-advertiseadds the well known no-advertise community to all routes sent to peers
0:peer-asdeny to peer-asblock announcement of route to peer-as
0:37700block allblock announcement of route to all peers
37700:peer-asallow to peer-asannounce prefix to specific peer-as (in conjunction with block all)
37700:37700allow allannounce prefix to all peers (implicit default)
Info
titleRemember to use the correct ASN
Note: The above communities apply to peers using the JINX route servers. The appropriate ASN should be substituted when using the CINX and DINX route servers.