<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:x="urn:schemas-microsoft-com:office:excel" 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 15 (filtered medium)">
<!--[if !mso]><style>v\:* {behavior:url(#default#VML);}
o\:* {behavior:url(#default#VML);}
w\:* {behavior:url(#default#VML);}
.shape {behavior:url(#default#VML);}
</style><![endif]--><style><!--
/* Font Definitions */
@font-face
{font-family:"Cambria Math";
panose-1:2 4 5 3 5 4 6 3 2 4;}
@font-face
{font-family:Calibri;
panose-1:2 15 5 2 2 2 4 3 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;}
span.EmailStyle17
{mso-style-type:personal-reply;
font-family:"Calibri",sans-serif;
color:#1F497D;}
.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="1027" />
</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">Hi Rodney,<o:p></o:p></span></p>
<p class="MsoNormal"><span style="font-size:11.0pt;font-family:"Calibri",sans-serif;color:#1F497D">Unfortunately, the MLX doesn’t support forwarding sFlow traffic out its management port; this limitation has to do with how the Management Module works. These
ports are closer to a server’s iLO port than an actual Ethernet port. <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">On the MLX, the MM doesn’t actually connect to the router’s data-plane fabric. Each line card runs a copy IronWare locally, so they behave like individual routers
for each card (this is what each LP has its own CPU, RAM, and Flash in addition to the Traffic Manager and Packet Processor chips). The Management Module’s job is to make sure table data stays in sync across all the cards, but its really not making the forwarding
decisions for each LP. <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">The MM talks to each LP through a separate internal network that only connects to the CPU in each LP; this is called the IPC Buss. Since the connections between
the MM and LPs aren’t part of the data-plane inside the box, there’s no way to get the sFlow data to the Management Module’s Ethernet port. Even if we could do this, we wouldn’t want to…too much sFlow traffic could overwhelm the IPC Buss and lock up the router.
<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">Although this architecture is a bit limiting for sFlow, it’s what allows someone to SSH into the MLX even if there’s a L2 loop or heavy load. It’s also why the
MLX can run at 100% capacity on the backplane and still have the CPUs run at 1%.<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">If your router is out of ports, I’d see if you can create a seprate management vlan to move sFlow data through. You can sonfigure sFlow to only forward traffic
out of a specific VE, so this would give you a way to keep the sFlow data away from existing traffic.<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">Wilbur
<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"><span style="font-size:11.0pt;font-family:"Calibri",sans-serif;color:#1F497D"><o:p> </o:p></span></p>
<div>
<div style="border:none;border-top:solid #E1E1E1 1.0pt;padding:3.0pt 0in 0in 0in">
<p class="MsoNormal"><b><span style="font-size:11.0pt;font-family:"Calibri",sans-serif">From:</span></b><span style="font-size:11.0pt;font-family:"Calibri",sans-serif"> foundry-nsp [mailto:foundry-nsp-bounces@puck.nether.net]
<b>On Behalf Of </b>i3D.net - Martijn Schmidt<br>
<b>Sent:</b> Thursday, May 21, 2015 12:16 PM<br>
<b>To:</b> foundry-nsp@puck.nether.net; tech@elecks.nl; i3D.net - Martijn Schmidt<br>
<b>Subject:</b> Re: [f-nsp] sflow through management interface<o:p></o:p></span></p>
</div>
</div>
<p class="MsoNormal"><o:p> </o:p></p>
<p class="MsoNormal" style="margin-bottom:12.0pt">Hi Rodney, <br>
<br>
Is there any special reason why you can't just send the sFlow samples to <br>
your collector server as in-line traffic? You don't need a dedicated <br>
interface for sFlow, it's not port mirroring. :-) <br>
<br>
Best regards, <br>
Martijn <br>
<br>
On 05/21/2015 08:07 PM, tech@<a href="mailto:elecks.nl">elecks.nl</a> wrote: <br>
<span style="color:black">> Hi, </span><br>
<span style="color:black">> </span><br>
<span style="color:black">> We use a NI-XMR-MR with NI-XMR-10GX4. </span><br>
<span style="color:black">> Has it pro/cons to run sFlow through the management interface (slow
</span><br>
<span style="color:black">> down?) ? </span><br>
<span style="color:black">> </span><br>
<span style="color:black">> We setting up sFLOW but we have no ports free only the mangement
</span><br>
<span style="color:black">> interface from the XMR-MR card. </span><br>
<span style="color:black">> </span><br>
<span style="color:black">> Regards, </span><br>
<span style="color:black">> </span><br>
<span style="color:black">> Rodney </span><br>
<span style="color:black">> </span><br>
<span style="color:black">> _______________________________________________ </span>
<br>
<span style="color:black">> foundry-nsp mailing list </span><br>
<span style="color:black">> foundry-nsp@<a href="mailto:puck.nether.net">puck.nether.net</a>
</span><br>
<span style="color:black">> <a href="http://puck.nether.net/mailman/listinfo/foundry-nsp">
http://puck.nether.net/mailman/listinfo/foundry-nsp</a> </span><br>
<br>
<br>
<br>
<span style="font-size:10.0pt;font-family:"Arial",sans-serif">Best regards,<br>
<br>
Martijn Schmidt<br>
<span style="color:black"><a href="http://www.i3D.net">http://www.i3D.net</a></span>
<br>
<br>
</span><!--[if gte vml 1]><v:shapetype id="_x0000_t75" coordsize="21600,21600" o:spt="75" o:preferrelative="t" path="m@4@5l@4@11@9@11@9@5xe" filled="f" stroked="f">
<v:stroke joinstyle="miter" />
<v:formulas>
<v:f eqn="if lineDrawn pixelLineWidth 0" />
<v:f eqn="sum @0 1 0" />
<v:f eqn="sum 0 0 @1" />
<v:f eqn="prod @2 1 2" />
<v:f eqn="prod @3 21600 pixelWidth" />
<v:f eqn="prod @3 21600 pixelHeight" />
<v:f eqn="sum @0 0 1" />
<v:f eqn="prod @6 1 2" />
<v:f eqn="prod @7 21600 pixelWidth" />
<v:f eqn="sum @8 21600 0" />
<v:f eqn="prod @7 21600 pixelHeight" />
<v:f eqn="sum @10 21600 0" />
</v:formulas>
<v:path o:extrusionok="f" gradientshapeok="t" o:connecttype="rect" />
<o:lock v:ext="edit" aspectratio="t" />
</v:shapetype><v:shape id="_x0000_s1026" type="#_x0000_t75" alt="" style='position:absolute;margin-left:0;margin-top:0;width:75pt;height:44.25pt;z-index:251658240;mso-wrap-distance-left:0;mso-wrap-distance-top:0;mso-wrap-distance-right:0;mso-wrap-distance-bottom:0;mso-position-horizontal:left;mso-position-horizontal-relative:text;mso-position-vertical-relative:line' o:allowoverlap="f">
<v:imagedata src="cid:image001.jpg@01D093C1.DB8B1200" o:title="5b9cf835.8e7c0883.jpg" />
<w:wrap type="square"/>
</v:shape><![endif]--><![if !vml]><img width="100" height="59" src="cid:image002.jpg@01D093C1.DB8B1200" align="left" v:shapes="_x0000_s1026"><![endif]><span style="font-size:10.0pt;font-family:"Arial",sans-serif">i3D.net
is a private company registered in The Netherlands at Meent 93b, Rotterdam. Registration #: 14074337 - VAT # NL 8202.63.886.B01. i3D.net is CDSA certified on Content Protection and Security and provides hosting from 16 global ISO-certified datacenters. We
are ranked in the Deloitte Technology Fast 500 EMEA as one of the fastest growing technology companies.
</span><o:p></o:p></p>
</div>
</body>
</html>