<?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: AIX, LUNs from XP disk array are not accessible in Disk Enclosures</title>
    <link>https://community.hpe.com/t5/disk-enclosures/aix-luns-from-xp-disk-array-are-not-accessible/m-p/3823704#M20941</link>
    <description>As the previous post has said this is probably some form of reserve on the LUNs.&lt;BR /&gt;&lt;BR /&gt;If its a SCSI-2 reserve this can be released with any of the following methods - &lt;BR /&gt;&lt;BR /&gt;1 - Your HP engineer can reset the CHIP ports that the LUN is presented on from the Engineers console on the SVP.&lt;BR /&gt;&lt;BR /&gt;2 - You can issue a SCSI BUS reset to the CHIP port that the LUNs are presented on.  To do this you can zone a server in to the CHIP ports that the LUN is rpesented on and then use the tool of your choice to issue SCSI BUS RESETS.  If you have windows hosts you can use a tool called scsicmd.exe&lt;BR /&gt;&lt;BR /&gt;Its best to do these during a maintenance window as both methods will release all SCSI-2 reserves on ALL LUNs on the the CHIP ports that are reset.  Resetting the CHIP ports is a quick procedure but it can be a little disruptive.  Ive had to do this many times in Microsoft Cluster environments and never had any problems although I always do it during a maintenance window.&lt;BR /&gt;&lt;BR /&gt;If the reserve is a SCSI-3 persistent reserve on the LUNS these are not released by issuing a SCSI BUS RESET.  HDS has a tool called DLMPR that you can run and it will show you if a LUN has a persistent reserve, what the reservation key is and also allows you to remove a persistant reserve.  It might be worth asking your HP contacts if HP has a similar tool (after all the XP range is rebadged HITACHI storage).&lt;BR /&gt;&lt;BR /&gt;HTH&lt;BR /&gt;&lt;BR /&gt;mackem</description>
    <pubDate>Sat, 15 Jul 2006 18:03:57 GMT</pubDate>
    <dc:creator>Nigel Poulton</dc:creator>
    <dc:date>2006-07-15T18:03:57Z</dc:date>
    <item>
      <title>AIX, LUNs from XP disk array are not accessible</title>
      <link>https://community.hpe.com/t5/disk-enclosures/aix-luns-from-xp-disk-array-are-not-accessible/m-p/3823702#M20939</link>
      <description>Hi, All,&lt;BR /&gt;&lt;BR /&gt;Two LUNs on XP were used by a server with AIX 5.2. Then AIX 5.3 was cold-installed to this server. Volume group export was not done before upgrade. Now new AIX can not open these disks, VG import is not successful. Even dd from these disks is not working.&lt;BR /&gt;Tried to present these LUNs to HPUX, they are seen as zero size disks.&lt;BR /&gt;It seems that AIX locked the disks somehow and this lock is not cleared. If so, is there any way to clear such lock?&lt;BR /&gt;Thank you in advance.</description>
      <pubDate>Fri, 14 Jul 2006 06:03:10 GMT</pubDate>
      <guid>https://community.hpe.com/t5/disk-enclosures/aix-luns-from-xp-disk-array-are-not-accessible/m-p/3823702#M20939</guid>
      <dc:creator>Sergey Blatov</dc:creator>
      <dc:date>2006-07-14T06:03:10Z</dc:date>
    </item>
    <item>
      <title>Re: AIX, LUNs from XP disk array are not accessible</title>
      <link>https://community.hpe.com/t5/disk-enclosures/aix-luns-from-xp-disk-array-are-not-accessible/m-p/3823703#M20940</link>
      <description>Sometimes, problems like this happens when the FC reservation was not released by the host. The problem is that I don't know how to clear FC reservations in AIX. Maybe you can find a support document for that. It would worth a try.</description>
      <pubDate>Fri, 14 Jul 2006 10:18:56 GMT</pubDate>
      <guid>https://community.hpe.com/t5/disk-enclosures/aix-luns-from-xp-disk-array-are-not-accessible/m-p/3823703#M20940</guid>
      <dc:creator>Ivan Ferreira</dc:creator>
      <dc:date>2006-07-14T10:18:56Z</dc:date>
    </item>
    <item>
      <title>Re: AIX, LUNs from XP disk array are not accessible</title>
      <link>https://community.hpe.com/t5/disk-enclosures/aix-luns-from-xp-disk-array-are-not-accessible/m-p/3823704#M20941</link>
      <description>As the previous post has said this is probably some form of reserve on the LUNs.&lt;BR /&gt;&lt;BR /&gt;If its a SCSI-2 reserve this can be released with any of the following methods - &lt;BR /&gt;&lt;BR /&gt;1 - Your HP engineer can reset the CHIP ports that the LUN is presented on from the Engineers console on the SVP.&lt;BR /&gt;&lt;BR /&gt;2 - You can issue a SCSI BUS reset to the CHIP port that the LUNs are presented on.  To do this you can zone a server in to the CHIP ports that the LUN is rpesented on and then use the tool of your choice to issue SCSI BUS RESETS.  If you have windows hosts you can use a tool called scsicmd.exe&lt;BR /&gt;&lt;BR /&gt;Its best to do these during a maintenance window as both methods will release all SCSI-2 reserves on ALL LUNs on the the CHIP ports that are reset.  Resetting the CHIP ports is a quick procedure but it can be a little disruptive.  Ive had to do this many times in Microsoft Cluster environments and never had any problems although I always do it during a maintenance window.&lt;BR /&gt;&lt;BR /&gt;If the reserve is a SCSI-3 persistent reserve on the LUNS these are not released by issuing a SCSI BUS RESET.  HDS has a tool called DLMPR that you can run and it will show you if a LUN has a persistent reserve, what the reservation key is and also allows you to remove a persistant reserve.  It might be worth asking your HP contacts if HP has a similar tool (after all the XP range is rebadged HITACHI storage).&lt;BR /&gt;&lt;BR /&gt;HTH&lt;BR /&gt;&lt;BR /&gt;mackem</description>
      <pubDate>Sat, 15 Jul 2006 18:03:57 GMT</pubDate>
      <guid>https://community.hpe.com/t5/disk-enclosures/aix-luns-from-xp-disk-array-are-not-accessible/m-p/3823704#M20941</guid>
      <dc:creator>Nigel Poulton</dc:creator>
      <dc:date>2006-07-15T18:03:57Z</dc:date>
    </item>
    <item>
      <title>Re: AIX, LUNs from XP disk array are not accessible</title>
      <link>https://community.hpe.com/t5/disk-enclosures/aix-luns-from-xp-disk-array-are-not-accessible/m-p/3823705#M20942</link>
      <description>Hello Sergey,&lt;BR /&gt;&lt;BR /&gt;AIX keeps disks reservation when you "varyon" the volumegroup and will remove it when you "varyoff" volume groups. If the reservations are not porperly cleared you will get reservation errors on the host with "scsi_disk_2" and "scsi_disk_4", I believe. &lt;BR /&gt;&lt;BR /&gt;If you can't access the disk using "dd", I hope the reservations is left on the LUNS and your HP CE or customer support has to remove by logging in to the array.&lt;BR /&gt;&lt;BR /&gt;What is the status of the "hdisks" for the luns? Are they in "available" or "defined" state Have you tried cleaning the ODM and run "cfgmgr"? &lt;BR /&gt;&lt;BR /&gt;&lt;BR /&gt;Regards&lt;BR /&gt;Sathish</description>
      <pubDate>Sat, 15 Jul 2006 19:23:51 GMT</pubDate>
      <guid>https://community.hpe.com/t5/disk-enclosures/aix-luns-from-xp-disk-array-are-not-accessible/m-p/3823705#M20942</guid>
      <dc:creator>sathish kannan</dc:creator>
      <dc:date>2006-07-15T19:23:51Z</dc:date>
    </item>
  </channel>
</rss>

