HP OpenView Operations Administrator's Reference - filibeto.org

Tuning and Troubleshooting OVO
Troubleshooting Problems
412
Filtering Internal OVO Error Messages
Internal OVO error messages can be extracted from the internal
Message Stream Interface (MSI). The purpose of this message filtering is
to attach automatic and operator-initiated actions, and to treat the
message as if it were a normal, visible OVO message.
You can internal OVO enable error message filtering on the managed
node and on the management server. Depending on where you have
enabled the functionality, all OVO internal messages are sent back to the
local message interceptor on the OVO management server or on the
managed node. There the messages are viewed and treated in the same
way as any other OVO message.
To Enable Internal OVO Error Message Filtering
To enable internal OVO error message filtering, perform one of the
following:
❏ Management Server
On the OVO management server, use the command-line tool
ovconfchg:
ovconfchg -ovrg -ns opc -set \
OPC_INT_MSG_FLT TRUE
Where is the name of the management
server resource group.
❏ Managed Nodes
HTTPS-based managed nodes
Use the ovoconfchg command-line tool as follows:
ovconfchg -ns eaagt -set OPC_INT_MSG_FLT TRUE
DCE-based managed nodes
Add the string OPC_INT_MSG_FLT TRUE to the opcinfo file. See
Table 11-1 on page 404 for the location of the opcinfo file on the
various agent platforms.
You should set up at least one condition for internal OVO error messages
in the opcmsg (1/3) template (using message group OpC) and set the
[Suppress Identical Output Messages] button in the Message
Correlation window.
Chapter 11