[ixpmanager] IRRDB back-end not working

[Kyle Spencer]

Surely it would be easy to just have the IRRDB system query and
display the data in the Prefix Analyzer tool without actually enabling
the filtering in BIRD unless that box is checked in the Customer
interface? I imagine there are a few lines of code somewhere that say
"if the customer's IRRDB box is checked, query and display the data"
that can just be deleted so as to allow the data to be queried and
displayed anyway?

There is extremely low IRRDB compliance in Africa based on my
observations. It seems to me that, if this minor change could be done,
it would greatly simplify the transition to IRRDB for African IXPs and
their customers which, in turn, would improve the overall
interconnection ecosystem's health across the region.

On Mon, Sep 18, 2017 at 5:08 PM, Barry O'Donovan <barry.odonovan at inex.ie> wrote:
>
> Kyle Spencer wrote:
>> If I enable IRRDB filtering, my IXP will implode due to the low level
>> of compliance among my membership.
>>
>> However, I do want to work toward enabling it, and IXP Manager's
>> Prefix Analyzer tool would be a very useful way for IXP members to
>> check their compliance in advance.
>>
>> The IRRDB Prefix Analyzer interface suggests this is possible with the
>> top-line message: "Warning! No ports have IRRDB filtering applied so,
>> while this information is useful, it has no impact on your services."
>
> I wouldn't pay too much heed to that message. The tool was not designed
> for users who do not have IRRDB filtering enabled and everyone at INEX
> does as a rule. We won't be developing that tool further as we think
> this can be done better using large community tagging by the route
> server on filtered routes.
>
> It can be a pain to migrate from no IRRDB filtering to using it but it
> is highly highly recommended.
>
> If it we INEX, the way we'd probably do this is:
>
> a) parallel install of IXP Manager with database clone
> b) migrate one route server (or create an additional one) that keys off
> the second install
> c) turn on IRRDB filtering on the second one
>
> There's overhead in that you need to keep the second in sync with the
> first but you can script this quite easily (mysqldump ... | mysql;
> followed by a single query to toggle the IRRDB flag).
>
> This is pretty much how we went about an peering LAN IP renumbering
> recently.
>
>
> LINX are in the middle of a similar exercise - see "IXP Route Server
> Prefix Validation at LINX - Progress and challenges" at:
>
> https://indico.uknof.org.uk/event/40/timetable/#20170912
>
> There should be videos available shortly.
>
>
>  - Barry
>
>
> _______________________________________________
> INEX IXP Manager mailing list
> ixpmanager at inex.ie
> https://www.inex.ie/mailman/listinfo/ixpmanager



-- 
Cell/WhatsApp/Signal: +256790884905