- Community Home
- >
- Storage
- >
- Entry Storage Systems
- >
- Disk Enclosures
- >
- MA6000 HP-UX LUN-id > 7 not seen
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-08-2003 10:54 PM
тАО04-08-2003 10:54 PM
MA6000 HP-UX LUN-id > 7 not seen
I've got a MA6000 connected to a HP-UX server (HPUX 11.0). Two new LUN's were defined on the MA6000 array, but a LUN with a LUN-id > 7 was not seen by the HPUX server (ioscan and insf-e discovered only one of the 2 new LUN's that had a LUN-id < 7).
After changing the LUN-id of the other LUN to an id below 7, it was discovered as well by an ioscan.
Are there some patches required or a kernel parameter that must be increased to detect LUN's larger than 7?
regards,
Kurt
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
тАО04-09-2003 12:49 AM
тАО04-09-2003 12:49 AM
Re: MA6000 HP-UX LUN-id > 7 not seen
HPUX uses a what they call a VBUS (virtual BUS). There is no LUN number defined above 7. They only have a range of 0-7. There is a document I've seen in the forums on this and I have it bookmarked, but I'm not in the office now. If someone doesn't list, I have a look tomorrow morning my time.
There is no patch nor kernel parameter. I know using an EMC array you have to define the VBUS number. Perhaps it is the same with this piece of equipment.
HTH
Regards
Michael
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
тАО04-09-2003 01:04 AM
тАО04-09-2003 01:04 AM
Re: MA6000 HP-UX LUN-id > 7 not seen
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
тАО04-09-2003 01:32 AM
тАО04-09-2003 01:32 AM
Re: MA6000 HP-UX LUN-id > 7 not seen
Please attach 'ioscan -fn' and how MA is connected to the host to your next reply
Eugeny
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
тАО04-09-2003 03:36 AM
тАО04-09-2003 03:36 AM
Re: MA6000 HP-UX LUN-id > 7 not seen
I know that a LUN > 7 on the MA6000 will be translated in a hardware path c
Attached is the output of an 'ioscan -fnk' and 'ioscan -fnkC disk'. The Secure Path was still version 3.0 when the ioscan was taken. After the upgrade to Secure Path version 3.0A SP the device files to the disks changed to c14t0d
regards,
Kurt
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
тАО04-09-2003 04:01 AM
тАО04-09-2003 04:01 AM
Re: MA6000 HP-UX LUN-id > 7 not seen
Eugeny
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
тАО04-09-2003 05:06 AM
тАО04-09-2003 05:06 AM
Re: MA6000 HP-UX LUN-id > 7 not seen
it is a Compaq switch and not a Brocade switch. I'm not managing the switch and a collegue of my didn't know what you mentioned with the showsupport command.
But he said that the problem has to be on the HPUX server, as the LUN was seen after changing the LUN-id on the MA6000.
Can you be pore specific about the information you want?
regards,
Kurt
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
тАО04-09-2003 05:42 AM
тАО04-09-2003 05:42 AM
Re: MA6000 HP-UX LUN-id > 7 not seen
I see that MA works in public loop. Is it correct? Why do not you set it up to work in fabric (using MA CLI 'set this
port_1_t = fabric' and 'set this
port_2_t = fabric') and configure it to use SCSI-3 protocol instead of SCSI-2?
Make sure you have latest ACS installed
Eugeny
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
тАО04-09-2003 06:27 AM
тАО04-09-2003 06:27 AM
Re: MA6000 HP-UX LUN-id > 7 not seen
Changing to fabric would not solve the situation, it is not tied to the problem Kurt is trying to solve, I think. The question is how to tell HP-UX to use volume set addressing. I am not a HP-UX expert, but You should definitely use SCSI2 mode and CCL (command console lun) presented. Command console lun should be visible to the host as LUN0, so if You create lun0 as a volume, You basically mask it. CCL is used besides other things also for querying LUNs higher than 7. So, I would recommend to check the array is in SCSI2 mode and CCL presented.
Next to Your LUNs 2-6, You should see also 1.16.255.x.y.0 where xy is AL_PA of Your hsg60 ctrl translated and 1.16.zz.0.0.0 CCL device... Once You see this, You have succeeded in switching the VBUS mode on... hmmmm, Vladimir
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
тАО04-09-2003 10:16 AM
тАО04-09-2003 10:16 AM
Re: MA6000 HP-UX LUN-id > 7 not seen
you really know what're you talking about :o)
Kurt,
I've checked with our hpux expert and she said that it's storage device responsibility to tell hpux driver if it's fcparray or fcpdev.
So the items to check are:
1. check for HSG60 to give correct fcparray-capable responce to hpux driver. It usually done by assigning correct OS behavior to host (WWN assigned to 'hpux'). I know HSG80 is capable of it;
2. hpux should have LUN 0, at least virtual one, to query. So please create LUN 0.
Good luck!
Eugeny