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

To prevent virtual media conflicts that can result in data damage, a proper accounting of how the
VSP whole disks are allocated for use by Virtual Disks needs to be done, as described in
Section 6.4.1.4 (page 69).
The following is the Virtual Disk resource statement form:
disk:avio_stor::disk:/dev/rdisk/diskX
where /dev/rdisk/diskX is an HP-UX esdisk character device file.
These device files can be located for a VSP LUN using the ioscan command.
For example:
# ioscan
# ioscan -NfunC disk
disk 64000/0xfa00/0x10 esdisk CLAIMED DEVICE
HP HSV210
/dev/disk/diskX /dev/rdisk/diskX
These system files are installed and removed using the insf and rmsf commands, respectively.
Device files are created automatically by the VSP for any storage it identifies during boot. New
devices connected or created after boot time, may require the use of ioscan and insf commands
to create the new device files. To remove old device files for storage, use the rmsf command.
A VSP disk LUN can also be specified using the corresponding Cluster DSF in the virtual disk
resource statement.
The following is the Virtual Disk resource statement form using cDSF:
disk:avio_stor::disk:/dev/rcdisk/diskX
where /dev/rcdisk/diskX is an HP-UX esdisk character cluster device special file.
These device files can be located for a VSP LUN using the ioscan command.
For example:
# ioscan
# ioscan -NfunC disk
disk 15 64000/0xfa00/0x4 esdisk CLAIMED DEVICE COMPAQ MSA1000 VOLUME
/dev/cdisk/diskX /dev/disk/diskY /dev/rcdisk/diskX /dev/rdisk/diskY
The /dev/rdisk/diskY is the corresponding device special file name for Cluster device special
file name /dev/rcdisk/diskX. The mapping between the two can be viewed using the ioscan
command.
For example:
# ioscan -m cluster_dsf
Cluster DSF Persistent DSF Legacy DSF(s)
=============================================================
/dev/rcdisk/diskX /dev/rdisk/diskY /dev/rdsk/c?t?d?
For example:
# cmsetdsfgroup -n <VSP-node1> -n <VSP-node2>
NOTE: If the VSP node is removed from the cDSF group then the cluster device special files must
be removed manually from that node.
These cluster device special files are installed and created using the cmsetdsfgroup(1M)
command. See cmsetdsfgroup(1M) manpage.
Cluster devices special files can be used as a backing store by the guests only if the Cluster DSF
(cDSF) feature is enabled on the VSP, that is, the VSP is a part of Cluster DSF group.
78 Storage devices