Cisco Systems 102075 Cisco Aironet 802.11n Dual Band Access Points User Manual Cisco Wireless LAN Controller Configuration Guide 7

Cisco Systems Inc Cisco Aironet 802.11n Dual Band Access Points Cisco Wireless LAN Controller Configuration Guide 7

UserManual.wiki >

Cisco Systems >

102075 User Manual >

Cisco Wireless LAN Controller Configuration Guide_7 HTML Version

Cisco Wireless LAN Controller Configuration Guide_7

11-27

Cisco Wireless LAN Controller Configuration Guide

OL-21524-02

Chapter 11 Managing User Accounts

Configuring Wired Guest Access

Wired guest access ports initially terminate on a Layer 2 access switch or switch port configured with

VLAN interfaces for wired guest access traffic. The wired guest traffic is then trunked from the access

switch to a controller. This controller is configured with an interface that is mapped to a wired guest

access VLAN on the access switch. See Figure 11-16.

Figure 11-16 Wired Guest Access Example with One Controller

If two controllers are being used, the foreign controller, which receives the wired guest traffic from the

access switch, forwards it to the anchor controller. A bidirectional EoIP tunnel is established between

the foreign and anchor controllers to handle this traffic. See Figure 11-17.

232048

Internet

VLAN ID:

236

guest LAN:

egress interface,

guest-ds

ingress interface,

sidkrish-intf

Controller

(foreign)

Controller

(anchor)

SSID: internal

SSID: guest

Wireless

guest

client

Access

switch

Conference

room

Guest

office

Wired guest access portsWired guest access ports

11-28

Cisco Wireless LAN Controller Configuration Guide

OL-21524-02

Chapter 11 Managing User Accounts

Configuring Wired Guest Access

Figure 11-17 Wired Guest Access Example with Two Controllers

Note Although wired guest access is managed by anchor and foreign anchors when two controllers are

deployed, mobility is not supported for wired guest access clients. In this case, DHCP and web

authentication for the client are handled by the anchor controller.

Note You can specify the amount of bandwidth allocated to a wired guest user in the network by configuring

a QoS role and a bandwidth contract. For details on configuring these features. See the “Configuring

Quality of Service” section on page 4-68.

Configuration Overview

To configure wired guest access on a wireless network, you will perform the following:

1. Configure a dynamic interface (VLAN) for wired guest user access

2. Create a wired LAN for guest user access

3. Configure the controller

4. Configure the anchor controller (if terminating traffic on another controller)

5. Configure security for the guest LAN

6. Verify the configuration

Wired Guest Access Guidelines

Follow these guidelines before using wired guest access on your network:

• Wired guest access is supported only on the following controllers: 5500 and 4400 series controllers,

the Cisco WiSM, and the Catalyst 3750G Integrated Wireless LAN Controller Switch.

• Wired guest access interfaces must be tagged.

232347

Internet

SSID: Internal

SSID: GUEST

Wired

guest

client

Access

switch

Wireless

guest client

Wired guest ports

Anchor controller,

mobility anchor,

export-anchor

Foreign controller,

export-foreign

11-29

Cisco Wireless LAN Controller Configuration Guide

OL-21524-02

Chapter 11 Managing User Accounts

Configuring Wired Guest Access

• Wired guest access ports must be in the same Layer 2 network as the foreign controller.

• Up to five wired guest access LANs can be configured on a controller.

• Layer 3 web authentication and web passthrough are supported for wired guest access clients. Layer

2 security is not supported.

• Do not attempt to trunk a guest VLAN on the Catalyst 3750G Integrated Wireless LAN Controller

Switch to multiple controllers. Redundancy cannot be achieved by doing this action.

Using the GUI to Configure Wired Guest Access

To configure wired guest user access on your network using the controller GUI, follow these steps:

Step 1 To create a dynamic interface for wired guest user access, choose Controller > Interfaces. The

Interfaces page appears.

Step 2 Click New to open the Interfaces > New page.

Step 3 Enter a name and VLAN ID for the new interface.

Step 4 Click Apply to commit your changes.

Step 5 In the Port Number text box, enter a valid port number. You can enter a number between 0 and 25

(inclusive).

Step 6 Select the Guest LAN check box.

Step 7 Click Apply to commit your changes.

Step 8 To create a wired LAN for guest user access, choose WLANs.

Step 9 On the WLANs page, choose Create New from the drop-down list and click Go. The WLANs > New

page appears (see Figure 11-18).

Figure 11-18 WLANs > New Page

Step 10 From the Type drop-down list, choose Guest LAN.

Step 11 In the Profile Name text box, enter a name that identifies the guest LAN. Do not use any spaces.

Step 12 From the WLAN ID drop-down list, choose the ID number for this guest LAN.

Note You can create up to five guest LANs, so the WLAN ID options are 1 through 5 (inclusive).

Step 13 Click Apply to commit your changes. The WLANs > Edit page appears (see Figure 11-19).

11-30

Cisco Wireless LAN Controller Configuration Guide

OL-21524-02

Chapter 11 Managing User Accounts

Configuring Wired Guest Access

Figure 11-19 WLANs > Edit Page

Step 14 Select the Enabled check box for the Status parameter.

Step 15 Web authentication (Web-Auth) is the default security policy. If you want to change this to web

passthrough, choose the Security tab after completing Step 16 and Step 17.

Step 16 From the Ingress Interface drop-down list, choose the VLAN that you created in Step 3. This VLAN

provides a path between the wired guest client and the controller by way of the Layer 2 access switch.

Step 17 From the Egress Interface drop-down list, choose the name of the interface. This WLAN provides a path

out of the controller for wired guest client traffic.

Step 18 If you want to change the authentication method (for example, from web authentication to web

passthrough), choose Security > Layer 3. The WLANs > Edit (Security > Layer 3) page appears (see

Figure 11-20).

Figure 11-20 WLANs > Edit (Security > Layer 3) Page

Step 19 From the Layer 3 Security drop-down list, choose one of the following:

• None—Layer 3 security is disabled.

• Web Authentication—Causes users to be prompted for a username and password when connecting

to the wireless network. This is the default value.

• Web Passthrough—Allows users to access the network without entering a username and password.

Note There should not be a Layer 3 gateway on the guest wired VLAN, as this would bypass the web

authentication done through the controller.

11-31

Cisco Wireless LAN Controller Configuration Guide

OL-21524-02

Chapter 11 Managing User Accounts

Configuring Wired Guest Access

Step 20 If you choose the Web Passthrough option, an Email Input check box appears. Select this check box if

you want users to be prompted for their e-mail address when attempting to connect to the network.

Step 21 To override the global authentication configuration set on the Web Login page, select the Override

Global Config check box.

Step 22 When the Web Auth Type drop-down list appears, choose one of the following options to define the web

authentication pages for wired guest users:

• Internal—Displays the default web login page for the controller. This is the default value.

• Customized—Displays custom web login, login failure, and logout pages. If you choose this option,

three separate drop-down lists appear for login, login failure, and logout page selection. You do not

need to define a customized page for all three options. Choose None from the appropriate drop-down

list if you do not want to display a customized page for that option.

Note These optional login, login failure, and logout pages are downloaded to the controller as

webauth.tar files.

• External—Redirects users to an external server for authentication. If you choose this option, you

must also enter the URL of the external server in the URL text box.

You can choose specific RADIUS or LDAP servers to provide external authentication on the

WLANs > Edit (Security > AAA Servers) page. Additionally, you can define the priority in which

the servers provide authentication.

Step 23 If you chose External as the web authentication type in Step 22, choose AAA Servers and choose up to

three RADIUS and LDAP servers using the drop-down lists.

Note The RADIUS and LDAP external servers must already be configured in order to be selectable

options on the WLANs > Edit (Security > AAA Servers) page. You can configure these servers

on the RADIUS Authentication Servers page and LDAP Servers page.

Step 24 To establish the priority in which the servers are contacted to perform web authentication as follows:

Note The default order is local, RADIUS, LDAP.

a. Highlight the server type (local, RADIUS, or LDAP) that you want to be contacted first in the box

next to the Up and Down buttons.

b. Click Up and Down until the desired server type is at the top of the box.

c. Click the < arrow to move the server type to the priority box on the left.

d. Repeat these steps to assign priority to the other servers.

Step 25 Click Apply to commit your changes.

Step 26 Click Save Configuration to save your changes.

Step 27 Repeat this process if a second (anchor) controller is being used in the network.

11-32

Cisco Wireless LAN Controller Configuration Guide

OL-21524-02

Chapter 11 Managing User Accounts

Configuring Wired Guest Access

Using the CLI to Configure Wired Guest Access

To configure wired guest user access on your network using the controller CLI, follow these steps:

Step 1 Create a dynamic interface (VLAN) for wired guest user access by entering this command:

config interface create interface_name vlan_id

Step 2 If link aggregation trunk is not configured, enter this command to map a physical port to the interface:

config interface port interface_name primary_port {secondary_port}

Step 3 Enable or disable the guest LAN VLAN by entering this command:

config interface guest-lan interface_name {enable | disable}

This VLAN is later associated with the ingress interface created in Step 5.

Step 4 Create a wired LAN for wired client traffic and associate it to an interface by entering this command:

config guest-lan create guest_lan_id interface_name

The guest LAN ID must be a value between 1 and 5 (inclusive).

Note To delete a wired guest LAN, enter the config guest-lan delete guest_lan_id command.

Step 5 Configure the wired guest VLAN’s ingress interface, which provides a path between the wired guest

client and the controller by way of the Layer 2 access switch by entering this command:

config guest-lan ingress-interface guest_lan_id interface_name

Step 6 Configure an egress interface to transmit wired guest traffic out of the controller by entering this

command:

config guest-lan interface guest_lan_id interface_name

Note If the wired guest traffic is terminating on another controller, repeat Step 4 and Step 6 for the

terminating (anchor) controller and Step 1 through Step 5 for the originating (foreign)

controller. Additionally, configure the config mobility group anchor add {guest-lan

guest_lan_id | wlan wlan_id} IP_address command for both controllers.

Step 7 Configure the security policy for the wired guest LAN by entering this command:

config guest-lan security {web-auth enable guest_lan_id | web-passthrough enable guest_lan_id}

Note Web authentication is the default setting.

Step 8 Enable or disable a wired guest LAN by entering this command:

config guest-lan {enable | disable} guest_lan_id

Step 9 If you want wired guest users to log into a customized web login, login failure, or logout page, enter

these commands to specify the filename of the web authentication page and the guest LAN for which it

should display:

• config guest-lan custom-web login-page page_name guest_lan_id—Defines a web login page.

• config guest-lan custom-web loginfailure-page page_name guest_lan_id—Defines a web login

failure page.

11-33

Cisco Wireless LAN Controller Configuration Guide

OL-21524-02

Chapter 11 Managing User Accounts

Configuring Wired Guest Access

Note To use the controller’s default login failure page, enter the config guest-lan custom-web

loginfailure-page none guest_lan_id command.

• config guest-lan custom-web logout-page page_name guest_lan_id—Defines a web logout page.

Note To use the controller’s default logout page, enter the config guest-lan custom-web

logout-page none guest_lan_id command.

Step 10 If you want wired guest users to be redirected to an external server before accessing the web login page,

enter this command to specify the URL of the external server:

config guest-lan custom-web ext-webauth-url ext_web_url guest_lan_id

Step 11 If you want to define the order in which local (controller) or external (RADIUS, LDAP) web

authentication servers are contacted, enter this command:

config wlan security web-auth server-precedence wlan_id {local | ldap | radius} {local | ldap |

radius} {local | ldap | radius}

The default order of server web authentication is local, RADIUS, LDAP.

Note All external servers must be preconfigured on the controller. You can configure them on the

RADIUS Authentication Servers page or the LDAP Servers page.

Step 12 Define the web login page for wired guest users by entering this command:

config guest-lan custom-web webauth-type {internal | customized | external} guest_lan_id

where

• internal displays the default web login page for the controller. This is the default value.

• customized displays the custom web pages (login, login failure, or logout) that were configured in

Step 9.

• external redirects users to the URL that was configured in Step 10.

Step 13 Use a guest-LAN specific custom web configuration rather than a global custom web configuration by

entering this command:

config guest-lan custom-web global disable guest_lan_id

Note If you enter the config guest-lan custom-web global enable guest_lan_id command, the custom

web authentication configuration at the global level is used.

Step 14 Save your changes by entering this command:

save config

Note Information on the configured web authentication appears in both the show run-config and

show running-config commands.

Step 15 Display the customized web authentication settings for a specific guest LAN by entering this command:

show custom-web {all | guest-lan guest_lan_id}

11-34

Cisco Wireless LAN Controller Configuration Guide

OL-21524-02

Chapter 11 Managing User Accounts

Configuring Wired Guest Access

Note If internal web authentication is configured, the Web Authentication Type displays as internal

rather than external (controller level) or customized (WLAN profile level).

Information similar to the following appears for the show custom-web all command:

Radius Authentication Method..................... PAP

Cisco Logo....................................... Enabled

CustomLogo....................................... None

Custom Title..................................... None

Custom Message................................... None

Custom Redirect URL.............................. None

Web Authentication Type............... External

External Web Authentication URL............ http:\\9.43.0.100\login.html

External Web Server list

Index IP Address

----- ---------------

1 9.43.0.100

2 0.0.0.0

3 0.0.0.0

4 0.0.0.0

5 0.0.0.0

...

20 0.0.0.0

Configuration Per Profile:

WLAN ID: 1

WLAN Status................................... Enabled

Web Security Policy........................... Web Based Authentication

Global Status................................. Disabled

WebAuth Type.................................. Customized

Loginfailure page name....................... loginfailure1.html

Logout page name............................. logout1.html

WLAN ID: 2

WLAN Status................................... Enabled

Web Security Policy........................... Web Based Authentication

Global Status................................. Disabled

WebAuth Type.................................. Internal

Loginfailure page name........................ None

Logout page name.............................. None

WLAN ID: 3

WLAN Status................................... Enabled

Web Security Policy........................... Web Based Authentication

Global Status................................. Disabled

WebAuth Type.................................. Customized

Loginfailure page name........................ LF2.html

Logout page name.............................. LG2.html

Information similar to the following appears for the show custom-web guest-lan guest_lan_id

command:

Guest LAN ID: 1

Guest LAN Status.............................. Disabled

Web Security Policy........................... Web Based Authentication

Global Status................................. Enabled

WebAuth Type.................................. Internal

11-35

Cisco Wireless LAN Controller Configuration Guide

OL-21524-02

Chapter 11 Managing User Accounts

Configuring Wired Guest Access

Loginfailure page name........................ None

Logout page name.............................. None

Step 16 Display a summary of the local interfaces by entering this command:

show interface summary

Information similar to the following appears:

Interface Name Port Vlan Id IP Address Type Ap Mgr Guest

-------------------------------- ---- -------- --------------- ------- ------ -----

ap-manager 1 untagged 1.100.163.25 Static Yes No

management 1 untagged 1.100.163.24 Static No No

service-port N/A N/A 172.19.35.31 Static No No

virtual N/A N/A 1.1.1.1 Static No No

wired 1 20 10.20.20.8 Dynamic No No

wired-guest 1 236 10.20.236.50 Dynamic No Yes

Note The interface name of the wired guest LAN in this example is wired-guest and its VLAN ID is

236.Display detailed interface information by entering this command:

show interface detailed interface_name

Information similar to the following appears:

Interface Name................................... wired-guest

MAC Address...................................... 00:1a:6d:dd:1e:40

IP Address....................................... 0.0.0.0

DHCP Option 82................................... Disabled

Virtual DNS Host Name............................ Disabled

AP Manager....................................... No

Guest Interface.................................. No

Step 17 Display the configuration of a specific wired guest LAN by entering this command:

show guest-lan guest_lan_id

Information similar to the following appears:

Guest LAN Identifier............................. 1

Profile Name..................................... guestlan

Network Name (SSID).............................. guestlan

Status........................................... Enabled

AAA Policy Override.............................. Disabled

Number of Active Clients......................... 1

Exclusionlist Timeout............................ 60 seconds

Session Timeout.................................. Infinity

Interface........................................ wired

Ingress Interface................................ wired-guest

WLAN ACL......................................... unconfigured

DHCP Server...................................... 10.20.236.90

DHCP Address Assignment Required................. Disabled

Quality of Service............................... Silver (best effort)

Security

Web Based Authentication...................... Enabled

ACL........................................... Unconfigured

Web-Passthrough............................... Disabled

Conditional Web Redirect...................... Disabled

11-36

Cisco Wireless LAN Controller Configuration Guide

OL-21524-02

Chapter 11 Managing User Accounts

Configuring Wired Guest Access

Auto Anchor................................... Disabled

Mobility Anchor List

GLAN ID IP Address Status

------- --------------- ------

Note Enter the show guest-lan summary command to see all wired guest LANs configured on the

controller.

Step 18 Display the active wired guest LAN clients by entering this command:

show client summary guest-lan

Information similar to the following appears:

Number of Clients................................ 1

MAC Address AP Name Status WLAN Auth Protocol Port Wired

------------------- ------- ----------- ----- ----- --------- ----- ------

00:16:36:40:ac:58 N/A Associated 1 No 802.3 1 Yes

