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