An Event Responder enables you to specify a response (if any) that you want OmniVista Cirrus to take when specified events are received by OmniVista Cirrus. You can specify the events to which OmniVista Cirrus will respond by severity level or with a custom filter. OmniVista Cirrus can make the following responses to receipt of a specified event:

  • OmniVista can send an e-mail to any address you specify. The e-mail can include the information you want in the email through the use of variables. Variables exist for information such as the event name, synopsis, description, etc..

  • Automatically acknowledge the traps.

To access the Event Responder screen, click on Diagnostic Tools > Network Events > Event Responder under the “Monitor” section of the OmniVista Cirrus Menu.

The Event Responder screen displays all configured event responders, and is used to create, edit, or delete Event Responders.

Creating an Event Responder

To configure an Event Responder, click Create Event Responder on the Event Responder screen. An Event Responder Wizard opens to walk you through the following configuration steps:

  1. Basic Information - Enter a name, an optional description, and enable/disable the Responder.

  2. Device Selection - Select the AP devices for the Responder configuration. The Responder will respond only if events are received from these devices.

  3. Event Type - Specify the events to which OmniVista Cirrus will respond by severity level or by selected custom filters.

  4. Response - Select one or both of the following actions that the Responder will take when an event matching the Responder criteria is received:

    1. Send an e-mail response to a specified recipient.

    2. Automatically acknowledge the events.

1. Basic Information

Complete the fields as described below, then click Next to move to Step 2:

  • Name - The name to assign to the Responder.

  • Description - An optional description.

  • Event Responder - Enable (the default) or disable the Responder action. If Responder is disabled, no response action is taken.

2. Device Selection

Select the devices or Access Point Groups to which a response is sent. The Responder will only send a response to device events sent from the selected devices. To pick devices from a list of devices, click on “Launch device selection dialog”. A Device Selection window opens from which you can select the devices for upgrade. Once devices are selected, click on Next to move to the Step 3.

3. Event Type

Specify the type of events to respond to by selecting one of the following two filter options:

  • Severity - Respond only to events that match the selected severity levels.

  • Custom - Define a custom filter to specify the event criteria that will trigger a response.

Creating a Custom Filter

When you select Custom for the Type of Filter, the Event Type screen prompts you to select the scope of the filter and provides an Add Filter button to define a custom filter.

Select the filter scope by clicking on Any or All:

  • Any - Respond to any event received from the specified devices that matches any of the custom filters.

  • All - Respond to any event received from the specified devices that matches all of the custom filters.

Click on Add Filter to open the Add Filter form, which consists of a Basic Information section and a Filter Condition(s) section.

In the Basic Information section, enter a name for the custom filter and an optional description. You can also change the status of the filter (enabled by default) by clicking on the Enable Filter slider.

In the Filter Condition(S) section, complete the following tasks:

  • Select the Scope (Any or All) then click on Add Condition.

  • Define the condition using the fields provided. If you want to define another condition, click on Add Condition again.

When you are done defining all the filter conditions that you want, click Create. The Add Filter form closes and your custom filters are displayed on the Event Type tab. Click Next to move to Step 4.

4. Response

Response Action - Select one or both of the following options to configure the response to events matching the specified criteria:

  • E-mail - The Event Responder will automatically send an e-mail. The configurable Responder Settings determine when the email response is sent. When this option is selected, you are prompted to complete the following e-mail parameters:

    • E-mail Recipients - Enter an e-mail address(es). Multiple e-mail addresses must be separated by a semi-colon (e.g., john.smith@al-enterprise.com; jane.sullivan@al-enterprise.com).

    • E-mail Subject - By default, the following is included in the E-Mail Subject Line: "OmniVista: Trap(s) Received $TrapSeverityCount$" (explained in the Event Variables section). You can also enter any additional information you want to include in the subject line.

    • E-mail Body - By default the variable $Details$ (explained in the Event Variables section) is included in the body of the e-mail. The variable automatically includes event details in the body of the e-mail. You can also enter any additional information you want to include in the e-mail.

  • Auto-Ack - The Event Responder will automatically acknowledge the events.

When you are finished, click Save to return to the Event Responder screen. The Event Responder you just created will appear in the Event Responder List.

Responder Settings

If you want to adjust when an email response is sent, click on Settings on the Event Responder screen to open the Responder Settings screen.

