<html><head>
<meta http-equiv="Content-Type" content="text/html; charset=utf-8">
</head><body style="font-family: Calibri; font-size: 11pt;"
text="#2e3572" bgcolor="#FFFFFF"><div style="font-size:
11pt;font-family: Calibri;">Hi Edd,<br><br>This mechanism is a bit
involved, but the way it works is as follows:<br><ul><li>each customer
is set up with an IRRDB policy in the customer setup page. You need to
select one of the existing policies which pulls prefixes with the
appropriate source: list from either RADB or else from the RIR-operated
IRRDB. Each customer can be set up with their own unique policy, so you
need to check out what works best for them.<br></li><li>when you issue
the 'artisan irrdb:update-prefix-db' and 'artisan irrdb:update-asn-db',
this pulls information from the per-customer IRRDB sources into the IXP
Manager SQL database.</li><li>'compare-route-server-prefixes.pl'
inspects what BIRD sees incoming from each client connection and
compares that against what it finds in the IXP-M SQL DB. If it doesn't
find a match, it prints: "irrdb:0" because that indicates that it
couldn't find that specific prefix in the IRRDB output for that
customer.<br></li></ul>To resolve your problem you need to find out what
IRRDB holds the definition for AS-THUSACONNECT and configure that as
the IRRDB source for your member in IXP Manager. Once you've done this,
you should run artisan irrdb:update-prefix-db and see if it picks up
that particular /32. If this doesn't solve the problem, there's
something more involved going on, but try this first and see how it
goes.<br><br>Nick<br><span>
</span><br><blockquote type="cite"
cite="mid:CAJZ9dTDdnOk=G0viboXDP3PPaqpFcNJ29kKLSABTZm0ajNs4GA@mail.gmail.com"
style="border: 0px none ! important;"><div
xmlns="http://www.w3.org/1999/xhtml" class="__pbConvHr"
style="margin:30px 25px 10px 25px;"><div
style="width:100%;border-top:2px solid #EDF1F4;padding-top:10px;"> <div
style="display:inline-block;white-space:nowrap;vertical-align:middle;width:49%;">
<a style="color:#485664
!important;padding-right:6px;font-weight:500;text-decoration:none
!important;" href="mailto:edd@edd.za.net" moz-do-not-send="true">Edrich
de Lange</a></div> <div
style="display:inline-block;white-space:nowrap;vertical-align:middle;width:48%;text-align:
right;"> <font color="#909AA4"><span style="padding-left:6px">7
August 2018 at 13:42</span></font></div> </div></div><div
xmlns="http://www.w3.org/1999/xhtml" class="__pbConvBody"
__pbrmquotes="true"
style="color:#909AA4;margin-left:24px;margin-right:24px;"><div>Hi All<br><br>We
are having some difficulty using the route server prefixes<br>functionality
with compare-route-server-prefixes.pl and thought it would<br>be wise
to see if there was something obvious that we were missing.<br><br>We’ve
converted one set of our route servers to use the ixpmanagers<br>generated
configs for bird, and that’s working fine. The<br>compare-route-server-prefixes.pl
script correctly pulls in the routes<br>being advertised. But it
thinks that 99% of these are not accepted (it<br>does show some as
accepted, and some not advertised but accepted)<br>according to the
frontend. (Meanwhile, at route-server level, the<br>actual routes are
being accepted, processed the route-server filters,<br>and propagated
onwards correctly)<br><br>My perl is really sucky, so debugging this is
also a bit difficult. :-)<br>I can see it inserting the routes into the
DB, all fine, but the routes<br>most get listed as “accepted but
filtered” as opposed to “accepted<br>and advertised”<br><br>Debug output
:<br>INSERT: peer-as: xxxxx, prefix: x.x.x.x/x origin-as: xxxx, irrdb: 0<br><br>Im
assuming the irrdb:0 is what determines if its filtered or not. But I<br>can
not figure out where that data comes from. Out of about 50 000<br>routes,
there is about 15 that it says is accepted. (which is obviously<br>incorrect).<br><br>I
have installed the perl libraries required, and I see no other errors<br>from
the script. It sees all the peers, along with their announcements.<br>And
if I run the command manually, it seems to be correct output:<br><br>root@rs2:~# /usr/sbin/birdc
-s /run/bird/bird6.ctl show route table<br>t_0130_as32437 protocol
pb_0130_as32437<br>BIRD 1.6.3 ready.<br>2c0f:f178::/32 via
2001:43f8:1f0::121 on eth1<br>[pb_0130_as32437 21:09:48] * (100)
[AS32437i]<br><br>And that prefix is definitely in the irrdb record<br>root@rs2:~#
bgpq3 -b -6 as-thusaconnect<br>NN = [<br> 2c0f:f178::/32<br>] ;<br><br>Cluebat
anyone?<br><br>Edd<br><br><a class="moz-txt-link-abbreviated" href="mailto:edd@edd.za.net">edd@edd.za.net</a><br>0832629566<br>_______________________________________________<br>INEX
IXP Manager mailing list<br><a class="moz-txt-link-abbreviated" href="mailto:ixpmanager@inex.ie">ixpmanager@inex.ie</a><br>Unsubscribe or change
options here: <a class="moz-txt-link-freetext" href="https://www.inex.ie/mailman/listinfo/ixpmanager">https://www.inex.ie/mailman/listinfo/ixpmanager</a><br><br></div>
</div></blockquote><br></div></body></html>