ASAP 3.2 Server Manual

HP NonStop ASAP Server Manual Page 89 of 381
Other ASAP components autoconfigure a small set of domains. For example, the
Process SGP automatically monitors only the ASAP Monitor process. When you
add a domain to monitor to any subsystem, ASAP turns off autoconfiguration for
that subsystem and only monitors the domains you specified. Adding a single
domain, and turning it OFF in the objectives database, makes ASAP monitor no
domains for the subsystem. For example, MONITOR CPU 1, ADD, OFF makes
ASAP monitor no processors if it is the only CPU object specified in the database,
or if all other CPU domains are also in the OFF state.
 DOTs lets you set simplex, escalating and Boolean thresholds on any attribute or
attributes for any domain. Using the ASAP CI GOAL or RANK command, you set
thresholds for subsystems and domains within subsystems on the attributes that
are important to you. For example, RANK CPU 0, BUSY < 90 sets a simplex
objective on the Busy attribute for CPU 0 that it must be less than 90 percent busy.
RANK CPU 1, QUEUE < 1 sets an objective for CPU 1 that the queue length
must be less than 1. RANK CPU, CHIT > 25 sets a global objective for all
processors that the cache hit rate must be greater than 25.
You set objectives using any of six operators for simplex objectives: greater than >;
less than <; equal to =; not equal <>; greater than or equal to >=; and less than or
equal to <=. A single attribute can have an objective for each operator.
For example, RANK PROCESS $ABC, CPU > 2, CPU <> 5 sets two simplex
objectives on the Process CPU attribute, process $ABC must execute in a
processor greater than 2 but not in processor 5. ASAP does not prevent you from
setting objectives that are illogical and causes alerts at each interval. For example,
RANK PROCESS $ABC, CPU < 1, CPU > 1 cause an alert at each interval
since the process cannot be in a processor less than 1 and a processor greater
than 1.
Escalating objectives define up to three levels of less than or greater than
thresholds for an attribute where each level has a different alert level and can have
unique actions and events. For example, GOAL CPU 1, BUSY < 40, BUSY <<
60, BUSY <<< 80 defines 3 levels of alerting for the CPU Busy attribute for CPU
1. If the CPU is 45% busy the alert level will be a high alert; if the CPU is 65%
busy the alert level will be a warning alert; and if the CPU is 85% busy the alert
level will be a critical alert. The alert levels are predefined and are not controlled
by the SET OBJECTIVESRANK setting.
Four operators are used to defined escalating goals: level 2 less than <<; level 3
less than <<<; level 2 greater than >>; and level 3 greater than >>>. When goals
are defined using the level 2 or level 3 less than operators they are considered to
be escalating goals and the value specified at each level should increase. When
they are defined using level 2 or level 3 greater than operators they are considered
to be descalating goals and the value specified should decrease at each level.
Like simplex objectives, ASAP does not prevent you from setting illogical values for
escalating goals.