Примечания к выпуску для Cisco Cisco 2106 Wireless LAN Controller
7
Release Notes for Cisco Wireless LAN Controllers and Lightweight Access Points for Release 4.2.205.0
OL-31336-01
New Features
Step 6
In the IP Address field, enter the IP address of the TFTP server.
Step 7
The default values of 10 retries and 6 seconds for the Maximum Retries and Timeout fields should work
fine without any adjustment. However, you can change these values if desired. To do so, enter the
maximum number of times that the TFTP server attempts to download the software in the Maximum
Retries field and the amount of time (in seconds) that the TFTP server attempts to download the software
in the Timeout field.
fine without any adjustment. However, you can change these values if desired. To do so, enter the
maximum number of times that the TFTP server attempts to download the software in the Maximum
Retries field and the amount of time (in seconds) that the TFTP server attempts to download the software
in the Timeout field.
Step 8
In the File Path field, enter the directory path of the software.
Step 9
In the File Name field, enter the name of the software file (filename.aes).
Step 10
Click Download to download the software to the controller. A message appears indicating the status of
the download.
the download.
Step 11
Repeat
to
to install the remaining file (either the 4.2.205.0 controller software or the
Cisco Unified Wireless Network Controller Boot Software 4.2.205.0 ER.aes file).
Step 12
After the download is complete, click Reboot.
Step 13
If prompted to save your changes, click Save and Reboot.
Step 14
Click OK to confirm your decision to reboot the controller.
Step 15
If desired, reload your latest configuration file to the controller.
Step 16
To verify that the 4.2.205.0 controller software is installed on your controller, click Monitor on the
controller GUI and look at the Software Version field under Controller Summary.
controller GUI and look at the Software Version field under Controller Summary.
Step 17
To verify that the Cisco Unified Wireless Network Controller Boot Software 4.2.205.0 ER.aes file is
installed on your controller, enter the show sysinfo command on the controller CLI and look at the
Bootloader Version field. “N/A” appears if the ER.aes file is installed successfully. “Error” appears if
the ER.aes file is not installed.
installed on your controller, enter the show sysinfo command on the controller CLI and look at the
Bootloader Version field. “N/A” appears if the ER.aes file is installed successfully. “Error” appears if
the ER.aes file is not installed.
Note
You can use this command to verify the boot software version on all controllers except the 2106
because the bootloader is not upgradable on the 2106 controller.
because the bootloader is not upgradable on the 2106 controller.
New Features
The following new feature is available in this software release:
•
Configurable Off-Channel Scanning to Improve Performance for Medical Devices—Using Radio
Resource Management, lightweight access point radios can simultaneously scan all valid
802.11a/b/g channels for the country of operation as well as for channels available in other locations.
The access point radios go “off-channel” for a period not greater than 60 ms to monitor these
channels for noise and interference. Packets collected during this time are analyzed to detect rogue
access points, rogue clients, ad-hoc clients, and interfering access points. In the presence of voice
or video traffic in the last 100 ms, the access points defer off-channel measurements.
Resource Management, lightweight access point radios can simultaneously scan all valid
802.11a/b/g channels for the country of operation as well as for channels available in other locations.
The access point radios go “off-channel” for a period not greater than 60 ms to monitor these
channels for noise and interference. Packets collected during this time are analyzed to detect rogue
access points, rogue clients, ad-hoc clients, and interfering access points. In the presence of voice
or video traffic in the last 100 ms, the access points defer off-channel measurements.
Some devices, including some medical equipment, require a longer elapsed time without the
appearance of a packet that defers off-channel scanning. Using two new CLI commands, you can
configure, per WLAN, the minimum number of milliseconds that must elapse without the
appearance of a specified packet before the access point radios begin an off-channel scan, and you
can specify the priorities of packets that defer off-channel scans.
appearance of a packet that defers off-channel scanning. Using two new CLI commands, you can
configure, per WLAN, the minimum number of milliseconds that must elapse without the
appearance of a specified packet before the access point radios begin an off-channel scan, and you
can specify the priorities of packets that defer off-channel scans.