<html>
<head>
<meta http-equiv="Content-Type" content="text/html; charset=UTF-8">
</head>
<body>
<p><font face="Calibri">Hi Barry,</font></p>
<p><font face="Calibri">I tried to "cheat" your birdseye API, by
sending my own reply formatted in the way how bird server does
it. However it looks to me once IXP manager receives reply it
compares some of the fields with its configuration statements
for given RS. I'm not generating Junos config from IXP Manager
(at least not yet), but I'm wondering if the reply check can be
somehow disabled in IXP manager?</font></p>
<p><font face="Calibri">br</font></p>
<p><font face="Calibri">Tomek</font><br>
</p>
<div class="moz-cite-prefix">W dniu 11.04.2020 o 16:53, Barry
O'Donovan pisze:<br>
</div>
<blockquote type="cite"
cite="mid:3bbf5540-d288-29fd-ed2a-aa4a5b7c8559@inex.ie">Hi Tomek,
<br>
<br>
Tomasz Szewczyk wrote on 10/04/2020 09:29:
<br>
<blockquote type="cite">I'd like to use IXP Manager with
Juniper/Junos baser Route Server. Could you give me some hints
about IXP manager requirements for API type "Other" or what are
requirements of IXP manager related to API answers?
<br>
</blockquote>
<br>
Thanks for your interest in this.
<br>
<br>
Route server configuration generation is fairly complex as it
involves a lot of components. Fortunately, for adding a new route
server, much of this is done including:
<br>
<br>
- customer and connection details
<br>
- IRRDB AS and prefix lists
<br>
- filtering preferences
<br>
<br>
The way in which IXP Manager generates route server config is
entirely integrated into many other IXP Manager features
including:
<br>
<br>
- looking glass (multiple diffferent features)
<br>
- monitoring (Nagios for example)
<br>
- API
<br>
- member community filtering preferences via UI (not released yet)
<br>
<br>
<br>
We do still plan to look at OpenBGPd during 2020 as an equal-class
alternative to Bird. This would mean updating the Birdseye looking
glass also to parse OpenBGPd output and provide programmatic
access to it via an API. It's a big job.
<br>
<br>
We previously looked at JunOS with one of Juniper's BGP experts
but it was quite difficult and complex to configure it up as a
multi-RIB route server.
<br>
<br>
To you specific question - the only looking glass / API that is
currently supported by IXP Manager is Birdseye. We created this
specifically for Bird for IXP Manager's use but more generically
so that it could be used separately:
<br>
<br>
<a class="moz-txt-link-freetext" href="https://github.com/inex/birdseye">https://github.com/inex/birdseye</a>
<br>
<br>
Any API that can be programmed to this interface should be fine:
<br>
<br>
<a class="moz-txt-link-freetext" href="https://github.com/inex/IXP-Manager/blob/master/app/Contracts/LookingGlass.php">https://github.com/inex/IXP-Manager/blob/master/app/Contracts/LookingGlass.php</a>
<br>
<br>
But if you plan to do this, please talk to me in detail as we
should review the API calls, formatting, etc. in respect to other
daemons - JunOS, OpenBGPd, GoBGP, etc.
<br>
<br>
Thanks,
<br>
- Barry
<br>
<br>
<br>
<br>
<br>
<br>
<br>
<blockquote type="cite">
<br>
br
<br>
<br>
Tomek
<br>
<br>
<br>
<br>
<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>
</blockquote>
<br>
<br>
</blockquote>
</body>
</html>