<?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 VNX5200UNB disk devices keep reappearing in Operating System - HP-UX</title>
    <link>https://community.hpe.com/t5/operating-system-hp-ux/vnx5200unb-disk-devices-keep-reappearing/m-p/6897499#M492707</link>
    <description>&lt;P&gt;Hello people,&lt;/P&gt;&lt;P&gt;I've been migrating the LUNs of a 2-node BL860c HP-UX 11.31 cluster from a Clariion CX4-240 storage array to a VNX-5200.&lt;BR /&gt;So far so good, new LUNs are seen and migration is performed smoothly using LVM mirroring.&lt;/P&gt;&lt;P&gt;However since I have started mapping LUNs from this new VNX-5200 array to this cluster, I keep getting alerts from HPSIM saying "(WBEM) Lun path belonging to LUN has gone offline."&lt;/P&gt;&lt;P&gt;Looking carefully, these hardware paths correspond to disk with a type of "VNX5200UNB" and the corresponding /dev/disk/diskNNN are not accessible (I/O error)&lt;/P&gt;&lt;P&gt;If I rmsf them by hardware paths (both the agile and legacy disks) they keep reappearing after a while, syslog.log tells me that the sfd deamon has run an insf command to create them back.&lt;/P&gt;&lt;P&gt;I see no obvious error in my configuration, the hosts are registered on the VNX-5200 as "HP non auto-tresspass" with failover mode = 4, which HP tells me are the recommended values.&lt;/P&gt;&lt;P&gt;The EMC Connectivity Guide for HP-UX mentions a few possible causes for this, including tresspassed LUNs. There were two, but I've moved them back to their home SP now and the problem is still there.&lt;/P&gt;&lt;P&gt;This has never happened with the old Clariion CX4-240 array. Clearly I must have done something wrong, but I fail to spot what. The only "unusual" thing I've done is to skip host LUN ID #0 &amp;nbsp;when affecting LUNs to the storage group (I've started at 1) based on some vague warning I had received to avoid using #0.&lt;/P&gt;&lt;P&gt;Any advice greatly appreciated, I can provide whatever extra info asked for.&lt;/P&gt;&lt;P&gt;Alain&lt;/P&gt;&lt;P&gt;&amp;nbsp;&lt;/P&gt;</description>
    <pubDate>Fri, 09 Sep 2016 16:15:51 GMT</pubDate>
    <dc:creator>HEGP</dc:creator>
    <dc:date>2016-09-09T16:15:51Z</dc:date>
    <item>
      <title>VNX5200UNB disk devices keep reappearing</title>
      <link>https://community.hpe.com/t5/operating-system-hp-ux/vnx5200unb-disk-devices-keep-reappearing/m-p/6897499#M492707</link>
      <description>&lt;P&gt;Hello people,&lt;/P&gt;&lt;P&gt;I've been migrating the LUNs of a 2-node BL860c HP-UX 11.31 cluster from a Clariion CX4-240 storage array to a VNX-5200.&lt;BR /&gt;So far so good, new LUNs are seen and migration is performed smoothly using LVM mirroring.&lt;/P&gt;&lt;P&gt;However since I have started mapping LUNs from this new VNX-5200 array to this cluster, I keep getting alerts from HPSIM saying "(WBEM) Lun path belonging to LUN has gone offline."&lt;/P&gt;&lt;P&gt;Looking carefully, these hardware paths correspond to disk with a type of "VNX5200UNB" and the corresponding /dev/disk/diskNNN are not accessible (I/O error)&lt;/P&gt;&lt;P&gt;If I rmsf them by hardware paths (both the agile and legacy disks) they keep reappearing after a while, syslog.log tells me that the sfd deamon has run an insf command to create them back.&lt;/P&gt;&lt;P&gt;I see no obvious error in my configuration, the hosts are registered on the VNX-5200 as "HP non auto-tresspass" with failover mode = 4, which HP tells me are the recommended values.&lt;/P&gt;&lt;P&gt;The EMC Connectivity Guide for HP-UX mentions a few possible causes for this, including tresspassed LUNs. There were two, but I've moved them back to their home SP now and the problem is still there.&lt;/P&gt;&lt;P&gt;This has never happened with the old Clariion CX4-240 array. Clearly I must have done something wrong, but I fail to spot what. The only "unusual" thing I've done is to skip host LUN ID #0 &amp;nbsp;when affecting LUNs to the storage group (I've started at 1) based on some vague warning I had received to avoid using #0.&lt;/P&gt;&lt;P&gt;Any advice greatly appreciated, I can provide whatever extra info asked for.&lt;/P&gt;&lt;P&gt;Alain&lt;/P&gt;&lt;P&gt;&amp;nbsp;&lt;/P&gt;</description>
      <pubDate>Fri, 09 Sep 2016 16:15:51 GMT</pubDate>
      <guid>https://community.hpe.com/t5/operating-system-hp-ux/vnx5200unb-disk-devices-keep-reappearing/m-p/6897499#M492707</guid>
      <dc:creator>HEGP</dc:creator>
      <dc:date>2016-09-09T16:15:51Z</dc:date>
    </item>
  </channel>
</rss>

