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

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

Wireless LAN Controller Configuration Guide_Part3

Configuring Web RedirectConfiguring Web Redirect (GUI)Step 1 Choose WLANs to open the WLANs page.Step 2 Click the ID number of the desired WLAN. The WLANs > Edit page appears.Step 3 Choose the Security and Layer 2 tabs to open the WLANs > Edit (Security > Layer 2) page.Step 4 From the Layer 2 Security drop-down list, choose 802.1X or WPA+WPA2.Step 5 Set any additional parameters for 802.1X or WPA+WPA2.Step 6 Choose the Layer 3 tab to open the WLANs > Edit (Security > Layer 3) page.Step 7 From the Layer 3 Security drop-down list, choose None.Step 8 Check the Web Policy check box.Step 9 Choose one of the following options to enable conditional or splash page web redirect: Conditional Web Redirect orSplash Page Web Redirect. The default value is disabled for both parameters.Step 10 If the user is to be redirected to a site external to the controller, choose the ACL that was configured on your RADIUSserver from the Preauthentication ACL drop-down list.Step 11 Click Apply to commit your changes.Step 12 Click Save Configuration to save your changes.Configuring Web Redirect (CLI)Step 1 Enable or disable conditional web redirect by entering this command:config wlan security cond-web-redir {enable |disable}wlan_idStep 2 Enable or disable splash page web redirect by entering this command:config wlan security splash-page-web-redir {enable |disable}wlan_idStep 3 Save your settings by entering this command:save configStep 4 See the status of the web redirect features for a particular WLAN by entering this command:show wlan wlan_idInformation similar to the following appears:WLAN Identifier.................................. 1Profile Name..................................... testNetwork Name (SSID).............................. test...Web Based Authentication......................... DisabledCisco Wireless LAN Controller Configuration Guide, Release 7.4       OL-28744-01 639Configuring Web Redirect
Web-Passthrough.................................. DisabledConditional Web Redirect......................... DisabledSplash-Page Web Redirect......................... Enabled...Disabling Accounting Servers per WLAN (GUI)Disabling accounting servers disables all accounting operations and prevents the controller from fallingback to the default RADIUS server for the WLAN.NoteStep 1 Choose WLANs to open the WLANs page.Step 2 Click the ID number of the WLAN to be modified. The WLANs > Edit page appears.Step 3 Choose the Security and AAA Servers tabs to open the WLANs > Edit (Security > AAA Servers) page.Step 4 Unselect the Enabled check box for the Accounting Servers.Step 5 Click Apply to commit your changes.Step 6 Click Save Configuration to save your changes.Disabling Coverage Hole Detection per WLANCoverage hole detection is enabled globally on the controller.NoteYou can disable coverage hole detection on a per-WLAN basis. When you disable coverage hole detectionon a WLAN, a coverage hole alert is still sent to the controller, but no other processing is done to mitigatethe coverage hole. This feature is useful for guest WLANs where guests are connected to your networkfor short periods of time and are likely to be highly mobile.Note   Cisco Wireless LAN Controller Configuration Guide, Release 7.4640 OL-28744-01  Disabling Accounting Servers per WLAN (GUI)
Disabling Coverage Hole Detection on a WLAN (GUI)Step 1 Choose WLANs to open the WLANs page.Step 2 Click the profile name of the WLAN to be modified. The WLANs > Edit page appears.Step 3 Choose the Advanced tab to display the WLANs > Edit (Advanced) page.Step 4 Unselect the Coverage Hole Detection Enabled check box.OEAP 600 Series Access Points do not support coverage holedetection.NoteStep 5 Click Apply.Step 6 Click Save Configuration.Disabling Coverage Hole Detection on a WLAN (CLI)Step 1 Disable coverage hole detection on a by entering this command:config wlan chd wlan-id disableOEAP 600 Series Access Points do not support Coverage Holedetection.NoteStep 2 Save your settings by entering this command:save configStep 3 See the coverage hole detection status for a particular WLAN by entering this command:show wlan wlan-idInformation similar to the following appears:WLAN Identifier.................................. 2Profile Name..................................... wlan2Network Name (SSID).............................. 2...CHD per WLAN.................................. DisabledCisco Wireless LAN Controller Configuration Guide, Release 7.4       OL-28744-01 641Disabling Coverage Hole Detection per WLAN
   Cisco Wireless LAN Controller Configuration Guide, Release 7.4642 OL-28744-01  Disabling Coverage Hole Detection per WLAN
CHAPTER 95Configuring NAC Out-of-Band Integration•Prerequisites for NAC Out Of Band, page 643•Restrictions for NAC Out of Band, page 644•Information About NAC Out-of-Band Integration, page 645•Configuring NAC Out-of-Band Integration (GUI), page 645•Configuring NAC Out-of-Band Integration (CLI), page 647Prerequisites for NAC Out Of Band•CCA software release 4.5 or later releases is required for NAC out-of-band integration.•Because the NAC appliance supports static VLAN mapping, you must configure a unique quarantineVLAN for each interface that is configured on the controller. For example, you might configure aquarantine VLAN of 110 on controller 1 and a quarantine VLAN of 120 on controller 2. However, iftwo WLANs or guest LANs use the same distribution system interface, they must use the same quarantineVLAN if they have one NAC appliance deployed in the network. The NAC appliance supports uniquequarantine-to-access VLAN mapping.•For a posture reassessment that is based on a session expiry, you must configure the session timeout onboth the NAC appliance and the WLAN, making sure that the session expiry on the WLAN is greaterthan that on the NAC appliance.•When a session timeout is configured on an open WLAN, the timing out of clients in the Quarantinestate is determined by the timer on the NAC appliance. After the session timeout expires for WLANsthat use web authentication, clients deauthenticate from the controller and must perform posture validationagain.•All Layer 2 and Layer 3 authentication occurs in the quarantine VLAN. To use external webauthentication, you must configure the NAC appliance to allow HTTP traffic to and from external webservers and to allow the redirect URL in the quarantine VLAN.Cisco Wireless LAN Controller Configuration Guide, Release 7.4        OL-28744-01 643
See the Cisco NAC appliance configuration guides for configuration instructions: http://www.cisco.com/en/US/products/ps6128/products_installation_and_configuration_guides_list.html.Note•If you want to enable NAC on an access point group VLAN, you must first enable NAC on the WLAN.Then you can enable or disable NAC on the access point group VLAN. If you ever decide to disableNAC on the WLAN, be sure to disable it on the access point group VLAN as well.•The NAC appliance supports up to 3500 users, and the controller supports up to 5000 users. MultipleNAC appliances might need to be deployed.•If you want to enable NAC on an access point group VLAN, you must first enable NAC on the WLAN.Then you can enable or disable NAC on the access point group VLAN. If you ever decide to disableNAC on the WLAN, be sure to disable it on the access point group VLAN as well.•The NAC appliance supports up to 3500 users, and the controller supports up to 5000 users. MultipleNAC appliances might need to be deployed.•In controller software releases prior to 5.1, the controller integrates with the NAC appliance only inin-band mode, where the NAC appliance must remain in the data path. For in-band mode, a NACappliance is required at each authentication location (such as at each branch or for each controller), andall traffic must traverse the NAC enforcement point. In controller software release 5.1 or later releases,the controller can integrate with the NAC appliance in out-of-band mode, where the NAC applianceremains in the data path only until clients have been analyzed and cleaned. Out-of-band mode reducesthe traffic load on the NAC appliance and enables centralized NAC processing.•NAC out-of-band integration is supported only on WLANs configured for FlexConnect central switching.It is not supported for use on WLANs configured for FlexConnect local switching.Restrictions for NAC Out of Band•Network Admission Control (NAC) is supported on 10 percent of the total number of wireless clientssupported on the controller.•NAC out-of-band integration is not supported for use with the WLAN AAA override feature.•In controller software releases prior to 5.1, the controller integrates with the NAC appliance only inin-band mode, where the NAC appliance must remain in the data path. For in-band mode, a NACappliance is required at each authentication location (such as at each branch or for each controller), andall traffic must traverse the NAC enforcement point. In controller software release 5.1 or later releases,the controller can integrate with the NAC appliance in out-of-band mode, where the NAC applianceremains in the data path only until clients have been analyzed and cleaned. Out-of-band mode reducesthe traffic load on the NAC appliance and enables centralized NAC processing.•NAC out-of-band integration is supported only on WLANs configured for FlexConnect central switching.It is not supported for use on WLANs configured for FlexConnect local switching.   Cisco Wireless LAN Controller Configuration Guide, Release 7.4644 OL-28744-01  Restrictions for NAC Out of Band
Information About NAC Out-of-Band IntegrationThe Cisco NAC Appliance, also known as Cisco Clean Access (CCA), is a network admission control (NAC)product that enables network administrators to authenticate, authorize, evaluate, and remediate wired, wireless,and remote users and their machines prior to allowing users onto the network. NAC identifies whether machinesare compliant with security policies and repairs vulnerabilities before permitting access to the network.The NAC appliance is available in two modes: in-band and out-of-band. Customers can deploy both modesif desired, each geared toward certain types of access (in-band for supporting wireless users and out-of-bandfor supporting wired users, for example).To implement the NAC out-of-band feature on the controller, you must enable NAC support on the WLANor guest LAN and then map this WLAN or guest LAN to an interface that is configured with a quarantineVLAN (untrusted VLAN) and an access VLAN (trusted VLAN). When a client associates and completesLayer 2 authentication, the client obtains an IP address from the access VLAN subnet, but the client state isQuarantine. While deploying the NAC out-of-band feature, be sure that the quarantine VLAN is allowed onlybetween the Layer 2 switch on which the controller is connected and the NAC appliance and that the NACappliance is configured with a unique quarantine-to-access VLAN mapping. Client traffic passes into thequarantine VLAN, which is trunked to the NAC appliance. After posture validation is completed, the clientis prompted to take remedial action. After cleaning is completed, the NAC appliance updates the controllerto change the client state from Quarantine to Access.The link between the controller and the switch is configured as a trunk, enabling the quarantine VLAN (110)and the access VLAN (10). On the Layer 2 switch, the quarantine traffic is trunked to the NAC appliancewhile the access VLAN traffic goes directly to the Layer 3 switch. Traffic that reaches the quarantine VLANon the NAC appliance is mapped to the access VLAN based on a static mapping configuration.Figure 47: Example of NAC Out-of-Band IntegrationConfiguring NAC Out-of-Band Integration (GUI)Step 1 Configure the quarantine VLAN for a dynamic interface as follows:Cisco Wireless LAN Controller Configuration Guide, Release 7.4       OL-28744-01 645Information About NAC Out-of-Band Integration
a) Choose Controller >Interfaces to open the Interfaces page.b) Click New to create a new dynamic interface.c) In the Interface Name text box, enter a name for this interface, such as “quarantine.”d) In the VLAN ID text box, enter a nonzero value for the access VLAN ID, such as “10.”e) Click Apply to commit your changes. The Interfaces > Edit page appears.f) Select the Quarantine check box and enter a nonzero value for the quarantine VLAN ID, such as “110.”We recommend that you configure unique quarantine VLANs throughout your network. If multiple controllersare configured in the same mobility group and access interfaces on all controllers are in the same subnet, itis mandatory to have the same quarantine VLAN if there is only one NAC appliance in the network. Ifmultiple controllers are configured in the same mobility group and access interfaces on all controllers arein different subnets, it is mandatory to have different quarantine VLANs if there is only one NAC appliancein the network.Noteg) Configure any remaining text boxes for this interface, such as the IP address, netmask, and default gateway.h) Click Apply to save your changes.Step 2 Configure NAC out-of-band support on a WLAN or guest LAN as follows:a) Choose WLANs to open the WLANs page.b) Click the ID number of the desired WLAN or guest LAN. The WLANs > Edit page appears.c) Choose the Advanced tab to open the WLANs > Edit (Advanced) page.d) Configure NAC out-of-band support for this WLAN or guest LAN by selecting the NAC State check box. To disableNAC out-of-band support, leave the check box unselected, which is the default value.e) Click Apply to commit your changes.Step 3 Configure NAC out-of-band support for a specific access point group as follows:a) Choose WLANs >Advanced >AP Groups to open the AP Groups page.b) Click the name of the desired access point group.c) Choose the WLANs tab to open the AP Groups > Edit (WLANs) page.d) Click Add New to assign a WLAN to this access point group. The Add New section appears at the top of the page.e) From the WLAN SSID drop-down list, choose the SSID of the WLAN.f) From the Interface Name drop-down list, choose the interface to which you want to map the access point group.Choose the quarantine VLAN if you plan to enable NAC out-of-band support.g) To enable NAC out-of-band support for this access point group, select the NAC State check box. To disable NACout-of-band support, leave the check box unselected, which is the default value.h) Click Add to add this WLAN to the access point group. This WLAN appears in the list of WLANs assigned to thisaccess point group.If you ever want to remove this WLAN from the access point group, hover your cursor over the bluedrop-down arrow for the WLAN and choose Remove.NoteStep 4 Click Save Configuration to save your changes.Step 5 See the current state of the client (Quarantine or Access) as follows:a) Choose Monitor >Clients to open the Clients page.b) Click the MAC address of the desired client to open the Clients > Detail page. The NAC state appears under theSecurity Information section.The client state appears as “Invalid”if the client is probing, has not yet associated to a WLAN, or cannotcomplete Layer 2 authentication.Note   Cisco Wireless LAN Controller Configuration Guide, Release 7.4646 OL-28744-01  Configuring NAC Out-of-Band Integration (GUI)
Configuring NAC Out-of-Band Integration (CLI)Step 1 Configure the quarantine VLAN for a dynamic interface by entering this command:config interface quarantine vlan interface_name vlan_idYou must configure a unique quarantine VLAN for each interface on the controller.NoteTo disable the quarantine VLAN on an interface, enter 0for the VLAN ID.Step 2 Enable or disable NAC out-of-band support for a WLAN or guest LAN by entering this command:config {wlan |guest-lan}nac {enable |disable} {wlan_id |guest_lan_id}Step 3 Enable or disable NAC out-of-band support for a specific access point group by entering this command:config wlan apgroup nac {enable |disable}group_name wlan_idStep 4 Save your changes by entering this command:save configStep 5 See the configuration of a WLAN or guest LAN, including the NAC state by entering this command:show {wlan wlan_ id |guest-lan guest_lan_id}Information similar to the following appears:WLAN Identifier.................................. 1Profile Name..................................... wlanNetwork Name (SSID).............................. wlanStatus........................................... DisabledMAC Filtering.................................... DisabledBroadcast SSID................................... EnabledAAA Policy Override.............................. DisabledNetwork Admission ControlNAC-State...................................... EnabledQuarantine VLAN............................. 110...Step 6 See the current state of the client (either Quarantine or Access) by entering this command:show client detailed client_macInformation similar to the following appears:Client’s NAC state.................................. QUARANTINEThe client state appears as “Invalid”if the client is probing, has not yet associated to a WLAN, or cannot completeLayer 2 authentication.NoteCisco Wireless LAN Controller Configuration Guide, Release 7.4       OL-28744-01 647Configuring NAC Out-of-Band Integration (CLI)
   Cisco Wireless LAN Controller Configuration Guide, Release 7.4648 OL-28744-01  Configuring NAC Out-of-Band Integration (CLI)
CHAPTER 96Configuring Passive Clients•Restrictions for Passive Clients, page 649•Information About Passive Clients, page 649•Configuring Passive Clients (GUI), page 650•Configuring Passive Clients (CLI), page 651Restrictions for Passive Clients•The passive client feature is not supported with the AP groups and FlexConnect centrally switchedWLANs.Information About Passive ClientsPassive clients are wireless devices, such as scales and printers that are configured with a static IP address.These clients do not transmit any IP information such as IP address, subnet mask, and gateway informationwhen they associate with an access point. As a result, when passive clients are used, the controller neverknows the IP address unless they use the DHCP.Wireless LAN controllers currently act as a proxy for ARP requests. Upon receiving an ARP request, thecontroller responds with an ARP response instead of passing the request directly to the client. This scenariohas two advantages:•The upstream device that sends out the ARP request to the client will not know where the client islocated.•Power for battery-operated devices such as mobile phones and printers is preserved because they do nothave to respond to every ARP requests.Since the wireless controller does not have any IP related information about passive clients, it cannot respondto any ARP requests. The current behavior does not allow the transfer of ARP requests to passive clients. Anyapplication that tries to access a passive client will fail.Cisco Wireless LAN Controller Configuration Guide, Release 7.4        OL-28744-01 649
The passive client feature enables the ARP requests and responses to be exchanged between wired and wirelessclients. This feature when enabled, allows the controller to pass ARP requests from wired to wireless clientsuntil the desired wireless client gets to the RUN state.Configuring Passive Clients (GUI)Before You BeginTo configure passive clients, you must enable multicast-multicast or multicast-unicast mode.Step 1 Choose Controller >General to open the General page.Step 2 Choose one of the following options from the AP Multicast Mode drop-down list:•Unicast—Configures the controller to use the unicast method to send multicast packets. This is the default value.•Multicast—Configures the controller to use the multicast method to send multicast packets to a CAPWAP multicastgroup.Step 3 From the AP Multicast Mode drop-down list, chooseMulticast. The Multicast Group Address text box is displayed.Step 4 In the Multicast Group Address text box, enter the IP address of the multicast group.Step 5 Click Apply.Step 6 Enable global multicast mode as follows:a) Choose Controller >Multicast.b) Select the Enable Global Multicast Mode check box.Enabling the Multicast-Multicast Mode (GUI)Before You BeginTo configure passive clients, you must enable multicast-multicast or multicast-unicast mode.Step 1 Choose Controller >General to open the General page.Step 2 Choose one of the following options from the AP Multicast Mode drop-down list:•Unicast—Configures the controller to use the unicast method to send multicast packets. This is the default value.•Multicast—Configures the controller to use the multicast method to send multicast packets to a CAPWAP multicastgroup.Step 3 From the AP Multicast Mode drop-down list, choose Multicast. The Multicast Group Address text box is displayed.It is not possible to configure the AP multicast mode for Cisco Flex 7500 Series controllers because only unicastis supported.Note   Cisco Wireless LAN Controller Configuration Guide, Release 7.4650 OL-28744-01  Configuring Passive Clients (GUI)
Step 4 In the Multicast Group Address text box, enter the IP address of the multicast group.Step 5 Click Apply.Step 6 Enable global multicast mode as follows:a) Choose Controller >Multicast.b) Select the Enable Global Multicast Mode check box.Enabling the Global Multicast Mode on Controllers (GUI)Step 1 Choose Controller >Multicast to open the Multicast page.The Enable IGMP Snooping text box is highlighted only when you enable the Enable Global Multicast mode.The IGMP Timeout (seconds) text box is highlighted only when you enable the Enable IGMP Snooping textbox.NoteStep 2 Select the Enable Global Multicast Mode check box to enable the multicast mode. This step configures the controllerto use the multicast method to send multicast packets to a CAPWAP multicast group.It is not possible to configure Global Multicast Mode for Cisco Flex 7500 Series Controllers.NoteStep 3 Select the Enable IGMP Snooping check box to enable the IGMP snooping. The default value is disabled.Step 4 In the IGMP Timeout text box to set the IGMP timeout, enter a value between 30 and 7200 seconds.Step 5 Click Apply to commit your changes.Enabling the Passive Client Feature on the Controller (GUI)Step 1 Choose WLANs >WLANs >WLAN ID to open the WLANs > Edit page. By default, the General tab is displayed.Step 2 Choose the Advanced tab.Step 3 Select the Passive Client check box to enable the passive client feature.Step 4 Click Apply to commit your changes.Configuring Passive Clients (CLI)Step 1 Enable multicasting on the controller by entering this command:config network multicast global enableCisco Wireless LAN Controller Configuration Guide, Release 7.4       OL-28744-01 651Configuring Passive Clients (CLI)
The default value is disabled.Step 2 Configure the controller to use multicast to send multicast to an access point by entering this command:config network multicast mode multicast multicast_group_IP_addressStep 3 Configure passive client on a wireless LAN by entering this command:config wlan passive-client {enable |disable}wlan_idStep 4 Configure a WLAN by entering this command:config wlanStep 5 Save your changes by entering this command:save configStep 6 Display the passive client information on a particular WLAN by entering this command:show wlan 2Step 7 Verify if the passive client is associated correctly with the AP and if the passive client has moved into the DHCP requiredstate at the controller by entering this command:debug client mac_addressStep 8 Display the detailed information for a client by entering this command:show client detail mac_addressStep 9 Check if the client moves into the run state, when a wired client tries to contact the client by entering this command:debug client mac_addressStep 10 Configure and check if the ARP request is forwarded from the wired side to the wireless side by entering this command:debug arp all enable   Cisco Wireless LAN Controller Configuration Guide, Release 7.4652 OL-28744-01  Configuring Passive Clients (CLI)
CHAPTER 97Configuring Client Profiling•Prerequisites for Configuring Client Profiling, page 653•Restrictions for Configuring Client Profiling, page 653•Information About Client Profiling, page 654•Configuring Client Profiling (GUI), page 654•Configuring Client Profiling (CLI), page 654Prerequisites for Configuring Client Profiling•By default, client profiling will be disabled on all WLANs.•Client profiling is supported on access points that are in Local mode and FlexConnect mode.•Both DHCP Proxy and DHCP Bridging mode on the controller are supported.•Accounting Server configuration on the WLAN must be pointing at an ISE running 1.1 MnR or laterreleases. Cisco ACS does not support client profiling.•The type of DHCP server used does not affect client profiling.•If the DHCP_REQUEST packet contains a string that is found in the Profiled Devices list of the ISE,then the client will be profiled automatically.•The client is identified based on the MAC address sent in the Accounting request packet.•Only a MAC address should be sent as calling station ID in accounting packets when profiling is enabled.•To enable client profiling, you must enable the DHCP required flag and disable the local authenticationflag.Restrictions for Configuring Client Profiling•Profiling is not supported for clients in the following scenarios:•Clients associating with FlexConnect mode APs in Standalone mode.Cisco Wireless LAN Controller Configuration Guide, Release 7.4        OL-28744-01 653
•Clients associating with FlexConnect mode APs when local authentication is done with localswitching is enabled.•With profiling enabled for local switching FlexConnect mode APs, only VLAN override is supportedas an AAA override attribute.•While the controller parses the DHCP profiling information every time the client sends a request, theprofiling information is sent to ISE only once.Information About Client ProfilingWhen a client tries to associate with a WLAN, it is possible to determine the client type from the informationreceived in the process. The controller acts as the collector of the information and sends the ISE with therequired data in an optimal form.Configuring Client Profiling (GUI)Step 1 Choose WLANs to open the WLANs page.Step 2 Click the WLAN ID. The WLANs > Edit page appears.Step 3 Click the Advanced tab.Step 4 In the Client Profiling area, do the following:a) To profile clients based on DHCP, select the DHCP Profiling check box.b) To profile clients based on HTTP, select the HTTP Profiling check box.Step 5 Click Apply.Step 6 Click Save Configuration.Configuring Client Profiling (CLI)•Enable or disable client profiling for a WLAN based on DHCP by entering this command:config wlan profiling radius dhcp {enable |disable}wlan-id•Enable or disable client profiling in RADIUS mode for a WLAN based on HTTP, DHCP, or both byentering this command:config wlan profiling radius {dhcp |http |all} {enable |disable}wlan-idUse the all parameter to configure client profiling based on both DHCP and HTTP.Note•To see the status of client profiling on a WLAN, enter the following command:show wlan wlan-id   Cisco Wireless LAN Controller Configuration Guide, Release 7.4654 OL-28744-01  Information About Client Profiling
•To enable or disable debugging of client profiling, enter the following command:debug profiling {enable |disable}Cisco Wireless LAN Controller Configuration Guide, Release 7.4       OL-28744-01 655Configuring Client Profiling (CLI)
   Cisco Wireless LAN Controller Configuration Guide, Release 7.4656 OL-28744-01  Configuring Client Profiling (CLI)
CHAPTER 98Configuring Per-WLAN RADIUS Source Support•Prerequisites for Per-WLAN RADIUS Source Support, page 657•Restrictions for Per-WLAN RADIUS Source Support, page 657•Information About Per-WLAN RADIUS Source Support, page 657•Configuring Per-WLAN RADIUS Source Support (CLI), page 658•Monitoring the Status of Per-WLAN RADIUS Source Support (CLI), page 658Prerequisites for Per-WLAN RADIUS Source Support•You must implement appropriate rule filtering on the new identity for the authentication server (RADIUS)because the controller sources traffic only from the selected interface.Restrictions for Per-WLAN RADIUS Source Support•callStationID is always in the APMAC:SSID format to comply with 802.1X over RADIUS RFC. Thisis also a legacy behavior. Web-auth can use different formats available in the config radiuscallStationIDType command.•If AP groups or AAA override are used, the source interface remains the WLAN interface, and not whatis specified on the new AP group or RADIUS profile configuration.Information About Per-WLAN RADIUS Source SupportBy default, the controller sources all RADIUS traffic from the IP address on its management interface, whichmeans that even if a WLAN has specific RADIUS servers configured instead of the global list, the identityused is the management interface IP address.If you want to filter WLANs, you can use the callStationID that is set by RFC 3580 to be in the APMAC:SSIDformat. You can also extend the filtering on the authentication server to be on a per-WLAN source interfaceby using the NAS-IP-Address attribute.Cisco Wireless LAN Controller Configuration Guide, Release 7.4        OL-28744-01 657
When you enable the per-WLAN RADIUS source support, the controller sources all RADIUS traffic for aparticular WLAN by using the dynamic interface that is configured. Also, RADIUS attributes are modifiedaccordingly to match the identity. This feature virtualizes the controller on the per-WLAN RADIUS traffic,where each WLAN can have a separate layer 3 identity. This feature is useful in deployments that integratewith ACS Network Access Restrictions and Network Access Profiles.You can combine per-WLAN RADIUS source support with the normal RADIUS traffic source and someWLANs that use the management interface and others using the per-WLAN dynamic interface as the addresssource.Configuring Per-WLAN RADIUS Source Support (CLI)Step 1 Enter the config wlan disable wlan-id command to disable the WLAN.Step 2 Enter the following command to enable or disable the per-WLAN RADIUS source support:config wlan radius_server overwrite-interface {enable |disable}wlan-idWhen enabled, the controller uses the interface specified on the WLAN configuration as identity and source forall RADIUS related traffic on that WLAN. When disabled, the controller uses the management interface as theidentity in the NAS-IP-Address attribute. If the RADIUS server is on a directly connected dynamic interface,the RADIUS traffic will be sourced from that interface. Otherwise, the management IP address is used. In allcases, the NAS-IP-Address attribute remains the management interface, unless the feature is enabled.NoteStep 3 Enter the config wlan enable wlan-id command to enable the WLAN.You can filter requests on the RADIUS server side using CiscoSecure ACS. You can filter (accept or reject) arequest depending on the NAS-IP-Address attribute through a Network Access Restrictions rule. The filteringto be used is the CLI/DNIS filtering.NoteMonitoring the Status of Per-WLAN RADIUS Source Support (CLI)To see if the feature is enabled or disabled, enter the following command:show wlan wlan-idExampleThe following example shows that the per-WLAN RADIUS source support is enabled on WLAN 1.show wlan 1Information similar to the following is displayed:WLAN Identifier.................................. 4Profile Name..................................... exampleNetwork Name (SSID).............................. exampleStatus........................................... EnabledMAC Filtering.................................... DisabledBroadcast SSID................................... EnabledAAA Policy Override.............................. DisabledNetwork Admission Control...Radius ServersAuthentication................................ Global ServersAccounting.................................... Global Servers   Cisco Wireless LAN Controller Configuration Guide, Release 7.4658 OL-28744-01  Configuring Per-WLAN RADIUS Source Support (CLI)
Overwrite Sending Interface................... EnabledLocal EAP Authentication......................... DisabledCisco Wireless LAN Controller Configuration Guide, Release 7.4       OL-28744-01 659Monitoring the Status of Per-WLAN RADIUS Source Support (CLI)
   Cisco Wireless LAN Controller Configuration Guide, Release 7.4660 OL-28744-01  Monitoring the Status of Per-WLAN RADIUS Source Support (CLI)
CHAPTER 99Configuring Mobile Concierge•Information About Mobile Concierge, page 661•Configuring 802.11u Mobility Services Advertisement Protocol, page 663•Configuring 802.11u HotSpot, page 664Information About Mobile ConciergeMobile Concierge is a solution that enables 802.1X capable clients to interwork with external networks. TheMobile Concierge feature provides service availability information to clients and can help them to associateavailable networks.The services offered by the network can be broadly classified into two protocols:•802.11u MSAP•802.11u HotSpot 2.0Configuring Mobile Concierge (802.11u)Configuring Mobile Concierge (802.11u) (GUI)Step 1 Choose WLAN to open the WLANs page.Step 2 Hover your mouse over the blue drop-down arrow for the desired WLAN on which you want to configure the 802.11uparameters and select 802.11u. The 802.11u page appears.Step 3 Select the 802.11u Status check box to enable 802.11u on the WLAN.Step 4 In the 802.11u General Parameters area, do the following:a) Select the Internet Access check box to enable this WLAN to provide Internet services.b) From the Network Type drop-down list, choose the network type that best describes the 802.11u you want to configureon this WLAN.c) From the Network Auth Type drop-down list, choose the authentication type that you want to configure for the802.11u parameters on this network.Cisco Wireless LAN Controller Configuration Guide, Release 7.4        OL-28744-01 661
d) In the HESSID box, enter the homogenous extended service set identifier (HESSID) value. The HESSID is a 6-octetMAC address that identifies the homogeneous ESS.e) If the IP address is in the IPv4 format, then from the IPv4 Type drop-down list, choose the IPv4 address type.f) From the IPv6 Type drop-down list, choose whether you want to make the IPv6 address type available or not.Step 5 In the OUI List area, do the following:a) In the OUI text box, enter the Organizationally Unique Identifier, which can be a hexadecimal number representedin 3 or 5 bytes (6 or 10 characters). For example, AABBDF.b) Select the Is Beacon check box to enable the OUI beacon responses.You can have a maximum of 3 OUIs with this fieldenabled.Notec) From the OUI Index drop-down list, choose a value from 1 to 32. The default is 1.d) Click Add to add the OUI entry to the WLAN.To remove this entry, hover your mouse pointer over the blue drop-down image and choose Remove.Step 6 In the Domain List area, do the following:a) In the Domain Name box, enter the domain name that is operating in the WLAN.b) From the Domain Index drop-down list, choose an index for the domain name from 1 to 32. The default is 1.c) Click Add to add the domain entry to the WLAN.To remove this entry, hover your mouse pointer over the blue drop-down image and choose Remove.Step 7 In the Realm List area, do the following:a) In the Realm text box, enter the realm name that you can assign to the WLAN.b) From the Realm Index drop-down list, choose an index for the realm from 1 to 32. The default is 1.c) Click Add to add the domain entry to this WLAN.To remove this entry, hover your mouse pointer over the blue drop-down image and choose Remove.Step 8 In the Cellular Network Information List area, do the following:a) In the Country Code text box, enter the 3-character mobile country code.b) From the CellularIndex drop-down list, choose a value between 1 and 32. The default is 1.c) In the Network Code text box, enter the character network code. The network code can be 2 or 3 characters.d) Click Add to add the cellular network information to the WLAN.To remove this entry, hover your mouse pointer over the blue drop-down image and select Remove.Step 9 Click Apply.Configuring Mobile Concierge (802.11u) (CLI)•To enable or disable 802.11u on a WLAN, enter this command:config wlan hotspot dot11u {enable |disable}wlan-id•To add or delete information about a third generation partnership project's cellular network, enter thiscommand:config wlan hotspot dot11u 3gpp-info {add index mobile-country-code network-code wlan-id |deleteindex wlan-id}•To configure the domain name for the entity operating in the 802.11u network, enter this command:   Cisco Wireless LAN Controller Configuration Guide, Release 7.4662 OL-28744-01  Information About Mobile Concierge
config wlan hotspot dot11u domain {{{add |modify}wlan-id domain-index domain-name} | {deletewlan-id domain-index}}•To configure a homogenous extended service set identifier (HESSID) value for a WLAN, enter thiscommand:config wlan hotspot dot11u hessid hessid wlan-idThe HESSID is a 6-octet MAC address that identifies the homogeneous ESS.•To configure the IP address availability type for the IPv4 and IPv6 IP addresses on the WLAN, enterthis command:config wlan hotspot dot11u ipaddr-type ipv4-type ipv6-type wlan-id•To configure the network authentication type, enter this command:config wlan hotspot dot11u auth-type network-auth wlan-id•To configure the Roaming Consortium OI list, enter this command:config wlan hotspot dot11u roam-oi {{{add |modify}wlan-id oi-index oi is-beacon} | {delete wlan-idoi-index}}•To configure the 802.11u network type and internet access, enter this command:config wlan hotspot dot11u network-type wlan-id network-type internet-access•To configure the realm for the WLAN, enter this command:config wlan hotspot dot11u nai-realm {{{add |modify}realm-name wlan-id realm-index realm-name| {delete realm-name wlan-id realm-index}}•To configure the authentication method for the realm, enter this command:config wlan hotspot dot11u nai-realm {add |modify}auth-method wlan-id realm-index eap-indexauth-index auth-method auth-parameter•To delete the authentication method for the realm, enter this command:config wlan hotspot dot11u nai-realm delete auth-method wlan-id realm-index eap-index auth-index•To configure the extensible authentication protocol (EAP) method for the realm, enter this command:config wlan hotpspot dot11u nai-realm {add |modify}eap-method wlan-id realm-index eap-indexeap-method•To delete the EAP method for the realm, enter this command:config wlan hotspot dot11u nai-realm delete eap-method wlan-id realm-index eap-indexConfiguring 802.11u Mobility Services Advertisement ProtocolInformation About 802.11u MSAPMSAP (Mobility Services Advertisement Protocol) is designed to be used primarily by mobile devices thatare configured with a set of policies for establishing network services. These services are available for devicesthat offer higher-layer services, or network services that are enabled through service providers.Service advertisements use MSAP to provide services to mobile devices prior to association to a Wi-Fi accessnetwork. This information is conveyed in a service advertisement. A single-mode or dual-mode mobile devicequeries the network for service advertisements before association. The device's network discovery and theselection function may use the service advertisements in its decision to join the network.Cisco Wireless LAN Controller Configuration Guide, Release 7.4       OL-28744-01 663Configuring 802.11u Mobility Services Advertisement Protocol
Configuring 802.11u MSAP (GUI)Step 1 Choose WLAN to open the WLANs page.Step 2 Hover your mouse over the blue drop-down arrow for the desired WLAN on which you want to configure the MSAPparameters and select Service Advertisements. The Service Advertisement page appears.Step 3 Enable the service advertisements.Step 4 Enter the server index for this WLAN. The server index field uniquely identifies an MSAP server instance serving avenue that is reachable through the BSSID.Step 5 Click Apply.Configuring MSAP (CLI)•To enable or disable MSAP on a WLAN, enter this command:config wlan hotspot msap {enable |disable}wlan-id•To assign a server ID, enter this command:config wlan hotspot msap server-id server-id wlan-idConfiguring 802.11u HotSpotInformation About 802.11u HotSpotThis feature, which enables IEEE 802.11 devices to interwork with external networks, is typically found inhotspots or other public networks irrespective of whether the service is subscription based or free.The interworking service aids network discovery and selection, enabling information transfer from externalnetworks. It provides information to the stations about the networks prior to association. Interworking notonly helps users within the home, enterprise, and public access, but also assists manufacturers and operatorsto provide common components and services for IEEE 802.11 customers. These services are configured ona per WLAN basis on the controller.Configuring 802.11u HotSpot (GUI)Step 1 Choose WLAN to open the WLANs page.Step 2 Hover your mouse over the blue drop-down arrow for the desired WLAN on which you want to configure the HotSpotparameters and choose HotSpot. The WLAN > HotSpot 2.0 page appears.Step 3 On the WLAN > HotSpot 2.0 page, enable HotSpot2.Step 4 To set the WAN link parameters, do the following:   Cisco Wireless LAN Controller Configuration Guide, Release 7.4664 OL-28744-01  Configuring 802.11u HotSpot
a) From the WAN Link Status drop-down list, choose the status. The default is the Not Configured status.b) From the WAN Symmetric Link Status drop-down list, choose the status as either Different or Same.c) Enter the WAN Downlink and Uplink speeds. The maximum value is 4,294,967,295 kbps.Step 5 In the Operator Name List area, do the following:a) In the Operator Name text box, enter the name of the 802.11 operator.b) From the Operator index drop-down list, choose an index value between 1 and 32 for the operator.c) In the Language Code text box, enter an ISO-14962-1997 encoded string defining the language. This string is athree-character language code.d) Click Add to add the operator details. The operator details are displayed in a tabular form. To remove an operator,hover your mouse pointer over the blue drop-down arrow and choose Remove.Step 6 In the Port Config List area, do the following:a) From the IP Protocol drop-down list, choose the IP protocol that you want to enable.b) From the Port No drop-down list, choose the port number that is enabled on the WLAN.c) From the Status drop-down list, choose the status of the port.d) From the Index drop-down list, choose an index value for the port configuration.e) Click Add to add the port configuration parameters. To remove a port configuration list, hover your mouse pointerover the blue drop-down arrow and choose Remove.Step 7 Click Apply.Configuring HotSpot 2.0 (CLI)•To enable or disable HotSpot2 on a WLAN, enter this command:config wlan hotspot hs2 {enable |disable}•To configure the operator name on a WLAN, enter this command:config wlan hotspot hs2 operator-name {add |modify}wlan-id index operator-name lang-codeThe following options are available:•wlan-id—The WLAN ID on which you want to configure the operator-name.•index—The operator index of the operator. The range is 1 to 32.•operator-name—The name of the 802.11an operator.•lang-code—The language used. An ISO-14962-1997 encoded string defining the language. Thisstring is a three character language code. Enter the first three letters of the language in English(For example: eng for English).Press the tab key after entering a keyword or argument to get a list of valid values forthe command.TipCisco Wireless LAN Controller Configuration Guide, Release 7.4       OL-28744-01 665Configuring 802.11u HotSpot
•To delete the operator name, enter this command:config wlan hotspot hs2 operator-name delete wlan-id index•To configure the port configuration parameters, enter this command:config wlan hotspot hs2 port-config {add |modify}wlan-id index ip-protocol port-number•To delete a port configuration, enter this command:config wlan hotspot hs2 port-config delete wlan-id index•To configure the WAN metrics, enter this command:config wlan hotspot hs2 wan-metrics wlan-id link-status symet-link downlink-speed uplink-speedThe values are as follows:•link-status—The link status. The valid range is 1 to 3.•symet-link—The symmetric link status. For example, you can configure the uplink and downlinkto have different speeds or same speeds.•downlink-speed—The downlink speed. The maximum value is 4,194,304 kbps.•uplink-speed—The uplink speed. The maximum value is 4,194,304 kbps.•To clear all HotSpot configurations, enter this command:config wlan hotspot clear-all wlan-id•To configure the Access Network Query Protocol (ANQP) 4-way messaging, enter this command:config advanced hotspot anqp-4way {enable |disable |threshold value}•To configure the ANQP comeback delay value in terms of TUs, enter this command:config advanced hotpsot cmbk-delay value•To configure the gratuitous ARP (GARP) forwarding to wireless networks, enter this command:config advanced hotpsot garp {enable |disable}•To limit the number of GAS request action frames to be sent to the controller by an AP in a given interval,enter this command:config advanced hotspot gas-limit {enable num-of-GAS-required interval |disable}Configuring Access Points for HotSpot2 (GUI)When HotSpot2 is configured, the access points that are part of the network must be configured to supportHotSpot2.Step 1 Click Wireless > All APs to open the All APs page.Step 2 Click the AP Name link to configure the HotSpot parameters on the desired access point. The AP Details page appears.Step 3 Under the General Tab, configure the following parameters:•Venue Group—The venue category that this access point belongs to. The following options are available:   Cisco Wireless LAN Controller Configuration Guide, Release 7.4666 OL-28744-01  Configuring 802.11u HotSpot
Unspecified◦◦Assembly◦Business◦Educational◦Factory and Industrial◦Institutional◦Mercantile◦Residential◦Storage◦Utility and Misc◦Vehicular◦Outdoor•Venue Type—Depending on the venue category selected above, the venue type drop-down list displays optionsfor the venue type.•Venue Name—Venue name that you can provide to the access point. This name is associated with the BSS. Thisis used in cases where the SSID does not provide enough information about the venue.•Language—The language used. An ISO-14962-1997 encoded string defining the language. This is a three characterlanguage code. Enter the first three letters of the language in English (For example, eng for English).Step 4 Click Apply.Configuring Access Points for HotSpot2 (CLI)•config ap venue add venue-name venue-group venue-type lang-code ap-name–Adds the venue detailsto the access point indicating support for HotSpot2.The values are as follows:◦venue-name—Name of the venue where this access point is located.◦venue-group—Category of the venue. See the following table.◦venue-type—Type of the venue. Depending on the venue-group chosen, select the venue type. Seethe following table.◦lang-code—The language used. An ISO-14962-1997 encoded string defining the language. Thisis a three character language code. Enter the first three letters of the language in English (Forexample: eng for English)◦ap-name—Access point name.Cisco Wireless LAN Controller Configuration Guide, Release 7.4       OL-28744-01 667Configuring 802.11u HotSpot
Press the tab key after entering a keyword or argument to get a list of valid values forthe command.Tip•config ap venue delete ap-name—Deletes the venue related information from the access point.Table 20: Venue Group MappingVenue Type for GroupValueVenue Group Name0UNSPECIFIED•0—UNSPECIFIED ASSEMBLY•1—ARENA•2—STADIUM•3—PASSENGER TERMINAL (E.G., AIRPORT, BUS,FERRY, TRAIN STATION)•4—AMPHITHEATER•5—AMUSEMENT PARK•6—PLACE OF WORSHIP•7—CONVENTION CENTER•8—LIBRARY•9—MUSEUM•10—RESTAURANT•11—THEATER•12—BAR•13—COFFEE SHOP•14—ZOO OR AQUARIUM•15—EMERGENCY COORDINATION CENTER1ASSEMBLY   Cisco Wireless LAN Controller Configuration Guide, Release 7.4668 OL-28744-01  Configuring 802.11u HotSpot
Venue Type for GroupValueVenue Group Name•0—UNSPECIFIED BUSINESS•1—DOCTOR OR DENTIST OFFICE•2—BANK•3—FIRE STATION•4—POLICE STATION•6—POST OFFICE•7—PROFESSIONAL OFFICE•8—RESEARCH AND DEVELOPMENT FACILITY•9—ATTORNEY OFFICE2BUSINESS•0—UNSPECIFIED EDUCATIONAL•1—SCHOOL, PRIMARY•2—SCHOOL, SECONDARY•3—UNIVERSITY OR COLLEGE3EDUCATIONAL•0—UNSPECIFIED FACTORY AND INDUSTRIAL•1—FACTORY4FACTORY-INDUSTRIAL•0—UNSPECIFIED INSTITUTIONAL•1—HOSPITAL•2—LONG-TERM CARE FACILITY (E.G., NURSINGHOME, HOSPICE, ETC.)•3—ALCOHOL AND DRUG RE-HABILITATIONCENTER•4—GROUP HOME•5—PRISON OR JAIL5INSTITUTIONALCisco Wireless LAN Controller Configuration Guide, Release 7.4       OL-28744-01 669Configuring 802.11u HotSpot
Venue Type for GroupValueVenue Group Name•0—UNSPECIFIED MERCANTILE•1—RETAIL STORE•2—GROCERY MARKET•3—AUTOMOTIVE SERVICE STATION•4—SHOPPING MALL•5—GAS STATION6MERCANTILE•0—UNSPECIFIED RESIDENTIAL•1—PRIVATE RESIDENCE•2—HOTEL OR MOTEL•3—DORMITORY•4—BOARDING HOUSE7RESIDENTIALUNSPECIFIED STORAGE8STORAGE0—UNSPECIFIED UTILITY AND MISCELLANEOUS9UTILITY-MISC•0—UNSPECIFIED VEHICULAR•1—AUTOMOBILE OR TRUCK•2—AIRPLANE•3—BUS•4—FERRY•5—SHIP OR BOAT•6—TRAIN•7—MOTOR BIKE10VEHICULAR   Cisco Wireless LAN Controller Configuration Guide, Release 7.4670 OL-28744-01  Configuring 802.11u HotSpot
Venue Type for GroupValueVenue Group Name•0—UNSPECIFIED OUTDOOR•1—MUNI-MESH NETWORK•2—CITY PARK•3—REST AREA•4—TRAFFIC CONTROL•5—BUS STOP•6—KIOSK11OUTDOORCisco Wireless LAN Controller Configuration Guide, Release 7.4       OL-28744-01 671Configuring 802.11u HotSpot
   Cisco Wireless LAN Controller Configuration Guide, Release 7.4672 OL-28744-01  Configuring 802.11u HotSpot
CHAPTER 100Configuring Assisted Roaming•Restrictions for Assisted Roaming, page 673•Information About Assisted Roaming, page 673•Configuring Assisted Roaming (CLI), page 674Restrictions for Assisted Roaming•This feature must be implemented only if you are using one controller. The assisted roaming feature isnot supported across multiple controllers.•This feature is supported only on 802.11n capable indoor access points. For a single band configuration,a maximum of 6 neighbors are visible in a neighbor list. For dual band configuration, a maximum of 12neighbors are visible.•You can configure assisted roaming only using the controller CLI. Configuration using the controllerGUI is not supported.Information About Assisted RoamingThe 802.11k standard allows clients to request neighbor reports containing information about known neighboraccess points that are candidates for a service set transition. The use of the 802.11k neighbor list can limit theneed for active and passive scanning.The assisted roaming feature is based on an intelligent and client optimized neighbor list.Unlike the Cisco Client Extension (CCX) neighbor list, the 802.11k neighbor list is generated dynamicallyon-demand and is not maintained on the controller. The 802.11k neighbor list is based on the location of theclients without requiring the mobility services engine (MSE). Two clients on the same controller but differentAPs can have different neighbor lists delivered depending on their individual relationship with the surroundingAPs.By default, the neighbor list contains only neighbors in the same band with which the client is associated.However, a switch exists that allows 802.11k to return neighbors in both bands.Cisco Wireless LAN Controller Configuration Guide, Release 7.4        OL-28744-01 673
Clients send requests for neighbor lists only after associating with the APs that advertize the RRM (RadioResource Management) capability information element (IE) in the beacon. The neighbor list includesinformation about BSSID, channel, and operation details of the neighboring radios.Assembling and Optimizing the Neighbor ListWhen the controller receives a request for an 802.11k neighbor list, the following occurs:1The controller searches the RRM neighbor table for a list of neighbors on the same band as the AP withwhich the client is currently associated with.2The controller checks the neighbors according to the RSSI (Received Signal Strength Indication) betweenthe APs, the current location of the present AP, the floor information of the neighboring AP from CiscoPrime Infrastructure, and roaming history information on the controller to reduce the list of neighbors tosix per band. The list is optimized for APs on the same floor.Assisted Roaming for Non-802.11k ClientsIt is also possible to optimize roaming for non-802.11k clients. You can generate a prediction neighbor listfor each client without the client requiring to send an 802.11k neighbor list request. When this is enabled ona WLAN, after each successful client association/reassociation, the same neighbor list optimization is appliedon the non-802.11k client to generate the neighbor list and store the list in the mobile station software datastructure. Clients at different locations have different lists because the client probes are seen with differentRSSI values by different neighbors. Because clients usually probe before any association or reassociation,this list is constructed with the most updated probe data and predicts the next AP that the client is likely toroam to.We discourage clients from roaming to those less desirable neighbors by denying association if the associationrequest to an AP does not match the entries on the stored prediction neighbor list.Similar to aggressive load balancing, there is a switch to turn on the assisted roaming feature both on aper-WLAN basis and globally. The following options are available:•Denial count—Maximum number of times a client is refused association.•Prediction threshold—Minimum number of entries required in the prediction list for the assisted roamingfeature to be activated.Because both load balancing and assisted roaming are designed to influence the AP that a client associateswith, it is not possible to enable both the options at the same time on a WLAN.Configuring Assisted Roaming (CLI)•Configure an 802.11k neighbor list for a WLAN by entering this command:config wlan assisted-roaming neighbor-list {enable |disable}wlan-id•Configure neighbor floor label bias by entering this command:config assisted-roaming floor-bias dBm•Configure a dual-band 802.11k neighbor list for a WLAN by entering this command:config wlan assisted-roaming dual-list {enable |disable}wlan-id   Cisco Wireless LAN Controller Configuration Guide, Release 7.4674 OL-28744-01  Configuring Assisted Roaming (CLI)
Default is the band which the client is using to associate.Note•Configure assisted roaming prediction list feature for a WLAN by entering this command:config wlan assisted-roaming prediction {enable |disable}wlan-idA warning message is displayed and load-balancing is disabled for the WLAN if load-balancing is alreadyenabled for the WLAN.Note•Configure the minimum number of predicted APs required for the prediction list feature to be activatedby entering this command:config assisted-roaming prediction-minimum countIf the number of the AP in the prediction assigned to the client is less than the number that you specify,the assisted roaming feature will not apply on this roam.Note•Configure the maximum number of times a client can be denied association if the association request issent to an AP does not match any AP on the prediction list by entering this command:config assisted-roaming denial-maximum count•Debug a client for assisted roaming by entering this command:debug mac addr client-mac-addr•Configure debugging of all of the 802.11k events by entering this command:debug 11k all {enable |disable}•Configure debugging of neighbor details by entering this command:debug 11k detail {enable |disable}•Configure debugging of 802.11k errors by entering this command:debug 11k errors {enable |disable}•See if the neighbor requests are being received by entering this command:debug 11k events {enable |disable}•Configure debugging of the roaming history of clients by entering this command:debug 11k history {enable |disable}•Configure debugging of 802.11k optimizations by entering this command:debug 11k optimization {enable |disable}•Get details of client roaming parameters that are to be imported for offline simulation use by enteringthis command:debug 11k simulation {enable |disable}Cisco Wireless LAN Controller Configuration Guide, Release 7.4       OL-28744-01 675Configuring Assisted Roaming (CLI)
   Cisco Wireless LAN Controller Configuration Guide, Release 7.4676 OL-28744-01  Configuring Assisted Roaming (CLI)
PART VIControlling Lightweight Access Points•Using Access Point Communication Protocols, page 679•Searching for Access Points, page 687•Searching for Access Point Radios, page 695•Configuring Global Credentials for Access Points, page 697•Configuring Authentication for Access Points, page 701•Configuring Embedded Access Points, page 705•Converting Autonomous Access Points to Lightweight Mode, page 707•Configuring Packet Capture, page 729•Configuring OfficeExtend Access Points, page 733•Using Cisco Workgroup Bridges, page 751•Using Non-Cisco Workgroup Bridges, page 757•Configuring Backup Controllers, page 759•Configuring High Availability, page 765•Configuring Failover Priority for Access Points, page 773•Configuring AP Retransmission Interval and Retry Count, page 777•Configuring Country Codes, page 781•Optimizing RFID Tracking on Access Points, page 785
•Configuring Probe Request Forwarding, page 787•Retrieving the Unique Device Identifier on Controllers and Access Points, page 789•Performing a Link Test, page 791•Configuring Link Latency, page 795•Configuring the TCP MSS, page 799•Configuring Power Over Ethernet, page 801•Viewing Clients, page 807•Configuring LED States for Access Points, page 809•Configuring Access Points with Dual-Band Radios, page 813
CHAPTER 101Using Access Point Communication Protocols•Information About Access Point Communication Protocols, page 679•Restrictions for Access Point Communication Protocols, page 680•Configuring Data Encryption, page 680•Viewing CAPWAP Maximum Transmission Unit Information, page 683•Debugging CAPWAP, page 683•Controller Discovery Process, page 684•Verifying that Access Points Join the Controller, page 685Information About Access Point Communication ProtocolsCisco lightweight access points use the IETF standard Control and Provisioning of Wireless Access PointsProtocol (CAPWAP) to communicate with the controller and other lightweight access points on the network.CAPWAP, which is based on LWAPP, is a standard, interoperable protocol that enables a controller to managea collection of wireless access points. CAPWAP is implemented in controller for these reasons:•To provide an upgrade path from Cisco products that use LWAPP to next-generation Cisco productsthat use CAPWAP•To manage RFID readers and similar devices•To enable controllers to interoperate with third-party access points in the futureLWAPP-enabled access points can discover and join a CAPWAP controller, and conversion to a CAPWAPcontroller is seamless. For example, the controller discovery process and the firmware downloading processwhen using CAPWAP are the same as when using LWAPP. The one exception is for Layer 2 deployments,which are not supported by CAPWAP.You can deploy CAPWAP controllers and LWAPP controllers on the same network. The CAPWAP-enabledsoftware allows access points to join either a controller running CAPWAP or LWAPP. The only exceptionsare that the Cisco Aironet 1040, 1140, 1260, 3500, and 3600 Series Access Points, which support onlyCAPWAP and join only controllers that run CAPWAP. For example, an 1130 series access point can join acontroller running either CAPWAP or LWAPP where an1140 series access point can join only a controllerthat runs CAPWAP.Cisco Wireless LAN Controller Configuration Guide, Release 7.4        OL-28744-01 679
The following are some guidelines that you must follow for access point communication protocols:•If your firewall is currently configured to allow traffic only from access points using LWAPP, you mustchange the rules of the firewall to allow traffic from access points using CAPWAP.•Ensure that the CAPWAP UDP ports 5246 and 5247 (similar to the LWAPP UDP ports 12222 and12223) are enabled and are not blocked by an intermediate device that could prevent an access pointfrom joining the controller.•If access control lists (ACLs) are in the control path between the controller and its access points, youneed to open new protocol ports to prevent access points from being stranded.Restrictions for Access Point Communication Protocols•On virtual controller platforms, per-client downstream rate limiting is not supported in FlexConnectcentral switching.•Rate-limiting is applicable to all traffic destined to the CPU from either direction (wireless or wired).We recommend that you always run the controller with the default config advanced rate enable commandin effect to rate limit traffic to the controller and protect against denial-of-service (DoS) attacks. Youcan use the config advanced rate disable command to stop rate-limiting of Internet Control MessageProtocol (ICMP) echo responses for testing purposes. However, we recommend that you reapply theconfig advanced rate enable command after testing is complete.•Ensure that the controllers are configured with the correct date and time. If the date and time configuredon the controller precedes the creation and installation date of certificates on the access points, the accesspoint fails to join the controller.Configuring Data EncryptionCisco 5500 Series Controllers enable you to encrypt CAPWAP control packets (and optionally, CAPWAPdata packets) that are sent between the access point and the controller using Datagram Transport Layer Security(DTLS). DTLS is a standards-track Internet Engineering Task Force (IETF) protocol based on TLS. CAPWAPcontrol packets are management packets exchanged between a controller and an access point while CAPWAPdata packets encapsulate forwarded wireless frames. CAPWAP control and data packets are sent over separateUDP ports: 5246 (control) and 5247 (data). If an access point does not support DTLS data encryption, DTLSis enabled only for the control plane, and a DTLS session for the data plane is not established.Guidelines for Data Encryption•Cisco 1130 and 1240 series access points support DTLS data encryption with software-based encryption.•Cisco 1040, 1140, 1250, 1260, 1530, 1550, 1600, 2600, 3500, and 3600 series access points supportDTLS data encryption with hardware-based encryption•Cisco Aironet 1552 and 1522 outdoor access points support data DTLS.•DTLS data encryption is not supported on Cisco Aironet 700 Series Access Points.•DTLS data encryption is enabled automatically for OfficeExtend access points but disabled by defaultfor all other access points. Most access points are deployed in a secure network within a company   Cisco Wireless LAN Controller Configuration Guide, Release 7.4680 OL-28744-01  Restrictions for Access Point Communication Protocols
building, so data encryption is not necessary. In contrast, the traffic between an OfficeExtend accesspoint and the controller travels through an unsecure public network, so data encryption is more importantfor these access points. When data encryption is enabled, traffic is encrypted at the access point beforeit is sent to the controller and at the controller before it is sent to the client.•Encryption limits throughput at both the controller and the access point, and maximum throughput isdesired for most enterprise networks.•In a Cisco unified local wireless network environment, do not enable DTLS on the Cisco 1130 and 1240access points, as it may result in severe throughput degradation and may render the APs unusable.See the OfficeExtend Access Points section for more information on OfficeExtend access points.•You can use the controller to enable or disable DTLS data encryption for a specific access point or forall access points.•The availability of data DTLS is as follows:◦The Cisco 5500 Series Controller will be available with two licenses options: One that allows dataDTLS without any license requirements and another image that requires a license to use data DTLS.See the Upgrading or Downgrading DTLS Images for Cisco 5500 Series Controllers section. Theimages for the DTLS and licensed DTLS images are as follows:Licensed DTLS—AS_5500_LDPE_x_x_x_x.aesNon licensed DTLS—AS_5500_x_x_x_x.aes◦Cisco 2500, Cisco WiSM2—By default, these platforms do not contain DTLS. To turn on dataDTLS, you must install a license. These platforms have a single image with data DTLS turned off.To use data DTLS you must have a license.•If your controller does not have a data DTLS license and if the access point associated with the controllerhas DTLS enabled, the data path will be unencrypted.•Non-Russian customers using Cisco 5508 Series Controller do not need data DTLS license. Howeverall customers using WISM2 and Cisco 2500 Series Controllers must enable data DTLS.Upgrading or Downgrading DTLS Images for Cisco 5500 Series ControllersStep 1 The upgrade operation fails on the first attempt with a warning indicating that the upgrade to a licensed DTLS image isirreversible.Do not reboot the controller after Step1.NoteStep 2 On a subsequent attempt, the license is applied and the image is successfully updated.Guidelines When Upgrading to or from a DTLS Image•You cannot install a regular image (nonlicensed data DTLS) once a licensed data DTLS image is installed.•You can upgrade from one licensed DTLS image to another licensed DTLS image.Cisco Wireless LAN Controller Configuration Guide, Release 7.4       OL-28744-01 681Configuring Data Encryption
•You can upgrade from a regular image (DTLS) to a licensed DTLS image in a two step process.•You can use the show sysinfo command to verify the LDPE image, before and after the image upgrade.Configuring Data Encryption (GUI)Ensure that the base license is installed on the Cisco 5500 Series Controller. Once the license is installed, youcan enable data encryption for the access points.Step 1 Choose Wireless >Access Points >All APs to open the All APs page.Step 2 Click the name of the access point for which you want to enable data encryption.Step 3 Choose the Advanced tab to open the All APs > Details for (Advanced) page.Step 4 Select the Data Encryption check box to enable data encryption for this access point or unselect it to disable this feature.The default value is unselected.Changing the data encryption mode requires the access points to rejoin the controller.NoteStep 5 Click Apply.Step 6 Click Save Configuration.Configuring Data Encryption (CLI)In images without a DTLS license, the config or show commands are not available.NoteTo enable DTLS data encryption for access points on the controller using the controller CLI, follow thesesteps:Step 1 Enable or disable data encryption for all access points or a specific access point by entering this command:config ap link-encryption {enable |disable} {all |Cisco_AP}The default value is disabled.Changing the data encryption mode requires the access points to rejoin the controller.NoteStep 2 When prompted to confirm that you want to disconnect the access point(s) and attached client(s), enter Y.Step 3 Enter the save config command to save your configuration.Step 4 See the encryption state of all access points or a specific access point by entering this command:show ap link-encryption {all |Cisco_AP}This command also shows authentication errors, which tracks the number of integrity check failures, and replay errors,which tracks the number of times that the access point receives the same packet.Step 5 See a summary of all active DTLS connections by entering this command:   Cisco Wireless LAN Controller Configuration Guide, Release 7.4682 OL-28744-01  Configuring Data Encryption
show dtls connectionsIf you experience any problems with DTLS data encryption, enter the debug dtls {all |event |trace |packet}{enable |disable} command to debug all DTLS messages, events, traces, or packets.NoteViewing CAPWAP Maximum Transmission Unit InformationSee the maximum transmission unit (MTU) for the CAPWAP path on the controller by entering this command:show ap config general Cisco_APThe MTU specifies the maximum size of any packet (in bytes) in a transmission.Information similar to the following appears:Cisco AP Identifier.............................. 9Cisco AP Name.................................... Maria-1250Country code..................................... US - United StatesRegulatory Domain allowed by Country............. 802.11bg:-A 802.11a:-AAP Country code.................................. US - United StatesAP Regulatory Domain............................. 802.11bg:-A 802.11a:-ASwitch Port Number .............................. 1MAC Address...................................... 00:1f:ca:bd:bc:7cIP Address Configuration......................... DHCPIP Address....................................... 1.100.163.193IP NetMask....................................... 255.255.255.0CAPWAP Path MTU.................................. 1485Debugging CAPWAPUse these commands to obtain CAPWAP debug information:•debug capwap events {enable |disable}—Enables or disables debugging of CAPWAP events.•debug capwap errors {enable |disable}—Enables or disables debugging of CAPWAP errors.•debug capwap detail {enable |disable}—Enables or disables debugging of CAPWAP details.•debug capwap info {enable |disable}—Enables or disables debugging of CAPWAP information.•debug capwap packet {enable |disable}—Enables or disables debugging of CAPWAP packets.•debug capwap payload {enable |disable}—Enables or disables debugging of CAPWAP payloads.•debug capwap hexdump {enable |disable}—Enables or disables debugging of the CAPWAPhexadecimal dump.•debug capwap dtls-keepalive {enable |disable}—Enables or disables debugging of CAPWAP DTLSdata keepalive packets.Cisco Wireless LAN Controller Configuration Guide, Release 7.4       OL-28744-01 683Viewing CAPWAP Maximum Transmission Unit Information
Controller Discovery ProcessIn a CAPWAP environment, a lightweight access point discovers a controller by using CAPWAP discoverymechanisms and then sends the controller a CAPWAP join request. The controller sends the access point aCAPWAP join response allowing the access point to join the controller. When the access point joins thecontroller, the controller manages its configuration, firmware, control transactions, and data transactions.The following are some guidelines for the controller discovery process:•Upgrade and downgrade paths from LWAPP to CAPWAP or from CAPWAP to LWAPP are supported.An access point with an LWAPP image starts the discovery process in LWAPP. If it finds an LWAPPcontroller, it starts the LWAPP discovery process to join the controller. If it does not find a LWAPPcontroller, it starts the discovery in CAPWAP. If the number of times that the discovery process startswith one discovery type (CAPWAP or LWAPP) exceeds the maximum discovery count and the accesspoint does not receive a discovery response, the discovery type changes to the other type. For example,if the access point does not discover the controller in LWAPP, it starts the discovery process in CAPWAP.•If an access point is in the UP state and its IP address changes, the access point tears down the existingCAPWAP tunnel and rejoins the controller.•To configure the IP addresses that the controller sends in its CAPWAP discovery responses, use theconfig network ap-discovery nat-ip-only {enable |disable} command.•Access points must be discovered by a controller before they can become an active part of the network.The lightweight access points support the following controller discovery processes:•Layer 3 CAPWAP or LWAPP discovery—This feature can be enabled on different subnets fromthe access point and uses IP addresses and UDP packets rather the MAC addresses used by Layer2 discovery.•Locally stored controller IP address discovery—If the access point was previously associated to acontroller, the IP addresses of the primary, secondary, and tertiary controllers are stored in theaccess point’s nonvolatile memory. This process of storing controller IP addresses on an accesspoint for later deployment is called priming the access point.•DHCP server discovery—This feature uses DHCP option 43 to provide controller IP addresses tothe access points. Cisco switches support a DHCP server option that is typically used for thiscapability. For more information about DHCP option 43, see the Using DHCP Option 43 andDHCP Option 60 section.•DNS discovery—The access point can discover controllers through your domain name server(DNS). You must configure your DNS to return controller IP addresses in response toCISCO-LWAPP-CONTROLLER.localdomain or CISCO-CAPWAP-CONTROLLER.localdomain,where localdomain is the access point domain name. When an access point receives an IP addressand DNS information from a DHCP server, it contacts the DNS to resolveCISCO-LWAPP-CONTROLLER.localdomain or CISCO-CAPWAP-CONTROLLER.localdomain.When the DNS sends a list of controller IP addresses, the access point sends discovery requeststo the controllers.   Cisco Wireless LAN Controller Configuration Guide, Release 7.4684 OL-28744-01  Controller Discovery Process
Restrictions for Controller Discovery Process•During the discovery process, the 1040, 1140, 1260, 3500, and 3600 series access points will only queryfor Cisco CAPWAP Controllers. It will not query for LWAPP controllers. If you want these accesspoints to query for both LWAPP and CAPWAP controllers then you need to update the DNS.•Ensure that the controller is set to the current time. If the controller is set to a time that has alreadyoccurred, the access point might not join the controller because its certificate may not be valid for thattime.Verifying that Access Points Join the ControllerWhen replacing a controller, ensure that access points join the new controller.Verifying that Access Points Join the Controller (GUI)Step 1 Configure the new controller as a master controller as follows:a) Choose Controller >Advanced >Master Controller Mode to open the Master Controller Configuration page.b) Select the Master Controller Mode check box.c) Click Apply to commit your changes.d) Click Save Configuration to save your changes.Step 2 (Optional) Flush the ARP and MAC address tables within the network infrastructure.Step 3 Restart the access points.Step 4 Once all the access points have joined the new controller, configure the controller not to be a master controller byunselecting the Master Controller Mode check box on the Master Controller Configuration page.Verifying that Access Points Join the Controller (CLI)Step 1 Configure the new controller as a master controller by entering this command:config network master-base enableStep 2 (Optional) Flush the ARP and MAC address tables within the network infrastructure.Step 3 Restart the access points.Step 4 Configure the controller not to be a master controller after all the access points have joined the new controller by enteringthis command:config network master-base disableCisco Wireless LAN Controller Configuration Guide, Release 7.4       OL-28744-01 685Verifying that Access Points Join the Controller
   Cisco Wireless LAN Controller Configuration Guide, Release 7.4686 OL-28744-01  Verifying that Access Points Join the Controller
CHAPTER 102Searching for Access Points•Information About Searching for Access Points, page 687•Searching the AP Filter (GUI), page 687•Monitoring the Interface Details, page 690•Searching for Access Point Radios, page 692Information About Searching for Access PointsYou can search for specific access points in the list of access points on the All APs page. To do so, you createa filter to display only access points that meet certain criteria (such as MAC address, status, access point mode,and certificate type). This feature is especially useful if your list of access points spans multiple pages,preventing you from viewing them all at once.Searching the AP Filter (GUI)Step 1 Choose Monitor >Access Point Summary>All APs >Details to open the All APs page.This page lists all of the access points joined to the controller. For each access point, you can see its name, MAC address,uptime, status, operating mode, certificates, OfficeExtend access point status, and access point submode.The total number of access points appears in the upper right-hand corner of the page. If the list of access points spansmultiple pages, you can access these pages by clicking the page number links. Each page shows up to 20 access points.Step 2 Click Change Filter to open the Search AP dialog box.Step 3 Select one or more of the following check boxes to specify the criteria used when displaying access points:•MAC Address—The MAC address of an access point.When you enable the MAC Address filter, the other filters are disabled automatically. When you enableany of the other filters, the MAC Address filter is disabled automatically.Note•AP Name—Enter the name of an access point.•AP Model—Enter the model name of an access point.Cisco Wireless LAN Controller Configuration Guide, Release 7.4        OL-28744-01 687
•Operating Status—Select one or more of the following check boxes to specify the operating status of the accesspoints:◦UP—The access point is up and running.◦DOWN—The access point is not operational.◦REG—The access point is registered to the controller.◦DEREG—The access point is not registered to the controller.◦DOWNLOAD—The controller is downloading its software image to the access point.•Port Number—Enter the controller port number to which the access point is connected.•Admin Status—Choose Enabled or Disabled to specify whether the access points are enabled or disabled on thecontroller.•AP Mode—Select one or more of the following options to specify the operating mode of the access points:◦Local—The default option.The 600 OEAP series access point uses only local mode.When an access point in local mode connects to a Cisco Flex 7500 Series Controller, it does notserve clients. The access point details are available in the controller. To enable an access point toserve clients or perform monitoring-related tasks when connected to the Cisco Flex 7500 SeriesController, the access point mode must be in FlexConnect or monitor mode. Use the followingcommand to automatically convert access points to a FlexConnect mode or monitor mode on joiningthe controller:config ap autoconvert {flexconnect |monitor |disable}All access points that connect to the controller will either be converted to FlexConnect mode ormonitor mode depending on the configuration provided.Note◦FlexConnect—This mode is used for 1040, 1130, 1140, 1240, 1250, 1260, 1600, 2600, 3500, 3600, and 800access points.◦REAP—This mode is the remote edge lightweight access point.◦Monitor—This mode is the monitor-only mode.◦Rogue Detector—This mode monitors the rogue APs on wire. It does not transmit or receive frames overthe air or contain rogue APs.Information about rogues that are detected is not shared between controllers. Therefore, we recommendthat every controller has its own connected rogue detector AP when rogue detector APs are used.Note◦Sniffer—The access point starts sniffing the air on a given channel. It captures and forwards all the packetsfrom the clients on that channel to a remote machine that runs Airopeek or Wireshark (packet analyzers forIEEE 802.11 wireless LANs). It includes information on the time stamp, signal strength, packet size, and soon.The Bridge option is displayed only if the AP is bridgecapable.NoteIf the AP mode is set to “Bridge”and the AP is not REAP capable, an error appears.Note◦Bridge—This mode sets the AP mode to “Bridge”if you are connecting a Root AP.   Cisco Wireless LAN Controller Configuration Guide, Release 7.4688 OL-28744-01  Searching the AP Filter (GUI)
◦SE-Connect—This mode allows you to connect to spectrum expert and it allows the access point to performspectrum intelligence.The AP3500 and the AP3600 support the spectrum intelligence and AP1260 does not support thespectrum intelligence.NoteWhen an access point is configured in SE-Connect mode, the access point reboots and rejoins thecontroller. Access points that are configured in this mode do not serve the client.Note•Certificate Type—Select one or more of the following check boxes to specify the types of certificates installedon the access points:◦MIC—Manufactured-installed certificate◦SSC—Self-signed certificate◦LSC—Local significant certificateSee the Authorizing Access Points section for more information about these certificatetypes.Note•Primary S/W Version—Select this check box to enter the primary software version number•Backup S/W Version—Select this check box to enter the secondary software version number.Step 4 Click Apply.Only the access points that match your search criteria appear on the All APs page, and the Current Filter parameter atthe top of the page specifies the filter used to generate the list (for example, MAC Address:00:1d:e5:54:0e:e6, APName:pmsk-ap, Operational Status: UP, Status: Enabled, and so on).If you want to remove the filters and display the entire access point list, click ClearFilter.NoteCisco Wireless LAN Controller Configuration Guide, Release 7.4       OL-28744-01 689Searching the AP Filter (GUI)
Monitoring the Interface DetailsStep 1 Choose Monitor >Summary >All APs. The All APs > Details page appears.Step 2 Click the Interfaces tab.Figure 48: Interfaces TabStep 3 Click on the available Interface name. The Interface Details page appears.Step 4 The Interface Details page displays the following parameter details.Table 21: Interfaces Parameters DetailsDescriptionButtonName of the access point.AP NameSpeed of the interference in Mbps.Link SpeedTotal number of bytes in the error-free packets received on the interface.RX BytesTotal number of unicast packets received on the interface.RX Unicast PacketsTotal number of nonunicast or multicast packets received on the interface.RX Non-Unicast PacketsTotal number of CRC error in packets while receiving on the interface.Input CRCSum of all errors in the packets while receiving on the interface.Input Errors   Cisco Wireless LAN Controller Configuration Guide, Release 7.4690 OL-28744-01  Monitoring the Interface Details
DescriptionButtonNumber of times the receiver hardware was incapable of handling received data to a hardwarebuffer because the input rate exceeded the receiver’s capability to handle that data.Input OverrunTotal number of resource errors in packets received on the interface.Input ResourceNumber of packets that are discarded because they are similar to the medium’s minimumpacket size.RuntsTotal number of times the interface advised a sending NIC that it was overwhelmed bypackets being sent and to slow the pace of delivery.ThrottleTotal number of packet retransmitted due to an Ethernet collision.Output CollisionResource errors in packets transmitted on the interface.Output ResourceErrors that prevented the final transmission of packets out of the interface.Output ErrorsOperational state of the physical ethernet interface on the AP.Operational StatusInterface’s duplex mode.DuplexNumber of bytes in the error-free packets transmitted on the interface.TX BytesTotal number of unicast packets transmitted on the interface.TX Unicast PacketsTotal number of nonunicast or multicast packets transmitted on the interface.TX Non-Unicast PacketsTotal number of packets aborted while receiving on the interface.Input AbortsTotal number of packets received incorrectly that has a CRC error and a noninteger numberof octets on the interface.Input FramesTotal number of packets dropped while receiving on the interface because the queue wasfull.Input DropsTotal number of packets discarded on the interface due to an unknown protocol.Unknown ProtocolNumber of packets that are discarded because they exceeded the medium’s maximum packetsize.GiantsNumber of times that an interface has been completely reset.Interface ResetsTotal number of packets discarded because there was no buffer space.Output No BufferNumber of times the transmitter has been running faster than the router can handle.Output UnderrunCisco Wireless LAN Controller Configuration Guide, Release 7.4       OL-28744-01 691Monitoring the Interface Details
DescriptionButtonTotal number of packets dropped while transmitting from the interface because the queuewas full.Output Total DropsSearching for Access Point RadiosInformation About Searching for Access Point RadiosYou can search for specific access point radios in the list of radios on the 802.11a/n Radios page or the802.11b/g/n Radios page. You can access these pages from the Monitor tab on the menu bar when viewingaccess point radios or from the Wireless tab on the menu bar when configuring access point radios. To searchfor specific access point radios, you create a filter to display only radios that meet certain criteria (such asradio MAC address, access point name, or CleanAir status). This feature is especially useful if your list ofaccess point radios spans multiple pages, which prevents you from viewing them all at once.Searching for Access Point Radios (GUI)Step 1 Perform either of the following:•Choose Monitor >Access Points Summary >802.11a/n (or 802.11b/g/n) >Radios >Details to open the 802.11a/n(or 802.11b/g/n) Radios page.•Choose Wireless >Access Points >Radios >802.11a/n (or 802.11b/g/n) to open the 802.11a/n (or 802.11b/g/n)Radios page.These pages show all of the 802.11a/n or 802.11b/g/n access point radios that are joined to the controller and theircurrent settings.The total number of access point radios appears in the upper right-hand corner of the page. If the list of radios spansmultiple pages, you can access these pages by clicking the page number links. Each page shows up to 25 accesspoint radios.In a Cisco Unified Wireless Network environment, the 802.11a/n and 802.11b/g/n radios should not bedifferentiated based on their Base Radio MAC addresses, as they may have the same addresses. Instead,the radios should be differentiated based on their physical addresses.NoteStep 2 Click Change Filter to open the Search AP dialog box.Step 3 Select one of the following check boxes to specify the criteria used when displaying access point radios:•MAC Address—Base radio MAC address of an access point radio.•AP Name—Access point name.   Cisco Wireless LAN Controller Configuration Guide, Release 7.4692 OL-28744-01  Searching for Access Point Radios
When you enable the MAC address filter, the other filters are disabled automatically. When you enableany of the other filters, the MAC address filter is disabled automatically.Note•CleanAir Status—Select one or more of the following check boxes to specify the operating status of the accesspoints:◦UP—The spectrum sensor for the access point radio is currently operational.◦DOWN—The spectrum sensor for the access point radio is currently not operational because an error hasoccurred. The most likely reason for the error is that the access point radio is disabled.◦ERROR—The spectrum sensor for the access point radio has crashed, making CleanAir monitoringnonoperational for this radio. We recommend rebooting the access point or disabling CleanAir functionalityon the radio.◦N/A—The access point radio is not capable of supporting CleanAir functionality. Currently, only CiscoAironet 3500 series access point radios can be configured for Cisco CleanAir.Step 4 Click Find to commit your changes. Only the access point radios that match your search criteria appear on the 802.11a/nRadios page or the 802.11b/g/n Radios page, and the Current Filter parameter at the top of the page specifies the filterused to generate the list (for example, MAC Address:00:1e:f7:75:0a:a0 or AP Name:pmsk-ap).If you want to remove the filter and display the entire access point radio list, click ClearFilter.NoteCisco Wireless LAN Controller Configuration Guide, Release 7.4       OL-28744-01 693Searching for Access Point Radios
   Cisco Wireless LAN Controller Configuration Guide, Release 7.4694 OL-28744-01  Searching for Access Point Radios
CHAPTER 103Searching for Access Point Radios•Information About Searching for Access Point Radios, page 695•Searching for Access Point Radios (GUI), page 695Information About Searching for Access Point RadiosYou can search for specific access point radios in the list of radios on the 802.11a/n Radios page or the802.11b/g/n Radios page. You can access these pages from the Monitor tab on the menu bar when viewingaccess point radios or from the Wireless tab on the menu bar when configuring access point radios. To searchfor specific access point radios, you create a filter to display only radios that meet certain criteria (such asradio MAC address, access point name, or CleanAir status). This feature is especially useful if your list ofaccess point radios spans multiple pages, which prevents you from viewing them all at once.Searching for Access Point Radios (GUI)Step 1 Perform either of the following:•Choose Monitor >Access Points Summary >802.11a/n (or 802.11b/g/n) >Radios >Details to open the 802.11a/n(or 802.11b/g/n) Radios page.•Choose Wireless >Access Points >Radios >802.11a/n (or 802.11b/g/n) to open the 802.11a/n (or 802.11b/g/n)Radios page.These pages show all of the 802.11a/n or 802.11b/g/n access point radios that are joined to the controller and theircurrent settings.The total number of access point radios appears in the upper right-hand corner of the page. If the list of radios spansmultiple pages, you can access these pages by clicking the page number links. Each page shows up to 25 accesspoint radios.In a Cisco Unified Wireless Network environment, the 802.11a/n and 802.11b/g/n radios should not bedifferentiated based on their Base Radio MAC addresses, as they may have the same addresses. Instead,the radios should be differentiated based on their physical addresses.NoteCisco Wireless LAN Controller Configuration Guide, Release 7.4        OL-28744-01 695
Step 2 Click Change Filter to open the Search AP dialog box.Step 3 Select one of the following check boxes to specify the criteria used when displaying access point radios:•MAC Address—Base radio MAC address of an access point radio.•AP Name—Access point name.When you enable the MAC address filter, the other filters are disabled automatically. When you enableany of the other filters, the MAC address filter is disabled automatically.Note•CleanAir Status—Select one or more of the following check boxes to specify the operating status of the accesspoints:◦UP—The spectrum sensor for the access point radio is currently operational.◦DOWN—The spectrum sensor for the access point radio is currently not operational because an error hasoccurred. The most likely reason for the error is that the access point radio is disabled.◦ERROR—The spectrum sensor for the access point radio has crashed, making CleanAir monitoringnonoperational for this radio. We recommend rebooting the access point or disabling CleanAir functionalityon the radio.◦N/A—The access point radio is not capable of supporting CleanAir functionality. Currently, only CiscoAironet 3500 series access point radios can be configured for Cisco CleanAir.Step 4 Click Find to commit your changes. Only the access point radios that match your search criteria appear on the 802.11a/nRadios page or the 802.11b/g/n Radios page, and the Current Filter parameter at the top of the page specifies the filterused to generate the list (for example, MAC Address:00:1e:f7:75:0a:a0 or AP Name:pmsk-ap).If you want to remove the filter and display the entire access point radio list, click ClearFilter.Note   Cisco Wireless LAN Controller Configuration Guide, Release 7.4696 OL-28744-01  Searching for Access Point Radios (GUI)
CHAPTER 104Configuring Global Credentials for Access Points•Information About Configuring Global Credentials for Access Points, page 697•Restrictions for Global Credentials for Access Points, page 698•Configuring Global Credentials for Access Points (GUI), page 698•Configuring Global Credentials for Access Points (CLI), page 699Information About Configuring Global Credentials for Access PointsCisco IOS access points are shipped from the factory with Cisco as the default enable password. This passwordallows users to log onto the nonprivileged mode and enter show and debug commands, which poses a securitythreat. The default enable password must be changed to prevent unauthorized access and to enable users toenter configuration commands from the access point’s console port.The following are some guidelines to configure global credentials for access points:•You can set a global username, password, and enable password that all access points that are currentlyjoined to the controller and any that join in the future inherit as they join the controller. If desired, youcan override the global credentials and assign a unique username, password, and enable password for aspecific access point.•After an access point joins the controller, the access point enables console port security, and you areprompted for your username and password whenever you log into the access point’s console port. Whenyou log on, you are in nonprivileged mode, and you must enter the enable password in order to use theprivileged mode.•The global credentials that you configure on the controller are retained across controller and access pointreboots. They are overwritten only if the access point joins a new controller that is configured with aglobal username and password. If the new controller is not configured with global credentials, the accesspoint retains the global username and password configured for the first controller.•You must keep track of the credentials used by the access points. Otherwise, you might not be able tolog onto the console port of the access point. If you need to return the access points to the defaultCisco/Cisco username and password, you must clear the controller’s configuration and the access point’sconfiguration to return them to factory-default settings. To clear the controller’s configuration, chooseCommands >Reset to Factory Default >Reset on the controller GUI, or enter the clear configcommand on the controller CLI. To clear the access point’s configuration, choose Wireless >AccessCisco Wireless LAN Controller Configuration Guide, Release 7.4        OL-28744-01 697
Points >All APs, click the AP name and click Clear All Config on the controller GUI, or enter theclear ap config Cisco_AP command on the controller CLI. To clear the access point's configurationexcept its static IP address, choose Wireless >Access Points >All APs, click the AP name and clickClear Config Except Static IP, or enter the clear ap config ap-name keep-ip-config command on thecontroller CLI. After the access point rejoins a controller, it adopts the default Cisco/Cisco usernameand password.Suppose you configure an indoor Cisco AP to go into the mesh mode. If you want toreset the Cisco AP to the local mode, use the test mesh mode local command.Note•To reset the AP hardware, choose Wireless >Access Points >All APs, click the AP name and clickReset AP Now.Restrictions for Global Credentials for Access Points•The controller software features are supported on all access points that have been converted to lightweightmode except the 1100 series. VxWorks access points are not supported.Configuring Global Credentials for Access Points (GUI)Step 1 Choose Wireless >Access Points >Global Configuration to open the Global Configuration page.Step 2 In the Username text box, enter the username that is to be inherited by all access points that join the controller.Step 3 In the Password text box, enter the password that is to be inherited by all access points that join the controller.You can set a global username, password, and enable password that all access points inherit as they join the controllerincluding access points that are currently joined to the controller and any that join in the future. You can override theglobal credentials and assign a unique username, password, and enable password for a specific access point. The followingare requirements enforced on the password:•The password should contain characters from at least three of the following classes: lowercase letters, uppercaseletters, digits, and special characters.•No character in the password can be repeated more than three times consecutively.•The password should not contain the management username or the reverse of the username.•The password should not contain words like Cisco, oscic, admin, nimda or any variant obtained by changing thecapitalization of letters by substituting 1, |, or ! or substituting 0 for o or substituting $ for s.   Cisco Wireless LAN Controller Configuration Guide, Release 7.4698 OL-28744-01  Restrictions for Global Credentials for Access Points
Step 4 In the Enable Password text box, enter the enable password that is to be inherited by all access points that join thecontroller.Step 5 Click Apply to send the global username, password, and enable password to all access points that are currently joinedto the controller or that join the controller in the future.Step 6 Click Save Configuration to save your changes.Step 7 (Optional) Override the global credentials for a specific access point and assign a unique username, password, and enablepassword to this access point as follows:a) Choose Access Points >All APs to open the All APs page.b) Click the name of the access point for which you want to override the global credentials.c) Choose the Credentials tab. The All APs > Details for (Credentials) page appears.d) Select the Over-ride Global Credentials check box to prevent this access point from inheriting the global username,password, and enable password from the controller. The default value is unselected.e) In the Username, Password, and Enable Password text boxes, enter the unique username, password, and enablepassword that you want to assign to this access point.The information that you enter is retained across controller and access point reboots and if the access pointjoins a new controller.Notef) Click Apply to commit your changes.g) Click Save Configuration to save your changes.If you want to force this access point to use the controller’s global credentials, unselect the Over-ride GlobalCredentials check box.NoteConfiguring Global Credentials for Access Points (CLI)Step 1 Configure the global username, password, and enable password for all access points currently joined to the controller aswell as any access points that join the controller in the future by entering this command:config ap mgmtuser add username user password password enablesecret enable_password allStep 2 (Optional) Override the global credentials for a specific access point and assign a unique username, password, and enablepassword to this access point by entering this command:config ap mgmtuser add username user password password enablesecret enable_password Cisco_APThe credentials that you enter in this command are retained across controller and access point reboots and if the accesspoint joins a new controller.If you want to force this access point to use the controller’s global credentials, enter the config ap mgmtuserdelete Cisco_AP command. The following message appears after you execute this command: “AP reverted toglobal username configuration.”NoteStep 3 Enter the save config command to save your changes.Step 4 Verify that global credentials are configured for all access points that join the controller by entering this command:show ap summaryIf global credentials are not configured, the Global AP User Name text box shows “Not Configured.”NoteTo view summary of specific access point you can specify the access point name. You can also use wildcard searcheswhen filtering for access points.Cisco Wireless LAN Controller Configuration Guide, Release 7.4       OL-28744-01 699Configuring Global Credentials for Access Points (CLI)
Step 5 See the global credentials configuration for a specific access point by entering this command:show ap config general Cisco_APThe name of the access point is casesensitive.NoteIf this access point is configured for global credentials, the AP User Mode text boxes shows “Automatic.”If theglobal credentials have been overwritten for this access point, the AP User Mode text box shows “Customized.”Note   Cisco Wireless LAN Controller Configuration Guide, Release 7.4700 OL-28744-01  Configuring Global Credentials for Access Points (CLI)
CHAPTER 105Configuring Authentication for Access Points•Information About Configuring Authentication for Access Points, page 701•Prerequisites for Configuring Authentication for Access Points, page 701•Restrictions for Authenticating Access Points, page 702•Configuring Authentication for Access Points (GUI), page 702•Configuring Authentication for Access Points (CLI), page 703•Configuring the Switch for Authentication, page 704Information About Configuring Authentication for Access PointsYou can configure 802.1X authentication between a lightweight access point and a Cisco switch. The accesspoint acts as an 802.1X supplicant and is authenticated by the switch using EAP-FAST with anonymous PACprovisioning.You can configure global authentication settings that all access points that are currently associated with thecontroller and any that associate in the future. You can also override the global authentication settings andassign unique authentication settings for a specific access point.Prerequisites for Configuring Authentication for Access PointsStep 1 If the access point is new, do the following:a) Boot the access point with the installed recovery image.b) If you choose not to follow this suggested flow and instead enable 802.1X authentication on the switch port connectedto the access point prior to the access point joining the controller, enter this command:lwapp ap dot1x username username password passwordIf you choose to follow this suggested flow and enable 802.1X authentication on the switch port after theaccess point has joined the controller and received the configured 802.1X credentials, you do not need toenter this command.NoteCisco Wireless LAN Controller Configuration Guide, Release 7.4        OL-28744-01 701
This command is available only for access points that are running the 5.1, 5.2, 6.0, or 7.0 recoveryimage.Connect the access point to the switch port.NoteStep 2 Install the 5.1, 5.2, 6.0, or 7.0 image on the controller and reboot the controller.Step 3 Allow all access points to join the controller.Step 4 Configure authentication on the controller. See the Configuring Authentication for Access Points (GUI) section or theConfiguring Authentication for Access Points (CLI) section for information about configuring authentication on thecontroller.Step 5 Configure the switch to allow authentication. See the Configuring the Switch for Authentication section for informationabout configuring the switch for authentication.Restrictions for Authenticating Access Points•The OEAP 600 Series access points do not support LEAP.Configuring Authentication for Access Points (GUI)Step 1 Choose Wireless >Access Points >Global Configuration to open the Global Configuration page.Step 2 Under 802.1x Supplicant Credentials, select the 802.1x Authentication check box.Step 3 In the Username text box, enter the username that is to be inherited by all access points that join the controller.Step 4 In the Password and Confirm Password text boxes, enter the password that is to be inherited by all access points thatjoin the controller.You must enter a strong password in these text boxes. Strong passwords have the following characteristics:Note•They are at least eight characters long•They contain a combination of uppercase and lowercase letters, numbers, and symbols•They are not a word in any languageStep 5 Click Apply to send the global authentication username and password to all access points that are currently joined tothe controller and to any that join the controller in the future.Step 6 Click Save Configuration to save your changes.Step 7 If desired, you can choose to override the global authentication settings and assign a unique username and password toa specific access point as follows:a) Choose Access Points >All APs to open the All APs page.b) Click the name of the access point for which you want to override the authentication settings.c) Click the Credentials tab to open the All APs > Details for (Credentials) page.d) Under 802.1x Supplicant Credentials, select the Over-ride Global Credentials check box to prevent this accesspoint from inheriting the global authentication username and password from the controller. The default value isunselected.   Cisco Wireless LAN Controller Configuration Guide, Release 7.4702 OL-28744-01  Restrictions for Authenticating Access Points
e) In the Username, Password, and Confirm Password text boxes, enter the unique username and password that youwant to assign to this access point.The information that you enter is retained across controller and access point reboots and whenever the accesspoint joins a new controller.Notef) Click Apply to commit your changes.g) Click Save Configuration to save your changes.If you want to force this access point to use the controller’s global authentication settings, unselect theOver-ride Global Credentials check box.NoteConfiguring Authentication for Access Points (CLI)Step 1 Configure the global authentication username and password for all access points currently joined to the controller aswell as any access points that join the controller in the future by entering this command:config ap 802.1Xuser add username ap-username password ap-password allYou must enter a strong password for the ap-password parameter. Strong passwords have the followingcharacteristics:Note•They are at least eight characters long.•They contain a combination of uppercase and lowercase letters, numbers, and symbols.•They are not a word in any language.Step 2 (Optional) Override the global authentication settings and assign a unique username and password to a specific accesspoint. To do so, enter this command:config ap 802.1Xuser add username ap-username password ap-password Cisco_APYou must enter a strong password for the ap-password parameter. See the note in Step 1 for the characteristicsof strong passwords.NoteThe authentication settings that you enter in this command are retained across controller and access point reboots andwhenever the access point joins a new controller.If you want to force this access point to use the controller’s global authentication settings, enter the config ap802.1Xuser delete Cisco_AP command. The following message appears after you execute this command: “APreverted to global username configuration.”NoteStep 3 Enter the save config command to save your changes.Step 4 (Optional) Disable 802.1X authentication for all access points or for a specific access point by entering this command:config ap 802.1Xuser disable {all |Cisco_AP}You can disable 802.1X authentication for a specific access point only if global 802.1X authentication is notenabled. If global 802.1X authentication is enabled, you can disable 802.1X for all access points only.NoteStep 5 See the authentication settings for all access points that join the controller by entering this command:show ap summaryCisco Wireless LAN Controller Configuration Guide, Release 7.4       OL-28744-01 703Configuring Authentication for Access Points (CLI)
Information similar to the following appears:Number of APs.................................... 1Global AP User Name.............................. globalapGlobal AP Dot1x User Name........................ globalDot1xStep 6 See the authentication settings for a specific access point by entering this command:show ap config general Cisco_APThe name of the access point is casesensitive.NoteIf this access point is configured for global authentication, the AP Dot1x User Mode text boxes shows “Automatic.”If the global authentication settings have been overwritten for this access point, the AP Dot1x User Mode textbox shows “Customized.”NoteConfiguring the Switch for AuthenticationTo enable 802.1X authentication on a switch port, on the switch CLI, enter these commands:•Switch# configure terminal•Switch(config)# dot1x system-auth-control•Switch(config)# aaa new-model•Switch(config)# aaa authentication dot1x default group radius•Switch(config)# radius-server host ip_addr auth-port port acct-port port key key•Switch(config)# interface fastethernet2/1•Switch(config-if)# switchport mode access•Switch(config-if)# dot1x pae authenticator•Switch(config-if)# dot1x port-control auto•Switch(config-if)# end   Cisco Wireless LAN Controller Configuration Guide, Release 7.4704 OL-28744-01  Configuring the Switch for Authentication
CHAPTER 106Configuring Embedded Access Points•Information About Embedded Access Points, page 705Information About Embedded Access PointsController software release 7.0.116.0 or later releases support the embedded access points: AP801 and AP802,which are the integrated access points on the Cisco 880 Series Integrated Services Routers (ISRs). This accesspoints use a Cisco IOS software image that is separate from the router Cisco IOS software image. The accesspoints can operate as autonomous access points configured and managed locally, or they can operate ascentrally managed access points that utilize the CAPWAP or LWAPP protocol. The AP801 and AP802 accesspoints are preloaded with both an autonomous Cisco IOS release and a recovery image for the unified mode.The following are some guidelines for embedded access points:•Before you use an AP801 or AP802 Series Lightweight Access Point with controller software release7.0.116.0 or later releases, you must upgrade the software in the Next Generation Cisco 880 SeriesIntegrated Services Routers (ISRs) to Cisco IOS 151-4.M or later.In Release 7.4, all AP modes except bridging (required for mesh) are supported for bothAP801 and AP802. In Release 7.5 and later, all AP modes are supported on AP802;however, bridging is not supported on AP801.Note•When you want to use the AP801 or AP802 with a controller, you must enable the recovery image forthe unified mode on the access point by entering the service-module wlan-ap 0 bootimage unifiedcommand on the router in privileged EXEC mode.•If the service-module wlan-ap 0 bootimage unified command does not work, make sure that thesoftware license is still eligible.•After enabling the recovery image, enter the service-module wlan-ap 0 reload command on the routerto shut down and reboot the access point. After the access point reboots, it discovers the controller,downloads the full CAPWAP or LWAPP software release from the controller, and acts as a lightweightaccess point.Cisco Wireless LAN Controller Configuration Guide, Release 7.4        OL-28744-01 705
To use the CLI commands mentioned above, the router must be running Cisco IOSRelease 12.4(20)T or later releases.Note•To support CAPWAP or LWAPP, the router must be activated with at least the Cisco Advanced IPServices IOS license-grade image. A license is required to upgrade to this Cisco IOS image on the router.For licensing information, see http://www.cisco.com/en/US/docs/routers/access/sw_activation/SA_on_ISR.html•After the AP801 or AP802 boots up with the recovery image for the unified mode, it requires an IPaddress to communicate with the controller and to download its unified image and configuration fromthe controller. The router can provide DHCP server functionality, the DHCP pool to reach the controller,and setup option 43 for the controller IP address in the DHCP pool configuration. Use the followingconfiguration to perform this task:ip dhcp pool pool_namenetwork ip_address subnet_maskdns-server ip_addressdefault-router ip_addressoption 43 hex controller_ip_address_in_hexExample:ip dhcp pool embedded-ap-poolnetwork 60.0.0.0 255.255.255.0dns-server 171.70.168.183default-router 60.0.0.1option 43 hex f104.0a0a.0a0f /* single WLC IP address(10.10.10.15) in hex format*/•The AP801 and AP802 802.11n radio supports lower power levels than the 802.11n radio in the CiscoAironet 1250 series access points. The AP801 and AP802 access points store the radio power levels andpasses them to the controller when the access point joins the controller. The controller uses the suppliedvalues to limit the user’s configuration.•The AP801 and AP802 access points can be used in FlexConnect mode.For more information about the AP801, see the documentation for the Cisco 800 Series ISRs at this URL:http://www.cisco.com/en/US/products/hw/routers/ps380/tsd_products_support_series_home.htmlFor more information about the AP802, see the documentation for the Next generation Cisco 880 Series ISRsat this URL: http://www.cisco.com/en/US/docs/routers/access/800/860-880-890/software/configuration/guide/SCG_880_series.pdf   Cisco Wireless LAN Controller Configuration Guide, Release 7.4706 OL-28744-01  Information About Embedded Access Points
CHAPTER 107Converting Autonomous Access Points toLightweight Mode•Information About Converting Autonomous Access Points to Lightweight Mode, page 707•Restrictions for Converting Autonomous Access Points to Lightweight Mode, page 708•Reverting from Lightweight Mode to Autonomous Mode, page 708•Authorizing Access Points, page 709•Configuring VLAN Tagging for CAPWAP Frames from Access Points, page 715•Using DHCP Option 43 and DHCP Option 60, page 716•Troubleshooting the Access Point Join Process, page 717•Sending Debug Commands to Access Points Converted to Lightweight Mode, page 721•Understanding How Converted Access Points Send Crash Information to the Controller, page 721•Understanding How Converted Access Points Send Radio Core Dumps to the Controller, page 721•Uploading Memory Core Dumps from Converted Access Points, page 723•Viewing the AP Crash Log Information, page 724•Displaying MAC Addresses for Converted Access Points, page 725•Disabling the Reset Button on Access Points Converted to Lightweight Mode, page 725•Configuring a Static IP Address on a Lightweight Access Point, page 726•Supporting Oversized Access Point Images, page 727Information About Converting Autonomous Access Points to Lightweight ModeYou can use an upgrade conversion tool to convert autonomous Cisco Aironet 1100, 1130AG, 1200, 1240AG,1260, and 1300 Series Access Points to lightweight mode. When you upgrade one of these access points tolightweight mode, the access point communicates with a controller and receives a configuration and softwareimage from the controller.Cisco Wireless LAN Controller Configuration Guide, Release 7.4        OL-28744-01 707
See the Upgrading Autonomous Cisco Aironet Access Points to Lightweight Mode document for instructionsto upgrade an autonomous access point to lightweight mode:http://www.cisco.com/en/US/docs/wireless/access_point/conversion/lwapp/upgrade/guide/lwapnote.htmlThe following are some guidelines for converting autonomous APs to lightweight mode APs:•All Cisco lightweight access points support 16 BSSIDs per radio and a total of 16 wireless LANs peraccess point. When a converted access point associates with a controller, only wireless LANs with IDs1 through 16 are pushed to the access point.•Access points converted to lightweight mode must get an IP address and discover the controller usingDHCP, DNS, or IP subnet broadcast.•The 1130AG and 1240AG access points support FlexConnect mode.Restrictions for Converting Autonomous Access Points to Lightweight Mode•Access points converted to lightweight mode do not support Wireless Domain Services (WDS). Convertedaccess points communicate only with Cisco wireless LAN controllers and cannot communicate withWDS devices. However, the controller provides functionality that is equivalent to WDS when the accesspoint associates to it.•After you convert an access point to lightweight mode, the console port provides read-only access tothe unit.Reverting from Lightweight Mode to Autonomous ModeAfter you use the upgrade tool to convert an autonomous access point to lightweight mode, you can convertthe access point from a lightweight unit back to an autonomous unit by loading a Cisco IOS release thatsupports autonomous mode (Cisco IOS Release 12.3(7)JA or earlier releases). If the access point is associatedto a controller, you can use the controller to load the Cisco IOS release. If the access point is not associatedto a controller, you can load the Cisco IOS release using TFTP. In either method, the access point must beable to access a TFTP server that contains the Cisco IOS release to be loaded.Reverting to a Previous Release (CLI)Step 1 Log on to the CLI on the controller to which the access point is associated.Step 2 Revert from lightweight mode, by entering this command:config ap tftp-downgrade tftp-server-ip-address filename access-point-nameStep 3 Wait until the access point reboots and reconfigure the access point using the CLI or GUI.   Cisco Wireless LAN Controller Configuration Guide, Release 7.4708 OL-28744-01  Restrictions for Converting Autonomous Access Points to Lightweight Mode
Reverting to a Previous Release Using the MODE Button and a TFTP ServerStep 1 Configure the PC on which your TFTP server software runs with a static IP address in the range of 10.0.0.2 to 10.0.0.30.Step 2 Make sure that the PC contains the access point image file (such as c1200-k9w7-tar.123-7.JA.tar for a 1200 series accesspoint) in the TFTP server folder and that the TFTP server is activated.Step 3 Rename the access point image file in the TFTP server folder to c1200-k9w7-tar.default for a 1200 series access point.Step 4 Connect the PC to the access point using a Category 5 (CAT5) Ethernet cable.Step 5 Disconnect power from the access point.Step 6 Press and hold the MODE button while you reconnect power to the access point.The MODE button on the access point must be enabled. Follow the steps in the Disabling the Reset Button onAccess Points Converted to Lightweight Mode to select the status of the access point MODE button.NoteStep 7 Hold the MODE button until the status LED turns red (approximately 20 to 30 seconds), and release the MODE button.Step 8 Wait until the access point reboots as indicated by all LEDs turning green followed by the Status LED blinking green.Step 9 After the access point reboots, reconfigure the access point using the GUI or the CLI.Authorizing Access PointsIn controller software releases prior to 5.2, the controller may either use self-signed certificates (SSCs) toauthenticate access points or send the authorization information to a RADIUS server (if access points havemanufactured-installed certificates [MICs]). In controller software release 5.2 or later releases, you canconfigure the controller to use a local significant certificate (LSC).Authorizing Access Points Using SSCsThe Control and Provisioning of Wireless Access Points protocol (CAPWAP) secures the controlcommunication between the access point and controller by a secure key distribution requiring X.509 certificateson both the access point and controller. CAPWAP relies on provisioning of the X.509 certificates. CiscoAironet access points shipped before July 18, 2005 do not have a MIC, so these access points create an SSCwhen upgraded to operate in lightweight mode. Controllers are programmed to accept local SSCs forauthentication of specific access points and do not forward those authentication requests to a RADIUS server.This behavior is acceptable and secure.Authorizing Access Points for Virtual Controllers Using SSCVirtual controllers use SSC certificates instead of Manufacturing Installed Certificates (MIC) used by physicalcontrollers. You can configure the controller to allow an AP to validate the SSC of the virtual controller.When an AP validates the SSC, the AP checks if the hash key of the virtual controller matches the hash keystored in its flash. If a match is found, the AP associates with the controller. If a match is not found, thevalidation fails and the AP disconnects from the controller and restarts the discovery process. By default, hashvalidation is enabled. An AP must have the virtual controller hash key in its flash before associating with thevirtual controller. If you disable hash validation of the SSC, the AP bypasses the hash validation and directlymoves to the Run state. APs can associate with a physical controller, download the hash keys and then associateCisco Wireless LAN Controller Configuration Guide, Release 7.4       OL-28744-01 709Authorizing Access Points
with a virtual controller. If the AP is associated with a physical controller and hash validation is disabled, theAP associates with any virtual controller without hash validation. The hash key of the virtual controller canbe configured for a mobility group member. This hash key gets pushed to the APs, so that the APs can validatethe hash key of the controller.Configuring SSC (GUI)Step 1 Choose Security >Certificate >SSC to open the Self Significant Certificates (SSC) page.The SSC device certification details are displayed.Step 2 Select the Enable SSC Hash Validation check box to enable the validation of the hash key.Step 3 Click Apply to commit your changes.Configuring SSC (CLI)Step 1 To configure hash validation of SSC, enter this command:config certificate ssc hash validation {enable |disable}Step 2 To see the hash key details, enter this command:show certificate sscAuthorizing Access Points Using MICsYou can configure controllers to use RADIUS servers to authorize access points using MICs. The controlleruses an access point’s MAC address as both the username and password when sending the information to aRADIUS server. For example, if the MAC address of the access point is 000b85229a70, both the usernameand password used by the controller to authorize the access point are 000b85229a70.The lack of a strong password by the use of the access point’s MAC address should not be an issue becausethe controller uses MIC to authenticate the access point prior to authorizing the access point through theRADIUS server. Using MIC provides strong authentication.NoteIf you use the MAC address as the username and password for access point authentication on a RADIUSAAA server, do not use the same AAA server for client authentication.Note   Cisco Wireless LAN Controller Configuration Guide, Release 7.4710 OL-28744-01  Authorizing Access Points
Authorizing Access Points Using LSCsYou can use an LSC if you want your own public key infrastructure (PKI) to provide better security, to havecontrol of your certificate authority (CA), and to define policies, restrictions, and usages on the generatedcertificates.The LSC CA certificate is installed on access points and controllers. You need to provision the device certificateon the access point. The access point gets a signed X.509 certificate by sending a certRequest to the controller.The controller acts as a CA proxy and receives the certRequest signed by the CA for the access point.When the CA server is in manual mode and if there is an AP entry in the LSC SCEP table that is pendingenrollment, the controller waits for the CA server to send a pending response. If there is no response fromthe CA server, the controller retries a total of three times to get a response, after which the fallback modecomes into effect where the AP provisioning times out and the AP reboots and comes up with MIC.NoteLSC on controller does not take password challenge. Therefore, for LSC to work, you must disablepassword challenge on the CA server. Also, you cannot use Microsoft Windows Server 2008 as a CAserver because it is not possible to disable password challenge on it.NoteConfiguring Locally Significant Certificates (GUI)Step 1 Choose Security >Certificate >LSC to open the Local Significant Certificates (LSC) - General page.Step 2 Select the Enable LSC on Controller check box to enable the LSC on the system.Step 3 In the CA Server URL text box, enter the URL to the CA server. You can enter either a domain name or an IP address.Step 4 In the Params text boxes, enter the parameters for the device certificate. The key size is a value from 384 to 2048 (inbits), and the default value is 2048.Step 5 Click Apply to commit your changes.Step 6 To add the CA certificate into the controller’s CA certificate database, hover your cursor over the blue drop-down arrowfor the certificate type and choose Add.Step 7 Choose the AP Provisioning tab to open the Local Significant Certificates (LSC) - AP Provisioning page.Step 8 Select the Enable check box and click Update to provision the LSC on the access point.Step 9 When a message appears indicating that the access points will be rebooted, click OK.Step 10 In the Number of Attempts to LSC text box, enter the number of times that the access point attempts to join the controllerusing an LSC before the access point reverts to the default certificate (MIC or SSC). The range is 0 to 255 (inclusive),and the default value is 3.If you set the number of retries to a nonzero value and the access point fails to join the controller using an LSCafter the configured number of retries, the access point reverts to the default certificate. If you set the numberof retries to 0 and the access point fails to join the controller using an LSC, the access point does not attemptto join the controller using the default certificate.NoteIf you are configuring LSC for the first time, we recommend that you configure a nonzerovalue.NoteCisco Wireless LAN Controller Configuration Guide, Release 7.4       OL-28744-01 711Authorizing Access Points
Step 11 Enter the access point MAC address in the AP Ethernet MAC Addresses text box and click Add to add access points tothe provision list.To remove an access point from the provision list, hover your cursor over the blue drop-down arrow for theaccess point and choose Remove.NoteIf you configure an access point provision list, only the access points in the provision list are provisioned whenyou enable AP provisioning. If you do not configure an access point provision list, all access points with a MICor SSC certificate that join the controller are LSC provisioned.NoteStep 12 Click Apply to commit your changes.Step 13 Click Save Configuration to save your changes.Configuring Locally Significant Certificates (CLI)Step 1 Enable LSC on the system by entering this command:config certificate lsc {enable |disable}Step 2 Configure the URL to the CA server by entering this command:config certificate lsc ca-server http://url:port/pathwhere url can be either a domain name or IP address.You can configure only one CA server. To configure a different CA server, delete the configured CA serverusing the config certificate lsc ca-server delete command, and then configure a different CA server.NoteStep 3 Add the LSC CA certificate into the controller’s CA certificate database by entering this command:config certificate lsc ca-cert {add |delete}Step 4 Configure the parameters for the device certificate by entering this command:config certificate lsc subject-params country state city orgn dept e-mailThe common name (CN) is generated automatically on the access point using the current MIC/SSC formatCxxxx-MacAddr, where xxxx is the product number.NoteStep 5 Configure a key size by entering this command:config certificate lsc other-params keysizeThe keysize is a value from 384 to 2048 (in bits), and the default value is 2048.Step 6 Add access points to the provision list by entering this command:config certificate lsc ap-provision auth-list add AP_mac_addrTo remove access points from the provision list, enter the config certificate lsc ap-provision auth-list deleteAP_mac_addr command.NoteIf you configure an access point provision list, only the access points in the provision list are provisioned whenyou enable AP provisioning (in Step 8). If you do not configure an access point provision list, all access pointswith a MIC or SSC certificate that join the controller are LSC provisioned.NoteStep 7 Configure the number of times that the access point attempts to join the controller using an LSC before the access pointreverts to the default certificate (MIC or SSC) by entering this command:config certificate lsc ap-provision revert-cert retrieswhere retries is a value from 0 to 255, and the default value is 3.   Cisco Wireless LAN Controller Configuration Guide, Release 7.4712 OL-28744-01  Authorizing Access Points
If you set the number of retries to a nonzero value and the access point fails to join the controller using an LSCafter the configured number of retries, the access point reverts to the default certificate. If you set the numberof retries to 0 and the access point fails to join the controller using an LSC, the access point does not attemptto join the controller using the default certificate.NoteIf you are configuring LSC for the first time, we recommend that you configure a nonzerovalue.NoteStep 8 Provision the LSC on the access point by entering this command:config certificate lsc ap-provision {enable |disable}Step 9 See the LSC summary by entering this command:show certificate lsc summaryInformation similar to the following appears:LSC Enabled.......................................... YesLSC CA-Server........................................ http://10.0.0.1:8080/caserverLSC AP-Provisioning.................................. YesProvision-List................................... Not ConfiguredLSC Revert Count in AP reboots................... 3LSC Params:Country.......................................... 4State............................................ caCity............................................. ssOrgn............................................. orgDept............................................. depEmail............................................ dep@co.comKeySize.......................................... 390LSC Certs:CA Cert.......................................... Not ConfiguredRA Cert....................................... Not ConfiguredStep 10 See details about the access points that are provisioned using LSC by entering this command:show certificate lsc ap-provisionInformation similar to the following appears:LSC AP-Provisioning........................... YesProvision-List................................ PresentIdx Mac Address--- ------------1 00:18:74:c7:c0:90Cisco Wireless LAN Controller Configuration Guide, Release 7.4       OL-28744-01 713Authorizing Access Points
Authorizing Access Points (GUI)Step 1 Choose Security >AAA >AP Policies to open the AP Policies page.Step 2 If you want the access point to accept self-signed certificates (SSCs), manufactured-installed certificates (MICs), or localsignificant certificates (LSCs), select the appropriate check box.Step 3 If you want the access points to be authorized using a AAA RADIUS server, select the Authorize MIC APs againstauth-list or AAA check box.Step 4 If you want the access points to be authorized using an LSC, select the Authorize LSC APs against auth-list checkbox.Step 5 Click Apply to commit your changes.Step 6 Follow these steps to add an access point to the controller’s authorization list:a) Click Add to access the Add AP to Authorization List area.b) In the MAC Address text box, enter the MAC address of the access point.c) From the Certificate Type drop-down list, choose MIC,SSC, or LSC.d) Click Add. The access point appears in the access point authorization list.To remove an access point from the authorization list, hover your cursor over the blue drop-down arrow forthe access point and choose Remove.NoteTo search for a specific access point in the authorization list, enter the MAC address of the access point inthe Search by MAC text box and click Search.NoteAuthorizing Access Points (CLI)•Configure an access point authorization policy by entering this command:config auth-list ap-policy {authorize-ap {enable |disable} | authorize-lsc-ap {enable |disable}}•Configure an access point to accept manufactured-installed certificates (MICs), self-signed certificates(SSCs), or local significant certificates (LSCs) by entering this command:config auth-list ap-policy {mic | ssc |lsc {enable |disable}}•Configure the user name to be used in access point authorization requests.config auth-list ap-policy {authorize-ap username {ap_name |ap_mac |both}}•Add an access point to the authorization list by entering this command:config auth-list add {mic |ssc |lsc}ap_mac [ap_key]where ap_key is an optional key hash value equal to 20 bytes or 40 digits.To delete an access point from the authorization list, enter this command: config auth-list delete ap_mac.Note•See the access point authorization list by entering this command:show auth-list   Cisco Wireless LAN Controller Configuration Guide, Release 7.4714 OL-28744-01  Authorizing Access Points
Configuring VLAN Tagging for CAPWAP Frames from Access PointsInformation About VLAN Tagging for CAPWAP Frames from Access PointsYou can configure VLAN tagging on the Ethernet interface either directly on the AP console or through thecontroller. The configuration is saved in the flash memory and all CAPWAP frames use the VLAN tag asconfigured, along with all the locally switched traffic, which is not mapped to a VLAN.This feature is not supported on mesh access points that are in bridge mode.Configuring VLAN Tagging for CAPWAP Frames from Access Points (GUI)Step 1 Choose Wireless >Access Points >All APs to open the All APs page.Step 2 Click the AP name from the list of AP names to open the Details page for the AP.Step 3 Click the Advanced tab.Step 4 In the VLAN Tagging area, select the VLAN Tagging check box.Step 5 In the Trunk VLAN ID text box, enter an ID.If the access point is unable to route traffic through the specified trunk VLAN after about 10 minutes, the access pointperforms a recovery procedure by rebooting and sending CAPWAP frames in untagged mode to try and reassociate withthe controller. The controller sends a trap to a trap server such as the Cisco Prime Infrastructure, which indicates thefailure of the trunk VLAN.If the access point is unable to route traffic through the specified trunk VLAN, it untags the packets and reassociateswith the controller. The controller sends a trap to a trap server such as the Cisco Prime Infrastructure, which indicatesthe failure of the trunk VLAN.If the trunk VLAN ID is 0, the access point untags the CAPWAP frames.The VLAN Tag status is displayed showing whether the AP tags or untags the CAPWAP frames.Step 6 Click Apply.Step 7 You are prompted with a warning message saying that the configuration will result in a reboot of the access point. ClickOK to continue.Step 8 Click Save Configuration.What to Do NextAfter the configuration, the switch or other equipment connected to the Ethernet interface of the AP must alsobe configured to support tagged Ethernet frames.Configuring VLAN Tagging for CAPWAP Frames from Access Points (CLI)Step 1 Configure VLAN tagging for CAPWAP frames from access points by entering this command:Cisco Wireless LAN Controller Configuration Guide, Release 7.4       OL-28744-01 715Configuring VLAN Tagging for CAPWAP Frames from Access Points
config ap ethernet tag {disable |id vlan-id} {ap-name |all}Step 2 You can see VLAN tagging information for an AP or all APs by entering this command:show ap ethernet tag {summary |ap-name}Using DHCP Option 43 and DHCP Option 60Cisco Aironet access points use the type-length-value (TLV) format for DHCP option 43. DHCP servers mustbe programmed to return the option based on the access point’s DHCP Vendor Class Identifier (VCI) string(DHCP option 60).This table lists the VCI strings for Cisco access points capable of operating in lightweight mode.Table 22: VCI Strings For Lightweight Access PointsVCI StringAccess PointCisco AP c1040Cisco Aironet 1040 SeriesCisco AP c1130Cisco Aironet 1130 SeriesCisco AP c1140Cisco Aironet 1140 SeriesCisco AP c1240Cisco Aironet 1240 SeriesCisco AP c1250Cisco Aironet 1250 SeriesCisco AP c1260Cisco Aironet 1260 SeriesCisco AP c1520Cisco Aironet 1520 SeriesCisco AP c1550Cisco Aironet 1550 SeriesCisco AP c3600Cisco Aironet 3600 SeriesCisco AP c3500Cisco Aironet 3500 SeriesCisco AP801Cisco AP801 Embedded Access PointCisco AP802Cisco AP802 Embedded Access PointThe format of the TLV block is as follows:•Type: 0xf1 (decimal 241)•Length: Number of controller IP addresses * 4   Cisco Wireless LAN Controller Configuration Guide, Release 7.4716 OL-28744-01  Using DHCP Option 43 and DHCP Option 60
•Value: List of the IP addresses of controller management interfacesSee the product documentation for your DHCP server for instructions on configuring DHCP option 43. TheUpgrading Autonomous Cisco Aironet Access Points to Lightweight Mode document contains example stepsfor configuring option 43 on a DHCP server.If the access point is ordered with the Service Provider Option - AIR-OPT60-DHCP selected, the VCI stringfor that access point will be different than those listed above. The VCI string will have the “ServiceProvider”.For example, a 1260 with this option will return this VCI string: "Cisco AP c1260-ServiceProvider".The controller IP address that you obtain from the DHCP server should be a unicast IP address. Do notconfigure the controller IP address as a multicast address when configuring DHCP Option 43.NoteTroubleshooting the Access Point Join ProcessAccess points can fail to join a controller for many reasons such as a RADIUS authorization is pending,self-signed certificates are not enabled on the controller, the access point and controller’s regulatory domainsdo not match, and so on.Controller software release 5.2 or later releases enable you to configure the access points to send allCAPWAP-related errors to a syslog server. You do not need to enable any debug commands on the controllerbecause all of the CAPWAP error messages can be viewed from the syslog server itself.The state of the access point is not maintained on the controller until it receives a CAPWAP join request fromthe access point, so it can be difficult to determine why the CAPWAP discovery request from a certain accesspoint was rejected. In order to troubleshoot such joining issues without enabling CAPWAP debug commandson the controller, the controller collects information for all access points that send a discovery message to thiscontroller and maintains information for any access points that have successfully joined this controller.The controller collects all join-related information for each access point that sends a CAPWAP discoveryrequest to the controller. Collection begins with the first discovery message received from the access pointand ends with the last configuration payload sent from the controller to the access point.You can view join-related information for the following numbers of access points:When the controller is maintaining join-related information for the maximum number of access points, it doesnot collect information for any more access points.If any of these conditions are met and the access point has not yet joined a controller, you can also configurea DHCP server to return a syslog server IP address to the access point using option 7 on the server. The accesspoint then starts sending all syslog messages to this IP address.You can also configure the syslog server IP address through the access point CLI, provided the access pointis currently not connected to the controller by entering the lwapp ap log-server syslog_server_IP_addresscommand.When the access point joins a controller for the first time, the controller pushes the global syslog server IPaddress (the default is 255.255.255.255) to the access point. After that, the access point sends all syslogmessages to this IP address, until it is overridden by one of the following scenarios:•The access point is still connected to the same controller, and the global syslog server IP addressconfiguration on the controller has been changed using the config ap syslog host globalCisco Wireless LAN Controller Configuration Guide, Release 7.4       OL-28744-01 717Troubleshooting the Access Point Join Process
syslog_server_IP_address command. In this case, the controller pushes the new global syslog server IPaddress to the access point.•The access point is still connected to the same controller, and a specific syslog server IP address hasbeen configured for the access point on the controller using the config ap syslog host specific Cisco_APsyslog_server_IP_address command. In this case, the controller pushes the new specific syslog serverIP address to the access point.•The access point gets disconnected from the controller, and the syslog server IP address has beenconfigured from the access point CLI using the lwapp ap log-server syslog_server_IP_address command.This command works only if the access point is not connected to any controller.•The access point gets disconnected from the controller and joins another controller. In this case, the newcontroller pushes its global syslog server IP address to the access point.Whenever a new syslog server IP address overrides the existing syslog server IP address, the old address iserased from persistent storage, and the new address is stored in its place. The access point also starts sendingall syslog messages to the new IP address, provided the access point can reach the syslog server IP address.You can configure the syslog server for access points using the controller GUI and view the access point joininformation using the controller GUI or CLI.Configuring the Syslog Server for Access Points (CLI)Step 1 Perform one of the following:•To configure a global syslog server for all access points that join this controller, enter this command:config ap syslog host global syslog_server_IP_addressBy default, the global syslog server IP address for all access points is 255.255.255.255. Make sure thatthe access points can reach the subnet on which the syslog server resides before configuring the syslogserver on the controller. If the access points cannot reach this subnet, the access points are unable to sendout syslog messages.Note•To configure a syslog server for a specific access point, enter this command:config ap syslog host specific Cisco_AP syslog_server_IP_addressBy default, the syslog server IP address for each access point is 0.0.0.0, which indicates that the accesspoint is not yet set. When the default value is used, the global access point syslog server IP address ispushed to the access point.NoteStep 2 Enter the save config command to save your changes.Step 3 See the global syslog server settings for all access points that join the controller by entering this command:show ap config globalInformation similar to the following appears:AP global system logging host.................... 255.255.255.255Step 4 See the syslog server settings for a specific access point by entering this command:show ap config general Cisco_AP   Cisco Wireless LAN Controller Configuration Guide, Release 7.4718 OL-28744-01  Troubleshooting the Access Point Join Process
Viewing Access Point Join InformationJoin statistics for an access point that sends a CAPWAP discovery request to the controller at least once aremaintained on the controller even if the access point is rebooted or disconnected. These statistics are removedonly when the controller is rebooted or when you choose to clear the statistics.Viewing Access Point Join Information (GUI)Step 1 Choose Monitor >Statistics >AP Join to open the AP Join Stats page.This page lists all of the access points that are joined to the controller or that have tried to join. It shows the radio MACaddress, access point name, current join status, Ethernet MAC address, IP address, and last join time for each accesspoint.The total number of access points appears in the upper right-hand corner of the page. If the list of access points spansmultiple pages, you can view these pages by clicking the page number links. Each page shows the join statistics for upto 25 access points.If you want to remove an access point from the list, hover your cursor over the blue drop-down arrow for thataccess point and click Remove.NoteIf you want to clear the statistics for all access points and start over, click Clear Stats on AllAPs.NoteStep 2 If you want to search for specific access points in the list of access points on the AP Join Stats page, follow these stepsto create a filter to display only access points that meet certain criteria (such as MAC address or access point name).This feature is especially useful if your list of access points spans multiple pages, preventing you from viewingthem all at once.Notea) Click Change Filter to open the Search AP dialog box.b) Select one of the following check boxes to specify the criteria used when displaying access points:•MAC Address—Enter the base radio MAC address of an access point.•AP Name—Enter the name of an access point.When you enable one of these filters, the other filter is disabledautomatically.Notec) Click Find to commit your changes. Only the access points that match your search criteria appear on the AP JoinStats page, and the Current Filter parameter at the top of the page specifies the filter used to generate the list (forexample, MAC Address:00:1e:f7:75:0a:a0 or AP Name:pmsk-ap).If you want to remove the filter and display the entire access point list, click ClearFilter.NoteStep 3 To see detailed join statistics for a specific access point, click the radio MAC address of the access point. The AP JoinStats Detail page appears.This page provides information from the controller’s perspective on each phase of the join process and shows any errorsthat have occurred.Cisco Wireless LAN Controller Configuration Guide, Release 7.4       OL-28744-01 719Troubleshooting the Access Point Join Process
Viewing Access Point Join Information (CLI)Use these CLI commands to see access point join information:•See the MAC addresses of all the access points that are joined to the controller or that have tried to joinby entering this command:show ap join stats summary all•See the last join error detail for a specific access point by entering this command:show ap join stats summary ap_macwhere ap_mac is the MAC address of the 802.11 radio interface.To obtain the MAC address of the 802.11 radio interface, enter the show interfacesDot11Radio 0 command on the access point.Information similar to the following appears:Is the AP currently connected to controller................ YesTime at which the AP joined this controller last time...... Aug 2112:50:36.061Type of error that occurred last........................... AP got or hasbeen disconnectedReason for error that occurred last........................ The AP hasbeen reset by the controllerTime at which the last join error occurred.............. Aug 2112:50:34.374Note•See all join-related statistics collected for a specific access point by entering this command:show ap join stats detailed ap_macInformation similar to the following appears:Discovery phase statistics- Discovery requests received.............................. 2- Successful discovery responses sent...................... 2- Unsuccessful discovery request processing................ 0- Reason for last unsuccessful discovery attempt........... Not applicable- Time at last successful discovery attempt................ Aug 21 12:50:23.335- Time at last unsuccessful discovery attempt.............. Not applicableJoin phase statistics- Join requests received................................... 1- Successful join responses sent........................... 1- Unsuccessful join request processing..................... 1- Reason for last unsuccessful join attempt................ RADIUS authorizationis pending for the AP- Time at last successful join attempt..................... Aug 21 12:50:34.481- Time at last unsuccessful join attempt................... Aug 21 12:50:34.374Configuration phase statistics- Configuration requests received.......................... 1- Successful configuration responses sent.................. 1- Unsuccessful configuration request processing............ 0- Reason for last unsuccessful configuration attempt....... Not applicable- Time at last successful configuration attempt............ Aug 21 12:50:34.374- Time at last unsuccessful configuration attempt.......... Not applicableLast AP message decryption failure details- Reason for last message decryption failure............... Not applicable   Cisco Wireless LAN Controller Configuration Guide, Release 7.4720 OL-28744-01  Troubleshooting the Access Point Join Process
Last AP disconnect details- Reason for last AP connection failure.................... The AP has been reset bythe controllerLast join error summary- Type of error that occurred last......................... AP got or has beendisconnected- Reason for error that occurred last...................... The AP has been reset bythe controller- Time at which the last join error occurred............... Aug 21 12:50:34.374•Clear the join statistics for all access points or for a specific access point by entering this command:clear ap join stats {all |ap_mac}Sending Debug Commands to Access Points Converted to Lightweight ModeYou can enable the controller to send debug commands to an access point converted to lightweight mode byentering this command:debug ap {enable |disable |command cmd}Cisco_APWhen this feature is enabled, the controller sends debug commands to the converted access point as characterstrings. You can send any debug command supported by Cisco Aironet access points that run Cisco IOSsoftware in lightweight mode.Understanding How Converted Access Points Send Crash Information to theControllerWhen a converted access point unexpectedly reboots, the access point stores a crash file on its local flashmemory at the time of the crash. After the unit reboots, it sends the reason for the reboot to the controller. Ifthe unit rebooted because of a crash, the controller pulls up the crash file using existing CAPWAP messagesand stores it in the controller flash memory. The crash info copy is removed from the access point flashmemory when the controller pulls it from the access point.Understanding How Converted Access Points Send Radio Core Dumps to theControllerWhen a radio module in a converted access point generates a core dump, the access point stores the core dumpfile of the radio on its local flash memory at the time of the radio crash. It sends a notification message to thecontroller indicating which radio generated a core dump file. The controller sends a trap that alerts you sothat you can retrieve the radio core file from the access point.The retrieved core file is stored in the controller flash and can be uploaded through TFTP or FTP to an externalserver for analysis. The core file is removed from the access point flash memory when the controller pulls itfrom the access point.Cisco Wireless LAN Controller Configuration Guide, Release 7.4       OL-28744-01 721Sending Debug Commands to Access Points Converted to Lightweight Mode
Retrieving Radio Core Dumps (CLI)Step 1 Transfer the radio core dump file from the access point to the controller by entering this command:config ap crash-file get-radio-core-dump slot Cisco_APFor the slot parameter, enter the slot ID of the radio that crashed.Step 2 Verify that the file was downloaded to the controller by entering this command:show ap crash-fileUploading Radio Core Dumps (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 Radio Core Dump.Step 3 From the Transfer Mode drop-down list, choose from the following options:•TFTP•FTP•SFTP (available in the 7.4 and later releases)Step 4 In the IP Address text box, enter the IP address of the server.Step 5 In the File Path text box, enter the directory path of the file.Step 6 In the File Name text box, enter the name of the radio core dump file.The filename that you enter should match the filename generated on the controller. You can determine thefilename on the controller by entering the show ap crash-file command.NoteStep 7 If you chose FTP as the Transfer Mode, follow these steps:a) In the Server Login Username text box, enter the FTP server login name.b) In the Server Login Password text box, enter the FTP server login password.c) In the Server Port Number text box, enter the port number of the FTP server. The default value for the server port is21.Step 8 Click Upload to upload the radio core dump file from the controller. A message appears indicating the status of theupload.   Cisco Wireless LAN Controller Configuration Guide, Release 7.4722 OL-28744-01  Understanding How Converted Access Points Send Radio Core Dumps to the Controller
Uploading Radio Core Dumps (CLI)Step 1 Transfer the file from the controller to a server by entering these commands:•transfer upload mode {tftp |ftp |sftp}•transfer upload datatype radio-core-dump•transfer upload serverip server_ip_address•transfer upload path server_path_to_file•transfer upload filename filenameThe filename that you enter should match the filename generated on the controller. You can determine thefilename on the controller by entering the show ap crash-file command.NoteEnsure that the filename and server_path_to_file do not contain these special characters: \, :, *, ?, ", <, >,and |. You can use only / (forward slash) as the path separator. If you use the disallowed special charactersin the filename, then the special characters are replaced with _ (underscores); and if you use the disallowedspecial characters in the server_path_to_file, then the path is set to the root path.NoteStep 2 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 3 View the updated settings by entering this command:transfer upload startStep 4 When prompted to confirm the current settings and start the software upload, answer y.Uploading Memory Core Dumps from Converted Access PointsBy default, access points converted to lightweight mode do not send memory core dumps to the controller.This section provides instructions to upload access point core dumps using the controller GUI or CLI.Cisco Wireless LAN Controller Configuration Guide, Release 7.4       OL-28744-01 723Uploading Memory Core Dumps from Converted Access Points
Uploading Access Point Core Dumps (GUI)Step 1 Choose Wireless >Access Points >All APs >access point name > and choose the Advanced tab to open the All APs> Details for (Advanced) page.Step 2 Select the AP Core Dump check box to upload a core dump of the access point.Step 3 In the TFTP Server IP text box, enter the IP address of the TFTP server.Step 4 In the File Name text box, enter a name of the access point core dump file (such as dump.log).Step 5 Select the File Compression check box to compress the access point core dump file. When you enable this option, thefile is saved with a .gz extension (such as dump.log.gz). This file can be opened with WinZip.Step 6 Click Apply to commit your changes.Step 7 Click Save Configuration to save your changes.Uploading Access Point Core Dumps (CLI)Step 1 Upload a core dump of the access point by entering this command on the controller:config ap core-dump enable tftp_server_ip_address filename {compress |uncompress} {ap_name |all}where•tftp_server_ip_address is the IP address of the TFTP server to which the access point sends core dump files.The access point must be able to reach the TFTPserver.Note•filename is the name that the access points uses to label the core file.•compress configures the access point to send compressed core files whereas uncompress configures the accesspoint to send uncompressed core files.When you choose compress, the file is saved with a .gz extension (for example, dump.log.gz). This filecan be opened with WinZip.Note•ap_name is the name of a specific access point for which core dumps are uploaded and all is all access pointsconverted to lightweight mode.Step 2 Enter the save config command to save your changes.Viewing the AP Crash Log InformationWhenever the controller reboots or upgrades, the AP crash log information gets deleted from the controller.We recommend that you make a backup of AP crash log information before rebooting or upgrading thecontroller.   Cisco Wireless LAN Controller Configuration Guide, Release 7.4724 OL-28744-01  Viewing the AP Crash Log Information
Viewing the AP Crash Log information (GUI)•Choose Management >Tech Support >AP Crash Log to open the AP Crash Logs page.Viewing the AP Crash Log information (CLI)Step 1 Verify that the crash file was downloaded to the controller by entering this command:show ap crash-fileInformation similar to the following appears:Local Core Files:lrad_AP1130.rdump0 (156)The number in parentheses indicates the size of the file. The size should be greater than zero if acore dump file is available.Step 2 See the contents of the AP crash log file by entering this command:show ap crash-file Cisoc_APDisplaying MAC Addresses for Converted Access PointsThere are some differences in the way that controllers display the MAC addresses of converted access pointson information pages in the controller GUI:•On the AP Summary page, the controller lists the Ethernet MAC addresses of converted access points.•On the AP Detail page, the controller lists the BSS MAC addresses and Ethernet MAC addresses ofconverted access points.•On the Radio Summary page, the controller lists converted access points by radio MAC address.Disabling the Reset Button on Access Points Converted to Lightweight ModeYou can disable the reset button on access points converted to lightweight mode. The reset button is labeledMODE on the outside of the access point.Use this command to disable or enable the reset button on one or all converted access points associated to acontroller:config ap rst-button {enable |disable} {ap-name}The reset button on converted access points is enabled by default.Cisco Wireless LAN Controller Configuration Guide, Release 7.4       OL-28744-01 725Displaying MAC Addresses for Converted Access Points
Configuring a Static IP Address on a Lightweight Access PointIf you want to specify an IP address for an access point rather than having one assigned automatically by aDHCP server, you can use the controller GUI or CLI to configure a static IP address for the access point.Static IP addresses are generally used only for deployments with a limited number of users.An access point cannot discover the controller using domain name system (DNS) resolution if a static IPaddress is configured for the access point, unless you specify a DNS server and the domain to which the accesspoint belongs. Previously, these parameters could be configured only using the CLI, but controller softwarerelease 6.0 or later releases expand this functionality to the GUI.If you configure an access point to use a static IP address that is not on the same subnet on which theaccess point’s previous DHCP address was, the access point falls back to a DHCP address after the accesspoint reboots. If the access point falls back to a DHCP address, enter the show ap config general Cisco_APCLI command to show that the access point is using a fallback IP address. However, the GUI shows boththe static IP address and the DHCP address, but it does not identify the DHCP address as a fallback address.NoteConfiguring a Static IP Address (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 configure a static IP address. The All APs > Details for (General)page appears.Step 3 Under IP Config, select the Static IP check box if you want to assign a static IP address to this access point. The defaultvalue is unselected.Step 4 Enter the static IP address, netmask, and default gateway in the corresponding text boxes.Step 5 Click Apply to commit your changes. The access point reboots and rejoins the controller, and the static IP address thatyou specified in Step 4 is sent to the access point.Step 6 After the static IP address has been sent to the access point, you can configure the DNS server IP address and domainname as follows:a) In the DNS IP Address text box, enter the IP address of the DNS server.b) In the Domain Name text box, enter the name of the domain to which the access point belongs.c) Click Apply to commit your changes.d) Click Save Configuration to save your changes.Configuring a Static IP Address (CLI)Step 1 Configure a static IP address on the access point by entering this command:config ap static-ip enable Cisco_AP ip_address mask gateway   Cisco Wireless LAN Controller Configuration Guide, Release 7.4726 OL-28744-01  Configuring a Static IP Address on a Lightweight Access Point
To disable static IP for the access point, enter the config ap static-ip disable Cisco_AP command.NoteStep 2 Enter the save config command to save your changes.The access point reboots and rejoins the controller, and the static IP address that you specified in Step 1 is pushed to theaccess point.Step 3 After the static IP address has been sent to the access point, you can configure the DNS server IP address and domainname as follows:a) To specify a DNS server so that a specific access point or all access points can discover the controller using DNSresolution, enter this command:config ap static-ip add nameserver {Cisco_AP |all}ip_addressTo delete a DNS server for a specific access point or all access points, enter the config ap static-ip deletenameserver {Cisco_AP |all} command.Noteb) To specify the domain to which a specific access point or all access points belong, enter this command:config ap static-ip add domain {Cisco_AP |all}domain_nameTo delete a domain for a specific access point or all access points, enter this command: config ap static-ipdelete domain {Cisco_AP |all}.Notec) Enter the save config command to save your changes.Step 4 See the IP address configuration for the access point by entering this command:show ap config general Cisco_APInformation similar to the following appears:Cisco AP Identifier.............................. 4Cisco AP Name................................. AP6...IP Address Configuration......................... Static IP assignedIP Address....................................... 10.10.10.118IP NetMask....................................... 255.255.255.0Gateway IP Addr............................... 10.10.10.1Domain........................................... Domain1Name Server................................... 10.10.10.205...Supporting Oversized Access Point ImagesController software release 5.0 or later releases allow you to upgrade to an oversized access point image byautomatically deleting the recovery image to create sufficient space.The recovery image provides a backup image that can be used if an access point power-cycles during an imageupgrade. The best way to avoid the need for access point recovery is to prevent an access point frompower-cycling during a system upgrade. If a power-cycle occurs during an upgrade to an oversized accesspoint image, you can recover the access point using the TFTP recovery procedure.Cisco Wireless LAN Controller Configuration Guide, Release 7.4       OL-28744-01 727Supporting Oversized Access Point Images
Recovering the Access Point—Using the TFTP Recovery ProcedureStep 1 Download the required recovery image from Cisco.com (c1100-rcvk9w8-mx, c1200-rcvk9w8-mx, or c1310-rcvk9w8-mx)and install it in the root directory of your TFTP server.Step 2 Connect the TFTP server to the same subnet as the target access point and power-cycle the access point. The access pointboots from the TFTP image and then joins the controller to download the oversized access point image and completethe upgrade procedure.Step 3 After the access point has been recovered, you may remove the TFTP server.   Cisco Wireless LAN Controller Configuration Guide, Release 7.4728 OL-28744-01  Supporting Oversized Access Point Images
CHAPTER 108Configuring Packet Capture•Information About Packet Capture, page 729•Restrictions for Packet Capture, page 730•Configuring Packet Capture (CLI), page 730Information About Packet CaptureTo resolve issues such as voice and security on wireless networks, you might need to dump packets from theAP for analysis while the AP continues to operate normally. The packets can be dumped on to an FTP server.This process of dumping packets for analysis is called Packet Capture. Use the controller to start or stop packetcapture for clients. You can choose the type of packets that need to be captured using the controller CLI fromthe following types:•Management Packets•Control Packets•Data Packets•Dot1X•ARP•IAPP•All IP•UDP with matching port number•DHCP•TCP with matching port number•Multicast frames•Broadcast framesThe packets are captured and dumped in the order of arrival or transmit of packets except for beacons andprobe responses. The packet capture contains information such as channel, RSSI, data rate, SNR, and timestamp.Cisco Wireless LAN Controller Configuration Guide, Release 7.4        OL-28744-01 729
Each packet is appended with additional information from the AP. You can choose to dump either just packetheaders or full packets.The following are some guidelines for packet capture:•If FTP transfer time is slower than the packet rate, some of the packets do not appear in the capture file.•If the buffer does not contain any packets, a known dummy packet is dumped to keep the connectionalive.•A file is created on the FTP server for each AP based on unique AP and controller name and timestamp.Ensure that the FTP server is reachable by the AP.•If the FTP transfer fails or FTP connection is lost during packet capture, the AP stops capturing packets,notifies with an error message and SNMP trap, and a new FTP connection is established.Restrictions for Packet Capture•Packet capture can be enabled for only one client.•This feature is not supported in intercontroller roaming scenarios. If you know the AP or the controllerto which the client is going to roam, you can configure the packet capture for the client in the newcontroller or AP using the CLI.•Not all packets in the air are captured, but only those that reach the radio driver.•By default, a packet capture process is stopped after 10 minutes. You can, however, configure the packetcapture to stop at any time between 1 to 60 minutes.Configuring Packet Capture (CLI)Step 1 Configure FTP parameters for packet capture by entering this command:config ap packet-dump ftp serverip ip-address path path username user_ID password passwordStep 2 Start or stop packet capture by entering this command:config ap packet-dump {start client-mac-address ap-name |stop}Step 3 Configure the buffer size for packet capture by entering this command:config ap packet-dump buffer-size size-in-kbStep 4 Configure the time for packet capture by entering this command:config ap packet-dump capture-time time-in-minutesThe valid range is between 1 to 60 minutes.Step 5 Configure the types of packets to be captured by entering this command:config ap packet-dump classifier {arp |broadcast |control |data |dot1x |iapp |ip |management |multicast | {tcpport port-number} | {udp port port-number}} {enable |disable}Step 6 Configure the packet length after truncation by entering this command:config ap packet-dump truncate length-in-bytes   Cisco Wireless LAN Controller Configuration Guide, Release 7.4730 OL-28744-01  Restrictions for Packet Capture
Step 7 Know the status of packet capture by entering this command:show ap packet-dump statusStep 8 Configure debugging of packet capture by entering this command:debug ap packet-dump {enable |disable}Cisco Wireless LAN Controller Configuration Guide, Release 7.4       OL-28744-01 731Configuring Packet Capture (CLI)
   Cisco Wireless LAN Controller Configuration Guide, Release 7.4732 OL-28744-01  Configuring Packet Capture (CLI)
CHAPTER 109Configuring OfficeExtend Access Points•Information About OfficeExtend Access Points, page 733•OEAP 600 Series Access Points, page 734•Implementing Security, page 742•Licensing for an OfficeExtend Access Point, page 743•Configuring OfficeExtend Access Points, page 743•Configuring a Personal SSID on an OfficeExtend Access Point, page 747•Viewing OfficeExtend Access Point Statistics, page 749Information About OfficeExtend Access PointsA Cisco 600 Series OfficeExtend access point (Cisco OEAP) provides secure communications from a controllerto an access point at a remote location, seamlessly extending the corporate WLAN over the Internet to anemployee’s residence. The user’s experience at the home office is exactly the same as it would be at thecorporate office. Datagram Transport Layer Security (DTLS) encryption between the access point and thecontroller ensures that all communications have the highest level of security.DTLS is permanently enabled on the Cisco OEAP. You cannot disable DTLS on this access point.NoteThe following figure shows a typical OfficeExtend access point setup.Cisco Wireless LAN Controller Configuration Guide, Release 7.4        OL-28744-01 733
Figure 49: Typical OfficeExtend Access Point SetupCisco OEAPs are designed to work behind a router or other gateway device that is using network addresstranslation (NAT). NAT allows a device, such as a router, to act as an agent between the Internet (public)and a personal network (private), enabling an entire group of computers to be represented by a single IPaddress. There is no limit to the number of Cisco OEAPs that you can deploy behind a NAT device.Roaming is not supported for the Cisco 600 OEAP model.NoteCurrently, Cisco 1040, 1130, 1140, 2602I, 3502I, and 3600 series access points that are associated with acontroller can be configured to operate as Cisco OEAPs.OEAP 600 Series Access PointsThis section details the requirements for configuring a Cisco wireless LAN controller for use with the Cisco600 Series OfficeExtend Access Point. The 600 Series OfficeExtend Access Point supports split mode operation,and it requires configuration through the WLAN controller in local mode. This section describes theconfigurations necessary for proper connection and supported feature sets.The CAPWAP UDP 5246 and 5247 ports must be open on the firewall between the WLAN controllerand the 600 Series OfficeExtend Access Point.NoteMulticast is not supported on Cisco 600 Series OfficeExtend Access Points.NoteOEAP in Local ModeThe 600 Series OfficeExtend Access Point connects to the controller in local mode. You cannot alter thesesettings.   Cisco Wireless LAN Controller Configuration Guide, Release 7.4734 OL-28744-01  OEAP 600 Series Access Points
Monitor mode, flexconnect mode, sniffer mode, rogue detector, bridge, and SE-Connect are not supportedon the 600 Series OfficeExtend Access Point and are not configurable.Figure 50: OEAP ModeNoteSupported WLAN Settings for 600 Series OfficeExtend Access PointThe 600 Series OfficeExtend Access Point supports a maximum of three WLANs and one remote LAN. Ifyour network deployment has more than three WLANs, you must place the 600 Series OfficeExtend AccessPoint in an AP group. If the 600 Series OfficeExtend Access Points are added to an AP group, the same limitof three WLANs and one remote LAN still applies for the configuration of the AP group.If the 600 Series OfficeExtend Access Point is in the default group, which means that it is not in a definedAP group, the WLAN/remote LAN IDs must be set lower than ID 8.If additional WLANs or remote LANs are created with the intent of changing the WLANs or remote LANbeing used by the 600 Series OfficeExtend Access Point, you must disable the current WLANs or remoteLAN that you are removing before enabling the new WLANs or remote LAN on the 600 Series OfficeExtendAccess Point. If there are more than one remote LANs enabled for an AP group, disable all remote LANs andthen enable only one of them.If more than three WLANs are enabled for an AP group, disable all WLANs and then enable only three ofthem.WLAN Security Settings for the 600 Series OfficeExtend Access PointWhen configuring the security settings in the WLAN (see the following figure), note that there are specificelements that are not supported on the 600 Series OfficeExtend Access Point. CCX is not supported on the600 Series OfficeExtend Access Point, and elements related to CCX are not supported.For Layer 2 Security, the following options are supported for the 600 Series OfficeExtend Access Point:Cisco Wireless LAN Controller Configuration Guide, Release 7.4       OL-28744-01 735OEAP 600 Series Access Points
•None•WPA+WPA2•Static WEP•802.1X (only for remote LANs)Figure 51: WLAN Layer 2 Security SettingsIn the Security tab (see the following figure), do not select CCKM in WPA+WPA2 settings. Select only802.1X or PSK.Figure 52: WLAN Security Settings - Auth Key Management   Cisco Wireless LAN Controller Configuration Guide, Release 7.4736 OL-28744-01  OEAP 600 Series Access Points
Security encryption settings must be identical for WPA and WPA2 for TKIP and AES. The following areexamples of incompatible settings for TKIP and AES.Figure 53: Incompatible WPA and WPA2 Security Encryption Settings for OEAP 600 SeriesFigure 54: Incompatible WPA and WPA2 Security Encryption Settings for OEAP 600 SeriesCisco Wireless LAN Controller Configuration Guide, Release 7.4       OL-28744-01 737OEAP 600 Series Access Points
The following are examples of compatible settings:Figure 55: Compatible Security Settings for OEAP SeriesFigure 56: Compatible Security Settings for OEAP SeriesQoS settings are supported (see the following figure), but CAC is not supported and should not be enabled.Do not enable Coverage Hole Detection.Note   Cisco Wireless LAN Controller Configuration Guide, Release 7.4738 OL-28744-01  OEAP 600 Series Access Points
Aironet IE should not be enabled. This option is not supported.Figure 57: QoS Settings for OEAP 600NoteMFP is also not supported and should be disabled or set to optional.Figure 58: MFP Settings for OEAP Series Access PointsClient Load Balancing and Client Band Select are not supported.Authentication SettingsFor authentication on the 600 Series OfficeExtend Access Point, LEAP is not supported. This configurationmust be addressed on the clients and RADIUS servers to migrate them to EAP-Fast, EAP-TTLS, EAP-TLS,or PEAP.If Local EAP is being utilized on the controller, the settings would also have to be modified not to use LEAP.Cisco Wireless LAN Controller Configuration Guide, Release 7.4       OL-28744-01 739OEAP 600 Series Access Points
Supported User Count on 600 Series OfficeExtend Access PointOnly 15 users are allowed to connect on the WLANs provided on the Cisco 600 Series OEAP at any one time,a sixteenth user cannot authenticate until one of the first clients is deauthenticated or timeout on the controlleroccurs. This number is cumulative across the controller WLANs on the 600 Series OfficeExtend Access Point.For example, if two controller WLANs are configured and there are 15 users on one of the WLANs, no otherusers can join the other WLAN on the 600 Series OfficeExtend Access Point at that time.This limit does not apply to the local private WLANs that the end user configures on the 600 SeriesOfficeExtend Access Point for personal use. Clients connected on these private WLANs or on the wired portsdo not affect these limits.This limit does not apply to other AP models that operate in the OfficeExtend mode.NoteRemote LAN SettingsOnly four clients can connect through a remote LAN port on the 600 Series OfficeExtend Access Point. Thisnumber does not affect the fifteen user limit imposed for the Controller WLANs. The remote LAN client limitsupports connecting a switch or hub to the remote LAN port for multiple devices or connecting directly to aCisco IP phone that is connected to that port. Only the first four devices can connect until one of the devicesis idle for more than one minute.Remote LAN is configured in the same way that a WLAN or Guest LAN is configured on the controller:Figure 59: Remote LAN Settings for OEAP 600 Series AP   Cisco Wireless LAN Controller Configuration Guide, Release 7.4740 OL-28744-01  OEAP 600 Series Access Points
Security settings can be left open, set for MAC filtering, or set for Web Authentication. The default is to useMAC filtering. Additionally, you can specify 802.1X Layer 2 security settings.Figure 60: Layer 2 Security Settings for OEAP 600 Series APs in Remote LANsFigure 61: Layer 3 Security Settings for OEAP 600 Series APs in Remote LANsChannel Management and SettingsThe radios for the 600 Series OfficeExtend Access Point are controlled through the Local GUI on the accesspoint and not through the Wireless LAN Controller. Attempting to control the spectrum channel or power, orto disable the radios through the controller does not have effect on the 600 Series OfficeExtend Access Point.RRM is not supported on the 600 Series OfficeExtend Access Point.The 600 series scans and chooses channels for 2.4-GHz and 5-GHz during startup as long as the default settingson the local GUI are left as default in both spectrums.Figure 62: Channel Selection for OEAP 600 Series APsCisco Wireless LAN Controller Configuration Guide, Release 7.4       OL-28744-01 741OEAP 600 Series Access Points
The channel bandwidth for 5.0 GHz is also configured on the 600 Series OfficeExtend Access Point LocalGUI, for 20-MHz or 40-MHz wide channels. Setting the channel width to 40 MHz for 2.4 GHz is not supportedand fixed at 20 MHz.Figure 63: Channel Width for OEAP 600 APsAdditional Caveats•The Cisco 600 Series OfficeExtend Access Points (OEAPs) are designed for single AP deployments,therefore client roaming between Cisco 600 Series OEAPs is not supported.Disabling the 802.11a/n or 802.11b/g/n on the controller may not disable these spectrums on the Cisco600 Series OEAP because local SSID may be still working.•Your firewall must be configured to allow traffic from access points using CAPWAP. Make sure thatUDP ports 5246 and 5247 are enabled and are not blocked by an intermediate device that could preventan access point from joining the controller.•APs such as 3500, 3600, 1260, 2600, and 1040 that are converted to OEAP mode and mapped to locallyswitched WLAN forward the DHCP request to the local subnet on the AP connected switch. To avoidthis condition, you must disable local switching and local authentication.•For Cisco 600 Series OEAP to associate with Cisco Virtual Wireless LAN Controller, follow these steps:1Configure the OEAP to associate with a physical controller that is using 7.5 or a later release anddownload the corresponding AP image.2Configure the OEAP so that the OEAP does not associate with the physical controller again; forexample, you can implement an ACL in the network to block CAPWAP between the OEAP and thephysical controller.3Configure the OEAP to associate with the Cisco Virtual Wireless LAN Controller.Implementing SecurityConfiguring LSC is not a requirement but is an option. The OfficeExtend 600 access points do not supportLSC.Note   Cisco Wireless LAN Controller Configuration Guide, Release 7.4742 OL-28744-01  Implementing Security
1Use local significant certificates (LSCs) to authorize your OfficeExtend access points, by following theinstructions in Authorizing Access Points Using LSCs.2Implement AAA server validation using the access point’s MAC address, name, or both as the usernamein authorization requests, by entering this command:config auth-list ap-policy authorize-ap username {ap_mac |Cisco_AP |both}Using the access point name for validation can ensure that only the OfficeExtend access points of validemployees can associate with the controller. To implement this security policy, ensure that you name eachOfficeExtend access point with an employee ID or employee number. When an employee is terminated,run a script to remove this user from the AAA server database, which prevents that employee’s OfficeExtendaccess point from joining the network.3Save your changes by entering this command:save configCCX is not supported on the 600 OEAP. Elements related to CCX are not supported. Also, only 802.1Xor PSK is supported. TKIP and AES security encryption settings must be identical for WPA and WPA2.NoteLicensing for an OfficeExtend Access PointTo use OfficeExtend access points, a base license must be installed and in use on the controller. After thelicense is installed, you can enable the OfficeExtend mode on the following AP models:•1130•1240•1040•1140•1250•1260•1600•2600•3500 (integrated antenna) series•3600 (integrated antenna) seriesConfiguring OfficeExtend Access PointsAfter the 1130 series, 1140 series, 1040 series, 3500 (integrated antenna) series, or 3600 (integrated antenna)series access point has joined the controller, you can configure it as an OfficeExtend access point.Cisco Wireless LAN Controller Configuration Guide, Release 7.4       OL-28744-01 743Licensing for an OfficeExtend Access Point
Configuring OfficeExtend Access Points (GUI)Step 1 Choose Wireless to open the All APs page.Step 2 Click the name of the desired access point to open the All APs > Details page.Step 3 Enable FlexConnect on the access point as follows:a) In the General tab, choose FlexConnect from the AP Mode drop-down list to enable FlexConnect for this accesspoint.Step 4 Configure one or more controllers for the access point as follows:a) Click the High Availability tab.b) Enter the name and IP address of the primary controller for this access point in the Primary Controller Name andManagement IP Address text boxes.You must enter both the name and IP address of the controller. Otherwise, the access point cannot join thiscontroller.Notec) If desired, enter the name and IP address of a secondary or tertiary controller (or both) in the corresponding ControllerName and Management IP Address text boxes.d) Click Apply. The access point reboots and then rejoins the controller.The names and IP addresses must be unique for the primary, secondary, and tertiary controllers.NoteStep 5 Enable OfficeExtend access point settings as follows:a) Click the FlexConnect tab.b) Select the Enable OfficeExtend AP check box to enable the OfficeExtend mode for this access point. The defaultvalue is selected.Unselecting this check box disables OfficeExtend mode for this access point. It does not undo all of the configurationsettings on the access point. If you want to clear the access point’s configuration and return it to the factory-defaultsettings, enter clear ap config Cisco_AP on the controller CLI. If you want to clear only the access point’s personalSSID, click Reset Personal SSID.Rogue detection is disabled automatically when you enable the OfficeExtend mode for an access point.However, you can enable or disable rogue detection for a specific access point by selecting the RogueDetection check box on the All APs > Details for (Advanced) page. Rogue detection is disabled by defaultfor OfficeExtend access points because these access points, which are deployed in a home environment, arelikely to detect a large number of rogue devices.NoteDTLS data encryption is enabled automatically when you enable the OfficeExtend mode for an access point.However, you can enable or disable DTLS data encryption for a specific access point by selecting the DataEncryption check box on the All APs > Details for (Advanced) page.NoteTelnet and SSH access are disabled automatically when you enable the OfficeExtend mode for an accesspoint. However, you can enable or disable Telnet or SSH access for a specific access point by selecting theTelnet or SSH check box on the All APs > Details for (Advanced) page.NoteLink latency is enabled automatically when you enable the OfficeExtend mode for an access point. However,you can enable or disable link latency for a specific access point by selecting the Enable Link Latencycheck box on the All APs > Details for (Advanced) page.Notec) Select the Enable Least Latency Controller Join check box if you want the access point to choose the controllerwith the least latency when joining. Otherwise, leave this check box unselected, which is the default value. Whenyou enable this feature, the access point calculates the time between the discovery request and discovery responseand joins the Cisco 5500 Series Controller that responds first.   Cisco Wireless LAN Controller Configuration Guide, Release 7.4744 OL-28744-01  Configuring OfficeExtend Access Points
d) Click Apply.The OfficeExtend AP text box on the All APs page shows which access points are configured as OfficeExtend accesspoints.Step 6 Configure a specific username and password for the OfficeExtend access point so that the user at home can log into theGUI of the OfficeExtend access point:a) Click the Credentials tab.b) Select the Over-ride Global Credentials check box to prevent this access point from inheriting the global username,password, and enable password from the controller. The default value is unselected.c) In the Username,Password, and Enable Password text boxes, enter the unique username, password, and enablepassword that you want to assign to this access point.The information that you enter is retained across controller and access point reboots and if the access pointjoins a new controller.Noted) Click Apply.If you want to force this access point to use the controller’s global credentials, unselect the Over-ride GlobalCredentials check box.NoteStep 7 Configure access to local GUI, LAN ports, and local SSID of the OfficeExtend access points:a) Choose Wireless > Access Points > Global Configuration to open the Global Configuration page.b) Under OEAP Config Parameters, select or unselect the Disable Local Access check box to enable or disable localaccess of the OfficeExtend access points.By default, the Disable Local Access check box is unselected and therefore the Ethernet ports and personalSSIDs are enabled. This configuration does not affect remote LAN. The port is enabled only when youconfigure a remote LAN.NoteStep 8 Click Save Configuration.Step 9 If your controller supports only OfficeExtend access points, see the Configuring RRM section for instructions on settingthe recommended values for the DCA interval, channel scan duration, and neighbor packet frequency.Configuring OfficeExtend Access Points (CLI)•Enable FlexConnect on the access point by entering this command:config ap mode flexconnect Cisco_AP•Configure one or more controllers for the access point by entering one or all of these commands:config ap primary-base controller_name Cisco_AP controller_ip_addressconfig ap secondary-base controller_name Cisco_AP controller_ip_addressconfig ap tertiary-base controller_name Cisco_AP controller_ip_addressYou must enter both the name and IP address of the controller. Otherwise, the access point cannot jointhis controller.NoteCisco Wireless LAN Controller Configuration Guide, Release 7.4       OL-28744-01 745Configuring OfficeExtend Access Points
The names and IP addresses must be unique for the primary, secondary, and tertiary controllers.Note•Enable the OfficeExtend mode for this access point by entering this command:config flexconnect office-extend {enable |disable}Cisco_APThe default value is enabled. The disable parameter disables OfficeExtend mode for this access point.It does not undo all of the configuration settings on the access point. If you want to clear the accesspoint’s configuration and return it to the factory-default settings, enter this command:clear ap config cisco-apIf you want to clear only the access point’s personal SSID, enter this command:config flexconnect office-extend clear-personalssid-config Cisco_AP.Rogue detection is disabled automatically when you enable the OfficeExtend mode for an access point.However, you can enable or disable rogue detection for a specific access point or for all access pointsusing the config rogue detection {enable |disable} {Cisco_AP |all} command. Rogue detection isdisabled by default for OfficeExtend access points because these access points, which are deployed in ahome environment, are likely to detect a large number of rogue devices.NoteDTLS data encryption is enabled automatically when you enable the OfficeExtend mode for an accesspoint. However, you can enable or disable DTLS data encryption for a specific access point or for allaccess points using the config ap link-encryption {enable |disable} {Cisco_AP |all} command.NoteTelnet and SSH access are disabled automatically when you enable the OfficeExtend mode for an accesspoint. However, you can enable or disable Telnet or SSH access for a specific access point using the configap {telnet |ssh} {enable |disable}Cisco_AP command.NoteLink latency is enabled automatically when you enable the OfficeExtend mode for an access point.However, you can enable or disable link latency for a specific access point or for all access points currentlyassociated to the controller using the config ap link-latency {enable |disable} {Cisco_AP |all} command.Note•Enable the access point to choose the controller with the least latency when joining by entering thiscommand:config flexconnect join min-latency {enable |disable}Cisco_APThe default value is disabled. When you enable this feature, the access point calculates the time betweenthe discovery request and discovery response and joins the Cisco 5500 Series Controller that respondsfirst.•Configure a specific username and password that users at home can enter to log into the GUI of theOfficeExtend access point by entering this command:   Cisco Wireless LAN Controller Configuration Guide, Release 7.4746 OL-28744-01  Configuring OfficeExtend Access Points
config ap mgmtuser add username user password password enablesecret enable_password Cisco_APThe credentials that you enter in this command are retained across controller and access point rebootsand if the access point joins a new controller.If you want to force this access point to use the controller’s global credentials, enter the config ap mgmtuserdelete Cisco_AP command. The following message appears after you execute this command: “AP revertedto global username configuration.”Note•To configure access to the local network for the Cisco 600 Series OfficeExtend access points, enter thefollowing command:config network oeap-600 local-network {enable |disable}When disabled, the local SSIDs, local ports are inoperative; and the console is not accessible. Whenreset, the default restores local access. This configuration does not affect the remote LAN configurationif configured on the access points.•Configure the Dual R-LAN Ports feature, which allows the Ethernet port 3 of Cisco 600 SeriesOfficeExtend access points to operate as a remote LAN by entering this command:config network oeap-600 dual-rlan-ports {enable |disable}This configuration is global to the controller and is stored by the AP and the NVRAM variable. Whenthis variable is set, the behavior of the remote LAN is changed. This feature supports different remoteLANs per remote LAN port.The remote LAN mapping is different depending on whether the default group or AP Groups is used:•Default Group—If you are using the default group, a single remote LAN with an even numberedremote LAN ID is mapped to port 4. For example, a remote LAN with remote LAN ID 2 is mappedto port 4 (on the Cisco 600 OEAP). The remote LAN with an odd numbered remote LAN ID ismapped to port 3 (on the Cisco 600 OEAP). For example, a remote LAN with remote LAN ID 1is mapped to port 3 (on the Cisco 600 OEAP).•AP Groups—If you are using an AP group, the mapping to the OEAP-600 ports is determined bythe order of the AP groups. To use an AP group, you must first delete all remote LANs and WLANsfrom the AP group leaving it empty. Then, add the two remote LANs to the AP group adding theport 3 AP remote LAN first, and the port 4 remote group second, followed by any WLANs.•Save your changes by entering this command:save configIf your controller supports only OfficeExtend access points, see the Configuring Radio ResourceManagement section for instructions on setting the recommended value for the DCA interval.NoteConfiguring a Personal SSID on an OfficeExtend Access PointStep 1 Find the IP address of your OfficeExtend access point by doing one of the following:Cisco Wireless LAN Controller Configuration Guide, Release 7.4       OL-28744-01 747Configuring a Personal SSID on an OfficeExtend Access Point
Log on to your home router and look for the IP address of your OfficeExtend access point.••Ask your company’s IT professional for the IP address of your OfficeExtend access point.•Use an application such as Network Magic to detect devices on your network and their IP addresses.Step 2 With the OfficeExtend access point connected to your home router, enter the IP address of the OfficeExtend access pointin the Address text box of your Internet browser and click Go.Make sure that you are not connected to your company’s network using a virtual private network (VPN)connection.NoteStep 3 When prompted, enter the username and password to log into the access point.Step 4 On the OfficeExtend Access Point Welcome page, click Enter. The OfficeExtend Access Point Home page appears.Figure 64: OfficeExtend Access Point Home PageThis page shows the access point name, IP address, MAC address, software version, status, channel, transmit power,and client traffic.   Cisco Wireless LAN Controller Configuration Guide, Release 7.4748 OL-28744-01  Configuring a Personal SSID on an OfficeExtend Access Point
Step 5 Choose Configuration to open the Configuration page.Figure 65: OfficeExtend Access Point Configuration PageStep 6 Select the Personal SSID check box to enable this wireless connection. The default value is disabled.Step 7 In the SSID text box, enter the personal SSID that you want to assign to this access point. This SSID is locally switched.A controller with an OfficeExtend access point publishes only up to 15 WLANs to each connected access pointbecause it reserves one WLAN for the personal SSID.NoteStep 8 From the Security drop-down list, choose Open,WPA2/PSK (AES), or 104 bit WEP to set the security type to be usedby this access point.If you choose WPA2/PSK (AES), make sure that the client is configured for WPA2/PSK and AES encryption.NoteStep 9 If you chose WPA2/PSK (AES) in Step 8, enter an 8- to 38-character WPA2 passphrase in the Secret text box. If youchose 104 bit WEP, enter a 13-character ASCII key in the Key text box.Step 10 Click Apply.If you want to use the OfficeExtend access point for another application, you can clear this configuration andreturn the access point to the factory-default settings by clicking Clear Config. You can also clear the accesspoint’s configuration from the controller CLI by entering the clear ap config Cisco_AP command.NoteViewing OfficeExtend Access Point StatisticsUse these commands to view information about the OfficeExtend access points on your network:•See a list of all OfficeExtend access points by entering this command:show flexconnect office-extend summaryCisco Wireless LAN Controller Configuration Guide, Release 7.4       OL-28744-01 749Viewing OfficeExtend Access Point Statistics
•See the link delay for OfficeExtend access points by entering this command:show flexconnect office-extend latency•See the encryption state of all access points or a specific access point by entering this command:show ap link-encryption {all |Cisco_AP}This command also shows authentication errors, which track the number of integrity check failures, andreplay errors, which track the number of times that the access point receives the same packet. See thedata plane status for all access points or a specific access point by entering this command:show ap data-plane {all |Cisco_AP}   Cisco Wireless LAN Controller Configuration Guide, Release 7.4750 OL-28744-01  Viewing OfficeExtend Access Point Statistics
CHAPTER 110Using Cisco Workgroup Bridges•Information About Cisco Workgroup Bridges, page 751•Restrictions for Cisco Workgroup Bridges, page 753•WGB Configuration Example, page 754•Viewing the Status of Workgroup Bridges (GUI), page 755•Viewing the Status of Workgroup Bridges (CLI), page 755•Debugging WGB Issues (CLI), page 756Information About Cisco Workgroup BridgesA workgroup bridge (WGB) is a mode that can be configured on an autonomous IOS access point to providewireless connectivity to a lightweight access point on behalf of clients that are connected by Ethernet to theWGB access point. A WGB connects a wired network over a single wireless segment by learning the MACaddresses of its wired clients on the Ethernet interface and reporting them to the lightweight access point usingInternet Access Point Protocol (IAPP) messaging. The WGB provides wireless access connectivity to wiredclients by establishing a single wireless connection to the lightweight access point. The lightweight accesspoint treats the WGB as a wireless client.Cisco Wireless LAN Controller Configuration Guide, Release 7.4        OL-28744-01 751
A Cisco IOS AP as a WGB using the Cisco IOS 15.2 or later releases support Protected ExtensibleAuthentication Protocol (PEAP) with the controller.Figure 66: WGB ExampleIf the lightweight access point fails, the WGB attempts to associate to another access point.NoteThe following are some guidelines for Cisco Workgroup Bridges:•The WGB can be any autonomous access point that supports the workgroup bridge mode and is runningCisco IOS Release 12.4(3g)JA or later releases (on 32-MB access points) or Cisco IOS Release 12.3(8)JEBor later releases (on 16-MB access points). These access points include the AP1120, AP1121, AP1130,AP1231, AP1240, and AP1310. Cisco IOS releases prior to 12.4(3g)JA and 12.3(8)JEB are not supported.If your access point has two radios, you can configure only one for workgroup bridgemode. This radio is used to connect to the lightweight access point. We recommend thatyou disable the second radio.Enable the workgroup bridge mode on the WGB as follows:Note•On the WGB access point GUI, choose Workgroup Bridge for the role in radionetwork on the Settings > Network Interfaces page.•On the WGB access point CLI, enter the station-role workgroup-bridgecommand.See the sample WGB access point configuration in the WGB Configuration Examplesection.Note•The following features are supported for use with a WGB:◦Guest N+1 redundancy◦Local EAP   Cisco Wireless LAN Controller Configuration Guide, Release 7.4752 OL-28744-01  Information About Cisco Workgroup Bridges
◦Open, WEP 40, WEP 128, CKIP, WPA+TKIP, WPA2+AES, LEAP, EAP-FAST, and EAP-TLSauthentication modes•Wired clients connected to the WGB are not authenticated for security. Instead, the WGB is authenticatedagainst the access point to which it associates. Therefore, we recommend that you physically secure thewired side of the WGB.•Wired clients connected to a WGB inherit the WGB’s QoS and AAA override attributes.•To enable the WGB to communicate with the lightweight access point, create a WLAN and make surethat Aironet IE is enabled.•If you have to apply ACL to WGB during run time, do not modify the ACL configuration for interfacein the controller during run time. If you need to modify any ACLs, then you must diable all WLANsthat are in the controller or disable both the 802.11a and 80.11b networks. Also, ensure that there areno clients associated and mapped to that interface and then you can modify the ACL settings.Restrictions for Cisco Workgroup Bridges•The WGB can associate only with lightweight access points.•Only WGBs in client mode (which is the default value) are supported. Those WGBs in infrastructuremode are not supported. Perform one of the following to enable client mode on the WGB:◦On the WGB access point GUI, choose Disabled for the Reliable Multicast to WGB parameter.◦On the WGB access point CLI, enter the no infrastructure client command.VLANs are not supported for use with WGBs.NoteSee the sample WGB access point configuration in the WGB Configuration Examplesection.Note•The following features are not supported for use with a WGB:◦Cisco Centralized Key Management (CCKM)◦Idle timeout◦Web authenticationIf a WGB associates to a web-authentication WLAN, the WGB is added to the exclusionlist, and all of the WGB wired clients are deleted.Note•The WGB supports a maximum of 20 wired clients. If you have more than 20 wired clients, use a bridgeor another device.Cisco Wireless LAN Controller Configuration Guide, Release 7.4       OL-28744-01 753Restrictions for Cisco Workgroup Bridges
•The DirectStream feature from the controller does not work for clients behind workgroup bridges andthe stream is denied.•With Layer 3 roaming, if you plug a wired client into the WGB network after the WGB has roamed toanother controller (for example, to a foreign controller), the wired client’s IP address displays only onthe anchor controller, not on the foreign controller.•If a wired client does not send traffic for an extended period of time, the WGB removes the client fromits bridge table, even if traffic is continuously being sent to the wired client. As a result, the traffic flowto the wired client fails. To avoid the traffic loss, prevent the wired client from being removed from thebridge table by configuring the aging-out timer on the WGB to a large value using the following CiscoIOS commands on the WGB:configure terminalbridge bridge-group-number aging-time secondsexitendwhere bridge-group-number is a value between 1 and 255, and seconds is a value between 10 and1,000,000 seconds. We recommend configuring the seconds parameter to a value greater than the wiredclient’s idle period.•When you delete a WGB record from the controller, all of the WGB wired clients’records are alsodeleted.•These features are not supported for wired clients connected to a WGB:◦MAC filtering◦Link tests◦Idle timeout•The broadcast forwarding toward wired WGB clients works only on the native VLAN. If additionalVLANs are configured, only the native VLAN forwards broadcast traffic.•Wired clients behind a WGB cannot connect to a DMZ/Anchor controller. To enable wired clients behinda WGB to connect to an anchor controller in a DMZ, you must enable VLANs in the WGB using theconfig wgb vlan enable command.•The dot11 arp-cache global configuration command that you can enter on the access point that is inWGB mode is not supported.WGB Configuration ExampleThe following is an example of the configuration of a WGB access point using static WEP with a 40-bit WEPkey:ap# configure terminalEnter configuration commands, one per line. End with CNTL/Z.ap(config)# dot11 ssid WGB_with_static_WEPap(config-ssid)# authentication openap(config-ssid)# guest-modeap(config-ssid)# exitap(config)# interface dot11Radio 0ap(config)# station-role workgroup-bridgeap(config-if)# encry mode wep 40ap(config-if)# encry key 1 size 40 0 1234567890   Cisco Wireless LAN Controller Configuration Guide, Release 7.4754 OL-28744-01  WGB Configuration Example
ap(config-if)# ssid WGB_with_static_WEPap(config-if)# endVerify that the WGB is associated to an access point by entering this command on the WGB:show dot11 associationInformation similar to the following appears:ap# show dot11 associations802.11 Client Stations on Dot11Radio0:SSID [FCVTESTING] :MAC Address IP address Device Name Parent State000b.8581.6aee 10.11.12.1 WGB-client map1 - Assocap#Viewing the Status of Workgroup Bridges (GUI)Step 1 Choose Monitor >Clients to open the Clients page.The WGB text box on the right side of the page indicates whether any of the clients on your network are workgroupbridges.Step 2 Click the MAC address of the desired client. The Clients > Detail page appears.The Client Type text box under Client Properties shows “WGB”if this client is a workgroup bridge, and the Number ofWired Client(s) text box shows the number of wired clients that are connected to this WGB.Step 3 See the details of any wired clients that are connected to a particular WGB as follows:a) Click Back on the Clients > Detail page to return to the Clients page.b) Hover your cursor over the blue drop-down arrow for the desired WGB and choose Show Wired Clients. The WGBWired Clients page appears.If you want to disable or remove a particular client, hover your cursor over the blue drop-down arrow forthe desired client and choose Remove or Disable, respectively.Notec) Click the MAC address of the desired client to see more details for this particular client. The Clients > Detail pageappears.The Client Type text box under Client Properties shows “WGB Client,”and the rest of the text boxes on this pageprovide additional information for this client.Viewing the Status of Workgroup Bridges (CLI)Step 1 See any WGBs on your network by entering this command:show wgb summaryStep 2 See the details of any wired clients that are connected to a particular WGB by entering this command:show wgb detail wgb_mac_addressCisco Wireless LAN Controller Configuration Guide, Release 7.4       OL-28744-01 755Viewing the Status of Workgroup Bridges (GUI)
Debugging WGB Issues (CLI)Before You Begin•Enable debugging for IAPP messages, errors, and packets by entering these commands:◦debug iapp all enable—Enables debugging for IAPP messages.◦debug iapp error enable—Enables debugging for IAPP error events.◦debug iapp packet enable—Enables debugging for IAPP packets.•Debug an roaming issue by entering this command:debug mobility handoff enable•Debug an IP assignment issue when DHCP is used by entering these commands:◦debug dhcp message enable◦debug dhcp packet enable•Debug an IP assignment issue when static IP is used by entering these commands:◦debug dot11 mobile enable◦debug dot11 state enable   Cisco Wireless LAN Controller Configuration Guide, Release 7.4756 OL-28744-01  Debugging WGB Issues (CLI)
CHAPTER 111Using Non-Cisco Workgroup Bridges•Information About Non-Cisco Workgroup Bridges, page 757•Restrictions for Non-Cisco Workgroup Bridges, page 758Information About Non-Cisco Workgroup BridgesWhen a Cisco workgroup bridge (WGB) is used, the WGB informs the access points of all the clients that itis associated with. The controller is aware of the clients associated with the access point. When non-CiscoWGBs are used, the controller has no information about the IP address of the clients on the wired segmentbehind the WGB. Without this information, the controller drops the following types of messages:•ARP REQ from the distribution system for the WGB client•ARP RPLY from the WGB client•DHCP REQ from the WGB client•DHCP RPLY for the WGB clientThe following are some guidelines for Non-Cisco workgroup bridges:•The controller can accommodate non-Cisco WGBs so that the controller can forward ARP, DHCP, anddata traffic to and from the wired clients behind workgroup bridges by enabling the passive client feature.To configure your controller to work with non-Cisco WGBs, you must enable the passive client featureso that all traffic from the wired clients is routed through the WGB to the access point. All traffic fromthe wired clients is routed through the work group bridge to the access point.•When a WGB wired client leaves a multicast group, the downstream multicast traffic to other WGBwired clients is interrupted briefly.•If you have clients that use PC virtualization software like VMware, you must enable this feature.We have tested multiple third-party devices for compatibility but cannot ensure that allnon-Cisco devices work. Support for any interaction or configuration details on thethird-party device should be discussed with the device manufacturer.NoteCisco Wireless LAN Controller Configuration Guide, Release 7.4        OL-28744-01 757
•You must enable the passive client functionality for all non-Cisco workgroup bridges.•You might need to use the following commands to configure DHCP on clients:◦Disable DHCP proxy by using the config dhcp proxy disable command.◦Enable DHCP boot broadcast by using the tconfig dhcp proxy disable bootp-broadcast enablecommand.Restrictions for Non-Cisco Workgroup Bridges•Only Layer 2 roaming is supported for WGB devices.•Layer 3 security (web authentication) is not support for WGB clients.•Visibility of wired hosts behind a WGB on a controller is not supported because the non-Cisco WGBdevice performs MAC hiding. Cisco WGB supports IAPP.•ARP poisoning detection does not work on a WLAN when the flag is enabled.•VLAN select is not supported for WGB clients.•Some third-party WGBs need to operate in non-DHCP relay mode. If problems occur with the DHCPassignment on devices behind the non-Cisco WGB, use the config dhcp proxy disable and config dhcpproxy disable bootp-broadcast disable commands.The default state is DHCP proxy enabled. The best combination depends on the third-party characteristicsand configuration.   Cisco Wireless LAN Controller Configuration Guide, Release 7.4758 OL-28744-01  Restrictions for Non-Cisco Workgroup Bridges
CHAPTER 112Configuring Backup Controllers•Information About Configuring Backup Controllers, page 759•Restrictions for Configuring Backup Controllers, page 760•Configuring Backup Controllers (GUI), page 760•Configuring Backup Controllers (CLI), page 761Information About Configuring Backup ControllersA single controller at a centralized location can act as a backup for access points when they lose connectivitywith the primary controller in the local region. Centralized and regional controllers do not need to be in thesame mobility group. You can specify a primary, secondary, and tertiary controller for specific access pointsin your network. Using the controller GUI or CLI, you can specify the IP addresses of the backup controllers,which allows the access points to fail over to controllers outside of the mobility group.The following are some guidelines for configuring backup controllers:•You can configure primary and secondary backup controllers (which are used if primary, secondary, ortertiary controllers are not specified or are not responsive) for all access points connected to the controlleras well as various timers, including heartbeat timers and discovery request timers. To reduce the controllerfailure detection time, you can configure the fast heartbeat interval (between the controller and the accesspoint) with a smaller timeout value. When the fast heartbeat timer expires (at every heartbeat interval),the access point determines if any data packets have been received from the controller within the lastinterval. If no packets have been received, the access point sends a fast echo request to the controller.•The access point maintains a list of backup controllers and periodically sends primary discovery requeststo each entry on the list. When the access point receives a new discovery response from a controller, thebackup controller list is updated. Any controller that fails to respond to two consecutive primary discoveryrequests is removed from the list. If the access point’s local controller fails, it chooses an availablecontroller from the backup controller list in this order: primary, secondary, tertiary, primary backup,and secondary backup. The access point waits for a discovery response from the first available controllerin the backup list and joins the controller if it receives a response within the time configured for theprimary discovery request timer. If the time limit is reached, the access point assumes that the controllercannot be joined and waits for a discovery response from the next available controller in the list.•When an access point's primary controller comes back online, the access point disassociates from thebackup controller and reconnects to its primary controller. The access point falls back only to its primaryCisco Wireless LAN Controller Configuration Guide, Release 7.4        OL-28744-01 759
controller and not to any available secondary controller for which it is configured. For example, if anaccess point is configured with primary, secondary, and tertiary controllers, it fails over to the tertiarycontroller when the primary and secondary controllers become unresponsive. If the secondary controllercomes back online while the primary controller is down, the access point does not fall back to thesecondary controller and stays connected to the tertiary controller. The access point waits until theprimary controller comes back online to fall back from the tertiary controller to the primary controller.If the tertiary controller fails and the primary controller is still down, the access point then falls back tothe available secondary controller.Restrictions for Configuring Backup Controllers•You can configure the fast heartbeat timer only for access points in local and FlexConnect modes.Configuring Backup Controllers (GUI)Step 1 Choose Wireless >Access Points >Global Configuration to open the Global Configuration page.Step 2 From the Local Mode AP Fast Heartbeat Timer State drop-down list, choose Enable to enable the fast heartbeat timerfor access points in local mode or choose Disable to disable this timer. The default value is Disable.Step 3 If you chose Enable in Step 2, enter the Local Mode AP Fast Heartbeat Timeout text box to configure the fast heartbeattimer for access points in local mode. Specifying a small heartbeat interval reduces the amount of time it takes to detecta controller failure.The range for the AP Fast Heartbeat Timeout value for Cisco Flex 7500 Controllers is 10–15 (inclusive) and is 1–10(inclusive) for other controllers. The default value for the heartbeat timeout for Cisco Flex 7500 Controllers is 10. Thedefault value for other controllers is 1 second.Step 4 .From the FlexConnect Mode AP Fast Heartbeat Timer State drop-down list, choose Enable to enable the fast heartbeattimer for FlexConnect access points or choose Disable to disable this timer. The default value is Disable.Step 5 If you enable FlexConnect fast heartbeat, enter the FlexConnect Mode AP Fast Heartbeat Timeout value in the FlexConnectMode AP Fast Heartbeat Timeout text box. Specifying a small heartbeat interval reduces the amount of time it takes todetect a controller failure.The range for the FlexConnect Mode AP Fast Heartbeat Timeout value for Cisco Flex 7500 Controllers is 10–15 (inclusive)and is 1–10 for other controllers. The default value for the heartbeat timeout for Cisco Flex 7500 Controllers is 10. Thedefault value for other controllers is 1 second.Step 6 In the AP Primary Discovery Timeout text box, a value between 30 and 3600 seconds (inclusive) to configure the accesspoint primary discovery request timer. The default value is 120 seconds.Step 7 If you want to specify a primary backup controller for all access points, enter the IP address of the primary backupcontroller in the Back-up Primary Controller IP Address text box and the name of the controller in the Back-up PrimaryController Name text box.The default value for the IP address is 0.0.0.0, which disables the primary backup controller.NoteStep 8 If you want to specify a secondary backup controller for all access points, enter the IP address of the secondary backupcontroller in the Back-up Secondary Controller IP Address text box and the name of the controller in the Back-upSecondary Controller Name text box.The default value for the IP address is 0.0.0.0, which disables the secondary backup controller.Note   Cisco Wireless LAN Controller Configuration Guide, Release 7.4760 OL-28744-01  Restrictions for Configuring Backup Controllers
Step 9 Click Apply to commit your changes.Step 10 Configure primary, secondary, and tertiary backup controllers for a specific access point as follows:a) Choose Access Points >All APs to open the All APs page.b) Click the name of the access point for which you want to configure primary, secondary, and tertiary backup controllers.c) Choose the High Availability tab to open the All APs > Details for (High Availability) page.d) If desired, enter the name and IP address of the primary controller for this access point in the Primary Controller textboxes.Entering an IP address for the backup controller is optional in this step and the next two steps. If the backupcontroller is outside the mobility group to which the access point is connected (the primary controller), thenyou need to provide the IP address of the primary, secondary, or tertiary controller, respectively. The controllername and IP address must belong to the same primary, secondary, or tertiary controller. Otherwise, theaccess point cannot join the backup controller.Notee) If desired, enter the name and IP address of the secondary controller for this access point in the Secondary Controllertext boxes.f) If desired, enter the name and IP address of the tertiary controller for this access point in the Tertiary Controller textboxes.g) Click Apply to commit your changes.Step 11 Click Save Configuration to save your changes.Configuring Backup Controllers (CLI)Step 1 Configure a primary controller for a specific access point by entering this command:config ap primary-base controller_name Cisco_AP [controller_ip_address]The controller_ip_address parameter in this command and the next two commands is optional. If the backupcontroller is outside the mobility group to which the access point is connected (the primary controller), thenyou need to provide the IP address of the primary, secondary, or tertiary controller, respectively. In eachcommand, the controller_name and controller_ip_address must belong to the same primary, secondary, ortertiary controller. Otherwise, the access point cannot join the backup controller.NoteStep 2 Configure a secondary controller for a specific access point by entering this command:config ap secondary-base controller_name Cisco_AP [controller_ip_address]Step 3 Configure a tertiary controller for a specific access point by entering this command:config ap tertiary-base controller_name Cisco_AP [controller_ip_address]Step 4 Configure a primary backup controller for all access points by entering this command:config advanced backup-controller primary backup_controller_name backup_controller_ip_addressStep 5 Configure a secondary backup controller for all access points by entering this command:config advanced backup-controller secondary backup_controller_name backup_controller_ip_addressTo delete a primary or secondary backup controller entry, enter 0.0.0.0 for the controller IP address.NoteStep 6 Enable or disable the fast heartbeat timer for local or FlexConnect access points by entering this command:config advanced timers ap-fast-heartbeat {local |flexconnect |all} {enable | disable}intervalCisco Wireless LAN Controller Configuration Guide, Release 7.4       OL-28744-01 761Configuring Backup Controllers (CLI)
where all is both local and FlexConnect access points, and interval is a value between 1 and 10 seconds (inclusive).Specifying a small heartbeat interval reduces the amount of time that it takes to detect a controller failure. The defaultvalue is disabled.Configure the access point heartbeat timer by entering this command:config advanced timers ap-heartbeat-timeout intervalwhere interval is a value between 1 and 30 seconds (inclusive). This value should be at least three times larger than thefast heartbeat timer. The default value is 30 seconds.Do not enable the fast heartbeat timer with the high latency link. If you have to enable the fast heartbeat timer,the timer value must be greater than the latency.CautionStep 7 Configure the access point primary discovery request timer by entering this command:config advanced timers ap-primary-discovery-timeout intervalwhere interval is a value between 30 and 3600 seconds. The default value is 120 seconds.Step 8 Configure the access point discovery timer by entering this command:config advanced timers ap-discovery-timeout intervalwhere interval is a value between 1 and 10 seconds (inclusive). The default value is 10 seconds.Step 9 Configure the 802.11 authentication response timer by entering this command:config advanced timers auth-timeout intervalwhere interval is a value between 10 and 600 seconds (inclusive). The default value is 10 seconds.Step 10 Save your changes by entering this command:save configStep 11 See an access point’s configuration by entering these commands:•show ap config general Cisco_AP•show advanced backup-controller•show advanced timersInformation similar to the following appears for the show ap config general Cisco_AP command:Cisco AP Identifier.............................. 1Cisco AP Name.................................... AP5Country code..................................... US - United StatesRegulatory Domain allowed by Country............. 802.11bg:-AB 802.11a:-ABAP Country code.................................. US - United StatesAP Regulatory Domain............................. 802.11bg:-A 802.11a:-NSwitch Port Number .............................. 1MAC Address...................................... 00:13:80:60:48:3eIP Address Configuration......................... DHCPIP Address....................................... 1.100.163.133...Primary Cisco Switch Name........................ 1-5508Primary Cisco Switch IP Address.................. 2.2.2.2Secondary Cisco Switch Name...................... 1-4404Secondary Cisco Switch IP Address................ 2.2.2.2Tertiary Cisco Switch Name....................... 2-4404Tertiary Cisco Switch IP Address................. 1.1.1.4   Cisco Wireless LAN Controller Configuration Guide, Release 7.4762 OL-28744-01  Configuring Backup Controllers (CLI)
...Information similar to the following appears for the show advanced backup-controller command:AP primary Backup Controller .................... controller1 10.10.10.10AP secondary Backup Controller ............... 0.0.0.0Information similar to the following appears for the show advanced timers command:Authentication Response Timeout (seconds)........ 10Rogue Entry Timeout (seconds).................... 1300AP Heart Beat Timeout (seconds).................. 30AP Discovery Timeout (seconds)................... 10AP Local mode Fast Heartbeat (seconds)........... 10 (enable)AP flexconnect mode Fast Heartbeat (seconds)........... disableAP Primary Discovery Timeout (seconds)........... 120Cisco Wireless LAN Controller Configuration Guide, Release 7.4       OL-28744-01 763Configuring Backup Controllers (CLI)
   Cisco Wireless LAN Controller Configuration Guide, Release 7.4764 OL-28744-01  Configuring Backup Controllers (CLI)
CHAPTER 113Configuring High Availability•Information About High Availability, page 765•Restrictions for High Availability, page 767•Configuring High Availability (GUI), page 769•Configuring High Availability (CLI), page 770Information About High AvailabilityHigh availability (HA) in controllers allows you to reduce the downtime of the wireless networks that occursdue to the failover of controllers.A 1:1 (Active:Standby-Hot) stateful switchover of access points (AP SSO) is supported. In an HA architecture,one controller is configured as the primary controller and another controller as the secondary controller.After you enable HA, the primary and secondary controllers are rebooted. During the boot process, the roleof the primary controller is negotiated as active and the role of the secondary controller as standby-hot. Aftera switchover, the secondary controller becomes the active controller and the primary controller becomes thestandby-hot controller. After subsequent switchovers, the roles are interchanged between the primary and thesecondary controllers. The reason for switchovers are either because of manual trigger or a controller ornetwork failure.During an AP SSO, all the AP sessions statefully switch over and all the clients are deauthenticated andreassociated with the new active controller except for the locally switched clients in the FlexConnect mode.The standby-hot controller continuously monitors the health of the active controller through a direct wiredconnection over a dedicated redundancy port. Both the controllers share the same configurations, includingthe IP address of the management interface.Before you enable HA, ensure that both the controllers are physically connected through the redundant portusing an Ethernet cable. Also, ensure that the uplink is connected to an infrastructure switch and that thegateway is reachable from both the controllers.In HA architecture, the redundancy port and redundant management interfaces have been newly introduced.The following are some guidelines for high availability:•We recommend that you do not pair two controllers of different hardware models. If they are paired,then a higher controller model becomes the active controller and the other controller goes into maintenancemode.Cisco Wireless LAN Controller Configuration Guide, Release 7.4        OL-28744-01 765
•We recommend that you do not pair two controllers on different controller software releases. If they arepaired, then the controller with the lower redundancy management address becomes the active controllerand the other controller goes into maintenance mode.•All download file types, such as Image, Config, Web-Authentication bundle, and Signature files, aredownloaded on the active controller first and then pushed to the standby-hot controller.•Certificates should be downloaded separately on each controller before they are paired.•You can upload file types such as Config, Event Logs, Crash files, and so on, from the standby-hotcontroller using the GUI or CLI of the active controller. You can also specify a suffix to the filenameto identify the uploaded file.•To perform a peer upload, use the service port. In a management network, you can also use the redundancymanagement interface (RMI) that is mapped to the redundancy port or RMI VLAN, or both, that is thesame as the management VLAN.•If the controllers cannot reach each other through the redundant port or the RMI, the primary controllerbecomes active and the standby-hot controller goes into the maintenance mode.To achieve HA between two Cisco WiSM2 platforms, the controllers should be deployedon a single chassis or on multiple chassis using a virtual switching system (VSS) andextending a redundancy VLAN between the multiple chassis.NoteA redundancy VLAN should be a nonroutable VLAN in which a Layer 3 interfaceshould not be created for the VLAN and the interface should be allowed on the trunkport to extend an HA setup between multiple chassis. Redundancy VLAN should becreated like any other data VLAN on Cisco IOS-based switching software. A redundancyVLAN is connected to the redundant port on Cisco WiSM2 through the backplane. Itis not necessary to configure the IP address for the redundancy VLAN because the IPaddress is automatically generated. Also, ensure that the redundancy VLAN is not thesame as the management VLAN.Note•When HA is enabled, ensure that you do not use the backed-up image. If this image is used, the HAfeature might not work as expected:•The service port and route information that is configured is lost after you enable SSO. You mustconfigure the service port and route information again after you enable SSO. You can configurethe service port and route information for the standby-hot controller using the peer-service-portand peer-route commands.•For Cisco WiSM2, service port reconfigurations are required after you enable redundancy.Otherwise, Cisco WiSM2 might not be able to communicate with the supervisor. We recommendthat you enable DHCP on the service port before you enable redundancy.•We recommend that you do not use the reset command on the standby-hot controller directly. Ifyou use this, unsaved configurations will be lost.•We recommend that you enable link aggregation (LAG) configuration on the controllers before youenable the port channel in the infrastructure switches.   Cisco Wireless LAN Controller Configuration Guide, Release 7.4766 OL-28744-01  Information About High Availability
•All configurations that require reboot of the active controller results in the reboot of the standby-hotcontroller.•The Ignore AP list is not synchronized from the active controller to the standby-hot controller. The listis relearned through SNMP messages from the Cisco Prime Infrastructure, after the standby-hot controllerbecomes active.•In Release 7.3.x, AP SSO is supported but client SSO is not supported, which means that after an HAsetup that uses Release 7.3.x encounters a switchover, all the clients associated with the Cisco WLC aredeauthenticated and are forced to reassociate.•You must manually configure the mobility MAC address on the then active controller post switchover,when a peer controller has a controller software release that is prior to Release 7.2.Redundancy Management InterfaceThe active and standby-hot controllers use the Redundancy Management Interface to check the health of thepeer controller and the default gateway of the management interface through the network infrastructure.The Redundancy Management Interface is also used to send notifications from the active controller to thestandby-hot controller if a failure or manual reset occurs. The standby-hot controller uses the RedundancyManagement Interface to communicate to the syslog, NTP server, FTP, and TFTP server.It is mandatory to configure the IP addresses of the Redundancy Management Interface and the ManagementInterface in the same subnet on both the primary and secondary controllers.Redundancy PortThe redundancy port is used for configuration, operational data synchronization, and role negotiation betweenthe primary and secondary controllers.The redundancy port checks for peer reachability by sending UDP keepalive messages every 100 milliseconds(default frequency) from the standby-hot controller to the active controller. If a failure of the active controlleroccurs, the redundancy port is used to notify the standby-hot controller.If an NTP server is not configured, the redundancy port performs a time synchronization from the activecontroller to the standby-hot controller.In Cisco WiSM2, the redundancy VLAN must be configured on the Cisco Catalyst 6000 supervisor enginebecause there is no physical redundancy port is available on Cisco WiSM2.The redundancy port and the redundancy VLAN in Cisco WiSM2 are assigned an automatically generatedIP address in which the last two octets are obtained from the last two octets of the Redundancy ManagementInterface. The first two octets are always 169.254. For example, if the IP address of the RedundancyManagement Interface is 209.165.200.225, the IP address of the redundancy port is 169.254.200.225.Restrictions for High Availability•When you configure the controller for HA SSO, the Cisco 600 Series OfficeExtend Access Points arenot supported.•In an HA environment using FlexConnect locally switched clients, the client information might not showthe username. To get details about the client, you must use the MAC address of the client. This restrictiondoes not apply to FlexConnect centrally switched clients or central (local) mode clients.Cisco Wireless LAN Controller Configuration Guide, Release 7.4       OL-28744-01 767Restrictions for High Availability
•It is not possible to access the Cisco WiSM2 GUI through the service interface when you have enabledHA. The workaround is to create a service port interface again after HA is established.•In an HA environment, an upgrade from an LDPE image to a non-LDPE image is not supported.•It is not possible to pair two primary controllers or two secondary controllers.•Standby controllers are unavailable on the APs connected switch port•An HA-SKU controller with an evaluation license cannot become a standby controller. However, anHA-SKU controller with zero license can become a standby controller.•The following scenario is not supported: The primary controller has the management address and theredundancy management address in the same VLAN, and the secondary controller has the managementaddress in the same VLAN as the primary one, and the redundancy management address in a differentVLAN.•The following is a list of some software upgrade scenarios:•A software upgrade on the active controller ensures the upgrade of the standby-hot controller.•An in-service upgrade is not supported. Therefore, you should plan your network downtime beforeyou upgrade the controllers in an HA environment.•Rebooting the active controller after a software upgrade also reboots the standby-hot controller.•If both active and standby-hot controllers have different software releases in the backup, and ifyou enter the config boot backup command in the active controller, both the controllers rebootwith their respective backup images breaking the HA pair due to a software mismatch.•A schedule reset applies to both the controllers in an HA environment. The peer controller rebootsa minute before the scheduled time expires on the active controller.•You can reboot the standby-hot controller from the active controller by entering the resetpeer-system command if the scheduled reset is not planned. If you reset only the standby-hotcontroller with this command, any unsaved configurations on the standby-hot controller is lost.Therefore, ensure that you save the configurations on the active controller before you reset thestandby-hot controller.•A preimage download is reinitiated if an SSO is triggered at the time of the image transfer.•Only debug and show commands are allowed on the standby-hot controller.•It is not possible to access the standby-hot controller through the controller GUI, Cisco PrimeInfrastructure, or Telnet. You can access the standby-hot controller only on its console.•To enable or disable LAG, you must disable HA.If LAG is disabled and both primary and backup ports are connected to the managementinterface and if the primary port becomes nonoperational, a switchover might occurbecause the default gateway is not reachable and backup port failover might exceed 12seconds.Note•When a failover occurs and the standby controller becomes the new active controller, it takesapproximately 15 to 20 minutes to synchronize the database (AP, client, and multicast) between the twocontrollers. If another failover occurs during this time, the HA structures would not yet be synchronized.Therefore, the APs and clients would have to get reassociated and reauthenticated respectively.   Cisco Wireless LAN Controller Configuration Guide, Release 7.4768 OL-28744-01  Restrictions for High Availability
•Pairwise Master Key (PMK) cache synchronization is not supported on FlexConnect local-authenticatedclients.•You cannot change the NAT address configuration of the management interface when the controllersare in redundancy mode. To enable NAT address configuration on the management interface, you mustremove the redundancy configuration first, make the required changes on the primary controller, andthen reenable the redundancy configuration on the same controller.Configuring High Availability (GUI)Before You BeginEnsure that the management interfaces of both controllers are in the same subnet. You can verify this on theGUI of both the controllers by choosing Controllers > Interfaces and viewing the IP addresses of themanagement interface.Step 1 On the GUI of both controllers, choose Controller > Redundancy > Global Configuration.The Global Configuration page is displayed.Step 2 Enter the addresses of both the controllers in the Redundant Management IP and the Peer Redundant ManagementIP text boxes.Ensure that the Redundant Management Interface IP address of one controller is the same as the Redundancy ManagementInterface IP address of the peer controller.Step 3 From the Redundant Unit drop-down list, choose one of the controllers as primary and the other as secondary.Step 4 On the GUI of both the controllers, set the SSO to Enabled state.After you enable an SSO, the service port peer IP address and the service port netmask appear on the configuration page.Note that the service port peer IP address and the netmask can be pushed to the peer only if the HA peer is available andoperational. When you enable HA, you do not have to configure the service port peer IP address and the service portnetmask parameters. You must configure the parameters only when the HA peer is available and operational. After youenable SSO, both the controllers are rebooted. During the reboot process, the controllers negotiate the redundancy rolethrough the redundant port based on the configuration. The primary controller becomes the active controller and thesecondary controller becomes the standby controller.Step 5 (Optional) When the HA pair becomes available and operational, you can configure the peer service port IP address andthe netmask when the service port is configured as static. If you enable DHCP on the service port, you do not have toconfigure these parameters on the Global Configuration page:•Service Port Peer IP—IP address of the service port of the peer controller.•Service Port Peer Netmask—Netmask of the service port of the peer controller.•Mobility MAC Address—A common MAC address for the active and standby controllers that is used in themobility protocol. If an HA pair has to be added as a mobility member for a mobility group, the mobility MACaddress (instead of the system MAC address of the active or standby controller) should be used. Normally, themobility MAC address is chosen as the MAC address of the active controller and you do not have to manuallyconfigure this.•Keep Alive Timer—The timer that controls how often the standby controller sends heartbeat keepalive messagesto the active controller. The valid range is between 100 to 400 milliseconds, in multiples of 50.Cisco Wireless LAN Controller Configuration Guide, Release 7.4       OL-28744-01 769Configuring High Availability (GUI)
•Peer Search Timer—The timer that controls how often the active controller sends peer search messages to thestandby controller. The valid range is between 60 to 180 seconds.After you enable the HA and pair the controllers, there is only one unified GUI to manage the HA pair through themanagement port. GUI access through the service port is not feasible for both the active and standby controllers. Thestandby controller can be managed only through the console or the service port.Only Telnet and SSH sessions are allowed through the service port of the active and standby controllers.Step 6 Click Apply.Step 7 Click Save Configuration.Step 8 View the redundancy status of the HA pair by choosing Monitor > Redundancy > Summary.The Redundancy Summary page is displayed.Step 9 Follow these steps to configure the peer network route:a) Choose Controller >Redundancy >Peer Network Route.The Network Routes Peer page is displayed.This page provides a summary of the existing service port network routes of the peer controller to network or elementmanagement systems on a different subnet. You can view the IP address, IP netmask, or gateway IP address.b) To create a new peer network route, click New.c) Enter the IP address, IP netmask, and the Gateway IP address of the route.d) Click Apply.Configuring High Availability (CLI)Before You BeginEnsure that the management interfaces of both controllers are in the same subnet.•Configure a local redundancy IP address and a peer redundancy management IP address by enteringthis command:config interface address redundancy-management ip-addr1 peer-redundancy-management ip-addr2•Configure the role of a controller by entering this command:config redundancy unit {primary |secondary}•Configure redundancy by entering this command:config redundancy mode {sso {ap |client} | disable}You can choose between an AP SSO and a client SSO.•Configure the route configurations of the standby controller by entering this command:config redundancy peer-route {add network-ip-addr ip-mask |delete network-ip-addr}This command can be run only if the HA peer controller is available and operational.•Configure a mobility MAC address by entering this command:config redundancy mobilitymac mac-addrThis command can be run only when SSO is disabled.   Cisco Wireless LAN Controller Configuration Guide, Release 7.4770 OL-28744-01  Configuring High Availability (CLI)
•Configure the IP address and netmask of the peer service port of the standby controller by entering thiscommand:config redundancy interface address peer-service-port ip-address netmaskThis command can be run only if the HA peer controller is available and operational.•Initiate a manual switchover by entering this command:config redundancy force-switchoverRun this command only when you require a manual switchover.•Configure the redundancy timers by entering this command:config redundancy timer {keep-alive-timer time-in-milliseconds |peer-search-timer time-in-seconds}•View the status of redundancy by entering this command:show redundancy summary•View information about the Redundancy Management Interface by entering this command:show interface detailed redundancy-management•View information about the redundancy port by entering this command:show interface detailed redundancy-port•Reboot a peer controller by entering this command:reset peer-system•Start the upload of file types, such as Config, Event Logs, Crash files, and so on from the standby-hotcontroller by entering this command on the active controller:transfer upload peer-start•Debug the commands for the Redundancy Manager by entering this command:debug rmgr {packet |events |errors |detail}•Debug the commands for the Redundancy Sync Manager by entering this command:debug rsnyncmgr {packet |events |errors |detail}•Debug the commands for the Redundancy Facilitator by entering this command:debug rfrac {packet |events |errors |detail}Cisco Wireless LAN Controller Configuration Guide, Release 7.4       OL-28744-01 771Configuring High Availability (CLI)
   Cisco Wireless LAN Controller Configuration Guide, Release 7.4772 OL-28744-01  Configuring High Availability (CLI)
CHAPTER 114Configuring Failover Priority for Access Points•Information About Configuring Failover Priority for Access Points, page 773•Configuring Failover Priority for Access Points (GUI), page 774•Configuring Failover Priority for Access Points (CLI), page 774•Viewing Failover Priority Settings (CLI), page 774Information About Configuring Failover Priority for Access PointsEach controller has a defined number of communication ports for access points. When multiple controllerswith unused access point ports are deployed on the same network and one controller fails, the dropped accesspoints automatically poll for unused controller ports and associate with them.The following are some guidelines for configuring failover priority for access points:•You can configure your wireless network so that the backup controller recognizes a join request froma higher-priority access point and if necessary disassociates a lower-priority access point as a means toprovide an available port.•Failover priority is not in effect during the regular operation of your wireless network. It takes effectonly if there are more association requests after a controller failure than there are available backupcontroller ports.•To configure this feature, you must enable failover priority on your network and assign priorities to theindividual access points.•By default, all access points are set to priority level 1, which is the lowest priority level. Therefore, youneed to assign a priority level only to those access points that warrant a higher priority.Cisco Wireless LAN Controller Configuration Guide, Release 7.4        OL-28744-01 773
Configuring Failover Priority for Access Points (GUI)Step 1 Choose Wireless > Access Points > Global Configuration to open the Global Configuration page.Step 2 From the Global AP Failover Priority drop-down list, choose Enable to enable access point failover priority or chooseDisable to disable this feature and turn off any access point priority assignments. The default value is Disable.Step 3 Click Apply to commit your changes.Step 4 Click Save Configuration to save your changes.Step 5 Choose Wireless >Access Points >All APs to open the All APs page.Step 6 Click the name of the access point for which you want to configure failover priority.Step 7 Choose the High Availability tab. The All APs > Details for (High Availability) page appears.Step 8 From the AP Failover Priority drop-down list, choose one of the following options to specify the priority of the accesspoint:•Low—Assigns the access point to the level 1 priority, which is the lowest priority level. This is the default value.•Medium—Assigns the access point to the level 2 priority.•High—Assigns the access point to the level 3 priority.•Critical—Assigns the access point to the level 4 priority, which is the highest priority level.Step 9 Click Apply to commit your changes.Step 10 Click Save Configuration to save your changes.Configuring Failover Priority for Access Points (CLI)Step 1 Enable or disable access point failover priority by entering this command:config network ap-priority {enable |disable}Step 2 Specify the priority of an access point by entering this command:config ap priority {1|2|3|4}Cisco_APwhere 1 is the lowest priority level and 4 is the highest priority level. The default value is 1.Step 3 Enter the save config command to save your changes.Viewing Failover Priority Settings (CLI)•Confirm whether access point failover priority is enabled on your network by entering this command:   Cisco Wireless LAN Controller Configuration Guide, Release 7.4774 OL-28744-01  Configuring Failover Priority for Access Points (GUI)
show network summaryInformation similar to the following appears:RF-Network Name............................. mrfWeb Mode.................................... EnableSecure Web Mode............................. EnableSecure Web Mode Cipher-Option High.......... DisableSecure Shell (ssh).......................... EnableTelnet...................................... EnableEthernet Multicast Mode..................... DisableEthernet Broadcast Mode..................... DisableIGMP snooping............................... DisabledIGMP timeout................................ 60 secondsUser Idle Timeout........................... 300 secondsARP Idle Timeout............................ 300 secondsCisco AP Default Master..................... DisableAP Join Priority......................... Enabled...•See the failover priority for each access point by entering this command:show ap summaryInformation similar to the following appears:Number of APs.................................... 2Global AP User Name.............................. userGlobal AP Dot1x User Name........................ Not ConfiguredAP Name Slots AP Model Ethernet MAC Location Port Country Priority------- ----- ------------------ ----------------- --------- ---- ------- -------ap:1252 2 AIR-LAP1252AG-A-K9 00:1b:d5:13:39:74 hallway 6 1 US 1ap:1121 1 AIR-LAP1121G-A-K9 00:1b:d5:a9:ad:08 reception 1 US 3To see the summary of a specific access point, you can specify the access point name. You can also usewildcard searches when filtering for access points.Cisco Wireless LAN Controller Configuration Guide, Release 7.4       OL-28744-01 775Viewing Failover Priority Settings (CLI)
   Cisco Wireless LAN Controller Configuration Guide, Release 7.4776 OL-28744-01  Viewing Failover Priority Settings (CLI)
CHAPTER 115Configuring AP Retransmission Interval and RetryCount•Information About Configuring the AP Retransmission Interval and Retry Count, page 777•Restrictions for Access Point Retransmission Interval and Retry Count, page 777•Configuring the AP Retransmission Interval and Retry Count (GUI), page 778•Configuring the Access Point Retransmission Interval and Retry Count (CLI), page 778Information About Configuring the AP Retransmission Interval and Retry CountThe controller and the APs exchange packets using the CAPWAP reliable transport protocol. For each request,a response is defined. This response is used to acknowledge the receipt of the request message. Responsemessages are not explicitly acknowledged; therefore, if a response message is not received, the original requestmessage is retransmitted after the retransmit interval. If the request is not acknowledged after a maximumnumber of retransmissions, the session is closed and the APs reassociate with another controller.Restrictions for Access Point Retransmission Interval and Retry Count•You can configure the retransmission intervals and retry count both at a global as well as a specificaccess point level. A global configuration applies these configuration parameters to all the access points.That is, the retransmission interval and the retry count are uniform for all access points. Alternatively,when you configure the retransmission level and retry count at a specific access point level, the valuesare applied to that particular access point. The access point specific configuration has a higher precedencethan the global configuration.•Retransmission intervals and the retry count do not apply for mesh access points.Cisco Wireless LAN Controller Configuration Guide, Release 7.4        OL-28744-01 777
Configuring the AP Retransmission Interval and Retry Count (GUI)You can configure the retransmission interval and retry count for all APs globally or a specific AP.Step 1 To configure the controller to set the retransmission interval and retry count globally using the controller GUI, followthese steps:a) Choose Wireless > Access Points > Global Configuration.b) Choose one of the following options under the AP Transmit Config Parameters section:•AP Retransmit Count—Enter the number of times you want the access point to retransmit the request to thecontroller. This parameter can take values between 3 and 8.•AP Retransmit Interval—Enter the time duration between the retransmission of requests. This parameter cantake values between 2 and 5.c) Click Apply.Step 2 To configure the controller to set the retransmission interval and retry count for a specific access point, follow thesesteps:a) Choose Wireless > Access Points > All APs.b) Click on the AP Name link for the access point on which you want to set the values.The All APs > Details page appears.c) Click the Advanced Tab to open the advanced parameters page.d) Choose one of the following parameters under the AP Transmit Config Parameters section:•AP Retransmit Count—Enter the number of times that you want the access point to retransmit the request tothe controller. This parameter can take values between 3 and 8.•AP Retransmit Interval—Enter the time duration between the retransmission of requests. This parameter cantake values between 2 and 5.e) Click Apply.Configuring the Access Point Retransmission Interval and Retry Count (CLI)You can configure the retransmission interval and retry count for all access points globally or a specific accesspoint.•Configure the retransmission interval and retry count for all access points globally by entering the thiscommand:config ap retransmit {interval |count}seconds allThe valid range for the interval parameter is between 3 and 8. The valid range for the count parameteris between 2 and 5.•Configure the retransmission interval and retry count for a specific access point, by entering this command:   Cisco Wireless LAN Controller Configuration Guide, Release 7.4778 OL-28744-01  Configuring the AP Retransmission Interval and Retry Count (GUI)
config ap retransmit {interval |count}seconds Cisco_APThe valid range for the interval parameter is between 3 and 8. The valid range for the count parameteris between 2 and 5.•See the status of the configured retransmit parameters on all or specific APs by entering this command:show ap retransmit allBecause retransmit and retry values cannot be set for access points in mesh mode, thesevalues are displayed as N/A (not applicable).Note•See the status of the configured retransmit parameters on a specific access point by entering this command:show ap retransmit Cisco_APCisco Wireless LAN Controller Configuration Guide, Release 7.4       OL-28744-01 779Configuring the Access Point Retransmission Interval and Retry Count (CLI)
   Cisco Wireless LAN Controller Configuration Guide, Release 7.4780 OL-28744-01  Configuring the Access Point Retransmission Interval and Retry Count (CLI)
CHAPTER 116Configuring Country Codes•Information About Configuring Country Codes, page 781•Restrictions for Configuring Country Codes, page 782•Configuring Country Codes (GUI), page 782•Configuring Country Codes (CLI), page 783Information About Configuring Country CodesControllers and access points are designed for use in many countries with varying regulatory requirements.The radios within the access points are assigned to a specific regulatory domain at the factory (such as -E forEurope), but the country code enables you to specify a particular country of operation (such as FR for Franceor ES for Spain). Configuring a country code ensures that each radio’s broadcast frequency bands, interfaces,channels, and transmit power levels are compliant with country-specific regulations.The following are some guidelines for configuring country codes:•Generally, you configure one country code per controller, the one matching the physical location of thecontroller and its access points. However, you can configure up to 20 country codes per controller. Thismultiple-country support enables you to manage access points in various countries from a single controller.•Although the controller supports different access points in different regulatory domains (countries), itrequires all radios in a single access point to be configured for the same regulatory domain. For example,you should not configure a Cisco 1231 access point’s 802.11b/g radio for the US (-A) regulatory domainand its 802.11a radio for the Great Britain (-E) regulatory domain. Otherwise, the controller allows onlyone of the access point’s radios to turn on, depending on which regulatory domain you selected for theaccess point on the controller. Therefore, make sure that the same country code is configured for bothof the access point’s radios.For a complete list of country codes supported per product, see http://tools.cisco.com/cse/prdapp/jsp/externalsearch.do?action=externalsearch&page=EXTERNAL_SEARCHorhttp://www.cisco.com/en/US/prod/collateral/wireless/ps5679/ps5861/product_data_sheet0900aecd80537b6a_ps6087_Products_Data_Sheet.html•When the multiple-country feature is being used, all controllers that are going to join the same RF groupmust be configured with the same set of countries, configured in the same order.Cisco Wireless LAN Controller Configuration Guide, Release 7.4        OL-28744-01 781
•When multiple countries are configured and the RRM auto-RF feature is enabled, the RRM assigns thechannels that are derived by performing a union of the allowed channels per the AP country code. TheAPs are assigned channels by the RRM based on their PID country code. APs are only allowed to uselegal frequencies that match their PID country code. Ensure that your AP's country code is legal in thecountry that it is deployed.•The country list configured on the RF group leader determines what channels the members would operateon. This list is independent of what countries have been configured on the RF group members.Information About Japanese Country CodesCountry codes define the channels that can be used legally in each country. These country codes are availablefor Japan:•JP—Allows only -J radios to join the controller•J2—Allows only -P radios to join the controller•J3—Uses the -U frequencies but allows -U, -P and -Q (other than 1550/1600/2600/3600) radios to jointhe controller•J4—Allows 2.4G JPQU and 5G PQU to join the controller.The 1550, 1600, 2600, and 3600 APs require J4.NoteSee the Channels and Maximum Power Settings for Cisco Aironet Lightweight Access Points document forthe list of channels and power levels supported by access points in the Japanese regulatory domains.Restrictions for Configuring Country Codes•The access point can only operate on the channels for the countries that they are designed for.If an access point was already set to a higher legal power level or is configured manually,the power level is limited only by the particular country to which that access point isassigned.NoteConfiguring Country Codes (GUI)Step 1 Disable the 802.11 networks as follows:a) Choose Wireless >802.11a/n >Network.b) Unselect the 802.11a Network Status check box.c) Click Apply.d) Choose Wireless >802.11a/n >Network.   Cisco Wireless LAN Controller Configuration Guide, Release 7.4782 OL-28744-01  Restrictions for Configuring Country Codes
e) Unselect the 802.11b/g Network Status check box.f) Click Apply.Step 2 Choose Wireless >Country to open the Country page.Step 3 Select the check box for each country where your access points are installed. If you selected more than one check box,a message appears indicating that RRM channels and power levels are limited to common channels and power levels.Step 4 Click OK to continue or Cancel to cancel the operation.Step 5 Click Apply.If you selected multiple country codes in Step 3, each access point is assigned to a country.Step 6 See the default country chosen for each access point and choose a different country if necessary as follows:If you remove a country code from the configuration, any access points currently assigned to the deleted countryreboot and when they rejoin the controller, they get re-assigned to one of the remaining countries if possible.Notea) Perform one of the following:•Leave the 802.11 networks disabled.•Reenable the 802.11 networks and then disable only the access points for which you are configuring a countrycode. To disable an access point, choose Wireless >Access Points >All APs, click the link of the desiredaccess point, choose Disable from the Status drop-down list, and click Apply.b) Choose Wireless >Access Points >All APs to open the All APs page.c) Click the link for the desired access point.d) Choose the Advanced tab to open the All APs > Details for (Advanced) page.The default country for this access point appears in the Country Code drop-down list.e) If the access point is installed in a country other than the one shown, choose the correct country from the drop-downlist. The box contains only those country codes that are compatible with the regulatory domain of at least one of theaccess point’s radios.f) Click Apply.g) Repeat these steps to assign all access points joined to the controller to a specific country.h) Reenable any access points that you disabled in Step a.Step 7 Reenable the 802.11 networks if you did not enable them in Step 6.Step 8 Click Save Configuration.Configuring Country Codes (CLI)Step 1 See a list of all available country codes by entering this command:show country supportedStep 2 Disable the 802.11 networks by entering these commands:config 802.11a disable networkconfig 802.11b disable networkStep 3 Configure the country codes for the countries where your access points are installed by entering this command:Cisco Wireless LAN Controller Configuration Guide, Release 7.4       OL-28744-01 783Configuring Country Codes (CLI)
config country code1[,code2,code3,...]If you are entering more than one country code, separate each by a comma (for example, config country US,CA,MX).Step 4 Enter Ywhen prompted to confirm your decision.Step 5 Verify your country code configuration by entering this command:show countryStep 6 See the list of available channels for the country codes configured on your controller by entering this command:show country channelsStep 7 Save your changes by entering this command:save configStep 8 See the countries to which your access points have been assigned by entering this command:To see a summary of specific access point you can specify the access point name. You can also use wildcard searcheswhen filtering for access points.show ap summaryStep 9 If you entered multiple country codes in Step 3, follow these steps to assign each access point to a specific country:a) Perform one of the following:•Leave the 802.11 networks disabled.•Reenable the 802.11 networks and then disable only the access points for which you are configuring a countrycode. To Reenable the networks, enter this command:config 802.11{a|b}enable networkTo disable an access point, enter this command:config ap disable ap_nameb) To assign an access point to a specific country, enter this command:config ap country code {ap_name |all}Make sure that the country code you choose is compatible with the regulatory domain of at least one of the accesspoint’s radios.If you enabled the networks and disabled some access points and then run the config ap country code allcommand, the specified country code is configured on only the disabled access points. All other accesspoints are ignored.Notec) To reenable any access points that you disabled in Step a, enter this command:config ap enable ap_nameStep 10 If you did not reenable the 802.11 networks in Step 9, enter these commands to reenable them now:config 802.11{a|b}enable networkStep 11 Save your changes by entering this command:save config   Cisco Wireless LAN Controller Configuration Guide, Release 7.4784 OL-28744-01  Configuring Country Codes (CLI)
CHAPTER 117Optimizing RFID Tracking on Access Points•Information About Optimizing RFID Tracking on Access Points, page 785•Optimizing RFID Tracking on Access Points (GUI), page 785•Optimizing RFID Tracking on Access Points (CLI), page 786Information About Optimizing RFID Tracking on Access PointsTo optimize the monitoring and location calculation of RFID tags, you can enable tracking optimization onup to four channels within the 2.4-GHz band of an 802.11b/g access point radio. This feature allows you toscan only the channels on which tags are usually programmed to operate (such as channels 1, 6, and 11).You can use the controller GUI or CLI to configure the access point for monitor mode and to then enabletracking optimization on the access point radio.Optimizing RFID Tracking on Access Points (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 configure monitor mode. The All APs > Details for pageappears.Step 3 From the AP Mode drop-down list, choose Monitor.Step 4 Click Apply.Step 5 Click OK when warned that the access point will be rebooted.Step 6 Click Save Configuration to save your changes.Step 7 Choose Wireless >Access Points >Radios >802.11b/g/n to open the 802.11b/g/n Radios page.Step 8 Hover your cursor over the blue drop-down arrow for the desired access point and choose Configure. The 802.11b/g/nCisco APs > Configure page appears.Step 9 Disable the access point radio by choosing Disable from the Admin Status drop-down list and click Apply.Step 10 Enable tracking optimization on the radio by choosing Enable from the Enable Tracking Optimization drop-down list.Step 11 From the four Channel drop-down lists, choose the channels on which you want to monitor RFID tags.Cisco Wireless LAN Controller Configuration Guide, Release 7.4        OL-28744-01 785
You must configure at least one channel on which the tags will bemonitored.NoteStep 12 Click Apply.Step 13 Click Save Configuration.Step 14 To reenable the access point radio, choose Enable from the Admin Status drop-down list and click Apply.Step 15 Click Save Configuration.Optimizing RFID Tracking on Access Points (CLI)Step 1 Configure an access point for monitor mode by entering this command:config ap mode monitor Cisco_APStep 2 When warned that the access point will be rebooted and asked if you want to continue, enter Y.Step 3 Save your changes by entering this command:save configStep 4 Disable the access point radio by entering this command:config 802.11b disable Cisco_APStep 5 Configure the access point to scan only the DCA channels supported by its country of operation by entering this command:config ap monitor-mode tracking-opt Cisco_APTo specify the exact channels to be scanned, enter the config ap monitor-mode tracking-opt Cisco_APcommand in Step 6.NoteTo disable tracking optimization for this access point, enter the config ap monitor-mode no-optimizationCisco_AP command.NoteStep 6 After you have entered the command in Step 5, you can enter this command to choose up to four specific 802.11b channelsto be scanned by the access point:config ap monitor-mode 802.11b fast-channel Cisco_AP channel1 channel2 channel3 channel4In the United States, you can assign any value between 1 and 11 (inclusive) to the channel variable. Othercountries support additional channels. You must assign at least one channel.NoteStep 7 Reenable the access point radio by entering this command:config 802.11b enable Cisco_APStep 8 Save your changes by entering this command:save configStep 9 See a summary of all access points in monitor mode by entering this command:show ap monitor-mode summary   Cisco Wireless LAN Controller Configuration Guide, Release 7.4786 OL-28744-01  Optimizing RFID Tracking on Access Points (CLI)
CHAPTER 118Configuring Probe Request Forwarding•Information About Configuring Probe Request Forwarding, page 787•Configuring Probe Request Forwarding (CLI), page 787Information About Configuring Probe Request ForwardingProbe requests are 802.11 management frames sent by clients to request information about the capabilities ofSSIDs. By default, access points forward acknowledged probe requests to the controller for processing.Acknowledged probe requests are probe requests for SSIDs that are supported by the access point. If desired,you can configure access points to forward both acknowledged and unacknowledged probe requests to thecontroller. The controller can use the information from unacknowledged probe requests to improve the locationaccuracy.Configuring Probe Request Forwarding (CLI)Step 1 Enable or disable the filtering of probe requests forwarded from an access point to the controller by entering this command:config advanced probe filter {enable |disable}If you enable probe filtering, the default filter setting, the access point forwards only acknowledged probe requests tothe controller. If you disable probe filtering, the access point forwards both acknowledged and unacknowledged proberequests to the controller.Step 2 Limit the number of probe requests sent to the controller per client per access point radio in a given interval by enteringthis command:config advanced probe limit num_probes intervalwhere•num_probes is the number of probe requests (from 1 to 100) forwarded to the controller per client per access pointradio in a given interval.•interval is the probe limit interval (from 100 to 10000 milliseconds).The default value for num_probes is 2 probe requests, and the default value for interval is 500 milliseconds.Cisco Wireless LAN Controller Configuration Guide, Release 7.4        OL-28744-01 787
Step 3 Enter the save config command to save your changes.Step 4 See the probe request forwarding configuration by entering this command:show advanced probeInformation similar to the following appears:Probe request filtering.......................... EnabledProbes fwd to controller per client per radio.... 2Probe request rate-limiting interval.......... 500 msec   Cisco Wireless LAN Controller Configuration Guide, Release 7.4788 OL-28744-01  Configuring Probe Request Forwarding (CLI)
CHAPTER 119Retrieving the Unique Device Identifier onControllers and Access Points•Information About Retrieving the Unique Device Identifier on Controllers and Access Points, page 789•Retrieving the Unique Device Identifier on Controllers and Access Points (GUI), page 789•Retrieving the Unique Device Identifier on Controllers and Access Points (CLI), page 790Information About Retrieving the Unique Device Identifier on Controllers andAccess PointsThe Unique Device Identifier (UDI) standard uniquely identifies products across all Cisco hardware productfamilies, enabling customers to identify and track Cisco products throughout their business and networkoperations and to automate their asset management systems. The standard is consistent across all electronic,physical, and standard business communications. The UDI consists of five data elements:•The orderable product identifier (PID)•The version of the product identifier (VID)•The serial number (SN)•The entity name•The product descriptionThe UDI is burned into the EEPROM of controllers and lightweight access points at the factory. It can beretrieved through either the GUI or the CLI.Retrieving the Unique Device Identifier on Controllers and Access Points (GUI)Step 1 Choose Controller >Inventory to open the Inventory page.This page shows the five data elements of the controller UDI.Cisco Wireless LAN Controller Configuration Guide, Release 7.4        OL-28744-01 789
Step 2 Choose Wireless >Access Points >All APs to open the All APs page.Step 3 Click the name of the desired access point.Step 4 Choose the Inventory tab to open the All APs > Details for (Inventory) page.This page shows the inventory information for the access point.Retrieving the Unique Device Identifier on Controllers and Access Points (CLI)Use these commands to retrieve the UDI on controllers and access points using the controller CLI:•show inventory—Shows the UDI string of the controller. Information similar to the following appears:NAME: "Chassis" , DESCR: "Cisco Wireless Controller"PID: WS-C3750G-24PS-W24, VID: V01, SN: FLS0952H00F•show inventory ap ap_id—Shows the UDI string of the access point specified.   Cisco Wireless LAN Controller Configuration Guide, Release 7.4790 OL-28744-01  Retrieving the Unique Device Identifier on Controllers and Access Points (CLI)
CHAPTER 120Performing a Link Test•Information About Performing a Link Test, page 791•Performing a Link Test (GUI), page 792•Performing a Link Test (CLI), page 792Information About Performing a Link TestA link test is used to determine the quality of the radio link between two devices. Two types of link-testpackets are transmitted during a link test: request and response. Any radio receiving a link-test request packetfills in the appropriate text boxes and echoes the packet back to the sender with the response type set.The radio link quality in the client-to-access point direction can differ from that in the access point-to-clientdirection due to the asymmetrical distribution of the transmit power and receive sensitivity on both sides. Twotypes of link tests can be performed: a ping test and a CCX link test.With the ping link test, the controller can test link quality only in the client-to-access point direction. The RFparameters of the ping reply packets received by the access point are polled by the controller to determine theclient-to-access point link quality.With the CCX link test, the controller can also test the link quality in the access point-to-client direction. Thecontroller issues link-test requests to the client, and the client records the RF parameters (received signalstrength indicator [RSSI], signal-to-noise ratio [SNR], and so on). of the received request packet in the responsepacket. Both the link-test requestor and responder roles are implemented on the access point and controller.Not only can the access point or controller initiate a link test to a CCX v4 or v5 client, but a CCX v4 or v5client can initiate a link test to the access point or controller.The controller shows these link-quality metrics for CCX link tests in both directions (out—access point toclient; in—client to access point):•Signal strength in the form of RSSI (minimum, maximum, and average)•Signal quality in the form of SNR (minimum, maximum, and average)•Total number of packets that are retried•Maximum retry count for a single packet•Number of lost packets•Data rate of a successfully transmitted packetCisco Wireless LAN Controller Configuration Guide, Release 7.4        OL-28744-01 791
The controller shows this metric regardless of direction:•Link test request/reply round-trip time (minimum, maximum, and average)The controller software supports CCX versions 1 through 5. CCX support is enabled automatically for everyWLAN on the controller and cannot be disabled. The controller stores the CCX version of the client in itsclient database and uses it to limit the features for this client. If a client does not support CCXv4 or v5, thecontroller performs a ping link test on the client. If a client supports CCXv4 or v5, the controller performs aCCX link test on the client. If a client times out during a CCX link test, the controller switches to the pinglink test automatically.NoteFollow the instructions in this section to perform a link test using either the GUI or the CLI.Performing a Link Test (GUI)Step 1 Choose Monitor >Clients to open the Clients page.Step 2 Hover your cursor over the blue drop-down arrow for the desired client and choose LinkTest. A link test page appears.You can also access this page by clicking the MAC address of the desired client and then clicking the LinkTest button on the top of the Clients > Detail page.NoteThis page shows the results of the CCX link test.If the client and/or controller does not support CCX v4 or later releases, the controller performs a ping link teston the client instead, and a much more limited link test page appears.NoteThe Link Test results of CCX clients when it fails will default to ping test results if the client is reachable.NoteStep 3 Click OK to exit the link test page.Performing a Link Test (CLI)Use these commands to run a link test using the controller CLI:•Run a link test by entering this command:linktest ap_macWhen CCX v4 or later releases is enabled on both the controller and the client being tested, informationsimilar to the following appears:CCX Link Test to 00:0d:88:c5:8a:d1.Link Test Packets Sent...................................... 20Link Test Packets Received................................. 10Link Test Packets Lost (Total/AP to Client/Client to AP).... 10/5/5Link Test Packets round trip time (min/max/average)......... 5ms/20ms/15msRSSI at AP (min/max/average)................................ -60dBm/-50dBm/-55dBmRSSI at Client (min/max/average)............................ -50dBm/-40dBm/-45dBm   Cisco Wireless LAN Controller Configuration Guide, Release 7.4792 OL-28744-01  Performing a Link Test (GUI)
SNR at AP (min/max/average)................................. 40dB/30dB/35dBSNR at Client (min/max/average)............................. 40dB/30dB/35dBTransmit Retries at AP (Total/Maximum)...................... 5/3Transmit Retries at Client (Total/Maximum).................. 4/2Transmit rate: 1M 2M 5.5M 6M 9M 11M 12M 18M 24M 36M 48M 54M 108MPacket Count: 0 0 0 0 0 0 0 0 0 2 0 18 0Transmit rate: 1M 2M 5.5M 6M 9M 11M 12M 18M 24M 36M 48M 54M 108MPacket Count: 0 0 0 0 0 0 0 0 0 2 0 8 0When CCX v4 or later releases is not enabled on either the controller or the client being tested, fewerdetails appear:Ping Link Test to 00:0d:88:c5:8a:d1.Link Test Packets Sent.......................... 20Link Test Packets Received...................... 20Local Signal Strength........................... -49dBmLocal Signal to Noise Ratio..................... 39dB•Adjust the link-test parameters that are applicable to both the CCX link test and the ping test by enteringthese commands from configuration mode:linktest frame-size size_of_link-test_frameslinktest num-of-frame number_of_link-test_request_frames_per_testCisco Wireless LAN Controller Configuration Guide, Release 7.4       OL-28744-01 793Performing a Link Test (CLI)
   Cisco Wireless LAN Controller Configuration Guide, Release 7.4794 OL-28744-01  Performing a Link Test (CLI)
CHAPTER 121Configuring Link Latency•Information About Configuring Link Latency, page 795•Restrictions for Link Latency, page 796•Configuring Link Latency (GUI), page 796•Configuring Link Latency (CLI), page 796Information About Configuring Link LatencyYou can configure link latency on the controller to measure the link between an access point and the controller.This feature can be used with all access points joined to the controller but is especially useful for FlexConnectand OfficeExtend access points, for which the link could be a slow or unreliable WAN connection.The following are some guidelines for link latency:•Link latency monitors the round-trip time of the CAPWAP heartbeat packets (echo request and response)from the access point to the controller and back. This time can vary due to the network link speed andcontroller processing loads. The access point timestamps the outgoing echo requests to the controllerand the echo responses received from the controller. The access point sends this delta time to the controlleras the system round-trip time. The access point sends heartbeat packets to the controller at a defaultinterval of 30 seconds.Link latency calculates the CAPWAP response time between the access point and thecontroller. It does not measure network latency or ping responses.Note•The controller displays the current round-trip time as well as a running minimum and maximum round-triptime. The minimum and maximum times continue to run as long as the controller is up or can be clearedand allowed to restart.•You can configure link latency for a specific access point using the controller GUI or CLI or for allaccess points joined to the controller using the CLI.Cisco Wireless LAN Controller Configuration Guide, Release 7.4        OL-28744-01 795
Restrictions for Link Latency•Link latency is supported for use only with FlexConnect access points in connected mode. FlexConnectaccess points in standalone mode are not supported.Configuring Link Latency (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 configure link latency.Step 3 Choose the Advanced tab to open the All APs > Details for (Advanced) page.Step 4 Select the Enable Link Latency check box to enable link latency for this access point or unselect it to prevent the accesspoint from sending the round-trip time to the controller after every echo response is received. The default value isunselected.Step 5 Click Apply to commit your changes.Step 6 Click Save Configuration to save your changes.Step 7 When the All APs page reappears, click the name of the access point again.Step 8 When the All APs > Details for page reappears, choose the Advanced tab again. The link latency and data latency resultsappear below the Enable Link Latency check box:•Current—The current round-trip time (in milliseconds) of CAPWAP heartbeat packets or data packets from theaccess point to the controller and back.•Minimum—Since link latency has been enabled or reset, the minimum round-trip time (in milliseconds) ofCAPWAP heartbeat packets or data packets from the access point to the controller and back.•Maximum—Since link latency has been enabled or reset, the maximum round-trip time (in milliseconds) ofCAPWAP heartbeat packets or data packets from the access point to the controller and back.Step 9 To clear the current, minimum, and maximum link latency and data latency statistics on the controller for this accesspoint, click Reset Link Latency.Step 10 After the page refreshes and the All APs > Details for page reappears, choose the Advanced tab. The updated statisticsappear in the Minimum and Maximum text boxes.Configuring Link Latency (CLI)Step 1 Enable or disable link latency for a specific access point or for all access points currently associated to the controller byentering this command:config ap link-latency {enable |disable} {Cisco_AP |all}The default value is disabled.   Cisco Wireless LAN Controller Configuration Guide, Release 7.4796 OL-28744-01  Restrictions for Link Latency
The config ap link-latency {enable |disable}all command enables or disables link latency only for accesspoints that are currently joined to the controller. It does not apply to access points that join in the future.NoteStep 2 See the link latency results for a specific access point by entering this command:show ap config general Cisco_APInformation similar to the following appears:Cisco AP Identifier.............................. 1Cisco AP Name.................................... AP1...AP Link Latency.................................. EnabledCurrent Delay................................... 1 msMaximum Delay................................... 1 msMinimum Delay................................... 1 msLast updated (based on AP Up Time)........... 0 days, 05 h 03 m 25 sThe output of this command contains the following link latency results:•Current Delay—The current round-trip time (in milliseconds) of CAPWAP heartbeat packets from the accesspoint to the controller and back.•Maximum Delay—Since link latency has been enabled or reset, the maximum round-trip time (in milliseconds)of CAPWAP heartbeat packets from the access point to the controller and back.•Minimum Delay—Since link latency has been enabled or reset, the minimum round-trip time (in milliseconds) ofCAPWAP heartbeat packets from the access point to the controller and back.Step 3 Clear the current, minimum, and maximum link latency statistics on the controller for a specific access point by enteringthis command:config ap link-latency reset Cisco_APStep 4 See the results of the reset by entering this command:show ap config general Cisco_APCisco Wireless LAN Controller Configuration Guide, Release 7.4       OL-28744-01 797Configuring Link Latency (CLI)
   Cisco Wireless LAN Controller Configuration Guide, Release 7.4798 OL-28744-01  Configuring Link Latency (CLI)
CHAPTER 122Configuring the TCP MSS•Information About Configuring the TCP MSS, page 799•Configuring TCP MSS (GUI), page 799•Configuring TCP MSS (CLI), page 800Information About Configuring the TCP MSSIf the client’s maximum segment size (MSS) in a Transmission Control Protocol (TCP) three-way handshakeis greater than the maximum transmission unit can handle, the client might experience reduced throughputand the fragmentation of packets. To avoid this problem in controller software release 6.0 or later releases,you can specify the MSS for all access points that are joined to the controller or for a specific access point.When you enable this feature, the access point selects the MSS for TCP packets to and from wireless clientsin its data path. If the MSS of these packets is greater than the value that you configured or greater than thedefault value for the CAPWAP tunnel, the access point changes the MSS to the new configured value.TCP MSS is supported only on APs that are in local mode.Configuring TCP MSS (GUI)Step 1 Choose WIRELESS > Access Points > Global Configuration to open the Global Configuration page.Step 2 Under TCP MSS, select the Global TCP Adjust MSS check box and set the MSS for all access points that are associatedwith the controller. The valid range is between 536 and 1363 bytes.Cisco Wireless LAN Controller Configuration Guide, Release 7.4        OL-28744-01 799
Configuring TCP MSS (CLI)Step 1 Enable or disable the TCP MSS on a particular access point or on all access points by entering this command:config ap tcp-mss-adjust {enable |disable} {Cisco_AP |all}sizewhere the size parameter is a value between 536 and 1363 bytes. The default value varies for different clients.Step 2 Save your changes by entering this command:save configStep 3 See the current TCP MSS setting for a particular access point or all access points by entering this command:show ap tcp-mss-adjust {Cisco_AP |all}Information similar to the following appears:AP Name TCP State MSS Size------------------ -------- -------AP-1140 enabled 536AP-1240 disabled -AP-1130 disabled -   Cisco Wireless LAN Controller Configuration Guide, Release 7.4800 OL-28744-01  Configuring TCP MSS (CLI)
CHAPTER 123Configuring Power Over Ethernet•Information About Configuring Power over Ethernet, page 801•Configuring Power over Ethernet (GUI), page 803•Configuring Power over Ethernet (CLI), page 804Information About Configuring Power over EthernetWhen an access point that has been converted to lightweight mode (such as an AP1131 or AP1242) or a 1250series access point is powered by a power injector that is connected to a Cisco pre-Intelligent PowerManagement (pre-IPM) switch, you need to configure Power over Ethernet (PoE), also known as inline power.The dual-radio 1250 series access points can operate in four different modes when powered using PoE:•20.0 W (Full Power)—This mode is equivalent to using a power injector or an AC/DC adapter.•16.8 W—Both transmitters are used but at reduced power. Legacy data rates are not affected, but theM0 to M15 data rates are reduced in the 2.4-GHz band. Throughput should be minimally impactedbecause all data rates are still enabled. The range is affected because of the lower transmit power. Allreceivers remain enabled.•15.4 W—Only a single transmitter is enabled. Legacy data rates and M0 to M7 rates are minimallyaffected. M8 to M15 rates are disabled because they require both transmitters. Throughput is better thanthat received with legacy access points but less than the 20 and 16.8 W power modes.•11.0 W (Low Power)—The access point runs, but both radios are disabled.The following are some guidelines for Power over Ethernet:•When a dual-radio 1250 series access point is powered using 15.4-W PoE, it cannot operate at fullfunctionality, which requires 20 W. The access point can operate with dual radios on 15.4-W PoE, butperformance is reduced in terms of throughput and range. If full functionality is required on 15.4 W,you can remove one of the radios from the 1250 series access point chassis or disable it in controllersoftware release 6.0 or later releases so that the other radio can operate in full 802.11n mode. After theaccess point radio is administratively disabled, the access point must be rebooted for the change to takeeffect. The access point must also be rebooted after you reenable the radio to put it into reduced throughputmode.Cisco Wireless LAN Controller Configuration Guide, Release 7.4        OL-28744-01 801
These modes provide the flexibility of running the 1250 series access points with the available wiredinfrastructure to obtain the desired level of performance. With enhanced PoE switches (such as the CiscoCatalyst 3750-E Series Switches), the 1250 series access points can provide maximum features andfunctionality with a minimum total cost of ownership. Alternatively, if you decide to power the accesspoint with the existing PoE (802.3af) switches, the access point chooses the appropriate mode of operationbased on whether it has one radio or two.For more information on the Cisco PoE switches, see this URL: http://www.cisco.com/en/US/prod/switches/epoe.htmlNote•The table below shows the maximum transmit power settings for 1250 series access points usingPoE.◦Table 23: Maximum Transmit Power Settings for 1250 Series Access Points Using PoEMaximum Transmit Power (dBm)5Cyclic ShiftDiversity (CSD)Number ofTransmittersData RatesRadioBandePoE Mode(20 W)ePoE PowerOptimizedMode (16.8W)802.3afMode (15.4W)202020—1802.11b2.4 GHz171717—1802.11g1720 (17 perTx)1714 (11 perTx)17DisabledDisabledEnabled(default)12802.11n MCS0-720 (17 perTx)14 (11 perTx)Disabled—2802.11n MCS8-15171717—1802.11a5 GHz1720 (17 perTx)1720 (17 perTx)17DisabledDisabledEnabled(default)12802.11n MCS0-720 (17 perTx)20 (17 perTx)Disabled—2802.11n MCS8-155Maximum transmit power varies by channel and according to individual country regulations. See the product documentation for specific details.•When powered with a non-Cisco standard PoE switch, the 1250 series access point operates under 15.4Watts. Even if the non-Cisco switch or midspan device is capable of providing higher power, the accesspoint does not operate in enhanced PoE mode.   Cisco Wireless LAN Controller Configuration Guide, Release 7.4802 OL-28744-01  Information About Configuring Power over Ethernet
Configuring Power over Ethernet (GUI)Step 1 Choose Wireless >Access Points >All APs and then the name of the desired access point.Step 2 Choose the Advanced tab to open the All APs > Details for (Advanced) page.The PoE Status text box shows the power level at which the access point is operating: High (20 W), Medium (16.8 W),or Medium (15.4 W). This text box is not configurable. The controller auto-detects the access point’s power source anddisplays the power level here.This text box applies only to 1250 series access points that are powered using PoE. There are two other waysto determine if the access point is operating at a lower power level. First, the “Due to low PoE, radio is transmittingat degraded power”message appears under the Tx Power Level Assignment section on the 802.11a/n (or802.11b/g/n) Cisco APs > Configure page. Second, the “PoE Status: degraded operation”message appears inthe controller’s trap log on the Trap Logs page.NoteStep 3 Perform one of the following:•Select the Pre-standard 802.3af switches check box if the access point is being powered by a high-power 802.3afCisco switch. This switch provides more than the traditional 6 Watts of power but do not support the intelligentpower management (IPM) feature.•Unselect the Pre-standard 802.3af switches check box if power is being provided by a power injector. This is thedefault value.Step 4 Select the Power Injector State check box if the attached switch does not support IPM and a power injector is beingused. If the attached switch supports IPM, you do not need to select this check box.Step 5 If you selected the Power Injector State check box in the previous step, the Power Injector Selection and Injector SwitchMAC Address parameters appear. The Power Injector Selection parameter enables you to protect your switch port froman accidental overload if the power injector is inadvertently bypassed. Choose one of these options from the drop-downlist to specify the desired level of protection:•Installed—This option examines and remembers the MAC address of the currently connected switch port andassumes that a power injector is connected. Choose this option if your network contains older Cisco 6-Watt switchesand you want to avoid possible overloads by forcing a double-check of any relocated access points.If you want to configure the switch MAC address, enter the MAC address in the Injector Switch MAC Addresstext box. If you want the access point to find the switch MAC address, leave the Injector Switch MAC Addresstext box blank.Each time an access point is relocated, the MAC address of the new switch port fails to match theremembered MAC address, and the access point remains in low-power mode. You must then physicallyverify the existence of a power injector and reselect this option to cause the new MAC address to beremembered.Note•Override—This option allows the access point to operate in high-power mode without first verifying a matchingMAC address. You can use this option if your network does not contain any older Cisco 6-W switches that couldbe overloaded if connected directly to a 12-W access point. The advantage of this option is that if you relocate theaccess point, it continues to operate in high-power mode without any further configuration. The disadvantage ofthis option is that if the access point is connected directly to a 6-W switch, an overload occurs.Cisco Wireless LAN Controller Configuration Guide, Release 7.4       OL-28744-01 803Configuring Power over Ethernet (GUI)
Step 6 Click Apply.Step 7 If you have a dual-radio 1250 series access point and want to disable one of its radios in order to enable the other radioto receive full power, follow these steps:a) Choose Wireless >Access Points >Radios >802.11a/n or 802.11b/g/n to open the 802.11a/n (or 802.11b/g/n)Radios page.b) Hover your cursor over the blue drop-down arrow for the radio that you want to disable and choose Configure.c) On the 802.11a/n (or 802.11b/g/n) Cisco APs > Configure page, choose Disable from the Admin Status drop-downlist.d) Click Apply.e) Manually reset the access point in order for the change to take effect.Step 8 Click Save Configuration.Configuring Power over Ethernet (CLI)Use these commands to configure and See PoE settings using the controller CLI:•If your network contains any older Cisco 6-W switches that could be accidentally overloaded if connecteddirectly to a 12-W access point, enter this command:config ap power injector enable {Cisco_AP |all}installedThe access point remembers that a power injector is connected to this particular switch port. If yourelocate the access point, you must reissue this command after the presence of a new power injector isverified.Ensure CDP is enabled before entering this command. Otherwise, this command willfail. See the Configuring the Cisco Discovery Protocol section for information aboutenabling CDP.Note•Remove the safety checks and allow the access point to be connected to any switch port by entering thiscommand:config ap power injector enable {Cisco_AP |all}overrideYou can use this command if your network does not contain any older Cisco 6-W switches that couldbe overloaded if connected directly to a 12-W access point. The access point assumes that a powerinjector is always connected. If you relocate the access point, it continues to assume that a power injectoris present.•If you know the MAC address of the connected switch port and do not want to automatically detect itusing the installed option, enter this command:config ap power injector enable {Cisco_AP |all}switch_port_mac_address•If you have a dual-radio 1250 series access point and want to disable one of its radios in order to enablethe other radio to receive full power, enter this command:config {802.11a |802.11b}disable Cisco_AP   Cisco Wireless LAN Controller Configuration Guide, Release 7.4804 OL-28744-01  Configuring Power over Ethernet (CLI)
You must manually reset the access point in order for the change to take effect.Note•See the PoE settings for a specific access point by entering this command:show ap config general Cisco_APInformation similar to the following appears:Cisco AP Identifier.............................. 1Cisco AP Name.................................... AP1...PoE Pre-Standard Switch.......................... EnabledPoE Power Injector MAC Addr...................... DisabledPower Type/Mode.................................. PoE/Low Power (degraded mode)...The Power Type/Mode text box shows “degraded mode”if the access point is not operating at full power.•See the controller’s trap log by entering this command:show traplogIf the access point is not operating at full power, the trap contains “PoE Status: degraded operation.”•You can power an access point by a Cisco prestandard 15-W switch with Power over Ethernet (PoE)by entering this command:config ap power pre-standard {enable |disable} {all |Cisco_AP}A Cisco prestandard 15-W switch does not support intelligent power management (IPM) but does havesufficient power for a standard access point. The following Cisco prestandard 15-W switches are available:•WS-C3550, WS-C3560, WS-C3750•C1880•2600, 2610, 2611, 2621, 2650, 2651•2610XM, 2611XM, 2621XM, 2650XM, 2651XM, 2691•2811, 2821, 2851•3631-telco, 3620, 3640, 3660•3725, 3745•3825, 3845The enable version of this command is required for full functionality when the access point is poweredby a Cisco prestandard 15-W switch. It is safe to use if the access point is powered by either an IPMswitch or a power injector or if the access point is not using one of the 15-W switches listed above.You might need this command if your radio operational status is "Down" when you expect it to be "Up."Enter the show msglog command to look for this error message, which indicates a PoE problem:Apr 13 09:08:24.986 spam_lrad.c:2262 LWAPP-3-MSGTAG041: AP 00:14:f1:af:f3:40 is unabletoverify sufficient in-line power. Radio slot 0 disabled.Cisco Wireless LAN Controller Configuration Guide, Release 7.4       OL-28744-01 805Configuring Power over Ethernet (CLI)
   Cisco Wireless LAN Controller Configuration Guide, Release 7.4806 OL-28744-01  Configuring Power over Ethernet (CLI)
CHAPTER 124Viewing Clients•Viewing Clients (GUI), page 807•Viewing Clients (CLI), page 808Viewing Clients (GUI)Step 1 Choose Monitor >Clients to open the Clients page.This page lists all of the clients that are associated to the controller’s access points. It provides the following informationfor each client:•The MAC address of the client•The name of the access point to which the client is associated•The name of the WLAN used by the client•The type of client (802.11a, 802.11b, 802.11g, or 802.11n)If the 802.11n client associates to an 802.11a radio that has 802.11n enabled, then the client type showsas 802.11a/n. If the 802.11n client associates to an 802.11b/g radio with 802.11n enabled, then the clienttype shows as 802.11b/n.Note•The status of the client connection•The authorization status of the client•The port number of the access point to which the client is associated•An indication of whether the client is a WGBIf you want to remove or disable a client, hover your cursor over the blue drop-down arrow for that clientand choose Remove or Disable, respectively. If you want to test the connection between the client andthe access point, hover your cursor over the blue drop-down arrow for that client and choose Link Test.NoteStep 2 Create a filter to display only clients that meet certain criteria (such as the MAC address, status, or radio type) as follows:a) Click Change Filter to open the Search Clients dialog box.b) Select one or more of the following check boxes to specify the criteria used when displaying clients:Cisco Wireless LAN Controller Configuration Guide, Release 7.4        OL-28744-01 807
MAC Address—Enter a client MAC address.When you enable the MAC address filter, the other filters are disabled automatically. When you enableany of the other filters, the MAC address filter is disabled automatically.Note••AP Name—Enter the name of an access point.•WLAN Profile—Choose one of the available WLAN profiles from the drop-down list.•Status—Select the Associated,Authenticated,Excluded, and/or Idle check boxes.•Radio Type—Choose 802.11a,802.11b,802.11g,802.11an,802.11bn or Mobile.•WGB—Enter the WGB clients associated to the controller’s access points.c) Click Apply. The Current Filter parameter at the top of the Clients page shows the filters that are currently applied.If you want to remove the filters and display the entire client list, click ClearFilter.NoteStep 3 Click the MAC address of the client to view detailed information for a specific client. The Clients > Detail page appears.This page shows the following information:•The general properties of the client•The security settings of the client•The QoS properties of the client•Client statistics•The properties of the access point to which the client is associatedViewing Clients (CLI)Use these commands to view client information:•See the clients associated to a specific access point by entering this command:show client ap {802.11a |802.11b}Cisco_AP•See a summary of the clients associated to the controller’s access points by entering this command:show client summary•See detailed information for a specific client by entering this command:show client detail client_mac   Cisco Wireless LAN Controller Configuration Guide, Release 7.4808 OL-28744-01  Viewing Clients (CLI)
CHAPTER 125Configuring LED States for Access Points•Configuring LED States, page 809•Configuring Flashing LEDs, page 810Configuring LED StatesInformation About Configuring LED States for Access PointsIn a wireless LAN network where there are a large number of access points, it is difficult to locate a specificaccess point associated with the controller. You can configure the controller to set the LED state of an accesspoint so that it blinks and the access point can be located. This configuration can be done in the wirelessnetwork on a global as well as per-AP level.The LED state configuration at the global level takes precedence over the AP level.Configuring the LED State for Access Points in a Network Globally (GUI)Step 1 Choose Wireless >Access Points >Global Configuration to open the Global Configuration page.Step 2 Select the LED state check box.Step 3 Choose Enable from the drop-down list adjacent to this check box.Step 4 Click Apply.Configuring the LED State for Access Point in a Network Globally (CLI)•Set the LED state for all access points associated with a controller by entering this command:config ap led-state {enable |disable}allCisco Wireless LAN Controller Configuration Guide, Release 7.4        OL-28744-01 809
Configuring LED State on a Specific Access Point (GUI)Step 1 Choose Wireless > Access Points > All APs and then the name of the desired access point.Step 2 Choose the Advanced tab to open the All APs > Details for (Advanced) page.Step 3 Select the LED state check box.Step 4 Choose Enable from the drop-down list adjacent to this text box.Step 5 Click Apply.Configuring LED State on a Specific Access Point (CLI)Step 1 Determine the ID of the access point for which you want to configure the LED state by entering this command:show ap summaryStep 2 Configure the LED state by entering the following command:config ap led-state {enable |disable}Cisco_APConfiguring Flashing LEDsInformation About Configuring Flashing LEDsController software enables you to flash the LEDs on an access point in order to locate it. All Cisco IOSlightweight access points support this feature.Configuring Flashing LEDs (CLI)Use these commands to configure LED flashing from the privileged EXEC mode of the controller:1Configure the LED flash for an AP by entering this command:config ap led-state flash {seconds |indefinite |disable} {Cisco_AP}The valid LED flash duration for the AP is 1 to 3600 seconds. You can also configure the LED to flashindefinitely or to stop flashing the LED.2Disable LED flash for an AP after enabling it by entering this command:config ap led-state flash disable Cisco_APThe command disables LED flashing immediately. For example, if you run the previous command (withthe seconds parameter set to 60 seconds) and then disable LED flashing after only 20 seconds, the accesspoint’s LEDs stop flashing immediately.   Cisco Wireless LAN Controller Configuration Guide, Release 7.4810 OL-28744-01  Configuring Flashing LEDs
3Save your changes by entering this command:save config4Check the status of LED flash for the AP by entering this command:show ap led-flash Cisco_APInformation similar to the following appears:(Cisco Controller)> show ap led-flash AP1040_46:b9Led Flash........................................ Enabled for 450 secs, 425 secs leftThe output of these commands is sent only to the controller console, regardless of whether the commandswere entered on the console or in a TELNET/SSH CLI session.NoteCisco Wireless LAN Controller Configuration Guide, Release 7.4       OL-28744-01 811Configuring Flashing LEDs
   Cisco Wireless LAN Controller Configuration Guide, Release 7.4812 OL-28744-01  Configuring Flashing LEDs
CHAPTER 126Configuring Access Points with Dual-BandRadios•Configuring Access Points with Dual-Band Radios (GUI), page 813•Configuring Access Points with Dual-Band Radios (CLI), page 814Configuring Access Points with Dual-Band Radios (GUI)Step 1 Choose Wireless >Access Points >Radios >Dual-Band Radios to open the Dual-Band Radios page.Step 2 Hover your cursor over the blue drop-down arrow of the AP and click Configure.Step 3 Configure the Admin Status.Step 4 Configure CleanAir Admin Status as one of the following:•Enable•Disable•5 GHz Only•2.4 GHz OnlyStep 5 Click Apply.Step 6 Click Save Configuration.What to Do NextYou can monitor the access points with dual-band radios by navigating to Monitor >Access Points >Radios>Dual-Band Radios.Cisco Wireless LAN Controller Configuration Guide, Release 7.4        OL-28744-01 813
Configuring Access Points with Dual-Band Radios (CLI)•Configure an access point with dual-band radios by entering this command:config 802.11-abgn {enable |disable}ap-name•Configure the CleanAir features for an access point with dual-band radios by entering this command:config 802.11-abgn cleanair {enable |disable}ap-name band 2.4-or-5-GHz   Cisco Wireless LAN Controller Configuration Guide, Release 7.4814 OL-28744-01  Configuring Access Points with Dual-Band Radios (CLI)
PART VIIConfiguring Radio Resource Management•Configuring RRM, page 817•Configuring RRM Neighbor Discovery Packets, page 837•Configuring RF Groups, page 839•Overriding RRM, page 847•Configuring CCX Radio Management Features, page 855
CHAPTER 127Configuring RRM•Information About Radio Resource Management, page 817•Restrictions for Configuring RRM, page 822•Configuring the RF Group Mode (GUI), page 822•Configuring the RF Group Mode (CLI), page 823•Configuring Transmit Power Control (GUI), page 823•Configuring Off-Channel Scanning Defer, page 825•Configuring RRM (CLI), page 831•Viewing RRM Settings (CLI), page 835•Debug RRM Issues (CLI), page 836Information About Radio Resource ManagementThe Radio Resource Management (RRM) software embedded in the Cisco Wireless LAN Controller acts asa built-in RF engineer to consistently provide real-time RF management of your wireless network. RRMenables Cisco WLCs to continually monitor their associated lightweight access points for the followinginformation:•Traffic load—The total bandwidth used for transmitting and receiving traffic. It enables wireless LANmanagers to track and plan network growth ahead of client demand.•Interference—The amount of traffic coming from other 802.11 sources.•Noise—The amount of non-802.11 traffic that is interfering with the currently assigned channel.•Coverage—The received signal strength (RSSI) and signal-to-noise ratio (SNR) for all connected clients.•Other—The number of nearby access points.Using this information, RRM can periodically reconfigure the 802.11 RF network for best efficiency. To dothis, RRM performs these functions:•Radio resource monitoringCisco Wireless LAN Controller Configuration Guide, Release 7.4        OL-28744-01 817
•Transmit power control•Dynamic channel assignment•Coverage hole detection and correctionRadio Resource MonitoringRRM automatically detects and configures new Cisco WLCs and lightweight access points as they are addedto the network. It then automatically adjusts associated and nearby lightweight access points to optimizecoverage and capacity.Lightweight access points can simultaneously scan all valid 802.11a/b/g channels for the country of operationas well as for channels available in other locations. The access points go “off-channel”for a period not greaterthan 60 ms to monitor these channels for noise and interference. Packets collected during this time are analyzedto detect rogue access points, rogue clients, ad-hoc clients, and interfering access points.In the presence of voice traffic (in the last 100 ms), the access points defer off-channel measurements.NoteEach access point spends only 0.2 percent of its time off-channel. This activity is distributed across all accesspoints so that adjacent access points are not scanning at the same time, which could adversely affect wirelessLAN performance.When there are numerous rogue access points in the network, the chance of detecting rogues on channels157 or 161 by a FlexConnect or local mode access point is small. In such cases, the monitor mode AP canbe used for rogue detection.NoteTransmit Power ControlThe Cisco WLC dynamically controls access point transmit power based on real-time wireless LAN conditions.You can choose between two versions of transmit power control: TPCv1 and TPCv2. With TPCv1, typically,power can be kept low to gain extra capacity and reduce interference. With TPCv2, transmit power isdynamically adjusted with the goal of minimum interference. TPCv2 is suitable for dense networks. In thismode, there could be higher roaming delays and coverage hole incidents.The Transmit Power Control (TPC) algorithm both increases and decreases an access point’s power in responseto changes in the RF environment. In most instances, TPC seeks to lower an access point's power to reduceinterference, but in the case of a sudden change in the RF coverage—for example, if an access point fails orbecomes disabled—TPC can also increase power on surrounding access points. This feature is different fromcoverage hole detection, which is primarily concerned with clients. TPC provides enough RF power to achievedesired coverage levels while avoiding channel interference between access points.This table shows the power level mapping.5 GHz2.4 GHzPower Level20 dBm (100 mW)23 dBm (200 mW) CCK Only117 dBm (50 mW)20 dBm (100 mW)2   Cisco Wireless LAN Controller Configuration Guide, Release 7.4818 OL-28744-01  Information About Radio Resource Management
5 GHz2.4 GHzPower Level14 dBm (25 mW)17 dBm (50 mW)311 dBm (12.5 mW)14 dBm (25 mW)48 dBm (6.25 mW)11 dBm (12.5 mW)55 dBm (3.13 mW)8 dBm (6.25 mW)62 dBm (1.56 mW)5 dBm (3.13 mW)7–1 dBm (0.78 mW)2 dBm (1.56 mW)8–1 dBm (0.78 mW)Overriding the TPC Algorithm with Minimum and Maximum Transmit Power SettingsThe TPC algorithm balances RF power in many diverse RF environments. However, it is possible that automaticpower control will not be able to resolve some scenarios in which an adequate RF design was not possible toimplement due to architectural restrictions or site restrictions—for example, when all access points must bemounted in a central hallway, placing the access points close together, but requiring coverage out to the edgeof the building.In these scenarios, you can configure maximum and minimum transmit power limits to override TPCrecommendations. The maximum and minimum TPC power settings apply to all access points through RFprofiles in a RF network.To set the Maximum Power Level Assignment and Minimum Power Level Assignment, enter the maximumand minimum transmit power used by RRM in the text boxes in the Tx Power Control page. The range forthese parameters is -10 to 30 dBm. The minimum value cannot be greater than the maximum value; themaximum value cannot be less than the minimum value.If you configure a maximum transmit power, RRM does not allow any access point attached to the controllerto exceed this transmit power level (whether the power is set by RRM TPC or by coverage hole detection).For example, if you configure a maximum transmit power of 11 dBm, then no access point would transmitabove 11 dBm, unless the access point is configured manually.Dynamic Channel AssignmentTwo adjacent access points on the same channel can cause either signal contention or signal collision. In acollision, data is not received by the access point. This functionality can become a problem, for example,when someone reading e-mail in a café affects the performance of the access point in a neighboring business.Even though these are completely separate networks, someone sending traffic to the café on channel 1 candisrupt communication in an enterprise using the same channel. Controllers can dynamically allocate accesspoint channel assignments to avoid conflict and to increase capacity and performance. Channels are “reused”to avoid wasting scarce RF resources. In other words, channel 1 is allocated to a different access point farfrom the café, which is more effective than not using channel 1 altogether.The controller’s Dynamic Channel Assignment (DCA) capabilities are also useful in minimizing adjacentchannel interference between access points. For example, two overlapping channels in the 802.11b/g band,such as 1 and 2, cannot both simultaneously use 11/54 Mbps. By effectively reassigning channels, the controllerkeeps adjacent channels separated.Cisco Wireless LAN Controller Configuration Guide, Release 7.4       OL-28744-01 819Information About Radio Resource Management
We recommend that you use only non-overlapping channels (1, 6, 11, and so on).NoteThe controller examines a variety of real-time RF characteristics to efficiently handle channel assignmentsas follows:•Access point received energy—The received signal strength measured between each access point andits nearby neighboring access points. Channels are optimized for the highest network capacity.•Noise—Noise can limit signal quality at the client and access point. An increase in noise reduces theeffective cell size and degrades user experience. By optimizing channels to avoid noise sources, thecontroller can optimize coverage while maintaining system capacity. If a channel is unusable due toexcessive noise, that channel can be avoided.•802.11 Interference—Interference is any 802.11 traffic that is not part of your wireless LAN, includingrogue access points and neighboring wireless networks. Lightweight access points constantly scan allchannels looking for sources of interference. If the amount of 802.11 interference exceeds a predefinedconfigurable threshold (the default is 10 percent), the access point sends an alert to the controller. Usingthe RRM algorithms, the controller may then dynamically rearrange channel assignments to increasesystem performance in the presence of the interference. Such an adjustment could result in adjacentlightweight access points being on the same channel, but this setup is preferable to having the accesspoints remain on a channel that is unusable due to an interfering foreign access point.In addition, if other wireless networks are present, the controller shifts the usage of channels tocomplement the other networks. For example, if one network is on channel 6, an adjacent wireless LANis assigned to channel 1 or 11. This arrangement increases the capacity of the network by limiting thesharing of frequencies. If a channel has virtually no capacity remaining, the controller may choose toavoid this channel. In very dense deployments in which all nonoverlapping channels are occupied, thecontroller does its best, but you must consider RF density when setting expectations.•Load and utilization—When utilization monitoring is enabled, capacity calculations can consider thatsome access points are deployed in ways that carry more traffic than other access points (for example,a lobby versus an engineering area). The controller can then assign channels to improve the access pointwith the worst performance reported. The load is taken into account when changing the channel structureto minimize the impact on clients currently in the wireless LAN. This metric keeps track of every accesspoint’s transmitted and received packet counts to determine how busy the access points are. New clientsavoid an overloaded access point and associate to a new access point. This parameter is disabled bydefault.The controller combines this RF characteristic information with RRM algorithms to make system-widedecisions. Conflicting demands are resolved using soft-decision metrics that guarantee the best choice forminimizing network interference. The end result is optimal channel configuration in a three-dimensionalspace, where access points on the floor above and below play a major factor in an overall wireless LANconfiguration.Radios using 40-MHz channels in the 2.4-GHz band or or 80MHz channels are not supported by DCA.NoteThe RRM startup mode is invoked in the following conditions:•In a single-controller environment, the RRM startup mode is invoked after the controller is rebooted.   Cisco Wireless LAN Controller Configuration Guide, Release 7.4820 OL-28744-01  Information About Radio Resource Management
•In a multiple-controller environment, the RRM startup mode is invoked after an RF Group leader iselected.You can trigger RRM startup mode from CLI.RRM startup mode runs for 100 minutes (10 iterations at 10-minute intervals). The duration of the RRMstartup mode is independent of the DCA interval, sensitivity, and network size. The startup mode consists of10 DCA runs with high sensitivity (making channel changes easy and sensitive to the environment) to convergeto a steady state channel plan. After the startup mode is finished, DCA continues to run at the specified intervaland sensitivity.Coverage Hole Detection and CorrectionThe RRM coverage hole detection algorithm can detect areas of radio coverage in a wireless LAN that arebelow the level needed for robust radio performance. This feature can alert you to the need for an additional(or relocated) lightweight access point.If clients on a lightweight access point are detected at threshold levels (RSSI, failed client count, percentageof failed packets, and number of failed packets) lower than those specified in the RRM configuration, theaccess point sends a “coverage hole”alert to the controller. The alert indicates the existence of an area whereclients are continually experiencing poor signal coverage, without having a viable access point to which toroam. The controller discriminates between coverage holes that can and cannot be corrected. For coverageholes that can be corrected, the controller mitigates the coverage hole by increasing the transmit power levelfor that specific access point. The controller does not mitigate coverage holes caused by clients that are unableto increase their transmit power or are statically set to a power level because increasing their downstreamtransmit power might increase interference in the network.Benefits of RRMRRM produces a network with optimal capacity, performance, and reliability. It frees you from having tocontinually monitor the network for noise and interference problems, which can be transient and difficult totroubleshoot. RRM ensures that clients enjoy a seamless, trouble-free connection throughout the Cisco unifiedwireless network.RRM uses separate monitoring and control for each deployed network: 802.11a and 802.11b/g. The RRMalgorithms run separately for each radio type (802.11a and 802.11b/g). RRM uses both measurements andalgorithms. RRM measurements can be adjusted using monitor intervals, but they cannot be disabled. RRMalgorithms are enabled automatically but can be disabled by statically configuring channel and powerassignment. The RRM algorithms run at a specified updated interval, which is 600 seconds by default.Information About Configuring RRMThe controller’s preconfigured RRM settings are optimized for most deployments. However, you can modifythe controller’s RRM configuration parameters at any time through either the GUI or the CLI.You can configure these parameters on controllers that are part of an RF group or on controllers that are notpart of an RF group.The RRM parameters should be set to the same values on every controller in an RF group. The RF groupleader can change as a result of controller reboots or depending on which radios hear each other. If the RRMparameters are not identical for all RF group members, varying results can occur when the group leaderchanges.Cisco Wireless LAN Controller Configuration Guide, Release 7.4       OL-28744-01 821Information About Radio Resource Management
Using the controller GUI, you can configure the following RRM parameters: RF group mode, transmit powercontrol, dynamic channel assignment, coverage hole detection, profile thresholds, monitoring channels, andmonitor intervals.Restrictions for Configuring RRM•The OEAP 600 series access points do not support RRM. The radios for the 600 series OEAP accesspoints are controlled through the local GUI of the 600 series access points and not through the CiscoWLC. Attempting to control the spectrum channel or power, or disabling the radios through the CiscoWLC will fail to have any effect on the 600 series OEAP.Configuring the RF Group Mode (GUI)Step 1 Choose Wireless >802.11a/n or 802.11b/g/n > RRM > RF Grouping to open the 802.11a (or 802.11b/g) RRM > RFGrouping page.Step 2 From the Group Mode drop-down list, select the mode you want to configure for this Cisco WLC.You can configure RF grouping in the following modes:•auto—Sets the RF group selection to automatic update mode.•leader—Sets the RF group selection to static mode, and sets this Cisco WLC as the group leader.•off—Sets the RF group selection off. Every Cisco WLC optimizes its own access point parameters.A configured static leader cannot become a member of another Cisco WLC until its mode is set to“auto”.NoteA Cisco WLC with a lower priority cannot assume the role of a group leader if a Cisco WLC with a higherpriority is available. Here priority is related to the processing power of the Cisco WLC.NoteWe recommend that Cisco WLCs participate in automatic RF grouping. You can override RRM settingswithout disabling automatic RF group participation.NoteStep 3 Click Apply to save the configuration and click Restart to restart RRM RF Grouping algorithm.Step 4 If you configured RF Grouping mode for this Cisco WLC as a static leader, you can add group members from the RFGroup Members section as follows:1In the Cisco WLC Name text box, enter the Cisco WLC that you want to add as a member to this group.2In the IP Address text box, enter the IP address of the Cisco WLC.3Click Add Member to add the member to this group.If the member has not joined the static leader, the reason of the failure is shown in parentheses.NoteStep 5 Click Apply.Step 6 Click Save Configuration.   Cisco Wireless LAN Controller Configuration Guide, Release 7.4822 OL-28744-01  Restrictions for Configuring RRM
Configuring the RF Group Mode (CLI)Step 1 Configure the RF Grouping mode by entering this command:config advanced {802.11a | 802.11b} group-mode {auto |leader|off |restart}•auto—Sets the RF group selection to automatic update mode.•leader—Sets the RF group selection to static mode, and sets this Cisco WLC as the group leader.•off—Sets the RF group selection off. Every Cisco WLC optimizes its own access point parameters.•restart—Restarts the RF group selection.A configured static leader cannot become a member of another Cisco WLC until its mode is set to“auto”.NoteA Cisco WLC with a lower priority cannot assume the role of a group leader if a Cisco WLC with higherpriority is available. Here priority is related to the processing power of the Cisco WLC.NoteStep 2 Add or remove a Cisco WLC as a static member of the RF group (if the mode is set to “leader”) by entering the thesecommands:•config advanced {802.11a | 802.11b} group-member add controller_name controller_ip_address•config advanced {802.11a | 802.11b} group-member remove controller_namecontroller_ip_addressStep 3 See RF grouping status by entering this command:show advanced {802.11a | 802.11b} groupConfiguring Transmit Power Control (GUI)Step 1 Choose Wireless >802.11a/n or 802.11b/g/n >RRM >TPC to open the 802.11a/n (or 802.11b/g/n) > RRM > Tx PowerControl (TPC) page.Step 2 Choose the Transmit Power Control version from the following options:•Interference Optimal Mode (TPCv2)—For scenarios where voice calls are extensively used. Transmit power isdynamically adjusted with the goal of minimum interference. It is suitable for dense networks. In this mode, therecould be higher roaming delays and coverage hole incidents.We recommend that you use TCPv2 only in cases where RF issues cannot be resolved by using TCPv1.Please evaluate and test the use of TPCv2 with the assistance of Cisco Services.Note•Coverage Optimal Mode (TPCv1)—(Default) Offers strong signal coverage and stability. In this mode, power canbe kept low to gain extra capacity and reduce interference.Cisco Wireless LAN Controller Configuration Guide, Release 7.4       OL-28744-01 823Configuring the RF Group Mode (CLI)
Step 3 Choose one of the following options from the Power Level Assignment Method drop-down list to specify the CiscoWLC’s dynamic power assignment mode:•Automatic—Causes the Cisco WLC to periodically evaluate and, if necessary, update the transmit power for alljoined access points. This is the default value.•On Demand—Causes the Cisco WLC to periodically evaluate the transmit power for all joined access points.However, the Cisco WLC updates the power, if necessary, only when you click Invoke Power Update Now.The Cisco WLC does not evaluate and update the transmit power immediately after you click InvokePower Update Now. It waits for the next 600-second interval. This value is not configurable.Note•Fixed—Prevents the Cisco WLC from evaluating and, if necessary, updating the transmit power for joined accesspoints. The power level is set to the fixed value chosen from the drop-down list.The transmit power level is assigned an integer value instead of a value in mW or dBm. The integercorresponds to a power level that varies depending on the regulatory domain, channel, and antennas inwhich the access points are deployed.NoteFor optimal performance, we recommend that you use the Automaticsetting.NoteStep 4 Enter the maximum and minimum power level assignment values in the Maximum Power Level Assignment and MinimumPower Level Assignment text boxes.The range for the Maximum Power Level Assignment is –10 to 30 dBm.The range for the Minimum Power Level Assignment is –10 to 30 dBm.Step 5 In the Power Threshold text box, enter the cutoff signal level used by RRM when determining whether to reduce anaccess point’s power. The default value for this parameter is –70 dBm for TPCv1 and –67 dBm for TPCv2, but can bechanged when access points are transmitting at higher (or lower) than desired power levels.The range for this parameter is –80 to –50 dBm. Increasing this value (between –65 and –50 dBm) causes the accesspoints to operate at a higher transmit power. Decreasing the value has the opposite effect.In applications with a dense population of access points, it may be useful to decrease the threshold to –80 or –75 dBmto reduce the number of BSSIDs (access points) and beacons seen by the wireless clients. Some wireless clients mighthave difficulty processing a large number of BSSIDs or a high beacon rate and might exhibit problematic behavior withthe default threshold.This page also shows the following nonconfigurable transmit power level parameter settings:•Power Neighbor Count—The minimum number of neighbors an access point must have for the transmit powercontrol algorithm to run.•Power Assignment Leader—The MAC address of the RF group leader, which is responsible for power levelassignment.•Last Power Level Assignment—The last time RRM evaluated the current transmit power level assignments.Step 6 Click Apply.Step 7 Click Save Configuration.   Cisco Wireless LAN Controller Configuration Guide, Release 7.4824 OL-28744-01  Configuring Transmit Power Control (GUI)
Configuring Off-Channel Scanning DeferInformation About Off-Channel Scanning DeferIn deployments with certain power-save clients, you sometimes need to defer the Radio Resource Management's(RRM) normal off-channel scanning to avoid missing critical information from low-volume clients (forexample, medical devices that use power-save mode and periodically send telemetry information). This featureimproves the way that Quality of Service (QoS) interacts with the RRM scan defer feature.You can use a client's Wi-Fi Multimedia (WMM) UP marking to configure the access point to defer off-channelscanning for a configurable period of time if it receives a packet marked UP.Off-Channel Scanning Defer is essential to the operation of RRM, which gathers information about alternatechannel choices such as noise and interference. Additionally, Off-Channel Scanning Defer is responsible forrogue detection. Devices that need to defer Off-Channel Scanning Defer should use the same WLAN as oftenas possible. If there are many of these devices (and the possibility exists that Off-Channel Defer scanningcould be completely disabled by the use of this feature), you should implement an alternative to local APOff-Channel Scanning Defer, such as monitoring access points, or other access points in the same locationthat do not have this WLAN assigned.You can assign a QoS policy (bronze, silver, gold, and platinum) to a WLAN to affect how packets are markedon the downlink connection from the access point regardless of how they were received on the uplink fromthe client. UP=1,2 is the lowest priority, and UP=0,3 is the next higher priority. The marking results of eachQoS policy are as follows:•Bronze marks all downlink traffic to UP= 1.•Silver marks all downlink traffic to UP= 0.•Gold marks all downlink traffic to UP=4.•Platinum marks all downlink traffic to UP=6.Configuring Off-Channel Scanning Defer for WLANsConfiguring Off-Channel Scanning Defer for a 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 configure off-channel scanning Defer.Step 3 Choose the Advanced tab from the WLANs > Edit page.Step 4 From the Off Channel Scanning Defer section, set the Scan Defer Priority by clicking on the priority argument.Step 5 Set the time in milliseconds in the Scan Defer Time text box.Valid values are 100 through 60000. The default value is 100 milliseconds.Step 6 Click Apply to save your configuration.Cisco Wireless LAN Controller Configuration Guide, Release 7.4       OL-28744-01 825Configuring Off-Channel Scanning Defer
Configuring Off Channel Scanning Defer for a WLAN (CLI)Step 1 Assign a defer-priority for the channel scan by entering this command:config wlan channel-scan defer-priority priority [enable | disable] WLAN-idThe valid range for the priority argument is 0 to 7.The priority is 0 to 7 (this value should be set to 6 on the client and on the WLAN).Use this command to configure the amount of time that scanning will be deferred following an UP packet in the queue.Step 2 Assign the channel scan defer time (in milliseconds) by entering this command:config wlan channel-scan defer-time msec WLAN-idThe time value is in miliseconds (ms) and the valid range is 100 (default) to 60000 (60 seconds). This setting shouldmatch the requirements of the equipment on your wireless LAN.You can also configure this feature on the Cisco WLC GUI by selecting WLANs, and either edit an existing WLAN orcreate a new one.Configuring Dynamic Channel Assignment (GUI)You can specify the channels that the dynamic channel assignment (DCA) algorithm considers when selectingthe channels to be used for RRM scanning by using the Cisco WLC GUI.This functionality is helpful when you know that the clients do not support certain channels because theyare legacy devices or they have certain regulatory restrictions.NoteStep 1 Disable the 802.11a/n or 802.11b/g/n network as follows:a) Choose Wireless >802.11a/n or 802.11b/g/n >Network to open the Global Parameters page.b) Unselect the 802.11a (or 802.11b/g)Network Status check box.c) Click Apply.Step 2 Choose Wireless >802.11a/n or 802.11b/g/n >RRM >DCA to open the Dynamic Channel Assignment (DCA) page.Step 3 Choose one of the following options from the Channel Assignment Method drop-down list to specify the Cisco WLC’sDCA mode:•Automatic—Causes the Cisco WLC to periodically evaluate and, if necessary, update the channel assignment forall joined access points. This is the default value.•Freeze—Causes the Cisco WLC to evaluate and update the channel assignment for all joined access points, ifnecessary, but only when you click Invoke Channel Update Once.The Cisco WLC does not evaluate and update the channel assignment immediately after you click InvokeChannel Update Once. It waits for the next interval to elapse.Note   Cisco Wireless LAN Controller Configuration Guide, Release 7.4826 OL-28744-01  Configuring Off-Channel Scanning Defer
•OFF—Turns off DCA and sets all access point radios to the first channel of the band, which is the default value.If you choose this option, you must manually assign channels on all radios.For optimal performance, we recommend that you use the Automatic setting. See the Disabling DynamicChannel and Power Assignment (GUI), on page 852 section for instructions on how to disable the CiscoWLC’s dynamic channel and power settings.NoteStep 4 From the Interval drop-down list, choose one of the following options to specify how often the DCA algorithm is allowedto run: 10 minutes,1 hour,2 hours,3 hours,4 hours,6 hours,8 hours,12 hours, or 24 hours. The default value is10 minutes.If your Cisco WLC supports only OfficeExtend access points, we recommend that you set the DCA interval to6 hours for optimal performance. For deployments with a combination of OfficeExtend access points and localaccess points, the range of 10 minutes to 24 hours can be used.NoteStep 5 From the AnchorTime drop-down list, choose a number to specify the time of day when the DCA algorithm is to start.The options are numbers between 0 and 23 (inclusive) representing the hour of the day from 12:00 a.m. to 11:00 p.m.Step 6 Select the Avoid Foreign AP Interference check box to cause the Cisco WLC’s RRM algorithms to consider 802.11traffic from foreign access points (those not included in your wireless network) when assigning channels to lightweightaccess points, or unselect it to disable this feature. For example, RRM may adjust the channel assignment to have accesspoints avoid channels close to foreign access points. The default value is selected.Step 7 Select the Avoid Cisco AP Load check box to cause the Cisco WLC’s RRM algorithms to consider 802.11 traffic fromCisco lightweight access points in your wireless network when assigning channels, or unselect it to disable this feature.For example, RRM can assign better reuse patterns to access points that carry a heavier traffic load. The default valueis unselected.Step 8 Select the Avoid Non-802.11a (802.11b) Noise check box to cause the Cisco WLC’s RRM algorithms to consider noise(non-802.11 traffic) in the channel when assigning channels to lightweight access points, or unselect it to disable thisfeature. For example, RRM may have access points avoid channels with significant interference from nonaccess pointsources, such as microwave ovens. The default value is selected.Step 9 Select the Avoid Persistent Non-WiFi Interference check box to enable the Cisco WLC to ignore persistent non-WiFiinterference.Step 10 From the DCA Channel Sensitivity drop-down list, choose one of the following options to specify how sensitive theDCA algorithm is to environmental changes such as signal, load, noise, and interference when determining whether tochange channels:•Low—The DCA algorithm is not particularly sensitive to environmental changes.•Medium—The DCA algorithm is moderately sensitive to environmental changes.•High—The DCA algorithm is highly sensitive to environmental changes.The default value is Medium. The DCA sensitivity thresholds vary by radio band, as noted in the table below.Table 24: DCA Sensitivity Thresholds5-GHz DCA Sensitivity Threshold2.4-GHz DCA Sensitivity ThresholdOption5 dB5 dBHigh15 dB10 dBMedium20 dB20 dBLowCisco Wireless LAN Controller Configuration Guide, Release 7.4       OL-28744-01 827Configuring Off-Channel Scanning Defer
Step 11 For 802.11a/n networks only, choose one of the following channel width options to specify the channel bandwidthsupported for all 802.11n radios in the 5-GHz band:•20 MHz—The 20-MHz channel bandwidth (default)•40 MHz—The 40-MHz channel bandwidthIf you choose 40 MHz, be sure to choose at least two adjacent channels from the DCA Channel List inStep 13 (for example, a primary channel of 36 and an extension channel of 40). If you choose only onechannel, that channel is not used for 40-MHz channel width.NoteIf you choose 40 MHz, you can also configure the primary and extension channels used by individualaccess points.NoteTo override the globally configured DCA channel width setting, you can statically configure an accesspoint’s radio for 20- or 40-MHz mode on the 802.11a/n Cisco APs > Configure page. if you then changethe static RF channel assignment method to WLC Controlled on the access point radio, the global DCAconfiguration overrides the channel width configuration that the access point was previously using. It cantake up to 30 minutes (depending on how often DCA is configured to run) for the change to take effect.NoteIf you choose 40 MHz on the A radio, you cannot pair channels 116, 140, and 165 with any other channels.NoteThis page also shows the following nonconfigurable channel parameter settings:•Channel Assignment Leader—The MAC address of the RF group leader, which is responsible for channel assignment.•Last Auto Channel Assignment—The last time RRM evaluated the current channel assignments.Step 12 Select the Avoid check for non-DFS channel to enable the Cisco WLC to avoid checks for non-DFS channels. DCAconfiguration requires at least one non-DFS channel in the list. In the EU countries, outdoor deployments do not supportnon-DFS channels. Customers based in EU or regions with similar regulations must enable this option or at least haveone non-DFS channel in the DCA list even if the channel is not supported by the APs.This parameter is applicable only for deployments having outdoor access points such as 1522 and1524.NoteStep 13 In the DCA Channel List area, the DCA Channels text box shows the channels that are currently selected. To choose achannel, select its check box in the Select column. To exclude a channel, unselect its check box.The ranges are as follows: 802.11a—36, 40, 44, 48, 52, 56, 60, 64, 100, 104, 108, 112, 116, 132, 136, 140, 149, 153,157, 161, 165, 190, 196 802.11b/g—1, 2, 3, 4, 5, 6, 7, 8, 9, 10, 11The defaults are as follows: 802.11a—36, 40, 44, 48, 52, 56, 60, 64, 100, 104, 108, 112, 116, 132, 136, 140, 149, 153,157, 161 802.11b/g—1, 6, 11These extended UNII-2 channels in the 802.11a band do not appear in the channel list: 100, 104, 108, 112, 116,132, 136, and 140. If you have Cisco Aironet 1520 series mesh access points in the -E regulatory domain, youmust include these channels in the DCA channel list before you start operation. If you are upgrading from aprevious release, verify that these channels are included in the DCA channel list. To include these channels inthe channel list, select the Extended UNII-2 Channels check box.NoteStep 14 If you are using Cisco Aironet 1520 series mesh access points in your network, you need to set the 4.9-GHz channels inthe 802.11a band on which they are to operate. The 4.9-GHz band is for public safety client access traffic only. To choosea 4.9-GHz channel, select its check box in the Select column. To exclude a channel, unselect its check box.The ranges are as follows: 802.11a—1, 2, 3, 4, 5, 6, 7, 8, 9, 10, 11, 12, 13, 14, 15, 16, 17, 18, 19, 20, 21, 22, 23, 24, 25,26The defaults are as follows: 802.11a—20, 26   Cisco Wireless LAN Controller Configuration Guide, Release 7.4828 OL-28744-01  Configuring Off-Channel Scanning Defer
Step 15 Click Apply.Step 16 Reenable the 802.11 networks as follows:1Choose Wireless >802.11a/n or 802.11b/g/n >Network to open the Global Parameters page.2Select the 802.11a (or 802.11b/g)Network Status check box.3Click Apply.Step 17 Click Save Configuration.To see why the DCA algorithm changed channels, choose Monitor and then choose View All under MostRecent Traps. The trap provides the MAC address of the radio that changed channels, the previous channel andthe new channel, the reason why the change occurred, the energy before and after the change, the noise beforeand after the change, and the interference before and after the change.NoteConfiguring Coverage Hole Detection (GUI)Step 1 Disable the 802.11 network as follows:a) Choose Wireless >802.11a/n or 802.11b/g/n >Network to open the 802.11a (or 802.11b/g) Global Parameterspage.b) Unselect the 802.11a (or 802.11b/g)Network Status check box.c) Click Apply.Step 2 Choose Wireless >802.11a/n or 802.11b/g/n >RRM >Coverage to open the 802.11a (or 802.11b/g/n) > RRM >Coverage page.Step 3 Select the Enable Coverage Hole Detection check box to enable coverage hole detection, or unselect it to disable thisfeature. If you enable coverage hole detection, the Cisco WLC automatically determines, based on data received fromthe access points, if any access points have clients that are potentially located in areas with poor coverage. The defaultvalue is selected.Step 4 In the Data RSSI text box, enter the minimum receive signal strength indication (RSSI) value for data packets receivedby the access point. The value that you enter is used to identify coverage holes (or areas of poor coverage) within yournetwork. If the access point receives a packet in the data queue with an RSSI value below the value that you enter here,a potential coverage hole has been detected. The valid range is –90 to –60 dBm, and the default value is –80 dBm. Theaccess point takes data RSSI measurements every 5 seconds and reports them to the Cisco WLC in 90-second intervals.Step 5 In the Voice RSSI text box, enter the minimum receive signal strength indication (RSSI) value for voice packets receivedby the access point. The value that you enter is used to identify coverage holes within your network. If the access pointreceives a packet in the voice queue with an RSSI value below the value that you enter here, a potential coverage holehas been detected. The valid range is –90 to –60 dBm, and the default value is –75 dBm. The access point takes voiceRSSI measurements every 5 seconds and reports them to the Cisco WLC in 90-second intervals.Step 6 In the Min Failed Client Count per AP text box, enter the minimum number of clients on an access point with an RSSIvalue at or below the data or voice RSSI threshold. The valid range is 1 to 75, and the default value is 3.Step 7 In the Coverage Exception Level per AP text box, enter the percentage of clients on an access point that are experiencinga low signal level but cannot roam to another access point. The valid range is 0 to 100%, and the default value is 25%.Cisco Wireless LAN Controller Configuration Guide, Release 7.4       OL-28744-01 829Configuring Off-Channel Scanning Defer
If both the number and percentage of failed packets exceed the values configured for Failed Packet Count andFailed Packet Percentage (configurable through the Cisco WLC CLI) for a 5-second period, the client is consideredto be in a pre-alarm condition. The Cisco WLC uses this information to distinguish between real and falsecoverage holes. False positives are generally due to the poor roaming logic implemented on most clients. Acoverage hole is detected if both the number and percentage of failed clients meet or exceed the values enteredin the Min Failed Client Count per AP and Coverage Exception Level per AP text boxes over a 90-secondperiod. The Cisco WLC determines if the coverage hole can be corrected and, if appropriate, mitigates thecoverage hole by increasing the transmit power level for that specific access point.NoteStep 8 Click Apply.Step 9 Reenable the 802.11 network as follows:a) Choose Wireless >802.11a/n or 802.11b/g/n >Network to open the 802.11a (or 802.11b/g) Global Parameterspage.b) Select the 802.11a (or 802.11b/g/n)Network Status check box.c) Click Apply.Step 10 Click Save Configuration.Configuring RRM Profile Thresholds, Monitoring Channels, and Monitor Intervals (GUI)Step 1 Choose Wireless >802.11a/n or 802.11b/g/n >RRM >General to open the 802.11a/n (or 802.11b/g/n) > RRM >General page.Step 2 Configure profile thresholds used for alarming as follows:The profile thresholds have no bearing on the functionality of the RRM algorithms. Lightweight access pointssend an SNMP trap (or an alert) to the Cisco WLC when the values set for these threshold parameters areexceeded.Notea) In the Interference text box, enter the percentage of interference (802.11 traffic from sources outside of your wirelessnetwork) on a single access point. The valid range is 0 to 100%, and the default value is 10%.b) In the Clients text box, enter the number of clients on a single access point. The valid range is 1 to 75, and the defaultvalue is 12.c) In the Noise text box, enter the level of noise (non-802.11 traffic) on a single access point. The valid range is –127to 0 dBm, and the default value is –70 dBm.d) In the Utilization text box, enter the percentage of RF bandwidth being used by a single access point. The valid rangeis 0 to 100%, and the default value is 80%.Step 3 From the Channel List drop-down list, choose one of the following options to specify the set of channels that the accesspoint uses for RRM scanning:•All Channels—RRM channel scanning occurs on all channels supported by the selected radio, which includeschannels not allowed in the country of operation.•Country Channels—RRM channel scanning occurs only on the data channels in the country of operation. This isthe default value.   Cisco Wireless LAN Controller Configuration Guide, Release 7.4830 OL-28744-01  Configuring Off-Channel Scanning Defer
•DCA Channels—RRM channel scanning occurs only on the channel set used by the DCA algorithm, which bydefault includes all of the non-overlapping channels allowed in the country of operation. However, you can specifythe channel set to be used by DCA if desired. To do so, follow instructions in the Dynamic Channel Assignment.Step 4 Configure monitor intervals as follows:1In the Channel Scan Interval text box, enter (in seconds) the sum of the time between scans for each channel withina radio band. The entire scanning process takes 50 ms per channel, per radio and runs at the interval configured here.The time spent listening on each channel is determined by the non-configurable 50-ms scan time and the number ofchannels to be scanned. For example, in the U.S. all 11 802.11b/g channels are scanned for 50 ms each within thedefault 180-second interval. So every 16 seconds, 50 ms is spent listening on each scanned channel (180/11 = ~16seconds). The Channel Scan Interval parameter determines the interval at which the scanning occurs.The valid rangeis 60 to 3600 seconds, and the default value is 60 seconds for 802.11a radios and 180 seconds for the 802.11b/gradios.If your Cisco WLC supports only OfficeExtend access points, we recommend that you set the channel scaninterval to 1800 seconds for optimal performance. For deployments with a combination of OfficeExtendaccess points and local access points, the range of 60 to 3600 seconds can be used.Note2In the Neighbor Packet Frequency text box, enter (in seconds) how frequently neighbor packets (messages) aresent, which eventually builds the neighbor list. The valid range is 60 to 3600 seconds, and the default value is 60seconds.If your Cisco WLC supports only OfficeExtend access points, we recommend that you set the neighborpacket frequency to 600 seconds for optimal performance. For deployments with a combination ofOfficeExtend access points and local access points, the range of 60 to 3600 seconds can be used.NoteIf the access point radio does not receive a neighbor packet from an existing neighbor within 60 minutes,the Cisco WLC deletes that neighbor from the neighbor list.NoteStep 5 Click Apply.Step 6 Click Save Configuration.Click Set to Factory Default if you want to return all of the Cisco WLC’s RRM parameters to their factory-defaultvalues.NoteConfiguring RRM (CLI)Step 1 Disable the 802.11 network by entering this command:config {802.11a |802.11b}disable networkStep 2 Choose the Transmit Power Control version by entering this command:config advanced {802.11a |802.11b}tpc-version {1|2}where:•TPCv1: Coverage-optimal—(Default) Offers strong signal coverage and stability with negligent intercell interferencesand sticky client syndrome.Cisco Wireless LAN Controller Configuration Guide, Release 7.4       OL-28744-01 831Configuring RRM (CLI)
•TPCv2: Interference-optimal—For scenarios where voice calls are extensively used. Tx power is dynamicallyadjusted with the goal of minimum interference. It is suitable for dense networks. In this mode, there can be higherroaming delays and coverage hole incidents.Step 3 Perform one of the following to configure transmit power control:•Have RRM automatically set the transmit power for all 802.11 radios at periodic intervals by entering this command:config {802.11a |802.11b}txPower global auto•Have RRM automatically reset the transmit power for all 802.11a or 802.11b/g radios one time by entering thiscommand:config {802.11a |802.11b}txPower global once•Configure the transmit power range that overrides the Transmit Power Control algorithm, use this command toenter the maximum and minimum transmit power used by RRM:config {802.11a |802.11b}txPower global {max |min}txpowerwhere txpower is a value from –10 to 30 dBM. The minimum value cannot be greater than the maximum value;the maximum value cannot be less than the minimum value.If you configure a maximum transmit power, RRM does not allow any access point to exceed this transmit power(whether the maximum is set at RRM startup, or by coverage hole detection). For example, if you configure amaximum transmit power of 11 dBm, then no access point would transmit above 11 dBm, unless the access pointis configured manually.•Manually change the default transmit power setting by entering this command:config advanced {802.11a |802.11b} {tpcv1-thresh |tpcv2-thresh}thresholdwhere threshold is a value from –80 to –50 dBm. Increasing this value causes the access points to operate at highertransmit power rates. Decreasing the value has the opposite effect.In applications with a dense population of access points, it may be useful to decrease the threshold to –80 or –75dBm in order to reduce the number of BSSIDs (access points) and beacons seen by the wireless clients. Somewireless clients may have difficulty processing a large number of BSSIDs or a high beacon rate and may exhibitproblematic behavior with the default threshold.•Configure the Transmit Power Control Version 2 on a per-channel basis by entering this command:config advanced {802.11a |802.11b}tpcv2-per-chan {enable |disable}Step 4 Perform one of the following to configure dynamic channel assignment (DCA):•Have RRM automatically configure all 802.11 channels based on availability and interference by entering thiscommand:config {802.11a |802.11b}channel global auto•Have RRM automatically reconfigure all 802.11 channels one time based on availability and interference by enteringthis command:config {802.11a |802.11b}channel global once•Disable RRM and set all channels to their default values by entering this command:config {802.11a |802.11b}channel global off   Cisco Wireless LAN Controller Configuration Guide, Release 7.4832 OL-28744-01  Configuring RRM (CLI)
•Restart aggressive DCA cycle by entering this command:config {802.11a |802.11b}channel global restart•To specify the channel set used for DCA by entering this command:config advanced {802.11a |802.11b}channel {add |delete}channel_numberYou can enter only one channel number per command. This command is helpful when you know that the clientsdo not support certain channels because they are legacy devices or they have certain regulatory restrictions.Step 5 Configure additional DCA parameters by entering these commands:•config advanced {802.11a |802.11b}channel dca anchor-time value—Specifies the time of day when the DCAalgorithm is to start. value is a number between 0 and 23 (inclusive) representing the hour of the day from 12:00a.m. to 11:00 p.m.•config advanced {802.11a |802.11b}channel dca interval value—Specifies how often the DCA algorithm isallowed to run. value is one of the following: 1, 2, 3, 4, 6, 8, 12, or 24 hours or 0, which is the default value of 10minutes (or 600 seconds).If your Cisco WLC supports only OfficeExtend access points, we recommend that you set the DCA intervalto 6 hours for optimal performance. For deployments with a combination of OfficeExtend access pointsand local access points, the range of 10 minutes to 24 hours can be used.Note•config advanced {802.11a |802.11b}channel dca sensitivity {low |medium |high}—Specifies how sensitivethe DCA algorithm is to environmental changes such as signal, load, noise, and interference when determiningwhether to change channel.◦low means that the DCA algorithm is not particularly sensitive to environmental changes.◦medium means that the DCA algorithm is moderately sensitive to environmental changes.◦high means that the DCA algorithm is highly sensitive to environmental changes.The DCA sensitivity thresholds vary by radio band, as noted in following table.Table 25: DCA Sensitivity Thresholds5-GHz DCA Sensitivity Threshold2.4-GHz DCA Sensitivity ThresholdOption5 dB5 dBHigh15 dB10 dBMedium20 dB20 dBLow•config advanced 802.11a channel dca chan-width-11n {20 |40}—Configures the DCA channel width for all802.11n radios in the 5-GHz band.where◦20 sets the channel width for 802.11n radios to 20 MHz. This is the default value.◦40 sets the channel width for 802.11n radios to 40 MHz.Cisco Wireless LAN Controller Configuration Guide, Release 7.4       OL-28744-01 833Configuring RRM (CLI)
If you choose 40, be sure to set at least two adjacent channels in the config advanced 802.11achannel {add |delete}channel_number command in Step 4 (for example, a primary channel of 36and an extension channel of 40). If you set only one channel, that channel is not used for 40-MHzchannel width.NoteIf you choose 40, you can also configure the primary and extension channels used by individualaccess points.NoteTo override the globally configured DCA channel width setting, you can statically configure anaccess point’s radio for 20-MHz or 40-MHz mode using the config 802.11a chan_width Cisco_AP{20 |40} command. If you change the static configuration to global on the access point radio, theglobal DCA configuration overrides the channel width configuration that the access point waspreviously using. It can take up to 30 minutes (depending on how often DCA is configured to run)for the change to take effect.Note•config advanced {802.11a | 802.11b} channel outdoor-ap-dca {enable |disable}—Enables or disables to theCisco WLC to avoid checks for non-DFS channels.This parameter is applicable only for deployments having outdoor access points such as 1522 and1524.Note•config advanced {802.11a |802.11b}channel foreign {enable |disable}—Enables or disables foreign accesspoint interference avoidance in the channel assignment.•config advanced {802.11a |802.11b}channel load {enable |disable}—Enables or disables load avoidance inthe channel assignment.•config advanced {802.11a |802.11b}channel noise {enable |disable}—Enables or disables noise avoidance inthe channel assignment.•config advanced {802.11a |802.11b}channel update—Initiates an update of the channel selection for everyCisco access point.Step 6 Configure coverage hole detection by entering these commands:In Cisco WLC software release 5.2 or later releases, you can disable coverage hole detection on a per-WLANbasis.Note•config advanced {802.11a |802.11b}coverage {enable |disable}—Enables or disables coverage hole detection.If you enable coverage hole detection, the Cisco WLC automatically determines, based on data received from theaccess points, if any access points have clients that are potentially located in areas with poor coverage. The defaultvalue is enabled.•config advanced {802.11a |802.11b}coverage {data |voice}rssi-threshold rssi—Specifies the minimum receivesignal strength indication (RSSI) value for packets received by the access point. The value that you enter is usedto identify coverage holes (or areas of poor coverage) within your network. If the access point receives a packet inthe data or voice queue with an RSSI value below the value you enter here, a potential coverage hole has beendetected. The valid range is –90 to –60 dBm, and the default value is –80 dBm for data packets and –75 dBm forvoice packets. The access point takes RSSI measurements every 5 seconds and reports them to the Cisco WLC in90-second intervals.•config advanced {802.11a |802.11b}coverage level global clients—Specifies the minimum number of clientson an access point with an RSSI value at or below the data or voice RSSI threshold. The valid range is 1 to 75, andthe default value is 3.   Cisco Wireless LAN Controller Configuration Guide, Release 7.4834 OL-28744-01  Configuring RRM (CLI)
•config advanced {802.11a |802.11b}coverage exception global percent—Specifies the percentage of clients onan access point that are experiencing a low signal level but cannot roam to another access point. The valid rangeis 0 to 100%, and the default value is 25%.•config advanced {802.11a |802.11b}coverage {data |voice}packet-count packets—Specifies the minimumfailure count threshold for uplink data or voice packets. The valid range is 1 to 255 packets, and the default valueis 10 packets.•config advanced {802.11a |802.11b}coverage {data |voice}fail-rate percent—Specifies the failure rate thresholdfor uplink data or voice packets. The valid range is 1 to 100%, and the default value is 20%.If both the number and percentage of failed packets exceed the values entered in the packet-count andfail-rate commands for a 5-second period, the client is considered to be in a pre-alarm condition. TheCisco WLC uses this information to distinguish between real and false coverage holes. False positives aregenerally due to the poor roaming logic implemented on most clients. A coverage hole is detected if boththe number and percentage of failed clients meet or exceed the values entered in the coverage level globaland coverage exception global commands over a 90-second period. The Cisco WLC determines if thecoverage hole can be corrected and, if appropriate, mitigates the coverage hole by increasing the transmitpower level for that specific access point.NoteStep 7 Enable the 802.11a or 802.11b/g network by entering this command:config {802.11a |802.11b}enable networkTo enable the 802.11g network, enter config 802.11b 11gSupport enable after the config 802.11b enablenetwork command.NoteStep 8 Save your settings by entering this command:save configViewing RRM Settings (CLI)To see 802.11a and 802.11b/g RRM settings, use these commands:show advanced {802.11a |802.11b} ?where ? is one of the following:•ccx {global |Cisco_AP}—Shows the CCX RRM configuration.•channel—Shows the channel assignment configuration and statistics.•coverage—Shows the coverage hole detection configuration and statistics.•logging—Shows the RF event and performance logging.•monitor—Shows the Cisco radio monitoring.•profile {global |Cisco_AP}—Shows the access point performance profiles.•receiver—Shows the 802.11a or 802.11b/g receiver configuration and statistics.•summary—Shows the configuration and statistics of the 802.11a or 802.11b/g access points.•txpower—Shows the transmit power assignment configuration and statistics.Cisco Wireless LAN Controller Configuration Guide, Release 7.4       OL-28744-01 835Viewing RRM Settings (CLI)
Debug RRM Issues (CLI)Use these commands to troubleshoot and verify RRM behavior:debug airewave-director ?where ?is one of the following:•all—Enables debugging for all RRM logs.•channel—Enables debugging for the RRM channel assignment protocol.•detail—Enables debugging for RRM detail logs.•error—Enables debugging for RRM error logs.•group—Enables debugging for the RRM grouping protocol.•manager—Enables debugging for the RRM manager.•message—Enables debugging for RRM messages.•packet—Enables debugging for RRM packets.•power—Enables debugging for the RRM power assignment protocol as well as coverage hole detection.•profile—Enables debugging for RRM profile events.•radar—Enables debugging for the RRM radar detection/avoidance protocol.•rf-change—Enables debugging for RRM RF changes.   Cisco Wireless LAN Controller Configuration Guide, Release 7.4836 OL-28744-01  Debug RRM Issues (CLI)
CHAPTER 128Configuring RRM Neighbor Discovery Packets•Information About RRM NDP and RF Grouping, page 837•Configuring RRM NDP (CLI), page 837Information About RRM NDP and RF GroupingThe Cisco Neighbor Discovery Packet (NDP) is the fundamental tool for RRM and other wireless applicationsthat provides information about the neighbor radio information. You can configure the Cisco WLC to encryptneighbor discovery packets.This feature enables you to be compliant with the PCI specifications.An RF group can only be formed between Cisco WLCs that have the same encryption mechanism. That is,an access point associated to a Cisco WLC that is encrypted can not be neighbors with an access point associatedto a Cisco WLC that is not encrypted. The two Cisco WLCs and their access points will not recognize eachother as neighbors and cannot form an RF group. It is possible to assign two Cisco WLCs in a static RF groupconfiguration that has mismatched encryption settings. In this case, the two Cisco WLCs do not function asa single RF group because the access points belonging to the mismatched Cisco WLCs do not recognize oneanother as neighbors in the group.Configuring RRM NDP (CLI)To configure RRM NDP using the Cisco WLC CLI, enter this command:config advanced 802.11{a|b}monitor ndp-mode {protected |transparent}This command configures NDP mode. By default, the mode is set to “transparent”. The following options areavailable:•Protected—Packets are encrypted.•Transparent—Packets are sent as is.Use this command to see the discovery type:show advanced 802.11{a|b}monitorCisco Wireless LAN Controller Configuration Guide, Release 7.4        OL-28744-01 837
   Cisco Wireless LAN Controller Configuration Guide, Release 7.4838 OL-28744-01  Configuring RRM NDP (CLI)
CHAPTER 129Configuring RF Groups•Information About RF Groups, page 839•Configuring RF Groups, page 841•Viewing the RF Group Status, page 842•Configuring Rogue Access Point Detection in RF Groups, page 843Information About RF GroupsAn RF group is a logical collection of Cisco WLCs that coordinate to perform RRM in a globally optimizedmanner to perform network calculations on a per-radio basis. An RF group exists for each 802.11 networktype. Clustering Cisco WLCs into a single RF group enable the RRM algorithms to scale beyond the capabilitiesof a single Cisco WLC.RF group is created based on following parameters:•User-configured RF network name.•Neighbor discovery performed at the radio level.•Country list configured on MC.RF grouping runs between MCs.Lightweight access points periodically send out neighbor messages over the air. Access points using the thesame RF group name validate messages from each other.When access points on different Cisco WLCs hear validated neighbor messages at a signal strength of –80dBm or stronger, the Cisco WLCs dynamically form an RF neighborhood in auto mode. In static mode, theleader is manually selected and the members are added to the RF Group. To know more about RF Groupmodes, RF Group Leader.RF groups and mobility groups are similar in that they both define clusters of Cisco WLCs, but they aredifferent in terms of their use. An RF group facilitates scalable, system-wide dynamic RF managementwhile a mobility group facilitates scalable, system-wide mobility and Cisco WLC redundancy.NoteCisco Wireless LAN Controller Configuration Guide, Release 7.4        OL-28744-01 839
RF Group LeaderStarting in the 7.0.116.0 release, the RF Group Leader can be configured in two ways as follows:•Auto Mode—In this mode, the members of an RF group elect an RF group leader to maintain a “master”power and channel scheme for the group. The RF grouping algorithm dynamically chooses the RF groupleader and ensures that an RF group leader is always present. Group leader assignments can and dochange (for instance, if the current RF group leader becomes inoperable or if RF group membersexperience major changes).•Static Mode—In this mode, the user selects a Cisco WLC as an RF group leader manually. In this mode,the leader and the members are manually configured and are therefore fixed. If the members are unableto join the RF group, the reason is indicated. The leader tries to establish a connection with a memberevery 1 minute if the member has not joined in the previous attempt.The RF group leader analyzes real-time radio data collected by the system, calculates the power and channelassignments, and sends them to each of the Cisco WLCs in the RF group. The RRM algorithms ensuresystem-wide stability and restrain channel and power scheme changes to the appropriate local RFneighborhoods.In Cisco WLC software releases prior to 6.0, the dynamic channel assignment (DCA) search algorithm attemptsto find a good channel plan for the radios associated to Cisco WLCs in the RF group, but it does not adopt anew channel plan unless it is considerably better than the current plan. The channel metric of the worst radioin both plans determines which plan is adopted. Using the worst-performing radio as the single criterion foradopting a new channel plan can result in pinning or cascading problems.Pinning occurs when the algorithm could find a better channel plan for some of the radios in an RF group butis prevented from pursuing such a channel plan change because the worst radio in the network does not haveany better channel options. The worst radio in the RF group could potentially prevent other radios in the groupfrom seeking better channel plans. The larger the network, the more likely pinning becomes.Cascading occurs when one radio’s channel change results in successive channel changes to optimize theremaining radios in the RF neighborhood. Optimizing these radios could lead to their neighbors and theirneighbors’neighbors having a suboptimal channel plan and triggering their channel optimization. This effectcould propagate across multiple floors or even multiple buildings, if all the access point radios belong to thesame RF group. This change results in considerable client confusion and network instability.The main cause of both pinning and cascading is the way in which the search for a new channel plan isperformed and that any potential channel plan changes are controlled by the RF circumstances of a singleradio. In Cisco WLC software release 6.0, the DCA algorithm has been redesigned to prevent both pinningand cascading. The following changes have been implemented:•Multiple local searches—The DCA search algorithm performs multiple local searches initiated bydifferent radios within the same DCA run rather than performing a single global search driven by asingle radio. This change addresses both pinning and cascading while maintaining the desired flexibilityand adaptability of DCA and without jeopardizing stability.•Multiple channel plan change initiators (CPCIs)—Previously, the single worst radio was the sole initiatorof a channel plan change. Now each radio within the RF group is evaluated and prioritized as a potentialinitiator. Intelligent randomization of the resulting list ensures that every radio is eventually evaluated,which eliminates the potential for pinning.•Limiting the propagation of channel plan changes (Localization)—For each CPCI radio, the DCAalgorithm performs a local search for a better channel plan, but only the CPCI radio itself and its one-hopneighboring access points are actually allowed to change their current transmit channels. The impact of   Cisco Wireless LAN Controller Configuration Guide, Release 7.4840 OL-28744-01  Information About RF Groups
an access point triggering a channel plan change is felt only to within two RF hops from that accesspoint, and the actual channel plan changes are confined to within a one-hop RF neighborhood. Becausethis limitation applies across all CPCI radios, cascading cannot occur.•Non-RSSI-based cumulative cost metric—A cumulative cost metric measures how well an entire region,neighborhood, or network performs with respect to a given channel plan. The individual cost metrics ofall access points in that area are considered in order to provide an overall understanding of the channelplan’s quality. These metrics ensure that the improvement or deterioration of each single radio is factoredinto any channel plan change. The objective is to prevent channel plan changes in which a single radioimproves but at the expense of multiple other radios experiencing a considerable performance decline.The RRM algorithms run at a specified updated interval, which is 600 seconds by default. Between updateintervals, the RF group leader sends keepalive messages to each of the RF group members and collects real-timeRF data.Several monitoring intervals are also available. See the Configuring RRM section for details.NoteRF Group NameA Cisco WLC is configured with an RF group name, which is sent to all access points joined to the CiscoWLC and used by the access points as the shared secret for generating the hashed MIC in the neighbormessages. To create an RF group, you configure all of the Cisco WLCs to be included in the group with thesame RF group name.If there is any possibility that an access point joined to a Cisco WLC may hear RF transmissions from anaccess point on a different Cisco WLC, you should configure the Cisco WLCs with the same RF group name.If RF transmissions between access points can be heard, then system-wide RRM is recommended to avoid802.11 interference and contention as much as possible.Configuring RF GroupsThis section describes how to configure RF groups through either the GUI or the CLI.The RF group name is generally set at deployment time through the Startup Wizard. However, you canchange it as necessary.NoteWhen the multiple-country feature is being used, all Cisco WLCs intended to join the same RF groupmust be configured with the same set of countries, configured in the same order.NoteYou can also configure RF groups using the Cisco Prime Infrastructure.NoteCisco Wireless LAN Controller Configuration Guide, Release 7.4       OL-28744-01 841Configuring RF Groups
Configuring an RF Group Name (GUI)Step 1 Choose Controller >General to open the General page.Step 2 Enter a name for the RF group in the RF-Network Name text box. The name can contain up to 19 ASCII characters.Step 3 Click Apply to commit your changes.Step 4 Click Save Configuration to save your changes.Step 5 Repeat this procedure for each controller that you want to include in the RF group.Configuring an RF Group Name (CLI)Step 1 Create an RF group by entering the config network rf-network-name name command:Enter up to 19 ASCII characters for the groupname.NoteStep 2 See the RF group by entering the show network command.Step 3 Save your settings by entering the save config command.Step 4 Repeat this procedure for each controller that you want to include in the RF group.Viewing the RF Group StatusThis section describes how to view the status of the RF group through either the GUI or the CLI.You can also view the status of RF groups using the Cisco Prime Infrastructure.NoteViewing the RF Group Status (GUI)Step 1 Choose Wireless >802.11a/n >or 802.11b/g/n > RRM >RF Grouping to open the 802.11a/n (or 802.11b/g/n) RRM> RF Grouping page.This page shows the details of the RF group, displaying the configurable parameter RF Group mode, the RF Grouprole of this Cisco WLC, the Update Interval and the Cisco WLC name and IP address of the Group Leader to thisCisco WLC.   Cisco Wireless LAN Controller Configuration Guide, Release 7.4842 OL-28744-01  Viewing the RF Group Status
RF grouping mode can be set using the Group Mode drop-down list.Tip Once a Cisco WLC has joined as a static member and you want to change the grouping mode, we recommendthat you remove the member from the configured static-leader and also make sure that a member Cisco WLChas not been configured to be a member on multiple static leaders. This is to avoid repeated join attempts fromone or more RF static leaders.NoteStep 2 (Optional) Repeat this procedure for the network type that you did not select (802.11a/n or 802.11b/g/n).Viewing the RF Group Status (CLI)Step 1 See which Cisco WLC is the RF group leader for the 802.11a RF network by entering this command:show advanced 802.11a groupInformation similar to the following appears:Radio RF Grouping802.11a Group Mode............................. STATIC802.11a Group Update Interval.................. 600 seconds802.11a Group Leader........................... test (209.165.200.225)802.11a Group Member......................... test (209.165.200.225)802.11a Last Run............................... 397 seconds agoThis output shows the details of the RF group, specifically the grouping mode for the Cisco WLC, how often the groupinformation is updated (600 seconds by default), the IP address of the RF group leader, the IP address of this Cisco WLC,and the last time the group information was updated.If the IP addresses of the group leader and the group member are identical, this Cisco WLC is currently thegroup leader.NoteA * indicates that the Cisco WLC has not joined as a staticmember.NoteStep 2 See which Cisco WLC is the RF group leader for the 802.11b/g RF network by entering this command:show advanced 802.11b groupConfiguring Rogue Access Point Detection in RF GroupsInformation About Rogue Access Point Detection in RF GroupsAfter you have created an RF group of Cisco WLCs, you need to configure the access points connected tothe Cisco WLCs to detect rogue access points. The access points will then select the beacon/probe-responseframes in neighboring access point messages to see if they contain an authentication information element (IE)that matches that of the RF group. If the select is successful, the frames are authenticated. Otherwise, theauthorized access point reports the neighboring access point as a rogue, records its BSSID in a rogue table,and sends the table to the Cisco WLC.Cisco Wireless LAN Controller Configuration Guide, Release 7.4       OL-28744-01 843Configuring Rogue Access Point Detection in RF Groups
Configuring Rogue Access Point Detection in RF GroupsEnabling Rogue Access Point Detection in RF Groups (GUI)Step 1 Make sure that each Cisco WLC in the RF group has been configured with the same RF group name.The name is used to verify the authentication IE in all beacon frames. If the Cisco WLCs have different names,false alarms will occur.NoteStep 2 Choose Wireless to open the All APs page.Step 3 Click the name of an access point to open the All APs > Details page.Step 4 Choose either local or monitor from the AP Mode drop-down list and click Apply to commit your changes.Step 5 Click Save Configuration to save your changes.Step 6 Repeat Step 2 through Step 5 for every access point connected to the Cisco WLC.Step 7 Choose Security >Wireless Protection Policies >AP Authentication/MFP to open the AP Authentication Policypage.The name of the RF group to which this Cisco WLC belongs appears at the top of the page.Step 8 Choose AP Authentication from the Protection Type drop-down list to enable rogue access point detection.Step 9 Enter a number in the Alarm Trigger Threshold edit box to specify when a rogue access point alarm is generated. Analarm occurs when the threshold value (which specifies the number of access point frames with an invalid authenticationIE) is met or exceeded within the detection period.The valid threshold range is from1 to 255, and the default threshold value is 1. To avoid false alarms, you maywant to set the threshold to a higher value.NoteStep 10 Click Apply to commit your changes.Step 11 Click Save Configuration to save your changes.Step 12 Repeat this procedure on every Cisco WLC in the RF group.If rogue access point detection is not enabled on every Cisco WLC in the RF group, the access points on theCisco WLCs with this feature disabled are reported as rogues.NoteConfiguring Rogue Access Point Detection in RF Groups (CLI)Step 1 Make sure that each Cisco WLC in the RF group has been configured with the same RF group name.The name is used to verify the authentication IE in all beacon frames. If the Cisco WLCs have different names,false alarms will occur.NoteStep 2 Configure a particular access point for local (normal) mode or monitor (listen-only) mode by entering this command:config ap mode local Cisco_AP or config ap mode monitor Cisco_APStep 3 Save your changes by entering this command:save configStep 4 Repeat Step 2 and Step 3 for every access point connected to the Cisco WLC.Step 5 Enable rogue access point detection by entering this command:   Cisco Wireless LAN Controller Configuration Guide, Release 7.4844 OL-28744-01  Configuring Rogue Access Point Detection in RF Groups
config wps ap-authenticationStep 6 Specify when a rogue access point alarm is generated by entering this command. An alarm occurs when the thresholdvalue (which specifies the number of access point frames with an invalid authentication IE) is met or exceeded withinthe detection period.config wps ap-authentication thresholdThe valid threshold range is from 1 to 255, and the default threshold value is 1. To avoid false alarms, you maywant to set the threshold to a higher value.NoteStep 7 Save your changes by entering this command:save configStep 8 Repeat Step 5 through Step 7 on every Cisco WLC in the RF group.If rogue access point detection is not enabled on every Cisco WLC in the RF group, the access points on theCisco WLCs with this feature disabled are reported as rogues.NoteCisco Wireless LAN Controller Configuration Guide, Release 7.4       OL-28744-01 845Configuring Rogue Access Point Detection in RF Groups
   Cisco Wireless LAN Controller Configuration Guide, Release 7.4846 OL-28744-01  Configuring Rogue Access Point Detection in RF Groups
CHAPTER 130Overriding RRM•Information About Overriding RRM, page 847•Prerequisites for Overriding RRM, page 847•Statically Assigning Channel and Transmit Power Settings to Access Point Radios, page 848•Disabling Dynamic Channel and Power Assignment Globally for a Cisco Wireless LAN Controller,page 852Information About Overriding RRMIn some deployments, it is desirable to statically assign channel and transmit power settings to the accesspoints instead of relying on the RRM algorithms provided by Cisco. Typically, this is true in challenging RFenvironments and non standard deployments but not the more typical carpeted offices.If you choose to statically assign channels and power levels to your access points and/or to disable dynamicchannel and power assignment, you should still use automatic RF grouping to avoid spurious rogue deviceevents.NoteYou can disable dynamic channel and power assignment globally for a Cisco WLC, or you can leave dynamicchannel and power assignment enabled and statically configure specific access point radios with a channeland power setting. While you can specify a global default transmit power parameter for each network typethat applies to all the access point radios on a Cisco WLC, you must set the channel for each access pointradio when you disable dynamic channel assignment. You may also want to set the transmit power for eachaccess point instead of leaving the global transmit power in effect.Prerequisites for Overriding RRMWe recommend that you assign different nonoverlapping channels to access points that are within closeproximity to each other. The nonoverlapping channels in the U.S. are 36, 40, 44, 48, 52, 56, 60, 64, 149, 153,157, and 161 in an 802.11a network and 1, 6, and 11 in an 802.11b/g network.Cisco Wireless LAN Controller Configuration Guide, Release 7.4        OL-28744-01 847
Statically Assigning Channel and Transmit Power Settings to Access PointRadiosStatically Assigning Channel and Transmit Power Settings (GUI)Step 1 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.This page shows all the 802.11a/n or 802.11b/g/n access point radios that are joined to the Cisco WLC and their currentsettings. The Channel text box shows both the primary and extension channels and uses an asterisk to indicate if theyare globally assigned.Step 2 Hover your cursor over the blue drop-down arrow for the access point for which you want to modify the radio configurationand choose Configure. The 802.11a/n (or 802.11b/g/n) Cisco APs > Configure page appears.Step 3 Specify the RF Channel Assignment from the following options:•Global—Choose this to specify a global value.•Custom—Choose this and then select a value from the adjacent drop-down list to specify a custom value.Step 4 Configure the antenna parameters for this radio as follows:1From the Antenna Type drop-down list, choose Internal or External to specify the type of antennas used with theaccess point radio.2Select and unselect the check boxes in the Antenna text box to enable and disable the use of specific antennas forthis access point, where A, B, and C are specific antenna ports. The D antenna appears for the Cisco 3600 SeriesAccess Points. A is the right antenna port, B is the left antenna port, and C is the center antenna port. For example,to enable transmissions from antenna ports A and B and receptions from antenna port C, you would select the followingcheck boxes: Tx: A and B and Rx: C. In 3600 APs, the valid combinations are A, A+B, A+B+C or A+B+C+D. Whenyou select a dual mode antenna, you can only apply single spatial 802.11n stream rates: MCS 0 to 7 data rates. Whenyou select two dual mode antennae, you can apply only the two spatial 802.11n stream rates: MCS 0 to 15 data rates.3In the Antenna Gain text box, enter a number to specify an external antenna’s ability to direct or focus radio energyover a region of space. High-gain antennas have a more focused radiation pattern in a specific direction. The antennagain is measured in 0.5 dBi units, and the default value is 7 times 0.5 dBi, or 3.5 dBi.If you have a high-gain antenna, enter a value that is twice the actual dBi value (see Cisco Aironet Antenna ReferenceGuide for antenna dBi values). Otherwise, enter 0. For example, if your antenna has a 4.4-dBi gain, multiply the 4.4dBi by 2 to get 8.8 and then round down to enter only the whole number (8). The Cisco WLC reduces the actualequivalent isotropic radiated power (EIRP) to make sure that the antenna does not violate your country’s regulations.4Choose one of the following options from the Diversity drop-down list:Enabled—Enables the antenna connectors on both sides of the access point. This is the default value.Side A or Right—Enables the antenna connector on the right side of the access point.Side B or Left—Enables the antenna connector on the left side of the access point.   Cisco Wireless LAN Controller Configuration Guide, Release 7.4848 OL-28744-01  Statically Assigning Channel and Transmit Power Settings to Access Point Radios
Step 5 In the RF Channel Assignment area, choose Custom for the Assignment Method under RF Channel Assignment andchoose a channel from the drop-down list to assign an RF channel to the access point radio.Step 6 In the Tx Power Level Assignment area, choose the Custom assignment method and choose a transmit power level fromthe drop-down list to assign a transmit power level to the access point radio.The transmit power level is assigned an integer value instead of a value in mW or dBm. The integer corresponds to apower level that varies depending on the regulatory domain in which the access points are deployed. The number ofavailable power levels varies based on the access point model. However, power level 1 is always the maximum powerlevel allowed per country code setting, with each successive power level representing 50% of the previous power level.For example, 1 = maximum power level in a particular regulatory domain, 2 = 50% power, 3 = 25% power, 4 = 12.5%power, and so on.See the hardware installation guide for your access point for the maximum transmit power levels supported perregulatory domain. Also, see the data sheet for your access point for the number of power levels supported.NoteIf the access point is not operating at full power, the “Due to low PoE, radio is transmitting at degraded power”message appears under the Tx Power Level Assignment section.NoteStep 7 Choose Enable from the Admin Status drop-down list to enable this configuration for the access point.Step 8 Click Apply.Step 9 Have the Cisco WLC send the access point radio admin state immediately to Cisco Prime Infrastructure as follows:1Choose Wireless > 802.11a/n or 802.11b/g/n > Network to open the 802.11a (or 802.11b/g) Global Parameterspage.2Select the 802.11a (or 802.11b/g)Network Status check box.3Click Apply.Step 10 Click Save Configuration.Step 11 Repeat this procedure for each access point radio for which you want to assign a static channel and power level.Statically Assigning Channel and Transmit Power Settings (CLI)Step 1 Disable the radio of a particular access point on the 802.11a/n or 802.11b/g/n network by entering this command:config {802.11a |802.11b}disable Cisco_APStep 2 Configure the channel width for a particular access point by entering this command:config {802.11a |802.11b}chan_width Cisco_AP {20 |40}where•20 allows the radio to communicate using only 20-MHz channels. Choose this option for legacy 802.11a radios,20-MHz 802.11n radios, or 40-MHz 802.11n radios that you want to operate using only 20-MHz channels. Thisis the default value.•40 allows 40-MHz 802.11n radios to communicate using two adjacent 20-MHz channels bonded together. Theradio uses the primary channel that you choose as well as its extension channel for faster throughput. Each channelhas only one extension channel (36 and 40 are a pair, 44 and 48 are a pair, and so on). For example, if you chooseCisco Wireless LAN Controller Configuration Guide, Release 7.4       OL-28744-01 849Statically Assigning Channel and Transmit Power Settings to Access Point Radios
a primary channel of 44, the Cisco WLC would use channel 48 as the extension channel. If you choose a primarychannel of 48, the Cisco WLC would use channel 44 as the extension channel.This parameter can be configured only if the primary channel is statically assigned.NoteStatically configuring an access point’s radio for 20-MHz or 40-MHz mode overrides the globally configuredDCA channel width setting (configured using the config advanced 802.11a channel dca chan-width-11n{20 |40} command). If you ever change the static configuration back to global on the access point radio,the global DCA configuration overrides the channel width configuration that the access point was previouslyusing. It can take up to 30 minutes (depending on how often DCA is configured to run) for the change totake effect.NoteChannels 116, 120, 124, and 128 are not available in the U.S. and Canada for 40-MHz channel bonding.NoteStep 3 Enable or disable the use of specific antennas for a particular access point by entering this command:config {802.11a |802.11b}11nsupport antenna {tx |rx}Cisco_AP {A|B|C} {enable |disable}where A, B, and C are antenna ports. A is the right antenna port, B is the left antenna port, and C is the center antennaport. For example, to enable transmissions from the antenna in access point AP1’s antenna port C on the 802.11a network,you would enter this command:config 802.11a 11nsupport antenna tx AP1 C enableStep 4 Specify the external antenna gain, which is a measure of an external antenna’s ability to direct or focus radio energy overa region of space entering this command:config {802.11a |802.11b}antenna extAntGain antenna_gain Cisco_APHigh-gain antennas have a more focused radiation pattern in a specific direction. The antenna gain is measured in 0.5dBi units, and the default value is 7 times 0.5 dBi, or 3.5 dBi.If you have a high-gain antenna, enter a value that is twice the actual dBi value (see Cisco Aironet Antenna ReferenceGuide for antenna dBi values). Otherwise, enter 0. For example, if your antenna has a 4.4-dBi gain, multiply the 4.4 dBiby 2 to get 8.8 and then round down to enter only the whole number (8). The Cisco WLC reduces the actual equivalentisotropic radiated power (EIRP) to make sure that the antenna does not violate your country’s regulations.Step 5 Specify the channel that a particular access point is to use by entering this command:config {802.11a |802.11b}channel ap Cisco_AP channelFor example, to configure 802.11a channel 36 as the default channel on AP1, enter the config 802.11a channel ap AP136 command.The channel you choose is the primary channel (for example, channel 36), which is used for communication by legacy802.11a radios and 802.11n 20-MHz radios. 802.11n 40-MHz radios use this channel as the primary channel but alsouse an additional bonded extension channel for faster throughput, if you chose 40 for the channel width.Changing the operating channel causes the access point radio toreset.NoteStep 6 Specify the transmit power level that a particular access point is to use by entering this command:config {802.11a |802.11b}txPower ap Cisco_AP power_levelFor example, to set the transmit power for 802.11a AP1 to power level 2, enter the config 802.11a txPower ap AP1 2command.The transmit power level is assigned an integer value instead of a value in mW or dBm. The integer corresponds to apower level that varies depending on the regulatory domain in which the access points are deployed. The number ofavailable power levels varies based on the access point model. However, power level 1 is always the maximum powerlevel allowed per country code setting, with each successive power level representing 50% of the previous power level.   Cisco Wireless LAN Controller Configuration Guide, Release 7.4850 OL-28744-01  Statically Assigning Channel and Transmit Power Settings to Access Point Radios
For example, 1 = maximum power level in a particular regulatory domain, 2 = 50% power, 3 = 25% power, 4 = 12.5%power, and so on.See the hardware installation guide for your access point for the maximum transmit power levels supported perregulatory domain. Also, see data sheet for your access point for the number of power levels supported.NoteStep 7 Save your settings by entering this command:save configStep 8 Repeat Step 2 through Step 7 for each access point radio for which you want to assign a static channel and power level.Step 9 Reenable the access point radio by entering this command:config {802.11a |802.11b}enable Cisco_APStep 10 Have the Cisco WLC send the access point radio admin state immediately to WCS by entering this command:config {802.11a |802.11b}enable networkStep 11 Save your changes by entering this command:save configStep 12 See the configuration of a particular access point by entering this command:show ap config {802.11a |802.11b}Cisco_APInformation similar to the following appears:Cisco AP Identifier.............................. 7Cisco AP Name.................................... AP1...Tx PowerNum Of Supported Power Levels ............. 8Tx Power Level 1 .......................... 20 dBmTx Power Level 2 .......................... 17 dBmTx Power Level 3 .......................... 14 dBmTx Power Level 4 .......................... 11 dBmTx Power Level 5 .......................... 8 dBmTx Power Level 6 .......................... 5 dBmTx Power Level 7 .......................... 2 dBmTx Power Level 8 .......................... -1 dBmTx Power Configuration .................... CUSTOMIZEDCurrent Tx Power Level .................... 1Phy OFDM parametersConfiguration ............................. CUSTOMIZEDCurrent Channel ........................... 36Extension Channel ......................... 40Channel Width.............................. 40 MhzAllowed Channel List....................... 36,44,52,60,100,108,116,132,......................................... 149,157TI Threshold .............................. -50Antenna Type............................... EXTERNAL_ANTENNAExternal Antenna Gain (in .5 dBi units).... 7Diversity.................................. DIVERSITY_ENABLED802.11n AntennasTxA....................................... ENABLEDB....................................... ENABLEDCisco Wireless LAN Controller Configuration Guide, Release 7.4       OL-28744-01 851Statically Assigning Channel and Transmit Power Settings to Access Point Radios
RxA....................................... DISABLEDB....................................... DISABLEDC.................................... ENABLEDDisabling Dynamic Channel and Power Assignment Globally for a CiscoWireless LAN ControllerDisabling Dynamic Channel and Power Assignment (GUI)Step 1 Choose Wireless >802.11a/n or 802.11b/g/n >RRM >Auto RF to open the 802.11a/n (or 802.11b/g/n) GlobalParameters > Auto RF page.Step 2 Disable dynamic channel assignment by choosing OFF under RF Channel Assignment.Step 3 Disable dynamic power assignment by choosing Fixed under Tx Power Level Assignment and choosing a default transmitpower level from the drop-down list.Step 4 Click Apply.Step 5 Click Save Configuration.Step 6 If you are overriding the default channel and power settings on a per radio basis, assign static channel and power settingsto each of the access point radios that are joined to the Cisco WLC.Step 7 (Optional) Repeat this procedure for the network type that you did not select (802.11a/n or 802.11b/g/n).Disabling Dynamic Channel and Power Assignment (CLI)Step 1 Disable the 802.11a or 802.11b/g network by entering this command:config {802.11a |802.11b}disable networkStep 2 Disable RRM for all 802.11a or 802.11b/g radios and set all channels to the default value by entering this command:config {802.11a |802.11b}channel global offStep 3 Enable the 802.11a or 802.11b/g network by entering this command:config {802.11a |802.11b}enable networkTo enable the 802.11g network, enter the config 802.11b 11gSupport enable command after the config 802.11benable network command.NoteStep 4 Save your changes by entering this command:save config   Cisco Wireless LAN Controller Configuration Guide, Release 7.4852 OL-28744-01  Disabling Dynamic Channel and Power Assignment Globally for a Cisco Wireless LAN Controller
Cisco Wireless LAN Controller Configuration Guide, Release 7.4       OL-28744-01 853Disabling Dynamic Channel and Power Assignment Globally for a Cisco Wireless LAN Controller
   Cisco Wireless LAN Controller Configuration Guide, Release 7.4854 OL-28744-01  Disabling Dynamic Channel and Power Assignment Globally for a Cisco Wireless LAN Controller
CHAPTER 131Configuring CCX Radio Management Features•Information About CCX Radio Management Features, page 855•Configuring CCX Radio Management, page 856Information About CCX Radio Management FeaturesYou can configure two parameters that affect client location calculations:•Radio measurement requests•Location calibrationThese parameters are supported in Cisco Client Extensions (CCX) v2 and later releases are designed to enhancelocation accuracy and timeliness for participating CCX clients.For the location features to operate properly, the access points must be configured for normal, monitor, orFlexConnect mode. However, for FlexConnect mode, the access point must be connected to the Cisco WLC.Radio Measurement RequestsWhen you enable the radio measurements requests feature, lightweight access points issue broadcast radiomeasurement request messages to clients running CCXv2 or later releases. The access points transmit thesemessages for every SSID over each enabled radio interface at a configured interval. In the process of performing802.11 radio measurements, CCX clients send 802.11 broadcast probe requests on all the channels specifiedin the measurement request. The Cisco Location Appliance uses the uplink measurements based on theserequests received at the access points to quickly and accurately calculate the client location. You do not needto specify on which channels the clients are to measure. The Cisco WLC, access point, and client automaticallydetermine which channels to use.The radio measurement feature enables the Cisco WLC to also obtain information on the radio environmentfrom the client’s perspective (rather than from just that of the access point). In this case, the access pointsissue unicast radio measurement requests to a particular CCXv4 or v5 client. The client then sends variousmeasurement reports back to the access point and onto the Cisco WLC. These reports include informationabout the radio environment and data used to interpret the location of the clients. To prevent the access pointsand Cisco WLC from being overwhelmed by radio measurement requests and reports, only two clients peraccess point and up to 20 clients per Cisco WLC are supported. You can view the status of radio measurementCisco Wireless LAN Controller Configuration Guide, Release 7.4        OL-28744-01 855
requests for a particular access point or client as well as radio measurement reports for a particular client fromthe Cisco WLC CLI.The Cisco WLC software improves the ability of the mobility services engine to accurately interpret thelocation of a device through a CCXv4 feature called location-based services. The Cisco WLC issues a path-lossrequest to a particular CCXv4 or v5 client. If the client chooses to respond, it sends a path-loss measurementreport to the Cisco WLC. These reports contain the channel and transmit power of the client.Non-CCX and CCXv1 clients ignore the CCX measurement requests and do not participate in the radiomeasurement activity.NoteLocation CalibrationFor CCX clients that need to be tracked more closely (for example, when a client calibration is performed),the Cisco WLC can be configured to command the access point to send unicast measurement requests to theseclients at a configured interval and whenever a CCX client roams to a new access point. These unicast requestscan be sent out more often to these specific CCX clients than the broadcast measurement requests, which aresent to all clients. When location calibration is configured for non-CCX and CCXv1 clients, the clients areforced to disassociate at a specified interval to generate location measurements.Configuring CCX Radio ManagementConfiguring CCX Radio Management (GUI)Step 1 Choose Wireless >802.11a/n or 802.11b/g/n >Network to open the 802.11a/n (or 802.11b/g/n) Global Parameterspage.Step 2 Under CCX Location Measurement, select the Mode check box to globally enable CCX radio management. This parametercauses the access points connected to this Cisco WLC to issue broadcast radio measurement requests to clients runningCCX v2 or later releases. The default value is disabled (or unselected).Step 3 If you selected the Mode check box in the previous step, enter a value in the Interval text box to specify how often theaccess points are to issue the broadcast radio measurement requests.The range is 60 to 32400 seconds.The default is 60 seconds.Step 4 Click Apply.Step 5 Click Save Configuration.Step 6 Follow the instructions in Step 2 of the Configuring CCX Radio Management (CLI) section below to enable access pointcustomization.To enable CCX radio management for a particular access point, you must enable access point customization,which can be done only through the Cisco WLC CLI.NoteStep 7 If desired, repeat this procedure for the other radio band (802.11a/n or 802.11b/g/n).   Cisco Wireless LAN Controller Configuration Guide, Release 7.4856 OL-28744-01  Configuring CCX Radio Management
Configuring CCX Radio Management (CLI)Step 1 Globally enable CCX radio management by entering this command:config advanced {802.11a |802.11b}ccx location-meas global enable interval_secondsThe range for the interval_seconds parameter is 60 to 32400 seconds, and the default value is 60 seconds. This commandcauses all access points connected to this Cisco WLC in the 802.11a or 802.11b/g network to issue broadcast radiomeasurement requests to clients running CCXv2 or later releases.Step 2 Enable access point customization by entering these commands:•config advanced {802.11a |802.11b}ccx customize Cisco_AP {on |off}This command enables or disables CCX radio management features for a particular access point in the 802.11a or802.11b/g network.•config advanced {802.11a |802.11b}ccx location-meas ap Cisco_AP enable interval_secondsThe range for the interval_seconds parameter is 60 to 32400 seconds, and the default value is 60 seconds. Thiscommand causes a particular access point in the 802.11a or 802.11b/g network to issue broadcast radio measurementrequests to clients running CCXv2 or higher.Step 3 Enable or disable location calibration for a particular client by entering this command:config client location-calibration {enable |disable}client _mac interval_secondsYou can configure up to five clients per Cisco WLC for locationcalibration.NoteStep 4 Save your settings by entering this command:save configViewing CCX Radio Management Information (CLI)•To see the CCX broadcast location measurement request configuration for all access points connectedto this Cisco WLC in the 802.11a or 802.11b/g network, enter this command:show advanced {802.11a |802.11b}ccx global•To see the CCX broadcast location measurement request configuration for a particular access point inthe 802.11a or 802.11b/g network, enter this command:show advanced {802.11a |802.11b}ccx ap Cisco_AP•To see the status of radio measurement requests for a particular access point, enter this command:show ap ccx rm Cisco_AP statusInformation similar to the following appears:A RadioBeacon Request................................. EnabledChannel Load Request........................... EnabledFrame Request.................................. DisabledCisco Wireless LAN Controller Configuration Guide, Release 7.4       OL-28744-01 857Configuring CCX Radio Management
Noise Histogram Request........................ DisabledPath Loss Request.............................. DisabledInterval....................................... 60Iteration...................................... 5B RadioBeacon Request................................. DisabledChannel Load Request........................... EnabledFrame Request.................................. DisabledNoise Histogram Request........................ EnabledPath Loss Request.............................. DisabledInterval....................................... 60Iteration................................... 5•To see the status of radio measurement requests for a particular client, enter this command:show client ccx rm client_mac statusInformation similar to the following appears:Client Mac Address............................... 00:40:96:ae:53:b4Beacon Request................................... EnabledChannel Load Request............................. DisabledFrame Request.................................... DisabledNoise Histogram Request.......................... DisabledPath Loss Request................................ DisabledInterval......................................... 5Iteration........................................ 3•To see radio measurement reports for a particular client, enter these commands:show client ccx rm client_mac report beacon—Shows the beacon report for the specified client.show client ccx rm client_mac report chan-load—Shows the channel-load report for the specifiedclient.show client ccx rm client_mac report noise-hist—Shows the noise-histogram report for the specifiedclient.show client ccx rm client_mac report frame—Shows the frame report for the specified client.•To see the clients configured for location calibration, enter this command:show client location-calibration summary•To see the RSSI reported for both antennas on each access point that heard the client, enter this command:show client detail client_macDebugging CCX Radio Management Issues (CLI)•Debug CCX broadcast measurement request activity by entering this command:debug airewave-director message {enable |disable}•Debug client location calibration activity by entering this command:debug ccxrm [all |error |warning |message |packet |detail {enable |disable}]•The CCX radio measurement report packets are encapsulated in Internet Access Point Protocol (IAPP)packets. Therefore, if the previous debug ccxrm command does not provide any debugs, enter thiscommand to provide debugs at the IAPP level:debug iapp error {enable |disable}   Cisco Wireless LAN Controller Configuration Guide, Release 7.4858 OL-28744-01  Configuring CCX Radio Management
•Debug the output for forwarded probes and their included RSSI for both antennas by entering thiscommand:debug dot11 load-balancingCisco Wireless LAN Controller Configuration Guide, Release 7.4       OL-28744-01 859Configuring CCX Radio Management
   Cisco Wireless LAN Controller Configuration Guide, Release 7.4860 OL-28744-01  Configuring CCX Radio Management
PART VIIIConfiguring Cisco CleanAir•Information About CleanAir, page 863•Prerequisites and Restrictions for CleanAir, page 867•Configuring Cisco CleanAir, page 869•Monitoring the Interference Devices, page 877•Configuring a Spectrum Expert Connection, page 885
CHAPTER 132Information About CleanAirThis chapter describes information about CleanAir.•Information About CleanAir, page 863Information About CleanAirCisco CleanAir is a spectrum intelligence solution designed to proactively manage the challenges of a sharedwireless spectrum. It allows you to see all of the users of the shared spectrum (both native devices and foreigninterferers). It also enables you or your network to act upon this information. For example, you could manuallyremove the interfering device, or the system could automatically change the channel away from the interference.CleanAir provides spectrum management and RF visibility.A Cisco CleanAir system consists of CleanAir-enabled access points, Cisco Wireless LAN Controllers, andCisco Prime Infrastructure. These access points collect information about all devices that operate in theindustrial, scientific, and medical (ISM) bands, identify and evaluate the information as a potential interferencesource, and forward it to the Cisco WLC. The Cisco WLC controls the access points, collects spectrum data,and forwards information to Cisco Prime Infrastructure or a Cisco mobility services engine (MSE) uponrequest.For every device operating in the unlicensed band, Cisco CleanAir tells you what it is, where it is, how it isimpacting your wireless network, and what actions you or your network should take. It simplifies RF so thatyou do not have to be an RF expert.Wireless LAN systems operate in unlicensed 2.4- and 5-GHz ISM bands. Many devices, such as microwaveovens, cordless phones, and Bluetooth devices also operate in these bands and can negatively affect Wi-Fioperations.Some of the most advanced WLAN services, such as voice over wireless and IEEE 802.11n radiocommunications, could be significantly impaired by the interference caused by other legal users of the ISMbands. The integration of Cisco CleanAir functionality into the Cisco Unified Wireless Network addressesthis problem of radio frequency (RF) interference.CleanAir is supported on mesh AP backhaul at a 5-GHz radio of mesh. You can enable CleanAir on backhaulradios and can provide report interference details and air quality.Cisco Wireless LAN Controller Configuration Guide, Release 7.4        OL-28744-01 863
Role of the Cisco Wireless LAN Controller in a Cisco CleanAir SystemThe Cisco WLC performs the following tasks in a Cisco CleanAir system:•Configures Cisco CleanAir capabilities on the access point.•Provides interfaces (GUI, CLI, and SNMP) for configuring Cisco CleanAir features and retrieving data•Displays spectrum data.•Collects and processes air quality reports from the access point and stores them in the air quality database.The Air Quality Report (AQR) contains information about the total interference from all identifiedsources represented by the Air Quality Index (AQI) and summary for the most severe interferencecategories. The CleanAir system can also include unclassified interference information under perinterference type reports, which enables you to take action in cases where the interference due tounclassified interfering devices is more.•Collects and processes interference device reports (IDRs) from the access point and stores them in theinterference device database.•Forwards spectrum data to Prime Infrastructure and the MSE.Interference Types that Cisco CleanAir Can DetectCisco CleanAir can detect interference, report on the location and severity of the interference, and recommenddifferent mitigation strategies. Two such mitigation strategies are persistent device avoidance and spectrumevent-driven RRM.Wi-Fi chip-based RF management systems share these characteristics:•Any RF energy that cannot be identified as a Wi-Fi signal is reported as noise.•Noise measurements that are used to assign a channel plan tend to be averaged over a period of time toavoid instability or rapid changes that can be disruptive to certain client devices.•Averaging measurements reduces the resolution of the measurement. As such, a signal that disruptsclients might not look like it needs to be mitigated after averaging.•All RF management systems available today are reactive in nature.Cisco CleanAir is different and can positively identify not only the source of the noise but also its locationand potential impact to a WLAN. Having this information allows you to consider the noise within the contextof the network and make intelligent and, where possible, proactive decisions. For CleanAir, two types ofinterference events are common:•Persistent interference•Spontaneous interferencePersistent interference events are created by devices that are stationary in nature and have intermittent butlargely repeatable patterns of interference. For example, consider the case of a microwave oven located in abreak room. Such a device might be active for only 1 or 2 minutes at a time. When operating, however, it canbe disruptive to the performance of the wireless network and associated clients. Using Cisco CleanAir, youcan positively identify the device as a microwave oven rather than indiscriminate noise. You can also determineexactly which part of the band is affected by the device, and because you can locate it, you can understandwhich access points are most severely affected. You can then use this information to direct RRM in selecting   Cisco Wireless LAN Controller Configuration Guide, Release 7.4864 OL-28744-01  Information About CleanAir
a channel plan that avoids this source of interference for the access points within its range. Because thisinterference is not active for a large portion of the day, existing RF management applications might attemptto again change the channels of the affected access points. Persistent device avoidance is unique, however,in that it remains in effect as long as the source of interference is periodically detected to refresh the persistentstatus. The Cisco CleanAir system knows that the microwave oven exists and includes it in all future planning.If you move either the microwave oven or the surrounding access points, the algorithm updates RRMautomatically.Spectrum event-driven RRM can be triggered only by Cisco CleanAir-enabled access points in local mode.NoteSpontaneous interference is interference that appears suddenly on a network, perhaps jamming a channel ora range of channels completely. The Cisco CleanAir spectrum event-driven RRM feature allows you to set athreshold for air quality (AQ) that, if exceeded, triggers an immediate channel change for the affected accesspoint. Most RF management systems can avoid interference, but this information takes time to propagatethrough the system. Cisco CleanAir relies on AQ measurements to continuously evaluate the spectrum andcan trigger a move within 30 seconds. For example, if an access point detects interference from a video camera,it can recover by changing channels within 30 seconds of the camera becoming active. Cisco CleanAir alsoidentifies and locates the source of interference so that more permanent mitigation of the device can beperformed at a later time.In the case of Bluetooth devices, Cisco CleanAir-enabled access points can detect and report interferencesonly if the devices are actively transmitting. Bluetooth devices have extensive power save modes. For example,interference can be detected when data or voice is being streamed between the connected devices.Persistent DevicesSome interference devices such as outdoor bridges and Microwave Ovens only transmit when needed. Thesedevices can cause significant interference to the local WLAN due to short duration and periodic operationremain largely undetected by normal RF management metrics. With CleanAir the RRM DCA algorithm candetect, measure, register and remember the impact and adjust the DCA algorithm. This minimizes the use ofchannels affected by the persistent devices in the channel plan local to the interference source. Cisco CleanAirdetects and stores the persistent device information in the Cisco WLC and this information is used to mitigateinterfering channels.Persistent Devices DetectionCleanAir-capable Monitor Mode access point collects information about persistent devices on all configuredchannels and stores the information in the Cisco WLC. Local/Bridge mode AP detects interference deviceson the serving channels only.Persistent Devices PropagationPersistent device information that is detected by local or monitor mode access points is propagated to theneighboring access points connected to the same Cisco WLC to provide better chance of handling and avoidingpersistent devices. Persistent device detected by the CleanAir-enabled access point is propagated to neighboringnon-CleanAir access points, thus enhancing channel selection quality.Cisco Wireless LAN Controller Configuration Guide, Release 7.4       OL-28744-01 865Information About CleanAir
Detecting Interferers by an Access PointWhen a CleanAir-enabled access point detects interference devices, detections of the same device from multiplesensors are merged together to create clusters. Each cluster is given a unique ID. Some devices conservepower by limiting the transmit time until actually needed which results in the spectrum sensor to temporarilystop detecting the device. This device is then correctly marked as down. A down device is correctly removedfrom the spectrum database. In cases when all the interferer detections for a specific devices are reported, thecluster ID is kept alive for an extended period of time to prevent possible device detection bouncing. If thesame device is detected again, it is merged with the original cluster ID and the device detection history ispreserved.For example, some bluetooth headsets operate on battery power. These devices employ methods to reducepower consumption, such as turning off the transmitter when not actually needed. Such devices can appearto come and go from the classification. To manage these devices, CleanAir keeps the cluster IDs longer andthey are remerged into a single record upon detection. This process smoothens the user records and accuratelyrepresents the device history.   Cisco Wireless LAN Controller Configuration Guide, Release 7.4866 OL-28744-01  Information About CleanAir
CHAPTER 133Prerequisites and Restrictions for CleanAirThis chapter describes the prerequisites and restrictions for configuring Cisco CleanAir.•Prerequisites for CleanAir, page 867•Restrictions for CleanAir, page 868Prerequisites for CleanAirYou can configure Cisco CleanAir only on CleanAir-enabled access points.Only Cisco CleanAir-enabled access points using the following access point modes can perform Cisco CleanAirspectrum monitoring:•Local—In this mode, each Cisco CleanAir-enabled access point radio provides air quality and interferencedetection reports for the current operating channel only.•FlexConnect—When a FlexConnect access point is connected to the controller, its Cisco CleanAirfunctionality is identical to local mode.•Monitor—When Cisco CleanAir is enabled in monitor mode, the access point provides air quality andinterference detection reports for all monitored channels.The following options are available:◦All—All channels◦DCA—Channel selection governed by the DCA list◦Country—All channel legal within a regulatory domainCisco Wireless LAN Controller Configuration Guide, Release 7.4        OL-28744-01 867
Suppose you have two APs, one in the FlexConnect mode and the other in the monitormode. Also suppose that you have created a profile enabling EAP attack against 802.1xauth. The Airmagnet (AM) tool, which can generate different types of attacks, fails togenerate any attack even if you have provided valid AP MAC and STA MAC addresses.But if the AP MAC and STA MAC addresses in the AM tool are swapped, that is, theAP MAC address is specified in the STA MAC field and the STA MAC address isspecified in the AP MAC field, then the tool is able to generate attacks, which the APin the Monitor mode is also able to detect.NoteThe access point does not participate in AQ HeatMap in Prime Infrastructure.Note•SE-Connect—This mode enables a user to connect a Spectrum Expert application running on an externalMicrosoft Windows XP or Vista PC to a Cisco CleanAir-enabled access point in order to display andanalyze detailed spectrum data. The Spectrum Expert application connects directly to the access point,bypassing the controller. An access point in SE-Connect mode does not provide any Wi-Fi, RF, orspectrum data to the controller. All CleanAir system functionality is suspended while the AP is in thismode, and no clients are served. This mode is intended for remote troubleshooting only. Up to threeactive Spectrum Expert connections are possible.Restrictions for CleanAir•Access points in monitor mode do not transmit Wi-Fi traffic or 802.11 packets. They are excluded fromradio resource management (RRM) planning and are not included in the neighbor access point list. IDRclustering depends on the controller’s ability to detect neighboring in-network access points. Correlatinginterference device detections from multiple access points is limited between monitor-mode accesspoints.•Spectrum Expert (SE) Connect functionality is supported for local, FlexConnect, bridge, and monitormodes. The access point provides spectrum information to Spectrum Expert only for the current channel(s).For local, FlexConnect, and bridge modes, the spectrum data is available for the current active channel(s)and for the monitor mode, the common monitored channel list is available. The access point continuesto send AQ (Air Quality) and IDR (Interference Device Reports) reports to the controller and performnormal activities according to the current mode. Sniffer and rogue detections access point modes areincompatible with all types of CleanAir spectrum monitoring.•Cisco recommends a ratio of 1 monitor mode access point for every 5 local mode access points, thismay also vary based on the network design and expert guidance for best coverage.•Do not connect access points in SE connect mode directly to any physical port on Cisco 2500 SeriesCisco WLCs.•Spectrum Expert (Windows XP laptop client) and AP should be pingable, otherwise; it will not work.   Cisco Wireless LAN Controller Configuration Guide, Release 7.4868 OL-28744-01  Restrictions for CleanAir
CHAPTER 134Configuring Cisco CleanAir•Configuring Cisco CleanAir on the Controller, page 869•Configuring Cisco CleanAir on an Access Point, page 875Configuring Cisco CleanAir on the ControllerConfiguring Cisco CleanAir on the Cisco Wireless LAN Controller (GUI)Step 1 Choose Wireless >802.11a/n or 802.11b/g/n > CleanAir to open the 802.11a (or 802.11b) > CleanAir page.Step 2 Select the CleanAir check box to enable Cisco CleanAir functionality on the 802.11a/n or 802.11b/g/n network, orunselect it to prevent the Cisco WLC from detecting spectrum interference. By default, the value is not selected.Step 3 Select the Report Interferers check box to enable the Cisco CleanAir system to report any detected sources of interference,or unselect it to prevent the Cisco WLC from reporting interferers. The default value is selected.Device Security alarms, Event Driven RRM, and the Persistence Device Avoidance algorithm do not work ifReport Interferers are disabled.NoteStep 4 Select the Persistent Device Propagation check box to enable propagation of information about persistent devices thatcan be detected by CleanAir. Persistent device propagation enables you to propagate information about persistent devicesto the neighboring access points connected to the same Cisco WLC. Persistent interferers are present at the location andinterfere with the WLAN operations even if they are not detectable at all times.Step 5 Ensure that any sources of interference that need to be detected and reported by the Cisco CleanAir system appear in theInterferences to Detect box and any that do not need to be detected appear in the Interferences to Ignore box. Use the >and <buttons to move interference sources between these two boxes. By default, all interference sources are detected.The possible sources of interference that you can choose are as follows:•Bluetooth Paging Inquiry—A Bluetooth discovery (802.11b/g/n only)•Bluetooth Sco Acl—A Bluetooth link (802.11b/g/n only)•Generic DECT—A digital enhanced cordless communication (DECT)-compatible phone•Generic TDD—A time division duplex (TDD) transmitter•Generic Waveform—A continuous transmitterCisco Wireless LAN Controller Configuration Guide, Release 7.4        OL-28744-01 869
•Jammer—A jamming device•Microwave—A microwave oven (802.11b/g/n only)•Canopy—A canopy bridge device•Spectrum 802.11 FH—An 802.11 frequency-hopping device (802.11b/g/n only)•Spectrum 802.11 inverted—A device using spectrally inverted Wi-Fi signals•Spectrum 802.11 non std channel—A device using nonstandard Wi-Fi channels•Spectrum 802.11 SuperG—An 802.11 SuperAG device•Spectrum 802.15.4—An 802.15.4 device (802.11b/g/n only)•Video Camera—An analog video camera•WiMAX Fixed—A WiMAX fixed device (802.11a/n only)•WiMAX Mobile—A WiMAX mobile device (802.11a/n only)•XBox—A Microsoft Xbox (802.11b/g/n only)Access points that are associated to the Cisco WLC send interference reports only for the interferers that appearin the Interferences to Detect box. This functionality allows you to filter out interferers that you do not want aswell as any that may be flooding the network and causing performance problems for the Cisco WLC or PrimeInfrastructure. Filtering allows the system to resume normal performance levels.NoteStep 6 Configure Cisco CleanAir alarms as follows:a) Select the Enable AQI (Air Quality Index) Trap check box to enable the triggering of air quality alarms, or unselectthe box to disable this feature. The default value is selected.b) If you selected the Enable AQI Trap check box in Step a, enter a value between 1 and 100 (inclusive) in the AQIAlarm Threshold text box to specify the threshold at which you want the air quality alarm to be triggered. When theair quality falls below the threshold level, the alarm is triggered. A value of 1 represents the worst air quality, and100 represents the best. The default value is 35.c) Enter the AQI Alarm Threshold (1 to 100) that you want to set. An alarm is generated when the air quality reachesa threshold value. The default is 35. Valid range is from 1 and 100.d) Select the Enable trap for Unclassified Interferences check box to enable the AQI alarm to be generated upondetection of unclassified interference beyond the severity threshond specified in the AQI Alarm Threshold.Unclassified interferences are interferences that are detected but do not correspond to any of the identifiable interferencetypes.e) Enter the Threshold for Unclassified category trap (1 to 99). Enter a value from 1 and 99. The default is 20. Thisis the severity index threshold for an unclassified interference category.f) Select the Enable Interference Type Trap check box to trigger interferer alarms when the Cisco WLC detectsspecified device types, or unselect it to disable this feature. The default value is selectedg) Make sure that any sources of interference that need to trigger interferer alarms appear in the Trap on These Typesbox and any that do not need to trigger interferer alarms appear in the Do Not Trap on These Types box. Use the >and <buttons to move interference sources between these two boxes. By default, all interference sources triggerinterferer alarms.For example, if you want the Cisco WLC to send an alarm when it detects a jamming device, select the EnableInterference Type Trap check box and move the jamming device to the Trap on These Types box.   Cisco Wireless LAN Controller Configuration Guide, Release 7.4870 OL-28744-01  Configuring Cisco CleanAir on the Controller
Step 7 Click Apply.Step 8 Trigger spectrum event-driven radio resource management (RRM) to run when a Cisco CleanAir-enabled access pointdetects a significant level of interference as follows:a) Look at the EDRRM field to see the current status of spectrum event-driven RRM and, if enabled, the SensitivityThreshold field to see the threshold level at which event-driven RRM is invoked.b) If you want to change the current status of event-driven RRM or the sensitivity level, click Change Settings. The802.11a (or 802.11b) > RRM > Dynamic Channel Assignment (DCA) page appears.c) Select the EDRRM check box to trigger RRM to run when an access point detects a certain level of interference, orunselect it to disable this feature. The default value is selected.d) If you selected the EDRRM check box in Step c, choose Low,Medium,High, or Custom from the SensitivityThreshold drop-down list to specify the threshold at which you want RRM to be triggered. When the interferencefor the access point rises above the threshold level, RRM initiates a local dynamic channel assignment (DCA) runand changes the channel of the affected access point radio if possible to improve network performance. Low representsa decreased sensitivity to changes in the environment while High represents an increased sensitivityIf you selected the EDRRM sensitivity threshold as custom, you must set a threshold value in the Custom SensitivityThreshold field. The default sensitivity is 35.The EDRRM AQ threshold value for low sensitivity is 35, medium sensitivity is 50, and high sensitivity is 60.e) Click Apply.Step 9 Click Save Configuration.Configuring Cisco CleanAir on the Cisco Wireless LAN Controller (CLI)Step 1 Configure Cisco CleanAir functionality on the 802.11 network by entering this command:config {802.11a | 802.11b} cleanair {enable | disable} allIf you disable this feature, the Cisco WLC does not receive any spectrum data. The default value is enable.Step 2 Enable CleanAir on all associated access points in a network:config {802.11a cleanair enable networkYou can enable CleanAir on a 5-GHz radio of mesh access points.Step 3 Configure interference detection and specify sources of interference that need to be detected by the Cisco CleanAirsystem by entering this command:config {802.11a | 802.11b} cleanair device {enable | disable} typewhere you choose the type as one of the following:•802.11-fh—An 802.11 frequency-hopping device (802.11b/g/n only)•802.11-inv—A device using spectrally inverted Wi-Fi signals•802.11-nonstd—A device using nonstandard Wi-Fi channels•802.15.4—An 802.15.4 device (802.11b/g/n only)•all—All interference device types (this is the default value)Cisco Wireless LAN Controller Configuration Guide, Release 7.4       OL-28744-01 871Configuring Cisco CleanAir on the Controller
•bt-discovery—A bluetooth discovery (802.11b/g/n only)•bt-link—A bluetooth link (802.11b/g/n only)•canopy—A canopy device•cont-tx—A continuous transmitter•dect-like—A digital enhanced cordless communication (DECT)-compatible phone•jammer—A jamming device•mw-oven—A microwave oven (802.11b/g/n only)•superag—An 802.11 SuperAG device•tdd-tx—A time division duplex (TDD) transmitter•video camera—An analog video camera•wimax-fixed—A WiMAX fixed device•wimax-mobile—A WiMAX mobile device•xbox—A Microsoft Xbox (802.11b/g/n only)Access points that are associated to the Cisco WLC send interference reports only for the interference typesspecified in this command. This functionality allows you to filter out interferers that may be flooding the networkand causing performance problems for the Cisco WLC or Prime Infrastructure. Filtering allows the system toresume normal performance levels.NoteStep 4 Configure the triggering of air quality alarms by entering this command:config {802.11a | 802.11b} cleanair alarm air-quality {enable | disable}The default value is enabled.Step 5 Specify the threshold at which you want the air quality alarm to be triggered by entering this command:config {802.11a | 802.11b} cleanair alarm air-quality {enable | disable}config {802.11a | 802.11b} cleanair alarmair-quality threshold thresholdwhere threshold is a value between 1 and 100 (inclusive). When the air quality falls below the threshold level, the alarmis triggered. A value of 1 represents the worst air quality, and 100 represents the best. The default value is 35.Step 6 Enable the triggering of interferer alarms by entering this command:config {802.11a | 802.11b} cleanair alarm device {enable | disable}The default value is enable.Step 7 Specify sources of interference that trigger alarms by entering this command:config {802.11a |802.11b}cleanair alarm device type {enable | disable}where you choose the type as one of thefollowing:•802.11-fh—An 802.11 frequency-hopping device (802.11b/g/n only)•802.11-inv—A device using spectrally inverted Wi-Fi signals•802.11-nonstd—A device using nonstandard Wi-Fi channels•802.15.4—An 802.15.4 device (802.11b/g/n only)•all—All interference device types (this is the default value)   Cisco Wireless LAN Controller Configuration Guide, Release 7.4872 OL-28744-01  Configuring Cisco CleanAir on the Controller
•bt-discovery—A Bluetooth discovery (802.11b/g/n only)•bt-link—A Bluetooth link (802.11b/g/n only)•canopy—A canopy device•cont-tx—A continuous transmitter•dect-like—A digital enhanced cordless communication (DECT)-compatible phone•jammer—A jamming device•mw-oven—A microwave oven (802.11b/g/n only)•superag—An 802.11 SuperAG device•tdd-tx—A time division duplex (TDD) transmitter•video camera—An analog video camera•wimax-fixed—A WiMAX fixed device•wimax-mobile—A WiMAX mobile device•xbox—A Microsoft Xbox (802.11b/g/n only)Step 8 Configure the triggering of air quality alarms for unclassified devices by entering this command:config {802.11a |802.11b}cleanair alarm unclassified {enable |disable}Step 9 Specify the threshold at which you want the air quality alarm to be triggered for unclassified devices by entering thiscommand:config {802.11a |802.11b}cleanair alarm unclassified threshold thresholdwhere threshold is a value from 1 and 99 (inclusive). When the air quality falls below the threshold level, the alarm istriggered. A value of 1 represents the worst air quality, and 100 represents the best. The default value is 35.Step 10 Trigger spectrum event-driven radio resource management (RRM) to run when a Cisco CleanAir-enabled access pointdetects a significant level of interference by entering these commands:config advanced {802.11a |802.11b}channel cleanair-event {enable |disable}—Enables or disables spectrumevent-driven RRM. The default value is disabled.config advanced {802.11a |802.11b}channel cleanair-event sensitivity {low |medium |high |custom}—Specifiesthe threshold at which you want RRM to be triggered. When the interference level for the access point rises above thethreshold level, RRM initiates a local dynamic channel assignment (DCA) run and changes the channel of the affectedaccess point radio if possible to improve network performance. Low represents a decreased sensitivity to changes in theenvironment while high represents an increased sensitivity. You can also set the sensitivity to a custom level of yourchoice. The default value is medium.config advanced {802.11a |802.11b}channel cleanair-event sensitivity threshold thresholdvalue—If you set thethreshold sensitivity as custom, you must set a custom threshold value. The default is 35.Step 11 Enable persistent devices propagation by entering this command:config advanced {802.11a |802.11b}channel pda-prop {enable |disable}Step 12 Save your changes by entering this command:save configStep 13 See the Cisco CleanAir configuration for the 802.11a/n or 802.11b/g/n network by entering this command:Cisco Wireless LAN Controller Configuration Guide, Release 7.4       OL-28744-01 873Configuring Cisco CleanAir on the Controller
show {802.11a |802.11b}cleanair configInformation similar to the following appears:(Cisco Controller) >show 802.11a cleanair configClean Air Solution............................... DisabledAir Quality Settings:Air Quality Reporting........................ EnabledAir Quality Reporting Period (min)........... 15Air Quality Alarms........................... EnabledAir Quality Alarm Threshold................ 35Unclassified Interference.................. DisabledUnclassified Severity Threshold............ 20Interference Device Settings:Interference Device Reporting................ EnabledInterference Device Types:TDD Transmitter.......................... EnabledJammer................................... EnabledContinuous Transmitter................... EnabledDECT-like Phone.......................... EnabledVideo Camera............................. EnabledWiFi Inverted............................ EnabledWiFi Invalid Channel..................... EnabledSuperAG.................................. EnabledCanopy................................... EnabledWiMax Mobile............................. EnabledWiMax Fixed.............................. EnabledInterference Device Alarms................... EnabledInterference Device Types Triggering Alarms:TDD Transmitter.......................... DisabledJammer................................... EnabledContinuous Transmitter................... DisabledDECT-like Phone.......................... DisabledVideo Camera............................. DisabledWiFi Inverted............................ EnabledWiFi Invalid Channel..................... EnabledSuperAG.................................. DisabledCanopy................................... DisabledWiMax Mobile............................. DisabledWiMax Fixed.............................. DisabledAdditional Clean Air Settings:CleanAir ED-RRM State........................ DisabledCleanAir ED-RRM Sensitivity.................. MediumCleanAir ED-RRM Custom Threshold............. 50CleanAir Persistent Devices state............ DisabledCleanAir Persistent Device Propagation....... EnabledStep 14 See the spectrum event-driven RRM configuration for the 802.11a/n or 802.11b/g/n network by entering this command:show advanced {802.11a |802.11b}channelInformation similar to the following appears:Automatic Channel AssignmentChannel Assignment Mode........................ AUTOChannel Update Interval........................ 600 seconds [startup]Anchor time (Hour of the day).................. 0Channel Update Contribution.................... SNICleanAir Event-driven RRM option.............. EnabledCleanAir Event-driven RRM sensitivity...... Medium   Cisco Wireless LAN Controller Configuration Guide, Release 7.4874 OL-28744-01  Configuring Cisco CleanAir on the Controller
Configuring Cisco CleanAir on an Access PointConfiguring Cisco CleanAir on an Access Point (GUI)Step 1 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 2 Hover your cursor over the blue drop-down arrow for the desired access point and click Configure. The 802.11a/n (or802.11b/g/n) Cisco APs > Configure page appears.The CleanAir Capable field shows whether this access point can support CleanAir functionality. If it can, go to the nextstep to enable or disable CleanAir for this access point. If the access point cannot support CleanAir functionality, youcannot enable CleanAir for this access point.By default, the Cisco CleanAir functionality is enabled on theradios.NoteStep 3 Enable Cisco CleanAir functionality for this access point by choosing Enable from the CleanAir Status drop-down list.To disable CleanAir functionality for this access point, choose Disable. The default value is Enable. This setting overridesthe global CleanAir configuration for this access point.The Number of Spectrum Expert Connections text box shows the number of Spectrum Expert applications that arecurrently connected to the access point radio. Up to three active connections are possible.Step 4 Click Apply.Step 5 Click Save Configuration.Step 6 Click Back to return to the 802.11a/n (or 802.11b/g/n) Radios page.Step 7 View the Cisco CleanAir status for each access point radio by looking at the CleanAir Status text box on the 802.11a/n(or 802.11b/g/n) Radios page.The Cisco CleanAir status is one of the following:•UP—The spectrum sensor for the access point radio is currently operational (error code 0).•DOWN—The spectrum sensor for the access point radio is currently not operational because an error has occurred.The most likely reason for the error is that the access point radio is disabled (error code 8). To correct this error,enable the radio.•ERROR—The spectrum sensor for the access point radio has crashed (error code 128), making CleanAir monitoringnonoperational for this radio. If this error occurs, reboot the access point. If the error continues to appear, you mightwant to disable Cisco CleanAir functionality on the radio.•N/A—This access point radio is not capable of supporting Cisco CleanAir functionality.You can create a filter to make the 802.11a/n Radios page or the 802.11b/g/n Radios page show only accesspoint radios that have a specific Cisco CleanAir status (such as UP, DOWN, ERROR, or N/A). This feature isespecially useful if your list of access point radios spans multiple pages, preventing you from viewing them allat once. To create a filter, click Change Filter to open the Search AP dialog box, select one or more of theCleanAir Status check boxes, and click Find. Only the access point radios that match your search criteria appearon the 802.11a/n Radios page or the 802.11b/g/n Radios page, and the Current Filter parameter at the top of thepage specifies the filter used to generate the list (for example, CleanAir Status: UP).NoteCisco Wireless LAN Controller Configuration Guide, Release 7.4       OL-28744-01 875Configuring Cisco CleanAir on an Access Point
Configuring Cisco CleanAir on an Access Point (CLI)Step 1 Configure Cisco CleanAir functionality for a specific access point by entering this command:config {802.11a |802.11b}cleanair {enable | disable}Cisco_APStep 2 Save your changes by entering this command:save configStep 3 See the Cisco CleanAir configuration for a specific access point on the 802.11a/n or 802.11b/g/n network by enteringthis command:show ap config {802.11a | 802.11b} Cisco_APInformation similar to the following appears:Cisco AP Identifier.............................. 0Cisco AP Name.................................... CISCO_AP3500...Spectrum Management InformationSpectrum Management Capable.............. YesSpectrum Management Admin State.......... EnabledSpectrum Management Operation State...... UpRapid Update Mode........................ DisabledSpectrum Expert connection............... DisabledSpectrum Sensor State................. Configured (Error code = 0)See step 7 of Configuring Cisco CleanAir on an Access Point (GUI), on page 875 for descriptions of the spectrummanagement operation states and the possible error codes for the spectrum sensor state.Note   Cisco Wireless LAN Controller Configuration Guide, Release 7.4876 OL-28744-01  Configuring Cisco CleanAir on an Access Point
CHAPTER 135Monitoring the Interference Devices•Prerequisites for Monitoring the Interference Devices, page 877•Monitoring the Interference Device (GUI), page 877•Monitoring the Interference Device (CLI), page 879•Monitoring Persistent Devices (GUI), page 880•Monitoring Persistent Devices (CLI), page 880•Monitoring the Air Quality of Radio Bands, page 881Prerequisites for Monitoring the Interference DevicesYou can configure Cisco CleanAir only on CleanAir-enabled access points.Monitoring the Interference Device (GUI)Step 1 Choose Monitor > Cisco CleanAir > 802.11a/n or 802.11b/g/n > Interference Devices to open the CleanAir >Interference Devices page.This page shows the following information:•AP Name—The name of the access point where the interference device is detected.•Radio Slot #—Slot where the radio is installed.•Interferer Type—Type of the interferer.•Affected Channel—Channel that the device affects.•Detected Time—Time at which the interference was detected.•Severity—Severity index of the interfering device.•Duty Cycle (%)—Proportion of time during which the interfering device was active.•RSSI—Receive signal strength indicator (RSSI) of the access point.Cisco Wireless LAN Controller Configuration Guide, Release 7.4        OL-28744-01 877
•DevID—Device identification number that uniquely identified the interfering device.•ClusterID—Cluster identification number that uniquely identifies the type of the devices.Step 2 Click Change Filter to display the information about interference devices based on a particular criteria.Step 3 Click Clear Filter to remove the filter and display the entire access point list.You can create a filter to display the list of interference devices that are based on the following filtering parameters:•Cluster ID—To filter based on the Cluster ID, select the check box and enter the Cluster ID in the text box nextto this field.•AP Name—To filter based on the access point name, select the check box and enter the access point name in thetext box next to this field.•Interferer Type—To filter based on the type of the interference device, select the check box and select the interfererdevice from the options.Select one of the interferer devices:◦BT Link◦MW Oven◦802.11 FH◦BT Discovery◦TDD Transmit◦Jammer◦Continuous TX◦DECT Phone◦Video Camera◦802.15.4◦WiFi Inverted◦WiFi Inv. Ch◦SuperAG◦Canopy◦XBox◦WiMax Mobile◦WiMax Fixed◦WiFi ACI◦Unclassified•Activity Channels•Severity   Cisco Wireless LAN Controller Configuration Guide, Release 7.4878 OL-28744-01  Monitoring the Interference Device (GUI)
•Duty Cycle (%)•RSSIStep 4 Click Find.The current filter parameters are displayed in the Current Filter field.Monitoring the Interference Device (CLI)This section describes the commands that you can use to monitor the interference devices for the 802.11a/nor 802.11b/g/n radio band.Detecting Interferers by an Access PointSee information for all of the interferers detected by a specific access point on the 802.11a/n or 802.11b/g/nradio band by entering this command:show {802.11a |802.11b}cleanair device ap Cisco_APWhen a CleanAir-enabled access point detects interference devices, detections of the same device from multiplesensors are merged together to create clusters. Each cluster is given a unique ID. Some devices conservepower by limiting the transmit time until actually needed which results in the spectrum sensor to temporarilystop detecting the device. This device is then correctly marked as down. A down device is correctly removedfrom the spectrum database. In cases when all the interferer detections for a specific devices are reported, thecluster ID is kept alive for an extended period of time to prevent possible device detection bouncing. If thesame device is detected again, it is merged with the original cluster ID and the device detection history ispreserved.For example, some Bluetooth headsets operate on battery power. These devices employ methods to reducepower consumption, such as turning off the transmitter when not actually needed. Such devices can appearto come and go from the classification. To manage these devices, CleanAir keeps the cluster IDs longer andthey are remerged into a single record upon detection. This process smoothens the user records and accuratelyrepresents the device history.Detecting Interferers by Device TypeSee information for all of the interferers of a specific device type on the 802.11a/n or 802.11b/g/n radio bandby entering this command:show {802.11a |802.11b}cleanair device type typeDetecting Persistent Sources of InterferenceSee a list of persistent sources of interference for a specific access point on the 802.11a/n or 802.11b/g/n radioband by entering this command:show ap auto-rf {802.11a |802.11b}Cisco_APCisco Wireless LAN Controller Configuration Guide, Release 7.4       OL-28744-01 879Monitoring the Interference Device (CLI)
Monitoring Persistent Devices (GUI)To monitor persistent devices on a specific access point using the Cisco WLC GUI:Choose Wireless >Access Points > Radios > 802.11a/n or 802.11b/g/n to open the 802.11a/n (or 802.11b/g/n)Radios page. Hover your cursor over the blue drop-down arrow for the desired access point and click Detail.The 802.11a/n (or 802.11b/g/n) AP Interfaces > Detail page appears.This page displays the details of the access points along with the list of persistent devices detected by thisaccess point. Details of the persistent devices is displayed under the Persistent Devices section.The following information for each persistent device is available:•Class Type—The class type of the persistent device.•Channel—Channel this device is affecting.•DC(%)—Duty cycle (in percentage) of the persistent device.•RSSI(dBm)—RSSI indicator of the persistent device.•Last Seen Time—Timestamp when the device was last active.Monitoring Persistent Devices (CLI)To view the list of persistent devices using the CLI, use the following command:show ap auto-rf {802.11a |802.11b}ap_nameInformation similar to the following appears:Number Of Slots.................................. 2AP Name.......................................... AP_1142_MAPMAC Address...................................... c4:7d:4f:3a:35:38Slot ID........................................ 1Radio Type..................................... RADIO_TYPE_80211aSub-band Type.................................. AllNoise Information. . ......Power Level.................................. 1RTS/CTS Threshold............................ 2347Fragmentation Threshold...................... 2346Antenna Pattern.............................. 0Persistent Interference DevicesClass Type Channel DC (%%) RSSI (dBm) Last Update Time------------------------- ------- ------ ---------- ------------------------Video Camera 149 100 -34 Tue Nov 8 10:06:25 2011The following information for each persistent device is available:•Class Type—The class type of the persistent device.•Channel—Channel this device is affecting.•DC(%)—Duty cycle (in percentage) of the persistent device.•RSSI(dBm)—RSSI indicator of the persistent device.•Last Seen Time—Timestamp when the device was last active.   Cisco Wireless LAN Controller Configuration Guide, Release 7.4880 OL-28744-01  Monitoring Persistent Devices (GUI)
Monitoring the Air Quality of Radio BandsThis section describes how to monitor the air quality of the 802.11a/n and 802.11b/g/n radio bands using boththe Cisco WLC GUI and CLI.Monitoring the Air Quality of Radio Bands (GUI)Choose Monitor > Cisco CleanAir > 802.11a/n or 802.11b/g/n >Air Quality Report to open the CleanAir> Air Quality Report page.This page shows the air quality of both the 802.11a/n and 802.11b/g/n radio bands. Specifically, it shows thefollowing information:•AP Name—The name of the access point that reported the worst air quality for the 802.11a/n or802.11b/g/n radio band.•Radio Slot—The slot number where the radio is installed.•Channel—The radio channel where the air quality is monitored.•Minimum AQ—The minimum air quality for this radio channel.•Average AQ—The average air quality for this radio channel.•Interferer—The number of interferers detected by the radios on the 802.11a/n or 802.11b/g/n radio band.•DFS—Dynamic Frequency Selection. This indicates if DFS is enabled or not.Monitoring the Air Quality of Radio Bands (CLI)This section describes the commands that you can use to monitor the air quality of the 802.11a/n or 802.11b/g/nradio band.Viewing a Summary of the Air QualitySee a summary of the air quality for the 802.11a/n or 802.11b/g/n radio band by entering this command:show {802.11a |802.11b}cleanair air-quality summaryViewing Air Quality for all Access Points on a Radio BandSee information for the 802.11a/n or 802.11b/g/n access point with the air quality by entering this command:show {802.11a |802.11b}cleanair air-qualityViewing Air Quality for an Access Point on a Radio BandSee air quality information for a specific access point on the 802.11a/n or 802.11b/g/n radio band by enteringthis command:show {802.11a |802.11b}cleanair air-quality Cisco_APCisco Wireless LAN Controller Configuration Guide, Release 7.4       OL-28744-01 881Monitoring the Air Quality of Radio Bands
Monitoring the Worst Air Quality of Radio Bands (GUI)Step 1 Choose Monitor >Cisco CleanAir >Worst Air-Quality to open the CleanAir > Worst Air Quality Report page.This page shows the air quality of both the 802.11a/n and 802.11b/g/n radio bands. Specifically, it shows the followinginformation:•AP Name—The name of the access point that reported the worst air quality for the 802.11 radio band.•Channel Number—The radio channel with the worst reported air quality.•Minimum Air Quality Index(1 to 100)—The minimum air quality for this radio channel. An air quality index(AQI) value of 100 is the best, and 1 is the worst.•Average Air Quality Index(1 to 100)—The average air quality for this radio channel. An air quality index (AQI)value of 100 is the best, and 1 is the worst.•Interference Device Count—The number of interferers detected by the radios on the 802.11 radio band.Step 2 See a list of persistent sources of interference for a specific access point radio as follows:a) Choose Wireless >Access Points >Radios >802.11a/n or 802.11b/g/n to open the 802.11a/n (or 802.11b/g/n)Radios page.b) Hover your cursor over the blue drop-down arrow for the desired access point radio and click CleanAir-RRM. The802.11a/n (or 802.11b/g/n) Cisco APs > Access Point Name > Persistent Devices page appears. This page lists thedevice types of persistent sources of interference detected by this access point radio. It also shows the channel onwhich the interference was detected, the percentage of time that the interferer was active (duty cycle), the receivedsignal strength (RSSI) of the interferer, and the day and time when the interferer was last detected.Monitoring the Worst Air Quality of Radio Bands (CLI)This section describes the commands that you can use to monitor the air quality of the 802.11 radio band.Viewing a Summary of the Air Quality (CLI)See a summary of the air quality for the 802.11a/n or 802.11b/g/n radio band by entering this command:show {802.11a |802.11b}cleanair air-quality summaryViewing the Worst Air Quality Information for all Access Points on a Radio Band (CLI)See information for the 802.11a/n or 802.11b/g/n access point with the worst air quality by entering thiscommand:show {802.11a |802.11b}cleanair air-quality worstViewing the Air Quality for an Access Point on a Radio Band (CLI)See the air quality information for a specific access point on the 802.11 radio band by entering this command:   Cisco Wireless LAN Controller Configuration Guide, Release 7.4882 OL-28744-01  Monitoring the Air Quality of Radio Bands
show {802.11a |802.11b}cleanair air-quality Cisco_APViewing the Air Quality for an Access Point by Device Type (CLI)•See information for all of the interferers detected by a specific access point on the 802.11a/n or802.11b/g/n radio band by entering this command:show {802.11a | 802.11b} cleanair device ap Cisco_AP•See information for all of the interferers of a specific device type on the 802.11a/n or 802.11b/g/n radioband by entering this command:show {802.11a | 802.11b} cleanair device type typewhere you choose type as one of the following:◦802.11-fh—An 802.11 frequency-hopping device (802.11b/g/n only)◦802.11-inv—A device using spectrally inverted Wi-Fi signals◦802.11-nonstd—A device using nonstandard Wi-Fi channels◦802.15.4—An 802.15.4 device (802.11b/g/n only)◦all—All interference device types (this is the default value)◦bt-discovery—A bluetooth discovery (802.11b/g/n only)◦bt-link—A bluetooth link (802.11b/g/n only)◦canopy—A canopy bridge device◦cont-tx—A continuous transmitter◦dect-like—A digital enhanced cordless communication (DECT)-compatible phone◦jammer—A jamming device◦mw-oven—A microwave oven (802.11b/g/n only)◦superag—An 802.11 SuperAG device◦tdd-tx—A time division duplex (TDD) transmitter◦video camera—An analog video camera◦wimax-fixed—A WiMAX fixed device◦wimax-mobile—A WiMAX mobile device◦xbox—A Microsoft Xbox (802.11b/g/n only)Detecting Persistent Sources of Interference (CLI)See a list of persistent sources of interference for a specific access point on the 802.11a/n or 802.11b/g/n radioband by entering this command:show ap auto-rf {802.11a |802.11b}Cisco_APCisco Wireless LAN Controller Configuration Guide, Release 7.4       OL-28744-01 883Monitoring the Air Quality of Radio Bands
   Cisco Wireless LAN Controller Configuration Guide, Release 7.4884 OL-28744-01  Monitoring the Air Quality of Radio Bands
CHAPTER 136Configuring a Spectrum Expert Connection•Information About Spectrum Expert Connection, page 885•Configuring Spectrum Expert (GUI), page 885Information About Spectrum Expert ConnectionTo obtain detailed spectrum data that can be used to generate RF analysis plots similar to those provided bya spectrum analyzer, you can configure a Cisco CleanAir-enabled access point to connect directly to a MicrosoftWindows XP or Vista PC running the Spectrum Expert application (referred to as a Spectrum Expert console).You can initiate the Spectrum Expert connection semi-automatically from Prime Infrastructure or by manuallylaunching it from the Cisco WLC. This section provides instructions for the latter.Configuring Spectrum Expert (GUI)Before You BeginPrior to establishing a connection between the Spectrum Expert console and the access point, make sure thatIP address routing is properly configured and the network spectrum interface (NSI) ports are open in anyintervening firewalls.Step 1 Ensure that Cisco CleanAir functionality is enabled for the access point that will be connected to the Spectrum Expertconsole.Step 2 Configure the access point for SE-Connect mode using the Cisco WLC GUI or CLI.The SE-Connect mode is set for the entire access point, not just a single radio. However, the Spectrum Expertconsole connects to a single radio at a time.NoteIf you are using the Cisco WLC GUI, follow these steps:a) Choose Wireless >Access Points >All APs to open the All APs page.b) Click the name of the desired access point to open the All APs > Details for page.c) Choose SE-Connect from the AP Mode drop-down list. This mode is available only for access points that are capableof supporting Cisco CleanAir functionality. For the SE-Connect mode to appear as an available option, the accesspoint must have at least one spectrum-capable radio in the Enable state.Cisco Wireless LAN Controller Configuration Guide, Release 7.4        OL-28744-01 885
d) Click Apply to commit your changes.e) Click OK when prompted to reboot the access point.If you are using the CLI, follow these steps:a) To configure the access point for SE-Connect mode, enter this command:config ap mode se-connect Cisco_APb) When prompted to reboot the access point, enter Y.c) To verify the SE-Connect configuration status for the access point, enter this command:show ap config {802.11a |802.11b}Cisco_APInformation similar to the following appears:Cisco AP Identifier.............................. 0Cisco AP Name.................................... CISCO_AP3500...Spectrum Management InformationSpectrum Management Capable.............. YesSpectrum Management Admin State.......... EnabledSpectrum Management Operation State...... UpRapid Update Mode........................ DisabledSpectrum Expert connection............... EnabledSpectrum Sensor State.................. Configured (Error code = 0)Step 3 On the Windows PC, access the Cisco Software Center from this URL:http://www.cisco.com/cisco/software/navigator.htmlStep 4 Click Product > Wireless > Cisco Spectrum Intelligence >Cisco Spectrum Expert >Cisco Spectrum Expert Wi-Fi,and then download the Spectrum Expert 4.0 executable (*.exe) file.Step 5 Run the Spectrum Expert application on the PC.Step 6 When the Connect to Sensor dialog box appears, enter the IP address of the access point, choose the access point radio,and enter the 16-byte network spectrum interface (NSI) key to authenticate. The Spectrum Expert application opens aTCP/IP connection directly to the access point using the NSI protocol.The access point must be a TCP server listening on ports 37540 for 2.4 GHz and 37550 for 5 GHz frequencies.These ports must be opened for the spectrum expert application to connect to the access point using the NSIprotocol.NoteOn the Cisco WLC GUI, the NSI key appears in the Network Spectrum Interface Key field (below the PortNumber field) on the All APs > Details for page. To view the NSI key from the Cisco WLC CLI, enter the showap config {802.11a |802.11b}Cisco_AP command.NoteWhen an access point in SE-Connect mode joins a Cisco WLC, it sends a Spectrum Capabilities notification message,and the Cisco WLC responds with a Spectrum Configuration Request. The request contains the 16-byte random NSI keygenerated by the Cisco WLC for use in NSI authentication. The Cisco WLC generates one key per access point, whichthe access point stores until it is rebooted.You can establish up to three Spectrum Expert console connections per access point radio. The Number ofSpectrum Expert Connections text box on the 802.11a/n (or 802.11b/g/n) Cisco APs > Configure page of theCisco WLC GUI shows the number of Spectrum Expert applications that are currently connected to the accesspoint radio.Note   Cisco Wireless LAN Controller Configuration Guide, Release 7.4886 OL-28744-01  Configuring Spectrum Expert (GUI)
Step 7 Verify that the Spectrum Expert console is connected to the access point by selecting the Slave Remote Sensor text boxin the bottom right corner of the Spectrum Expert application. If the two devices are connected, the IP address of theaccess point appears in this text box.Step 8 Use the Spectrum Expert application to view and analyze spectrum data from the access point.Cisco Wireless LAN Controller Configuration Guide, Release 7.4       OL-28744-01 887Configuring Spectrum Expert (GUI)
   Cisco Wireless LAN Controller Configuration Guide, Release 7.4888 OL-28744-01  Configuring Spectrum Expert (GUI)
PART IXConfiguring FlexConnect•Configuring FlexConnect, page 891•Configuring FlexConnect ACLs, page 909•Configuring FlexConnect Groups, page 915•Configuring AAA Overrides for FlexConnect, page 923•Configuring FlexConnect AP Upgrades for FlexConnect APs, page 927
CHAPTER 137Configuring FlexConnect•Information About FlexConnect, page 891•Restrictions for FlexConnect, page 896•Configuring FlexConnect, page 897Information About FlexConnectFlexConnect (previously known as Hybrid Remote Edge Access Point or H-REAP) is a wireless solution forbranch office and remote office deployments. It enables customers to configure and control access points ina branch or remote office from the corporate office through a wide area network (WAN) link without deployinga controller in each office. The FlexConnect access points can switch client data traffic locally and performclient authentication locally when their connection to the controller is lost. When they are connected to thecontroller, they can also send traffic back to the controller. In the connected mode, the FlexConnect accesspoint can also perform local authentication.This figure shows a typical FlexConnect deployment.Figure 67: FlexConnect DeploymentCisco Wireless LAN Controller Configuration Guide, Release 7.4        OL-28744-01 891
The controller software has a more robust fault tolerance methodology to FlexConnect access points. Inprevious releases, whenever a FlexConnect access point disassociates from a controller, it moves to thestandalone mode. The clients that are centrally switched are disassociated. However, the FlexConnect accesspoint continues to serve locally switched clients. When the FlexConnect access point rejoins the controller(or a standby controller), all clients are disconnected and are authenticated again. This functionality has beenenhanced and the connection between the clients and the FlexConnect access points are maintained intact andthe clients experience seamless connectivity. This feature can be used only when both the access point andthe controller have the same configuration.Clients that are centrally authenticated are reauthenticated.Session timeout and reauthentication is performed when the access point establishes a connected to thecontroller.After the client connection has been established, the controller does not restore the original attributes of theclient. The client username, current rate and supported rates, and listen interval values are reset to the defaultvalues only after the session timer expires.There is no deployment restriction on the number of FlexConnect access points per location. MultipleFlexConnect groups can be defined in a single location.The controller can send multicast packets in the form of unicast or multicast packets to the access point. InFlexConnect mode, the access point can receive multicast packets only in unicast form.FlexConnect access points support a 1-1 network address translation (NAT) configuration. They also supportport address translation (PAT) for all features except true multicast. Multicast is supported across NATboundaries when configured using the Unicast option. FlexConnect access points also support a many-to-oneNAT/PAT boundary, except when you want true multicast to operate for all centrally switched WLANs.Although NAT and PAT are supported for FlexConnect access points, they are not supported on thecorresponding controller. Cisco does not support configurations in which the controller is behind aNAT/PAT boundary.NoteVPN and PPTP are supported for locally switched traffic if these security types are accessible locally at theaccess point.FlexConnect access points support multiple SSIDs.Workgroup bridges and Universal Workgroup bridges are supported on FlexConnect access points for locallyswitched clients.FlexConnect supports IPv6 clients by bridging the traffic to local VLAN, similar to IPv4 operation. FlexConnectsupports Client Mobility for a group of up to 100 access points.FlexConnect Authentication ProcessWhen an access point boots up, it looks for a controller. If it finds one, it joins the controller, downloads thelatest software image and configuration from the controller, and initializes the radio. It saves the downloadedconfiguration in nonvolatile memory for use in standalone mode.Once the access point is rebooted after downloading the latest controller software, it must be convertedto the FlexConnect mode. This can done using the GUI or CLI.Note   Cisco Wireless LAN Controller Configuration Guide, Release 7.4892 OL-28744-01  Information About FlexConnect
A FlexConnect access point can learn the controller IP address in one of these ways:•If the access point has been assigned an IP address from a DHCP server, it can discover a controllerthrough the regular CAPWAP or LWAPP discovery process.OTAP is no longer supported on the controllers with 6.0.196 code and above.Note•If the access point has been assigned a static IP address, it can discover a controller through any of thediscovery process methods except DHCP option 43. If the access point cannot discover a controllerthrough Layer 3 broadcast, we recommend DNS resolution. With DNS, any access point with a staticIP address that knows of a DNS server can find at least one controller.•If you want the access point to discover a controller from a remote network where CAPWAP or LWAPPdiscovery mechanisms are not available, you can use priming. This method enables you to specify(through the access point CLI) the controller to which the access point is to connect.For more information about how access points find controllers, see the controllerdeployment guide at: http://www.cisco.com/en/US/docs/wireless/technology/controller/deployment/guide/dep.html.NoteWhen a FlexConnect access point can reach the controller (referred to as the connected mode), the controllerassists in client authentication. When a FlexConnect access point cannot access the controller, the access pointenters the standalone mode and authenticates clients by itself.The LEDs on the access point change as the device enters different FlexConnect modes. See the hardwareinstallation guide for your access point for information on LED patterns.NoteWhen a client associates to a FlexConnect access point, the access point sends all authentication messages tothe controller and either switches the client data packets locally (locally switched) or sends them to thecontroller (centrally switched), depending on the WLAN configuration. With respect to client authentication(open, shared, EAP, web authentication, and NAC) and data packets, the WLAN can be in any one of thefollowing states depending on the configuration and state of controller connectivity:•central authentication, central switching—In this state, the controller handles client authentication, andall client data is tunneled back to the controller. This state is valid only in connected mode.•central authentication, local switching—In this state, the controller handles client authentication, andthe FlexConnect access point switches data packets locally. After the client authenticates successfully,the controller sends a configuration command with a new payload to instruct the FlexConnect accesspoint to start switching data packets locally. This message is sent per client. This state is applicable onlyin connected mode.•local authentication, local switching—In this state, the FlexConnect access point handles clientauthentication and switches client data packets locally. This state is valid in standalone mode andconnected mode.In connected mode, the access point provides minimal information about the locally authenticated clientto the controller. The following information is not available to the controller:Cisco Wireless LAN Controller Configuration Guide, Release 7.4       OL-28744-01 893Information About FlexConnect
◦Policy type◦Access VLAN◦VLAN name◦Supported rates◦Encryption cipherLocal authentication is useful where you cannot maintain a remote office setup of a minimumbandwidth of 128 kbps with the round-trip latency no greater than 100 ms and the maximumtransmission unit (MTU) no smaller than 500 bytes. In local authentication, the authenticationcapabilities are present in the access point itself. Local authentication reduces the latencyrequirements of the branch office.Local authentication can only be enabled on the WLAN of a FlexConnect access pointthat is in local switching mode.Notes about local authentication are as follows:Note◦Guest authentication cannot be done on a FlexConnect local authentication-enabled WLAN.◦Local RADIUS on the controller is not supported.◦Once the client has been authenticated, roaming is only supported after the controller and the otherFlexConnect access points in the group are updated with the client information.◦Local authentication in connected mode requires a WLAN configuration.When locally switched clients that are connected to a FlexConnect access point renewthe IP addresses, on joining back, the client continues to stay in the run state. Theseclients are not reauthenticated by the controller.Note•authentication down, switch down—In this state, the WLAN disassociates existing clients and stopssending beacon and probe requests. This state is valid in both standalone mode and connected mode.•authentication down, local switching—In this state, the WLAN rejects any new clients trying toauthenticate, but it continues sending beacon and probe responses to keep existing clients alive. Thisstate is valid only in standalone mode.When a FlexConnect access point enters standalone mode, WLANs that are configured for open, shared,WPA-PSK, or WPA2-PSK authentication enter the “local authentication, local switching”state and continuenew client authentications. In controller software release 4.2 or later releases, this configuration is also correctfor WLANs that are configured for 802.1X, WPA-802.1X, WPA2-802.1X, or CCKM, but these authenticationtypes require that an external RADIUS server be configured. You can also configure a local RADIUS serveron a FlexConnect access point to support 802.1X in a standalone mode or with local authentication.Other WLANs enter either the “authentication down, switching down”state (if the WLAN was configuredfor central switching) or the “authentication down, local switching”state (if the WLAN was configured forlocal switching).   Cisco Wireless LAN Controller Configuration Guide, Release 7.4894 OL-28744-01  Information About FlexConnect
When FlexConnect access points are connected to the controller (rather than in standalone mode), the controlleruses its primary RADIUS servers and accesses them in the order specified on the RADIUS AuthenticationServers page or in the config radius auth add CLI command (unless the server order is overridden for aparticular WLAN). However, to support 802.1X EAP authentication, FlexConnect access points in standalonemode need to have their own backup RADIUS server to authenticate clients.A controller does not use a backup RADIUS server. The controller uses the backup RADIUS server inlocal authentication mode.NoteYou can configure a backup RADIUS server for individual FlexConnect access points in standalone modeby using the controller CLI or for groups of FlexConnect access points in standalone mode by using eitherthe GUI or CLI. A backup server configured for an individual access point overrides the backup RADIUSserver configuration for a FlexConnect.When a FlexConnect access point enters standalone mode, it disassociates all clients that are on centrallyswitched WLANs. For web-authentication WLANs, existing clients are not disassociated, but the FlexConnectaccess point stops sending beacons when the number of associated clients reaches zero (0). It also sendsdisassociation messages to new clients associating to web-authentication WLANs. Controller-dependentactivities, such as network access control (NAC) and web authentication (guest access), are disabled, and theaccess point does not send any intrusion detection system (IDS) reports to the controller. Most radio resourcemanagement (RRM) features (such as neighbor discovery; noise, interference, load, and coverage measurements;use of the neighbor list; and rogue containment and detection) are disabled. However, a FlexConnect accesspoint supports dynamic frequency selection in standalone mode.When web-authentication is used on FlexConnect access points at a remote site, the clients get the IP addressfrom the remote local subnet. To resolve the initial URL request, the DNS is accessible through the subnet'sdefault gateway. In order for the controller to intercept and redirect the DNS query return packets, thesepackets must reach the controller at the data center through a CAPWAP connection. During theweb-authentication process, the FlexConnect access points allows only DNS and DHCP messages; the accesspoints forward the DNS reply messages to the controller before web-authentication for the client is complete.After web-authentication for the client is complete, all the traffic is switched locally.If your controller is configured for NAC, clients can associate only when the access point is in connectedmode. When NAC is enabled, you need to create an unhealthy (or quarantined) VLAN so that the datatraffic of any client that is assigned to this VLAN passes through the controller, even if the WLAN isconfigured for local switching. After a client is assigned to a quarantined VLAN, all of its data packetsare centrally switched. See the Configuring Dynamic Interfaces section for information about creatingquarantined VLANs and the Configuring NAC Out-of-Band section for information about configuringNAC out-of-band support.NoteWhen a FlexConnect access point enters into a standalone mode, the following occurs:•The access point checks whether it is able to reach the default gateway via ARP. If so, it will continueto try and reach the controller.If the access point fails to establish the ARP, the following occurs:•The access point attempts to discover for five times and if it still cannot find the controller, it tries torenew the DHCP on the ethernet interface to get a new DHCP IP.Cisco Wireless LAN Controller Configuration Guide, Release 7.4       OL-28744-01 895Information About FlexConnect
•The access point will retry for five times, and if that fails, the access point will renew the IP address ofthe interface again, this will happen for three attempts.•If the three attempts fail, the access point will fall back to the static IP and will reboot (only if the accesspoint is configured with a static IP).•Reboot is done to remove the possibility of any unknown error the access point configuration.Once the access point reestablishes a connection with the controller, it disassociates all clients, applies newconfiguration information from the controller, and allows client connectivity again.Restrictions for FlexConnect•When you apply a configuration change to a locally switched WLAN, the access point resets the radio,causing associated client devices to disassociate (including the clients that are not associated to themodified WLAN). However, this behavior does not occur if the modified WLAN is centrally switched.We recommend that you perform a configuration change only during a maintenance window.•You can deploy a FlexConnect access point with either a static IP address or a DHCP address. In thecase of DHCP, a DHCP server must be available locally and must be able to provide the IP address forthe access point at bootup.•FlexConnect supports up to four fragmented packets or a minimum 500-byte maximum transmissionunit (MTU) WAN link.•FlexConnect is supported only on the following access points: 1040, 1130, 1140, 1250, 1240, 1260,1600, 1550, 2600, 3500, 3600, OEAP 600, ISR 891, and ISR 881.•Round-trip latency must not exceed 300 milliseconds (ms) between the access point and the controller,and CAPWAP control packets must be prioritized over all other traffic. In cases where you cannotachieve the 300 milliseconds round-trip latency, you can configure the access point to perform localauthentication.•Client connections are restored only for locally switched clients that are in the RUN state when theaccess point moves from standalone mode to connected mode. After the access point moves from thestandalone mode to the connected mode, the access point’s radio is also reset.•The configuration on the controller must be the same between the time the access point went intostandalone mode and the time the access point came back to connected mode. Similarly, if the accesspoint is falling back to a secondary or backup controller, the configuration between the primary andsecondary or backup controller must be the same.•A newly connected access point cannot be booted in FlexConnect mode.•To use CCKM fast roaming with FlexConnect access points, you must configure FlexConnect Groups.•NAC out-of-band integration is supported only on WLANs configured for FlexConnect central switching.It is not supported for use on WLANs configured for FlexConnect local switching.•The primary and secondary controllers for a FlexConnect access point must have the same configuration.Otherwise, the access point might lose its configuration, and certain features (such as WLAN overrides,VLANs, static channel number, and so on) might not operate correctly. In addition, make sure to duplicatethe SSID of the FlexConnect access point and its index number on both controllers.   Cisco Wireless LAN Controller Configuration Guide, Release 7.4896 OL-28744-01  Restrictions for FlexConnect
•The QoS profile per-user bandwidth contracts are not supported for FlexConnect locally switchedWLANs. The QoS per-user bandwidth contracts are only supported for centrally switched WLANs andAPs in the local mode.•Do not connect access points in FlexConnect mode directly to a 2500 Series Controller.•If you configure a FlexConnect access point with a syslog server configured on the access point, afterthe access point is reloaded and the native VLAN other than 1, at time of initialization, few syslogpackets from the access point are tagged with VLAN ID 1. This is a known issue.•MAC Filtering is not supported on FlexConnect access points in standalone mode. However, MACFiltering is supported on FlexConnect access points in connected mode with local switching and centralauthentication. Also, Open SSID, MAC Filtering, and RADIUS NAC for a locally switched WLANwith FlexConnect access points is a valid configuration where MAC is checked by ISE.•FlexConnect does not support IPv6 ACLs, neighbor discovery caching, and DHCPv6 snooping of IPv6NDP packets.•FlexConnect does not display any IPv6 client addresses within the client detail page.•FlexConnect Access Points with Locally Switched WLAN cannot perform IP Source Guard and preventARP spoofing. For Centrally Switched WLAN, the wireless controller performs the IP Source Guardand ARP Spoofing.•To prevent ARP spoofing attacks in FlexConnect AP with Local Switching, we recommend that youuse ARP Inspection.•When you enable local switching on WLAN for the Flexconnect APs, then APs perform local switching.However, for the APs in local mode, central switching is performed.•For Wi-Fi Protected Access version 2 (WPA2) in FlexConnect standalone mode or local-auth in connectedmode or CCKM fast-roaming in connected mode, only Advanced Encryption Standard (AES) is supported.•For Wi-Fi Protected Access (WPA) in FlexConnect standalone mode or local-auth in connected modeor CCKM fast-roaming in connected mode, only Temporal Key Integrity Protocol (TKIP) is supported.•WPA2 with TKIP and WPA with AES is not supported in standalone mode, local-auth in connectedmode, and CCKM fast-roaming in connected mode.•AVC is not supported on APs in FlexConnect local switched mode.Configuring FlexConnectThe configuration tasks must be performed in the order in which they are listed.NoteConfiguring the Switch at a Remote SiteStep 1 Attach the access point that will be enabled for FlexConnect to a trunk or access port on the switch.The sample configuration in this procedure shows the FlexConnect access point connected to a trunk port onthe switch.NoteCisco Wireless LAN Controller Configuration Guide, Release 7.4       OL-28744-01 897Configuring FlexConnect
Step 2 See the sample configuration in this procedure to configure the switch to support the FlexConnect access point.In this sample configuration, the FlexConnect access point is connected to trunk interface FastEthernet 1/0/2 with nativeVLAN 100. The access point needs IP connectivity on the native VLAN. The remote site has local servers/resources onVLAN 101. A DHCP pool is created in the local switch for both VLANs in the switch. The first DHCP pool (NATIVE)is used by the FlexConnect access point, and the second DHCP pool (LOCAL-SWITCH) is used by the clients whenthey associate to a WLAN that is locally switched. The bolded text in the sample configuration shows these settings.A sample local switch configuration is as follows:ip dhcp pool NATIVEnetwork 209.165.200.224 255.255.255.224default-router 209.165.200.225dns-server 192.168.100.167!ip dhcp pool LOCAL-SWITCHnetwork 209.165.201.224 255.255.255.224default-router 209.165.201.225dns-server 192.168.100.167!interface FastEthernet1/0/1description Uplink portno switchportip address 209.165.202.225 255.255.255.224!interface FastEthernet1/0/2description the Access Point portswitchport trunk encapsulation dot1qswitchport trunk native vlan 100switchport trunk allowed vlan 101switchport mode trunk!interface Vlan100ip address 209.165.200.225 255.255.255.224!interface Vlan101ip address 209.165.201.225 255.255.255.224end!Configuring the Controller for FlexConnectYou can configure the controller for FlexConnect in two environments:•Centrally switched WLAN•Locally switched WLANThe controller configuration for FlexConnect consists of creating centrally switched and locally switchedWLANs. This table shows three WLAN scenarios.   Cisco Wireless LAN Controller Configuration Guide, Release 7.4898 OL-28744-01  Configuring FlexConnect
Table 26: WLANs ExampleInterface Mapping (VLAN)SwitchingAuthenticationSecurityWLANmanagement (centrallyswitched VLAN)CentralCentralWPA1+WPA2employee101 (locally switchedVLAN)LocalLocalWPA1+WPA2(PSK)employee-localmanagement (centrallyswitched VLAN)CentralCentralWeb authenticationguest-central101 (locally switchedVLAN)LocalLocalWPA1+WPA2employee-local-authConfiguring the Controller for FlexConnect for a Centrally Switched WLAN Used for Guest AccessBefore You BeginYou must have created guest user accounts. For more information about creating guest user accounts, see theCisco Wireless LAN Controller System Management Guide.Step 1 Choose WLANs to open the WLANs page.Step 2 From the drop-down list, choose Create New and click Go to open the WLANs > New page .Step 3 From the Type drop-down list, choose WLAN.Step 4 In the Profile Name text box, enter guest-central.Step 5 In the WLAN SSID text box, enter guest-central.Step 6 From the WLAN ID drop-down list, choose an ID for the WLAN.Step 7 Click Apply. The WLANs > Edit page appears.Step 8 In the General tab, select the Status check box to enable the WLAN.Step 9 In the Security > Layer 2 tab, choose None from the Layer 2 Security drop-down list.Step 10 In the Security > Layer 3 tab:a) Choose None from the Layer 3 Security drop-down list.b) Choose the Web Policy check box.c) Choose Authentication.NoteIf you are using an external web server, you must configure a preauthentication access control list (ACL) on theWLAN for the server and then choose this ACL as the WLAN preauthentication ACL on the Layer 3 tab.Step 11 Click Apply.Step 12 Click Save Configuration.Cisco Wireless LAN Controller Configuration Guide, Release 7.4       OL-28744-01 899Configuring FlexConnect
Configuring the Controller for FlexConnect (GUI)Step 1 Choose WLANs to open the WLANs page.Step 2 From the drop-down list, choose Create New and click Go to open the WLANs > New page.Step 3 From the Type drop-down list, choose WLAN.Step 4 In the Profile Name text box, enter a unique profile name for the WLAN.Step 5 In the WLAN SSID text box, enter a name for the WLAN.Step 6 From the WLAN ID drop-down list, choose the ID number for this WLAN.Step 7 Click Apply to commit your changes. The WLANs > Edit page appears.Step 8 You can configure the controller for FlexConnect in both centrally switched and locally switched WLANs:To configure the controller for FlexConnect in a centrally switched WLAN:a) In the General tab, select the Status check box to enable the WLAN.b) If you have enabled NAC and have created a quarantined VLAN and want to use it for this WLAN, select the interfacefrom the Interface/Interface Group(G) drop-down list in the General tab.c) In the Security > Layer 2 tab, choose WPA+WPA2 from the Layer 2 Security drop-down list and then set theWPA+WPA2 parameters as required.To configure the controller for FlexConnect in a locally switched WLAN:a) In the General tab, select the Status check box to enable the WLAN.b) If you have enabled NAC and have created a quarantined VLAN and want to use it for this WLAN, select the interfacefrom the Interface/Interface Group(G) drop-down list in the General tab.c) In the Security > Layer 2 tab, select WPA+WPA2 from the Layer 2 Security drop-down list and then set theWPA+WPA2 parameters as required.d) In the Advanced tab:•Select or unselect the FlexConnect Local Switching check box to enable or disable local switching of clientdata associated with the APs in FlexConnect mode.The guidelines and limitations for this feature are as follows:Note•When you enable local switching, any FlexConnect access point that advertises this WLAN isable to locally switch data packets (instead of tunneling them to the controller).•When you enable FlexConnect local switching, the controller is enabled to learn the client’s IPaddress by default. However, if the client is configured with Fortress Layer 2 encryption, thecontroller cannot learn the client’s IP address, and the controller periodically drops the client.Disable the client IP address learning feature so that the controller maintains the client connectionwithout waiting to learn the client’s IP address. The ability to disable this option is supportedonly with FlexConnect local switching; it is not supported with FlexConnect central switching.•For FlexConnect access points, the interface mapping at the controller for WLANs that isconfigured for FlexConnect Local Switching is inherited at the access point as the default VLANtagging. This mapping can be changed per SSID and per FlexConnect access point.Non-FlexConnect access points tunnel all traffic back to the controller, and VLAN tagging isdetermined by each WLAN’s interface mapping.•Select or unselect the FlexConnect Local Auth check box to enable or disable local authentication for theWLAN.   Cisco Wireless LAN Controller Configuration Guide, Release 7.4900 OL-28744-01  Configuring FlexConnect
•Select or unselect the Learn Client IP Address check box to enable or disable the IP address of the client tobe learned.•Select or unselect the VLAN based Central Switching check box to enable or disable central switching on alocally switched WLAN based on AAA overridden VLAN.These are the guidelines and limitations for this feature:Note•Multicast on overridden interfaces is not supported.•This feature is available only on a per-WLAN basis, where the WLAN is locally switched.•IPv6 ACLs, CAC, NAC, and IPv6 are not supported.•IPv4 ACLs are supported only with VLAN-based central switching enabled and applicable onlyto central switching clients on the WLAN.•This feature is applicable to APs in FlexConnect mode in locally switched WLANs.•This feature is not applicable to APs in Local mode.•This feature is not supported on APs in FlexConnect mode in centrally switched WLANs.•This feature is supported on central authentication only.•This features is not supported on web authentication security clients.•Layer 3 roaming for local switching clients is not supported.•Select or unselect the Central DHCP Processing check box to enable or disable the feature. When you enablethis feature, the DHCP packets received from AP are centrally switched to the controller and then forwardedto the corresponding VLAN based on the AP and the SSID.•Select or unselect the Override DNS check box to enable or disable the overriding of the DNS server addresson the interface assigned to the locally switched WLAN. When you override DNS in centrally switched WLANs,the clients get their DNS server IP address from the AP, not from the controller.•Select or unselect the NAT-PAT check box to enable or disable Network Address Translation (NAT) and PortAddress Translation (PAT) on locally switched WLANs. You must enable Central DHCP Processing to enableNAT and PAT.Step 9 Click Apply.Step 10 Click Save Configuration.Configuring the Controller for FlexConnect (CLI)•config wlan flexconnect local-switching wlan_id enable—Configures the WLAN for local switching.Cisco Wireless LAN Controller Configuration Guide, Release 7.4       OL-28744-01 901Configuring FlexConnect
When you enable FlexConnect local switching, the controller waits to learn the clientIP address by default. However, if the client is configured with Fortress Layer 2encryption, the controller cannot learn the client IP address, and the controller periodicallydrops the client. Use the config wlan flexconnect learn-ipaddr wlan_id disablecommand to disable the client IP address learning feature so that the controller maintainsthe client connection without waiting to learn the client’s IP address. The ability todisable this feature is supported only with FlexConnect local switching; it is not supportedwith FlexConnect central switching. To enable this feature, enter the config wlanflexconnect learn-ipaddr wlan_id enable command.NoteWhen a WLAN is locally switched (LS), you must use the config wlan flexconnectlearn-ipaddr wlan-id {enable |disable} command. When the WLAN is centrallyswitched (CS), you must use the config wlan learn-ipaddr-cswlan wlan-id {enable |disable} command.Note•config wlan flexconnect local-switching wlan_id {enable |disable}—Configures the WLAN for centralswitching.•config wlan flexconnect vlan-central-switching wlan_id {enable |disable}—Configures centralswitching on a locally switched WLAN based on an AAA overridden VLAN.The guidelines and limitations for this feature are as follows:•Multicast on overridden interfaces is not supported.•This feature is available only on a per-WLAN basis, where the WLAN is locally switched.•IPv6 ACLs, CAC, NAC, and IPv6 are not supported.•IPv4 ACLs are supported only with VLAN-based central switching enabled and applicable onlyto central switching clients on the WLAN.•This feature is applicable to APs in FlexConnect mode in locally switched WLANs.•This feature is not applicable to APs in Local mode.•This feature is not supported on APs in FlexConnect mode in centrally switched WLANs.•This feature is supported on central authentication only.•This features is not supported on web authentication security clients.•Layer 3 roaming for local switching clients is not supported.Use these commands to get FlexConnect information:•show ap config general Cisco_AP—Shows VLAN configurations.•show wlan wlan_id—Shows whether the WLAN is locally or centrally switched.•show client detail client_mac—Shows whether the client is locally or centrally switched.Use these commands to obtain debug information:   Cisco Wireless LAN Controller Configuration Guide, Release 7.4902 OL-28744-01  Configuring FlexConnect
•debug flexconnect aaa {event |error} {enable |disable}—Enables or disables debugging ofFlexConnect backup RADIUS server events or errors.•debug flexconnect cckm {enable |disable}—Enables or disables debugging of FlexConnect CCKM.•debug flexconnect {enable |disable}—Enables or disables debugging of FlexConnect Groups.•debug pem state {enable |disable}—Enables or disables debugging of the policy manager state machine.•debug pem events {enable |disable}—Enables or disables debugging of policy manager events.Configuring an Access Point for FlexConnectConfiguring an Access Point for FlexConnect (GUI)Ensure that the access point has been physically added to your network.Step 1 Choose Wireless to open the All APs page.Step 2 Click the name of the desired access point. The All APs > >Details page appears.Step 3 From the AP Mode drop-down list, choose FlexConnect to enable FlexConnect for this access point.The last parameter in the Inventory tab indicates whether the access point can be configured for FlexConnect.NoteStep 4 Click Apply to commit your changes and to cause the access point to reboot.Step 5 Choose the FlexConnect tab to open the All APs > Details for (FlexConnect) page.If the access point belongs to a FlexConnect group, the name of the group appears in the FlexConnect Name text box.Step 6 Select the VLAN Support check box and enter the number of the native VLAN on the remote network (such as 100)in the Native VLAN ID text box.By default, a VLAN is not enabled on the FlexConnect access point. After FlexConnect is enabled, the accesspoint inherits the VLAN ID associated to the WLAN. This configuration is saved in the access point and receivedafter the successful join response. By default, the native VLAN is 1. One native VLAN must be configured perFlexConnect access point in a VLAN-enabled domain. Otherwise, the access point cannot send and receivepackets to and from the controller.NoteTo preserve the VLAN mappings in the access point after an upgrade or downgrade, it is necessary that theaccess point join is restricted to the controller for which it is primed. That is, no other discoverable controllerwith a different configuration should be available by other means. Similarly, at the time the access point joins,if it moves across controllers that have different VLAN mappings, the VLAN mappings at the access point mayget mismatched.NoteStep 7 Click Apply. The access point temporarily loses its connection to the controller while its Ethernet port is reset.Step 8 Click the name of the same access point and then click the FlexConnect tab.Step 9 Click VLAN Mappings to open the All APs >Access Point Name > VLAN Mappings page.Step 10 Enter the number of the VLAN from which the clients will get an IP address when doing local switching (VLAN 101,in this example) in the VLAN ID text box.Step 11 To configure Web Authentication ACLs, do the following:a) Click the External WebAuthentication ACLs link to open the ACL mappings page. The ACL Mappings page listsdetails of WLAN ACL mappings and web policy ACLs.b) In the WLAN Id box, enter the WLAN ID.c) From the WebAuth ACL drop-down list, choose the FlexConnect ACL.Cisco Wireless LAN Controller Configuration Guide, Release 7.4       OL-28744-01 903Configuring FlexConnect
To create a FlexConnect ACL, choose Wireless > FlexConnect Groups > FlexConnect ACLs, click New,enter the FlexConnect ACL name, and click Apply.Noted) Click Add.e) Click Apply.Step 12 To configure Local Split ACLs:a) Click the Local Split ACLs link to open the ACL Mappings page.b) In the WLAN Id box, enter the WLAN ID.c) From the Local-Split ACL drop-down list, choose the FlexConnect ACL.To create a FlexConnect ACL, choose Wireless > FlexConnect Groups > FlexConnect ACLs, click New,enter the FlexConnect ACL name, and click Apply.NoteIf a client that connects over a WAN link associated with a centrally switched WLAN has to send some traffic to adevice present in the local site, the client has to send traffic over CAPWAP to the controller and then get the sametraffic back to the local site either over CAPWAP or using some offband connectivity. This process unnecessarilyconsumes WAN link bandwidth. To avoid this issue, you can use the split tunneling feature, which allows the trafficsent by a client to be classified based on the packet contents. The matching packets are locally switched and the restof the traffic is centrally switched. The traffic that is sent by the client that matches the IP address of the devicepresent in the local site can be classified as locally switched traffic and the rest of the traffic as centrally switched.To configure local split tunneling on an AP, ensure that you have enabled DCHP Required on the WLAN, whichensures that the client associating with the split WLAN does DHCP.Local split tunneling is not supported on Cisco 1500 Series, Cisco 1130, and Cisco 1240 access points, anddoes not work for clients with static IP address.Noted) Click Add.Step 13 To configure Central DHCP processing:a) In the WLAN Id box, enter the WLAN ID with which you want to map Central DHCP.b) Select or unselect the Central DHCP check box to enable or disable Central DHCP for the mapping.c) Select or unselect the Override DNS check box to enable or disable overriding of DNS for the mapping.d) Select or unselect the NAT-PAT check box to enable or disable network address translation and port address translationfor the mapping.e) Click Add to add the Central DHCP - WLAN mapping.Step 14 To map a locally switched WLAN with a WebAuth ACL, follow these steps:a) In the WLAN Id box, enter the WLAN ID.b) From the WebAuth ACL drop-down list, choose the FlexConnect ACL.To create a FlexConnect ACL, choose Wireless > FlexConnect Groups > FlexConnect ACLs, click New,enter the FlexConnect ACL name, and click Apply.Notec) Click Add.The FlexConnect ACLs that are specific to an AP have the highest priority. The FlexConnect ACLs that arespecific to WLANs have the lowest priority.NoteStep 15 From the WebPolicy ACL drop-down list, choose a FlexConnect ACL and then click Add to configure the FlexConnectACL as a web policy.You can configure up to 16 Web Policy ACLs that are specific to an accesspoint.NoteStep 16 Click Apply.Step 17 Click Save Configuration.Repeat this procedure for any additional access points that need to be configured for FlexConnect at the remotesite.Note   Cisco Wireless LAN Controller Configuration Guide, Release 7.4904 OL-28744-01  Configuring FlexConnect
Configuring an Access Point for FlexConnect (CLI)•config ap mode flexconnect Cisco_AP—Enables FlexConnect for this access point.•config ap flexconnect radius auth set {primary | secondary}ip_address auth_port secretCisco_AP—Configures a primary or secondary RADIUS server for a specific FlexConnect access point.Only the Session Timeout RADIUS attribute is supported in standalone mode. All otherattributes as well as RADIUS accounting are not supported.NoteTo delete a RADIUS server that is configured for a FlexConnect access point, enter theconfig ap flexconnect radius auth delete {primary | secondary}Cisco_AP command.Note•config ap flexconnect vlan wlan wlan_id vlan-id Cisco_AP—Enables you to assign a VLAN ID to thisFlexConnect access point. By default, the access point inherits the VLAN ID associated to the WLAN.•config ap flexconnect vlan {enable | disable}Cisco_AP—Enables or disables VLAN tagging for thisFlexConnect access point. By default, VLAN tagging is not enabled. After VLAN tagging is enabledon the FlexConnect access point, WLANs that are enabled for local switching inherit the VLAN assignedat the controller.•config ap flexconnect vlan native vlan-id Cisco_AP—Enables you to configure a native VLAN forthis FlexConnect access point. By default, no VLAN is set as the native VLAN. One native VLAN mustbe configured per FlexConnect access point (when VLAN tagging is enabled). Make sure the switchport to which the access point is connected has a corresponding native VLAN configured as well. If theFlexConnect access point’s native VLAN setting and the upstream switch port native VLAN do notmatch, the access point cannot transmit packets to and from the controller.To save the VLAN mappings in the access point after an upgrade or downgrade, youshould restrict the access point to join the controller for which it is primed. No otherdiscoverable controller with a different configuration should be available by other means.Similarly, at the time the access point joins, if it moves across controllers that havedifferent VLAN mappings, the VLAN mappings at the access point might getmismatched.Note•Configure the mapping of a Web-Auth or a Web Passthrough ACL to a WLAN for an access point inFlexConnect mode by entering this command:config ap flexconnect web-auth wlan wlan_id cisco_ap acl_name {enable |disable}Cisco Wireless LAN Controller Configuration Guide, Release 7.4       OL-28744-01 905Configuring FlexConnect
The FlexConnect ACLs that are specific to an AP have the highest priority. TheFlexConnect ACLs that are specific to WLANs have the lowest priority.Note•Configure a Policy ACL on an AP in FlexConnect mode by entering this command:config ap flexconnect acl {add |delete}acl_name cisco_apYou can configure up to 16 Policy ACLs that are specific to an access point.Note•To configure local split tunneling on a per-AP basis, enter this command:config ap local-split {enable |disable}wlan-id acl acl-name ap-name•Configure central DHCP on the AP per WLAN by entering this command:config ap flexconnect central-dhcp wlan-id ap-name {enable override dns |disable |delete}The gratuitous ARP for the gateway is sent by the access point to the client, whichobtained an IP address from the central site. This is performed to proxy the gateway bythe access point.NoteUse these commands on the FlexConnect access point to get status information:•show capwap reap status—Shows the status of the FlexConnect access point (connected or standalone).•show capwap reap association—Shows the list of clients associated to this access point and their SSIDs.Use these commands on the FlexConnect access point to get debug information:•debug capwap reap—Shows general FlexConnect activities.•debug capwap reap mgmt—Shows client authentication and association messages.•debug capwap reap load—Shows payload activities, which are useful when the FlexConnect accesspoint boots up in standalone mode.•debug dot11 mgmt interface—Shows 802.11 management interface events.•debug dot11 mgmt msg—Shows 802.11 management messages.•debug dot11 mgmt ssid—Shows SSID management events.•debug dot11 mgmt state-machine—Shows the 802.11 state machine.•debug dot11 mgmt station—Shows client events.   Cisco Wireless LAN Controller Configuration Guide, Release 7.4906 OL-28744-01  Configuring FlexConnect
Configuring an Access Point for Local Authentication on a WLAN (GUI)Step 1 Choose WLANs to open the WLANs page.Step 2 Click the ID of the WLAN. The WLANs > Edit page appears.Step 3 Clicked the Advanced tab to open the WLANs >Edit (WLAN Name) page.Step 4 Select the FlexConnect Local Switching check box to enable FlexConnect local switching.Step 5 Select the FlexConnect Local Auth check box to enable FlexConnect local authentication.Do not connect access points in FlexConnect mode directly to 2500 Series Controllers.CautionStep 6 Click Apply to commit your changes.Configuring an Access Point for Local Authentication on a WLAN (CLI)Before You BeginBefore you begin, you must have enabled local switching on the WLAN where you want to enable localauthentication for an access point. For instructions on how to enable local switching on the WLAN, see theConfiguring the Controller for FlexConnect (CLI) section.•config wlan flexconnect ap-auth wlan_id {enable |disable}—Configures the access point to enableor disable local authentication on a WLAN.Do not connect the access points in FlexConnect mode directly to Cisco 2500 Series Controllers.Caution•show wlan wlan-id —Displays the configuration for the WLAN. If local authentication is enabled, thefollowing information appears:......Web Based Authentication...................... DisabledWeb-Passthrough............................... DisabledConditional Web Redirect...................... DisabledSplash-Page Web Redirect...................... DisabledAuto Anchor................................... DisabledFlexConnect Local Switching........................ EnabledFlexConnect Local Authentication................... EnabledFlexConnect Learn IP Address....................... EnabledClient MFP.................................... OptionalTkip MIC Countermeasure Hold-down Timer....... 60Call Snooping.................................... DisabledRoamed Call Re-Anchor Policy..................... Disabled......Connecting Client Devices to WLANsFollow the instructions for your client device to create profiles to connect to the WLANs you created in theConfiguring the Controller for FlexConnect.Cisco Wireless LAN Controller Configuration Guide, Release 7.4       OL-28744-01 907Configuring FlexConnect
In the example scenarios (see Table 26: WLANs Example), there are three profiles on the client:1To connect to the “employee”WLAN, create a client profile that uses WPA/WPA2 with PEAP-MSCHAPV2authentication. After the client becomes authenticated, the client gets an IP address from the managementVLAN of the controller.2To connect to the “local-employee”WLAN, create a client profile that uses WPA/WPA2 authentication.After the client becomes authenticated, the client gets an IP address from VLAN 101 on the local switch.3To connect to the “guest-central”WLAN, create a client profile that uses open authentication. After theclient becomes authenticated, the client gets an IP address from VLAN 101 on the network local to theaccess point. After the client connects, the local user can type any HTTP address in the web browser. Theuser is automatically directed to the controller to complete the web-authentication process. When the weblogin page appears, the user enters the username and password.To determine if a client’s data traffic is being locally or centrally switched, choose Monitor > Clients on thecontroller GUI, click the Detail link for the desired client, and look at the Data Switching parameter underAP Properties.   Cisco Wireless LAN Controller Configuration Guide, Release 7.4908 OL-28744-01  Configuring FlexConnect
CHAPTER 138Configuring FlexConnect ACLs•Information About Access Control Lists, page 909•Restrictions for FlexConnect ACLs, page 909•Configuring FlexConnect ACLs (GUI), page 910•Configuring FlexConnect ACLs (CLI), page 912•Viewing and Debugging FlexConnect ACLs (CLI), page 913Information About Access Control ListsAn access control list (ACL) is a set of rules used to limit access to a particular interface (for example, if youwant to restrict a wireless client from pinging the management interface of the controller). ACLs enable accesscontrol of network traffic. After ACLs are configured on the controller, you can apply them to the managementinterface, the AP-Manager interface, any of the dynamic interfaces, or a WLAN. ACLs enable you to controldata traffic to and from wireless clients or to the controller CPU.You can configure ACLs on FlexConnectaccess points to enable effective usage and access control of locally switched data traffic on an access point.The FlexConnect ACLs can be applied to VLAN interfaces on access points in both the Ingress and Egressmode.Existing interfaces on an access point can be mapped to ACLs. The interfaces can be created by configuringa WLAN-VLAN mapping on a FlexConnect access point.The FlexConnect ACLs can be applied to an access point’s VLAN only if VLAN support is enabled on theFlexConnect access point.Restrictions for FlexConnect ACLs•FlexConnect ACLs can be applied only to FlexConnect access points. The configurations applied areper AP and per VLAN.•You can configure up to 512 ACLs on a controller.•Non-FlexConnect ACLs that are configured on the controller cannot be applied to a FlexConnect AP.Cisco Wireless LAN Controller Configuration Guide, Release 7.4        OL-28744-01 909
•FlexConnect ACLs do not support direction per rule. Unlike normal ACLs, Flexconnect ACLs cannotbe configured with a direction. An ACL as a whole needs to be applied to an interface as ingress oregress.•You can define up to 512 FlexConnect ACLs, each with up to 64 rules (or filters). Each rule hasparameters that affect its action. When a packet matches all the parameters pertaining to a rule, the actionset pertaining to that rule is applied to the packet.•ACLs in your network might have to be modified because Control and Provisioning of Wireless AccessPoints (CAPWAP) use ports that are different from the ones used by the Lightweight Access PointProtocol (LWAPP).•All ACLs have an implicit deny all rule as the last rule. If a packet does not match any of the rules, it isdropped by the corresponding access point.•ACLs mapping on the VLANs that are created on an AP using WLAN-VLAN mapping, should beperformed on a per-AP basis only. VLANs can be created on a FlexConnect group for AAA override.These VLANs will not have any mapping for a WLAN.•ACLs for VLANs that are created on a FlexConnect group should be mapped only on the FlexCconnectgroup. If the same VLAN is present on the corresponding AP as well as the FlexConnect group, APVLAN will take priority. This means that if no ACL is mapped on the AP, the VLAN will not have anyACL, even if the ACL is mapped to the VLAN on the FlexConnect group.Configuring FlexConnect ACLs (GUI)Step 1 Choose Security >Access Control Lists >FlexConnect Access Control Lists.The FlexConnect ACL page is displayed.This page lists all the FlexConnect ACLs configured on the controller. This page also shows the FlexConnect ACLscreated on the corresponding controller. To remove an ACL, hover your mouse over the blue drop-down arrow adjacentto the corresponding ACL name and choose Remove.Step 2 Add a new ACL by clicking New.The Access Control Lists >New page is displayed.Step 3 In the Access Control List Name text box, enter a name for the new ACL. You can enter up to 32 alphanumeric characters.Step 4 Click Apply.Step 5 When the Access Control Lists page reappears, click the name of the new ACL.When the Access Control Lists > Edit page appears, click Add New Rule.The Access Control Lists >Rules >New page is displayed.Step 6 Configure a rule for this ACL as follows:a) The controller supports up to 64 rules for each ACL. These rules are listed in order from 1 to 64. In the Sequencetext box, enter a value (between 1 and 64) to determine the order of this rule in relation to any other rules defined forthis ACL.If rules 1 through 4 are already defined and you add rule 29, it is added as rule 5. If you add or change asequence number of a rule, the sequence numbers of the other rules are automatically adjusted to maintaina continuous sequence. For instance, if you change a rule’s sequence number from 7 to 5, the rules withsequence numbers 5 and 6 are automatically reassigned as 6 and 7, respectively.Note   Cisco Wireless LAN Controller Configuration Guide, Release 7.4910 OL-28744-01  Configuring FlexConnect ACLs (GUI)
b) From the Source drop-down list, choose one of these options to specify the source of the packets to which this ACLis applicable:•Any—Any source (This is the default value.)•IP Address—A specific source. If you choose this option, enter the IP address and netmask of the source inthe corresponding text boxes.c) From the Destination drop-down list, choose one of these options to specify the destination of the packets to whichthis ACL applies:•Any—Any destination (This is the default value.)•IP Address—A specific destination. If you choose this option, enter the IP address and netmask of the destinationin the text boxes.d) From the Protocol drop-down list, choose the protocol ID of the IP packets to be used for this ACL. The protocoloptions that you can use are the following:•Any—Any protocol (This is the default value.)•TCP•UDP•ICMP—Internet Control Message Protocol•ESP—IP Encapsulating Security Payload•AH—Authentication Header•GRE—Generic Routing Encapsulation•IP in IP—Permits or denies IP-in-IP packets•Eth Over IP—Ethernet-over-Internet Protocol•OSPF—Open Shortest Path First•Other—Any other Internet-Assigned Numbers Authority (IANA) protocolIf you choose Other, enter the number of the desired protocol in the Protocol text box. You can findthe list of available protocols in the INAI website.NoteThe controller can permit or deny only the IP packets in an ACL. Other types of packets (such as Address ResolutionProtocol (ARP) packets) cannot be specified.If you chose TCP or UDP, two additional parameters, Source Port and Destination Port, are displayed. These parametersenable you to choose a specific source port and destination port or port range. The port options are used by applicationsthat send and receive data to and from the networking stack. Some ports are designated for certain applications, suchas Telnet, SSH, HTTP, and so on.e) From the DSCP drop-down list, choose one of these options to specify the differentiated services code point (DSCP)value of this ACL. DSCP is an IP header text box that can be used to define the quality of service across the Internet.•Any—Any DSCP (This is the default value.)•Specific—A specific DSCP from 0 to 63, which you enter in the DSCP text boxCisco Wireless LAN Controller Configuration Guide, Release 7.4       OL-28744-01 911Configuring FlexConnect ACLs (GUI)
f) From the Action drop-down list, choose Deny to cause this ACL to block packets, or Permit to cause this ACL toallow packets. The default value is Deny.g) Click Apply.The Access Control Lists > Edit page is displayed on which the rules for this ACL are shown.h) Repeat this procedure to add additional rules, if any, for this ACL.Step 7 Click Save Configuration.Configuring FlexConnect ACLs (CLI)•config flexconnect acl create name—Creates an ACL on a FlexConnect access point. The name mustbe an IPv4 ACL name of up to 32 characters.•config flexconnect acl delete name—Deletes a FlexConnect ACL.•config flexconnect acl rule action acl-name rule-index {permit |deny}—Permits or denies an ACL.•config flexconnect acl rule add acl-name rule-index—Adds an ACL rule.•config flexconnect acl rule change index acl-name old-index new-index—Changes the index value foran ACL rule.•config flexconnect acl rule delete name—Deletes an ACL rule.•config flexconnect acl rule dscp acl-name rule-index {0-63 | any }—Specifies the differentiated servicescode point (DSCP) value of the rule index. DSCP is an IP header that can be used to define the qualityof service across the Internet. Enter a value between 0 and 63 or the value any. The default value is any.•config flexconnect acl rule protocol acl-name rule-index {0-255 | any}—Assigns the rule index to anACL rule. Specify a value between 0 and 255 or ‘any’. The default is ‘any.’•config flexconnect acl rule destination address acl-name rule-index ipv4-addr subnet-mask—Configuresa rule's destination IP address, netmask and port range.•config flexconnect acl rule destination port range acl-name rule-index start-port end-port—Configuresa rule’s destination port range.•config flexconnect acl rule source address acl-name rule-index ipv4-addr subnet-mask—Configuresa rule's source IP address and netmask.•config flexconnect acl apply acl-name—Applies an ACL to the FlexConnect access point.•config flexconnectacl rule swap acl-name index-1 index-2—Swaps the index values of two rules.•config ap flexconnect vlan add acl vlan-id ingress-aclname egress-acl-name ap-name—Adds a VLANon a FlexConnect access point.•config flexconnect acl rule source port range acl-name rule-index start-port end-port—Configures arule’s source port range.   Cisco Wireless LAN Controller Configuration Guide, Release 7.4912 OL-28744-01  Configuring FlexConnect ACLs (CLI)
Viewing and Debugging FlexConnect ACLs (CLI)•show flexconnect acl summary—Displays a summary of the ACLs.•show flexconnect acl detailed acl-name—Displays the detailed information about the ACL.•debug flexconnect acl {enable | disable}—Enables or disables the debugging of FlexConnect ACL.•debug capwap reap—Enables debugging of CAPWAP.Cisco Wireless LAN Controller Configuration Guide, Release 7.4       OL-28744-01 913Viewing and Debugging FlexConnect ACLs (CLI)
   Cisco Wireless LAN Controller Configuration Guide, Release 7.4914 OL-28744-01  Viewing and Debugging FlexConnect ACLs (CLI)
CHAPTER 139Configuring FlexConnect Groups•Information About FlexConnect Groups, page 915•Configuring FlexConnect Groups, page 917•Configuring VLAN-ACL Mapping on FlexConnect Groups, page 922Information About FlexConnect GroupsTo organize and manage your FlexConnect access points, you can create FlexConnect Groups and assignspecific access points to them.All of the FlexConnect access points in a group share the same backup RADIUS server, CCKM, and localauthentication configuration information. This feature is helpful if you have multiple FlexConnect accesspoints in a remote office or on the floor of a building and you want to configure them all at once. For example,you can configure a backup RADIUS server for a FlexConnect rather than having to configure the same serveron each access point.The following figure shows a typical FlexConnect deployment with a backup RADIUS server in the branchoffice.Figure 68: FlexConnect Group DeploymentCisco Wireless LAN Controller Configuration Guide, Release 7.4        OL-28744-01 915
FlexConnect Groups and Backup RADIUS ServersYou can configure the controller to allow a FlexConnect access point in standalone mode to perform full802.1X authentication to a backup RADIUS server. You can configure a primary backup RADIUS server orboth a primary and secondary backup RADIUS server. These servers can be used when the FlexConnectaccess point is in of these two modes: standalone or connected.FlexConnect Groups and CCKMFlexConnect Groups are required for CCKM fast roaming to work with FlexConnect access points. CCKMfast roaming is achieved by caching a derivative of the master key from a full EAP authentication so that asimple and secure key exchange can occur when a wireless client roams to a different access point. This featureprevents the need to perform a full RADIUS EAP authentication as the client roams from one access point toanother. The FlexConnect access points need to obtain the CCKM cache information for all the clients thatmight associate so they can process it quickly instead of sending it back to the controller. If, for example, youhave a controller with 300 access points and 100 clients that might associate, sending the CCKM cache forall 100 clients is not practical. If you create a FlexConnect that includes a limited number of access points(for example, you create a group for four access points in a remote office), the clients roam only among thosefour access points, and the CCKM cache is distributed among those four access points only when the clientsassociate to one of them.CCKM fast roaming among FlexConnect and non-FlexConnect access points is not supported.NoteFlexConnect Groups and Opportunistic Key CachingStarting in the 7.0.116.0 release, FlexConnect groups enable Opportunistic Key Caching (OKC) to enablefast roaming of clients. OKC facilitates fast roaming by using PMK caching in access points that are in thesame FlexConnect group.This feature prevents the need to perform a full authentication as the client roams from one access point toanother. Whenever a client roams from one FlexConnect access point to another, the FlexConnect groupaccess point calculates the PMKID using the cached PMK.To see the PMK cache entries at the FlexConnect access point, use the show capwap reap pmk command.This feature is supported on Cisco FlexConnect access points.The FlexConnect access point must be in connected mode when the PMK is derived during WPA2/802.1xauthentication.NoteWhen using FlexConnect groups for OKC or CCKM, the PMK-cache is shared only across the access pointsthat are part of the same FlexConnect group and are associated to the same controller. If the access points arein the same FlexConnect group but are associated to different controllers that are part of the same mobilitygroup, the PMK cache is not updated and CCKM roaming will fail.   Cisco Wireless LAN Controller Configuration Guide, Release 7.4916 OL-28744-01  Information About FlexConnect Groups
FlexConnect Groups and Local AuthenticationYou can configure the controller to allow a FlexConnect access point in standalone mode to perform LEAP,EAP-FAST authentication for up to 100 statically configured users. The controller sends the static list ofusernames and passwords to each FlexConnect access point when it joins the controller. Each access point inthe group authenticates only its own associated clients.This feature is ideal for customers who are migrating from an autonomous access point network to a lightweightFlexConnect access point network and are not interested in maintaining a large user database or adding anotherhardware device to replace the RADIUS server functionality available in the autonomous access point.This feature can be used with the FlexConnect backup RADIUS server feature. If a FlexConnect isconfigured with both a backup RADIUS server and local authentication, the FlexConnect access pointalways attempts to authenticate clients using the primary backup RADIUS server first, followed by thesecondary backup RADIUS server (if the primary is not reachable), and finally the FlexConnect accesspoint itself (if the primary and secondary are not reachable).NoteThe number of FlexConnect groups and access point support depends on the platform that you are using. Youcan configure the following:•Up to 100 FlexConnect groups and 25 access points per group for a Cisco 5500 Series Controller.•Up to 1000 FlexConnect groups and 50 access points per group for a Cisco Flex 7500 Series Controllerin the 7.2 release.•Up to 2000 FlexConnect groups and 100 access points per group for Cisco Flex 7500 and Cisco 8500Series Controllers in the 7.3 release.•Up to 20 FlexConnect groups and up to 25 access points per group for the remaining platforms.Configuring FlexConnect GroupsConfiguring FlexConnect Groups (GUI)Step 1 Choose Wireless >FlexConnect Groups to open the FlexConnect Groups page.This page lists any FlexConnect groups that have already been created.If you want to delete an existing group, hover your cursor over the blue drop-down arrow for that group andchoose Remove.NoteCisco Wireless LAN Controller Configuration Guide, Release 7.4       OL-28744-01 917Configuring FlexConnect Groups
Step 2 Click New to create a new FlexConnect Group.Step 3 On the FlexConnect Groups >New page, enter the name of the new group in the Group Name text box. You canenter up to 32 alphanumeric characters.Step 4 Click Apply. The new group appears on the FlexConnect Groups page.Step 5 To edit the properties of a group, click the name of the desired group. The FlexConnect Groups >Edit page appears.Step 6 If you want to configure a primary RADIUS server for this group (for example, the access points are using 802.1Xauthentication), choose the desired server from the Primary RADIUS Server drop-down list. Otherwise, leave the textbox set to the default value of None.Step 7 If you want to configure a secondary RADIUS server for this group, choose the server from the Secondary RADIUSServer drop-down list. Otherwise, leave the field set to the default value of None.Step 8 Configure the RADIUS server for the FlexConnect group by doing the following:a) Enter the RADIUS server IP address.b) Choose the server type as either Primary or Secondary.c) Enter a shared secret to log on to the RADIUS server and confirm it.d) Enter the port number.e) Click Add.Step 9 To add an access point to the group, click Add AP. Additional fields appear on the page under Add AP.Step 10 Perform one of the following tasks:•To choose an access point that is connected to this controller, select the Select APs from Current Controllercheck box and choose the name of the access point from the AP Name drop-down list.If you choose an access point on this controller, the MAC address of the access point is automaticallyentered in the Ethernet MAC text box to prevent any mismatches from occurring.Note•To choose an access point that is connected to a different controller, leave the Select APs from Current Controllercheck box unselected and enter its MAC address in the Ethernet MAC text box.If the FlexConnect access points within a group are connected to different controllers, all of the controllersmust belong to the same mobility group.NoteStep 11 Click Add to add the access point to this FlexConnect group. The access point’s MAC address, name, and status appearat the bottom of the page.If you want to delete an access point, hover your cursor over the blue drop-down arrow for that access pointand choose Remove.NoteStep 12 Click Apply.Step 13 Enable local authentication for a FlexConnect Group as follows:a) Ensure that the Primary RADIUS Server and Secondary RADIUS Server parameters are set to None.b) Select the Enable AP Local Authentication check box to enable local authentication for this FlexConnect Group.The default value is unselected.c) Click Apply.d) Choose the Local Authentication tab to open the FlexConnect >Edit (Local Authentication > Local Users)page.e) To add clients that you want to be able to authenticate using LEAP, EAP-FAST, perform one of the following:f) Upload a comma-separated values (CSV) file by selecting the Upload CSV File check box, clicking the Browsebutton to browse to an CSV file that contains usernames and passwords (each line of the file needs to be in the   Cisco Wireless LAN Controller Configuration Guide, Release 7.4918 OL-28744-01  Configuring FlexConnect Groups
following format: username, password), and clicking Add to upload the CSV file. The clients’names appear on theleft side of the page under the “User Name”heading.g) Add clients individually by entering the client’s username in the User Name text box and a password for the clientin the Password and Confirm Password text boxes, and clicking Add to add this client to the list of supported localusers. The client name appears on the left side of the page under the “User Name”heading.You can add up to 100clients.Noteh) Click Apply.i) Choose the Protocols tab to open the FlexConnect >Edit (Local Authentication > Protocols) page.j) To allow a FlexConnect access point to authenticate clients using LEAP, select the Enable LEAP Authenticationcheck box.k) To allow a FlexConnect access point to authenticate clients using EAP-FAST, select the Enable EAP-FASTAuthentication check box. The default value is unselected.l) Perform one of the following, depending on how you want protected access credentials (PACs) to be provisioned:•To use manual PAC provisioning, enter the server key used to encrypt and decrypt PACs in the Server Key andConfirm Server Key text boxes. The key must be 32 hexadecimal characters.•To allow PACs to be sent automatically to clients that do not have one during PAC provisioning, select theEnable Auto Key Generation check boxm) In the Authority ID text box, enter the authority identifier of the EAP-FAST server. The identifier must be 32hexadecimal characters.n) In the Authority Info text box, enter the authority identifier of the EAP-FAST server in text format. You can enterup to 32 hexadecimal characters.o) To specify a PAC timeout value, select the PAC Timeout check box and enter the number of seconds for the PACto remain viable in the text box. The default value is unselected, and the valid range is 2 to 4095 seconds whenenabled.p) Click Apply.Step 14 In the WLAN-ACL mapping tab, you can do the following:a) Under Web Auth ACL Mapping, enter the WLAN ID, choose the WebAuth ACL, and click Add to map the webauthentication ACL and the WLAN.b) Under Local Split ACL Mapping, enter the WLAN ID, and choose the Local Split ACL, and click Add to map theLocal Split ACL to the WLAN.You can configure up to 16 WLAN-ACL combinations for local split tunneling. Local split tunneling doesnot work for clients with static IP address.NoteStep 15 In the Central DHCP tab, you can do the following:a) In the WLAN Id box, enter the WLAN ID with which you want to map Central DHCP.b) Select or unselect the Central DHCP check box to enable or disable Central DHCP for the mapping.c) Select or unselect the Override DNS check box to enable or disable overriding of DNS for the mapping.d) Select or unselect the NAT-PAT check box to enable or disable network address translation and port address translationfor the mapping.e) Click Add to add the Central DHCP - WLAN mapping.Step 16 Click Save Configuration.Step 17 Repeat this procedure if you want to add more FlexConnects.To see if an individual access point belongs to a FlexConnect Group, you can choose Wireless >Access Points>All APs > the name of the desired access point in the FlexConnect tab. If the access point belongs to aFlexConnect, the name of the group appears in the FlexConnect Name text box.NoteCisco Wireless LAN Controller Configuration Guide, Release 7.4       OL-28744-01 919Configuring FlexConnect Groups
Configuring FlexConnect Groups (CLI)Step 1 Add add or delete a FlexConnect Group by entering this command:config flexconnect group group_name {add |delete}Step 2 Configure a primary or secondary RADIUS server for the FlexConnect group by entering this command:config flexconect group group-name radius server auth {{add {primary |secondary}ip-addr auth-port secret} |{delete {primary |secondary}}}Step 3 Add an access point to the FlexConnect Group by entering this command:config flexconnect group_name ap {add |delete}ap_macStep 4 Configure local authentication for a FlexConnect as follows:a) Make sure that a primary and secondary RADIUS server are not configured for the FlexConnect Group.b) To enable or disable local authentication for this FlexConnect group, enter this command:config flexconnect group group_name radius ap {enable |disable}c) Enter the username and password of a client that you want to be able to authenticate using LEAP, EAP-FAST byentering this command:config flexconnect group group_name radius ap user add username password passwordYou can add up to 100clients.Noted) Allow a FlexConnect access point group to authenticate clients using LEAP or to disable this behavior by enteringthis command:config flexconnect group group_name radius ap leap {enable |disable}e) Allow a FlexConnect access point group to authenticate clients using EAP-FAST or to disable this behavior byentering this command:config flexconnect group group_name radius ap eap-fast {enable |disable}f) To download EAP Root and Device certificate to AP, enter this command:config flexconnect group group_name radius ap eap-cert downloadg) Allow a FlexConnect access point group to authenticate clients using EAP-TLS or to disable this behavior by enteringthis command:config flexconnect group group_name radius ap eap-tls {enable |disable}h) Allow a FlexConnect access point group to authenticate clients using PEAP or to disable this behavior by enteringthis command:config flexconnect group group_name radius ap peap {enable |disable}i) Enter one of the following commands, depending on how you want PACs to be provisioned:•config flexconnect group group_name radius ap server-key key—Specifies the server key used to encryptand decrypt PACs. The key must be 32 hexadecimal characters.•config flexconnect group group_name radius ap server-key auto—Allows PACs to be sent automatically toclients that do not have one during PAC provisioning.   Cisco Wireless LAN Controller Configuration Guide, Release 7.4920 OL-28744-01  Configuring FlexConnect Groups
j) To specify the authority identifier of the EAP-FAST server, enter this command:config flexconnect group group_name radius ap authority id idwhere id is 32 hexadecimal characters.k) To specify the authority identifier of the EAP-FAST server in text format, enter this command:config flexconnect group group_name radius ap authority info infowhere info is up to 32 hexadecimal characters.l) To specify the number of seconds for the PAC to remain viable, enter this command:config flexconnect group group_name radius ap pac-timeout timeoutwhere timeout is a value between 2 and 4095 seconds (inclusive) or 0. A value of 0, which is the default value,disables the PAC timeout.Step 5 Configure a Policy ACL on a FlexConnect group by entering this command:config flexconnect group group-name acl {add |delete}acl-nameStep 6 Configure local split tunneling on a per-FlexConnect group basis by entering this command:config flexconnect group group_name local-split wlan wlan-id acl acl-name flexconnect-group-name {enable |disable}Step 7 To set multicast/broadcast across L2 broadcast domain on overridden interface for locally switched clients, enter thiscommand:config flexconnect group group_name multicast overridden-interface {enable |disable}Step 8 Configure central DHCP per WLAN by entering this command:config flexconnect group group-name central-dhcp wlan-id {enable override dns |disable |delete}Step 9 Configure policy acl on FlexConnect group by entering this command:config flexconnect group group_name policy acl {add |delete}acl-nameStep 10 Configure web-auth acl on flexconnect group by entering this command:config flexconnect group group_name web-auth wlan wlan-id acl acl-name {enable |disable}Step 11 Configure wlan-vlan mapping on flexconnect group by entering this command:config flexconnect group group_name wlan-vlan wlan wlan-id{add |delete}vlan vlan-idStep 12 To set efficient upgrade for group, enter this command:config flexconnect group group_name predownload {enable |disable |master |slave}ap-name retry-count maximumretry count ap-name ap-nameStep 13 Save your changes by entering this command:save configStep 14 See the current list of flexconnect groups by entering this command:show flexconnect group summaryStep 15 See the details for a specific FlexConnect Groups by entering this command:show flexconnect group detail group_nameCisco Wireless LAN Controller Configuration Guide, Release 7.4       OL-28744-01 921Configuring FlexConnect Groups
Configuring VLAN-ACL Mapping on FlexConnect GroupsConfiguring VLAN-ACL Mapping on FlexConnect Groups (GUI)Step 1 Choose Wireless >FlexConnect Groups.The FlexConnect Groups page appears. This page lists the access points associated with the controller.Step 2 Click the Group Name link of the FlexConnect Group for which you want to configure VLAN-ACL mapping.Step 3 Click the VLAN-ACL Mapping tab.The VLAN-ACL Mapping page for that FlexConnect group appears.Step 4 Enter the Native VLAN ID in the VLAN ID text box.Step 5 From the Ingress ACL drop-down list, choose the Ingress ACL.Step 6 From the Egress ACL drop-down list, choose the Egress ACL.Step 7 Click Add to add this mapping to the FlexConnect Group.The VLAN ID is mapped with the required ACLs. To remove the mapping, hover your mouse over the blue drop-downarrow and choose Remove.Configuring VLAN-ACL Mapping on FlexConnect Groups (CLI)•Add a VLAN to a FlexConnect group and map the ingress and egress ACLs by entering this command:config flexconnect group group-name vlan add vlan-id acl ingress-acl egress aclViewing VLAN-ACL Mappings (CLI)•See the FlexConnect group details by entering this command:show flexconnect group detail group-name•See the VLAN-ACL mappings on the access point by entering this command:show ap config general ap-name   Cisco Wireless LAN Controller Configuration Guide, Release 7.4922 OL-28744-01  Configuring VLAN-ACL Mapping on FlexConnect Groups
CHAPTER 140Configuring AAA Overrides for FlexConnect•Information About Authentication, Authorization, Accounting Overrides, page 923•Restrictions for AAA Overrides for FlexConnect, page 924•Configuring AAA Overrides for FlexConnect on an Access Point (GUI), page 924•Configuring VLAN Overrides for FlexConnect on an Access Point (CLI), page 925Information About Authentication, Authorization, Accounting OverridesThe Allow Authentication, Authorization, Accouting (AAA) Override option of a WLAN enables you toconfigure the WLAN for authentication. It enables you to apply VLAN tagging, QoS, and ACLs to individualclients based on the returned RADIUS attributes from the AAA server.AAA overrides for FlexConnect access points introduce a dynamic VLAN assignment for locally switchedclients. AAA overrides for FlexConnect also support fast roaming (Opportunistic Key Caching [OKC]/ CiscoCentralized Key management [CCKM]) of overridden clients.VLAN overrides for FlexConnect are applicable for both centrally and locally authenticated clients. VLANscan be configured on FlexConnect groups.If a VLAN on the AP is configured using the WLAN-VLAN, the AP configuration of the corresponding ACLis applied. If the VLAN is configured using the FlexConnect group, the corresponding ACL configured onthe FlexConnect group is applied. If the same VLAN is configured on the FlexConnect group and also on theAP, the AP configuration, with its ACL takes precedence. If there is no slot for a new VLAN from theWLAN-VLAN mapping, the latest configured FlexConnect group VLAN is replaced.If the VLAN that was returned from the AAA is not present on the AP, the client falls back to the defaultVLAN configured for the WLAN.Before configuring a AAA override, the VLAN must be created on the access points. These VLANs can becreated by using the existing WLAN-VLAN mappings on the access points, or by using the FlexConnectgroup VLAN-ACL mappings.AAA Override for IPv6 ACLsIn order to support centralized access control through a centralized AAA server such as the Cisco IdentityServices Engine (ISE) or ACS, the IPv6 ACL can be provisioned on a per-client basis using AAA Overrideattributes. In order to use this feature, the IPv6 ACL must be configured on the controller and the WLANmust be configured with the AAA Override feature enabled. The AAA attribute for an IPv6 ACL isCisco Wireless LAN Controller Configuration Guide, Release 7.4        OL-28744-01 923
Airespace-IPv6-ACL-Name similar to the Airespace-ACL-Name attribute used for provisioning an IPv4-basedACL. The AAA attribute-returned contents should be a string that is equal to the name of the IPv6 ACL asconfigured on the controller.Restrictions for AAA Overrides for FlexConnect•Before configuring a AAA override, VLANs must be created on the access points. These VLANs canbe created by using the existing WLAN-VLAN mappings on the access points, or by using theFlexConnect group VLAN-ACL mappings.•At any given point, an AP has a maximum of 16 VLANs. First, the VLANs are selected as per the APconfiguration (WLAN-VLAN), and then the remaining VLANs are pushed from the FlexConnect groupin the order that they are configured or displayed in the FlexConnect group. If the VLAN slots are full,an error message is displayed.•AAA for locally switched clients supports only VLAN overrides.•Dynamic VLAN assignment is not supported for web authentication from a controller with AccessControl Server (ACS).Configuring AAA Overrides for FlexConnect on an Access Point (GUI)Step 1 Choose Wireless >All >APs.The All APs page is displayed. This page lists the access points associated with the controller.Step 2 Click the corresponding AP name.Step 3 Click the FlexConnect tab.Step 4 Enter a value for Native VLAN ID.Step 5 Click the VLAN Mappings button to configure the AP VLANs mappings.The following parameters are displayed:•AP Name—The access point name.•Base Radio MAC—The base radio of the AP.•WLAN-SSID-VLAN ID Mapping—For each WLAN configured on the controller, the corresponding SSID andVLAN IDs are listed. Change a WLAN-VLAN ID mapping by editing the VLAN ID column for a WLAN.•Centrally Switched WLANs—If centrally switched WLANs are configured, WLAN–VLAN mapping is listed.•AP Level VLAN ACL Mapping—The following parameters are available:◦VLAN ID—The VLAN ID.◦Ingress ACL—The Ingress ACL corresponding to the VLAN.◦Egress ACL—The Egress ACL corresponding to the VLAN.Change the ingress ACL and egress ACL mappings by selecting the mappings from the drop-down list for eachACL type.   Cisco Wireless LAN Controller Configuration Guide, Release 7.4924 OL-28744-01  Restrictions for AAA Overrides for FlexConnect
•Group Level VLAN ACL Mapping—The following group level VLAN ACL mapping parameters are available:◦VLAN ID—The VLAN ID.◦Ingress ACL—The ingress ACL for this VLAN.◦Egress ACL—The egress ACL for this VLAN.Step 6 Click Apply.Configuring VLAN Overrides for FlexConnect on an Access Point (CLI)To configure VLAN overrides on a FlexConnect access point, use the following command:config ap flexconnect vlan add vlan-id acl ingress-acl egress-acl ap_nameCisco Wireless LAN Controller Configuration Guide, Release 7.4       OL-28744-01 925Configuring VLAN Overrides for FlexConnect on an Access Point (CLI)
   Cisco Wireless LAN Controller Configuration Guide, Release 7.4926 OL-28744-01  Configuring VLAN Overrides for FlexConnect on an Access Point (CLI)
CHAPTER 141Configuring FlexConnect AP Upgrades forFlexConnect APs•Information About FlexConnect AP Upgrades, page 927•Restrictions for FlexConnect AP Upgrades for FlexConnect Access Points, page 927•Configuring FlexConnect AP Upgrades (GUI), page 928•Configuring FlexConnect AP Upgrades (CLI), page 928Information About FlexConnect AP UpgradesNormally, when upgrading the image of an AP, you can use the pre-image download feature to reduce theamount of time the AP is unavailable to serve clients. However, it also increases the downtime because theaccess point cannot serve clients during an upgrade. The Pre-image download feature can be used to reducethis downtime. However, in the case of a branch office set up, the upgrade images are still downloaded toeach access point over the WAN link, which has a higher latency.A more efficient way is to use the FlexConnect AP Upgrade feature. When this feature is enabled, one accesspoint of each model in the local network first downloads the upgrade image over the WAN link. It workssimilarly to the master-slave or client-server model. This access point then becomes the master for the remainingaccess point of the similar model. The remaining access points then download the upgrade image from themaster access point using the pre-image download feature over the local network, which reduces the WANlatency.Restrictions for FlexConnect AP Upgrades for FlexConnect Access Points•The primary and secondary controllers in the network must have the same set of primary and backupimages.•If you configured a FlexConnect group, all access points in that group must be within the same subnetor must be accessible through NAT.Cisco Wireless LAN Controller Configuration Guide, Release 7.4        OL-28744-01 927
Configuring FlexConnect AP Upgrades (GUI)Step 1 Choose Wireless >FlexConnect Groups.The FlexConnect Groups page appears. This page lists the FlexConnect Groups configured on the controller.Step 2 Click the Group Name link on which you want to configure the image upgrade.Step 3 Click the Image Upgrade tab.Step 4 Select the FlexConnect AP Upgrade check box to enable a FlexConnect AP Upgrade.Step 5 If you enabled the FlexConnect AP upgrade in the previous step, you must enable the following parameters:•Slave Maximum Retry Count—The number of attempts the slave access point must try to connect to the masteraccess point for downloading the upgrade image. If the image download does not occur for the configured retryattempts, the image is upgraded over the WAN.•Upgrade Image—Select the upgrade image. The options are Primary,Backup, and Abort.•Click FlexConnect Upgrade to upgrade.Step 6 From the AP Name drop-down list, click Add Master to add the master access point.You can manually assign master access points in the FlexConnect group by selecting the access points.Step 7 Click Apply.Configuring FlexConnect AP Upgrades (CLI)•config flexconnect group group-name predownload {enable | disable}—Enables or disables theFlexConnect AP upgrade.•config flexconnect group group-name predownload master ap-name—Manually assigns an accesspoint as the master access point.•config flexconnect group group-name predownload slave retry-count ap-name—Sets the access pointas a slave access point with a retry count.•config flexconnect group group-name predownload start—Initiates the image download on the accesspoints in the FlexConnect group.•config ap image predownload {abort | primary | backup}—Assigns the image type that must bedownloaded for the preimage upgrade.•show flexconnect group group-name—Displays the summary of the FlexConnect group configuration.•show ap image all—Displays the details of the images on the access point.   Cisco Wireless LAN Controller Configuration Guide, Release 7.4928 OL-28744-01  Configuring FlexConnect AP Upgrades (GUI)
PART XConfiguring Mobility Groups•Configuring Mobility Groups, page 931•Viewing Mobility Group Statistics, page 943•Configuring Auto-Anchor Mobility, page 945•Validating WLAN Mobility Security Values, page 951•Using Symmetric Mobility Tunneling, page 953•Running Mobility Ping Tests, page 955•Configuring Dynamic Anchoring for Clients with Static IP Addresses, page 957•Configuring Foreign Mappings, page 961•Configuring Proxy Mobile IPv6, page 963
CHAPTER 142Configuring Mobility Groups•Information About Mobility, page 931•Information About Mobility Groups, page 935•Prerequisites for Configuring Mobility Groups, page 938•Configuring Mobility Groups (GUI), page 940•Configuring Mobility Groups (CLI), page 941Information About MobilityMobility, or roaming, is a wireless LAN client’s ability to maintain its association seamlessly from one accesspoint to another securely and with as little latency as possible. This section explains how mobility works whencontrollers are included in a wireless network.When a wireless client associates and authenticates to an access point, the access point’s controller places anentry for that client in its client database. This entry includes the client’s MAC and IP addresses, securitycontext and associations, quality of service (QoS) contexts, the WLAN, and the associated access point. Thecontroller uses this information to forward frames and manage traffic to and from the wireless client.Cisco Wireless LAN Controller Configuration Guide, Release 7.4        OL-28744-01 931
This figure shows a wireless client that roams from one access point to another when both access points arejoined to the same controller.Figure 69: Intracontroller RoamingWhen the wireless client moves its association from one access point to another, the controller simply updatesthe client database with the newly associated access point. If necessary, new security context and associationsare established as well.The process becomes more complicated, however, when a client roams from an access point joined to onecontroller to an access point joined to a different controller. It also varies based on whether the controllers areoperating on the same subnet.   Cisco Wireless LAN Controller Configuration Guide, Release 7.4932 OL-28744-01  Information About Mobility
This figure shows intercontroller roaming, which occurs when the wireless LAN interfaces of the controllersare on the same IP subnet.Figure 70: Intercontroller RoamingWhen the client associates to an access point joined to a new controller, the new controller exchanges mobilitymessages with the original controller, and the client database entry is moved to the new controller. Newsecurity context and associations are established if necessary, and the client database entry is updated for thenew access point. This process remains transparent to the user.All clients configured with 802.1X/Wi-Fi Protected Access (WPA) security complete a full authenticationin order to comply with the IEEE standard.NoteCisco Wireless LAN Controller Configuration Guide, Release 7.4       OL-28744-01 933Information About Mobility
This figure shows intersubnet roaming, which occurs when the wireless LAN interfaces of the controllers areon different IP subnets.Figure 71: Intersubnet RoamingInter-subnet roaming is similar to inter-controller roaming in that the controllers exchange mobility messageson the client roam. However, instead of moving the client database entry to the new controller, the originalcontroller marks the client with an “Anchor”entry in its own client database. The database entry is copied tothe new controller client database and marked with a “Foreign”entry in the new controller. The roam remainstransparent to the wireless client, and the client maintains its original IP address.In inter-subnet roaming, WLANs on both anchor and foreign controllers need to have the same network accessprivileges and no source-based routing or source-based firewalls in place. Otherwise, the clients may havenetwork connectivity issues after the handoff.In a static anchor setup using controllers and ACS, if AAA override is enabled to dynamically assign VLANand QoS, the foreign controller updates the anchor controller with the right VLAN after a Layer 2 authentiation(802.1x). For Layer 3 RADIUS authentication, the RADIUS requests for authentication are sent by the anchorcontroller.Mobility is not supported for SSIDs with security type configured for Webauth on MAC filter failure.If a client roams in web authentication state, the client is considered as a new client on another controllerinstead of considering it as a mobile client.Note   Cisco Wireless LAN Controller Configuration Guide, Release 7.4934 OL-28744-01  Information About Mobility
Information About Mobility GroupsA mobility group is a set of controllers, identified by the same mobility group name, that defines the realmof seamless roaming for wireless clients. By creating a mobility group, you can enable multiple controllersin a network to dynamically share information and forward data traffic when inter-controller or inter-subnetroaming occurs. Controllers in the same mobility group can share the context and state of client devices aswell as their list of access points so that they do not consider each other’s access points as rogue devices. Withthis information, the network can support inter-controller wireless LAN roaming and controller redundancy.Controllers do not have to be of the same model to be a member of a mobility group. Mobility groups canbe comprised of any combination of controller platforms.NoteFigure 72: Example of a Single Mobility GroupAs shown above, each controller is configured with a list of the other members of the mobility group. Whenevera new client joins a controller, the controller sends out a unicast message (or multicast message if mobilitymulticast is configured) to all of the controllers in the mobility group. The controller to which the client waspreviously connected passes on the status of the client.For example, if a controller supports 6000 access points, a mobility group that consists of 24 such controllerssupports up to 144,000 access points (24 * 6000 = 144,000 access points).Cisco Wireless LAN Controller Configuration Guide, Release 7.4       OL-28744-01 935Information About Mobility Groups
Mobility groups enable you to limit roaming between different floors, buildings, or campuses in the sameenterprise by assigning different mobility group names to different controllers within the same wirelessnetwork.This figure shows the results of creating distinct mobility group names for two groups of controllers.Figure 73: Two Mobility GroupsThe controllers in the ABC mobility group share access point and client information with each other. Thecontrollers in the ABC mobility group do not share the access point or client information with the XYZcontrollers, which are in a different mobility group. Likewise, the controllers in the XYZ mobility group donot share access point or client information with the controllers in the ABC mobility group. This featureensures mobility group isolation across the network.Every controller maintains information about its peer controllers in a mobility list. Controllers can communicateacross mobility groups and clients may roam between access points in different mobility groups if the controllersare included in each other’s mobility lists. In the following example, controller 1 can communicate with eithercontroller 2 or 3, but controller 2 and controller 3 can communicate only with controller 1 and not with eachother. Similarly, clients can roam between controller 1 and controller 2 or between controller 1 and controller3 but not between controller 2 and controller 3.   Cisco Wireless LAN Controller Configuration Guide, Release 7.4936 OL-28744-01  Information About Mobility Groups
Table 27: ExampleController 3Mobility group: CMobility list:Controller 1 (group A)Controller 3 (group C)Controller 2Mobility group: AMobility list:Controller 1 (group A)Controller 2 (group A)Controller 1Mobility group: AMobility list:Controller 1 (group A)Controller 2 (group A)Controller 3 (group C) ?The controller supports seamless roaming across multiple mobility groups. During seamless roaming, theclient maintains its IP address across all mobility groups; however, Cisco Centralized Key Management(CCKM) and proactive key caching (PKC) are supported only for inter-mobility-group roaming. When aclient crosses a mobility group boundary during a roam, the client is fully authenticated, but the IP address ismaintained, and mobility tunneling is initiated for Layer 3 roaming.Messaging Among Mobility GroupsThe controller provides intersubnet mobility for clients by sending mobility messages to other membercontrollers.•The controller sends a Mobile Announce message to members in the mobility list each time that a newclient associates to it. The controller sends the message only to those members that are in the same groupas the controller (the local group) and then includes all of the other members while sending retries.•You can configure the controller to use multicast to send the Mobile Announce messages. This behaviorallows the controller to send only one copy of the message to the network, which destines it to themulticast group that contains all the mobility members. To derive the maximum benefit from multicastmessaging, we recommend that it be enabled on all group members.Using Mobility Groups with NAT DevicesMobility message payloads carry IP address information about the source controller. This IP address is validatedwith the source IP address of the IP header. This behavior is a problem when a NAT device is introduced inthe network because it changes the source IP address in the IP header. In the guest WLAN feature, any mobilitypacket, that is being routed through a NAT device is dropped because of the IP address mismatch.The mobility group lookup uses the MAC address of the source controller. Because the source IP address ischanged due to the mapping in the NAT device, the mobility group database is searched before a reply is sentto get the IP address of the requesting controller. This process is done using the MAC address of the requestingcontroller.When configuring the mobility group in a network where NAT is enabled, enter the IP address that is sent tothe controller from the NAT device rather than the controller’s management interface IP address. Also, makesure that the following ports are open on the firewall if you are using a firewall such as PIX:•UDP 16666 for tunnel control traffic•IP protocol 97 for user data traffic•UDP 161 and 162 for SNMPCisco Wireless LAN Controller Configuration Guide, Release 7.4       OL-28744-01 937Information About Mobility Groups
Client mobility among controllers works only if auto-anchor mobility (also called guest tunneling) orsymmetric mobility tunneling is enabled. Asymmetric tunneling is not supported when mobility controllersare behind the NAT device. See the Configuring Auto-Anchor Mobility and Using Symmetric MobilityTunneling sections for details on these mobility options.NotePrerequisites for Configuring Mobility GroupsBefore you add controllers to a mobility group, you must verify that the following requirements have beenmet for all controllers that are to be included in the group:•IP connectivity must exist between the management interfaces of all controllers.You can verify IP connectivity by pinging the controllers.NoteMobility control packets can use any interface address as the source, based on routingtable. It is recommended that all controllers in the mobility group should have themanagement interface in the same subnet. A topology where one controller's managementinterface and other controller's dynamic interface are on same subnet not recommendedfor seamless mobility.Note•When controllers in the mobility list use different software versions, Layer 2 or Layer 3 clients havelimited roaming support. Layer 2 or Layer 3 client roaming is supported only between controllers thatuse the same version or with controllers that run versions 7.X.X.If you inadvertently configure a controller with a failover controller that runs a differentsoftware release, the access point might take a long time to join the failover controllerbecause the access point starts the discovery process in CAPWAP and then changes toLWAPP discovery.Note•All controllers must be configured with the same virtual interface IP address.If necessary, you can change the virtual interface IP address by editing the virtualinterface name on the Controller > Interfaces page.NoteIf all the controllers within a mobility group are not using the same virtual interface,inter-controller roaming may appear to work, but the handoff does not complete, andthe client loses connectivity for a period of time.Note   Cisco Wireless LAN Controller Configuration Guide, Release 7.4938 OL-28744-01  Prerequisites for Configuring Mobility Groups
•You must have gathered the MAC address and IP address of every controller that is to be included inthe mobility group. This information is necessary because you will be configuring all controllers withthe MAC address and IP address of all the other mobility group members.You can find the MAC and IP addresses of the other controllers to be included in themobility group on the Controller > Mobility Groups page of each controller’s GUI.Note•When you configure mobility groups using a third-party firewall, for example, Cisco PIX, or Cisco ASA,you must open port 16666, and IP protocol 97.•For intercontroller CAPWAP data and control traffic, you must open the ports 5247 and 5264.This table lists the protocols and port numbers that must be used for management and operational purposes:Table 28: Protocol/Service and Port NumberPort NumberProtocol/ServiceTCP Port 22 or 29SSH/TelnetUDP Port 69TFTPUDP Port 123NTPUDP Port 161 for gets and sets and UDP port 162 for traps.SNMPTCP port 443 for HTTPS and port 80 for HTTPHTTPS/HTTPTCP port 514SyslogUDP port 1812 and 1813Radius Auth/AccountTo view information on mobility support across controllers with different software versions, see the CiscoWireless Solutions Software Compatibility Matrix.NoteYou cannot perform port address translation (PAT) on the firewall. You must configure one-to-one networkaddress translation (NAT).NoteCisco Wireless LAN Controller Configuration Guide, Release 7.4       OL-28744-01 939Prerequisites for Configuring Mobility Groups
Configuring Mobility Groups (GUI)Step 1 Choose Controller > Mobility Management > Mobility Groups to open the Static Mobility Group Members page.This page shows the mobility group name in the Default Mobility Group text box and lists the MAC address and IPaddress of each controller that is currently a member of the mobility group. The first entry is the local controller, whichcannot be deleted.If you want to delete any of the remote controllers from the mobility group, hover your cursor over the bluedrop-down arrow for the desired controller and choose Remove.NoteStep 2 Perform one of the following to add controllers to a mobility group:•If you are adding only one controller or want to individually add multiple controllers, click New and go.OR•If you are adding multiple controllers and want to add them in bulk, click EditAll and go to.The EditAll option enables you to enter the MAC and IP addresses of all the current mobility group membersand then copy and paste all the entries from one controller to the other controllers in the mobility group.NoteStep 3 Click New to open the Mobility Group Member > New page.Step 4 Add a controller to the mobility group as follows:1In the Member IP Address text box, enter the management interface IP address of the controller to be added.If you are configuring the mobility group in a network where network address translation (NAT) is enabled,enter the IP address that is sent to the controller from the NAT device rather than the controller’s managementinterface IP address. Otherwise, mobility will fail among controllers in the mobility group.Note2In the Member MAC Address text box, enter the MAC address of the controller to be added.3In the Group Name text box, enter the name of the mobility group.The mobility group name is casesensitive.Note4In the Hash text box, enter the hash key of the peer mobility controller, which should be a virtual controller in thesame domain.You must configure the hash only if the peer mobility controller is a virtual controller in the same domain.5Click Apply to commit your changes. The new controller is added to the list of mobility group members on the StaticMobility Group Members page.6Click Save Configuration to save your changes.7Repeat Step a through Step e to add all of the controllers in the mobility group.8Repeat this procedure on every controller to be included in the mobility group. All controllers in the mobility groupmust be configured with the MAC address and IP address of all other mobility group members.The Mobility Group Members > Edit All page lists the MAC address, IP address, and mobility group name (optional)of all the controllers currently in the mobility group. The controllers are listed one per line with the local controller atthe top of the list.If desired, you can edit or delete any of the controllers in thelist.Note   Cisco Wireless LAN Controller Configuration Guide, Release 7.4940 OL-28744-01  Configuring Mobility Groups (GUI)
Step 5 Add more controllers to the mobility group as follows:1Click inside the edit box to start a new line.2Enter the MAC address, the management interface IP address, and the name of the mobility group for the controllerto be added.You should enter these values on one line and separate each value with one or twospaces.NoteThe mobility group name is casesensitive.Note3Repeat Step a and Step b for each additional controller that you want to add to the mobility group.4Highlight and copy the complete list of entries in the edit box.5Click Apply to commit your changes. The new controllers are added to the list of mobility group members on theStatic Mobility Group Members page.6Click Save Configuration to save your changes.7Paste the list into the text box on the Mobility Group Members > Edit All page of all the other controllers in themobility group and click Apply and Save Configuration.Step 6 Choose Multicast Messaging to open the Mobility Multicast Messaging page.The names of all the currently configured mobility groups appear in the middle of the page.Step 7 On the Mobility Multicast Messaging page, select the Enable Multicast Messaging check box to enable the controllerto use multicast mode to send Mobile Announce messages to the mobility members. If you leave it unselected, thecontroller uses unicast mode to send the Mobile Announce messages. The default value is unselected.Step 8 If you enabled multicast messaging in the previous step, enter the multicast group IP address for the local mobility groupin the Local Group Multicast IP Address text box. This address is used for multicast mobility messaging.In order to use multicast messaging, you must configure the IP address for the local mobilitygroup.NoteStep 9 Click Apply to commit your changes.Step 10 If desired, you can also configure the multicast group IP address for nonlocal groups within the mobility list. To do so,click the name of a nonlocal mobility group to open the Mobility Multicast Messaging > Edit page, and enter the multicastgroup IP address for the nonlocal mobility group in the Multicast IP Address text box.If you do not configure the multicast IP address for nonlocal groups, the controller uses unicast mode to sendmobility messages to those members.NoteStep 11 Click Apply to commit your changes.Step 12 Click Save Configuration to save your changes.Configuring Mobility Groups (CLI)Step 1 Check the current mobility settings by entering this command:show mobility summaryCisco Wireless LAN Controller Configuration Guide, Release 7.4       OL-28744-01 941Configuring Mobility Groups (CLI)
Step 2 Create a mobility group by entering this command:config mobility group domain domain_nameEnter up to 31 case-sensitive ASCII characters for the group name. Spaces are not allowed in mobility groupnames.NoteStep 3 Add a group member by entering this command:config mobility group member add mac_address ip_addressIf you are configuring the mobility group in a network where network address translation (NAT) is enabled,enter the IP address that is sent to the controller from the NAT device rather than the controller’s managementinterface IP address. Otherwise, mobility will fail among controllers in the mobility group.NoteEnter the config mobility group member delete mac_address command if you want to delete a group member.NoteStep 4 To configure the hash key of a peer mobility controller, which is a virtual controller in the same domain, enter thiscommand:config mobility group member hash peer-ip-address keyStep 5 Enable or disable multicast mobility mode by entering this command:config mobility multicast-mode {enable |disable}local_group_multicast_addresswhere local_group_multicast_address is the multicast group IP address for the local mobility group. This address is usedfor multicast mobility messaging.If you enable multicast mobility mode, the controller uses multicast mode to send Mobile Announce messages to thelocal group. If you disable multicast mobility mode, the controller uses unicast mode to send the Mobile Announcemessages to the local group. The default value is disabled.Step 6 (Optional) You can also configure the multicast group IP address for nonlocal groups within the mobility list. To do so,enter this command:config mobility group multicast-address group_name IP_addressIf you do not configure the multicast IP address for nonlocal groups, the controller uses unicast mode to send mobilitymessages to those members.Step 7 Verify the mobility configuration by entering this command:show mobility summaryStep 8 To see the hash key of mobility group members in the same domain, enter this command:show mobility group member hashStep 9 Save your changes by entering this command:save configStep 10 Repeat this procedure on every controller to be included in the mobility group. All controllers in the mobility group mustbe configured with the MAC address and IP address of all other mobility group members.Step 11 Enable or disable debugging of multicast usage for mobility messages by entering this command:debug mobility multicast {enable |disable}   Cisco Wireless LAN Controller Configuration Guide, Release 7.4942 OL-28744-01  Configuring Mobility Groups (CLI)
CHAPTER 143Viewing Mobility Group Statistics•Viewing Mobility Group Statistics (GUI), page 943•Viewing Mobility Group Statistics (CLI), page 944Viewing Mobility Group Statistics (GUI)Step 1 Choose Monitor > Statistics > Mobility Statistics to open the Mobility Statistics page.This page contains the following fields•Group Mobility Statistics◦Rx Errors—Generic protocol packet receive errors, such as packet too short or format incorrect.◦Tx Errors—Generic protocol packet transmit errors, such as packet transmission fail.◦Responses Retransmitted—Mobility protocol that uses UDP and resends requests several times if it does notreceive a response. Because of network or processing delays, the responder may receive one or more retryrequests after it initially responds to a request. This text box shows a count of the response resends.◦Handoff Requests Received—Total number of handoff requests received, ignored, or responded to.◦Handoff End Requests Received—Total number of handoff end requests received. These requests are sentby the anchor or foreign controller to notify the other about the close of a client session.◦State Transitions Disallowed—Policy enforcement module (PEM) that has denied a client state transition,usually resulting in the handoff being aborted.◦Resource Unavailable—Necessary resource, such as a buffer, was unavailable, resulting in the handoff beingaborted.•Mobility Initiator Statistics◦Handoff Requests Sent—Number of clients that have associated to the controller and have been announcedto the mobility group.◦Handoff Replies Received—Number of handoff replies that have been received in response to the requestssent.Cisco Wireless LAN Controller Configuration Guide, Release 7.4        OL-28744-01 943
◦Handoff as Local Received—Number of handoffs in which the entire client session has been transferred.◦Handoff as Foreign Received—Number of handoffs in which the client session was anchored elsewhere.◦Handoff Denys Received—Number of handoffs that were denied.◦Anchor Request Sent—Number of anchor requests that were sent for a three-party (foreign-to-foreign) handoff.The handoff was received from another foreign controller, and the new controller is requesting the anchor tomove the client.◦Anchor Deny Received—Number of anchor requests that were denied by the current anchor.◦Anchor Grant Received—Number of anchor requests that were approved by the current anchor.◦Anchor Transfer Received—Number of anchor requests that closed the session on the current anchor andtransferred the anchor back to the requestor.•Mobility Responder Statistics◦Handoff Requests Ignored—Number of handoff requests or client announcements that were ignored becausethe controller had no knowledge of that client.◦Ping Pong Handoff Requests Dropped—Number of handoff requests that were denied because the handoffperiod was too short (3 seconds).◦Handoff Requests Dropped—Number of handoff requests that were dropped due to either an incompleteknowledge of the client or a problem with the packet.◦Handoff Requests Denied—Number of handoff requests that were denied.◦Client Handoff as Local—Number of handoff responses sent while the client is in the local role.◦Client Handoff as Foreign—Number of handoff responses sent while the client is in the foreign role.◦Anchor Requests Received—Number of anchor requests received.◦Anchor Requests Denied—Number of anchor requests denied.◦Anchor Requests Granted—Number of anchor requests granted.◦Anchor Transferred—Number of anchors transferred because the client has moved from a foreign controllerto a controller on the same subnet as the current anchor.Step 2 If you want to clear the current mobility statistics, click Clear Stats.Viewing Mobility Group Statistics (CLI)•See mobility group statistics by entering the show mobility statistics command.•To clear the current mobility statistics, enter the clear stats mobility command.   Cisco Wireless LAN Controller Configuration Guide, Release 7.4944 OL-28744-01  Viewing Mobility Group Statistics (CLI)
CHAPTER 144Configuring Auto-Anchor Mobility•Information About Auto-Anchor Mobility, page 945•Guidelines and Limitations, page 946•Configuring Auto-Anchor Mobility (GUI), page 947•Configuring Auto-Anchor Mobility (CLI), page 947Information About Auto-Anchor MobilityYou can use auto-anchor mobility (also called guest tunneling) to improve load balancing and security forroaming clients on your wireless LANs. Under normal roaming conditions, client devices join a wireless LANand are anchored to the first controller that they contact. If a client roams to a different subnet, the controllerto which the client roamed sets up a foreign session for the client with the anchor controller. However, whenyou use the auto-anchor mobility feature, you can specify a controller or set of controllers as the anchor pointsfor clients on a wireless LAN.In auto-anchor mobility mode, a subset of a mobility group is specified as the anchor controllers for a WLAN.You can use this feature to restrict a WLAN to a single subnet, regardless of a client’s entry point into thenetwork. Clients can then access a guest WLAN throughout an enterprise but still be restricted to a specificsubnet. Auto-anchor mobility can also provide geographic load balancing because the WLANs can representa particular section of a building (such as a lobby, a restaurant, and so on), effectively creating a set of homecontrollers for a WLAN. Instead of being anchored to the first controller that they happen to contact, mobileclients can be anchored to controllers that control access points in a particular vicinity.When a client first associates to a controller of a mobility group that has been preconfigured as a mobilityanchor for a WLAN, the client associates to the controller locally, and a local session is created for the client.Clients can be anchored only to preconfigured anchor controllers of the WLAN. For a given WLAN, youshould configure the same set of anchor controllers on all controllers in the mobility group.When a client first associates to a controller of a mobility group that has not been configured as a mobilityanchor for a WLAN, the client associates to the controller locally, a local session is created for the client, andthe client is announced to the other controllers in the mobility list. If the announcement is not answered, thecontroller contacts one of the anchor controllers configured for the WLAN and creates a foreign session forthe client on the local switch. Packets from the client are encapsulated through a mobility tunnel using EtherIPand sent to the anchor controller, where they are decapsulated and delivered to the wired network. Packets tothe client are received by the anchor controller and forwarded to the foreign controller through a mobilitytunnel using EtherIP. The foreign controller decapsulates the packets and forwards them to the client.Cisco Wireless LAN Controller Configuration Guide, Release 7.4        OL-28744-01 945
If multiple controllers are added as mobility anchors for a particular WLAN on a foreign controller, the foreigncontroller internally sorts the controller by their IP address. The controller with the lowest IP address is thefirst anchor. For example, a typical ordered list would be 172.16.7.25, 172.16.7.28, 192.168.5.15. If the firstclient associates to the foreign controller's anchored WLAN, the client database entry is sent to the first anchorcontroller in the list, the second client is sent to the second controller in the list, and so on, until the end ofthe anchor list is reached. The process is repeated starting with the first anchor controller. If any of the anchorcontroller is detected to be down, all the clients anchored to the controller are deauthenticated, and the clientsthen go through the authentication/anchoring process again in a round-robin manner with the remainingcontroller in the anchor list. This functionality is also extended to regular mobility clients through mobilityfailover. This feature enables mobility group members to detect failed members and reroute clients.Guidelines and Limitations•Mobility list members can send ping requests to one another to check the data and control paths amongthem to find failed members and reroute clients. You can configure the number and interval of pingrequests that are sent to each anchor controller. This functionality provides guest N+1 redundancy forguest tunneling and mobility failover for regular mobility.•You must add controllers to the mobility group member list before you can designate them as mobilityanchors for a WLAN.•You can configure multiple controllers as mobility anchors for a WLAN.•Auto-anchor mobility supports web authentication but does not support other Layer 3 security types.•You must configure the WLANs on both the foreign controller and the anchor controller with mobilityanchors. On the anchor controller, configure the anchor controller itself as a mobility anchor. On theforeign controller, configure the anchor as a mobility anchor.•Auto-anchor mobility is not supported for use with DHCP option 82.•When using the guest N+1 redundancy and mobility failover features with a firewall, make sure that thefollowing ports are open:◦UDP 16666 for tunnel control traffic◦IP Protocol 97 for user data traffic◦UDP 161 and 162 for SNMP•A client, when it moves from anchor controller to foreign controller, sends th•In case of roaming between anchor controller and foreign mobility, the client addresses learned at theanchor controller is shown at the foreign controller. You must check the foreign controller to view theRA throttle statistics.•For Layer 3 RADIUS authentication, the RADIUS requests for authentication are sent by the anchorcontroller.   Cisco Wireless LAN Controller Configuration Guide, Release 7.4946 OL-28744-01  Guidelines and Limitations
Configuring Auto-Anchor Mobility (GUI)Step 1 Configure the controller to detect failed anchor controllers within a mobility group as follows:a) Choose Controller >Mobility Management >Mobility Anchor Config to open the Mobility Anchor Config page.b) In the Keep Alive Count text box, enter the number of times a ping request is sent to an anchor controller before theanchor is considered to be unreachable. The valid range is 3 to 20, and the default value is 3.c) In the Keep Alive Interval text box, enter the amount of time (in seconds) between each ping request that is sent toan anchor controller. The valid range is 1 to 30 seconds, and the default value is 10 seconds.d) In the DSCP Value text box, enter the DSCP value. The default is 0.e) Click Apply to commit your changes.Step 2 Choose WLANs to open the WLANs page.Step 3 Click the blue drop-down arrow for the desired WLAN or wired guest LAN and choose Mobility Anchors. The MobilityAnchors page appears.This page lists the controllers that have already been configured as mobility anchors and shows the current state of theirdata and control paths. Controllers within a mobility group communicate among themselves over a well-known UDPport and exchange data traffic through an Ethernet-over-IP (EoIP) tunnel. They send mpings, which test mobility controlpacket reachability over the management interface over mobility UDP port 16666 and they send epings, which test themobility data traffic over the management interface over EoIP port 97. The Control Path text box shows whether mpingshave passed (up) or failed (down), and the Data Path text box shows whether epings have passed (up) or failed (down).If the Data or Control Path text box shows “down,”the mobility anchor cannot be reached and is considered failed.Step 4 Select the IP address of the controller to be designated a mobility anchor in the Switch IP Address (Anchor) drop-downlist.Step 5 Click Mobility Anchor Create. The selected controller becomes an anchor for this WLAN or wired guest LAN.To delete a mobility anchor for a WLAN or wired guest LAN, hover your cursor over the blue drop-down arrowfor the anchor and choose Remove.NoteStep 6 Click Save Configuration.Step 7 Repeat Step 4 and Step 6 to set any other controllers as mobility anchors for this WLAN or wired guest LAN.Step 8 Configure the same set of mobility anchors on every controller in the mobility group.Configuring Auto-Anchor Mobility (CLI)•The controller is programmed to always detect failed mobility list members. To change the parametersfor the ping exchange between mobility members, enter these commands:◦config mobility group keepalive count count—Specifies the number of times a ping request issent to a mobility list member before the member is considered to be unreachable. The valid rangeis 3 to 20, and the default value is 3.◦config mobility group keepalive interval seconds—Specifies the amount of time (in seconds)between each ping request sent to a mobility list member. The valid range is 1 to 30 seconds, andthe default value is 10 seconds.Cisco Wireless LAN Controller Configuration Guide, Release 7.4       OL-28744-01 947Configuring Auto-Anchor Mobility (GUI)
•Disable the WLAN or wired guest LAN for which you are configuring mobility anchors by enteringthis command:config {wlan | guest-lan} disable {wlan_id | guest_lan_id}•Create a new mobility anchor for the WLAN or wired guest LAN by entering one of these commands:◦config mobility group anchor add {wlan | guest-lan} {wlan_id | guest_lan_id}anchor_controller_ip_address◦config {wlan | guest-lan}mobility anchor add {wlan_id | guest_lan_id}anchor_controller_ip_addressThe wlan_id or guest_lan_id must exist and be disabled, and theanchor_controller_ip_address must be a member of the default mobility group.NoteAuto-anchor mobility is enabled for the WLAN or wired guest LAN when you configurethe first mobility anchor.Note•Delete a mobility anchor for the WLAN or wired guest LAN by entering one of these commands:◦config mobility group anchor delete {wlan | guest-lan} {wlan_id | guest_lan_id}anchor_controller_ip_address◦config {wlan | guest-lan} mobility anchor delete {wlan_id | guest_lan_id}anchor_controller_ip_addressThe wlan_id or guest_lan_id must exist and be disabled.NoteDeleting the last anchor disables the auto-anchor mobility feature and resumes normalmobility for new associations.Note•Save your settings by entering this command:save config•See a list and status of controllers configured as mobility anchors for a specific WLAN or wired guestLAN by entering this command:show mobility anchor {wlan |guest-lan} {wlan_id |guest_lan_id}   Cisco Wireless LAN Controller Configuration Guide, Release 7.4948 OL-28744-01  Configuring Auto-Anchor Mobility (CLI)
The wlan_id and guest_lan_id parameters are optional and constrain the list to theanchors in a particular WLAN or guest LAN. To see all of the mobility anchors on yoursystem, enter the show mobility anchor command.The Status text box shows one of these values:UP—The controller is reachable and able to pass data.CNTRL_PATH_DOWN—The mpings failed. The controller cannot be reached throughthe control path and is considered failed.DATA_PATH_DOWN—The epings failed. The controller cannot be reached and isconsidered failed.CNTRL_DATA_PATH_DOWN—Both the mpings and epings failed. The controllercannot be reached and is considered failed.Note•See the status of all mobility group members by entering this command:show mobility summary•Troubleshoot mobility issues by entering these commands:◦debug mobility handoff {enable |disable}—Debugs mobility handoff issues.◦debug mobility keep-alive {enable |disable}all—Dumps the keepalive packets for all mobilityanchors.◦debug mobility keep-alive {enable |disable}IP_address—Dumps the keepalive packets for aspecific mobility anchor.Cisco Wireless LAN Controller Configuration Guide, Release 7.4       OL-28744-01 949Configuring Auto-Anchor Mobility (CLI)
   Cisco Wireless LAN Controller Configuration Guide, Release 7.4950 OL-28744-01  Configuring Auto-Anchor Mobility (CLI)
CHAPTER 145Validating WLAN Mobility Security Values•Information About WLAN Mobility Security Values, page 951Information About WLAN Mobility Security ValuesFor any anchoring or mobility event, the WLAN security policy values on each controller must match. Thesevalues can be validated in the controller debugs. This table lists the WLAN mobility security values and theircorresponding security policy.Table 29: WLAN Mobility Security ValuesSecurity PolicySecurity Hexadecimal ValueSecurity_None0x00000000Security_WEP0x00000001Security_802_1X0x00000002Security_IPSec*0x00000004Security_IPSec_Passthrough*0x00000008Security_Web0x00000010Security_PPTP*0x00000020Security_DHCP_Required0x00000040Security_WPA_NotUsed0x00000080Security_Cranite_Passthrough*0x00000100Security_Fortress_Passthrough*0x00000200Security_L2TP_IPSec*0x00000400Cisco Wireless LAN Controller Configuration Guide, Release 7.4        OL-28744-01 951
Security PolicySecurity Hexadecimal ValueSecurity_802_11i_NotUsedControllers running software release 6.0 or later donot support this security policy.Note0x00000800Security_Web_Passthrough0x00001000   Cisco Wireless LAN Controller Configuration Guide, Release 7.4952 OL-28744-01  Information About WLAN Mobility Security Values
CHAPTER 146Using Symmetric Mobility Tunneling•Information About Symmetric Mobility Tunneling, page 953•Guidelines and Limitations, page 954•Verifying Symmetric Mobility Tunneling (GUI), page 954•Verifying if Symmetric Mobility Tunneling is Enabled (CLI), page 954Information About Symmetric Mobility TunnelingWhen symmetric mobility tunneling is enabled, all client traffic is sent to the anchor controller and can thensuccessfully pass the RPF check.Figure 74: Symmetric Mobility Tunneling or Bi-Directional TunnelingSymmetric mobility tunneling is also useful in the following situations:•If a firewall installation in the client packet path drops packets because the source IP address does notmatch the subnet on which the packets are received.Cisco Wireless LAN Controller Configuration Guide, Release 7.4        OL-28744-01 953
•If the access-point group VLAN on the anchor controller is different than the WLAN interface VLANon the foreign controller. In this case, client traffic could be sent on an incorrect VLAN during mobilityevents.Guidelines and Limitations•Symmetric mobility tunneling is enabled by default.Verifying Symmetric Mobility Tunneling (GUI)Step 1 Choose Controller >Mobility Management >Mobility Anchor Config to open the Mobility Anchor Config page.Step 2 The Symmetric Mobility Tunneling Mode text box shows Enabled.Verifying if Symmetric Mobility Tunneling is Enabled (CLI)Verify that symmetric mobility tunneling is enabled by entering this command:show mobility summary   Cisco Wireless LAN Controller Configuration Guide, Release 7.4954 OL-28744-01  Guidelines and Limitations
CHAPTER 147Running Mobility Ping Tests•Information About Mobility Ping Tests, page 955•Guidelines and Limitations, page 955•Running Mobility Ping Tests (CLI), page 956Information About Mobility Ping TestsControllers in a mobility list communicate with each other by controlling information over a well-knownUDP port and exchanging data traffic through an Ethernet-over-IP (EoIP) tunnel. Because UDP and EoIP arenot reliable transport mechanisms, there is no guarantee that a mobility control packet or data packet will bedelivered to a mobility peer. Mobility packets may be lost in transit due to a firewall filtering the UDP portor EoIP packets or due to routing issues.Guidelines and LimitationsController software release 4.0 or later releases enable you to test the mobility communication environmentby performing mobility ping tests. These tests may be used to validate connectivity between members of amobility group (including guest controllers). Two ping tests are available:•Mobility ping over UDP—This test runs over mobility UDP port 16666. It tests whether the mobilitycontrol packet can be reached over the management interface.•Mobility ping over EoIP—This test runs over EoIP. It tests the mobility data traffic over the managementinterface.Only one mobility ping test per controller can be run at a given time.These ping tests are not Internet Control Message Protocol (ICMP) based. The term “ping”is used toindicate an echo request and an echo reply message.NoteCisco Wireless LAN Controller Configuration Guide, Release 7.4        OL-28744-01 955
Any ICMP packet greater than 1280 bytes will always be responded with a packet that is truncated to1280 bytes. For example, a ping with a packet that is greater than 1280 bytes from a host to the managementinterface is always responded with a packet that is truncated to 1280 bytes.NoteRunning Mobility Ping Tests (CLI)•To test the mobility UDP control packet communication between two controllers, enter this command:mping mobility_peer_IP_addressThe mobility_peer_IP_address parameter must be the IP address of a controller that belongs to themobility list.•To test the mobility EoIP data packet communication between two controllers, enter this command:eping mobility_peer_IP_addressThe mobility_peer_IP_address parameter must be the IP address of a controller that belongs to themobility list.•To troubleshoot your controller for mobility ping, enter these commands:config logging buffered debuggingshow loggingTo troubleshoot your controller for mobility ping over UDP, enter this command to display the mobilitycontrol packet:debug mobility handoff enableWe recommend using an ethereal trace capture when troubleshooting.Note   Cisco Wireless LAN Controller Configuration Guide, Release 7.4956 OL-28744-01  Running Mobility Ping Tests (CLI)
CHAPTER 148Configuring Dynamic Anchoring for Clients withStatic IP Addresses•Information About Dynamic Anchoring for Clients with Static IP, page 957•Guidelines and Limitations, page 958•Configuring Dynamic Anchoring of Static IP Clients (GUI), page 958•Configuring Dynamic Anchoring of Static IP Clients (CLI), page 959Information About Dynamic Anchoring for Clients with Static IPAt times you may want to configure static IP addresses for wireless clients. When these wireless clients moveabout in a network, they could try associating with other controllers. If the clients try to associate with acontroller that does not support the same subnet as the static IP, the clients fail to connect to the network. Youcan now enable dynamic tunneling of clients with static IP addresses.Dynamic anchoring of static IP clients with static IP addresses can be associated with other controllers wherethe client’s subnet is supported by tunneling the traffic to another controller in the same mobility group. Thisfeature enables you to configure your WLAN so that the network is serviced even though the clients use staticIP addresses.How Dynamic Anchoring of Static IP Clients WorksThe following sequence of steps occur when a client with a static IP address tries to associate with a controller:1When a client associates with a controller, for example, WLC-1, it performs a mobility announcement. Ifa controller in the mobility group responds (for example WLC-2), the client traffic is tunneled to thecontroller WLC-2. As a result, the controller WLC 1 becomes the foreign controller and WLC-2 becomesthe anchor controller.2If none of the controllers responds, the client is treated as a local client and authentication is performed.The IP address for the client is updated either through an orphan packet handling or an ARP requestprocessing. If the IP subnet of the client is not supported in the controller (WLC-1), WLC-1 sends anotherstatic IP mobile announce and if a controller (for example WLC-3) that supports the client's subnet respondsto that announcement, the client traffic is tunneled to that controller, that is WLC-3. As a result, thecontroller WLC 1 becomes the export foreign controller and WLC-3 becomes the export anchor controller.Cisco Wireless LAN Controller Configuration Guide, Release 7.4        OL-28744-01 957
3Once the acknowledgement is received, the client traffic is tunneled between the anchor and the controller(WLC-1).If you configure WLAN with an interface group and any of the interfaces in the interface group supportsthe static IP client subnet, the client is assigned to that interface. This situation occurs in local or remote(static IP Anchor) controller.NoteA security level 2 authentication is performed only in the local (static IP foreign) controller, which is alsoknown as the exported foreign controller.NoteGuidelines and Limitations•Do not configure overridden interfaces when you perform AAA for static IP tunneling, this is becausetraffic can get blocked for the client if the overridden interface does not support the client’s subnet. Thiscan be possible in extreme cases where the overriding interface group supports the client’s subnet.•The local controller must be configured with the correct AAA server where this client entry is present.The following restrictions apply when configuring static IP tunneling with other features on the same WLAN:•Auto anchoring mobility (guest tunneling) cannot be configured for the same WLAN.•FlexConnect local authentication cannot be configured for the same WLAN.•The DHCP required option cannot be configured for the same WLAN.•You cannot configure dynamic anchoring of static IP clients with FlexConnect local switching.Configuring Dynamic Anchoring of Static IP Clients (GUI)Step 1 Choose WLANs to open the WLANs page.Step 2 Click the ID number of the WLAN on which you want to enable dynamic anchoring of IP clients. The WLANs > Editpage is displayed.Step 3 Choose the Advanced tab to open the WLANs > Edit (Advanced) page.Step 4 Enable dynamic anchoring of static IP clients by selecting the Static IP Tunneling check box.Step 5 Click Apply to commit your changes.   Cisco Wireless LAN Controller Configuration Guide, Release 7.4958 OL-28744-01  Guidelines and Limitations
Configuring Dynamic Anchoring of Static IP Clients (CLI)config wlan static-ip tunneling {enable | disable} wlan_id—Enables or disables the dynamic anchoring ofstatic IP clients on a given WLAN.To monitor and troubleshoot your controller for clients with static IP, use the following commands:•show wlan wlan_id—Enables you to see the status of the static IP clients feature.…………..Static IP client tunneling.............. Enabled…………..•debug client client-mac•debug dot11 mobile enable•debug mobility handoff enableCisco Wireless LAN Controller Configuration Guide, Release 7.4       OL-28744-01 959Configuring Dynamic Anchoring of Static IP Clients (CLI)
   Cisco Wireless LAN Controller Configuration Guide, Release 7.4960 OL-28744-01  Configuring Dynamic Anchoring of Static IP Clients (CLI)
CHAPTER 149Configuring Foreign Mappings•Information About Foreign Mappings, page 961•Configuring Foreign Controller MAC Mapping (GUI), page 961•Configuring Foreign Controller MAC Mapping (CLI), page 961Information About Foreign MappingsAuto-Anchor mobility, also known as Foreign Mapping, allows you to configure users that are on differentforeign controllers from different physical location to obtain IP addresses from a subnet or group of subnetsbased on their physical location.Configuring Foreign Controller MAC Mapping (GUI)Step 1 Choose the WLANs tab.The WLANs page appears listing the available WLANs.Step 2 Click the Blue drop down arrow for the desired WLAN and choose Foreign-Maps.The foreign mappings page appears. This page also lists the MAC addresses of the foreign controllers that are in themobility group and interfaces/interface groups.Step 3 Choose the desired foreign controller MAC and the interface or interface group to which it must be mapped and clickon Add Mapping.Configuring Foreign Controller MAC Mapping (CLI)•To add foreign controller mapping, enter this command:config wlan mobility foreign-map add wlan-id foreign_ctlr_mac interface/interface_grp nameCisco Wireless LAN Controller Configuration Guide, Release 7.4        OL-28744-01 961
   Cisco Wireless LAN Controller Configuration Guide, Release 7.4962 OL-28744-01  Configuring Foreign Controller MAC Mapping (CLI)
CHAPTER 150Configuring Proxy Mobile IPv6•Information About Proxy Mobile IPv6, page 963•Guidelines and Limitations, page 963•Configuring Proxy Mobile IPv6 (GUI), page 964•Configuring Proxy Mobile IPv6 (CLI), page 965Information About Proxy Mobile IPv6Proxy Mobile IPv6 (PMIPv6) is a network-based mobility management protocol that supports a mobile nodeby acting as the proxy for the mobile node in any IP mobility-related signaling. The mobility entities in thenetwork track the movements of the mobile node and initiate the mobility signaling and set up the requiredrouting state.The main functional entities are the Local Mobility Anchor (LMA) and Mobile Access Gateway (MAG). TheLMA maintains the reachability state of the mobile node and is the topological anchor point for the IP addressof the mobile node. The MAG performs the mobility management on behalf of a mobile node. The MAGresides on the access link where the mobile node is anchored. The controller implements the MAG functionality.In the Cisco 5500 Series, Cisco WiSM2, and Cisco 8500 Series controllers, PMIPv6 Mobility Access Gateway(MAG) support for integration with Local Mobility Anchor (LMA) such as Cisco ASR 5000 Series in cellulardata networks.For PMIPv6 clients, controller supports both central web authentication and local web authentication.Guidelines and Limitations•IPv6/dual stack clients are supported. IPv6 clients are not supported. IPv6 addresses for the client arenot learnt if the WLAN is marked for PMIPv6.•PMIPv6 is not supported on local switching WLANs on FlexConnect APs.•Roaming between controllers is supported only on PMIPv6-enabled WLANs.Cisco Wireless LAN Controller Configuration Guide, Release 7.4        OL-28744-01 963
Configuring Proxy Mobile IPv6 (GUI)Step 1 Choose Controller > PMIPv6 > General to open the PMIPv6 General page.Step 2 Enter the values for the following parameters:•Maximum Bindings Allowed—Maximum number of binding updates that the controller can send to the MAG.The valid range is between 0 to 40000.•Binding Lifetime—Lifetime of the binding entries in the controller. The valid range is between 10 to 65535seconds. The default value is 3600. The binding lifetime should be a multiple of 4 seconds.•Binding Refresh Time—Refresh time of the binding entries in the controller. The valid range is between 4 to65535 seconds. The default value is 300 seconds. The binding refresh time should be a multiple of 4 seconds.•Binding Initial Retry Timeout—Initial timeout between the proxy binding updates (PBUs) when the controllerdoes not receive the proxy binding acknowledgments (PBAs). The valid range is between 100 to 65535 seconds.The default value is 1000 seconds.•Binding Maximum Retry Timeout—Maximum timeout between the proxy binding updates (PBUs) when thecontroller does not receive the proxy binding acknowledgments (PBAs). The valid range is between 100 to 65535seconds. The default value is 32000 seconds.•Replay Protection Timestamp—Maximum amount of time difference between the timestamp in the receivedproxy binding acknowledgment and the current time of the day. The valid range is between 1 to 255 milliseconds.The default value is 7 milliseconds.•Minimum BRI Retransmit Timeout—Minimum amount of time that the controller waits before retransmittingthe BRI message. The valid range is between 500 to 65535 seconds. The default value is 1000 seconds.•Maximum BRI Retransmit Timeout—Maximum amount of time that the controller waits before retransmittingthe Binding Revocation Indication (BRI) message. The valid range is between 500 to 65535 seconds. The defaultvalue is 2000 seconds.•BRI Retries—Maximum number of times that the controller retransmits the BRI message before receiving theBinding Revocation Acknowledgment (BRA) message. The valid range is between 1 to 10. The default value is 1.Step 3 Click Apply.To clear your configuration, click Clear Domain.Step 4 To create the LMA, follow these steps:a) Choose Controller > PMIPv6 > LMA and click New.b) Enter the values for the following parameters:•Member Name—Name of the LMA connected to the controller.•Member IP Address—IP address of the LMA connected to the controller.c) Click Apply.Step 5 To create a PMIPv6 profile, follow these steps:a) Choose Controller > PMIPv6 > Profiles and click New.b) On the PMIPv6 Profile > New page, enter the values for the following parameters:   Cisco Wireless LAN Controller Configuration Guide, Release 7.4964 OL-28744-01  Configuring Proxy Mobile IPv6 (GUI)
Profile Name—Name of the profile.••Network Access Identifier—Name of the Network Access Identifier (NAI) associated with the profile.•LMA Name—Name of the LMA to which the profile is associated.•Access Point Node—Name of the access point node connected to the controller.c) Click Apply.Step 6 On the PMIPv6 Profile > New page, enter the values for the following parameters:•Profile Name—Name of the profile.•Network Access Identifier—Name of the Network Access Identifier (NAI) associated with the profile.•LMA Name—Name of the LMA to which the profile is associated.•Access Point Node—Name of the access point node connected to the controller.Step 7 To configure PMIPv6 parameters for a WLAN, follow these steps:a) Choose WLANs > WLAN ID to open the WLANs > Edit page.b) Click the Advanced tab.c) Under PMIP from the PMIP Mobility Type drop-down list, choose the mobility type from the following options:•None—Configures the WLAN with Simple IP•PMIPv6—Configures the WLAN with only PMIPv6d) From the PMIP Profile drop-down list, choose the PMIP profile for the WLAN.e) In the PMIP Realm box, enter the default realm for the WLAN.f) Click Apply.Step 8 Click Save Configuration.Configuring Proxy Mobile IPv6 (CLI)Step 1 To configure MAG, use these commands:•To configure maximum binding update entries allowed, enter this command:config pmipv6 mag binding maximum units•To configure the binding entry lifetime, enter this command:config pmipv6 mag lifetime units•To configure the binding refresh interval, enter this command:config pmipv6 mag refresh-time unitsCisco Wireless LAN Controller Configuration Guide, Release 7.4       OL-28744-01 965Configuring Proxy Mobile IPv6 (CLI)
•To configure the initial timeout between PBUs if PBA does not arrive, enter this command:config pmipv6 mag init-retx-time units•To configure the maximum initial timeout between PBUs if PBA does not arrive, enter this command:config pmipv6 mag max-retx-time units•To configure the replay protection mechanism, enter this command:config pmipv6 mag replay-protection {timestamp window units |sequence-no |mobile-node-timestamp}•To configure the minimum or maximum amount of time in seconds that the MAG should wait before it retransmitsthe binding revocation indication (BRI) message, enter this command:config pmipv6 mag bri delay {min |max}units•To configure the maximum number of times the MAG should retransmit the BRI message before it receives thebinding revocation acknowledgment (BRA) message, enter this command:config pmipv6 mag bri retries units•To configure the list of LMAs for the MAG, enter this command:config pmipv6 mag lma lma-name ipv4-address ip-addressStep 2 To configure a PMIPv6 domain name, enter this command:config pmipv6 domain domain-nameThis command also enables the MAG functionality on thecontroller.NoteStep 3 To add a profile to a PMIPv6 domain, enter this command:config pmipv6 add profile profile-name nai {user@realm |@realm |*}lma lma-name apn apn-nameNAI stands for network access identifier. APN stands for access pointname.NoteStep 4 To delete a PMIPv6 entity, enter this command:config pmipv6 delete {domain domain-name |lma lma-name |profile profile-name nai {user@realm |@realm |*}}Step 5 To configure the PMIPv6 parameters for the WLAN, use these commands:•To configure the default realm for the WLAN, enter this command:config wlan pmipv6 default-realm {realm-name |none}wlan-id•To configure the mobility type for a WLAN or for all WLANs, enter this command:config wlan pmipv6 mobility-type {none |pmipv6} {wlan-id |all}•To configure the profile name for a PMIPv6 WLAN, enter this command:config wlan pmipv6 profile-name name wlan-idStep 6 Save your changes by entering this command:save configStep 7 To see the PMIPv6 configuration details, use the following show commands:•To see the details of a profile of a PMIPv6 domain, enter this command:show pmipv6 domain domain-name profile profile-name   Cisco Wireless LAN Controller Configuration Guide, Release 7.4966 OL-28744-01  Configuring Proxy Mobile IPv6 (CLI)
•To see a summary of all the PMIPv6 profiles, enter this command:show pmipv6 profile summary•To see the global information about the PMIPv6 for a MAG, enter this command:show pmipv6 mag globals•To see information about the MAG bindings for LMA or NAI, enter this command:show pmipv6 mag bindings {lma lma-name |nai nai-name}•To see statistical information about MAG, enter this command:show pmipv6 mag stats domain domain-name peer peer-name•To see information about PMIPv6 for all clients, enter this command:show client summary•To see information about PMIPv6 for a client, enter this command:show client details client-mac-address•To see information about PMIPv6 for a WLAN, enter this command:show wlan wlan-idCisco Wireless LAN Controller Configuration Guide, Release 7.4       OL-28744-01 967Configuring Proxy Mobile IPv6 (CLI)
   Cisco Wireless LAN Controller Configuration Guide, Release 7.4968 OL-28744-01  Configuring Proxy Mobile IPv6 (CLI)
INDEX11n Mode parameter 831250 series access points 801, 802, 803and PoE Status field 803operating modes when using PoE 801transmit power settings when using PoE 8027920 AP CAC parameter 5937920 Client CAC parameter 5937920 support mode 592configuring 592described 5927921 support mode 592802.11a (or 802.11b) > Client Roaming page 117802.11a (or 802.11b) > Voice Parameters page 140, 143, 151802.11a (or 802.11b/g) > EDCA Parameters page 153802.11a (or 802.11b/g) Global Parameters page 75, 856802.11a (or 802.11b/g) Network Status parameter 75, 86, 87802.11a/n (or 802.11b/g/n) Radios page 145, 848802.11a/n Radios page (from Monitor Menu) 692, 695802.11g Support parameter 75802.11h Global Parameters page 86802.11h, described 86802.11n 83, 807clients 807devices 83802.1Q VLAN trunk port 290802.1X 556, 568dynamic key settings 556configuring 556described 568802.1X authentication for access points 701, 703, 704configuring 703, 704the switch 704using the CLI 703, 704described 701802.1x Authentication parameter 702802.3 bridging 103, 104configuring using the CLI 104configuring using the GUI 103, 104802.3 Bridging parameter 104802.3 frames 103802.3X flow control, enabling 104AAccess Control List Name parameter 426access control lists (ACLs) 274, 425, 426, 430, 431, 910applying to a WLAN 431using the CLI 431applying to the controller CPU 431using the CLI 431configuring 430, 431using the CLI 430, 431counters 426, 430configuring using the CLI 430configuring using the GUI 426rules 425, 430, 910using with the debug facility 274Access Control Lists > Edit page 428, 912Access Control Lists > New page 426Access Control Lists page 426Access Mode parameter 95, 210access point core dumps, uploading 723using the GUI 723access point count, approved tiers for 5500 series controllers 56access point event logs, viewing 254access point groups 624, 625, 626, 627assigning access points to 625, 626using the CLI 626using the GUI 625creating 626using the CLI 626removing 624, 626using the CLI 626using the GUI 624viewing 626, 627access point monitor service, debugging 283access point radios, searching for 693, 696access points 116, 242, 684, 685, 709, 710, 711, 714, 719, 727, 728assisted roaming 116authorization list 714authorizing 709, 710, 711using LSCs 711using MICs 710using SSCs 709Cisco Wireless LAN Controller Configuration Guide, Release 7.4       OL-28744-01 IN-1
access points (continued)LEDs 242interpreting 242priming 684supporting oversized images 727, 728verifying that they join the controller 685viewing join information 719using the GUI 719Accounting Server parameters 640ACL Name parameter 428, 429ACL. See access control lists (ACLs) 425, 909Action parameter 428, 912active exploits 513Add AAA Client page (on CiscoSecure ACS) 353, 376Add AP button 918Add New Rule button 426Admin Status parameter 315, 316administrator access 208Admission Control (ACM) parameter 140AES-CCMP 568Aggregated MAC Service Data Unit (A-MSDU) 85aggregation method, specifying 85AirMagnet Enterprise Analyzer 280Aironet IE parameter 614Airopeek 280All APs > Access Point Name > VLAN Mappings page 903All APs > Details for (Advanced) page 682, 724, 796configuring link latency 796All APs > Details for (Credentials) page 699, 702All APs > Details for (FlexConnect) page 903All APs > Details for (General) page 903All APs > Details for (High Availability) page 761, 774All APs page 687, 844AnchorTime parameter 827Anonymous Provision parameter 403Antenna Gain parameter 848Antenna parameter 848Antenna Type parameter 848AP > Clients > Traffic Stream Metrics page 145AP Authentication Policy page 435AP Core Dump parameter 724AP Ethernet MAC Addresses parameter 712AP Failover Priority parameter 774AP Group Name parameter 624AP Groups > Edit (APs) page 625AP Groups page 624, 646AP local authentication 907Using GUI 907AP Local Authentication on a WLAN 907Using the CLI 907AP Mode parameter 280, 744, 844, 903AP Name parameter 625AP Primary Discovery Timeout parameter 760ap-count evaluation licenses, activating 64, 65using the CLI 64, 65using the GUI 64AP-manager interface 292, 299and dynamic interfaces 292described 299AP801 access point 705described 705using with a controller 705Applying ACLs to a WLAN 429Applying ACLs to the controller CPU 429Assignment Method parameter 849authenticated local authentication bind method 394, 396Authority ID Information parameter 403, 919, 921Authority ID parameter 403, 919Authorize LSC APs against auth-list parameter 714Authorize MIC APs against auth-list or AAA parameter 714auto-anchor mobility 945, 947configuring 947using the GUI 947overview 945AutoInstall 39, 40, 41, 42described 39, 42example operation 42obtaining 40DHCP addresses for interfaces 40TFTP server information 40selecting configuration file 41using 39Average Data Rate parameter 124, 127, 588Average Real-Time Rate parameter 124, 127, 589Avoid Cisco AP Load parameter 827Avoid Foreign AP Interference parameter 827, 944Avoid Non-802.11a (802.11b) Noise parameter 827BBack-up Primary Controller Name field 760Back-up Secondary Controller Name parameter 760bandwidth-based CAC 138, 140, 142described 138enabling 140, 142using the CLI 142using the GUI 140Beacon Period parameter 75Bind Username parameter 394browsers supported 30Burst Data Rate parameter 124, 127, 589Burst Real-Time Rate parameter 124, 127, 589   Cisco Wireless LAN Controller Configuration Guide, Release 7.4IN-2 OL-28744-01  Index
CCA Server URL parameter 711CAC 143, 144, 146, 592configuring for 7920 phones 592enabling 143, 144using the CLI 144using the GUI 143viewing using the CLI 146capacity adder license. See licenses 55CCKM 569, 916configuring 569FlexConnect groups 916CCX 614, 791configuring Aironet IEs 614using the CLI 614described 614link test 791viewing a client’s version 614using the GUI 614CCX Layer 2 client roaming 116, 117, 118, 119configuring 118using the CLI 118debugging using the CLI 119described 116, 117obtaining information using the CLI 118CCX radio management 855features 855flexconnect considerations 855CCX Version parameter 614CCXv5 Req button 270CDP > AP Neighbors > Detail page 162CDP > Interface Neighbors > Detail page 161CDP > Traffic Metrics page 162CDP Advertisement Version parameter 159CDP AP Neighbors page 162CDP Protocol Status parameter 159CDP State parameter 160Certificate Authority (CA) certificates 193, 194, 195, 401, 404downloading 193, 194, 195using the CLI 194, 195using the GUI 193overview 193using with local EAP 401, 404Certificate File Name parameter 214Certificate File Path parameter 214Certificate Issuer parameter 403Certificate Password parameter 191, 214Certificate Type parameter 714Change Rules Priority parameter 466Channel Announcement parameter 86Channel Assignment Leader parameter 828Channel Assignment Method parameter 826Channel parameter 280, 848Channel Quiet Mode parameter 86Channel Scan Duration parameter 831Channel Width Parameter 828Check Against CA Certificates parameter 403Check Certificate Date Validity parameter 403chokepoints for RFID tag tracking 168CIDS Sensor Add page 482CIDS Shun List page 483ciphers 568, 569, 570configuring 569, 570described 568Cisco 2500 Series Controller 8Cisco 3300 Series Mobility Services Engine (MSE), using withwIPS 497Cisco 5500 Series Wireless LAN Controllers 9, 289, 290, 301, 303described 9multiple AP-manager interfaces 301, 303ports 289, 290Cisco 7921 Wireless IP Phones 591Cisco AV-pairs 637, 638Cisco Centralized Key Management (CCKM). See CCKM 568Cisco Clean Access (CCA) 645Cisco Discovery Protocol (CDP) 157, 159, 160, 161, 162, 163configuring 159, 160, 161using the CLI 160, 161using the GUI 159, 160described 157enabling using the GUI 159, 160supported devices 157viewing neighbors 161, 162, 163using the CLI 163using the GUI 161, 162viewing traffic information 163using the CLI 163Cisco Discovery Protocol parameter 159Cisco License Manager (CLM) 71and the controller license agent 71Cisco Licensing website 68Cisco Logo parameter 219Cisco Unified Wireless Network (UWN) Solution 6described 6Cisco Wireless Solution 3described 3CiscoSecure Access Control Server (ACS) 352Clear Filter link 526, 689, 719Clear Stats button 944Clear Stats on All APs button 719CLI 36, 38, 39, 52, 247enabling wireless connections 52logging into 36logging out 38navigating 39troubleshooting commands 247using 36, 39Cisco Wireless LAN Controller Configuration Guide, Release 7.4       OL-28744-01 IN-3Index
Client Certificate Required parameter 402client location, using Prime Infrastructure 8client MFP 434Client Protection parameter 436client reporting 270described 270client roaming, configuring 119Client Type parameter 755clients 614, 615, 807, 808, 907connecting to WLANs 907viewing 807, 808using the CLI 808using the GUI 807, 808viewing CCX version 614, 615using the CLI 615using the GUI 614Clients > AP > Traffic Stream Metrics page 145Clients > Detail page 755viewing client details 755viewing the status of workgroup bridges 755Commands > Reset to Factory Defaults page 171Community Name parameter 95conditional web redirect 637, 638described 638Conditional Web Redirect parameter 639Configuration File Encryption parameter 199configuration files 199, 200, 203downloading 199, 200using the GUI 199, 200editing 203configuration wizard 15, 27CLI version 27described 15Configuration Wizard - 802.11 Configuration page 25Configuration Wizard - Management Interface Configurationpage 20Configuration Wizard - Miscellaneous Configuration page 21Configuration Wizard - Service Interface Configuration page 19Configuration Wizard - Set Time page 26Configuration Wizard - SNMP Summary page 18, 20Configuration Wizard - System Information page 17Configuration Wizard - Virtual Interface Configuration page 22Configuration Wizard Completed page 27Configure Dynamic Anchoring of Static IP Clients 959Using the CLI 959Configure option for RRM override 848Configure RF Group 823Using CLI 823Configure RF Group Mode 822Using GUI 822Configuring a Spectrum Expert 885Configuring ACLs - GUI 426Configuring Cisco Cleanair 871Using the CLI 871Configuring Cisco CleanAir 869Using the GUI 869Configuring Client Exclusion Policies (CLI) 440Configuring Client Exclusion Policies (GUI) 439Configuring Controller (GUI) 16Configuring Country Codes (CLI) 783Configuring Country Codes (GUI) 782Configuring Coverage Hole Detection on a WLAN (GUI) 641Configuring Dynamic Anchoring of Static IP Clients 958Using the GUI 958Configuring FlexConnect APs using the CLI. 906configuring for the debug facility 276Configuring Sniffing on an Access Point 280Using the GUI 280Configuring Web Redirect (GUI) 639Control and Provisioning of Wireless Access Points protocol(CAPWAP) 679, 680, 683debugging 683described 679restrictions 680viewing MTU information 683Controller Time Source Valid parameter 436controllers 4, 5, 8, 178, 179, 202, 684configuration 202saving 202discovery process 684multiple-controller deployment 5overview 8platforms 8single-controller deployment 4upgrading software 178, 179using the CLI 179using the GUI 178core dump files 257, 260described 257uploading from a 5500 series controller to a TFTP or FTPserver 260Core Dump page 258Country Code parameter 783country codes 781, 784described 781viewing using the CLI 784Country page 783Coverage Exception Level per AP parameter 829coverage hole detection 640, 829, 830, 834configuring per controller 829, 830, 834using the CLI 834using the GUI 829, 830disabling on a WLAN 640described 640coverage hole detection and correction 821Coverage Hole Detection Enabled parameter 641CPUs, 5500 series controllers 245   Cisco Wireless LAN Controller Configuration Guide, Release 7.4IN-4 OL-28744-01  Index
crash files 256uploading 256using the CLI 256Creating Multiple AP Manager Interfaces - CLI 324Creating Multiple AP-Manager Interfaces (GUI) 324Custom Signatures page 490Ddata encryption 682, 683, 746and OfficeExtend access points 746configuring 682, 683using the CLI 682, 683using the GUI 682Data Encryption parameter 682, 744Data Path parameter 947Data Rates parameter 76date 43configuring through NTP server 43DCA Channel Sensitivity parameter 827DCA Channels parameter 828debug commands, sending 721debug facility 274, 275described 274, 275default enable password 697Default Mobility Group parameter 940Default Routers parameter 538default-group access point group 622Description parameter 386Destination parameter 427, 911Destination Port parameter 427, 911Detect and Report Ad-Hoc Networks parameter 456device certificates 190, 191downloading 190, 191using the GUI 190, 191overview 190DHCP Addr. Assignment Required parameter 535DHCP option 43, in controller discovery process 684DHCP option 82 421, 422configuring 422using the GUI 422described 421example 421DHCP Option 82 Remote ID Field Format parameter 422DHCP Parameters page 90, 91DHCP proxy 89, 91configuring 91using the CLI 91described 89DHCP scopes 537described 537DHCP Scopes page 537DHCP Server IP Addr parameter 535DHCP servers 533internal 533DHCP Timeout 91configurie using GUI 91diagnostic channel 265configuring 265using the GUI 265described 265Diagnostic Channel parameter 265directed roam request 117Direction parameter 428disabled clients, configuring a timeout 545discovery request timer, configuring 762distribution system ports 290Diversity parameter 848DNS Domain Name parameter 538DNS IP Address parameter 726DNS Servers parameter 538Domain Name parameter 726domain name server (DNS) discovery 684Download button 191, 194, 227downloading a CA certificate 194downloading a customized web authentication login page 227downloading a device certificate 191Download File to Controller page 188, 193, 199, 226downloading a customized web authentication login page 226downloading CA certificates 193downloading configuration files 199downloading login banner file 188Download SSL Certificate parameter 214DSCP parameter 428, 911DTIM 549DTLS 55DTLS data encryption. See data encryption 680DTPC Support parameter 76Dynamic Anchoring for Clients with Static IP Addresses 957Configuring 957dynamic AP management 297, 312for dynamic interface 312for the management interface 297Dynamic AP Management parameter 296, 311for dynamic interface 311for management interface 296dynamic AP-manager interface 292dynamic channel assignment (DCA) 819, 828, 829, 833, 83440-MHz channelization 828configuring 829, 833, 834using the CLI 833, 834using the GUI 829described 819dynamic interface example 302dynamic transmit power control, configuring 76Dynamic WEP Key Index parameter 401Cisco Wireless LAN Controller Configuration Guide, Release 7.4       OL-28744-01 IN-5Index
EEAP Profile Name parameter 403EAPOL-Key Max Retries parameter 402EAPOL-Key Timeout parameter 402EDCA Profile parameter 153Edit QoS Profile page 124Edit QoS Role Data Rates page 127Egress Interface parameter 235Email Input parameter 235Enable AP Local Authentication parameter 918Enable Authentication for Listener parameter 72Enable Check for All Standard and Custom Signaturesparameter 491Enable Counters parameter 426Enable Coverage Hole Detection parameter 829Enable CPU ACL parameter 429Enable Default Authentication parameter 72Enable DHCP Proxy parameter 90Enable Dynamic AP Management parameter 324Enable EAP-FAST Authentication parameter 919Enable LEAP Authentication parameter 919Enable Least Latency Controller Join parameter 744Enable Link Latency parameter 744, 796Enable Listener parameter 72Enable Low Latency MAC parameter 153Enable LSC on Controller parameter 711Enable NAT Address parameter 296Enable Notification parameter 72Enable OfficeExtend AP parameter 744Enable Password parameter 699Enable Server Status parameter 394Enable Tracking Optimization parameter 785Encryption Key parameter 576end-user license agreement (EULA) 58, 59enhanced distributed channel access (EDCA) parameters 154, 155configuring using the CLI 154, 155enhanced neighbor list 116request (E2E) 116described 116Enter Saved Permission Ticket File Name parameter 68EoIP port 955epings 956error codes, for failed VoIP calls 599Ethernet connection, using remotely 38evaluation licenses 56installed on 5500 series controllers 56event reporting for MFP 434Expedited Bandwidth parameter 141Expiration Timeout for Rogue AP and Rogue Client Entriesparameter 456Extensible Authentication Protocol (EAP) 404, 405, 407setting local timers 404, 405Extensible Authentication Protocol (EAP) (continued)timeout and failure counters 407per access point 407per client 407Ffactory default settings 171resetting using the GUI 171failover priority for access points 773, 774configuring 774using the GUI 774configuring 774using the CLI 774described 773viewing using the CLI 774failover protection 12Fallback Mode parameter 357fast heartbeat timer 759, 760, 761configuring 760, 761using the CLI 761using the GUI 760described 759fast SSID changing 101configuring using the GUI 101fault tolerance 892File Compression parameter 724File Name to Save Credentials parameter 68file transfers 11File Type parameter 177, 182, 184, 188, 191, 193, 195, 198, 199, 226, 262downloading a CA certificate 193downloading a configuration file 199downloading a customized web authentication login page 226downloading a device certificate 191Login Banner 188upgrading controller software 177, 182, 184uploading a configuration file 198uploading packet capture files 262uploading PACs 195filter, using to view clients 807, 808Fingerprint parameter 482FlexConnect 892, 894, 896, 902, 906authentication process 892, 896bandwidth restriction 894debugging 902, 906FlexConnect Group Support 917FlexConnect groups 915, 916, 917backup RADIUS server 916CCKM 916described 915local authentication 917   Cisco Wireless LAN Controller Configuration Guide, Release 7.4IN-6 OL-28744-01  Index
FlexConnect Mode AP Fast Heartbeat Timeout parameter 760Fragmentation Threshold parameter 76FTP server guidelines 174GGeneral (controller) page 321, 842configuring an RF group 842enabling link aggregation 321General (security) page 383General page 401Generate Rehost Ticket button 68Global AP Failover Priority parameter 774Global Configuration page 760, 774configuring backup controllers 760configuring failover priority for access points 774global credentials for access points 699overriding 699using the CLI 699using the GUI 699Group Mode parameter 843, 943Group Name parameter 918, 940Guest LAN parameter 235guest user accounts 208viewing 208using the CLI 208using the GUI 208Guest User parameter 386Guest User Role parameter 386guest WLAN, creating 207GUI 29, 30guidelines 30using 29Guidelines and Limitations for Predownloading 181HHeadline parameter 219hex2pcap sample output 277Holdtime parameter 159HTTP Access parameter 31HTTP Configuration page 31HTTPS Access parameter 31Hysteresis parameter 117IIdentity Request Max Retries parameter 401Identity Request Timeout parameter 401IDS sensors 481described 481IDS signatures 487, 491, 492, 493, 494described 487frequency 492MAC frequency 492, 493measurement interval 492pattern 491quiet time 492, 494tracking method 491IGMP Snooping 651IGMP Timeout parameter 108IKE Diffie Hellman Group parameter 357IKE Phase 1 parameter 357Index parameter for IDS 482infrastructure MFP 434components 434Ingress Interface parameter 235Injector Switch MAC Address parameter 803inline power 801Install License button 58inter-controller roaming 115, 932described 115example 932inter-release mobility 938inter-subnet mobility 937inter-subnet roaming 116, 934described 116illustrated 934Interface groups 328, 331Interface Name parameter 625, 646Interface parameter 535interfaces 291, 309overview 291, 309Interfaces > Edit page 324creating multiple AP-manager interfaces 324interference 820Interference threshold parameter 830Interferences 864Internet Group Management Protocol (IGMP) 106, 108, 109snooping 106configuring 108, 109using the CLI 109using the GUI 108Interval parameter 827intra-controller roaming 115, 931described 115illustrated 931Inventory page 789Invoke Channel Update Now button 826Invoke Power Update Now button 824IP address-to-MAC address binding 121described 121IP Mask parameter 95Cisco Wireless LAN Controller Configuration Guide, Release 7.4       OL-28744-01 IN-7Index
IPSec parameter 356JJapanese country codes 782KKeep Alive Count parameter 947Keep Alive Interval parameter 947Key Encryption Key (KEK) parameter 356Key Index parameter 576key permutation 575, 576, 577configuring 576, 577described 575Key Size parameter 576Key Wrap Format parameter 355Key Wrap parameter 355, 356LLAG Mode on Next Reboot parameter 321Last Auto Channel Assignment parameter 828Layer 2 7operation 7Layer 2 Security parameter 569, 576, 639Layer 3 7, 350operation 7security 350described 350Layer 3 Security parameter 235, 580, 582, 585, 639for VPN passthrough 580, 585for web authentication 582for web redirect 639for wired guest access 235LDAP 395choosing server priority order 395configuring 395using the GUI 395LDAP server 395assigning to WLANs 395LDAP Servers page 394LDAP Servers parameter 403Lease Time parameter 538LEDs 242, 810configuring 810interpreting 242license agent 71described 71License Commands page 58License Detail page 60, 63licenses 56, 57, 58, 59, 60, 67, 68, 69, 70installing 58, 59using the CLI 59using the GUI 58, 59obtaining 56, 58rehosting 67, 68, 69described 67using the GUI 68, 69removing 59, 60using the CLI 59using the GUI 60saving 58, 59using the CLI 59using the GUI 58SKUs 57transferring to a replacement controller after an RMA 70viewing 60using the CLI 60Licenses page 59, 63Lifetime parameter 207, 386lightweight mode, reverting to autonomous mode 708link aggregation (LAG) 319, 320described 319illustrated 320link latency 746, 795and OfficeExtend access points 746described 795Link Status parameter 315link test 791, 792performing 792using the CLI 792using the GUI 792types of packets 791Link Test 792button 792option 792Link Trap parameter 316Listener Message Processing URL parameter 72load-based CAC 138, 141described 138enabling 141using the GUI 141Lobby Ambassador Guest Management > Guest Users Listpage 207Local Auth Active Timeout parameter 401Local Authentication on a WLAN 907using the GUI 907local authentication, local switching 893local EAP 400, 406, 407, 408debugging 407, 408example 400viewing information using the CLI 406Local EAP Authentication parameter 403   Cisco Wireless LAN Controller Configuration Guide, Release 7.4IN-8 OL-28744-01  Index
Local Management Users > New page 206Local Management Users page 205Local Mode AP Fast Heartbeat Timer parameter 760Local Net Users > New page 386local significant certificate (LSC) 711, 712configuring 711, 712using the GUI 711, 712described 711Local Significant Certificates (LSC) - AP Provisioning page 711Local Significant Certificates (LSC) - General page 711local user database, capacity 205location 856calibration 856login banner file 187, 188, 189, 190clearing 190described 187downloading 188, 189using the CLI 189using the GUI 188, 189logs 255, 257, 271RSNA 271uploading 255, 257using the CLI 257using the GUI 255LWAPP-enabled access points 708, 709, 721, 722, 723, 725debug commands 721disabling the reset button 725retrieving radio core dumps 722reverting to autonomous mode 708, 709sending crash information to controller 721uploading 722, 723access point core dumps 723radio core dumps 722, 723MMAC address of access point 725displayed on controller GUI 725MAC filtering 541, 545configuring on WLANs 541, 545management frame protection (MFP) 433types 433Management Frame Protection parameter 436management frame validation 434management interface 295described 295Management IP Address parameter 744management over wireless 417described 417Master Controller Configuration page 685Master Controller Mode parameter 685Max HTTP Message Size parameter 72Max RF Bandwidth parameter 141, 143Max-Login Ignore Identity Response parameter 402maximum local database entries 383configuring using the GUI 383Maximum Local Database Entries parameter 383Maximum Number of Sessions parameter 72MCS data rates 83Member MAC Address parameter 940memory 12types 12memory leaks, monitoring 263Message Authentication Code Key (MACK) parameter 356message logs 247, 250, 251, 254configuring 247using the GUI 247viewing 250, 251, 254using the CLI 254using the GUI 250, 251Message Logs page 250Message parameter for web authentication 219Metrics Collection parameter 142MFP Client Protection parameter 435MIC 575Min Failed Client Count per AP parameter 829Minimum RSSI parameter 117MMH MIC 576, 577configuring 576, 577mobility 931overview 931Mobility Anchor Create button 947Mobility Anchors option 947mobility anchors. See auto-anchor mobility 945mobility groups 839, 935, 937difference from RF groups 839illustrated 935messaging among 937mobility ping tests, running 955MODE access point button 725Mode parameter 117, 856monitor intervals, configuring using the GUI 831Monitoring 881mpings 956multicast client table, viewing 110Multicast Groups page 109multicast mode 105, 107, 108described 105, 107guidelines 108Multicast Optimization 335Multicast page 108Multicast VLAN 335using the GUI 335multiple country codes 783configuring 783using the CLI 783Cisco Wireless LAN Controller Configuration Guide, Release 7.4       OL-28744-01 IN-9Index
multiple country codes (continued)configuring (continued)using the GUI 783NNAC in-band mode 644NAC out-of-band integration 643, 645diagram 645guidelines 643NAC out-of-band support 646, 647configuring for a specific access point group 646, 647using the CLI 647using the GUI 646NAC State parameter 625, 646NAT address 296, 297, 311, 312for dynamic interface 311, 312for management interface 296, 297NAT devices in mobility groups 937Native VLAN ID parameter 903Neighbor Discovery Packet 837Neighbor Packet Frequency parameter 831Netbios Name Servers parameter 538Netmask parameter 538Network Mobility Services Protocol (NMSP) 168Network parameter 538NTP server 43configuring to obtain time and date 43Number of Attempts to LSC parameter 711Number of Hits parameter 428OOfficeExtend Access Point Home page 748OfficeExtend access points 733, 734, 742, 743, 745, 749and NAT 734configuring 743, 745, 749a personal SSID 749using the GUI 743, 745described 733firewall requirements 742supported access point models 734typical setup 733viewing statistics 749OfficeExtend Access Points 284LEDs 284positioning 284OfficeExtend AP parameter 745online help, using 30operating system 6security 6operating system (continued)software 6Order Used for Authentication parameter 357, 379Over-ride Global Credentials parameter 699, 702, 703, 745Override Global Config parameter 229, 235Override Interface ACL parameter 429Overview of CleanAir 863PP2P Blocking parameter 552packet capture files 260, 261, 262, 263described 260sample output in Wireshark 261uploading 262, 263using the CLI 262, 263Params parameter 711Passive clients 649password guidelines 702Password parameter 195, 386, 698, 702for access point authentication 702for access points 698for local net users 386for PACs 195passwords 247viewing in clear text 247PEAP parameter 402peer-to-peer blocking 551described 551Personal SSID parameter 749Physical Mode parameter 315Physical Status parameter 315ping link test 791ping tests 955PMK cache lifetime timer 570PMKID caching 570PoE Status parameter 803Pool End Address parameter 538Pool Start Address parameter 538Port Number parameter 235, 315, 356, 379, 394for controller 315for LDAP server 394for RADIUS server 356for TACACS+ server 379for wired guest access 235Port parameter for IDS 482ports 315configuring 315Ports page 315Power Injector Selection parameter 803Power Injector State parameter 803Power Neighbor Count parameter 824   Cisco Wireless LAN Controller Configuration Guide, Release 7.4IN-10 OL-28744-01  Index
Power over Ethernet (PoE) 11, 803, 804configuring 803, 804using the CLI 804using the GUI 803, 804described 11Power Over Ethernet (PoE) parameter 316Power Threshold parameter 824preauthentication access control list (ACL) 225, 431, 899applying to a WLAN 431using the CLI 431for external web server 225, 899Preauthentication ACL parameter 430, 639Predownloading an image 180Primary Controller parameters 761Primary RADIUS Server parameter 918Priority Order > Local-Auth page 401Priority Order > Management User page 357, 379Privacy Protocol parameter 210proactive key caching (PKC), with mobility 937probe requests, described 787product authorization key (PAK) 56, 57obtaining for license upgrade 56registering 57Profile Name parameter 235, 524, 618protected access credentials (PACs) 195, 196, 197, 401, 919overview 195uploading 195, 196, 197using the CLI 196, 197using the GUI 195using with local EAP 401, 919Protection Type parameter 435, 844Protocol parameter 427, 911Protocol Type parameter 125PSK 568described 568PSK Format parameter 569QQBSS 592QoS 123, 587levels 123, 587QoS profiles 124, 125, 126configuring 124, 125, 126using the CLI 125, 126using the GUI 124, 125QoS roles 126, 128configuring 126, 128using the CLI 128using the GUI 126, 128Quality of Service (QoS) parameter 588Quarantine parameter 311, 646for dynamic interface 311NAC out-of-band integration 646quarantined VLAN 296, 311, 646, 895, 900configuring 296, 311using 900with FlexConnect 895with NAC out-of-band integration 646Query Interval parameter 482Rradio core dumps 721, 722described 721uploading 722using the GUI 722radio measurement requests 855, 856, 857configuring 856, 857on the CLI 857on the GUI 856overview 855viewing status using the CLI 857radio resource management (RRM) 821, 823, 826, 828, 829, 831, 836, 841, 843, 847, 848, 852, 855CCX features. See CCX radio management 855configuring 831monitor intervals using the GUI 831coverage hole detection 821, 829configuring per controller using the GUI 829described 821debugging 836disabling dynamic channel and power assignment 852using the CLI 852overriding RRM 847specifying channels 826, 828statically assigning channel and transmit power settings 848using the GUI 848update interval 841, 843Wireless > 802.11a/n (or 802.11b/g/n) > RRM > TPCparameter 823radio resource management (RRM) settings 835viewing using the CLI 835radio resource monitoring 818RADIUS 352, 353, 358, 359, 360, 916KEK parameter 359MACK parameter 359configuring on ACS 352, 353FIPS standard 358server fallback behavior 360using FlexConnect 916RADIUS authentication attributes 361RADIUS authentication attributes, Airespace 364Cisco Wireless LAN Controller Configuration Guide, Release 7.4       OL-28744-01 IN-11Index
rc4-preference, configuring for web administration 32Re-sync button 483Redirect URL After Login parameter 219Refresh-time Interval parameter 159Regenerate Certificate button 213Rehost Ticket File Name parameter 68rehosting a license. See licenses 67Remote Authentication Dial-In User Service. See RADIUS 351Request Max Retries parameter 402Request Timeout parameter 402Reserved Roaming Bandwidth parameter 141Reset Link Latency button 796Reset Personal SSID parameter 744resetting the controller 204RF Channel Assignment parameter 852RF group leader 840described 840RF group name 841described 841RF groups 839, 840, 841, 842, 843cascading 840configuring 842using the GUI 842overview 839, 841pinning 840viewing status 842, 843using the CLI 843using the GUI 842, 843RF-Network Name parameter 842RFID tags 167, 169tracking 169debugging using the CLI 169described 167RFID tracking on access points, optimizing 786using the GUI 786RLDP. See Rogue Location Discovery Protocol (RLDP) 454roam reason report 117roaming and real-time diagnostics 271, 272described 271logs 271, 272described 271viewing 272rogue access points 457, 458, 844alarm 844automatically containing 457, 458using the CLI 458using the GUI 457rogue detection 457, 746and OfficeExtend access points 746Rogue Detection parameter 456, 744Rogue Location Discovery Protocol parameter 456Rogue Policies page 456rogue states 463Role Name parameter 127Role of the Controller 864Role parameter 386RRM. See radio resource management (RRM) 817RSNA logs 271configuring 271described 271SSave and Reboot button 194Save Licenses button 59saving configuration settings 202Scan Threshold parameter 118Scope Name parameter 538SE-Connect 885Search AP window 692, 696, 719Search WLANs window 526, 687Secondary Controller parameters 761Secondary RADIUS Server parameter 918security 349overview 349Select APs from Current Controller parameter 918self-signed certificate (SSC) 709used to authorize access points 709Sequence parameter 426, 910serial number for controller, finding 69serial number of controller, finding 68Server Address parameter 482Server Index (Priority) parameter 355, 378, 394Server IP Address parameter 280, 355, 378, 394for LDAP server 394for RADIUS server 355for TACACS+ server 378for wireless sniffer 280Server Key parameter 403, 919Server Status parameter 356, 379Server Timeout parameter 356, 379, 395service port 291service-port interface 297, 306, 307configuring 297, 306using the GUI 297, 306described 307Set Priority button 63Set to Factory Default button 831Severity Level Filtering parameter 248Shared Secret Format parameter 355, 378Shared Secret parameter 355, 378Short Preamble Enabled parameter 409shunned clients 481described 481Signature Events Summary page 492Sniff parameter 280   Cisco Wireless LAN Controller Configuration Guide, Release 7.4IN-12 OL-28744-01  Index
sniffing. See wireless sniffing 279SNMP engine Id 94SNMP v1 / v2c Community page 95SNMP v3 users 210changing default values using the GUI 210SNMP V3 Users page 210SNMP, configuring 94software, upgrading 173, 176, 178guidelines 173using the CLI 178using the GUI 176Source parameter for ACLs 427, 911SpectraLink NetLink phones 409overview 409Spectrum Expert 885configuring using GUI 885Splash Page Web Redirect parameter 639SSH 49, 50, 51, 281, 744, 746and OfficeExtend access points 744, 746configuring 49, 50using the CLI 49, 50troubleshooting access points 51, 281using the GUI 51, 281SSH parameter 51, 282SSID 517, 523, 524configuring 524using the CLI 524using the GUI 524described 517, 523SSL certificate 33, 34, 35loading 33, 34, 35using the CLI 35using the GUI 33, 34SSL Protocol 31SSLv2 for web authentication, disabling 218SSLv2, configuring for web administration 32State parameter 482, 492stateful DHCPv6 IP addressing 607static IP address 726configuring 726using the GUI 726Static IP address 726described 726Static IP parameter 726Status parameter 95, 235, 524, 538, 618for DHCP scopes 538for guest LANs 235for SNMP community 95for WLANs 524, 618Summary page 49Switch IP Address (Anchor) parameter 947SX/LC/T small form-factor plug-in (SFP) modules 290symmetric mobility tunneling 953, 954illustrated 953symmetric mobility tunneling (continued)overview 953verifying status 954using the CLI 954Symmetric Mobility Tunneling Mode parameter 954syslog 271, 272, 273described 271logs 272, 273Syslog Configuration page 248Syslog Facility parameter 249syslog server 248removing from controller 248severity level filtering 248Syslog Server IP Address parameter 248system logging 247configuring 247using the GUI 247system logs, viewing using the CLI 254System Messages 242System Resource Information page 246system resources 245, 246viewing using the CLI 246viewing using the GUI 245TTACACS+ 373, 374, 377, 379accounting 374authentication 373authorization 373configuring 379using the GUI 379described 373roles 377TACACS+ (Authentication, Authorization, or Accounting) Servers> New page 378TACACS+ (Authentication, Authorization, or Accounting) Serverspage 378TACACS+ Administration .csv page (on CiscoSecure ACS) 381, 382Telnet 51, 281, 282troubleshooting access points 51, 281, 282using the CLI 51, 282using the GUI 51, 281, 282Telnet parameter 51, 282Telnet sessions 48, 49configuring 48, 49using the GUI 48, 49Telnet-SSH Configuration page 48Tertiary Controller parameters 761text2pcap sample output 278Time to Live for the PAC parameter 403, 919Cisco Wireless LAN Controller Configuration Guide, Release 7.4       OL-28744-01 IN-13Index
time zone 45, 46configuring using the CLI 46configuring using the GUI 45time-length-values (TLVs), supported for CDP 157, 158time, configuring 43using the NTP server 43timestamps, enabling or disabling in log and debug messages 253, 254traffic specifications (TSPEC) request 138examples 138traffic stream metrics (TSM) 139, 145, 146, 148described 139viewing statistics 145, 146, 148using the CLI 146, 148using the GUI 145Transfer Mode parameter 177, 182, 184, 191, 193, 195, 198, 199, 226, 262downloading a CA certificate 193downloading a configuration file 199downloading a customized web authentication login page 226downloading a device certificate 191upgrading controller software 177, 182, 184uploading a configuration file 198uploading a PAC 195uploading packet capture files 262Transition Time parameter 118transmit power 849statically assigning using the CLI 849statically assigning using the GUI 849transmit power levels 849transmit power threshold, decreasing 832trap logs 743for OfficeExtend access points 743Trap Logs page 596troubleshooting 246, 264, 717, 721access point join process 717, 721CCXv5 clients 264problems 246Troubleshooting OEAPs 284tunnel attributes and identity networking 447Tx Power Level Assignment parameter 852Type parameter 235, 523, 618UU-APSD 139, 145, 146described 139viewing status 145, 146using the CLI 146using the GUI 145UDP port 955UDP, use in RADIUS 351unicast mode 105unique device identifier (UDI) 789, 790described 789retrieving 789, 790using the CLI 790using the GUI 789, 790Upload button 196, 256, 262, 490Upload CSV File parameter 918Upload File from Controller page 195, 198, 262, 722URL to Send the Notifications parameter 72USB console port, using on a 5500 series controller 317, 318Use AES Key Wrap parameter 355User Access Mode parameter 206User Attribute parameter 395User Base DN parameter 394User Credentials parameter 395User Name parameter 386User Object Type parameter 395User parameter 195User Profile Name parameter 210Username parameter 698, 702, 703Using CLI to monitor the Air quality 881Using GUI to monitor air quality 881using the GUI 428VValidate Rogue Clients Against AAA parameter 456Validity parameter 195VCI strings 716Verify Certificate CN Identity parameter 403virtual interface 305described 305VLAN ID parameter 646, 903VLAN Identifier parameter 300, 311for AP-manager interface 300for dynamic interface 311VLAN Select 327VLANs 294, 309described 309guidelines 294Voice RSSI parameter 829voice settings 142configuring 142using the GUI 142voice-over-IP (VoIP) telephone roaming 116VoIP calls, error codes 599VoIP snooping 595described 595VoIP Snooping and Reporting parameter 596VPN Gateway Address parameter 580   Cisco Wireless LAN Controller Configuration Guide, Release 7.4IN-14 OL-28744-01  Index

Navigation menu