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.
System Administration
Showing results for 
Search instead for 
Did you mean: 

Interpreting Disk Hardware Path

Telefonica OSI
Occasional Advisor

Interpreting Disk Hardware Path

Reading the HP Fibre Channel Mass Storage Adapters Manual, on the subject related to intrepretint the disk hardware path in private loop topology, when it goes down to the target or lun, it talks about " The value of bits x-x of the 14-bit volume number for an array device using the volume set addressing method".
Anybody knows how to translate that 14-bit volume number from the xpinfo or inqSym utilities output?



P.S. This thread has been moved from Network Attached Storage (NAS) (Enterprise) to HP-UX > sysadmin - HP Forums moderator

Eugeny Brychkov
Honored Contributor

Re: Interpreting Disk Hardware Path

in ioscan output last 3 fields are usually defined as bus, target and LUN. In volume set addressing mode, all these 3 fields used in non-usual way, and indicate Storage Array LUN number.
bus = 7 bits
target = 4 bits
LUN = 3 bits
real disk array's LUN number will be (consisting of 7+4+3=14 bits):
Honored Contributor

Re: Interpreting Disk Hardware Path

you'll see an explaination in this link:,,0x48691012aa92d5118ff10090279cd0f9,00.html

and also:,,0x869de7e60861d511abcd0090277a778c,00.html

for examples of Volume Set Addressing /SCSI protocol limitations on device file construct.

Good Luck
It works for me (tm)