On Fri, Jan 26, 2007 at 01:11:52PM +0100, Toni Mueller wrote: > Hi, > > On Fri, 26.01.2007 at 11:45:36 +0100, Henning Brauer <[EMAIL PROTECTED]> > wrote: > > IF, and only IF, the nexthops are valid and reachable. > > bgpctl show nexthop > > is your friend. > > well, it turns out that the machine can't see their neighbours too > well. The iBGP peer isn't listed, and the upstream is now marked > "invalid" although they can both be reached via static routes, are up, > and the session (in 'bgpctl show') to the iBGP peer was, and is, up at > all times. The iBGP peer is even on the same LAN segment, and the > summary output says that the session to this peer is now up for 2+ > hours (I restarted it this morning, it was well over a week old > before). > > What does "invalid" in this case mean? I have a multihop session to > that router, and restarting the session, I get all ~204k routes again > from said peer... As per RFC1105 these routes should be deleted from > the routing table, but I can't see that happening either. > > If it makes a difference, I have softreconfig on in both directions and > for all peers to be able to change filter rules on the fly w/o > restarting any sessions (and thus cause route flap). > >
You probably need to either add a static route for the router or add a nexthop qualify via default or nexthop qualify via bgp to your config. Since 4.0 bgpd will only use nexthops that reachable via static routes or routes added by other routing daemons like ospfd(8). -- :wq Claudio
