- Community Home
- >
- Storage
- >
- Entry Storage Systems
- >
- Disk Enclosures
- >
- hds 9900 connected to rp7400 ioscan multiple lun...
Disk Enclosures
1752772
Members
5623
Online
108789
Solutions
Forums
Categories
Company
Local Language
юдл
back
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
юдл
back
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
Blogs
Information
Community
Resources
Community Language
Language
Forums
Blogs
Go to solution
Topic Options
- 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
тАО02-14-2002 12:29 PM
тАО02-14-2002 12:29 PM
The rp7400 ioscan -fn of a hds 9900 is displaying entries /dev/dsk/cxt(0 to 15)d0 (lun 0) even though lun 0 has not been allocated any size or presented to the FC port and has a description of "HITACHI DISK-SUBSYSTEM". The HDS HP extension to allow 120 luns is installed. This is duplicated for every SCSI target 0 to 15. The ioscan for open-E devices is fine. (See example below). Is there any way to stop the rp7400 seeing these lun0 entries when they have not been created on the hds?
disk 6 0/10/0/0.1.64.0.0.2.0 sdisk CLAIMED DEVICE HITACHI DISK-SUBSYSTEM
/dev/dsk/c4t2d0 /dev/rdsk/c4t2d0
disk 37 0/10/0/0.1.64.0.0.2.4 sdisk CLAIMED DEVICE HITACHI OPEN-E
disk 6 0/10/0/0.1.64.0.0.2.0 sdisk CLAIMED DEVICE HITACHI DISK-SUBSYSTEM
/dev/dsk/c4t2d0 /dev/rdsk/c4t2d0
disk 37 0/10/0/0.1.64.0.0.2.4 sdisk CLAIMED DEVICE HITACHI OPEN-E
Solved! Go to Solution.
3 REPLIES 3
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
тАО02-15-2002 03:44 AM
тАО02-15-2002 03:44 AM
Solution
This is the way that HP-UX sees the HDS.
The fiber channel is emulated as F/W SCSI on the HP9000 host and the LUN number (0-119) will be translated by the host to SCSI target IDs and LUN numbers.
Bear in mind that there are basic LUN assignment rules.
1. Each SCSI target must have a LUN 0 or none of the LUNs on that target will be visible to the host.
2. Don't break a string of LUNs or the subsequent LUNs will not be visible to the host.
(Ex: if LUN 30,31,32, and 36 are assigned, the host will only see LUNs 30,31,32 but this vulnerability can be overcome by creating a pseudo device. I'll explain that below)
The array fools the host into thinking LUN 0 and the string are available by creating a psuedo device for each SCSI target ID on a given FC card, that is, a fake device will show up for SCSI IDs 0,1,2,3,4, etc even if a LUN is not assigned to that target.
This allows you to assign LUNs without having to assign to LUN 0 and also allows you to skip a LUN in the string.
That's why you see a psuedo device file on each
SCSI target ID when you issue ioscan.
Hope this helps,
Insu,
The fiber channel is emulated as F/W SCSI on the HP9000 host and the LUN number (0-119) will be translated by the host to SCSI target IDs and LUN numbers.
Bear in mind that there are basic LUN assignment rules.
1. Each SCSI target must have a LUN 0 or none of the LUNs on that target will be visible to the host.
2. Don't break a string of LUNs or the subsequent LUNs will not be visible to the host.
(Ex: if LUN 30,31,32, and 36 are assigned, the host will only see LUNs 30,31,32 but this vulnerability can be overcome by creating a pseudo device. I'll explain that below)
The array fools the host into thinking LUN 0 and the string are available by creating a psuedo device for each SCSI target ID on a given FC card, that is, a fake device will show up for SCSI IDs 0,1,2,3,4, etc even if a LUN is not assigned to that target.
This allows you to assign LUNs without having to assign to LUN 0 and also allows you to skip a LUN in the string.
That's why you see a psuedo device file on each
SCSI target ID when you issue ioscan.
Hope this helps,
Insu,
Never say "no" first.
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
тАО02-22-2002 01:11 PM
тАО02-22-2002 01:11 PM
Re: hds 9900 connected to rp7400 ioscan multiple lun0
You can ignore the DISK-SUBSYSTEM lines in the ioscan. They really mean nothing.
The non-consecutive LUN problem has been fixed; you need only download the patch (which I forget the number of...)
Good luck
The non-consecutive LUN problem has been fixed; you need only download the patch (which I forget the number of...)
Good luck
No matter where you go, there you are.
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
тАО03-07-2002 03:50 AM
тАО03-07-2002 03:50 AM
Re: hds 9900 connected to rp7400 ioscan multiple lun0
Thanks for the help.
The other gotcha with the LUN0s which I have discovered is that EMS doesn't like them! The file /var/stm/data/tools/monitor/disabled_instances needs the hardware path of each LUN0 adding to it to stop EMS reporting errors on them.
The other gotcha with the LUN0s which I have discovered is that EMS doesn't like them! The file /var/stm/data/tools/monitor/disabled_instances needs the hardware path of each LUN0 adding to it to stop EMS reporting errors on them.
The opinions expressed above are the personal opinions of the authors, not of Hewlett Packard Enterprise. By using this site, you accept the Terms of Use and Rules of Participation.
News and Events
Support
© Copyright 2024 Hewlett Packard Enterprise Development LP