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. If you'd prefer to explore, try our test area to get started. And see here for current known issues.

New Member

WLC 4402 + LAP-1242AG + No DHCP

Greetings to all,

I am trying to get some LAP-1242 to join a 4402 controller without using any DHCP server. Is that possible?

Thank you in advance

Hall of Fame Super Silver

Re: WLC 4402 + LAP-1242AG + No DHCP

You can assign an IP to the AP's via the console port and also assing the primary WLC management port.

AP#lwapp ap ip address

AP#lwapp ap ip default-gateway

AP#lwapp ap controller ip address

AP#lwapp ap hostname


*** Please rate helpful posts ***
New Member

Re: WLC 4402 + LAP-1242AG + No DHCP

We tried to connect via console to LWAP directly, but it does not let us write a configuration. the AP does not accept any configuration. can I connect to the AP's console via the controller and set the IP from there?

Thank you

Re: WLC 4402 + LAP-1242AG + No DHCP

Reset the AP by holding down the mode button for 20seconds at bootup.

Then console to the AP, end issue the command "Clear lwapp private-config".

You will then be able to issue the commands detailed above.


New Member

Re: WLC 4402 + LAP-1242AG + No DHCP

OK, but I have one question. after performing the above, the AP will work in Autonomous mode? I would like to keep the LightWeight mode on the AP in order to use it with the 4402 Controler.

Thank you very much

Hall of Fame Super Silver

Re: WLC 4402 + LAP-1242AG + No DHCP

the ap is not autonomous it is lightweight... unless to convert it to IOS. If you were able to enter the commands mentioned in previous post, then the ap is an LWAP. if not, and you can issues a wr mem, then you will need to convert that ap the Lightweight.

*** Please rate helpful posts ***
Hall of Fame Super Red

Re: WLC 4402 + LAP-1242AG + No DHCP

Hi Stelios,

Just thought I might add a note to the good info from Scott and Richard (5 points to both of you for this helpful info!)

There is no danger of this AP reverting to Autonomous without a concerted effort on your part to reload an IOS :)

Here is a summary;

To clear or remove the manually entered controller information, you can use these EXEC mode CLI commands:

clear lwapp ap ip address

clear lwapp ip default-gateway

clear lwapp controller ip address

clear lwapp ap hostname

Manually Resetting the Access Point to Defaults

You can manually reset your access point to default settings using this EXEC mode CLI command:


Note This command requires the controller configured Enable password to enter the CLI EXEC mode.


clear lwapp private-config

From this Troubleshooting doc;

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

So try this;

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 password

From this excellent doc :)

Resetting the LWAPP Configuration on a Lightweight AP (LAP)

Hope this helps!