In the recent months we have seen multiple client machines causing broadcast storms on our network, usually from faulty network cards or drivers. At the moment, I try to identify the source of these storms by manually inspecting each SNMP sensor on our switches. Is there a way for PRTG to do the laborious work of sensor inspection and then give me a concise report to identify the switch ports doing the "talking" during a storm?
Identify source of a broadcast storm with PRTG
Modified on 2025-06-10 13:15:56 +0200
Disclaimer:
The information in the Paessler Knowledge Base comes without warranty of any kind. Use at your own risk. Before applying any instructions please exercise proper system administrator housekeeping. You must make sure that a proper backup of all your data is available.
The information in the Paessler Knowledge Base comes without warranty of any kind. Use at your own risk. Before applying any instructions please exercise proper system administrator housekeeping. You must make sure that a proper backup of all your data is available.
Dear user
There is no direct solution. However, you can do the following:
1. Set channel limits for the broadcast channel. If you use multi edit, you can set a channel limits for many sensors at the same time. Create a warning limit.
2. Create a PRTG map and use the table for sensor warnings. Filter this table for traffic sensors.
3. Use this map to see the sensors which currently exceed the limit set.
Mar, 2015 - Permalink