SNMP error Reason: (noSuchName)

Troubleshooting
,
1

CMK version: CRE 2.3.0p22
OS version: Ubuntu 22.04

**Error message: ERROR: SNMP error
Error in packet
Reason: (noSuchName) There is no such variable name in this MIB.
Failed object: .1.3.6.1.4.1.2036.2.1.1.4.0
**

Output of “cmk --debug -vvn hostname”: (If it is a problem with checks or plugins)
Since one month a SNMP monitored host (Synology NAS) didn’t work again due to time out. Nothing has changed at the host during this period. I didn’t find a reason for this. Finally I deleted all cached data for this host and deleted and discovered all services of this host. This brought back a successful monitoring but I still investigated an issue with SNMP.
On the command line I see these errors:

OMD[inseo]:~/tmp$ cmk -v INS-Backup33
+ FETCHING DATA
ERROR: SNMP error
Error in packet
Reason: (noSuchName) There is no such variable name in this MIB.
Failed object: .1.3.6.1.4.1.2036.2.1.1.4.0


ERROR: SNMP error
Error in packet
Reason: (noSuchName) There is no such variable name in this MIB.
Failed object: .1.3.6.1.4.1.232.2.2.4.2.0


No piggyback files for 'INS-Backup33'. Skip processing.
No piggyback files for '10.x.x.x'. Skip processing.
Get piggybacked data
CPU load             15 min load: 0.27, 15 min load per core: 0.03 (8 cores)
CPU utilization      Total CPU: 0.38%
Disk IO dm-0         [52], Read: 0.00 B/s, Write: 0.00 B/s
Disk IO dm-1         [53], Read: 0.00 B/s, Write: 0.00 B/s
  :
Update               Update Status: Unavailable, Current Version: DSM 7.2-72806
Uptime               Up since 2024-12-02 06:41:46, Uptime: 13 days 5 hours
+ EXECUTING INVENTORY PLUGINS
 inv_if: ok
 mem_used: ok
 snmp_info: ok
No piggyback files for 'INS-Backup33'. Skip processing.
No piggyback files for '10.x.x.x'. Skip processing.
[snmp] Success, [piggyback] Success (but no data found for this host), execution time 12.9 sec | execution_time=12.920 user_time=0.120 system_time=0.020 children_user_time=0.390 children_system_time=0.190 cmk_time_snmp=12.200 cmk_time_agent=0.000

Yes, this error is not comming from CMK it comes from SNMP.

snmpget -v1 -c xxxxxx -m "" -M "" -t 20.00 -On -OQ -Oe -Ot 10.x.x.x .1.3.6.1.4.1.232.2.2.4.2.0'
ERROR: SNMP error
Error in packet
Reason: (noSuchName) There is no such variable name in this MIB.
Failed object: .1.3.6.1.4.1.232.2.2.4.2.0

My question is, how can I remove/solve this error? As I wrote, finally I did a brand new discovery. Why is CMK asking for this OID? I have a 2nd Synology NAS where this error don’t occur.
regards Robi
INS-Backup33.debug.txt (33.8 KB)

2

I can’t tell you why CMK checks for these OIDs, but I looked for them in the code base, and the first seems to belong to Quantum Storage, the second to HP Proliant devices:

3

Is this issue specific to SNMPv1, or does it happen with v2 or v3 as well?

4

I didn’t try any other SNMP version. I don’t know (didn’t check) if the box also supports SNMP v3. But, as I wrote, there is a 2nd similar box using the same CMK rules but don’t produce this error msg.

5

Then you want to understand, what the difference between those two devices is.

6

Yes, that’s right. On what does CMK select which OIDs to query?

7

That is based on the check plugins. They register for certain criteria, e.g., the SysDesc.
You can see which plugins register themselves when running cmk -Ivv $HOST.

8

This topic was automatically closed 365 days after the last reply. New replies are no longer allowed. Contact an admin if you think this should be re-opened.