No snmp latency data received from Nimble

CMK version: 1.6.0p17 cee
OS version: Debian 9 on checkmk server

Error message: Nimble volume checks for Read/Write IO are pending due to no data has been received within the last 1.5 check periods. Only interfaces, SNMP info, Uptime and Volume usage are being monitored properly

Output of “cmk --debug -vvn hostname”: (If it is a problem with checks or plugins)

OMD[sitename]:~$ cmk --debug -vvn [Nimble IP address]
[cpu_tracking] Start with phase 'busy'
Check_MK version 1.6.0p17
Updating IPv4 DNS cache for [Nimble IP address]: [Nimble IP address]
Try aquire lock on /omd/sites/[sitename]/var/check_mk/ipaddresses.cache
Got lock on /omd/sites/[sitename]/var/check_mk/ipaddresses.cache
Releasing lock on /omd/sites/[sitename]/var/check_mk/ipaddresses.cache
Released lock on /omd/sites/[sitename]/var/check_mk/ipaddresses.cache
Try aquire lock on /omd/sites/[sitename]/tmp/check_mk/counters/[Nimble IP address]
Got lock on /omd/sites/[sitename]/tmp/check_mk/counters/[Nimble IP address]
Releasing lock on /omd/sites/[sitename]/tmp/check_mk/counters/[Nimble IP address]
Released lock on /omd/sites/[sitename]/tmp/check_mk/counters/[Nimble IP address]
+ FETCHING DATA
[cpu_tracking] Push phase 'agent' (Stack: ['busy'])
 [piggyback] No persisted sections loaded
 [piggyback] Execute data source
No piggyback files for '[Nimble IP address]'. Skip processing.
No piggyback files for '[Nimble IP address]'. Skip processing.
[cpu_tracking] Pop phase 'agent' (Stack: ['busy', 'agent'])
[cpu_tracking] End
OK - execution time 0.1 sec | execution_time=0.100 user_time=0.090 system_time=0.000 children_user_time=0.000 children_system_time=0.000 cmk_time_agent=0.005

Hi @vu.nguyen,

your Checkmk is terribly out of date. You should upgrade as soon and as far as possible.

Other than that, this sounds like an issue on Nimble site, because it does not seem to provide the data needed properly.

1 Like

Hi @robin.gierse ,
Thanks for your quick help.
Unfortunately, we are unable to upgrade our checkmk for the time being.
In fact, I looked into Nimble site but did not see any further settings there. Anyway I will be checking with Nimble support on this point.

Hi @robin.gierse ,

I just did an snmpwalk to our Nimble for read/write IO and it worked well.

OMD[[sitename]]:~/share/check_mk/checks$ snmpwalk -v2c -c checkmk [Nimble] .1.3.6.1.4.1.37447.1.2.1.3
SNMPv2-SMI::enterprises.37447.1.2.1.3.0 = STRING: "[sitename]-APP-VOL-A"
SNMPv2-SMI::enterprises.37447.1.2.1.3.1 = STRING: "[sitename]-APP-VOL-A"
SNMPv2-SMI::enterprises.37447.1.2.1.3.2 = STRING: "[sitename]-APP-VOL-B"
SNMPv2-SMI::enterprises.37447.1.2.1.3.3 = STRING: "[sitename]-APP-VOL-B"
SNMPv2-SMI::enterprises.37447.1.2.1.3.4 = STRING: "[sitename]-DBA-VOL-A"
SNMPv2-SMI::enterprises.37447.1.2.1.3.5 = STRING: "[sitename]-DBA-VOL-A"
SNMPv2-SMI::enterprises.37447.1.2.1.3.6 = STRING: "[sitename]-DBA-VOL-B"
SNMPv2-SMI::enterprises.37447.1.2.1.3.7 = STRING: "[sitename]-DBA-VOL-B"
OMD[[sitename]]:~/share/check_mk/checks$ snmpwalk -v2c -c checkmk [Nimble] .1.3.6.1.4.1.37447.1.2.1.10
SNMPv2-SMI::enterprises.37447.1.2.1.10.0 = INTEGER: 1
SNMPv2-SMI::enterprises.37447.1.2.1.10.1 = INTEGER: 1
SNMPv2-SMI::enterprises.37447.1.2.1.10.2 = INTEGER: 1
SNMPv2-SMI::enterprises.37447.1.2.1.10.3 = INTEGER: 1
SNMPv2-SMI::enterprises.37447.1.2.1.10.4 = INTEGER: 1
SNMPv2-SMI::enterprises.37447.1.2.1.10.5 = INTEGER: 1
SNMPv2-SMI::enterprises.37447.1.2.1.10.6 = INTEGER: 1
SNMPv2-SMI::enterprises.37447.1.2.1.10.7 = INTEGER: 1
OMD[[sitename]]:~/share/check_mk/checks$ snmpwalk -v2c -c checkmk [Nimble] .1.3.6.1.4.1.37447.1.2.1.13
SNMPv2-SMI::enterprises.37447.1.2.1.13.0 = Counter64: 0
SNMPv2-SMI::enterprises.37447.1.2.1.13.1 = Counter64: 201054158
SNMPv2-SMI::enterprises.37447.1.2.1.13.2 = Counter64: 593083134
SNMPv2-SMI::enterprises.37447.1.2.1.13.3 = Counter64: 43927927
SNMPv2-SMI::enterprises.37447.1.2.1.13.4 = Counter64: 652519675
SNMPv2-SMI::enterprises.37447.1.2.1.13.5 = Counter64: 0
SNMPv2-SMI::enterprises.37447.1.2.1.13.6 = Counter64: 430276770
SNMPv2-SMI::enterprises.37447.1.2.1.13.7 = Counter64: 157339703
OMD[[sitename]]:~/share/check_mk/checks$ snmpwalk -v2c -c checkmk [Nimble] .1.3.6.1.4.1.37447.1.2.1.34
SNMPv2-SMI::enterprises.37447.1.2.1.34.0 = Counter64: 0
SNMPv2-SMI::enterprises.37447.1.2.1.34.1 = Counter64: 738403156
SNMPv2-SMI::enterprises.37447.1.2.1.34.2 = Counter64: 302297082
SNMPv2-SMI::enterprises.37447.1.2.1.34.3 = Counter64: 89770904
SNMPv2-SMI::enterprises.37447.1.2.1.34.4 = Counter64: 986612077
SNMPv2-SMI::enterprises.37447.1.2.1.34.5 = Counter64: 0
SNMPv2-SMI::enterprises.37447.1.2.1.34.6 = Counter64: 308340581
SNMPv2-SMI::enterprises.37447.1.2.1.34.7 = Counter64: 134048478
OMD[[sitename]]:~/share/check_mk/checks$

However checkmk still displayed no data received. The service check command showed check_mk-nimble_latency

I don’t know if checkmk is doing the nimble latency check correctly. Would you mind help on this point?

Thank you!

I can only circle back to the Checkmk upgrade. There might be bugs, preventing proper functionality.
If this is that important to you, an upgrade should be as important at least.

1 Like

Thank you @robin.gierse for kindly help.

1 Like

Hey everyone,

I have the same problem - SNMP is showing data, but check_mk is not showing the latency data.

I am already using 1.6.0p30 (raw), Nimble firmware is also up to date. So if it is a bug, it is not yet fixed in this version (I want to go to Version 2 soon, but did not yet find the time…).

Is there any way to troubleshoot this further, to find the reason why there is no data?

Thanks,

Tobias

Hi @Tobs661,
As far as I know, it could be a visualize matter with the version 1.6 when data can be polled properly from Nimble.
FYI, updating to version 2 worked for me.

2 Likes

Thanks, then I have at least a solution. So for now I will disable the latency sensors, and when I finally get to install v2, I can enable it again…

Thanks!