ASAP Migration Guide for NSX and OMF Users

ASAP Migration Guide for NSX and OMF Users—520627-001
3-1
3
DOTs, EMS Events, and Other Features
DOTs and EMS Events
In NSX, you could set thresholds on only some attributes of the CPU, Disk, Expand, and
Process[Busy] entities.
In OMF, you could set thresholds on a per-object basis, and decide what type of EMS
event message was generated if the threshold was exceeded. However, OMF was limited
in the types of attributes reported, did not provide lower bound thresholds, and could not
generate repeating events.
In ASAP 2.0, you can set upper and lower bound thresholds on:
•
A per-object basis
•
A subdomain basis; for example, ATM\Chicago\Loop and ATM\Chicago
Thresholds in ASAP are most often referred to as Discrete Object Thresholds (DOTs).
Because ASAP monitors availability, for each attribute that has a state pair, you can
define objectives that are upper bound, lower bound, or both. If an objective is not met,
an alert state is raised in the ASAP Server and propagated to the ASAP Client.
The centrally administered objectives discussed here are not the only way to achieve
state determination. For a discussion about state determination, see the ASAP white
paper on the internet at http://nonstop.compaq.com/view.asp?IOID=5664.
To determine which attributes can have centrally administered objectives, use the ASAP
SHOW entity command:
+show cpu
Cpu
Nodename
Sysnum
Cpu
Status
Op
Date
Time
Topic Page
DOTs and EMS Events 3-1
Sampling Rate 3-3
ASAPCONF File 3-3
Network Time Synchronization 3-3
Network Statistics Collection 3-4