Routing on the Host has been replaced by Host Pack. Please read the Host Pack user guide instead.

There are two ways to troubleshoot Routing on the Host:

  • Checking the log file /var/log/quagga
  • Using Cumulus Quagga and ip show commands on the host or in a container

Checking the Cumulus Quagga Log File

You can get a lot of troubleshooting information from the Cumulus Quagga log file:

root@host:~# log file /var/log/quagga
2016/06/15 13:48:27 BGP: %NOTIFICATION: sent to neighbor eth1 6/4 (Cease/Administratively Reset) 0 bytes
2016/06/15 13:48:27 BGP: %NOTIFICATION: sent to neighbor eth1 6/4 (Cease/Administratively Reset) 0 bytes
2016/06/15 13:48:27 BGP: %ADJCHANGE: neighbor eth1 Down User reset
2016/06/15 13:48:27 BGP: %ADJCHANGE: neighbor eth2 Down User reset
2016/06/15 13:48:29 BGP: %ADJCHANGE: neighbor eth2 Up
2016/06/15 13:48:29 BGP: %NOTIFICATION: sent to neighbor eth2 6/7 (Cease/Connection collision resolution) 0 bytes
2016/06/15 13:48:29 BGP: %NOTIFICATION: received from neighbor eth1 6/7 (Cease/Connection collision resolution) 0 bytes
2016/06/15 13:48:29 BGP: %ADJCHANGE: neighbor eth1 Up

Using show Commands

You can troubleshoot routes directly on the server host using the ip route show command. If you're running Cumulus Quagga in a container on the host, you can use Cumulus Quagga show commands.

root@host:~# ip route show
default via 192.168.0.254 dev eth0
10.0.0.0/8
  nexthop via 10.0.0.15  dev eth1 weight 1 onlink
  nexthop via 10.0.0.15  dev eth2 weight 1 onlink
10.0.0.11 via 169.254.0.1 dev eth1  proto zebra  metric 20 onlink
10.0.0.12 via 169.254.0.1 dev eth1  proto zebra  metric 20 onlink
10.0.0.13 via 169.254.0.1 dev eth1  proto zebra  metric 20 onlink
10.0.0.14 via 169.254.0.1 dev eth1  proto zebra  metric 20 onlink
10.0.0.21 via 169.254.0.1 dev eth1  proto zebra  metric 20 onlink
10.0.0.22 via 169.254.0.1 dev eth1  proto zebra  metric 20 onlink
10.0.1.101 via 169.254.0.1 dev eth1  proto zebra  metric 20 onlink
10.0.1.103 via 169.254.0.1 dev eth1  proto zebra  metric 20 onlink
10.0.1.104 via 169.254.0.1 dev eth1  proto zebra  metric 20 onlink
172.17.0.0/16 dev docker0  proto kernel  scope link  src 172.17.0.1 linkdown
192.168.0.0/24 dev eth0  proto kernel  scope link  src 192.168.0.32 

The linkdown in this output above is normal since it's from a privileged container. If another container is added, this appears.

If you are running Cumulus Quagga in a container, you can troubleshoot within the container as well using the following show commands. 

host# sh ip route
Codes: K - kernel route, C - connected, S - static, R - RIP,
       O - OSPF, I - IS-IS, B - BGP, T - Table,
       > - selected route, * - FIB route

K>* 0.0.0.0/0 via 192.168.0.254, eth0
B>* 10.0.0.11/32 [20/0] via fe80::4638:39ff:fe00:29, eth1, 00:00:45
B>* 10.0.0.12/32 [20/0] via fe80::4638:39ff:fe00:29, eth1, 00:00:45
B>* 10.0.0.13/32 [20/0] via fe80::4638:39ff:fe00:29, eth1, 00:00:45
B>* 10.0.0.14/32 [20/0] via fe80::4638:39ff:fe00:29, eth1, 00:00:45
B>* 10.0.0.21/32 [20/0] via fe80::4638:39ff:fe00:29, eth1, 00:00:45
B>* 10.0.0.22/32 [20/0] via fe80::4638:39ff:fe00:29, eth1, 00:00:45
B>* 10.0.1.101/32 [20/0] via fe80::4638:39ff:fe00:29, eth1, 00:00:45
B>* 10.0.1.102/32 [20/0] via fe80::4638:39ff:fe00:29, eth1, 00:00:45
B   10.0.1.103/32 [20/0] via fe80::4638:39ff:fe00:29, eth1, 00:00:45
C * 10.0.1.103/32 is directly connected, eth2
C>* 10.0.1.103/32 is directly connected, eth1
B>* 10.0.1.104/32 [20/0] via fe80::4638:39ff:fe00:29, eth1, 00:00:45
C>* 192.168.0.0/24 is directly connected, eth0
host# sh ip bgp summ
BGP router identifier 10.0.0.100, local AS number 65035 vrf-id 0
BGP table version 51
RIB entries 17, using 2040 bytes of memory
Peers 1, using 16 KiB of memory
Peer groups 1, using 56 bytes of memory
 
Neighbor        V    AS MsgRcvd MsgSent   TblVer  InQ OutQ Up/Down  State/PfxRcd
leaf03(eth1)    4 65013     495     500        0    0    0 00:02:57        9
 
Total number of neighbors 1
  • No labels