LWAPP 1252 not associating to WLC

[Michael Garcia]

I have a 1252 LAP that just won't associate to the WLC. It won't pull an IP address from my DHCP server either. I've tried a number of things to get this AP to associate but it just won't. Is it just a Bad Unit that needs to be replaced? Someone please help.

Note that in the show cdp neighbor output it shows that this is NOT operating as a "Transbridge".

Capability Codes: R - Router, T - Trans Bridge, B - Source Route Bridge
                  S - Switch, H - Host, I - IGMP, r - Repeater, P - Phone,
                  D - Remote, C - CVTA, M - Two-port Mac Relay

Device ID        Local Intrfce     Holdtme    Capability  Platform  Port ID
pv_3-1_sw1.phaznet.local
                 Gig 0/48          150              S I   WS-C4506  Fas 3/32
AP0025.4506.5532 Gig 0/43          150               T    AIR-LAP12 Gig 0
AP0025.45cf.c3a2 Gig 0/33          168               T    AIR-LAP12 Gig 0
AP0025.45cf.c3b2 Gig 0/39          156               T    AIR-LAP12 Gig 0
AP0026.cbd2.bbf0 Gig 0/32          169                    AIR-LAP12 Gig 0  <--- This is the offending AP.
AP0025.45cf.c40a Gig 0/42          175               T    AIR-LAP12 Gig 0

I've also included the show cdp neighbor detail output.

Device ID: AP0026.cbd2.bbf0
Entry address(es):
Platform: cisco AIR-LAP1252AG-A-K9  ,  Capabilities:
Interface: GigabitEthernet0/32,  Port ID (outgoing port): GigabitEthernet0
Holdtime : 154 sec

Version :
Cisco IOS Software, C1250 Software (C1250-RCVK9W8-M), Version 12.4(10b)JA1, RELEASE SOFTWARE (fc2)
Technical Support: http://www.cisco.com/techsupport
Copyright (c) 1986-2008 by Cisco Systems, Inc.
Compiled Wed 30-Jan-08 12:11 by prod_rel_team

advertisement version: 2
Duplex: full
Power drawn: 13.000 Watts
Power request id: 5096, Power management id: 0
Power request levels are:13000 0 0 0 0
Management address(es):

[Leo Laohoo]

What is the firmware of your WLC?

Console into the AP and enter the command "lwapp ap ip address" to enter IP address statically.

If it still won't join the controller, enter the second command "lwapp ap controller IP address ".

[Michael Garcia]

Firmware version is 5.2.157.0

System Information
Manufacturer's Name.............................. Cisco Systems Inc.
Product Name..................................... Cisco Controller
Product Version.................................. 6.0.196.159
RTOS Version..................................... 6.0.196.159
Bootloader Version............................... 4.2.112.0
Emergency Image Version.......................... 5.2.157.0
Build Type....................................... DATA + WPS

I'll have to schedule going to the location to console into the LWAPP. Thank you for your suggestion. I'll let you know what comes of it.

Michael

[Serge Yasmine]

when AP boots up, it will request an IP address. AP will not join any WLC and will not send discovery requests if it doesn't have an IP address.

Make sure AP is plugged to a switchport correctly configured with an access VLAN and where that VLAN clients (AP in this case) will be able to reach the DHCP server via broadcast.

[Nicolas Darchis]

If the AP cannot get an ip on that port, I suspect something is wrong.

An easy test is to swap that AP with another one. So that the AP with the problem is plugged on another switchport with another cable that we know both work. That will isolate either the AP itself either the cable or switchport config.

Best regards,

Nicolas

===

Please rate answers that you find useful

[dselfridge]

Hi,

Just a 'for info' post. I was following these threads with a similar issue.

My customer wanted to upgrade an Autonomous 1252 to Lightwieght. We did that and the AP wouldn't join the controller (2106 in this case).

Now I was working with the customer over the phone and could not see the console or GUI for the AP & Controller.

It wasn't until I got him to send me the logs from the controller that I spotted the WLC was setup for the wrong regulatory domain (US - but AP's were ETSI). Very simple problem to resolve from there.

Just be aware that most problems can be very simple but difficult to spot. Especially if you weren't involved with the setup from the outset.

Good luck!