Questions[quagga](server)

I have 2 routers announcing a /22 subnet to different providers (one providers connects to each of the 2 routers). I have split the /22 in two /23 to announce one /23 on each of the routers plus the /22 (the providers will take the more specific route). This allows me to fail over and keep traffic inside the /23 in and out the same provider.

What are other ways in which I could announce just the /22 with both routers and have packets from servers on the network behind the routers go back out the same router in which they came in from?

EDIT:

The main problem I come across, which end users and clients complain about the most, is that the least hop route is sometimes not the "optimal" route. In my case, I know that Provider B may have better latency to X nation. But when packets come in from provider B, they may go out Provider A or provider B. The reverse is also true. If I send a packet to X nation out provider A, even though it may have more hops back, the packet will likely come in from Provider B (which may have higher latency, packet loss, etc. to this nation)

I'm going to setup redundant failover Redmine:

• another instance was installed on the second server without problem
• MySQL (running on the same machine with Redmine) was configured as master-master replication

Because they are in different subnet (192.168.3.x and 192.168.6.x), it seems that VIPArip is the only choice.

/etc/ha.d/ha.cf on node1

logfacility none
debug 1
debugfile /var/log/ha-debug
logfile /var/log/ha-log
autojoin none
warntime 3
deadtime 6
initdead 60
udpport 694
ucast eth1 node2.ip
keepalive 1
node node1
node node2
crm respawn

/etc/ha.d/ha.cf on node2:

logfacility none
debug 1
debugfile /var/log/ha-debug
logfile /var/log/ha-log
autojoin none
warntime 3
deadtime 6
initdead 60
udpport 694
ucast eth0 node1.ip
keepalive 1
node node1
node node2
crm respawn

crm configure show:

node $id="6c27077e-d718-4c82-b307-7dccaa027a72" node1
node $id="740d0726-e91d-40ed-9dc0-2368214a1f56" node2
primitive VIPArip ocf:heartbeat:VIPArip \
        params ip="192.168.6.8" nic="lo:0" \
        op start interval="0" timeout="20s" \
        op monitor interval="5s" timeout="20s" depth="0" \
        op stop interval="0" timeout="20s" \
        meta is-managed="true"
property $id="cib-bootstrap-options" \
        stonith-enabled="false" \
        dc-version="1.0.12-unknown" \
        cluster-infrastructure="Heartbeat" \
        last-lrm-refresh="1338870303"

crm_mon -1:

============
Last updated: Tue Jun  5 18:36:42 2012
Stack: Heartbeat
Current DC: node2 (740d0726-e91d-40ed-9dc0-2368214a1f56) - partition with quorum
Version: 1.0.12-unknown
2 Nodes configured, unknown expected votes
1 Resources configured.
============

Online: [ node1 node2 ]

 VIPArip    (ocf::heartbeat:VIPArip):   Started node1

ip addr show lo:

1: lo: <LOOPBACK,UP,LOWER_UP> mtu 16436 qdisc noqueue 
    link/loopback 00:00:00:00:00:00 brd 00:00:00:00:00:00
    inet 127.0.0.1/8 scope host lo
    inet 192.168.6.8/32 scope global lo
    inet6 ::1/128 scope host 
       valid_lft forever preferred_lft forever

I can ping 192.168.6.8 from node1 (192.168.3.x):

# ping -c 4 192.168.6.8
PING 192.168.6.8 (192.168.6.8) 56(84) bytes of data.
64 bytes from 192.168.6.8: icmp_seq=1 ttl=64 time=0.062 ms
64 bytes from 192.168.6.8: icmp_seq=2 ttl=64 time=0.046 ms
64 bytes from 192.168.6.8: icmp_seq=3 ttl=64 time=0.059 ms
64 bytes from 192.168.6.8: icmp_seq=4 ttl=64 time=0.071 ms

--- 192.168.6.8 ping statistics ---
4 packets transmitted, 4 received, 0% packet loss, time 3000ms
rtt min/avg/max/mdev = 0.046/0.059/0.071/0.011 ms

but cannot ping virtual IP from node2 (192.168.6.x) and outside. Did I miss something?

PS: you probably want to set IP2UTIL=/sbin/ip in the /usr/lib/ocf/resource.d/heartbeat/VIPArip resource agent script if you get something like this:

Jun 5 11:08:10 node1 lrmd: [19832]: info: RA output: (VIPArip:stop:stderr) 2012/06/05_11:08:10 ERROR: Invalid OCF_RESK EY_ip [192.168.6.8]

