44 Enterprise Fabric Suite 2007 User Guide • September 2008
Note – Events (Alarms, Critical, Warning, and Informative) generated by the
application are not saved on the switch. They are permanently discarded when you
close a Enterprise Fabric Suite 2007 session, but you can save these events to a file on
the workstation before you close Enterprise Fabric Suite 2007 and read it later with a
text editor or browser.
Note – Events generated by the switch are stored on the switch, and will be
retrieved when the application is restarted. Some alarms are configurable. Refer to
“Configuring Port Threshold Alarms” on page116.
Filtering the Event Browser
Filtering the Event Browser allows you to display only those events that are of
interest based on the event severity, timestamp, source, type, and description. To
filter the Event Browser, open the Filter menu and select Filter Entries. This opens
the Filter Events dialog (FIGURE2-6). The Event Browser displays those events that
meet all of the criteria in the Filter Events dialog. If the filtering criteria is cleared or
changed, then all the events that were previously hidden that satisfy the new criteria
will be shown.
TABLE2-3 Severity Levels
Severity Icon Description
Alarm — a "serviceable event". This means that attention by the user or
field service is required. Alarms are posted asynchronously to the screen
and cannot be turned off. If the alarm denotes that a system error has
occurred the customer and/or field representative will generally be directed
to provide a "show support" capture of the switch.
Critical event — an event that indicates a potential failure. Critical log
messages are events that warrant notice by the user. By default, these log
messages will be posted to the screen. Critical log messages do not have
alarm status as they require no immediate attention from a user or service
representative.
Warning event — an event that indicates errors or other conditions that may
require attention to maintain maximum performance. Warning messages
will not be posted to the screen unless the log is configured to do so.
Warning messages are not disruptive and, therefore, do not meet the criteria
of Critical. The user need not be informed asynchronously
No icon Informative — an unclassified event that provides supporting information.