<?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 Legacy Vs New device tree in Operating System - HP-UX</title>
    <link>https://community.hpe.com/t5/operating-system-hp-ux/legacy-vs-new-device-tree/m-p/5179638#M459760</link>
    <description>Hi, &lt;BR /&gt;&lt;BR /&gt;Is it expected(possible) that on an 11.31 machine for some disks only the new device nodes(/dev/disk) are created and there will be no nodes in the old device tree(/dev/dsk)? &lt;BR /&gt;&lt;BR /&gt;I have a machine with some external disks connected which have entries only in the new device tree. From the documents available I could not find anything which explains this.&lt;BR /&gt;&lt;BR /&gt;The disks are missing from ioscan -fnC &lt;BR /&gt;ioscan -fNC shows the disks.&lt;BR /&gt;sam shows the disks but the hardware path entry is empty.&lt;BR /&gt;ioscan -m dsf also does not show the mapping of missing devices.&lt;BR /&gt;&lt;BR /&gt;Thanks &lt;BR /&gt;Sri</description>
    <pubDate>Fri, 05 Jun 2009 14:02:08 GMT</pubDate>
    <dc:creator>Srimalik</dc:creator>
    <dc:date>2009-06-05T14:02:08Z</dc:date>
    <item>
      <title>Legacy Vs New device tree</title>
      <link>https://community.hpe.com/t5/operating-system-hp-ux/legacy-vs-new-device-tree/m-p/5179638#M459760</link>
      <description>Hi, &lt;BR /&gt;&lt;BR /&gt;Is it expected(possible) that on an 11.31 machine for some disks only the new device nodes(/dev/disk) are created and there will be no nodes in the old device tree(/dev/dsk)? &lt;BR /&gt;&lt;BR /&gt;I have a machine with some external disks connected which have entries only in the new device tree. From the documents available I could not find anything which explains this.&lt;BR /&gt;&lt;BR /&gt;The disks are missing from ioscan -fnC &lt;BR /&gt;ioscan -fNC shows the disks.&lt;BR /&gt;sam shows the disks but the hardware path entry is empty.&lt;BR /&gt;ioscan -m dsf also does not show the mapping of missing devices.&lt;BR /&gt;&lt;BR /&gt;Thanks &lt;BR /&gt;Sri</description>
      <pubDate>Fri, 05 Jun 2009 14:02:08 GMT</pubDate>
      <guid>https://community.hpe.com/t5/operating-system-hp-ux/legacy-vs-new-device-tree/m-p/5179638#M459760</guid>
      <dc:creator>Srimalik</dc:creator>
      <dc:date>2009-06-05T14:02:08Z</dc:date>
    </item>
    <item>
      <title>Re: Legacy Vs New device tree</title>
      <link>https://community.hpe.com/t5/operating-system-hp-ux/legacy-vs-new-device-tree/m-p/5179639#M459761</link>
      <description>Shalom,&lt;BR /&gt;&lt;BR /&gt;Clearly its possible because you see it.&lt;BR /&gt;&lt;BR /&gt;At this point, I'd run some dd tests to see if everything you think you see is real.&lt;BR /&gt;&lt;BR /&gt;SEP</description>
      <pubDate>Fri, 05 Jun 2009 14:17:27 GMT</pubDate>
      <guid>https://community.hpe.com/t5/operating-system-hp-ux/legacy-vs-new-device-tree/m-p/5179639#M459761</guid>
      <dc:creator>Steven E. Protter</dc:creator>
      <dc:date>2009-06-05T14:17:27Z</dc:date>
    </item>
    <item>
      <title>Re: Legacy Vs New device tree</title>
      <link>https://community.hpe.com/t5/operating-system-hp-ux/legacy-vs-new-device-tree/m-p/5179640#M459762</link>
      <description>It's possible in 2 circumstances that I can think of:&lt;BR /&gt;&lt;BR /&gt;i) Legacy mode addresshas ben turned off. Check with "insf -Lv"&lt;BR /&gt;&lt;BR /&gt;ii) There are a large number of disks (or a large number of disk changes) on the system and the maximum number of controllers for legacy device naming has been exceeded (no more that 255 ext_bus entries). You can check this with "ioscan -fuC ext_bus" - if the instance numbers are anywhere need 255 you probably hit this limit (bear in mind you can't see entries for devices that have been removed)&lt;BR /&gt;&lt;BR /&gt;HTH&lt;BR /&gt;&lt;BR /&gt;Duncan</description>
      <pubDate>Fri, 05 Jun 2009 14:28:17 GMT</pubDate>
      <guid>https://community.hpe.com/t5/operating-system-hp-ux/legacy-vs-new-device-tree/m-p/5179640#M459762</guid>
      <dc:creator>Duncan Edmonstone</dc:creator>
      <dc:date>2009-06-05T14:28:17Z</dc:date>
    </item>
    <item>
      <title>Re: Legacy Vs New device tree</title>
      <link>https://community.hpe.com/t5/operating-system-hp-ux/legacy-vs-new-device-tree/m-p/5179641#M459763</link>
      <description>&lt;BR /&gt;&lt;BR /&gt;&amp;gt;Clearly its possible because you see it.&lt;BR /&gt;I also wrote expected :-)&lt;BR /&gt;&lt;BR /&gt;&amp;gt;At this point, I'd run some dd tests to see if everything you think you see is real.&lt;BR /&gt;&lt;BR /&gt;scsci enquiry works for the device, diskinfo works, dd also works.&lt;BR /&gt;&lt;BR /&gt;&amp;gt;i) Legacy mode addresshas ben turned off. Check with "insf -Lv"&lt;BR /&gt;Its on&lt;BR /&gt;# insf -Lv&lt;BR /&gt;insf: Legacy mode is enabled&lt;BR /&gt;#&lt;BR /&gt;&lt;BR /&gt;This machine has 12 disks 8 of which show up fine in the legacy tree just 4 of them are missing.&lt;BR /&gt;&lt;BR /&gt;&amp;gt;ii) There are a large number of disks (or a large number of disk changes) on the system and the maximum number of controllers for legacy device naming has been exceeded (no more that 255 ext_bus entries). You can check this with "ioscan -fuC ext_bus" - if the instance numbers are anywhere need 255 you probably hit this limit (bear in mind you can't see entries for devices that have been removed)&lt;BR /&gt;&lt;BR /&gt;This is not the cases here, i am not hitting this limit. &lt;BR /&gt;&lt;BR /&gt;I tried recreating these entries with insf but not success. :-(, reboots also have no effect.</description>
      <pubDate>Fri, 05 Jun 2009 17:28:49 GMT</pubDate>
      <guid>https://community.hpe.com/t5/operating-system-hp-ux/legacy-vs-new-device-tree/m-p/5179641#M459763</guid>
      <dc:creator>Srimalik</dc:creator>
      <dc:date>2009-06-05T17:28:49Z</dc:date>
    </item>
    <item>
      <title>Re: Legacy Vs New device tree</title>
      <link>https://community.hpe.com/t5/operating-system-hp-ux/legacy-vs-new-device-tree/m-p/5179642#M459764</link>
      <description>So the next question is - what sort of disks are you having problems with? Sometimes having the wrong settings on disk arrays can cause this sort of thing...&lt;BR /&gt;&lt;BR /&gt;HTH&lt;BR /&gt;&lt;BR /&gt;Duncan</description>
      <pubDate>Fri, 05 Jun 2009 18:39:10 GMT</pubDate>
      <guid>https://community.hpe.com/t5/operating-system-hp-ux/legacy-vs-new-device-tree/m-p/5179642#M459764</guid>
      <dc:creator>Duncan Edmonstone</dc:creator>
      <dc:date>2009-06-05T18:39:10Z</dc:date>
    </item>
    <item>
      <title>Re: Legacy Vs New device tree</title>
      <link>https://community.hpe.com/t5/operating-system-hp-ux/legacy-vs-new-device-tree/m-p/5179643#M459765</link>
      <description>This was due to the LUN addressing mode which was assigning a LUN ID greater than 7 and those LUNS were not visible.</description>
      <pubDate>Sat, 09 Oct 2010 04:44:04 GMT</pubDate>
      <guid>https://community.hpe.com/t5/operating-system-hp-ux/legacy-vs-new-device-tree/m-p/5179643#M459765</guid>
      <dc:creator>Srimalik</dc:creator>
      <dc:date>2010-10-09T04:44:04Z</dc:date>
    </item>
  </channel>
</rss>

