persistant alarm state SNMP trap

Hey vk6xre,
Thanks for your KB-posting.

Actually, it is not possible in PRTG to leave the SMTP Trap sensor in DOWN/ERROR-state until it receives an OK-message.

Please see a summary from our manual, which explains how the sensors changes its status:
Messages are collected until a scanning interval ends. As long as the scanning interval is running, no status change will happen. By default, the sensor will turn into a Down status after a scanning interval has finished and there was at least one error message during this interval. The status will remain Down at least until the succeeding scanning interval has finished. If the sensor did not receive any warning or error message in this scanning interval, its status will turn Up again after the interval.

A workaround could be to create a notification which simulates a DOWN/ERROR-state and to trigger that with a state-trigger. For example, "If State: DOWN for at least 0 seconds --> simulate ERROR-State".

On that way your sensor stays in DOWN/ERROR-state (but with the error-message Simulated error (code: PE034)). To bring the sensor back to OK-state, you have to explicitly click on "Resume".

To to so, the following steps, have to be done:

1) Add a notification
1.1) Please navigate to "Setup >> Account Settings >> Notifications"
1.2) Click on "Add new notification"
1.3) Under "Method", please choose "Always notify ASAP, never summarize"
1.4) Please activate the option "Execute HTTP action" and enter the following URL:

https://[IP of your Core Server]/api/simulate.htm?id=%sensorid&action=1&username=[Your username]&password=[Your password]

1.5) Save the notification
For further details, please refer to this manual

2) Add a state-trigger
2.1) Please navigate to your SNMP-Trap-Receiver-Sensor
2.2) Switch to tab "Notifications"
2.3) Click on "Add State Trigger"
2.4) Please set the values which should reached to trigger the notification (Suggestion: 0 seconds)
2.5) Please choose your "Simulate Error"-notification
2.6) Save the state-trigger
For further details, please refer to this manual

Best regards,
Sven