Cisco Cisco Aironet 1200 Access Point 릴리즈 노트

This section lists 

 and 

 in Cisco IOS Release 12.3(2)JA2.

These caveats are open in Cisco IOS Release 12.3(2)JA2:

CSCeb52431—When logging into a TACACS+ server, 1100 series access points sometimes send 
hundreds of additional authentication requests to the server after a successful authentication.

CSCee87287—Access points sometimes fail to generate accounting records when a wireless client 
is re-authenticated on an automatic interval (for example, when the access point is configured using 
the dot1x reauthentication seconds command). 

CSCef11167—The access point sometimes returns an inaccurate value when you poll 
cDot11ActiveWirelessClients through SNMP.

CSCef65076—The access point GUI sometimes reports this error when you a RADIUS server 
hostname to the access point:

HTTP 400 - Bad Request

Workaround: Enter the server IP address instead of the hostname.

CSCef78627—The access point reports an incorrect transmit power value for the 802.11a radio 
when you change the external antenna position from high-gain to low-gain or from low-gain to 
high-gain while the access point is on.

Workaround: Change the antenna position on the 802.11a radio only when the unit is off.

CSCef95410—When an access point is configured to interact with a WDS device, the WLCCP 
packets that it receives from the WDS device sometimes cause the radio interface output drop 
counter to increment when it should not.

CSCeg70288—On 1200 series access points, tracebacks occur when you enter the 
no dot11 arp-cache command when ARP caching is already disabled.

These caveats are resolved in Cisco IOS Release 12.3(2)JA2:

CSCea72719—An access point configured as the WDS device no longer uses up all UDP ports for 
RADIUS accounting.

CSCeb50727—Unpowered 1100 series access points manufactured after January, 2004 no longer 
cause a loopback when connected to switches without loopback detection. 

If your 1100 series access point was manufactured before January, 2004, the access point might 
cause a loopback when the power is off and it is connected to a switch without loopback detection. 
To avoid this problem, make sure loopback detection is enabled on the switch to which the access 
point is connected. If your switch does not have loopback detection, disconnect the access point 
from the switch when the access point power is off.

CSCee51985—Access points now correctly apply QoS priorities to DSCP-tagged packets.

CSCee90230—When the access point is configured for TACACS+ administrator authentication and 
uses an IP address from the DHCP server, tracebacks no longer occur when the access point reboots.