cancel
Showing results for 
Search instead for 
Did you mean: 
cancel
1365
Views
0
Helpful
3
Replies

2702I-E AP cannot join WLC after changing mode to FlexConnect

casanavep
Level 3
Level 3

I have a 5508 WLC in the states running 7.6.130 firmware.  I am deploying six APs in Great Brittan. The APs were able to draw option 43, find the WLC, download firmware, and register under default local mode.  When I change an APs mode to FlexConnect it resets and is expected, but never is able to register after that.  I have added the MAC to the WLC MAC filtering list with all WLANs access on the management interface (registration interface).  When I debug the AP's MAC, capwap errors and events on the AP, I get the following:

 

*spamApTask5: Jun 01 09:31:07.360: acDtlsPlumbControlPlaneKeys: lrad:10.90.224.140(16873) mwar:10.60.1.20(5246)

*spamApTask5: Jun 01 09:31:07.479: apModel: AIR-CAP2702I-E-K9

*spamApTask5: Jun 01 09:31:07.479: apType = 41 apModel: AIR-CAP2702I-E-K9

*spamApTask5: Jun 01 09:31:07.479: Unknown AP type. Using Controller Version!!!

 

I have tried two different controller running 7.6.130 and have the same results.  European country codes have already be allowed, hence the initial registration before moving it to FlexConnect mode.  Thoughts?  I appreciate any pointers here.

3 Replies 3

casanavep
Level 3
Level 3

Followed the workaround guidelines in the following and now have it registered again:

  https://tools.cisco.com/bugsearch/bug/CSCuo44310/?referring_site=bugquickviewredir

  Unfortunately, this puts the AP back in local mode. 

From there, it reregisters.  If I try to push any changes to the AP, whether FlexConnect or simply defining a name, it tries to go our other controller which does not have European countries address.  Even if I configure HA and define the controller with Europe CC's defines, it tries to go to the other:

*Jun  1 15:52:55.107: %CAPWAP-3-ERRORLOG: Selected MWAR ' "other controllers name"

Even manually defining CAPWAP and LWAPP controllers in the AP via console doesn't overwrite this behavior.

 

This is not a fix - any change and any outage cause it to register with another WLC randomly.  Defining HA order does not change it.  APs are on the same subnet as WLC, so not communications blocked between the APs and controller - on an isolated WLC control VLAN.

casanavep
Level 3
Level 3

Glad to see it is not so easy that Cisco rep even know a fix....

Review Cisco Networking for a $25 gift card