11-18-2023 08:57 AM
I have multiple sg500x switches in a stack, when I go to backup the config, I am only able to backup the config of the master. How can I target/define a different switch in the stack in order to backup that units startup-config, re. that units port configurations..
Thanks..
11-18-2023 09:27 AM
When Stack means only 1 Master and rest of the members of the Stack.
All the configuration related stack members are stored in the Master switch only, When you take the config of that back is good enough.
11-18-2023 09:39 AM
Hello @bgleason
In a stack of Cisco SG500X switches, the stack is managed as a single logical unit. When you perform a configuration backup, you typically connect to the stack master to retrieve the configuration.
11-18-2023 09:53 AM
To Reply to both @balaji.bandi and M02@rt37, appreciate your time in replying.. When I backup the startup-config, it is only exporting the config of the master, I see no indication of the other switch/switches and the ports I have configured on those devices in the backed up startup-config.
11-18-2023 10:00 AM
As long as you have saved the config from running config to Startup that should be there.
Login to switch using SSH - show run (you should see all the port config) also check show startup config see that should be identical config.
11-18-2023 10:16 AM - edited 11-18-2023 10:17 AM
Hello @bgleason
If you have properly saved the configuration from the running configuration to the startup configuration using the `copy running-config startup-config` command, the configurations for all switches in the stack, including individual port configurations, should indeed be present in the startup configuration.
When you log in to the switch and use the `show running-config` command, you should be able to see the configurations for all the ports.
11-18-2023 10:28 AM
It appears the startup-configs are unique to each unit in the stack, and when the units power on, they aggregate to the running-config. Backing up the running-config has all the details/configuration for the stack. so that is the config that I will be backing up, not the startup-config.
11-18-2023 11:38 AM
Suggestions :
1. If you using GUI, always save config to running to startup so there is no difference config
2. always backup running configuration that is one running live.
It appears the startup-configs are unique to each unit in the stack
how you checking this, - when this is part of the Stack - ( As I we mentioned repeatedly, MASTER switch own all the config) - Ignore what config on the member switch (i would not bother to look, since that config not valid - and not sure what config it going to be) - when the MASTER switch fails, respected member switch become MASTER, all the configuration will be available SLAVE (that is master now)
how are you viewing the member config ? (console ?)
how the process works explained here clearly :
SMB Switches backup :
Discover and save your favorite ideas. Come back to expert answers, step-by-step guides, recent topics, and more.
New here? Get started with these tips. How to use Community New member guide