<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=us-ascii"><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;}
@font-face
{font-family:Consolas;
panose-1:2 11 6 9 2 2 4 3 2 4;}
@font-face
{font-family:"Times New Roman \, serif";
panose-1:0 0 0 0 0 0 0 0 0 0;}
/* Style Definitions */
p.MsoNormal, li.MsoNormal, div.MsoNormal
{margin:0in;
margin-bottom:.0001pt;
font-size:11.0pt;
font-family:"Calibri","sans-serif";
color:black;}
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;}
pre
{mso-style-priority:99;
mso-style-link:"HTML Preformatted Char";
margin:0in;
margin-bottom:.0001pt;
font-size:10.0pt;
font-family:"Courier New";
color:black;}
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";
color:black;}
span.HTMLPreformattedChar
{mso-style-name:"HTML Preformatted Char";
mso-style-priority:99;
mso-style-link:"HTML Preformatted";
font-family:Consolas;
color:black;}
span.EmailStyle19
{mso-style-type:personal;
font-family:"Calibri","sans-serif";
color:windowtext;}
span.EmailStyle20
{mso-style-type:personal;
font-family:"Calibri","sans-serif";
color:#1F497D;}
span.EmailStyle21
{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";
color:black;}
.MsoChpDefault
{mso-style-type:export-only;
font-size:10.0pt;}
@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 bgcolor=white lang=EN-US link=blue vlink=purple><div class=WordSection1><p class=MsoNormal><span style='color:#1F497D'>We have three switch fabrics installed, all are under 1% utilized.<o:p></o:p></span></p><p class=MsoNormal><span style='color:#1F497D'><o:p> </o:p></span></p><p class=MsoNormal><span style='color:#1F497D'><o:p> </o:p></span></p><div><div style='border:none;border-top:solid #B5C4DF 1.0pt;padding:3.0pt 0in 0in 0in'><p class=MsoNormal><b><span style='font-size:10.0pt;font-family:"Tahoma","sans-serif";color:windowtext'>From:</span></b><span style='font-size:10.0pt;font-family:"Tahoma","sans-serif";color:windowtext'> Jeroen Wunnink | Hibernia Networks [mailto:jeroen.wunnink@atrato.com] <br><b>Sent:</b> Friday, February 13, 2015 12:27 PM<br><b>To:</b> nethub@gmail.com; 'Jeroen Wunnink | Hibernia Networks'<br><b>Subject:</b> Re: [f-nsp] MLX throughput issues<o:p></o:p></span></p></div></div><p class=MsoNormal><o:p> </o:p></p><div><p class=MsoNormal>How many switchfabrics do you have in that MLX and how high is the utilization on them<br><br>On 13/02/15 18:12, <a href="mailto:nethub@gmail.com">nethub@gmail.com</a> wrote:<o:p></o:p></p></div><blockquote style='margin-top:5.0pt;margin-bottom:5.0pt'><p class=MsoNormal><span style='color:#1F497D'>We also tested with a spare Quanta LB4M we have and are seeing about the same speeds as we are seeing with the FLS648 (around 20MB/s or 160Mbps).</span><o:p></o:p></p><p class=MsoNormal><span style='color:#1F497D'> </span><o:p></o:p></p><p class=MsoNormal><span style='color:#1F497D'>I also reduced the number of routes we are accepting down to about 189K and that did not make a difference.</span><o:p></o:p></p><p class=MsoNormal><span style='color:#1F497D'> </span><o:p></o:p></p><p class=MsoNormal><span style='color:#1F497D'> </span><o:p></o:p></p><div><div style='border:none;border-top:solid #B5C4DF 1.0pt;padding:3.0pt 0in 0in 0in'><p class=MsoNormal><b><span style='font-size:10.0pt;font-family:"Tahoma","sans-serif";color:windowtext'>From:</span></b><span style='font-size:10.0pt;font-family:"Tahoma","sans-serif";color:windowtext'> foundry-nsp [<a href="mailto:foundry-nsp-bounces@puck.nether.net">mailto:foundry-nsp-bounces@puck.nether.net</a>] <b>On Behalf Of </b>Jeroen Wunnink | Hibernia Networks<br><b>Sent:</b> Friday, February 13, 2015 3:35 AM<br><b>To:</b> <a href="mailto:foundry-nsp@puck.nether.net">foundry-nsp@puck.nether.net</a><br><b>Subject:</b> Re: [f-nsp] MLX throughput issues</span><o:p></o:p></p></div></div><p class=MsoNormal> <o:p></o:p></p><div><p class=MsoNormal>The FLS switches do something weird with packets. I've noticed they somehow interfere with changing the MSS window size dynamically, resulting in destinations further away having very poor speed results compared to destinations close by. <br><br>We got rid of those a while ago.<br><br><br>On 12/02/15 17:37, <a href="mailto:nethub@gmail.com">nethub@gmail.com</a> wrote:<o:p></o:p></p></div><blockquote style='margin-top:5.0pt;margin-bottom:5.0pt'><p class=MsoNormal>We are having a strange issue on our MLX running code 5.6.00c. We are encountering some throughput issues that seem to be randomly impacting specific networks.<o:p></o:p></p><p class=MsoNormal> <o:p></o:p></p><p class=MsoNormal>We use the MLX to handle both external BGP and internal VLAN routing. Each FLS648 is used for Layer 2 VLANs only.<o:p></o:p></p><p class=MsoNormal> <o:p></o:p></p><p class=MsoNormal>From a server connected by 1 Gbps uplink to a Foundry FLS648 switch, which is then connected to the MLX on a 10 Gbps port, running a speed test to an external network is getting 20MB/s.<o:p></o:p></p><p class=MsoNormal> <o:p></o:p></p><p class=MsoNormal>Connecting the same server directly to the MLX is getting 70MB/s.<o:p></o:p></p><p class=MsoNormal> <o:p></o:p></p><p class=MsoNormal>Connecting the same server to one of my customer's Juniper EX3200 (which BGP peers with the MLX) also gets 70MB/s.<o:p></o:p></p><p class=MsoNormal> <o:p></o:p></p><p class=MsoNormal>Testing to another external network, all three scenarios get 110MB/s.<o:p></o:p></p><p class=MsoNormal> <o:p></o:p></p><p class=MsoNormal>The path to both test network locations goes through the same IP transit provider.<o:p></o:p></p><p class=MsoNormal> <o:p></o:p></p><p class=MsoNormal>We are running NI-MLX-MR with 2GB RAM, NI-MLX-10Gx4 connect to the Foundry FLS648 by XFP-10G-LR, NI-MLX-1Gx20-GC was used for directly connecting the server. A separate NI-MLX-10Gx4 connects to our upstream BGP providers. Customer’s Juniper EX3200 connects to the same NI-MLX-10Gx4 as the FLS648. We take default routes plus full tables from three providers by BGP, but filter out most of the routes.<o:p></o:p></p><p class=MsoNormal> <o:p></o:p></p><p class=MsoNormal>The fiber and optics on everything look fine. CPU usage is less than 10% on the MLX and all line cards and CPU usage at 1% on the FLS648. ARP table on the MLX is about 12K, and BGP table is about 308K routes.<o:p></o:p></p><p class=MsoNormal> <o:p></o:p></p><p class=MsoNormal>Any assistance would be appreciated. I suspect there is a setting that we’re missing on the MLX that is causing this issue.<o:p></o:p></p><p class=MsoNormal><span style='font-size:12.0pt;font-family:"Times New Roman , serif","serif"'><br><br><br><br></span><o:p></o:p></p><pre>_______________________________________________<o:p></o:p></pre><pre>foundry-nsp mailing list<o:p></o:p></pre><pre><a href="mailto:foundry-nsp@puck.nether.net">foundry-nsp@puck.nether.net</a><o:p></o:p></pre><pre><a href="http://puck.nether.net/mailman/listinfo/foundry-nsp">http://puck.nether.net/mailman/listinfo/foundry-nsp</a><o:p></o:p></pre></blockquote><p class=MsoNormal><span style='font-size:12.0pt;font-family:"Times New Roman , serif","serif"'><br><br><br><br></span><o:p></o:p></p><pre>-- <o:p></o:p></pre><pre> <o:p></o:p></pre><pre>Jeroen Wunnink<o:p></o:p></pre><pre>IP NOC Manager - Hibernia Networks<o:p></o:p></pre><pre>Main numbers (Ext: 1011): USA +1.908.516.4200 | UK +44.1704.322.300 <o:p></o:p></pre><pre>Netherlands +31.208.200.622 | 24/7 IP NOC Phone: +31.20.82.00.623<o:p></o:p></pre><pre><a href="mailto:jeroen.wunnink@hibernianetworks.com">jeroen.wunnink@hibernianetworks.com</a><o:p></o:p></pre><pre><a href="http://www.hibernianetworks.com">www.hibernianetworks.com</a><o:p></o:p></pre></blockquote><p class=MsoNormal><span style='font-size:12.0pt;font-family:"Times New Roman","serif"'><br><br><br><o:p></o:p></span></p><pre>-- <o:p></o:p></pre><pre><o:p> </o:p></pre><pre>Jeroen Wunnink<o:p></o:p></pre><pre>IP NOC Manager - Hibernia Networks<o:p></o:p></pre><pre>Main numbers (Ext: 1011): USA +1.908.516.4200 | UK +44.1704.322.300 <o:p></o:p></pre><pre>Netherlands +31.208.200.622 | 24/7 IP NOC Phone: +31.20.82.00.623<o:p></o:p></pre><pre><a href="mailto:jeroen.wunnink@hibernianetworks.com">jeroen.wunnink@hibernianetworks.com</a><o:p></o:p></pre><pre><a href="http://www.hibernianetworks.com">www.hibernianetworks.com</a><o:p></o:p></pre></div></body></html>