ASAP 2.8 Server Manual

Using Discrete Object Thresholds (DOTs)
HP NonStop ASAP Server Manual—522303-007
4-3
Specifying Domains and Objectives
Action strings can also be stored as predefined rules by using the ASAP CI
ACTION command. ASAP creates an initial set of predefined rules automatically,
including one called RELOAD that executes the TACL RELOAD command. The
command RANK CPU, STATUS ACTION RELOAD WAIT 5 uses the predefined
ASAP action rule instead of the TACL command string as shown in the previous
example.
•
DOTs lets you generate EMS events when objectives are not met. Using the ASAP
CI RANK command, you set objectives on attributes for any domain and include
event generation keywords to make ASAP generate events.
For example, RANK CPU 1, BUSY > 15 CRITICAL REPEAT makes ASAP
generate a critical EMS event when percent busy for processor 1 drops to 15% or
below and keeps repeating that event for each interval where the problem persists.
DOTs require that you define entities using the ASAP Entity Definition Language (EDL)
and that entity information is available for each caller of the DOTs API.
EDL lets you describe entity information required for the ASAP Client, Server, and
Extension. Each product shares some information from EDL, and each has specific
requirements for EDL information. ASAP Server must also keep non-EDL information
in memory for each entity. For more information on EDL, see the ASAP Client Manual.
Specifying Domains and Objectives
The MONITOR command controls which objects, or domains, ASAP monitors. If no
domains are specified, ASAP autoconfigures the domains it monitors. For example, if
you SET DISK ON, all disks are monitored unless you use the MONITOR command to
select specific disks.
Once a domain is monitored, use the RANK command to set availability and
performance objectives for that domain. When a ranked property upper or lower bound
threshold is exceeded, the state of the ranked property is assigned an alert state.
States in ASAP describe the status of a property such as up, down, warning, or critical.
States can also indicate utilization such as low, medium, and high. ASAP displays
ranked alert states in the ASAP Client, the EMS subsystem, or both.
To enable ranked property alerts in the ASAP Client, set State Determination to
UseStateGraphState for each ranked property in the ASAP Client Attribute Property
sheet. For more information, see the ASAP Client Manual.
To enable ranked property events in EMS, SET OBJECTIVESEVENT ON from the
ASAP command interpreter before starting ASAP Server components. For more
information, see SET OBJECTIVESEVENT on 6-103.
<#LASTSTATE> The last state of the attribute
<#VALUE> The value of the attribute
<#GOAL> The objective value