Automated Conversion Tools

The configuration conversion tool is available as a link from the Software Center page on cisco.com. This tool allows users to paste in the configuration of a switch running Catalyst OS and see the resulting command equivalents under native IOS. In addition to pasting in the configuration in the supplied window, users may also upload configuration files for conversion.

After the configuration is converted from hybrid to native syntax, native software must be loaded into the Catalyst. As a last step, the proper changes to boot commands must be made pointing to the native software. This can be accomplished by one of two ways:

Software conversion tool available on cisco.com
Manual process

The software conversion tool is available as a link from the Software Center page on cisco.com. The software conversion tool is a JAVA-based application that relies on multiple scripts to convert a switch running hybrid to a native configuration. Figure A-1 shows the main configuration screen of the software conversion tool.

Figure A-1. Software Conversion Tool

[View full size image]

The software conversion tool has a few requirements and limitations. You must understand the preconversion instructions that follow before using the automated tool:

Step 1. Verify that an MSFC is installed.

Step 2. Verify that the Trivial File Transfer Protocol (TFTP) server is reachable from the Supervisor.

Step 3. Verify that the TFTP server is reachable from the MSFC.

Step 4. Verify that the c6sup## image is on the TFTP server.

Step 5. Ensure that enough room is available on the device (slot0: or sup-bootflash:) for the image being copied.

Step 6. If the configurations are going to be copied to the TFTP server, and the TFTP server is a UNIX machine, make sure to "touch" the files and "chmod" the permissions so that they are writable.

Step 7. The configuration files for both the Supervisor and the MSFC are backed up as

SupConfig.cfg? Default Supervisor config filename

RConfig.cfg? Default MSFC config filename

NOTE

The automated software conversion tool and the manual conversion process do not work with dual Supervisors. Switches with dual supervisors must be converted one Supervisor at a time. The secondary Supervisor should be physically ejected while the primary is converted. After the primary is converted to native, it should be ejected, and the secondary should be converted using the same process.