Designing and Managing Behavior Models - Using Other Data Sources - Veritas Manage Exec -
Previous: An Example Trigger Function     Next: Creating Trap Masks for Manage Exec NT Agents

Veritas Manage Exec

The section Integration with Veritas Manage Exec introduced the Manage Exec product and explained that it can be integrated with NerveCenter. Using these two products together, you can detect and correlate system conditions on Windows NT workstations and servers.

Briefly, here's how you integrate the two products. On the Manage Exec side, you use Alert Agents to monitor the use of system resources on Windows NT machines and to establish threshold crossings that will result in alerts being generated. Either an Alert Agent or the Alert Server can translate an alert into an SNMP trap and forward that trap to a machine running the NerveCenter server. On the NerveCenter side, you create a trap mask to receive the trap. The only things special about the trap masks you use to receive traps from Manage Exec are that:

• For the trap's enterprise OID, you must supply the OID of the Manage Exec trap agent.
• For the trap mask's specific trap number, you must supply a specific trap number defined in the Manage Exec MIB. These trap numbers define only whether an alert is being created or cleared and the priority (severity) of the alert.
• You must use a trigger function to determine the exact nature of the problem, for example, high CPU utilization. A code describing the problem is contained in one of the trap's variable bindings, and the meanings of the codes are explained in a file that ships with Manage Exec.

For further information about receiving traps from Manage Exec, see the following sections:

• Creating Trap Masks for Manage Exec NT Agents
• Manage Exec's Specific Trap Numbers
• Variable Bindings in a Manage Exec Trap
• Manage Exec Trap Contents