Configuring the SNMP Server Event Manager

The SNMP server event manager works in conjunction with the Event MIB (RFC 2981). The purpose of this application is to allow many management functions (for example, fault detection, configuration management, accounting management, and performance management).

To configure the SNMP server event manager:

1. Access the SNMP server management event application. For more information about launching the SNMP Server Event Manager Configuration mode, see Launching the SNMP Server Event Manager Mode.

   Note: You must create a management event instance for each virtual router.

   host1(config)#snmp-server management-event host1(config-mgmtevent)#
2. (Optional) Specify the maximum number of trigger entries that you want the virtual router to support. For more information about the limit for total triggers, see Configuring the Limit for Total Triggers Allowed by the Virtual Router.
   host1(config-mgmtevent)#resource 275
3. Create an event for each trap notification (mteTriggerFailure, mteTriggerFalling, or mteTriggerRising) that you want to use by specifying an event owner and event name. For more information about creation of an event, see Creating an Event and Accessing Event Configuration Mode.

   Note: You must create a separate event for each trap notification that you want to use. However, you can specify the trap notification and enable the trap before exiting the event context.

   host1(config-mgmtevent)#event sysadmin failuretrigger host1(config-mgmtevent-event)#exit host1(config-mgmtevent)#event sysadmin fallingtrigger host1(config-mgmtevent-event)#exit host1(config-mgmtevent)#event sysadmin risingtrigger host1(config-mgmtevent-event)#exit
4. Define each event to send a trap notification (mteTriggerFailure, mteTriggerFalling, and mteTriggerRising). For more information about configuring a trap notification for an event, see Configuring a Trap Notification for an Event.

   Note: The mteTriggerFailure notification is a global value. After you create a failure event notification, it is automatically bound to every trigger with the same owner. If a failure occurs, and the trigger owner and the event owner are the same, the router sends the trap.

   host1(config-mgmtevent)#event sysadmin failuretrigger host1(config-mgmtevent-event)#notification id mteTriggerFailure host1(config-mgmtevent-event)#exit host1(config-mgmtevent)#event sysadmin fallingtrigger host1(config-mgmtevent-event)#notification id mteTriggerFalling host1(config-mgmtevent-event)#exit host1(config-mgmtevent)#event sysadmin risingtrigger host1(config-mgmtevent-event)#notification id mteTriggerRising host1(config-mgmtevent-event)#exit
5. Enable the event, and exit the event configuration level. For more information about enabling an event, see Enabling an Event or Trigger Configuration.

   Note: Once enabled, you cannot edit an event or trigger configuration. To change an enabled event or trigger, you must delete it and re-create it.

   host1(config-mgmtevent)#event sysadmin failuretrigger host1(config-mgmtevent-event)#enable host1(config-mgmtevent-event)#exit host1(config-mgmtevent)#event sysadmin fallingtrigger host1(config-mgmtevent-event)#enable host1(config-mgmtevent-event)#exit host1(config-mgmtevent)#event sysadmin risingtrigger host1(config-mgmtevent-event)#enable host1(config-mgmtevent-event)#exit host1(config-mgmtevent)#
6. Define the trigger that you want to use for an event by specifying a trigger owner and trigger name. For more information about creating a trigger, see Creating a Trigger and Accessing Trigger Configuration Mode.
   host1(config-mgmtevent)#trigger george trigger1 host1(config-mgmtevent-trigger)#
7. Specify a MIB object to sample. For more information about sample MIB object configuration, see Specifying the MIB Object to be Sampled for the Trigger.
   host1(config-mgmtevent-trigger)#sample value-id 1.3.6.1.2.1.60.1.2.1.1.7
8. Specify the frequency (in seconds) at which you want the sampling to occur. For more information about MIB sampling frequency, see Configuring the MIB Sampling Frequency.

   Note: Unless you specify that you want to perform delta sampling, the values are absolute.

   host1(config-mgmtevent-trigger)#frequency 100
9. (Optional) Specify that you want to perform delta sampling on the sample value ID. For more information about configuring delta sampling, see Configuring Delta Sampling for the Trigger.
   host1(config-mgmtevent-trigger)#delta-sampling
   • (Optional) Enter the discontinuity MIB value ID that you want to test.
     host1(config-mgmtevent-trigger)#delta-sampling discontinuity-id 1.3.6.1.2.1.31.1.1.1.19.9
   • (Optional) Enter the discontinuity type (timeStamp or timeTicks) that you want the test to use.
     host1(config-mgmtevent-trigger)#delta-sampling discontinuity-id-type timeStamp
10. (Optional) Configure the desired SNMP security level for the agent that you want to poll. For more information about SNMP security access level, see Configuring a Security Access Level for the SNMP Agent.
    host1(config)#snmp security read
11. Define the test values that you want this trigger to use. You can define a Boolean test, existence test, or threshold test. For more information about defining Boolean, existence and threshold tests, see Defining Boolean Test Values for the Trigger, Defining Existence Test Values for the Trigger, and Defining Threshold Test Values for the Trigger.