HP-UX vPars and Integrity VM V6.3 Administrator Guide

7.4.3.4 Configuring storage for a vPar or VM guest with NPIV HBAs
You can assign storage for a vPar or VM guest with an NPIV HBA either before or after it starts
up. In both cases, the guest boots if a non-NPIV boot device is configured. If it does not have a
boot device, the guest boot halts at EFI.
To configure storage for a guest with an NPIV HBA:
1. Start the guest.
After the guest starts, the virtual port instance corresponding to the NPIV HBA assigned to the
guest logs into the FC fabric to which the physical HBA is connected.
2. Obtain the port WWN assigned to the NPIV HBA using the vparstatus or hpvmstatus
command on VSP.
3. Note the port WWN number, and work with the storage administrator to get the required
storage provisioned.
The storage administrator must use the storage management utility corresponding to the storage
device from which the administrator plans to provision storage, and then create LUNs of the
required capacity.
4. Present the LUNs to the port WWN corresponding to the NPIV HBA.
7.4.3.5 Enabling EFI driver enumeration policy for NPIV devices
Starting Integrity VM 4.3 (and later), the enumeration policy at EFI is differentiated by the following
storage types:
• SCSI (non-NPIV) LUNs
• FC (NPIV) LUNs
By default, the policy is to enumerate and configure only those AVIO storage devices that are
present as EFI boot options. When a new NPIV device is presented to a guest to be configured as
the boot device, it will not get automatically enumerated at EFI. To get a list of all NPIV devices at
EFI shell, the EFI enumeration policy must be modified to enumerate all FC LUNs using the drvcfg
utility.
106 NPIV with vPars and Integrity VM