OVNM 5.3 - Operations Agent for NonStop Troubleshooting Guide

Appendix B 124
Table 8 Internal Messages Logged to HP Operations Manager by OVNM SPI
Message Description
OVNM: local Elink is not
responding (hung state)
Message logged when the local Elink goes into Hung state and is not
responding. The severity of this message can be controlled by modifying the
internalmsgseverity parameter in the OVNMCONF file.
OVNM: Catchup-request sent fail
to the node NODE, goback=10
seconds
Message logged for a particular node in HP Operations Manager, when the
catch-up request sent fails to reach the node. The severity of this message can
be controlled by modifying the internalmsgseverity parameter in the
OVNMCONF file.
111:OVNM: MSG RECONN RCVRY
DONE: SDISTxx
If OVNM is configured with Message Queuing option, this message is logged
after the connection between the NonStop node and HP Operations Manager
has been reestablished and all NonStop events (which were logged during the
time when the connection was lost with HP Operations Manager) are recovered
(resent) to HP Operations Manager.
Corrupt multi bytes events
received. <Field-Name> field is
invalid
Corrupted messages are logged in log file and for each corrupted message,
message “Corrupt multi bytes events received. <Field-Name> field is invalid”
will be logged in log file as well as in HP Operations Manager.