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. And see here for current known issues.

New Member

AIR-CT2504-K9 and AIR-CAP3502I-A-K9 - Unable to Join the controller

Hi Everyone,

I am having a problem with some of my access points AIR-CAP3502I-A-K9 . My controller has 25 licenses for 25 APs but only 9 are joined right now. The other ones can't join. And below is the errors i read from the Console.

Controller is  AIR-CT2504-K9

Software Version7.0.220.0


Can you guys tell me what is wrong here?

Thanks,

*Jul 26 15:13:34.745: %LINK-6-UPDOWN: Interface Dot11Radio0, changed state to up

*Jul 26 15:13:35.746: %LINEPROTO-5-UPDOWN: Line protocol on Interface Dot11Radio0, changed state to up

*Jul 26 15:13:43.673: %CAPWAP-3-ERRORLOG: Go join a capwap controller

*Jul 26 15:13:44.000: %CAPWAP-5-DTLSREQSEND: DTLS connection request sent peer_ip: 192.168.10.30 peer_port: 5246

*Jul 26 15:13:44.003: %LINK-6-UPDOWN: Interface Dot11Radio0, changed state to down

*Jul 26 15:13:44.009: %LINK-5-CHANGED: Interface Dot11Radio0, changed state to reset

*Jul 26 15:13:44.415: %CAPWAP-5-DTLSREQSUCC: DTLS connection created sucessfully peer_ip: 192.168.10.30  peer_port: 5246

*Jul 26 15:13:44.415: %CAPWAP-5-SENDJOIN: sending Join Request to 192.168.10.30

*Jul 26 15:13:44.418: %DTLS-5-ALERT: Received WARNING : Close notify alert from 192.168.10.30

*Jul 26 15:13:44.418: %DTLS-5-SEND_ALERT: Send FATAL : Close notify Alert to 192.168.10.30:5246

*Jul 26 15:13:44.418: %CAPWAP-3-ERRORLOG: Go join a capwap controller

*Jul 26 15:13:44.000: %CAPWAP-5-DTLSREQSEND: DTLS connection request sent peer_ip: 192.168.10.30 peer_port: 5246

*Jul 26 15:13:44.418: %CAPWAP-5-DTLSREQSUCC: DTLS connection created sucessfully peer_ip: 192.168.10.30 peer_port: 5246

*Jul 26 15:13:44.418: %CAPWAP-5-SENDJOIN: sending Join Request to 192.168.10.30

*Jul 26 15:13:44.421: %DTLS-5-ALERT: Received WARNING : Close notify alert from 192.168.10.30

*Jul 26 15:13:45.481: %LWAPP-3-CLIENTERRORLOG: LWAPP LED Init: incorrect led state 255

*Jul 26 15:13:45.497: %LINK-5-CHANGED: Interface Dot11Radio0, changed state to administratively down

*Jul 26 15:13:45.528: %LINK-6-UPDOWN: Interface Dot11Radio0, changed state to up

*Jul 26 15:13:45.642: %LINK-6-UPDOWN: Interface Dot11Radio0, changed state to down

*Jul 26 15:13:45.648: %LINK-5-CHANGED: Interface Dot11Radio0, changed state to reset

*Jul 26 15:13:46.664: %LINK-6-UPDOWN: Interface Dot11Radio0, changed state to up

*Jul 26 15:13:47.664: %LINEPROTO-5-UPDOWN: Line protocol on Interface Dot11Radio0, changed state to up

*Jul 26 15:13:55.529: %CAPWAP-3-ERRORLOG: Go join a capwap controller

*Jul 26 15:13:56.000: %CAPWAP-5-DTLSREQSEND: DTLS connection request sent peer_ip: 192.168.10.30 peer_port: 5246

*Jul 26 15:13:56.003: %LINK-6-UPDOWN: Interface Dot11Radio0, changed state to down

*Jul 26 15:13:56.009: %LINK-5-CHANGED: Interface Dot11Radio0, changed state to reset

*Jul 26 15:13:56.415: %CAPWAP-5-DTLSREQSUCC: DTLS connection created sucessfully peer_ip: 192.168.10.30 peer_port: 5246

*Jul 26 15:13:56.418: %CAPWAP-5-SENDJOIN: sending Join Request to 192.168.10.30

*Jul 26 15:13:56.418: %DTLS-5-ALERT: Received WARNING : Close notify alert from 192.168.10.30

*Jul 26 15:13:56.418: %DTLS-5-SEND_ALERT: Send FATAL : Close notify Alert to 192.168.10.30:5246

*Jul 26 15:13:56.418: %CAPWAP-3-ERRORLOG: Go join a capwap controller

*Jul 26 15:13:56.000: %CAPWAP-5-DTLSREQSEND: DTLS connection request sent peer_ip: 192.168.10.30 peer_port: 5246

*Jul 26 15:13:56.421: %CAPWAP-5-DTLSREQSUCC: DTLS connection created sucessfully peer_ip: 192.168.10.30 peer_port: 5246

*Jul 26 15:13:56.421: %CAPWAP-5-SENDJOIN: sending Join Request to 192.168.10.30

*Jul 26 15:13:56.424: %DTLS-5-ALERT: Received WARNING : Close notify alert from 192.168.10.30

*Jul 26 15:13:57.635: %LINK-6-UPDOWN: Interface Dot11Radio0, changed state to up

*Jul 26 15:13:58.636: %LINEPROTO-5-UPDOWN: Line protocol on Interface Dot11Radio0, changed state to up

*Jul 26 15:14:06.519: %CAPWAP-3-ERRORLOG: Go join a capwap controller

*Jul 26 15:14:07.000: %CAPWAP-5-DTLSREQSEND: DTLS connection request sent peer_ip: 192.168.10.30 peer_port: 5246

*Jul 26 15:14:07.003: %LINK-6-UPDOWN: Interface Dot11Radio0, changed state to down

*Jul 26 15:14:07.009: %LINK-5-CHANGED: Interface Dot11Radio0, changed state to reset

*Jul 26 15:14:07.418: %CAPWAP-5-DTLSREQSUCC: DTLS connection created sucessfully peer_ip: 192.168.10.30  peer_port: 5246

*Jul 26 15:14:07.418: %CAPWAP-5-SENDJOIN: sending Join Request to 192.168.10.30

*Jul 26 15:14:07.421: %DTLS-5-ALERT: Received WARNING : Close notify alert from 192.168.10.30

*Jul 26 15:14:07.421: %DTLS-5-SEND_ALERT: Send FATAL : Close notify Alert to 192.168.10.30:5246

*Jul 26 15:14:07.421: %CAPWAP-3-ERRORLOG: Go join a capwap controller

*Jul 26 15:14:07.000: %CAPWAP-5-DTLSREQSEND: DTLS connection request sent peer_ip: 192.168.10.30 peer_port: 5246

*Jul 26 15:14:07.418: %CAPWAP-5-DTLSREQSUCC: DTLS connection created sucessfully peer_ip: 192.168.10.30 peer_port: 5246

*Jul 26 15:14:07.418: %CAPWAP-5-SENDJOIN: sending Join Request to 192.168.10.30

*Jul 26 15:14:07.421: %DTLS-5-ALERT: Received WARNING : Close notify alert from 192.168.10.30

*Jul 26 15:14:08.632: %LINK-6-UPDOWN: Interface Dot11Radio0, changed state to up

*Jul 26 15:14:09.632: %LINEPROTO-5-UPDOWN: Line protocol on Interface Dot11Radio0, changed state to up

*Jul 26 15:14:11.495: %MESH-3-TIMER_EXPIRED: Mesh Lwapp join timer expired

*Jul 26 15:14:11.495: %MESH-3-TIMER_EXPIRED: Mesh Lwapp join failed expired

*Jul 26 15:14:11.495: %MESH-6-LINK_UPDOWN: Mesh station 0006.f6ee.5c41 link Down

*Jul 26 15:14:13.495: %LINK-6-UPDOWN: Interface BVI1, changed state to down

*Jul 26 15:14:17.516: %CAPWAP-3-ERRORLOG: Go join a capwap controller

*Jul 26 15:14:18.000: %CAPWAP-5-DTLSREQSEND: DTLS connection request sent peer_ip: 192.168.10.30 peer_port: 5246

*Jul 26 15:14:19.481: %LINEPROTO-5-UPDOWN: Line protocol on Interface BVI1, changed state to down

*Jul 26 15:14:21.004: %LINK-6-UPDOWN: Interface Dot11Radio0, changed state to down

*Jul 26 15:14:21.010: %LINK-5-CHANGED: Interface Dot11Radio0, changed state to reset

*Jul 26 15:14:22.004: %LINEPROTO-5-UPDOWN: Line protocol on Interface Dot11Radio0, changed state to down

*Jul 26 15:14:22.029: %LINK-6-UPDOWN: Interface Dot11Radio0, changed state to up

*Jul 26 15:14:23.030: %LINEPROTO-5-UPDOWN: Line protocol on Interface Dot11Radio0, changed state to up

4 REPLIES
Bronze

Re: AIR-CT2504-K9 and AIR-CAP3502I-A-K9 - Unable to Join the con

the ap is in mesh mode... add the radio 0 mac address in mac filter or ap auth page should make it regidtered, then change it back to local mode.

Sent from Cisco Technical Support iPad App

New Member

AIR-CT2504-K9 and AIR-CAP3502I-A-K9 - Unable to Join the control

How do i do that?

Can you guide me?

VIP Purple

Re: AIR-CT2504-K9 and AIR-CAP3502I-A-K9 - Unable to Join the con

Here is another way of doing this. Go to the AP Console & try below

1. clear capwap private-config

2. reload

Then AP should comeback in local mode & join the WLC (as long as AP discover a controller to join, worse case you have to manually configure an IP & controller IP on the AP itself)

HTH

Rasika

New Member

AIR-CT2504-K9 and AIR-CAP3502I-A-K9 - Unable to Join the control

You can also get a MESH AP to join a WLC by adding it as an allowed MAC address. Then switch it from Bridge mode to Local mode.

Step-by-Step instructions on that process can be found here.

http://supertekboy.com/2014/01/13/cisco-lightweight-access-point-will-not-join-to-a-wireless-lan-controller/

1884
Views
0
Helpful
4
Replies