Step 19 Display detailed information for a specific client by entering this command:

show client detail client_mac

Information similar to the following appears:

Client MAC Address............................... 00:40:96:b2:a3:44

Client Username ................................. N/A

AP MAC Address................................... 00:18:74:c7:c0:90

Client State..................................... Associated

Wireless LAN Id.................................. 1

BSSID............................................ 00:18:74:c7:c0:9f

Channel.......................................... 56

IP Address....................................... 192.168.10.28

Association Id................................... 1

Authentication Algorithm......................... Open System

Reason Code...................................... 0

Status Code...................................... 0

Session Timeout.................................. 0

Client CCX version............................... 5

Client E2E version............................... No E2E support

Diagnostics Capability........................... Supported

S69 Capability................................... Supported

Mirroring........................................ Disabled

QoS Level........................................ Silver

...

CHAPTER

12-1

Cisco Wireless LAN Controller Configuration Guide

OL-21524-02

Configuring Cisco CleanAir

This chapter describes how to configure Cisco CleanAir functionality on the controller and lightweight

access points. It contains these sections:

• Overview of Cisco CleanAir, page 12-1

• Configuring Cisco CleanAir on the Controller, page 12-5

• Configuring Cisco CleanAir on an Access Point, page 12-11

• Monitoring the Air Quality of Radio Bands, page 12-18

• Configuring a Spectrum Expert Connection, page 12-23

Overview of Cisco CleanAir

Wireless LAN systems operate in unlicensed 2.4- and 5-GHz industrial, scientific, and medical (ISM)

bands. Many devices, such as microwave ovens, cordless phones, and Bluetooth devices also operate in

these bands and can negatively affect Wi-Fi operations. Some of the most advanced WLAN services,

such as voice over wireless and IEEE 802.11n radio communications, could be significantly impaired by

the interference caused by other legal users of the ISM bands. The integration of Cisco CleanAir

functionality into the Cisco Unified Wireless Network addresses this problem of radio frequency (RF)

interference. The Cisco CleanAir feature, available in controller software release 7.0.98.0, enables you

to identify and track non-Wi-Fi sources of interference, adjust your network configuration for optimal

performance, identify threats from malicious devices, and allow your WLAN to coexist with other

wireless devices.

A Cisco CleanAir system consists of CleanAir-enabled access points, controllers, and WCS. Currently,

only Cisco Aironet 3500 series access points can be configured for Cisco CleanAir. These access points

collect information about all devices that operate in the ISM bands, identify and evaluate the information

as a potential interference source, and forward it to the controller. The controller controls the access

points, collects spectrum data, and forwards information to WCS or a Cisco mobility services engine

(MSE) upon request. The controller provides a local user interface to configure basic CleanAir features

and display basic spectrum information. WCS provides an advanced user interface for configuring Cisco

CleanAir features, displaying information, and keeping records. The MSE is optional for the basic

feature set but required for advanced features such as tracking the location of non-Wi-Fi interference

devices.

Role of the Controller

The controller performs these tasks in a Cisco CleanAir system:

12-2

Cisco Wireless LAN Controller Configuration Guide

OL-21524-02

Chapter 12 Configuring Cisco CleanAir

Overview of Cisco CleanAir

• 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

• Collects and processes interference device reports (IDRs) from the access point and stores them in

the interference device database

• Forwards spectrum data to WCS and the MSE

Benefits

Cisco CleanAir is a spectrum intelligence solution designed to proactively manage the challenges of a

shared wireless spectrum. It allows you to see all of the users of the shared spectrum (both native devices

and foreign interferers). It also enables you or your network to act upon this information. For example,

you could manually remove the interfering device, or the system could automatically change the channel

away from the interference.

For every device operating in the unlicensed band, Cisco CleanAir tells you what it is, where it is, how

it is impacting your wireless network, and what actions you or your network should take. It simplifies

RF so that you do not have to be an RF expert.

Types of Interferences

Cisco CleanAir can detect interference, report on the location and severity of the interference, and

recommend different mitigation strategies. Two such mitigation strategies are persistent device

avoidance and spectrum event-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

to avoid 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 disrupts

clients 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

location and potential impact to a WLAN. Having this information allows you to consider the noise

within the context of the network and make intelligent and, where possible, proactive decisions. For

CleanAir, two types of interference events are common:

• Persistent interference

• Spontaneous interference

Persistent interference events are created by devices that are stationary in nature and have intermittent

but largely repeatable patterns of interference. For example, consider the case of a microwave oven

located in a break room. Such a device might be active for only 1 or 2 minutes at a time. When operating,

however, it can be disruptive to the performance of the wireless network and associated clients. Using

Cisco CleanAir, you can positively identify the device as a microwave oven rather than indiscriminate

12-3

Cisco Wireless LAN Controller Configuration Guide

OL-21524-02

Chapter 12 Configuring Cisco CleanAir

Overview of Cisco CleanAir

noise. You can also determine exactly which part of the band is affected by the device, and because you

can locate it, you can understand which access points are most severely affected. You can then use this

information to direct RRM in selecting a channel plan that avoids this source of interference for the

access points within its range. Because this interference is not active for a large portion of the day,

existing RF management applications might attempt to again change the channels of the affected access

points. Persistent device avoidance is unique, however, in that it remains in effect as long as the source

of interference is periodically detected to refresh the persistent status. The Cisco CleanAir system knows

that the microwave oven exists and includes it in all future planning. If you move either the microwave

oven or the surrounding access points, the algorithm updates RRM automatically.

Spontaneous interference is interference that appears suddenly on a network, perhaps jamming a channel

or a range of channels completely. The Cisco CleanAir spectrum event-driven RRM feature allows you

to set a threshold for air quality (AQ) that, if exceeded, triggers an immediate channel change for the

affected access point. Most RF management systems can avoid interference, but this information takes

