ASAP 3.2 Server Manual

HP NonStop ASAP Server Manual Page 96 of 381
using the Linux application
API
RDF
$ZOON
DBRDF
All RDF environments with
RDF configuration files on
$SYSTEM
SPOOLER
$ZOOO
DBSPL
$SPLS
SWAP
$ZOOA
DBSWP
All configured KMSF swap
files
SYSTEM
$ZOOn (n=0
through 15)
DBSYS
Average utilization for all Up
CPU’s
TAPE
$ZOOQ
DBTAP
All SYSGENed tape drives
TCP/IP **
$ZOOV
DBTCP
All TCP/IP Processes,
Routes and Subnets, and
Telserv Processes
TMF
$ZOOR
DBTMF
All TMF components
* The Expand SGP is a multi-entity (Expand and ExpandIP) SGP. Use the Expand entity for setting monitoring of
any Expand line. For use of the MONITOR command for Expand and ExpandIP, see System Entity Specifics.
**The SGP is a multi-entity SGP. For more information, see System Entity Specifics.
GOAL and RANK Usage Considerations
Use the GOAL and RANK commands to set simplex, escalating or Boolean objectives
on any attribute defined in EDL that has an associated state (StatePair Yes). A
simplex objective is a single goal set on an attribute; an escalating objective defines
multiple alert levels for the same attribute; and a Boolean objective combines several
goals into a single alert indicator.
For example, to set a global simplex objective for all CPUs to less than 90% busy with
a queue length less than 2, then override it with a specific objective on CPU 2 that its
queue length must be less than 1:
GOAL CPU, BUSY < 90, QUEUE < 2
GOAL CPU 2, QUEUE < 1
Note
GOAL and RANK are synonyms for the same command. You can interchange
them at will.
To designate that Informative or Critical EMS events be generated when a simplex or
escalating objective is not met, specify one of the keywords in the GOAL or RANK
command. For example, to specify that a critical EMS event be generated if CPU 4 is
busier than 95% and to repeat the event at each interval where the condition persists:
RANK CPU 4, BUSY <= 95 CRITICAL REPEAT