The Forwarding page is used to relay measurements to a remote machine for analysis, allowing a number of different sFlow enabled applications to share the same data.
Topics:
How do I configure forwarding?
The following settings are available:
- Enabled, enables or disables forwarding of sFlow for this entry.
- Agent Address, specify the agent or agents to be monitored. An agent can be specified by its domain name or IP address. If a subnet is specified then all the agents in that subnet will be monitored. For example: a value of 10.0.0.254 would forward traffic data collected from 10.0.0.254; a value or 10.0.0.0/24 would forward traffic from all the agents in the 10.0.0.0/8 subnet (including 10.0.0.254) and finally 0.0.0.0/0 will forward traffic from all agents.
- Destination Address, specifies the address of the host that will receive the forwarded sFlow. The address can be specified using the host address or domain name. A value of localhost or 127.0.0.1 will direct packets to the host running Traffic Sentinel. If you are receiving packets on the local machine, you must change the port from 6343 to some other value (see below).
- Port, specifies the UDP port that will receive the forwarded sFlow packets. The well known port for the sFlow protocol is 6343.
Note: If you want to forward sFlow to another application running on the same machine as Traffic Sentinel, you cannot use port 6343. Traffic Sentinel uses port 6343 to receive sFlow and so no other application will be able to open the port. In order to prevent looping of packets, Traffic Sentinel will report an error if you try to forward to port 6343 on any of the local interfaces.