THRESHOLD_VIOLATION: Rx power high warning

[vincent.villaluzii]

Our Cisco 2960X switches display warning, the optical signal received by transceiver is too high. Is there anyone can explain and advise how to resolve the issue?

May 21 00:14:47.726: %SFF8472-5-THRESHOLD_VIOLATION: Gi1/0/27: Rx power high warning; Operating value: -1.8 dBm, Threshold value: -3.0 dBm.
May 21 00:14:56.559: %SFF8472-5-THRESHOLD_VIOLATION: Gi1/0/28: Rx power high warning; Operating value: 0.3 dBm, Threshold value: -3.0 dBm.
May 21 00:24:48.669: %SFF8472-5-THRESHOLD_VIOLATION: Gi1/0/27: Rx power high warning; Operating value: -1.8 dBm, Threshold value: -3.0 dBm.
May 21 00:24:57.508: %SFF8472-5-THRESHOLD_VIOLATION: Gi1/0/28: Rx power high warning; Operating value: 0.3 dBm, Threshold value: -3.0 dBm.

[Joseph W. Doherty]

https://en.wikipedia.org/wiki/Optical_attenuator

[vincent.villaluzii]

What will be the tolerance value of Rx Power? There is a standard fiber optics will be use for GLC-LH-SMD Transceiver to avoid the error?

[Joseph W. Doherty]

Often, I believe, the device might show what it considers the "ideal" range.

See if this helps: https://community.cisco.com/t5/optical-networking/optical-receive-power-warning-operating-above-threshold/td-p/2545244

[Leo Laohoo]

1. Bounce the port.
2. Clean the fibre patch cables
3. Clean the optics
4. Replace the fibre patch cables
5. Replace the optics

[Joseph W. Doherty]

Leo, just wondering, I would suspect what you suggest, excluding bouncing the port, would likely be more likely to help if the issue was RX too low, rather than too high.  Yes, no?

[Leo Laohoo]

---

@Joseph W. Doherty wrote:

would likely be more likely to help if the issue was RX too low, rather than too high.  Yes, no?

---

Ever since we've switch to DOM, our NMS gets flooded with these "too high" or "too low" alarms.  We go to through the motions listed above just to fix it.  

I agree what you said, but I've seen worst.