ASAP Migration Guide for NSX and OMF Users

DOTs, EMS Events, and Other Features
ASAP Migration Guide for NSX and OMF Users—520627-001
3-2
DOTs and EMS Events
Valid
Type
Et
Busy
Busystate
Queue
Queuestate
Disp
Dispstate
more attributes…
In this CPU example, any attribute followed by an attribute with the same name plus the
word "state" can accept objectives; for example, "Busy" followed by "BusyState".
Objectives are set against the attributes, not the state; for example, Busy, Queue, Disp.
Adding the state suffix to an attribute does not automatically make it a state pair. EDL
identifies state pairs with the StatePair Yes specification. The only exception is the
attribute for which EDL specifies StateIsOp Yes. This attribute, often called Status, is
reserved to reflect the overall operational state of an object.
When setting objectives, you can decide what type of EMS event is generated, if any,
when the objective is not met. You can also specify whether to repeat the event at each
interval or issue it only once. To specify objectives and configure EMS event
generation, use the ASAP RANK command. For example:
•
To set the service-level-availability objectives of CPU 5 to be less than 55% busy,
and its Queue less than 4, and all other CPUs to be less than 70% busy:
+ RANK CPU, Busy < 70
+ RANK CPU 5, Busy < 55, Queue < 4
•
To repeatedly generate critical EMS events if the RWEP is not OOOO for the
system Userid file:
+ RANK FILE $System.System.Userid, RWEP = "OOOO" CRITICAL
REPEAT
Once you define all your objectives using the RANK command, use the COMMIT
command to see the changes, which are applied at the next sample.
To generate EMS events, enable EMS event generation with this ASAP command:
+ SET OBJECTIVESEVENT ON
EMS event generation in ASAP is also controlled by other SET command options:
OBJECTIVESEVENT, OBJECTIVESEVENTUP, OBJECTIVESEVENTCONSOLE,
OBJECTIVESEVENTCONSOLEUP, OBJECTIVESEVENTSTATE, and
OBJECTIVESEVENTMAX. These options offer extensive control over EMS event
generation. For more details, see the ASAP Server Manual.
Objectives are stored in the Objectives database. To configure the location of this
database, use the SET OBJECTIVESDB command. When you shut down ASAP and
restart it, all your previously configured objectives apply. If you are configuring
multiple nodes, the SET Objectives DB volume name must be present on each node that
you start, because objectives are kept on the node where they are specified.