[j-nsp] BFD timers for OSPF - MX80 - 10.3R2.11
Mark Tinka
mtinka at globaltransit.net
Fri Mar 4 21:09:42 EST 2011
On Friday, March 04, 2011 06:27:27 am Doug Hanks wrote:
> We generally recommend 150ms to most customers. The
> added benefit of going from 150ms to 50ms is generally
> not enough to warrant the move.
We've been using 250ms with multipliers of 3 on short runs
and 5 on longer ones. Has been stable, except for cases when
CPU suddenly becomes busy, dropping BFD packets, e.g., when
inserting a compact flash card into a (software-based)
router.
We have both Cisco and Juniper, ranging from software- to
hardware-based platforms, with centralized and distributed
forwarding designs. The numbers above help us harmonize
things.
We're now settling on fairly modern kit (Juniper MX, Juniper
M120, Cisco ASR1000, Cisco ASR9000, Cisco CRS, e.t.c.), so
it may well be time to review these values if we can find a
common understanding across these boxes in how better they
implement BFD.
Cheers,
Mark.
-------------- next part --------------
A non-text attachment was scrubbed...
Name: signature.asc
Type: application/pgp-signature
Size: 836 bytes
Desc: This is a digitally signed message part.
URL: <https://puck.nether.net/pipermail/juniper-nsp/attachments/20110305/c010b4b8/attachment.pgp>
More information about the juniper-nsp
mailing list