HP Integrity VM 4.3 N-Port ID Virtualization - A brief overview
13
Identifying vHBAs and LUNs in a VM
The ioscan command, when run in a virtual environment, can be used to identify the NPIV HBA from the set of HBAs
seen in the VM:
# ioscan -kfNd gvsd
Class I H/W Path Driver S/W State H/W Type Description
==================================================================
ext_bus 0 0/0/0/0 gvsd CLAIMED INTERFACE HPVM AVIO Stor Adapter
ext_bus 1 0/0/4/0 gvsd CLAIMED INTERFACE HPVM NPIV Stor Adapter
ext_bus 4 0/1/3/0 gvsd CLAIMED INTERFACE HPVM NPIV Stor Adapter
Note that the ioscan output listing of targets and LUNs on the vHBA in the VM is the same as a listing of SAN LUNs
on a standalone system (other than the driver used to access the device):
# ioscan -kfNH 0/0/4/0
Class I H/W Path Driver S/W State H/W Type Description
==================================================================
ext_bus 1 0/0/4/0 gvsd CLAIMED INTERFACE HPVM NPIV Stor Adapter
tgtpath 3 0/0/4/0.0x207000c0ffda0287 estp CLAIMED TGT_PATH Virtual Storage
HBA target served by gvsd driver, target port id 0x105ef
lunpath 5 0/0/4/0.0x207000c0ffda0287.0x0 eslpt CLAIMED LUN_PATH LUN path for ctl1
lunpath 8 0/0/4/0.0x207000c0ffda0287.0x4001000000000000 eslpt CLAIMED LUN_PATH LUN path for disk7
lunpath 9 0/0/4/0.0x207000c0ffda0287.0x401d000000000000 eslpt CLAIMED LUN_PATH LUN path for disk8
tgtpath 4 0/0/4/0.0x247000c0ffda0287 estp CLAIMED TGT_PATH Virtual Storage
HBA target served by gvsd driver, target port id 0x104ef
lunpath 6 0/0/4/0.0x247000c0ffda0287.0x0 eslpt CLAIMED LUN_PATH LUN path for ctl2
lunpath 11 0/0/4/0.0x247000c0ffda0287.0x4001000000000000 eslpt CLAIMED LUN_PATH LUN path for disk7
lunpath 12 0/0/4/0.0x247000c0ffda0287.0x401d000000000000 eslpt CLAIMED LUN_PATH LUN path for disk8
Identifying the VFC Controller’s creation in a virtual environment
If a VM with NPIV is not started, no VFC controllers are shown in the “ioscan –kfnNd fcd” output on the host.
Below is an example where the VM is down as shown by hpvmstatus command and the output of “ioscan –kfnNd
fcd” on the host.
# hpvmstatus
[Virtual Machines]
Virtual Machine Name VM # OS Type State #VCPUs #Devs #Nets Memory RHost
==================== ==== ======= ========= ====== ===== ===== ======= =====
V1 1 HPUX Off 1 1 1 3 GB -
V2 2 HPUX Off 1 1 1 2 GB -
V3 3 HPUX Off 2 2 1 3 GB -
V4 4 HPUX Off 1 1 1 2 GB -
# ioscan -kfnNd fcd
Class I H/W Path Driver S/W State H/W Type Description
=====================================================================
fc 0 0/0/0/8/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/8/0/0/1 fcd CLAIMED INTERFACE HP 451871-B21 8Gb Dual Port PCIe Fibre Channel
Mezzanine (FC Port 2)
/dev/fcd1
If a VM with an NPIV entry is started, one can identify if the VFC is created on the host (as shown below):
# hpvmstatus
[Virtual Machines]
Virtual Machine Name VM # OS Type State #VCPUs #Devs #Nets Memory RHost
==================== ==== ======= ========= ====== ===== ===== ======= =====
V1 1 HPUX On (OS) 1 1 1 3 GB -
V2 2 HPUX Off 1 1 1 2 GB -
V3 3 HPUX Off 2 2 1 3 GB -
V4 4 HPUX Off 1 1 1 2 GB -