Randomly wireless APs getting reboot. Last reboot reason showing as "Power loss". But there is no any power issues.

[SMK91]

Hi Guys,

I have 42 wireless APs (cisco AIR-CAP3702E-E-K9). All the APs getting rebooted time to time without any pattern. The last rebooted reason showing as "Power loss".

LKKURXA157 uptime is 1 day, 10 hours, 53 minutes
System returned to ROM by power-on
System image file is "flash:/ap3g2-k9w8-mx.153-3.JF10/ap3g2-k9w8-xx.153-3.JF10"
Last reload reason: Power Loss

Until now, we have done several things to resolve this issue. Until no any improvement.

1. Upgraded to latest recommended version.

2. To isolate the power issue we have Installed a PoE switch to provide the PoE power to one AP (earlier all the APs powered up with power injector).

2. Monitor the states of the selected POE powered AP , Observed that AP also showing last reboot reason as "Power Loss". But PoE switch has good uptime.

3. Enabled the AP core dump feature. But there is no any crash logs.

These are the logs generated from APs.

---------------Show msglog---------------

Message Log Severity Level ...................... ERROR
*spamApTask0: Jan 02 15:03:37.983: %LWAPP-3-VENDOR_PLD_VALIDATE_ERR: spam_lrad.c:11913 Validation of SPAM_VENDOR_SPECIFIC_PAYLOAD(185) with length=9 failed - AP 84:b2:61:b9:d5:10
*spamApTask5: Jan 02 15:03:27.282: %CAPWAP-3-DTLS_CLOSED_ERR: capwap_ac_sm.c:7076 84:b2:61:b9:d5:10: DTLS connection closed forAP 10:110:16:121 (55340), Controller: 10:110:16:23 (5246) Echo Timer Expiry
*spamApTask5: Jan 02 15:03:27.281: %CAPWAP-3-ECHO_ERR: capwap_ac_sm.c:7821 Did not receive heartbeat reply; AP: 84:b2:61:b9:d5:10
*Dot1x_NW_MsgTask_2: Jan 02 15:01:42.485: %DOT1X-3-ABORT_AUTH: 1x_bauth_sm.c:487 Authentication Aborted for client 78:61:7c:28:c8:4a Abort Reason:DOT1X RESTARTED DUE TO EAPOL-START/CLIENT ROAM

Please advise.

[Scott Fella]

I don’t have any other suggestions. If your cabling and patches are good, your ports and rj45 ends don’t have any dirt/dust, your switch has enough PoE and you have no modules, then I don’t know what to say but try to use a different code. One thing to keep in mind is that CDP and LLDP should not be enabled on the ports that APs are connected to, if so, disable LLDP on those ports and see if that helps.

[SMK91]

Thanks Scott-
I'll check that one also.

[alexandre.jr1]

@Scott Fella - just for my benefits why CDP and LLDP should not be enabled on the ports that APs are connected to? 

[Scott Fella]

TAC has seen AP’s negotiate LLDP and have reloaded in my crash files. There is no need to have LLDP enabled on ports Cisco AP’s are connected to.