Juniper JUNOSE SOFTWARE FOR E SERIES 11.3.X - SYSTEM BASICS CONFIGURATION GUIDE 2010-10-04 Configuration Manual page 205

existence-test
frequency
notification id
Copyright © 2010, Juniper Networks, Inc.
Use to create an event and access the event configuration mode of the SNMP server
event manager.
Example
host1(config-mgmtevent)#event sysadmin failuretrigger
host1(config-mgmtevent-event)#
To leave the event configuration mode, use the exit command.
Use the no version to remove the event.
See event.
Use to define existence test values for the trigger that you are configuring, including
binding an event to the existence-test trigger, specifying a startup condition, and
defining an existence-test type.
You can specify one or both startup conditions in the same command. You can specify
one, two, or all three test types in the same command.
Example 1—Binding an event to the Boolean-test trigger
host1(config-mgmtevent-trigger)#existence-test event sysadmin existenceTrigger
Example 2—Specifying a startup condition
host1(config-mgmtevent-trigger)#existence-test startup present
Example 3—Specifying an existence test type
host1(config-mgmtevent-trigger)#existence-test test-type absent
Use the no version to delete the existence-test values for this trigger or to remove
either the startup condition or event binding.
See existence-test.
Use to set the frequency (in seconds) at which you want MIB sampling to occur.
Example
host1(config-mgmtevent)#frequency 100
Use the no version to restore the default frequency value (600 seconds).
See frequency.
Use to specify a trap notification for an event.
Example
host1(config-mgmtevent-event)#notification id mteTriggerFailure
Chapter 4: Configuring SNMP
175