Upgrading Controller and Config Files

Unanswered Question
Jul 7th, 2008
User Badges:

Hello,


I am upgrading my 4402 controller from 4.1.171.0 to 4.2.130. It says I need to save my current config because it will get dumped when I do the upgrade. What extension type do I save the config files as? It does not state this anywhere...



Cisco sure doesn't make this process very easy. Save config file. Upgrade code. Download saved config file to controller. Hope nothing gets corrupted with all that and hope everything is re-enabled and configured like it was before upgrade? Seems like a lot can go wrong...

  • 1
  • 2
  • 3
  • 4
  • 5
Overall Rating: 5 (2 ratings)
Loading.
jeromehenry_2 Mon, 07/07/2008 - 12:30
User Badges:
  • Silver, 250 points or more

From a proprietary format, Cisco went to XML in 4.2. This means that your config cannot be transfered from a 4.1 controller to a 4.2 controller.

Of course if you have a config, it will be upgraded with the code, saving is just a precaution.

hth


Jerome

ssking111 Mon, 07/07/2008 - 12:34
User Badges:

Jerome,


I understand that. The documentation from Cisco says I have to save my config while my controller is still using 4.1.170. Then upgrade to 4.2.130. It said to back the config up before doing so as I will lose the current config. My question is what do I save the 4.1 config file as .txt, .xml, .make something up??? I'm presuming that once I upload that saved config back to the controller it will convert it to the newer 4.2 .xml format. Am I correct in assuming that?

ssking111 Mon, 07/07/2008 - 12:43
User Badges:

Jerome,


This is from the 4.2.112.0 release notes:


In controller software 4.2, the controller's bootup configuration file is stored in an Extensible Markup

Language (XML) format rather than in binary format. Therefore, you cannot download a binary

configuration file onto a controller running software release 4.2. However, when you upgrade a

controller from a previous software release to 4.2, the configuration file is migrated and converted to

XML.


This conflicts with what Cisco states earlier in their documentation. I thought when you upgrade it wipes everything and you loser your current config? After reading this section I gather that I only lose the running config and that it will upgrade the config stored in NVRAM? That all makes a lot more sense than what they say earlier in the guide. Once I do the upgrade I can't impor the old config due to it being in the wrong format.


So in closing this mess my take is that I just need to upload the new software image to the controller. It will load the new software version and then convert the existing config in NVRAM into the new .xml format? Yes?

Scott Fella Mon, 07/07/2008 - 19:07
User Badges:
  • Super Silver, 17500 points or more
  • Hall of Fame,

    The Hall of Fame designation is a lifetime achievement award based on significant overall achievements in the community. 

  • Cisco Designated VIP,

    2017 Wireless

In short, you will be fine upgrading, but when you downgrade, you will loose everything. I have just tested it with a wlc running 3 code and upgrading it to 4.2.130. Kept the configuration.

jeromehenry_2 Tue, 07/08/2008 - 03:31
User Badges:
  • Silver, 250 points or more

Yes!

To be clearer:

- You have a controller with 4.1 code, you save your config as a safety, it's a binary file, name it the way you want (I use .cfg, but there is no boligation, the file extension will not determine the file format, it will be proprietary binary format anyway).

- You upgrade the config to 4.2. The config onboard the controller is maintained.

- You suddenly change your mind and want to downgrade to 4.1 (not using the 4.1 backup image still present in your controller, but by downloading a new 4.1 image). Your config is wipped but you can reimport the config you wisely saved before moving to 4.2.

Does that make more sense?

hth


J

Actions

This Discussion

 

 

Trending Topics: Other Wireless Mobility

client could not be authenticated
Network Analysis Module (NAM) Products
Cisco 6500 nam
reason 440 driver failure
Cisco password cracker
Cisco Wireless mode