<?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 Replacing a failed Summit X450 in a stack in ExtremeSwitching (EXOS/Switch Engine)</title>
    <link>https://community.extremenetworks.com/t5/extremeswitching-exos-switch/replacing-a-failed-summit-x450-in-a-stack/m-p/53566#M15101</link>
    <description>Create Date: Sep  3 2013  5:28PM&lt;BR /&gt;
&lt;BR /&gt;
Just hoping I could get a pointed in the correct direction.  I have about 20 closets with mostly x450's in virtual stacks.  For the most part they have been stable and running without issues.  We have had to add additional switches a few times and I have a process for that which works well.  I have been tasked to write up a new procedure for if and when a X450 fails in one of the stacks, and how to replace it with as little downtime as possible.&lt;BR /&gt;
Have done some searches both with Google, and on Extreme support and have not found much of what I'm looking for yet.&lt;BR /&gt;
&lt;BR /&gt;
I assume the commands are very similar to adding a new switch to the stack.&lt;BR /&gt;
&lt;BR /&gt;
1)  Make sure software and licenses match&lt;BR /&gt;
2)  Swap out the failed switch with new switch and connect stacking cables&lt;BR /&gt;
3)  Console into master switch and issue command "synchronize stacking node-address (Mac of new switch)"&lt;BR /&gt;
4)  Issue the next command "configure stacking node-address (Mac of new switch) slot-number (slot of failed switch)&lt;BR /&gt;
5) restart the new switch only&lt;BR /&gt;
&lt;BR /&gt;
Is this the correct sequence of commands?  It is very similar to what we use when adding a new switch to a stack, and I thought the process would be very identical.  Unfortunately I don't have a couple of spares to use as a test either.&lt;BR /&gt;
&lt;BR /&gt;
Thanks for any help!  (from Sam_Perkins)</description>
    <pubDate>Wed, 08 Jan 2014 06:05:00 GMT</pubDate>
    <dc:creator>EtherNation_Use</dc:creator>
    <dc:date>2014-01-08T06:05:00Z</dc:date>
    <item>
      <title>Replacing a failed Summit X450 in a stack</title>
      <link>https://community.extremenetworks.com/t5/extremeswitching-exos-switch/replacing-a-failed-summit-x450-in-a-stack/m-p/53566#M15101</link>
      <description>Create Date: Sep  3 2013  5:28PM&lt;BR /&gt;
&lt;BR /&gt;
Just hoping I could get a pointed in the correct direction.  I have about 20 closets with mostly x450's in virtual stacks.  For the most part they have been stable and running without issues.  We have had to add additional switches a few times and I have a process for that which works well.  I have been tasked to write up a new procedure for if and when a X450 fails in one of the stacks, and how to replace it with as little downtime as possible.&lt;BR /&gt;
Have done some searches both with Google, and on Extreme support and have not found much of what I'm looking for yet.&lt;BR /&gt;
&lt;BR /&gt;
I assume the commands are very similar to adding a new switch to the stack.&lt;BR /&gt;
&lt;BR /&gt;
1)  Make sure software and licenses match&lt;BR /&gt;
2)  Swap out the failed switch with new switch and connect stacking cables&lt;BR /&gt;
3)  Console into master switch and issue command "synchronize stacking node-address (Mac of new switch)"&lt;BR /&gt;
4)  Issue the next command "configure stacking node-address (Mac of new switch) slot-number (slot of failed switch)&lt;BR /&gt;
5) restart the new switch only&lt;BR /&gt;
&lt;BR /&gt;
Is this the correct sequence of commands?  It is very similar to what we use when adding a new switch to a stack, and I thought the process would be very identical.  Unfortunately I don't have a couple of spares to use as a test either.&lt;BR /&gt;
&lt;BR /&gt;
Thanks for any help!  (from Sam_Perkins)</description>
      <pubDate>Wed, 08 Jan 2014 06:05:00 GMT</pubDate>
      <guid>https://community.extremenetworks.com/t5/extremeswitching-exos-switch/replacing-a-failed-summit-x450-in-a-stack/m-p/53566#M15101</guid>
      <dc:creator>EtherNation_Use</dc:creator>
      <dc:date>2014-01-08T06:05:00Z</dc:date>
    </item>
    <item>
      <title>RE: Replacing a failed Summit X450 in a stack</title>
      <link>https://community.extremenetworks.com/t5/extremeswitching-exos-switch/replacing-a-failed-summit-x450-in-a-stack/m-p/53567#M15102</link>
      <description>Create Date: Sep  4 2013  6:13AM&lt;BR /&gt;
&lt;BR /&gt;
Can't check this, but I think that you need enable stacking on new sw before restart   (from pacan4ik1_pacan4ik1)</description>
      <pubDate>Wed, 08 Jan 2014 06:05:00 GMT</pubDate>
      <guid>https://community.extremenetworks.com/t5/extremeswitching-exos-switch/replacing-a-failed-summit-x450-in-a-stack/m-p/53567#M15102</guid>
      <dc:creator>EtherNation_Use</dc:creator>
      <dc:date>2014-01-08T06:05:00Z</dc:date>
    </item>
    <item>
      <title>RE: Replacing a failed Summit X450 in a stack</title>
      <link>https://community.extremenetworks.com/t5/extremeswitching-exos-switch/replacing-a-failed-summit-x450-in-a-stack/m-p/53568#M15103</link>
      <description>Create Date: Sep  7 2013  1:54AM&lt;BR /&gt;
&lt;BR /&gt;
Here's a guide on how to replace the Master Node in a stack with minimal impact on the operation of the stack. It may be a good guide for what you are trying to do...&lt;BR /&gt;
https://www.dropbox.com/s/ut6ijijshbolnuv/Tech%20Guide%20EXOS%20Stacking%20Master%20Node%20Replacement%20v1.pdf&lt;BR /&gt;
&lt;BR /&gt;
One thing to remember is that not only must the new switch run the same EXOS version as the remaining switches in the stack, but it has to be stored IN THE SAME partition (primary/secondary)...&lt;BR /&gt;
&lt;BR /&gt;
Regards, Daniel&lt;BR /&gt;
  (from Daniel_Flouret)</description>
      <pubDate>Wed, 08 Jan 2014 06:05:00 GMT</pubDate>
      <guid>https://community.extremenetworks.com/t5/extremeswitching-exos-switch/replacing-a-failed-summit-x450-in-a-stack/m-p/53568#M15103</guid>
      <dc:creator>EtherNation_Use</dc:creator>
      <dc:date>2014-01-08T06:05:00Z</dc:date>
    </item>
    <item>
      <title>RE: Replacing a failed Summit X450 in a stack</title>
      <link>https://community.extremenetworks.com/t5/extremeswitching-exos-switch/replacing-a-failed-summit-x450-in-a-stack/m-p/53569#M15104</link>
      <description>Create Date: Sep 10 2013  1:43PM&lt;BR /&gt;
&lt;BR /&gt;
That is exactly what I was looking for, thanks!  (from Sam_Perkins)</description>
      <pubDate>Wed, 08 Jan 2014 06:05:00 GMT</pubDate>
      <guid>https://community.extremenetworks.com/t5/extremeswitching-exos-switch/replacing-a-failed-summit-x450-in-a-stack/m-p/53569#M15104</guid>
      <dc:creator>EtherNation_Use</dc:creator>
      <dc:date>2014-01-08T06:05:00Z</dc:date>
    </item>
  </channel>
</rss>

