Hi Stefan,

If you already double-checked that this general parameter is not monitored in the alarm template, then there is likely something else causing this behavior.

I would suggest contacting DataMiner Support (support@dataminer.services) so they can perform a more thorough investigation.

Hope it helps.

Hi Stefan,

Note that those general parameters (=parameters added by DataMiner to each element independent of the connector it is using) are a little bit more hidden away.

As indicated on the screenshot here below, those parameters are located under a special page 'General parameters' located at the very bottom of the navigation panel of the element card.

Also, in the alarm template those general parameters are not being shown by default. You need to click on the selection button at the top to select 'All parameters (protocol + general)' and then you will be able to see those general parameters towards the end of the list.

If you activate monitoring on this specific parameter 'Element alarm state', and you generate a major alarm when this parameter goes to the value 'Major'. Then you basically lock the alarm.

Imagine that a normal parameter goes into major alarm, then the element state will go into major state as well. So this means that this parameter will also generate a major alarm. Then if the original alarm clears, your element will remain in alarm forever because that alarm on the element state will never clear... I think you have to be very careful when activating alarming on this parameter, unless you want this kind of behavior.

Bert