Aironet APs not joining the 4402 controller

[ethutchinson]

     Got a strange one here.

I have six Aironet a/b/g access points that wont join my 4402 Wireless

Lan Controller. They are getting IP s from my DHCP server. I have

set up the scope with the Vendor description and Option 43 info

that has the ip of the controller embedded. The controller can ping

the APs no problem but when I reboot them they do not join the controller

Any ideas?

[Sandeep Choudhary]

Ok, Your country and AP regualtery domain is matching so it can not be a problem.

Now you can try to reset one AP and try to join again.(Is AP are in one subnet as WLC management IP?).

Also:

it  seem like something is blocking udp 5246 & or 5247. If that AP doesn't join, then something is indeed blocking.

Regards

[ethutchinson]

Well after I reset the AP according to the instructions it is in a constant state of resetting. Here is the output from the boot.

Initializing flashfs...

flashfs[1]: 9 files, 4 directories
flashfs[1]: 0 orphaned files, 0 orphaned directories
flashfs[1]: Total bytes: 15998976
flashfs[1]: Bytes used: 6976512
flashfs[1]: Bytes available: 9022464
flashfs[1]: flashfs fsck took 4 seconds.
flashfs[1]: Initialization complete....done Initializing flashfs.
cisco AIR-AP1242AG-A-K9    (PowerPCElvis) processor (revision A0) with 24566K/8192K bytes of memory.
Processor board ID FTX1120B4HZ
PowerPCElvis CPU at 266Mhz, revision number 0x0950
Last reset from reload
LWAPP image version 3.0.51.0
1 FastEthernet interface

32K bytes of flash-simulated non-volatile configuration memory.
Base ethernet MAC Address: 00:1B:D4:C1:6C:1A
Part Number                          : 73-9925-06
PCA Assembly Number                  : 800-26579-05
PCA Revision Number                  : A0
PCB Serial Number                    : FOC11171ZC7
Top Assembly Part Number             : 800-29232-01
Top Assembly Serial Number           : FTX1120B4HZ
Top Revision Number                  : A0
Product/Model Number                 : AIR-AP1242AG-A-K9  

Press RETURN to get started!

*Mar  1 00:00:06.220: %SYS-5-RESTART: System restarted --
Cisco IOS Software, C1240 Software (C1240-RCVK9W8-M), Version 12.3(11)JX1, RELEASE SOFTWARE (fc1)
Technical Support: http://www.cisco.com/techsupport
Copyright (c) 1986-2006 by Cisco Systems, Inc.
Compiled Mon 17-Jul-06 11:44 by alnguyen
*Mar  1 00:00:07.156: %LINK-3-UPDOWN: Interface FastEthernet0, changed state to up
*Mar  1 00:00:08.156: %LINEPROTO-5-UPDOWN: Line protocol on Interface FastEthernet0, changed state to up
*Mar  1 00:00:25.229: %LWAPP-5-CHANGED: LWAPP changed state to DISCOVERY
*Mar  1 00:00:33.365: %DHCP-6-ADDRESS_ASSIGN: Interface FastEthernet0 assigned DHCP address 192.168.10.3, mask 255.255.255.0, hostna

Translating "CISCO-LWAPP-CONTROLLER.AD.NEWTONMA.GOV"...domain server (192.9.202.207) [OK]

*Mar  1 00:00:46.639: %LWAPP-5-CHANGED: LWAPP changed state to JOIN
*Mar  1 00:00:54.640: LWAPP_CLIENT_ERROR_DEBUG: spamHandleJoinTimer: Did not recieve the Join response

*Mar  1 00:00:54.640: LWAPP_CLIENT_ERROR_DEBUG: No more AP manager IP addresses remain.

*Mar  1 00:01:02.649: LWAPP_CLIENT_ERROR_DEBUG: spamHandleJoinTimer: Did not recieve the Join response

*Mar  1 00:01:02.649: LWAPP_CLIENT_ERROR_DEBUG: No more AP manager IP addresses remain.

