There is currently a single route server each at respective INX. It is planned to make these redundant, and extend their services.
Bi-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!
BGP next hop
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.
| INX | ASN | Type | IPv4 | IPv6 |
|---|---|---|---|---|
| JINX | 37700 | - | 196.223.14.1 | 2001:43f8:1f0::1 |
| BIRD | 196.223.14.2 | 2001:43f8:1f0::2 | ||
| CINX | 37701 | - | 196.223.22.1 | 2001:43f8:1f1::1 |
| BIRD | 196.223.22.2 | 2001:43f8:1f1::2 | ||
| DINX | 37699 | - | 196.223.30.1 | 2001:43f8:1f2::1 |
| - | 196.223.30.2 | 2001: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.
| Community | Action | Explanation |
|---|---|---|
| 37700:65281 | add no-export | adds the well known no-export community to all routes sent to peers |
| 37700:65282 | add no-advertise | adds the well known no-advertise community to all routes sent to peers |
| 0:peer-as | deny to peer-as | block announcement of route to peer-as |
| 0:37700 | block all | block announcement of route to all peers |
| 37700:peer-as | allow to peer-as | announce prefix to specific peer-as (in conjunction with block all) |
| 37700:37700 | allow all | announce prefix to all peers (implicit default) |
Remember to check your ASN