HP NonStop G-Series - Manual (Page 116)

Appendix K: Internal Messages Generated by OVNM-SPI 116
Appendix K: Internal Messages Generated by OVNM-
SPI
Enhancements have been made in the OVNM SPI runtime parameters to perform the following functions related
to HPOM events generated by the OVNM SPI process. You You can use the ovnm_spi binary in order to alter the
runtime parameters.
1. Enabling/Disabling HPOM Messages
You can use the following runtime parameter to enable or disable the HPOM messages generated by
OVNM SPI process.
-internalmsg
By default the parameter is ON.
2. Changing Message Severity
You can use the following runtime parameter in order to change the severity of the HPOM events generated
by the OVNM SPI process.
-internalmsgseverity < NORMAL | WARNING | MINOR | MAJOR | CRITICAL >
This section provides a list of internal messages logged to HPOM by OVNM.
Table 2 Internal Messages Logged to HPOM by OVNM
Message Description
111:OVNM: Connection established
with remote Node \NODE
Message logged for a particular node in HPOM, when the connection is
established with the remote node. The severity of this message is Normal.
OVNM: Connection lost with local
Elink
Message logged at the nodes level in HPOM when the connection is lost with
the local Elink. The severity of this message can be controlled by modifying the
internalmsgseverity parameter in the OVNMCONF file.
OVNM: Connection resumed with
local Elink
Message logged at the nodes level in HPOM when the connection is resumed
with the local Elink. The severity of this message is Normal.
111:OVNM: Catchup-request is
sent to the node NODE, goback=10
seconds
If the connection between HPOM Management Server and the HP NonStop
Server(s) is lost due to any reason, the event messages generated by the HP
NonStop server(s) are not forwarded to the HPOM Message Browser. When
the connection is reestablished, OVNM SPI sends the auto-catch-up request to
the NonStop agent to recollect the lost messages. This message is logged for a
particular node in HPOM, when the catch-up request is sent. The severity of this
message is Normal.
111:OVNM: Catchup completed
Message logged when the catch-up request sent by OVNM SPI to the NonStop
agent is completed. This message is logged for a particular node in HPOM.
The severity of this message is Normal.
111:OVNM: Connection lost with
remote Node \NODE
Message logged at the nodes level in HPOM when the connection is lost with
the remote node. The severity of this message can be controlled by modifying
the internalmsgseverity parameter in the OVNMCONF file.
OVNM: Connection established
with local ELINK
Message logged at the node level when the agents in the front-end are started.
The severity of the message is Normal.
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 HPOM, 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 HPOM has been
reestablished and all NonStop events (which were logged during the time when
the connection was lost with HPOM) are recovered (resent) to HPOM.
A
pp
en
di
x K