The Remote Monitoring (Rmon) Mib; Traps And Smart Traps; Device Status Polling; Telnet Polling - Extreme Networks Ridgeline Guide Manual

Concepts and solutions guide
Hide thumbs Also See for Ridgeline Guide:
Table of Contents

Advertisement

Ridgeline Overview

The Remote Monitoring (RMON) MIB

Ridgeline can use statistics gathered from the Remote Monitoring (RMON) MIB to provide utilization
statistics on a port-by-port basis, if RMON is supported and enabled on the Extreme devices Ridgeline
is managing. Utilization and error statistics can be displayed within the Real-Time Statistics application,
which provides a number of chart, graph, and tabular display formats. The Ridgeline Alarm Manager
also provides the ability to define threshold-based RMON rules for generating trap events that can be
used in Ridgeline alarm definitions.

Traps and Smart Traps

Fault detection is based on Simple Network Management Protocol (SNMP) traps, syslog messages, and
some limited polling. The Alarm System supports SNMP Management Information Base-2 (MIB-2), the
Extreme Networks private MIB, Remote Monitoring (RMON) traps, and selected traps from other MIBs.
The Ridgeline software uses a mechanism called SmartTraps to identify changes in Extreme device
configuration.
When an Extreme switch is added to the Ridgeline database, the Ridgeline software creates a set of
SmartTraps rules that define the configuration change events that the Ridgeline server needs to know
about. These rules are downloaded into the Extreme switch, and the Ridgeline server is automatically
registered as a trap receiver on the switch. Subsequently, whenever a status or configuration change
takes place, the ExtremeWare software on the switch uses the SmartTraps rules to determine if the
Ridgeline server should be notified. These changes can be changes in device status, such as fan failure
or overheating, or configuration changes made on the switch through the ExtremeWare CLI or
ExtremeWare Vista.
For non-Extreme devices, Ridgeline does not automatically register itself as a trap receiver; you must
manually configure those devices to send traps to Ridgeline. See
"Configuring Devices for Use With
Ridgeline" on page 309
for information on configuring devices to send traps to Ridgeline.

Device Status Polling

Ridgeline uses several types of polling to monitor the status of the devices it manages. Since device
polling adds a certain amount of traffic load to the network, Ridgeline tries to minimize the amount of
polling that it does, and many aspects of its polling algorithms are configurable.
Ridgeline polls for basic device status approximately every five minutes using SNMP. This poll interval
can be changed in Ridgeline Administration under the Server Properties for SNMP. Ridgeline also polls
periodically for detailed device status information. By default, this interval is 30 minutes for Extreme
modular chassis switches, and 90 minutes for Extreme stackable chassis switches. The detailed polling
interval can be set for individual devices. The detailed polling gets more complete information, still
only polls for information that has changed; a manual Update Devices action is required to retrieve all
information about the device. An Update Devices action is performed automatically whenever the
Ridgeline client application is started.

Telnet Polling

When it is not possible to use SNMP to obtain information from Extreme devices, Ridgeline uses Telnet
polling instead. Ridgeline uses Telnet polling to obtain MAC address information for edge ports from a
device Forwarding Database (FDB) and to obtain netlogin information. Telnet polling is also used to
obtain power supply IDs for Alpine devices.
Ridgeline Concepts and Solutions Guide
22

Advertisement

Table of Contents
loading

This manual is also suitable for:

Ridgeline 3.0

Table of Contents