06-05-2007 07:52 AM - edited 07-03-2021 02:10 PM
I've got a big stack of statically-addressed autonomous AP1130s which I'm converting to LWAPP. Unfortunately, the LWAPP conversion tool loads the AP with the IOS_STATIC_IP_ADDR from env_vars, not the address from the running config.
So my question is, if I simply delete this file and reload, will it boot up correctly and recreate the file from the data in the running config? Or is there any way to directly edit the file, or overwrite it via tftp?
My goal is to be able to convert the AP without having to pull it down out of the ceiling and console into it. If it were just 1 or 2, no problem... for a whole campus, I need a working hands-off solution.
06-05-2007 02:39 PM
gamccall,
i have had a variety of results from upgrading to LWAPP, mainly the fact that if they had a static IP address did not cause a problem. Once the AP's have joined the controller you can simply click on the details of the AP and de-select the "AP Static IP" tick box and leave it to DHCP on next reload.
On other occassions (like today) i had to clear the configs once upgraded and leave them to DHCP.
Post back your results
Cheers
*Pls rate all useful posts
06-10-2007 09:45 PM
Go ahead and delete it..write erase as well and reload...should work fine. Also make sure your switch port is configured as an access point for the respective vlan.
Discover and save your favorite ideas. Come back to expert answers, step-by-step guides, recent topics, and more.
New here? Get started with these tips. How to use Community New member guide