<?xml version="1.0" encoding="UTF-8"?>
<rss xmlns:content="http://purl.org/rss/1.0/modules/content/" xmlns:dc="http://purl.org/dc/elements/1.1/" xmlns:rdf="http://www.w3.org/1999/02/22-rdf-syntax-ns#" xmlns:taxo="http://purl.org/rss/1.0/modules/taxonomy/" version="2.0">
  <channel>
    <title>topic Pre HP-UX 11i v3 device special file creation in Operating System - HP-UX</title>
    <link>https://community.hpe.com/t5/operating-system-hp-ux/pre-hp-ux-11i-v3-device-special-file-creation/m-p/4067587#M306965</link>
    <description>Hi Experts,&lt;BR /&gt;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.&lt;BR /&gt;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.&lt;BR /&gt;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?&lt;BR /&gt;Many thanks&lt;BR /&gt;kind regards</description>
    <pubDate>Sun, 09 Sep 2007 07:05:43 GMT</pubDate>
    <dc:creator>hontoy</dc:creator>
    <dc:date>2007-09-09T07:05:43Z</dc:date>
    <item>
      <title>Pre HP-UX 11i v3 device special file creation</title>
      <link>https://community.hpe.com/t5/operating-system-hp-ux/pre-hp-ux-11i-v3-device-special-file-creation/m-p/4067587#M306965</link>
      <description>Hi Experts,&lt;BR /&gt;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.&lt;BR /&gt;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.&lt;BR /&gt;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?&lt;BR /&gt;Many thanks&lt;BR /&gt;kind regards</description>
      <pubDate>Sun, 09 Sep 2007 07:05:43 GMT</pubDate>
      <guid>https://community.hpe.com/t5/operating-system-hp-ux/pre-hp-ux-11i-v3-device-special-file-creation/m-p/4067587#M306965</guid>
      <dc:creator>hontoy</dc:creator>
      <dc:date>2007-09-09T07:05:43Z</dc:date>
    </item>
    <item>
      <title>Re: Pre HP-UX 11i v3 device special file creation</title>
      <link>https://community.hpe.com/t5/operating-system-hp-ux/pre-hp-ux-11i-v3-device-special-file-creation/m-p/4067588#M306966</link>
      <description>&lt;!--!*#--&gt;The C value is given by the value of the instance in the ext_bus internal table:&lt;BR /&gt;&lt;BR /&gt;ioscan -kfnC ext_bus&lt;BR /&gt;&lt;BR /&gt;# ioscan -kfnC ext_bus&lt;BR /&gt;Class     I  H/W Path       Driver   S/W State   H/W Type     Description&lt;BR /&gt;==========================================================================&lt;BR /&gt;ext_bus   0  2/0/1/1/0/4/0  c720     CLAIMED     INTERFACE    SCSI C896 Ultra2 Wide LVD&lt;BR /&gt;ext_bus   1  2/0/1/1/0/4/1  c720     CLAIMED     INTERFACE    SCSI C896 Ultra2 Wide Single-Ended&lt;BR /&gt;ext_bus   8  2/0/4/1/0.127.140.19.0   fcd_vbus CLAIMED     INTERFACE    FCP Array Interface&lt;BR /&gt;ext_bus   9  2/0/4/1/0.127.140.255.1  fcd_vbus CLAIMED     INTERFACE    FCP Device Interface&lt;BR /&gt;ext_bus  10  2/0/6/1/0.123.140.19.0   fcd_vbus CLAIMED     INTERFACE    FCP Array Interface&lt;BR /&gt;ext_bus  11  2/0/6/1/0.123.140.255.1  fcd_vbus CLAIMED     INTERFACE    FCP Device Interface&lt;BR /&gt;ext_bus   2  2/0/8/1/0/4/0  c720     CLAIMED     INTERFACE    SCSI C896 Fast Wide LVD&lt;BR /&gt;ext_bus   3  2/0/8/1/0/4/1  c720     CLAIMED     INTERFACE    SCSI C896 Fast Wide LVD&lt;BR /&gt;&lt;BR /&gt;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).&lt;BR /&gt;&lt;BR /&gt;Pay attention that you MAY change those instance number by means of well-known ioinit procedure.&lt;BR /&gt;&lt;BR /&gt;Each instance of an "FCP Array Interface" is able to handle a given number of LUNs (128 but I'm guessing).&lt;BR /&gt;&lt;BR /&gt;When more than 128 LUNs must be handled, the FC driver creates a new instance (a new FCP Array Interface)&lt;BR /&gt;</description>
      <pubDate>Mon, 10 Sep 2007 06:49:23 GMT</pubDate>
      <guid>https://community.hpe.com/t5/operating-system-hp-ux/pre-hp-ux-11i-v3-device-special-file-creation/m-p/4067588#M306966</guid>
      <dc:creator>Jdamian</dc:creator>
      <dc:date>2007-09-10T06:49:23Z</dc:date>
    </item>
    <item>
      <title>Re: Pre HP-UX 11i v3 device special file creation</title>
      <link>https://community.hpe.com/t5/operating-system-hp-ux/pre-hp-ux-11i-v3-device-special-file-creation/m-p/4067589#M306967</link>
      <description>Thank you so much Oscar (o mejor: muchas gracias). Saludos  hontoy</description>
      <pubDate>Mon, 10 Sep 2007 14:01:44 GMT</pubDate>
      <guid>https://community.hpe.com/t5/operating-system-hp-ux/pre-hp-ux-11i-v3-device-special-file-creation/m-p/4067589#M306967</guid>
      <dc:creator>hontoy</dc:creator>
      <dc:date>2007-09-10T14:01:44Z</dc:date>
    </item>
  </channel>
</rss>

