3PAR InForm OS 2.2.4 Configuration Matrix (QL226-96281, November 2011)

HP Support Policy
Support of Non-Compliant Environments
 A non-compliant configuration is defined as the use of the HP 3PAR Storage System outside of
current published specifications including Storage System Technical Specifications, InForm OS
Configuration Matrix (this document), and the HP 3PAR Implementation Guides.
 The Configuration Matrix represents the logical and physical elements that are fully qualified and
supported by HP. Any issues or problems with supported configurations receive our highest priority,
our very best effort, and have a high probability of being reproduced, quickly explained, and
aggressively corrected. Where a customer consciously chooses to implement components or
configurations that are not included in this matrix, they do so at their own risk, and with the
understanding that any issues for such non-compliant configurations will be handled on a
commercially reasonable best effort basis, at a priority level subservient to supported configurations,
and could invoke an extended response and resolution timeframe. It is also possible that complex
problems in non-compliant configurations cannot be reproduced within HP QA and test lab
environments, and the customer should be prepared to provide their own lab environment for
problem reproduction and troubleshooting activities. The end-result of a troubleshooting exercise for
a non-compliant configuration could be the realization that an unsupported element might not
function within HP’s ecosystem, resulting in the need to revert, change, or upgrade disruptively in
order to resolve a specific problem.
 Under most circumstances, HP will not specifically refuse to troubleshoot non-compliant
configurations, but it’s important for customers with non-compliant configurations to understand the
risks associated with deployment of these configurations. Customers implementing non-compliant
configurations should be prepared with Disaster Recovery solutions and contingency plans to work
around these configurations if the need arises. It’s also strongly recommended that non-compliant
configurations be brought into compliance with the Configuration Matrix as soon as possible.
Support of OEM FC Host Bus Adapters
 We qualify storage systems for FC SAN connectivity to QLogic and Emulex branded FC HBAs and
associated drivers/FW across all OS platforms we support, and branded HBA models (HP, IBM,
AIX, and others) applying specifically to the cases recorded in this configuration matrix.
 Whether listed in this configuration matrix or not, we will support rebranded versions of QLogic and
Emulex HBAs under the following conditions:
 The rebranded HBA HW is identical to that sold under the QLogic or Emulex brand.
 The driver, FW, and BIOS versions listed as qualified in this configuration matrix are used
on those rebranded HBAs.
Note: HBAs that are not listed have not been tested by HP.
Support of OEM FC Switches
 We qualify storage systems for FC SAN connectivity to Brocade, Cisco, and QLogic FC switches
and associated switch FW/OS.
 Whether listed in this configuration matrix or not, we will support rebranded versions of Brocade,
QLogic, and Cisco FC switches under the following conditions:
 The rebranded FC switch hardware is identical to that sold under the Brocade, QLogic, or
Cisco brand.
 The switch FW/OS versions listed as qualified in this configuration matrix are used on those
rebranded FC switches.
Note: Switches that are not listed have not been tested by HP.