[j-nsp] Netflow/Jflow

[Scott Granados]

Hi, it’s been a while so if I’m wrong I’m happy to be corrected but in your case you’d sample on the input side of each of the individual interfaces facing the customer.

The load shouldn’t be an issue providing you’re running later code with out the JFlow related bugs such as the PR (I don’t recall the number) for the bug where flow processing blocked the PFE from accepting routes from the RE.  These were pre 13.2 on the 480 if memory serves but this is going back in the haze a bit so feel free to sanity check.  Inline JFlow does not have the same impact to processing of other platforms so you can be less concerned. 
	The other thing to remember is that all sampling takes place at 1:1 and the sampling rate knob is more of a scaling factor rather than actually adjusting the rate of sampling.  Setting this to 1/1 instead of 1/1000 or what ever value will help the data appear correctly.

Thanks
Scott

> On Nov 2, 2016, at 1:34 PM, Keith <kwoody at citywest.ca> wrote:
> 
> We have a small network with one customer with ten connections all from an MX480
> w/MPCE 2 3D,  RE2000 acting as a PE
> router.
> 
> All interfaces are L3VPN and have multiple vrf's on them.
> 
> Unit 11
> Unit 101
> Unit 102
> Unit 1000 - our management
> 
> The CPE at the customer is an EX4200 at each location.
> 
> The customer would like to see top talkers etc on each site.
> 
> We have flow capture setup on our peering/transit locations, but use
> unit 0 on those interfaces, and is pretty simple.
> 
> Would I put the sampling on each unit on each interface that from where
> we want to capture?
> 
> When setting up multiple captures on several interfaces is this going to
> be too much to do load wise?
> 
> The sites in question schools, are low bandwidth, mostly 30 megs with one at 90.
> 
> Thanks,
> Keith
> 
> 
> 
> 
> 
> 
> 
> 
> 
> 
> _______________________________________________
> juniper-nsp mailing list juniper-nsp at puck.nether.net
> https://puck.nether.net/mailman/listinfo/juniper-nsp