Traffic Sentinel : Help
Help Index Top > File > Forwarding

The Forwarding page is used to relay measurements to a remote machine for analysis.


How do I configure flow forwarding?

Select Flows from the Options: list. The following Flow Forwarding Settings are available:

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.

Back to Top

How do I convert sFlow to NetFlow?

Set the Format to NetFlow v5 to convert the sFlow to NetFlow version 5 before exporting. This will allow an application that only understands NetFlow to receive data from Traffic Sentinel.

Note: Traffic Sentinel's native data format is sFlow. Any flow information received in other formats (e.g. NetFlow) is converted to sFlow as it is received. Using the forwarding option to forward this data as NetFlow will result in data that has been converted from NetFlow to sFlow and back to NetFlow; causing a possible loss of precision. In this case a preferred mechanism would be to directly bounce received NetFlow using the CCNetFlowHost1 option in the global.prefs file.

Back to Top

How do I configure event forwarding?

Any events that appear under Sentinel: Events>List can be forwarded via:

To use the RSS field, simply select the event list that you want to follow, then click the button.

To configure syslog, SNMP Trap or email forwarding of events; select Events from the Options: list. The following Event Forwarding Settings are available:

For mail to be forwarded successfully the service sendmail must be configured on your server. Use a comma separated list of addresses if you want to send email events to more than one recipient.

The SNMP traps are described by the INMON-TRAP-MIB.

Back to Top