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
Improve SNMP result handling for non-numeric results #311
Comments
I'm pretty sure this is fixed in the 1.2.x branch. |
Indeed, this seems to be fixed in latest 1.2.x branch. But maybe this fix brought me a new problem where input script isn't working anymore - because of new placed quotes.
And compared to this with spine release 1.2.24:
|
Do the following
Send the results. |
|
I've just fixed this. Try again. Marking this closed as I have found my mistake and corrected it now. |
In which commit? |
Here. |
Thank you TheWitness, the latest 1.2.x branch made it working. |
Oh no, it seems I was a bit too hasty. A bulkget gives me all values I would expect:
Now I spine where only the last two OIDs bring me a value.
I have no clue, other devices should draw two graphs and both are working. An other one has four and only three are there. |
It seems to depend on how many snmp bulkget I configure for each device:
If I look at the wireshark data structure with max 30 OIDs per get where at the end I only receive the last two values. |
Describe the bug
There are devices with unusual complex SNMP query result. Such a value can contain numeric value together with unit and text.
snmpget -v2c -c xxx host .1.3.6.1.4.1.1991.1.1.3.3.10.1.4.17.1 -Ovqa "-008.6806 dBm Normal"
This will lead to a NaN situation in Cacti.
The same graph is working using cmd.php oder realtime-monitoring.
Screenshots
normal mode
realtime mode
Server (please complete the following information):
Additional context
cacti.log:
2023-07-18 18:11:19 - SPINE: Poller[1] PID[78909] PT[139655334712896] WARNING: Invalid Response, Device[81] HT[1] DS[20783] SNMP: v2: <device>, dsname: snIfMonitoringTxPwr, oid: .1.3.6.1.4.1.1991.1.1.3.3.10.1.3.17.1, value: -001.9661 dBm Normal
Spine debugging output:
The text was updated successfully, but these errors were encountered: