CNX Documentation

Getting started at CNX

CNX supplies the port handoff and peering assignments during onboarding. Keep that connection record with the router configuration; the values are specific to your port and are not published in these guides.

1. Collect the connection details

Record:

  • physical port and facility;
  • interface speed and expected negotiation mode;
  • whether the handoff is untagged or uses an assigned VLAN tag (VLAN 500 is the default peering VLAN);
  • interface MTU;
  • your IPv4 and IPv6 peering addresses;
  • your ASN;
  • the CNX route-server addresses; and
  • any agreed GTSM, BFD, or session-authentication settings.

Do not copy another member's address or VLAN configuration. CNX assigns these values per connection. Use VLAN 500 for a tagged peering handoff unless the CNX connection record specifies another value.

2. Prepare public routing data

Before announcing routes, complete Publishing routing data. At minimum:

  • publish IRR route and route6 objects;
  • publish ROAs for every originated prefix;
  • maintain a hierarchical AS-SET if you announce downstream networks; and
  • set the AS-SET and realistic prefix counts in PeeringDB.

3. Decide your local routing policy

Choose the prefixes you will export and how CNX routes should compare with transit and bilateral paths. Define explicit export prefix lists. Do not export the CNX peering LAN, a default route, private address space, or a route that you are not authorized to announce.

Plan for asymmetric traffic. Stateful firewalls and internal routing must permit a flow to enter through a different edge from the one used for its outbound packets.

4. Configure and verify

Continue in this order:

  1. Configure the IX port.
  2. Configure route-server BGP.
  3. Verify peering.
  4. Optionally enable Add-Path and ECMP.
  5. Apply traffic-steering communities where needed.