There was a problem loading the comments.

Checking that the route servers are accepting your prefixes

Support Portal  »  Knowledgebase  »  Viewing Article

  Print

Please make sure you have read our earlier discussion on how filters are generated.  See:   https://support.inx.net.za/en/kb/article/what-is-the-importance-of-an-as-set

 

This article shows how to use the INX portal to see if any of the prefixes that you are advertising to the BGP route servers are being filtered, and, consequently not being advertised to other peers.  INX filter according to industry best practices, and, there is a very good chance, that if we are filtering your prefixes, then, other, responsible network operators will also be doing the same.  

 

Remember that INX performs strict IRR filtering;  this means that there *must* to be an IRR route(6) object in the IRRDB, matching the exact length of the prefix advertised.

 

Log into the INX portal https://portal.inx.net.za/

If you need a reminder on how to do this see this article https://support.inx.net.za/en/kb/article/how-do-i-login-to-the-inx-portal

 

Click the "Filtered Prefixes" tab

c27e83f47121c962eed038159a74e58d731da48c94a018c5793de20d4f1165eb3c7df37bff8d5841?t=cb4b1843fb3fae95ddd82d51a28e4aea

 

 

 

You should see the message below, indicating that the INX portal is retrieving your records from the appropriate route servers.  

Wait a minute, and then click to refresh the page. 

 

67ce08e5141cf1dba16fd8ffb104144e45a7943e692c4ccb8c467a9d3839b22d42af61f01b67f8dd?t=01a94dd63bd31d72211d941fdf9542ec

 

 

What you are hoping for is to be greeted with a "Good news!" message.  This indicates that we are not filtering and of your advertised prefixes.  

937f7142ff2b161e75fd8dea66c766d46c43c7863192b89623f081e29f30517dab52003ae51e00d2?t=50ba04db451a4686b4716209db88a766

 

But the response might come back with "Bad news" and a list of prefixes and reasons for them being filtered

c67725df0c4b366af2cffc57f296056ead095216708876094794583b6d057654988a47c727db1253?t=76ab9e287a0360558311f3f3744a191a

 

There are a number of reasons why a prefix may be filtered, below is a list of the most common reasons for filtered prefixes

IRRDB PREFIX FILTERED - Typically an IRR route/6 object cannot be found in the IRR Database

NEXT HOP NOT PEER IP - The advertised prefix has a next hop that is not the peer's IP address

PREFIX NOT IN ORIGIN AS - There may be an IRR route/6 object for the prefix but the ASN is not a member the peer's AS-SET

RPKI INVALID - The prefix has an invalid RPKI ROA
 
INX typically imports the AS-SET of a Peer from their PeeringDB profile where the field is "IRR as-set/route-set "
 

To dig deeper to see what ASNs and Prefixes have been included in the prefix list build check the following,

 

On the top right of the  filtered prefix page there is a drop down "View / Update IRRDB Entries"

19fee1da08f74cdeaa96c12ca018316866279adfd8d95f69a7ac9304a4a1f40752297d7c54c60ab7?t=92e255eb2577082c788cebcb218bc93c

 

Select IPv4/IPv6 IRRDB ASNs for a list of ASNs in your AS-SET or IPv4/IPv6 IRRDB Prefixes for the full list of prefixes built from the AS-SET

 

If you do not see the expected output or you feel the filter is out of date do not hesitate to get in touch with us by sending an email to ops@inx.net.za

We can help debug what the issue may be.

 


Share via
Did you find this article useful?  

Related Articles

© INX-ZA