ASAP 3.2 Server Manual

HP NonStop ASAP Server Manual Page 41 of 381
different sub-entities and ASAP record types to report CIP information to the ASAP
Collector process.
COMM Statistics Gathering Process
Communication SGPs collect availability for all communication lines configured on the
node or only user-specified communication lines on the node. This process uses the
Measure subsystem programmatic interface for collecting raw communication
performance counters. The COMM SGP reports on objective thresholds that exceed
the user-defined values maintained in the objectives database.
The COMM SGP gathers availability information, bundles it in a single message, and
forwards it to the ASAP Collector process. The Collector process unpacks the
information and stores it in the normalized ASAP database so the ASAP COMM
command or ASAP client can retrieve it.
CPU Statistics Gathering Process
The remote ASAP Monitor starts the CPU SGP in each CPU of the monitored node.
CPU SGPs are responsible for gathering CPU-level statistics, including CPU
performance metrics, Operational state, and information about the busiest processes
in their CPU.
The CPU SGPs reports CPU-level information to the ASAP Monitor process. The
Monitor bundles it in a single message and forwards it to the ASAP Collect process on
the main Collection node. The Collect process parses this information and stores it in
the normalized ASAP database. You can then display the data with the ASAP CPU
and PROCESSBUSY commands, or with various block-mode or workstation programs.
Disk Statistics Gathering Process
Disk SGPs collect disk availability information for all non-phantom disks on the node.
These processes use the Measure subsystem programmatic interface for collecting
raw disk process counters. They do not use the Measure subsystem for determining
performance counters, disk capacity utilization, or operational state information. The
Disk SGP reports on objective thresholds when they do not meet the user-defined
values.
The Disk SGP gathers availability information, bundles it in a single message, and
forwards it to the ASAP Collect process. The Collect process unpacks the information
and stores it in the normalized ASAP database so the ASAP DISK command or ASAP
Client can retrieve it.
Expand Statistics Gathering Process
Expand SGPs collect Expand availability information for all Expand lines on the node.
These processes use the Subsystem Programmatic Interface (SPI) for communicating