Cisco Cisco Aironet 1530i Outdoor Access Point Notas de publicación
13
Release Notes for Cisco Aironet Access Points and Bridges for Cisco IOS Release 15.2(4)JB5
OL-30935-01
Important Notes
This violates RFC 3748.
The workaround for this is to use the commands
dot1x credentials
and
dot1x eap profile
for LEAP
authentication.
For configuration procedures, see the Cisco IOS Software Configuration Guide for Cisco Aironet Access
Points.
Points.
Autonomous AP Will Treat The Sub-interface Tied To Bridge-group1 As The
Native Vlan
Native Vlan
When using a configuration on an autonomous AP where there is no native VLAN defined, each
interface is being dot1q tagged, communication will fail after upgrading to release 15.2(4)JB5 or later.
It appears that the configuration is still correct after the upgrade, but the AP sends the untagged frames
for bridge-group 1, even though the encapsulation is not defined as native. The autonomous AP will treat
the sub-interface tied to bridge-group 1 as the native VLAN, even if it is not defined with the native
keyword: "encapsulation dot1 <vlan> native". The VLAN associated with bridge-group 1 must be set to
native on the connecting switchport configuration
interface is being dot1q tagged, communication will fail after upgrading to release 15.2(4)JB5 or later.
It appears that the configuration is still correct after the upgrade, but the AP sends the untagged frames
for bridge-group 1, even though the encapsulation is not defined as native. The autonomous AP will treat
the sub-interface tied to bridge-group 1 as the native VLAN, even if it is not defined with the native
keyword: "encapsulation dot1 <vlan> native". The VLAN associated with bridge-group 1 must be set to
native on the connecting switchport configuration
The workaround for this is to configure VLAN 100 as the native VLAN on the connected switchport
trunk, even though the encapsulation is not specified as native on the AP.
trunk, even though the encapsulation is not specified as native on the AP.
DHCP Failure When Access Point Renewal Time Is Greater Than Rebind Time
An access point is unable to obtain IP through the same IOS DHCP server when the access point is
running on 15.2x. The problem occurs because the Renewal (T1) time dhcp option 58 is larger than
Rebinding (T2) time dhcp option 59.
running on 15.2x. The problem occurs because the Renewal (T1) time dhcp option 58 is larger than
Rebinding (T2) time dhcp option 59.
Configuring the radius server using the old cli
This cli command was used in the previous releases to configure radius servers:
radius-server host {hostname | ip-address} [auth-port port-number] [acct-port port-number]
[timeout seconds] [retransmit retries] [key string]
[timeout seconds] [retransmit retries] [key string]
Though this command can still be used, we recommend that you use this new command:
radius server {server-name}[auth-port port-number] [acct-port port-number] [timeout seconds]
[retransmit retries] [key string]
[retransmit retries] [key string]
Upgrade from IOS 12.4 to IOS 15 breaks access point L3 Connectivity
The following table shows the behavior change: