Convert Configuration Files using the Configuration Migration Tool on Cisco Small Business Switches
Introduction
The Cisco Configuration Migration Tool allows you to convert configuration files from previous generation of Cisco Small Business switches such as Sx200, Sx300, and Sx500 series to the newest devices such as Sx250, Sx350, SG350X and Sx550X.
The Configuration Migration Tool will perform the following conversions:
Update interface names to the new interface naming conventions used in the new devices.
- When converting the settings from the source device to the destination device, the tool will attempt to map the commands from interfaces in the source device to the interfaces that would use the same role in the destination device.
Convert commands that are no longer supported to analogous commands from the newer devices.
- The tool will attempt to keep the same functionality between the original behavior and the behavior in the updated configuration.
Remove commands for features that are no longer supported.
To use the Configuration Migration Service, follow this process:
Back up a system configuration file of an Sx200, Sx300, and Sx500 series switch through Hyper Text Transfer Protocol (HTTP) or Hyper Text Transfer Protocol Secure (HTTPS), Trivial File Transfer Protocol (TFTP), or Secure Copy (SCP). The current firmware version should be at least 1.4.x or higher. For instructions, click here.
Convert the configuration file using the Configuration Migration Tool. To do this, follow the steps in this article.
Update the system configuration file of an Sx250, Sx350, SG350X, and Sx550X switch through HTTP/HTTPS, TFTP, SCP, or USB. The current firmware version should be at least 2.3.x or higher. For instructions, click here.
Objective
This article provides instructions on how to use the Configuration Migration Tool to convert a configuration file of a previous generation switch and update a newer switch using the converted configuration file.
Step 2. In the Source Configuration area, choose a device model from the Source Device Model drop-down list. This is the device used in the backup configuration file. In this example, SG300-28 switch is chosen.
Note: Choosing a source device model will determine the compatible devices in the Device Destination model area.
Step 3. Open the backed-up configuration file then copy all the contents.
Step 4. Paste the configuration file into the Source Configuration box.
Step 5. In the Updated Configuration area, choose a device model from the Destination Device Model drop-down list. The backed-up configuration file will be converted to be used into this switch. In this example, SG350X-48MP is chosen.
Note: The Destination Device Model drop-down lists the compatible devices according to the chosen Source Device model.
Step 6. Click the Convert button to convert the source configuration file to the updated configuration file which is compatible to the chosen destination device model.
The bottom notification box should display the Conversion completed successfully! message to indicate successful conversion.
Step 7. Highlight the contents of the Updated Configuration box and then click the Copy to Clipboard button to copy the converted configuration file.
Step 8. Open a new text file then paste the copied configuration file.
Step 9. Click File then click Save.
Step 10. Enter the file name in the Save As field then save the file to the file location (such as local drive, USB, TFTP, or SCP server) according to your preferred transfer method.
Note: In this example, the updated configuration file named For SG350X-48MP.txt is saved in the Firmware folder in the local computer.
You should now have successfully converted the source configuration file into an updated configuration file through the Configuration Migration Tool.
To update the system configuration file of the switch through HTTP/HTTPS, TFTP, SCP, or USB, click here for instructions.
Find answers to your questions by entering keywords or phrases in the Search bar above. New here? Use these resources to familiarize yourself with the community: