[quagga-users 14568] Re: iBGP not propagating v6 route problem (again)
Mark Kamichoff <prox-1QuQYt+lk/[email protected]>
| Newsgroups | gmane.network.quagga.user |
|---|---|
| Message-ID | <[email protected]> |
On Wed, Dec 21, 2016 at 10:44:34PM +0000, Paul Thornton wrote: > > https://bugzilla.quagga.net/show_bug.cgi?id=870 > > [..snip..] > > I just read through that bug report - and it looks like I'm seeing almost > exactly the same thing, except for me it is a route learned from a peer that > the box isn't passing on. So we have your case (network statement) and mine > (learned route from elsewhere) - it does seem that it is the iBGP > advertising that is at fault. I'm now seeing your exact issue where bgpd is not passing on a route that's learned elsewhere, too. > I also have a consistently >0 OutQ on the peers that are not being sent the > prefix. > > The nexthop cache, however, looks sane: Interesting, maybe that's a red herring. > I also have bgp debugging enabled. This is what I see in the log when the > iBGP peer is brought up - no sign of any attempt to actually send an update > to the iBGP peer. I'm not sure about that 'NH unresolved' message - it may > or may not be related. > > 2016/12/19 11:55:39 BGP: %ADJCHANGE: neighbor 2001:1420::7e Up > 2016/12/19 11:55:39 BGP: 2001:1420::7e rcvd UPDATE w/ attr: , origin i, > mp_nexthop 2001:1420::7e, localpref 100, path > 2016/12/19 11:55:39 BGP: 2001:1420::7e rcvd ::/0 > 2016/12/19 11:55:39 BGP: bgp_update_main(0.0.0.0): NH unresolved > 2016/12/19 11:55:39 BGP: parse nexthop update(2001:1420:16:2::1/128): > metric=0, #nexthop=0 > 2016/12/19 11:55:39 BGP: parse nexthop update(2001:1420:16:2::1/128): > metric=1, #nexthop=1 > 2016/12/19 11:55:39 BGP: Zebra send: IPv6 route add ::/0 nexthop > 2001:1420:16:2::1 metric 0 tag 0 > 2016/12/19 11:55:58 BGP: 2001:1420:16:3::1 send UPDATE ::/0 My logs are similar - no help here. > I do have this currently and reliably broken on a lab environment router, so > can do additional debugging etc. if someone wants to make suggestions. Same here! Although, I'm wondering if I restart bgpd enough, it'll go away. I have a feeling it's something circumstantial but this is pure speculation. - Mark -- Mark Kamichoff prox-1QuQYt+lk/[email protected] http://www.prolixium.com/