OVNM 5.3 - Operations Agent for NonStop Object Configuration Client Guide

Object Configuration Client: The Understanding 38
When an Escalation event occurs the event will have a unique Event Number, and the text Escalation will be
included in the original violation text. You have the option of sending an email (assuming a Email server is
configured) in case of an escalation. For details, refer to Email Alerts.
Specifying Unique Escalation Actions
It is also possible to perform different actions for the escalation event that OVNM generates. If you have
specified the Log escalation event after time period, you can create a separate EMS threshold for that event and
then define unique actions, Emails and/or messages to the Enterprise Management system. Normally, you will
define everything you need to on the original threshold definition. But when the object has been in a violation
mode too long (has reached its escalation time) and you need to take a different action, by creating an EMS
threshold on the OVNM-generated EMS message, you can specify different activities. The activities defined on
the original threshold (email and auto-recovery) will still happen – these ‘escalation’ activities will happen in
addition to those. To use this feature, configuration changes must be made to the OVNM configuration file
OCCCONF.
To use this feature for Email and recoveries, you must EDIT and add the CHECKALLEVENTSFOR ACTION
parameter to the OCCCONF file.
SET OCC CHECKALLEVENTSFORACTION YES
This line must be placed between the Customer Changes #1 lines in the OCCCONF file.
Without those lines, EMS violation messages that are generated by OVNM will NOT be checked to determine if
there are EMS thresholds defined. The standard process is for OVNM to ignore its own events for that function.
An EMS threshold for the OVNM-generated escalation event needs to be added via the Object Configuration
Client. The escalation event numbers can be found in Chapter 4: Threshold Events of the Object Reference
Guide. The SSID will be TANDEM.OVMON.
While creating the EMS threshold, you can use the normal process for defining the email, recovery and/or
eEvent message that will be used for the escalation event. Please note that on the Email page, there is a check
box for Mail on Escalation Only and Mail on Normal. Neither of these options actually applies to EMS
thresholds. These options are no longer available for EMS thresholds with OVNM 5.3 onwards.
In addition to specifying additional email and/or recovery options for the Escalation event, you can also alter the
message that is sent to the Enterprise Management system (the eEvents panel). But in order for this to work, you
need to add the same CheckAllEventsForAction parameter as above to the OVNMCONF file, between the
Customer Changes #1 lines. In this case, you will use SET OVNM instead of SET OCC. Note that if you use this
option, the message defined in the normal threshold will be overridden with the message defined in the EMS
threshold – you will not receive two messages in the Enterprise Management system. This does allow you to have
one message for the standard violation alert (and repeated alerts), a different message for the ‘back to normal’
event and a third message for the Escalation event if you create 2 EMS thresholds (one for the violation alert and
one for the escalation alert).