Cisco Cisco 2106 Wireless LAN Controller Notas de publicación
7
Release Notes for Cisco Wireless LAN Controllers and Lightweight Access Points for Release 5.2.193.0
OL-31336-01
Software Release Information
Special Rules for Upgrading to Controller Software 5.2.193.0 in Mesh Networks
Caution
Before upgrading your controller to software release 5.2.193.0 in a mesh network, you must comply with
the following rules.
the following rules.
Upgrade Compatibility Matrix
outlines the upgrade compatibility of controller mesh and non-mesh releases and indicates the
intermediate software releases required as part of the upgrade path.
Software Upgrade Notes
•
You can upgrade from all mesh releases to controller software release 5.2.193.0 without any
configuration file loss.
configuration file loss.
Note
If you downgrade to a mesh release, you must then reconfigure the controller. Cisco
recommends that you save the configuration from the mesh release before upgrading to
release 5.2.193.0 for the first time. Then you can reapply the configuration if you need to
downgrade.
recommends that you save the configuration from the mesh release before upgrading to
release 5.2.193.0 for the first time. Then you can reapply the configuration if you need to
downgrade.
•
You cannot downgrade from controller software release 5.2.193.0 to a mesh release (4.1.190.5,
4.1.191.22M, or 4.1.192.xM) without losing your configuration settings.
4.1.191.22M, or 4.1.192.xM) without losing your configuration settings.
•
Configuration files are in the binary state immediately after upgrade from a mesh release to
controller software release 5.2.193.0. After reset, the XML configuration file is selected.
controller software release 5.2.193.0. After reset, the XML configuration file is selected.
•
Do not edit XML files.
•
Any field with an invalid value is filtered out and set to default by the XML validation engine.
Validation occurs during bootup.
Validation occurs during bootup.
•
If you upgrade the controller from software release 4.1.191.xM to 4.1.192.xM and then to software
release 5.2.193.0, the controller might reboot without a crash file. To work around this problem,
manually reset the controller without saving the configuration after you upgrade the controller to
software release 5.2.193.0. Also, make sure to check the RRM configuration settings after the reset
to verify that they are correct (CSCsv50357).
release 5.2.193.0, the controller might reboot without a crash file. To work around this problem,
manually reset the controller without saving the configuration after you upgrade the controller to
software release 5.2.193.0. Also, make sure to check the RRM configuration settings after the reset
to verify that they are correct (CSCsv50357).