Working with events
RMON events and alarms work together to notify you when values in your network go out of a specified range. When a value passes the specified range, the alarm is triggered and "fires." The event specifies how the activity is recorded.
An event specifies whether a trap, a log, or a trap and a log are generated to view alarm activity. When RMON is globally enabled, two default events are generated:
The default events specify that when an alarm goes out of range, both a trap and a log track the "firing" of the alarm. For example, when an alarm fires at the rising threshold, the rising event specifies that this information be sent to both a trap and a log. Likewise, when an alarm passes the falling threshold, the falling event specifies that this information be sent to a trap and a log.
To create an event with default rising and falling settings:
- From the Device Manager menu bar, choose Rmon > Alarms.
| The Rmon Alarms dialog box opens with the Alarm tab displayed. |
- Click the Event tab.
- In the Event tab, click Insert.
| If RMON is not globally enabled, a dialog box displays the following message: |
| RMON is currently disabled. Do you want to enable it now? |
- Click Yes.
When you create events in this manner, you create two default events (a rising event and a falling event).
To create events with nondefault parameter values:
- From the Device Manager menu bar, choose Rmon > Alarms
| The Rmon Alarms dialog box opens with the Alarm tab displayed. |
- Click the Event tab.
- Click Insert to display the RmonAlarms.
| The RmonAlarms, Insert Event dialog box opens. |
- In the Description text box, type a name for the event.
- From Type options, select the type of event you want.
| The default setting is log-and-trap. You may opt to set the event type to log to save memory or to snmp-trap to reduce traffic from the switch. If you select snmp-trap or log, you must set trap receivers. |
- Click Insert.
See Also:
