-
-
Notifications
You must be signed in to change notification settings - Fork 2.2k
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
FortiSwitch - SNMP bug? #15747
Comments
Looks like a bug on this FortiSwitch 200E precisely, yes. Please open a case at the vendor. |
Thanks. Created a ticket at FortiNet. Will follow up! |
Having a hard time convincing FortiNet that this is a their-problem and not a me-problem. |
Issue has been escalated to Fortinet Engineering My initial conclusion that it's limited to the 200-FPOE was wrong. All their switches have the same issue, but it's more prominent on the 200-FPOE's. 148F for example has the same problem. Index with ID 4 is missing from entPhysicalTable
|
The problem
I noticed from my PR #15735 that I had some weird non-working sensors on 200E-series switches:
Did some digging, turns out for this model (sw fw 7.4.0) the switch seems to be skipping a few indexes in the ENTITY-SENSOR-MIB. I'd appreciate if someone can confirm this is wrong behavior from the switch:
The ENTITY-SENSOR-MIB starts with index 4 and stops at 14. While ENTITY-MIB starts with 1 (as expected) and ends with 10. So the ENTITY-SENSOR-MIB indexes do not correspond to the ENTITY-MIB indexes.
This is not supposed to happen, correct? If so I'll submit a bug report at FortiNet
Currently this causes the power supply at ENTITY-SENSOR-MIB index 10 to be named as 'Fan3'.
I can confirm this is not an issue on 400-series switches.
Output of ./validate.php
What was the last working version of LibreNMS?
No response
Device info
FortiSwitch 242E
Discovery output
Poller output
The text was updated successfully, but these errors were encountered: