Defining a Threshold Test

To define a threshold test:

1. Define the threshold-test values that you want this trigger to use.

   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

2. Define the startup threshold condition that you predict the sample to initially follow—falling, rising, risingorfalling. For example, if you are sampling a MIB value that you know will start from zero and rise, you would specify a rising startup condition.

   host1(config-mgmtevent-trigger)#threshold-test startup rising

3. Specify the events (rising or falling) that you want the threshold-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)#threshold-test event falling sysadmin fallingtrigger

   host1(config-mgmtevent-trigger)#threshold-test event rising sysadmin risingtrigger

   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.

agent context-name

• Use to specify the virtual router SNMP agent on which you want to poll MIB objects.
• The default is the current context (virtual router).
• The contextName value is the virtual router number in the order the virtual router was created (for example, router1, router2, and so on). Use the show snmp agent command to obtain the context name for the virtual router.
• Use the wildcard keyword to specify that the context name is a wildcard value.

  Note: Use caution when assigning wildcards. Wildcards can rapidly use up trigger resources.

• Use the limit keyword to specify the maximum number of agents to be polled.
• Example 1

  host1(config-mgmtevent-trigger)#agent context-name router1 wildcard

• Example 2

  host1(config-mgmtevent-trigger)#agent context-name router1 wildcard limit 15

  Note: SNMP server security defaults to “ no access.” When using a separate virtual router, you must use the snmp-server security command and provide “ read” or “ read-write” access to other virtual routers.

• Use the no version to return to the default context (virtual router).
• See agent context-name.

boolean-test

• Use to define Boolean test values for the trigger that you are configuring, including comparison settings, a Boolean value, a startup condition, and binding an event to the Boolean-test trigger.
• Example 1—Specifying a comparison setting

  host1(config-mgmtevent-trigger)#boolean-test comparison less

• Example 2—Specifying a Boolean value to which the test compares

  host1(config-mgmtevent-trigger)#boolean-test value 5175438

• Example 3—Binding an event to the Boolean-test trigger

  host1(config-mgmtevent-trigger)#boolean-test event sysadmin booleanTrigger

• Example 4—Setting the trigger to not perform a Boolean test on startup

  host1(config-mgmtevent-trigger)#boolean-test startup

• Use the no version to delete the Boolean-test values for this trigger or to remove either the startup condition or event binding.
• See boolean-test.

delta-sampling

• Use to specify delta sampling for the trigger you are configuring.
• Example

  host1(config-mgmtevent-trigger)#delta-sampling

• (Optional) Use the discontinuity-id option to specify a discontinuity MIB ID for the sample. The discontinuity MIB ID monitors the sample for any discontinuity errors during the sample frequency. If a discontinuity error occurs, the router removes the sampling for that interval.
• (Optional) Use the discontinuity-id-type option to specify a discontinuity ID type (either timeStamp or timeTicks). The discontinuity ID type indicates the time value that you expect for a specific sample.
• Use the no version to turn off delta sampling and use absolute sampling (the default).
• See delta-sampling.

enable

• Use to enable an event configuration or trigger configuration.
• Example 1—Event Configuration Mode

  host1(config-mgmtevent-event)#enable

• Example 2—Trigger Configuration Mode

  host1(config-mgmtevent-trigger)#enable

• Once enabled, you cannot edit an event or trigger configuration (even when it is disabled). To change an enabled event or trigger, you must delete it and re-create it.
• There is no no version.
• See enable.

event

• 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.

existence-test

• 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.

frequency

• 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.

notification id

• 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.

resource

• Use to specify the total number of triggers that the virtual router allows.

  Caution: When assigning wildcards, make sure to allow for enough trigger resources.

• Example

  host1(config-mgmtevent-event)#resource 250

• Use the no version to restore the default resource value (50).
• See resource.

sample

• Use to specify the MIB object that you want to sample for the trigger that you are configuring.
• Example

  host1(config-mgmtevent)#sample value-id 1.3.6.1.2.1.60.1.2.1.1.7

• Use the no version to remove the MIB object from the trigger. Removal returns the sample value-id to its default (0.0).
• See sample.

set

• Use to perform an SNMP set operation under certain event conditions.
• Example—Sets the administrative status of interface 123 to down (2)

  host1(config-mgmtevent-event)#set context-name router1

  host1(config-mgmtevent-event)#set id 1.3.6.1.2.1.2.2.1.7.123

  host1(config-mgmtevent-event)#set value 2

• Use the no version to remove the set operation.
• See set.

snmp-server management-event

• Use to launch the SNMP server event manager mode on each virtual router on which you plan to manage events.
• Example

  host1(config)#snmp-server management-event

  host1(config-mgmtevent)#

• To leave the SNMP server event manager, use the exit command.
• Use the no version to delete all the management events.
• See snmp-server management-event.

snmp-server security

• Use to specify a security access level for the SNMP agent.
• Example

  host1(config)#snmp-server security read

• Use the no version to return to the SNMP security level to its default (no-access).
• See snmp-server security.

threshold-test

• Use to define the threshold values for the trigger that you are configuring, including specifying rising and falling values, a startup threshold condition, and binding an event to the threshold-test trigger.
• Example 1—Specifying absolute values

  host1(config-mgmtevent-trigger)#threshold-test absolute-value rising 2000 falling 1900

• Example 2—Specifying a startup threshold condition

  host1(config-mgmtevent-trigger)#threshold-test startup rising

• Example 3—Binding an event to the threshold-test trigger

  host1(config-mgmtevent-trigger)#threshold-test event sysadmin failureTrigger

• Use the no version to delete the threshold-test values for this trigger or remove either the threshold startup condition or event binding.
• See threshold-test.

trigger

• Use to create a trigger and access the trigger configuration mode of the SNMP server event manager.
• Example

  host1(config-mgmtevent)#trigger fred trigger1

  host1(config-mgmtevent-trigger)#

• To leave the trigger configuration mode, use the exit command.
• Use the no version to remove the trigger.
• See trigger.

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