09-12-2013 10:31 AM - edited 03-11-2019 07:37 PM
The title pretty much says it all. I have a customer who is running 5510s on 8.2. We are replacing them with 5515-Xs, but obviously need to upgrade the configs first. One thought I had: copy the old config to the startup config on the new box, then reload it and let it do it's automagical conversion. But it occured to me that, since the X series never ran on 8.2, the code probably doesn't have that feature in it. Does anyone know?
09-12-2013 10:47 AM
Hello James,
the lowest version u can run on the 5515 is 8.6.
So you will need to do the upgrade on the 5510 and then copy-paste the configuration
For more information about Core and Security Networking follow my website at http://laguiadelnetworking.com
Any question contact me at jcarvaja@laguiadelnetworking.com
Cheers,
Julio Carvajal Segura
09-12-2013 10:53 AM
I know that 8.6 is the lowest version. My idea, though, was to take the old config and, copy it directly to the startup-config (via the "copy tftp: start" command) and then reload. My thought process was that this would be like booting up a box after upgrading it. But I dont know if the code for the 55XX-X train still will detect and upgrade pre-8.3 configs...
09-12-2013 10:56 AM
Hello James,
That will not work sa the 55-XX does not have concept of that previous code.
Again my recommendation would be to do it on the 5510. and then place it into the X one
For more information about Core and Security Networking follow my website at http://laguiadelnetworking.com
Any question contact me at jcarvaja@laguiadelnetworking.com
Cheers,
Julio Carvajal Segura
09-12-2013 11:09 AM
Hi,
Here is a link to a document.
It states that Cisco has a Web based tool to migrate the configuration but I have never used it. I guess you will need to have a service contract to get access to it through TAC
http://www.cisco.com/en/US/prod/collateral/vpndevc/ps5708/ps5709/ps6120/guide_c07-727453.html
The document doesnt have an index so scroll a bit down to reach the section which mentions the conversion/migration tool.
I would personally suggest learning the new NAT format and do the configurations manually. Otherwise you might end up not understanding the new NAT format completely.
Ofcourse I am not sure how big NAT configuration we are dealing with. With regards to the amount of works needed for the manual conversion naturally depends on how well the 8.2 format configuration was done originally.
- Jouni
09-12-2013 11:04 AM
Hi James
Before any copy and paste, you must be sure that all syntact will be the same from 8.2 to 8.3. Take in consideretion the following link:
https://supportforums.cisco.com/docs/DOC-12690
Best Regars
Andres
09-12-2013 01:45 PM
All,
Thanks for the heads up. I did figure out a workaround: I can run 8.4 in GNS3. I should be able to import the config to the startup in that, and then do a reload and it should do the migration. I will still most likely need to massage it afterwards, but it gives me something to start with without having to disrupt the current FWs.
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