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

1242 AP can't used capwap/Lwapp command in Lightweight mode

1242 AP can't used capwap/Lwapp command in Lightweight mode

Hall of Fame Super Gold

If you can't use "lwapp" or

If you can't use "lwapp" or "capwap" commands then maybe the AP is running on autonomous IOS?

VIP Purple

Can you configure other

Can you configure other commands ??

I am not sure but may be you have to run this commend before other confg:


"debug lwapp console cli"
"debug capwap console cli"



Dont forget to rate helpful posts

If an lwapp ap is unable to

If an lwapp ap is unable to reach a DHCP server, you can manually configure static controller information using the power injector console port and EXEC mode CLI commands. The static settings configured with the CLI commands are used by the lightweight access point to connect with a controller. These CLI commands can be used only on lightweight access points that are not associated to a controller.


Also, H-REAP access points that are in the Connected mode will not allow the setting or clearing of any configurations via the console. When the access point is in this state, configurations must be done through the controller interface. If access to configuration commands at the access point is required, ensure the access point is in Standalone mode before attempting to enter any configuration commands.


Once the access point has connected to a controller at any point (even if the H-REAP has moved back to Standalone mode), the access point's console will not allow configuration commands until a new password is set. Each H-REAP's password needs to be changed. This can only be set through the CLI of the controller to which the access point is connected. This command syntax can be used at the controller to set either an individual access point's console password or the password to all the controller's access points:


(WLC_CLI)>config ap username password {all | }

Note: For an access point that has not had its console passwords set, be aware that this configuration is only sent to the access point at the point the command is entered at the controller. Any access points that subsequently join to this will require the command be entered again.


Even once the access point has both been given a non-default password and the access point is in Standalone mode, the access point will still not allow access to these commands. In order to make changes to the H-REAP's configuration, the removal of pre-existing static IP addressing and controller IP address configurations is required. This configuration is called the LWAPP Private Configuration and will need to be removed before any new access point CLI commands may be input. In order to do this, enter this command:


AP_CLI#clear lwapp private-config

Note: In order to completely return the access point to factory defaults, upon access point boot, press the Mode button until the Ethernet light turns amber.

Only at this point may any LWAPP configurations be made

Cisco Employee

In WLC releases prior to 6.0

In WLC releases prior to, 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.

If you enter the clear lwapp private-config command, you might see this error message:

AP0017.5922.f384#clear lwapp private-config 
ERROR!!! Command is disabled.

This error message indicates that the static configuration commands are locked out because either:

  • This command was entered while the LAP is registered to a controller.

  • The LAP was previously registered to a WLC, but the username/password was not changed from the default.

CreatePlease login to create content