On Mon, Oct 29, 2007 at 03:32:59PM -0700, Aaron Glenn wrote: > On 10/29/07, Claudio Jeker <[EMAIL PROTECTED]> wrote: > > > > The nexthop depends on a bgp route which is considered evil and therefor > > not allowed by default. Add "nexthop qualify via bgp" to the global config > > part and your setup should work again. > > Henning hit me with that clue-by-four privately, and that does make > perfect sense...but it's still not working. Below is with a refresh, > tried it with a hard clear as well. I have "nexthop quality via bgp" > properly situation in the global configuration area. > > At the risk of being hit by the clue-by-four again...here goes nothing: > > [EMAIL PROTECTED] bgpctl show rib nei 38.103.65.50 in > flags: * = Valid, > = Selected, I = via IBGP, A = Announced > origin: i = IGP, e = EGP, ? = Incomplete > > flags destination gateway lpref med aspath origin > 0.0.0.0/0 38.103.XXX.50 100 0 174 i > [EMAIL PROTECTED] cat /etc/bgpd.conf | grep nexthop > nexthop qualify via bgp > [EMAIL PROTECTED] bgpctl reload > reload request sent. > request processed > [EMAIL PROTECTED] bgpctl nei 38.104.XXX.37 refresh > request processed > [EMAIL PROTECTED] bgpctl show rib nei 38.103.65.50 in > flags: * = Valid, > = Selected, I = via IBGP, A = Announced > origin: i = IGP, e = EGP, ? = Incomplete > > flags destination gateway lpref med aspath origin > 0.0.0.0/0 38.103.XXX.50 100 0 174 i > [EMAIL PROTECTED]
please restart your bgpd process it could be that the nexthop qualify options are not correctly reloaded on config change. Maybe a bgpctl nei 38.104.XXX.37 clear would work as well but I'm not 100% sure about that. Also include the "bgpctl show nexthop" and "bgpctl show fib nexthop" output. -- :wq Claudio
