User Manual
Table Of Contents
- 1 About this Guide
- 2 Safety Instructions
- 3 Unpacking
- 4 Configurations
- 5 Access Point Ports and Connectors
- 6 Configuring the Access Point
- 7 Mounting the Access Point
- 8 Deploying the Access Point on the Wireless Network
- 9 Troubleshooting
- 10 Declarations of Conformity and Regulatory Information
- Manufacturers Federal Communication Commission Declaration of Conformity Statement
- VCCI Statement for Japan
- Guidelines for Operating Cisco Aironet Access Points in Japan
- Statement 371-Power Cable and AC Adapter
- 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 & Medical Directive 93/42/EEC
- Declaration of Conformity for RF Exposure
- Administrative Rules for Cisco Aironet Access Points in Taiwan
- Operation of Cisco Aironet Access Points in Brazil
- Declaration of Conformity Statements
- 11 Configuring DHCP Option 43 and DHCP Option 60
- 12 Access Point Specifications
7
collection of wireless termination points. The discovery process using CAPWAP is identical to the
Lightweight Access Point Protocol (LWAPP) used with previous Cisco Aironet access points.
LWAPP-enabled access points are compatible with CAPWAP, and conversion to a CAPWAP controller
is seamless. Deployments can combine CAPWAP and LWAPP software on the controllers.
The functionality provided by the controller does not change except for customers who have Layer 2
deployments, which CAPWAP does not support.
In a CAPWAP environment, a wireless access point discovers a controller by using CAPWAP discovery
mechanisms and then sends it a 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 later. However, your
controller must be running release 7.5.0.0 or later to support 3702P access points.
Note You cannot edit or query any access point using the controller 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.
Access points must be discovered by a controller before they can become an active part of the network.
The access point supports these controller discovery processes:
• Layer 3 CAPWAP discovery—Can occur on different subnets than the access point and uses IP
addresses and UDP packets rather than MAC addresses used by Layer 2 discovery.
• Locally stored controller IP address discovery—If the access point was previously joined to a
controller, the IP addresses of the primary, secondary, and tertiary controllers are stored in the
access point’s non-volatile memory. This process of storing controller IP addresses on an access
point for later deployment is called priming the access point. For more information about priming,
see the
“Performing a Pre-Installation Configuration” section on page 9.
ap3702pgetstart.fm Page 7 Monday, September 9, 2013 8:58 AM