1 | Kensington lock slot | 4 | Console port |
|
|
|
|
2 | DC Power connection | 5 | Security padlock and hasp (padlock not |
| included) | ||
|
|
|
|
3 | Gbit Ethernet port | 6 | Mounting bracket pins (feet for desk or |
|
|
| |
|
|
|
|
7Configuring the Access Point
This section describes how to connect the access point to a wireless LAN controller. Because the configuration process takes place on the controller, see the Cisco Wireless LAN Controller Configuration Guide for additional information. This guide is available on Cisco.com.
The Controller Discovery Process
The access point uses standard Control and Provisioning of Wireless Access Points Protocol (CAPWAP) to communicate between the controller and other wireless access points on the network. CAPWAP is a standard, interoperable protocol which enables an access controller to manage a 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.
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.1.91.0 or later to support 3600 series access points.
9
