HP StorageWorks HSG60 and HSG80 Array Controller and Array Controller Software Troubleshooting Guide (EK-G80TS-SA. C01, March 2005)

Troubleshooting Information
41HSG60 and HSG80 Array Controller and Array Controller Software Troubleshooting Guide
Spontaneous Event logs are reported to the Host Error log on SCSI Sense Data
Templates 01, 04, 05, 11, 12, 13, 14, 41, 51, and 90. See the “Event Reporting
Templates” chapter on page 135 for a detailed explanation of templates.
CLI Event reporting
CLI Event reports are automatically displayed on the maintenance terminal
(unless disabled with the FMU) and use %CER formatting, as shown in the
following example:
Figure 4: Sample CLI Event report showing %CER formatting
Running the controller diagnostic test
During startup, the controller automatically tests the device ports, host ports,
cache module, and value-added functions. If intermittent problems occur with one
of these components, run the controller diagnostic test in a continuous loop rather
than restarting the controller repeatedly.
Use the following steps to run the controller diagnostic test:
1. Connect a terminal to the controller maintenance port.
2. Start the self-test with one of the following commands:
SELFTEST THIS_CONTROLLER
SELFTEST OTHER_CONTROLLER
Note: The self-test runs until it detects an error or until you press the Reset button.
If the self-test detects an error, the self-test saves information about the error and
produces an OCP LED code for a daemon hard error. Restart the controller
to write the error information to the host error log, then check the host error log
for a built-in self-test failure event report. This report contains an
Instance Code, located at offset 32 through 35, that can be used to determine the
cause of the error. See the “Translating event codes” section that starts on page 70
for help translating Instance Codes.
%CER--HSG> --13-OCT-2004 04:32:20 (time not set)-- Previous controller-
operation stopped with display of solid fault code, OCP Code: 3F
HSG>