ASAP Migration Guide for NSX and OMF Users

OMFCOM Versus ASAP 2.0 Commands
ASAP Migration Guide for NSX and OMF Users—520627-001
B-3
Monitor disk
Primary CPU
Available when monitoring Listdev +monitor disk $data
+rank disk $data,
cpu=1 Critical
Monitor Primary
disk controller
path
Available when monitoring Listdev +monitor disk $data
+rank disk $data,
P=”P” Critical
Monitor Mirror
disk controller
path
Available when monitoring Listdev +monitor disk $data
+rank disk $data,
M=”B” Critical
Note. In ASAP 2.0, once all your configuration changes are complete, issue the COMMIT
command to activate those changes. Results appear at the next sample.
To generate EMS events with ASAP 2.0, enable EMS event generation using: SET
OBJECTIVESEVENT ON, and include specific event generation parameters with each RANK
command.
Table B-1. OMFCOM Versus ASAP 2.0 Commands (page 3 of 3)
Function OMFCOM ASAP 2.0
* OMF had some default threshold values; for example, all CPUs had a default busy threshold of 90%. In
ASAP, you can select an object to monitor, but do not have to specify objectives for an attribute. You can also
specify global attribute objectives; for example, RANK CPU, BUSY < 90 Critical which applies to all CPUs,
or identify objectives for a particular CPU; for example, RANK CPU 3, BUSY < 75 Info. With ASAP, users
get greater flexibility in choosing attribute objectives.