<?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: Device file name change in HPE EVA Storage</title>
    <link>https://community.hpe.com/t5/hpe-eva-storage/device-file-name-change/m-p/4977693#M52622</link>
    <description>Is this an EVA 3000/5000(VCS 3.X) or 3000/5000 VCS 4.X or 4/6/8000? If is is the formal, Secure Path is required or you can get weird behavior. This is do to the Active Passive controllers.&lt;BR /&gt;&lt;BR /&gt;On VCS 4.X on the 3000/5000 or all the 4/6/8000's the controllers are Active/Active, so PVlinks are supported. &lt;BR /&gt;&lt;BR /&gt;Curt</description>
    <pubDate>Mon, 08 May 2006 23:13:49 GMT</pubDate>
    <dc:creator>krusty</dc:creator>
    <dc:date>2006-05-08T23:13:49Z</dc:date>
    <item>
      <title>Device file name change</title>
      <link>https://community.hpe.com/t5/hpe-eva-storage/device-file-name-change/m-p/4977687#M52616</link>
      <description>Hi,&lt;BR /&gt;I reseated on of the disks in the EVA and regrouped the diskgroup. After that I noticed disk device file name has changed in the HP-UX servers connected to the EVA. Is this is normal behaviour? If so then on what situation can this happen and is there any solution to prevent this from happening?&lt;BR /&gt;</description>
      <pubDate>Mon, 08 May 2006 04:44:41 GMT</pubDate>
      <guid>https://community.hpe.com/t5/hpe-eva-storage/device-file-name-change/m-p/4977687#M52616</guid>
      <dc:creator>BPatrick</dc:creator>
      <dc:date>2006-05-08T04:44:41Z</dc:date>
    </item>
    <item>
      <title>Re: Device file name change</title>
      <link>https://community.hpe.com/t5/hpe-eva-storage/device-file-name-change/m-p/4977688#M52617</link>
      <description>What exactly do you mean by "re-grouped the diskgroup?" Did you at any time delete and re-create Vdisks?</description>
      <pubDate>Mon, 08 May 2006 10:20:35 GMT</pubDate>
      <guid>https://community.hpe.com/t5/hpe-eva-storage/device-file-name-change/m-p/4977688#M52617</guid>
      <dc:creator>Mark Poeschl_2</dc:creator>
      <dc:date>2006-05-08T10:20:35Z</dc:date>
    </item>
    <item>
      <title>Re: Device file name change</title>
      <link>https://community.hpe.com/t5/hpe-eva-storage/device-file-name-change/m-p/4977689#M52618</link>
      <description>One of the disk was went out of the group when I reseated it. so I added that disk back in to the diskgroup. Thats all I have done. I dint do any changes to the Vdisks.</description>
      <pubDate>Mon, 08 May 2006 10:43:35 GMT</pubDate>
      <guid>https://community.hpe.com/t5/hpe-eva-storage/device-file-name-change/m-p/4977689#M52618</guid>
      <dc:creator>BPatrick</dc:creator>
      <dc:date>2006-05-08T10:43:35Z</dc:date>
    </item>
    <item>
      <title>Re: Device file name change</title>
      <link>https://community.hpe.com/t5/hpe-eva-storage/device-file-name-change/m-p/4977690#M52619</link>
      <description>Patrick,&lt;BR /&gt;&lt;BR /&gt;Did you by chance reboot your HP-UX box?  I am wondering if you have your disks persistent across reboots?  &lt;BR /&gt;&lt;BR /&gt;Have you ran these commands?&lt;BR /&gt;&lt;BR /&gt;# spmgr update&lt;BR /&gt;# kmadmin -L swspData&lt;BR /&gt;# config -M swspData -u</description>
      <pubDate>Mon, 08 May 2006 11:42:49 GMT</pubDate>
      <guid>https://community.hpe.com/t5/hpe-eva-storage/device-file-name-change/m-p/4977690#M52619</guid>
      <dc:creator>Sheriff Andy</dc:creator>
      <dc:date>2006-05-08T11:42:49Z</dc:date>
    </item>
    <item>
      <title>Re: Device file name change</title>
      <link>https://community.hpe.com/t5/hpe-eva-storage/device-file-name-change/m-p/4977691#M52620</link>
      <description>Sheriff,&lt;BR /&gt;I dont use secure path, instead I use pvlinks. So spmgr is not available.</description>
      <pubDate>Mon, 08 May 2006 12:05:58 GMT</pubDate>
      <guid>https://community.hpe.com/t5/hpe-eva-storage/device-file-name-change/m-p/4977691#M52620</guid>
      <dc:creator>BPatrick</dc:creator>
      <dc:date>2006-05-08T12:05:58Z</dc:date>
    </item>
    <item>
      <title>Re: Device file name change</title>
      <link>https://community.hpe.com/t5/hpe-eva-storage/device-file-name-change/m-p/4977692#M52621</link>
      <description>We have had our device file names change on 3 different occasions;&lt;BR /&gt;&lt;BR /&gt;As you said, we do use secure path.  We have a EVA 5K, attached to 3 HP-UX systems, and 5 Windows systems.&lt;BR /&gt;&lt;BR /&gt;1)  After a reboot, the device file names came up different because we didn't make the disks persistent across reboots.&lt;BR /&gt;2)  After a datacenter power outage, we had one volume group change its device file names.  Everyone else was fine.&lt;BR /&gt;3)  After an ignite all of the device file names changed.&lt;BR /&gt;</description>
      <pubDate>Mon, 08 May 2006 12:28:10 GMT</pubDate>
      <guid>https://community.hpe.com/t5/hpe-eva-storage/device-file-name-change/m-p/4977692#M52621</guid>
      <dc:creator>Sheriff Andy</dc:creator>
      <dc:date>2006-05-08T12:28:10Z</dc:date>
    </item>
    <item>
      <title>Re: Device file name change</title>
      <link>https://community.hpe.com/t5/hpe-eva-storage/device-file-name-change/m-p/4977693#M52622</link>
      <description>Is this an EVA 3000/5000(VCS 3.X) or 3000/5000 VCS 4.X or 4/6/8000? If is is the formal, Secure Path is required or you can get weird behavior. This is do to the Active Passive controllers.&lt;BR /&gt;&lt;BR /&gt;On VCS 4.X on the 3000/5000 or all the 4/6/8000's the controllers are Active/Active, so PVlinks are supported. &lt;BR /&gt;&lt;BR /&gt;Curt</description>
      <pubDate>Mon, 08 May 2006 23:13:49 GMT</pubDate>
      <guid>https://community.hpe.com/t5/hpe-eva-storage/device-file-name-change/m-p/4977693#M52622</guid>
      <dc:creator>krusty</dc:creator>
      <dc:date>2006-05-08T23:13:49Z</dc:date>
    </item>
    <item>
      <title>Re: Device file name change</title>
      <link>https://community.hpe.com/t5/hpe-eva-storage/device-file-name-change/m-p/4977694#M52623</link>
      <description>Its an EVA4000 and i guess secure path is not compatible with the eva 4k</description>
      <pubDate>Tue, 09 May 2006 02:05:42 GMT</pubDate>
      <guid>https://community.hpe.com/t5/hpe-eva-storage/device-file-name-change/m-p/4977694#M52623</guid>
      <dc:creator>BPatrick</dc:creator>
      <dc:date>2006-05-09T02:05:42Z</dc:date>
    </item>
    <item>
      <title>Re: Device file name change</title>
      <link>https://community.hpe.com/t5/hpe-eva-storage/device-file-name-change/m-p/4977695#M52624</link>
      <description>Hi Patrick,&lt;BR /&gt;&lt;BR /&gt;EVA4000 supports autopath component of the securepath. therefore "autopath display" should display the LUNs and device files.&lt;BR /&gt;&lt;BR /&gt;If you had deleted LUNs and created newer LUNs then the device files can change after the system reboots.&lt;BR /&gt;&lt;BR /&gt;Always remember to delete the LUN from Securepath first and then unpresent the LUNs.&lt;BR /&gt;If you had not followed this, you might see the device files changing when your HP-UX system reboots.&lt;BR /&gt;&lt;BR /&gt;With regards,&lt;BR /&gt;Mohan.</description>
      <pubDate>Tue, 09 May 2006 06:01:25 GMT</pubDate>
      <guid>https://community.hpe.com/t5/hpe-eva-storage/device-file-name-change/m-p/4977695#M52624</guid>
      <dc:creator>Mohanasundaram_1</dc:creator>
      <dc:date>2006-05-09T06:01:25Z</dc:date>
    </item>
    <item>
      <title>Re: Device file name change</title>
      <link>https://community.hpe.com/t5/hpe-eva-storage/device-file-name-change/m-p/4977696#M52625</link>
      <description>Mohan,&lt;BR /&gt;The disks are configured with pvlinks and i am not using securepath or autopath. I got a response from HP that the device names can change if the fibre channel ports change. in my case this has happened when i recently swapped both the cables recently during some test. So I think that answers my question. I will create a link to the new device file which will solve the problem. &lt;BR /&gt;Thank you all for your valuable responses. I will assign points and close this case now</description>
      <pubDate>Tue, 09 May 2006 06:54:43 GMT</pubDate>
      <guid>https://community.hpe.com/t5/hpe-eva-storage/device-file-name-change/m-p/4977696#M52625</guid>
      <dc:creator>BPatrick</dc:creator>
      <dc:date>2006-05-09T06:54:43Z</dc:date>
    </item>
    <item>
      <title>Re: Device file name change</title>
      <link>https://community.hpe.com/t5/hpe-eva-storage/device-file-name-change/m-p/4977697#M52626</link>
      <description>Thread closed</description>
      <pubDate>Tue, 09 May 2006 06:57:53 GMT</pubDate>
      <guid>https://community.hpe.com/t5/hpe-eva-storage/device-file-name-change/m-p/4977697#M52626</guid>
      <dc:creator>BPatrick</dc:creator>
      <dc:date>2006-05-09T06:57:53Z</dc:date>
    </item>
  </channel>
</rss>

