Configuring
RMON
Event Actions
Effective use of the Events group saves you time. Rather than having
to watch real-time graphs for important occurrences, you can
depend on the Event group for notification. Through the SNMP
traps, events can trigger other actions, providing a mechanism for an
automated response to certain occurrences.
RMON requires one probe per LAN segment, and standalone RMON
probes have traditionally been expensive. Therefore, Allied Telesyn's
approach has been to build an inexpensive RMON probe into the
agent of each system. This allows RMON to be widely deployed
around the network without costing more than traditional network
management. The switch accurately maintains RMON statistics at the
maximum line rate of all of its ports.
For example, statistics can be related to individual ports. Also,
because a probe must be able to see all traffic, a stand-alone probe
must be attached to a nonsecure port. Implementing RMON in the
switch means that all ports can have security features enabled.
To enable or disable the collection of RMON statistics on the switch,
use the following command:
[enable | disable] rmon
By default, RMON is disabled. However, even in the disabled state,
the switch response to RMON queries and sets for alarms and events.
By enabling RMON, the switch begins the processes necessary for
collecting switch statistics.
The actions that you can define for each alarm are shown in
Table
13-6.
Action
No action
Notify only
Notify and log
To be notified of events using SNMP traps, you must configure one
or more trap receivers, as described in
AT-9108, AT-8518, AT-8525, and AT-8550 User's Guide
Table 13-6 Event Actions
High Threshold
Send trap to all trap receivers.
Send trap; place entry in RMON log.
Chapter
2.
13-13