Administration Guide › Action Alerts › Working with SNMP Traps › About MIB Files › MIB Usage Considerations

MIB Usage Considerations

For a system to understand an SNMP trap it receives from CA Enterprise Log Manager using MIBs, it must know what the composing OIDs define. Requirements follow:

• Import and compile the CA-ELM.MIB file; keep this file updated.
• (CA NSM only) Create, import, and compile one custom MIB for each scheduled alert sent as an SNMP trap.

  Note: The same custom MIB can be used for alerts based on queries that send the same fields in the same order as a trap.

  For example, the following queries all return values for the fields dest_hostname and event_count.

  • Five Failed System Access by System
  • Failed Restore Activity in Last Seven Days by Host Summary
  • Failed Backup Activity in Last Seven Days by Host Summary
  • Excessive (25) Configuration Failures in Last Hour
  • Excessive (25) Configuration Changes in Last Hour
  • Excessive (25) SU Activity by Host in Last Hour
  • Critical or Fatal Events on Critical Host Summary

  If you create separate alerts based on these queries, those alerts would specify the same Custom Trap ID and would be interpreted with the same custom MIB.

Individuals who monitor the SNMP traps received at the destination product can interpret traps sent from CA Enterprise Log Manager in two ways:

• Launch the SNMP trap results page from the URL sent in the trap.
• Use an application that references imported MIBs.