HP StorageWorks MSA2012i HP StorageWorks 2000 Modular Smart Array Reference Gu - Page 221

For example: Severity Level Info Critical Date/Time 2008-08-06 09:35:07 2008-04 12:12:05 Event Code 33 65 Event Serial Number A29856 A29809 Message Time/date has been changed Uncorrectable ECC error in buffer memory address 0x0 on bootup Viewing an Event Log Saved From SMU You can save event log data to a file on your network as described in "Saving Log Information to a File" on page 192. A saved log file has the following sections: ■ Contact information and comments ■ Combined SC event log - All events logged by both controllers. ■ SC event log for controller A - Events logged by controller A. ■ SC event log for controller B - Events logged by controller B. ■ SC error/warning log - Only critical and warning events for both controllers. The file lists up to 200 events for a single controller or up to 400 events for both controllers. The events are listed in chronological order; that is, the most recent event is at the bottom of a section. In the event log sections, the following information appears: ■ Event SN - Event Serial Number. The prefix (A or B) indicates which controller logged the event. This corresponds to the Event Serial Number column in SMU. ■ Date/Time - Year, month, day, and time when the event occurred. ■ Code - Event code that assists service personnel when diagnosing problems. This corresponds to the Event Code column in SMU. ■ Sev - I (informational); W (warning); C (critical). This corresponds to the Severity Level column in SMU. ■ Ctrlr - A or B indicates which controller logged the event. ■ Description - Information about the event. This corresponds to the Message column in SMU. Chapter 7 Troubleshooting Using SMU 221