Technical data

4–2 Troubleshooting
Running the Controller’s Diagnostic Test
During start up, the controller automatically tests its device ports, host port, cache
module, and value-added functions. If you’re experiencing intermittent problems with
one of these components, you can run the controller’s diagnostic test in a continuous
loop, rather than restarting the controller over and over again.
Use the following steps to run the controller’s diagnostic test:
1. Connect a terminal to the controller’s 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 controller’s
reset button.
If the self test detects an error, it 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’s error log, then check the log for a “built-in self-test
failure” event report. This report will contain an instance code, located at offset
32 through 35, that you can use to determine the cause of the error. See “Translat-
ing Event Codes,” page 4-39 for help on translating instance codes.
Charging Diagnostics
Whenever you restart the controller, its diagnostic routines automatically check the
charge in the ECB’s batteries. If the batteries are fully charged, the controller reports
them as good and rechecks them every 24 hours. If the batteries are charging, the
controller rechecks them every four minutes. Batteries are reported as being either
above or below 50 percent in capacity. Batteries below 50 percent in capacity are
referred to as being low.