Versions Compared
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 BGP Route Servers at a location. Connections to both servers ensure that there is no disruption to routing should it be necessary to performance maintenance.
| Note | ||
|---|---|---|
| ||
While the Route Server service is made available as a convenience, 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! |
| INX | ASN | Hostname | Type | IPv4 | IPv6 |
|---|---|---|---|---|---|
| JINX | 37700 | routeserver1.jinx.net.za | BIRD | 196.223.14.1 | 2001:43f8:1f0::1 |
| routeserver2.jinx.net.za | BIRD | 196.223.14.2 | 2001:43f8:1f0::2 | ||
| CINX | 37701 | routeserver1.cinx.net.za | BIRD | 196.223.22.1 | 2001:43f8:1f1::1 |
| routeserver2.cinx.net.za | BIRD | 196.223.22.2 | 2001:43f8:1f1::2 | ||
| DINX | 37699 | routeserver1.dinx.net.za | BIRD | 196.223.30.1 | 2001:43f8:1f2::1 |
| routeserver2.dinx.net.za | BIRD | 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.
| Tip | ||
|---|---|---|
| ||
| 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. |
| 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) |
| Info | ||
|---|---|---|
| ||
| Note: The above communities example applies to peers using the JINX route servers. The appropriate ASN for each INX, should be substituted when using the BGP route servers, at other INXes. |