<div dir="ltr">Barry,<div><br></div><div>I don't see those questions in previous e-mails, can you reshare please.</div><div><br></div><div>regards,</div><div><br></div><div>Diarmuid</div></div><div class="gmail_extra"><br clear="all"><div><div class="gmail_signature" data-smartmail="gmail_signature"><div dir="ltr"><div><div dir="ltr"><div><div dir="ltr"><div dir="ltr"><div dir="ltr">--</div><div dir="ltr"><br><div><b style="font-size:small"><i><font color="#38761d">Irish by birth,</font><font color="#ff9900"> located in Uganda</font> but <font color="#cc0000">Munster by the grace of God.</font></i></b><br></div><div><br></div><div><br></div></div></div></div></div></div></div></div></div></div>
<br><div class="gmail_quote">On 12 February 2018 at 18:21, Barry O'Donovan <span dir="ltr"><<a href="mailto:barry.odonovan@inex.ie" target="_blank">barry.odonovan@inex.ie</a>></span> wrote:<br><blockquote class="gmail_quote" style="margin:0 0 0 .8ex;border-left:1px #ccc solid;padding-left:1ex">Re the Birdseye issues Diarmuid, does this thread help:<br>
<br>
<a href="https://www.inex.ie/pipermail/ixpmanager/2018-January/001361.html" rel="noreferrer" target="_blank">https://www.inex.ie/pipermail/<wbr>ixpmanager/2018-January/<wbr>001361.html</a><br>
<br>
If not, I pose a number of diagnostic questions in the last email, can<br>
you answer those?<br>
<br>
- Barry<br>
<br>
<br>
Diarmuid O Briain wrote:<br>
> Hi all,<br>
><br>
> I have setup IXP Manager in a testbed with three ISPs. I am having two<br>
> problems at the moment<br>
><br>
> *1. Looking glass*<br>
><br>
> I setup birds's eye on the Route Server (rs1) and it is working for<br>
><br>
> <a href="http://rs1-lan1-ipv4.netlabsug.tst/" rel="noreferrer" target="_blank">http://rs1-lan1-ipv4.<wbr>netlabsug.tst/</a> <<a href="http://rs1-lan1-ipv4.netlabsug.tst/" rel="noreferrer" target="_blank">http://rs1-lan1-ipv4.<wbr>netlabsug.tst/</a>><br>
> <a href="http://rs1-lan1-ipv4.netlabsug.tst/" rel="noreferrer" target="_blank">http://rs1-lan1-ipv4.<wbr>netlabsug.tst/</a> <<a href="http://rs1-lan1-ipv4.netlabsug.tst/" rel="noreferrer" target="_blank">http://rs1-lan1-ipv4.<wbr>netlabsug.tst/</a>><br>
><br>
> Looking glass on these instances of Birds's Eye works fine, I get a<br>
> webpage for each and can review peerings and route tables, etc..<br>
><br>
> However in IXP Manager when I select a router on looking glass I get:<br>
><br>
> */<a href="http://ixpm1.netlabsug.tst/lg/rs1-lan1-ipv4" rel="noreferrer" target="_blank">http://ixpm1.netlabsug.tst/<wbr>lg/rs1-lan1-ipv4</a><br>
> <<a href="http://ixpm1.netlabsug.tst/lg/rs1-lan1-ipv4" rel="noreferrer" target="_blank">http://ixpm1.netlabsug.tst/<wbr>lg/rs1-lan1-ipv4</a>>/*<br>
><br>
> Whoops, looks like something went wrong.<br>
><br>
> */<a href="http://ixpm1.netlabsug.tst/lg/rs1-lan1-ipv6" rel="noreferrer" target="_blank">http://ixpm1.netlabsug.tst/<wbr>lg/rs1-lan1-ipv6</a><br>
> <<a href="http://ixpm1.netlabsug.tst/lg/rs1-lan1-ipv6" rel="noreferrer" target="_blank">http://ixpm1.netlabsug.tst/<wbr>lg/rs1-lan1-ipv6</a>>/*<br>
><br>
> Whoops, looks like something went wrong.<br>
><br>
> How is IXP Manager getting the config's back from Birds's Eye ?, is<br>
> there something I need to enable to allow this to happen ?<br>
><br>
> In the IPv4 router rs1-lan1-ipv4 I have configured<br>
><br>
> - API Type: Birdseye<br>
> - API Endpoint: <a href="http://rs1-lan1-ipv4.netlabsug.tst/api/" rel="noreferrer" target="_blank">http://rs1-lan1-ipv4.<wbr>netlabsug.tst/api/</a><br>
> <<a href="http://rs1-lan1-ipv4.netlabsug.tst/api/" rel="noreferrer" target="_blank">http://rs1-lan1-ipv4.<wbr>netlabsug.tst/api/</a>><br>
><br>
> and in the IPv4 router rs1-lan1-ipv6 I have configured<br>
><br>
> - API Type: Birdseye<br>
> - API Endpoint: <a href="http://rs1-lan1-ipv6.netlabsug.tst/api/" rel="noreferrer" target="_blank">http://rs1-lan1-ipv6.<wbr>netlabsug.tst/api/</a><br>
> <<a href="http://rs1-lan1-ipv6.netlabsug.tst/api/" rel="noreferrer" target="_blank">http://rs1-lan1-ipv6.<wbr>netlabsug.tst/api/</a>><br>
><br>
> *2. IPv6 problem*<br>
><br>
> I tested the configuration with a simple bird and bird6 setup first to<br>
> ensure it was working.<br>
><br>
> ubuntu@rs1:~$*cat /etc/bird/bird6.conf*<br>
> log syslog all;<br>
><br>
> router id 199.9.9.1;<br>
> define LOCAL_AS = 5999;<br>
><br>
> template bgp PEERS {<br>
> rs client;<br>
> local as LOCAL_AS;<br>
> import all;<br>
> export all;<br>
> }<br>
><br>
> protocol device {<br>
> scan time 10;<br>
> }<br>
><br>
> protocol kernel {<br>
> export all;<br>
> scan time 15;<br>
> }<br>
><br>
> protocol bgp AS5111 from PEERS {<br>
> neighbor 2a99:9:9::11 as 5111;<br>
> }<br>
><br>
> protocol bgp AS5222 from PEERS {<br>
> neighbor 2a99:9:9::22 as 5222;<br>
> }<br>
><br>
> protocol bgp AS5222 from PEERS {<br>
> neighbor 2a99:9:9::33 as 5333;<br>
> }<br>
><br>
> pretty much the same for the bird.conf file except for the neighbour<br>
> addresses.<br>
><br>
> After setting up the IXP Manager scripts on thers1 the<br>
> bird-rs1-lan1-ipv{4|6}.ctl and thebird-rs1-lan1-ipv{4|6}.conf files are<br>
> now generated by IXP Manager.<br>
><br>
> BGP peers are establishing for both birdc andbirdc6 daemons but under<br>
> the birdc6 no routes are being learnt. They were fine with the simple<br>
> configuration above.<br>
><br>
> ubuntu@rs1:~$ sudo birdc<br>
> BIRD 1.6.3 ready.<br>
> bird> *show protocol*<br>
> name proto table state since info<br>
> device1 Device master up 15:24:54<br>
> pp_0001_as5111 Pipe master up 15:24:54 => t_0001_as5111<br>
> pb_0001_as5111 BGP t_0001_as5111 up 15:24:58 Established<br>
> pp_0002_as5222 Pipe master up 15:24:54 => t_0002_as5222<br>
> pb_0002_as5222 BGP t_0002_as5222 up 15:24:58 Established<br>
> pp_0003_as5333 Pipe master up 15:24:54 => t_0003_as5333<br>
> pb_0003_as5333 BGP t_0003_as5333 up 15:24:58 Established<br>
><br>
> bird> *show route*<br>
> <a href="http://199.1.1.0/24" rel="noreferrer" target="_blank">199.1.1.0/24</a> <<a href="http://199.1.1.0/24" rel="noreferrer" target="_blank">http://199.1.1.0/24</a>> via 199.9.9.11 on ens4<br>
> [pb_0001_as5111 15:24:58] * (100) [AS5111i]<br>
> <a href="http://199.3.3.0/24" rel="noreferrer" target="_blank">199.3.3.0/24</a> <<a href="http://199.3.3.0/24" rel="noreferrer" target="_blank">http://199.3.3.0/24</a>> via 199.9.9.33 on ens4<br>
> [pb_0003_as5333 15:24:58] * (100) [AS5333i]<br>
> <a href="http://199.2.2.0/24" rel="noreferrer" target="_blank">199.2.2.0/24</a> <<a href="http://199.2.2.0/24" rel="noreferrer" target="_blank">http://199.2.2.0/24</a>> via 199.9.9.22 on ens4<br>
> [pb_0002_as5222 15:24:58] * (100) [AS5222i]<br>
> bird> exit<br>
><br>
> ubuntu@rs1:~$*sudo birdc6*<br>
> BIRD 1.6.3 ready.<br>
> bird> show protocol<br>
> name proto table state since info<br>
> device1 Device master up 15:24:54<br>
> pp_0001_as5111 Pipe master up 15:24:54 => t_0001_as5111<br>
> pb_0001_as5111 BGP t_0001_as5111 up 15:24:58 Established<br>
> pp_0002_as5222 Pipe master up 15:24:54 => t_0002_as5222<br>
> pb_0002_as5222 BGP t_0002_as5222 up 15:24:58 Established<br>
> pp_0003_as5333 Pipe master up 15:24:54 => t_0003_as5333<br>
> pb_0003_as5333 BGP t_0003_as5333 up 15:24:55 Established<br>
><br>
> bird> *show route*<br>
> bird><br>
><br>
> Any ideas ? I am using the networks 2a99:9:9::0/64 on the peering LAN<br>
> and 2a99:1:1::0/64, 2a99:2:2::0/64 and 2a99:3:3::0/64 for the ISP<br>
> internal networks.<br>
><br>
> regards,<br>
><br>
> Diarmuid<br>
> --<br>
><br>
> */Irish by birth, located in Uganda but Munster by the grace of God./*<br>
><br>
><br>
><br>
> ______________________________<wbr>_________________<br>
> INEX IXP Manager mailing list<br>
> <a href="mailto:ixpmanager@inex.ie">ixpmanager@inex.ie</a><br>
> <a href="https://www.inex.ie/mailman/listinfo/ixpmanager" rel="noreferrer" target="_blank">https://www.inex.ie/mailman/<wbr>listinfo/ixpmanager</a><br>
<br>
--<br>
<br>
Kind regards,<br>
Barry O'Donovan<br>
INEX Operations<br>
<br>
<a href="https://www.inex.ie/support/" rel="noreferrer" target="_blank">https://www.inex.ie/support/</a><br>
<a href="tel:%2B353%201%20531%203339" value="+35315313339">+353 1 531 3339</a><br>
<br>
______________________________<wbr>_________________<br>
INEX IXP Manager mailing list<br>
<a href="mailto:ixpmanager@inex.ie">ixpmanager@inex.ie</a><br>
<a href="https://www.inex.ie/mailman/listinfo/ixpmanager" rel="noreferrer" target="_blank">https://www.inex.ie/mailman/<wbr>listinfo/ixpmanager</a><br>
</blockquote></div><br></div>