[Contents] [Prev] [Next] [Index] [Report an Error]

# Configuring the SNMP Server Event Manager

The SNMP server event manager works in conjunction with the Event MIB (RFC 2981). The purpose of this application is to allow many management functions (for example, fault detection, configuration management, accounting management, and performance management). These functions are traditionally performed by the network management station. However, by using the SNMP server event manager, you can distribute some of these functions to E Series routers and automate them.

## Event MIB Purpose

The rapid growth of networks has made it impractical to directly manage networks from a single network management station (NMS). This brought about a need for a model that both automated and distributed event management. The goal was to allow devices to monitor themselves and other devices, and to take action under certain conditions.

The Event MIB (RFC 2981) defines a method for creating trigger conditions, testing those conditions, and determining which action to take when a trigger meets those conditions.

The Event MIB allows you to define test conditions for object integers that are accessible in the agent, making it possible to monitor any aspect of a device without defining specific notifications and complicating the agent definition. In this model, because devices have the ability to monitor themselves or other devices, the processing is distributed throughout the network. Also, sending the information only to the NMS that uses an event model reduces both network overhead and processing drain on the NMS.

## Event MIB Structure

The Event MIB has three major parts: the trigger table, the objects table, and the event table. These tables also contain subordinate MIB tables that contain more detailed information about the trigger tests.

### Trigger Table

The trigger table (mteTriggerTable) lists any currently-defined trigger conditions. Triggers fall into three categories—existence, Boolean, and threshold.

An existence trigger tests for the existence of a MIB object instance; you can specify that the trigger occur by either the appearance, disappearance, or change in value of a MIB instance.

A Boolean trigger tests whether the value of a MIB object (base syntax integer) is equal, unequal, greater than, less than, less than or equal to, or greater than or equal to some defined value.

A threshold trigger verifies a MIB object (base syntax integer) in relation to either a rising threshold value, falling threshold value, or both.

You can configure both Boolean and threshold tests to trigger on an absolute value or a delta value over a determined polling interval.

Subordinate MIB tables exist within the trigger section of each type of trigger test. In other words, each type of trigger (existence, threshold, and Boolean) contains a table that stores added information about that type of trigger test.

For example, a trigger entry of a specific type of test in the mteTriggerTable creates a linked entry in the appropriate subtable. In turn, this subtable contains more specific information about the specific test.

A delta table also exists within the trigger tables. This table stores information about any delta values based on any Boolean and threshold triggers. The delta table stores a MIB object that indicates whether any discontinuities occurred for any delta trigger (for example, a router reset).

| Note: When determining discontinuity, the MIB object must be a time-based counter or number. When a polling interval expires and the event agent (router) needs to perform a delta calculation, it first checks the discontinuity MIB object for that trigger. If a discontinuity occurs, the agent does not perform the test for that trigger until the next polling interval.

### Objects Table

The objects table (mteObjectsTable) defines objects that you want to add to event messages. In other words, you can create a list of user-specified objects and bind them to a trigger event. This can provide a snapshot of other values on a router when the trigger occurs. You can bind objects to a specific trigger, a type of test (for example, existence or Boolean tests), or a type of event (for example, rising or falling events).

| Note: This release does not support the objects table.

### Event Table

The event table (mteEventTable) defines what action you want the device to take when a trigger occurs. This action can be in the form of a notification, setting a specified MIB object, or both. The results of these actions are controlled within two subordinate MIB tables—notification and set.

Notifications (mteNotifications), or traps, define what the router sends when an event occurs. These traps include the following:

- When a Boolean or existence trigger occurs, the router sends an mteTriggerFired trap.
- When a rising threshold trigger occurs, the router sends an mteTriggerRising trap.
- When a falling threshold trigger occurs, the router sends an mteTriggerFalling trap.
- If a trigger fails to complete a test for any reason, the router sends a global mteTriggerFailure trap.
- If an event fails to set, the router sends an mteEventSetFailure trap.

Sets define certain modifications to other MIB objects based on a particular event.

## Configuration Tasks

To configure the SNMP server event manager:

1. Access the SNMP server management event application.
   `
   host1(config)#snmp-server management-event
   host1(config-mgmtevent)#
   `

   | Note: You must create a management event instance for each virtual router.

