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

Cisco 2602 won't connect to the controller

Hello,

i have a problem with my cisco 2602e lightweight/capwap access points. They won't connect anymore to the controller?

It seems to be that ap will connect ap as mesh ap on the controller? A few weeks ago everything was working fine with

these ap's and they are connecting as local access point. When i add the mac address as mic ap to the mac address

table the ap connects to ctl without problem. We have a lot of access points and i don't want to add all of them to the

ap mac address table.

 

AP Modell:                      Cisco 2602e

AP Version:                    System image file is "flash:/ap3g2-k9w8-mx.152-2.JB/ap3g2-k9w8-xx.152-2.JB"

Controller Type:               8510

Controller Software:          7.4.100.0

Controller IP:                    10.45.29.101

Serial Log from the Access Point without mac adding:

*Aug  8 11:53:18.999: %DTLS-5-SEND_ALERT: Send FATAL : Close notify Alert to 10.45.29.101:5246
*Aug  8 11:53:19.051: %LWAPP-3-CLIENTERRORLOG: LWAPP LED Init: incorrect led state 255
*Aug  8 11:53:19.063: %LINK-5-CHANGED: Interface Dot11Radio0, changed state to administratively down
*Aug  8 11:53:19.091: %LINK-6-UPDOWN: Interface Dot11Radio0, changed state to up
*Aug  8 11:53:20.063: %LINEPROTO-5-UPDOWN: Line protocol on Interface Dot11Radio0, changed state to down
*Aug  8 11:53:20.095: %LINK-6-UPDOWN: Interface Dot11Radio0, changed state to down
*Aug  8 11:53:20.103: %LINK-5-CHANGED: Interface Dot11Radio0, changed state to reset
*Aug  8 11:53:21.123: %LINK-6-UPDOWN: Interface Dot11Radio0, changed state to up
*Aug  8 11:53:22.123: %LINEPROTO-5-UPDOWN: Line protocol on Interface Dot11Radio0, changed st        p
AP6c41.6a78.ceca#$flash:/ap3g2-k9w8-mx.152-2.JB/ap3g2-k9w8-xx.152-2.JB"
*Aug  8 11:53:29.091: %CAPWAP-3-ERRORLOG: Go join a capwap controller
*Aug  8 11:53:29.000: %CAPWAP-5-DTLSREQSEND: DTLS connection request sent peer_ip: 10.45.29.101 peer_port: 5246
*Aug  8 11:53:29.003: %LINK-6-UPDOWN: Interface Dot11Radio0, changed state to down
*Aug  8 11:53:29.187: %LINK-5-CHANGED: Interface Dot11Radio0, changed state to reset
*Aug  8 11:53:29.199: %CAPWAP-5-DTLSREQSUCC: DTLS connection created sucessfully peer_ip: 10.45.29.101 peer_port: 5246
*Aug  8 11:53:29.199: %CAPWAP-5-SENDJOIN: sending Join Request to 10.45.29.101
*Aug  8 11:53:29.199: %CAPWAP-3-ERRORLOG: Invalid event 10 & state 5 combination.
*Aug  8 11:53:29.199: %CAPWAP-3-ERRORLOG: CAPWAP SM handler: Failed to process message type 10 state 5.
*Aug  8 11:53:29.199: %CAPWAP-3-ERRORLOG: Failed to handle capwap control message from controller
*Aug  8 11:53:30.003: %LINEPROTO-5-UPDOWN: Line protocol on Interface Dot11Radio0, changed state to down
*Aug  8 11:53:30.031: %LINK-6-UPDOWN: Interface Dot11Radio0, changed state to up
*Aug  8 11:53:30.039: %LINK-6-UPDOWN: Interface Dot11Radio0, changed state to down
*Aug  8 11:53:30.047: %LINK-5-CHANGED: Interface Dot11Radio0, changed state to reset
*Aug  8 11:53:31.067: %LINK-6-UPDOWN: Interface Dot11Radio0, changed state to up
*Aug  8 11:53:32.067: %LINEPROTO-5-UPDOWN: Line protocol on Interface Dot11Radio0, changed state to up
*Aug  8 11:53:34.199: %CAPWAP-5-SENDJOIN: sending Join Request to 10.45.29.101
*Aug  8 11:53:34.203: %LINK-6-UPDOWN: Interface Dot11Radio0, changed state to down
*Aug  8 11:53:34.211: %LINK-5-CHANGED: Interface Dot11Radio0, changed state to reset
*Aug  8 11:53:35.203: %LINEPROTO-5-UPDOWN: Line protocol on Interface Dot11Radio0, changed state to down
*Aug  8 11:53:35.231: %LINK-6-UPDOWN: Interface Dot11Radio0, changed state to up
*Aug  8 11:53:36.231: %LINEPROTO-5-UPDOWN: Line protocol on Interface Dot11Radio0, changed state to up
*Aug  8 11:54:19.175: %MESH-3-TIMER_EXPIRED: Mesh Lwapp join timer expired
*Aug  8 11:54:19.175: %MESH-3-TIMER_EXPIRED: Mesh Lwapp join failed expired
*Aug  8 11:54:19.175: %MESH-6-LINK_UPDOWN: Mesh station 6c41.6a78.ceca link Down
*Aug  8 11:54:21.175: %LINK-6-UPDOWN: Interface BVI1, changed state to down
*Aug  8 11:54:26.675: %LINEPROTO-5-UPDOWN: Line protocol on Interface BVI1, changed state to down
*Aug  8 11:54:28.999: %DTLS-5-SEND_ALERT: Send FATAL : Close notify Alert to 10.45.29.101:5246
*Aug  8 11:54:32.067: %LINK-5-CHANGED: Interface Dot11Radio0, changed state to administratively down
*Aug  8 11:54:32.083: %LINK-6-UPDOWN: Interface Dot11Radio0, changed state to up
*Aug  8 11:54:33.067: %LINEPROTO-5-UPDOWN: Line protocol on Interface Dot11Radio0, changed state to down
*Aug  8 11:54:33.107: %LINK-6-UPDOWN: Interface Dot11Radio0, changed state to down
*Aug  8 11:54:33.115: %LINK-5-CHANGED: Interface Dot11Radio0, changed state to reset
*Aug  8 11:54:34.135: %LINK-6-UPDOWN: Interface Dot11Radio0, changed state to up
*Aug  8 11:54:35.135: %LINEPROTO-5-UPDOWN: Line protocol on Interface Dot11Radio0, changed state to up
*Aug  8 11:54:52.087: %LINK-6-UPDOWN: Interface Dot11Radio0, changed state to down
*Aug  8 11:54:52.095: %LINK-5-CHANGED: Interface Dot11Radio0, changed state to reset
*Aug  8 11:54:53.087: %LINEPROTO-5-UPDOWN: Line protocol on Interface Dot11Radio0, changed state to down
*Aug  8 11:54:53.115: %LINK-6-UPDOWN: Interface Dot11Radio0, changed state to up
*Aug  8 11:54:54.115: %LINEPROTO-5-UPDOWN: Line protocol on Interface Dot11Radio0, changed state to up
*Aug  8 11:54:59.567: %MESH-6-CAPWAP_RESTART: Mesh Capwap re-started
*Aug  8 11:55:01.567: %LINK-6-UPDOWN: Interface BVI1, changed state to up
*Aug  8 11:55:02.083: %CAPWAP-3-ERRORLOG: Invalid event 29 & state 4 combination.
*Aug  8 11:55:02.083: %CAPWAP-3-ERRORLOG: SM handler: Failed to process timer message. Event 29, state 4
*Aug  8 11:55:02.083: %CAPWAP-3-ERRORLOG: Failed to handle timer message.
*Aug  8 11:55:02.083: %CAPWAP-3-ERRORLOG: Failed to process timer message.
*Aug  8 11:55:02.567: %LINEPROTO-5-UPDOWN: Line protocol on Interface BVI1, changed state to up
*Aug  8 11:55:04.635: %LINK-5-CHANGED: Interface Dot11Radio0, changed state to administratively down
*Aug  8 11:55:05.635: %LINEPROTO-5-UPDOWN: Line protocol on Interface Dot11Radio0, changed state to down
*Aug  8 11:55:10.159: %LINK-5-CHANGED: Interface Dot11Radio0, changed state to reset
*Aug  8 11:55:11.183: %LINK-6-UPDOWN: Interface Dot11Radio0, changed state to up
*Aug  8 11:55:12.183: %LINEPROTO-5-UPDOWN: Line protocol on Interface Dot11Radio0, changed state to up
*Aug  8 11:55:13.279: %MESH-6-CAPWAP_RESTART: Mesh Capwap re-started
*Aug  8 11:55:13.343: %DHCP-6-ADDRESS_ASSIGN: Interface BVI1 assigned DHCP address 10.36.9.58, mask 255.255.248.0, hostname AP6c41.6a78.ceca

