HP-UX vPars and Integrity VM V6.1.5 Administrator Guide (5900-2295, April 2013)

PciBus | | |(Addr(Target Id) / 16) <-> HP-UX lun ID
| | | | |
V V V V V
disk 49 0/0/2/0.6.1 esdisk CLAIMED DEVICE HP Virtual Disk
/dev/rdisk/disk7 /dev/rdisk/disk7
Acpi(PNP0A03,0)/Pci(2|0)/Scsi(Pun16,Lun0)
^ ^ ^ ^
| | | |
PciBus | PCIFtn Addr(Target Id)
|
PciDev
In this example, exp1 / exp2 represents the quotient from exp1 divided by exp2 (integer
division), and exp1 % exp2 finds modulo of exp1 divided by exp2 (that is, finds the remainder
of an integer division).
2. get_info option of the gvsdmgr utility
If you are using the HP-UX DSF, the following gvsdmgr option can be used to get the VSD
LUN ID, which is the same as the Addr (Target Id) in the hpvmstatus display. The gvsdmgr
utility displays VSD LUN Id as a hexidecimal number. The first nibble of VSD LUN Id becomes
HP-UX lun ID, and the second nibble becomes HP-UX tgt ID.
The following example shows the get_info option with the gvdsmgr utility:
# gvsdmgr get_info -D /dev/gvsd0 -q lun=/dev/rdisk/disk7
Tue Oct 2 13:35:32 2007
Lun DSF : /dev/rdisk/disk7
VSD LUN Id : 0x16
Lun Hardware path : 0/0/2/0.6.1
LUN State : UNOPENED
The following is a method for mapping an Integrity VM HP-UX 11i v3 guest hardware path or
HP-UX 11i v3 DSF to an Integrity VSP hpvmstatus display using the ioscan utility:
# ioscan -m dsf /dev/rdisk/c0t6d1
Persistent DSF Legacy DSF(s)
========================================
/dev/rdisk/disk22 /dev/rdisk/c0t6d1
# ioscan -m lun /dev/rdisk/disk22
Class I Lun H/W Path Driver S/W State H/W Type Health Description
======================================================================
disk 22 64000/0xfa00/0x1 esdisk CLAIMED DEVICE online HP Virtual Disk
0/0/2/0.0x16.1x0
/dev/disk/disk22 /dev/rdisk/disk22
/dev/disk/disk22_p1 /dev/rdisk/disk22_p1
/dev/disk/disk22_p2 /dev/rdisk/disk22_p2
/dev/disk/disk22_p3 /dev/rdisk/disk22_p3
An HP-UX 11iv3 Lun Path hardware path displayed by the ioscan utility can be mapped to an
hpvmstatus utility output as follows:
PciDev
| PCIFtn
| | Addr(Target Id)
PciBus | | | Lun
| | | | |
V V V V V
0/0/2/0.0x16.1x0
9.1.3.5 Patch dependency
Table 7–2 lists the patch dependencies for the AVIO attached devices features.
9.1 Introduction to vParVM storage 115