<?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: Active/Active EVA8000 OpenVMS 7.3-2 in Operating System - OpenVMS</title>
    <link>https://community.hpe.com/t5/operating-system-openvms/active-active-eva8000-openvms-7-3-2/m-p/3958178#M82223</link>
    <description>Personally, I'd expect OpenVMS VAX V7.3-2 to V8.x to be equivalent to a minor upgrade.&lt;BR /&gt;&lt;BR /&gt;----&lt;BR /&gt;&lt;BR /&gt;Steve, of course, meant OpenVMS Alpha; there is no planned OpenVMS VAX V8.x release.&lt;BR /&gt;&lt;BR /&gt;I'd also agree that V7.3-2 --&amp;gt; V8.x is not as potentially treacherous as the traditional major version upgrade.&lt;BR /&gt;&lt;BR /&gt;-- Rob</description>
    <pubDate>Thu, 08 Mar 2007 18:05:44 GMT</pubDate>
    <dc:creator>Robert Brooks_1</dc:creator>
    <dc:date>2007-03-08T18:05:44Z</dc:date>
    <item>
      <title>Active/Active EVA8000 OpenVMS 7.3-2</title>
      <link>https://community.hpe.com/t5/operating-system-openvms/active-active-eva8000-openvms-7-3-2/m-p/3958170#M82215</link>
      <description>I have the possibility or accessesing our new EVA8000  - will my OpenVMS 7.3-2 be able to negotiate the Active/Active disks?</description>
      <pubDate>Thu, 08 Mar 2007 10:28:51 GMT</pubDate>
      <guid>https://community.hpe.com/t5/operating-system-openvms/active-active-eva8000-openvms-7-3-2/m-p/3958170#M82215</guid>
      <dc:creator>Karen Lee_3</dc:creator>
      <dc:date>2007-03-08T10:28:51Z</dc:date>
    </item>
    <item>
      <title>Re: Active/Active EVA8000 OpenVMS 7.3-2</title>
      <link>https://community.hpe.com/t5/operating-system-openvms/active-active-eva8000-openvms-7-3-2/m-p/3958171#M82216</link>
      <description>The "Multipath Enhancement for Active-Active Feature of EVA and MSA Controllers" appears to be what you want, and it's a V8.3 feature.  Haven't looked to see if it's been back-ported.&lt;BR /&gt;&lt;BR /&gt;OpenVMS Alpha V8.x isn't a major upgrade for an OpenVMS Alpha V7.x release.</description>
      <pubDate>Thu, 08 Mar 2007 10:49:54 GMT</pubDate>
      <guid>https://community.hpe.com/t5/operating-system-openvms/active-active-eva8000-openvms-7-3-2/m-p/3958171#M82216</guid>
      <dc:creator>Hoff</dc:creator>
      <dc:date>2007-03-08T10:49:54Z</dc:date>
    </item>
    <item>
      <title>Re: Active/Active EVA8000 OpenVMS 7.3-2</title>
      <link>https://community.hpe.com/t5/operating-system-openvms/active-active-eva8000-openvms-7-3-2/m-p/3958172#M82217</link>
      <description>my eva group presented a disk from the EVA8000 and I can mount it a write to it without a problem.  &lt;BR /&gt;&lt;BR /&gt;Is the enhancement just improvement in IO?</description>
      <pubDate>Thu, 08 Mar 2007 11:13:55 GMT</pubDate>
      <guid>https://community.hpe.com/t5/operating-system-openvms/active-active-eva8000-openvms-7-3-2/m-p/3958172#M82217</guid>
      <dc:creator>Karen Lee_3</dc:creator>
      <dc:date>2007-03-08T11:13:55Z</dc:date>
    </item>
    <item>
      <title>Re: Active/Active EVA8000 OpenVMS 7.3-2</title>
      <link>https://community.hpe.com/t5/operating-system-openvms/active-active-eva8000-openvms-7-3-2/m-p/3958173#M82218</link>
      <description>I've seen comments about OpenVMS v8.x not being a major release for Alpha.  I believe it but other who read the official words on this subject think otherwise.&lt;BR /&gt;&lt;BR /&gt;For many shops, there's a big difference in paperwork/approvals when moving from a v7 something to a v8 something.&lt;BR /&gt;&lt;BR /&gt;For a reference on this subject:&lt;BR /&gt;&lt;BR /&gt;&lt;A href="http://h71000.www7.hp.com/openvms/binary_compatibility.html" target="_blank"&gt;http://h71000.www7.hp.com/openvms/binary_compatibility.html&lt;/A&gt;&lt;BR /&gt;&lt;BR /&gt;Dave...&lt;BR /&gt;</description>
      <pubDate>Thu, 08 Mar 2007 11:22:16 GMT</pubDate>
      <guid>https://community.hpe.com/t5/operating-system-openvms/active-active-eva8000-openvms-7-3-2/m-p/3958173#M82218</guid>
      <dc:creator>Dave Gudewicz</dc:creator>
      <dc:date>2007-03-08T11:22:16Z</dc:date>
    </item>
    <item>
      <title>Re: Active/Active EVA8000 OpenVMS 7.3-2</title>
      <link>https://community.hpe.com/t5/operating-system-openvms/active-active-eva8000-openvms-7-3-2/m-p/3958174#M82219</link>
      <description>&amp;gt; Is the enhancement just improvement in IO?&lt;BR /&gt;&lt;BR /&gt;Correct. The EVA 4000/6000/8000 provide asymmetric active/active support. It means that there is still one controller who owns a single virtual disk at a time and who does the I/O to the disk drives. If the non-owning controller receives an I/O request, it passes it on to the owning one - on the EVA 3000/5000 with active/passive failover it would have responded with a "NOT READY" status.&lt;BR /&gt;&lt;BR /&gt;OpenVMS was able to deal with A/P, but it was not able to find out the "performance path" on an A/A/A array. Of course, you were able to select it manually if you were familiar with the details...</description>
      <pubDate>Thu, 08 Mar 2007 13:20:27 GMT</pubDate>
      <guid>https://community.hpe.com/t5/operating-system-openvms/active-active-eva8000-openvms-7-3-2/m-p/3958174#M82219</guid>
      <dc:creator>Uwe Zessin</dc:creator>
      <dc:date>2007-03-08T13:20:27Z</dc:date>
    </item>
    <item>
      <title>Re: Active/Active EVA8000 OpenVMS 7.3-2</title>
      <link>https://community.hpe.com/t5/operating-system-openvms/active-active-eva8000-openvms-7-3-2/m-p/3958175#M82220</link>
      <description>VMS Alpha V8.2 is a major version update as far as the version number goes. However the internal changes between V7.3-2 and V8.2 are not big so its more like V7.4&lt;BR /&gt;&lt;BR /&gt;</description>
      <pubDate>Thu, 08 Mar 2007 14:41:43 GMT</pubDate>
      <guid>https://community.hpe.com/t5/operating-system-openvms/active-active-eva8000-openvms-7-3-2/m-p/3958175#M82220</guid>
      <dc:creator>Ian Miller.</dc:creator>
      <dc:date>2007-03-08T14:41:43Z</dc:date>
    </item>
    <item>
      <title>Re: Active/Active EVA8000 OpenVMS 7.3-2</title>
      <link>https://community.hpe.com/t5/operating-system-openvms/active-active-eva8000-openvms-7-3-2/m-p/3958176#M82221</link>
      <description>I was directly involved with the investigation for EVA Active/Active support within VMS Engineering.&lt;BR /&gt;&lt;BR /&gt;The I/O performance difference is *only* on read I/O (bearing in mind that most VMS systems  have a read/write I/O ratio of 75/25, or higher).&lt;BR /&gt;&lt;BR /&gt;The change made to support Active/Active on the various EVA controllers was contained in the SCSI Disk class driver SYS$DKDRIVER for V8.3 and was not backported&lt;BR /&gt;to any older version.&lt;BR /&gt;&lt;BR /&gt;&lt;BR /&gt;-- Rob</description>
      <pubDate>Thu, 08 Mar 2007 16:01:17 GMT</pubDate>
      <guid>https://community.hpe.com/t5/operating-system-openvms/active-active-eva8000-openvms-7-3-2/m-p/3958176#M82221</guid>
      <dc:creator>Robert Brooks_1</dc:creator>
      <dc:date>2007-03-08T16:01:17Z</dc:date>
    </item>
    <item>
      <title>Re: Active/Active EVA8000 OpenVMS 7.3-2</title>
      <link>https://community.hpe.com/t5/operating-system-openvms/active-active-eva8000-openvms-7-3-2/m-p/3958177#M82222</link>
      <description>I'm likely the guy that wrote the text that led to that binary_compatibility.html document, FWIW.  That text looks really familiar.&lt;BR /&gt;&lt;BR /&gt;The text is correct in as far as it goes, but there are other cases where a version number gets bumped for other reasons.  OpenVMS Alpha V8.0, for instance, was not a traditional upgrade.  V7.0 was a major release, however.&lt;BR /&gt;&lt;BR /&gt;The V6.x to V7.x upgrade on OpenVMS VAX was not a traditional major release upgrade, either.  V7.0 may well have arguably ended up as OpenVMS VAX V6.3.&lt;BR /&gt;&lt;BR /&gt;There's potentially more automated approach around verification.  It involves mapping the kernel API versions against the image header references for same.  (I should create a VerifyUpgrade tool to do this; that would not seem particularly difficult, but would seem useful.)  &lt;BR /&gt;&lt;BR /&gt;There have been kernel changes in mid-release, there was a TQE structural change around V7.3-1, for instance -- the old linked list became a tree structure at V7.3-1.  So you can find kernel changes even in minor and even in dash releases.&lt;BR /&gt;&lt;BR /&gt;Personally, I'd expect OpenVMS VAX V7.3-2 to V8.x to be equivalent to a minor upgrade.&lt;BR /&gt;&lt;BR /&gt;</description>
      <pubDate>Thu, 08 Mar 2007 17:06:47 GMT</pubDate>
      <guid>https://community.hpe.com/t5/operating-system-openvms/active-active-eva8000-openvms-7-3-2/m-p/3958177#M82222</guid>
      <dc:creator>Hoff</dc:creator>
      <dc:date>2007-03-08T17:06:47Z</dc:date>
    </item>
    <item>
      <title>Re: Active/Active EVA8000 OpenVMS 7.3-2</title>
      <link>https://community.hpe.com/t5/operating-system-openvms/active-active-eva8000-openvms-7-3-2/m-p/3958178#M82223</link>
      <description>Personally, I'd expect OpenVMS VAX V7.3-2 to V8.x to be equivalent to a minor upgrade.&lt;BR /&gt;&lt;BR /&gt;----&lt;BR /&gt;&lt;BR /&gt;Steve, of course, meant OpenVMS Alpha; there is no planned OpenVMS VAX V8.x release.&lt;BR /&gt;&lt;BR /&gt;I'd also agree that V7.3-2 --&amp;gt; V8.x is not as potentially treacherous as the traditional major version upgrade.&lt;BR /&gt;&lt;BR /&gt;-- Rob</description>
      <pubDate>Thu, 08 Mar 2007 18:05:44 GMT</pubDate>
      <guid>https://community.hpe.com/t5/operating-system-openvms/active-active-eva8000-openvms-7-3-2/m-p/3958178#M82223</guid>
      <dc:creator>Robert Brooks_1</dc:creator>
      <dc:date>2007-03-08T18:05:44Z</dc:date>
    </item>
    <item>
      <title>Re: Active/Active EVA8000 OpenVMS 7.3-2</title>
      <link>https://community.hpe.com/t5/operating-system-openvms/active-active-eva8000-openvms-7-3-2/m-p/3958179#M82224</link>
      <description>&amp;gt; The I/O performance difference is *only* on read I/O&lt;BR /&gt;&lt;BR /&gt;Yes, sure. For write I/O the data always goes across one of the mirror ports. If the I/O goes to the non-owning controller, it is sent to the owning one to do the physical I/O. If the I/O goes to the owning one, it is set to the non-owning controller to be saved in the cache-mirror.</description>
      <pubDate>Fri, 09 Mar 2007 00:52:22 GMT</pubDate>
      <guid>https://community.hpe.com/t5/operating-system-openvms/active-active-eva8000-openvms-7-3-2/m-p/3958179#M82224</guid>
      <dc:creator>Uwe Zessin</dc:creator>
      <dc:date>2007-03-09T00:52:22Z</dc:date>
    </item>
  </channel>
</rss>

