You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
You're doing something opposite to what check_netint is deigned to do with it optimizations which are aimed at minimizing number of queries and obtaining all results together ....
So --maxrepetitions=1 effectively turns off bulk snmp, which results in many more queries for table queries. And splitting @oid_perf into blocks of 10 results in many more queries for single OIDs. That you have to do it all points to bug in your vendor's SNMP implementation. You really should contact their tech support.
Now I will take your feedback here and in the future may add option to limit number of SNMP OIDs retrieved together for those with buggy vendor software. However this should not be a common case use.
I understand that this is indeed contrary to the optimizations, but I had the issue with lots of linux servers, just centos servers with standard snmp. Take there into account 8 interfaces, some bondings, venet interfaces and such et voila: no output any more ... I really did test the limits of it all and some just have too many interfaces for snmp to handle in one go.
I needed to add this for the performance output to work, even after setting the octetlength to 65535:
also, in a number of cases the snmp call get_table failed on me, so I needed to add
to every get_table call.
The text was updated successfully, but these errors were encountered: