<?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 hardware path information required in Operating System - HP-UX</title>
    <link>https://community.hpe.com/t5/operating-system-hp-ux/hardware-path-information-required/m-p/4207657#M325693</link>
    <description>i want to know the meanings of device path&lt;BR /&gt;&lt;BR /&gt;like when we do ioscan -fn disk&lt;BR /&gt;we get any disk or attached device name&lt;BR /&gt;like /dev/rdsk/c3t0d1&lt;BR /&gt;&lt;BR /&gt;what does the c3t0d1 stands for??&lt;BR /&gt;wht i remember is c=controller and rest.....??&lt;BR /&gt;&lt;BR /&gt;any one help...</description>
    <pubDate>Fri, 30 May 2008 08:34:22 GMT</pubDate>
    <dc:creator>Asim_5</dc:creator>
    <dc:date>2008-05-30T08:34:22Z</dc:date>
    <item>
      <title>hardware path information required</title>
      <link>https://community.hpe.com/t5/operating-system-hp-ux/hardware-path-information-required/m-p/4207657#M325693</link>
      <description>i want to know the meanings of device path&lt;BR /&gt;&lt;BR /&gt;like when we do ioscan -fn disk&lt;BR /&gt;we get any disk or attached device name&lt;BR /&gt;like /dev/rdsk/c3t0d1&lt;BR /&gt;&lt;BR /&gt;what does the c3t0d1 stands for??&lt;BR /&gt;wht i remember is c=controller and rest.....??&lt;BR /&gt;&lt;BR /&gt;any one help...</description>
      <pubDate>Fri, 30 May 2008 08:34:22 GMT</pubDate>
      <guid>https://community.hpe.com/t5/operating-system-hp-ux/hardware-path-information-required/m-p/4207657#M325693</guid>
      <dc:creator>Asim_5</dc:creator>
      <dc:date>2008-05-30T08:34:22Z</dc:date>
    </item>
    <item>
      <title>Re: hardware path information required</title>
      <link>https://community.hpe.com/t5/operating-system-hp-ux/hardware-path-information-required/m-p/4207658#M325694</link>
      <description>Hi,&lt;BR /&gt;&lt;BR /&gt;c=controller&lt;BR /&gt;t=target&lt;BR /&gt;d=lun/disk&lt;BR /&gt;&lt;BR /&gt;Robert-Jan</description>
      <pubDate>Fri, 30 May 2008 08:42:48 GMT</pubDate>
      <guid>https://community.hpe.com/t5/operating-system-hp-ux/hardware-path-information-required/m-p/4207658#M325694</guid>
      <dc:creator>Robert-Jan Goossens</dc:creator>
      <dc:date>2008-05-30T08:42:48Z</dc:date>
    </item>
    <item>
      <title>Re: hardware path information required</title>
      <link>https://community.hpe.com/t5/operating-system-hp-ux/hardware-path-information-required/m-p/4207659#M325695</link>
      <description>In old fashion SCSI environments c is the controller instance, t the target (SCSI address) and d the disk or lun.&lt;BR /&gt;&lt;BR /&gt;In SAN environments it is more or less the same, but since lun numbers could be very large, there are some internal rules for building the special device files.&lt;BR /&gt;&lt;BR /&gt;To be sure what the LUN number is, you need to know the hardware path.</description>
      <pubDate>Fri, 30 May 2008 12:29:58 GMT</pubDate>
      <guid>https://community.hpe.com/t5/operating-system-hp-ux/hardware-path-information-required/m-p/4207659#M325695</guid>
      <dc:creator>Torsten.</dc:creator>
      <dc:date>2008-05-30T12:29:58Z</dc:date>
    </item>
  </channel>
</rss>

