ASAP 3.0 QuickStart Guide

HP NonStop ASAP QuickStart Guide Page 25 of 35
Section 4: Monitoring Objects
The ASAP installation wizard (ASAPWIZ) helped you configure the startup settings for ASAP
server, but that doesn’t mean ASAP is configured to provide you the information you need to
manage your environment. It only means that ASAP has been primed so that you can
configure it to manage your environment.
The first thing you need to decide when using ASAP is the set of objects that you will
monitor. Most ASAP SGPs (subsystem monitors) will auto-configure all objects that are
defined for the subsystem they monitor. However, there are some SGPs that require you to
define the complete set of monitored objects for that particular subsystem.
Let’s start with the CPU entity. By default ASAP will monitor all CPUs that have been
configured for your system. In the early days, your NonStop system would have been
configured in the factory for the number of CPUs it actually contained. But beginning several
years ago, all systems have been configured for 16 processors even if fewer processors are
present. This was done to facilitate on-line additions while minimizing downtime on your
system.
Since ASAP reads the number of configured processors, for any newer system it expects 16
processors and attempts to report data on all 16 CPUs. If your system doesn’t have 16
CPUs then ASAP will report the missing CPUs as being down. When this happens, you
need to configure ASAP to only monitor the CPUs that really exist, and this is a good
introduction to the concept of Monitoring specific objects.
Let’s assume you have a 4-processor system. When you first start ASAP it will report
processors 0-3 as being UP, and will report processors 4-15 as being down. You need to
tell ASAP to only monitor the 4 processors that you have purchased. Use the ASAP
MONITOR command to do this by running the ASAP command interpreter and telling it you
are only interested in monitoring CPUs 0-3.
ASAP
+ MONITOR CPU 0
+ MONITOR CPU 1
+ MONITOR CPU 2
+ MONITOR CPU 3
You have now updated the permanent ASAP monitored objects and goals database to tell
ASAP that you only want to monitor the first 4 CPUs on your system. However you have
only updated ASAP’s database; to tell the running copy of ASAP you must commit the
changes you have made. You do this by entering the COMMIT command, which tells ASAP
to do an online load of all the changes you have made to the database and to start using
that configuration immediately. This two-step process is used to allow you to make multiple
configuration changes via MONITOR commands without having each change immediately