06-05-2009 09:42 AM - edited 07-03-2021 05:41 PM
I upgraded my 1131AG AP from autonomous to lightweight with file "c1130-rcvk9w8-tar.123-11JX1.tar". Now, I can't get the AP to join my WLC, and the lights on the AP constantly blinks red, orange and green. I can't get the AP to get an IP from my DHCP server.
My Ethernet light blinks green, and my radio light blinks amber.
Any ideas how I can fix this issue?
Thanks.
06-05-2009 10:10 AM
How do you have your network setup for the AP's to find the controller? Do you have any other AP's working and associated to the WLC?
Take a look at this link:
06-05-2009 05:30 PM
From the AP, if you can ping the Management IP Address, then type the command lwap ap controller ip address
Hope this helps.
06-05-2009 06:19 PM
You can also try changing the IP address on the ap manager to one that you know is available. I had a similar situation.
* Thanks Leolaohoo *
06-06-2009 11:39 PM
Hii ,
Can you please tell how you converted the autonomous AP to LWAPP ?
Have you used the WCS ? If yes , there is option to provide the controller details.
If no , Put the AP is same subnet as the controller as AP broadcast the discovery in same subnet . It will join the controller.
Once it joins the controller , you can prime it for the correct controller. You can use the commans "config ap primary-base" or you can prim using the controller UI
Thanks
Vinay
06-08-2009 03:46 AM
I used the Cisco Upgrade Tool v3.4 to change autonomous AP to a lightweight.
I have other lightweight APs, and when I connect them, I have no issues connecting to our WLC. So I know it's not a network issue (DHCP, VLAN, etc)
So, the issue is only when I convert an autonomous AP to a lightweight AP.
Now, my ap does not receive an IP from my DHCP (it did before the conversion), and when I connect to the console port of the AP I receive the following error:
*Mar 1 00:08:39.312: LWAPP_CLIENT_ERROR: lwapp_name_lookup - Could Not resolve CISCO-LWAPP-CONTROLLER.mydomain.ca
06-08-2009 04:49 AM
Hii ,
The error is fine , it just tells that AP has not recieved the controller IP via DNS.
Can you please attach the full console logs after the AP reboots?
Also provide these debugs: "debug lwapp client events" from the AP
Thanks
Vinay
06-08-2009 11:27 AM
Here is the information you requested....MY DHCP server gives the AP an IP address, but the only way I can access to AP is with my console cable. His there a way I can change back my AP to autonomous, and try my migration to lightweight again?
AP0021.a0d6.dc1a#sh log
Syslog logging: enabled (0 messages dropped, 2 messages rate-limited,
0 flushes, 0 overruns, xml disabled, filtering disabled)
Console logging: level debugging, 10 messages logged, xml disabled,
filtering disabled
Monitor logging: level debugging, 0 messages logged, xml disabled,
filtering disabled
Buffer logging: level debugging, 11 messages logged, xml disabled,
filtering disabled
Logging Exception size (4096 bytes)
Count and timestamp logging messages: disabled
Log Buffer (4096 bytes):
*Mar 1 00:00:05.979: %SYS-6-LOGGERSTART: Logger process started
*Mar 1 00:00:06.020: %SYS-5-RESTART: System restarted --
Cisco IOS Software, C1130 Software (C1130-RCVK9W8-M), Version 12.3(11)JX1, RELEASE SOFTWARE (fc1)
Technical Support: http://www.cisco.com/techsupport
Copyright (c) 1986-2006 by Cisco Systems, Inc.
Compiled Mon 17-Jul-06 11:38 by alnguyen
*Mar 1 00:00:06.975: %LINK-3-UPDOWN: Interface FastEthernet0, changed state to up
*Mar 1 00:00:07.975: %LINEPROTO-5-UPDOWN: Line protocol on Interface FastEthernet0, changed state to up
*Mar 1 00:00:18.388: %CDP_PD-4-POWER_OK: Full power - NEGOTIATED inline power source
*Mar 1 00:00:25.027: %LWAPP-5-CHANGED: LWAPP changed state to DISCOVERY
*Mar 1 00:00:33.166: %DHCP-6-ADDRESS_ASSIGN: Interface FastEthernet0 assigned DHCP address 10.6.3.156, mask 255.255.248.0, hostname AP0021.a0d6.dc1a
*Mar 1 00:00:36.441: LWAPP_CLIENT_ERROR: lwapp_name_lookup - Could Not resolve CISCO-LWAPP-CONTROLLER.r6.rha-rrs.ca
*Mar 1 00:00:46.442: LWAPP_CLIENT_ERROR: lwapp_name_lookup - Could Not resolve CISCO-LWAPP-CONTROLLER.r6.rha-rrs.ca
*Mar 1 00:00:56.443: LWAPP_CLIENT_ERROR: lwapp_name_lookup - Could Not resolve CISCO-LWAPP-CONTROLLER.r6.rha-rrs.ca
*Mar 1 00:01:06.445: LWAPP_CLIENT_ERROR: lwapp_name_lookup - Could Not resolve CISCO-LWAPP-CONTROLLER.r6.rha-rrs.ca
AP0021.a0d6.dc1a#
Translating "CISCO-LWAPP-CONTROLLER.r6.rha-rrs.ca"...domain server (10.6.0.198)
*Mar 1 00:01:16.446: LWAPP_CLIENT_ERROR: lwapp_name_lookup - Could Not resolve CISCO-LWAPP-CONTROLLER.r6.rha-rrs.ca
LWAPP Client EVENT display debugging is on
AP0021.a0d6.dc1a#
AP0021.a0d6.dc1a#
AP0021.a0d6.dc1a#
AP0021.a0d6.dc1a#
AP0021.a0d6.dc1a#
AP0021.a0d6.dc1a#
Translating "CISCO-LWAPP-CONTROLLER.r6.rha-rrs.ca"...domain server (10.6.0.198)
*Mar 1 00:02:56.456: LWAPP_CLIENT_EVENT: spamHandleDiscoveryTimer: Could not discover any MWAR
*Mar 1 00:02:56.456: LWAPP_CLIENT_EVENT: spamResolveStaticGateway - gateway found
*Mar 1 00:02:56.456: LWAPP_CLIENT_EVENT: DNS Option IpAddr 10.6.0.198 SwitchName CISCO-LWAPP-CONTROLLER.r6.rha-rrs.ca
*Mar 1 00:02:56.458: LWAPP_CLIENT_ERROR: lwapp_name_lookup - Could Not resolve CISCO-LWAPP-CONTROLLER.r6.rha-rrs.ca
Translating "CISCO-LWAPP-CONTROLLER.r6.rha-rrs.ca"...domain server (10.6.0.198)
*Mar 1 00:03:06.458: LWAPP_CLIENT_EVENT: spamHandleDiscoveryTimer: Could not discover any MWAR
*Mar 1 00:03:06.458: LWAPP_CLIENT_EVENT: spamResolveStaticGateway - gateway found
*Mar 1 00:03:06.458: LWAPP_CLIENT_EVENT: DNS Option IpAddr 10.6.0.198 SwitchName CISCO-LWAPP-CONTROLLER.r6.rha-rrs.ca
*Mar 1 00:03:06.459: LWAPP_CLIENT_ERROR: lwapp_name_lookup - Could Not resolve CISCO-LWAPP-CONTROLLER.r6.rha-rrs.ca
Translating "CISCO-LWAPP-CONTROLLER.r6.rha-rrs.ca"...domain server (10.6.0.198)
*Mar 1 00:03:16.460: LWAPP_CLIENT_EVENT: spamHandleDiscoveryTimer: Could not discover any MWAR
*Mar 1 00:03:16.460: LWAPP_CLIENT_EVENT: spamResolveStaticGateway - gateway found
06-08-2009 07:51 PM
Hii ,
Ok rest is fine , only thing is AP is not able to discovery the controller. Please check the ACL , it should not block the LWAPP and CAPWAP ports (12222,12223,5246,5247).
On controller , "debug lwapp events" and "debug lwapp errors enable"
and check if the discovery reaching controller or are there any errors.
Thanks
Vinay
06-08-2009 03:27 PM
Can you please tell how you converted the autonomous AP to LWAPP?
Autonomous to LWAPP (Shortcut)
Requirements:
⢠Image file (The recovery file has the prefix ârcvâ in the image name, such as <>c1240-rcvk9w7-tar.122-15.JA.tar);
⢠AP is connected to the Wireless LAN Controller; and
⢠AP can ping the TFTP server where the image is located.
Procedure
1. Copy the recovery file to the AP using the following command:
archive tar /x tftp://
2. Let the AP boot on this image:
boot system flash:/
3. Reboot the AP.
OPTIONAL
⢠DO NOT ALLOW THE AP TO JOIN THE WIRELESS LAN CONTROLLER IN ORDER TO USE THE OPTIONAL COMMANDS BELOW.
⢠IF POSSIBLE, type the following commands:
ï¾ clear lwapp private-config (This will bring the AP to factory default.);
ï¾ clear lwapp ap ip address
ï¾ clear lwapp ap hostname
ï¾ clear lwapp ap controller ip address
4. Let the AP connect to the Wireless LAN controller.
Discover and save your favorite ideas. Come back to expert answers, step-by-step guides, recent topics, and more.
New here? Get started with these tips. How to use Community New member guide