[ixpmanager] IRR updating issue with BGPQ3

[Paul Emmons]

Hello Team,

Can we remove the -S flag that the IRR update is invoking??

I had some time to track down some issues regarding IRR issues with 
BGPQ3 querying RADB that seems to affect mostly North American IXPs.  I 
ran this off a test box.  We have a member AS14237 - IXPManager sees the 
following prefixes in the IRR listing:

root at ixp:/home/pemmons# /usr/bin/bgpq3 -S 'RADB' -h 'whois.radb.net' -l 
pl -j -m 24 'AS14237'
{ "pl": [
     { "prefix": "38.126.240.0\/22", "exact": true },
     { "prefix": "38.126.248.0\/21", "exact": true },
     { "prefix": "68.64.234.0\/24", "exact": true },
     { "prefix": "192.198.233.0\/24", "exact": true },
     { "prefix": "204.48.136.0\/21", "exact": true },
     { "prefix": "206.72.88.0\/22", "exact": true }
] }

They are short a bunch of prefixes.

root at ixp:/home/pemmons# /usr/bin/bgpq3  -h 'whois.radb.net' -l pl -j -m 
24 'AS14237'
{ "pl": [
     { "prefix": "38.123.224.0\/23", "exact": true },
     { "prefix": "38.126.234.0\/23", "exact": true },
     { "prefix": "38.126.236.0\/23", "exact": true },
     { "prefix": "38.126.240.0\/22", "exact": true },
     { "prefix": "38.126.248.0\/21", "exact": true },
     { "prefix": "45.41.164.0\/22", "exact": true },
     { "prefix": "45.61.64.0\/22", "exact": true },
     { "prefix": "68.64.234.0\/24", "exact": true },
     { "prefix": "192.198.233.0\/24", "exact": true },
     { "prefix": "204.48.136.0\/21", "exact": true },
     { "prefix": "206.72.88.0\/22", "exact": true },
     { "prefix": "216.152.248.0\/21", "exact": true }
] }

In short RADB doesn't mirror any other datasets this member uses.  They 
don't have an account with RADB; the entries listed there are proxy 
entries from providers.