GreenLake Administration
- Community Home
- >
- Servers and Operating Systems
- >
- Operating Systems
- >
- Operating System - HP-UX
- >
- Re: Pre HP-UX 11i v3 device special file creation
Operating System - HP-UX
1847860
Members
4501
Online
104021
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
Forums
Discussions
Discussions
Forums
Discussions
back
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
Blogs
Information
Community
Resources
Community Language
Language
Forums
Blogs
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
09-09-2007 12:05 AM
09-09-2007 12:05 AM
Pre HP-UX 11i v3 device special file creation
Hi Experts,
would you please advise on the following: In pre HP-UX 11i v3 a device special file has this syntax: /dev/(r)dsk/cCtTdD, with C: controller instance number, T: target id and D: LUN number.
With FC being introduced, T is not simply the target number anymore, it is subject to change in case of soft-addressing but also if it comes to explicit AL-PA setting.
Could someone please let me know how C is built? I.e. is there any algorithm that would allow me to calculate the "C" of a device that is going to be insf-ed?
Many thanks
kind regards
would you please advise on the following: In pre HP-UX 11i v3 a device special file has this syntax: /dev/(r)dsk/cCtTdD, with C: controller instance number, T: target id and D: LUN number.
With FC being introduced, T is not simply the target number anymore, it is subject to change in case of soft-addressing but also if it comes to explicit AL-PA setting.
Could someone please let me know how C is built? I.e. is there any algorithm that would allow me to calculate the "C" of a device that is going to be insf-ed?
Many thanks
kind regards
2 REPLIES 2
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
09-09-2007 11:49 PM
09-09-2007 11:49 PM
Re: Pre HP-UX 11i v3 device special file creation
The C value is given by the value of the instance in the ext_bus internal table:
ioscan -kfnC ext_bus
# ioscan -kfnC ext_bus
Class I H/W Path Driver S/W State H/W Type Description
==========================================================================
ext_bus 0 2/0/1/1/0/4/0 c720 CLAIMED INTERFACE SCSI C896 Ultra2 Wide LVD
ext_bus 1 2/0/1/1/0/4/1 c720 CLAIMED INTERFACE SCSI C896 Ultra2 Wide Single-Ended
ext_bus 8 2/0/4/1/0.127.140.19.0 fcd_vbus CLAIMED INTERFACE FCP Array Interface
ext_bus 9 2/0/4/1/0.127.140.255.1 fcd_vbus CLAIMED INTERFACE FCP Device Interface
ext_bus 10 2/0/6/1/0.123.140.19.0 fcd_vbus CLAIMED INTERFACE FCP Array Interface
ext_bus 11 2/0/6/1/0.123.140.255.1 fcd_vbus CLAIMED INTERFACE FCP Device Interface
ext_bus 2 2/0/8/1/0/4/0 c720 CLAIMED INTERFACE SCSI C896 Fast Wide LVD
ext_bus 3 2/0/8/1/0/4/1 c720 CLAIMED INTERFACE SCSI C896 Fast Wide LVD
In the output above, the CARD number of the disk device files (/dev/dsk/c8t* and /dev/dsk/c10t*) matches the instance number of the "FCP Array Interface" (8 and 10).
Pay attention that you MAY change those instance number by means of well-known ioinit procedure.
Each instance of an "FCP Array Interface" is able to handle a given number of LUNs (128 but I'm guessing).
When more than 128 LUNs must be handled, the FC driver creates a new instance (a new FCP Array Interface)
ioscan -kfnC ext_bus
# ioscan -kfnC ext_bus
Class I H/W Path Driver S/W State H/W Type Description
==========================================================================
ext_bus 0 2/0/1/1/0/4/0 c720 CLAIMED INTERFACE SCSI C896 Ultra2 Wide LVD
ext_bus 1 2/0/1/1/0/4/1 c720 CLAIMED INTERFACE SCSI C896 Ultra2 Wide Single-Ended
ext_bus 8 2/0/4/1/0.127.140.19.0 fcd_vbus CLAIMED INTERFACE FCP Array Interface
ext_bus 9 2/0/4/1/0.127.140.255.1 fcd_vbus CLAIMED INTERFACE FCP Device Interface
ext_bus 10 2/0/6/1/0.123.140.19.0 fcd_vbus CLAIMED INTERFACE FCP Array Interface
ext_bus 11 2/0/6/1/0.123.140.255.1 fcd_vbus CLAIMED INTERFACE FCP Device Interface
ext_bus 2 2/0/8/1/0/4/0 c720 CLAIMED INTERFACE SCSI C896 Fast Wide LVD
ext_bus 3 2/0/8/1/0/4/1 c720 CLAIMED INTERFACE SCSI C896 Fast Wide LVD
In the output above, the CARD number of the disk device files (/dev/dsk/c8t* and /dev/dsk/c10t*) matches the instance number of the "FCP Array Interface" (8 and 10).
Pay attention that you MAY change those instance number by means of well-known ioinit procedure.
Each instance of an "FCP Array Interface" is able to handle a given number of LUNs (128 but I'm guessing).
When more than 128 LUNs must be handled, the FC driver creates a new instance (a new FCP Array Interface)
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
09-10-2007 07:01 AM
09-10-2007 07:01 AM
Re: Pre HP-UX 11i v3 device special file creation
Thank you so much Oscar (o mejor: muchas gracias). Saludos hontoy
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.
Company
Events and news
Customer resources
© Copyright 2026 Hewlett Packard Enterprise Development LP