Versions Compared
Key
- This line was added.
- This line was removed.
- Formatting was changed.
Each peering LAN has a BGP route collector. A A BGP session with the collector is setup to each peer, and used for statistics gathering and is also made available via the Looking Glass as a diagnostics tool for peers. We strongly heartily encourage all peers to peer with the route-collectorscollector at each of the INXes that they are present at.
INX
| Location | ASN | Hostname | IPv4 | IPv6 |
|---|---|---|---|---|
| JINX | 37474 | routecollector.jinx.net.za | 196.223.14.3 | 2001:43f8:1f0::3 |
| CINX | 37663 | routecollector.cinx.net.za | 196.223.22.3 | 2001:43f8:1f1::3 |
| DINX | 37668 | routecollector.dinx.net.za | 196.223.30.3 | 2001:43f8:1f2::3 |
We distinctly use separately distinctly separately ASNs for the route-collector and the route-server, as we expect that for their own purposes, not all peers will want to peer with the BGP route servers. While we would prefer to use a completely separate ASN for this, AfriNIC would not allocate us a third ASN explicitly for this purpose, so we are re-using the AS number that we use for each of the INX management networks. Note however, that the router collectors do not advertise any prefixes back to the networks that they peer to.
Peering sessions to route-collectors are done in advance of port turn-up, and set to passive, so we will automatically respond to, and activate peering sessions from active peers.