time to propagate through the system. Cisco CleanAir relies on AQ measurements to continuously

evaluate the spectrum and can trigger a move within 30 seconds. For example, if an access point detects

interference from a video camera, it can recover by changing channels within 30 seconds of the camera

becoming active. Cisco CleanAir also identifies and locates the source of interference so that more

permanent mitigation of the device can be performed at a later time.

Note Spectrum event-driven RRM can be triggered only by Cisco CleanAir-enabled access points in local

mode.

Supported Access Point Modes

Only Cisco CleanAir-enabled access points using the following access point modes can perform Cisco

CleanAir spectrum monitoring:

• Local—In this mode, each Cisco CleanAir-enabled access point radio provides air quality and

interference detection reports for the current operating channel only.

• Hybrid-REAP—When a hybrid-REAP access point is connected to the controller, its Cisco

CleanAir functionality is identical to local mode.

• Monitor—When Cisco CleanAir is enabled in monitor mode, the access point provides air quality

and interference detection reports for all monitored channels.

Note Suppose you have two APs, one in the H-REAP mode and the other in the Monitor mode. Also

suppose that you have created a profile enabling EAP attack against 802.1x auth. The Airmagnet

(AM) tool, which can generate different types of attacks, fails to generate any attack even if you

have provided valid AP MAC and STA MAC addresses. But if the AP MAC and STA MAC

addresses in the AM tool are swapped, that is, the AP MAC address is specified in the STA MAC

field and the STA MAC address is specified in the AP MAC field, then the tool is able to generate

attacks, which the AP in the Monitor mode is also able to detect.

Note The access point does not participate in AQ HeatMap in WCS.

The following options are available:

–

All— All channels

12-4

Cisco Wireless LAN Controller Configuration Guide

OL-21524-02

Chapter 12 Configuring Cisco CleanAir

Overview of Cisco CleanAir

–

DCA—Channel selection governed by the DCA list

–

Country—All channel legal within a regulatory domain

• SE-Connect—This mode enables a user to connect a Spectrum Expert application running on an

external Microsoft Windows XP or Vista PC to a Cisco CleanAir-enabled access point in order to

display and analyze detailed spectrum data. The Spectrum Expert application connects directly to

the access point, bypassing the controller. An access point in SE-Connect mode does not provide

any Wi-Fi, RF, or spectrum data to the controller. In addition to performing spectrum intellegence,

an access point can provide other. See the “Configuring a Spectrum Expert Connection” section on

page 12-23 for instructions on establishing a Spectrum Expert console connection.

Guidelines

Follow these guidelines when using Cisco CleanAir functionality:

• The Cisco 2100 Series Controller and Controller Network Modules support up to 75 device clusters

(unique interference devices detected by a single or multiple radios) and up to 300 device records

(information about an interference device detected by a single radio). The Cisco 4400 Series

Controllers, Cisco WiSM, and Catalyst 3750G Wireless LAN Controller Switch support up to 750

device clusters and up to 3,000 device records. The Cisco 5500 Series Controllers support up to

2,500 device clusters and up to 10,000 device records.

• The amount of power required for processing spectrum data limits the number of monitor-mode

access points that can be used for Cisco CleanAir monitoring. The Cisco CleanAir system supports

up to 6 monitor-mode access points on the Cisco 2100 Series Controller and Controller Network

Modules; up to 25 monitor-mode access points on the Cisco 4400 Series Controllers, the Catalyst

3750G Wireless LAN Controller Switch, and each Cisco WiSM controller; number of supported

monitor mode access points is equal to the maximum number of supported access points on the

Cisco 5500 and Flex 7500 Series Controllers. This limitation affects only Cisco CleanAir

functionality.

• Access points in monitor mode do not transmit Wi-Fi traffic or 802.11 packets. They are excluded

from radio resource management (RRM) planning and are not included in the neighbor access point

list. IDR clustering depends on the controller’s ability to detect neighboring in-network access

points. Correlating interference device detections from multiple access points is limited between

monitor-mode access points.

• Spectrum Expert (SE) Connect functionality is supported for local, hybrid REAP, bridge, and

monitor modes. The access point provides spectrum information to Spectrum Expert only for the

current channel(s). For local, hybrid REAP, 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 continues to send AQ (Air Quality) and IDR (Interference Device Reports) reports

to the controller and perform normal activities according to the current mode. Sniffer and rogue

detections access point modes are incompatible with all types of CleanAir spectrum monitoring.

• Controllers have limitations on the number of monitor mode AP’s that they can support. This is

because, a monitor mode AP saves data for all the channels.

• Do not connect access points in SE connect mode directly to any physical port on the Cisco 2100 or

2500 Series Controller.

12-5

Cisco Wireless LAN Controller Configuration Guide

OL-21524-02

Chapter 12 Configuring Cisco CleanAir

Configuring Cisco CleanAir on the Controller

This section describes how to configure Cisco CleanAir functionality on the 802.11a/n or 802.11b/g/n

network using either the controller GUI or CLI.

Note See the “Configuring Cisco CleanAir on an Access Point” section on page 12-11 to enable or disable

Cisco CleanAir functionality for a specific access point, rather than globally across the network. For

example, you may want to enable Cisco CleanAir globally on the 802.11a/n network but then disable it

for a particular access point on that network.

Using the GUI to Configure Cisco CleanAir on the Controller

To configure Cisco CleanAir functionality on the controller using the controller GUI, follow these steps:

Step 1 Choose Wireless > 802.11a/n or 802.11b/g/n > CleanAir to open the 802.11a (or 802.11b) > CleanAir

page (see Figure 12-1).

Figure 12-1 802.11a > CleanAir Page

Step 2 Select the CleanAir check box to enable Cisco CleanAir functionality on the 802.11a/n or 802.11b/g/n

network, or unselect it to prevent the controller from detecting spectrum interference. The default value

is 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 controller from reporting interferers. The default

