[ixpmanager] Fwd: IXPM 2 problems
Diarmuid O Briain
diarmuid at obriain.com
Mon Feb 12 15:14:56 GMT 2018
Kyle,
I did have that, IRRDB filtering is not specific to IPv4 or IPv6 and as
IPv4 is working it shouldn't have any impact on IPv6.
regards,
Diarmuid
[image: Inline images 1]
--
*Irish by birth, located in Uganda but Munster by the grace of God.*
---------- Forwarded message ----------
From: Kyle Spencer <kyle at stormzero.com>
Date: 11 February 2018 at 21:41
Subject: Fwd: [ixpmanager] IXPM 2 problems
To: Diarmuid O Briain <diarmuid at obriain.com>
As for lack of routes learned, make sure IRRDB filtering is disabled in IXP
Manager for each customer network.
--
Cell/WhatsApp/Signal: +256790884905 <+256%20790%20884905>
---------- Forwarded message ----------
From: "Diarmuid O Briain" <diarmuid at obriain.com>
Date: 11 Feb 2018 21:36
Subject: [ixpmanager] IXPM 2 problems
To: <ixpmanager at inex.ie>
Cc:
Hi all,
I have setup IXP Manager in a testbed with three ISPs. I am having two
problems at the moment
*1. Looking glass*
I setup birds's eye on the Route Server (rs1) and it is working for
http://rs1-lan1-ipv4.netlabsug.tst/
http://rs1-lan1-ipv4.netlabsug.tst/
Looking glass on these instances of Birds's Eye works fine, I get a webpage
for each and can review peerings and route tables, etc..
However in IXP Manager when I select a router on looking glass I get:
*http://ixpm1.netlabsug.tst/lg/rs1-lan1-ipv4
<http://ixpm1.netlabsug.tst/lg/rs1-lan1-ipv4>*
Whoops, looks like something went wrong.
*http://ixpm1.netlabsug.tst/lg/rs1-lan1-ipv6
<http://ixpm1.netlabsug.tst/lg/rs1-lan1-ipv6>*
Whoops, looks like something went wrong.
How is IXP Manager getting the config's back from Birds's Eye ?, is there
something I need to enable to allow this to happen ?
In the IPv4 router rs1-lan1-ipv4 I have configured
- API Type: Birdseye
- API Endpoint: http://rs1-lan1-ipv4.netlabsug.tst/api/
and in the IPv4 router rs1-lan1-ipv6 I have configured
- API Type: Birdseye
- API Endpoint: http://rs1-lan1-ipv6.netlabsug.tst/api/
*2. IPv6 problem*
I tested the configuration with a simple bird and bird6 setup first to
ensure it was working.
ubuntu at rs1:~$* cat /etc/bird/bird6.conf*
log syslog all;
router id 199.9.9.1;
define LOCAL_AS = 5999;
template bgp PEERS {
rs client;
local as LOCAL_AS;
import all;
export all;
}
protocol device {
scan time 10;
}
protocol kernel {
export all;
scan time 15;
}
protocol bgp AS5111 from PEERS {
neighbor 2a99:9:9::11 as 5111;
}
protocol bgp AS5222 from PEERS {
neighbor 2a99:9:9::22 as 5222;
}
protocol bgp AS5222 from PEERS {
neighbor 2a99:9:9::33 as 5333;
}
pretty much the same for the bird.conf file except for the neighbour
addresses.
After setting up the IXP Manager scripts on the rs1 the b
ird-rs1-lan1-ipv{4|6}.ctl and the bird-rs1-lan1-ipv{4|6}.conf files are now
generated by IXP Manager.
BGP peers are establishing for both birdc and birdc6 daemons but under the
birdc6 no routes are being learnt. They were fine with the simple
configuration above.
ubuntu at rs1:~$ sudo birdc
BIRD 1.6.3 ready.
bird> *show protocol*
name proto table state since info
device1 Device master up 15:24:54
pp_0001_as5111 Pipe master up 15:24:54 => t_0001_as5111
pb_0001_as5111 BGP t_0001_as5111 up 15:24:58 Established
pp_0002_as5222 Pipe master up 15:24:54 => t_0002_as5222
pb_0002_as5222 BGP t_0002_as5222 up 15:24:58 Established
pp_0003_as5333 Pipe master up 15:24:54 => t_0003_as5333
pb_0003_as5333 BGP t_0003_as5333 up 15:24:58 Established
bird> *show route*
199.1.1.0/24 via 199.9.9.11 on ens4 [pb_0001_as5111 15:24:58] * (100)
[AS5111i]
199.3.3.0/24 via 199.9.9.33 on ens4 [pb_0003_as5333 15:24:58] * (100)
[AS5333i]
199.2.2.0/24 via 199.9.9.22 on ens4 [pb_0002_as5222 15:24:58] * (100)
[AS5222i]
bird> exit
ubuntu at rs1:~$* sudo birdc6*
BIRD 1.6.3 ready.
bird> show protocol
name proto table state since info
device1 Device master up 15:24:54
pp_0001_as5111 Pipe master up 15:24:54 => t_0001_as5111
pb_0001_as5111 BGP t_0001_as5111 up 15:24:58 Established
pp_0002_as5222 Pipe master up 15:24:54 => t_0002_as5222
pb_0002_as5222 BGP t_0002_as5222 up 15:24:58 Established
pp_0003_as5333 Pipe master up 15:24:54 => t_0003_as5333
pb_0003_as5333 BGP t_0003_as5333 up 15:24:55 Established
bird> *show route*
bird>
Any ideas ? I am using the networks 2a99:9:9::0/64 on the peering LAN and
2a99:1:1::0/64, 2a99:2:2::0/64 and 2a99:3:3::0/64 for the ISP internal
networks.
regards,
Diarmuid
--
*Irish by birth, located in Uganda but Munster by the grace of God.*
_______________________________________________
INEX IXP Manager mailing list
ixpmanager at inex.ie
https://www.inex.ie/mailman/listinfo/ixpmanager
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <https://www.inex.ie/pipermail/ixpmanager/attachments/20180212/40700bee/attachment-0001.html>
-------------- next part --------------
A non-text attachment was scrubbed...
Name: image.png
Type: image/png
Size: 10761 bytes
Desc: not available
URL: <https://www.inex.ie/pipermail/ixpmanager/attachments/20180212/40700bee/attachment-0001.png>
More information about the ixpmanager
mailing list