LWAPP 1130 is no longer associated with the controller. Tried command "clear lwapp private-config" and cleared the config. Now when trying to issue the lwapp commands to set the ip and other configuration, getting "ERROR!!! Command is disabled".
Is this means the static configuration is locked? How to "unlock" it?
You'll need to hold down the "Mode" button during startup for a few seconds (Until the light turns amber) which will get AP out of the controller mode and should allow to set the controller IP and so forth.
That said, if the AP is on the same subnet as the controller, you wouldn't need to set the IP address on the AP. That's supposed to be one of the benefits of using LWAPP APs.
Question - why the command may be locked?
Answer - The LAP was previously registered to a WLC, but the username/password was not changed from the default
Solution - Once your LAP successfully registers with the WLC, the static LWAPP configuration commands (discussed in the previous section) are locked out and are no longer accessible. In order to re-enable the commands, you must have set the username and password while the LAP was joined to the previous controller.
When the LAP is registered to a controller, use this controller CLI command to set the AP's username and password:
config ap username <username> password <password> <ALL | AP Name>
When tried resetting the device (1242AG) by holding down the mode button. It shows:
button pressed for 20 seconds
process_config_recovery: set IP address and config to default 10.0.0.1
process_config_recovery: image recovery
Upon restarting though I still get the ERROR!!! when attempting to set the lwapp private-config. I also note that a 'show lwapp private-config' indicates that there is still a default gateway set. Again, I cannot 'clear' that due to the ERROR!!!
Put that AP on the same subnet as the controller, and try to join it. You'll be able to reset it to factory configs then.
AP should boot to ap> prompt and initialise. It may well generate r0.core and r1.core dump files as radio firmware not available.
ap> en (password in our case was the default) ap# conf t
ap(config)# int bvi1
ap(config-if)# ip address a.a.a.a m.m.m.m
ap(config-if)# line vty 0 4
ap(config-line)# login local
ap(config)# username test password aptest
Once this is done the AP should be alive on the network and you should be able to ping and telnet to it and logon. Enable secret will still be the default password.
Now you need to put the logon details in an ip.txt file for the Cisco WLAN recovery tool, we used the recovery tool's own tftp server and didn't enter WLC details.
Click Start and Cisco tool should contact the AP, telnet in, modify the config and download the recovery image and a basic config. Once done it will reboot the AP and it will go into lwapp discovery mode.
To get the radio up you'll actually have to untar the full package (c1240-k9w7-tar.124-10b.JA.tar) as this has the firmware for the wireless:
The workaround we had was specifically to get it back to a 'configurable' state so that we could use the upgrade tool to convert it to a clean LAP. There is no need or capacity to use wireless for this process - it's all done over Ethernet - so we did not load the radio firmware (hence the r0.core and r1.core dumps).
Steps - If the recovery image is still on the AP
First, check the flash:
Directory of flash:/
2 -rwx 279 May 09 2008 11:52:20 +00:00 env_vars
4 -rwx 6168 May 09 2008 11:52:20 +00:00 private-multiple-fs
6 drwx 256 May 09 2008 11:49:05 +00:00 c1240-k9w8-mx.124-3g.JA2
5 drwx 128 Mar 01 2002 00:03:43 +00:00 c1240-rcvk9w8-mx