Cisco Cisco Aironet 350 Access Points Notas de publicación

Descargar
Página de 16
12
Release Notes for Cisco Aironet 340 and 350 Series Access Points and 350 Series Bridges Running Firmware Version 12.00T
OL-3346-01
Caveats
CSCin18914—IP release or renew not occurring with EAP-TLS+MIC+KH+BWR
When a client associates with EAP-TLS + 40/128 bit broadcast key + MIC +Keyhash + Broadcast 
WEP key rotation (10sec), and IP ipconfig release or renew commands are issued, the client releases 
the IP address, never receives it again, and remains EAP authenticated. A ping from the AP to the 
client reaches the client, but doesn’t reveal an IP address. The access point association table shows 
the IP address for the client as 0.0.0.0.
CSCdy29556—Symbol IP phone continuously associates and authenticates to an access point 
configured with multiple VLANs
When a Symbol IP phone is associated to a VoiP VLAN (Symbol extensions enabled), the phone 
associates to the access point and is authenticated approximately every 2 seconds. The Symbol 
phone shows a “No Network” error every 1 to 2 minutes.
It also appears that Symbol phones do not work well when using a non-primary SSID. It is possible 
that the phone does not perform an active Probe and therefore does not hear information about the 
SSID it associated with in the beacon, causing it to reassociate and re authenticate.
There is no workaround for this caveat
.
CSCdy79715—WEP enable issue for 340 series access points
In an AP340 without WEP, the radio gives an error (Fatal) : Failed to start driver for port "awc0" 
(errno=0x006d0002). The radio in the AP will not start. A symptom of this condition is a fatal error 
message: Failed to start driver for port "awc0" (errno=0x006d0002).is seen after upgrade of AP 
firmware.
There is no workaround for this caveat.
CSCdx81372—Access point does not accept version 11.21-generated .ini file
If you download the full configuration .ini from an access point running 11.21, upgrade to version 
12.00T, and then attempt to download the .ini file from an FTP server, the following error message 
displays:
*** No Such MIB Variable as Specified on Initialization File Line xxx! for the 
following variables: 
awcAaaServerAccountingEnabled.x, 
awcVoIPVlanId, awcVoIPVlanEnabled,
awcPublicVlanId.
*** Bad Value for MIB Variable awcVlanEncapMode Specified on Initialization File Line 
xxx (error 13)!
Workaround—When producing .ini files, dump a non-default configuration for version 11.21 
instead of a full configuration.
CSCdw89705—All Ethernet devices behind a client bridge show up as roamed
When a non-root bridge roams from one root bridge to another, messages might appear in the logs 
of the root bridges stating that Ethernet devices connected to the non-root bridge and wireless client 
devices associated to the non-root bridge have roamed. 
You can ignore these messages.
Resolved Caveats
The following caveats have been resolved in firmware version 12.00T:
Resolved: CSCdy13290—Nested repeaters now work with static WEP. 
Resolved: CSCdx22660—Hot Standby now works with LEAP enabled.