KNet wireless CWLAT 1 0 student guide vol 2 2006

4-91 Overview ...4-91Controller and Access Point Information...4-92Upgrading the Cisco WLAN Controller ...4-95Uploading Files on the Cisco WLAN Controller ...4-99Clearing the Cisco WLAN

Trang 2

Cisco Systems has more than 200 offices in the following countries and regions Addresses, phone numbers, and fax numbers are listed on the Cisco Web site at www.cisco.com/go/offices

Argentina • Australia • Austria • Belgium • Brazil • Bulgaria • Canada • Chile • China PRC • Colombia • Costa Rica Croatia • Czech

Republic • Denmark • Dubai, UAE • Finland • France • Germany • Greece • Hong Kong SAR • Hungary

India • Indonesia • Ireland • Israel • Italy • Japan • Korea • Luxembourg • Malaysia • Mexico • The Netherlands

New Zealand • Norway • Peru • Philippines • Poland • Portugal • Puerto Rico • Romania • Russia • Saudi Arabia Scotland • Singapore • Slovakia • Slovenia • South Africa • Spain • Sweden • Switzerland • Taiwan • Thailand • Turkey Ukraine •

United Kingdom • United States • Venezuela • Vietnam • Zimbabwe

Copyright © 2006, Cisco Systems, Inc All rights reserved CCIP, the Cisco Powered Network mark, the Cisco Systems Verified logo, Cisco Unity, Fast Step, Follow Me Browsing, FormShare, Internet Quotient, iQ Breakthrough, iQ Expertise, iQ FastTrack, the iQ logo, iQ Net Readiness Scorecard, Networking Academy, ScriptShare, SMARTnet, TransPath, and Voice LAN are trademarks of Cisco Systems, Inc.; Changing the Way We Work, Live, Play, and Learn, Discover All That’s Possible, The Fastest Way to Increase Your Internet Quotient, and iQuick Study are service marks of Cisco Systems, Inc.; and Aironet, ASIST, BPX, Catalyst, CCDA, CCDP, CCIE, CCNA, CCNP, Cisco, the Cisco Certified Internetwork Expert logo, Cisco IOS, the Cisco IOS logo, Cisco Press, Cisco Systems, Cisco Systems Capital, the Cisco Systems logo, Empowering the Internet Generation,

Enterprise/Solver, EtherChannel, EtherSwitch, GigaStack, IOS, IP/TV, LightStream, MGX, MICA, the Networkers

logo, Network Registrar, Packet, PIX, Post-Routing, Pre-Routing, RateMUX, Registrar, SlideCast, StrataView Plus,

Stratm, SwitchProbe, TeleRouter, and VCO are registered trademarks of Cisco Systems, Inc and/or its affiliates in the U.S and certain other countries

All other trademarks mentioned in this document or Web site are the property of their respective owners The use of the word partner does not imply a partnership relationship between Cisco and any other company (0201R)

Trang 3

Table of Contents

Volume 2

WLAN Management 4-1 Managing the WLAN from the WLAN Controller 4-3

Overview 4-3Sniffer AP Mode 4-4Logging Options 4-13Aggressive Load Balancing 4-25Statistics 4-29Lesson Self-Check 4-38

Summary 4-40

Managing the Cisco Unified Wireless Network using Cisco WCS 4-41

Overview 4-41Monitor Tab 4-42Location Tracking 4-66Calibration 4-71Cisco WCS Upgrade 4-78Lesson Self-Check 4-87

Summary 4-89

Managing the Cisco WLAN Controller 4-91

Overview 4-91Controller and Access Point Information 4-92Upgrading the Cisco WLAN Controller 4-95Uploading Files on the Cisco WLAN Controller 4-99Clearing the Cisco WLAN Controller 4-100Lesson Self-Check 4-104

Summary 4-106

Managing CiscoWorks WLSE Management with Autonomous Access Points 4-107

Overview 4-107Managing Devices 4-109Duplicate IP Address 4-113Device Description 4-118Faults 4-125Reports 4-140Configurations 4-146Upgrading CiscoWorks WLSE Software 4-161

Trang 4

Wireless Network Troubleshooting 5-1 Troubleshooting the Cisco Advanced Feature Set Wireless Network 5-3

Overview 5-3Troubleshooting Methods 5-5Troubleshooting the Wireless Client 5-14Troubleshooting Link Aggregation (4402/4404) 5-31Troubleshooting Mobility Anchors 5-34Troubleshooting Dynamic Frequency Selection 5-45Troubleshooting the Enhanced Security Module 5-47Lesson Self-Check 5-50

