Cisco Support Community
Showing results for 
Search instead for 
Did you mean: 

Welcome to Cisco Support Community. We would love to have your feedback.

For an introduction to the new site, click here. And see here for current known issues.

New Member

Error Joining the AP-1242AG with 2106 controller

i have converted Autonomous 1242AG series Ap into lightweight mode.i am using 2106 WLC with software version 4.1.185.the Ap doesn't associate the controller .its produce the following error:

Mar 1 00:00:38.071: LWAPP_CLIENT_ERROR: lwapp_name_lookup - Could Not resolve CISCO-LWAPP-CONTROLLER

*Mar 1 00:00:48.098: %LWAPP-5-CHANGED: LWAPP changed state to JOIN

*Mar 1 00:00:48.099: %LINK-5-CHANGED: Interface Dot11Radio0, changed state to administratively down

*Mar 1 00:00:48.099: %LINK-5-CHANGED: Interface Dot11Radio1, changed state to administratively down

*Mar 1 00:00:49.098: %LINEPROTO-5-UPDOWN: Line protocol on Interface Dot11Radio0, changed state to down

*Mar 1 00:00:49.098: %LINEPROTO-5-UPDOWN: Line protocol on Interface Dot11Radio1, changed state to down

*Oct 6 12:30:57.289: %LWAPP-5-CHANGED: LWAPP changed state to CFG

*Oct 6 12:31:02.289: LWAPP_CLIENT_ERROR_DEBUG: spamHandleCfgReqTimer: Did not recieve the Config response

*Oct 6 12:31:02.998: %SYS-5-RELOAD: Reload requested by LWAPP CLIENT. Reload Reason: DID NOT GET CONFIG RESPONSE.

*Oct 6 12:31:02.998: %LWAPP-5-CHANGED: LWAPP changed state to DOWN

Cisco Employee

Re: Error Joining the AP-1242AG with 2106 controller

Hi Sundar,

Can you post me the output of "dir flash:" from AP console and also can you confirm if this is SSC AP or MIC AP?



New Member

Re: Error Joining the AP-1242AG with 2106 controller



its an MIC AP ,now i am in offsite .tommorow i wil send you the output Flash.


Mohana sundaram

New Member

Re: Error Joining the AP-1242AG with 2106 controller


show Flash output as follows

AP001d.4501.2fd0#show flash

Directory of flash:/

2 -rwx 253 Mar 01 2002 00:07:49 +00:00 env_vars

3 -rwx 6168 Oct 06 2007 12:39:34 +00:00 private-multiple-fs

156 drwx 128 Oct 04 2007 01:00:20 +00:00 c1240-rcvk9w8-mx

5 drwx 256 Oct 06 2007 12:01:40 +00:00 c1240-k9w8-mx.124-3g.JA2

15998976 bytes total (10716672 bytes free)

i am expecting your reply



New Member

Re: Error Joining the AP-1242AG with 2106 controller


I think we have experienced something similar and we did a 'more' on the env_vars file and found that the env_vars contained out of date IP default gateway information.

For example:

We established that the env_vars file contents have not been updating correctly. Documentation on the Cisco site suggests that changes to IP configuration information should be reflected in env_vars after a reload of the WAP.

This does not always seem to happen.

As an example, this env_vars contains the incorrect information that the static IP is XX.11.60.100, which is incorrect and at least least a year out of date, despite having undergone reloads since being reconfigured. Obviously, if the WAP comes up using this info, the gateway address etc. will not work...and the WAP is unable to contact the WiSM. We have also had a case where the incorrect DNS address is stored and used, which might be more of an issue for you looking at your output above.

WAPXXX#more flash:/env_vars












We wrote a script to go around and delete all the env_vars files on the 1240 WAP but then discovered that the LWAPP migration tool forces a reload of the WAP that auto-generates the env_vars file that we just deleted, complete with the wrong information again!

I can offer no solution on how to stop the old information being written to env_vars, as I cannot find where it is stored in the first place, it must be somewhere in the flash, but am aware that other people in UK educational establishments have also experienced this issue without a proper fix being provided.

The usual solution appears to be to get the WAP on your desk, delete the env_vars file and then pull the plug on the power. DO NOT SAVE/RELOAD. Put the power lead back in and the WAP should come up without refering to the env_vars file and will take all and any DHCP info you are providing.