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:

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

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:

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

If you want to allow Traffic Server to configure sFlow using SNMP (using the sFlow MIB (RFC 3176)) you will need to make sure that both read and write access is allowed (GET/SET).

To specify a particular community string and/or sampling-rate for your router, create an [agent] entry in your inmon configuration file like this...

You may need to create a new [subnet] entry for this [agent] entry to go under.

Note: The sampling rate setting will only take effect if SNMP is being used to configure sFlow.