value is selected.

12-6

Cisco Wireless LAN Controller Configuration Guide

OL-21524-02

Chapter 12 Configuring Cisco CleanAir

Configuring Cisco CleanAir on the Controller

Step 4 Make sure that any sources of interference that need to be detected and reported by the Cisco CleanAir

system appear in the Interferences to Detect box and any that do not need to be detected appear in the

Interferences to Ignore box. Use the > and < buttons to move interference sources between these two

boxes. By default, all interference sources are detected. The possible sources of interference are as

follows:

• Bluetooth Paging Inquiry—A Bluetooth discovery (802.11b/g/n only)

• Bluetooth Sco Acl—A Bluetooth link (802.11b/g/n only)

• Generic DECT—A digital enhanced cordless communication (DECT)-compatible phone

• Generic TDD—A time division duplex (TDD) transmitter

• Generic Waveform—A continuous transmitter

• Jammer—A jamming device

• Microwave—A microwave oven (802.11b/g/n only)

• Canopy—A canopy device

• Radar—A radar device (802.11a/n only)

• 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)

Note Access points that are associated to the controller send interference reports only for the

interferers that appear in the Interferences to Detect box. This functionality allows you to filter

out interferers that you do not want as well as any that may be flooding the network and causing

performance problems for the controller or WCS. Filtering allows the system to resume normal

performance levels.

Step 5 Configure Cisco CleanAir alarms as follows:

a. Select the Enable AQI (Air Quality Index) Trap check box to enable the triggering of air quality

alarms, or unselect the box to disable this feature. The default value is selected.

b. If you selected the Enable AQI Trap check box in Step a, enter a value between 1 and 100 (inclusive)

in the AQI Alarm Threshold text box to specify the threshold at which you want the air quality alarm

to be triggered. When the air quality falls below the threshold level, the alarm is triggered. A value

of 1 represents the worst air quality, and 100 represents the best. The default value is 35.

c. Select the Enable Interference Type Trap check box to trigger interferer alarms when the

controller detects specified device types, or unselect it to disable this feature. The default value is

selected.

12-7

Cisco Wireless LAN Controller Configuration Guide

OL-21524-02

Chapter 12 Configuring Cisco CleanAir

Configuring Cisco CleanAir on the Controller

d. Make sure that any sources of interference that need to trigger interferer alarms appear in the Trap

on These Types box and any that do not need to trigger interferer alarms appear in the Do Not Trap

on These Types box. Use the > and < buttons to move interference sources between these two boxes.

By default, all interference sources trigger interferer alarms.

For example, if you want the controller to send an alarm when it detects a jamming device, select

the Enable Interference Type Trap check box and move the jamming device to the Trap on These

Types box.

Step 6 Click Apply to commit your changes.

Step 7 Trigger spectrum event-driven radio resource management (RRM) to run when a Cisco

CleanAir-enabled access point detects 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 Sensitivity Threshold 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. The 802.11a (or 802.11b) > RRM > Dynamic Channel Assignment (DCA) page appears

(see Figure 12-2).

Figure 12-2 802.11a > RRM > Dynamic Channel Assignment (DCA) Page

c. Select the EDRRM check box to trigger RRM to run when an access point detects a certain level of

interference, or unselect it to disable this feature. The default value is selected.

d. If you selected the EDRRM check box in Step c, choose Low, Medium, or High from the Sensitivity

Threshold drop-down list to specify the threshold at which you want RRM to be triggered. When

the interference for the access point rises above the threshold level, RRM initiates a local dynamic

channel assignment (DCA) run and changes the channel of the affected access point radio if possible

to improve network performance. Low represents a decreased sensitivity to changes in the

environment while High represents an increased sensitivity.

The EDRRM AQ threshold value for low sensitivity is 35, medium sensitivity is 50, and high

sensitivity is 60.

The default value is Medium.

12-8

Cisco Wireless LAN Controller Configuration Guide

OL-21524-02

Chapter 12 Configuring Cisco CleanAir

Configuring Cisco CleanAir on the Controller

e. Click Apply to commit your changes.

Step 8 Click Save Configuration to save your changes.

Using the CLI to Configure Cisco CleanAir on the Controller

To configure Cisco CleanAir functionality on the controller using the controller CLI, follow these steps:

Step 1 Configure Cisco CleanAir functionality on the 802.11a/n or 802.11b/g/n network by entering this

command:

config {802.11a | 802.11b} CleanAir {enable | disable} all

If you disable this feature, the controller does not receive any spectrum data. The default value is enable.

Step 2 Configure interference detection and specify sources of interference that need to be detected by the Cisco

CleanAir system by entering this command:

config {802.11a | 802.11b} CleanAir device {enable | disable} type

where type is 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 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)

• radar—A radar device (802.11a/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)

12-9

Cisco Wireless LAN Controller Configuration Guide

OL-21524-02

Chapter 12 Configuring Cisco CleanAir

Configuring Cisco CleanAir on the Controller

Note Access points that are associated to the controller send interference reports only for the

interference types specified in this command. This functionality allows you to filter out

interferers that may be flooding the network and causing performance problems for the

controller or WCS. Filtering allows the system to resume normal performance levels.

Step 3 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 enable.

Step 4 Specify the threshold at which you want the air quality alarm to be triggered by entering this command:

config {802.11a | 802.11b} CleanAir alarm air-quality threshold threshold

where threshold is a value between 1 and 100 (inclusive). When the air quality falls below the threshold

level, the alarm is triggered. A value of 1 represents the worst air quality, and 100 represents the best.

The default value is 35.

Step 5 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 6 Specify sources of interference that trigger alarms by entering this command:

config {802.11a | 802.11b} CleanAir alarm device type {enable | disable}

where type is 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 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)

• radar—A radar device (802.11a/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)

12-10

Cisco Wireless LAN Controller Configuration Guide

OL-21524-02

