Defining A Threshold Test - Juniper SYSTEM BASICS - CONFIGURATION GUIDE V 11.1.X Configuration Manual

host1(config-mgmtevent-trigger)#existence-test test-type changed
Define the startup threshold condition absent or present that you want this
2.
trigger to use.
host1(config-mgmtevent-trigger)#existence-test startup absent
Specify the events that you want the existence-test trigger to use by entering an
3.
event owner name and event name.
NOTE: You do not need to bind a failure event to a trigger. If you create a failure
event, if a failure occurs, and if the trigger owner and the event owner are the same,
the router sends the trap.
host1(config-mgmtevent-trigger)#boolean-test event george trigger1
When specifying an event, make sure to use the exact owner name and event
name.
Specify the agent on which the object resides.
4.
host1(config-mgmtevent-trigger)#agent context-name router1
You can obtain the agent context name for a virtual router from the show snmp
agent command. The agent context name is independent of the virtual router
name.
Enable the trigger.
5.
host1(config-mgmtevent-trigger)#enable
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.

Defining a Threshold Test

To define a threshold test:
Define the threshold-test values that you want this trigger to use.
1.
NOTE: The rising value must always be larger than the falling value. Entering a lower
rising value than a falling value will provide invalid results or errors.
absolute-value Use when defining absolute threshold values
host1(config-mgmtevent-trigger)#threshold-test absolute-value rising 2000
falling 1900
delta-value Use when defining delta threshold values
host1(config-mgmtevent-trigger)#threshold-test delta-value rising 2000 falling
1900
Chapter 4: Configuring SNMP
Configuring the SNMP Server Event Manager
183