Summary 5-52

Troubleshooting the CiscoWorks Wireless LAN Solution Engine 5-53

Overview 5-53Inventory 5-54Faults 5-55Configuration and Firmware 5-57System Level Diagnostics 5-62Lesson Self-Check 5-75Summary 5-77

Cisco WLAN Security 6-1 Describing Cisco WLAN Security Standards 6-3

Overview 6-3Reasons for Wireless LAN Security 6-4WLAN Security Standards 6-9Lesson Self-Check 6-15Summary 6-17

Describing WLAN Security Threats and Mitigations 6-19

Overview 6-19WLAN Security Vulnerabilities and Threats 6-20WLAN Security Best Practices 6-33Lesson Self-Check 6-41Summary 6-43

Describing Authentication and Encryption 6-45

Overview 6-45802.1X Overview 6-46EAP-Cisco Wireless (LEAP) 6-50EAP-FAST 6-52EAP-TLS 6-58EAP-PEAP 6-60WPA and 802.11i Encryption 6-62WPA2/802.11i 6-69

Trang 5

Lesson Self-Check 6-77 Summary 6-79

Securing the WLAN 6-81

Overview 6-81 RADIUS Server Scalability and Availability 6-82 CiscoWorks WLSE Wireless Intrusion Detection System 6-84 Wireless Protection Policies on the WLAN Controller 6-92 Rogue Access Points and Ad-Hoc Clients 6-96 Intrusion Detection Management 6-110 Client Exclusion Policies 6-115 Lesson Self-Check 6-125 Summary 6-127

Trang 6

Trang 7

Manage WLAN controllers and lightweight access points using the Cisco WCS

Manage the Cisco WLAN controller

Determine the necessary processes to manage the wireless LAN with CiscoWorks WLSE

Trang 8

Trang 9

Describe the steps to enable Sniffer AP mode on the Cisco WLAN controller

Describe the logging options available on the Cisco WLAN controller

Describe the steps to enable aggressive load balancing on the Cisco WLAN controller

Describe the statistics available on the Cisco WLAN controller

Trang 10

Sniffer AP Mode

This topic will describe the steps to enable Sniffer AP mode on the Cisco WLAN controller

• socket.dll

• socketres.dll

When an access point is set to Sniffer AP Mode, the access point goes into promiscuous mode and all traffic collected will be forwarded to a PC running WildPackets® AiroPeek Traffic from the access point will be tunneled back to the WLAN controller and then forwarded to a

PC running AiroPeek

Note Sniffer feature can be enabled only if you are running AiroPeek, which is a third-party

network analyzer software that supports decoding of data packets

Trang 11

Sniffer AP Mode

Remote AiroPeek PC must be reachable via IP from the management interface of the controller

AP Sniffer Mode Channel 36

Controller

AP Local Mode

Collected Data

AiroPeek PC

Collected Data

When sniffer feature is enabled on an access point, the access point functions as a sniffer and captures and forwards all the packets on a particular channel to a remote machine that runs AiroPeek These packets contain information on timestamp, signal strength, packet size and so

on

How it works:

The access point goes into promiscuous mode and collects data on a configured channel

The access point forwards the captured packets to its associated controller

The associated controller forwards the packets from its management interface to the PC running AiroPeek at a central site

Note The PC running AiroPeek must be reachable via IP from the management interface of the

controller

Note When the access point is put in sniffer mode it goes to “listen only” so it will not service

clients

Trang 12

Sniffer AP Mode Packet Format From Access Point

AP Sniffer Mode Channel 36

Controller

Collected Data

LWAPP Header (layer 2 or layer 3)

AiroPeek Header

Include size, rssi, timestamp &

Flags (wep, crc, error, control frame, etc.)

Original 802.11 frame as captured

Access point adds extra 802.11 header and SNAP header along with the LWAPP header to allow the NPU to switch the packet as client traffic

The inner IP packet including the IP Header, UDP Header, and AiroPeek Header may exceed the 1500 byte limit If this is the case, the access point will fragment the inner IP packet and send it to the switch as two IP fragments

Trang 13

Sniffer AP Mode Packet Format from Controller

Controller

AiroPeek PC

Collected Data

AiroPeek Header

Include size, rssi, timestamp &

Flags (wep, crc, error, control frame, etc.)

Original 802.11 frame as captured

Once the packet leaves the controller, it is routed via regular IP methods to the AiroPeek PC

Trang 14

Wireless > Cisco APs > Detail

Configure an access point in sniffer mode using the web user interface by completing these steps:

Step 1 Use Configure > Access Points, select an item under AP Name list to navigate to

Trang 15

Wireless > 802.11a or 802.11b/g Radios >

Configure

After enabling the radio to Sniff, configure the channel to monitor and

IP address of the AiroPeek PC

Step 3 Select a protocol (802.11a/802.11b/g) under Radio Interfaces This will open the

configuration page

Step 4 Enable the Sniff check box to bring up the Sniff parameters Select the channel to be

sniffed and enter the IP address of the server (The remote machine running AiroPeek)

Step 5 Select Save to save the changes

Now the access point is configured to sniff that particular channel, capture packets and forward them to the server

Trang 16

Configuring AiroPeek

Configured an access point

in sniffer mode at the remote site

Installed AiroPeek version 2.05 or later on a Windows

XP machine Copy two special dll files

to specific directories Start AiroPeek

Before using sniffer feature, you must have completed the following:

Configure an access point in sniffer mode at the remote site

Install AiroPeek version 2.05 or later on a Windows XP machine

Copy the following dll files:

— socket.dll file to the Plugins folder (Example:

C:\ProgramFiles\WildPackets\AiroPeek\Plugins)

— socketres.dll file to the PluginRes folder (Example:C:\ProgramFiles\WildPackets\AiroPeek\1033\PluginRes)

Note Contact Wildpackets® for the files

Complete the following steps to configure AiroPeek on the remote machine

Step 1 Start AiroPeek to launch the application

Step 2 From the Tools menu, choose Options

Step 3 In the Options window, select Analysis Module

Step 4 Right click inside the Analysis Modules table and choose Disable All option

Step 5 Find Cisco remote module column and enable it Select OK to save the changes

Trang 17

Configuring AiroPeek (Cont.)

Select Adapter from the list of adapter modules, and then select Cisco remote adapter

Expand it to locate the new remote adapter option.

Open a new window

• Enter a name in the name field

• Enter the IP address of the controller management interface

New adapter will be added

Step 6 Select New capture to bring up the Capture Option window

Step 7 Select Adapter and from the list of adapter modules, and then select remote Cisco

adapter

Step 8 Expand it to locate the new remote adapter option Double click on it to open a new

window, enter a name in the field provided and enter the controller management interface IP in the IP address column

Step 9 Select OK The new adapter will be added to the remote Cisco adapter

Trang 18

Configuring AiroPeek (Cont.)

Start socket capture to start the remote capture Enter CLI command config ap mode

sniffer <ap-name>

Step 10 Select the new adapter for remote AiroPeek capture using the access point

Use any name that you wish in the name field

Use the IP address of the controller management interface

Step 11 Select start socket capture option in capture window to start the remote capture

process

Step 12 Go to the controller CLI, bring up an access point and set it to sniffer mode by

keying the command config ap mode sniffer <ap-name>

The access point will reboot and come up in sniffer mode

Trang 19

Logging Options

This topic will describe the logging options available on the Cisco WLAN controller

Logging Options

Message logs Simple Network Management Protocol (SNMP) Controller crash

Access point log Syslog server

The information collected in these log options are highly valued by technical support and sustaining engineering for detailed trouble analysis

Trang 20

Management > Message Logs

Message Logs are a “first in first out”

log with a maximum of 256 entries which requires a syslog server if more than 256 entries are required

Use MANAGEMENT > Message logs to navigate to this page

This page allows you to set the Message Log filter to include the following or more critical messages:

Critical Failure

Software Error

Authentication or Security Errors

Unexpected Software Events

Significant System Events

Select Apply to implement the desired Message Log filter level

You can view the message logs which have been captured by the controller, last to first message Each trap entry includes the System Time, Filename and Line, Message Type and Message

Trang 21

Management > SNMP > General

Use MANAGEMENT > SNMP > General to navigate to this page This page allows you to

change some of the SNMP system parameters

Name: Customer definable name of the controller

Location: Customer definable controller location

Contact: Customer definable contact details

System Description: Read-only controller description

System Object ID: Read-only object ID

SNMP Port Number: Read-only Simple Network Management Protocol (SNMP) port

number

Trap Port Number: Definable trap port number; Default is 162

SNMP v1 Mode: Enable or disable SNMP v1; Default is disabled

SNMP v2c Mode: Enable or disable SNMP v2c; Default is disabled This parameter

should be modified if remote management is desired

SNMP v3 Mode: Enable or disable SNMP v3; Default is disabled This parameter should

be modified if remote management is desired

Trang 22

Management > SNMP > SNMP V3 Users

To add new users use MANAGEMENT > SNMP > SNMP V3 to navigate to this page

This page provides a summary of the SNMP users as described as follows

SNMP User Summary includes the following parameters:

User Name: Name of the user profile

Access Level: Read Only; Read Write

Auth Protocol: None; HMAC-MD5; HMAC-SHA

Privacy Protocol: None; CBC-DES

Remove a user profile by selecting the appropriate Remove link You are prompted for confirmation of the user removal

Command buttons include:

New: Select to add a new SNMP user (SNMP V3 Users > New)

Help: Request that the help page be displayed in a new browser window

Trang 23

Management > SNMP > Communities

Cisco recommends that default SNMP community of private be modified at the time of installation

Use MANAGEMENT > SNMP > Communities to navigate to this page

This page provides a summary of the SNMP community as described below:

Community Name: The community string to which this entry grants access A valid entry

is a case-sensitive alphanumeric string of up to 16 characters Each row of this table must contain a unique community name

IP Address: An IP address from which this device accepts SNMP packets with the

associated community The requesting entity's IP address is ANDed with the Subnet Mask before being compared to the IP Address

Note If the Subnet Mask is set to 0.0.0.0, an IP Address of 0.0.0.0 matches all IP addresses The

default value is 0.0.0.0

IP Mask: A mask to be ANDed with the requesting entity's IP address before comparison

with IP Address If the result matches with IP Address then the address is an authenticated

IP address For example, if the IP Address = 9.47.128.0 and the corresponding Subnet Mask = 255.255.255.0 a range of incoming IP addresses would match, that is, the incoming

IP Address could equal 9.47.128.0 - 9.47.128.255 The default value is 0.0.0.0

Access Mode: The access level for this community string May be specified by selecting

Read/Write or Read Only from the pull-down

Status: The status of this community access entry When this object is set to enabled, if the

Community Name for this row is not unique among all valid rows, the set request is rejected

Trang 24

Management > SNMP > Trap Receiver

Use MANAGEMENT > SNMP > Trap Receivers to navigate to this page

This page provides a summary of existing SNMP trap receivers as described below:

Trap Receiver Name: The name of the server where the traps are sent

IP Address: The IP address of the server

Status: Status must be enabled for the SNMP traps to be sent to the server

Edit a user profile by selecting the Edit link (SNMP Trap Receiver > Edit)

Remove a user profile by selecting the appropriate Remove link You are prompted for

confirmation of the trap removal

Trang 25

Management > SNMP > Trap Logs

Trap Logs are a “first in first out” log with a maximum of 256 entries which requires a syslog server if more than 256 entries are required

Use MANAGEMENT > SNMP/Trap Logs to navigate to this page

You can view the traps logs which have been captured by the controller Each trap entry

includes the Log Number, System Time, and Trap Description

This screen also displays the number of traps since Last Reset and number of traps since Log Last Viewed

Note Refer to the online help for the Client Reason and Status Codes You are likely to encounter

them when reviewing the Trap Logs

Trap Logs are a “first in first out” log with a maximum of 256 entries A syslog server must be configured if more than 256 entries are required

Trang 26

Management > SNMP > Trap Controls

Only those SNMP traps that are checked will be sent to WCS or Trap Receivers

Use MANAGEMENT > SNMP > Trap Controls to navigate to this page

This page allows you to select which traps logs should be captured Select the applicable logs

and select Apply

Trang 27

Management > Tech Support > Controller Crash

Controller will maintain up to 5 controller Crash files

Use MANAGEMENT > Tech Support > Controller Crash to navigate to this page

You can view the most recent controller CPU crash files on this page, from most to least recent

Trang 28

Management > Tech Support > AP Log

Use MANAGEMENT > Tech Support > AP Log to navigate to this page

You can view the most recent access point log information on this page

The information available is listed below

Trang 29

Syslog Configuration

Syslog messages are similar to debug messages and can be viewed in the message log

There are select message only made available to syslog which will not appear

in the message log

Use MANAGEMENT > Syslog to navigate to this page Use this page to enable or disable

system logs If you enable syslogs, enter the Syslog Server IP Address

Note When a controller is rebooted, all messages are lost Forwarding those messages to a

Syslog server will provide an audit trail even in the event of a controller reboot

Enable syslog is disabled by default Multiple facilities are not currently supported Multiple syslog servers are not currently supported

Trang 30

Management > Tech Support > System Resource Information

Use MANAGEMENT > Tech Support > System Resource Information to navigate to this

page

You can view the current controller CPU usage, system buffer, and web server buffers parameters on this page

Trang 31

Aggressive Load Balancing

This topic will describe the steps to enable aggressive load balancing on the Cisco WLAN controller

Aggressive Load Balancing

The ability, on a single controller, to detect access point load and attempt to move new clients to access points that can provide adequate coverage based on the following criteria

Invoked only when the following criteria have been met

• If more than one access point on a given controller has heard a given client

• If more than one access point from the “list” has heard a given client in the last 5 seconds

• If any access points from the “short list” can provide coverage equal to or greater than the Coverage parameter

• If any access points from the “acceptable access points” have less clients plus the Window parameter than the loaded access point

–Only available in CLI config load-balancing window <value> in release later than 2.0.141.0

Normal client behavior is to send out a Probe Request looking for the strongest signal Usually the client will attempt to connect to the access point with the strongest signal and if that fails, the next strongest Since the controller has a record of all the access points that heard the client, and the controller already knows the number of clients already connected to each access point, the controller has all of the information needed to create a balanced network

When a new client attempts to connect to a particular access point and if that access point is already loaded, the controller will attempt to find another access point which can communicate with the client at acceptable signal strength If the controller finds an acceptable Received Signal Strength Indicator (RSSI) and signal-to-noise ratio (SNR) value for another access point connected to the controller which has a lighter load, the controller will deny the connection of the client to the loaded access point Typically, the client should try the next best signal and successfully associate to that access point

Note The controller will list up to 8 access points per client that have heard any given client for

efficient load balancing and location tracking

Trang 32

Aggressive Load Balancing (Cont.)

If criteria is met, the controller will send new clients attempting association a single unicast status code=17 response (unable to support additional associations)

• Allows denied clients to roam to an access point with less load supporting the same coverage area

• Client that attempts association to the same loaded access point will be allowed onto the system but a trap can be generated to note the issue

With not met, the access point will accept new clients subject to the normal 802.11 restrictions

Not invoked when the following are true

• If client requests association/reassociation to an access point to which it is already associated

• If turned off

As an example, if a given client has been heard by three access points associated with a single controller, the “list” would consist of all three access points If only two of the access points can provide coverage to a minimum of the coverage parameter or if only two the access points have heard the client within the last five seconds, the “acceptable access points” would consist

of only those two access points that meet these criteria

Of those two access point, let us say that AP1 has four clients while AP2 has 2 clients and the Windows value is set to 1 If a new client attempted to associate with AP1, it would receive a status code=17 response in the hope that it would roam to AP2

If the Windows value were set to two, the new client would be allowed to associate to AP1 since the relative difference of clients on AP2 plus the Windows value was equal to or greater than the number of clients already associated with AP1

Note The Windows value by default is set to 0

Trang 33

Controller > General

Use CONTROLLER > General to navigate to this page

Enable or disable the aggressive load balance algorithm

The Cisco Wireless IP Phone 7920 has its own method of determining when to load balance Having Aggressive Load Balancing enabled creates unneeded delays that could lead to

noticeable jitter and may also cause authentication failures and association flapping For the Cisco Wireless IP Phone 7920, aggressive load balancing must be disabled on the controller

Trang 34

Wireless > Global RF > 802.11b/g Network >

Auto RF

A client must have another access point associated to the same controller with Coverage Exception Level different than the first access point to which association is attempted prior to the controller denying association.

Use WIRELESS > Global RF 802.11b/g Network and then select Auto RF to navigate to this

page The Auto RF characteristics may be modified on this page

Coverage Exception Level (0 to 100%): The coverage exception level is between 0 and 100

percent

A client must have another access point associated to the same controller with a coverage exception level different than the first access point to which association is attempted prior to the controller denying association

Trang 35

Statistics

This topic will describe the statistics available on the Cisco WLAN controller

Monitor > Statistics > Controller

Use MONITOR > Statistics > Controller to navigate to this page

The following describes the controller statistics displayed on this page

