[quagga-users 8337] Re: Rip announcing default route

Sean Fulton sean at gcnpublishing.com
Tue May 1 09:16:11 IST 2007


This is from one of the web servers. Note the current default 
(209.2.68.1) is correct:
user> sh ip rip
Codes: R - RIP, C - connected, S - Static, O - OSPF, B - BGP
Sub-codes:
      (n) - normal, (s) - static, (d) - default, (r) - redistribute,
      (i) - interface

     Network            Next Hop         Metric From            Tag Time
R(n) 0.0.0.0/0          209.2.68.1            2 209.2.68.1        0 02:58
R(n) 69.25.73.108/30    209.2.69.9            2 209.2.69.9        0 02:16
C(i) 209.2.68.0/26      0.0.0.0               1 self              0
R(n) 209.2.68.20/32     209.2.68.2            7 209.2.68.2        0 02:26
R(n) 209.2.68.21/32     209.2.68.2            7 209.2.68.2        0 02:26
R(n) 209.2.68.22/32     209.2.68.2            7 209.2.68.2        0 02:26
R(n) 209.2.68.23/32     209.2.68.2            7 209.2.68.2        0 02:26
R(n) 209.2.68.24/32     209.2.68.2            7 209.2.68.2        0 02:26
R(n) 209.2.68.25/32     209.2.68.2            7 209.2.68.2        0 02:26
R(n) 209.2.68.26/32     209.2.68.2            7 209.2.68.2        0 02:26
R(n) 209.2.68.27/32     209.2.68.2            7 209.2.68.2        0 02:26
R(n) 209.2.68.28/32     209.2.68.2            7 209.2.68.2        0 02:26
R(n) 209.2.68.29/32     209.2.68.2            7 209.2.68.2        0 02:26
R(n) 209.2.68.30/32     209.2.68.2            7 209.2.68.2        0 02:26
R(n) 209.2.68.32/32     209.2.68.2            7 209.2.68.2        0 02:26
C(i) 209.2.69.0/26      0.0.0.0               1 self              0
R(n) 209.2.69.10/32     209.2.68.7            7 209.2.68.7        0 02:44
C(i) 209.2.70.29/32     0.0.0.0               1 self              0
C(i) 209.2.70.30/32     0.0.0.0               1 self              0
C(i) 209.2.70.33/32     0.0.0.0               1 self              0
C(i) 209.2.70.34/32     0.0.0.0               1 self              0
C(i) 209.2.70.35/32     0.0.0.0               1 self              0
C(i) 209.2.70.40/32     0.0.0.0               1 self              0
C(i) 209.2.70.41/32     0.0.0.0               1 self              0
C(i) 209.2.70.42/32     0.0.0.0               1 self              0
C(i) 209.2.70.44/32     0.0.0.0               1 self              0
C(i) 209.2.70.45/32     0.0.0.0               1 self              0
C(i) 209.2.70.46/32     0.0.0.0               1 self              0
C(i) 209.2.70.47/32     0.0.0.0               1 self              0
C(i) 209.2.70.48/32     0.0.0.0               1 self              0
C(i) 209.2.70.53/32     0.0.0.0               1 self              0
C(i) 209.2.70.54/32     0.0.0.0               1 self              0
C(i) 209.2.70.55/32     0.0.0.0               1 self              0
C(i) 209.2.70.57/32     0.0.0.0               1 self              0
C(i) 209.2.70.60/32     0.0.0.0               1 self              0
C(i) 209.2.70.61/32     0.0.0.0               1 self              0
C(i) 209.2.70.62/32     0.0.0.0               1 self              0
C(i) 209.2.70.63/32     0.0.0.0               1 self              0
C(i) 209.2.70.66/32     0.0.0.0               1 self              0
C(i) 209.2.70.68/32     0.0.0.0               1 self              0
C(i) 209.2.70.69/32     0.0.0.0               1 self              0
C(i) 209.2.70.70/32     0.0.0.0               1 self              0
C(i) 209.2.70.71/32     0.0.0.0               1 self              0
C(i) 209.2.70.72/32     0.0.0.0               1 self              0
C

Now when I kill rip on the default (209.2.68.1), instead of 209.2.68.9 
becoming the default, I get one of our web servers (209.2.69.6):

user> sh ip rip
Codes: R - RIP, C - connected, S - Static, O - OSPF, B - BGP
Sub-codes:
      (n) - normal, (s) - static, (d) - default, (r) - redistribute,
      (i) - interface

     Network            Next Hop         Metric From            Tag Time
