Cisco Cisco Aironet 1310 Access Point Bridge 릴리즈 노트
![Cisco](https://files.manualsbrain.com/attachments/7380d0050044647c30f5c24bbbf5d0c0b6d9bb84/common/fit/150/50/faa183d287233c52228cfea3dbc2a127fe780f60564fcb0955d9c3d1cd23/brand_logo.png)
18
Release Notes for Cisco Aironet Access Points and Bridges for Cisco IOS Release 12.4(10b)JA
OL-14517-01
Caveats
•
CSCsj88333—When Dot11 ARP cache is enabled on an access point, the access point puts 0 in the
VLAN field of the 802.1q header when it sends out ARP responses on behalf of associated wireless
clients. Thus, the ethernet switch considers the ARP response is for the native VLAN. As a result,
the device sending ARPs for the wireless client may not receive the ARP response.
VLAN field of the 802.1q header when it sends out ARP responses on behalf of associated wireless
clients. Thus, the ethernet switch considers the ARP response is for the native VLAN. As a result,
the device sending ARPs for the wireless client may not receive the ARP response.
Conditions: The problem first appeared in Cisco IOS Release 12.3(8)JA. Dot11 ARP cache is
enabled and the associated wireless clients are on the non-native VLAN. An output ACL is
configured on the radio interface.
enabled and the associated wireless clients are on the non-native VLAN. An output ACL is
configured on the radio interface.
Workaround: Configure the SSID on the native VLAN; or disable dot11 ARP cache; or remove the
output ACL from the dot11radio interface.
output ACL from the dot11radio interface.
•
CSCsk05871—Sometimes packets are not marked as voice to 7921 phones.
Condition: A 7921 phone talking to a non-WMM client (a 7920 phone, for example), a wired client,
or another 7921 client with WMM disabled.
or another 7921 client with WMM disabled.
Workaround: None.
•
CSCsk13961—The following MIB objects display incorrect values for 802.11n radios in 1250 series
access points:
access points:
–
cd11IfAssignedSta
–
cd11IfPhyMacSpecification
–
cd11IfPhyDsssMaxCompatibleRate
–
cd11IfErpOfdmTxPowerLevel5
–
cd11IfClientCurrentTxPowerLeve1
Workaround: None.
•
CSCsk23262—A change in WDS units sometimes triggers shutdown of the radios in an access point
in hot standby mode.
in hot standby mode.
The backup Hot Standby unit takes over as the primary Hot Standby unit when the WDS changes
from primary to backup.
from primary to backup.
Workaround: Adjust cell coverage so that Hot Standby unit can hear only its parent access point.
When the WDS change happens, all the clients attached to access point receive a deauthentication
message, and they are forced to reassociate. When the backup Hot Standby unit receives the
deauthentication message, it can join any access point with matching credentials.
When the WDS change happens, all the clients attached to access point receive a deauthentication
message, and they are forced to reassociate. When the backup Hot Standby unit receives the
deauthentication message, it can join any access point with matching credentials.
•
CSCsk28551—A root bridge sometimes fails to update its bridge table for clients that are connected
to an access point behind a workgroup bridge when these clients reload.
to an access point behind a workgroup bridge when these clients reload.
Workaround: Perform a shut and no-shut radio interface operation on the root bridge.
•
CSCsk35829—On 1410 series bridges, you can select WPAv2 as a WPA setting even though AES
encryption is not supported on 1410 series bridges.
encryption is not supported on 1410 series bridges.
Workaround: None.
•
CSCsk40578—When the access point radio interface is reset, the access point sends a
deauthentication message to the associated wireless clients and removes the client entries from its
association table. The existing PMK cache is not cleared for the WPAv2 clients. However, the access
point should clear the PMK cache because clients do a full re-authentication.
deauthentication message to the associated wireless clients and removes the client entries from its
association table. The existing PMK cache is not cleared for the WPAv2 clients. However, the access
point should clear the PMK cache because clients do a full re-authentication.
Workaround: None.