[quagga-dev 4606] bgpd lost a route

Andrew J. Schorr aschorr at telemetry-investments.com
Wed Mar 7 12:58:47 GMT 2007


Hi,

I'm not exactly sure how to interpret these messages, but the end result
was that bgpd lost a route to 204.166.106.0/24.  This is on linux 2.6.16
with a quagga 0.99 CVS snapshot from 20061130.  I restarted bgpd,
and the route was recovered.  Here are all the log messages from
the incident:

2007/03/06 05:36:39 BGP: 10.128.12.90 rcvd UPDATE about 204.166.106.0/24 -- withdrawn
2007/03/06 05:36:39 BGP: 10.128.12.90 rcvd UPDATE w/ attr: nexthop 10.128.12.90, origin ?, community 26585:112 26585:118, path 26
585
2007/03/06 05:36:39 BGP: 10.128.12.90 rcvd 204.166.106.0/24...duplicate ignored
2007/03/06 05:36:39 BGP: Zebra send: IPv4 route delete 204.166.106.0/24 nexthop 10.128.12.90 metric 0
2007/03/06 05:36:39 BGP: Zebra rcvd: IPv4 route add ospf 204.166.106.0/24 nexthop 192.168.21.24 metric 55
2007/03/06 05:36:39 BGP: Zebra rcvd: IPv4 route delete ospf 204.166.106.0/24 nexthop 192.168.21.24 metric 55
2007/03/06 05:36:41 BGP: Zebra rcvd: IPv4 route add ospf 204.166.106.0/24 nexthop 192.168.21.24 metric 55

I'm guessing that the route was dropped and then re-added almost immediately
(I'm not sure why, I don't know what was happening on the peer's side).
The "duplicate ignored" message looks a little suspicious.  Is that
a duplicate withdraw message that it's complaining about?  Or is it
the re-add message that's being ignored?

I think the 3 "Zebra rcvd" messages are irrelevant: just zebra telling bgpd
about another route to that prefix (known via ospf).

The route reappeared immediately when I restarted bgpd, so I'm guessing
there's a bug either on my side or theirs (perhaps they failed to tell
me that the route had been restored).

If anybody has any insight into these messages and an idea of where the problem
might be, please let me know.

Regards,
Andy



More information about the Quagga-dev mailing list