[j-nsp] bfd = busted failure detection :)
David Ball
davidtball at gmail.com
Wed Dec 9 11:13:28 EST 2009
Do your KRT queues eventually flush though? Is it just a slow
control->fwding thing when large route updates occur? I've done 2
upgrades in as many years to resolve a KRT related bug, but that
resulted in the queue NEVER emptying. It's apparently related to a
residual variable being set after an RPD restart (caused by another
bug) resulting in a kernel/rpd inconsistency. I'm told mine is
resolved in 9.5R3 (PR291407), but I got nervous when I read Richard's
earlier post.
David
2009/12/9 Mark Tinka <mtinka at globaltransit.net>:
> On Wednesday 09 December 2009 05:40:00 pm Richard A
> Steenbergen wrote:
>
>> Nothing current, it ended up spread out over a bunch of
>> cases which all got closed with no real resolution to
>> the root problem. Everyone I've talked to at Juniper
>> knows that the problem exists, they just don't know why,
>> and I don't know of any currently ongoing effort to fix
>> it. Maybe it's time we all get organized and start
>> raising the attention level for this very serious issue.
>
> I'd be willing to help if we can offline this to a
> reproduction in my lab.
>
> I have a case that will have been open for 1 year, if
> February 2010 comes and we still haven't fixed it. So I know
> what it's like :-).
>
> Cheers,
>
> Mark.
>
> _______________________________________________
> juniper-nsp mailing list juniper-nsp at puck.nether.net
> https://puck.nether.net/mailman/listinfo/juniper-nsp
>
More information about the juniper-nsp
mailing list