multiple waitopors

[asewell]

NSM 3.0
We have a distinct trap forwarded by multiple DSMs to our EM console which in turn causes multiple held alerts (waitopers)for the same issue. Is there a technique in a MRA that can be used to display only one waitoper.

 

[jseah]

If there is a reset trap you can use the Delkeep message action to remove the message from the held area. otherwise best I know you will have to use AEC if you are wanting a Unicenter solution to the issue

 

[asewell]

Traps are comming at the same time so a delkeep does not work - AEC not installed - I was expecting an education on EVALNODE (currently set as the default at this shop)

 

[JonnoGT]

Not sure if this is quite what you are looking for, but it may help.
In the message record, on the config tab page you can set the interval and count of the message you are watching for.
IE: set interval to 60, count to 5 and it will only perform the message actions if the message is received 5 times in a minute. Hence, only one waitopr.

 

[UberGeek27]

Alternately, you could use a variable... use the EXPORT action to set &MSGRECEIVED to 1 when you send the SENDOPER. At the beginning of the action sequence, test if &MSGRECEIVED = 1 before SENOPERing...

 

[asewell]

These responses are good in suppressing multiple alerts, and we do apply them at our shop, but they do not correct the problem I have stated. Because the DSM's are forwarding the traps simultaneously any method to create a 'is one already there' scenario does not work. Using the interval counter would work, but can not be used for other reasons. I am just beginning to use this app and although i have some (little) experience with MRA -I am not familiar with how the DSM talk to EM. Does EM know what DSM is forwarding the trap. If it does - then a method of


trap sent from DSM x and y

TEST ?DSM
if DSM = x
wait 10
waitoper (caught by dsm y)
inqoper (once x wakes up will see held message)
or test an exported var

This would solve the issue, and keep the redundancy, but it does not appear that EM knows the DSM forwarding.

 

[jseah]

If you know which DSMs are the ones that are going to be forwarding the message up to the main COR, then you could actually use an MRA at the DSM (Evalnode) to limit the messages that you send up. Use a combination of the evalnode and by what is written JonnGT and you should be ok.

 

[UberGeek27]

You could also have the source DSM "tag" it when forwarding the message; use the overrides tab on the FORWARD action to insert data into either the source or category fields...