On the VIO client LPAR
———————-

1. Determine parent adapter for virtual SCSI disk…

/=> lsdev -C -l hdisk0 -F parent
vscsi0
2. lscfg shows vscsi0 is a virtual adapter for partiton ID 2 (V2) in slot 3 (C3)…

/=> lscfg | grep vscsi0
* vscsi0 U9113.550.100A19F-V2-C3-T1 Virtual SCSI Client Adapter
3. hdisk0 LUN ID is 81 (L81000000000)

KERNVIOC1 /=> lscfg | grep hdisk0
* hdisk0 U9113.550.100A19F-V2-C3-T1-L810000000000 Virtual SCSI Disk Drive
Use the HMC to view client LPAR profile properties for the Virtual Adapter
————————————————————————–

Server Management
Open Properties of client LPAR
Select Virtual Adapters tab
View Virtual SCSI device for the virtual slot from lscfg command (in this case slot C3)

In our example, this virtual SCSI adapter belongs to partition 1 (1), slot 20 on the VIO server..
On the VIO Server

1. See what’s in the virtual slot for partion 1, slot 20 on the VIO server..

$ lsdev -vpd | grep V1-C20
vhost0 U9113.550.100A19F-V1-C20 Virtual SCSI Server Adapter
Device Specific.(YL)……..U9113.550.100A19F-V1-C20
vtscsi11 U9113.550.100A19F-V1-C20-L12 Virtual Target Device – Logical Volume
vtscsi10 U9113.550.100A19F-V1-C20-L11 Virtual Target Device – Logical Volume
vtscsi9 U9113.550.100A19F-V1-C20-L10 Virtual Target Device – Logical Volume
vtscsi7 U9113.550.100A19F-V1-C20-L8 Virtual Target Device – Logical Volume
vtscsi6 U9113.550.100A19F-V1-C20-L7 Virtual Target Device – Logical Volume
vtscsi5 U9113.550.100A19F-V1-C20-L6 Virtual Target Device – Logical Volume
vtscsi4 U9113.550.100A19F-V1-C20-L5 Virtual Target Device – Logical Volume
vtscsi8 U9113.550.100A19F-V1-C20-L9 Virtual Target Device – Logical Volume
vtscsi3 U9113.550.100A19F-V1-C20-L4 Virtual Target Device – Logical Volume
vtscsi2 U9113.550.100A19F-V1-C20-L2 Virtual Target Device – Logical Volume
vtscsi1 U9113.550.100A19F-V1-C20-L3 Virtual Target Device – Logical Volume
vtscsi0 U9113.550.100A19F-V1-C20-L1 Virtual Target Device – Logical Volume
Physical Location: U9113.550.100A19F-V1-C20
2. Use lsmap to view the VTD’s assigned to vhost0 and locate the VTD with the matching LUN ID. In our example, it’s VTD=vtscsi0 with LUN ID 81 (from above) which has a backing device of kernvioc1_lv…

$ lsmap -vadapter vhost0
SVSA Physloc Client Partition ID
————— ——————————————– ——————
vhost0 U9113.550.100A19F-V1-C20 0x00000002

VTD vtscsi0
LUN 0x8100000000000000
Backing device kernvioc1_lv
Physloc

(unrelated VTD’s removed for clarity)
3. See which physical devices contain kernvioc1_lv…

$ lslv -pv kernvioc1_lv
kernvioc1_lv:N/A
PV COPIES IN BAND DISTRIBUTION
hdisk1 090:000:000 88% 000:080:010:000:000
4. See if hdisk1 contains any other logical volumes…

$ lspv -lv hdisk1
hdisk1:
LV NAME LPs PPs DISTRIBUTION MOUNT POINT
mylv1 100 100 100..00..00..00..00 N/A
mylv2 200 200 200..00..00..00..00 N/A
kernvioc1_lv 90 90 90..00..00..00..00 N/A
kernvioc2_lv 90 90 90..00..00..00..00 N/A