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

Welcome to Cisco Support Community. We would love to have your feedback.

For an introduction to the new site, click here. If you'd prefer to explore, try our test area to get started. And see here for current known issues.

New Member

Cisco LWAPP 2602e can't join the controller

i have a problem with a 2602e access point that he wouldn't join the controller (wlc 8510)

i gave him the image --> p3g2-k9w8-tar.152-2.JB.tar

we have a lot of capwap ap's but ive never had this problem before

*Jul 19 07:53:59.999: %DTLS-5-SEND_ALERT: Send FATAL : Close notify Alert to 10.45.29.101:5246

*Jul 19 07:54:00.059: %LWAPP-3-CLIENTERRORLOG: LWAPP LED Init: incorrect led state 255

*Jul 19 07:54:00.067: %LINK-5-CHANGED: Interface Dot11Radio0, changed state to administratively down

*Jul 19 07:54:00.095: %LINK-6-UPDOWN: Interface Dot11Radio0, changed state to up

*Jul 19 07:54:01.067: %LINEPROTO-5-UPDOWN: Line protocol on Interface Dot11Radio0, changed state to down

*Jul 19 07:54:01.099: %LINK-6-UPDOWN: Interface Dot11Radio0, changed state to down

*Jul 19 07:54:01.107: %LINK-5-CHANGED: Interface Dot11Radio0, changed state to reset

*Jul 19 07:54:02.127: %LINK-6-UPDOWN: Interface Dot11Radio0, changed state to up

*Jul 19 07:54:03.127: %LINEPROTO-5-UPDOWN: Line protocol on Interface Dot11Radio0, changed state to up

*Jul 19 07:54:10.095: %CAPWAP-3-ERRORLOG: Selected MWAR 'WLC041D1M120101'(index 0).

*Jul 19 07:54:10.095: %CAPWAP-3-ERRORLOG: Go join a capwap controller

*Jul 19 07:54:10.000: %CAPWAP-5-DTLSREQSEND: DTLS connection request sent peer_ip: 10.45.29.101 peer_port: 5246

*Jul 19 07:54:10.003: %LINK-6-UPDOWN: Interface Dot11Radio0, changed state to down

*Jul 19 07:54:10.187: %LINK-5-CHANGED: Interface Dot11Radio0, changed state to reset

*Jul 19 07:54:10.199: %CAPWAP-5-DTLSREQSUCC: DTLS connection created sucessfully peer_ip: 10.45.29.101 peer_port: 5246

*Jul 19 07:54:10.199: %CAPWAP-5-SENDJOIN: sending Join Request to 10.45.29.101

*Jul 19 07:54:10.199: %CAPWAP-3-ERRORLOG: Invalid event 10 & state 5 combination.

*Jul 19 07:54:10.199: %CAPWAP-3-ERRORLOG: CAPWAP SM handler: Failed to process message type 10 state 5.

*Jul 19 07:54:11.003: %LINEPROTO-5-UPDOWN: Line protocol on Interface Dot11Radio0, changed state to down

*Jul 19 07:54:11.031: %LINK-6-UPDOWN: Interface Dot11Radio0, changed state to up

*Jul 19 07:54:11.039: %LINK-6-UPDOWN: Interface Dot11Radio0, changed state to down

*Jul 19 07:54:11.047: %LINK-5-CHANGED: Interface Dot11Radio0, changed state to reset

*Jul 19 07:54:12.067: %LINK-6-UPDOWN: Interface Dot11Radio0, changed state to up

*Jul 19 07:54:13.067: %LINEPROTO-5-UPDOWN: Line protocol on Interface Dot11Radio0, changed state to up

*Jul 19 07:54:15.199: %CAPWAP-5-SENDJOIN: sending Join Request to 10.45.29.101

*Jul 19 07:54:15.203: %LINK-6-UPDOWN: Interface Dot11Radio0, changed state to down

*Jul 19 07:54:15.211: %LINK-5-CHANGED: Interface Dot11Radio0, changed state to reset

*Jul 19 07:54:16.203: %LINEPROTO-5-UPDOWN: Line protocol on Interface Dot11Radio0, changed state to down

*Jul 19 07:54:16.231: %LINK-6-UPDOWN: Interface Dot11Radio0, changed state to up

*Jul 19 07:54:17.231: %LINEPROTO-5-UPDOWN: Line protocol on Interface Dot11Radio0, changed state to up

*Jul 19 07:55:00.155: %MESH-3-TIMER_EXPIRED: Mesh Lwapp join timer expired

*Jul 19 07:55:00.155: %MESH-3-TIMER_EXPIRED: Mesh Lwapp join failed expired

*Jul 19 07:55:00.155: %MESH-6-LINK_UPDOWN: Mesh station 4c4e.3563.a6bc link Down

*Jul 19 07:55:02.155: %LINK-6-UPDOWN: Interface BVI1, changed state to down

*Jul 19 07:55:07.655: %LINEPROTO-5-UPDOWN: Line protocol on Interface BVI1, changed state to down

*Jul 19 07:55:09.999: %DTLS-5-SEND_ALERT: Send FATAL : Close notify Alert to 10.45.29.101:5246