*Mar  1 00:01:02.674: %SYS-5-RELOAD: Reload requested by LWAPP CLIENT. Reload Reason: DID NOT GET JOIN RESPONSE.
*Mar  1 00:01:02.674: %LWAPP-5-CHANGED: LWAPP changed state to DOWN
*Mar  1 00:01:07.018: %CDP_PD-4-POWER_OK: Full power - NON_CISCO-NO_CDP_RECEIVED inline power sourceXmodem file system is available.
flashfs[0]: 9 files, 4 directories
flashfs[0]: 0 orphaned files, 0 orphaned directories
flashfs[0]: Total bytes: 15998976
flashfs[0]: Bytes used: 6976512
flashfs[0]: Bytes available: 9022464
flashfs[0]: flashfs fsck took 28 seconds.
Base ethernet MAC Address: 00:1b:d4:c1:6c:1a
Initializing ethernet port 0...
Reset ethernet port 0...
Reset done!
ethernet link up, 100 mbps, full-duplex
Ethernet port 0 initialized: link is up

It looks like the option 43 stuff is not getting to the ap. It was before because the controller ip was getting installed as you can see from my previous post.

[ethutchinson]

How do you know udp 5246 and 5247 are being blocked? If that is the case then where does the ap need to communicate to over those ports?

[Sandeep Choudhary]

I asked you because something is blocking AP to join WLC.

Just for info:

The CAPWAP UDP ports 5246 and 5247 (similar to the LWAPP UDP ports 12222 and 12223) are enabled and are not blocked by an intermediate device that could prevent an access point from joining the controller.

The access points use a random UDP source port to reach these destination ports on the controller. In controller software release 5.2, LWAPP was removed and replaced by CAPWAP, but if you have a new out-of-the-box access point, it could try to use LWAPP to contact the controller before it downloads the CAPWAP image from the controller.

Regards

[Scott Fella]

Place the AP on the same subnet as the WLC management and see if the AP joins.  If not, post the output from the console of the AP, but post everything from rebooting until about 5 minutes worth of data.

Thanks,

Scott

Help out other by using the rating system and marking answered questions as "Answered"

[Sandeep Choudhary]

HI,

This is the output from console port,

*Mar  1 00:01:02.649: LWAPP_CLIENT_ERROR_DEBUG: spamHandleJoinTimer: Did not recieve the Join response 
*Mar  1 00:01:02.649: LWAPP_CLIENT_ERROR_DEBUG: No more AP manager IP addresses remain.

This is a clear indication that the LAP is not part of the AP authorization list on the controller.

You can view the status of the AP authorization list using this command:

(Cisco Controller) >show auth-list

Authorize APs against AAA ....................... enabled

Allow APs with Self-signed Certificate (SSC) .... disabled

Via GUI: Security > AP Policies

Solution is to:  To add an LAP to the AP authorization list, use the config auth-list add mic command.

Regards

Dont forget to rate helpful posts

[ethutchinson]

Can I add them via the GUI?

[ethutchinson]

I take it is the base ethernet mac address.

[Scott Fella]

You can add the base Mac on the GUI or CLI.

Sent from Cisco Technical Support iPhone App

[Sandeep Choudhary]

HI You can do by GUI or CLI:

GUI:

Login to WLC:

Go to Security > AP Policies, enter the AP MAC address under Add AP to Authorization List and click Add

In my above post I told u about CLI way to add AP mac.

Regards

Dont forget to rate helpful posts

[KAMAL MISHRA]

thanks sandeep.

[Sandeep Choudhary]

Is Now AP joining to WLC ??

If this is resolved then please mark this question as answered, it may help others.

Reagrds

Dont forget to rate helpful posts

[KAMAL MISHRA]

ok i will do these steps in gui...

[Sandeep Choudhary]

Hi Kamal,

I dont know. is you are facing this issue or this guy ethutchinson ?

If you are facing the similier or bit diff issue then you can create a new thread with problem description.

** I also replied on your personal message.

Regards

[KAMAL MISHRA]

Ealier i have tried but it will not work and its a remote issue i can not take console right now but i think it will resolve my issue because i have not tried GUI steps.