<?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 Arbiter\Plugin version different from Nodes in HPE SimpliVity</title>
    <link>https://community.hpe.com/t5/hpe-simplivity/arbiter-plugin-version-different-from-nodes/m-p/7038889#M390</link>
    <description>&lt;P&gt;We have a big project this year moving a datacenter.&amp;nbsp; We currently have a bunch of Simplivity nodes on 3.7.4 and are ordering new nodes that we don't want to downgrade which we've had to do in the past.&amp;nbsp; Due to business reasons we can't have any maintenance windows for a couple more months to upgrade our Simplivity version.&amp;nbsp; Our current VCenter is on 6.5 but we are looking to deploy VCenter 6.7u1 in our new datacenter to support the upgraded Simplivity version.&lt;/P&gt;&lt;P&gt;What I'd like to do is upgrade the 6.5 version to 6.7u1 and then setup both VCenters in linked mode.&amp;nbsp; To do this I'm wondering if I could have the arbiter and plugin versions upgraded to the latest on both vcenter servers and then have our new nodes on the latest Simplivity but our existing nodes still on the old version until we can upgrade?&lt;/P&gt;&lt;P&gt;&amp;nbsp;&lt;/P&gt;</description>
    <pubDate>Tue, 19 Mar 2019 16:30:25 GMT</pubDate>
    <dc:creator>bbelew</dc:creator>
    <dc:date>2019-03-19T16:30:25Z</dc:date>
    <item>
      <title>Arbiter\Plugin version different from Nodes</title>
      <link>https://community.hpe.com/t5/hpe-simplivity/arbiter-plugin-version-different-from-nodes/m-p/7038889#M390</link>
      <description>&lt;P&gt;We have a big project this year moving a datacenter.&amp;nbsp; We currently have a bunch of Simplivity nodes on 3.7.4 and are ordering new nodes that we don't want to downgrade which we've had to do in the past.&amp;nbsp; Due to business reasons we can't have any maintenance windows for a couple more months to upgrade our Simplivity version.&amp;nbsp; Our current VCenter is on 6.5 but we are looking to deploy VCenter 6.7u1 in our new datacenter to support the upgraded Simplivity version.&lt;/P&gt;&lt;P&gt;What I'd like to do is upgrade the 6.5 version to 6.7u1 and then setup both VCenters in linked mode.&amp;nbsp; To do this I'm wondering if I could have the arbiter and plugin versions upgraded to the latest on both vcenter servers and then have our new nodes on the latest Simplivity but our existing nodes still on the old version until we can upgrade?&lt;/P&gt;&lt;P&gt;&amp;nbsp;&lt;/P&gt;</description>
      <pubDate>Tue, 19 Mar 2019 16:30:25 GMT</pubDate>
      <guid>https://community.hpe.com/t5/hpe-simplivity/arbiter-plugin-version-different-from-nodes/m-p/7038889#M390</guid>
      <dc:creator>bbelew</dc:creator>
      <dc:date>2019-03-19T16:30:25Z</dc:date>
    </item>
    <item>
      <title>Re: Arbiter\Plugin version different from Nodes</title>
      <link>https://community.hpe.com/t5/hpe-simplivity/arbiter-plugin-version-different-from-nodes/m-p/7039481#M394</link>
      <description>&lt;P&gt;You cannot deploy into a mixed version federation if your existing federation is 3.7.4 then all new nodes must be deployed at that version and then upgraded when your shedule allows.&lt;/P&gt;&lt;P&gt;"Downgrading" as such would be to install an&amp;nbsp; older&amp;nbsp; version of the deploy installer the easyest way to do this via physical usb.Talk to your deployment team to allow you to achive this in the most efficent way.&lt;/P&gt;&lt;P&gt;&amp;nbsp;&lt;/P&gt;</description>
      <pubDate>Sun, 24 Mar 2019 16:14:22 GMT</pubDate>
      <guid>https://community.hpe.com/t5/hpe-simplivity/arbiter-plugin-version-different-from-nodes/m-p/7039481#M394</guid>
      <dc:creator>DaveOb</dc:creator>
      <dc:date>2019-03-24T16:14:22Z</dc:date>
    </item>
  </channel>
</rss>

