beautypg.com

Remote monitoring, Configuring rmon alarms, Figure 274 s – Brocade 6910 Ethernet Access Switch Configuration Guide (Supporting R2.2.0.0) User Manual

Page 1029: Remote monitoring (rmon)

background image

Brocade 6910 Ethernet Access Switch Configuration Guide

973

53-1002651-02

43

Remote Monitoring

FIGURE 274

Showing SNMP Statistics

Remote Monitoring

Remote Monitoring allows a remote device to collect information or respond to specified events on
an independent basis. This switch is an RMON-capable device which can independently perform a
wide range of tasks, significantly reducing network management traffic. It can continuously run
diagnostics and log information on network performance. If an event is triggered, it can
automatically notify the network administrator of a failure and provide historical information about
the event. If it cannot connect to the management agent, it will continue to perform any specified
tasks and pass data back to the management station the next time it is contacted.

The switch supports mini-RMON, which consists of the Statistics, History, Event and Alarm groups.
When RMON is enabled, the system gradually builds up information about its physical interfaces,
storing this information in the relevant RMON database group. A management agent then
periodically communicates with the switch using the SNMP protocol. However, if the switch
encounters a critical event, it can automatically send a trap message to the management agent
which can then respond to the event if so configured.

Configuring RMON Alarms

Use the Administration > RMON (Configure Global - Add - Alarm) page to define specific criteria that
will generate response events. Alarms can be set to test data over any specified time interval, and
can monitor absolute or changing values (such as a statistical counter reaching a specific value, or
a statistic changing by a certain amount over the set interval). Alarms can be set to respond to
rising or falling thresholds. (However, note that after an alarm is triggered it will not be triggered
again until the statistical value crosses the opposite bounding threshold and then back across the
trigger threshold.

CLI References

“Remote Monitoring Commands”

on page 125