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.02T1
OL-3868-01
Caveats
The following is an example Livingston RADIUS server users file entry:
User password = “aironet”
Service-Type = Outbound
cisco-avpair = “aironet:admin-capability=ident+admin”
The following is an example TACACS + server users file entry:
Service - Aironet
Protocol - Shell
cisco-avpair = “aironet:admin-capability=ident+admin”
See Chapter 8 of the Cisco Aironet 340 and 350 Access Point Software Configuration Guide or click
Help on the Authenticator Configuration page for an explanation of the attributes returned by the server.
Help on the Authenticator Configuration page for an explanation of the attributes returned by the server.
Caveats
This section lists open and resolved software issues in firmware version 12.02T1.
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.02T1:
•
CSCdz04380—Incorrect values are advertised for CWMin and CWMax on Voice VLAN.
When a voice VLAN using Cisco IP Phones is configured with default settings (CSMin=31,
CWMax=31), the values advertised by the access point in the beacons and probes are CWMin=7 and
CWMax=255.
CWMax=31), the values advertised by the access point in the beacons and probes are CWMin=7 and
CWMax=255.
There is no workaround for this caveat.
•
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.
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.
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.