Cisco Wireless Controller Configuration Guide, Release 7.6
Cisco Wireless Controller Configuration Guide, Release 7.6
Cisco Wireless Controller Configuration Guide, Release 7.6
6
First Published: 2013-12-19
Last Modified: 2015-07-27
Americas Headquarters
Cisco Systems, Inc.
170 West Tasman Drive
San Jose, CA 95134-1706
USA
http://www.cisco.com
Tel: 408 526-4000
800 553-NETS (6387)
Fax: 408 527-0883
THE SPECIFICATIONS AND INFORMATION REGARDING THE PRODUCTS IN THIS MANUAL ARE SUBJECT TO CHANGE WITHOUT NOTICE. ALL STATEMENTS,
INFORMATION, AND RECOMMENDATIONS IN THIS MANUAL ARE BELIEVED TO BE ACCURATE BUT ARE PRESENTED WITHOUT WARRANTY OF ANY KIND,
EXPRESS OR IMPLIED. USERS MUST TAKE FULL RESPONSIBILITY FOR THEIR APPLICATION OF ANY PRODUCTS.
THE SOFTWARE LICENSE AND LIMITED WARRANTY FOR THE ACCOMPANYING PRODUCT ARE SET FORTH IN THE INFORMATION PACKET THAT SHIPPED WITH
THE PRODUCT AND ARE INCORPORATED HEREIN BY THIS REFERENCE. IF YOU ARE UNABLE TO LOCATE THE SOFTWARE LICENSE OR LIMITED WARRANTY,
CONTACT YOUR CISCO REPRESENTATIVE FOR A COPY.
The Cisco implementation of TCP header compression is an adaptation of a program developed by the University of California, Berkeley (UCB) as part of UCB's public domain version
of the UNIX operating system. All rights reserved. Copyright © 1981, Regents of the University of California.
NOTWITHSTANDING ANY OTHER WARRANTY HEREIN, ALL DOCUMENT FILES AND SOFTWARE OF THESE SUPPLIERS ARE PROVIDED “AS IS" WITH ALL FAULTS.
CISCO AND THE ABOVE-NAMED SUPPLIERS DISCLAIM ALL WARRANTIES, EXPRESSED OR IMPLIED, INCLUDING, WITHOUT LIMITATION, THOSE OF
MERCHANTABILITY, FITNESS FOR A PARTICULAR PURPOSE AND NONINFRINGEMENT OR ARISING FROM A COURSE OF DEALING, USAGE, OR TRADE PRACTICE.
IN NO EVENT SHALL CISCO OR ITS SUPPLIERS BE LIABLE FOR ANY INDIRECT, SPECIAL, CONSEQUENTIAL, OR INCIDENTAL DAMAGES, INCLUDING, WITHOUT
LIMITATION, LOST PROFITS OR LOSS OR DAMAGE TO DATA ARISING OUT OF THE USE OR INABILITY TO USE THIS MANUAL, EVEN IF CISCO OR ITS SUPPLIERS
HAVE BEEN ADVISED OF THE POSSIBILITY OF SUCH DAMAGES.
Any Internet Protocol (IP) addresses and phone numbers used in this document are not intended to be actual addresses and phone numbers. Any examples, command display output, network
topology diagrams, and other figures included in the document are shown for illustrative purposes only. Any use of actual IP addresses or phone numbers in illustrative content is unintentional
and coincidental.
Cisco and the Cisco logo are trademarks or registered trademarks of Cisco and/or its affiliates in the U.S. and other countries. To view a list of Cisco trademarks, go to this URL: http://
www.cisco.com/go/trademarks. Third-party trademarks mentioned are the property of their respective owners. The use of the word partner does not imply a partnership
relationship between Cisco and any other company. (1110R)
Troubleshooting 120
CHAPTER 18 Configuring Authentication for the Controller and NTP/SNTP Server 175
Information About Configuring Authentication for the Controller and NTP/SNTP Server 175
Configuring the NTP/SNTP Server for Authentication (GUI) 175
Configuring the NTP/SNTP Server for Authentication (CLI) 176
CHAPTER 33 Information About Using Cisco 5500 Series Controller USB Console Port 337
USB Console OS Compatibility 337
Changing the Cisco USB Systems Management Console COM Port to an Unused Port 338
CHAPTER 84 Configuring a Fallback Policy with MAC Filtering and Web Authentication 641
Information About Fallback Policy with MAC Filtering and Web Authentication 641
Configuring a Fallback Policy with MAC Filtering and Web Authentication (GUI) 642
Configuring a Fallback Policy with MAC Filtering and Web Authentication (CLI) 642
Information About VLAN Tagging for CAPWAP Frames from Access Points 770
Configuring VLAN Tagging for CAPWAP Frames from Access Points (GUI) 770
Configuring VLAN Tagging for CAPWAP Frames from Access Points (CLI) 771
Using DHCP Option 43 and DHCP Option 60 771
Troubleshooting the Access Point Join Process 772
Configuring the Syslog Server for Access Points (CLI) 773
Viewing Access Point Join Information 774
Viewing Access Point Join Information (GUI) 774
Viewing Access Point Join Information (CLI) 775
Sending Debug Commands to Access Points Converted to Lightweight Mode 777
Understanding How Converted Access Points Send Crash Information to the Controller 777
Understanding How Converted Access Points Send Radio Core Dumps to the
Controller 777
Retrieving Radio Core Dumps (CLI) 777
Uploading Radio Core Dumps (GUI) 778
Uploading Radio Core Dumps (CLI) 778
Uploading Memory Core Dumps from Converted Access Points 779
Uploading Access Point Core Dumps (GUI) 779
Uploading Access Point Core Dumps (CLI) 779
Viewing the AP Crash Log Information 780
Viewing the AP Crash Log information (GUI) 780
Viewing the AP Crash Log information (CLI) 780
Displaying MAC Addresses for Converted Access Points 781
Disabling the Reset Button on Access Points Converted to Lightweight Mode 781
Configuring a Static IP Address on a Lightweight Access Point 781
Configuring a Static IP Address (GUI) 782
Configuring a Static IP Address (CLI) 782
Supporting Oversized Access Point Images 783
Recovering the Access Point—Using the TFTP Recovery Procedure 784
CHAPTER 118 Retrieving the Unique Device Identifier on Controllers and Access Points 837
Information About Retrieving the Unique Device Identifier on Controllers and Access
Points 837
Retrieving the Unique Device Identifier on Controllers and Access Points (GUI) 837
Retrieving the Unique Device Identifier on Controllers and Access Points (CLI) 838
CHAPTER 147 Configuring Dynamic Anchoring for Clients with Static IP Addresses 1015
Information About Dynamic Anchoring for Clients with Static IP 1015
How Dynamic Anchoring of Static IP Clients Works 1015
Restrictions on Dynamic Anchoring for Clients With Static IP Addresses 1016
Configuring Dynamic Anchoring of Static IP Clients (GUI) 1017
Configuring Dynamic Anchoring of Static IP Clients (CLI) 1017
Audience
This publication is for experienced network administrators who configure and maintain Cisco wireless
controllers and Cisco lightweight access points.
Conventions
This document uses the following conventions:
Table 1: Conventions
Convention Indication
bold font Commands and keywords and user-entered text appear in bold font.
italic font Document titles, new or emphasized terms, and arguments for which you supply
values are in italic font.
[] Elements in square brackets are optional.
{x | y | z } Required alternative keywords are grouped in braces and separated by vertical
bars.
[x|y|z] Optional alternative keywords are grouped in brackets and separated by vertical
bars.
Convention Indication
string A nonquoted set of characters. Do not use quotation marks around the string.
Otherwise, the string will include the quotation marks.
courier font Terminal sessions and information the system displays appear in courier font.
<> Nonprinting characters such as passwords are in angle brackets.
[] Default responses to system prompts are in square brackets.
!, # An exclamation point (!) or a pound sign (#) at the beginning of a line of code
indicates a comment line.
Note Means reader take note. Notes contain helpful suggestions or references to material not covered in the
manual.
Tip Means the following information will help you solve a problem.
Caution Means reader be careful. In this situation, you might perform an action that could result in equipment
damage or loss of data.
Related Documentation
• For information about Cisco Wireless Controller software, see
http://www.cisco.com/c/en/us/support/wireless/wireless-lan-controller-software/tsd-products-support-series-home.html
• For other information about Cisco 8540 Wireless Controller, see
http://www.cisco.com/c/en/us/support/wireless/8500-series-wireless-controllers/tsd-products-support-series-home.html
• Cisco 8540 Wireless Controller Deployment Guide
Introduction
Cisco Wireless is designed to provide 802.11 wireless networking solutions for enterprises and service
providers. Cisco Wireless simplifies deploying and managing large-scale wireless LANs and enables a unique
best-in-class security infrastructure. The operating system manages all data client, communications, and system
administration functions, performs radio resource management (RRM) functions, manages system-wide
mobility policies using the operating system security solution, and coordinates all security functions using
the operating system security framework.
Cisco Wireless solution consists of Cisco wireless controllers (Cisco WLCs) and their associated lightweight
access points controlled by the operating system, all concurrently managed by any or all of the operating
system user interfaces:
• An HTTP and/or HTTPS full-featured Web User Interface hosted by Cisco WLCs can be used to
configure and monitor individual Cisco WLCs.
• A full-featured command-line interface (CLI) can be used to configure and monitor individual Cisco
Cisco WLCs.
• The Cisco Prime Infrastructure, which you use to configure and monitor one or more Cisco WLCs and
associated access points. The Prime Infrastructure has tools to facilitate large-system monitoring and
The Cisco Wireless solution supports client data services, client monitoring and control, and all rogue access
point detection, monitoring, and containment functions. It uses lightweight access points, Cisco WLCs, and
the optional Cisco Prime Infrastructure to provide wireless services to enterprises and service providers.
For detailed information about Cisco Wireless solution, see the Enterprise Mobility Design Guide at http://
www.cisco.com/c/en/us/td/docs/wireless/controller/8-1/Enterprise-Mobility-8-1-Design-Guide/Enterprise_
Mobility_8-1_Deployment_Guide.html.
Single-Controller Deployments
A standalone controller can support lightweight access points across multiple floors and buildings
simultaneously and support the following features:
• Autodetecting and autoconfiguring lightweight access points as they are added to the network.
• Full control of lightweight access points.
• Lightweight access points connect to controllers through the network. The network equipment may or
may not provide Power over Ethernet (PoE) to the access points.
Some controllers use redundant Gigabit Ethernet connections to bypass single network failures.
Note Some controllers can connect through multiple physical ports to multiple subnets in the network. This
feature can be helpful when you want to confine multiple VLANs to separate subnets.
Multiple-Controller Deployments
Each controller can support lightweight access points across multiple floors and buildings simultaneously.
However, full functionality of the Cisco wireless LAN solution occurs when it includes multiple controllers.
A multiple-controller system has the following additional features:
• Autodetecting and autoconfiguring RF parameters as the controllers are added to the network.
• Same-subnet (Layer 2) roaming and inter-subnet (Layer 3) roaming.
• Automatic access point failover to any redundant controller with a reduced access point load.
The following figure shows a typical multiple-controller deployment. The figure also shows an optional
dedicated management network and the three physical connection types between the network and the controllers.
Figure 2: Typical Multiple-Controller Deployment
The WEP problem can be further solved using the following industry-standard Layer 3 security solutions:
• Passthrough VPNs
• Local and RADIUS MAC address filtering
• Local and RADIUS user/password authentication
• Manual and automated disabling to block access to network services. In manual disabling, you block
access using client MAC addresses. In automated disabling, which is always active, the operating system
software automatically blocks access to network services for a user-defined period of time when a client
fails to authenticate for a fixed number of consecutive attempts. This feature can be used to deter
brute-force login attacks.
These and other security features use industry-standard authorization and authentication methods to ensure
the highest possible security for your business-critical wireless LAN traffic.
Note The IPv4 network layer protocol is supported for transport through a CAPWAP or LWAPP controller
system. IPv6 (for clients only) and AppleTalk are also supported but only on Cisco 5500 Series Controllers
and the Cisco WiSM2. Other Layer 3 protocols (such as IPX, DECnet Phase IV, OSI CLNP, and so on)
and Layer 2 (bridged) protocols (such as LAT and NetBeui) are not supported.
Operational Requirements
The requirement for Layer 3 LWAPP communications is that the controller and lightweight access points can
be connected through Layer 2 devices on the same subnet or connected through Layer 3 devices across subnets.
Another requirement is that the IP addresses of access points should be either statically assigned or dynamically
assigned through an external DHCP server.
The requirement for Layer 3 CAPWAP communications is that the controller and lightweight access points
can be connected through Layer 2 devices on the same subnet or connected through Layer 3 devices across
subnets.
Configuration Requirements
When you are operating the Cisco wireless LAN solution in Layer 2 mode, you must configure a management
interface to control your Layer 2 communications.
When you are operating the Cisco wireless LAN solution in Layer 3 mode, you must configure an AP-manager
interface to control lightweight access points and a management interface as configured for Layer 2 mode.
Note Lightweight access points without a primary, secondary, and tertiary Cisco WLC assigned always search
for a master Cisco WLC first upon reboot. After adding lightweight access points through the master Cisco
WLC, you should assign primary, secondary, and tertiary Cisco WLCs to each access point. We recommend
that you disable the master setting on all Cisco WLCs after initial configuration.
Client Location
When you use Cisco Prime Infrastructure in your Cisco wireless LAN solution, controllers periodically
determine the client, rogue access point, rogue access point client, radio frequency ID (RFID) tag location
and store the locations in the Cisco Prime Infrastructure database.
Note We recommend that you assign one set of VLANs for WLANs and a different set of VLANs for
management interfaces to ensure that controllers operate with optimum performance and ease of
management.
If management over wireless is enabled across the Cisco Wireless solution, you can manage the system across
the enabled WLAN using CLI and Telnet, HTTP/HTTPS, and SNMP.
File Transfers
You can upload and download operating system code, configuration, and certificate files to and from the
controller using the GUI, CLI, or Cisco NCSCisco Prime Infrastructure.
When you are using PoE, you run a single CAT-5 cable from each lightweight access point to PoE-equipped
network elements, such as a PoE power hub or a Cisco WLAN solution single-line PoE injector. When the
PoE equipment determines that the lightweight access point is PoE-enabled, it sends 48 VDC over the unused
pairs in the Ethernet cable to power the access point.
The PoE cable length is limited by the 100BASE-T or 10BASE-T specification to 100 m or 200 m, respectively.
In multiple-controller deployments, if one controller fails, the access points perform the following tasks:
• If the lightweight access point has a primary, secondary, and tertiary controller assigned, it attempts to
associate with that controller.
• If the access point has no primary, secondary, or tertiary controllers assigned or if its primary, secondary,
or tertiary controllers are unavailable, it attempts to associate with a master controller.
• If the access point finds no master controller, it attempts to contact stored mobility group members by
the IP address.
• If the mobility group members are available, and if the lightweight access point has no primary, secondary,
and tertiary controllers assigned and there is no master controller active, it attempts to associate with
the least-loaded controller to respond to its discovery messages.
When controllers are deployed, if one controller fails, active access point client sessions are momentarily
dropped while the dropped access point associates with another controller, allowing the client device to
immediately reassociate and reauthenticate.
To know more about high availability, see
http://www.cisco.com/c/en/us/support/docs/wireless/4400-series-wireless-lan-controllers/107250-ha-wlc.html.
Note On Cisco 5500 Series Controllers, you can use either the RJ-45 console port or the USB console port. If
you use the USB console port, plug the 5-pin mini Type B connector into the controller’s USB console
port and the other end of the cable into the PC’s USB Type A port. The first time that you connect a
Windows PC to the USB console port, you are prompted to install the USB console driver. Follow the
installation prompts to install the driver. The USB console driver maps to a COM port on your PC; you
then need to map the terminal emulator application to the COM port.
Step 1 Connect one end of a null-modem serial cable to the controller’s console port and the other end to your PC’s serial port.
Step 2 Start the PC’s VT-100 terminal emulation program.
Step 3 Configure the terminal emulation program for these parameters:
• 9600 baud
• 8 data bits
• 1 stop bit
• No parity
• No hardware flow control
Step 4 Plug the AC power cord into the controller and a grounded 100 to 240 VAC, 50/60-Hz electrical outlet.Turn on the
power supply. The bootup script displays operating system software initialization (code download and power-on self
test verification) and basic configuration.
If the controller passes the power-on self test, the bootup script runs the configuration wizard, which prompts you for
basic configuration input.
Step 1 Connect your PC to the service port and configure it to use the same subnet as the controller.
Note In case of Cisco 2504 WLC, connect your PC to the port 2 on the controller and configure to use the same
subnet.
Step 2 Browse to http://192.168.1.1. The configuration wizard appears.
Note You can use both HTTP and HTTPS when using the service port interface. HTTPS is enabled by default and
HTTP can also be enabled. The default IP address to connect to the service port interface is 192.168.1.1.
Note For the initial GUI Configuration Wizard only, you cannot access the Cisco WLC using IPv6 address.
Step 3 In the System Name box, enter the name that you want to assign to this Cisco WLC. You can enter up to 31 ASCII
characters.
Step 4 In the User Name box, enter the administrative username to be assigned to this Cisco WLC. You can enter up to 24
ASCII characters. The default username is admin.
Step 5 In the Password and Confirm Password boxes, enter the administrative password to be assigned to this Cisco WLC.
You can enter up to 24 ASCII characters. The default password is admin.
Starting in release 7.0.116.0, the following password policy has been implemented:
• The password must contain characters from at least three of the following classes:
◦Lowercase letters
◦Uppercase letters
◦Digits
◦Special characters
• No character in the password must be repeated more than three times consecutively.
• The new password must not be the same as the associated username and not be the username reversed.
• The password must not be cisco, ocsic, or any variant obtained by changing the capitalization of letters of the word
Cisco. In addition, you cannot substitute 1, I, or ! for i, 0 for o, or $ for s.
Step 7 If you want to enable Simple Network Management Protocol (SNMP) v1 mode for this Cisco WLC, choose Enable
from the SNMP v1 Mode drop-down list. Otherwise, leave this parameter set to Disable.
Note SNMP manages nodes (servers, workstations, routers, switches, and so on) on an IP network. Currently, there
are three versions of SNMP: SNMPv1, SNMPv2c, and SNMPv3.
Step 8 If you want to enable SNMPv2c mode for this Cisco WLC, leave this parameter set to Enable. Otherwise, choose Disable
from the SNVP v2c Mode drop-down list.
Step 9 If you want to enable SNMPv3 mode for this Cisco WLC, leave this parameter set to Enable. Otherwise, choose Disable
from the SNVP v3 Mode drop-down list.
Step 10 Click Next.
Step 11 When the following message appears, click OK:
Step 12 If you want the Cisco WLC’s service-port interface to obtain an IP address from a DHCP server, check the DHCP
Protocol Enabled check box. If you do not want to use the service port or if you want to assign a static IP address to
the service port, leave the check box unchecked.
Note The service-port interface controls communications through the service port. Its IP address must be on a different
subnet from the management interface. This configuration enables you to manage the controller directly or
through a dedicated management network to ensure service access during network downtime.
Step 13 Perform one of the following:
• If you enabled DHCP, clear out any entries in the IP Address and Netmask text boxes, leaving them blank.
• If you disabled DHCP, enter the static IP address and netmask for the service port in the IP Address and Netmask
text boxes.
Step 15 To enable link aggregation (LAG), choose Enabled from the Link Aggregation (LAG) Mode drop-down list. To disable
LAG, leave this text box set to Disabled.
Step 16 Click Next.
The Management Interface Configuration page is displayed.
Note The management interface is the default interface for in-band management of the controller and connectivity
to enterprise services such as AAA servers.
Step 17 In the VLAN Identifier box, enter the VLAN identifier of the management interface (either a valid VLAN identifier or
0 for an untagged VLAN). The VLAN identifier should be set to match the switch interface configuration.
Step 18 In the IP Address box, enter the IP address of the management interface.
Step 19 In the Netmask box, enter the IP address of the management interface netmask.
Step 20 In the Gateway box, enter the IP address of the default gateway.
Step 21 In the Port Number box, enter the number of the port assigned to the management interface. Each interface is mapped
to at least one primary port.
Step 22 In the Backup Port box, enter the number of the backup port assigned to the management interface. If the primary port
for the management interface fails, the interface automatically moves to the backup port.
Step 23 In the Primary DHCP Server box, enter the IP address of the default DHCP server that will supply IP addresses to
clients, the controller’s management interface, and optionally, the service port interface.
Step 24 In the Secondary DHCP Server box, enter the IP address of an optional secondary DHCP server that will supply IP
addresses to clients, the controller’s management interface, and optionally, the service port interface.
Step 25 Click Next. The AP-Manager Interface Configuration page is displayed.
Note This screen does not appear for Cisco 5508 WLCs because you are not required to configure an AP-manager
interface. The management interface acts like an AP-manager interface by default.
Step 26 In the IP Address box, enter the IP address of the AP-manager interface.
Step 27 Click Next. The Miscellaneous Configuration page is displayed.
Step 28 In the RF Mobility Domain Name box, enter the name of the mobility group/RF group to which you want the controller
to belong.
Note Although the name that you enter here is assigned to both the mobility group and the RF group, these groups
are not identical. Both groups define clusters of controllers, but they have different purposes. All of the controllers
in an RF group are usually also in the same mobility group and vice versa. However, a mobility group facilitates
scalable, system-wide mobility and controller redundancy while an RF group facilitates scalable, system-wide
dynamic RF management.
Step 29 The Configured Country Code(s) box shows the code for the country in which the controller will be used. If you want
to change the country of operation, check the check box for the desired country.
Note You can choose more than one country code if you want to manage access points in multiple countries from a
single controller. After the configuration wizard runs, you must assign each access point joined to the controller
to a specific country.
Step 30 Click Next.
Step 31 When the following message appears, click OK:
Warning! To maintain regulatory compliance functionality, the country code
setting may only be modified by a network administrator or qualified IT professional.
Ensure that proper country codes are selected before proceeding.?
Step 32 In the IP Address box, enter the IP address of the Cisco WLC’s virtual interface. You should enter a fictitious, unassigned
IP address.
Note The virtual interface is used to support mobility management, DHCP relay, and embedded Layer 3 security
such as guest web authentication and VPN termination. All controllers within a mobility group must be configured
with the same virtual interface IP address.
Step 33 In the DNS Host Name box, enter the name of the Domain Name System (DNS) gateway used to verify the source of
certificates when Layer 3 web authorization is enabled.
Note To ensure connectivity and web authentication, the DNS server should always point to the virtual interface. If
a DNS hostname is configured for the virtual interface, then the same DNS hostname must be configured on
the DNS servers used by the client.
Step 35 In the Profile Name box, enter up to 32 alphanumeric characters for the profile name to be assigned to this WLAN.
Step 36 In the WLAN SSID box, enter up to 32 alphanumeric characters for the network name, or service set identifier (SSID).
The SSID enables basic functionality of the Cisco WLC and allows access points that have joined the controller to enable
their radios.
Step 37 Click Next.
Step 38 When the following message appears, click OK:
Default Security applied to WLAN is: [WPA2(AES)][Auth(802.1x)]. You can change
this after the wizard is complete and the system is rebooted.?
Step 39 In the Server IP Address box, enter the IP address of the RADIUS server.
Step 40 From the Shared Secret Format drop-down list, choose ASCII or Hex to specify the format of the shared secret.
Note Due to security reasons, the RADIUS shared secret key reverts to ASCII mode even if you have selected HEX
as the shared secret format from the Shared Secret Format drop-down list.
Step 41 In the Shared Secret and Confirm Shared Secret boxes, enter the secret key used by the RADIUS server.
Step 42 In the Port Number box, enter the communication port of the RADIUS server. The default value is 1812.
Step 43 To enable the RADIUS server, choose Enabled from the Server Status drop-down list. To disable the RADIUS server,
leave this box set to Disabled.
Step 44 Click Apply. The 802.11 Configuration page is displayed.
Step 45 To enable the 802.11a, 802.11b, and 802.11g lightweight access point networks, leave the 802.11a Network Status,
802.11b Network Status, and 802.11g Network Status check boxes checked. To disable support for any of these
networks, uncheck the check boxes.
Step 46 To enable the controller’s radio resource management (RRM) auto-RF feature, leave the Auto RF check box selected.
To disable support for the auto-RF feature, uncheck this check box.
Note The auto-RF feature enables the controller to automatically form an RF group with other controllers. The group
dynamically elects a leader to optimize RRM parameter settings, such as channel and transmit power assignment,
for the group.
Step 48 To manually configure the system time on your controller, enter the current date in Month/DD/YYYY format and the
current time in HH:MM:SS format.
Step 49 To manually set the time zone so that Daylight Saving Time (DST) is not set automatically, enter the local hour difference
from Greenwich Mean Time (GMT) in the Delta Hours box and the local minute difference from GMT in the Delta
Mins box.
Note When manually setting the time zone, enter the time difference of the local current time zone with respect to
GMT (+/–). For example, Pacific time in the United States is 8 hours behind GMT. Therefore, it is entered as
–8.
Step 51 Click Save and Reboot to save your configuration and reboot the Cisco WLC.
Step 52 When the following message appears, click OK:
Configuration will be saved and the controller will be
rebooted. Click ok to confirm.?
The Cisco WLC saves your configuration, reboots, and prompts you to log on.
Step 1 When prompted to terminate the AutoInstall process, enter yes. If you do not enter yes, the AutoInstall process begins
after 30 seconds.
Note The AutoInstall feature downloads a configuration file from a TFTP server and then loads the configuration
onto the controller automatically.
Step 2 Enter the system name, which is the name that you want to assign to the controller. You can enter up to 31 ASCII
characters.
Step 3 Enter the administrative username and password to be assigned to this controller. You can enter up to 24 ASCII characters
for each.
Starting in release 7.0.116.0, the following password policy has been implemented:
• The password must contain characters from at least three of the following classes:
• Lowercase letters
• Uppercase letters
• Digits
• Special characters
• No character in the password must be repeated more than three times consecutively.
• The new password must not be the same as the associated username and not be the username reversed.
• The password must not be cisco, ocsic, or any variant obtained by changing the capitalization of letters of the word
Cisco. In addition, you cannot substitute 1, I, or ! for i, 0 for o, or $ for s.
Step 4 If you want the controller’s service-port interface to obtain an IP address from a DHCP server, enter DHCP. If you do
not want to use the service port or if you want to assign a static IP address to the service port, enter none.
Note The service-port interface controls communications through the service port. Its IP address must be on a different
subnet from the management interface. This configuration enables you to manage the controller directly or
through a dedicated management network to ensure service access during network downtime.
Step 5 If you entered none in Step 4, enter the IP address and netmask for the service-port interface on the next two lines.
Step 6 Enable or disable link aggregation (LAG) by choosing yes or NO.
Step 7 Enter the IP address of the management interface.
Note The management interface is the default interface for in-band management of the controller and connectivity
to enterprise services such as AAA servers.
Step 8 Enter the IP address of the management interface netmask.
Step 9 Enter the IP address of the default router.
Step 10 Enter the VLAN identifier of the management interface (either a valid VLAN identifier or 0 for an untagged VLAN).
The VLAN identifier should be set to match the switch interface configuration.
Step 11 Enter the IP address of the default DHCP server that will supply IP addresses to clients, the management interface of
the controller, and optionally, the service port interface. Enter the IP address of the AP-manager interface.
Note This prompt does not appear for Cisco 5500 Series Controllers because you are not required to configure an
AP-manager interface. The management interface acts like an AP-manager interface by default.
Step 12 Enter the IP address of the controller’s virtual interface. You should enter a fictitious unassigned IP address.
Note The virtual interface is used to support mobility management, DHCP relay, and embedded Layer 3 security
such as guest web authentication and VPN termination. All controllers within a mobility group must be configured
with the same virtual interface IP address.
Step 13 If desired, enter the name of the mobility group/RF group to which you want the controller to belong.
Note Although the name that you enter here is assigned to both the mobility group and the RF group, these groups
are not identical. Both groups define clusters of controllers, but they have different purposes. All of the controllers
in an RF group are usually also in the same mobility group and vice versa. However, a mobility group facilitates
scalable, system-wide mobility and controller redundancy while an RF group facilitates scalable, system-wide
dynamic RF management.
Step 14 Enter the network name or service set identifier (SSID). The SSID enables basic functionality of the controller and allows
access points that have joined the controller to enable their radios.
Step 15 Enter YES to allow clients to assign their own IP address or no to require clients to request an IP address from a DHCP
server.
Step 16 To configure a RADIUS server now, enter YES and then enter the IP address, communication port, and secret key of
the RADIUS server. Otherwise, enter no. If you enter no, the following message appears: “Warning! The default WLAN
security policy requires a RADIUS server. Please see the documentation for more details.”
Step 17 Enter the code for the country in which the controller will be used.
Note Enter help to view the list of available country
codes.
Note You can enter more than one country code if you want to manage access points in multiple countries from a
single controller. To do so, separate the country codes with a comma (for example, US,CA,MX). After the
configuration wizard runs, you need to assign each access point joined to the controller to a specific country.
Step 18 Enable or disable the 802.11b, 802.11a, and 802.11g lightweight access point networks by entering YES or no.
Step 19 Enable or disable the controller’s radio resource management (RRM) auto-RF feature by entering YES or no.
Note The auto-RF feature enables the controller to automatically form an RF group with other controllers. The group
dynamically elects a leader to optimize RRM parameter settings, such as channel and transmit power assignment,
for the group.
Step 20 If you want the controller to receive its time setting from an external Network Time Protocol (NTP) server when it powers
up, enter YES to configure an NTP server. Otherwise, enter no.
Note The controller network module installed in a Cisco Integrated Services Router does not have a battery and cannot
save a time setting. Therefore, it must receive a time setting from an external NTP server when it powers up.
Step 21 If you entered no in Step 20 and want to manually configure the system time on your controller now, enter YES. If you
do not want to configure the system time now, enter no.
Step 22 If you entered YES in Step 21, enter the current date in the MM/DD/YY format and the current time in the HH:MM:SS
format.
After you have completed step 22, the wizard prompts you to configure IPv6 parameters. Enter yes to proceed.
Step 23 Enter the service port interface IPv6 address configuration. You can enter either static or SLAAC.
• If you entered, SLAAC, then IPv6 address is autoconfigured.
• If you entered, static, you need to enter the IPv6 address and its prefix length of the service interface.
Once the RADIUS server configuration is complete, the wizard prompts to configure IPv6 NTP server. Enter yes.
Step 30 Enter the IPv6 address of the NTP server.
Step 31 When prompted to verify that the configuration is correct, enter yes or NO.
The Cisco WLC saves your configuration when you enter yes, reboots, and prompts you to log on.
Note We recommend that you enable the HTTPS interface and disable the HTTP interface to ensure more robust
security.
• To view the Main Dashboard that is introduced in Release 8.1.102.0, you must enable JavaScript on the
web browser.
• You can use either the service port interface or the management interface to access the GUI. We
recommend that you use the service-port interface.
• You can use both HTTP and HTTPS when using the service port interface. HTTPS is enabled by default
and HTTP can also be enabled. The default IP address to connect to the service port interface is
192.168.1.1.
• Click Help at the top of any page in the GUI to display online help. You might need to disable your
browser’s pop-up blocker to view the online help.
Note Do not configure TACACS authentication when the controller is set to use local authentication.
Step 1 Enter the IP address in your browser’s address bar. For a secure connection, enter https://ip-address. For a less secure
connection, enter http://ip-address.
Step 2 When prompted, enter a valid username and password, and click OK.
The Summary page is displayed.
Note The administrative username and password that you created in the configuration wizard are case sensitive. The
default username is admin, and the default password is admin.
Step 2 To enable web mode, which allows users to access the controller GUI using “http://ip-address,” choose Enabled from
the HTTP Access drop-down list. Otherwise, choose Disabled. The default value is Disabled. Web mode is not a secure
connection.
Step 3 To enable secure web mode, which allows users to access the controller GUI using “https://ip-address,” choose Enabled
from the HTTPS Access drop-down list. Otherwise, choose Disabled. The default value is Enabled. Secure web mode
is a secure connection.
Step 4 In the Web Session Timeout text box, enter the amount of time, in minutes, before the web session times out due to
inactivity. You can enter a value between 10 and 160 minutes (inclusive). The default value is 30 minutes.
Step 5 Click Apply.
Step 6 If you enabled secure web mode in Step 3, the controller generates a local web administration SSL certificate and
automatically applies it to the GUI. The details of the current certificate appear in the middle of the HTTP-HTTPS
Configuration page.
Note If desired, you can delete the current certificate by clicking Delete Certificate and have the controller generate
a new certificate by clicking Regenerate Certificate.
Step 7 Click Save Configuration.
Step 3 Enable or disable secure web mode with increased security by entering this command:
config network secureweb cipher-option high {enable | disable}
This command allows users to access the controller GUI using “https://ip-address” but only from browsers that support
128-bit (or larger) ciphers. The default value is disabled.
Step 4 Enable or disable SSLv2 for web administration by entering this command:
config network secureweb cipher-option sslv2 {enable | disable}
If you disable SSLv2, users cannot connect using a browser configured with SSLv2 only. They must use a browser that
is configured to use a more secure protocol such as SSLv3 or later. The default value is disabled.
Step 5 Enable or disable preference for RC4-SHA (Rivest Cipher 4-Secure Hash Algorithm) cipher suites (over CBC cipher
suites) for web authentication and web administration by entering this command:
config network secureweb cipher-option rc4-preference {enable | disable}
Step 6 Verify that the controller has generated a certificate by entering this command:
show certificate summary
Information similar to the following appears:
Step 8 Save the SSL certificate, key, and secure web password to nonvolatile RAM (NVRAM) so that your changes are retained
across reboots by entering this command:
save config
Note Chained certificates are supported for web authentication only and not for the
management certificate.
Note Every HTTPS certificate contains an embedded RSA key. The length of the key can
vary from 512 bits, which is relatively insecure, to thousands of bits, which is very
secure. When you obtain a new certificate from a Certificate Authority, make sure that
the RSA key embedded in the certificate is at least 768 bits long.
Step 1 On the HTTP Configuration page, select the Download SSL Certificate check box.
Step 2 In the Server IP Address text box, enter the IP address of the TFTP server.
Step 3 In the Maximum Retries text box, enter the maximum number of times that the TFTP server attempts to download the
certificate.
Step 4 In the Timeout text box, enter the amount of time (in seconds) that the TFTP server attempts to download the certificate.
Step 5 In the Certificate File Path text box, enter the directory path of the certificate.
Step 6 In the Certificate File Name text box, enter the name of the certificate (webadmincert_name.pem).
Step 7 (Optional) In the Certificate Password text box, enter a password to encrypt the certificate.
Step 8 Click Apply.
Step 9 Click Save Configuration.
Step 10 Choose Commands > Reboot > Reboot > Save and Reboot to reboot the controller for your changes to take effect,
Step 1 Use a password to encrypt the HTTPS certificate in a .PEM-encoded file. The PEM-encoded file is called a web
administration certificate file (webadmincert_name.pem).
Step 2 Move the webadmincert_name.pem file to the default directory on your TFTP server.
Step 3 To view the current download settings, enter this command and answer n to the prompt:
transfer download start
Information similar to the following appears:
Mode........................................... TFTP
Data Type...................................... Admin Cert
TFTP Server IP................................. xxx.xxx.xxx.xxx
TFTP Path...................................... <directory path>
TFTP Filename..................................
Are you sure you want to start? (y/n) n
Transfer Canceled
Step 4 Use these commands to change the download settings:
transfer download mode tftp
transfer download datatype webauthcert
transfer download serverip TFTP_server IP_address
transfer download path absolute_TFTP_server_path_to_the_update_file
transfer download filename webadmincert_name.pem
Step 5 To set the password for the .PEM file so that the operating system can decrypt the web administration SSL key and
certificate, enter this command:
transfer download certpassword private_key_password
Step 6 To confirm the current download settings and start the certificate and key download, enter this command and answer y
to the prompt:
transfer download start
Information similar to the following appears:
Mode........................................... TFTP
Data Type...................................... Site Cert
TFTP Server IP................................. xxx.xxx.xxx.xxx
TFTP Path...................................... directory path
TFTP Filename.................................. webadmincert_name
Are you sure you want to start? (y/n) y
TFTP Webadmin cert transfer starting.
Certificate installed.
Please restart the switch (reset system) to use the new certificate.
Step 7 To save the SSL certificate, key, and secure web password to NVRAM so that your changes are retained across reboots,
enter this command:
save config
Step 8 To reboot the controller, enter this command:
reset system
Note See the Cisco Wireless LAN Controller Command Reference for information on specific commands.
Note If you want to input any strings from the XML configuration into CLI commands, you must enclose the
strings in quotation marks.
Before you log on to the CLI, configure your connectivity and environment variables based on the type of
connection you use.
To log on to the controller CLI through the serial port, follow these steps:
Step 1 Connect one end of a null-modem serial cable to the controller’s console port and the other end to your PC’s serial port.
Step 2 Start the PC’s VT-100 terminal emulation program. Configure the terminal emulation program for these parameters:
• 9600 baud
• 8 data bits
• 1 stop bit
• No parity
• No hardware flow control
Note Minimum serial timeout on Controller is 15 seconds instead of 1
minute.
Note The controller serial port is set for a 9600 baud rate and a short timeout. If you would like to change either
of these values, enter config serial baudrate baudrate and config serial timeout timeout to make your
changes. If you enter config serial timeout 0, serial sessions never time out.
Step 3 When prompted, enter a valid username and password to log into the controller. The administrative username and
password that you created in the configuration wizard are case sensitive.
Note The default username is admin, and the default password is
admin.
The CLI displays the root level system prompt:
#(system prompt)>
Note The system prompt can be any alphanumeric string up to 31 characters. You can change it by entering the config
prompt command.
• A VT-100 terminal emulation program or a DOS shell for the Telnet session
Note By default, controllers block Telnet sessions. You must use a local connection to the serial port to enable
Telnet sessions.
Step 1 Verify that your VT-100 terminal emulation program or DOS shell interface is configured with these parameters:
• Ethernet address
• Port 23
Note The CLI automatically logs you out without saving any changes after 5 minutes of inactivity. You can set
the automatic logout from 0 (never log out) to 160 minutes using the config serial timeout command.
When you log into the CLI, you are at the root level. From the root level, you can enter any full command
without first navigating to the correct command level.
The following table lists commands you use to navigate the CLI and to perform common tasks.
Command Action
help At the root level, view system wide navigation
commands
reset system At the root level, reset the controller without logging
out
if the TFTP task has locked the flash and is in the process of downloading and installing a valid configuration
file.
Note The AutoInstall process and manual configuration using both the GUI and CLI of Cisco WLC can occur
in parallel. As part of the AutoInstall cleanup process, the service port IP address is set to 192.168.1.1 and
the service port protocol configuration is modified. Because the AutoInstall process takes precedence over
the manual configuration, whatever manual configuration is performed is overwritten by the AutoInstall
process.
Restrictions on AutoInstall
• In Cisco 5508 WLCs, the following interfaces are used:
◦eth0—Service port (untagged)
◦dtl0—Gigabit port 1 through the NPU (untagged)
Obtaining an IP Address Through DHCP and Downloading a Configuration File from a TFTP
Server
AutoInstall attempts to obtain an IP address from the DHCP server until the DHCP process is successful or
until you abort the AutoInstall process. The first interface to successfully obtain an IP address from the DHCP
server registers with the AutoInstall task. The registration of this interface causes AutoInstall to begin the
process of obtaining TFTP server information and downloading the configuration file.
Following the acquisition of the DHCP IP address for an interface, AutoInstall begins a short sequence of
events to determine the host name of the controller and the IP address of the TFTP server. Each phase of this
sequence gives preference to explicitly configured information over default or implied information and to
explicit host names over explicit IP addresses.
The process is as follows:
• If at least one Domain Name System (DNS) server IP address is learned through DHCP, AutoInstall
creates a /etc/resolv.conf file. This file includes the domain name and the list of DNS servers that have
been received. The Domain Name Server option provides the list of DNS servers, and the Domain Name
option provides the domain name.
• If the domain servers are not on the same subnet as the controller, static route entries are installed for
each domain server. These static routes point to the gateway that is learned through the DHCP Router
option.
• The host name of the controller is determined in this order by one of the following:
◦If the DHCP Host Name option was received, this information (truncated at the first period [.]) is
used as the host name for the controller.
◦A reverse DNS lookup is performed on the controller IP address. If DNS returns a hostname, this
name (truncated at the first period [.]) is used as the hostname for the controller.
• The IP address of the TFTP server is determined in this order by one of the following:
◦If AutoInstall received the DHCP TFTP Server Name option, AutoInstall performs a DNS lookup
on this server name. If the DNS lookup is successful, the returned IP address is used as the IP
address of the TFTP server.
◦If the DHCP Server Host Name (sname) text box is valid, AutoInstall performs a DNS lookup on
this name. If the DNS lookup is successful, the IP address that is returned is used as the IP address
of the TFTP server.
◦If AutoInstall received the DHCP TFTP Server Address option, this address is used as the IP
address of the TFTP server.
◦AutoInstall performs a DNS lookup on the default TFTP server name (cisco-wlc-tftp). If the DNS
lookup is successful, the IP address that is received is used as the IP address of the TFTP server.
◦If the DHCP server IP address (siaddr) text box is nonzero, this address is used as the IP address
of the TFTP server.
◦The limited broadcast address (255.255.255.255) is used as the IP address of the TFTP server.
• If the TFTP server is not on the same subnet as the controller, a static route (/32) is installed for the IP
address of the TFTP server. This static route points to the gateway that is learned through the DHCP
Router option.
AutoInstall runs through this list until it finds a configuration file. It stops running if it does not find a
configuration file after it cycles through this list three times on each registered interface.
Note The downloaded configuration file can be a complete configuration, or it can be a minimal configuration
that provides enough information for the controller to be managed by the Cisco Prime Infrastructure. Full
configuration can then be deployed directly from the Prime Infrastructure.
Note AutoInstall does not expect the switch connected to the controller to be configured for either channels.
AutoInstall works with a service port in LAG configuration.
Note Cisco Prime Infrastructure provides AutoInstall capabilities for controllers. A Cisco Prime Infrastructure
administrator can create a filter that includes the host name, the MAC address, or the serial number of the
controller and associate a group of templates (a configuration group) to this filter rule. The Prime
Infrastructure pushes the initial configuration to the controller when the controller boots up initially. After
the controller is discovered, the Prime Infrastructure pushes the templates that are defined in the
configuration group. For more information about the AutoInstall feature and Cisco Prime Infrastructure,
see the Cisco Prime Infrastructure documentation.
Step 1 Choose Controller > NTP > Servers to open the NTP Servers page.
Step 2 Click New to add an NTP server.
Step 3 Choose a server priority from the Server Index (Priority) drop-down list.
Step 4 Enter the NTP server IPv4/IPv6 address in the Server IP Address (IPv4/IPv6) text box.
Step 5 Enable NTP server authentication by checking the NTP Server Authentication check box.
Step 6 Click Apply.
Step 7 Choose Controller > NTP > Keys.
Step 8 Click New to create a key.
Step 9 Enter the key index in the Key Index text box.
Step 10 Choose the key format from the Key Format drop-down list.
Step 11 Enter the key in the Key text box.
Step 12 Click Apply.
Step 1 Choose Commands > Set Time to open the Set Time page.
The current date and time appear at the top of the page.
Step 2 In the Timezone area, choose your local time zone from the Location drop-down list.
Note When you choose a time zone that uses Daylight Saving Time (DST), the controller automatically sets its system
clock to reflect the time change when DST occurs. In the United States, DST starts on the second Sunday in
March and ends on the first Sunday in November.
Note You cannot set the time zone delta on the controller GUI. However, if you do so on the Cisco WLC CLI, the
change is reflected in the Delta Hours and Mins boxes on the Cisco WLC GUI.
Step 3 Click Set Timezone to apply your changes.
Step 4 In the Date area, choose the current local month and day from the Month and Day drop-down lists, and enter the year
in the Year box.
Step 5 In the Time area, choose the current local hour from the Hour drop-down list, and enter the minutes and seconds in the
Minutes and Seconds boxes.
Note If you change the time zone location after setting the date and time, the values in the Time area are updated to
reflect the time in the new time zone location. For example, if the controller is currently configured for noon
Eastern time and you change the time zone to Pacific time, the time automatically changes to 9:00 a.m.
Step 6 Click Set Date and Time to apply your changes.
Step 7 Click Save Configuration.
Step 1 Configure the current local date and time in GMT on the controller by entering this command:
config time manual mm/dd/yy hh:mm:ss
Note When setting the time, the current local time is entered in terms of GMT and as a value between 00:00 and
24:00. For example, if it is 8:00 a.m. Pacific time in the United States, you would enter 16:00 because the Pacific
time zone is 8 hours behind GMT.
Step 2 Perform one of the following to set the time zone for the controller:
• Set the time zone location in order to have Daylight Saving Time (DST) set automatically when it occurs by entering
this command:
config time timezone location location_index
where location_index is a number representing one of the following time zone locations:
1 (GMT-12:00) International Date Line West
2 (GMT-11:00) Samoa
3 (GMT-10:00) Hawaii
4 (GMT-9:00) Alaska
5 (GMT-8:00) Pacific Time (US and Canada)
6 (GMT-7:00) Mountain Time (US and Canada)
7 (GMT-6:00) Central Time (US and Canada)
8 (GMT-5:00) Eastern Time (US and Canada)
9 (GMT-4:00) Atlantic Time (Canada)
10 (GMT-3:00) Buenos Aires (Argentina)
11 (GMT-2:00) Mid-Atlantic
12 (GMT-1:00) Azores
13 (GMT) London, Lisbon, Dublin, Edinburgh (default value)
14 (GMT +1:00) Amsterdam, Berlin, Rome, Vienna
15 (GMT +2:00) Jerusalem
16 (GMT +3:00) Baghdad
17 (GMT +4:00) Muscat, Abu Dhabi
18 (GMT +4:30) Kabul
19 (GMT +5:00) Karachi, Islamabad, Tashkent
20 (GMT +5:30) Colombo, Kolkata, Mumbai, New Delhi
21 (GMT +5:45) Katmandu
22 (GMT +6:00) Almaty, Novosibirsk
Note If you enter this command, the controller automatically sets its system clock to reflect DST when it occurs.
In the United States, DST starts on the second Sunday in March and ends on the first Sunday in November.
• Manually set the time zone so that DST is not set automatically by entering this command:
config time timezone delta_hours delta_mins
where delta_hours is the local hour difference from GMT, and delta_mins is the local minute difference from GMT.
When manually setting the time zone, enter the time difference of the local current time zone with respect to GMT
(+/–). For example, Pacific time in the United States is 8 hours behind GMT. Therefore, it is entered as –8.
Note You can manually set the time zone and prevent DST from being set only on the controller
CLI.
Step 4 Verify that the controller shows the current local time with respect to the local time zone by entering this command:
show time
Information similar to the following appears:
NTP Servers
NTP Polling Interval......................... 3600
Index NTP Key Index NTP Server NTP Msg Auth Status
------- ---------------------------------------------------------------
1 1 209.165.200.225 AUTH SUCCESS
Note If you configured the time zone location, the Timezone Delta value is set to “0:0.” If you manually configured
the time zone using the time zone delta, the Timezone Location is blank.
Step 1 Choose Management > Telnet-SSH to open the Telnet-SSH Configuration page.
Step 2 In the Telnet Login Timeout text box, enter the number of minutes that a Telnet session is allowed to remain inactive
before being terminated. The valid range is 0 to 160 minutes (inclusive), and the default value is 5 minutes. A value of
0 indicates no timeout.
Step 3 From the Maximum Number of Sessions drop-down list, choose the number of simultaneous Telnet or SSH sessions
allowed. The valid range is 0 to 5 sessions (inclusive), and the default value is 5 sessions. A value of zero indicates that
Telnet/SSH sessions are disallowed.
Step 4 To forcefully close current login sessions, choose Management > User Sessions > close from the CLI session drop-down
list.
Step 5 From the Allow New Telnet Sessions drop-down list, choose Yes or No to allow or disallow new Telnet sessions on
the controller. The default value is No.
Step 6 From the \ drop-down list, choose Yes or No to allow or disallow new SSH sessions on the controller. The default value
is Yes.
Step 7 Click Apply.
Step 8 Click Save Configuration.
Step 9 To see a summary of the Telnet configuration settings, choose Management > Summary. The Summary page appears.
This page shows whether additional Telnet and SSH sessions are permitted.
Note If you are unable to create a new telnet session, close the existing sessions by following the
steps:
Step 1 Allow or disallow new Telnet sessions on the controller by entering this command:
config network telnet {enable | disable}
Step 2 Allow or disallow new SSH sessions on the controller by entering this command:
config network ssh {enable | disable}
The default value is enabled.
Note Use the config network ssh cipher-option high {enable | disable} command to enable sha2 which is supported
in WLC.
Step 3 Specify the number of minutes that a Telnet session is allowed to remain inactive before being terminated by entering
this command:
config sessions timeout timeout
where timeout is a value between 0 and 160 minutes (inclusive). The default value is 5 minutes. A value of 0 indicates
no timeout.
Step 4 Specify the number of simultaneous Telnet or SSH sessions allowed by entering this command:
config sessions maxsessions session_num
where session_num is a value between 0 and 5 (inclusive). The default value is 5 sessions. A value of zero indicates that
Telnet/SSH sessions are disallowed.
Step 6 See the Telnet and SSH configuration settings by entering this command:
show network summary
Information similar to the following appears:
Step 7 See the Telnet session configuration settings by entering this command:
show sessions
Information similar to the following appears:
Step 9 You can close all the Telnet or SSH sessions by entering this command:
config loginsession close {session-id | all}
The session-id can be taken from the show login-session command.
Note For instructions on configuring Telnet or SSH SSH sessions on the controller, see the
Telnet and Secure Shell Sessions section.
Step 1 Choose Wireless > Access Points > All APs to open the All APs page.
Step 2 Click the name of the access point for which you want to enable Telnet or SSH.
Step 3 Choose the Advanced tab to open the All APs > Details for (Advanced) page.
Step 4 Select the Telnet check box to enable Telnet connectivity on this access point. The default value is unchecked.
Step 5 Select the SSH check box to enable SSH connectivity on this access point. The default value is unchecked.
Step 6 Click Apply.
Step 7 Click Save Configuration.
Step 1 Enable Telnet or SSH connectivity on an access point by entering this command:
config ap {telnet | ssh} enable Cisco_AP
The default value is disabled.
Note Disable Telnet or SSH connectivity on an access point by entering this command: config ap {telnet | ssh}
disable Cisco_AP
Step 2 Save your changes by entering this command:
save config
Step 3 See whether Telnet or SSH is enabled on an access point by entering this command:
show ap config general Cisco_AP
Information similar to the following appears:
Cisco AP Identifier.............................. 5
Cisco AP Name.................................... AP33
Country code..................................... Multiple Countries:US,AE,AR,AT,AU,BH
Reg. Domain allowed by Country................... 802.11bg:-ABCENR 802.11a:-ABCEN
AP Country code.................................. US - United States
AP Regulatory Domain............................. 802.11bg:-A 802.11a:-A
Switch Port Number .............................. 2
MAC Address...................................... 00:19:2f:11:16:7a
IP Address Configuration......................... Static IP assigned
IP Address....................................... 10.22.8.133
IP NetMask....................................... 255.255.248.0
• Support for OfficeExtend access points, which are used for secure mobile teleworking.
All features included in a Wireless LAN Controller WPLUS license are now included in the base license.
There are no changes to Cisco Prime Infrastructure BASE and PLUS licensing. These WPlus license features
are included in the base license:
• OfficeExtend AP
• Enterprise Mesh
• CAPWAP Data Encryption
For information about upgrade and capacity adder licenses, see the product data sheet of your controller model.
• In the controller software 7.0.116.0 and later releases, the AP association trap is ciscoLwappApAssociated.
In prior releases, the trap was bsnAPAssociated.
• The ap-count licenses and their corresponding image-based licenses are installed together. The controller
keeps track of the licensed access point count and does not allow more than the number of access points
to associate to it.
• The Cisco 5500 Series Controller is shipped with both permanent and evaluation base and base-ap-count
licenses. If desired, you can activate the evaluation licenses, which are designed for temporary use and
set to expire after 60 days.
• No licensing steps are required after you receive your Cisco 5500 Series Controller because the licenses
you ordered are installed at the factory. In addition, licenses and product authorization keys (PAKs) are
preregistered to serial numbers. However, as your wireless network evolves, you might want to add
support for additional access points or upgrade from the standard software set to the base software set.
To do so, you must obtain and install an upgrade license.
For example, if your controller was initially ordered with support for 100 access points (base license
AIR-CT5508-100-K9), you could increase the capacity to 500 access points by purchasing a 250 access point,
100 access point, and a 50 access point additive capacity license (LIC-CT5508-250A, LIC-CT5508-100A,
and LIC-CT5508-50A).
You can find more information on ordering capacity adder licenses at this URL:
http://www.cisco.com/c/en/us/products/wireless/5500-series-wireless-controllers/datasheet-listing.html
Note If you skip any tiers when upgrading (for example, if you do not install the -25U and -50U licenses along
with the -100U), the license registration for the upgraded capacity fails.
For a single controller, you can order different upgrade licenses in one transaction (for example, -25U, -50U,
-100U, and -250U), for which you receive one PAK with one license. Then you have only one license (instead
of four) to install on your controller.
If you have multiple controllers and want to upgrade all of them, you can order multiple quantities of each
upgrade license in one transaction (for example, you can order 10 each of the -25U, -50U, -100U, and -250
upgrade licenses), for which you receive one PAK with one license. You can continue to register the PAK
for multiple controllers until it is exhausted.
For more information about the base license SKUs and capacity adder licenses, see the respective controller’s
data sheet.
Step 1 Order the PAK certificate for an upgrade license through your Cisco channel partner or your Cisco sales representative,
or order it online at this URL:
http://www.cisco.com/go/ordering
Step 2 If you are ordering online, begin by choosing the primary upgrade SKU L-LIC-CT5508-UPG or LIC CT5508-UPG.
Then, choose any number of the following options to upgrade one or more controllers under one PAK. After you receive
the certificate, use one of the following methods to register the PAK:
• Licensing portal—This alternative method enables you to manually obtain and install licenses on your controller.
If you want to use the licensing portal to register the PAK, follow the instructions in Step 3.
e) On the Designate Licensee page, enter the product ID and serial number of the controller on which you plan to install
the license, read and accept the conditions of the end-user license agreement (EULA), complete the rest of the text
boxes on this page, and click Submit.
f) On the Finish and Submit page, verify that all information is correct and click Submit.
g) When a message appears indicating that the registration is complete, click Download License. The license is e-mailed
within 1 hour to the address that you specified.
h) When the e-mail arrives, follow the instructions provided.
i) Copy the license file to your TFTP server.
Installing a License
Step 1 Choose Management > Software Activation > Commands to open the License Commands page.
Step 2 From the Action drop-down list, choose Install License. The Install License from a File section appears.
Step 3 In the File Name to Install text box, enter the path to the license (*.lic) on the TFTP server.
Step 4 Click Install License. A message appears to show whether the license was installed successfully. If the installation fails,
the message provides the reason for the failure, such as the license is an existing license, the path was not found, the
license does not belong to this device, you do not have correct permissions for the license, and so on.
Step 5 If the end-user license agreement (EULA) acceptance dialog box appears, read the agreement and click Accept to accept
the terms of the agreement.
Note Typically, you are prompted to accept the EULA for evaluation, extension, and rehost licenses. The EULA is
also required for permanent licenses, but it is accepted during license generation.
Step 6 Save a backup copy of all installed licenses as follows:
a) From the Action drop-down list, choose Save License.
b) In the File Name to Save text box, enter the path on the TFTP server where you want the licenses to be saved.
Note You cannot save evaluation
licenses.
c) Click Save Licenses.
Step 7 Reboot the controller.
Note We recommend that you reset the system to ensure that the newly installed license file is saved in the
WLC.
Step 4 Save a backup copy of all installed licenses by entering this command:
license save url
where url is tftp://server_ip/path/filename.
Viewing Licenses
Step 1 Choose Management > Software Activation > Licenses to open the Licenses page.
This page lists all of the licenses installed on the controller. For each license, it shows the license type, expiration, count
(the maximum number of access points allowed for this license), priority (low, medium, or high), and status (in use, not
in use, inactive, or EULA not accepted).
Note Controller platforms do not support the status of “grace period” or “extension” as a license type. The license
status will always show “evaluation” even if a grace period or an extension evaluation license is installed.
Note If you ever want to remove a license from the controller, hover your cursor over the blue drop-down arrow for
the license and click Remove. For example, you might want to delete an expired evaluation license or any
unused license. You cannot delete unexpired evaluation licenses, the permanent base image license, or licenses
that are in use by the controller.
Step 2 Click the link for the desired license to view more details for a particular license. The License Detail page appears.
This page shows the following additional information for the license:
Step 3 If you want to enter a comment for this license, type it in the Comment text box and click Apply.
Step 4 Click Save Configuration to save your changes.
OUI File Last Update Time........................ Sun Sep 07 10:44:07 IST 2014
--More-- or (q)uit
System Timezone Location.........................
System Stats Realtime Interval................... 5
System Stats Normal Interval..................... 180
--More-- or (q)uit
Power Supply 2................................... Present, OK
Maximum number of APs supported.................. 6000
System Nas-Id....................................
WLC MIC Certificate Types........................ SHA1/SHA2
Licensing Type................................... RTU
Note The Operating Environment and Internal Temp Alarm Limits data are not displayed for
Cisco Flex 7500 Series Controllers.
• See a brief summary of all active licenses installed on the controller by entering this command:
show license summary
Information similar to the following appears:
• See all of the licenses installed on the controller by entering this command:
show license all
Information similar to the following appears:
• See all expiring, evaluation, permanent, or in-use licenses by entering this command:
show license {expiring | evaluation | permanent | in-use}
Information similar to the following appears for the show license in-use command:
Note Controller platforms do not support the status of “grace period” or “extension” as a license
type. The license status will always show “evaluation” even if a grace period or an
extension evaluation license is installed.
• See the maximum number of access points allowed for this license on the controller, the number of
access points currently joined to the controller, and the number of access points that can still join the
controller by entering this command:
show license capacity
Information similar to the following appears:
• See statistics for all licenses on the controller by entering this command:
show license statistics
• See a summary of license-enabled features by entering this command:
show license feature
Note To prevent disruptions in operation, the controller does not switch licenses when an evaluation license
expires. You must reboot the controller in order to return to a permanent license. Following a reboot, the
controller defaults to the same feature set level as the expired evaluation license. If no permanent license
at the same feature set level is installed, the controller uses a permanent license at another level or an
unexpired evaluation license.
Step 1 Choose Management > Software Activation > Licenses to open the Licenses page.
The Status column shows which licenses are currently in use, and the Priority column shows the current priority of each
license.
d) When the EULA appears, read the terms of the agreement and then click Accept.
e) When prompted to reboot the controller, click OK.
f) Reboot the controller in order for the priority change to take effect.
g) Click Licenses to open the Licenses page and verify that the ap-count evaluation license now has a low priority and
is not in use. Instead, the ap-count permanent license should be in use.
Step 1 See the current status of all the licenses on your controller by entering this command:
show license all
Information similar to the following appears:
The License State text box shows the licenses that are in use, and the License Priority text box shows the current priority
of each license.
Note In the 7.2.110.0 release, the command output displays the full in-use count for active base-ap-count license even
though there are no APs connected.
Step 2 Activate an ap-count evaluation license as follows:
a) Raise the priority of the base-ap-count evaluation license by entering this command:
license modify priority license_name high
Note You can set the priority only for ap-count evaluation licenses. AP-count permanent licenses always have a
medium priority, which cannot be configured.
b) Reboot the controller in order for the priority change to take effect by entering this command:
reset system
c) Verify that the ap-count evaluation license now has a high priority and is in use by entering this command:
show license all
You can use the evaluation license until it expires.
Step 3 If you decide to stop using the ap-count evaluation license and want to revert to using an ap-count permanent license,
follow these steps:
a) Lower the priority of the ap-count evaluation license by entering this command:
license modify priority license_name low
b) Reboot the controller in order for the priority change to take effect by entering this command:
reset system
c) Verify that the ap-count evaluation license now has a low priority and is not in use by entering this command:
show license all
Instead, the ap-count permanent license should be in use.
In the RTU licensing model, the following types of licenses are available:
• Permanent or base licenses—These licenses are programmed into the controller hardware at the time of
manufacturing. These licenses are base count licenses that cannot be deleted or transferred.
• Adder licenses—These licenses are wireless access point count licenses that you can activate by accepting
the RTU EULA. The EULA states that you are obliged to purchase the specified access point count
licenses at the time of activation. You must activate these licenses for the purchased access points count
and accept the EULA.
You can remove an adder license from one controller and transfer the license to another controller in
the same product family. For example, an adder license such as LIC-CT7500-100A can be transferred
(partially or fully) from one Cisco Flex 7500 Series Controller to another Cisco Flex 7500 Series
Controller.
Note Licenses embedded in the controller at the time of shipment is not transferrable.
• Evaluation licenses—These licenses are demo or trial mode licenses that are valid for 90 days. Fifteen
days prior to the expiry of the 90-day period, you are notified about the requirement to buy the permanent
license. These evaluation licenses are installed with the license image. You can activate the evaluation
licenses anytime with a command. A EULA is prompted after you run the activation command on the
controller CLI. The EULA states that you are obligated to pay for the specified license count within 90
days of usage. The countdown starts after you accept the EULA.
Whenever you add or delete an access point adder license on the controller, you are prompted with an RTU
EULA. You can either accept or decline the RTU EULA for each add or delete operation.
For high-availability (HA) controllers when you enable HA, the controllers synchronize with the enabled
license count of the primary controller and support high availability for up to the license count enabled on the
primary controller.
You can view the RTU licenses through the controller GUI or CLI. You can also view these licenses across
multiple wireless controllers through Cisco Prime Infrastructure.
With Release 8.1, the license management for Cisco Virtual Wireless Controller is changed from license-file
based management to Right-to-Use-based management. The previous licenses are still valid, and when you
upgrade to Release 8.1 from an earlier release, you are required to only accept an end-user license agreement
again to the quantity installed before.
Step 1 Choose Management > Software Activation > Licenses to open the Licenses page.
Step 2 In the Adder License area, choose to add or delete the number of APs that an AP license can support, enter a value, and
click Set Count.
Step 3 Click Save Configuration.
Note When you activate the license, you are prompted to accept or reject the End User License
Agreement (EULA) for the given license. If you activate a license that supports fewer
number of APs than the current number of APs connected to the controller, the activation
command fails.
Note After you add or delete the license, WLC must use the save config command to save the license.
Rehosting Licenses
This section describes how to rehost licenses.
Note Starting in the release 7.3, the Right-to-Use licensing is supported on the Cisco Flex 7500 Series Controllers,
thereby the rehosting behavior changes on these controllers. If you require to rehost licenses, you need to
plan rehosting the installed adder licenses prior to an upgrade.
Rehosting a License
Step 1 Choose Management > Software Activation > Commands to open the License Commands page.
Step 2 From the Action drop-down list, choose Rehost. The Revoke a License from the Device and Generate Rehost Ticket
area appears.
Step 3 In the File Name to Save Credentials text box, enter the path on the TFTP server where you want the device credentials
to be saved and click Save Credentials.
Step 4 To obtain a permission ticket to revoke the license, follow these steps:
a) Click Cisco Licensing (https://tools.cisco.com/SWIFT/Licensing/PrivateRegistrationServlet).
b) On the Product License Registration page, click Look Up a License under Manage Licenses.
c) Enter the product ID and serial number for your controller.
Note To find the controller’s product ID and serial number, choose Controller > Inventory on the controller
GUI.
d) Open the device credential information file that you saved in Step 3 and copy and paste the contents of the file into
the Device Credentials text box.
e) Enter the security code in the blank box and click Continue.
f) Choose the licenses that you want to revoke from this controller and click Start License Transfer.
g) On the Rehost Quantities page, enter the number of licenses that you want to revoke in the To Rehost text box and
click Continue.
h) On the Designate Licensee page, enter the product ID and serial number of the controller for which you plan to revoke
the license, read and accept the conditions of the End User License Agreement (EULA), complete the rest of the text
boxes on this page, and click Continue.
i) On the Review and Submit page, verify that all information is correct and click Submit.
j) When a message appears indicating that the registration is complete, click Download Permission Ticket. The rehost
permission ticket is e-mailed within 1 hour to the address that you specified.
k) After the e-mail arrives, copy the rehost permission ticket to your TFTP server.
Step 5 Use the rehost permission ticket to revoke the license from this controller and generate a rehost ticket as follows:
a) In the Enter Saved Permission Ticket File Name text box, enter the TFTP path and filename (*.lic) for the rehost
permission ticket that you generated in Step 4.
b) In the Rehost Ticket File Name text box, enter the TFTP path and filename (*.lic) for the ticket that will be used to
rehost this license on another controller.
c) Click Generate Rehost Ticket.
d) When the End User License Agreement (EULA) acceptance dialog box appears, read the agreement and click Accept
to accept the terms of the agreement.
Step 6 Use the rehost ticket generated in Step 5 to obtain a license installation file, which can then be installed on another
controller as follows:
a) Click Cisco Licensing.
b) On the Product License Registration page, click Upload Rehost Ticket under Manage Licenses.
c) On the Upload Ticket page, enter the rehost ticket that you generated in Step 5 in the Enter Rehost Ticket text box
and click Continue.
d) On the Validate Features page, verify that the license information for your controller is correct, enter the rehost
quantity, and click Continue.
e) On the Designate Licensee page, enter the product ID and serial number of the controller on which you plan to use
the license, read and accept the conditions of the End User License Agreement (EULA), complete the rest of the text
boxes on this page, and click Continue.
f) On the Review and Submit page, verify that all information is correct and click Submit.
g) When a message appears indicating that the registration is complete, click Download License. The rehost license
key is e-mailed within 1 hour to the address that you specified.
h) After the e-mail arrives, copy the rehost license key to your TFTP server.
i) Follow the instructions in the Installing a License section to install this on another controller.
Step 7 After revoking the license on original controller, correspondent evaluation licence appear with High pritority. Lower the
priority of the evaluation license so that the parmanent license is in "In Use" status.
h) On the Designate Licensee page, enter the product ID and serial number of the controller for which you plan to revoke
the license, read and accept the conditions of the End-User License Agreement (EULA), complete the rest of the text
boxes on this page, and click Continue.
i) On the Review and Submit page, verify that all information is correct and click Submit.
j) When a message appears indicating that the registration is complete, click Download Permission Ticket. The rehost
permission ticket is e-mailed within 1 hour to the address that you specified.
k) After the e-mail arrives, copy the rehost permission ticket to your TFTP server.
Step 3 Use the rehost permission ticket to revoke the license from this controller and generate a rehost ticket as follows:
a) Revoke the license from the controller by entering this command:
license revoke permission_ticket_url
where permission_ticket_url is tftp://server_ip/path/filename.
b) Generate the rehost ticket by entering this command:
license revoke rehost rehost_ticket_url
where rehost_ticket_url is tftp://server_ip/path/filename.
c) If prompted, read and accept the terms of the End-User License Agreement (EULA).
Step 4 Use the rehost ticket generated in Step 3 to obtain a license installation file, which can then be installed on another
controller as follows:
a) Go to https://tools.cisco.com/SWIFT/Licensing/PrivateRegistrationServlet.
b) On the Product License Registration page, click Upload Rehost Ticket under Manage Licenses.
c) On the Upload Ticket page, enter the rehost ticket that you generated in Step 3 in the Enter Rehost Ticket text box
and click Continue.
d) On the Validate Features page, verify that the license information for your controller is correct, enter the rehost
quantity, and click Continue.
e) On the Designate Licensee page, enter the product ID and serial number of the controller on which you plan to use
the license, read and accept the conditions of the End-User License Agreement (EULA), complete the rest of the text
boxes on this page, and click Continue.
f) On the Review and Submit page, verify that all information is correct and click Submit.
g) When a message appears indicating that the registration is complete, click Download License. The rehost license
key is e-mailed within 1 hour to the address that you specified.
h) After the e-mail arrives, copy the rehost license key to your TFTP server.
i) Follow the instructions in the Installing a License (GUI), on page 54 section to install this license on another
controller.
Step 5 After revoking the license on original controller, correspondent evaluation licence appear with High pritority. Lower the
priority of the evaluation license so that the parmanent license is in "In Use" status.
Replacement controllers come preinstalled with the following licenses: permanent base and evaluation base,
base-ap-count. No other permanent licenses are installed. The SKU for replacement controllers is
AIR-CT5508-CA-K9.
Because licenses are registered to the serial number of a controller, you can use the licensing portal on
Cisco.com to request that the license from your returned controller be revoked and authorized for use on the
replacement controller. After your request is approved, you can install the old license on the replacement
controller. Any additional ap-count licenses if installed in the returned controller has to be rehosted on the
replacement controller. Before you begin, you need the product ID and serial number of both the returned
controller and the replacement controller. This information is included in your purchase records.
Note The evaluation licenses on the replacement controller are designed for temporary use and expire after 60
days. To prevent disruptions in operation, the controller does not switch licenses when an evaluation
license expires. You must reboot the controller in order to return to a permanent license. If the evaluation
licenses expire before you transfer the permanent licenses from your defective controller to your replacement
controller, the replacement controller remains up and running using the permanent base license, but access
points are no longer able to join the controller.
Step 1 Choose Wireless > 802.11a/n/ac or 802.11b/g/n > Network to open the Global Parameters page.
Step 2 Select the 802.11a (or 802.11b/g) Network Status check box to enable the 802.11a or 802.11b/g band. To disable the
band, unselect the check box. The default value is enabled. You can enable both the 802.11a and 802.11b/g bands.
Step 3 If you enabled the 802.11b/g band in Step 2, select the 802.11g Support check box if you want to enable 802.11g network
support. The default value is enabled. If you disable this feature, the 802.11b band is enabled without 802.11g support.
Step 4 Specify the period at which the SSID is broadcast by the access point by entering a value between 20 and 1000 milliseconds
(inclusive) in the Beacon Period text box. The default value is 100 milliseconds.
Note The beacon period in controllers is listed in terms of milliseconds. The beacon period can also be measured in
time units, where one time unit equals 1024 microseconds or 102.4 milliseconds. If a beacon interval is listed
as 100 milliseconds in a controller, it is only a rounded off value for 102.4 milliseconds. Due to hardware
limitation in certain radios, even though the beacon interval is, say 100 time units, it is adjusted to 102 time
units, which roughly equals 104.448 milliseconds. When the beacon period is to be represented in terms of time
units, the value is adjusted to the nearest multiple of 17.
Step 5 Specify the size at which packets are fragmented by entering a value between 256 and 2346 bytes (inclusive) in the
Fragmentation Threshold text box. Enter a low number for areas where communication is poor or where there is a great
deal of radio interference.
Step 6 Make access points advertise their channel and transmit power level in beacons and probe responses for CCX clients.
Select the DTPC Support check box. Otherwise, unselect this check box. The default value is enabled.
Client devices using dynamic transmit power control (DTPC) receive the channel and power level information from the
access points and adjust their settings automatically. For example, a client device used primarily in Japan could rely on
DTPC to adjust its channel and power settings automatically when it travels to Italy and joins a network there.
Note On access points that run Cisco IOS software, this feature is called world
mode.
Note DTPC and 801.11h power constraint cannot be enabled simultaneously.
Step 7 Specify the maximum allowed clients by entering a value between 1 to 200 in the Maximum Allowed Client text box.
The default value is 200.
Step 8 Select or unselect the RSSI Low Check check box to enable or disable the RSSI Low Check feature.
Service providers can use the RSSI Low Check feature to prevent clients from connecting to their Wi-Fi network unless
the client has a viable connection. In many scenarios, even though clients can hear beacons and connect to Wi-Fi, the
signal might not be strong enough to support a stable connection. Use this feature to determine how strong a client must
be heard for it to associate with the Wi-Fi network.
If you enable the RSSI Low Check feature, when a client sends an association request to the AP, the controller gets the
RSSI value from the association message and compares it with the RSSI threshold that is configured. If the RSSI value
from the association message is less than the RSSI threshold value, the controller rejects the association request. Note
that this is only for association frames, and not for other messages.
The default RSSI Low Check value is –80 dBm, which means an association request from a client can be rejected if the
AP hears a client with a signal that is weaker than –80 dBm. If you lower the value to –90 dBm, clients are allowed to
connect at a further distance, but there is also a higher probability of the connection quality being poor. We recommend
that you do not go higher than –80 dBm, for example –70 dBm, because this makes the cell size significantly smaller.
Step 10 Use the Data Rates options to specify the rates at which data can be transmitted between the access point and the client.
These data rates are available:
• 802.11a—6, 9, 12, 18, 24, 36, 48, and 54 Mbps
• 802.11b/g—1, 2, 5.5, 6, 9, 11, 12, 18, 24, 36, 48, or 54 Mbps
Step 3 Specify the rate at which the SSID is broadcast by the access point by entering this command:
config {802.11a | 802.11b} beaconperiod time_unit
where time_unit is the beacon interval in time units (TUs). One TU is 1024 microseconds. You can configure the access
point to send a beacon every 20 to 1000 milliseconds.
Step 4 Specify the size at which packets are fragmented by entering this command:
config {802.11a | 802.11b} fragmentation threshold
where threshold is a value between 256 and 2346 bytes (inclusive). Specify a low number for areas where communication
is poor or where there is a great deal of radio interference.
Step 5 Make access points advertise their channel and transmit power level in beacons and probe responses by entering this
command:
config {802.11a | 802.11b } dtpc {enable | disable}
The default value is enabled. Client devices using dynamic transmit power control (DTPC) receive the channel and
power level information from the access points and adjust their settings automatically. For example, a client device used
primarily in Japan could rely on DTPC to adjust its channel and power settings automatically when it travels to Italy and
joins a network there.
Note On access points that run Cisco IOS software, this feature is called world
mode.
Step 6 Specify the maximum allowed clients that can be configured by entering this command:
config {802.11a | 802.11b} max-clients max_allow_clients
The valid range is between 1 to 200.
Step 7 Configure the RSSI Low Check feature by entering this command:
config 802.11{a | b} rssi-check {enable | disable}
Step 8 Configure the RSSI Threshold value by entering this command:
config 802.11{a | b} rssi-threshold value-in-dBm
Note The default value is –80
dBm.
Step 9 Specify the rates at which data can be transmitted between the controller and the client by entering this command:
config {802.11a | 802.11b} rate {disabled | mandatory | supported} rate
where
• disabled—Clients specify the data rates used for communication.
• mandatory—Clients support this data rate in order to associate to an access point on the controller.
• supported—Any associated clients that support this data rate may communicate with the access point using that
rate. However, the clients are not required to be able to use this rate in order to associate.
Note The WMM default configuration will not be shown in show running-config output.
• Scenario - 2: Client RSSI (as seen from show cont d0/d1 | begin RSSI) lies between Mid-RSSI and
Acceptable Client RSSI.
• All 2.4-GHz and 5-GHz probe requests are responded without any restrictions.
• This scenario is similar to the band select disabled.
Note The client RSSI value (seen as sh cont d0 | begin RSSI) is the average of the client packets received, and
the Mid-RSSI feature is the instantaneous RSSI value of the probe packets. As a result, the client RSSI is
seen as weaker than the configured Mid-RSSI value (7 dB delta). The 802.11b probes from the client are
suppressed to push the client to associate with the 802.11a band.
Step 1 Choose Wireless > Advanced > Band Select to open the Band Select page.
Step 2 In the Probe Cycle Count text box, enter a value between 1 and 10. This cycle count sets the number of 2.4 GHz probe
suppression cycles. The cycle count sets the number of suppression cycles for a new client. The default cycle count is
2.
Step 3 In the Scan Cycle Period Threshold (milliseconds) text box, enter a value between 1 and 1000 milliseconds for the
scan cycle period threshold. This setting determines the time threshold during which new probe requests from a client
come from a new scanning cycle (i.e. only if the time difference between the successive probe requests is greater than
this configured value, then the count value in the band select table increases). The default cycle threshold is 200
milliseconds.
Step 4 In the Age Out Suppression (seconds) text box, enter a value between 10 and 200 seconds. Age-out suppression sets
the expiration time for pruning previously known 802.11b/g/n clients. The default value is 20 seconds. After this time
elapses, clients become new and are subject to probe response suppression.
Step 5 In the Age Out Dual Band (seconds) text box, enter a value between 10 and 300 seconds. The age-out period sets the
expiration time for pruning previously known dual-band clients. The default value is 60 seconds. After this time elapses,
clients become new and are subject to probe response suppression.
Step 6 In the Acceptable Client RSSI (dBm) text box, enter a value between –20 and –90 dBm. This parameter sets the
minimum RSSI for a client to respond to a probe. The default value is –80 dBm.
Step 7 In the Acceptable Client Mid RSSI (dBm) text box, enter a value between –20 and –90 dBm. This parameter sets the
mid-RSSI, whose value can be used for toggling 2.4 GHz probe suppression based on the RSSI value. The default value
is –60 dBm.
Step 8 Click Apply.
Step 9 Click Save Configuration.
Step 10 To enable or disable band selection on specific WLANs, choose WLANs > WLAN ID. The WLANs > Edit page
appears.
Step 11 Click the Advanced tab.
Step 12 In the Load Balancing and Band Select text area, if you want to enable band selection, select the Client Band Select
check box. If you want to disable band selection, leave the check box unselected. The default value is disabled.
Step 13 Click Save Configuration.
Step 1 Set the probe cycle count for band select by entering this command:
config band-select cycle-count cycle_count
You can enter a value between 1 and 10 for the cycle_count parameter.
Step 2 Set the time threshold for a new scanning cycle period by entering this command:
config band-select cycle-threshold milliseconds
You can enter a value for threshold between 1 and 1000 for the milliseconds parameter.
Step 3 Set the suppression expire to the band select by entering this command:
config band-select expire suppression seconds
You can enter a value for suppression between 10 to 200 for the seconds parameter.
You can enter a value for minimum dBm of a client RSSI to respond to a probe between -20 and -90 for the client_rssi
parameter.
Step 6 Set the client mid RSSI threshold by entering this command:
config band-select client-mid-rssi client_mid_rssi
You can enter a value for mid RSSI between -20 and -90 for the client_mid_rssi parameter.
Note Some Cisco 802.11n APs may intermittently emit incorrect beacon frames, which can trigger false wIPS
alarms. We recommend that you ignore these alarms. The issue is observed in the following Cisco 802.11n
APs: 1140, 1250, 2600, 3500, and 3600.
Step 1 Choose Wireless > 802.11a/n/ac or 802.11b/g/n > High Throughput to open the (5 GHz or 2.4 GHz) High Throughput
page.
Step 2 Select the 11n Mode check box to enable 802.11n support on the network. The default value is enabled.
If you want to disable 802.11n mode when both 802.11n and 802.11ac modes are enabled, you must disable the 802.11ac
mode first.
Step 3 Select the check boxes of the desired rates to specify the modulation and coding scheme (MCS) rates at which data can
be transmitted between the access point and the client. These data rates, which are calculated for a 20-MHz channel
width using a short guard interval, are available:
• 0 (7 Mbps)
• 1 (14 Mbps)
• 2 (21 Mbps)
• 3 (29 Mbps)
• 4 (43 Mbps)
• 5 (58 Mbps)
• 6 (65 Mbps)
• 7 (72 Mbps)
• 8 (14 Mbps)
• 9 (29 Mbps)
• 10 (43 Mbps)
• 11 (58 Mbps)
• 12 (87 Mbps)
• 13 (116 Mbps)
• 14 (130 Mbps)
• 15 (144 Mbps)
Any associated clients that support the selected rates may communicate with the access point using those rates.
However, the clients are not required to be able to use this rate in order to associate. The MCS settings determine
the number of spatial streams, the modulation, the coding rate, and the data rate values that are used.
If you choose Allowed, devices that cannot support WMM can join the WLAN but will not benefit from the 802.11n
rates.
e) Click Apply.
Step 6 Click Save Configuration.
Note To determine if an access point supports 802.11n, look at the 11n Supported text box on either the 802.11a/n/ac
(or 802.11b/g/n) Cisco APs > Configure page or the 802.11a/n/ac (or 802.11b/g/n) AP Interfaces > Details page.
Note For 802.11ac, all packets are A-MPDU. The A-MSDU option does not apply for 802.11ac.
You can specify the aggregation method for various types of traffic from the access point to the
clients. This table defines the priority levels (0-7) assigned per traffic type.
2 Spare
3 Excellent effort
4 Controlled load
7 Network control
You can configure each priority level independently, or you can use the all parameter to configure
all of the priority levels at once. When you use the enable command, the traffic associated with that
priority level uses A-MPDU transmission. When you use the disable command, the traffic associated
with that priority level uses A-MSDU transmission. Configure the priority levels to match the
aggregation method used by the clients. By default, A-MPDU is enabled for priority level 0, 4 and
5 and the rest are disabled. By default, A-MSDU is enabled for all priorities except 6 and 7.
c) Reenable the network by entering this command:
config {802.11a | 802.11b} enable network
• Configure the 802.11n-5 GHz A-MPDU transmit aggregation scheduler by entering this command:
config 802.11{a | b} 11nsupport a-mpdu tx scheduler {enable | disable | timeout rt timeout-value}
The timeout value is in milliseconds. The valid range is between 1 millisecond to 1000 milliseconds.
• Configure the guard interval for the network by entering this command:
config 802.11{a | b} 11nsupport guard_interval {any | long}
• Configure the Reduced Interframe Space (RIFS) for the network by entering this command:
config 802.11{a | b} 11nsupport rifs rx {enable | disable}
• Save your changes by entering this command:
save config
• View the configuration settings for the 802.11 networks by entering this command:
show {802.11a | 802.11b}
Step 2 Enable or disable an access point to announce when it is switching to a new channel, and the new channel number by
entering this command:
config 802.11h channelswitch {enable | disable} switch_mode
Enter either 0 or 1 for the switch_mode parameter to specify whether transmissions are restricted until the actual channel
switch (0), or are not restricted (1). By default, this feature is in disabled state.
Step 3 Configure a new channel using the 802.11h channel announcement by entering this command:
config 802.11h setchannel channel channel
Step 4 Configure the 802.11h power constraint value by entering this command:
config 802.11h powerconstraint value
Use increments of 3 dB for the value so that the AP goes down one power level at a time.
Step 6 View the status of the 802.11h parameters by entering this command:
show 802.11h
Information similar to the following appears:
Power Constraint................................. 0
Channel Switch................................... Disabled
Channel Switch Mode.............................. 0
Note The 11ac Supported field is a nonconfigurable parameter that appears for the 802.11ac
slave radio in slot 2.
Note When the Cisco Aironet 3600 Series access point with 802.11ac radio module is in unsupported mode
such as Monitor and Sniffer, Admin Status and Channel Width will not be configured.
This section provides instructions to manage 802.11ac devices such as the Cisco Aironet 3600 Series Access
Points and Cisco Aironet 3700 Series Access Point on your network.
Note AP3600 and AP3700 with the 802.11ac module can advertise only the first 8 WLANs on the 5-GHz
radios.
Changing the 802.11n radio channel also changes the 802.11ac channels.
On the Cisco WLC GUI, the 802.11ac clients that are connected to the 802.11n radio are displayed 802.11an
clients, and the 802.11ac clients that are connected to the 802.11ac radio are displayed as 802.11ac clients.
Ensure that your WLAN has WMM enabled and open or WPA2/AES for 802.11ac to be supported. Otherwise,
the speed of 802.11ac is not available, even on 802.11ac clients.
For more information about the 802.11ac module on the Cisco Aironet 3600 Series access point, see http://
www.cisco.com/c/en/us/products/wireless/aironet-3600-series/relevant-interfaces-and-modules.html.
• Controllers do not support High availability for 802.11ac modules. The 802.11ac configuration (802.11ac
Data Rates and 802.11ac Global mode) on the controller is not synchronized with the standby controller.
This might result in client throughput fluctuations and reassociations when you explicitly disable those
configurations on the active controller.
In addition, the 802.11ac Global mode configuration controls whether the radio module is enabled. If
802.11ac Global mode is enabled on one controller but not on another, the 802.11ac module might be
disabled if the access point associates with a controller on which 802.11ac Global mode is disabled.
• When changing AP from static to auto channel assignment, by default AP moves to best possible
bandwidth supported by the radio and a valid channel. Channel number and width assignment may be
suboptimal until next DCA cycle gets started.
• SSIDs with TKIP and SSIDs with TKIP+AES are not enabled on the 802.11ac radios. Therefore, all the
5-GHz clients are expected to associate with the 802.11n radios.
Step 3 Check the check boxes of the desired rates to specify the Modulation and Coding Scheme (MCS) rates at which data
can be transmitted between the access point and the client.
MCS index 8 and 9 are specific to 802.11ac. Enabling MCS data rate with index 9 automatically enables data rate with
MCS index 8. You can enable or disable MCS index 8 only when MCS index 9 is disabled.
Note Enabling MCS data rate with MCS index 9 automatically enables data rate with MCS index 8.
Step 1 Choose Controller > Advanced > DHCP to open the DHCP Parameters page.
Step 2 Select the Enable DHCP Proxy check box to enable DHCP proxy on a global basis. Otherwise, unselect the check box.
The default value is selected.
Step 3 Click Apply to commit your changes.
Step 4 Click Save Configuration to save your changes.
Step 1 Configure the DHCP primary and secondary servers on the interface. To do this, enter the following commands:
• config interface dhcp management primary primary-server
• config interface dhcp dynamic-interface interface-name primary primary-s
Step 2 Configure DHCP proxy on the management or dynamic interface of the controller. To do this, enter the following
command:
• config interface dhcp management proxy-mode enableglobaldisable
• config interface dhcp dynamic-interface interface-name proxy-mode enableglobaldisable.
Note To ensure additional security when DHCP is configured, use the config interface dhcpinterface typeoption-82
enable command.
Step 3 Enter the save config command.
Step 4 To view the proxy settings of the controller interface enter the show dhcp proxy command.
Step 1 Choose Controller > Advanced > DHCP to open the DHCP Parameters page.
Step 2 Select the DHCP Timeout (5 - 120 seconds) check box to enable a DHCP timeout on a global basis. Otherwise, unselect
the check box. The valid range is 5 through 120 seconds.
Step 3 Click Apply to commit your changes.
Step 4 Click Save Configuration to save your changes.
Note This command behaves like an SNMP access list. It specifies the IP address from which the device accepts
SNMP packets with the associated community. An AND operation is performed between the requesting
entity’s IP address and the subnet mask before being compared to the IP address. If the subnet mask is set
to 0.0.0.0, an IP address of 0.0.0.0 matches to all IP addresses. The default value is 0.0.0.0.
Note The controller can use only one IP address range to manage an SNMP community.
• For IPv6 configuration—Configure an IPv6 address and prefix-length for an SNMP community by
entering this command:
Step 1 Choose Management and then Communities under SNMP. The SNMP v1 / v2c Community page appears.
Step 2 If “public” or “private” appears in the Community Name column, hover your cursor over the blue drop-down arrow for
the desired community and choose Remove to delete this community.
Step 3 Click New to create a new community. The SNMP v1 / v2c Community > New page appears.
Step 4 In the Community Name text box, enter a unique name containing up to 16 alphanumeric characters. Do not enter “public”
or “private.”
Step 5 In the next two text boxes, enter the IPv4/IPv6 address and IP Mask/Prefix Length from which this device accepts SNMP
packets with the associated community and the IP mask.
Step 6 Choose Read Only or Read/Write from the Access Mode drop-down list to specify the access level for this community.
Step 7 Choose Enable or Disable from the Status drop-down list to specify the status of this community.
Step 8 Click Apply to commit your changes.
Step 9 Click Save Configuration to save your settings.
Step 10 Repeat this procedure if a “public” or “private” community still appears on the SNMP v1 / v2c Community page.
Step 1 See the current list of SNMP communities for this controller by entering this command:
show snmp community
Step 2 If "public" or "private" appears in the SNMP Community Name column, enter this command to delete this community:
config snmp community delete name
The name parameter is the community name (in this case, “public” or “private”).
Step 4 For IPv4 specific configuration, enter the IPv4 address from which this device accepts SNMP packets with the associated
community by entering this command:
config snmp community ipaddr ip_address ip_mask name
Step 5 For IPv6 specific configuration, enter the IPv6 address from which this device accepts SNMP packets with the associated
community by entering this command:
config snmp community ipaddr ip_address prefix_length name
Step 6 Specify the access level for this community by entering this command, where ro is read-only mode and rw is read/write
mode:
config snmp community accessmode {ro | rw} name
Step 8 Enable or disable SNMP IPSec sessions for all SNMP communities by entering this command:
config snmp community ipsec {enable | disable} name
By default SNMP IPSec session is disabled. SNMP IPSec session must be disabled state to change the authentication
mode.
Step 11 Repeat this procedure if you still need to change the default values for a “public” or “private” community string.
Note To get the right value for the current memory usage, you should configure either sampling interval or
statistics interval.
d) Check the IPSec check box if you want to configure IPSec parameters for the trap receiver.
e) From the Auth Method drop-down list, choose the IKE authentication method as either Certificate or PSK.
• If authentication mode is configured as certificate, then Cisco WLC uses the IPSEC CA and IPSEC device
certificates for SNMP sessions.
• If authentication mode is configured as pre-shared-key, then enter a secret value. The secret value can either
be an ASCII or a hexadecimal value. If auth-mode configured is certificate, then Cisco WLC uses the ipsecCaCert
and ipsecDevCerts for SNMP over IPSEC.
Note Clients are load balanced between access points on the same controller. Load balancing does not occur
between access points on different controllers.
When a wireless client attempts to associate to a lightweight access point, association response packets are
sent to the client with an 802.11 response packet including status code 17. The code 17 indicates that the AP
is busy. The AP does not respond with an association response bearing 'success' if the AP threshold is not
met, and with code 17 (AP busy) if the AP utilization threshold is exceeded, and another less busy AP heard
the client request.
For example, if the number of clients on AP1 is more than the number of clients on AP2 plus the load-balancing
window, then AP1 is considered to be busier than AP2. When a client attempts to associate to AP1, it receives
an 802.11 response packet with status code 17, indicating that the access point is busy, and the client attempts
to associate to a different access point.
You can configure the controller to deny client associations up to 10 times (if a client attempted to associate
11 times, it would be allowed to associate on the 11th try). You can also enable or disable load balancing on
a particular WLAN, which is useful if you want to disable load balancing for a select group of clients (such
as time-sensitive voice clients).
Note Voice Client does not authenticate when delay is configured more than 300 ms. To avoid this configure
a Central-Auth, Local Switching WLAN with CCKM, configure a Pagent Router between AP and WLC
with a delay of 600 ms (300 ms UP and 300 ms DOWN and try associating the voice client
Passive scanning clients will be able to associate to an AP irrespective of whether load balancing is enabled
or not.
Note Cisco 600 Series OfficeExtend Access Points do not support client load balancing.
With the 7.4 release, FlexConnect access points do support client load balancing.
You can configure the controller to analyze the WAN interface utilization of neighboring APs and then load
balance the clients across the lightly loaded APs. You can configure this by defining a load balancing threshold.
By defining the threshold, you can measure the WAN interface utilization percentage. For example, a threshold
value of 50 triggers the load balancing upon detecting utilization of 50% or more on an AP-WAN interface.
Note For a FlexConnect AP the association is locally handled. The load-balancing decisions are taken at the
Cisco WLC. A FlexConnect AP initially responds to the client before knowing the result of calculations
at the Cisco WLC. Load-balancing doesn't take effect when the FlexConnect AP is in standalone mode.
FlexConnect AP does not send (re)association response with status 17 for Load-Balancing as Local mode
APs do; instead, it first sends (re)association with status 0 (success) and then deauth with reason 5.
Step 1 Choose Wireless > Advanced > Load Balancing to open the Load Balancing page.
Step 2 In the Client Window Size text box, enter a value between 1 and 20.
The window size becomes part of the algorithm that determines whether an access point is too heavily loaded to accept
more client associations:
load-balancing window + client associations on AP with the lightest load = load-balancing threshold
In the group of access points accessible to a client device, each access point has a different number of client associations.
The access point with the lowest number of clients has the lightest load. The client window size plus the number of
clients on the access point with the lightest load forms the threshold. Access points with more client associations than
this threshold is considered busy, and clients can associate only to access points with client counts lower than the threshold.
Step 3 In the Maximum Denial Count text box, enter a value between 0 and 10.
The denial count sets the maximum number of association denials during load balancing.
Step 1 Set the client window for aggressive load balancing by entering this command:
config load-balancing window client_count
You can enter a value between 0 and 20 for the client_count parameter.
Step 2 Set the denial count for load balancing by entering this command:
config load-balancing denial denial_count
You can enter a value between 1 and 10 for the denial_count parameter.
Step 1 See the current status of 802.3 bridging for all WLANs by entering this command:
show network
Step 2 Enable or disable 802.3 bridging globally on all WLANs by entering this command:
config network 802.3-bridging {enable | disable}
The default value is disabled.
When you enable multicast mode and the controller receives a multicast packet from the wired LAN, the
controller encapsulates the packet using CAPWAP and forwards the packet to the CAPWAP multicast group
address. The controller always uses the management interface for sending multicast packets. Access points
in the multicast group receive the packet and forward it to all the BSSIDs mapped to the interface on which
clients receive multicast traffic. From the access point perspective, the multicast appears to be a broadcast to
all SSIDs.
Note Until Release 7.5, the port number used for CAPWAP multicast was 12224. From Release 7.6 onwards,
the port number used for CAPWAP is changed to 5247.
The controller supports Multicast Listener Discovery (MLD) v1 snooping for IPv6 multicast. This feature
keeps track of and delivers IPv6 multicast flows to the clients that request them. To support IPv6 multicast,
you must enable Global Multicast Mode.
Note When you disable the Global Multicast Mode, the controller still forwards the IPv6 ICMP multicast
messages, such as router announcements and DHCPv6 solicits, as these are required for IPv6 to work. As
a result, enabling the Global Multicast Mode on the controller does not impact the ICMPv6 and the
DHCPv6 messages. These messages will always be forwarded irrespective of whether or not the Global
Multicast Mode is enabled.
Internet Group Management Protocol (IGMP) snooping is available to better direct multicast packets. When
this feature is enabled, the controller gathers IGMP reports from the clients, processes them, creates unique
multicast group IDs (MGIDs) from the IGMP reports after selecting the Layer 3 multicast address and the
VLAN number, and sends the IGMP reports to the infrastructure switch. The controller sends these reports
with the source address as the interface address on which it received the reports from the clients. The controller
then updates the access point MGID table on the access point with the client MAC address. When the controller
receives multicast traffic for a particular multicast group, it forwards it to all the access points, but only those
access points that have active clients listening or subscribed to that multicast group send multicast traffic on
that particular WLAN. IP packets are forwarded with an MGID that is unique for an ingress VLAN and the
destination multicast group. Layer 2 multicast packets are forwarded with an MGID that is unique for the
ingress interface.
When IGMP snooping is disabled, the following is true:
• The controller always uses Layer 2 MGID when it sends multicast data to the access point. Every interface
created is assigned one Layer 2 MGID. For example, the management interface has an MGID of 0, and
the first dynamic interface created is assigned an MGID of 8, which increments as each dynamic interface
is created.
• The IGMP packets from clients are forwarded to the router. As a result, the router IGMP table is updated
with the IP address of the clients as the last reporter.
Note The MGIDs are controller specific. The same multicast group packets coming from the
same VLAN in two different controllers may be mapped to two different MGIDs.
Note If Layer 2 multicast is enabled, a single MGID is assigned to all the multicast addresses
coming from an interface.
Note The number of multicast addresses supported per VLAN for a Cisco WLC is 100.
• When you enable multicast mode on the controller, you also must configure a CAPWAP multicast group
address. Access points subscribe to the CAPWAP multicast group using IGMP.
• Cisco 1100, 1130, 1200, 1230, and 1240 access points use IGMP versions 1, 2, and 3.
• Access points in monitor mode, sniffer mode, or rogue detector mode do not join the CAPWAP multicast
group address.
• The CAPWAP multicast group configured on the controllers should be different for different controllers.
• Lightweight Access Points transmit multicast packets at the highest configured mandatory data rate.
Because multicast frames are not retransmitted at the MAC layer, clients at the edge of the cell might
fail to receive them successfully. If reliable reception is a goal, multicast frames should be transmitted
at a low data rate. If support for high data rate multicast frames is required, it might be useful to shrink
the cell size and disable all lower data rates.
Depending on your requirements, you can take the following actions:
◦If you need to transmit multicast data with the greatest reliability and if there is no need for great
multicast bandwidth, then configure a single basic rate, that is low enough to reach the edges of
the wireless cells.
◦If you need to transmit multicast data at a certain data rate in order to achieve a certain throughput,
you can configure that rate as the highest basic rate. You can also set a lower basic rate for coverage
of nonmulticast clients.
• Multicast mode does not operate across intersubnet mobility events such as guest tunneling. It does,
however, operate with interface overrides using RADIUS (but only when IGMP snooping is enabled)
and with site-specific VLANs (access point group VLANs).
• For LWAPP, the controller drops multicast packets sent to UDP control port 12223. For CAPWAP, the
controller drops multicast packets sent to UDP control and data ports 5246 and 5247, respectively.
Therefore, you may want to consider not using these port numbers with the multicast applications on
your network.
• We recommend that any multicast applications on your network not use the multicast address configured
as the CAPWAP multicast group address on the controller.
• For multicast to work on Cisco 2500 Series WLC, you have to configure the multicast IP address.
• Multicast mode is not supported on Cisco Flex 7500 Series WLCs.
• In a multicast group, when multicast audio is initiated, the recipients do not hear the first two seconds
of the multicast audio. As a workaround, we recommend that you set the Cisco APs to FlexConnect +
Local Switching mode for small-scale deployments.
• To reduce join latency, we recommend disabling IPv6 on the Cisco WLC.
• FlexConnect APs do not join the multicast group when the Multicast mode is Multicast-Multicast and
CAPWAP has IPv4 and IPv6. For Cisco 5508 and 8510 WLCs, you can disable the Multicast-Multicast
mode and enable the Multicast-Unicast mode. For Cisco Flex 7510 WLC, there is no Multicast-Multicast
configuration. For FlexConnect APs in Multicast-Multicast mode joined with central switching clients,
there is reduction of 0-13 percent in data throughput.
• We recommend that you do not use Broadcast-Unicast or Multicast-Unicast mode on Cisco WLC setup
where there are more than 50 APs connected together.
If a Cisco WLC setup has more than 50 APs, the CAPWAP control messages between Cisco WLC and
AP may be delayed due to duplication of each Multicast or Broadcast traffic to each of the APs. The
delay in the CAPWAP control messages causes client association or 802.1X authentication to be delayed
for 1 to 3 seconds. As a result of this, the client receives repeated authentication prompts or failure
messages.
• While using Local and FlexConnect AP mode the Cisco WLC platform's multicast support differs for
different platforms.
The parameters that affect Multicast forwarding are:
◦Cisco WLC platform.
◦Global AP multicast mode configuration at Cisco WLC.
◦Mode of the AP—Local, FlexConnect central switching.
◦For Local switching, it does not send/receive the packet to/from Cisco WLC, so it does not matter
which Multicast mode is configured on the Cisco WLC.
Note FlexConnect mode AP cannot join Multicast group address configured at Cisco WLC.
Therefore, the FlexConnect mode AP cannot receive Multicast packets that are sent by
Cisco WLC (Multicast packets sent by FlexConnect central switching is received by
local mode APs). If Multicast needs to be forwarded for FlexConnect central switching,
you must configure AP mode as Multicast to Unicast. This configuration is global
because it is applicable to local mode AP.
• Effective with Release 8.2.100.0, it is not possible to download some of the older configurations from
the Cisco WLC because of the Multicast and IP address validations introduced in this release. The
platform support for global multicast and multicast mode are listed in the following table.
Disabled Multicast No
Disabled Multicast No
Step 7 In the MLD Timeout text box, enter a value between 30 and 7200 seconds to set the MLD timeout.
Step 8 Enter the MLD Query Interval (seconds). The valid range is between 15 and 2400 seconds.
Step 9 Click Apply.
Step 10 Click Save Configuration.
Step 1 Choose Monitor > Multicast. The Multicast Groups page appears.
This page shows all the multicast groups and their corresponding MGIDs.
Step 2 Click the link for a specific MGID (such as MGID 550) to see a list of all the clients joined to the multicast group in that
particular MGID.
• See all the clients joined to the multicast group in a specific MGID by entering this command:
show network multicast mgid detail mgid_value
where the mgid_value parameter is a number between 550 and 4095.
Information similar to the following appears:
Mgid........................................ 550
Multicast Group Address..................... 239.255.255.250
Vlan........................................ 0
Rx Packet Count............................. 807399588
No of clients............................... 1
Client List.................................
Client MAC Expire Time (mm:ss)
00:13:02:23:82:ad 0:20
Step 1 Initiate a remote debug of the access point by entering this command:
debug ap enable Cisco_AP
Step 2 See all of the MGIDs on the access point and the number of clients per WLAN by entering this command:
debug ap command “show capwap mcast mgid all” Cisco_AP
Step 3 See all of the clients per MGID on the access point and the number of clients per WLAN by entering this command:
debug ap command “show capwap mcast mgid id mgid_value” Cisco_AP
mDNS AP
The mDNS AP feature allows the controller to have visibility of wired service providers that are on VLANs
that are not visible to the controller. You can configure any AP as an mDNS AP and enable the AP to forward
mDNS packets to the controller. VLAN visibility on the controller is achieved by APs that forward the mDNS
advertisements to the controller. The mDNS packets between the AP and the controller are forwarded in
Control and Provisioning of Wireless Access Points (CAPWAP) data tunnel that is similar to the mDNS
packets from a wireless client. Only CAPWAP v4 tunnels are supported. APs can be in either the access port
or the trunk port to learn the mDNS packets from the wired side and forward them to the controller.
You can use the configurable knob that is provided on the controller to start or stop mDNS packet forwarding
from a specific AP. You can also use this configuration to specify the VLANs from which the AP should
snoop the mDNS advertisements from the wired side. The maximum number of VLANs that an AP can snoop
is 10.
If the AP is in the access port, you should not configure any VLANs on the AP to snoop. The AP sends
untagged packets when a query is to be sent. When an mDNS advertisement is received by the mDNS AP,
the VLAN information is not passed on to the controller. The service provider's VLAN that is learned through
the mDNS AP's access VLAN is maintained as 0 in the controller.
By default, the mDNS AP snoops in native VLAN. When an mDNS AP is enabled, native VLAN snooping
is enabled by default and the VLAN information is passed as 0 for advertisements received on the native
VLAN.
The mDNS AP feature is supported only on local mode and monitor mode APs.
The mDNS AP configuration is retained on those mDNS APs even if global mDNs snooping is disabled.
Note There is no check to ensure that no two mDNS APs are duplicating the same traffic for the same service.
But, for the same VLAN, there is such a check.
If an mDNS AP is reset or associated with the same controller or another controller, one of the following
occurs:
• If the global snooping is disabled on the controller, a payload is sent to the AP to disable mDNS snooping.
• If the global snooping is enabled on the controller, the configuration of the AP before the reset or the
association procedure is retained.
If the total number of service providers for all services is within the specified limit, any service is free to learn
or discover as many other services. There is no per service reservation or restriction, which allows flexibility
to accommodate more service providers for any service with respect to other services.
• mDNS APs cannot duplicate the same traffic for the same service or VLAN.
• LSS filtering is restricted to only wireless services.
• The LSS, mDNS AP, Priority MAC address, and origin-based discovery features cannot be configured
using the controller GUI.
Step 1 Configure the global mDNS parameters and the Master Services Database by following these steps:
a) Choose Controller > mDNS > General.
b) Select or unselect the mDNS Global Snooping check box to enable or disable snooping of mDNS packets, respectively.
c) Enter the mDNS query interval in minutes. The query interval is the frequency at which the controller queries for a
service.
d) Choose a service from the Select Service drop-down list.
Note To add a new mDNS-supported service to the list, choose Other. Specify the service name and the service
string. The controller snoops and learns about the mDNS service advertisements only if the service is available
in the Master Services Database. The controller can snoop and learn a maximum of 64 services.
e) Select or unselect the Query Status check box to enable or disable an mDNS query for a service, respectively.
f) Click Add.
g) Click Apply.
h) To view the details of an mDNS service, hover your cursor over the blue drop-down arrow of a service, and choose
Details.
Step 2 Configure an mDNS profile by following these steps:
a) Choose Controller > mDNS > Profiles.
The controller has a default mDNS profile, which is default-mdns-profile. It is not possible to delete the default
profile.
b) To create a new profile, click New, enter a profile name, and click Apply.
c) To edit a profile, click a profile name on the mDNS Profiles page; from the Service Name drop-down list, choose
a service to be associated with the profile, and click Apply.
You can add multiple services to a profile.
What to Do Next
After creating a new profile, you must map the profile to an interface group, an interface, or a WLAN. Clients
receive service advertisements only for the services associated with the profile. The highest priority is given
to the profiles associated with interface groups, followed by the interface profiles, and then the WLAN profiles.
Each client is mapped to a profile based on the order of priority.
• Map an mDNS profile to an interface group by following these steps:
1 Choose Controller > Interface Groups.
2 Click the corresponding interface group name.
Note The wireless controller advertises the services from the wired devices (such as Apple TVs) learnt over
VLANs, when:
• mDNS snooping is enabled in the WLAN Advanced options.
• mDNS profile is enabled either at interface group (if available), interface, or WLAN.
Note If you try to delete an mDNS profile that is already associated with an interface group,
an interface, or a WLAN, an error message is displayed.
Note If the mDNS profile name is none, no profiles are attached to the interface group. Any
existing profile that is attached is removed.
• View information about an mDNS profile that is associated with an interface group by entering this
command:
show interface group detailed interface-group-name
• Map an mDNS profile to an interface by entering this command:
config interface mdns-profile {management | {interface-name | all}} {mdns-profile-name | none}
• View information about the mDNS profile that is associated with an interface by entering this command:
show interface detailed interface-name
• Configure mDNS for a WLAN by entering this command:
config wlan mdns {enable | disable} {wlan-id | all}
• Map an mDNS profile to a WLAN by entering this command:
config wlan mdns profile {wlan-id | all} {mdns-profile-name | none}
• View information about an mDNS profile that is associated with a WLAN by entering this command:
show wlan wlan-id
• View information about all mDNS profiles or a particular mDNS profile by entering this command:
show mdns profile {summary | detailed mdns-profile-name}
• View information about all mDNS services or a particular mDNS service by entering this command:
show mdns service {summary | detailed mdns-service-name}
• View information about the mDNS domain names that are learned by entering this command:
show mdns domain-name-ip summary
• View the mDNS profile for a client by entering this command:
show client detail client-mac-address
• View the mDNS details for a network by entering this command:
show network summary
• Clear the mDNS service database by entering this command:
◦Configure per-service MAC addresses of service-providing devices to ensure that they are snooped
and discovered even if the service provider database is full, by entering this command:
config mdns service priority-mac {add | delete} priority-mac-addr service-name ap-group
ap-group-name
The optional AP group is applicable only to wired service provider devices to give them a sense
of location; these service providers are placed higher in the order than the other wired devices.
◦View the status of Priority MAC address by entering this command:
Detailed—show mdns service detailed service-name
The configuration can be applied to wired and wireless service instances. The response to any query is on the
policy configured for each service instance. The response enables the selective sharing of service instances
based on the location, user-id or role.
As the most service publishing devices are wired, the configuration allows filtering of wired services at par
with the wireless service instances.
There are two levels of filtering client queries:
1 At the service type level by using the mDNS profile
2 At the service instance level using the access policy associated with the service.
Step 1 Log in to the Cisco Prime Infrastructure using the Admin credentials.
Step 2 Choose Administration > AAA > Users > Add User.
Step 3 Choose mDNS Policy Admin.
Step 4 Add or remove the devices in the mDNS Device Filter. Click Save.
Step 5 Add the users for a device in the Users list dialog box. Click Save.
Note See Cisco Prime Infrastructure Administrator Guide for the release 2.2 for more details.
Note The list of current service instances associated with the service group is shown in a
table.
Step 4 Under Policy / Rule enter the role names and the user names as the criteria of enforcing the policy.
Step 1 Enable or disable the mDNS policy by entering this command: config mdns policy enable | disable
Step 2 Create or delete a mDNS policy service group by entering this command: config mdns policy service-group create |
delete <service-group-name>
Step 3 Configure the parameters of a service group by entering this command: config mdns policy service-group device-mac
add <service-group-name> <mac-addr> <device name> location-type [<AP_LOCATION | AP_NAME | AP_GROUP>]
device-location [<location string | any | same>]
Step 4 Configure the user role for a service-group by entering this command: config mdns policy service-group user-role add
| delete <service-group-name> <user-role-name>
Step 5 Configure the user name for a service-group by entering this command: config mdns policy service-group user-name
add | delete <service-group-name> <user-name>
Multicast Configuration for Cisco vWLC, Flex 7510, 5520, 8510, and 8540 WLCs
Step 1 Assign both IPv4 and IPv6 (required only if IPv6 is enabled) multicast addresses by entering this command:
a) config network multicast mode multicast IPv4-multicast-address
Restrictions
• We recommend that you do not switch from Multicast-Multicast mode to Multicast-Unicast mode on a
loaded network because it can burden the network. We recommend that you use Multicast-Multicast
mode on these platforms because of the scale factor.
• IGMP and MLD snooping cannot be enabled unless global multicast is enabled, and multicast mode is
Multicast-Multicast.
• Global multicast can be enabled only when Multicast-Multicast mode is configured.
• Switching from Multicast-Multicast mode to Multicast-Unicast mode is not allowed if the global multicast
is enabled. You must disable global multicast before switching the mode in this case.
• FlexConnect APs:
• Can join in Multicast-Multicast mode from Release 8.0 onwards.
• Multicast-Unicast mode has to be enabled if IPv6 support is required on FlexConnect APs by the
central-switching clients. Therefore, IGMP or MLD snooping is not supported.
• VideoStream is not supported because it requires IGMP or MLD snooping.
Troubleshooting
Solution—Disable IPv6 if it is not being used or switch Multicast-Unicast to Multicast-Multicast mode for
IPv6.
Inter-Controller Roaming
Multiple-controller deployments support client roaming across access points managed by controllers in the
same mobility group and on the same subnet. This roaming is also transparent to the client because the session
is sustained and a tunnel between controllers allows the client to continue using the same DHCP- or
client-assigned IP address as long as the session remains active. The tunnel is torn down, and the client must
reauthenticate when the client sends a DHCP Discover with a 0.0.0.0 client IP address or a 169.254.*.* client
auto-IP address or when the operator-set session timeout is exceeded.
Intra-Controller Roaming
Each controller supports same-controller client roaming across access points managed by the same controller.
This roaming is transparent to the client as the session is sustained, and the client continues using the same
DHCP-assigned or client-assigned IP address. The controller provides DHCP functionality with a relay
Inter-Subnet Roaming
Multiple-controller deployments support client roaming across access points managed by controllers in the
same mobility group on different subnets. This roaming is transparent to the client because the session is
sustained and a tunnel between the controllers allows the client to continue using the same DHCP-assigned
or client-assigned IP address as long as the session remains active. The tunnel is torn down, and the client
must reauthenticate when the client sends a DHCP Discover with a 0.0.0.0 client IP address or a 169.254.*.*
client auto-IP address or when the operator-set user timeout is exceeded.
Note To see whether a particular client supports E2E, choose Wireless > Clients on the
controller GUI, click the Detail link for the desired client, and look at the E2E Version
text box in the Client Properties area.
• Roam reason report—This feature enables CCXv4 clients to report the reason why they roamed to a
new access point. It also allows network administrators to build and monitor a roam history.
• Directed roam request—This feature enables the controller to send directed roam requests to the client
in situations when the controller can better service the client on an access point different from the one
to which it is associated. In this case, the controller sends the client a list of the best access points that
it can join. The client can either honor or ignore the directed roam request. Non-CCX clients and clients
running CCXv3 or below must not take any action. No configuration is required for this feature.
Step 1 Choose Wireless > 802.11a/n/ac or 802.11b/g/n > Client Roaming. The 802.11a (802.11b) > Client Roaming page
appears.
Step 2 If you want to fine-tune the RF parameters that affect client roaming, choose Custom from the Mode drop-down list
and go to Step 3. If you want to leave the RF parameters at their default values, choose Default and go to Step 8.
Step 3 In the Minimum RSSI text box, enter a value for the minimum received signal strength indicator (RSSI) required for
the client to associate to an access point. If the client’s average received signal power dips below this threshold, reliable
communication is usually impossible. Therefore, clients must already have found and roamed to another access point
with a stronger signal before the minimum RSSI value is reached.
The range is –90 to –50 dBm.
The default is –85 dBm.
Step 4 In the Hysteresis text box, enter a value to indicate how much greater the signal strength of a neighboring access point
must be in order for the client to roam to it. This parameter is intended to reduce the amount of roaming between access
points if the client is physically located on or near the border between two access points.
The range is 3 to 20 dB.
The default is 3 dB.
Step 5 In the Scan Threshold text box, enter the minimum RSSI that is allowed before the client should roam to a better access
point. When the RSSI drops below the specified value, the client must be able to roam to a better access point within the
specified transition time. This parameter also provides a power-save method to minimize the time that the client spends
in active or passive scanning. For example, the client can scan slowly when the RSSI is above the threshold and scan
more rapidly when the RSSI is below the threshold.
The range is –90 to –50 dBm.
The default is –72 dBm.
Step 6 In the Transition Time text box, enter the maximum time allowed for the client to detect a suitable neighboring access
point to roam to and to complete the roam, whenever the RSSI from the client’s associated access point is below the scan
threshold.
The Scan Threshold and Transition Time parameters guarantee a minimum level of client roaming performance. Together
with the highest expected client speed and roaming hysteresis, these parameters make it possible to design a wireless
LAN network that supports roaming simply by ensuring a certain minimum overlap distance between access points.
The range is 1 to 5 seconds.
The default is 5 seconds.
Step 1 View the current RF parameters configured for client roaming for the 802.11a or 802.11b/g network by entering this
command:
show {802.11a | 802.11b} l2roam rf-param
Step 2 View the CCX Layer 2 client roaming statistics for a particular access point by entering this command:
show {802.11a | 802.11b} l2roam statistics ap_mac
This command provides the following information:
Step 3 View the roaming history for a particular client by entering this command:
show client roam-history client_mac
This command provides the following information:
• The time when the report was received
• The MAC address of the access point to which the client is currently associated
• The MAC address of the access point to which the client was previously associated
• The channel of the access point to which the client was previously associated
• The SSID of the access point to which the client was previously associated
• The time when the client disassociated from the previous access point
• The reason for the client roam
Note If the IP address or MAC address of the packet has been spoofed, the check does not pass, and the controller
discards the packet. Spoofed packets can pass through the controller only if both the IP and MAC addresses
are spoofed together and changed to that of another valid client on the same controller.
Note You must disable this binding check in order to use an access point in sniffer mode if the access point is joined
to a Cisco 5500 Series Controller.
Step 2 Save your changes by entering this command:
save config
Step 3 View the status of IP-MAC address binding by entering this command:
show network summary
Information similar to the following appears:
...<?Line-Break?><?HardReturn?>
You can configure the bandwidth of each QoS level using QoS profiles and then apply the profiles to WLANs.
The profile settings are pushed to the clients associated to that WLAN. In addition, you can create QoS roles
to specify different bandwidth levels for regular and guest users. Follow the instructions in this section to
configure QoS profiles and QoS roles. You can also define the maximum and default QoS levels for unicast
and multicast traffic when you assign a QoS profile to a WLAN.
The wireless rate limits can be defined on both upstream and downstream traffic. Rate limits can be defined
per SSID and/or specified as a maximum rate limit for all clients. These rate limits can be individually
configured.
Step 1 Disable the 802.11a and 802.11b/g networks so that you can configure the QoS profiles.
To disable the radio networks, choose Wireless > 802.11a/n/ac or 802.11b/g/n > Network, unselect the 802.11a (or
802.11b/g) Network Status check box, and click Apply.
Step 2 Choose Wireless > QoS > Profiles to open the QoS Profiles page.
Step 3 Click the name of the profile that you want to configure to open the Edit QoS Profile page.
Step 4 Change the description of the profile by modifying the contents of the Description text box.
Step 5 Define the data rates on a per-user basis as follows:
a) Define the average data rate for TCP traffic per user by entering the rate in Kbps in the Average Data Rate text boxes.
A value of 0 indicates that the value specified in the selected QoS profile will take effect.
b) Define the peak data rate for TCP traffic per user by entering the rate in Kbps in the Burst Data Rate text boxes. A
value of 0 indicates that the value specified in the selected QoS profile will take effect.
Note The burst data rate should be greater than or equal to the average data rate. Otherwise, the QoS policy may
block traffic to and from the wireless client.
Ensure that you configure the average data rate before you configure the burst data rate.
c) Define the average real-time rate for UDP traffic per user by entering the rate in Kbps in the Average Real-Time
Rate text boxes. A value of 0 indicates that the value specified in the selected QoS profile will take effect.
Note Average Data Rate is used to measure TCP traffic while Average Real-time rate is used for UDP traffic.
They are measured in kbps for all the entries. The values for Average Data Rate and Average Real-time rate
can be different because they are applied to different upper layer protocols such as TCP and UDP. These
different values for the rates do not impact the bandwidth.
d) Define the peak real-time rate for UDP traffic per user by entering the rate in Kbps in the Burst Real-Time Rate text
boxes. A value of 0 indicates that the value specified in the selected QoS profile will take effect.
Note The burst real-time rate should be greater than or equal to the average real-time rate. Otherwise, the QoS
policy may block traffic to and from the wireless client.
Step 7 Define the maximum and default QoS levels for unicast and multicast traffic when you assign a QoS profile to a WLAN.
a) From the Maximum Priority drop-down list, choose the maximum QoS priority for any data frames transmitted by
the AP to any station in the WLAN.
For example, a QoS profile named ‘gold’ targeted for video applications has the maximum priority set to video by
default.
b) From the Unicast Default Priority drop-down list, choose the QoS priority for unicast data frames transmitted by the
AP to non-WMM stations in the WLAN
c) From the Multicast Default Priority drop-down list, choose the QoS priority for multicast data frames transmitted by
the AP to stations in the WLAN,
Note The default unicast priority cannot be used for non-WMM clients in a mixed WLAN.
Step 8 Choose 802.1p from the Protocol Type drop-down list and enter the maximum priority value in the 802.1p Tag text box
to define the maximum value (0–7) for the priority tag associated with packets that fall within the profile.
The tagged packets include CAPWAP data packets (between access points and the controller) and packets sent toward
the core network.
Note If a QoS profile has 802.1p tagging configured and if this QoS profile is assigned to a WLAN that uses an
untagged interface on the controller, the client traffic will be blocked.
Step 9 Click Apply.
Step 10 Click Save Configuration.
Step 11 Reenable the 802.11 networks.
To enable the radio networks, choose Wireless > 802.11a/n/ac or 802.11b/g/n > Network, select the 802.11a (or
802.11b/g) Network Status check box, and click Apply.
Step 12 Choose WLANs and select a WLAN ID to apply the new QoS profile to it.
Step 13 In the WLAN > Edit page, go to the QoS tab and select the QoS Profile type from the Quality of Service drop-down
list. The QoS profile will add the rate limit values configured on the controller on per WLAN, per radio and per AP basis.
For example, if upstream rate limit of 5Mbps is configured for a QoS profile of type silver, then every WLAN that has
silver profile will limit traffic to 5Mbps (5Mbps for each wlan) on each radio and on each AP where the WLAN is
applicable.
Step 1 Disable the 802.11a and 802.11b/g networks so that you can configure the QoS profiles by entering these commands:
config 802.11{a | b} disable network
Step 3 Define the average data rate for TCP traffic per user or per SSID by entering this command:
config qos average-data-rate {bronze | silver | gold | platinum} {per-ssid | per-client} {downstream | upstream}
rate
Note For the rate parameter, you can enter a value between 0 and 512,000 Kbps (inclusive). A value of 0 imposes
no bandwidth restriction on the QoS profile.
Step 4 Define the peak data rate for TCP traffic per user or per SSID by entering this command:
config qos burst-data-rate {bronze | silver | gold | platinum} {per-ssid | per-client} {downstream | upstream} rate
Step 5 Define the average real-time data rate for UDP traffic per user or per SSID by entering this command:
config qos average-realtime-rate {bronze | silver | gold | platinum} {per-ssid | per-client} {downstream | upstream}
rate
Step 6 Define the peak real-time data rate for UDP traffic per user or per SSID by entering this command:
config qos burst-realtime-rate {bronze | silver | gold | platinum} {per-ssid | per-client} {downstream | upstream}
rate
Step 7 Define the maximum and default QoS levels for unicast and multicast traffic when you assign a QoS profile to a WLAN
by entering this command:
config qos priority {bronze | gold | platinum | silver} {maximum priority} {default unicast priority} {default multicast
priority}
You choose from the following options for the maximum priority, default unicast priority, and default multicast priority
parameters:
• besteffort
• background
• video
• voice
Step 8 Define the maximum value (0–7) for the priority tag associated with packets that fall within the profile, by entering these
commands:
config qos protocol-type {bronze | silver | gold | platinum} dot1p
config qos dot1p-tag {bronze | silver | gold | platinum} tag
The tagged packets include CAPWAP data packets (between access points and the controller) and packets sent toward
the core network.
Note The 802.1p tagging has impact only on wired packets. Wireless packets are impacted only by the maximum
priority level set for a QoS profile.
Note If a QoS profile has 802.1p tagging configured and if this QoS profile is assigned to a WLAN that uses an
untagged interface on the controller, the client traffic will be blocked.
Step 9 Reenable the 802.11a and 802.11b/g networks so that you can configure the QoS profiles by entering these commands:
config 802.11{a | b} enable network
Step 10 Apply the new QoS profile to a WLAN, by entering these commands:
config wlan qos <WLAN ID> {bronze | silver | gold | platinum}
Note If you choose to create an entry on the RADIUS server for a guest user and enable RADIUS authentication
for the WLAN on which web authentication is performed rather than adding a guest user to the local user
database from the controller, you need to assign the QoS role on the RADIUS server itself. To do so, a
“guest-role” Airespace attribute needs to be added on the RADIUS server with a datatype of “string” and
a return value of “11.” This attribute is sent to the controller when authentication occurs. If a role with the
name returned from the RADIUS server is found configured on the controller, the bandwidth associated
to that role is enforced for the guest user after authentication completes successfully.
Step 1 Choose Wireless > QoS > Roles to open the QoS Roles for the Guest Users page.
This page shows any existing QoS roles for guest users.
Note If you want to delete a QoS role, hover your cursor over the blue drop-down arrow for that role and choose
Remove.
Step 2 Click New to create a new QoS role. The QoS Role Name > New page appears.
Step 3 In the Role Name text box, enter a name for the new QoS role. The name should uniquely identify the role of the QoS
user (such as Contractor, Vendor, and so on).
Step 4 Click Apply.
Step 5 Click the name of the QoS role to edit the bandwidth of a QoS role. The Edit QoS Role Data Rates page appears.
Note The values that you configure for the per-user bandwidth contracts affect only the amount of bandwidth going
downstream (from the access point to the wireless client). They do not affect the bandwidth for upstream traffic
(from the client to the access point).
Note The Access Points that support per-user bandwidth contracts for upstream (from the client to the access point)
are - AP1140, AP1040, AP3500, AP3600, AP1250, and AP1260.
Step 6 Define the average data rate for TCP traffic on a per-user basis by entering the rate in Kbps in the Average Data Rate
text box. You can enter a value between 0 and 60,000 Kbps (inclusive). A value of 0 imposes no bandwidth restriction
on the QoS role.
Step 7 Define the peak data rate for TCP traffic on a per-user basis by entering the rate in Kbps in the Burst Data Rate text box.
You can enter a value between 0 and 60,000 Kbps (inclusive). A value of 0 imposes no bandwidth restriction on the QoS
role.
Note The burst data rate should be greater than or equal to the average data rate. Otherwise, the QoS policy may block
traffic to and from the wireless client.
Ensure that you configure the average data rate before you configure the burst data rate.
Step 8 Define the average real-time rate for UDP traffic on a per-user basis by entering the rate in Kbps in the Average Real-Time
Rate text box. You can enter a value between 0 and 60,000 Kbps (inclusive). A value of 0 imposes no bandwidth
restriction on the QoS role.
Step 9 Define the peak real-time rate for UDP traffic on a per-user basis by entering the rate in Kbps in the Burst Real-Time
Rate text box. You can enter a value between 0 and 60,000 Kbps (inclusive). A value of 0 imposes no bandwidth
restriction on the QoS role.
Note The burst real-time rate should be greater than or equal to the average real-time rate. Otherwise, the QoS policy
may block traffic to and from the wireless client.
Step 10 Click Apply.
Step 11 Click Save Configuration.
Step 12 Apply a QoS role to a guest user by following the instructions in the Configuring Local Network Users for the Controller
(GUI) section.
Step 1 Create a QoS role for a guest user by entering this command:
config netuser guest-role create role_name
Note If you want to delete a QoS role, enter the config netuser guest-role delete role_name command.
Step 2 Configure the bandwidth contracts for a QoS role by entering these commands:
• config netuser guest-role qos data-rate average-data-rate role_name rate—Configures the average data rate
for TCP traffic on a per-user basis.
• config netuser guest-role qos data-rate burst-data-rate role_name rate—Configures the peak data rate for TCP
traffic on a per-user basis.
Note The burst data rate should be greater than or equal to the average data rate. Otherwise, the QoS policy may
block traffic to and from the wireless client.
• config netuser guest-role qos data-rate average-realtime-rate role_name rate—Configures the average real-time
rate for UDP traffic on a per-user basis.
• config netuser guest-role qos data-rate burst-realtime-rate role_name rate—Configures the peak real-time rate
for UDP traffic on a per-user basis.
Note The burst real-time rate should be greater than or equal to the average real-time rate. Otherwise, the QoS
policy may block traffic to and from the wireless client.
Note For the role_name parameter in each of these commands, enter a name for the new QoS role. The name
should uniquely identify the role of the QoS user (such as Contractor, Vendor, and so on). For the rate
parameter, you can enter a value between 0 and 60,000 Kbps (inclusive). A value of 0 imposes no bandwidth
restriction on the QoS role.
Step 5 See a list of the current QoS roles and their bandwidth parameters by entering this command:
show netuser guest-roles
Information similar to the following appears:
Note You can view list of 30 applications in Top Applications in Monitor Summary section of the UI.
AVC DSCP marks only the DSCP of the original packet in the controller in both directions (upstream and
downstream). It does not affect the outer CAPWAP DCSP. AVC DSCP is applicable only when the application
is classified. For example, based on the AVC profile configuration, if an application is classified as ftp or
http, the corresponding DSCP marking is applied irrespective of the WLAN QoS. For downstream, the DSCP
value of outer CAPWAP header and inner packet’s DSCP are taken from AVC DSCP. WLAN QoS is only
applicable for all traffic from WLC to AP through CAPWAP. It does not change the DSCP of the original
packet.
Using AVC rule, you can limit the bandwidth of a particular application for all the clients joined on the WLAN.
These bandwidth contracts coexist with per-client downstream rate limiting with per client downstream rate
limits that takes precedence over the per-application rate limits.
Note When you downgrade the controller from 8.0 to any earlier version, the AVC rate limit rules display the
action as drop. This action is expected since the AVC rate limit rule is introduced in the controller version
8.0.
AVC is supported in central switching mode on the following controller platforms: Cisco 2500 Series Wireless
Controllers, Cisco 5500 Series Wireless Controllers, Cisco Flex 7500 Series Wireless Controllers, Cisco 8500
Series Wireless Controllers, and Cisco Wireless Services Module 2 (WiSM2).
The number of concurrent flows supported for AVC classification on different controller platforms for 8.0
release are noted in the following table. The absolute maximum number of flows supported on one platform
cannot exceed more than 110% of the numbers shown in the following table and this 10% extra flows support
will happen based on availability of the free memory in the system.
Controller Flow
Cisco 5500 Series Wireless LAN Controller 1,75,000
Cisco 2500 Series Wireless LAN Controller 25,000
WISM-2 3,75,000
Cisco 8500 Series Wireless LAN Controller 3,50,000
i) If you choose Mark from the Action drop-down list, choose a DSCP value from the DSCP (0 to 63) drop-down list.
The DSCP value is a packet header code that is used to define QoS across the Internet. The DSCP values are mapped
to the following QoS levels:
You can also choose Custom and specify the DSCP value. The valid range is from 0 to 63.
j) Click Apply.
k) Click Save Configuration.
Step 2 Associate an AVC profile to a WLAN by following these steps:
a) Choose WLANs and click the corresponding WLAN ID.
The WLANs > Edit page is displayed.
b) Click the QoS tab.
c) Choose the AVC profile from the AVC Profile drop-down list.
d) Click Apply.
e) Click Save Configuration.
• View information about all AVC profile or a particular AVC profile by entering this command:
show avc profile {summary | detailed avc-profile-name}
• View information about AVC applications by entering these commands:
◦show avc applications [application-group]—Displays all the supported AVC applications for the
application group.
◦show avc statistics application application_name top-users [downstream wlan | upstream wlan
| wlan] [wlan_id ]} —Displays AVC statistics for the top users of an application.
◦show avc statistics top-apps [upstream | downstream]—Displays the AVC statistics for the
most used application.
◦show avc statistics wlan wlan_id {application application_name | top-app-groups [upstream
| downstream] | top-apps [upstream | downstream]}—Displays the AVC statistics of a WLAN
per application or top applications or top application groups.
◦show avc statistics client client_MAC {application application_name | top-apps [upstream |
downstream]}—Displays the client AVC statistics per application or top applications.
Note You can view list of 30 applications using the show avc applications and show avc
statistics commands.
• View the protocol pack that is used on the controller by entering this command:
show avc protocol-pack version
• View the AVC engine version information by entering this command:
show avc engine version
• Configure troubleshooting for AVC events by entering this command:
debug avc events {enable | disable}
• Configure troubleshooting for AVC errors by entering this command:
debug avc error {enable | disable}
Configuring NetFlow
Note Cisco WLC does not support IPv6 address format when acting as an exporter for
NetFlow.
e) Click Apply.
f) Click Save Configuration.
Step 3 Associate a NetFlow Monitor to a WLAN by performing these steps:
a) Choose WLANs and click a WLAN ID to open the WLANs > Edit page.
b) In the QoS tab, choose a NetFlow monitor from the Netflow Monitor drop-down list.
c) Click Apply.
d) Click Save Configuration.
Each of these parameters is supported in Cisco Compatible Extensions (CCX) v4 and v5.
Note Traffic stream metrics (TSM) can be used to monitor and report issues with voice quality.
Note CAC is not supported in Flexconnect local auth, resulting in voice traffic not getting properly tagged.
Bandwidth-Based CAC
Bandwidth-based, or static, CAC enables the client to specify how much bandwidth or shared medium time
is required to accept a new call and in turn enables the access point to determine whether it is capable of
accommodating this particular call. The access point rejects the call if necessary in order to maintain the
maximum allowed number of calls with acceptable quality.
The QoS setting for a WLAN determines the level of bandwidth-based CAC support. To use bandwidth-based
CAC with voice applications, the WLAN must be configured for Platinum QoS. To use bandwidth-based
CAC with video applications, the WLAN must be configured for Gold QoS. Also, make sure that WMM is
enabled for the WLAN. See the Information About Configuring 802.3 Bridging, on page 101 section for QoS
and WMM configuration instructions.
Note You must enable admission control (ACM) for CCXv4 clients that have WMM enabled. Otherwise,
bandwidth-based CAC does not operate properly.
Load-Based CAC
Load-based CAC incorporates a measurement scheme that takes into account the bandwidth consumed by all
traffic types (including that from clients), co-channel access point loads, and collocated channel interference,
for voice applications. Load-based CAC also covers the additional bandwidth consumption resulting from
PHY and channel impairment.
In load-based CAC, the access point continuously measures and updates the utilization of the RF channel
(that is, the percentage of bandwidth that has been exhausted), channel interference, and the additional calls
that the access point can admit. The access point admits a new call only if the channel has enough unused
bandwidth to support that call. By doing so, load-based CAC prevents oversubscription of the channel and
maintains QoS under all conditions of WLAN loading and interference.
Note Load-based CAC is supported only on lightweight access points. If you disable load-based CAC, the
access points start using bandwidth-based CAC.
2
CAC Mode Reserved Usage Normal TSPEC with Expedited
bandwidth TSPEC Bandwidth Request
for voice Request
1
calls
Bandwidth-based 75% Less than 75% Admitted Admitted
CAC (default
setting) Between 75% and 90% Rejected Admitted
(reserved bandwidth for
voice calls exhausted)
1 For bandwidth-based CAC, the voice call bandwidth usage is per access point and does not take into account co-channel access points. For load-based CAC,
the voice call bandwidth usage is measured for the entire channel.
2 Bandwidth-based CAC (consumed voice and video bandwidth) or load-based CAC (channel utilization [Pb]).
Note When video ACM is enabled, the controller rejects a video TSPEC if the non-MSDU size in the TSPEC
is greater than 149 or the mean data rate is greater than 1 Kbps.
U-APSD
Unscheduled automatic power save delivery (U-APSD) is a QoS facility defined in IEEE 802.11e that extends
the battery life of mobile clients. In addition to extending battery life, this feature reduces the latency of traffic
flow delivered over the wireless media. Because U-APSD does not require the client to poll each individual
packet buffered at the access point, it allows delivery of multiple downlink packets by sending a single uplink
trigger packet. U-APSD is enabled automatically when WMM is enabled.
The metrics consist of a collection of uplink (client side) and downlink (access point side) statistics between
an access point and a client device that supports CCX v4 or later releases. If the client is not CCX v4 or CCXv5
compliant, only downlink statistics are captured. The client and access point measure these metrics. The access
point also collects the measurements every 5 seconds, prepares 90-second reports, and then sends the reports
to the controller. The controller organizes the uplink measurements on a client basis and the downlink
measurements on an access point basis and maintains an hour’s worth of historical data. To store this data,
the controller requires 32 MB of additional memory for uplink metrics and 4.8 MB for downlink metrics.
TSM can be configured through either the GUI or the CLI on a per radio-band basis (for example, all 802.11a
radios). The controller saves the configuration in flash memory so that it persists across reboots. After an
access point receives the configuration from the controller, it enables TSM on the specified radio band.
Note Access points support TSM entries in both local and FlexConnect modes.
This table shows the upper limit for TSM entries in different controller series.
Note Once the upper limit is reached, additional TSM entries cannot be stored and sent to Cisco Prime
Infrastructure. If client TSM entries are full and AP TSM entries are available, then only the AP entries
are stored, and vice versa. This leads to partial output. TSM cleanup occurs every one hour. Entries are
removed only for those APs and clients that are not in the system.
Step 1 Ensure that the WLAN is configured for WMM and the Platinum QoS level.
Step 2 Disable all WLANs with WMM enabled and click Apply.
Step 3 Choose Wireless and then Network under 802.11a/n/ac or 802.11b/g/n, unselect the 802.11a (or 802.11b/g) Network
Status check box, and click Apply to disable the radio network.
Step 4 Choose Wireless > 802.11a/n/ac or 802.11b/g/n > Media. The 802.11a (or 802.11b) > Media page appears. The Voice
tab is displayed by default.
Step 5 Select the Admission Control (ACM) check box to enable bandwidth-based CAC for this radio band. The default value
is disabled.
Step 6 Select the Admission Control (ACM) you want to use by choosing from the following choices:
Step 7 In the Max RF Bandwidth text box, enter the percentage of the maximum bandwidth allocated to clients for voice
applications on this radio band. Once the client reaches the value specified, the access point rejects new calls on this
radio band.
The range is 5% to 85%. The sum of maximum bandwidth percentage of voice and video should not exceed 85%.
The default is 75%.
Step 8 In the Reserved Roaming Bandwidth text box, enter the percentage of maximum allocated bandwidth that is reserved
for roaming voice clients. The controller reserves this bandwidth from the maximum allocated bandwidth for roaming
voice clients.
The range is 0% to 25%.
The default is 6%.
Step 9 To enable expedited bandwidth requests, select the Expedited Bandwidth check box. By default, this text box is disabled.
Step 10 To enable SIP CAC support, select the SIP CAC Support check box. By default, SIP CAC support is disabled.
Step 11 From the SIP Codec drop-down list, choose one of the following options to set the codec name. The default value is
G.711. The options are as follows:
• User Defined
• G.711
• G.729
Step 12 In the SIP Bandwidth (kbps) text box, enter the bandwidth in kilobits per second.
The possible range is 8 to 64.
The default value is 64.
Note The SIP Bandwidth (kbps) text box is highlighted only when you select the SIP codec as User-Defined. If you
choose the SIP codec as G.711, the SIP Bandwidth (kbps) text box is set to 64. If you choose the SIP codec
as G.729, the SIP Bandwidth (kbps) text box is set to 8.
Step 13 In the SIP Voice Sample Interval (msecs) text box, enter the value for the sample interval.
Step 14 In the Maximum Calls text box, enter the maximum number of calls that can be made to this radio. The maximum call
limit includes both direct and roaming-in calls. If the maximum call limit is reached, the new or roaming-in calls result
in failure.
The possible range is 0 to 25.
The default value is 0, which indicates that there is no check for maximum call limit.
Note If SIP CAC is supported and the CAC method is static, the Maximum Possible Voice Calls and Maximum
Possible Roaming Reserved Calls fields appear.
Step 15 Select the Metrics Collection check box to collect traffic stream metrics. By default, this box is unselected. That is, the
traffic stream metrics is not collected by default.
Step 16 Click Apply.
Step 17 Reenable all WMM WLANs and click Apply.
Step 18 Choose Network under 802.11a/n/ac or 802.11b/g/n, select the 802.11a (or 802.11b/g) Network Status check box, and
click Apply to reenable the radio network.
Step 19 Click Save Configuration.
Step 20 Repeat this procedure if you want to configure voice parameters for another radio band.
Step 1 See all of the WLANs configured on the controller by entering this command:
show wlan summary
Step 2 Make sure that the WLAN that you are planning to modify is configured for WMM and the QoS level is set to Platinum
by entering this command:
show wlan wlan_id
Step 3 Disable all WLANs with WMM enabled prior to changing the voice parameters by entering the command:
config wlan disable wlan_id
Step 6 Enable or disable bandwidth-based voice CAC for the 802.11a or 802.11b/g network by entering this command:
config {802.11a | 802.11b} cac voice acm {enable | disable}
Step 7 Set the percentage of maximum bandwidth allocated to clients for voice applications on the 802.11a or 802.11b/g network
by entering this command:
config {802.11a | 802.11b} cac voice max-bandwidth bandwidth
The bandwidth range is 5 to 85%, and the default value is 75%. Once the client reaches the value specified, the access
point rejects new calls on this network.
Step 8 Set the percentage of maximum allocated bandwidth reserved for roaming voice clients by entering this command:
config {802.11a | 802.11b} cac voice roam-bandwidth bandwidth
The bandwidth range is 0 to 25%, and the default value is 6%. The controller reserves this much bandwidth from the
maximum allocated bandwidth for roaming voice clients.
Step 9 Configure the codec name and sample interval as parameters and to calculate the required bandwidth per call by entering
this command:
config {802.11a | 802.11b} cac voice sip codec {g711 | g729} sample-interval number_msecs
Step 10 Configure the bandwidth that is required per call by entering this command:
config {802.11a | 802.11b} cac voice sip bandwidth bandwidth_kbps sample-interval number_msecs
Step 11 Reenable all WLANs with WMM enabled by entering this command:
config wlan enable wlan_id
Step 1 Ensure that the WLAN is configured for WMM and the Gold QoS level.
Step 2 Disable all WLANs with WMM enabled and click Apply.
Step 3 Choose Wireless and then Network under 802.11a/n/ac or 802.11b/g/n, unselect the 802.11a (or 802.11b/g) Network
Status check box, and click Apply to disable the radio network.
Step 4 Choose Wireless > 802.11a/n/ac or 802.11b/g/n > Media. The 802.11a (or 802.11b) > Media page appears.
Step 5 In the Video tab, select the Admission Control (ACM) check box to enable video CAC for this radio band. The default
value is disabled.
Step 6 From the CAC Method drop-down list, choose between Static and Load Based methods.
The static CAC method is based on the radio and the load-based CAC method is based on the channel.
Note For TSpec and SIP based CAC for video calls, only Static method is supported.
Step 7 In the Max RF Bandwidth text box, enter the percentage of the maximum bandwidth allocated to clients for video
applications on this radio band. When the client reaches the value specified, the access point rejects new requests on this
radio band.
The range is 5% to 85%. The sum of maximum bandwidth percentage of voice and video should not exceed 85%. The
default is 0%.
Step 8 In the Reserved Roaming Bandwidth text box, enter the percentage of the maximum RF bandwidth that is reserved for
roaming clients for video.
Step 9 Configure the SIP CAC Support by selecting or unselecting the SIP CAC Support check box.
SIP CAC is supported only if SIP Snooping is enabled.
Note You cannot enable SIP CAC if you have selected the Load Based CAC method.
Step 1 See all of the WLANs configured on the controller by entering this command:
show wlan summary
Step 2 Make sure that the WLAN that you are planning to modify is configured for WMM and the QoS level is set to Gold by
entering this command:
show wlan wlan_id
Step 3 Disable all WLANs with WMM enabled prior to changing the video parameters by entering this command:
config wlan disable wlan_id
Step 6 Enable or disable video CAC for the 802.11a or 802.11b/g network by entering this command:
config {802.11a | 802.11b} cac video acm {enable | disable}
Step 7 To configure the CAC method as either static or load-based, enter this command:
config {802.11a | 802.11b} cac video cac-method {static | load-based}
Step 8 Set the percentage of maximum bandwidth allocated to clients for video applications on the 802.11a or 802.11b/g network
by entering this command:
config {802.11a | 802.11b} cac video max-bandwidth bandwidth
The bandwidth range is 5 to 85%, and the default value is 5%. However, the maximum RF bandwidth cannot exceed
85% for voice and video. Once the client reaches the value specified, the access point rejects new calls on this network.
Note If this parameter is set to zero (0), the controller assumes that you do not want to do any bandwidth allocation
and, therefore, allows all bandwidth requests.
Step 9 To configure the percentage of the maximum RF bandwidth that is reserved for roaming clients for video, enter this
command:
config {802.11a | 802.11b} cac video roam-bandwidth bandwidth
Step 10 To configure the CAC parameters for SIP-based video calls, enter this command:
config {802.11a | 802.11b} cac video sip {enable | disable}
Step 11 Process or ignore the TSPEC inactivity timeout received from an access point by entering this command:
config {802.11a | 802.11b} cac video tspec-inactivity-timeout {enable | ignore}
Step 12 Reenable all WLANs with WMM enabled by entering this command:
config wlan enable wlan_id
Step 5 See the TSM statistics for a particular access point and a particular client associated to this access point, as follows:
a) Choose Wireless > Access Points > Radios > 802.11a/n/ac or 802.11b/g/n. The 802.11a/n/ac Radios or 802.11b/g/n
Radios page appears.
b) Hover your cursor over the blue drop-down arrow for the desired access point and choose 802.11aTSM or 802.11b/g
TSM. The AP > Clients page appears.
c) Click the Detail link for the desired client to open the AP > Clients > Traffic Stream Metrics page.
This page shows the TSM statistics for this access point and a client associated to it. The statistics are shown in
90-second intervals. The timestamp text box shows the specific interval when the statistics were collected.
Step 1 See the CAC configuration for the 802.11 network by entering this command:
show ap stats {802.11a | 802.11b}
Step 2 See the CAC statistics for a particular access point by entering this command:
show ap stats {802.11a | 802.11b} ap_name
Information similar to the following appears:
In the example above, “MT” is medium time, “Na” is the number of additional calls, and “exp bw” is expedited bandwidth.
Note Suppose an AP has to be rebooted when a voice client associated with the AP is on an active call. After the AP
is rebooted, the client continues to maintain the call, and during the time the AP is down, the database is not
refreshed by the controller. Therefore, we recommend that all active calls are ended before the AP is taken
down.
Step 3 See the U-APSD status for a particular client by entering this command:
show client detail client_mac
Step 4 See the TSM statistics for a particular client and the access point to which this client is associated by entering this
command:
show client tsm {802.11a | 802.11b} client_mac {ap_mac | all}
The optional all command shows all access points to which this client has associated. Information similar to the following
appears:
Note The statistics are shown in 90-second intervals. The timestamp text box shows the specific interval when the
statistics were collected.
Note Clear the TSM statistics for a particular access point or all the access points to which this client is associated
by entering this clear client tsm {802.11a | 802.11b} client_mac {ap_mac | all} command.
Step 5 See the TSM statistics for a particular access point and a particular client associated to this access point by entering this
command:
show ap stats {802.11a | 802.11b} ap_name tsm {client_mac | all}
The optional all command shows all clients associated to this access point. Information similar to the following appears:
================
Average Delay (5sec intervals)............................35
Delay less than 10 ms.....................................20
Delay bet 10 - 20 ms......................................20
Delay bet 20 - 40 ms......................................20
Delay greater than 40 ms..................................20
Total packet Count.........................................80
Total packet lost count (5sec).............................10
Maximum Lost Packet count(5sec)............................5
Average Lost Packet count(5secs)...........................2
Note The statistics are shown in 90-second intervals. The timestamp text box shows the specific interval when the
statistics were collected.
Step 6 Enable or disable debugging for call admission control (CAC) messages, events, or packets by entering this command:
debug cac {all | event | packet}{enable | disable}
where all configures debugging for all CAC messages, event configures debugging for all CAC events, and packet
configures debugging for all CAC packets.
Step 7 Use the following command to perform voice diagnostics and to view the debug messages between a maximum of two
802.11 clients:
debug voice-diag {enable | disable} mac-id mac-id2 [verbose]
The verbose mode is an optional argument. When the verbose option is used, all debug messages are displayed in the
console. You can use this command to monitor a maximum of two 802.11 clients. If one of the clients is a non-WiFi
client, only the 802.11 client is monitored for debug messages.
Note It is implicitly assumed that the clients being monitored are on
call.
Note The debug command automatically stops after 60
minutes.
Step 8 Use the following commands to view various voice-related parameters:
• show client voice-diag status
Displays information about whether voice diagnostics is enabled or disabled. If enabled, will also displays information
about the clients in the watch list and the time remaining for the diagnostics of the voice call.
If voice diagnostics is disabled when the following commands are entered, a message indicating that voice diagnostics
is disabled appears.
• show client voice-diag tspec
Displays the TSPEC information sent from the clients that are enabled for voice diagnostics.
• show client voice-diag qos-map
Displays information about the QoS/DSCP mapping and packet statistics in each of the four queues: VO, VI, BE,
BK. The different DSCP values are also displayed.
• show client voice-diag avrg_rssi
Display the client’s RSSI values in the last 5 seconds when voice diagnostics is enabled.
• show client voice-diag roam-history
Displays information about the last three roaming calls. The output contains the timestamp, access point associated
with roaming, roaming reason, and if there is a roaming failure, the reason for the roaming-failure.
Step 9 Use the following commands to troubleshoot video debug messages and statistics:
• debug ap show stats {802.11b | 802.11a} ap-name multicast—Displays the access point’s supported multicast
rates.
• debug ap show stats {802.11b | 802.11a} ap-name load—Displays the access point’s QBSS and other statistics.
• debug ap show stats {802.11b | 802.11a} ap-name tx-queue—Displays the access point’s transmit queue traffic
statistics.
• debug ap show stats {802.11b | 802.11a} ap-name client {all | video | client-mac}—Displays the access point’s
client metrics.
• debug ap show stats {802.11b | 802.11a} ap-name packet—Displays the access point’s packet statistics.
• debug ap show stats {802.11b | 802.11a} ap-name video metrics—Displays the access point’s video metrics.
• debug ap show stats video ap-name multicast mgid number —Displays an access point’s Layer 2 MGID database
number.
• debug ap show stats video ap-name admission—Displays an access point’s admission control statistics.
• debug ap show stats video ap-name bandwidth—Displays an access point’s video bandwidth.
• Ensure that you have enabled the Admission Control (ACM) for this radio.
Step 1 Choose Wireless > Advanced > SIP Snooping to open the SIP Snooping page.
Step 2 Specify the call-snooping ports by entering the starting port and the ending port.
Step 3 Click Apply and then click Save Configuration.
Step 1 Set the voice to the platinum QoS level by entering this command:
config wlan qos wlan-id Platinum
Step 2 Enable the call-snooping feature for a particular WLAN by entering this command:
config wlan call-snoop enable wlan-id
Step 1 Ensure that the WLAN is configured for WMM and the Gold QoS level.
Step 2 Disable all WLANs with WMM enabled and click Apply.
Step 3 Choose Wireless and then Network under 802.11a/n/ac or 802.11b/g/n, unselect the 802.11a (or 802.11b/g) Network
Status check box, and click Apply to disable the radio network.
Step 4 Choose Wireless > 802.11a/n/ac or 802.11b/g/n > Media. The 802.11a (or 802.11b) > Media > Parameters page appears.
Step 5 Choose the Media tab to open the Media page.
Step 6 Select the Unicast Video Redirect check box to enable Unicast Video Redirect. The default value is disabled.
Step 7 In the Maximum Media Bandwidth (0-85%) text box, enter the percentage of the maximum bandwidth to be allocated
for media applications on this radio band. Once the client reaches the specified value, the access point rejects new calls
on this radio band.
The default value is 85%; valid values are from 0 to 85%.
Step 8 In the Client Phy Rate text box, enter the value for the rate in kilobits per second at which the client operates.
Step 9 In the Maximum Retry Percent (0-100%) text box, enter the percentage of the maximum retry. The default value is
80.
Step 10 Select the Multicast Direct Enable check box to enable the Multicast Direct Enable text box. The default value is
enabled.
Step 11 From the Max Streams per Radio drop-down list, choose the maximum number of allowed multicast direct streams
per radio. Choose a value between 1 to 20 or No Limit. The default value is set to No Limit.
Step 12 From the Max Streams per Client drop-down list, choose the maximum number of allowed clients per radio. Choose
a value between 1 to 20 or No Limit. The default value is set to No Limit.
Step 13 If you want to enable the best radio queue for this radio, select the Best Effort QoS Admission check box. The default
value is disabled.
Step 1 Set the voice to the platinum QoS level by entering this command:
config wlan qos wlan-id Platinum
Step 3 Enable the call-snooping feature for a particular WLAN by entering this command:
config wlan call-snoop enable wlan-id
Step 6 View the preferred call statistics by entering the following command:
show ap stats {802.11{a | b} | wlan} ap_name
Step 7 Enter the following command to list the preferred call numbers:
show advanced sip-preferred-call-no
Step 1 Choose Wireless and then Network under 802.11a/n/ac or 802.11b/g/n, unselect the 802.11a (or 802.11b/g) Network
Status check box, and click Apply to disable the radio network.
Step 2 Click EDCA Parametersunder 802.11a/n/ac or 802.11b/g/n.
Step 3 The 802.11a (or 802.11b/g) > EDCA Parameters window is displayed.
Step 4 Choose one of the following options from the EDCA Profile drop-down list:
• WMM—Enables the Wi-Fi Multimedia (WMM) default parameters. This is the default value. Choose this option
when voice or video services are not deployed on your network.
• Spectralink Voice Priority—Enables SpectraLink voice-priority parameters. Choose this option if SpectraLink
phones are deployed on your network to improve the quality of calls.
• Voice Optimized—Enables Enhanced Distributed Channel Access (EDCA) voice-optimized profile parameters.
Choose this option when voice services other than SpectraLink are deployed on your network.
• Voice & Video Optimized—Enables EDCA voice-optimized and video-optimized profile parameters. Choose
this option when both voice and video services are deployed on your network.
• Custom Voice—Enables custom voice EDCA parameters for 802.11a. The EDCA parameters under this option
also match the 6.0 WMM EDCA parameters when this profile is applied.
Note If you deploy video services, admission control must be
disabled.
Step 5 To enable MAC optimization for voice, check the Enable Low Latency MAC check box. By default, this check box is
not checked. This feature enhances voice performance by controlling packet retransmits and appropriately aging out
voice packets on lightweight access points, which improves the number of voice calls serviced per access point.
Note We recommend against you enabling low latency MAC. You should enable low-latency MAC only if the WLAN
allows WMM clients. If WMM is enabled, then low-latency MAC can be used with any of the EDCA profiles.
Step 4 View the current status of MAC optimization for voice by entering this command:
show {802.11a | 802.11b}
Information that is similar to the following example is displayed:
Voice-mac-optimization...................Disabled
Step 5 Enable or disable MAC optimization for voice by entering this command:
config advanced {802.11a | 802.11b} voice-mac-optimization {enable | disable}
Note This feature enhances voice performance by controlling packet retransmits and appropriately aging out voice
packets on lightweight APs. This, in tun improves the number of voice calls serviced per AP. The default value
is disabled.
Note Cisco recommends that you disable Cisco Discovery Protocol on the controller and access point when
connected to non-Cisco switches as CDP is unsupported on non-Cisco switches and network elements.
Note To use the Intelligent Power Management feature, ensure that CDPv2 is enabled on the
Cisco 2504 Wireless Controller. CDP v2 is enabled by default.
• The Cisco 600 Series OEAP access points do not support CDP.
• The support of CDPv1 and CDPv2 enables network management applications to discover Cisco devices.
• The following TLVs are supported by both the controller and the access point:
◦Device-ID TLV: 0x0001—The hostname of the controller, the access point, or the CDP neighbor.
◦Address TLV: 0x0002—The IP address of the controller, the access point, or the CDP neighbor.
◦Port-ID TLV: 0x0003—The name of the interface on which CDP packets are sent out.
◦Capabilities TLV: 0x0004—The capabilities of the device. The controller sends out this TLV with
a value of Host: 0x10, and the access point sends out this TLV with a value of Transparent Bridge:
0x02.
◦Version TLV: 0x0005—The software version of the controller, the access point, or the CDP
neighbor.
◦Platform TLV: 0x0006—The hardware platform of the controller, the access point, or the CDP
neighbor.
◦Power Available TLV: 0x001a— The amount of power available to be transmitted by power
sourcing equipment to permit a device to negotiate and select an appropriate power setting.
◦Full/Half Duplex TLV: 0x000b—The full- or half-duplex mode of the Ethernet link on which CDP
packets are sent out.
• Changing the CDP configuration on the controller does not change the CDP configuration on the access
points that are connected to the controller. You must enable and disable CDP separately for each access
point.
• You can enable or disable the CDP state on all or specific interfaces and radios. This configuration can
be applied to all access points or a specific access point.
• The following is the behavior assumed for various interfaces and access points:
◦CDP is disabled on radio interfaces on indoor (nonindoor mesh) access points.
◦Nonmesh access points have CDPs disabled on radio interfaces when they join the controller. The
persistent CDP configuration is used for the APs that had CDP support in its previous image.
◦CDP is enabled on radio interfaces on indoor-mesh and mesh access points.
◦Mesh access points will have CDP enabled on their radio interfaces when they join the controller.
The persistent CDP configuration is used for the access points that had CDP support in a previous
image. The CDP configuration for radio interfaces is applicable only for mesh APs.
Step 1 Choose Controller > CDP > Global Configuration to open the CDP > Global Configuration page.
Step 2 Select the CDP Protocol Status check box to enable CDP on the controller or unselect it to disable this feature. The
default value is selected.
Note Enabling or disabling this feature is applicable to all controller
ports.
Step 3 From the CDP Advertisement Version drop-down list, choose v1 or v2 to specify the highest CDP version supported on
the controller. The default value is v1.
Step 4 In the Refresh-time Interval text box, enter the interval at which CDP messages are to be generated. The range is 5 to
254 seconds, and the default value is 60 seconds.
Step 5 In the Holdtime text box, enter the amount of time to be advertised as the time-to-live value in generated CDP packets.
The range is 10 to 255 seconds, and the default value is 180 seconds.
Step 6 Click Apply to commit your changes.
Step 7 Click Save Configuration to save your changes.
Step 8 Perform one of the following:
• To enable or disable CDP on a specific access point, follow these steps:
Choose Wireless > Access Points > All APs to open the All APs page.
Click the link for the desired access point.
Choose the Advanced tab to open the All APs > Details for (Advanced) page.
Select the Cisco Discovery Protocol check box to enable CDP on this access point or unselect it to disable this
feature. The default value is enabled.
Note If CDP is disabled in Step 2, a message indicating that the Controller CDP is disabled appears.
Step 2 Specify the interval at which CDP messages are to be generated by entering this command:
config cdp timer seconds
The range is 5 to 254 seconds, and the default value is 60 seconds.
Step 3 Specify the amount of time to be advertised as the time-to-live value in generated CDP packets by entering this command:
config cdp holdtime seconds
The range is 10 to 255 seconds, and the default value is 180 seconds.
Step 4 Specify the highest CDP version supported on the controller by entering this command:
config cdp advertise {v1 | v2}
The default value is v1.
Step 5 Enable or disable CDP on all access points that are joined to the controller by entering the config ap cdp {enable |
disable} all command.
The config ap cdp disable all command disables CDP on all access points that are joined to the controller and all access
points that join in the future. CDP remains disabled on both current and future access points even after the controller or
access point reboots. To enable CDP, enter the config ap cdp enable all command.
Note After you enable CDP on all access points joined to the controller, you may disable and then reenable CDP on
individual access points using the command in Step 6. After you disable CDP on all access points joined to the
controller, you may not enable and then disable CDP on individual access points.
Step 6 Enable or disable CDP on a specific access point by entering this command:
config ap cdp {enable | disable} Cisco_AP
Step 7 Configure CDP on a specific or all access points for a specific interface by entering this command:
config ap cdp {ethernet | radio} interface_number slot_id {enable | disable} {all | Cisco_AP}
Note When you use the config ap cdp command to configure CDP on radio interfaces, a warning message appears
indicating that the configuration is applicable only for mesh access points.
Step 8 Save your changes by entering this command:
save config
Step 1 Choose Monitor > CDP > Interface Neighbors to open the CDP > Interface Neighbors page appears.
This page shows the following information:
• The controller port on which the CDP packets were received
• The name of each CDP neighbor
• The IP address of each CDP neighbor
• The port used by each CDP neighbor for transmitting CDP packets
• The time left (in seconds) before each CDP neighbor entry expires
• The functional capability of each CDP neighbor, defined as follows: R - Router, T - Trans Bridge, B - Source Route
Bridge, S - Switch, H - Host, I - IGMP, r - Repeater, or M - Remotely Managed Device
• The hardware platform of each CDP neighbor device
Step 2 Click the name of the desired interface neighbor to see more detailed information about each interface’s CDP neighbor.
The CDP > Interface Neighbors > Detail page appears.
This page shows the following information:
• The controller port on which the CDP packets were received
• The name of the CDP neighbor
• The IP address of the CDP neighbor
• The port used by the CDP neighbor for transmitting CDP packets
• The CDP version being advertised (v1 or v2)
• The time left (in seconds) before the CDP neighbor entry expires
• The functional capability of the CDP neighbor, defined as follows: Router, Trans Bridge,?Source Route Bridge,
Switch, Host, IGMP, Repeater, or Remotely Managed Device
• The hardware platform of the CDP neighbor device
Step 3 Choose AP Neighbors to see a list of CDP neighbors for all access points connected to the controller. The CDP AP
Neighbors page appears.
Step 4 Click the CDP Neighbors link for the desired access point to see a list of CDP neighbors for a specific access point.
The CDP > AP Neighbors page appears.
This page shows the following information:
• The name of each access point
• The IP address of each access point
• The name of each CDP neighbor
• The IP address of each CDP neighbor
• The port used by each CDP neighbor
• The CDP version being advertised (v1 or v2)
Step 5 Click the name of the desired access point to see detailed information about an access point’s CDP neighbors. The CDP
> AP Neighbors > Detail page appears.
This page shows the following information:
• The name of the access point
• The MAC address of the access point’s radio
• The IP address of the access point
• The interface on which the CDP packets were received
• The name of the CDP neighbor
• The IP address of the CDP neighbor
• The port used by the CDP neighbor
• The CDP version being advertised (v1 or v2)
• The time left (in seconds) before the CDP neighbor entry expires
• The functional capability of the CDP neighbor, defined as follows: R - Router, T - Trans Bridge,?B - Source Route
Bridge, S - Switch, H - Host, I - IGMP, r - Repeater, or M - Remotely Managed Device
• The hardware platform of the CDP neighbor device
• The software running on the CDP neighbor
Step 6 Choose Traffic Metrics to see CDP traffic information. The CDP > Traffic Metrics page appears.
This page shows the following information:
• The number of CDP packets received by the controller
• The number of CDP packets sent from the controller
• The number of packets that experienced a checksum error
• The number of packets dropped due to insufficient memory
Step 1 See the status of CDP and to view CDP protocol information by entering this command:
show cdp
Step 2 See a list of all CDP neighbors on all interfaces by entering this command:
show cdp neighbors [detail]
The optional detail command provides detailed information for the controller’s CDP neighbors.
Note This command shows only the CDP neighbors of the controller. It does not show the CDP neighbors of the
controller’s associated access points. Additional commands are provided below to show the list of CDP neighbors
per access point.
Step 3 See all CDP entries in the database by entering this command:
show cdp entry all
Step 4 See CDP traffic information on a given port (for example, packets sent and received, CRC errors, and so on) by entering
this command:
show cdp traffic
Step 5 See the CDP status for a specific access point by entering this command:
show ap cdp ap-name Cisco_AP
Step 6 See the CDP status for all access points that are connected to the controller by entering this command:
show ap cdp all
Step 7 See a list of all CDP neighbors for a specific access point by entering these commands:
• show ap cdp neighbors ap-name Cisco_AP
• show ap cdp neighbors detail Cisco_AP
Note The access point sends CDP neighbor information to the controller only when the information changes.
Step 8 See a list of all CDP neighbors for all access points connected to the controller by entering these commands:
• show ap cdp neighbors all
• show ap cdp neighbors detail all
Note The access point sends CDP neighbor information to the controller only when the information changes.
Step 1 Choose Controller > NTP > Server to open the NTP Severs page.
Step 2 Click New to add a new NTP/SNTP Server.
Step 3 In the Server Index (Priority) text box, enter the NTP/SNTP server index.
The controller tries Index 1 first, then Index 2 through 3, in a descending order. Set this to 1 if your network is using
only one NTP/SNTP server.
Telemetry
Temperature X X — X
Pressure — — — —
Humidity — — — —
Status — — — —
Fuel — — — —
Distance — — — —
Motion Detection X X — X
Tampering X X X
Battery Information X X X X
Multiple-Frequency Tags3 X X X
3 For chokepoint systems, note that the tag can work only with chokepoints coming from the same vendor.
Note The Network Mobility Services Protocol (NMSP) runs on the mobility services engine. For NMSP to
function, the TCP port (16113) over which the controller and the mobility services engine communicate
must be open (not blocked) on any firewall that exists between these two devices.
You can configure and view RFID tag tracking information through the controller CLI.
Step 2 Specify a static timeout value (between 60 and 7200 seconds) by entering this command:
config rfid timeout seconds
The static timeout value is the amount of time that the controller maintains tags before expiring them. For example, if a
tag is configured to beacon every 30 seconds, we recommend that you set the timeout value to 90 seconds (approximately
three times the beacon value). The default value is 1200 seconds.
Step 3 Enable or disable RFID tag mobility for specific tags by entering these commands:
• config rfid mobility vendor_name enable—Enables client mobility for a specific vendor’s tags. When you enter
this command, tags are unable to obtain a DHCP address for client mode when attempting to select and/or download
a configuration.
• config rfid mobility vendor_name disable—Disables client mobility for a specific vendor’s tags. When you enter
this command, tags can obtain a DHCP address. If a tag roams from one subnet to another, it obtains a new address
rather than retaining the anchor state.
Note These commands can be used only for Pango tags. Therefore, the only valid entry for vendor_name is
“pango” in all lowercase letters.
Step 1 See the current configuration for RFID tag tracking by entering this command:
show rfid config
Step 2 See detailed information for a specific RFID tag by entering this command:
show rfid detail mac_address
where mac_address is the tag’s MAC address.
Step 3 See a list of all RFID tags currently connected to the controller by entering this command:
show rfid summary
Step 4 See a list of RFID tags that are associated to the controller as clients by entering this command:
show rfid client
Note We recommend that you perform the debugging on a per-tag basis. If you enable
debugging for all of the tags, the console or Telnet screen is inundated with messages.
• Enable or disable debugging for the 802.11 RFID tag module by entering this command:
debug dot11 rfid {enable | disable}
• Enable or disable RFID debug options by entering this command:
debug rfid {all | detail | error | nmsp | receive} {enable | disable}
where
◦all configures debugging of all RFID messages.
◦detail configures debugging of RFID detailed messages.
◦error configures debugging of RFID error messages.
◦nmsp configures debugging of RFID NMSP messages.
◦receive configures debugging of incoming RFID tag messages.
Step 1 Enter the reset system command. At the prompt that asks whether you need to save changes to the configuration, enter
N. The unit reboots.
Step 2 When you are prompted for a username, enter the recover-config command to restore the factory-default configuration.
The controller reboots and displays this message:
Step 3 Use the configuration wizard to enter configuration settings. See the Configuring the Controller—Using the CLI
Configuration Wizard section for more information.
Caution Do not power down the controller or any access point during this process; otherwise, you might corrupt
the software image. Upgrading a controller with a large number of access points can take as long as 30
minutes, depending on the size of your network. However, with the increased number of concurrent access
point upgrades supported in the controller software release, the upgrade time should be significantly
reduced. The access points must remain powered, and the controller must not be reset during this time.
• You can upgrade or downgrade the controller software only between certain releases. In some instances,
you must first install an intermediate release prior to upgrading to the latest software release.
• When you upgrade the controller to an intermediate software release, you must wait until all of the access
points that are associated with the controller are upgraded to the intermediate release before you install
the latest controller software. In large networks, it can take some time to download the software on each
access point.
• When you upgrade to the latest software release, the software on the access points associated with the
controller is also automatically upgraded. When an access point is loading software, each of its LEDs
blinks in succession.
• We recommend that you access the Cisco WLC GUI using Microsoft Internet Explorer 10 or a later
version, or Mozilla Firefox 32 or a later version.
• Cisco controllers support standard SNMP Management Information Base (MIB) files. MIBs can be
downloaded from the Software Center on Cisco.com.
• The controller software is factory installed on your controller and automatically downloaded to the
access points after a release upgrade and whenever an access point joins a controller. We recommend
that you install the latest software version available for maximum operational benefit.
• We recommend that you install Wireless LAN Controller Field Upgrade Software for Release 1.7.0.0-FUS,
which is a special AES package that contains several system-related component upgrades. These include
the bootloader, field recovery image, and FPGA/MCU firmware. Installing the FUS image requires
special attention because it installs some critical firmware. The FUS image is independent of the runtime
image. For more information, see
http://www.cisco.com/c/en/us/td/docs/wireless/controller/release/notes/fus_rn_1_7_0_0.html.
• Ensure that you have a TFTP or FTP server available for the software upgrade. Follow these guidelines
when setting up a TFTP or FTP server:
◦Ensure that your TFTP server supports files that are larger than the size of the controller software
release. Some TFTP servers that support files of this size are tftpd32 and the TFTP server within
the Cisco Prime Infrastructure. If you attempt to download the controller software and your TFTP
server does not support files of this size, the following error message appears: “TFTP failure while
storing in flash.”
◦If you are upgrading through the distribution system network port, the TFTP or FTP server can be
on the same or a different subnet because the distribution system port is routable
• When you plug a controller into an AC power source, the bootup script and power-on self-test run to
initialize the system. During this time, you can press Esc to display the bootloader Boot Options Menu.
The menu options for the 5500 and Flex 7500 series controllers are different than for other controller
platforms.
Bootloader menu for 5500 Series Controllers:
Boot Options
Please choose an option from below:
1. Run primary image
2. Run backup image
3. Change active boot image
4. Clear Configuration
5. Format FLASH Drive
6. Manually update images
Please enter your choice:
Enter 1 to run the current software, enter 2 to run the previous software, enter 4 (on a 5500 series
controller), or enter 5 (on another controller platform) to run the current software and set the controller
configuration to factory defaults. Do not choose the other options unless directed to do so.
Note See the Installation Guide or the Quick Start Guide for your controller for more details
on running the bootup script and power-on self-test.
• Control which address(es) are sent in CAPWAP discovery responses when NAT is enabled on the
Management Interface using the following command:
config network ap-discovery nat-ip-only {enable | disable}
where
• enable—Enables use of NAT IP only in Discovery response. This is the default. Use this command
if all APs are outside of the NAT gateway.
• disable—Enables use of both NAT IP and non-NAT IP in discovery response. Use this command
if APs are on the inside and outside of the NAT gateway; for example, Local Mode and OfficeExtend
APs on the same controller.
Note To avoid stranding APs, you must disable AP link-latency (if enabled) before you use
the disable option for the config network ap-discovery nat-ip-only command. To
disable AP link-latency, use the config ap link-latency disable all command.
• You can configure 802.1p tagging by using the config qos dot1p-tag {bronze | silver | gold | platinum}
tag. For the 7.2.103.0 and later releases, if you tag 802.1p packets, the tagging has impact only on wired
packets. Wireless packets are impacted only by the maximum priority level set for QoS.
• You can reduce the network downtime using the following options:
• You can predownload the AP image.
• For FlexConnect access points, use the FlexConnect Efficient AP upgrade feature to reduce traffic
between the controller and the AP (main site and the branch).
• Do not power down the controller or any access point during the upgrade process; otherwise, you might
corrupt the software image. Upgrading a controller with a large number of access points can take as long
as 30 minutes, depending on the size of your network. However, with the increased number of concurrent
access point upgrades supported, the upgrade time should be significantly reduced. The access points
must remain powered, and the controller must not be reset during this time.
• If you want to downgrade to a previous release, do either of the following:
• Delete all WLANs that are mapped to interface groups and create new ones.
• Ensure that all WLANs are mapped to interfaces rather than interface groups.
• After you perform these functions on the controller, you must reboot the controller for the changes to
take effect:
• Enable or disable link aggregation (LAG)
• Enable a feature that is dependent on certificates (such as HTTPS and web authentication)
• Add new or modify existing SNMP v3 users
• Modify an existing SNMP v3 engine ID
• Add a new license or modify an existing license
• Increase the priority for a license
• The controller bootloader stores a copy of the active primary image and the backup image. If the primary
image becomes corrupted, you can use the bootloader to boot with the backup image.
With the backup image stored before rebooting, be sure to choose Option 2: Run Backup Image from
the boot menu to boot from the backup image. Then, upgrade with a known working image and reboot
the controller.
• The recovery image provides a backup image that can be used if an access point power-cycles during
an image upgrade. The best way to avoid the need for access point recovery is to prevent an access point
from power-cycling during a system upgrade. If a power-cycle occurs during an upgrade to an oversized
access point image, you can recover the access point using the TFTP recovery procedure.
To recover the access point using the TFTP recovery procedure, follow these steps:
1 Download the required recovery image from Cisco.com (c1100-rcvk9w8-mx, c1200-rcvk9w8-mx,
or c1310-rcvk9w8-mx) and install it in the root directory of your TFTP server.
2 Connect the TFTP server to the same subnet as the target access point and power-cycle the access
point. The access point boots from the TFTP image and then joins the controller to download the
oversized access point image and complete the upgrade procedure.
3 After the access point has been recovered, you can remove the TFTP server.
• You can upgrade to a new release of the controller software or downgrade to an older release even if
Federal Information Processing Standard (FIPS) is enabled.
• If you upgrade from a release that is prior to Release 7.5 directly to Release 7.6.X or a later release, the
predownload process on Cisco AP2600 and AP3600 fails. After the Cisco WLC is upgraded to Release
7.6.X or a later release, the new image is loaded on Cisco AP2600 and AP3600. After the upgrade to a
Release 7.6.X image, the predownload functionality works as expected. The predownload failure is only
a one-time failure.
Step 1 Upload your controller configuration files to a server to back them up.
Note We highly recommend that you back up your configuration files of the controller prior to upgrading the controller
software. Otherwise, you must manually reconfigure the controller.
Step 2 Get the controller software image by following these steps:
a) Browse to http://www.cisco.com/cisco/software/navigator.html.
b) Choose Wireless > Wireless LAN Controller.
The following options are available: Integrated Controllers and Controller Modules, Mobility Express, and
Standalone Controllers.
c) Depending on your controller platform, click one of the above options.
d) Click the controller model number or name. The Download Software page is displayed.
e) Click a controller software release. The software releases are labeled as follows to help you determine which release
to download:
Early Deployment (ED)—These software releases provide new features, new hardware platform support, and bug
fixes.
Maintenance Deployment (MD)—These software releases provide bug fixes and ongoing software maintenance.
Deferred (DF)—These software releases have been deferred. We recommend that you migrate to an upgraded release.
f) Choose a software release number.
g) Click the filename (filename.aes).
h) Click Download.
i) Read Cisco’s End User Software License Agreement and then click Agree.
j) Save the file to your hard drive.
k) Repeat steps a through k to download the remaining file.
Step 3 Copy the controller software image (filename.aes) to the default directory on your TFTP or FTP server.
Note In Release 8.3, for Cisco 2504 WLC, 5508 WLC, and WiSM2, the Cisco WLC software image is split into two
images: Base Install Image and Supplementary AP Bundle Image. Therefore, to upgrade to Release 8.3, you
must repeat Step 2 through Step 14 to complete the installation of both Base Install Image and Supplementary
AP Bundle Image.
Download the Supplementary AP Bundle Image only if you are using any of these APs: AP801, AP802, Cisco
Aironet 1550 Series AP (with 64-MB memory), Cisco Aironet 1550 Series AP (with 128-MB memory), and/or
Cisco Aironet 1570 Series APs.
Step 4 (Optional) Disable the 802.11 networks.
Note For busy networks, controllers on high utilization, or small controller platforms, we recommend that you disable
the 802.11 networks as a precautionary measure.
Step 5 Disable any WLANs on the controller.
Step 6 Choose Commands > Download File to open the Download File to Controller page.
Step 7 From the File Type drop-down list, choose Code.
Step 8 From the Transfer Mode drop-down list, choose from the following options:
• TFTP
• FTP
• SFTP (available in 7.4 and later releases)
• HTTP (available in 8.1 and later releases)
Step 9 In the IP Address text box, enter the IP address of the server.
If you are using a TFTP server, the default values of 10 retries and 6 seconds for the Maximum Retries and Timeout
text boxes should work correctly without any adjustment. However, you can change these values.
Step 10 If you are using a TFTP server, the default values of 10 retries for the Maximum Retries text field, and 6 seconds for the
Timeout text field should work correctly without any adjustment. However, you can change these values if desired. To
do so, enter the maximum number of times that the TFTP server attempts to download the software in the Maximum
Retries text box and the amount of time (in seconds) that the TFTP server attempts to download the software in the
Timeout text box.
Step 11 In the File Path text box, enter the directory path of the software.
Step 12 In the File Name text box, enter the name of the controller software file (filename.aes).
Step 13 If you are using an FTP server, follow these steps:
a) In the Server Login Username text box, enter the username to log into the FTP server.
b) In the Server Login Password text box, enter the password to log into the FTP server.
c) In the Server Port Number text box, enter the port number on the FTP server through which the download occurs.
The default value is 21.
Step 14 Click Download to download the software to the controller. A message appears indicating the status of the download.
Note In Release 8.3, for Cisco 2504 WLC, 5508 WLC, and WiSM2, the Cisco WLC software image is split into two
images: Base Install Image and Supplementary AP Bundle Image. Therefore, to upgrade to Release 8.3.100.0,
you must repeat Step 2 through Step 14 to complete the installation of both Base Install Image and Supplementary
AP Bundle Image.
Download the Supplementary AP Bundle Image only if you are using any of these APs: AP801, AP802, Cisco
Aironet 1550 Series AP (with 64-MB memory), Cisco Aironet 1550 Series AP (with 128-MB memory), and/or
Cisco Aironet 1570 Series APs.
Step 15 After the download is complete, click Reboot.
Step 16 If prompted to save your changes, click Save and Reboot.
Step 17 Click OK to confirm.
Step 18 After the controller reboots, repeat step 6 to step 17 to install the remaining file.
Step 19 Reenable the WLANs.
Step 20 For Cisco WiSM2, reenable the controller port channel on the Catalyst switch.
Step 21 If you have disabled the 802.11 networks in Step 4, reenable them.
Step 22 To verify the controller software version, choose Monitor on the controller GUI and see Software Version in the
Controller Summary area.
Step 1 Upload your controller configuration files to a server to back them up.
Note We highly recommend that you back up your controller's configuration files prior to upgrading the controller
software. Otherwise, you must manually reconfigure the controller.
Step 2 Get the controller software image by following these steps:
a) Browse to http://www.cisco.com/cisco/software/navigator.html.
b) Choose Wireless > Wireless LAN Controller.
The following options are available: Integrated Controllers and Controller Modules, Mobility Express, and
Standalone Controllers.
c) Depending on your controller platform, click one of the above options.
d) Click the controller model number or name. The Download Software page is displayed.
e) Click a controller software release. The software releases are labeled as follows to help you determine which release
to download:
Early Deployment (ED)—These software releases provide new features, new hardware platform support, and bug
fixes.
Maintenance Deployment (MD)—These software releases provide bug fixes and ongoing software maintenance.
Deferred (DF)—These software releases have been deferred. We recommend that you migrate to an upgraded release.
f) Choose a software release number.
g) Click the filename (filename.aes).
h) Click Download.
i) Read Cisco’s End User Software License Agreement and then click Agree.
j) Save the file to your hard drive.
k) Repeat steps a through k to download the remaining file.
Step 3 Copy the controller software image (filename.aes) to the default directory on your TFTP or FTP server.
Note In Release 8.3, for Cisco 2504 WLC, 5508 WLC, and WiSM2, the Cisco WLC software image is split into two
images: Base Install Image and Supplementary AP Bundle Image. Therefore, to upgrade to Release 8.3, you
must repeat Step 2 through Step 10 to complete the installation of both Base Install Image and Supplementary
AP Bundle Image.
Download the Supplementary AP Bundle Image only if you are using any of these APs: AP801, AP802, Cisco
Aironet 1550 Series AP (with 64-MB memory), Cisco Aironet 1550 Series AP (with 128-MB memory), and/or
Cisco Aironet 1570 Series APs.
Step 4 (Optional) Disable the 802.11 networks.
Note For busy networks, controllers on high utilization, or small controller platforms, we recommend that you disable
the 802.11 networks as a precautionary measure.
Step 5 Disable any WLANs on the controller (using the config wlan disable wlan_id command).
Step 6 Log onto the controller CLI.
Step 7 Enter the ping server-ip-address command to verify that the controller can contact the TFTP or FTP server.
Step 8 View current download settings by entering the transfer download start command. Answer n to the prompt to view the
current download settings.
Step 9 Change the download settings, if necessary by entering these commands:
• transfer download mode {tftp | ftp | sftp}
• transfer download datatype code
• transfer download serverip server-ip-address
• transfer download filename filename
• transfer download path server-path-to-file
Note Pathnames on a TFTP or FTP server are relative to the server’s default or root directory. For example, in
the case of the Solaris TFTP server, the path is “/”.
Step 10 View the current updated settings by entering the transfer download start command. Answer y to the prompt to confirm
the current download settings and start the software download.
Step 11 Save the code update to nonvolatile NVRAM and reboot the controller by entering this command:
reset system
The controller completes the bootup process.
Step 12 After the controller reboots, repeat Steps 6 through 11 to install the remaining file.
Step 13 Reenable the WLANs by entering this command:
config wlan enable wlan_id
Step 14 For Cisco WiSMs, re-enable the controller port channel on the Catalyst switch.
Step 15 If you have disabled the 802.11 networks in Step 4, renable them.
Step 16 To verify the controller software that is installed, enter the show sysinfo command and see Product Version.
Step 17 To verify the Cisco Unified Wireless Network Controller Boot Software file that is installed on the controller, enter the
show sysinfo command on the controller CLI and see Recovery Image Version or Emergency Image Version.
Note If a Cisco Unified Wireless Network Controller Boot Software ER.aes file is not installed, Recovery Image
Version or Emergency Image Version show 'N/A.'
2602(I/E) 14 MB
1602(I/E) 12 MB
1262 14 MB
1142 12 MB
Note • The required flash memory can vary based on the radio type and the number of antennas used.
• This predownload feature is not supported on 1242 and 1131 Cisco AP models.
• Cisco AP1142 has 32 MB of total flash memory and can support the predownload feature.
• The actual upgrade of the images occur. The following sequence of actions occur:
◦During boot time, the access point sends a join request.
◦The controller responds with the join response with the image version that the controller is running.
◦The access point compares its running image with the running image on the controller. If the
versions match, the access point joins the controller.
◦If the versions do not match, the access point compares the version of the backup image and if
they match, the access point swaps the primary and backup images and reloads and subsequently
joins the controller.
◦If the primary image of the access point is the same as the controller image, the access point reloads
and joins the controller.
◦If none of the above conditions are true, the access point sends an image data request to the
controller, downloads the latest image, reloads, and joins the controller.
If you reach the predownload limit, then the access points that cannot get an image sleep for a time
between 180 to 600 seconds and then reattempt the predownload.
• Before you predownload, you should change the active controller boot image to the backup image to
ensure that if the controller reboots for some reason, it comes back up with the earlier running image,
not the partially downloaded upgrade image.
• This predownload feature is not supported on 1242 and 1131 Cisco AP models.
• When the system time is changed by using the config time command, the time set for a scheduled reset
is not valid and the scheduled system reset is canceled. You are given an option either to cancel the
scheduled reset before configuring the time or retain the scheduled reset and not configure the time.
• All the primary, secondary, and tertiary controllers should run the same images as the primary and
backup images. That is, the primary image of all three controllers should be X and the secondary image
of all three controllers should be Y or the feature is not effective.
• At the time of the reset, if any AP is downloading the controller image, the scheduled reset is canceled.
The following message appears with the reason why the scheduled reset was canceled:
• Predownloading a 7.2 or later version of image on a Cisco Aironet 1240 access point is not supported
when upgrading from a previous controller release. If predownloading is attempted to the Cisco Aironet
1240 access point, the AP gets disconnected.
• There are two images for the1550 Mesh AP - 1550 with 64 MB memory and 1550 with 128 MB memory.
During the controller upgrade to 7.6 and higher versions, the AP images are downloaded and there are
two reboots.
• If you upgrade from a release that is prior to Release 7.5 directly to Release 7.6.X or a later release, the
predownload process on Cisco AP2600 and AP3600 fails. After the Cisco WLC is upgraded to Release
7.6.X or a later release, the new image is loaded on Cisco AP2600 and AP3600. After the upgrade to a
Release 7.6.X image, the predownload functionality works as expected. The predownload failure is only
a one-time failure.
Step 1 Upload your controller configuration files to a server to back them up.
Note We highly recommend that you back up your controller's configuration files prior to upgrading the controller
software. Otherwise, you must manually reconfigure the controller.
Step 2 Follow these steps to obtain the controller software:
a) Browse to the Cisco Software Center: http://www.cisco.com/cisco/software/navigator.html
b) Choose Wireless from the center selection window.
c) Click Wireless LAN Controllers.
The following options are available: Integrated Controllers and Controller Modules and Standalone Controllers.
d) Depending on your controller platform, click one of the above options.
e) Click the controller model number or name. The Download Software page is displayed.
f) Click a controller software release. The software releases are labeled as follows to help you determine which release
to download:
Early Deployment (ED)—These software releases provide new features, new hardware platform support, and bug
fixes.
Maintenance Deployment (MD)—These software releases provide bug fixes and ongoing software maintenance.
Deferred (DF)—These software releases have been deferred. We recommend that you migrate to an upgraded release.
g) Choose a software release number.
h) Click the filename (filename.aes).
i) Click Download.
j) Read Cisco’s End User Software License Agreement and then click Agree.
k) Save the file to your hard drive.
l) Repeat steps a through k to download the remaining file.
Step 3 Copy the controller software file (filename.aes) to the default directory on your TFTP or FTP server.
Step 4 (Optional) Disable the controller 802.11X networks.
Note For busy networks, controllers on high utilization, or small controller platforms, we recommend that you disable
the 802.11X networks as a precautionary measure.
Step 5 Choose Commands > Download File to open the Download File to Controller page.
Step 6 From the File Type drop-down list, choose Code.
Step 7 From the Transfer Mode drop-down list, choose from the following options:
• TFTP
• FTP
• SFTP (available in 7.4 and later releases)
Step 8 In the IP Address text box, enter the IP address of the server.
If you are using a TFTP server, the default values of 10 retries and 6 seconds for the Maximum Retries and Timeout text
boxes should work correctly without any adjustment. However, you can change these values.
Step 9 Enter the maximum number of times that the TFTP server attempts to download the software in the Maximum Retries
text box and the amount of time (in seconds) that the TFTP server attempts to download the software in the Timeout
text box.
Step 10 In the File Path text box, enter the directory path of the software.
Step 11 In the File Name text box, enter the name of the controller software file (filename.aes).
Step 12 If you are using an FTP server, follow these steps:
a) In the Server Login Username text box, enter the username to log into the FTP server.
b) In the Server Login Password text box, enter the password to log into the FTP server.
c) In the Server Port Number text box, enter the port number on the FTP server through which the download occurs.
The default value is 21.
Step 13 Click Download to download the software to the controller. A message appears indicating the status of the download.
Step 14 To configure the predownloading of access point images globally, choose Wireless > Access Points > Global
Configuration to open the Global Configuration page.
Step 15 In the AP Image Pre-download section, perform one of the following:
• To instruct all the access points to predownload a primary image from the controller, click Download Primary
under the AP Image Pre-download.
• To instruct all the access points to swap their primary and backup images, click Interchange Image.
• To download an image from the controller and store it as a backup image, click Download Backup.
• To abort the predownload operation, click Abort Predownload.
The output lists access points that are specified for predownloading and provides for each access point, primary and
secondary image versions, the version of the predownload image, the predownload retry time (if necessary), and the
number of predownload attempts. The output also includes the predownload status for each device. The status of the
access points is as follows:
• None—The access point is not scheduled for predownload.
• Predownloading—The access point is predownloading the image.
• Not supported—The access point (1120, 1230, and 1310) does not support predownloading.
• Initiated—The access point is waiting to get the predownload image because the concurrent download limit has
been reached.
• Failed—The access point has failed 64 predownload attempts.
• Complete—The access point has completed predownloading.
Step 7 Set a reboot time for the controller and the access points.
Use one of these commands to schedule a reboot of the controller and access points:
• Specify the amount of time delay before the devices reboot by entering this command:
reset system in HH:MM:SS image {swap | no-swap} reset-aps [save-config]
Note The swap operand in the reset command will result in the swapping of the primary and backup images
on both the controller and the access point.
The controller sends a reset message to all joined access points, and then the controller resets.
• Specify a date and time for the devices to reboot by entering this command:
reset system at YYYY-MM-DD HH:MM:SS image {swap | no-swap} reset-aps [save-config]
The controller sends a reset message to all joined access points, and then the controller resets.
Note The swap operand in the reset command will result in the swapping of the primary and backup images
on both the controller and the access point.
• Set up an SNMP trap message that announces the upcoming reset by entering this command:
reset system notify-time minutes
The controller sends the announcement trap the configured number of minutes before the reset.
• Cancel the scheduled reboot by entering this command:
reset system cancel
Note If you configure reset times and then use the config time command to change the system time on the
controller, the controller notifies you that any scheduled reset times will be canceled and must be
reconfigured after you set the system time.
Note The ASCII character set consists of printable and nonprintable characters. The login banner supports only
printable characters.
Follow the instructions in this section to download a login banner to the controller through the GUI or CLI.
However, before you begin, make sure that you have a TFTP or FTP server available for the file download.
Follow these guidelines when setting up a TFTP or FTP server:
• If you are downloading through the service port, the TFTP or FTP server must be on the same subnet
as the service port because the service port is not routable, or you must create static routes on the
controller.
• If you are downloading through the distribution system network port, the TFTP or FTP server can be
on the same or a different subnet because the distribution system port is routable.
• A third-party TFTP or FTP server cannot run on the same computer as Cisco Prime Infrastructure because
the Prime Infrastructure built-in TFTP or FTP server and the third-party TFTP or FTP server require
the same communication port.
Note Clearing the controller configuration does not remove the login banner. See the Clearing
the Login Banner (GUI) section for information about clearing the login banner using
the controller GUI or CLI.
Note The controller can have only one login banner file. If you download another login banner
file to the controller, the first login banner file is overwritten.
Step 1 Copy the login banner file to the default directory on your server.
Step 2 Choose Commands > Download File to open the Download File to Controller page.
Step 3 From the File Type drop-down list, choose Login Banner.
Step 4 From the Transfer Mode drop-down list, choose from the following options:
• TFTP
• FTP
• SFTP (available in 7.4 and later releases)
Step 5 In the IP Address text box, enter the IP address of the server type you chose in Step 4.
If you are using a TFTP server, the default values of 10 retries and 6 seconds for the Maximum Retries and Timeout text
boxes should work correctly without any adjustment. However, you can change these values.
Step 6 Enter the maximum number of times that the TFTP server attempts to download the certificate in the Maximum Retries
text box and the amount of time (in seconds) that the TFTP server attempts to download the certificate in the Timeout
text box.
Step 7 In the File Path text box, enter the directory path of the login banner file.
Step 8 In the File Name text box, enter the name of the login banner text (*.txt) file.
Step 9 If you are using an FTP server, follow these steps:
a) In the Server Login Username text box, enter the username to log into the FTP server.
b) In the Server Login Password text box, enter the password to log into the FTP server.
c) In the Server Port Number text box, enter the port number on the FTP server through which the download occurs.
The default value is 21.
Step 10 Click Download to download the login banner file to the controller. A message appears indicating the status of the
download.
Step 4 Specify the IP address of the TFTP or FTP server by entering this command:
transfer download serverip server-ip-address
Step 5 Specify the name of the config file to be downloaded by entering this command:
transfer download path server-path-to-file
Step 6 Specify the directory path of the config file by entering this command:
transfer download filenamefilename.txt
Step 9 View the download settings by entering the transfer download start command. Enter y when prompted to confirm the
current settings and start the download process.
Step 1 Choose Commands > Login Banner to open the Login Banner page.
Step 2 Click Clear.
Step 3 When prompted, click OK to clear the banner.
To clear the login banner from the controller using the controller CLI, enter the clear login-banner command.
Note For more information about configuring local EAP, see the Configuring Local EAP section.
Follow the instructions in this section to download a vendor-specific device certificate to the controller through
the GUI or CLI. However, before you begin, make sure you have a TFTP or FTP server available for the
certificate download. Follow these guidelines when setting up a TFTP or FTP server:
• If you are downloading through the service port, the TFTP or FTP server must be on the same subnet
as the service port because the service port is not routable, or you must create static routes on the
controller.
• If you are downloading through the distribution system network port, the TFTP or FTP server can be
on the same or a different subnet because the distribution system port is routable.
• A third-party TFTP or FTP server cannot run on the same computer as Cisco Prime Infrastructure because
the Prime Infrastructure built-in TFTP or FTP server and the third-party TFTP or FTP server require
the same communication port.
Step 1 Copy the device certificate to the default directory on your server.
Step 2 Choose Commands > Download File to open the Download File to Controller page.
Step 3 From the File Type drop-down list, choose Vendor Device Certificate.
Step 4 In the Certificate Password text box, enter the password that was used to protect the certificate.
Step 5 From the Transfer Mode drop-down list, choose from the following options:
• TFTP
• FTP
• SFTP (available in 7.4 and later releases)
Step 6 In the IP Address text box, enter the IP address of the server.
If you are using a TFTP server, the default values of 10 retries and 6 seconds for the Maximum Retries and Timeout text
boxes should work correctly without any adjustment. However, you can change these values.
Step 7 Enter the maximum number of times that the TFTP server attempts to download the certificate in the Maximum Retries
text box and the amount of time (in seconds) that the TFTP server attempts to download the certificate in the Timeout
text box.
Step 8 In the File Path text box, enter the directory path of the certificate.
Step 9 In the File Name text box, enter the name of the certificate.
Step 10 If you are using an FTP server, follow these steps:
a) In the Server Login Username text box, enter the username to log into the FTP server.
b) In the Server Login Password text box, enter the password to log into the FTP server.
c) In the Server Port Number text box, enter the port number on the FTP server through which the download occurs.
The default value is 21.
Step 11 Click Download to download the device certificate to the controller. A message appears indicating the status of the
download.
Step 12 After the download is complete, choose Commands > Reboot > Reboot.
Step 13 If prompted to save your changes, click Save and Reboot.
Step 14 Click OK to confirm your decision to reboot the controller.
Step 3 Specify the type of the file to be downloaded by entering this command:
Step 5 Specify the IP address of the TFTP or FTP server by entering this command:
transfer download serverip server-ip-address
Step 6 Specify the name of the config file to be downloaded by entering this command:
transfer download path server-path-to-file
Step 7 Specify the directory path of the config file by entering this command:
transfer download filename filename.pem
Step 10 View the updated settings by entering the transfer download start command. Answer y when prompted to confirm the
current settings and start the download process.
Step 11 Reboot the controller by entering this command:
reset system
Downloading CA Certificates
Controllers and access points have a Certificate Authority (CA) certificate that is used to sign and validate
device certificates. The controller is shipped with a Cisco-installed CA certificate. This certificate may be
used by EAP-FAST (when not using PACs), EAP-TLS, PEAP-GTC, and PEAP-MSCHAPv2 to authenticate
wireless clients during local EAP authentication. However, if you want to use your own vendor-specific CA
certificate, it must be downloaded to the controller.
Note For more information about configuring local EAP, see the Configuring Local EAP section.
Follow the instructions in this section to download CA certificates to the controller through the GUI or CLI.
However, before you begin, make sure that you have a TFTP or FTP server available for the certificate
download. Follow these guidelines when setting up a TFTP or FTP server:
• If you are downloading through the service port, the TFTP or FTP server must be on the same subnet
as the service port because the service port is not routable, or you must create static routes on the
controller.
• If you are downloading through the distribution system network port, the TFTP or FTP server can be
on the same or a different subnet because the distribution system port is routable.
• A third-party TFTP or FTP server cannot run on the same computer as Cisco Prime Infrastructure because
the Prime Infrastructure built-in TFTP or FTP server and the third-party TFTP or FTP server require
the same communication port.
Step 5 In the IP Address text box, enter the IP address of the server.
If you are using a TFTP server, the default values of 10 retries and 6 seconds for the Maximum Retries and Timeout text
boxes should work correctly without any adjustment. However, you can change these values.
Step 6 Enter the maximum number of times that the TFTP server attempts to download the certificate in the Maximum Retries
text box and the amount of time (in seconds) that the TFTP server attempts to download the certificate in the Timeout
text box.
Step 7 In the File Path text box, enter the directory path of the certificate.
Step 8 In the File Name text box, enter the name of the certificate.
Step 9 If you are using an FTP server, follow these steps:
a) In the Server Login Username text box, enter the username to log on to the FTP server.
b) In the Server Login Password text box, enter the password to log on to the FTP server.
c) In the Server Port Number text box, enter the port number on the FTP server through which the download occurs.
The default value is 21.
Step 10 Click Download to download the CA certificate to the controller. A message appears indicating the status of the download.
Step 11 After the download is complete, choose Commands > Reboot > Reboot.
Step 12 If prompted to save your changes, click Save and Reboot.
Step 13 Click OK to confirm your decision to reboot the controller.
Step 3 Specify the type of the file to be downloaded by entering this command:
transfer download datatype eapdevcert
Step 4 Specify the IP address of the TFTP or FTP server by entering this command:
transfer download serverip server-ip-address
Step 5 Specify the directory path of the config file by entering this command:
transfer download path server-path-to-file
Step 6 Specify the name of the config file to be downloaded by entering this command:
transfer download filename filename
Step 9 View the updated settings by entering the transfer download start command. Answer y when prompted to confirm the
current settings and start the download process.
Step 10 Reboot the controller by entering the reset system command.
Uploading PACs
Protected access credentials (PACs) are credentials that are either automatically or manually provisioned and
used to perform mutual authentication with a local EAP authentication server during EAP-FAST authentication.
When manual PAC provisioning is enabled, the PAC file is manually generated on the controller.
Follow the instructions in this section to generate and load PACs from the controller through the GUI or CLI.
However, before you begin, make sure you have a TFTP or FTP server available for the PAC upload. Follow
these guidelines when setting up a TFTP or FTP server:
• If you are uploading through the service port, the TFTP or FTP server must be on the same subnet as
the service port because the service port is not routable, or you must create static routes on the controller.
• If you are uploading through the distribution system network port, the TFTP or FTP server can be on
the same or a different subnet because the distribution system port is routable.
• A third-party TFTP or FTP server cannot run on the same computer as Cisco Prime Infrastructure because
the Prime Infrastructure built-in TFTP or FTP server and the third-party TFTP or FTP server require
the same communication port.
Step 1 Choose Commands > Upload File to open the Upload File from Controller page.
Step 2 From the File Type drop-down list, choose PAC (Protected Access Credential).
Step 3 In the User text box, enter the name of the user who will use the PAC.
Step 4 In the Validity text box, enter the number of days for the PAC to remain valid. The default setting is zero (0).
Step 5 In the Password and Confirm Password text boxes, enter a password to protect the PAC.
Step 6 From the Transfer Mode drop-down list, choose from the following options:
• TFTP
• FTP
• SFTP (available in 7.4 and later releases)
Step 7 In the IP Address (IPv4/IPv6) text box, enter the IPv4/IPv6 address of the server.
Step 8 In the File Path text box, enter the directory path of the PAC.
Step 9 In the File Name text box, enter the name of the PAC file. PAC files have a .pac extension.
Step 10 If you are using an FTP server, follow these steps:
a) In the Server Login Username text box, enter the username to log into the FTP server.
b) In the Server Login Password text box, enter the password to log into the FTP server.
c) In the Server Port Number text box, enter the port number on the FTP server through which the upload occurs. The
default value is 21.
Step 11 Click Upload to upload the PAC from the controller. A message appears indicating the status of the upload.
Step 12 Follow the instructions for your wireless client to load the PAC on your client devices. Make sure to use the password
that you entered above.
Step 5 Specify the IP address of the TFTP or FTP server by entering this command:
transfer upload serverip server-ip-address
Note The server supports both, IPv4 and
IPv6.
Step 6 Specify the directory path of the config file by entering this command:
transfer upload path server-path-to-file
Step 7 Specify the name of the config file to be uploaded by entering this command:
transfer upload filename manual.pac.
Step 9 View the updated settings by entering the transfer upload start command. Answer y when prompted to confirm the
current settings and start the upload process.
Step 10 Follow the instructions for your wireless client to load the PAC on your client devices. Make sure to use the password
that you entered above.
Note Do not download a configuration file to your controller that was uploaded from a different controller
platform. For example, a Cisco 5500 Series Controller does not support the configuration file from a Cisco
2500 Series Controller.
Note While Cisco WLC configuration backup is in progress, we recommend you do not initiate any new
configuration or modify any existing configuration settings. This is to avoid corrupting the configuration
file.
Note You can also read and modify the configuration file.
• The FTP or the TFTP servers for transfer of configuration, image, and so on, must be reachable over a
wired connection. The transfer cannot be performed over one of the wireless clients of the Cisco WLC.
If you try to use a wireless client of the Cisco WLC, you are prompted with a system message saying
that the server is not reachable. However, if you use a wireless client that is associated with another
Cisco WLC, the FTP or the TFTP servers are reachable.
Step 1 Choose Commands > Upload File to open the Upload File from Controller page.
Step 2 From the File Type drop-down list, choose Configuration.
Step 3 Encrypt the configuration file by selecting the Configuration File Encryption check box and entering the encryption
key in the Encryption Key text box.
Step 4 From the Transfer Mode drop-down list, choose from the following options:
• TFTP
• FTP
• SFTP (available in 7.4 and later releases)
Step 5 In the IP Address text box, enter the IP address of the server.
Step 6 In the File Path text box, enter the directory path of the configuration file.
Step 7 In the File Name text box, enter the name of the configuration file.
Step 8 If you are using an FTP server, follow these steps:
a) In the Server Login Username text box, enter the username to log into the FTP server.
b) In the Server Login Password text box, enter the password to log into the FTP server.
c) In the Server Port Number text box, enter the port number on the FTP server through which the upload occurs. The
default value is 21.
Step 9 Click Upload to upload the configuration file to the server. A message appears indicating the status of the upload. If the
upload fails, repeat this procedure and try again.
Step 1 Specify the transfer mode used to upload the configuration file by entering this command:
transfer upload mode {tftp | ftp | sftp}
Step 2 Specify the type of file to be uploaded by entering this command:
transfer upload datatype config
Step 3 Encrypt the configuration file by entering these commands:
• transfer encrypt enable
• transfer encrypt set-key key, where key is the encryption key used to encrypt the file.
Mode............................................. TFTP
TFTP Server IP................................... 10.10.10.4
TFTP Path........................................ Config/
TFTP Filename.................................... AS_4402_4_2_55_8_Config.xml
Data Type........................................ Config File
Encryption....................................... Disabled
**************************************************
*** WARNING: Config File Encryption Disabled ***
**************************************************
Step 1 Choose Commands > Download File to open the Download File to Controller page.
Step 2 From the File Type drop-down list, choose Configuration.
Step 3 If the configuration file is encrypted, select the Configuration File Encryption check box and enter the encryption key
used to decrypt the file in the Encryption Key text box.
Note The key that you enter here should match the one entered during the upload process.
Step 4 From the Transfer Mode drop-down list, choose from the following options:
• TFTP
• FTP
• SFTP (available in 7.4 and later releases)
Step 5 In the IP Address text box, enter the IP address of the server.
If you are using a TFTP server, the default values of 10 retries and 6 seconds for the Maximum Retries and Timeout text
boxes should work correctly without any adjustment. However, you can change these values.
Step 6 Enter the maximum number of times that the TFTP server attempts to download the configuration file in the Maximum
Retries text box and the amount of time (in seconds) that the TFTP server attempts to download the configuration file
in the Timeout text box.
Step 7 In the File Path text box, enter the directory path of the configuration file.
Step 8 In the File Name text box, enter the name of the configuration file.
Step 9 If you are using an FTP server, follow these steps:
a) In the Server Login Username text box, enter the username to log into the FTP server.
b) In the Server Login Password text box, enter the password to log into the FTP server.
c) In the Server Port Number text box, enter the port number on the FTP server through which the download occurs.
The default value is 21.
Step 10 Click Download to download the file to the controller. A message appears indicating the status of the download, and
the controller reboots automatically. If the download fails, repeat this procedure and try again.
Note The controller does not support incremental configuration downloads. The configuration file contains all
mandatory commands (all interface address commands, mgmtuser with read-write permission commands,
and interface port or LAG enable or disable commands) required to successfully complete the download.
For example, if you download only the config time ntp server index server_address command as part of
the configuration file, the download fails. Only the commands present in the configuration file are applied
to the controller, and any configuration in the controller prior to the download is removed.
Step 1 Specify the transfer mode used to download the configuration file by entering this command:
transfer download mode {tftp | ftp | sftp}
Step 2 Specify the type of file to be downloaded by entering this command:
transfer download datatype config
Step 3 If the configuration file is encrypted, enter these commands:
• transfer encrypt enable
• transfer encrypt set-key key, where key is the encryption key used to decrypt the file.
Note The key that you enter here should match the one entered during the upload process.
Step 4 Specify the IP address of the TFTP or FTP server by entering this command:
transfer download serverip server-ip-address
Step 5 Specify the directory path of the configuration file by entering this command:
transfer download path server-path-to-file
Step 6 Specify the name of the configuration file to be downloaded by entering this command:
transfer download filename filename
Step 7 If you are using a TFTP server, enter these commands:
• transfer download tftpMaxRetries retries
• transfer download tftpPktTimeout timeout
Note The default values of 10 retries and a 6-second timeout should work correctly without any adjustment.
However, you can change these values. To do so, enter the maximum number of times that the TFTP
server attempts to download the software for the retries parameter and the amount of time (in seconds)
that the TFTP server attempts to download the software for the timeout parameter.
Step 8 If you are using an FTP server, enter these commands to specify the username and password used to log into the FTP
server and the port number through which the download occurs:
• transfer upload username username
• transfer upload password password
• transfer upload port port
Note The default value for the port parameter is
21.
Mode............................................. TFTP
TFTP Server IP................................... 10.10.10.4
TFTP Path........................................ Config/
TFTP Filename.................................... AS_4402_4_2_55_8_Config.xml
Data Type........................................ Config File
Encryption....................................... Disabled
**************************************************
*** WARNING: Config File Encryption Disabled ***
**************************************************
Saving Configurations
Controllers contain two kinds of memory: volatile RAM and NVRAM. At any time, you can save the
configuration changes from active volatile RAM to nonvolatile RAM (NVRAM) using one of these commands:
• save config—Saves the configuration from volatile RAM to NVRAM without resetting the controller.
• reset system—Prompts you to confirm that you want to save configuration changes before the controller
reboots.
• logout—Prompts you to confirm that you want to save configuration changes before you log out.
Step 1 Upload the configuration file to a TFTP/FTP/SFTP server by performing one of the following:
• Upload the file using the controller GUI.
• Upload the file using the controller CLI.
Step 2 Read or edit the configuration file on the server. You can modify or delete existing CLI commands and add new CLI
commands to the file.
Note To edit the configuration file, you can use either Notepad or WordPad on Windows or the VI editor on
Linux.
Step 3 Save your changes to the configuration file on the server.
Step 4 Download the configuration file to the controller by performing one of the following:
• Download the file using the controller GUI.
• Download the file using the controller CLI.
The controller converts the configuration file to an XML format, saves it to flash memory, and then reboots using the
new configuration. CLI commands with known keywords and proper syntax are converted to XML while improper CLI
commands are ignored and saved to flash memory. Any CLI commands that have invalid values are replaced with default
values. To see any ignored commands or invalid configuration values, enter this command:
show invalid-config
Note You cannot execute this command after the clear config or save config command.
Step 5 If the downloaded configuration contains a large number of invalid CLI commands, you might want to upload the invalid
configuration to the TFTP or FTP server for analysis. To do so, perform one of the following:
• Upload the invalid configuration using the controller GUI. Follow the instructions in the Uploading Configuration
Files (GUI) section but choose Invalid Config from the File Type drop-down list in Step 2 and skip Step 3.
• Upload the invalid configuration using the controller CLI. Follow the instructions in the Uploading Configuration
Files (CLI) section but enter the transfer upload datatype invalid-config command in Step 2 and skip Step 3.
Step 6 The controller does not support the uploading and downloading of port configuration CLI commands. If you want to
configure the controller ports, enter these commands:
• config port linktrap {port | all} {enable | disable}—Enables or disables the up and down link traps for a specific
controller port or for all ports.
• config port adminmode {port | all} {enable | disable}—Enables or disables the administrative mode for a specific
controller port or for all ports.
Step 3 Follow the instructions in the Configuring the Controller-Using the Configuration Wizard section to complete the initial
configuration.
Step 2 When you are prompted for a username, restore the factory-default settings by entering this command:
recover-config
The controller reboots and the configuration wizard starts automatically.
Step 3 Follow the instructions in the Configuring the Controller-Using the Configuration Wizard section to complete the initial
configuration.
When the controller reboots, the CLI console displays the following reboot information:
• Initializing the system.
• Verifying the hardware configuration.
• Loading microcode into memory.
• Verifying the operating system software load.
• Initializing with its stored configurations.
• Displaying the login prompt.
Step 1 Choose Management > Local Management Users to open the Local Management Users page.
This page lists the names and access privileges of the local management users.
Note If you want to delete any of the user accounts from the controller, hover your cursor over the blue drop-down
arrow and choose Remove. However, deleting the default administrative user prohibits both GUI and CLI access
to the controller. Therefore, you must create a user with administrative privileges (ReadWrite) before you remove
the default user.
Step 2 Click New to create a lobby ambassador account. The Local Management Users > New page appears.
Step 3 In the User Name text box, enter a username for the lobby ambassador account.
Note Management usernames must be unique because they are stored in a single database.
Step 4 In the Password and Confirm Password text boxes, enter a password for the lobby ambassador account.
Note Passwords are case sensitive. The settings for the management User Details parameters depends on the settings
that you make in the Password Policy page. The following requirements are enforced on the password
• The password should contain characters from at least three of the following classes: lowercase letters,
uppercase letters, digits, and special characters.
• No character in the password can be repeated more than three times consecutively.
• The password should not contain a management username or the reverse letters of a username.
• The password should not contain words like Cisco, oscic, admin, nimda, or any variant obtained by changing
the capitalization of letters by substituting 1, |, or ! or substituting 0 for o or substituting $ for s.
Step 5 Choose LobbyAdmin from the User Access Mode drop-down list. This option enables the lobby ambassador to create
guest user accounts.
Note The ReadOnly option creates an account with read-only privileges, and the ReadWrite option creates an
administrative account with both read and write privileges.
Step 6 Click Apply to commit your changes. The new lobby ambassador account appears in the list of local management users.
Step 7 Click Save Configuration to save your changes.
Note Replacing lobby-admin with read-only creates an account with read-only privileges. Replacing
lobby-admin with read-write creates an administrative account with both read and write privileges.
Step 1 Log into the controller as the lobby ambassador, using the username and password. The Lobby Ambassador Guest
Management > Guest Users List page appears.
Step 2 Click New to create a guest user account. The Lobby Ambassador Guest Management > Guest Users List > New page
appears.
Step 3 In the User Name text box, enter a name for the guest user. You can enter up to 24 characters.
Step 4 Perform one of the following:
• If you want to generate an automatic password for this guest user, select the Generate Password check box. The
generated password is entered automatically in the Password and Confirm Password text boxes.
• If you want to create a password for this guest user, leave the Generate Password check box unselected and enter
a password in both the Password and Confirm Password text boxes.
Note Passwords can contain up to 24 characters and are case
sensitive.
Step 5 From the Lifetime drop-down lists, choose the amount of time (in days, hours, minutes, and seconds) that this guest user
account is to remain active. A value of zero (0) for all four text boxes creates a permanent account.
Default: 1 day
Range: 5 minutes to 30 days
Note The smaller of this value or the session timeout for the guest WLAN, which is the WLAN on which the guest
account is created, takes precedence. For example, if a WLAN session timeout is due to expire in 30 minutes
but the guest account lifetime has 10 minutes remaining, the account is deleted in 10 minutes upon guest account
expiry. Similarly, if the WLAN session timeout expires before the guest account lifetime, the client experiences
a recurring session timeout that requires reauthentication.
Note You can change a guest user account with a nonzero lifetime to another lifetime value at any time while the
account is active. However, to make a guest user account permanent using the controller GUI, you must delete
the account and create it again. If desired, you can use the config netuser lifetime user_name 0 command to
make a guest user account permanent without deleting and recreating it.
Step 6 From the WLAN SSID drop-down list, choose the SSID that will be used by the guest user. The only WLANs that are
listed are those WLANs for which Layer 3 web authentication has been configured.
Note We recommend that you create a specific guest WLAN to prevent any potential conflicts. If a guest account
expires and it has a name conflict with an account on the RADIUS server and both are on the same WLAN, the
users associated with both accounts are disassociated before the guest account is deleted.
Step 7 In the Description text box, enter a description of the guest user account. You can enter up to 32 characters.
Step 8 Click Apply to commit your changes. The new guest user account appears in the list of guest users on the Guest Users
List page.
From this page, you can see all of the guest user accounts, their WLAN SSID, and their lifetime. You can also edit or
remove a guest user account. When you remove a guest user account, all of the clients that are using the guest WLAN
and are logged in using that account’s username are deleted.
Step 9 Repeat this procedure to create any additional guest user accounts.
Restoring Passwords
Before You Begin
Ensure that you are accessing the controller CLI through the console port.
Step 1 After the controller boots up, enter Restore-Password at the User prompt.
Note For security reasons, the text that you enter does not appear on the controller console.
Note SNMP v3 is time sensitive. Ensure that you configure the correct time and time zone on your controller.
Step 1 Choose Management > SNMP > SNMP V3 Users to open the SNMP V3 Users page.
Step 2 If “default” appears in the User Name column, hover your cursor over the blue drop-down arrow for the desired user and
choose Remove to delete this SNMP v3 user.
Step 3 Click New to add a new SNMP v3 user. The SNMP V3 Users > New page appears.
Step 4 In the User Profile Name text box, enter a unique name. Do not enter “default.”
Step 5 Choose Read Only or Read Write from the Access Mode drop-down list to specify the access level for this user. The
default value is Read Only.
Step 6 From the Authentication Protocol drop-down list, choose the desired authentication method: None, HMAC-MD5 (Hashed
Message Authentication Coding-Message Digest 5), or HMAC-SHA (Hashed Message Authentication Coding-Secure
Hashing Algorithm). The default value is HMAC-SHA.
Step 7 In the Auth Password and Confirm Auth Password text boxes, enter the shared secret key to be used for authentication.
You must enter at least 12 characters that include both letters and numbers.
Step 8 From the Privacy Protocol drop-down list, choose the desired encryption method: None, CBC-DES (Cipher Block
Chaining-Digital Encryption Standard), or CFB-AES-128 (Cipher Feedback Mode-Advanced Encryption Standard-128).
The default value is CFB-AES-128.
Note In order to configure CBC-DES or CFB-AES-128 encryption, you must have selected either HMAC-MD5 or
HMAC-SHA as the authentication protocol in Step 6.
Step 9 In the Priv Password and Confirm Priv Password text boxes, enter the shared secret key to be used for encryption. You
must enter at least 12 characters that include both letters and numbers.
Step 10 Click Apply.
Step 11 Click Save Configuration.
Step 12 Reboot the controller so that the SNMP v3 user that you added takes effect.
Step 1 See the current list of SNMP v3 users for this controller by entering this command:
show snmpv3user
Step 2 If “default” appears in the SNMP v3 User Name column, enter this command to delete this user:
config snmp v3user delete username
The username parameter is the SNMP v3 username (in this case, “default”).
OpenSSL> req -new -newkey rsa:1024 -nodes -keyout mykey.pem -out myreq.pem
Loading 'screen' into random state - done
Generating a 1024 bit RSA private key
................................................................++++++
...................................................++++++
writing new private key to 'mykey.pem'
-----
You are about to be asked to enter information that will be incorporated
into your certificate request.
What you are about to enter is what is called a Distinguished Name or a DN.
There are quite a few fields but you can leave some blank
For some fields there will be a default value,
If you enter '.', the field will be left blank.
-----
Country Name (2 letter code) [AU]:US
State or Province Name (full name) [Some-State]:CA
Locality Name (eg, city) []:San Jose
Organization Name (eg, company) [Internet Widgits Pty Ltd]:ABC
Organizational Unit Name (eg, section) []:CDE
Common Name (eg, YOUR name) []:XYZ.ABC
Email Address []:[email protected]
After you provide all the required details two files are generated:
• A new private key that includes the name mykey.pem
• A CSR that includes the name myreq.pem
Step 3 Copy and paste the Certificate Signing Request (CSR) information into any CA enrollment tool. After you submit the
CSR to a third party CA, the third party CA digitally signs the certificate and sends back the signed certificate chain
through e-mail. In case of chained certificates, you receive the entire chain of certificates from the CA. If you only have
one intermediate certificate similar to the example above, you will receive the following three certificates from the CA:
• Root certificate.pem
• Intermediate certificate.pem
• Device certificate.pem
Step 4 Once you have all the three certificates, copy and paste into another file the contents of each .pem file in this order:
------BEGIN CERTIFICATE------
*Device cert*
------END CERTIFICATE------
------BEGIN CERTIFICATE------
*Intermediate CA cert *
------END CERTIFICATE--------
------BEGIN CERTIFICATE------
*Root CA cert *
------END CERTIFICATE------
What to Do Next
Download the final.pem file to the controller either using CLI or GUI.
Step 1 Copy the device certificate final.pem to the default directory on your TFTP server.
Step 2 Choose Security > Web Auth > Certificate to open the Web Authentication Certificate page.
Step 3 Check the Download SSL Certificate check box to view the Download SSL Certificate From Server parameters.
Step 4 In the Server IP Address text box, enter the IP address of the TFTP server.
Step 5 In the File Path text box, enter the directory path of the certificate.
Step 6 In the File Name text box, enter the name of the certificate.
Step 7 In the Certificate Password text box, enter the password to protect the certificate.
Step 8 Click Apply.
Step 9 After the download is complete, choose Commands > Reboot and click Save and Reboot.
Step 10 Click OK in order to confirm your decision to reboot the controller.
Step 1 Move the final.pem file to the default directory on your TFTP server. Change the download settings by entering the
following commands:
Step 2 Enter the password for the .pem file so that the operating system can decrypt the SSL key and certificate.
Note Ensure that the value for certpassword is the same as the -passout parameter when you generate a
CSR.
Step 3 Start the certificate and key download by entering the this command:
transfer download start
Example:
(Cisco Controller) > transfer download start
Mode............................................. TFTP
Data Type........................................ Site Cert
TFTP Server IP................................... 10.77.244.196
TFTP Packet Timeout.............................. 6
TFTP Max Retries................................. 10
TFTP Path........................................./
TFTP Filename.................................... final.pem
Certificate installed.
Reboot the switch to use new certificate.
Note The WEB UI home page may not load when ip http access class command is enabled. When you encounter
this issue, we recommend that you do the following:
1 Run the show iosd liin command.
2 Get the internet-address and configure the same ip as permit in the access-list.
Note For WEB UI access using TACACS+ server, custom method-list for authentication and authorization
pointing to the TACACS+ server group does not work. You should use the default authorization method-list
pointing to the same TACACS+ server group for the WEB UI to work.
Note While installing certificate for web authentication for Release 7.6, certificate load fails due to Missing
Root CA cert error. Please download a chained certificate that includes intermediate Certificate Authority
(CA) & root CA and install it on the Cisco WLC.
Step 1 Choose Security > Web Auth > Certificate to open the Web Authentication Certificate page.
This page shows the details of the current web authentication certificate.
Step 2 If you want to use a new operating system-generated web authentication certificate, follow these steps:
a) Click Regenerate Certificate. The operating system generates a new web authentication certificate, and a successfully
generated web authentication certificate message appears.
b) Reboot the controller to register the new certificate.
Step 3 If you prefer to use an externally generated web authentication certificate, follow these steps:
a) Verify that the controller can ping the TFTP server.
b) Select the Download SSL Certificate check box.
c) In the Server IP Address text box, enter the IP address of the TFTP server.
The default values of 10 retries and 6 seconds for the Maximum Retries and Timeout text boxes should work correctly
without any adjustment. However, you can change these values.
d) Enter the maximum number of times that each download can be attempted in the Maximum Retries text box and the
amount of time (in seconds) allowed for each download in the Timeout text box.
e) In the Certificate File Path text box, enter the directory path of the certificate.
f) In the Certificate File Name text box, enter the name of the certificate (certname.pem).
g) In the Certificate Password text box, enter the password for the certificate.
h) Click Apply to commit your changes. The operating system downloads the new certificate from the TFTP server.
i) Reboot the controller to register the new certificate.
Step 1 See the current web authentication certificate by entering this command:
show certificate summary
Information similar to the following appears:
Step 2 If you want the operating system to generate a new web authentication certificate, follow these steps:
a) To generate the new certificate, enter this command:
config certificate generate webauth
b) To reboot the controller to register the new certificate, enter this command:
reset system
Step 3 If you prefer to use an externally generated web authentication certificate, follow these steps:
Note We recommend that the Common Name (CN) of the externally generated web authentication certificate be
1.1.1.1 (or the equivalent virtual interface IP address) in order for the client’s browser to match the domains of
the web authentication URL and the web authentication certificate.
1 Specify the name, path, and type of certificate to be downloaded by entering these commands:
transfer download mode tftp
transfer download datatype webauthcert
transfer download serverip server_ip_address
transfer download path server_path_to_file
transfer download filename certname.pem
transfer download certpassword password
transfer download tftpMaxRetries retries
transfer download tftpPktTimeout timeout
Note The default values of 10 retries and a 6-second timeout should work correctly without any adjustment.
However, you can change these values. To do so, enter the maximum number of times that each download
can be attempted for the retries parameter and the amount of time (in seconds) allowed for each download
for the timeout parameter.
2 Start the download process by entering this command:
transfer download start
3 Reboot the controller to register the new certificate by entering this command:
reset system
Note If a client uses more than 20 DNS resolved addresses, the controller overwrites the 21st address in the
first address space in the Mobile Station Control Block (MSCB) table, but the first address is still retained
in the client. If the client again tries to use the first address, it will not be reachable because the controller
does not have this address in the list of allowed addresses for the client's MSCB table.
When a client is associated with 802.1X + WebAuth Security and when the client roams, the 802.1X username
is updated in the client information.
Note Web Authentication does not work with IPv6 URL when WLAN is LS however IPv4 with LS and IPv6
with CS works.. The re-directed web-auth page is not displayed when IPv6 URL is typed in the browser
and WLAN is in Local Switching.
Note When clients connect to a WebAuth SSID with preauthorization ACL configured to allow VPN users, the
clients will get disconnected from the SSID every few minutes. Webauth SSIDs must not connect without
authenticating on the web page.
After the user clicks Yes to proceed (or if the client’s browser does not display a security alert), the web
authentication system redirects the client to a login page.
Step 9 Reboot the PC. On the next web authentication attempt, the login page appears.
The following figure shows the default web authentication login page.
Figure 19: Default Web Authentication Login Page
The default login page contains a Cisco logo and Cisco-specific text. You can choose to have the web authentication
system display one of the following:
• The default login page
• A modified version of the default login page
• A customized login page that you configure on an external web server
• A customized login page that you download to the controller
The Choosing the Default Web Authentication Login Page section provides instructions for choosing how the web
authentication login page appears.
When the user enters a valid username and password on the web authentication login page and clicks Submit, the web
authentication system displays a successful login page and redirects the authenticated client to the requested URL.
The default successful login page contains a pointer to a virtual gateway address URL in the https://<IP
address>/logout.html format. The IP address that you set for the controller virtual interface serves as the redirect address
for the login page
disable command. If you enter this command, users must use a browser that is configured to use a more
secure protocol such as SSLv3 or later releases. The default value is disabled.
Note Cisco TAC is not responsible for creating a custom webauth bundle.
If you have a complex custom web authentication module, it is recommended that you use an external web-auth
config on the controller, where the full login page is hosted at an external web server.
Step 1 Choose Security > Web Auth > Web Login Page to open the Web Login page.
Step 2 From the Web Authentication Type drop-down list, choose Internal (Default).
Step 3 If you want to use the default web authentication login page as is, go to Step 8. If you want to modify the default login
page, go to Step 4.
Step 4 If you want to hide the Cisco logo that appears in the top right corner of the default page, choose the Cisco Logo Hide
option. Otherwise, click the Show option.
Step 5 If you want the user to be directed to a particular URL (such as the URL for your company) after login, enter the desired
URL in the Redirect URL After Login text box. You can enter up to 254 characters.
Step 6 If you want to create your own headline on the login page, enter the desired text in the Headline text box. You can enter
up to 127 characters. The default headline is “Welcome to the Cisco wireless network.”
Step 7 If you want to create your own message on the login page, enter the desired text in the Message text box. You can enter
up to 2047 characters. The default message is “Cisco is pleased to provide the Wireless LAN infrastructure for your
network. Please login and put your air space to work.”
Step 8 Click Apply to commit your changes.
Step 9 Click Preview to view the web authentication login page.
Step 10 If you are satisfied with the content and appearance of the login page, click Save Configuration to save your changes.
Otherwise, repeat any of the previous steps as necessary to achieve your desired results.
Step 1 Specify the default web authentication type by entering this command:
config custom-web webauth_type internal
Step 2 If you want to use the default web authentication login page as is, go to Step 7. If you want to modify the default login
page, go to Step 3.
Step 3 To show or hide the Cisco logo that appears in the top right corner of the default login page, enter this command:
config custom-web weblogo {enable | disable}
Step 4 If you want the user to be directed to a particular URL (such as the URL for your company) after login, enter this
command:
Step 5 If you want to create your own headline on the login page, enter this command:
config custom-web webtitle title
You can enter up to 130 characters. The default headline is “Welcome to the Cisco wireless network.” To reset the
headline to the default setting, enter the clear webtitle command.
Step 6 If you want to create your own message on the login page, enter this command:
config custom-web webmessage message
You can enter up to 130 characters. The default message is “Cisco is pleased to provide the Wireless LAN infrastructure
for your network. Please login and put your air space to work.” To reset the message to the default setting, enter the clear
webmessage command.
Step 7 To enable or disable the web authentication logout popup window, enter this command:
config custom-web logout-popup {enable | disable}
2 Ensure that the controller can contact the TFTP server by entering this command:
ping ip-address
3 Copy the logo file (in .jpg, .gif, or .png format) to the default directory on your TFTP server. The maximum file size
is 30 kilobits. For an optimal fit, the logo should be approximately 180 pixels wide and 360 pixels high.
4 Specify the download mode by entering this command:
transfer download mode tftp
5 Specify the type of file to be downloaded by entering this command:
transfer download datatype image
6 Specify the IP address of the TFTP server by entering this command:
transfer download serverip tftp-server-ip-address
Note Some TFTP servers require only a forward slash (/) as the TFTP server IP address, and the TFTP server
automatically determines the path to the correct directory.
7 Specify the download path by entering this command:
transfer download path absolute-tftp-server-path-to-file
Step 10 Follow the instructions in the Verifying the Web Authentication Login Page Settings (CLI), on page 241 section to verify
your settings.
<html>
<head>
<meta http-equiv="Pragma" content="no-cache">
<meta HTTP-EQUIV="Content-Type" CONTENT="text/html; charset=iso-8859-1">
<title>Web Authentication</title>
<script>
function submitAction(){
var link = document.location.href;
var searchString = "redirect=";
var equalIndex = link.indexOf(searchString);
var redirectUrl = "";
if (document.forms[0].action == "") {
var url = window.location.href;
var args = new Object();
var query = location.search.substring(1);
var pairs = query.split("&");
for(var i=0;i<pairs.length;i++){
var pos = pairs[i].indexOf('=');
if(pos == -1) continue;
var argname = pairs[i].substring(0,pos);
var value = pairs[i].substring(pos+1);
args[argname] = unescape(value);
}
document.forms[0].action = args.switch_url;
}
if(equalIndex >= 0) {
equalIndex += searchString.length;
redirectUrl = "";
redirectUrl += link.substring(equalIndex);
}
if(redirectUrl.length > 255)
redirectUrl = redirectUrl.substring(0,255);
document.forms[0].redirect_url.value = redirectUrl;
document.forms[0].buttonClicked.value = 4;
document.forms[0].submit();
}
function loadAction(){
var url = window.location.href;
var args = new Object();
var query = location.search.substring(1);
var pairs = query.split("&");
for(var i=0;i<pairs.length;i++){
var pos = pairs[i].indexOf('=');
if(pos == -1) continue;
var argname = pairs[i].substring(0,pos);
var value = pairs[i].substring(pos+1);
args[argname] = unescape(value);
}
//alert( "AP MAC Address is " + args.ap_mac);
//alert( "The Switch URL to post user credentials is " + args.switch_url);
document.forms[0].action = args.switch_url;
</script>
</head>
<body topmargin="50" marginheight="50" onload="loadAction();">
<form method="post" action="https://209.165.200.225/login.html">
<input TYPE="hidden" NAME="buttonClicked" SIZE="16" MAXLENGTH="15" value="0">
<input TYPE="hidden" NAME="redirect_url" SIZE="255" MAXLENGTH="255" VALUE="">
<input TYPE="hidden" NAME="err_flag" SIZE="16" MAXLENGTH="15" value="0">
<div align="center">
<table border="0" cellspacing="0" cellpadding="0">
<tr> <td> </td></tr>
<tr align="center">
<tr align="center">
<td colspan="2"><input type="button" name="Submit" value="Submit" class="button"
onclick="submitAction();">
</td>
</tr>
</table>
</div>
</form>
</body>
</html>
These parameters are added to the URL when the user’s Internet browser is redirected to the customized login
page:
• ap_mac—The MAC address of the access point to which the wireless user is associated.
• switch_url—The URL of the controller to which the user credentials should be posted.
• redirect—The URL to which the user is redirected after authentication is successful.
• statusCode—The status code returned from the controller’s web authentication server.
• wlan—The WLAN SSID to which the wireless user is associated.
Note For additional information, see the External Web Authentication with Wireless LAN Controllers
Configuration Example at
http://www.cisco.com/c/en/us/support/docs/wireless-mobility/wlan-security/71881-ext-web-auth-wlc.html.
This figure shows an example of a modified default web authentication login page.
Figure 21: Modified Default Web Authentication Login Page Example
You must configure a preauthentication access control list (ACL) on the WLAN for the external web server
and then choose this ACL as the WLAN preauthentication ACL under Security Policies > Web Policy on the
WLANs > Edit page.
Choosing a Customized Web Authentication Login Page from an External Web Server (GUI)
Step 1 Choose Security > Web Auth > Web Login Page to open the Web Login page.
Step 2 From the Web Authentication Type drop-down list, choose External (Redirect to external server).
Step 3 In the Redirect URL after login text box, enter the URL that you want the user to be redirected after a login.
For example, you may enter your company's URL here and the users will be directed to that URL after login. The
maximum length is 254 characters. By default, the user is redirected to the URL that was entered in the user's browser
before the login page was served. of the customized web authentication login page on your web server. You can enter
up to 252 characters.
Step 4 In the External Webauth URL text box, enter the URL that is to be used for external web authentication.
Step 5 Click Apply.
Step 6 Click Save Configuration.
Choosing a Customized Web Authentication Login Page from an External Web Server (CLI)
Step 2 Specify the URL of the customized web authentication login page on your web server by entering this command:
config custom-web ext-webauth-url url
You can enter up to 252 characters for the URL.
Step 3 Specify the IP address of your web server by entering this command:
config custom-web ext-webserver {add | delete} server_IP_address
You can download a login page example from Cisco Prime Infrastructure and use it as a starting point for
your customized login page. For more information, see the Cisco Prime Infrastructure documentation.
Note If you load a webauth bundle with a .tar compression application that is not GNU compliant, the controller
cannot extract the files in the bundle and the following error messages appear: “Extracting error” and
“TFTP transfer failed.” Therefore, we recommend that you use an application that complies with GNU
standards, such as PicoZip, to compress the .tar file for the webauth bundle.
Note Configuration backups do not include extra files or components, such as the webauth bundle or external
licenses, that you download and store on your controller, so you should manually save external backup
copies of those files or components.
Note If the customized webauth bundle has more than 3 separated elements, we advise you to use an external
server to prevent page load issues that may be caused because of TCP rate-limiting policy on the controller.
Step 1 Copy the .tar file containing your login page to the default directory on your server.
Step 2 Choose Commands > Download File to open the Download File to Controller page.
Step 3 From the File Type drop-down list, choose Webauth Bundle.
Step 4 From the Transfer Mode drop-down list, choose from the following options:
• TFTP
• FTP
Step 5 In the IP Address text box, enter the IP address of the server.
Step 6 If you are using a TFTP server, enter the maximum number of times the controller should attempt to download the .tar
file in the Maximum Retries text box.
The range is 1 to 254.
The default is 10.
Step 7 If you are using a TFTP server, enter the amount of time in seconds before the controller times out while attempting to
download the *.tar file in the Timeout text box.
The range is 1 to 254 seconds.
The default is 6 seconds.
Step 8 In the File Path text box, enter the path of the .tar file to be downloaded. The default value is “/.”
Step 9 In the File Name text box, enter the name of the .tar file to be downloaded.
Step 10 If you are using an FTP server, follow these steps:
1 In the Server Login Username text box, enter the username to log into the FTP server.
2 In the Server Login Password text box, enter the password to log into the FTP server.
3 In the Server Port Number text box, enter the port number on the FTP server through which the download occurs.
The default value is 21.
Step 1 Copy the .tar file containing your login page to the default directory on your server.
Step 2 Specify the download mode by entering this command:
transfer download mode {tftp | ftp | sftp}
Step 4 Specify the IP address of the TFTP server by entering this command:
transfer download serverip tftp-server-ip-address.
Note Some TFTP servers require only a forward slash (/) as the TFTP server IP address, and the TFTP server
automatically determines the path to the correct directory.
Step 7 View your updated settings and answer y to the prompt to confirm the current download settings and start the download
by entering this command:
transfer download start
Information About Assigning Login, Login Failure, and Logout Pages per WLAN
You can display different web authentication login, login failure, and logout pages to users per WLAN. This
feature enables user-specific web authentication pages to be displayed for a variety of network users, such as
guest users or employees within different departments of an organization.
Different login pages are available for all web authentication types (internal, external, and customized).
However, different login failure and logout pages can be specified only when you choose customized as the
web authentication type.
Assigning Login, Login Failure, and Logout Pages per WLAN (GUI)
Step 7 If you chose External as the web authentication type in Step 6, choose AAA Servers and choose up to three RADIUS
and LDAP servers using the drop-down lists.
Note The RADIUS and LDAP external servers must already be configured in order to be selectable options on the
WLANs > Edit (Security > AAA Servers) page. You can configure these servers on the RADIUS Authentication
Servers page and LDAP Servers page.
Step 8 Establish the priority in which the servers are contacted to perform web authentication as follows:
Note The default order is local, RADIUS,
LDAP.
1 Highlight the server type (local, RADIUS, or LDAP) that you want to be contacted first in the box next to the Up
and Down buttons.
2 Click Up and Down until the desired server type is at the top of the box.
3 Click the < arrow to move the server type to the priority box on the left.
4 Repeat these steps to assign priority to the other servers.
Assigning Login, Login Failure, and Logout Pages per WLAN (CLI)
Step 1 Determine the ID number of the WLAN to which you want to assign a web login, login failure, or logout page by entering
this command:
show wlan summary
Step 2 If you want wireless guest users to log into a customized web login, login failure, or logout page, enter these commands
to specify the filename of the web authentication page and the WLAN for which it should display:
• config wlan custom-web login-page page_name wlan_id—Defines a customized login page for a given WLAN.
• config wlan custom-web loginfailure-page page_name wlan_id—Defines a customized login failure page for a
given WLAN.
Note To use the controller’s default login failure page, enter the config wlan custom-web loginfailure-page
none wlan_id command.
• config wlan custom-web logout-page page_name wlan_id—Defines a customized logout page for a given WLAN.
Note To use the controller’s default logout page, enter the config wlan custom-web logout-page none wlan_id
command.
Step 3 Redirect wireless guess users to an external server before accessing the web login page by entering this command to
specify the URL of the external server:
config wlan custom-web ext-webauth-url ext_web_url wlan_id
Step 4 Define the order in which web authentication servers are contacted by entering this command:
config wlan security web-auth server-precedence wlan_id {local | ldap | radius} {local | ldap | radius} {local | ldap
| radius}
The default order of server web authentication is local, RADIUS and LDAP.
Note All external servers must be preconfigured on the controller. You can configure them on the RADIUS
Authentication Servers page and the LDAP Servers page.
Step 5 Define which web authentication page displays for a wireless guest user by entering this command:
config wlan custom-web webauth-type {internal | customized | external} wlan_id
where
• internal displays the default web login page for the controller. This is the default value.
• customized displays the custom web login page that was configured in Step 2.
Note You do not need to define the web authentication type in Step 5 for the login failure and logout pages as
they are always customized.
• external redirects users to the URL that was configured in Step 3.
Step 6 Use a WLAN-specific custom web configuration rather than a global custom web configuration by entering this command:
config wlan custom-web global disable wlan_id
Note If you enter the config wlan custom-web global enable wlan_id command, the custom web authentication
configuration at the global level is used.
Step 7 Save your changes by entering this command:
save config
Caution If the MAC address of a client that goes to sleep mode is spoofed, the fake device such as a laptop can be
authenticated.
Step 3 Click the Security tab and then click the Layer 3 tab.
Step 4 Select the Sleeping Client check box to enable authentication for sleeping clients.
Step 5 Enter the Sleeping Client Timeout, which is the duration for which the sleeping clients are to be remembered before
reauthentication becomes necessary.
The default timeout is 12 hours.
Note Although wired guest access is managed by anchor and foreign anchors when two controllers are deployed,
mobility is not supported for wired guest access clients. In this case, DHCP and web authentication for
the client are handled by the anchor controller.
Note You can specify the amount of bandwidth allocated to a wired guest user in the network by configuring
a QoS role and a bandwidth contract.
You can create a basic peer to peer WLAN ACL and apply it to the wired guest WLAN. This will not block
peer to peer traffic and the guest users can still communicate with each other.
Step 1 To create a dynamic interface for wired guest user access, choose Controller > Interfaces. The Interfaces page appears.
Step 2 Click New to open the Interfaces > New page.
Step 3 Enter a name and VLAN ID for the new interface.
Step 4 Click Apply to commit your changes.
Step 5 In the Port Number text box, enter a valid port number. You can enter a number between 0 and 25 (inclusive).
Step 6 Select the Guest LAN check box.
Step 7 Click Apply to commit your changes.
Step 8 To create a wired LAN for guest user access, choose WLANs.
Step 9 On the WLANs page, choose Create New from the drop-down list and click Go. The WLANs > New page appears.
Step 10 From the Type drop-down list, choose Guest LAN.
Step 11 In the Profile Name text box, enter a name that identifies the guest LAN. Do not use any spaces.
Step 12 From the WLAN ID drop-down list, choose the ID number for this guest LAN.
Note You can create up to five guest LANs, so the WLAN ID options are 1 through 5 (inclusive).
Step 20 If you choose the Web Passthrough option, an Email Input check box appears. Select this check box if you want users
to be prompted for their e-mail address when attempting to connect to the network.
Step 21 To override the global authentication configuration set on the Web Login page, select the Override Global Config check
box.
Step 22 When the Web Auth Type drop-down list appears, choose one of the following options to define the web authentication
pages for wired guest users:
• Internal—Displays the default web login page for the controller. This is the default value.
• Customized—Displays custom web login, login failure, and logout pages. If you choose this option, three separate
drop-down lists appear for login, login failure, and logout page selection. You do not need to define a customized
page for all three options. Choose None from the appropriate drop-down list if you do not want to display a
customized page for that option.
Note These optional login, login failure, and logout pages are downloaded to the controller as webauth.tar
files.
• External—Redirects users to an external server for authentication. If you choose this option, you must also enter
the URL of the external server in the URL text box.
You can choose specific RADIUS or LDAP servers to provide external authentication on the WLANs > Edit
(Security > AAA Servers) page. Additionally, you can define the priority in which the servers provide authentication.
Step 23 If you chose External as the web authentication type in Step 22, choose Security > AAA Servers and choose up to three
RADIUS and LDAP servers using the drop-down lists.
Note You can configure the Authentication and LDAP Server using both IPv4 and IPv6 addresses.
Note The RADIUS and LDAP external servers must already be configured in order to be selectable options on the
WLANs > Edit (Security > AAA Servers) page. You can configure these servers on the RADIUS Authentication
Servers page and LDAP Servers page.
Step 24 To establish the priority in which the servers are contacted to perform web authentication as follows:
Note The default order is local, RADIUS,
LDAP.
1 Highlight the server type (local, RADIUS, or LDAP) that you want to be contacted first in the box next to the Up
and Down buttons.
2 Click Up and Down until the desired server type is at the top of the box.
3 Click the < arrow to move the server type to the priority box on the left.
4 Repeat these steps to assign priority to the other servers.
Step 1 Create a dynamic interface (VLAN) for wired guest user access by entering this command:
config interface create interface_name vlan_id
Step 2 If link aggregation trunk is not configured, enter this command to map a physical port to the interface:
config interface port interface_name primary_port {secondary_port}
Step 3 Enable or disable the guest LAN VLAN by entering this command:
Step 4 Create a wired LAN for wired client traffic and associate it to an interface by entering this command:
config guest-lan create guest_lan_id interface_name
The guest LAN ID must be a value between 1 and 5 (inclusive).
Note To delete a wired guest LAN, enter the config guest-lan delete guest_lan_id command.
Step 5 Configure the wired guest VLAN’s ingress interface, which provides a path between the wired guest client and the
controller by way of the Layer 2 access switch by entering this command:
config guest-lan ingress-interface guest_lan_id interface_name
Step 6 Configure an egress interface to transmit wired guest traffic out of the controller by entering this command:
config guest-lan interface guest_lan_id interface_name
Note If the wired guest traffic is terminating on another controller, repeat Step 4 and Step 6 for the terminating (anchor)
controller and Step 1 through Step 5 for the originating (foreign) controller. Additionally, configure the config
mobility group anchor add {guest-lan guest_lan_id | wlan wlan_id} IP_address command for both controllers.
Step 7 Configure the security policy for the wired guest LAN by entering this command:
config guest-lan security {web-auth enable guest_lan_id | web-passthrough enable guest_lan_id}
Note Web authentication is the default
setting.
Step 8 Enable or disable a wired guest LAN by entering this command:
config guest-lan {enable | disable} guest_lan_id
Step 9 If you want wired guest users to log into a customized web login, login failure, or logout page, enter these commands
to specify the filename of the web authentication page and the guest LAN for which it should display:
• config guest-lan custom-web login-page page_name guest_lan_id—Defines a web login page.
• config guest-lan custom-web loginfailure-page page_name guest_lan_id—Defines a web login failure page.
Note To use the controller’s default login failure page, enter the config guest-lan custom-web loginfailure-page
none guest_lan_id command.
• config guest-lan custom-web logout-page page_name guest_lan_id—Defines a web logout page.
Note To use the controller’s default logout page, enter the config guest-lan custom-web logout-page none
guest_lan_id command.
Step 10 If you want wired guest users to be redirected to an external server before accessing the web login page, enter this
command to specify the URL of the external server:
config guest-lan custom-web ext-webauth-url ext_web_url guest_lan_id
Step 11 If you want to define the order in which local (controller) or external (RADIUS, LDAP) web authentication servers are
contacted, enter this command:
config wlan security web-auth server-precedence wlan_id {local | ldap | radius} {local | ldap | radius} {local | ldap
| radius}
The default order of server web authentication is local, RADIUS, LDAP.
Note All external servers must be preconfigured on the controller. You can configure them on the RADIUS
Authentication Servers page or the LDAP Servers page.
Step 12 Define the web login page for wired guest users by entering this command:
config guest-lan custom-web webauth-type {internal | customized | external} guest_lan_id
where
• internal displays the default web login page for the controller. This is the default value.
• customized displays the custom web pages (login, login failure, or logout) that were configured in Step 9.
• external redirects users to the URL that was configured in Step 10.
Step 13 Use a guest-LAN specific custom web configuration rather than a global custom web configuration by entering this
command:
config guest-lan custom-web global disable guest_lan_id
Note If you enter the config guest-lan custom-web global enable guest_lan_id command, the custom web
authentication configuration at the global level is used.
Step 14 Save your changes by entering this command:
save config
Note Information on the configured web authentication appears in both the show run-config and show running-config
commands.
Step 15 Display the customized web authentication settings for a specific guest LAN by entering this command:
show custom-web {all | guest-lan guest_lan_id}
Note If internal web authentication is configured, the Web Authentication Type displays as internal rather than external
(controller level) or customized (WLAN profile level).
Step 16 Display a summary of the local interfaces by entering this command:
show interface summary
Note The interface name of the wired guest LAN in this example is wired-guest and its VLAN ID is
236.
Display detailed interface information by entering this command:
show interface detailed interface_name
Step 17 Display the configuration of a specific wired guest LAN by entering this command:
show guest-lan guest_lan_id
Note Enter the show guest-lan summary command to see all wired guest LANs configured on the controller.
Step 18 Display the active wired guest LAN clients by entering this command:
show client summary guest-lan
Step 19 Display detailed information for a specific client by entering this command:
show client detail client_mac
In order to support the redirection of IPv6-only clients, the controller automatically creates an IPv6 virtual
address based on the IPv4 virtual address configured on the controller. The virtual IPv6 address follows the
convention of [::ffff:<virtual IPv4 address>]. For example, a virtual IP address of 192.0.2.1 would translate
into [::ffff:192.0.2.1]. For an IPv6 captive portal to be displayed, the user must request an IPv6 resolvable
DNS entry such as ipv6.google.com which returns a DNSv6 (AAAA) record.
Interpreting LEDs
System Messages
dtl_arp.c 480: Got an idle-timeout message The controller’s network processing unit (NPU) sends a timeout
from an unknown client xx:xx:xx:xx:xx:xx message to the central processing unit (CPU) indicating that a
particular client has timed out or aged out. This situation typically
occurs when the CPU has removed a wireless client from its
internal database but has not notified the NPU. Because the client
remains in the NPU database, it ages out on the network
processor and notifies the CPU. The CPU finds the client that
is not present in its database and then sends this message.
STATION_DISASSOCIATE The client may have intentionally terminated usage or may have
experienced a service disruption.
AP_MAX_ROGUE_COUNT_EXCEEDED The current number of active rogue access points has exceeded
system threshold.
MAX_ROGUE_COUNT_EXCEEDED The current number of active rogue access points has exceeded
system threshold.
MULTIPLE_USERS Another user with the same username has logged in.
• show process cpu—Shows how various tasks in the system are using the CPU at that instant in time.
This command is helpful in understanding if any single task is monopolizing the CPU and preventing
other tasks from being performed.
The Priority field shows two values: 1) the original priority of the task that was created by the actual
function call and 2) the priority of the task divided by a range of system priorities.
The CPU Use field shows the CPU usage of a particular task.
The Reaper field shows three values: 1) the amount of time for which the task is scheduled in user mode
operation, 2) the amount of time for which the task is scheduled in system mode operation, and 3) whether
the task is being watched by the reaper task monitor (indicated by a “T”). If the task is being watched
by the reaper task monitor, this field also shows the timeout value (in seconds) before which the task
needs to alert the task monitor.
Note If you want to see the total CPU usage as a percentage, enter the show cpu command.
• show process memory—Shows the allocation and deallocation of memory from various processes in
the system at that instant in time.
In the example above, the following fields provide information:
The Name field shows the tasks that the CPU is to perform.
The Priority field shows two values: 1) the original priority of the task that was created by the actual
function call and 2) the priority of the task divided by a range of system priorities.
The BytesInUse field shows the actual number of bytes used by dynamic memory allocation for a
particular task.
The BlocksInUse field shows the chunks of memory that are assigned to perform a particular task.
The Reaper field shows three values: 1) the amount of time for which the task is scheduled in user mode
operation, 2) the amount of time for which the task is scheduled in system mode operation, and 3) whether
the task is being watched by the reaper task monitor (indicated by a “T”). If the task is being watched
by the reaper task monitor, this field also shows the timeout value (in seconds) before which the task
needs to alert the task monitor.
• show tech-support—Shows an array of information related to the state of the system, including the
current configuration, last crash file, CPU utilization, and memory utilization.
• show run-config—Shows the complete configuration of the controller. To exclude access point
configuration settings, use the show run-config no-ap command.
Note If you want to see the passwords in clear text, enter the config passwd-cleartext enable command. To
execute this command, you must enter an admin password. This command is valid only for this particular
session. It is not saved following a reboot.
• show run-config commands—Shows the list of configured commands on the controller. This command
shows only values configured by the user. It does not show system-configured default values.
Step 1 Choose Management > Logs > Config. The Syslog Configuration page appears.
Step 2 In the Syslog Server IP Address (IPv4/IPv6) text box, enter the IPv4/IPv6 address of the server to which to send the
syslog messages and click Add. You can add up to three syslog servers to the controller. The list of syslog servers that
have already been added to the controller appears below this text box.
Note If you want to remove a syslog server from the controller, click Remove to the right of the desired server.
Step 3 To set the severity level for filtering syslog messages to the syslog servers, choose one of the following options from
the Syslog Level drop-down list:
• Emergencies = Severity level 0
If you set a syslog level, only those messages whose severity is equal to or less than that level are sent to the syslog
servers. For example, if you set the syslog level to Warnings (severity level 4), only those messages whose severity is
between 0 and 4 are sent to the syslog servers.
Step 4 To set the facility for outgoing syslog messages to the syslog servers, choose one of the following options from the
Syslog Facility drop-down list :
• Kernel = Facility level 0
• User Process = Facility level 1
• Mail = Facility level 2
• System Daemons = Facility level 3
• Authorization = Facility level 4
• Syslog = Facility level 5 (default value)
• Line Printer = Facility level 6
• USENET = Facility level 7
• Unix-to-Unix Copy = Facility level 8
• Cron = Facility level 9
• FTP Daemon = Facility level 11
• System Use 1 = Facility level 12
• System Use 2 = Facility level 13
• System Use 3 = Facility level 14
• System Use 4 = Facility level 15
• Local Use 0 = Facility level 16
• Local Use 2 = Facility level 17
• Local Use 3 = Facility level 18
• Local Use 4 = Facility level 19
• Local Use 5 = Facility level 20
• Local Use 5 = Facility level 21
If you set a logging level, only those messages whose severity is equal to or less than that level are logged by the controller.
For example, if you set the logging level to Warnings (severity level 4), only those messages whose severity is between
0 and 4 are logged.
Step 7 Select the File Info check box if you want the message logs to include information about the source file. The default
value is enabled.
Step 8 Select the Trace Info check box if you want the message logs to include traceback information. The default is disabled.
Step 9 Click Apply.
Step 10 Click Save Configuration.
Note To clear the current message logs from the controller, click Clear.
Step 1 Enable system logging and set the IP address of the syslog server to which to send the syslog messages by entering this
command:
config logging syslog host server_IP_address
You can add up to three syslog servers to the controller.
Note To remove a syslog server from the controller by entering this command: config logging syslog host
server_IP_address delete
Step 2 Set the severity level for filtering syslog messages to the syslog server by entering this command:
config logging syslog level severity_level
where severity_level is one of the following:
• emergencies = Severity level 0
• alerts = Severity level 1
• critical = Severity level 2
• errors = Severity level 3
• warnings = Severity level 4
• notifications = Severity level 5
• informational = Severity level 6
• debugging = Severity level 7
Note As an alternative, you can enter a number from 0 through 7 for the severity_level parameter.
Note If you set a syslog level, only those messages whose severity is equal to or less than that level are sent to the
syslog server. For example, if you set the syslog level to Warnings (severity level 4), only those messages whose
severity is between 0 and 4 are sent to the syslog server.
Step 3 Set the severity level for filtering syslog messages for a particular access point or for all access points by entering this
command:
config ap logging syslog level severity_level {Cisco_AP | all}
where severity_level is one of the following:
• emergencies = Severity level 0
• alerts = Severity level 1
• critical = Severity level 2
• errors = Severity level 3
• warnings = Severity level 4
• notifications = Severity level 5
• informational = Severity level 6
• debugging = Severity level 7
Note If you set a syslog level, only those messages whose severity is equal to or less than that level are sent to
the access point. For example, if you set the syslog level to Warnings (severity level 4), only those messages
whose severity is between 0 and 4 are sent to the access point.
Step 4 Set the facility for outgoing syslog messages to the syslog server by entering this command:
config logging syslog facility facility_code
where Cleint is one of the following:
• authorization = Authorization system. Facility level = 4.
• auth-private = Authorization system (private). Facility level = 10.
• cron = Cron/at facility. Facility level = 9.
• daemon = System daemons. Facility level = 3.
• ftp = FTP daemon. Facility level = 11.
• kern = Kernel. Facility level = 0.
• local0 = Local use. Facility level = 16.
• local1 = Local use. Facility level = 17.
• local2 = Local use. Facility level = 18.
• local3 = Local use. Facility level = 19.
• local4 = Local use. Facility level = 20.
• local5 = Local use. Facility level = 21.
• local6 = Local use. Facility level = 22.
• local7 = Local use. Facility level = 23.
• lpr = Line printer system. Facility level = 6.
• mail = Mail system. Facility level = 2.
• news = USENET news. Facility level = 7.
• sys12 = System use. Facility level = 12.
• sys13 = System use. Facility level = 13.
• sys14 = System use. Facility level = 14.
• sys15 = System use. Facility level = 15.
• syslog = The syslog itself. Facility level = 5.
• user = User process. Facility level = 1.
• uucp = Unix-to-Unix copy system. Facility level = 8.
Step 5 Configure the syslog facility for AP using the following command:
config logging syslog facility AP
where AP can be:
Step 6 Configure the syslog facility for Client using the following command:
config logging syslog facility Client
where Cleint can be:
• assocfail Dot11= association fail syslog for clients
• associate Dot11=association syslog for clients
• authentication=authentication success syslog for clients
• authfail Dot11=authentication fail syslog for clients
• deauthenticate Dot11=deauthentication syslog for clients
• disassociate Dot11=disassociation syslog for clients
• excluded Excluded=syslog for clients
Step 7 Set the severity level for logging messages to the controller buffer and console, enter these commands:
• config logging buffered severity_level
• config logging console severity_level
Note If you set a logging level, only those messages whose severity is equal to or less than that level are logged by
the controller. For example, if you set the logging level to Warnings (severity level 4), only those messages
whose severity is between 0 and 4 are logged.
Step 8 Save debug messages to the controller buffer, the controller console, or a syslog server by entering these commands:
• config logging debug buffered {enable | disable}
• config logging debug console {enable | disable}
• config logging debug syslog {enable | disable}
By default, the console command is enabled, and the buffered and syslog commands are disabled.
Step 9 To cause the controller to include information about the source file in the message logs or to prevent the controller from
displaying this information by entering this command:
config logging fileinfo {enable | disable}
The default value is enabled.
Step 10 Configure the controller to include process information in the message logs or to prevent the controller from displaying
this information by entering this command:
config logging procinfo {enable | disable}
The default value is disabled.
Step 11 Configure the controller to include traceback information in the message logs or to prevent the controller from displaying
this information by entering this command:
config logging traceinfo {enable | disable}
The default value is disabled.
Step 12 Enable or disable timestamps in log messages and debug messages by entering these commands:
• config service timestamps log {datetime | disable}
• config service timestamps debug {datetime | disable}
where
◦datetime = Messages are timestamped with the standard date and time. This is the default value.
◦disable = Messages are not timestamped.
To minimize the number of writes to the access point flash, the contents of the event log are written to the
event log file during normal reload and crash scenarios only.
• To delete the existing event log and create an empty event log file for a specific access point or for all
access points joined to the controller, enter this command:
clear ap-eventlog {specific Cisco_AP | all}
◦If you are uploading through the service port, the TFTP or FTP server must be on the same subnet
as the service port because the service port is not routable, or you must create static routes on the
controller.
◦If you are uploading through the distribution system network port, the TFTP or FTP server can be
on the same or a different subnet because the distribution system port is routable.
◦A third-party TFTP or FTP server cannot run on the same computer as Cisco Prime Infrastructure
because the Prime Infrastructure built-in TFTP or FTP server and the third-party TFTP or FTP
server require the same communication port.
Step 1 Choose Command > Upload File. The Upload File from Controller page appears.
Step 2 From the File Type drop-down list, choose one of the following:
• Event Log
• Message Log
• Trap Log
• Crash File
Step 3 From the Transfer Mode drop-down list, choose from the following options:
• TFTP
• FTP
• SFTP (available in the 7.4 and later releases)
Step 4 In the IP Address text box, enter the IP address of the server.
Step 5 In the File Path text box, enter the directory path of the log or crash file.
Step 6 In the File Name text box, enter the name of the log or crash file.
Step 7 If you chose FTP as the Transfer Mode, follow these steps:
1 In the Server Login Username text box, enter the FTP server login name.
2 In the Server Login Password text box, enter the FTP server login password.
3 In the Server Port Number text box, enter the port number of the FTP server. The default value for the server port
is 21.
Step 8 Click Upload to upload the log or crash file from the controller. A message appears indicating the status of the upload.
Step 1 To transfer the file from the controller to a server, enter this command:
transfer upload mode {tftp | ftp | sftp}
Step 4 If you are using an FTP server, also enter these commands:
• transfer upload username username
• transfer upload password password
• transfer upload port port
Note The default value for the port parameter is
21.
Step 6 When prompted to confirm the current settings and start the software upload, answer y.
Configuring the Controller to Automatically Upload Core Dumps to an FTP Server (GUI)
Step 1 Choose Management > Tech Support > Core Dump to open the Core Dump page.
Step 2 To enable the controller to generate a core dump file following a crash, select the Core Dump Transfer check box.
Step 3 To specify the type of server to which the core dump file is uploaded, choose FTP from the Transfer Mode drop-down
list.
Step 4 In the IP Address text box, enter the IP address of the FTP server.
Note The controller must be able to reach the FTP
server.
Step 5 In the File Name text box, enter the name that the controller uses to label the core dump file.
Step 6 In the User Name text box, enter the username for FTP login.
Step 7 In the Password text box, enter the password for FTP login.
Step 8 Click Apply to commit your changes.
Step 9 Click Save Configuration to save your changes.
Configuring the Controller to Automatically Upload Core Dumps to an FTP Server (CLI)
Step 1 To enable or disable the controller to generate a core dump file following a crash, enter this command:
config coredump {enable | disable}
Step 2 To specify the FTP server to which the core dump file is uploaded, enter this command:
config coredump ftp server_ip_address filename
where
• server_ip_address is the IP address of the FTP server to which the controller sends its core dump file.
Note The controller must be able to reach the FTP
server.
• filename is the name that the controller uses to label the core dump file.
Step 3 To specify the username and password for FTP login, enter this command:
config coredump username ftp_username password ftp_password
Step 4 To save your changes, enter this command:
save config
Step 5 To see a summary of the controller’s core dump file, enter this command:
show coredump summary
Example:
Information similar to the following appears:
Step 1 To see information about the core dump file in flash memory, enter this command:
show coredump summary
Information similar to the following appears:
Sw Version.................................... 6.0.83.0
Time Stamp.................................... Wed Feb 4 13:23:11 2009
File Size..................................... 9081788
File Name Suffix........................... filename.gz
Step 2 To transfer the file from the controller to a server, enter these commands:
• transfer upload mode {tftp | ftp | sftp}
• transfer upload datatype coredump
• transfer upload serverip server_ip_address
• transfer upload path server_path_to_file
• transfer upload filename filename
Note After the file is uploaded, it ends with a .gz suffix. If desired, you can upload the same core dump file
multiple times with different names to different servers.
Step 3 If you are using an FTP server, also enter these commands:
• transfer upload username username
transfer upload password password
• transfer upload port port
Note The default value for the port parameter is
21.
Step 5 When prompted to confirm the current settings and start the software upload, answer y.
You can use the controller GUI or CLI to upload the packet capture file from the controller. You can then use
Wireshark or another standard packet capture tool to view and analyze the contents of the file.
◦A third-party TFTP or FTP server cannot run on the same computer as Cisco Prime Infrastructure
because the Prime Infrastructure built-in TFTP or FTP server and the third-party TFTP or FTP
server require the same communication port.
Step 1 Choose Commands > Upload File to open the Upload File from Controller page.
Step 2 From the File Type drop-down list, choose Packet Capture.
Step 3 From the Transfer Mode drop-down list, choose from the following options:
• TFTP
• FTP
• SFTP (available in the 7.4 and later releases)
Step 4 In the IP Address text box, enter the IP address of the server.
Step 5 In the File Path text box, enter the directory path of the packet capture file.
Step 6 In the File Name text box, enter the name of the packet capture file. These files have a .pcap extension.
Step 7 If you are using an FTP server, follow these steps:
a) In the Server Login Username text box, enter the username to log into the FTP server.
b) In the Server Login Password text box, enter the password to log into the FTP server.
c) In the Server Port Number text box, enter the port number on the FTP server through which the upload occurs. The
default value is 21.
Step 8 Click Upload to upload the packet capture file from the controller. A message appears indicating the status of the upload.
Step 9 Use Wireshark or another standard packet capture tool to open the packet capture file and see the last 50 packets that
were received by the controller.
Step 8 Enter the transfer upload start command to see the updated settings and then answer y when prompted to confirm the
current settings and start the upload process.
Step 9 Use Wireshark or another standard packet capture tool to open the packet capture file and see the last 50 packets that
were received by the controller.
Caution The commands in this section can be disruptive to your system and should be run only when you are
advised to do so by the Cisco Technical Assistance Center (TAC).
Step 1 To enable or disable monitoring for memory errors and leaks, enter this command:
config memory monitor errors {enable | disable}
The default value is disabled.
Note Your changes are not saved across reboots. After the controller reboots, it uses the default setting for this feature.
Step 2 If you suspect that a memory leak has occurred, enter this command to configure the controller to perform an auto-leak
analysis between two memory thresholds (in kilobytes):
config memory monitor leaks low_thresh high_thresh
If the free memory is lower than the low_thresh threshold, the system crashes, generating a crash file. The default value
for this parameter is 10000 kilobytes, and you cannot set it below this value.
Set the high_thresh threshold to the current free memory level or higher so that the system enters auto-leak-analysis
mode. After the free memory reaches a level lower than the specified high_thresh threshold, the process of tracking and
freeing memory allocation begins. As a result, the debug memory events enable command shows all allocations and
frees, and the show memory monitor detail command starts to detect any suspected memory leaks. The default value
for this parameter is 30000 kilobytes.
Step 3 To see a summary of any discovered memory issues, enter this command:
show memory monitor
-------------------------------------------
Step 4 To see the details of any memory leaks or corruption, enter this command:
show memory monitor detail
Information similar to the following appears:
Step 5 If a memory leak occurs, enter this command to enable debugging of errors or events during memory allocation:
debug memory {errors | events} {enable | disable}
Note We recommend that you enable the diagnostic channel feature only for nonanchored SSIDs that use the
management interface. CCX Diagnostic feature has been tested only with clients having Cisco ADU card
Step 4 If you want to enable diagnostic channel troubleshooting on this WLAN, select the Diagnostic Channel check box.
Otherwise, leave this check box unselected, which is the default value.
Note You can use the CLI to initiate diagnostic tests on the
client.
Step 5 Click Apply to commit your changes.
Step 6 Click Save Configuration to save your changes.
Step 1 To enable diagnostic channel troubleshooting on a particular WLAN, enter this command:
config wlan diag-channel {enable | disable} wlan_id
Step 2 To verify that your change has been made, enter this command:
show wlan wlan_id
Information similar to the following appears:
WLAN Identifier.................................. 1
Profile Name..................................... employee1
Network Name (SSID).............................. employee
Status........................................... Disabled
MAC Filtering.................................... Disabled
Broadcast SSID................................... Enabled
AAA Policy Override.............................. Disabled
Number of Active Clients......................... 0
Exclusionlist Timeout............................ 60 seconds
Session Timeout.................................. Infinity
Interface........................................ virtual
WLAN ACL......................................... unconfigured
DHCP Server...................................... Default
DHCP Address Assignment Required................. Disabled
Quality of Service............................... Silver (best effort)
WMM.............................................. Disabled
CCX - AironetIe Support.......................... Enabled
CCX - Gratuitous ProbeResponse (GPR)............. Disabled
CCX - Diagnostics Channel Capability............. Enabled
...
Step 3 To send a request to the client to perform the DHCP test, enter this command:
config client ccx dhcp-test client_mac_address
Note This test does not require the client to use the diagnostic
channel.
Step 4 To send a request to the client to perform the default gateway ping test, enter this command:
config client ccx default-gw-ping client_mac_address
Note This test does not require the client to use the diagnostic
channel.
Step 5 To send a request to the client to perform the DNS server IP address ping test, enter this command:
Step 8 To send a request to the client to perform the 802.1X test, enter this command:
config client ccx test-dot1x client_mac_address profile_id bssid {802.11a | 802.11b | 802.11g} channel
Step 9 To send a request to the client to perform the profile redirect test, enter this command:
config client ccx test-profile client_mac_address profile_id
The profile_id should be from one of the client profiles for which client reporting is enabled.
Note Users are redirected back to the parent WLAN, not to any other profile. The only profile shown is the user’s
parent profile. Note however that parent WLAN profiles can have one child diagnostic WLAN.
Step 10 Use these commands if necessary to abort or clear a test:
• To send a request to the client to abort the current test, enter this command:
config client ccx test-abort client_mac_address
Only one test can be pending at a time, so this command aborts the current pending test.
• To clear the test results on the controller, enter this command:
config client ccx clear-results client_mac_address
Step 12 To see the status of the last test, enter this command:
show client ccx last-test-status client_mac_address
Information similar to the following appears for the default gateway ping test:
Dialog Token..................................... 15
Timeout.......................................... 15000 ms
Request Time..................................... 1329 seconds since system boot
Step 13 To see the status of the last test response, enter this command:
show client ccx last-response-status client_mac_address
Information similar to the following appears for the 802.1X authentication test:
Step 15 To see the relevant data frames captured by the client during the previous test, enter this command:
show client ccx frame-data client_mac_address
Information similar to the following appears:
LOG Frames:
Frame Number:.................................... 1
Last Frame Number:............................... 1120
Direction:....................................... 1
Timestamp:....................................... 0d 00h 50m 39s 863954us
Frame Length:.................................... 197
Frame Data:
00000000: 80 00 00 00 ff ff ff ff ff ff 00 12 44 bd bd b0 ............D...
00000010: 00 12 44 bd bd b0 f0 af 43 70 00 f2 82 01 00 00 ..D.....Cp......
00000020: 64 00 11 08 00 01 00 01 08 8c 12 98 24 b0 48 60 d...........$.H`
00000030: 6c 05 04 01 02 00 00 85 1e 00 00 89 00 0f 00 ff l...............
00000040: 03 19 00 41 50 32 33 2d 31 30 00 00 00 00 00 00 ...AP23-10......
00000050: 00 00 00 00 00 00 26 96 06 00 40 96 00 ff ff dd ......&...@.....
00000060: 18 00 50 f2 01 01 00 00 50 f2 05 01 00 00 50 f2 ..P.....P.....P.
00000070: 05 01 00 00 40 96 00 28 00 dd 06 00 40 96 01 01 ....@..(....@...
00000080: 00 dd 05 00 40 96 03 04 dd 16 00 40 96 04 00 02 ....@......@....
00000090: 07 a4 00 00 23 a4 00 00 42 43 00 00 62 32 00 00 ....#...BC..b2..
000000a0: dd 05 00 40 96 0b 01 dd 18 00 50 f2 02 01 01 82 [email protected].....
000000b0: 00 03 a4 00 00 27 a4 00 00 42 43 5e 00 62 32 2f .....'...BC^.b2/
LOG Frames:
Frame Number:.................................... 2
Last Frame Number:............................... 1120
Direction:....................................... 1
Timestamp:....................................... 0d 00h 50m 39s 878289us
Frame Length:.................................... 147
Frame Data:
00000000: 80 00 00 00 ff ff ff ff ff ff 00 0d ed c3 a0 22 ..............."
00000010: 00 0d ed c3 a0 22 00 bd 4d 50 a5 f7 78 08 00 00 ....."..MP..x...
00000020: 64 00 01 00 00 01 00 01 08 8c 12 98 24 b0 48 60 d...........$.H`
00000030: 6c 05 04 01 02 00 00 85 1e 00 00 84 00 0f 00 ff l...............
00000040: 03 19 00 72 6f 67 75 65 2d 74 65 73 74 31 00 00 ...rogue-test1..
00000050: 00 00 00 00 00 00 23 96 06 00 40 96 00 10 00 dd ......#...@.....
00000060: 06 00 40 96 01 01 00 dd 05 00 40 96 03 04 dd 05 ..@.......@.....
00000070: 00 40 96 0b 01 dd 18 00 50 f2 02 01 01 81 00 03 [email protected].......
00000080: a4 00 00 27 a4 00 00 42 43 5e 00 62 32 2f 00 d2 ...'...BC^.b2/..
00000090: b4 ab 84 ...
LOG Frames:
Frame Number:.................................... 3
Last Frame Number:............................... 1120
Direction:....................................... 1
Timestamp:....................................... 0d 00h 50m 39s 881513us
Frame Length:.................................... 189
Frame Data:
00000000: 80 00 00 00 ff ff ff ff ff ff 00 12 44 bd 80 30 ............D..0
00000010: 00 12 44 bd 80 30 60 f7 46 c0 8b 4b d1 05 00 00 ..D..0`.F..K....
00000020: 64 00 11 08 00 01 00 01 08 8c 12 98 24 b0 48 60 d...........$.H`
00000030: 6c 05 04 00 02 00 00 85 1e 00 00 89 00 0f 00 ff l...............
00000040: 03 19 00 41 50 34 30 2d 31 37 00 00 00 00 00 00 ...AP40-17......
00000050: 00 00 00 00 00 00 26 dd 18 00 50 f2 01 01 00 00 ......&...P.....
00000060: 50 f2 05 01 00 00 50 f2 05 01 00 00 40 96 00 28 P.....P.....@..(
00000070: 00 dd 06 00 40 96 01 01 00 dd 05 00 40 96 03 04 ....@.......@...
00000080: dd 16 00 40 96 04 00 05 07 a4 00 00 23 a4 00 00 ...@........#...
00000090: 42 43 00 00 62 32 00 00 dd 05 00 40 96 0b 01 dd BC..b2.....@....
000000a0: 18 00 50 f2 02 01 01 85 00 03 a4 00 00 27 a4 00 ..P..........'..
000000b0: 00 42 43 5e 00 62 32 2f 00 0b 9a 1d 6f .BC^.b2/....o
...
Step 1 To send a request to the client to send its profiles, enter this command:
Step 2 To send a request to the client to send its current operating parameters, enter this command:
config client ccx get-operating-parameters client_mac_address
Step 3 To send a request to the client to send the manufacturer’s information, enter this command:
config client ccx get-manufacturer-info client_mac_address
Step 4 To send a request to the client to send its capability information, enter this command:
config client ccx get-client-capability client_mac_address
The statistics report provides 802.1X and security information for the client. You can use the controller CLI
to send the event log and statistics request to any CCXv5 client any time after the client associates.
Information similar to the following appears for a log response with a log_type of rsna:
Information similar to the following appears for a log response with a log_type of syslog:
Measurement duration = 1
dot11TransmittedFragmentCount = 1
dot11MulticastTransmittedFrameCount = 2
dot11FailedCount = 3
dot11RetryCount = 4
dot11MultipleRetryCount = 5
dot11FrameDuplicateCount = 6
dot11RTSSuccessCount = 7
dot11RTSFailureCount = 8
dot11ACKFailureCount = 9
dot11ReceivedFragmentCount = 10
dot11MulticastReceivedFrameCount = 11
dot11FCSErrorCount = 12
dot11TransmittedFrameCount = 13
◦Source address
◦Ethernet type
◦VLAN ID
• IP header ACL
◦Source address
◦Destination address
◦Protocol
◦Source port (if applicable)
◦Destination port (if applicable)
At each level, you can define multiple ACLs. The first ACL that matches the packet is the one that is selected.
• debug packet logging acl ip rule_index action src dst proto src_port dst_port
where
◦proto is a numeric or any string recognized by getprotobyname(). The controller supports the following strings:
ip, icmp, igmp, ggp, ipencap, st, tcp, egp, pup, udp, hmp, xns-idp, rdp, iso-tp4, xtp, ddp, idpr-cmtp, rspf, vmtp,
ospf, ipip, and encap.
◦src_port is the UDP/TCP two-byte source port (for example, telnet, 23) or “any.” The controller accepts a
numeric or any string recognized by getservbyname(). The controller supports the following strings: tcpmux,
echo, discard, systat, daytime, netstat, qotd, msp, chargen, ftp-data, ftp, fsp, ssh, telnet, smtp, time, rlp,
nameserver, whois, re-mail-ck, domain, mtp, bootps, bootpc, tftp, gopher, rje, finger, www, link, kerberos,
supdup, hostnames, iso-tsap, csnet-ns, 3com-tsmux, rtelnet, pop-2, pop-3, sunrpc, auth, sftp, uucp-path, nntp,
ntp, netbios-ns, netbios-dgm, netbios-ssn, imap2, snmp, snmp-trap, cmip-man, cmip-agent, xdmcp, nextstep,
bgp, prospero, irc, smux, at-rtmp, at-nbp, at-echo, at-zis, qmtp, z3950, ipx, imap3, ulistserv, https, snpp, saft,
npmp-local, npmp-gui, and hmmp-ind.
◦dst_port is the UDP/TCP two-byte destination port (for example, telnet, 23) or “any.” The controller accepts
a numeric or any string recognized by getservbyname(). The controller supports the same strings as those for
the src_port.
• debug packet logging acl eoip-eth rule_index action dst src type vlan
• debug packet logging acl eoip-ip rule_index action src dst proto src_port dst_port
• debug packet logging acl lwapp-dot11 rule_index action dst src bssid snap_type
where
◦bssid is the Basic Service Set Identifier.
◦snap_type is the Ethernet type.
• debug packet logging acl lwapp-ip rule_index action src dst proto src_port dst_port
Note To remove all configured ACLs, enter this command: debug packet logging acl clear-all.
Step 2 To configure the format of the debug output, enter this command:
debug packet logging format {hex2pcap | text2pcap}
The debug facility supports two output formats: hex2pcap and text2pcap. The standard format used by IOS supports the
use of hex2pcap and can be decoded using an HTML front end. The text2pcap option is provided as an alternative so
that a sequence of packets can be decoded from the same console log file.
Step 3 To determine why packets might not be displayed, enter this command:
debug packet error {enable | disable}
Step 4 To display the status of packet debugging, enter this command:
show debug packet
Information similar to the following appears:
Status........................................... disabled
Number of packets to display..................... 25
Bytes/packet to display.......................... 0
Packet display format............................ text2pcap
Driver ACL:
[1]: disabled
[2]: disabled
[3]: disabled
[4]: disabled
[5]: disabled
[6]: disabled
Ethernet ACL:
[1]: disabled
[2]: disabled
[3]: disabled
[4]: disabled
[5]: disabled
[6]: disabled
IP ACL:
[1]: disabled
[2]: disabled
[3]: disabled
[4]: disabled
[5]: disabled
[6]: disabled
EoIP-Ethernet ACL:
[1]: disabled
[2]: disabled
[3]: disabled
[4]: disabled
[5]: disabled
[6]: disabled
EoIP-IP ACL:
[1]: disabled
[2]: disabled
[3]: disabled
[4]: disabled
[5]: disabled
[6]: disabled
LWAPP-Dot11 ACL:
[1]: disabled
[2]: disabled
[3]: disabled
[4]: disabled
[5]: disabled
[6]: disabled
LWAPP-IP ACL:
[1]: disabled
[2]: disabled
[3]: disabled
[4]: disabled
[5]: disabled
[6]: disabled?
• The latest version of Wireshark can decode the packets by going to the Analyze mode. Select decode
as, and switch UDP5555 to decode as PEEKREMOTE..
• You must disable IP-MAC address binding in order to use an access point in sniffer mode if the access
point is joined to a Cisco 5500 Series Controller. To disable IP-MAC address binding, enter the config
network ip-mac-binding disable command in the controller CLI.
• You must enable WLAN 1 in order to use an access point in sniffer mode if the access point is joined
to a Cisco 5500 Series Controller. If WLAN 1 is disabled, the access point cannot send packets.
Step 1 Choose Wireless > Access Points > All APs to open the All APs page.
Step 2 Click the name of the access point that you want to configure as the sniffer. The All APs > Details for page appears.
Step 3 From the AP Mode drop-down list, choose Sniffer.
Step 4 Click Apply.
Step 5 Click OK when prompted that the access point will be rebooted.
Step 6 Choose Wireless > Access Points > Radios > 802.11a/n/ac (or 802.11b/g/n) to open the 802.11a/n (or 802.11b/g/n)
Radios page.
Step 7 Hover your cursor over the blue drop-down arrow for the desired access point and choose Configure. The 802.11a/n/ac
(or 802.11b/g/n) Cisco APs > Configure page appears.
Step 8 Select the Sniff check box to enable sniffing on this access point, or leave it unselected to disable sniffing. The default
value is unchecked.
Step 9 If you enabled sniffing in Step 8, follow these steps:
a) From the Channel drop-down list, choose the channel on which the access point sniffs for packets.
b) In the Server IP Address text box, enter the IP address of the remote machine running Omnipeek, Airopeek,
AirMagnet, or Wireshark.
Step 10 Click Apply.
Step 11 Click Save Configuration.
Step 2 When warned that the access point will be rebooted and asked if you want to continue, enter Y. The access point reboots
in sniffer mode.
Step 3 Enable sniffing on the access point by entering this command:
config ap sniff {802.11a | 802.11b} enable channel server_IP_address Cisco_AP
where
• channel is the radio channel on which the access point sniffs for packets. The default values are 36 (802.11a/n/ac)
and 1 (802.11b/g/n).
• server_IP_address is the IP address of the remote machine running Omnipeek, Airopeek, AirMagnet, or Wireshark.
• Cisco_AP is the access point configured as the sniffer.
Note To disable sniffing on the access point, enter the config ap sniff {802.11a | 802.11b} disable Cisco_AP
command.
Step 5 See the sniffer configuration settings for an access point by entering this command:
show ap config {802.11a | 802.11b} Cisco_AP
clock, crypto, delete, fsck, lwapp, mkdir, radius, release, reload, rename, renew, rmdir, save, set,
test, upgrade.
• Commands available during a Telnet or SSH session include debug, disable, enable, help, led, login,
logout, more, no debug, show, systat, undebug and where.
Note For instructions on configuring Telnet or SSH SSH sessions on the controller, see the
Telnet and Secure Shell Sessions section.
Note For instructions on configuring Telnet or SSH sessions on the controller, see the Telnet
and Secure Shell Sessions section.
You can configure Telnet or SSH by using the controller CLI in software release 5.0 or later releases or using
the controller GUI in software release 6.0 or later releases.
Step 1 Choose Wireless > Access Points > All APs to open the All APs page.
Step 2 Click the name of the access point for which you want to enable Telnet or SSH.
Step 3 Choose the Advanced tab to open the All APs > Details for (Advanced) page.
Step 4 Select the Telnet check box to enable Telnet connectivity on this access point. The default value is unchecked.
Step 5 Select the SSH check box to enable SSH connectivity on this access point. The default value is unchecked.
Step 6 Click Apply.
Step 7 Click Save Configuration.
Step 1 Enable Telnet or SSH connectivity on an access point by entering this command:
config ap {telnet | ssh} enable Cisco_AP
The default value is disabled.
Note Disable Telnet or SSH connectivity on an access point by entering this command: config ap {telnet | ssh}
disable Cisco_AP
Step 2 Save your changes by entering this command:
save config
Step 3 See whether Telnet or SSH is enabled on an access point by entering this command:
show ap config general Cisco_AP
Information similar to the following appears:
Cisco AP Identifier.............................. 5
Cisco AP Name.................................... AP33
Country code..................................... Multiple Countries:US,AE,AR,AT,AU,BH
Reg. Domain allowed by Country................... 802.11bg:-ABCENR 802.11a:-ABCEN
AP Country code.................................. US - United States
AP Regulatory Domain............................. 802.11bg:-A 802.11a:-A
Switch Port Number .............................. 2
MAC Address...................................... 00:19:2f:11:16:7a
IP Address Configuration......................... Static IP assigned
IP Address....................................... 10.22.8.133
IP NetMask....................................... 255.255.248.0
Gateway IP Addr.................................. 10.22.8.1
Domain...........................................
Name Server......................................
Telnet State..................................... Enabled
Ssh State........................................ Enabled
...
Resolution: Ask the teleworker to perform a speed test and a ping test. Some servers do not return big
packet pings.
• Clients keep dropping data. This behavior usually occurs because the home router closes the port because
of short timeouts.
Resolution: Perform client troubleshooting in Cisco Prime Infrastructure to determine if the problem
is related to the OfficeExtend access point or the client.
• The access point is not broadcasting the enterprise WLAN.
Resolution: Ask the teleworker to check the cables, power supply, and LED status. If you still cannot
identify the problem, ask the teleworker to try the following:
◦Connect to the home router directly and see if the PC is able to connect to an Internet website such
as http://www.cisco.com/. If the PC cannot connect to the Internet, check the router or modem. If
the PC can connect to the Internet, check the home router configuration to see if a firewall or
MAC-based filter is enabled that is blocking the access point from reaching the Internet.
◦Log on to the home router and check to see if the access point has obtained an IP address. If it has,
the access point’s LED normally blinks orange.
• The access point cannot join the controller, and you cannot identify the problem.
Resolution: A problem could exist with the home router. Ask the teleworker to check the router manual
and try the following:
◦Assign the access point a static IP address based on the access point’s MAC address.
◦Put the access point in a demilitarized zone (DMZ), which is a small network inserted as a neutral
zone between a company’s private network and the outside public network. It prevents outside
users from getting direct access to a server that has company data.
◦If problems still occur, contact your company’s IT department for assistance.
• The teleworker experiences problems while configuring a personal SSID on the access point.
Resolution: Clear the access point configuration and return it to factory default settings by clicking
Clear Config on the access point GUI or by entering the clear ap config Cisco_AP command and then
configuring a personal SSID on an OfficeExtend Access Point. If problems still occur, contact your
company’s IT department for assistance.
• The home network needs to be rebooted.
Resolution: Ask the teleworker to follow these steps:
Leave all devices networked and connected, and then power down all the devices.
Turn on the cable or DSL modem, and then wait for 2 minutes. (Check the LED status.)
Turn on the home router, and then wait for 2 minutes. (Check the LED status.)
Turn on the access point, and then wait for 5 minutes. (Check the LED status.)
Turn on the client.
Figure 31: Ports on the Cisco 5500 Series Wireless LAN Controllers
3 Console port (RJ-45) 8 SFP distribution port Link and Activity LEDs
4 USB ports 0 and 1 (Type A) 9 Power supply (PS1 and PS2), System (SYS), and
Alarm (ALM) LEDs
Note The Gigabit Ethernet ports on the Cisco 5508 Controllers accept these SX/LC/T small
form-factor plug-in (SFP) modules: -
• 1000BASE-SX SFP modules, which provide a 1000-Mbps wired connection to a
network through an 850nM (SX) fiber-optic link using an LC physical connector
• 1000BASE-LX SFP modules, which provide a 1000-Mbps wired connection to a
network through a 1300nM (LX/LH) fiber-optic link using an LC physical
connector
• 1000BASE-T SFP modules, which provide a 1000-Mbps wired connection to a
network through a copper link using an RJ-45 physical connector
Note Some controllers support link aggregation (LAG), which bundles all of the controller’s
distribution system ports into a single 802.3ad port channel. Cisco 5500 Series Controllers
support LAG, and LAG is enabled automatically on the controllers within the Cisco
WiSM2.
• Cisco WLC configuration in access mode is not supported. We recommend that you configure Cisco
WLC in trunk mode when you configure Cisco WLC ports on a switch.
• In Cisco Flex 7500 and 8500 Series Controllers:
• If a port is unresponsive after a soaking period of 5 seconds, all the interfaces for which the port
is the primary and the active port, fail over to the backup port, if a backup is configured and is
operational. Similarly, if the unresponsive port is the backup port, then all the interfaces fail over
to the primary port if it is operational.
• After the unresponsive port is restored, there is a soaking period of 60 seconds after which if the
port is still operational, then all the interfaces fall back to this port, which was the primary port. If
the port was the backup port, then no change is done.
• You must ensure that you configure the port before you connect a switch or distribution system in
the Cisco Wireless LAN Controller 2500 series.
• If an IPv6 packet is destined to controller management IPv6 address and the client VLAN is different
from the controller management VLAN, then the IPv6 packet is switched out of the WLC box. If the
same IPv6 packet comes as a network packet to the WLC, management access is not denied.
Note The service port is not auto-sensing. You must use the correct straight-through or crossover Ethernet cable
to communicate with the service port.
Caution Do not configure wired clients in the same VLAN or subnet of the service port of the controller on the
network. If you configure wired clients on the same subnet or VLAN as the service port, it is not possible
to access the management interface of the controller.
Note You are not required to configure an AP-manager interface on Cisco 5500 Series
Controllers.
Note Typically, you define the management, AP-manager, virtual, and service-port interface parameters using
the Startup Wizard. However, you can display and configure interface parameters through either the GUI
or CLI after the controller is running.
When LAG is disabled, each interface is mapped to at least one primary port, and some interfaces (management
and dynamic) can be mapped to an optional secondary (or backup) port. If the primary port for an interface
fails, the interface automatically moves to the backup port. In addition, multiple interfaces can be mapped to
a single controller port.
In Cisco Wireless LAN Controller 5508 Series, the controller marks packets greater than 1500 bytes as long.
However, the packets are not dropped. The workaround to this is to configure the MTU on a switch to less
than 1500 bytes.
Note Interfaces that are quarantined are not displayed on the Controller > Interfaces page. For example, if there
are 6 interfaces and one of them is quarantined, the quarantined interface is not displayed and the details
of the other 5 interfaces are displayed on the GUI. You can get the total number of interfaces that is
inclusive of quarantined interfaces through the count displayed on the top-right corner of the GUI.
• Cisco 5500 Series Controllers do not support fragmented pings on any interface.
• When the port comes up in VMware ESXi with configuration for NIC teaming, the vWLC may lose
connectivity. However, the virtual wireless LAN controller (vWLC) resumes connectivity after a while.
Note If link aggregation (LAG) is enabled, there can be only one AP-manager interface.
Each controller port connection is an 802.1Q trunk and should be configured as such on the neighbor switch.
On Cisco switches, the native VLAN of an 802.1Q trunk is an untagged VLAN. If you configure an interface
to use the native VLAN on a neighboring Cisco switch, make sure you configure the interface on the controller
to be untagged.
Note A zero value for the VLAN identifier (on the Controller > Interfaces page) means that the interface is
untagged.
The default (untagged) native VLAN on Cisco switches is VLAN 1. When controller interfaces are configured
as tagged (meaning that the VLAN identifier is set to a nonzero value), the VLAN must be allowed on the
802.1Q trunk configuration on the neighbor switch and not be the native untagged VLAN.
We recommend that tagged VLANs be used on the controller. You should also allow only relevant VLANs
on the neighbor switch’s 802.1Q trunk connections to controller ports. All other VLANs should be disallowed
or pruned in the switch port trunk configuration. This practice is extremely important for optimal performance
of the controller.
Note We recommend that you assign one set of VLANs for WLANs and a different set of VLANs for
management interfaces to ensure that controllers properly route VLAN traffic.
Note To prevent or block a wired or wireless client from accessing the management network on a controller
(from the wireless client dynamic interface or VLAN), the network administrator must ensure that only
authorized clients gain access to the management network through proper CPU ACLs, or use a firewall
between the client dynamic interface and the management network.
Caution Do not map a guest WLAN to the management interface. If the EoIP tunnel breaks, the client could obtain
an IP and be placed on the management subnet.
Caution Do not configure wired clients in the same VLAN or subnet of the service port of the controller on the
network. If you configure wired clients on the same subnet or VLAN as the service port, it is not possible
to access the management interface of the controller.
Example
Follow these steps to configure Telnet:
1 Configure TACACS+ server by entering these commands:
a tacacs server server-name
b address ipv4 ip-address
c key key-name
Note These and all the other authentication and authorization parameters must be using the same database, be
it RADIUS, TACACS+, or Local. For example, if command authorization has to be enabled, it also needs
to be pointing to the same database.
Note • Do not configure any method-lists on the "line vty" configuration parameters. If the above steps and
the line vty have different configurations, then line vty configurations take precedence.
• The database should be the same across all management configuration types such as SSH/Telnet
and webui.
• You must explicitly define the method list for HTTP authentication.
Workaround
As a workaround, enter the following commands:
1 aaa authentication login default group server-group local
2 aaa authorization exec default group server-group local
Note Enter 0 for an untagged VLAN or a nonzero value for a tagged VLAN. We recommend using tagged
VLANs for the management interface.
• Configuring Management Interface using IPv4— Fixed IP address, IP netmask, and default gateway.
◦Configuring Management Interface using IPv6— Fixed IPv6 address, prefix-length (interface subnet mask
for IPv6) and the link local address of the IPv6 gateway router.
Note • In a setup where IPv6 is used, we recommend the APs to be at least one hop away from the Cisco
WLC. As the IPv6 packets are always sent to the Gateway, if the AP and WLC are in the same subnet,
it increases the packet hops and impacts the performance.
• Once the Primary IPv6 Address, Prefix Length, and Primary IPv6 Gateway are configured on the
management interface, they cannot be changed back to default values (:: /128).
• A configuration backup must be carried out before configuring IPv6 in case the user wants to revert
back to IPv4 only management interface.
• When more than 1300 IPv6 APs are in use, on a single Catalyst 6000 Switch, then assign APs on
multiple VLANs.
• In 8500 controller running a ha-pair,IPv6 primary gateway(link local) configured though 3600 AP
joined with the IPv6 address tears down the capwap. Using the command test capwap though the
AP joined with ipv6 address, it is seen that when the Link local address is not reachable capwap
should not be formed.
If APs are joined on V6 tunnel and if IPv6 gateway is misconfigured then v6 tunnel will not be teared
down. The APs will still be on v6 tunnel and will not fall back to v4 tunnel.
• Dynamic AP management (for Cisco 2500 Series Controllers or Cisco 5500 Series Controller only)
Note For Cisco 5500 Series Controllers, the management interface acts like an AP-manager interface by default.
If desired, you can disable the management interface as an AP-manager interface and create another
dynamic interface as an AP manager.
• Physical port assignment (for all controllers except the Cisco 2500 Series Controllers or Cisco 5500 Series Controller)
• Primary and secondary DHCP servers
• Access control list (ACL) setting, if required
Step 1 Enter the show interface detailed management command to view the current management interface settings.
Note The management interface uses the controller’s factory-set distribution system MAC address.
Step 2 Enter the config wlan disable wlan-number command to disable each WLAN that uses the management interface for
distribution system communication.
Step 3 Enter these commands to define the management interface:
a) Using IPv4 Address
• config interface address management ip-addr ip-netmask gateway
• config interface quarantine vlan management vlan_id
Note Use the config interface quarantine vlan management vlan_id command to configure a quarantine
VLAN on the management interface.
• config interface vlan management {vlan-id | 0}
Note Enter 0 for an untagged VLAN or a nonzero value for a tagged VLAN. We recommend using tagged
VLANs for the management interface.
• config interface ap-manager management {enable | disable} (for Cisco 5500 Series Controllers only)
Note Use the config interface ap-manager management {enable | disable} command to enable or disable
dynamic AP management for the management interface. For Cisco 5500 Series Controllers, the
management interface acts like an AP-manager interface by default. If desired, you can disable the
management interface as an AP-manager interface and create another dynamic interface as an AP
manager.
• config interface port management physical-ds-port-number (for all controllers except the 5500 series)
• config interface dhcp management ip-address-of-primary-dhcp-server [ip-address-of-secondary-dhcp-server]
• config interface acl management access-control-list-name
• config interface port management physical-ds-port-number (for all controllers except the 5500 series)
• config interface dhcp management ip-address-of-primary-dhcp-server [ip-address-of-secondary-dhcp-server]
• config ipv6 interface acl management access-control-list-name
Step 4 Enter these commands if you want to be able to deploy your Cisco 5500 Series Controller behind a router or other gateway
device that is using one-to-one mapping network address translation (NAT):
• config interface nat-address management {enable | disable}
• config interface nat-address management set public_IP_address
NAT allows a device, such as a router, to act as an agent between the Internet (public) and a local network (private). In
this case, it maps the controller’s intranet IP addresses to a corresponding external address. The controller’s dynamic
AP-manager interface must be configured with the external NAT IP address so that the controller can send the correct
IP address in the Discovery Response.
Note These commands are supported for use only with one-to-one-mapping NAT, where each private client has a
direct and fixed mapping to a global address. These commands do not support one-to-many NAT, which uses
source port mapping to enable a group of clients to be represented by a single IP address.
Step 5 Enter the save config command.
Step 6 Enter the show interface detailed management command to verify that your changes have been saved.
Step 7 If you made any changes to the management interface, enter the reset system command to reboot the controller in order
for the changes to take effect.
Note Release 8.2 does not support multiple non-AP Manager dynamic interfaces, untagged management
interfaces, management interfaces mapped to physical ports, and non-LAG scenarios.
Note A controller configured with IPv6 has only one AP-manager and is applicable on management interface.
You cannot remove the AP-manager configured on management interface.
The AP-manager IP address is used as the tunnel source for CAPWAP packets from the controller to the
access point and as the destination for CAPWAP packets from the access point to the controller.
Note The controller does not support transmitting the jumbo frames. To avoid having the controller transmit
CAPWAP packets to the AP that will necessitate fragmentation and reassembly, reduce MTU/MSS on
the client side.
The AP-manager interface communicates through any distribution system port by listening across the Layer
3 network for access point CAPWAP or LWAPP join messages to associate and communicate with as many
lightweight access points as possible.
A controller configured with IPv6 does not support Dynamic AP-Manager. By default, the management
interface acts like an AP-manager interface. Link Aggregation (LAG) is used for IPv6 AP load balancing.
Note When you enable LAG, all the ports would lose their AP Manager status and the AP
management reverts back onto the Management interface.
• Port redundancy for the AP-manager interface is not supported. You cannot map the AP-manager
interface to a backup port.
Note The gig/wired subinterface is numbered with VLAN number and dot11 subinterface is numbered with the
WLAN ID. The first configured WLAN becomes dot11 0.1 & dot11 1.1 and second WLAN ID subinterface
becomes dot11 0.2 & dot11 1.2 onwards. This dot11 sub interface number cannot be mapped with a VLAN
ID because multiple WLAN can be assigned with a same VLAN number. We cannot have duplicate
subinterface created in the system. The native subinterface configuration in wired interface is the AP native
VLAN configuration, if VLAN support is enabled in FlexConnect mode or else the native interface is
always gig prime interface in AP(Local / Flex with no VLAN support).
• Fixed IP address, IP netmask, and default gateway
• Primary and secondary DHCP servers
• Access control list (ACL) name, if required
Note A controller configured with IPv6 address does not support Dynamic AP-Manager. The management
interface acts like an AP-manager interface by default.
Step 1 Enter the show interface summary command to view the current interfaces.
Note If the system is operating in Layer 2 mode, the AP-manager interface is not
listed.
Step 2 Enter the show interface detailed ap-manager command to view the current AP-manager interface settings.
Step 3 Enter the config wlan disable wlan-number command to disable each WLAN that uses the AP-manager interface for
distribution system communication.
Step 4 Enter these commands to define the AP-manager interface:
• config interface address ap-manager ip-addr ip-netmask gateway
• config interface vlan ap-manager {vlan-id | 0}
Note Enter 0 for an untagged VLAN or a nonzero value for a tagged VLAN. We recommend using tagged
VLANs for the AP-manager interface.
• config interface port ap-manager physical-ds-port-number
• config interface dhcp ap-manager ip-address-of-primary-dhcp-server [ip-address-of-secondary-dhcp-server]
Note For IPv6 only—A controller configured with IPv6 address does not support Dynamic AP-Manager. By
default, the management interface acts like an AP-manager interface. Use LAG for IPv6 AP load balancing.
This figure shows a dynamic interface that is enabled as a dynamic AP-manager interface and associated to
port number 2.
Figure 33: Dynamic Interface Example with Dynamic AP Management
This figure shows a Cisco 5500 Series Controller with LAG disabled, the management interface used as one
dynamic AP-manager interface, and seven additional dynamic AP-manager interfaces, each mapped to a
different Gigabit port.
Figure 34: Cisco 5500 Series Controller Interface Configuration Example
The virtual interface IP address is used only in communications between the controller and wireless clients.
It never appears as the source or destination address of a packet that goes out a distribution system port and
onto the switched network. For the system to operate correctly, the virtual interface IP address must be set (it
cannot be 0.0.0.0), and no other device on the network can have the same address as the virtual interface.
Therefore, the virtual interface must be configured with an unassigned and unused gateway IP address. The
virtual interface IP address is not pingable and should not exist in any routing table in your network. In addition,
the virtual interface cannot be mapped to a physical port.
Note All controllers within a mobility group must be configured with the same virtual interface IP address.
Otherwise, inter-controller roaming may appear to work, but the handoff does not complete, and the client
loses connectivity for a period of time.
Step 1 Enter the show interface detailed virtual command to view the current virtual interface settings.
Step 2 Enter the config wlan disable wlan-number command to disable each WLAN that uses the virtual interface for distribution
system communication.
Step 3 Enter these commands to define the virtual interface:
• config interface address virtual ip-address
Note For ip-address, enter a valid, unassigned, and unused gateway IP address.
Step 4 Enter the reset system command. At the confirmation prompt, enter Y to save your configuration changes to NVRAM.
The controller reboots.
Step 5 Enter the show interface detailed virtual command to verify that your changes have been saved.
Note While IPv6 addressing is used along with stateless address auto-configuration, the controller does not
perform the subnet verification; however, you must not connect the service-port in the same subnet as the
other interfaces in the controller.
Note This is the only SLAAC interface on the controller, all other interfaces must be statically assigned (just
like for IPv4).
Note User does not require IPv6 static routes to reach service port from the same network, but IPv6 routes
requires to access service port from different network. The IPv6 static routes should be as same as IPv4.
Step 1 To view the current service-port interface settings, enter this command:
show interface detailed service-port
Note The service-port interface uses the controller’s factory-set service-port MAC address.
Step 3 The service port is used for out-of-band management of the controller. If the management workstation is in a remote
subnet, you may need to add a IPv4 route on the controller in order to manage the controller from that remote workstation.
To do so, enter this command:
config route add network-ip-addr ip-netmask gateway
Step 4 To remove the IPv4 route on the controller, enter this command:
config route delete ip_address
Step 1 To view the current service-port interface settings, enter this command:
show interface detailed service-port
Note The service-port interface uses the controller’s factory-set service-port MAC address.
Step 3 The service port is used for out-of-band management of the controller. If the management workstation is in a remote
subnet, you may need to add a route on the controller in order to manage the controller from that remote workstation.
To do so, enter this command:
config ipv6 route add network_ipv6_addr prefix-len ipv6_gw_addr
Step 4 To remove the IPv6 route on the controller, enter this command:
config ipv6 route delete network _ipv6 addr
Note You must not configure a dynamic interface in the same network as that of Local Mobility Anchor (LMA).
If you do so, the GRE tunnel between the controller and LMA does not come up.
• To modify the settings of an existing dynamic interface, click the name of the interface. The Interfaces > Edit
page for that interface appears. Go to Step 5.
• To delete an existing dynamic interface, hover your cursor over the blue drop-down arrow for the desired interface
and choose Remove.
Step 3 Enter an interface name and a VLAN identifier, as shown in the figure above.
Note You cannot enter ap-manager as the interface name while configuring a dynamic interface as ap-manager is a
reserved name.
Step 4 Click Apply to commit your changes. The Interfaces > Edit page appears.
Step 5 Configure the following parameters:
• Guest LAN, if applicable
• Quarantine and quarantine VLAN ID, if applicable
Note Select the Quarantine check box if you want to configure this VLAN as unhealthy or you want to configure
network access control (NAC) out-of-band integration. Doing so causes the data traffic of any client that
is assigned to this VLAN to pass through the controller.
• Physical port assignment (for all controllers except the 5500 series)
• NAT address (only for Cisco 5500 Series Controllers configured for dynamic AP management)
Note Select the Enable NAT Address check box and enter the external NAT IP address if you want to be able
to deploy your Cisco 5500 Series Controller behind a router or other gateway device that is using one-to-one
mapping network address translation (NAT). NAT allows a device, such as a router, to act as an agent
between the Internet (public) and a local network (private). In this case, it maps the controller’s intranet
IP addresses to a corresponding external address. The controller’s dynamic AP-manager interface must
be configured with the external NAT IP address so that the controller can send the correct IP address in
the Discovery Response.
Note The NAT parameters are supported for use only with one-to-one-mapping NAT, where each private client
has a direct and fixed mapping to a global address. The NAT parameters do not support one-to-many NAT,
which uses source port mapping to enable a group of clients to be represented by a single IP address.
• Dynamic AP management
Note When you enable this feature, this dynamic interface is configured as an AP-manager interface (only one
AP-manager interface is allowed per physical port). A dynamic interface that is marked as an AP-manager
interface cannot be used as a WLAN interface.
Note Set the APs in a VLAN that is different than the dynamic interface configured on the controller. If the APs
are in the same VLAN as the dynamic interface, the APs are not registered on the controller and the
“LWAPP discovery rejected” and “Layer 3 discovery request not received on management VLAN” errors
are logged on the controller.
• VLAN identifier
• Fixed IP address, IP netmask, and default gateway
Note Enter valid IP addresses in these
fields.
• Primary and secondary DHCP servers
• Access control list (ACL) name, if required
Note To ensure proper operation, you must set the Port Number and Primary DHCP Server parameters.
Step 1 Enter the show interface summary command to view the current dynamic interfaces.
Step 2 View the details of a specific dynamic interface by entering this command:
show interface detailed operator_defined_interface_name.
Note Interface names that contain spaces must be enclosed in double quotes. For example: config interface create
"vlan 25"
Step 3 Enter the config wlan disable wlan_id command to disable each WLAN that uses the dynamic interface for distribution
system communication.
Step 4 Enter these commands to configure dynamic interfaces:
• config interface create operator_defined_interface_name {vlan_id | x}
• config interface address interface ip_addr ip_netmask [gateway]
• config interface vlan operator_defined_interface_name {vlan_id | o}
• config interface port operator_defined_interface_name physical_ds_port_number
• config interface ap-manager operator_defined_interface_name {enable | disable}
Note Use the config interface ap-manager operator_defined_interface_name {enable | disable} command
to enable or disable dynamic AP management. When you enable this feature, this dynamic interface is
configured as an AP-manager interface (only one AP-manager interface is allowed per physical port). A
dynamic interface that is marked as an AP-manager interface cannot be used as a WLAN interface. You
cannot use ap-manager as the operator_defined_interface_name while configuring a dynamic interface
as ap-manager is a reserved name.
• config interface dhcp operator_defined_interface_name ip_address_of_primary_dhcp_server
[ip_address_of_secondary_dhcp_server]
• config interface quarantine vlan interface_name vlan_id
Note Use the config interface quarantine vlan interface_name vlan_id command to configure a quarantine
VLAN on any interface.
• config interface acl operator_defined_interface_name access_control_list_name
Step 5 Enter these commands if you want to be able to deploy your Cisco 5500 Series Controller behind a router or other gateway
device that is using one-to-one mapping network address translation (NAT):
• config interface nat-address dynamic-interface operator_defined_interface_name {enable | disable}
• config interface nat-address dynamic-interface operator_defined_interface_name set public_IP_address
NAT allows a device, such as a router, to act as an agent between the Internet (public) and a local network (private). In
this case, it maps the controller’s intranet IP addresses to a corresponding external address. The controller’s dynamic
AP-manager interface must be configured with the external NAT IP address so that the controller can send the correct
IP address in the Discovery Response.
Note These commands are supported for use only with one-to-one-mapping NAT, whereby each private client has a
direct and fixed mapping to a global address. These commands do not support one-to-many NAT, which uses
source port mapping to enable a group of clients to be represented by a single IP address.
Step 6 Enter the config wlan enable wlan_id command to reenable each WLAN that uses the dynamic interface for distribution
system communication.
Step 7 Enter the save config command to save your changes.
Step 8 Enter the show interface detailed operator_defined_interface_name command and show interface summary command
to verify that your changes have been saved.
Note If desired, you can enter the config interface delete operator_defined_interface_name command to delete a
dynamic interface.
• Link Trap—Whether the port is set to send a trap when the link status changes. Values: Enable or Disable
• Power over Ethernet (PoE)—If the connecting device is equipped to receive power through the Ethernet cable and
if so, provides –48 VDC. Values: Enable or Disable
Note Some older Cisco access points do not draw PoE even if it is enabled on the controller port. In such cases,
contact the Cisco Technical Assistance Center (TAC).
Note The 4-pin mini Type B connector is easily confused with the 5-pin mini Type B connector. They are not
compatible. Only the 5-pin mini Type B connector can be used.
For operation with Microsoft Windows, the Cisco Windows USB console driver must be installed on any
PC connected to the console port. With this driver, you can plug and unplug the USB cable into and from
the console port without affecting Windows HyperTerminal operations.
Note Only one console port can be active at a time. When a cable is plugged into the USB console port, the
RJ-45 port becomes inactive. Conversely, when the USB cable is removed from the USB port, the RJ-45
port becomes active.
Changing the Cisco USB Systems Management Console COM Port to an Unused
Port
Before You Begin
The USB driver is mapped to COM port 6. Some terminal emulation programs do not recognize a port higher
than COM 4. If necessary, you must change the Cisco USB systems management console COM port to an
unused port of COM 4 or lower.
Step 1 From your Windows desktop, right-click My Computer and choose Manage.
Step 2 From the list on the left side, choose Device Manager.
Step 3 From the device list on the right side, double-click Ports (COM & LPT).
Step 4 Right-click Cisco USB System Management Console 0108 and choose Properties.
Step 5 Click the Port Settings tab and click the Advanced button.
Step 6 From the COM Port Number drop-down list, choose an unused COM port of 4 or lower.
Step 7 Click OK to save and then close the Advanced Settings dialog box.
Step 8 Click OK to save and then close the Communications Port Properties dialog box.
• Terminating on two different modules within a single Catalyst 6500 series switch provides redundancy
and ensures that connectivity between the switch and the controller is maintained when one module
fails. The controller’s port 1 is connected to Gigabit interface 3/1, and the controller’s port 2 is connected
to Gigabit interface 2/1 on the Catalyst 6500 series switch. Both switch ports are assigned to the same
channel group.
• LAG requires the EtherChannel to be configured for 'mode on' on both the controller and the Catalyst
switch.
• Once the EtherChannel is configured as on at both ends of the link, the Catalyst switch should not be
configured for either Link Aggregation Control Protocol (LACP) or Cisco proprietary Port Aggregation
Protocol (PAgP) but be set unconditionally to LAG. Because no channel negotiation is done between
the controller and the switch, the controller does not answer to negotiation frames and the LAG is not
formed if a dynamic form of LAG is set on the switch. Additionally, LACP and PAgP are not supported
on the controller.
• If the recommended load-balancing method cannot be configured on the Catalyst switch, then configure
the LAG connection as a single member link or disable LAG on the controller.
Figure 35: Link Aggregation with the Catalyst 6500 Series Neighbor Switch
• You cannot configure the controller’s ports into separate LAG groups. Only one LAG group is supported
per controller. Therefore, you can connect a controller in LAG mode to only one neighbor device.
• When you enable LAG or make any changes to the LAG configuration, you must immediately reboot
the controller.
• When you enable LAG, you can configure only one AP-manager interface because only one logical port
is needed. LAG removes the requirement for supporting multiple AP-manager interfaces.
• When you enable LAG, all dynamic AP-manager interfaces and untagged interfaces are deleted, and all
WLANs are disabled and mapped to the management interface. Also, the management, static AP-manager,
and VLAN-tagged dynamic interfaces are moved to the LAG port.
• Multiple untagged interfaces to the same port are not allowed.
• When you enable LAG, you cannot create interfaces with a primary port other than 29.
• When you enable LAG, all ports participate in LAG by default. You must configure LAG for all of the
connected ports in the neighbor switch.
• When you enable LAG, if any single link goes down, traffic migrates to the other links.
• When you enable LAG, only one functional physical port is needed for the controller to pass client
traffic.
• When you enable LAG, access points remain connected to the controller until you reboot the controller,
which is needed to activate the LAG mode change, and data service for users continues uninterrupted.
• When you enable LAG, you eliminate the need to configure primary and secondary ports for each
interface.
• When you enable LAG, the controller sends packets out on the same port on which it received them. If
a CAPWAP packet from an access point enters the controller on physical port 1, the controller removes
the CAPWAP wrapper, processes the packet, and forwards it to the network on physical port 1. This
may not be the case if you disable LAG.
• When you disable LAG, the management, static AP-manager, and dynamic interfaces are moved to port
1.
• When you disable LAG, you must configure primary and secondary ports for all interfaces.
• When you disable LAG, you must assign an AP-manager interface to each port on the controller.
Otherwise, access points are unable to join.
• Cisco 5500 Series Controllers support a single static link aggregation bundle.
• LAG is typically configured using the Startup Wizard, but you can enable or disable it at any time through
either the GUI or CLI.
• When you enable LAG on Cisco 2500 Series Controller to which the direct-connect access point is
associated, the direct connect access point is disconnected since LAG enabling is still in the transition
state. You must reboot the controller immediately after enabling LAG.
• In 8500 when more than 1000 APs joining WLC flapping occurs, to avoid this do not add more than
1000 Aps on a single catalyst switch for Capwap IPv6.
LAG Enabled
• With LAG, all of the controller ports need to connect to the same neighbor switch. If the neighbor switch
goes down, the controller loses connectivity.
• With multiple AP-manager interfaces, you can connect your ports to different neighbor devices. If one
of the neighbor switches goes down, the controller still has connectivity. However, using multiple
AP-manager interfaces presents certain challenges when port redundancy is a concern.
Note Access points may not be distributed completely evenly across all of the AP-manager interfaces, but a
certain level of load balancing occurs.
• AP-manager interfaces do not need to be on the same VLAN or IP subnet, and they may or may not be
on the same VLAN or IP subnet as the management interface. However, we recommend that you configure
all AP-manager interfaces on the same VLAN or IP subnet.
• If the port of one of the AP-manager interfaces fails, the controller clears the state of the access points,
and the access points must reboot to reestablish communication with the controller using the normal
controller join process. The controller no longer includes the failed AP-manager interface in the CAPWAP
or LWAPP discovery responses. The access points then rejoin the controller and are load balanced among
the available AP-manager interfaces.
In the case of management interface, because there is support for backup port, APs already connected
to management interface continue to be in connected state (falling to backup port) rather than dropping
off. However, AP-Mgr will get disabled any new APs will associate with the current AP-Mgr.
Step 6 To make this interface an AP-manager interface, select the Enable Dynamic AP Management check box.
Note Only one AP-manager interface is allowed per physical port. A dynamic interface that is marked as an AP-manager
interface cannot be used as a WLAN interface.
Step 7 Click Save Configuration to save your settings.
Step 8 Repeat this procedure for each additional AP-manager interface that you want to create.
• While you configure VLAN-ACL mapping using the native VLAN identifier as part of Flex group
configuration, the ACL mapping does not take place. However, if you use the same VLAN to configure
ACL mapping at the access point level, the configuration is allowed.
Step 2 Click the name of the interface group to which you want to add interfaces.
The Interface Groups > Edit page appears.
Step 3 Choose the interface name that you want to add to this interface group from the Interface Name drop-down list.
Step 4 Click Add Interface to add the interface to the Interface group.
Step 5 Repeat Steps 2 and 3 if you want to add multiple interfaces to this interface group.
Note To remove an interface from the interface group, hover your mouse pointer over the blue drop-down arrow and
choose Remove.
Step 2 Click the WLAN ID of the WLAN to which you want to add the interface group.
Step 3 In the General tab, choose the interface group from the Interface/Interface Group (G) drop-down list.
Step 4 Click Apply.
Note Suppose that the interface group that you add to a WLAN has RADIUS Server Overwrite interface enabled. In
this case, when a client requests for authentication, the controller selects the first IP address from the interface
group as the RADIUS server.
This feature enables network administrators to configure guest anchor restrictions where a wireless guest user
at a foreign location can obtain an IP address from multiple subnets on the foreign location and controllers
from within the same anchor controller.
Controller marks VLAN as dirty when the clients are unable to receive IP address using DHCP. The VLAN
interface is marked as dirty based on two methods:
Aggressive Method—When only one failure is counted per association per client and controller marks VLAN
as dirty interface when a failure occurs three times for a client or for three different clients.
Non-Aggressive Method—When only one failure is counted per association per client and controller marks
VLAN as a dirty interface only when three or more clients fail.
• While you configure VLAN-ACL mapping using the native VLAN identifier as part of Flex group
configuration, the ACL mapping does not take place. However, if you use the same VLAN to configure
ACL mapping at the access point level, the configuration is allowed.
Step 2 Click the name of the interface group to which you want to add interfaces.
The Interface Groups > Edit page appears.
Step 3 Choose the interface name that you want to add to this interface group from the Interface Name drop-down list.
Step 4 Click Add Interface to add the interface to the Interface group.
Step 5 Repeat Steps 2 and 3 if you want to add multiple interfaces to this interface group.
Note To remove an interface from the interface group, hover your mouse pointer over the blue drop-down arrow and
choose Remove.
Step 2 Click the WLAN ID of the WLAN to which you want to add the interface group.
Step 3 In the General tab, choose the interface group from the Interface/Interface Group (G) drop-down list.
Step 4 Click Apply.
Note Suppose that the interface group that you add to a WLAN has RADIUS Server Overwrite interface enabled. In
this case, when a client requests for authentication, the controller selects the first IP address from the interface
group as the RADIUS server.
Step 1 Choose WLANs > WLAN ID. The WLAN > Edit page appears.
Step 2 In the General tab, select the Multicast VLAN feature check box to enable multicast VLAN for the WLAN.
The Multicast Interface drop-down list appears.
Step 3 Choose the VLAN from the Multicast Interface drop-down list.
Step 4 Click Apply.
state, are synchronized with the peer controller. The data structures of clients are synchronized based on the
client state. Clients that are in the transient state are dissociated after a switchover.
ACL and NAT IP configurations are synchronized to the HA standby controller when these parameters are
configured before HA pair-up. If the NAT IP is set on the management interface, the access point sets the AP
manager IP address as the NAT IP address. This issue is seen only when the NAT IP address and ACL are
set on the management interface before you enable high availability.
The following are some guidelines for high availability:
• We recommend that you do not pair two controllers of different hardware models. If they are paired,
the higher controller model becomes the active controller and the other controller goes into maintenance
mode.
• We recommend that you do not pair two controllers on different controller software releases. If they are
paired, the controller with the lower redundancy management address becomes the active controller and
the other controller goes into maintenance mode.
• All download file types, such as image, configuration, web-authentication bundle, and signature files–
are downloaded on the active controller first and then pushed to the standby-hot controller.
• Certificates should be downloaded separately on each controller before they are paired.
• You can upload file types such as configuration files, event logs, crash files, and so on, from the
standby-hot controller using the GUI or CLI of the active controller. You can also specify a suffix to
the filename to identify the uploaded file.
• To perform a peer upload, use the service port. In a management network, you can also use the redundancy
management interface (RMI) that is mapped to the redundancy port or RMI VLAN, or both, where the
RMI is the same as the management VLAN. Note that the RMI and the redundancy port should be in
two separate Layer2 VLANs, which is a mandatory configuration.
• If the controllers cannot reach each other through the redundant port and the RMI, the primary controller
becomes active and the standby-hot controller goes into the maintenance mode.
Note To achieve HA between two Cisco Wireless Services Module 2 (WiSM2) platforms,
the controllers should be deployed on a single chassis, or on multiple chassis using a
virtual switching system (VSS) and extending a redundancy VLAN between the multiple
chassis.
Note When the RMIs for two controllers that are a pair, and that are mapped to same VLAN
and connected to same Layer3 switch stop working, the standby controller is restarted.
Note The " mobilityHaMac is out of range" xml message is seen during the active/standby
second switch over in HA setup. This occurs if mobility HA mac field is more than 128.
• When HA is enabled, the standby controller always uses the Remote Method Invocation (RMI), and all
the other interfaces, dynamic and management, are invalid.
Note The RMI is meant to be used only for active and standby communications and not for
any other purpose.
• When HA is enabled, ensure that you do not use the backed-up image. If this image is used, the HA
feature might not work as expected:
• The service port and route information that is configured is lost after you enable SSO. You must
configure the service port and route information again after you enable SSO. You can configure
the service port and route information for the standby-hot controller using the peer-service-port
and peer-route commands.
• For Cisco WiSM2, service port reconfigurations are required after you enable redundancy.
Otherwise, Cisco WiSM2 might not be able to communicate with the supervisor. We recommend
that you enable DHCP on the service port before you enable redundancy.
• We recommend that you do not use the reset command on the standby-hot controller directly. If
you use this, unsaved configurations will be lost.
• We recommend that you enable link aggregation configuration on the controllers before you enable the
port channel in the infrastructure switches.
• All the configurations that require reboot of the active controller results in the reboot of the standby-hot
controller.
• The Ignore AP list is not synchronized from the active controller to the standby-hot controller. The list
is relearned through SNMP messages from Cisco Prime Infrastructure after the standby-hot controller
becomes active.
• Client SSO related guidelines:
• The standby controller maintains two client lists: one is a list of clients in the Run state and the
other is a list of transient clients in all the other states.
• Only the clients that are in the Run state are maintained during failover. Clients that are in transition,
such as roaming, 802.1X key regeneration, web authentication logout, and so on, are dissociated.
• As with AP SSO, Client SSO is supported only on WLANs. The controllers must be in the same
subnet. Layer3 connection is not supported.
• In Release 7.3.x, AP SSO is supported, but client SSO is not supported, which means that after an HA
setup that uses Release 7.3.x encounters a switchover, all the clients associated with the controller are
deauthenticated and forced to reassociate.
• You must manually configure the mobility MAC address on the then active controller post switchover,
when a peer controller has a controller software release that is prior to Release 7.2.
Redundancy Port
The redundancy port is used for configuration, operational data synchronization, and role negotiation between
the primary and secondary controllers.
The redundancy port checks for peer reachability by sending UDP keepalive messages every 100 milliseconds
(default frequency) from the standby-hot controller to the active controller. If a failure of the active controller
occurs, the redundancy port is used to notify the standby-hot controller.
If an NTP/SNTP server is not configured, the redundancy port performs a time synchronization from the
active controller to the standby-hot controller.
In Cisco WiSM2, the redundancy VLAN must be configured on the Cisco Catalyst 6000 Supervisor Engine
because there is no physical redundancy port available on Cisco WiSM2.
The redundancy port and the redundancy VLAN in Cisco WiSM2 are assigned an automatically generated
IP address in which the last two octets are obtained from the last two octets of the RMI. The first two octets
are always 169.254. For example, if the IP address of the RMI is 209.165.200.225, the IP address of the
redundancy port is 169.254.200.225.
The redundancy ports can connect over an L2 switch. Ensure that the redundancy port round-trip time is less
than 80 milliseconds if the keepalive timer is set to default, that is, 100 milliseconds, or 80 percent of the
keepalive timer if you have configured the keepalive timer in the range of 100 milliseconds to 400 milliseconds.
The failure detection time is calculated, for example, if the keepalive timer is set to 100 milliseconds, as
follows: 3 * 100 = 300 + 60 = 360 + jitter (12 milliseconds) = ~400 milliseconds. Also, ensure that the
bandwidth between redundancy ports is 60 Mbps or higher. Ensure that the maximum transmission unit (MTU)
is 1500 bytes or higher.
• In an HA environment using FlexConnect locally switched clients, the client information might not show
the username. To get details about the client, you must use the MAC address of the client. This restriction
does not apply to FlexConnect centrally switched clients or central (local) mode clients.
• It is not possible to access the Cisco WiSM2 GUI through the service interface when you have enabled
HA. The workaround is to create a service port interface again after HA is established.
• In an HA environment, an upgrade from an LDPE image to a non-LDPE image is not supported.
• It is not possible to pair two primary controllers or two secondary controllers.
• Standby controllers are unavailable on the APs connected switch port
• An HA-SKU controller with an evaluation license cannot become a standby controller. However, an
HA-SKU controller with zero license can become a standby controller.
• Service VLAN configuration is lost when moving from HA mode to non-HA mode and vice versa. You
should configure the service IP address manually again.
• The following scenario is not supported: The primary controller has the management address and the
redundancy management address in the same VLAN, and the secondary controller has the management
address in the same VLAN as the primary one, and the redundancy management address in a different
VLAN.
• The following is a list of some software upgrade scenarios:
• A software upgrade on the active controller ensures the upgrade of the standby-hot controller.
• An in-service upgrade is not supported. Therefore, you should plan your network downtime before
you upgrade the controllers in an HA environment.
• Rebooting the active controller after a software upgrade also reboots the standby-hot controller.
• If both active and standby-hot controllers have different software releases in the backup, and if
you enter the config boot backup command in the active controller, both the controllers reboot
with their respective backup images breaking the HA pair due to a software mismatch.
• A schedule reset applies to both the controllers in an HA environment. The peer controller reboots
a minute before the scheduled time expires on the active controller.
• You can reboot the standby-hot controller from the active controller by entering the reset
peer-system command if the scheduled reset is not planned. If you reset only the standby-hot
controller with this command, any unsaved configurations on the standby-hot controller is lost.
Therefore, ensure that you save the configurations on the active controller before you reset the
standby-hot controller.
• A preimage download is reinitiated if an SSO is triggered at the time of the image transfer.
• Only debug and show commands are allowed on the standby-hot controller.
• After a switchover, if a peer controller has a controller software release that is prior to Release 7.5,
all the mobility clients are deauthenticated.
• It is not possible to access the standby-hot controller through the controller GUI, Cisco Prime
Infrastructure, or Telnet. You can access the standby-hot controller only on its console.
• When a failover occurs, the standby controller must be in a standby-hot state and the redundant port in
a terminal state in SSO for successful switchover to occur.
• To enable or disable LAG, you must disable HA.
Note If LAG is disabled and both primary and backup ports are connected to the management
interface and if the primary port becomes nonoperational, a switchover might occur
because the default gateway is not reachable and backup port failover might exceed 12
seconds.
• When a failover occurs and the standby controller becomes the new active controller, it takes
approximately 15 to 20 minutes to synchronize the database (AP, client, and multicast) between the two
controllers. If another failover occurs during this time, the HA structures would not yet be synchronized.
Therefore, the APs and clients would have to get reassociated and reauthenticated respectively.
• Pairwise Master Key (PMK) cache synchronization is not supported on FlexConnect local-authenticated
clients.
• Client SSO restrictions:
• New mobility is not supported.
• Posture and network admission control out-of-band are not supported because the client is not in
the Run state.
• The following are not synchronized between the active and standby controller:
• Cisco Compatible Extension-based applications
• Client statistics
• Proxy Mobile IPv6, Application Visibility and Control, session initiation protocol (SIP), and
static call admission control (CAC) tree
• Workgroup bridges and the clients associated with them
• Clients that are associated with Cisco 600 Series OfficeExtend Access Points
• Passive clients
• Encryption is supported
• Encryption is supported only if the active and standby controllers communicate through the Redundancy
Management Interface on the management ports. Encryption is not supported if the redundancy port is
used for communication between the active and standby controllers.
• You cannot change the NAT address configuration of the management interface when the controllers
are in redundancy mode. To enable NAT address configuration on the management interface, you must
remove the redundancy configuration first, make the required changes on the primary controller, and
then reenable the redundancy configuration on the same controller.
• On Cisco WiSM2 and Cisco Catalyst 6500 Series Supervisor Engine 2T, if HA is enabled, post switchover,
the APs might disconnect and reassociate with the WiSM2 controller. To prevent this from occurring,
before you configure HA, we recommend that you verify, in the port channel, the details of both the
active and standby Cisco WiSM2 controllers that the ports are balanced in the same order and the port
channel hash distribution uses fixed algorithm. If they are not in order, you must change the port channel
distribution to be fixed and reset Cisco WiSM2 from the Cisco Catalyst 6500 Series Supervisor Engine
2T.
• After you enable SSO, you must access both the standby and active controller using:
Note While SSO is enabled, you can not access both the standby and active controller either
using the web UI/the telnet facility or using Cisco Prime Infrastructure/Prime NCS on
the service port.
• After the switch over of controller, clients along with children mesh access points (MAPs) are
disconnected and are rejoined with the new active controller. The entire mesh tree is rebuilt. The clients
of root access points (RAPs) are also disconnected but the RAPs are intact with the controller.
• Synchronization of bulk configurations is supported only for the configurations that are stored in XMLs.
Scheduled reboot is a configuration that is not stored in XMLs or Flash. Therefore, the scheduled reboot
configuration is not included in the synchronization of bulk configurations.
• When a switchover occurs, the controller does not synchronize the information on DHCP dirty bit from
the active to standby controller even when DHCP dirty bit is set on the active controller. After a
switchover, the controller populates the DHCP dirty bit based on the client DHCP retries.
• If you are using Cisco WiSM2, we recommend that you use the following release versions of Cisco IOS
on Cisco Catalyst 6500 Series Supervisor Engine 2T:
• 15.1(02)SY
• 15.1(01)ICB40.1
• 15.1(01)ICB29.36
• 15.1(01)ICB29.1
• 15.1(01)IC66.25
• 15.1(01)IB273.72
Step 1 On the GUI of both the controllers, choose Controller > Redundancy > Global Configuration.
The Global Configuration page is displayed.
Step 2 Enter the addresses of the controllers in the Redundant Management IP and the Peer Redundant Management IP
text boxes.
Note Ensure that the Redundant Management Interface IP address of one controller is the same as the Redundant
Management Interface IP address of the peer controller.
Step 3 From the Redundant Unit drop-down list, choose one of the controllers as primary and the other as secondary.
Step 4 On the GUI of both the controllers, set the SSO to Enabled state.
Note After you enable an SSO, the service port peer IP address and the service port netmask appear on the configuration
page. Note that the service port peer IP address and the netmask can be pushed to the peer only if the HA peer
is available and operational. When you enable high availability, you do not have to configure the service port
peer IP address and the service port netmask parameters. You must configure the parameters only when the HA
peer is available and operational. After you enable SSO, both the controllers are rebooted. During the reboot
process, the controllers negotiate the redundancy role through the redundant port based on the configuration.
The primary controller becomes the active controller and the secondary controller becomes the standby controller.
Step 5 (Optional) When the HA pair becomes available and operational, you can configure the peer service port IP address and
the netmask when the service port is configured as static. If you enable DHCP on the service port, you do not have to
configure these parameters on the Global Configuration page:
• Service Port Peer IP—IP address of the service port of the peer controller.
• Service Port Peer Netmask—Netmask of the service port of the peer controller.
• Mobility MAC Address—A common MAC address for the active and standby controllers that is used in the
mobility protocol. If an HA pair has to be added as a mobility member for a mobility group, the mobility MAC
address (instead of the system MAC address of the active or standby controller) should be used. Normally, the
mobility MAC address is chosen as the MAC address of the active controller and you do not have to manually
configure this.
• Keep Alive Timer—The timer that controls how often the standby controller sends keepalive messages to the
active controller. The valid range is between 100 to 1000 milliseconds.
• Peer Search Timer—The timer that controls how often the active controller sends peer search messages to the
standby controller. The valid range is between 60 to 300 seconds.
After you enable the high availability and pair the controllers, there is only one unified GUI to manage the HA pair
through the management port. GUI access through the service port is not feasible for both the active and standby
controllers. The standby controller can be managed only through the console or the service port.
Only Telnet and SSH sessions are allowed through the service port of the active and standby controllers.
Note Both controllers reboot and then negotiate the roles of active and standby-hot controllers.
• Configure the route configurations of the standby controller by entering this command:
config redundancy peer-route {add network-ip-addr ip-mask | delete network-ip-addr}
Note This command can be run only if the HA peer controller is available and operational.
• Configure the IP address and netmask of the peer service port of the standby controller by entering this
command:
config redundancy interface address peer-service-port ip-address netmask
This command can be run only if the HA peer controller is available and operational.
• Initiate a manual switchover by entering this command:
redundancy force-switchover
Note Execute this command only when you require a manual switchover.
Note Ensure that SSO is enabled to use these debug commands. Enter config redundancy mode SSO command
to enable SSO.
debug redundancy {infra | facilitator | transport | keepalive | gw-reachability | config-sync | ap-sync
| client-sync | mobility}
• infra—Configures debug of Redundancy Infra Module
• facilitator—Configures debug of Redundancy Facilitator Module
• transport—Configures debug of Redundancy Transport Module
• keepalive—Configures debug of Redundancy Keepalive Module
• gw-reachability—Configures debug of Redundancy Gw-reachability Module
• config-sync—Configures debug of Redundancy Config-Sync Module
• ap-sync—Configures debug of Redundancy AP-Sync Module
The Cisco OEAP-600 does not support VideoStream. All other access points support VideoStream.
h) Click Apply.
Step 3 Enable the media stream for multicast-direct by following these steps:
a) Choose WLANs > WLAN ID to open the WLANs > Edit page.
b) Click the QoS tab and select Gold (Video) from the Quality of Service (QoS) drop-down list.
c) Click Apply.
Step 4 Set the EDCA parameters to voice and video optimized (optional) by following these steps:
a) Choose Wireless > 802.11a/n/ac or 802.11b/g/n > EDCA Parameters.
b) From the EDCA Profile drop-down list, choose the Voice and Video Optimized option.
c) Click Apply.
Step 5 Enable the admission control on a band for video (optional) by following these steps:
Note Keep the voice bandwidth allocation to a minimum for better performance.
a) Choose Wireless > 802.11a/n/ac or 802.11b/g/n > Media to open the 802.11a/n (5 GHZ) or 802.11b/g/n > Media
page.
b) Click the Video tab.
c) Select the Admission Control (ACM) check box to enable bandwidth-based CAC for this radio band. The default
value is disabled.
d) Click Apply.
Step 6 Configure the video bandwidth by following these steps:
Note The template bandwidth that is configured for a media stream should be more than the bandwidth for the source
media stream.
Note The voice configuration is optional. Keep the voice bandwidth allocation to a minimum for better performance.
b) Choose Wireless > 802.11a/n/ac or 802.11b/g/n > Media to open the 802.11a/n/ac (5 GHZ) or 802.11b/g/n > Media
page.
c) Click the Video tab.
d) Select the Admission Control (ACM) check box to enable the video CAC for this radio band. The default value is
disabled.
e) In the Max RF Bandwidth field, enter the percentage of the maximum bandwidth allocated to clients for video
applications on this radio band. Once the client reaches the value specified, the access point rejects new requests on
this radio band.
f) The range is 5 to 85%.
g) The default value is 9%.
h) Click Apply.
i) Reenable all WMM WLANs and click Apply.
Step 7 Configure the media bandwidth by following these steps:
a) Choose Wireless > 802.11a/n/ac or 802.11b/g/n > Media to open the 802.11a (or 802.11b) > Media > Parameters
page.
b) Click the Media tab to open the Media page.
c) Select the Unicast Video Redirect check box to enable Unicast Video Redirect. The default value is disabled.
d) In the Maximum Media Bandwidth (0-85%) text box, enter the percentage of the maximum bandwidth to be
allocated for media applications on this radio band. Once the client reaches a specified value, the access point rejects
new calls on this radio band.
e) The default value is 85%; valid values are from 0% to 85%.
f) In the Client Minimum Phy Rate text box, enter the minimum transmission data rate to the client. If the transmission
data rate is below the phy rate, either the video will not start or the client may be classified as a bad client. The bad
client video can be demoted for better effort QoS or subject to denial.
g) In the Maximum Retry Percent (0-100%) text box, enter the percentage of maximum retries that are allowed. The
default value is 80. If it exceeds 80, either the video will not start or the client might be classified as a bad client. The
bad client video can be demoted for better effort QoS or subject to denial.
h) Select the Multicast Direct Enable check box to enable the Multicast Direct Enable field. The default value is
enabled.
i) From the Max Streams per Radio drop-down list, choose the maximum number of streams allowed per radio from
the range 0 to 20. The default value is set to No-limit. If you choose No-limit, there is no limit set for the number of
client subscriptions.
j) From the Max Streams per Client drop-down list, choose the maximum number of streams allowed per client from
the range 0 to 20. The default value is set to No-limit. If you choose No-limit, there is no limit set for the number of
client subscriptions.
k) Select the Best Effort QoS Admission check box to enable best-effort QoS admission.
l) Click Apply.
Step 8 Enable a WLAN by following these steps:
a) Choose WLANS > WLAN ID. The WLANs > Edit page appears.
b) Select the Status check box.
c) Click Apply.
Step 9 Enable the 802.11 a/n/ac or 802.11 b/g/n network by following these steps:
a) Choose Wireless > 802.11a/n/ac or 802.11b/g/n > Network.
b) Select the 802.11a or 802.11b/g Network Status check box to enable the network status.
c) Click Apply.
Step 10 Verify that the clients are associated with the multicast groups and group IDs by following these steps:
a) Choose Monitor > Clients. The Clients page appears.
b) Check if the 802.11a/n/ac or 802.11b/g/n network clients have the associated access points.
c) Choose Monitor > Multicast. The Multicast Groups page appears.
d) Select the MGID check box for the VideoStream to the clients.
e) Click MGID. The Multicast Group Detail page appears. Check the Multicast Status details.
Step 1 Configure the multicast-direct feature on WLANs media stream by entering this command:
config wlan media-stream multicast-direct {wlan_id | all} {enable | disable}
Step 7 Enable a specific enhanced distributed channel access (EDC) profile by entering this command:
config advanced{ 801.11a | 802.11b} edca-parameters optimized-video-voice
Step 8 Enable the admission control on the desired bandwidth by entering the following commands:
• Enable bandwidth-based voice CAC for 802.11a or 802.11b/g network by entering this command:
config {802.11a | 802.11b} cac voice acm enable
• Set the percentage of the maximum bandwidth allocated to clients for voice applications on the 802.11a or 802.11b/g
network by entering this command:
config {802.11a | 802.11b} cac voice max-bandwidth bandwidth
• Configure the percentage of the maximum allocated bandwidth reserved for roaming voice clients on the 802.11a
or 802.11b/g network by entering this command:
config {802.11a | 802.11b} cac voice roam-bandwidth bandwidth
Note For TSpec and SIP based CAC for video calls, only Static method is supported.
Step 9 Set the maximum number of streams per radio and/or per client by entering these commands:
• Set the maximum limit to the number multicast streams per radio by entering this command:
config {802.11a | 802.11b} media-stream multicast-direct radio-maximum [value | no-limit]
• Set the maximum number of multicast streams per client by entering this command:
config {802.11a | 802.11b} media-stream multicast-direct client-maximum [value | no-limit]
Security Overview
The Cisco Unified Wireless Network (UWN) security solution bundles potentially complicated Layer 1,
Layer 2, and Layer 3 802.11 Access Point security components into a simple policy manager that customizes
system-wide security policies on a per-WLAN basis. The Cisco UWN security solution provides simple,
unified, and systematic security management tools.
One of the biggest hurdles to WLAN deployment in the enterprise is WEP encryption, which is a weak
standalone encryption method. A newer problem is the availability of low-cost access points, which can be
connected to the enterprise network and used to mount man-in-the-middle and denial-of-service attacks.
Layer 1 Solutions
The Cisco UWN security solution ensures that all clients gain access within a user-set number of attempts. If
a client fails to gain access within that limit, it is automatically excluded (blocked from access) until the
user-set timer expires. The operating system can also disable SSID broadcasts on a per-WLAN basis.
Layer 2 Solutions
If a higher level of security and encryption is required, you can also implement industry-standard security
solutions such as Extensible Authentication Protocol (EAP), Wi-Fi Protected Access (WPA), and WPA2. The
Cisco UWN solution WPA implementation includes AES (Advanced Encryption Standard), TKIP and Michael
(temporal key integrity protocol and message integrity code checksum) dynamic keys, or WEP (Wired
Equivalent Privacy) static keys. Disabling is also used to automatically block Layer 2 access after a user-set
number of failed authentication attempts.
Regardless of the wireless security solution selected, all Layer 2 wired communications between controllers
and lightweight access points are secured by passing data through CAPWAP tunnels.
Layer 3 Solutions
The WEP problem can be further solved using industry-standard Layer 3 security solutions such as passthrough
VPNs (virtual private networks).
The Cisco UWN solution supports local and RADIUS MAC (media access control) filtering. This filtering
is best suited to smaller client groups with a known list of 802.11 access card MAC addresses.
The Cisco UWN solution supports local and RADIUS user/password authentication. This authentication is
best suited to small to medium client groups.
RADIUS uses User Datagram Protocol (UDP) for its transport. It maintains a database and listens on UDP
port 1812 for incoming authentication requests and UDP port 1813 for incoming accounting requests. The
controller, which requires access control, acts as the client and requests AAA services from the server. The
traffic between the controller and the server is encrypted by an algorithm defined in the protocol and a shared
secret key configured on both devices.
You can configure multiple RADIUS accounting and authentication servers. For example, you may want to
have one central RADIUS authentication server but several RADIUS accounting servers in different regions.
If you configure multiple servers of the same type and the first one fails or becomes unreachable, the controller
automatically tries the second one, then the third one if necessary, and so on.
When a management user is authenticated using a RADIUS server, only the PAP protocol is used. For web
authentication users, PAP, MSCHAPv2 and MD5 security mechanisms are supported.
RADIUS DNS
You can use a fully qualified domain name (FQDN) that enables you to change the IP address when needed,
for example, for load balancing updates. A submenu, DNS, is added to the Security > AAA > RADIUS menu,
which you can use to get RADIUS IP information from a DNS. The DNS query is disabled by default.
Note The pages used to configure authentication and accounting contain mostly the same text boxes. Therefore, these
instructions walk through the configuration only once, using the Authentication pages as examples. You would
follow the same steps to configure multiple services and/or multiple servers.
The RADIUS Authentication (or Accounting) Servers page appears.
This page lists any RADIUS servers that have already been configured.
• If you want to delete an existing server, hover your cursor over the blue drop-down arrow for that server and choose
Remove.
• If you want to make sure that the controller can reach a particular server, hover your cursor over the blue drop-down
arrow for that server and choose Ping.
Step 3 From the Acct Call Station ID Type drop-down list, choose the option that is sent to the RADIUS server in the
Access-Request message. The following options are available:
• IP Address
• System MAC Address
• AP MAC Address
• AP MAC Address:SSID
• AP Name:SSID
• AP Name
• AP Group
• Flex Group
• AP Location
• VLAN ID
• AP Ethernet MAC Address
• AP Ethernet MAC Address:SSID
Note The AP Name:SSID, AP Name, AP Group, Flex Group, AP Location, and VLAN ID options are added in the
7.4 release.
The AP Ethernet MAC Address and AP Ethernet MAC Address:SSID are added in the 7.6 release.
Step 4 From the Auth Call Station ID Type drop-down list, choose the option that is sent to the RADIUS server in the
Access-Request message. The following options are available:
• IP Address
• System MAC Address
• AP MAC Address
• AP MAC Address:SSID
• AP Name:SSID
• AP Name
• AP Group
• Flex Group
• AP Location
• VLAN ID
• AP Ethernet MAC Address
• AP Ethernet MAC Address:SSID
Step 5 Enable RADIUS-to-controller key transport using AES key wrap protection by checking the Use AES Key Wrap check
box. The default value is unchecked. This feature is required for FIPS customers.
Step 6 From the MAC Delimiter drop-down list, choose the option that is sent to the RADIUS server in the Access-Request
message. The following options are available:
• Colon
• Hyphen
• Single-hyphen
• None
Step 8 If you are adding a new server, choose a number from the Server Index (Priority) drop-down list to specify the priority
order of this server in relation to any other configured RADIUS servers providing the same service.
Step 9 If you are adding a new server, enter the IP address of the RADIUS server in the Server IP Address text box.
Note Auto IPv6 is not supported on RADIUS server. The RADIUS server must not be configured with Auto IPv6
address. Use fixed IPv6 address instead.
Step 10 From the Shared Secret Format drop-down list, choose ASCII or Hex to specify the format of the shared secret key
to be used between the controller and the RADIUS server. The default value is ASCII.
Step 11 In the Shared Secret and Confirm Shared Secret text boxes, enter the shared secret key to be used for authentication
between the controller and the server.
Note The shared secret key must be the same on both the server and the controller.
Step 12 If you are configuring a new RADIUS authentication server and want to enable AES key wrap, which makes the shared
secret between the controller and the RADIUS server more secure, follow these steps:
Note AES key wrap is designed for Federal Information Processing Standards (FIPS) customers and requires a
key-wrap compliant RADIUS authentication server.
a) Check the Key Wrap check box.
b) From the Key Wrap Format drop-down list, choose ASCII or HEX to specify the format of the AES key wrap
keys: Key Encryption Key (KEK) and Message Authentication Code Key (MACK).
c) In the Key Encryption Key (KEK) text box, enter the 16-byte KEK.
d) In the Message Authentication Code Key (MACK) text box, enter the 20-byte KEK.
Step 13 If you are adding a new server, enter the RADIUS server’s UDP port number for the interface protocols in the Port
Number text box. The valid range is 1 to 65535, and the default value is 1812 for authentication and 1813 for accounting.
Step 14 From the Server Status text box, choose Enabled to enable this RADIUS server or choose Disabled to disable it. The
default value is enabled.
Step 15 If you are configuring a new RADIUS authentication server, from the Support for RFC 3576 drop-down list, choose
Enabled to enable change of authorization, which is an extension to the RADIUS protocol that allows dynamic changes
to a user session, or choose Disabled to disable this feature. By default, this is set to Disabled state. Support for RFC
3576 includes support for disconnecting users and changing authorizations applicable to a user session and supports
disconnect and change of authorization (CoA) messages. Disconnect messages cause a user session to be terminated
immediately where CoA messages modify session authorization attributes such as data filters.
Step 16 In the Server Timeout text box, enter the number of seconds between retransmissions. The valid range is 2 to 30 seconds,
and the default value is 2 seconds.
Check the Key Wrap check box.
Note We recommend that you increase the timeout value if you experience repeated reauthentication attempts or the
controller falls back to the backup server when the primary server is active and reachable.
Step 17 Check the Network User check box to enable network user authentication (or accounting), or uncheck it to disable this
feature. The default value is unchecked. If you enable this feature, this entry is considered the RADIUS authentication
(or accounting) server for network users. If you did not configure a RADIUS server entry on the WLAN, you must enable
this option for network users.
Step 18 If you are configuring a RADIUS authentication server, check the Management check box to enable management
authentication, or uncheck the check box to disable this feature. The default value is checked. If you enable this feature,
this entry is considered the RADIUS authentication server for management users, and authentication requests go to the
RADIUS server.
Step 19 Enter the Management Retransmit Timeout value, which denotes the network login retransmission timeout for the
server.
Step 20 Check the IPSec check box to enable the IP security mechanism, or uncheck the check box to disable this feature. The
default value is unchecked.
Note IPSec is not supported for IPv6. Use this only if you have used IPv4 for Server IP Address.
Step 21 If you enabled IPsec in Step 17, follow these steps to configure additional IPsec parameters:
a) From the IPSec drop-down list, choose one of the following options as the authentication protocol to be used for IP
security: HMAC MD5 or HMAC SHA1. The default value is HMAC SHA1.
A message authentication code (MAC) is used between two parties that share a secret key to validate information
transmitted between them. HMAC (Hash MAC) is based on cryptographic hash functions. It can be used in combination
with any iterated cryptographic hash function. HMAC MD5 and HMAC SHA1 are two constructs of the HMAC
using the MD5 hash function and the SHA1 hash function. HMAC also uses a secret key for calculation and verification
of the message authentication values.
b) From the IPSec Encryption drop-down list, choose one of the following options to specify the IP security encryption
mechanism:
• DES—Data Encryption Standard that is a method of data encryption using a private (secret) key. DES applies
a 56-bit key to each 64-bit block of data.
• 3DES—Data Encryption Standard that applies three keys in succession. This is the default value.
• AES CBC—Advanced Encryption Standard that uses keys with a length of 128, 192, or 256 bits to encrypt
data blocks with a length of 128, 192, or 256 bits. AES 128 CBC uses a 128-bit data path in Cipher Block
Chaining (CBC) mode.
• 256-AES—Advanced Encryption Standard that uses keys with a length of 256 bits.
c) From the IKE Phase 1 drop-down list, choose one of the following options to specify the Internet Key Exchange
(IKE) protocol: Aggressive or Main. The default value is Aggressive.
IKE Phase 1 is used to negotiate how IKE should be protected. Aggressive mode passes more information in fewer
packets with the benefit of slightly faster connection establishment at the cost of transmitting the identities of the
security gateways in the clear.
d) In the Lifetime text box, enter a value (in seconds) to specify the timeout interval for the session. The valid range is
1800 to 57600 seconds, and the default value is 1800 seconds.
e) From the IKE Diffie Hellman Group drop-down list, choose one of the following options to specify the IKE Diffie
Hellman group: Group 1 (768 bits), Group 2 (1024 bits), or Group 5 (1536 bits). The default value is Group 1
(768 bits).
Diffie-Hellman techniques are used by two devices to generate a symmetric key through which they can publicly
exchange values and generate the same symmetric key. Although all three groups provide security from conventional
attacks, Group 5 is considered more secure because of its larger key size. However, computations involving Group
1 and Group 2 based keys might occur slightly faster because of their smaller prime number size.
Note If the shared secret for IPSec is not configured, the default radius shared secret is used. If the authentication
method is PSK, WLANCC should be enabled to use the IPSec shared secret, default value is used otherwise.
You can view the status for the WLANCC and UCAPL prerequisite modes in Controller > Inventory.
Step 22 Click Apply.
Step 23 Click Save Configuration.
Step 24 Repeat the previous steps if you want to configure any additional services on the same server or any additional RADIUS
servers.
Step 25 Specify the RADIUS server fallback behavior, as follows:
a) Choose Security > AAA > RADIUS > Fallback to open the RADIUS > Fallback Parameters to open the fallback
parameters page.
b) From the Fallback Mode drop-down list, choose one of the following options:
• Off—Disables RADIUS server fallback. This is the default value.
• Passive—Causes the controller to revert to a server with a lower priority from the available backup servers
without using extraneous probe messages. The controller ignores all inactive servers for a time period and retries
later when a RADIUS message needs to be sent.
• Active—Causes the controller to revert to a server with a lower priority from the available backup servers by
using RADIUS probe messages to proactively determine whether a server that has been marked inactive is back
online. The controller ignores all inactive servers for all active RADIUS requests. Once the primary server
receives a response from the recovered ACS server, the active fallback RADIUS server no longer sends probe
messages to the server requesting the active probe authentication.
c) If you enabled Active fallback mode in Step b, enter the name to be sent in the inactive server probes in the Username
text box. You can enter up to 16 alphanumeric characters. The default value is “cisco-probe.”
d) If you enabled Active fallback mode in Step b, enter the probe interval value (in seconds) in the Interval in Sec text
box. The interval serves as inactive time in passive mode and probe interval in active mode. The valid range is 180
to 3600 seconds, and the default value is 300 seconds.
Step 26 Specify the RADIUS DNS parameters as follows:
Note IPv6 is not supported for RADIUS
DNS.
a) Choose Security > AAA > RADIUS > DNS. The RADIUS DNS Parameters page appears.
b) Check or uncheck the DNS Query check box.
c) In the Port Number text box, enter the authentication port number. The valid range is 1 to 65535.
The accounting port number is an increment of 1 of the authentication port number. For example, if you define the
authentication port number as 1812, the accounting port number is 1813. The accounting port number is always
derived from the authentication port number.
d) From the Secret Format drop-down list, choose the format in which you want to configure the secret. Valid options
are ASCII and Hex.
e) Depending on the format selected, enter and confirm the secret.
Note All servers are expected to use the same authentication port and the same secret.
f) In the DNS Timeout text box, enter the number of days after which the DNS query is refreshed to get the latest
update from the DNS server.
g) In the URL text box, enter the fully qualified domain name or the absolute domain name of the RADIUS server.
h) In the Server IP Address text box, enter the IP address of the DNS server.
i) Click Apply.
Step 27 Specify the order of authentication when multiple databases are configured by choosing Security > Priority Order >
Management User. The Priority Order > Management User page appears.
Step 28 In the Order Used for Authentication text box, specify which servers have priority when the controller attempts to
authenticate management users. Use the > and < buttons to move servers between the Not Used and Order Used for
Authentication text boxes. After the desired servers appear in the Order Used for Authentication text box, use the Up
and Down buttons to move the priority server to the top of the list.
By default, the local database is always queried first. If the username is not found, the controller switches to the RADIUS
server if configured for RADIUS or to the TACACS+ server if configured for TACACS+. The default setting is local
and then RADIUS.
Related Topics
Configuring TACACS+ (GUI), on page 410
• Specify the delimiter to be used in the MAC addresses that are sent to the RADIUS authentication or
accounting server in Access-Request messages by entering this command:
config radius {auth | acct} mac-delimiter {colon | hyphen | single-hyphen | none}
where
• colon sets the delimiter to a colon (the format is xx:xx:xx:xx:xx:xx).
• hyphen sets the delimiter to a hyphen (the format is xx-xx-xx-xx-xx-xx). This is the default value.
• single-hyphen sets the delimiter to a single hyphen (the format is xxxxxx-xxxxxx).
• none disables delimiters (the format is xxxxxxxxxxxx).
• config radius auth rfc3576 {enable | disable} index—Enables or disables RFC 3576, which is
an extension to the RADIUS protocol that allows dynamic changes to a user session. RFC 3576
includes support for disconnecting users and changing authorizations applicable to a user session
and supports disconnect and change-of-authorization (CoA) messages. Disconnect messages cause
a user session to be terminated immediately where CoA messages modify session authorization
attributes such as data filters.
• config radius auth retransmit-timeout index timeout—Configures the retransmission timeout
value for a RADIUS authentication server.
• config radius auth mgmt-retransmit-timeout index timeout—Configures the default management
login retransmission timeout for a RADIUS authentication server.
• config radius auth network index {enable | disable}—Enables or disables network user
authentication. If you enable this feature, this entry is considered the RADIUS authentication server
for network users. If you did not configure a RADIUS server entry on the WLAN, you must enable
this option for network users.
• config radius auth management index {enable | disable}—Enables or disables management
authentication. If you enable this feature, this entry is considered the RADIUS authentication server
for management users, and authentication requests go to the RADIUS server.
• config radius auth ipsec {enable | disable} index—Enables or disables the IP security mechanism.
• config radius auth ipsec authentication {hmac-md5 | hmac-sha1} index—Configures the
authentication protocol to be used for IP security.
• config radius auth ipsec encryption {3des | aes | des | none} index—Configures the IP security
encryption mechanism.
• config radius auth ipsec ike dh-group {group-1 | group-2 | group-5| 2048bit-group-14}
index—Configures the IKE Diffie-Hellman group.
• config radius auth ipsec ike lifetime interval index—Configures the timeout interval for the
session.
• config radius auth ipsec ike phase1{aggressive | main} index—Configures the Internet Key
Exchange (IKE) protocol.
• config radius auth ipsec ike auth-method {PSK | certificate} index—Configures the IKE
authentication methods. By default PSK is be used for IPSEC sessions.
• config radius auth ipsec ike auth-mode pre-shared-key index hex/asciisecret—Configures the
IPSEC pre-shared key.
• config radius auth ipsec ike auth-mode {pre-shared-key index hex-ascii-index shared-secret |
certificate index} —Configures the IKE authentication method. By default, preshared key is used
for IPSEC sessions.
• config radius auth {enable | disable} index—Enables or disables a RADIUS authentication server.
• config radius auth delete index—Deletes a previously added RADIUS authentication server.
• config radius acct network index {enable | disable}—Enables or disables network user accounting.
If you enable this feature, this entry is considered the RADIUS accounting server for network
users. If you did not configure a RADIUS server entry on the WLAN, you must enable this option
for network users.
• config radius acct ipsec {enable | disable} index—Enables or disables the IP security mechanism.
• config radius acct ipsec authentication {hmac-md5 | hmac-sha1} index—Configures the
authentication protocol to be used for IP security.
• config radius acct ipsec encryption { 3des | aes | des | none} index—Configures the IP security
encryption mechanism.
• config radius acct ipsec ike dh-group {group-1 | group-2 | group-5} index—Configures the
IKE Diffie Hellman group.
• config radius acct ipsec ike lifetime interval index—Configures the timeout interval for the
session.
• config radius acct ipsec ike phase1{aggressive | main} index—Configures the Internet Key
Exchange (IKE) protocol.
• config radius acct {enable | disable} index—Enables or disables a RADIUS accounting server.
• config radius acct delete index—Deletes a previously added RADIUS accounting server.
• config radius auth callStationIdType {ap-ethmac-only | ap-ethmac-ssid}—Sets the Called
Station ID type to be AP’s radio MAC address or AP’s radio MAC address with SSID.
• config radius auth callStationIdType ap-label-address—Sets the Called Station ID Type to the
AP MAC address that is printed on the AP label, for the authentication messages.
config radius auth callStationIdType ap-label-address-ssid—Sets the Call Station ID Type to
the <AP label MAC address>:<SSID> format, for the authentication messages.
• config radius auth callStationIdType ap-group-name —Sets the Called Station ID type to use
the AP group name. If the AP is not part of any AP group, default-group is taken as the AP group
name.
• config radius auth callStationIdType ap-location—Sets the Called Station ID to the AP Location.
• config radius auth callStationIdType {ap-macaddr-only | ap-macaddr-ssid}—Sets the Called
Station ID type to be AP’s radio MAC address or AP’s radio MAC address with SSID in the <AP
radio MAC address>:<SSID> format.
• config radius auth callStationIdType {ap-name | ap-name-ssid}—Sets the Called Station ID
type to be AP name or AP name with SSID in the <AP name>:<SSID> format.
• config radius auth callStationIdType flex-group-name—Sets the Called Station ID type to the
FlexConnect group name.
• config radius auth callStationIdType {ipaddr | macaddr}—Sets the Called Station ID type to
use the IP address (only Layer 3) or system's MAC address.
• config radius auth callStationIdType vlan-id—Sets the Called Station ID type to the system's
VLAN ID.
where
• off disables RADIUS server fallback.
• passive causes the controller to revert to a server with a lower priority from the available backup
servers without using extraneous probe messages. The controller simply ignores all inactive servers
for a time period and retries later when a RADIUS message needs to be sent.
• active causes the controller to revert to a server with a lower priority from the available backup
servers by using RADIUS probe messages to proactively determine whether a server that has been
marked inactive is back online. The controller simply ignores all inactive servers for all active
RADIUS requests. Once the primary server receives a response from the recovered ACS server,
the active fallback RADIUS server no longer sends probe messages to the server requesting the
active probe authentication.
• If you enabled Active mode in Step 5, enter these commands to configure additional fallback parameters:
• config radius fallback-test username username—Specifies the name to be sent in the inactive
server probes. You can enter up to 16 alphanumeric characters for the username parameter.
• config radius fallback-test interval interval—Specifies the probe interval value (in seconds).
• Clear the statistics for one or more RADIUS servers by entering this command:
clear stats radius {auth | acct} {index | all}
• Make sure that the controller can reach the RADIUS server by entering this command:
ping server_ip_address
Related Topics
Configuring TACACS+ (CLI), on page 412
Attribute ID Description
1 User-Name
2 Password
3 CHAP-Password
4 NAS-IP-Address
5 NAS-Port
6 Service-Type4
12 Framed-MTU
30 Called-Station-ID (MAC address)
31 Calling-Station-ID (MAC address)
32 NAS-Identifier
33 Proxy-State
60 CHAP-Challenge
61 NAS-Port-Type
79 EAP-Message
4 To specify read-only or read-write access to controllers through RADIUS authentication, you must set the Service-Type attribute (6) on the RADIUS server
to Callback NAS Prompt for read-only access or to Administrative for read-write privileges.
Attribute ID Description
1 Cisco-LEAP-Session-Key
2 Cisco-Keywrap-Msg-Auth-Code
3 Cisco-Keywrap-NonCE
4 Cisco-Keywrap-Key
5 Cisco-URL-Redirect
6 Cisco-URL-Redirect-ACL
Note These Cisco-specific attributes are not supported: Auth-Algo-Type and SSID.
Attribute ID Description
6 Service-Type. To specify read-only or read-write access to controllers
through RADIUS authentication, you must set the Service-Type attribute
(6) on the RADIUS server to Callback NAS Prompt for read-only access
or to Administrative for read-write privileges.
8 Framed-IP-Address
25 Class
26 Vendor-Specific
27 Timeout
29 Termination-Action
40 Acct-Status-Type
64 Tunnel-Type
79 EAP-Message
81 Tunnel-Group-ID
Attribute ID Description
11 MS-CHAP-Challenge
16 MS-MPPE-Send-Key
17 MS-MPPE-Receive-Key
25 MS-MSCHAP2-Response
26 MS-MSCHAP2-Success
Attribute ID Description
1 VAP-ID
3 DSCP
4 8021P-Type
5 VLAN-Interface-Name
6 ACL-Name
7 Data-Bandwidth-Average-Contract
8 Real-Time-Bandwidth-Average-Contract
9 Data-Bandwidth-Burst-Contract
10 Real-Time-Bandwidth-Burst-Contract
11 Guest-Role-Name
13 Data-Bandwidth-Average-Contract-US
14 Real-Time-Bandwidth-Average-Contract-US
15 Data-Bandwidth-Burst-Contract-US
16 Real-Time-Bandwidth-Burst-Contract-US
VAP ID
This attribute indicates the WLAN ID of the WLAN to which the client should belong. When the WLAN-ID
attribute is present in the RADIUS Access Accept, the system applies the WLAN-ID (SSID) to the client
station after it authenticates. The WLAN ID is sent by the Cisco WLC in all instances of authentication except
IPsec. In case of web authentication, if the Cisco WLC receives a WLAN-ID attribute in the authentication
response from the AAA server, and it does not match the ID of the WLAN, authentication is rejected. The
802.1X/MAC filtering is also rejected. The rejection, based on the response from the AAA server, is because
of the SSID Cisco AVPair support. The fields are transmitted from left to right.
0 1 2 3
0 1 2 3 4 5 6 7 8 9 0 1 2 3 4 5 6 7 8 9 0 1 2 3 4 5 6 7 8 9 0 1
+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
| Type | Length | Vendor-Id
+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
Vendor-Id (cont.) | Vendor type | Vendor length |
+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
| WLAN ID (VALUE) |
+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
QoS-Level
This attribute indicates the QoS level to be applied to the mobile client's traffic within the switching fabric,
as well as over the air. This example shows a summary of the QoS-Level Attribute format. The fields are
transmitted from left to right.
0 1 2 3
0 1 2 3 4 5 6 7 8 9 0 1 2 3 4 5 6 7 8 9 0 1 2 3 4 5 6 7 8 9 0 1
+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
| Type | Length | Vendor-Id
+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
Vendor-Id (cont.) | Vendor type | Vendor length |
+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
| QoS Level |
+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
0 1 2 3
0 1 2 3 4 5 6 7 8 9 0 1 2 3 4 5 6 7 8 9 0 1 2 3 4 5 6 7 8 9 0 1
+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
| Type | Length | Vendor-Id
+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
Vendor-Id (cont.) | Vendor type | Vendor length |
+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
| DSCP (VALUE) |
+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
0 1 2 3
0 1 2 3 4 5 6 7 8 9 0 1 2 3 4 5 6 7 8 9 0 1 2 3 4 5 6 7 8 9 0 1
+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
| Type | Length | Vendor-Id
+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
Vendor-Id (cont.) | Vendor type | Vendor length |
+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
| 802.1p (VALUE) |
+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-
0 1 2 3
0 1 2 3 4 5 6 7 8 9 0 1 2 3 4 5 6 7 8 9 0 1 2 3 4 5 6 7 8 9 0 1
+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
| Type | Length | Vendor-Id
+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
Vendor-Id (cont.) | Vendor type | Vendor length |
+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
| Interface Name...
+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-
Note This attribute only works when MAC filtering is enabled or if 802.1X or WPA is used
as the security policy.
ACL-Name
This attribute indicates the ACL name to be applied to the client. A summary of the ACL-Name Attribute
format is shown below. The fields are transmitted from left to right.
0 1 2 3
0 1 2 3 4 5 6 7 8 9 0 1 2 3 4 5 6 7 8 9 0 1 2 3 4 5 6 7 8 9 0 1
+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
| Type | Length | Vendor-Id
+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
Vendor-Id (cont.) | Vendor type | Vendor length |
+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
| ACL Name...
+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-
0 1 2 3
0 1 2 3 4 5 6 7 8 9 0 1 2 3 4 5 6 7 8 9 0 1 2 3 4 5 6 7 8 9 0 1
+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
| Type | Length | Vendor-Id
+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
Vendor-Id (cont.) | Vendor type | Vendor length |
+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
| Data Bandwidth Average Contract...
+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-
0 1 2 3
0 1 2 3 4 5 6 7 8 9 0 1 2 3 4 5 6 7 8 9 0 1 2 3 4 5 6 7 8 9 0 1
+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
| Type | Length | Vendor-Id
+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
Vendor-Id (cont.) | Vendor type | Vendor length |
+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
| Real Time Bandwidth Average Contract...
+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-
0 1 2 3
0 1 2 3 4 5 6 7 8 9 0 1 2 3 4 5 6 7 8 9 0 1 2 3 4 5 6 7 8 9 0 1
+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
| Type | Length | Vendor-Id
+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
Vendor-Id (cont.) | Vendor type | Vendor length |
+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
| Data Bandwidth Burst Contract...
+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-
Note If you try to implement Average Data Rate and Burst Data Rate as AAA override parameters to be pushed
from a AAA server, both Average Data Rate and Burst Data Rate have to be sent from ISE.
0 1 2 3
0 1 2 3 4 5 6 7 8 9 0 1 2 3 4 5 6 7 8 9 0 1 2 3 4 5 6 7 8 9 0 1
+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
| Type | Length | Vendor-Id
+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
Vendor-Id (cont.) | Vendor type | Vendor length |
+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
| Real Time Bandwidth Burst Contract...
+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-
0 1 2 3
0 1 2 3 4 5 6 7 8 9 0 1 2 3 4 5 6 7 8 9 0 1 2 3 4 5 6 7 8 9 0 1
+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
| Type | Length | Vendor-Id
+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
Vendor-Id (cont.) | Vendor type | Vendor length |
+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
| GuestRoleName ...
+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-
Attribute ID Description
1 User-Name
4 NAS-IP-Address
5 NAS-Port
8 Framed-IP-Address
25 Class
30 Called-Station-ID (MAC address)
31 Calling-Station-ID (MAC address)
32 NAS-Identifier
40 Accounting-Status-Type
41 Accounting-Delay-Time (Stop and interim messages only)
42 Accounting-Input-Octets (Stop and interim messages only)
43 Accounting-Output-Octets (Stop and interim messages only)
Attribute ID Description
44 Accounting-Session-ID
45 Accounting-Authentic
46 Accounting-Session-Time (Stop and interim messages only)
47 Accounting-Input-Packets (Stop and interim messages only)
48 Accounting-Output-Packets (Stop and interim messages only)
49 Accounting-Terminate-Cause (Stop messages only)
52 Accounting-Input-Gigawords
53 Accounting-Output-Gigawords
55 Event-Timestamp
64 Tunnel-Type
65 Tunnel-Medium-Type
81 Tunnel-Group-ID
IPv6-Framed-Prefix
190 IPv6-Framed-Address
This table lists the different values for the Accounting-Status-Type attribute (40).
Attribute ID Description
1 Start
2 Stop
3 Interim-Update
Note RADIUS Accounting Interim updates are sent upon each client
authentication, even if the RADIUS Server Accounting - Interim
Update feature is not enabled on the client's WLAN.
7 Accounting-On
8 Accounting-Off
9-14 Reserved for Tunneling Accounting
15 Reserved for Failed
Note When multiple databases are configured, you can use the controller GUI or CLI to
specify the sequence in which the backend databases should be tried.
• Authorization—The process of determining the actions that users are allowed to take on the controller
based on their level of access.
For TACACS+, authorization is based on privilege (or role) rather than specific actions. The available
roles correspond to the seven menu options on the controller GUI: MONITOR, WLAN, CONTROLLER,
WIRELESS, SECURITY, MANAGEMENT, and COMMANDS. An additional role, LOBBY, is available
for users who require only lobby ambassador privileges. The roles to which users are assigned are
configured on the TACACS+ server. Users can be authorized for one or more roles. The minimum
authorization is MONITOR only, and the maximum is ALL, which authorizes the user to execute the
functionality associated with all seven menu options. For example, a user who is assigned the role of
SECURITY can make changes to any items appearing on the Security menu (or designated as security
commands in the case of the CLI). If users are not authorized for a particular role (such as WLAN), they
can still access that menu option in read-only mode (or the associated CLI show commands). If the
TACACS+ authorization server becomes unreachable or unable to authorize, users are unable to log
into the controller.
Note If users attempt to make changes on a controller GUI page that are not permitted for
their assigned role, a message appears indicating that they do not have sufficient privilege.
If users enter a controller CLI command that is not permitted for their assigned role, a
message may appear indicating that the command was successfully executed although
it was not. In this case, the following additional message appears to inform users that
they lack sufficient privileges to successfully execute the command: “Insufficient
Privilege! Cannot execute command!”
TACACS+ uses Transmission Control Protocol (TCP) for its transport, unlike RADIUS which uses User
Datagram Protocol (UDP). It maintains a database and listens on TCP port 49 for incoming requests. The
controller, which requires access control, acts as the client and requests AAA services from the server. The
traffic between the controller and the server is encrypted by an algorithm defined in the protocol and a shared
secret key configured on both devices.
You can configure up to three TACACS+ authentication, authorization, and accounting servers each. For
example, you may want to have one central TACACS+ authentication server but several TACACS+
authorization servers in different regions. If you configure multiple servers of the same type and the first one
fails or becomes unreachable, the controller automatically tries the second one and then the third one if
necessary.
Note If multiple TACACS+ servers are configured for redundancy, the user database must be identical in all
the servers for the backup to work properly.
single connection to the controller to function properly. The controller currently does not have any
intelligence or checks to correct a client that is trying to establish multiple connections.
• We recommend that you increase the retransmit timeout value for TACACS+ authentication, authorization,
and accounting servers if you experience repeated reauthentication attempts or the controller falls back
to the backup server when the primary server is active and reachable. The default retransmit timeout
value is 2 seconds and you can increase the retransmit timeout value to a maximum of 30 seconds.
• To configure the TACACS+ server:
• Using Access Control Server (ACS)—See the latest Cisco Secure Access Control System guide
at http://www.cisco.com/c/en/us/support/security/secure-access-control-system/
products-user-guide-list.html.
• Using Identity Services Engine (ISE)—See the ISE TACACS+ Configuration Guide for Wireless
LAN Controllers at http://www.cisco.com/c/dam/en/us/td/docs/security/ise/how_to/
HowTo-TACACS_for_WLC.pdf.
TACACS+ DNS
You can use a fully qualified domain name (FQDN) that enables you to change the IP address when needed,
for example, for load balancing updates. A submenu, DNS, is added to the Security > AAA > TACACS+
menu, which you can use to get TACACS+ IP information from a DNS. The DNS query is disabled by default.
It is not possible to use both the static list and the DNS list at the same time. The addresses returned by the
DNS override the static entries.
DNS AAA is valid for FlexConnect AP clients that use central authentication.
DNS AAA is not supported to define a RADIUS for FlexConnect AP groups. For FlexConnect clients with
local switching, you have to manually define AAA.
Rogue, 802.1X, web authentication, MAC filtering, mesh, and other features that use the global list also use
the DNS-defined servers.
TACACS+ VSA
The Internet Engineering Task Force (IETF) draft standard specifies a method for communicating
vendor-specific attributes (VSAs) between the network access server and the TACACS+ server. The IETF
uses attribute 26. VSAs allow vendors to support their own extended attributes that are not suitable for general
use.
The Cisco TACACS+ implementation supports one vendor-specific option using the format recommended
in the IETF specification. The Cisco vendor ID is 9, and the supported option is vendor type 1, which is named
cisco-av-pair. The value is a string with the following format:
Note The pages used to configure authentication, authorization, and accounting all contain the same text boxes.
Therefore, these instructions walk through the configuration only once, using the Authentication pages as
examples. You would follow the same steps to configure multiple services and/or multiple servers.
Note For basic management authentication via TACACS+ to succeed, it is required to configure authentication and
authorization servers on the WLC. Accounting configuration is optional.
The TACACS+ (Authentication, Authorization, or Accounting) Servers page appears. This page lists any TACACS+
servers that have already been configured.
• If you want to delete an existing server, hover your cursor over the blue drop-down arrow for that server and choose
Remove.
• If you want to make sure that the controller can reach a particular server, hover your cursor over the blue drop-down
arrow for that server and choose Ping.
Step 4 If you are adding a new server, choose a number from the Server Index (Priority) drop-down list to specify the priority
order of this server in relation to any other configured TACACS+ servers providing the same service. You can configure
up to three servers. If the controller cannot reach the first server, it tries the second one in the list and then the third if
necessary.
Step 5 If you are adding a new server, enter the IP address of the TACACS+ server in the Server IP Address text box.
Step 6 From the Shared Secret Format drop-down list, choose ASCII or Hex to specify the format of the shared secret key
to be used between the controller and the TACACS+ server. The default value is ASCII.
Step 7 In the Shared Secret and Confirm Shared Secret text boxes, enter the shared secret key to be used for authentication
between the controller and the server.
Note The shared secret key must be the same on both the server and the controller.
Step 8 If you are adding a new server, enter the TACACS+ server’s TCP port number for the interface protocols in the Port
Number text box. The valid range is 1 to 65535, and the default value is 49.
Step 9 In the Server Status text box, choose Enabled to enable this TACACS+ server or choose Disabled to disable it. The
default value is Enabled.
Step 10 In the Server Timeout text box, enter the number of seconds between retransmissions. The valid range is 5 to 30 seconds,
and the default value is 5 seconds.
Note We recommend that you increase the timeout value if you experience repeated reauthentication attempts or the
controller falls back to the backup server when the primary server is active and reachable.
Related Topics
Configuring RADIUS (GUI), on page 387
• Clear the statistics for one or more TACACS+ servers by entering this command:
clear stats tacacs [auth | athr | acct] {index | all}
• Configure the order of authentication when multiple databases are configured by entering this command.
The default setting is local and then radius.
config aaa auth mgmt [radius | tacacs]
See the current management authentication server order by entering the show aaa auth command.
• Make sure the controller can reach the TACACS+ server by entering this command:
ping server_ip_address
• Configure TACACS+ DNS parameters by entering these commands:
• config tacacs dns global port-num {ascii | hex} secret—Adds global port number and secret
information for the TACACS+ DNS.
• config tacacs dns query url timeout-in-days—Configures the FQDN of the TACACS+ server and
timeout after which a refresh is performed to get the latest update from the DNS server.
• config tacacs dns serverip ip-addr—Configures the IP address of the DNS server.
• config tacacs dns {enable | disable}—Enables or disables the DNS query.
Related Topics
Configuring RADIUS (CLI), on page 392
Step 1 On the ACS main page, in the left navigation pane, choose Reports and Activity.
Step 2 Under Reports, choose TACACS+ Administration.
Click the .csv file corresponding to the date of the logs you want to view. The TACACS+ Administration .csv page
appears.
Sometimes a single action (or command) is logged multiple times, once for each parameter in the command. For example,
if you enter the snmp community ipaddr ip_address subnet_mask community_name command, the IP address may be
logged on one line while the subnet mask and community name are logged as “E.” On another line, the subnet mask
maybe logged while the IP address and community name are logged as “E.” See the first and third lines in the example
in this figure.
Step 1 Choose Security > AAA > General to open the General page.
Step 2 In the Maximum Local Database Entries text box, enter a value for the maximum number of entries that can be added
to the local database the next time the controller reboots. The currently configured value appears in parentheses to the
right of the text box. The valid range is 512 to 2048, and the default setting is 2048.
The Number of Entries, Already Used text box shows the number of entries currently in the database.
Step 1 Specify the maximum number of entries that can be added to the local database the next time the controller reboots by
entering this command:
config database size max_entries
Step 3 View the maximum number of database entries and the current database contents by entering this command:
show database summary
Note The controller passes client information to the RADIUS authentication server first. If the client information
does not match a RADIUS database entry, the RADIUS authentication server replies with an authentication
failure message. If the RADIUS authentication server does not reply, then the local user database is queried.
Clients located in this database are granted access to network services if the RADIUS authentication fails
or does not exist.
Step 1 Choose Security > AAA > Local Net Users to open the Local Net Users page.
Note If you want to delete an existing user, hover your cursor over the blue drop-down arrow for that user and choose
Remove.
• To add a local network user, click New. The Local Net Users > New page appears.
Step 3 If you are adding a new user, enter a username for the local user in the User Name text box. You can enter up to 49
alphanumeric characters.
Note Local network usernames must be unique because they are all stored in the same database.
Step 4 In the Password and Confirm Password text boxes, enter a password for the local user. You can enter up to 49
alphanumeric characters.
Step 5 If you are adding a new user, select the Guest User check box if you want to limit the amount of time that the user has
access to the local network. The default setting is unselected.
Step 6 If you are adding a new user and you selected the Guest User check box, enter the amount of time (in seconds) that the
guest user account is to remain active in the Lifetime text box. The valid range is 60 to 2,592,000 seconds (30 days)
inclusive, and the default setting is 86,400 seconds.
Step 7 If you are adding a new user, you selected the Guest User check box, and you want to assign a QoS role to this guest
user, select the Guest User Role check box. The default setting is unselected.
Note If you do not assign a QoS role to a guest user, the bandwidth contracts for this user are defined in the QoS
profile for the WLAN.
Step 8 If you are adding a new user and you selected the Guest User Role check box, choose the QoS role that you want to
assign to this guest user from the Role drop-down list.
Step 9 From the WLAN Profile drop-down list, choose the name of the WLAN that is to be accessed by the local user. If you
choose Any WLAN, which is the default setting, the user can access any of the configured WLANs.
Step 10 In the Description text box, enter a descriptive title for the local user (such as “User 1”).
Step 11 Click Apply to commit your changes.
Step 12 Click Save Configuration to save your changes.
Note Instead of adding a permanent user or a guest user to the local user database from the controller, you can
choose to create an entry on the RADIUS server for the user and enable RADIUS authentication for the
WLAN on which web authentication is performed.
Note Local network usernames must be unique because they are all stored in the same database.
• See information related to the local network users configured on the controller by entering these
commands:
◦show netuser detail username—Shows the configuration of a particular user in the local user
database.
◦show netuser summary—Lists all the users in the local user database.
Step 1 Choose Security > AAA > Password Policies to open the Password Policies page.
Step 2 Select the Password must contain characters from at least 3 different classes check box if you want your password
to contain characters from at least three of the following classes: lower case letters, upper case letters, digits, and special
characters.
Step 3 Select the No character can be repeated more than 3 times consecutively check box if you do not want character in
the new password to repeat more than three times consecutively.
Step 4 Select the Password cannot be the default words like cisco, admin check box if you do not want the password to
contain words such as Cisco, ocsic, admin, nimda, or any variant obtained by changing the capitalization of letters or by
substituting 1, |, or! or substituting 0 for o or substituting $ for s.
Step 5 Select the Password cannot contain username or reverse of username check box if you do not want the password to
contain a username or the reverse letters of a username.
Step 6 Click Apply to commit your changes.
Step 7 Click Save Configuration to save your changes.
• Configure minimum number of upper, lower, digit, and special characters in a password by entering this
command:
config switchconfig strong-pwd minimum {upper-case | lower-case | digits | special-chars}
num-of-chars
• Configure minimum length for a password by entering this command:
config switchconfig strong-pwd min-length pwd-length
• Configure lockout for management or SNMPv3 users by entering this command:
config switchconfig strong-pwd lockout {mgmtuser | snmpv3user} {enable | disable}
• Configure lockout time for management or SNMPv3 users by entering this command:
config switchconfig strong-pwd lockout time {mgmtuser | snmpv3user} timeout-in-mins
• Configure the number of consecutive failure attempts for management or SNMPv3 users by entering
this command:
config switchconfig strong-pwd lockout attempts {mgmtuser | snmpv3user} num-of-failure-attempts
• Configure lifetime for management or SNMPv3 users by entering this command:
config switchconfig strong-pwd lifetime {mgmtuser | snmpv3user} lifetime-in-days
• See the configured options for strong password check by entering this command:
show switchconfig
Information similar to the following appears:
case-check ...........Enabled
consecutive-check ....Enabled
default-check .......Enabled
username-check ......Enabled
Note From Release 8.0, IPv6 can also be used to configure the LDAP server on the controller.
Step 1 Choose Security > AAA > LDAP to open the LDAP Servers page.
• If you want to delete an existing LDAP server, hover your cursor over the blue drop-down arrow for that server
and choose Remove.
• If you want to make sure that the controller can reach a particular server, hover your cursor over the blue drop-down
arrow for that server and choose Ping.
Step 3 If you are adding a new server, enter the IP address of the LDAP server in the Server IP Address text box.
Note From Release 8.0, IPv6 can also be used to configure the LDAP server on the controller.
Step 4 If you are adding a new server, enter the LDAP server’s TCP port number in the Port Number text box. The valid range
is 1 to 65535, and the default value is 389.
Note Only LDAP port 389 is supported on Cisco WLC. No other ports are supported for LDAP.
Step 5 From the Server Mode (via TLS) drop-down list, choose Disabled to establish LDAP connection (without secure tunnel)
between LDAP server and the Cisco WLC using TCP or Enabled to establish a secure LDAP connection using TLS.
Step 6 Select the Enable Server Status check box to enable this LDAP server or unselect it to disable it. The default value is
disabled.
Step 7 From the Simple Bind drop-down list, choose Anonymous or Authenticated to specify the local authentication bind
method for the LDAP server. The Anonymous method allows anonymous access to the LDAP server. The Authenticated
method requires that a username and password be entered to secure access. The default value is Anonymous.
Step 8 If you chose Authenticated in the previous step, follow these steps:
a) In the Bind Username text box, enter a username to be used for local authentication to the LDAP server. The username
can contain up to 80 characters.
Note If the username starts with “cn=” (in lowercase letters), the controller assumes that the username includes
the entire LDAP database path and does not append the user base DN. This designation allows the
authenticated bind user to be outside the user base DN.
b) In the Bind Username text box, enter a username to be used for local authentication to the LDAP server. The username
can contain up to 80 characters.
Step 9 In the User Base DN text box, enter the distinguished name (DN) of the subtree in the LDAP server that contains a list
of all the users. For example, ou=organizational unit, .ou=next organizational unit, and o=corporation.com. If the tree
containing users is the base DN, type.
o=corporation.com
or
dc=corporation,dc=com
Step 10 In the User Attribute text box, enter the name of the attribute in the user record that contains the username. You can
obtain this attribute from your directory server.
Step 11 In the User Object Type text box, enter the value of the LDAP objectType attribute that identifies the record as a user.
Often, user records have several values for the objectType attribute, some of which are unique to the user and some of
which are shared with other object types.
Step 12 In the Server Timeout text box, enter the number of seconds between retransmissions. The valid range is 2 to 30 seconds,
and the default value is 2 seconds.
Step 13 Click Apply to commit your changes.
Step 14 Click Save Configuration to save your changes.
Step 15 Specify LDAP as the priority backend database server for local EAP authentication as follows:
a) Choose Security > Local EAP > Authentication Priority to open the Priority Order > Local-Auth page.
b) Highlight LOCAL and click < to move it to the left User Credentials box.
c) Highlight LDAP and click > to move it to the right User Credentials box. The database that appears at the top of the
right User Credentials box is used when retrieving user credentials.
Note If both LDAP and LOCAL appear in the right User Credentials box with LDAP on the top and LOCAL on
the bottom, local EAP attempts to authenticate clients using the LDAP backend database and fails over to
the local user database if the LDAP servers are not reachable. If the user is not found, the authentication
attempt is rejected. If LOCAL is on the top, local EAP attempts to authenticate using only the local user
database. It does not fail over to the LDAP backend database.
d) Click Apply to commit your changes.
e) Click Save Configuration to save your changes.
Step 16 (Optional) Assign specific LDAP servers to a WLAN as follows:
a) Choose WLANs to open the WLANs page.
b) Click the ID number of the desired WLAN.
c) When the WLANs > Edit page appears, choose the Security > AAA Servers tabs to open the WLANs > Edit (Security
> AAA Servers) page.
d) From the LDAP Servers drop-down lists, choose the LDAP server(s) that you want to use with this WLAN. You can
choose up to three LDAP servers, which are tried in priority order.
Note These LDAP servers apply only to WLANs with web authentication enabled. They are not used by local
EAP.
e) Click Apply to commit your changes.
f) Click Save Configuration to save your changes.
Step 17 Specify the LDAP server fallback behavior, as follows:
a) Choose WLAN > AAA Server to open the Fallback Parameters page.
b) From the LDAP Servers drop-down list, choose the LDAP server in the order of priority when the controller attempts
to authenticate management users. The order of authentication is from server.
c) Choose Security > AAA > LDAP to view the list of global LDAP servers configured for the controller.
• Specify LDAP as the priority backend database server by entering this command:
config local-auth user-credentials ldap
If you enter the config local-auth user-credentials ldap local command, local EAP attempts to
authenticate clients using the LDAP backend database and fails over to the local user database if the
LDAP servers are not reachable. If the user is not found, the authentication attempt is rejected. If you
enter the config local-auth user-credentials local ldap command, local EAP attempts to authenticate
using only the local user database. It does not fail over to the LDAP backend database.
• (Optional) Assign specific LDAP servers to a WLAN by entering these commands:
◦config wlan ldap add wlan_id server_index—Links a configured LDAP server to a WLAN.
The LDAP servers specified in this command apply only to WLANs with web authentication
enabled. They are not used by local EAP.
◦config wlan ldap delete wlan_id {all | index}—Deletes a specific or all configured LDAP server(s)
from a WLAN.
1 2.3.1.4 389 No No
2 2.3.1.5 389 Yes No
◦show ldap index—Shows detailed LDAP server information. Information like the following
appears:
Server Index..................................... 2
Address.......................................... 10.10.20.22
Port............................................. 389
Enabled.......................................... Yes
User DN.......................................... ou=active,ou=employees,ou=people,
o=cisco.com
User Attribute................................... uid
User Type........................................ Person
Retransmit Timeout............................... 2 seconds
Bind Method ..................................... Authenticated
Bind Username................................. user1
Controller# show ldap 1
Server Index..................................... 1
Address.......................................... 9.1.0.100
Port............................................. 389
Server State..................................... Disabled
User DN.......................................... user1
User Attribute................................... user
User Type........................................ user
Retransmit Timeout............................... 2 seconds
Secure (via TLS)................................. Disabled
Bind Method ..................................... Anonymous
Server Index..................................... 1
Server statistics:
Initialized OK................................. 0
Initialization failed.......................... 0
Initialization retries......................... 0
Closed OK...................................... 0
Request statistics:
Received....................................... 0
Sent........................................... 0
OK............................................. 0
Success........................................ 0
Authentication failed.......................... 0
Server not found............................... 0
No received attributes......................... 0
No passed username............................. 0
Not connected to server........................ 0
Internal error................................. 0
Retries........................................ 0
Server Index..................................... 2
..
◦show wlan wlan_id—Shows the LDAP servers that are applied to a WLAN.
• Make sure the controller can reach the LDAP server by entering this command:
ping server_ip_address
• Save your changes by entering this command:
save config
• Enable or disable debugging for LDAP by entering this command:
debug aaa ldap {enable | disable}
Note The LDAP backend database supports these local EAP methods: EAP-TLS, EAP-FAST/GTC, and
PEAPv1/GTC. LEAP, EAP-FAST/MSCHAPv2, and PEAPv0/MSCHAPv2 are also supported but only
if the LDAP server is set up to return a clear-text password.
Note Cisco wireless LAN controllers support Local EAP authentication against external LDAP databases such as Microsof
Active Directory and Novell’s eDirectory. For more information about configuring the controller for Local EAP
authentication against Novell’s eDirectory, see the Configure Unified Wireless Network for Authentication Against
Novell's eDirectory Database whitepaper at
http://www.cisco.com/c/en/us/support/docs/wireless/4400-series-wireless-lan-controllers/112137-novell-edirectory-00.ht
If any RADIUS servers are configured on the controller, the controller tries to authenticate the wireless clients
using the RADIUS servers first. Local EAP is attempted only if no RADIUS servers are found, either because
the RADIUS servers timed out or no RADIUS servers were configured. If four RADIUS servers are configured,
the controller attempts to authenticate the client with the first RADIUS server, then the second RADIUS
server, and then local EAP. If the client attempts to then reauthenticate manually, the controller tries the third
RADIUS server, then the fourth RADIUS server, and then local EAP. If you never want the controller to try
to authenticate clients using an external RADIUS server, enter these CLI commands in this order:
• config wlan disable wlan_id
• config wlan radius_server auth disable wlan_id
• config wlan enable wlan_id
Note EAP-TLS, P EAPv0/MSCHAPv2, and PEAPv1/GTC use certificates for authentication, and EAP-FAST
uses either certificates or PACs. The controller is shipped with Cisco-installed device and Certificate
Authority (CA) certificates. However, if you want to use your own vendor-specific certificates, they must
be imported on the controller.
Step 1 If you are configuring local EAP to use one of the EAP types listed in the note above, make sure that the appropriate
certificates and PACs (if you will use manual PAC provisioning) have been imported on the controller.
Step 2 If you want the controller to retrieve user credentials from the local user database, make sure that you have properly
configured the local network users on the controller.
Step 3 If you want the controller to retrieve user credentials from an LDAP backend database, make sure that you have properly
configured an LDAP server on the controller.
Step 4 Specify the order in which user credentials are retrieved from the backend database servers as follows:
a) Choose Security > Local EAP > Authentication Priority to open the Priority Order > Local-Auth page.
b) Determine the priority order in which user credentials are to be retrieved from the local and/or LDAP databases. For
example, you may want the LDAP database to be given priority over the local user database, or you may not want
the LDAP database to be considered at all.
c) When you have decided on a priority order, highlight the desired database. Then use the left and right arrows and
the Up and Down buttons to move the desired database to the top of the right User Credentials box.
Note If both LDAP and LOCAL appear in the right User Credentials box with LDAP on the top and LOCAL on
the bottom, local EAP attempts to authenticate clients using the LDAP backend database and fails over to
the local user database if the LDAP servers are not reachable. If the user is not found, the authentication
attempt is rejected. If LOCAL is on the top, local EAP attempts to authenticate using only the local user
database. It does not fail over to the LDAP backend database.
d) Click Apply to commit your changes.
Step 5 Specify values for the local EAP timers as follows:
a) Choose Security > Local EAP > General to open the General page.
b) In the Local Auth Active Timeout text box, enter the amount of time (in seconds) in which the controller attempts
to authenticate wireless clients using local EAP after any pair of configured RADIUS servers fails. The valid range
is 1 to 3600 seconds, and the default setting is 100 seconds.
Step 6 Specify values for the Advanced EAP parameters as follows:
a) Choose Security> Advanced EAP.
b) In the Identity Request Timeout text box, enter the amount of time (in seconds) in which the controller attempts to
send an EAP identity request to wireless clients using local EAP. The valid range is 1 to 120 seconds, and the default
setting is 30 seconds.
c) In the Identity Request Max Retries text box, enter the maximum number of times that the controller attempts to
retransmit the EAP identity request to wireless clients using local EAP. The valid range is 1 to 20 retries, and the
default setting is 20 retries.
d) In the Dynamic WEP Key Index text box, enter the key index used for dynamic wired equivalent privacy (WEP).
The default value is 0, which corresponds to a key index of 1; the valid values are 0 to 3 (key index of 1 to 4).
e) In the Request Timeout text box, enter the amount of time (in seconds) in which the controller attempts to send an
EAP request to wireless clients using local EAP. The valid range is 1 to 120 seconds, and the default setting is 30
seconds.
f) In the Request Max Retries text box, enter the maximum number of times that the controller attempts to retransmit
the EAP request to wireless clients using local EAP. The valid range is 1 to 120 retries, and the default setting is 20
retries.
g) From the Max-Login Ignore Identity Response drop-down list, choose Enable to limit the number of devices that
can be connected to the controller with the same username. You can log in up to eight times from different devices
(PDA, laptop, IP phone, and so on) on the same controller. The default value is enabled.
h) In the EAPOL-Key Timeout text box, enter the amount of time (in seconds) in which the controller attempts to send
an EAP key over the LAN to wireless clients using local EAP. The valid range is 1 to 5 seconds, and the default
setting is 1 second.
Note If the controller and access point are separated by a WAN link, the default timeout of 1 second may not be
sufficient.
i) In the EAPOL-Key Max Retries text box, enter the maximum number of times that the controller attempts to send
an EAP key over the LAN to wireless clients using local EAP. The valid range is 0 to 4 retries, and the default setting
is 2 retries.
j) Click Apply to commit your changes.
Step 7 Create a local EAP profile, which specifies the EAP authentication types that are supported on the wireless clients as
follows:
a) Choose Security > Local EAP > Profiles to open the Local EAP Profiles page.
This page lists any local EAP profiles that have already been configured and specifies their EAP types. You can
create up to 16 local EAP profiles.
Note If you want to delete an existing profile, hover your cursor over the blue drop-down arrow for that profile
and choose Remove.
b) Click New to open the Local EAP Profiles > New page.
c) In the Profile Name text box, enter a name for your new profile and then click Apply.
Note You can enter up to 63 alphanumeric characters for the profile name. Make sure not to include spaces.
d) When the Local EAP Profiles page reappears, click the name of your new profile. The Local EAP Profiles > Edit
page appears.
e) Select the LEAP, EAP-FAST, EAP-TLS, and/or PEAP check boxes to specify the EAP type that can be used for
local authentication.
Note You can specify more than one EAP type per profile. However, if you choose multiple EAP types that use
certificates (such as EAP-FAST with certificates, EAP-TLS, PEAPv0/MSCHAPv2, and PEAPv1/GTC), all
of the EAP types must use the same certificate (from either Cisco or another vendor).
Note If you select the PEAP check box, both PEAPv0/MSCHAPv2 or PEAPv1/GTC are enabled on the controller.
f) If you chose EAP-FAST and want the device certificate on the controller to be used for authentication, select the
Local Certificate Required check box. If you want to use EAP-FAST with PACs instead of certificates, leave this
check box unselected, which is the default setting.
Note This option applies only to EAP-FAST because device certificates are not used with LEAP and are mandatory
for EAP-TLS and PEAP.
g) If you chose EAP-FAST and want the wireless clients to send their device certificates to the controller in order to
authenticate, select the Client Certificate Required check box. If you want to use EAP-FAST with PACs instead
of certificates, leave this check box unselected, which is the default setting.
Note This option applies only to EAP-FAST because client certificates are not used with LEAP or PEAP and are
mandatory for EAP-TLS.
h) If you chose EAP-FAST with certificates, EAP-TLS, or PEAP, choose which certificates will be sent to the client,
the ones from Cisco or the ones from another Vendor, from the Certificate Issuer drop-down list. The default setting
is Cisco.
i) If you chose EAP-FAST with certificates or EAP-TLS and want the incoming certificate from the client to be validated
against the CA certificates on the controller, select the Check against CA certificates check box. The default setting
is enabled.
j) If you chose EAP-FAST with certificates or EAP-TLS and want the common name (CN) in the incoming certificate
to be validated against the CA certificates’ CN on the controller, select the Verify Certificate CN Identity check
box. The default setting is disabled.
k) If you chose EAP-FAST with certificates or EAP-TLS and want the controller to verify that the incoming device
certificate is still valid and has not expired, select the Check Certificate Date Validity check box. The default setting
is enabled.
Note Certificate date validity is checked against the current UTC (GMT) time that is configured on the controller.
Timezone offset will be ignored.
l) Click Apply to commit your changes.
Step 8 If you created an EAP-FAST profile, follow these steps to configure the EAP-FAST parameters:
a) Choose Security > Local EAP > EAP-FAST Parameters to open the EAP-FAST Method Parameters page.
b) In the Server Key and Confirm Server Key text boxes, enter the key (in hexadecimal characters) used to encrypt and
decrypt PACs.
c) In the Time to Live for the PAC text box, enter the number of days for the PAC to remain viable. The valid range is
1 to 1000 days, and the default setting is 10 days.
d) In the Authority ID text box, enter the authority identifier of the local EAP-FAST server in hexadecimal characters.
You can enter up to 32 hexadecimal characters, but you must enter an even number of characters.
e) In the Authority ID Information text box, enter the authority identifier of the local EAP-FAST server in text format.
f) If you want to enable anonymous provisioning, select the Anonymous Provision check box. This feature allows
PACs to be sent automatically to clients that do not have one during PAC provisioning. If you disable this feature,
PACS must be manually provisioned. The default setting is enabled.
Note If the local and/or client certificates are required and you want to force all EAP-FAST clients to use
certificates, unselect the Anonymous Provision check box.
g) Click Apply to commit your changes.
Step 9 Enable local EAP on a WLAN as follows:
a) Choose WLANs to open the WLANs page.
b) Click the ID number of the desired WLAN.
c) When the WLANs > Edit page appears, choose the Security > AAA Servers tabs to open the WLANs > Edit
(Security > AAA Servers) page.
d) Unselect the Enabled check boxes for Radius Authentication Servers and Accounting Server to disable RADIUS
accounting and authentication for this WLAN.
e) Select the Local EAP Authentication check box to enable local EAP for this WLAN.
f) From the EAP Profile Name drop-down list, choose the EAP profile that you want to use for this WLAN.
g) If desired, choose the LDAP server that you want to use with local EAP on this WLAN from the LDAP Servers
drop-down lists.
h) Click Apply to commit your changes.
Step 10 Enable EAP parameters on a WLAN as follows:
a) Choose WLANs to open the WLANs page.
b) Click the ID number of the desired WLAN.
c) When the WLANs > Edit page appears, choose the Security > AAA Servers tabs to open the WLANs > Edit
(Security > AAA Servers) page.
d) Select the Enable check box to configure EAP parameters for this WLAN.
e) In the EAPOL Key Timeout (200 to 5000 millisec) text box, enter the amount of time (in milliseconds) in which
the controller attempts to send an EAP key over the WLAN to wireless clients using local EAP. The valid range is
200 to 5000 milliseconds and the default value is 1000 milliseconds.
f) In the EAPOL Key Retries (0 to 4) text box, enter the maximum number of times that the controller attempts to
send an EAP key over the WLAN to wireless clients using local EAP. The valid range is 0 to 4 retries and the default
setting is 2 retries.
g) In the Identity Request Timeout (1 to 120 sec) text box, enter the amount of time (in seconds) in which the controller
attempts to send an EAP identity request to wireless clients within WLAN using local EAP. The valid range is 1 to
120 seconds and the default value is 30 seconds.
h) In the Identity Request Retries (1 to 20 sec) text box, enter the maximum number of times that the controller attempts
to retransmit the EAP identity request to wireless clients within WLAN using local EAP. The valid range is 1 to 20
retries, and the default setting is 2 retries.
i) In the Request Timeout (1 to 120 sec) text box, enter the amount of time (in seconds) in which the controller attempts
to send an EAP parameter request to wireless clients within WLAN using local EAP. The valid range is 1 to 120
seconds, and the default setting is 30 seconds.
j) In the Request Retries (1 to 20 sec) text box, enter the maximum number of times that the controller attempts to
retransmit the EAP parameter request to wireless clients within WLAN using local EAP. The valid range is 1 to 20
retries, and the default setting is 2 retries.
k) Click Apply to commit your changes.
Step 11 Click Save Configuration to save your changes.
Note EAP-TLS, P EAPv0/MSCHAPv2, and PEAPv1/GTC use certificates for authentication, and EAP-FAST
uses either certificates or PACbs. The controller is shipped with Cisco-installed device and Certificate
Authority (CA) certificates. However, if you want to use your own vendor-specific certificates, they must
be imported on the controller.
Step 1 If you are configuring local EAP to use one of the EAP types listed in the note above, make sure that the appropriate
certificates and PACs (if you will use manual PAC provisioning) have been imported on the controller.
Step 2 If you want the controller to retrieve user credentials from the local user database, make sure that you have properly
configured the local network users on the controller.
Step 3 If you want the controller to retrieve user credentials from an LDAP backend database, make sure that you have properly
configured an LDAP server on the controller.
Step 4 Specify the order in which user credentials are retrieved from the local and/or LDAP databases by entering this command:
config local-auth user-credentials {local | ldap}
Note If you enter the config local-auth user-credentials ldap local command, local EAP attempts to authenticate
clients using the LDAP backend database and fails over to the local user database if the LDAP servers are not
reachable. If the user is not found, the authentication attempt is rejected. If you enter the config local-auth
user-credentials local ldap command, local EAP attempts to authenticate using only the local user database.
It does not fail over to the LDAP backend database.
Step 5 Specify values for the local EAP timers by entering these commands:
• config local-auth active-timeout timeout—Specifies the amount of time (in seconds) in which the controller
attempts to authenticate wireless clients using local EAP after any pair of configured RADIUS servers fails. The
valid range is 1 to 3600 seconds, and the default setting is 100 seconds.
• config advanced eap identity-request-timeout timeout—Specifies the amount of time (in seconds) in which the
controller attempts to send an EAP identity request to wireless clients using local EAP. The valid range is 1 to 120
seconds, and the default setting is 30 seconds.
• config advanced eap identity-request-retries retries—Specifies the maximum number of times that the controller
attempts to retransmit the EAP identity request to wireless clients using local EAP. The valid range is 1 to 20 retries,
and the default setting is 20 retries.
• config advanced eap key-index index—Specifies the key index used for dynamic wired equivalent privacy (WEP).
The default value is 0, which corresponds to a key index of 1; the valid values are 0 to 3 (key index of 1 to 4).
• config advanced eap request-timeout timeout—Specifies the amount of time (in seconds) in which the controller
attempts to send an EAP request to wireless clients using local EAP. The valid range is 1 to 120 seconds, and the
default setting is 30 seconds.
• config advanced eap request-retries retries—Specifies the maximum number of times that the controller attempts
to retransmit the EAP request to wireless clients using local EAP. The valid range is 1 to 120 retries, and the default
setting is 20 retries.
• config advanced eap eapol-key-timeout timeout—Specifies the amount of time (in seconds) in which the controller
attempts to send an EAP key over the LAN to wireless clients using local EAP. The valid range is 1 to 5 seconds,
and the default setting is 1 second.
Note If the controller and access point are separated by a WAN link, the default timeout of 1 second may not
be sufficient.
• config advanced eap eapol-key-retries retries—Specifies the maximum number of times that the controller
attempts to send an EAP key over the LAN to wireless clients using local EAP. The valid range is 0 to 4 retries,
and the default setting is 2 retries.
• config advanced eap max-login-ignore-identity-response {enable | disable}—When enabled, this command
ignores the limit set for the number of devices that can be connected to the controller with the same username
through 802.1x authentication. When disabled, this command limits the number of devices that can be connected
to the controller with the same username. This is not applicable for web authentication users. You can log in up to
eight times from different devices (PDA, laptop, IP phone, and so on) on the same controller. The default value is
enabled. Use the command config netuser maxUserLogin to set the limit of maximum number of devices per
same username.
Step 6 Specify values for the local EAP timers on a WLAN by entering these commands:
• config wlan security eap-params {enable | disable} wlan_id—Specifies to enable or disable SSID specific EAP
timeouts or retries. The default value is disabled.
• config wlan security eap-params eapol-key-timeout timeout wlan_id—Specifies the amount of time (in
milliseconds) in which the controller attempts to send an EAP key over the WLAN to wireless clients using local
EAP. The valid range is 200 to 5000 milliseconds, and the default setting is 1000 milliseconds.
• config wlan security eap-params eapol-key-retries retries wlan_id—Specifies the maximum number of times
that the controller attempts to send an EAP key over the WLAN to wireless clients using local EAP. The valid
range is 0 to 4 retries, and the default setting is 2 retries.
• config wlan security eap-params identity-request-timeout timeout wlan_id—Specifies the amount of time (in
seconds) in which the controller attempts to send an EAP identity request to wireless clients within WLAN using
local EAP. The valid range is 1 to 120 seconds, and the default setting is 30 seconds.
• config wlan security eap-params identity-request-retries retries wlan_id—Specifies the maximum number of
times that the controller attempts to retransmit the EAP identity request to wireless clients within WLAN using
local EAP. The valid range is 1 to 20 retries, and the default setting is 2 retries.
• config wlan security eap-params request-timeout timeout wlan_id—Specifies the amount of time (in seconds)
in which the controller attempts to send an EAP parameter request to wireless clients within WLAN using local
EAP. The valid range is 1 to 120 seconds, and the default setting is 30 seconds.
• config wlan security eap-params request-retries retries wlan_id—Specifies the maximum number of times that
the controller attempts to retransmit the EAP parameter request to wireless clients within WLAN using local EAP.
The valid range is 1 to 20 retries, and the default setting is 2 retries.
Step 8 Add an EAP method to a local EAP profile by entering this command:
config local-auth eap-profile method add method profile_name
The supported methods are leap, fast, tls, and peap.
Note If you choose peap, both P EAPv0/MSCHAPv2 or PEAPv1/GTC are enabled on the controller.
Note You can specify more than one EAP type per profile. However, if you create a profile with multiple EAP types
that use certificates (such as EAP-FAST with certificates, EAP-TLS, PEAPv0/MSCHAPv2, and PEAPv1/GTC),
all of the EAP types must use the same certificate (from either Cisco or another vendor).
Note To delete an EAP method from a local EAP profile, enter the config local-auth eap-profile method delete
method profile_name command:
Step 9 Configure EAP-FAST parameters if you created an EAP-FAST profile by entering this command:
config local-auth method fast ?
where ? is one of the following:
• anon-prov {enable | disable}—Configures the controller to allow anonymous provisioning, which allows PACs
to be sent automatically to clients that do not have one during PAC provisioning.
• authority-id auth_id—Specifies the authority identifier of the local EAP-FAST server.
• pac-ttl days—Specifies the number of days for the PAC to remain viable.
• server-key key—Specifies the server key used to encrypt and decrypt PACs.
Step 11 Enable local EAP and attach an EAP profile to a WLAN by entering this command:
Timer:
Active timeout .............................. 300
• show ap stats wlan Cisco_AP—Shows the EAP timeout and failure counters for a specific access point for each
WLAN.
• show client detail client_mac—Shows the EAP timeout and failure counters for a specific associated client. These
statistics are useful in troubleshooting client association issues.
...
Client Statistics:
Number of Bytes Received................... 10
Number of Bytes Sent....................... 10
Number of Packets Received................. 2
Number of Packets Sent..................... 2
Number of EAP Id Request Msg Timeouts...... 0
Number of EAP Id Request Msg Failures...... 0
Number of EAP Request Msg Timeouts......... 2
Number of EAP Request Msg Failures......... 1
Number of EAP Key Msg Timeouts............. 0
Number of EAP Key Msg Failures............. 0
Number of Policy Errors.................... 0
Radio Signal Strength Indicator............ Unavailable
Signal to Noise Ratio...................... Unavailable
Step 1 Choose Wireless > 802.11b/g/n > Network to open the 802.11b/g Global Parameters page.
Step 2 If the Short Preamble check box is selected, continue with this procedure. However, if the Short Preamble check box
is unselected (which means that long preambles are enabled), the controller is already optimized for SpectraLink NetLink
phones and you do not need to continue this procedure.
Step 3 Unselect the Short Preamble check box to enable long preambles.
Step 4 Click Apply to update the controller configuration.
Note If you do not already have an active CLI session to the controller, we recommend that you start a CLI session
to reboot the controller and watch the reboot process. A CLI session is also useful because the GUI loses its
connection when the controller reboots.
Step 5 Choose Commands > Reboot > Reboot > Save and Reboot to reboot the controller. Click OK in response to this
prompt:
Configuration will be saved and the controller will be rebooted. Click ok to confirm.
The controller reboots.
Step 6 Log back onto the controller GUI to verify that the controller is properly configured.
Step 7 Choose Wireless > 802.11b/g/n > Network to open the 802.11b/g Global Parameters page. If the Short Preamble check
box is unselected, the controller is optimized for SpectraLink NetLink phones.
Step 6 Enter the reset system command to reboot the controller. Enter y when the prompt to save the system changes is displayed.
The controller reboots.
Step 7 Verify that the controller is properly configured by logging back into the CLI and entering the show 802.11b command
to view these parameters:
Note To propagate this command to all access points connected to the controller, make sure to disable and then
reenable the 802.11b/g network after entering this command.
Note The client moves to the Central Web Authentication state, if the URL returned by the Cisco ISE server
has the keyword cwa.
The NAC agent in the client triggers the posture validation process. On successful posture validation by the
Cisco ISE server, the client is moved to the Run state.
Note FlexConnect local switching with RADIUS NAC support is added in Release 7.2.110.0. It is not supported
in the 7.0 releases and Release 7.2.103.0. Downgrading from Release 7.2.110.0 or a later release to either
Release 7.2.103.0 or a 7.0 release will require you to reconfigure the WLAN for the RADIUS NAC feature
to work.
Device Registration
Device registration enables you to authenticate and provision new devices on the WLAN with RADIUS NAC
enabled. When a device is registered on the WLAN, it can use the network based on the configured ACL.
before the clients move to the Run state. If HA is configured, the client is automatically moved to the
Run state in the fallback Cisco ISE server.
• Do not swap AAA server indexes in a live network because clients might get disconnected and have to
reconnect to the RADIUS server, which might result in log messages to be appended to the ISE server
logs.
• Enable AAA override on the WLAN to use RADIUS NAC.
• WPA and WPA2 or dot1X must be enabled on the WLAN. This is also required in case of PSK in Layer
2 security.
• During slow roaming, clients go through posture validation.
• If the AAA url-redirect-acl and url-redirect attributes are expected from the AAA server, the AAA
override feature must be enabled on the controller.
Restrictions
• A RADIUS NAC-enabled WLAN supports only Open Authentication and MAC filtering.
• The RADIUS NAC functionality does not work if the configured accounting server is different from
the authentication (Cisco ISE) server. You should configure the same server as the authentication and
accounting server if Cisco ISE functionalities are used. If Cisco ISE is used only for Cisco ACS
functionality, the accounting server can be flexible.
• The controller software configured with RADIUS NAC does not support a CoA on the service port.
• Guest tunneling mobility is supported only for ISE NAC–enabled WLANs.
• VLAN select is not supported.
• Workgroup bridges are not supported.
• The AP Group over NAC is not supported in RADIUS NAC.
• When RADIUS NAC is enabled, the RADIUS server overwrite interface is not supported.
Note AAA override is automatically enabled when you use RADIUS NAC on a WLAN.
Step 1 Choose Management > Mgmt Via Wireless to open the Management Via Wireless page.
Step 2 Select the Enable Controller Management to be accessible from Wireless Clients check box to enable management
over wireless for the WLAN or unselect it to disable this feature. The default value is unselected.
Step 3 Click Apply to commit your changes.
Step 4 Click Save Configuration to save your changes.
Step 1 Verify whether the management over wireless interface is enabled or disabled by entering this command:
show network summary
• If disabled: Enable management over wireless by entering this command:config network mgmt-via-wireless
enable
• Otherwise, use a wireless client to associate with an access point connected to the controller that you want to
manage.
Step 2 Log into the CLI to verify that you can manage the WLAN using a wireless client by entering this command:
telnet controller-ip-address command
Here, management is not the management interface but the configuration access. If the Cisco WLC configuration
is accessed from any other IP address on the Cisco WLC other than the management IP, it is management
using dynamic interface.
The access point forwards all DHCP requests from a client to the . The adds the DHCP option 82 payload
and forwards the request to the DHCP server. The payload can contain the MAC address or the MAC address
and SSID of the access point, depending on how you configure this option.
Note Any DHCP packets that already include a relay agent option are dropped at the .
Step 1 Choose Controller > Advanced > DHCP to open the DHCP Parameters page.
Step 2 Select the Enable DHCP Proxy check box to enable DHCP proxy.
Step 3 Choose a DHCP Option 82 format from the drop-down list. You can choose either binary or ascii to specify the format
of the DHCP option 82 payload.
Step 4 Choose a DHCP Option 82 Remote ID field format from the drop-down list to specify the format of the DHCP option
82 payload.
For more information about the options available, see the Controller Online Help.
Step 5 Enter the DHCP timeout value in the DHCP Timeout field. The timeout value is globally applicable. You can specify
the DHCP timeout value in range from 5 to 120 seconds.
Step 6 Click Apply.
Step 7 Click Save Configuration .
What to Do Next
On the controller CLI, you can enable DHCP option 82 on the dynamic interface to which the WLAN is
associated by entering this command:
config interface dhcp dynamic-interface interface-name option-82 enable
◦config dhcp opt-82 remote-id apname:ssid—Adds the AP name and SSID of the access point to
the DHCP option 82 payload.
◦config dhcp opt-82 remote-id ap-group-name—Adds the AP group name to the DHCP option
82 payload.
◦config dhcp opt-82 remote-id flex-group-name—Adds the FlexConnect group name to the DHCP
option 82 payload.
◦config dhcp opt-82 remote-id ap-location—Adds the AP location to the DHCP option 82 payload.
◦config dhcp opt-82 remote-id apmac-vlan-id—Adds the radio MAC address of the access point
and the VLAN ID to the DHCP option 82 payload.
◦config dhcp opt-82 remote-id apname-vlan-id—Adds the AP name and its VLAN ID to the DHCP
option 82 payload.
◦config dhcp opt-82 remote-id ap-ethmac-ssid—Adds the Ethernet MAC address of the access
point and the SSID to the DHCP option 82 payload.
• Configure the format of the DHCP option 82 as binary or ASCII by entering this command:
config dhcp opt-82 format {binary |ascii}
• Enable DHCP Option 82 on the dynamic interface to which the WLAN is associated by entering this
command:
config interface dhcp dynamic-interface interface-name option-82 enable
• See the status of DHCP option 82 on the dynamic interface by entering the show interface detailed
dynamic-interface-namecommand.
Note You can enable only IPv4 traffic in your network by blocking IPv6 traffic. That is, you can configure an
IPv6 ACL to deny all IPv6 traffic and apply it on specific or all WLANs.
• When you apply CPU ACLs on a Cisco 5508 WLC or a Cisco WiSM2, you must permit traffic towards
the virtual interface IP address for web authentication.
• All ACLs have an implicit “deny all rule” as the last rule. If a packet does not match any of the rules, it
is dropped by the controller.
• If you are using an external web server with a Cisco 5508 WLC or a WLC network module, you must
configure a preauthentication ACL on the WLAN for the external web server.
• If you apply an ACL to an interface or a WLAN, wireless throughput is degraded when downloading
from a 1-Gbps file server. To improve throughput, remove the ACL from the interface or WLAN, move
the ACL to a neighboring wired device with a policy rate-limiting restriction, or connect the file server
using 100 Mbps rather than 1 Gbps.
• Multicast traffic received from wired networks that is destined to wireless clients is not processed by
WLC ACLs. Multicast traffic initiated from wireless clients, destined to wired networks or other wireless
clients on the same controller, is processed by WLC ACLs.
• ACLs are configured on the controller directly or configured through Cisco Prime Infrastructure templates.
The ACL name must be unique.
• You can configure ACL per client (AAA overridden ACL) or on either an interface or a WLAN. The
AAA overridden ACL has the highest priority. However, each interface, WLAN, or per client ACL
configuration that you apply can override one another.
• If peer-to-peer blocking is enabled, traffic is blocked between peers even if the ACL allows traffic
between them.
• Authentication traffic has to go through the Cisco WLC for this feature to be supported, even if DNS-based
ACL is local to the AP.
• When you create an ACL, it is recommended to perform the two actions (create an ACL or ACL rule
and apply the ACL or ACL rule) continuously either from CLI or GUI.
• In Cisco Wireless Releases prior to 8.0.100.0, the behavior of the Redirect-URL-ACL (as returned via
RADIUS attributes) may have been incorrect. The ACL was applied in only the Ingress direction (traffic
destined for the LAN or distribution system) of the radio interface. These ACLs should also be applied
in the Egress direction (traffic destined for the wireless client). Therefore, after upgrading to a Cisco
Wireless Release 8.0 or a later release, you may need to adjust the ACL to accommodate the correction
of this behavior.
Note ACL ID 0 is not supported in Cisco WLC. Foreign WLC does not send url-redirect-acl to anchor WLC
if the received ACL attribute from RADIUS/ISE is mapped to ACL ID 0. It causes web redirect failure
on wireless client later.
Step 1 Choose Security > Access Control Lists > Access Control Lists to open the Access Control Lists page.
Step 2 If you want to see if packets are hitting any of the ACLs configured on your controller, select the Enable Counters
check box and click Apply. Otherwise, leave the check box unselected, which is the default value. This feature is useful
when troubleshooting your system.
Note If you want to clear the counters for an ACL, hover your cursor over the blue drop-down arrow for that ACL
and choose Clear Counters.
Step 3 Add a new ACL by clicking New. The Access Control Lists > New page appears.
Step 4 In the Access Control List Name text box, enter a name for the new ACL. You can enter up to 32 alphanumeric characters.
Step 5 Choose the ACL type. There are two types of ACL supported, IPv4 and IPv6.
Step 6 Click Apply. When the Access Control Lists page reappears, click the name of the new ACL.
Step 7 When the Access Control Lists > Edit page appears, click Add New Rule. The Access Control Lists > Rules > New
page appears.
Step 8 Configure a rule for this ACL as follows:
a) The controller supports up to 64 rules for each ACL. These rules are listed in order from 1 to 64. In the Sequence
text box, enter a value (between 1 and 64) to determine the order of this rule in relation to any other rules defined for
this ACL.
Note If rules 1 through 4 are already defined and you add rule 29, it is added as rule 5. If you add or change a
sequence number for a rule, the sequence numbers for other rules adjust to maintain a continuous sequence.
For instance, if you change a rule’s sequence number from 7 to 5, the rules with sequence numbers 5 and 6
are automatically reassigned as 6 and 7, respectively.
b) From the Source drop-down list, choose one of these options to specify the source of the packets to which this ACL
applies:
• Any—Any source (this is the default value).
• IP Address—A specific source. If you choose this option, enter the IP address and netmask of the source in
the text boxes. If you are configuring IPv6 ACL, enter the IPv6 address and prefix length of the destination in
the text boxes.
c) From the Destination drop-down list, choose one of these options to specify the destination of the packets to which
this ACL applies:
• Any—Any destination (this is the default value).
• IP Address—A specific destination. If you choose this option, enter the IP address and netmask of the destination
in the text boxes. If you are configuring IPv6 ACL, enter the IPv6 address and prefix length of the destination
in the text boxes.
d) From the Protocol drop-down list, choose the protocol ID of the IP packets to be used for this ACL. These are the
protocol options:
• Any—Any protocol (this is the default value)
The controller can permit or deny only IP packets in an ACL. Other types of packets (such as ARP packets) cannot
be specified.
e) If you chose TCP or UDP in the previous step, two additional parameters appear: Source Port and Destination Port.
These parameters enable you to choose a specific source port and destination port or port ranges. The port options
are used by applications that send and receive data to and from the networking stack. Some ports are designated for
certain applications such as Telnet, SSH, HTTP, and so on.
Note Source and Destination ports based on the ACL
type.
f) From the DSCP drop-down list, choose one of these options to specify the differentiated services code point (DSCP)
value of this ACL. DSCP is an IP header text box that can be used to define the quality of service across the Internet.
• Any—Any DSCP (this is the default value)
• Specific—A specific DSCP from 0 to 63, which you enter in the DSCP edit box
g) From the Direction drop-down list, choose one of these options to specify the direction of the traffic to which this
ACL applies:
• Any—Any direction (this is the default value)
• Inbound—From the client
• Outbound—To the client
Note If you are planning to apply this ACL to the controller CPU, the packet direction does not have any
significance, it is always ‘Any’.
h) From the Action drop-down list, choose Deny to cause this ACL to block packets or Permit to cause this ACL to
allow packets. The default value is Deny.
i) Click Apply to commit your changes. The Access Control Lists > Edit page reappears, showing the rules for this
ACL.
The Deny Counters fields shows the number of times that packets have matched the explicit deny ACL rule. The
Number of Hits field shows the number of times that packets have matched an ACL rule. You must enable ACL
counters on the Access Control Lists page to enable these fields.
Note If you want to edit a rule, click the sequence number of the desired rule to open the Access Control Lists
> Rules > Edit page. If you want to delete a rule, hover your cursor over the blue drop-down arrow for the
desired rule and choose Remove.
j) Repeat this procedure to add any additional rules for this ACL.
Step 9 Click Save Configuration to save your changes.
Step 10 Repeat this procedure to add any additional ACLs.
Step 1 Choose Security > Access Control Lists > CPU Access Control Lists to open the CPU Access Control Lists page.
Step 2 Select the Enable CPU ACL check box to enable a designated ACL to control the IPv4 traffic to the controller CPU or
unselect the check box to disable the CPU ACL feature and remove any ACL that had been applied to the CPU. The
default value is unselected.
Step 3 From the ACL Name drop-down list, choose the ACL that will control the IPv4 traffic to the controller CPU. None is
the default value when the CPU ACL feature is disabled. If you choose None while the Enable CPU ACL check box is
selected, an error message appears indicating that you must choose an ACL.
Note This parameter is available only if you have selected the CPU ACL Enable check
box.
Note When CPU ACL is enabled, it is applicable to both wireless and wired traffic.
Step 4 Select the Enable CPU IPv6 ACL check box to enable a designated ACL to control the IPv6 traffic to the controller
CPU or unselect the check box to disable the CPU ACL feature and remove any ACL that had been applied to the CPU.
The default value is unselected.
Note For CPU IPv6 ACL, along with permit rules for HTTP/Telnet, you must add a rule to allow ICMPv6 (NA/ND
uses ICMPv6) for the CPU IPv6 ACLs to work.
Step 5 From the IPv6 ACL Name drop-down list, choose the ACL that will control the IPv6 traffic to the controller CPU. None
is the default value when the CPU ACL feature is disabled. If you choose None while the Enable CPU IPv6 ACL check
box is selected, an error message appears indicating that you must choose an ACL.
Step 6 Click Apply to commit your changes.
Step 7 Click Save Configuration to save your changes.
Step 1 See all of the ACLs that are configured on the controller by entering this command:
show [ipv6] acl summary
Step 2 See detailed information for a particular ACL by entering this command:
show [ipv6] acl detailed acl_name
The Counter text box increments each time a packet matches an ACL rule, and the DenyCounter text box increments
each time a packet does not match any of the rules.
Note If a traffic/request is allowed from the controller by a permit rule, then the response to the traffic/request in the
opposite direction also is allowed and cannot be blocked by a deny rule in the ACL.
Step 3 Enable or disable ACL counters for your controller by entering this command:
config acl counter {start | stop}
Note If you want to clear the current counters for an ACL, enter the clear acl counters acl_name command.
• To apply an ACL to the controller CPU to restrict the IPv4 type of traffic (wired, wireless, or both) reaching the
CPU, enter this command:
config acl cpu acl_name {wired | wireless | both}
Note To see the ACL that is applied to the controller CPU, enter the show acl cpu command. To remove the
ACL that is applied to the controller CPU, enter the config acl cpu none command.
Note For 2504 and 4400 series WLC, the CPU ACL cannot be used to control the CAPWAP traffic. Use the
access-list on the network to control CAPWAP traffic.
Note WLC devices configured to preform Central Switching and Centralized Authentication displays the name
of the Layer-2 ACL being applied to roaming users incorrectly. The situation occurs when an authorized
device preforms a Layer-3 roam from the anchor controller to a foreign controller. After roaming, if an
administrator issues the show acl layer2 summary command on the CLI of the foreign controller the
incorrect information is displayed. It is expected that the ACL applied by the anchor will follow the
authenticated client as it roams from controller to controller.
Mapping of Layer 2 ACLs with Locally Switched WLANs Using FlexConnect Access Points (CLI)
This is applicable to locally switched WLANs that have FlexConnect access points.
• config ap flexconnect wlan l2acl add wlan-id ap-name acl-name—Maps a Layer 2 ACL to a locally
switched WLAN.
• config ap flexconnect wlan l2acl delete wlan-id ap-name—Deletes the mapping.
• show ap config general ap-name—Shows the details of the mapping.
Step 1 Choose Security > Access Control Lists > Layer2 ACLs to open the Layer2 Access Control Lists page.
Step 2 Add a new ACL by clicking New. The Layer2 Access Control Lists > New page appears.
Step 3 In the Access Control List Name text box, enter a name for the new ACL. You can enter up to 32 alphanumeric characters.
Step 4 Click Apply. When the Layer2 Access Control Lists page reappears, click the name of the new ACL.
Step 5 When the Layer2 Access Control Lists > Edit page appears, click Add New Rule. The Layer2 Access Control Lists >
Rules > New page appears.
Step 6 Configure a rule for this ACL as follows:
a) The controller supports up to 16 rules for each ACL. These rules are listed in order from 1 to 16. In the Sequence
text box, enter a value (between 1 and 16) to determine the order of this rule in relation to any other rules defined for
this ACL.
Note If rules 1 through 4 are already defined and you add rule 15, it is added as rule 5. If you add or change a
sequence number for a rule, the sequence numbers for other rules adjust to maintain a continuous sequence.
For instance, if you change a rule’s sequence number from 7 to 5, the rules with sequence numbers 5 and 6
are automatically reassigned as 6 and 7, respectively.
b) From the Ether Type drop-down list, choose any option from the following Ether type:
• AppleTalk Address Resolution Protocol
• VLAN-tagged Frame & Short Path Bridging
• IPX (0x8137)
• IPX (0x8138)
• QNS Qnet
• Internet Protocol Version 6
• Ethernet Flow Control
• Slow Protocol
• CobraNet
• MPLS Unicast
• MPLS Multicast
• PPPoE Discovery Stage
• PPPoE Session Stage
• Jumbo Frames
• HomePlug 1.0 MME
• EAP over LAN
• PROFINET over Protocol
• HyperSCSI
• ATA over Ethernet
• EtherCAT Protocol
Note You can select any predefined Ether Types from the Ether Type drop-down list or enter your own Ether type
value using the custom option from the Ether Type drop-down list.
c) From the Action drop-down list, choose Deny to cause this ACL to block packets or Permit to cause this ACL to
allow packets. The default value is Deny.
d) Click Apply to commit your changes. The Layer2 Access Control Lists > Edit page reappears, showing the rules for
this ACL.
e) Repeat this procedure to add any additional rules for this ACL.
Step 7 Click Save Configuration to save your changes.
Step 8 Repeat this procedure to add any additional ACLs.
Step 1 Choose Wireless > Access Points > All APs to open the All APs page.
Step 2 Click the name of the desired access point to open the All APs > Details page.
Step 3 On the All APs > Details page, click the FlexConnect tab.
Step 4 From the PreAuthentication Access Control Lists area, click the Layer2 ACLs link to open the ACL Mappings page.
Step 5 From the Layer2 ACL drop-down list in the WLAN ACL Mapping area, choose the ACL you have created and click
Add.
Step 6 Click Apply.
Step 7 Click Save Configuration.
Step 1 Specifies to create ACL. You can enter an IPv4 ACL name up to 32 alphanumeric characters.
config acl create name
Example:
(Cisco Controller) >> config acl create android
Step 2 Specifies to add a new URL domain for the access control list. URL domain name should be given in a valid format, for
example, Cisco.com, bbc.in, or play.google.com. The hostname comparison is a sub string matched (wildcard based).
You must use the ACL name that you have created already.
config acl url-domain add domain-name acl-name
Example:
(Cisco Controller) >> config acl url-domain add cisco.com android
(Cisco Controller) >> config acl url-domain add play.google.com android
Step 3 Specifies to delete an existing URL domain for the access control list.
config acl url-domain delete domain-name acl-name
Example:
(Cisco Controller) >> config acl url-domain delete cisco.com android
Step 4 Specifies to apply the ACL.
config acl apply acl-name
Example:
(Cisco Controller) >> config acl apply android
Step 5 Displays DNS-based ACL information by entering this command:
show acl summary
Example:
(Cisco Controller) >> show acl summary
Example:
(Cisco Controller) >> show acl detailed android
o rules are configured for this ACL.
DenyCounter : 0
URLs configured in this ACL
---------------------------
*.play.google.com
*.store.google.com
Step 7 Displays the IP addresses per client learned through DNS snooping (DNS-based ACL) by entering this command:
show client detail mac-address
Example:
(Cisco Controller) >> show client detail mac-address
Step 8 Enables debugging of information related to DNS-based ACL.
debug aaa events enable
Example:
(Cisco Controller) >> debug aaa events enable
Step 1 Choose Security > Access Control Lists > Access Control Lists to open the Access Control Lists page.
Step 2 If you want to see if packets are hitting any of the ACLs configured on your controller, select the Enable Counters
check box and click Apply. Otherwise, leave the check box unselected, which is the default value. This feature is useful
when troubleshooting your system.
Note If you want to clear the counters for an ACL, hover your cursor over the blue drop-down arrow for that ACL
and choose Clear Counters.
Step 3 Add a new ACL by clicking New. The Access Control Lists > New page appears.
Step 4 In the Access Control List Name text box, enter a name for the new ACL. You can enter up to 32 alphanumeric characters.
Step 5 Select the ACL type as IPv4.
Step 6 Click Apply.
Step 7 When the Access Control Lists page reappears, click the name of the new ACL. The ACLs have no IP rules. Hover
your cursor over the blue drop-down arrow, choose Add-Remove URL from the drop-down list to open the URL List
page.
Step 8 To add a new URL domain for an ACL, enter the new URL domain for the access control list in the URL String Name
text box. The URL domain name should be given in a valid format, for example, Cisco.com, bbc.in, or play.google.com.
Step 9 To delete an URL domain, hover your cursor over the blue drop-down arrow under the URL Name you want to delete,
and select Delete.
to protect the following types of class 3 unicast management frames: disassociation, deauthentication,
and QoS (WMM) action. Client MFP protects a client-access point session from the most common type
of denial-of-service attack. It protects class 3 management frames by using the same encryption method
used for the session’s data frames. If a frame received by the access point or client fails decryption, it is
dropped, and the event is reported to the controller.
To use client MFP, clients must support CCXv5 MFP and must negotiate WPA2 using either TKIP or
AES-CCMP. EAP or PSK may be used to obtain the PMK. CCKM and controller mobility management
are used to distribute session keys between access points for Layer 2 and Layer 3 fast roaming.
Note To prevent attacks using broadcast frames, access points supporting CCXv5 will not
emit any broadcast class 3 management frames (such as disassociation, deauthentication,
or action). CCXv5 clients and access points must discard broadcast class 3 management
frames.
Client MFP supplements infrastructure MFP rather than replaces it because infrastructure
MFP continues to detect and report invalid unicast frames sent to clients that are not
client-MFP capable as well as invalid class 1 and 2 management frames. Infrastructure
MFP is applied only to management frames that are not protected by client MFP.
Infrastructure MFP consists of three main components:
• Management frame protection—The access point protects the management frames it transmits by adding
a MIC IE to each frame. Any attempt to copy, alter, or replay the frame invalidates the MIC, causing
any receiving access point configured to detect MFP frames to report the discrepancy. MFP is supported
for use with Cisco Aironet lightweight access points.
• Management frame validation—In infrastructure MFP, the access point validates every management
frame that it receives from other access points in the network. It ensures that the MIC IE is present (when
the originator is configured to transmit MFP frames) and matches the content of the management frame.
If it receives any frame that does not contain a valid MIC IE from a BSSID belonging to an access point
that is configured to transmit MFP frames, it reports the discrepancy to the network management system.
In order for the timestamps to operate properly, all controllers must be Network Time Protocol (NTP)
synchronized.
• Event reporting—The access point notifies the controller when it detects an anomaly, and the controller
aggregates the received anomaly events and can report the results through SNMP traps to the network
management system.
Note Client MFP uses the same event reporting mechanisms as infrastructure MFP.
Infrastructure MFP is disabled by default and can be enabled globally. When you upgrade from a previous
software release, infrastructure MFP is disabled globally if access point authentication is enabled because the
two features are mutually exclusive. Once infrastructure MFP is enabled globally, signature generation (adding
MICs to outbound frames) can be disabled for selected WLANs, and validation can be disabled for selected
access points.
Client MFP is enabled by default on WLANs that are configured for WPA2. It can be disabled, or it can be
made mandatory (in which case, only clients that negotiate MFP are allowed to associate) on selected WLANs.
Step 1 Choose Security> Wireless Protection Policies > AP Authentication/MFP to open the AP Authentication Policy page.
Step 2 Enable infrastructure MFP globally for the controller by choosing Management Frame Protection from the Protection
Type drop-down list.
Step 3 Click Apply to commit your changes.
Note If more than one controller is included in the mobility group, you must configure an NTP/SNTP server on all
controllers in the mobility group that are configured for infrastructure MFP.
Step 4 Configure client MFP for a particular WLAN after infrastructure MFP has been enabled globally for the controller as
follows:
a) Choose WLANs.
b) Click the profile name of the desired WLAN. The WLANs > Edit page appears.
c) Choose Advanced. The WLANs > Edit (Advanced) page appears.
d) Choose Disabled, Optional, or Required from the MFP Client Protection drop-down list. The default value is
Optional. If you choose Required, clients are allowed to associate only if MFP is negotiated (that is, if WPA2 is
configured on the controller and the client supports CCXv5 MFP and is also configured for WPA2).
Note For Cisco OEAP 600, MFP is not supported. It should either be Disabled or Optional.
e) Click Apply to commit your changes.
Step 5 Click Save Configuration to save your settings.
• The Management Frame Protection field shows if infrastructure MFP is enabled globally for the
controller.
• The Controller Time Source Valid field indicates whether the controller time is set locally (by manually
entering the time) or through an external source (such as the NTP/SNTP server). If the time is set by an
external source, the value of this field is “True.” If the time is set locally, the value is “False.” The time
source is used for validating the timestamp on management frames between access points of different
controllers within a mobility group.
• The Client Protection field shows if client MFP is enabled for individual WLANs and whether it is
optional or required.
Note This report contains no data unless an active attack is in progress. This table is cleared every 5 minutes
when the data is forwarded to any network management stations.
capwap—Configures debugging for MFP messages between the controller and access points.
detail—Configures detailed debugging for MFP messages.
report—Configures debugging for MFP reporting.
mm—Configures debugging for MFP mobility (inter-controller) messages.
Step 1 Choose Security > Wireless Protection Policies > Client Exclusion Policies to open the Client Exclusion Policies
page.
Step 2 Select any of these check boxes if you want the controller to exclude clients for the condition specified. The default value
for each exclusion policy is enabled.
• Excessive 802.11 Association Failures—Clients are excluded on the sixth 802.11 association attempt, after five
consecutive failures.
• Excessive 802.11 Authentication Failures—Clients are excluded on the sixth 802.11 authentication attempt, after
five consecutive failures.
• Excessive 802.1X Authentication Failures—Clients are excluded on the fourth 802.1X authentication attempt,
after three consecutive failures.
• IP Theft or IP Reuse—Clients are excluded if the IP address is already assigned to another device.
• Excessive Web Authentication Failures—Clients are excluded on the fourth web authentication attempt, after
three consecutive failures.
Step 1 Enable or disable the controller to exclude clients on the sixth 802.11 association attempt, after five consecutive failures
by entering this command:
config wps client-exclusion 802.11-assoc {enable | disable}
Step 2 Enable or disable the controller to exclude clients on the sixth 802.11 authentication attempt, after five consecutive
failures by entering this command:
config wps client-exclusion 802.11-auth {enable | disable}
Step 3 Enable or disable the controller to exclude clients on the fourth 802.1X authentication attempt, after three consecutive
failures by entering this command:
config wps client-exclusion 802.1x-auth {enable | disable}
Step 4 Configure the controller to exclude clients that reaches the maximum failure 802.1X authentication attempt with the
RADIUS server by entering this command:
config wps client-exclusion 802.1x-auth max-1x-aaa-fail-attempts
You can configure the maximum failure 802.1X authentication attempt from 1 to 3 and the default value is 3.
Step 5 Enable or disable the controller to exclude clients if the IP address is already assigned to another device by entering this
command:
config wps client-exclusion ip-theft {enable | disable}
Step 6 Enable or disable the controller to exclude clients on the fourth web authentication attempt, after three consecutive
failures by entering this command:
config wps client-exclusion web-auth {enable | disable}
Step 7 Enable or disable the controller to exclude clients for all of the above reasons by entering this command:
config wps client-exclusion all {enable | disable}
Step 8 Use the following command to add or delete client exclusion entries.
config exclusionlist {add mac-addr description | delete mac-addr | description mac-addr description}
Step 9 Save your changes by entering this command:
save config
Step 10 See a list of clients that have been dynamically excluded, by entering this command:
show exclusionlist
Information similar to the following appears:
Auto-Immune
Auto-Immune.................................... Disabled
Signature Policy
Signature Processing........................ Enabled
Note The VLAN feature only supports MAC filtering, 802.1X, and WPA. The VLAN feature
does not support web authentication or IPsec.
• Tunnel Attributes.
Note When any of the other RADIUS attributes (QoS-Level, ACL-Name, Interface-Name,
or VLAN-Tag), which are described later in this section, are returned, the Tunnel
Attributes must also be returned.
The operating system’s local MAC filter database has been extended to include the interface name, allowing
local MAC filters to specify to which interface the client should be assigned. A separate RADIUS server can
also be used, but the RADIUS server must be defined using the Security menus.
0 1 2 3
0 1 2 3 4 5 6 7 8 9 0 1 2 3 4 5 6 7 8 9 0 1 2 3 4 5 6 7 8 9 0 1
+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
| Type | Length | Vendor-Id
+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
Vendor-Id (cont.) | Vendor type | Vendor length |
+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
| QoS Level |
+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
ACL-Name
This attribute indicates the ACL name to be applied to the client. A summary of the ACL-Name Attribute
format is shown below. The text boxes are transmitted from left to right.
0 1 2 3
0 1 2 3 4 5 6 7 8 9 0 1 2 3 4 5 6 7 8 9 0 1 2 3 4 5 6 7 8 9 0 1
+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
| Type | Length | Vendor-Id
+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
Vendor-Id (cont.) | Vendor type | Vendor length |
+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
| ACL Name...
+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-
Interface Name
This attribute indicates the VLAN Interface a client is to be associated to. A summary of the Interface-Name
Attribute format is shown below. The text boxes are transmitted from left to right.
0 1 2 3
0 1 2 3 4 5 6 7 8 9 0 1 2 3 4 5 6 7 8 9 0 1 2 3 4 5 6 7 8 9 0 1
+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
| Type | Length | Vendor-Id
+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
Vendor-Id (cont.) | Vendor type | Vendor length |
+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
| Interface Name...
+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-
Note This Attribute only works when MAC filtering is enabled or if 802.1X or WPA is used
as the security policy.
VLAN Tag
This attribute indicates the group ID for a particular tunneled session and is also known as the
Tunnel-Private-Group-ID attribute.
This attribute might be included in the Access-Request packet if the tunnel initiator can predetermine the
group resulting from a particular connection and should be included in the Access-Accept packet if this tunnel
session is to be treated as belonging to a particular private group. Private groups may be used to associate a
tunneled session with a particular group of users. For example, it may be used to facilitate routing of unregistered
IP addresses through a particular interface. It should be included in Accounting-Request packets which contain
Acct-Status-Type attributes with values of either Start or Stop and which pertain to a tunneled session.
A summary of the Tunnel-Private-Group-ID Attribute format is shown below. The text boxes are transmitted
from left to right.
0 1 2 3
0 1 2 3 4 5 6 7 8 9 0 1 2 3 4 5 6 7 8 9 0 1 2 3 4 5 6 7 8 9 0 1
+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
| Type | Length | Tag | String...
+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
Note When any of the other RADIUS attributes (QoS-Level, ACL-Name, Interface-Name,
or VLAN-Tag) are returned, the Tunnel Attributes must also be returned.
Tunnel Attributes
RFC 2868 defines RADIUS tunnel attributes used for authentication and authorization, and RFC2867 defines
tunnel attributes used for accounting. Where the IEEE 802.1X authenticator supports tunneling, a compulsory
tunnel may be set up for the Supplicant as a result of the authentication.
In particular, it may be desirable to allow a port to be placed into a particular VLAN, defined in IEEE 8021Q,
based on the result of the authentication. This configuration can be used, for example, to allow a wireless host
to remain on the same VLAN as it moves within a campus network.
The RADIUS server typically indicates the desired VLAN by including tunnel attributes within the
Access-Accept. However, the IEEE 802.1X authenticator may also provide a hint as to the VLAN to be
assigned to the Supplicant by including Tunnel attributes within the AccessRequest.
For use in VLAN assignment, the following tunnel attributes are used:
• Tunnel-Type=VLAN (13)
• Tunnel-Medium-Type=802
• Tunnel-Private-Group-ID=VLANID
The VLAN ID is 12 bits, with a value between 1 and 4094, inclusive. Because the Tunnel-Private-Group-ID
is of type String as defined in RFC 2868, for use with IEEE 802.1X, the VLANID integer value is encoded
as a string.
When Tunnel attributes are sent, it is necessary to fill in the Tag text box. As noted in RFC 2868, section 3.1:
• The Tag text box is one octet in length and is intended to provide a means of grouping attributes in the
same packet that refer to the same tunnel. Valid values for this text box are 0x01 through 0x1F, inclusive.
If the Tag text box is unused, it must be zero (0x00).
Note From Release 7.5, the upstream AAA override rate limiting value is same as the downstream AAA override
rate limiting value.
interface, or disable and then reenable the WLAN after you apply the interface so that the clients can
reauthenticate.
• If the ACL returned from the AAA server does not exist on the controller or if the ACL is configured
with an incorrect name, then the clients are not allowed to be authenticated.
• With FlexConnect local switching, Multicast is forwarded only for the VLAN that the SSID is mapped
to and not to any overridden VLANs. Therefore, IPv6 does not work as expected because Multicast
traffic is forwarded from the incorrect VLAN.
• When the interface group is mapped to a WLAN and clients connect to the WLAN, the client does not
get the IP address in a round robin fashion. The AAA override with interface group is supported.
• Most of the configuration for allowing AAA override is done at the RADIUS server, where you should
configure the Access Control Server (ACS) with the override properties you would like it to return to
the controller (for example, Interface-Name, QoS-Level, and VLAN-Tag).
• On the controller, enable the Allow AAA Override configuration parameter using the GUI or CLI.
Enabling this parameter allows the controller to accept the attributes returned by the RADIUS server.
The controller then applies these attributes to its clients.
• During Layer2 authentication if AAA override is enabled, local policies are not applied and the override
takes precedence.
• Cisco TrustSec security group tag is not applied until you enable AAA override on a WLAN.
Updating the RADIUS Server Dictionary File for Proper QoS Values
If you are using a Steel-Belted RADIUS (SBR), FreeRadius, or similar RADIUS server, clients may not obtain
the correct QoS values after the AAA override feature is enabled. For these servers, which allow you to edit
the dictionary file, you need to update the file to reflect the proper QoS values: Silver is 0, Gold is 1, Platinum
is 2, and Bronze is 3. To update the RADIUS server dictionary file, follow these steps:
Note This issue does not apply to the Cisco Secure Access Control Server (ACS).
################################################################################
# CiscoWLAN.dct- Cisco Wireless Lan Controllers
#
# (See README.DCT for more details on the format of this file)
################################################################################
################################################################################
# CiscoWLAN.dct - Cisco WLC dictionary
##############################################################################
3 Open the dictiona.dcm file (in the same directory) and add the line “@ciscowlan.dct.”
4 Save and close the dictiona.dcm file.
5 Open the vendor.ini file (in the same directory) and add the following text:
ensuring that the radio goes off-channel more frequently, which improves the chances of rogue detection.
However, the access point will still spend about 50 milliseconds on each channel.
• Rogue detection is disabled by default for OfficeExtend access points because these access points, which
are deployed in a home environment, are likely to detect a large number of rogue devices.
• Client card implementations might mitigate the effectiveness of ad hoc containment.
• It is possible to classify and report rogue access points through the use of rogue states and user-defined
classification rules that enable rogues to automatically move between states.
• Each controller limits the number of rogue containment to three per radio (or six per radio for access
points in the monitor mode).
• Rogue Location Discovery Protocol (RLDP) detects rogue access points that are configured for open
authentication.
• RLDP detects rogue access points that use a broadcast Basic Service Set Identifier (BSSID), that is, the
access point broadcasts its Service Set Identifier in beacons.
• RLDP detects only those rogue access points that are on the same network. If an access list in the network
prevents the sending of RLDP traffic from the rogue access point to the controller, RLDP does not work.
• RLDP does not work on 5-GHz dynamic frequency selection (DFS) channels. However, RLDP works
when the managed access point is in the monitor mode on a DFS channel.
• If RLDP is enabled on mesh APs, and the APs perform RLDP tasks, the mesh APs are dissociated from
the controller. The workaround is to disable RLDP on mesh APs.
• If RLDP is enabled on nonmonitor APs, client connectivity outages occur when RLDP is in process.
• If the rogue is manually contained, the rogue entry is retained even after the rogue expires.
• If the rogue is contained by any other means, such as auto, rule, and AwIPS preventions, the rogue entry
is deleted when it expires.
• The controller will request to AAA server for rogue client validation only once. As a result, if rogue
client validation fails on the first attempt then the rogue client will not be detected as a threat any more.
To avoid this, add the valid client entries in the authentication server before enabling Validate Rogue
Clients Against AAA.
• In the 7.4 and earlier releases, if a rogue that was already classified by a rule was not reclassified. In the
7.5 release, this behavior is enhanced to allow reclassification of rogues based on the priority of the
rogue rule. The priority is determined by using the rogue report that is received by the controller.
• All rogues that are marked as friendly or contained state (due to auto or rule or manual) are stored in
the flash memory of the controller. When you reboot the controller loaded with Release 7.4, these rogues
are shown as manually changed. If you wish to reboot the controller, you need to clear all rogue APs
and rogue adhoc from the controller, save the configuration, and then reboot the controller.
• All rogues that are marked as friendly or contained state (only due to manual) are stored in the flash
memory of the controller. If you upgrade the controller from the Release 7.4 to 7.6 or later versions,
then all rogues stored in the Release 7.4 are shown as manually classified (if friendly classified) or
manually contained. Hence after upgrading the controller from the Release 7.4 to 7.6 or later versions,
you need to delete all rogue APs and rogue adhoc from the controller and then start configuring rogue
detection.
• A FlexConnect AP (with rogue detection enabled) in the connected mode takes the containment list
from the controller. If auto-contain SSID and auto contain adhoc are set in the controller, then these
configurations are set to all FlexConnect APs in the connected mode and the AP stores it in its memory.
When the FlexConnect AP moves to a standalone mode, the following tasks are performed:
◦The containment set by the controller continues.
◦If the FlexConnect AP detects any rogue AP that has same SSID as that of infra SSID (SSID
configured in the controller that the FlexConnect AP is connected to), then containment gets started
if auto contain SSID was enabled from the controller before moving to the standalone mode.
◦If the FlexConnect AP detects any adhoc rogue, containment gets started if auto-contain adhoc
was enabled from the controller when it was in the connected mode.
When the standalone FlexConnect AP moves back to the connected mode, then the following tasks are
performed:
◦All containment gets cleared.
◦Containment initiated from the controller will take over.
• The rogue detector AP fails to co-relate and contain the wired rogue AP on a 5Mhz channel because the
MAC address of the rogue AP for WLAN, LAN, 11a radio and 11bg radio are configured with a difference
of +/-1 of the rogue BSSID. In the 8.0 release, this behavior is enhanced by increasing the range of MAC
address, that the rogue detector AP co-relates the wired ARP MAC and rogue BSSID, by +/-3.
• The rogue access points with open authentication can be detected on wire. The NAT wired or rogue
wired detection is not supported in by WLC (both RLDP and rogue detector AP). The non-adjacent
MAC address is supported by rogue detector mode of AP and not by RLDP.
• In a High Availability scenario, if the rogue detection security level is set to either High or Critical, the
rogue timer on the standby Cisco WLC starts only after the rogue detection pending stabilization time,
which is 300 seconds. Therefore, the active configurations on the standby Cisco WLC are reflected only
after 300 seconds.
Note A rogue AP or client or adhoc containment configuration is not saved after the reload. You have to configure
all the rogues again after the reload.
Note No separate command exists for controlling rogue client traps. However, you can enable or disable rogue
client traps using the config trapflags rogueap {enable | disable} command, which is also used for rouge
APs. In GUI configuration also, you should use the rogue AP flag under
Management->SNMP->TrapControl->Security->Rogue AP to control rogue clients.
to the rogue AP as a client. The AP then tries to obtain an IP address from the rogue AP and forwards a User
Datagram Protocol (UDP) packet (port 6352) that contains the local AP and rogue connection information to
the controller through the rogue AP. If the controller receives this packet, the alarm is set to notify the network
administrator that a rogue AP was discovered on the wired network with the RLDP feature.
RLDP has 100 % accuracy in rouge AP detection. It detects Open APs and NAT APs.
Note Use the debug dot11 rldp enable command in order to check if the Lightweight AP associates and receives
a DHCP address from the rogue AP. This command also displays the UDP packet sent by the Lightweight
AP to the controller.
A sample of a UDP (destination port 6352) packet sent by the Lightweight AP is shown here: 0020 0a 01 01
0d 0a 01 .......(.*...... 0030 01 1e 00 07 85 92 78 01 00 00 00 00 00 00 00 00 ......x......... 0040 00 00 00 00 00
00 00 00 00 00
The first 5 bytes of the data contain the DHCP address given to the local mode AP by the rogue AP. The next
5 bytes are the IP address of the controller, followed by 6 bytes that represent the rogue AP MAC address.
Then, there are 18 bytes of zeroes.
Steps of how RLDP works are listed here:
1 Identify the closest Unified AP to the rogue using signal strength values.
2 The AP then connects to the rogue as a WLAN client, attempting three associations before timing out.
3 If association is successful, the AP then uses DHCP to obtain an IP address.
4 If an IP address was obtained, the AP (acting as a WLAN client) sends a UDP packet to each of the
controller's IP addresses.
5 If the controller receives even one of the RLDP packets from the client, that rogue is marked as on-wire
with a severity of critical.
Note The RLDP packets are unable to reach the controller if filtering rules are placed between the controller's
network and the network where the rogue device is located.
Caveats of RLDP:
• RLDP only works with open rogue APs broadcasting their SSID with authentication and encryption
disabled.
• RLDP requires that the Managed AP acting as a client is able to obtain an IP address via DHCP on the
rogue network.
• Manual RLDP can be used to attempt an RLDP trace on a rogue multiple number of times.
• During RLDP process, the AP is unable to serve clients. This negatively impacts performance and
connectivity for local mode APs. To avoid this case, RLDP can be selectively enabled for Monitor Mode
AP only.
• RLDP does not attempt to connect to a rogue AP operating in a 5GHz DFS channel.
Note RLDP is not supported for use with Cisco autonomous rogue access points. These access points drop the
DHCP Discover request sent by the RLDP client. Also, RLDP is not supported if the rogue access point
channel requires dynamic frequency selection (DFS). If the automatic RLDP attempt does not detect the
rogue (due to a noisy RF environment, for example), the controller does not retry. However, you can
initiate RLDP manually on a rogue device.
A rogue access point is moved to a contained state either automatically or manually. The controller selects
the best available access point for containment and pushes the information to the access point. The access
point stores the list of containments per radio. For auto containment, you can configure the controller to use
only the monitor mode access point. The containment operation occurs in the following two ways:
• The container access point goes through the list of containments periodically and sends unicast
containment frames. For rogue access point containment, the frames are sent only if a rogue client is
associated.
• Whenever a contained rogue activity is detected, containment frames are transmitted.
Individual rogue containment involves sending a sequence of unicast disassociation and deauthentication
frames.
Step 1 Make sure that rogue detection is enabled on the corresponding access points. Rogue detection is enabled by default for
all access points joined to the controller (except for OfficeExtend access points). However, you can enable or disable
rogue detection for individual access points by selecting or unselecting the Rogue Detection check box on the All APs
> Details for (Advanced) page.
Step 2 Choose Security > Wireless Protection Policies > Rogue Policies > General.
The Rogue Policies page is displayed.
Step 3 Choose the Rogue Detection Security Level from the following options:
• Low—Basic rogue detection for small-scale deployments.
• High—Basic rogue detection with auto containment for medium-scale deployments.
• Critical—Basic rogue detection with auto containment and RLDP for highly sensitive deployments.
• Custom
Note For auto RLDP, set the security level to Custom mode. Do not enable scheduling for RLDP even in the
Custom mode.
Step 4 Choose one of the following options from the Rogue Location Discovery Protocol drop-down list:
• Disable—Disables RLDP on all the access points. This is the default value.
• All APs—Enables RLDP on all the access points.
• Monitor Mode APs—Enables RLDP only on the access points in the monitor mode.
Step 5 In the Expiration Timeout for Rogue AP and Rogue Client Entries text box, enter the number of seconds after which
the rogue access point and client entries expire and are removed from the list. The valid range is 240 to 3600 seconds,
and the default value is 1200 seconds.
Note If a rogue access point or client entry times out, it is removed from the controller only if its rogue state is Alert
or Threat for any classification type.
Step 6 To use the AAA server or local database to validate if rogue clients are valid clients, select the Validate Rogue Clients
Against AAA check box. By default, the check box is unselected.
Note To validate a rogue client against AAA, the format of the Cisco AVP pair is mandatory. The free RADIUS
format is:
• e09d3166fb2c Cleartext-Password := "e09d3166fb2c"
• Cisco-AVPair := "rogue-ap-state=threat"
Step 7 To use the Cisco Mobility Services Engine (MSE) that has the rogue client details to validate the clients, select the
Validate Rogue Clients Against MSE check box.
MSE responds with information about whether the rogue client is a valid learned client or not. The controller can contain
or consider the rogue client as a threat.
Step 8 If necessary, select the Detect and Report Ad-Hoc Networks check box to enable ad hoc rogue detection and reporting.
By default, the check box is selected.
Step 9 In the Rogue Detection Report Interval text box, enter the time interval, in seconds, at which APs sends the rogue
detection report to the controller. The valid range is 10 to 300 seconds, and the default value is 10 seconds.
Step 10 In the Rogue Detection Minimum RSSI text box, enter the minimum Received Signal Strength Indicator (RSSI) value
for APs to detect the rogue and for a rogue entry to be created in the controller. The valid range is –128 dBm to –0 dBm,
and the default value is 0 dBm.
Note This feature is applicable to all the AP modes. There can be many rogues with weak RSSI values that do not
provide any valuable information in rogue analysis. Therefore, you can use this option to filter rogues by
specifying the minimum RSSI value at which APs detect rogues.
Step 11 In the Rogue Detection Transient Interval text box, enter the time interval at which a rogue should be scanned for by
the AP after the first time the rogue is scanned. After the rogue is scanned for consistently, updates are sent periodically
to the controller. Thus, the APs filter the transient rogues, which are active for a short period and are then silent. The
valid range is between 120 to 1800 seconds, and the default value is 0.
The rogue detection transient interval is applicable to the monitor mode APs only.
This feature has the following advantages:
• Rogue reports from APs to the controller are shorter.
• Transient rogue entries are avoided in the controller.
• Unnecessary memory allocation for transient rogues is avoided.
Step 12 In the Rogue Client Threshold text box, enter the threshold value. A value of 0 disables the rogue client threshold
parameter.
Step 13 Enable or disable the Rogue Containment Automatic Rate Selection check box.
Using this option, you can optimize the rate to use the best rate for the target rogue. The AP selects the best rate based
on rogue RSSI.
Step 14 If you want the controller to automatically contain certain rogue devices, enable the following parameters. By default,
these parameters are in disabled state.
Caution When you select any of the Auto Contain parameters and click Apply, the following message is displayed:
“Using this feature may have legal consequences. Do you want to continue?”
The 2.4-GHz and 5-GHz frequencies in the Industrial, Scientific, and Medical (ISM) band are open to the
public and can be used without a license. As such, containing devices on another party’s network could have
legal consequences.
• Auto Containment Level—Set the auto containment level. By default, the auto containment level is set to 1.
If you choose Auto, the controller dynamically chooses the number of APs required for effective containment.
• Auto Containment only for Monitor mode APs—Configure the monitor mode access points for auto-containment.
• Auto Containment on FlexConnect Standalone—Configure the FlexConnect Standalone mode access points for
auto containment.
Note The auto-containment is continued if it was configured when the AP was in connected FlexConnect mode.
After the standalone AP reassociates with the controller, auto containment is stopped. The configuration
on the controller the AP is associated with determines the future course of action. You can also configure
auto containment on the ad hoc SSIDs and managed SSIDs on FlexConnect APs.
• Rogue on Wire—Configure the auto containment of rogues that are detected on the wired network.
• Using Our SSID—Configure the auto containment of rogues that are advertising your network’s SSID. If you
leave this parameter unselected, the controller only generates an alarm when such a rogue is detected.
• Valid Client on Rogue AP—Configure the auto containment of a rogue access point to which trusted clients are
associated. If you leave this parameter unselected, the controller only generates an alarm when such a rogue is
detected.
• AdHoc Rogue AP—Configure the auto containment of ad hoc networks detected by the controller. If you leave
this parameter unselected, the controller only generates an alarm when such a network is detected.
Step 1 Ensure that rogue detection is enabled on the desired access points. Rogue detection is enabled by default for all the
access points that are associated with the controller. You can enable or disable rogue detection for individual access
points by entering this command:
config rogue detection {enable | disable} cisco-ap command.
Note To see the current rogue detection configuration for a specific access point, enter the show ap config general
Cisco_AP command.
Note Rogue detection is disabled by default for OfficeExtend access points because these access points, which are
deployed in a home environment, are likely to detect a large number of rogue devices.
Step 2 Configure the rogue detection security level by entering this command:
config rogue detection security-level {critical | custom | high | low}
• critical—Basic rogue detection with auto containment and RLDP for highly sensitive deployments.
• high—Basic rogue detection with auto containment for medium-scale deployments.
• low—Basic rogue detection for small-scale deployments.
Step 4 Specify the number of seconds after which the rogue access point and client entries expire and are removed from the list
by entering this command:
config rogue ap timeout seconds
The valid range for the seconds parameter is 240 to 3600 seconds (inclusive). The default value is 1200 seconds.
Note If a rogue access point or client entry times out, it is removed from the controller only if its rogue state is Alert
or Threat for a classification type.
Step 5 Enable or disable ad hoc rogue detection and reporting by entering this command:
config rogue adhoc {enable | disable}
Step 6 Enable or disable the AAA server or local database to validate if rogue clients are valid clients by entering this command:
config rogue client aaa {enable | disable}
Step 7 Enable or disable the use of MSE that has the rogue client details to validate the clients by entering this command:
config rogue client mse {enable | disable}
Step 8 Specify the time interval, in seconds, at which APs should send the rogue detection report to the controller by entering
this command:
config rogue detection monitor-ap report-interval time in sec
The valid range for the time in sec parameter is 10 seconds to 300 seconds. The default value is 10 seconds.
Note This feature is applicable only to the monitor mode
APs.
Step 9 Specify the minimum RSSI value that rogues should have for APs to detect them and for the rogue entries to be created
in the controller by entering this command:
config rogue detection min-rssi rssi in dBm
The valid range for the rssi in dBm parameter is –128 dBm to 0 dBm. The default value is 0 dBm.
Note This feature is applicable to all the AP modes. There can be many rogues with very weak RSSI values that do
not provide any valuable information in rogue analysis. Therefore, you can use this option to filter rogues by
specifying the minimum RSSI value at which APs should detect rogues.
Step 10 Specify the time interval at which rogues have to be consistently scanned for by APs after the first time the rogues are
scanned for by entering this command:
config rogue detection monitor-ap transient-rogue-interval time in sec
The valid range for the time in sec parameter is 120 seconds to 1800 seconds. The default value is 0.
Note This feature is applicable only to the monitor mode APs.
Using the transient interval values, you can control the time interval at which APs should scan for rogues. APs
can also filter rogues based on their transient interval values.
This feature has the following advantages:
• Rogue reports from APs to the controller are shorter.
• Transient rogue entries are avoided in the controller.
• Unnecessary memory allocation for transient rogues are avoided.
Step 11 If you want the controller to automatically contain certain rogue devices, enter these commands.
Caution When you enter any of these commands, the following message is displayed: Using this feature
may have legal consequences. Do you want to continue? The 2.4-GHz and 5-GHz
frequencies in the Industrial, Scientific, and Medical (ISM) band are open to the public and can be used
without a license. As such, containing devices on another party’s network could have legal consequences.
• config rogue ap rldp enable auto-contain—Automatically contains the rogues that are detected on the wired
network.
• config rogue ap ssid auto-contain—Automatically contains the rogues that are advertising your network’s SSID.
Note If you want the controller to only generate an alarm when such a rogue is detected, enter the config rogue
ap ssid alarm command.
• config rogue ap valid-client auto-contain—Automatically contains a rogue access point to which trusted clients
are associated.
Note If you want the controller to only generate an alarm when such a rogue is detected, enter the config rogue
ap valid-client alarm command.
• config rogue adhoc auto-contain—Automatically contains ad hoc networks detected by the controller.
Note If you want the controller to only generate an alarm when such a network is detected, enter the config
rogue adhoc alert command.
• config rogue auto-contain level level monitor_mode_ap_only—Sets the auto containment level for the monitor
mode access points. The default value is 1. If you enter the level as 0, then the controller dynamically chooses the
number of APs required for effective containment.
• config rogue containment flexconnect {enable | disable}—Sets the auto containment options for standalone
FlexConnect access points.
Note The auto containment is continued if the auto containment was configured when the AP was in the connected
FlexConnect mode. After the standalone AP is reassociated with the controller, auto containment is stopped
and the future course of action is determined by the configuration on the controller the AP is associated
with. You can also configure auto containment on ad hoc SSIDs and managed SSIDs on FlexConnect
APs.
• config rogue containment auto-rate {enable | disable}—Sets the auto rate for containment of rogues.
Note When you configure RLDP scheduling, it is assumed that the scheduling will occur in the future, that is, after
the configuration is saved.
Step 14 Save your changes by entering this command:
save config
Note Rogue client detection on non monitor AP on serving channel was not done until 8.1 Release . From Release
8.1 onwards, serving channel rogue client detection will happen only if WIPS submode is turned on non monitor
AP's.
Note Manual classification and classification that is the result of auto-containment or rogue-on-wire overrides
the rogue rule. If you have manually changed the class and/or the state of a rogue AP, then to apply rogue
rules to the AP, you must change it to unclassified and alert condition.
Note If you manually move any rogue device to contained state (any class) or friendly state, this information
is stored in the standby Cisco WLC flash memory; however, the database is not updated. When HA
switchover occurs, the rogue list from the previously standby Cisco WLC flash memory is loaded.
By default, none of the classification rules are enabled. Therefore, all unknown access points are categorized
as Unclassified. When you create a rule, configure conditions for it, and enable the rule, the unclassified access
points are reclassified. Whenever you change a rule, it is applied to all access points (friendly, malicious,
custom, and unclassified) in the Alert state only.
You can configure up to 64 rogue classification rules per controller.
You can also apply rogue rules to ad hoc rogues except for client count condition.
The number of rogue clients that can be stored in the database table of a rogue access point is 256.
If a rogue AP or an ad hoc rogue is classified because of an RSSI rogue rule condition, the RSSI value that
caused the trigger is displayed on the controller GUI/CLI. The controller includes the classified RSSI, the
classified AP MAC address, and rule name in the trap. A new trap is generated for every new classification
or change of state due to rogue rule but³ is rate limited to every half hour for every rogue AP or ad hoc rogue.
However, if there is a change of state in containment by rogue rule, the trap is sent immediately. The ‘classified
by,’ ‘classified at,’ and ‘classified by rule name’ are valid for the non-default classification types, which are
Friendly, Malicious, and Custom classifications. For the unclassified types, these fields are not displayed.
Note For the RSSI condition of rogue rule, reclassification occurs only if the RSSI change is more than 2 dBm
of the configured RSSI value.
The rogue rule may not work properly if friendly rogue rule is configured with RSSI as a condition. Then,
you need to modify the rules with the expectation that friendly rule is using maximum RSSI and modify rules
accordingly.
When the controller receives a rogue report from one of its managed access points, it responds as follows:
1 The controller verifies that the unknown access point is in the friendly MAC address list. If it is, the
controller classifies the access point as Friendly.
2 If the unknown access point is not in the friendly MAC address list, the controller starts applying rogue
classification rules.
3 If the rogue is already classified as Malicious, Alert or Friendly, Internal or External, the controller does
not reclassify it automatically. If the rogue is classified differently, the controller reclassifies it automatically
only if the rogue is in the Alert state.
4 The controller applies the first rule based on priority. If the rogue access point matches the criteria specified
by the rule, the controller classifies the rogue according to the classification type configured for the rule.
5 If the rogue access point does not match any of the configured rules, the controller classifies the rogue as
Unclassified.
6 The controller repeats the previous steps for all rogue access points.
7 If RLDP determines that the rogue access point is on the network, the controller marks the rogue state as
Threat and classifies it as Malicious automatically, even if no rules are configured. You can then manually
contain the rogue (unless you have configured RLDP to automatically contain the rogue), which would
change the rogue state to Contained. If the rogue access point is not on the network, the controller marks
the rogue state as Alert, and you can manually contain the rogue.
8 If desired, you can manually move the access point to a different classification type and rogue state.
Malicious
• Alert—The unknown access point is moved to Alert if it is not in the neighbor
list or in the user-configured friendly MAC list.
• Contained—The unknown access point is contained.
Custom
• Alert—The unknown access point is moved to Alert if it is not in the neighbor
list or in the user-configured friendly MAC list.
• Contained—The unknown access point is contained.
Unclassified
• Pending—On first detection, the unknown access point is put in the Pending
state for 3 minutes. During this time, the managed access points determine if the
unknown access point is a neighbor access point.
• Alert—The unknown access point is moved to Alert if it is not in the neighbor
list or in the user-configured friendly MAC list.
• Contained—The unknown access point is contained.
• Contained Pending—The unknown access point is marked Contained, but the
action is delayed due to unavailable resources.
The classification and state of the rogue access points are configured as follows:
• From Known to Friendly, Internal
• From Acknowledged to Friendly, External
• From Contained to Malicious, Contained
If the rogue state is Contained, you have to uncontain the rogue access point before you can change the
classification type. If you want to move a rogue access point from Malicious to Unclassified, you must delete
the access point and allow the controller to reclassify it.
• Transition of the rogue's state from friendly to malicious is possible by multiple rogue rules if some
attribute is missing in new rogue report.
• Transition of the rogue's state from malicious to any other classification is not possible by any rogue
rule.
• If a rogue AP is classified as friendly, it means that the rogue AP exists in the vicinity, is a known AP,
and need not be tracked. Therefore, all the rogue clients are either deleted or not tracked if they are
associated with the friendly rogue AP.
Step 1 Choose Security > Wireless Protection Policies > Rogue Policies > Rogue Rules to open the Rogue Rules page.
Any rules that have already been created are listed in priority order. The name, type, and status of each rule is provided.
Note To delete a rule, hover your cursor over the blue drop-down arrow for that rule and click Remove.
• Friendly
• Malicious
• Custom
d) Configure the notification when the rule is matched from the Notify drop-down list to All, Global, Local, or None.
Note Rogue Rule Notification options All, Global, Local, and None can control only the following rogue traps
mentioned:
• Rogue AP Detected (Rogue AP: XX:XX:XX:XX:XX:XX detected on Base Radio MAC:
XX:XX:XX:XX:XX:XX Interface no: 0(1) Channel: 6 RSSI: 45 SNR: 10 Classification: unclassified,
State: alert, RuleClassified : unclassified, Severity Score: 100, RuleName: rule1, Classified AP MAC:
XX:XX:XX:XX:XX:XX, Classified RSSI: 45)
• Rogue Adhoc Detected (Adhoc Rogue : XX:XX:XX:XX:XX:XX detected on Base Radio MAC :
XX:XX:XX:XX:XX:XX Interface no: 0(1) on Channel 6 with RSSI: 45 and SNR: 10 Classification:
unclassified, State: alert, RuleClassified: unclassified, Severity Score: 100, RuleName: rule1,Classified
APMAC: XX:XX:XX:XX:XX:XX, Classified RSSI: 45)
• Rogue AP contained (Rogue AP: Rogue with MAC Address: XX:XX:XX:XX:XX:XX has been
contained due to rule with containment Level : 1)
• Rogue AP clear contained (Rogue AP: Rogue with MAC Address: XX:XX:XX:XX:XX:XX is no
longer contained due to rule
e) Configure the state of the rogue AP when the rule is matched from the State drop-down list.
f) If you choose the Rule Type as Custom, enter the Severity Score and the Classification Name.
g) Click Add to add this rule to the list of existing rules, or click Cancel to discard this new rule.
Step 3 Edit a rule as follows:
a) Click the name of the rule that you want to edit. The Rogue Rule > Edit page appears.
b) From the Type drop-down list, choose from the following options to classify rogue access points matching this rule:
• Friendly
• Malicious
• Custom
c) Configure the notification when the rule is matched from the Notify drop-down list to All, Global, Local, or None.
d) Configure the state of the rogue AP when the rule is matched from the State drop-down list.
e) From the Match Operation text box, choose one of the following:
Match All—If this rule is enabled, a detected rogue access point must meet all of the conditions specified by the rule
in order for the rule to be matched and the rogue to adopt the classification type of the rule.
Match Any—If this rule is enabled, a detected rogue access point must meet any of the conditions specified by the
rule in order for the rule to be matched and the rogue to adopt the classification type of the rule. This is the default
value.
f) To enable this rule, select the Enable Rule check box. The default value is unselected.
g) If you choose the Rule Type as Custom, enter the Severity Score and the Classification Name.
h) From the Add Condition drop-down list, choose one or more of the following conditions that the rogue access point
must meet and click Add Condition.
• SSID—Requires that the rogue access point have a specific user-configured SSID. If you choose this option,
enter the SSID in the User Configured SSID text box, and click Add SSID.
Note To delete an SSID, highlight the SSID and click
Remove.
• RSSI—Requires that the rogue access point have a minimum received signal strength indication (RSSI) value.
For example, if the rogue access point has an RSSI that is greater than the configured value, then the access
point could be classified as malicious. If you choose this option, enter the minimum RSSI value in the Minimum
RSSI text box. The valid range is –95 to –50 dBm (inclusive), and the default value is 0 dBm.
• Duration—Requires that the rogue access point be detected for a minimum period of time. If you choose this
option, enter a value for the minimum detection period in the Time Duration text box. The valid range is 0 to
3600 seconds (inclusive), and the default value is 0 seconds.
• Client Count—Requires that a minimum number of clients be associated to the rogue access point. For example,
if the number of clients associated to the rogue access point is greater than or equal to the configured value,
then the access point could be classified as malicious. If you choose this option, enter the minimum number of
clients to be associated to the rogue access point in the Minimum Number of Rogue Clients text box. The
valid range is 1 to 10 (inclusive), and the default value is 0.
• No Encryption—Requires that the rogue access point’s advertised WLAN does not have encryption enabled.
If a rogue access point has encryption disabled, it is likely that more clients will try to associate to it. No further
configuration is required for this option.
Note Cisco Prime Infrastructure refers to this option as “Open Authentication.”
• Managed SSID—Requires that the rogue access point’s managed SSID (the SSID configured for the WLAN)
be known to the controller. No further configuration is required for this option.
Note The SSID and Managed SSID conditions cannot be used with the Match All operation because these
two SSID lists are mutually exclusive. If you define a rule with Match All and have these two conditions
configured, the rogue access points are never classified as friendly or malicious because one of the
conditions can never be met.
You can add up to six conditions per rule. When you add a condition, it appears under the Conditions
section.
Note To delete a condition from this rule, hover your cursor over the blue drop-down arrow for that condition
and click Remove.
• SSID Wildcard—Requires that the rogue access point have a substring of the specific user-configured SSID.
The controller searches the substring in the same occurrence pattern and returns a match if the substring is found
in the whole string of an SSID.
i) Click Apply.
Step 4 Click Save Configuration.
Step 5 If you want to change the order in which rogue classification rules are applied, follow these steps:
1 Click Back to return to the Rogue Rules page.
2 Click Change Priority to access the Rogue Rules > Priority page.
The rogue rules are listed in priority order in the Change Rules Priority text box.
3 Highlight the rule for which you want to change the priority, and click Up to raise its priority in the list or Down to
lower its priority in the list.
4 Continue to move the rules up or down until the rules are in the desired order.
5 Click Apply.
Step 6 Classify any rogue access points as friendly and add them to the friendly MAC address list as follows:
• Choose Security > Wireless Protection Policies > Rogue Policies > Friendly Rogue to open the Friendly Rogue
> Create page.
• In the MAC Address text box, enter the MAC address of the friendly rogue access point.
• Click Apply.
• Click Save Configuration. This access point is added to the controller’s list of friendly access points and should
now appear on the Friendly Rogue APs page.
Caution When you choose to contain a rogue device, the following warning appears: “There may be legal issues
following this containment. Are you sure you want to continue?” The 2.4- and 5-GHz frequencies in the
Industrial, Scientific, and Medical (ISM) band are open to the public and can be used without a license.
As such, containing devices on another party’s network could have legal consequences.
The respective rogue APs pages provide the following information: the MAC address and SSID of the rogue access
point, channel number, the number of radios that detected the rogue access point, the number of clients connected to the
rogue access point, and the current status of the rogue access point.
Note To remove acknowledged rogues from the database, change the rogue state to Alert. If the rogue is no longer
present, the rogue data is deleted from the database in 20 minutes.
Note To delete a rogue access point from one of these pages, hover your cursor over the blue drop-down arrow and
click Remove. To delete multiple rogue access points, select the check box corresponding to the row you want
to delete and click Remove.
Note You can move the Malicious or Unclassified rogue APs that are being contained or were contained back to Alert
state by clicking the Move to Alert button on the respective pages.
Step 3 Get more details about a rogue access point by clicking the MAC address of the access point. The Rogue AP Detail page
appears.
This page provides the following information: the MAC address of the rogue device, the type of rogue device (such as
an access point), whether the rogue device is on the wired network, the dates and times when the rogue device was first
and last reported, and the current status of the device.
The Class Type text box shows the current classification for this rogue access point:
• Friendly—An unknown access point that matches the user-defined friendly rules or an existing known and
acknowledged rogue access point. Friendly access points cannot be contained.
• Malicious—An unknown access point that matches the user-defined malicious rules or is moved manually by the
user from the Friendly or Unclassified classification type.
Note Once an access point is classified as Malicious, you cannot apply rules to it in the future, and it cannot be
moved to another classification type. If you want to move a malicious access point to the Unclassified
classification type, you must delete the access point and allow the controller to reclassify it.
• Unclassified—An unknown access point that does not match the user-defined friendly or malicious rules. An
unclassified access point can be contained. It can also be moved to the Friendly or Malicious classification type
automatically in accordance with user-defined rules or manually by the user.
• Custom—A user-defined classification type that is tied to rogue rules. It is not possible to manually classify a
rogue as Custom. Custom class change can occur only using rogue rules.
Step 4 If you want to change the classification of this device, choose a different classification from the Class Type drop-down
list.
Note A rogue access point cannot be moved to another class if its current state is Contain.
Step 5 From the Update Status drop-down list, choose one of the following options to specify how the controller should respond
to this rogue access point:
• Internal—The controller trusts this rogue access point. This option is available if the Class Type is set to Friendly.
• External—The controller acknowledges the presence of this rogue access point. This option is available if the
Class Type is set to Friendly.
• Contain—The controller contains the offending device so that its signals no longer interfere with authorized clients.
This option is available if the Class Type is set to Malicious or Unclassified.
• Alert—The controller forwards an immediate alert to the system administrator for further action. This option is
available if the Class Type is set to Malicious or Unclassified.
The bottom of the page provides information on both the access points that detected this rogue access point and any
clients that are associated to it. To see more details for any of the clients, click Edit to open the Rogue Client Detail
page.
to which the rogue client is associated, the SSID of the rogue client, the number of radios that detected the rogue client,
the date and time when the rogue client was last reported, and the current status of the rogue client.
Step 9 Obtain more details about a rogue client by clicking the MAC address of the client. The Rogue Client Detail page appears.
This page provides the following information: the MAC address of the rogue client, the MAC address of the rogue access
point to which this client is associated, the SSID and IP address of the rogue client, the dates and times when the rogue
client was first and last reported, and the current status of the rogue client.
Step 10 From the Update Status drop-down list, choose one of the following options to specify how the controller should respond
to this rogue client:
• Contain—The controller contains the offending device so that its signals no longer interfere with authorized clients.
• Alert—The controller forwards an immediate alert to the system administrator for further action.
The bottom of the page provides information on the access points that detected this rogue client.
Step 15 Obtain more details about an ad-hoc rogue by clicking the MAC address of the rogue. The Adhoc Rogue Detail page
appears.
This page provides the following information: the MAC address and BSSID of the ad-hoc rogue, the dates and times
when the rogue was first and last reported, and the current status of the rogue.
Step 16 From the Update Status drop-down list, choose one of the following options to specify how the controller should respond
to this ad-hoc rogue:
• Contain—The controller contains the offending device so that its signals no longer interfere with authorized clients.
• Alert—The controller forwards an immediate alert to the system administrator for further action.
• Internal—The controller trusts this rogue access point.
• External—The controller acknowledges the presence of this rogue access point.
Step 17 From the Maximum number of APs to contain the rogue drop-down list, choose one of the following options to specify
the maximum number of access points used to contain this ad-hoc rogue: 1, 2, 3, or 4.
The bottom of the page provides information on the access points that detected this ad-hoc rogue.
• 1—Specifies targeted rogue access point is contained by one access point. This is the lowest containment level.
• 2—Specifies targeted rogue access point is contained by two access points.
• 3—Specifies targeted rogue access point is contained by three access points.
• 4—Specifies targeted rogue access point is contained by four access points. This is the highest containment level.
config rogue rule add ap priority priority classify custom severity-score classification-name notify {all | global
| local | none} state {alert | contain} rule-name
If you later want to change the priority of this rule and shift others in the list accordingly, enter the config rogue rule
priority priority rule-name command.
If you later want to change the classification of this rule, enter the config rogue rule classify {friendly | malicious |
custom severity-score classification-name} rule-name command.
If you ever want to delete all of the rogue classification rules or a specific rule, enter the {config rogue rule delete {all
| rule-name} command.
Step 3 Configure the state on the rogue AP upon rule match by entering this command:
config rogue rule state {alert | contain | internal | external} rule-name
Step 4 Configure the notification upon rule match by entering this command:
config rogue rule notify {all | global | local | none} rule-name
• client-count—Requires that a minimum number of clients be associated to the rogue access point. For example,
if the number of clients associated to the rogue access point is greater than or equal to the configured value, then
the access point could be classified as malicious. If you choose this option, enter the minimum number of clients
to be associated to the rogue access point for the condition_value parameter. The valid range is 1 to 10 (inclusive),
and the default value is 0.
• managed-ssid—Requires that the rogue access point’s SSID be known to the controller. A condition_value parameter
is not required for this option.
Note You can add up to six conditions per rule. If you ever want to delete all of the conditions or a specific
condition from a rule, enter the config rogue rule condition ap delete all condition_type condition_value
rule_name command.
• wildcard-ssid—Requires that the rogue access point have a wildcard of the specific user-configured SSID. The
controller searches the wildcard in the same occurrence pattern and returns a match if the substring is found in the
whole string of an SSID.
Step 7 Specify whether a detected rogue access point must meet all or any of the conditions specified by the rule in order for
the rule to be matched and the rogue access point to adopt the classification type of the rule by entering this command:
config rogue rule match {all | any} rule_name
Step 11 View the rogue classification rules that are configured on the controller by entering this command:
show rogue rule summary
Step 12 View detailed information for a specific rogue classification rule by entering this command:
show rogue rule detailed rule_name
Note See the Viewing and Classifying Rogue Devices (GUI) section for more information on the rogue-ignore
access point list.
Note A rogue access point cannot be moved to the Friendly class if its current state is Contain.
Note A rogue access point cannot be moved to the Malicious class if its current state is Contain.
Note A rogue access point cannot be moved to the Unclassified class if its current state is Contain.
alert means that the controller forwards an immediate alert to the system administrator for further action.
contain means that the controller contains the offending device so that its signals no longer interfere with
authorized clients.
• Choose the maximum number of access points used to contain the ad-hoc rogue by entering this command:
config rogue ap classify unclassified state contain rogue_ap_mac_address 1, 2, 3, or 4
• 1—Specifies targeted rogue access point will be contained by one access point. This is the lowest
containment level.
• 2—Specifies targeted rogue access point will be contained by two access points.
• 3—Specifies targeted rogue access point will be contained by three access points.
• 4—Specifies targeted rogue access point will be contained by four access points. This is the highest
containment level.
• Specify how the controller should respond to a rogue client by entering one of these commands:
config rogue client alert client_mac_address—The controller forwards an immediate alert to the system
administrator for further action.
config rogue client contain client_mac_address—The controller contains the offending device so that
its signals no longer interfere with authorized clients.
• Specify how the controller should respond to an ad-hoc rogue by entering one these commands:
config rogue adhoc alert rogue_mac_address—The controller forwards an immediate alert to the
system administrator for further action.
config rogue adhoc contain rogue_mac_address—The controller contains the offending device so that
its signals no longer interfere with authorized clients.
config rogue adhoc external rogue_mac_address—The controller acknowledges the presence of this
ad-hoc rogue.
• Configure the classification of ad hoc rogues by entering any one of these commands:
◦Friendly state—config rogue adhoc classify friendly state {internal | external} mac-addr
◦Malicious state—config rogue adhoc classify malicious state {alert | contain} mac-addr
◦Unclassified state—config rogue adhoc classify unclassified state {alert | contain} mac-addr
Speaker mode. To implement the SXP on a network, only the egress distribution switch needs to be
CTS-enabled, and all the other switches can be non-CTS-capable switches.
The SXP runs between any access layer and distribution switch or between two distribution switches. The
SXP uses TCP as the transport layer. CTS authentication is performed for any host (client) joining the network
on the access layer switch similar to an access switch with CTS-enabled hardware. The access layer switch
is not CTS hardware enabled. Therefore, data traffic is not encrypted or cryptographically authenticated when
it passes through the access layer switch. The SXP is used to pass the IP address of the authenticated device,
that is a wireless client, and the corresponding SGT up to the distribution switch. If the distribution switch is
CTS hardware enabled, the switch inserts the SGT into the packet on behalf of the access layer switch. If the
distribution switch is not CTS hardware enabled, the SXP on the distribution switch passes the IP-SGT mapping
to all the distribution switches that have CTS hardware. On the egress side, the enforcement of the RBACL
occurs at the egress L3 interface on the distribution switch.
The following are some guidelines for Cisco TrustSec SXP:
• SXP is supported on the following security policies only:
◦WPA2-dot1x
◦WPA-dot1x
◦MAC Filtering using RADIUS servers
◦Web authentication using RADIUS servers for user authentication
Restrictions on SXP
• SXP is not supported on FlexConnect access points.
• SXP is supported only in centrally switched networks that have central authentication.
• By default, SXP is supported for APs that work in local mode only.
• The configuration of the default password should be consistent for both controller and the switch.
• Fault tolerance is not supported because fault tolerance requires local switching on APs.
• Static IP-SGT mapping for local authentication of users is not supported.
• IP-SGT mapping requires authentication with external ACS servers.
• In auto-anchor/guest-anchor mobility the SGT information passed by the RADIUS server to foreign
WLC can be communicated to the anchor WLC through the EoIP/CAPWAP mobility tunnel. The anchor
WLC can then build the SGT-IP mapping and communicate it to another peer via SXP.
Step 1 Choose Security > TrustSec SXP to open the SXP Configuration page. This page lists the following SXP configuration
details:
• Total SXP Connections—Number of SXP connections that are configured.
• SXP State—Status of SXP connections as either disabled or enabled.
• SXP Mode—SXP mode of the controller. The controller is always set to Speaker mode for SXP connections.
• Default Password—Password for MD5 authentication of SXP messages. We recommend that the password contain
a minimum of 6 characters.
• Default Source IP—IP address of the management interface. SXP uses the default source IP address for all new
TCP connections.
• Retry Period—SXP retry timer. The default value is 120 seconds (2 minutes). The valid range is 0 to 64000
seconds. The SXP retry period determines how often the controller retries for an SXP connection. When an SXP
connection is not successfully set up, the controller makes a new attempt to set up the connection after the SXP
retry period timer expires. Setting the SXP retry period to 0 seconds disables the timer and retries are not attempted.
This page also displays the following information about SXP connections:
• Peer IP Address—The IP address of the peer, that is the IP address of the next hop switch to which the controller
is connected. There is no effect on the existing TCP connections when you configure a new peer connection.
• Source IP Address—The IP address of the source, that is the management IP address of the controller.
• Connection Status—Status of the SXP connection.
Step 2 From the SXP State drop-down list, choose Enabled to enable Cisco TrustSec SXP.
Step 3 Enter the default password that should be used to make an SXP connection. We recommend that the password contain
a minimum of 6 characters.
Step 4 In the Retry Period box, enter the time in seconds that determines how often the Cisco TrustSec software retries for an
SXP connection.
Step 5 Click Apply to commit your changes.
Step 6 Click Refresh Env Data to refresh the environment data.
Step 1 Choose SECURITY > TrustSec SXP and click New to open the SXP Connection > New page.
Step 2 In the Peer IP Address text box, enter the IP address of the next hop switch to which the controller is connected.
Step 3 Click Apply.
• See the list of SXP connections that are configured by entering this command:
show cts sxp connections
Information similar to the following appears:
• Establish connection between the controller and a Cisco Nexus 7000 Series switch by following either
of these steps:
◦Enter the following commands:
1 config cts sxp version sxp version 1 or 2 1
2 config cts sxp disable
3 config cts sxp enable
◦If SXP version 2 is used on the controller and version 1 is used on the Cisco Nexus 7000 Series
switch, an amount of retry period is required to establish the connection. We recommend that you
initially have less interval between connection attempts. The default is 120 seconds.
When these policy attributes match, you can define the following actions:
• Virtual local area network (VLAN)
• Access control list (ACL)
• Quality of Service (QoS) level
• Session timeout value
• Sleeping client timeout value
• Select either AVC profile or role, or both based on local policy attributes defined in the AAA server.
The following are the different ways by which local policies are applied based on a combination of AVC
profile and role defined in the AAA server:
• Both AVC profile and role are derived from the AAA server, the following options are available:
◦If AAA override is enabled, then AVC profile is prioritized and is applied.
◦If AAA override is disabled, then role matching is applied.
• Only role is derived from the AAA server and role matching takes place, the following options are
available:
◦If profile is defined in the policy, then role policy is applied.
◦If profile is not defined in the policy, then AVC profile defined in WLAN is applied.
• Only AVC profile is derived from the AAA server, the following options are available:
◦If AAA override is enabled, then AVC profile received from the AAA server is applied.
◦If AAA override is disabled, then AVC profile defined on the WLAN is applied.
Table 18: Differences Between Cisco Identity Services Engine (ISE) and Controller Profiling Support
ISE Controller
Supports profiling using RADIUS probes, DHCP Supports MAC OUI, DHCP, and HTTP-based
probes, HTTP, and other protocols used to identify profiling.
the client type.
Supports multiple different attributes for the policy Supports VLAN, ACL, Session Timeout, and QoS
action and has an interface to pick and select each of as policy action attributes.
the attributes.
Supports customization of profiling rules with Supports only default profiling rules.
user-defined attributes.
n) Click Apply.
What to Do Next
Apply a local policy that you have created to a WLAN by following these steps:
1 Choose WLANs.
2 Click the corresponding WLAN ID.
The WLANs > Edit page is displayed.
3 Click the Policy-Mapping tab.
4 Enter the Priority Index for a policy.
5 From the Local Policy drop-down list, choose the policy that has to be applied for the WLAN.
6 Click Add.
The priority index and the policy that you choose is listed. You can apply up to 16 policies for a WLAN.
• Configure an action that has to be enforced as part of a policy by entering these commands:
◦ACL action to a policy—config policy policy-name action acl {enable | disable} acl-name
◦QoS average data rate—config policy policy-name action average-data-rate {enable | disable}
rate
◦QoS average real-time data rate—config policy policy-name action average-realtime-rate {enable
| disable} rate
◦QoS burst data rate—config policy policy-name action burst-data-rate {enable | disable} rate
◦QoS burst real-time data rate—config policy policy-name action burst-realtime-rate {enable |
disable} rate
◦QoS action—config policy policy-name action qos {enable | disable} {bronze | gold | platinum
| silver}
◦Session timeout action—config policy policy-name action session-timeout {enable | disable}
timeout-in-seconds
Note Ensure that you configure the Average Data Rate before you configure the Burst Data Rate.
You can configure IDS sensors to detect various types of IP-level attacks in your network. When the sensors
identify an attack, they can alert the controller to shun the offending client. When you add a new IDS sensor,
you register the controller with that IDS sensor so that the controller can query the sensor to get the list of
shunned clients.
Shunned Clients
When an IDS sensor detects a suspicious client, it alerts the controller to shun this client. The shun entry is
distributed to all controllers within the same mobility group. If the client to be shunned is currently joined to
a controller in this mobility group, the anchor controller adds this client to the dynamic exclusion list, and the
foreign controller removes the client. The next time that the client tries to connect to a controller, the anchor
controller rejects the handoff and informs the foreign controller that the client is being excluded.
Step 1 Choose Security > Advanced > CIDS > Sensors to open the CIDS Sensors List page.
Note If you want to delete an existing sensor, hover your cursor over the blue drop-down arrow for that sensor and
choose Remove.
Step 2 Click New to add a new IDS sensor to the list. The CIDS Sensor Add page is displayed.
Step 3 From the Index drop-down list, choose a number (between 1 and 5) to determine the sequence in which the controller
consults the IDS sensors. For example, if you choose 1, the controller consults this IDS sensor first.
Cisco WLC supports up to five IDS sensors.
Step 4 In the Server Address text box, enter the IP address of your IDS server.
Step 5 In the Port text box, enter the number of the HTTPS port through which the controller has to communicate with the IDS
sensor.
We recommend that you set this parameter to 443 because the sensor uses this value to communicate by default. The
default value is 443 and the range is 1 to 65535.
Step 6 In the Username text box, enter the name that the controller uses to authenticate to the IDS sensor.
Note This username must be configured on the IDS sensor and have at least a read-only privilege.
Step 7 In the Password and Confirm Password text boxes, enter the password that the controller uses to authenticate to the
IDS sensor.
Step 8 In the Query Interval text box, enter the time (in seconds) for how often the controller should query the IDS server for
IDS events.
The default is 60 seconds and the range is 10 to 3600 seconds.
Step 9 Check the State check box to register the controller with this IDS sensor or uncheck this check box to disable registration.
The default value is disabled.
Step 10 Enter a 40-hexadecimal-character security key in the Fingerprint text box. This key is used to verify the validity of the
sensor and is used to prevent security attacks.
Note Make sure you include colons that appear between every two bytes within the key. For example, enter
AA:BB:CC:DD.
Step 11 Click Apply. Your new IDS sensor appears in the list of sensors on the CIDS Sensors List page.
Step 12 Click Save Configuration.
Step 1 Choose Security > Advanced > CIDS > Shunned Clients to open the CIDS Shun List page.
This page shows the IP address and MAC address of each shunned client, the length of time that the client’s data packets
should be blocked by the controller as requested by the IDS sensor, and the IP address of the IDS sensor that discovered
the client.
Note The controller does not take any action on shun entries when the corresponding timers have expired. The shun
entry timers are maintained only for the display purpose. The shun entries are cleaned up whenever the controller
polls the IPS server. If the CIDS IPS server is not reachable, the shun entries are not removed even if they are
timed out on the controller. The shun entries are cleaned up only when the CIDS IPS server is operational again
and the controller polls the CIDS IPS server.
Step 2 (Optional) Specify the number of the HTTPS port through which the controller is to communicate with the IDS sensor
by entering this command:
config wps cids-sensor port index port
For the port-number parameter, you can enter a value between 1 and 65535. The default value is 443. This step is optional
because we recommend that you use the default value of 443. The sensor uses this value to communicate by default.
Step 3 Specify how often the controller should query the IDS server for IDS events by entering this command:
config wps cids-sensor interval index interval
For the interval parameter, you can enter a value between 10 and 3600 seconds. The default value is 60 seconds.
Step 4 Enter a 40-hexadecimal-character security key used to verify the validity of the sensor by entering this command:
config wps cids-sensor fingerprint index sha1 fingerprint
You can get the value of the fingerprint by entering show tls fingerprint on the sensor’s console.
Note Make sure to include the colons that appear between every two bytes within the key (for example,
AA:BB:CC:DD).
Step 5 Enable or disable this controller’s registration with an IDS sensor by entering this command:
config wps cids-sensor {enable | disable} index
Step 6 Enable or disable protection from DoS attacks by entering this command:
The default value is disabled.
Note A potential attacker can use specially crafted packets to mislead the IDS into treating a legitimate client as an
attacker. It causes the controller to wrongly disconnect this legitimate client and launches a DoS attack. The
auto-immune feature, when enabled, is designed to protect against such attacks. However, conversations using
Cisco 792x phones might be interrupted intermittently when the auto-immune feature is enabled. If you experience
frequent disruptions when using 792x phones, you might want to disable this feature.
Step 7 Save your settings by entering this command:
save config
Step 8 See the IDS sensor configuration by entering one of these commands:
• show wps cids-sensor summary
Step 9 The second command provides more information than the first.
Step 10 See the auto-immune configuration setting by entering this command:
show wps summary
Information similar to the following appears:
Auto-Immune
Auto-Immune.................................... Disabled
Step 11 Obtain debug information regarding IDS sensor configuration by entering this command:
debug wps cids enable
Note If you ever want to delete or change the configuration of a sensor, you must first disable it by entering the config
wps cids-sensor disable index command. To delete the sensor, enter the config wps cids-sensor delete index
command.
Note Controller does not log historical NULL Probe IDS events within the Signature Events
Summary output.
• Management frame flood signatures—During a management frame flood attack, a hacker floods an
access point with 802.11 management frames. The result is a denial of service to all clients associated
or attempting to associate to the access point. This attack can be implemented with different types of
management frames: association requests, authentication requests, reassociation requests, probe requests,
disassociation requests, deauthentication requests, and reserved management subtypes.
When a management frame flood signature is used to detect such an attack, the access point identifies
management frames matching the entire characteristic of the signature. If the frequency of these frames
is greater than the value of the frequency set in the signature, an access point that hears these frames
triggers an alarm. The controller generates a trap and forwards it to Cisco Prime Infrastructure.
The management frame flood signatures are as follows:
◦Assoc flood (precedence 4)
◦Auth flood (precedence 5)
◦Reassoc flood (precedence 6)
◦Broadcast probe flood (precedence 7)
◦Disassoc flood (precedence 8)
◦Deauth flood (precedence 9)
◦Reserved mgmt 7 (precedence 10)
◦Reserved mgmt F (precedence 11)
The reserved management frame signatures 7 and F are reserved for future use.
• Wellenreiter signature—Wellenreiter is a wireless LAN scanning and discovery utility that can reveal
access point and client information. When the Wellenreiter signature (precedence 17) is used to detect
such an attack, the access point identifies the offending device and alerts the controller.
• EAPOL flood signature—During an EAPOL flood attack, a hacker floods the air with EAPOL frames
that contain 802.1X authentication requests. As a result, the 802.1X authentication server cannot respond
to all of the requests and fails to send successful authentication responses to valid clients. The result is
a denial of service to all affected clients. When the EAPOL flood signature (precedence 12) is used to
detect such an attack, the access point waits until the maximum number of allowed EAPOL packets is
exceeded. It then alerts the controller and proceeds with the appropriate mitigation.
• NetStumbler signatures—NetStumbler is a wireless LAN scanning utility that reports access point
broadcast information (such as operating channel, RSSI information, adapter manufacturer name, SSID,
WEP status, and the latitude and longitude of the device running NetStumbler when a GPS is attached).
If NetStumbler succeeds in authenticating and associating to an access point, it sends a data frame with
the following strings, depending on the NetStumbler version:
Version String
3.2.0 “Flurble gronk bloopit, bnip Frundletrune”
Version String
3.2.3 “All your 802.11b are belong to us”
When a NetStumbler signature is used to detect such an attack, the access point identifies the offending device
and alerts the controller. The NetStumbler signatures are as follows:
• NetStumbler 3.2.0 (precedence 13)
• NetStumbler 3.2.3 (precedence 14)
• NetStumbler 3.3.0 (precedence 15)
• NetStumbler generic (precedence 16)
A standard signature file exists on the controller by default. You can upload this signature file from the
controller, or you can create a custom signature file and download it to the controller or modify the standard
signature file to create a custom signature.
Step 3 If you are downloading a custom signature file (*.sig), copy it to the default directory on your TFTP server.
Step 4 Choose Commands to open the Download File to Controller page.
Step 5 Perform one of the following:
• If you want to download a custom signature file to the controller, choose Signature File from the File Type
drop-down list on the Download File to Controller page.
• If you want to upload a standard signature file from the controller, choose Upload File and then Signature File
from the File Type drop-down list on the Upload File from Controller page.
Step 6 From the Transfer Mode drop-down list, choose TFTP, FTP, or SFTP.
The SFTP option was added in Release 7.4.
Step 7 In the IP Address text box, enter the IP address of the TFTP, FTP, or SFTP server.
Step 8 If you are downloading the signature file using a TFTP server, enter the maximum number of times that the controller
should attempt to download the signature file in the Maximum retries text box.
The range is 1 to 254 and the default value is 10.
Step 9 If you are downloading the signature file using a TFTP server, enter the amount of time in seconds before the controller
times out while attempting to download the signature file in the Timeout text box.
The range is 1 to 254 seconds and the default is 6 seconds.
Step 10 In the File Path text box, enter the path of the signature file to be downloaded or uploaded. The default value is “/.”
Step 11 In the File Name text box, enter the name of the signature file to be downloaded or uploaded.
Note When uploading signatures, the controller uses the filename that you specify as a base name and then adds
“_std.sig” and “_custom.sig” to it in order to upload both standard and custom signature files to the TFTP server.
For example, if you upload a signature file called “ids1,” the controller automatically generates and uploads both
ids1_std.sig and ids1_custom.sig to the TFTP server. If desired, you can then modify ids1_custom.sig on the
TFTP server (making sure to set “Revision = custom”) and download it by itself.
Step 12 If you are using an FTP or SFTP server, follow these steps:
1 In the Server Login Username text box, enter the username to log into the FTP or SFTP server.
2 In the Server Login Password text box, enter the password to log into the FTP or SFTP server.
3 In the Server Port Number text box, enter the port number on the FTP or SFTP server through which the download
occurs. The default value is 21.
Step 13 Choose Download to download the signature file to the controller or Upload to upload the signature file from the
controller.
Step 1 Choose Security > Wireless Protection Policies > Standard Signatures or Custom Signatures to open the Standard
Signatures page or the Custom Signatures page.
The Standard Signatures page shows the list of Cisco-supplied signatures that are currently on the controller. The Custom
Signatures page shows the list of customer-supplied signatures that are currently on the controller. This page shows the
following information for each signature:
• The order, or precedence, in which the controller performs the signature checks.
• The name of the signature, which specifies the type of attack that the signature is trying to detect.
• The frame type on which the signature is looking for a security attack. The possible frame types are data and
management.
• The action that the controller is directed to take when the signature detects an attack. The possible actions are None
and Report.
• The state of the signature, which indicates whether the signature is enabled to detect security attacks.
• A description of the type of attack that the signature is trying to detect.
Step 5 In the Measurement Interval text box, enter the number of seconds that must elapse before the signature frequency
threshold is reached within the configured interval. The range is 1 to 3600 seconds, and the default value varies per
signature.
Step 6 In the Signature Frequency text box, enter the number of matching packets per interval that must be identified at the
individual access point level before an attack is detected. The range is 1 to 32,000 packets per interval, and the default
value varies per signature.
Step 7 In the Signature MAC Frequency text box, enter the number of matching packets per interval that must be identified per
client per access point before an attack is detected. The range is 1 to 32,000 packets per interval, and the default value
varies per signature.
Step 8 In the Quiet Time text box, enter the length of time (in seconds) after which no attacks have been detected at the individual
access point level and the alarm can stop. The range is 60 to 32,000 seconds, and the default value varies per signature.
Step 9 Select the State check box to enable this signature to detect security attacks or unselect it to disable this signature. The
default value is enabled (or selected).
Step 10 Click Apply to commit your changes. The Standard Signatures or Custom Signatures page reflects the signature’s updated
state.
Step 11 Click Save Configuration to save your changes.
Step 1 Choose Security > Wireless Protection Policies > Signature Events Summary to open the Signature Events Summary
page.
Step 2 Click the Signature Type for the signature to see more information on the attacks detected by a particular signature. The
Signature Events Detail page appears.
This page shows the following information:
• The MAC addresses of the clients identified as attackers
• The method used by the access point to track the attacks
• The number of matching packets per second that were identified before an attack was detected.
• The number of access points on the channel on which the attack was detected
• The day and time when the access point detected the attack
Step 3 Click the Detail link for that attack to see more information for a particular attack. The Signature Events Track Detail
page appears.
• The MAC address of the access point that detected the attack
• The name of the access point that detected the attack
• The type of radio (802.11a or 802.11b/g) used by the access point to detect the attack
• The radio channel on which the attack was detected
• The day and time when the access point reported the attack
Step 11 Specify the number of matching packets per interval that must be identified at the individual access point level before
an attack is detected by entering this command:
config wps signature frequencysignature_id frequency
The range is 1 to 32,000 packets per interval, and the default value varies per signature.
Step 12 Specify the number of matching packets per interval that must be identified per client per access point before an attack
is detected by entering this command:
config wps signature mac-frequency signature_id mac_frequency
The range is 1 to 32,000 packets per interval, and the default value varies per signature.
Step 13 Specify the length of time (in seconds) after which no attacks have been detected at the individual access point level and
the alarm can stop by entering by entering this command:
config wps signature quiet-time signature_id quiet_time
The range is 60 to 32,000 seconds, and the default value varies per signature.
Note If IDS signature processing is disabled, all signatures are disabled, regardless of the state configured for
individual signatures.
• See individual summaries of all of the standard and custom signatures installed on the controller by
entering this command:
show wps signature summary
• See the number of attacks detected by the enabled signatures by entering this command:
show wps signature events summary
• See more information on the attacks detected by a particular standard or custom signature by entering
this command:
show wps signature events {standard | custom} precedence# summary
• See information on attacks that are tracked by access points on a per-signature and per-channel basis by
entering this command:
show wps signature events {standard | custom} precedence# detailed per-signature source_mac
• See information on attacks that are tracked by access points on an individual-client basis (by MAC
address) by entering this command:
show wps signature events {standard | custom} precedence# detailed per-mac source_mac
Note If your wIPS deployment consists of a Cisco WLC, access point, and Cisco MSE, you must set all the
three entities to the UTC time zone.
Cisco Adaptive wIPS is not configured on the Cisco WLC. Instead, the Cisco Prime Infrastructure forwards
the profile configuration to the wIPS service, which forwards the profile to the Cisco WLC. The profile is
stored in flash memory on the Cisco WLC and sent to APs when they join the Cisco WLC. When an access
point disassociates and joins another Cisco WLC, it receives the wIPS profile from the new Cisco WLC.
Local-mode or FlexConnect mode APs with a subset of wIPS capabilities are referred to as Enhanced Local
Mode access point or ELM AP. You can configure an access point to work in the wIPS mode if the AP is in
any of the following modes:
• Monitor
• Local
• FlexConnect
The regular local mode or FlexConnect mode AP is extended with a subset of wIPS capabilities. This feature
enables you to deploy your APs to provide protection without needing a separate overlay network.
wIPS ELM has the limited capability of detecting off-channel alarms. AN AP periodically goes off-channel,
and monitors the nonserving channels for a short duration, and triggers alarms if any attack is detected on the
channel. But off-channel alarm detection is best effort, and it takes a longer time to detect attacks and trigger
alarms, which might cause the ELM AP to intermittently detect an alarm and clear it because it is not visible.
APs in any of the above modes can periodically send alarms based on the policy profile to the wIPS service
through the Cisco WLC. The wIPS service stores and processes the alarms and generates SNMP traps. Cisco
Prime Infrastructure configures its IP address as a trap destination to receive SNMP traps from the Cisco
MSE.
This table lists all the SNMP trap controls and their respective traps. When a trap control is enabled, all the
traps of that trap control are also enabled.
Note The Cisco WLC uses only SNMPv2 for SNMP trap transmission.
Exclusion bsnDot11StationBlacklisted
Rogue AP bsnAdhocRogueAutoContained,
bsnRogueApAutoContained,
bsnTrustedApHasInvalidEncryption,
bsnMaxRogueCountExceeded,
bsnMaxRogueCountClear,
bsnApMaxRogueCountExceeded,
bsnApMaxRogueCountClear,
bsnTrustedApHasInvalidRadioPolicy,
bsnTrustedApHasInvalidSsid,
bsnTrustedApIsMissing
The following are the trap descriptions for the traps mentioned in the SNMP Trap Controls and Their Respective
Traps table:
• General Traps
◦SNMP Authentication—The SNMPv2 entity has received a protocol message that is not properly
authenticated.
Note When a user who is configured in SNMP V3 mode tries to access the Cisco WLC with
an incorrect password, the authentication fails and a failure message is displayed.
However, no trap logs are generated for the authentication failure.
• Cisco AP Traps
◦AP Register—Notification sent when an access point associates or disassociates with the Cisco
WLC.
◦AP Interface Up/Down—Notification sent when an access point interface (802.11X) status goes
up or down.
• Client-Related Traps
◦802.11 Association—Associate notification that is sent when a client sends an association frame.
◦802.11 Disassociation—Disassociate notification that is sent when a client sends a disassociation
frame.
◦802.11 Deauthentication—Deauthenticate notification that is sent when a client sends a
deauthentication frame.
◦802.11 Failed Authentication—Authenticate failure notification that is sent when a client sends
an authentication frame with a status code other than successful.
◦802.11 Failed Association—Associate failure notification that is sent when the client sends an
association frame with a status code other than successful.
◦Exclusion—Associate failure notification that is sent when a client is exclusion listed (blacklisted).
◦Authentication—Authentication notification that is sent when a client is successfully authenticated.
◦Max Clients Limit Reached—Notification that is sent when the maximum number of clients,
defined in the Threshold field, are associated with the Cisco WLC.
◦NAC Alert—Alert that is sent when a client joins an SNMP NAC-enabled WLAN.
This notification is generated when a client on NAC-enabled SSIDs completes Layer2 authentication
to inform the NAC appliance about the client's presence. cldcClientWlanProfileName represents
the profile name of the WLAN that the 802.11 wireless client is connected to, cldcClientIPAddress
represents the unique IP address of the client. cldcApMacAddress represents the MAC address of
the AP to which the client is associated. cldcClientQuarantineVLAN represents the quarantine
VLAN for the client. cldcClientAccessVLAN represents the access VLAN for the client.
◦Association with Stats—Associate notification that is sent with data statistics when a client is
associated with the Cisco WLC, or roams. Data statistics include transmitted and received bytes
and packets.
◦Disassociation with Stats—Disassociate notification that is sent with data statistics when a client
disassociates from the Cisco WLC. Data statistics include transmitted and received bytes and
packets, SSID, and session ID.
Note When you downgrade to Release 7.4 from a later release, if a trap that was not supported
in Release 7.4 (for example, NAC Alert trap) is enabled before the downgrade, all traps
are disabled. After the downgrade, you must enable all the traps that were enabled before
the downgrade. We recommend that you disable the new traps before the downgrade
so that all the other traps are not disabled.
• Security Traps
◦User Auth Failure—This trap informs that a client RADIUS Authentication failure has occurred.
◦RADIUS Server No Response—This trap is to indicate that no RADIUS servers are responding
to authentication requests sent by the RADIUS client.
◦WEP Decrypt Error—Notification sent when the Cisco WLC detects a WEP decrypting error.
◦Rouge AP—Whenever a rogue access point is detected, this trap is sent with its MAC address;
when a rogue access point that was detected earlier no longer exists, this trap is sent.
◦SNMP Authentication—The SNMPv2 entity has received a protocol message that is not properly
authenticated.
Note When a user who is configured in SNMP V3 mode tries to access the Cisco WLC with
an incorrect password, authentication fails and a failure message is displayed. However,
no trap logs are generated for the authentication failure.
• SNMP Authentication
◦Load Profile—Notification sent when the Load Profile state changes between PASS and FAIL.
◦Noise Profile—Notification sent when the Noise Profile state changes between PASS and FAIL.
◦Interference Profile—Notification sent when the Interference Profile state changes between PASS
and FAIL.
◦Coverage Profile—Notification sent when the Coverage Profile state changes between PASS and
FAIL.
• Mesh Traps
◦Child Excluded Parent—Notification that is sent when a defined number of failed association to
the Cisco WLC occurs through a parent mesh node.
◦Notification sent when a child mesh node exceeds the threshold limit of the number of discovery
response timeouts. The child mesh node does not try to associate an excluded parent mesh node
for the interval defined. The child mesh node remembers the excluded parent MAC address when
it joins the network, and informs the Cisco WLC.
◦Parent Change—Notification is sent by the agent when a child mesh node changes its parent. The
child mesh node remembers previous parent and informs the Cisco WLC about the change of
parent when it rejoins the network.
◦Child Moved—Notification sent when a parent mesh node loses connection with its child mesh
node.
◦Excessive Parent Change—Notification sent when the child mesh node changes its parent frequently.
Each mesh node keeps a count of the number of parent changes in a fixed time. If it exceeds the
defined threshold, the child mesh node informs the Cisco WLC.
◦Excessive Children—Notification sent when the child count exceeds for a RAP and a MAP.
◦Poor SNR—Notification sent when the child mesh node detects a lower SNR on a backhaul link.
For the other trap, a notification is sent to clear a notification when the child mesh node detects an
SNR on a backhaul link that is higher then the object defined by 'clMeshSNRThresholdAbate'.
◦Console Login—Notification is sent by the agent when a login on a MAP console is either successful
or fail after three attempts.
◦Default Bridge Group Name—Notification sent when the MAP mesh node joins its parent using
the default bridge group name.
Note The remaining traps do not have trap controls. These traps are not generated too frequently and do not
require any trap control. Any other trap that is generated by the Cisco WLC cannot be turned off.
Note In all of the above cases, the Cisco WLC functions solely as a forwarding device.
Step 1 Choose Wireless > Access Points > All APs > access point name.
Step 2 Set the AP Mode parameter. To configure an access point for wIPS, you must choose one of the following modes from
the AP Mode drop-down list:
• Local
• FlexConnect
• Monitor
Step 1 Configure an access point for the monitor mode by entering this command:
config ap mode {monitor | local | flexconnect} Cisco_AP
Note To configure an access point for wIPS, the access point must be in monitor, local, or flexconnect modes.
Step 2 Enter Y when you see the message that the access point will be rebooted if you want to continue.
Step 3 Save your changes by entering this command:
save config
Step 6 Enable wIPS-optimized channel scanning for the access point by entering this command:
config ap monitor-mode wips-optimized Cisco_AP
The access point scans each channel for 250 milliseconds. It derives the list of channels to be scanned from the monitor
configuration. You can choose one of these options:
• All—All channels are supported by the access point’s radio
• Country—Only the channels supported by the access point’s country of operation
• DCA—Only the channel set used by the dynamic channel assignment (DCA) algorithm, which, by default, includes
all of the nonoverlapping channels allowed in the access point’s country of operation
The 802.11a or 802.11b Monitor Channels information in the output of the show advanced {802.11a | 802.11b} monitor
command shows the monitor configuration channel set:
Note You can also view the access point submode from the controller GUI. To do so, choose Wireless > Access
Points > All APs > access point name > the Advanced tab. The AP Sub Mode field shows wIPS if the
access point is in the monitor mode and the wIPS submode is configured on the access point, or None if
the access point is not in the monitor mode or the access point is in the monitor mode, but the wIPS
submode is not configured.
• See the wIPS submode in the access point by entering this command:
show ap config general Cisco_AP
• See the wIPS-optimized channel-scanning configuration in the access point by entering this command:
show ap monitor-mode summary
• See the wIPS configuration forwarded by Cisco Prime Infrastructure to the controller by entering this
command:
show wps wips summary
• See the current state of the wIPS operation in the controller by entering this command:
show wps wips statistics
• Clear the wIPS statistics in the controller by entering this command:
clear stats wps wips
Step 1 Configure the Wi-Fi Direct Client Policy on WLANs by entering this command:
config wlan wifidirect {allow | disable | not-allow} wlan-id
The syntax of the command is as follows:
• allow—Allows Wi-Fi Direct clients to associate with the WLAN
• disable—Ignores the Wi-Fi Direct status of clients thereby allowing Wi-Fi Direct clients to associate
• not-allow—Disallows the Wi-Fi Direct clients from associating with the WLAN
• xconnect-not-allow—Enables AP to allow a client with the Wi-Fi Direct option enabled to associate, but the client
(if it works according to the Wi-Fi standards) will refrain from setting up a peer-to-peer connection
• wlan-id—WLAN identifier
Note The web authentication proxy redirect ports are not blocked through CPU ACL. If a CPU ACL is configured
to block the port 8080, 3128, and one random port as part of web authentication proxy configuration, those
ports are not blocked because the webauth rules take higher precedence than the CPU ACL rules unless
the client is in the webauth_req state.
A web browser has the following three types of Internet settings that you can configure:
• Auto detect
• System Proxy
• Manual
In a manual proxy server configuration, the browser uses the IP address of a proxy server and a port. If this
configuration is enabled on the browser, the wireless client communicates with the IP address of the destination
proxy server on the configured port. In a web authentication scenario, the controller does not listen to such
proxy ports and the client is not able to establish a TCP connection with the controller. The user is unable to
get any login page to authentication and get access to the network.
When a wireless client enters a web-authenticated WLAN, the client tries to access a URL. If a manual proxy
configuration is configured on the client's browser, all the web traffic going out from the client will be destined
to the proxy IP and port configured on the browser.
• A TCP connection is established between the client and the proxy server IP address that the controller
proxies for.
• The client processes the DHCP response and obtains a JavaScript file from the controller. The script
disables all proxy configurations on the client for that session.
Note For external clients, the controller sends the login page as is (with or without JavaScipt).
• Any requests that bypass the proxy configuration. The controller can then perform web-redirection,
login, and authentication.
• When the client goes out of the network, and then back into its own network, a DHCP refresh occurs
and the client continues to use the old proxy configuration configured on the browser.
• If the external DHCP server is used with webauth proxy, then DHCP option 252 must be configured on
the DHCP server for that scope. The value of option 252 will have the format http://<virtual ip>/proxy.js.
No extra configuration is needed for internal DHCP servers.
Note When you configure FIPS mode with secure web authentication, we recommend that
you use Mozilla Firefox as your browser.
Note If you configure to disallow secure web (HTTPS) authentication for clients using the config network
web-auth secureweb disable command, then you must reboot the Cisco WLC to implement the change.
• If you configured your WLAN with EAP Passthrough and if you downgrade to an earlier controller
version, you might encounter XML validation errors during the downgrade process. This problem is
because EAP Passthrough is not supported in earlier releases. The configuration will default to the default
security settings (WPA2/802.1X).
Note The OEAP 600 Series access point supports a maximum of two WLANs and one remote
LAN. If you have configured more than two WLANs and one remote LAN, you can
assign the 600 Series access point to an AP group. The support for two WLANs and
one remote LAN still applies to the AP Group If the 600 Series OEAP is in the default
group, the WLAN or remote LAN IDs must be lower than 8.
• Profile name of WLAN can be of max 31 characters for a locally switched WLAN. For central switched
WLAN, the profile name can be of 32 characters.
• When multiple WLANs with the same SSID get assigned to the same AP radio, you must have a unique
Layer 2 security policy so that clients can safely select between them.
• When WLAN is local switching, associate the client to local-switching WLAN where AVC is enabled.
Send some traffic from client, when you check the AVC stats after 90 sec. Cisco WLC shows stats under
top-apps but does not show under client. There is timer issue so for the first slot Cisco WLC might not
show stats for the clients. Earlier, only 1 sec stats for a client is seen if the timers at AP and at WLC are
off by 89 seconds. Now, clearing of the stats is after 180 seconds so stats from 91 seconds to 179 seconds
for a client is seen. This is done because two copies of the stats per client cannot be kept due to memory
constraint in Cisco 5508 WLC.
Caution Some clients might not be able to connect to WLANs properly if they detect the same SSID with multiple
security policies. Use this feature with care.
Note If the Cisco OEAP 600 is in the default group, the WLAN/Remote LAN IDs need to be set as lower than ID
8.
Step 7 Click Apply to commit your changes. The WLANs > Edit page appears.
Note You can also open the WLANs > Edit page from the WLANs page by clicking the ID number of the WLAN
that you want to edit.
Step 8 Use the parameters on the General, Security, QoS, and Advanced tabs to configure this WLAN. See the sections in the
rest of this chapter for instructions on configuring specific features for WLANs.
Step 9 On the General tab, select the Status check box to enable this WLAN. Be sure to leave it unselected until you have
finished making configuration changes to the WLAN.
Step 10 Click Apply to commit your changes.
Step 11 Click Save Configuration to save your changes.
Step 2 Enable or disable WLANs from the WLANs page by selecting the check boxes to the left of the WLANs that you want
to enable or disable, choosing Enable Selected or Disable Selected from the drop-down list, and clicking Go.
Step 3 Click Apply.
Note If you do not specify an ssid, the profile_name parameter is used for both the profile
name and the SSID.
Note When WLAN 1 is created in the configuration wizard, it is created in enabled mode.
Disable it until you have finished configuring it. When you create a new WLAN using
the config wlan create command, it is created in disabled mode. Leave it disabled until
you have finished configuring it.
Note An error message appears if you try to delete a WLAN that is assigned to an access
point group. If you proceed, the WLAN is removed from the access point group and
from the access point’s radio.
Note If the command fails, an error message appears (for example, “Request failed for wlan 10 - Static WEP
key size does not match 802.1X WEP key size”).
• Disable a WLAN (for example, before making any modifications to a WLAN) by entering this command:
config wlan disable {wlan_id | foreign_ap | all}
where
wlan_id is a WLAN ID between 1 and 512.
foreign_ap is a third-party access point.
all is all WLANs.
Note If the management and AP-manager interfaces are mapped to the same port and are members of the same
VLAN, you must disable the WLAN before making a port-mapping change to either interface. If the
management and AP-manager interfaces are assigned to different VLANs, you do not need to disable the
WLAN.
Note If the WLAN is disabled, the VLAN acls corresponding to the WLAN-VLAN mapping at the AP is pushed
to the AP and has precedence over the group mappings. Before WLAN is disabled there should be 16 sub
interface created for vlan-acl mapping and 3 ap specific WLAN-VLAN mapping and 3 more sub interface
should be created for group specific WLAN-VLAN mapping, as of now out of 16 vlan-acl mapping only
14 are pushed. After disabling all the WLAN only vlan-acl sub interface should be pushed and other sub
interface should be deleted from the AP.
Step 1 On the WLANs page, click Change Filter. The Search WLANs dialog box appears.
Step 2 Perform one of the following:
• To search for WLANs based on profile name, select the Profile Name check box and enter the desired profile
name in the edit box.
• To search for WLANs based on SSID, select the SSID check box and enter the desired SSID in the edit box.
• To search for WLANs based on their status, select the Status check box and choose Enabled or Disabled from
the drop-down list.
Step 3 Click Find. Only the WLANs that match your search criteria appear on the WLANs page, and the Current Filter field
at the top of the page specifies the search criteria used to generate the list (for example, None, Profile Name:user1,
SSID:test1, Status: disabled).
Note To clear any configured search criteria and display the entire list of WLANs, click Clear
Filter.
• Verify the interface assignment status by entering the show wlan summary command.
For the client with an IPv6 address, controller supports only one untagged interface for a controller. However,
in an ideal scenario of IPv4 address, the controller supports one untagged interface per port.
When the controller communicates with the RADIUS server, the NAS-ID attribute is replaced with the
configured NAS-ID in an AP group, a WLAN, or a VLAN interface.
The NAS-ID that is configured on the controller for an AP group, a WLAN, or a VLAN interface is used for
authentication. The configuration of NAS-ID is not propagated across controllers.
Note If WLAN interface is overridden at AP group then overridden interface NAS ID will be used. Since
Interface NASID is given priority over WLAN NAS ID.
Note For more information about the number of clients that are supported, see the product data sheet of your .
Step 1 Determine the WLAN ID for which you want to configure the maximum clients by entering this command:
show wlan summary
Get the WLAN ID from the list.
Step 2 Configure the maximum number of clients for each WLAN by entering this command:
config wlan max-associated-clients max-clients wlan-id
Configuring the Maximum Number of Clients for each AP Radio per WLAN
(GUI)
Configuring the Maximum Number of Clients for each AP Radio per WLAN
(CLI)
Step 1 Determine the WLAN ID for which you want to configure the maximum clients for each radio by entering this command:
show wlan summary
Obtain the WLAN ID from the list.
Step 2 Configure the maximum number of clients for each WLAN by entering this command:
config wlan max-radio-clients client_count
You can configure up to 200 clients.
Step 3 See the configured maximum associated clients by entering the show 802.11a command.
DHCP option 43 is not supported on the internal server. Therefore, the access point must use an alternative
method to locate the management interface IP address of the , such as local subnet broadcast, Domain Name
System (DNS), or priming.
An internal DHCP server pool only serves the wireless clients of that , not clients of other . Also, an internal
DHCP server can serve only wireless clients, not wired clients.
When clients use the internal DHCP server of the , IP addresses are not preserved across reboots. As a result,
multiple clients can be assigned with the same IP address. To resolve any IP address conflicts, clients must
release their existing IP address and request a new one. Wired guest clients are always on a Layer 2 network
connected to a local or foreign .
DHCP Assignments
You can configure DHCP on a per-interface or per-WLAN basis. We recommend that you use the primary
DHCP server address that is assigned to a particular interface.
You can assign DHCP servers for individual interfaces. You can configure the management interface,
AP-manager interface, and dynamic interface for a primary and secondary DHCP server, and you can configure
the service-port interface to enable or disable DHCP servers. You can also define a DHCP server on a WLAN.
In this case, the server overrides the DHCP server address on the interface assigned to the WLAN.
Security Considerations
For enhanced security, we recommend that you require all clients to obtain their IP addresses from a DHCP
server. To enforce this requirement, you can configure all WLANs with a DHCP Addr. Assignment Required
setting, which disallows client static IP addresses. If DHCP Addr. Assignment Required is selected, clients
must obtain an IP address via DHCP. Any client with a static IP address is not allowed on the network. The
monitors DHCP traffic because it acts as a DHCP proxy for the clients.
Note • WLANs that support management over wireless must allow management (device-servicing) clients
to obtain an IP address from a DHCP server.
If slightly less security is tolerable, you can create WLANs with DHCP Addr. Assignment Required disabled.
Clients then have the option of using a static IP address or obtaining an IP address from a designated DHCP
server.
Note DHCP Addr. Assignment Required is not supported for wired guest LANs.
You can create separate WLANs with DHCP Addr. Assignment Required configured as disabled. This is
applicable only if DHCP proxy is enabled for the . You must not define the primary/secondary configuration
DHCP server you should disable the DHCP proxy. These WLANs drop all DHCP requests and force clients
to use a static IP address. These WLANs do not support management over wireless connections.
Step 8 If you want to require all clients to obtain their IP addresses from a DHCP server, select the DHCP Addr. Assignment
Required check box. When this feature is enabled, any client with a static IP address is not allowed on the network. The
default value is disabled.
Note DHCP Addr. Assignment Required is not supported for wired guest LANs.
Note PMIPv6 supports only DHCP based clients and Static IP address is not supported.
Step 2 Specify the interface for which you configured a primary DHCP server to be used with this WLAN by entering this
command:
config wlan interface wlan-id interface_name
Step 3 If you want to define a DHCP server on the WLAN that will override the DHCP server address on the interface assigned
to the WLAN, enter this command:
config wlan dhcp_server wlan-id dhcp_server_ip_address
Note The preferred method for configuring DHCP is to use the primary DHCP address assigned to a particular interface
instead of the DHCP server override. If you enable the override, you can use the show wlan command to verify
that the DHCP server has been assigned to the WLAN.
Note If a WLAN has the DHCP server override option enabled and the controller has DHCP proxy enabled, any
interface mapped to the WLAN must have a DHCP server IP address or the WLAN must be configured with a
DHCP server IP address.
Note PMIPv6 supports only DHCP based clients and Static IP address is not supported.
Broadcast to Yes No
Unicast
RFC Non-compliant Proxy and relay agent are not exactly the No
same concept. But DHCP bridging mode
is recommended for full RFC compliance.
SUMMARY STEPS
1. To enable client profiling, you must enable the DHCP required flag and disable the local authentication
flag.
2. To configure a DHCP timeout value, use the config dhcp timeout command. If you have configured a
WLAN to be in DHCP required state, this timer controls how long the WLC will wait for a client to get
a DHCP lease through DHCP.
DETAILED STEPS
Step 1 Choose Controller > Internal DHCP Server > DHCP Scope to open the DHCP Scopes page.
This page lists any DHCP scopes that have already been configured.
Note If you ever want to delete an existing DHCP scope, hover your cursor over the blue drop-down arrow for that
scope and choose Remove.
Step 2 Click New to add a new DHCP scope. The DHCP Scope > New page appears.
Step 3 In the Scope Name text box, enter a name for the new DHCP scope.
Step 4 Click Apply. When the DHCP Scopes page reappears, click the name of the new scope. The DHCP Scope > Edit page
appears.
Step 5 In the Pool Start Address text box, enter the starting IP address in the range assigned to the clients.
Note This pool must be unique for each DHCP scope and must not include the static IP addresses of routers or other
servers.
Step 6 In the Pool End Address text box, enter the ending IP address in the range assigned to the clients.
Note This pool must be unique for each DHCP scope and must not include the static IP addresses of routers or other
servers.
Step 7 In the Network text box, enter the network served by this DHCP scope. This IP address is used by the management
interface with Netmask applied, as configured on the Interfaces page.
Step 8 In the Netmask text box, enter the subnet mask assigned to all wireless clients.
Step 9 In the Lease Time text box, enter the amount of time (from 0 to 65536 seconds) that an IP address is granted to a client.
Step 10 In the Default Routers text box, enter the IP address of the optional router connecting the controllers. Each router must
include a DHCP forwarding agent, which allows a single controller to serve the clients of multiple controllers.
Step 11 In the DNS Domain Name text box, enter the optional domain name system (DNS) domain name of this DHCP scope
for use with one or more DNS servers.
Step 12 In the DNS Servers text box, enter the IP address of the optional DNS server. Each DNS server must be able to update
a client’s DNS entry to match the IP address assigned by this DHCP scope.
Step 13 In the Netbios Name Servers text box, enter the IP address of the optional Microsoft Network Basic Input Output System
(NetBIOS) name server, such as the Internet Naming Service (WINS) server.
Step 14 From the Status drop-down list, choose Enabled to enable this DHCP scope or choose Disabled to disable it.
Step 15 Save the configuration.
Step 16 Choose DHCP Allocated Leases to see the remaining lease time for wireless clients. The DHCP Allocated Lease page
appears, showing the MAC address, IP address, and remaining lease time for the wireless clients.
Step 4 Specify the amount of time (from 0 to 65536 seconds) that an IP address is granted to a client by entering this command:
config dhcp lease scope lease_duration
Step 5 Specify the IP address of the optional router connecting the controllers by entering this command:
config dhcp default-router scope router_1 [router_2] [router_3]
Each router must include a DHCP forwarding agent, which allows a single controller to serve the clients of multiple
controllers.
Step 6 Specify the optional domain name system (DNS) domain name of this DHCP scope for use with one or more DNS
servers by entering this command:
config dhcp domain scope domain
Step 7 Specify the IP address of the optional DNS server(s) by entering this command:
config dhcp dns-servers scope dns1 [dns2] [dns3]
Each DNS server must be able to update a client’s DNS entry to match the IP address assigned by this DHCP scope
Step 8 Specify the IP address of the optional Microsoft Network Basic Input Output System (NetBIOS) name server, such as
the Internet Naming Service (WINS) server by entering this command:
config dhcp netbios-name-server scope wins1 [wins2] [wins3]
Step 11 See the list of configured DHCP scopes by entering this command:
show dhcp summary
Information similar to the following appears:
Enabled....................................... No
Lease Time.................................... 0
Pool Start.................................... 0.0.0.0
Pool End...................................... 0.0.0.0
Network....................................... 0.0.0.0
Netmask....................................... 0.0.0.0
Default Routers............................... 0.0.0.0 0.0.0.0 0.0.0.0
DNS Domain....................................
DNS........................................... 0.0.0.0 0.0.0.0 0.0.0.0
Netbios Name Servers.......................... 0.0.0.0 0.0.0.0 0.0.0.0
When you enable MAC filtering, only the MAC addresses that you add to the WLAN are allowed to join the
WLAN. MAC addresses that have not been added are not allowed to join the WLAN.
When a client tries to associate to a WLAN for the first time, the client gets authenticated with its MAC
address from AAA server. If the authentication is successful, the client gets an IP address from DHCP server,
and then the client is connected to the WLAN.
When the client roams or sends association request to the same AP or different AP and is still connected to
WLAN, the client is not authenticated again to AAA server.
If the client is not connected to WLAN, then the client has to get authenticated from the AAA server.
• Assign an IP address to an existing MAC filter entry, if one was not assigned in the config macfilter
add command by entering the config macfilter ip-address mac_addr IP_addr command.
• Verify that MAC addresses are assigned to the WLAN by entering the show macfilter command.
Note If MAC filtering is configured, the controller tries to authenticate the wireless clients using the RADIUS
servers first. Local MAC filtering is attempted only if no RADIUS servers are found, either because the
RADIUS servers timed out or no RADIUS servers were configured.
Note If you configure session timeout as 0, it means disabling session-timeout, in case of open system, and
86400 seconds for all other system types.
Note When a 802.1x WLAN session timeout value is modified, the associated clients pmk-cache does not
change to reflect the new session time out value.
Step 1 Configure a session timeout for wireless clients on a WLAN by entering this command:
config wlan session-timeout wlan_id timeout
The default value is 1800 seconds for the following Layer 2 security types: 802.1X, Static WEP+802.1X, WPA+WPA2
with 802.1X, CCKM, or 802.1X+CCKM authentication key management and 0 seconds for all other Layer 2 security
types (Open WLAN/CKIP/Static WEP). A value of 0 is equivalent to no timeout.
Step 3 See the current session timeout value for a WLAN by entering this command:
show wlan wlan_id
Information similar to the following appears:
WLAN Identifier.................................. 9
Profile Name..................................... test12
Note A beacon period, which is specified in milliseconds on the , is converted internally by the software to
802.11 Time Units (TUs), where 1 TU = 1.024 milliseconds. On Cisco’s 802.11n access points, this value
is rounded to the nearest multiple of 17 TUs. For example, a configured beacon period of 100 ms results
in an actual beacon period of 104 ms.
Many applications cannot tolerate a long time between broadcast and multicast messages, which results in
poor protocol and application performance. We recommend that you set a low DTIM value for 802.11 networks
that support such clients.
You can configure the DTIM period for the 802.11 radio networks on specific WLANs. For example, you
might want to set different DTIM values for voice and data WLANs.
Step 2 Configure the DTIM period for a 802.11 radio network on a specific WLAN by entering this command:
config wlan dtim {802.11a | 802.11b} dtim wlan_id
where dtim is a value between 1 and 255 (inclusive). The default value is 1 (transmit broadcast and multicast frames
after every beacon).
Peer-to-peer blocking is supported for clients that are associated with the local switching WLAN.
Per WLAN, peer-to-peer configuration is pushed by the controller to FlexConnect AP. In controller software
releases prior to 4.2, peer-to-peer blocking is applied globally to all clients on all WLANs and causes traffic
between two clients on the same VLAN to be transferred to the upstream VLAN rather than being bridged
by the controller. This behavior usually results in traffic being dropped at the upstream switch because switches
do not forward packets out the same port on which they are received.
Step 3 See the status of peer-to-peer blocking for a WLAN by entering this command:
show wlan wlan_id
WLAN Identifier.................................. 1
Profile Name..................................... test
Network Name (SSID).............................. test
Status........................................... Enabled
...
...
...
Peer-to-Peer Blocking Action..................... Disabled
Radio Policy..................................... All
Local EAP Authentication...................... Disabled
Note • Because static WEP and 802.1X are both advertised by the same bit in beacon and
probe responses, they cannot be differentiated by clients. Therefore, they cannot
both be used by multiple WLANs with the same SSID.
• WLAN WEP is not supported in 1810w Access Point.
• CKIP
• WPA/WPA2
Note • Although WPA and WPA2 cannot be used by multiple WLANs with the same
SSID, you can configure two WLANs with the same SSID with WPA/TKIP with
PSK and Wi-Fi Protected Access (WPA )/Temporal Key Integrity Protocol (TKIP)
with 802.1X, or with WPA/TKIP with 802.1X or WPA/AES with 802.1X.
• A WLAN that is configured with TKIP support will not be enabled on an
RM3000AC module.
Note To use LEAP with lightweight access points and wireless clients, make sure to choose Cisco-Aironet as
the RADIUS server type when configuring the CiscoSecure Access Control Server (ACS).
Note The controller performs both web authentication and 802.1X authentication in the same
WLAN. The clients are initially authenticated with 802.1X. After a successful
authentication, the client must provide the web authentication credentials. After a
successful web authentication, the client is moved to the run state.
• Change the 802.1X encryption level for a WLAN by entering this command:
config wlan security 802.1X encryption wlan_id [0 | 40 | 104]
◦Use the 0 option to specify no 802.1X encryption.
◦Use the 40 option to specify 40/64-bit encryption.
◦Use the 104 option to specify 104/128-bit encryption. (This is the default encryption setting.)
• This feature is not supported on Linux-based APs such as Cisco 600 Series OfficeExtend Access Points.
• 802.11r fast roaming is not supported if the client uses Over-the-DS preauthentication in standalone
mode.
• EAP LEAP method is not supported. WAN link latency prevents association time to a maximum of 2
seconds.
• The service from standalone AP to client is only supported until the session timer expires.
• TSpec is not supported for 802.11r fast roaming. Therefore, RIC IE handling is not supported.
• If WAN link latency exists, fast roaming is also delayed. Voice or data maximum latency should be
verified. The Cisco WLC handles 802.11r Fast Transition authentication request during roaming for
both Over-the-Air and Over-the-DS methods.
• This feature is supported only on open and WPA2 configured WLANs.
• Legacy clients cannot associate with a WLAN that has 802.11r enabled if the driver of the supplicant
that is responsible for parsing the Robust Security Network Information Exchange (RSN IE) is old and
not aware of the additional AKM suites in the IE. Due to this limitation, clients cannot send association
requests to WLANs. These clients, however, can still associate with non-802.11r WLANs. Clients that
are 802.11r capable can associate as 802.11i clients on WLANs that have both 802.11i and 802.11r
Authentication Key Management Suites enabled.
The workaround is to enable or upgrade the driver of the legacy clients to work with the new 802.11r
AKMs, after which the legacy clients can successfully associate with 802.11r enabled WLANs.
Another workaround is to have two SSIDs with the same name but with different security settings (FT
and non-FT).
• Fast Transition resource request protocol is not supported because clients do not support this protocol.
Also, the resource request protocol is an optional protocol.
• To avoid any Denial of Service (DoS) attack, each Cisco WLC allows a maximum of three Fast Transition
handshakes with different APs.
• Non-802.11r capable devices will not be able to associate with FT-enabled WLAN.
• 802.11r FT + PMF is not recommended.
• 802.11r FT Over-the-Air roaming is recommended for FlexConnect deployments.
The FT key hierarchy is designed to allow clients to make fast BSS transitions between APs without requiring
reauthentication at every AP. WLAN configuration contains a new Authenticated Key Management (AKM)
type called FT (Fast Transition).
• Over-the-Air—The client communicates directly with the target AP using IEEE 802.11 authentication
with the FT authentication algorithm.
• Over-the-DS—The client communicates with the target AP through the current AP. The communication
between the client and the target AP is carried in FT action frames between the client and the current
AP and is then sent through the .
This figure shows the sequence of message exchanges that occur when Over the Air client roaming is
configured.
Figure 40: Message Exchanges when Over the Air client roaming is configured
This figure shows the sequence of message exchanges that occur when Over the DS client roaming is configured.
Figure 41: Message Exchanges when Over the DS client roaming is configured
Step 5 From the Fast Transition drop-down list, choose Fast Transition on the WLAN.
Step 6 Check or uncheck the Over the DS check box to enable or disable Fast Transition over a distributed system.
This option is available only if you enable Fast Transition or if Fast Transition is adaptive.
To use 802.11r Fast Transition over-the-air and over-the-ds must be disabled.
Step 7 In the Reassociation Timeout field, enter the number of seconds after which the reassociation attempt of a client to an
AP should time out. The valid range is 1 to 100 seconds.
Note This option is available only if you enable Fast
Transition.
Step 8 Under Authentication Key Management, choose FT 802.1X or FT PSK. Check or uncheck the corresponding check
boxes to enable or disable the keys. If you check the FT PSK check box, from the PSK Format drop-down list, choose
ASCII or Hex and enter the key value.
Note When Fast Transition adaptive is enabled, you can use only 802.1X and PSK AKM..
Step 9 From the WPA gtk-randomize State drop-down list, choose Enable or Disable to configure the Wi-Fi Protected Access
(WPA) group temporal key (GTK) randomize state.
Step 10 Click Apply to save your settings.
Step 1 To enable or disable 802.11r fast transition parameters, use the config wlan security ft {enable | disable} wlan-id
command.
Step 2 To enable or disable 802.11r fast transition parameters over a distributed system, use the config wlan security ft
over-the-ds {enable | disable} wlan-id command.
The Client devices normally prefer fast transition over-the-ds if the capability is advertised in the WLAN. To force a
client to perform fast transition over-the-air, disable fast transition over-the-ds.
Step 3 To enable or disable the authentication key management for fast transition using preshared keys (PSK), use the config
wlan security wpa akm ft psk {enable | disable} wlan-id command.
By default, the authentication key management using PSK is disabled.
Step 4 To enable or disable authentication key management for adaptive using PSK, use the config wlan security wpa akm
psk {enable | disable} wlan-id command.
Step 5 To enable or disable authentication key management for fast transition using 802.1X, use the config wlan security wpa
akm ft-802.1X {enable | disable} wlan-id command.
By default, authentication key management using 802.1X is enabled.
Step 6 To enable or disable authentication key management for adaptive using 802.1x, use the config wlan security wpa akm
802.1x {enable | disable} wlan-id command.
Note When Fast Transition adaptive is enabled, you can use only 802.1X and PSK AKM.
Step 7 To enable or disable 802.11r fast transition reassociation timeout, use the config wlan security ft reassociation-timeout
timeout-in-seconds wlan-id command.
The valid range is 1 to 100 seconds. The default value of reassociation timeout is 20 seconds.
Step 8 To view the fast transition configuration on a WLAN, use the show wlan wlan-id command.
Step 9 To view the fast transition configuration on a client, use the show client detail client-mac command.
Note This command is relevant only for a connected or connecting client station (STA).
Step 10 To enable or disable debugging of fast transition events, use the debug ft events {enable | disable} command.
Note WLAN with WPA2 + 802.1X + WebAuth with WebAuth on MAC failure is not supported.
Step 1 Choose WLANs > WLAN ID to open the WLANs > Edit page.
Step 2 In the Security tab, click the Layer 2 tab.
Step 3 Select the MAC Filtering check box.
Step 4 Select the Mac Auth or Dot1x check box.
Configuring 802.11w
• Block Ack
• Radio Measurement
• Fast BSS Transition
• SA Query
• Protected Dual of Public Action
• Vendor-specific Protected
Step 1 Choose WLANs > WLAN ID to open the WLANs > Edit page.
Step 2 In the Security tab, choose the Layer 2 security tab.
Step 3 From the Layer 2 Security drop-down list, choose WPA+WPA2.
The 802.11w IGTK Key is derived using the 4-way handshake, which means that it can only be used on WLANs that
are configured for WPA2 security at Layer 2.
Note WPA2 is mandatory and encryption type must be AES. TKIP is not
valid.
Step 4 Choose the PMF state from the drop-down list
The following options are available:
• Disabled—Disables 802.11w MFP protection on a WLAN
• Optional—To be used if the client supports 802.11w.
• Required—Ensures that the clients that do not support 802.11w cannot associate with the WLAN.
Step 5 If you choose the PMF state as either Optional or Required, do the following:
a) In the Comeback Timer box, enter the association comeback interval in milliseconds. It is the time within which the
access point reassociates with the client after a valid security association.
b) In the SA Query Timeout box, enter the maximum time before an Security Association (SA) query times out.
Step 6 In the Authentication Key Management section, follow these steps:
a) Select or unselect the PMF 802.1X check box to configure the 802.1X authentication for the protection of management
frames.
b) Select or unselect the PMF PSK check box to configure the preshared keys for PMF. Choose the PSK format as
either ASCII or Hexadecimal and enter the PSK.
Step 7 Click Apply.
Step 8 Click Save Configuration.
Note Dynamic WEP encryption method is not supported. The last release to support this method was Release
7.0 (7.0.240.0 and later 7.0 releases).
On a single WLAN, you can allow WPA1, WPA2, and 802.1X/PSK/CCKM/802.1X+CCKM clients to join.
All of the access points on such a WLAN advertise WPA1, WPA2, and 802.1X/PSK/CCKM/ 802.1X+CCKM
information elements in their beacons and probe responses. When you enable WPA1 and/or WPA2, you can
also enable one or two ciphers, or cryptographic algorithms, designed to protect data traffic. Specifically, you
can enable AES and/or TKIP data encryption for WPA1 and/or WPA2. TKIP is the default value for WPA1,
and AES is the default value for WPA2.
Configuring WPA1+WPA2
Step 8 If you chose PSK in Step 7, choose ASCII or HEX from the PSK Format drop-down list and then enter a preshared key
in the blank text box. WPA preshared keys must contain 8 to 63 ASCII text characters or 64 hexadecimal characters.
Note The PSK parameter is a set-only parameter. The value set for the PSK key is not visible to the user for security
reasons. For example, if you selected HEX as the key format when setting the PSK key, and later when you
view the parameters of this WLAN, the value shown is the default value. The default is ASCII.
Step 9 Click Apply to commit your changes.
Step 10 Click Save Configuration to save your changes.
Step 2 Enable or disable WPA for the WLAN by entering this command:
config wlan security wpa {enable | disable} wlan_id
Step 3 Enable or disable WPA1 for the WLAN by entering this command:
config wlan security wpa wpa1 {enable | disable} wlan_id
Step 4 Enable or disable WPA2 for the WLAN by entering this command:
config wlan security wpa wpa2 {enable | disable} wlan_id
Step 5 Enable or disable AES or TKIP data encryption for WPA1 or WPA2 by entering one of these commands:
• config wlan security wpa wpa1 ciphers {aes | tkip} {enable | disable} wlan_id
• config wlan security wpa wpa2 ciphers {aes | tkip} {enable | disable} wlan_id
The default values are TKIP for WPA1 and AES for WPA2.
Note You can enable or disable TKIP encryption only using the CLI. Configuring TKIP encryption is not supported
in GUI.
When you have VLAN configuration on WGB, you need to configure the encryption cipher mode and keys for a particular
VLAN, for example, encryption vlan 80 mode ciphers tkip. Then, you need configure the encryption cipher mode
globally on the multicast interface by entering the following command: encryption mode ciphers tkip.
Step 6 Enable or disable 802.1X, PSK, or CCKM authenticated key management by entering this command:
config wlan security wpa akm {802.1X | psk | cckm} {enable | disable} wlan_id
The default value is 802.1X.
Step 7 If you enabled PSK in Step 6, enter this command to specify a preshared key:
config wlan security wpa akm psk set-key {ascii | hex} psk-key wlan_id
WPA preshared keys must contain 8 to 63 ASCII text characters or 64 hexadecimal characters.
Step 8 Enable or disable authentication key management suite for fast transition by entering this command:
config wlan security wpa akm ft {802.1X | psk} {enable | disable} wlan_id
Note You can now choose between the PSK and the fast transition PSK as the AKM
suite.
Step 9 Enable or disable randomization of group temporal keys (GTK) between AP and clients by entering this command:
config wlan security wpa gtk-random {enable | disable} wlan_id
Step 10 If you enabled WPA2 with 802.1X authenticated key management or WPA1 or WPA2 with CCKM authenticated key
management, the PMK cache lifetime timer is used to trigger reauthentication with the client when necessary. The timer
is based on the timeout value received from the AAA server or the WLAN session timeout setting. To see the amount
of time remaining before the timer expires, enter this command:
show pmk-cache all
If you enabled WPA2 with 802.1X authenticated key management, the controller supports both opportunistic PMKID
caching and sticky (or non-opportunistic) PMKID caching. In sticky PMKID caching (SKC), the client stores multiple
PMKIDs, a different PMKID for every AP it associates with. Opportunistic PMKID caching (OKC) stores only one
PMKID per client. By default, the controller supports OKC.
WLAN Identifier.................................. 2
Profile Name..................................... new
Network Name (SSID).............................. new
Status........................................... Disabled
MAC Filtering.................................... Disabled
Security
802.11 Authentication:........................ Open System
Static WEP Keys............................... Disabled
802.1X........................................ Disabled
Wi-Fi Protected Access (WPA/WPA2)............. Enabled
WPA (SSN IE)............................... Disabled
WPA2 (RSN IE).............................. Enabled
TKIP Cipher............................. Disabled
AES Cipher.............................. Enabled
Auth Key Management
802.1x.................................. Disabled
PSK..................................... Enabled
CCKM.................................... Disabled
FT(802.11r)............................. Disabled
FT-PSK(802.11r)......................... Disabled
SKC Cache Support......................... Enabled
FT Reassociation Timeout................... 20
FT Over-The-Air mode....................... Enabled
FT Over-The-Ds mode........................ Enabled
CCKM tsf Tolerance............................... 1000
Wi-Fi Direct policy configured................ Disabled
EAP-Passthrough............................... Disabled
Note CKIP is supported for use only with static WEP. It is not supported for use with dynamic WEP. Therefore,
a wireless client that is configured to use CKIP with dynamic WEP is unable to associate to a WLAN that
is configured for CKIP. We recommend that you use either dynamic WEP without CKIP (which is less
secure) or WPA/WPA2 with TKIP or AES (which are more secure).
Step 2 Enable Aironet IEs for this WLAN by entering this command:
config wlan ccx aironet-ie enable wlan_id
Step 3 Enable or disable CKIP for the WLAN by entering this command:
config wlan security ckip {enable | disable} wlan_id
Step 4 Specify a CKIP encryption key for the WLAN by entering this command:
config wlan security ckip akm psk set-key wlan_id {40 | 104} {hex | ascii} key key_index
Step 5 Enable or disable CKIP MMH MIC for the WLAN by entering this command:
config wlan security ckip mmh-mic {enable | disable} wlan_id
Step 6 Enable or disable CKIP key permutation for the WLAN by entering this command:
config wlan security ckip kp {enable | disable} wlan_id
• The allow rule for the virtual IP should be for TCP protocol and port 80 (if secureweb is disabled) or
port 443 (if secureweb is enabled). This process is required to allow client’s access to the virtual interface
IP address, post successful authentication when the CPU ACL rules are in place.
If multiple identity stores are selected, then the controller checks each identity store in the list, in the
order specified, from top to bottom, until authentication for the user succeeds. The authentication fails,
if the controller reaches the end of the list and user remains un-authenticated in any of the identity stores.
Step 1 Enable or disable web authentication on a particular WLAN by entering this command:
config wlan security web-auth {enable | disable} wlan_id
Step 2 Release the guest user IP address when the web authentication policy timer expires and prevent the guest user from
acquiring an IP address for 3 minutes by entering this command:
config wlan webauth-exclude wlan_id {enable | disable}
The default value is disabled. This command is applicable when you configure the internal DHCP scope on the controller.
By default, when the web authentication timer expires for a guest user, the user can immediately reassociate to the same
IP address before another guest user can acquire it. If there are many guest users or limited IP addresses in the DHCP
pool, some guest users might not be able to acquire an IP address.
When you enable this feature on the guest WLAN, the guest user’s IP address is released when the web authentication
policy timer expires and the guest user is excluded from acquiring an IP address for 3 minutes. The IP address is available
for another guest user to use. After 3 minutes, the excluded guest user can reassociate and acquire an IP address, if
available.
Note The captive portal bypass for IOS7 is supported only with Cisco Wireless LAN Controller, Release 7.6.
This HTTP request triggers a web authentication interception in the controller as any other page requests are
performed by a wireless client. This interception leads to a web authentication process, which will be completed
normally. If the web authentication is being used with any of the controller splash page features (URL provided
by a configured RADIUS server), the splash page may never be displayed because the WISPr requests are
made at very short intervals, and as soon as one of the queries is able to reach the designated server, any web
redirection or splash page display process that is performed in the background is aborted, and the device
processes the page request, thus breaking the splash page functionality.
For example, Apple introduced an iOS feature to facilitate network access when captive portals are present.
This feature detects the presence of a captive portal by sending a web request on connecting to a wireless
network. This request is directed to http://www.apple.com/library/test/success.html for Apple IOS version 6
and older, and to several possible target URLs for Apple IOS version 7 and later. If a response is received,
then the Internet access is assumed to be available and no further interaction is required. If no response is
received, then the Internet access is assumed to be blocked by the captive portal and Apple’s Captive Network
Assistant (CNA) auto-launches the pseudo-browser to request portal login in a controlled window. The CNA
may break when redirecting to an ISE captive portal. The controller prevents this pseudo-browser from popping
up.
You can now configure the controller to bypass WISPr detection process, so the web authentication interception
is only done when a user requests a web page leading to splash page load in user context, without the WISPr
detection being performed in the background.
Information About Fallback Policy with MAC Filtering and Web Authentication
You can configure a fallback policy mechanism that combines Layer 2 and Layer 3 security. In a scenario
where you have both MAC filtering and web authentication implemented, when a client tries to connect to a
WLAN using the MAC filter (RADIUS server), if the client fails the authentication, you can configure the
authentication to fall back to web authentication. When a client passes the MAC filter authentication, the web
authentication is skipped and the client is connected to the WLAN. With this feature, you can avoid
disassociations based on only a MAC filter authentication failure.
Restrictions
Mobility is not supported for SSIDs with security type configured for Webauth on MAC filter failure.
Note Before configuring a fallback policy, you must have MAC filtering enabled.
Note Before configuring a fallback policy, you must have MAC filtering enabled. To know more about how to
enable MAC filtering, see the Information About MAC Filtering of WLANs, on page 595 section.
Step 1 Enable or disable web authentication on a particular WLAN by entering this command:
config wlan security web-auth on-macfilter-failure wlan-id
AVVID Traffic Type AVVID IP DSCP QoS Profile AVVID 802.1p IEEE 802.11e
UP
Network control 56 (CS7) Platinum 7 7
AVVID Traffic Type AVVID IP DSCP QoS Profile AVVID 802.1p IEEE 802.11e
UP
Mission critical 26 (AF31) Gold 3 4
Scavenger 2 Bronze 0 1
Note The IEEE 802.11e UP value for DSCP values that are not mentioned in the table is calculated by considering
3 MSB bits of DSCP.
For example, the IEEE 802.11e UP value for DSCP 32 (100 000 in binary), would be the decimal equivalent
of the MSB (100) which is 4. The 802.11e UP value of DSCP 32 is 4.
b) Define the peak data rate for TCP traffic per user by entering the rate in Kbps in the Burst Data Rate text boxes. A
value of 0 indicates that the value specified in the selected QoS profile will take effect.
Note The burst data rate should be greater than or equal to the average data rate. Otherwise, the QoS policy may
block traffic to and from the wireless client.
Ensure that you configure the average data rate before you configure the burst data rate.
c) Define the average real-time rate for UDP traffic per user by entering the rate in Kbps in the Average Real-Time
Rate text boxes. A value of 0 indicates that the value specified in the selected QoS profile will take effect.
Note Average Data Rate is used to measure TCP traffic while Average Real-time rate is used for UDP traffic.
They are measured in kbps for all the entries. The values for Average Data Rate and Average Real-time rate
can be different because they are applied to different upper layer protocols such as TCP and UDP. These
different values for the rates do not impact the bandwidth.
d) Define the peak real-time rate for UDP traffic per user by entering the rate in Kbps in the Burst Real-Time Rate text
boxes. A value of 0 indicates that the value specified in the selected QoS profile will take effect.
Note The burst real-time rate should be greater than or equal to the average real-time rate. Otherwise, the QoS
policy may block traffic to and from the wireless client.
Step 2 To override QoS profile rate limit parameters, enter this command:
WLAN Identifier.................................. 1
Profile Name..................................... test
Network Name (SSID).............................. test
Status........................................... Enabled
MAC Filtering.................................... Disabled
Broadcast SSID................................... Enabled
AAA Policy Override.............................. Disabled
Number of Active Clients......................... 0
Exclusionlist.................................... Disabled
Session Timeout.................................. 0
Interface........................................ management
WLAN ACL......................................... unconfigured
DHCP Server...................................... 1.100.163.24
DHCP Address Assignment Required................. Disabled
Quality of Service............................... Silver (best effort)
WMM.............................................. Disabled
...
Prerequisites for Using QoS Enhanced BSS on Cisco 7921 and 7920 Wireless
IP Phones
Follow these guidelines to use Cisco 7921 and 7920 Wireless IP Phones with controllers:
• Aggressive load balancing must be disabled for each controller. Otherwise, the initial roam attempt by
the phone may fail, causing a disruption in the audio path.
• The Dynamic Transmit Power Control (DTPC) information element (IE) must be enabled using the
config 802.11b dtpc enable command. The DTPC IE is a beacon and probe information element that
allows the access point to broadcast information on its transmit power. The 7921 or 7920 phone uses
this information to automatically adjust its transmit power to the same level as the access point to which
it is associated. In this manner, both devices are transmitting at the same level.
• Both the 7921 and 7920 phones and the controllers support Cisco Centralized Key Management (CCKM)
fast roaming.
• When configuring WEP, there is a difference in nomenclature for the controller and the 7921 or 7920
phone. Configure the controller for 104 bits when using 128-bit WEP for the 7921 or 7920.
• For standalone 7921 phones, load-based CAC must be enabled, and the WMM Policy must be set to
Required on the WLAN.
• The controller supports traffic classification (TCLAS) coming from 7921 phones using firmware version
1.1.1. This feature ensures proper classification of voice streams to the 7921 phones.
• When using a 7921 phone with the 802.11a radio of a 1242 series access point, set the 24-Mbps data
rate to Supported and choose a lower Mandatory data rate (such as 12 Mbps). Otherwise, the phone
might experience poor voice quality.
Step 5 Select the 7920 AP CAC check box if you want to enable 7920 support mode for phones that require access
point-controlled CAC. The default value is unselected.
Step 6 Select the 7920 Client CAC check box if you want to enable 7920 support mode for phones that require client-controlled
CAC. The default value is unselected.
Note You cannot enable both WMM mode and client-controlled CAC mode on the same WLAN.
Step 1 Determine the ID number of the WLAN to which you want to add QBSS support by entering this command:
show wlan summary
Step 3 Configure WMM mode for 7921 phones and other devices that meet the WMM standard by entering this command:
config wlan wmm {disabled | allowed | required} wlan_id
where
• disabled disables WMM mode on the WLAN.
• allowed allows client devices to use WMM on the WLAN.
• required requires client devices to use WMM. Devices that do not support WMM cannot join the WLAN.
Step 4 Enable or disable 7920 support mode for phones that require client-controlled CAC by entering this command:
config wlan 7920-support client-cac-limit {enable | disable} wlan_id
Note You cannot enable both WMM mode and client-controlled CAC mode on the same WLAN.
Step 5 Enable or disable 7920 support mode for phones that require access point-controlled CAC by entering this command:
config wlan 7920-support ap-cac-limit {enable | disable} wlan_id
Step 8 Verify that the WLAN is enabled and the Dot11-Phone Mode (7920) text box is configured for compact mode by entering
this command:
show wlan wlan_id
Step 8 Choose Management > SNMP > Trap Logs to see the traps generated for failed calls. The Trap Logs page appears.
For example, log 0 in the figure shows that a call failed. The log provides the date and time of the call, a description of
the failure, and the reason why the failure occurred.
Step 1 Enable or disable VoIP snooping for a particular WLAN by entering this command:
config wlan call-snoop {enable | disable} wlan_id
Step 3 See the status of media session snooping on a particular WLAN by entering this command:
show wlan wlan_id
Information similar to the following appears:
WLAN Identifier.................................. 1
Profile Name..................................... wpa2-psk
Network Name (SSID).............................. wpa2-psk
Status........................................... Enabled
...
FlexConnect Local Switching........................ Disabled
Step 4 See the call information for an MSA client when media session snooping is enabled and the call is active by entering
this command:
show call-control client callInfo client_MAC_address
Information similar to the following appears:
Step 5 See the metrics for successful calls or the traps generated for failed calls by entering this command:
show call-control ap {802.11a | 802.11b} Cisco_AP {metrics | traps}
Information similar to the following appears when you enter show call-control ap {802.11a | 802.11b} Cisco_AP
metrics:
To aid in troubleshooting, the output of this command shows an error code for any failed calls. This table explains the
possible error codes for failed calls.
400 badRequest The request could not be understood because of malformed syntax.
403 forbidden The server understood the request but refuses to fulfill it.
405 methodNotallowed The method specified in the Request-Line is understood but not
allowed for the address identified by the Request-URI.
406 notAcceptabl The resource identified by the request is only capable of generating
response entities with content characteristics that are not acceptable
according to the Accept header text box sent in the request.
407 proxyAuthenticationRequired The client must first authenticate with the proxy.
408 requestTimeout The server could not produce a response within a suitable amount
of time, if it could not determine the location of the user in time.
409 conflict The request could not be completed due to a conflict with the
current state of the resource.
410 gone The requested resource is no longer available at the server, and no
forwarding address is known.
411 lengthRequired The server is refusing to process a request because the request
entity-body is larger than the server is willing or able to process.
413 requestEntityTooLarge The server is refusing to process a request because the request
entity-body is larger than the server is willing or able to process.
414 requestURITooLarge The server is refusing to service the request because the
Request-URI is longer than the server is willing to interpret.
415 unsupportedMediaType The server is refusing to service the request because the message
body of the request is in a format not supported by the server for
the requested method.
420 badExtension The server did not understand the protocol extension specified in
a Proxy-Require or Require header text box.
480 temporarilyNotAvailable The callee’s end system was contacted successfully, but the callee
is currently unavailable.
481 callLegDoesNotExist The UAS received a request that does not match any existing dialog
or transaction.
483 tooManyHops The server received a request that contains a Max-Forwards header
text box with the value zero.
486 busy The callee’s end system was contacted successfully, but the callee
is currently not willing or able to take additional calls at this end
system.
501 notImplemented The server does not support the functionality required to fulfill the
request.
502 badGateway The server, while acting as a gateway or proxy, received an invalid
response from the downstream server it accessed in attempting to
fulfill the request.
503 serviceUnavailable The server is temporarily unable to process the request because of
a temporary overloading or maintenance of the server.
504 serverTimeout The server did not receive a timely response from an external server
it accessed in attempting to process the request.
505 versionNotSupported The server does not support or refuses to support the SIP protocol
version that was used in the request.
600 busyEverywhere The callee’s end system was contacted successfully, but the callee
is busy or does not want to take the call at this time.
603 decline The callee’s machine was contacted successfully, but the user does
not want to or cannot participate.
604 doesNotExistAnywhere The server has information that the user indicated in the
Request-URI does not exist anywhere.
606 notAcceptable The user’s agent was contacted successfully, but some aspects of
the session description (such as the requested media, bandwidth,
or addressing style) were not acceptable.
Note If you experience any problems with media session snooping, enter the debug call-control {all | event} {enable
| disable} command to debug all media session snooping messages or events.
Bandwidth allocation depends on the median time calculated using the data rate from the Bandwidth Request
message and the packetization interval. For KTS-based CAC clients, the G.711 codec with 20 milliseconds
as the packetization interval is used to compute the medium time.
The controller releases the bandwidth after it receives the bandwidth release message from the client. When
the client roams to another AP, the controller releases the bandwidth on the previous AP and allocates bandwidth
on the new AP, in both intracontroller and intercontroller roaming scenarios. The controller releases the
bandwidth if the client is dissociated or if there is inactivity for 120 seconds. The controller does not inform
the client when the bandwidth is released for the client due to inactivity or dissociation of the client.
Step 1 To enable KTS-based CAC for a WLAN, enter the following command:
config wlan kts-cac enable wlan-id
Step 2 To enable the functioning of the KTS-based CAC feature, ensure you do the following:
a) Enable WMM on the WLAN by entering the following command:
config wlan wmm allow wlan-id
b) Enable ACM at the radio level by entering the following command:
config 802.11a cac voice acm enable
c) Enable the processing of the TSPEC inactivity timeout at the radio level by entering the following command:
config 802.11a cac voice tspec-inactivity-timeout enable
Related Commands
• To see whether the client supports KTS-based CAC, enter the following command:
show client detail client-mac-address
Information similar to the following appears:
Note You can reanchor roaming of voice clients for each WLAN.
Step 1 Enable or disable reanchoring of roaming voice clients for a particular WLAN by entering this command:
config wlan roamed-voice-client re-anchor {enable | disable} wlan id
Step 3 See the status of reanchoring roaming voice client on a particular WLAN by entering this command:
show wlan wlan_id
Information similar to the following appears:
WLAN Identifier.................................. 1
Profile Name..................................... wpa2-psk
Network Name (SSID).............................. wpa2-psk
Status........................................... Enabled
...
Call Snooping.................................... Enabled
Roamed Call Re-Anchor Policy..................... Enabled
Band Select...................................... Disabled
Load Balancing................................... Disabled
Step 4 Save your changes by entering this command:
save config
To support the seamless IPv6 Mobility, you might need to configure the following:
• Configuring RA Guard for IPv6 Clients
• Configuring RA Throttling for IPv6 Clients
• Configuring IPv6 Neighbor Discovery Caching
Note Currently, Windows Vista does not provide static stateless auto configuration
functionality. Therefore, DHCPv6 is required for seamless roaming. Otherwise, these
clients must manually renew their address after each change of VLANs.
• Roaming of IPv6 clients that are associated with a WLAN that is mapped to an untagged interface to
another WLAN that is mapped to a tagged interface is not supported.
• On the 7.4 release, the WLCs that have the same mobility group, same VLAN ID, and different IPv4
and IPv6 subnets, generate different IPv6 router advertisements. WLAN on these WLCs is assigned to
the same dynamic interface with the same VLAN ID on all the controllers. The client receives correct
IPv4 address; however it receives a router advertisement from the different subnets that reach the other
WLCs. There could be issue of no traffic from the client, because the first given IPv6 address to the
client does not match to the subnet for the IPv4 address. To resolve this, you can configure the WLCs
in different mobility group.
Note While adding or deleting IPv6 mobility peer, the SSH rules for bypassing traffic are
applicable for the 16666 port and for the pairs of IPs of the mobility peers.
• When AAA override is enabled on WLAN with flex local switching, the client must receive the IPv6
address from the VLAN returned by the AAA server. This implies that if a WLAN with both local
switching and AAA override enabled is mapped to VLAN X and the AAA server returns a VLAN Y;
then, the client must receive an address from VLAN Y. However, this is not supported in this controller
release.
Note IPv6 ping from Cisco WLC to a client is not supported if the client is in the management
subnet.
The configuration for IPv6 mobility is the same as IPv4 mobility and requires no separate software on the
client side to achieve seamless roaming. The controllers must be part of the same mobility group. Both IPv4
and IPv6 client mobility are enabled by default.
Note • IPv6 RA guard feature works on wireless clients only. This feature does not work on wired guest
access (GA).
• RA guard is also supported in FlexConnect local switching mode.
Step 1 Choose Controller > IPv6 > RA Guard to open the IPv6 RA Guard page. By default the IPv6 RA Guard on AP is
enabled.
Step 2 From the drop-down list, choose Disable to disable RA Guard. The controller also displays the clients that have been
identified as sending RA packets.
Step 3 Click Apply to commit your changes.
Step 4 Click Save Configuration to save your changes.
Step 1 Choose Controller > IPv6 > RA Throttle Policy page. By default the IPv6 RA Throttle Policy is disabled. Unselect
the check box to disable RA throttle policy.
Step 2 Configure the following parameters:
• Throttle period—The period of time for throttling. RA throttling takes place only after the Max Through limit is
reached for the VLAN or the Allow At-Most value is reached for a particular router. The range is from 10 seconds
to 86400 seconds. The default is 600 seconds.
• Max Through—The maximum number of RA packets on a VLAN that can be sent before throttling takes place.
The No Limit option allows an unlimited number of RA packets through with no throttling. The range is from 0
to 256 RA packets. The default is 10 RA packets.
• Interval Option—This option allows the controller to act differently based on the RFC 3775 value set in IPv6 RA
packets.
◦Passthrough— Allows any RA messages with the RFC 3775 interval option to go through without throttling.
◦Ignore—Causes the RA throttle to treat packets with the interval option as a regular RA and subject to
throttling if in effect.
◦Throttle—Causes the RA packets with the interval option to always be subject to rate limiting.
• Allow At-least—The minimum number of RA packets per router that can be sent as multicast before throttling
takes place. The range is from 0 to 32 RA packets.
• Allow At-most—The maximum number of RA packets per router that can be sent as multicast before throttling
takes place. The No Limit option allows an unlimited number of RA packets through the router. The range is from
0 to 256 RA packets.
Note When RA throttling occurs, only the first IPv6 capable router is allowed through. For networks that have
multiple IPv6 prefixes being served by different routers, you should disable RA throttling.
Step 7 Use the parameters on the General, Security, and Advanced tabs to configure this remote LAN. See the sections in the
rest of this chapter for instructions on configuring specific features.
Step 8 On the General tab, select the Status check box to enable this remote LAN. Be sure to leave it unselected until you have
finished making configuration changes to the remote LAN.
Note You can also enable or disable remote LANs from the WLANs page by selecting the check boxes to the left of
the IDs that you want to enable or disable, choosing Enable Selected or Disable Selected from the drop-down
list, and clicking Go.
Step 9 Click Apply to commit your changes.
Step 10 Click Save Configuration to save your changes.
• Enable or disable local EAP with the controller as an authentication server, by entering this command:
config remote-lan local-auth enable profile-name remote-lan-id
• If you are using an external AAA authentication server, use the following command:
config remote-lan radius_server auth {add | delete} remote-lan-id server id
config remote-lan radius_server auth {enable | disable} remote-lan-id
Note A with OfficeExtend access points in an access point group publishes up to 15 WLANs
to each connected OfficeExtend access point because it reserves one WLAN for the
personal SSID.
• We recommend that you configure all Flex+Bridge APs in a mesh tree (in the same sector) in the same
AP group and the same FlexConnect group, to inherit the WLAN-VLAN mappings properly.
same subnet or VLAN. However, you can choose to distribute the load among several interfaces or to a group
of users based on specific criteria such as individual departments (such as Marketing) by creating access point
groups. Additionally, these access point groups can be configured in separate VLANs to simplify network
administration.
Step 1 Configure the appropriate dynamic interfaces and map them to the desired VLANs.
For example, to implement the network described in the Information About Access Point Groups section, create dynamic
interfaces for VLANs 61, 62, and 63 on the controller. See the Configuring Dynamic Interfaces section for information
about how to configure dynamic interfaces.
Step 2 Create the access point groups. See the Creating Access Point Groups section.
Step 3 Create a RF profile. See the Creating an RF Profile section.
Step 4 Assign access points to the appropriate access point groups. See the Creating Access Point Groups section.
Step 5 Apply the RF profile on the AP groups. See the Applying RF Profile to AP Groups section.
Step 1 Choose WLANs > Advanced > AP Groups to open the AP Groups page.
This page lists all the access point groups currently created on the controller. By default, all access points belong to the
default access point group “default-group,” unless you assign them to other access point groups.
Note The controller creates a default access point group and automatically populates it with the first 16 WLANs
(WLANs with IDs 1 through 16, or fewer if 16 WLANs are not configured). This default group cannot be
modified (you cannot add WLANs to it nor delete WLANs from it). It is dynamically updated whenever the
first 16 WLANs are added or deleted. If an access point does not belong to an access point group, it is assigned
to the default group and uses the WLANs in that group. If an access point joins the controller with an undefined
access point group name, the access point keeps its group name but uses the WLANs in the default-group access
point group.
Step 2 Click Add Group to create a new access point group. The Add New AP Group section appears at the top of the page.
Step 3 In the AP Group Name text box, enter the group’s name.
Step 4 In the Description text box, enter the group’s description.
Step 5 In the NAS-ID text box, enter the network access server identifier for the AP group.
Step 6 Click Add. The newly created access point group appears in the list of access point groups on the AP Groups page.
Note If you ever want to delete this group, hover your cursor over the blue drop-down arrow for the group and choose
Remove. An error message appears if you try to delete an access point group that is used by at least one access
point. Before deleting an access point group in controller software release 6.0 or later releases, move all access
points in the group to another group. The access points are not moved to the default-group access point group
as in previous releases.
Step 7 Click the name of the group to edit this new group. The AP Groups > Edit (General) page appears.
Step 8 Change the description of this access point group by entering the new text in the AP Group Description text box and
click Apply.
Step 9 Choose the WLANs tab to open the AP Groups > Edit (WLANs) page. This page lists the WLANs that are currently
assigned to this access point group.
Step 10 Click Add New to assign a WLAN to this access point group. The Add New section appears at the top of the page.
Step 11 From the WLAN SSID drop-down list, choose the SSID of the WLAN.
Step 12 From the Interface Name drop-down list, choose the interface to which you want to map the access point group. Choose
the quarantine VLAN if you plan to enable network admission control (NAC) out-of-band support.
Note The interface name in the default-group access point group matches the WLAN interface.
Step 13 Select the SNMP NAC State check box to enable NAC out-of-band support for this access point group. To disable NAC
out-of-band support, leave the check box unselected, which is the default value.
Step 14 Click Add to add this WLAN to the access point group. This WLAN appears in the list of WLANs that are assigned to
this access point group.
Note If you ever want to remove this WLAN from the access point group, hover your cursor over the blue drop-down
arrow for the WLAN and choose Remove.
Step 15 Repeat Step 10 through Step 14 to add any additional WLANs to this access point group.
Step 16 Choose the APs tab to assign access points to this access point group. The AP Groups > Edit (APs) page lists the access
points that are currently assigned to this group as well as any access points that are available to be added to the group.
If an access point is not currently assigned to a group, its group name appears as “default-group”.
Step 17 Select the check box to the left of the access point name and click Add APs to add an access point to this access point
group. The access point, after it is reloaded, appears in the list of access points currently in this access point group. The
AP has to be reloaded if the AP has to be moved from one group to another.
Note To select all of the available access points at once, select the AP Name check box. All of the access points are
then selected.
Note If you ever want to remove an access point from the group, select the check box to the left of the access point
name and click Remove APs. To select all of the access points at once, select the AP Name check box. All of
the access points are then removed from this group.
Note If you ever want to change the access point group to which an access point belongs, choose Wireless > Access
Points > All APs > ap_name > Advanced tab, choose the name of another access point group from the AP
Group Name drop-down list, and click Apply.
Step 18 In the 802.11u tab, do the following:
a) Choose a HotSpot group that groups similar HotSpot venues.
b) Choose a venue type that is based on the HotSpot venue group that you choose.
c) To add a new venue, click Add New Venue and enter the language name that is used at the venue and the venue name
that is associated with the basic service set (BSS). This name is used in cases where the SSID does not provide enough
information about the venue.
d) Select the operating class(es) for the AP group.
e) Click Apply.
Step 19 Click Save Configuration.
Step 5 Configure a WLAN radio policy on the access point group by entering this command:
config wlan apgroup wlan-radio-policy apgroup_name wlan_id {802.11a-only | 802.11bg | 802.11g-only | all}
Step 6 Assign an access point to an access point group by entering this command:
config ap group-name group_name Cisco_AP
Note To remove an access point from an access point group, reenter this command and assign the access point to
another group.
Step 7 To configure HotSpot for the AP group, enter this command:
config wlan apgroup hotspot {venue | operating-class}
• You can enable only IPv4 DHCP packets and not IPv6 DHCP packets for 802.1Q-in-Q VLAN tagging.
• The IETF attribute which is a tunnel-type is required to override the C-VLAN.
• C-VLAN can be set with tunnel-private-group-ID /tunnel-type and tunnel-private-group-id.
Step 1 Choose WLANs > Advanced > AP Groups to open the AP Groups page.
Step 2 Click an AP group Name to open the corresponding AP Group > Edit page.
Step 3 Click the General tab to configure the 802.1Q-in-Q VLAN tagging details.
Step 4 Select the Enable Client Traffic QinQ check box to enable 802.1Q-in-Q VLAN tagging for the AP group.
Step 5 Select the Enable DHCPv4 QinQ check box to enable 802.1Q-in-Q VLAN tagging of IPv4 DHCP packets in the AP
group.
Step 6 In the QinQ Service VLAN ID text box, enter the VLAN ID for 802.1Q-in-Q VLAN tagging.
Step 7 Click Apply.
Step 1 Enable or disable 802.1Q-in-Q VLAN tagging for an AP group by entering this command:
config wlan apgroup qinq tagging client-traffic apgroup_name {enable | disable}
By default, 802.1Q-in-Q tagging of client traffic for an AP group is disabled.
Step 2 Configure the service VLAN for the AP group by entering this command:
config wlan apgroup qinq service-vlan apgroup_name vlan_id
Step 3 Enable or disable IPv4 DHCP packets of the client traffic in the AP group by entering this command::
config wlan apgroup qinq tagging dhcp-v4 apgroup_name {enable | disable}
Note You must enable 802.1Q-in-Q tagging of client traffic before you enable 802.1Q-in-Q tagging of DHCPv4
traffic.
By default, 802.1Q-in-Q tagging of DHCPv4 traffic for an AP group is disabled.
Step 4 Enable or disable 802.1Q-in-Q VLAN tagging for EAP for Global System for Mobile Communications (GSM) Subscriber
Identity Module (EAP-SIM) or EAP for Authentication and Key Agreement-authenticated client traffic in the AP group
by entering this command:
config wlan apgroup qinq tagging eap-sim-aka apgroup_name {enable | disable}
When you enable 802.1Q-in-Q tagging of client traffic, the 802.1Q-in-Q tagging of EAP for Authentication and Key
Agreement (EAP-AKA) and EAP-SIM traffic is enabled.
NAS-identifier................................... CTB1
Client Traffic QinQ Enable....................... TRUE
DHCPv4 QinQ Enable............................... TRUE
AP Operating Class............................... Not-configured
add it back to the AP group. You can also work around this restriction by disabling the network
that will be affected by the changes that you will be making either for 802.11a or 802.11b.
◦You cannot delete an AP group that has APs assigned to it.
◦You cannot delete an RF profile that is applied to an AP group.
• If you enable Out of Box, save the configuration, and then reboot the CIsco WLC, the status of Out of
Box is changed to disabled. This behavior is observed in Cisco WiSM2, Cisco 5500 Series WLC, and
Cisco 2500 Series WLC. The workaround is to enable Out of Box again after you reboot the Cisco WLC.
Note The application of an RF profile does not change the AP’s status in RRM. It is still in global configuration
mode controlled by RRM.
• When Out-of-Box is enabled, default-group APs currently associated with the controller remain
in the default group until they reassociate with the controller.
• All default-group APs that subsequently associate with the controller (existing APs on the same
controller that have dropped and reassociated, or APs from another controller) are placed in the
Out-of-Box AP group.
Note When removing APs from the Out-of-Box AP group for production use, we recommend
that you assign the APs to a custom AP group to prevent inadvertently having them
revert to the Out-of-Box AP group.
• Special RF profiles are created per 802.11 band. These RF profiles have default settings for all the
existing RF parameters and additional new configurations.
Note When you disable this feature after you enable it, only subscription of new APs to the
Out of Box AP group stops. All APs that are subscribed to the Out of Box AP Group
remain in this AP group. The network administrators can move such APs to the default
group or a custom AP group upon network convergence.
• Band Select Configurations— Band Select addresses client distribution between the 2.4-GHz and 5-GHz
bands by first understanding the client capabilities to verify whether a client can associate on both
2.4-GHz and 5-GHz spectrum. Enabling band select on a WLAN forces the AP to do probe suppression
on the 2.4-GHz band that ultimately moves dual band clients to 5-GHz spectrum. You can configure
the following band select parameters per AP Group:
• Probe response—Probe responses to clients that you can enable or disable.
• Probe Cycle Count—Probe cycle count for the RF profile. The cycle count sets the number of
suppression cycles for a new client.
• Cycle Threshold—Time threshold for a new scanning RF Profile band select cycle period. This
setting determines the time threshold during which new probe requests from a client come in a
new scanning cycle.
• Suppression Expire—Expiration time for pruning previously known 802.11b/g clients. After this
time elapses, clients become new and are subject to probe response suppression.
• Dual Band Expire—Expiration time for pruning previously known dual-band clients. After this
time elapses, clients become new and are subject to probe response suppression.
• Client RSSI—Minimum RSSI for a client to respond to a probe.
• Load Balancing Configurations—Load balancing maintains fair distribution of clients across APs. You
can configure the following parameters:
• Window—Load balancing sets client association limits by enforcing a client window size. For
example, if the window size is defined as 3, assuming fair client distribution across the floor area,
then an AP should have no more than 3 clients associated with it than the group average.
• Denial—The denial count sets the maximum number of association denials during load balancing.
The window size becomes part of the algorithm that determines whether an access point is too heavily loaded to
accept more client associations:
load-balancing window + client associations on AP with the lightest load = load-balancing threshold
In the group of access points accessible to a client device, each access point has a different number of client associations.
The access point with the lowest number of clients has the lightest load. The client window size plus the number of
clients on the access point with the lightest load forms the threshold. Access points with more client associations
than this threshold is considered busy, and clients can associate only to access points with client counts lower than
the threshold.
The denial count sets the maximum number of association denials during load balancing.
b) In the Band Select area, select or unselect the Probe Response check box.
Note The Band Select configurations are available only for the 802.11b/g RF profiles.
c) In the Cycle Count text box, enter a value that sets the number of suppression cycles for a new client. The default
count is 2.
d) In the Cycle Threshold text box, enter a time period in milliseconds that determines the time threshold during which
new probe requests from a client from a new scanning cycle. The default cycle threshold is 200 milliseconds.
e) In the Suppression Expire text box, enter a time period after which the 802.11 b/g clients become new and are subject
to probe response suppression.
f) In the Dual Band Expire text box, enter a time period after which the dual band clients become new and are subject
to probe response suppression.
g) In the Client RSSI text box, enter the minimum RSSI for a client to respond to a probe.
Step 11 Click Apply to commit your changes.
Step 12 Click Save Configuration to save your changes.
Step 1 To configure the out-of-box status for all RF profiles, enter this command:
config rf-profile out-of-box {enable | disable}
Step 4 To configure the data rates to be applied to the APs of this profile, enter this command:
config rf-profile data-rates {802.11a | 802.11b} {disabled | mandatory | supported} rate profile-name
Step 5 To configure the maximum and minimum power level assignment, that is the maximum and minimum power that the
APs in this RF profile are allowed to use, enter this command:
config rf-profile {tx-power-max | tx-power-min} power-value profile-name
Step 6 To configure a custom TPC power threshold for either Version1 or Version 2 of TPC, enter this command:
Step 8 To configure the maximum number of clients to be allowed per AP radio, enter this command:
config rf-profile max-clients num-of-clients profile-name
Step 9 To configure the client trap threshold value, enter this command:
config rf-profile client-trap-threshold threshold-value profile-name
Step 13 Configure the 802.11n only mode for an access point group base by entering this command:
config rf-profile 11n-client-only {enable | disable} rf-profile-name
In the 802.11n only mode, the access point broadcasts support for 802.11n speeds. Only 802.11n clients are allowed to
associate with the access point
Step 1 Choose WLANs > Advanced > AP Groups to open the AP Groups page.
Step 2 Click the AP Group Name to open the AP Group > Edit page.
Step 3 Click the RF Profile tab to configure the RF profile details. You can choose an RF profile for each band (802.11a/802.11b)
or you can choose just one or none to apply to this group.
Note Until you choose the APs and add them to the new group, no configurations are applied. You can save the new
configuration as is, but no profiles are applied. Once you choose the APs to move the AP group, the process of
moving the APs into the new group reboots the APs and the configurations for the RF profiles are applied to
the APs in that AP group.
Step 4 Click the APs tab and choose the APs to add to the AP group.
Step 5 Click Add APs to add the selected APs to the AP group. A warning message displays that the AP group will reboot the
APs will rejoin the controller.
Note APs cannot belong to two AP groups at
once.
Step 6 Click Apply. The APs are added to the AP Group.
Note The conditional web redirect feature is available only for WLANs that are configured for 802.1X or
WPA+WPA2 Layer 2 security.
After you configure the RADIUS server, you can then configure the conditional web redirect on the controller
using either the controller GUI or CLI.
Note The splash page web redirect feature is available only for WLANs that are configured for 802.1X or
WPA+WPA2 Layer 2 security with 802.1x key management. Preshared key management is not supported
with any Layer 2 security method.
Suppose there are backend applications running on the wireless clients and they use HTTP or HTTPS port
for their communication. If the applications start communicating before the actual web page is opened, the
redirect functionality does not work with web passthrough.
After you configure the RADIUS server, you can then configure the splash page web redirect on the controller
using either the controller GUI or CLI.
Note These instructions are specific to the CiscoSecure ACS; however, they should be similar to those for other
RADIUS servers.
Step 1 From the CiscoSecure ACS main menu, choose Group Setup.
Step 2 Click Edit Settings.
Step 3 From the Jump To drop-down list, choose RADIUS (Cisco IOS/PIX 6.0).
Step 4 Select the [009\001] cisco-av-pair check box.
Step 5 Enter the following Cisco AV-pairs in the [009\001] cisco-av-pair edit box to specify the URL to which the user is
redirected and, if configuring conditional web redirect, the conditions under which the redirect takes place, respectively:
url-redirect=http://url
url-redirect-acl=acl_name
Step 2 Enable or disable splash page web redirect by entering this command:
config wlan security splash-page-web-redir {enable | disable} wlan_id
Step 4 See the status of the web redirect features for a particular WLAN by entering this command:
show wlan wlan_id
Information similar to the following appears:
WLAN Identifier.................................. 1
Profile Name..................................... test
Network Name (SSID).............................. test
...
Web Based Authentication......................... Disabled
Web-Passthrough.................................. Disabled
Conditional Web Redirect......................... Disabled
Splash-Page Web Redirect......................... Enabled
...
Note Disabling accounting servers disables all accounting operations and prevents the controller from falling
back to the default RADIUS server for the WLAN.
Note You can disable coverage hole detection on a per-WLAN basis. When you disable coverage hole detection
on a WLAN, a coverage hole alert is still sent to the controller, but no other processing is done to mitigate
the coverage hole. This feature is useful for guest WLANs where guests are connected to your network
for short periods of time and are likely to be highly mobile.
Step 3 See the coverage hole detection status for a particular WLAN by entering this command:
show wlan wlan-id
Information similar to the following appears:
WLAN Identifier.................................. 2
Profile Name..................................... wlan2
Network Name (SSID).............................. 2
. . .
CHD per WLAN.................................. Disabled
Note See the Cisco NAC appliance configuration guides for configuration instructions at
http://www.cisco.com/c/en/us/support/security/nac-appliance-clean-access/
products-installation-and-configuration-guides-list.html.
• If you want to enable NAC on an access point group VLAN, you must first enable NAC on the WLAN.
Then you can enable or disable NAC on the access point group VLAN. If you ever decide to disable
NAC on the WLAN, be sure to disable it on the access point group VLAN as well.
• The NAC appliance supports up to 3500 users, and the controller supports up to 5000 users. Multiple
NAC appliances might need to be deployed.
• If you want to enable NAC on an access point group VLAN, you must first enable NAC on the WLAN.
Then you can enable or disable NAC on the access point group VLAN. If you ever decide to disable
NAC on the WLAN, be sure to disable it on the access point group VLAN as well.
• The NAC appliance supports up to 3500 users, and the controller supports up to 5000 users. Multiple
NAC appliances might need to be deployed.
• In controller software releases prior to 5.1, the controller integrates with the NAC appliance only in
in-band mode, where the NAC appliance must remain in the data path. For in-band mode, a NAC
appliance is required at each authentication location (such as at each branch or for each controller), and
all traffic must traverse the NAC enforcement point. In controller software release 5.1 or later releases,
the controller can integrate with the NAC appliance in out-of-band mode, where the NAC appliance
remains in the data path only until clients have been analyzed and cleaned. Out-of-band mode reduces
the traffic load on the NAC appliance and enables centralized NAC processing.
• NAC out-of-band integration is supported only on WLANs configured for FlexConnect central switching.
It is not supported for use on WLANs configured for FlexConnect local switching.
To implement the NAC out-of-band feature on the controller, you must enable NAC support on the WLAN
or guest LAN and then map this WLAN or guest LAN to an interface that is configured with a quarantine
VLAN (untrusted VLAN) and an access VLAN (trusted VLAN). When a client associates and completes
Layer 2 authentication, the client obtains an IP address from the access VLAN subnet, but the client state is
Quarantine. While deploying the NAC out-of-band feature, be sure that the quarantine VLAN is allowed only
between the Layer 2 switch on which the controller is connected and the NAC appliance and that the NAC
appliance is configured with a unique quarantine-to-access VLAN mapping. Client traffic passes into the
quarantine VLAN, which is trunked to the NAC appliance. After posture validation is completed, the client
is prompted to take remedial action. After cleaning is completed, the NAC appliance updates the controller
to change the client state from Quarantine to Access.
The link between the controller and the switch is configured as a trunk, enabling the quarantine VLAN (110)
and the access VLAN (10). On the Layer 2 switch, the quarantine traffic is trunked to the NAC appliance
while the access VLAN traffic goes directly to the Layer 3 switch. Traffic that reaches the quarantine VLAN
on the NAC appliance is mapped to the access VLAN based on a static mapping configuration.
Figure 43: Example of NAC Out-of-Band Integration
Note We recommend that you configure unique quarantine VLANs throughout your network. If multiple controllers
are configured in the same mobility group and access interfaces on all controllers are in the same subnet, it
is mandatory to have the same quarantine VLAN if there is only one NAC appliance in the network. If
multiple controllers are configured in the same mobility group and access interfaces on all controllers are
in different subnets, it is mandatory to have different quarantine VLANs if there is only one NAC appliance
in the network.
g) Configure any remaining text boxes for this interface, such as the IP address, netmask, and default gateway.
h) Click Apply to save your changes.
Step 2 Configure NAC out-of-band support on a WLAN or guest LAN as follows:
a) Choose WLANs to open the WLANs page.
b) Click the ID number of the desired WLAN or guest LAN. The WLANs > Edit page appears.
c) Choose the Advanced tab to open the WLANs > Edit (Advanced) page.
d) Configure NAC out-of-band support for this WLAN or guest LAN by selecting the NAC State check box. To disable
NAC out-of-band support, leave the check box unselected, which is the default value.
e) Click Apply to commit your changes.
Step 3 Configure NAC out-of-band support for a specific access point group as follows:
a) Choose WLANs > Advanced > AP Groups to open the AP Groups page.
b) Click the name of the desired access point group.
c) Choose the WLANs tab to open the AP Groups > Edit (WLANs) page.
d) Click Add New to assign a WLAN to this access point group. The Add New section appears at the top of the page.
e) From the WLAN SSID drop-down list, choose the SSID of the WLAN.
f) From the Interface Name drop-down list, choose the interface to which you want to map the access point group.
Choose the quarantine VLAN if you plan to enable NAC out-of-band support.
g) To enable NAC out-of-band support for this access point group, select the NAC State check box. To disable NAC
out-of-band support, leave the check box unselected, which is the default value.
h) Click Add to add this WLAN to the access point group. This WLAN appears in the list of WLANs assigned to this
access point group.
Note If you ever want to remove this WLAN from the access point group, hover your cursor over the blue
drop-down arrow for the WLAN and choose Remove.
Step 4 Click Save Configuration to save your changes.
Step 5 See the current state of the client (Quarantine or Access) as follows:
a) Choose Monitor > Clients to open the Clients page.
b) Click the MAC address of the desired client to open the Clients > Detail page. The NAC state appears under the
Security Information section.
Note The client state appears as “Invalid” if the client is probing, has not yet associated to a WLAN, or cannot
complete Layer 2 authentication.
Step 1 Configure the quarantine VLAN for a dynamic interface by entering this command:
Step 2 Enable or disable NAC out-of-band support for a WLAN or guest LAN by entering this command:
config {wlan | guest-lan} nac {enable | disable} {wlan_id | guest_lan_id}
Step 3 Enable or disable NAC out-of-band support for a specific access point group by entering this command:
config wlan apgroup nac {enable | disable} group_name wlan_id
Step 5 See the configuration of a WLAN or guest LAN, including the NAC state by entering this command:
show {wlan wlan_ id | guest-lan guest_lan_id}
Information similar to the following appears:
WLAN Identifier.................................. 1
Profile Name..................................... wlan
Network Name (SSID).............................. wlan
Status........................................... Disabled
MAC Filtering.................................... Disabled
Broadcast SSID................................... Enabled
AAA Policy Override.............................. Disabled
Network Admission Control
NAC-State...................................... Enabled
Quarantine VLAN............................. 110
...
Step 6 See the current state of the client (either Quarantine or Access) by entering this command:
show client detailed client_mac
Information similar to the following appears:
Note The client state appears as “Invalid” if the client is probing, has not yet associated to a WLAN, or cannot complete
Layer 2 authentication.
Note Client ARP forwarding will not work if any one of the two scenarios, mentioned above,
is not configured.
• The passive client feature is not supported with the AP groups and FlexConnect centrally switched
WLANs.
• Power for battery-operated devices such as mobile phones and printers is preserved because they do not
have to respond to every ARP requests.
Since the wireless controller does not have any IP related information about passive clients, it cannot respond
to any ARP requests. The current behavior does not allow the transfer of ARP requests to passive clients. Any
application that tries to access a passive client will fail.
The passive client feature enables the ARP requests and responses to be exchanged between wired and wireless
clients. This feature when enabled, allows the controller to pass ARP requests from wired to wireless clients
until the desired wireless client gets to the RUN state.
Note For FlexConnect APs with locally switched WLANs, passive client feature enables the broadcast of ARP
requests and the APs respond on behalf of the client.
Step 3 From the AP Multicast Mode drop-down list, choose Multicast. The Multicast Group Address text box is displayed.
Note It is not possible to configure the AP multicast mode for Cisco Flex 7500 Series controllers because only unicast
is supported.
Step 4 In the Multicast Group Address text box, enter the IP address of the multicast group.
Step 5 Click Apply.
Step 6 Enable global multicast mode as follows:
a) Choose Controller > Multicast.
b) Check the Enable Global Multicast Mode check box.
Step 2 Select the Enable Global Multicast Mode check box to enable the multicast mode. This step configures the controller
to use the multicast method to send multicast packets to a CAPWAP multicast group.
Note It is not possible to configure Global Multicast Mode for Cisco Flex 7500 Series Controllers.
Step 3 Select the Enable IGMP Snooping check box to enable the IGMP snooping. The default value is disabled.
Step 4 In the IGMP Timeout text box to set the IGMP timeout, enter a value between 30 and 7200 seconds.
Step 5 Click Apply to commit your changes.
Step 1 Choose WLANs > WLANs > WLAN ID to open the WLANs > Edit page. By default, the General tab is displayed.
Step 2 Choose the Advanced tab.
Step 3 Select the Passive Client check box to enable the passive client feature.
Step 4 Click Apply to commit your changes.
Step 2 Configure the controller to use multicast to send multicast to an access point by entering this command:
config network multicast mode multicast multicast_group_IP_address
Step 6 Display the passive client information on a particular WLAN by entering this command:
show wlan 2
Step 7 Verify if the passive client is associated correctly with the AP and if the passive client has moved into the DHCP required
state at the controller by entering this command:
debug client mac_address
Step 8 Display the detailed information for a client by entering this command:
show client detail mac_address
Step 9 Check if the client moves into the run state, when a wired client tries to contact the client by entering this command:
debug client mac_address
Step 10 Configure and check if the ARP request is forwarded from the wired side to the wireless side by entering this command:
debug arp all enable
Note Cisco WLC detects duplicate IP addresses based on the ARP table, and not based on the VLAN information.
If two clients in different VLANs are using the same IP address, Cisco WLC reports IP conflict and sends
GARP. This is not limited to two wired clients, but also for a wired client and a wireless client.
Note DHCP is required for DHCP profiling and Webauth for HTTP user agent.
• With profiling enabled for local switching FlexConnect mode APs, only VLAN override is supported
as an AAA override attribute.
• While the controller parses the DHCP profiling information every time the client sends a request, the
profiling information is sent to ISE only once.
• Custom profiles cannot be created for this release.
• This release contains 88 pre-existing policies where CLI is check only except if you create a policy.
• When local profiling is enabled radius profiling is not allowed on a particular WLAN.
• Only the first policy rule that matches is applied.
• Only 16 policies per WLAN can be configured and globally 16 policies can be allowed.
• Policy action is done only after L2/L3 authentication is complete or when the device sends http traffic
and gets the device profiled. Profiling and policing actions will happen more than once per client.
• If AAA override is enabled and if you get any AAA attributes from the AAA server other than role type,
configured policy does not apply since the AAA override attributes have a higher precedence.
Note Use the all parameter to configure client profiling based on both DHCP and HTTP.
• Enable or disable client profiling in Local mode for a WLAN based on HTTP, DHCP, or both by entering
this command:
config wlan profiling local {dhcp | http | all} {enable | disable} wlan-id
• To see the status of client profiling on a WLAN, enter the following command:
show wlan wlan-id
• To enable or disable debugging of client profiling, enter the following command:
debug profiling {enable | disable}
Step 1 Enter the config wlan disable wlan-id command to disable the WLAN.
Step 2 Enter the following command to enable or disable the per-WLAN RADIUS source support:
config wlan radius_server overwrite-interface {enable | disable} wlan-id
Note When enabled, the controller uses the interface specified on the WLAN configuration as identity and source for
all RADIUS related traffic on that WLAN. When disabled, the controller uses the management interface as the
identity in the NAS-IP-Address attribute. If the RADIUS server is on a directly connected dynamic interface,
the RADIUS traffic will be sourced from that interface. Otherwise, the management IP address is used. In all
cases, the NAS-IP-Address attribute remains the management interface, unless the feature is enabled.
Step 3 Enable either an AP group's interface or a WLAN's interface for RADIUS packet routing by entering these commands:
• AP group's interface—config wlan radius_server overwrite-interface apgroup wlan-id
• WLAN's interface—config wlan radius_server overwrite-interface wlan wlan-id
WLAN Identifier.................................. 4
Profile Name..................................... example
Network Name (SSID).............................. example
Status........................................... Enabled
MAC Filtering.................................... Disabled
Broadcast SSID................................... Enabled
AAA Policy Override.............................. Disabled
Network Admission Control
...
Radius Servers
Authentication................................ Global Servers
Accounting.................................... Global Servers
Overwrite Sending Interface................... Enabled
Local EAP Authentication......................... Disabled
d) In the HESSID box, enter the homogenous extended service set identifier (HESSID) value. The HESSID is a 6-octet
MAC address that identifies the homogeneous ESS.
e) If the IP address is in the IPv4 format, then from the IPv4 Type drop-down list, choose the IPv4 address type.
f) From the IPv6 Type drop-down list, choose whether you want to make the IPv6 address type available or not.
Step 5 In the OUI List area, do the following:
a) In the OUI text box, enter the Organizationally Unique Identifier, which can be a hexadecimal number represented
in 3 or 5 bytes (6 or 10 characters). For example, AABBDF.
b) Select the Is Beacon check box to enable the OUI beacon responses.
Note You can have a maximum of 3 OUIs with this field
enabled.
c) From the OUI Index drop-down list, choose a value from 1 to 32. The default is 1.
d) Click Add to add the OUI entry to the WLAN.
To remove this entry, hover your mouse pointer over the blue drop-down image and choose Remove.
config wlan hotspot dot11u domain {{{add | modify} wlan-id domain-index domain-name} | {delete
wlan-id domain-index}}
• To configure a homogenous extended service set identifier (HESSID) value for a WLAN, enter this
command:
config wlan hotspot dot11u hessid hessid wlan-id
The HESSID is a 6-octet MAC address that identifies the homogeneous ESS.
• To configure the IP address availability type for the IPv4 and IPv6 IP addresses on the WLAN, enter
this command:
config wlan hotspot dot11u ipaddr-type ipv4-type ipv6-type wlan-id
• To configure the network authentication type, enter this command:
config wlan hotspot dot11u auth-type network-auth wlan-id
• To configure the Roaming Consortium OI list, enter this command:
config wlan hotspot dot11u roam-oi {{{add | modify} wlan-id oi-index oi is-beacon} | {delete wlan-id
oi-index}}
• To configure the 802.11u network type and internet access, enter this command:
config wlan hotspot dot11u network-type wlan-id network-type internet-access
• To configure the realm for the WLAN, enter this command:
config wlan hotspot dot11u nai-realm {{{add | modify} realm-name wlan-id realm-index realm-name
| {delete realm-name wlan-id realm-index}}
• To configure the authentication method for the realm, enter this command:
config wlan hotspot dot11u nai-realm {add | modify} auth-method wlan-id realm-index eap-index
auth-index auth-method auth-parameter
• To delete the authentication method for the realm, enter this command:
config wlan hotspot dot11u nai-realm delete auth-method wlan-id realm-index eap-index auth-index
• To configure the extensible authentication protocol (EAP) method for the realm, enter this command:
config wlan hotpspot dot11u nai-realm {add | modify} eap-method wlan-id realm-index eap-index
eap-method
• To delete the EAP method for the realm, enter this command:
config wlan hotspot dot11u nai-realm delete eap-method wlan-id realm-index eap-index
Note The Downstream Group-Addressed Forwarding (DGAF) bit in the Hotspot 2.0 IE will not be updated
automatically until you disable and enable the WLAN.
Step 6 In the Port Config List area, perform the following tasks:
a) From the IP Protocol drop-down list, choose the IP protocol that you want to enable.
b) From the Port No drop-down list, choose the port number that is enabled on the WLAN.
c) From the Status drop-down list, choose the status of the port.
d) From the Index drop-down list, choose an index value for the port configuration.
e) Click Add to add the port configuration parameters.
To remove a port configuration list, hover your mouse over the blue drop-down arrow and choose Remove.
Note The character '?' is not supported in the value part of the commands.
Tip Press the tab key after entering a keyword or argument to get a list of valid values for
the command.
Step 1 Click Wireless > All APs to open the All APs page.
Step 2 Click the AP Name link to configure the HotSpot parameters on the desired access point. The AP Details page appears.
Step 3 Under the General Tab, configure the following parameters:
• Venue Group—The venue category that this access point belongs to. The following options are available:
◦Unspecified
◦Assembly
◦Business
◦Educational
◦Factory and Industrial
◦Institutional
◦Mercantile
◦Residential
◦Storage
◦Utility and Misc
◦Vehicular
◦Outdoor
• Venue Type—Depending on the venue category selected above, the venue type drop-down list displays options
for the venue type.
• Venue Name—Venue name that you can provide to the access point. This name is associated with the BSS. This
is used in cases where the SSID does not provide enough information about the venue.
• Language—The language used. An ISO-14962-1997 encoded string defining the language. This is a three character
language code. Enter the first three letters of the language in English (For example, eng for English).
Tip Press the tab key after entering a keyword or argument to get a list of valid values for
the command.
• config ap venue delete ap-name—Deletes the venue related information from the access point.
ASSEMBLY 1
• 0—UNSPECIFIED ASSEMBLY
• 1—ARENA
• 2—STADIUM
• 3—PASSENGER TERMINAL (E.G., AIRPORT, BUS,
FERRY, TRAIN STATION)
• 4—AMPHITHEATER
• 5—AMUSEMENT PARK
• 6—PLACE OF WORSHIP
• 7—CONVENTION CENTER
• 8—LIBRARY
• 9—MUSEUM
• 10—RESTAURANT
• 11—THEATER
• 12—BAR
• 13—COFFEE SHOP
• 14—ZOO OR AQUARIUM
• 15—EMERGENCY COORDINATION CENTER
EDUCATIONAL 3
• 0—UNSPECIFIED EDUCATIONAL
• 1—SCHOOL, PRIMARY
• 2—SCHOOL, SECONDARY
• 3—UNIVERSITY OR COLLEGE
FACTORY-INDUSTRIAL 4
• 0—UNSPECIFIED FACTORY AND INDUSTRIAL
• 1—FACTORY
INSTITUTIONAL 5
• 0—UNSPECIFIED INSTITUTIONAL
• 1—HOSPITAL
• 2—LONG-TERM CARE FACILITY (E.G., NURSING
HOME, HOSPICE, ETC.)
• 3—ALCOHOL AND DRUG RE-HABILITATION
CENTER
• 4—GROUP HOME
• 5—PRISON OR JAIL
RESIDENTIAL 7
• 0—UNSPECIFIED RESIDENTIAL
• 1—PRIVATE RESIDENCE
• 2—HOTEL OR MOTEL
• 3—DORMITORY
• 4—BOARDING HOUSE
VEHICULAR 10
• 0—UNSPECIFIED VEHICULAR
• 1—AUTOMOBILE OR TRUCK
• 2—AIRPLANE
• 3—BUS
• 4—FERRY
• 5—SHIP OR BOAT
• 6—TRAIN
• 7—MOTOR BIKE
Because both load balancing and assisted roaming are designed to influence the AP that a client associates
with, it is not possible to enable both the options at the same time on a WLAN.
• Configure Assisted Roaming Prediction List feature for a WLAN by entering this command:
config wlan assisted-roaming prediction {enable | disable} wlan-id
Note A warning message is displayed and load balancing is disabled for the WLAN if load balancing is already
enabled for the WLAN.
• Configure the minimum number of predicted APs required for the prediction list feature to be activated
by entering this command:
config assisted-roaming prediction-minimum count
Note If the number of APs in the prediction assigned to a client is less than the number that you specify, the
assisted roaming feature will not apply on this roam.
• Configure the maximum number of times a client can be denied association if the association request
that is sent to an AP does not match any AP in the prediction list by entering this command:
config assisted-roaming denial-maximum count
• Debug a client for assisted roaming by entering this command:
debug mac addr client-mac-addr
• Configure debugging of all of 802.11k events by entering this command:
debug 11k all {enable | disable}
• Configure debugging of neighbor details by entering this command:
debug 11k detail {enable | disable}
• Configure debugging of 802.11k errors by entering this command:
debug 11k errors {enable | disable}
• Verify if the neighbor requests are being received by entering this command:
debug 11k events {enable | disable}
• Configure debugging of the roaming history of clients by entering this command:
debug 11k history {enable | disable}
• Configure debugging of 802.11k optimizations by entering this command:
debug 11k optimization {enable | disable}
• Get details of the client-roaming parameters that are to be imported for offline simulation by entering
this command:
debug 11k simulation {enable | disable}
LWAPP-enabled access points can discover and join a CAPWAP controller, and conversion to a CAPWAP
controller is seamless. For example, the controller discovery process and the firmware downloading process
when using CAPWAP are the same as when using LWAPP. The one exception is for Layer 2 deployments,
which are not supported by CAPWAP.
You can deploy CAPWAP controllers and LWAPP controllers on the same network. The CAPWAP-enabled
software allows access points to join either a controller running CAPWAP or LWAPP. The only exceptions
are that the Cisco Aironet 1040, 1140, 1260, 3500, and 3600 Series Access Points, which support only
CAPWAP and join only controllers that run CAPWAP. For example, an 1130 series access point can join a
controller running either CAPWAP or LWAPP where an1140 series access point can join only a controller
that runs CAPWAP.
The following are some guidelines that you must follow for access point communication protocols:
• If your firewall is currently configured to allow traffic only from access points using LWAPP, you must
change the rules of the firewall to allow traffic from access points using CAPWAP.
• Ensure that the CAPWAP UDP ports 5246 and 5247 (similar to the LWAPP UDP ports 12222 and
12223) are enabled and are not blocked by an intermediate device that could prevent an access point
from joining the controller.
• If access control lists (ACLs) are in the control path between the controller and its access points, you
need to open new protocol ports to prevent access points from being stranded.
Note With Release 8.2, DTLSv1.2 for CAPWAP is not supported. The following are supported for web
authentication and WebAdmin based on the configuration:
• TLSv1.2
• TLSv1.0
• SSLv3
• SSLv2
Note Cisco WLC supports only static configuration of gateway. Therefore, the ICMP redirect to change IP
address of the gateway is not considered.
• If your controller does not have a data DTLS license and if the access point associated with the controller
has DTLS enabled, the data path will be unencrypted.
• Non-Russian customers using Cisco 5508 Series Controller do not need data DTLS license. However
all customers using Cisco 2500 Series Controllers, Cisco 8500 Series Controllers, WISM2, and Cisco
Virtual Wireless Controllers need a data DTLS license to turn on the Data DTLS feature.
Step 1 The upgrade operation fails on the first attempt with a warning indicating that the upgrade to a licensed DTLS image is
irreversible.
Note Do not reboot the controller after Step
1.
Step 2 On a subsequent attempt, the license is applied and the image is successfully updated.
Step 1 Choose Wireless > Access Points > All APs to open the All APs page.
Step 2 Click the name of the access point for which you want to enable data encryption.
Step 3 Choose the Advanced tab to open the All APs > Details for (Advanced) page.
Step 4 Select the Data Encryption check box to enable data encryption for this access point or unselect it to disable this feature.
The default value is unselected.
Note Changing the data encryption mode requires the access points to rejoin the controller.
Note In images without a DTLS license, the config or show commands are not available.
To enable DTLS data encryption for access points on the controller using the controller CLI, follow these
steps:
Step 1 Enable or disable data encryption for all access points or a specific access point by entering this command:
config ap link-encryption {enable | disable} {all | Cisco_AP}
The default value is disabled.
Note Changing the data encryption mode requires the access points to rejoin the controller.
Step 2 When prompted to confirm that you want to disconnect the access point(s) and attached client(s), enter Y.
Step 3 Enter the save config command to save your configuration.
Step 4 See the encryption state of all access points or a specific access point by entering this command:
show ap link-encryption {all | Cisco_AP}
This command also shows authentication errors, which tracks the number of integrity check failures, and replay errors,
which tracks the number of times that the access point receives the same packet.
Step 5 See a summary of all active DTLS connections by entering this command:
show dtls connections
Note If you experience any problems with DTLS data encryption, enter the debug dtls {all | event | trace | packet}
{enable | disable} command to debug all DTLS messages, events, traces, or packets.
Cisco AP Identifier.............................. 9
Cisco AP Name.................................... Maria-1250
Country code..................................... US - United States
Regulatory Domain allowed by Country............. 802.11bg:-A 802.11a:-A
AP Country code.................................. US - United States
AP Regulatory Domain............................. 802.11bg:-A 802.11a:-A
Switch Port Number .............................. 1
MAC Address...................................... 00:1f:ca:bd:bc:7c
IP Address Configuration......................... DHCP
IP Address....................................... 1.100.163.193
IP NetMask....................................... 255.255.255.0
CAPWAP Path MTU.................................. 1485
Debugging CAPWAP
Use these commands to obtain CAPWAP debug information:
• debug capwap events {enable | disable}—Enables or disables debugging of CAPWAP events.
• debug capwap errors {enable | disable}—Enables or disables debugging of CAPWAP errors.
• debug capwap detail {enable | disable}—Enables or disables debugging of CAPWAP details.
• debug capwap info {enable | disable}—Enables or disables debugging of CAPWAP information.
• debug capwap packet {enable | disable}—Enables or disables debugging of CAPWAP packets.
• debug capwap payload {enable | disable}—Enables or disables debugging of CAPWAP payloads.
• debug capwap hexdump {enable | disable}—Enables or disables debugging of the CAPWAP
hexadecimal dump.
• debug capwap dtls-keepalive {enable | disable}—Enables or disables debugging of CAPWAP DTLS
data keepalive packets.
receives the IPv6 discovery request from the AP only if it is in the same L2 segment and sends
back the IPv6 discovery response.
• Locally stored controller IPv4 or IPv6 address discovery—If the access point was previously
associated to a controller, the IPv4 or IPv6 addresses of the primary, secondary, and tertiary
controllers are stored in the access point’s nonvolatile memory. This process of storing controller
IPv4 or IPv6 addresses on an access point for later deployment is called priming the access point.
• DHCP server discovery using option 43—This feature uses DHCP option 43 to provide controller
IPv4 addresses to the access points. Cisco switches support a DHCP server option that is typically
used for this capability. For more information about DHCP option 43, see the Using DHCP Option
43 and DHCP Option 60 section.
• DHCP server discovery using option 52 —This feature uses DHCP option 52 to allow the AP to
discover the IPv6 address of the controller to which it connects. As part of the DHCPv6 messages,
the DHCP server provides the controllers management with an IPv6 address.
• DNS discovery—The access point can discover controllers through your domain name server
(DNS). You must configure your DNS to return controller IPv4 and IPv6 addresses in response to
CISCO-LWAPP-CONTROLLER.localdomain or CISCO-CAPWAP-CONTROLLER.localdomain,
where localdomain is the access point domain name.
When an access point receives an IPv4/IPv6 address and DNSv4/DNSv6 information from a
DHCPv4/DHCPv6 server, it contacts the DNS to resolve
CISCO-LWAPP-CONTROLLER.localdomain or CISCO-CAPWAP-CONTROLLER.localdomain.
When the DNS sends a list of controller IP addresses, which may include either IPv4 addresses or
IPv6 addresses or both the addresses, the access point sends discovery requests to the controllers.
Step 1 Configure the new controller as a master controller by entering this command:
config network master-base enable
Step 2 (Optional) Flush the ARP and MAC address tables within the network infrastructure.
Step 3 Restart the access points.
Step 4 Configure the controller not to be a master controller after all the access points have joined the new controller by entering
this command:
config network master-base disable
Step 1 Choose Monitor > Access Point Summary> All APs > Details to open the All APs page.
This page lists all of the access points joined to the controller. For each access point, you can see its name, MAC address,
uptime, status, operating mode, certificates, OfficeExtend access point status, and access point submode.
The total number of access points appears in the upper right-hand corner of the page. If the list of access points spans
multiple pages, you can access these pages by clicking the page number links. Each page shows up to 20 access points.
• Operating Status—Select one or more of the following check boxes to specify the operating status of the access
points:
◦UP—The access point is up and running.
Note When the APs are in downloading state, during which time the APs are nonfunctional due to no
configuration on the APs, the WLC GUI shows these AP radios in UP state on the Monitor page.
◦DOWN—The access point is not operational.
◦REG—The access point is registered to the controller.
◦DEREG—The access point is not registered to the controller.
◦DOWNLOAD—The controller is downloading its software image to the access point.
• Port Number—Enter the controller port number to which the access point is connected.
• Admin Status—Choose Enabled or Disabled to specify whether the access points are enabled or disabled on the
controller.
• AP Mode—Select one or more of the following options to specify the operating mode of the access points:
◦Local—The default option.
Note The 600 OEAP series access point uses only local mode.
When an access point in local mode connects to a Cisco Flex 7500 Series Controller, it does not
serve clients. The access point details are available in the controller. To enable an access point to
serve clients or perform monitoring-related tasks when connected to the Cisco Flex 7500 Series
Controller, the access point mode must be in FlexConnect or monitor mode. Use the following
command to automatically convert access points to a FlexConnect mode or monitor mode on joining
the controller:
config ap autoconvert {flexconnect | monitor | disable}
All access points that connect to the controller will either be converted to FlexConnect mode or
monitor mode depending on the configuration provided.
◦FlexConnect—This mode is used for 1040, 1130, 1140, 1240, 1250, 1260, 1600, 2600, 3500, 3600, and 800
access points.
◦REAP—This mode is the remote edge lightweight access point.
◦Monitor—This mode is the monitor-only mode.
◦Rogue Detector—This mode monitors the rogue APs on wire. It does not transmit or receive frames over
the air or contain rogue APs.
Note Information about rogues that are detected is not shared between controllers. Therefore, we recommend
that every controller has its own connected rogue detector AP when rogue detector APs are used.
◦Sniffer—The access point starts sniffing the air on a given channel. It captures and forwards all the packets
from the clients on that channel to a remote machine that runs Airopeek or Wireshark (packet analyzers for
IEEE 802.11 wireless LANs). It includes information on the time stamp, signal strength, packet size, and so
on.
Note The Bridge option is displayed only if the AP is bridge
capable.
Note If the AP mode is set to “Bridge” and the AP is not REAP capable, an error appears.
Note In the access point sniffer, the server to which the data is to be sent should be on the same VLAN
as the wireless controller management VLAN otherwise an error will be displayed.
◦Bridge—This mode sets the AP mode to “Bridge” if you are connecting a Root AP.
◦SE-Connect—This mode allows you to connect to spectrum expert and it allows the access point to perform
spectrum intelligence.
Note Spectrum intelligence is supported on , 2600 and 3600 series access points. 1260 series access points
does not support the spectrum intelligence.
Note When an access point is configured in SE-Connect mode, the access point reboots and rejoins the
controller. Access points that are configured in this mode do not serve the client.
◦Flex+Bridge— The standalone mode support is applicable when the AP is in this mode.
• Certificate Type—Select one or more of the following check boxes to specify the types of certificates installed
on the access points:
◦MIC—Manufactured-installed certificate
◦SSC—Self-signed certificate
◦LSC—Local significant certificate
Note See the Authorizing Access Points section for more information about these certificate
types.
• Primary S/W Version—Select this check box to enter the primary software version number
• Backup S/W Version—Select this check box to enter the secondary software version number.
Step 1 Choose Monitor > Summary > All APs. The All APs > Details page appears.
Step 2 Click the Interfaces tab.
Step 3 Click on the available Interface name. The Interface Details page appears.
Step 4 The Interface Details page displays the following parameter details.
Button Description
AP Name Name of the access point.
RX Bytes Total number of bytes in the error-free packets received on the interface.
RX Non-Unicast Packets Total number of nonunicast or multicast packets received on the interface.
Input CRC Total number of CRC error in packets while receiving on the interface.
Input Errors Sum of all errors in the packets while receiving on the interface.
Button Description
Input Overrun Number of times the receiver hardware was incapable of handling received data to a hardware
buffer because the input rate exceeded the receiver’s capability to handle that data.
Input Resource Total number of resource errors in packets received on the interface.
Runts Number of packets that are discarded because they are similar to the medium’s minimum
packet size.
Throttle Total number of times the interface advised a sending NIC that it was overwhelmed by
packets being sent and to slow the pace of delivery.
Output Errors Errors that prevented the final transmission of packets out of the interface.
Operational Status Operational state of the physical ethernet interface on the AP.
TX Non-Unicast Packets Total number of nonunicast or multicast packets transmitted on the interface.
Input Aborts Total number of packets aborted while receiving on the interface.
Input Frames Total number of packets received incorrectly that has a CRC error and a noninteger number
of octets on the interface.
Input Drops Total number of packets dropped while receiving on the interface because the queue was
full.
Unknown Protocol Total number of packets discarded on the interface due to an unknown protocol.
Giants Number of packets that are discarded because they exceeded the medium’s maximum packet
size.
Interface Resets Number of times that an interface has been completely reset.
Output No Buffer Total number of packets discarded because there was no buffer space.
Output Underrun Number of times the transmitter has been running faster than the router can handle.
Button Description
Output Total Drops Total number of packets dropped while transmitting from the interface because the queue
was full.
Note When you enable the MAC address filter, the other filters are disabled automatically. When you enable
any of the other filters, the MAC address filter is disabled automatically.
• CleanAir Status—Select one or more of the following check boxes to specify the operating status of the access
points:
◦UP—The spectrum sensor for the access point radio is currently operational.
◦DOWN—The spectrum sensor for the access point radio is currently not operational because an error has
occurred. The most likely reason for the error is that the access point radio is disabled.
◦ERROR—The spectrum sensor for the access point radio has crashed, making CleanAir monitoring
nonoperational for this radio. We recommend rebooting the access point or disabling CleanAir functionality
on the radio.
◦N/A—The access point radio is not capable of supporting CleanAir functionality. Currently, only Cisco
Aironet 3500 series access point radios can be configured for Cisco CleanAir.
Step 4 Click Find to commit your changes. Only the access point radios that match your search criteria appear on the 802.11a/n/ac
Radios page or the 802.11b/g/n Radios page, and the Current Filter parameter at the top of the page specifies the filter
used to generate the list (for example, MAC Address:00:1e:f7:75:0a:a0 or AP Name:pmsk-ap).
Note If you want to remove the filter and display the entire access point radio list, click Clear
Filter.
except its static IP address, choose Wireless > Access Points > All APs, click the AP name and click
Clear Config Except Static IP, or enter the clear ap config ap-name keep-ip-config command on the
controller CLI. After the access point rejoins a controller, it adopts the default Cisco/Cisco username
and password.
Note Suppose you configure an indoor Cisco AP to go into the mesh mode. If you want to
reset the Cisco AP to the local mode, use the test mesh mode local command.
• To reset the AP hardware, choose Wireless > Access Points > All APs, click the AP name and click
Reset AP Now.
Step 1 Choose Wireless > Access Points > Global Configuration to open the Global Configuration page.
Step 2 In the Username text box, enter the username that is to be inherited by all access points that join the controller.
Step 3 In the Password text box, enter the password that is to be inherited by all access points that join the controller.
You can set a global username, password, and enable password that all access points inherit as they join the controller
including access points that are currently joined to the controller and any that join in the future. You can override the
global credentials and assign a unique username, password, and enable password for a specific access point. The following
are requirements enforced on the password:
• The password should contain characters from at least three of the following classes: lowercase letters, uppercase
letters, digits, and special characters.
• No character in the password can be repeated more than three times consecutively.
• The password should not contain the management username or the reverse of the username.
• The password should not contain words like Cisco, oscic, admin, nimda or any variant obtained by changing the
capitalization of letters by substituting 1, |, or ! or substituting 0 for o or substituting $ for s.
Step 4 In the Enable Password text box, enter the enable password that is to be inherited by all access points that join the
controller.
Step 5 Click Apply to send the global username, password, and enable password to all access points that are currently joined
to the controller or that join the controller in the future.
Step 6 Click Save Configuration to save your changes.
Step 7 (Optional) Override the global credentials for a specific access point and assign a unique username, password, and enable
password to this access point as follows:
a) Choose Access Points > All APs to open the All APs page.
b) Click the name of the access point for which you want to override the global credentials.
c) Choose the Credentials tab. The All APs > Details for (Credentials) page appears.
d) Select the Over-ride Global Credentials check box to prevent this access point from inheriting the global username,
password, and enable password from the controller. The default value is unselected.
e) In the Username, Password, and Enable Password text boxes, enter the unique username, password, and enable
password that you want to assign to this access point.
Note The information that you enter is retained across controller and access point reboots and if the access point
joins a new controller.
f) Click Apply to commit your changes.
g) Click Save Configuration to save your changes.
Note If you want to force this access point to use the controller’s global credentials, unselect the Over-ride Global
Credentials check box.
Step 1 Configure the global username, password, and enable password for all access points currently joined to the controller as
well as any access points that join the controller in the future by entering this command:
config ap mgmtuser add username user password password enablesecret enable_password all
Step 2 (Optional) Override the global credentials for a specific access point and assign a unique username, password, and enable
password to this access point by entering this command:
config ap mgmtuser add username user password password enablesecret enable_password Cisco_AP
The credentials that you enter in this command are retained across controller and access point reboots and if the access
point joins a new controller.
Note If you want to force this access point to use the controller’s global credentials, enter the config ap mgmtuser
delete Cisco_AP command. The following message appears after you execute this command: “AP reverted to
global username configuration.”
Step 5 See the global credentials configuration for a specific access point by entering this command:
show ap config general Cisco_AP
Note The name of the access point is case
sensitive.
Note If this access point is configured for global credentials, the AP User Mode text boxes shows “Automatic.” If the
global credentials have been overwritten for this access point, the AP User Mode text box shows “Customized.”
Note This command is available only for access points that are running the 5.1, 5.2, 6.0, or 7.0 recovery
image.
Connect the access point to the switch port.
Step 2 Install the 5.1, 5.2, 6.0, or 7.0 image on the controller and reboot the controller.
Step 3 Allow all access points to join the controller.
Step 4 Configure authentication on the controller. See the Configuring Authentication for Access Points (GUI) section or the
Configuring Authentication for Access Points (CLI) section for information about configuring authentication on the
controller.
Step 5 Configure the switch to allow authentication. See the Configuring the Switch for Authentication section for information
about configuring the switch for authentication.
Step 1 Choose Wireless > Access Points > Global Configuration to open the Global Configuration page.
Step 2 Under 802.1x Supplicant Credentials, select the 802.1x Authentication check box.
Step 3 In the Username text box, enter the username that is to be inherited by all access points that join the controller.
Step 4 In the Password and Confirm Password text boxes, enter the password that is to be inherited by all access points that
join the controller.
Note You must enter a strong password in these text boxes. Strong passwords have the following characteristics:
• They are at least eight characters long
• They contain a combination of uppercase and lowercase letters, numbers, and symbols
• They are not a word in any language
Step 5 Click Apply to send the global authentication username and password to all access points that are currently joined to
the controller and to any that join the controller in the future.
Step 6 Click Save Configuration to save your changes.
Step 7 If desired, you can choose to override the global authentication settings and assign a unique username and password to
a specific access point as follows:
a) Choose Access Points > All APs to open the All APs page.
b) Click the name of the access point for which you want to override the authentication settings.
c) Click the Credentials tab to open the All APs > Details for (Credentials) page.
d) Under 802.1x Supplicant Credentials, select the Over-ride Global Credentials check box to prevent this access
point from inheriting the global authentication username and password from the controller. The default value is
unselected.
e) In the Username, Password, and Confirm Password text boxes, enter the unique username and password that you
want to assign to this access point.
Note The information that you enter is retained across controller and access point reboots and whenever the access
point joins a new controller.
f) Click Apply to commit your changes.
g) Click Save Configuration to save your changes.
Note If you want to force this access point to use the controller’s global authentication settings, unselect the
Over-ride Global Credentials check box.
Step 1 Configure the global authentication username and password for all access points currently joined to the controller as
well as any access points that join the controller in the future by entering this command:
config ap 802.1Xuser add username ap-username password ap-password all
Note You must enter a strong password for the ap-password parameter. Strong passwords have the following
characteristics:
• They are at least eight characters long.
• They contain a combination of uppercase and lowercase letters, numbers, and symbols.
• They are not a word in any language.
Step 2 (Optional) Override the global authentication settings and assign a unique username and password to a specific access
point. To do so, enter this command:
config ap 802.1Xuser add username ap-username password ap-password Cisco_AP
Note You must enter a strong password for the ap-password parameter. See the note in Step 1 for the characteristics
of strong passwords.
The authentication settings that you enter in this command are retained across controller and access point reboots and
whenever the access point joins a new controller.
Note If you want to force this access point to use the controller’s global authentication settings, enter the config ap
802.1Xuser delete Cisco_AP command. The following message appears after you execute this command: “AP
reverted to global username configuration.”
Step 3 Enter the save config command to save your changes.
Step 4 (Optional) Disable 802.1X authentication for all access points or for a specific access point by entering this command:
config ap 802.1Xuser disable {all | Cisco_AP}
Note You can disable 802.1X authentication for a specific access point only if global 802.1X authentication is not
enabled. If global 802.1X authentication is enabled, you can disable 802.1X for all access points only.
Step 5 See the authentication settings for all access points that join the controller by entering this command:
show ap summary
Information similar to the following appears:
Number of APs.................................... 1
Global AP User Name.............................. globalap
Global AP Dot1x User Name........................ globalDot1x
Step 6 See the authentication settings for a specific access point by entering this command:
show ap config general Cisco_AP
Note The name of the access point is case
sensitive.
Note If this access point is configured for global authentication, the AP Dot1x User Mode text boxes shows “Automatic.”
If the global authentication settings have been overwritten for this access point, the AP Dot1x User Mode text
box shows “Customized.”
Note In Release 7.4, all AP modes except bridging (required for mesh) are supported for both
AP801 and AP802. In Release 7.5 and later, all AP modes are supported on AP802;
however, bridging is not supported on AP801.
• When you want to use the AP801 or AP802 with a controller, you must enable the recovery image for
the unified mode on the access point by entering the service-module wlan-ap 0 bootimage unified
command on the router in privileged EXEC mode.
• If the service-module wlan-ap 0 bootimage unified command does not work, make sure that the
software license is still eligible.
• After enabling the recovery image, enter the service-module wlan-ap 0 reload command on the router
to shut down and reboot the access point. After the access point reboots, it discovers the controller,
downloads the full CAPWAP or LWAPP software release from the controller, and acts as a lightweight
access point.
Note To use the CLI commands mentioned above, the router must be running Cisco IOS
Release 12.4(20)T or later releases.
• To support CAPWAP or LWAPP, the router must be activated with at least the Cisco Advanced IP
Services IOS license-grade image. A license is required to upgrade to this Cisco IOS image on the router.
For licensing information, see
http://www.cisco.com/c/en/us/td/docs/routers/access/sw_activation/SA_on_ISR.html.
• After the AP801 or AP802 boots up with the recovery image for the unified mode, it requires an IP
address to communicate with the controller and to download its unified image and configuration from
the controller. The router can provide DHCP server functionality, the DHCP pool to reach the controller,
and setup option 43 for the controller IP address in the DHCP pool configuration. Use the following
configuration to perform this task:
ip dhcp pool pool_name
network ip_address subnet_mask
dns-server ip_address
default-router ip_address
option 43 hex controller_ip_address_in_hex
Example:
• The AP801 and AP802 802.11n radio supports lower power levels than the 802.11n radio in the Cisco
Aironet 1250 series access points. The AP801 and AP802 access points store the radio power levels and
passes them to the controller when the access point joins the controller. The controller uses the supplied
values to limit the user’s configuration.
• The AP801 and AP802 access points can be used in FlexConnect mode.
For more information about the AP801, see the documentation for the Cisco 800 Series ISRs at
http://www.cisco.com/c/en/us/support/routers/800-series-routers/tsd-products-support-series-home.html.
For more information about the AP802, see the documentation for the Next generation Cisco 880 Series ISRs
at
http://www.cisco.com/c/dam/en/us/td/docs/routers/access/800/860-880-890/software/configuration/guide/SCG_880_series.pdf.
See the Upgrading Autonomous Cisco Aironet Access Points to Lightweight Mode document for instructions
to upgrade an autonomous access point to lightweight mode:
http://www.cisco.com/c/en/us/td/docs/wireless/controller/8-0/configuration-guide/b_cg80/b_cg80_chapter_01101010.html
The following are some guidelines for converting autonomous APs to lightweight mode APs:
• All Cisco lightweight access points support 16 BSSIDs per radio and a total of 16 wireless LANs per
access point. When a converted access point associates with a controller, wireless LANs with IDs 1
through 16 are pushed to the access point if the AP is part of the default AP group on the controller.
You can use other AP group configurations to push other wireless LANs to the new AP.
When a 802.11ac module (the RM3000AC) is added to a 3600 AP, you can have only 8 wireless LANs
on the 802.11a/n/ac radio.
• Access points converted to lightweight mode must get an IP address and discover the controller using
DHCP, DNS, or IP subnet broadcast.
4 Once the parameters are configured, you can start the download process on the AP. Use the archive
download-sw command, with the /force-reload argument to have the AP reboot at the end of the cycle,
and /overwrite to replace the autonomous code with the CAPWAP code. See the following example:
ap#archive download-sw /force-reload /overwrite
ftp://10.100.1.31/ap3g2-rcvk9w8-tar.152-4.JB6.tar
examining image...
Loading ap3g2-rcvk9w8-tar.152-4.JB6.tar
extracting info (273 bytes)!
Image info:
Version Suffix: rcvk9w8-
Image Name: ap3g2-rcvk9w8-mx
Version Directory: ap3g2-rcvk9w8-mx
Ios Image Size: 2335232
Total Image Size: 2335232
Image Feature: WIRELESS LAN|CAPWAP|RECOVERY
Image Family: ap3g2
Wireless Switch Management Version: 3.0.51.0
Extracting files...
ap3g2-rcvk9w8-mx/ (directory) 0 (bytes)
extracting ap3g2-rcvk9w8-mx/ap3g2-rcvk9w8-mx (2327653 bytes)!!!!!!!!!
extracting ap3g2-rcvk9w8-mx/info (273 bytes)
The AP reboots into lightweight mode and looks for a controller.
Step 1 Log on to the CLI on the controller to which the access point is associated.
Step 2 Revert from lightweight mode, by entering this command:
config ap tftp-downgrade tftp-server-ip-address filename access-point-name
Step 3 Wait until the access point reboots and reconfigure the access point using the CLI or GUI.
Reverting to a Previous Release Using the MODE Button and a TFTP Server
Step 1 Configure the PC on which your TFTP server software runs with a static IP address in the range of 10.0.0.2 to 10.0.0.30.
Step 2 Make sure that the PC contains the access point image file (such as ap3g2-k9w7-tar.152-4.JB4.tar for a 2700 or 3700
series access point) in the TFTP server folder and that the TFTP server is activated.
Step 3 Rename the access point image file in the TFTP server folder to ap3g2-k9w7-tar.default for a 2700 or a 3700 series
access point.
Step 4 Connect the PC to the access point using a Category 5 (CAT5) Ethernet cable.
Step 5 Disconnect power from the access point.
Step 6 Press and hold the MODE button while you reconnect power to the access point.
Note The MODE button on the access point must be enabled. Follow the steps in the Disabling the Reset Button on
Access Points Converted to Lightweight Mode to select the status of the access point MODE button.
Step 7 Hold the MODE button until the status LED turns red (approximately 20 to 30 seconds), and release the MODE button.
Step 8 Wait until the access point reboots as indicated by all LEDs turning green followed by the Status LED blinking green.
Step 9 After the access point reboots, reconfigure the access point using the GUI or the CLI.
stored in its flash. If a match is found, the AP associates with the controller. If a match is not found, the
validation fails and the AP disconnects from the controller and restarts the discovery process. By default, hash
validation is enabled. An AP must have the virtual controller hash key in its flash before associating with the
virtual controller. If you disable hash validation of the SSC, the AP bypasses the hash validation and directly
moves to the Run state. APs can associate with a physical controller, download the hash keys and then associate
with a virtual controller. If the AP is associated with a physical controller and hash validation is disabled, the
AP associates with any virtual controller without hash validation. The hash key of the virtual controller can
be configured for a mobility group member. This hash key gets pushed to the APs, so that the APs can validate
the hash key of the controller.
Step 1 Choose Security > Certificate > SSC to open the Self Significant Certificates (SSC) page.
The SSC device certification details are displayed.
Step 2 Select the Enable SSC Hash Validation check box to enable the validation of the hash key.
Step 3 Click Apply to commit your changes.
Note The lack of a strong password by the use of the access point’s MAC address should not be an issue because
the controller uses MIC to authenticate the access point prior to authorizing the access point through the
RADIUS server. Using MIC provides strong authentication.
Note If you use the MAC address as the username and password for access point authentication on a RADIUS
AAA server, do not use the same AAA server for client authentication.
Note When the CA server is in manual mode and if there is an AP entry in the LSC SCEP table that is pending
enrollment, the controller waits for the CA server to send a pending response. If there is no response from
the CA server, the controller retries a total of three times to get a response, after which the fallback mode
comes into effect where the AP provisioning times out and the AP reboots and comes up with MIC.
Note LSC on controller does not take password challenge. Therefore, for LSC to work, you must disable
password challenge on the CA server.
Step 1 Choose Security > Certificate > LSC to open the Local Significant Certificates (LSC) - General page.
Step 2 Select the Enable LSC on Controller check box to enable the LSC on the system.
Step 3 In the CA Server URL text box, enter the URL to the CA server. You can enter either a domain name or an IP address.
Step 4 In the Params text boxes, enter the parameters for the device certificate. The key size is a value from 384 to 2048 (in
bits), and the default value is 2048.
Step 5 Click Apply to commit your changes.
Step 6 To add the CA certificate into the controller’s CA certificate database, hover your cursor over the blue drop-down arrow
for the certificate type and choose Add.
Step 7 Choose the AP Provisioning tab to open the Local Significant Certificates (LSC) - AP Provisioning page.
Step 8 Select the Enable check box and click Update to provision the LSC on the access point.
Step 9 When a message appears indicating that the access points will be rebooted, click OK.
Step 10 In the Number of Attempts to LSC text box, enter the number of times that the access point attempts to join the controller
using an LSC before the access point reverts to the default certificate (MIC or SSC). The range is 0 to 255 (inclusive),
and the default value is 3.
Note If you set the number of retries to a nonzero value and the access point fails to join the controller using an LSC
after the configured number of retries, the access point reverts to the default certificate. If you set the number
of retries to 0 and the access point fails to join the controller using an LSC, the access point does not attempt
to join the controller using the default certificate.
Note If you are configuring LSC for the first time, we recommend that you configure a nonzero
value.
Step 11 Enter the access point MAC address in the AP Ethernet MAC Addresses text box and click Add to add access points to
the provision list.
Note To remove an access point from the provision list, hover your cursor over the blue drop-down arrow for the
access point and choose Remove.
Note If you configure an access point provision list, only the access points in the provision list are provisioned when
you enable AP provisioning. If you do not configure an access point provision list, all access points with a MIC
or SSC certificate that join the controller are LSC provisioned.
Step 4 Configure the parameters for the device certificate by entering this command:
config certificate lsc subject-params country state city orgn dept e-mail
Note The common name (CN) is generated automatically on the access point using the current MIC/SSC format
Cxxxx-MacAddr, where xxxx is the product number.
Step 5 Configure a key size by entering this command:
config certificate lsc other-params keysize
The keysize is a value from 384 to 2048 (in bits), and the default value is 2048.
Step 6 Add access points to the provision list by entering this command:
config certificate lsc ap-provision auth-list add AP_mac_addr
Note To remove access points from the provision list, enter the config certificate lsc ap-provision auth-list delete
AP_mac_addr command.
Note If you configure an access point provision list, only the access points in the provision list are provisioned when
you enable AP provisioning (in Step 8). If you do not configure an access point provision list, all access points
with a MIC or SSC certificate that join the controller are LSC provisioned.
Step 7 Configure the number of times that the access point attempts to join the controller using an LSC before the access point
reverts to the default certificate (MIC or SSC) by entering this command:
config certificate lsc ap-provision revert-cert retries
where retries is a value from 0 to 255, and the default value is 3.
Note If you set the number of retries to a nonzero value and the access point fails to join the controller using an LSC
after the configured number of retries, the access point reverts to the default certificate. If you set the number
of retries to 0 and the access point fails to join the controller using an LSC, the access point does not attempt
to join the controller using the default certificate.
Note If you are configuring LSC for the first time, Cisco recommends that you configure a nonzero
value.
Step 8 Provision the LSC on the access point by entering this command:
config certificate lsc ap-provision {enable | disable}
LSC Params:
Country.......................................... 4
State............................................ ca
City............................................. ss
Orgn............................................. org
Dept............................................. dep
Email............................................ [email protected]
KeySize.......................................... 390
LSC Certs:
CA Cert.......................................... Not Configured
RA Cert....................................... Not Configured
Step 10 See details about the access points that are provisioned using LSC by entering this command:
show certificate lsc ap-provision
Information similar to the following appears:
1 00:18:74:c7:c0:90
Step 1 Choose Security > AAA > AP Policies to open the AP Policies page.
Step 2 If you want the access point to accept self-signed certificates (SSCs), manufactured-installed certificates (MICs), or local
significant certificates (LSCs), select the appropriate check box.
Step 3 If you want the access points to be authorized using a AAA RADIUS server, select the Authorize MIC APs against
auth-list or AAA check box.
Step 4 If you want the access points to be authorized using an LSC, select the Authorize LSC APs against auth-list check
box.
Enter the Ethernet MAC address for all APs except when in bridge mode (where you need to enter the radio Mac address).
Note To delete an access point from the authorization list, enter this command: config auth-list delete ap_mac.
Information About VLAN Tagging for CAPWAP Frames from Access Points
You can configure VLAN tagging on the Ethernet interface either directly on the AP console or through the
controller. The configuration is saved in the flash memory and all CAPWAP frames use the VLAN tag as
configured, along with all the locally switched traffic, which is not mapped to a VLAN.
This feature is not supported on mesh access points that are in bridge mode.
Configuring VLAN Tagging for CAPWAP Frames from Access Points (GUI)
Step 1 Choose Wireless > Access Points > All APs to open the All APs page.
Step 2 Click the AP name from the list of AP names to open the Details page for the AP.
Step 3 Click the Advanced tab.
Step 4 In the VLAN Tagging area, select the VLAN Tagging check box.
Step 5 In the Trunk VLAN ID text box, enter an ID.
If the access point is unable to route traffic through the specified trunk VLAN after about 10 minutes, the access point
performs a recovery procedure by rebooting and sending CAPWAP frames in untagged mode to try and reassociate with
the controller. The controller sends a trap to a trap server such as the Cisco Prime Infrastructure, which indicates the
failure of the trunk VLAN.
If the access point is unable to route traffic through the specified trunk VLAN, it untags the packets and reassociates
with the controller. The controller sends a trap to a trap server such as the Cisco Prime Infrastructure, which indicates
the failure of the trunk VLAN.
If the trunk VLAN ID is 0, the access point untags the CAPWAP frames.
The VLAN Tag status is displayed showing whether the AP tags or untags the CAPWAP frames.
What to Do Next
After the configuration, the switch or other equipment connected to the Ethernet interface of the AP must also
be configured to support tagged Ethernet frames.
Configuring VLAN Tagging for CAPWAP Frames from Access Points (CLI)
Step 1 Configure VLAN tagging for CAPWAP frames from access points by entering this command:
config ap ethernet tag {disable | id vlan-id} {ap-name | all}
Step 2 You can see VLAN tagging information for an AP or all APs by entering this command:
show ap ethernet tag {summary | ap-name}
See the product documentation for your DHCP server for instructions on configuring DHCP option 43. The
Upgrading Autonomous Cisco Aironet Access Points to Lightweight Mode document contains example steps
for configuring option 43 on a DHCP server.
If the access point is ordered with the Service Provider Option - AIR-OPT60-DHCP selected, the VCI string
for that access point will be different than those listed above. The VCI string will have the “ServiceProvider”.
For example, a 1260 with this option will return this VCI string: "Cisco AP c1260-ServiceProvider".
Note The controller IP address that you obtain from the DHCP server should be a unicast IP address. Do not
configure the controller IP address as a multicast address when configuring DHCP Option 43.
If any of these conditions are met and the access point has not yet joined a controller, you can also configure
a DHCP server to return a syslog server IP address to the access point using option 7 on the server. The access
point then starts sending all syslog messages to this IP address.
You can also configure the syslog server IP address through the access point CLI, provided the access point
is currently not connected to the controller by entering the capwap ap log-server syslog_server_IP_address
command.
When the access point joins a controller for the first time, the controller pushes the global syslog server IP
address (the default is 255.255.255.255) to the access point. After that, the access point sends all syslog
messages to this IP address, until it is overridden by one of the following scenarios:
• The access point is still connected to the same controller, and the global syslog server IP address
configuration on the controller has been changed using the config ap syslog host global
syslog_server_IP_address command. In this case, the controller pushes the new global syslog server IP
address to the access point.
• The access point is still connected to the same controller, and a specific syslog server IP address has
been configured for the access point on the controller using the config ap syslog host specific Cisco_AP
syslog_server_IP_address command. In this case, the controller pushes the new specific syslog server
IP address to the access point.
• The access point gets disconnected from the controller, and the syslog server IP address has been
configured from the access point CLI using the lwapp ap log-server syslog_server_IP_address command.
This command works only if the access point is not connected to any controller.
• The access point gets disconnected from the controller and joins another controller. In this case, the new
controller pushes its global syslog server IP address to the access point.
Whenever a new syslog server IP address overrides the existing syslog server IP address, the old address is
erased from persistent storage, and the new address is stored in its place. The access point also starts sending
all syslog messages to the new IP address, provided the access point can reach the syslog server IP address.
You can configure the syslog server for access points using the controller GUI and view the access point join
information using the controller GUI or CLI.
Note When an AP in a Release 8.0 image tries to join Cisco WLC, Release 8.3 (having Release 8.2 as the
primary image and Release 8.2.1 as the secondary image on Flash), the AP goes into a perpetual loop.
(Note that the release numbers are used only as an example to illustrate the scenario of three different
images and does not apply to the releases mentioned.) This loop occurs due to version mismatch. After
the download, when the AP compares its image with the Cisco WLC image, there will be a version
mismatch. The AP will start the entire process again, resulting in a loop.
Note By default, the global syslog server IPv4/IPv6 address for all access points is 255.255.255.255. Make sure
that the access points can reach the subnet on which the syslog server resides before configuring the syslog
server on the controller. If the access points cannot reach this subnet, the access points are unable to send
out syslog messages.
Note Only one Syslog Server is used for both IPv4 and
IPv6.
• To configure a syslog server for a specific access point, enter this command:
config ap syslog host specific Cisco_AP syslog_server_IP_address
Note By default, the syslog server IPv4/IPv6 address for each access point is 0.0.0.0, which indicates that the
access point is not yet set. When the default value is used, the global access point syslog server IP address
is pushed to the access point.
Step 4 See the syslog server settings for a specific access point by entering this command:
show ap config general Cisco_AP
Step 1 Choose Monitor > Statistics > AP Join to open the AP Join Stats page.
This page lists all of the access points that are joined to the controller or that have tried to join. It shows the radio MAC
address, access point name, current join status, Ethernet MAC address, IP address, and last join time for each access
point.
The total number of access points appears in the upper right-hand corner of the page. If the list of access points spans
multiple pages, you can view these pages by clicking the page number links. Each page shows the join statistics for up
to 25 access points.
Note If you want to remove an access point from the list, hover your cursor over the blue drop-down arrow for that
access point and click Remove.
Note If you want to clear the statistics for all access points and start over, click Clear Stats on All
APs.
Step 2 If you want to search for specific access points in the list of access points on the AP Join Stats page, follow these steps
to create a filter to display only access points that meet certain criteria (such as MAC address or access point name).
Note This feature is especially useful if your list of access points spans multiple pages, preventing you from viewing
them all at once.
a) Click Change Filter to open the Search AP dialog box.
b) Select one of the following check boxes to specify the criteria used when displaying access points:
• MAC Address—Enter the base radio MAC address of an access point.
• AP Name—Enter the name of an access point.
Note When you enable one of these filters, the other filter is disabled
automatically.
c) Click Find to commit your changes. Only the access points that match your search criteria appear on the AP Join
Stats page, and the Current Filter parameter at the top of the page specifies the filter used to generate the list (for
example, MAC Address:00:1e:f7:75:0a:a0 or AP Name:pmsk-ap).
Note If you want to remove the filter and display the entire access point list, click Clear
Filter.
Step 3 To see detailed join statistics for a specific access point, click the radio MAC address of the access point. The AP Join
Stats Detail page appears.
This page provides information from the controller’s perspective on each phase of the join process and shows any errors
that have occurred.
Note To obtain the MAC address of the 802.11 radio interface, enter the show interfaces
Dot11Radio 0 command on the access point.
Information similar to the following appears:
• See all join-related statistics collected for a specific access point by entering this command:
show ap join stats detailed ap_mac
Information similar to the following appears:
• Clear the join statistics for all access points or for a specific access point by entering this command:
clear ap join stats {all | ap_mac}
Understanding How Converted Access Points Send Radio Core Dumps to the
Controller
When a radio module in a converted access point generates a core dump, the access point stores the core dump
file of the radio on its local flash memory at the time of the radio crash. It sends a notification message to the
controller indicating which radio generated a core dump file. The controller sends a trap that alerts you so
that you can retrieve the radio core file from the access point.
The retrieved core file is stored in the controller flash and can be uploaded through TFTP or FTP to an external
server for analysis. The core file is removed from the access point flash memory when the controller pulls it
from the access point.
Step 1 Transfer the radio core dump file from the access point to the controller by entering this command:
config ap crash-file get-radio-core-dump slot Cisco_AP
For the slot parameter, enter the slot ID of the radio that crashed.
Step 2 Verify that the file was downloaded to the controller by entering this command:
show ap crash-file
Step 1 Choose Commands > Upload File to open the Upload File from Controller page.
Step 2 From the File Type drop-down list, choose Radio Core Dump.
Step 3 From the Transfer Mode drop-down list, choose from the following options:
• TFTP
• FTP
• SFTP (available in the 7.4 and later releases)
Step 4 In the IP Address text box, enter the IP address of the server.
Step 5 In the File Path text box, enter the directory path of the file.
Step 6 In the File Name text box, enter the name of the radio core dump file.
Note The filename that you enter should match the filename generated on the controller. You can determine the
filename on the controller by entering the show ap crash-file command.
Step 7 If you chose FTP as the Transfer Mode, follow these steps:
a) In the Server Login Username text box, enter the FTP server login name.
b) In the Server Login Password text box, enter the FTP server login password.
c) In the Server Port Number text box, enter the port number of the FTP server. The default value for the server port is
21.
Step 8 Click Upload to upload the radio core dump file from the controller. A message appears indicating the status of the
upload.
Step 1 Transfer the file from the controller to a server by entering these commands:
• transfer upload mode {tftp | ftp | sftp}
• transfer upload datatype radio-core-dump
• transfer upload serverip server_ip_address
• transfer upload path server_path_to_file
• transfer upload filename filename
Note The filename that you enter should match the filename generated on the controller. You can determine the
filename on the controller by entering the show ap crash-file command.
Note Ensure that the filename and server_path_to_file do not contain these special characters: \, :, *, ?, ", <, >,
and |. You can use only / (forward slash) as the path separator. If you use the disallowed special characters
in the filename, then the special characters are replaced with _ (underscores); and if you use the disallowed
special characters in the server_path_to_file, then the path is set to the root path.
Step 2 If you are using an FTP server, also enter these commands:
• transfer upload username username
• transfer upload password password
• transfer upload port port
Note The default value for the port parameter is
21.
Step 4 When prompted to confirm the current settings and start the software upload, answer y.
Step 1 Choose Wireless > Access Points > All APs > access point name > and choose the Advanced tab to open the All APs
> Details for (Advanced) page.
Step 2 Select the AP Core Dump check box to upload a core dump of the access point.
Step 3 In the TFTP Server IP text box, enter the IP address of the TFTP server.
Step 4 In the File Name text box, enter a name of the access point core dump file (such as dump.log).
Step 5 Select the File Compression check box to compress the access point core dump file. When you enable this option, the
file is saved with a .gz extension (such as dump.log.gz). This file can be opened with WinZip.
Step 6 Click Apply to commit your changes.
Step 7 Click Save Configuration to save your changes.
Step 1 Upload a core dump of the access point by entering this command on the controller:
config ap core-dump enable tftp_server_ip_address filename {compress | uncompress} {ap_name | all}
where
• tftp_server_ip_address is the IP address of the TFTP server to which the access point sends core dump files.
Note The access point must be able to reach the TFTP
server.
• filename is the name that the access points uses to label the core file.
• compress configures the access point to send compressed core files whereas uncompress configures the access
point to send uncompressed core files.
Note When you choose compress, the file is saved with a .gz extension (for example, dump.log.gz). This file
can be opened with WinZip.
• ap_name is the name of a specific access point for which core dumps are uploaded and all is all access points
converted to lightweight mode.
Step 1 Verify that the crash file was downloaded to the controller by entering this command:
show ap crash-file
Information similar to the following appears:
Step 2 See the contents of the AP crash log file by entering this command:
show ap crash-file Cisoc_AP
Note If you configure an access point to use a static IP address that is not on the same subnet on which the
access point’s previous DHCP address was, the access point falls back to a DHCP address after the access
point reboots. If the access point falls back to a DHCP address, enter the show ap config general Cisco_AP
CLI command to show that the access point is using a fallback IP address. However, the GUI shows both
the static IP address and the DHCP address, but it does not identify the DHCP address as a fallback address.
Step 1 Choose Wireless > Access Points > All APs to open the All APs page.
Step 2 Click the name of the access point for which you want to configure a static IP address. The All APs > Details for (General)
page appears.
Step 3 Under IP Config, select the Static IP (IPv4/IPv6) check box if you want to assign a static IP address to this access point.
The default value is unselected.
Note The static IP configured on the AP will take precedence over the preferred mode configured on the AP. For
example: If AP has static IPV6 address and prefer-mode is set to IPV4, then the AP will join over IPv6.
Step 4 Enter the static IPv4/IPv6 address of the access point, subnet mask/ prefix length assigned to the access point IPv4/IPv6
address, and the IPv4/IPv6 gateway of the access point in the corresponding text boxes.
Step 5 Click Apply to commit your changes. The access point reboots and rejoins the controller, and the static IPv4/IPv6 address
that you specified in Step 4 is sent to the access point.
Step 6 After the static IPv4/IPv6 address has been sent to the access point, you can configure the DNS server IP address and
domain name as follows:
a) In the DNS IP Address text box, enter the IPv4/IPv6 address of the DNS server.
b) In the Domain Name text box, enter the name of the domain to which the access point belongs.
c) Click Apply to commit your changes.
d) Click Save Configuration to save your changes.
Step 1 Configure a static IP address on the access point by entering this command:
For IPv4—config ap static-ip enable Cisco_AP ip_address mask gateway
For IPv6—config ap static-ip enable Cisco_AP ip_address prefix_length gateway
Note To disable static IP for the access point, enter the config ap static-ip disable Cisco_AP command.
Note The static IP configured on the AP will take precedence over the preferred mode configured on the AP. For
example: If AP has static IPV6 address and prefer-mode is set to IPV4, then the AP will join over IPv6.
Step 2 Enter the save config command to save your changes.
The access point reboots and rejoins the controller, and the static IP address that you specified in Step 1 is pushed to the
access point.
Step 3 After the static IPv4/IPv6 address has been sent to the access point, you can configure the DNSv4/DNSv6 server IP
address and domain name as follows:
a) To specify a DNSv4/DNSv6 server so that a specific access point or all access points can discover the controller
using DNS resolution, enter this command:
config ap static-ip add nameserver {Cisco_AP | all} ip_address
Note To delete a DNSv4/DNSv6 server for a specific access point or all access points, enter the config ap static-ip
delete nameserver {Cisco_AP | all} command.
b) To specify the domain to which a specific access point or all access points belong, enter this command:
Cisco AP Identifier.............................. 4
Cisco AP Name................................. AP6
...
IP Address Configuration......................... Static IP assigned
IP Address....................................... 10.10.10.118
IP NetMask....................................... 255.255.255.0
Gateway IP Addr............................... 10.10.10.1
Domain........................................... Domain1
Name Server................................... 10.10.10.205
...
• For IPv6:
show ap config general Cisco_AP
Information similar to the following appears:
Cisco AP Identifier.............................. 16
Cisco AP Name.................................... AP2602I-A-K9-1
...
IPv6 Address Configuration....................... DHCPv6
IPv6 Address..................................... 2001:9:2:16:1ae:a1da:c2c7:44b
IPv6 Prefix Length............................... 128
Gateway IPv6 Addr................................ fe80::c60a:cbff:fe79:53c4
NAT External IP Address.......................... None
...
IPv6 Capwap UDP Lite............................. Enabled
Capwap Prefer Mode............................... Ipv6 (ApGroup Config)
Hotspot Venue Group.............................. Unspecified
Hotspot Venue Type............................... Unspecified
DNS server IP ............................. Not Available
power-cycling during a system upgrade. If a power-cycle occurs during an upgrade to an oversized access
point image, you can recover the access point using the TFTP recovery procedure.
Step 1 Download the required recovery image from Cisco.com (for example, ap3g2-rcvk9w8-tar.152-4.JB6.tar for 2700 or
3700 APs) and install it in the root directory of your TFTP server.
Step 2 Connect the TFTP server to the same subnet as the target access point and power-cycle the access point. The access point
boots from the TFTP image and then joins the controller to download the oversized access point image and complete
the upgrade procedure.
Step 3 After the access point has been recovered, you may remove the TFTP server.
The packets are captured and dumped in the order of arrival or transmit of packets except for beacons and
probe responses. The packet capture contains information such as channel, RSSI, data rate, SNR, and timestamp.
Each packet is appended with additional information from the AP. You can choose to dump either just packet
headers or full packets.
The following are some guidelines for packet capture:
• If FTP transfer time is slower than the packet rate, some of the packets do not appear in the capture file.
• If the buffer does not contain any packets, a known dummy packet is dumped to keep the connection
alive.
• A file is created on the FTP server for each AP based on unique AP and controller name and timestamp.
Ensure that the FTP server is reachable by the AP.
• If the FTP transfer fails or FTP connection is lost during packet capture, the AP stops capturing packets,
notifies with an error message and SNMP trap, and a new FTP connection is established.
Step 1 Configure FTP parameters for packet capture by entering this command:
config ap packet-dump ftp serverip ip-address path path username user_ID password password
Step 3 Configure the buffer size for packet capture by entering this command:
config ap packet-dump buffer-size size-in-kb
Step 4 Configure the time for packet capture by entering this command:
config ap packet-dump capture-time time-in-minutes
The valid range is between 1 to 60 minutes.
Step 6 Configure the packet length after truncation by entering this command:
config ap packet-dump truncate length-in-bytes
Note DTLS is permanently enabled on the Cisco OEAP. You cannot disable DTLS on this access point.
Note Cisco OEAPs are designed to work behind a router or other gateway device that is using network address
translation (NAT). NAT allows a device, such as a router, to act as an agent between the Internet (public)
and a personal network (private), enabling an entire group of computers to be represented by a single IP
address. There is no limit to the number of Cisco OEAPs that you can deploy behind a NAT device.
Roaming is not supported for the Cisco 600 OEAP model.
All the supported indoor AP models with integrated antenna can be configured as OEAP except the AP-700I,
AP-700W, and AP802 series access points.
Note IPv6 is not supported on Cisco 600 Series OfficeExtend Access Points.
Note The CAPWAP UDP 5246 and 5247 ports must be open on the firewall between the WLAN controller
and the 600 Series OfficeExtend Access Point.
Note Multicast is not supported on Cisco 600 Series OfficeExtend Access Points.
Note Monitor mode, flexconnect mode, sniffer mode, rogue detector, bridge, and SE-Connect are not supported
on the 600 Series OfficeExtend Access Point and are not configurable.
WLAN Security Settings for the 600 Series OfficeExtend Access Point
When configuring the security settings in the WLAN (see the following figure), note that there are specific
elements that are not supported on the 600 Series OfficeExtend Access Point. CCX is not supported on the
600 Series OfficeExtend Access Point, and elements related to CCX are not supported.
For Layer 2 Security, the following options are supported for the 600 Series OfficeExtend Access Point:
• None
• WPA+WPA2
• Static WEP
• 802.1X (only for remote LANs)
In the Security tab (see the following figure), do not select CCKM in WPA+WPA2 settings. Select only
802.1X or PSK.
Security encryption settings must be identical for WPA and WPA2 for TKIP and AES. The following are
examples of incompatible settings for TKIP and AES.
Figure 49: Incompatible WPA and WPA2 Security Encryption Settings for OEAP 600 Series
Figure 50: Incompatible WPA and WPA2 Security Encryption Settings for OEAP 600 Series
QoS settings are supported (see the following figure), but CAC is not supported and should not be enabled.
Client Load Balancing and Client Band Select are not supported.
Authentication Settings
For authentication on the 600 Series OfficeExtend Access Point, LEAP is not supported. This configuration
must be addressed on the clients and RADIUS servers to migrate them to EAP-Fast, EAP-TTLS, EAP-TLS,
or PEAP.
If Local EAP is being utilized on the controller, the settings would also have to be modified not to use LEAP.
Note This limit does not apply to other AP models that operate in the OfficeExtend mode.
Security settings can be left open, set for MAC filtering, or set for Web Authentication. The default is to use
MAC filtering. Additionally, you can specify 802.1X Layer 2 security settings.
Figure 56: Layer 2 Security Settings for OEAP 600 Series APs in Remote LANs
Figure 57: Layer 3 Security Settings for OEAP 600 Series APs in Remote LANs
The channel bandwidth for 5.0 GHz is also configured on the 600 Series OfficeExtend Access Point Local
GUI, for 20-MHz or 40-MHz wide channels. Setting the channel width to 40 MHz for 2.4 GHz is not supported
and fixed at 20 MHz.
Additional Caveats
• The Cisco 600 Series OfficeExtend Access Points (OEAPs) are designed for single AP deployments,
therefore client roaming between Cisco 600 Series OEAPs is not supported.
Disabling the 802.11a/n/ac or 802.11b/g/n on the controller may not disable these spectrums on the
Cisco 600 Series OEAP because local SSID may be still working.
• Your firewall must be configured to allow traffic from access points using CAPWAP. Make sure that
UDP ports 5246 and 5247 are enabled and are not blocked by an intermediate device that could prevent
an access point from joining the controller.
• Cisco Aironet APs other than 600 Series OEAPs that are converted to OEAP mode and mapped to locally
switched WLAN forward the DHCP request to the local subnet on the AP connected switch. To avoid
this condition, you must disable local switching and local authentication.
• For Cisco 600 Series OEAP to associate with Cisco Virtual Wireless LAN Controller, follow these steps:
1 Configure the OEAP to associate with a physical controller that is using 7.5 or a later release and
download the corresponding AP image.
2 Configure the OEAP so that the OEAP does not associate with the physical controller again; for
example, you can implement an ACL in the network to block CAPWAP between the OEAP and the
physical controller.
3 Configure the OEAP to associate with the Cisco Virtual Wireless LAN Controller.
Implementing Security
Note Configuring LSC is not a requirement but is an option. The OfficeExtend 600 access points do not support
LSC.
1 Use local significant certificates (LSCs) to authorize your OfficeExtend access points, by following the
instructions in Authorizing Access Points Using LSCs.
2 Implement AAA server validation using the access point’s MAC address, name, or both as the username
in authorization requests, by entering this command:
config auth-list ap-policy authorize-ap username {ap_mac | Cisco_AP | both}
Using the access point name for validation can ensure that only the OfficeExtend access points of valid
employees can associate with the controller. To implement this security policy, ensure that you name each
OfficeExtend access point with an employee ID or employee number. When an employee is terminated,
run a script to remove this user from the AAA server database, which prevents that employee’s OfficeExtend
access point from joining the network.
3 Save your changes by entering this command:
save config
Note CCX is not supported on the 600 OEAP. Elements related to CCX are not supported. Also, only 802.1X
or PSK is supported. TKIP and AES security encryption settings must be identical for WPA and WPA2.
c) If desired, enter the name and IP address of a secondary or tertiary controller (or both) in the corresponding Controller
Name and Management IP Address text boxes.
d) Click Apply. The access point reboots and then rejoins the controller.
Note The names and IP addresses must be unique for the primary, secondary, and tertiary controllers.
Step 6 Configure a specific username and password for the OfficeExtend access point so that the user at home can log into the
GUI of the OfficeExtend access point:
a) Click the Credentials tab.
b) Select the Over-ride Global Credentials check box to prevent this access point from inheriting the global username,
password, and enable password from the controller. The default value is unselected.
c) In the Username, Password, and Enable Password text boxes, enter the unique username, password, and enable
password that you want to assign to this access point.
Note The information that you enter is retained across controller and access point reboots and if the access point
joins a new controller.
d) Click Apply.
Note If you want to force this access point to use the controller’s global credentials, unselect the Over-ride Global
Credentials check box.
Step 7 Configure access to local GUI, LAN ports, and local SSID of the OfficeExtend access points:
a) Choose Wireless > Access Points > Global Configuration to open the Global Configuration page.
b) Under OEAP Config Parameters, select or unselect the Disable Local Access check box to enable or disable local
access of the OfficeExtend access points.
Note By default, the Disable Local Access check box is unselected and therefore the Ethernet ports and personal
SSIDs are enabled. This configuration does not affect remote LAN. The port is enabled only when you
configure a remote LAN.
Step 8 Configure split tunneling for the OfficeExtend access points as follows:
a) Choose Wireless > Access Points > Global Configuration.
b) In the OEAP Config Parameters area, select or unselect the Disable Split Tunnel check box.
Disabling split tunneling here disables split tunneling for all the WLANs and remote LANs. You can also disable
split tunneling on a specific WLAN or remote LAN.
c) Click Apply.
Step 9 Click Save Configuration.
Step 10 If your controller supports only OfficeExtend access points, see the Configuring RRM section for instructions on setting
the recommended values for the DCA interval, channel scan duration, and neighbor packet frequency.
Note You must enter both the name and IP address of the controller. Otherwise, the access point cannot join
this controller.
Note The names and IP addresses must be unique for the primary, secondary, and tertiary controllers.
• Enable the OfficeExtend mode for this access point by entering this command:
config flexconnect office-extend {enable | disable} Cisco_AP
The default value is enabled. The disable parameter disables OfficeExtend mode for this access point.
It does not undo all of the configuration settings on the access point. If you want to clear the access
point’s configuration and return it to the factory-default settings, enter this command:
Note Rogue detection is disabled automatically when you enable the OfficeExtend mode for an access point.
However, you can enable or disable rogue detection for a specific access point or for all access points
using the config rogue detection {enable | disable} {Cisco_AP | all} command. Rogue detection is
disabled by default for OfficeExtend access points because these access points, which are deployed in a
home environment, are likely to detect a large number of rogue devices.
Note DTLS data encryption is enabled automatically when you enable the OfficeExtend mode for an access
point. However, you can enable or disable DTLS data encryption for a specific access point or for all
access points using the config ap link-encryption {enable | disable} {Cisco_AP | all} command.
Note Telnet and SSH access are disabled automatically when you enable the OfficeExtend mode for an access
point. However, you can enable or disable Telnet or SSH access for a specific access point using the config
ap {telnet | ssh} {enable | disable} Cisco_AP command.
Note Link latency is enabled automatically when you enable the OfficeExtend mode for an access point.
However, you can enable or disable link latency for a specific access point or for all access points currently
associated to the controller using the config ap link-latency {enable | disable} {Cisco_AP | all} command.
• Enable the access point to choose the controller with the least latency when joining by entering this
command:
config flexconnect join min-latency {enable | disable} Cisco_AP
The default value is disabled. When you enable this feature, the access point calculates the time between
the discovery request and discovery response and joins the Cisco 5500 Series Controller that responds
first.
• Configure a specific username and password that users at home can enter to log into the GUI of the
OfficeExtend access point by entering this command:
config ap mgmtuser add username user password password enablesecret enable_password Cisco_AP
The credentials that you enter in this command are retained across controller and access point reboots
and if the access point joins a new controller.
Note If you want to force this access point to use the controller’s global credentials, enter the config ap mgmtuser
delete Cisco_AP command. The following message appears after you execute this command: “AP reverted
to global username configuration.”
• To configure access to the local network for the Cisco 600 Series OfficeExtend access points, enter the
following command:
config network oeap-600 local-network {enable | disable}
When disabled, the local SSIDs, local ports are inoperative; and the console is not accessible. When
reset, the default restores local access. This configuration does not affect the remote LAN configuration
if configured on the access points.
• Configure the Dual R-LAN Ports feature, which allows the Ethernet port 3 of Cisco 600 Series
OfficeExtend access points to operate as a remote LAN by entering this command:
config network oeap-600 dual-rlan-ports {enable | disable}
This configuration is global to the controller and is stored by the AP and the NVRAM variable. When
this variable is set, the behavior of the remote LAN is changed. This feature supports different remote
LANs per remote LAN port.
The remote LAN mapping is different depending on whether the default group or AP Groups is used:
• Default Group—If you are using the default group, a single remote LAN with an even numbered
remote LAN ID is mapped to port 4. For example, a remote LAN with remote LAN ID 2 is mapped
to port 4 (on the Cisco 600 OEAP). The remote LAN with an odd numbered remote LAN ID is
mapped to port 3 (on the Cisco 600 OEAP). For example, a remote LAN with remote LAN ID 1
is mapped to port 3 (on the Cisco 600 OEAP).
• AP Groups—If you are using an AP group, the mapping to the OEAP-600 ports is determined by
the order of the AP groups. To use an AP group, you must first delete all remote LANs and WLANs
from the AP group leaving it empty. Then, add the two remote LANs to the AP group adding the
port 3 AP remote LAN first, and the port 4 remote group second, followed by any WLANs.
Note If your controller supports only OfficeExtend access points, see the Configuring Radio Resource
Management section for instructions on setting the recommended value for the DCA interval.
Step 1 Choose WLANs and click the WLAN ID to open the WLANs > Edit page.
The WLAN that you choose can be a WLAN or a remote LAN depending on its configuration.
Note When a remote LAN or wireless client on a corporate SSID communicate among themselves, all the traffic
on the corporate SSID and remote LAN is tunneled back to the controller.
Step 1 Find the IP address of your OfficeExtend access point by doing one of the following:
• Log on to your home router and look for the IP address of your OfficeExtend access point.
• Ask your company’s IT professional for the IP address of your OfficeExtend access point.
• Use an application such as Network Magic to detect devices on your network and their IP addresses.
Step 2 With the OfficeExtend access point connected to your home router, enter the IP address of the OfficeExtend access point
in the Address text box of your Internet browser and click Go.
Note Make sure that you are not connected to your company’s network using a virtual private network (VPN)
connection.
Step 3 When prompted, enter the username and password to log into the access point.
Step 4 On the OfficeExtend Access Point Welcome page, click Enter. The OfficeExtend Access Point Home page appears.
Step 5 Choose Configuration to open the Configuration page.
Step 6 In the SSID text box, enter the personal SSID that you want to assign to this access point. This SSID is locally switched.
Note A controller with an OfficeExtend access point publishes only up to 15 WLANs to each connected access point
because it reserves one WLAN for the personal SSID.
Step 7 From the Security drop-down list, choose Open, WPA2/PSK (AES), or 104 bit WEP to set the security type to be used
by this access point.
Note If you choose WPA2/PSK (AES), make sure that the client is configured for WPA2/PSK and AES encryption.
Step 8 If you chose WPA2/PSK (AES) in Step 8, enter an 8- to 38-character WPA2 passphrase in the Secret text box. If you
chose 104 bit WEP, enter a 13-character ASCII key in the Key text box.
Step 9 Click Apply.
Note If you want to use the OfficeExtend access point for another application, you can clear this configuration and
return the access point to the factory-default settings by clicking Clear Config. You can also clear the access
point’s configuration from the controller CLI by entering the clear ap config Cisco_AP command.
These steps can be used for configuring a personal SSID on OfficeExtend access points only. See the Aironet 600 Series
OfficeExtend Access Point Configuration Guide for information on configuring a personal SSID on OEAP 600 APs.
A Cisco IOS AP as a WGB using the Cisco IOS 15.2 or later releases support Protected Extensible
Authentication Protocol (PEAP) with the controller.
Note If the lightweight access point fails, the WGB attempts to associate to another access point.
Note If your access point has two radios, you can configure only one for workgroup bridge
mode. This radio is used to connect to the lightweight access point. We recommend that
you disable the second radio.
Enable the workgroup bridge mode on the WGB as follows:
• On the WGB access point GUI, choose Workgroup Bridge for the role in radio
network on the Settings > Network Interfaces page.
• On the WGB access point CLI, enter the station-role workgroup-bridge
command.
Note See the sample WGB access point configuration in the WGB Configuration Example
section.
◦Open, WEP 40, WEP 128, CKIP, WPA+TKIP, WPA2+AES, LEAP, EAP-FAST, and EAP-TLS
authentication modes
• Wired clients connected to the WGB are not authenticated for security. Instead, the WGB is authenticated
against the access point to which it associates. Therefore, we recommend that you physically secure the
wired side of the WGB.
• Wired clients connected to a WGB inherit the WGB’s QoS and AAA override attributes.
• To enable the WGB to communicate with the lightweight access point, create a WLAN and make sure
that Aironet IE is enabled.
• If you have to apply ACL to WGB during run time, do not modify the ACL configuration for interface
in the controller during run time. If you need to modify any ACLs, then you must disable all WLANs
that are in the controller or disable both the 802.11a and 80.11b networks. Also, ensure that there are
no clients associated and mapped to that interface and then you can modify the ACL settings.
Note See the sample WGB access point configuration in the WGB Configuration Example
section.
• The following features are not supported for use with a WGB:
◦Idle timeout
◦Web authentication
Note If a WGB associates to a web-authentication WLAN, the WGB is added to the exclusion
list, and all of the WGB wired clients are deleted.
• The WGB supports a maximum of 20 wired clients. If you have more than 20 wired clients, use a bridge
or another device.
• The DirectStream feature from the controller does not work for clients behind workgroup bridges and
the stream is denied.
• With Layer 3 roaming, if you plug a wired client into the WGB network after the WGB has roamed to
another controller (for example, to a foreign controller), the wired client’s IP address displays only on
the anchor controller, not on the foreign controller.
• If a wired client does not send traffic for an extended period of time, the WGB removes the client from
its bridge table, even if traffic is continuously being sent to the wired client. As a result, the traffic flow
to the wired client fails. To avoid the traffic loss, prevent the wired client from being removed from the
bridge table by configuring the aging-out timer on the WGB to a large value using the following Cisco
IOS commands on the WGB:
configure terminal
bridge bridge-group-number aging-time seconds
exit
end
where bridge-group-number is a value between 1 and 255, and seconds is a value between 10 and
1,000,000 seconds. We recommend configuring the seconds parameter to a value greater than the wired
client’s idle period.
• When you delete a WGB record from the controller, all of the WGB wired clients’ records are also
deleted.
• These features are not supported for wired clients connected to a WGB:
◦MAC filtering
◦Link tests
◦Idle timeout
• The broadcast forwarding toward wired WGB clients works only on the native VLAN. If additional
VLANs are configured, only the native VLAN forwards broadcast traffic.
• Wired clients behind a WGB cannot connect to a DMZ/Anchor controller. To enable wired clients behind
a WGB to connect to an anchor controller in a DMZ, you must enable VLANs in the WGB using the
config wgb vlan enable command.
• The dot11 arp-cache global configuration command that you can enter on the access point that is in
WGB mode is not supported.
• WGB clients do not show enc-cipher and AKM because they are wired clients. WGB APs, however,
show correct values of enc-cipher and AKM.
Verify that the WGB is associated to an access point by entering this command on the WGB:
show dot11 association
Information similar to the following appears:
Step 2 Click the MAC address of the desired client. The Clients > Detail page appears.
The Client Type text box under Client Properties shows “WGB” if this client is a workgroup bridge, and the Number of
Wired Client(s) text box shows the number of wired clients that are connected to this WGB.
Step 3 See the details of any wired clients that are connected to a particular WGB as follows:
a) Click Back on the Clients > Detail page to return to the Clients page.
b) Hover your cursor over the blue drop-down arrow for the desired WGB and choose Show Wired Clients. The WGB
Wired Clients page appears.
Note If you want to disable or remove a particular client, hover your cursor over the blue drop-down arrow for
the desired client and choose Remove or Disable, respectively.
c) Click the MAC address of the desired client to see more details for this particular client. The Clients > Detail page
appears.
The Client Type text box under Client Properties shows “WGB Client,” and the rest of the text boxes on this page
provide additional information for this client.
Step 2 See the details of any wired clients that are connected to a particular WGB by entering this command:
show wgb detail wgb_mac_address
Note For FlexConnect APs in local switching, non-Cisco workgroup-bridge clients in bridged
mode are supported using the config flexconnect group group-name dhcp
overridden-interface enable command.
• When a WGB wired client leaves a multicast group, the downstream multicast traffic to other WGB
wired clients is interrupted briefly.
• If you have clients that use PC virtualization software such as VMware, you must enable this feature.
Note We have tested multiple third-party devices for compatibility but cannot ensure that all
non-Cisco devices work. Support for any interaction or configuration details on the
third-party device should be discussed with the device manufacturer.
• You must enable the passive client functionality for all non-Cisco workgroup bridges.
• You might need to use the following commands to configure DHCP on clients:
◦Disable DHCP proxy by using the config dhcp proxy disable command.
◦Enable DHCP boot broadcast by using the config dhcp proxy disable bootp-broadcast enable
command.
controller and not to any available secondary controller for which it is configured. For example, if an
access point is configured with primary, secondary, and tertiary controllers, it fails over to the tertiary
controller when the primary and secondary controllers become unresponsive. If the secondary controller
comes back online while the primary controller is down, the access point does not fall back to the
secondary controller and stays connected to the tertiary controller. The access point waits until the
primary controller comes back online to fall back from the tertiary controller to the primary controller.
If the tertiary controller fails and the primary controller is still down, the access point then falls back to
the available secondary controller.
Step 1 Choose Wireless > Access Points > Global Configuration to open the Global Configuration page.
Step 2 From the Local Mode AP Fast Heartbeat Timer State drop-down list, choose Enable to enable the fast heartbeat timer
for access points in local mode or choose Disable to disable this timer. The default value is Disable.
Step 3 If you chose Enable in Step 2, enter the Local Mode AP Fast Heartbeat Timeout text box to configure the fast heartbeat
timer for access points in local mode. Specifying a small heartbeat interval reduces the amount of time it takes to detect
a controller failure.
The range for the AP Fast Heartbeat Timeout value for Cisco Flex 7500 Controllers is 10–15 (inclusive) and is 1–10
(inclusive) for other controllers. The default value for the heartbeat timeout for Cisco Flex 7500 Controllers is 10. The
default value for other controllers is 1 second.
Step 4 From the FlexConnect Mode AP Fast Heartbeat Timer State drop-down list, choose Enable to enable the fast heartbeat
timer for FlexConnect access points or choose Disable to disable this timer. The default value is Disable.
Step 5 If you enable FlexConnect fast heartbeat, enter the FlexConnect Mode AP Fast Heartbeat Timeout value in the FlexConnect
Mode AP Fast Heartbeat Timeout text box. Specifying a small heartbeat interval reduces the amount of time it takes to
detect a controller failure.
The range for the FlexConnect Mode AP Fast Heartbeat Timeout value for Cisco Flex 7500 Controllers is 10–15 (inclusive)
and is 1–10 for other controllers. The default value for the heartbeat timeout for Cisco Flex 7500 Controllers is 10. The
default value for other controllers is 1 second.
Step 6 In the AP Primary Discovery Timeout text box, a value between 30 and 3600 seconds (inclusive) to configure the access
point primary discovery request timer. The default value is 120 seconds.
Step 7 If you want to specify a primary backup controller for all access points, enter the IPv4/IPv6 address of the primary backup
controller in the Back-up Primary Controller IP Address (IPv4/IPv6) text box and the name of the controller in the
Back-up Primary Controller Name text box.
Note The default value for the IP address is 0.0.0.0, which disables the primary backup controller.
Step 8 If you want to specify a secondary backup controller for all access points, enter the IPv4/IPv6 address of the secondary
backup controller in the Back-up Secondary Controller IP Address (IPv4/IPv6) text box and the name of the controller
in the Back-up Secondary Controller Name text box.
Note The default value for the IP address is 0.0.0.0, which disables the secondary backup controller.
Step 1 Configure a primary controller for a specific access point by entering this command:
config ap primary-base controller_name Cisco_AP [controller_ip_address]
Note The controller_ip_address parameter in this command and the next two commands is optional. If the backup
controller is outside the mobility group to which the access point is connected (the primary controller), then
you need to provide the IP address of the primary, secondary, or tertiary controller, respectively. In each
command, the controller_name and controller_ip_address must belong to the same primary, secondary, or
tertiary controller. Otherwise, the access point cannot join the backup controller.
Step 2 Configure a secondary controller for a specific access point by entering this command:
config ap secondary-base controller_name Cisco_AP [controller_ip_address]
Step 3 Configure a tertiary controller for a specific access point by entering this command:
config ap tertiary-base controller_name Cisco_AP [controller_ip_address]
Step 4 Configure a primary backup controller for all access points by entering this command:
config advanced backup-controller primary system name ip_addr
Note This command is valid for both IPv4 and
IPv6
Step 5 Configure a secondary backup controller for all access points by entering this command:
config advanced backup-controller secondary system name ip_addr
Note To delete a primary or secondary backup controller entry, enter 0.0.0.0 for the controller IPv4/IPv6 address.
Step 8 Configure the access point discovery timer by entering this command:
config advanced timers ap-discovery-timeout interval
where interval is a value between 1 and 10 seconds (inclusive). The default value is 10 seconds.
Step 9 Configure the 802.11 authentication response timer by entering this command:
config advanced timers auth-timeout interval
where interval is a value between 5 and 600 seconds (inclusive). The default value is 10 seconds.
Information similar to the following appears for the show ap config general Cisco_AP command for Primary Cisco
Switch IP Address using IPv4:
Cisco AP Identifier.............................. 1
Cisco AP Name.................................... AP5
Country code..................................... US - United States
Regulatory Domain allowed by Country............. 802.11bg:-AB 802.11a:-AB
AP Country code.................................. US - United States
AP Regulatory Domain............................. 802.11bg:-A 802.11a:-N
Switch Port Number .............................. 1
MAC Address...................................... 00:13:80:60:48:3e
IP Address Configuration......................... DHCP
IP Address....................................... 1.100.163.133
...
Primary Cisco Switch Name........................ 1-5508
Information similar to the following appears for the show ap config general Cisco_AP command for Primary Cisco
Switch IP Address using IPv6:
Cisco AP Identifier.............................. 1
Cisco AP Name.................................... AP6
Country code..................................... US - United States
Regulatory Domain allowed by Country............. 802.11bg:-A 802.11a:-A
AP Country code.................................. US - United States
AP Regulatory Domain............................. 802.11bg:-A 802.11a:-A
Switch Port Number .............................. 13
MAC Address...................................... 44:2b:03:9a:9d:30
IPv6 Address Configuration....................... DHCPv6
IPv6 Address..................................... 2001:9:5:96:295d:3b2:2db2:9b47
IPv6 Prefix Length............................... 128
Gateway IPv6 Addr................................ fe80::6abd:abff:fe8c:764a
NAT External IP Address.......................... None
CAPWAP Path MTU.................................. 1473
Telnet State..................................... Globally Disabled
Ssh State........................................ Globally Disabled
Cisco AP Location................................ _5500
Cisco AP Floor Label............................. 0
Cisco AP Group Name.............................. IPv6-Same_VLAN
Primary Cisco Switch Name........................ Maulik_WLC_5500-HA
Primary Cisco Switch IP Address.................. 2001:9:5:95::11
Information similar to the following appears for the show advanced backup-controller command when configured
using IPv4:
Information similar to the following appears for the show advanced backup-controller command when configured
using IPv6:
Information similar to the following appears for the show advanced timers command:
Step 1 Choose Wireless > Access Points > Global Configuration to open the Global Configuration page.
Step 2 From the Global AP Failover Priority drop-down list, choose Enable to enable access point failover priority or choose
Disable to disable this feature and turn off any access point priority assignments. The default value is Disable.
Step 3 Click Apply to commit your changes.
Step 4 Click Save Configuration to save your changes.
Step 5 Choose Wireless > Access Points > All APs to open the All APs page.
Step 6 Click the name of the access point for which you want to configure failover priority.
Step 7 Choose the High Availability tab. The All APs > Details for (High Availability) page appears.
Step 8 From the AP Failover Priority drop-down list, choose one of the following options to specify the priority of the access
point:
• Low—Assigns the access point to the level 1 priority, which is the lowest priority level. This is the default value.
• Medium—Assigns the access point to the level 2 priority.
• High—Assigns the access point to the level 3 priority.
• Critical—Assigns the access point to the level 4 priority, which is the highest priority level.
Step 1 Enable or disable access point failover priority by entering this command:
config network ap-priority {enable | disable}
• See the failover priority for each access point by entering this command:
show ap summary
Information similar to the following appears:
Number of APs.................................... 2
Global AP User Name.............................. user
Global AP Dot1x User Name........................ Not Configured
To see the summary of a specific access point, you can specify the access point name. You can also use
wildcard searches when filtering for access points.
Step 1 To configure the controller to set the retransmission interval and retry count globally using the controller GUI, follow
these steps:
a) Choose Wireless > Access Points > Global Configuration.
b) Choose one of the following options under the AP Transmit Config Parameters section:
• AP Retransmit Count—Enter the number of times you want the access point to retransmit the request to the
controller. This parameter can take values between 3 and 8.
• AP Retransmit Interval—Enter the time duration between the retransmission of requests. This parameter can
take values between 2 and 5.
c) Click Apply.
Step 2 To configure the controller to set the retransmission interval and retry count for a specific access point, follow these
steps:
a) Choose Wireless > Access Points > All APs.
b) Click on the AP Name link for the access point on which you want to set the values.
The All APs > Details page appears.
c) Click the Advanced Tab to open the advanced parameters page.
d) Choose one of the following parameters under the AP Transmit Config Parameters section:
• AP Retransmit Count—Enter the number of times that you want the access point to retransmit the request to
the controller. This parameter can take values between 3 and 8.
• AP Retransmit Interval—Enter the time duration between the retransmission of requests. This parameter can
take values between 2 and 5.
e) Click Apply.
Configuring the Access Point Retransmission Interval and Retry Count (CLI)
You can configure the retransmission interval and retry count for all access points globally or a specific access
point.
• Configure the retransmission interval and retry count for all access points globally by entering the this
command:
config ap retransmit {interval | count} seconds all
The valid range for the interval parameter is between 3 and 8. The valid range for the count parameter
is between 2 and 5.
• Configure the retransmission interval and retry count for a specific access point, by entering this command:
Note Because retransmit and retry values cannot be set for access points in mesh mode, these
values are displayed as N/A (not applicable).
• See the status of the configured retransmit parameters on a specific access point by entering this command:
show ap retransmit Cisco_AP
• When the multiple-country feature is being used, all controllers that are going to join the same RF group
must be configured with the same set of countries, configured in the same order.
• When multiple countries are configured and the RRM auto-RF feature is enabled, the RRM assigns the
channels that are derived by performing a union of the allowed channels per the AP country code. The
APs are assigned channels by the RRM based on their PID country code. APs are only allowed to use
legal frequencies that match their PID country code. Ensure that your AP's country code is legal in the
country that it is deployed.
• The country list configured on the RF group leader determines what channels the members would operate
on. This list is independent of what countries have been configured on the RF group members.
Note The 1550, 1600, 2600, and 3600 APs require J4.
See the Channels and Maximum Power Settings for Cisco Aironet Lightweight Access Points document for
the list of channels and power levels supported by access points in the Japanese regulatory domains.
Note If an access point was already set to a higher legal power level or is configured manually,
the power level is limited only by the particular country to which that access point is
assigned.
b) Choose Wireless > Access Points > All APs to open the All APs page.
c) Click the link for the desired access point.
d) Choose the Advanced tab to open the All APs > Details for (Advanced) page.
The default country for this access point appears in the Country Code drop-down list.
e) If the access point is installed in a country other than the one shown, choose the correct country from the drop-down
list. The box contains only those country codes that are compatible with the regulatory domain of at least one of the
access point’s radios.
f) Click Apply.
g) Repeat these steps to assign all access points joined to the controller to a specific country.
h) Reenable any access points that you disabled in Step a.
Step 7 Reenable the 802.11 networks if you did not enable them in Step 6.
Step 8 Click Save Configuration.
Step 1 See a list of all available country codes by entering this command:
show country supported
Step 3 Configure the country codes for the countries where your access points are installed by entering this command:
config country code1[,code2,code3,...]
If you are entering more than one country code, separate each by a comma (for example, config country US,CA,MX).
Step 9 If you entered multiple country codes in Step 3, follow these steps to assign each access point to a specific country:
a) Perform one of the following:
• Leave the 802.11 networks disabled.
• Reenable the 802.11 networks and then disable only the access points for which you are configuring a country
code. To Reenable the networks, enter this command:
config 802.11{a | b} enable network
To disable an access point, enter this command:
config ap disable ap_name
Step 10 If you did not reenable the 802.11 networks in Step 9, enter these commands to reenable them now:
config 802.11{a | b} enable network
Step 1 Choose Wireless > Access Points > All APs to open the All APs page.
Step 2 Click the name of the access point for which you want to configure monitor mode. The All APs > Details for page
appears.
Step 3 From the AP Mode drop-down list, choose Monitor.
Step 4 Click Apply.
Step 5 Click OK when warned that the access point will be rebooted.
Step 6 Click Save Configuration to save your changes.
Step 7 Choose Wireless > Access Points > Radios > 802.11b/g/n to open the 802.11b/g/n Radios page.
Step 8 Hover your cursor over the blue drop-down arrow for the desired access point and choose Configure. The 802.11b/g/n
Cisco APs > Configure page appears.
Step 9 Disable the access point radio by choosing Disable from the Admin Status drop-down list and click Apply.
Step 10 Enable tracking optimization on the radio by choosing Enable from the Enable Tracking Optimization drop-down list.
Step 11 From the four Channel drop-down lists, choose the channels on which you want to monitor RFID tags.
Note You must configure at least one channel on which the tags will be
monitored.
Step 12 Click Apply.
Step 13 Click Save Configuration.
Step 14 To reenable the access point radio, choose Enable from the Admin Status drop-down list and click Apply.
Step 15 Click Save Configuration.
Step 1 Configure an access point for monitor mode by entering this command:
config ap mode monitor Cisco_AP
Step 2 When warned that the access point will be rebooted and asked if you want to continue, enter Y.
Step 3 Save your changes by entering this command:
save config
Step 4 Disable the access point radio by entering this command:
config 802.11b disable Cisco_AP
Step 5 Configure the access point to scan only the DCA channels supported by its country of operation by entering this command:
config ap monitor-mode tracking-opt Cisco_AP
Note To specify the exact channels to be scanned, enter the config ap monitor-mode tracking-opt Cisco_AP
command in Step 6.
Note To disable tracking optimization for this access point, enter the config ap monitor-mode no-optimization
Cisco_AP command.
Step 6 After you have entered the command in Step 5, you can enter this command to choose up to four specific 802.11b channels
to be scanned by the access point:
config ap monitor-mode 802.11b fast-channel Cisco_AP channel1 channel2 channel3 channel4
Note In the United States, you can assign any value between 1 and 11 (inclusive) to the channel variable. Other
countries support additional channels. You must assign at least one channel.
Step 7 Reenable the access point radio by entering this command:
config 802.11b enable Cisco_AP
Step 1 Enable or disable the filtering of probe requests forwarded from an access point to the controller by entering this command:
config advanced probe filter {enable | disable}
If you enable probe filtering, the default filter setting, the access point forwards only acknowledged probe requests to
the controller. If you disable probe filtering, the access point forwards both acknowledged and unacknowledged probe
requests to the controller.
Step 2 Limit the number of probe requests sent to the controller per client per access point radio in a given interval by entering
this command:
config advanced probe limit num_probes interval
where
• num_probes is the number of probe requests (from 1 to 100) forwarded to the controller per client per access point
radio in a given interval.
• interval is the probe limit interval (from 100 to 10000 milliseconds).
The default value for num_probes is 2 probe requests, and the default value for interval is 500 milliseconds.
Step 5 See the probe request forwarding configuration by entering this command:
show advanced probe
Information similar to the following appears:
The UDI is burned into the EEPROM of controllers and lightweight access points at the factory. It can be
retrieved through either the GUI or the CLI.
Retrieving the Unique Device Identifier on Controllers and Access Points (GUI)
Step 2 Choose Wireless > Access Points > All APs to open the All APs page.
Step 3 Click the name of the desired access point.
Step 4 Choose the Inventory tab to open the All APs > Details for (Inventory) page.
This page shows the inventory information for the access point.
Retrieving the Unique Device Identifier on Controllers and Access Points (CLI)
Use these commands to retrieve the UDI on controllers and access points using the controller CLI:
• show inventory—Shows the UDI string of the controller. Information similar to the following appears:
...
...
NAME: "Chassis" , DESCR: "Cisco 5500 Series Wireless LAN Controller"
PID: AIR-CT5508-K9, VID: V01, SN: XXXXXXXXXXX
• show inventory ap ap_id—Shows the UDI string of the access point specified.
The controller software supports CCX versions 1 through 5. CCX support is enabled automatically for every
WLAN on the controller and cannot be disabled. The controller stores the CCX version of the client in its
client database and uses it to limit the features for this client. If a client does not support CCXv4 or v5, the
controller performs a ping link test on the client. If a client supports CCXv4 or v5, the controller performs a
CCX link test on the client. If a client times out during a CCX link test, the controller switches to the ping
link test automatically.
Note Follow the instructions in this section to perform a link test using either the GUI or the CLI.
Packet Count: 0 0 0 0 0 0 0 0 0 2 0 18 0
Transmit rate: 1M 2M 5.5M 6M 9M 11M 12M 18M 24M 36M 48M 54M 108M
Packet Count: 0 0 0 0 0 0 0 0 0 2 0 8 0
When CCX v4 or later releases is not enabled on either the controller or the client being tested, fewer
details appear:
• Adjust the link-test parameters that are applicable to both the CCX link test and the ping test by entering
these commands from configuration mode:
linktest frame-size size_of_link-test_frames
linktest num-of-frame number_of_link-test_request_frames_per_test
Note Link latency calculates the CAPWAP response time between the access point and the
controller. It does not measure network latency or ping responses.
• The controller displays the current round-trip time as well as a running minimum and maximum round-trip
time. The minimum and maximum times continue to run as long as the controller is up or can be cleared
and allowed to restart.
• You can configure link latency for a specific access point using the controller GUI or CLI or for all
access points joined to the controller using the CLI.
Step 1 Choose Wireless > Access Points > All APs to open the All APs page.
Step 2 Click the name of the access point for which you want to configure link latency.
Step 3 Choose the Advanced tab to open the All APs > Details for (Advanced) page.
Step 4 Select the Enable Link Latency check box to enable link latency for this access point or unselect it to prevent the access
point from sending the round-trip time to the controller after every echo response is received. The default value is
unselected.
Step 5 Click Apply to commit your changes.
Step 6 Click Save Configuration to save your changes.
Step 7 When the All APs page reappears, click the name of the access point again.
Step 8 When the All APs > Details for page reappears, choose the Advanced tab again. The link latency and data latency results
appear below the Enable Link Latency check box:
• Current—The current round-trip time (in milliseconds) of CAPWAP heartbeat packets or data packets from the
access point to the controller and back.
• Minimum—Since link latency has been enabled or reset, the minimum round-trip time (in milliseconds) of
CAPWAP heartbeat packets or data packets from the access point to the controller and back.
• Maximum—Since link latency has been enabled or reset, the maximum round-trip time (in milliseconds) of
CAPWAP heartbeat packets or data packets from the access point to the controller and back.
Step 9 To clear the current, minimum, and maximum link latency and data latency statistics on the controller for this access
point, click Reset Link Latency.
Step 10 After the page refreshes and the All APs > Details for page reappears, choose the Advanced tab. The updated statistics
appear in the Minimum and Maximum text boxes.
Step 1 Enable or disable link latency for a specific access point or for all access points currently associated to the controller by
entering this command:
config ap link-latency {enable | disable} {Cisco_AP | all}
The default value is disabled.
Note The config ap link-latency {enable | disable} all command enables or disables link latency only for access
points that are currently joined to the controller. It does not apply to access points that join in the future.
Step 2 See the link latency results for a specific access point by entering this command:
show ap config general Cisco_AP
Information similar to the following appears:
Cisco AP Identifier.............................. 1
Cisco AP Name.................................... AP1
...
AP Link Latency.................................. Enabled
Current Delay................................... 1 ms
Maximum Delay................................... 1 ms
Minimum Delay................................... 1 ms
Last updated (based on AP Up Time)........... 0 days, 05 h 03 m 25 s
The output of this command contains the following link latency results:
• Current Delay—The current round-trip time (in milliseconds) of CAPWAP heartbeat packets from the access
point to the controller and back.
• Maximum Delay—Since link latency has been enabled or reset, the maximum round-trip time (in milliseconds)
of CAPWAP heartbeat packets from the access point to the controller and back.
• Minimum Delay—Since link latency has been enabled or reset, the minimum round-trip time (in milliseconds) of
CAPWAP heartbeat packets from the access point to the controller and back.
Step 3 Clear the current, minimum, and maximum link latency statistics on the controller for a specific access point by entering
this command:
config ap link-latency reset Cisco_AP
Step 1 Choose WIRELESS > Access Points > Global Configuration to open the Global Configuration page.
Step 2 Under TCP MSS, select the Global TCP Adjust MSS check box and set the MSS for all access points that are associated
with the controller.
Note The valid range are:
• For IPv4 TCP - between 536 and
1363 bytes.
• For IPv6 TCP - between 1220 and
1331.
Any TCP MSS value that is below 1220 and above 1331 will not be effective for CAPWAP v6 AP .
Step 1 Enable or disable the TCP MSS on a particular access point or on all access points by entering this command:
config ap tcp-mss-adjust {enable|disable} {Cisco_AP | all} size
where the size parameter is a value between 536 and 1363 bytes for IPv4 and between 1220 and 1331 for IPv6. The
default value varies for different clients.
Note The valid ranges are:
• For IPv4 - Use a value between 536 and 1363 bytes.
• For IPv6 - Use a value between 1220 and 1331 bytes.
Any TCP MSS value that is below 1220 and above 1331 will not be effective for CAPWAP v6
AP.
Step 2 Save your changes by entering this command:
save config
Step 3 See the current TCP MSS setting for a particular access point or all access points by entering this command:
show ap tcp-mss-adjust {Cisco_AP | all}
Information similar to the following appears:
These modes provide the flexibility of running the 1250 series access points with the available wired
infrastructure to obtain the desired level of performance. With enhanced PoE switches (such as the Cisco
Catalyst 3750-E Series Switches), the 1250 series access points can provide maximum features and
functionality with a minimum total cost of ownership. Alternatively, if you decide to power the access
point with the existing PoE (802.3af) switches, the access point chooses the appropriate mode of operation
based on whether it has one radio or two.
Table 26: Maximum Transmit Power Settings for 1250 Series Access Points Using PoE
Radio Data Rates Number of Cyclic Shift Maximum Transmit Power (dBm)5
Band Transmitters Diversity (CSD)
802.3af ePoE Power ePoE Mode
Mode (15.4 Optimized (20 W)
W) Mode (16.8
W)
802.11g 1 — 17 17 17
5 GHz 802.11a 1 — 17 17 17
5 Maximum transmit power varies by channel and according to individual country regulations. See the product documentation for specific details.
• When powered with a non-Cisco standard PoE switch, the 1250 series access point operates under 15.4
Watts. Even if the non-Cisco switch or midspan device is capable of providing higher power, the access
point does not operate in enhanced PoE mode.
Step 1 Choose Wireless > Access Points > All APs and then the name of the desired access point.
Step 2 Choose the Advanced tab to open the All APs > Details for (Advanced) page.
The PoE Status text box shows the power level at which the access point is operating: High (20 W), Medium (16.8 W),
or Medium (15.4 W). This text box is not configurable. The controller auto-detects the access point’s power source and
displays the power level here.
Note This text box applies only to 1250 series access points that are powered using PoE. There are two other ways
to determine if the access point is operating at a lower power level. First, the “Due to low PoE, radio is transmitting
at degraded power” message appears under the Tx Power Level Assignment section on the 802.11a/n/ac (or
802.11b/g/n) Cisco APs > Configure page. Second, the “PoE Status: degraded operation” message appears in
the controller’s trap log on the Trap Logs page.
Step 3 Perform one of the following:
• Select the Pre-standard 802.3af switches check box if the access point is being powered by a high-power 802.3af
Cisco switch. This switch provides more than the traditional 6 Watts of power but do not support the intelligent
power management (IPM) feature.
• Unselect the Pre-standard 802.3af switches check box if power is being provided by a power injector. This is the
default value.
Step 4 Select the Power Injector State check box if the attached switch does not support IPM and a power injector is being
used. If the attached switch supports IPM, you do not need to select this check box.
Step 5 If you selected the Power Injector State check box in the previous step, the Power Injector Selection and Injector Switch
MAC Address parameters appear. The Power Injector Selection parameter enables you to protect your switch port from
an accidental overload if the power injector is inadvertently bypassed. Choose one of these options from the drop-down
list to specify the desired level of protection:
• Installed—This option examines and remembers the MAC address of the currently connected switch port and
assumes that a power injector is connected. Choose this option if your network contains older Cisco 6-Watt switches
and you want to avoid possible overloads by forcing a double-check of any relocated access points.
If you want to configure the switch MAC address, enter the MAC address in the Injector Switch MAC Address
text box. If you want the access point to find the switch MAC address, leave the Injector Switch MAC Address
text box blank.
Note Each time an access point is relocated, the MAC address of the new switch port fails to match the
remembered MAC address, and the access point remains in low-power mode. You must then physically
verify the existence of a power injector and reselect this option to cause the new MAC address to be
remembered.
• Override—This option allows the access point to operate in high-power mode without first verifying a matching
MAC address. You can use this option if your network does not contain any older Cisco 6-W switches that could
be overloaded if connected directly to a 12-W access point. The advantage of this option is that if you relocate the
access point, it continues to operate in high-power mode without any further configuration. The disadvantage of
this option is that if the access point is connected directly to a 6-W switch, an overload occurs.
Note Ensure CDP is enabled before entering this command. Otherwise, this command will
fail. See the Configuring the Cisco Discovery Protocol section for information about
enabling CDP.
• Remove the safety checks and allow the access point to be connected to any switch port by entering this
command:
config ap power injector enable {Cisco_AP | all} override
You can use this command if your network does not contain any older Cisco 6-W switches that could
be overloaded if connected directly to a 12-W access point. The access point assumes that a power
injector is always connected. If you relocate the access point, it continues to assume that a power injector
is present.
• If you know the MAC address of the connected switch port and do not want to automatically detect it
using the installed option, enter this command:
config ap power injector enable {Cisco_AP | all} switch_port_mac_address
• If you have a dual-radio 1250 series access point and want to disable one of its radios in order to enable
the other radio to receive full power, enter this command:
config {802.11a | 802.11b} disable Cisco_AP
Note You must manually reset the access point in order for the change to take effect.
• See the PoE settings for a specific access point by entering this command:
show ap config general Cisco_AP
Information similar to the following appears:
Cisco AP Identifier.............................. 1
Cisco AP Name.................................... AP1
...
PoE Pre-Standard Switch.......................... Enabled
PoE Power Injector MAC Addr...................... Disabled
Power Type/Mode.................................. PoE/Low Power (degraded mode)
...
The Power Type/Mode text box shows “degraded mode” if the access point is not operating at full power.
• See the controller’s trap log by entering this command:
show traplog
If the access point is not operating at full power, the trap contains “PoE Status: degraded operation.”
• You can power an access point by a Cisco prestandard 15-W switch with Power over Ethernet (PoE)
by entering this command:
config ap power pre-standard {enable | disable} {all | Cisco_AP}
A Cisco prestandard 15-W switch does not support intelligent power management (IPM) but does have
sufficient power for a standard access point. The following Cisco prestandard 15-W switches are available:
• WS-C3550, WS-C3560, WS-C3750
• C1880
• 2600, 2610, 2611, 2621, 2650, 2651
• 2610XM, 2611XM, 2621XM, 2650XM, 2651XM, 2691
• 2811, 2821, 2851
• 3631-telco, 3620, 3640, 3660
• 3725, 3745
• 3825, 3845
The enable version of this command is required for full functionality when the access point is powered
by a Cisco prestandard 15-W switch. It is safe to use if the access point is powered by either an IPM
switch or a power injector or if the access point is not using one of the 15-W switches listed above.
You might need this command if your radio operational status is "Down" when you expect it to be "Up."
Enter the show msglog command to look for this error message, which indicates a PoE problem:
Step 2 Create a filter to display only clients that meet certain criteria (such as the MAC address, status, or radio type) as follows:
a) Click Change Filter to open the Search Clients dialog box.
b) Select one or more of the following check boxes to specify the criteria used when displaying clients:
c) Click Apply. The Current Filter parameter at the top of the Clients page shows the filters that are currently applied.
Note If you want to remove the filters and display the entire client list, click Clear
Filter.
Step 3 Click the MAC address of the client to view detailed information for a specific client. The Clients > Detail page appears.
This page shows the following information:
• The general properties of the client
• The security settings of the client
• The QoS properties of the client
• Client statistics
• The properties of the access point to which the client is associated
Configuring the LED State for Access Points in a Network Globally (GUI)
Step 1 Choose Wireless > Access Points > Global Configuration to open the Global Configuration page.
Step 2 Select the LED state check box.
Step 3 Choose Enable from the drop-down list adjacent to this check box.
Step 4 Click Apply.
Configuring the LED State for Access Point in a Network Globally (CLI)
• Set the LED state for all access points associated with a controller by entering this command:
config ap led-state {enable | disable} all
Step 1 Choose Wireless > Access Points > All APs and then the name of the desired access point.
Step 2 Choose the Advanced tab to open the All APs > Details for (Advanced) page.
Step 3 Select the LED state check box.
Step 4 Choose Enable from the drop-down list adjacent to this text box.
Step 5 Click Apply.
Step 1 Determine the ID of the access point for which you want to configure the LED state by entering this command:
show ap summary
Note The output of these commands is sent only to the controller console, regardless of whether the commands
were entered on the console or in a TELNET/SSH CLI session.
Step 1 Choose Wireless > Access Points > Radios > Dual-Band Radios to open the Dual-Band Radios page.
Step 2 Hover your cursor over the blue drop-down arrow of the AP and click Configure.
Step 3 Configure the Admin Status.
Step 4 Configure CleanAir Admin Status as one of the following:
• Enable
• Disable
• 5 GHz Only
• 2.4 GHz Only
What to Do Next
You can monitor the access points with dual-band radios by navigating to Monitor > Access Points > Radios
> Dual-Band Radios.
Using this information, RRM can periodically reconfigure the 802.11 RF network for best efficiency. To do
this, RRM performs these functions:
• Radio resource monitoring
Note In the presence of voice traffic (in the last 100 ms), the access points defer off-channel measurements.
Each access point spends only 0.2 percent of its time off-channel. This activity is distributed across all access
points so that adjacent access points are not scanning at the same time, which could adversely affect wireless
LAN performance.
Note When there are numerous rogue access points in the network, the chance of detecting rogues on channels
157 or 161 by a FlexConnect or local mode access point is small. In such cases, the monitor mode AP can
be used for rogue detection.
Overriding the TPC Algorithm with Minimum and Maximum Transmit Power Settings
The TPC algorithm balances RF power in many diverse RF environments. However, it is possible that automatic
power control will not be able to resolve some scenarios in which an adequate RF design was not possible to
implement due to architectural restrictions or site restrictions—for example, when all access points must be
mounted in a central hallway, placing the access points close together, but requiring coverage out to the edge
of the building.
In these scenarios, you can configure maximum and minimum transmit power limits to override TPC
recommendations. The maximum and minimum TPC power settings apply to all access points through RF
profiles in a RF network.
To set the Maximum Power Level Assignment and Minimum Power Level Assignment, enter the maximum
and minimum transmit power used by RRM in the text boxes in the Tx Power Control page. The range for
these parameters is -10 to 30 dBm. The minimum value cannot be greater than the maximum value; the
maximum value cannot be less than the minimum value.
If you configure a maximum transmit power, RRM does not allow any access point attached to the to exceed
this transmit power level (whether the power is set by RRM TPC or by coverage hole detection). For example,
if you configure a maximum transmit power of 11 dBm, then no access point would transmit above 11 dBm,
unless the access point is configured manually.
Note We recommend that you use only non-overlapping channels (1, 6, 11, and so on).
The examines a variety of real-time RF characteristics to efficiently handle channel assignments as follows:
• Access point received energy—The received signal strength measured between each access point and
its nearby neighboring access points. Channels are optimized for the highest network capacity.
• Noise—Noise can limit signal quality at the client and access point. An increase in noise reduces the
effective cell size and degrades user experience. By optimizing channels to avoid noise sources, the can
optimize coverage while maintaining system capacity. If a channel is unusable due to excessive noise,
that channel can be avoided.
• 802.11 Interference—Interference is any 802.11 traffic that is not part of your wireless LAN, including
rogue access points and neighboring wireless networks. Lightweight access points constantly scan all
channels looking for sources of interference. If the amount of 802.11 interference exceeds a predefined
configurable threshold (the default is 10 percent), the access point sends an alert to the . Using the RRM
algorithms, the may then dynamically rearrange channel assignments to increase system performance
in the presence of the interference. Such an adjustment could result in adjacent lightweight access points
being on the same channel, but this setup is preferable to having the access points remain on a channel
that is unusable due to an interfering foreign access point.
In addition, if other wireless networks are present, the shifts the usage of channels to complement the
other networks. For example, if one network is on channel 6, an adjacent wireless LAN is assigned to
channel 1 or 11. This arrangement increases the capacity of the network by limiting the sharing of
frequencies. If a channel has virtually no capacity remaining, the may choose to avoid this channel. In
very dense deployments in which all nonoverlapping channels are occupied, the does its best, but you
must consider RF density when setting expectations.
• Load and utilization—When utilization monitoring is enabled, capacity calculations can consider that
some access points are deployed in ways that carry more traffic than other access points (for example,
a lobby versus an engineering area). The can then assign channels to improve the access point with the
worst performance reported. The load is taken into account when changing the channel structure to
minimize the impact on clients currently in the wireless LAN. This metric keeps track of every access
point’s transmitted and received packet counts to determine how busy the access points are. New clients
avoid an overloaded access point and associate to a new access point. This parameter is disabled by
default.
The combines this RF characteristic information with RRM algorithms to make system-wide decisions.
Conflicting demands are resolved using soft-decision metrics that guarantee the best choice for minimizing
network interference. The end result is optimal channel configuration in a three-dimensional space, where
access points on the floor above and below play a major factor in an overall wireless LAN configuration.
Note Radios using 40-MHz channels in the 2.4-GHz band or or 80MHz channels are not supported by DCA.
Note DCA algorithm interval is set to one hour, but DCA algorithm always runs in default interval of 10min,
channel allocation happens for every 10min interval for the first 10 cycles, and channel changes as per
DCA algorithm for every 10min. After that it goes back to the configured time interval. This is common
for both DCA interval and Anchor time since it follows the steady state.
Note If DCA/TPC is turned off on the RF-group member, and auto is set on RF-group leader, the channel/TX
power on member gets changed as per the algorithm run on the RF-group leader.
Benefits of RRM
RRM produces a network with optimal capacity, performance, and reliability. It frees you from having to
continually monitor the network for noise and interference problems, which can be transient and difficult to
troubleshoot. RRM ensures that clients enjoy a seamless, trouble-free connection throughout the Cisco unified
wireless network.
RRM uses separate monitoring and control for each deployed network: 802.11a and 802.11b/g. The RRM
algorithms run separately for each radio type (802.11a and 802.11b/g). RRM uses both measurements and
algorithms. RRM measurements can be adjusted using monitor intervals, but they cannot be disabled. RRM
algorithms are enabled automatically but can be disabled by statically configuring channel and power
assignment. The RRM algorithms run at a specified updated interval, which is 600 seconds by default.
to a Cisco WLC that is not encrypted. The two Cisco WLCs and their access points will not recognize each
other as neighbors and cannot form an RF group. It is possible to assign two Cisco WLCs in a static RF group
configuration that has mismatched encryption settings. In this case, the two Cisco WLCs do not function as
a single RF group because the access points belonging to the mismatched Cisco WLCs do not recognize one
another as neighbors in the group.
Step 1 Choose Wireless > 802.11a/n/ac or 802.11b/g/n > RRM > RF Grouping to open the 802.11a (or 802.11b/g) RRM >
RF Grouping page.
Step 2 From the Group Mode drop-down list, select the mode you want to configure for this Cisco WLC.
You can configure RF grouping in the following modes:
• auto—Sets the RF group selection to automatic update mode.
Note This mode does not support IPv6 based
configuration.
• leader—Sets the RF group selection to static mode, and sets this Cisco WLC as the group leader.
Note Leader supports static IPv6
address.
Note If a RF group member is configured using IPv4 address, then IPv4 address is used to communicate with
the leader. The same is applicable for a RF group member configured using IPv6 too.
• off—Sets the RF group selection off. Every Cisco WLC optimizes its own access point parameters.
Note A configured static leader cannot become a member of another Cisco WLC until its mode is set to “auto”.
Note A Cisco WLC with a lower priority cannot assume the role of a group leader if a Cisco WLC with a higher
priority is available. Here priority is related to the processing power of the Cisco WLC.
Note We recommend that Cisco WLCs participate in automatic RF grouping. You can override RRM settings
without disabling automatic RF group participation.
Step 3 Click Apply to save the configuration and click Restart to restart RRM RF Grouping algorithm.
Step 4 If you configured RF Grouping mode for this Cisco WLC as a static leader, you can add group members from the RF
Group Members section as follows:
1 In the Cisco WLC Name text box, enter the Cisco WLC that you want to add as a member to this group.
2 In the IP Address (IPv4/IPv6) text box, enter the IPv4/IPv6 address of the RF Group Member.
3 Click Add Member to add the member to this group.
Note If the member has not joined the static leader, the reason of the failure is shown in parentheses.
Step 2 Add or remove a Cisco WLC as a static member of the RF group (if the mode is set to “leader”) by entering the these
commands:
• config advanced {802.11a | 802.11b} group-member add controller-name ipv4-or-ipv6-address
• config advanced {802.11a | 802.11b} group-member remove controller-name ipv4-or-ipv6-address
Note You can add RF Group Members using either IPv4 or IPv6 address.
Step 1 Choose Wireless > 802.11a/n/ac or 802.11b/g/n > RRM > TPC to open the 802.11a/n/ac (or 802.11b/g/n) > RRM >
Tx Power Control (TPC) page.
Step 2 Choose the Transmit Power Control version from the following options:
• Interference Optimal Mode (TPCv2)—For scenarios where voice calls are extensively used. Transmit power is
dynamically adjusted with the goal of minimum interference. It is suitable for dense networks. In this mode, there
could be higher roaming delays and coverage hole incidents.
Note We recommend that you use TCPv2 only in cases where RF issues cannot be resolved by using TCPv1.
Please evaluate and test the use of TPCv2 with the assistance of Cisco Services.
• Coverage Optimal Mode (TPCv1)—(Default) Offers strong signal coverage and stability. In this mode, power can
be kept low to gain extra capacity and reduce interference.
Step 3 Choose one of the following options from the Power Level Assignment Method drop-down list to specify the Cisco
WLC’s dynamic power assignment mode:
• Automatic—Causes the Cisco WLC to periodically evaluate and, if necessary, update the transmit power for all
joined access points. This is the default value.
• On Demand—Causes the Cisco WLC to periodically evaluate the transmit power for all joined access points.
However, the Cisco WLC updates the power, if necessary, only when you click Invoke Power Update Now.
Note The Cisco WLC does not evaluate and update the transmit power immediately after you click Invoke
Power Update Now. It waits for the next 600-second interval. This value is not configurable.
• Fixed—Prevents the Cisco WLC from evaluating and, if necessary, updating the transmit power for joined access
points. The power level is set to the fixed value chosen from the drop-down list.
Note The transmit power level is assigned an integer value instead of a value in mW or dBm. The integer
corresponds to a power level that varies depending on the regulatory domain, channel, and antennas in
which the access points are deployed.
Note For optimal performance, we recommend that you use the Automatic
setting.
Step 4 Enter the maximum and minimum power level assignment values in the Maximum Power Level Assignment and Minimum
Power Level Assignment text boxes.
The range for the Maximum Power Level Assignment is –10 to 30 dBm.
The range for the Minimum Power Level Assignment is –10 to 30 dBm.
Step 5 In the Power Threshold text box, enter the cutoff signal level used by RRM when determining whether to reduce an
access point’s power. The default value for this parameter is –70 dBm for TPCv1 and –67 dBm for TPCv2, but can be
changed when access points are transmitting at higher (or lower) than desired power levels.
The range for this parameter is –80 to –50 dBm. Increasing this value (between –65 and –50 dBm) causes the access
points to operate at a higher transmit power. Decreasing the value has the opposite effect.
In applications with a dense population of access points, it may be useful to decrease the threshold to –80 or –75 dBm
to reduce the number of BSSIDs (access points) and beacons seen by the wireless clients. Some wireless clients might
have difficulty processing a large number of BSSIDs or a high beacon rate and might exhibit problematic behavior with
the default threshold.
This page also shows the following nonconfigurable transmit power level parameter settings:
• Power Neighbor Count—The minimum number of neighbors an access point must have for the transmit power
control algorithm to run.
• Power Assignment Leader—The MAC address of the RF group leader, which is responsible for power level
assignment.
• Last Power Level Assignment—The last time RRM evaluated the current transmit power level assignments.
Step 1 Assign a defer-priority for the channel scan by entering this command:
config wlan channel-scan defer-priority priority [enable | disable] WLAN-id
The valid range for the priority argument is 0 to 7.
The priority is 0 to 7 (this value should be set to 6 on the client and on the WLAN).
Use this command to configure the amount of time that scanning will be deferred following an UP packet in the queue.
Step 2 Assign the channel scan defer time (in milliseconds) by entering this command:
config wlan channel-scan defer-time msec WLAN-id
The time value is in miliseconds (ms) and the valid range is 100 (default) to 60000 (60 seconds). This setting should
match the requirements of the equipment on your wireless LAN.
You can also configure this feature on the Cisco WLC GUI by selecting WLANs, and either edit an existing WLAN or
create a new one.
Note This functionality is helpful when you know that the clients do not support certain channels because they
are legacy devices or they have certain regulatory restrictions.
Step 4 From the Interval drop-down list, choose one of the following options to specify how often the DCA algorithm is allowed
to run: 10 minutes, 1 hour, 2 hours, 3 hours, 4 hours, 6 hours, 8 hours, 12 hours, or 24 hours. The default value is
10 minutes.
Note If your Cisco WLC supports only OfficeExtend access points, we recommend that you set the DCA interval to
6 hours for optimal performance. For deployments with a combination of OfficeExtend access points and local
access points, the range of 10 minutes to 24 hours can be used.
Step 5 From the AnchorTime drop-down list, choose a number to specify the time of day when the DCA algorithm is to start.
The options are numbers between 0 and 23 (inclusive) representing the hour of the day from 12:00 a.m. to 11:00 p.m.
Step 6 Select the Avoid Foreign AP Interference check box to cause the Cisco WLC’s RRM algorithms to consider 802.11
traffic from foreign access points (those not included in your wireless network) when assigning channels to lightweight
access points, or unselect it to disable this feature. For example, RRM may adjust the channel assignment to have access
points avoid channels close to foreign access points. The default value is selected.
Step 7 Select the Avoid Cisco AP Load check box to cause the Cisco WLC’s RRM algorithms to consider 802.11 traffic from
Cisco lightweight access points in your wireless network when assigning channels, or unselect it to disable this feature.
For example, RRM can assign better reuse patterns to access points that carry a heavier traffic load. The default value
is unselected.
Step 8 Select the Avoid Non-802.11a (802.11b) Noise check box to cause the Cisco WLC’s RRM algorithms to consider noise
(non-802.11 traffic) in the channel when assigning channels to lightweight access points, or unselect it to disable this
feature. For example, RRM may have access points avoid channels with significant interference from nonaccess point
sources, such as microwave ovens. The default value is selected.
Step 9 Select the Avoid Persistent Non-WiFi Interference check box to enable the Cisco WLC to ignore persistent non-WiFi
interference.
Step 10 From the DCA Channel Sensitivity drop-down list, choose one of the following options to specify how sensitive the
DCA algorithm is to environmental changes such as signal, load, noise, and interference when determining whether to
change channels:
• Low—The DCA algorithm is not particularly sensitive to environmental changes.
• Medium—The DCA algorithm is moderately sensitive to environmental changes.
• High—The DCA algorithm is highly sensitive to environmental changes.
The default value is Medium. The DCA sensitivity thresholds vary by radio band, as noted in the table below.
Medium 10 dB 15 dB
Low 20 dB 20 dB
Step 11 For 802.11a/n/ac networks only, choose one of the following channel width options to specify the channel bandwidth
supported for all 802.11n radios in the 5-GHz band:
• 20 MHz—The 20-MHz channel bandwidth.
◦40 MHz—The 40-MHz channel bandwidth
Note If you choose 40 MHz, be sure to choose at least two adjacent channels from the DCA Channel List
in Step 13 (for example, a primary channel of 36 and an extension channel of 40). If you choose only
one channel, that channel is not used for 40-MHz channel width.
Note If you choose 40 MHz, you can also configure the primary and extension channels used by individual
access points.
Note To override the globally configured DCA channel width setting, you can statically configure an
access point’s radio for 20- or 40-MHz mode on the 802.11a/n Cisco APs > Configure page. if you
then change the static RF channel assignment method to WLC Controlled on the access point radio,
the global DCA configuration overrides the channel width configuration that the access point was
previously using. It can take up to 30 minutes (depending on how often DCA is configured to run)
for the change to take effect.
Note If you choose 40 MHz on the 802.11a radio, you cannot pair channels 116, 140, and 165 with any
other channels.
• best—It selects the best bandwidth suitable. This option is enabled for the 5-GHz radios only.
This page also shows the following nonconfigurable channel parameter settings:
• Channel Assignment Leader—The MAC address of the RF group leader, which is responsible for channel assignment.
• Last Auto Channel Assignment—The last time RRM evaluated the current channel assignments.
Step 12 Select the Avoid check for non-DFS channel to enable the Cisco WLC to avoid checks for non-DFS channels. DCA
configuration requires at least one non-DFS channel in the list. In the EU countries, outdoor deployments do not support
non-DFS channels. Customers based in EU or regions with similar regulations must enable this option or at least have
one non-DFS channel in the DCA list even if the channel is not supported by the APs.
Note This parameter is applicable only for deployments having outdoor access points such as 1522 and
1524.
Step 13 In the DCA Channel List area, the DCA Channels text box shows the channels that are currently selected. To choose a
channel, select its check box in the Select column. To exclude a channel, unselect its check box.
The ranges are as follows: 802.11a—36, 40, 44, 48, 52, 56, 60, 64, 100, 104, 108, 112, 116, 132, 136, 140, 149, 153,
157, 161, 165, 190, 196 802.11b/g—1, 2, 3, 4, 5, 6, 7, 8, 9, 10, 11
The defaults are as follows: 802.11a—36, 40, 44, 48, 52, 56, 60, 64, 100, 104, 108, 112, 116, 132, 136, 140, 149, 153,
157, 161 802.11b/g—1, 6, 11
Note These extended UNII-2 channels in the 802.11a band do not appear in the channel list: 100, 104, 108, 112, 116,
132, 136, and 140. If you have Cisco Aironet 1520 series mesh access points in the -E regulatory domain, you
must include these channels in the DCA channel list before you start operation. If you are upgrading from a
previous release, verify that these channels are included in the DCA channel list. To include these channels in
the channel list, select the Extended UNII-2 Channels check box.
Step 14 If you are using Cisco Aironet 1520 series mesh access points in your network, you need to set the 4.9-GHz channels in
the 802.11a band on which they are to operate. The 4.9-GHz band is for public safety client access traffic only. To choose
a 4.9-GHz channel, select its check box in the Select column. To exclude a channel, unselect its check box.
The ranges are as follows: 802.11a—1, 2, 3, 4, 5, 6, 7, 8, 9, 10, 11, 12, 13, 14, 15, 16, 17, 18, 19, 20, 21, 22, 23, 24, 25,
26
The defaults are as follows: 802.11a—20, 26
Configuring RRM Profile Thresholds, Monitoring Channels, and Monitor Intervals (GUI)
Step 1 Choose Wireless > 802.11a/n/ac or 802.11b/g/n > RRM > General to open the 802.11a/n/ac (or 802.11b/g/n) > RRM
> General page.
Step 2 Configure profile thresholds used for alarming as follows:
Note The profile thresholds have no bearing on the functionality of the RRM algorithms. Lightweight access points
send an SNMP trap (or an alert) to the Cisco WLC when the values set for these threshold parameters are
exceeded.
a) In the Interference text box, enter the percentage of interference (802.11 traffic from sources outside of your wireless
network) on a single access point. The valid range is 0 to 100%, and the default value is 10%.
b) In the Clients text box, enter the number of clients on a single access point. The valid range is 1 to 200, and the
default value is 12.
c) In the Noise text box, enter the level of noise (non-802.11 traffic) on a single access point. The valid range is –127
to 0 dBm, and the default value is –70 dBm.
d) In the Utilization text box, enter the percentage of RF bandwidth being used by a single access point. The valid range
is 0 to 100%, and the default value is 80%.
Step 3 From the Channel List drop-down list, choose one of the following options to specify the set of channels that the access
point uses for RRM scanning:
• All Channels—RRM channel scanning occurs on all channels supported by the selected radio, which includes
channels not allowed in the country of operation.
• Country Channels—RRM channel scanning occurs only on the data channels in the country of operation. This is
the default value.
• DCA Channels—RRM channel scanning occurs only on the channel set used by the DCA algorithm, which by
default includes all of the non-overlapping channels allowed in the country of operation. However, you can specify
the channel set to be used by DCA if desired. To do so, follow instructions in the Dynamic Channel Assignment.
Step 2 Choose the Transmit Power Control version by entering this command:
config advanced {802.11a | 802.11b} tpc-version {1 | 2}
where:
• TPCv1: Coverage-optimal—(Default) Offers strong signal coverage and stability with negligent intercell interferences
and sticky client syndrome.
• TPCv2: Interference-optimal—For scenarios where voice calls are extensively used. Tx power is dynamically
adjusted with the goal of minimum interference. It is suitable for dense networks. In this mode, there can be higher
roaming delays and coverage hole incidents.
where threshold is a value from –80 to –50 dBm. Increasing this value causes the access points to operate at higher
transmit power rates. Decreasing the value has the opposite effect.
In applications with a dense population of access points, it may be useful to decrease the threshold to –80 or –75
dBm in order to reduce the number of BSSIDs (access points) and beacons seen by the wireless clients. Some
wireless clients may have difficulty processing a large number of BSSIDs or a high beacon rate and may exhibit
problematic behavior with the default threshold.
• Configure the Transmit Power Control Version 2 on a per-channel basis by entering this command:
config advanced {802.11a | 802.11b} tpcv2-per-chan {enable | disable}
Step 4 Perform one of the following to configure dynamic channel assignment (DCA):
• Have RRM automatically configure all 802.11 channels based on availability and interference by entering this
command:
config {802.11a | 802.11b} channel global auto
• Have RRM automatically reconfigure all 802.11 channels one time based on availability and interference by entering
this command:
config {802.11a | 802.11b} channel global once
• Disable RRM and set all channels to their default values by entering this command:
config {802.11a | 802.11b} channel global off
• Restart aggressive DCA cycle by entering this command:
config {802.11a | 802.11b} channel global restart
• To specify the channel set used for DCA by entering this command:
config advanced {802.11a | 802.11b} channel {add | delete} channel_number
You can enter only one channel number per command. This command is helpful when you know that the clients
do not support certain channels because they are legacy devices or they have certain regulatory restrictions.
◦high means that the DCA algorithm is highly sensitive to environmental changes.
The DCA sensitivity thresholds vary by radio band, as noted in following table.
Medium 10 dB 15 dB
Low 20 dB 20 dB
• config advanced 802.11a channel dca chan-width {20 | 40 | 80}—Configures the DCA channel width for all
802.11n radios in the 5-GHz band.
where
◦20 sets the channel width for 802.11n radios to 20 MHz. This is the default value.
◦40 sets the channel width for 802.11n radios to 40 MHz.
Note If you choose 40, be sure to set at least two adjacent channels in the config advanced 802.11a
channel {add | delete} channel_number command in Step 4 (for example, a primary channel of 36
and an extension channel of 40). If you set only one channel, that channel is not used for 40-MHz
channel width.
Note If you choose 40, you can also configure the primary and extension channels used by individual
access points.
Note To override the globally configured DCA channel width setting, you can configure an access point’s
radio mode using the config 802.11a chan_width Cisco_AP {20 | 40 | 80} command. If you change
the static configuration to global on the access point radio, the global DCA configuration overrides
the channel width configuration that the access point was previously using. It can take up to 30
minutes (depending on how often DCA is configured to run) for the change to take effect.
◦80 sets the channel width for the 802.11ac radios to 80 MHz.
• config advanced {802.11a | 802.11b} channel noise {enable | disable}—Enables or disables noise avoidance in
the channel assignment.
• config advanced {802.11a | 802.11b} channel update—Initiates an update of the channel selection for every
Cisco access point.
Note See the discovery type by entering the show advanced 802.11{a|b} monitor command.
Note RF groups and mobility groups are similar in that they both define clusters of Cisco WLCs, but they are
different in terms of their use. An RF group facilitates scalable, system-wide dynamic RF management
while a mobility group facilitates scalable, system-wide mobility and Cisco WLC redundancy.
RF Group Leader
Starting in the 7.0.116.0 release, the RF Group Leader can be configured in two ways as follows:
• Auto Mode—In this mode, the members of an RF group elect an RF group leader to maintain a “master”
power and channel scheme for the group. The RF grouping algorithm dynamically chooses the RF group
leader and ensures that an RF group leader is always present. Group leader assignments can and do
change (for instance, if the current RF group leader becomes inoperable or if RF group members
experience major changes).
• Static Mode—In this mode, the user selects a Cisco WLC as an RF group leader manually. In this mode,
the leader and the members are manually configured and are therefore fixed. If the members are unable
to join the RF group, the reason is indicated. The leader tries to establish a connection with a member
every 1 minute if the member has not joined in the previous attempt.
The RF group leader analyzes real-time radio data collected by the system, calculates the power and channel
assignments, and sends them to each of the Cisco WLCs in the RF group. The RRM algorithms ensure
system-wide stability and restrain channel and power scheme changes to the appropriate local RF
neighborhoods.
In Cisco WLC software releases prior to 6.0, the dynamic channel assignment (DCA) search algorithm attempts
to find a good channel plan for the radios associated to Cisco WLCs in the RF group, but it does not adopt a
new channel plan unless it is considerably better than the current plan. The channel metric of the worst radio
in both plans determines which plan is adopted. Using the worst-performing radio as the single criterion for
adopting a new channel plan can result in pinning or cascading problems.
Pinning occurs when the algorithm could find a better channel plan for some of the radios in an RF group but
is prevented from pursuing such a channel plan change because the worst radio in the network does not have
any better channel options. The worst radio in the RF group could potentially prevent other radios in the group
from seeking better channel plans. The larger the network, the more likely pinning becomes.
Cascading occurs when one radio’s channel change results in successive channel changes to optimize the
remaining radios in the RF neighborhood. Optimizing these radios could lead to their neighbors and their
neighbors’ neighbors having a suboptimal channel plan and triggering their channel optimization. This effect
could propagate across multiple floors or even multiple buildings, if all the access point radios belong to the
same RF group. This change results in considerable client confusion and network instability.
The main cause of both pinning and cascading is the way in which the search for a new channel plan is
performed and that any potential channel plan changes are controlled by the RF circumstances of a single
radio. In Cisco WLC software release 6.0, the DCA algorithm has been redesigned to prevent both pinning
and cascading. The following changes have been implemented:
• Multiple local searches—The DCA search algorithm performs multiple local searches initiated by
different radios within the same DCA run rather than performing a single global search driven by a
single radio. This change addresses both pinning and cascading while maintaining the desired flexibility
and adaptability of DCA and without jeopardizing stability.
• Multiple channel plan change initiators (CPCIs)—Previously, the single worst radio was the sole initiator
of a channel plan change. Now each radio within the RF group is evaluated and prioritized as a potential
initiator. Intelligent randomization of the resulting list ensures that every radio is eventually evaluated,
which eliminates the potential for pinning.
• Limiting the propagation of channel plan changes (Localization)—For each CPCI radio, the DCA
algorithm performs a local search for a better channel plan, but only the CPCI radio itself and its one-hop
neighboring access points are actually allowed to change their current transmit channels. The impact of
an access point triggering a channel plan change is felt only to within two RF hops from that access
point, and the actual channel plan changes are confined to within a one-hop RF neighborhood. Because
this limitation applies across all CPCI radios, cascading cannot occur.
• Non-RSSI-based cumulative cost metric—A cumulative cost metric measures how well an entire region,
neighborhood, or network performs with respect to a given channel plan. The individual cost metrics of
all access points in that area are considered in order to provide an overall understanding of the channel
plan’s quality. These metrics ensure that the improvement or deterioration of each single radio is factored
into any channel plan change. The objective is to prevent channel plan changes in which a single radio
improves but at the expense of multiple other radios experiencing a considerable performance decline.
The RRM algorithms run at a specified updated interval, which is 600 seconds by default. Between update
intervals, the RF group leader sends keepalive messages to each of the RF group members and collects real-time
RF data.
Note Several monitoring intervals are also available. See the Configuring RRM section for details.
RF Group Name
A Cisco WLC is configured with an RF group name, which is sent to all access points joined to the Cisco
WLC and used by the access points as the shared secret for generating the hashed MIC in the neighbor
messages. To create an RF group, you configure all of the Cisco WLCs to be included in the group with the
same RF group name.
If there is any possibility that an access point joined to a Cisco WLC may hear RF transmissions from an
access point on a different Cisco WLC, you should configure the Cisco WLCs with the same RF group name.
If RF transmissions between access points can be heard, then system-wide RRM is recommended to avoid
802.11 interference and contention as much as possible.
Configuring RF Groups
This section describes how to configure RF groups through either the GUI or the CLI.
Note The RF group name is generally set at deployment time through the Startup Wizard. However, you can
change it as necessary.
Note When the multiple-country feature is being used, all Cisco WLCs intended to join the same RF group
must be configured with the same set of countries, configured in the same order.
Note You can also configure RF groups using the Cisco Prime Infrastructure.
Step 1 Create an RF group by entering the config network rf-network-name name command:
Note You can also view the status of RF groups using the Cisco Prime Infrastructure.
Step 1 Choose Wireless > 802.11a/n/ac > or 802.11b/g/n > RRM > RF Grouping to open the 802.11a/n/ac (or 802.11b/g/n)
RRM > RF Grouping page.
This page shows the details of the RF group, displaying the configurable parameter RF Group mode, the RF Group
role of this Cisco WLC, the Update Interval and the Cisco WLC name and IP address of the Group Leader to this
Cisco WLC.
Note RF grouping mode can be set using the Group Mode drop-down list.
Tip Once a Cisco WLC has joined as a static member and you want to change the grouping mode, we recommend
that you remove the member from the configured static-leader and also make sure that a member Cisco WLC
has not been configured to be a member on multiple static leaders. This is to avoid repeated join attempts from
one or more RF static leaders.
Step 2 (Optional) Repeat this procedure for the network type that you did not select (802.11a/n/ac or 802.11b/g/n).
Step 1 See which Cisco WLC is the RF group leader for the 802.11a RF network by entering this command:
show advanced 802.11a group
Information similar to the following appears:
Radio RF Grouping
802.11a Group Mode............................. STATIC
Step 1 Make sure that each Cisco WLC in the RF group has been configured with the same RF group name.
Note The name is used to verify the authentication IE in all beacon frames. If the Cisco WLCs have different names,
false alarms will occur.
Step 2 Choose Wireless to open the All APs page.
Step 3 Click the name of an access point to open the All APs > Details page.
Step 4 Choose either local or monitor from the AP Mode drop-down list and click Apply to commit your changes.
Step 5 Click Save Configuration to save your changes.
Step 6 Repeat Step 2 through Step 5 for every access point connected to the Cisco WLC.
Step 7 Choose Security > Wireless Protection Policies > AP Authentication/MFP to open the AP Authentication Policy
page.
The name of the RF group to which this Cisco WLC belongs appears at the top of the page.
Step 8 Choose AP Authentication from the Protection Type drop-down list to enable rogue access point detection.
Step 9 Enter a number in the Alarm Trigger Threshold edit box to specify when a rogue access point alarm is generated. An
alarm occurs when the threshold value (which specifies the number of access point frames with an invalid authentication
IE) is met or exceeded within the detection period.
Note The valid threshold range is from1 to 255, and the default threshold value is 1. To avoid false alarms, you may
want to set the threshold to a higher value.
Step 10 Click Apply to commit your changes.
Step 11 Click Save Configuration to save your changes.
Step 12 Repeat this procedure on every Cisco WLC in the RF group.
Note If rogue access point detection is not enabled on every Cisco WLC in the RF group, the access points on the
Cisco WLCs with this feature disabled are reported as rogues.
Step 1 Make sure that each Cisco WLC in the RF group has been configured with the same RF group name.
Note The name is used to verify the authentication IE in all beacon frames. If the Cisco WLCs have different names,
false alarms will occur.
Step 2 Configure a particular access point for local (normal) mode or monitor (listen-only) mode by entering this command:
config ap mode local Cisco_AP or config ap mode monitor Cisco_AP
Note If you choose to statically assign channels and power levels to your access points and/or to disable dynamic
channel and power assignment, you should still use automatic RF grouping to avoid spurious rogue device
events.
You can disable dynamic channel and power assignment globally for a Cisco WLC, or you can leave dynamic
channel and power assignment enabled and statically configure specific access point radios with a channel
and power setting. While you can specify a global default transmit power parameter for each network type
that applies to all the access point radios on a Cisco WLC, you must set the channel for each access point
radio when you disable dynamic channel assignment. You may also want to set the transmit power for each
access point instead of leaving the global transmit power in effect.
Step 1 Choose Wireless > Access Points > Radios > 802.11a/n/ac or 802.11b/g/n to open the 802.11a/n/ac (or 802.11b/g/n)
Radios page.
This page shows all the 802.11a/n/ac or 802.11b/g/n access point radios that are joined to the Cisco WLC and their
current settings. The Channel text box shows both the primary and extension channels and uses an asterisk to indicate
if they are globally assigned.
Step 2 Hover your cursor over the blue drop-down arrow for the access point for which you want to modify the radio configuration
and choose Configure. The 802.11a/n/ac (or 802.11b/g/n) Cisco APs > Configure page appears.
Step 3 Specify the RF Channel Assignment from the following options:
• Global—Choose this to specify a global value.
• Custom—Choose this and then select a value from the adjacent drop-down list to specify a custom value.
Step 5 In the RF Channel Assignment area, choose Custom for the Assignment Method under RF Channel Assignment and
choose a channel from the drop-down list to assign an RF channel to the access point radio.
Step 6 In the Tx Power Level Assignment area, choose the Custom assignment method and choose a transmit power level from
the drop-down list to assign a transmit power level to the access point radio.
The transmit power level is assigned an integer value instead of a value in mW or dBm. The integer corresponds to a
power level that varies depending on the regulatory domain in which the access points are deployed. The number of
available power levels varies based on the access point model. However, power level 1 is always the maximum power
level allowed per country code setting, with each successive power level representing 50% of the previous power level.
For example, 1 = maximum power level in a particular regulatory domain, 2 = 50% power, 3 = 25% power, 4 = 12.5%
power, and so on.
Note See the hardware installation guide for your access point for the maximum transmit power levels supported per
regulatory domain. Also, see the data sheet for your access point for the number of power levels supported.
Note If the access point is not operating at full power, the “Due to low PoE, radio is transmitting at degraded power”
message appears under the Tx Power Level Assignment section.
Step 7 Choose Enable from the Admin Status drop-down list to enable this configuration for the access point.
Step 8 Click Apply.
Step 9 Have the Cisco WLC send the access point radio admin state immediately to Cisco Prime Infrastructure as follows:
1 Choose Wireless > 802.11a/n/ac or 802.11b/g/n > Network to open the 802.11a (or 802.11b/g) Global Parameters
page.
2 Select the 802.11a (or 802.11b/g) Network Status check box.
3 Click Apply.
Step 1 Disable the radio of a particular access point on the 802.11a/n/ac or 802.11b/g/n network by entering this command:
config {802.11a | 802.11b} disable Cisco_AP
Step 2 Configure the channel width for a particular access point by entering this command:
config {802.11a | 802.11b} chan_width Cisco_AP {20 | 40 | 80}
where
• 20 allows the radio to communicate using only 20-MHz channels. Choose this option for legacy 802.11a radios,
20-MHz 802.11n radios, or 40-MHz 802.11n radios that you want to operate using only 20-MHz channels. This
is the default value.
• 40 allows 40-MHz 802.11n radios to communicate using two adjacent 20-MHz channels bonded together. The
radio uses the primary channel that you choose as well as its extension channel for faster throughput. Each channel
has only one extension channel (36 and 40 are a pair, 44 and 48 are a pair, and so on). For example, if you choose
a primary channel of 44, the Cisco WLC would use channel 48 as the extension channel. If you choose a primary
channel of 48, the Cisco WLC would use channel 44 as the extension channel.
Note This parameter can be configured only if the primary channel is statically assigned.
Note Statically configuring an access point’s radio for 20-MHz or 40-MHz or 80-MHz mode overrides the
globally configured DCA channel width setting (configured using the config advanced 802.11a channel
dca chan-width-11n {20 | 40 | 80} command). If you ever change the static configuration back to global
on the access point radio, the global DCA configuration overrides the channel width configuration that
the access point was previously using. It can take up to 30 minutes (depending on how often DCA is
configured to run) for the change to take effect.
• 80 sets the channel width for the 802.11ac radios to 80 MHz.
Note Channels 116, 120, 124, and 128 are not available in the U.S. and Canada for 40-MHz channel bonding.
Step 3 Enable or disable the use of specific antennas for a particular access point by entering this command:
config {802.11a | 802.11b} 11nsupport antenna {tx | rx} Cisco_AP {A | B | C} {enable | disable}
where A, B, and C are antenna ports. A is the right antenna port, B is the left antenna port, and C is the center antenna
port. For example, to enable transmissions from the antenna in access point AP1’s antenna port C on the 802.11a network,
you would enter this command:
config 802.11a 11nsupport antenna tx AP1 C enable
Note You cannot enable or disable individual antennas for 802.11ac because the 802.11ac module antennas are
internal.
Step 4 Specify the external antenna gain, which is a measure of an external antenna’s ability to direct or focus radio energy over
a region of space entering this command:
config {802.11a | 802.11b} antenna extAntGain antenna_gain Cisco_AP
High-gain antennas have a more focused radiation pattern in a specific direction. The antenna gain is measured in 0.5
dBi units, and the default value is 7 times 0.5 dBi, or 3.5 dBi.
If you have a high-gain antenna, enter a value that is twice the actual dBi value (see Cisco Aironet Antenna Reference
Guide for antenna dBi values). Otherwise, enter 0. For example, if your antenna has a 4.4-dBi gain, multiply the 4.4 dBi
by 2 to get 8.8 and then round down to enter only the whole number (8). The Cisco WLC reduces the actual equivalent
isotropic radiated power (EIRP) to make sure that the antenna does not violate your country’s regulations.
Step 5 Configure beamforming for the 5-GHz radios for all APs or a specific by entering this command:
config 802.11a {global | ap ap-name} {enable | disable}
Step 6 Specify the channel that a particular access point is to use by entering this command:
config {802.11a | 802.11b} channel ap Cisco_AP channel
For example, to configure 802.11a channel 36 as the default channel on AP1, enter the config 802.11a channel ap AP1
36 command.
The channel you choose is the primary channel (for example, channel 36), which is used for communication by legacy
802.11a radios and 802.11n 20-MHz radios. 802.11n 40-MHz radios use this channel as the primary channel but also
use an additional bonded extension channel for faster throughput, if you chose 40 for the channel width.
Note Changing the operating channel causes the access point radio to
reset.
Step 7 Specify the transmit power level that a particular access point is to use by entering this command:
config {802.11a | 802.11b} txPower ap Cisco_AP power_level
For example, to set the transmit power for 802.11a AP1 to power level 2, enter the config 802.11a txPower ap AP1 2
command.
The transmit power level is assigned an integer value instead of a value in mW or dBm. The integer corresponds to a
power level that varies depending on the regulatory domain in which the access points are deployed. The number of
available power levels varies based on the access point model. However, power level 1 is always the maximum power
level allowed per country code setting, with each successive power level representing 50% of the previous power level.
For example, 1 = maximum power level in a particular regulatory domain, 2 = 50% power, 3 = 25% power, 4 = 12.5%
power, and so on.
In certain cases, Cisco access points support only 7 power levels for certain channels, so that the Cisco Wireless Controller
considers the 7th and 8th power levels as the same. If the 8th power level is configured on those channels, the configuration
would fail since the controller considers the 7th power level as the lowest acceptable valid power level. These power
values are derived based on the regulatory compliance limits and minimum hardware limitation which varies across
different Cisco access points. For example, Cisco 3500, 1140, and 1250 series access points allow the configuration of
last power levels because those access points report the "per path power" to the controller, whereas all next generation
acess points such as Cisco 3700, 3600, 2600, and 1600 series access points report "total power value" to the controller,
thereby decreasing the allowed power levels for newer generation products. For example, if the last power level in the
3600E access point has a power value of 4dbm (total power), then it actually means the power value is -2dbm (per path).
Note See the hardware installation guide for your access point for the maximum transmit power levels supported per
regulatory domain. Also, see data sheet for your access point for the number of power levels supported.
Step 8 Save your settings by entering this command:
save config
Step 9 Repeat Step 2 through Step 7 for each access point radio for which you want to assign a static channel and power level.
Step 10 Reenable the access point radio by entering this command:
config {802.11a | 802.11b} enable Cisco_AP
Step 11 Have the Cisco WLC send the access point radio admin state immediately to WCS by entering this command:
config {802.11a | 802.11b} enable network
Cisco AP Identifier.............................. 7
Cisco AP Name.................................... AP1
...
Tx Power
Num Of Supported Power Levels ............. 8
Tx Power Level 1 .......................... 20 dBm
Tx Power Level 2 .......................... 17 dBm
Tx Power Level 3 .......................... 14 dBm
Tx Power Level 4 .......................... 11 dBm
Tx Power Level 5 .......................... 8 dBm
Tx Power Level 6 .......................... 5 dBm
Tx Power Level 7 .......................... 2 dBm
Tx Power Level 8 .......................... -1 dBm
Tx Power Configuration .................... CUSTOMIZED
Current Tx Power Level .................... 1
802.11n Antennas
Tx
A....................................... ENABLED
B....................................... ENABLED
Rx
A....................................... DISABLED
B....................................... DISABLED
C.................................... ENABLED
Step 1 Choose Wireless > 802.11a/n/ac or 802.11b/g/n > RRM > Auto RF to open the 802.11a/n/ac (or 802.11b/g/n) Global
Parameters > Auto RF page.
Step 2 Disable dynamic channel assignment by choosing OFF under RF Channel Assignment.
Step 3 Disable dynamic power assignment by choosing Fixed under Tx Power Level Assignment and choosing a default transmit
power level from the drop-down list.
Step 4 Click Apply.
Step 5 Click Save Configuration.
Step 6 If you are overriding the default channel and power settings on a per radio basis, assign static channel and power settings
to each of the access point radios that are joined to the Cisco WLC.
Step 7 (Optional) Repeat this procedure for the network type that you did not select (802.11a/n/ac or 802.11b/g/n).
Step 2 Disable RRM for all 802.11a or 802.11b/g radios and set all channels to the default value by entering this command:
config {802.11a | 802.11b} channel global off
These parameters are supported in Cisco Client Extensions (CCX) v2 and later releases are designed to enhance
location accuracy and timeliness for participating CCX clients.
For the location features to operate properly, the access points must be configured for normal, monitor, or
FlexConnect mode. However, for FlexConnect mode, the access point must be connected to the Cisco WLC.
requests for a particular access point or client as well as radio measurement reports for a particular client from
the Cisco WLC CLI.
The Cisco WLC software improves the ability of the mobility services engine to accurately interpret the
location of a device through a CCXv4 feature called location-based services. The Cisco WLC issues a path-loss
request to a particular CCXv4 or v5 client. If the client chooses to respond, it sends a path-loss measurement
report to the Cisco WLC. These reports contain the channel and transmit power of the client.
Note Non-CCX and CCXv1 clients ignore the CCX measurement requests and do not participate in the radio
measurement activity.
Location Calibration
For CCX clients that need to be tracked more closely (for example, when a client calibration is performed),
the Cisco WLC can be configured to command the access point to send unicast measurement requests to these
clients at a configured interval and whenever a CCX client roams to a new access point. These unicast requests
can be sent out more often to these specific CCX clients than the broadcast measurement requests, which are
sent to all clients. When location calibration is configured for non-CCX and CCXv1 clients, the clients are
forced to disassociate at a specified interval to generate location measurements.
Step 1 Choose Wireless > 802.11a/n/ac or 802.11b/g/n > Network to open the 802.11a/n/ac (or 802.11b/g/n) Global Parameters
page.
Step 2 Under CCX Location Measurement, select the Mode check box to globally enable CCX radio management. This parameter
causes the access points connected to this Cisco WLC to issue broadcast radio measurement requests to clients running
CCX v2 or later releases. The default value is disabled (or unselected).
Step 3 If you selected the Mode check box in the previous step, enter a value in the Interval text box to specify how often the
access points are to issue the broadcast radio measurement requests.
The range is 60 to 32400 seconds.
The default is 60 seconds.
A Radio
B Radio
• To see the status of radio measurement requests for a particular client, enter this command:
show client ccx rm client_mac status
Information similar to the following appears:
• To see radio measurement reports for a particular client, enter these commands:
show client ccx rm client_mac report beacon—Shows the beacon report for the specified client.
show client ccx rm client_mac report chan-load—Shows the channel-load report for the specified
client.
show client ccx rm client_mac report noise-hist—Shows the noise-histogram report for the specified
client.
show client ccx rm client_mac report frame—Shows the frame report for the specified client.
• To see the clients configured for location calibration, enter this command:
show client location-calibration summary
• To see the RSSI reported for both antennas on each access point that heard the client, enter this command:
show client detail client_mac
Cisco CleanAir is different and can positively identify not only the source of the noise but also its location
and potential impact to a WLAN. Having this information allows you to consider the noise within the context
of the network and make intelligent and, where possible, proactive decisions. For CleanAir, two types of
interference events are common:
• Persistent interference
• Spontaneous interference
Persistent interference events are created by devices that are stationary in nature and have intermittent but
largely repeatable patterns of interference. For example, consider the case of a microwave oven located in a
break room. Such a device might be active for only 1 or 2 minutes at a time. When operating, however, it can
be disruptive to the performance of the wireless network and associated clients. Using Cisco CleanAir, you
can positively identify the device as a microwave oven rather than indiscriminate noise. You can also determine
exactly which part of the band is affected by the device, and because you can locate it, you can understand
which access points are most severely affected. You can then use this information to direct RRM in selecting
a channel plan that avoids this source of interference for the access points within its range. Because this
interference is not active for a large portion of the day, existing RF management applications might attempt
to again change the channels of the affected access points. Persistent device avoidance is unique, however,
in that it remains in effect as long as the source of interference is periodically detected to refresh the persistent
status. The Cisco CleanAir system knows that the microwave oven exists and includes it in all future planning.
If you move either the microwave oven or the surrounding access points, the algorithm updates RRM
automatically.
Note Spectrum event-driven RRM can be triggered only by Cisco CleanAir-enabled access points in local mode.
Spontaneous interference is interference that appears suddenly on a network, perhaps jamming a channel or
a range of channels completely. The Cisco CleanAir spectrum event-driven RRM feature allows you to set a
threshold for air quality (AQ) that, if exceeded, triggers an immediate channel change for the affected access
point. Most RF management systems can avoid interference, but this information takes time to propagate
through the system. Cisco CleanAir relies on AQ measurements to continuously evaluate the spectrum and
can trigger a move within 30 seconds. For example, if an access point detects interference from a video camera,
it can recover by changing channels within 30 seconds of the camera becoming active. Cisco CleanAir also
identifies and locates the source of interference so that more permanent mitigation of the device can be
performed at a later time.
In the case of Bluetooth devices, Cisco CleanAir-enabled access points can detect and report interferences
only if the devices are actively transmitting. Bluetooth devices have extensive power save modes. For example,
interference can be detected when data or voice is being streamed between the connected devices.
Persistent Devices
Some interference devices such as outdoor bridges and Microwave Ovens only transmit when needed. These
devices can cause significant interference to the local WLAN due to short duration and periodic operation
remain largely undetected by normal RF management metrics. With CleanAir the RRM DCA algorithm can
detect, measure, register and remember the impact and adjust the DCA algorithm. This minimizes the use of
channels affected by the persistent devices in the channel plan local to the interference source. Cisco CleanAir
detects and stores the persistent device information in the Cisco WLC and this information is used to mitigate
interfering channels.
Note Suppose you have two APs, one in the FlexConnect mode and the other in the monitor
mode. Also suppose that you have created a profile enabling EAP attack against 802.1x
auth. The Airmagnet (AM) tool, which can generate different types of attacks, fails to
generate any attack even if you have provided valid AP MAC and STA MAC addresses.
But if the AP MAC and STA MAC addresses in the AM tool are swapped, that is, the
AP MAC address is specified in the STA MAC field and the STA MAC address is
specified in the AP MAC field, then the tool is able to generate attacks, which the AP
in the Monitor mode is also able to detect.
Note The access point does not participate in AQ HeatMap in Prime Infrastructure.
• SE-Connect—This mode enables a user to connect a Spectrum Expert application running on an external
Microsoft Windows XP or Vista PC to a Cisco CleanAir-enabled access point in order to display and
analyze detailed spectrum data. The Spectrum Expert application connects directly to the access point,
bypassing the . An access point in SE-Connect mode does not provide any Wi-Fi, RF, or spectrum data
to the . All CleanAir system functionality is suspended while the AP is in this mode, and no clients are
served. This mode is intended for remote troubleshooting only. Up to three active Spectrum Expert
connections are possible.
Step 1 Choose Wireless > 802.11a/n/ac or 802.11b/g/n > CleanAir to open the 802.11a (or 802.11b) > CleanAir page.
Step 2 Select the CleanAir check box to enable Cisco CleanAir functionality on the 802.11a/n or 802.11b/g/n network, or
unselect it to prevent the Cisco WLC from detecting spectrum interference. By default, the value is not selected.
Step 3 Select the Report Interferers check box to enable the Cisco CleanAir system to report any detected sources of interference,
or unselect it to prevent the Cisco WLC from reporting interferers. The default value is selected.
Note Device Security alarms, Event Driven RRM, and the Persistence Device Avoidance algorithm do not work if
Report Interferers are disabled.
Step 4 Select the Persistent Device Propagation check box to enable propagation of information about persistent devices that
can be detected by CleanAir. Persistent device propagation enables you to propagate information about persistent devices
to the neighboring access points connected to the same Cisco WLC. Persistent interferers are present at the location and
interfere with the WLAN operations even if they are not detectable at all times.
Step 5 Ensure that any sources of interference that need to be detected and reported by the Cisco CleanAir system appear in the
Interferences to Detect box and any that do not need to be detected appear in the Interferences to Ignore box. Use the >
and < buttons to move interference sources between these two boxes. By default, all interference sources are detected.
The possible sources of interference that you can choose are as follows:
• Bluetooth Paging Inquiry—A Bluetooth discovery (802.11b/g/n only)
• Bluetooth Sco Acl—A Bluetooth link (802.11b/g/n only)
• Generic DECT—A digital enhanced cordless communication (DECT)-compatible phone
• Generic TDD—A time division duplex (TDD) transmitter
• Generic Waveform—A continuous transmitter
Note Access points that are associated to the Cisco WLC send interference reports only for the interferers that appear
in the Interferences to Detect box. This functionality allows you to filter out interferers that you do not want as
well as any that may be flooding the network and causing performance problems for the Cisco WLC or Prime
Infrastructure. Filtering allows the system to resume normal performance levels.
Step 6 Configure Cisco CleanAir alarms as follows:
a) Select the Enable AQI (Air Quality Index) Trap check box to enable the triggering of air quality alarms, or unselect
the box to disable this feature. The default value is selected.
b) If you selected the Enable AQI Trap check box in Step a, enter a value between 1 and 100 (inclusive) in the AQI
Alarm Threshold text box to specify the threshold at which you want the air quality alarm to be triggered. When the
air quality falls below the threshold level, the alarm is triggered. A value of 1 represents the worst air quality, and
100 represents the best. The default value is 35.
c) Enter the AQI Alarm Threshold (1 to 100) that you want to set. An alarm is generated when the air quality reaches
a threshold value. The default is 35. Valid range is from 1 and 100.
d) Select the Enable trap for Unclassified Interferences check box to enable the AQI alarm to be generated upon
detection of unclassified interference beyond the severity threshond specified in the AQI Alarm Threshold.
Unclassified interferences are interferences that are detected but do not correspond to any of the identifiable interference
types.
e) Enter the Threshold for Unclassified category trap (1 to 99). Enter a value from 1 and 99. The default is 20. This
is the severity index threshold for an unclassified interference category.
f) Select the Enable Interference Type Trap check box to trigger interferer alarms when the Cisco WLC detects
specified device types, or unselect it to disable this feature. The default value is selected
g) Make sure that any sources of interference that need to trigger interferer alarms appear in the Trap on These Types
box and any that do not need to trigger interferer alarms appear in the Do Not Trap on These Types box. Use the >
and < buttons to move interference sources between these two boxes. By default, all interference sources trigger
interferer alarms.
For example, if you want the Cisco WLC to send an alarm when it detects a jamming device, select the Enable
Interference Type Trap check box and move the jamming device to the Trap on These Types box.
Step 1 Configure Cisco CleanAir functionality on the 802.11 network by entering this command:
config {802.11a | 802.11b} cleanair {enable | disable} all
If you disable this feature, the Cisco WLC does not receive any spectrum data. The default value is enable.
Step 3 Configure interference detection and specify sources of interference that need to be detected by the Cisco CleanAir
system by entering this command:
config {802.11a | 802.11b} cleanair device {enable | disable} type
where you choose the type as one of the following:
• 802.11-fh—An 802.11 frequency-hopping device (802.11b/g/n only)
• 802.11-inv—A device using spectrally inverted Wi-Fi signals
• 802.11-nonstd—A device using nonstandard Wi-Fi channels
• 802.15.4—An 802.15.4 device (802.11b/g/n only)
• all—All interference device types (this is the default value)
Note Access points that are associated to the Cisco WLC send interference reports only for the interference types
specified in this command. This functionality allows you to filter out interferers that may be flooding the network
and causing performance problems for the Cisco WLC or Prime Infrastructure. Filtering allows the system to
resume normal performance levels.
Step 4 Configure the triggering of air quality alarms by entering this command:
config {802.11a | 802.11b} cleanair alarm air-quality {enable | disable}
The default value is enabled.
Step 5 Specify the threshold at which you want the air quality alarm to be triggered by entering this command:
config {802.11a | 802.11b} cleanair alarm air-quality threshold threshold
where threshold is a value between 1 and 100 (inclusive). When the air quality falls below the threshold level, the alarm
is triggered. A value of 1 represents the worst air quality, and 100 represents the best. The default value is 35.
Step 7 Specify sources of interference that trigger alarms by entering this command:
config {802.11a | 802.11b} cleanair alarm device type {enable | disable} where you choose the type as one of the
following:
• 802.11-fh—An 802.11 frequency-hopping device (802.11b/g/n only)
• 802.11-inv—A device using spectrally inverted Wi-Fi signals
• 802.11-nonstd—A device using nonstandard Wi-Fi channels
• 802.15.4—An 802.15.4 device (802.11b/g/n only)
• all—All interference device types (this is the default value)
• bt-discovery—A Bluetooth discovery (802.11b/g/n only)
Step 8 Configure the triggering of air quality alarms for unclassified devices by entering this command:
config {802.11a | 802.11b} cleanair alarm unclassified {enable | disable}
Step 9 Specify the threshold at which you want the air quality alarm to be triggered for unclassified devices by entering this
command:
config {802.11a | 802.11b} cleanair alarm unclassified threshold threshold
where threshold is a value from 1 and 99 (inclusive). When the air quality falls below the threshold level, the alarm is
triggered. A value of 1 represents the worst air quality, and 100 represents the best. The default value is 35.
Step 10 Trigger spectrum event-driven radio resource management (RRM) to run when a Cisco CleanAir-enabled access point
detects a significant level of interference by entering these commands:
config advanced {802.11a | 802.11b} channel cleanair-event {enable | disable}—Enables or disables spectrum
event-driven RRM. The default value is disabled.
config advanced {802.11a | 802.11b} channel cleanair-event sensitivity {low | medium | high | custom}—Specifies
the threshold at which you want RRM to be triggered. When the interference level for the access point rises above the
threshold level, RRM initiates a local dynamic channel assignment (DCA) run and changes the channel of the affected
access point radio if possible to improve network performance. Low represents a decreased sensitivity to changes in the
environment while high represents an increased sensitivity. You can also set the sensitivity to a custom level of your
choice. The default value is medium.
config advanced {802.11a | 802.11b} channel cleanair-event sensitivity threshold thresholdvalue—If you set the
threshold sensitivity as custom, you must set a custom threshold value. The default is 35.
Step 13 See the Cisco CleanAir configuration for the 802.11a/n or 802.11b/g/n network by entering this command:
show {802.11a | 802.11b} cleanair config
Step 14 See the spectrum event-driven RRM configuration for the 802.11a/n/ac or 802.11b/g/n network by entering this command:
show advanced {802.11a | 802.11b} channel
Information similar to the following appears:
Step 1 Choose Wireless > Access Points > Radios > 802.11a/n/ac or 802.11b/g/n to open the 802.11a/n/ac (or 802.11b/g/n)
Radios page.
Step 2 Hover your cursor over the blue drop-down arrow for the desired access point and click Configure. The 802.11a/n/ac
(or 802.11b/g/n) Cisco APs > Configure page appears.
The CleanAir Capable field shows whether this access point can support CleanAir functionality. If it can, go to the next
step to enable or disable CleanAir for this access point. If the access point cannot support CleanAir functionality, you
cannot enable CleanAir for this access point.
Note By default, the Cisco CleanAir functionality is enabled on the
radios.
Step 3 Enable Cisco CleanAir functionality for this access point by choosing Enable from the CleanAir Status drop-down list.
To disable CleanAir functionality for this access point, choose Disable. The default value is Enable. This setting overrides
the global CleanAir configuration for this access point.
The Number of Spectrum Expert Connections text box shows the number of Spectrum Expert applications that are
currently connected to the access point radio. Up to three active connections are possible.
Note You can create a filter to make the 802.11a/n/ac Radios page or the 802.11b/g/n Radios page show only access
point radios that have a specific Cisco CleanAir status (such as UP, DOWN, ERROR, or N/A). This feature is
especially useful if your list of access point radios spans multiple pages, preventing you from viewing them all
at once. To create a filter, click Change Filter to open the Search AP dialog box, select one or more of the
CleanAir Status check boxes, and click Find. Only the access point radios that match your search criteria appear
on the 802.11a/n/ac Radios page or the 802.11b/g/n Radios page, and the Current Filter parameter at the top of
the page specifies the filter used to generate the list (for example, CleanAir Status: UP).
Step 1 Configure Cisco CleanAir functionality for a specific access point by entering this command:
config {802.11a | 802.11b} cleanair {enable | disable}Cisco_AP
Step 3 See the Cisco CleanAir configuration for a specific access point on the 802.11a/n/ac or 802.11b/g/n network by entering
this command:
show ap config {802.11a | 802.11b} Cisco_AP
Information similar to the following appears:
Cisco AP Identifier.............................. 0
Cisco AP Name.................................... CISCO_AP3500
...
Spectrum Management Information
Spectrum Management Capable.............. Yes
Spectrum Management Admin State.......... Enabled
Spectrum Management Operation State...... Up
Rapid Update Mode........................ Disabled
Spectrum Expert connection............... Disabled
Spectrum Sensor State................. Configured (Error code = 0)
Note See step 7 of Configuring Cisco CleanAir on an Access Point (GUI), on page 923 for descriptions of the spectrum
management operation states and the possible error codes for the spectrum sensor state.
Step 1 Choose Monitor > Cisco CleanAir > 802.11a/n or 802.11b/g/n > Interference Devices to open the CleanAir >
Interference Devices page.
This page shows the following information:
• AP Name—The name of the access point where the interference device is detected.
• Radio Slot #—Slot where the radio is installed.
• Interferer Type—Type of the interferer.
• Affected Channel—Channel that the device affects.
• Detected Time—Time at which the interference was detected.
• Severity—Severity index of the interfering device.
• Duty Cycle (%)—Proportion of time during which the interfering device was active.
• RSSI—Receive signal strength indicator (RSSI) of the access point.
Step 2 Click Change Filter to display the information about interference devices based on a particular criteria.
Step 3 Click Clear Filter to remove the filter and display the entire access point list.
You can create a filter to display the list of interference devices that are based on the following filtering parameters:
• Cluster ID—To filter based on the Cluster ID, select the check box and enter the Cluster ID in the text box next
to this field.
• AP Name—To filter based on the access point name, select the check box and enter the access point name in the
text box next to this field.
• Interferer Type—To filter based on the type of the interference device, select the check box and select the interferer
device from the options.
Select one of the interferer devices:
◦BT Link
◦MW Oven
◦802.11 FH
◦BT Discovery
◦TDD Transmit
◦Jammer
◦Continuous TX
◦DECT Phone
◦Video Camera
◦802.15.4
◦WiFi Inverted
◦WiFi Inv. Ch
◦SuperAG
◦Canopy
◦XBox
◦WiMax Mobile
◦WiMax Fixed
◦WiFi ACI
◦Unclassified
• Activity Channels
• Severity
Number Of Slots.................................. 2
AP Name.......................................... AP_1142_MAP
MAC Address...................................... c4:7d:4f:3a:35:38
Slot ID........................................ 1
Radio Type..................................... RADIO_TYPE_80211a
Sub-band Type.................................. All
Noise Information
. . ..
. . . .
Power Level.................................. 1
RTS/CTS Threshold............................ 2347
Fragmentation Threshold...................... 2346
Antenna Pattern.............................. 0
Step 1 Choose Monitor > Cisco CleanAir >Worst Air-Quality to open the CleanAir > Worst Air Quality Report page.
This page shows the air quality of both the 802.11a/n/ac and 802.11b/g/n radio bands. Specifically, it shows the following
information:
• AP Name—The name of the access point that reported the worst air quality for the 802.11 radio band.
• Channel Number—The radio channel with the worst reported air quality.
• Minimum Air Quality Index(1 to 100)—The minimum air quality for this radio channel. An air quality index
(AQI) value of 100 is the best, and 1 is the worst.
• Average Air Quality Index(1 to 100)—The average air quality for this radio channel. An air quality index (AQI)
value of 100 is the best, and 1 is the worst.
• Interference Device Count—The number of interferers detected by the radios on the 802.11 radio band.
Step 2 See a list of persistent sources of interference for a specific access point radio as follows:
a) Choose Wireless > Access Points > Radios > 802.11a/n/ac or 802.11b/g/n to open the 802.11a/n/ac (or 802.11b/g/n)
Radios page.
b) Hover your cursor over the blue drop-down arrow for the desired access point radio and click CleanAir-RRM. The
802.11a/n/ac (or 802.11b/g/n) Cisco APs > Access Point Name > Persistent Devices page appears. This page lists
the device types of persistent sources of interference detected by this access point radio. It also shows the channel
on which the interference was detected, the percentage of time that the interferer was active (duty cycle), the received
signal strength (RSSI) of the interferer, and the day and time when the interferer was last detected.
Viewing the Worst Air Quality Information for all Access Points on a Radio Band (CLI)
See information for the 802.11a/n/ac or 802.11b/g/n access point with the worst air quality by entering this
command:
show {802.11a | 802.11b} cleanair air-quality worst
Viewing the Air Quality for an Access Point on a Radio Band (CLI)
See the air quality information for a specific access point on the 802.11 radio band by entering this command:
show {802.11a | 802.11b} cleanair air-quality Cisco_AP
Viewing the Air Quality for an Access Point by Device Type (CLI)
• See information for all of the interferers detected by a specific access point on the 802.11a/n/ac or
802.11b/g/n radio band by entering this command:
show {802.11a | 802.11b} cleanair device ap Cisco_AP
• See information for all of the interferers of a specific device type on the 802.11a/n or 802.11b/g/n radio
band by entering this command:
show {802.11a | 802.11b} cleanair device type type
where you choose type as one of the following:
◦802.11-fh—An 802.11 frequency-hopping device (802.11b/g/n only)
◦802.11-inv—A device using spectrally inverted Wi-Fi signals
◦802.11-nonstd—A device using nonstandard Wi-Fi channels
◦802.15.4—An 802.15.4 device (802.11b/g/n only)
◦all—All interference device types (this is the default value)
◦bt-discovery—A bluetooth discovery (802.11b/g/n only)
◦bt-link—A bluetooth link (802.11b/g/n only)
◦canopy—A canopy bridge device
◦cont-tx—A continuous transmitter
◦dect-like—A digital enhanced cordless communication (DECT)-compatible phone
◦jammer—A jamming device
◦mw-oven—A microwave oven (802.11b/g/n only)
◦superag—An 802.11 SuperAG device
◦tdd-tx—A time division duplex (TDD) transmitter
◦video camera—An analog video camera
◦wimax-fixed—A WiMAX fixed device
◦wimax-mobile—A WiMAX mobile device
Note The Cisco Aironet Access Point Module for Wireless Security and Spectrum Intelligence (WSSI) for the
Cisco Aironet 3600 Series Access Point tightly couples data connectivity, spectrum analysis, and security
threat detection and mitigation into a single, multipurpose access point. With WSSI you have to use
Metageek Chanalyzer Pro with CleanAir support and not Spectrum expert for wIPS, CleanAir and spectrum
analysis.
Step 1 Ensure that Cisco CleanAir functionality is enabled for the access point that will be connected to the Spectrum Expert
console.
Step 2 Configure the access point for SE-Connect mode using the Cisco WLC GUI or CLI.
Note The SE-Connect mode is set for the entire access point, not just a single radio. However, the Spectrum Expert
console connects to a single radio at a time.
If you are using the Cisco WLC GUI, follow these steps:
a) Choose Wireless > Access Points > All APs to open the All APs page.
b) Click the name of the desired access point to open the All APs > Details for page.
c) Choose SE-Connect from the AP Mode drop-down list. This mode is available only for access points that are capable
of supporting Cisco CleanAir functionality. For the SE-Connect mode to appear as an available option, the access
point must have at least one spectrum-capable radio in the Enable state.
d) Click Apply to commit your changes.
e) Click OK when prompted to reboot the access point.
If you are using the CLI, follow these steps:
a) To configure the access point for SE-Connect mode, enter this command:
config ap mode se-connect Cisco_AP
b) When prompted to reboot the access point, enter Y.
c) To verify the SE-Connect configuration status for the access point, enter this command:
show ap config {802.11a | 802.11b} Cisco_AP
Information similar to the following appears:
Cisco AP Identifier.............................. 0
Cisco AP Name.................................... CISCO_AP3500
...
Spectrum Management Information
Spectrum Management Capable.............. Yes
Spectrum Management Admin State.......... Enabled
Spectrum Management Operation State...... Up
Rapid Update Mode........................ Disabled
Spectrum Expert connection............... Enabled
Spectrum Sensor State.................. Configured (Error code = 0)
Step 3 On the Windows PC, access the Cisco Software Center from this URL:
http://www.cisco.com/cisco/software/navigator.html
Step 4 Click Product > Wireless > Cisco Spectrum Intelligence > Cisco Spectrum Expert > Cisco Spectrum Expert Wi-Fi,
and then download the Spectrum Expert 4.0 executable (*.exe) file.
Step 5 Run the Spectrum Expert application on the PC.
Step 6 When the Connect to Sensor dialog box appears, enter the IP address of the access point, choose the access point radio,
and enter the 16-byte network spectrum interface (NSI) key to authenticate. The Spectrum Expert application opens a
TCP/IP connection directly to the access point using the NSI protocol.
Note The access point must be a TCP server listening on ports 37540 for 2.4 GHz and 37550 for 5 GHz frequencies.
These ports must be opened for the spectrum expert application to connect to the access point using the NSI
protocol.
Note On the Cisco WLC GUI, the NSI key appears in the Network Spectrum Interface Key field (below the Port
Number field) on the All APs > Details for page. To view the NSI key from the Cisco WLC CLI, enter the show
ap config {802.11a | 802.11b} Cisco_AP command.
When an access point in SE-Connect mode joins a Cisco WLC, it sends a Spectrum Capabilities notification message,
and the Cisco WLC responds with a Spectrum Configuration Request. The request contains the 16-byte random NSI key
generated by the Cisco WLC for use in NSI authentication. The Cisco WLC generates one key per access point, which
the access point stores until it is rebooted.
Note You can establish up to three Spectrum Expert console connections per access point radio. The Number of
Spectrum Expert Connections text box on the 802.11a/n/ac (or 802.11b/g/n) Cisco APs > Configure page of
the Cisco WLC GUI shows the number of Spectrum Expert applications that are currently connected to the
access point radio.
Step 7 Verify that the Spectrum Expert console is connected to the access point by selecting the Slave Remote Sensor text box
in the bottom right corner of the Spectrum Expert application. If the two devices are connected, the IP address of the
access point appears in this text box.
Step 8 Use the Spectrum Expert application to view and analyze spectrum data from the access point.
The controller software has a more robust fault tolerance methodology to FlexConnect access points. In
previous releases, whenever a FlexConnect access point disassociates from a controller, it moves to the
standalone mode. The clients that are centrally switched are disassociated. However, the FlexConnect access
point continues to serve locally switched clients. When the FlexConnect access point rejoins the controller
(or a standby controller), all clients are disconnected and are authenticated again. This functionality has been
enhanced and the connection between the clients and the FlexConnect access points are maintained intact and
the clients experience seamless connectivity. When both the access point and the controller have the same
configuration, the connection between the clients and APs is maintained.
After the client connection has been established, the controller does not restore the original attributes of the
client. The client username, current rate and supported rates, and listen interval values are reset to the default
values only after the session timer expires.
There is no deployment restriction on the number of FlexConnect access points per location. Multiple
FlexConnect groups can be defined in a single location.
The controller can send multicast packets in the form of unicast or multicast packets to the access point. In
FlexConnect mode, the access point can receive multicast packets only in unicast form.
FlexConnect access points support a 1-1 network address translation (NAT) configuration. They also support
port address translation (PAT) for all features except true multicast. Multicast is supported across NAT
boundaries when configured using the Unicast option. FlexConnect access points also support a many-to-one
NAT/PAT boundary, except when you want true multicast to operate for all centrally switched WLANs.
Note Although NAT and PAT are supported for FlexConnect access points, they are not supported on the
corresponding controller. Cisco does not support configurations in which the controller is behind a
NAT/PAT boundary.
VPN and PPTP are supported for locally switched traffic if these security types are accessible locally at the
access point.
FlexConnect access points support multiple SSIDs.
Workgroup bridges and Universal Workgroup bridges are supported on FlexConnect access points for locally
switched clients.
FlexConnect supports IPv6 clients by bridging the traffic to local VLAN, similar to IPv4 operation. FlexConnect
supports Client Mobility for a group of up to 100 access points.
In the release 8.0, the access point no longer needs to reboot when moving from local to FlexConnect mode.
Note For the Cisco Flex 7500 Series Wireless LAN Controller, auto convert mode is available on the CLI. The
auto convert mode triggers the change on all the connected APs. The change of the mode from Local to
FlexConnect and the reboot works in conjunction with the auto convert mode for the Cisco Flex 7500
Series WLC.
Note When AP is changed from local to FlexConnect it will not reboot, but when it is changed from FlexConnect
to local it reboots and displays the following error message, "Warning: Changing AP Mode will reboot
the AP and will rejoin the controller afer a few minutes. Are you sure you want to continue?" but CLI
remains the same. Changing the AP's mode will also cause the AP to reboot.
Note Once the access point is rebooted after downloading the latest controller software, it must be converted
to the FlexConnect mode. This can be done using the GUI or CLI.
A FlexConnect access point can learn the controller IP address in one of these ways:
• If the access point has been assigned an IP address from a DHCP server, it can discover a controller
through the regular CAPWAP or LWAPP discovery process.
Note OTAP is no longer supported on the controllers with 6.0.196.0 and later releases.
• If the access point has been assigned a static IP address, it can discover a controller through any of the
discovery process methods except DHCP option 43. If the access point cannot discover a controller
through Layer 3 broadcast, we recommend DNS resolution. With DNS, any access point with a static
IP address that knows of a DNS server can find at least one controller.
• If you want the access point to discover a controller from a remote network where CAPWAP or LWAPP
discovery mechanisms are not available, you can use priming. This method enables you to specify
(through the access point CLI) the controller to which the access point is to connect.
Note For more information about how access points find controllers, see the controller deployment
guide at:
http://www.cisco.com/c/en/us/td/docs/wireless/technology/controller/deployment/guide/dep.html.
When a FlexConnect access point can reach the controller (referred to as the connected mode), the controller
assists in client authentication. When a FlexConnect access point cannot access the controller, the access point
enters the standalone mode and authenticates clients by itself.
Note The LEDs on the access point change as the device enters different FlexConnect modes. See the hardware
installation guide for your access point for information on LED patterns.
When a client associates to a FlexConnect access point, the access point sends all authentication messages to
the controller and either switches the client data packets locally (locally switched) or sends them to the
controller (centrally switched), depending on the WLAN configuration. With respect to client authentication
(open, shared, EAP, web authentication, and NAC) and data packets, the WLAN can be in any one of the
following states depending on the configuration and state of controller connectivity:
• central authentication, central switching—In this state, the controller handles client authentication, and
all client data is tunneled back to the controller. This state is valid only in connected mode.
• central authentication, local switching—In this state, the controller handles client authentication, and
the FlexConnect access point switches data packets locally. After the client authenticates successfully,
the controller sends a configuration command with a new payload to instruct the FlexConnect access
point to start switching data packets locally. This message is sent per client. This state is applicable only
in connected mode.
Note For the FlexConnect local switching, central authentication deployments, if there is a
passive client with a static IP address, it is recommended to disable the Learn Client IP
Address feature under the WLAN > Advanced tab.
• local authentication, local switching—In this state, the FlexConnect access point handles client
authentication and switches client data packets locally. This state is valid in standalone mode and
connected mode.
In connected mode, the access point provides minimal information about the locally authenticated client
to the controller. The following information is not available to the controller:
◦Policy type
◦Access VLAN
◦VLAN name
◦Supported rates
◦Encryption cipher
Local authentication is useful where you cannot maintain a remote office setup of a minimum
bandwidth of 128 kbps with the round-trip latency no greater than 100 ms and the maximum
transmission unit (MTU) no smaller than 576 bytes. In local authentication, the authentication
capabilities are present in the access point itself. Local authentication reduces the latency
requirements of the branch office.
Note Local authentication can only be enabled on the WLAN of a FlexConnect access point
that is in local switching mode.
Notes about local authentication are as follows:
Note When locally switched clients that are connected to a FlexConnect access point renew
the IP addresses, on joining back, the client continues to stay in the run state. These
clients are not reauthenticated by the controller.
• authentication down, switch down—In this state, the WLAN disassociates existing clients and stops
sending beacon and probe requests. This state is valid in both standalone mode and connected mode.
• authentication down, local switching—In this state, the WLAN rejects any new clients trying to
authenticate, but it continues sending beacon and probe responses to keep existing clients alive. This
state is valid only in standalone mode.
When a FlexConnect access point enters standalone mode, WLANs that are configured for open, shared,
WPA-PSK, or WPA2-PSK authentication enter the “local authentication, local switching” state and continue
new client authentications. In controller software release 4.2 or later releases, this configuration is also correct
for WLANs that are configured for 802.1X, WPA-802.1X, WPA2-802.1X, or CCKM, but these authentication
types require that an external RADIUS server be configured. You can also configure a local RADIUS server
on a FlexConnect access point to support 802.1X in a standalone mode or with local authentication.
Other WLANs enter either the “authentication down, switching down” state (if the WLAN was configured
for central switching) or the “authentication down, local switching” state (if the WLAN was configured for
local switching).
When FlexConnect access points are connected to the controller (rather than in standalone mode), the controller
uses its primary RADIUS servers and accesses them in the order specified on the RADIUS Authentication
Servers page or in the config radius auth add CLI command (unless the server order is overridden for a
particular WLAN). However, to support 802.1X EAP authentication, FlexConnect access points in standalone
mode need to have their own backup RADIUS server to authenticate clients.
Note A controller does not use a backup RADIUS server. The controller uses the backup RADIUS server in
local authentication mode.
You can configure a backup RADIUS server for individual FlexConnect access points in standalone mode
by using the controller CLI or for groups of FlexConnect access points in standalone mode by using either
the GUI or CLI. A backup server configured for an individual access point overrides the backup RADIUS
server configuration for a FlexConnect.
When a FlexConnect access point enters standalone mode, it disassociates all clients that are on centrally
switched WLANs. For web-authentication WLANs, existing clients are not disassociated, but the FlexConnect
access point stops sending beacons when the number of associated clients reaches zero (0). It also sends
disassociation messages to new clients associating to web-authentication WLANs. Controller-dependent
activities, such as network access control (NAC) and web authentication (guest access), are disabled, and the
access point does not send any intrusion detection system (IDS) reports to the controller. Most radio resource
management (RRM) features (such as neighbor discovery; noise, interference, load, and coverage measurements;
use of the neighbor list; and rogue containment and detection) are disabled. However, a FlexConnect access
point supports dynamic frequency selection in standalone mode.
When web-authentication is used on FlexConnect access points at a remote site, the clients get the IP address
from the remote local subnet. To resolve the initial URL request, the DNS is accessible through the subnet's
default gateway. In order for the controller to intercept and redirect the DNS query return packets, these
packets must reach the controller at the data center through a CAPWAP connection. During the
web-authentication process, the FlexConnect access points allows only DNS and DHCP messages; the access
points forward the DNS reply messages to the controller before web-authentication for the client is complete.
After web-authentication for the client is complete, all the traffic is switched locally.
Note If your controller is configured for NAC, clients can associate only when the access point is in connected
mode. When NAC is enabled, you need to create an unhealthy (or quarantined) VLAN so that the data
traffic of any client that is assigned to this VLAN passes through the controller, even if the WLAN is
configured for local switching. After a client is assigned to a quarantined VLAN, all of its data packets
are centrally switched. See the Configuring Dynamic Interfaces section for information about creating
quarantined VLANs and the Configuring NAC Out-of-Band section for information about configuring
NAC out-of-band support.
When a FlexConnect access point enters into a standalone mode, the following occurs:
• The access point checks whether it is able to reach the default gateway via ARP. If so, it will continue
to try and reach the controller.
If the access point fails to establish the ARP, the following occurs:
• The access point attempts to discover for five times and if it still cannot find the controller, it tries to
renew the DHCP on the ethernet interface to get a new DHCP IP.
• The access point will retry for five times, and if that fails, the access point will renew the IP address of
the interface again, this will happen for three attempts.
• If the three attempts fail, the access point will fall back to the static IP and will reboot (only if the access
point is configured with a static IP).
• Reboot is done to remove the possibility of any unknown error the access point configuration.
Once the access point reestablishes a connection with the controller, it disassociates all clients, applies new
configuration information from the controller, and allows client connectivity again.
Restrictions on FlexConnect
• You can deploy a FlexConnect access point with either a static IP address or a DHCP address. In the
case of DHCP, a DHCP server must be available locally and must be able to provide the IP address for
the access point at bootup.
• FlexConnect supports up to four fragmented packets or a minimum 576-byte maximum transmission
unit (MTU) WAN link.
• Round-trip latency must not exceed 300 milliseconds (ms) between the access point and the controller,
and CAPWAP control packets must be prioritized over all other traffic. In cases where you cannot
achieve the 300 milliseconds round-trip latency, you can configure the access point to perform local
authentication.
• Client connections are restored only for locally switched clients that are in the RUN state when the
access point moves from standalone mode to connected mode. After the access point moves from the
standalone mode to the connected mode, the access point’s radio is also reset.
• The configuration on the controller must be the same between the time the access point went into
standalone mode and the time the access point came back to connected mode. Similarly, if the access
point is falling back to a secondary or backup controller, the configuration between the primary and
secondary or backup controller must be the same.
• A newly connected access point cannot be booted in FlexConnect mode.
• To use CCKM fast roaming with FlexConnect access points, you must configure FlexConnect Groups.
• NAC out-of-band integration is supported only on WLANs configured for FlexConnect central switching.
It is not supported for use on WLANs configured for FlexConnect local switching.
• The primary and secondary controllers for a FlexConnect access point must have the same configuration.
Otherwise, the access point might lose its configuration, and certain features (such as WLAN overrides,
VLANs, static channel number, and so on) might not operate correctly. In addition, make sure to duplicate
the SSID of the FlexConnect access point and its index number on both controllers.
• Do not connect access points in FlexConnect mode directly to a 2500 Series Controller.
• If you configure a FlexConnect access point with a syslog server configured on the access point, after
the access point is reloaded and the native VLAN other than 1, at time of initialization, few syslog
packets from the access point are tagged with VLAN ID 1. This is a known issue.
• MAC Filtering is not supported on FlexConnect access points in standalone mode. However, MAC
Filtering is supported on FlexConnect access points in connected mode with local switching and central
authentication. Also, Open SSID, MAC Filtering, and RADIUS NAC for a locally switched WLAN
with FlexConnect access points is a valid configuration where MAC is checked by ISE.
• FlexConnect does not support IPv6 ACLs, neighbor discovery caching, and DHCPv6 snooping of IPv6
NDP packets.
• FlexConnect does not display any IPv6 client addresses within the client detail page.
• FlexConnect Access Points with Locally Switched WLAN cannot perform IP Source Guard and prevent
ARP spoofing. For Centrally Switched WLAN, the wireless controller performs the IP Source Guard
and ARP Spoofing.
• To prevent ARP spoofing attacks in FlexConnect AP with Local Switching, we recommend that you
use ARP Inspection.
• When you enable local switching on WLAN for the Flexconnect APs, then APs perform local switching.
However, for the APs in local mode, central switching is performed.
• For Wi-Fi Protected Access version 2 (WPA2) in FlexConnect standalone mode or local-auth in connected
mode or CCKM fast-roaming in connected mode, only Advanced Encryption Standard (AES) is supported.
• For Wi-Fi Protected Access (WPA) in FlexConnect standalone mode or local-auth in connected mode
or CCKM fast-roaming in connected mode, only Temporal Key Integrity Protocol (TKIP) is supported.
• WPA2 with TKIP and WPA with AES is not supported in standalone mode, local-auth in connected
mode, and CCKM fast-roaming in connected mode.
• AVC is not supported on APs in FlexConnect local switched mode.
• Flexconnect access points in WIPS mode can significantly increase the bandwidth utilization depending
on the activity detected by the access points. If the rules have forensics enabled, the link utilization can
go up by almost 100kbps.
• Local authentication fall back is not supported when user is not available in the external RADIUS server.
• For WLAN configured for the FlexConnect AP in the local switching and local authentication,
synchronization of dot11 clients information is supported.
• It is not possible for the Cisco WLC to detect if an AP has dissociated and with that whether the radio
is in operational state or non-operational state.
When a FlexConnect AP dissociates from the Cisco WLC, the AP can still serve the clients with the
radios being operational; however, with all other AP modes, the radios go into non-operational state.
• When you apply a configuration change to a locally switched WLAN, the access point resets the radio,
causing associated client devices to disassociate (including the clients that are not associated with the
modified WLAN). However, this behavior does not occur if the modified WLAN is centrally switched.
We recommend that you modify the configuration only during a maintenance window. This is also
applicable when a centrally switched WLAN is changed to a locally switched WLAN.
Configuring FlexConnect
Note The configuration tasks must be performed in the order in which they are listed.
Step 1 Attach the access point that will be enabled for FlexConnect to a trunk or access port on the switch.
Note The sample configuration in this procedure shows the FlexConnect access point connected to a trunk port on
the switch.
Step 2 See the sample configuration in this procedure to configure the switch to support the FlexConnect access point.
In this sample configuration, the FlexConnect access point is connected to trunk interface FastEthernet 1/0/2 with native
VLAN 100. The access point needs IP connectivity on the native VLAN. The remote site has local servers/resources on
VLAN 101. A DHCP pool is created in the local switch for both VLANs in the switch. The first DHCP pool (NATIVE)
is used by the FlexConnect access point, and the second DHCP pool (LOCAL-SWITCH) is used by the clients when
they associate to a WLAN that is locally switched. The bolded text in the sample configuration shows these settings.
A sample local switch configuration is as follows:
The controller configuration for FlexConnect consists of creating centrally switched and locally switched
WLANs. This table shows three WLAN scenarios.
Configuring the Controller for FlexConnect for a Centrally Switched WLAN Used for Guest Access
If you are using an external web server, you must configure a preauthentication access control list (ACL) on the
WLAN for the server and then choose this ACL as the WLAN preauthentication ACL on the Layer 3 tab.
Note Do not enable ip-learn on flex local switched WLAN. When several sites use similar local subnets or overlapping
subnets that are terminated on the same WLC, you will see ip-theft false positives. If ip-theft exclusion is enabled
on the WLC, the clients might get blacklisted or a similar message is displayed to convey the feature behavior.
To configure the controller for FlexConnect in a centrally switched WLAN:
a) In the General tab, select the Status check box to enable the WLAN.
b) If you have enabled NAC and have created a quarantined VLAN and want to use it for this WLAN, select the interface
from the Interface/Interface Group(G) drop-down list in the General tab.
c) In the Security > Layer 2 tab, choose WPA+WPA2 from the Layer 2 Security drop-down list and then set the
WPA+WPA2 parameters as required.
To configure the controller for FlexConnect in a locally switched WLAN:
a) In the General tab, select the Status check box to enable the WLAN.
b) If you have enabled NAC and have created a quarantined VLAN and want to use it for this WLAN, select the interface
from the Interface/Interface Group(G) drop-down list in the General tab.
c) In the Security > Layer 2 tab, select WPA+WPA2 from the Layer 2 Security drop-down list and then set the
WPA+WPA2 parameters as required.
d) In the Advanced tab:
• Select or unselect the FlexConnect Local Switching check box to enable or disable local switching of client
data associated with the APs in FlexConnect mode.
Note The guidelines and limitations for this feature are as follows:
• When you enable local switching, any FlexConnect access point that advertises this WLAN is
able to locally switch data packets (instead of tunneling them to the controller).
• When you enable FlexConnect local switching, the controller is enabled to learn the client’s IP
address by default. However, if the client is configured with Fortress Layer 2 encryption, the
controller cannot learn the client’s IP address, and the controller periodically drops the client.
Disable the client IP address learning feature so that the controller maintains the client connection
without waiting to learn the client’s IP address. The ability to disable this option is supported
only with FlexConnect local switching; it is not supported with FlexConnect central switching.
• For FlexConnect access points, the interface mapping at the controller for WLANs that is
configured for FlexConnect Local Switching is inherited at the access point as the default VLAN
tagging. This mapping can be changed per SSID and per FlexConnect access point.
Non-FlexConnect access points tunnel all traffic back to the controller, and VLAN tagging is
determined by each WLAN’s interface mapping.
• Select or unselect the FlexConnect Local Auth check box to enable or disable local authentication for the
WLAN.
• Select or unselect the Learn Client IP Address check box to enable or disable the IP address of the client to
be learned.
• Select or unselect the VLAN based Central Switching check box to enable or disable central switching on a
locally switched WLAN based on AAA overridden VLAN.
Note These are the guidelines and limitations for this feature:
• Multicast on overridden interfaces is not supported.
• This feature is available only on a per-WLAN basis, where the WLAN is locally switched.
• IPv6 ACLs, CAC, NAC, and IPv6 are not supported.
• IPv4 ACLs are supported only with VLAN-based central switching enabled and applicable only
to central switching clients on the WLAN.
• This feature is applicable to APs in FlexConnect mode in locally switched WLANs.
• This feature is not applicable to APs in Local mode.
• This feature is not supported on APs in FlexConnect mode in centrally switched WLANs.
• This feature is supported on central authentication only.
• This features is not supported on web authentication security clients.
• Layer 3 roaming for local switching clients is not supported.
• Select or unselect the Central DHCP Processing check box to enable or disable the feature. When you enable
this feature, the DHCP packets received from AP are centrally switched to the controller and then forwarded
to the corresponding VLAN based on the AP and the SSID.
• Select or unselect the Override DNS check box to enable or disable the overriding of the DNS server address
on the interface assigned to the locally switched WLAN. When you override DNS in centrally switched WLANs,
the clients get their DNS server IP address from the AP, not from the controller.
• Select or unselect the NAT-PAT check box to enable or disable Network Address Translation (NAT) and Port
Address Translation (PAT) on locally switched WLANs. You must enable Central DHCP Processing to enable
NAT and PAT.
Note When you enable FlexConnect local switching, the controller waits to learn the client
IP address by default. However, if the client is configured with Fortress Layer 2
encryption, the controller cannot learn the client IP address, and the controller periodically
drops the client. Use the config wlan flexconnect learn-ipaddr wlan_id disable
command to disable the client IP address learning feature so that the controller maintains
the client connection without waiting to learn the client’s IP address. The ability to
disable this feature is supported only with FlexConnect local switching; it is not supported
with FlexConnect central switching. To enable this feature, enter the config wlan
flexconnect learn-ipaddr wlan_id enable command.
Note When a WLAN is locally switched (LS), you must use the config wlan flexconnect
learn-ipaddr wlan-id {enable | disable} command. When the WLAN is centrally
switched (CS), you must use the config wlan learn-ipaddr-cswlan wlan-id {enable |
disable} command.
• config wlan flexconnect local-switching wlan_id {enable | disable}—Configures the WLAN for central
switching.
• config wlan flexconnect vlan-central-switching wlan_id {enable | disable}—Configures central
switching on a locally switched WLAN based on an AAA overridden VLAN.
The guidelines and limitations for this feature are as follows:
• Multicast on overridden interfaces is not supported.
• This feature is available only on a per-WLAN basis, where the WLAN is locally switched.
• IPv6 ACLs, CAC, NAC, and IPv6 are not supported.
• IPv4 ACLs are supported only with VLAN-based central switching enabled and applicable only
to central switching clients on the WLAN.
• This feature is applicable to APs in FlexConnect mode in locally switched WLANs.
• This feature is not applicable to APs in Local mode.
• This feature is not supported on APs in FlexConnect mode in centrally switched WLANs.
• This feature is supported on central authentication only.
• This features is not supported on web authentication security clients.
• Layer 3 roaming for local switching clients is not supported.
Note The AP will reboot when you change the AP behavior from Flexconnect to Local.
Step 4 Click Apply to commit your changes and to cause the access point to reboot.
Step 5 Choose the FlexConnect tab to open the All APs > Details for (FlexConnect) page.
If the access point belongs to a FlexConnect group, the name of the group appears in the FlexConnect Name text box.
Step 6 To configure WLAN VLAN mapping, choose from the following options in the drop-down list:
• Make AP Specific
• Remove AP Specific
Step 7 Select the VLAN Support check box and enter the number of the native VLAN on the remote network (such as 100)
in the Native VLAN ID text box.
Note By default, a VLAN is not enabled on the FlexConnect access point. After FlexConnect is enabled, the access
point inherits the VLAN ID associated to the WLAN. This configuration is saved in the access point and received
after the successful join response. By default, the native VLAN is 1. One native VLAN must be configured per
FlexConnect access point in a VLAN-enabled domain. Otherwise, the access point cannot send and receive
packets to and from the controller.
Note If PMIPv6 MAG on FlexConnect AP is configured, VLAN Support can be checked or unchecked on the
FlexConnect AP. If you check the VLAN Support check box, enter the number of the native VLAN on the
remote network in the Native VLAN ID text box.
Note To preserve the VLAN mappings in the access point after an upgrade or downgrade, it is necessary that the
access point join is restricted to the controller for which it is primed. That is, no other discoverable controller
with a different configuration should be available by other means. Similarly, at the time the access point joins,
if it moves across controllers that have different VLAN mappings, the VLAN mappings at the access point may
get mismatched.
Note For Cisco 1140 access point, when the native VLAN ID is set, it disconnects and joins back the Cisco 8500
series wireless controller. And after resuming the admin mode for the AP, is disabled.
Step 8 Click Apply. The access point temporarily loses its connection to the controller while its Ethernet port is reset.
Step 9 Click the name of the same access point and then click the FlexConnect tab.
Step 10 Click VLAN Mappings to open the All APs > Access Point Name > VLAN Mappings page.
Step 11 Enter the number of the VLAN from which the clients will get an IP address when doing local switching (VLAN 101,
in this example) in the VLAN ID text box.
Step 12 To configure Web Authentication ACLs, do the following:
a) Click the External WebAuthentication ACLs link to open the ACL mappings page. The ACL Mappings page lists
details of WLAN ACL mappings and web policy ACLs.
b) In the WLAN Id box, enter the WLAN ID.
c) From the WebAuth ACL drop-down list, choose the FlexConnect ACL.
Note To create a FlexConnect ACL, choose Wireless > FlexConnect Groups > FlexConnect ACLs, click New,
enter the FlexConnect ACL name, and click Apply.
d) Click Add.
e) Click Apply.
Step 13 To configure Local Split ACLs:
a) Click the Local Split ACLs link to open the ACL Mappings page.
b) In the WLAN Id box, enter the WLAN ID.
c) From the Local-Split ACL drop-down list, choose the FlexConnect ACL.
Note To create a FlexConnect ACL, choose Wireless > FlexConnect Groups > FlexConnect ACLs, click New,
enter the FlexConnect ACL name, and click Apply.
If a client that connects over a WAN link associated with a centrally switched WLAN has to send some traffic to a
device present in the local site, the client has to send traffic over CAPWAP to the controller and then get the same
traffic back to the local site either over CAPWAP or using some offband connectivity. This process unnecessarily
consumes WAN link bandwidth. To avoid this issue, you can use the split tunneling feature, which allows the traffic
sent by a client to be classified based on the packet contents. The matching packets are locally switched and the rest
of the traffic is centrally switched. The traffic that is sent by the client that matches the IP address of the device
present in the local site can be classified as locally switched traffic and the rest of the traffic as centrally switched.
To configure local split tunneling on an AP, ensure that you have enabled DCHP Required on the WLAN, which
ensures that the client associating with the split WLAN does DHCP.
Note Local split tunneling is not supported on Cisco 1500 Series, Cisco 1130, and Cisco 1240 access points, and
does not work for clients with static IP address.
d) Click Add.
Step 14 To configure Central DHCP processing:
a) In the WLAN Id box, enter the WLAN ID with which you want to map Central DHCP.
b) Select or unselect the Central DHCP check box to enable or disable Central DHCP for the mapping.
c) Select or unselect the Override DNS check box to enable or disable overriding of DNS for the mapping.
d) Select or unselect the NAT-PAT check box to enable or disable network address translation and port address translation
for the mapping.
Note The AP will reboot when you change the AP behavior from Flexconnect to Local.
Note Only the Session Timeout RADIUS attribute is supported in standalone mode. All other
attributes as well as RADIUS accounting are not supported.
Note To delete a RADIUS server that is configured for a FlexConnect access point, enter the
config ap flexconnect radius auth delete {primary | secondary} Cisco_AP command.
• config ap flexconnect vlan wlan wlan_id vlan-id Cisco_AP—Enables you to assign a VLAN ID to this
FlexConnect access point. By default, the access point inherits the VLAN ID associated to the WLAN.
• config ap flexconnect vlan {enable | disable} Cisco_AP—Enables or disables VLAN tagging for this
FlexConnect access point. By default, VLAN tagging is not enabled. After VLAN tagging is enabled
on the FlexConnect access point, WLANs that are enabled for local switching inherit the VLAN assigned
at the controller.
• config ap flexconnect vlan native vlan-id Cisco_AP—Enables you to configure a native VLAN for
this FlexConnect access point. By default, no VLAN is set as the native VLAN. One native VLAN must
be configured per FlexConnect access point (when VLAN tagging is enabled). Make sure the switch
port to which the access point is connected has a corresponding native VLAN configured as well. If the
FlexConnect access point’s native VLAN setting and the upstream switch port native VLAN do not
match, the access point cannot transmit packets to and from the controller.
Note To save the VLAN mappings in the access point after an upgrade or downgrade, you
should restrict the access point to join the controller for which it is primed. No other
discoverable controller with a different configuration should be available by other means.
Similarly, at the time the access point joins, if it moves across controllers that have
different VLAN mappings, the VLAN mappings at the access point might get
mismatched.
• Configure the mapping of a Web-Auth or a Web Passthrough ACL to a WLAN for an access point in
FlexConnect mode by entering this command:
config ap flexconnect web-auth wlan wlan_id cisco_ap acl_name {enable | disable}
Note The FlexConnect ACLs that are specific to an AP have the highest priority. The
FlexConnect ACLs that are specific to WLANs have the lowest priority.
Note You can configure up to 16 Web Policy ACLs that are specific to an access point.
Note The gratuitous ARP for the gateway is sent by the access point to the client, which
obtained an IP address from the central site. This is performed to proxy the gateway by
the access point.
Use these commands on the FlexConnect access point to get status information:
• show capwap reap status—Shows the status of the FlexConnect access point (connected or standalone).
• show capwap reap association—Shows the list of clients associated with this access point and their
SSIDs.
Use these commands on the FlexConnect access point to get debug information:
• debug capwap reap—Shows general FlexConnect activities.
• debug capwap reap mgmt—Shows client authentication and association messages.
• debug capwap reap load—Shows payload activities, which are useful when the FlexConnect access
point boots up in standalone mode.
• debug dot11 mgmt interface—Shows 802.11 management interface events.
• debug dot11 mgmt msg—Shows 802.11 management messages.
• debug dot11 mgmt ssid—Shows SSID management events.
• debug dot11 mgmt state-machine—Shows the 802.11 state machine.
• debug dot11 mgmt station—Shows client events.
Caution Do not connect the access points in FlexConnect mode directly to Cisco 2500 Series Controllers.
• show wlan wlan-id —Displays the configuration for the WLAN. If local authentication is enabled, the
following information appears:
. . .
. . .
Web Based Authentication...................... Disabled
Web-Passthrough............................... Disabled
Conditional Web Redirect...................... Disabled
Splash-Page Web Redirect...................... Disabled
Auto Anchor................................... Disabled
FlexConnect Local Switching........................ Enabled
FlexConnect Local Authentication................... Enabled
FlexConnect Learn IP Address....................... Enabled
Client MFP.................................... Optional
Tkip MIC Countermeasure Hold-down Timer....... 60
Call Snooping.................................... Disabled
Roamed Call Re-Anchor Policy..................... Disabled
. . .
. . .
To determine if a client’s data traffic is being locally or centrally switched, choose Monitor > Clients on the
controller GUI, click the Detail link for the desired client, and look at the Data Switching parameter under
AP Properties.
Note FlexConnect ACLs are not supported on native VLAN when setting comes from
FlexConnect Group.
Note A Local Switching WLAN is configured and ACL is mapped to a FlexConnect group with an ACL. The
ACL has set of 'deny and permit' rules. When you associate a client to the WLAN, the client needs to have
DHCP permit rule added for getting the IP address.
Step 1 Choose Security > Access Control Lists > FlexConnect Access Control Lists.
The FlexConnect ACL page is displayed.
This page lists all the FlexConnect ACLs configured on the controller. This page also shows the FlexConnect ACLs
created on the corresponding controller. To remove an ACL, hover your mouse over the blue drop-down arrow adjacent
to the corresponding ACL name and choose Remove.
Step 3 In the Access Control List Name text box, enter a name for the new ACL. You can enter up to 32 alphanumeric characters.
Step 4 Click Apply.
Step 5 When the Access Control Lists page reappears, click the name of the new ACL.
When the Access Control Lists > Edit page appears, click Add New Rule.
The Access Control Lists > Rules > New page is displayed.
c) From the Destination drop-down list, choose one of these options to specify the destination of the packets to which
this ACL applies:
• Any—Any destination (This is the default value.)
• IP Address—A specific destination. If you choose this option, enter the IP address and netmask of the destination
in the text boxes.
d) From the Protocol drop-down list, choose the protocol ID of the IP packets to be used for this ACL. The protocol
options that you can use are the following:
• Any—Any protocol (This is the default value.)
• TCP
• UDP
f) From the Action drop-down list, choose Deny to cause this ACL to block packets, or Permit to cause this ACL to
allow packets. The default value is Deny.
g) Click Apply.
The Access Control Lists > Edit page is displayed on which the rules for this ACL are shown.
h) Repeat this procedure to add additional rules, if any, for this ACL.
Step 7 Click Save Configuration.
The following figure shows a typical FlexConnect deployment with a backup RADIUS server in the branch
office.
Figure 62: FlexConnect Group Deployment
For more information about FlexConnect deployment considerations, see the FlexConnect chapter of the
Enterprise Mobility Design Guide.
Note CCKM fast roaming among FlexConnect and non-FlexConnect access points is not supported.
Note FlexConnect Groups is needed for CCKM to work. Flex group needs to be created for CCKM, 11r , and
OKC , only then the caching can happen on an AP. The group name must be same between APS for a fast
roaming to happen for 11r/CCKM. The group can be different for OKC as final check is done at Cisco
WLC.
Note The FlexConnect access point must be in connected mode when the PMK is derived during WPA2/802.1x
authentication.
When using FlexConnect groups for OKC or CCKM, the PMK-cache is shared only across the access points
that are part of the same FlexConnect group and are associated to the same controller. If the access points are
in the same FlexConnect group but are associated to different controllers that are part of the same mobility
group, the PMK cache is not updated and CCKM roaming will fail but OKC roaming will still work.
Note Fast roaming works only if the APs are in the same FlexConnect group for APs in FlexConnect mode,
802.11r .
Note • You can configure LEAP, EAP-FAST, PEAP, or EAP-TLS authentication only if AP local
authentication is enabled.
You have to provision a certificate to the AP because the AP has to send the certificate to the client. You must
download the Vendor Device Certificate and the Vendor Certification Authority Certificate to the controller.
The controller then pushes these certificates to the AP. If you do not configure a Vendor Device Certificate
and the Vendor CA Certificate on the controller, the APs associating with the FlexConnect group download
the self-signed certificate of the controller, which may not be recognized by many wireless clients.
With EAP-TLS, AP does not recognize and accept client certificate if the client root CA is different from the
AP root CA. When you use Enterprise public key infrastructures (PKI), you must download a Vendor Device
Certificate and Vendor CA Certificate to the controller so that the controller can push the certificates to the
AP in the FlexConnect group. Without a common client and AP root CA, EAP-TLS fails on the local AP.
The AP cannot check an external CA and relies on its own CA chain for client certificate validation.
The space on the AP for the local certificate and the CA certificate is around 7 Kb, which means that only
short chains are adapted. Longer chains or multiple chains are not supported.
Note This feature can be used with the FlexConnect backup RADIUS server feature. If a FlexConnect is
configured with both a backup RADIUS server and local authentication, the FlexConnect access point
always attempts to authenticate clients using the primary backup RADIUS server first, followed by the
secondary backup RADIUS server (if the primary is not reachable), and finally the FlexConnect access
point itself (if the primary and secondary are not reachable).
For information about the number of FlexConnect groups and access point support for a Cisco WLC model,
see the data sheet of the respective Cisco WLC model.
Step 1 Choose Wireless > FlexConnect Groups to open the FlexConnect Groups page.
This page lists any FlexConnect groups that have already been created.
Note If you want to delete an existing group, hover your cursor over the blue drop-down arrow for that group and
choose Remove.
Step 2 Click New to create a new FlexConnect Group.
Step 3 On the FlexConnect Groups > New page, enter the name of the new group in the Group Name text box. You can
enter up to 32 alphanumeric characters.
Step 4 Click Apply. The new group appears on the FlexConnect Groups page.
Step 5 To edit the properties of a group, click the name of the desired group. The FlexConnect Groups > Edit page appears.
Step 6 If you want to configure a primary RADIUS server for this group (for example, the access points are using 802.1X
authentication), choose the desired server from the Primary RADIUS Server drop-down list. Otherwise, leave the text
box set to the default value of None.
Note IPv6 RADIUS Server is not configurable. Only IPv4 configuration is supported.
Step 7 If you want to configure a secondary RADIUS server for this group, choose the server from the Secondary RADIUS
Server drop-down list. Otherwise, leave the field set to the default value of None.
Step 8 Configure the RADIUS server for the FlexConnect group by doing the following:
a) Enter the RADIUS server IP address.
b) Choose the server type as either Primary or Secondary.
c) Enter a shared secret to log on to the RADIUS server and confirm it.
d) Enter the port number.
e) Click Add.
Step 9 To add an access point to the group, click Add AP. Additional fields appear on the page under Add AP.
Step 10 Perform one of the following tasks:
• To choose an access point that is connected to this controller, select the Select APs from Current Controller
check box and choose the name of the access point from the AP Name drop-down list.
Note If you choose an access point on this controller, the MAC address of the access point is automatically
entered in the Ethernet MAC text box to prevent any mismatches from occurring.
• To choose an access point that is connected to a different controller, leave the Select APs from Current Controller
check box unselected and enter its MAC address in the Ethernet MAC text box.
Note If the FlexConnect access points within a group are connected to different controllers, all of the controllers
must belong to the same mobility group.
Step 11 Click Add to add the access point to this FlexConnect group. The access point’s MAC address, name, and status appear
at the bottom of the page.
Note If you want to delete an access point, hover your cursor over the blue drop-down arrow for that access point
and choose Remove.
Step 12 Click Apply.
Step 13 Enable local authentication for a FlexConnect Group as follows:
a) Ensure that the Primary RADIUS Server and Secondary RADIUS Server parameters are set to None.
b) Select the Enable AP Local Authentication check box to enable local authentication for this FlexConnect Group.
The default value is unselected.
c) Click Apply.
d) Choose the Local Authentication tab to open the FlexConnect > Edit (Local Authentication > Local Users)
page.
e) To add clients that you want to be able to authenticate using LEAP, EAP-FAST, PEAP, or EAP-TLS, perform one
of the following:
f) Upload a comma-separated values (CSV) file by selecting the Upload CSV File check box, clicking the Browse
button to browse to an CSV file that contains usernames and passwords (each line of the file needs to be in the
following format: username, password), and clicking Add to upload the CSV file. The clients’ names appear on the
left side of the page under the “User Name” heading.
g) Add clients individually by entering the client’s username in the User Name text box and a password for the client
in the Password and Confirm Password text boxes, and clicking Add to add this client to the list of supported local
users. The client name appears on the left side of the page under the “User Name” heading.
Note You can add up to 100
clients.
h) Click Apply.
i) Choose the Protocols tab to open the FlexConnect > Edit (Local Authentication > Protocols) page.
j) To allow a FlexConnect access point to authenticate clients using LEAP, select the Enable LEAP Authentication
check box.
k) To allow a FlexConnect access point to authenticate clients using EAP-FAST, select the Enable EAP-FAST
Authentication check box. The default value is unselected.
l) To allow a FlexConnect access point to authenticate clients using PEAP Authentication, select the Enable PEAP
Authentication check box.
You can configure PEAP authentication only when AP local authentication is configured.
m) To allow a FlexConnect access point to authenticate clients using EAP-TLS, select the Enable EAP TLS
Authentication check box.
You can configure EAP-TLS authentication only when AP local authentication is configured.
Enabling the EAP-TLS authentication results in enabling the downloading of EAP root and device certificate to the
access point. You can unselect the EAP TLS Certificate download check box if you do not want to download the
certificate.
n) Perform one of the following, depending on how you want protected access credentials (PACs) to be provisioned:
• To use manual PAC provisioning, enter the server key used to encrypt and decrypt PACs in the Server Key and
Confirm Server Key text boxes. The key must be 32 hexadecimal characters.
• To allow PACs to be sent automatically to clients that do not have one during PAC provisioning, select the
Enable Auto Key Generation check box
o) In the Authority ID text box, enter the authority identifier of the EAP-FAST server. The identifier must be 32
hexadecimal characters.
p) In the Authority Info text box, enter the authority identifier of the EAP-FAST server in text format. You can enter
up to 32 hexadecimal characters.
q) To specify a PAC timeout value, select the PAC Timeout check box and enter the number of seconds for the PAC
to remain viable in the text box. The default value is unselected, and the valid range is 2 to 4095 seconds when
enabled.
r) Click Apply.
Step 14 In the WLAN-ACL mapping tab, you can do the following:
a) Under Web Auth ACL Mapping, enter the WLAN ID, choose the WebAuth ACL, and click Add to map the web
authentication ACL and the WLAN.
b) Under Local Split ACL Mapping, enter the WLAN ID, and choose the Local Split ACL, and click Add to map the
Local Split ACL to the WLAN.
Note You can configure up to 16 WLAN-ACL combinations for local split tunneling. Local split tunneling does
not work for clients with static IP address.
Step 15 In the Central DHCP tab, you can do the following:
a) In the WLAN Id box, enter the WLAN ID with which you want to map Central DHCP.
b) Select or unselect the Central DHCP check box to enable or disable Central DHCP for the mapping.
c) Select or unselect the Override DNS check box to enable or disable overriding of DNS for the mapping.
d) Select or unselect the NAT-PAT check box to enable or disable network address translation and port address translation
for the mapping.
e) Click Add to add the Central DHCP - WLAN mapping.
Note When the overridden interface is enabled for the FlexConnect Group DHCP, the DHCP broadcast to unicast is
optional for locally switched clients.
Step 2 Configure a primary or secondary RADIUS server for the FlexConnect group by entering this command:
config flexconnect group group_name radius server auth{add | delete} {primary | secondary} server_index
Step 3 Configure a primary or secondary RADIUS server for the FlexConnect group by entering this command:
config flexconect group group-name radius server auth {{add {primary | secondary} ip-addr auth-port secret} |
{delete {primary | secondary}}}
Step 4 Add an access point to the FlexConnect Group by entering this command:
config flexconnect group_name ap {add | delete} ap_mac
m) To specify the authority identifier of the EAP-FAST server, enter this command:
config flexconnect group group_name radius ap authority id id
where id is 32 hexadecimal characters.
n) To specify the authority identifier of the EAP-FAST server in text format, enter this command:
config flexconnect group group_name radius ap authority info info
where info is up to 32 hexadecimal characters.
o) To specify the number of seconds for the PAC to remain viable, enter this command:
config flexconnect group group_name radius ap pac-timeout timeout
where timeout is a value between 2 and 4095 seconds (inclusive) or 0. A value of 0, which is the default value,
disables the PAC timeout.
Step 6 Configure a Web Policy ACL on a FlexConnect group by entering this command:
config flexconnect group group-name web-policy policy acl {add | delete} acl-name
Step 7 Configure local split tunneling on a per-FlexConnect group basis by entering this command:
config flexconnect group group_name local-split wlan wlan-id acl acl-name flexconnect-group-name {enable |
disable}
Step 8 To set multicast/broadcast across L2 broadcast domain on overridden interface for locally switched clients, enter this
command:
config flexconnect group group_name multicast overridden-interface {enable | disable}
Step 10 Configure the DHCP overridden interface for FlexConnect group, use the
configflexconnectgroupflexgroupdhcpoverridden-interfaceenablecommand.
Step 11 Configure policy acl on FlexConnect group by entering this command:
config flexconnect group group_name policy acl {add | delete} acl-name
Step 17 See the details for a specific FlexConnect Groups by entering this command:
show flexconnect group detail group_name
Step 2 Click the Group Name link of the FlexConnect Group for which you want to configure VLAN-ACL mapping.
Step 3 Click the VLAN-ACL Mapping tab.
The VLAN-ACL Mapping page for that FlexConnect group appears.
ACL Present on AP ACL Name sent from AAA Result of 802.1X Authentication
No No Authenticated, no ACL applied
No Yes Authentication Denied
Yes No Authenticated, no ACL applied
Yes Yes Authenticated, client ACL
applied
• After client authentication, if the ACL name is changed in the RADIUS server, the client must go through
a full authentication again to get the correct client ACL.
• The WLAN-VLAN mapping on FlexConnect groups is not supported on Cisco APs 1131 and 1242.
This table shows the order of preference for local and FlexConnect central switching:
• Dynamic VLAN assignment is not supported for web authentication from a controller with Access
Control Server (ACS).
• AAA override of bidirectional rate limiting on an AP and the controller is supported on all the following
802.11n nonmesh access points:
◦1040
◦1140
◦1250
◦1260
◦1600
◦2600
◦3500
◦3600
Change the ingress ACL and egress ACL mappings by selecting the mappings from the drop-down list for each
ACL type.
• Group Level VLAN ACL Mapping—The following group level VLAN ACL mapping parameters are available:
◦VLAN ID—The VLAN ID.
◦Ingress ACL—The ingress ACL for this VLAN.
◦Egress ACL—The egress ACL for this VLAN.
• A FlexConnect group can have one master AP per AP model. If a master AP is not selected manually,
the AP that has the least MAC address value is automatically chosen as the master AP for that model.
• A maximum of 3 slave APs of the same model can download the image from their master AP (a maximum
of 3 TFTP connections can serve at a time). The rest of the slave APs use the random back-off timer to
retry for the master AP to download the image. The random back-off value is more than 100 seconds.
After a slave AP downloads the image, the AP informs the Cisco WLC about the completion of the
download. After random back-off, the waiting slave AP can occupy the empty TFTP slot at the master
AP.
If a slave AP fails to download the image from its master AP even after the slave retry count that you
have configured is exhausted, the slave AP reaches out to the Cisco WLC to fetch the new image.
• This feature works only with CAPWAP APs.
• This feature does not work if a master AP is connected over CAPWAP6.
• If you upgrade from a release that is prior to Release 7.5 directly to Release 7.6.X or a later release, the
predownload process on Cisco AP2600 and AP3600 fails. After the Cisco WLC is upgraded to Release
7.6.X or a later release, the new image is loaded on Cisco AP2600 and AP3600. After the upgrade to a
Release 7.6.X image, the predownload functionality works as expected. The predownload failure is only
a one-time failure.
Step 2 Click the Group Name link on which you want to configure the image upgrade.
Step 3 Click the Image Upgrade tab.
Step 4 Check the FlexConnect AP Upgrade check box to enable a FlexConnect AP Upgrade.
Step 5 If you enabled the FlexConnect AP upgrade in the previous step, you must enable the following parameters:
• Slave Maximum Retry Count—The number of attempts the slave access point must try to connect to the master
access point for downloading the upgrade image. If the image download does not occur for the configured retry
attempts, the image is upgraded over the WAN. The default value is 44; the valid range is between 1 and 63.
• Upgrade Image—Select the upgrade image. The options are Primary, Backup, and Abort.
Step 6 From the AP Name drop-down list, click Add Master to add the master access point.
You can manually assign master access points in the FlexConnect group by selecting the access points.
This figure shows a wireless client that roams from one access point to another when both access points are
joined to the same controller.
Figure 63: Intracontroller Roaming
When the wireless client moves its association from one access point to another, the controller simply updates
the client database with the newly associated access point. If necessary, new security context and associations
are established as well.
The process becomes more complicated, however, when a client roams from an access point joined to one
controller to an access point joined to a different controller. It also varies based on whether the controllers are
operating on the same subnet.
This figure shows intercontroller roaming, which occurs when the wireless LAN interfaces of the controllers
are on the same IP subnet.
Figure 64: Intercontroller Roaming
When the client associates to an access point joined to a new controller, the new controller exchanges mobility
messages with the original controller, and the client database entry is moved to the new controller. New
security context and associations are established if necessary, and the client database entry is updated for the
new access point. This process remains transparent to the user.
Note All clients configured with 802.1X/Wi-Fi Protected Access (WPA) security complete a full authentication
in order to comply with the IEEE standard.
This figure shows intersubnet roaming, which occurs when the wireless LAN interfaces of the controllers are
on different IP subnets.
Figure 65: Intersubnet Roaming
Inter-subnet roaming is similar to inter-controller roaming in that the controllers exchange mobility messages
on the client roam. However, instead of moving the client database entry to the new controller, the original
controller marks the client with an “Anchor” entry in its own client database. The database entry is copied to
the new controller client database and marked with a “Foreign” entry in the new controller. The roam remains
transparent to the wireless client, and the client maintains its original IP address.
In inter-subnet roaming, WLANs on both anchor and foreign controllers need to have the same network access
privileges and no source-based routing or source-based firewalls in place. Otherwise, the clients may have
network connectivity issues after the handoff.
In a static anchor setup using controllers and ACS, if AAA override is enabled to dynamically assign VLAN
and QoS, the foreign controller updates the anchor controller with the right VLAN after a Layer 2 authentication
(802.1x). For Layer 3 RADIUS authentication, the RADIUS requests for authentication are sent by the anchor
controller.
Mobility is not supported for SSIDs with security type configured for Webauth on MAC filter failure.
If the management VLAN of one Cisco WLC is present as a dynamic VLAN on another Cisco WLC, the
mobility feature is not supported.
Note If a client roams in web authentication state, the client is considered as a new client on another controller
instead of considering it as a mobile client.
Note New Mobility with WebAuth and MAC filter is not supported. For a client, if L2 authentication fails and
it falls back to L3 authentication and then tries to roam to a different Cisco WLC, the roaming will fail.
The same behavior is applicable to FlexConnect central switching and local mode as well.
Note Cisco Wireless Controllers (that are mobility peers) must use the same DHCP server to have an updated
client mobility move count on intra-VLAN.
Note When an AP moves from one WLC to another WLC (when both WLCs are mobility peers), a client
associated to the first WLC before the move may be anchored to it even after the move. To prevent such
a scenario, you should remove the mobility peer configuration of the WLC.
Note Controllers do not have to be of the same model to be a member of a mobility group. Mobility groups can
be comprised of any combination of controller platforms.
As shown above, each controller is configured with a list of the other members of the mobility group. Whenever
a new client joins a controller, the controller sends out a unicast message (or multicast message if mobility
multicast is configured) to all of the controllers in the mobility group. The controller to which the client was
previously connected passes on the status of the client.
For example, if a controller supports 6000 access points, a mobility group that consists of 24 such controllers
supports up to 144,000 access points (24 * 6000 = 144,000 access points).
Mobility groups enable you to limit roaming between different floors, buildings, or campuses in the same
enterprise by assigning different mobility group names to different controllers within the same wireless
network.
This figure shows the results of creating distinct mobility group names for two groups of controllers.
Figure 67: Two Mobility Groups
The controllers in the ABC mobility group share access point and client information with each other. The
controllers in the ABC mobility group do not share the access point or client information with the XYZ
controllers, which are in a different mobility group. Likewise, the controllers in the XYZ mobility group do
not share access point or client information with the controllers in the ABC mobility group. This feature
ensures mobility group isolation across the network.
Every controller maintains information about its peer controllers in a mobility list. Controllers can communicate
across mobility groups and clients may roam between access points in different mobility groups if the controllers
are included in each other’s mobility lists. In the following example, controller 1 can communicate with either
controller 2 or 3, but controller 2 and controller 3 can communicate only with controller 1 and not with each
other. Similarly, clients can roam between controller 1 and controller 2 or between controller 1 and controller
3 but not between controller 2 and controller 3.
In a mobility list, the following combinations of mobility groups and members are allowed:
• 3 mobility groups with 24 members in each group
• 12 mobility groups with 6 members in each group
• 24 mobility groups with 3 members in each group
• 72 mobility groups with 1 member in each group
The controller supports seamless roaming across multiple mobility groups. During seamless roaming, the
client maintains its IP address across all mobility groups; however, Cisco Centralized Key Management
(CCKM) and proactive key caching (PKC) are supported only for inter-mobility-group roaming. When a
client crosses a mobility group boundary during a roam, the client is fully authenticated, but the IP address is
maintained, and mobility tunneling is initiated for Layer 3 roaming.
Note When a controller is added to a mobility group, some of the APs (which are running in local mode) do
not get the complete controllers list updated, those APs are connected to controllers that are in the same
mobility group. You can view the controller list in the APs using the command "show capwap client
config" AP-NAME command. For example, if the mobility group is for 19 controllers and then you add
two more controllers to the mobility group, the AP shows 19 controllers instead of 21 in its list. To address
this issue, you can reboot the AP or move it to another controller that is part of the same mobility group
to get the controller list updated. This issue is observed in AP1242 connected to different 5508 controllers
running code 7.6.120.0.
Note When client moves to a non anchored SSID from an anchored sSSID on foreign, there is a stale entry on
foreign .This happens when multicast mobile announce does not reach from foreign to guest anchor due
to whatsoever reason, due to this the service is not impacted and configuration goes unnoticed but silently
leaks MSCB on GA .There is no debug or error message shown nor does the GA runs a timer per client
to cleanup. A HandoffEnd needs to be sent from foreign to Anchor since there is no timer.
Note Client mobility among controllers works only if auto-anchor mobility (also called guest tunneling) or
symmetric mobility tunneling is enabled. Asymmetric tunneling is not supported when mobility controllers
are behind the NAT device. See the Configuring Auto-Anchor Mobility and Using Symmetric Mobility
Tunneling sections for details on these mobility options.
The scenario where there are different RF group names if the APs can hear each other is:
• RF group names are usually consistent across a single deployment.
• APs which have unrecognizable neighbor packets or wrong entries are deemed rogues.
• If there are Cisco APs with two different RF groups. They would hear each other but will not populate
the other in the RF neighbor list. (This RF list is sent to WLC for further munching as discussed above)
• Usually when two local neighborhoods have widely varying RF characteristics, then the network admin
may adopt two RF group names to separate the two RF neighborhood or they may belong two different
networks.
• AP neighborhood determines RF grouping(auto-mode) /Rogue classification and other and not vice-versa.
Note Mobility control packets can use any interface address as the source, based on routing
table. It is recommended that all controllers in the mobility group should have the
management interface in the same subnet. A topology where one controller's management
interface and other controller's dynamic interface are on same subnet not recommended
for seamless mobility.
• When controllers in the mobility list use different software versions, Layer 2 or Layer 3 clients have
limited roaming support. Layer 2 or Layer 3 client roaming is supported only between controllers that
use the same version or with controllers that run versions 7.X.X.
Note If you inadvertently configure a controller with a failover controller that runs a different
software release, the access point might take a long time to join the failover controller
because the access point starts the discovery process in CAPWAP and then changes to
LWAPP discovery.
• All controllers must be configured with the same virtual interface IP address.
Note If necessary, you can change the virtual interface IP address by editing the virtual
interface name on the Controller > Interfaces page.
Note If all the controllers within a mobility group are not using the same virtual interface,
inter-controller roaming may appear to work, but the handoff does not complete, and
the client loses connectivity for a period of time.
• You must have gathered the MAC address and IP address of every controller that is to be included in
the mobility group. This information is necessary because you will be configuring all controllers with
the MAC address and IP address of all the other mobility group members.
Note You can find the MAC and IP addresses of the other controllers to be included in the
mobility group on the Controller > Mobility Groups page of each controller’s GUI.
• When you configure mobility groups using a third-party firewall, for example, Cisco PIX, or Cisco ASA,
you must open port 16666, and IP protocol 97.
• For intercontroller CAPWAP data and control traffic, you must open the ports 5247 and 5246.
This table lists the protocols and port numbers that must be used for management and operational purposes:
SNMP UDP Port 161 for gets and sets and UDP port 162 for traps.
HTTPS/HTTP TCP port 443 for HTTPS and port 80 for HTTP
Note To view information on mobility support across controllers with different software versions, see the
http://www.cisco.com/c/en/us/td/docs/wireless/compatibility/matrix/compatibility-matrix.html. .
Note You cannot perform port address translation (PAT) on the firewall. You must configure one-to-one network
address translation (NAT).
Step 1 Choose Controller > Mobility Management > Mobility Groups to open the Static Mobility Group Members page.
This page shows the mobility group name in the Default Mobility Group text box and lists the MAC address and IPv4/IPv6
address of each controller that is currently a member of the mobility group. The first entry is the local controller, which
cannot be deleted.
Note If you want to delete any of the remote controllers from the mobility group, hover your cursor over the blue
drop-down arrow for the desired controller and choose Remove.
Step 2 Perform one of the following to add controllers to a mobility group:
• If you are adding only one controller or want to individually add multiple controllers, click New and go.
OR
• If you are adding multiple controllers and want to add them in bulk, click EditAll and go to.
Note The EditAll option enables you to enter the MAC and IPv4/IPv6 addresses of all the current mobility group
members and then copy and paste all the entries from one controller to the other controllers in the mobility
group.
Step 3 Click New to open the Mobility Group Member > New page.
Step 4 Add a controller to the mobility group as follows:
1 In the Member IP Address text box, enter the management interface IPv4/IPv6 address of the controller to be added.
Note If you are configuring the mobility group in a network where network address translation (NAT) is enabled,
enter the IPv4/IPv6 address that is sent to the controller from the NAT device rather than the controller’s
management interface IPv4/IPv6 address. Otherwise, mobility will fail among controllers in the mobility
group.
2 In the Member MAC Address text box, enter the MAC address of the controller to be added.
3 In the Group Name text box, enter the name of the mobility group.
Note The mobility group name is case
sensitive.
4 In the Hash text box, enter the hash key of the peer mobility controller, which should be a virtual controller in the
same domain.
You must configure the hash only if the peer mobility controller is a virtual controller in the same domain.
Note Hash is not supported for IPv6
members.
5 Click Apply to commit your changes. The new controller is added to the list of mobility group members on the Static
Mobility Group Members page.
6 Click Save Configuration to save your changes.
7 Repeat Step a through Step e to add all of the controllers in the mobility group.
8 Repeat this procedure on every controller to be included in the mobility group. All controllers in the mobility group
must be configured with the MAC address and IPv4/IPv6 address of all other mobility group members.
The Mobility Group Members > Edit All page lists the MAC address, IPv4/IPv6 address, and mobility group name
(optional) of all the controllers currently in the mobility group. The controllers are listed one per line with the local
controller at the top of the list.
Note If desired, you can edit or delete any of the controllers in the
list.
Step 5 Add more controllers to the mobility group as follows:
1 Click inside the edit box to start a new line.
2 Enter the MAC address, the management interface IPv4/IPv6 address, and the name of the mobility group for the
controller to be added.
Note You should enter these values on one line and separate each value with one or two spaces.
Note The mobility group name is case
sensitive.
3 Repeat Step a and Step b for each additional controller that you want to add to the mobility group.
4 Highlight and copy the complete list of entries in the edit box.
5 Click Apply to commit your changes. The new controllers are added to the list of mobility group members on the
Static Mobility Group Members page.
6 Click Save Configuration to save your changes.
7 Paste the list into the text box on the Mobility Group Members > Edit All page of all the other controllers in the
mobility group and click Apply and Save Configuration.
Step 6 Choose Mobility Management > Multicast Messaging to open the Mobility Multicast Messaging page.
The names of all the currently configured mobility groups appear in the middle of the page.
Step 7 On the Mobility Multicast Messaging page, select the Enable Multicast Messaging check box to enable the controller
to use multicast mode to send Mobile Announce messages to the mobility members. If you leave it unselected, the
controller uses unicast mode to send the Mobile Announce messages. The default value is unselected.
Step 8 If you enabled multicast messaging in the previous step, enter the multicast group IPv4 address for the local mobility
group in the Local Group Multicast IPv4 Address text box. This address is used for multicast mobility messaging.
Note In order to use multicast messaging, you must configure the IPv4 address for the local mobility group.
Note In release 8.0, IPv6 is not supported for mobility
multicast.
Step 9 Click Apply to commit your changes.
Step 10 If desired, you can also configure the multicast group IPv4 address for non-local groups within the mobility list. To do
so, click the name of a non-local mobility group to open the Mobility Multicast Messaging > Edit page, and enter the
multicast group IPv4 address for the non-local mobility group in the Multicast IP Address text box.
Note If you do not configure the multicast IPv4 address for non-local groups, the controller uses unicast mode to send
mobility messages to those members.
Step 11 Click Apply to commit your changes.
Step 12 Click Save Configuration to save your changes.
Step 4 To configure the hash key of a peer mobility controller, which is a virtual controller in the same domain, enter this
command:
config mobility group member hash peer-ip-address key
Step 6 (Optional) You can also configure the multicast group IPv4 address for non-local groups within the mobility list. To do
so, enter this command:
config mobility group multicast-address group_name IP_address
If you do not configure the multicast IPv4 address for non-local groups, the controller uses unicast mode to send mobility
messages to those members.
Step 8 To see the hash key of mobility group members in the same domain, enter this command:
show mobility group member hash
Step 10 Repeat this procedure on every controller to be included in the mobility group. All controllers in the mobility group must
be configured with the MAC address and IP address of all other mobility group members.
Step 11 Enable or disable debugging of multicast usage for mobility messages by entering this command:
debug mobility multicast {enable | disable}
Step 1 Choose Monitor > Statistics > Mobility Statistics to open the Mobility Statistics page.
This page contains the following fields
• Group Mobility Statistics
◦Rx Errors—Generic protocol packet receive errors, such as packet too short or format incorrect.
◦Tx Errors—Generic protocol packet transmit errors, such as packet transmission fail.
◦Responses Retransmitted—Mobility protocol that uses UDP and resends requests several times if it does not
receive a response. Because of network or processing delays, the responder may receive one or more retry
requests after it initially responds to a request. This text box shows a count of the response resends.
◦Handoff Requests Received—Total number of handoff requests received, ignored, or responded to.
◦Handoff End Requests Received—Total number of handoff end requests received. These requests are sent
by the anchor or foreign controller to notify the other about the close of a client session.
◦State Transitions Disallowed—Policy enforcement module (PEM) that has denied a client state transition,
usually resulting in the handoff being aborted.
◦Resource Unavailable—Necessary resource, such as a buffer, was unavailable, resulting in the handoff being
aborted.
◦Handoff as Local Received—Number of handoffs in which the entire client session has been transferred.
◦Handoff as Foreign Received—Number of handoffs in which the client session was anchored elsewhere.
◦Handoff Denys Received—Number of handoffs that were denied.
◦Anchor Request Sent—Number of anchor requests that were sent for a three-party (foreign-to-foreign) handoff.
The handoff was received from another foreign controller, and the new controller is requesting the anchor to
move the client.
◦Anchor Deny Received—Number of anchor requests that were denied by the current anchor.
◦Anchor Grant Received—Number of anchor requests that were approved by the current anchor.
◦Anchor Transfer Received—Number of anchor requests that closed the session on the current anchor and
transferred the anchor back to the requestor.
Step 2 If you want to clear the current mobility statistics, click Clear Stats.
controller in the list, the second client is sent to the second controller in the list, and so on, until the end of
the anchor list is reached. The process is repeated starting with the first anchor controller. If any of the anchor
controller is detected to be down, all the clients anchored to the controller are deauthenticated, and the clients
then go through the authentication/anchoring process again in a round-robin manner with the remaining
controller in the anchor list. This functionality is also extended to regular mobility clients through mobility
failover. This feature enables mobility group members to detect failed members and reroute clients.
• In case of roaming between anchor controller and foreign mobility, the client addresses learned at the
anchor controller is shown at the foreign controller. You must check the foreign controller to view the
RA throttle statistics.
• For Layer 3 RADIUS authentication, the RADIUS requests for authentication are sent by the anchor
controller.
• The mobility anchor is not supported on virtual wireless LAN controllers.
• In a guest anchor Cisco WLC deployment, ensure that the foreign Cisco WLC does not have a WLAN
mapped to a VLAN that is associated with the guest anchor Cisco WLC.
• In Old Mobility, when roaming from foreign to anchor WLC, the other foreign WLCs in the mobility
group do not receive mobile announce messages.
Step 1 Configure the controller to detect failed anchor controllers within a mobility group as follows:
a) Choose Controller > Mobility Management > Mobility Anchor Config to open the Mobility Anchor Config page.
b) In the Keep Alive Count text box, enter the number of times a ping request is sent to an anchor controller before the
anchor is considered to be unreachable. The valid range is 3 to 20, and the default value is 3.
c) In the Keep Alive Interval text box, enter the amount of time (in seconds) between each ping request that is sent to
an anchor controller. The valid range is 1 to 30 seconds, and the default value is 10 seconds.
d) In the DSCP Value text box, enter the DSCP value. The default is 0.
Note While configuring the Mobility DSCP value, the mobility control socket (i.e control messages exchanged
between mobility peers only and not the data) is also updated. The configured value must reflect in the IPV4
header TOS field. This is a global configuration on the controller that is used to communicate among
configured mobility peers only.
e) Click Apply to commit your changes.
Step 2 Choose WLANs to open the WLANs page.
Step 3 Click the blue drop-down arrow for the desired WLAN or wired guest LAN and choose Mobility Anchors. The Mobility
Anchors page appears.
This page lists the controllers that have already been configured as mobility anchors and shows the current state of their
data and control paths. Controllers within a mobility group communicate among themselves over a well-known UDP
port and exchange data traffic through an Ethernet-over-IP (EoIP) tunnel. They send mpings, which test mobility control
packet reachability over the management interface over mobility UDP port 16666 and they send epings, which test the
mobility data traffic over the management interface over EoIP port 97. The Control Path text box shows whether mpings
have passed (up) or failed (down), and the Data Path text box shows whether epings have passed (up) or failed (down).
If the Data or Control Path text box shows “down,” the mobility anchor cannot be reached and is considered failed.
Step 4 Select the IPv4/IPv6 address of the controller to be designated a mobility anchor in the Switch IP Address (Anchor)
drop-down list.
Step 5 Click Mobility Anchor Create. The selected controller becomes an anchor for this WLAN or wired guest LAN.
Note To delete a mobility anchor for a WLAN or wired guest LAN, hover your cursor over the blue drop-down arrow
for the anchor and choose Remove.
Step 6 Click Save Configuration.
Step 7 Repeat Step 4 and Step 6 to set any other controllers as mobility anchors for this WLAN or wired guest LAN.
Step 8 Configure the same set of mobility anchors on every controller in the mobility group.
◦config mobility group keepalive interval seconds—Specifies the amount of time (in seconds)
between each ping request sent to a mobility list member. The valid range is 1 to 30 seconds, and
the default value is 10 seconds.
• Disable the WLAN or wired guest LAN for which you are configuring mobility anchors by entering
this command:
config {wlan | guest-lan} disable {wlan_id | guest_lan_id}
• Create a new mobility anchor for the WLAN or wired guest LAN by entering one of these commands:
◦config mobility group anchor add {wlan | guest-lan} {wlan_id | guest_lan_id}
anchor_controller_ip_address
◦config {wlan | guest-lan} mobility anchor add {wlan_id | guest_lan_id}
anchor_controller_ip_address
Note The wlan_id or guest_lan_id must exist and be disabled, and the
anchor_controller_ip_address must be a member of the default mobility group.
Note Auto-anchor mobility is enabled for the WLAN or wired guest LAN when you configure
the first mobility anchor.
• Delete a mobility anchor for the WLAN or wired guest LAN by entering one of these commands:
◦config mobility group anchor delete {wlan | guest-lan} {wlan_id | guest_lan_id}
anchor_controller_ip_address
◦config {wlan | guest-lan} mobility anchor delete {wlan_id | guest_lan_id}
anchor_controller_ip_address
Note Deleting the last anchor disables the auto-anchor mobility feature and resumes normal
mobility for new associations.
Note The wlan_id and guest_lan_id parameters are optional and constrain the list to the
anchors in a particular WLAN or guest LAN. To see all of the mobility anchors on your
system, enter the show mobility anchor command.
The Status text box shows one of these values:
UP—The controller is reachable and able to pass data.
CNTRL_PATH_DOWN—The mpings failed. The controller cannot be reached through
the control path and is considered failed.
DATA_PATH_DOWN—The epings failed. The controller cannot be reached and is
considered failed.
CNTRL_DATA_PATH_DOWN—Both the mpings and epings failed. The controller
cannot be reached and is considered failed.
• See the status of all mobility group members by entering this command:
show mobility summary
• Troubleshoot mobility issues by entering these commands:
◦debug mobility handoff {enable | disable}—Debugs mobility handoff issues.
◦debug mobility keep-alive {enable | disable} all—Dumps the keepalive packets for all mobility
anchors.
◦debug mobility keep-alive {enable | disable} IP_address—Dumps the keepalive packets for a
specific mobility anchor.
0x00000001 Security_WEP
0x00000002 Security_802_1X
0x00000004 Security_IPSec*
0x00000008 Security_IPSec_Passthrough*
0x00000010 Security_Web
0x00000020 Security_PPTP*
0x00000040 Security_DHCP_Required
0x00000080 Security_WPA_NotUsed
0x00000100 Security_Cranite_Passthrough*
0x00000200 Security_Fortress_Passthrough*
0x00000400 Security_L2TP_IPSec*
• If the access-point group VLAN on the anchor controller is different than the WLAN interface VLAN
on the foreign controller. In this case, client traffic could be sent on an incorrect VLAN during mobility
events.
Step 1 Choose Controller > Mobility Management > Mobility Anchor Config to open the Mobility Anchor Config page.
Step 2 The Symmetric Mobility Tunneling Mode text box shows Enabled.
Only one mobility ping test per controller can be run at a given time.
Note These ping tests are not Internet Control Message Protocol (ICMP) based. The term “ping” is used to
indicate an echo request and an echo reply message.
Note Any ICMP packet greater than 1280 bytes will always be responded with a packet that is truncated to
1280 bytes. For example, a ping with a packet that is greater than 1280 bytes from a host to the management
interface is always responded with a packet that is truncated to 1280 bytes.
3 Once the acknowledgment is received, the client traffic is tunneled between the anchor and the controller
(WLC-1).
Note If you configure WLAN with an interface group and any of the interfaces in the interface group supports
the static IP client subnet, the client is assigned to that interface. This situation occurs in local or remote
(static IP Anchor) controller.
When AAA override is used along with the interface group that is mapped to WLAN, the source interface
that is used for DHCP transactions is the Management interface.
If the interface group that you add to a WLAN has RADIUS Server Overwrite interface enabled and a
client requests for authentication, the controller selects the first IP address from the interface group as the
RADIUS server.
Note A security level 2 authentication is performed only in the local (static IP foreign) controller, which is also
known as the exported foreign controller.
The following restrictions apply when configuring static IP tunneling with other features on the same WLAN:
• Auto anchoring mobility (guest tunneling) cannot be configured for the same WLAN.
• FlexConnect local authentication cannot be configured for the same WLAN.
• The DHCP required option cannot be configured for the same WLAN.
• You cannot configure dynamic anchoring of static IP clients with FlexConnect local switching.
• We recommend that you configure the same NTP/SNTP servers on the Cisco WLCs. If the NTP/SNTP
servers are different, ensure that the system time on all Cisco WLCs is the same when NTP/SNTP is
enabled. If the system time is not in sync, seamless mobility might fail in some scenarios. Also, a Cisco
WLC that has the lagging time with NTP/SNTP enabled drops the mobile announce messages.
…………..
Static IP client tunneling.............. Enabled
…………..
Step 2 Click the Blue drop down arrow for the desired WLAN and choose Foreign-Maps.
The foreign mappings page appears. This page also lists the MAC addresses of the foreign controllers that are in the
mobility group and interfaces/interface groups.
Step 3 Choose the desired foreign controller MAC and the interface or interface group to which it must be mapped and click
on Add Mapping.
Step 1 Choose Controller > PMIPv6 > General. The PMIPv6 Generalwindow is displayed.
Step 2 Enter the values for the following parameters:
• Domain Name—Name of the PMIPv6 domain. The domain name can be up to 127 case-sensitive, alphanumeric
characters.
• MAG Name—Name of the MAG.
• Maximum Bindings Allowed—Maximum number of binding updates that the Cisco WLC can send to the MAG.
The valid range is between 0 and 40000.
• Binding Lifetime—Lifetime, in seconds, of the binding entries in the Cisco WLC. The valid range is between 10
and 65535. The default value is 3600. The binding lifetime should be a multiple of 4.
• Binding Refresh Time—Refresh time, in seconds, of the binding entries in the Cisco WLC. The valid range is
between 4 and 65535 seconds. The default value is 300 seconds. The binding refresh time should be a multiple of
4.
• Binding Initial Retry Timeout—Initial timeout, in milliseconds, between the Proxy Binding Updates (PBUs)
when the Cisco WLC does not receive the Proxy Binding Acknowledgments (PBAs). The valid range is between
100 and 65535. The default value is 1000.
• Binding Maximum Retry Timeout—Maximum timeout between the PBUs when the Cisco WLC does not receive
the PBAs. The valid range is between 100 and 65535. The default value is 32000.
• Replay Protection Timestamp—Maximum amount of time, in milliseconds, difference between the timestamp
in the received PBA and the current time of the day. The valid range is between 1 and 255. The default value is 7.
• Minimum BRI Retransmit Timeout—Minimum amount of time, in milliseconds, that the Cisco WLC waits for
before retransmitting the BRI message. The valid range is between 500 and 65535. The default value is 1000.
• Maximum BRI Retransmit Timeout—Maximum amount of time, in milliseconds, that the Cisco WLC waits for
before retransmitting the Binding Revocation Indication (BRI) message. The valid range is between 500 and 65535.
The default value is 2000.
• BRI Retries—Maximum number of times that the Cisco WLC retransmits the BRI message before receiving the
Binding Revocation Acknowledgment (BRA) message. The valid range is between 1 to 10. The default value is 1.
c) Click Apply.
Step 5 To create a PMIPv6 profile, follow these steps:
a) Choose Controller > PMIPv6 > Profiles and click New.
b) In the PMIPv6 Profile > New window, enter the values for the following parameters:
• Profile Name—Name of the profile.
• Network Access Identifier—Name of the Network Access Identifier (NAI) associated with the profile.
• LMA Name—Name of the LMA to which the profile is associated.
• Access Point Node—Name of the access point node; APN identifies a particular routing domain for user traffic.
c) Click Apply.
Step 6 To configure PMIPv6 parameters for a WLAN, follow these steps:
a) Choose WLANs > WLAN ID. The WLANs > Edit window is displayed.
b) Click the Advanced tab.
c) Under PMIP, from the PMIP Mobility Type drop-down list, choose the mobility type from the following options:
• None—Configures the WLAN with simple IP
• PMIPv6—Configures the WLAN with only PMIPv6
d) From the PMIP Profile drop-down list, choose the PMIP profile for the WLAN.
e) In the PMIP Realm field, enter the default realm for the WLAN.
f) Click Apply.
Step 7 Click Save Configuration.
• Configure the list of LMAs for the MAG by entering this command:
config pmipv6 mag lma lma-name ipv4-address ip-address
Step 5 Configure the PMIPv6 parameters for the WLAN by using these commands:
• Configure the default realm for the WLAN by entering this command:
config wlan pmipv6 default-realm {realm-name | none} wlan-id
• Configure the mobility type for a WLAN or for all WLANs by entering this command:
config wlan pmipv6 mobility-type {none | pmipv6} {wlan-id | all}
• Configure the profile name for a PMIPv6 WLAN by entering this command:
Note With Release 8.1 in a New Mobility environment, Cisco WLCs running Cisco Wireless software cannot
function as mobility controllers (MC). However, the Cisco WLCs can function as guest anchors.
• For seamless mobility, the controller should either use new mobility or old mobility (flat mobility).
• Interoperability between two types of mobility is not supported. When you downgrade the controller
from Release 7.5 to a controller software release that does not support new mobility, such as Releases
7.4.100.0, 7.3.101.0, 7.2, 7.0, or earlier (all releases prior to 7.3.112.0), the controller automatically
transits to flat mobility (old mobility). This is due to the difference in mobility architecture and
noninteroperability between flat mobility (EOIP tunnels) and new mobility(CAPWAP tunnels).
• High availability for Mobility Oracle is not supported.
• When a client associates for the very first time as local, then in the Cisco WLC, the MA sends a 'handoff
complete' message to the MC to update the client database in the MC. However, the 'handoff complete'
message is sent in a 'DHCP REQD' state because of which the IP address of the client is 0.0.0.0 for the
very first time. This event is triggered by timer expiry.
• IPv6 is not supported with new mobility.
Step 1 Choose Controller > Mobility Management > Mobility Configuration to enable and configure new mobility on the
controller.
Note When you enable or disable new mobility, you must save the configuration and reboot the controller.
Step 2 To configure new mobility, select or unselect the Enable New Mobility (Converged Access) check box.
Note When you enable new mobility, you must save the configuration and reboot the controller.
Step 3 To configure the controller as Mobility Oracle, select or unselect the Mobility Oracle check box.
Note Mobility Oracle is optional; it maintains the client database under one complete mobility domain.
Step 4 To configure multicast mode in a mobility group, select or unselect the Multicast Mode check box.
Step 5 In the Multicast IP Address text box, enter the multicast IP address of the switch peer group.
Step 6 In the Mobility Oracle IP Address text box, enter the IP address of the Mobility Oracle.
You cannot enter a value for this field if you have checked the Mobility Oracle check box.
Step 7 In the Mobility Controller Public IP Address text box, enter the IP address of the controller, if there is no network
address translation (NAT).
Note If the controller has NAT configured, the public IP address will be the network address translated IP address.
Note New mobility does not support
IPv6.
Step 8 In the Mobility Keep Alive Count text box, enter the number of times a ping request is sent to a peer controller before
the peer is considered to be unreachable. The range is from 3 to 20. The default value is 3.
Step 9 In the Mobility Keep Alive Interval text box, enter the amount of time, in seconds, between each ping request sent to
an peer controller. The range is from 1 to 30 seconds. The default value is 10 seconds.
Step 10 In the Mobility DSCP text box, enter the DSCP value that you can set for the mobility controller. The range is from 0
to 63. The default value is 0.
Note While configuring the Mobility DSCP value, the mobility control socket (i.e control messages exchanged
between mobility peers only and not the data) is also updated. The configured value must reflect in the IPV4
header TOS field. This is a global configuration on the controller that is used to communicate among configured
mobility peers only.
Step 13 Choose Controller > Mobility Management > Mobility Controller to view all the mobility controllers and their details,
such as IP address, MAC address, client count, and link status.
Step 14 Choose Controller > Mobility Management > Mobility Clients to view all the mobility clients and their parameters.
Step 15 In the Client MAC Address and Client IP Address text boxes, enter the MAC address and IP address of the mobility
client, respectively.
Step 16 In the Anchor MC IP Address and Anchor MC Public IP Address text boxes, enter the IP address and public IP
address of the anchor Mobility Controller, respectively.
Step 17 In the Foreign MC IP Address and Foreign MC Public IP Address text boxes, enter the IP address and public IP
address of the foreign MC, respectively.
Step 18 In the Client Association Time text box, enter the time at which the mobility client should be associated with the Mobility
Controller.
Step 19 In the Client Entry Update Timestamp text box, enter the timestamp at which the client entry should be updated.
Note When you enable or disable new mobility, you must save the configuration and reboot the controller.
• Enable the Mobility Oracle or configure an external Mobility Oracle by entering this command:
config mobility oracle{enable| disable | ip ip_address}
Here, ip_address is the IP address of the Mobility Oracle. The Mobility Oracle maintains the client
database under one complete mobility domain. It consists of a station database, an interface to the
Mobility Controller, and an NTP/SNTP server. There can be only one Mobility Oracle in the entire
mobility domain.
• Create or delete switch peer groups by entering this command:
config mobility switchPeerGroup{create | delete} peer-group-name
Here, peer-group-name is the name of the switch peer group.
• Configure the MAC address of the member switch for compatibility between the flat (old) and new
mobility by entering this command:
config mobility group member add ip_address{[group-name] | mac-address | [public-ip-address]}
where ip_address is the IP address of the member.
group-name is the member switch group name, if it is different from the default group name.
Note If the controller has NAT configured, the public IP address will be the network address translated IP
address.
• Add or remove members and configure the bridge domain ID and multicast address of the switch peer
group by entering this command:
config mobility switchPeerGroup {bridge-domain-id peer-group-name bridge domain id | member
{add | delete} IP_address [public_IP_address] peer-group-name | multicast-address peer-group-name
multicast_IP_address}
Here, peer-group-name is the name of the switch peer group.
IP_address is the IP address of switch peer group member.
public_IP_address is the public IP address of the switch peer group member.
• View the details of the mobility controllers according to the Mobility Oracle by entering this command:
show mobility oracle summary
• View the summary and details of the Mobility Oracle client database by entering this command:
show mobility oracle client {summary | detail}
• Verify the mobility statistics by entering this command:
show mobility statistics
• Verify the mobility configuration by entering this command:
show mobility summary
• Save your changes by entering this command:
save config
• Enable or disable debugging of mobility packets by entering this command:
debug mobility packet {enable | disable}
• Enable or disable debugging of the Mobility Oracle events and errors by entering this command:
debug mobility oracle {events | errors} {enable| disable}
Burst Real-Time Rate parameter 132, 136, 647 Channel Announcement parameter 81
Channel Assignment Leader parameter 877
Channel Assignment Method parameter 875
Channel parameter 295, 898
C Channel Quiet Mode parameter 81
CA Server URL parameter 766 Channel Scan Duration parameter 879
CAC 153, 154, 156, 650 Channel Width Parameter 876
configuring for 7920 phones 650 Check Against CA Certificates parameter 437
enabling 153, 154 Check Certificate Date Validity parameter 437
using the CLI 154 chokepoints for RFID tag tracking 178
using the GUI 153 CIDS Sensor Add page 538
viewing using the CLI 156 CIDS Shun List page 538
capacity adder license. See licenses 51 ciphers 623, 624
CCKM 623, 966 configuring 623, 624
configuring 623 described 623
FlexConnect groups 966 Cisco 3300 Series Mobility Services Engine (MSE), using with
CCX 672, 839 wIPS 551
configuring Aironet IEs 672 Cisco 5500 Series Wireless LAN Controllers 303, 304, 320, 322
using the CLI 672 multiple AP-manager interfaces 320, 322
described 672 ports 303, 304
link test 839 Cisco 7921 Wireless IP Phones 649
viewing a client’s version 672 Cisco AV-pairs 695, 696
using the GUI 672 Cisco Centralized Key Management (CCKM). See CCKM 622
CCX Layer 2 client roaming 124, 125, 126, 127 Cisco Clean Access (CCA) 702
configuring 126 Cisco Discovery Protocol (CDP) 167, 169, 170, 171, 173
using the CLI 126 configuring 169, 170, 171
debugging using the CLI 127 using the CLI 170, 171
described 124, 125 using the GUI 169, 170
obtaining information using the CLI 126 described 167
CCX radio management 905 enabling using the GUI 169, 170
features 905 supported devices 167
flexconnect considerations 905 viewing neighbors 171, 173
CCX Version parameter 672 using the CLI 173
CCXv5 Req button 284 using the GUI 171, 173
CDP > AP Neighbors > Detail page 172 viewing traffic information 173
CDP > Interface Neighbors > Detail page 171 using the CLI 173
CDP > Traffic Metrics page 172 Cisco Discovery Protocol parameter 169
CDP Advertisement Version parameter 169 Cisco Licensing website 65
CDP AP Neighbors page 172 Cisco Logo parameter 232
CDP Protocol Status parameter 169 Cisco Unified Wireless Network (UWN) Solution 5
CDP State parameter 170 described 5
Certificate Authority (CA) certificates 202, 203, 204, 205, 435, 439 Cisco Wireless Solution 3
downloading 203, 204, 205 described 3
using the CLI 204, 205 Clear Filter link 578, 745, 775
using the GUI 203 Clear Stats button 1002
overview 202 Clear Stats on All APs button 774
using with local EAP 435, 439 CLI 32, 34, 35, 49, 261
Certificate File Name parameter 226 enabling wireless connections 49
Certificate File Path parameter 226 logging into 32
Certificate Issuer parameter 437 logging out 34
Certificate Password parameter 201, 226 navigating 34
Certificate Type parameter 769 troubleshooting commands 261
Change Rules Priority parameter 514 using 32, 35
Client Certificate Required parameter 437
client location, using Prime Infrastructure 7 Configuring Client Exclusion Policies (CLI) 484
client MFP 478 Configuring Client Exclusion Policies (GUI) 483
Client Protection parameter 480 Configuring Controller (GUI) 12
client reporting 284 Configuring Country Codes (CLI) 831
described 284 Configuring Country Codes (GUI) 830
client roaming, configuring 127 Configuring Coverage Hole Detection on a WLAN (GUI) 699
Client Type parameter 811 Configuring Dynamic Anchoring of Static IP Clients 1017
clients 672, 673, 855, 856, 957 Using the GUI 1017
connecting to WLANs 957 Configuring FlexConnect APs using the CLI. 955
viewing 855, 856 configuring for the debug facility 290
using the CLI 856 Configuring Layer2 ACLs - GUI 471
using the GUI 855, 856 Configuring Sniffing on an Access Point 294
viewing CCX version 672, 673 Using the GUI 294
using the CLI 673 Configuring Web Redirect (GUI) 697
using the GUI 672 Control and Provisioning of Wireless Access Points protocol
Clients > AP > Traffic Stream Metrics page 155 (CAPWAP) 735, 736, 739, 740
Clients > Detail page 811 debugging 740
viewing client details 811 described 735
viewing the status of workgroup bridges 811 restrictions 736
Commands > Reset to Factory Defaults page 181 viewing MTU information 739
Community Name parameter 91 Controller Time Source Valid parameter 480
conditional web redirect 695, 696 controllers 4, 5, 7, 8, 188, 190, 212, 740
described 696 configuration 212
Conditional Web Redirect parameter 697 saving 212
Configuration File Encryption parameter 209 discovery process 740
configuration files 209, 210, 213 multiple-controller deployment 5
downloading 209, 210 overview 7
using the GUI 209, 210 platforms 8
editing 213 single-controller deployment 4
configuration wizard 11, 23 upgrading software 188, 190
CLI version 23 using the CLI 190
described 11 using the GUI 188
Configuration Wizard - 802.11 Configuration page 21 core dump files 274
Configuration Wizard - Miscellaneous Configuration page 17 uploading from a 5500 series controller to a TFTP or FTP
Configuration Wizard - Set Time page 22 server 274
Configuration Wizard - SNMP Summary page 14, 16 Core Dump page 272
Configuration Wizard - System Information page 13 Country Code parameter 831
Configuration Wizard - Virtual Interface Configuration page 18 country codes 829, 832
Configuration Wizard Completed page 23 described 829
Configuration Wizard-Management Interface Configuration 16 viewing using the CLI 832
Configuration Wizard-System Information 15 Country page 831
Configure Dynamic Anchoring of Static IP Clients 1017 Coverage Exception Level per AP parameter 878
Using the CLI 1017 coverage hole detection 698, 878, 883
Configure option for RRM override 898 configuring per controller 878, 883
Configure RF Group 871 using the CLI 883
Using CLI 871 using the GUI 878
Configure RF Group Mode 870 disabling on a WLAN 698
Using GUI 870 described 698
Configuring a Spectrum Expert 933 coverage hole detection and correction 869
Configuring ACLs - GUI 463 Coverage Hole Detection Enabled parameter 699
Configuring Cisco Cleanair 919 CPUs, 5500 series controllers 259
Using the CLI 919 crash files 271
Configuring Cisco CleanAir 917 uploading 271
Using the GUI 917 using the CLI 271
Local Mode AP Fast Heartbeat Timer parameter 816 maximum local database entries 417
Local Net Users > New page 420 configuring using the GUI 417
local significant certificate (LSC) 766, 767 Maximum Local Database Entries parameter 417
configuring 766, 767 MCS data rates 78
using the GUI 766, 767 Member MAC Address parameter 998
described 766 memory 9
Local Significant Certificates (LSC) - AP Provisioning page 766 types 9
Local Significant Certificates (LSC) - General page 766 memory leaks, monitoring 277
local user database, capacity 215 Message Authentication Code Key (MACK) parameter 389
location 906 message logs 262, 264, 265, 268
calibration 906 configuring 262
login banner file 197, 198, 199, 200 using the GUI 262
clearing 200 viewing 264, 265, 268
described 197 using the CLI 268
downloading 198, 199 using the GUI 264, 265
using the CLI 199 Message parameter for web authentication 232
using the GUI 198 Metrics Collection parameter 152
logs 270, 271, 286 MFP Client Protection parameter 479
RSNA 286 MIC 631
uploading 270, 271 Min Failed Client Count per AP parameter 878
using the CLI 271 Minimum RSSI parameter 125
using the GUI 270 MMH MIC 632, 633
LWAPP-enabled access points 763, 764, 777, 778, 779, 781 configuring 632, 633
debug commands 777 mobility 987
disabling the reset button 781 overview 987
retrieving radio core dumps 777 Mobility Anchor Create button 1005
reverting to autonomous mode 763, 764 Mobility Anchors option 1005
sending crash information to controller 777 mobility anchors. See auto-anchor mobility 1003
uploading 778, 779 mobility groups 890, 991, 994, 995
access point core dumps 779 behavior in 995
radio core dumps 778, 779 difference from RF groups 890
illustrated 991
messaging among 994
mobility ping tests, running 1013
M MODE access point button 781
MAC address of access point 781 Mode parameter 125, 906
displayed on controller GUI 781 monitor intervals, configuring using the GUI 879
MAC filtering 595, 599 Monitoring 929
configuring on WLANs 595, 599 mpings 1014
management frame protection (MFP) 477 multicast client table, viewing 110
types 477 Multicast Groups page 109
Management Frame Protection parameter 480 multicast mode 103, 105, 106
management frame validation 478 described 103, 105
management interface 311 guidelines 106
described 311 Multicast Optimization 357
Management IP Address parameter 799 Multicast page 107
management over wireless 453 Multicast VLAN 357
described 453 using the GUI 357
Master Controller Configuration page 742 multiple country codes 831, 832
Master Controller Mode parameter 742 configuring 831, 832
Max RF Bandwidth parameter 151, 153 using the CLI 832
Max-Login Ignore Identity Response parameter 436 using the GUI 831
traffic stream metrics (TSM) 149, 155, 156, 158 User Access Mode parameter 216
described 149 User Attribute parameter 429
viewing statistics 155, 156, 158 User Base DN parameter 428
using the CLI 156, 158 User Credentials parameter 429
using the GUI 155 User Name parameter 420
Transfer Mode parameter 187, 194, 201, 203, 205, 208, 209, 239, 276 User Object Type parameter 429
downloading a CA certificate 203 User parameter 205
downloading a configuration file 209 User Profile Name parameter 220
downloading a customized web authentication login page 239 Username parameter 752, 756, 757
downloading a device certificate 201 Using CLI to monitor the Air quality 929
upgrading controller software 187, 194 Using GUI to monitor air quality 929
uploading a configuration file 208 using the GUI 465
uploading a PAC 205
uploading packet capture files 276
Transition Time parameter 126
transmit power 899
V
statically assigning using the CLI 899 Validate Rogue Clients Against AAA parameter 503
statically assigning using the GUI 899 Validity parameter 205
transmit power levels 899 VCI strings 771
transmit power threshold, decreasing 880 Verify Certificate CN Identity parameter 437
trap logs 799 virtual interface 323
for OfficeExtend access points 799 described 323
Trap Logs page 654 VLAN ID parameter 703, 953
troubleshooting 260, 278, 772, 776 VLAN Identifier parameter 318, 331
access point join process 772, 776 for AP-manager interface 318
CCXv5 clients 278 for dynamic interface 331
problems 260 VLAN Select 349
Troubleshooting OEAPs 299 VLANs 309, 329
tunnel attributes and identity networking 491 described 329
Tx Power Level Assignment parameter 902 guidelines 309
Type parameter 249, 575, 676 Voice RSSI parameter 878
voice settings 152
configuring 152
U using the GUI 152
voice-over-IP (VoIP) telephone roaming 124
U-APSD 149, 155, 156 VoIP calls, error codes 657
described 149 VoIP snooping 653
viewing status 155, 156 described 653
using the CLI 156 VoIP Snooping and Reporting parameter 654
using the GUI 155 VPN passthrough 642
UDP port 1013 configuring using the GUI 642
UDP, use in RADIUS 385
unicast mode 103
unique device identifier (UDI) 837, 838
described 837
W
retrieving 837, 838 Web Auth Type parameter 242, 249
using the CLI 838 web authentication 225, 226, 228, 231, 636
using the GUI 837, 838 certificate 225, 226
Upload button 206, 270, 276, 544 obtaining using the GUI 225, 226
Upload CSV File parameter 969 configuring a WLAN for 636
Upload File from Controller page 205, 208, 276, 778 using the GUI 636
USB console port, using on a 5500 series controller 337, 338 described 228
Use AES Key Wrap parameter 388 process 231