cancel
Showing results forĀ 
Search instead forĀ 
Did you mean:Ā 
cancel
8987
Views
0
Helpful
1
Replies

SFF8472-3-THRESHOLD_VIOLATION error on WS-C3850-48T & WS-C3850-48U

stephenauxter
Level 1
Level 1

I have been receiving syslog error %SFF8472-3-THRESHOLD_VIOLATION on a few of our Cisco Catalyst 3850 model switches. We have roughly 35 of these devices in district, and nearly all of them have been upgraded from 16.3.7 (Denali) to 16.9.4 (Fuji) as recently as 3 weeks ago. I am currently receiving this error on 2 of these switches, and each time it is reported from the same interface on the device.

 

Here is an example:
Jan 16 2020 20:41:53 EST: %SFF8472-3-THRESHOLD_VIOLATION: Te2/1/4: Rx power high warning; Operating value: 2.5 dBm, Threshold value: 0.4 dBm.
Jan 16 2020 20:31:52 EST: %SFF8472-3-THRESHOLD_VIOLATION: Te2/1/4: Rx power high warning; Operating value: 2.2 dBm, Threshold value: 0.4 dBm.
Jan 16 2020 20:21:52 EST: %SFF8472-3-THRESHOLD_VIOLATION: Te2/1/4: Rx power high warning; Operating value: 2.5 dBm, Threshold value: 0.4 dBm.

 

I have never received these errors at any other time until after the upgrade to 16.9.4. The threshold violation always reports from the same switches on the same interface at various intervals. However, I never see a threshold violation from the other endpoint of the connection.

 

In other community forums, I have seen reports where this is simply a cosmetic bug and can be ignored. Or, upgrading the IOS version is a possibility - except that 16.9.4 is the current recommended version for a Catalyst 3850. Even comments of replacing fiber cabling or other modular components has been suggested.

 

Does anyone have any suggestions or guidance for me?

1 Accepted Solution

Accepted Solutions

Reza Sharifi
Hall of Fame
Hall of Fame

It is cosmetic bug that Cisco apparently has not fixed even in 16.9.4 version. Sometime, if you admin shut the interface, the error goes away but that is not always the case. So, you may want to give it a try and test.

HTH

View solution in original post

1 Reply 1

Reza Sharifi
Hall of Fame
Hall of Fame

It is cosmetic bug that Cisco apparently has not fixed even in 16.9.4 version. Sometime, if you admin shut the interface, the error goes away but that is not always the case. So, you may want to give it a try and test.

HTH

Review Cisco Networking for a $25 gift card