In our example the LPAR is AIXLPAR2 and we have 2 VIOS AIXVIO1 and AIXVIO2.
Now we have the VIOSs.
Enter the AIXVIO1 first entering the corresponding number on the vtmenu.
4.- To enter the VIOS we have to enter as padmin user, to have root permisions we have to issue this command oem_setup_env.
Now on the VIOS we have to check if it sees hte LUNs
as padmin ---> lsdev -virtual ---> this will show all the virtualized devices from the VIOS.
$ lsdev -virtual
name status description
ent7 Available Virtual I/O Ethernet Adapter (l-lan)
ent8 Available Virtual I/O Ethernet Adapter (l-lan)
ent9 Available Virtual I/O Ethernet Adapter (l-lan)
ent10 Available Virtual I/O Ethernet Adapter (l-lan)
vasi0 Available Virtual Asynchronous Services Interface (VASI)
vhost0 Available Virtual SCSI Server Adapter
vhost1 Available Virtual SCSI Server Adapter
vhost2 Available Virtual SCSI Server Adapter
vhost3 Available Virtual SCSI Server Adapter
vhost4 Available Virtual SCSI Server Adapter
vhost5 Available Virtual SCSI Server Adapter
vhost6 Available Virtual SCSI Server Adapter
vhost7 Available Virtual SCSI Server Adapter
vhost8 Available Virtual SCSI Server Adapter
vhost9 Available Virtual SCSI Server Adapter
vsa0 Available LPAR Virtual Serial Adapter
vtscsi0 Available Virtual Target Device - Logical Volume
vtscsi1 Available Virtual Target Device - Logical Volume
vtscsi2 Available Virtual Target Device - Logical Volume
vtscsi3 Available Virtual Target Device - Logical Volume
vtscsi4 Available Virtual Target Device - Logical Volume
vtscsi5 Available Virtual Target Device - Disk
vtscsi6 Available Virtual Target Device - Disk
vtscsi7 Available Virtual Target Device - Disk
vtscsi8 Available Virtual Target Device - Disk
vtscsi9 Available Virtual Target Device - Disk
vtscsi10 Available Virtual Target Device - Disk
vtscsi11 Available Virtual Target Device - Disk
vtscsi12 Available Virtual Target Device - Disk
vtscsi13 Available Virtual Target Device - Disk
vtscsi14 Available Virtual Target Device - Disk
vtscsi15 Available Virtual Target Device - Disk
vtscsi16 Available Virtual Target Device - Disk
vtscsi17 Available Virtual Target Device - Disk
vtscsi18 Available Virtual Target Device - Disk
vtscsi19 Available Virtual Target Device - Disk
ent11 Available EtherChannel / IEEE 802.3ad Link Aggregation
ent12 Available Shared Ethernet Adapter
ent13 Available EtherChannel / IEEE 802.3ad Link Aggregation
ent14 Available Shared Ethernet Adapter
as root ---> lsdev -Cc disk ---> this will show all the fisical disks that the VIOS is seeing.
hdisk143 Available 05-08-02 EMC CLARiiON FCP RAID 5 Disk
hdisk144 Available 05-08-02 EMC CLARiiON FCP RAID 5 Disk
hdisk145 Available 05-08-02 EMC CLARiiON FCP RAID 5 Disk
hdisk146 Available 05-08-02 EMC CLARiiON FCP RAID 5 Disk
hdisk147 Available 05-08-02 EMC CLARiiON FCP RAID 5 Disk
hdisk148 Available 05-08-02 EMC CLARiiON FCP RAID 5 Disk
hdisk149 Available 05-08-02 EMC CLARiiON FCP RAID 5 Disk
hdisk150 Available 05-08-02 EMC CLARiiON FCP RAID 5 Disk
hdisk151 Available 05-08-02 EMC CLARiiON FCP RAID 5 Disk
hdisk152 Available 06-00-02 EMC CLARiiON FCP RAID 5 Disk
hdisk153 Available 06-00-02 EMC CLARiiON FCP RAID 5 Disk
hdisk154 Available 06-00-02 EMC CLARiiON FCP RAID 5 Disk
hdisk155 Available 06-00-02 EMC CLARiiON FCP RAID 5 Disk
hdisk156 Available 06-00-02 EMC CLARiiON FCP RAID 5 Disk
hdisk157 Available 06-00-02 EMC CLARiiON FCP RAID 5 Disk
hdisk158 Available 06-00-02 EMC CLARiiON FCP RAID 5 Disk
hdisk159 Available 06-00-02 EMC CLARiiON FCP RAID 5 Disk
hdisk160 Available 06-00-02 EMC CLARiiON FCP RAID 5 Disk
hdisk161 Available 06-00-02 EMC CLARiiON FCP RAID 5 Disk
hdisk162 Available 06-00-02 EMC CLARiiON FCP RAID 5 Disk
hdisk163 Available 06-00-02 EMC CLARiiON FCP RAID 5 Disk
hdisk164 Available 07-00-02 EMC CLARiiON FCP RAID 5 Disk
hdisk165 Available 07-00-02 EMC CLARiiON FCP RAID 5 Disk
hdisk166 Available 07-00-02 EMC CLARiiON FCP RAID 5 Disk
hdisk167 Available 07-00-02 EMC CLARiiON FCP RAID 5 Disk
hdisk168 Available 07-00-02 EMC CLARiiON FCP RAID 5 Disk
hdisk169 Available 07-00-02 EMC CLARiiON FCP RAID 5 Disk
hdisk170 Available 07-00-02 EMC CLARiiON FCP RAID 5 Disk
hdisk171 Available 07-00-02 EMC CLARiiON FCP RAID 5 Disk
hdisk172 Available 07-00-02 EMC CLARiiON FCP RAID 5 Disk
hdisk173 Available 07-00-02 EMC CLARiiON FCP RAID 5 Disk
hdisk174 Available 07-00-02 EMC CLARiiON FCP RAID 5 Disk
hdisk175 Available 07-00-02 EMC CLARiiON FCP RAID 5 Disk
hdiskpower0 Available 07-00-02 PowerPath Device
hdiskpower1 Available 07-00-02 PowerPath Device
hdiskpower2 Available 07-00-02 PowerPath Device
hdiskpower3 Available 07-00-02 PowerPath Device
hdiskpower4 Available 07-00-02 PowerPath Device
hdiskpower5 Available 07-00-02 PowerPath Device
hdiskpower6 Available 07-00-02 PowerPath Device
hdiskpower7 Available 07-00-02 PowerPath Device
hdiskpower8 Available 07-00-02 PowerPath Device
hdiskpower9 Available 07-00-02 PowerPath Device
hdiskpower10 Available 07-00-02 PowerPath Device
hdiskpower11 Available 07-00-02 PowerPath Device
hdiskpower12 Available 07-00-02 PowerPath Device
hdiskpower13 Available 07-00-02 PowerPath Device
hdiskpower14 Available 07-00-02 PowerPath Device
From the padmin side we can see that we have many virtualized LUNs ( vtscsi0-25) and many virutal cards (vhost0-9)
From the root side we can see that the VIOS is seeing the SAN and that we have PowerPath.
So to see how is the VIOS is mapping the devices we issue
#lsmap -all as padmin
SVSA Physloc Client Partition ID
--------------- -------------------------------------------- ------------------
vhost6 U9117.MMA.0626C64-V8-C62 0x00000006
VTD vtscsi3
Status Available
LUN 0x8100000000000000
Backing device rv_aixlpar1
Physloc
SVSA Physloc Client Partition ID
--------------- -------------------------------------------- ------------------
vhost7 U9117.MMA.0626C64-V8-C63 0x00000006
VTD vtscsi13
Status Available
LUN 0x8100000000000000
Backing device hdiskpower13
Physloc U789D.001.DQD48WT-P1-C2-T1-L30
SVSA Physloc Client Partition ID
--------------- -------------------------------------------- ------------------
vhost8 U9117.MMA.0626C64-V8-C72 0x00000007
VTD vtscsi4
Status Available
LUN 0x8100000000000000
Backing device rv_aixlpar2
Physloc
SVSA Physloc Client Partition ID
--------------- -------------------------------------------- ------------------
vhost9 U9117.MMA.0626C64-V8-C73 0x00000007
VTD vtscsi14
Status Available
LUN 0x8100000000000000
Backing device hdiskpower7
Physloc U789D.001.DQD48WT-P1-C2-T1-L19
VTD vtscsi15
Status Available
LUN 0x8200000000000000
Backing device hdiskpower8
Physloc U789D.001.DQD48WT-P1-C2-T1-L20
VTD vtscsi16
Status Available
LUN 0x8300000000000000
Backing device hdiskpower9
Physloc U789D.001.DQD48WT-P1-C2-T1-L22
VTD vtscsi17
Status Available
LUN 0x8400000000000000
Backing device hdiskpower10
Physloc U789D.001.DQD48WT-P1-C2-T1-L24
VTD vtscsi18
Status Available
LUN 0x8500000000000000
Backing device hdiskpower11
Physloc U789D.001.DQD48WT-P1-C2-T1-L26
VTD vtscsi19
Status Available
LUN 0x8600000000000000
Backing device hdiskpower14
Physloc U789D.001.DQD48WT-P1-C2-T1-L2
Here we have to do some research to know which is our LPAR.
So the first thing we can see is that the VIOS is also virtualizing the OS disks on more then one LPAR.
SVSA Physloc Client Partition ID
--------------- -------------------------------------------- ------------------
vhost6 U9117.MMA.0626C64-V8-C62 0x00000006
VTD vtscsi3
Status Available
LUN 0x8100000000000000
Backing device rv_aixlpar1
Physloc
SVSA Physloc Client Partition ID
--------------- -------------------------------------------- ------------------
vhost7 U9117.MMA.0626C64-V8-C63 0x00000006
VTD vtscsi13
Status Available
LUN 0x8100000000000000
Backing device hdiskpower13
Physloc U789D.001.DQD48WT-P1-C2-T1-L30
SVSA Physloc Client Partition ID
--------------- -------------------------------------------- ------------------
vhost8 U9117.MMA.0626C64-V8-C72 0x00000007
VTD vtscsi4
Status Available
LUN 0x8100000000000000
Backing device rv_aixlpar2
Physloc
We have the aixlpar1 and aixlpar2.
Backing device rv_aixlpar1
Backing device rv_aixlpar2
From this info we can see that the AIXLPAR2 LPAR is the Client Partition 0x00000007 with this number we have to see which are the LUNs that are beeing virtualized to that client partition.
SVSA Physloc Client Partition ID
--------------- -------------------------------------------- ------------------
vhost9 U9117.MMA.0626C64-V8-C73 0x00000007
VTD vtscsi14
Status Available
LUN 0x8100000000000000
Backing device hdiskpower7
Physloc U789D.001.DQD48WT-P1-C2-T1-L19
VTD vtscsi15
Status Available
LUN 0x8200000000000000
Backing device hdiskpower8
Physloc U789D.001.DQD48WT-P1-C2-T1-L20
VTD vtscsi16
Status Available
LUN 0x8300000000000000
Backing device hdiskpower9
Physloc U789D.001.DQD48WT-P1-C2-T1-L22
VTD vtscsi17
Status Available
LUN 0x8400000000000000
Backing device hdiskpower10
Physloc U789D.001.DQD48WT-P1-C2-T1-L24
VTD vtscsi18
Status Available
LUN 0x8500000000000000
Backing device hdiskpower11
Physloc U789D.001.DQD48WT-P1-C2-T1-L26
VTD vtscsi19
Status Available
LUN 0x8600000000000000
Backing device hdiskpower14
Physloc U789D.001.DQD48WT-P1-C2-T1-L2
From this we can see that our LPAR LUNs are beeing virtualized through the virtual card vhost9, and the disks are hdiskpower7 hdiskpower8 hdiskpower9 hdiskpower10 hdiskpower11 and hdiskpower14 also notice that each disk has a LUN ID for example 0x8100000000000000, with this number we can check on the LPAR to confirm if these are the LUNs.
We can also see the virtual name of the disks for example vtscsi14.
ON THE LPAR we issue hte lscfg command
# lscfg | grep hdisk
* hdisk25 U9117.MMA.0626C64-V7-C5-T1-L8c0000000000 Virtual SCSI Disk Drive
* hdisk24 U9117.MMA.0626C64-V7-C5-T1-L8b0000000000 Virtual SCSI Disk Drive
* hdisk23 U9117.MMA.0626C64-V7-C5-T1-L8a0000000000 Virtual SCSI Disk Drive
* hdisk22 U9117.MMA.0626C64-V7-C5-T1-L890000000000 Virtual SCSI Disk Drive
* hdisk21 U9117.MMA.0626C64-V7-C5-T1-L880000000000 Virtual SCSI Disk Drive
* hdisk20 U9117.MMA.0626C64-V7-C5-T1-L870000000000 Virtual SCSI Disk Drive
* hdisk19 U9117.MMA.0626C64-V7-C5-T1-L840000000000 Virtual SCSI Disk Drive
* hdisk18 U9117.MMA.0626C64-V7-C5-T1-L820000000000 Virtual SCSI Disk Drive
* hdisk17 U9117.MMA.0626C64-V7-C5-T1-L860000000000 Virtual SCSI Disk Drive
* hdisk16 U9117.MMA.0626C64-V7-C5-T1-L810000000000 Virtual SCSI Disk Drive
* hdisk15 U9117.MMA.0626C64-V7-C5-T1-L850000000000 Virtual SCSI Disk Drive
* hdisk14 U9117.MMA.0626C64-V7-C5-T1-L830000000000 Virtual SCSI Disk Drive
* hdisk1 U9117.MMA.0626C64-V7-C4-T1-L810000000000 Virtual SCSI Disk Drive
* hdisk7 U9117.MMA.0626C64-V7-C3-T1-L8c0000000000 Virtual SCSI Disk Drive
* hdisk6 U9117.MMA.0626C64-V7-C3-T1-L8b0000000000 Virtual SCSI Disk Drive
* hdisk5 U9117.MMA.0626C64-V7-C3-T1-L8a0000000000 Virtual SCSI Disk Drive
* hdisk4 U9117.MMA.0626C64-V7-C3-T1-L890000000000 Virtual SCSI Disk Drive
* hdisk3 U9117.MMA.0626C64-V7-C3-T1-L880000000000 Virtual SCSI Disk Drive
* hdisk2 U9117.MMA.0626C64-V7-C3-T1-L870000000000 Virtual SCSI Disk Drive
* hdisk13 U9117.MMA.0626C64-V7-C3-T1-L840000000000 Virtual SCSI Disk Drive
* hdisk12 U9117.MMA.0626C64-V7-C3-T1-L820000000000 Virtual SCSI Disk Drive
* hdisk11 U9117.MMA.0626C64-V7-C3-T1-L860000000000 Virtual SCSI Disk Drive
* hdisk10 U9117.MMA.0626C64-V7-C3-T1-L810000000000 Virtual SCSI Disk Drive
* hdisk9 U9117.MMA.0626C64-V7-C3-T1-L850000000000 Virtual SCSI Disk Drive
* hdisk8 U9117.MMA.0626C64-V7-C3-T1-L830000000000 Virtual SCSI Disk Drive
* hdisk0 U9117.MMA.0626C64-V7-C2-T1-L810000000000 Virtual SCSI Disk Drive
From that command we got two things first the AIX ID and second that we have 2 paths to that disk. (THE OTHER PATH IS FROM THE SECOND VIOS AIXVIO2)
hdisk16 U9117.MMA.0626C64-V7-C5-T1-L810000000000
hdisk10 U9117.MMA.0626C64-V7-C3-T1-L810000000000
With this we confirm that the LUNs that we saw on the VIOS is our LUNs.
We have 6 LUNs virtualized to the server.
5.- SCAN THE NEW DISKS.
On the VIOS as root we issue
#cfmgr -v
#lsdev -Cc disk
....
hdiskpower15 Available 07-00-02 PowerPath Device
hdiskpower16 Available 07-00-02 PowerPath Device
hdiskpower17 Available 07-00-02 PowerPath Device
hdiskpower18 Available 07-00-02 PowerPath Device
hdiskpower19 Available 07-00-02 PowerPath Device
hdiskpower20 Available 07-00-02 PowerPath Device
We have 6 new LUNs.
6.- MAP THE NEW LUNS TO THE LPAR.
FIRST OF ALL WE HAVE TO SEE THE reserv_lock ATTRIBUTE ON EACH NEW LUN.
This attribute it has to bee NO, that way we make sure that we can map the luns from both VIOS. If this attribute is in YES we are just going to be able to map from only one VIO and when we try to do it from the other one its going to return an error.
a.- CHANGE THE reserv_lock ATTRIBUTE
#chdev -a reserve_lock=no -l hdiskpower15 --> DO IT IN THAT ORDER IF NOT IS NOT GOING TO WORK AND THE OTHER VIOS STILL GOING TO RETURN ERROR WHEN YOU MAP.
Issue it for each LUN.
To check if it work
# lsattr -El hdiskpower15
cgname Consistency Group Name True
clr_q no Clear Queue (RS/6000) True
location Location True
lun_id 0x0 LUN ID False
lun_reset_spt yes FC Forced Open LUN True
max_coalesce 0x100000 Maximum coalesce size True
max_transfer 0x100000 Maximum transfer size True
pvid none Physical volume identifier False
pvid_takeover yes Takeover PVIDs from hdisks True
q_err yes Use QERR bit True
q_type simple Queue TYPE False
queue_depth 32 Queue DEPTH True
reassign_to 120 REASSIGN time out value True
reserve_lock no Reserve device on open True
rw_timeout 30 READ/WRITE time out True
scsi_id 0x384aef SCSI ID False
start_timeout 60 START unit time out True
ww_name 0x5006016d3b206d3b World Wide Name False
See that the reserve_lock attribute is no
b.- MAP THE LUNS FROM THE FIRST VIOS AIXVIO1
To do it we have to issue the next command as padmin for each disk.
#mkvdev -vdev hdiskpower15 -vadapter vhost9 ---> remember that the vhost9 we got it from the lsmap -all command.
To check it we issue the lsmap -all command as padmin.
SVSA Physloc Client Partition ID
--------------- -------------------------------------------- ------------------
vhost9 U9117.MMA.0626C64-V8-C73 0x00000007
VTD vtscsi14
Status Available
LUN 0x8100000000000000
Backing device hdiskpower7
Physloc U789D.001.DQD48WT-P1-C2-T1-L19
VTD vtscsi15
Status Available
LUN 0x8200000000000000
Backing device hdiskpower8
Physloc U789D.001.DQD48WT-P1-C2-T1-L20
VTD vtscsi16
Status Available
LUN 0x8300000000000000
Backing device hdiskpower9
Physloc U789D.001.DQD48WT-P1-C2-T1-L22
VTD vtscsi17
Status Available
LUN 0x8400000000000000
Backing device hdiskpower10
Physloc U789D.001.DQD48WT-P1-C2-T1-L24
VTD vtscsi18
Status Available
LUN 0x8500000000000000
Backing device hdiskpower11
Physloc U789D.001.DQD48WT-P1-C2-T1-L26
VTD vtscsi19
Status Available
LUN 0x8600000000000000
Backing device hdiskpower14
Physloc U789D.001.DQD48WT-P1-C2-T1-L2
VTD vtscsi20
Status Available
LUN 0x8700000000000000
Backing device hdiskpower15
Physloc U789D.001.DQD48WT-P1-C2-T1-L37
VTD vtscsi21
Status Available
LUN 0x8800000000000000
Backing device hdiskpower16
Physloc U789D.001.DQD48WT-P1-C2-T1-L39
VTD vtscsi22
Status Available
LUN 0x8900000000000000
Backing device hdiskpower17
Physloc U789D.001.DQD48WT-P1-C2-T1-L41
VTD vtscsi23
Status Available
LUN 0x8a00000000000000
Backing device hdiskpower18
Physloc U789D.001.DQD48WT-P1-C2-T1-L38
VTD vtscsi24
Status Available
LUN 0x8b00000000000000
Backing device hdiskpower19
Physloc U789D.001.DQD48WT-P1-C2-T1-L40
VTD vtscsi25
Status Available
LUN 0x8c00000000000000
Backing device hdiskpower20
Physloc U789D.001.DQD48WT-P1-C2-T1-L42
We can see the new LUNs and their respective virtual name.
c.- NOW on the second VIOS we san the new disks with
#cfgmgr -v as root
check with lsmap -all as padmin to see the vhost9 name and the virtual LUNs name.
from that command we got that the vhost card is vhost9.
so we MAP THE LUNS
# mkvdev -vdev hdiskpower15 -vadapter vhost9 --> as padmin, this for each of the LUNs.
7.- SCAN THE DISKS ON THE LPAR.
As root we issue
# cfgmgr -v
Now we can see the new luns and we have to check both paths to the LUNS.
# lscfg | grep hdisk
* hdisk25 U9117.MMA.0626C64-V7-C5-T1-L8c0000000000 Virtual SCSI Disk Drive
* hdisk24 U9117.MMA.0626C64-V7-C5-T1-L8b0000000000 Virtual SCSI Disk Drive
* hdisk23 U9117.MMA.0626C64-V7-C5-T1-L8a0000000000 Virtual SCSI Disk Drive
* hdisk22 U9117.MMA.0626C64-V7-C5-T1-L890000000000 Virtual SCSI Disk Drive
* hdisk21 U9117.MMA.0626C64-V7-C5-T1-L880000000000 Virtual SCSI Disk Drive
* hdisk20 U9117.MMA.0626C64-V7-C5-T1-L870000000000 Virtual SCSI Disk Drive
* hdisk19 U9117.MMA.0626C64-V7-C5-T1-L840000000000 Virtual SCSI Disk Drive
* hdisk18 U9117.MMA.0626C64-V7-C5-T1-L820000000000 Virtual SCSI Disk Drive
* hdisk17 U9117.MMA.0626C64-V7-C5-T1-L860000000000 Virtual SCSI Disk Drive
* hdisk16 U9117.MMA.0626C64-V7-C5-T1-L810000000000 Virtual SCSI Disk Drive
* hdisk15 U9117.MMA.0626C64-V7-C5-T1-L850000000000 Virtual SCSI Disk Drive
* hdisk14 U9117.MMA.0626C64-V7-C5-T1-L830000000000 Virtual SCSI Disk Drive
* hdisk1 U9117.MMA.0626C64-V7-C4-T1-L810000000000 Virtual SCSI Disk Drive
* hdisk7 U9117.MMA.0626C64-V7-C3-T1-L8c0000000000 Virtual SCSI Disk Drive
* hdisk6 U9117.MMA.0626C64-V7-C3-T1-L8b0000000000 Virtual SCSI Disk Drive
* hdisk5 U9117.MMA.0626C64-V7-C3-T1-L8a0000000000 Virtual SCSI Disk Drive
* hdisk4 U9117.MMA.0626C64-V7-C3-T1-L890000000000 Virtual SCSI Disk Drive
* hdisk3 U9117.MMA.0626C64-V7-C3-T1-L880000000000 Virtual SCSI Disk Drive
* hdisk2 U9117.MMA.0626C64-V7-C3-T1-L870000000000 Virtual SCSI Disk Drive
* hdisk13 U9117.MMA.0626C64-V7-C3-T1-L840000000000 Virtual SCSI Disk Drive
* hdisk12 U9117.MMA.0626C64-V7-C3-T1-L820000000000 Virtual SCSI Disk Drive
* hdisk11 U9117.MMA.0626C64-V7-C3-T1-L860000000000 Virtual SCSI Disk Drive
* hdisk10 U9117.MMA.0626C64-V7-C3-T1-L810000000000 Virtual SCSI Disk Drive
* hdisk9 U9117.MMA.0626C64-V7-C3-T1-L850000000000 Virtual SCSI Disk Drive
* hdisk8 U9117.MMA.0626C64-V7-C3-T1-L830000000000 Virtual SCSI Disk Drive
* hdisk0 U9117.MMA.0626C64-V7-C2-T1-L810000000000 Virtual SCSI Disk Drive
with this we can see that we have all the LUNs configured and both paths form the 2 VIOS.
Más concretamente lo que quieren probar los científicos es que el mundo en el que vivimos es en realidad… un holograma. Una idea que se sostiene sobre la teoría de que el espacio-tiempo no es un todo uniforme si no que se muestra separado y “pixelado” según vamos aumentando nuestra vista sobre él, como si fuera una imagen de baja resolución.