HP-UX vPars and Integrity VM V6.3 Administrator Guide
Example 38 Configuration
The VSP has an active VM guest configured with legacy AVIO backing stores.
hpux-atc-sd2-001par1# hpvmstatus
[Virtual Machines]
Virtual Machine Name VM # Type OS Type State #VCPUs #Devs #Nets Memory
==================== ===== ==== ======= ========= ====== ===== ===== =======
Dscvr_G03 3 SH HPUX On(OS) 2 2 1 4 GB
# hpvmstatus -p 3 -d | grep avio_stor
disk:avio_stor:0,0,0:disk:/dev/rdisk/disk51
disk:avio_stor:1,0,0:disk:/dev/rdisk/disk52
The boot device of the guest is /dev/rdisk/disk28, and it is mapped to the VSP device /dev/
rdisk/disk51
dscvr_g03# ioscan -kfNd gvsd
Class I H/W Path Driver S/W State H/W Type Description
======= === ======== ====== ========== ========== ====================
ext_bus 18 0/0/0/0 gvsd CLAIMED INTERFACE HPVM AVIO Stor Adapter
ext_bus 21 0/1/0/0 gvsd CLAIMED INTERFACE HPVM AVIO Stor Adapter
dscvr_g01# setboot
Primary bootpath : 0/0/0/0.0x0.0x0 (/dev/rdisk/disk28) -------------> Boot device
HA Alternate bootpath :
Alternate bootpath :
dscvr_g03# hpvmdevinfo
Device Type Bus,Device,Target Backing Store Type Host Device Name Virtual Machine Device Name
=========== ================= ================== ================ ============================
disk [0,0,0] disk /dev/rdisk/disk51 /dev/rdisk/disk28
disk [1,0,0] disk /dev/rdisk/disk52 /dev/rdisk/disk29
With legacy AVIO devices, there is no multi-pathing capability within the guest, so the guest has
one single path to each legacy AVIO device that it sees.
On the VSP, the two paths to the boot device of the guest are through the same FC port (/dev/
fclp3), which is on the HBA card in slot 10-0-1-0-2-3.
# ioscan -m lun /dev/rdisk/disk51
Class I Lun H/W Path Driver S/W State H/W Type Health Description
======= ==== ================ ======= ======= ====== ======= ======= ===========
disk 51 4000/0xfa00/0x1 esdisk CLAIMED DEVICE online HP HSV200
42/0/0/2/0/0/0/4/0/0/0.0x50001fe15006c768.0x4002000000000000 ----> Both paths are through the same HBA
port
42/0/0/2/0/0/0/4/0/0/0.0x50001fe15006c76d.0x4002000000000000 ----> Both paths are through the same HBA
port
/dev/disk/disk51 /dev/disk/disk51_p2 /dev/rdisk/disk51 /dev/rdisk/disk51_p2
/dev/disk/disk51_p1 /dev/disk/disk51_p3 /dev/rdisk/disk51_p1 /dev/rdisk/disk51_p3
OLR Operation:
# olrad -C 10-0-1-0-2-3
Critical Resource Analysis(CRA) in progress...
[NOTE: The CRA may take a few minutes to complete on large
configurations. It is recommended not to disrupt this operation.]
CRA REPORT SUMMARY: CRA detected SYSTEM CRITICAL usages.
Detailed CRA report is available in /var/adm/cra.log file.
The following is the snippet from the CRA log on the VSP:
ANALYSIS SCOPE: HPVM Legacy AVIO storage
This report provides details on critical HPVM legacy AVIO storage usage in the HPVM environment.
DETAILED HPVM legacy AVIO CRA REPORT:
SYSTEM CRITICAL RESULTS
Affected vPars or VM guest are:
3 --------> VM guest Dscvr_G03
If there was an additional path to /dev/rdisk/disk51 on the VSP through an FC card on a
slot other than 10-0-1-0-2-3, then, the CRA on slot 10-0-1-0-2-3 reports the severity as WARNING
and the administrator can proceed with the OLR operation without having to bring down the VM
guest Dscvr_G03.
192 PCI OLR support on VSPs