X9720 Lun Layout; X9720 Component Monitoring; Identifying Failed I/O Modules On An X9700Cx Chassis - HP IBRIX X9720 System Administrator Manual

Lockup code
Hn66
Hn67
Hn68
Hn70
Hn71

X9720 LUN layout

The LUN layout is presented here for troubleshooting purposes.
For a capacity block with 1 TB HDDs:
2x 1 GB LUNs—These were used by the X9100 for membership partitions, and remain in the
X9720 for backwards compatibility. Customers may use them as they see fit, but HP does not
recommend their use for normal data storage, due to performance limitations.
1x 100 GB LUN—This is intended for administrative use, such as backups. Bandwidth to these
disks is shared with the 1 GB LUNs above and one of the data LUNs below.
8x ~8 TB LUNs—These are intended as the main data storage of the product. Each is supported
by ten disks in a RAID6 configuration; the first LUN shares its disks with the three LUNs
described above.
For capacity blocks with 2 TB HDDs:
The 1 GB and 100 GB LUNs are the same as above.
16x ~8 TB LUNs—These are intended as the main data storage of the product. Each pair of
LUNs is supported by a set of ten disks in a RAID6 configuration. The first pair of LUNs shares
its disks with the three LUNs described above.

X9720 component monitoring

The system actively monitors the following components in the system:
Blade Chassis: Power Supplies, Fans, Networking Modules, SAS Switches, Onboard
Administrator modules.
Blades: Local hard drives, access to all 9100cc controllers.
9100c: Power Supplies, Fans, Hard Drives, 9100cc controllers, and LUN status.
9100cx: Power Supplies, Fans, I/O modules, and Hard Drives.
If any of these components fail, an event is generated. Depending on how you have Events
configured, each event will generate an e-mail or SNMP trap. Some components may generate
multiple events if they fail. Failed components will be reported in the output of ibrix_vs -i,
and failed storage components will be reported in the output of ibrix_health -V -i.

Identifying failed I/O modules on an X9700cx chassis

When an X9700cx I/O module (or the SAS cable connected to it) fails, the X9700c controller
attached to the I/O module reboots and if the I/O module does not immediately recover, the
X9700c controller stays halted. Because there are two X9700cx I/O modules, it is not immediately
obvious which I/O module has failed. In addition, the X9700c controller may halt or appear to
fail for other reasons. This document describes how to identify whether the failure condition is on
the X9700cx I/O module or elsewhere.
146 Troubleshooting
Description
SAS core killed intentionally
SAS expander appears to have failed
SAS core reported invalid I/O index
EMU thermal shutdown imminent
EMU fan failure thermal shutdown