AS62981 is AMS-IX Chicago's administrative LAN. Although peering is in no regard mandatory, we highly recommend setting up redundant peering sessions for the following reasons:
AMS-IX NOC can handle troubleshooting requests more efficiently as long as it has a reference point. Having redundant BGP sessions established to routers situated in separate colocations that we directly administer can be a significant aid.
Peering with AS62981 means that traffic can be exchanged directly between our administrative LAN and you, eliminating the need to be routed via third parties. This of course is entirely optional, should you not want to attract any additional traffic. Advertising no prefixes at all is acceptable.
|Please Note the Following:|
This section describes the necessary steps to set up a peering with the AMS-IX Chicago ASN (AS62981). Also shown is a sample Cisco router config that can be used to set up this peering with the AS62981 routers.
In case of questions, please contact firstname.lastname@example.org.
In the "router bgp xxx" configuration section of your router that is attached to the AMS-IX Chicago shared medium you should add the following peer: the AS62981 router at AMS-IX.
neighbor 184.108.40.206 remote-as 62981
neighbor 220.127.116.11 version 4
neighbor 18.104.22.168 filter-list 31 in
neighbor 22.214.171.124 filter-list 32 out
neighbor 126.96.36.199 next-hop-self
Adjust the numbers of the AS path filter-lists according to your own preferences.
You only need to do this if you use peer-groups based on peer location. Where possible, AMS-IX peering routers are located at different co-locations.
neighbor 188.8.131.52 peer-group IPV4-PEERS-A
Make sure the AS path filter-lists are set up such that you only permit routes with the AMS-IX Autonomous System Number from AS62981 and that you announce any routes you care to share to the AMS-IX router.
ip as-path access-list 31 permit ^(62981_)+$
ip as-path access-list 32 permit ^my-AS$
ip as-path access-list 32 permit my-Customer-1$
ip as-path access-list 32 permit my-Customer-2$
In case you adjusted the numbers of the AS path filter-lists in Step 1, you should use the same numbers in this step.
The above is only an example. In general, you want to configure outgoing access list to only announce your (and your customer's) routes. If you plan on sending us a full routing table, please let us know in advance. We will use best routes for transit. Also, please do not announce AS62981 advertisements to non-customers without our explicit request.
When you configured your end of the peering, please notify the operator of the AMS-IX by sending e-mail to <email@example.com> stating you set up the peering with the AS62981 router and you want the AS62981 router to start the peering with you. Please include the following details in your e-mail message:
- Provider name
- IP address of router at AMS-IX Chicago
- ASN that the router at AMS-IX Chicago resides in
The peering from the AS62981 router will be set up as soon as possible. You will be notified when the peering is up.
Your peering with AS62981 should be registered in the Internet Routing Registry at the RIPE NCC, just like all your other peerings. You can use the template below. Please adjust the cost in the “import” clause according to your own needs and put the correct AS set(s) in the “export” clause
import: from AS62981
export: to AS62981
If you want to implement IPv6 peerings on the AMS-IX: