HP Integrity Virtual Machines 4.2: Installation, Configuration, and Administration

0/5/0/0/0/0.0x500110a0008b9de2.0x0
/dev/rtape/tape5_BEST /dev/rtape/tape5_BESTn
/dev/rtape/tape5_BESTb /dev/rtape/tape5_BESTnb
# ioscan -m lun /dev/rtape/tape6_BEST
Class I Lun H/W Path Driver S/W State H/W Type Health Description
======================================================================
tape 6 64000/0xfa00/0x3 estape CLAIMED DEVICE online STK T9840B
0/4/1/0.0x500104f0004732d9.0x0
0/4/1/1.0x500104f0004732d9.0x0
0/4/1/0.0x500104f0004732da.0x0
0/4/1/1.0x500104f0004732da.0x0
/dev/rtape/tape6_BEST /dev/rtape/tape6_BESTn
/dev/rtape/tape6_BESTb /dev/rtape/tape6_BESTnb
Device tape5 is connected to the VM Host using a single HBA port (initiator). It has one
lunpath through initiator (0/5/0/0/0/0). Device tape6 is connected to the VM Host using
two HBA ports(initiators). It has four lunpaths through two initiators (0/4/1/0 and 0/4/1/1).
3. Here is an example of sharing a tape device using a single initiator (single lunpath):
# hpvmmodify -P guest1 -a tape:avio_stor::attach_path:0/5/0/0/0/0.0x500110a0008b9de2.0x0
# hpvmmodify -P guest2 -a tape:avio_stor::attach_path:0/5/0/0/0/0.0x500110a0008b9de2.0x0
# hpvmdevmgmt -l gdev:0/5/0/0/0/0.0x500110a0008b9de2.0x0
0/5/0/0/0/0.0x500110a0008b9de2.0x0,lunpath1:CONFIG=gdev,EXIST=YES,SHARE=NO,DEVTYPE=ATTACHPATHLUN,AGILE_DSF=
/dev/rtape/tape5_BESTn:guest1,guest2:0x01.0x00.0x03.0x500110a0008b9de1_lunpath1
# hpvmdevmgmt -m gdev:0/5/0/0/0/0.0x500110a0008b9de2.0x0:attr:SHARE=YES
# hpvmdevmgmt -l gdev:0/5/0/0/0/0.0x500110a0008b9de2.0x0
0/5/0/0/0/0.0x500110a0008b9de2.0x0,lunpath1:CONFIG=gdev,EXIST=YES,SHARE=YES,DEVTYPE=ATTACHPATHLUN,AGILE_DSF=
/dev/rtape/tape5_BESTn:guest1,guest2:0x01.0x00.0x03.0x500110a0008b9de1_lunpath1
The hpvmdevmgmt -m command can also take the following form:
# hpvmdevmgmt -m gdev:lunpath1:attr:SHARE=YES
Where "lunpath1" is the Integrity VM- generated alias for the hardware path. The Integrity
VM-generated alias of the form "lunpath#" can be used as shorthand in device management
commands, but it cannot be used in hpvmcreate or hpvmmodify commands.
4. Here is an example of sharing a tape device using different initiators (different lunpaths):
a. Add different paths to each guest:
# hpvmmodify -P guest1 -a tape:avio_stor::attach_path:0/4/1/0.0x500104f0004732d9.0x0
# hpvmmodify -P guest2 -a tape:avio_stor::attach_path:0/4/1/1.0x500104f0004732d9.0x0
Note that the two lunpath hardware paths in the previous example are through two
different initiators (0/4/1/0/ and 0/4/1/1/).
b. List the attributes of each path (Note the value of the AGILE_DSF attribute is the same
for both lunpaths.):
# hpvmdevmgmt -l gdev:0/4/1/0.0x500104f0004732d9.0x0
0/4/1/0.0x500104f0004732d9.0x0,lunpath3:CONFIG=gdev,EXIST=YES,SHARE=NO,DEVTYPE=ATTACHPATHLUN,AGILE_DSF=
/dev/rtape/tape6_BESTn:vme01,guest1:0x01.0x00.0x03.0x500104f0004732d8_lunpath3
# hpvmdevmgmt -l gdev:0/4/1/1.0x500104f0004732d9.0x0
0/4/1/1.0x500104f0004732d9.0x0,lunpath4:CONFIG=gdev,EXIST=YES,SHARE=NO,DEVTYPE=ATTACHPATHLUN,AGILE_DSF=
/dev/rtape/tape6_BESTn:guest2:0x01.0x00.0x03.0x500104f0004732d8_lunpath4
c. List the attributes of the parent tape DSF:
# hpvmdevmgmt -l gdev:/dev/rtape/tape6_BESTn
/dev/rtape/tape6_BESTn:CONFIG=gdev,EXIST=YES,SHARE=NO,DEVTYPE=ATTACH,SHARE_LUNPATHS=NO:
lunpath3,lunpath6,lunpath5,lunpath4:0x01.0x00.0x03.0x500104f0004732d8
d. Modify the SHARE_LUNPATHS attribute:
# hpvmdevmgmt -m gdev:/dev/rtape/tape6_BESTn:attr:SHARE_LUNPATHS=YES
NOTE: The SHARE_LUNPATHS and SHARE attributes take effect only after an
hpvmstop command.
e. Relist the attribute of the parent tape DSF:
# hpvmdevmgmt -l gdev:/dev/rtape/tape6_BESTn
7.1 Introduction to Integrity VM Storage 97