ASAP Migration Guide for NSX and OMF Users

ASAP Installation and Configuration
ASAP Migration Guide for NSX and OMF Users—520627-001
2-4
Autodiscovery
Autodiscovery
In NSX, autodiscovery of objects was automatic. You had no control over which objects
were monitored.
In OMF, if the OMFDB database was not present, autoconfiguration occurred. For most
object types, all objects discovered on the system were automatically added to the OMF
configuration and monitored.
ASAP 2.0 also offers automatic discovery of domains. When an SGP starts up and does
not find a domain to monitor in the Objectives DB, it discovers its own set of domains
and starts monitoring them.
For each entity, autodiscovery occurs only when no domains of that entity exist in the
Objectives DB. If at least one domain is configured in the Objectives DB for that entity,
even if its monitoring attribute is set to OFF, autodiscovery does not occur.
Dynamic Configuration
Object selectivity did not apply to NSX, but it applied to OMF. OMF users could add,
modify, or delete specific objects while OMF was running.
Using the ASAP MONITOR command, you can add, modify, or delete domains from
the configuration. Once you configure the domains to monitor, you commit those
changes using the ASAP COMMIT command:
+ MONITOR PROCESS $Funds
+ MONITOR PROCESS $Funds, OFF
+ MONITOR PROCESS $Xyz
+ MONITOR PROCESS, INFO
Table 2-1. Domain Autodiscovery for ASAP Entities
Entity Autodiscovers...
APP User defined
CPU All CPUs
Disk All disk volumes
Expand All Expand lines
File $System.System.Asapmon
Node All nodes on the network
Process AsapIdM (for example, $ZOOM)
ProcessBusy Busiest processes in all CPUs
RDF All RDF environments defined on $SYSTEM
Spooler $Spls, the default spooler supervisor
System Local node
Tape All tape devices
TMF Auditdump, Audittrail, TMF, Transactions