Примечания к выпуску для Cisco Cisco 2000 Series Wireless LAN Controller
20
Release Notes for Cisco Wireless LAN Controllers and Lightweight Access Points for Release 3.2.150.10
OL-10607-02
Caveats
•
CSCsc86705—The controller may crash when configured for Cranite Layer 2 security. This
problem occurs due to raw IP packets in a Cranite-passthrough-enabled WLAN.
problem occurs due to raw IP packets in a Cranite-passthrough-enabled WLAN.
•
CSCsc96640—When a clustered firewall is used as the default gateway for wireless clients, web
authentication does not work.
authentication does not work.
•
CSCsd03934—When an access point uses a power injector to join the controller, the controller may
log erroneous power injector errors after the access point reboots.
log erroneous power injector errors after the access point reboots.
•
CSCsd13731—The configuration wizard does not allow you to configure the AP-manager interface
with a subnet of 192.168.1.x/24 if the same subnet is already configured on the management
interface.
with a subnet of 192.168.1.x/24 if the same subnet is already configured on the management
interface.
•
CSCsd19752—If a controller is configured for Layer 3 mode and subsequently Layer 2 mode, a
client that attempts to associate does not move to the Run state if its IP address is the same as that
of the AP-manager interface. Although the IP address is not being configured correctly for the client,
the controller sends a DHCP acknowledgment, so the client assumes that it has obtained an IP
address. This problem has been resolved such that in Layer 2 mode the IP address comparison does
not include the AP-manager interface, and the controller does not send a DHCP acknowledgment if
the IP address configuration fails.
client that attempts to associate does not move to the Run state if its IP address is the same as that
of the AP-manager interface. Although the IP address is not being configured correctly for the client,
the controller sends a DHCP acknowledgment, so the client assumes that it has obtained an IP
address. This problem has been resolved such that in Layer 2 mode the IP address comparison does
not include the AP-manager interface, and the controller does not send a DHCP acknowledgment if
the IP address configuration fails.
•
CSCsd19776—When clients are MAC authenticated, the calling station ID changes to the access
point’s MAC address rather than the client’s MAC address.
point’s MAC address rather than the client’s MAC address.
•
CSCsd22087—Intel 2200 b/g clients cannot pass traffic with an AP1000 when connected in 802.11g
mode. This condition lasts for 5 to 60 seconds and then recovers, but it can occur quite frequently.
mode. This condition lasts for 5 to 60 seconds and then recovers, but it can occur quite frequently.
•
CSCsd26260—A 4100 controller configured for intrusion detection system (IDS) may crash when
connected to access points in monitor mode.
connected to access points in monitor mode.
•
CSCsd29699—The NPU may occasionally have invalid crypto handles (set to 0), which causes the
traffic to stop flowing for that client.
traffic to stop flowing for that client.
•
CSCsd32317—Attempting to enter a long custom web message from the CLI on a 2006 or 4404
controller causes the controller to crash and reboot.
controller causes the controller to crash and reboot.
•
CSCsd32384—Defining several DHCP servers may result in duplicate leases for a single client.
•
CSCsd35492—The client exclusion feature does not operate correctly when aek keywrap is
configured.
configured.
•
CSCsd36689—Access points in monitor mode do not detect probing clients. These access points do
not track the clients’ RSSI values and do not contribute location information to the Location
Appliance.
not track the clients’ RSSI values and do not contribute location information to the Location
Appliance.
•
CSCsd39937—An access point may crash due to an invalid cache index.
•
CSCsd40065—If you set a certain time zone (such as JST) on your controller, you may notice that
the real time shown on your controller jumps ahead after a reboot.
the real time shown on your controller jumps ahead after a reboot.
•
CSCsd40853—The 2.4-GHz Singapore regulatory settings for the AP1000 are incorrect. The
Allowed EIRP value should be 20 dBm (rather than 19 dBm), and channel 14 is not allowed to be
used in Singapore.
Allowed EIRP value should be 20 dBm (rather than 19 dBm), and channel 14 is not allowed to be
used in Singapore.
•
CSCsd41360—An 802.11g client cannot associate to a controller if 802.11g is disabled on the
WLAN or globally.
WLAN or globally.
•
CSCsd41602—The controller software stops and is reset by the reaper if the Task
“pemReceiveTask” misses the software watchdog.
“pemReceiveTask” misses the software watchdog.
•
CSCsd43744—A deleted SNMP community string may intermittently reappear after the controller
reboots.
reboots.