Re: [j-nsp] KRT queue stalls fixed in 11.4R8?

2013-06-28 Thread Nick Ryce
It doesn't appear to mention anything about sampling. I assume this is the fix for the BGP convergence issues per RAS's Nanog presso http://www.nanog.org/meetings/nanog57/presentations/Tuesday/tue.lightning2. steenbergen.juniper-slowfib.pdf Nick -- Nick Ryce Fluency Communications Ltd. e.

Re: [j-nsp] KRT queue stalls fixed in 11.4R8?

2013-06-28 Thread Richard Hesse
Ah. I was thinking of the bug referenced in KB13463. http://kb.juniper.net/InfoCenter/index?page=contentid=KB13463 That RPD/KRT stall is triggered by sampling and still exists in 11.4R8. -richard On Fri, Jun 28, 2013 at 2:29 AM, Nick Ryce n...@fluency.net.uk wrote: It doesn't appear to

Re: [j-nsp] KRT queue stalls fixed in 11.4R8?

2013-06-27 Thread Richard Hesse
Is this the one that's exacerbated by sampling? If so, it's still not fixed in 11.4R8. -richard On Mon, Jun 24, 2013 at 3:12 PM, Sebastian Wiesinger juniper-...@ml.karotte.org wrote: * Grzegorz Janoszka grzeg...@janoszka.pl [2013-06-24 21:57]: On 24-06-13 21:07, Rob Foehl wrote:

[j-nsp] KRT queue stalls fixed in 11.4R8?

2013-06-24 Thread Rob Foehl
According to the release notes for 11.4R8, the KRT queue stall issue (PR836197) has been marked as resolved. Has anyone had a chance to confirm this on a suitably session-heavy MX? -Rob ___ juniper-nsp mailing list juniper-nsp@puck.nether.net

Re: [j-nsp] KRT queue stalls fixed in 11.4R8?

2013-06-24 Thread Grzegorz Janoszka
On 24-06-13 21:07, Rob Foehl wrote: According to the release notes for 11.4R8, the KRT queue stall issue (PR836197) has been marked as resolved. Has anyone had a chance to confirm this on a suitably session-heavy MX? You still have to wait a while for all the prefixes, but at least there is

Re: [j-nsp] KRT queue stalls fixed in 11.4R8?

2013-06-24 Thread Sebastian Wiesinger
* Grzegorz Janoszka grzeg...@janoszka.pl [2013-06-24 21:57]: On 24-06-13 21:07, Rob Foehl wrote: According to the release notes for 11.4R8, the KRT queue stall issue (PR836197) has been marked as resolved. Has anyone had a chance to confirm this on a suitably session-heavy MX? You still