Defining an Existence Test

An existence test looks for the existence of a MIB object. The appearance, disappearance, or a change in value of the object can trigger the existence test.

To define an existence test:

1. Define the existence test test-type value that you want this trigger to use.

   host1(config-mgmtevent-trigger)#existence-test test-type changed

2. Define the startup threshold condition—absent or present—that you want this trigger to use.

   host1(config-mgmtevent-trigger)#existence-test startup absent

3. Specify the events that you want the existence-test trigger to use by entering an 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.

4. Specify the agent on which the object resides.

   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.

5. Enable the trigger.

   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.

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