By default, the maximum event limit is set to 15 events and the maximum time limit is set to 10 minutes. This means that 10 minutes after the first event is sent, OmniVista Cirrus will send an email response if no other response was sent during that time or 15 events were received before the 10 minutes is up.

Change the Maximum Event Limit and/or the Maximum Time Limit, if necessary, then click Save to retain the changes. Note that the event and time limit values are maintained at the Organization level.

Event Variables

You can use the following variables when you configure an automatic trap responder. There are two types of variables: generic variables (which currently apply only to traps) and trap-specific variables.

Generic Variables

$Details$
For traps, this variable is equivalent to the following combination of text and trap-specific variables (trap-specific variables are described in the following section):

Trap Received: $TrapName$
Severity: $TrapSeverity$
Synopsis: $TrapSynopsis$
Agent: $TrapAgent$
Variables: $TrapVariables$

Output Example:
Trap Received: portPartitioned
Severity: Minor
Synopsis: Port jabber on slot 7 frtrunking port 1 instance 156 (port state alternated between enabled and disabled more than 50 times in 200 ms)
Agent: 128.251.30.27

$Synopsis$
For traps, this variable is equivalent to the trap-specific variable $TrapSynopsis$, which is a brief description of the trap.

Output Example: Port jabber on slot 7 frtrunking port 1 instance 156 (port state alternated between enabled and disabled more than 50 times in 200 ms)

Trap Specific Variables

$TrapName$
The name of the trap (as defined in the MIB)

Output Example: portPartitioned

$TrapSynopsis$
A brief description of the trap.

Output Example: Port jabber on slot 7 frtrunking port 1 instance 156 (port state alternated between enabled and disabled more than 50 times in 200 ms)

$TrapDescription$
A detailed description of the trap (as it appears in the MIB)

Output Example: A portPartitioned trap occurs when the physical port has transitioned through enable/disable states faster than 10 times in the past second...indicative of a flaky cable.

$TrapSeverity$
The severity level assigned to the trap in the Notifications application's Trap Definitions pane. The severity level can be Normal, Warning, Minor, Major, or Critical.

Output Example: Minor

$TrapSeverityCount$
A summary of the trap severity counts.

Output Example: (2 Critical)

$TrapSeverityInt$
The severity level assigned to the trap in the Notifications application's Trap Definitions pane, expressed as an integer. The severity level integer can be 1 (Normal), 2 (Warning), 3 (Minor), 4 (Major), or 5 (Critical).

Output Example: 3

$TrapSnmpVersion$
The version of the trap request, either 1 (version 1) or 2 (version 2).

All traps sent with SNMP version 1 protocol are "version 1" trap requests. All traps sent with SNMP versions 2, 2c, or 3 protocol are "version 2" trap requests. There are actually two different types of trap requests (not three). The message packet in which trap requests are sent can be one of four different versions: 1, 2, 2c, or 3. When you use the AOS CLI to create a version 1 trap station, version 1 traps in version 1 protocol are sent to that station. When you use the AOS CLI to create a version 2 trap station, version 2 traps in version 2c protocol are sent to that station. When you use the AOS CLI to create a version 3 trap station, version 2 traps in version 3 protocol are sent to that station. The version 2 trap request itself is identical whether wrapped in a version 2 or version 3 packet.

Output Example: 1

$TrapSource$
The IP address of the switch that generated the trap.

Output Example: 127.0.0.1

$TrapUpTime$
The length of time the switch that sent the trap has been up (or the amount of time since the last reset).

Output Example: 21 hours, 35 minutes, 49 seconds

$TrapAgent$
The IP address of the SNMP agent.

Output Example: 128.251.30.27

$TrapAgentName$
The name of the switch that generated the trap.

Output Example: NMS-6450

$TrapV1Enterprise$
The enterprise name. This only applies to SNMP Version 1 traps.

Output Example: .1.3.6.1.4.1.800.3.1.1

$TrapV1GenericID$
The generic trap number. This only applies to SNMP Version 1 traps.

Output Example: 6

$TrapV1SpecificID$
The enterprise trap number. This only applies to SNMP Version 1 traps.

Output Example: 10

$TrapVariables$
Describes all of the variables in the trap.

$TrapVariable[1]$, $TrapVariable[2]$...
Accesses the first (second, etc.) variable in the trap.

$TrapVariable[someVariableName]$
Accesses the trap variable by its name.