Extreme Networks ExtremeWare XOS 11.3, Manual

Page: 215 / 698

RMON
ExtremeWare XOS 11.3 Concepts Guide
215
The group is useful for analysis of traffic patterns and trends on an Ethernet port, and to establish
baseline information indicating normal operating parameters.
Alarms
The Alarms group provides a versatile, general mechanism for setting threshold and sampling intervals
to generate events on any RMON variable. Both rising and falling thresholds are supported, and
thresholds can be on the absolute value of a variable or its delta value.
Please note, creating an entry in the alarmTable does not validate the alarmVariable and does not
generate a badValue error message.
Alarms inform you of a network performance problem and can trigger automated action responses
through the Events group.
Events
The Events group creates entries in an event log and/or sends SNMP traps to the management
workstation. An event is triggered by an RMON alarm. The action taken can be configured to ignore it,
to log the event, to send an SNMP trap to the receivers listed in the trap receiver table, or to both log
and send a trap. The RMON traps are defined in RFC 1757 for rising and falling thresholds.
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, which provides a mechanism for an automated response to certain
occurrences.
RMON Probe Configuration Parameters
The RMON probe configuration parameters supported in ExtremeWare XOS are a subset of the probe
configuration group as defined in RFC 2021. The probe configuration group controls and defines the
operation of the RMON agent. You can configure the following objects:
●
probeCapabilities—If you configure the probeCapabilities object, you can view the RMON MIB
groups supported on at least one interface by the probe.
●
probeSoftwareRev—If you configure the probeSoftwareRev object, you can view the current software
version of the monitored device.
●
probeHardwareRev—If you configure the probeHardwareRev object, you can view the current
hardware version of the monitored device.
●
probeDateTime—If you configure the probeDateTime object, you can view the current date and time
of the probe. For example, Friday December 31, 2004 at 1:30:15 PM EST is displayed as: 2004-12-
31,13:30:15.0
If the probe is aware of time zones, the display also includes the Greenwich Mean Time (GMT)
offset. For example, Friday, December 31, 2004, 1:30:15 PM EST with the offset known is displayed
as: 2004-12-31,13:30:15.0, -4.0
If time information is unavailable or unknown, the time is not displayed.
●
probeResetControl—If you configure the probeResetControl object, you can restart a managed device
that is not running normally. Depending on your configuration, you can do one of the following:
■
Warm boot—A warm boot restarts the device using the current configuration saved in non-
volatile memory.