ASAP 2.8 Server Manual

HP NonStop ASAP Server Manual—522303-007
4-1
4
Using Discrete Object Thresholds
(DOTs)
DOTs let users set discrete objectives and recovery actions against specific attributes
for any domain within an ASAP entity. DOTs also let users selectively monitor specific
objects (domains), and provide an event generation service.
DOTs are implemented within ASAP by:
•
Providing a database to store and retrieve domain names, objective values, and
recovery actions
•
A user command interface (ASAP CI)
•
A recovery action service
•
Automatic event generation service
•
An internal service for calculating the ASAP OEM states and retrieving information
from the database
DOTs Overview
DOTs provide services to ASAP users in four ways:
•
DOTs let you choose the objects to monitor with ASAP. Using the ASAP CI
MONITOR command, you enter the list of objects (domains) in each subsystem to
monitor with ASAP. For example, MONITOR CPU 1 makes ASAP monitor
processor 1. ASAP does not monitor any other processors unless they are
included in the list to monitor.
Many ASAP components autoconfigure domains at startup if you do not enter any.
For example, the Disk SGP automatically monitors all disk drives.
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
Topic Page
DOTs Overview
4-1
MONITOR Usage Considerations 4-6
GOAL and RANK Usage
Considerations
4-7
EMS Event Considerations 4-7
System Entity Specifics 4-11