- Community Home
- >
- Servers and Operating Systems
- >
- Legacy
- >
- Operating System - Tru64 Unix
- >
- Re: Blast from the past: 4.0F device file naming r...
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
Forums
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
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
тАО01-10-2006 12:16 AM
тАО01-10-2006 12:16 AM
e.g. rz+(some-letter)+....
which relates to Bus Target and LUN. I am googling around, but it isn't popping up quickly for me.
Solved! Go to Solution.
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
тАО01-10-2006 12:25 AM
тАО01-10-2006 12:25 AM
Re: Blast from the past: 4.0F device file naming rules
For example:
disk with SCSI ID 5 bus 0: rz5
disk with SCSI ID 5 bus 1: rz13
disk with SCSI ID 1 bus 4: rz33
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
тАО01-10-2006 12:36 AM
тАО01-10-2006 12:36 AM
Re: Blast from the past: 4.0F device file naming rules
rze128c would be: ???
What is the "e" representing? LUN?
So is it?:
rze128c: BUS 16, Target 0, LUN4, ?
and
rzg128c: BUS 16, Target 0, LUN5, ?
Also, (bonus points) how can you determine WWID for a disk with 4.0F from the UNIX level?
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
тАО01-10-2006 01:00 AM
тАО01-10-2006 01:00 AM
Re: Blast from the past: 4.0F device file naming rules
For example on a an HSZ40 you would create a device DKA400, DKA401
The bus number came from teh actuall scsi bus, and thus would chance when you added/removed an interface, or used a differnt bus.
The 400 would be Unit 4, lun 0
That 401 woudl be Unit 4, lun 1
hth,
Hein.
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
тАО01-10-2006 01:13 AM
тАО01-10-2006 01:13 AM
SolutionAh, now I see this is pretty much the same question as:
http://forums1.itrc.hp.com/service/forums/questionanswer.do?threadId=969030
Similar question was dicussed a year before that in:
http://forums1.itrc.hp.com/service/forums/questionanswer.do?threadId=476248
[going for the bonus points :-) ]
Would the wwid not be in one of the scsi mode pages tha t you can see with SCU, notably the "Device identification page."?
(http://home.comcast.net/~SCSIguy/SCSI_FAQ/RMiller_Tools/scu/scu.html)
Or maybe use the console software? P00>>> wwidmgr -show ...
Hein.
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
тАО01-10-2006 01:18 AM
тАО01-10-2006 01:18 AM
Re: Blast from the past: 4.0F device file naming rules
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
тАО01-10-2006 02:00 AM
тАО01-10-2006 02:00 AM
Re: Blast from the past: 4.0F device file naming rules
If you have multilun devices then:
LUN 0 : no additional leter
LUN 1 : lettr a
LUN 2 : letter b
...
For example like Hein said.
Another example:
rza33 would be BUS 4 ID 1 LUN 1
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
тАО01-10-2006 03:26 AM
тАО01-10-2006 03:26 AM
Re: Blast from the past: 4.0F device file naming rules
scu> show inquiry pages
Gives me the WWID. thanks.
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
тАО01-10-2006 03:33 AM
тАО01-10-2006 03:33 AM
Re: Blast from the past: 4.0F device file naming rules
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
тАО01-11-2006 12:02 AM
тАО01-11-2006 12:02 AM
Re: Blast from the past: 4.0F device file naming rules
LUN 0 = rzaNN or rzNN
LUN 1 = rzbNN
LUN 2 = rzcNN
LUN 3 = rzdNN
LUN 4 = rzeNN
LUN 5 = rzfNN
LUN 6 = rzgNN
LUN 7 = rzhNN
where NN = (8 * SCSI Bus number) + SCSI target ID.
V4 was limited to a max target ID of 7 and a max LUN of 7.
Martin
A quick resolution to technical issues for your HPE products is just a click away HPE Support Center
See Self Help Post for more details