Updated to 2.1 and SNMPv1 interface graphs won't show

CMK version:
2.1.0p15
OS version:
Windows 10
Error message:
None
Output of “cmk --debug -vvn hostname”: (If it is a problem with checks or plugins)
Command ‘cmk’ not found, but can be installed with:
snap install cloudmonkey
(There is a step missing with these instructions)

There looks to be an issue in CheckMK Raw with SNMPv1 and graphs for monitoring purposes

When polling interface bandwidth on a Cisco Nexus switch, on SNMPv1 (it doesn’t work on v2c, we’re stuck with it in v1) and CMK2.0 the graphs worked fine.

Now on CMK 2.1 and the graphs will not show unless a Service rescan is done on the switch and then that tab left open, not practical for the long term, but it at least reveals logged graph data.

Any tips?

Hi username,

before we go into troubleshooting I want to point out that cmk is a checkmk command and has nothing
to do with cloudmonkey!
If you have a ssh session with your checkmk server there will be a cmk command. No need to install anything new or change any instructions.
Have a look at Checkmk on the command line - Understanding and using command line commands

1 Like

I did note there was a step missing with the command?
I got Checkmk version 2.1.0p15 out of the debug command on the site

I would really appreciate some help restoring SNMPv1 graphs for our displays.
Thanks!

Let us try to solve this issue.

If you do a ‘remove all and find new’ operation and then ’ Apply all’ are the services showing up on your host?
image

And don’t forget to activate the pending changes!

Sorry for the delay,
Running NX-OS - Version 6.0(2)U6(10)
Remove/Rescan with SNMP v2c - No discovery information available
Rescan with SNMPv1 and the Perf-o-meter is still disappearing from the interfaces and takes the graphing with it, why is that happening?

The measured SNMP execution time is 14 seconds and every update 30-60 seconds later a different perf for the interfaces appears… or disappears on just this switch.

This is a buggy experience and quite the nuisance to the network team as we’re trying to accurately monitor over 7000 services and 275 devices.

What check/monitor parameters can be changed to allow CMK more time to collect the PerfData?

I am also working to build a new CMK instance to see if it behaves the same or different with this switch.

Hi there.
This ist the Blog post you are looking for:
https://checkmk.com/blog/snmp-troubleshooting

Sounds a little bit strange to me. The amount that you want to Monitor shouldnt be a problem.

A new instance ist maybe a good Idea and quickly done via the omd command.

Another thing ist snmpv1. Whith snmpv2 and v3 you are able to collect many OIDs with one call.
So maybe you can get it working?

New instance has the same issue

The SNMP guide is a good place to start, but how do you run the cmk interrogate commands on an IP address?

Have a look at Checkmk on the command line - Understanding and using command line commands

Took quite a bit of digging, but this is the solution to turn off bulkwalk on SNMP v2c - Monitoring via SNMP - Monitoring of SNMP devices with Checkmk

V2c works, but bulk requests fail

Some devices support version v2c — and will provide an answer to this in the diagnostics — however, the implementation of the GetBulk command is missing in the protocol. This is used by Checkmk to get as much information as possible with a single request and is very important for the performance.

With such a host, some simple SNMP checks will work — such as SNMP Info or SNMP Uptime, but other services will be missing — especially the network interfaces that must be present on each device.

If you actually have a host where this is the case, you can run it with v2c, but without bulk requests. Configure such a host as follows:

    Set the SNMP version for the host properties to SNMP v1.

    In the Setup > Agents > SNMP rules > Legacy SNMP devices using SNMP v2c rule set, create a rule for the host, and set the value typically to Positive match (Add matching hosts to the set).

This forces the host to use the SNMP v2c protocol — although version 1 has been set — however without bulkwalk. Incidentally, we do not recommend the use of SNMP v1 — even if that is supported — because it does not support 64-bit counters. This can lead to missing or erroneous measurement data for network ports which are subject to heavy traffic.

Glad you figured it out :wink:

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.