Each peering LAN has a BGP route collector. A BGP session with the collector is pre-configured for each peer, and used for BGP statistics gathering. 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. BGP prefix information gathered is made available via the Looking Glass as a diagnostics tool for peers. We heartily encourage all peers to peer with the route-collector at each of the INXes that they are present at.
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 use 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.
Commonly asked questions about the BGP Route Collector
What is the point of the Route Collector
It's a relatively simple way to see which networks, and which prefixes are available at the IXP. We also provide simple diagnostic tools (ping, traceroute) for network debugging purposes.
What value do I get from peering with the Route Collector?
The collector (and its interface via the looking glass) acts as a neutral view into multiple networks. By peering with the collector, you're allowing your peers to perform simple debugging techniques (like ping and traceroute) that can aid them in the work. In the same manner, third party networks that do this, give you the same benefit, for your network.
Will the route collector advertise any prefixes back to me?
No, the route-collector does not advertise any prefixes back to you.
How safe is this? Can the service be abused by a third party?
Since the route-collector does not advertise any prefixes back to you, there is no risk in peering with it. The policy of "non-advertisements" has been hard-coded into the BGP collector setup, so there is little chance of this breaking.
I have a restrictive peering policy ...
That's quite fine; we'd still welcome your peering session, since peering with the route-collector is not an indication of network policy.