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-2
Add Listdev -> add listdev +monitor disk $data
+monitor tape $tape1
+monitor expand $lhdom
Delete a Process -> delete process $Xyz +monitor process $Xyz,
delete
Suspend
monitoring of a
Process
Not supported +monitor process $Xyz,
off
Specify the
primary CPU of
a process
-> alter process $Xyz,
default-cpu 1
+rank process $Xyz,
cpu=1
Do not care
about the Priority
of a process
-> alter process $Xyz,
monitor-priority N
Do not issue any RANK
command on the Priority attribute
for that process
See how a
process is
configured
-> info process $Xyz +rank process $Xyz
Modify EMS
event generation
-> alter process $Xyz,
odd-event C
+rank process $Xyz,
cpu=1 Critical
Repeat EMS
event
Not supported +rank process $Xyz,
cpu=1 Critical Repeat
Don’t display
EMS event on
Console
-> alter process $Xyz,
odd-display N
+rank process $Xyz,
cpu=1 Critical Repeat
NoDisplay
Save
configuration
-> info process $Xyz,
obeyform
+monitor process $Xyz,
obeyform
+rank process $Xyz,
obeyform
Display Process
statistics on
current node
-> status process * +process
Display Process
statistics on all
nodes
-> set system \NodeA
-> status process *
-> set system \NodeB
-> status process *
+process \*
Table B-1. OMFCOM Versus ASAP 2.0 Commands (page 2 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.