<?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 SimpliVity 5.2 cluster deployment in HPE SimpliVity</title>
    <link>https://community.hpe.com/t5/hpe-simplivity/simplivity-5-2-cluster-deployment/m-p/7235660#M5261</link>
    <description>&lt;P&gt;hi&lt;/P&gt;&lt;P&gt;I will be deplying a new SimpliVity cluster into an existing federation consisting of several clusters running ESXi 7.0U3r, vCenter 7.0U3t and SimpliVity version 4.1.2. All existing clusters share a single arbiter instance&lt;/P&gt;&lt;P&gt;The new cluster is to run SimpliVity 5.2.0 - which I see is compatible with vCenter 7.0U3t and can co-exist within a federation with 4.1.2 clusters.&lt;/P&gt;&lt;P&gt;I have three questions:&lt;/P&gt;&lt;P&gt;Will backups successfully run between the old 4.1.2 clusters to the new 5.2.0 cluster (both directions)?&lt;/P&gt;&lt;P&gt;As my vCenter is only running 7.0U3t I need to run ESXi 7.0.U3r on the new hosts - this is simply done by ensuring I have the&amp;nbsp;ESXi 7.0.U3r offline package within the Deployment Manager directory and select this when deploying??&lt;/P&gt;&lt;P&gt;I will also need to update the arbiter and the vcenter plugin to the 5.2.0 versions??&lt;/P&gt;&lt;P&gt;thanks&lt;/P&gt;</description>
    <pubDate>Mon, 03 Mar 2025 13:46:56 GMT</pubDate>
    <dc:creator>CadenLange</dc:creator>
    <dc:date>2025-03-03T13:46:56Z</dc:date>
    <item>
      <title>SimpliVity 5.2 cluster deployment</title>
      <link>https://community.hpe.com/t5/hpe-simplivity/simplivity-5-2-cluster-deployment/m-p/7235660#M5261</link>
      <description>&lt;P&gt;hi&lt;/P&gt;&lt;P&gt;I will be deplying a new SimpliVity cluster into an existing federation consisting of several clusters running ESXi 7.0U3r, vCenter 7.0U3t and SimpliVity version 4.1.2. All existing clusters share a single arbiter instance&lt;/P&gt;&lt;P&gt;The new cluster is to run SimpliVity 5.2.0 - which I see is compatible with vCenter 7.0U3t and can co-exist within a federation with 4.1.2 clusters.&lt;/P&gt;&lt;P&gt;I have three questions:&lt;/P&gt;&lt;P&gt;Will backups successfully run between the old 4.1.2 clusters to the new 5.2.0 cluster (both directions)?&lt;/P&gt;&lt;P&gt;As my vCenter is only running 7.0U3t I need to run ESXi 7.0.U3r on the new hosts - this is simply done by ensuring I have the&amp;nbsp;ESXi 7.0.U3r offline package within the Deployment Manager directory and select this when deploying??&lt;/P&gt;&lt;P&gt;I will also need to update the arbiter and the vcenter plugin to the 5.2.0 versions??&lt;/P&gt;&lt;P&gt;thanks&lt;/P&gt;</description>
      <pubDate>Mon, 03 Mar 2025 13:46:56 GMT</pubDate>
      <guid>https://community.hpe.com/t5/hpe-simplivity/simplivity-5-2-cluster-deployment/m-p/7235660#M5261</guid>
      <dc:creator>CadenLange</dc:creator>
      <dc:date>2025-03-03T13:46:56Z</dc:date>
    </item>
    <item>
      <title>Re: SimpliVity 5.2 cluster deployment</title>
      <link>https://community.hpe.com/t5/hpe-simplivity/simplivity-5-2-cluster-deployment/m-p/7236027#M5268</link>
      <description>&lt;P dir="auto" style="margin: 0;"&gt;Thank you for reaching out.&amp;nbsp;&lt;/P&gt;
