topic Re: LWAPP error and change status to Discovery in Wireless

LWAPP error and change status to Discovery

stanleyworks — Sun, 04 Jul 2021 00:11:10 GMT

Hello,

I have a LWAPP AP keep on up and down.

The following is error message I got from the log.

%LWAPP-3-CLIENTERRORLOG: Retransmission count for packet exceeded max(ECHO_REQUE

ST, 1)

%LWAPP-3-CLIENTERRORLOG: GOING BACK TO DISCOVER MODE

%WIDS-6-DISABLED: IDS Signature is removed and disabled.

%LWAPP-5-CHANGED: LWAPP changed state to DISCOVERY

COW1242-05#

Re: LWAPP error and change status to Discovery

dennischolmes — Wed, 18 Feb 2009 16:56:56 GMT

The AP is not finding the controller. Try using option 43 or dns resolution for locating the LWAPP controller.

Re: LWAPP error and change status to Discovery

stanleyworks — Wed, 18 Feb 2009 17:00:04 GMT

It does report back to the controller and allow user to connect. however, it stay for about 5 minutes and go back to discovery, and keep repeating...

Re: LWAPP error and change status to Discovery

dennischolmes — Wed, 18 Feb 2009 17:07:47 GMT

Look at power and network connectivity issues. Also look to the length of the cable to the AP.

Re: LWAPP error and change status to Discovery

Leo Laohoo — Thu, 19 Feb 2009 00:19:06 GMT

Weird. This is the 3rd case I've seen for this week alone. What's the firmware of your WLC, AP (include the RCV and the LWAPP image please)?

Re: LWAPP error and change status to Discovery

Leo Laohoo — Mon, 16 Mar 2009 05:49:44 GMT

Hey Stanley,

Is this problem still ongoing?

Re: LWAPP error and change status to Discovery

Tyrone Van Der Haar — Mon, 07 Sep 2009 16:27:41 GMT

Hi I'm experiencing the same problem(same error spittig out) my firmware level is at 4.2.130

Anymore news on this problem would be greatly appreciated!

Tyrone

Re: LWAPP error and change status to Discovery

Leo Laohoo — Mon, 07 Sep 2009 22:07:33 GMT

Hi Tyronne,

Has the AP ever discovered the WLC before or is this a new AP out from a box?

Re: LWAPP error and change status to Discovery

Tyrone Van Der Haar — Tue, 08 Sep 2009 06:28:29 GMT

Yes the AP has registered once before but never again.

I also had an issue where the local support team plugged this AP in to a POE switch and plugged the power cord in aswell! But it doen't seem to be damaged physically.

Re: LWAPP error and change status to Discovery

dennischolmes — Tue, 08 Sep 2009 09:59:42 GMT

Is the regulatory domain correct? Is the time and date correct on the controller? Was this AP converted or new (SSC or MIC)? These are some basic starting points.

Re: LWAPP error and change status to Discovery

Tyrone Van Der Haar — Tue, 08 Sep 2009 10:34:24 GMT

The regulatory domain is correct the time and date is synced with NTP and is correct this is a new LAP.

These are the errors I'm getting

%LWAPP-5-CHANGED: LWAPP changed state to CFG

%LWAPP-3-CLIENTERRORLOG: Process Secure Msg: decrypting with CCM returned failure

%LWAPP-3-CLIENTERRORLOG: Config Command: error processing secure message

%LWAPP-5-CHANGED: LWAPP changed state to DOWN

%LWAPP-3-CLIENTEVENTLOG: AP has joined controller WiSM-D5-B

%LWAPP-3-CLIENTERRORLOG: Retransmission count for packet exceeded max(ECHO_REQUEST

, 1)

%LWAPP-3-CLIENTERRORLOG: GOING BACK TO DISCOVER MODE

%LWAPP-5-CHANGED: LWAPP changed state to DISCOVERY

%LINK-3-UPDOWN: Interface Dot11Radio0, changed state to up

%LINK-5-CHANGED: Interface Dot11Radio1, changed state to reset

%LINK-3-UPDOWN: Interface Dot11Radio1, changed state to up

%LINK-5-CHANGED: Interface Dot11Radio0, changed state to reset

%LINEPROTO-5-UPDOWN: Line protocol on Interface Dot11Radio1, changed state to up

%LINK-3-UPDOWN: Interface Dot11Radio0, changed state to up

%LINEPROTO-5-UPDOWN: Line protocol on Interface Dot11Radio0, changed state to up

%CDP_PD-4-POWER_OK: Full power - NEGOTIATED inline power source

Re: LWAPP error and change status to Discovery

Leo Laohoo — Tue, 08 Sep 2009 21:03:32 GMT

How many APs can the WLC WiSM-D5-B support and how many APs have joined?

What is the model of the AP?

What is the firmware of the WLC?

Have you tried converting it again from autonomous to LWAP?

Re: LWAPP error and change status to Discovery

ddmoe — Thu, 10 Sep 2009 00:52:23 GMT

I had a few APs that would reboot periodically. Since upgrading to code level 4.2.207 all the rebooting issues have gone away. In the resolved caveats section of the release notes it mentions that the watchdog timer timeout issue is resolved with version 4.2.207.

Re: LWAPP error and change status to Discovery

Tyrone Van Der Haar — Thu, 10 Sep 2009 18:06:56 GMT

It's WiSM WLC so I think 300 AP's are supported???

Model 1242

firmware 4.2.130

This AP has always been LWAP

Re: LWAPP error and change status to Discovery

Tyrone Van Der Haar — Thu, 10 Sep 2009 18:09:34 GMT

Interesting I might have to go back to the release notes for 4.2.130 and look out for the watch dog timer caveat!

strangely enough I have 50 AP's connected without any problem just have this problem with about 5 LAP.

Re: LWAPP error and change status to Discovery

Leo Laohoo — Thu, 10 Sep 2009 23:06:01 GMT

How many APs can the WLC WiSM-D5-B support and how many APs have joined?

What the bl00dy hell am I talking about??? I probably mean, how many APs have already joined the WiSM? WiSMs can support 150 APs per side or 300 per blade.

Re: LWAPP error and change status to Discovery

Tyrone Van Der Haar — Tue, 15 Sep 2009 10:58:26 GMT

Update:

I deleted the following directories/files

c1240-k9w8-mx.124-10b.JA4

lwapp_reap.cfg

mutiple_fs(something can't remember the exact name)

and everything came back.

I was forced to move the AP so I could get to it's console because it kept rebooting iteslf with the error mentioned above, but I'm going to move it again to it's place and see weather I get the same problem again.