The case of the missing OUT traffic with sFlow and NetFlow Analyzer
With more vendors introducing sFlow support, we have seen some users running into one issue in particular: they are unable to see OUT traffic from the sFlow device within NetFlow Analyzer. Let me try to explain why this is happening.
An overview on sFlow technology
sFlow, like NetFlow, is a monitoring technology that allows you to capture the traffic data from a switched or routed network to give complete visibility into the use of network bandwidth. sFlow datagrams are exported based on sampling, which minimizes the impact on device CPU, memory, and available bandwidth. Based on a defined sampling rate, one out of N packets (where N is the sampling rate) is captured and sent to NetFlow Analyzer for traffic analysis.The issue
There are two main reasons for NetFlow Analyzer not displaying OUT traffic:- NetFlow/sFlow is not enabled on all the interfaces of the monitored devices.
- There is an issue with the exporting devices, which is specific to sFlow.
1. NetFlow/sFlow not enabled on all interfaces
By default, only IN traffic across an interface is accounted for. However, we can capture the OUT traffic for other interfaces from this IN traffic because a captured flow will contain information on the exit interface of the traffic flow. So, in order to view both IN and OUT traffic graphs for a specific interface, NetFlow/sFlow should be enabled on all the interfaces through which traffic flows.2. Issue with the exporting device
Now to the specific issue with sFlow. What if you have enabled sFlow on all the devices but still cannot view any OUT traffic? All sFlow packets exported are expected to include the following key fields:- Source interface (input interface for traffic)
- Destination interface (output interface for traffic)
- Source IP address
- Destination IP address
- Protocol
- Source port
- Destination port
- ToS
Thank you for the information. I can attest that turning on ip route-cache cef on all of the interfaces solved the problem for me.