*Aug  8 11:55:13.343: %MESH-6-CAPWAP_RESTART: Mesh Capwap re-started
*Aug  8 11:55:18.395: %LWAPP-3-CLIENTERRORLOG: LWAPP LED Init: incorrect led state 255
*Aug  8 11:55:18.407: %LINK-5-CHANGED: Interface Dot11Radio0, changed state to administratively down
*Aug  8 11:55:18.435: %LINK-6-UPDOWN: Interface Dot11Radio0, changed state to up
*Aug  8 11:55:19.407: %LINEPROTO-5-UPDOWN: Line protocol on Interface Dot11Radio0, changed state to down
*Aug  8 11:55:19.435: %CAPWAP-3-ERRORLOG: Did not get log server settings from DHCP.
*Aug  8 11:55:19.491: %LINK-6-UPDOWN: Interface Dot11Radio0, changed state to down
*Aug  8 11:55:19.495: %LINK-5-CHANGED: Interface Dot11Radio0, changed state to reset
*Aug  8 11:55:20.515: %LINK-6-UPDOWN: Interface Dot11Radio0, changed state to up
*Aug  8 11:55:20.523: %LINK-6-UPDOWN: Interface Dot11Radio0, changed state to down
*Aug  8 11:55:20.531: %LINK-5-CHANGED: Interface Dot11Radio0, changed state to reset
*Aug  8 11:55:21.551: %LINK-6-UPDOWN: Interface Dot11Radio0, changed state to up
*Aug  8 11:55:22.551: %LINEPROTO-5-UPDOWN: Line protocol on Interface Dot11Radio0, changed state to up

