Configuration Tasks

To configure the SNMP server event manager:

1. Access the SNMP server management event application.

   host1(config)#snmp-server management-event

   host1(config-mgmtevent)#

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

2. (Optional) Specify the maximum number of trigger entries that you want the virtual router to support.

   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.

   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

   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.

4. Define each event to send a trap notification (mteTriggerFailure, mteTriggerFalling, and mteTriggerRising).

   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

   Note: The mteTriggerFailure notification is a global value. Once 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.

5. Enable the event, and exit the event configuration level.

   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)#

   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.

6. Define the trigger that you want to use for an event by specifying a trigger owner and trigger name.

   host1(config-mgmtevent)#trigger george trigger1

   host1(config-mgmtevent-trigger)#

7. Specify a MIB object to sample.

   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.

   host1(config-mgmtevent-trigger)#frequency 100

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

9. (Optional) Specify that you want to perform delta sampling on the sample value ID.

   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.

    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. See the following sections for procedures.

Copyright © 2008, Juniper Networks, Inc. All rights reserved. Trademark Notice.