[f-nsp] MLX throughput issues

[G B]

Wondering if you might have some imbalance in a LAG somewhere.  Where it is
hashing too much traffic to one link of a lag.  By default it uses the mac
address of the next layer 2 hop and traffic going to a gateway will all
hash to the same link.  Are there any LAGs involved?  Is there a major
imbalance of traffic on a LAG in the traffic path?

On Thu, Feb 12, 2015 at 9:43 PM, <nethub at gmail.com> wrote:

> We are only accepting about 300k IPv4 routes currently (we filter to reduce
> the table size).  We are on the multi-service-2 CAM partition profile and
> we
> have the system-max values for ip-route and ip-cache set to 445K.
>
> Also, we upgraded to 5.6f today to see if that would help but it did not
> change anything.
>
> CPU usage is very low across the board (under 10% use on everything), so if
> it is routing in software, it isn't causing a jump in CPU load.
>
>
> -----Original Message-----
> From: foundry-nsp [mailto:foundry-nsp-bounces at puck.nether.net] On Behalf
> Of
> Niels Bakker
> Sent: Thursday, February 12, 2015 8:38 PM
> To: foundry-nsp at puck.nether.net
> Subject: Re: [f-nsp] MLX throughput issues
>
> * nethub at gmail.com (nethub at gmail.com) [Fri 13 Feb 2015, 01:45 CET]:
> >As I stated in the first message, the Juniper EX3200 is a downstream
> >BGP customer that is single homed to our network, so it is on a
> >different ASN and the communication between my network and his network
> >is layer 3.
>
> Are you running that MLX with a full BGP table?  20 MB/sec sounds like
> you're forwarding packets over its CPU, perhaps because it ran out of CAM
> space.
>
>
>         -- Niels.
>
> --
> _______________________________________________
> foundry-nsp mailing list
> foundry-nsp at puck.nether.net
> http://puck.nether.net/mailman/listinfo/foundry-nsp
>
> _______________________________________________
> foundry-nsp mailing list
> foundry-nsp at puck.nether.net
> http://puck.nether.net/mailman/listinfo/foundry-nsp
>
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <https://puck.nether.net/pipermail/foundry-nsp/attachments/20150212/8e54ef5c/attachment.html>