[c-nsp] UDLD - why is default 60 seconds?

Hank Nussbacher hank at efes.iucc.ac.il
Fri Feb 24 02:15:36 EST 2006


On Thu, 23 Feb 2006, Saku Ytti wrote:

> On (2006-02-23 18:32 +0200), Hank Nussbacher wrote:
>
> > <http://www.cisco.com/en/US/products/hw/routers/ps368/products_configuration_guide_chapter09186a0080160ecf.html>
> >
> > Why is the default probe message time 60 seconds and in addition one can
> > only go as low as 7 seconds?  If a GE port suddenly becomes
> > unidirectional, I would like to know about in 1-2 seconds and not after 7
> > seconds, so that the link is forced down and OSPF turns to an alternate
> > path.  Or am I missing something?
>
>  Valid question, which I don't have answer to, I agree they're quite
> conservative. But I'd suggest that you'll solve your rapid IGP
> livelyness detection with BFD instead, UDLD only helps in very spesific
> problem, which should happen extremely rarely.
>
>  Also you may want to complement UDLD with STP loopguard, to cover
> another corner case (mainly STP software issues).

BFD only works on 12.2(18)SXE, 12.0(31)S, 12.4(4)T, and 12.0(32)S.  The
remote systems are all 12.4(3b) and the core is 12.2(18)SXE.  So BFD is
not a solution and UDLD doesn't appear to be supported either in 12.4 so
what other solution would people recommend to determine failed P-2-P GE
links?

Thanks,
Hank

>
> >
> > Thanks,
> > Hank
> > _______________________________________________
> > cisco-nsp mailing list  cisco-nsp at puck.nether.net
> > https://puck.nether.net/mailman/listinfo/cisco-nsp
> > archive at http://puck.nether.net/pipermail/cisco-nsp/
> >
>
> --
>   ++ytti
> _______________________________________________
> cisco-nsp mailing list  cisco-nsp at puck.nether.net
> https://puck.nether.net/mailman/listinfo/cisco-nsp
> archive at http://puck.nether.net/pipermail/cisco-nsp/
>
>  +++++++++++++++++++++++++++++++++++++++++++
>  This Mail Was Scanned By Mail-seCure System
>  at the Tel-Aviv University CC.
>


More information about the cisco-nsp mailing list