Child pages
  • BGP Route Servers
Skip to end of metadata
Go to start of metadata

You are viewing an old version of this page. View the current version.

Compare with Current View Page History

« Previous Version 8 Next »

There is currently one route server each at JINX and CINX respectively.  

Bi-lateral peering

It is strongly recommended that, in addition to any sessions you plan to establish with the BGP Route Servers, you still maintain discrete bi-lateral peering sessions with peers that you feel are important to your network! 

INXASNTypeIPv4IPv6
JINX37700-196.223.14.12001:43f8:1f0::1
BIRD196.223.14.22001:43f8:1f0::2
CINX37701-196.223.22.12001:43f8:1f1::1
BIRD196.223.22.22001:43f8:1f1::2
DINX37699-196.223.30.12001:43f8:1f2::1
-196.223.30.22001:43f8:1f2::2

 

BGP Communities for policy control

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)

Note: Above communities apply to peers using the JINX route servers. The ASN 37701 should be substituted when using the CINX route servers.

  • No labels