- Community Home
- >
- Servers and Operating Systems
- >
- Operating Systems
- >
- Operating System - HP-UX
- >
- Re: LUN details with mount point
Categories
Company
Local Language
Forums
Discussions
Forums
- Data Protection and Retention
- Entry Storage Systems
- Legacy
- Midrange and Enterprise Storage
- Storage Networking
- HPE Nimble Storage
Discussions
Discussions
Discussions
Forums
Forums
Discussions
Discussion Boards
Discussion Boards
Discussion Boards
Discussion Boards
- BladeSystem Infrastructure and Application Solutions
- Appliance Servers
- Alpha Servers
- BackOffice Products
- Internet Products
- HPE 9000 and HPE e3000 Servers
- Networking
- Netservers
- Secure OS Software for Linux
- Server Management (Insight Manager 7)
- Windows Server 2003
- Operating System - Tru64 Unix
- ProLiant Deployment and Provisioning
- Linux-Based Community / Regional
- Microsoft System Center Integration
Discussion Boards
Discussion Boards
Discussion Boards
Discussion Boards
Discussion Boards
Discussion Boards
Discussion Boards
Discussion Boards
Discussion Boards
Discussion Boards
Discussion Boards
Discussion Boards
Discussion Boards
Discussion Boards
Discussion Boards
Discussion Boards
Discussion Boards
Discussion Boards
Discussion Boards
Discussion Boards
Discussion Boards
Discussion Boards
Community
Resources
Forums
Blogs
- Subscribe to RSS Feed
- Mark Topic as New
- Mark Topic as Read
- Float this Topic for Current User
- Bookmark
- Subscribe
- Printer Friendly Page
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
тАО04-22-2011 02:31 AM
тАО04-22-2011 02:31 AM
I need to find out LUN info with mount point details. The HPUX machine connected with IBM Storage DS4800 so unable to find which LUN belongs to which mount point.
Is there any command on hpux to check or any formula to calculate ?
Regards,
Sumant M Kumar
Solved! Go to Solution.
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
тАО04-22-2011 06:30 AM
тАО04-22-2011 06:30 AM
Re: LUN details with mount point
for disk in `ioscan -fknC disk | grep rdsk | awk {'print $2'}`; do diskinfo ${disk}; done >/tmp/disklist
(all of the above is on one line)
edit /tmp/disklist and look for the line where it says product ID and find the disks with some sort of IBM designator (I am not familiar with DS4800 so I can't tell you the exact string but it should have IBM letters in it)
Now that you identified the cXtXdX device files for your DS4800 LUNs, it all depends what kind of volume management you are using, i.e.. LVM or VxVM. I am assuming you are using one of these volume managers. Everyone does nowadays.
Provide the output from bdf and people can tell you what you are using, if you don't know the difference between LVM and VxVM
UNIX because I majored in cryptology...
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
тАО04-23-2011 10:49 AM
тАО04-23-2011 10:49 AM
Solutionan ioscan -fnCdisk will give something like:
disk 249 0/2/1/0.3.0.239.0.13.6 sdisk CLAIMED DEVICE HP MSA2312fc
/dev/dsk/c33t13d6 /dev/rdsk/c33t13d6
Taking the last 3 octets of the disk HW address,
0.13.6
you can calculate the LUN from the array by:
LUN= $(( 128*0 + 8*13 + 6 )) = 110
or generally by 128*3rd + 8*2nd + 1st
.
I wrote a script to do that parsing, but it is very complicated and
dependent on certain kinds of arrays.
Now, for your case, you would have to do:
1) get the Volume Group via:
mount | grep mountpointv2 \
|sed -e 's/.*\/dev\///' -e 's/\/.*//'
2) get the physical paths via:
vgdisplay -v VG | grep -e 'PVG Name' -e 'PV Name'
3) ioscan -fnCdisk < /tmp/ioscan-fnCdisk
4) peruse the /tmp/ioscan-fnCdisk file
for the PV names from step 2
5) use the above formula to get the LU number
E.g.,
1) ## mount | grep /oradatamt \
|sed -e 's/.*\/dev\///' -e 's/\/.*//'
vgoradatamt
2) ## vgdisplay -v vgoradatamt | grep -e 'PVG Name' -e 'PV Name'
PV Name /dev/dsk/c33t13d6
PV Name /dev/dsk/c34t13d6 Alternate Link
PV Name /dev/dsk/c31t13d6 Alternate Link
PV Name /dev/dsk/c32t13d6 Alternate Link
PV Name /dev/dsk/c35t13d6
PV Name /dev/dsk/c36t13d6 Alternate Link
PV Name /dev/dsk/c37t13d6 Alternate Link
PV Name /dev/dsk/c38t13d6 Alternate Link
PVG Name vgoramt_pMSA
PV Name /dev/dsk/c33t13d6
PVG Name vgoramt_lMSA
PV Name /dev/dsk/c35t13d6
NOTE: In my case here, I have PVGs, which devices can be ignored --
there're the same as a device in the part above the PVG section.
NOTE: The LUN # is the SAME for all paths (alternate links) to a device.
Duh. Winning...
er, I mean,
Duh.. thay're pointing to the same LUN!
3) ioscan -fnCdisk < /tmp/ioscan-fnCdisk
4) perusing the /tmp/ioscan-fnCdisk file or using
## grep -e ^disk -e /dev/dsk/c33t13d6 /tmp/ioscan-fnCdisk
I get
...
...
...
disk 249 0/2/1/0.3.0.239.0.13.6 sdisk CLAIMED DEVICE HP MSA2312fc
/dev/dsk/c33t13d6 /dev/rdsk/c33t13d6
...
...
...
5) use formula :
## echo $(( 128*0 + 8*13 + 6 ))
110
so my LUN for that device is 110
bv
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
тАО04-23-2011 10:54 AM
тАО04-23-2011 10:54 AM
Re: LUN details with mount point
ioscan -m dsf
to see the legacy name for the flexible name.
bv
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
тАО04-23-2011 11:12 PM
тАО04-23-2011 11:12 PM
Re: LUN details with mount point
echo $(( 128*0 + 8*13 + 6 ))
are we skipping continuous binary conversion here ( like 16,8,4,2,0 ) ..just to know the fact over here
Thanks
Manix
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
тАО04-24-2011 04:02 AM
тАО04-24-2011 04:02 AM
Re: LUN details with mount point
It's not a simple progression of powers of 2.
In cXtTdL,
relating to the last 3 octets of the HW address,
the T comes from the 2nd octet and L comes from the 3rd octet
But, L (3rd octet) goes only from 0-7,
so, T represents a multiple of 8.
The progression of LUNs would be:
...
HW 0.0.6 --> t0d6 = (0*8) + 6 = 6
HW 0.0.7 --> t0d7 = (0*8) + 7 = 7
then we roll over to
HW 0.1.0 --> t1d0 = 1*8 (+0) = 8
T (2nd octet) only goes from 0-15,
so, the first octet represents a multiple of 8*16 = 128.
The progression of LUNs would be:
...
HW 0.15.6 --> cNt15d6 = (15*8) + 6 = 126
HW 0.15.7 --> cNt15d7 = (15*8) + 7 = 127
then we roll over to
HW 1.0.0 --> cMt0d0 = 1*128 (+0*8) (+0) = 80
A little simplified, we can say:
There's nothing special, really, about these restrictions (0-7 an 0-15) in the cXtTdL convention. It all relates to trying to fit Fibre Channel devices/LUNs into the original, simple, halcyon days of simple SCSI disk naming convention, where the cXtTdL came from.
Back then, all we had were disks and tapes and the T was the SCSI target and L was the target's LUN (still is, for real SCSI disks). LUN was 3 bits and so restricted to 0-7.
However, real SCSI disks *always* report as LUN0 (so L was always 0 -- and still is for all the disks attached to actual SCSI busses on our systems -- check it out for the "internal" disks).
So, interestingly, the DISK ID that we change with the jumpers on a real SCSI disk or the switches on a Jamaica box changes the TARGET number, not the LUN number. LUN 0 is required for all targets, and so the DISK always reports as LUN0, whatever its target is.
SCSI-1 spec allowed up to 8 targets on the bus. while
SCSI-2 spec allowed only up to 16 targets on the bus
-- hence T = 0-15.
bv
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
тАО04-25-2011 03:24 AM
тАО04-25-2011 03:24 AM
Re: LUN details with mount point
Dear Bob & Experts , Let me know if there is any command like xpinfo -i for IBM storage also.
Regards,
Sumant M Kumar
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
тАО04-26-2011 12:46 AM
тАО04-26-2011 12:46 AM
Re: LUN details with mount point
There is an IBM multipathing software named IBMSdd for DS storages for hp-ux, which is free & available on IBM site.
You can install that on hp-ux & run the below commands:
querysn -l
showvpath -l
With this commands, you can get the LUN ID wrt device file. Further you can trace that device file in lvmtab.
Even, you can use the vpath device files like pdsf in 11.31 & can define load balancing.
Thanks,
Vivek
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
тАО04-26-2011 07:41 PM
тАО04-26-2011 07:41 PM
Re: LUN details with mount point
http://www-01.ibm.com/support/docview.wss?uid=ssg1S4000053
My system configuration is hpux 11.23 and connected with IBM Storage DS4800
Regards,
Sumant M Kumar
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
тАО04-26-2011 08:19 PM
тАО04-26-2011 08:19 PM
Re: LUN details with mount point
ftp://ftp.software.ibm.com/storage/subsystem/hp-ux/1.8.0.2/readme_v1802.txt
http://www-01.ibm.com/support/docview.wss?uid=ssg1S4000053#ds4k
As, you have ds4800 & the above drivers are suitable for almost all DS series.
Try it & let me know,
Thanks,
Vivek