User Manual
Table Of Contents
- 1 About this Guide
- 2 Introduction to the Access Point
- 3 Safety Instructions
- 4 Unpacking
- 5 Configurations
- 6 Access Point Ports and Connectors
- 7 Configuring the Access Point
- 8 Mounting the Access Point
- 9 Deploying the Access Point on the Wireless Network
- 10 Installing Modules
- 11 Troubleshooting
- 12 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
- 13 Configuring DHCP Option 43 and DHCP Option 60
- 14 Access Point Specifications
21
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.
The state of the access point is not maintained on the controller until it receives a CAPWAP join
request from the access point. Therefore, it can be difficult to determine why the CAPWAP discovery
request from a certain access point was rejected. In order to troubleshoot such joining problems
without enabling CAPWAP debug commands on the controller, the controller collects information for
all access points that send a discovery message to it and maintains information for any access points
that have successfully joined it.
The controller collects all join-related information for each access point that sends a CAPWAP
discovery request to the controller. Collection begins with the first discovery message received from
the access point and ends with the last configuration payload sent from the controller to the access
point.
You can view join-related information for up to three times the maximum number of access points
supported by the platform for the 2500 series controllers and the Controller Network Module within
the Cisco 28/37/38xx Series Integrated Services Routers.
Note The maximum number of access points varies for the Cisco WiSM2, depending on which
controller software release is being used.
When the controller is maintaining join-related information for the maximum number of access points,
it does not collect information for any more access points.
An access point sends all syslog messages to IP address 255.255.255.255 by default when any of the
following conditions are met:
• An access point running software release 5.2 or later has been newly deployed.
• An existing access point running software release 5.2 or later has been reset after clearing the
configuration.
If any of these conditions are met and the access point has not yet joined a controller, you can also
configure a DHCP server to return a syslog server IP address to the access point using option 7 on the
server. The access point then starts sending all syslog messages to this IP address.
When the access point joins a controller for the first time, the controller sends the global syslog server
IP address (the default is 255.255.255.255) to the access point. After that, the access point sends all
syslog messages to this IP address until it is overridden by one of the following scenarios:
• The access point is still connected to the same controller, and the global syslog server IP address
configuration on the controller has been changed using the config ap syslog host global
syslog_server_IP_address command. In this case, the controller sends the new global syslog server
IP address to the access point.
ap3700getstart.fm Page 21 Wednesday, March 27, 2013 10:16 AM