Cisco Systems 102087P Cisco Aironet 802.11ac Dual Band Access Points User Manual Wireless LAN Controller Configuration Guide Part1

Cisco Systems Inc Cisco Aironet 802.11ac Dual Band Access Points Wireless LAN Controller Configuration Guide Part1

Wireless LAN Controller Configuration Guide_Part1

Cisco Wireless LAN Controller Configuration Guide, Release 7.4First Published: January 08, 2013Last Modified: March 26, 2013Americas HeadquartersCisco Systems, Inc.170 West Tasman DriveSan Jose, CA 95134-1706USAhttp://www.cisco.comTel: 408 526-4000       800 553-NETS (6387)Fax: 408 527-0883Text Part Number: OL-28744-01
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 WITHTHE 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 versionof 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 OFMERCHANTABILITY, 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, WITHOUTLIMITATION, LOST PROFITS OR LOSS OR DAMAGE TO DATA ARISING OUT OF THE USE OR INABILITY TO USE THIS MANUAL, EVEN IF CISCO OR ITS SUPPLIERSHAVE 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, networktopology 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 unintentionaland 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 partnershiprelationship between Cisco and any other company. (1110R)©2013 Cisco Systems, Inc. All rights reserved.
CONTENTSPreface     Preface xlviiAudience xlviiConventions xlviiRelated Documentation xlviiiObtaining Documentation and Submitting a Service Request xlixPART I     System Management 1CHAPTER 1 Overview 3Cisco Wireless Overview 3Single-Controller Deployments 4Multiple-Controller Deployments 5Operating System Software 6Operating System Security 6Layer 2 and Layer 3 Operation 7Operational Requirements 7Configuration Requirements 7Cisco Wireless LAN Controllers 8Client Location 8Controller Platforms 8Cisco 2500 Series Controllers 8Cisco 5500 Series Controller 9Cisco Flex 7500 Series Controllers 9Cisco 8500 Series Controllers 9Cisco Virtual Wireless LAN Controllers 10Cisco Wireless Services Module 2 10Cisco Wireless Controller on Cisco Services-Ready Engine (SRE) 10Cisco Wireless LAN Controller Configuration Guide, Release 7.4       OL-28744-01 iii
Cisco UWN Solution WLANs 11File Transfers 11Power over Ethernet 11Cisco Wireless LAN Controller Memory 12Cisco Wireless LAN Controller Failover Protection 12CHAPTER 2 Getting Started 15Configuring the Controller Using the Configuration Wizard 15Connecting the Console Port of the Controller 16Configuring the Controller (GUI) 16Configuring the Controller—Using the CLI Configuration Wizard 27Using the Controller Web GUI 29Guidelines and Limitations 30Logging On to the Web GUI 30Logging out of the GUI 31Enabling Web and Secure Web Modes 31Enabling Web and Secure Web Modes (GUI) 31Enabling Web and Secure Web Modes (CLI) 32Loading an Externally Generated SSL Certificate 33Information About Externally Generated SSL Certificates 33Loading an SSL Certificate (GUI) 34Loading an SSL Certificate (CLI) 35Using the Controller CLI 36Logging on to the Controller CLI 36Guidelines and Limitations 36Using a Local Serial Connection 37Using a Remote Ethernet Connection 37Logging Out of the CLI 38Navigating the CLI 38Using the AutoInstall Feature for Controllers Without a Configuration 39Information About the AutoInstall Feature 39Guidelines and Limitations 40Obtaining an IP Address Through DHCP and Downloading a Configuration File froma TFTP Server 40Selecting a Configuration File 41   Cisco Wireless LAN Controller Configuration Guide, Release 7.4iv OL-28744-01  Contents
Example: AutoInstall Operation 42Managing the Controller System Date and Time 43Information About Controller System Date and Time 43Guidelines and Limitations 43Configuring an NTP Server to Obtain the Date and Time 43Configuring NTP Authentication (GUI) 44Configuring NTP Authentication (CLI) 44Configuring the Date and Time (GUI) 45Configuring the Date and Time (CLI) 46Configuring Telnet and Secure Shell Sessions 48Information About Telnet and SSH 48Restrictions for Telnet and SSH 48Configuring Telnet and SSH Sessions (GUI) 48Configuring Telnet and SSH Sessions (CLI) 49Troubleshooting Access Points Using Telnet or SSH_old 51Troubleshooting Access Points Using Telnet or SSH (GUI) 51Troubleshooting Access Points Using Telnet or SSH (CLI) 51Managing the Controller Wirelessly 52Enabling Wireless Connections (GUI) 52Enabling Wireless Connections (CLI) 53CHAPTER 3 Managing Licenses 55Installing and Configuring Licenses 55Information About Installing and Configuring Licenses 55Restrictions for Using Licenses 56Obtaining an Upgrade or Capacity Adder License 56Information About Obtaining an Upgrade or Capacity Adder License 56Obtaining and Registering a PAK Certificate 57Installing a License 58Installing a License (GUI) 58Installing a License (CLI) 59Viewing Licenses 59Viewing Licenses (GUI) 59Viewing Licenses (CLI) 60Troubleshooting Licensing Issues 63Cisco Wireless LAN Controller Configuration Guide, Release 7.4       OL-28744-01 vContents
Activating an AP-Count Evaluation License 63Information About Activating an AP-Count Evaluation License 63Activating an AP-Count Evaluation License (GUI) 63Activating an AP-Count Evaluation License (CLI) 64Configuring Right to Use Licensing 65Information About Right to Use Licensing 65Configuring Right to Use Licensing (GUI) 66Configuring Right to Use Licensing (CLI) 66Rehosting Licenses 67Information About Rehosting Licenses 67Rehosting a License 68Rehosting a License (GUI) 68Rehosting a License (CLI) 69Transferring Licenses to a Replacement Controller after an RMA 70Information About Transferring Licenses to a Replacement Controller after anRMA 70Transferring a License to a Replacement Controller after an RMA 71Configuring the License Agent 71Information About Configuring the License Agent 71Configuring the License Agent (GUI) 72Configuring the License Agent (CLI) 72CHAPTER 4 Configuring 802.11 Bands 75Configuring 802.11 Bands 75Information About Configuring 802.11 Bands 75Configuring the 802.11 Bands (GUI) 75Configuring the 802.11 Bands (CLI) 76Configuring Band Selection 78Information About Configuring Band Selection 78Restrictions on Band Selection 79Configuring Band Selection 80Configuring Band Selection (GUI) 80Configuring Band Selection (CLI) 80CHAPTER 5 Configuring 802.11 Parameters 83   Cisco Wireless LAN Controller Configuration Guide, Release 7.4vi OL-28744-01  Contents
Configuring the 802.11n Parameters 83Information About Configuring the 802.11n Parameters 83Configuring the 802.11n Parameters (GUI) 83Configuring the 802.11n Parameters (CLI) 84Configuring 802.11h Parameters 86Information About Configuring 802.11h Parameters 86Configuring the 802.11h Parameters (GUI) 86Configuring the 802.11h Parameters (CLI) 87CHAPTER 6 Configuring DHCP Proxy 89Information About Configuring DHCP Proxy 89Restrictions on Using DHCP Proxy 89Configuring DHCP Proxy (GUI) 90Configuring DHCP Proxy (GUI) 90Configuring DHCP Proxy (CLI) 90Configuring DHCP Proxy (CLI) 91Configuring a DHCP Timeout (GUI) 91Configuring a DHCP Timeout (CLI) 91CHAPTER 7 Configuring SNMP 93Configuring SNMP (CLI) 93SNMP Community Strings 95Changing the SNMP Community String Default Values (GUI) 95Changing the SNMP Community String Default Values (CLI) 95Configuring Real Time Statistics (CLI) 96SNMP Trap Enhancements 96CHAPTER 8 Configuring Aggressive Load Balancing 97Information About Configuring Aggressive Load Balancing 97Configuring Aggressive Load Balancing (GUI) 98Configuring Aggressive Load Balancing (CLI) 98CHAPTER 9 Configuring Fast SSID Changing 101Information About Configuring Fast SSID Changing 101Configuring Fast SSID Changing (GUI) 101Cisco Wireless LAN Controller Configuration Guide, Release 7.4       OL-28744-01 viiContents
Configuring Fast SSID Changing (CLI) 101CHAPTER 10 Configuring 802.3 Bridging 103Configuring 802.3 Bridging 103Information About Configuring 802.3 Bridging 103Restrictions on 802.3 Bridging 103Configuring 802.3 Bridging 104Configuring 802.3 Bridging (GUI) 104Configuring 802.3 Bridging (CLI) 104Enabling 802.3X Flow Control 104CHAPTER 11 Configuring Multicast 105Configuring Multicast Mode 105Information About Multicast Mode 105Restrictions for Configuring Multicast Mode 107Enabling Multicast Mode (GUI) 108Enabling Multicast Mode (CLI) 108Viewing Multicast Groups (GUI) 109Viewing Multicast Groups (CLI) 110Viewing an Access Point’s Multicast Client Table (CLI) 110Configuring Multicast Domain Name System 111Information About Multicast Domain Name System 111Restrictions for Configuring Multicast DNS 111Configuring Multicast DNS (GUI) 111Configuring Multicast DNS (CLI) 113CHAPTER 12 Configuring Client Roaming 115Information About Client Roaming 115Inter-Controller Roaming 115Intra-Controller Roaming 115Inter-Subnet Roaming 116Voice-over-IP Telephone Roaming 116CCX Layer 2 Client Roaming 116Guidelines and Limitations 117Configuring CCX Client Roaming Parameters (GUI) 117   Cisco Wireless LAN Controller Configuration Guide, Release 7.4viii OL-28744-01  Contents
Configuring CCX Client Roaming Parameters (CLI) 118Obtaining CCX Client Roaming Information (CLI) 118Debugging CCX Client Roaming Issues (CLI) 119CHAPTER 13 Configuring IP-MAC Address Binding 121Information About Configuring IP-MAC Address Binding 121Configuring IP-MAC Address Binding (CLI) 121CHAPTER 14 Configuring Quality of Service 123Configuring Quality of Service 123Information About Quality of Service 123Configuring Quality of Service Profiles 124Configuring QoS Profiles (GUI) 124Configuring QoS Profiles (CLI) 125Configuring Quality of Service Roles 126Information About Quality of Service Roles 126Configuring QoS Roles 127Configuring QoS (GUI) 127Configuring QoS Roles (CLI) 128CHAPTER 15 Configuring Application Visibility and Control 131Information About Application Visibility and Control 131Restrictions for Application Visibility and Control 131Configuring Application Visibility and Control (GUI) 132Configuring Application Visibility and Control (CLI) 133Configuring NetFlow 134Information About NetFlow 134Configuring NetFlow (GUI) 134Configuring NetFlow (CLI) 134CHAPTER 16 Configuring Media and EDCA Parameters 137Configuring Voice and Video Parameters 137Information About Configuring Voice and Video Parameters 137Call Admission Control 137Bandwidth-Based CAC 138Cisco Wireless LAN Controller Configuration Guide, Release 7.4       OL-28744-01 ixContents
Load-Based CAC 138Expedited Bandwidth Requests 138U-APSD 139Traffic Stream Metrics 139Configuring Voice Parameters 140Configuring Voice Parameters (GUI) 140Configuring Voice Parameters (CLI) 142Configuring Video Parameters 143Configuring Video Parameters (GUI) 143Configuring Video Parameters (CLI) 144Viewing Voice and Video Settings 145Viewing Voice and Video Settings (GUI) 145Viewing Voice and Video Settings (CLI) 146Configuring SIP-Based CAC 149Restrictions for SIP-Based CAC 149Configuring SIP-Based CAC (GUI) 149Configuring SIP-Based CAC (CLI) 150Configuring Media Parameters 151Configuring Media Parameters (GUI) 151Configuring Voice Prioritization Using Preferred Call Numbers 151Information About Configuring Voice Prioritization Using Preferred Call Numbers 151Prerequisites for Configuring Voice Prioritization Using Preferred Call Numbers 152Configuring a Preferred Call Number (GUI) 152Configuring a Preferred Call Number (CLI) 152Configuring EDCA Parameters 153Information About EDCA Parameters 153Configuring EDCA Parameters (GUI) 153Configuring EDCA Parameters (CLI) 154CHAPTER 17 Configuring the Cisco Discovery Protocol 157Information About Configuring the Cisco Discovery Protocol 157Restrictions for Configuring the Cisco Discovery Protocol 157Configuring the Cisco Discovery Protocol 159Configuring the Cisco Discovery Protocol (GUI) 159Configuring the Cisco Discovery Protocol (CLI) 160   Cisco Wireless LAN Controller Configuration Guide, Release 7.4xOL-28744-01  Contents
Viewing Cisco Discovery Protocol Information 161Viewing Cisco Discovery Protocol Information (GUI) 161Viewing Cisco Discovery Protocol Information (CLI) 163Getting CDP Debug Information 163CHAPTER 18 Configuring Authentication for the Controller and NTP Server 165Information About Configuring Authentication for the Controller and NTP Server 165Configuring the NTP Server for Authentication (GUI) 165Configuring the NTP Server for Authentication (CLI) 166CHAPTER 19 Configuring RFID Tag Tracking 167Information About Configuring RFID Tag Tracking 167Configuring RFID Tag Tracking (CLI) 168Viewing RFID Tag Tracking Information (CLI) 169Debugging RFID Tag Tracking Issues (CLI) 169CHAPTER 20 Resetting the Controller to Default Settings 171Information About Resetting the Controller to Default Settings 171Resetting the Controller to Default Settings (GUI) 171Resetting the Controller to Default Settings (CLI) 172CHAPTER 21 Managing Controller Software and Configurations 173Upgrading the Controller Software 173Restrictions for Upgrading Controller Software 173Upgrading Controller Software (GUI) 176Upgrading Controller Software (CLI) 178Predownloading an Image to an Access Point 180Access Point Predownload Process 180Restrictions for Predownloading an Image to an Access Point 181Predownloading an Image to Access Points—Global Configuration (GUI) 182Configuring Predownload Image to an Access Point (GUI) 183Predownloading an Image to Access Points (CLI) 185Transferring Files to and from a Controller 187Downloading a Login Banner File 187Downloading a Login Banner File (GUI) 188Cisco Wireless LAN Controller Configuration Guide, Release 7.4       OL-28744-01 xiContents
Downloading a Login Banner File (CLI) 189Clearing the Login Banner (GUI) 190Downloading Device Certificates 190Downloading Device Certificates (GUI) 191Downloading Device Certificates (CLI) 192Downloading CA Certificates 193Download CA Certificates (GUI) 193Downloading CA Certificates (CLI) 194Uploading PACs 195Uploading PACs (GUI) 195Uploading PACs (CLI) 196Uploading and Downloading Configuration Files 197Uploading Configuration Files 197Uploading the Configuration Files (GUI) 198Uploading the Configuration Files (CLI) 198Downloading Configuration Files 199Downloading the Configuration Files (GUI) 199Downloading the Configuration Files (CLI) 200Saving Configurations 202Editing Configuration Files 202Clearing the Controller Configuration 203Erasing the Controller Configuration 203Resetting the Controller 204CHAPTER 22 Managing User Accounts 205Configuring Guest User Accounts 205Information About Creating Guest Accounts 205Restrictions for Managing User Accounts 205Creating a Lobby Ambassador Account 205Creating a Lobby Ambassador Account (GUI) 205Creating a Lobby Ambassador Account (CLI) 206Creating Guest User Accounts as a Lobby Ambassador (GUI) 207Viewing Guest User Accounts 208Viewing the Guest Accounts (GUI) 208Viewing the Guest Accounts (CLI) 208   Cisco Wireless LAN Controller Configuration Guide, Release 7.4xii OL-28744-01  Contents
Configuring Administrator Usernames and Passwords 208Information About Configuring Administrator Usernames and Passwords 208Configuring Usernames and Passwords (GUI) 208Configuring Usernames and Passwords (CLI) 209Restoring Passwords 209Changing the Default Values for SNMP v3 Users 210Information About Changing the Default Values for SNMP v3 Users 210Changing the SNMP v3 User Default Values (GUI) 210Changing the SNMP v3 User Default Values (CLI) 211CHAPTER 23 Managing Web Authentication 213Obtaining a Web Authentication Certificate 213Information About Web Authentication Certificates 213Obtaining a Web Authentication Certificate (GUI) 213Obtaining a Web Authentication Certificate (CLI) 214Web Authentication Process 215Disabling Security Alert for Web Authentication Process 216Choosing the Default Web Authentication Login Page 218Information About Default Web Authentication Login Page 218Choosing the Default Web Authentication Login Page (GUI) 219Choosing the Default Web Authentication Login Page (CLI) 219Example: Creating a Customized Web Authentication Login Page 221Example: Modified Default Web Authentication Login Page Example 224Using a Customized Web Authentication Login Page from an External Web Server 224Information About Customized Web Authentication Login Page 224Choosing a Customized Web Authentication Login Page from an External Web Server(GUI) 225Choosing a Customized Web Authentication Login Page from an External Web Server(CLI) 225Downloading a Customized Web Authentication Login Page 225Prerequisites for Downloading a Customized Web Authentication Login Page 226Downloading a Customized Web Authentication Login Page (GUI) 226Downloading a Customized Web Authentication Login Page (CLI) 227Example: Customized Web Authentication Login Page 228Verifying the Web Authentication Login Page Settings (CLI) 228Cisco Wireless LAN Controller Configuration Guide, Release 7.4       OL-28744-01 xiiiContents
Assigning Login, Login Failure, and Logout Pages per WLAN 229Information About Assigning Login, Login Failure, and Logout Pages per WLAN 229Assigning Login, Login Failure, and Logout Pages per WLAN (GUI) 229Assigning Login, Login Failure, and Logout Pages per WLAN (CLI) 230CHAPTER 24 Configuring Wired Guest Access 233Information About Wired Guest Access 233Prerequisites for Configuring Wired Guest Access 234Restrictions for Configuring Wired Guest Access 234Configuring Wired Guest Access (GUI) 235Configuring Wired Guest Access (CLI) 236Supporting IPv6 Client Guest Access 238CHAPTER 25 Troubleshooting 241Interpreting LEDs 241Information About Interpreting LEDs 241Interpreting Controller LEDs 242Interpreting Lightweight Access Point LEDs 242System Messages 242Information About System Messages 242Viewing System Resources 245Information About Viewing System Resources 245Viewing System Resources (GUI) 246Viewing System Resources (CLI) 246Using the CLI to Troubleshoot Problems 246Configuring System and Message Logging 247Information About System and Message Logging 247Configuring System and Message Logging (GUI) 248Viewing Message Logs (GUI) 250Configuring System and Message Logging (CLI) 251Viewing System and Message Logs (CLI) 254Viewing Access Point Event Logs 254Information About Access Point Event Logs 254Viewing Access Point Event Logs (CLI) 254Uploading Logs and Crash Files 255   Cisco Wireless LAN Controller Configuration Guide, Release 7.4xiv OL-28744-01  Contents
Prerequisites to Upload Logs and Crash Files 255Uploading Logs and Crash Files (GUI) 255Uploading Logs and Crash Files (CLI) 256Uploading Core Dumps from the Controller 257Information About Uploading Core Dumps from the Controller 257Configuring the Controller to Automatically Upload Core Dumps to an FTP Server(GUI) 258Configuring the Controller to Automatically Upload Core Dumps to an FTP Server(CLI) 258Uploading Core Dumps from Controller to a Server (CLI) 259Uploading Packet Capture Files 260Information About Uploading Packet Capture Files 260Restrictions for Uploading Packet Capture Files 261Uploading Packet Capture Files (GUI) 262Uploading Packet Capture Files (CLI) 262Monitoring Memory Leaks 263Monitoring Memory Leaks (CLI) 263Troubleshooting CCXv5 Client Devices 264Information About Troubleshooting CCXv5 Client Devices 264Restrictions for CCXv5 Client Devices 264Configuring Diagnostic Channel 265Configuring the Diagnostic Channel (GUI) 265Configuring the Diagnostic Channel (CLI) 266Configuring Client Reporting 270Configuring Client Reporting (GUI) 270Configuring Client Reporting (CLI) 270Configuring Roaming and Real-Time Diagnostics 271Configuring Roaming and Real-Time Diagnostics (CLI) 271Using the Debug Facility 274Information About Using the Debug Facility 274Configuring the Debug Facility (CLI) 275Configuring Wireless Sniffing 279Information About Wireless Sniffing 279Prerequisites for Wireless Sniffing 279Restrictions for Wireless Sniffing 279Cisco Wireless LAN Controller Configuration Guide, Release 7.4       OL-28744-01 xvContents
Configuring Sniffing on an Access Point (GUI) 280Configuring Sniffing on an Access Point (CLI) 280Troubleshooting Access Points Using Telnet or SSH_old 281Information About Troubleshooting Access Points Using Telnet or SSH 281Troubleshooting Access Points Using Telnet or SSH (GUI) 282Troubleshooting Access Points Using Telnet or SSH (CLI) 282Debugging the Access Point Monitor Service 283Information About Debugging the Access Point Monitor Service 283Debugging Access Point Monitor Service Issues (CLI) 283Troubleshooting OfficeExtend Access Points 284Information About Troubleshooting OfficeExtend Access Points 284Interpreting OfficeExtend LEDs 284Positioning OfficeExtend Access Points for Optimal RF Coverage 284Troubleshooting Common Problems 284PART II     Configuring Ports and Interfaces 287CHAPTER 26 Overview of Ports and Interfaces 289Information About Ports 289Information About Distribution System Ports 290Restrictions for Configuring Distribution System Ports 290Information About Service Port 291Information About Interfaces 291Restrictions for Configuring Interfaces 292Information About Dynamic AP Management 292Information About WLANs 293CHAPTER 27 Configuring the Management Interface 295Information About the Management Interface 295Configuring the Management Interface (GUI) 296Configuring the Management Interface (CLI) 297CHAPTER 28 Configuring the AP-Manager Interface 299Information the About AP-Manager Interface 299Restrictions for Configuring AP Manager Interfaces 299   Cisco Wireless LAN Controller Configuration Guide, Release 7.4xvi OL-28744-01  Contents
Configuring the AP-Manager Interface (GUI) 300Configuring the AP Manager Interface (CLI) 300Configuration Example: Configuring AP-Manager on a Cisco 5500 Series Controller 301CHAPTER 29 Configuring Virtual Interfaces 305Information About the Virtual Interface 305Configuring Virtual Interfaces (GUI) 306Configuring Virtual Interfaces (CLI) 306CHAPTER 30 Configuring Service-Port Interfaces 307Information About Service-Port Interfaces 307Restrictions for Configuring Service-Port Interfaces 307Configuring Service-Port Interfaces (GUI) 307Configuring Service-Port Interfaces (CLI) 308CHAPTER 31 Configuring Dynamic Interfaces 309Information About Dynamic Interface 309Pre - requisites for Configuring Dynamic Interfaces 310Restrictions for Configuring Dynamic Interfaces 310Configuring Dynamic Interfaces (GUI) 310Configuring Dynamic Interfaces (CLI) 312CHAPTER 32 Configuring Ports 315Configuring Ports (GUI) 315CHAPTER 33 Information About Using Cisco 5500 Series Controller USB Console Port 317USB Console OS Compatibility 317Changing the Cisco USB Systems Management Console COM Port to an Unused Port 318CHAPTER 34 Configuring Link Aggregation 319Information About Link Aggregation 319Restrictions for Link Aggregation 319Enabling Link Aggregation (GUI) 321Enabling Link Aggregation (CLI) 321Verifying Link Aggregation Settings (CLI) 322Cisco Wireless LAN Controller Configuration Guide, Release 7.4       OL-28744-01 xviiContents
Configuring Neighbor Devices to Support Link Aggregation 322Choosing Between Link Aggregation and Multiple AP-Manager Interfaces 322CHAPTER 35 Configuring Multiple AP-Manager Interfaces 323Information About Multiple AP-Manager Interfaces 323Restrictions for Configuring Multiple AP Manager Interfaces 323Creating Multiple AP-Manager Interfaces (GUI) 324Creating Multiple AP-Manager Interfaces (CLI) 324CHAPTER 36 Configuring VLAN Select 327Information About VLAN Select 327Restrictions for Configuring VLAN Select 328Configuring Interface Groups 328Information About Interface Groups 328Restrictions for Configuring Interface Groups 328Creating Interface Groups (GUI) 328Creating Interface Groups (CLI) 329Adding Interfaces to Interface Groups (GUI) 329Adding Interfaces to Interface Groups (CLI) 329Viewing VLANs in Interface Groups (CLI) 330Adding an Interface Group to a WLAN (GUI) 330Adding an Interface Group to a WLAN (CLI) 330CHAPTER 37 Configuring Interface Groups 331Information About Interface Groups 331Restrictions for Configuring Interface Groups 332Creating Interface Groups (GUI) 332Creating Interface Groups (CLI) 332Adding Interfaces to Interface Groups (GUI) 333Adding Interfaces to Interface Groups (CLI) 333Viewing VLANs in Interface Groups (CLI) 333Adding an Interface Group to a WLAN (GUI) 333Adding an Interface Group to a WLAN (CLI) 334CHAPTER 38 Configuring Multicast Optimization 335   Cisco Wireless LAN Controller Configuration Guide, Release 7.4xviii OL-28744-01  Contents
Information About Multicast Optimization 335Configuring a Multicast VLAN (GUI) 335Configuring a Multicast VLAN (CLI) 336PART III     Configuring VideoStream 337CHAPTER 39 Configuring VideoStream 339Information about VideoStream 339Prerequisites for VideoStream 339Restrictions for Configuring VideoStream 339Configuring VideoStream (GUI) 340Configuring VideoStream (CLI) 343Viewing and Debugging Media Streams 344PART IV     Configuring Security Solutions 347CHAPTER 40 Cisco Unified Wireless Network Solution Security 349Security Overview 349Layer 1 Solutions 349Layer 2 Solutions 349Restrictions for Layer 2 Solutions 350Layer 3 Solutions 350Integrated Security Solutions 350CHAPTER 41 Configuring RADIUS 351Information About RADIUS 351Configuring RADIUS on the ACS 353Configuring RADIUS (GUI) 354Configuring RADIUS (CLI) 358RADIUS Authentication Attributes Sent by the Controller 361Authentication Attributes Honored in Access-Accept Packets (Airespace) 364RADIUS Accounting Attributes 371CHAPTER 42 Configuring TACACS+ 373Information About TACACS+ 373Cisco Wireless LAN Controller Configuration Guide, Release 7.4       OL-28744-01 xixContents
TACACS+ VSA 375Configuring TACACS+ on the ACS 376Configuring TACACS+ (GUI) 378Configuring TACACS+ (CLI) 379Viewing the TACACS+ Administration Server Logs 380CHAPTER 43 Configuring Maximum Local Database Entries 383Information About Configuring Maximum Local Database Entries 383Configuring Maximum Local Database Entries (GUI) 383Configuring Maximum Local Database Entries (CLI) 384CHAPTER 44 Configuring Local Network Users on the Controller 385Information About Local Network Users on Controller 385Configuring Local Network Users for the Controller (GUI) 385Configuring Local Network Users for the Controller (CLI) 386CHAPTER 45 Configuring Password Policies 389Information About Password Policies 389Configuring Password Policies (GUI) 390Configuring Password Policies (CLI) 390CHAPTER 46 Configuring LDAP 393Information About LDAP 393Configuring LDAP (GUI) 394Configuring LDAP (CLI) 396CHAPTER 47 Configuring Local EAP 399Information About Local EAP 399Restrictions for Local EAP 400Configuring Local EAP (GUI) 401Configuring Local EAP (CLI) 404CHAPTER 48 Configuring the System for SpectraLink NetLink Telephones 409Information About SpectraLink NetLink Telephones 409Configuring SpectraLink NetLink Phones 409   Cisco Wireless LAN Controller Configuration Guide, Release 7.4xx OL-28744-01  Contents
Enabling Long Preambles (GUI) 409Enabling Long Preambles (CLI) 410Configuring Enhanced Distributed Channel Access (CLI) 410CHAPTER 49 Configuring RADIUS NAC Support 413Information About RADIUS NAC Support 413Device Registration 414Central Web Authentication 414Local Web Authentication 414Restrictions for RADIUS NAC Support 414Configuring RADIUS NAC Support (GUI) 415Configuring RADIUS NAC Support (CLI) 416CHAPTER 50 Using Management Over Wireless 417Information About Management over Wireless 417Enabling Management over Wireless (GUI) 417Enabling Management over Wireless (CLI) 417CHAPTER 51 Using Dynamic Interfaces for Management 419Information About Using Dynamic Interfaces for Management 419Configuring Management using Dynamic Interfaces (CLI) 420CHAPTER 52 Configuring DHCP Option 82 421Information About DHCP Option 82 421Restrictions for DHCP Option 82 422Configuring DHCP Option 82 (GUI) 422Configuring DHCP Option 82 (CLI) 422CHAPTER 53 Configuring and Applying Access Control Lists 425Information About Access Control Lists 425Restrictions for Access Control Lists 425Configuring and Applying Access Control Lists (GUI) 426Configuring Access Control Lists 426Applying an Access Control List to an Interface 428Applying an Access Control List to the Controller CPU 429Cisco Wireless LAN Controller Configuration Guide, Release 7.4       OL-28744-01 xxiContents
Applying an Access Control List to a WLAN 429Applying a Preauthentication Access Control List to a WLAN 430Configuring and Applying Access Control Lists (CLI) 430Configuring Access Control Lists 430Applying Access Control Lists 431CHAPTER 54 Configuring Management Frame Protection 433Information About Management Frame Protection 433Restrictions for Management Frame Protection 435Configuring Management Frame Protection (GUI) 435Viewing the Management Frame Protection Settings (GUI) 435Configuring Management Frame Protection (CLI) 436Viewing the Management Frame Protection Settings (CLI) 436Debugging Management Frame Protection Issues (CLI) 436CHAPTER 55 Configuring Client Exclusion Policies 439Configuring Client Exclusion Policies (GUI) 439Configuring Client Exclusion Policies (CLI) 440CHAPTER 56 Configuring Identity Networking 443Information About Identity Networking 443RADIUS Attributes Used in Identity Networking 444CHAPTER 57 Configuring AAA Override 449Information About AAA Override 449Restrictions for AAA Override 449Updating the RADIUS Server Dictionary File for Proper QoS Values 450Configuring AAA Override (GUI) 451Configuring AAA Override (CLI) 451CHAPTER 58 Managing Rogue Devices 453Information About Rogue Devices 453Configuring Rogue Detection (GUI) 456Configuring Rogue Detection (CLI) 457   Cisco Wireless LAN Controller Configuration Guide, Release 7.4xxii OL-28744-01  Contents
CHAPTER 59 Classifying Rogue Access Points 461Information About Classifying Rogue Access Points 461Restrictions for Classifying Rogue Access Points 463Configuring Rogue Classification Rules (GUI) 464Viewing and Classifying Rogue Devices (GUI) 466Configuring Rogue Classification Rules (CLI) 469Viewing and Classifying Rogue Devices (CLI) 471CHAPTER 60 Configuring Cisco TrustSec SXP 475Information About Cisco TrustSec SXP 475Restrictions for Cisco TrustSec SXP 476Configuring Cisco TrustSec SXP (GUI) 477Creating a New SXP Connection (GUI) 477Configuring Cisco TrustSec SXP (CLI) 478CHAPTER 61 Configuring Cisco Intrusion Detection System 481Information About Cisco Intrusion Detection System 481Shunned Clients 481Additional Information 482Configuring IDS Sensors (GUI) 482Viewing Shunned Clients (GUI) 483Configuring IDS Sensors (CLI) 483Viewing Shunned Clients (CLI) 484CHAPTER 62 Configuring IDS Signatures 487Information About IDS Signatures 487Configuring IDS Signatures (GUI) 489Uploading or Downloading IDS Signatures 489Enabling or Disabling IDS Signatures 490Viewing IDS Signature Events (GUI) 492Configuring IDS Signatures (CLI) 493Viewing IDS Signature Events (CLI) 494CHAPTER 63 Configuring wIPS 497Cisco Wireless LAN Controller Configuration Guide, Release 7.4       OL-28744-01 xxiiiContents
Information About wIPS 497Restrictions for wIPS 503Configuring wIPS on an Access Point (GUI) 503Configuring wIPS on an Access Point (CLI) 504Viewing wIPS Information (CLI) 505CHAPTER 64 Configuring the Wi-Fi Direct Client Policy 507Information About the Wi-Fi Direct Client Policy 507Restrictions for the Wi-Fi Direct Client Policy 507Configuring the Wi-Fi Direct Client Policy (GUI) 507Configuring the Wi-Fi Direct Client Policy (CLI) 508Monitoring and Troubleshooting the Wi-Fi Direct Client Policy (CLI) 508CHAPTER 65 Configuring Web Auth Proxy 509Information About the Web Authentication Proxy 509Configuring the Web Authentication Proxy (GUI) 510Configuring the Web Authentication Proxy (CLI) 510CHAPTER 66 Detecting Active Exploits 513Detecting Active Exploits 513PART V     Working with WLANs 515CHAPTER 67 Overview 517Information About WLANs 517Prerequisites for WLANs 517Restrictions for WLANs 518CHAPTER 68 Configuring WLANs 521Prerequisites for WLANs 521Restrictions for WLANs 522Information About WLANs 523Creating and Removing WLANs (GUI) 523Enabling and Disabling WLANs (GUI) 524Creating and Deleting WLANs (CLI) 524   Cisco Wireless LAN Controller Configuration Guide, Release 7.4xxiv OL-28744-01  Contents
Enabling and Disabling WLANs (CLI) 525Viewing WLANs (CLI) 525Searching WLANs (GUI) 526Assigning WLANs to Interfaces 526Configuring Network Access Identifier (CLI) 526CHAPTER 69 Setting the Client Count per WLAN 529Restrictions for Setting Client Count for WLANs 529Information About Setting the Client Count per WLAN 530Configuring the Client Count per WLAN (GUI) 530Configuring the Maximum Number of Clients per WLAN (CLI) 530Configuring the Maximum Number of Clients for each AP Radio per WLAN (GUI) 531Configuring the Maximum Number of Clients for each AP Radio per WLAN (CLI) 531CHAPTER 70 Configuring DHCP 533Restrictions for Configuring DHCP for WLANs 533Information About the Dynamic Host Configuration Protocol 533Internal DHCP Servers 533External DHCP Servers 534DHCP Assignments 534Configuring DHCP (GUI) 535Configuring DHCP (CLI) 536Debugging DHCP (CLI) 536CHAPTER 71 Configuring DHCP Scopes 537Restrictions for Configuring DHCP Scopes 537Information About DHCP Scopes 537Configuring DHCP Scopes (GUI) 537Configuring DHCP Scopes (CLI) 538CHAPTER 72 Configuring MAC Filtering for WLANs 541Restrictions for MAC Filtering 541Information About MAC Filtering of WLANs 541Enabling MAC Filtering 541Cisco Wireless LAN Controller Configuration Guide, Release 7.4       OL-28744-01 xxvContents
CHAPTER 73 Configuring Local MAC Filters 543Prerequisites for Configuring Local MAC Filters 543Information About Local MAC Filters 543Configuring Local MAC Filters (CLI) 543CHAPTER 74 Configuring Timeouts 545Configuring a Timeout for Disabled Clients 545Information About Configuring a Timeout for Disabled Clients 545Configuring Timeout for Disabled Clients (CLI) 545Configuring Session Timeout 545Information About Session Timeouts 545Configuring a Session Timeout (GUI) 546Configuring a Session Timeout (CLI) 546Configuring the User Idle Timeout 547Information About the User Idle Timeout Per WLAN 547Configuring Per-WLAN User Idle Timeout (CLI) 547CHAPTER 75 Configuring the DTIM Period 549Information About DTIM Period 549Configuring the DTIM Period (GUI) 550Configuring the DTIM Period (CLI) 550CHAPTER 76 Configuring Peer-to-Peer Blocking 551Restrictions for Peer-to-Peer Blocking 551Information About Peer-to-Peer Blocking 551Configuring Peer-to-Peer Blocking (GUI) 552Configuring Peer-to-Peer Blocking (CLI) 552CHAPTER 77 Configuring Layer2 Security 555Prerequisites for Layer 2 Security 555Configuring Static WEP Keys (CLI) 556Configuring Dynamic 802.1X Keys and Authorization (CLI) 556Configuring 802.11r BSS Fast Transition 557Restrictions for 802.11r Fast Transition 557   Cisco Wireless LAN Controller Configuration Guide, Release 7.4xxvi OL-28744-01  Contents
Information About 802.11r Fast Transition 558Configuring 802.11r Fast Transition (GUI) 560Configuring 802.11r Fast Transition (CLI) 561Troubleshooting 802.11r BSS Fast Transition 562Configuring MAC Authentication Failover to 802.1X Authentication 562Configuring MAC Authentication Failover to 802.1x Authentication (GUI) 562Configuring MAC Authentication Failover to 802.1X Authentication (CLI) 562Configuring 802.11w 563Restrictions for 802.11w 563Information About 802.11w 563Configuring 802.11w (GUI) 564Configuring 802.11w (CLI) 565CHAPTER 78 Configuring a WLAN for Both Static and Dynamic WEP 567Restrictions for Configuring Static and Dynamic WEP 567Information About WLAN for Both Static and Dynamic WEP 567WPA1 and WPA2 568Configuring WPA1 +WPA2 569Configuring WPA1+WPA2 (GUI) 569Configuring WPA1+WPA2 (CLI) 569CHAPTER 79 Configuring Sticky Key Caching 571Information About Sticky Key Caching 571Restrictions for Sticky Key Caching 571Configuring Sticky Key Caching (CLI) 572CHAPTER 80 Configuring CKIP 575Information About CKIP 575Configuring CKIP (GUI) 576Configuring CKIP (CLI) 576CHAPTER 81 Configuring Layer 3 Security 579Configuring Layer 3 Security Using VPN Passthrough 579Restrictions for Layer 3 Security Using VPN Passthrough 579Information About VPN Passthrough 579Cisco Wireless LAN Controller Configuration Guide, Release 7.4       OL-28744-01 xxviiContents
Configuring VPN Passthrough 580Configuring VPN Passthrough (GUI) 580Configuring VPN Passthrough (CLI) 580Configuring Layer 3 Security Using Web Authentication 580Prerequisites for Configuring Web Authentication on a WLAN 580Restrictions for Configuring Web Authentication on a WLAN 581Information About Web Authentication 581Configuring Web Authentication 582Configuring Web Authentication (GUI) 582Configuring Web Authentication (CLI) 582CHAPTER 82 Configuring Captive Bypassing 583Information About Captive Bypassing 583Configuring Captive Bypassing (CLI) 584CHAPTER 83 Configuring a Fallback Policy with MAC Filtering and Web Authentication 585Information About Fallback Policy with MAC Filtering and Web Authentication 585Configuring a Fallback Policy with MAC Filtering and Web Authentication (GUI) 585Configuring a Fallback Policy with MAC Filtering and Web Authentication (CLI) 586CHAPTER 84 Assigning QoS Profiles 587Information About QoS Profiles 587Assigning a QoS Profile to a WLAN (GUI) 588Assigning a QoS Profile to a WLAN (CLI) 589CHAPTER 85 Configuring QoS Enhanced BSS 591Prerequisites for Using QoS Enhanced BSS on Cisco 7921 and 7920 Wireless IPPhones 591Restrictions for QoS Enhanced BSS 592Information About QoS Enhanced BSS 592Configuring QBSS (GUI) 593Configuring QBSS (CLI) 593CHAPTER 86 Configuring Media Session Snooping and Reporting 595Restrictions for Media Session Snooping and Reporting 595   Cisco Wireless LAN Controller Configuration Guide, Release 7.4xxviii OL-28744-01  Contents
Information About Media Session Snooping and Reporting 595Configuring Media Session Snooping (GUI) 596Configuring Media Session Snooping (CLI) 596CHAPTER 87 Configuring Key Telephone System-Based CAC 601Restrictions for Key Telephone System-Based CAC 601Information About Key Telephone System-Based CAC 601Configuring KTS-based CAC (GUI) 602Configuring KTS-based CAC (CLI) 602Related Commands 603CHAPTER 88 Configuring Reanchoring of Roaming Voice Clients 605Restrictions for Configuring Reanchoring of Roaming Voice Clients 605Information About Reanchoring of Roaming Voice Clients 605Configuring Reanchoring of Roaming Voice Clients (GUI) 606Configuring Reanchoring of Roaming Voice Clients (CLI) 606CHAPTER 89 Configuring Seamless IPv6 Mobility 607Prerequisites for Configuring IPv6 Mobility 607Restrictions for Configuring IPv6 Mobility 607Information About IPv6 Mobility 608Configuring IPv6 Globally 608Configuring IPv6 Globally (GUI) 608Configuring IPv6 Globally (CLI) 608Configuring RA Gaurd for IPv6 Clients 609Information About RA Guard 609Configuring RA Guard (GUI) 609Configuring RA Guard (CLI) 609Configuring RA Throttling for IPv6 Clients 609Information about RA Throttling 609Configuring RA Throttling (GUI) 610Configuring the RA Throttle Policy (CLI) 610Configuring IPv6 Neighbor Discovery Caching 611Information About IPv6 Neighbor Discovery 611Configuring Neighbor Binding (GUI) 611Cisco Wireless LAN Controller Configuration Guide, Release 7.4       OL-28744-01 xxixContents
Configuring Neighbor Binding (CLI) 611CHAPTER 90 Configuring Cisco Client Extensions 613Prerequisites for Configuring Cisco Client Extensions 613Restrictions for Configuring Cisco Client Extensions 613Information About Cisco Client Extensions 614Configuring CCX Aironet IEs (GUI) 614Viewing a Client’s CCX Version (GUI) 614Configuring CCX Aironet IEs (CLI) 614Viewing a Client’s CCX Version (CLI) 615CHAPTER 91 Configuring Remote LANs 617Prerequisites for Configuring Remote LANs 617Restrictions for Configuring Remote LANs 617Information About Remote LANs 617Configuring a Remote LAN (GUI) 618Configuring a Remote LAN (CLI) 618CHAPTER 92 Configuring AP Groups 621Prerequisites for Configuring AP Groups 621AP Groups Supported on Controller Platforms 621Restrictions for Configuring Access Point Groups 622Information About Access Point Groups 622Configuring Access Point Groups 624Creating Access Point Groups (GUI) 624Creating Access Point Groups (CLI) 626Viewing Access Point Groups (CLI) 626CHAPTER 93 Configuring RF Profiles 629Prerequisites for Configuring RF Profiles 629Restrictions for Configuring RF Profiles 629Information About RF Profiles 630Configuring an RF Profile (GUI) 632Configuring an RF Profile (CLI) 633Applying an RF Profile to AP Groups (GUI) 634   Cisco Wireless LAN Controller Configuration Guide, Release 7.4xxx OL-28744-01  Contents
Applying RF Profiles to AP Groups (CLI) 635CHAPTER 94 Configuring Web Redirect with 8021.X Authentication 637Information About Web Redirect with 802.1X Authentication 637Conditional Web Redirect 637Splash Page Web Redirect 638Configuring the RADIUS Server (GUI) 638Configuring Web Redirect 639Configuring Web Redirect (GUI) 639Configuring Web Redirect (CLI) 639Disabling Accounting Servers per WLAN (GUI) 640Disabling Coverage Hole Detection per WLAN 640Disabling Coverage Hole Detection on a WLAN (GUI) 641Disabling Coverage Hole Detection on a WLAN (CLI) 641CHAPTER 95 Configuring NAC Out-of-Band Integration 643Prerequisites for NAC Out Of Band 643Restrictions for NAC Out of Band 644Information About NAC Out-of-Band Integration 645Configuring NAC Out-of-Band Integration (GUI) 645Configuring NAC Out-of-Band Integration (CLI) 647CHAPTER 96 Configuring Passive Clients 649Restrictions for Passive Clients 649Information About Passive Clients 649Configuring Passive Clients (GUI) 650Enabling the Multicast-Multicast Mode (GUI) 650Enabling the Global Multicast Mode on Controllers (GUI) 651Enabling the Passive Client Feature on the Controller (GUI) 651Configuring Passive Clients (CLI) 651CHAPTER 97 Configuring Client Profiling 653Prerequisites for Configuring Client Profiling 653Restrictions for Configuring Client Profiling 653Information About Client Profiling 654Cisco Wireless LAN Controller Configuration Guide, Release 7.4       OL-28744-01 xxxiContents
Configuring Client Profiling (GUI) 654Configuring Client Profiling (CLI) 654CHAPTER 98 Configuring Per-WLAN RADIUS Source Support 657Prerequisites for Per-WLAN RADIUS Source Support 657Restrictions for Per-WLAN RADIUS Source Support 657Information About Per-WLAN RADIUS Source Support 657Configuring Per-WLAN RADIUS Source Support (CLI) 658Monitoring the Status of Per-WLAN RADIUS Source Support (CLI) 658CHAPTER 99 Configuring Mobile Concierge 661Information About Mobile Concierge 661Configuring Mobile Concierge (802.11u) 661Configuring Mobile Concierge (802.11u) (GUI) 661Configuring Mobile Concierge (802.11u) (CLI) 662Configuring 802.11u Mobility Services Advertisement Protocol 663Information About 802.11u MSAP 663Configuring 802.11u MSAP (GUI) 664Configuring MSAP (CLI) 664664Configuring 802.11u HotSpot 664Information About 802.11u HotSpot 664Configuring 802.11u HotSpot (GUI) 664Configuring HotSpot 2.0 (CLI) 665665Configuring Access Points for HotSpot2 (GUI) 666Configuring Access Points for HotSpot2 (CLI) 667CHAPTER 100 Configuring Assisted Roaming 673Restrictions for Assisted Roaming 673Information About Assisted Roaming 673Configuring Assisted Roaming (CLI) 674PART VI     Controlling Lightweight Access Points 677   Cisco Wireless LAN Controller Configuration Guide, Release 7.4xxxii OL-28744-01  Contents
CHAPTER 101 Using Access Point Communication Protocols 679Information About Access Point Communication Protocols 679Restrictions for Access Point Communication Protocols 680Configuring Data Encryption 680Guidelines for Data Encryption 680Upgrading or Downgrading DTLS Images for Cisco 5500 Series Controllers 681Guidelines When Upgrading to or from a DTLS Image 681Configuring Data Encryption (GUI) 682Configuring Data Encryption (CLI) 682Viewing CAPWAP Maximum Transmission Unit Information 683Debugging CAPWAP 683Controller Discovery Process 684Restrictions for Controller Discovery Process 685Verifying that Access Points Join the Controller 685Verifying that Access Points Join the Controller (GUI) 685Verifying that Access Points Join the Controller (CLI) 685CHAPTER 102 Searching for Access Points 687Information About Searching for Access Points 687Searching the AP Filter (GUI) 687Monitoring the Interface Details 690Searching for Access Point Radios 692Information About Searching for Access Point Radios 692Searching for Access Point Radios (GUI) 692CHAPTER 103 Searching for Access Point Radios 695Information About Searching for Access Point Radios 695Searching for Access Point Radios (GUI) 695CHAPTER 104 Configuring Global Credentials for Access Points 697Information About Configuring Global Credentials for Access Points 697Restrictions for Global Credentials for Access Points 698Configuring Global Credentials for Access Points (GUI) 698Configuring Global Credentials for Access Points (CLI) 699Cisco Wireless LAN Controller Configuration Guide, Release 7.4       OL-28744-01 xxxiiiContents
CHAPTER 105 Configuring Authentication for Access Points 701Information About Configuring Authentication for Access Points 701Prerequisites for Configuring Authentication for Access Points 701Restrictions for Authenticating Access Points 702Configuring Authentication for Access Points (GUI) 702Configuring Authentication for Access Points (CLI) 703Configuring the Switch for Authentication 704CHAPTER 106 Configuring Embedded Access Points 705Information About Embedded Access Points 705CHAPTER 107 Converting Autonomous Access Points to Lightweight Mode 707Information About Converting Autonomous Access Points to Lightweight Mode 707Restrictions for Converting Autonomous Access Points to Lightweight Mode 708Reverting from Lightweight Mode to Autonomous Mode 708Reverting to a Previous Release (CLI) 708Reverting to a Previous Release Using the MODE Button and a TFTP Server 709Authorizing Access Points 709Authorizing Access Points Using SSCs 709Authorizing Access Points for Virtual Controllers Using SSC 709Configuring SSC (GUI) 710Configuring SSC (CLI) 710Authorizing Access Points Using MICs 710Authorizing Access Points Using LSCs 711Configuring Locally Significant Certificates (GUI) 711Configuring Locally Significant Certificates (CLI) 712Authorizing Access Points (GUI) 714Authorizing Access Points (CLI) 714Configuring VLAN Tagging for CAPWAP Frames from Access Points 715Information About VLAN Tagging for CAPWAP Frames from Access Points 715Configuring VLAN Tagging for CAPWAP Frames from Access Points (GUI) 715Configuring VLAN Tagging for CAPWAP Frames from Access Points (CLI) 715Using DHCP Option 43 and DHCP Option 60 716Troubleshooting the Access Point Join Process 717   Cisco Wireless LAN Controller Configuration Guide, Release 7.4xxxiv OL-28744-01  Contents
Configuring the Syslog Server for Access Points (CLI) 718Viewing Access Point Join Information 719Viewing Access Point Join Information (GUI) 719Viewing Access Point Join Information (CLI) 720Sending Debug Commands to Access Points Converted to Lightweight Mode 721Understanding How Converted Access Points Send Crash Information to the Controller 721Understanding How Converted Access Points Send Radio Core Dumps to the Controller 721Retrieving Radio Core Dumps (CLI) 722Uploading Radio Core Dumps (GUI) 722Uploading Radio Core Dumps (CLI) 723Uploading Memory Core Dumps from Converted Access Points 723Uploading Access Point Core Dumps (GUI) 724Uploading Access Point Core Dumps (CLI) 724Viewing the AP Crash Log Information 724Viewing the AP Crash Log information (GUI) 725Viewing the AP Crash Log information (CLI) 725Displaying MAC Addresses for Converted Access Points 725Disabling the Reset Button on Access Points Converted to Lightweight Mode 725Configuring a Static IP Address on a Lightweight Access Point 726Configuring a Static IP Address (GUI) 726Configuring a Static IP Address (CLI) 726Supporting Oversized Access Point Images 727Recovering the Access Point—Using the TFTP Recovery Procedure 728CHAPTER 108 Configuring Packet Capture 729Information About Packet Capture 729Restrictions for Packet Capture 730Configuring Packet Capture (CLI) 730CHAPTER 109 Configuring OfficeExtend Access Points 733Information About OfficeExtend Access Points 733OEAP 600 Series Access Points 734OEAP in Local Mode 734Supported WLAN Settings for 600 Series OfficeExtend Access Point 735WLAN Security Settings for the 600 Series OfficeExtend Access Point 735Cisco Wireless LAN Controller Configuration Guide, Release 7.4       OL-28744-01 xxxvContents
Authentication Settings 739Supported User Count on 600 Series OfficeExtend Access Point 740Remote LAN Settings 740Channel Management and Settings 741Additional Caveats 742Implementing Security 742Licensing for an OfficeExtend Access Point 743Configuring OfficeExtend Access Points 743Configuring OfficeExtend Access Points (GUI) 744Configuring OfficeExtend Access Points (CLI) 745Configuring a Personal SSID on an OfficeExtend Access Point 747Viewing OfficeExtend Access Point Statistics 749CHAPTER 110 Using Cisco Workgroup Bridges 751Information About Cisco Workgroup Bridges 751Restrictions for Cisco Workgroup Bridges 753WGB Configuration Example 754Viewing the Status of Workgroup Bridges (GUI) 755Viewing the Status of Workgroup Bridges (CLI) 755Debugging WGB Issues (CLI) 756CHAPTER 111 Using Non-Cisco Workgroup Bridges 757Information About Non-Cisco Workgroup Bridges 757Restrictions for Non-Cisco Workgroup Bridges 758CHAPTER 112 Configuring Backup Controllers 759Information About Configuring Backup Controllers 759Restrictions for Configuring Backup Controllers 760Configuring Backup Controllers (GUI) 760Configuring Backup Controllers (CLI) 761CHAPTER 113 Configuring High Availability 765Information About High Availability 765Restrictions for High Availability 767Configuring High Availability (GUI) 769   Cisco Wireless LAN Controller Configuration Guide, Release 7.4xxxvi OL-28744-01  Contents
Configuring High Availability (CLI) 770CHAPTER 114 Configuring Failover Priority for Access Points 773Information About Configuring Failover Priority for Access Points 773Configuring Failover Priority for Access Points (GUI) 774Configuring Failover Priority for Access Points (CLI) 774Viewing Failover Priority Settings (CLI) 774CHAPTER 115 Configuring AP Retransmission Interval and Retry Count 777Information About Configuring the AP Retransmission Interval and Retry Count 777Restrictions for Access Point Retransmission Interval and Retry Count 777Configuring the AP Retransmission Interval and Retry Count (GUI) 778Configuring the Access Point Retransmission Interval and Retry Count (CLI) 778CHAPTER 116 Configuring Country Codes 781Information About Configuring Country Codes 781Restrictions for Configuring Country Codes 782Configuring Country Codes (GUI) 782Configuring Country Codes (CLI) 783CHAPTER 117 Optimizing RFID Tracking on Access Points 785Information About Optimizing RFID Tracking on Access Points 785Optimizing RFID Tracking on Access Points (GUI) 785Optimizing RFID Tracking on Access Points (CLI) 786CHAPTER 118 Configuring Probe Request Forwarding 787Information About Configuring Probe Request Forwarding 787Configuring Probe Request Forwarding (CLI) 787CHAPTER 119 Retrieving the Unique Device Identifier on Controllers and Access Points 789Information About Retrieving the Unique Device Identifier on Controllers and AccessPoints 789Retrieving the Unique Device Identifier on Controllers and Access Points (GUI) 789Retrieving the Unique Device Identifier on Controllers and Access Points (CLI) 790Cisco Wireless LAN Controller Configuration Guide, Release 7.4       OL-28744-01 xxxviiContents
CHAPTER 120 Performing a Link Test 791Information About Performing a Link Test 791Performing a Link Test (GUI) 792Performing a Link Test (CLI) 792CHAPTER 121 Configuring Link Latency 795Information About Configuring Link Latency 795Restrictions for Link Latency 796Configuring Link Latency (GUI) 796Configuring Link Latency (CLI) 796CHAPTER 122 Configuring the TCP MSS 799Information About Configuring the TCP MSS 799Configuring TCP MSS (GUI) 799Configuring TCP MSS (CLI) 800CHAPTER 123 Configuring Power Over Ethernet 801Information About Configuring Power over Ethernet 801Configuring Power over Ethernet (GUI) 803Configuring Power over Ethernet (CLI) 804CHAPTER 124 Viewing Clients 807Viewing Clients (GUI) 807Viewing Clients (CLI) 808CHAPTER 125 Configuring LED States for Access Points 809Configuring LED States 809Information About Configuring LED States for Access Points 809Configuring the LED State for Access Points in a Network Globally (GUI) 809Configuring the LED State for Access Point in a Network Globally (CLI) 809Configuring LED State on a Specific Access Point (GUI) 810Configuring LED State on a Specific Access Point (CLI) 810Configuring Flashing LEDs 810Information About Configuring Flashing LEDs 810   Cisco Wireless LAN Controller Configuration Guide, Release 7.4xxxviii OL-28744-01  Contents
Configuring Flashing LEDs (CLI) 810CHAPTER 126 Configuring Access Points with Dual-Band Radios 813Configuring Access Points with Dual-Band Radios (GUI) 813Configuring Access Points with Dual-Band Radios (CLI) 814PART VII     Configuring Radio Resource Management 815CHAPTER 127 Configuring RRM 817Information About Radio Resource Management 817Radio Resource Monitoring 818Transmit Power Control 818Overriding the TPC Algorithm with Minimum and Maximum Transmit PowerSettings 819Dynamic Channel Assignment 819Coverage Hole Detection and Correction 821Benefits of RRM 821Information About Configuring RRM 821Restrictions for Configuring RRM 822Configuring the RF Group Mode (GUI) 822Configuring the RF Group Mode (CLI) 823Configuring Transmit Power Control (GUI) 823Configuring Off-Channel Scanning Defer 825Information About Off-Channel Scanning Defer 825Configuring Off-Channel Scanning Defer for WLANs 825Configuring Off-Channel Scanning Defer for a WLAN (GUI) 825Configuring Off Channel Scanning Defer for a WLAN (CLI) 826Configuring Dynamic Channel Assignment (GUI) 826Configuring Coverage Hole Detection (GUI) 829Configuring RRM Profile Thresholds, Monitoring Channels, and Monitor Intervals(GUI) 830Configuring RRM (CLI) 831Viewing RRM Settings (CLI) 835Debug RRM Issues (CLI) 836Cisco Wireless LAN Controller Configuration Guide, Release 7.4       OL-28744-01 xxxixContents
CHAPTER 128 Configuring RRM Neighbor Discovery Packets 837Information About RRM NDP and RF Grouping 837Configuring RRM NDP (CLI) 837CHAPTER 129 Configuring RF Groups 839Information About RF Groups 839RF Group Leader 840RF Group Name 841Configuring RF Groups 841Configuring an RF Group Name (GUI) 842Configuring an RF Group Name (CLI) 842Viewing the RF Group Status 842Viewing the RF Group Status (GUI) 842Viewing the RF Group Status (CLI) 843Configuring Rogue Access Point Detection in RF Groups 843Information About Rogue Access Point Detection in RF Groups 843Configuring Rogue Access Point Detection in RF Groups 844Enabling Rogue Access Point Detection in RF Groups (GUI) 844Configuring Rogue Access Point Detection in RF Groups (CLI) 844CHAPTER 130 Overriding RRM 847Information About Overriding RRM 847Prerequisites for Overriding RRM 847Statically Assigning Channel and Transmit Power Settings to Access Point Radios 848Statically Assigning Channel and Transmit Power Settings (GUI) 848Statically Assigning Channel and Transmit Power Settings (CLI) 849Disabling Dynamic Channel and Power Assignment Globally for a Cisco Wireless LANController 852Disabling Dynamic Channel and Power Assignment (GUI) 852Disabling Dynamic Channel and Power Assignment (CLI) 852CHAPTER 131 Configuring CCX Radio Management Features 855Information About CCX Radio Management Features 855Radio Measurement Requests 855   Cisco Wireless LAN Controller Configuration Guide, Release 7.4xl OL-28744-01  Contents
Location Calibration 856Configuring CCX Radio Management 856Configuring CCX Radio Management (GUI) 856Configuring CCX Radio Management (CLI) 857Viewing CCX Radio Management Information (CLI) 857Debugging CCX Radio Management Issues (CLI) 858PART VIII     Configuring Cisco CleanAir 861CHAPTER 132 Information About CleanAir 863Information About CleanAir 863Role of the Cisco Wireless LAN Controller in a Cisco CleanAir System 864Interference Types that Cisco CleanAir Can Detect 864Persistent Devices 865Persistent Devices Detection 865Persistent Devices Propagation 865Detecting Interferers by an Access Point 866CHAPTER 133 Prerequisites and Restrictions for CleanAir 867Prerequisites for CleanAir 867Restrictions for CleanAir 868CHAPTER 134 Configuring Cisco CleanAir 869Configuring Cisco CleanAir on the Controller 869Configuring Cisco CleanAir on the Cisco Wireless LAN Controller (GUI) 869Configuring Cisco CleanAir on the Cisco Wireless LAN Controller (CLI) 871Configuring Cisco CleanAir on an Access Point 875Configuring Cisco CleanAir on an Access Point (GUI) 875Configuring Cisco CleanAir on an Access Point (CLI) 876CHAPTER 135 Monitoring the Interference Devices 877Prerequisites for Monitoring the Interference Devices 877Monitoring the Interference Device (GUI) 877Monitoring the Interference Device (CLI) 879Detecting Interferers by an Access Point 879Cisco Wireless LAN Controller Configuration Guide, Release 7.4       OL-28744-01 xliContents
Detecting Interferers by Device Type 879Detecting Persistent Sources of Interference 879Monitoring Persistent Devices (GUI) 880Monitoring Persistent Devices (CLI) 880Monitoring the Air Quality of Radio Bands 881Monitoring the Air Quality of Radio Bands (GUI) 881Monitoring the Air Quality of Radio Bands (CLI) 881Viewing a Summary of the Air Quality 881Viewing Air Quality for all Access Points on a Radio Band 881Viewing Air Quality for an Access Point on a Radio Band 881Monitoring the Worst Air Quality of Radio Bands (GUI) 882Monitoring the Worst Air Quality of Radio Bands (CLI) 882Viewing a Summary of the Air Quality (CLI) 882Viewing the Worst Air Quality Information for all Access Points on a Radio Band(CLI) 882Viewing the Air Quality for an Access Point on a Radio Band (CLI) 882Viewing the Air Quality for an Access Point by Device Type (CLI) 883Detecting Persistent Sources of Interference (CLI) 883CHAPTER 136 Configuring a Spectrum Expert Connection 885Information About Spectrum Expert Connection 885Configuring Spectrum Expert (GUI) 885PART IX     Configuring FlexConnect 889CHAPTER 137 Configuring FlexConnect 891Information About FlexConnect 891FlexConnect Authentication Process 892Restrictions for FlexConnect 896Configuring FlexConnect 897Configuring the Switch at a Remote Site 897Configuring the Controller for FlexConnect 898Configuring the Controller for FlexConnect for a Centrally Switched WLAN Usedfor Guest Access 899Configuring the Controller for FlexConnect (GUI) 900   Cisco Wireless LAN Controller Configuration Guide, Release 7.4xlii OL-28744-01  Contents
Configuring the Controller for FlexConnect (CLI) 901Configuring an Access Point for FlexConnect 903Configuring an Access Point for FlexConnect (GUI) 903Configuring an Access Point for FlexConnect (CLI) 905Configuring an Access Point for Local Authentication on a WLAN (GUI) 907Configuring an Access Point for Local Authentication on a WLAN (CLI) 907Connecting Client Devices to WLANs 907CHAPTER 138 Configuring FlexConnect ACLs 909Information About Access Control Lists 909Restrictions for FlexConnect ACLs 909Configuring FlexConnect ACLs (GUI) 910Configuring FlexConnect ACLs (CLI) 912Viewing and Debugging FlexConnect ACLs (CLI) 913CHAPTER 139 Configuring FlexConnect Groups 915Information About FlexConnect Groups 915FlexConnect Groups and Backup RADIUS Servers 916FlexConnect Groups and CCKM 916FlexConnect Groups and Opportunistic Key Caching 916FlexConnect Groups and Local Authentication 917Configuring FlexConnect Groups 917Configuring FlexConnect Groups (GUI) 917Configuring FlexConnect Groups (CLI) 920Configuring VLAN-ACL Mapping on FlexConnect Groups 922Configuring VLAN-ACL Mapping on FlexConnect Groups (GUI) 922Configuring VLAN-ACL Mapping on FlexConnect Groups (CLI) 922Viewing VLAN-ACL Mappings (CLI) 922CHAPTER 140 Configuring AAA Overrides for FlexConnect 923Information About Authentication, Authorization, Accounting Overrides 923Restrictions for AAA Overrides for FlexConnect 924Configuring AAA Overrides for FlexConnect on an Access Point (GUI) 924Configuring VLAN Overrides for FlexConnect on an Access Point (CLI) 925Cisco Wireless LAN Controller Configuration Guide, Release 7.4       OL-28744-01 xliiiContents
CHAPTER 141 Configuring FlexConnect AP Upgrades for FlexConnect APs 927Information About FlexConnect AP Upgrades 927Restrictions for FlexConnect AP Upgrades for FlexConnect Access Points 927Configuring FlexConnect AP Upgrades (GUI) 928Configuring FlexConnect AP Upgrades (CLI) 928PART X     Configuring Mobility Groups 929CHAPTER 142 Configuring Mobility Groups 931Information About Mobility 931Information About Mobility Groups 935Messaging Among Mobility Groups 937Using Mobility Groups with NAT Devices 937Prerequisites for Configuring Mobility Groups 938Configuring Mobility Groups (GUI) 940Configuring Mobility Groups (CLI) 941CHAPTER 143 Viewing Mobility Group Statistics 943Viewing Mobility Group Statistics (GUI) 943Viewing Mobility Group Statistics (CLI) 944CHAPTER 144 Configuring Auto-Anchor Mobility 945Information About Auto-Anchor Mobility 945Guidelines and Limitations 946Configuring Auto-Anchor Mobility (GUI) 947Configuring Auto-Anchor Mobility (CLI) 947CHAPTER 145 Validating WLAN Mobility Security Values 951Information About WLAN Mobility Security Values 951CHAPTER 146 Using Symmetric Mobility Tunneling 953Information About Symmetric Mobility Tunneling 953Guidelines and Limitations 954Verifying Symmetric Mobility Tunneling (GUI) 954   Cisco Wireless LAN Controller Configuration Guide, Release 7.4xliv OL-28744-01  Contents
Verifying if Symmetric Mobility Tunneling is Enabled (CLI) 954CHAPTER 147 Running Mobility Ping Tests 955Information About Mobility Ping Tests 955Guidelines and Limitations 955Running Mobility Ping Tests (CLI) 956CHAPTER 148 Configuring Dynamic Anchoring for Clients with Static IP Addresses 957Information About Dynamic Anchoring for Clients with Static IP 957How Dynamic Anchoring of Static IP Clients Works 957Guidelines and Limitations 958Configuring Dynamic Anchoring of Static IP Clients (GUI) 958Configuring Dynamic Anchoring of Static IP Clients (CLI) 959CHAPTER 149 Configuring Foreign Mappings 961Information About Foreign Mappings 961Configuring Foreign Controller MAC Mapping (GUI) 961Configuring Foreign Controller MAC Mapping (CLI) 961CHAPTER 150 Configuring Proxy Mobile IPv6 963Information About Proxy Mobile IPv6 963Guidelines and Limitations 963Configuring Proxy Mobile IPv6 (GUI) 964Configuring Proxy Mobile IPv6 (CLI) 965Cisco Wireless LAN Controller Configuration Guide, Release 7.4       OL-28744-01 xlvContents
   Cisco Wireless LAN Controller Configuration Guide, Release 7.4xlvi OL-28744-01  Contents
PrefaceThis preface describes the audience, organization, and conventions of this document. It also providesinformation on how to obtain other documentation. This chapter includes the following sections:•Audience, page xlvii•Conventions, page xlvii•Related Documentation, page xlviii•Obtaining Documentation and Submitting a Service Request, page xlixAudienceThis publication is for experienced network administrators who configure and maintain Cisco wireless LANcontrollers and Cisco lightweight access points.ConventionsThis document uses the following conventions:Table 1: ConventionsIndicationConventionCommands and keywords and user-entered text appear in bold font.bold fontDocument titles, new or emphasized terms, and arguments for which you supplyvalues are in italic font.italic fontElements in square brackets are optional.[ ]Required alternative keywords are grouped in braces and separated by verticalbars.{x | y | z }Optional alternative keywords are grouped in brackets and separated by verticalbars.[x|y|z]Cisco Wireless LAN Controller Configuration Guide, Release 7.4       OL-28744-01 xlvii
IndicationConventionA nonquoted set of characters. Do not use quotation marks around the string orthe string will include the quotation marks.stringTerminal sessions and information the system displays appear in courier font.courier fontNonprinting 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 codeindicates a comment line.!, #Means reader take note. Notes contain helpful suggestions or references to material not covered in themanual.NoteMeans the following information will help you solve a problem.TipMeans reader be careful. In this situation, you might perform an action that could result in equipmentdamage or loss of data.CautionRelated DocumentationThese documents provide complete information about Cisco Wireless:•Cisco Wireless LAN Controller configuration guides:http://www.cisco.com/en/US/products/ps10315/products_installation_and_configuration_guides_list.html•Cisco Wireless LAN Controller command references:http://www.cisco.com/en/US/products/ps10315/prod_command_reference_list.html•Cisco Wireless LAN Controller System Message Guide:•http://www.cisco.com/en/US/products/ps10315/products_system_message_guides_list.html•Release Notes for Cisco Wireless LAN Controllers and Lightweight Access Points:•http://www.cisco.com/en/US/products/ps10315/prod_release_notes_list.html•Cisco Wireless Mesh Access Points, Design and Deployment Guide:•http://www.cisco.com/en/US/products/ps11451/products_implementation_design_guides_list.html•Cisco Prime Infrastructure documentation:http://www.cisco.com/en/US/products/ps12239/products_documentation_roadmaps_list.html   Cisco Wireless LAN Controller Configuration Guide, Release 7.4xlviii OL-28744-01  PrefaceRelated Documentation
•Cisco Mobility Services Engine documentation:http://www.cisco.com/en/US/products/ps9806/tsd_products_support_series_home.htmlClick this link to access user documentation pertaining to Cisco Wireless solution:http://www.cisco.com/cisco/web/psa/default.html?mode=prodObtaining Documentation and Submitting a Service RequestFor information on obtaining documentation, using the Cisco Bug Search Tool (BST), submitting a servicerequest, and gathering additional information, see What's New in Cisco Product Documentation, at: http://www.cisco.com/en/US/docs/general/whatsnew/whatsnew.html.Subscribe to What's New in Cisco Product Documentation, which lists all new and revised Cisco technicaldocumentation, as an RSS feed and deliver content directly to your desktop using a reader application. TheRSS feeds are a free service.Cisco Wireless LAN Controller Configuration Guide, Release 7.4       OL-28744-01 xlixPrefaceObtaining Documentation and Submitting a Service Request
   Cisco Wireless LAN Controller Configuration Guide, Release 7.4lOL-28744-01  PrefaceObtaining Documentation and Submitting a Service Request
PART ISystem Management•Overview, page 3•Getting Started, page 15•Managing Licenses, page 55•Configuring 802.11 Bands, page 75•Configuring 802.11 Parameters, page 83•Configuring DHCP Proxy, page 89•Configuring SNMP, page 93•Configuring Aggressive Load Balancing, page 97•Configuring Fast SSID Changing, page 101•Configuring 802.3 Bridging, page 103•Configuring Multicast, page 105•Configuring Client Roaming, page 115•Configuring IP-MAC Address Binding, page 121•Configuring Quality of Service, page 123•Configuring Application Visibility and Control, page 131•Configuring Media and EDCA Parameters, page 137•Configuring the Cisco Discovery Protocol, page 157
•Configuring Authentication for the Controller and NTP Server, page 165•Configuring RFID Tag Tracking, page 167•Resetting the Controller to Default Settings, page 171•Managing Controller Software and Configurations, page 173•Managing User Accounts, page 205•Managing Web Authentication, page 213•Configuring Wired Guest Access, page 233•Troubleshooting, page 241
CHAPTER 1Overview•Cisco Wireless Overview, page 3•Operating System Software, page 6•Operating System Security, page 6•Layer 2 and Layer 3 Operation, page 7•Cisco Wireless LAN Controllers, page 8•Controller Platforms, page 8•Cisco UWN Solution WLANs, page 11•File Transfers, page 11•Power over Ethernet, page 11•Cisco Wireless LAN Controller Memory, page 12•Cisco Wireless LAN Controller Failover Protection, page 12Cisco Wireless OverviewCisco Wireless is designed to provide 802.11 wireless networking solutions for enterprises and serviceproviders. Cisco Wireless simplifies deploying and managing large-scale wireless LANs and enables a uniquebest-in-class security infrastructure. The operating system manages all data client, communications, and systemadministration functions, performs radio resource management (RRM) functions, manages system-widemobility policies using the operating system security solution, and coordinates all security functions usingthe operating system security framework.Cisco Wireless solution consists of Cisco wireless LAN controllers and their associated lightweight accesspoints controlled by the operating system, all concurrently managed by any or all of the operating system userinterfaces:•An HTTP and/or HTTPS full-featured Web User Interface hosted by Cisco wireless LAN controllerscan be used to configure and monitor individual controllers.•A full-featured command-line interface (CLI) can be used to configure and monitor individual Ciscowireless LAN controllers.Cisco Wireless LAN Controller Configuration Guide, Release 7.4        OL-28744-01 3
•The Cisco Prime Infrastructure, which you use to configure and monitor one or more Cisco wirelessLAN controllers and associated access points. The Prime Infrastructure has tools to facilitate large-systemmonitoring and control. For more information about Cisco Prime Infrastructure, see http://www.cisco.com/en/US/products/ps12239/tsd_products_support_series_home.html.•An industry-standard SNMP V1, V2c, and V3 interface can be used with any SNMP-compliant third-partynetwork management system.The Cisco Wireless solution supports client data services, client monitoring and control, and all rogue accesspoint detection, monitoring, and containment functions. It uses lightweight access points, Cisco wireless LANcontrollers, and the optional Cisco Prime Infrastructure to provide wireless services to enterprises and serviceproviders.Unless otherwise noted in this publication, all of the Cisco wireless LAN controllers are referred to ascontrollers, and all of the Cisco lightweight access points are referred to as access points.NoteSingle-Controller DeploymentsA standalone controller can support lightweight access points across multiple floors and buildingssimultaneously 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 ormay not provide Power over Ethernet (PoE) to the access points.Some controllers use redundant Gigabit Ethernet connections to bypass single network failures.Some controllers can connect through multiple physical ports to multiple subnets in the network. Thisfeature can be helpful when you want to confine multiple VLANs to separate subnets.Note   Cisco Wireless LAN Controller Configuration Guide, Release 7.44OL-28744-01  Cisco Wireless Overview
This figure shows a typical single-controller deployment.Figure 1: Single-Controller DeploymentMultiple-Controller DeploymentsEach 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 optionaldedicated management network and the three physical connection types between the network and the controllers.Cisco Wireless LAN Controller Configuration Guide, Release 7.4       OL-28744-01 5Cisco Wireless Overview
Figure 2: Typical Multiple-Controller DeploymentOperating System SoftwareThe operating system software controls controllers and lightweight access points. It includes full operatingsystem security and radio resource management (RRM) features.Operating System SecurityOperating system security bundles Layer 1, Layer 2, and Layer 3 security components into a simple, CiscoWLAN solution-wide policy manager that creates independent security policies for each of up to 16 wirelessLANs.The 802.11 Static WEP weaknesses can be overcome using the following robust industry-standard securitysolutions:•802.1X dynamic keys with extensible authentication protocol (EAP).•Wi-Fi protected access (WPA) dynamic keys. The Cisco WLAN solution WPA implementation includes:◦Temporal key integrity protocol (TKIP) and message integrity code checksum dynamic keys◦WEP keys, with or without a preshared key passphrase   Cisco Wireless LAN Controller Configuration Guide, Release 7.46OL-28744-01  Operating System Software
•RSN with or without a preshared key•Optional MAC filteringThe 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 blockaccess using client MAC addresses. In automated disabling, which is always active, the operating systemsoftware automatically blocks access to network services for a user-defined period of time when a clientfails to authenticate for a fixed number of consecutive attempts. This feature can be used to deterbrute-force login attacks.These and other security features use industry-standard authorization and authentication methods to ensurethe highest possible security for your business-critical wireless LAN traffic.Layer 2 and Layer 3 OperationLightweight Access Point Protocol (LWAPP) communications between the controller and lightweight accesspoints can be conducted at Layer 2 or Layer 3. Control and Provisioning of Wireless Access Points protocol(CAPWAP) communications between the controller and lightweight access points are conducted at Layer 3.Layer 2 mode does not support CAPWAP.The IPv4 network layer protocol is supported for transport through a CAPWAP or LWAPP controllersystem. IPv6 (for clients only) and AppleTalk are also supported but only on Cisco 5500 Series Controllersand 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.NoteOperational RequirementsThe requirement for Layer 3 LWAPP communications is that the controller and lightweight access points canbe 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 dynamicallyassigned through an external DHCP server.The requirement for Layer 3 CAPWAP communications is that the controller and lightweight access pointscan be connected through Layer 2 devices on the same subnet or connected through Layer 3 devices acrosssubnets.Configuration RequirementsWhen you are operating the Cisco wireless LAN solution in Layer 2 mode, you must configure a managementinterface to control your Layer 2 communications.Cisco Wireless LAN Controller Configuration Guide, Release 7.4       OL-28744-01 7Layer 2 and Layer 3 Operation
When you are operating the Cisco wireless LAN solution in Layer 3 mode, you must configure an AP-managerinterface to control lightweight access points and a management interface as configured for Layer 2 mode.Cisco Wireless LAN ControllersWhen you are adding lightweight access points to a multiple-controller deployment network, it is convenientto have all lightweight access points associate with one master controller on the same subnet. That way, theyou do not have to log into multiple controllers to find out which controller newly-added lightweight accesspoints associated with.One controller in each subnet can be assigned as the master controller while adding lightweight access points.As long as a master controller is active on the same subnet, all new access points without a primary, secondary,and tertiary controller assigned automatically attempt to associate with the master controller. This process isdescribed in Cisco Wireless LAN Controller Failover Protection, on page 12.You can monitor the master controller using the Cisco Prime Infrastructure Web User Interface and watch asaccess points associate with the master controller. You can then verify the access point configuration andassign a primary, secondary, and tertiary controller to the access point, and reboot the access point so itreassociates with its primary, secondary, or tertiary controller.Lightweight access points without a primary, secondary, and tertiary controller assigned always searchfor a master controller first upon reboot. After adding lightweight access points through the mastercontroller, you should assign primary, secondary, and tertiary controllers to each access point. Werecommend that you disable the master setting on all controllers after initial configuration.NoteClient LocationWhen you use Cisco Prime Infrastructure in your Cisco wireless LAN solution, controllers periodicallydetermine the client, rogue access point, rogue access point client, radio frequency ID (RFID) tag locationand store the locations in the Cisco Prime Infrastructure database.Controller PlatformsControllers are enterprise-class high-performance wireless switching platforms that support 802.11a/n and802.11b/g/n protocols. They operate under control of the operating system, which includes the radio resourcemanagement (RRM), creating a Cisco UWN solution that can automatically adjust to real-time changes inthe 802.11 RF environment. Controllers are built around high-performance network and security hardware,resulting in highly reliable 802.11 enterprise networks with unparalleled security.The following controllers are supported:Cisco 2500 Series ControllersThe Cisco 2500 Series Wireless Controller works in conjunction with Cisco lightweight access points andthe Cisco Prime Infrastructure to provide system-wide wireless LAN functions. The Cisco 2500 Seriescontroller provides real-time communication between a wireless access points and other devices to delivercentralized security policies, guest access, wireless intrusion prevention system (wIPS), context-aware   Cisco Wireless LAN Controller Configuration Guide, Release 7.48OL-28744-01  Cisco Wireless LAN Controllers
(location), RF management, quality of services for mobility services such as voice and video, and OEAPsupport for the teleworker solution.For more information about Cisco 2500 series controllers, see http://www.cisco.com/en/US/products/ps11630/index.html.Cisco 5500 Series ControllerThe Cisco 5500 Series Wireless LAN Controller is currently available in one model: 5508. The Cisco 5500Series Wireless Controller is a highly scalable and flexible platform that enables systemwide services formission-critical wireless networking in medium-sized to large enterprises and campus environments.The Cisco 5500 Series Controller can be equipped with one or two power supplies. When the controller isequipped with two power supplies, the power supplies are redundant, and either power supply can continueto power the controller if the other power supply fails.For more information about the Cisco 5500 Series Controller, see http://www.cisco.com/en/US/products/ps10315/tsd_products_support_series_home.html.Cisco Flex 7500 Series ControllersThe Cisco Flex 7500 Series Controller enables you to deploy full featured, scalable, and secure FlexConnectnetwork services across geographic locations. Cisco Flex 7500 Series Controller virtualizes the complexsecurity, management, configuration and troubleshooting operations within the data center and then transparentlyextends those services to each store. Deployments using Cisco Flex 7500 Series Controller are easier for ITto set up, manage and scale.The Cisco Flex 7500 Series Controller is designed to meet the scaling requirements to deploy the FlexConnectsolution in branch networks. Cisco Wireless supports two major deployment models: FlexConnect and monitormode. FlexConnect is designed to support wireless branch networks by allowing the data to be switchedlocally while the access points are being controlled and managed by a centralized controller. It aims at deliveringa cost effective FlexConnect solution on a large scale.RestrictionsFor a FlexConnect only deployment, the following restrictions apply:•Multicast-unicast is the only available default mode.•Global multicast and IGMP snooping are not supported.•IPv6 and Generic Attribute Registration Protocol (GARP) are supported but not multicast data.For more information about the Cisco Flex 7500 series controllers, see http://www.cisco.com/en/US/products/ps11635/tsd_products_support_series_home.html.Cisco 8500 Series ControllersCisco 8500 Series Controllers were introduced in the 7.3 release with support for local mode, FlexConnect,and mesh modes. The Cisco 8500 Series Controller is a highly scalable and flexible platform that enablesmission-critical wireless networking in large-scale service provider and large-campus deployments.Cisco Wireless LAN Controller Configuration Guide, Release 7.4       OL-28744-01 9Controller Platforms
The DC powered 8510 controller is not available with any of the country-specific power cords. Therefore,we recommend that you use a 12 gauge wire and connect to the DC power supply.NoteRestrictions•Local mode only deployment—Multicast-multicast is the default mode.•Local and FlexConnect mode deployment:•If you require IPv6 on FlexConnect mode APs, disable global multicast and change tomulticast-unicast mode. IPv6 and Generic Attribute Registration Protocol (GARP) works, butmulticast data and video streaming are not supported across the controller.•If you do not require IPv6 and GARP on FlexConnect APs, change the mode to multicast-multicastand enable global multicast and IGMP/MLD snooping. IPv6, GARP, multicast data, andVideoStream are supported on FlexConnect APs.For more information about the Cisco 8500 series controllers, see http://www.cisco.com/en/US/products/ps12722/tsd_products_support_series_home.html.Cisco Virtual Wireless LAN ControllersThe virtual wireless LAN controller is software that can run on hardware that is compliant with an industrystandard virtualization infrastructure. Virtual Wireless LAN controllers provide flexibility for users to selectthe hardware based on their requirement.When you take a snapshot of the virtual wireless LAN controller, the VMware suspends activities forabout 15 seconds. During this time, the APs are disconnected from the virtual wireless LAN controller.NoteFor more information about the Cisco Virtual Wireless LAN controllers, see http://www.cisco.com/en/US/products/ps12723/tsd_products_support_series_home.html.Cisco Wireless Services Module 2The Cisco Wireless Services Module 2 (WiSM2) provides medium-sized to large single-site WLANdeployments with exceptional performance, security, and scalability to support mission-critical wirelessbusiness communications. It helps to lower hardware costs and offers flexible configuration options that canreduce the total cost of operations and ownership for wireless networks.For more information about Cisco WiSM2, see http://www.cisco.com/en/US/products/ps11634/index.html.Cisco Wireless Controller on Cisco Services-Ready Engine (SRE)The Cisco wireless controller application on the Cisco Services-Ready Engine (SRE) enables systemwidewireless functions in small to medium-sized enterprises and branch offices. Delivering 802.11n performanceand scalability, the Cisco wireless controller on the SRE is an entry-level controller that provides low totalcost of ownership and investment protection by integrating seamlessly with the existing network. The Cisco   Cisco Wireless LAN Controller Configuration Guide, Release 7.410 OL-28744-01  Controller Platforms
SRE modules are router blades for the Cisco Integrated Services Routers Generation 2 (ISR G2), which allowsyou to provision the Cisco Wireless Controller applications on the module remotely at any time. This canhelp your organization to quickly deploy wireless on-demand, reduce operating costs, and consolidate thebranch office infrastructure.This controller provides real-time communication between Cisco Aironet access points, the Cisco PrimeInfrastructure, and the Cisco Mobility Services Engine (MSE) to deliver centralized security policies, wirelessintrusion prevention system (wIPS) capabilities, award-winning RF management, context-aware capabilitiesfor location tracking, and quality of service (QoS) for voice and video.For more information about Cisco wireless controller application on the Cisco Services-Ready Engine (SRE),see http://www.cisco.com/en/US/products/ps11716/index.html.Cisco UWN Solution WLANsThe Cisco UWN solution can control up to 512 WLANs for lightweight access points. Each WLAN has aseparate WLAN ID (1 through 512), a separate profile name, and a WLAN SSID and can be assigned withunique security policies. The lightweight access points broadcast all active Cisco UWN solution WLAN SSIDsand enforce the policies defined for each WLAN.We recommend that you assign one set of VLANs for WLANs and a different set of VLANs formanagement interfaces to ensure that controllers operate with optimum performance and ease ofmanagement.NoteIf management over wireless is enabled across the Cisco UWN solution, you can manage the system acrossthe enabled WLAN using CLI and Telnet, HTTP/HTTPS, and SNMP.File TransfersYou can upload and download operating system code, configuration, and certificate files to and from thecontroller using the GUI, CLI, or Cisco Prime Infrastructure.Power over EthernetLightweight access points can receive power through their Ethernet cables from 802.3af-compatible Powerover Ethernet (PoE) devices, which can reduce the cost of discrete power supplies, additional wiring, conduits,outlets, and installation time. PoE frees you from having to mount lightweight access points or other poweredequipment near AC outlets, which provides greater flexibility in positioning the access points for maximumcoverage.When you are using PoE, you run a single CAT-5 cable from each lightweight access point to PoE-equippednetwork elements, such as a PoE power hub or a Cisco WLAN solution single-line PoE injector. When thePoE equipment determines that the lightweight access point is PoE-enabled, it sends 48 VDC over the unusedpairs 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.Cisco Wireless LAN Controller Configuration Guide, Release 7.4       OL-28744-01 11Cisco UWN Solution WLANs
Cisco Wireless LAN Controller MemoryThe controller contains two kinds of memory: volatile RAM, which holds the current, active controllerconfiguration, and NVRAM (nonvolatile RAM), which holds the reboot configuration. When you areconfiguring the operating system in the controller, you are modifying volatile RAM; you must save theconfiguration from the volatile RAM to the NVRAM to ensure that the controller reboots in the currentconfiguration.Knowing which memory you are modifying is important when you are doing the following tasks:•Using the configuration wizard•Clearing the controller configuration•Saving configurations•Resetting the controller•Logging out of the CLICisco Wireless LAN Controller Failover ProtectionDuring installation, we recommend that you connect all lightweight access points to a dedicated controller,and configure each lightweight access point for final operation. This step configures each lightweight accesspoint for a primary, secondary, and tertiary controller and allows it to store the configured mobility groupinformation.During the failover recovery, the following tasks are performed:•The configured access point attempts to contact the primary, secondary, and tertiary controllers, andthen attempts to contact the IP addresses of the other controllers in the mobility group.•DNS is resolved with the controller IP address.•DHCP servers get the controller IP addresses (vendor-specific option 43 in DHCP offer).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 toassociate 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 bythe 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 withthe least-loaded controller to respond to its discovery messages.When controllers are deployed, if one controller fails, active access point client sessions are momentarilydropped while the dropped access point associates with another controller, allowing the client device toimmediately reassociate and reauthenticate.   Cisco Wireless LAN Controller Configuration Guide, Release 7.412 OL-28744-01  Cisco Wireless LAN Controller Memory
To know more about high availability, see http://www.cisco.com/en/US/products/ps6366/products_tech_note09186a00809a3f5d.shtmlCisco Wireless LAN Controller Configuration Guide, Release 7.4       OL-28744-01 13Cisco Wireless LAN Controller Failover Protection
   Cisco Wireless LAN Controller Configuration Guide, Release 7.414 OL-28744-01  Cisco Wireless LAN Controller Failover Protection
CHAPTER 2Getting Started•Configuring the Controller Using the Configuration Wizard, page 15•Connecting the Console Port of the Controller, page 16•Configuring the Controller (GUI), page 16•Configuring the Controller—Using the CLI Configuration Wizard, page 27•Using the Controller Web GUI, page 29•Loading an Externally Generated SSL Certificate, page 33•Information About Externally Generated SSL Certificates, page 33•Loading an SSL Certificate (GUI), page 34•Loading an SSL Certificate (CLI), page 35•Using the Controller CLI, page 36•Logging on to the Controller CLI, page 36•Using the AutoInstall Feature for Controllers Without a Configuration, page 39•Information About the AutoInstall Feature, page 39•Guidelines and Limitations, page 40•Managing the Controller System Date and Time, page 43•Configuring Telnet and Secure Shell Sessions, page 48•Managing the Controller Wirelessly, page 52Configuring the Controller Using the Configuration WizardThe configuration wizard enables you to configure basic settings on the controller. You can run the wizardafter you receive the controller from the factory or after the controller has been reset to factory defaults. Theconfiguration wizard is available in both GUI and CLI formats.Cisco Wireless LAN Controller Configuration Guide, Release 7.4        OL-28744-01 15
Connecting the Console Port of the ControllerBefore you can configure the controller for basic operations, you need to connect it to a PC that uses a VT-100terminal emulation program (such as HyperTerminal, ProComm, Minicom, or Tip).On Cisco 5500 Series Controllers, you can use either the RJ-45 console port or the USB console port. Ifyou use the USB console port, plug the 5-pin mini Type B connector into the controller’s USB consoleport and the other end of the cable into the PC’s USB Type A port. The first time that you connect aWindows PC to the USB console port, you are prompted to install the USB console driver. Follow theinstallation prompts to install the driver. The USB console driver maps to a COM port on your PC; youthen need to map the terminal emulator application to the COM port.NoteStep 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 controlStep 4 Plug the AC power cord into the controller and a grounded 100 to 240 VAC, 50/60-Hz electrical outlet.Turn on thepower supply. The bootup script displays operating system software initialization (code download and power-on selftest verification) and basic configuration.If the controller passes the power-on self test, the bootup script runs the configuration wizard, which prompts you forbasic configuration input.Configuring the Controller (GUI)Step 1 Connect your PC to the service port and configure it to use the same subnet as the controller.Step 2 Start Internet Explorer 6.0 SP1 (or later) or Firefox 2.0.0.11 (or later) on your PC and browse to http://192.168.1.1. Theconfiguration wizard appears.You can use both HTTP and HTTPS when using the service port interface. HTTPS is enabled by default andHTTP can also be enabled. The default IP address to connect to the service port interface is 192.168.1.1.Note   Cisco Wireless LAN Controller Configuration Guide, Release 7.416 OL-28744-01  Connecting the Console Port of the Controller
Figure 3: Configuration Wizard — System Information ScreenStep 3 In the System Name text box, enter the name that you want to assign to this controller. You can enter up to 31 ASCIIcharacters.Step 4 In the User Name text box, enter the administrative username to be assigned to this controller. You can enter up to 24ASCII characters. The default username is admin.Step 5 In the Password and Confirm Password text boxes, enter the administrative password to be assigned to this controller.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 wordCisco. In addition, you cannot substitute 1, I, or ! for i, 0 for o, or $ for s.Cisco Wireless LAN Controller Configuration Guide, Release 7.4       OL-28744-01 17Configuring the Controller (GUI)
Step 6 Click Next. The SNMP Summary screen appears.Figure 4: Configuration Wizard — SNMP Summary ScreenStep 7 If you want to enable Simple Network Management Protocol (SNMP) v1 mode for this controller, choose Enable fromthe SNMP v1 Mode drop-down list. Otherwise, leave this parameter set to Disable.SNMP manages nodes (servers, workstations, routers, switches, and so on) on an IP network. Currently, thereare three versions of SNMP: SNMPv1, SNMPv2c, and SNMPv3.NoteStep 8 If you want to enable SNMPv2c mode for this controller, leave this parameter set to Enable. Otherwise, choose Disablefrom the SNVP v2c Mode drop-down list.Step 9 If you want to enable SNMPv3 mode for this controller, leave this parameter set to Enable. Otherwise, choose Disablefrom the SNVP v3 Mode drop-down list.Step 10 Click Next.Step 11 When the following message appears, click OK:Default values are present for v1/v2c community strings.Please make sure to create new v1/v2c community strings once the system comes up.Please make sure to create new v3 users once the system comes up.   Cisco Wireless LAN Controller Configuration Guide, Release 7.418 OL-28744-01  Configuring the Controller (GUI)
The Service Interface Configuration screen appears.Figure 5: Configuration Wizard — Service Interface Configuration ScreenStep 12 If you want the controller’s service-port interface to obtain an IP address from a DHCP server, select the DHCP ProtocolEnabled check box. If you do not want to use the service port or if you want to assign a static IP address to the serviceport, leave the check box unselected.The service-port interface controls communications through the service port. Its IP address must be on a differentsubnet from the management interface. This configuration enables you to manage the controller directly orthrough a dedicated management network to ensure service access during network downtime.NoteStep 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 Netmasktext boxes.Step 14 Click Next.Cisco Wireless LAN Controller Configuration Guide, Release 7.4       OL-28744-01 19Configuring the Controller (GUI)
The LAG Configuration screen appears.Figure 6: Configuration Wizard — LAG Configuration ScreenStep 15 To enable link aggregation (LAG), choose Enabled from the Link Aggregation (LAG) Mode drop-down list. To disableLAG, leave this text box set to Disabled.Step 16 Click NextThe Management Interface Configuration screen appears.Figure 7: Configuration Wizard — Management Interface Configuration Screen   Cisco Wireless LAN Controller Configuration Guide, Release 7.420 OL-28744-01  Configuring the Controller (GUI)
The management interface is the default interface for in-band management of the controller and connectivityto enterprise services such as AAA servers.NoteStep 17 In the VLAN Identifier text box, enter the VLAN identifier of the management interface (either a valid VLAN identifieror 0for an untagged VLAN). The VLAN identifier should be set to match the switch interface configuration.Step 18 In the IP Address text box, enter the IP address of the management interface.Step 19 In the Netmask text box, enter the IP address of the management interface netmask.Step 20 In the Gateway text box, enter the IP address of the default gateway.Step 21 In the Port Number text box, enter the number of the port assigned to the management interface. Each interface is mappedto at least one primary port.Step 22 In the Backup Port text box, enter the number of the backup port assigned to the management interface. If the primaryport for the management interface fails, the interface automatically moves to the backup port.Step 23 In the Primary DHCP Server text box, enter the IP address of the default DHCP server that will supply IP addresses toclients, the controller’s management interface, and optionally, the service port interface.Step 24 In the Secondary DHCP Server text box, enter the IP address of an optional secondary DHCP server that will supply IPaddresses to clients, the controller’s management interface, and optionally, the service port interface.Step 25 Click Next. The AP-Manager Interface Configuration screen appears.This screen does not appear for Cisco 5500 Series Controllers because you are not required to configure anAP-manager interface. The management interface acts like an AP-manager interface by default.NoteStep 26 In the IP Address text box, enter the IP address of the AP-manager interface.Step 27 Click Next. The Miscellaneous Configuration screen appears.Figure 8: Configuration Wizard — Miscellaneous Configuration ScreenStep 28 In the RF Mobility Domain Name text box, enter the name of the mobility group/RF group to which you want thecontroller to belong.Cisco Wireless LAN Controller Configuration Guide, Release 7.4       OL-28744-01 21Configuring the Controller (GUI)
Although the name that you enter here is assigned to both the mobility group and the RF group, these groupsare not identical. Both groups define clusters of controllers, but they have different purposes. All of the controllersin an RF group are usually also in the same mobility group and vice versa. However, a mobility group facilitatesscalable, system-wide mobility and controller redundancy while an RF group facilitates scalable, system-widedynamic RF management.NoteStep 29 The Configured Country Code(s) text box shows the code for the country in which the controller will be used. If youwant to change the country of operation, select the check box for the desired country.You can choose more than one country code if you want to manage access points in multiple countries from asingle controller. After the configuration wizard runs, you must assign each access point joined to the controllerto a specific country.NoteStep 30 Click Next.Step 31 When the following message appears, click OK:Warning! To maintain regulatory compliance functionality, the country codesetting may only be modified by a network administrator or qualified IT professional.Ensure that proper country codes are selected before proceeding.?The Virtual Interface Configuration screen appears.Figure 9: Configuration Wizard — Virtual Interface Configuration ScreenStep 32 In the IP Address text box, enter the IP address of the controller’s virtual interface. You should enter a fictitious, unassignedIP address.The virtual interface is used to support mobility management, DHCP relay, and embedded Layer 3 securitysuch as guest web authentication and VPN termination. All controllers within a mobility group must be configuredwith the same virtual interface IP address.NoteStep 33 In the DNS Host Name text box, enter the name of the Domain Name System (DNS) gateway used to verify the sourceof certificates when Layer 3 web authorization is enabled.To ensure connectivity and web authentication, the DNS server should always point to the virtual interface. Ifa DNS hostname is configured for the virtual interface, then the same DNS hostname must be configured onthe DNS servers used by the client.Note   Cisco Wireless LAN Controller Configuration Guide, Release 7.422 OL-28744-01  Configuring the Controller (GUI)
Step 34 Click Next. The WLAN Configuration screen appears.Figure 10: Configuration Wizard — WLAN Configuration ScreenStep 35 In the Profile Name text box, enter up to 32 alphanumeric characters for the profile name to be assigned to this WLAN.Step 36 In the WLAN SSID text box, enter up to 32 alphanumeric characters for the network name, or service set identifier(SSID). The SSID enables basic functionality of the controller and allows access points that have joined the controllerto 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 changethis after the wizard is complete and the system is rebooted.?Cisco Wireless LAN Controller Configuration Guide, Release 7.4       OL-28744-01 23Configuring the Controller (GUI)
The RADIUS Server Configuration screen is displayed.Figure 11: Configuration Wizard — RADIUS Server Configuration ScreenStep 39 In the Server IP Address text 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.Due to security reasons, the RADIUS shared secret key reverts to ASCII mode even if you have selected HEXas the shared secret format from the Shared Secret Format drop-down list.Note   Cisco Wireless LAN Controller Configuration Guide, Release 7.424 OL-28744-01  Configuring the Controller (GUI)
Step 41 In the Shared Secret and Confirm Shared Secret text boxes, enter the secret key used by the RADIUS server.Step 42 In the Port Number text 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 text box set to Disabled.Step 44 Click Apply. The 802.11 Configuration screen appears.Figure 12: Configuration Wizard — 802.11 Configuration ScreenStep 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 selected. To disable support for any of thesenetworks, unselect 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, unselect this check box.The auto-RF feature enables the controller to automatically form an RF group with other controllers. The groupdynamically elects a leader to optimize RRM parameter settings, such as channel and transmit power assignment,for the group.NoteCisco Wireless LAN Controller Configuration Guide, Release 7.4       OL-28744-01 25Configuring the Controller (GUI)
Step 47 Click Next. The Set Time screen appears.Figure 13: Configuration Wizard — Set Time ScreenStep 48 To manually configure the system time on your controller, enter the current date in Month/DD/YYYY format and thecurrent 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 differencefrom Greenwich Mean Time (GMT) in the Delta Hours text box and the local minute difference from GMT in the DeltaMins text box.When manually setting the time zone, enter the time difference of the local current time zone with respect toGMT (+/–). For example, Pacific time in the United States is 8 hours behind GMT. Therefore, it is entered as–8.Note   Cisco Wireless LAN Controller Configuration Guide, Release 7.426 OL-28744-01  Configuring the Controller (GUI)
Step 50 Click Next. The Configuration Wizard Completed screen appears.Figure 14: Configuration Wizard — Configuration Wizard Completed ScreenStep 51 Click Save and Reboot to save your configuration and reboot the controller.Step 52 When the following message appears, click OK:Configuration will be saved and the controller will berebooted. Click ok to confirm.?The controller saves your configuration, reboots, and prompts you to log on.Configuring the Controller—Using the CLI Configuration WizardBefore You Begin•The available options appear in brackets after each configuration parameter. The default value appearsin all uppercase letters.•If you enter an incorrect response, the controller provides you with an appropriate error message, suchas “Invalid Response,”and returns you to the wizard prompt.•Press the hyphen key if you ever need to return to the previous command line.Step 1 When prompted to terminate the AutoInstall process, enter yes. If you do not enter yes, the AutoInstall process beginsafter 30 seconds.Cisco Wireless LAN Controller Configuration Guide, Release 7.4       OL-28744-01 27Configuring the Controller—Using the CLI Configuration Wizard
The AutoInstall feature downloads a configuration file from a TFTP server and then loads the configurationonto the controller automatically.NoteStep 2 Enter the system name, which is the name that you want to assign to the controller. You can enter up to 31 ASCIIcharacters.Step 3 Enter the administrative username and password to be assigned to this controller. You can enter up to 24 ASCII charactersfor 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 wordCisco. 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 donot want to use the service port or if you want to assign a static IP address to the service port, enter none.The service-port interface controls communications through the service port. Its IP address must be on a differentsubnet from the management interface. This configuration enables you to manage the controller directly orthrough a dedicated management network to ensure service access during network downtime.NoteStep 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.The management interface is the default interface for in-band management of the controller and connectivityto enterprise services such as AAA servers.NoteStep 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 ofthe controller, and optionally, the service port interface. Enter the IP address of the AP-manager interface.This prompt does not appear for Cisco 5500 Series Controllers because you are not required to configure anAP-manager interface. The management interface acts like an AP-manager interface by default.NoteStep 12 Enter the IP address of the controller’s virtual interface. You should enter a fictitious unassigned IP address.The virtual interface is used to support mobility management, DHCP relay, and embedded Layer 3 securitysuch as guest web authentication and VPN termination. All controllers within a mobility group must be configuredwith the same virtual interface IP address.NoteStep 13 If desired, enter the name of the mobility group/RF group to which you want the controller to belong.   Cisco Wireless LAN Controller Configuration Guide, Release 7.428 OL-28744-01  Configuring the Controller—Using the CLI Configuration Wizard
Although the name that you enter here is assigned to both the mobility group and the RF group, these groupsare not identical. Both groups define clusters of controllers, but they have different purposes. All of the controllersin an RF group are usually also in the same mobility group and vice versa. However, a mobility group facilitatesscalable, system-wide mobility and controller redundancy while an RF group facilitates scalable, system-widedynamic RF management.NoteStep 14 Enter the network name or service set identifier (SSID). The SSID enables basic functionality of the controller and allowsaccess 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 DHCPserver.Step 16 To configure a RADIUS server now, enter YES and then enter the IP address, communication port, and secret key ofthe RADIUS server. Otherwise, enter no. If you enter no, the following message appears: “Warning! The default WLANsecurity 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.Enter help to view the list of available countrycodes.NoteYou can enter more than one country code if you want to manage access points in multiple countries from asingle controller. To do so, separate the country codes with a comma (for example, US,CA,MX). After theconfiguration wizard runs, you need to assign each access point joined to the controller to a specific country.NoteStep 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.The auto-RF feature enables the controller to automatically form an RF group with other controllers. The groupdynamically elects a leader to optimize RRM parameter settings, such as channel and transmit power assignment,for the group.NoteStep 20 If you want the controller to receive its time setting from an external Network Time Protocol (NTP) server when it powersup, enter YES to configure an NTP server. Otherwise, enter no.The controller network module installed in a Cisco Integrated Services Router does not have a battery and cannotsave a time setting. Therefore, it must receive a time setting from an external NTP server when it powers up.NoteStep 21 If you entered no in Step 20 and want to manually configure the system time on your controller now, enter YES. If youdo 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:SSformat.Step 23 When prompted to verify that the configuration is correct, enter yes or NO.The controller saves your configuration, reboots, and prompts you to log on.Using the Controller Web GUIA web browser, or graphical user interface (GUI), is built into each controller.It allows up to five users to simultaneously browse into the controller HTTP or HTTPS (HTTP + SSL)management pages to configure parameters and monitor the operational status for the controller and itsassociated access points.Cisco Wireless LAN Controller Configuration Guide, Release 7.4       OL-28744-01 29Using the Controller Web GUI
We recommend that you enable the HTTPS interface and disable the HTTP interface to ensure more robustsecurity for your Cisco UWN solution.NoteGuidelines and LimitationsFollow these guidelines when using the controller GUI:•The GUI must be used on a PC running Windows 7, Windows XP SP1 (or later releases), or Windows2000 SP4 (or later releases).•The controller GUI is compatible with Microsoft Internet Explorer version 6.0 SP1 (or later versions)or Mozilla Firefox 2.0.0.11 (or later versions).Opera and Netscape are not supported.Note•You can use either the service port interface or the management interface to access the GUI. Werecommend that you use the service-port interface.•You can use both HTTP and HTTPS when using the service port interface. HTTPS is enabled by defaultand HTTP can also be enabled. The default IP address to connect to the service port interface is192.168.1.1.•Click Help at the top of any page in the GUI to display online help. You might need to disable yourbrowser’s pop-up blocker to view the online help.Logging On to the Web GUIStep 1 Enter the controller IP address in your browser’s address bar. For a secure connection, enter https://ip-address. For aless secure connection, enter http://ip-address.Step 2 When prompted, enter a valid username and password, and click OK.The Summary page is displayed.The administrative username and password that you created in the configuration wizard are case sensitive. Thedefault username is admin, and the default password is admin.Note   Cisco Wireless LAN Controller Configuration Guide, Release 7.430 OL-28744-01  Using the Controller Web GUI
Logging out of the GUIStep 1 Click Logout in the top right corner of the page.Step 2 Click Close to complete the log out process and prevent unauthorized users from accessing the controllercontroller GUI.Step 3 When prompted to confirm your decision, click Yes.Enabling Web and Secure Web ModesThis section provides instructions to enable the distribution system port as a web port (using HTTP) or as asecure web port (using HTTPS). You can protect communication with the GUI by enabling HTTPS. HTTPSprotects HTTP browser sessions by using the Secure Sockets Layer (SSL) protocol. When you enable HTTPS,the controller generates its own local web administration SSL certificate and automatically applies it to theGUI. You also have the option of downloading an externally generated certificate.You can configure web and secure web mode using the controller GUI or CLI.Enabling Web and Secure Web Modes (GUI)Step 1 Choose Management >HTTP-HTTPS.The HTTP-HTTPS Configuration page is displayed.Step 2 To enable web mode, which allows users to access the controller GUI using “http://ip-address,”choose Enabled fromthe HTTP Access drop-down list. Otherwise, choose Disabled. The default value is Disabled. Web mode is not a secureconnection.Step 3 To enable secure web mode, which allows users to access the controller GUI using “https://ip-address,”choose Enabledfrom the HTTPS Access drop-down list. Otherwise, choose Disabled. The default value is Enabled. Secure web modeis 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 toinactivity. 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 andautomatically applies it to the GUI. The details of the current certificate appear in the middle of the HTTP-HTTPSConfiguration page.If desired, you can delete the current certificate by clicking Delete Certificate and have the controller generatea new certificate by clicking Regenerate Certificate.NoteStep 7 Click Save Configuration.Cisco Wireless LAN Controller Configuration Guide, Release 7.4       OL-28744-01 31Using the Controller Web GUI
Enabling Web and Secure Web Modes (CLI)Step 1 Enable or disable web mode by entering this command:config network webmode {enable |disable}This command allows users to access the controller GUI using "http://ip-address." The default value is disabled. Webmode is not a secure connection.Step 2 Enable or disable secure web mode by entering this command:config network secureweb {enable |disable}This command allows users to access the controller GUI using “https://ip-address.”The default value is enabled. Secureweb mode is a secure connection.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 support128-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 thatis 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 ciphersuites) 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 summaryInformation similar to the following appears:Web Administration Certificate................. Locally GeneratedWeb Authentication Certificate................. Locally GeneratedCertificate compatibility mode:................ offStep 7 (Optional) Generate a new certificate by entering this command:config certificate generate webadminAfter a few seconds, the controller verifies that the certificate has been generated.Step 8 Save the SSL certificate, key, and secure web password to nonvolatile RAM (NVRAM) so that your changes are retainedacross reboots by entering this command:save configStep 9 Reboot the controller by entering this command:reset system   Cisco Wireless LAN Controller Configuration Guide, Release 7.432 OL-28744-01  Using the Controller Web GUI
Loading an Externally Generated SSL CertificateThis section describes how to load an externally generated SSL certificate.Information About Externally Generated SSL CertificatesYou can use a TFTP server to download an externally generated SSL certificate to the controller. Follow theseguidelines for using TFTP:•If you load the certificate through the service port, the TFTP server must be on the same subnet as thecontroller because the service port is not routable, or you must create static routes on the controller.Also, if you load the certificate through the distribution system network port, the TFTP server can beon any subnet.•A third-party TFTP server cannot run on the same PC as the Cisco Prime Infrastructure because thePrime Infrastructure built-in TFTP server and the third-party TFTP server require the same communicationport.Chained certificates are supported for web authentication only and not for themanagement certificate.NoteEvery HTTPS certificate contains an embedded RSA key. The length of the key canvary from 512 bits, which is relatively insecure, to thousands of bits, which is verysecure. When you obtain a new certificate from a Certificate Authority, make sure thatthe RSA key embedded in the certificate is at least 768 bits long.NoteCisco Wireless LAN Controller Configuration Guide, Release 7.4       OL-28744-01 33Loading an Externally Generated SSL Certificate
Loading an SSL Certificate (GUI)Step 1 On the HTTP Configuration page, select the Download SSL Certificate check box.Figure 15: HTTP Configuration PageStep 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 thecertificate.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,   Cisco Wireless LAN Controller Configuration Guide, Release 7.434 OL-28744-01  Loading an SSL Certificate (GUI)
Loading an SSL Certificate (CLI)Step 1 Use a password to encrypt the HTTPS certificate in a .PEM-encoded file. The PEM-encoded file is called a webadministration 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 nto the prompt:transfer download startInformation similar to the following appears:Mode........................................... TFTPData Type...................................... Admin CertTFTP Server IP................................. xxx.xxx.xxx.xxxTFTP Path...................................... <directory path>TFTP Filename..................................Are you sure you want to start? (y/n) nTransfer CanceledStep 4 Use these commands to change the download settings:transfer download mode tftptransfer download datatype webauthcerttransfer download serverip TFTP_server IP_addresstransfer download path absolute_TFTP_server_path_to_the_update_filetransfer download filename webadmincert_name.pemStep 5 To set the password for the .PEM file so that the operating system can decrypt the web administration SSL key andcertificate, enter this command:transfer download certpassword private_key_passwordStep 6 To confirm the current download settings and start the certificate and key download, enter this command and answer yto the prompt:transfer download startInformation similar to the following appears:Mode........................................... TFTPData Type...................................... Site CertTFTP Server IP................................. xxx.xxx.xxx.xxxTFTP Path...................................... directory pathTFTP Filename.................................. webadmincert_nameAre you sure you want to start? (y/n) yTFTP 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:Cisco Wireless LAN Controller Configuration Guide, Release 7.4       OL-28744-01 35Loading an SSL Certificate (CLI)
save configStep 8 To reboot the controller, enter this command:reset systemUsing the Controller CLIA Cisco UWN solution command-line interface (CLI) is built into each controller. The CLI enables you touse a VT-100 terminal emulation program to locally or remotely configure, monitor, and control individualcontrollers and its associated lightweight access points. The CLI is a simple text-based, tree-structured interfacethat allows up to five users with Telnet-capable terminal emulation programs to access the controller.See the Cisco Wireless LAN Controller Command Reference for information on specific commands.NoteIf you want to input any strings from the XML configuration into CLI commands, you must enclose thestrings in quotation marks.NoteLogging on to the Controller CLIYou can access the controller CLI using one of the following two methods:•A direct serial connection to the controller console port•A remote console session over Ethernet through the preconfigured service port or the distribution systemportsBefore you log on to the CLI, configure your connectivity and environment variables based on the type ofconnection you use.Guidelines and LimitationsOn Cisco 5500 Series Controllers, you can use either the RJ-45 console port or the USB console port. If youuse the USB console port, plug the 5-pin mini Type B connector into the controller’s USB console port andthe other end of the cable into the PC’s USB Type A port. The first time that you connect a Windows PC tothe USB console port, you are prompted to install the USB console driver. Follow the installation prompts toinstall the driver. The USB console driver maps to a COM port on your PC; you then need to map the terminalemulator application to the COM port.See the Configuring Telnet and Secure Shell Sessions section for information on enabling Telnet sessions.   Cisco Wireless LAN Controller Configuration Guide, Release 7.436 OL-28744-01  Using the Controller CLI
Using a Local Serial ConnectionBefore You BeginYou need these items to connect to the serial port:•A PC that is running a VT-100 terminal emulation program (such as HyperTerminal, ProComm, Minicom,or Tip)•A null-modem serial cableTo 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 controlMinimum serial timeout on Controller is 15 seconds instead of 1minute.NoteThe controller serial port is set for a 9600 baud rate and a short timeout. If you would like to change eitherof these values, enter config serial baudrate baudrate and config serial timeout timeout to make yourchanges. If you enter config serial timeout 0, serial sessions never time out.NoteStep 3 When prompted, enter a valid username and password to log into the controller. The administrative username andpassword that you created in the configuration wizard are case sensitive.The default username is admin, and the default password isadmin.NoteThe CLI displays the root level system prompt:#(system prompt)>The system prompt can be any alphanumeric string up to 31 characters. You can change it by entering the configprompt command.NoteUsing a Remote Ethernet ConnectionBefore You BeginYou need these items to connect to a controller remotely:•A PC with access to the controller over the Ethernet networkCisco Wireless LAN Controller Configuration Guide, Release 7.4       OL-28744-01 37Logging on to the Controller CLI
•The IP address of the controller•A VT-100 terminal emulation program or a DOS shell for the Telnet sessionBy default, controllers block Telnet sessions. You must use a local connection to the serial port to enableTelnet sessions.NoteStep 1 Verify that your VT-100 terminal emulation program or DOS shell interface is configured with these parameters:•Ethernet address•Port 23Step 2 Use the controller IP address to Telnet to the CLI.Step 3 When prompted, enter a valid username and password to log into the controller. The administrative username andpassword that you created in the configuration wizard are case sensitive.The default username is admin, and the default password isadmin.NoteThe CLI displays the root level system prompt.The system prompt can be any alphanumeric string up to 31 characters. You can change it by entering the configprompt command.NoteLogging Out of the CLIWhen you finish using the CLI, navigate to the root level and enter logout. The system prompts you to saveany changes you made to the volatile RAM.The CLI automatically logs you out without saving any changes after 5 minutes of inactivity. You can setthe automatic logout from 0 (never log out) to 160 minutes using the config serial timeout command.NoteNavigating the CLIThe CLI is organized into five levels:•Root Level•Level 2•Level 3•Level 4•Level 5   Cisco Wireless LAN Controller Configuration Guide, Release 7.438 OL-28744-01  Logging on to the Controller CLI
When you log into the CLI, you are at the root level. From the root level, you can enter any full commandwithout first navigating to the correct command level.The following table lists commands you use to navigate the CLI and to perform common tasks.Table 2: Commands for CLI Navigation and Common TasksActionCommandAt the root level, view system wide navigationcommandshelpView commands available at the current level?View parameters for a specific commandcommand ?Move down one levelexitReturn from any level to the root levelCtrl-ZAt the root level, save configuration changes fromactive working RAM to nonvolatile RAM (NVRAM)so they are retained after rebootsave configAt the root level, reset the controller without loggingoutreset systemUsing the AutoInstall Feature for Controllers Without a ConfigurationThis section describes how to use the AutoInstall feature for controllers without a configuration.Information About the AutoInstall FeatureWhen you boot up a controller that does not have a configuration, the AutoInstall feature can download aconfiguration file from a TFTP server and then load the configuration onto the controller automatically.If you create a configuration file on a controller that is already on the network (or through a Prime Infrastructurefilter), place that configuration file on a TFTP server, and configure a DHCP server so that a new controllercan get an IP address and TFTP server information, the AutoInstall feature can obtain the configuration filefor the new controller automatically.When the controller boots, the AutoInstall process starts. The controller does not take any action untilAutoInstall is notified that the configuration wizard has started. If the wizard has not started, the controllerhas a valid configuration.If AutoInstall is notified that the configuration wizard has started (which means that the controller does nothave a configuration), AutoInstall waits for an additional 30 seconds. This time period gives you an opportunityto respond to the first prompt from the configuration wizard:Would you like to terminate autoinstall? [yes]:Cisco Wireless LAN Controller Configuration Guide, Release 7.4       OL-28744-01 39Using the AutoInstall Feature for Controllers Without a Configuration
When the 30-second abort timeout expires, AutoInstall starts the DHCP client. You can abort the AutoInstalltask even after this 30-second timeout if you enter Yes at the prompt. However, AutoInstall cannot be abortedif the TFTP task has locked the flash and is in the process of downloading and installing a valid configurationfile.Guidelines and LimitationsAutoInstall uses the following interfaces:•Cisco 5500 Series Controllers◦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 TFTPServerAutoInstall attempts to obtain an IP address from the DHCP server until the DHCP process is successful oruntil you abort the AutoInstall process. The first interface to successfully obtain an IP address from the DHCPserver registers with the AutoInstall task. The registration of this interface causes AutoInstall to begin theprocess 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 ofevents to determine the host name of the controller and the IP address of the TFTP server. Each phase of thissequence gives preference to explicitly configured information over default or implied information and toexplicit 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, AutoInstallcreates a /etc/resolv.conf file. This file includes the domain name and the list of DNS servers that havebeen received. The Domain Name Server option provides the list of DNS servers, and the Domain Nameoption provides the domain name.•If the domain servers are not on the same subnet as the controller, static route entries are installed foreach domain server. These static routes point to the gateway that is learned through the DHCP Routeroption.•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 [.]) isused as the host name for the controller.◦A reverse DNS lookup is performed on the controller IP address. If DNS returns a hostname, thisname (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 lookupon this server name. If the DNS lookup is successful, the returned IP address is used as the IPaddress of the TFTP server.   Cisco Wireless LAN Controller Configuration Guide, Release 7.440 OL-28744-01  Guidelines and Limitations
◦If the DHCP Server Host Name (sname) text box is valid, AutoInstall performs a DNS lookup onthis name. If the DNS lookup is successful, the IP address that is returned is used as the IP addressof the TFTP server.◦If AutoInstall received the DHCP TFTP Server Address option, this address is used as the IPaddress of the TFTP server.◦AutoInstall performs a DNS lookup on the default TFTP server name (cisco-wlc-tftp). If the DNSlookup 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 addressof 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 IPaddress of the TFTP server. This static route points to the gateway that is learned through the DHCPRouter option.Selecting a Configuration FileAfter the hostname and TFTP server have been determined, AutoInstall attempts to download a configurationfile. AutoInstall performs three full download iterations on each interface that obtains a DHCP IP address. Ifthe interface cannot download a configuration file successfully after three attempts, the interface does notattempt further.The first configuration file that is downloaded and installed successfully triggers a reboot of the controller.After the reboot, the controller runs the newly downloaded configuration.AutoInstall searches for configuration files in the order in which the names are listed:•The filename that is provided by the DHCP Boot File Name option•The filename that is provided by the DHCP File text box•host name-confg•host name.cfg•base MAC address-confg (for example, 0011.2233.4455-confg)•serial number-confg•ciscowlc-confg•ciscowlc.cfgAutoInstall runs through this list until it finds a configuration file. It stops running if it does not find aconfiguration file after it cycles through this list three times on each registered interface.The downloaded configuration file can be a complete configuration, or it can be a minimal configurationthat provides enough information for the controller to be managed by the Cisco Prime Infrastructure. Fullconfiguration can then be deployed directly from the Prime Infrastructure.NoteCisco Wireless LAN Controller Configuration Guide, Release 7.4       OL-28744-01 41Guidelines and Limitations
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.NoteCisco Prime Infrastructure provides AutoInstall capabilities for controllers. A Cisco Prime Infrastructureadministrator can create a filter that includes the host name, the MAC address, or the serial number of thecontroller and associate a group of templates (a configuration group) to this filter rule. The PrimeInfrastructure pushes the initial configuration to the controller when the controller boots up initially. Afterthe controller is discovered, the Prime Infrastructure pushes the templates that are defined in theconfiguration group. For more information about the AutoInstall feature and Cisco Prime Infrastructure,see the Cisco Prime Infrastructure documentation.NoteExample: AutoInstall OperationThe following is an example of an AutoInstall process from start to finish:Welcome to the Cisco Wizard Configuration ToolUse the '-' character to backupWould you like to terminate autoinstall? [yes]:AUTO-INSTALL: starting now...AUTO-INSTALL: interface 'service-port' - setting DHCP TFTP Filename ==> 'abcd-confg'AUTO-INSTALL: interface 'service-port' - setting DHCP TFTP Server IP ==> 1.100.108.2AUTO-INSTALL: interface 'service-port' - setting DHCP siaddr ==> 1.100.108.2AUTO-INSTALL: interface 'service-port' - setting DHCP Domain Server[0] ==> 1.100.108.2AUTO-INSTALL: interface 'service-port' - setting DHCP Domain Name ==> 'engtest.com'AUTO-INSTALL: interface 'service-port' - setting DHCP yiaddr ==> 172.19.29.253AUTO-INSTALL: interface 'service-port' - setting DHCP Netmask ==> 255.255.255.0AUTO-INSTALL: interface 'service-port' - setting DHCP Gateway ==> 172.19.29.1AUTO-INSTALL: interface 'service-port' registeredAUTO-INSTALL: interation 1 -- interface 'service-port'AUTO-INSTALL: DNS reverse lookup 172.19.29.253 ===> 'wlc-1'AUTO-INSTALL: hostname 'wlc-1'AUTO-INSTALL: TFTP server 1.100.108.2 (from DHCP Option 150)AUTO-INSTALL: attempting download of 'abcd-confg'AUTO-INSTALL: TFTP status - 'TFTP Config transfer starting.' (2)AUTO-INSTALL: interface 'management' - setting DHCP file ==> 'bootfile1'AUTO-INSTALL: interface 'management' - setting DHCP TFTP Filename ==> 'bootfile2-confg'AUTO-INSTALL: interface 'management' - setting DHCP siaddr ==> 1.100.108.2AUTO-INSTALL: interface 'management' - setting DHCP Domain Server[0] ==> 1.100.108.2AUTO-INSTALL: interface 'management' - setting DHCP Domain Server[1] ==> 1.100.108.3AUTO-INSTALL: interface 'management' - setting DHCP Domain Server[2] ==> 1.100.108.4AUTO-INSTALL: interface 'management' - setting DHCP Domain Name ==> 'engtest.com'AUTO-INSTALL: interface 'management' - setting DHCP yiaddr ==> 1.100.108.238AUTO-INSTALL: interface 'management' - setting DHCP Netmask ==> 255.255.254.0AUTO-INSTALL: interface 'management' - setting DHCP Gateway ==> 1.100.108.1AUTO-INSTALL: interface 'management' registeredAUTO-INSTALL: TFTP status - 'Config file transfer failed - Error from server: File notfound' (3)AUTO-INSTALL: attempting download of 'wlc-1-confg'AUTO-INSTALL: TFTP status - 'TFTP Config transfer starting.' (2)AUTO-INSTALL: TFTP status - 'TFTP receive complete... updating configuration.' (2)AUTO-INSTALL: TFTP status - 'TFTP receive complete... storing in flash.' (2)AUTO-INSTALL: TFTP status - 'System being reset.' (2)Resetting system   Cisco Wireless LAN Controller Configuration Guide, Release 7.442 OL-28744-01  Guidelines and Limitations
Managing the Controller System Date and TimeThis section describes how to manage the date and time of a controller system.Information About Controller System Date and TimeYou can configure the controller system date and time at the time of configuring the controller using theconfiguration wizard. If you did not configure the system date and time through the configuration wizard orif you want to change your configuration, you can follow the instructions in this section to configure thecontroller to obtain the date and time from a Network Time Protocol (NTP) server or to configure the dateand time manually. Greenwich Mean Time (GMT) is used as the standard for setting the time zone on thecontroller.You can also configure an authentication mechanism between various NTP servers.Guidelines and Limitations•If you are configuring wIPS, you must set the controller time zone to UTC.•Cisco Aironet lightweight access points might not connect to the controller if the date and time are notset properly. Set the current date and time on the controller before allowing the access points to connectto it.•You can configure an authentication channel between the controller and the NTP server.Configuring an NTP Server to Obtain the Date and TimeEach NTP server IP address is added to the controller database. Each controller searches for an NTP serverand obtains the current time upon reboot and at each user-defined polling interval (daily to weekly).Use these commands to configure an NTP server to obtain the date and time:•To specify the NTP server for the controller, enter this command:config time ntp server index ip_address•To specify the polling interval (in seconds), enter this command:config time ntp intervalCisco Wireless LAN Controller Configuration Guide, Release 7.4       OL-28744-01 43Managing the Controller System Date and Time
Configuring NTP Authentication (GUI)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 IP address in the Server IP Address text box.Step 5 Enable NTP server authentication by selecting 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.Configuring NTP Authentication (CLI)By default, MD5 is used.Note•config time ntp auth enable server-index key-index•config time ntp auth disable server-index•config time ntp key-auth add key-index md5 key-format key•Delete an authentication key by entering this command:config time ntp key-auth delete key-index•View the list of NTP key Indices by entering this command:show ntp-keys   Cisco Wireless LAN Controller Configuration Guide, Release 7.444 OL-28744-01  Managing the Controller System Date and Time
Configuring the Date and Time (GUI)Step 1 Choose Commands > Set Time to open the Set Time page.Figure 16: Set Time PageThe 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.When you choose a time zone that uses Daylight Saving Time (DST), the controller automatically sets its systemclock to reflect the time change when DST occurs. In the United States, DST starts on the second Sunday inMarch and ends on the first Sunday in November.NoteYou cannot set the time zone delta on the controller GUI. However, if you do so on the controller CLI, thechange is reflected in the Delta Hours and Mins text boxes on the controller GUI.NoteStep 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 inthe Year text 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 theMinutes and Seconds text boxes.If you change the time zone location after setting the date and time, the values in the Time area are updated toreflect the time in the new time zone location. For example, if the controller is currently configured for noonEastern time and you change the time zone to Pacific time, the time automatically changes to 9:00 a.m.NoteStep 6 Click Set Date and Time to apply your changes.Step 7 Click Save Configuration to save your changes.Cisco Wireless LAN Controller Configuration Guide, Release 7.4       OL-28744-01 45Managing the Controller System Date and Time
Configuring the Date and Time (CLI)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:ssWhen setting the time, the current local time is entered in terms of GMT and as a value between 00:00 and24:00. For example, if it is 8:00 a.m. Pacific time in the United States, you would enter 16:00 because the Pacifictime zone is 8 hours behind GMT.NoteStep 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 enteringthis command:config time timezone location location_indexwhere location_index is a number representing one of the following time zone locations:1(GMT-12:00) International Date Line West2(GMT-11:00) Samoa3(GMT-10:00) Hawaii4(GMT-9:00) Alaska5(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-Atlantic12 (GMT-1:00) Azores13 (GMT) London, Lisbon, Dublin, Edinburgh (default value)14 (GMT +1:00) Amsterdam, Berlin, Rome, Vienna15 (GMT +2:00) Jerusalem16 (GMT +3:00) Baghdad17 (GMT +4:00) Muscat, Abu Dhabi18 (GMT +4:30) Kabul19 (GMT +5:00) Karachi, Islamabad, Tashkent20 (GMT +5:30) Colombo, Kolkata, Mumbai, New Delhi21 (GMT +5:45) Katmandu22 (GMT +6:00) Almaty, Novosibirsk   Cisco Wireless LAN Controller Configuration Guide, Release 7.446 OL-28744-01  Managing the Controller System Date and Time
23 (GMT +6:30) Rangoon24 (GMT +7:00) Saigon, Hanoi, Bangkok, Jakarta25 (GMT +8:00) Hong Kong, Beijing, Chongqing26 (GMT +9:00) Tokyo, Osaka, Sapporo27 (GMT +9:30) Darwin28 (GMT+10:00) Sydney, Melbourne, Canberra29 (GMT+11:00) Magadan, Solomon Is., New Caledonia30 (GMT+12:00) Kamchatka, Marshall Is., Fiji31 (GMT+12:00) Auckland (New Zealand)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.Note•Manually set the time zone so that DST is not set automatically by entering this command:config time timezone delta_hours delta_minswhere 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.You can manually set the time zone and prevent DST from being set only on the controllerCLI.NoteStep 3 Save your changes by entering this command:save configStep 4 Verify that the controller shows the current local time with respect to the local time zone by entering this command:show timeInformation similar to the following appears:Time.................................... Thu Apr 7 13:56:37 2011Timezone delta........................... 0:0Timezone location....................... (GMT +5:30) Colombo, New Delhi, Chennai, KolkataNTP ServersNTP Polling Interval......................... 3600Index NTP Key Index NTP Server NTP Msg Auth Status------- ---------------------------------------------------------------1 1 209.165.200.225 AUTH SUCCESSIf you configured the time zone location, the Timezone Delta value is set to “0:0.”If you manually configuredthe time zone using the time zone delta, the Timezone Location is blank.NoteCisco Wireless LAN Controller Configuration Guide, Release 7.4       OL-28744-01 47Managing the Controller System Date and Time
Configuring Telnet and Secure Shell SessionsThis section describes how to configure Telnet and Secure Shell (SSH) sessions.Information About Telnet and SSHTelnet is a network protocol used to provide access to the controller’s CLI. Secure Shell (SSH) is a moresecure version of Telnet that uses data encryption and a secure channel for data transfer. You can use thecontroller GUI or CLI to configure Telnet and SSH sessions.Restrictions for Telnet and SSH•Only the FIPS approved algorithm aes128-cbc is supported when using SSH to control WLANs.•The controller does not support raw Telnet mode.Configuring Telnet and SSH Sessions (GUI)Step 1 Choose Management >Telnet-SSH to open the Telnet-SSH Configuration page.Figure 17: Telnet-SSH Configuration Page   Cisco Wireless LAN Controller Configuration Guide, Release 7.448 OL-28744-01  Configuring Telnet and Secure Shell Sessions
Step 2 In the Telnet Login Timeout text box, enter the number of minutes that a Telnet session is allowed to remain inactivebefore being terminated. The valid range is 0 to 160 minutes (inclusive), and the default value is 5 minutes. A value of0 indicates no timeout.Step 3 From the Maximum Number of Sessions drop-down list, choose the number of simultaneous Telnet or SSH sessionsallowed. The valid range is 0 to 5 sessions (inclusive), and the default value is 5 sessions. A value of zero indicates thatTelnet/SSH sessions are disallowed.Step 4 From the Allow New Telnet Sessions drop-down list, choose Yes or No to allow or disallow new Telnet sessions onthe controller. The default value is No.Step 5 From the \drop-down list, choose Yes or No to allow or disallow new SSH sessions on the controller. The default valueis Yes.Step 6 Click Apply.Step 7 Click Save Configuration.Step 8 To see a summary of the Telnet configuration settings, choose Management >Summary. The Summary page appears.Figure 18: Summary PageThis page shows whether additional Telnet and SSH sessions are permitted.Configuring Telnet and SSH Sessions (CLI)Step 1 Allow or disallow new Telnet sessions on the controller by entering this command:config network telnet {enable |disable}The default value is disabled.Step 2 Allow or disallow new SSH sessions on the controller by entering this command:config network ssh {enable |disable}Cisco Wireless LAN Controller Configuration Guide, Release 7.4       OL-28744-01 49Configuring Telnet and Secure Shell Sessions
The default value is enabled.Step 3 Specify the number of minutes that a Telnet session is allowed to remain inactive before being terminated by enteringthis command:config sessions timeout timeoutwhere timeout is a value between 0 and 160 minutes (inclusive). The default value is 5 minutes. A value of 0 indicatesno timeout.Step 4 Specify the number of simultaneous Telnet or SSH sessions allowed by entering this command:config sessions maxsessions session_numwhere session_num is a value between 0 and 5 (inclusive). The default value is 5 sessions. A value of zero indicates thatTelnet/SSH sessions are disallowed.Step 5 Save your changes by entering this command:save configStep 6 See the Telnet and SSH configuration settings by entering this command:show network summaryInformation similar to the following appears:RF-Network Name............................. TestNetwork1Web Mode.................................... EnableSecure Web Mode............................. EnableSecure Web Mode Cipher-Option High.......... DisableSecure Web Mode Cipher-Option SSLv2......... DisableSecure Shell (ssh).......................... EnableTelnet................................... Disable...Step 7 See the Telnet session configuration settings by entering this command:show sessionsInformation similar to the following appears:CLI Login Timeout (minutes)............ 5Maximum Number of CLI Sessions....... 5Step 8 See all active Telnet sessions by entering this command:show loginsessionInformation similar to the following appears:ID User Name Connection From Idle Time Session Time-- --------------- --------------- ------------ ------------00 admin EIA-232 00:00:00 00:19:04Step 9 You can close all active Telnet sessions or a specific Telnet session by entering this command:config loginsession close {all |session_id}   Cisco Wireless LAN Controller Configuration Guide, Release 7.450 OL-28744-01  Configuring Telnet and Secure Shell Sessions
Troubleshooting Access Points Using Telnet or SSH_oldThe controller supports the use of the Telnet and Secure Shell (SSH) protocols to troubleshoot lightweightaccess points. Using these protocols makes debugging easier, especially when the access point is unable toconnect to the controller.•To avoid potential conflicts and security threats to the network, the following commands are unavailablewhile a Telnet or SSH session is enabled: config terminal, telnet, ssh, rsh, ping, traceroute, clear,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.For instructions on configuring Telnet or SSH SSH sessions on the controller, see theConfiguring Telnet and Secure Shell Sessions section.NoteTroubleshooting Access Points Using Telnet or SSH (GUI)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.Troubleshooting Access Points Using Telnet or SSH (CLI)Step 1 Enable Telnet or SSH connectivity on an access point by entering this command:config ap {telnet | ssh}enable Cisco_APThe default value is disabled.Disable Telnet or SSH connectivity on an access point by entering this command: config ap {telnet | ssh}disable Cisco_APNoteStep 2 Save your changes by entering this command:save configStep 3 See whether Telnet or SSH is enabled on an access point by entering this command:show ap config general Cisco_APCisco Wireless LAN Controller Configuration Guide, Release 7.4       OL-28744-01 51Configuring Telnet and Secure Shell Sessions
Information similar to the following appears:Cisco AP Identifier.............................. 5Cisco AP Name.................................... AP33Country code..................................... Multiple Countries:US,AE,AR,AT,AU,BHReg. Domain allowed by Country................... 802.11bg:-ABCENR 802.11a:-ABCENAP Country code.................................. US - United StatesAP Regulatory Domain............................. 802.11bg:-A 802.11a:-ASwitch Port Number .............................. 2MAC Address...................................... 00:19:2f:11:16:7aIP Address Configuration......................... Static IP assignedIP Address....................................... 10.22.8.133IP NetMask....................................... 255.255.248.0Gateway IP Addr.................................. 10.22.8.1Domain...........................................Name Server......................................Telnet State..................................... EnabledSsh State........................................ Enabled...Managing the Controller WirelesslyYou can monitor and configure controllers using a wireless client. This feature is supported for all managementtasks except uploads from and downloads to the controller.Before you can open the GUI or the CLI from a wireless client device, you must configure the controller toallow the connection.Enabling Wireless Connections (GUI)Step 1 Log onto the GUI.Step 2 Choose Management >Mgmt Via Wireless page.Step 3 Enable the Controller Management to be accessible from wireless clients.Step 4 Click Apply.   Cisco Wireless LAN Controller Configuration Guide, Release 7.452 OL-28744-01  Managing the Controller Wirelessly
Enabling Wireless Connections (CLI)Step 1 Log onto the CLI.Step 2 Enter the config network mgmt-via-wireless enable command.Step 3 Use a wireless client to associate to a lightweight access point connected to the controller.Step 4 On the wireless client, open a Telnet session to the controller, or browse to the controller GUI.Cisco Wireless LAN Controller Configuration Guide, Release 7.4       OL-28744-01 53Managing the Controller Wirelessly
   Cisco Wireless LAN Controller Configuration Guide, Release 7.454 OL-28744-01  Managing the Controller Wirelessly
CHAPTER 3Managing Licenses•Installing and Configuring Licenses, page 55•Rehosting Licenses, page 67•Configuring the License Agent, page 71Installing and Configuring LicensesInformation About Installing and Configuring LicensesYou can order Cisco 5500 Series Controllers with support for 12, 25, 50, 100, 250 or 500 access points as thecontroller’s base capacity. You can add additional access point capacity through capacity adder licensesavailable at 25, 50, 100 and 250 access point capacities. You can add the capacity adder licenses to any baselicense in any combination to arrive at the maximum capacity of 500 access points. The base and adder licensesare supported through both rehosting and RMAs.The base license supports the standard base software set, and the premium software set is included as part ofthe base feature set, which includes this functionality:•Datagram Transport Layer Security (DTLS) data encryption for added security across remote WAN andLAN links.•The availability of data DTLS is as follows:•Cisco 5500 Series Controller—The Cisco 5500 Series Controller is available with two licensingoptions: One with data DTLS capabilities and another image without data DTLS.•2500, WiSM2—These platforms by default do not contain DTLS. To turn on data DTLS, you mustinstall a license. These platforms will have a single image with data DTLS turned off. To use dataDTLS, you must have a license.•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 featuresare included in the base license:Cisco Wireless LAN Controller Configuration Guide, Release 7.4        OL-28744-01 55
•OfficeExtend AP•Enterprise Mesh•CAPWAP Data EncryptionFor information about upgrade and capacity adder licenses, see the product data sheet of your controller model.Restrictions for Using LicensesThe following are the restrictions you must keep in mind when using licenses for the controllers:•The licensing change can affect features on your wireless LAN when you upgrade or downgrade softwarereleases, so you should be aware of these guidelines:◦If you have a WPlus license and you upgrade from 6.0.x.x to 7.x.x.x, your license file containsboth Basic and WPlus license features. There is no disruption in feature availability and operation.◦If you have a WPlus license and you downgrade from 7.x.x.x to 6.0.196.0 or 6.0.188.0 or 6.0.182.0,your license file contains only base license, and you will lose all WPlus features.◦If you have a base license and you downgrade from 6.0.196.0 to 6.0.188.0 or 6.0.182.0, when youdowngrade, you lose all WPlus features.•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 controllerkeeps track of the licensed access point count and does not allow more than the number of access pointsto associate to it.•The Cisco 5500 Series Controller is shipped with both permanent and evaluation base and base-ap-countlicenses. If desired, you can activate the evaluation licenses, which are designed for temporary use andset to expire after 60 days.•No licensing steps are required after you receive your Cisco 5500 Series Controller because the licensesyou ordered are installed at the factory. In addition, licenses and product authorization keys (PAKs) arepreregistered to serial numbers. However, as your wireless network evolves, you might want to addsupport 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.Obtaining an Upgrade or Capacity Adder LicenseThis section describes how to get an upgrade or capacity adder license.Information About Obtaining an Upgrade or Capacity Adder LicenseA certificate with a product authorization key (PAK) is required before you can obtain an upgrade license.You can use the capacity adder licenses to increase the number of access points supported by the controllerup to a maximum of 500 access points. The capacity adder licenses are available in access point capacities of10, 25, 50, 100 and 250 access points. You can add these licenses to any of the base capacity licenses of 12,25, 50, 100 and 250 access points.   Cisco Wireless LAN Controller Configuration Guide, Release 7.456 OL-28744-01  Installing and Configuring Licenses
For example, if your controller was initially ordered with support for 100 access points (base licenseAIR-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/en/US/products/ps10315/products_data_sheets_list.htmlIf you skip any tiers when upgrading (for example, if you do not install the -25U and -50U licenses alongwith the -100U), the license registration for the upgraded capacity fails.NoteFor 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 (insteadof four) to install on your controller.If you have multiple controllers and want to upgrade all of them, you can order multiple quantities of eachupgrade license in one transaction (for example, you can order 10 each of the -25U, -50U, -100U, and -250upgrade licenses), for which you receive one PAK with one license. You can continue to register the PAKfor multiple controllers until it is exhausted.For more information about the base license SKUs and capacity adder licenses, see the respective controller’sdata sheet.Obtaining and Registering a PAK CertificateStep 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/orderingStep 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 receivethe certificate, use one of the following methods to register the PAK:•Cisco License Manager (CLM)—This method automates the process of obtaining licenses and deploying themon Cisco devices. For deployments with more than five controllers, we recommend using CLM to register PAKsand install licenses. You can also use CLM to rehost or RMA a license.You cannot use CLM to change the licensed feature set or activate an ap-count evaluation license. Toperform these operations, you must follow the instructions in the Activating an AP-Count EvaluationLicense section. Because you can use CLM to perform all other license operations, you can disregard theremaining licensing information in this chapter except these two sections and the Configuring the LicenseAgent section if you want your controller to use HTTP to communicate with CLM.NoteYou can download the CLM software and access user documentation at this URL: http://www.cisco.com/go/clmNote•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.Step 3 Use the licensing portal to register the PAK as follows:a) Go to http://tools.cisco.com/SWIFT/Licensing/PrivateRegistrationServletCisco Wireless LAN Controller Configuration Guide, Release 7.4       OL-28744-01 57Installing and Configuring Licenses
b) On the main Product License Registration page, enter the PAK mailed with the certificate in the Product AuthorizationKey (PAK) text box and click Submit.c) On the Validate Features page, enter the number of licenses that you want to register in the Qty text box and clickUpdate.d) To determine the controller’s product ID and serial number, choose Controller >Inventory on the controller GUIor enter the show license udi command on the controller CLI.Information similar to the following appears on the controller CLI:Device# PID SN UDI------- ------------------- --------------- -----------------------*0 AIR-CT5508-K9 CW1308L030 AIR-CT5508-K9:FCW1308L030e) On the Designate Licensee page, enter the product ID and serial number of the controller on which you plan to installthe license, read and accept the conditions of the end-user license agreement (EULA), complete the rest of the textboxes 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-mailedwithin 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 LicenseInstalling a License (GUI)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, thelicense 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 acceptthe terms of the agreement.Typically, you are prompted to accept the EULA for evaluation, extension, and rehost licenses. The EULA isalso required for permanent licenses, but it is accepted during license generation.NoteStep 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.You cannot save evaluationlicenses.Note   Cisco Wireless LAN Controller Configuration Guide, Release 7.458 OL-28744-01  Installing and Configuring Licenses
c) Click Save Licenses.Step 7 Reboot the controller.Installing a License (CLI)Step 1 Install a license on the controller by entering this command:license install urlwhere url is tftp://server_ip/path/filename.To remove a license from the controller, enter the license clear license_name command. For example, youmight want to delete an expired evaluation license or any unused license. You cannot delete unexpired evaluationlicenses, the permanent base image license, or licenses that are in use by the controller.NoteStep 2 If you are prompted to accept the end-user license agreement (EULA), read and accept the terms of the agreement.Typically, you are prompted to accept the EULA for evaluation, extension, and rehost licenses. The EULA isalso required for permanent licenses, but it is accepted during license generation.NoteStep 3 Add comments to a license or delete comments from a license by entering this command:license comment {add |delete}license_name comment_stringStep 4 Save a backup copy of all installed licenses by entering this command:license save urlwhere url is tftp://server_ip/path/filename.Step 5 Reboot the controller by entering this command:reset system.Viewing LicensesViewing Licenses (GUI)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, notin use, inactive, or EULA not accepted).Controller platforms do not support the status of “grace period”or “extension”as a license type. The licensestatus will always show “evaluation”even if a grace period or an extension evaluation license is installed.NoteCisco Wireless LAN Controller Configuration Guide, Release 7.4       OL-28744-01 59Installing and Configuring Licenses
If you ever want to remove a license from the controller, hover your cursor over the blue drop-down arrow forthe license and click Remove. For example, you might want to delete an expired evaluation license or anyunused license. You cannot delete unexpired evaluation licenses, the permanent base image license, or licensesthat are in use by the controller.NoteStep 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:•The license type (permanent, evaluation, or extension)•The license version•The status of the license (in use, not in use, inactive, or EULA not accepted)•The length of time before the license expiresPermanent licenses neverexpire.Note•Whether the license is a built-in license•The maximum number of access points allowed for this license•The number of access points currently using this licenseStep 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.Viewing Licenses (CLI)Before You Begin•See the license level, license type, and number of access points licensed on the controller by enteringthis command:show sysinfoInformation similar to the following appears:Manufacturer's Name.............................. Cisco Systems Inc.Product Name..................................... Cisco ControllerProduct Version.................................. 7.0RTOS Version..................................... 7.0Bootloader Version............................... 5.2Emergency Image Version.......................... N/ABuild Type....................................... DATA + WPSSystem Name...................................... Cisco 69System Location.................................. naSystem Contact................................... abc@cisco.comSystem ObjectID.................................. 1.3.6.1.4.1.14179.1.1.4.3IP Address....................................... 10.10.10.10System Up Time................................... 3 days 1 hrs 12 mins 42 secsSystem Timezone Location.........................CurrentBoot License Level..........................baseCurrentBoot License Type...........................PermanentNextBoot License Level............................baseNextBoot License Type.............................PermanentOperating Environment............................ Commercial (0 to 40 C)   Cisco Wireless LAN Controller Configuration Guide, Release 7.460 OL-28744-01  Installing and Configuring Licenses
Internal Temp Alarm Limits....................... 0 to 65 CInternal Temperature............................. +40 CState of 802.11b Network......................... EnabledState of 802.11a Network......................... EnabledNumber of WLANs.................................. 4Number of Active Clients......................... 0Burned-in MAC Address............................ 00:1A:6D:DD:1E:40Crypto Accelerator 1............................. AbsentCrypto Accelerator 2............................. AbsentPower Supply 1................................... AbsentPower Supply 2................................... Present, OKMaximum number of APs supported.................. 12The Operating Environment and Internal Temp Alarm Limits data are not displayed forCisco Flex 7500 Series Controllers.Note•See a brief summary of all active licenses installed on the controller by entering this command:show license summaryInformation similar to the following appears:Index 1 Feature: wplusPeriod left: 0 minute 0 secondIndex 2 Feature: wplus-ap-countPeriod left: 0 minute 0 secondIndex3 Feature: basePeriod left: Life timeLicense Type: PermanentLicense State: Active, In UseLicense Count: Non-CountedLicense Priority: MediumIndex 4 Feature: base-ap-countPeriod left: 6 weeks, 4 daysLicense Type: EvaluationLicense State: Active, In UseLicense Count: 250/250/0License Priority: High•See all of the licenses installed on the controller by entering this command:show license allInformation similar to the following appears:License Store: Primary License StorageStoreIndex: 1 Feature: base Version: 1.0License Type: PermanentLicense State: Active, Not in UseLicense Count: Non-CountedLicense Priority: MediumStoreIndex: 3 Feature: base-ap-count Version: 1.0License Type: EvaluationLicense State: Active, In UseEvaluation total period: 8 weeks 4 daysEvaluation period left: 8 weeks 3 daysLicense Count: 250/0/0License Priority: High•See the details for a particular license by entering this command:show license detail license_nameCisco Wireless LAN Controller Configuration Guide, Release 7.4       OL-28744-01 61Installing and Configuring Licenses
Information similar to the following appears:Index: 1 Feature: base-ap-count Version: 1.0License Type: PermanentLicense State: Active, Not in UseLicense Count: 12/0/0License Priority: MediumStore Index: 0Store Name: Primary License StorageIndex: 2 Feature: base-ap-count Version: 1.0License Type: EvaluationLicense State: InactiveEvaluation total period: 8 weeks 4 daysEvaluation period left: 8 weeks 4 daysLicense Count: 250/0/0License Priority: LowStore Index: 3Store Name: Evaluation License Storage•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:StoreIndex: 2 Feature: base-ap-count Version: 1.0License Type: PermanentLicense State: Active, In UseLicense Count: 12/12/0License Priority: MediumStoreIndex: 3 Feature: base Version: 1.0License Type: PermanentLicense State: Active, In UseLicense Count: Non-Counted License Priority: MediumController platforms do not support the status of “grace period”or “extension”as a licensetype. The license status will always show “evaluation”even if a grace period or anextension evaluation license is installed.Note•See the maximum number of access points allowed for this license on the controller, the number ofaccess points currently joined to the controller, and the number of access points that can still join thecontroller by entering this command:show license capacityInformation similar to the following appears:Licensed Feature Max Count Current Count Remaining Count---------------- --------- ------------- ---------------AP Count 250 4 246•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   Cisco Wireless LAN Controller Configuration Guide, Release 7.462 OL-28744-01  Installing and Configuring Licenses
Troubleshooting Licensing Issues•Configure debugging of license agent by entering this command:debug license agent {errors |all} {enable |disable}•Configure debugging of licensing core events and core errors by entering this command:debug license core {all |errors |events} {enable |disable}•Configure debugging of licensing errors by entering this command:debug license errors {enable |disable}•Configure debugging of licensing events by entering this command:debug license events {enable |disable}Activating an AP-Count Evaluation LicenseInformation About Activating an AP-Count Evaluation LicenseIf you are considering upgrading to a license with a higher access point count, you can try an evaluation licensebefore upgrading to a permanent version of the license. For example, if you are using a permanent licensewith a 50-access-point count and want to try an evaluation license with a 100-access-point count, you can tryout the evaluation license for 60 days.AP-count evaluation licenses are set to low priority by default so that the controller uses the ap-count permanentlicense. If you want to try an evaluation license with an increased access point count, you must change itspriority to high. If you no longer want to have this higher capacity, you can lower the priority of the ap-countevaluation license, which forces the controller to use the permanent license.To prevent disruptions in operation, the controller does not switch licenses when an evaluation licenseexpires. You must reboot the controller in order to return to a permanent license. Following a reboot, thecontroller defaults to the same feature set level as the expired evaluation license. If no permanent licenseat the same feature set level is installed, the controller uses a permanent license at another level or anunexpired evaluation license.NoteActivating an AP-Count Evaluation License (GUI)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 eachlicense.Step 2 Activate an ap-count evaluation license as follows:a) Click the link for the ap-count evaluation license that you want to activate. The License Detail page appears.b) Choose High from the Priority drop-down list and click Set Priority.You can set the priority only for ap-count evaluation licenses. AP-count permanent licenses always have amedium priority, which cannot be configured.NoteCisco Wireless LAN Controller Configuration Guide, Release 7.4       OL-28744-01 63Installing and Configuring Licenses
c) Click OK when prompted to confirm your decision about changing the priority of the 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 high priority andis in use. 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) On the Licenses page, click the link for the ap-count evaluation license that is in use.b) Choose Low from the Priority drop-down list and click Set Priority.You can set the priority only for ap-count evaluation licenses. AP-count permanent licenses always have amedium priority, which cannot be configured.Notec) Click OK when prompted to confirm your decision about changing the priority of the 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 andis not in use. Instead, the ap-count permanent license should be in use.Activating an AP-Count Evaluation License (CLI)Step 1 See the current status of all the licenses on your controller by entering this command:show license allInformation similar to the following appears:License Store: Primary License StorageStoreIndex: 0 Feature: base-ap-count Version: 1.0License Type: PermanentLicense State: Active, In UseLicense Count: 12/0/0License Priority: MediumStoreIndex: 1 Feature: base Version: 1.0License Type: PermanentLicense State: Active, In UseLicense Count: Non-CountedLicense Priority: MediumStoreIndex: 2 Feature: base Version: 1.0License Type: EvaluationLicense State: InactiveEvaluation total period: 8 weeks 4 daysEvaluation period left: 8 weeks 4 daysLicense Count: Non-CountedLicense Priority: LowStoreIndex: 3 Feature: base-ap-count Version: 1.0   Cisco Wireless LAN Controller Configuration Guide, Release 7.464 OL-28744-01  Installing and Configuring Licenses
License Type: EvaluationLicense State: InactiveEvaluation total period: 8 weeks 4 daysEvaluation period left: 8 weeks 4 daysLicense Count: 250/0/0License Priority: LowThe License State text box shows the licenses that are in use, and the License Priority text box shows the current priorityof each license.In the 7.2.110.0 release, the command output displays the full in-use count for active base-ap-count license eventhough there are no APs connected.NoteStep 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 highYou can set the priority only for ap-count evaluation licenses. AP-count permanent licenses always have amedium priority, which cannot be configured.Noteb) Reboot the controller in order for the priority change to take effect by entering this command:reset systemc) Verify that the ap-count evaluation license now has a high priority and is in use by entering this command:show license allYou 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 lowb) Reboot the controller in order for the priority change to take effect by entering this command:reset systemc) Verify that the ap-count evaluation license now has a low priority and is not in use by entering this command:show license allInstead, the ap-count permanent license should be in use.Configuring Right to Use LicensingInformation About Right to Use LicensingRight to Use (RTU) licensing is a model in which licenses are not tied to a unique device identifier (UDI),product ID, or serial number. Use RTU licensing to enable a desired AP license count on the controller afteryou accept the End User License Agreement (EULA). This allows you to add AP counts on a controllerinteracting with external tools.RTU licensing is supported only on Cisco Flex 7500 Series and Cisco 8500 Series Wireless LAN Controllers.In the RTU licensing model, the following types of licenses are available:Cisco Wireless LAN Controller Configuration Guide, Release 7.4       OL-28744-01 65Installing and Configuring Licenses
•Permanent or base licenses—These licenses are programmed into the controller hardware at the time ofmanufacturing. 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 acceptingthe RTU EULA. The EULA states that you are obliged to purchase the specified access point countlicenses at the time of activation. You must activate these licenses for the purchased access points countand accept the EULA.You can remove an adder license from one controller and transfer the license to another controller inthe 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 SeriesController.Licenses embedded in the controller at the time of shipment is not transferrable.Note•Evaluation licenses—These licenses are demo or trial mode licenses that are valid for 90 days. Fifteendays prior to the expiry of the 90-day period, you are notified about the requirement to buy the permanentlicense. These evaluation licenses are installed with the license image. You can activate the evaluationlicenses anytime with a command. A EULA is prompted after you run the activation command on thecontroller CLI. The EULA states that you are obligated to pay for the specified license count within 90days 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 RTUEULA. 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 enabledlicense count of the primary controller and support high availability for up to the license count enabled on theprimary controller.You can view the RTU licenses through the controller GUI or CLI. You can also view these licenses acrossmultiple wireless controllers through Cisco Prime Infrastructure.Configuring Right to Use Licensing (GUI)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, andclick Set Count.Step 3 Click Save Configuration.Configuring Right to Use Licensing (CLI)•Add or delete the number of APs that an AP license can support by entering this command:license {add |delete}ap-count count•Add or delete a license for a feature by entering this command:license {add |delete}feature license_name   Cisco Wireless LAN Controller Configuration Guide, Release 7.466 OL-28744-01  Installing and Configuring Licenses
•Activate or deactivate an evaluation AP count license by entering this command:license {activate |deactivate}ap-count evalWhen you activate the license, you are prompted to accept or reject the End User LicenseAgreement (EULA) for the given license. If you activate a license that supports fewernumber of APs than the current number of APs connected to the controller, the activationcommand fails.Note•Activate or deactivate a feature license by entering this command:license {activate |deactivate}feature license_name•See the licensing information by entering this command:show license allRehosting LicensesThis section describes how to rehost licenses.Information About Rehosting LicensesRevoking a license from one controller and installing it on another is called rehosting. You might want torehost a license in order to change the purpose of a controller. For example, if you want to move yourOfficeExtend or indoor mesh access points to a different controller, you could transfer the adder license fromone controller to another controller of the same model (intramodel transfer). This can be done in the case ofRMA or a network rearchitecture that requires you to transfer licenses from one appliance to another. It is notpossible to rehost base licenses in normal scenarios of network rearchitecture. The only exception where thetransfer of base licenses is allowed is for RMA when you get a replacement hardware when your existingappliance has a failure.Evaluation licenses cannot be rehosted.In order to rehost a license, you must generate credential information from the controller and use it to obtaina permission ticket to revoke the license from the Cisco licensing site. Next, you must obtain a rehost ticketand use it to obtain a license installation file for the controller on which you want to install the license.A revoked license cannot be reinstalled on the same controller.NoteStarting 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 toplan rehosting the installed adder licenses prior to an upgrade.NoteCisco Wireless LAN Controller Configuration Guide, Release 7.4       OL-28744-01 67Rehosting Licenses
Rehosting a LicenseRehosting a License (GUI)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 Ticketarea appears.Step 3 In the File Name to Save Credentials text box, enter the path on the TFTP server where you want the device credentialsto 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.To find the controller’s product ID and serial number, choose Controller >Inventory on the controllerGUI.Noted) Open the device credential information file that you saved in Step 3 and copy and paste the contents of the file intothe 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 andclick Continue.h) On the Designate Licensee page, enter the product ID and serial number of the controller for which you plan to revokethe license, read and accept the conditions of the End User License Agreement (EULA), complete the rest of the textboxes 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 rehostpermission 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 rehostpermission 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 torehost 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 Acceptto 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 anothercontroller 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 boxand click Continue.   Cisco Wireless LAN Controller Configuration Guide, Release 7.468 OL-28744-01  Rehosting Licenses
d) On the Validate Features page, verify that the license information for your controller is correct, enter the rehostquantity, and click Continue.e) On the Designate Licensee page, enter the product ID and serial number of the controller on which you plan to usethe license, read and accept the conditions of the End User License Agreement (EULA), complete the rest of the textboxes 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 licensekey 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.Rehosting a License (CLI)Step 1 Save device credential information to a file by entering this command:license save credential urlwhere url is tftp://server_ip/path/filename.Step 2 Obtain a permission ticket to revoke the license as follows:a) Go to https://tools.cisco.com/SWIFT/Licensing/PrivateRegistrationServlet. The Product License Registration pageappears.b) Under Manage Licenses, click Look Up a License.c) Enter the product ID and serial number for your controller.To find the controller’s product ID and serial number, enter the show license udi command on the controllerCLI.Noted) Open the device credential information file that you saved in Step 1 and copy and paste the contents of the file intothe 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 andclick Continue.h) On the Designate Licensee page, enter the product ID and serial number of the controller for which you plan to revokethe license, read and accept the conditions of the End-User License Agreement (EULA), complete the rest of the textboxes 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 rehostpermission 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_urlwhere permission_ticket_url is tftp://server_ip/path/filename.Cisco Wireless LAN Controller Configuration Guide, Release 7.4       OL-28744-01 69Rehosting Licenses
b) Generate the rehost ticket by entering this command:license revoke rehost rehost_ticket_urlwhere 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 anothercontroller 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 boxand click Continue.d) On the Validate Features page, verify that the license information for your controller is correct, enter the rehostquantity, and click Continue.e) On the Designate Licensee page, enter the product ID and serial number of the controller on which you plan to usethe license, read and accept the conditions of the End-User License Agreement (EULA), complete the rest of the textboxes 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 licensekey 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 58 section to install this license on anothercontroller.Transferring Licenses to a Replacement Controller after an RMAInformation About Transferring Licenses to a Replacement Controller after an RMAIf you return a Cisco 5500 Series Controller to Cisco as part of the Return Material Authorization (RMA)process, you must transfer that controller’s licenses within 60 days to a replacement controller that you receivefrom Cisco.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 isAIR-CT5508-CA-K9.Because licenses are registered to the serial number of a controller, you can use the licensing portal onCisco.com to request that the license from your returned controller be revoked and authorized for use on thereplacement controller. After your request is approved, you can install the old license on the replacementcontroller. Any additional ap-count licenses if installed in the returned controller has to be rehosted on thereplacement controller. Before you begin, you need the product ID and serial number of both the returnedcontroller and the replacement controller. This information is included in your purchase records.   Cisco Wireless LAN Controller Configuration Guide, Release 7.470 OL-28744-01  Rehosting Licenses
The evaluation licenses on the replacement controller are designed for temporary use and expire after 60days. To prevent disruptions in operation, the controller does not switch licenses when an evaluationlicense expires. You must reboot the controller in order to return to a permanent license. If the evaluationlicenses expire before you transfer the permanent licenses from your defective controller to your replacementcontroller, the replacement controller remains up and running using the permanent base license, but accesspoints are no longer able to join the controller.NoteTransferring a License to a Replacement Controller after an RMAStep 1 Browse to http://cisco.com/go/license.Step 2 On the Product License Registration page, choose Transfer >License for RMA.Step 3 Click Specify Device and then choose the controller model from the Product Family drop-down list.Step 4 Complete the on-screen instructions to generate the license file.The license is provided online or in an e-mail.Step 5 Copy the license file to the TFTP server.Step 6 Install the license by choosing Management >Software Activation >Commands >Action >Install License.Configuring the License AgentInformation About Configuring the License AgentIf your network contains various Cisco-licensed devices, you might want to consider using the Cisco LicenseManager (CLM) to manage all of the licenses using a single application. CLM is a secure client/serverapplication that manages Cisco software licenses network wide.The license agent is an interface module that runs on the controller and mediates between CLM and thecontroller’s licensing infrastructure. CLM can communicate with the controller using various channels, suchas HTTP, Telnet, and so on. If you want to use HTTP as the communication method, you must enable thelicense agent on the controller.The license agent receives requests from CLM and translates them into license commands. It also sendsnotifications to CLM. It uses XML messages over HTTP or HTTPS to receive the requests and send thenotifications. For example, CLM sends a license install command, and the agent notifies CLM after the licenseexpires.You can download the CLM software and access user documentation at http://www.cisco.com/go/clm.NoteCisco Wireless LAN Controller Configuration Guide, Release 7.4       OL-28744-01 71Configuring the License Agent
Configuring the License Agent (GUI)Step 1 Choose Management >Software Activation >License Agent to open the License Agent Configuration page.Step 2 Select the Enable Default Authentication check box to enable the license agent, or leave it unselected to disable thisfeature. The default value is unselected.Step 3 In the Maximum Number of Sessions text box, enter the maximum number of sessions for the license agent. The validrange is 1 to 25 sessions (inclusive).Step 4 Configure the license agent to listen for requests from the CLM as follows:a) Select the Enable Listener check box to enable the license agent to receive license requests from the CLM, or unselectthis check box to disable this feature. The default value is unselected.b) In the Listener Message Processing URL text box, enter the URL where the license agent receives license requests(for example, http://209.165.201.30/licenseAgent/custom). The Protocol parameter indicates whether the URL requiresHTTP or HTTPS.You can specify the protocol to use on the HTTP Configurationpage.Notec) Select the Enable Authentication for Listener check box to enable authentication for the license agent when it isreceiving license requests, or unselect this check box to disable this feature. The default value is unselected.d) In the Max HTTP Message Size text box, enter the maximum size for license requests. The valid range is 0 to 9999bytes, and the default value is 0.Step 5 Configure the license agent to send license notifications to the CLM as follows:a) Select the Enable Notification check box to enable the license agent to send license notifications to the CLM, orunselect this check box to disable this feature. The default value is unselected.b) In the URL to Send the Notifications text box, enter the URL where the license agent sends the notifications (forexample, http://www.cisco.com/license/notify).c) In the User Name text box, enter the username required in order to view the notification messages at this URL.d) In the Password and Confirm Password text boxes, enter the password required in order to view the notificationmessages at this URL.Step 6 Click Apply to commit your changes.Step 7 Click Save Configuration to save your changes.Configuring the License Agent (CLI)Step 1 Enable the license agent by entering one of these commands:•config license agent default authenticate—Enables the license agent default listener with authentication.•config license agent default authenticate none—Enables the license agent default listener without authentication.To disable the license agent default listener, enter the config license agent default disable command.The default value is disabled.Note   Cisco Wireless LAN Controller Configuration Guide, Release 7.472 OL-28744-01  Configuring the License Agent
Step 2 Specify the maximum number of sessions for the license agent by entering this command:config license agent max-sessions sessionsThe valid range for the sessions parameter is 1 to 25 (inclusive), and the default value is 9.Step 3 Enable the license agent to receive license requests from the CLM and to specify the URL where the license agent receivesthe requests by entering this command:config license agent listener http {plaintext |encrypt}url authenticate [none] [max-message size] [acl acl]The valid range for the size parameter is 0 to 65535 bytes, and the default value is 0.To prevent the license agent from receiving license requests from the CLM, enter the config license agentlistener http disable command. The default value is disabled.NoteStep 4 Configure the license agent to send license notifications to the CLM and to specify the URL where the license agentsends the notifications by entering this command:config license agent notify url username passwordTo prevent the license agent from sending license notifications to the CLM, enter the config license agent notifydisable username password command. The default value is disabled.NoteStep 5 Enter the save config command to save your changes.Step 6 See statistics for the license agent’s counters or sessions by entering this command:show license agent {counters |sessions}Information similar to the following appears for the show license agent counters command:License Agent CountersRequest Messages Received:10: Messages with Errors:1Request Operations Received:9: Operations with Errors:0Notification Messages Sent:12: Transmission Errors:0: Soap Errors:0Information similar to the following appears for the show license agent sessions command:License Agent Sessions: 1 open, maximum is 9To clear the license agent’s counter or session statistics, enter the clear license agent {counters |sessions}command.NoteCisco Wireless LAN Controller Configuration Guide, Release 7.4       OL-28744-01 73Configuring the License Agent
   Cisco Wireless LAN Controller Configuration Guide, Release 7.474 OL-28744-01  Configuring the License Agent
CHAPTER 4Configuring 802.11 Bands•Configuring 802.11 Bands, page 75•Configuring Band Selection, page 78Configuring 802.11 BandsInformation About Configuring 802.11 BandsYou can configure the 802.11b/g/n (2.4-GHz) and 802.11a/n (5-GHz) bands for the controller to comply withthe regulatory requirements in your country. By default, both 802.11b/g/n and 802.11a/n are enabled.When a controller is configured to allow only 802.11g traffic, 802.11b client devices are able to successfullyconnect to an access point but cannot pass traffic. When you configure the controller for 802.11g traffic only,you must mark 11g rates as mandatory.Configuring the 802.11 Bands (GUI)Step 1 Choose Wireless >802.11a/n 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 theband, 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 networksupport. 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.The beacon period in controllers is listed in terms of milliseconds. The beacon period can also be measured intime units, where one time unit equals 1024 microseconds or 102.4 milliseconds. If a beacon interval is listedas 100 milliseconds in a controller, it is only a rounded off value for 102.4 milliseconds. Due to hardwarelimitation in certain radios, even though the beacon interval is, say 100 time units, it is adjusted to 102 timeunits, which roughly equals 104.448 milliseconds. When the beacon period is to be represented in terms of timeunits, the value is adjusted to the nearest multiple of 17.NoteCisco Wireless LAN Controller Configuration Guide, Release 7.4        OL-28744-01 75
Step 5 Specify the size at which packets are fragmented by entering a value between 256 and 2346 bytes (inclusive) in theFragmentation Threshold text box. Enter a low number for areas where communication is poor or where there is a greatdeal 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 theaccess points and adjust their settings automatically. For example, a client device used primarily in Japan could rely onDTPC to adjust its channel and power settings automatically when it travels to Italy and joins a network there.On access points that run Cisco IOS software, this feature is called worldmode.NoteDTPC and 801.11h power constraint cannot be enabled simultaneously.NoteStep 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 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 MbpsFor each data rate, choose one of these options:•Mandatory—Clients must 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 thatrate. However, the clients are not required to be able to use this rate in order to associate.•Disabled—The clients specify the data rates used for communication.Step 9 Click Apply.Step 10 Click Save Configuration.Configuring the 802.11 Bands (CLI)Step 1 Disable the 802.11a band by entering this command:config 802.11a disable networkThe 802.11a band must be disabled before you can configure the 802.11a network parameters in this section.NoteStep 2 Disable the 802.11b/g band by entering this command:config 802.11b disable networkThe 802.11b band must be disabled before you can configure the 802.11b network parameters in this section.NoteStep 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   Cisco Wireless LAN Controller Configuration Guide, Release 7.476 OL-28744-01  Configuring 802.11 Bands
where time_unit is the beacon interval in time units (TUs). One TU is 1024 microseconds. You can configure the accesspoint 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 thresholdwhere threshold is a value between 256 and 2346 bytes (inclusive). Specify a low number for areas where communicationis 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 thiscommand:config {802.11a |802.11b }dtpc {enable |disable}The default value is enabled. Client devices using dynamic transmit power control (DTPC) receive the channel andpower level information from the access points and adjust their settings automatically. For example, a client device usedprimarily in Japan could rely on DTPC to adjust its channel and power settings automatically when it travels to Italy andjoins a network there.On access points that run Cisco IOS software, this feature is called worldmode.NoteStep 6 Specify the maximum allowed clients that can be configured by entering this command:config {802.11a |802.11b}max-clients max_allow_clientsThe valid range is between 1 to 200.Step 7 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}ratewhere•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 thatrate. However, the clients are not required to be able to use this rate in order to associate.•rate—The rate at which data is transmitted:◦6, 9, 12, 18, 24, 36, 48, and 54 Mbps (802.11a)◦1, 2, 5.5, 6, 9, 11, 12, 18, 24, 36, 48, or 54 Mbps (802.11b/g)Step 8 Enable the 802.11a band by entering this command:config 802.11a enable networkThe default value is enabled.Step 9 Enable the 802.11b band by entering this command:config 802.11b enable networkThe default value is enabled.Step 10 Enable or disable 802.11g network support by entering this command:config 802.11b 11gSupport {enable |disable}Cisco Wireless LAN Controller Configuration Guide, Release 7.4       OL-28744-01 77Configuring 802.11 Bands
The default value is enabled. You can use this command only if the 802.11b band is enabled. If you disable this feature,the 802.11b band is enabled without 802.11g support.Step 11 Enter the save config command to save your changes.Step 12 View the configuration settings for the 802.11a or 802.11b/g band by entering this command:show {802.11a |802.11b}Information similar to the following appears:802.11a Network............................... Enabled11nSupport.................................... Enabled802.11a Low Band........................... Enabled802.11a Mid Band........................... Enabled802.11a High Band.......................... Enabled802.11a Operational Rates802.11a 6M Rate.............................. Mandatory802.11a 9M Rate.............................. Supported802.11a 12M Rate............................. Mandatory802.11a 18M Rate............................. Supported802.11a 24M Rate............................. Mandatory802.11a 36M Rate............................. Supported802.11a 48M Rate............................. Supported802.11a 54M Rate............................. Supported...Beacon Interval.................................. 100...Default Channel............................... 36Default Tx Power Level........................ 1DTPC Status................................... EnabledFragmentation Threshold....................... 2346Maximum Number of Clients per AP................. 200Configuring Band SelectionInformation About Configuring Band SelectionBand selection enables client radios that are capable of dual-band (2.4- and 5-GHz) operation to move to aless congested 5-GHz access point. The 2.4-GHz band is often congested. Clients on this band typicallyexperience interference from Bluetooth devices, microwave ovens, and cordless phones as well as co-channelinterference from other access points because of the 802.11b/g limit of three nonoverlapping channels. Toprevent these sources of interference and improve overall network performance, you can configure bandselection on the controller.Band selection is enabled globally by default.Band selection works by regulating probe responses to clients. It makes 5-GHz channels more attractive toclients by delaying probe responses to clients on 2.4-GHz channels.   Cisco Wireless LAN Controller Configuration Guide, Release 7.478 OL-28744-01  Configuring Band Selection
Restrictions on Band Selection•Band-selection enabled WLANs do not support time-sensitive applications like voice and video becauseof roaming delays.•Band selection can be used only with Cisco Aironet 1040, 1140, 1250, 1260, 3500, and the 3600 seriesaccess points.OEAP 600 Series access points do not support band select.Note•Band selection operates only on access points that are connected to a controller. A FlexConnect accesspoint without a controller connection does not perform band selection after a reboot.•The band-selection algorithm directs dual-band clients only from the 2.4-GHz radio to the 5-GHz radioof the same access point, and it only runs on an access point when both the 2.4-GHz and 5-GHz radiosare up and running.•You can enable both band selection and aggressive load balancing on the controller. They runindependently and do not impact one another.•It is not possible to enable or disable band selection and client load balancing globally through thecontroller GUI or CLI. You can, however, enable or disable band selection and client load balancingfor a particular WLAN. Band selection and client load balancing are enabled globally by default.Cisco Wireless LAN Controller Configuration Guide, Release 7.4       OL-28744-01 79Configuring Band Selection
Configuring Band SelectionConfiguring Band Selection (GUI)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. The cycle count sets the number of suppressioncycles 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 thescan cycle period threshold. This setting determines the time threshold during which new probe requests from a clientcome from a new scanning cycle. 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 setsthe expiration time for pruning previously known 802.11b/g/n clients. The default value is 20 seconds. After this timeelapses, 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 theexpiration 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 theminimum RSSI for a client to respond to a probe. The default value is –80 dBm.Step 7 Click Apply.Step 8 Click Save Configuration.Step 9 To enable or disable band selection on specific WLANs, choose WLANs >WLAN ID. The WLANs > Edit pageappears.Step 10 Click the Advanced tab.Step 11 In the Load Balancing and Band Select text area, if you want to enable band selection, select the Client Band Selectcheck box. If you want to disable band selection, leave the check box unselected. The default value is disabled.Step 12 Click Save Configuration.Configuring Band Selection (CLI)Step 1 Set the probe cycle count for band select by entering this command:config band-select cycle-count cycle_countYou 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 millisecondsYou 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   Cisco Wireless LAN Controller Configuration Guide, Release 7.480 OL-28744-01  Configuring Band Selection
You can enter a value for suppression between 10 to 200 for the seconds parameter.Step 4 Set the dual band expire by entering this command:config band-select expire dual-band secondsYou can enter a value for dual band between 10 and 300 for the seconds parameter.Step 5 Set the client RSSI threshold by entering this command:config band-select client-rssi client_rssiYou can enter a value for minimum dBm of a client RSSI to respond to a probe between 20 and 90 for the client_rssiparameter.Step 6 Enter the save config command to save your changes.Step 7 Enable or disable band selection on specific WLANs by entering this command:config wlan band-select allow {enable |disable}wlan_IDYou can enter a value between 1 and 512 for wlan_ID parameter.Step 8 Verify your settings by entering this command:show band-selectInformation similar to the following appears:Band Select Probe Response....................... EnabledCycle Count................................... 3 cyclesCycle Threshold............................... 300 millisecondsAge Out Suppression........................... 20 secondsAge Out Dual Band............................. 20 secondsClient RSSI................................... -30 dBmStep 9 Enter the save config command to save your changes.Cisco Wireless LAN Controller Configuration Guide, Release 7.4       OL-28744-01 81Configuring Band Selection
   Cisco Wireless LAN Controller Configuration Guide, Release 7.482 OL-28744-01  Configuring Band Selection
CHAPTER 5Configuring 802.11 Parameters•Configuring the 802.11n Parameters, page 83•Configuring 802.11h Parameters, page 86Configuring the 802.11n ParametersInformation About Configuring the 802.11n ParametersThis section provides instructions for managing 802.11n devices such as the Cisco Aironet 1140 and 3600Series Access Points on your network. The 802.11n devices support the 2.4- and 5-GHz bands and offerhigh-throughput data rates.The 802.11n high-throughput rates are available on all 802.11n access points for WLANs using WMM withno Layer 2 encryption or with WPA2/AES encryption enabled.Some Cisco 802.11n APs may intermittently emit incorrect beacon frames, which can trigger false wIPSalarms. We recommend that you ignore these alarms. The issue is observed in the following Cisco 802.11nAPs: 1140, 1250, 2600, 3500, and 3600.NoteConfiguring the 802.11n Parameters (GUI)Step 1 Choose Wireless >802.11a/n or 802.11b/g/n >High Throughput to open the (5 GHz or 2.4 GHz) High Throughputpage.Step 2 Select the 11n Mode check box to enable 802.11n support on the network. The default value is enabled.Step 3 Select the check boxes of the desired rates to specify the modulation and coding scheme (MCS) rates at which data canbe transmitted between the access point and the client. These data rates, which are calculated for a 20-MHz channelwidth using a short guard interval, are available:•0 (7 Mbps)Cisco Wireless LAN Controller Configuration Guide, Release 7.4        OL-28744-01 83
•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 determinethe number of spatial streams, the modulation, the coding rate, and the data rate values that are used.Step 4 Click Apply.Step 5 Use the 802.11n data rates that you configured by enabling WMM on the WLAN as follows:a) Choose WLANs to open the WLANs page.b) Click the ID number of the WLAN for which you want to configure WMM mode.c) When the WLANs > Edit page appears, choose the QoS tab to open the WLANs > Edit (Qos) page.d) From the WMM Policy drop-down list, choose Required or Allowed to require or allow client devices to use WMM.Devices that do not support WMM cannot join the WLAN.If you choose Allowed, devices that cannot support WMM can join the WLAN but will not benefit from the 802.11nrates.e) Click Apply.Step 6 Click Save Configuration.To determine if an access point supports 802.11n, look at the 11n Supported text box on either the 802.11a/n(or 802.11b/g/n) Cisco APs > Configure page or the 802.11a/n (or 802.11b/g/n) AP Interfaces > Details page.NoteConfiguring the 802.11n Parameters (CLI)•Enable 802.11n support on the network by entering this command:config {802.11a |802.11b}11nsupport {enable |disable}   Cisco Wireless LAN Controller Configuration Guide, Release 7.484 OL-28744-01  Configuring the 802.11n Parameters
•Specify the modulation and coding scheme (MCS) rates at which data can be transmitted between theaccess point and the client by entering this command:config {802.11a |802.11b}11nsupport mcs tx {0-15} {enable |disable}•Use the 802.11n data rates that you configured by enabling WMM on the WLAN as follows:config wlan wmm {allow |disable |require}wlan_idThe require parameter requires client devices to use WMM. Devices that do not support WMM cannotjoin the WLAN.If set to allow, devices that cannot support WMM can join the WLAN but do not benefit from 802.11nrates.•Specify the aggregation method used for 802.11n packets as follows:a) Disable the network by entering this command:config {802.11a |802.11b}disable networkb) Specify the aggregation method entering this command:config {802.11a |802.11b}11nsupport {a-mpdu |a-msdu}tx priority {0-7 |all} {enable |disable}Aggregation is the process of grouping packet data frames together rather than transmitting themseparately. Two aggregation methods are available: Aggregated MAC Protocol Data Unit (A-MPDU)and Aggregated MAC Service Data Unit (A-MSDU). A-MSDU is performed in hardware andtherefore is the default method.You can specify the aggregation method for various types of traffic from the access point to theclients. This table defines the priority levels (0-7) assigned per traffic type.Table 3: Traffic Type Priority LevelsTraffic TypeUser PriorityBest effort0Background1Spare2Excellent effort3Controlled load4Video, less than 100-ms latency and jitter5Voice, less than 10-ms latency and jitter6Network control7You can configure each priority level independently, or you can use the all parameter to configureall of the priority levels at once. When you use the enable command, the traffic associated with thatpriority level uses A-MPDU transmission. When you use the disable command, the traffic associatedwith that priority level uses A-MSDU transmission. Configure the priority levels to match theCisco Wireless LAN Controller Configuration Guide, Release 7.4       OL-28744-01 85Configuring the 802.11n Parameters
aggregation method used by the clients. By default, A-MPDU is enabled for priority level 0, 4 and5 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}Configuring 802.11h ParametersInformation About Configuring 802.11h Parameters802.11h informs client devices about channel changes and can limit the transmit power of those client devices.Configuring the 802.11h Parameters (GUI)Step 1 Disable the 802.11 band as follows:a) Choose Wireless > 802.11a/n > Network to open the 802.11a Global Parameters page.b) Unselect the 802.11a Network Status check box.c) Click Apply.Step 2 Choose Wireless > 802.11a/n > DFS (802.11h) to open the 802.11h Global Parameters page.Step 3 In the Power Constraint area, enter the local power constraint. The valid range is between 0 dBm and 30 dBm.Step 4 In the Channel Switch Announcement area, select the Channel Announcement check box if you want the access pointto announce when it is switching to a new channel and the new channel number, or unselect this check box to disablethe channel announcement. The default value is disabled.Step 5 If you enabled the channel announcement, the Channel Quiet Mode check box appears. Select this check box if youwant the access point to stop transmitting on the current channel, or unselect this check box to disable quiet mode. Thedefault value is disabled.Step 6 Click Apply.Step 7 Reenable the 802.11a band as follows:a) Choose Wireless > 802.11a/n > Network to open the 802.11a Global Parameters page.   Cisco Wireless LAN Controller Configuration Guide, Release 7.486 OL-28744-01  Configuring 802.11h Parameters
b) Select the 802.11a Network Status check box.c) Click Apply.Step 8 Click Save Configuration.Configuring the 802.11h Parameters (CLI)Step 1 Disable the 802.11a network by entering this command:config 802.11a disable networkStep 2 Enable or disable an access point to announce when it is switching to a new channel, and the new channel number byentering this command:config 802.11h channelswitch {enable |disable}switch_modeEnter either 0 or 1 for the switch_mode parameter to specify whether transmissions are restricted until the actual channelswitch (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 channelStep 4 Configure the 802.11h power constraint value by entering this command:config 802.11h powerconstraint valueUse increments of 3 dB for the value so that the AP goes down one power level at a time.Step 5 Reenable the 802.11a network by entering this command:config 802.11a enable networkStep 6 View the status of the 802.11h parameters by entering this command:show 802.11hInformation similar to the following appears:Power Constraint................................. 0Channel Switch................................... DisabledChannel Switch Mode.............................. 0Cisco Wireless LAN Controller Configuration Guide, Release 7.4       OL-28744-01 87Configuring 802.11h Parameters
   Cisco Wireless LAN Controller Configuration Guide, Release 7.488 OL-28744-01  Configuring 802.11h Parameters
CHAPTER 6Configuring DHCP Proxy•Information About Configuring DHCP Proxy, page 89•Restrictions on Using DHCP Proxy, page 89•Configuring DHCP Proxy (GUI), page 90•Configuring DHCP Proxy (CLI), page 90•Configuring a DHCP Timeout (GUI), page 91•Configuring a DHCP Timeout (CLI), page 91Information About Configuring DHCP ProxyWhen DHCP proxy is enabled on the controller, the controller unicasts DHCP requests from the client to theconfigured servers. At least one DHCP server must be configured on either the interface associated with theWLAN or the WLAN itself.When DHCP proxy is disabled on the controller, those DHCP packets transmitted to and from the clients arebridged by the controller without any modification to the IP portion of the packet. Packets received from theclient are removed from the CAPWAP tunnel and transmitted on the upstream VLAN. DHCP packets directedto the client are received on the upstream VLAN, converted to 802.11, and transmitted through a CAPWAPtunnel toward the client. As a result, the internal DHCP server cannot be used when DHCP proxy is disabled.The ability to disable DHCP proxy allows organizations to use DHCP servers that do not support Cisco’snative proxy mode of operation. It should be disabled only when required by the existing infrastructure.DHCP proxy is enabled by default.NoteRestrictions on Using DHCP Proxy•DHCP proxy must be enabled in order for DHCP option 82 to operate correctly.•All controllers that will communicate must have the same DHCP proxy setting.Cisco Wireless LAN Controller Configuration Guide, Release 7.4        OL-28744-01 89
Configuring DHCP Proxy (GUI)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.Configuring DHCP Proxy (GUI)Step 1 Choose Controller > Interfaces.Step 2 Select the interface you want to configure the DHCP proxy.You can configure the DHCP proxy on the management, virtual, ap manager, or dynamic interfaces in the controller.The Interfaces > Edit page is displayed with DHCP information on the primary and secondary DHCP servers configuredin the controller. If the primary and secondary servers are not listed, you must enter values for the IP address of theDHCP servers in the text boxes displayed in this window.Step 3 Select from the following option of the proxy mode drop-down to enable DHCP proxy on the selected managementinterface:Global—Uses the global DHCP proxy mode on the controller.Enabled—Enables the DHCP proxy mode onthe interface. When you enable DHCP proxy on the controller; the controller unicasts the DHCP requests from the clientto the configured servers. You must configure at least one DHCP server on either the interface associated with the WLANor on the WLAN.Disabled—Disables the DHCP proxy mode on the interface. When you disable the DHCP proxy onthe controller, the DHCP packets transmitted to and from the clients are bridged by the controller without any modificationto the IP portion of the packet. Packets received from the client are removed from the CAPWAP tunnel and transmittedon the upstream VLAN. DHCP packets directed to the client are received on the upstream VLAN, converted to 802.11,and transmitted through a CAPWAP tunnel toward the client. As a result, the internal DHCP server cannot be used whenDHCP proxy is disabled.Step 4 Check the Enable DHCP option 82 checkbox to ensure additional security when DHCP is used to allocate networkaddresses, check the Enable DHCP option 82 checkbox.Step 5 Click Apply to save the configuration.Configuring DHCP Proxy (CLI)Step 1 Enable or disable DHCP proxy by entering this command:config dhcp proxy {enable |disable}Step 2 View the DHCP proxy configuration by entering this command:   Cisco Wireless LAN Controller Configuration Guide, Release 7.490 OL-28744-01  Configuring DHCP Proxy (GUI)
show dhcp proxyInformation similar to the following appears:DHCP Proxy Behavior: enabledConfiguring DHCP Proxy (CLI)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-sStep 2 Configure DHCP proxy on the management or dynamic interface of the controller. To do this, enter the followingcommand:•config interface dhcp management proxy-mode enableglobaldisable•config interface dhcp dynamic-interface interface-name proxy-mode enableglobaldisable.To ensure additional security when DHCP is configured, use the config interface dhcpinterface typeoption-82enable command.NoteStep 3 Enter the save config command.Step 4 To view the proxy settings of the controller interface enter the show dhcp proxy command.Configuring a DHCP Timeout (GUI)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, unselectthe 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.Configuring a DHCP Timeout (CLI)Configure a DHCP timeout by entering this command:config dhcp timeout secondsCisco Wireless LAN Controller Configuration Guide, Release 7.4       OL-28744-01 91Configuring a DHCP Timeout (GUI)
   Cisco Wireless LAN Controller Configuration Guide, Release 7.492 OL-28744-01  Configuring a DHCP Timeout (CLI)
CHAPTER 7Configuring SNMP•Configuring SNMP (CLI), page 93•SNMP Community Strings, page 95•Configuring Real Time Statistics (CLI), page 96Configuring SNMP (CLI)To view the controller trap log, choose Monitor and click View All under “Most Recent Traps”on thecontroller GUI.Note•Create an SNMP community name by entering this command:config snmp community create name•Delete an SNMP community name by entering this command:config snmp community delete name•Configure an SNMP community name with read-only privileges by entering this command:config snmp community accessmode ro name•Configure an SNMP community name with read-write privileges by entering this command:config snmp community accessmode rw name•Configure an IP address and subnet mask for an SNMP community by entering this command:config snmp community ipaddr ip-address ip-mask nameThis command behaves like an SNMP access list. It specifies the IP address from which the device acceptsSNMP packets with the associated community. An AND operation is performed between the requestingentity’s IP address and the subnet mask before being compared to the IP address. If the subnet mask is setto 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.NoteCisco Wireless LAN Controller Configuration Guide, Release 7.4        OL-28744-01 93
The controller can use only one IP address range to manage an SNMP community.Note•Enable or disable a community name by entering this command:config snmp community mode {enable |disable}•Configure a destination for a trap by entering this command:config snmp trapreceiver create name ip-address•Delete a trap by entering this command:config snmp trapreceiver delete name•Change the destination for a trap by entering this command:config snmp trapreceiver ipaddr old-ip-address name new-ip-address•Enable or disable the traps by entering this command:config snmp trapreceiver mode {enable |disable}•Configure the name of the SNMP contact by entering this command:config snmp syscontact syscontact-nameEnter up to 31 alphanumeric characters for the contact name.•Configure the SNMP system location by entering this command:config snmp syslocation syslocation-nameEnter up to 31 alphanumeric characters for the location.•Verify that the SNMP traps and communities are correctly configured by entering these commands:show snmpcommunityshow snmptrap•See the enabled and disabled trap flags by entering this command:show trapflagsIf necessary, use the config trapflags command to enable or disable trap flags.•Configure when the warning message should be displayed after the number of clients or RFID tagsassociated with the controller hover around the threshold level by entering this command:config trapflags {client |rfid} max-warning-threshold {threshold-between-80-to-100 |enable |disable}The warning message is displayed at an interval of 600 seconds (10 minutes).•Configure the SNMP engine ID by entering this command:config snmp engineID engine-id-stringThe engine ID string can be a maximum of 24 characters.Note•View the engine ID by entering this command:show snmpengineID•Configure the SNMP version by entering this command:config snmp version {v1 |v2c |v3} {enable |disable}   Cisco Wireless LAN Controller Configuration Guide, Release 7.494 OL-28744-01  Configuring SNMP (CLI)
SNMP Community StringsThe controller has commonly known default values of "public" and "private" for the read-only and read-writeSNMP community strings. Using these standard values presents a security risk. If you use the default communitynames, and since these are known, the community names could be used to communicate to the controllerusing SNMP. Therefore, we strongly advise that you change these values.Changing the SNMP Community String Default Values (GUI)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 forthe 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 IP address from which this device accepts SNMP packets with the associatedcommunity 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.Changing the SNMP Community String Default Values (CLI)Step 1 See the current list of SNMP communities for this controller by entering this command:show snmp communityStep 2 If "public" or "private" appears in the SNMP Community Name column, enter this command to delete this community:config snmp community delete nameThe name parameter is the community name (in this case, “public”or “private”).Step 3 Create a new community by entering this command:config snmp community create nameEnter up to 16 alphanumeric characters for the name parameter. Do not enter “public”or “private.”Step 4 Enter the IP address from which this device accepts SNMP packets with the associated community by entering thiscommand:config snmp community ipaddr ip_address ip_mask nameCisco Wireless LAN Controller Configuration Guide, Release 7.4       OL-28744-01 95SNMP Community Strings
Step 5 Specify the access level for this community by entering this command, where ro is read-only mode and rw is read/writemode:config snmp community accessmode {ro |rw}nameStep 6 Enable or disable this SNMP community by entering this command:config snmp community mode {enable |disable}nameStep 7 Save your changes by entering this command:save configStep 8 Repeat this procedure if you still need to change the default values for a “public”or “private”community string.Configuring Real Time Statistics (CLI)SNMP traps are defined for CPU and memory utilization of AP and controller. The SNMP trap is sent outwhen the threshold is crossed. The sampling period and statistics update interval can be configured usingSNMP and CLI.•Configure the sampling interval by entering this command:config service statistics sampling-interval seconds•Configure the statistics interval by entering this command:config service statistics statistics-interval seconds•See sampling and service interval statistics by entering this command:show service statistics intervalSNMP Trap EnhancementsThis feature provides soaking of SNMP traps and resending of traps after a threshold that you can configurecalled the hold time. The hold time helps in suppressing false traps being generated. The traps that are supportedare for CPU and memory utilization of AP and controller. The retransmission of the trap occurs until the trapis cleared.•Configure the hold time after which the SNMP traps are to be resent by entering this command:config service alarm hold-time seconds•Configure the retransmission interval of the trap by entering this command:config service alarm trap retransmit-interval seconds•Configure debugging of the traps by entering this command:debug service alarm {enable |disable}   Cisco Wireless LAN Controller Configuration Guide, Release 7.496 OL-28744-01  Configuring Real Time Statistics (CLI)
CHAPTER 8Configuring Aggressive Load Balancing•Information About Configuring Aggressive Load Balancing, page 97•Configuring Aggressive Load Balancing (GUI), page 98•Configuring Aggressive Load Balancing (CLI), page 98Information About Configuring Aggressive Load BalancingEnabling aggressive load balancing on the controller allows lightweight access points to load balance wirelessclients across access points. You can enable aggressive load balancing using the controller.Clients are load balanced between access points on the same controller. Load balancing does not occurbetween access points on different controllers.NoteWhen a wireless client attempts to associate to a lightweight access point, association response packets aresent to the client with an 802.11 response packet including status code 17. The code 17 indicates that the APis busy. The AP responds with an association response bearing 'success' if the AP threshold is not met, andwith code 17 (AP busy) if the AP utilization threshold is reached or exceeded and another less busy AP heardthe client request.For example, if the number of clients on AP1 is more than the number of clients on AP2 plus the load-balancingwindow, then AP1 is considered to be busier than AP2. When a client attempts to associate to AP1, it receivesan 802.11 response packet with status code 17, indicating that the access point is busy, and the client attemptsto associate to a different access point.You can configure the controller to deny client associations up to 10 times (if a client attempted to associate11 times, it would be allowed to associate on the 11th try). You can also enable or disable load balancing ona particular WLAN, which is useful if you want to disable load balancing for a select group of clients (suchas time-sensitive voice clients).Passive scanning clients will be able to associate to an AP irrespective of whether load balancing is enabledor not.Cisco Wireless LAN Controller Configuration Guide, Release 7.4        OL-28744-01 97
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.NoteYou can configure the controller to analyze the WAN interface utilization of neighboring APs and then loadbalance 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 thresholdvalue of 50 triggers the load balancing upon detecting utilization of 50% or more on an AP-WAN interface.Configuring Aggressive Load Balancing (GUI)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 acceptmore client associations:load-balancing window + client associations on AP with the lightest load = load-balancing thresholdIn 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 ofclients on the access point with the lightest load forms the threshold. Access points with more client associations thanthis 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 4 Click Apply.Step 5 Click Save Configuration.Step 6 To enable or disable aggressive load balancing on specific WLANs, do the following:a) Choose WLANs >WLAN ID. The WLANs > Edit page appears.b) In the Advanced tab, select or unselect the Client Load Balancing check box.c) Click Apply.d) Click Save Configuration.Configuring Aggressive Load Balancing (CLI)Step 1 Set the client window for aggressive load balancing by entering this command:config load-balancing window client_countYou 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:   Cisco Wireless LAN Controller Configuration Guide, Release 7.498 OL-28744-01  Configuring Aggressive Load Balancing (GUI)
config load-balancing denial denial_countYou can enter a value between 1 and 10 for the denial_count parameter.Step 3 Save your changes by entering this command:save configStep 4 Enable or disable aggressive load balancing on specific WLANs by entering this command:config wlan load-balance allow {enable |disable}wlan_IDYou can enter a value between 1 and 512 for wlan_ID parameter.Step 5 Verify your settings by entering this command:show load-balancingStep 6 Save your changes by entering this command:save configStep 7 Configure the load balance mode on a WLAN by entering this command:config wlan load-balance mode {client-count |uplink-usage}wlan-idThis feature requires the AP to upload its uplink usage statistics to the controller periodically. Check these statistics byentering this command:show ap stats system cisco-APCisco Wireless LAN Controller Configuration Guide, Release 7.4       OL-28744-01 99Configuring Aggressive Load Balancing (CLI)
   Cisco Wireless LAN Controller Configuration Guide, Release 7.4100 OL-28744-01  Configuring Aggressive Load Balancing (CLI)
CHAPTER 9Configuring Fast SSID Changing•Information About Configuring Fast SSID Changing, page 101•Configuring Fast SSID Changing (GUI), page 101•Configuring Fast SSID Changing (CLI), page 101Information About Configuring Fast SSID ChangingWhen fast SSID changing is enabled, the controller allows clients to move faster between SSIDs. When fastSSID is enabled, the client entry is not cleared and the delay is not enforced.When fast SSID changing is disabled, the controller enforces a delay before clients are allowed to move to anew SSID. When fast SSID is disabled and the client sends a new association for a different SSID, the cliententry in the controller connection table is cleared before the client is added to the new SSID.Configuring Fast SSID Changing (GUI)Step 1 Choose Controller to open the General page.Step 2 From the Fast SSID Change drop-down list, choose Enabled to enable this feature or Disabled to disable it. The defaultvalue is disabled.Step 3 Click Apply to commit your changes.Step 4 Click Save Configuration to save your changes.Configuring Fast SSID Changing (CLI)Step 1 Enable or disable fast SSID changing by entering this command:Cisco Wireless LAN Controller Configuration Guide, Release 7.4        OL-28744-01 101
config network fast-ssid-change {enable |disable}Step 2 Save your changes by entering this command:save config   Cisco Wireless LAN Controller Configuration Guide, Release 7.4102 OL-28744-01  Configuring Fast SSID Changing (CLI)
CHAPTER 10Configuring 802.3 Bridging•Configuring 802.3 Bridging, page 103•Enabling 802.3X Flow Control, page 104Configuring 802.3 BridgingInformation About Configuring 802.3 BridgingThe controller supports 802.3 frames and the applications that use them, such as those typically used for cashregisters and cash register servers. However, to make these applications work with the controller, the 802.3frames must be bridged on the controller.You can also configure 802.3 bridging using the Cisco Prime Network Control System. See the Cisco PrimeNetwork Control System Configuration Guide for instructions.Restrictions on 802.3 Bridging•Support for raw 802.3 frames allows the controller to bridge non-IP frames for applications not runningover IP.The raw 802.3 frame contains destination MAC address, source MAC address, total packet length, andpayload.•By default, Cisco 5500 Series Controllers bridge all non-IPv4 packets (such as AppleTalk, IPv6, and soon). You can also use ACLs to block the bridging of these protocols.Cisco Wireless LAN Controller Configuration Guide, Release 7.4        OL-28744-01 103
Configuring 802.3 BridgingConfiguring 802.3 Bridging (GUI)Step 1 Choose Controller >General to open the General page.Step 2 From the 802.3 Bridging drop-down list, choose Enabled to enable 802.3 bridging on your controller or Disabled todisable this feature. The default value is Disabled.Step 3 Click Apply to commit your changes.Step 4 Click Save Configuration to save your changes.Configuring 802.3 Bridging (CLI)Step 1 See the current status of 802.3 bridging for all WLANs by entering this command:show networkStep 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.Step 3 Save your changes by entering this command:save configEnabling 802.3X Flow Control802.3X Flow Control is disabled by default. To enable it, enter the config switchconfig flowcontrol enablecommand.   Cisco Wireless LAN Controller Configuration Guide, Release 7.4104 OL-28744-01  Enabling 802.3X Flow Control
CHAPTER 11Configuring Multicast•Configuring Multicast Mode, page 105•Configuring Multicast Domain Name System, page 111Configuring Multicast ModeInformation About Multicast ModeIf your network supports packet multicasting, you can configure the multicast method that the controller uses.The controller performs multicasting in two modes:•Unicast mode—In this mode, the controller unicasts every multicast packet to every access point associatedto the controller. This mode is inefficient but might be required on networks that do not supportmulticasting.•Multicast mode—In this mode, the controller sends multicast packets to a CAPWAP multicast group.This method reduces overhead on the controller processor and shifts the work of packet replication toyour network, which is much more efficient than the unicast method.When you enable multicast mode and the controller receives a multicast packet from the wired LAN, thecontroller encapsulates the packet using CAPWAP and forwards the packet to the CAPWAP multicast groupaddress. The controller always uses the management interface for sending multicast packets. Access pointsin the multicast group receive the packet and forward it to all the BSSIDs mapped to the interface on whichclients receive multicast traffic. From the access point perspective, the multicast appears to be a broadcast toall SSIDs.The controller supports Multicast Listener Discovery (MLD) v1 snooping for IPv6 multicast. This featurekeeps track of and delivers IPv6 multicast flows to the clients that request them. To support IPv6 multicast,you must enable Global Multicast Mode.Cisco Wireless LAN Controller Configuration Guide, Release 7.4        OL-28744-01 105
When you disable the Global Multicast Mode, the controller still forwards the IPv6 ICMP multicastmessages, such as router announcements and DHCPv6 solicits, as these are required for IPv6 to work. Asa result, enabling the Global Multicast Mode on the controller does not impact the ICMPv6 and theDHCPv6 messages. These messages will always be forwarded irrespective of whether or not the GlobalMulticast Mode is enabled.NoteIn controller software 4.2 or later releases, Internet Group Management Protocol (IGMP) snooping is introducedto better direct multicast packets. When this feature is enabled, the controller gathers IGMP reports from theclients, processes them, creates unique multicast group IDs (MGIDs) from the IGMP reports after selectingthe 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 thereports from the clients. The controller then updates the access point MGID table on the access point with theclient MAC address. When the controller receives multicast traffic for a particular multicast group, it forwardsit to all the access points, but only those access points that have active clients listening or subscribed to thatmulticast group send multicast traffic on that particular WLAN. IP packets are forwarded with an MGID thatis unique for an ingress VLAN and the destination multicast group. Layer 2 multicast packets are forwardedwith 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 interfacecreated is assigned one Layer 2 MGID. For example, the management interface has an MGID of 0, andthe first dynamic interface created is assigned an MGID of 8, which increments as each dynamic interfaceis created.•The IGMP packets from clients are forwarded to the router. As a result, the router IGMP table is updatedwith the IP address of the clients as the last reporter.When IGMP snooping is enabled, the following is true:•The controller always uses Layer 3 MGID for all Layer 3 multicast traffic sent to the access point. Forall Layer 2 multicast traffic, it continues to use Layer 2 MGID.•IGMP report packets from wireless clients are consumed or absorbed by the controller, which generatesa query for the clients. After the router sends the IGMP query, the controller sends the IGMP reportswith its interface IP address as the listener IP address for the multicast group. As a result, the routerIGMP table is updated with the controller IP address as the multicast listener.•When the client that is listening to the multicast groups roams from one controller to another, the firstcontroller transmits all the multicast group information for the listening client to the second controller.As a result, the second controller can immediately create the multicast group information for the client.The second controller sends the IGMP reports to the network for all multicast groups to which the clientwas listening. This process aids in the seamless transfer of multicast data to the client.•If the listening client roams to a controller in a different subnet, the multicast packets are tunneled tothe anchor controller of the client to avoid the reverse path filtering (RPF) check. The anchor thenforwards the multicast packets to the infrastructure switch.The MGIDs are controller specific. The same multicast group packets coming from thesame VLAN in two different controllers may be mapped to two different MGIDs.Note   Cisco Wireless LAN Controller Configuration Guide, Release 7.4106 OL-28744-01  Configuring Multicast Mode
If Layer 2 multicast is enabled, a single MGID is assigned to all the multicast addressescoming from an interface.NoteRestrictions for Configuring Multicast Mode•The Cisco Unified Wireless Network solution uses some IP address ranges for specific purposes, andyou should keep these ranges in mind when configuring a multicast group:◦224.0.0.0 through 224.0.0.255—Reserved link local addresses◦224.0.1.0 through 238.255.255.255—Globally scoped addresses◦239.0.0.0 through 239.255.x.y /16—Limited scope addresses•When you enable multicast mode on the controller, you also must configure a CAPWAP multicast groupaddress. 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 multicastgroup address.•The CAPWAP multicast group configured on the controllers should be different for different controllers.•Access points running recent Cisco IOS versions transmit multicast frames at the highest configuredbasic rate and management frames at the lowest basic mandatory rates, can cause reliability problems.Access points running LWAPP or autonomous Cisco IOS should transmit multicast and managementframes at the lowest configured basic rate. Such behavior is necessary to provide good coverage at thecell's edge, especially for unacknowledged multicast transmissions where multicast wireless transmissionsmight fail to be received.Because multicast frames are not retransmitted at the MAC layer, clients at the edge of the cell mightfail to receive them successfully. If reliable reception is a goal, multicast frames should be transmittedat a low data rate. If support for high data rate multicast frames is required, it might be useful to shrinkthe 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 greatmulticast bandwidth, then configure a single basic rate, that is low enough to reach the edges ofthe 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 coverageof 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, thecontroller drops multicast packets sent to UDP control and data ports 5246 and 5247, respectively.Cisco Wireless LAN Controller Configuration Guide, Release 7.4       OL-28744-01 107Configuring Multicast Mode
Therefore, you may want to consider not using these port numbers with the multicast applications onyour network.•We recommend that any multicast applications on your network not use the multicast address configuredas the CAPWAP multicast group address on the controller.•For multicast to work on 2500 series controller, you have to configure the multicast IP address.•Multicast mode is not supported on Cisco Flex 7500 Series Controllers.Enabling Multicast Mode (GUI)Step 1 Choose Controller >Multicast to open the Multicast page.Step 2 Select the Enable Global Multicast Mode check box to configure sending multicast packets. The default value isdisabled.FlexConnect supports unicast modeonly.NoteStep 3 If you want to enable IGMP snooping, select the Enable IGMP Snooping check box. If you want to disable IGMPsnooping, leave the check box unselected. The default value is disabled.Step 4 To set the IGMP timeout, enter a value between 30 and 7200 seconds in the IGMP Timeout text box. The controllersends three queries in one timeout value at an interval of timeout/ 3 to see if any clients exist for a particular multicastgroup. If the controller does not receive a response through an IGMP report from the client, the controller times out theclient entry from the MGID table. When no clients are left for a particular multicast group, the controller waits for theIGMP timeout value to expire and then deletes the MGID entry from the controller. The controller always generates ageneral IGMP query (that is, to destination address 224.0.0.1) and sends it on all WLANs with an MGID value of 1.Step 5 Enter the IGMP Query Interval (seconds).Step 6 Select the Enable MLD Snooping check box to support IPv6 forwarding decisions.To enable MLD Snooping, you must enable Global Multicast Mode of the controller.NoteStep 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 to commit your changes.Step 10 Click Save Configuration to save your changes.Enabling Multicast Mode (CLI)Step 1 Enable or disable multicasting on the controller by entering this command:config network multicast global {enable |disable}The default value is disabled.The config network broadcast {enable |disable} command allows you to enable or disable broadcastingwithout enabling or disabling multicasting as well. This command uses the multicast mode currently on thecontroller to operate.Note   Cisco Wireless LAN Controller Configuration Guide, Release 7.4108 OL-28744-01  Configuring Multicast Mode
Step 2 Perform either of the following:a) Configure the controller to use the unicast method to send multicast packets by entering this command:config network multicast mode unicastb) Configure the controller to use the multicast method to send multicast packets to a CAPWAP multicast group byentering this command:config network multicast mode multicast multicast_group_ip_addressStep 3 Enable or disable IGMP snooping by entering this command:config network multicast igmp snooping {enable |disable}The default value is disabled.Step 4 Set the IGMP timeout value by entering this command:config network multicast igmp timeout timeoutYou can enter a timeout value between 30 and 7200 seconds. The controller sends three queries in one timeout value atan interval of timeout/3 to see if any clients exist for a particular multicast group. If the controller does not receive aresponse through an IGMP report from the client, the controller times out the client entry from the MGID table. Whenno clients are left for a particular multicast group, the controller waits for the IGMP timeout value to expire and thendeletes the MGID entry from the controller. The controller always generates a general IGMP query (that is, to destinationaddress 224.0.0.1) and sends it on all WLANs with an MGID value of 1.Step 5 Enable or disable MLD snooping by entering this command:config network multicast mld snooping {enable |disable}The default value is disabled.To enable MLD snooping, you must enable global multicast mode of the controller.NoteStep 6 Set the MLD timeout value by entering this command:config network multicast mld timeout timeoutEnter the MLD Query Interval (seconds). The valid range is between 15 and 2400 seconds.Step 7 Save your changes by entering this command:save configViewing Multicast Groups (GUI)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 thatparticular MGID.Cisco Wireless LAN Controller Configuration Guide, Release 7.4       OL-28744-01 109Configuring Multicast Mode
Viewing Multicast Groups (CLI)Before You Begin•See all the multicast groups and their corresponding MGIDs by entering this command:show network multicast mgid summaryInformation similar to the following appears:Layer2 MGID Mapping:-------------------InterfaceName vlanId MGID-------------------------------- ------ ----management 0 0test 0 9wired 20 8Layer3 MGID Mapping:-------------------Number of Layer3 MGIDs........................... 1Group address Vlan MGID--------------- ---- ----239.255.255.250 0 550•See all the clients joined to the multicast group in a specific MGID by entering this command:show network multicast mgid detail mgid_valuewhere the mgid_value parameter is a number between 550 and 4095.Information similar to the following appears:Mgid........................................ 550Multicast Group Address..................... 239.255.255.250Vlan........................................ 0Rx Packet Count............................. 807399588No of clients............................... 1Client List.................................Client MAC Expire Time (mm:ss)00:13:02:23:82:ad 0:20Viewing an Access Point’s Multicast Client Table (CLI)To help troubleshoot roaming events, you can view an access point’s multicast client table from the controllerby performing a remote debug of the access point.Step 1 Initiate a remote debug of the access point by entering this command:debug ap enable Cisco_APStep 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_APStep 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   Cisco Wireless LAN Controller Configuration Guide, Release 7.4110 OL-28744-01  Configuring Multicast Mode
Configuring Multicast Domain Name SystemInformation About Multicast Domain Name SystemMulticast Domain Name System (mDNS) service discovery provides a way to announce and discover theservices on the local network. The mDNS service discovery enables wireless clients to access Apple servicessuch as Apple Printer and Apple TV advertised in a different Layer 3 network. mDNS performs DNS queriesover IP multicast. mDNS supports zero-configuration IP networking. As a standard, mDNS uses multicast IPaddress 224.0.0.251 as the destination address and 5353 as the UDP destination port.Restrictions for Configuring Multicast DNS•mDNS over IPv6 is not supported.•mDNS is not supported on access points in FlexConnect mode in a locally switched WLAN and meshaccess points.•mDNS is not supported on remote LANs.•mDNS is not supported on Cisco AP1240 and Cisco AP1130.•Third-party mDNS servers or applications are not supported on the Cisco WLC using the mDNS feature.Devices that are advertised by the third-party servers or applications are not populated on the mDNSservice or device table correctly on the Cisco WLC.•Video is not supported on Apple iOS 6 with WMM in enabled state.Configuring Multicast DNS (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 aservice.d) Choose a service from the Select Service drop-down list.To add a new mDNS-supported service to the list, choose Other. Specify the service name and the servicestring. The controller snoops and learns about the mDNS service advertisements only if the service is availablein the Master Services Database. The controller can snoop and learn a maximum of 64 services.Notee) 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.Cisco Wireless LAN Controller Configuration Guide, Release 7.4       OL-28744-01 111Configuring Multicast Domain Name System
h) To view the details of an mDNS service, hover your cursor over the blue drop-down arrow of a service, and chooseDetails.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 defaultprofile.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, choosea service to be associated with the profile, and click Apply.You can add multiple services to a profile.Step 3 Click Save Configuration.What to Do NextAfter creating a new profile, you must map the profile to an interface group, an interface, or a WLAN. Clientsreceive service advertisements only for the services associated with the profile. The highest priority is givento 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:1Choose Controller >Interface Groups.2Click the corresponding interface group name.The Interface Groups > Edit page is displayed.3From the mDNS Profile drop-down list, choose a profile.•Map an mDNS profile to an interface by following these steps:1Choose Controller >Interfaces.2Click the corresponding interface name.The Interfaces > Edit page is displayed.3From the mDNS Profile drop-down list, choose a profile.•Map an mDNS profile to a WLAN by following these steps:1Choose WLANs. click the WLAN ID to open the WLANs > Edit page.2Click the corresponding WLAN ID.The WLANs > Edit page is displayed.3Click the Advanced tab.4Select the mDNS Snooping check box.5From the mDNS Profile drop-down list, choose a profile.   Cisco Wireless LAN Controller Configuration Guide, Release 7.4112 OL-28744-01  Configuring Multicast Domain Name System
Configuring Multicast DNS (CLI)•Configure mDNS snooping by entering this command:config mdns snooping {enable |disable}•Configure an mDNS service by entering this command:config mdns service {{create service-name service-string query {enable |disable}} | deleteservice-name}•Configure a query for an mDNS service by entering this command:config mdns service query {enable |disable}service-name•Configure a query interval for mDNS services by entering this command:config mdns query interval value-in-minutes•Configure an mDNS profile by entering this command:config mdns profile {create |delete}profile-nameIf 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•Configure mDNS services to a profile by entering this command:config mdns profile service {add |delete}profile-name service-name•Map an mDNS profile to an interface group by entering this command:config interface group mdns-profile {interface-group-name |all} {mdns-profile-name |none}If the mDNS profile name is none, no profiles are attached to the interface group. Anyexisting profile that is attached is removed.Note•View information about an mDNS profile that is associated with an interface group by entering thiscommand: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:Cisco Wireless LAN Controller Configuration Guide, Release 7.4       OL-28744-01 113Configuring Multicast Domain Name System
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:clear mdns service-database {all |service-name}•View events related to mDNS by entering this command:debug mdns message {enable |disable}•View mDNS details of the events by entering this command:debug mdns detail {enable |disable}•View errors related to mDNS processing by entering this command:debug mdns error {enable |disable}•Configure debugging of all mDNS details by entering this command:debug mdns all {enable |disable}   Cisco Wireless LAN Controller Configuration Guide, Release 7.4114 OL-28744-01  Configuring Multicast Domain Name System
CHAPTER 12Configuring Client Roaming•Information About Client Roaming, page 115•Guidelines and Limitations, page 117•Configuring CCX Client Roaming Parameters (GUI), page 117•Configuring CCX Client Roaming Parameters (CLI), page 118•Obtaining CCX Client Roaming Information (CLI), page 118•Debugging CCX Client Roaming Issues (CLI), page 119Information About Client RoamingThe Cisco UWN solution supports seamless client roaming across lightweight access points managed by thesame controller, between controllers in the same mobility group on the same subnet, and across controllersin the same mobility group on different subnets. Also, in controller software release 4.1 or later releases, clientroaming with multicast packets is supported.You can adjust the default RF settings (RSSI, hysteresis, scan threshold, and transition time) to fine-tune theoperation of client roaming using the controller GUI or CLI.Inter-Controller RoamingMultiple-controller deployments support client roaming across access points managed by controllers in thesame mobility group and on the same subnet. This roaming is also transparent to the client because the sessionis sustained and a tunnel between controllers allows the client to continue using the same DHCP- orclient-assigned IP address as long as the session remains active. The tunnel is torn down, and the client mustreauthenticate when the client sends a DHCP Discover with a 0.0.0.0 client IP address or a 169.254.*.* clientauto-IP address or when the operator-set session timeout is exceeded.Intra-Controller RoamingEach 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 sameDHCP-assigned or client-assigned IP address. The controller provides DHCP functionality with a relayCisco Wireless LAN Controller Configuration Guide, Release 7.4        OL-28744-01 115
function. Same-controller roaming is supported in single-controller deployments and in multiple-controllerdeployments.Inter-Subnet RoamingMultiple-controller deployments support client roaming across access points managed by controllers in thesame mobility group on different subnets. This roaming is transparent to the client because the session issustained and a tunnel between the controllers allows the client to continue using the same DHCP-assignedor client-assigned IP address as long as the session remains active. The tunnel is torn down, and the clientmust 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.Voice-over-IP Telephone Roaming802.11 voice-over-IP (VoIP) telephones actively seek out associations with the strongest RF signal to ensurethe best quality of service (QoS) and the maximum throughput. The minimum VoIP telephone requirementof 20-millisecond or shorter latency time for the roaming handover is easily met by the Cisco Unified WirelessNetwork (Cisco UWN) solution, which has an average handover latency of 5 or fewer milliseconds whenopen authentication is used. This short latency period is controlled by controllers rather than allowingindependent access points to negotiate roaming handovers.The Cisco UWN solution supports 802.11 VoIP telephone roaming across lightweight access points managedby controllers on different subnets, as long as the controllers are in the same mobility group. This roaming istransparent to the VoIP telephone because the session is sustained and a tunnel between controllers allowsthe VoIP telephone to continue using the same DHCP-assigned IP address as long as the session remainsactive. The tunnel is torn down, and the VoIP client must reauthenticate when the VoIP telephone sends aDHCP Discover with a 0.0.0.0 VoIP telephone IP address or a 169.254.*.* VoIP telephone auto-IP addressor when the operator-set user timeout is exceeded.CCX Layer 2 Client RoamingThe controller supports five CCX Layer 2 client roaming enhancements:•Access point assisted roaming—This feature helps clients save scanning time. When a CCXv2 clientassociates to an access point, it sends an information packet to the new access point listing thecharacteristics of its previous access point. Roaming time decreases when the client recognizes and usesan access point list built by compiling all previous access points to which each client was associated andsent (unicast) to the client immediately after association. The access point list contains the channels,BSSIDs of neighbor access points that support the client’s current SSID(s), and time elapsed sincedisassociation.•Enhanced neighbor list—This feature focuses on improving a CCXv4 client’s roam experience andnetwork edge performance, especially when servicing voice applications. The access point provides itsassociated client information about its neighbors using a neighbor-list update unicast message.•Enhanced neighbor list request (E2E)—The End-2-End specification is a Cisco and Intel joint programthat defines new protocols and interfaces to improve the overall voice and roaming experience. It appliesonly to Intel clients in a CCX environment. Specifically, it enables Intel clients to request a neighborlist at will. When this occurs, the access point forwards the request to the controller. The controllerreceives the request and replies with the current CCX roaming sublist of neighbors for the access pointto which the client is associated.   Cisco Wireless LAN Controller Configuration Guide, Release 7.4116 OL-28744-01  Information About Client Roaming
To see whether a particular client supports E2E, choose Wireless >Clients on thecontroller GUI, click the Detail link for the desired client, and look at the E2E Versiontext box in the Client Properties area.Note•Roam reason report—This feature enables CCXv4 clients to report the reason why they roamed to anew 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 clientin situations when the controller can better service the client on an access point different from the oneto which it is associated. In this case, the controller sends the client a list of the best access points thatit can join. The client can either honor or ignore the directed roam request. Non-CCX clients and clientsrunning CCXv3 or below must not take any action. No configuration is required for this feature.Guidelines and Limitations•Controller software release 4.2 or later releases support CCX versions 1 through 5. CCX support isenabled automatically for every WLAN on the controller and cannot be disabled. The controller storesthe CCX version of the client in its client database and uses it to generate and respond to CCX framesappropriately. Clients must support CCXv4 or v5 (or CCXv2 for access point assisted roaming) in orderto utilize these roaming enhancements.The roaming enhancements mentioned above are enabled automatically, with the appropriate CCXsupport.•FlexConnect access points in standalone mode do not support CCX Layer 2 roaming.•Client roaming between 600 Series Access points is not supported.Configuring CCX Client Roaming Parameters (GUI)Step 1 Choose Wireless >802.11a/n 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 listand 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 forthe client to associate to an access point. If the client’s average received signal power dips below this threshold, reliablecommunication is usually impossible. Therefore, clients must already have found and roamed to another access pointwith 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 pointmust be in order for the client to roam to it. This parameter is intended to reduce the amount of roaming between accesspoints if the client is physically located on or near the border between two access points.The range is 3 to 20 dB.Cisco Wireless LAN Controller Configuration Guide, Release 7.4       OL-28744-01 117Guidelines and Limitations
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 accesspoint. When the RSSI drops below the specified value, the client must be able to roam to a better access point within thespecified transition time. This parameter also provides a power-save method to minimize the time that the client spendsin active or passive scanning. For example, the client can scan slowly when the RSSI is above the threshold and scanmore 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 accesspoint to roam to and to complete the roam, whenever the RSSI from the client’s associated access point is below the scanthreshold.The Scan Threshold and Transition Time parameters guarantee a minimum level of client roaming performance. Togetherwith the highest expected client speed and roaming hysteresis, these parameters make it possible to design a wirelessLAN 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 7 Click Apply.Step 8 Click Save Configuration.Step 9 Repeat this procedure if you want to configure client roaming for another radio band.Configuring CCX Client Roaming Parameters (CLI)Configure CCX Layer 2 client roaming parameters by entering this command:config {802.11a |802.11b}l2roam rf-params {default |custom min_rssi roam_hyst scan_thresh trans_time}Obtaining CCX Client Roaming Information (CLI)Step 1 View the current RF parameters configured for client roaming for the 802.11a or 802.11b/g network by entering thiscommand:show {802.11a |802.11b}l2roam rf-paramStep 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_macThis command provides the following information:•The number of roam reason reports received•The number of neighbor list requests received•The number of neighbor list reports sent   Cisco Wireless LAN Controller Configuration Guide, Release 7.4118 OL-28744-01  Configuring CCX Client Roaming Parameters (CLI)
•The number of broadcast neighbor updates sentStep 3 View the roaming history for a particular client by entering this command:show client roam-history client_macThis 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 roamDebugging CCX Client Roaming Issues (CLI)If you experience any problems with CCX Layer 2 client roaming, enter this command:debug l2roam [detail |error |packet |all] {enable |disable}Cisco Wireless LAN Controller Configuration Guide, Release 7.4       OL-28744-01 119Debugging CCX Client Roaming Issues (CLI)
   Cisco Wireless LAN Controller Configuration Guide, Release 7.4120 OL-28744-01  Debugging CCX Client Roaming Issues (CLI)
CHAPTER 13Configuring IP-MAC Address Binding•Information About Configuring IP-MAC Address Binding, page 121•Configuring IP-MAC Address Binding (CLI), page 121Information About Configuring IP-MAC Address BindingIn the controller software Release 5.2 or later releases, the controller enforces strict IP address-to-MAC addressbinding in client packets. The controller checks the IP address and MAC address in a packet, compares themto the addresses that are registered with the controller, and forwards the packet only if they both match. Inprevious releases, the controller checks only the MAC address of the client and ignores the IP address.You must disable IP-MAC address binding to use an access point in sniffer mode if the access point isassociated with a 5500 series controller, a 2500 series controller, or a controller network module. To disableIP-MAC address binding, enter the config network ip-mac-binding disable.WLAN must be enabled to use an access point in sniffer mode if the access point is associated with a 5500series controller, a 2500 series controller, or a controller network module. If WLAN is disabled, the accesspoint cannot send packets.If the IP address or MAC address of the packet has been spoofed, the check does not pass, and the controllerdiscards the packet. Spoofed packets can pass through the controller only if both the IP and MAC addressesare spoofed together and changed to that of another valid client on the same controller.NoteConfiguring IP-MAC Address Binding (CLI)Step 1 Enable or disable IP-MAC address binding by entering this command:config network ip-mac-binding {enable |disable}The default value is enabled.You might want to disable this binding check if you have a routed network behind a workgroup bridge (WGB).NoteCisco Wireless LAN Controller Configuration Guide, Release 7.4        OL-28744-01 121
You must disable this binding check in order to use an access point in sniffer mode if the access point is joinedto a Cisco 5500 Series Controller.NoteStep 2 Save your changes by entering this command:save configStep 3 View the status of IP-MAC address binding by entering this command:show network summaryInformation similar to the following appears:RF-Network Name............................. ctrl4404Web Mode.................................... DisableSecure Web Mode............................. EnableSecure Web Mode Cipher-Option High.......... DisableSecure Web Mode Cipher-Option SSLv2......... Disable...IP/MAC Addr Binding Check ............... Enabled...<?Line-Break?><?HardReturn?>   Cisco Wireless LAN Controller Configuration Guide, Release 7.4122 OL-28744-01  Configuring IP-MAC Address Binding (CLI)
CHAPTER 14Configuring Quality of Service•Configuring Quality of Service, page 123•Configuring Quality of Service Roles, page 126Configuring Quality of ServiceInformation About Quality of ServiceQuality of service (QoS) refers to the capability of a network to provide better service to selected networktraffic over various technologies. The primary goal of QoS is to provide priority including dedicated bandwidth,controlled jitter and latency (required by some real-time and interactive traffic), and improved losscharacteristics.The controller supports four QoS levels:•Platinum/Voice—Ensures a high quality of service for voice over wireless.•Gold/Video—Supports high-quality video applications.•Silver/Best Effort—Supports normal bandwidth for clients. This is the default setting.•Bronze/Background—Provides the lowest bandwidth for guest services.VoIP clients should be set to Platinum.NoteYou 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 rolesto specify different bandwidth levels for regular and guest users. Follow the instructions in this section toconfigure QoS profiles and QoS roles. You can also define the maximum and default QoS levels for unicastand 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 definedper SSID and/or specified as a maximum rate limit for all clients. These rate limits can be individuallyconfigured.Cisco Wireless LAN Controller Configuration Guide, Release 7.4        OL-28744-01 123
Configuring Quality of Service ProfilesYou can configure the Platinum, Gold, Silver, and Bronze QoS profiles.Configuring QoS Profiles (GUI)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 or 802.11b/g/n > Network, unselect the 802.11a (or802.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. Avalue of 0 indicates that the value specified in the selected QoS profile will take effect.The burst data rate should be greater than or equal to the average data rate. Otherwise, the QoS policy mayblock traffic to and from the wireless client.Ensure that you configure the average data rate before you configure the burst data rate.Notec) Define the average real-time rate for UDP traffic per user by entering the rate in Kbps in the Average Real-TimeRate text boxes. A value of 0 indicates that the value specified in the selected QoS profile will take effect.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 ratecan be different because they are applied to different upper layer protocols such as TCP and UDP. Thesedifferent values for the rates do not impact the bandwidth.Noted) Define the peak real-time rate for UDP traffic per user by entering the rate in Kbps in the Burst Real-Time Rate textboxes. A value of 0 indicates that the value specified in the selected QoS profile will take effect.The burst real-time rate should be greater than or equal to the average real-time rate. Otherwise, the QoSpolicy may block traffic to and from the wireless client.NoteStep 6 Define the data rates on a per-SSID basis as follows:a) Define the average data rate TCP traffic per SSID 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 SSID by entering the rate in Kbps in the Burst Data Rate text boxes. Avalue of 0 indicates that the value specified in the selected QoS profile will take effect.The burst data rate should be greater than or equal to the average data rate. Otherwise, the QoS policy mayblock traffic in the WLANs.Notec) Define the average real-time rate for UDP traffic per SSID by entering the rate in Kbps in the Average Real-TimeRate text boxes. A value of 0 indicates that the value specified in the selected QoS profile will take effect.d) Define the peak real-time rate for UDP traffic per SSID by entering the rate in Kbps in the Burst Real-Time Ratetext boxes. A value of 0 indicates that the value specified in the selected QoS profile will take effect.The burst real-time rate should be greater than or equal to the average real-time rate. Otherwise, the QoSpolicy may block traffic in the WLANs.Note   Cisco Wireless LAN Controller Configuration Guide, Release 7.4124 OL-28744-01  Configuring Quality of Service
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 bythe 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 bydefault.b) From the Unicast Default Priority drop-down list, choose the QoS priority for unicast data frames transmitted by theAP to non-WMM stations in the WLANc) From the Multicast Default Priority drop-down list, choose the QoS priority for multicast data frames transmitted bythe AP to stations in the WLAN,The default unicast priority cannot be used for non-WMM clients in a mixed WLAN.NoteStep 8 Choose 802.1p from the Protocol Type drop-down list and enter the maximum priority value in the 802.1p Tag text boxto 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 towardthe core network.If a QoS profile has 802.1p tagging configured and if this QoS profile is assigned to a WLAN that uses anuntagged interface on the controller, the client traffic will be blocked.NoteStep 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 or 802.11b/g/n > Network, select the 802.11a (or 802.11b/g)Network Status check box, and click Apply.Configuring QoS Profiles (CLI)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 networkStep 2 Change the profile description by entering this command:config qos description {bronze |silver |gold |platinum }descriptionStep 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}rateFor the rate parameter, you can enter a value between 0 and 512,000 Kbps (inclusive). A value of 0 imposesno bandwidth restriction on the QoS profile.NoteStep 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}rateStep 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}rateCisco Wireless LAN Controller Configuration Guide, Release 7.4       OL-28744-01 125Configuring Quality of Service
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}rateStep 7 Define the maximum and default QoS levels for unicast and multicast traffic when you assign a QoS profile to a WLANby entering this command:config qos priority {bronze |gold |platinum |silver} {maximum priority} {default unicast priority} {default multicastpriority}You choose from the following options for the maximum priority,default unicast priority, and default multicast priorityparameters:•besteffort•background•video•voiceStep 8 Define the maximum value (0–7) for the priority tag associated with packets that fall within the profile, by entering thesecommands:config qos protocol-type {bronze |silver |gold |platinum}dot1pconfig qos dot1p-tag {bronze |silver |gold |platinum}tagThe tagged packets include CAPWAP data packets (between access points and the controller) and packets sent towardthe core network.The 802.1p tagging has impact only on wired packets. Wireless packets are impacted only by the maximumpriority level set for a QoS profile.NoteIf a QoS profile has 802.1p tagging configured and if this QoS profile is assigned to a WLAN that uses anuntagged interface on the controller, the client traffic will be blocked.NoteStep 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 networkConfiguring Quality of Service RolesInformation About Quality of Service RolesAfter you configure a QoS profile and apply it to a WLAN, it limits the bandwidth level of clients associatedto that WLAN. Multiple WLANs can be mapped to the same QoS profile, which can result in bandwidthcontention between regular users (such as employees) and guest users. In order to prevent guest users fromusing the same level of bandwidth as regular users, you can create QoS roles with different (and presumablylower) bandwidth contracts and assign them to guest users.You can configure up to ten QoS roles for guest users.   Cisco Wireless LAN Controller Configuration Guide, Release 7.4126 OL-28744-01  Configuring Quality of Service Roles
If you choose to create an entry on the RADIUS server for a guest user and enable RADIUS authenticationfor the WLAN on which web authentication is performed rather than adding a guest user to the local userdatabase 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”anda return value of “11.”This attribute is sent to the controller when authentication occurs. If a role with thename returned from the RADIUS server is found configured on the controller, the bandwidth associatedto that role is enforced for the guest user after authentication completes successfully.NoteConfiguring QoS RolesConfiguring QoS (GUI)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.If you want to delete a QoS role, hover your cursor over the blue drop-down arrow for that role and chooseRemove.NoteStep 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 QoSuser (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.The values that you configure for the per-user bandwidth contracts affect only the amount of bandwidth goingdownstream (from the access point to the wireless client). They do not affect the bandwidth for upstream traffic(from the client to the access point).NoteThe 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.NoteStep 6 Define the average data rate for TCP traffic on a per-user basis by entering the rate in Kbps in the Average Data Ratetext box. You can enter a value between 0 and 60,000 Kbps (inclusive). A value of 0 imposes no bandwidth restrictionon 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 QoSrole.The burst data rate should be greater than or equal to the average data rate. Otherwise, the QoS policy may blocktraffic to and from the wireless client.Ensure that you configure the average data rate before you configure the burst data rate.NoteStep 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-TimeRate text box. You can enter a value between 0 and 60,000 Kbps (inclusive). A value of 0 imposes no bandwidthrestriction 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-TimeRate text box. You can enter a value between 0 and 60,000 Kbps (inclusive). A value of 0 imposes no bandwidthrestriction on the QoS role.The burst real-time rate should be greater than or equal to the average real-time rate. Otherwise, the QoS policymay block traffic to and from the wireless client.NoteCisco Wireless LAN Controller Configuration Guide, Release 7.4       OL-28744-01 127Configuring Quality of Service Roles
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.Configuring QoS Roles (CLI)Step 1 Create a QoS role for a guest user by entering this command:config netuser guest-role create role_nameIf you want to delete a QoS role, enter the config netuser guest-role delete role_name command.NoteStep 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 ratefor 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 TCPtraffic on a per-user basis.The burst data rate should be greater than or equal to the average data rate. Otherwise, the QoS policy mayblock traffic to and from the wireless client.Note•config netuser guest-role qos data-rate average-realtime-rate role_name rate—Configures the average real-timerate 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 ratefor UDP traffic on a per-user basis.The burst real-time rate should be greater than or equal to the average real-time rate. Otherwise, the QoSpolicy may block traffic to and from the wireless client.NoteFor the role_name parameter in each of these commands, enter a name for the new QoS role. The nameshould uniquely identify the role of the QoS user (such as Contractor, Vendor, and so on). For the rateparameter, you can enter a value between 0 and 60,000 Kbps (inclusive). A value of 0 imposes no bandwidthrestriction on the QoS role.NoteStep 3 Apply a QoS role to a guest user by entering this command:config netuser guest-role apply username role_nameFor example, the role of Contractor could be applied to guest user jsmith.If you do not assign a QoS role to a guest user, the Role text box in the User Details shows the role as “default.”The bandwidth contracts for this user are defined in the QoS profile for the WLAN.NoteIf you want to unassign a QoS role from a guest user, enter the config netuser guest-role apply usernamedefault command. This user now uses the bandwidth contracts defined in the QoS profile for the WLAN.NoteStep 4 Save your changes by entering this command:save configStep 5 See a list of the current QoS roles and their bandwidth parameters by entering this command:   Cisco Wireless LAN Controller Configuration Guide, Release 7.4128 OL-28744-01  Configuring Quality of Service Roles
show netuser guest-rolesInformation similar to the following appears:Role Name........................................ ContractorAverage Data Rate........................... 10Burst Data Rate............................. 10Average Realtime Rate....................... 100Burst Realtime Rate......................... 100Role Name........................................ VendorAverage Data Rate........................... unconfiguredBurst Data Rate............................. unconfiguredAverage Realtime Rate....................... unconfiguredBurst Realtime Rate...................... unconfiguredCisco Wireless LAN Controller Configuration Guide, Release 7.4       OL-28744-01 129Configuring Quality of Service Roles
   Cisco Wireless LAN Controller Configuration Guide, Release 7.4130 OL-28744-01  Configuring Quality of Service Roles
CHAPTER 15Configuring Application Visibility and Control•Information About Application Visibility and Control, page 131•Restrictions for Application Visibility and Control, page 131•Configuring Application Visibility and Control (GUI), page 132•Configuring Application Visibility and Control (CLI), page 133•Configuring NetFlow, page 134Information About Application Visibility and ControlApplication Visibility and Control (AVC) classifies applications using deep packet inspection techniques withthe Network-Based Application Recognition (NBAR) engine, and provides application-level visibility andcontrol into Wi-Fi networks. After the applications are recognized, the AVC feature enables you to eitherdrop or mark the data traffic.Using AVC, we can detect more than 1000 applications. AVC enables you to perform real-time analysis andcreate policies to reduce network congestion, costly network link usage, and infrastructure upgrades.AVC is supported on the following controller platforms: Cisco 2500 Series Wireless LAN Controllers, Cisco5500 Series Wireless LAN Controllers, Cisco Flex 7500 Series Wireless LAN Controllers in central switchingmode, Cisco 8500 Series Wireless LAN Controllers, and Cisco Wireless Services Module 2 (WiSM2).AVC DSCP marks only the DSCP of the original packet in the controller in both directions (upstream anddownstream). It does not affect the outer CAPWAP DCSP. AVC DSCP is applicable only when the applicationis classified. For example, based on the AVC profile configuration, if an application is classified as ftp orhttp, the corresponding DSCP marking is applied irrespective of the WLAN QoS. For downstream, the DSCPvalue of outer CAPWAP header and inner packet’s DSCP are taken from AVC DSCP. WLAN QoS is onlyapplicable for all traffic from WLC to AP through CAPWAP. It does not change the DSCP of the originalpacketRestrictions for Application Visibility and Control•IPv6 packet classification is not supported.•Layer 2 roaming is not supported across controllers.Cisco Wireless LAN Controller Configuration Guide, Release 7.4        OL-28744-01 131
•Multicast traffic is not supported.Configuring Application Visibility and Control (GUI)Step 1 Create and configure an AVC profile by following these steps:a) Choose Wireless >Application Visibility and Control >AVC Profiles.b) Click New.c) Enter the AVC profile name.d) Click Apply.e) On the AVC Profile Name page, click the corresponding AVC profile name.The AVC Profile > Edit page is displayed.f) Click Add New Rule.g) Choose the application group and the application name from the respective drop-down lists.View the list of default AVC applications available by choosing Wireless >Application Visibility and Control >AVC Applications.h) From the Action drop-down list, choose either of the following:•Drop—Drops the upstream and downstream packets that correspond to the chosen application.•Mark—Marks the upstream and downstream packets that correspond to the chosen application with theDifferentiated Services Code Point (DSCP) value that you specify in the DSCP (0 to 63) drop-down list. TheDSCP value helps you provide differentiated services based on the QoS levels.The default action is to give permission to allapplications.Notei) 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 mappedto the following QoS levels:•Platinum (Voice)—Assures a high QoS for Voice over Wireless.•Gold (Video)—Supports high-quality video applications.•Silver (Best Effort)—Supports normal bandwidth for clients.•Bronze (Background)—Provides the lowest bandwidth for guest services.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.   Cisco Wireless LAN Controller Configuration Guide, Release 7.4132 OL-28744-01  Configuring Application Visibility and Control (GUI)
d) Click Apply.e) Click Save Configuration.Configuring Application Visibility and Control (CLI)•Create or delete an AVC profile by entering this command:config avc profile avc-profile-name {create |delete}•Add a rule for an AVC profile by entering this command:config avc profile avc-profile-name rule add application application-name {drop |mark dscp-value}•Remove a rule for an AVC profile by entering this command:config avc profile avc-profile-name rule remove application application-name•Configure an AVC profile to a WLAN by entering this command:config wlan avc wlan-id profile avc-profile-name {enable |disable}•Configure application visibility for a WLAN by entering this command:config wlan avc wlan-id visibility {enable |disable}Application visibility is the subset of an AVC profile. Therefore, visibility isautomatically enabled when you configure an AVC profile on the WLAN.Note•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 this command:show avc applications [application-group]•View various statistical information about AVC by entering this command:show avc statistics•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}Cisco Wireless LAN Controller Configuration Guide, Release 7.4       OL-28744-01 133Configuring Application Visibility and Control (CLI)
Configuring NetFlowInformation About NetFlowNetFlow is a protocol that provides information about network users and applications, peak usage times, andtraffic routing. The NetFlow protocol collects IP traffic information from network devices to monitor traffic.The NetFlow architecture consists of the following components:•Collector—Entity that collects all the IP traffic information from various network elements.•Exporter—Network entity that exports the template with the IP traffic information. The controller actsas an exporter.Configuring NetFlow (GUI)Step 1 Configure the Exporter by following these steps:a) Choose Wireless >Netflow >Exporter.b) Click New.c) Enter the Exporter name, IP address, and the port number.The valid range for the port number is from 1 to 65535.d) Click Apply.e) Click Save Configuration.Step 2 Configure the NetFlow Monitor by following these steps:a) Choose Wireless >Netflow >Monitor.b) Click New and enter the Monitor name.c) On the Monitor List page, click the Monitor name to open the Netflow Monitor > Edit page.d) Choose the Exporter name and the Record name from the respective drop-down lists.e) Click Apply.f) Click Save Configuration.Step 3 Associate a NetFlow Monitor to a WLAN by following these steps:a) Choose WLANs and click the WLAN ID to open the WLANs > Edit page.b) In the QoS tab, choose the NetFlow Monitor from the Netflow Monitor drop-down list.c) Click Apply.d) Click Save Configuration.Configuring NetFlow (CLI)•Create an Exporter by entering this command:config flow create exporter exporter-name ip-addr port-number   Cisco Wireless LAN Controller Configuration Guide, Release 7.4134 OL-28744-01  Configuring NetFlow
•Create a NetFlow Monitor by entering this command:config flow create monitor monitor-name•Associate or dissociate a NetFlow Monitor with an Exporter by entering this command:config flow {add |delete}monitor monitor-name exporter exporter-name•Associate or dissociate a NetFlow Monitor with a Record by entering this command:config flow {add |delete}monitor monitor-name record ipv4_client_app_flow_record•Associate or dissociate a NetFlow Monitor with a WLAN by entering this command:config wlan flow wlan-id monitor monitor-name {enable |disable}•See a summary of NetFlow Monitors by entering this command:show flow monitor summary•See information about the Exporter by entering this command:show flow exporter {summary |statistics}•Configure a debug of NetFlow by entering this command:debug flow {detail |error |info} {enable |disable}Cisco Wireless LAN Controller Configuration Guide, Release 7.4       OL-28744-01 135Configuring NetFlow
   Cisco Wireless LAN Controller Configuration Guide, Release 7.4136 OL-28744-01  Configuring NetFlow
CHAPTER 16Configuring Media and EDCA Parameters•Configuring Voice and Video Parameters, page 137•Configuring SIP-Based CAC, page 149•Configuring Media Parameters, page 151•Configuring Voice Prioritization Using Preferred Call Numbers, page 151•Configuring EDCA Parameters, page 153Configuring Voice and Video ParametersInformation About Configuring Voice and Video ParametersThree parameters on the controller affect voice and/or video quality:•Call admission control•Expedited bandwidth requests•Unscheduled automatic power save deliveryEach of these parameters is supported in Cisco Compatible Extensions (CCX) v4 and v5.Traffic stream metrics (TSM) can be used to monitor and report issues with voice quality.NoteCall Admission ControlCall admission control (CAC) enables an access point to maintain controlled quality of service (QoS) whenthe wireless LAN is experiencing congestion. The Wi-Fi Multimedia (WMM) protocol deployed in CCXv3ensures sufficient QoS as long as the wireless LAN is not congested. However, in order to maintain QoSunder differing network loads, CAC in CCXv4 is required. Two types of CAC are available: bandwidth-basedCAC and load-based CAC.Cisco Wireless LAN Controller Configuration Guide, Release 7.4        OL-28744-01 137
Bandwidth-Based CACBandwidth-based, or static, CAC enables the client to specify how much bandwidth or shared medium timeis required to accept a new call and in turn enables the access point to determine whether it is capable ofaccommodating this particular call. The access point rejects the call if necessary in order to maintain themaximum allowed number of calls with acceptable quality.The QoS setting for a WLAN determines the level of bandwidth-based CAC support. To use bandwidth-basedCAC with voice applications, the WLAN must be configured for Platinum QoS. To use bandwidth-basedCAC with video applications, the WLAN must be configured for Gold QoS. Also, make sure that WMM isenabled for the WLAN. See the Information About Configuring 802.3 Bridging, on page 103 section for QoSand WMM configuration instructions.You must enable admission control (ACM) for CCXv4 clients that have WMM enabled. Otherwise,bandwidth-based CAC does not operate properly.NoteLoad-Based CACLoad-based CAC incorporates a measurement scheme that takes into account the bandwidth consumed by alltraffic 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 fromPHY 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 callsthat the access point can admit. The access point admits a new call only if the channel has enough unusedbandwidth to support that call. By doing so, load-based CAC prevents oversubscription of the channel andmaintains QoS under all conditions of WLAN loading and interference.Load-based CAC is supported only on lightweight access points. If you disable load-based CAC, theaccess points start using bandwidth-based CAC.NoteExpedited Bandwidth RequestsThe expedited bandwidth request feature enables CCXv5 clients to indicate the urgency of a WMM trafficspecifications (TSPEC) request (for example, an e911 call) to the WLAN. When the controller receives thisrequest, it attempts to facilitate the urgency of the call in any way possible without potentially altering thequality of other TSPEC calls that are in progress.You can apply expedited bandwidth requests to both bandwidth-based and load-based CAC. Expeditedbandwidth requests are disabled by default. When this feature is disabled, the controller ignores all expeditedrequests and processes TSPEC requests as normal TSPEC requests.This table lists examples of TSPEC request handling for normal TSPEC requests and expedited bandwidthrequests.   Cisco Wireless LAN Controller Configuration Guide, Release 7.4138 OL-28744-01  Configuring Voice and Video Parameters
Table 4: TSPEC Request Handling ExamplesTSPEC with ExpeditedBandwidth RequestNormalTSPECRequestUsage2Reservedbandwidthfor voicecalls1CAC ModeAdmittedAdmittedLess than 75%75%(defaultsetting)Bandwidth-basedCACAdmittedRejectedBetween 75% and 90%(reserved bandwidth forvoice calls exhausted)RejectedRejectedMore than 90%AdmittedAdmittedLess than 75%Load-based CACAdmittedRejectedBetween 75% and 85%(reserved bandwidth forvoice calls exhausted)RejectedRejectedMore than 85%1For 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.2Bandwidth-based CAC (consumed voice and video bandwidth) or load-based CAC (channel utilization [Pb]).Admission control for TSPEC g711-40ms codec type is supported.NoteWhen video ACM is enabled, the controller rejects a video TSPEC if the non-MSDU size in the TSPECis greater than 149 or the mean data rate is greater than 1 Kbps.NoteU-APSDUnscheduled automatic power save delivery (U-APSD) is a QoS facility defined in IEEE 802.11e that extendsthe battery life of mobile clients. In addition to extending battery life, this feature reduces the latency of trafficflow delivered over the wireless media. Because U-APSD does not require the client to poll each individualpacket buffered at the access point, it allows delivery of multiple downlink packets by sending a single uplinktrigger packet. U-APSD is enabled automatically when WMM is enabled.Traffic Stream MetricsIn a voice-over-wireless LAN (VoWLAN) deployment, traffic stream metrics (TSM) can be used to monitorvoice-related metrics on the client-access point air interface. It reports both packet latency and packet loss.You can isolate poor voice quality issues by studying these reports.Cisco Wireless LAN Controller Configuration Guide, Release 7.4       OL-28744-01 139Configuring Voice and Video Parameters
The metrics consist of a collection of uplink (client side) and downlink (access point side) statistics betweenan access point and a client device that supports CCX v4 or later releases. If the client is not CCX v4 or CCXv5compliant, only downlink statistics are captured. The client and access point measure these metrics. The accesspoint also collects the measurements every 5 seconds, prepares 90-second reports, and then sends the reportsto the controller. The controller organizes the uplink measurements on a client basis and the downlinkmeasurements 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.11aradios). The controller saves the configuration in flash memory so that it persists across reboots. After anaccess point receives the configuration from the controller, it enables TSM on the specified radio band.Access points support TSM entries in both local and FlexConnect modes.NoteThis table shows the upper limit for TSM entries in different controller series.75005500TSM Entries100100MAX AP TSM entries250250MAX Client TSM entries100*250=25000100*250=25000MAX TSM entriesOnce the upper limit is reached, additional TSM entries cannot be stored and sent to Cisco PrimeInfrastructure. If client TSM entries are full and AP TSM entries are available, then only the AP entriesare stored, and vice versa. This leads to partial output. TSM cleanup occurs every one hour. Entries areremoved only for those APs and clients that are not in the system.NoteConfiguring Voice ParametersConfiguring Voice Parameters (GUI)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 or 802.11b/g/n, unselect the 802.11a (or 802.11b/g) Network Statuscheck box, and click Apply to disable the radio network.Step 4 Choose Wireless >802.11a/n or 802.11b/g/n >Media. The 802.11a (or 802.11b) > Media page appears. The Voicetab is displayed by default.Step 5 Select the Admission Control (ACM) check box to enable bandwidth-based CAC for this radio band. The default valueis disabled.Step 6 Select the Admission Control (ACM) you want to use by choosing from the following choices:   Cisco Wireless LAN Controller Configuration Guide, Release 7.4140 OL-28744-01  Configuring Voice and Video Parameters
Load-based—To enable channel-based CAC. This is the default option.••Static—To enable radio-based CAC.Step 7 In the Max RF Bandwidth text box, enter the percentage of the maximum bandwidth allocated to clients for voiceapplications on this radio band. Once the client reaches the value specified, the access point rejects new calls on thisradio 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 reservedfor roaming voice clients. The controller reserves this bandwidth from the maximum allocated bandwidth for roamingvoice 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 isG.711. The options are as follows:•User Defined•G.711•G.729Step 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.The SIP Bandwidth (kbps) text box is highlighted only when you select the SIP codec as User-Defined. If youchoose the SIP codec as G.711, the SIP Bandwidth (kbps) text box is set to 64. If you choose the SIP codecas G.729, the SIP Bandwidth (kbps) text box is set to 8.NoteStep 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 calllimit includes both direct and roaming-in calls. If the maximum call limit is reached, the new or roaming-in calls resultin failure.The possible range is 0 to 25.The default value is 0, which indicates that there is no check for maximum call limit.If SIP CAC is supported and the CAC method is static, the Maximum Possible Voice Calls and MaximumPossible Roaming Reserved Calls fields appear.NoteCisco Wireless LAN Controller Configuration Guide, Release 7.4       OL-28744-01 141Configuring Voice and Video Parameters
Step 15 Select the Metrics Collection check box to collect traffic stream metrics. By default, this box is unselected. That is, thetraffic 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 or 802.11b/g/n, select the 802.11a (or 802.11b/g)Network Status check box, andclick 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.Configuring Voice Parameters (CLI)Before You BeginEnsure that you have configured SIP-based CAC.Step 1 See all of the WLANs configured on the controller by entering this command:show wlan summaryStep 2 Make sure that the WLAN that you are planning to modify is configured for WMM and the QoS level is set to Platinumby entering this command:show wlan wlan_idStep 3 Disable all WLANs with WMM enabled prior to changing the voice parameters by entering the command:config wlan disable wlan_idStep 4 Disable the radio network by entering this command:config {802.11a |802.11b}disable networkStep 5 Save your settings by entering this command:save configStep 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 networkby entering this command:config {802.11a |802.11b}cac voice max-bandwidth bandwidthThe bandwidth range is 5 to 85%, and the default value is 75%. Once the client reaches the value specified, the accesspoint 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 bandwidthThe bandwidth range is 0 to 25%, and the default value is 6%. The controller reserves this much bandwidth from themaximum allocated bandwidth for roaming voice clients.   Cisco Wireless LAN Controller Configuration Guide, Release 7.4142 OL-28744-01  Configuring Voice and Video Parameters
Step 9 Configure the codec name and sample interval as parameters and to calculate the required bandwidth per call by enteringthis command:config {802.11a |802.11b}cac voice sip codec {g711 |g729}sample-interval number_msecsStep 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_msecsStep 11 Reenable all WLANs with WMM enabled by entering this command:config wlan enable wlan_idStep 12 Reenable the radio network by entering this command:config {802.11a |802.11b}enable networkStep 13 View the TSM voice metrics by entering this command:show [802.11a | 802.11b] cu-metrics AP_NameThe command also displays the channel utilization metrics.Step 14 Enter the save config command to save your settings.Step 15 Configure voice automatically for a WLAN by entering this command:config auto-configure voice cisco wlan-id radio {802.11a |802.11b |all}Step 16 Enter the save config command to save your settings.Configuring Video ParametersConfiguring Video Parameters (GUI)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 or 802.11b/g/n, unselect the 802.11a (or 802.11b/g)NetworkStatus check box, and click Apply to disable the radio network.Step 4 Choose Wireless >802.11a/n 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 defaultvalue 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.For TSpec and SIP based CAC for video calls, only Static method is supported.NoteStep 7 In the Max RF Bandwidth text box, enter the percentage of the maximum bandwidth allocated to clients for videoapplications on this radio band. When the client reaches the value specified, the access point rejects new requests on thisradio band.The range is 5% to 85%. The sum of maximum bandwidth percentage of voice and video should not exceed 85%. Thedefault is 0%.Cisco Wireless LAN Controller Configuration Guide, Release 7.4       OL-28744-01 143Configuring Voice and Video Parameters
Step 8 In the Reserved Roaming Bandwidth text box, enter the percentage of the maximum RF bandwidth that is reserved forroaming 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.You cannot enable SIP CAC if you have selected the Load Based CAC method.NoteStep 10 Click Apply.Step 11 Reenable all WMM WLANs and click Apply.Step 12 Choose Network under 802.11a/n or 802.11b/g/n, select the 802.11a (or 802.11b/g)Network Status check box, andclick Apply to reenable the radio network.Step 13 Click Save Configuration.Step 14 Repeat this procedure if you want to configure video parameters for another radio band.Configuring Video Parameters (CLI)Before You BeginEnsure that you have configured SIP-based CAC.Step 1 See all of the WLANs configured on the controller by entering this command:show wlan summaryStep 2 Make sure that the WLAN that you are planning to modify is configured for WMM and the QoS level is set to Gold byentering this command:show wlan wlan_idStep 3 Disable all WLANs with WMM enabled prior to changing the video parameters by entering this command:config wlan disable wlan_idStep 4 Disable the radio network by entering this command:config {802.11a |802.11b}disable networkStep 5 Save your settings by entering this command:save configStep 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 networkby entering this command:config {802.11a |802.11b}cac video max-bandwidth bandwidthThe bandwidth range is 5 to 85%, and the default value is 5%. However, the maximum RF bandwidth cannot exceed85% for voice and video. Once the client reaches the value specified, the access point rejects new calls on this network.   Cisco Wireless LAN Controller Configuration Guide, Release 7.4144 OL-28744-01  Configuring Voice and Video Parameters
If this parameter is set to zero (0), the controller assumes that you do not want to do any bandwidth allocationand, therefore, allows all bandwidth requests.NoteStep 9 To configure the percentage of the maximum RF bandwidth that is reserved for roaming clients for video, enter thiscommand:config {802.11a |802.11b}cac video roam-bandwidth bandwidthStep 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_idStep 13 Reenable the radio network by entering this command:config {802.11a |802.11b}enable networkStep 14 Enter the save config command to save your settings.Viewing Voice and Video SettingsViewing Voice and Video Settings (GUI)Step 1 Choose Monitor >Clients to open the Clients page.Step 2 Click the MAC address of the desired client to open the Clients > Detail page.This page shows the U-APSD status (if enabled) for this client under Quality of Service Properties.Step 3 Click Back to return to the Clients page.Step 4 See the TSM statistics for a particular client and the access point to which this client is associated as follows:a) Hover your cursor over the blue drop-down arrow for the desired client and choose 802.11aTSM or 802.11b/g TSM.The Clients > AP page appears.b) Click the Detail link for the desired access point to open the Clients > AP > Traffic Stream Metrics page.This page shows the TSM statistics for this client and the access point to which it is associated. The statistics areshown in 90-second intervals. The timestamp text box shows the specific interval when the statistics were collected.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 or 802.11b/g/n. The 802.11a/n Radios or 802.11b/g/nRadios page appears.b) Hover your cursor over the blue drop-down arrow for the desired access point and choose 802.11aTSM or 802.11b/gTSM. 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 in90-second intervals. The timestamp text box shows the specific interval when the statistics were collected.Cisco Wireless LAN Controller Configuration Guide, Release 7.4       OL-28744-01 145Configuring Voice and Video Parameters
Viewing Voice and Video Settings (CLI)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_nameInformation similar to the following appears:Call Admission Control (CAC) StatsVoice Bandwidth in use(% of config bw)......... 0Total channel MT free........................ 0Total voice MT free.......................... 0Na Direct.................................... 0Na Roam...................................... 0Video Bandwidth in use(% of config bw)......... 0Total num of voice calls in progress........... 0Num of roaming voice calls in progress......... 0Total Num of voice calls since AP joined....... 0Total Num of roaming calls since AP joined..... 0Total Num of exp bw requests received.......... 5Total Num of exp bw requests admitted.......... 2Num of voice calls rejected since AP joined...... 0Num of roam calls rejected since AP joined..... 0Num of calls rejected due to insufficient bw....0Num of calls rejected due to invalid params.... 0Num of calls rejected due to PHY rate.......... 0Num of calls rejected due to QoS policy..... 0In the example above, “MT”is medium time, “Na”is the number of additional calls, and “exp bw”is expedited bandwidth.Suppose an AP has to be rebooted when a voice client associated with the AP is on an active call. After the APis rebooted, the client continues to maintain the call, and during the time the AP is down, the database is notrefreshed by the controller. Therefore, we recommend that all active calls are ended before the AP is takendown.NoteStep 3 See the U-APSD status for a particular client by entering this command:show client detail client_macStep 4 See the TSM statistics for a particular client and the access point to which this client is associated by entering thiscommand: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 followingappears:Client Interface Mac: 00:01:02:03:04:05   Cisco Wireless LAN Controller Configuration Guide, Release 7.4146 OL-28744-01  Configuring Voice and Video Parameters
Measurement Duration: 90 secondsTimestamp 1st Jan 2006, 06:35:80UpLink Stats================Average Delay (5sec intervals)............................35Delay less than 10 ms.....................................20Delay bet 10 - 20 ms......................................20Delay bet 20 - 40 ms......................................20Delay greater than 40 ms..................................20Total packet Count.........................................80Total packet lost count (5sec).............................10Maximum Lost Packet count(5sec)............................5Average Lost Packet count(5secs)...........................2DownLink Stats================Average Delay (5sec intervals)............................35Delay less than 10 ms.....................................20Delay bet 10 - 20 ms......................................20Delay bet 20 - 40 ms......................................20Delay greater than 40 ms..................................20Total packet Count.........................................80Total packet lost count (5sec).............................10Maximum Lost Packet count(5sec)............................5Average Lost Packet count(5secs)...........................2The statistics are shown in 90-second intervals. The timestamp text box shows the specific interval when thestatistics were collected.NoteClear the TSM statistics for a particular access point or all the access points to which this client is associatedby entering this clear client tsm {802.11a |802.11b}client_mac {ap_mac |all} command.NoteStep 5 See the TSM statistics for a particular access point and a particular client associated to this access point by entering thiscommand: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:AP Interface Mac: 00:0b:85:01:02:03Client Interface Mac: 00:01:02:03:04:05Measurement Duration: 90 secondsTimestamp 1st Jan 2006, 06:35:80UpLink Stats================Average Delay (5sec intervals)............................35Delay less than 10 ms.....................................20Delay bet 10 - 20 ms......................................20Delay bet 20 - 40 ms......................................20Delay greater than 40 ms..................................20Total packet Count.........................................80Total packet lost count (5sec).............................10Maximum Lost Packet count(5sec)............................5Average Lost Packet count(5secs)...........................2DownLink StatsCisco Wireless LAN Controller Configuration Guide, Release 7.4       OL-28744-01 147Configuring Voice and Video Parameters
================Average Delay (5sec intervals)............................35Delay less than 10 ms.....................................20Delay bet 10 - 20 ms......................................20Delay bet 20 - 40 ms......................................20Delay greater than 40 ms..................................20Total packet Count.........................................80Total packet lost count (5sec).............................10Maximum Lost Packet count(5sec)............................5Average Lost Packet count(5secs)...........................2The statistics are shown in 90-second intervals. The timestamp text box shows the specific interval when thestatistics were collected.NoteStep 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 packetconfigures 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 two802.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 theconsole. You can use this command to monitor a maximum of two 802.11 clients. If one of the clients is a non-WiFiclient, only the 802.11 client is monitored for debug messages.It is implicitly assumed that the clients being monitored are oncall.NoteThe debug command automatically stops after 60minutes.NoteStep 8 Use the following commands to view various voice-related parameters:•show client voice-diag statusDisplays information about whether voice diagnostics is enabled or disabled. If enabled, will also displays informationabout 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 diagnosticsis disabled appears.•show client voice-diag tspecDisplays the TSPEC information sent from the clients that are enabled for voice diagnostics.•show client voice-diag qos-mapDisplays 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_rssiDisplay the client’s RSSI values in the last 5 seconds when voice diagnostics is enabled.•show client voice-diag roam-historyDisplays information about the last three roaming calls. The output contains the timestamp, access point associatedwith roaming, roaming reason, and if there is a roaming failure, the reason for the roaming-failure.   Cisco Wireless LAN Controller Configuration Guide, Release 7.4148 OL-28744-01  Configuring Voice and Video Parameters
•show client calls {active | rejected} {802.11a | 802.11bg | all}This command lists the details of active TSPEC and SIP calls on the controller.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 multicastrates.•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 trafficstatistics.•debug ap show stats {802.11b | 802.11a} ap-name client {all |video |client-mac}—Displays the access point’sclient 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 databasenumber.•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.Configuring SIP-Based CACRestrictions for SIP-Based CAC•SIPs are available only on the Cisco 5500 Series Controllers, Cisco 8500 Series Controllers, and on the1240, 1130, and 11n access points.•SIP CAC should only be used for phones that support status code 17 and do not support TSPEC-basedadmission control.•SIP CAC will be supported only if SIP snooping is enabled.Configuring SIP-Based CAC (GUI)Before You Begin•Ensure that you have set the voice to the platinum QoS level.•Ensure that you have enabled call snooping for the WLAN.Cisco Wireless LAN Controller Configuration Guide, Release 7.4       OL-28744-01 149Configuring SIP-Based CAC
•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.Configuring SIP-Based CAC (CLI)Step 1 Set the voice to the platinum QoS level by entering this command:config wlan qos wlan-id PlatinumStep 2 Enable the call-snooping feature for a particular WLAN by entering this command:config wlan call-snoop enable wlan-idStep 3 Enable the ACM to this radio by entering this command:config {802.11a |802.11b}cac {voice |video}acm enableStep 4 To configure the call snooping ports, enter this command:config advanced sip-snooping-ports starting-port ending-portStep 5 To troubleshoot SIP-based CAC events, enter this command:debug sip event {enable |disable}   Cisco Wireless LAN Controller Configuration Guide, Release 7.4150 OL-28744-01  Configuring SIP-Based CAC
Configuring Media ParametersConfiguring Media Parameters (GUI)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 or 802.11b/g/n, unselect the 802.11a (or 802.11b/g)NetworkStatus check box, and click Apply to disable the radio network.Step 4 Choose Wireless >802.11a/n 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 allocatedfor media applications on this radio band. Once the client reaches the specified value, the access point rejects new callson 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 is80.Step 10 Select the Multicast Direct Enable check box to enable the Multicast Direct Enable text box. The default value isenabled.Step 11 From the Max Streams per Radio drop-down list, choose the maximum number of allowed multicast direct streamsper 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. Choosea 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 defaultvalue is disabled.Configuring Voice Prioritization Using Preferred Call NumbersInformation About Configuring Voice Prioritization Using Preferred Call NumbersYou can configure a controller to support calls from clients that do not support TSPEC-based calls. Thisfeature is known as voice prioritization. These calls are given priority over other clients utilizing the voicepool. Voice prioritization is available only for SIP-based calls and not for TSPEC-based calls. If the bandwidthis available, it takes the normal flow and allocates the bandwidth to those calls.You can configure up to six preferred call numbers. When a call comes to one of the configured preferrednumbers, the controller does not check on the maximum call limit. It invokes the CAC to allocate bandwidthfor the preferred call. The bandwidth allocation is 85 percent of the entire bandwidth pool, not just from themaximum configured voice pool. The bandwidth allocation is the same even for roaming calls.Cisco Wireless LAN Controller Configuration Guide, Release 7.4       OL-28744-01 151Configuring Media Parameters
Prerequisites for Configuring Voice Prioritization Using Preferred Call NumbersYou must configure the following before configuring voice prioritization:•Set WLAN QoS to platinum.•Enable ACM for the radio.•Enable SIP call snooping on the WLAN.Configuring a Preferred Call Number (GUI)Step 1 Set the WLAN QoS profile to Platinum.Step 2 Enable ACM for the WLAN radio.Step 3 Enable SIP call snooping for the WLAN.Step 4 Choose Wireless > Advanced > Preferred Call to open the Preferred Call page.All calls configured on the controller appear.To remove a preferred call, hover your cursor over the blue drop-down arrow and choose Remove.NoteStep 5 Click Add Number to add a new preferred call.Step 6 In the Call Index text box, enter the index that you want to assign to the call. Valid values are from 1 through 6.Step 7 In the Call Number text box, enter the number.Step 8 Click Apply to add the new number.Configuring a Preferred Call Number (CLI)Step 1 Set the voice to the platinum QoS level by entering this command:config wlan qos wlan-id PlatinumStep 2 Enable the ACM to this radio by entering this command:config {802.11a | 802.11b} cac {voice | video} acm enableStep 3 Enable the call-snooping feature for a particular WLAN by entering this command:config wlan call-snoop enable wlan-idStep 4 Add a new preferred call by entering this command:config advanced sip-preferred-call-no call_index {call_number |none}Step 5 Remove a preferred call by entering this command:config advanced sip-preferred-call-no call_index noneStep 6 View the preferred call statistics by entering the following command:show ap stats {802.11{a | b} | wlan} ap_name   Cisco Wireless LAN Controller Configuration Guide, Release 7.4152 OL-28744-01  Configuring Voice Prioritization Using Preferred Call Numbers
Step 7 Enter the following command to list the preferred call numbers:show advanced sip-preferred-call-noConfiguring EDCA ParametersInformation About EDCA ParametersEnhanced distributed channel access (EDCA) parameters are designed to provide preferential wireless channelaccess for voice, video, and other quality-of-service (QoS) traffic.Configuring EDCA Parameters (GUI)Step 1 Choose Wireless and then Network under 802.11a/n or 802.11b/g/n, unselect the 802.11a (or 802.11b/g)NetworkStatus check box, and click Apply to disable the radio network.Step 2 Choose EDCA Parametersunder 802.11a/n or 802.11b/g/n. The 802.11a (or 802.11b/g) > EDCA Parameters pageappears.Step 3 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 optionwhen voice or video services are not deployed on your network.•Spectralink Voice Priority—Enables SpectraLink voice priority parameters. Choose this option if SpectraLinkphones are deployed on your network to improve the quality of calls.•Voice Optimized—Enables EDCA voice-optimized profile parameters. Choose this option when voice servicesother than SpectraLink are deployed on your network.•Voice & Video Optimized—Enables EDCA voice- and video-optimized profile parameters. Choose this optionwhen 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 optionalso match the 6.0 WMM EDCA parameters when this profile is applied.If you deploy video services, admission control (ACM) must bedisabled.NoteStep 4 If you want to enable MAC optimization for voice, select the Enable Low Latency MAC check box. Otherwise, leavethis check box unselected, which is the default value. This feature enhances voice performance by controlling packetretransmits and appropriately aging out voice packets on lightweight access points, which improves the number of voicecalls serviced per access point.We do not recommend you to enable low latency MAC. You should enable low latency MAC only if the WLANallows WMM clients. If WMM is enabled, then low latency MAC can be used with any of the EDCA profiles.NoteCisco Wireless LAN Controller Configuration Guide, Release 7.4       OL-28744-01 153Configuring EDCA Parameters
Step 5 Click Apply to commit your changes.Step 6 To reenable the radio network, choose Network under 802.11a/n or 802.11b/g/n, select the 802.11a (or 802.11b/g)Network Status check box, and click Apply.Step 7 Click Save Configuration.Configuring EDCA Parameters (CLI)Step 1 Disable the radio network by entering this command:config {802.11a |802.11b}disable networkStep 2 Save your settings by entering this command:save configStep 3 Enable a specific EDCA profile by entering this command:config advanced {802.11a | 802.11b}edca-parameters {wmm-default | svp-voice| optimized-voice|optimzed-voice-video| custom-voice}•wmm-default—Enables the Wi-Fi Multimedia (WMM) default parameters. This is the default value. Choose thisoption when voice or video services are not deployed on your network.•svp-voice—Enables SpectraLink voice priority parameters. Choose this option if SpectraLink phones are deployedon your network to improve the quality of calls.•optimized-voice—Enables EDCA voice-optimized profile parameters. Choose this option when voice servicesother than SpectraLink are deployed on your network.•optimized-video-voice—Enables EDCA voice- and video-optimized profile parameters. Choose this option whenboth 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 alsomatch the 6.0 WMM EDCA parameters when this profile is applied.If you deploy video services, admission control (ACM) must bedisabled.NoteStep 4 View the current status of MAC optimization for voice by entering this command:show {802.11a |802.11b}Information similar to the following appears:Voice-mac-optimization...................DisabledStep 5 Enable or disable MAC optimization for voice by entering this command:config advanced {802.11a |802.11b}voice-mac-optimization {enable |disable}This feature enhances voice performance by controlling packet retransmits and appropriately aging out voice packetson lightweight access points, which improves the number of voice calls serviced per access point. The default value isdisabled.   Cisco Wireless LAN Controller Configuration Guide, Release 7.4154 OL-28744-01  Configuring EDCA Parameters
Step 6 Reenable the radio network by entering this command:config {802.11a |802.11b}enable networkStep 7 Enter the save config command to save your settings.Cisco Wireless LAN Controller Configuration Guide, Release 7.4       OL-28744-01 155Configuring EDCA Parameters
   Cisco Wireless LAN Controller Configuration Guide, Release 7.4156 OL-28744-01  Configuring EDCA Parameters
CHAPTER 17Configuring the Cisco Discovery Protocol•Information About Configuring the Cisco Discovery Protocol, page 157•Restrictions for Configuring the Cisco Discovery Protocol, page 157•Configuring the Cisco Discovery Protocol, page 159•Viewing Cisco Discovery Protocol Information, page 161•Getting CDP Debug Information, page 163Information About Configuring the Cisco Discovery ProtocolThe Cisco Discovery Protocol (CDP) is a device discovery protocol that runs on all Cisco-manufacturedequipment. A device enabled with CDP sends out periodic interface updates to a multicast address in orderto make itself known to neighboring devices.The default value for the frequency of periodic transmissions is 60 seconds, and the default advertisedtime-to-live value is 180 seconds. The second and latest version of the protocol, CDPv2, introduces newtime-length-values (TLVs) and provides a reporting mechanism that allows for more rapid error tracking,which reduces downtime.Cisco recommends that you disable Cisco Discovery Protocol on the controller and access point whenconnected to non-Cisco switches as CDP is unsupported on non-Cisco switches and network elements.NoteRestrictions for Configuring the Cisco Discovery Protocol•CDPv1 and CDPv2 are supported on the following devices:◦Cisco 5500 and 2500 Series Controllers◦CAPWAP-enabled access points◦An access point connected directly to a Cisco 5500 Series ControllerCisco Wireless LAN Controller Configuration Guide, Release 7.4        OL-28744-01 157
To use the Intelligent Power Management feature, ensure that CDPv2 is enabled on theCisco 2500 Series Controllers. CDP v2 is enabled by default.Note•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 witha 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 CDPneighbor.◦Platform TLV: 0x0006—The hardware platform of the controller, the access point, or the CDPneighbor.◦Power Available TLV: 0x001a—The amount of power available to be transmitted by powersourcing 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 CDPpackets are sent out.•These TLVs are supported only by the access point:◦Power Consumption TLV: 0x0010—The maximum amount of power consumed by the accesspoint.◦Power Request TLV:0x0019—The amount of power to be transmitted by a powerable device inorder to negotiate a suitable power level with the supplier of the network power.•Changing the CDP configuration on the controller does not change the CDP configuration on the accesspoints that are connected to the controller. You must enable and disable CDP separately for each accesspoint.•You can enable or disable the CDP state on all or specific interfaces and radios. This configuration canbe 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. Thepersistent 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.   Cisco Wireless LAN Controller Configuration Guide, Release 7.4158 OL-28744-01  Restrictions for Configuring the Cisco Discovery Protocol
◦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 previousimage. The CDP configuration for radio interfaces is applicable only for mesh APs.Configuring the Cisco Discovery ProtocolConfiguring the Cisco Discovery Protocol (GUI)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. Thedefault value is selected.Enabling or disabling this feature is applicable to all controllerports.NoteStep 3 From the CDP Advertisement Version drop-down list, choose v1 or v2 to specify the highest CDP version supported onthe 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 to254 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 thisfeature. The default value is enabled.If CDP is disabled in Step 2, a message indicating that the Controller CDP is disabled appears.Note•Enable CDP for a specific Ethernet interface, radio, or slot as follows:Choose Wireless >Access Points >All APs to open the All APs page.Click the link for the desired access point.Choose the Interfaces tab and select the corresponding check boxes for the radios or slots from the CDPConfiguration section.Configuration for radios is only applicable for mesh accesspoints.Click Apply to commit your changes.NoteCisco Wireless LAN Controller Configuration Guide, Release 7.4       OL-28744-01 159Configuring the Cisco Discovery Protocol
•To enable or disable CDP on all access points currently associated to the controller, follow these steps:Choose Wireless >Access Points >Global Configuration to open the Global Configuration page.Select the CDP State check box to enable CDP on all access points associated to the controller or unselect it todisable CDP on all access points. The default value is selected. You can enable CDP on a specific Ethernet interface,radio, or slot by selecting the corresponding check box. This configuration will be applied to all access pointsassociated with the controller.Click Apply to commit your changes.Step 9 Click Save Configuration to save your changes.Configuring the Cisco Discovery Protocol (CLI)Step 1 Enable or disable CDP on the controller by entering this command:config cdp {enable |disable}CDP is enabled by default.Step 2 Specify the interval at which CDP messages are to be generated by entering this command:config cdp timer secondsThe 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 secondsThe 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 accesspoints that join in the future. CDP remains disabled on both current and future access points even after the controller oraccess point reboots. To enable CDP, enter the config ap cdp enable all command.After you enable CDP on all access points joined to the controller, you may disable and then reenable CDP onindividual access points using the command in Step 6. After you disable CDP on all access points joined to thecontroller, you may not enable and then disable CDP on individual access points.NoteStep 6 Enable or disable CDP on a specific access point by entering this command:config ap cdp {enable |disable}Cisco_APStep 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}When you use the config ap cdp command to configure CDP on radio interfaces, a warning message appearsindicating that the configuration is applicable only for mesh access points.Note   Cisco Wireless LAN Controller Configuration Guide, Release 7.4160 OL-28744-01  Configuring the Cisco Discovery Protocol
Step 8 Save your changes by entering this command:save configViewing Cisco Discovery Protocol InformationViewing Cisco Discovery Protocol Information (GUI)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 RouteBridge, S - Switch, H - Host, I - IGMP, r - Repeater, or M - Remotely Managed Device•The hardware platform of each CDP neighbor deviceStep 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•The software running on the CDP neighborCisco Wireless LAN Controller Configuration Guide, Release 7.4       OL-28744-01 161Viewing Cisco Discovery Protocol Information
Step 3 Choose AP Neighbors to see a list of CDP neighbors for all access points connected to the controller. The CDP APNeighbors 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 RouteBridge, 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 neighborStep 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•The number of invalid packets   Cisco Wireless LAN Controller Configuration Guide, Release 7.4162 OL-28744-01  Viewing Cisco Discovery Protocol Information
Viewing Cisco Discovery Protocol Information (CLI)Step 1 See the status of CDP and to view CDP protocol information by entering this command:show cdpStep 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.This command shows only the CDP neighbors of the controller. It does not show the CDP neighbors of thecontroller’s associated access points. Additional commands are provided below to show the list of CDP neighborsper access point.NoteStep 3 See all CDP entries in the database by entering this command:show cdp entry allStep 4 See CDP traffic information on a given port (for example, packets sent and received, CRC errors, and so on) by enteringthis command:show cdp trafficStep 5 See the CDP status for a specific access point by entering this command:show ap cdp ap-name Cisco_APStep 6 See the CDP status for all access points that are connected to the controller by entering this command:show ap cdp allStep 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_APThe access point sends CDP neighbor information to the controller only when the information changes.NoteStep 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 allThe access point sends CDP neighbor information to the controller only when the information changes.NoteGetting CDP Debug Information•Get debug information related to CDP packets by entering by entering this command:Cisco Wireless LAN Controller Configuration Guide, Release 7.4       OL-28744-01 163Getting CDP Debug Information
debug cdp packets•Get debug information related to CDP events by entering this command:debug cdp events   Cisco Wireless LAN Controller Configuration Guide, Release 7.4164 OL-28744-01  Getting CDP Debug Information
CHAPTER 18Configuring Authentication for the Controller andNTP Server•Information About Configuring Authentication for the Controller and NTP Server, page 165•Configuring the NTP Server for Authentication (GUI), page 165•Configuring the NTP Server for Authentication (CLI), page 166Information About Configuring Authentication for the Controller and NTP ServerStarting in release 7.0.116.0, the controller software is now compliant with RFC 1305. As per this requirement,controllers must synonymize time with an NTP server by authentication. By default, an MD5 checksum isused.Configuring the NTP Server for Authentication (GUI)Step 1 Choose Controller >NTP >Server to open the NTP Severs page.Step 2 Click New to add a new NTP Server.Step 3 In the Server Index (Priority) text box, enter the NTP 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 usingonly one NTP server.Step 4 Enter the server IP address.Step 5 Enable or disable the NTP Authentication.Step 6 If you enable the NTP Authentication, enter the Key Index.Step 7 Click Apply.Cisco Wireless LAN Controller Configuration Guide, Release 7.4        OL-28744-01 165
Configuring the NTP Server for Authentication (CLI)Before You Begin•config time ntp auth enable server-index key-index—Enables NTP authentication on a given NTPserver.•config time ntp key-auth add key-index md5 key-format key—Adds an authentication key. By defaultMD5 is used. The key format can be "ascii" or "hex".•config time ntp key-auth delete key-index—Deletes authentication keys.•config time ntp auth disable server-index—Disables NTP authentication.•show ntp-keys—Displays the NTP authentication related parameter.   Cisco Wireless LAN Controller Configuration Guide, Release 7.4166 OL-28744-01  Configuring the NTP Server for Authentication (CLI)
CHAPTER 19Configuring RFID Tag Tracking•Information About Configuring RFID Tag Tracking, page 167•Configuring RFID Tag Tracking (CLI), page 168•Viewing RFID Tag Tracking Information (CLI), page 169•Debugging RFID Tag Tracking Issues (CLI), page 169Information About Configuring RFID Tag TrackingThe controller enables you to configure radio-frequency identification (RFID) tag tracking. RFID tags aresmall wireless devices that are affixed to assets for real-time location tracking. They operate by advertisingtheir location using special 802.11 packets, which are processed by access points, the controller, and themobility services engine.To know more about the tags supported by controller, see http://www.cisco.com/web/partners/pr46/pr147/ccx_wifi_tags.html. The mobility services engine receives telemetry and chokepoint information from tagsthat are compliant with this CCX specification.Table 5: Cisco Compatible Extensions for RFID Tags SummaryPango (InnerWireless)WhereNetAeroScoutPartnersV3Wheretag IVT3T2Product NameTelemetryX—XXTemperature————Pressure————Humidity————Status————FuelCisco Wireless LAN Controller Configuration Guide, Release 7.4        OL-28744-01 167
Pango (InnerWireless)WhereNetAeroScoutPartners————Quantity————DistanceX—XXMotion Detection1021Number of Panic ButtonsXXXTamperingXXXXBattery InformationXXXMultiple-Frequency Tags33For chokepoint systems, note that the tag can work only with chokepoints coming from the same vendor.The Network Mobility Services Protocol (NMSP) runs on the mobility services engine. For NMSP tofunction, the TCP port (16113) over which the controller and the mobility services engine communicatemust be open (not blocked) on any firewall that exists between these two devices.NoteThe Cisco-approved tags support these capabilities:•Information notifications—Enables you to view vendor-specific and emergency information.•Information polling—Enables you to monitor battery status and telemetry data. Many telemetry datatypes provide support for sensory networks and a large range of applications for RFID tags.•Measurement notifications—Enables you to deploy chokepoints at strategic points within your buildingsor campuses. Whenever an RFID tag moves to within a defined proximity of a chokepoint, the tag beginstransmitting packets that advertise its location in relation to the chokepoint.You can configure and view RFID tag tracking information through the controller CLI.Configuring RFID Tag Tracking (CLI)Step 1 Enable or disable RFID tag tracking by entering this command:config rfid status {enable |disable}The default value is enabled.Step 2 Specify a static timeout value (between 60 and 7200 seconds) by entering this command:config rfid timeout seconds   Cisco Wireless LAN Controller Configuration Guide, Release 7.4168 OL-28744-01  Configuring RFID Tag Tracking (CLI)
The static timeout value is the amount of time that the controller maintains tags before expiring them. For example, if atag is configured to beacon every 30 seconds, we recommend that you set the timeout value to 90 seconds (approximatelythree 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 enterthis command, tags are unable to obtain a DHCP address for client mode when attempting to select and/or downloada configuration.•config rfid mobility vendor_name disable—Disables client mobility for a specific vendor’s tags. When you enterthis command, tags can obtain a DHCP address. If a tag roams from one subnet to another, it obtains a new addressrather than retaining the anchor state.These commands can be used only for Pango tags. Therefore, the only valid entry for vendor_name is“pango”in all lowercase letters.NoteViewing RFID Tag Tracking Information (CLI)Step 1 See the current configuration for RFID tag tracking by entering this command:show rfid configStep 2 See detailed information for a specific RFID tag by entering this command:show rfid detailmac_addresswhere 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 summaryStep 4 See a list of RFID tags that are associated to the controller as clients by entering this command:show rfid clientDebugging RFID Tag Tracking Issues (CLI)If you experience any problems with RFID tag tracking, use these debug commands.•Configure MAC address debugging by entering this command:debug mac addr mac_addressCisco Wireless LAN Controller Configuration Guide, Release 7.4       OL-28744-01 169Viewing RFID Tag Tracking Information (CLI)
We recommend that you perform the debugging on a per-tag basis. If you enabledebugging for all of the tags, the console or Telnet screen is inundated with messages.Note•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.   Cisco Wireless LAN Controller Configuration Guide, Release 7.4170 OL-28744-01  Debugging RFID Tag Tracking Issues (CLI)
CHAPTER 20Resetting the Controller to Default Settings•Information About Resetting the Controller to Default Settings, page 171•Resetting the Controller to Default Settings (GUI), page 171•Resetting the Controller to Default Settings (CLI), page 172Information About Resetting the Controller to Default SettingsYou can return the controller to its original configuration by resetting the controller to factory-default settings.Resetting the Controller to Default Settings (GUI)Step 1 Start your Internet browser.Step 2 Enter the controller IP address in the browser address line and press Enter. An Enter Network Password dialog boxappears.Step 3 Enter your username in the User Name text box. The default username is admin.Step 4 Enter the wireless device password in the Password text box and press Enter. The default password is admin.Step 5 Choose Commands >Reset to Factory Default.Step 6 Click Reset.Step 7 When prompted, confirm the reset.Step 8 Reboot the controller without saving the configuration.Step 9 Use the configuration wizard to enter configuration settings. See the Configuring the Controller—Using the CLIConfiguration Wizard section for more information.Cisco Wireless LAN Controller Configuration Guide, Release 7.4        OL-28744-01 171
Resetting the Controller to Default Settings (CLI)Step 1 Enter the reset system command. At the prompt that asks whether you need to save changes to the configuration, enterN. 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:Welcome to the Cisco WLAN Solution Wizard Configuration ToolStep 3 Use the configuration wizard to enter configuration settings. See the Configuring the Controller—Using the CLIConfiguration Wizard section for more information.   Cisco Wireless LAN Controller Configuration Guide, Release 7.4172 OL-28744-01  Resetting the Controller to Default Settings (CLI)
CHAPTER 21Managing Controller Software andConfigurations•Upgrading the Controller Software, page 173•Transferring Files to and from a Controller, page 187•Saving Configurations, page 202•Editing Configuration Files, page 202•Clearing the Controller Configuration, page 203•Erasing the Controller Configuration, page 203•Resetting the Controller, page 204Upgrading the Controller SoftwareWhen you upgrade the controller software, the software on the access points associated with the controller isalso automatically upgraded. When an access point is loading software, each of its LEDs blinks in succession.Up to 10 access points can be concurrently upgraded from the controller.Do not power down the controller or any access point during this process; otherwise, you might corruptthe software image. Upgrading a controller with a large number of access points can take as long as 30minutes, depending on the size of your network. However, with the increased number of concurrent accesspoint upgrades supported in the controller software release, the upgrade time should be significantlyreduced. The access points must remain powered, and the controller must not be reset during this time.CautionRestrictions for Upgrading Controller Software•If you require a downgrade from one release to another, you might lose the configuration from yourcurrent release. The workaround is to reload the previous controller configuration files saved on thebackup server or to reconfigure the controller.•It is not possible to directly upgrade to this release from a release that is older than 6.0.182.0.Cisco Wireless LAN Controller Configuration Guide, Release 7.4        OL-28744-01 173
•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 accesspoints that are associated with the controller are upgraded to the intermediate release before you installthe latest controller software. In large networks, it can take some time to download the software on eachaccess point.•When you upgrade to the latest software release, the software on the access points associated with thecontroller is also automatically upgraded. When an access point is loading software, each of its LEDsblinks in succession.•We recommend that you access the controller GUI using Microsoft Internet Explorer 6.0 SP1 (or a laterrelease) or Mozilla Firefox 2.0.0.11 (or a later release).•Cisco controllers support standard SNMP Management Information Base (MIB) files. MIBs can bedownloaded from the Software Center on Cisco.com.•The controller software is factory installed on your controller and automatically downloaded to theaccess points after a release upgrade and whenever an access point joins a controller. We recommendthat 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 includethe bootloader, field recovery image, and FPGA/MCU firmware. Installing the FUS image requiresspecial attention because it installs some critical firmware. The FUS image is independent of the runtimeimage. For more information, see http://www.cisco.com/en/US/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 guidelineswhen setting up a TFTP or FTP server:◦Ensure that your TFTP server supports files that are larger than the size of the controller softwarerelease. Some TFTP servers that support files of this size are tftpd32 and the TFTP server withinthe Cisco Prime Infrastructure. If you attempt to download the controller software and your TFTPserver does not support files of this size, the following error message appears: “TFTP failure whilestoring in flash.”◦If you are upgrading through the distribution system network port, the TFTP or FTP server can beon 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 toinitialize 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 controllerplatforms.Bootloader menu for 5500 Series Controllers:Boot OptionsPlease choose an option from below:1. Run primary image2. Run backup image3. Change active boot image4. Clear Configuration5. Format FLASH Drive6. Manually update imagesPlease enter your choice:   Cisco Wireless LAN Controller Configuration Guide, Release 7.4174 OL-28744-01  Upgrading the Controller Software
Bootloader menu for other controller platforms:Boot OptionsPlease choose an option from below:1. Run primary image2. Run backup image3. Manually update images4. Change active boot image5. Clear ConfigurationPlease enter your choice:Enter 1to run the current software, enter 2to run the previous software, enter 4(on a 5500 seriescontroller), or enter 5(on another controller platform) to run the current software and set the controllerconfiguration to factory defaults. Do not choose the other options unless directed to do so.See the Installation Guide or the Quick Start Guide for your controller for more detailson running the bootup script and power-on self-test.Note•Control which address(es) are sent in CAPWAP discovery responses when NAT is enabled on theManagement 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 commandif all APs are outside of the NAT gateway.•disable—Enables use of both NAT IP and non-NAT IP in discovery response. Use this commandif APs are on the inside and outside of the NAT gateway; for example, Local Mode and OfficeExtendAPs on the same controller.To avoid stranding APs, you must disable AP link-latency (if enabled) before you usethe disable option for the config network ap-discovery nat-ip-only command. Todisable AP link-latency, use the config ap link-latency disable all command.Note•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 wiredpackets. 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 trafficbetween 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 mightcorrupt the software image. Upgrading a controller with a large number of access points can take as longas 30 minutes, depending on the size of your network. However, with the increased number of concurrentaccess point upgrades supported, the upgrade time should be significantly reduced. The access pointsmust 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:Cisco Wireless LAN Controller Configuration Guide, Release 7.4       OL-28744-01 175Upgrading the Controller Software
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 totake 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 primaryimage 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 fromthe boot menu to boot from the backup image. Then, upgrade with a known working image and rebootthe controller.•The recovery image provides a backup image that can be used if an access point power-cycles duringan image upgrade. The best way to avoid the need for access point recovery is to prevent an access pointfrom power-cycling during a system upgrade. If a power-cycle occurs during an upgrade to an oversizedaccess 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:1Download 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.2Connect the TFTP server to the same subnet as the target access point and power-cycle the accesspoint. The access point boots from the TFTP image and then joins the controller to download theoversized access point image and complete the upgrade procedure.3After 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 ifFederal Information Processing Standard (FIPS) is enabled.Upgrading Controller Software (GUI)Step 1 Upload your controller configuration files to a server to back them up.We highly recommend that you back up your configuration files of the controller prior to upgrading the controllersoftware. Otherwise, you must manually reconfigure the controller.NoteStep 2 Get the controller software image by following these steps:a) Browse to the Cisco Software Center: http://www.cisco.com/cisco/software/navigator.html.b) Choose Wireless >Wireless LAN Controller.   Cisco Wireless LAN Controller Configuration Guide, Release 7.4176 OL-28744-01  Upgrading the Controller Software
The following options are available: Integrated Controllers and Controller Modules 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 releaseto download:Early Deployment (ED)—These software releases provide new features, new hardware platform support, and bugfixes.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 athrough kto download the remaining file.Step 3 Copy the controller software image (filename.aes) to the default directory on your TFTP or FTP server.Step 4 (Optional) Disable the 802.11 networks.For busy networks, controllers on high utilization, or small controller platforms, we recommend that you disablethe 802.11 networks as a precautionary measure.NoteStep 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)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 Timeouttext 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 theTimeout text field should work correctly without any adjustment. However, you can change these values if desired. Todo so, enter the maximum number of times that the TFTP server attempts to download the software in the MaximumRetries text box and the amount of time (in seconds) that the TFTP server attempts to download the software in theTimeout 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.Cisco Wireless LAN Controller Configuration Guide, Release 7.4       OL-28744-01 177Upgrading the Controller Software
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.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 theController Summary area.Upgrading Controller Software (CLI)Step 1 Upload your controller configuration files to a server to back them up.We highly recommend that you back up your controller's configuration files prior to upgrading the controllersoftware. Otherwise, you must manually reconfigure the controller.NoteStep 2 Get the controller software image by following these steps:a) Browse to the Cisco Software Center: http://www.cisco.com/cisco/software/navigator.html.b) Choose Wireless >Wireless LAN Controller.The following options are available: Integrated Controllers and Controller Modules 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 releaseto download:Early Deployment (ED)—These software releases provide new features, new hardware platform support, and bugfixes.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 athrough kto download the remaining file.Step 3 Copy the controller software image (filename.aes) to the default directory on your TFTP or FTP server.Step 4 (Optional) Disable the 802.11 networks.   Cisco Wireless LAN Controller Configuration Guide, Release 7.4178 OL-28744-01  Upgrading the Controller Software
For busy networks, controllers on high utilization, or small controller platforms, we recommend that you disablethe 802.11 networks as a precautionary measure.NoteStep 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 thecurrent 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-filePathnames on a TFTP or FTP server are relative to the server’s default or root directory. For example, inthe case of the Solaris TFTP server, the path is “/”.NoteIf you are using a TFTP server, also enter these commands:•transfer download tftpMaxRetries retries•transfer download tftpPktTimeout timeoutThe 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 TFTPserver 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.NoteIf you are using an FTP server, also enter these commands:•transfer download username username•transfer download password password•transfer download port portThe default value for the port parameter is21.NoteStep 10 View the current updated settings by entering the transfer download start command. Answer y to the prompt to confirmthe 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 systemThe 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_idCisco Wireless LAN Controller Configuration Guide, Release 7.4       OL-28744-01 179Upgrading the Controller Software
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 theshow sysinfo command on the controller CLI and see Recovery Image Version or Emergency Image Version.If a Cisco Unified Wireless Network Controller Boot Software ER.aes file is not installed, Recovery ImageVersion or Emergency Image Version show 'N/A.'NotePredownloading an Image to an Access PointTo minimize a network outages, you can now download an upgrade image to the access point from thecontroller without resetting the access point or losing network connectivity. Previously, you would downloadan upgrade image to the controller and reset it, which causes the access point to go into discovery mode. Afterthe access point discovers the controller with the new image, the access point downloads the new image,resets, goes into discovery mode, and rejoins the controller.You can now download the upgrade image to the controller and then download the image to the access pointwhile the network is still up. You can also schedule a reboot of the controller and access points, either aftera specified amount of time or at a specific date and time. When both devices are up, the access point discoversand rejoins the controller.Access Point Predownload ProcessThe access point predownload feature works as follows:•The controller image is downloaded.◦The primary image becomes the backup image of the controller and the downloaded image becomesthe new primary image. Change the current boot image as the backup image by using the configboot backup command to ensure that if a system failure occurs, the controller boots with the lastworking image of the controller.◦To switch over to the new downloaded image, start predownload of the upgraded image using theconfig ap image predownload primary all command.◦The upgrade image is downloaded as the backup image on the access points. You can verify thisby using the show ap image all command.◦Change the boot image to primary image manually using the config boot primary command andreboot the controller for the upgrade image to be activated.or◦You issue a scheduled reboot with the swap keyword. The swap keyword has the followingimportance: The swapping occurs to the primary and backup images on the access point and thecurrently active image on controller with the backup image.◦When the controller reboots, the access points are disassociated and eventually come up with anupgraded image. Once the controller responds to the discovery request sent by an access point withits discovery response packet, the access point sends a join request.   Cisco Wireless LAN Controller Configuration Guide, Release 7.4180 OL-28744-01  Upgrading the Controller Software
•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 theversions match, the access point joins the controller.◦If the versions do not match, the access point compares the version of the backup image and ifthey match, the access point swaps the primary and backup images and reloads and subsequentlyjoins the controller.◦If the primary image of the access point is the same as the controller image, the access point reloadsand joins the controller.◦If none of the above conditions are true, the access point sends an image data request to thecontroller, downloads the latest image, reloads, and joins the controller.Restrictions for Predownloading an Image to an Access Point•The maximum number of concurrent predownloads is limited to half the number of concurrent normalimage downloads. This limitation allows new access points to join the controller during imagedownloading.If you reach the predownload limit, then the access points that cannot get an image sleep for a timebetween 180 to 600 seconds and then reattempt the predownload.•Before you predownload, you should change the active controller boot image to the backup image toensure that if the controller reboots for some reason, it comes back up with the earlier running image,not the partially downloaded upgrade image.•Access points with 16-MB total available memory (1130 and 1240 access points) may not have enoughfree memory to download an upgrade image and may automatically delete crash info files, radio files,and any backup images to free up space. However, this limitation does not affect the predownload processbecause the predownload image replaces any backup image on the access point.•When the system time is changed by using the config time command, the time set for a scheduled resetis not valid and the scheduled system reset is canceled. You are given an option either to cancel thescheduled 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 andbackup images. That is, the primary image of all three controllers should be X and the secondary imageof 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:%OSAPI-3-RESETSYSTEM_FAILED: osapi_task.c:4458 System will not reset as software isbeing upgraded.•Predownloading a 7.2 or later version of image on a Cisco Aironet 1240 access point is not supportedwhen upgrading from a previous controller release. If predownloading is attempted to the Cisco Aironet1240 access point, the AP gets disconnected.Cisco Wireless LAN Controller Configuration Guide, Release 7.4       OL-28744-01 181Upgrading the Controller Software
Predownloading an Image to Access Points—Global Configuration (GUI)Step 1 Upload your controller configuration files to a server to back them up.We highly recommend that you back up your controller's configuration files prior to upgrading the controllersoftware. Otherwise, you must manually reconfigure the controller.NoteStep 2 Follow these steps to obtain the controller software:a) Browse to the Cisco Software Center: http://www.cisco.com/cisco/software/navigator.htmlb) 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 releaseto download:Early Deployment (ED)—These software releases provide new features, new hardware platform support, and bugfixes.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.For busy networks, controllers on high utilization, or small controller platforms, we recommend that you disablethe 802.11X networks as a precautionary measure.NoteStep 5 For Cisco WiSM2, shut down the controller port channel on the Catalyst switch to allow the controller to reboot beforethe access points start downloading the software.Step 6 Disable any WLANs on the controller.Step 7 Choose Commands > Download File to open the Download File to Controller page.Step 8 From the File Type drop-down list, choose Code.Step 9 From the Transfer Mode drop-down list, choose from the following options:•TFTP•FTP•SFTP (available in 7.4 and later releases)Step 10 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 textboxes should work correctly without any adjustment. However, you can change these values.   Cisco Wireless LAN Controller Configuration Guide, Release 7.4182 OL-28744-01  Upgrading the Controller Software
Step 11 Enter the maximum number of times that the TFTP server attempts to download the software in the Maximum Retriestext box and the amount of time (in seconds) that the TFTP server attempts to download the software in the Timeouttext box.Step 12 In the File Path text box, enter the directory path of the software.Step 13 In the File Name text box, enter the name of the controller software file (filename.aes).Step 14 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 15 Click Download to download the software to the controller. A message appears indicating the status of the download.Step 16 To configure the predownloading of access point images globally, choose Wireless > Access Points > GlobalConfiguration to open the Global Configuration page.Step 17 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 Primaryunder 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.Step 18 Click OK.Step 19 Click Apply.Configuring Predownload Image to an Access Point (GUI)Step 1 Upload your controller configuration files to a server to back them up.We highly recommend that you back up your controller's configuration files prior to upgrading the controllersoftware. Otherwise, you must manually reconfigure the controller.NoteStep 2 Follow these steps to obtain the controller software:a) Browse to the Cisco Software Center: http://www.cisco.com/cisco/software/navigator.htmlb) Select 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 releaseto download:Early Deployment (ED)—These software releases provide new features, new hardware platform support, and bugfixes.Cisco Wireless LAN Controller Configuration Guide, Release 7.4       OL-28744-01 183Upgrading the Controller Software
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 802.11 networks.For busy networks, controllers on high utilization, or small controller platforms, we recommend that you disablethe 802.11 networks as a precautionary measure.NoteStep 5 For Cisco WiSM2, shut down the controller port channel on the Catalyst switch to allow the controller to reboot beforethe access points start downloading the software.Step 6 Disable any WLANs on the controller.Step 7 Choose Commands > Download File to open the Download File to Controller page.Step 8 From the File Type drop-down list, choose Code.Step 9 From the Transfer Mode drop-down list, choose from the following options:•TFTP•FTP•SFTP (available from the 7.4 release onwardsStep 10 In the IP Address text box, enter the IP address of the TFTP or FTP server.If you are using a TFTP server, the default values of 10 retries and 6 seconds for the Maximum Retries and Timeouttext boxes should work correctly without any adjustment. However, you can change these values.Step 11 Enter the maximum number of times that the TFTP server attempts to download the software in the Maximum Retriestext box and the amount of time (in seconds) that the TFTP server attempts to download the software in the Timeouttext box.Step 12 In the File Path text box, enter the directory path of the software.Step 13 In the File Name text box, enter the name of the controller software file (filename.aes).Step 14 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 15 Click Download to download the software to the controller. A message appears indicating the status of the download.Step 16 To configure the predownloading of a specific access point, choose Wireless > All APs > AP_Name to open the AllAP Details page for the selected AP.Step 17 Click the Advanced tab.Step 18 In the AP Image Pre-download section, perform one of the following:   Cisco Wireless LAN Controller Configuration Guide, Release 7.4184 OL-28744-01  Upgrading the Controller Software
•To instruct the access point to predownload a primary image from the controller, click Download Primary underthe AP Image Pre-download.•To instruct the access point to swap its 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.Step 19 Click OK.Step 20 Click Apply.Predownloading an Image to Access Points (CLI)Using the CLI, you can predownload an image to a specific access point or to all access points.Step 1 Follow these steps to obtain the controller software:a) Browse to the Cisco Software Center: http://www.cisco.com/cisco/software/navigator.htmlb) Select 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 releaseto download:Early Deployment (ED)—These software releases provide new features, new hardware platform support, and bugfixes.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 n to download the remaining file.Step 2 Copy the controller software file (filename.aes) to the default directory on your TFTP or FTP server.Step 3 (Optional) Disable the 802.11 networks.For busy networks, controllers on high utilization, or small controller platforms, we recommend that you disablethe 802.11a/n or 802.11b/g/n networks as a precautionary measure.NoteCisco Wireless LAN Controller Configuration Guide, Release 7.4       OL-28744-01 185Upgrading the Controller Software
Step 4 For Cisco WiSM2, shut down the controller port channel on the Catalyst switch to allow the controller to reboot beforethe access points start downloading the software.Step 5 Disable any WLANs on the controller using the config wlan disable wlan_id command.Step 6 Specify access points that will receive the predownload image.Use one of these commands to specify access points for predownload:•Specify access points for predownload by entering this command:config ap image predownload {primary |backup} {ap_name |all}The primary image is the new image; the backup image is the existing image. Access points always boot with theprimary image.•Swap an access point’s primary and backup images by entering this command:config ap image swap {ap_name |all}•Display detailed information on access points specified for predownload by entering this command:show ap image {all |ap-name}The output lists access points that are specified for predownloading and provides for each access point, primary andsecondary image versions, the version of the predownload image, the predownload retry time (if necessary), and thenumber of predownload attempts. The output also includes the predownload status for each device. The status of theaccess 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 hasbeen 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]The swap operand in the reset command will result in the swapping of the primary and backup imageson both the controller and the access point.The controller sends a reset message to all joined access points, and then the controller resets.Note•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.The swap operand in the reset command will result in the swapping of the primary and backup imageson both the controller and the access point.Note   Cisco Wireless LAN Controller Configuration Guide, Release 7.4186 OL-28744-01  Upgrading the Controller Software
•Set up an SNMP trap message that announces the upcoming reset by entering this command:reset system notify-time minutesThe controller sends the announcement trap the configured number of minutes before the reset.•Cancel the scheduled reboot by entering this command:reset system cancelIf you configure reset times and then use the config time command to change the system time on thecontroller, the controller notifies you that any scheduled reset times will be canceled and must bereconfigured after you set the system time.NoteUse the show reset command to display scheduled resets.Information similar to the following appears:System reset is scheduled for Apr 08 01:01:01 2010.Current local time and date is Apr 07 02:57:44 2010.A trap will be generated 10 minutes before each scheduled system reset.Use 'reset system cancel' to cancel the reset.Configuration will be saved before the system reset.Transferring Files to and from a ControllerControllers have built-in utilities for uploading and downloading various files. Follow the instructions in thesesections to import files using either the controller GUI or CLI:•Downloading a Login Banner File•Downloading Device Certificates•Downloading CA Certificates•Uploading PACs•Uploading and Downloading Configuration FilesDownloading a Login Banner FileYou can download a login banner file using either the GUI or the CLI. The login banner is the text that appearson the page before user authentication when you access the controller GUI or CLI using Telnet, SSH, or aconsole port connection.You save the login banner information as a text (*.txt) file. The text file cannot be larger than 1296 charactersand cannot have more than 16 lines of text.Cisco Wireless LAN Controller Configuration Guide, Release 7.4       OL-28744-01 187Transferring Files to and from a Controller
The ASCII character set consists of printable and nonprintable characters. The login banner supports onlyprintable characters.NoteHere is an example of a login banner:Welcome to the Cisco Wireless Controller!Unauthorized access prohibited.Contact sysadmin@corp.com for access.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 subnetas the service port because the service port is not routable, or you must create static routes on thecontroller.•If you are downloading through the distribution system network port, the TFTP or FTP server can beon 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 becausethe Prime Infrastructure built-in TFTP or FTP server and the third-party TFTP or FTP server requirethe same communication port.Clearing the controller configuration does not remove the login banner. See the Clearingthe Login Banner (GUI) section for information about clearing the login banner usingthe controller GUI or CLI.NoteThe controller can have only one login banner file. If you download another login bannerfile to the controller, the first login banner file is overwritten.NoteDownloading a Login Banner File (GUI)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   Cisco Wireless LAN Controller Configuration Guide, Release 7.4188 OL-28744-01  Transferring Files to and from a Controller
•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 textboxes 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 Retriestext box and the amount of time (in seconds) that the TFTP server attempts to download the certificate in the Timeouttext 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 thedownload.Downloading a Login Banner File (CLI)Step 1 Log into the controller CLI.Step 2 Specify the transfer mode used to download the config file by entering this command:transfer download mode {tftp |ftp |sftp}Step 3 Download the controller login banner by entering this command:transfer download datatype login-bannerStep 4 Specify the IP address of the TFTP or FTP server by entering this command:transfer download serverip server-ip-addressStep 5 Specify the name of the config file to be downloaded by entering this command:transfer download path server-path-to-fileStep 6 Specify the directory path of the config file by entering this command:transfer download filenamefilename.txtStep 7 If you are using a TFTP server, enter these commands:•transfer download tftpMaxRetries retries•transfer download tftpPktTimeout timeoutThe 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 TFTPserver 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.NoteCisco Wireless LAN Controller Configuration Guide, Release 7.4       OL-28744-01 189Transferring Files to and from a Controller
Step 8 If you are using an FTP server, enter these commands:•transfer download username username•transfer download password password•transfer download port portThe default value for the port parameter is21.NoteStep 9 View the download settings by entering the transfer download start command. Enter y when prompted to confirm thecurrent settings and start the download process.Clearing the Login Banner (GUI)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.Downloading Device CertificatesEach wireless device (controller, access point, and client) has its own device certificate. For example, thecontroller is shipped with a Cisco-installed device certificate. This certificate is used by EAP-FAST (whennot using PACs), EAP-TLS, PEAP-GTC, and PEAP-MSCHAPv2 to authenticate wireless clients during localEAP authentication. However, if you want to use your own vendor-specific device certificate, it must bedownloaded to the controller.For more information about configuring local EAP, see the Configuring Local EAP section.NoteFollow the instructions in this section to download a vendor-specific device certificate to the controller throughthe GUI or CLI. However, before you begin, make sure you have a TFTP or FTP server available for thecertificate 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 subnetas the service port because the service port is not routable, or you must create static routes on thecontroller.•If you are downloading through the distribution system network port, the TFTP or FTP server can beon the same or a different subnet because the distribution system port is routable.   Cisco Wireless LAN Controller Configuration Guide, Release 7.4190 OL-28744-01  Transferring Files to and from a Controller
•A third-party TFTP or FTP server cannot run on the same computer as Cisco Prime Infrastructure becausethe Prime Infrastructure built-in TFTP or FTP server and the third-party TFTP or FTP server requirethe same communication port.All certificates downloaded to the controller must be in PEM format.NoteDownloading Device Certificates (GUI)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 textboxes 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 Retriestext box and the amount of time (in seconds) that the TFTP server attempts to download the certificate in the Timeouttext 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 thedownload.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.Cisco Wireless LAN Controller Configuration Guide, Release 7.4       OL-28744-01 191Transferring Files to and from a Controller
Downloading Device Certificates (CLI)Step 1 Log onto the controller CLI.Step 2 Specify the transfer mode used to download the config file by entering this command:transfer download mode {tftp |ftp |sftp}Step 3 Specify the type of the file to be downloaded by entering this command:transfer download datatype eapdevcertStep 4 Specify the certificate’s private key by entering this command:transfer download certpassword passwordStep 5 Specify the IP address of the TFTP or FTP server by entering this command:transfer download serverip server-ip-addressStep 6 Specify the name of the config file to be downloaded by entering this command:transfer download path server-path-to-fileStep 7 Specify the directory path of the config file by entering this command:transfer download filename filename.pemStep 8 If you are using a TFTP server, enter these commands:•transfer download tftpMaxRetries retries•transfer download tftpPktTimeout timeoutThe 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 TFTPserver 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.NoteStep 9 If you are using an FTP server, enter these commands:•transfer download username username•transfer download password password•transfer download port portThe default value for the port parameter is21.NoteStep 10 View the updated settings by entering the transfer download start command. Answer y when prompted to confirm thecurrent settings and start the download process.Step 11 Reboot the controller by entering this command:reset system   Cisco Wireless LAN Controller Configuration Guide, Release 7.4192 OL-28744-01  Transferring Files to and from a Controller
Downloading CA CertificatesControllers and access points have a Certificate Authority (CA) certificate that is used to sign and validatedevice certificates. The controller is shipped with a Cisco-installed CA certificate. This certificate may beused by EAP-FAST (when not using PACs), EAP-TLS, PEAP-GTC, and PEAP-MSCHAPv2 to authenticatewireless clients during local EAP authentication. However, if you want to use your own vendor-specific CAcertificate, it must be downloaded to the controller.For more information about configuring local EAP, see the Configuring Local EAP section.NoteFollow 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 certificatedownload. 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 subnetas the service port because the service port is not routable, or you must create static routes on thecontroller.•If you are downloading through the distribution system network port, the TFTP or FTP server can beon 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 becausethe Prime Infrastructure built-in TFTP or FTP server and the third-party TFTP or FTP server requirethe same communication port.All certificates downloaded to the controller must be in PEM format.NoteDownload CA Certificates (GUI)Step 1 Copy the CA 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 CA Certificate.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 textboxes should work correctly without any adjustment. However, you can change these values.Cisco Wireless LAN Controller Configuration Guide, Release 7.4       OL-28744-01 193Transferring Files to and from a Controller
Step 6 Enter the maximum number of times that the TFTP server attempts to download the certificate in the Maximum Retriestext box and the amount of time (in seconds) that the TFTP server attempts to download the certificate in the Timeouttext 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.Downloading CA Certificates (CLI)Step 1 Log on to the controller CLI.Step 2 Specify the transfer mode used to download the config file by entering this command:transfer download mode {tftp |ftp |sftp}Step 3 Specify the type of the file to be downloaded by entering this command:transfer download datatype eapdevcertStep 4 Specify the IP address of the TFTP or FTP server by entering this command:transfer download serverip server-ip-addressStep 5 Specify the directory path of the config file by entering this command:transfer download path server-path-to-fileStep 6 Specify the name of the config file to be downloaded by entering this command:transfer download filename filename.pemStep 7 If you are using a TFTP server, enter these commands:•transfer download tftpMaxRetries retries•transfer download tftpPktTimeout timeoutThe 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 TFTPserver 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.NoteStep 8 If you are using an FTP server, enter these commands:   Cisco Wireless LAN Controller Configuration Guide, Release 7.4194 OL-28744-01  Transferring Files to and from a Controller
•transfer download username username•transfer download password password•transfer download port portThe default value for the port parameter is21.NoteStep 9 View the updated settings by entering the transfer download start command. Answer y when prompted to confirm thecurrent settings and start the download process.Step 10 Reboot the controller by entering the reset system command.Uploading PACsProtected access credentials (PACs) are credentials that are either automatically or manually provisioned andused 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. Followthese 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 asthe 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 onthe 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 becausethe Prime Infrastructure built-in TFTP or FTP server and the third-party TFTP or FTP server requirethe same communication port.Uploading PACs (GUI)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•FTPCisco Wireless LAN Controller Configuration Guide, Release 7.4       OL-28744-01 195Transferring Files to and from a Controller
•SFTP (available in 7.4 and later releases)Step 7 In the IP Address text box, enter the IP 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. Thedefault 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 passwordthat you entered above.Uploading PACs (CLI)Step 1 Log on to the controller CLI.Step 2 Specify the transfer mode used to upload the config file by entering this command:transfer upload mode {tftp |ftp |sftp}Step 3 Upload a Protected Access Credential (PAC) by entering this command:transfer upload datatype pacStep 4 Specify the identification of the user by entering this command:transfer upload pac username validity passwordStep 5 Specify the IP address of the TFTP or FTP server by entering this command:transfer upload serverip server-ip-addressStep 6 Specify the directory path of the config file by entering this command:transfer upload path server-path-to-fileStep 7 Specify the name of the config file to be uploaded by entering this command:transfer upload filename manual.pac.Step 8 If you are using an FTP server, enter these commands:•transfer upload username username•transfer upload password password•transfer upload port portThe default value for the port parameter is21.Note   Cisco Wireless LAN Controller Configuration Guide, Release 7.4196 OL-28744-01  Transferring Files to and from a Controller
Step 9 View the updated settings by entering the transfer upload start command. Answer y when prompted to confirm thecurrent 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 passwordthat you entered above.Uploading and Downloading Configuration FilesWe recommend that you upload your controller’s configuration file to a server to back it up. If you lose yourconfiguration, you can then download the saved configuration to the controller.Do not download a configuration file to your controller that was uploaded from a different controllerplatform. For example, a Cisco 5500 Series Controller does not support the configuration file from a Cisco2500 Series Controller.NoteFollow these guidelines when working with configuration files:•Any CLI with an invalid value is filtered out and set to default by the XML validation engine. Validationoccurs during bootup. A configuration may be rejected if the validation fails. A configuration may failif you have an invalid CLI. For example, if you have a CLI where you try to configure a WLAN withoutadding appropriate commands to add the WLAN.•A configuration may be rejected if the dependencies are not addressed. For example, if you try toconfigure dependent parameters without using the add command. The XML validation may succeed butthe configuration download infrastructure will immediately reject the configuration with no validationerrors.•An invalid configuration can be verified by using the show invalid-config command. The showinvalid-config command reports the configuration that is rejected by the controller either as part ofdownload process or by XML validation infrastructure.You can also read and modify the configuration file.NoteUploading Configuration FilesYou can upload configuration files using either the GUI or the CLI.Cisco Wireless LAN Controller Configuration Guide, Release 7.4       OL-28744-01 197Transferring Files to and from a Controller
Uploading the Configuration Files (GUI)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 encryptionkey 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. Thedefault 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 theupload fails, repeat this procedure and try again.Uploading the Configuration Files (CLI)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 configStep 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.Step 4 Specify the IP address of the server by entering this command:transfer upload serverip server-ip-addressStep 5 Specify the directory path of the configuration file by entering this command:transfer upload path server-path-to-fileStep 6 Specify the name of the configuration file to be uploaded by entering this command:   Cisco Wireless LAN Controller Configuration Guide, Release 7.4198 OL-28744-01  Transferring Files to and from a Controller
transfer upload filename filenameStep 7 If you are using an FTP server, enter these commands to specify the username and password used to log into the FTPserver and the port number through which the upload occurs:•transfer upload username username•transfer upload password password•transfer upload port portThe default value for the port parameter is21.NoteStep 8 Initiate the upload process by entering this command:transfer upload startStep 9 When prompted to confirm the current settings, answer y.Information similar to the following appears:Mode............................................. TFTPTFTP Server IP................................... 10.10.10.4TFTP Path........................................ Config/TFTP Filename.................................... AS_4402_4_2_55_8_Config.xmlData Type........................................ Config FileEncryption....................................... Disabled***************************************************** WARNING: Config File Encryption Disabled *****************************************************Are you sure you want to start? (y/N) YFile transfer operation completed successfully.If the upload fails, repeat this procedure and try again.Downloading Configuration FilesYou can download configuration files using either the GUI or the CLI.Downloading the Configuration Files (GUI)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 keyused to decrypt the file in the Encryption Key text box.The key that you enter here should match the one entered during the upload process.NoteStep 4 From the Transfer Mode drop-down list, choose from the following options:Cisco Wireless LAN Controller Configuration Guide, Release 7.4       OL-28744-01 199Transferring Files to and from a Controller
•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 textboxes 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 MaximumRetries text box and the amount of time (in seconds) that the TFTP server attempts to download the configuration filein 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, andthe controller reboots automatically. If the download fails, repeat this procedure and try again.Downloading the Configuration Files (CLI)The controller does not support incremental configuration downloads. The configuration file contains allmandatory 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 ofthe configuration file, the download fails. Only the commands present in the configuration file are appliedto the controller, and any configuration in the controller prior to the download is removed.NoteStep 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 configStep 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.The key that you enter here should match the one entered during the upload process.Note   Cisco Wireless LAN Controller Configuration Guide, Release 7.4200 OL-28744-01  Transferring Files to and from a Controller
Step 4 Specify the IP address of the TFTP or FTP server by entering this command:transfer download serverip server-ip-addressStep 5 Specify the directory path of the configuration file by entering this command:transfer download path server-path-to-fileStep 6 Specify the name of the configuration file to be downloaded by entering this command:transfer download filename filenameStep 7 If you are using a TFTP server, enter these commands:•transfer download tftpMaxRetries retries•transfer download tftpPktTimeout timeoutThe 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 TFTPserver 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.NoteStep 8 If you are using an FTP server, enter these commands to specify the username and password used to log into the FTPserver and the port number through which the download occurs:•transfer upload username username•transfer upload password password•transfer upload port portThe default value for the port parameter is21.NoteStep 9 View the updated settings by entering this command:transfer download startStep 10 When prompted to confirm the current settings and start the download process, answer y.Information similar to the following appears:Mode............................................. TFTPTFTP Server IP................................... 10.10.10.4TFTP Path........................................ Config/TFTP Filename.................................... AS_4402_4_2_55_8_Config.xmlData Type........................................ Config FileEncryption....................................... Disabled***************************************************** WARNING: Config File Encryption Disabled *****************************************************Are you sure you want to start? (y/N) yFile transfer operation completed successfully.If the download fails, repeat this procedure and try again.Cisco Wireless LAN Controller Configuration Guide, Release 7.4       OL-28744-01 201Transferring Files to and from a Controller
Saving ConfigurationsControllers contain two kinds of memory: volatile RAM and NVRAM. At any time, you can save theconfiguration 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 controllerreboots.•logout—Prompts you to confirm that you want to save configuration changes before you log out.Editing Configuration FilesWhen you save the controller’s configuration, the controller stores it in XML format in flash memory. Controllersoftware release 5.2 or later releases enable you to easily read and modify the configuration file by convertingit to CLI format. When you upload the configuration file to a TFTP/FTP/SFTP server, the controller initiatesthe conversion from XML to CLI. You can then read or edit the configuration file in a CLI format on theserver. When you are finished, you download the file back to the controller, where it is reconverted to anXML format and saved.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 CLIcommands to the file.To edit the configuration file, you can use either Notepad or WordPad on Windows or the VI editor onLinux.NoteStep 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 thenew configuration. CLI commands with known keywords and proper syntax are converted to XML while improper CLIcommands are ignored and saved to flash memory. Any CLI commands that have invalid values are replaced with defaultvalues. To see any ignored commands or invalid configuration values, enter this command:show invalid-configYou cannot execute this command after the clear config or save config command.NoteStep 5 If the downloaded configuration contains a large number of invalid CLI commands, you might want to upload the invalidconfiguration to the TFTP or FTP server for analysis. To do so, perform one of the following:   Cisco Wireless LAN Controller Configuration Guide, Release 7.4202 OL-28744-01  Saving Configurations
•Upload the invalid configuration using the controller GUI. Follow the instructions in the Uploading ConfigurationFiles (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 ConfigurationFiles (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 toconfigure the controller ports, enter these commands:•config port linktrap {port |all} {enable |disable}—Enables or disables the up and down link traps for a specificcontroller port or for all ports.•config port adminmode {port |all} {enable |disable}—Enables or disables the administrative mode for a specificcontroller port or for all ports.Step 7 Save your changes by entering this command:save configClearing the Controller ConfigurationStep 1 Clear the configuration by entering this command:clear configEnter yat the confirmation prompt to confirm the action.Step 2 Reboot the system by entering this command:reset systemEnter n to reboot without saving configuration changes. When the controller reboots, the configuration wizard startsautomatically.Step 3 Follow the instructions in the Configuring the Controller-Using the Configuration Wizard section to complete the initialconfiguration.Erasing the Controller ConfigurationStep 1 Reset the configuration by entering this command:reset systemAt the confirmation prompt, enter y to save configuration changes to NVRAM. The controller reboots.Step 2 When you are prompted for a username, restore the factory-default settings by entering this command:Cisco Wireless LAN Controller Configuration Guide, Release 7.4       OL-28744-01 203Clearing the Controller Configuration
recover-configThe 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 initialconfiguration.Resetting the ControllerYou can reset the controller and view the reboot process on the CLI console using one of the following twomethods:•Turn the controller off and then turn it back on.•On the CLI, enter reset system. At the confirmation prompt, enter y to save configuration changes toNVRAM. The controller reboots.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.   Cisco Wireless LAN Controller Configuration Guide, Release 7.4204 OL-28744-01  Resetting the Controller
CHAPTER 22Managing User Accounts•Configuring Guest User Accounts, page 205•Configuring Administrator Usernames and Passwords, page 208•Changing the Default Values for SNMP v3 Users, page 210Configuring Guest User AccountsInformation About Creating Guest AccountsThe controller can provide guest user access on WLANs. The first step in creating guest user accounts is tocreate a lobby administrator user, also known as a lobby ambassador account. Once this account has beencreated, a lobby ambassador can create and manage guest user accounts on the controller. The lobby ambassadorhas limited configuration privileges and access only to the web pages used to manage the guest accounts.The lobby ambassador can specify the amount of time that the guest user accounts remain active. After thespecified time elapses, the guest user accounts expire automatically.Restrictions for Managing User AccountsThe local user database is limited to a maximum of 2048 entries, which is also the default value. This databaseis shared by local management users (including lobby ambassadors), local network users (including guestusers), MAC filter entries, exclusion list entries, and access point authorization list entries. Together theycannot exceed the configured maximum value.Creating a Lobby Ambassador AccountCreating a Lobby Ambassador Account (GUI)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.Cisco Wireless LAN Controller Configuration Guide, Release 7.4        OL-28744-01 205
If you want to delete any of the user accounts from the controller, hover your cursor over the blue drop-downarrow and choose Remove. However, deleting the default administrative user prohibits both GUI and CLI accessto the controller. Therefore, you must create a user with administrative privileges (ReadWrite) before you removethe default user.NoteStep 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.Management usernames must be unique because they are stored in a single database.NoteStep 4 In the Password and Confirm Password text boxes, enter a password for the lobby ambassador account.Passwords are case sensitive. The settings for the management User Details parameters depends on the settingsthat you make in the Password Policy page. The following requirements are enforced on the passwordNote•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 changingthe 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 createguest user accounts.The ReadOnly option creates an account with read-only privileges, and the ReadWrite option creates anadministrative account with both read and write privileges.NoteStep 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.Creating a Lobby Ambassador Account (CLI)To create a lobby ambassador account use the following command:config mgmtuser add lobbyadmin_username lobbyadmin_pwd lobby-adminReplacing lobby-admin with read-only creates an account with read-only privileges. Replacinglobby-admin with read-write creates an administrative account with both read and write privileges.Note   Cisco Wireless LAN Controller Configuration Guide, Release 7.4206 OL-28744-01  Configuring Guest User Accounts
Creating Guest User Accounts as a Lobby Ambassador (GUI)Step 1 Log into the controller as the lobby ambassador, using the username and password. The Lobby Ambassador GuestManagement > Guest Users List page appears.Step 2 Click New to create a guest user account. The Lobby Ambassador Guest Management > Guest Users List > New pageappears.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. Thegenerated 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 entera password in both the Password and Confirm Password text boxes.Passwords can contain up to 24 characters and are casesensitive.NoteStep 5 From the Lifetime drop-down lists, choose the amount of time (in days, hours, minutes, and seconds) that this guest useraccount is to remain active. A value of zero (0) for all four text boxes creates a permanent account.Default: 1 dayRange: 5 minutes to 30 daysThe smaller of this value or the session timeout for the guest WLAN, which is the WLAN on which the guestaccount is created, takes precedence. For example, if a WLAN session timeout is due to expire in 30 minutesbut the guest account lifetime has 10 minutes remaining, the account is deleted in 10 minutes upon guest accountexpiry. Similarly, if the WLAN session timeout expires before the guest account lifetime, the client experiencesa recurring session timeout that requires reauthentication.NoteYou can change a guest user account with a nonzero lifetime to another lifetime value at any time while theaccount is active. However, to make a guest user account permanent using the controller GUI, you must deletethe account and create it again. If desired, you can use the config netuser lifetime user_name 0 command tomake a guest user account permanent without deleting and recreating it.NoteStep 6 From the WLAN SSID drop-down list, choose the SSID that will be used by the guest user. The only WLANs that arelisted are those WLANs for which Layer 3 web authentication has been configured.We recommend that you create a specific guest WLAN to prevent any potential conflicts. If a guest accountexpires and it has a name conflict with an account on the RADIUS server and both are on the same WLAN, theusers associated with both accounts are disassociated before the guest account is deleted.NoteStep 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 UsersList page.From this page, you can see all of the guest user accounts, their WLAN SSID, and their lifetime. You can also edit orremove a guest user account. When you remove a guest user account, all of the clients that are using the guest WLANand are logged in using that account’s username are deleted.Step 9 Repeat this procedure to create any additional guest user accounts.Cisco Wireless LAN Controller Configuration Guide, Release 7.4       OL-28744-01 207Configuring Guest User Accounts
Viewing Guest User AccountsViewing the Guest Accounts (GUI)To view guest user accounts using the controller GUI, choose Security >AAA >Local Net Users. The LocalNet Users page appears.From this page, you can see all of the local net user accounts (including guest user accounts) and can edit orremove them as desired. When you remove a guest user account, all of the clients that are using the guestWLAN and are logged in using that account’s username are deleted.Viewing the Guest Accounts (CLI)To see all of the local net user accounts (including guest user accounts) using the controller CLI, enter thiscommand:show netuser summaryConfiguring Administrator Usernames and PasswordsInformation About Configuring Administrator Usernames and PasswordsYou can configure administrator usernames and passwords to prevent unauthorized users from reconfiguringthe controller and viewing configuration information. This section provides instructions for initial configurationand for password recovery.Configuring Usernames and Passwords (GUI)Step 1 Choose Management >Local Management Users.Step 2 Click New.Step 3 Enter the username and password, and confirm the password.Usernames and passwords are case-sensitive and can contain up to 24 ASCII characters. Usernames and passwordscannot contain spaces.Step 4 Choose the User Access Mode as one of the following:•ReadOnly•ReadWrite•LobbyAdminStep 5 Click Apply.   Cisco Wireless LAN Controller Configuration Guide, Release 7.4208 OL-28744-01  Configuring Administrator Usernames and Passwords
Configuring Usernames and Passwords (CLI)Step 1 Configure a username and password by entering one of these commands:•config mgmtuser add username password read-write—Creates a username-password pair with read-writeprivileges.•config mgmtuser add username password read-only—Creates a username-password pair with read-only privileges.Usernames and passwords are case-sensitive and can contain up to 24 ASCII characters. Usernames and passwordscannot contain spaces.If you ever need to change the password for an existing username, enter the config mgmtuser passwordusername new_password command.NoteStep 2 List the configured users by entering this command:show mgmtuserRestoring PasswordsBefore You BeginEnsure 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.For security reasons, the text that you enter does not appear on the controller console.NoteStep 2 At the Enter User Name prompt, enter a new username.Step 3 At the Enter Password prompt, enter a new password.Step 4 At the Re-enter Password prompt, reenter the new password. The controller validates and stores your entries in thedatabase.Step 5 When the User prompt reappears, enter your new username.Step 6 When the Password prompt appears, enter your new password. The controller logs you in with your new username andpassword.Cisco Wireless LAN Controller Configuration Guide, Release 7.4       OL-28744-01 209Configuring Administrator Usernames and Passwords
Changing the Default Values for SNMP v3 UsersInformation About Changing the Default Values for SNMP v3 UsersThe controller uses a default value of “default”for the username, authentication password, and privacy passwordfor SNMP v3 users. Using these standard values presents a security risk. Therefore, Cisco strongly advisesthat you change these values.SNMP v3 is time sensitive. Ensure that you configure the correct time and time zone on your controller.NoteChanging the SNMP v3 User Default Values (GUI)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 andchoose 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. Thedefault value is Read Only.Step 6 From the Authentication Protocol drop-down list, choose the desired authentication method: None,HMAC-MD5 (HashedMessage Authentication Coding-Message Digest 5), or HMAC-SHA (Hashed Message Authentication Coding-SecureHashing 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 BlockChaining-Digital Encryption Standard), or CFB-AES-128 (Cipher Feedback Mode-Advanced Encryption Standard-128).The default value is CFB-AES-128.In order to configure CBC-DES or CFB-AES-128 encryption, you must have selected either HMAC-MD5 orHMAC-SHA as the authentication protocol in Step 6.NoteStep 9 In the Priv Password and Confirm Priv Password text boxes, enter the shared secret key to be used for encryption. Youmust 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.   Cisco Wireless LAN Controller Configuration Guide, Release 7.4210 OL-28744-01  Changing the Default Values for SNMP v3 Users
Changing the SNMP v3 User Default Values (CLI)Step 1 See the current list of SNMP v3 users for this controller by entering this command:show snmpv3userStep 2 If “default”appears in the SNMP v3 User Name column, enter this command to delete this user:config snmp v3user delete usernameThe username parameter is the SNMP v3 username (in this case, “default”).Step 3 Create a new SNMP v3 user by entering this command:config snmp v3user create username {ro |rw} {none |hmacmd5 |hmacsha} {none |des | aescfb128}auth_keyencrypt_keywhere•username is the SNMP v3 username.•ro is read-only mode and rw is read-write mode.•none,hmacmd5, and hmacsha are the authentication protocol options.•none,des, and aescfb128 are the privacy protocol options.•auth_key is the authentication shared secret key.•encrypt_key is the encryption shared secret key.Do not enter “default”for the username,auth_key, and encrypt_key parameters.Step 4 Enter the save config command.Step 5 Reboot the controller so that the SNMP v3 user that you added takes effect by entering reset system command.Cisco Wireless LAN Controller Configuration Guide, Release 7.4       OL-28744-01 211Changing the Default Values for SNMP v3 Users
   Cisco Wireless LAN Controller Configuration Guide, Release 7.4212 OL-28744-01  Changing the Default Values for SNMP v3 Users
CHAPTER 23Managing Web Authentication•Obtaining a Web Authentication Certificate, page 213•Web Authentication Process, page 215•Choosing the Default Web Authentication Login Page, page 218•Using a Customized Web Authentication Login Page from an External Web Server, page 224•Downloading a Customized Web Authentication Login Page, page 225•Assigning Login, Login Failure, and Logout Pages per WLAN, page 229Obtaining a Web Authentication CertificateInformation About Web Authentication CertificatesThe operating system of the controller automatically generates a fully functional web authentication certificate,so you do not need to do anything in order to use certificates with Layer 3 web authentication. However, ifdesired, you can prompt the operating system to generate a new web authentication certificate, or you candownload an externally generated SSL certificate.Obtaining a Web Authentication Certificate (GUI)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 successfullygenerated 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.Cisco Wireless LAN Controller Configuration Guide, Release 7.4        OL-28744-01 213
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 correctlywithout 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 theamount 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.Obtaining a Web Authentication Certificate (CLI)Step 1 See the current web authentication certificate by entering this command:show certificate summaryInformation similar to the following appears:Web Administration Certificate................... Locally GeneratedWeb Authentication Certificate................... Locally GeneratedCertificate compatibility mode:............... offStep 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 webauthb) To reboot the controller to register the new certificate, enter this command:reset systemStep 3 If you prefer to use an externally generated web authentication certificate, follow these steps:We recommend that the Common Name (CN) of the externally generated web authentication certificate be1.1.1.1 (or the equivalent virtual interface IP address) in order for the client’s browser to match the domains ofthe web authentication URL and the web authentication certificate.Note1Specify the name, path, and type of certificate to be downloaded by entering these commands:transfer download mode tftptransfer download datatype webauthcerttransfer download serverip server_ip_addresstransfer download path server_path_to_filetransfer download filename certname.pemtransfer download certpassword password   Cisco Wireless LAN Controller Configuration Guide, Release 7.4214 OL-28744-01  Obtaining a Web Authentication Certificate
transfer download tftpMaxRetries retriestransfer download tftpPktTimeout timeoutThe 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 downloadcan be attempted for the retries parameter and the amount of time (in seconds) allowed for each downloadfor the timeout parameter.Note2Start the download process by entering this command:transfer download start3Reboot the controller to register the new certificate by entering this command:reset systemWeb Authentication ProcessWeb authentication is a Layer 3 security feature that causes the controller to not allow IP traffic (exceptDHCP-related packets) from a particular client until that client has correctly supplied a valid username andpassword. When you use web authentication to authenticate clients, you must define a username and passwordfor each client. When the clients attempt to join the wireless LAN, their users must enter the username andpassword when prompted by a login page.If a client uses more than 20 DNS resolved addresses, the controller overwrites the 21st address in thefirst address space in the Mobile Station Control Block (MSCB) table, but the first address is still retainedin the client. If the client again tries to use the first address, it will not be reachable because the controllerdoes not have this address in the list of allowed addresses for the client's MSCB table.NoteOne-Time Passwords (OTP) are not supported on web authentication.NoteCisco Wireless LAN Controller Configuration Guide, Release 7.4       OL-28744-01 215Web Authentication Process
Disabling Security Alert for Web Authentication ProcessWhen web authentication is enabled (under Layer 3 Security), users might receive a web-browser securityalert the first time that they attempt to access a URL.Figure 19: Typical Web-Browser Security AlertWhen clients connect to a WebAuth SSID with preauthorization ACL configured to allow VPN users, theclients will get disconnected from the SSID every few minutes. Webauth SSIDs must not connect withoutauthenticating on the web page.NoteAfter the user clicks Yes to proceed (or if the client’s browser does not display a security alert), the webauthentication system redirects the client to a login page.Step 1 Click View Certificate on the Security Alert page.Step 2 Click Install Certificate.Step 3 When the Certificate Import Wizard appears, click Next.Step 4 Choose Place all certificates in the following store and click Browse.Step 5 Choose Place all certificates in the following store and click Browse.Step 6 Expand the Trusted Root Certification Authorities folder and choose Local Computer.Step 7 Click OK.Step 8 Click Next >Finish.Step 9 When the “The import was successful”message appears, click OK.   Cisco Wireless LAN Controller Configuration Guide, Release 7.4216 OL-28744-01  Web Authentication Process
Because the issuer text box is blank on the controller self-signed certificate, open Internet Explorer, choose Tools >Internet Options >Advanced, unselect the Warn about Invalid Site Certificates check box under Security, and clickOK.Step 10 Reboot the PC. On the next web authentication attempt, the login page appears.The following figure shows the default web authentication login page.Figure 20: Default Web Authentication Login PageThe default login page contains a Cisco logo and Cisco-specific text. You can choose to have the web authenticationsystem 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 controllerThe Choosing the Default Web Authentication Login Page section provides instructions for choosing how the webauthentication login page appears.Cisco Wireless LAN Controller Configuration Guide, Release 7.4       OL-28744-01 217Web Authentication Process
When the user enters a valid username and password on the web authentication login page and clicks Submit, the webauthentication system displays a successful login page and redirects the authenticated client to the requested URL.Figure 21: Successful Login PageThe default successful login page contains a pointer to a virtual gateway address URL in the https://<IPaddress>/logout.html format. The IP address that you set for the controller virtual interface serves as the redirect addressfor the login pageChoosing the Default Web Authentication Login PageInformation About Default Web Authentication Login PageIf you are using a custom web-auth bundle that is served by the internal controller web server, the page shouldnot contain more than 5 elements (including HTML, CSS, and Images). This is because the internal controllerweb server implements a DoS protection mechanism that limits each client to open a maximum of 5 (five)concurrent TCP connections depending on the load. Some browsers may try to open more than 5 TCP sessionsat the same time (For example Firefox 4) if the page contains more elements and this may result in the pageloading slowly depending on how the browser handles the DoS protection.If you do not want users to connect to a web page using a browser that is configured with SSLv2 only, youcan disable SSLv2 for web authentication by entering the config network secureweb cipher-option sslv2   Cisco Wireless LAN Controller Configuration Guide, Release 7.4218 OL-28744-01  Choosing the Default Web Authentication Login Page
disable command. If you enter this command, users must use a browser that is configured to use a moresecure protocol such as SSLv3 or later releases. The default value is disabled.Cisco TAC is not responsible for creating a custom webauth bundle.NoteIf you have a complex custom web authentication module, it is recommended that you use an external web-authconfig on the controller, where the full login page is hosted at an external web server.Choosing the Default Web Authentication Login Page (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 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 loginpage, 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 Hideoption. 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 desiredURL in the Redirect URL After Login text box. You can enter up to 254 characters.The controller supports web authentication redirects only to HTTP (HTTP over TCP) servers. It does not supportweb authentication redirects to HTTPS (HTTP over SSL) servers.NoteStep 6 If you want to create your own headline on the login page, enter the desired text in the Headline text box. You can enterup 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 enterup to 2047 characters. The default message is “Cisco is pleased to provide the Wireless LAN infrastructure for yournetwork. 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.Choosing the Default Web Authentication Login Page (CLI)Step 1 Specify the default web authentication type by entering this command:config custom-web webauth_type internalStep 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 loginpage, 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}Cisco Wireless LAN Controller Configuration Guide, Release 7.4       OL-28744-01 219Choosing the Default Web Authentication Login Page
Step 4 If you want the user to be directed to a particular URL (such as the URL for your company) after login, enter thiscommand:config custom-web redirecturl urlYou can enter up to 130 characters for the URL. To change the redirect back to the default setting, enter the clearredirecturl command.The controller supports web authentication redirects only to HTTP (HTTP over TCP) servers. It does not supportweb authentication redirects to HTTPS (HTTP over SSL) servers.NoteStep 5 If you want to create your own headline on the login page, enter this command:config custom-web webtitle titleYou can enter up to 130 characters. The default headline is “Welcome to the Cisco wireless network.”To reset theheadline 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 messageYou can enter up to 130 characters. The default message is “Cisco is pleased to provide the Wireless LAN infrastructurefor your network. Please login and put your air space to work.”To reset the message to the default setting, enter the clearwebmessage command.Step 7 To enable or disable the web authentication logout popup window, enter this command:config custom-web logout-popup {enable |disable}Step 8 Enter the save config command to save your settings.Step 9 Import your own logo into the web authentication login page as follows:1Make sure that you have a Trivial File Transfer Protocol (TFTP) server available for the file download. Follow theseguidelines when setting up a TFTP server:•If you are downloading through the service port, the TFTP server must be on the same subnet as the serviceport 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 server can be on the same or adifferent subnet because the distribution system port is routable.•A third-party TFTP server cannot run on the same computer as the Cisco Prime Infrastructure because the PrimeInfrastructure built-in TFTP server and the third-party TFTP server require the same communication port.2Ensure that the controller can contact the TFTP server by entering this command:ping ip-address3Copy the logo file (in .jpg, .gif, or .png format) to the default directory on your TFTP server. The maximum file sizeis 30 kilobits. For an optimal fit, the logo should be approximately 180 pixels wide and 360 pixels high.4Specify the download mode by entering this command:transfer download mode tftp5Specify the type of file to be downloaded by entering this command:transfer download datatype image6Specify the IP address of the TFTP server by entering this command:transfer download serverip tftp-server-ip-address   Cisco Wireless LAN Controller Configuration Guide, Release 7.4220 OL-28744-01  Choosing the Default Web Authentication Login Page
Some TFTP servers require only a forward slash (/) as the TFTP server IP address, and the TFTP serverautomatically determines the path to the correct directory.Note7Specify the download path by entering this command:transfer download path absolute-tftp-server-path-to-file8Specify the file to be downloaded by entering this command:transfer download filename {filename.jpg |filename.gif |filename.png}9View your updated settings and answer yto the prompt to confirm the current download settings and start the downloadby entering this command:transfer download start10 Save your settings by entering this command:save configIf you ever want to remove this logo from the web authentication login page, enter the clear webimagecommand.NoteStep 10 Follow the instructions in the Verifying the Web Authentication Login Page Settings (CLI), on page 228 section to verifyyour settings.Example: Creating a Customized Web Authentication Login PageThis section provides information on creating a customized web authentication login page, which can thenbe accessed from an external web server.Here is a web authentication login page template. It can be used as a model when creating your own customizedpage:<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;}Cisco Wireless LAN Controller Configuration Guide, Release 7.4       OL-28744-01 221Choosing the Default Web Authentication Login Page
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;// This is the status code returned from webauth login action// Any value of status code from 1 to 5 is error condition and user// should be shown error as below or modify the message as it suits// the customerif(args.statusCode == 1){alert("You are already logged in. No further action is required on your part.");}else if(args.statusCode == 2){alert("You are not configured to authenticate against web portal. No further actionis required on your part.");}else if(args.statusCode == 3){alert("The username specified cannot be used at this time. Perhaps the username isalready logged into the system?");}else if(args.statusCode == 4){alert("The User has been excluded. Please contact the administrator.");}else if(args.statusCode == 5){alert("Invalid username and password. Please try again.");}else if(args.statusCode == 6){alert("Invalid email address format. Please try again.");}}</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"> <td colspan="2"><font size="10" color="#336699">WebAuthentication</font></td></tr><tr align="center"><td colspan="2"> User Name    <input type="TEXT" name="username" SIZE="25"MAXLENGTH="63" VALUE="">   Cisco Wireless LAN Controller Configuration Guide, Release 7.4222 OL-28744-01  Choosing the Default Web Authentication Login Page
</td></tr><tr align="center" ><td colspan="2"> Password      <input type="Password" name="password"SIZE="25" MAXLENGTH="24"></td></tr><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 loginpage:•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.The available status codes are as follows:•Status Code 1: “You are already logged in. No further action is required on your part.”•Status Code 2: “You are not configured to authenticate against web portal. No further action is requiredon your part.”•Status Code 3: “The username specified cannot be used at this time. Perhaps the username is alreadylogged into the system?”•Status Code 4: “You have been excluded.”•Status Code 5: “The User Name and Password combination you have entered is invalid. Please try again.”For additional information, see the External Web Authentication with Wireless LANControllers Configuration Example at this URL: http://www.cisco.com/en/US/tech/tk722/tk809/technologies_configuration_example09186a008076f974.shtmlNoteCisco Wireless LAN Controller Configuration Guide, Release 7.4       OL-28744-01 223Choosing the Default Web Authentication Login Page
Example: Modified Default Web Authentication Login Page ExampleThis figure shows an example of a modified default web authentication login page.Figure 22: Modified Default Web Authentication Login Page ExampleThese CLI commands were used to create this login page:•config custom-web weblogo disable•config custom-web webtitle Welcome to the AcompanyBC Wireless LAN!•config custom-web webmessage Contact the System Administrator for a Username and Password.•transfer download start•config custom-web redirecturl urlUsing a Customized Web Authentication Login Page from an External WebServerInformation About Customized Web Authentication Login PageYou can customize the web authentication login page to redirect to an external web server. When you enablethis feature, the user is directed to your customized login page on the external web server.   Cisco Wireless LAN Controller Configuration Guide, Release 7.4224 OL-28744-01  Using a Customized Web Authentication Login Page from an External Web Server
You must configure a preauthentication access control list (ACL) on the WLAN for the external web serverand then choose this ACL as the WLAN preauthentication ACL under Security Policies > Web Policy on theWLANs > 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. Themaximum length is 254 characters. By default, the user is redirected to the URL that was entered in the user's browserbefore the login page was served. of the customized web authentication login page on your web server. You can enterup 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 1 Specify the web authentication type by entering this command:config custom-web webauth_type externalStep 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 urlYou 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_addressStep 4 Enter the save config command to save your settings.Step 5 Follow the instructions in the Verifying the Web Authentication Login Page Settings (CLI), on page 228 section to verifyyour settings.Downloading a Customized Web Authentication Login PageYou can compress the page and image files used for displaying a web authentication login page into a.tar filefor download to a controller. These files are known as the webauth bundle. The maximum allowed size of thefiles in their uncompressed state is 1 MB. When the .tar file is downloaded from a local TFTP server, it entersthe controller’s file system as an untarred file.Cisco Wireless LAN Controller Configuration Guide, Release 7.4       OL-28744-01 225Downloading a Customized Web Authentication Login Page
You can download a login page example from Cisco Prime Infrastructure and use it as a starting point foryour customized login page. For more information, see the Cisco Prime Infrastructure documentation.If you load a webauth bundle with a .tar compression application that is not GNU compliant, the controllercannot 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 GNUstandards, such as PicoZip, to compress the .tar file for the webauth bundle.NoteConfiguration backups do not include extra files or components, such as the webauth bundle or externallicenses, that you download and store on your controller, so you should manually save external backupcopies of those files or components.NoteIf the customized webauth bundle has more than 3 separated elements, we advise you to use an externalserver to prevent page load issues that may be caused because of TCP rate-limiting policy on the controller.NotePrerequisites for Downloading a Customized Web Authentication Login Page•Name the login page login.html. The controller prepares the web authentication URL based on thisname. If the server does not find this file after the webauth bundle has been untarred, the bundle isdiscarded, and an error message appears.•Include input text boxes for both a username and password.•Retain the redirect URL as a hidden input item after extracting from the original URL.•Extract and set the action URL in the page from the original URL.•Include scripts to decode the return status code.•Make sure that all paths used in the main page (to refer to images, for example).•Ensure that no filenames within the bundle are greater than 30 characters.Downloading a Customized Web Authentication Login Page (GUI)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   Cisco Wireless LAN Controller Configuration Guide, Release 7.4226 OL-28744-01  Downloading a Customized Web Authentication Login Page
•SFTP (available in the 7.4 and later releases)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 .tarfile 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 todownload 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:1In the Server Login Username text box, enter the username to log into the FTP server.2In the Server Login Password text box, enter the password to log into the FTP server.3In 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 .tar file to the controller.Step 12 Choose Security >Web Auth >Web Login Page to open the Web Login page.Step 13 From the Web Authentication Type drop-down list, choose Customized (Downloaded).Step 14 Click Apply.Step 15 Click Preview to view your customized web authentication login page.Step 16 If you are satisfied with the content and appearance of the login page, click Save Configuration.Downloading a Customized Web Authentication Login Page (CLI)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 |sftpStep 3 Specify the type of file to be downloaded by entering this command:transfer download datatype webauthbundleStep 4 Specify the IP address of the TFTP server by entering this command:transfer download serverip tftp-server-ip-address.Some TFTP servers require only a forward slash (/) as the TFTP server IP address, and the TFTP serverautomatically determines the path to the correct directory.NoteCisco Wireless LAN Controller Configuration Guide, Release 7.4       OL-28744-01 227Downloading a Customized Web Authentication Login Page
Step 5 Specify the download path by entering this command:transfer download path absolute-tftp-server-path-to-fileStep 6 Specify the file to be downloaded by entering this command:transfer download filename filename.tarStep 7 View your updated settings and answer yto the prompt to confirm the current download settings and start the downloadby entering this command:transfer download startStep 8 Specify the web authentication type by entering this command:config custom-web webauth_type customizedStep 9 Enter the save config command to save your settings.Example: Customized Web Authentication Login PageThis figure shows an example of a customized web authentication login page.Figure 23: Customized Web Authentication Login Page ExampleVerifying the Web Authentication Login Page Settings (CLI)Verify your changes to the web authentication login page by entering this command:show custom-web   Cisco Wireless LAN Controller Configuration Guide, Release 7.4228 OL-28744-01  Downloading a Customized Web Authentication Login Page
Assigning Login, Login Failure, and Logout Pages per WLANInformation About Assigning Login, Login Failure, and Logout Pages per WLANYou can display different web authentication login, login failure, and logout pages to users per WLAN. Thisfeature enables user-specific web authentication pages to be displayed for a variety of network users, such asguest 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 theweb authentication type.Assigning Login, Login Failure, and Logout Pages per WLAN (GUI)Step 1 Choose WLANs to open the WLANs page.Step 2 Click the ID number of the WLAN to which you want to assign a web login, login failure, or logout page.Step 3 Choose Security >Layer 3.Step 4 Make sure that Web Policy and Authentication are selected.Step 5 To override the global authentication configuration web authentication pages, select the Override Global Config checkbox.Step 6 When the Web Auth Type drop-down list appears, choose one of the following options to define the web authenticationpages for wireless 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 separatedrop-down lists appear for login, login failure, and logout page selection. You do not need to define a customizedpage for all three options. Choose None from the appropriate drop-down list if you do not want to display acustomized page for that option.These optional login, login failure, and logout pages are downloaded to the controller as webauth.tarfiles.Note•External—Redirects users to an external server for authentication. If you choose this option, you must also enterthe 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 7 If you chose External as the web authentication type in Step 6, choose AAA Servers and choose up to three RADIUSand LDAP servers using the drop-down lists.The RADIUS and LDAP external servers must already be configured in order to be selectable options on theWLANs > Edit (Security > AAA Servers) page. You can configure these servers on the RADIUS AuthenticationServers page and LDAP Servers page.NoteStep 8 Establish the priority in which the servers are contacted to perform web authentication as follows:The default order is local, RADIUS,LDAP.NoteCisco Wireless LAN Controller Configuration Guide, Release 7.4       OL-28744-01 229Assigning Login, Login Failure, and Logout Pages per WLAN
1Highlight the server type (local, RADIUS, or LDAP) that you want to be contacted first in the box next to the Upand Down buttons.2Click Up and Down until the desired server type is at the top of the box.3Click the <arrow to move the server type to the priority box on the left.4Repeat these steps to assign priority to the other servers.Step 9 Click Apply to commit your changes.Step 10 Click Save Configuration to save your changes.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 enteringthis command:show wlan summaryStep 2 If you want wireless guest users to log into a customized web login, login failure, or logout page, enter these commandsto 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 agiven WLAN.To use the controller’s default login failure page, enter the config wlan custom-web loginfailure-pagenone wlan_id command.Note•config wlan custom-web logout-page page_name wlan_id—Defines a customized logout page for a given WLAN.To use the controller’s default logout page, enter the config wlan custom-web logout-page none wlan_idcommand.NoteStep 3 Redirect wireless guess users to an external server before accessing the web login page by entering this command tospecify the URL of the external server:config wlan custom-web ext-webauth-url ext_web_url wlan_idStep 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.All external servers must be preconfigured on the controller. You can configure them on the RADIUSAuthentication Servers page and the LDAP Servers page.NoteStep 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_idwhere   Cisco Wireless LAN Controller Configuration Guide, Release 7.4230 OL-28744-01  Assigning Login, Login Failure, and Logout Pages per WLAN
•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.You do not need to define the web authentication type in Step 5 for the login failure and logout pages asthey are always customized.Note•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_idIf you enter the config wlan custom-web global enable wlan_id command, the custom web authenticationconfiguration at the global level is used.NoteStep 7 Save your changes by entering this command:save configCisco Wireless LAN Controller Configuration Guide, Release 7.4       OL-28744-01 231Assigning Login, Login Failure, and Logout Pages per WLAN
   Cisco Wireless LAN Controller Configuration Guide, Release 7.4232 OL-28744-01  Assigning Login, Login Failure, and Logout Pages per WLAN
CHAPTER 24Configuring Wired Guest Access•Information About Wired Guest Access, page 233•Prerequisites for Configuring Wired Guest Access, page 234•Restrictions for Configuring Wired Guest Access, page 234•Configuring Wired Guest Access (GUI), page 235•Configuring Wired Guest Access (CLI), page 236•Supporting IPv6 Client Guest Access, page 238Information About Wired Guest AccessWired guest access enables guest users to connect to the guest access network from a wired Ethernet connectiondesignated and configured for guest access. Wired guest access ports might be available in a guest office orthrough specific ports in a conference room. Like wireless guest user accounts, wired guest access ports areadded to the network using the lobby ambassador feature.Wired guest access can be configured in a standalone configuration or in a dual-controller configuration thatuses both an anchor controller and a foreign controller. This latter configuration is used to further isolate wiredguest access traffic but is not required for deployment of wired guest access.Wired guest access ports initially terminate on a Layer 2 access switch or switch port configured with VLANinterfaces for wired guest access traffic. The wired guest traffic is then trunked from the access switch to acontroller. This controller is configured with an interface that is mapped to a wired guest access VLAN onthe access switch.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 forthe client are handled by the anchor controller.NoteYou can specify the amount of bandwidth allocated to a wired guest user in the network by configuringa QoS role and a bandwidth contract.NoteCisco Wireless LAN Controller Configuration Guide, Release 7.4        OL-28744-01 233
You can create a basic peer to peer WLAN ACL and apply it to the wired guest WLAN. This will not blockpeer to peer traffic and the guest users can still communicate with each other.Prerequisites for Configuring Wired Guest AccessTo configure wired guest access on a wireless network, you must perform the following:1Configure a dynamic interface (VLAN) for wired guest user access2Create a wired LAN for guest user access3Configure the controller4Configure the anchor controller (if terminating traffic on another controller)5Configure security for the guest LAN6Verify the configurationRestrictions for Configuring Wired Guest Access•Wired guest access interfaces must be tagged.•Wired guest access ports must be in the same Layer 2 network as the foreign controller.•Up to five wired guest access LANs can be configured on a controller. Also in a wired guest accessLAN, multiple anchors are supported.•Layer 3 web authentication and web passthrough are supported for wired guest access clients. Layer 2security is not supported.•Do not trunk a wired guest VLAN to multiple foreign controllers, as it might produce unpredictableresults.   Cisco Wireless LAN Controller Configuration Guide, Release 7.4234 OL-28744-01  Prerequisites for Configuring Wired Guest Access
Configuring Wired Guest Access (GUI)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.You can create up to five guest LANs, so the WLAN ID options are 1 through 5 (inclusive).NoteStep 13 Click Apply to commit your changes.Step 14 Select the Enabled check box for the Status parameter.Step 15 Web authentication (Web-Auth) is the default security policy. If you want to change this to web passthrough, choosethe Security tab after completing Step 16 and Step 17.Step 16 From the Ingress Interface drop-down list, choose the VLAN that you created in Step 3. This VLAN provides a pathbetween the wired guest client and the controller by way of the Layer 2 access switch.Step 17 From the Egress Interface drop-down list, choose the name of the interface. This WLAN provides a path out of thecontroller for wired guest client traffic.Step 18 If you want to change the authentication method (for example, from web authentication to web passthrough), chooseSecurity >Layer 3. The WLANs > Edit (Security > Layer 3) page appears.Step 19 From the Layer 3 Security drop-down list, choose one of the following:•None—Layer 3 security is disabled.•Web Authentication—Causes users to be prompted for a username and password when connecting to the wirelessnetwork. This is the default value.•Web Passthrough—Allows users to access the network without entering a username and password.There should not be a Layer 3 gateway on the guest wired VLAN, as this would bypass the webauthentication done through the controller.NoteStep 20 If you choose the Web Passthrough option, an Email Input check box appears. Select this check box if you want usersto 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 checkbox.Step 22 When the Web Auth Type drop-down list appears, choose one of the following options to define the web authenticationpages for wired guest users:Cisco Wireless LAN Controller Configuration Guide, Release 7.4       OL-28744-01 235Configuring Wired Guest Access (GUI)
•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 separatedrop-down lists appear for login, login failure, and logout page selection. You do not need to define a customizedpage for all three options. Choose None from the appropriate drop-down list if you do not want to display acustomized page for that option.These optional login, login failure, and logout pages are downloaded to the controller as webauth.tarfiles.Note•External—Redirects users to an external server for authentication. If you choose this option, you must also enterthe 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 AAA Servers and choose up to three RADIUSand LDAP servers using the drop-down lists.The RADIUS and LDAP external servers must already be configured in order to be selectable options on theWLANs > Edit (Security > AAA Servers) page. You can configure these servers on the RADIUS AuthenticationServers page and LDAP Servers page.NoteStep 24 To establish the priority in which the servers are contacted to perform web authentication as follows:The default order is local, RADIUS,LDAP.Note1Highlight the server type (local, RADIUS, or LDAP) that you want to be contacted first in the box next to the Upand Down buttons.2Click Up and Down until the desired server type is at the top of the box.3Click the <arrow to move the server type to the priority box on the left.4Repeat these steps to assign priority to the other servers.Step 25 Click Apply.Step 26 Click Save Configuration.Step 27 Repeat this process if a second (anchor) controller is being used in the network.Configuring Wired Guest Access (CLI)Step 1 Create a dynamic interface (VLAN) for wired guest user access by entering this command:config interface create interface_name vlan_idStep 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:config interface guest-lan interface_name {enable | disable}   Cisco Wireless LAN Controller Configuration Guide, Release 7.4236 OL-28744-01  Configuring Wired Guest Access (CLI)
This VLAN is later associated with the ingress interface created in Step 5.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_nameThe guest LAN ID must be a value between 1 and 5 (inclusive).To delete a wired guest LAN, enter the config guest-lan delete guest_lan_id command.NoteStep 5 Configure the wired guest VLAN’s ingress interface, which provides a path between the wired guest client and thecontroller by way of the Layer 2 access switch by entering this command:config guest-lan ingress-interface guest_lan_id interface_nameStep 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_nameIf 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 configmobility group anchor add {guest-lan guest_lan_id |wlan wlan_id} IP_address command for both controllers.NoteStep 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}Web authentication is the defaultsetting.NoteStep 8 Enable or disable a wired guest LAN by entering this command:config guest-lan {enable | disable} guest_lan_idStep 9 If you want wired guest users to log into a customized web login, login failure, or logout page, enter these commandsto 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.To use the controller’s default login failure page, enter the config guest-lan custom-web loginfailure-pagenone guest_lan_id command.Note•config guest-lan custom-web logout-page page_name guest_lan_id—Defines a web logout page.To use the controller’s default logout page, enter the config guest-lan custom-web logout-page noneguest_lan_id command.NoteStep 10 If you want wired guest users to be redirected to an external server before accessing the web login page, enter thiscommand to specify the URL of the external server:config guest-lan custom-web ext-webauth-url ext_web_url guest_lan_idStep 11 If you want to define the order in which local (controller) or external (RADIUS, LDAP) web authentication servers arecontacted, 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.All external servers must be preconfigured on the controller. You can configure them on the RADIUSAuthentication Servers page or the LDAP Servers page.NoteStep 12 Define the web login page for wired guest users by entering this command:Cisco Wireless LAN Controller Configuration Guide, Release 7.4       OL-28744-01 237Configuring Wired Guest Access (CLI)
config guest-lan custom-web webauth-type {internal |customized |external}guest_lan_idwhere••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 thiscommand:config guest-lan custom-web global disable guest_lan_idIf you enter the config guest-lan custom-web global enable guest_lan_id command, the custom webauthentication configuration at the global level is used.NoteStep 14 Save your changes by entering this command:save configInformation on the configured web authentication appears in both the show run-config and show running-configcommands.NoteStep 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}If internal web authentication is configured, the Web Authentication Type displays as internal rather than external(controller level) or customized (WLAN profile level).NoteStep 16 Display a summary of the local interfaces by entering this command:show interface summaryThe interface name of the wired guest LAN in this example is wired-guest and its VLAN ID is236.NoteDisplay detailed interface information by entering this command:show interface detailed interface_nameStep 17 Display the configuration of a specific wired guest LAN by entering this command:show guest-lan guest_lan_idEnter the show guest-lan summary command to see all wired guest LANs configured on the controller.NoteStep 18 Display the active wired guest LAN clients by entering this command:show client summary guest-lanStep 19 Display detailed information for a specific client by entering this command:show client detail client_macSupporting IPv6 Client Guest AccessThe client is in WebAuth Required state until the client is authenticated. The controller intercepts both IPv4and IPv6 traffic in this state and redirects it to the virtual IP address of the controller. Once authenticated, theuser's MAC address is moved to the run state and both IPv4 and IPv6 traffic is allowed to pass.   Cisco Wireless LAN Controller Configuration Guide, Release 7.4238 OL-28744-01  Supporting IPv6 Client Guest Access
In order to support the redirection of IPv6-only clients, the controller automatically creates an IPv6 virtualaddress based on the IPv4 virtual address configured on the controller. The virtual IPv6 address follows theconvention of [::ffff:<virtual IPv4 address>]. For example, a virtual IP address of 192.0.2.1 would translateinto [::ffff:192.0.2.1]. For an IPv6 captive portal to be displayed, the user must request an IPv6 resolvableDNS entry such as ipv6.google.com which returns a DNSv6 (AAAA) record.Cisco Wireless LAN Controller Configuration Guide, Release 7.4       OL-28744-01 239Supporting IPv6 Client Guest Access
   Cisco Wireless LAN Controller Configuration Guide, Release 7.4240 OL-28744-01  Supporting IPv6 Client Guest Access
CHAPTER 25Troubleshooting•Interpreting LEDs, page 241•System Messages, page 242•Viewing System Resources, page 245•Using the CLI to Troubleshoot Problems, page 246•Configuring System and Message Logging, page 247•Viewing Access Point Event Logs, page 254•Uploading Logs and Crash Files, page 255•Uploading Core Dumps from the Controller, page 257•Uploading Packet Capture Files, page 260•Monitoring Memory Leaks, page 263•Troubleshooting CCXv5 Client Devices, page 264•Using the Debug Facility, page 274•Configuring Wireless Sniffing, page 279•Troubleshooting Access Points Using Telnet or SSH_old, page 281•Debugging the Access Point Monitor Service, page 283•Troubleshooting OfficeExtend Access Points, page 284Interpreting LEDsInformation About Interpreting LEDsThis section describes how to interpret controller LEDs and lightweight access point LEDs.Cisco Wireless LAN Controller Configuration Guide, Release 7.4        OL-28744-01 241
Interpreting Controller LEDsSee the quick start guide for your specific controller for a description of the LED patterns. See the list ofcontrollers and the respective documentation at http://www.cisco.com/en/US/products/hw/wireless/index.html.Interpreting Lightweight Access Point LEDsSee the quick start guide or hardware installation guide for your specific access point for a description of theLED patterns. See the list of access points and the respective documentation at http://www.cisco.com/en/US/products/hw/wireless/index.html.System MessagesInformation About System MessagesThis table lists some common system messages and their descriptions. For a complete list of system messages,see the Cisco Wireless LAN Controller System Message Guide, Release 7.0.Table 6: System Messages and DescriptionsDescriptionError MessageA client is sending an association request on a security-enabledWLAN with the protected bit set to 0 (in the Capability field ofthe association request). As designed, the controller rejects theassociation request, and the client sees an association failure.apf_utils.c 680: Received a CIF fieldwithout the protected bit set from mobilexx:xx:xx:xx:xx:xxThe controller’s network processing unit (NPU) sends a timeoutmessage to the central processing unit (CPU) indicating that aparticular client has timed out or aged out. This situation typicallyoccurs when the CPU has removed a wireless client from itsinternal database but has not notified the NPU. Because the clientremains in the NPU database, it ages out on the networkprocessor and notifies the CPU. The CPU finds the client thatis not present in its database and then sends this message.dtl_arp.c 480: Got an idle-timeout messagefrom an unknown client xx:xx:xx:xx:xx:xxThe client may have intentionally terminated usage or may haveexperienced a service disruption.STATION_DISASSOCIATEThe client may have intentionally terminated usage or thismessage could indicate an authentication issue.STATION_DEAUTHENTICATECheck disable, key mismatch, or other configuration issues.STATION_AUTHENTICATION_FAILCheck load on the Cisco radio or signal quality issues.STATION_ASSOCIATE_FAILThe associated lightweight access point is now managed by thiscontroller.LRAD_ASSOCIATED   Cisco Wireless LAN Controller Configuration Guide, Release 7.4242 OL-28744-01  System Messages
DescriptionError MessageThe lightweight access point may have associated to a differentcontroller or may have become completely unreachable.LRAD_DISASSOCIATEDThe lightweight access point is operational; no action required.LRAD_UPThe lightweight access point may have a problem or isadministratively disabled.LRAD_DOWNThe Cisco radio is UP.LRADIF_UPThe Cisco radio may have a problem or is administrativelydisabled.LRADIF_DOWNThe client density may have exceeded system capacity.LRADIF_LOAD_PROFILE_FAILEDThe non-802.11 noise has exceeded the configured threshold.LRADIF_NOISE_PROFILE_FAILED802.11 interference has exceeded threshold on channel; checkchannel assignments.LRADIF_INTERFERENCE_PROFILE_FAILEDA possible coverage hole has been detected. Check thelightweight access point history to see if it is a common problemand add lightweight access points if necessary.LRADIF_COVERAGE_PROFILE_FAILEDThe load is now within threshold limits.LRADIF_LOAD_PROFILE_PASSEDThe detected noise is now less than threshold.LRADIF_NOISE_PROFILE_PASSEDThe detected interference is now less than threshold.LRADIF_INTERFERENCE_PROFILE_PASSEDThe number of clients receiving a poor signal are withinthreshold.LRADIF_COVERAGE_PROFILE_PASSEDInformational message.LRADIF_CURRENT_TXPOWER_CHANGEDInformational message.LRADIF_CURRENT_CHANNEL_CHANGEDInformational message.LRADIF_RTS_THRESHOLD_CHANGEDInformational message.LRADIF_ED_THRESHOLD_CHANGEDInformational message.LRADIF_FRAGMENTATION_THRESHOLD_CHANGEDInformational message.RRM_DOT11_A_GROUPING_DONEInformational message.RRM_DOT11_B_GROUPING_DONEMay be a security issue. Use maps and trends to investigate.ROGUE_AP_DETECTEDCisco Wireless LAN Controller Configuration Guide, Release 7.4       OL-28744-01 243System Messages
DescriptionError MessageA detected rogue access point has timed out. The unit mighthave shut down or moved out of the coverage area.ROGUE_AP_REMOVEDThe current number of active rogue access points has exceededsystem threshold.AP_MAX_ROGUE_COUNT_EXCEEDEDPositive confirmation message.LINK_UPA port may have a problem or is administratively disabled.LINK_DOWNA port may have a problem or is administratively disabled.LINK_FAILUREAn attempted security breech has occurred. Investigate.AUTHENTICATION_FAILUREInformational message.STP_NEWROOTInformational message.STP_TOPOLOGY_CHANGECheck WLAN IPsec configuration.IPSEC_ESP_AUTH_FAILURECheck for an attempt to spoof an IP address.IPSEC_ESP_REPLAY_FAILURECheck for a IPsec configuration mismatch between WLAN andclient.IPSEC_ESP_POLICY_FAILUREInformational message.IPSEC_ESP_INVALID_SPICheck for a IPsec configuration mismatch between WLAN andclient.IPSEC_OTHER_POLICY_FAILURECheck for a IPsec IKE configuration mismatch between WLANand client.IPSEC_IKE_NEG_FAILURECheck for a IPsec IKE configuration mismatch between WLANand client.IPSEC_SUITE_NEG_FAILUREInformational message.IPSEC_INVALID_COOKIEThe maximum number of supported Cisco radios has beenexceeded. Check for a controller failure in the same Layer 2network or add another controller.RADIOS_EXCEEDEDCheck fan, air conditioning, and/or other cooling arrangements.SENSED_TEMPERATURE_HIGHCheck room temperature and/or other reasons for lowtemperature.SENSED_TEMPERATURE_LOWReplace temperature sensor as soon as possible.TEMPERATURE_SENSOR_FAILURE   Cisco Wireless LAN Controller Configuration Guide, Release 7.4244 OL-28744-01  System Messages
DescriptionError MessageThe temperature sensor is operational.TEMPERATURE_SENSOR_CLEARCheck ports; a possible serious failure has been detected.POE_CONTROLLER_FAILUREThe current number of active rogue access points has exceededsystem threshold.MAX_ROGUE_COUNT_EXCEEDEDThe controller is responding to SNMP polls.SWITCH_UPThe controller is not responding to SNMP polls; check controllerand SNMP settings.SWITCH_DOWNCheck network connectivity between RADIUS and the controller.RADIUS_SERVERS_FAILEDThe running configuration has been saved to flash; it will beactive after a reboot.CONFIG_SAVEDAnother user with the same username has logged in.MULTIPLE_USERSMonitor controller temperature to avoid overheating.FAN_FAILURECheck for a power-supply malfunction.POWER_SUPPLY_CHANGEThe controller may have been rebooted.COLD_STARTThe controller may have been rebooted.WARM_STARTViewing System ResourcesInformation About Viewing System ResourcesYou can determine the amount of system resources being used by the controller. Specifically, you can viewthe current controller CPU usage, system buffers, and web server buffers.The Cisco 5500 Series Controllers have multiple CPUs, so you can view individual CPU usage. For eachCPU, you can see the percentage of the CPU in use and the percentage of the CPU time spent at the interruptlevel (for example, 0%/3%).Cisco Wireless LAN Controller Configuration Guide, Release 7.4       OL-28744-01 245Viewing System Resources
Viewing System Resources (GUI)On the controller GUI, choose Management > Tech Support > System Resource Information. The SystemResource Information page appears.Figure 24: System Resource Information PageViewing System Resources (CLI)On the controller CLI, enter these commands:•show cpuWhere the first number is the CPU percentage that the controller spent on the user application and thesecond number is the CPU percentage that the controller spent on the OS services.•show tech-supportUsing the CLI to Troubleshoot ProblemsIf you experience any problems with your controller, you can use the commands in this section to gatherinformation and debug issues.•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 preventingother tasks from being performed.The Priority field shows two values: 1) the original priority of the task that was created by the actualfunction 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 modeoperation, 2) the amount of time for which the task is scheduled in system mode operation, and 3) whetherthe task is being watched by the reaper task monitor (indicated by a “T”). If the task is being watched   Cisco Wireless LAN Controller Configuration Guide, Release 7.4246 OL-28744-01  Using the CLI to Troubleshoot Problems
by the reaper task monitor, this field also shows the timeout value (in seconds) before which the taskneeds to alert the task monitor.If you want to see the total CPU usage as a percentage, enter the show cpu command.Note•show process memory—Shows the allocation and deallocation of memory from various processes inthe 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 actualfunction 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 aparticular 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 modeoperation, 2) the amount of time for which the task is scheduled in system mode operation, and 3) whetherthe task is being watched by the reaper task monitor (indicated by a “T”). If the task is being watchedby the reaper task monitor, this field also shows the timeout value (in seconds) before which the taskneeds to alert the task monitor.•show tech-support—Shows an array of information related to the state of the system, including thecurrent configuration, last crash file, CPU utilization, and memory utilization.•show run-config—Shows the complete configuration of the controller. To exclude access pointconfiguration settings, use the show run-config no-ap command.If you want to see the passwords in clear text, enter the config passwd-cleartext enable command. Toexecute this command, you must enter an admin password. This command is valid only for this particularsession. It is not saved following a reboot.Note•show run-config commands—Shows the list of configured commands on the controller. This commandshows only values configured by the user. It does not show system-configured default values.Configuring System and Message LoggingInformation About System and Message LoggingSystem logging allows controllers to log their system events to up to three remote syslog servers. The controllersends a copy of each syslog message as it is logged to each syslog server configured on the controller. Beingable to send the syslog messages to multiple servers ensures that the messages are not lost due to the temporaryunavailability of one syslog server. Message logging allows system messages to be logged to the controllerbuffer or console.Cisco Wireless LAN Controller Configuration Guide, Release 7.4       OL-28744-01 247Configuring System and Message Logging
Configuring System and Message Logging (GUI)Step 1 Choose Management > Logs > Config. The Syslog Configuration page appears.Figure 25: Syslog Configuration PageStep 2 In the Syslog Server IP Address text box, enter the IP address of the server to which to send the syslog messages andclick Add. You can add up to three syslog servers to the controller. The list of syslog servers that have already beenadded to the controller appears below this text box.If you want to remove a syslog server from the controller, click Remove to the right of the desiredserver.NoteStep 3 To set the severity level for filtering syslog messages to the syslog servers, choose one of the following options fromthe Syslog Level drop-down list:•Emergencies = Severity level 0•Alerts = Severity level 1 (default value)•Critical = Severity level 2•Errors = Severity level 3•Warnings = Severity level 4•Notifications = Severity level 5•Informational = Severity level 6•Debugging = Severity level 7   Cisco Wireless LAN Controller Configuration Guide, Release 7.4248 OL-28744-01  Configuring System and Message Logging
If you set a syslog level, only those messages whose severity is equal to or less than that level are sent to the syslogservers. For example, if you set the syslog level to Warnings (severity level 4), only those messages whose severity isbetween 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 theSyslog 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•Local Use 5 = Facility level 22•Local Use 5 = Facility level 23Step 5 Click Apply.Step 6 To set the severity level for logging messages to the controller buffer and console, choose one of the following optionsfrom both the Buffered Log Level and Console Log Level drop-down lists:•Emergencies = Severity level 0•Alerts = Severity level 1•Critical = Severity level 2Cisco Wireless LAN Controller Configuration Guide, Release 7.4       OL-28744-01 249Configuring System and Message Logging
•Errors = Severity level 3 (default value)•Warnings = Severity level 4•Notifications = Severity level 5•Informational = Severity level 6•Debugging = Severity level 7•Disable—This option is available only for Console Log level. Select this option to disable console logging.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 between0 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 defaultvalue 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.Viewing Message Logs (GUI)To view message logs using the controller GUI, choose Management > Logs > Message Logs. The MessageLogs page appears.Figure 26: Message Logs Page   Cisco Wireless LAN Controller Configuration Guide, Release 7.4250 OL-28744-01  Configuring System and Message Logging
To clear the current message logs from the controller, click Clear.NoteConfiguring System and Message Logging (CLI)Step 1 Enable system logging and set the IP address of the syslog server to which to send the syslog messages by entering thiscommand:config logging syslog host server_IP_addressYou can add up to three syslog servers to the controller.To remove a syslog server from the controller by entering this command: config logging syslog hostserver_IP_address deleteNoteStep 2 Set the severity level for filtering syslog messages to the syslog server by entering this command:config logging syslog level severity_levelwhere 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 7As an alternative, you can enter a number from 0 through 7 for the severity_level parameter.NoteIf you set a syslog level, only those messages whose severity is equal to or less than that level are sent to thesyslog server. For example, if you set the syslog level to Warnings (severity level 4), only those messages whoseseverity is between 0 and 4 are sent to the syslog server.NoteStep 3 Set the severity level for filtering syslog messages for a particular access point or for all access points by entering thiscommand: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 4Cisco Wireless LAN Controller Configuration Guide, Release 7.4       OL-28744-01 251Configuring System and Message Logging
•notifications = Severity level 5•informational = Severity level 6•debugging = Severity level 7If you set a syslog level, only those messages whose severity is equal to or less than that level are sent tothe access point. For example, if you set the syslog level to Warnings (severity level 4), only those messageswhose severity is between 0 and 4 are sent to the access point.NoteStep 4 Set the facility for outgoing syslog messages to the syslog server by entering this command:config logging syslog facility facility_codewhere facility_code 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.   Cisco Wireless LAN Controller Configuration Guide, Release 7.4252 OL-28744-01  Configuring System and Message Logging
•uucp = Unix-to-Unix copy system. Facility level = 8.Step 5 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_levelwhere 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 7As an alternative, you can enter a number from 0 through 7 for the severity_level parameter.NoteIf you set a logging level, only those messages whose severity is equal to or less than that level are logged bythe controller. For example, if you set the logging level to Warnings (severity level 4), only those messageswhose severity is between 0 and 4 are logged.NoteStep 6 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 7 To cause the controller to include information about the source file in the message logs or to prevent the controller fromdisplaying this information by entering this command:config logging fileinfo {enable | disable}The default value is enabled.Step 8 Configure the controller to include process information in the message logs or to prevent the controller from displayingthis information by entering this command:config logging procinfo {enable |disable}The default value is disabled.Step 9 Configure the controller to include traceback information in the message logs or to prevent the controller from displayingthis information by entering this command:config logging traceinfo {enable | disable}The default value is disabled.Cisco Wireless LAN Controller Configuration Guide, Release 7.4       OL-28744-01 253Configuring System and Message Logging
Step 10 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.Step 11 Save your changes by entering this command:save configViewing System and Message Logs (CLI)To see the logging parameters and buffer contents, enter this command:show loggingViewing Access Point Event LogsInformation About Access Point Event LogsAccess points log all system messages (with a severity level greater than or equal to notifications) to the accesspoint event log. The event log can contain up to 1024 lines of messages, with up to 128 characters per line.When the event log becomes filled, the oldest message is removed to accommodate a new event message.The event log is saved in a file on the access point flash, which ensures that it is saved through a reboot cycle.To minimize the number of writes to the access point flash, the contents of the event log are written to theevent log file during normal reload and crash scenarios only.Viewing Access Point Event Logs (CLI)Use these CLI commands to view or clear the access point event log from the controller:•To see the contents of the event log file for an access point that is joined to the controller, enter thiscommand:show ap eventlog Cisco_APInformation similar to the following appears:AP event log download has been initiatedWaiting for download to completeAP event log download completed.======================= AP Event log Contents =====================*Sep 22 11:44:00.573: %CAPWAP-5-CHANGED: CAPWAP changed state to IMAGE*Sep 22 11:44:01.514: %LINEPROTO-5-UPDOWN: Line protocol on Interface Dot11Radio0,   Cisco Wireless LAN Controller Configuration Guide, Release 7.4254 OL-28744-01  Viewing Access Point Event Logs
changed state to down*Sep 22 11:44:01.519: %LINEPROTO-5-UPDOWN: Line protocol on Interface Dot11Radio1,changed state to down*Sep 22 11:44:53.539: *** Access point reloading. Reason: NEW IMAGE DOWNLOAD ****Mar 1 00:00:39.078: %CAPWAP-3-ERRORLOG: Did not get log server settings from DHCP.*Mar 1 00:00:42.142: %CDP_PD-4-POWER_OK: Full power - NEGOTIATED inline power source*Mar 1 00:00:42.151: %LINK-3-UPDOWN: Interface Dot11Radio1, changed state to up*Mar 1 00:00:42.158: %LINK-3-UPDOWN: Interface Dot11Radio0, changed state to up*Mar 1 00:00:43.143: %LINEPROTO-5-UPDOWN: Line protocol on Interface Dot11Radio1,changed state to up*Mar 1 00:00:43.151: %LINEPROTO-5-UPDOWN: Line protocol on Interface Dot11Radio0,changed state to up*Mar 1 00:00:48.078: %CAPWAP-3-ERRORLOG: Could Not resolve CISCO-CAPWAP-CONTROLLER*Mar 1 00:01:42.144: %CDP_PD-4-POWER_OK: Full power - NEGOTIATED inline power source*Mar 1 00:01:48.121: %CAPWAP-3-CLIENTERRORLOG: Set Transport Address: no more AP managerIP addresses remain*Mar 1 00:01:48.122: %CAPWAP-5-CHANGED: CAPWAP changed state to JOIN*Mar 1 00:01:48.122: %LINK-5-CHANGED: Interface Dot11Radio0, changed state toadministratively down*Mar 1 00:01:48.122: %LINK-5-CHANGED: Interface Dot11Radio1, changed state toadministratively down•To delete the existing event log and create an empty event log file for a specific access point or for allaccess points joined to the controller, enter this command:clear ap-eventlog {specific Cisco_AP |all}Uploading Logs and Crash FilesPrerequisites to Upload Logs and Crash Files•Follow the instructions in this section to upload logs and crash files from the controller. However, beforeyou begin, ensure you have a TFTP or FTP server available for the file upload. Follow these guidelineswhen 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 subnetas the service port because the service port is not routable, or you must create static routes on thecontroller.◦If you are uploading through the distribution system network port, the TFTP or FTP server can beon 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 Infrastructurebecause the Prime Infrastructure built-in TFTP or FTP server and the third-party TFTP or FTPserver require the same communication port.Uploading Logs and Crash Files (GUI)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 LogCisco Wireless LAN Controller Configuration Guide, Release 7.4       OL-28744-01 255Uploading Logs and Crash Files
•Message Log•Trap Log•Crash FileStep 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:1In the Server Login Username text box, enter the FTP server login name.2In the Server Login Password text box, enter the FTP server login password.3In the Server Port Number text box, enter the port number of the FTP server. The default value for the server portis 21.Step 8 Click Upload to upload the log or crash file from the controller. A message appears indicating the status of the upload.Uploading Logs and Crash Files (CLI)Step 1 To transfer the file from the controller to a server, enter this command:transfer upload mode {tftp |ftp |sftp}Step 2 To specify the type of file to be uploaded, enter this command:transfer upload datatype datatypewhere datatype is one of the following options:•crashfile—Uploads the system’s crash file.•errorlog—Uploads the system’s error log.•panic-crash-file—Uploads the kernel panic information if a kernel panic occurs.•systemtrace—Uploads the system’s trace file.•traplog—Uploads the system’s trap log.   Cisco Wireless LAN Controller Configuration Guide, Release 7.4256 OL-28744-01  Uploading Logs and Crash Files
•watchdog-crash-file—Uploads the console dump resulting from a software-watchdog-initiated reboot of thecontroller following a crash. The software watchdog module periodically checks the integrity of the internal softwareand makes sure that the system does not stay in an inconsistent or nonoperational state for a long period of time.Step 3 To specify the path to the file, enter these commands:•transfer upload serverip server_ip_address•transfer upload path server_path_to_file•transfer upload filename filenameStep 4 If you are using an FTP server, also enter these commands:•transfer upload username username•transfer upload password password•transfer upload port portThe default value for the port parameter is21.NoteStep 5 To see the updated settings, enter this command:transfer upload startStep 6 When prompted to confirm the current settings and start the software upload, answer y.Uploading Core Dumps from the ControllerInformation About Uploading Core Dumps from the ControllerTo help troubleshoot controller crashes, you can configure the controller to automatically upload its core dumpfile to an FTP server after experiencing a crash. You cannot upload the core dump file directly to an FTP orTFTP server but you can upload a crash file to an FTP or TFTP server. The controllers save the core dumpfile to flash memory following a crash.Cisco Wireless LAN Controller Configuration Guide, Release 7.4       OL-28744-01 257Uploading Core Dumps from the Controller
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.Figure 27: Core Dump PageStep 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-downlist.Step 4 In the IP Address text box, enter the IP address of the FTP server.The controller must be able to reach the FTPserver.NoteStep 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:   Cisco Wireless LAN Controller Configuration Guide, Release 7.4258 OL-28744-01  Uploading Core Dumps from the Controller
config coredump ftp server_ip_address filenamewhere•server_ip_address is the IP address of the FTP server to which the controller sends its core dump file.The controller must be able to reach the FTPserver.Note•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_passwordStep 4 To save your changes, enter this command:save configStep 5 To see a summary of the controller’s core dump file, enter this command:Example:Information similar to the following appears:show coredump summaryInformation similar to the following appears:Core Dump is enabledFTP Server IP.................................... 10.10.10.17FTP Filename..................................... file1FTP Username..................................... ftpuserFTP Password.................................. *********Uploading Core Dumps from Controller to a Server (CLI)Step 1 To see information about the core dump file in flash memory, enter this command:show coredump summaryInformation similar to the following appears:Core Dump is disabledCore Dump file is saved on flashSw Version.................................... 6.0.83.0Time Stamp.................................... Wed Feb 4 13:23:11 2009File Size..................................... 9081788File Name Suffix........................... filename.gzCisco Wireless LAN Controller Configuration Guide, Release 7.4       OL-28744-01 259Uploading Core Dumps from the Controller
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 filenameAfter the file is uploaded, it ends with a .gz suffix. If desired, you can upload the same core dump filemultiple times with different names to different servers.NoteStep 3 If you are using an FTP server, also enter these commands:•transfer upload username usernametransfer upload password password•transfer upload port portThe default value for the port parameter is21.NoteStep 4 To view the updated settings, enter this command:transfer upload startStep 5 When prompted to confirm the current settings and start the software upload, answer y.Uploading Packet Capture FilesInformation About Uploading Packet Capture FilesWhen a Cisco 5500 Series Controller’s data plane crashes, it stores the last 50 packets that the controllerreceived in flash memory. This information can be useful in troubleshooting the crash.When a crash occurs, the controller generates a new packet capture file (*.pcap) file, and a message similarto the following appears in the controller crash file:Last 5 packets processed at each core are stored in"last_received_pkts.pcap" captured file.- Frame 36,38,43,47,49, processed at core #0.- Frame 14,27,30,42,45, processed at core #1.- Frame 15,18,20,32,48, processed at core #2.- Frame 11,29,34,37,46, processed at core #3.- Frame 7,8,12,31,35, processed at core #4.- Frame 21,25,39,41,50, processed at core #5.- Frame 16,17,19,22,33, processed at core #6.- Frame 6,10,13,23,26, processed at core #7.- Frame 9,24,28,40,44, processed at core #8.- Frame 1,2,3,4,5, processed at core #9.   Cisco Wireless LAN Controller Configuration Guide, Release 7.4260 OL-28744-01  Uploading Packet Capture Files
You can use the controller GUI or CLI to upload the packet capture file from the controller. You can then useWireshark or another standard packet capture tool to view and analyze the contents of the file.This figure shows a sample output of the packet capture in Wireshark.Figure 28: Sample Output of Packet Capture File in WiresharkRestrictions for Uploading Packet Capture Files•Only Cisco 5500 Series Controllers generate packet capture files. This feature is not available on othercontroller platforms.•Ensure that you have a TFTP or FTP server available for the file upload. Follow these guidelines whensetting up a TFTP or FTP server:◦If you are uploading through the service port, the TFTP or FTP server must be on the same subnetas the service port because the service port is not routable, or you must create static routes on thecontroller.◦If you are uploading through the distribution system network port, the TFTP or FTP server can beon 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 Infrastructurebecause the Prime Infrastructure built-in TFTP or FTP server and the third-party TFTP or FTPserver require the same communication port.Cisco Wireless LAN Controller Configuration Guide, Release 7.4       OL-28744-01 261Uploading Packet Capture Files
Uploading Packet Capture Files (GUI)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. Thedefault 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 thatwere received by the controller.Uploading Packet Capture Files (CLI)Step 1 Log on to the controller CLI.Step 2 Enter the transfer upload mode {tftp |ftp |sftp} command.Step 3 Enter the transfer upload datatype packet-capture command.Step 4 Enter the transfer upload serverip server-ip-address command.Step 5 Enter the transfer upload path server-path-to-file command.Step 6 Enter the transfer upload filename last_received_pkts.pcap command.Step 7 If you are using an FTP server, enter these commands:•transfer upload username username•transfer upload password password•transfer upload port portThe default value for the port parameter is21.Note   Cisco Wireless LAN Controller Configuration Guide, Release 7.4262 OL-28744-01  Uploading Packet Capture Files
Step 8 Enter the transfer upload start command to see the updated settings and then answer y when prompted to confirm thecurrent settings and start the upload process. This example shows the upload command output:Step 9 Use Wireshark or another standard packet capture tool to open the packet capture file and see the last 50 packets thatwere received by the controller.Monitoring Memory LeaksThis section provides instructions for troubleshooting hard-to-solve or hard-to-reproduce memory problems.The commands in this section can be disruptive to your system and should be run only when you areadvised to do so by the Cisco Technical Assistance Center (TAC).CautionMonitoring Memory Leaks (CLI)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.Your changes are not saved across reboots. After the controller reboots, it uses the default setting for this feature.NoteStep 2 If you suspect that a memory leak has occurred, enter this command to configure the controller to perform an auto-leakanalysis between two memory thresholds (in kilobytes):config memory monitor leaks low_thresh high_threshIf the free memory is lower than the low_thresh threshold, the system crashes, generating a crash file. The default valuefor 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-analysismode. After the free memory reaches a level lower than the specified high_thresh threshold, the process of tracking andfreeing memory allocation begins. As a result, the debug memory events enable command shows all allocations andfrees, and the show memory monitor detail command starts to detect any suspected memory leaks. The default valuefor this parameter is 30000 kilobytes.Step 3 To see a summary of any discovered memory issues, enter this command:show memory monitorInformation similar to the following appears:Memory Leak Monitor Status:low_threshold(10000), high_threshold(30000), current status(disabled)-------------------------------------------Memory Error Monitor Status:Cisco Wireless LAN Controller Configuration Guide, Release 7.4       OL-28744-01 263Monitoring Memory Leaks
Crash-on-error flag currently set to (disabled)No memory error detected.Step 4 To see the details of any memory leaks or corruption, enter this command:show memory monitor detailInformation similar to the following appears:Memory error detected. Details:------------------------------------------------- Corruption detected at pmalloc entry address: (0x179a7ec0)- Corrupt entry:headerMagic(0xdeadf00d),trailer(0xabcd),poison(0xreadceef),entrysize(128),bytes(100),thread(Unknown task name, task id = (332096592)),file(pmalloc.c),line(1736),time(1027)Previous 1K memory dump from error location.------------------------------------------------(179a7ac0): 00000000 00000000 00000000 ceeff00d readf00d 00000080 00000000 00000000(179a7ae0): 17958b20 00000000 1175608c 00000078 00000000 readceef 179a7afc 00000001(179a7b00): 00000003 00000006 00000001 00000004 00000001 00000009 00000009 0000020d(179a7b20): 00000001 00000002 00000002 00000001 00000004 00000000 00000000 5d7b9aba(179a7b40): cbddf004 192f465e 7791acc8 e5032242 5365788c a1b7cee6 00000000 00000000(179a7b60): 00000000 00000000 00000000 00000000 00000000 ceeff00d readf00d 00000080(179a7b80): 00000000 00000000 17958dc0 00000000 1175608c 00000078 00000000 readceef(179a7ba0): 179a7ba4 00000001 00000003 00000006 00000001 00000004 00000001 00003763(179a7bc0): 00000002 00000002 00000010 00000001 00000002 00000000 0000001e 00000013(179a7be0): 0000001a 00000089 00000000 00000000 000000d8 00000000 00000000 17222194(179a7c00): 1722246c 1722246c 00000000 00000000 00000000 00000000 00000000 ceeff00d(179a7c20): readf00d 00000080 00000000 00000000 179a7b78 00000000 1175608c 00000078Step 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}Troubleshooting CCXv5 Client DevicesInformation About Troubleshooting CCXv5 Client DevicesThe controller supports three features designed to help troubleshoot communication problems with CCXv5clients: diagnostic channel, client reporting, and roaming and real-time diagnostics.Restrictions for CCXv5 Client DevicesDiagnostic channel, client reporting, and roaming and real-time diagnostics features are supported only onCCXv5 clients. They are not supported for use with non-CCX clients or with clients running an earlier versionof CCX.   Cisco Wireless LAN Controller Configuration Guide, Release 7.4264 OL-28744-01  Troubleshooting CCXv5 Client Devices
Configuring Diagnostic ChannelYou can choose a diagnostic channel to troubleshoot why the client is having communication problems witha WLAN. You can test the client and access points to identify the difficulties that the client is experiencingand allow corrective measures to be taken to make the client operational on the network. You can use thecontroller GUI or CLI to enable the diagnostic channel, and you can use the controller CLI to run the diagnostictests.We recommend that you enable the diagnostic channel feature only for nonanchored SSIDs that use themanagement interface.NoteConfiguring the Diagnostic Channel (GUI)Step 1 Choose WLANs to open the WLANs page.Step 2 Create a new WLAN or click the ID number of an existing WLAN.We recommend that you create a new WLAN on which to run the diagnostictests.NoteStep 3 When the WLANs > Edit page appears, choose the Advanced tab to open the WLANs > Edit (Advanced) page.Figure 29: WLANs > Edit (Advanced) PageStep 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.You can use the CLI to initiate diagnostic tests on theclient.NoteStep 5 Click Apply to commit your changes.Step 6 Click Save Configuration to save your changes.Cisco Wireless LAN Controller Configuration Guide, Release 7.4       OL-28744-01 265Troubleshooting CCXv5 Client Devices
Configuring the Diagnostic Channel (CLI)Step 1 To enable diagnostic channel troubleshooting on a particular WLAN, enter this command:config wlan diag-channel {enable |disable}wlan_idStep 2 To verify that your change has been made, enter this command:show wlan wlan_idInformation similar to the following appears:WLAN Identifier.................................. 1Profile Name..................................... employee1Network Name (SSID).............................. employeeStatus........................................... DisabledMAC Filtering.................................... DisabledBroadcast SSID................................... EnabledAAA Policy Override.............................. DisabledNumber of Active Clients......................... 0Exclusionlist Timeout............................ 60 secondsSession Timeout.................................. InfinityInterface........................................ virtualWLAN ACL......................................... unconfiguredDHCP Server...................................... DefaultDHCP Address Assignment Required................. DisabledQuality of Service............................... Silver (best effort)WMM.............................................. DisabledCCX - AironetIe Support.......................... EnabledCCX - Gratuitous ProbeResponse (GPR)............. DisabledCCX - 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_addressThis test does not require the client to use the diagnosticchannel.NoteStep 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_addressThis test does not require the client to use the diagnosticchannel.NoteStep 5 To send a request to the client to perform the DNS server IP address ping test, enter this command:config client ccx dns-ping client_mac_addressThis test does not require the client to use the diagnosticchannel.NoteStep 6 To send a request to the client to perform the DNS name resolution test to the specified host name, enter this command:config client ccx dns-resolve client_mac_address host_nameThis test does not require the client to use the diagnosticchannel.Note   Cisco Wireless LAN Controller Configuration Guide, Release 7.4266 OL-28744-01  Troubleshooting CCXv5 Client Devices
Step 7 To send a request to the client to perform the association test, enter this command:config client ccx test-association client_mac_address ssid bssid {802.11a | 802.11b | 802.11g}channelStep 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}channelStep 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_idThe profile_id should be from one of the client profiles for which client reporting is enabled.Users are redirected back to the parent WLAN, not to any other profile. The only profile shown is the user’sparent profile. Note however that parent WLAN profiles can have one child diagnostic WLAN.NoteStep 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_addressOnly 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_addressStep 11 To send a message to the client, enter this command:Example:config client ccx send-message client_mac_address message_idwhere message_id is one of the following:•1 = The SSID is invalid.•2 = The network settings are invalid.•3 = There is a WLAN credibility mismatch.•4 = The user credentials are incorrect.•5 = Please call support.•6 = The problem is resolved.•7 = The problem has not been resolved.•8 = Please try again later.•9 = Please correct the indicated problem.•10 = Troubleshooting is refused by the network.•11 = Retrieving client reports.•12 = Retrieving client logs.•13 = Retrieval complete.•14 = Beginning association test.•15 = Beginning DHCP test.Cisco Wireless LAN Controller Configuration Guide, Release 7.4       OL-28744-01 267Troubleshooting CCXv5 Client Devices
•16 = Beginning network connectivity test.•17 = Beginning DNS ping test.•18 = Beginning name resolution test.•19 = Beginning 802.1X authentication test.•20 = Redirecting client to a specific profile.•21 = Test complete.•22 = Test passed.•23 = Test failed.•24 = Cancel diagnostic channel operation or select a WLAN profile to resume normal operation.•25 = Log retrieval refused by the client.•26 = Client report retrieval refused by the client.•27 = Test request refused by the client.•28 = Invalid network (IP) setting.•29 = There is a known outage or problem with the network.•30 = Scheduled maintenance period.•31 = The WLAN security method is not correct.•32 = The WLAN encryption method is not correct.•33 = The WLAN authentication method is not correct.Step 12 To see the status of the last test, enter this command:show client ccx last-test-status client_mac_addressInformation similar to the following appears for the default gateway ping test:Test Type........................................ Gateway Ping TestTest Status...................................... Pending/Success/TimeoutDialog Token..................................... 15Timeout.......................................... 15000 msRequest Time..................................... 1329 seconds since system bootStep 13 To see the status of the last test response, enter this command:show client ccx last-response-status client_mac_addressInformation similar to the following appears for the 802.1X authentication test:Test Status...................................... SuccessResponse Dialog Token............................ 87Response Status.................................. SuccessfulResponse Test Type............................... 802.1x Authentication TestResponse Time.................................... 3476 seconds since system bootStep 14 To see the results from the last successful diagnostics test, enter this command:show client ccx results client_mac_addressInformation similar to the following appears for the 802.1X authentication test:   Cisco Wireless LAN Controller Configuration Guide, Release 7.4268 OL-28744-01  Troubleshooting CCXv5 Client Devices
dot1x Complete................................... SuccessEAP Method....................................... *1,Host OS Login Credentialsdot1x Status.................................. 255Step 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_addressInformation similar to the following appears:LOG Frames:Frame Number:.................................... 1Last Frame Number:............................... 1120Direction:....................................... 1Timestamp:....................................... 0d 00h 50m 39s 863954usFrame Length:.................................... 197Frame 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 ...@......P.....000000b0: 00 03 a4 00 00 27 a4 00 00 42 43 5e 00 62 32 2f .....'...BC^.b2/LOG Frames:Frame Number:.................................... 2Last Frame Number:............................... 1120Direction:....................................... 1Timestamp:....................................... 0d 00h 50m 39s 878289usFrame Length:.................................... 147Frame 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 .@......P.......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:.................................... 3Last Frame Number:............................... 1120Direction:....................................... 1Timestamp:....................................... 0d 00h 50m 39s 881513usFrame Length:.................................... 189Frame Data:00000000: 80 00 00 00 ff ff ff ff ff ff 00 12 44 bd 80 30 ............D..000000010: 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 ....@.......@...Cisco Wireless LAN Controller Configuration Guide, Release 7.4       OL-28744-01 269Troubleshooting CCXv5 Client Devices
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...Configuring Client ReportingThe client reporting protocol is used by the client and the access point to exchange client information. Clientreports are collected automatically when the client associates. You can use the controller GUI or CLI to senda client report request to any CCXv5 client any time after the client associates. There are four types of clientreports:•Client profile—Provides information about the configuration of the client.•Operating parameters—Provides the details of the client’s current operational modes.•Manufacturers’information—Provides data about the wireless LAN client adapter in use.•Client capabilities—Provides information about the client’s capabilities.Configuring Client Reporting (GUI)Step 1 Choose Monitor > Clients to open the Clients page.Step 2 Click the MAC address of the desired client. The Clients > Detail page appears.Step 3 To send a report request to the client, click Send CCXV5 Req.You must create a Trusted Profile using ACAU for Cisco CB21AG or equivalent software from your CCXv5vendor.NoteStep 4 To view the parameters from the client, click Display. The Client Reporting page appears.Step 5 Click the link for the desired client profile. The Profile Details page appears displaying the client profile details, includingthe SSID, power save mode, radio channel, data rates, and 802.11 security settings.Configuring Client Reporting (CLI)Step 1 To send a request to the client to send its profiles, enter this command:config client ccx get-profiles client_mac_addressStep 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_addressStep 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   Cisco Wireless LAN Controller Configuration Guide, Release 7.4270 OL-28744-01  Troubleshooting CCXv5 Client Devices
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_addressStep 5 To clear the client reporting information, enter this command:config client ccx clear-reports client_mac_addressStep 6 To see the client profiles, enter this command:show client ccx profiles client_mac_addressStep 7 To see the client operating parameters, enter this command:show client ccx operating-parameters client_mac_addressStep 8 To see the client manufacturer information, enter this command:show client ccx manufacturer-info client_mac_addressStep 9 To see the client’s capability information, enter this command:show client ccx client-capability client_mac_addressThis command displays the client’s available capabilities, not current settings for the capabilities.NoteConfiguring Roaming and Real-Time DiagnosticsYou can use roaming and real-time logs and statistics to solve system problems. The event log enables youto identify and track the behavior of a client device. It is especially useful when attempting to diagnosedifficulties that a user may be having on a WLAN. The event log provides a log of events and reports themto the access point. There are three categories of event logs:•Roaming log—This log provides a historical view of the roaming events for a given client. The clientmaintains a minimum of five previous roaming events including failed attempts and successful roams.•Robust Security Network Association ( RSNA) log—This log provides a historical view of theauthentication events for a given client. The client maintains a minimum of five previous authenticationattempts including failed attempts and successful ones.•Syslog—This log provides internal system information from the client. For example, it may indicateproblems with 802.11 operation, system operation, and so on.The statistics report provides 802.1X and security information for the client. You can use the controller CLIto send the event log and statistics request to any CCXv5 client any time after the client associates.Configuring Roaming and Real-Time Diagnostics (CLI)Step 1 To send a log request, enter this command:config client ccx log-request log_type client_mac_addresswhere log_type is roam, rsna, or syslog.Step 2 To view a log response, enter this command:Cisco Wireless LAN Controller Configuration Guide, Release 7.4       OL-28744-01 271Troubleshooting CCXv5 Client Devices
show client ccx log-response log_type client_mac_addresswhere log_type is roam, rsna, or syslog.Information similar to the following appears for a log response with a log_type of roam:Tue Jun 26 18:28:48 2007 Roaming Response LogID=133: Status=SuccessfulEvent Timestamp=0d 00h 00m 13s 322396usSource BSSID=00:0b:85:81:06:c2, Target BSSID=00:0b:85:81:06:c2, TransitionTime=3125(ms)Transition Reason: Normal roam, poor linkTransition Result: SuccessTue Jun 26 18:28:48 2007 Roaming Response LogID=133: Status=SuccessfulEvent Timestamp=0d 00h 00m 16s 599006usSource BSSID=00:0b:85:81:06:c2, Target BSSID=00:0b:85:81:06:c2, TransitionTime=3235(ms)Transition Reason: Normal roam, poor linkTransition Result: SuccessEvent Timestamp=0d 00h 00m 19s 882921usSource BSSID=00:0b:85:81:06:c2, Target BSSID=00:0b:85:81:06:c2, TransitionTime=3234(ms)Transition Reason: Normal roam, poor linkTransition Result: SuccessTue Jun 26 18:28:48 2007 Roaming Response LogID=133: Status=SuccessfulEvent Timestamp=0d 00h 00m 08s 815477usSource BSSID=00:0b:85:81:06:c2, Target BSSID=00:0b:85:81:06:d2, TransitionTime=3281(ms)Transition Reason: First association to WLANTransition Result: SuccessEvent Timestamp=0d 00h 00m 26s 637084usSource BSSID=00:0b:85:81:06:d2, Target BSSID=00:0b:85:81:06:c2, TransitionTime=3313(ms)Information similar to the following appears for a log response with a log_type of rsna:Tue Jun 26 18:24:09 2007 RSNA Response LogID=132: Status=SuccessfulEvent Timestamp=0d 00h 00m 00s 246578usTarget BSSID=00:14:1b:58:86:cdRSNA Version=1Group Cipher Suite=00-0f-ac-02Pairwise Cipher Suite Count = 1Pairwise Cipher Suite 0 = 00-0f-ac-04AKM Suite Count = 1AKM Suite 0 = 00-0f-ac-01RSN Capability = 0x0RSNA Result: SuccessTue Jun 26 18:24:09 2007 RSNA Response LogID=132: Status=SuccessfulEvent Timestamp=0d 00h 00m 00s 246625usTarget BSSID=00:14:1b:58:86:cdRSNA Version=1Group Cipher Suite=00-0f-ac-02Pairwise Cipher Suite Count = 1Pairwise Cipher Suite 0 = 00-0f-ac-04AKM Suite Count = 1   Cisco Wireless LAN Controller Configuration Guide, Release 7.4272 OL-28744-01  Troubleshooting CCXv5 Client Devices
AKM Suite 0 = 00-0f-ac-01RSN Capability = 0x0RSNA Result: SuccessTue Jun 26 18:24:09 2007 RSNA Response LogID=132: Status=SuccessfulEvent Timestamp=0d 00h 00m 01s 624375usTarget BSSID=00:14:1b:58:86:cdRSNA Version=1Group Cipher Suite=00-0f-ac-02Pairwise Cipher Suite Count = 1Pairwise Cipher Suite 0 = 00-0f-ac-04AKM Suite Count = 1AKM Suite 0 = 00-0f-ac-01RSN Capability = 0x0RSNA Result: SuccessInformation similar to the following appears for a log response with a log_type of syslog:Tue Jun 26 18:07:48 2007 SysLog Response LogID=131: Status=SuccessfulEvent Timestamp=0d 00h 19m 42s 278987usClient SysLog = '<11> Jun 19 11:49:47 uraval3777 Mandatory elements missingin the OID response'Event Timestamp=0d 00h 19m 42s 278990usClient SysLog = '<11> Jun 19 11:49:50 uraval3777 Mandatory elements missingin the OID response'Tue Jun 26 18:07:48 2007 SysLog Response LogID=131: Status=SuccessfulEvent Timestamp=0d 00h 19m 42s 278993usClient SysLog = '<11> Jun 19 11:49:53 uraval3777 Mandatory elements missingin the OID response'Event Timestamp=0d 00h 19m 42s 278996usClient SysLog = '<11> Jun 19 11:49:56 uraval3777 Mandatory elements missingin the OID response'Tue Jun 26 18:07:48 2007 SysLog Response LogID=131: Status=SuccessfulEvent Timestamp=0d 00h 19m 42s 279000usClient SysLog = '<11> Jun 19 11:50:00 uraval3777 Mandatory elements missingin the OID response'Event Timestamp=0d 00h 19m 42s 279003usClient SysLog = '<11> Jun 19 11:50:03 uraval3777 Mandatory elements missingin the OID response'Tue Jun 26 18:07:48 2007 SysLog Response LogID=131: Status=SuccessfulEvent Timestamp=0d 00h 19m 42s 279009usClient SysLog = '<11> Jun 19 11:50:09 uraval3777 Mandatory elements missingin the OID response'Event Timestamp=0d 00h 19m 42s 279012usClient SysLog = '<11> Jun 19 11:50:12 uraval3777 Mandatory elements missingin the OID response'Step 3 To send a request for statistics, enter this command:config client ccx stats-request measurement_duration stats_name client_mac_addresswhere stats_name is dot11 or security.Step 4 To view the statistics response, enter this command:show client ccx stats-report client_mac_addressCisco Wireless LAN Controller Configuration Guide, Release 7.4       OL-28744-01 273Troubleshooting CCXv5 Client Devices
Information similar to the following appears:Measurement duration = 1dot11TransmittedFragmentCount = 1dot11MulticastTransmittedFrameCount = 2dot11FailedCount = 3dot11RetryCount = 4dot11MultipleRetryCount = 5dot11FrameDuplicateCount = 6dot11RTSSuccessCount = 7dot11RTSFailureCount = 8dot11ACKFailureCount = 9dot11ReceivedFragmentCount = 10dot11MulticastReceivedFrameCount = 11dot11FCSErrorCount = 12dot11TransmittedFrameCount = 13Using the Debug FacilityInformation About Using the Debug FacilityThe debug facility enables you to display all packets going to and from the controller CPU. You can enableit for received packets, transmitted packets, or both. By default, all packets received by the debug facility aredisplayed. However, you can define access control lists (ACLs) to filter packets before they are displayed.Packets not passing the ACLs are discarded without being displayed.Each ACL includes an action (permit, deny, or disable) and one or more fields that can be used to match thepacket. The debug facility provides ACLs that operate at the following levels and on the following values:•Driver ACL◦NPU encapsulation type◦Port•Ethernet header ACL◦Destination address◦Source address◦Ethernet type◦VLAN ID•IP header ACL◦Source address   Cisco Wireless LAN Controller Configuration Guide, Release 7.4274 OL-28744-01  Using the Debug Facility
◦Destination address◦Protocol◦Source port (if applicable)◦Destination port (if applicable)•EoIP payload Ethernet header ACL◦Destination address◦Source address◦Ethernet type◦VLAN ID•EoIP payload IP header ACL◦Source address◦Destination address◦Protocol◦Source port (if applicable)◦Destination port (if applicable)•CAPWAP payload 802.11 header ACL◦Destination address◦Source address◦BSSID◦SNAP header type•CAPWAP payload 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.Configuring the Debug Facility (CLI)Step 1 To enable the debug facility, enter this command:Cisco Wireless LAN Controller Configuration Guide, Release 7.4       OL-28744-01 275Using the Debug Facility
debug packet logging enable {rx |tx |all}packet_count display_size•where◦rx displays all received packets, tx displays all transmitted packets, and all displays both transmitted andreceived packets.◦packet_count is the maximum number of packets to log. You can enter a value between 1 and 65535 packets,and the default value is 25 packets.◦display_size is the number of bytes to display when printing a packet. By default, the entire packet is displayed.To disable the debug facility, enter this command: debug packet logging disable.Note•debug packet logging acl driver rule_index action npu_encap portwhere◦rule_index is a value between 1 and 6 (inclusive).◦action is permit, deny, or disable.◦npu_encap specifies the NPU encapsulation type, which determines how packets are filtered. The possiblevalues include dhcp, dot11-mgmt, dot11-probe, dot1x, eoip-ping, iapp, ip, lwapp, multicast, orphan-from-sta,orphan-to-sta, rbcp, wired-guest, or any.◦port is the physical port for packet transmission or reception.•Use these commands to configure packet-logging ACLs:debug packet logging acl eth rule_index action dst src type vlanwhere◦rule_index is a value between 1 and 6 (inclusive).◦action is permit, deny, or disable.◦dst is the destination MAC address.◦src is the source MAC address.◦type is the two-byte type code (such as 0x800 for IP, 0x806 for ARP). This parameter also accepts a fewcommon string values such as “ip”(for 0x800) or “arp”(for 0x806).◦vlan is the two-byte VLAN ID.•debug packet logging acl ip rule_index action src dst proto src_port dst_portwhere◦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 anumeric 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,   Cisco Wireless LAN Controller Configuration Guide, Release 7.4276 OL-28744-01  Using the Debug Facility
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 acceptsa numeric or any string recognized by getservbyname(). The controller supports the same strings as those forthe 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_typewhere◦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_portTo remove all configured ACLs, enter this command: debug packet logging acl clear-all.NoteStep 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 theuse of hex2pcap and can be decoded using an HTML front end. The text2pcap option is provided as an alternative sothat a sequence of packets can be decoded from the same console log file.This figure shows an example of hex2pcap output.Figure 30: Sample Hex2pcap OutputCisco Wireless LAN Controller Configuration Guide, Release 7.4       OL-28744-01 277Using the Debug Facility
This figure shows an example of text2pcap output.Figure 31: Sample Text2pcap OutputStep 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 packetInformation similar to the following appears:Status........................................... disabledNumber of packets to display..................... 25Bytes/packet to display.......................... 0Packet display format............................ text2pcapDriver ACL:[1]: disabled[2]: disabled[3]: disabled[4]: disabled[5]: disabled[6]: disabledEthernet ACL:[1]: disabled[2]: disabled[3]: disabled[4]: disabled[5]: disabled[6]: disabledIP ACL:[1]: disabled[2]: disabled[3]: disabled[4]: disabled[5]: disabled[6]: disabledEoIP-Ethernet ACL:[1]: disabled[2]: disabled[3]: disabled[4]: disabled   Cisco Wireless LAN Controller Configuration Guide, Release 7.4278 OL-28744-01  Using the Debug Facility
[5]: disabled[6]: disabledEoIP-IP ACL:[1]: disabled[2]: disabled[3]: disabled[4]: disabled[5]: disabled[6]: disabledLWAPP-Dot11 ACL:[1]: disabled[2]: disabled[3]: disabled[4]: disabled[5]: disabled[6]: disabledLWAPP-IP ACL:[1]: disabled[2]: disabled[3]: disabled[4]: disabled[5]: disabled[6]: disabled?Configuring Wireless SniffingInformation About Wireless SniffingThe controller enables you to configure an access point as a network “sniffer,”which captures and forwardsall the packets on a particular channel to a remote machine that runs packet analyzer software. These packetscontain information on time stamps, signal strength, packet sizes, and so on. Sniffers allow you to monitorand record network activity and to detect problems.Prerequisites for Wireless SniffingTo perform wireless sniffing, you need the following hardware and software:•A dedicated access point—An access point configured as a sniffer cannot simultaneously provide wirelessaccess service on the network. To avoid disrupting coverage, use an access point that is not part of yourexisting wireless network.•A remote monitoring device—A computer capable of running the analyzer software.•Windows XP or Linux operating system—The controller supports sniffing on both Windows XP andLinux machines.•Software and supporting files, plug-ins, or adapters—Your analyzer software may require specializedfiles before you can successfully enableRestrictions for Wireless Sniffing•Supported third-party network analyzer software applications are as follows:Cisco Wireless LAN Controller Configuration Guide, Release 7.4       OL-28744-01 279Configuring Wireless Sniffing
◦Wildpackets Omnipeek or Airopeek◦AirMagnet Enterprise Analyzer◦Wireshark•The latest version of Wireshark can decode the packets by going to the Analyze mode. Select decodeas, and switch UDP5555 to decode as AIROPEEK.•You must disable IP-MAC address binding in order to use an access point in sniffer mode if the accesspoint is joined to a Cisco 5500 Series Controller. To disable IP-MAC address binding, enter the confignetwork 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 joinedto a Cisco 5500 Series Controller. If WLAN 1 is disabled, the access point cannot send packets.Prerequisites for Wireless SniffingConfiguring Sniffing on an Access Point (GUI)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 (or 802.11b/g/n) to open the 802.11a/n (or 802.11b/g/n) Radiospage.Step 7 Hover your cursor over the blue drop-down arrow for the desired access point and choose Configure. The 802.11a/n(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 defaultvalue 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.Configuring Sniffing on an Access Point (CLI)Step 1 Configure the access point as a sniffer by entering this command:config ap mode sniffer Cisco_AP   Cisco Wireless LAN Controller Configuration Guide, Release 7.4280 OL-28744-01  Configuring Wireless Sniffing
where Cisco_AP is the access point configured as the sniffer.Step 2 When warned that the access point will be rebooted and asked if you want to continue, enter Y. The access point rebootsin 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_APwhere•channel is the radio channel on which the access point sniffs for packets. The default values are 36 (802.11a/n)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.To disable sniffing on the access point, enter the config ap sniff {802.11a | 802.11b}disable Cisco_APcommand.NoteStep 4 Save your changes by entering this command:save configStep 5 See the sniffer configuration settings for an access point by entering this command:show ap config {802.11a | 802.11b}Cisco_APTroubleshooting Access Points Using Telnet or SSH_oldThe controller supports the use of the Telnet and Secure Shell (SSH) protocols to troubleshoot lightweightaccess points. Using these protocols makes debugging easier, especially when the access point is unable toconnect to the controller.•To avoid potential conflicts and security threats to the network, the following commands are unavailablewhile a Telnet or SSH session is enabled: config terminal, telnet, ssh, rsh, ping, traceroute, clear,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.For instructions on configuring Telnet or SSH SSH sessions on the controller, see theConfiguring Telnet and Secure Shell Sessions section.NoteInformation About Troubleshooting Access Points Using Telnet or SSHThe controller supports the use of the Telnet and Secure Shell (SSH) protocols to troubleshoot lightweightaccess points. Using these protocols makes debugging easier, especially when the access point is unable toconnect to the controller.Cisco Wireless LAN Controller Configuration Guide, Release 7.4       OL-28744-01 281Troubleshooting Access Points Using Telnet or SSH_old
•To avoid potential conflicts and security threats to the network, the following commands are unavailablewhile a Telnet or SSH session is enabled: config terminal, telnet, ssh, rsh, ping, traceroute, clear,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.For instructions on configuring Telnet or SSH SSH sessions on the controller, see theConfiguring Telnet and Secure Shell Sessions section.NoteYou can configure Telnet or SSH by using the controller CLI in software release 5.0 or later releases or usingthe controller GUI in software release 6.0 or later releases.Troubleshooting Access Points Using Telnet or SSH (GUI)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.Troubleshooting Access Points Using Telnet or SSH (CLI)Step 1 Enable Telnet or SSH connectivity on an access point by entering this command:config ap {telnet | ssh}enable Cisco_APThe default value is disabled.Disable Telnet or SSH connectivity on an access point by entering this command: config ap {telnet | ssh}disable Cisco_APNoteStep 2 Save your changes by entering this command:save configStep 3 See whether Telnet or SSH is enabled on an access point by entering this command:show ap config general Cisco_APInformation similar to the following appears:Cisco AP Identifier.............................. 5   Cisco Wireless LAN Controller Configuration Guide, Release 7.4282 OL-28744-01  Troubleshooting Access Points Using Telnet or SSH_old
Cisco AP Name.................................... AP33Country code..................................... Multiple Countries:US,AE,AR,AT,AU,BHReg. Domain allowed by Country................... 802.11bg:-ABCENR 802.11a:-ABCENAP Country code.................................. US - United StatesAP Regulatory Domain............................. 802.11bg:-A 802.11a:-ASwitch Port Number .............................. 2MAC Address...................................... 00:19:2f:11:16:7aIP Address Configuration......................... Static IP assignedIP Address....................................... 10.22.8.133IP NetMask....................................... 255.255.248.0Gateway IP Addr.................................. 10.22.8.1Domain...........................................Name Server......................................Telnet State..................................... EnabledSsh State........................................ Enabled...Debugging the Access Point Monitor ServiceInformation About Debugging the Access Point Monitor ServiceThe controller sends access point status information to the Cisco 3300 Series Mobility Services Engine (MSE)using the access point monitor service.The MSE sends a service subscription and an access point monitor service request to get the status of all accesspoints currently known to the controller. When any change is made in the status of an access point, a notificationis sent to the MSE.Debugging Access Point Monitor Service Issues (CLI)If you experience any problems with the access point monitor service, enter this command:debug service ap-monitor {all | error | event | nmsp | packet} {enable | disable}where•all configures debugging of all access point status messages.•error configures debugging of access point monitor error events.•event configures debugging of access point monitor events.•nmsp configures debugging of access point monitor NMSP events.•packet configures debugging of access point monitor packets.•enable enables the debub service ap-monitor mode.•disable disables the debug service ap-monitor mode.Cisco Wireless LAN Controller Configuration Guide, Release 7.4       OL-28744-01 283Debugging the Access Point Monitor Service
Troubleshooting OfficeExtend Access PointsInformation About Troubleshooting OfficeExtend Access PointsThis section provides troubleshooting information if you experience any problems with your OfficeExtendaccess points.Interpreting OfficeExtend LEDsThe LED patterns are different for 1130 series and 1140 series OfficeExtend access points. See the CiscoOfficeExtend Access Point Quick Start Guide for a description of the LED patterns. You can find this guideat this URL:http://www.cisco.com/en/US/products/hw/wireless/index.htmlPositioning OfficeExtend Access Points for Optimal RF CoverageWhen positioning your OfficeExtend access point, consider that its RF signals are emitted in a cone shapespreading outward from the LED side of the access point. Ensure to mount the access point so that air canflow behind the metal back plate and prevent the access point from overheating.Figure 32: OfficeExtend Access Point Radiation PatternsTroubleshooting Common ProblemsMost of the problems experienced with OfficeExtend access points are one of the following:•The access point cannot join the controller because of network or firewall issues.Resolution: Follow the instructions in the Viewing Access Point Join Information section to see joinstatistics for the OfficeExtend access point, or find the access point’s public IP address and performpings of different packet sizes from inside the company.•The access point joins but keeps dropping off. This behavior usually occurs because of network problemsor when the network address translation (NAT) or firewall ports close because of short timeouts.Resolution: Ask the teleworker for the LED status.•Clients cannot associate because of NAT issues.Resolution: Ask the teleworker to perform a speed test and a ping test. Some servers do not return bigpacket pings.   Cisco Wireless LAN Controller Configuration Guide, Release 7.4284 OL-28744-01  Troubleshooting OfficeExtend Access Points
•Clients keep dropping data. This behavior usually occurs because the home router closes the port becauseof short timeouts.Resolution: Perform client troubleshooting in Cisco Prime Infrastructure to determine if the problem isrelated 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 cannotidentify 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 suchas http://www.cisco.com/. If the PC cannot connect to the Internet, check the router or modem. Ifthe PC can connect to the Internet, check the home router configuration to see if a firewall orMAC-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 manualand 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 neutralzone between a company’s private network and the outside public network. It prevents outsideusers 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 clickingClear Config on the access point GUI or by entering the clear ap config Cisco_AP command and thenconfiguring a personal SSID on an OfficeExtend Access Point. If problems still occur, contact yourcompany’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.Cisco Wireless LAN Controller Configuration Guide, Release 7.4       OL-28744-01 285Troubleshooting OfficeExtend Access Points
   Cisco Wireless LAN Controller Configuration Guide, Release 7.4286 OL-28744-01  Troubleshooting OfficeExtend Access Points
PART IIConfiguring Ports and Interfaces•Overview of Ports and Interfaces, page 289•Configuring the Management Interface, page 295•Configuring the AP-Manager Interface, page 299•Configuring Virtual Interfaces, page 305•Configuring Service-Port Interfaces, page 307•Configuring Dynamic Interfaces, page 309•Configuring Ports, page 315•Information About Using Cisco 5500 Series Controller USB Console Port, page 317•Configuring Link Aggregation, page 319•Configuring Multiple AP-Manager Interfaces, page 323•Configuring VLAN Select, page 327•Configuring Interface Groups, page 331•Configuring Multicast Optimization, page 335
CHAPTER 26Overview of Ports and InterfacesThree concepts are key to understanding how controllers connect to a wireless network: ports, interfaces,and WLANs.•Information About Ports, page 289•Information About Distribution System Ports, page 290•Information About Interfaces, page 291•Information About Dynamic AP Management, page 292•Information About WLANs, page 293Information About PortsA port is a physical entity that is used for connections on the controller platform. Controllers have two typesof ports: distribution system ports and a service port.Figure 33: Ports on the Cisco 5500 Series Wireless LAN ControllersSFP distribution system ports 1–86Redundant port (RJ-45)1Management port LEDs7Service port (RJ-45)2SFP distribution port Link and Activity LEDs8Console port (RJ-45)3Cisco Wireless LAN Controller Configuration Guide, Release 7.4        OL-28744-01 289
Power supply (PS1 and PS2), System (SYS), andAlarm (ALM) LEDs9USB ports 0 and 1 (Type A)4Expansion module slot10Console port (Mini USB Type B)You can use only one console port(either RJ-45 or mini USB). Whenyou connect to one console port, theother is disabled.Note5Information About Distribution System PortsA distribution system port connects the controller to a neighbor switch and serves as the data path betweenthese two devices.Restrictions for Configuring Distribution System Ports•Cisco 5508 Controllers have eight Gigabit Ethernet distribution system ports, through which the Controllercan manage multiple access points. The 5508-12, 5508-25, 5508-50, 5508-100, and 5508-250 modelsallow a total of 12, 25, 50, 100, or 250 access points to join the controller. Cisco 5508 controllers haveno restrictions on the number of access points per port. However, we recommend using link aggregation(LAG) or configuring dynamic AP-manager interfaces on each Gigabit Ethernet port to automaticallybalance the load. If more than 100 access points are connected to the Cisco 5500 Series Controller, makesure that more than one Gigabit Ethernet interface is connected to the upstream switch.The Gigabit Ethernet ports on the Cisco 5508 Controllers accept these SX/LC/T smallform-factor plug-in (SFP) modules: - 1000BASE-SX SFP modules, which provide a1000-Mbps wired connection to a network through an 850nM (SX) fiber-optic linkusing an LC physical connector - 1000BASE-LX SFP modules, which provide a1000-Mbps wired connection to a network through a 1300nM (LX/LH) fiber-optic linkusing an LC physical connector - 1000BASE-T SFP modules, which provide a1000-Mbps wired connection to a network through a copper link using an RJ-45 physicalconnectorNote•Each distribution system port is, by default, an 802.1Q VLAN trunk port. The VLAN trunkingcharacteristics of the port are not configurable.Some controllers support link aggregation (LAG), which bundles all of the controller’sdistribution system ports into a single 802.3ad port channel. Cisco 5500 Series Controllerssupport LAG, and LAG is enabled automatically on the controllers within the CiscoWiSM2.Note•In Cisco Flex 7500 and 8500 Series Controllers:   Cisco Wireless LAN Controller Configuration Guide, Release 7.4290 OL-28744-01  Information About Distribution System Ports
If a port is unresponsive after a soaking period of 5 seconds, all the interfaces for which the portis 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 overto the primary port if it is operational.•After the unresponsive port is restored, there is a soaking period of 60 seconds after which if theport is still operational, then all the interfaces fall back to this port, which was the primary port. Ifthe port was the backup port, then no change is done.Information About Service PortCisco 5500 Series Controllers also have a 10/100/1000 copper Ethernet service port. The service port iscontrolled by the service-port interface and is reserved for out-of-band management of the controller andsystem recovery and maintenance in the event of a network failure. It is also the only port that is active whenthe controller is in boot mode. The service port is not capable of carrying 802.1Q tags, so it must be connectedto an access port on the neighbor switch. Use of the service port is optional.The service port is not autosensing. You must use the correct straight-through or crossover Ethernet cableto communicate with the service port.NoteDo not configure wired clients in the same VLAN or subnet of the service port of the controller on thenetwork. If you configure wired clients on the same subnet or VLAN as the service port, it is not possibleto access the management interface of the controller.CautionInformation About InterfacesAn interface is a logical entity on the controller. An interface has multiple parameters associated with it,including an IP address, default gateway (for the IP subnet), primary physical port, secondary physical port,VLAN identifier, and DHCP server.These five types of interfaces are available on the controller. Four of these are static and are configured atsetup time:•Management interface (static and configured at setup time; mandatory)•AP-manager interface (static and configured at setup time; mandatory)You are not required to configure an AP-manager interface on Cisco 5500 SeriesControllers.Note•Virtual interface (static and configured at setup time; mandatory)•Service-port interface (static and configured at setup time; optional)•Dynamic interface (user-defined)Cisco Wireless LAN Controller Configuration Guide, Release 7.4       OL-28744-01 291Information About Interfaces
Typically, you define the management, AP-manager, virtual, and service-port interface parameters usingthe Startup Wizard. However, you can display and configure interface parameters through either the GUIor CLI after the controller is running.NoteWhen LAG is disabled, each interface is mapped to at least one primary port, and some interfaces (managementand dynamic) can be mapped to an optional secondary (or backup) port. If the primary port for an interfacefails, the interface automatically moves to the backup port. In addition, multiple interfaces can be mapped toa single controller port.Interfaces that are quarantined are not displayed on the Controller > Interfaces page. For example, if thereare 6 interfaces and one of them is quarantined, the quarantined interface is not displayed and the detailsof the other 5 interfaces are displayed on the GUI. You can get the total number of interfaces that isinclusive of quarantined interfaces through the count displayed on the top-right corner of the GUI.NoteRestrictions for Configuring Interfaces•Each physical port on the wireless controller can have only one AP-manager configured with it. For theCisco 5500 Series Controllers, the management interface with AP-management enabled cannot fail overto the backup port, which is primary for the AP-manager on the management or dynamic VLAN interface.•Cisco 5500 Series Controllers do not support fragmented pings on any interface.Information About Dynamic AP ManagementA dynamic interface is created as a WLAN interface by default. However, any dynamic interface can beconfigured as an AP-manager interface, with one AP-manager interface allowed per physical port. A dynamicinterface with the Dynamic AP Management option enabled is used as the tunnel source for packets from thecontroller to the access point and as the destination for CAPWAP packets from the access point to the controller.The dynamic interfaces for AP management must have a unique IP address and are usually configured on thesame subnet as the management interface.If link aggregation (LAG) is enabled, there can be only one AP-manager interface.NoteWe recommend having a separate dynamic AP-manager interface per controller port.   Cisco Wireless LAN Controller Configuration Guide, Release 7.4292 OL-28744-01  Information About Dynamic AP Management
Information About WLANsA WLAN associates a service set identifier (SSID) to an interface or an interface group. It is configured withsecurity, quality of service (QoS), radio policies, and other wireless network parameters. Up to 512 WLANscan be configured per controller.Figure 34: Relationship between Ports, Interfaces, and WLANsEach 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 interfaceto use the native VLAN on a neighboring Cisco switch, make sure you configure the interface on the controllerto be untagged.A zero value for the VLAN identifier (on the Controller > Interfaces page) means that the interface isuntagged.NoteCisco Wireless LAN Controller Configuration Guide, Release 7.4       OL-28744-01 293Information About WLANs
The default (untagged) native VLAN on Cisco switches is VLAN 1. When controller interfaces are configuredas tagged (meaning that the VLAN identifier is set to a nonzero value), the VLAN must be allowed on the802.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 VLANson the neighbor switch’s 802.1Q trunk connections to controller ports. All other VLANs should be disallowedor pruned in the switch port trunk configuration. This practice is extremely important for optimal performanceof the controller.We recommend that you assign one set of VLANs for WLANs and a different set of VLANs formanagement interfaces to ensure that controllers properly route VLAN traffic.Note   Cisco Wireless LAN Controller Configuration Guide, Release 7.4294 OL-28744-01  Information About WLANs

Navigation menu