Примечания к выпуску для Cisco Cisco 4402 Wireless LAN Controller

CSCsh68089—Access points connected directly to a port on 2000 or 4400 series controllers 
sometimes fail to receive an IP address through DHCP.

CSCsh68207—Access points in the same mobility group are sometimes reported as rogues.

CSCsh69985—When a Cisco 7920 phone is associated to a lightweight access point the controller 
sometimes fails to forward packets to the phone.

CSCsh76986—Access points sometimes reboot repeatedly when upgraded to software versions 
later than 4.0.206.0.

CSCsh78110—DHCP sometimes fails for client devices that associate to an access point in HREAP 
mode.

CSCsh80791—Access points in MAP mode sometimes disconnect from the controller and reload a 
backup image that does not contain the latest updates for DFS operation. The MAP access points 
then become stranded and must be manually reset.

CSCsh81746—Some client devices discard received packets with a header length shorter than 46 
bytes. The header length on Cisco Aironet 802.11 packets is shorter than 46 bytes.

CSCsh84091—Access points in HREAP mode sometimes rejoin the controller and use the wrong 
pre-shared key (PSK).

CSCsh88074—Remove Layer 3 Fortress Support.

CSCsh91578—When you upgrade a controller to software release 3.2.193.5, the Accept Self Signed 
Certificate box is unchecked, which prevents any access point with a self-signed certificate from 
rejoining the controller.

CSCsi07209—Access points enabled for RLDP sometimes fail to find the IP address for a gorue 
access point.

CSCsi15393—The controller sometimes fails to forward RFID tags to access points.

CSCsi20234—Incorrect MIBs were posted with controller software releases 3.2 and 4.0.

CSCsi49767—When a WLAN is configured with an interface that has an ACL and an AP group has 
been applied on the access point which overrides the ACL, the controller sometimes crashes when 
a client associates to the access point.

If you need information about a specific caveat that does not appear in these release notes, you can use 
the Cisco Bug Toolkit to find caveats of any severity. Click this URL to browse to the Bug Toolkit:

(If you request a defect that cannot be displayed, the defect number might not exist, the defect might not 
yet have a customer-visible description, or the defect might be marked Cisco Confidential.) 

For the most up-to-date, detailed troubleshooting information, refer to the Cisco TAC website at

Click Product Support > Wireless. Then choose your product and Troubleshooting to find information 
on the problem you are experiencing.