Lwapp Client Error
Contents |
Aironet 1200 SeriesTroubleshoot and AlertsTroubleshooting TechNotes Resetting the LWAPP Configuration on a Lightweight AP (LAP) Download Print Available Languages Download Options PDF (10.0 KB) View with Adobe Reader on a variety lwapp ap controller ip address of devices Updated:Nov 30, 2011 Document ID:99763 Contents Introduction Prerequisites Requirements Components Used could not resolve cisco-capwap-controller Conventions Manually Configuring the LAP Resetting the LWAPP Configuration on the LAP Behavior in WLC release prior to 6.0.188.0 Behavior in
Discarding Discovery Request In Lwapp From Ap Supporting Capwap
WLC release 6.0.188.0 and later Reset LAP through WLC How to Disable the Reset Button on the AP Registered to the Controller Verify Troubleshoot Related Information Introduction This document explains how to manually set
Lwapp Discovery Request Rejected
or reset the Lightweight Access Point Protocol (LWAPP) static configuration information on a Lightweight Access Point (LAP). Prerequisites Requirements Cisco recommends that you have knowledge of these topics: Basic knowledge of the configuration of LAPs and Cisco WLCs Basic knowledge of LWAPP/CAPWAP Components Used The information in this document is based on these software and hardware versions: Cisco 4400 WLC that runs firmware release 4.1.181.0 Cisco 4400 WLC debug capwap console cli that runs firmware release 7.0.116.0 Cisco Aironet 1240AG Series AP that runs version 12.3(7)JX5 The information in this document was created from the devices in a specific lab environment. All of the devices used in this document started with a cleared (default) configuration. If your network is live, make sure that you understand the potential impact of any command. Conventions Refer to Cisco Technical Tips Conventions for more information on document conventions. Manually Configuring the LAP In a new installation, when a LAP is unable to find a WLC using the discovery algorithms, you can statically configure the information necessary to join a controller via the console port and the AP’s CLI. Refer to Lightweight AP (LAP) Registration to a Wireless LAN Controller (WLC) for more information on the WLC discovery algorithms and the LAP registration process. In order to manually configure static information on a LAP using the AP CLI interface, you can use these EXEC mode CLI commands: AP#capwap ap ip address
it might be useful for all of us... you know that the AP, upon booting, will try
Capwap 3 Dhcp_renew Could Not Discover Wlc
hard to discover a controller, using broadcast, pre-configuration (AP priming as they say) %capwap-3-errorlog: could not resolve cisco-capwap-controller DHCP option 43, DNS, OTAP, etc.Now my friend has an AP at home, and wants to use it to this ap model is not supported by lwapp wlc connect to its corporate network over his VPN link (my friend's router to the company VPN concentrator).The AP is new, so there is no controller IP address the AP could remember http://www.cisco.com/c/en/us/support/docs/wireless/aironet-1200-series/99763-reset-lwappconfig-lap.html from a previous life (AP priming).There is no other AP around, so forget about OTAP.My friend's network is small, so no option 43 or DNS that you can dream of.Okay. Time to be creative... but Cisco thought about this case!You can configure your AP directly from the CLI to provide information to it... boot the AP, get yourself a console connection, and try:AP0023.0410.4aea#lwapp ap http://wirelessccie.blogspot.com/2009/08/configure-your-lwapp-ap-from-ap-cli.html ? controller lwapp primary controller hostname Configure ap hostname ip lwapp ap ip command log-server Configure the syslog server where all LWAPP errors will be loggedAs you can see, you can give your AP, in LWAPP mode, information about a controller:AP0023.0410.4aea#lwapp ap controller ? ip lwapp primary controller ipAP0023.0410.4aea#lwapp ap controller ipAP0023.0410.4aea#lwapp ap controller ip ? address Configure primary Controller IP addressAP0023.0410.4aea#lwapp ap controller ip addAP0023.0410.4aea#lwapp ap controller ip address ? A.B.C.D Controller IP addressAP0023.0410.4aea#lwapp ap controller ip address 10.1.1.10Done. You AP knows how to get to a controller (careful, if your AP is already connected to a controller, using this command does not make any sense anymore, and you get a nice "ERROR!!! Command is disabled" when you issue it).You can also give some other information to your AP, such as AP hostname, or syslog IP address where to dump all issues that the AP might encounter while trying to get to your controller. A useful one is the AP IP address:AP0023.0410.4aea#lwapp ap ip ? address Configure ap static IP address default-gateway Configure Default-gateway IP addressConfigure both! The AP needs both to get out of the loc
unanswered posts View active topics View new posts View your posts Aironet, Access Points, Client Adapters and software, Mobile and Outdoor Wireless, Antennas. Post a reply 6 posts http://www.networking-forum.com/viewtopic.php?t=25879 Page 1 of 1 tuga Junior Member Posts: 75 Joined: Mon Nov 20, 2006 8:43 pm Certs: CCNA LWAPP not connecting Controller Mon Aug 08, 2011 9:55 pm Hi, Recenlty http://what-when-how.com/deploying-and-troubleshooting-cisco-wireless-lan-controllers/ap-debugs-debugging-commands-cisco-wireless-lan-controllers/ i installed Cisco 4400 and connected 1130 to my lan which has LWAPP, but AP is not connecting to the 4400, any idea? Looks like controller not not allowing to could not connect AP to it, AP can ping the controller, AP getting IP address from 2003 dhcp server. I tried manually configured Manager IP on the AP but still ... on the Certificate i enabled Accept Self Signed Certificate (SSC) Accept Manufactured Installed Certificate (MIC) Accept Local Significant Certificate (LSC) Error message on AP:*Mar 1 00:00:06.268: %SYS-5-RESTART: System restarted --Cisco IOS Software, could not resolve C1130 Software (C1130-RCVK9W8-M), Version 12.3(11)JX1, RELEASE SOFTWARE (fc1)Technical Support: http://www.cisco.com/techsupportCopyright (c) 1986-2006 by Cisco Systems, Inc.Compiled Mon 17-Jul-06 11:38 by alnguyen*Mar 1 00:00:07.226: %LINK-3-UPDOWN: Interface FastEthernet0, changed state to up*Mar 1 00:00:08.226: %LINEPROTO-5-UPDOWN: Line protocol on Interface FastEthernet0, changed state to upap>ap>*Mar 1 00:00:19.994: %CDP_PD-4-POWER_OK: Full power - NEGOTIATED inline power sourceenPassword:ap#ap#ap#*Mar 1 00:00:25.274: %LWAPP-5-CHANGED: LWAPP changed state to DISCOVERY*Mar 1 00:00:33.413: %DHCP-6-ADDRESS_ASSIGN: Interface FastEthernet0 assigned DHCP address 10.0.0.200, mask 255.255.225.0, hostname APc471.fe20.4184*Mar 1 00:00:46.689: LWAPP_CLIENT_ERROR_DEBUG: spamHandleDiscoveryTimer : Found the discovery response from MASTER Mwar*Mar 1 00:00:46.698: %LWAPP-5-CHANGED: LWAPP changed state to JOIN*Mar 1 00:00:51.698: LWAPP_CLIENT_ERROR_DEBUG: spamHandleJoinTimer: Did not recieve the Join response*Mar 1 00:00:51.698: LWAPP_CLIENT_ERROR_DEBUG: No more AP manager IP addresses remain.APc471.fe20.4184#*Mar 1 00:00:51.726: %SYS-5-RELOAD: Reload requested by LWAPP CLIENT. Reload Reason: DID NOT GET JOIN RESPONSE.*Mar 1 00:00:51.726: %LWAPP-5-CHANGED: LWAPP changed state to DOWNerror message on 4400:*Mar 06 10:25:34.425: %LWAPP-3-DECODE_ERR: spam_lrad.c:2215 Error decoding join request from AP c4:71:fe:20:41:84*Mar 06 10:25:34.425: %LWAPP-3-KEY_ERR3: spam_crypto.c:1627 Unable to free public key for AP c4:71:fe:20:41:84*Mar 06 10:25:34.425: %LWAPP-3-PAYLOAD_ERR: spam_lrad.c:7222 Join request does not contain valid certificate in certificate payload - AP c4:71:fe:2
commands on an AP. You can achieve this in two ways: ■ Accessing the AP via the console and executing the debug/show commands like you used to do on every IOS device. ■ Executing the show/debug commands from the controller using the AP remote-debug feature. The first method is the one you are used to from IOS devices, although it is not always possible to use this method. That is because the console port from APs is not always physically cabled, and APs are often mounted at places based on a good RF coverage rather than comfortable console access. To execute an AP show/debug command via the controller console, you first need to enable remote debugging on the AP. The following commands needs to be executed using debug ap Cisco_AP. After this, you can execute every IOS command using debug ap command command Cisco_AP syntax. Example A-1 shows how to display the contents of logging buffers of the AP with the name SE.AP-01-1240 using the remote debugs on the controller CLI. Example A-2 shows how to enable CAPWAP event debugs on the AP with the name SE.AP-01-1240 using the remote debugs on the controller CLI. Example A-1 Collecting "show logging" Using the remote-AP-debug Feature Example A-2 Running debug capwap client events Using the remote-AP-debug Feature Example A-3 demonstrates how to verify that remote debugging is enabled on a specific AP. Example A-3 Verifying That Remote Debugging Is Enabled on a Specific AP Table A-52 lists several useful remote debugs for the APs. Table A-52 Remote Debugs
Command Description debug ap command "show capwap client rcb" AP_Name Displays the RCB of the AP. debug ap command "show capwap reap association" AP_Name Displays CAPWAP REAP association information from an AP in H-REAP mode. debug ap command "show capwap reap status" AP_Name Displays the AP mode and its connection state. debug ap command "debug dtls client events" AP_Name Enables DTLS event debugs on an AP. debug a