PDF(189.2 KB) View with Adobe Reader on a variety of devices
ePub(255.7 KB) View in various apps on iPhone, iPad, Android, Sony Reader, or Windows Phone
Mobi (Kindle)(162.8 KB) View on Kindle device or Kindle app on multiple devices
Updated:December 12, 2018
Cannot Add a New Switch to an Existing Stack
Stacking is a network solution that connects two or more switches on top of one another and configuring them as one device. The switches in a stack function as a single switch with all its characteristics and functionality, at the same time, having additional ports to accommodate more devices. This procedure provides users the convenience to expand their network without the hassle of managing multiple switches.
A stack is composed of switches that has three roles:
Master — This switch is the commander of the whole stack. It handles all the configuration and other functions of the whole stack. Each time you need to change or configure any of the settings, you must do it on this switch.
Backup — This switch is like a standby switch in case the master goes offline. It automatically assumes the responsibility and become the master switch.
Slave — This switch serves as a member of the stack and operates as an additional unit within the stack.
To learn how to configure stack settings on your switch through the web-based utility, click here. To configure through the CLI, click here.
Stackable switches can be replaced, added, or removed from a stack as needed without affecting the overall performance of the stack. In this scenario, a stack already exists and the original master switch has been replaced. However, the new replacement switch is not working as expected when it was added to the stack. This can be due to the following reasons:
Power — The new switch is powered on and the stacking cable is already attached to it and connected to the stack.
Cable Issues — The cables attached to the switches are not properly connected.
If the new switch is already powered on and a cable is already attached to it prior to connecting it to the stack, the entire stack will reboot. Make sure the new switch is powered off before connecting it to the stack.
If there are one or more cables used in the stack that are either not working properly or not connected properly, the connectivity of the stack will be affected. Make sure to check all cables and their connection to each of the switches in the stack.
All the switches in the stack should have the same firmware version. Make sure to check the firmware version of the new switch. Follow the steps below to check the firmware version of your switch:
Step 1. Log in to the switch web-based utility and choose Status and Statistics > System Summary.
Step 2. Under the Software Information area, look for the Firmware Version (Active Image). This will determine the version of the firmware the new switch is currently using.
Step 3. Repeat these steps on any of the active switches in the stack and check the firmware version they are using. If the new switch has a different version than the rest of the switches in the stack, you need to upgrade or downgrade it, whichever is needed. To learn how to upgrade the firmware of your switch, click here.
If the new switch already contains configuration settings, it may cause issues the moment you add it to the stack. If you are not sure, it is recommended to reset the switch to set it back to factory default settings before adding it to the stack. To learn how to reset the switch through the web-based utility, click here. To reset it through the CLI, click here.
If the port on the new switch is not properly configured, it will not work with the stack. Make sure the switch is reset to its factory default settings in order to erase improper configuration so it can be recognized immediately by the stack.
You now should have added a new switch to your existing stack.