We have and existing switch in the dashboard configured doing it's thing but I have bought a new switch and want to physical stack them to together.
Is this straight forward or do I need to take steps so I don't wipe the existing config from the old switch?
I have bought the stacking cables and ready to stack them but it just wanted to double check that connecting new switch and inserting the stacking cables, then creating the stack in the dashboard it won't wipe the config from the existing switch.
Also do both switches need to be powered off to connected the stacking cables or can the switches be powered on?
Solved! Go to solution.
The original switch port configuration will be maintained (trunk, access, vlans, etc).
Things like layer 3 interfaces, spanning tree priority, etc will be wiped. Things that you configure across the whole switch.
So in summary, port style config is kept, switch style config is lost.
Take a look at this:
https://documentation.meraki.com/MS/Stacking/Switch_Stacks#Understanding_Physical_Stacking
And also this:
https://documentation.meraki.com/MS/Stacking/Switch_Stacks#Configuring_a_Physical_Switch_Stack
Thanks for the links, but it doesn't mention anything about adding a new switch to one that has been in the network for some time and is currently the core of the network, by adding a new switch in and creating a stack I don't want to lose the config on the existing switch.
I want to add a some redundancy to the network hence adding a new switch and creating a stack.
You will not lose the config of the existing switch. But adding a member to a stack (or especially building a stack) is better done with the switches being switched off and not doing it online.
Are you sure?
When a new switch stack is created, or a new switch is added to an existing stack, the below configurations will be removed from the stand-alone switch(es) and will need to be reconfigured on the stack:
Features like the ones above run one instance for the entire switch. When a stack is created, you are combining multiple physical switches all running their own instances of the feature to a single logical switch, which is why some features need to be reconfigured.
The steps below explain how to prepare a group of switches for physical stacking, how to stack them together, and how to configure the stack in Dashboard.
The original switch port configuration will be maintained (trunk, access, vlans, etc).
Things like layer 3 interfaces, spanning tree priority, etc will be wiped. Things that you configure across the whole switch.
So in summary, port style config is kept, switch style config is lost.
@alemabrahao wrote:
When a new switch stack is created, or a new switch is added to an existing stack, the below configurations will be removed from the stand-alone switch(es) and will need to be reconfigured on the stack:
- Link aggregates
[...]
Hah! That explains the recent f*ck up on a customer network I made, when guiding the customer to stack two switches, resulting in a loop.
I honestly thought that it was the clean, unprovisioned switch introduced with redundant stack cables that made the loop, and brought everything down.