[j-nsp] Krt queue issues

[Jonathan Lassoff]

It's sadly a known issue for which there is no easy fix.

When turning up new adjacencies, I generally hack in policy to avoid
announcing any routes at first until the box has had a while to learn and
pick up the tables, only then do I start announcing space and sinking
traffic through the router.

However, this does little help after an unexpected reboot.

--j

On Mon, Oct 1, 2012 at 5:26 AM, Darren O'Connor <darrenoc at outlook.com>wrote:

> Hi Saku.
>
> Indeed, this is the worst thing this router can do. I have redundant
> routers sitting there doing absolutely nothing as this router's
> control-plane says everything is fine.
>
> Juniper aren't really telling me anything, only that the links I've shows
> are 'corner cases' - no comment on the comment I got from JTAC.
>
> I do happen to have a spare Brocade XMR that I might just use instead.
>
> Juniper should just come out straight.
>
> > Date: Mon, 1 Oct 2012 15:15:39 +0300
> > From: saku at ytti.fi
> > To: juniper-nsp at puck.nether.net
> > Subject: Re: [j-nsp] Krt queue issues
> >
> > On (2012-10-01 08:38 +0100), Darren O'Connor wrote:
> >
> > Hi Darren,
> >
> > > So to me this means this problem is a software issue, not hardware.
> And it's not yet fixed. Hence spending the money on a new box would be of
> no use.
> >
> > Certainly not hardware issue, cisco boxes running significantly lower
> > performance RPs wont do this (well at this scale). Like crappy old
> > sup720-3bxl.
> >
> > IMHO this is absolutely worst thing router can do, not have RIB and FIB
> in
> > sync, since then all your investments in redundant network was lost. You
> > have working backup paths, but they cannot be used due to your router
> > sucking traffic it cannot handle yet.
> > If they can't fix the FIB programming, they should also stop accepting
> > routes from routing protocols, even if BGP convergence takes 30min, it's
> > much more preferable to FIB/RIB desync.
> >
> > > This particular router for me will be connected to a peering point so
> will have around 200 neighbours, as well as a transit link with a full BGP
> table.
> >
> > JunOS is exceedingly poorly performing platform in control-plane,
> > especially with PPC control-plane. 200 neighbours on MX80 does not sound
> > like a good idea right now. You probably should have gone with bigger MX
> > where you'd get XEON.
> >
> > MX80 has faster CPU than RSP720, but RSP720 runs circles around MX80 :/
> > --
> >   ++ytti
> > _______________________________________________
> > juniper-nsp mailing list juniper-nsp at puck.nether.net
> > https://puck.nether.net/mailman/listinfo/juniper-nsp
>
> _______________________________________________
> juniper-nsp mailing list juniper-nsp at puck.nether.net
> https://puck.nether.net/mailman/listinfo/juniper-nsp
>