HP NonStop G-Series - Manual (Page 113)

Appendix H: Customizing OVNM Configuration Files 113
If the OCCCONF file is updated with this command, when you use the Object Configuration Client to turn node
monitoring off, ALL EMS thresholds will also be disabled. When you turn node monitoring off, then as the EMS
messages are received by the ACC program, it will toss them away. There is no automated method of re-
processing those events while node monitoring has been turned off. When node monitoring is turned back on,
the system will act the same as if you had just started it – it will start processing new EMS messages.
If the OVNMCONF file is updated with this command, then when you use the Object Configuration Client to turn
node monitoring off, NO EMS messages will be sent to HPOM or Console. There is no automated procedure for
getting those messages into HPOM.
EMS messages that are generated when node monitoring is turned OFF or ON look like the following. The only
difference is the process name that generates it.
$OVxxx:Node Monitoring has been requested to be turned off - ALL EMS msgs
ignored.
$OVxxx:Node Monitoring has been requested to be turned ON. EMS will be
processed.
You can use this optional feature when you want all OVNM processing to be suspended for some critical reason.
By default the node monitoring does not impact the EMS processing. The feature has to be turned on manually.
Using Secondary Log to Capture Enterprise Management Messages
OVNM logs a second copy of every message that it sends to the Enterprise Management System (for example
HPOM). This feature allows the user to log any message that is sent to the Enterprise Management system to a
secondary EMS collector. Follow the steps given below to use this feature:
1. Edit the OVNMCONF file and locate the lines that specify the CopyEMSToColl parameter. This will explain
the parameter in detail.
2. Copy the line that has been commented out and paste it between the CUSTOMER CHANGES #1 lines.
SET OVNM CopyEMSToColl
3. Change to the secondary collector that you want to use.
4. Execute the following commands:
RUN STOPOVNM
RUN STRTOVNM
Once this feature has been turned ON, it will write the secondary messages to the specified collector. If the
collector specified in this parameter cannot be written to, it tries the primary collector.
The EMS message that is written to the secondary collector will use SSID TANDEM.OVNM and the event number
will be 152.