<?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: 22.6.1.4 Auto Stacking in ExtremeSwitching (EXOS/Switch Engine)</title>
    <link>https://community.extremenetworks.com/t5/extremeswitching-exos-switch/22-6-1-4-auto-stacking/m-p/29871#M4969</link>
    <description>As I continue reading the release notes, I wonder if "checking during easy stacking setup" could behave the same way and simply create the stack without a backup?&lt;BR /&gt;
&lt;BR /&gt;
"ExtremeXOS 22.6 includes enhanced checking when executing easy stacking setup (configure stacking easy-setup). When using easy stacking setup, ExtremeXOS now checks: 1 ExtremeXOS selected partition on all nodes; if mismatch, warning message appears. 2 ExtremeXOS image version on selected partition on all nodes; if mismatch, warning message appears. 3 E&amp;#136;ective license level on master and backup nodes; if mismatch, set stacking license-level on the node of higher level with the lower level, and then continue with easy-setup. 4 Feature pack licenses on master and backup nodes; if mismatch, warning message appears, and the command is aborted. "&lt;BR /&gt;
&lt;BR /&gt;</description>
    <pubDate>Wed, 19 Sep 2018 22:19:00 GMT</pubDate>
    <dc:creator>davidj_cogliane</dc:creator>
    <dc:date>2018-09-19T22:19:00Z</dc:date>
    <item>
      <title>22.6.1.4 Auto Stacking</title>
      <link>https://community.extremenetworks.com/t5/extremeswitching-exos-switch/22-6-1-4-auto-stacking/m-p/29868#M4966</link>
      <description>Looking for other people experiences and reporting my test results below.&lt;BR /&gt;
&lt;BR /&gt;
First tests who that auto  stacking is pretty cool and works well.&lt;BR /&gt;
&lt;BR /&gt;
     &lt;BR /&gt;
&lt;BR /&gt;
    I stacked a single X450-G2 and  let it run. I then connected a second X450-G2 with stack cables and powered it  on. The stacked switched added the second switch to the stack and upgraded the  firmware to match what was installed on the master.&lt;BR /&gt;
&lt;BR /&gt;
     &lt;BR /&gt;
&lt;BR /&gt;
    Next I unplugged the stack  cables and connected the master to a different X450-G2 to simulate replacing a  failed slot. The master added the new switch as slot 2 and upgraded its  firmware just as it did with the first switch.&lt;BR /&gt;
&lt;BR /&gt;
     &lt;BR /&gt;
&lt;BR /&gt;
    Unfortunatly adding a trial  license to the master switch causes the second switch to come up with a role of  “none” I had hoped it would make the second switch a standby node that could  easily have its license upgraded… &lt;BR /&gt;
&lt;BR /&gt;
Do we know the expected behavior in case of a license mismatch?</description>
      <pubDate>Wed, 19 Sep 2018 21:52:00 GMT</pubDate>
      <guid>https://community.extremenetworks.com/t5/extremeswitching-exos-switch/22-6-1-4-auto-stacking/m-p/29868#M4966</guid>
      <dc:creator>davidj_cogliane</dc:creator>
      <dc:date>2018-09-19T21:52:00Z</dc:date>
    </item>
    <item>
      <title>RE: 22.6.1.4 Auto Stacking</title>
      <link>https://community.extremenetworks.com/t5/extremeswitching-exos-switch/22-6-1-4-auto-stacking/m-p/29869#M4967</link>
      <description>Thanks for the feedback.&lt;BR /&gt;
