<html xmlns:v="urn:schemas-microsoft-com:vml" xmlns:o="urn:schemas-microsoft-com:office:office" xmlns:w="urn:schemas-microsoft-com:office:word" xmlns:m="http://schemas.microsoft.com/office/2004/12/omml" xmlns="http://www.w3.org/TR/REC-html40"><head><meta http-equiv=Content-Type content="text/html; charset=utf-8"><meta name=Generator content="Microsoft Word 14 (filtered medium)"><style><!--
/* Font Definitions */
@font-face
{font-family:Calibri;
panose-1:2 15 5 2 2 2 4 3 2 4;}
@font-face
{font-family:Tahoma;
panose-1:2 11 6 4 3 5 4 4 2 4;}
/* Style Definitions */
p.MsoNormal, li.MsoNormal, div.MsoNormal
{margin:0in;
margin-bottom:.0001pt;
font-size:12.0pt;
font-family:"Times New Roman","serif";}
a:link, span.MsoHyperlink
{mso-style-priority:99;
color:blue;
text-decoration:underline;}
a:visited, span.MsoHyperlinkFollowed
{mso-style-priority:99;
color:purple;
text-decoration:underline;}
p.MsoAcetate, li.MsoAcetate, div.MsoAcetate
{mso-style-priority:99;
mso-style-link:"Balloon Text Char";
margin:0in;
margin-bottom:.0001pt;
font-size:8.0pt;
font-family:"Tahoma","sans-serif";}
span.im
{mso-style-name:im;}
span.EmailStyle18
{mso-style-type:personal-reply;
font-family:"Calibri","sans-serif";
color:#1F497D;}
span.BalloonTextChar
{mso-style-name:"Balloon Text Char";
mso-style-priority:99;
mso-style-link:"Balloon Text";
font-family:"Tahoma","sans-serif";}
.MsoChpDefault
{mso-style-type:export-only;
font-family:"Calibri","sans-serif";}
@page WordSection1
{size:8.5in 11.0in;
margin:1.0in 1.0in 1.0in 1.0in;}
div.WordSection1
{page:WordSection1;}
--></style><!--[if gte mso 9]><xml>
<o:shapedefaults v:ext="edit" spidmax="1026" />
</xml><![endif]--><!--[if gte mso 9]><xml>
<o:shapelayout v:ext="edit">
<o:idmap v:ext="edit" data="1" />
</o:shapelayout></xml><![endif]--></head><body lang=EN-US link=blue vlink=purple><div class=WordSection1><p class=MsoNormal><span style='font-size:11.0pt;font-family:"Calibri","sans-serif";color:#1F497D'>We are not using LAG anywhere in our network.<o:p></o:p></span></p><p class=MsoNormal><span style='font-size:11.0pt;font-family:"Calibri","sans-serif";color:#1F497D'><o:p> </o:p></span></p><p class=MsoNormal><span style='font-size:11.0pt;font-family:"Calibri","sans-serif";color:#1F497D'><o:p> </o:p></span></p><p class=MsoNormal><b><span style='font-size:10.0pt;font-family:"Tahoma","sans-serif"'>From:</span></b><span style='font-size:10.0pt;font-family:"Tahoma","sans-serif"'> G B [mailto:georgeb@gmail.com] <br><b>Sent:</b> Friday, February 13, 2015 1:16 AM<br><b>To:</b> nethub@gmail.com<br><b>Cc:</b> Niels Bakker; foundry-nsp<br><b>Subject:</b> Re: [f-nsp] MLX throughput issues<o:p></o:p></span></p><p class=MsoNormal><o:p> </o:p></p><div><p class=MsoNormal>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?<o:p></o:p></p></div><div><p class=MsoNormal><o:p> </o:p></p><div><p class=MsoNormal>On Thu, Feb 12, 2015 at 9:43 PM, <<a href="mailto:nethub@gmail.com" target="_blank">nethub@gmail.com</a>> wrote:<o:p></o:p></p><p class=MsoNormal>We are only accepting about 300k IPv4 routes currently (we filter to reduce<br>the table size). We are on the multi-service-2 CAM partition profile and we<br>have the system-max values for ip-route and ip-cache set to 445K.<br><br>Also, we upgraded to 5.6f today to see if that would help but it did not<br>change anything.<br><br>CPU usage is very low across the board (under 10% use on everything), so if<br>it is routing in software, it isn't causing a jump in CPU load.<br><br><br><span class=im>-----Original Message-----</span><br><span class=im>From: foundry-nsp [mailto:<a href="mailto:foundry-nsp-bounces@puck.nether.net">foundry-nsp-bounces@puck.nether.net</a>] On Behalf Of</span><o:p></o:p></p><div><div><p class=MsoNormal>Niels Bakker<br>Sent: Thursday, February 12, 2015 8:38 PM<br>To: <a href="mailto:foundry-nsp@puck.nether.net">foundry-nsp@puck.nether.net</a><br>Subject: Re: [f-nsp] MLX throughput issues<br><br>* <a href="mailto:nethub@gmail.com">nethub@gmail.com</a> (<a href="mailto:nethub@gmail.com">nethub@gmail.com</a>) [Fri 13 Feb 2015, 01:45 CET]:<br>>As I stated in the first message, the Juniper EX3200 is a downstream<br>>BGP customer that is single homed to our network, so it is on a<br>>different ASN and the communication between my network and his network<br>>is layer 3.<br><br>Are you running that MLX with a full BGP table? 20 MB/sec sounds like<br>you're forwarding packets over its CPU, perhaps because it ran out of CAM<br>space.<br><br><br> -- Niels.<br><br>--<br>_______________________________________________<br>foundry-nsp mailing list<br><a href="mailto:foundry-nsp@puck.nether.net">foundry-nsp@puck.nether.net</a><br><a href="http://puck.nether.net/mailman/listinfo/foundry-nsp" target="_blank">http://puck.nether.net/mailman/listinfo/foundry-nsp</a><br><br>_______________________________________________<br>foundry-nsp mailing list<br><a href="mailto:foundry-nsp@puck.nether.net">foundry-nsp@puck.nether.net</a><br><a href="http://puck.nether.net/mailman/listinfo/foundry-nsp" target="_blank">http://puck.nether.net/mailman/listinfo/foundry-nsp</a><o:p></o:p></p></div></div></div><p class=MsoNormal><o:p> </o:p></p></div></div></body></html>