PDF(288.8 KB) View with Adobe Reader on a variety of devices
ePub(324.8 KB) View in various apps on iPhone, iPad, Android, Sony Reader, or Windows Phone
Mobi (Kindle)(236.3 KB) View on Kindle device or Kindle app on multiple devices
Updated:July 7, 2016
The documentation set for this product strives to use bias-free language. For the purposes of this documentation set, bias-free is defined as language that does not imply discrimination based on age, disability, gender, racial identity, ethnic identity, sexual orientation, socioeconomic status, and intersectionality. Exceptions may be present in the documentation due to language that is hardcoded in the user interfaces of the product software, language used based on RFP documentation, or language that is used by a referenced third-party product. Learn more about how Cisco is using Inclusive Language.
Copy/Save Configuration on the ESW2-550X Switch
The copy/save settings are used to save or copy the switch configuration from a volatile memory to a non-volatile memory. Configuration changes made on the switch are saved in the running configuration (volatile memory) and are removed once the switch is rebooted. To preserve these configurations the running configuration must be copied to startup configuration (non-volatile memory) or saved on another device.
This article explains how to copy/save configurations on the ESW2-550X stackable managed switch.
• ESW2-550X • ESW2-550X-DC
Step 1. Log in to the web configuration utility and choose Administration > File Management > Copy/Save Configuration. The Copy/Save Configuration page opens:
Step 2. Click the desired radio button in the Source File Name field to choose the configuration file that needs to be copied. The available configuration files are:
• Running configuration — The current configuration running on the switch will be in the volatile memory.
• Startup configuration — The configuration used when the switch is started or rebooted.
• Backup configuration — The configuration saved in the non-volatile memory can be used if the startup and running configuration are crashed.
• Mirror configuration — If running configuration is not modified for at least 24 hours, it is automatically saved to the mirror configuration and a log message is generated with the appropriate event severity level.
Step 3. Click the desired radio button in the Destination File Name field to which the source file is to be copied. The available configuration files are:
Note: Sensitive Data field is enabled when Backup configuration is chosen in Step 3.
Secure Sensitive Data (SSD) is an architecture that provides protection to sensitive data on a device, such as passwords and keys. SSD also enables the secure backup and sharing of configuration files which contains sensitive data. To configure SSD rules choose Security > Secure Sensitive Data Management > SSD Rules. The SSD rules can be configured by users who have read permission of Plaintext and encrypted.
Step 4. Click the desired radio button in the Sensitive Data field to define how the sensitive data should be saved in the backup process.
• Exclude — The sensitive data are not saved to the backup configuration.
• Encrypted — The sensitive data are saved in the encrypted form only.
• Plaintext — The sensitive data are saved as the plaintext only.
Step 5. Click Apply.
Step 6. (Optional) The configuration changes are saved in the running configuration by default and if the switch gets rebooted all the running configuration would be lost, so in order to notify this to the user, save icon always blinks on the top right of the switch web utility. To disable the save icon from blinking, click Disable Save Icon Blinking but it is not recommended.