Netflow PRTG Download

The PRTG Manual: Monitor Bandwidth via Flow

Netflow PRTG Download using the flow protocol, you can move the bandwidth usage of all packets using the device. In PRTG, you can see the Top List for all xFlow sensors (NetFlow, IPFIX, sFlow, jFlow). Flow is a type of communication data that is driven from network devices to PRTG. You can use to transfer any data, traveling to and from, and how much. This way determines which machines, protocols, and users use bandwidth. PRTG currently supports the following stream types.

NetFlow v5 / v9 and IPFIX: Introduced by Cisco and supported by several vendors jFlow: Traffic sampling technology introduced by the Juniper network. sFlow: Short for sample streams, introduced by HP. sFlow uses statistical samples of traffic at specified intervals to achieve scalability for high-volume interfaces. You can also use the sniffing package to support bandwidth if your hardware doesn't support this stream version.

How xFlow Monitoring Works

You can use bandwidth using IP addresses or applications on the network, using one of the xFlow protocols (including IPFIX). They are the best choice for high traffic networks (megabit or gigabit connections). To redirect xFlow, the router collects bandwidth (current) data, transmits, and sends information about it to PRTG using the UDP package. 

When you use take samples (mandatory for sFlow), only information about each n-packet is sent to PRTG, which reduces a lot of CPU load. Because it has already pre-aggregated traffic data, the data flow to PRTG is much smaller than the monitored traffic. This makes xFlow the ideal choice for networks with high traffic that need to be determined by bandwidth by network protocols and / or IP addresses.

NetFlow and IPFIX Monitoring

Netflow PRTG Download protocols (and IPFIX) are mainly used by Cisco devices. After deciding, the router sends for each stream of NetFlow or IPFIX data packets to a monitoring system that runs on the PRTG probe. You can filter and change data in PRTG. There are several NetFlow and IPFIX sensors available: Basic sensors that offer predefined channel resolutions, special variants that you can use to determine your own channel.

The Advantages of Using NetFlow or IPFIX:

Produces a bit of CPU load on the router itself (according to Cisco, 10,000 active streams generate around 7% additional CPU load; 45,000 active streams cover around 20% additional CPU load). Produces less CPU load on the PRTG core system compared to the Packet Sniffer sensor. icon-i-round-red You must enable NetFlow or export IPFIX on the device you want to monitor. The device must send a stream of data flow to the IP address of the PRTG inquiry system where you set up NetFlow or IPFIX sensors.

Download Netflow PRTG 

Netflow PRTG
Free Driver

icon-i-round You can monitor Juniper jFlow with the appropriate sensor too. Basically they adjusted the NetFlow v5 sensor. Icon-i-round NetFlow Lite monitoring is possible using the Sampling Mode from the NetFlow V9 sensor or NetFlow V9 sensor (Custom). You can activate sampling mode and determine the appropriate Sampling Rate in the sensor settings. Please note that NetFlow Lite monitoring may not work in every case even with active sampling mode with Netflow PRTG Download.

sFlow Monitoring

sFlow works similar to Netflow PRTG Download. The router sends a packet of data flow to the monitoring system that runs on the PRTG probe. The most obvious difference between the two flow protocols: With sFlow, not all traffic is analyzed, but only every nth packet. It's like having a river of traffic and you take a cup of water from the river so often and analyze it.

The advantage is clear: There is less data to analyze, less CPU load needed, and less monitoring traffic generated. However, you can get good insight into your network bandwidth usage. icon-i-roundPRTG supports sFlow version 5.


For example, with dual core, 2.5 Ghz hardware systems, you can process around 100,000 streams per second for one xFlow stream. Using sampling, the actual amount of current can be much higher. When using complex filters, the value can be very much lower. For example, with a router that sends around 2,000 currents / second (which corresponds to mixed traffic at gigabit / second level without sampling), you can configure up to 50 xFlow sensors that are operating correctly.

The PRTG internally monitors its own xFlow processing. You can see a decrease in value in the Core Health and Health Probe sensor health channels as soon as the xFlow package is not processed due to overload (you find this sensor in the local inquiry device). We advise you not to add more than 50 xFlow sensors per PRTG probe. This type of sensor cannot be used in cluster mode, it can set it on a local probe or a remote probe only, not on a cluster probe with Netflow PRTG Download.