- Community Home
- >
- Servers and Operating Systems
- >
- Operating Systems
- >
- Operating System - HP-UX
- >
- HP/UX IBM SVC & 8300 and missing LUN configuration
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
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
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
09-06-2012 08:59 AM
09-06-2012 08:59 AM
HP/UX IBM SVC & 8300 and missing LUN configuration
Hi
Normally we present disk via EMC DMX to our HP hosts and occassionaly via IBM SVC & DS8300.
When using the latter we normally only present a few LUN's ie no more than 8 as they are normally just a few large LUN's but I had occasion to present 16 smaller LUN's the other day.
We configure the SVC using scripts and can see all the LUN's being created correctly. When I look for them using ioscan I only see 8. On the DMX the next 8 would have the next controller number up and so on.
Out put from ioscan;
root@hp90:# ioscan -fnC disk
Class I H/W Path Driver S/W State H/W Type Description
==================================================================
disk 1 0/1/1/0.0.0.0.0 sdisk CLAIMED DEVICE HP DG146ABAB4
/dev/dsk/c6t0d0 /dev/dsk/c6t0d0s3 /dev/rdsk/c6t0d0s2
/dev/dsk/c6t0d0s1 /dev/rdsk/c6t0d0 /dev/rdsk/c6t0d0s3
/dev/dsk/c6t0d0s2 /dev/rdsk/c6t0d0s1
disk 0 0/1/1/0.0.0.1.0 sdisk CLAIMED DEVICE HP DG146ABAB4
/dev/dsk/c6t1d0 /dev/rdsk/c6t1d0
disk 2 0/1/1/0.0.0.2.0 sdisk CLAIMED DEVICE HP DG146ABAB4
/dev/dsk/c6t2d0 /dev/rdsk/c6t2d0
disk 10 0/2/1/0.134.107.255.10.6.0 sdisk CLAIMED DEVICE IBM 2145
/dev/dsk/c9t6d0 /dev/rdsk/c9t6d0
disk 11 0/2/1/0.134.107.255.10.6.1 sdisk CLAIMED DEVICE IBM 2145
/dev/dsk/c9t6d1 /dev/rdsk/c9t6d1
disk 12 0/2/1/0.134.107.255.10.6.2 sdisk CLAIMED DEVICE IBM 2145
/dev/dsk/c9t6d2 /dev/rdsk/c9t6d2
disk 13 0/2/1/0.134.107.255.10.6.3 sdisk CLAIMED DEVICE IBM 2145
/dev/dsk/c9t6d3 /dev/rdsk/c9t6d3
disk 14 0/2/1/0.134.107.255.10.6.4 sdisk CLAIMED DEVICE IBM 2145
/dev/dsk/c9t6d4 /dev/rdsk/c9t6d4
disk 15 0/2/1/0.134.107.255.10.6.5 sdisk CLAIMED DEVICE IBM 2145
/dev/dsk/c9t6d5 /dev/rdsk/c9t6d5
disk 16 0/2/1/0.134.107.255.10.6.6 sdisk CLAIMED DEVICE IBM 2145
/dev/dsk/c9t6d6 /dev/rdsk/c9t6d6
disk 17 0/2/1/0.134.107.255.10.6.7 sdisk CLAIMED DEVICE IBM 2145
/dev/dsk/c9t6d7 /dev/rdsk/c9t6d7
Now if I do a ioscan for LUNPATH I see all 16.
root@hp90:# ioscan -fnkNC lunpath
Class I H/W Path Driver S/W State H/W Type Description
==================================================================
lunpath 7 0/1/1/0.0x5000c50007a947a9.0x0 eslpt CLAIMED LUN_PATH LUN path for disk4
lunpath 6 0/1/1/0.0x5000c50008c4647d.0x0 eslpt CLAIMED LUN_PATH LUN path for disk3
lunpath 8 0/1/1/0.0x5000c50008c63ee9.0x0 eslpt CLAIMED LUN_PATH LUN path for disk5
lunpath 11 0/2/1/0.0x5005076801301a34.0x0 eslpt CLAIMED LUN_PATH LUN path for disk18
lunpath 12 0/2/1/0.0x5005076801301a34.0x1000000000000 eslpt CLAIMED LUN_PATH LUN path for disk19
lunpath 13 0/2/1/0.0x5005076801301a34.0x2000000000000 eslpt CLAIMED LUN_PATH LUN path for disk20
lunpath 14 0/2/1/0.0x5005076801301a34.0x3000000000000 eslpt CLAIMED LUN_PATH LUN path for disk21
lunpath 15 0/2/1/0.0x5005076801301a34.0x4000000000000 eslpt CLAIMED LUN_PATH LUN path for disk22
lunpath 16 0/2/1/0.0x5005076801301a34.0x5000000000000 eslpt CLAIMED LUN_PATH LUN path for disk23
lunpath 19 0/2/1/0.0x5005076801301a34.0x6000000000000 eslpt CLAIMED LUN_PATH LUN path for disk26
lunpath 17 0/2/1/0.0x5005076801301a34.0x7000000000000 eslpt CLAIMED LUN_PATH LUN path for disk24
lunpath 18 0/2/1/0.0x5005076801301a34.0x8000000000000 eslpt CLAIMED LUN_PATH LUN path for disk25
lunpath 20 0/2/1/0.0x5005076801301a34.0x9000000000000 eslpt CLAIMED LUN_PATH LUN path for disk27
lunpath 21 0/2/1/0.0x5005076801301a34.0xa000000000000 eslpt CLAIMED LUN_PATH LUN path for disk28
lunpath 22 0/2/1/0.0x5005076801301a34.0xb000000000000 eslpt CLAIMED LUN_PATH LUN path for disk29
lunpath 23 0/2/1/0.0x5005076801301a34.0xc000000000000 eslpt CLAIMED LUN_PATH LUN path for disk30
lunpath 24 0/2/1/0.0x5005076801301a34.0xd000000000000 eslpt CLAIMED LUN_PATH LUN path for disk31
lunpath 25 0/2/1/0.0x5005076801301a34.0xe000000000000 eslpt CLAIMED LUN_PATH LUN path for disk32
lunpath 26 0/2/1/0.0x5005076801301a34.0xf000000000000 eslpt CLAIMED LUN_PATH LUN path for disk33
lunpath 0 0/2/1/0.0x5006048452a975e8.0x0 eslpt CLAIMED LUN_PATH LUN path for ctl4
lunpath 1 0/2/1/0.0x5006048452a975e9.0x0 eslpt CLAIMED LUN_PATH LUN path for ctl5
lunpath 2 0/2/1/1.0x5006048452a975e6.0x0 eslpt CLAIMED LUN_PATH LUN path for ctl6
lunpath 3 0/2/1/1.0x5006048452a975e7.0x0 eslpt CLAIMED LUN_PATH LUN path for ctl7
Also listing /dev/rdisk shows all the disks however only the first 8 are useable but you can interrogate them using scsimgr
root@hp90:# scsimgr get_attr -D /dev/rdisk/disk29 -a wwid
SCSI ATTRIBUTES FOR LUN : /dev/rdisk/disk29
name = wwid
current = 0x60050768018680d1a000000000004e4d
default =
saved =
I know this is probably a setting on the DS8300 or within the SVC scripting or possibly a license issue but does anyone have any information that can assist me with this?
Here is the config file the script uses, the first 4 fields are dates and names, the 5th is HBA number, 6th is a LUN ID, and 7th is LUN size.
0907,0906,sean_test,hp90,HP166,a,36
0907,0906,sean_test,hp90,HP166,b,36
0907,0906,sean_test,hp90,HP166,c,36
0907,0906,sean_test,hp90,HP166,d,36
0907,0906,sean_test,hp90,HP166,e,36
0907,0906,sean_test,hp90,HP166,f,36
0907,0906,sean_test,hp90,HP166,g,36
0907,0906,sean_test,hp90,HP166,h,36
0907,0906,sean_test,hp90,HP166,i,36
0907,0906,sean_test,hp90,HP166,j,36
0907,0906,sean_test,hp90,HP166,k,36
0907,0906,sean_test,hp90,HP166,l,36
0907,0906,sean_test,hp90,HP166,m,36
0907,0906,sean_test,hp90,HP166,n,36
0907,0906,sean_test,hp90,HP166,o,36
0907,0906,sean_test,hp90,HP166,p,36
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
09-06-2012 10:11 AM
09-06-2012 10:11 AM
Re: HP/UX IBM SVC & 8300 and missing LUN configuration
Hope this helps!
Regards
Torsten.
__________________________________________________
There are only 10 types of people in the world -
those who understand binary, and those who don't.
__________________________________________________
No support by private messages. Please ask the forum!
If you feel this was helpful please click the KUDOS! thumb below!