• Getting Started
• NetFlow
• sFlow
• XRMon
• Tutorials
• Server
• Monitor
• Reports
• Queries
• Multi-Site
• Routing
• Security
• Support

Help : Getting Started : sFlow

There are two mechanisms for configuring the export of sFlow data from routers and switches: the command line interface (CLI) or SNMP:

CLI

Configure routers/switches to direct sFlow data to the Traffic Server using port 6343. Consult your router/switch/probe documentation for instructions on configuring sFlow:

• Foundry Networks
• InMon sFlow Probe

You can confirm that sFlow packets are arriving at the server by running:

% /usr/sbin/tcpdump -n udp port 6343

The source IP address should be the loopback IP address of the router. If the traffic server has received these packets, then the IP address should also be listed in the file /usr/local/inmon/server/state/agents.txt.

Follow the steps in the following section on SNMP to make sure that Traffic Server is able to communicate with the router using SNMP. While not essential this provides additional information (such as interface descriptions) that provide improved functionality.

SNMP

Make sure that the Traffic Server can make SNMP requests to the IP address of the router:

% snmpwalk <router IP> <community string> interfaces

If this does not work, then you may need to change the router configuration to enable SNMP access.

Autodiscovery

If you have devices that support the sFlow Version 5 MIB then Traffic Server can automatically discover and configure them using SNMP

First make sure that both read and write SNMP access is allowed (GET/SET). Then make sure you enable discovery in the configuration file:

[enterprise]
.
.
samplingEnabled = YES  ; turn on sampling on all devices
discoveryEnabled = YES ; sweep subnets for sFlow devices

You should also make sure that you add [zone] and [subnet] sections for all the address ranges that you would like tested for sFlow agents.