[j-nsp] bfd = busted failure detection :)

Ross Vandegrift ross at kallisti.us
Tue Dec 8 19:54:49 EST 2009


On Fri, Dec 04, 2009 at 02:40:14PM -0600, Richard A Steenbergen wrote:
> FYI I found the root problem and hereby take back any comments impugning
> BFD's reputation. It turns out there actually WAS some kind of pfe bug
> which was causing intermittent blackholing of traffic for a few seconds
> at a time at seemingly random intervals several times a day. Ping from
> the affected devices didn't catch the issue becuase of the re->pfe
> forwarding path, only traffic routed entirely via pfe was being
> affected. BFD was actually doing its job and detected the failures that
> were too short to be noticed by normal routing protocols. I discovered
> the issue on several MX960s (mostly running 9.2R4, but one pair was
> running 9.4R3), and upgrading them to 9.5R3 seems to solve it (or
> perhaps it was just the pfe rstart that did it, remains to be seen).

Is there a PR number for this issue?  Sounds like it could be a drag.

Ross

-- 
Ross Vandegrift
ross at kallisti.us

"If the fight gets hot, the songs get hotter.  If the going gets tough,
the songs get tougher."
	--Woody Guthrie
-------------- next part --------------
A non-text attachment was scrubbed...
Name: not available
Type: application/pgp-signature
Size: 197 bytes
Desc: Digital signature
URL: <https://puck.nether.net/pipermail/juniper-nsp/attachments/20091208/c22f9700/attachment.bin>


More information about the juniper-nsp mailing list