Cisco Cisco 2106 Wireless LAN Controller
11
Release Notes for Cisco Wireless LAN Controllers and Lightweight Access Points for Release 5.0.148.2
OL-31336-01
Important Notes
Installation Instructions
Refer to the appropriate quick start guide or hardware installation guide for instructions on installing
controllers and access points.
controllers and access points.
Note
To meet regulatory restrictions, all external antenna configurations must be professionally installed.
Personnel installing the controllers and access points must understand wireless techniques and
grounding methods. Access points with internal antennas can be installed by an experienced IT
professional.
grounding methods. Access points with internal antennas can be installed by an experienced IT
professional.
The controller must be installed by a network administrator or qualified IT professional, and the proper
country code must be selected. Following installation, access to the controller should be password
protected by the installer to maintain compliance with regulatory requirements and ensure proper unit
functionality.
country code must be selected. Following installation, access to the controller should be password
protected by the installer to maintain compliance with regulatory requirements and ensure proper unit
functionality.
Important Notes
This section describes important information about the controllers and access points.
Software Upgrade Might Fail If Certain Characters Used in Previous
Configuration
Configuration
In controller software release 4.2.61.0 and later, the controller’s bootup configuration file is stored in an
Extensible Markup Language (XML) format rather than in binary format. When you upgrade a controller
to 4.2.61.0 or a later software release, the binary configuration file is migrated and converted to XML.
However, the configuration file does not migrate correctly if it contains any of the following characters
as part of a user configuration string: &, <, >, ', ". For example, a WLAN profile named R&D causes an
XML parsing error after the second reboot, even though this profile name is valid in 4.1 and previous
configurations.
Extensible Markup Language (XML) format rather than in binary format. When you upgrade a controller
to 4.2.61.0 or a later software release, the binary configuration file is migrated and converted to XML.
However, the configuration file does not migrate correctly if it contains any of the following characters
as part of a user configuration string: &, <, >, ', ". For example, a WLAN profile named R&D causes an
XML parsing error after the second reboot, even though this profile name is valid in 4.1 and previous
configurations.
Note
You cannot download a binary configuration file onto a controller running software release 5.0.148.2.
Also, do not attempt to make changes to the configuration file. If you do so and then download the file
to a controller, the controller displays a cyclic redundancy checksum (CRC) error while it is rebooting
and returns the configuration parameters to their default values.
Also, do not attempt to make changes to the configuration file. If you do so and then download the file
to a controller, the controller displays a cyclic redundancy checksum (CRC) error while it is rebooting
and returns the configuration parameters to their default values.
LWAPP Mode Changes
When you upgrade to controller software release 5.0.148.2, the LWAPP mode changes to Layer 3 if it
was previously configured for Layer 2.
was previously configured for Layer 2.
If you downgrade from controller software release 5.0.148.2 to 4.2.61.0 or an earlier release, the LWAPP
mode changes from Layer 3 to Layer 2. Access points may not join the controller, and you must manually
reset the controller to Layer 3 to resolve this issue.
mode changes from Layer 3 to Layer 2. Access points may not join the controller, and you must manually
reset the controller to Layer 3 to resolve this issue.