How to Assign Static ip to lightweight Access Point (LAP) 2602i-c-k9 before Registering to Controller (WLC)

[Rasika Nayanajith]

See below, you need to replace "lwapp" keyword with "capwap"

http://wirelessccie.blogspot.com.au/2009/08/configure-your-lwapp-ap-from-ap-cli.html

Refer this as well for some more detail about AP Registration

http://mrncciew.com/2013/03/17/ap-registration/

HTH

Rasika

**** Pls rate all useful responses ****

[Abhishek Abhishek]

Workaround 1:

1. configure the AP to boot the recovery image:
ap#debug lwapp console cli (use "debug capwap console cli" if running 5.2 or above)
ap#dir flash:/ (look for a folder with "rcvk9w8" in its name)
ap#configure terminal
ap(config)#boot system flash:/c1250-rcvk9w8-mx/c1250-rcvk9w8-mx

2. disconnect the AP from the LAN (e.g. shutdown the switchport)

3. reload the AP

4. from the AP console, clear the LWAPP (CAPWAP) configuration:

ap#clear lwapp private-config

5. You can now enter the "lwapp ap" "Ease of Deploy" CLI commands.

Workaround 2:

1. Disconnect the AP from the LAN (e.g. shutdown the switchport)

2. ap#debug lwapp console cli (use "debug capwap console cli" if running 5.2 or above)

3. ap#write erase

4. ap#reload

5. After reloading, you can now use the "lwapp ap" (or "capwap ap")
"Ease of Deploy" CLI commands.

Workaround 3:

ap#test lwapp controller ip a.b.c.d [w.x.y.z] (or "test capwap controller")

[Prakash Parvathala]

Please see the below similar discussion

https://supportforums.cisco.com/discussion/11056351/how-assign-static-ip-lightweight-access-point-1131ag-registering-controller

[sobhardw]

Following are the commands :

AP#lwapp ap ip address

AP#lwapp ap ip default-gateway

AP#lwapp ap controller ip address

AP#lwapp ap hostname

let me know If the solution is useful.

[Abhishek Abhishek]

The LWAPP AP goes through this process on startup for Layer 3 mode:

1. The LAP boots and DHCPs an IP address if it was not previously assigned a static IP address.

2. The LAP sends discovery requests to controllers through the various discovery algorithms and builds a controller list. Essentially, the LAP learns as many management interface addresses for the controller list as possible via:

   1. DHCP option 43 (good for global companies where offices and controllers are on different continents)

   2. DNS entry for cisco-capwap-controller (good for local businesses - can also be used to find where brand new APs join)

      Note: If you use CAPWAP, make sure that there is a DNS entry for cisco-capwap-controller.

   3. Management IP addresses of controllers the LAP remembers previously

   4. A Layer 3 broadcast on the subnet

   5. Over the air provisioning

   6. Statically configured information