<?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: windows boot from SAN upgrade basic MPIO to full MPIO in Disk Enclosures</title>
    <link>https://community.hpe.com/t5/disk-enclosures/windows-boot-from-san-upgrade-basic-mpio-to-full-mpio/m-p/4359567#M30177</link>
    <description>Hi,&lt;BR /&gt;the following coexistences are supported:&lt;BR /&gt;MPIO FF for EVA 4k/6k/8k coexistence on the same server :&lt;BR /&gt;a) Secure Path, YES&lt;BR /&gt;b) HP MPIO Full Featured DSM for EVA3000/5000 VCS 4.xxx, YES&lt;BR /&gt;c) HP MPIO Full Featured DSM for MSA1000/1500&lt;BR /&gt;(Active-Active), YES&lt;BR /&gt;d) HP MPIO basic failover for EVA arrays, YES &lt;BR /&gt;e) HP MPIO basic failover for XP arrays, No&lt;BR /&gt;f) MS DSM, Yes&lt;BR /&gt;&lt;BR /&gt;</description>
    <pubDate>Mon, 16 Feb 2009 19:19:54 GMT</pubDate>
    <dc:creator>IBaltay</dc:creator>
    <dc:date>2009-02-16T19:19:54Z</dc:date>
    <item>
      <title>windows boot from SAN upgrade basic MPIO to full MPIO</title>
      <link>https://community.hpe.com/t5/disk-enclosures/windows-boot-from-san-upgrade-basic-mpio-to-full-mpio/m-p/4359562#M30172</link>
      <description>My blades are currently booting from SAN with Windows 2003 x86 and x64 to an EVA 5000 [3.110] esing basic HP MPIO.&lt;BR /&gt;&lt;BR /&gt;I will soon be migrating all of the data to an EVA8100 using Continuous Access.&lt;BR /&gt;&lt;BR /&gt;I have viewed the HP MPIO Full Featured DSM EVA4x00/6x00/8x00 family of Disk Arrays 3.01.00 Installation and Reference guide which describes upgrade steps for HP MPIO of a stand alone and clustered systems However, there was no procedures listed if you boot Windows from SAN.&lt;BR /&gt;&lt;BR /&gt;Can anyone tell me the best practice I should follow to move my Windows boot from SAN blades to my new EVA?  &lt;BR /&gt;&lt;BR /&gt;I was thinking I would perform the following steps.&lt;BR /&gt;shut down Windows blade&lt;BR /&gt;unzone blade from EVA5000&lt;BR /&gt;zone blade for EVA8100&lt;BR /&gt;Command View EVA EVA8100, present vdisks to blade&lt;BR /&gt;boot up blade&lt;BR /&gt;upgrade MPIO&lt;BR /&gt;&lt;BR /&gt;thanks in advance</description>
      <pubDate>Mon, 16 Feb 2009 17:10:44 GMT</pubDate>
      <guid>https://community.hpe.com/t5/disk-enclosures/windows-boot-from-san-upgrade-basic-mpio-to-full-mpio/m-p/4359562#M30172</guid>
      <dc:creator>mgtow</dc:creator>
      <dc:date>2009-02-16T17:10:44Z</dc:date>
    </item>
    <item>
      <title>Re: windows boot from SAN upgrade basic MPIO to full MPIO</title>
      <link>https://community.hpe.com/t5/disk-enclosures/windows-boot-from-san-upgrade-basic-mpio-to-full-mpio/m-p/4359563#M30173</link>
      <description>The basic MPIO does not provide coexistence with any other MPIO.&lt;BR /&gt;&lt;BR /&gt;I would first configure a singe-path access to the EVA-5000 (make sure you hit the controller that owns the virtual disk). Then un-install the basic MPIO and reboot.&lt;BR /&gt;&lt;BR /&gt;Replicate the disk to the EVA8100 and boot single-path from the 8100. Install the full-featured MPIO and MMC plugin. Configure the remaining paths and do a reboot to be sure all paths are recognized fine and everything works.</description>
      <pubDate>Mon, 16 Feb 2009 18:19:31 GMT</pubDate>
      <guid>https://community.hpe.com/t5/disk-enclosures/windows-boot-from-san-upgrade-basic-mpio-to-full-mpio/m-p/4359563#M30173</guid>
      <dc:creator>Uwe Zessin</dc:creator>
      <dc:date>2009-02-16T18:19:31Z</dc:date>
    </item>
    <item>
      <title>Re: windows boot from SAN upgrade basic MPIO to full MPIO</title>
      <link>https://community.hpe.com/t5/disk-enclosures/windows-boot-from-san-upgrade-basic-mpio-to-full-mpio/m-p/4359564#M30174</link>
      <description>Hi,&lt;BR /&gt;the san design guide p.192 lists windows supported windows multipathin coexistence matrix:&lt;BR /&gt;&lt;A href="http://h20000.www2.hp.com/bc/docs/support/SupportManual/c00403562/c00403562.pdf?jumpid=reg_R1002_USEN" target="_blank"&gt;http://h20000.www2.hp.com/bc/docs/support/SupportManual/c00403562/c00403562.pdf?jumpid=reg_R1002_USEN&lt;/A&gt;&lt;BR /&gt;&lt;BR /&gt;from that you can see that the mpio basic for the eva 3k/5k (3110) can coexist with mpio ff for eva 4k/6k/8k (e.g. 6110) and thus giving you the opportunity to nicely CA migrate all relevant VDISKS to new EVA and then shut down the server and do the CA failover to the new EVA (the failover means that roles of the primary and secondary VDISKs swap and then you can try to boot the servers now from Active/Active EVA...&lt;BR /&gt;&lt;BR /&gt;&lt;BR /&gt;&lt;BR /&gt;&lt;BR /&gt;</description>
      <pubDate>Mon, 16 Feb 2009 18:31:26 GMT</pubDate>
      <guid>https://community.hpe.com/t5/disk-enclosures/windows-boot-from-san-upgrade-basic-mpio-to-full-mpio/m-p/4359564#M30174</guid>
      <dc:creator>IBaltay</dc:creator>
      <dc:date>2009-02-16T18:31:26Z</dc:date>
    </item>
    <item>
      <title>Re: windows boot from SAN upgrade basic MPIO to full MPIO</title>
      <link>https://community.hpe.com/t5/disk-enclosures/windows-boot-from-san-upgrade-basic-mpio-to-full-mpio/m-p/4359565#M30175</link>
      <description>I don't have high-speed download capability right now to check that link...&lt;BR /&gt;&lt;BR /&gt;If it is document number AA-RW86Z-TE (January 26, 2009), then page 192 contains the HP-UX matrix. This thread is about Windows and if I am reading the Windows matrix on page 214 correctly, there is NO coexistence.</description>
      <pubDate>Mon, 16 Feb 2009 18:46:51 GMT</pubDate>
      <guid>https://community.hpe.com/t5/disk-enclosures/windows-boot-from-san-upgrade-basic-mpio-to-full-mpio/m-p/4359565#M30175</guid>
      <dc:creator>Uwe Zessin</dc:creator>
      <dc:date>2009-02-16T18:46:51Z</dc:date>
    </item>
    <item>
      <title>Re: windows boot from SAN upgrade basic MPIO to full MPIO</title>
      <link>https://community.hpe.com/t5/disk-enclosures/windows-boot-from-san-upgrade-basic-mpio-to-full-mpio/m-p/4359566#M30176</link>
      <description>Uwe,&lt;BR /&gt;the page number is different (214), but i see it as supported :-) with 4k/6k/8k (minimum XCS6110) and not supported with 3k/5k (VCS4x), so I will check it...</description>
      <pubDate>Mon, 16 Feb 2009 19:04:10 GMT</pubDate>
      <guid>https://community.hpe.com/t5/disk-enclosures/windows-boot-from-san-upgrade-basic-mpio-to-full-mpio/m-p/4359566#M30176</guid>
      <dc:creator>IBaltay</dc:creator>
      <dc:date>2009-02-16T19:04:10Z</dc:date>
    </item>
    <item>
      <title>Re: windows boot from SAN upgrade basic MPIO to full MPIO</title>
      <link>https://community.hpe.com/t5/disk-enclosures/windows-boot-from-san-upgrade-basic-mpio-to-full-mpio/m-p/4359567#M30177</link>
      <description>Hi,&lt;BR /&gt;the following coexistences are supported:&lt;BR /&gt;MPIO FF for EVA 4k/6k/8k coexistence on the same server :&lt;BR /&gt;a) Secure Path, YES&lt;BR /&gt;b) HP MPIO Full Featured DSM for EVA3000/5000 VCS 4.xxx, YES&lt;BR /&gt;c) HP MPIO Full Featured DSM for MSA1000/1500&lt;BR /&gt;(Active-Active), YES&lt;BR /&gt;d) HP MPIO basic failover for EVA arrays, YES &lt;BR /&gt;e) HP MPIO basic failover for XP arrays, No&lt;BR /&gt;f) MS DSM, Yes&lt;BR /&gt;&lt;BR /&gt;</description>
      <pubDate>Mon, 16 Feb 2009 19:19:54 GMT</pubDate>
      <guid>https://community.hpe.com/t5/disk-enclosures/windows-boot-from-san-upgrade-basic-mpio-to-full-mpio/m-p/4359567#M30177</guid>
      <dc:creator>IBaltay</dc:creator>
      <dc:date>2009-02-16T19:19:54Z</dc:date>
    </item>
    <item>
      <title>Re: windows boot from SAN upgrade basic MPIO to full MPIO</title>
      <link>https://community.hpe.com/t5/disk-enclosures/windows-boot-from-san-upgrade-basic-mpio-to-full-mpio/m-p/4359568#M30178</link>
      <description>Thank both for your quick responses!&lt;BR /&gt;&lt;BR /&gt;So with both basic and full able to coexist in Windows at the same time, I should be able to:&lt;BR /&gt;&lt;BR /&gt;Shutdown my blades&lt;BR /&gt;Perform the CA failover&lt;BR /&gt;Rezone and update Command View for the eva8100&lt;BR /&gt;Boot up the blades&lt;BR /&gt;Upgrade MPIO and reboot  &lt;BR /&gt;</description>
      <pubDate>Mon, 16 Feb 2009 19:24:54 GMT</pubDate>
      <guid>https://community.hpe.com/t5/disk-enclosures/windows-boot-from-san-upgrade-basic-mpio-to-full-mpio/m-p/4359568#M30178</guid>
      <dc:creator>mgtow</dc:creator>
      <dc:date>2009-02-16T19:24:54Z</dc:date>
    </item>
    <item>
      <title>Re: windows boot from SAN upgrade basic MPIO to full MPIO</title>
      <link>https://community.hpe.com/t5/disk-enclosures/windows-boot-from-san-upgrade-basic-mpio-to-full-mpio/m-p/4359569#M30179</link>
      <description>To reduce the downtime to minimum&lt;BR /&gt;&lt;BR /&gt;1. Add new host/eva8100 zones, update Command View for the eva8100&lt;BR /&gt;(online no downtime)&lt;BR /&gt;&lt;BR /&gt;2. install the MPIO FF (coexistence with the MPIO basic)&lt;BR /&gt;(online no downtime)&lt;BR /&gt;&lt;BR /&gt;3. Shutdown my blades&lt;BR /&gt;(short downtime)&lt;BR /&gt;&lt;BR /&gt;4. Perform the CA failover&lt;BR /&gt;(several minutes of downtime)&lt;BR /&gt;&lt;BR /&gt;5. Boot up the blades</description>
      <pubDate>Mon, 16 Feb 2009 19:32:11 GMT</pubDate>
      <guid>https://community.hpe.com/t5/disk-enclosures/windows-boot-from-san-upgrade-basic-mpio-to-full-mpio/m-p/4359569#M30179</guid>
      <dc:creator>IBaltay</dc:creator>
      <dc:date>2009-02-16T19:32:11Z</dc:date>
    </item>
    <item>
      <title>Re: windows boot from SAN upgrade basic MPIO to full MPIO</title>
      <link>https://community.hpe.com/t5/disk-enclosures/windows-boot-from-san-upgrade-basic-mpio-to-full-mpio/m-p/4359570#M30180</link>
      <description>Thanks</description>
      <pubDate>Mon, 16 Feb 2009 19:39:27 GMT</pubDate>
      <guid>https://community.hpe.com/t5/disk-enclosures/windows-boot-from-san-upgrade-basic-mpio-to-full-mpio/m-p/4359570#M30180</guid>
      <dc:creator>mgtow</dc:creator>
      <dc:date>2009-02-16T19:39:27Z</dc:date>
    </item>
  </channel>
</rss>

