189
Agent IP: 3.3.3.1(CLI)
Source address:
Collector information:
ID IP Port Aging Size VPN-instance Description
1 3.3.3.2 6343 N/A 1400 netserver
Port information:
Interface CID Interval(s) FID MaxHLen Rate Mode Status
XGE1/0/1 1 120 1 128 4000 Random Active
Troubleshooting sFlow configuration
The remote sFlow collector cannot receive sFlow packets
Symptom
The remote sFlow collector cannot receive sFlow packets.
Analysis
The possible reasons include:
• The sFlow collector is not specified.
• sFlow is not configured on the interface.
• The IP address of the sFlow collector specified on the sFlow agent is different from that of the
remote sFlow collector.
• No IP address is configured for the Layer 3 interface that sends sFlow packets,
• An IP address is configured for the Layer 3 interface that sends sFlow packets. However, the
UDP datagrams with this source IP address cannot reach the sFlow collector.
• The physical link between the device and the sFlow collector fails.
• The sFlow collector is bound to a non-existent VPN.
• The length of an sFlow packet is less than the sum of the following two values:
{ The length of the sFlow packet header.
{ The number of bytes that flow sampling can copy per packet.
Solution
To resolve the problem:
1. Verify that sFlow is correctly configured by using the display sflow command.
2. Verify that a correct IP address is configured for the device to communicate with the sFlow
collector.
3. Verify that the physical link between the device and the sFlow collector is up.
4. Verify that the bound VPN already exists.
5. Verify that the length of an sFlow packet is greater than the sum of the following two values:
{ The length of the sFlow packet header.
{ The number of bytes (as a best practice, use the default) that flow sampling can copy per
packet.
To Next Page
Loading...
Need help?
General
