ASAP 3.2 Server Manual

HP NonStop ASAP Server Manual Page 98 of 381
actions at all levels. Any other attributes configured for events with states of equal or
higher values are not alerted via EMS events. Boolean goals are processed after
simplex and escalating goals, so no event will be written for Boolean goals if an event
is written for a simplex or escalating goals. To have more than one event per domain
per interval, place the SET ObjectivesEventMax command in your ASAPCONF
file.
Other settings control whether events are displayed on the operator console. For more
information, see the SET Command.
To turn on down and up events for warnings and higher alerts, allowing two events per
domain per interval, put these event commands in your ASAPCONF file:
SET ObjectivesEvent ON
SET ObjectivesEventUp ON
SET ObjectivesEventMax 2
SET ObjectivesEventState Warning
To create an informative EMS event when process $Abc is not executing in CPU 1:
RANK PROCESS $ABC, CPU = 1 INFO
Status Change Events
ASAP DOTs automatically generates EMS events for Status changes in ASAP system
entities when events are turned on. It uses the operational state—the associated state
for the Status attribute—to determine whether to write an event. The operational state
(OpState) is compared against the value defined in ObjectivesEventState. If OpState is
greater than or equal to that value, an event is generated.
You cannot set objectives against the Status attribute. The operational status of a
domain is always determined by the ASAP component that monitors the domain, and
the associated operational state is set directly by ASAP. For example, if a monitored
process fails, ASAP sets the Status to Down and sets OpState to 8 (the down state.)
You cannot enter an objective to control that behavior.
Therefore, RANK PROCESS, STATUS = “DOWN” is an invalid command because
objectives cannot be set on the Status attribute.
However, to control how ASAP generates events on Status changes, you can enter
event control keywords using the Status attribute. By default, ASAP writes one critical
EMS event when it finds a system object whose OpState passes the event generation
test. If up events are on, it writes one corresponding up event when the object
recovers.
To repeat the event at each interval, to have the event be an informative event, or to
turn off events for the object altogether, use the RANK command: