ASAP 3.2 Server Manual

HP NonStop ASAP Server Manual Page 97 of 381
For ASAP to generate EMS events, you must turn EMS event generation on as
described in EMS Event Considerations. To load objective database changes into a
running copy of ASAP, you must use the COMMIT command.
EMS Event Considerations
ASAP generates two classes of events:
 Normal status and problem events describing ASAP operation
These are events such as component startup messages or error messages when a
component cannot obtain a system resource. They are written to EMS and the
ASAPLOG log file, and are subject to event suppression if turned on within ASAP.
 Events generated by DOTs to describe the status of objects (domains) being
monitored by ASAP
DOTs events are not written to the ASAPLOG log file or subject to event
suppression within ASAP. Because the ASAP Client provides many features for
monitoring the state of monitored domains, DOTs EMS event generation is turned
off by default.
ASAP DOTs can generate EMS events for status changes and for failed objective
comparisons:
 To turn on ASAP generation of down EMS events (ASAP event 4000) for failed
domains and objectives, place the SET ObjectivesEvent ON command in your
ASAPCONF file.
 To turn on the corresponding up event (event 4001) when the domain or objective
recovers, place the SET ObjectivesEventUp ON command in your
ASAPCONF file.
ASAP generates down events for a domain whenever the state for a goal configured to
generate events is greater than or equal to the state specified in the SET
ObjectivesEventState command. The default is CRITICAL, meaning that ASAP
generates an EMS event when attribute states are critical or down. To generate events
for warnings or lesser alert conditions, include the SET ObjectivesEventState
command in your ASAPCONF file.
ASAP also lets you control the number of events written per domain. The SET
ObjectivesEventMax value determines how many events ASAP writes per interval
for a domain. The default is one, meaning ASAP writes one EMS event per domain.
For simplex or escalating goals the event will be written for the goal set on the first
attribute configured for events whose state is greater than or equal to the
ObjectivesEventState. Since escalating goals can create High, Warning and Critical
alerts ObjectivesEventState should be set to HIGH or lower to generate events and/or