&lt;BR /&gt;
If a switch is added and is the backup switch, the licenses must match the master. If the licenses do not match, then the backup switch is not allowed to join the stack.&lt;BR /&gt;
During the EXOS 22.6 release training, our GTAC team suggested that if a backup switch has mismatched licenses, just let it join the stack as standby.&lt;BR /&gt;
Base license mismatch and feature license mismatch cause this behavior.&lt;BR /&gt;
&lt;BR /&gt;
I can update the feature to switch to standby and post it to github, which means downloading the updated feature to your switch, (not the full EXOS, just the auto stacking part. Internally it's called ztpstack)&lt;BR /&gt;
&lt;BR /&gt;
or just tweak for the next EXOS release&lt;BR /&gt;
&lt;BR /&gt;
or leave it as it is as an indication that the backup licenses need to be updated</description>
      <pubDate>Wed, 19 Sep 2018 22:19:00 GMT</pubDate>
      <guid>https://community.extremenetworks.com/t5/extremeswitching-exos-switch/22-6-1-4-auto-stacking/m-p/29869#M4967</guid>
      <dc:creator>Dave_Hammers</dc:creator>
      <dc:date>2018-09-19T22:19:00Z</dc:date>
    </item>
    <item>
      <title>RE: 22.6.1.4 Auto Stacking</title>
      <link>https://community.extremenetworks.com/t5/extremeswitching-exos-switch/22-6-1-4-auto-stacking/m-p/29870#M4968</link>
      <description>It would be great if it could make the switch a standby in the case of a license mismatch in the next release. I was simply doing some testing in the lab and wanted to see how it behaved.&lt;BR /&gt;
&lt;BR /&gt;
Thanks,</description>
      <pubDate>Wed, 19 Sep 2018 22:19:00 GMT</pubDate>
      <guid>https://community.extremenetworks.com/t5/extremeswitching-exos-switch/22-6-1-4-auto-stacking/m-p/29870#M4968</guid>
      <dc:creator>davidj_cogliane</dc:creator>
      <dc:date>2018-09-19T22:19:00Z</dc:date>
    </item>
    <item>
      <title>RE: 22.6.1.4 Auto Stacking</title>
      <link>https://community.extremenetworks.com/t5/extremeswitching-exos-switch/22-6-1-4-auto-stacking/m-p/29871#M4969</link>
      <description>As I continue reading the release notes, I wonder if "checking during easy stacking setup" could behave the same way and simply create the stack without a backup?&lt;BR /&gt;
&lt;BR /&gt;
"ExtremeXOS 22.6 includes enhanced checking when executing easy stacking setup (configure stacking easy-setup). When using easy stacking setup, ExtremeXOS now checks: 1 ExtremeXOS selected partition on all nodes; if mismatch, warning message appears. 2 ExtremeXOS image version on selected partition on all nodes; if mismatch, warning message appears. 3 E&amp;#136;ective license level on master and backup nodes; if mismatch, set stacking license-level on the node of higher level with the lower level, and then continue with easy-setup. 4 Feature pack licenses on master and backup nodes; if mismatch, warning message appears, and the command is aborted. "&lt;BR /&gt;
&lt;BR /&gt;</description>
      <pubDate>Wed, 19 Sep 2018 22:19:00 GMT</pubDate>
      <guid>https://community.extremenetworks.com/t5/extremeswitching-exos-switch/22-6-1-4-auto-stacking/m-p/29871#M4969</guid>
      <dc:creator>davidj_cogliane</dc:creator>
      <dc:date>2018-09-19T22:19:00Z</dc:date>
    </item>
    <item>
      <title>RE: 22.6.1.4 Auto Stacking</title>
      <link>https://community.extremenetworks.com/t5/extremeswitching-exos-switch/22-6-1-4-auto-stacking/m-p/29872#M4970</link>
      <description>FYI, I've added the functionality for the next release that detects if a backup has mismatched licenses with the master, and changes the backup to standby.&lt;BR /&gt;
Thanks again for the feedback.&lt;BR /&gt;
&lt;BR /&gt;
Example log message:&lt;BR /&gt;
09/23/2018 20:19:49.59 &lt;I&gt; Slot-1: ztpstack: slot 2 : License mismatch with master. Disabling master capability&lt;BR /&gt;
&lt;BR /&gt;&lt;/I&gt;</description>
      <pubDate>Wed, 19 Sep 2018 22:19:00 GMT</pubDate>
      <guid>https://community.extremenetworks.com/t5/extremeswitching-exos-switch/22-6-1-4-auto-stacking/m-p/29872#M4970</guid>
      <dc:creator>Dave_Hammers</dc:creator>
      <dc:date>2018-09-19T22:19:00Z</dc:date>
    </item>
    <item>
      <title>RE: 22.6.1.4 Auto Stacking</title>
      <link>https://community.extremenetworks.com/t5/extremeswitching-exos-switch/22-6-1-4-auto-stacking/m-p/29873#M4971</link>
      <description>Great,&lt;BR /&gt;
&lt;BR /&gt;
Thanks for the update.</description>
      <pubDate>Wed, 19 Sep 2018 22:19:00 GMT</pubDate>
      <guid>https://community.extremenetworks.com/t5/extremeswitching-exos-switch/22-6-1-4-auto-stacking/m-p/29873#M4971</guid>
      <dc:creator>davidj_cogliane</dc:creator>
      <dc:date>2018-09-19T22:19:00Z</dc:date>
    </item>
  </channel>
</rss>

