clear lwapp IP address

Unanswered Question
Aug 25th, 2009

Is there a way to clear the IP config on an LWAPP that has a configured IP address that was set when converting it from AP to LWAPP?

When I enter the clear lwapp private-config command that does not clear the IP address. I need the unit to get the DHCP address.

The unit is an 1130.

Seth

I have this problem too.
0 votes
  • 1
  • 2
  • 3
  • 4
  • 5
Overall Rating: 0 (0 ratings)
Loading.
rob.huffman Tue, 08/25/2009 - 07:34

Hey Seth,

The AP is most likely looking for the username/password that can be configured while the AP is connected to the WLC :) If no username/password was configured via the WLC this command is not available.

If the LWAPP AP did have the username and password changed while the LAP was joined to the controller then this is available via the AP's console connection

--------------------------------------------------------------------------------

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

--------------------------------------------------------------------------------

clear lwapp private-config

From this Troubleshooting doc;

http://www.cisco.com/en/US/docs/wireless/access_point/1130/installation/guide/113h_c4.html#wp1091061

setting of a Username/Password on an LWAPP AP becomes a valuable step in the configuration process;

Resetting the LWAPP Configuration on a Lightweight AP (LAP)

http://www.cisco.com/en/US/products/hw/wireless/ps430/products_tech_note09186a00808e2d27.shtml

Deleting the LWAPP Configuration File to Redeploy the AP

When you redeploy an access point after moving it from one location to another, you must first delete the LWAPP configuration file and restore the access point to the factory default settings. Deleting the LWAPP configuration enables the commands on the access point console to configure the static IP address on the access point, the IP address on the controller, the access point hostname, and the default gateway IP address.

To delete the LWAPP configuration and restore the factory defaults, enter the following command in EXEC mode on the access point console:

clear lwapp private-config

The clear lwapp private-config command becomes available on the access point console after the controller pushes a new username and password to the access point.

http://www.cisco.com/en/US/docs/wireless/access_point/conversion/lwapp/upgrade/guide/lwapnote.html#wp169479

Hope this helps!

Rob

srosenthal Thu, 08/27/2009 - 05:59

Rob,

This unit has never connected to the WLAN controller. It was converted from autonomous to LWAPP and I forgot to have the program clear the IP address when it converted it. So it has the IP address that was configured on it for conversion.

Any suggestions?

Seth

Leo Laohoo Tue, 08/25/2009 - 14:23

Hi Seth,

In addition to Rob's posting, you'll get "command disabled" when the LAP is running the LWAP image.

If the LAP has two image, one RCV image and one LWAP image, delete the LWAP image and let the LAP boot the RCV image.

The command to delete the lwapp configuration should be enabled.

Hope this helps.

rob.huffman Thu, 08/27/2009 - 13:07

Hey Seth,

The first thing that comes to mind is to revert from LWAPP to Autonomous and start the process over. I can't think of anything else right now :)

Cheers!

Rob

Leo Laohoo Thu, 08/27/2009 - 15:24

Hi Rob,

Don't need to go that far. In my expereience, just booting the AP in the RCV image is sufficient.

Hope this helps.

srosenthal Fri, 08/28/2009 - 11:46

If the AP has never talked to a controller doesn't that mean that it is already booting with the RCV image? This is an AP that was converted from autonomous to LWAPP and has never talked to a controller. The file that I used was c1130-rcvk9w8-tar.123-11JX1.tar

Seth

weterry Thu, 08/27/2009 - 19:37

If the running configuration on the AP shows the static IP address assignment on the Fa0 port, you might be able to type:

"debug lwapp console cli"

"config t"

Then go into the Fa0 interface and convert the IP address statement to that of DHCP (not sure the exact syntax.. but it should be something like "ip address dhcp....").

This will not fix the issue permanantly, but it might be enough to get it to join the controller where you can then set it back to DHCP on the controller...

Leo Laohoo Sun, 08/30/2009 - 16:13

Hi Seth,

Didn't realize you were using a very old RCV image, 12.3. Try using any 12.4 and the command should work.

pirateoftheairwaves Sun, 08/30/2009 - 23:39

if you have a spare controller like a 2100 series. just change the management ip on the same subnet as the converted ap. right after it registers to the 2100 wlc, then you can change the ip of the ap.

Actions

This Discussion

 

 

Trending Topics: Other Wireless Mobility

client could not be authenticated
Network Analysis Module (NAM) Products
Cisco 6500 nam
reason 440 driver failure
Cisco password cracker
Cisco Wireless mode