Cisco Cisco 2106 Wireless LAN Controller Notas de publicación

specify the IP address of the backup controller, which allows the access points to fail over to 
controllers outside of the mobility group. This feature is currently supported only through the 
controller CLI.

CCKM support for hybrid REAP—Hybrid-REAP mode supports Layer 2 fast secure roaming 
using Cisco Centralized Key Management (CCKM). This feature prevents the need for full RADIUS 
EAP authentication as the client roams from one access point to another. To use CCKM fast roaming 
with hybrid-REAP access points, you need to configure hybrid-REAP groups.

Debug facility—The debug facility enables you to display all packets going to and from the 
controller CPU. You can enable it for received packets, transmitted packets, or both. By default, all 
packets received by the debug facility are displayed. However, you can define access control lists 
(ACLs) to filter packets before they are displayed. Packets not passing the ACLs are discarded 
without being displayed.

DHCP proxy—When DHCP proxy is disabled, the controller passes DHCP packets without any 
modification from the client to the upstream VLAN and vice versa. As a result, the internal DHCP 
server cannot be used when DHCP proxy is disabled. The ability to disable DHCP proxy allows 
organizations to use DHCP servers that do not support Cisco’s native proxy mode of operation. It 
should be disabled only when required by the existing infrastructure.

EDCA support—You can configure enhanced distributed channel access (EDCA) profiles per radio 
band to provide preferential wireless channel access for voice, video, and other quality-of-service 
(QoS) traffic. The available options are WMM (the default value), Spectralink Voice Priority, Voice 
Optimized, and Voice & Video Optimized.

In controller software release 4.1, the EDCA profiles are not configurable per radio and do 
not offer four configuration options. Therefore, you might need to reconfigure the EDCA 
profiles after upgrading to 4.2.61.0.

Hybrid-REAP groups—To better organize and manage your hybrid-REAP access points, you can 
create hybrid-REAP groups and assign specific access points to them. All of the hybrid-REAP 
access points in a group share the same CCKM, WLAN, and backup RADIUS server configuration 
information. This feature is helpful if you have multiple hybrid-REAP access points in a remote 
office or on the floor of a building and you want to configure them all at once. For example, you can 
configure a backup RADIUS server for a hybrid-REAP group rather than having to configure the 
same server on each access point. Per controller, you can configure up to 20 hybrid-REAP groups 
with up to 25 access points per group.

Hybrid-REAP 802.1X support—Hybrid-REAP mode supports 802.1X authentication to a backup 
AAA server when the WAN link is down. To support 802.1X EAP authentication, hybrid-REAP 
access points in standalone mode need to have their own RADIUS servers to authenticate clients. 
You can configure a backup RADIUS server for individual hybrid-REAP access points by using the 
controller CLI or for hybrid-REAP groups by using either the GUI or CLI. A backup server 
configured for an individual access point overrides the RADIUS server configuration for a 
hybrid-REAP group.

IPv4 and IPv6 support on the same WLAN—You can enable IPv6 bridging and IPv4 web 
authentication on the same WLAN. The controller bridges IPv6 traffic from all clients on the WLAN 
while IPv4 traffic goes through the normal web authentication process. The controller begins 
bridging IPv6 as soon as the client associates and even before web authentication for IPv4 clients is 
complete.