ASAP 2.8 Server Manual

Using Discrete Object Thresholds (DOTs)
HP NonStop ASAP Server Manual—522303-007
4-2
DOTs Overview
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 discrete thresholds on any attribute for any domain. Using the
ASAP CI 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 the 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: 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 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.
•
DOTs lets you define recovery actions to be to taken when objectives are not met.
Using the ACTION parameter to the ASAP CI RANK command, a user can define
commands to be sent to command interpreters such as SCF and TACL when
specific objectives are not met. For example, the command RANK CPU, STATUS
ACTION "TACL RELOAD <#OBJECT>, PRIME" WAIT 5 causes ASAP to
automatically reload a failed CPU, waiting 5 minutes between attempts. The token
named <#OBJECT> is automatically replaced in the action string with the number
of the failed processor. Other tokens that you can use in action strings:
<#ENTITY> The entity name
<#OBJECT> The NonStop OS or OSS object name
<#DOMAIN> The domain name
<#D1> Leftmost part of a multilevel domain name
<#D2> 2nd part of a multilevel domain name
<#D3> 3rd part of a multilevel domain name
<#D4> 4th part of a multilevel domain name
<#D5> 5th part of a multilevel domain name
<#ATTR> The attribute name
<#OP> The objective operator
<#STATE> The current state of the attribute