[ZBX-860] "No Such Instance" snmp status not recognised Created: 2009 Apr 09 Updated: 2017 May 30 Resolved: 2012 Feb 09 |
|
| Status: | Closed |
| Project: | ZABBIX BUGS AND ISSUES |
| Component/s: | Server (S) |
| Affects Version/s: | None |
| Fix Version/s: | 1.8.11, 2.0.0rc1 |
| Type: | Incident report | Priority: | Major |
| Reporter: | richlv | Assignee: | Unassigned |
| Resolution: | Fixed | Votes: | 2 |
| Labels: | snmp | ||
| Remaining Estimate: | Not Specified | ||
| Time Spent: | Not Specified | ||
| Original Estimate: | Not Specified | ||
| Environment: |
1.6.4 on sles10 sp2, net-snmp 5.3.0.1 |
||
| Description |
|
if device does not have a particular oid that is queried, zabbix logs and reports on the frontend : 0x81 is reported by net-snmp on the same box as : No Such Instance currently exists at this OID to ease the debugging and provide more useful messages, it would be nice to display such a message instead of the quite mysterious 0x81 type one. |
| Comments |
| Comment by Alexander Vladishev [ 2012 Feb 09 ] |
|
The problem still in pre-1.8.11, r25278. |
| Comment by Alexander Vladishev [ 2012 Feb 09 ] |
|
Fixed in the development branch svn://svn.zabbix.com/branches/dev/ZBX-860 |
| Comment by dimir [ 2012 Feb 10 ] |
|
Successfully tested. Check my small changes in r25324. <Sasha> Thanks! |
| Comment by Alexander Vladishev [ 2012 Feb 10 ] |
|
Fixed in version pre-1.8.11 (revision 25330) and pre-1.9.10 (revision 25331) |