CMK version: Checkmk Managed Services Edition 2.4.0p12
OS version: Ubuntu 22.04.5 LTS
We are tring to monitor an Fortigate via SNMv3 AuthPriv with AES256 and SHA256. The basic Check_MK Service is OK but the Check_MK Inventory goes into Crit with following Error Message.
Error message: Services: all up to date, Host labels: all up to date, [snmp] Cannot fetch system description OID .1.3.6.1.2.1.1.1.0. Please check your SNMP configuration. Possible reason might be: Wrong credentials, wrong SNMP version, Firewall rules, etc.CRIT, execution time 6.1 sec
We don’t discover any services for the Fortigate. snmwalks from the server are sucessful as normal user and also when we do it from su SITE. One change we did in CMK is changing the snmp backend to classic, this didn’T change anything though.
Output of “cmk --debug -vvn hostname”:
value store: loading from diskCheckmk version 2.4.0p12
FETCHING DATASource: SourceInfo(hostname=‘FGT-1’, ipaddress=‘xxx.xxx.xxx.xxx’, ident=‘snmp’, fetcher_type=<FetcherType.SNMP: 7>, source_type=<SourceType.HOST: 1>)[cpu_tracking] Start [7f93df2dca70]Read from cache: SNMPFileCache(path_template=/omd/sites/SITE/tmp/check_mk/data_source_cache/snmp/{mode}/FGT-1, max_age=MaxAge(checking=0, discovery=450.0, inventory=450.0), simulation=False, use_only_cache=False, file_cache_mode=6)Not using cache (Too old. Age is 135 sec, allowed is 0 sec)Write data to cache file /omd/sites/SITE/tmp/check_mk/data_source_cache/snmp/checking/FGT-1Trying to acquire lock on /omd/sites/SITE/tmp/check_mk/data_source_cache/snmp/checking/FGT-1Got lock on /omd/sites/SITE/tmp/check_mk/data_source_cache/snmp/checking/FGT-1Releasing lock on /omd/sites/SITE/tmp/check_mk/data_source_cache/snmp/checking/FGT-1Released lock on /omd/sites/SITE/tmp/check_mk/data_source_cache/snmp/checking/FGT-1[cpu_tracking] Stop [7f93df2dca70 - Snapshot(process=posix.times_result(user=0.0, system=0.0, children_user=0.0, children_system=0.0, elapsed=0.010000001639127731))]Source: SourceInfo(hostname=‘FGT-1’, ipaddress=‘xxx.xxx.xxx.xxx’, ident=‘piggyback’, fetcher_type=<FetcherType.PIGGYBACK: 4>, source_type=<SourceType.HOST: 1>)[cpu_tracking] Start [7f93df9cffb0]Read from cache: NoCache(path_template=/dev/null, max_age=MaxAge(checking=0.0, discovery=0.0, inventory=0.0), simulation=False, use_only_cache=False, file_cache_mode=1)0 piggyback files for ‘FGT-1’.0 piggyback files for ‘xxx.xxx.xxx.xxx’.Get piggybacked data[cpu_tracking] Stop [7f93df9cffb0 - Snapshot(process=posix.times_result(user=0.0, system=0.0, children_user=0.0, children_system=0.0, elapsed=0.0))][cpu_tracking] Start [7f93df8aa3c0]
PARSE FETCHER RESULTSHostKey(hostname=‘FGT-1’, source_type=<SourceType.HOST: 1>) → Add sections: HostKey(hostname=‘FGT-1’, source_type=<SourceType.HOST: 1>) → Add sections: Received no piggyback data0 piggyback files for ‘FGT-1’.[cpu_tracking] Stop [7f93df8aa3c0 - Snapshot(process=posix.times_result(user=0.0, system=0.0, children_user=0.0, children_system=0.0, elapsed=0.0))][snmp] Success, [piggyback] Success (but no data found for this host), execution time 0.0 sec | execution_time=0.010 user_time=0.000 system_time=0.000 children_user_time=0.000 children_system_time=0.000 cmk_time_snmp=0.010 cmk_time_agent=0.000