Simpler Navigation for Servers and Operating Systems - Please Update Your Bookmarks
Completed: a much simpler Servers and Operating Systems section of the Community. We combined many of the older boards, so you won't have to click through so many levels to get at the information you need. Check the consolidated boards here as many sub-forums are now single boards.
If you have bookmarked forums or discussion boards in Servers and Operating Systems, we suggest you check and update them as needed.
Operating System - Tru64 Unix
cancel
Showing results for 
Search instead for 
Did you mean: 

Blast from the past: 4.0F device file naming rules

SOLVED
Go to solution
Adam Garsha
Valued Contributor

Blast from the past: 4.0F device file naming rules

Does anyone remember what the naming convention for disks was back in good 'ol 4.0F?

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.
9 REPLIES
Vladimir Fabecic
Honored Contributor

Re: Blast from the past: 4.0F device file naming rules

rz ((SCSI ID) + (Bus number X 8))
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
In vino veritas, in VMS cluster
Adam Garsha
Valued Contributor

Re: Blast from the past: 4.0F device file naming rules

Thanks, so:

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?

Hein van den Heuvel
Honored Contributor

Re: Blast from the past: 4.0F device file naming rules

The 'some-letter' were the luns.

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.
Hein van den Heuvel
Honored Contributor
Solution

Re: Blast from the past: 4.0F device file naming rules


Ah, 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.
Adam Garsha
Valued Contributor

Re: Blast from the past: 4.0F device file naming rules

I disagree about the relevance of the first to links, they weren't on point. The last link may help, if it does, I'll pay-up.
Vladimir Fabecic
Honored Contributor

Re: Blast from the past: 4.0F device file naming rules

Addon:
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
In vino veritas, in VMS cluster
Adam Garsha
Valued Contributor

Re: Blast from the past: 4.0F device file naming rules

scu> set nexus bus 5 target 1 lun 1
scu> show inquiry pages

Gives me the WWID. thanks.
Adam Garsha
Valued Contributor

Re: Blast from the past: 4.0F device file naming rules

Are you sure that LUN0 doesn't equal "a"?
Martin Moore
HPE Pro

Re: Blast from the past: 4.0F device file naming rules

rza33 would be LUN 0, not LUN 1. "a" or no extra letter is LUN 0.

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
I work for HP
A quick resolution to technical issues for your HP Enterprise products is just a click away HP Support Center Knowledge-base
See Self Help Post for more details