Cisco Cisco Aironet 1200 Access Point 릴리즈 노트

You must use a Wireless LAN Services Module (WLSM) as your WDS device to configure Layer 3 
mobility. If you enable Layer 3 mobility for an SSID and your WDS device does not support Layer 3 
mobility, client devices cannot associate using that SSID.

This section lists open and resolved caveats for access points.

These caveats are open in Cisco IOS Release 12.3(8)JEC1:

CSCsv36602—Files appearing on access point flash with 5-GHz serial number as filename

These files are created when radar is detected on a DFS channel. The files are created with the 
filename consisting of the serial number of the radio that detected the radar and include the DFS 
channel on which the radar was detected. The file is used is used when the access point is reset to 
ensure that the radar detected channels are not immediately selected after the reset.

Conditions: When radar is detected on a DFS channel.

Workaround: None. This is an expected behavior. The file should not be removed.

CSCsm12509—DOT11-4-MAXRETRIES increase exponentially after upgrade 

After upgrading from Cisco IOS version 12.3(7)JA or a rebuild to either 12.3(8)JEB or 12.3(11)JA1, 
the following system log message appears:

DOT11-4-MAXRETRIES 

This message is seen with much greater frequency than before. Quantity of these messages have 
increased by a factor of 10 to 15. This increase in messages can overflow the syslog server, and 
changing the logging level less than 4 is unacceptable as other significant system messages will be 
missed.

Workaround—Downgrade to a previous version.

CSCsk80813—Vista's anonymous provisioning does not work with access point local AAA server

CSCsm62622—Applying access-group to physical int modifies ACL in running-config

Applying access-group to physical interfaces modifies ACL in running-config when using bridge 
mode on the physical interfaces. 

When making a physical interface part of a bridge group and the physical interface has an ip 
access-group <list> [in/out] assigned from a corresponding Access List (ACL) and if this ACL has 
the logging labeled, the running-config gets modified at the first list match that hits any of the 
bridged interfaces in such a way that the logging is removed from the ACL. 

Workaround—Instead of assigning the ACL to a physical interface, create a BVI interface for the 
bridge group and assign the ACL to the BVI.