<div dir="ltr"><div>Thanks Roland</div><div><br></div>><span style="font-family:arial,sans-serif;font-size:12.727272033691406px">NetFlow v9 is necessary for IPv6 and for MPLS support - don't know if those apply in your environment.</span><div>
<span style="font-family:arial,sans-serif;font-size:12.727272033691406px">Not at the moment. </span></div><div><span style="font-family:arial,sans-serif;font-size:12.727272033691406px"><br></span></div><div><span style="font-family:arial,sans-serif;font-size:12.727272033691406px">>P</span><span style="font-family:arial,sans-serif;font-size:12.727272033691406px">erforming management tasks and exporting flow telemetry inline in your production network runs the risk of losing the ability to control and to observe your network during a network partition event, network congestion event (DDoS, etc.), and so forth.</span></div>
<div><span style="font-family:arial,sans-serif;font-size:12.727272033691406px"><br></span></div><div><font face="arial, sans-serif">Thanks for this. The collector is on a separate interface/subnet from the production but no OOB access yet on it.</font></div>
<div><font face="arial, sans-serif"><br></font></div><div><font face="arial, sans-serif">></font><span style="font-family:arial,sans-serif;font-size:12.727272033691406px">Why only one interface? You want to get both inbound and outbound traffic, yes?</span></div>
<div><font face="arial, sans-serif">For now, I only require to monitor the internet interface and just to see if the SRX650 can handle it.</font></div><div><font face="arial, sans-serif"><br></font></div><div><font face="arial, sans-serif"><br>
</font></div><div><font face="arial, sans-serif"><br></font></div><div><font face="arial, sans-serif"><br></font></div><div><font face="arial, sans-serif"><br></font></div></div><div class="gmail_extra"><br><br><div class="gmail_quote">
On Thu, May 8, 2014 at 8:46 PM, Dobbins, Roland <span dir="ltr"><<a href="mailto:rdobbins@arbor.net" target="_blank">rdobbins@arbor.net</a>></span> wrote:<br><blockquote class="gmail_quote" style="margin:0 0 0 .8ex;border-left:1px #ccc solid;padding-left:1ex">
<div class=""><br>
On May 8, 2014, at 5:22 PM, Mark Anthony Delfin <<a href="mailto:mark@delfin.me">mark@delfin.me</a>> wrote:<br>
<br>
> 4x GE Base PIC and 16x GE gPIM<br>
<br>
</div>My understanding is that in order to get NetFlow v9, and to get a lower sampling ratio, you need a services PIC (I'm not a Juniper person, clue welcome!).<br>
<br>
NetFlow v9 is necessary for IPv6 and for MPLS support - don't know if those apply in your environment.<br>
<div class=""><br>
> ManageEngine Netflow (currently on trial version)<br>
<br>
</div>What's the flows-per-second rating of the ManageEngine box?<br>
<br>
> None<br>
<br>
You should have OOB connectivity for lots of reasons, including flow telemetry export. Performing management tasks and exporting flow telemetry inline in your production network runs the risk of losing the ability to control and to observe your network during a network partition event, network congestion event (DDoS, etc.), and so forth.<br>
<div class=""><br>
> I plan to enable it on one interface average 50 mbps peaking at 200 mbps<br>
<br>
</div>Why only one interface? You want to get both inbound and outbound traffic, yes?<br>
<div class="HOEnZb"><div class="h5"><br>
-----------------------------------------------------------------------<br>
Roland Dobbins <<a href="mailto:rdobbins@arbor.net">rdobbins@arbor.net</a>> // <<a href="http://www.arbornetworks.com" target="_blank">http://www.arbornetworks.com</a>><br>
<br>
Luck is the residue of opportunity and design.<br>
<br>
-- John Milton<br>
<br>
_______________________________________________<br>
AusNOG mailing list<br>
<a href="mailto:AusNOG@lists.ausnog.net">AusNOG@lists.ausnog.net</a><br>
<a href="http://lists.ausnog.net/mailman/listinfo/ausnog" target="_blank">http://lists.ausnog.net/mailman/listinfo/ausnog</a><br>
</div></div></blockquote></div><br></div>