User's Manual
Table Of Contents
- 1 About this Guide
- 2 About the Access Point
- 3 Safety Instructions
- 4 Unpacking the AP
- 5 Ports and Connectors on the AP
- 6 Preparing the AP for Installation
- 7 Installation Overview
- 8 Performing a Pre-Installation Configuration
- 9 Mounting the Access Point
- 10 Powering the Access Point
- 11 Configuring and Deploying the Access Point
- 12 Checking the Access Point LEDs
- 13 Miscellaneous Usage and Configuration Guidelines
- 14 Related Documentation
- 15 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
- Generic Discussion on RF Exposure
- This Device Meets International Guidelines for Exposure to Radio Waves
- This Device Meets FCC Guidelines for Exposure to Radio Waves
- This Device Meets the Industry Canada Guidelines for Exposure to Radio Waves
- Cet appareil est conforme aux directives internationales en matière d'exposition aux fréquences radioélectriques
- Additional Information on RF Exposure
- Administrative Rules for Cisco Aironet Access Points in Taiwan
- Operation of Cisco Aironet Access Points in Brazil
- Declaration of Conformity Statements
- 16 Obtaining Documentation and Submitting a Service Request
30
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 12.
• DHCP server discovery—This feature uses DHCP option 43 to provide controller IP addresses to
the access points. Cisco switches support a DHCP server option that is typically used for this
capability. For more information about DHCP option 43, see the
“Configuring DHCP Option 43”
section on page 38.
• DNS discovery—The access point can discover controllers through your domain name server
(DNS). For the access point to do so, you must configure your DNS to return controller IP
addresses in response to CISCO-CAPWAP-CONTROLLER.localdomain, where localdomain is
the access point domain name. Configuring the CISCO-CAPWAP-CONTROLLER provides
backwards compatibility in an existing customer deployment. When an access point receives an IP
address and DNS information from a DHCP server, it contacts the DNS to resolve
CISCO-CAPWAP-CONTROLLER.localdomain. When the DNS sends a list of controller IP
addresses, the access point sends discovery requests to the controllers.