We have AIX VIO servers connected to VMAX with PowePath multipath s/w installed.We are doing migrations from IBM array to VMAX. When I assign all the VIO Lpar volume group luns to VIO server all at once from the SMC, how can the AIX admin keep track of which lun goes to which lpar volume group?
Does he see any lun ID or device name/logical device id on the AIX server. I know what devices are going to a particular Lpar , does he see the same device id on his system too. I am assuming powermt display dev=all will give logical device id. Can I ask him to use it as a reference , is there any better alternative.
AIX is funky like that, it's hdisk number will not match LUN address you assigned on FA, for example here is output from lspv
hdiskpower8 00cb0d2fc39753f9 tsmlogvg active
now when i run "powermt display dev=all" i see this information (this is a test server with only one path to storage, typically you will see two hdisk devices)
so as you can see my symmetrix device id is 2AF5, PowerPath device is hdiskpower8 and native AIX device is hdisk11. If i run "symdev show 2AF5 -sid 123" ..you will see this output (snipped for abrivity)
Front Director Paths (1): { ---------------------------------------------------------------------- POWERPATH DIRECTOR PORT LUN --------- ---------- ---- -------- --------- PdevName Type Type Num Sts VBUS TID SYMM Host ---------------------------------------------------------------------- Not Visible N/A FA 08C:0 RW 000 00 0B8 N/A }
Mirror Set Type : [RAID-5,RAID-5,N/A,N/A]
as you can see this device is mapped to address 0B8, when converted from hex to decimal is address 184. If you are using dynamic lun masking (it's default on VMAX) that address 0B8 may not mean anything because it's dynamically masking and uses the next available address for that particular host. I think vSphere and HPUX are the only platforms that show you the actual LUN address that matches your FA address. So i would say use powerpath output or inq utility to keep track of devices.
Onething I can say is when you create LUN on the VMAX you will be assigning host LUN address either dynamically or manually, these addresses can be useful to keep track of the LUNs you provisioned, for example you have provisioned one LUN of 100 gig with LUN address from VMAX as "010" as this address is Hexadecimal always at VMAX end, your admin sees the LUN at the address "16" decimal on the host. That tells him you have provisioned a LUN of 100 gig at LUN address "16". I guess AIX shows this LUN at LUN address 16...Lets see how others will suggest this...
if you look in the SER NUM column ...123 is the serial number of your array and Volume column is your symdev device.
./inq.aix64_51 -showvol -nodots
Inquiry utility, Version V7.3-1108 (Rev 0.0) (SIL Version V7.2.0.0 (Edit Level 1108)
Copyright (C) by EMC Corporation, all rights reserved.
For help type inq -h.
i don't think there is one command that will do that, you can do this:
1) run lspv to list disks on the system:
lspv | grep -i power
hdiskpower0 00cb0d2f2f3330cb tsmdbvg active
hdiskpower1 00cb0d2f2f33326b tsmdbvg active
hdiskpower2 00cb0d2f2f333400 tsmstgpoolvg active
hdiskpower3 00cb0d2f2f333597 tsmstgpoolvg active
hdiskpower4 00cb0d2f2f33373a tsmstgpoolvg active
hdiskpower5 00cb0d2f2f3338de tsmstgpoolvg active
hdiskpower6 00cb0d2f33af665a tsmstgpoolvg active
hdiskpower7 00cb0d2f33af6816 tsmstgpoolvg active
hdiskpower8 00cb0d2fc39753f9 tsmlogvg active
2) use "powermt display dev=x" to see symmetrix device id:
dynamox
11 Legend
•
20419 Posts
•
87439 Points
3902
0
Posted December 22nd, 2010 21:00
AIX is funky like that, it's hdisk number will not match LUN address you assigned on FA, for example here is output from lspv
hdiskpower8 00cb0d2fc39753f9 tsmlogvg active
now when i run "powermt display dev=all" i see this information (this is a test server with only one path to storage, typically you will see two hdisk devices)
so as you can see my symmetrix device id is 2AF5, PowerPath device is hdiskpower8 and native AIX device is hdisk11. If i run "symdev show 2AF5 -sid 123" ..you will see this output (snipped for abrivity)
as you can see this device is mapped to address 0B8, when converted from hex to decimal is address 184. If you are using dynamic lun masking (it's default on VMAX) that address 0B8 may not mean anything because it's dynamically masking and uses the next available address for that particular host. I think vSphere and HPUX are the only platforms that show you the actual LUN address that matches your FA address. So i would say use powerpath output or inq utility to keep track of devices.