HP StorageWorks 9100 Extreme Data Storage System administration guide V1.0.2 (AN540-96018, February 2010)

ExDS9100c seven-segment display shows an H1, H2, C1, or C2 code
If the seven-segment display of an ExDS9100c enclosure shows an H1, H2, C1 or C2 error code this
indicates that one of the controllers has been halted. The amber fault LED of one of the controllers will
also be lit.
The usual cause is that an ExDS9100cx I/O module has failed. In this situation is is normal for the
ExDS9100cc controller that is attached to the I/O module to halt. See Identifying failed I/O modules
on an X9700cx chassis
ExDS9100cc has amber LED and code in seven-segment display
If the amber fault LED of an ExDS9100cc controller is on and the seven-segment does not show "on",
then you should follow this procedure:
1. Record the code displayed. This may be something like "H1".
2. Press the down arrow button beside the seven-segment display. The seven-segment display now
shows two digits. Record these. You now have a 4-character alphanumeric code.
3. If the 4-character alphanumeric code is Cxxxx or Hxxxx (where x is a numeric digit), then follow
the procedure in Identifying failed I/O modules on an X9700cx chassis
4. If the 4-character alphanumeric code is something else, re-seat the controller as follows. There is
no need to remove SAS cables.
a. Squeeze the controller thumb latch and rotate the latch handle down.
b. Pull the controller straight out of the chassis until it has clearly disengaged.
c. Push the controller fully into the chassis so it engages.
5. Wait for the controller to finish booting. If the seven-segment display shows "on", you have
resolved the issue.
6. If the seven-segment display continues to show an alphanumeric code, then record the full
4-character code as explained above and contact HP Support.
The exdsmgr command sometimes responds with: "Unable to contact
database...The service may be transitioning. Please try again."
This message can indicate that a server has failed. Within a few seconds the database should failover
to a backup server and the exdsmgr command will work normally. However, if the problem persists,
there is a problem with access to the database.
Workaround: You can isolate the problem as follows:
1. Use the mx alert status command to determine whether there are any issues with the Matrix.
The following relate to the operation of the database:
• Issues with the exdsadmin virtual host
• Issues with the varmxso device (that is, the /var/mxso utility filesystem)
• Issues with the mysqld service
Usually, you can determine the source of the problem and its resolution at this time. The resolution
may involve the reboot of a server.
2. Use the workaround described in Management database is inaccessible according to exdsmgr
command (or ExDS monitoring daemons).
Troubleshooting142