Cisco Systems AIRCAP3602IAK9RF, AIRCAP3602ITK9 Troubleshooting the Access Point Join Process

Page 21
Troubleshooting the Access Point Join Process

Troubleshooting the Access Point Join Process

Access 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.

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:

21

Page 20 Page 22
Image 21
Page 20 Page 22
Contents GETTING STARTED GUIDE Cisco Aironet 3600 Series Lightweight Access Points1 About this Guide 2 Introduction to the Access PointIMPORTANT SAFETY INSTRUCTIONS 3 Safety Instructionstranslated safety warnings that accompanied this device. Statement SAVE THESE INSTRUCTIONS20A. Statement 5 Configurations 4 UnpackingExternal Antennas Internal Antennas Regulatory DomainsCountries Supported 6 Access Point Ports and Connectors LED indicator Figure 2 Access Point LED Indicator top-3602I Model272377 The Controller Discovery Process 7 Configuring the Access PointPreparing the Access Point Performing a Pre-Installation Configuration Installation SummaryController Layer 3 devices Cisco Aironet access points Pre-Installation Configuration Setup2106 controller WS-C3550, WS-C3560, and WS-C3750 switches Step 2 Apply power to the access pointC1880 switch 2600, 2610, 2611, 2621, 2650, and 2651 multiservice platformsc. If the access point shuts down, check the power source 9 Deploying the Access Point on the Wireless Network 8 Mounting the Access PointInstalling a Module 10 Installing ModulesStep 5 Screw down the thumb screws on the module Guidelines for Using Cisco Aironet Lightweight Access Points 11 TroubleshootingUsing DHCP Option Checking the Access Point LEDStatus LED LED Status Indications continued Troubleshooting the Access Point Join Process Tested To Comply With FCC Standards FOR HOME OR OFFICE USE 12 Declarations of Conformity and Regulatory InformationModule Models Access Point ModelsVCCI Statement for Japan Japanese Translation Guidelines for Operating Cisco Aironet Access Points in JapanEnglish Translation 03-6434-6500Statement 371-Power Cable and AC Adapter Industry CanadaCanadian Compliance Statement Access Point Models European Community, Switzerland, Norway, Iceland, and LiechtensteinModule Models Page The following standards were applied Health & Safety-EN60950-1 2005 EN 50385EMC-EN 301.489-1 v1.8.1 EN 301.489-17 Radio-EN 300 328 v 1.7.1 EN 301.893 vGeneric Discussion on RF Exposure Declaration of Conformity for RF ExposureThis Device Meets FCC Guidelines for Exposure to Radio Waves Additional Information on RF Exposure Chinese Translation Administrative Rules for Cisco Aironet Access Points in TaiwanAdministrative Rules for Low-power Radio-Frequency Devices Article Regulatory Information Operation of Cisco Aironet Access Points in BrazilPortuguese Translation Declaration of Conformity Statements13 Configuring DHCP Option 43 and DHCP Option Cisco AP c3600-ServiceProviderCisco AP c3600 Type + Length + Value 14 Access Point SpecificationsSpecification CategoryAccess Point Specifications continued refer to Channels and Maximum Power Settings for Cisco Aironet15 Obtaining Documentation and Submitting a Service Request
Related manuals
Manual 52 pages 58.61 Kb
Top Page Image Contents