R(n) 0.0.0.0/0          209.2.69.6            4 209.2.69.6        0 02:52
R(n) 69.25.73.108/30    209.2.68.9            2 209.2.68.9        0 02:36
C(i) 209.2.68.0/26      0.0.0.0               1 self              0
R(n) 209.2.68.20/32     209.2.68.2            7 209.2.68.2        0 02:50
R(n) 209.2.68.21/32     209.2.68.2            7 209.2.68.2        0 02:50
R(n) 209.2.68.22/32     209.2.68.2            7 209.2.68.2        0 02:50
R(n) 209.2.68.23/32     209.2.68.2            7 209.2.68.2        0 02:50
R(n) 209.2.68.24/32     209.2.68.2            7 209.2.68.2        0 02:50
R(n) 209.2.68.25/32     209.2.68.2            7 209.2.68.2        0 02:50
R(n) 209.2.68.26/32     209.2.68.2            7 209.2.68.2        0 02:50
R(n) 209.2.68.27/32     209.2.68.2            7 209.2.68.2        0 02:50
R(n) 209.2.68.28/32     209.2.68.2            7 209.2.68.2        0 02:50
R(n) 209.2.68.29/32     209.2.68.2            7 209.2.68.2        0 02:50
R(n) 209.2.68.30/32     209.2.68.2            7 209.2.68.2        0 02:50
R(n) 209.2.68.32/32     209.2.68.2            7 209.2.68.2        0 02:50
C(i) 209.2.69.0/26      0.0.0.0               1 self              0
R(n) 209.2.69.10/32     209.2.68.7            7 209.2.68.7        0 02:59
C(i) 209.2.70.29/32     0.0.0.0               1 self              0
C(i) 209.2.70.30/32     0.0.0.0               1 self              0
C(i) 209.2.70.33/32     0.0.0.0               1 self              0
C(i) 209.2.70.34/32     0.0.0.0               1 self              0
C(i) 209.2.70.35/32     0.0.0.0               1 self              0
C(i) 209.2.70.40/32     0.0.0.0               1 self              0
C(i) 209.2.70.41/32     0.0.0.0               1 self              0
C(i) 209.2.70.42/32     0.0.0.0               1 self              0
C(i) 209.2.70.44/32     0.0.0.0               1 self              0
C(i) 209.2.70.45/32     0.0.0.0               1 self              0
C(i) 209.2.70.46/32     0.0.0.0               1 self              0
C(i) 209.2.70.47/32     0.0.0.0               1 self              0
C(i) 209.2.70.48/32     0.0.0.0               1 self              0
C(i) 209.2.70.53/32     0.0.0.0               1 self              0
C(i) 209.2.70.54/32     0.0.0.0               1 self              0
C(i) 209.2.70.55/32     0.0.0.0               1 self              0
C(i) 209.2.70.57/32     0.0.0.0               1 self              0
C(i) 209.2.70.60/32     0.0.0.0               1 self              0
C(i) 209.2.70.61/32     0.0.0.0               1 self              0
C(i) 209.2.70.62/32     0.0.0.0               1 self              0
C(i) 209.2.70.63/32     0.0.0.0               1 self              0
C(i) 209.2.70.66/32     0.0.0.0               1 self              0
C(i) 209.2.70.68/32     0.0.0.0               1 self              0
C(i) 209.2.70.69/32     0.0.0.0               1 self              0
C(i) 209.2.70.70/32     0.0.0.0               1 self              0
C(i) 209.2.70.71/32     0.0.0.0               1 self              0
C(i) 209.2.70.72/32     0.0.0.0               1 self              0
C(i) 209.2.70.73/32     0.0.0.0               1 self              0
 

Paul Jakma wrote:
> On Mon, 30 Apr 2007, Sean Fulton wrote:
>
>> I have a strange problem with several machines running 
>> quagga-0.97.3-1.FC3.
>
> You probably should upgrade.
>
>> We have two border routers running BGP/RIP, and each announces a 
>> default route to the network. We have five or six web servers that 
>> each assign static IP addresses to the loopback interface and 
>> announce those static routes via RIP.
>
>> What should happen is that if one of the border routers fails and 
>> stops announcing the default route, the other border router's RIP 
>> announcement will be next in line and each of the machines will 
>> default route through the working router. Unfortunately, what is 
>> happening is that all of the web servers are announcing a default 
>> route through themselves. So for example, if XXX.XXX.XXX.1 goes down, 
>> instead of XXX.XXX.XXX.9 becoming the default route, the default 
>> route becomes XXX.XXX.XXX.4, which is one of the web servers.
>
>> Here is the ripd.conf that we use on all of the web servers. Any help 
>> or guidance would be appreciated.
>
> Can we see 'show ip rip' output?
>
> regards,

-- 
Sean Fulton
GCN Publishing, Inc.
Internet Design, Development and Consulting For Today's Media Companies
http://www.gcnpublishing.com
(914) 937-2451, x203




More information about the Quagga-users mailing list