[ZBXNEXT-4935] Substitute SNMP_NOSUCHOBJECT|SNMP_NOSUCHINSTANCE with a value Created: 2019 Jan 02 Updated: 2019 Jan 02 |
|
Status: | Open |
Project: | ZABBIX FEATURE REQUESTS |
Component/s: | Proxy (P), Server (S) |
Affects Version/s: | 4.0.2 |
Fix Version/s: | None |
Type: | Change Request | Priority: | Trivial |
Reporter: | Joost Bekkers | Assignee: | Andris Zeila |
Resolution: | Unresolved | Votes: | 1 |
Labels: | SNMP | ||
Remaining Estimate: | Not Specified | ||
Time Spent: | Not Specified | ||
Original Estimate: | Not Specified |
Attachments: | patch-src_zabbix__server_poller_checks__snmp.c |
Description |
With some snmp tables, instead of setting a field to some equivalent of 'down', the entire row is removed. Some examples of this: OSPF neighbor state: OSPF-MIB::ospfNbrState When polling such an OID the host returns either SNMP_NOSUCHOBJECT or SNMP_NOSUCHINSTANCE. The item becomes "not supported" and it is rather difficult to write a trigger for it. In most cases I've encountered there is a value defined for 'down', so it would be great is you could use that value and ignore the SNMP_NOSUCH* error. I have a patch that does this by extending the OID syntax. Can't attach it to this issue: "JIRA could not attach the file as there was a missing token. Please try attaching the file again." For static OIDs you can append an equal-sign '=' and the value you want to use For dynamic OIDs an optional forth parameter is used as the value to used in case of SNMP_NOSUCH* |
Comments |
Comment by Joost Bekkers [ 2019 Jan 02 ] |
I was able to attach the patch after creating the issue. |