Chapter 12 Configuring Cisco CleanAir

Configuring Cisco CleanAir on the Controller

Step 7 Trigger spectrum event-driven radio resource management (RRM) to run when a Cisco

CleanAir-enabled access point detects a significant level of interference by entering these commands:

• config advanced {802.11a | 802.11b} channel cleanair-event {enable | disable}—Enables or

disables spectrum event-driven RRM. The default value is disabled.

• config advanced {802.11a | 802.11b} channel cleanair-event sensitivity {low | medium |

high}—Specifies the threshold at which you want RRM to be triggered. When the interference level

for the access point rises above the threshold level, RRM initiates a local dynamic channel

assignment (DCA) run and changes the channel of the affected access point radio if possible to

improve network performance. Low represents a decreased sensitivity to changes in the environment

while high represents an increased sensitivity. The default value is medium.

Step 8 Save your changes by entering this command:

save config

Step 9 See the Cisco CleanAir configuration for the 802.11a/n or 802.11b/g/n network by entering this

command:

show {802.11a | 802.11b} cleanair config

Information similar to the following appears:

Clean Air Solution............................... Enabled

Air Quality Settings:

Air Quality Reporting........................ Enabled

Air Quality Reporting Period (min)........... 15

Air Quality Alarms........................... Enabled

Air Quality Alarm Threshold.................. 35

Interference Device Settings:

Interference Device Reporting................ Enabled

Interference Device Types:

TDD Transmitter.......................... Disabled

Jammer................................... Disabled

Continuous Transmitter................... Disabled

DECT-like Phone.......................... Disabled

Video Camera............................. Disabled

WiFi Inverted............................ Disabled

WiFi Invalid Channel..................... Disabled

SuperAG.................................. Disabled

Radar.................................... Disabled

Canopy................................... Disabled

WiMax Mobile............................. Disabled

WiMax Fixed.............................. Disabled

Interference Device Alarms....................... Enabled

Interference Device Types Triggering Alarms:

TDD Transmitter.......................... Disabled

Jammer................................... Enabled

Continuous Transmitter................... Disabled

DECT-like Phone.......................... Disabled

Video Camera............................. Disabled

WiFi Inverted............................ Enabled

WiFi Invalid Channel..................... Enabled

SuperAG.................................. Disabled

Radar.................................... Disabled

Canopy................................... Disabled

WiMax Mobile............................. Disabled

WiMax Fixed.............................. Disabled

Interference Device Merging Type............. normal

Additional Clean Air Settings:

CleanAir Event-driven RRM State............. Enabled

CleanAir Driven RRM Sensitivity............. Medium

12-11

Cisco Wireless LAN Controller Configuration Guide

OL-21524-02

Chapter 12 Configuring Cisco CleanAir

Configuring Cisco CleanAir on an Access Point

CleanAir Persistent Devices state........ Disabled

Step 10 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} channel

Information similar to the following appears:

Automatic Channel Assignment

Channel Assignment Mode........................ AUTO

Channel Update Interval........................ 600 seconds [startup]

Anchor time (Hour of the day).................. 0

Channel Update Contribution.................... SNI

CleanAir Event-driven RRM option.............. Enabled

CleanAir Event-driven RRM sensitivity...... Medium

...

Configuring Cisco CleanAir on an Access Point

This section describes how to configure Cisco CleanAir functionality on an individual access point using

either the controller GUI or CLI.

Note See the “Configuring Cisco CleanAir on the Controller” section on page 12-5 to enable or disable Cisco

CleanAir functionality globally across the 802.11a/n or 802.11b/g/n network rather than for specific

access points.

Using the GUI to Configure Cisco CleanAir on an Access Point

To configure Cisco CleanAir functionality for a specific access point using the controller GUI, follow

these steps:

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) Radios page.

Step 2 Hover your cursor over the blue drop-down arrow for the desired access point and click Configure. The

802.11a/n (or 802.11b/g/n) Cisco APs > Configure page appears (see Figure 12-3).

12-12

Cisco Wireless LAN Controller Configuration Guide

OL-21524-02

Chapter 12 Configuring Cisco CleanAir

Configuring Cisco CleanAir on an Access Point

Figure 12-3 802.11a/n Cisco APs > Configure Page

The CleanAir Capable field shows whether this access point can support CleanAir functionality. If it can,

go to the next step to enable or disable CleanAir for this access point. If the access point cannot support

CleanAir functionality, you cannot enable CleanAir for this access point.

Note Currently, only Cisco Aironet 3500 series access points can be configured for Cisco CleanAir.

Note By default, the Cisco CleanAir functionality is enabled on the radios.

Step 3 Enable Cisco CleanAir functionality for this access point by choosing Enable from the CleanAir Status

drop-down list. To disable CleanAir functionality for this access point, choose Disable. The default

value is Enable. This setting overrides the global CleanAir configuration for this access point.

The Number of Spectrum Expert Connections text box shows the number of Spectrum Expert

applications that are currently connected to the access point radio. Up to three active connections are

possible.

Step 4 Click Apply to commit your changes.

Step 5 Click Save Configuration to save your changes.

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 monitoring nonoperational for this radio. If this error occurs, reboot the access point. If

the error continues to appear, you might want to disable Cisco CleanAir functionality on the radio.

12-13

Cisco Wireless LAN Controller Configuration Guide

OL-21524-02

Chapter 12 Configuring Cisco CleanAir

Configuring Cisco CleanAir on an Access Point

• N/A—This access point radio is not capable of supporting Cisco CleanAir functionality. Currently,

only Cisco Aironet 3500 series access point radios can be configured for Cisco CleanAir.

Note You can create a filter to make the 802.11a/n Radios page or the 802.11b/g/n Radios page show

only access point radios that have a specific Cisco CleanAir status (such as UP, DOWN, ERROR,

or N/A). This feature is especially useful if your list of access point radios spans multiple pages,

