On Fri, Jun 29, 2007 at 11:12:15AM +0100, Stuart Henderson wrote: > On 2007/06/29 10:15, Jon Morby wrote: > > On 29 Jun 2007, at 08:47, Henning Brauer wrote: > > > >> * Jon Morby <[EMAIL PROTECTED]> [2007-06-29 02:56]: > >>> I've just updated one of our routers from an end of May snapshot to a > >>> Jun 28th snapshot and have noticed that we seem to be having problems > >>> with our multihop sessions since the upgrade. > >> > >> errr... I'm inlcined to say "impossible", since there weren't many > >> changes at all in bgpd since then, and nothing that remotely touches > >> nexthop verification. check your routes, something must be different. > >> bgpctl sh nex on both machines might give insight > >> > > > > I know ... whether it's just something that has now cropped up because it's > > the first time these several of these boxes have been rebooted in months ... > > > > The addition of nexthop qualify via bgp seems to have overcome things .. > > however the next hops should be learnt by ospf and are reachable (otherwise > > the bgp sessions wouldn't actually be up, which they are) > > Are the nexthops in subnets where you receive the same exact prefixes > by both BGP and OSPF? I have found ospfd sometimes doesn't overwrite > routes installed by bgpd. That's not new though.. >
ospfd will remove bgpd routes if the same network is distributed via bgp and ospf. This should work since some time now. So if you still can reproduce it I would like to know how because that is a bug. -- :wq Claudio
