cancel
Showing results for 
Search instead for 
Did you mean: 
cancel
1901
Views
0
Helpful
2
Replies

Netflow sampling

chinguun bayar
Level 1
Level 1

i have configured netflow in my router but my router is overheaded. So i decided to configure sampled netflow and sampling rate of 1 out of 100 packets may reduce the export if Netflow data by as musch as 50 percent.So you know its not suitable for security monitoring.

Whats your recommendation ? is there any solution on collector?

2 Replies 2

Hello Chinguun,

Collecting sampled flows should be a native capability of most collectors on the market. The ability to receive a high volume of flows is a feature that sets vendors apart. Keep in mind that collection and then reporting are two separate issues in terms of performance.  You might want to test our free version of Scrutinizer. 

Also, if you want to reduce flow volumes but, reduce flow volumes, read this post involving Flexible NetFlow: https://www.plixer.com/blog/sflow/how-to-avoid-ipfix-or-netflow-sampling-vs-sflow/ 

I hope this helps.

Mike

brford
Cisco Employee
Cisco Employee

Hello Chinguun,

You've encountered a somewhat common problem.   Many engineers find that enabling NetFlow and the telemetry data that it produces is very valuable.  The problem is they may not have considered the impact of enabling flow on the router both in terms of processor and bandwidth utilization.

Engineers will frequently resort to sampling flow.  Sampled flow is good for some tasks such as gaining indicators of network or application utilization; but not good for others.  Sampled flow creates big gaps in the telemetry stream making the data less valuable for anomaly detection and other security purposes.

A solution to this problem is to deploy a Flow Sensor.  A Cisco Stealthwatch connects to your router via a span port and offloads the process of creating flow.  The Flow Sensor captures packets on the span port and uses that data to create a NetFlow. The Flow Sensor is then configured to send that NetFlow to a Flow Collector.

When used with our Cisco Stealthwatch Flow Collectors the flow traffic from a Flow Sensor is not counted towards the Flows Per Second license normally required on a Flow Collector.  The Stealthwatch Flow Collector then reports flow telemetry via the Cisco Stealthwatch Management Console.

Flow Sensors are valuable for gathering flow data from places in the network where you can't (due to reasons such as processor utilization) or shouldn't (if the device on the network is not under your administrative control; as is the case if the router is supplied by a service provider or other third party).

For more information see:  http://www.cisco.com/go/stealthwatch

Brian Ford  | Technical Marketing Engineer  | Cisco Security Business Group  | @ccie2106

 

Brian Ford | brford@cisco.com | brford@yahoo.com | 51 75 61 6c 69 74 79 20 6d 65 61 6e 73 20 64 6f 69 6e 67 20 69 74 20 72 69 67 68 74 20 77 68 65 6e 20 6e 6f 20 6f 6e 65 20 69 73 20 6c 6f 6f 6b 69 6e 67 2e | Email me when you figure this out.