AP not joining WLC in Bridge mode

[kidops0104]

I have several Cisco 1552 outdoor APs which are joined to a 5508 WLC and working fine in Local mode,

Needed to configure MESH and changed one of the AP mode to bridge to enable me configure it as RootAP for my MESH, upon restarting after accepting the bridge mode configuration it has refused to re-join the WLC.  

Below is summary of join attempt.

Last join error summary
- Type of error that occurred last......................... Lwapp join request rejected
- Reason for error that occurred last...................... 
- Time at which the last join error occurred............... Feb 27 09:16:08.776

I am now unable to access the AP remotely to revers the config on the AP

[Scott Fella]

Typically when I have implemented mesh, I would stage everything first, capture the mac and add them to the WLC and then boot them all on local. Once in local, I then choose which will be the RAP and which are the MAP's.  Then after all that is set, I would remove the Ethernet from all the MAP's and verify it has all joined. 

Even with your scenario, it should work. When you move the AP from local to bridge, as long as the Ethernet is connected, it should join the WLC like if it was in local mode.  The only way now is either to power cycle the AP and see if that helps or you will have to access the cosole and see what is going wrong or even factory default the AP while your there. 

-Scott

[kidops0104]

Hi Scott Fella

Thanks for your response,

Yes Apart from the AP in production which i changed to bridge mode and it refused to join the controller again, i have the rest of the AP's which i want to configure MESH on staging, but its the same scenerio, not joining after changing to bridge mode,

below is the error message from one of the AP's.

APb8be.bf3b.8f80#
*Mar  1 00:01:24.523: %MESH-6-CAPWAP_RESTART: Mesh Capwap re-started
*Mar  1 00:01:26.523: %LINK-6-UPDOWN: Interface BVI1, changed state to up
*Mar  1 00:01:27.523: %LINEPROTO-5-UPDOWN: Line protocol on Interface BVI1, changed state to up
% CDP is not supported on this interface, or for this encapsulation
*Mar  1 00:01:29.627: %CAPWAP-3-ERRORLOG: Not sending discovery request AP does not have an Ip !!
*Mar  1 00:01:38.451: %MESH-6-CAPWAP_RESTART: Mesh Capwap re-started
*Mar  1 00:01:38.471: %DHCP-6-ADDRESS_ASSIGN: Interface BVI1 assigned DHCP address 172.17.30.63, mask 255.255.254.0, hostname APb8be.bf3b.8f80

*Mar  1 00:01:38.471: %MESH-6-CAPWAP_RESTART: Mesh Capwap re-started
*Mar  1 00:01:39.627: %CAPWAP-3-ERRORLOG: Invalid event 29 & state 4 combination.
*Mar  1 00:01:39.627: %CAPWAP-3-ERRORLOG: SM handler: Failed to process timer message. Event 29, state 4
*Mar  1 00:01:39.627: %CAPWAP-3-ERRORLOG: Failed to handle timer message.
*Mar  1 00:01:39.627: %CAPWAP-3-ERRORLOG: Failed to process timer message.
% CDP is not supported on this interface, or for this encapsulation
Translating "CISCO-CAPWAP-CONTROLLER.xxxxx.com"...domain server (1xx.xx.100.5) [OK]

*Mar  1 00:01:43.511: %LWAPP-3-CLIENTERRORLOG: LWAPP LED Init: incorrect led state 255
*Mar  1 00:01:44.567: %CAPWAP-3-ERRORLOG: Did not get log server settings from DHCP.
*Mar  1 00:01:54.567: %CAPWAP-3-ERRORLOG: Go join a capwap controller
*Feb 27 15:35:03.000: %CAPWAP-5-DTLSREQSEND: DTLS connection request sent peer_ip: 172.20.70.4 peer_port: 5246
*Feb 27 15:35:03.583: %CAPWAP-5-DTLSREQSUCC: DTLS connection created sucessfully peer_ip: 172.20.70.4 peer_port: 5246
*Feb 27 15:35:03.583: %CAPWAP-5-SENDJOIN: sending Join Request to 1xx.xx.70.4
*Feb 27 15:35:03.587: %CAPWAP-3-ERRORLOG: Invalid event 10 & state 5 combination.
*Feb 27 15:35:03.587: %CAPWAP-3-ERRORLOG: CAPWAP SM handler: Failed to process message type 10 state 5.
*Feb 27 15:35:03.587: %CAPWAP-3-ERRORLOG: Failed to handle capwap control message from controller
*Feb 27 15:35:03.587: %CAPWAP-3-ERRORLOG: Failed to process encrypted capwap packet from 172.20.70.4
*Feb 27 15:35:08.583: %CAPWAP-5-SENDJOIN: sending Join Request to 1xx.xx.70.4

[kidops0104]

Anybody with ideas, i cant get the 3 AP's to return back to local mode since they are not joining the WLC any more. 2 were working as local mode on the same controller and the last was a brand new AP all 3 after configuring bridge mode from the controller refused to join controller back after restart.

[Sebastian Pusta]

Hi,

You should authorize the APs to join the WLC by adding their MAC adresses to AP Policies:Security > AAA > AP Policies, click Add.

HTH,

Sebastian

[kidops0104]

Hi,

I already have the Mac addresses on the WLC before changing the mode to bridge from its working local mode. 

I later discovered the issue to be regulatory domain on the controller.

Because of some indoor AP i also have on the controller i had CN, GB and US regulatory domain configured on the controller. so i had to use my second controller to get them to join the WLC as i configured only one regulatory domain on this (GB).

So now i need to do my MESH staging and deployment using my second WLC.

[Abhishek Abhishek]

The regulatory domain should be the same between the WLC and AP so that the AP can join the WLC. Please check this link for details-

http://www.cisco.com/c/en/us/support/docs/wireless/4400-series-wireless-lan-controllers/99948-lap-notjoin-wlc-tshoot.html#p2