CBW140AC un-joins every few minutes

[AlanO]

I've got a hardwired CBW140AC AP connected to a primary CBW145AC AP.  The primary is rock solid, but the CBW140AC un-joins every few minutes.  

Any suggestions on how to debug?

Alan

[marce1000]

                 - Check logs on both access points when that happens.

 M.

[AlanO]

Here's what I find in my log and repeats every few minutes...

*ConfigSynctoAp: Aug 07 08:19:52.161: %LWAPP-3-MSG_SEND_ERR: spam_api.c:78668 The system is unable to send Rsync to AP 192.168.1.121 Failed, ExidCode 255, File Type: FindIT CA certs message to LWAPP; AP 57feb9ac:618abd20:618aba60:57feb3b0:76b91067:618aba60
*ConfigSync: Aug 07 08:19:52.106: %LWAPP-3-MSG_SEND_ERR: spam_api.c:78668 The system is unable to send Rsync to AP 192.168.1.121 Failed, ExidCode 255, File Type: FindIT CA certs message to LWAPP; AP 57feb9ac:604abcd8:604aba18:57feb3b0:76b91067:604aba18
*spamApTask0: Aug 07 08:19:48.773: %HREAP-3-EFFUPG_IMAGE_PRIMARY: hreap.c:9562 AP5CE1.76F2.3784 is elected as Image Primary for Primary Capable APs.
*spamApTask0: Aug 07 08:19:48.773: %HREAP-3-EFFUPG_IMAGE_REPLICA: hreap.c:9516 will get image from AP5CE1.76F2.3784.
*spamApTask0: Aug 07 08:19:48.773: %HREAP-3-EFFUPG_IMAGE_PRIMARY: hreap.c:9562 AP5CE1.76F2.3784 is elected as Image Primary for Primary Capable APs.
*spamApTask0: Aug 07 08:19:48.773: %HREAP-3-EFFUPG_IMAGE_REPLICA: hreap.c:9516 will get image from AP5CE1.76F2.3784.
*spamApTask0: Aug 07 08:18:54.819: %CAPWAP-3-CCO_ASD_LOG_ERROR: spam_lrad.c:103634 CCO ASD logging failed on AP-MAC 6c:71:0d:54:05:70, reason: Index not found unable to delete tmp log
*spamApTask0: Aug 07 08:18:54.814: %LWAPP-3-AP_DEL: spam_lrad.c:6117 6c:71:0d:52:28:80: Entry deleted for AP: 192.168.1.121 (5272) reason : Normal Termination.
*ConfigSynctoAp: Aug 07 08:15:57.533: %LWAPP-3-MSG_SEND_ERR: spam_api.c:78668 The system is unable to send Rsync to AP 192.168.1.121 Failed, ExidCode 255, File Type: FindIT CA certs message to LWAPP; AP 57feb9ac:618abd20:618aba60:57feb3b0:76b91067:618aba60
*ConfigSync: Aug 07 08:15:57.376: %LWAPP-3-MSG_SEND_ERR: spam_api.c:78668 The system is unable to send Rsync to AP 192.168.1.121 Failed, ExidCode 255, File Type: FindIT CA certs message to LWAPP; AP 57feb9ac:604abcd8:604aba18:57feb3b0:76b91067:604aba18
*spamApTask0: Aug 07 08:15:54.212: %HREAP-3-EFFUPG_IMAGE_PRIMARY: hreap.c:9562 AP5CE1.76F2.3784 is elected as Image Primary for Primary Capable APs.
*spamApTask0: Aug 07 08:15:54.212: %HREAP-3-EFFUPG_IMAGE_REPLICA: hreap.c:9516 will get image from AP5CE1.76F2.3784.
*spamApTask0: Aug 07 08:15:54.211: %HREAP-3-EFFUPG_IMAGE_PRIMARY: hreap.c:9562 AP5CE1.76F2.3784 is elected as Image Primary for Primary Capable APs.
*spamApTask0: Aug 07 08:15:54.211: %HREAP-3-EFFUPG_IMAGE_REPLICA: hreap.c:9516 will get image from AP5CE1.76F2.3784.
*spamApTask0: Aug 07 08:15:00.259: %CAPWAP-3-CCO_ASD_LOG_ERROR: spam_lrad.c:103634 CCO ASD logging failed on AP-MAC 6c:71:0d:54:05:70, reason: Index not found unable to delete tmp log

[marce1000]

 - Some advisories ,1) look at port counters for interfaces where the access points are connected too on the switch(s). check if the error counters are 'idle'         2) Use latest firmware available            3) If all of that does not help , involve Cisco : https://www.cisco.com/c/en/us/support/web/tsd-cisco-small-business-support-center-contacts.html

 M.

[AlanO]

Thanks for you help with this, but I'm not sure what you mean when you say look at the port counters for interfaces.  I'm running pfsense if that helps. I've got one other AP on the network, a CBW143ACM-B-NA mesh extender. This also seems to be rock solid. Any help would be appreciated. I fear that try to get Cisco involved will cost more than all the hardware I've spent!

[marce1000]

 - Make sure  that pfsense isn't blocking any connections between the access points.

 M.

[AlanO]

The pfsense configuration is virtually right out of the box. I've got a couple of port forwards setup but nothing exotic.  I don't see anything in the configuration that could result in failed communication.  I'm using the latest software, 10.7.1.0.   

Could this be a hardware error?   

[marce1000]

        >...Could this be a hardware error?   

 I doubt it, disable the pfsense or remove it (temporarily) as a test.

 M.

[AlanO]

Update... I actually have three APs on my network. The third is a CBW143 Mesh extender.  I disconnected it from the network and the CBW140 was stable - no more un-joining!  I reconnected the Mesh extender and it's still fine.  Go figure. Hope this helps someone else, perhaps someone out there knows why.