Cisco Support Community
cancel
Showing results for 
Search instead for 
Did you mean: 
New Member

LAP1131AG in endless Join loop (WCS 5.2.130.0, WLC 5.2.178.0)

I have som Aironet LAP1131AG accesspoints, that after a upgrade to WCS 5.2 (including upgrade of WLC) will not rejoin the controller.

I have attached a dump of the console. The accesspoints will upgrade the image, if they are hardreset (by holding down reset for some seconds while rebooting), but they will end up i an endless quest to join (last good message is CAPWAP changed state to CFG)...

We have 100+ accesspoints that are unaffected by the upgrade, but 2 accesspoints are giving me the same problem.

Any ideas as what to try ?

2 ACCEPTED SOLUTIONS

Accepted Solutions

Re: LAP1131AG in endless Join loop (WCS 5.2.130.0, WLC 5.2.178.0

- I would recommend that you use a browser to connect to your AP. The first page after logon has a nice summary of the status of all interfaces.

- For the WCS error: are you using the same SNMP strings and versions on WCS and on the AP? They must match (but I have never tried to add an autonomous AP to WCS).

Re: LAP1131AG in endless Join loop (WCS 5.2.130.0, WLC 5.2.178.0

I would say that it's time to open up a TAC.

16 REPLIES
Hall of Fame Super Gold

Re: LAP1131AG in endless Join loop (WCS 5.2.130.0, WLC 5.2.178.0

Can the LWAP AP ping the management IP Address of the WLC? If yes, please enter the command in enable mode on the AP: lwapp ap controller ip address

Hope this helps.

New Member

Re: LAP1131AG in endless Join loop (WCS 5.2.130.0, WLC 5.2.178.0

Ths accesspoint can ping the management IP (The one defined i CISCO-LWAP/CAPWAP-CONTROLLER in DNS), but it is unable to ping the ap-management interface. However this is the same for all my APs also the ones that are OK.

When (from an enabled prompt) trying the command lwapp ap controller ip addresse I get:

ERROR!!! Command is disabled.

I noticed that the difference from an OK AP and a failing AP is the following loglines just after CAPWAP change to CFG:

*Apr 22 06:57:58.188: %CAPWAP-5-CHANGED: CAPWAP changed state to CFG

RSSI IDB null

RSSI IDB null

*Apr 22 06:58:16.188: %CAPWAP-3 ERRORLOG: Retransmission count for packet exceeded max(UNKNOWN_MESSAGE_TYPE (5)., 1)

After that the failing AP goes to DISCOVER mode and the OK AP (which does not have the errorlines) says CAPWAP changed state to UP.

That that give anyone a clue as to where to search?

Hall of Fame Super Silver

Re: LAP1131AG in endless Join loop (WCS 5.2.130.0, WLC 5.2.178.0

Since you got the ERROR!!! Command is disabled, that AP actually had joined the wlc initially. I would think that maybe the 2 ap's didn't fully upgrade or the upgrade got corrupted. You might just have to revert thoses 2 back to IOS and then back to LWAPP.

-Scott
*** Please rate helpful posts ***
New Member

Re: LAP1131AG in endless Join loop (WCS 5.2.130.0, WLC 5.2.178.0

I tend to agree, that the AP does join, but something fails in the CFG state, and therefore the AP automatically removes itself or is removed from the WLC.

I have attached a console-log from one of the accesspoints where it is forced to boot from the recovery image.

It then joins the WLC (and it shows in the WLC interface as upgrading image), upgrades the image, but when booting the new image it again fails in CFG state.

I'm really have no clue as to what is going on...

Hall of Fame Super Silver

Re: LAP1131AG in endless Join loop (WCS 5.2.130.0, WLC 5.2.178.0

I only see that when the upgrade got corrupted on the LAP. You will need to convert it to IOS and then back to LWAPP. What you can try is to load the rcv image back on. If you console into the lap and hold the reset button for about 20 seconds, it should show you the file name the LAP is trying to find via tftp. You can look at this link:

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

-Scott
*** Please rate helpful posts ***
Hall of Fame Super Gold

Re: LAP1131AG in endless Join loop (WCS 5.2.130.0, WLC 5.2.178.0

Hi Michael,

You will never be able to ping the AP-Manager IP Address.

Can you please post the "dir" output?

How many AP's can your WLC control and how many AP's are there now in?

New Member

Re: LAP1131AG in endless Join loop (WCS 5.2.130.0, WLC 5.2.178.0

Hi

We have 2 WS-SVC-WISM-1-K9 modules. Each able to handle 300 AP's. At the moment only one of the modules are in real production. Each module contains two WLC's (WISM controllers) each capable of 150 APs. At the moment we have 32 AP on WISM-1A and 75 AP on WISM-1B. All WiSM controllers are managed from a WCS with 500 APs licensed at the moment.

Output from dir:

AP001d.e556.bf84#dir

Directory of flash:/

3 -rwx 88598 Apr 22 2009 15:00:14 +00:00 event.log

4 drwx 128 Jan 1 1970 00:02:01 +00:00 c1130-rcvk9w8-mx

9 drwx 256 Apr 22 2009 12:15:03 +00:00 c1130-k9w8-mx.124-18a.JA1

7 -rwx 5144 Apr 22 2009 15:18:20 +00:00 private-multiple-fs

8 -rwx 232 Apr 22 2009 15:18:20 +00:00 env_vars

15998976 bytes total (9431040 bytes free)

In the last days I have tried deleting env_vars, private-multiple-fs and event.log. It seemed to remove the hostname previously configured on the AP, but didn't solve the problem...

Hall of Fame Super Gold

Re: LAP1131AG in endless Join loop (WCS 5.2.130.0, WLC 5.2.178.0

Hi Michael,

Thanks for the output.

I propose for you to delete the LWAP image (delete /f /r flash:c1130-k9w8-mx.124-18a.JA1), reboot the AP, and during the search for a WLC controller, delete the LWAP configuration (clear lwapp private), reboot the AP again and when the AP's searching for the WLC, force it to the WLC of your choice "lwapp ap controller ip address ".

Hope this will work for you.

New Member

Re: LAP1131AG in endless Join loop (WCS 5.2.130.0, WLC 5.2.178.0

Hi,

I have now tried to hardreset the AP, and load an autonomious (non LWAP image).

I was able to load the image, and can now talk (via telnet and console) to the AP.

What I notice is that the AP seem to not have any Dot11Radio interfaces. show interfaces does not mention any interfaces but BVI1 and FastEthernet0.

When tryint to add the autonomious AP using the WCS, I get:

Autonomous AP Failed to add device to WCS Reason: SNMP operation to Device failed: Too few VarBinds in response

Could my problem be that I'm experiencing 2 APs (of 100+ deployed) that have somehow lost their dot11 radios ?

Regards and thanks for the help so far

-Michael

Re: LAP1131AG in endless Join loop (WCS 5.2.130.0, WLC 5.2.178.0

- I would recommend that you use a browser to connect to your AP. The first page after logon has a nice summary of the status of all interfaces.

- For the WCS error: are you using the same SNMP strings and versions on WCS and on the AP? They must match (but I have never tried to add an autonomous AP to WCS).

New Member

Re: LAP1131AG in endless Join loop (WCS 5.2.130.0, WLC 5.2.178.0

Hi,

I guess this screendump says it all. Radio0 and Radio1 is marked as not installed.. Guess it is a hardware error... An AP without radios is not of much use is it ;-)

Thanks a lot to all who helped :-)

Re: LAP1131AG in endless Join loop (WCS 5.2.130.0, WLC 5.2.178.0

I would say that it's time to open up a TAC.

New Member

Re: LAP1131AG in endless Join loop (WCS 5.2.130.0, WLC 5.2.178.0

Are the two that will not join on a different network segment. If so check to see if UDP ports 5246 &5247 are allowed. It use to be lwap udp 12222 12223.

New Member

Re: LAP1131AG in endless Join loop (WCS 5.2.130.0, WLC 5.2.178.0

The disfunctional APs are on networks that has other APs that are functional.

Hall of Fame Super Gold

Re: LAP1131AG in endless Join loop (WCS 5.2.130.0, WLC 5.2.178.0

Hi Michael,

Did you try to force the AP to the WLC of your choice "lwapp ap controller ip address "?

New Member

Re: LAP1131AG in endless Join loop (WCS 5.2.130.0, WLC 5.2.178.0

Hi

I went for the IOS reinstall with a non Lightweight image route, as the AP apparently did join the WLC, but disassociated instead of turning the radios on.

My guess is that the lack of functional radios messed the join process up.

I have now opened a case with my local cisco supplier :-)

654
Views
0
Helpful
16
Replies
CreatePlease to create content