Help us improve your experience.

Let us know what you think.

Do you have time for a two-minute survey?

Guide That Contains This Content
[+] Expand All
[-] Collapse All

    Defining Existence Test Values for the Trigger

    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. You can use the existence-test command 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 existence-test command. You can specify one, two, or all three test types in the same existence-test command.

    You can use the no version of the existence-test command to delete the existence-test values for this trigger or to remove either the startup condition or event binding.

    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. When specifying an event, make sure to use the exact 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)#existence-test event george trigger1
    4. Specify the agent on which the object resides. 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. For more information about configuring the SNMP agent name, see Configuring the Virtual Router SNMP Agent on Which MIB Objects Are to Be Polled.
      host1(config-mgmtevent-trigger)#agent context-name router1
    5. Enable the trigger. For more information about enabling the trigger, see Creating a Trigger and Accessing Trigger Configuration Mode.

      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.


    Published: 2014-08-12