WANGUARD 5.2 User Manual & Administrator's Guide
Flow Sensor Configuration
Many routers and switches can collect IP trafc statstcs on monitored interfaces, and later export those
statstcs as fow records, towards the Flow Sensor
to do the actual trafc analysis.
For detailed instructons on how to enable NetFlow, sFlow or IPFIX on your network device, please consult
the vendor's website. An example on how to confgure NetFlow on IOS, CatOS & Juniper can be found in Appendix 2
at page 63.
The Flow Sensor Confguraton window contains the following felds:
●
Sensor Name
A short name to help you identfy the Flow Sensor.
●
Interface Group
Optonal descripton used within the Console to group multple interfaces by locaton, roles etc.
●
Flow Protocol
The type of fows exported towards the Sensor: NetFlow or IPFIX or sFlow.
●
IP Address
The IP address of the router, switch, probe etc. Usually the Loopback0 address of the router. Each server
running the Flow Sensor must have its system tme synchronized with the fow exporter.
●
Sampling (1/N)
Must contain the sampling rate as confgured on the fow exporter. It's 1/1 if no sampling is used.
NeFlow v9 contains the sampling value so in that case the value of this feld will be ignored.
●
Time Zone
The tme-zone diference between the Console's server and the fow exporter.
●
Sensor Server
The Server running the Sensor. To add a new one, go to Confguraton » Servers » Add Server.
●
Listener IP/Port
The IP address of the network interface that receives fows and the destnaton port.
●
Sensor Type
If the license key permits it, you can change the type of the Sensor.
●
SNMP Community
The read-only SNMP community of the network device allows Console to connect to the fow exporter
and request SNMP indexes and other useful informaton for adding new interfaces.
●
Monitored Interfaces
The list of interfaces that should be monitored. Add as few as possible. Setngs per interface:
- 47 -
Summary of Contents for Wanguard 5.2
Page 1: ......
