[j-nsp] eBGP neighbor link failure detection

[Andy Litzinger]

Hi Chris,
 yes, i am taking full routes from this neighbor.

is there any way to reduce the time it takes to handle the updates?  if i
wanted to test this behavior in my lab, what would i want to watch?
(logs/traceoptions)

i don't think I've seen this behavior during scheduled maintenance- for
example during times when i've deactivated the neighbor config.  Am I
correct in thinking this is because in this scenario even though the RE is
taking awhile to remove the routes from the FIB the actual next hop router
is still available and thus the routes are still valid?

-andy


On Thu, Mar 13, 2014 at 3:54 PM, Chris Adams <cma at cmadams.net> wrote:

> Once upon a time, Andy Litzinger <andy.litzinger.lists at gmail.com> said:
> > what surprised me is that it looks like routes toward that provider were
> > not immediately removed from my routing table.  Instead i see evidence of
> > blackholing for almost 3 minutes.
>
> Are you taking full routes from this neighbor?  It takes a while for the
> routing engine to send updates to remove/replace 200k+ prefixes to the
> forwarding engine.
>
> --
> Chris Adams <cma at cmadams.net>
> _______________________________________________
> juniper-nsp mailing list juniper-nsp at puck.nether.net
> https://puck.nether.net/mailman/listinfo/juniper-nsp
>