The configuration files record settings for all global and interface specific settings that define the operation of the stack and individual members. Once a save to the configuration is issued, all stack members store a copy of the configuration settings. If a stack manager becomes unavailable, any stack member assuming the role of stack manager will operate from the saved configuration files.
When a new, out-of-box switch joins a switch stack, it uses the system-level settings of that switch stack. For the switch to store this system-level configuration, you must issue the following command:
copy system:running-config nvram:startup-config (in Privileged EXEC)
This command saves passwords and all other changes to the device.
If you do not save the configuration using this command, all configurations will be lost when a power cycle is performed on the networking device or when the networking device is rebooted.
Note
After downloading a configuration file to a stack, you must perform a configuration save operation from the 200 Series user interface (that is, the copy command shown above) to distribute this configuration to non-management units in the stack. This is also true of SSH key files and SSL certificate files. From the command line interface, the following command can be used:copy system:running-config nvram:startup-config (in Privileged EXEC)
You back up and restore the stack configuration in the same way as you would for standalone switch configuration.