<?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 Considerations for forming a SecureStack Mixed Stack in FAQs</title>
    <link>https://community.extremenetworks.com/t5/faqs/considerations-for-forming-a-securestack-mixed-stack/m-p/51771#M741</link>
    <description>Article ID: 12760 &lt;BR /&gt;
&lt;BR /&gt;
&lt;B&gt;Products&lt;/B&gt;&lt;BR /&gt;
SecureStack C3, C2&lt;BR /&gt;
SecureStack B3, B2 &lt;BR /&gt;
&lt;BR /&gt;
&lt;B&gt;Goals&lt;/B&gt;&lt;BR /&gt;
Combine multiple SecureStack C3 and SecureStack C2 units into a single "mixed" stack.&lt;BR /&gt;
Combine multiple SecureStack B3 and SecureStack B2 units into a single "mixed" stack. &lt;BR /&gt;
&lt;BR /&gt;
&lt;B&gt;Solution&lt;/B&gt;&lt;BR /&gt;
For the SecureStack stackable product line, permitted "mixed stack" combinations - C3&amp;lt;-&amp;gt;C2 and B3&amp;lt;-&amp;gt;B2 - are outlined in &lt;A href="http://bit.ly/1cGWsHh" target="_blank" rel="nofollow noreferrer noopener"&gt;5834&lt;/A&gt;. A broader process overview is provided in &lt;A href="http://bit.ly/1BetvzD" target="_blank" rel="nofollow noreferrer noopener"&gt;7086&lt;/A&gt;. &lt;BR /&gt;
&lt;BR /&gt;
All units must be running the same &lt;I&gt;x&lt;/I&gt;2 (C2 or B2, respectively) firmware version before being physically interconnected by stack cables, and an &lt;I&gt;x&lt;/I&gt;3 (C3 or B3, respectively) unit must ultimately be the stack manager. &lt;BR /&gt;
&lt;BR /&gt;
The procedure to integrate units of identical firmware version into a single stack is explained in &lt;A href="http://bit.ly/1BetvzD" target="_blank" rel="nofollow noreferrer noopener"&gt;7086&lt;/A&gt;, in one of these three sections, according to your needs: &lt;BR /&gt;
&lt;UL&gt; 
&lt;LI&gt;&lt;B&gt;Installing a New Stackable System of Up to Eight Units&lt;/B&gt; 
&lt;/LI&gt;&lt;LI&gt;&lt;B&gt;Installing a Previously-Configured System of Up to Eight Units&lt;/B&gt; 
&lt;/LI&gt;&lt;LI&gt;&lt;B&gt;Adding a New Unit to an Existing Stack&lt;/B&gt;&lt;/LI&gt;&lt;/UL&gt;
&lt;U&gt;Management failover&lt;/U&gt; &lt;BR /&gt;
If the C3 or B3 which has been assigned the stack manager role fails, there is no automated provision to ensure that any remaining C3 or B3 will pick up the role in its place, in preference to a C2 or B2. To assure failover to a C3 or B3 when such are available for this purpose, use the 'set switch &amp;lt;&lt;I&gt;unit#&lt;/I&gt;&amp;gt; priority 15' command (&lt;A href="http://bit.ly/1BetvzD" target="_blank" rel="nofollow noreferrer noopener"&gt;7086&lt;/A&gt;) to give all C3s or B3s a high management priority. &lt;BR /&gt;
&lt;BR /&gt;
&lt;U&gt;Licensing compatibility&lt;/U&gt; &lt;BR /&gt;
* When running C2 firmware on a C3; any previously installed C3L3-LIC (&lt;A href="http://bit.ly/18QSYzC" target="_blank" rel="nofollow noreferrer noopener"&gt;5828&lt;/A&gt;) and/or C3IPV6-LIC (&lt;A href="http://bit.ly/17r6HzV" target="_blank" rel="nofollow noreferrer noopener"&gt;5873&lt;/A&gt;) is functionally ignored though will appear in the output of a 'show license' command, and it is not possible to add or remove either of these licenses because the necessary C3 commands are not recognized. &lt;BR /&gt;
* When running B2 firmware on a B3; either a B3POL-LIC or B2POL-LIC may be used (&lt;A href="http://bit.ly/Ig6wNS" target="_blank" rel="nofollow noreferrer noopener"&gt;5781&lt;/A&gt;) - but not both within the same stack. As a corollary to this, a B3POL-LIC is not compatible with B2s in a mixed stack.&lt;BR /&gt;</description>
    <pubDate>Thu, 21 Nov 2013 07:50:00 GMT</pubDate>
    <dc:creator>FAQ_User</dc:creator>
    <dc:date>2013-11-21T07:50:00Z</dc:date>
    <item>
      <title>Considerations for forming a SecureStack Mixed Stack</title>
      <link>https://community.extremenetworks.com/t5/faqs/considerations-for-forming-a-securestack-mixed-stack/m-p/51771#M741</link>
      <description>Article ID: 12760 &lt;BR /&gt;
