That's basically a bug in the way Cisco reports some fiber interfaces warning thresholds when they aren't in use. What you see in the CLI is not the same as what you get when you query for those thresholds with SNMP, and Solarwinds is working based on what it sees in SNMPunfortunately. It's super annoying and I tend to either disable the sensor or switch to the envmon hardware health mib. If you wanted to be more thorough you would need to over ride the built in thresholds for those sensors and specify the correct thresholds, but I'm usually not motivated enough to do so.
I always recommend to modify the thresholds instead of disabling the sensor. I only recommend disabling the sensor when the data reported is correct (for example when it says temperature is 0 degrees when it is not).
Modifying thresholds you will get alerts when you really need to.
Installation | Consultancy | Training | Licenses