Start a Conversation

This post is more than 5 years old

Solved!

Go to Solution

10126

December 22nd, 2010 21:00

AIX lun reference

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.

1 Rookie

 • 

20.4K Posts

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)

Pseudo name=hdiskpower8
Symmetrix ID=000000100123
Logical device ID=2AF5
state=alive; policy=SymmOpt; priority=0; queued-IOs=0
==============================================================================
---------------- Host ---------------   - Stor -   -- I/O Path -  -- Stats ---
### HW Path                 I/O Paths    Interf.   Mode    State  Q-IOs Errors
==============================================================================
   0 fscsi0                    hdisk11   FA  8cA   active  alive      0      0

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.

125 Posts

December 22nd, 2010 21:00

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...

44 Posts

December 22nd, 2010 22:00

SAN_AK,

Just to keep you updated. Different OS behave differently, whatever you said may apply to other operating system, maybe to Vsphere.

That is not true with AIX as Dynamox mentioned it clearly with an example.

Thanks Dynamox for you time and help!

44 Posts

December 22nd, 2010 23:00

Dynamox,

How do I get a list of lun id's and its size for symmetrix devices on AIX. PowerPath is only managing sym devices in our environment

powermt display dev=all   displays whole bunch of data and it does not show the size of the device.

for inq utility I think the command is

inq -sym_wwn  but its not listing the device size.

want to know the command that lists the symmetrix device id's and its size.


1 Rookie

 • 

20.4K Posts

December 23rd, 2010 06:00

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.

-------------------------------------------------------------------------------------
DEVICE            :VEND    :PROD            :REV   :SER NUM    :Volume  :CAP(kb)
-------------------------------------------------------------------------------------
/dev/rhdiskpower0 :EMC     :SYMMETRIX       :5773  :1230890000 :   00890:    60315840
/dev/rhdiskpower1 :EMC     :SYMMETRIX       :5773  :1230891000 :   00891:    60315840
/dev/rhdiskpower2 :EMC     :SYMMETRIX       :5773  :1230892000 :   00892:    60315840
/dev/rhdiskpower3 :EMC     :SYMMETRIX       :5773  :1230893000 :   00893:    60315840
/dev/rhdiskpower4 :EMC     :SYMMETRIX       :5773  :1230894000 :   00894:    60315840
/dev/rhdiskpower5 :EMC     :SYMMETRIX       :5773  :1230895000 :   00895:    60315840
/dev/rhdiskpower6 :EMC     :SYMMETRIX       :5773  :1230896000 :   00896:    60315840
/dev/rhdiskpower7 :EMC     :SYMMETRIX       :5773  :1230897000 :   00897:    60315840
/dev/rhdiskpower8 :EMC     :SYMMETRIX       :5773  :1232af5000 :   02AF5:     8838720
/dev/rhdisk0      :IBM     :ST373207LC      :0     :0000039B21 :   00039:    71687000
/dev/rhdisk1      :IBM     :ST373207LC      :0     :0000039A62 :   00039:    71687000
/dev/rhdisk2      :EMC     :SYMMETRIX       :5773  :1230020000 :   00020:        2880
/dev/rhdisk3      :EMC     :SYMMETRIX       :5773  :1230890000 :   00890:    60315840
/dev/rhdisk4      :EMC     :SYMMETRIX       :5773  :1230891000 :   00891:    60315840
/dev/rhdisk5      :EMC     :SYMMETRIX       :5773  :1230892000 :   00892:    60315840
/dev/rhdisk6      :EMC     :SYMMETRIX       :5773  :1230893000 :   00893:    60315840
/dev/rhdisk7      :EMC     :SYMMETRIX       :5773  :1230894000 :   00894:    60315840
/dev/rhdisk8      :EMC     :SYMMETRIX       :5773  :1230895000 :   00895:    60315840
/dev/rhdisk9      :EMC     :SYMMETRIX       :5773  :1230896000 :   00896:    60315840
/dev/rhdisk10     :EMC     :SYMMETRIX       :5773  :1230897000 :   00897:    60315840
/dev/rhdisk11     :EMC     :SYMMETRIX       :5773  :1232af5000 :   02AF5:     8838720

1.3K Posts

January 8th, 2011 15:00

even on Hp-UX its not matching.  Also in addition to the inq , `sympd list` also returns the size, but the SE need installed for this.

1 Rookie

 • 

20.4K Posts

January 9th, 2011 17:00

target and lun has always mached for me on HPUX

1-9-2011 8-26-25 PM.png

44 Posts

January 11th, 2011 13:00

Is there any command on AIX which shows vg, pvid, and emc id information.

1 Rookie

 • 

20.4K Posts

January 11th, 2011 14:00

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:

powermt display dev=hdiskpower8
Pseudo name=hdiskpower8
Symmetrix ID=000000000123
Logical device ID=2AF5
state=alive; policy=SymmOpt; priority=0; queued-IOs=0
==============================================================================
---------------- Host ---------------   - Stor -   -- I/O Path -  -- Stats ---
###  HW Path                I/O Paths    Interf.   Mode    State  Q-IOs Errors
==============================================================================
   0 fscsi0                    hdisk11   FA  8cA   active  alive      0      0

137 Posts

January 13th, 2011 05:00

Hello,

  The inq.sol64 -no_dots -btl  command will give you, Device, Vendor, Serial number, Cap (KB) and Bus:TID: Lun info.

Not quite what you are looking for, but just in case it helps.

Regards,

   Nollaig

1.3K Posts

January 18th, 2011 18:00

This is really helpful Dynamox, you are right with the tid  , Lun matching on hp-ux. May be i did not understand what you tried to say from the symdev o/p /dev/rdsk/c58t0d7  :EMC    :SYMMETRIX      :5874  :68016af008 :    8838720:  3a:  0:  7 /dev/rdsk/c60t0d0  :EMC    :SYMMETRIX      :5874  :68000a0000 :        2880:  3c:  0:  0

85 Posts

May 13th, 2011 12:00

Hi dynamox,

I am going through the Article which looks good for the AIX host running Powerpath where I can look for the symdevice details agaianst lspv output.

I have AIX running and having Sym vmax Devices assigned but do not have Powerpath but have MPIO running on it. could you please help me how to

a) Identify the Sym Devices

b) how can map output from the MPIO command to the Sym Devices

c) How I can see from which Frame the devices are coming from.

Thanks

govind

1 Rookie

 • 

20.4K Posts

May 13th, 2011 22:00

did you try the inq utility ?

inq.aix64_51 -showvol -nodots

85 Posts

May 19th, 2011 06:00

Hi dynamox,

Thanks for your rely.  Unfortunately we dont have inq utility loaded on the hosts connected to the Storage.

thanks

govind

1 Rookie

 • 

20.4K Posts

May 19th, 2011 17:00

i looked at native AIX and MPIO (lspath) commands and could not easily find anything that would give symmetrix device id or wwn.  Inq utility runs stand alone, it does not need to be installed or anything like that ..simply copy it to the host and run it.

No Events found!

Top