I have seperate routers configured to send netflow data to a specified IP address, and I have setup PRTG NM to monitor that IP address. How do I configure PRTG NM to identify the data per router?
Best Answer
we recommend using remote probes in the distant locations. Send the flow data to the remote probes, they will process it and send data to the core server on a dedicated port.
All remote probes can use the same port, so you will have to open only one port in your firewall,
please take a look at
http://www.paessler.com/manuals/prtg7/multiple_probes_and_remote_probes.htm
Created on Mar 24, 2010 4:56:10 AM by
Aurelio Lombardi [Paessler Support]
(7,239)
●3
●1
Last change on Mar 24, 2010 4:56:26 AM by
Aurelio Lombardi [Paessler Support]
(7,239)
●3
●1
5 Replies
you have to configure your devices to send flow data on different ports. A different port for each device.
At the moment PRTG differs the flows not by sender IP but by port the flows are sent on.
In the PRTG sensor settings you have to change the port accordingly.
So if I have 40 sites, I need to have 40 different ports open on my firewall - doesn't make sense!
we recommend using remote probes in the distant locations. Send the flow data to the remote probes, they will process it and send data to the core server on a dedicated port.
All remote probes can use the same port, so you will have to open only one port in your firewall,
please take a look at
http://www.paessler.com/manuals/prtg7/multiple_probes_and_remote_probes.htm
Created on Mar 24, 2010 4:56:10 AM by
Aurelio Lombardi [Paessler Support]
(7,239)
●3
●1
Last change on Mar 24, 2010 4:56:26 AM by
Aurelio Lombardi [Paessler Support]
(7,239)
●3
●1
Hi, Is it planned for PRTG to support netflow on one PRTG server port only?
Having to specify a different port of each remote device is not scalable for the following reasons:
1) You have to track which devices are assigned to which port, and keep that list updated.
2) You cannot push a generic netflow configlet to the remote device, but have to make individual device changes.
Both the above issues mean the netflow functionality is not suitable for an organisation with more than a handful of devices.
If PRTG used the source IP address as the device identifier (and not the port), the netflow feature of PRTG would be very useful and I think you would sell more netflow collector licenses.
Thanks Peter
Such an option is already in consideration but the implementation is more complex than it may appear. We are cheking our options, cannot, however, provide a time frame for when such a feature would actually be available. Please bear with us.
Please log in or register to enter your reply.
Add comment