Use the Event Log Viewer to display a detailed list of events that occur in a . The is stored on reserved areas on the storage array's disks and records configuration events and storage array component failures.
Important: Use this option only under the guidance of a Customer and Technical Support representative.
The Event Log stores approximately 8,000 events before replacing them. If you want to keep the events, save them, and clear them from the Event Log. Refer to How to Save Selected Events to a File and How to Clear Events for procedures and more information.
Event Log Window Views
The Event Log window shows two types of event views:
When the View Details check box is selected, the window divides into two views. To resize the panes, select the splitter bar between the two views and move it up or down.
Displaying Events
Important: It can take up to several minutes for an event to be logged and become visible in the Event Log Viewer.
When you open the Event Log window, the most recent critical and informational events are displayed, starting with the most recent event. The default number of critical events displayed is 100. You can configure values for the number of events displayed, as well as values for View only critical events and View details. Your configuration settings are retained in the next session, even if the or Enterprise Management Window has been shut down.
Use the following procedure to display events:
1
From the Array Management Window, select Advanced >> Troubleshooting >> View Event Log.
2
Specify or type the number of events to retrieve in the Retrieve most recent events spinner box.
Note: When View only critical events is selected, the
box is labeled Retrieve most recent critical events.
3
To toggle between all events or critical events only,
select View only critical events.
4
To view details about a selected event, select View details.
5
Click Update to retrieve new events from the storage array for display.
Interpreting Event Summary Data
The Event Summary table has five columns, which are described in the
following table.
Column
Description
Date/Time
The date and time stamp of the event, according to the clock.
Note: The Event Log initially sorts events based on sequence number (shown in the event details). Normally, this sequence corresponds to the date/time. However, the two RAID controller module clocks in the storage array could be unsynchronized. In this case, some perceived inconsistencies could be displayed in the Event Log relative to events and the date/time shown. Select Storage Array >> Set RAID Controller Module Clocks to synchronize storage array RAID controller module clocks with the clock on your .
Priority
The Event Summary table displays two priority values:
Critical -
A problem exists with the storage array. However, immediate action by the user might prevent losing access to data. Critical events are used for alert notifications. All critical events are sent to any Network Management Station (through SNMP traps) or to the email recipient you configured
by selecting Edit >> Alert in the Enterprise Management Window. For critical event codes, see Critical Event Descriptions.
Information - Non-critical information related to the storage array.
Component Type
The component affected by the event. The component could be hardware, such as a physical disk or a RAID controller module, or it could be software, such as a or RAID controller module .
Component Location
The physical location of the component in the storage array.
Description
A description of the event.
Example:Physical Disk write failure - retries exhausted
Interpreting Event Details
Use the View details check box to show event details of a single-selected Summary event. When you have enabled the View details check box, click a single event in the Summary View to show the details about that event in the Event Details View.
Note: Because some of the fields in the Event Details View require no explanation, this table describes only those fields that require additional detail.
Column
Description
Sequence Number
A 64-bit number that uniquely identifies a specific log entry for a storage array. This number increments by one with every new event log entry.
Event Type
A four-digit number that identifies each type of logged event.
Event Specific Codes
This information is used by Customer and Technical Support.
Event Category
Category Name
Description
Failure
Some component on the storage array has failed.
Examples: Physical Disk failure, battery failure.
State Change
An element of the storage array has changed state.
Examples: A virtual disk transitioned to ; a RAID controller module transitioned to offline.
Internal
Internal RAID controller module operations that do not require user action.
Example: The RAID controller module has completed start-of-day.
Command
A command has been issued to the storage array.
Example: A hot spare has been assigned.
Host
Host software has posted the entry into the Event Log.
Error
An error condition has been detected on the storage array.
Examples: A RAID controller module is unable to synchronize and purge cache; a error is detected on the storage array.
General
Any events that do not fit well into any other category.
Logged By
The name of the RAID controller module that logged the event.
Raw Data
This information is used by Customer and Technical Support.
Saving Selected Events to a File
Use the following procedure to save selected events from the Summary area to a
file.
1
Select the events you want to save to a file in the Summary View.
Press Ctrl-mouse click to select nonadjacent events to be saved.
Press
Shift-mouse click to select adjacent events to be saved.
Press Select All to save every displayed event.
2
Click Save As.
3
Save the selected events by choosing an appropriate directory and file name.
The Save dialog can filter on files with a .log extension. Therefore, you might want to save the file with a .log extension using the file name conventions you used for any previous log files. If no extension is specified, the
Save As dialog appends a .log extension by default.
4
Type your desired file name in the File Name
field.
Example: Name the file january13.log.
5
Click Save.
An ASCII text file containing the selected events, with a .log extension, is saved to the designated directory.
Clearing Events
Important: If you want to save the current event log entries, be sure to save a copy of the log before clearing it.
Use the following procedure to clear all events from the event log.
1
Click Clear All to delete all entries in the Event
Log.
-
A problem exists with the storage array. However, immediate action by the user might prevent losing access to data. Critical events are used for alert notifications. All critical events are sent to any Network Management Station (through SNMP traps) or to the email recipient you configured
by selecting Edit >> Alert in the Enterprise Management Window. For critical event codes, see Critical Event Descriptions.
- Non-critical information related to the storage array.