http://www.clusterlabs.org/wiki/Debugging_Resource_Failures

Reply to @DukeLion:

Which router receives RIP updates?

When I start the VIPArip resource, ripd was run with below configuration file (on node1):

/var/run/resource-agents/VIPArip-ripd.conf:

hostname ripd
password zebra
debug rip events
debug rip packet
debug rip zebra
log file /var/log/quagga/quagga.log
router rip
!nic_tag
 no passive-interface lo:0
 network lo:0
 distribute-list private out lo:0
 distribute-list private in lo:0
!metric_tag
 redistribute connected metric 3
!ip_tag
access-list private permit 192.168.6.8/32
access-list private deny any

show ip route:

Codes: K - kernel route, C - connected, S - static, R - RIP,
       O - OSPF, I - IS-IS, B - BGP, A - Babel,
       > - selected route, * - FIB route

K>* 0.0.0.0/0 via 192.168.3.1, eth1
C>* 127.0.0.0/8 is directly connected, lo
K>* 169.254.0.0/16 is directly connected, eth1
C>* 192.168.3.0/24 is directly connected, eth1
C>* 192.168.6.8/32 is directly connected, lo

sh ip rip status:

Routing Protocol is "rip"
  Sending updates every 30 seconds with +/-50%, next due in 7 seconds
  Timeout after 180 seconds, garbage collect after 120 seconds
  Outgoing update filter list for all interface is not set
    lo:0 filtered by private
  Incoming update filter list for all interface is not set
    lo:0 filtered by private
  Default redistribution metric is 1
  Redistributing: connected
  Default version control: send version 2, receive any version 
    Interface        Send  Recv   Key-chain
  Routing for Networks:
    lo:0
  Routing Information Sources:
    Gateway          BadPackets BadRoutes  Distance Last Update
  Distance: (default is 120)

This question is related to a previous one on OSPF routing.

Based on the advice give to the previous question, I have now made myself a network diagram, identified the backbone area and all other areas and started configuring OSPF on the various routers. All the HP ProCurve 7102dl routers talk to each and that works fine. However, on the intra-area routers, which are all Linux servers, I am using quagga (Version 0.99.10, from debian lenny) and this just won't work at all.

Here are some examples: In one particular area the primary network is 192.168.51.0/24 and both the linux router and the HP router have an interface in that network. The HP router has VPN tunnels to other HP routers and connects the entire subnet to the outside world. Behind the Linux router is another subnet on 192.168.52.0/24. When I look at the OSPF configuration for these interfaces, this is what I get:

Linux router:

uk-swa-bps01# show ip ospf interface eth0
eth0 is up
  ifindex 2, MTU 1500 bytes, BW 0 Kbit <UP,BROADCAST,RUNNING,MULTICAST>
  Internet Address 192.168.51.1/24, Broadcast 192.168.51.255, Area 0.0.0.51
  MTU mismatch detection:enabled
  Router ID 192.168.51.1, Network Type BROADCAST, Cost: 10
  Transmit Delay is 1 sec, State DR, Priority 1
  Designated Router (ID) 192.168.51.1, Interface Address 192.168.51.1
  No backup designated router on this network
  Multicast group memberships: OSPFAllRouters OSPFDesignatedRouters
  Timer intervals configured, Hello 10s, Dead 40s, Wait 40s, Retransmit 5
    Hello due in 6.595s
  Neighbor Count is 0, Adjacent neighbor count is 0

uk-swa-bps01# show ip ospf database
   OSPF Router with ID (192.168.51.1)

            Router Link States (Area 0.0.0.51)

    Link ID         ADV Router      Age  Seq#       CkSum  Link count
    192.168.51.1    192.168.51.1    1335 0x80000016 0xabf6 2

And on the HP router:

bps-test-vpn#show ip ospf interface ethernet 0/2
eth 0/2 is UP, line protocol is UP
  IP address: 192.168.51.254 255.255.255.0, Area: 0.0.0.51
  Router ID: 192.168.51.254, Network type: Broadcast, Cost: 1
  Transmit delay: 1, State: DR, Priority: 1
  Designated Router (ID): 192.168.51.254, Interface Address: 192.168.51.254
  Backup Designated Router (ID): 0.0.0.0, Interface Address: 0.0.0.0
  Timer intervals: Hello: 10, Dead: 40, Retransmit: 5
    Hello due in: 00:00:05
  Number of neighbors: 0, Adjacent neighbors: 0

