Cisco Cisco Aironet 350 Access Points
9
Release Notes for Cisco Aironet 340 and 350 Series Access Points and 350 Series Bridges Running Firmware Version 12.01T
OL-3642-01
Caveats
Unexpected Results on Lost Ethernet
When backbone connectivity is lost on an access point running version 12.01T, the device switches to
repeater mode. Switch to Repeater mode is the default setting for this condition. Therefore, if the access
point’s role in your network is not a repeater access point, make sure you connect it to your wired
network before booting it up. If you do not connect the access point to your network, it switches to the
repeater mode when it fails to detect the presence of an Ethernet connection. When this occurs, wireless
client devices are unable to connect and you cannot correct the problem using a wireless client. The only
way you can change the configuration is through a serial connection using the access point’s command
line interface.
repeater mode. Switch to Repeater mode is the default setting for this condition. Therefore, if the access
point’s role in your network is not a repeater access point, make sure you connect it to your wired
network before booting it up. If you do not connect the access point to your network, it switches to the
repeater mode when it fails to detect the presence of an Ethernet connection. When this occurs, wireless
client devices are unable to connect and you cannot correct the problem using a wireless client. The only
way you can change the configuration is through a serial connection using the access point’s command
line interface.
Caveats
This section lists open and resolved software issues in firmware version 12.01T.
Getting Bug Information on Cisco.com
If you are a registered Cisco user, you can use the Cisco TAC Software Bug Toolkit, which consists of
three tools (Bug Navigator, Bug Watcher, and Search by Bug ID Number) that help you identify existing
bugs (or caveats) in Cisco software products.
three tools (Bug Navigator, Bug Watcher, and Search by Bug ID Number) that help you identify existing
bugs (or caveats) in Cisco software products.
Access the TAC Software Bug Toolkit at
.
Open Caveats
The following caveats have not been resolved for firmware version 12.01T:
•
CSCdz04708—Early 340 series access points are incompatible with VLAN tagging.
Early versions of the 340 series access point are able to set up VLANs, but clients on non-native
VLANs will be unable to transmit and receive large packets. The reason for this is because early 340
series access points were limited to a maximum packet data length of 1500 bytes.
VLANs will be unable to transmit and receive large packets. The reason for this is because early 340
series access points were limited to a maximum packet data length of 1500 bytes.
You can identify an affected access point by browsing to the Ethernet Identification page and
checking the Maximum Packet Data Length parameter. If it is 1500, the failure will occur.
checking the Maximum Packet Data Length parameter. If it is 1500, the failure will occur.
Possible workaround—If you have an early 340 series access point on your network, you can
eliminate the problem by setting the Maximum Packet Data Length parameter for all other devices
to 1400 bytes.
eliminate the problem by setting the Maximum Packet Data Length parameter for all other devices
to 1400 bytes.
•
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 DHCP release and renew commands are issued, the client releases
the IP address, never receives it again, and remains EAP authenticated. A ping from the access point
to the client appears to succeed, but does not reveal an IP address. The access point association table
shows the IP address for the client as 0.0.0.0.
WEP key rotation (10sec), and IP DHCP release and renew commands are issued, the client releases
the IP address, never receives it again, and remains EAP authenticated. A ping from the access point
to the client appears to succeed, but does not reveal an IP address. The access point association table
shows the IP address for the client as 0.0.0.0.