&lt;BR /&gt;
&lt;B&gt;Products&lt;/B&gt;&lt;BR /&gt;
SecureStack C3, C2&lt;BR /&gt;
SecureStack B3, B2 &lt;BR /&gt;
&lt;BR /&gt;
&lt;B&gt;Goals&lt;/B&gt;&lt;BR /&gt;
Combine multiple SecureStack C3 and SecureStack C2 units into a single "mixed" stack.&lt;BR /&gt;
Combine multiple SecureStack B3 and SecureStack B2 units into a single "mixed" stack. &lt;BR /&gt;
&lt;BR /&gt;
&lt;B&gt;Solution&lt;/B&gt;&lt;BR /&gt;
For the SecureStack stackable product line, permitted "mixed stack" combinations - C3&amp;lt;-&amp;gt;C2 and B3&amp;lt;-&amp;gt;B2 - are outlined in &lt;A href="http://bit.ly/1cGWsHh" target="_blank" rel="nofollow noreferrer noopener"&gt;5834&lt;/A&gt;. A broader process overview is provided in &lt;A href="http://bit.ly/1BetvzD" target="_blank" rel="nofollow noreferrer noopener"&gt;7086&lt;/A&gt;. &lt;BR /&gt;
&lt;BR /&gt;
All units must be running the same &lt;I&gt;x&lt;/I&gt;2 (C2 or B2, respectively) firmware version before being physically interconnected by stack cables, and an &lt;I&gt;x&lt;/I&gt;3 (C3 or B3, respectively) unit must ultimately be the stack manager. &lt;BR /&gt;
&lt;BR /&gt;
The procedure to integrate units of identical firmware version into a single stack is explained in &lt;A href="http://bit.ly/1BetvzD" target="_blank" rel="nofollow noreferrer noopener"&gt;7086&lt;/A&gt;, in one of these three sections, according to your needs: &lt;BR /&gt;
&lt;UL&gt; 
&lt;LI&gt;&lt;B&gt;Installing a New Stackable System of Up to Eight Units&lt;/B&gt; 
&lt;/LI&gt;&lt;LI&gt;&lt;B&gt;Installing a Previously-Configured System of Up to Eight Units&lt;/B&gt; 
&lt;/LI&gt;&lt;LI&gt;&lt;B&gt;Adding a New Unit to an Existing Stack&lt;/B&gt;&lt;/LI&gt;&lt;/UL&gt;
&lt;U&gt;Management failover&lt;/U&gt; &lt;BR /&gt;
If the C3 or B3 which has been assigned the stack manager role fails, there is no automated provision to ensure that any remaining C3 or B3 will pick up the role in its place, in preference to a C2 or B2. To assure failover to a C3 or B3 when such are available for this purpose, use the 'set switch &amp;lt;&lt;I&gt;unit#&lt;/I&gt;&amp;gt; priority 15' command (&lt;A href="http://bit.ly/1BetvzD" target="_blank" rel="nofollow noreferrer noopener"&gt;7086&lt;/A&gt;) to give all C3s or B3s a high management priority. &lt;BR /&gt;
&lt;BR /&gt;
&lt;U&gt;Licensing compatibility&lt;/U&gt; &lt;BR /&gt;
* When running C2 firmware on a C3; any previously installed C3L3-LIC (&lt;A href="http://bit.ly/18QSYzC" target="_blank" rel="nofollow noreferrer noopener"&gt;5828&lt;/A&gt;) and/or C3IPV6-LIC (&lt;A href="http://bit.ly/17r6HzV" target="_blank" rel="nofollow noreferrer noopener"&gt;5873&lt;/A&gt;) is functionally ignored though will appear in the output of a 'show license' command, and it is not possible to add or remove either of these licenses because the necessary C3 commands are not recognized. &lt;BR /&gt;
* When running B2 firmware on a B3; either a B3POL-LIC or B2POL-LIC may be used (&lt;A href="http://bit.ly/Ig6wNS" target="_blank" rel="nofollow noreferrer noopener"&gt;5781&lt;/A&gt;) - but not both within the same stack. As a corollary to this, a B3POL-LIC is not compatible with B2s in a mixed stack.&lt;BR /&gt;</description>
      <pubDate>Thu, 21 Nov 2013 07:50:00 GMT</pubDate>
      <guid>https://community.extremenetworks.com/t5/faqs/considerations-for-forming-a-securestack-mixed-stack/m-p/51771#M741</guid>
      <dc:creator>FAQ_User</dc:creator>
      <dc:date>2013-11-21T07:50:00Z</dc:date>
    </item>
  </channel>
</rss>

