<?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 securepath devices names change in Disk Enclosures</title>
    <link>https://community.hpe.com/t5/disk-enclosures/securepath-devices-names-change/m-p/3798174#M20535</link>
    <description>Hi All,&lt;BR /&gt;I Have an rp7410 running HP-UX 11.11 and securepath ver. 3.0C connected to an EVA5000 Storage via two HBA's and two SAN switches, recently we had power down siutuation and after starting the system all the device files of the Vdisks have changed, I had to export and import all my Volume Groups, the question is what cused this problem and what can I do to prevent it from happining again?</description>
    <pubDate>Wed, 31 May 2006 23:53:55 GMT</pubDate>
    <dc:creator>Amin_1</dc:creator>
    <dc:date>2006-05-31T23:53:55Z</dc:date>
    <item>
      <title>securepath devices names change</title>
      <link>https://community.hpe.com/t5/disk-enclosures/securepath-devices-names-change/m-p/3798174#M20535</link>
      <description>Hi All,&lt;BR /&gt;I Have an rp7410 running HP-UX 11.11 and securepath ver. 3.0C connected to an EVA5000 Storage via two HBA's and two SAN switches, recently we had power down siutuation and after starting the system all the device files of the Vdisks have changed, I had to export and import all my Volume Groups, the question is what cused this problem and what can I do to prevent it from happining again?</description>
      <pubDate>Wed, 31 May 2006 23:53:55 GMT</pubDate>
      <guid>https://community.hpe.com/t5/disk-enclosures/securepath-devices-names-change/m-p/3798174#M20535</guid>
      <dc:creator>Amin_1</dc:creator>
      <dc:date>2006-05-31T23:53:55Z</dc:date>
    </item>
    <item>
      <title>Re: securepath devices names change</title>
      <link>https://community.hpe.com/t5/disk-enclosures/securepath-devices-names-change/m-p/3798175#M20536</link>
      <description>Hi,&lt;BR /&gt;Persistant binding!! Upgrade to secure path 3.0F. check VCS is compatible with 3.0F&lt;BR /&gt;&lt;BR /&gt;3.0D or earlier have this problem. 3.0E or above this is fixed. If you want to continue using the 3.0C there are some special steps to make it persistent across reboots.&lt;BR /&gt;&lt;BR /&gt;spmgr update&lt;BR /&gt;kmadmin -L swspData&lt;BR /&gt;config -M swspData -u&lt;BR /&gt;&lt;BR /&gt;This will make the changes persistent across the reboots&lt;BR /&gt;&lt;BR /&gt;Please read page 13/14/15  of the attachment.&lt;BR /&gt;&lt;BR /&gt;Regds&lt;BR /&gt;TT</description>
      <pubDate>Thu, 01 Jun 2006 01:34:02 GMT</pubDate>
      <guid>https://community.hpe.com/t5/disk-enclosures/securepath-devices-names-change/m-p/3798175#M20536</guid>
      <dc:creator>Thayanidhi</dc:creator>
      <dc:date>2006-06-01T01:34:02Z</dc:date>
    </item>
    <item>
      <title>Re: securepath devices names change</title>
      <link>https://community.hpe.com/t5/disk-enclosures/securepath-devices-names-change/m-p/3798176#M20537</link>
      <description>We had this happen during a power outage, and also after we ignited our server.&lt;BR /&gt;&lt;BR /&gt;I am not so sure about updating the securepath as we are on version 3.0E.  I would have some good map files of your volume groups.  Make sure that you vgexport -p -v -s -m /dev/vgnn.map vgnn (use the -s switch).&lt;BR /&gt;&lt;BR /&gt;Andy</description>
      <pubDate>Thu, 01 Jun 2006 18:36:08 GMT</pubDate>
      <guid>https://community.hpe.com/t5/disk-enclosures/securepath-devices-names-change/m-p/3798176#M20537</guid>
      <dc:creator>Sheriff Andy</dc:creator>
      <dc:date>2006-06-01T18:36:08Z</dc:date>
    </item>
  </channel>
</rss>

