Subscribing is a smart move!
You can subscribe to this board after you log in or create your free account.
Invite a Co-worker
Send a co-worker an invite to the portal.Just enter their email address and we'll connect them to register. After joining, they will belong to the same company.
Send Invite Cancel
Link copied. Please paste this link to share this article on your social media post.
Hi Javier,
That would have to be done at the threshold level and for SNMP and modbus devices, there is no option for a delay in the default communications threshold:
If you don't want to see these alerts at all, you could change their severity and in the NMS integration configuration, remove the lower level severities from being sent:
The only other option I can think for you to try would be to disable the offending thresholds and recreate them as thresholds for state for time. You can create thresholds for multiple devices at once and maybe even test them before you go system wide. Create an "other state threshold and choose state for time:
Click next and as long as they have a communications status sensor:
You can con configure a lost comm to alarm after a certain amount of time...here I put in 500 seconds or 10 minutes:
Different devices may or may not have this sensor and you may need to play around with it.
As you've seen, there is no option to delay NMS integration traps across the board and the easiest and recommended way around your issue other than fixing the reason for the lost comm issues is to use the alarm action /trap which uses the NetBotz MIB OIDs.
Steve.
Link copied. Please paste this link to share this article on your social media post.
This question is closed for comments. You're welcome to start a new topic if you have further comments on this issue.
Create your free account or log in to subscribe to the board - and gain access to more than 10,000+ support articles along with insights from experts and peers.