Примечания к выпуску для Cisco Cisco 2106 Wireless LAN Controller
12
Release Notes for Cisco Wireless LAN Controllers and Lightweight Access Points for Release 4.2.207.0
OL-31336-01
Important Notes
These examples show the output from the CLI commands (in bold) that you use to check the bootloader
version on LWAPP and autonomous 1250 series access points:
version on LWAPP and autonomous 1250 series access points:
LWAPP (commands entered on the controller CLI):
(wlc) >debug ap enable AP001b.d513.1754
(wlc) >debug ap command "show version | include BOOTLDR" AP001b.d513.1754
(wlc) >Thu Apr 23 09:31:38 2009: AP001b.d513.1754: BOOTLDR: C1250 Boot Loader
(C1250-BOOT-M) Version 12.4(10b)JA, RELEASE SOFTWARE (fc1)
Autonomous (command entered on the access point CLI):
ap# show version | include BOOTLDR
BOOTLDR: C1250 Boot Loader (C1250-BOOT-M) Version 12.4(10b)JA, RELEASE SOFTWARE (fc1)
Port Mirroring Not Supported on Some Controller Platforms
The controller port mirroring feature is not supported on 2100 series controllers, 4400 series controllers,
Cisco WiSM controllers, and controller network modules.
Cisco WiSM controllers, and controller network modules.
Internal DHCP Server
When clients use the controller’s internal DHCP server, IP addresses are not preserved across reboots.
As a result, multiple clients can be assigned the same IP address. To resolve any IP address conflicts,
clients must release their existing IP address and request a new one.
As a result, multiple clients can be assigned the same IP address. To resolve any IP address conflicts,
clients must release their existing IP address and request a new one.
RLDP Limitations
Rogue Location Discovery Protocol (RLDP) is a controller feature that detects the presence of rogue
access points that are connected to your wired network. RLDP operates with these limitations:
access points that are connected to your wired network. RLDP operates with these limitations:
•
RLDP detects rogue access points that are configured for open authentication.
•
RLDP detects rogue AP which use a broadcast BSSID--that is, the access point broadcasts its SSID
in beacons.
in beacons.
•
RLDP detects only rogue AP that are on the same the network. In other words, if an access list in
the network prevents the sending of RLDP traffic from the rogue AP to the controller, RLDP will
not work.
the network prevents the sending of RLDP traffic from the rogue AP to the controller, RLDP will
not work.
•
RLDP does not work on 5-GHz DFS channels.
•
RLDP is a best-effort protocol. For each rogue, the controller initiates RLDP only once. If the
controller does not detect a rogue (due to a noisy RF environment, for example), the controller does
not retry. However, you can initiate RLDP manually on a rogue at any time.
controller does not detect a rogue (due to a noisy RF environment, for example), the controller does
not retry. However, you can initiate RLDP manually on a rogue at any time.
Configuration File Stored in XML Format
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.
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.