I started out with a single trap receiver sensor on the probe device itself but since there's no reverse lookup for the source IP, its unusable for immediate identification of the offending device.

Is it wise to have a separate trap sensor for each switch? I have about 200 switches in my network that I have to monitor for port flapping and loop detection.

Can someone point out what is a recommended setup?

Thanks.

Article Comments

Hello,

The feature to support reverse lookup for the source IP is still on our wishlist, but I'm afraid I cannot give you an exact release-date/version in the moment.

To the number of switches you would like to monitor, we recommend to use a separate trap sensor for each switch.


Feb, 2015 - Permalink

And one more thing,

Apparently it's not possible to have trap sensor in a template? If I were to use separate trap sensor for each switch there should be an option to use a template with trap sensor and its filters included.

Can someone confirm this?


Mar, 2015 - Permalink

Hello,

Unfortunately, SNMP Trap Receiver Sensor and also some others are excluded for device templates, since you need individual settings configured for each sensor. However, you can clone the sensors one by one, or write your own Powershell script, which will find all your device IDs in PRTG and add a Trap Receiver sensor on it. There is currently no simpler way to do this.


Mar, 2015 - Permalink

That is quite unfortunate as it limits the functionality of such a sensor. Both approaches to the problem, either by creating a global trap sensor or by creating separate trap sensors for each device, are plagued by simple to solve issues. The first lacks DNS lookup in order to identify the sender device, and the second offers no simple way for configuration.

Are there any plans to improve this?


Mar, 2015 - Permalink

Hello,

Thanks for your feedback, we really appreciate it.

In the moment we do not plan any changes, but we have it on the list.

Please bear with us.


Mar, 2015 - Permalink