preventing you from viewing them all at once. To create a filter, click Change Filter to open the

Search AP dialog box, select one or more of the CleanAir Status check boxes, and click Find.

Only the access point radios that match your search criteria appear on the 802.11a/n Radios page

or the 802.11b/g/n Radios page, and the Current Filter parameter at the top of the page specifies

the filter used to generate the list (for example, CleanAir Status: UP).

Using the CLI to Configure Cisco CleanAir on an Access Point

To configure CleanAir functionality for a specific access point using the controller CLI, follow these

steps:

Step 1 Configure Cisco CleanAir functionality for a specific access point by entering this command:

config {802.11a | 802.11b} cleanair {enable | disable} Cisco_AP

Step 2 Save your changes by entering this command:

save config

Step 3 See the Cisco CleanAir configuration for a specific access point on the 802.11a/n or 802.11b/g/n network

by entering this command:

show ap config {802.11a | 802.11b} Cisco_AP

Information similar to the following appears:

Cisco AP Identifier.............................. 0

Cisco AP Name.................................... CISCO_AP3500

...

Spectrum Management Information

Spectrum Management Capable.............. Yes

Spectrum Management Admin State.......... Enabled

Spectrum Management Operation State...... Up

Rapid Update Mode........................ Disabled

Spectrum Expert connection............... Disabled

Spectrum Sensor State................. Configured (Error code = 0)

Note See Step 7 in the “Using the GUI to Configure Cisco CleanAir on an Access Point” section for

descriptions of the spectrum management operation states and the possible error codes for the spectrum

sensor state.

12-14

Cisco Wireless LAN Controller Configuration Guide

OL-21524-02

Chapter 12 Configuring Cisco CleanAir

Monitoring the Interference Devices

This section describes how to monitor the interference devices of the 802.11a/n and 802.11b/g/n radio

bands using the controller GUI or CLI.

Note Only Cisco Aironet 3500 series access point radios can be configured for Cisco CleanAir.

Using GUI to Monitor the Interference Device

To monitor the interference devices using the controller GUI, follow these steps:

Step 1 Choose Monitor > Cisco CleanAir > 802.11a/n or 802.11b/g > Interference Devices to open the

CleanAir > Interference Devices page see (Figure 12-4).

Figure 12-4 CleanAir > Interference Device 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.

• DevID—Device identification number that uniquely identified the interfering device.

• ClusterID—Cluster identification number that uniquely identifies the type of the devices.

When a CleanAir-enabled access point detects interference devices, detections of the same device

from multiple sensors are merged together to create clusters. Each cluster is given a unique ID. Some

devices conserve power by limiting the transmit time until actually needed which results in the

12-15

Cisco Wireless LAN Controller Configuration Guide

OL-21524-02

Chapter 12 Configuring Cisco CleanAir

Monitoring the Interference Devices

spectrum sensor to temporarily stop detecting the device. This device is then correctly marked as

down. A down device is correctly removed from the spectrum database. In cases when all the

interferer detections for a specific devices are reported, the cluster ID is kept alive for an extended

period of time to prevent possible device detection bouncing. If the same device is detected again,

it is merged with the original cluster ID and the device detection history is preserved.

For example, some bluetooth headsets operate on battery power. These devices employ methods to

reduce power consumption, such as turning off the transmitter when not actually needed. Such

devices can appear to come and go from the classification. To manage these devices, CleanAir keeps

the cluster IDs longer and they are remerged into a single record upon detection. This process

smoothens the user records and accurately represents the device history.

Step 2 Click Change Filter to display the information about interference devices based on a particular criteria.

Step 3 Click Clear Filter to remove the filter and display the entire access point list.

You can create a filter to display the list of interference devices that are based on the following filtering

parameters:

• Cluster ID—To filter based on the Cluster ID, select the check box and enter the Cluster ID in the

text box next to this field.

• AP Name—To filter based on the access point name, select the check box and enter the access point

name in the text box next to this field.

• Interferer Type—To filter based on the type of the interference device, select the check box and

select the interferer device from the options.

Select one of the interferer devices:

–

BT Link

–

MW Oven

–

802.11 FH

–

BT Discovery

–

TDD Transmit

–

Jammer

–

Continuous TX

–

DECT Phone

–

Video Camera

–

802.15.4

–

WiFi Inverted

–

WiFi Inv. Ch

–

SuperAG

–

Canopy

–

XBox

–

WiMax Mobile

–

WiMax Fixed

–

WiFi ACI

–

Unclassified

• Activity Channels

12-16

Cisco Wireless LAN Controller Configuration Guide

OL-21524-02

Chapter 12 Configuring Cisco CleanAir

Monitoring the Interference Devices

• Severity

• Duty Cycle (%)

• RSSI

Step 4 Click Find to commit your changes.

The current filter parameters are displayed in the Current Filter field.

Using the CLI to Monitor the Interference Device

Use these commands to monitor the interference devices for the 802.11a/n or 802.11b/g/n radio band.

• See information for all of the interferers detected by a specific access point on the 802.11a/n or

802.11b/g/n radio band by entering this command:

show {802.11a | 802.11b} cleanair device ap Cisco_AP

Information similar to the following appears:

DC = Duty Cycle (%)

ISI = Interference Severity Index (1-Low Interference, 100-High Interference)

RSSI = Received Signal Strength Index (dBm)

DevID = Device ID

No ClusterID DevID Type AP Name ISI RSSI DC Channel

--- ------------------ ------ ---------- --------------- ---- ----- ---- -------------

1 c2:f7:40:00:00:03 0x8001 DECT phone CISCO_AP3500 1 -43 3 149,153,157,161

2 c2:f7:40:00:00:51 0x8002 Radar CISCO_AP3500 1 -81 2 153,157,161,165

3 c2:f7:40:00:00:03 0x8005 Canopy CISCO_AP3500 2 -62 2 153,157,161,165