

Administration Guide › Action Alerts › Working with SNMP Traps › About MIB Files › Example: MIB Tree for Custom MIB 33
Example: MIB Tree for Custom MIB 33
The MIB tree for a custom MIB differs from the MIB tree for CA-ELM.MIB in the following ways:
- The objects under elmAlertVariables are limited to the fields in the query. Consider the example where the selected fields are:
- event_datetime
- event_trend
- The elmTrap that contains only the query fields replaces elmTrap (1) in CA-ELM.MIB, which contains all CEG fields. Consider the example where the elmTrap is 33. This elmTrap identifier references the final node of the Custom Trap ID, which is 1.3.6.1.4.1.791.9845.3.33.
A depiction of Custom MIB 33 in MIB tree format follows, where the highlighted blocks indicate differences between this custom MIB and the CA-ELM.MIB. The custom MIB defines only two fields under elmAlertVariables. The custom elmTrap includes only the two query fields and has a unique number, 33. The elmDataGroup includes only the two query fields.
Copyright © 2013 CA.
All rights reserved.
 
|
|