<?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 Re: Device path explain? in Operating System - HP-UX</title>
    <link>https://community.hpe.com/t5/operating-system-hp-ux/device-path-explain/m-p/4705523#M547409</link>
    <description>Hi,&lt;BR /&gt;&lt;BR /&gt;Use the lssf command to display detailed information about a device file.&lt;BR /&gt;&lt;BR /&gt;#lssf /dev/rdsk/c4t0d0&lt;BR /&gt;&lt;BR /&gt;&lt;BR /&gt;Regds \ Vel</description>
    <pubDate>Thu, 28 Oct 2010 03:34:46 GMT</pubDate>
    <dc:creator>P Arumugavel</dc:creator>
    <dc:date>2010-10-28T03:34:46Z</dc:date>
    <item>
      <title>Device path explain?</title>
      <link>https://community.hpe.com/t5/operating-system-hp-ux/device-path-explain/m-p/4705518#M547404</link>
      <description>Dear Team&lt;BR /&gt;&lt;BR /&gt;disk        3  1/0/6/1/0/4/0.8.0.255.0.0.0    sdisk     CLAIMED     DEVICE       HPQ     BF03658242&lt;BR /&gt;&lt;BR /&gt;                              /dev/dsk/c4t0d0   /dev/rdsk/c4t0d0&lt;BR /&gt;&lt;BR /&gt;Explain above device path breifly?</description>
      <pubDate>Wed, 27 Oct 2010 06:33:12 GMT</pubDate>
      <guid>https://community.hpe.com/t5/operating-system-hp-ux/device-path-explain/m-p/4705518#M547404</guid>
      <dc:creator>seenivasan</dc:creator>
      <dc:date>2010-10-27T06:33:12Z</dc:date>
    </item>
    <item>
      <title>Re: Device path explain?</title>
      <link>https://community.hpe.com/t5/operating-system-hp-ux/device-path-explain/m-p/4705519#M547405</link>
      <description>Hi,&lt;BR /&gt;&lt;BR /&gt;proivide model and uname -a out put.&lt;BR /&gt;&lt;BR /&gt;Chandra</description>
      <pubDate>Wed, 27 Oct 2010 06:57:29 GMT</pubDate>
      <guid>https://community.hpe.com/t5/operating-system-hp-ux/device-path-explain/m-p/4705519#M547405</guid>
      <dc:creator>Chandrahasa s</dc:creator>
      <dc:date>2010-10-27T06:57:29Z</dc:date>
    </item>
    <item>
      <title>Re: Device path explain?</title>
      <link>https://community.hpe.com/t5/operating-system-hp-ux/device-path-explain/m-p/4705520#M547406</link>
      <description>Without&lt;BR /&gt;&lt;BR /&gt;# model&lt;BR /&gt;&lt;BR /&gt;and&lt;BR /&gt;&lt;BR /&gt;# ioscan -fn&lt;BR /&gt;&lt;BR /&gt;I can only tell it is a fiber channel loop connected disk.</description>
      <pubDate>Wed, 27 Oct 2010 09:11:11 GMT</pubDate>
      <guid>https://community.hpe.com/t5/operating-system-hp-ux/device-path-explain/m-p/4705520#M547406</guid>
      <dc:creator>Torsten.</dc:creator>
      <dc:date>2010-10-27T09:11:11Z</dc:date>
    </item>
    <item>
      <title>Re: Device path explain?</title>
      <link>https://community.hpe.com/t5/operating-system-hp-ux/device-path-explain/m-p/4705521#M547407</link>
      <description>Hardware path: 1/0/6/1/0/4/0.8.0.255.0.0.0&lt;BR /&gt;&lt;BR /&gt;This looks like a hardware path from a nPar-capable server. So the first four numbers can be used to identify the PCI slot. Run "rad -q" or "olrad -q" (depending on your HP-UX version) to get a list of device path components and the corresponding PCI slot numbers.&lt;BR /&gt;&lt;BR /&gt;1 = cell #1&lt;BR /&gt;0 = system bus adapter&lt;BR /&gt;6 = local bus adapter&lt;BR /&gt;1 = PCI device number&lt;BR /&gt;&lt;BR /&gt;0/4 = unknown; probably indicates this is a multi-port or multi-function PCI card.&lt;BR /&gt;&lt;BR /&gt;0 = card port #0&lt;BR /&gt;&lt;BR /&gt;8.0.255.0.0.0 = a FibreChannel device path; structure is Domain.Area.Port.Bus.Target.LUN.&lt;BR /&gt;&lt;BR /&gt;Domain 8 indicates Private Loop addressing, so this FC HBA is not connected to a SAN fabric, but only to stand-alone FC disk box(es). In Private Loop mode, the Area is always 0.&lt;BR /&gt;&lt;BR /&gt;Port 255 indicates Peripheral Device Addressing mode is used. In this mode, the FC Loop ID = (Bus * 16) + Target, or 0 in your case. &lt;BR /&gt;&lt;BR /&gt;In Peripheral Device Addressing mode, the LUN field is simply the target disk/LUN number.&lt;BR /&gt;&lt;BR /&gt;To summarize:&lt;BR /&gt;This is probably the first disk or LUN in an external FibreChannel-connected storage box, connected to FC port 0 of a FibreChannel HBA located in slot identified by hardware path 1/0/6/1. &lt;BR /&gt;&lt;BR /&gt;If the "rad -q" / "olrad -q" listing identifies the slot by a dash-separated four-digit string (like A-B-C-D), then the first digit is the cabinet number, second is the side (0 = front, 1 = back), third is the I/O box number, and the fourth is the slot number in that I/O box.&lt;BR /&gt;&lt;BR /&gt;MK</description>
      <pubDate>Wed, 27 Oct 2010 15:22:30 GMT</pubDate>
      <guid>https://community.hpe.com/t5/operating-system-hp-ux/device-path-explain/m-p/4705521#M547407</guid>
      <dc:creator>Matti_Kurkela</dc:creator>
      <dc:date>2010-10-27T15:22:30Z</dc:date>
    </item>
    <item>
      <title>Re: Device path explain?</title>
      <link>https://community.hpe.com/t5/operating-system-hp-ux/device-path-explain/m-p/4705522#M547408</link>
      <description>In the beginning (e.g. E-class servers) the rules for device paths were very strict, but later they became a bit more individual.&lt;BR /&gt;&lt;BR /&gt;So without knowing the server model you cannot tell anything for sure.&lt;BR /&gt;&lt;BR /&gt;The path "1/0/6/1" can be found on many different servers, cell-based and non cell-based, perhaps even non-hotswap (so you cannot get details by using "olrad" commands).&lt;BR /&gt;&lt;BR /&gt;&lt;BR /&gt;&lt;BR /&gt;Tell your server model ("model" command)and provide an "ioscan -fn" and we can provide you more details.&lt;BR /&gt;&lt;BR /&gt;&lt;BR /&gt;The part of the path "8.0.255" indicates it is using fiber channel in loop mode, so you probably use a FC connected disk chassis like DS2405 or DS2500 or FC10 or something - this will be shown in the ioscan.&lt;BR /&gt;&lt;BR /&gt;&lt;BR /&gt;&lt;BR /&gt;BTW, did you already read this?&lt;BR /&gt;&lt;BR /&gt;&lt;A href="http://forums11.itrc.hp.com/service/forums/helptips.do?#33" target="_blank"&gt;http://forums11.itrc.hp.com/service/forums/helptips.do?#33&lt;/A&gt;&lt;BR /&gt;&lt;BR /&gt;&lt;BR /&gt;</description>
      <pubDate>Wed, 27 Oct 2010 19:21:04 GMT</pubDate>
      <guid>https://community.hpe.com/t5/operating-system-hp-ux/device-path-explain/m-p/4705522#M547408</guid>
      <dc:creator>Torsten.</dc:creator>
      <dc:date>2010-10-27T19:21:04Z</dc:date>
    </item>
    <item>
      <title>Re: Device path explain?</title>
      <link>https://community.hpe.com/t5/operating-system-hp-ux/device-path-explain/m-p/4705523#M547409</link>
      <description>Hi,&lt;BR /&gt;&lt;BR /&gt;Use the lssf command to display detailed information about a device file.&lt;BR /&gt;&lt;BR /&gt;#lssf /dev/rdsk/c4t0d0&lt;BR /&gt;&lt;BR /&gt;&lt;BR /&gt;Regds \ Vel</description>
      <pubDate>Thu, 28 Oct 2010 03:34:46 GMT</pubDate>
      <guid>https://community.hpe.com/t5/operating-system-hp-ux/device-path-explain/m-p/4705523#M547409</guid>
      <dc:creator>P Arumugavel</dc:creator>
      <dc:date>2010-10-28T03:34:46Z</dc:date>
    </item>
    <item>
      <title>Re: Device path explain?</title>
      <link>https://community.hpe.com/t5/operating-system-hp-ux/device-path-explain/m-p/4705524#M547410</link>
      <description>Hi mr. seenivasan,&lt;BR /&gt;&lt;BR /&gt;/dev/dsk and /dev/rdsk are block and character device files respectively in legacy fashion. c stands for controller, t for target and d for the lun or disk. The controller is 7 bit , the target is 4 bit and the lun is 3 bit.  Hope this is useful!! Cez of what i understood you were interested in device file naming as well including the H/W path.&lt;BR /&gt;&lt;BR /&gt;Regards</description>
      <pubDate>Thu, 11 Nov 2010 21:24:02 GMT</pubDate>
      <guid>https://community.hpe.com/t5/operating-system-hp-ux/device-path-explain/m-p/4705524#M547410</guid>
      <dc:creator>Ismail Azad</dc:creator>
      <dc:date>2010-11-11T21:24:02Z</dc:date>
    </item>
    <item>
      <title>Re: Device path explain?</title>
      <link>https://community.hpe.com/t5/operating-system-hp-ux/device-path-explain/m-p/4705525#M547411</link>
      <description>@seenivasan: Do you still join this (your) thread?</description>
      <pubDate>Thu, 11 Nov 2010 21:34:03 GMT</pubDate>
      <guid>https://community.hpe.com/t5/operating-system-hp-ux/device-path-explain/m-p/4705525#M547411</guid>
      <dc:creator>Torsten.</dc:creator>
      <dc:date>2010-11-11T21:34:03Z</dc:date>
    </item>
  </channel>
</rss>