&lt;P dir="auto" style="margin: 0;"&gt;&amp;nbsp;&lt;/P&gt;
&lt;P dir="auto" style="margin: 0;"&gt;&amp;nbsp;&lt;/P&gt;
&lt;P dir="auto" style="margin: 0;"&gt;&lt;BR /&gt;These were all pulled from our HPE OmniStack 5.2.0 for vSphere Upgrade Guide located at:&amp;nbsp;&lt;BR /&gt;&lt;A href="https://support.hpe.com/hpesc/public/docDisplay?docId=sd00005177en_us&amp;amp;page=index.html" target="_blank"&gt;https://support.hpe.com/hpesc/public/docDisplay?docId=sd00005177en_us&amp;amp;page=index.html&lt;/A&gt;&lt;BR /&gt;&lt;A href="https://support.hpe.com/hpesc/public/docDisplay?docLocale=en_US&amp;amp;docId=sd00005177en_us" target="_blank"&gt;https://support.hpe.com/hpesc/public/docDisplay?docLocale=en_US&amp;amp;docId=sd00005177en_us&lt;/A&gt;&lt;/P&gt;
&lt;P dir="auto" style="margin: 0;"&gt;Keep in mind:&amp;nbsp;&lt;BR /&gt;Compatible = "Compatible Version but not explicitly verified"&lt;/P&gt;
&lt;P dir="auto" style="margin: 0;"&gt;1. - &lt;EM&gt;&lt;STRONG&gt;Will backups successfully run between the old 4.1.2 clusters to the new 5.2.0 cluster (both directions)?&lt;/STRONG&gt;&lt;/EM&gt;&lt;BR /&gt;Concerns here: old 4.1.2 clusters ; Inactive as of 28 Mar 2024&lt;BR /&gt;They should but for best performance supported versions of SimpliVity are recommended.&amp;nbsp;&lt;/P&gt;
&lt;P dir="auto" style="margin: 0;"&gt;&lt;BR /&gt;2. - &lt;EM&gt;&lt;STRONG&gt;As my vCenter is only running 7.0U3t I need to run ESXi 7.0.U3r on the new hosts - this is simply done by ensuring I have the ESXi 7.0.U3r offline package within the Deployment Manager directory and select this when deploying??&lt;/STRONG&gt;&lt;/EM&gt;&lt;BR /&gt;"Download the HPE SimpliVity Upgrade Package zip file from the HPE SimpliVity OmniStack Software for VMware vSphere product page of My HPE Software Center (&lt;A href="https://www.hpe.com/software/hpesoftwarecenter" target="_blank"&gt;https://www.hpe.com/software/hpesoftwarecenter&lt;/A&gt;) and save the file in the same directory on the computer that is local to the hosts you want to upgrade."&lt;/P&gt;
&lt;P dir="auto" style="margin: 0;"&gt;&amp;amp;&amp;amp;&amp;nbsp;&lt;/P&gt;
&lt;P dir="auto" style="margin: 0;"&gt;"If upgrading the VMware ESXi software, download the zipped upgrade bundle from the HPE SimpliVity Custom ESXi offline bundle product page, and the zipped Interop Catalog bundle from the HPE SimpliVity OmniStack Interop Catalog product page of the My HPE Software Center (&lt;A href="https://www.hpe.com/software/hpesoftwarecenter" target="_blank"&gt;https://www.hpe.com/software/hpesoftwarecenter&lt;/A&gt;) and save them in the same directory. You must extract the contents of the HPE SimpliVity InterOp Catalog bundle in the same directory."&lt;/P&gt;
&lt;P dir="auto" style="margin: 0;"&gt;&lt;BR /&gt;3. - &lt;EM&gt;&lt;STRONG&gt;I will also need to update the arbiter and the vcenter plugin to the 5.2.0 versions?? thanks - 5387973746&lt;/STRONG&gt;&lt;/EM&gt;&lt;BR /&gt;"If upgrading the HPE OmniStack software, upgrade the Arbiter software (without removing the current version) to the same version of the HPE OmniStack software that you plan to use for the upgrade. The Arbiter and HPE OmniStack software versions must match to complete the upgrade."&lt;/P&gt;
&lt;P dir="auto" style="margin: 0;"&gt;&amp;amp;&amp;amp;&lt;/P&gt;
&lt;P dir="auto" style="margin: 0;"&gt;"Install (or upgrade) HPE SimpliVity Plug-in for vSphere Client on your vCenter Server to check your current HPE OmniStack and ESXi versions."&lt;/P&gt;</description>
      <pubDate>Tue, 25 Feb 2025 18:43:03 GMT</pubDate>
      <guid>https://community.hpe.com/t5/hpe-simplivity/simplivity-5-2-cluster-deployment/m-p/7236027#M5268</guid>
      <dc:creator>Joshua610</dc:creator>
      <dc:date>2025-02-25T18:43:03Z</dc:date>
    </item>
    <item>
      <title>Re: SimpliVity 5.2 cluster deployment</title>
      <link>https://community.hpe.com/t5/hpe-simplivity/simplivity-5-2-cluster-deployment/m-p/7236214#M5272</link>
      <description>&lt;P dir="auto" style="margin: 0;"&gt;I am following up to see if any further questions regarding 5.2 Cluster deployment. If not would we be in the position to archive this case?&amp;nbsp;&lt;/P&gt;</description>
      <pubDate>Thu, 27 Feb 2025 14:26:19 GMT</pubDate>
      <guid>https://community.hpe.com/t5/hpe-simplivity/simplivity-5-2-cluster-deployment/m-p/7236214#M5272</guid>
      <dc:creator>Joshua610</dc:creator>
      <dc:date>2025-02-27T14:26:19Z</dc:date>
    </item>
    <item>
      <title>Re: SimpliVity 5.2 cluster deployment</title>
      <link>https://community.hpe.com/t5/hpe-simplivity/simplivity-5-2-cluster-deployment/m-p/7236363#M5273</link>
      <description>&lt;P dir="auto" style="margin: 0;"&gt;I am following up to see if any further questions regarding 5.2 Cluster deployment. If not would we be in the position to archive this case?&amp;nbsp;&lt;/P&gt;</description>
      <pubDate>Fri, 28 Feb 2025 18:24:05 GMT</pubDate>
      <guid>https://community.hpe.com/t5/hpe-simplivity/simplivity-5-2-cluster-deployment/m-p/7236363#M5273</guid>
      <dc:creator>Joshua610</dc:creator>
      <dc:date>2025-02-28T18:24:05Z</dc:date>
    </item>
    <item>
      <title>Re: SimpliVity 5.2 cluster deployment</title>
      <link>https://community.hpe.com/t5/hpe-simplivity/simplivity-5-2-cluster-deployment/m-p/7236440#M5277</link>
      <description>&lt;P&gt;Hi Joshua&lt;/P&gt;&lt;P&gt;Many thanks and sorry for the late response&lt;/P&gt;</description>
      <pubDate>Mon, 03 Mar 2025 08:19:21 GMT</pubDate>
      <guid>https://community.hpe.com/t5/hpe-simplivity/simplivity-5-2-cluster-deployment/m-p/7236440#M5277</guid>
      <dc:creator>CadenLange</dc:creator>
      <dc:date>2025-03-03T08:19:21Z</dc:date>
    </item>
    <item>
      <title>Re: SimpliVity 5.2 cluster deployment</title>
      <link>https://community.hpe.com/t5/hpe-simplivity/simplivity-5-2-cluster-deployment/m-p/7236518#M5278</link>
      <description>&lt;P&gt;Hello&amp;nbsp;&lt;a href="https://community.hpe.com/t5/user/viewprofilepage/user-id/2004946"&gt;@CadenLange&lt;/a&gt;,&amp;nbsp;&lt;/P&gt;
&lt;P&gt;Awesome!&amp;nbsp;&lt;/P&gt;
&lt;P&gt;We are glad to know your concern has been addressed.&amp;nbsp;&lt;/P&gt;</description>
      <pubDate>Tue, 04 Mar 2025 06:48:52 GMT</pubDate>
      <guid>https://community.hpe.com/t5/hpe-simplivity/simplivity-5-2-cluster-deployment/m-p/7236518#M5278</guid>
      <dc:creator>Sunitha_Mod</dc:creator>
      <dc:date>2025-03-04T06:48:52Z</dc:date>
    </item>
  </channel>
</rss>

