Operating System - HP-UX
1754803 Members
3402 Online
108825 Solutions
New Discussion

Tracing "disks" on guests to the corresponding LV on host?

 
Doug O'Leary
Honored Contributor

Tracing "disks" on guests to the corresponding LV on host?

Hey;

 

Is there a foolproof method of identifying the LV on the host that corresponds to each PV on the guest system?  I'm pretty good at reasoning it out; however, there's one case that has me baffled.  

 

For instance: I'm trying to track down which PVs on the guest correspond to these 'disks' in the hpvmstatus output:

 

disk    avio_stor    0   0   0   0   0 lv        /dev/vgvmboot/rr3db21v2

disk    avio_stor    0   0   0   1   0 lv        /dev/vgvmboot/rr3db21v2_d1

disk    avio_stor    0   0   0   3   0 lv        /dev/vg00/rvgAD1db_d8

disk    avio_stor    0   2   0   5   0 lv        /dev/vg00/rvgAS1db_d8

disk    avio_stor    0   6   0   1   0 lv        /dev/vgvmboot/rr3db21v2_d2

 

The last one's pretty easy: 

 

disk     66  0/0/6/0.1.0   sdisk   CLAIMED     DEVICE       HP      Virtual LvDisk

                          /dev/dsk/c2t1d0   /dev/rdsk/c2t1d0

 

as the h/w path exacty matches the information in the storage interface section.  Most of the others were equally as obvious.  What's confusing me, though, is the one listed as tgt 3:

 

# ioscan -funC disk -H 0/0/0/0.3

Class     I  H/W Path     Driver S/W State   H/W Type     Description

=====================================================================

disk     23  0/0/0/0.3.0  sdisk   CLAIMED     DEVICE       HP      Virtual LvDisk

                         /dev/dsk/c0t3d0   /dev/rdsk/c0t3d0

disk     86  0/0/0/0.3.1  sdisk   CLAIMED     DEVICE       HP      Virtual LvDisk

                         /dev/dsk/c0t3d1   /dev/rdsk/c0t3d1

 

There are two disks listed on h/w address 0/0/0/0.3.  I assume it's the first one; however, I'd like a verifiable method of idnetifying that.  "I think that's it" doesn't sound good when talking to cients :)

 

Here's the entire storage section from the hpvmstatus.  

 

# hpvmstatus -P r3db21v2 | grep ^disk                  

disk    avio_stor    0   0   0   0   0 lv        /dev/vgvmboot/rr3db21v2

disk    avio_stor    0   0   0   1   0 lv        /dev/vgvmboot/rr3db21v2_d1

disk    avio_stor    0   0   0   2   0 lv        /dev/vgvmdata/rvgAS1ci_d0

disk    avio_stor    0   0   0   3   0 lv        /dev/vg00/rvgAD1db_d8

disk    avio_stor    0   0   0   4   0 lv        /dev/vgvmdata/rvgAD1db_d0

disk    avio_stor    0   0   0   5   0 lv        /dev/vgvmdata/rvgAD1db_d1

disk    avio_stor    0   0   0   6   0 lv        /dev/vgvmdata/rvgAD1db_d2

disk    avio_stor    0   0   0   7   0 lv        /dev/vgvmdata/rvgAD1db_d3

disk    avio_stor    0   0   0   8   0 lv        /dev/vgvmdata/rvgAD1db_d4

disk    avio_stor    0   0   0   9   0 lv        /dev/vgvmdata/rvgAD1db_d5

disk    avio_stor    0   0   0  10   0 lv        /dev/vgvmdata/rvgAD1db_d6

disk    avio_stor    0   0   0  11   0 lv        /dev/vgvmdata/rvgAD1db_d7

disk    avio_stor    0   0   0  12   0 lv        /dev/vgvmdata/rvgAS1db_d0

disk    avio_stor    0   0   0  13   0 lv        /dev/vgvmdata/rvgAS1db_d1

disk    avio_stor    0   0   0  14   0 lv        /dev/vgvmdata/rvgAS1db_d2

disk    avio_stor    0   0   0  15   0 lv        /dev/vgvmdata/rvgAS1db_d14

disk    avio_stor    0   0   0  16   0 lv        /dev/vgvmdata/rvgAS1db_d15

disk    avio_stor    0   0   0  17   0 lv        /dev/vgvmdata/rvgAS1db_d16

disk    avio_stor    0   0   0  18   0 lv        /dev/vgvmdata/rvgAS1db_d17

disk    avio_stor    0   0   0  19   0 lv        /dev/vgvmdata/rvgAD1db_d8

disk    avio_stor    0   0   0  20   0 lv        /dev/vgvmdata/rvgAD1db_d9

disk    avio_stor    0   0   0  21   0 lv        /dev/vgvmdata/rvgAD1db_d10

disk    avio_stor    0   0   0  22   0 lv        /dev/vgvmdata/rvgAD1db_d11

disk    avio_stor    0   0   0  23   0 lv        /dev/vgvmdata/rvgAD1db_d12

