HP Matrix Operating Environment 7.3 Release Notes

3. Use the HBA vendor's utility to configure the HBA's boot path to boot from the desired SAN
boot LUN.
4. Power off the target server after the Boot Controller Order and the HBA's boot path have been
configured correctly.
Required HBA firmware and OS drivers to access multi-initiator N-Port ID Virtualization (NPIV) data
disks
The HP blade multi-initiator NPIV feature allows you to configure multiple WWNs for a single HBA
connected with a Virtual Connect Fibre Channel module. Although Matrix OE automates the
configuration, certain versions of HBA firmware and drivers are required to access multi-initiator
NPIV data disks configured for any target BL server.
Suggested action
The HBA firmware and drivers shown for the following operating systems are required to support
multi-initiator NPIV data disks.
QLogic HBA (BIOS version 2.07 or higher)
RHEL 5.3 and higher
SLES 11 and higher
SLES 10 SP3 and higher
Windows 2003/2008: QLogic driver 9.1.7.29 or higher
Emulex HBA (BIOS version 3.11a3 or higher)
RHEL 5.4 or higher
SLES 10 SP3 or higher
SLES 11 in-box driver not yet available. Requires out-of-box Emulex driver version: 8.2.8.32
Windows 2003/2008: Emulex driver 5.00.17.06-2 or higher
Multi-initiator NPIV support on Integrity blades
Multi-initiator NPIV features used by Matrix OE and Virtual Connect Enterprise Manager are
supported on Integrity blades using the QLogic FC controller with the HP-UX 11i v3 Update 8
(March 2011) and later release. Multi-initiator NPIV features are supported on Integrity blades
with Emulex FC controllers with HP-UX 11iv3 March 2013 update and later release.
Suggested action
On Integrity blades with Emulex controllers and/or versions of HP-UX earlier than 11i v3 March
2013 update release, create a single storage pool entry that combines a boot volume and the
data volumes intended to be allocated to a single physical server. You can do this in one of the
following ways:
Pre-provision any number of these composite storage pool entries to enable fully automated
allocation of SAN volumes to physical servers.
Pre-provision storage pool entries with only boot volumes. An automated provisioning request
pauses after the operating system is deployed if the infrastructure service template specifies
data disks. You can modify the storage pool entry allocated to the server to add data volumes,
and then continue the request.
Required software versions for FlexFabric Integrity physical provisioning support
Matrix OE infrastructure orchestration requires the following minimum software versions to support
HP FlexFabric for Integrity physical provisioning:
Ignite-UX C.7.12.475 or higher
HP-UX 11i v3 Update 8 (March 2011) or higher
22 Issues and suggested actions