<?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: Upgrade A3 cluster in ExtremeCloud A3</title>
    <link>https://community.extremenetworks.com/t5/extremecloud-a3/upgrade-a3-cluster/m-p/21298#M9</link>
    <description>There is no set time; it's a matter of what you are comfortable with and what your experience has been. In my own environment I simply turn on all three nodes in a cluster and allow it to converge - this is how it is designed. However granted there are issues from time to time so waiting until say the GUI of the first node is operational (i.e. you can log in) to wait to start the next node and so on is as arbitrary a wait period as any.&lt;BR /&gt;&lt;BR /&gt;I run / start the upgrade from the VIP, which is to say you run / start it from the Master member of the cluster. The upgrade runs in consecutively; and if memory serves it is a member node first, restarted following by the next member node, followed by the master... but don't quote me.&lt;BR /&gt;&lt;BR /&gt;As for time - YMMV. On my 'fast' system ~ 20m for a cluster.. on my slow hypervisor... hour+.</description>
    <pubDate>Fri, 14 Jan 2022 22:25:00 GMT</pubDate>
    <dc:creator>Robert_Haynes</dc:creator>
    <dc:date>2022-01-14T22:25:00Z</dc:date>
    <item>
      <title>Upgrade A3 cluster</title>
      <link>https://community.extremenetworks.com/t5/extremecloud-a3/upgrade-a3-cluster/m-p/21295#M6</link>
      <description>I'm trying to upgrade my 3 node A3 cluster from v3.5 to v4.0, but can't find any procedure regarding the cluster upgrade.</description>
      <pubDate>Thu, 13 Jan 2022 17:22:00 GMT</pubDate>
      <guid>https://community.extremenetworks.com/t5/extremecloud-a3/upgrade-a3-cluster/m-p/21295#M6</guid>
      <dc:creator>MLD</dc:creator>
      <dc:date>2022-01-13T17:22:00Z</dc:date>
    </item>
    <item>
      <title>RE: Upgrade A3 cluster</title>
      <link>https://community.extremenetworks.com/t5/extremecloud-a3/upgrade-a3-cluster/m-p/21296#M7</link>
      <description>Hello.&lt;BR /&gt;&lt;BR /&gt;The upgrade procedure is fairly straightforward.&lt;BR /&gt;&lt;BR /&gt;It would be recommended to power down the cluster first, the member nodes before the master. Once offline, take snapshots of the appliances for any disaster recovery type scenario.&lt;BR /&gt;Bring the cluster back online.&lt;BR /&gt;You would then log in, click on the tools icon (wrench/screwdriver icon) and select "Update software".&lt;BR /&gt;It should say 4.0 is available. Proceed with the upgrade.</description>
      <pubDate>Fri, 14 Jan 2022 20:36:00 GMT</pubDate>
      <guid>https://community.extremenetworks.com/t5/extremecloud-a3/upgrade-a3-cluster/m-p/21296#M7</guid>
      <dc:creator>Robert_Haynes</dc:creator>
      <dc:date>2022-01-14T20:36:00Z</dc:date>
    </item>
    <item>
      <title>RE: Upgrade A3 cluster</title>
      <link>https://community.extremenetworks.com/t5/extremecloud-a3/upgrade-a3-cluster/m-p/21297#M8</link>
      <description>How long should I wait between each node powering up (master first). &lt;BR /&gt;Can I run the update using the cluster VIP or should I update each node. Can the update run on all 3 nodes at the same time and how long does it typically take. &lt;BR /&gt;&lt;BR /&gt;--&lt;BR /&gt;Thanks,&lt;BR /&gt;Matt</description>
      <pubDate>Fri, 14 Jan 2022 21:51:00 GMT</pubDate>
      <guid>https://community.extremenetworks.com/t5/extremecloud-a3/upgrade-a3-cluster/m-p/21297#M8</guid>
      <dc:creator>MLD</dc:creator>
      <dc:date>2022-01-14T21:51:00Z</dc:date>
    </item>
    <item>
      <title>RE: Upgrade A3 cluster</title>
      <link>https://community.extremenetworks.com/t5/extremecloud-a3/upgrade-a3-cluster/m-p/21298#M9</link>
      <description>There is no set time; it's a matter of what you are comfortable with and what your experience has been. In my own environment I simply turn on all three nodes in a cluster and allow it to converge - this is how it is designed. However granted there are issues from time to time so waiting until say the GUI of the first node is operational (i.e. you can log in) to wait to start the next node and so on is as arbitrary a wait period as any.&lt;BR /&gt;&lt;BR /&gt;I run / start the upgrade from the VIP, which is to say you run / start it from the Master member of the cluster. The upgrade runs in consecutively; and if memory serves it is a member node first, restarted following by the next member node, followed by the master... but don't quote me.&lt;BR /&gt;&lt;BR /&gt;As for time - YMMV. On my 'fast' system ~ 20m for a cluster.. on my slow hypervisor... hour+.</description>
      <pubDate>Fri, 14 Jan 2022 22:25:00 GMT</pubDate>
      <guid>https://community.extremenetworks.com/t5/extremecloud-a3/upgrade-a3-cluster/m-p/21298#M9</guid>
      <dc:creator>Robert_Haynes</dc:creator>
      <dc:date>2022-01-14T22:25:00Z</dc:date>
    </item>
  </channel>
</rss>

