What is the 3CIX? | Why non-ISP's should peer | Who uses the 3CIX? | How does it work? | Getting Started | Route registry | Show 3CIX Routes | Change 3CIX Route filters | IPv4 Looking Glass | NZ Internet Exchanges | Home

Getting Started

If you'd like to participate in the 3CIX then you'll need:

  • a router that supports BGP-4 - check with your supplier
  • a block of IP addresses to advertise - we can't supply these addresses. You'll either have them already or need to get a block of at least 6 usable addresses from your ISP. Tell them you need at least a /29 prefix
  • an Autonomous System (AS) number - you may already have one assigned by APNIC. We'll assign one for you if you haven't got one
  • to complete the 3CIX Application Form

Once you've completed the form we'll send you some details on your 3CIX IP address and a sample config for a Unix based router using Zebra or Quagga. If you are a Cisco router this config will work with minor changess. If you're using another type of router you'll need to do a little more work.

Checking the running system

You can check your details in the route servers via a web based interface called a looking glass. The 3CIX Looking Glass allows you to check whether your BGP peering sessions with our route servers are running correctly.

If you are a 3CIX peer you should check that you are peering with both route servers and announcing the same number of prefixes on each one - use the show ip bgp summary option and look for the 3CIX IP address you were assigned in the output.

  • If the right hand column shows a number greater than zero and it matches your expectations - then things are probably working well. You can check the actual routes being announced on your behalf on the Looking Glass if you select the show ip bgp option on the web page, type neighbor 218.100.26.254 routes (note the American spelling) in the Argument box and Execute. The Next Hop on the output should point to your router!
  • If your session is marked as Active in the right hand column then the setup on your router almost certainly needs some attention - Active means that our route server is waiting for a connection from your router and for some reason it's not happening!
  • If the right hand column shows 0 (zero) then your BGP session is up but the route server is not advertising any routes for you. The likely causes of this are:
    a) your BGP session is not advertising any routes to the route server
    b) your BGP session is advertising routes to the route server but the announcements are being filtered out.

If things aren't working as you'd like you can debug this using the Looking Glass. Let's use the router on 218.100.26.254 to check details of some routing announcements to the route servers. Select the show ip bgp option on the web page, type neighbor 218.100.26.254 received-routes (note the American spelling) in the Argument box and Execute. This will show you something like this: 

Executing command = show

ip bgp neighbor 202.7.0.1 received-routes

BGP table version is 0, local router ID is 202.7.0.2
Status codes: s suppressed, d damped, h history, * valid, > best, i - internal
Origin codes: i - IGP, e - EGP, ? - incomplete

   Network          Next Hop            Metric LocPrf Weight Path
*> 198.48.0.0/22    202.7.0.1                              0 23754 i
*> 202.37.19.0      202.7.0.1                              0 23754 i
*> 203.97.231.224/28
                    202.7.0.1                0             0 23754 ?
*> 203.118.144.0    202.7.0.1                              0 23754 i
*> 210.48.103.0/28  202.7.0.1                0             0 23754 ?
*> 210.48.103.136/29
                    202.7.0.1                0             0 23754 ?
*> 210.48.103.144/28
                    202.7.0.1                0             0 23754 ?

Total number of prefixes 7
pele-bgp

If you do this using the 3CIX IP address we assigned to you then this will show a list of prefixes you are actually sending to the route servers. If the list is empty then your BGP process is not announcing prefixes to us. If this list matches what you're sending then it looks the filter lists don't match your announcements and you'll need to contact us to get that fixed.

If things are working correctly then the routes and received-routes outputs should match.