Bernd Spiess, peering expert for many years, has developed 10 tips for peering; from optimizing routing data base entries to prefix aggregation.
1. Optimize your routing data base entry
Please make sure that you:
- have your routing data in just one routing database like RIPE, AFRINIC, RADB etc. (unless you are a global player)
- have all used prefixes covered by one correct database entry, matching the ASN which they come from (more-specifics need dedicated entries too)
- have all active (!) own and customer ASNs and AS-SETs listed in your main AS-SET - and remove unused ones
2. Use the route servers (2 sessions ipv4, 2 sessions ipv6)
The route servers help you to get the majority of possible sessions. It will help you to avoid extra work to configure all the newly-arriving members.
3. Verify your prefix amounts and details
Please verify via the route server looking glass whether the route server accepts all of your sent prefixes. If you see a difference, most probably you have not specified the right AS-SET during turn-up, or you have missing or wrong routing database entries.
If you want to know more, then download the guide by filling in the form.