If a critical message arrives with application "test," then this message matches rules A and B, but the management server evaluates only the first matching rule and so forwards the message only to server X and not to server Y.
If you do not want this behavior, you must write an additional message target rule that matches only on critical messages with application "test" and forward these messages to server X and server Y; then you must place this rule before rule A.
<configfile> ::= <epsilon> | RESPMGRCONFIGS <respmgrconfigs> <respmgrconfigs> ::= <epsilon> | <respmgrconfigs> RESPMGRCONFIG DESCRIPTION <string> <respmgrconds> <respmgrconds> ::= SECONDARYMANAGERS <secondmgrs> ACTIONALLOWMANAGERS <actallowmgrs> | SECONDARYMANAGERS <secondmgrs> ACTIONALLOWMANAGERS <actallowmgrs> MSGTARGETRULES <msgtargetrules> | MSGTARGETRULES <msgtargetrules> <secondmgrs> ::= <epsilon> | <secondmgrs> SECONDARYMANAGER NODE <node> | <secondmgrs> SECONDARYMANAGER NODE <node> DESCRIPTION <string> <actallowmgrs> ::= <epsilon> | <actallowmgrs> ACTIONALLOWMANAGER NODE <node> | <actallowmgrs> ACTIONALLOWMANAGER NODE <node> DESCRIPTION <string> <msgtargetrules> ::= <epsilon> | <msgtargetrules> MSGTARGETRULE DESCRIPTION <string> <msgtargetrule> <msgtargetrule> ::= MSGTARGETRULECONDS <mtrconditions> MSGTARGETMANAGERS <msgtargetmgrs> | MSGTARGETRULECONDS <mtrconditions> MSGTARGETMANAGERS <msgtargetmgrs> <mtrconditions> ::= <epsilon> | <mtrconditions> MSGTARGETRULECOND DESCRIPTION <string> <mtrcond> <mtrcond> ::= <epsilon> | <mtrcond> SEVERITY <severity> | <mtrcond> NODE <nodelist> | <mtrcond> APPLICATION <string> | <mtrcond> MSGGRP <string> | <mtrcond> OBJECT <string> | <mtrcond> MSGTYPE <string> | <mtrcond> TEXT <string> | <mtrcond> SERVICE_NAME <string> | <mtrcond> MSGCONDTYPE <msgcondtype> <msgtargetmgrs> ::= <epsilon> | <msgtargetmgrs> MSGTARGETMANAGER TIMETEMPLATE "$OPC_ALWAYS" OPCMGR <node> <severity> ::= Unknown | Normal | Warning | Minor | Mayor | Critical <msgcondtype> ::= Match | Suppress <nodelist> ::= <node> | <nodelist> <node> <node> ::= IP <ipaddress> | IP <ipaddress> <string> <string> ::= "any alphanumeric string" <ipaddress> ::= <digits>.<digits>.<digits>.<digits>
NOTE:
The keywords ACKNONLOCALMGR
,
MSGCONTROLLINGMGR
, and NOTIFYMGR
are not
supported for server-based flexible management policies.
note:
The syntax check allows the keywords
SECONDARYMANAGERS
and ACTIONALLOWMANAGERS
in server-based flexible management policies for backwards
compatibility with MsgForwarding.ini
files. However,
these keywords have no effect in server-based flexible management
policies.