re-Installation
Configuration Setup
2)
Since we don’t have Controller .
Cycling through green, red, and off
|
||||
So result in 3 )
toubleshooting
the Access Point Join Process
Note
The controller must be running Cisco IOS
Software Release 7.6.120.x or later to support 2700 series access points.
The controller must be running Cisco IOS
Software Release 7.6.120.x or later to support 2700 series access points.
http://www.cisco.com/c/en/us/support/docs/wireless/4400-series-wireless-lan-controllers/99948-lap-notjoin-wlc-tshoot.html
cess
points can fail to join a controller for many reasons: a RADIUS authorization
is pending; self-signed certificates are not enabled on the controller; the
access point’s and controller’s regulatory domains don’t match, and so on.
Controller software enables you to configure the access points
to send all CAPWAP-related errors to a syslog server. You do not need to enable
any debug commands on the controller because all of the CAPWAP
error messages can be viewed from the syslog server itself.
4)
5) Guidelines
for Using Cisco Aironet Lightweight Access Points
· The access point does not support Wireless Domain Services
(WDS) and cannot communicate with WDS devices. However, the controller provides
functionality equivalent to WDS when the access point joins it.
· CAPWAP does not support Layer 2. The access point must get
an IP address and discover the controller using Layer 3, DHCP, DNS, or IP
subnet broadcast.
· The access point console port is enabled for monitoring
and debug purposes. All configuration commands are disabled when the access
point is connected to a controller.
Refer : http://www.cisco.com/c/en/us/td/docs/wireless/access_point/2700/quick/guide/ap2700getstart.pdf
Config issues
https://supportforums.cisco.com/document/61936/autonomous-ap-and-bridge-basic-configuration-template
