WAN port getting high power alarm logs , What is the command to check the status and how to rectify this.
cisco ASR-920-4SZ-A
Dec 3 08:46:54.397 %SFF8472-3-THRESHOLD_VIOLATION: Te0/0/2: Rx power high warning; Operating value: -0.6 dBm, Threshold value: -3.0 dBm.
Dec 3 09:06:54.788 %SFF8472-3-THRESHOLD_VIOLATION: Te0/0/2: Rx power high warning; Operating value: -0.6 dBm, Threshold value: -3.0 dBm.
Hello Aparna
Your Te0/0/2 is an optical interface that terminates fiber optic cabling. There is no command you can use to determine the problem here. It looks like a physical layer problem, and you will have to deal with it by checking your physical infrastructure.
This syslog message appears whenever the incoming signal surpasses the acceptable level of power that the device can correctly process. In other words, the light received on the fiber optic cable is too bright, brighter than the maximum that the transceiver can handle.
This error can be a result of several things. First of all, make sure that you are using the correct type of fiber and the correct transceiver. Sometimes if you mismatch multimode fiber with a single-mode transceiver (or visa versa), you may get such errors. Similarly, make sure that the optical patch cords you are using are of the same type as the infrastructure fiber optics along the whole optical path.
If your cabling and transceivers are of the correct types, then the next thing you should check is damaged fiber optic cables. Sometimes a bent or damaged cable can amplify the incoming light and cause the error.
It’s always a good idea to try to test the connectivity of the specific port directly with another switch with other transceivers and other cables to determine if it is the transceivers/cables causing the problem or if it is internal to the router.
Finally, if none of these issues seem to be the source of the problem, it would always be a good idea to open a TAC case with Cisco. Sometimes such errors are only cosmetic (they appear but do not affect the actual operation of the device), and may need to be fixed with a newer version of the IOS. Take a look at this CIsco community post about a similar topic.
I hope this has been helpful!
Laz