HP Matrix Operating Environment 7.3 Update 1 Release Notes

Required HBA firmware and OS drivers to access multi-initiator N-Port ID Virtualization

(NPIV) data disks

The 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

• Emulex CNA cards

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 releases.

NOTE: NPIV support has been added for Emulex CNA cards in HP-UX vPars and

Integrity VM version 6.3. The host must have WEB1310 release (B.11.31.1310) or

later versions of the Emulex FCoE driver installed. For details see, the HP-UX vPars and

Integrity VM V6.3 Release Notes at http://www.hp.com/go/hpux-hpvm-docs.

Suggested action

On Integrity blades with Emulex controllers and/or versions of HP-UX earlier than 11i

v3 March 2013 update release or HP-UX vPars and Integrity VM prior to version 6.3,

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.