Hi there,
at a customer site I am encountering the following nas behaviours in test and prod:
In test:
- when logmon sends an alarm because it found a pattern match, the corresponding alarm shows up in the IM alarm console,
- when logmon encounters the pattern again, then the alarm goes away vor a second and then returns with a new timestamp, or it just assumes a new timestamp - but it doesn't increase the count.
In prod:
- when the hub sends a queue contact loss alarm once a minute, then its count is increased correctly but after five minutes we get the same alarm anew and the old one vanishes. This is particularly painful as it leads to an email flood when you configure notification - even if you say you want the mail sent only for alarm counts less than 3...
It would actually be my understanding that, in usual configurations, in both cases nas would just increase the alarm count for the respective alarms. Am I not right with that?
In both cases, I have checked the message bus with hub monitor sniffing and on this end, everything is OK.
So, what would be a good candidate for a "mis"configuration here (I haven't configured the system myself). Conflicting AO profiles? I have tried to get rid of this by playing around with the suppression settings in the NAS but to no avail.
I am really curious about this...
Any ideas?
Best
Alex
------------------------------
Linkedin:
www.linkedin.com/in/alexander-kuehn/------------------------------