2. (Optional) Specify the maximum number of trigger entries that you want the virtual router to support.
   `
   host1(config-mgmtevent)#resource 275
   `
3. Create an event for each trap notification (mteTriggerFailure, mteTriggerFalling, or mteTriggerRising) that you want to use by specifying an event owner and event name.
   `
   host1(config-mgmtevent)#event sysadmin failuretrigger
   host1(config-mgmtevent-event)#exit
   host1(config-mgmtevent)#event sysadmin fallingtrigger
   host1(config-mgmtevent-event)#exit
   host1(config-mgmtevent)#event sysadmin risingtrigger
   host1(config-mgmtevent-event)#exit
   `

   | Note: You must create a separate event for each trap notification that you want to use. However, you can specify the trap notification and enable the trap before exiting the event context.

4. Define each event to send a trap notification (mteTriggerFailure, mteTriggerFalling, and mteTriggerRising).
   `
   host1(config-mgmtevent)#event sysadmin failuretrigger
   host1(config-mgmtevent-event)#notification id mteTriggerFailure
   host1(config-mgmtevent-event)#exit
   host1(config-mgmtevent)#event sysadmin fallingtrigger
   host1(config-mgmtevent-event)#notification id mteTriggerFalling
   host1(config-mgmtevent-event)#exit
   host1(config-mgmtevent)#event sysadmin risingtrigger
   host1(config-mgmtevent-event)#notification id mteTriggerRising
   host1(config-mgmtevent-event)#exit
   `

   | Note: The mteTriggerFailure notification is a global value. After you create a failure event notification, it is automatically bound to every trigger with the same owner. If a failure occurs, and the trigger owner and the event owner are the same, the router sends the trap.

5. Enable the event, and exit the event configuration level.
   `
   host1(config-mgmtevent)#event sysadmin failuretrigger
   host1(config-mgmtevent-event)#enable
   host1(config-mgmtevent-event)#exit
   host1(config-mgmtevent)#event sysadmin fallingtrigger
   host1(config-mgmtevent-event)#enable
   host1(config-mgmtevent-event)#exit
   host1(config-mgmtevent)#event sysadmin risingtrigger
   host1(config-mgmtevent-event)#enable
   host1(config-mgmtevent-event)#exit
   host1(config-mgmtevent)#
   `

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

6. Define the trigger that you want to use for an event by specifying a trigger owner and trigger name.
   `
   host1(config-mgmtevent)#trigger george trigger1
   host1(config-mgmtevent-trigger)#
   `
7. Specify a MIB object to sample.
   `
   host1(config-mgmtevent-trigger)#sample value-id 1.3.6.1.2.1.60.1.2.1.1.7
   `
8. Specify the frequency (in seconds) at which you want the sampling to occur.
   `
   host1(config-mgmtevent-trigger)#frequency 100
   `

   | Note: Unless you specify that you want to perform delta sampling, the values are absolute.

9. (Optional) Specify that you want to perform delta sampling on the sample value ID.
   `
   host1(config-mgmtevent-trigger)#delta-sampling
   `
   - (Optional) Enter the discontinuity MIB value ID that you want to test.
     `
     host1(config-mgmtevent-trigger)#delta-sampling discontinuity-id 1.3.6.1.2.1.31.1.1.1.19.9
     `
   - (Optional) Enter the discontinuity type (timeStamp or timeTicks) that you want the test to use.
     `
     host1(config-mgmtevent-trigger)#delta-sampling discontinuity-id-type timeStamp
     `
10. (Optional) Configure the desired SNMP security level for the agent that you want to poll.
    `
    host1(config)#snmp security read
    `
11. Define the test values that you want this trigger to use.

    You can define a Boolean test, existence test, or threshold test. See the following sections for procedures.

### Defining a Boolean Test

You can configure a Boolean trigger to test whether the value of an integer object is equal, unequal, greater than, less than, less than or equal to, or greater than or equal to some defined value.

To define a Boolean test:

1. Define the Boolean-test comparison that you want this trigger to use.
   `
   host1(config-mgmtevent-trigger)#boolean-test comparison greater
   `
2. (Optional) Specify that you do not want the Boolean test to perform a comparison when this trigger first becomes active.
   `
   host1(config-mgmtevent-trigger)#boolean-test startup
   `
