<?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 Upgrade firmware on EAPS Master in ExtremeSwitching (EXOS/Switch Engine)</title>
    <link>https://community.extremenetworks.com/t5/extremeswitching-exos-switch/upgrade-firmware-on-eaps-master/m-p/43282#M10403</link>
    <description>I need to upgrade the firmware on my EAPS Master which is a stack of 2 - X450-G2-48p's. When I reboot the stack how will the ring be affected? Should I remove the uplinks from the switches prior too, do the upgrade and reboot off network then plug it back into the network? &lt;BR /&gt;
&lt;BR /&gt;
Just curious how the ring will behave when the Master goes down.</description>
    <pubDate>Wed, 11 Jul 2018 21:47:00 GMT</pubDate>
    <dc:creator>DH1</dc:creator>
    <dc:date>2018-07-11T21:47:00Z</dc:date>
    <item>
      <title>Upgrade firmware on EAPS Master</title>
      <link>https://community.extremenetworks.com/t5/extremeswitching-exos-switch/upgrade-firmware-on-eaps-master/m-p/43282#M10403</link>
      <description>I need to upgrade the firmware on my EAPS Master which is a stack of 2 - X450-G2-48p's. When I reboot the stack how will the ring be affected? Should I remove the uplinks from the switches prior too, do the upgrade and reboot off network then plug it back into the network? &lt;BR /&gt;
&lt;BR /&gt;
Just curious how the ring will behave when the Master goes down.</description>
      <pubDate>Wed, 11 Jul 2018 21:47:00 GMT</pubDate>
      <guid>https://community.extremenetworks.com/t5/extremeswitching-exos-switch/upgrade-firmware-on-eaps-master/m-p/43282#M10403</guid>
      <dc:creator>DH1</dc:creator>
      <dc:date>2018-07-11T21:47:00Z</dc:date>
    </item>
    <item>
      <title>RE: Upgrade firmware on EAPS Master</title>
      <link>https://community.extremenetworks.com/t5/extremeswitching-exos-switch/upgrade-firmware-on-eaps-master/m-p/43283#M10404</link>
      <description>You can just upgrade the stack. The other ringswitches won't be affected. They just don't see the hellos from the master anymore and may go into a ring failed state. But this has no effect on the data forwarding. As the master owns the blocked port, there will also be no flush fdb. Obviously anything connected to the master driectly will loose connection.&lt;BR /&gt;</description>
      <pubDate>Wed, 11 Jul 2018 22:44:00 GMT</pubDate>
      <guid>https://community.extremenetworks.com/t5/extremeswitching-exos-switch/upgrade-firmware-on-eaps-master/m-p/43283#M10404</guid>
      <dc:creator>AnonymousM</dc:creator>
      <dc:date>2018-07-11T22:44:00Z</dc:date>
    </item>
    <item>
      <title>RE: Upgrade firmware on EAPS Master</title>
      <link>https://community.extremenetworks.com/t5/extremeswitching-exos-switch/upgrade-firmware-on-eaps-master/m-p/43284#M10405</link>
      <description>I was able to update the firmware as you stated and all worked great. Thanks for the advice!</description>
      <pubDate>Wed, 18 Jul 2018 18:07:00 GMT</pubDate>
      <guid>https://community.extremenetworks.com/t5/extremeswitching-exos-switch/upgrade-firmware-on-eaps-master/m-p/43284#M10405</guid>
      <dc:creator>DH1</dc:creator>
      <dc:date>2018-07-18T18:07:00Z</dc:date>
    </item>
    <item>
      <title>RE: Upgrade firmware on EAPS Master</title>
      <link>https://community.extremenetworks.com/t5/extremeswitching-exos-switch/upgrade-firmware-on-eaps-master/m-p/43285#M10406</link>
      <description>You're welcome! &lt;span class="lia-unicode-emoji" title=":slightly_smiling_face:"&gt;🙂&lt;/span&gt;&lt;BR /&gt;</description>
      <pubDate>Wed, 18 Jul 2018 18:16:00 GMT</pubDate>
      <guid>https://community.extremenetworks.com/t5/extremeswitching-exos-switch/upgrade-firmware-on-eaps-master/m-p/43285#M10406</guid>
      <dc:creator>AnonymousM</dc:creator>
      <dc:date>2018-07-18T18:16:00Z</dc:date>
    </item>
  </channel>
</rss>

