Using Device Groups And Port Groups For Alarm Scopes; The Alarm And Event Log Archives; Using The Mib Poller Tools - Extreme Networks Ridgeline Guide Manual

Using Device Groups and Port Groups for Alarm Scopes

Special-purpose Device Groups and Port Groups are very useful for purposes of alarm scoping. Since
Ridgeline allows you to put the same devices or ports into multiple top-level groups, you can create
special purpose groups that simplify the configuration of alarm scopes.
For example, you might create a port group for the critical links on your core devices, another for edge
port links or for wireless interfaces.
A major benefit of using Device and Port Groups for alarm scoping, rather than configuring the scope
with individual devices and ports, is that you can then change the scope of an alarm by simply
changing the membership of the relevant groups. You can add or remove ports from a Port Group, or
add or remove devices from a Device Group, and the scope of the alarm will automatically reflect the
changed group membership. You do not need to modify the alarm definition every time you add or
change devices or ports on your network.

The Alarm and Event Log Archives

The Ridgeline server stores a maximum of 50,000 events in the event log, and a maximum of 12,000
alarms in the alarm log. Both are stored as tables in the server database. Excess data from the event log
and alarm log are archived to files when the logs reach 115% of their maximum size.
The event log archive is made up of two 30MB rotating archive files and includes all traps and Syslog
messages. The event log is stored in a file called
.
event_log.old
The alarm log archive is made up of two 6 MB rotating files and includes all alarms associated with
traps and Syslog messages. The alarm log is stored in a file called
called .
alarm_log.old
An archiving check is performed once an hour. If you need to store additional historical data beyond
the two 30 MB file limit for events and the 6 MB file limit for alarms, you can periodically make backup
copies of the archive files to a separate location. Refer to "Ridgeline Backup" in the Ridgeline Reference
Guide for more information about alarm log backups.

Using the MIB Poller Tools

The MIB Poller Tools, found in the Reports module, can be used to collect and inspect data from any
MIB variables supported by the devices on your network. These tools allow you to retrieve data that is
not available through Ridgeline's reports or other status displays, and to accumulate historical data for
MIB variables of interest. The collected data can then be exported as a comma-separated text file which
can be imported into another application such as a spreadsheet for analysis.
You must have an Administrator role to set up and initiate MIB collection or query actions, However,
users with other roles can view the results of a collection that has been initiated by an Administrator.
There are two separate tool available for retrieving MIB variable data:
The MIB Poller Summary displays a MIB collection, or allows an Administrator to load a MIB
●
collection XML file to initiate MIB collection activity. A MIB collection is a historical log of MIB
values as defined in the
devices, retrieves the values of specified MIB variables and saves them in the Ridgeline database.
Ridgeline Concepts and Solutions Guide
event_log.txt
file. In a running collection, Ridgeline polls specified
collections.xml
and the archive file is called
and the archive file is
alarm_log.txt
15
221