3. Specify the events that you want the Boolean-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 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
   `
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.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:

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.

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

## Monitoring Events

To view the status of the SNMP agent, use the following show snmp agent command. To view statistics associated with events, resources, and triggers, use the show snmp management-event command.

show snmp agent

- Use to view SNMP MIB agent information.
- Field descriptions
  - context name—Router that contains the MIB agent
  - access permission level—Access permission level for other virtual routers that may want to access the agent
  - snmp proxy—Proxy gateway through which other virtual routers may access the agent
- Example

      host1#show snmp agent
      context name: router1
      access permission level: no access
      snmp proxy: enabled

- See show snmp agent.

show snmp management-event

- Use to view statistical SNMP event information for event table entries, router resources, and trigger table entries.
- Omit the events, resource, statistics, or triggers options to obtain a full output.
- Field descriptions
  - Resource
    - SampleMinimum—Minimum number of samples to be taken
    - SampleInstanceMaximum—Maximum number of samples to be taken
    - SampleInstances—Number of sample instances being monitored
    - SampleInstancesHigh—Highest number of samples taken for any of the sample instances
    - SampleInstancesLacks—Number of times this system could not take a new sample because that allocation would have exceeded the limit set by mteResourceSampleInstanceMaximum
  - Triggers
    - Owner—Owner value assigned to the trigger
    - Name—Name value assigned to the trigger
    - Test—Type of trigger test to perform
    - SampleType—Type of sampling (absolute or delta) to perform
    - ValueID—Object ID of the MIB sample for this trigger
    - ValueIDLimit—Not supported in this release; reads as zero
    - ValueIDWildcard—Not supported in this release; reads as False
    - ContextName—Management context (for example, router1) from which to obtain mteTriggerValueID
    - ContextNameRgulrExprssn—Not supported in this release
    - ContextNameLimit—Not supported in this release; reads as zero
    - ContextNameWildcard—Not supported in this release; reads as False
    - Frequency—Frequency at which this trigger is sampled
    - ObjectsOwner—Not supported in this release
    - Objects—Not supported in this release
    - Enabled—State (False [disabled] or True [enabled]) of the trigger
    - EntryStatus—Active/inactive status of the instance
  - Boolean
    - Comparison—Comparison value for this trigger
    - Value—Object ID value to which this trigger compares
    - Startup—Whether or not this trigger performs a Boolean test on startup
    - ObjectsOwner—Owner of this object
    - Objects—Name of this object
    - EventOwner—Owner of this event
    - Event—Name of this event
  - Existence
    - Test—Test type for this trigger
    - Startup—Startup condition for this trigger
    - ObjectsOwner—Owner of this object
    - Objects—Name of this object
    - EventOwner—Owner of this event
    - Event—Name of this event
  - Statistics
    - trigger owner—Owner value assigned to the trigger
    - trigger name—Name value assigned to the trigger
    - current time—Current UTC time
    - started sampling—UTC time sampling started
    - last sampled—UTC time event last sampled
    - sample instances—Number of sample instances being monitored
    - times sampled—Number of times events sampled
    - event traps—Number of traps sent
    - event sets—Number of events set
    - failures—Number of event failures
    - sample overrun—Number of times the event manager missed sampling for the current value within the given time period
    - failure traps—Number of failure traps sent as a result of event failures
  - Threshold
    - Startup—Startup threshold condition for this trigger
    - Rising—Rising threshold condition for this trigger
    - Falling—Falling threshold condition for this trigger
    - DeltaRising—Delta rising threshold condition for this trigger
    - DeltaFalling—Delta falling threshold condition for this trigger
    - ObjectsOwner—Not supported in this release
    - Objects—Not supported in this release
    - RisingEventOwner—Rising event owner value for this trigger
    - RisingEvent—Rising event name value for this trigger
    - FallingEventOwner—Falling event owner value for this trigger
    - FallingEvent—Falling event name value for this trigger
    - DeltaRisingEventOwner—Delta rising event owner value for this trigger
    - DeltaRisingEvent—Delta rising event name value for this trigger
    - DeltaFallingEventOwner—Delta falling event owner value for this trigger
  - DeltaFallingEvent—Delta falling event name value for this trigger
    - Delta
    - DiscontinuityID—Discontinuity MIB ID for this trigger
    - DiscontinuityIDWildcard—Not supported in this release
    - DiscontinuityIDType—Discontinuity ID type for this trigger
  - Events
    - Owner—Owner value for this event
    - Name—Name of this event
    - Actions—Action (for example, notification) that takes place when this event is triggered
    - Enabled—Enabled state (True [enabled] or False [disabled]) of this event
    - EntryStatus—Entry status for this event
  - Notification
    - Notification—Notification trap setting for this event
    - ObjectsOwner—Not supported in this release
    - Objects—Not supported in this release
  - Set
    - Object—Object ID that the trigger is setting
    - ObjectWildcard—Whether or not the object is a wildcard
    - Value—Value to which you are setting the object ID when the trigger fires
    - ContextName—Management context (for example, router1) from which to obtain mteTriggerValueID
    - ContextNameWildcard—Whether or not the context name is a wildcard
  - Example

        host1#show snmp management-event
                                         Resource
        ---------------------------------------------------------------------------
        SampleMinimum: 1
        SampleInstanceMaximum: 50
        SampleInstances: 14
        SampleInstancesHigh: 14
        SampleInstancesLacks: 0

                                          Triggers
        ---------------------------------------------------------------------------
        Owner: unitTest
        Name: booleantest1
        Test: boolean
        SampleType: absoluteValue
        ValueID: 1.3.6.1.2.1.92.1.1.2.0
        ValueIDLimit: 0
        ValueIDWildcard: False
        ContextName: router1
        ContextNameLimit: 0
        ContextNameWildcard: False
        Frequency: 40
        ObjectsOwner: unitTest
        Objects: test3
        Enabled: False
        EntryStatus: createAndWait
        ------------------------ Boolean
        Comparison: equal
        Value: 300
        Startup: False
        ObjectsOwner:
        Objects:
        EventOwner: unitTest
        Event: eventTest1
        --------------------------------- Trigger
        Owner: unitTest
        Name: booleantest2
        Test: boolean
        SampleType: absoluteValue
        ValueID: 1.3.6.1.2.1.92.1.1.2.0
        ValueIDLimit: 0
        ValueIDWildcard: False
        ContextName: router1
        ContextNameLimit: 0
        ContextNameWildcard: False
        Frequency: 40
        ObjectsOwner: unitTest
        Objects: test3
        Enabled: False
        EntryStatus: createAndWait
        ------------------------ Existence
        Test: absent
        Startup: absent
        ObjectsOwner: unitTest
        Objects: test3
        EventOwner: unitTest
        Event: eventTest3
        ------------------------ Threshold
        Startup: falling
        Rising: 200
        Falling: 100
        DeltaRising: 0
        DeltaFalling: 0
        ObjectsOwner:
        Objects:
        RisingEventOwner: unitTest
        RisingEvent: eventTest2
        FallingEventOwner: unitTest
        FallingEvent: eventTest3
        DeltaRisingEventOwner:
        DeltaRisingEvent:
        DeltaFallingEventOwner:
        DeltaFallingEvent:
        ------------------------ Delta
        DiscontinuityID: 1.3.6.1.2.1.92.1.1.2
        DiscontinuityIDWildcard: True
        DiscontinuityIDType: timeTicks

                                            Objects
        ---------------------------------------------------------------------------
        Owner: unitTest Name: test1
        Index: 1
        ID: 1.3.6.1.2.1.11.1.0
        IDWildcard: False
        EntryStatus: active
        Index: 2
        ID: 1.3.6.1.2.1.11.2.0
        IDWildcard: False
        EntryStatus: active
        Index: 5
        ID: 1.3.6.1.2.1.11.30.0
        IDWildcard: False
        EntryStatus: active

                                            Events
        ---------------------------------------------------------------------------
        Owner: unitTest
        Name: eventTest1
        Actions: notification set
        Enabled: True
        EntryStatus: active
        ------------------------ Notification
        Notification: mteTriggerFired
        ObjectsOwner: unitTest
        Objects: test3
        ------------------------ Set
        Object: 1.3.6.1.2.1.11.1.0
        ObjectWildcard: False
        Value: -20
        ContextName: router
        ContextNameWildcard: True

- See show snmp management-event.

[Contents] [Prev] [Next] [Index] [Report an Error]