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

Cisco 1852i continue to lost and rejoin to Mobility Express

thomas546
Level 1
Level 1

Dear all,

I met one problem when testing Cisco 1852i with Mobility Express.

There're two 1852i called AP1 and AP2.

AP1 is running Mobility Express and AP roles. AP2 is only AP role.

At first, everything is OK, but I find AP2 could not contact to ME , then run DISCOVER process, and rejoin to ME again.

Lost and rejoin processions happen frequently,  AP2's log is as following.

AP1 and AP2 are connecting to stacking L2 switches, power are from PoE injectors.

I changed ME role to AP2 to try, but AP1's lost and rejoin happened again.

Thanks,

Thomas

AP2's Log
[*09/13/2016 13:48:03.8363] Re-Tx Count=11, Max Re-Tx Value=10, NumofPendingMsgs=8
[*09/13/2016 13:48:03.8363]
[*09/13/2016 13:48:06.6854] Re-Tx Count=12, Max Re-Tx Value=10, NumofPendingMsgs=8
[*09/13/2016 13:48:06.6854]
[*09/13/2016 13:48:09.5345] Re-Tx Count=13, Max Re-Tx Value=10, NumofPendingMsgs=8
[*09/13/2016 13:48:09.5345]
[*09/13/2016 13:48:12.3936] Re-Tx Count=14, Max Re-Tx Value=10, NumofPendingMsgs=8
[*09/13/2016 13:48:12.3936]
[*09/13/2016 13:48:15.2427] Re-Tx Count=15, Max Re-Tx Value=10, NumofPendingMsgs=8
[*09/13/2016 13:48:15.2427]
[*09/13/2016 13:48:18.0918] Re-Tx Count=16, Max Re-Tx Value=10, NumofPendingMsgs=9
[*09/13/2016 13:48:18.0918]
[*09/13/2016 13:48:18.0918] Max retransmission count exceeded going back to DISCOVER mode.
[*09/13/2016 13:48:18.0918] GOING BACK TO DISCOVER MODE

ME's Log

Tue Sep 13 21:48:42 2016;10.8.8.58; <131>MMGSHWLC: *spamApTask0: Sep 13 21:48:42.644: %LWAPP-3-RD_ERR9: spam_lrad.c:12482 APs 80:e8:6f:d3:87:c0 country code changed from (UX) to (CN )
Tue Sep 13 21:48:42 2016;10.8.8.58; <131>MMGSHWLC: *spamApTask0: Sep 13 21:48:42.852: %LOG-3-Q_IND: spam_lrad.c:12482 APs 80:e8:6f:d3:87:c0 country code changed from (UX) to (CN )
Tue Sep 13 21:48:42 2016;10.8.8.58; <131>MMGSHWLC: *spamApTask0: Sep 13 21:48:42.852: %CAPWAP-3-AP_AUTOCONVERT_ERR: capwap_ac_sm.c:3579 The system is unable to autoconvert AP  80:e8:6f:d3:87:c0 to supported mode.
Tue Sep 13 21:48:42 2016;10.8.8.58; <131>MMGSHWLC: *spamApTask0: Sep 13 21:48:42.920: %CAPWAP-3-MDNS_INIT_NOT_DONE: capwap_ac_sm.c:7911 mDNS module is not initialized yet, but a mDNS AP : 80:e8:6f:d3:87:c0 has joined.Aggregated query is not sent until mDNS init.

3 Replies 3

thomas546
Level 1
Level 1

Dear all,

After discuss with TAC, the problem was resolved.

1, Update to 8.2.130.0

2, Configure ME ip address on all APs manually

capwap ap primary-base <Primary-WLC-sysname> <Primary-WLC-IP address>

3, Disable AVC function

config flexconnect group <group-name> avc <wlan-id> visibility disable

Thanks,

Thomas

nikhil.kapure
Level 1
Level 1

Dear all,

After discuss with TAC, the problem was resolved.

1, Update to 8.2.145.44

2, Configure ME ip address on all APs manually

capwap ap primary-base <Primary-WLC-sysname> <Primary-WLC-IP address>

3, Disable AVC function

config flexconnect group <group-name> avc <wlan-id> visibility disable

Thanks,

Thomas

Why not upgrade to 8.2.130.0 since that was the solution from the other user on this thread. I'm not a fan of escalation images.

-Scott 

*** Please rate helpful posts *** 

-Scott
*** Please rate helpful posts ***
Review Cisco Networking products for a $25 gift card