HP Integrity VM 4.3 N-Port ID Virtualization - A brief overview

14
Since only V1 is on, and it has only one vHBA, there is only 1 VFC:
# ioscan -kfnNd fcd
Class I H/W Path Driver S/W State H/W Type Description
=====================================================================
fc 0 0/0/0/5/0/0/0 fcd CLAIMED INTERFACE HP 451871-B21 8Gb Dual Port PCIe Fibre Channel
Mezzanine (FC Port 1)
/dev/fcd0
fc 1 0/0/0/5/0/0/1 fcd CLAIMED INTERFACE HP 451871-B21 8Gb Dual Port PCIe Fibre Channel
Mezzanine (FC Port 2)
/dev/fcd1
fc 2 0/0/0/5/0/0/1.0x11 fcd CLAIMED INTERFACE HPVM Virtual FC (VFC) Controller
/dev/fcd2
The line above in bold shows that /dev/fcd2 is the VFC controller and is created under the Physical Fibre Channel
HBA /dev/fcd1. In other words, the vHBA was created with /dev/fcd1 serving as the backing physical device.
(Please note the difference in the descriptions of the two controllers.)
Accessing the NPIV LUNs from EFI
Once LUNs are presented to the vHBA, the administrator can choose to install the HP-UX OS image on a NPIV LUN.
If you run Ignite-UX at this time, the installation application will see the LUNs and make them visible to EFI.
If you are mounting a disk that has been pre-installed, or if you have problems seeing your LUN, then follow these
steps:
1. Once the VM boot process reaches the EFI shell, issue the command:
Shell> drvcfg –s
HP AVIO Stor Driver Configuration
==================================
Warning: Enumerating all SCSI or FC LUNs increases initialization times.
Enumerate all SCSI LUNs (Y/N)? [current setting: N]: N
Enumerate all FC LUNs (Y/N)? [current setting: N]: Y
Answer the last question “Y” to ensure that EFI can map the NPIV LUNs.
2. Reset the VM (Shell> reset) in order to make the changes active.
3. Run the devices command to get a listing of all of the LUNs available.
4. Identify the NPIV LUN by looking for the following format:
Acpi(PNP0A03,0)/Pci(4|0)/Fibre(WWN207000C0FFDA0287,Lun4001000000000000)/HD(Part3,Sig5CA3A696
-E349-11DF-8000-D6217B60E588)
5. At this point, you may boot from the NPIV LUN, just as you would from any disk (“fsN:” or “blkN:” followed by
“hpux”).
These steps are not necessary to access LUNs from a booted OS (including the Ignite-UX screens). The HP-UX and
install kernels do their own scan of the available I/O resources.