bps-test-vpn#show ip ospf 0 database 

OSPF router with ID: 192.168.51.254

  Router Link States, Area 0
    Link ID          Adv Router        Age     Seq #         Checksum
    10.10.2.1        10.10.2.1          601    0x80000004    0xECAD
    10.176.1.33      10.176.1.33       1526    0x80000086    0xAAE1
    10.181.1.1       10.181.1.1         826    0x8000009A    0x56EF
    192.168.51.254   192.168.51.254     819    0x8000001D    0x0B13

  Summary Net Link States, Area 0
    Link ID          Adv Router        Age     Seq #         Checksum
    10.171.0.0       10.10.2.1          825    0x80000001    0x2867
    10.171.0.0       10.176.1.33       1520    0x80000001    0x3990
    10.181.0.0       10.181.1.1        1226    0x80000009    0x4989
    10.181.1.0       10.181.1.1        1226    0x80000032    0xD9D1
    192.168.51.0     192.168.51.254     824    0x80000016    0xF915
bps-test-vpn#show ip ospf 0.0.0.51 database 

OSPF router with ID: 192.168.51.254

  Router Link States, Area 0.0.0.51
    Link ID          Adv Router        Age     Seq #         Checksum
    192.168.51.254   192.168.51.254     845    0x80000009    0xFD79

  Summary Net Link States, Area 0.0.0.51
    Link ID          Adv Router        Age     Seq #         Checksum
    0.0.0.0          192.168.51.254     610    0x80000005    0x15AA
    10.10.1.40       192.168.51.254     835    0x80000001    0x87FF
    10.10.1.44       192.168.51.254     830    0x80000001    0x6919
    10.10.1.52       192.168.51.254     835    0x80000001    0x0F6C
    10.10.1.72       192.168.51.254     844    0x80000001    0x3C2C
    10.10.1.76       192.168.51.254     835    0x80000001    0x1E45
    10.171.0.0       192.168.51.254     830    0x80000001    0xA269
    10.181.0.0       192.168.51.254     830    0x80000001    0x34CC
    10.181.1.0       192.168.51.254     830    0x80000001    0x17EB

Clearly OSPF is enabled on both sides on the interfaces that are in the 192.168.51.0/24 subnet, yet they don't talk to each other, because otherwise I would be getting some OSPF routes on the Linux Box. But I am not. So what am I doing wrong? I have tried all sorts of things, but I am not making any headways. Any advice would be appreciated. If you need additional info, just ask and I'll edit my post.

I have a route that is both directly connected to a router as well as received via iBGP. With quagga, if I telnet to bgpd and run show ip bgp, I can see the route in the table as an iBGP route and a directly connected route, however the directly connected route is of course the one that is preferred.

When I take down the directly connected route by bringing down the interface, the directly connected route is not removed from the bgp table and it is still preferred. In the kernel routing table, there is no longer any entry for the route. How do I make sure the routing tables update properly when this happens?

I have set up BGP on two routers using qugga. When I down the interface that holds the IP block that I am advertising zerba removes the route from its table but bgpd keeps advertising it. I can see that it is still advertised via the neighboring BGP tables as well as the show ip bgp nei 172.16.14.1 ad command from the router that is doing the advertising. This interface holds the full route that is being advertised so there is no aggregation.

As anyone run into this before ... it seems to fundamentally break the main functionality of a routing protocol...

Update:
So in the router I have the following for a BGP table.

so-rt1# show ip bgp
BGP table version is 0, local router ID is 172.16.14.1
Status codes: s suppressed, d damped, h history, * valid, > best, i - internal,
              r RIB-failure, S Stale, R Removed
Origin codes: i - IGP, e - EGP, ? - incomplete

   Network          Next Hop            Metric LocPrf Weight Path
*> 0.0.0.0          12.12.12.12                   200      0 5555 i
*  15.15.15.0/24    172.16.14.2              0    100      0 i
*>                  0.0.0.0                  0         32768 i

Total number of prefixes 2

For the 15.15.15.0/24 network, which I announce, the directly connect route (the last entry) is the route that is preferred. If I shutdown the interface that holds 15.15.15.0/24 not only is the directly connected route not removed from the BGP table, it is still the preferred route. So after shutting down that interface, the BGP table stays exactly the same.

Zebra is aware that the directly connected 15.15.15.0/24 route is no longer there. I see it with show ip route while the interface is up and the entry is gone when I shut it down. So the problem I think is that the BGP table is somehow not getting the updates I believe it should from zebra.