Octets Received: The total number of octets of data received by the processor (excluding

framing bits but including FCS octets)

Packets Received Without Error: The total number of packets received by the processor

Unicast Packets: The number of subnetwork-unicast packets delivered to a higher-layer

protocol

Multicast Packets: The total number of packets received that were directed to a multicast

address Note that this number does not include packets directed to the broadcast address

Broadcast Packets: The total number of packets received that were directed to the

broadcast address

Receive Packets Discarded: The number of inbound packets which were chosen to be

discarded even though no errors had been detected to prevent their being deliverable to a higher-layer protocol A possible reason for discarding a packet could be to free up buffer space

Octets Transmitted: The total number of octets transmitted out of the interface, including

framing characters

Trang 36

Multicast Packets Transmitted: The total number of packets that higher-level protocols

requested be transmitted to a Multicast address, including those that were discarded or not sent

Broadcast Packets Transmitted: The total number of packets that higher-level protocols

requested be transmitted to the Broadcast address, including those that were discarded or not sent

Transmit Packets Discarded: The number of outbound packets which were chosen to be

discarded even though no errors had been detected to prevent their being deliverable to a higher-layer protocol A possible reason for discarding a packet could be to free up buffer space

Most Address Entries Ever Used: The highest number of Forwarding Database Address

Table entries that have been learned by this controller since the most recent reboot

Address Entries in Use: The number of Learned and static entries in the Forwarding

Database Address Table for this controller

Maximum VLAN Entries: The maximum number of virtual LANs (VLANs) allowed on

this controller

Most VLAN Entries Ever Used: The largest number of VLANs that have been active on

this controller since the last reboot

Static VLAN Entries: The number of presently active VLAN entries on this controller that

have been created statically

VLAN Deletes: The number of VLANs on this controller that have been created and then

deleted since the last reboot

Time Since Counters Last Cleared: The elapsed time, in days, hours, minutes, and

seconds, since the statistics for this controller were last cleared

Trang 37

Monitor > Statistics > Ports > Port Statistics

> View Stats

Use MONITOR > Statistics > Ports and then select View Stats to navigate to this page

This page displays statistics on a per port basis The Port Number appears on the main data page directly below the page title and above the Traffic Statistics tables See the Controller Web User Interface Online Help for an explanation the port statistics

Select Clear Counters to set all summary and controller detailed statistics counters to zero; also resets the "Time Since Counters Last Cleared" field

Trang 38

Monitor > Wireless > 802.11a or 802.11b/g Radios > Detail

Details are available for either 802.11a or 802.11b/g radios This screen can also be viewed in a Text View.

Use MONITOR > Wireless > 802.11a Radios or MONITOR > Wireless > 802.11b Radios and then select Detail to navigate to this page

This page displays the RF (Radio Frequency) statistics for the selected Cisco radio You can alternate between the Graphics View and the Text View clicking the Graphics View/Text View button You can view and refresh statistics by selecting them (using the checkboxes) and then selecting the Refresh button on the data page:

Radio Type (802.11a or 802.11b/g)

Operational Status - Displays the operational status of the Cisco radios, either UP or DOWN

Monitor Only Mode (Cisco Aironet 1000 Series lightweight access point) Status - Local (Cisco Aironet 1000 Series lightweight access point in same-subnet mode or in Rogue Detector mode), Cisco 1030 remote edge lightweight access point (Cisco Aironet 1030 IEEE 802.11a/b/g remote edge lightweight access point), or Monitor (Cisco Aironet 1000 Series lightweight access point in monitor-only mode)

Current Channel Number

Profile Information - Graphics View and Text View

Trang 39

The RF statistics are used to derive the Radio Resource Management (RRM) profile for each Cisco radio in your network The controller uses the RRM profile to adjust the Cisco radio transmit and receive levels in order to maintain the most efficient configuration for your

network This data view also displays the RF properties of the controller and its clients

The RRM PASSED/FAILED thresholds are globally set for all access points in the 802.11a Global Parameters > Auto RF and 802.11b/g Global Parameters > Auto RF pages

The RRM PASSED/FAILED thresholds are individually set for this access point in the 802.11

AP Interfaces > Performance Profile page

Trang 40

Monitor > Wireless > 802.11a or 802.11b/g Radios > Detail - Text View

This figure represents the Text View You can alternate between the Graphics view and text view by selecting the Graphics View/Text View button

Định dạng
Số trang	406
Dung lượng	16,15 MB