Escolar Documentos
Profissional Documentos
Cultura Documentos
English English
IBM®
Site map
Close
My IBM dashboard
My IBM dashboard
My IBM Cloud dashboard
Sign in
Site navigation
Site navigation
Close
IBM Support
My support
Downloads
Documents
Tickets
Communities
Training
Other
Marketplace
Products
Services
Industries
Developers
Support
Careers
IBM Support
What's new?
IBM Support
Question
How can i discover the storage mapping between client lpar and vio server?
Where does hdisk,cdrom come from?
Answer
System Administrator might be confused about this relationship and how to discover a dedicated storage device for troubleshooting .
This document will detail the easiest way to identify client-vios storage mapping
https://www.ibm.com/support/knowledgecenter/en/8284-22A/p8hat/p8hat_virtualscsi.htm
https://www.ibm.com/support/knowledgecenter/8284-22A/p8hat/p8hat_vfc.htm
Let's discover the mapping between the client lpar and vio server via CLI, when whole disk is mapped from vios to client
On AIX lpar client, let's start by identifying the lpar name and lpar id with "uname -L" command.
[aix_7.1test:root:/home/root:]> uname -L
5 aix_7.1test
[aix_7.1test:root:/home/root:]> lsmpio
name path_id status path_status parent connection
hdisk0 0 Enabled Sel,Opt fscsi0 5005076802205316,0
hdisk0 1 Enabled Non fscsi0 5005076802205317,0
hdisk0 2 Enabled Opt fscsi1 5005076802305316,0
hdisk0 3 Enabled Non fscsi1 5005076802305317,0
hdisk1 0 Enabled Clo fscsi0 5005076802205316,1000000000000
hdisk1 1 Enabled Clo fscsi0 5005076802205317,1000000000000
hdisk1 2 Enabled Clo fscsi1 5005076802305316,1000000000000
hdisk1 3 Enabled Clo fscsi1 5005076802305317,1000000000000
hdisk2 0 Enabled Clo fscsi0 5005076802205316,2000000000000
hdisk2 1 Enabled Clo fscsi0 5005076802205317,2000000000000
hdisk2 2 Enabled Clo fscsi1 5005076802305316,2000000000000
hdisk2 3 Enabled Clo fscsi1 5005076802305317,2000000000000
hdisk3 0 Enabled Clo fscsi0 5005076802205316,3000000000000
hdisk3 1 Enabled Clo fscsi0 5005076802205317,3000000000000
hdisk3 2 Enabled Clo fscsi1 5005076802305316,3000000000000
hdisk3 3 Enabled Clo fscsi1 5005076802305317,3000000000000
hdisk4 0 Enabled Clo vscsi0 810000000000
hdisk5 0 Enabled Clo vscsi0 820000000000
As you note the hdisk0, hdisk1, hdisk2 and hdisk3 have fscsi0 and fscsi1 as parent adapters, while hdisk4 and hdisk5 are disks provided through vscsi connection .
To confirm that above fscsi# adapters are NPIV, check that Description field is "Virtual Fibre Channel Client Adapter" by using "lsdev -Cc adapter"
To discover virtual scsi server and virtual fiber channel adapters with vio server name relation, use below commands :
OR
[aix_7.1test:root:]> kdb
START END <name>
0000000000001000 0000000005840000 start+000FD8
F00000002FF47600 F00000002FFDF9C8 __ublock+000000
000000002FF22FF4 000000002FF22FF8 environ+000000
000000002FF22FF8 000000002FF22FFC errno+000000
F1000F0A00000000 F1000F0A10000000 pvproc+000000
F1000F0A10000000 F1000F0A18000000 pvthread+000000
read vscsi_scsi_ptrs OK, ptr = 0xF1000000C020BE20
(0)> exit
[aix_7.1test:root:]>
OR
If you gathered "snap -ac" collection, vscsi and vfc mapping information are stored there :
/tmp/ibmsupt/vfc_client_collect/fcs#.state
/tmp/ibmsupt/client_collect/vscsi#.state
EX.
[aix_7.1test:root:/home/root:]>more /tmp/ibmsupt/client_collect/vscsi0.state
START END <name>
0000000000001000 0000000005840000 start+000FD8
F00000002FF47600 F00000002FFDF9C8 __ublock+000000
000000002FF22FF4 000000002FF22FF8 environ+000000
000000002FF22FF8 000000002FF22FFC errno+000000
F1000F0A00000000 F1000F0A10000000 pvproc+000000
F1000F0A10000000 F1000F0A18000000 pvthread+000000
read vscsi_scsi_ptrs OK, ptr = 0xF1000000C020BE20
(0)> vfcs
so :
fcs0 on the client is mapped to vfchost7 on vio server bladevio1
Now, we move to the virtual i/o server ( on Bladevio1 in this example, with padmin account )
VTD vtscsi1
Status Available
LUN 0x8100000000000000
Backing device hdisk7
Physloc U78A5.001.WIHC7F8-P1-C11-T1-W5005076802205316-L5000000000000
Mirrored false
VTD vtscsi2
Status Available
LUN 0x8200000000000000
Backing device hdisk8
Physloc U78A5.001.WIHC7F8-P1-C11-T1-W5005076802205316-L6000000000000
Mirrored false
Note :
- VTD is the virtual target device and can have a specific name as the following:
- We can identify the backing device by checking the matching of the LUN ID between child device on the client and correspondent LUN ID under vhost3
In this ex.
The hdisk4 on the client has hdisk7 as backing device on vio server bladevio1 with LUN 0x8100000000000000
NOTE: The more reliable way to see identifier's matching between the disks of the client and vios is the unique_id method :
The hdisk5 on the client has hdisk8 as backing device on vio server bladevio1 with LUN 0x8200000000000000
Status:LOGGED_IN
FC name:fcs0 FC loc code:U78A5.001.WIHC7F8-P1-C11-T1
Ports logged in:3
Flags:a<LOGGED_IN,STRIP_MERGE>
VFC client name:fcs0 VFC client DRC:U8406.70Y.06FB98A-V5-C5
Status:LOGGED_IN
FC name:fcs1 FC loc code:U78A5.001.WIHC7F8-P1-C11-T2
Ports logged in:3
Flags:a<LOGGED_IN,STRIP_MERGE>
VFC client name:fcs1 VFC client DRC:U8406.70Y.06FB98A-V5-C6
- The vfchost7 in bladevio1 with ID 1 and slot 32 (V1-C32 ) is mapped to VFC client name:fcs0
- The vfchost8 in bladevio1 with ID 1 and slot 33 (V1-C33 ) is mapped to VFC client name:fcs1
You can also get information about the mapping from IVM or HMC
it is very useful, especially when we have non AIX client lpar like IBMi or LINUX partition.
lpar_name=aix_7.1test,lpar_id=5,slot_num=2,state=1,adapter_type=client,remote_lpar_id=1,remote_lpar_name=bladevio1,remote_slot_num=31,is_required=1
NOTE : For HMC, specify option -m <Managed system> because an HMC can handle more than one managed system.
# lshwres -m <Managed System> -r virtualio --rsubtype scsi --level lpar --filter lpar_names=aix_7.1test
client information
lpar id=5
slot number=2
adapter_type = client
vios(bladevio1) information
remote_lpar_id = 1 >>>>>>>>> With IVM management the vios should be the first partition so ID=1
remote_lpar_name = bladevio1
remote_slot_num= 31
on client:
on vios:
You can identify the backing device by checking the matching of LUN ID between child device on client and the corresponding LUN ID under vhost3
lpar_name=aix_7.1test,lpar_id=5,slot_num=5,adapter_type=client,remote_lpar_id=1,remote_lpar_name=bladevio1,remote_slot_num=32,is_required=0,
"wwpns=C0507604831E003A,C0507604831E003B",state=1
lpar_name=aix_7.1test,lpar_id=5,slot_num=6,adapter_type=client,remote_lpar_id=1,remote_lpar_name=bladevio1,remote_slot_num=33,is_required=0,
"wwpns=C0507604831E003C,C0507604831E003D",state=1
lpar_name=aix_7.1test remote_lpar_name=bladevio1
lpar_id=5 remote_lpar_id=1
slot_num=5 remote_slot_num=32
adapter_type=client wwpns=C0507604831E003A,C0507604831E003B
------------------------------------------
lpar_name=aix_7.1test remote_lpar_name=bladevio1
lpar_id=5 remote_lpar_id=1
slot_num=6 remote_slot_num=33
adapter_type=client wwpns=C0507604831E003C,C0507604831E003D
----------------------------
On the client:
(0)> vfcs
On the vios :
Now, take a look on different Backing Device type (lv, cd-rom, tape and virtual media repository) mapped on dual vios through HMC
On AIX lpar client, let's start by identifying the lpar name and lpar id with "uname -L" command.
# uname -L
10 lpar1-149-nim-7.1.4
To discover the parent of all child devices (disk, cdrom, rmt, lv or virtual media repository) the below command is useful :
VTD vtopt2
Status Available
LUN 0x8200000000000000
Backing device /var/vio/VMLibrary/AIX_7.2_TL_72000000_BI_DVD_2OF2.iso
Physloc
Mirrored N/A
-------------------------
VTD vtopt6
Status Available
LUN 0x8500000000000000
Backing device cd0
Physloc U78AA.001.WZSJ7PA-P2-D9
Mirrored N/A
-------------------------
VTD vtscsi0
Status Available
LUN 0x8100000000000000
Backing device lpar1-rootvg
Physloc
Mirrored N/A
-------------------------
VTD vttape0
Status Available
LUN 0x8600000000000000
Backing device rmt0
Physloc U78AA.001.WZSJ7PA-P1-D1
Mirrored N/A
-vtopt2 is a virtual media repository with an ISO image under /var/vio/VMLibrary as backing device
For more information how to create and map virtual media repository, consult the following URL:
http://www-01.ibm.com/support/docview.wss?uid=isg3T1013047
Checking the matching of LUN id between client and vios1 to know the backing device.
NOTES:
VTD vtscsi2
Status Available
LUN 0x8100000000000000
Backing device nim2
Physloc
Mirrored N/A
-----------------------
VTD vtscsi3
Status Available
LUN 0x8200000000000000
Backing device prova
Physloc
Mirrored N/A
-------------------------------------------------------------------------------------------------------------------
Document information
More support for: Virtual I/O Server
Software version: 2.1.0.x-FP20.x, 2.1.1.x-FP21.x, 2.1.2.x-FP22.x, 2.1.2, 2.1.3, 2.2.0, 2.2.1, 2.2.2, 2.2.3, 2.2.4, 2.2.5
Reference #: T1025037
Site availability
Site assistance
Close
1-800-IBM-7378 (USA)
Back to top
Contact
Privacy
Terms of use
Accessibility
Select a country/region
Close
Providing your name and email will allow IBM to follow-up with you, if needed.
Name:
Email:
For technical support about IBM products, use IBM Support Portal.
IBM reviews all feedback. Not all comments will receive a response.
All responses will be in English.
About ongoing feedback at IBM
IBM collects opt-in feedback from IBM web users on a broad and continual basis throughout it's web sites. All feedback submitted are reviewed only by IBM employees or
IBM affiliates and no feedback is shared outside of IBM for any reason. See IBM's privacy policy and terms of use for further detail.
Back to Feedback
Close
Thank you for your rating. Please tell us how to improve the technical support document.
Providing your name and email will allow IBM to follow-up with you, if needed.
Name:
Email:
For technical support about IBM products, use IBM Support Portal.
IBM reviews all feedback. Not all comments will receive a response.
All responses will be in English.
IBM collects opt-in feedback from IBM web users on a broad and continual basis throughout it's web sites. All feedback submitted are reviewed only by IBM employees or
IBM affiliates and no feedback is shared outside of IBM for any reason. See IBM's privacy policy and terms of use for further detail.
IBM may use a third party to collect or process feedback. Any such party is also bound by the IBM policy. Currently we use opinionlab for feedback processing.
OpinionLab
Back to Feedback