6 REPLIES

Cisco 2602 won't connect to the controller

it looksl like that AP somehow got configured to be in MESH mode, you'll need to add it to the mac filter.  Once it joins you can then change the mode back to local and remove the filter entry.

HTH,
Steve

------------------------------------------------------------------------------------------------
Please remember to rate useful posts, and mark questions as answered

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

Cisco 2602 won't connect to the controller

yes i know but is there no other way except the mac filter? A few weeks ago the system was working without adding mac's to the address table?

Cisco 2602 won't connect to the controller

If they are MESH mode then they have to be added.  Though I've seein it work with either mac-filter or AP Auth list.

You said your AP had been in local mode, did you change them to MESH?

HTH,
Steve

------------------------------------------------------------------------------------------------
Please remember to rate useful posts, and mark questions as answered

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

Cisco 2602 won't connect to the controller

the access point is new. a few weeks ago they are connected as local ap but now they try to connect as bridge or mesh ap?

Community Member

Cisco 2602 won't connect to the controller

In the field we've seen a few hundred ship from the factory, right out of the box, in Mesh mode. Finding the broken ones and adding the MACs is becoming a nusiance for large depolyments.

Community Member

Cisco 2602 won't connect to the controller

Step-by-step guide on fixing it for anyone else facing the same problem.

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

2620
Views
5
Helpful
6
Replies
CreatePlease to create content