The Alarm And Event Log Archives; Using The Mib Poller Tools - Extreme Networks EPICenter Guide Manual

changing the membership of the relevant groups. You can add or remove links 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 EPICenter 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 Appendix C, "EPICenter Backup" in the
EPICenter 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 EPICenter'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 collections
devices, retrieves the values of specified MIB variables and saves them in the EPICenter database.
The OIDs and devices to be polled, the poll interval, number of polling cycles and the amount of
polled data to be stored is all defined in the Administrator-created
• The MIB Query tool allows an Administrator to create a one-time MIB query request to retrieve the
value of specific variables from a set of specified devices. This is a one-shot query, and does not poll
repeatedly or store the data it retrieves.
The MIB Query tool is accessible only to users who have an Administrator role.
EPICenter Concepts and Solutions Guide
.
.
.xml
and the archive file is called
event_log.txt
alarm_log.txt
file. In a running collection, EPICenter polls specified
Using the MIB Poller Tools
and the archive file is
file.
collections.xml
123