Use the Event Log Viewer to display a detailed list of events that occur in a storage subsystem. The event log is stored on reserved areas on the storage subsystem's disks and records configuration events and storage subsystem component failures.
Important: It can take up to several minutes for an event to be logged and become visible in the Event Log Viewer.
There are two possible event views in the window:
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.
Note: When you open the Event Log Window, only critical events are displayed. The default number of critical events displayed is 50.
1 |
From the Subsystem Management Window, select the View >> View Event Log pull-down menu option. Result: The Event Log dialog is displayed. |
2 |
Specify or type the number of events to retrieve in the Retrieve most recent events spinner box (numbers increment by 25). Note: When only critical events are selected, the label on this toggle will be Retrieve most recent critical events and the toggle will increase or decrease in increments of five. |
3 |
Toggle between all events or critical events only by selecting the View only critical events check box. |
4 |
Select Update to retrieve new events from the storage subsystem for display. The Update button:
|
5 |
Select Clear All to delete all entries in the Event Log. Important: If you want to save the current Event Log entries, be sure to save a copy of the log before clearing it. |
The Event Summary table has five columns:
Column |
Description |
Date/Time |
The date and time stamp of the event, according to the controller clock. Note: The Event Log initially sorts events based on sequence number (shown in the event details). Normally, this will correspond to the date/time. However, the two controller clocks in the storage subsystem could be unsynchronized. In this case, some perceived inconsistencies could be displayed in the Event Log relative to events and the date/time shown. Use the Storage Subsystem >> Set Controller Clocks pull-down menu option to synchronize storage subsystem controller clocks with the clock on your storage management station. |
Priority |
There are two priority values:
|
Component Type |
The component affected by the event. The component could be hardware, such as a drive or a controller, or it could be software, such as a logical drive or controller firmware. |
Component Location |
The physical location of the component in the storage subsystem. |
Description |
A description of the event. Example: Drive write failure - retries exhausted |
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 on 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 only focuses on those fields which require additional detail.
Column |
Description |
||||||||||||||||
Date/Time |
The date and time stamp of the error, according to the controller clock. Note: The Event Log initially sorts events based on sequence number (shown in the event details). Normally, this will correspond to the date/time. However, the two controller clocks in the storage subsystem could be unsynchronized. In this case, some perceived inconsistencies could be displayed in the Event Log relative to events and the date/time shown. Use the Storage Subsystem >> Set Controller Clocks pull-down menu option to synchronize storage subsystem controller clocks with the clock on your storage management station. |
||||||||||||||||
Category |
|
||||||||||||||||
Description |
A description of the event. Example: Drive write failure - retries exhausted |
To save selected events from the Summary area to a file, do the following:
1 |
Select the events you want to save to a file in the Summary View.
|
2 |
Select Save As. Result: The Save Events dialog is displayed. |
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 may 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 will append a .log extension by default. |
4 |
Type the file name of your choice in the File Name text box. Example: Name the file january13.log |
5 |
Select Save. Result: An ASCII text file containing the selected events, with a .log extension, is saved to the designated directory. |