Hello. I've noticed that alarms that have been "masked until unmasked" get unmasked as soon the agent reboots. Is this behaviour by design or do we have a bug there? I would expect that the alarms remain masked until they get unmasked by a user. It is very annoying masking alarms over again.
Hi,
I got some news on the case. We were unfortunatly not able to clearly reproduce the issue. It happened though when we restarted the active agent. After the following failover and alarm storm, some of the permanently masked alarms got unmasked. These were table row alarms coming from a grouped alarm template.
Restarting the new active server (the other way around) did not cause this problem. I have to monitor this case for a longer period to get the real reason.
Thanks for your help anyway
Hi Michael,
That should not be the case. Alarms should stayed masked after a DMA restart.
Please could you let us know if you experience the same behavior if you restart the element where these alarms belongs?
Are you masking alarms related to rows in a table?
Also single params.
Hi,
Alarms in table rows, yes. This does not happen when just restarting the element. I will try tomorrow morning to reproduce the situation. At the moment are to many users working on the DMA.
Works for me just fine in the latest DM internal 10.3.8, (still masked after restart). Alarms in table rows