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

Can`t add AP to MESH

Hello, we have 2504 controller with 7.4 version software and 3602E AP. Now i am trying to add this AP to mesh network as described in the deployment guide, i added mac address to the filter, then convert AP to the bride mode trought controller and after that AP doesn`t join to controller. An AP`s console we are seeing errors below:

*Aug 13 03:19:51.067: %LINK-6-UPDOWN: Interface Dot11Radio0, changed state to up

*Aug 13 03:19:52.067: %LINEPROTO-5-UPDOWN: Line protocol on Interface Dot11Radio0, changed state to up

*Aug 13 03:19:54.419: %CAPWAP-5-SENDJOIN: sending Join Request to 172.16.1.100

*Aug 13 03:19:54.423: %LINK-6-UPDOWN: Interface Dot11Radio0, changed state to down

*Aug 13 03:19:54.431: %LINK-5-CHANGED: Interface Dot11Radio0, changed state to reset

*Aug 13 03:19:55.423: %LINEPROTO-5-UPDOWN: Line protocol on Interface Dot11Radio0, changed state to down

*Aug 13 03:19:55.451: %LINK-6-UPDOWN: Interface Dot11Radio0, changed state to up

*Aug 13 03:19:56.451: %LINEPROTO-5-UPDOWN: Line protocol on Interface Dot11Radio0, changed state to up

*Aug 13 03:20:38.787: %MESH-3-TIMER_EXPIRED: Mesh Lwapp join timer expired

*Aug 13 03:20:38.787: %MESH-3-TIMER_EXPIRED: Mesh Lwapp join failed expired

*Aug 13 03:20:38.787: %MESH-6-LINK_UPDOWN: Mesh station 0006.f64d.5cd0 link Down

*Aug 13 03:20:40.787: %LINK-6-UPDOWN: Interface BVI1, changed state to down

*Aug 13 03:20:46.287: %LINEPROTO-5-UPDOWN: Line protocol on Interface BVI1, changed state to down

*Aug 13 03:20:48.999: %DTLS-5-SEND_ALERT: Send FATAL : Close notify Alert to 172.16.1.100:5246

*Aug 13 03:20:52.055: %LINK-5-CHANGED: Interface Dot11Radio0, changed state to administratively down

*Aug 13 03:20:52.071: %LINK-6-UPDOWN: Interface Dot11Radio0, changed state to up

*Aug 13 03:20:53.055: %LINEPROTO-5-UPDOWN: Line protocol on Interface Dot11Radio0, changed state to down

*Aug 13 03:20:53.095: %LINK-6-UPDOWN: Interface Dot11Radio0, changed state to down

*Aug 13 03:20:53.103: %LINK-5-CHANGED: Interface Dot11Radio0, changed state to reset

*Aug 13 03:20:54.123: %LINK-6-UPDOWN: Interface Dot11Radio0, changed state to up

*Aug 13 03:20:55.123: %LINEPROTO-5-UPDOWN: Line protocol on Interface Dot11Radio0, changed state to up

*Aug 13 03:21:12.075: %LINK-6-UPDOWN: Interface Dot11Radio0, changed state to down

*Aug 13 03:21:12.083: %LINK-5-CHANGED: Interface Dot11Radio0, changed state to reset

*Aug 13 03:21:13.075: %LINEPROTO-5-UPDOWN: Line protocol on Interface Dot11Radio0, changed state to down

*Aug 13 03:21:13.103: %LINK-6-UPDOWN: Interface Dot11Radio0, changed state to up

*Aug 13 03:21:14.103: %LINEPROTO-5-UPDOWN: Line protocol on Interface Dot11Radio0, changed state to up

*Aug 13 03:21:17.147: %MESH-6-CAPWAP_RESTART: Mesh Capwap re-started

*Aug 13 03:21:19.147: %LINK-6-UPDOWN: Interface BVI1, changed state to up

*Aug 13 03:21:20.147: %LINEPROTO-5-UPDOWN: Line protocol on Interface BVI1, changed state to up

*Aug 13 03:21:22.071: %CAPWAP-3-ERRORLOG: Invalid event 29 & state 4 combination.

*Aug 13 03:21:22.071: %CAPWAP-3-ERRORLOG: SM handler: Failed to process timer message. Event 29, state 4

*Aug 13 03:21:22.071: %CAPWAP-3-ERRORLOG: Failed to handle timer message.

*Aug 13 03:21:22.071: %CAPWAP-3-ERRORLOG: Failed to process timer message.

*Aug 13 03:21:22.199: %LINK-5-CHANGED: Interface Dot11Radio0, changed state to administratively down

*Aug 13 03:21:22.227: %LINK-6-UPDOWN: Interface Dot11Radio0, changed state to up

*Aug 13 03:21:23.199: %LINEPROTO-5-UPDOWN: Line protocol on Interface Dot11Radio0, changed state to down

*Aug 13 03:21:23.231: %LINK-6-UPDOWN: Interface Dot11Radio0, changed state to down

*Aug 13 03:21:23.239: %LINK-5-CHANGED: Interface Dot11Radio0, changed state to reset

*Aug 13 03:21:24.259: %LINK-6-UPDOWN: Interface Dot11Radio0, changed state to up

*Aug 13 03:21:25.215: %MESH-6-CAPWAP_RESTART: Mesh Capwap re-started

*Aug 13 03:21:25.259: %LINEPROTO-5-UPDOWN: Line protocol on Interface Dot11Radio0, changed state to up

*Aug 13 03:21:25.283: %DHCP-6-ADDRESS_ASSIGN: Interface BVI1 assigned DHCP address 172.16.1.13, mask 255.255.255.0, hostname AP0006.f64d.5cd0

*Aug 13 03:21:25.283: %MESH-6-CAPWAP_RESTART: Mesh Capwap re-started

*Aug 13 03:21:30.323: %LWAPP-3-CLIENTERRORLOG: LWAPP LED Init: incorrect led state 255

*Aug 13 03:21:30.335: %LINK-5-CHANGED: Interface Dot11Radio0, changed state to administratively down

*Aug 13 03:21:30.359: %LINK-6-UPDOWN: Interface Dot11Radio0, changed state to up

Translating "CISCO-CAPWAP-CONTROLLER"...domain server (255.255.255.255)

*Aug 13 03:21:31.335: %LINEPROTO-5-UPDOWN: Line protocol on Interface Dot11Radio0, changed state to down

*Aug 13 03:21:31.359: %CAPWAP-3-ERRORLOG: Did not get log server settings from DHCP.

*Aug 13 03:21:31.367: %LINK-6-UPDOWN: Interface Dot11Radio0, changed state to down

*Aug 13 03:21:31.375: %LINK-5-CHANGED: Interface Dot11Radio0, changed state to reset

*Aug 13 03:21:32.395: %LINK-6-UPDOWN: Interface Dot11Radio0, changed state to up

*Aug 13 03:21:33.395: %LINEPROTO-5-UPDOWN: Line protocol on Interface Dot11Radio0, changed state to up

*Aug 13 03:21:40.359: %CAPWAP-3-ERRORLOG: Could Not resolve CISCO-CAPWAP-CONTROLLER

*Aug 13 03:21:41.363: %LINK-6-UPDOWN: Interface Dot11Radio0, changed state to down

*Aug 13 03:21:41.411: %LINK-5-CHANGED: Interface Dot11Radio0, changed state to reset

*Aug 13 03:21:42.363: %LINEPROTO-5-UPDOWN: Line protocol on Interface Dot11Radio0, changed state to down

*Aug 13 03:21:42.431: %LINK-6-UPDOWN: Interface Dot11Radio0, changed state to up

*Aug 13 03:21:43.431: %LINEPROTO-5-UPDOWN: Line protocol on Interface Dot11Radio0, changed state to up

*Mar  1 00:01:37.515: %MESH-6-CAPWAP_RESTART: Mesh Capwap re-started

*Mar  1 00:01:38.695: %CAPWAP-3-ERRORLOG: Invalid event 29 & state 4 combination.

*Mar  1 00:01:38.695: %CAPWAP-3-ERRORLOG: SM handler: Failed to process timer message. Event 29, state 4

*Mar  1 00:01:38.695: %CAPWAP-3-ERRORLOG: Failed to handle timer message.

*Mar  1 00:01:38.695: %CAPWAP-3-ERRORLOG: Failed to process timer message.

*Mar  1 00:01:42.555: %LWAPP-3-CLIENTERRORLOG: LWAPP LED Init: incorrect led state 255

*Mar  1 00:01:42.567: %LINK-5-CHANGED: Interface Dot11Radio0, changed state to administratively down

Translating "CISCO-CAPWAP-CONTROLLER"...domain server (255.255.255.255)

*Mar  1 00:01:42.591: %LINK-6-UPDOWN: Interface Dot11Radio0, changed state to up

*Mar  1 00:01:43.567: %LINEPROTO-5-UPDOWN: Line protocol on Interface Dot11Radio0, changed state to down

*Mar  1 00:01:43.591: %CAPWAP-3-ERRORLOG: Did not get log server settings from DHCP.

*Mar  1 00:01:43.599: %LINK-6-UPDOWN: Interface Dot11Radio0, changed state to down

*Mar  1 00:01:43.607: %LINK-5-CHANGED: Interface Dot11Radio0, changed state to reset

*Mar  1 00:01:44.627: %LINK-6-UPDOWN: Interface Dot11Radio0, changed state to up

*Mar  1 00:01:45.627: %LINEPROTO-5-UPDOWN: Line protocol on Interface Dot11Radio0, changed state to up

*Mar  1 00:01:52.591: %CAPWAP-3-ERRORLOG: Could Not resolve CISCO-CAPWAP-CONTROLLER

*Mar  1 00:01:53.631: %LINK-6-UPDOWN: Interface Dot11Radio0, changed state to down

*Mar  1 00:01:53.639: %LINK-5-CHANGED: Interface Dot11Radio0, changed state to reset

*Mar  1 00:01:54.631: %LINEPROTO-5-UPDOWN: Line protocol on Interface Dot11Radio0, changed state to down

*Mar  1 00:01:54.659: %LINK-6-UPDOWN: Interface Dot11Radio0, changed state to up

*Mar  1 00:01:55.659: %LINEPROTO-5-UPDOWN: Line protocol on Interface Dot11Radio0, changed state to up

*Mar  1 00:02:03.591: %CAPWAP-3-ERRORLOG: Go join a capwap controller

*Aug 13 03:57:09.000: %CAPWAP-5-DTLSREQSEND: DTLS connection request sent peer_ip: 172.16.1.100 peer_port: 5246

*Aug 13 03:57:09.003: %LINK-6-UPDOWN: Interface Dot11Radio0, changed state to down

*Aug 13 03:57:09.011: %LINK-5-CHANGED: Interface Dot11Radio0, changed state to reset

*Aug 13 03:57:09.415: %CAPWAP-5-DTLSREQSUCC: DTLS connection created sucessfully peer_ip: 172.16.1.100 peer_port: 5246

*Aug 13 03:57:09.415: %CAPWAP-5-SENDJOIN: sending Join Request to 172.16.1.100

*Aug 13 03:57:09.419: %CAPWAP-3-ERRORLOG: Invalid event 10 & state 5 combination.

*Aug 13 03:57:09.419: %CAPWAP-3-ERRORLOG: CAPWAP SM handler: Failed to process message type 10 state 5.

*Aug 13 03:57:09.419: %CAPWAP-3-ERRORLOG: Failed to handle capwap control message from controller

*Aug 13 03:57:10.003: %LINEPROTO-5-UPDOWN: Line protocol on Interface Dot11Radio0, changed state to down

4 REPLIES
Hall of Fame Super Silver

Re: Can`t add AP to MESH

I run the same setup at home with no issues. Did you set a BGN, and is this AP close to a RAP since the back haul is the 5ghz?

Sent from Cisco Technical Support iPhone App

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

Re: Can`t add AP to MESH

Thanks for your reply! I didn`t set BGN because there is even no Mesh tabs in WLC AP menu interface.

UPDATE!

There is also such error:

it is saying that bridge mode cannot be supported on Multi Country Controller

Bronze

Re: Can`t add AP to MESH

then check if you enabled more than one country code . mesh can only work when 1 country code enabled.

in wireless tab.

Sent from Cisco Technical Support iPad App

Re: Can`t add AP to MESH

Make sure that your AP regulatory domain matches the country selected on the WLC.
AFAIK if multiple countries are selected on the WLC then it will work but the AP is limited only to the common channel of the selected countries. I did not try that in practice though.

Btw, can you try to connect your AP to the wlc via a wire and male sure it joins (in either briedge or local mode) before trying to connect it as a MAP?

Regards,


Amjad

Sent from Cisco Technical Support iPad App

Rating useful replies is more useful than saying "Thank you"
538
Views
0
Helpful
4
Replies
CreatePlease login to create content