<?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: EVA Disk Device Changes in Operating System - HP-UX</title>
    <link>https://community.hpe.com/t5/operating-system-hp-ux/eva-disk-device-changes/m-p/3797335#M265956</link>
    <description>Hi Guys,&lt;BR /&gt;&lt;BR /&gt;As queried, I encounter before the vgexport of -s option will automatically take care of the device file should there be changes. Is that right to say?&lt;BR /&gt;&lt;BR /&gt;Thanks/cliff</description>
    <pubDate>Wed, 31 May 2006 10:48:39 GMT</pubDate>
    <dc:creator>Cliff Lim Kok Hwee</dc:creator>
    <dc:date>2006-05-31T10:48:39Z</dc:date>
    <item>
      <title>EVA Disk Device Changes</title>
      <link>https://community.hpe.com/t5/operating-system-hp-ux/eva-disk-device-changes/m-p/3797331#M265952</link>
      <description>Hi Forumers,&lt;BR /&gt;&lt;BR /&gt;I will be having my existing 8 port SAN switch (non-HP) to be changed to a 8 port SAN switch (HP).&lt;BR /&gt;&lt;BR /&gt;All SAN connectivities will be left unchanged.&lt;BR /&gt;&lt;BR /&gt;Query: &lt;BR /&gt;&lt;BR /&gt;- Will the disks device file changed upon the new SAN switch changed?&lt;BR /&gt;- If so I will be doing the following &lt;BR /&gt;1)vgexport -p -v -s -&lt;BR /&gt; &lt;MAPFILE&gt; &lt;VGNAME&gt; and safe the mapfile. &lt;BR /&gt;2)vgexport the existing vg &lt;BR /&gt;3)mkdir /dev/vgname&lt;BR /&gt;chmod 755 /dev/vgname&lt;BR /&gt;mknod /dev/vgname/group c 64 0x010000&lt;BR /&gt;4)vgimport -v -s &lt;MAPFILE&gt; &lt;VGNAME&gt;&lt;BR /&gt;&lt;BR /&gt;I encounter before the vgexport of -s option will automatically take care of the device file should there be changes. &lt;BR /&gt;&lt;BR /&gt;Any advises on my steps and findings?&lt;BR /&gt;&lt;BR /&gt;Thanks/Cliff&lt;BR /&gt;&lt;BR /&gt;&lt;/VGNAME&gt;&lt;/MAPFILE&gt;&lt;/VGNAME&gt;&lt;/MAPFILE&gt;</description>
      <pubDate>Wed, 31 May 2006 04:13:30 GMT</pubDate>
      <guid>https://community.hpe.com/t5/operating-system-hp-ux/eva-disk-device-changes/m-p/3797331#M265952</guid>
      <dc:creator>Cliff Lim Kok Hwee</dc:creator>
      <dc:date>2006-05-31T04:13:30Z</dc:date>
    </item>
    <item>
      <title>Re: EVA Disk Device Changes</title>
      <link>https://community.hpe.com/t5/operating-system-hp-ux/eva-disk-device-changes/m-p/3797332#M265953</link>
      <description>Hi Cliff,&lt;BR /&gt;&lt;BR /&gt;Theoritically it should not change you dev files. &lt;BR /&gt;&lt;BR /&gt;Only thing you missed out is "ioscan -fCdisk" and "insg -e"&lt;BR /&gt;#1 missed the -m &lt;MAPFILE&gt;&lt;BR /&gt;#4 does not have the /dev/dsk/&lt;DEV file=""&gt;&lt;BR /&gt;#5 vgchange -a y &lt;VGNAME&gt;&lt;BR /&gt;&lt;BR /&gt;Also what ever you have said is sufficient in the event of a change in dev file. &lt;BR /&gt;&lt;BR /&gt;My advice is don't do all servers in one go. Just do one by one. &lt;BR /&gt;&lt;BR /&gt;Please ensure you shutdown the application. Connect to the new san port.&lt;BR /&gt;&lt;BR /&gt;All the best.&lt;BR /&gt;&lt;BR /&gt;Chan&lt;/VGNAME&gt;&lt;/DEV&gt;&lt;/MAPFILE&gt;</description>
      <pubDate>Wed, 31 May 2006 04:24:19 GMT</pubDate>
      <guid>https://community.hpe.com/t5/operating-system-hp-ux/eva-disk-device-changes/m-p/3797332#M265953</guid>
      <dc:creator>Chan 007</dc:creator>
      <dc:date>2006-05-31T04:24:19Z</dc:date>
    </item>
    <item>
      <title>Re: EVA Disk Device Changes</title>
      <link>https://community.hpe.com/t5/operating-system-hp-ux/eva-disk-device-changes/m-p/3797333#M265954</link>
      <description>Hello Cliff,&lt;BR /&gt;&lt;BR /&gt;Yes, you are right the device files may change so it is better to be on the safer side..wanted to add some changes to ur action plan..&lt;BR /&gt;&lt;BR /&gt;Before the SAN changes&lt;BR /&gt;# vgexport -p -v -s -m &lt;FILENAME&gt; &lt;VGNAME&gt;&lt;BR /&gt;# vgcfgbackup /dev/vgname&lt;BR /&gt;# cp -p /etc/lvmtab /etc/lvmtab.&lt;DATE&gt;&lt;BR /&gt;# cp -p /etc/lvmconf/vgnaem.conf /etc/lvmconf/vgname.date&lt;BR /&gt;# list of PV's part of this vg..&lt;BR /&gt;&lt;BR /&gt;Once the changes on the san are completed..&lt;BR /&gt;&lt;BR /&gt;# ioscan -fn&lt;BR /&gt;# insf -e (to recreate the device files)&lt;BR /&gt;# check if the device files have changed..then&lt;BR /&gt;# vgexport the existing vg &lt;BR /&gt;3)mkdir /dev/vgname&lt;BR /&gt;chmod 755 /dev/vgname&lt;BR /&gt;mknod /dev/vgname/group c 64 0x010000&lt;BR /&gt;4)vgimport -p -v -s -m &lt;MAPFILE&gt; &lt;VGNAME&gt;&lt;BR /&gt;If there are no errors reported above then proceed further,else resolve the errors before proceeding..&lt;BR /&gt;&lt;BR /&gt;# vgimport -v -s -m &lt;MAPFILE&gt; &lt;VGNAME&gt;&lt;BR /&gt;# vgcfgbackup /dev/vgname&lt;BR /&gt;&lt;BR /&gt;Hope this helps..&lt;BR /&gt;&lt;BR /&gt;regards&lt;BR /&gt;&lt;BR /&gt;albert&lt;BR /&gt;&lt;BR /&gt;&lt;BR /&gt;&lt;BR /&gt;&lt;/VGNAME&gt;&lt;/MAPFILE&gt;&lt;/VGNAME&gt;&lt;/MAPFILE&gt;&lt;/DATE&gt;&lt;/VGNAME&gt;&lt;/FILENAME&gt;</description>
      <pubDate>Wed, 31 May 2006 04:26:31 GMT</pubDate>
      <guid>https://community.hpe.com/t5/operating-system-hp-ux/eva-disk-device-changes/m-p/3797333#M265954</guid>
      <dc:creator>Albert_31</dc:creator>
      <dc:date>2006-05-31T04:26:31Z</dc:date>
    </item>
    <item>
      <title>Re: EVA Disk Device Changes</title>
      <link>https://community.hpe.com/t5/operating-system-hp-ux/eva-disk-device-changes/m-p/3797334#M265955</link>
      <description>Any changes to the fabric will result in the change of device files. Son in your case it definitely change. The steps that you metntioned are correct.</description>
      <pubDate>Wed, 31 May 2006 07:15:05 GMT</pubDate>
      <guid>https://community.hpe.com/t5/operating-system-hp-ux/eva-disk-device-changes/m-p/3797334#M265955</guid>
      <dc:creator>BPatrick</dc:creator>
      <dc:date>2006-05-31T07:15:05Z</dc:date>
    </item>
    <item>
      <title>Re: EVA Disk Device Changes</title>
      <link>https://community.hpe.com/t5/operating-system-hp-ux/eva-disk-device-changes/m-p/3797335#M265956</link>
      <description>Hi Guys,&lt;BR /&gt;&lt;BR /&gt;As queried, I encounter before the vgexport of -s option will automatically take care of the device file should there be changes. Is that right to say?&lt;BR /&gt;&lt;BR /&gt;Thanks/cliff</description>
      <pubDate>Wed, 31 May 2006 10:48:39 GMT</pubDate>
      <guid>https://community.hpe.com/t5/operating-system-hp-ux/eva-disk-device-changes/m-p/3797335#M265956</guid>
      <dc:creator>Cliff Lim Kok Hwee</dc:creator>
      <dc:date>2006-05-31T10:48:39Z</dc:date>
    </item>
    <item>
      <title>Re: EVA Disk Device Changes</title>
      <link>https://community.hpe.com/t5/operating-system-hp-ux/eva-disk-device-changes/m-p/3797336#M265957</link>
      <description>vgexport and then vgimport are the safest way to make sure that you will have the same device name even after the changing your SAN switch.&lt;BR /&gt;If the device file name change is not a problem then, after the changing switch you can do a vgscan to re-create the lvmtab file with the new device names.&lt;BR /&gt;you can use vgscan -a -v&lt;BR /&gt;and then vgchange -a -y to resync the information on the disk</description>
      <pubDate>Wed, 31 May 2006 11:26:31 GMT</pubDate>
      <guid>https://community.hpe.com/t5/operating-system-hp-ux/eva-disk-device-changes/m-p/3797336#M265957</guid>
      <dc:creator>BPatrick</dc:creator>
      <dc:date>2006-05-31T11:26:31Z</dc:date>
    </item>
  </channel>
</rss>

