<?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: hardware paths in Operating System - HP-UX</title>
    <link>https://community.hpe.com/t5/operating-system-hp-ux/hardware-paths/m-p/3657438#M241516</link>
    <description>Hi,&lt;BR /&gt;&lt;BR /&gt;no worries about the link u sent earlier..:)&lt;BR /&gt;however, whtu j ust explained kinda makes sense as far knowing wht the c#t#d# stand for..But i am still not clear on how to figure out what kind of device wehave by looking at such info? And also in class today wht we were doing was multiplying 'd' by 1 't' by 8 and c is the 128th place for example in c5t0d0 the lun # is d*1 t*8..and so on???? I have no idea how thts done ! Sorry about the trouble but I am new to all this and I just trying to keep pace with my class. I understand the concept of the whole scsi fibre thing but these calculations ---i need help !!</description>
    <pubDate>Wed, 26 Oct 2005 19:57:00 GMT</pubDate>
    <dc:creator>geeta</dc:creator>
    <dc:date>2005-10-26T19:57:00Z</dc:date>
    <item>
      <title>hardware paths</title>
      <link>https://community.hpe.com/t5/operating-system-hp-ux/hardware-paths/m-p/3657429#M241507</link>
      <description>hi, &lt;BR /&gt;&lt;BR /&gt;I am fairly new to HPUX and fibre channels and raid systems, going through training in fact. If anyone could help with deciphering the h/w path frm an ioscan output..what the different numbers represent in the path and how does it differ for scsi and fibre? I am not sure if i am clear enough, so heres an example frm our training class: 8/0/2/0.8 ...by looking at this we are supposed to know this : c0t0d0 or something like that..really confusing and would appreciate if someone can explain it in simple terms so i understand how this works and how this helps troubleshooting whn we are looking at an ioscan output? thanx :)</description>
      <pubDate>Tue, 25 Oct 2005 18:49:58 GMT</pubDate>
      <guid>https://community.hpe.com/t5/operating-system-hp-ux/hardware-paths/m-p/3657429#M241507</guid>
      <dc:creator>geeta</dc:creator>
      <dc:date>2005-10-25T18:49:58Z</dc:date>
    </item>
    <item>
      <title>Re: hardware paths</title>
      <link>https://community.hpe.com/t5/operating-system-hp-ux/hardware-paths/m-p/3657430#M241508</link>
      <description>Hi Geetha,&lt;BR /&gt;&lt;BR /&gt;  Just look on this URL.,&lt;BR /&gt;&lt;BR /&gt; &lt;A href="http://docs.hp.com/en/32650-90854/ch12s09.html." target="_blank"&gt;http://docs.hp.com/en/32650-90854/ch12s09.html.&lt;/A&gt;&lt;BR /&gt;&lt;BR /&gt; Rgds,Granite</description>
      <pubDate>Tue, 25 Oct 2005 19:19:36 GMT</pubDate>
      <guid>https://community.hpe.com/t5/operating-system-hp-ux/hardware-paths/m-p/3657430#M241508</guid>
      <dc:creator>Granite</dc:creator>
      <dc:date>2005-10-25T19:19:36Z</dc:date>
    </item>
    <item>
      <title>Re: hardware paths</title>
      <link>https://community.hpe.com/t5/operating-system-hp-ux/hardware-paths/m-p/3657431#M241509</link>
      <description>Hi,..&lt;BR /&gt; &lt;BR /&gt;  Is this working..&lt;BR /&gt;&lt;BR /&gt;&lt;A href="http://docs.hp.com/en/B2355-90053/ch01s04.html.." target="_blank"&gt;http://docs.hp.com/en/B2355-90053/ch01s04.html..&lt;/A&gt;</description>
      <pubDate>Tue, 25 Oct 2005 19:32:53 GMT</pubDate>
      <guid>https://community.hpe.com/t5/operating-system-hp-ux/hardware-paths/m-p/3657431#M241509</guid>
      <dc:creator>Granite</dc:creator>
      <dc:date>2005-10-25T19:32:53Z</dc:date>
    </item>
    <item>
      <title>Re: hardware paths</title>
      <link>https://community.hpe.com/t5/operating-system-hp-ux/hardware-paths/m-p/3657432#M241510</link>
      <description>The document is missing</description>
      <pubDate>Tue, 25 Oct 2005 19:46:37 GMT</pubDate>
      <guid>https://community.hpe.com/t5/operating-system-hp-ux/hardware-paths/m-p/3657432#M241510</guid>
      <dc:creator>geeta</dc:creator>
      <dc:date>2005-10-25T19:46:37Z</dc:date>
    </item>
    <item>
      <title>Re: hardware paths</title>
      <link>https://community.hpe.com/t5/operating-system-hp-ux/hardware-paths/m-p/3657433#M241511</link>
      <description>just a typo w/ the url... this should do it.&lt;BR /&gt;&lt;BR /&gt;&lt;A href="http://docs.hp.com/en/32650-90854/ch12s09.html" target="_blank"&gt;http://docs.hp.com/en/32650-90854/ch12s09.html&lt;/A&gt;&lt;BR /&gt;&lt;A href="http://docs.hp.com/en/B2355-90053/ch01s04.html" target="_blank"&gt;http://docs.hp.com/en/B2355-90053/ch01s04.html&lt;/A&gt;&lt;BR /&gt;&lt;BR /&gt;If you have any specific questions re: h/w paths and fabric, post it here.&lt;BR /&gt;&lt;BR /&gt;-denver&lt;BR /&gt;</description>
      <pubDate>Tue, 25 Oct 2005 19:51:07 GMT</pubDate>
      <guid>https://community.hpe.com/t5/operating-system-hp-ux/hardware-paths/m-p/3657433#M241511</guid>
      <dc:creator>Denver Osborn</dc:creator>
      <dc:date>2005-10-25T19:51:07Z</dc:date>
    </item>
    <item>
      <title>Re: hardware paths</title>
      <link>https://community.hpe.com/t5/operating-system-hp-ux/hardware-paths/m-p/3657434#M241512</link>
      <description>very helpful..thanx. the second link infact is perfect! lets see how the training goes tom and i am sure i will be back with more :) thanx again</description>
      <pubDate>Tue, 25 Oct 2005 20:24:06 GMT</pubDate>
      <guid>https://community.hpe.com/t5/operating-system-hp-ux/hardware-paths/m-p/3657434#M241512</guid>
      <dc:creator>geeta</dc:creator>
      <dc:date>2005-10-25T20:24:06Z</dc:date>
    </item>
    <item>
      <title>Re: hardware paths</title>
      <link>https://community.hpe.com/t5/operating-system-hp-ux/hardware-paths/m-p/3657435#M241513</link>
      <description>Hi Geeta, If this is useful, you can assign points to posts and close the thread. &lt;BR /&gt;&lt;BR /&gt;&lt;A href="http://forums1.itrc.hp.com/service/forums/helptips.do?#28" target="_blank"&gt;http://forums1.itrc.hp.com/service/forums/helptips.do?#28&lt;/A&gt;&lt;BR /&gt;&lt;BR /&gt;-Arun</description>
      <pubDate>Wed, 26 Oct 2005 00:15:04 GMT</pubDate>
      <guid>https://community.hpe.com/t5/operating-system-hp-ux/hardware-paths/m-p/3657435#M241513</guid>
      <dc:creator>Arunvijai_4</dc:creator>
      <dc:date>2005-10-26T00:15:04Z</dc:date>
    </item>
    <item>
      <title>Re: hardware paths</title>
      <link>https://community.hpe.com/t5/operating-system-hp-ux/hardware-paths/m-p/3657436#M241514</link>
      <description>And more frm the training class! &lt;BR /&gt;&lt;BR /&gt;How do we figure out a LUN # frm something like this: c0t0d0? And how would it be different for a scsi and fibre channel system?&lt;BR /&gt;&lt;BR /&gt;The h/w path seems to be more clear now, so thanx everybody for helping me out on tht:)</description>
      <pubDate>Wed, 26 Oct 2005 19:26:03 GMT</pubDate>
      <guid>https://community.hpe.com/t5/operating-system-hp-ux/hardware-paths/m-p/3657436#M241514</guid>
      <dc:creator>geeta</dc:creator>
      <dc:date>2005-10-26T19:26:03Z</dc:date>
    </item>
    <item>
      <title>Re: hardware paths</title>
      <link>https://community.hpe.com/t5/operating-system-hp-ux/hardware-paths/m-p/3657437#M241515</link>
      <description>Hi Geetha,&lt;BR /&gt; &lt;BR /&gt; Think a DOT in the link last may took you to an missing URL..my above links..&lt;BR /&gt;&lt;BR /&gt; Back to the track..LUN is just a logical space you are assigning to the server from any disk-array/JBOD/storage. Ideally, server will see a LUN as one single unit(c#t#d#) as like a disk. &lt;BR /&gt;&lt;BR /&gt;root-/&amp;gt;ioscan -funC disk |pg&lt;BR /&gt;Class     I  H/W Path       Driver   S/W State   H/W Type     Description&lt;BR /&gt;==========================================================================&lt;BR /&gt;disk      0  0/0/1/0/0.6.0  sdisk    CLAIMED     DEVICE       HP 36.4GST336706LC&lt;BR /&gt;                           /dev/dsk/c0t6d0   /dev/rdsk/c0t6d0&lt;BR /&gt;disk    273  0/0/3/0/0.4.0  sdisk    CLAIMED     DEVICE       HP 73.4GST373307LC&lt;BR /&gt;                           /dev/dsk/c1t4d0   /dev/rdsk/c1t4d0&lt;BR /&gt;disk      2  0/0/3/0/0.6.0  sdisk    CLAIMED     DEVICE       HP 36.4GST336706LC&lt;BR /&gt;                           /dev/dsk/c1t6d0   /dev/rdsk/c1t6d0&lt;BR /&gt;disk    305  255/255/0/3.3  sdisk    CLAIMED     DEVICE       HSV110 (C)COMPAQ&lt;BR /&gt;                           /dev/dsk/c21t3d3   /dev/rdsk/c21t3d3&lt;BR /&gt;disk    306  255/255/0/3.4  sdisk    CLAIMED     DEVICE       HSV110 (C)COMPAQ&lt;BR /&gt;                           /dev/dsk/c21t3d4   /dev/rdsk/c21t3d4&lt;BR /&gt;disk    385  255/255/0/4.6  sdisk    CLAIMED     DEVICE       HSV110 (C)COMPAQ&lt;BR /&gt;                           /dev/dsk/c21t4d6   /dev/rdsk/c21t4d6&lt;BR /&gt;disk    386  255/255/0/4.7  sdisk    CLAIMED     DEVICE       HSV110 (C)COMPAQ&lt;BR /&gt;                           /dev/dsk/c21t4d7   /dev/rdsk/c21t4d7&lt;BR /&gt;&lt;BR /&gt;  I can map from the "Description" column to find the LUNs from where it has been assigned to server.Here"COMPAQ" is my SAN and "HP ..." are my int.disks.&lt;BR /&gt;&lt;BR /&gt;regds,granite</description>
      <pubDate>Wed, 26 Oct 2005 19:38:55 GMT</pubDate>
      <guid>https://community.hpe.com/t5/operating-system-hp-ux/hardware-paths/m-p/3657437#M241515</guid>
      <dc:creator>Granite</dc:creator>
      <dc:date>2005-10-26T19:38:55Z</dc:date>
    </item>
    <item>
      <title>Re: hardware paths</title>
      <link>https://community.hpe.com/t5/operating-system-hp-ux/hardware-paths/m-p/3657438#M241516</link>
      <description>Hi,&lt;BR /&gt;&lt;BR /&gt;no worries about the link u sent earlier..:)&lt;BR /&gt;however, whtu j ust explained kinda makes sense as far knowing wht the c#t#d# stand for..But i am still not clear on how to figure out what kind of device wehave by looking at such info? And also in class today wht we were doing was multiplying 'd' by 1 't' by 8 and c is the 128th place for example in c5t0d0 the lun # is d*1 t*8..and so on???? I have no idea how thts done ! Sorry about the trouble but I am new to all this and I just trying to keep pace with my class. I understand the concept of the whole scsi fibre thing but these calculations ---i need help !!</description>
      <pubDate>Wed, 26 Oct 2005 19:57:00 GMT</pubDate>
      <guid>https://community.hpe.com/t5/operating-system-hp-ux/hardware-paths/m-p/3657438#M241516</guid>
      <dc:creator>geeta</dc:creator>
      <dc:date>2005-10-26T19:57:00Z</dc:date>
    </item>
    <item>
      <title>Re: hardware paths</title>
      <link>https://community.hpe.com/t5/operating-system-hp-ux/hardware-paths/m-p/3657439#M241517</link>
      <description>And also lets take this example :&lt;BR /&gt;&lt;BR /&gt;8/12.8.0.255.0.1.0   sdisk    CLAIMED    DEVICE   DGC C3400WDR5 &lt;BR /&gt; &lt;BR /&gt;&lt;BR /&gt;The example above is the hardware path of LUN0 of a directly attached Fibre Channel Mass Storage device with Loop ID of 1&lt;BR /&gt;&lt;BR /&gt;&lt;BR /&gt;how do we know its LUN 0 and tht the loop id is 1?</description>
      <pubDate>Wed, 26 Oct 2005 20:04:53 GMT</pubDate>
      <guid>https://community.hpe.com/t5/operating-system-hp-ux/hardware-paths/m-p/3657439#M241517</guid>
      <dc:creator>geeta</dc:creator>
      <dc:date>2005-10-26T20:04:53Z</dc:date>
    </item>
    <item>
      <title>Re: hardware paths</title>
      <link>https://community.hpe.com/t5/operating-system-hp-ux/hardware-paths/m-p/3657440#M241518</link>
      <description>Hi geetha,&lt;BR /&gt;&lt;BR /&gt;  The multiplication wat u said is to find the LUN ID using the hardware path.&lt;BR /&gt;Ex;disk    385  255/255/0/4.6  sdisk    CLAIMED     DEVICE       HSV110 (C)COMPAQ&lt;BR /&gt;                           /dev/dsk/c21t4d6   /dev/rdsk/c21t4d6.&lt;BR /&gt;&lt;BR /&gt; For the above disk,the LUN ID is (128*0)+(4*8)+6 = 38.&lt;BR /&gt;Just take the last serials from your hardware path.&lt;BR /&gt;&lt;BR /&gt;Regds,Granite.&lt;BR /&gt;&lt;BR /&gt;</description>
      <pubDate>Wed, 26 Oct 2005 20:05:10 GMT</pubDate>
      <guid>https://community.hpe.com/t5/operating-system-hp-ux/hardware-paths/m-p/3657440#M241518</guid>
      <dc:creator>Granite</dc:creator>
      <dc:date>2005-10-26T20:05:10Z</dc:date>
    </item>
    <item>
      <title>Re: hardware paths</title>
      <link>https://community.hpe.com/t5/operating-system-hp-ux/hardware-paths/m-p/3657441#M241519</link>
      <description>ok tht helps.then wht about the fibre stuff? why is it LUN 0 in the fibre example i pasted in the last question?&lt;BR /&gt;&lt;BR /&gt;Thanx Granite :)</description>
      <pubDate>Wed, 26 Oct 2005 20:10:53 GMT</pubDate>
      <guid>https://community.hpe.com/t5/operating-system-hp-ux/hardware-paths/m-p/3657441#M241519</guid>
      <dc:creator>geeta</dc:creator>
      <dc:date>2005-10-26T20:10:53Z</dc:date>
    </item>
    <item>
      <title>Re: hardware paths</title>
      <link>https://community.hpe.com/t5/operating-system-hp-ux/hardware-paths/m-p/3657442#M241520</link>
      <description>Hi&lt;BR /&gt;Let check the attachment.&lt;BR /&gt;You will know why :)&lt;BR /&gt;&lt;BR /&gt;Regard,&lt;BR /&gt;Hoang Chi Cong</description>
      <pubDate>Wed, 26 Oct 2005 21:31:13 GMT</pubDate>
      <guid>https://community.hpe.com/t5/operating-system-hp-ux/hardware-paths/m-p/3657442#M241520</guid>
      <dc:creator>Hoang Chi Cong_1</dc:creator>
      <dc:date>2005-10-26T21:31:13Z</dc:date>
    </item>
  </channel>
</rss>

