Designing and Managing Behavior Models - Using Other Data Sources - Veritas Manage Exec - Manage Exec Trap Contents -
Previous: Variable Bindings in a Manage Exec Trap     Next: HP OpenView IT/Operations

Manage Exec Trap Contents

When a trap arrives from Manage Exec, the specific trap number indicates whether Manage Exec has set (created) or cleared an alert. It also indicates the severity of the alert that was created or cleared. The specific trap number doesn't, however, tell you anything about what condition caused the alert. This information is represented in the trap's variable bindings. You can retrieve the value of this variable binding using the variable-binding function VbValue(). (For complete information about the variable-binding functions, see the section Variable-Binding Functions.)

---

Note    If you're familiar with the Windows NT Performance Monitor program, you can use that program to get some documentation about the objects and counters. If you bring up the Add to Chart, Add to Alert, or Add to Report dialog, you can select the counter you're interested in and then select the Explain button.

---

The following figure shows trap information in the stream coming directly from the agent as it's received by NerveCenter.

Trap Information Direct from the Agent

The following table identifies each trap object in the preceding figure and what each means:

Key to Trap Objects

With the trap masks that you create for Manage Exec, you can build a NerveCenter behavior model to correlate these traps to evaluate alert conditions. For example, if NerveCenter detects threshold alarms for CPU utilization, memory, and disk I/O, the behavior model you create can help you to determine which of these conditions is actually affecting system performance. For more information, see the section, Constructing Behavior Models.