Avatar of it-rex
it-rex

asked on 

AIX mount points physical disks

we have these mountpoints

/dev/oraclelv01     33.62     11.24   67%    74222     3% /ora01
/dev/oraclelv02     33.69     31.97    6%       21     1% /ora02
/dev/oraclelv03     67.88     62.31    9%       19     1% /ora03
/dev/oraclelv04     67.81     62.18    9%      317     1% /ora04
/dev/oraclelv05     33.88     32.88    3%       20     1% /ora05
/dev/oraclelv06     33.88     33.13    3%       17     1% /ora06
/dev/oraclelv07     67.81     64.89    5%       22     1% /ora07
/dev/oraclelv08     67.75     59.06   13%      103     1% /ora08


we want to know which ones are on physically separate disks? this AIX
Unix OS

Avatar of undefined
Last Comment
it-rex
SOLUTION
Avatar of DonConsolio
DonConsolio
Flag of Austria image

Blurred text
THIS SOLUTION IS ONLY AVAILABLE TO MEMBERS.
View this solution by signing up for a free trial.
Members can start a 7-Day free trial and enjoy unlimited access to the platform.
See Pricing Options
Start Free Trial
ASKER CERTIFIED SOLUTION
Avatar of woolmilkporc
woolmilkporc
Flag of Germany image

Blurred text
THIS SOLUTION IS ONLY AVAILABLE TO MEMBERS.
View this solution by signing up for a free trial.
Members can start a 7-Day free trial and enjoy unlimited access to the platform.
Avatar of it-rex
it-rex

ASKER

but we are concerned about how the disks
hdisk* were created on the SAN side .
my understanding is that these hdisk* tht composes these lv's and VG's could be from 1 or more physical splinders on the SAN storage.

please advise.
Avatar of woolmilkporc
woolmilkporc
Flag of Germany image

It's not possible to find get this info using AIX commands.

You must find out the LUN ID of the hdisk in question with

lscfg -l hdiskx

and use this LUN ID on your SAN box to get allocation details.

Which SAN storage hardware do you use?

If in doubt please post the output of the above command, I think I will be able to assist you finding out the LUN ID.
Avatar of woolmilkporc
woolmilkporc
Flag of Germany image

A more straightforward way to find the LUN ID:

lsattr -HE -a lun_id -l hdiskx
Avatar of Tomunique
Tomunique
Flag of United States of America image

@WMP,
   Unless there's another ID that Z1(via lscfg) represents, these don't match for us.

lsattr returns "30"
lscfg retruns "3B", which is what our Storage team sees as the LDEV ID on the SAN.

The "30" appears to come from the "L#" in the physical location field.
I'm guessing this may vary by SAN Vendor.


On one of our VIO servers:

# lsattr -HE -a lun_id -l hdisk33
attribute value           description            user_settable

lun_id    0x3000000000000 Logical Unit Number ID False
#
# lscfg -vl hdisk33
  hdisk33          U78A5.001.WIH6507-P1-C12-T1-W50060E80100542DD-L3000000000000  Hitachi Disk Array (Fibre)

        Manufacturer................HITACHI
        Machine Type and Model......DF600F
        Part Number.................
        ROS Level and ID............30303030
        Serial Number...............87011549
        EC Level....................
        FRU Number..................1549
        Device Specific.(Z0)........00000432B3001102
        Device Specific.(Z1)........003B
        Device Specific.(Z2).........
        Device Specific.(Z3).........
        Device Specific.(Z4)........2...
        Device Specific.(Z5)........
        Device Specific.(Z6)........
Avatar of woolmilkporc
woolmilkporc
Flag of Germany image

@Tomunique

the LUN ID of your disk is definitely "30", as returned by lsattr.

lscfg returns this ID as well, see the "-L30..." part in the location data.

The "Z1" value seems to be a particularity of HDS.

It could well be that HDLM would update this field with information obtained directly from the SAN box.

The IBM DS8000 constructs the LUN IDs passed to AIX according to this pattern:

"40"[left 2 digiits of volid]"40"[right two digits of volid]

That's why I asked for the particular SAN storage type (and implicitly for the driver used).
Taking this info along with "lscfg" we could perhaps advance a bit further.

wmp

Avatar of it-rex
it-rex

ASKER

lsattr -HE -a lun_id -l hdisk4

returns


lsattr: 0514-528 The "lun_id" attribute does not exist in the predefined
        device configuration database.
Avatar of Tomunique
Tomunique
Flag of United States of America image

are you on an LPAR running behind a vio server?
If so, you'll have to look at the disks from the VIO server

Avatar of it-rex
it-rex

ASKER

we are using VIO yes
what to do?
SOLUTION
Avatar of Tomunique
Tomunique
Flag of United States of America image

Blurred text
THIS SOLUTION IS ONLY AVAILABLE TO MEMBERS.
View this solution by signing up for a free trial.
Members can start a 7-Day free trial and enjoy unlimited access to the platform.
Avatar of it-rex
it-rex

ASKER

thanks all
Unix OS
Unix OS

Unix is a multitasking, multi-user computer operating system originally developed in 1969 at Bell Labs. Today, it is a modern OS with many commercial flavors and licensees, including FreeBSD, Hewlett-Packard’s UX, IBM AIX and Apple Mac OS-X. Apart from its command-line interface, most UNIX variations support the standardized X Window System for GUIs, with the exception of the Mac OS, which uses a proprietary system.

33K
Questions
--
Followers
--
Top Experts
Get a personalized solution from industry experts
Ask the experts
Read over 600 more reviews

TRUSTED BY

IBM logoIntel logoMicrosoft logoUbisoft logoSAP logo
Qualcomm logoCitrix Systems logoWorkday logoErnst & Young logo
High performer badgeUsers love us badge
LinkedIn logoFacebook logoX logoInstagram logoTikTok logoYouTube logo