Add new node to stack
Options
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Get Direct Link
- Report Inappropriate Content
‎01-07-2014 09:56 PM
Create Date: Oct 9 2012 3:03PM
Is the process of adding a new node to a stack disruptive? Will it cause downtime?
IS it possible to downgrade the firmware on a switch to match the version in the stack?
Can you confirm that this is the correct procedure to add the new node?
1)Make sure the Summitstack cards is inserted in Slot B
2)Verify the new node is running the same ExtremeXOS software version by using the show switch command
3)Verify the new node is running on the same image (prmary or secondary) that the stack is running on using the show switch command
4)Use the enable stacking command to enable stacking
5) Type show stacking to get the node address
6)To configure a unigue slot number for the switch type configure stacking node-address (Node address from step 5) slot-number (slot number next in stack)
7)To assign the new switch as a member type the following configure stacking node-address (Node address from step 5) license-level edge
8)Connect to new switch to the stack using the stacking cable
Disconnect port 2 in the last node
Connect port 1 of the new node to port 2 of the last node
Connect port 2 of the new node to port 1 of the first node
9)type the following command on the new switch to reboot reboot
10)Log into the stack master node before entering the next command
Synchronize stacking node-address (Node address from step 5)
Reboot node-address (Node address from step 5)
11)Once the new node is rebooted type the following command to view the stack
Show stacking
You should see the new node listed as active
(from Vince_MacNeil)
Is the process of adding a new node to a stack disruptive? Will it cause downtime?
IS it possible to downgrade the firmware on a switch to match the version in the stack?
Can you confirm that this is the correct procedure to add the new node?
1)Make sure the Summitstack cards is inserted in Slot B
2)Verify the new node is running the same ExtremeXOS software version by using the show switch command
3)Verify the new node is running on the same image (prmary or secondary) that the stack is running on using the show switch command
4)Use the enable stacking command to enable stacking
5) Type show stacking to get the node address
6)To configure a unigue slot number for the switch type configure stacking node-address (Node address from step 5) slot-number (slot number next in stack)
7)To assign the new switch as a member type the following configure stacking node-address (Node address from step 5) license-level edge
8)Connect to new switch to the stack using the stacking cable
Disconnect port 2 in the last node
Connect port 1 of the new node to port 2 of the last node
Connect port 2 of the new node to port 1 of the first node
9)type the following command on the new switch to reboot reboot
10)Log into the stack master node before entering the next command
Synchronize stacking node-address (Node address from step 5)
Reboot node-address (Node address from step 5)
11)Once the new node is rebooted type the following command to view the stack
Show stacking
You should see the new node listed as active
(from Vince_MacNeil)
6 REPLIES 6
Options
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Get Direct Link
- Report Inappropriate Content
‎01-07-2014 09:56 PM
Create Date: Oct 11 2012 8:18PM
Do I console onto the new switch to run the command enable stacking? (from Vince_MacNeil)
Do I console onto the new switch to run the command enable stacking? (from Vince_MacNeil)
Options
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Get Direct Link
- Report Inappropriate Content
‎01-07-2014 09:56 PM
Create Date: Oct 9 2012 4:03PM
Hello vmacnell
Adding a node is not disruptive to the other stack. There should be no downtime
Depends on the switch. Some switches require a min code as that code is when the switch was introduced. If there is no code restrictions then yes you can down rev the switch.
That procedure will work. one that may be simpler.
Make sure the switch has the right code in the same image container as the other switches in the stack. If the code is prior to 12.6 make sure all switches have the same license level.
with the stack running in normal operation add the new switch to the stack by disconnecting the cable from the last switch and inserting it to the new switch and then using the other cable to reconnect the ring to the top of stack.
Turn on new switch
Type enable stacking (MAKE SURE YOU ANSWER NO TO USING EASY STACK)
let the new switch come up it should join without an issue. IF not then use the config node command to add the MAC to the new slot into the master then reboot new switch
Everything should be one stack and no current users are affected.
Let me know if that helps.
P (from Paul_Russo)
Hello vmacnell
Adding a node is not disruptive to the other stack. There should be no downtime
Depends on the switch. Some switches require a min code as that code is when the switch was introduced. If there is no code restrictions then yes you can down rev the switch.
That procedure will work. one that may be simpler.
Make sure the switch has the right code in the same image container as the other switches in the stack. If the code is prior to 12.6 make sure all switches have the same license level.
with the stack running in normal operation add the new switch to the stack by disconnecting the cable from the last switch and inserting it to the new switch and then using the other cable to reconnect the ring to the top of stack.
Turn on new switch
Type enable stacking (MAKE SURE YOU ANSWER NO TO USING EASY STACK)
let the new switch come up it should join without an issue. IF not then use the config node command to add the MAC to the new slot into the master then reboot new switch
Everything should be one stack and no current users are affected.
Let me know if that helps.
P (from Paul_Russo)
