Defining An Existence Test - Juniper JUNOSE SOFTWARE FOR E SERIES 11.3.X - SYSTEM BASICS CONFIGURATION GUIDE 2010-10-04 Configuration Manual
Software for e series broadband services routers system basics configuration guide
Hide thumbs
Also See for JUNOSE SOFTWARE FOR E SERIES 11.3.X - SYSTEM BASICS CONFIGURATION GUIDE 2010-10-04:
- Configuration manual (304 pages) ,
- Reference manual (284 pages)
Table of Contents
Advertisement
Copyright © 2010, Juniper Networks, Inc.
host1(config-mgmtevent-trigger)#boolean-test comparison greater
(Optional) Specify that you do not want the Boolean test to perform a comparison
2.
when this trigger first becomes active.
host1(config-mgmtevent-trigger)#boolean-test startup
Specify the events that you want the Boolean-test trigger to use by entering an event
3.
owner name and event name.
NOTE: You do not need to bind a failure event to a trigger. If you create a
failure event and a failure occurs, the router sends the trap if the event
owner is the same as the trigger owner.
host1(config-mgmtevent-trigger)#boolean-test event george trigger1
When specifying an event, use the exact owner name and event name.Specify the
Boolean value to which the test compares.
host1(config-mgmtevent-trigger)#boolean-test value 5175438
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.
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 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:
Define the existence test test-type value that you want this trigger to use.
1.
host1(config-mgmtevent-trigger)#existence-test test-type changed
Define the startup threshold condition—absent or present—that you want this trigger
2.
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 event
3.
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.
Chapter 4: Configuring SNMP
171
Advertisement
Table of Contents
Troubleshooting