*Jul 19 07:55:13.071: %LINK-5-CHANGED: Interface Dot11Radio0, changed state to administratively down

*Jul 19 07:55:13.087: %LINK-6-UPDOWN: Interface Dot11Radio0, changed state to up

*Jul 19 07:55:14.071: %LINEPROTO-5-UPDOWN: Line protocol on Interface Dot11Radio0, changed state to down

*Jul 19 07:55:14.111: %LINK-6-UPDOWN: Interface Dot11Radio0, changed state to down

*Jul 19 07:55:14.119: %LINK-5-CHANGED: Interface Dot11Radio0, changed state to reset

*Jul 19 07:55:15.139: %LINK-6-UPDOWN: Interface Dot11Radio0, changed state to up

*Jul 19 07:55:16.139: %LINEPROTO-5-UPDOWN: Line protocol on Interface Dot11Radio0, changed state to up

*Jul 19 07:55:23.091: %LINK-6-UPDOWN: Interface Dot11Radio0, changed state to down

*Jul 19 07:55:23.099: %LINK-5-CHANGED: Interface Dot11Radio0, changed state to reset

*Jul 19 07:55:24.091: %LINEPROTO-5-UPDOWN: Line protocol on Interface Dot11Radio0, changed state to down

*Jul 19 07:55:24.119: %LINK-6-UPDOWN: Interface Dot11Radio0, changed state to up

*Jul 19 07:55:25.119: %LINEPROTO-5-UPDOWN: Line protocol on Interface Dot11Radio0, changed state to up

*Jul 19 07:55:33.091: %LINK-6-UPDOWN: Interface Dot11Radio0, changed state to down

*Jul 19 07:55:33.099: %LINK-5-CHANGED: Interface Dot11Radio0, changed state to reset

*Jul 19 07:55:34.091: %LINEPROTO-5-UPDOWN: Line protocol on Interface Dot11Radio0, changed state to down

*Jul 19 07:55:34.119: %LINK-6-UPDOWN: Interface Dot11Radio0, changed state to up

*Jul 19 07:55:35.119: %LINEPROTO-5-UPDOWN: Line protocol on Interface Dot11Radio0, changed state to up

*Jul 19 07:55:40.539: %MESH-6-CAPWAP_RESTART: Mesh Capwap re-started

*Jul 19 07:55:42.539: %LINK-6-UPDOWN: Interface BVI1, changed state to up

*Jul 19 07:55:43.087: %CAPWAP-3-ERRORLOG: Invalid event 29 & state 4 combination.

*Jul 19 07:55:43.087: %CAPWAP-3-ERRORLOG: SM handler: Failed to process timer message. Event 29, state 4

*Jul 19 07:55:43.087: %CAPWAP-3-ERRORLOG: Failed to handle timer message.

*Jul 19 07:55:43.087: %CAPWAP-3-ERRORLOG: Failed to process timer message.

*Jul 19 07:55:43.539: %LINEPROTO-5-UPDOWN: Line protocol on Interface BVI1, changed state to up

*Jul 19 07:55:45.607: %LINK-5-CHANGED: Interface Dot11Radio0, changed state to administratively down

*Jul 19 07:55:46.607: %LINEPROTO-5-UPDOWN: Line protocol on Interface Dot11Radio0, changed state to down

6 REPLIES
Hall of Fame Super Silver

Re: Cisco LWAPP 2602e can't join the controller

You should use this code


WIRELESS LAN RECOVERY
ap3g2-rcvk9w8-tar.124-25e.JA1.tar


Sent from Cisco Technical Support iPhone App

-Scott
*** Please rate helpful posts ***

Re: Cisco LWAPP 2602e can't join the controller

It looks like that AP came as a MESH Mode AP. Add the MAC address of that ap to the WLC in the Mac filter list. The ap should then join and you can change it from MESH to normal

Steve

Sent from Cisco Technical Support iPhone App

HTH, Steve ------------------------------------------------------------------------------------------------ Please remember to rate useful posts, and mark questions as answered
New Member

your answer was successful

your answer was successful resolved my problem, you are my superstar!

thank you very much!

Bronze

Re: Cisco LWAPP 2602e can't join the controller

stephen is correct. add its base radio mac to wlc

Sent from Cisco Technical Support iPad App

New Member

Re: Cisco LWAPP 2602e can't join the controller

Thx for your help problem is solved (i've added the mac address of the ap)

But why came the ap in the bridge mode?

what is the difference between the both leightweight images..

p3g2-k9w8-tar.152-2.JB.tar and  ap3g2-rcvk9w8-tar.124-25e.JA1.tar

Hall of Fame Super Silver

Re: Cisco LWAPP 2602e can't join the controller

One is mesh the other is non mesh. So changing the code or setting up the ap as mesh would fix your issue. Either could of been the wrong ap purchased or the wrong image placed on the ap. the thing now is that you have to put the ap in local mode and delete the mesh files in flash. This will prevent the ap from still thinking its mesh.

Sent from Cisco Technical Support iPhone App

-Scott
*** Please rate helpful posts ***
1757
Views
0
Helpful
6
Replies