Ethernet Tab

Have anSM which errors evident on the ethernet tab, not showing this on other SM's on our AP. 

Some of our recommendation would be :

Replaced SMPS if cont. climbing/ replacement PMP-450 and Install new ground block, and new cable run, then proceed inspect ethernet tab.  InErrors/CrcErrors are slowly climbing / lost links.

Was wondering if any else has any ideas? Could this be power releated? SM going bad?

I've included logs.

Ethernet Statistics
 


Link Detected :
8
Link Uptime :
8 minutes, 30 seconds
Link Lost :
8
Undersized Toss Count :
0
inoctets Count :
112151798
inucastpkts Count :
1125859
Innucastpkts Count :
33223
indiscards Count :
0
inerrors Count :
3503
inunknownprotos Count :
0
outoctets Count :
1847221446
outucastpktsCount :
1187357
outnucastpkts Count :
557794
outdiscards Count :
0
outerrors Count :
0
CRC Error :
3503
RcvFifoNoBuf :
0
Late Collision :
0
Excessive Collision :
0
Tx Underrun :
0
Carrier Sense Lost :
0
No Carrier :
0
Large Frame :
0
Runt Frame :
0
Excessive Deferrals :
0
 
SM Session Log

01/01/2016 : 00:00:39 UTC : Event: SMSESACTIVATE, NewState: REGISTERING, Flag 0
01/01/2016 : 00:00:39 UTC : Event: SMSESINS, NewState: REGISTERED, Flag 19
01/01/2016 : 00:00:39 UTC : Event: SMAUTHORMSG, NewState: REGISTERED, Flag 0
repeated 2 times
02/16/2018 : 12:20:20 UTC : Event: SMSESFAIL, MsgType: OOS, NewState: OOSERVICE, Flag 0
02/16/2018 : 12:22:40 UTC : Event: SMSESACTIVATE, NewState: REGISTERING, Flag 0
02/16/2018 : 12:22:40 UTC : Event: SMSESINS, NewState: REGISTERED, Flag 19
02/16/2018 : 12:22:40 UTC : Event: SMAUTHORMSG, NewState: REGISTERED, Flag 0
repeated 2 times
 
SM Power Adjust Log03/15/2018 : 09:08:44 UTC : Event: SMSESMSG, MsgType: PASRSP, NewState: REGISTERED, Flag 26
03/15/2018 : 09:09:44 UTC : Event: SMSESMSG, MsgType: PAREQTO, NewState: REGISTERED, Flag 0
03/15/2018 : 09:09:44 UTC : Event: SMSESMSG, MsgType: PASRSP, NewState: REGISTERED, Flag 26
03/15/2018 : 09:10:44 UTC : Event: SMSESMSG, MsgType: PAREQTO, NewState: REGISTERED, Flag 0
03/15/2018 : 09:10:44 UTC : Event: SMSESMSG, MsgType: PASRSP, NewState: REGISTERED, Flag 26
03/15/2018 : 09:11:44 UTC : Event: SMSESMSG, MsgType: PAREQTO, NewState: REGISTERED, Flag 0
Device Agent Log
03/15/2018 : 09:46:47 UTC : : Not enough credentials, trying to get zero touch token
03/15/2018 : 09:46:47 UTC : : Attempting (re)connection in 5 seconds
03/15/2018 : 09:46:52 UTC : : Not enough credentials, trying to get zero touch token
03/15/2018 : 09:46:52 UTC : : Attempting (re)connection in 5 seconds
03/15/2018 : 09:46:57 UTC : : Not enough credentials, trying to get zero touch token
03/15/2018 : 09:46:57 UTC : : Attempting (re)connection in 5 seconds

Typically CRC Errors are caused by bad cable, bad Ethernet port, or interference on the Ethernet line.

Since you said you replaced the cable and power supply already, this part should have been corrected.  Are you creating the cable on site (i.e. crimping cable at the radio side)?  Was the same crimp tool used both times?

What is the data side plugging into?  A home router of some kind?  Was this device changed with something else (like direct to a PC or something) to elminate that port (connection) as being an issue.

These kinds of errors are typically not caused by hardware failure, but it's not impossible.