ASAP Migration Guide for NSX and OMF Users

ASAP Installation and Configuration
ASAP Migration Guide for NSX and OMF Users—520627-001
2-3
Adding or Deleting Domains
In ASAP 2.0, for performance and multithreading purposes, most entities have a private
SGP process that collects statistics. Before starting ASAP components on a node, you
must decide which entities to enable. When you start ASAP, the ASAP Monitor starts
the associated entity SGPs.
To enable an entity, use the ASAP SET entity ON|OFF command. If you put these
commands in the ASAP configuration file (ASAPCONF), you do not have to re-enter
them for each startup. To verify the results, use the ASAP SET command alone:
+ SET DISK OFF
+ SET TMF OFF
+ SET FILE ON, PARAM “RATE 10”
+ SET
Once you enter your SET commands, use the ASAP START node command to start
monitoring this node. Before you start another node, you can use the SET entity
commands to monitor different entities on that node, then start the other node. Once you
determine how you want each node configured, you can avoid re-entering your settings
by putting all your settings in an OBEY file that you can always use for startup. To
check the status of the startup, enter LOG node.
By default, these entities are set to ON: CPU, File, Process, ProcessBusy, and System.
When an entity is ON, ASAP Monitor starts its associated SGP. If you add domains for
an entity or let autodiscovery do it for you, statistics are collected for that entity.
Adding or Deleting Domains
In NSX, you had no control over which objects were monitored for an entity: when the
Disk entity was ON, all disks on the system were monitored.
In OMF, you had total control over which objects were monitored. You could add or
delete them using the block-mode interface or OMFCOM.
ASAP 2.0 follows the OMF model but uses different syntax. To specify which domains
to monitor, use the ASAP MONITOR command. For example:
+ MONITOR PROCESS $Funds
+ MONITOR PROCESS $Atms
+ MONITOR FILE $System.System.Userid
+ COMMIT
Also consistent with continuous availability requirements, you can remove objects from
service at any time. For example, monitoring of process $Xyz could be temporarily
suspended or stopped altogether with either of these commands:
+ MONITOR PROCESS $Xyz, OFF -- suspends monitoring, keeps object in data base
+ MONITOR PROCESS $Xyz, DELETE -- removes object from objectives data base
+ COMMIT
When you use the MONITOR command, the results are immediately stored in the
ASAP Objectives DB database. This database contains the list of domains to monitor
and the objectives for each domain.
If ASAP is running, you must use the COMMIT command to make the SGPs pick up
new changes from the Objectives DB. If ASAP is not running, the COMMIT command
is not required. The next time you start ASAP, the new list of domains is picked up. For
more information, see Dynamic Configuration
on page 2-4.