<?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: Non sequenced LUNs in Disk Enclosures</title>
    <link>https://community.hpe.com/t5/disk-enclosures/non-sequenced-luns/m-p/2520882#M1748</link>
    <description>That issue is one of the assignment rlues applied to EMC disk array itself.&lt;BR /&gt;That is, LUNS should be in the string in order to be visible to the host.&lt;BR /&gt;&lt;BR /&gt;And HP has applied the same rule to XP-array but with a new released microcode, what XP-array does is to trick the host into thinking LUN0 and the string are available by creating a pseudo devices for each SCSI target ID so you can see pseudo device by issuing "ioscan" even if a LUN is not assigned.&lt;BR /&gt;&lt;BR /&gt;Because HP achieved this under the microcode level of the array, it would be better to ask for information about that from EMC support personal.&lt;BR /&gt;&lt;BR /&gt;Regards,&lt;BR /&gt;&lt;BR /&gt;</description>
    <pubDate>Wed, 25 Apr 2001 01:39:33 GMT</pubDate>
    <dc:creator>Insu Kim</dc:creator>
    <dc:date>2001-04-25T01:39:33Z</dc:date>
    <item>
      <title>Non sequenced LUNs</title>
      <link>https://community.hpe.com/t5/disk-enclosures/non-sequenced-luns/m-p/2520879#M1745</link>
      <description>&lt;BR /&gt;I would like to know what patch resolved the problem on HP-UX 11 where LUNs presented to the HBA had to be in sequence for the HBA and Host to properly see the devices.&lt;BR /&gt;&lt;BR /&gt;I have experienced this feature a number of times with EMC arrays and have always insisted upon getting devices presented to the host in a sequential manner so as to ensure that all devices were seen by the host.&lt;BR /&gt;&lt;BR /&gt;Thanks&lt;BR /&gt;&lt;BR /&gt;</description>
      <pubDate>Tue, 24 Apr 2001 19:10:44 GMT</pubDate>
      <guid>https://community.hpe.com/t5/disk-enclosures/non-sequenced-luns/m-p/2520879#M1745</guid>
      <dc:creator>Vince Inman</dc:creator>
      <dc:date>2001-04-24T19:10:44Z</dc:date>
    </item>
    <item>
      <title>Re: Non sequenced LUNs</title>
      <link>https://community.hpe.com/t5/disk-enclosures/non-sequenced-luns/m-p/2520880#M1746</link>
      <description>I've never seen the behavior you describe either in 10.20,11.0, or 11i. I've created and destroyed LUN's with abandon with with multiple&lt;BR /&gt;SCSI controller's on the same bus. The RAID LUN's always appeared as expected.</description>
      <pubDate>Tue, 24 Apr 2001 19:17:13 GMT</pubDate>
      <guid>https://community.hpe.com/t5/disk-enclosures/non-sequenced-luns/m-p/2520880#M1746</guid>
      <dc:creator>A. Clay Stephenson</dc:creator>
      <dc:date>2001-04-24T19:17:13Z</dc:date>
    </item>
    <item>
      <title>Re: Non sequenced LUNs</title>
      <link>https://community.hpe.com/t5/disk-enclosures/non-sequenced-luns/m-p/2520881#M1747</link>
      <description>I think patch PHKL_22759 is what you are looking for.  Have a look at &lt;A href="http://us-support.external.hp.com/cki/bin/doc.pl/sid=08bb2b2e119d58495c/screen=ckiDisplayDocument?docId=200000054213098" target="_blank"&gt;http://us-support.external.hp.com/cki/bin/doc.pl/sid=08bb2b2e119d58495c/screen=ckiDisplayDocument?docId=200000054213098&lt;/A&gt; for more details.  There were a couple of newer patches, but they have been  recalled due to other problems. &lt;BR /&gt;&lt;BR /&gt;Note that this patch depends on PHKL_18543, which if it is already installed and you attempt to re-install it, can really cause you problems.</description>
      <pubDate>Tue, 24 Apr 2001 20:02:48 GMT</pubDate>
      <guid>https://community.hpe.com/t5/disk-enclosures/non-sequenced-luns/m-p/2520881#M1747</guid>
      <dc:creator>Patrick Wallek</dc:creator>
      <dc:date>2001-04-24T20:02:48Z</dc:date>
    </item>
    <item>
      <title>Re: Non sequenced LUNs</title>
      <link>https://community.hpe.com/t5/disk-enclosures/non-sequenced-luns/m-p/2520882#M1748</link>
      <description>That issue is one of the assignment rlues applied to EMC disk array itself.&lt;BR /&gt;That is, LUNS should be in the string in order to be visible to the host.&lt;BR /&gt;&lt;BR /&gt;And HP has applied the same rule to XP-array but with a new released microcode, what XP-array does is to trick the host into thinking LUN0 and the string are available by creating a pseudo devices for each SCSI target ID so you can see pseudo device by issuing "ioscan" even if a LUN is not assigned.&lt;BR /&gt;&lt;BR /&gt;Because HP achieved this under the microcode level of the array, it would be better to ask for information about that from EMC support personal.&lt;BR /&gt;&lt;BR /&gt;Regards,&lt;BR /&gt;&lt;BR /&gt;</description>
      <pubDate>Wed, 25 Apr 2001 01:39:33 GMT</pubDate>
      <guid>https://community.hpe.com/t5/disk-enclosures/non-sequenced-luns/m-p/2520882#M1748</guid>
      <dc:creator>Insu Kim</dc:creator>
      <dc:date>2001-04-25T01:39:33Z</dc:date>
    </item>
    <item>
      <title>Re: Non sequenced LUNs</title>
      <link>https://community.hpe.com/t5/disk-enclosures/non-sequenced-luns/m-p/2520883#M1749</link>
      <description>yes it has,&lt;BR /&gt;this was called the LUN gap problem and occured when, on EMCs for example you deleted a LUN 3 for example, LUN4 and greater vanishes&lt;BR /&gt;&lt;BR /&gt;I can't recall exactly the patch, I'll ask around.&lt;BR /&gt;&lt;BR /&gt;Later,&lt;BR /&gt;Bill</description>
      <pubDate>Wed, 25 Apr 2001 09:32:01 GMT</pubDate>
      <guid>https://community.hpe.com/t5/disk-enclosures/non-sequenced-luns/m-p/2520883#M1749</guid>
      <dc:creator>Bill McNAMARA_1</dc:creator>
      <dc:date>2001-04-25T09:32:01Z</dc:date>
    </item>
    <item>
      <title>Re: Non sequenced LUNs</title>
      <link>https://community.hpe.com/t5/disk-enclosures/non-sequenced-luns/m-p/2520884#M1750</link>
      <description>Yes, PHKL_22759 is the right patch to get for HP-UX 11.00.  There was also an earlier patch, PHKL_21607 that also included this fix.&lt;BR /&gt;&lt;BR /&gt;Note that some customers with large numbers of LUNs have experience much longer boot times with PHKL_22759 installed (because we are now spending time scanning the "LUN holes").  We are working on a complementary patch to improve the boot times.&lt;BR /&gt;&lt;BR /&gt;Ron Lawson&lt;BR /&gt;project manager, hp-ux mass storage&lt;BR /&gt;</description>
      <pubDate>Fri, 27 Apr 2001 05:51:29 GMT</pubDate>
      <guid>https://community.hpe.com/t5/disk-enclosures/non-sequenced-luns/m-p/2520884#M1750</guid>
      <dc:creator>Ron Lawson_1</dc:creator>
      <dc:date>2001-04-27T05:51:29Z</dc:date>
    </item>
    <item>
      <title>Re: Non sequenced LUNs</title>
      <link>https://community.hpe.com/t5/disk-enclosures/non-sequenced-luns/m-p/2520885#M1751</link>
      <description>Two patches are available today.  PHKL_24004 is the latest SCSI patch for 11.00, which includes the fix to look for non-sequenced LUNs.  PHKL_24187 dramatically reduces boot and ioscan times for large fibrechannel configurations.  Enjoy!&lt;BR /&gt;&lt;BR /&gt;Ron Lawson&lt;BR /&gt;hp-ux mass storage r&amp;amp;d&lt;BR /&gt;&lt;BR /&gt;</description>
      <pubDate>Wed, 13 Jun 2001 15:00:12 GMT</pubDate>
      <guid>https://community.hpe.com/t5/disk-enclosures/non-sequenced-luns/m-p/2520885#M1751</guid>
      <dc:creator>Ron Lawson_1</dc:creator>
      <dc:date>2001-06-13T15:00:12Z</dc:date>
    </item>
  </channel>
</rss>

