Cisco Cisco Aironet 1200 Access Point Release Notes
14
Release Notes for Cisco Aironet 1100 and 1200 Series Access Points for Cisco IOS Release 12.2(13)JA3
OL-5428-02
Caveats
•
CSCec02800—The access point web-browser interface sometimes displays cached information for
the Associations page and does not list all associated client devices.
the Associations page and does not list all associated client devices.
Workaround: Refresh the Associations page in the web-browser interface to display current client
associations.
associations.
•
CSCec23329—Access points with PMIP enabled sometimes misinterpret an ARP sent by some
client devices that check to make sure that their IP addresses are not in use. When the access point
receives the ARP from the client, the access point interprets the ARP as a DHCP request and disables
PMIP for the client session.
client devices that check to make sure that their IP addresses are not in use. When the access point
receives the ARP from the client, the access point interprets the ARP as a DHCP request and disables
PMIP for the client session.
Workaround: If possible, disable the feature on the client device that automatically sends an ARP to
the access point to check IP address availability.
the access point to check IP address availability.
•
CSCec25559—When both 802.11g and 802.11a client devices transmit data simultaneously to the
802.11g and 802.11a radios in a 1200 series access point, the throughput of the 802.11a radio might
decrease.
802.11g and 802.11a radios in a 1200 series access point, the throughput of the 802.11a radio might
decrease.
•
CSCec28612—ACL logging is not supported on access point radio interfaces. You must remove the
log option from the command for the ACL to take effect. However, ACL logging is supported on
access point BVI interfaces.
log option from the command for the ACL to take effect. However, ACL logging is supported on
access point BVI interfaces.
•
CSCec33268—When the access point is configured for optional or mandatory WPA authentication,
client adapters in Windows XP platforms sometimes experience a delay when initially
authenticating to the access point immediately after it starts up.
client adapters in Windows XP platforms sometimes experience a delay when initially
authenticating to the access point immediately after it starts up.
•
CSCec33519—Administrative users assigned the admin-capability attribute sometimes cannot log
into the access point using Telnet.
into the access point using Telnet.
•
CSCec43008—When you update a WEP key using SNMP, the access point radio does not restart
automatically, and the access point continues to use the old WEP key.
automatically, and the access point continues to use the old WEP key.
Workaround: Restart the access point radio after using SNMP to update a WEP key.
•
CSCec43849—When you configure your access point for MAC address authentication for a large
number of MAC addresses, client devices sometimes experience long delays when several clients
roam from one access point to another at the same time.
number of MAC addresses, client devices sometimes experience long delays when several clients
roam from one access point to another at the same time.
•
CSCec55763, CSCec55820—When both the 802.11g and 802.11a radios in a 1200 series access
point simultaneously operate under extremely high data loads for an extended period, the 802.11a
radio sometimes hangs or the access point reboots.
point simultaneously operate under extremely high data loads for an extended period, the 802.11a
radio sometimes hangs or the access point reboots.
•
CSCec59848—The access point uses only multiples of 8 for the Max Data Retries setting on the
802.11g radio. If you set the Max Data Retries setting to a value that is not a multiple of 8, the access
point rounds down to the closest multiple of 8. For example, if you set Max Data Retries to 20, the
access point rounds the setting down to 16.
802.11g radio. If you set the Max Data Retries setting to a value that is not a multiple of 8, the access
point rounds down to the closest multiple of 8. For example, if you set Max Data Retries to 20, the
access point rounds the setting down to 16.
•
CSCec60868—Changing the TKIP MIC failure holdoff time to a non-default value triggers the
holdoff timeout in these situations:
holdoff timeout in these situations:
–
Immediately after you set the timeout to a non-default value, the holdoff timeout is in effect and
clients cannot associate for the specified holdoff period. However, if you set the holdoff timeout
to the default value (60 seconds), the timeout is not triggered immediately after you set it.
clients cannot associate for the specified holdoff period. However, if you set the holdoff timeout
to the default value (60 seconds), the timeout is not triggered immediately after you set it.
–
When the access point reboots, the holdoff timeout is triggered and clients cannot associate until
the timeout expires. However, the timeout is not triggered after a reboot if the timeout is set to
the default value (60 seconds).
the timeout expires. However, the timeout is not triggered after a reboot if the timeout is set to
the default value (60 seconds).
•
CSCin60014—These invalid configurations cause radio errors:
–
WPA optional with the TKIP cipher
–
WPA mandatory with TKIP+WEP40