Juniper SYSTEM BASICS - CONFIGURATION GUIDE V 11.1.X Configuration Manual page 217

frequency
notification id
resource
CAUTION: When assigning wildcards, make sure to allow for enough trigger resources.
sample
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
Use the no version to remove the notification from the event. Removal returns
the notification value to its default (0.0)
See notification id.
Use to specify the total number of triggers that the virtual router allows.
Example
host1(config-mgmtevent-event)#resource 250
Use the no version to restore the default resource value (50).
See resource.
Use to specify the MIB object that you want to sample for the trigger that you
are configuring.
Example
Chapter 4: Configuring SNMP
Configuring the SNMP Server Event Manager
187