[ixpmanager] IXPM 2 problems

[Barry O'Donovan]

Re the Birdseye issues Diarmuid, does this thread help:

https://www.inex.ie/pipermail/ixpmanager/2018-January/001361.html

If not, I pose a number of diagnostic questions in the last email, can
you answer those?

 - Barry


Diarmuid O Briain wrote:
> 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/>
> 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/
> <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/
> <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 thers1 the
> bird-rs1-lan1-ipv{4|6}.ctl and thebird-rs1-lan1-ipv{4|6}.conf files are
> now generated by IXP Manager.
> 
> BGP peers are establishing for both birdc andbirdc6 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 <http://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 <http://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 <http://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

-- 

Kind regards,
Barry O'Donovan
INEX Operations

https://www.inex.ie/support/
+353 1 531 3339