-
When this technology is used PRTG queries the devices (e.g. routers, switches, and servers) for the traffic counters of each port. This option creates the least CPU load and network load of the three methods.
-
PACKET SNIFFING IN LANS
If you need to know what applications or IP-addresses are causing the traffic in your network you can use a Packet Sniffer which looks at every single data packet travelling in your network for accounting purposes. PRTG can analyze the packets passing the network card of a PC or it can be connected to a so-called monitoring port of a switch.
DATA ACQUISITION USING PACKET SNIFFING (LAN)
In order to calculate bandwidth usage PRTG inspects all network data packets either passing the PC’s network card (shown on the left side) or the data packets sent by a monitoring port of a switch (right side) with its built-in Packet Sniffer. From the three technologies shown here this one creates the most CPU and network load. For larger networks PRTG offers remote probes that distribute the load and assure maximum performance.
-
NETFLOW PROTOCOL
Professional routers and switches from vendors like Cisco, HP, Juniper, and others support NetFlow or sFlow export for bandwidth usage monitoring. It is the most powerful monitoring method, suitable for high traffic networks.
DATA AQUISITION USING CISCO’S NETFLOW PROTOCOL
Cisco devices with NetFlow support track the bandwidth usage of the network internally and then only send pre-aggregated data to the PRTG system for accounting purposes. This way the computing load for
-
The following table shows the differences between PRTG’s four methods available for bandwidth monitoring:
-
WMI
SNMP
PACKET SNIFFER
XFLOW (IPFIX, NETFLOW, SFLOW, JFLOW)
Setup
Medium
Easy
Easy to complex (depending on filter rules used)
Can be complex (e.g., the switch must be configured)
Traffic can be filtered
No
No
Yes
Yes
Differentiate bandwidth usage by protocol or IPs
No
No
Yes
Yes
PRTG can show Toplists (Top Talker, Top Connections, Top Protocols, custom)
No
No
Yes
Yes
Filter bandwidth usage by IP
No
No
Yes
Yes
Filter bandwidth usage by MAC address
No
No
Yes
No
Filter bandwidth usage by physical network port
Yes
Yes
No
No
Monitor network parameters other than bandwidth usage
Yes
Yes
No
No
CPU load on the machine running PRTG
Low
Low
Higher, depends on the amount of traffic
Higher, depends on the amount of traffic
Excess bandwidth usage of monitoring
Small
Small
None (except when monitoring switch ports are used)
Depends on the traffic
Leave a Reply
You must be logged in to post a comment.