disk    avio_stor    0   0   0  24   0 lv        /dev/vgvmdata/rvgAD1db_d13

disk    avio_stor    0   0   0  25   0 lv        /dev/vgvmdata/rvgAD1db_d14

disk    avio_stor    0   0   0  26   0 lv        /dev/vgvmdata/rvgAD1db_d15

disk    avio_stor    0   2   0   0   0 lv        /dev/vgvmdata/rvgAS1db_d3

disk    avio_stor    0   2   0   1   0 lv        /dev/vgvmdata/rvgAS1db_d4

disk    avio_stor    0   2   0   2   0 lv        /dev/vgvmdata/rvgAS1db_d5

disk    avio_stor    0   2   0   3   0 lv        /dev/vgvmdata/rvgAS1db_d6

disk    avio_stor    0   2   0   4   0 lv        /dev/vgvmdata/rvgAS1db_d7

disk    avio_stor    0   2   0   5   0 lv        /dev/vg00/rvgAS1db_d8

disk    avio_stor    0   2   0   6   0 lv        /dev/vgvmdata/rvgAS1db_d9

disk    avio_stor    0   2   0   7   0 lv        /dev/vgvmdata/rvgAS1db_d10

disk    avio_stor    0   2   0   8   0 lv        /dev/vgvmdata/rvgAS1db_d11

disk    avio_stor    0   2   0   9   0 lv        /dev/vgvmdata/rvgAS1db_d12

disk    avio_stor    0   2   0  10   0 lv        /dev/vgvmdata/rvgAS1db_d13

disk    avio_stor    0   2   0  13   0 lv        /dev/vgvmdata/rvgAD1ci_d0

disk    avio_stor    0   2   0  14   0 lv        /dev/vgvmdata/rvgAD1ci_d1

disk    avio_stor    0   6   0   0   0 lv        /dev/vgvmdata/rvgAS1ci_d1

disk    avio_stor    0   6   0   1   0 lv        /dev/vgvmboot/rr3db21v2_d2

 

If someone could give me the clue I'm missing, I'd appreciate it.

 

Doug O'Leary

 

 

 


------
Senior UNIX Admin
O'Leary Computers Inc
linkedin: http://www.linkedin.com/dkoleary
Resume: http://www.olearycomputers.com/resume.html
3 REPLIES 3
Stan_M
HPE Pro

Re: Tracing "disks" on guests to the corresponding LV on host?

The thing is that the target>15 is not directly mappable to legacy io path.

See Admin manual 6.1.3.6 for mapping details.

 

The easiest way to achive what you are after is hpvmdevinfo command.

 

HTH

Stan

I work for HPE
Doug O'Leary
Honored Contributor

Re: Tracing "disks" on guests to the corresponding LV on host?

Hey;

 

Thanks for the reply.  I looked on both the host and a guest and I don't have that command installed.  I have an old version of HPIVM, though, so maybe that's it.

 

Could you show an example of what hpvmdevinfo displays?

 

Thanks.

 

Doug O'leary


------
Senior UNIX Admin
O'Leary Computers Inc
linkedin: http://www.linkedin.com/dkoleary
Resume: http://www.olearycomputers.com/resume.html
Dave Olker
HPE Pro

Re: Tracing "disks" on guests to the corresponding LV on host?

Here's an hpvmdevinfo output from one of my Integrity VM v4.2 servers.  Unfortunately the text formatting in this window doesn't help much.  Trust me, in a wide-format terminal window, the output is much easier to read when the columns line up properly:

 

atcuxbl1(/home/dolker) -> hpvmdevinfo
Virtual Machine Name Device Type Bus,Device,Target Backing Store Type Host Device Name Virtual Machine Device Name
==================== =========== ================= ================== ================ ===========================
atcuxvm1 disk [0,2,0] disk /dev/rdisk/disk36 /dev/rdisk/disk1
atcuxvm1 disk [0,2,1] disk /dev/rdisk/disk37 /dev/rdisk/disk3
atcux6 disk [0,0,0] disk /dev/rdisk/disk39 /dev/rdisk/disk1
atcux6 disk [0,0,1] disk /dev/rdisk/disk8 /dev/rdisk/disk3
atcuxvm4 disk [0,0,0] disk /dev/rdisk/disk40 /dev/rdisk/disk1
atcuxvm7 disk [0,0,0] lv /dev/hpvm/ratcuxvm7 /dev/rdisk/disk1
atcuxvm7 disk [1,0,0] disk /dev/rdisk/disk57 /dev/rdisk/disk4
atcuxvm8 disk [0,2,0] lv /dev/hpvm2/ratcuxvm8 /dev/rdisk/disk1
atcuxvm8 disk [1,0,0] disk /dev/rdisk/disk57 /dev/rdisk/disk3

 

Dave


I work for HPE

[Any personal opinions expressed are mine, and not official statements on behalf of Hewlett Packard Enterprise]
Accept or Kudo