User's Manual
Table Of Contents
- 1 About this Guide
- 2 Taking Out What You Need
- 3 Overview
- 4 Installing the Access Point
- 5 Configuring the Access Point
- 6 Troubleshooting
- 7 Declarations of Conformity and Regulatory Information
- Manufacturers Federal Communication Commission Declaration of Conformity Statement
- VCCI Statement for Japan
- Industry Canada
- Canadian Compliance Statement
- European Community, Switzerland, Norway, Iceland, and Liechtenstein
- Declaration of Conformity with Regard to the R&TTE Directive 1999/5/EC
- Declaration of Conformity for RF Exposure
- Guidelines for Operating Cisco Aironet Access Points in Japan
- Administrative Rules for Cisco Aironet Access Points in Taiwan
- All Access Points
- Declaration of Conformity Statements
- Declaration of Conformity Statements for European Union Countries
- 8 Configuring Option 43
- 9 Access Point Specifications
6
REVIEW DRAFT—CISCO CONFIDENTIAL
LWAPP enabled access points are compatible with CAPWAP and conversion to a CAPWAP controller
is seamless. Deployments can have a mix of CAPWAP and LWAPP software running on the controllers.
The CAPWAP enabled software will allow for access points to join either a controller running
CAPWAP or LWAPP.
The functionality provided by the controller does not change except for customers that have Layer 2
deployments, which CAPWAP does not support.
In an CAPWAP environment, a wireless access point discovers a controller by using CAPWAP
discovery mechanisms and then sends it an CAPWAP join request. The controller sends the access point
a CAPWAP join response allowing the access point to join the controller. When the access point joins
the controller, the controller manages its configuration, firmware, control transactions, and data
transactions.
Note For additional information about the discovery process and CAPWAP, see the Cisco Wireless
LAN Controller Software Configuration Guide. This document is available on cisco.com.
Note CAPWAP support is provided in controller software release 5.2 or greater.
Note Cisco controllers cannot edit or query any access point information using the CLI if the name
of the access point contains a space.
Note Make sure that the controller is set to the current time. If the controller is set to a time that
has already occurred, the access point might not join the controller because its certificate may
not be valid for that time.
Follow these steps to prepare the access point and connect it to the wireless network.
Step 1 TBD ==== ILLUSTRATION(S)
Step 2
ap1140getstart.fm Page 6 Monday, June 16, 2008 8:49 AM