[j-nsp] BFD/IS-IS wait to re-establish adjacency after failure tweak knob?

[Alan Gravett]

If the interface is ethernet you may want to consider ethernet OAM options
LFM or CFM
depending on the topology.

On Thu, May 19, 2016 at 12:45 PM, James Bensley <jwbensley at gmail.com> wrote:

> On 19 May 2016 at 10:53, Mark Tinka <mark.tinka at seacom.mu> wrote:
> >
> >
> > On 19/May/16 11:49, James Bensley wrote:
> >
> >> In Cisco land we have the interface command "carrier-delay", for Junos
> >> (this scenario) can the OP not use some variant of "set interfaces
> >> xe-0/0/1 hold-time up 5000" ?
> >
> > OP says the issue is remote.
> >
> > Local link to provider's switch does not fail, and appears to have no
> > way of relaying upstream outages to the OP's port.
>
> Ah OK I missread, although in the case the physical interfaces is up
> to the carriers switch but the far end is down, BFD should keep the
> OP's interface down.
>
> From the original post:
>
> > However, the IS-IS adjacency is coming up more quickly than desired.
> > On average, it is coming up 7-8 seconds later. Unfortunately, the L2
> > link is still unstable, so the BFD causes the session to drop again
> > fairly quickly. This causes a lot of flapping that I do not need.
>
> OK so assuming BFD is detecting the link as recovered then I think the
> only options are dampening or increasing the carrier delay / hold
> time.
>
> Cheers,
> James,
> _______________________________________________
> juniper-nsp mailing list juniper-nsp at puck.nether.net
> https://puck.nether.net/mailman/listinfo/juniper-nsp
>