Fortigate 60D all services are not discovering

Hi,
I am using check-mk version RAW 1.6.0p7 .monitor a fortigate firewall with snmp.All the services are not discovering like cpu, memory ,vpn,uptime etc.

please find the screen shot

Hey,
the service “Uptime” is there. Can you try to run “Full discovery” in WATO? What is happening?
BR

thank you for reply

i have done full discovery , still i cannot see the fortigate checks .

what FortiOS version is it?
What SNMP version do you use there?

Can you try
cmk --debug -nv -vII FW-AL-ARBOR-LODGE
and post the output here?

1 Like

another possibility is to discover the checks by hand in your console:

for example as site user

cmk -Ivv --checks=fortigate_cpu your-host

then you see what happend

FW-CC-CONCORDIA:

  • FETCHING DATA
    [mgmt_snmp] No persisted sections loaded
    [mgmt_snmp] Not using cache (Don’t try it)
    [mgmt_snmp] Execute data source
    SNMP scan:
    Getting OID .1.3.6.1.2.1.1.1.0: Running ‘snmpget -v2c -c public -m “” -M “” -On -OQ -Oe -Ot 192.168.24.1 .1.3.6.1.2.1.1.1.0’
    ERROR: SNMP error
    Timeout: No Response from 192.168.24.1.failed.
    [mgmt_snmp] ERROR: Cannot fetch system description OID .1.3.6.1.2.1.1.1.0. This might be OK for some bogus devices. In that case please configure the ruleset “Hosts without system description OID” to tell Check_MK not to fetch the system description and system object OIDs.
    Traceback (most recent call last):
    File “/omd/sites/nsm/bin/cmk”, line 94, in
    exit_status = modes.call(mode_name, mode_args, opts, args)
    File “/omd/sites/nsm/lib/python/cmk_base/modes/_ init _.py”, line 72, in call
    return mode.handler_function(*handler_args)
    File “/omd/sites/nsm/lib/python/cmk_base/modes/check_mk.py”, line 1498, in mode_discover
    discovery.do_discovery(hostnames, options.get(“checks”), options[“discover”] == 1)
    File “/omd/sites/nsm/lib/python/cmk_base/discovery.py”, line 130, in do_discovery
    multi_host_sections = _get_host_sections_for_discovery(sources, use_caches=use_caches)
    File “/omd/sites/nsm/lib/python/cmk_base/discovery.py”, line 889, in get_host_sections_for_discovery
    return sources.get_host_sections(max_cachefile_age)
    File “/omd/sites/nsm/lib/python/cmk_base/data_sources/
    init _.py”, line 279, in get_host_sections
    host_sections_from_source = source.run()
    File “/omd/sites/nsm/lib/python/cmk_base/data_sources/abstract.py”, line 133, in run
    raw_data, is_cached_data = self._get_raw_data()
    File “/omd/sites/nsm/lib/python/cmk_base/data_sources/abstract.py”, line 182, in _get_raw_data
    raw_data = self._execute()
    File “/omd/sites/nsm/lib/python/cmk_base/data_sources/snmp.py”, line 177, in _execute
    check_plugin_names = self.get_check_plugin_names()
    File “/omd/sites/nsm/lib/python/cmk_base/data_sources/abstract.py”, line 290, in get_check_plugin_names
    return self._gather_check_plugin_names()
    File “/omd/sites/nsm/lib/python/cmk_base/data_sources/snmp.py”, line 168, in _gather_check_plugin_names
    for_mgmt_board=self._for_mgmt_board)
    File “/omd/sites/nsm/lib/python/cmk_base/snmp_scan.py”, line 52, in gather_snmp_check_plugin_names
    for_mgmt_board=for_mgmt_board))
    File “/omd/sites/nsm/lib/python/cmk_base/snmp_scan.py”, line 86, in _snmp_scan
    “description and system object OIDs.” % (name, oid))
    cmk_base.exceptions.MKSNMPError: Cannot fetch system description OID .1.3.6.1.2.1.1.1.0. This might be OK for some bogus devices. In that case please configure the ruleset “Hosts without system description OID” to tell Check_MK not to fetch the system description and system object OIDs.

OMD[nsm]:~$ cmk -Ivv --checks=fortigate_cpu FW-CC-CONCORDIA
Discovering services on: FW-CC-CONCORDIA
FW-CC-CONCORDIA:

  • FETCHING DATA
    [mgmt_snmp] No persisted sections loaded
    [mgmt_snmp] Not using cache (Don’t try it)
    [mgmt_snmp] Execute data source
    [mgmt_snmp] Write data to cache file /omd/sites/nsm/tmp/check_mk/data_source_cache/mgmt_snmp/FW-CC-CONCORDIA
    Try aquire lock on /omd/sites/nsm/tmp/check_mk/data_source_cache/mgmt_snmp/FW-CC-CONCORDIA
    Got lock on /omd/sites/nsm/tmp/check_mk/data_source_cache/mgmt_snmp/FW-CC-CONCORDIA
    Releasing lock on /omd/sites/nsm/tmp/check_mk/data_source_cache/mgmt_snmp/FW-CC-CONCORDIA
    Released lock on /omd/sites/nsm/tmp/check_mk/data_source_cache/mgmt_snmp/FW-CC-CONCORDIA
    [snmp] No persisted sections loaded
    [snmp] Not using cache (Don’t try it)
    [snmp] Execute data source
    [snmp] fortigate_cpu: Fetching data
    Running ‘snmpbulkwalk -Cr10 -v2c -c NewSeasons -m “” -M “” -Cc -OQ -OU -On -Ot 192.168.24.1 .1.3.6.1.4.1.12356.1.8’
    [snmp] Write data to cache file /omd/sites/nsm/tmp/check_mk/data_source_cache/snmp/FW-CC-CONCORDIA
    Try aquire lock on /omd/sites/nsm/tmp/check_mk/data_source_cache/snmp/FW-CC-CONCORDIA
    Got lock on /omd/sites/nsm/tmp/check_mk/data_source_cache/snmp/FW-CC-CONCORDIA
    Releasing lock on /omd/sites/nsm/tmp/check_mk/data_source_cache/snmp/FW-CC-CONCORDIA
    Released lock on /omd/sites/nsm/tmp/check_mk/data_source_cache/snmp/FW-CC-CONCORDIA
  • EXECUTING DISCOVERY PLUGINS (1)
    Trying discovery with: fortigate_cpu
    Try aquire lock on /omd/sites/nsm/var/check_mk/autochecks/FW-CC-CONCORDIA.mk
    Got lock on /omd/sites/nsm/var/check_mk/autochecks/FW-CC-CONCORDIA.mk
    Releasing lock on /omd/sites/nsm/var/check_mk/autochecks/FW-CC-CONCORDIA.mk
    Released lock on /omd/sites/nsm/var/check_mk/autochecks/FW-CC-CONCORDIA.mk
    SUCCESS - Found no new services, no new host labels

OMD[nsm]:~$ cmk -lvv – checks=fortigate_memory FW-CC-CONCORDIA
OMD[nsm]:~$

OMD[nsm]:~$ cmk --debug -vvI FW-CC-CONCORDIA
Discovering services on: FW-CC-CONCORDIA
FW-CC-CONCORDIA:

  • FETCHING DATA
    [mgmt_snmp] No persisted sections loaded
    [mgmt_snmp] Not using cache (Don’t try it)
    [mgmt_snmp] Execute data source
    SNMP scan:
    Getting OID .1.3.6.1.2.1.1.1.0: Running ‘snmpget -v2c -c public -m “” -M “” -On -OQ -Oe -Ot 192.168.24.1 .1.3.6.1.2.1.1.1.0’
    ERROR: SNMP error
    Timeout: No Response from 192.168.24.1.
    failed.
    [mgmt_snmp] ERROR: Cannot fetch system description OID .1.3.6.1.2.1.1.1.0. This might be OK for some bogus devices. In that case please configure the ruleset “Hosts without system description OID” to tell Check_MK not to fetch the system description and system object OIDs.
    Traceback (most recent call last):
    File “/omd/sites/nsm/bin/cmk”, line 94, in
    exit_status = modes.call(mode_name, mode_args, opts, args)
    File “/omd/sites/nsm/lib/python/cmk_base/modes/ init .py”, line 72, in call
    return mode.handler_function(*handler_args)
    File “/omd/sites/nsm/lib/python/cmk_base/modes/check_mk.py”, line 1498, in mode_discover
    discovery.do_discovery(hostnames, options.get(“checks”), options[“discover”] == 1)
    File “/omd/sites/nsm/lib/python/cmk_base/discovery.py”, line 130, in do_discovery
    multi_host_sections = _get_host_sections_for_discovery(sources, use_caches=use_caches)
    File “/omd/sites/nsm/lib/python/cmk_base/discovery.py”, line 889, in _get_host_sections_for_discovery
    return sources.get_host_sections(max_cachefile_age)
    File “/omd/sites/nsm/lib/python/cmk_base/data_sources/ init .py”, line 279, in get_host_sections
    host_sections_from_source = source.run()
    File “/omd/sites/nsm/lib/python/cmk_base/data_sources/abstract.py”, line 133, in run
    raw_data, is_cached_data = self._get_raw_data()
    File “/omd/sites/nsm/lib/python/cmk_base/data_sources/abstract.py”, line 182, in _get_raw_data
    raw_data = self._execute()
    File “/omd/sites/nsm/lib/python/cmk_base/data_sources/snmp.py”, line 177, in _execute
    check_plugin_names = self.get_check_plugin_names()
    File “/omd/sites/nsm/lib/python/cmk_base/data_sources/abstract.py”, line 290, in get_check_plugin_names
    return self._gather_check_plugin_names()
    File “/omd/sites/nsm/lib/python/cmk_base/data_sources/snmp.py”, line 168, in _gather_check_plugin_names
    for_mgmt_board=self._for_mgmt_board)
    File “/omd/sites/nsm/lib/python/cmk_base/snmp_scan.py”, line 52, in gather_snmp_check_plugin_names
    for_mgmt_board=for_mgmt_board))
    File “/omd/sites/nsm/lib/python/cmk_base/snmp_scan.py”, line 86, in _snmp_scan
    “description and system object OIDs.” % (name, oid))
    cmk_base.exceptions.MKSNMPError: Cannot fetch system description OID .1.3.6.1.2.1.1.1.0. This might be OK for some bogus devices. In that case please configure the ruleset “Hosts without system description OID” to tell Check_MK not to fetch the system description and system object OIDs.
    OMD[nsm]:~$

i am getting following errors still i cannot discovery the fortigate services we are using Fortigate ios version 6.0.6. it took the snmp walk 5 seconds
OMD[nsm]:~$ snmpwalk -v 2c -c Xxxxx FW-CC-CONCORDIA
snmpwalk: Unknown host (FW-CC-CONCORDIA) (Resource temporarily unavailable)

OMD[nsm]:~$ cmk --debug -nv -vII FW-CC-CONCORDIA
Discovering services on: FW-CC-CONCORDIA
FW-CC-CONCORDIA:

  • FETCHING DATA
    [mgmt_snmp] No persisted sections loaded
    [mgmt_snmp] Not using cache (Don’t try it)
    [mgmt_snmp] Execute data source
    SNMP scan:
    Skipping system description OID (Set .1.3.6.1.2.1.1.1.0 and .1.3.6.1.2.1. 1.2.0 to “”)
    Using cached OID .1.3.6.1.2.1.1.2.0:
    Using cached OID .1.3.6.1.2.1.1.2.0:
    Using cached OID .1.3.6.1.2.1.1.1.0:
    Using cached OID .1.3.6.1.2.1.1.1.0:
    Using cached OID .1.3.6.1.2.1.1.1.0:
    Using cached OID .1.3.6.1.2.1.1.1.0:
    Using cached OID .1.3.6.1.2.1.1.2.0:
    Using cached OID .1.3.6.1.2.1.1.2.0:
    Using cached OID .1.3.6.1.2.1.1.1.0:
    Using cached OID .1.3.6.1.2.1.1.2.0:
    Using cached OID .1.3.6.1.2.1.1.2.0:
    Getting OID .1.3.6.1.4.1.232.2.2.4.2.0: Running ‘snmpget -v2c -c public - m “” -M “” -On -OQ -Oe -Ot 192.168.24.1 .1.3.6.1.4.1.232.2.2.4.2.0’
    ERROR: SNMP error
    Timeout: No Response from 192.168.24.1.

failed.
Using cached OID .1.3.6.1.2.1.1.2.0:
Using cached OID .1.3.6.1.2.1.1.2.0:
Using cached OID .1.3.6.1.2.1.1.2.0:
Using cached OID .1.3.6.1.2.1.1.2.0:
Using cached OID .1.3.6.1.2.1.1.2.0:
Using cached OID .1.3.6.1.2.1.1.2.0:
Using cached OID .1.3.6.1.2.1.1.2.0:
Using cached OID .1.3.6.1.2.1.1.1.0:
Using cached OID .1.3.6.1.2.1.1.2.0:
Using cached OID .1.3.6.1.2.1.1.2.0:
Using cached OID .1.3.6.1.2.1.1.2.0:
Using cached OID .1.3.6.1.2.1.1.2.0:
Using cached OID .1.3.6.1.2.1.1.2.0:
Using cached OID .1.3.6.1.2.1.1.2.0:
Using cached OID .1.3.6.1.2.1.1.2.0:
Using cached OID .1.3.6.1.2.1.1.2.0:
Using cached OID .1.3.6.1.2.1.1.1.0:
Using cached OID .1.3.6.1.2.1.1.2.0:
Using cached OID .1.3.6.1.2.1.1.1.0:
Getting OID .1.3.6.1.4.1.1139.21.2.2.8.1.*: Running 'snmpgetnext -Cf -v2c -c public -m “” -M “” -On -OQ -Oe -Ot 192.168.24.1 .1.3.6.1.4.1.1139.21.2.2.8.1 ’
ERROR: SNMP error
Timeout: No Response from 192.168.24.1.

failed.
Using cached OID .1.3.6.1.2.1.1.2.0:
Using cached OID .1.3.6.1.4.1.232.2.2.4.2.0: None
Using cached OID .1.3.6.1.2.1.1.2.0:
Using cached OID .1.3.6.1.2.1.1.2.0:
Using cached OID .1.3.6.1.2.1.1.1.0:
Using cached OID .1.3.6.1.2.1.1.2.0:
Using cached OID .1.3.6.1.2.1.1.2.0:
Using cached OID .1.3.6.1.2.1.1.2.0:
Using cached OID .1.3.6.1.2.1.1.2.0:
Using cached OID .1.3.6.1.2.1.1.2.0:
Using cached OID .1.3.6.1.2.1.1.2.0:
Using cached OID .1.3.6.1.2.1.1.2.0:
Using cached OID .1.3.6.1.2.1.1.1.0:
Using cached OID .1.3.6.1.4.1.232.2.2.4.2.0: None
Using cached OID .1.3.6.1.2.1.1.2.0:
Using cached OID .1.3.6.1.2.1.1.2.0:
Using cached OID .1.3.6.1.2.1.1.1.0:
Using cached OID .1.3.6.1.2.1.1.2.0:
Using cached OID .1.3.6.1.2.1.1.2.0:
Using cached OID .1.3.6.1.2.1.1.2.0:
Using cached OID .1.3.6.1.2.1.1.2.0:
Using cached OID .1.3.6.1.2.1.1.1.0:
Using cached OID .1.3.6.1.2.1.1.2.0:
Using cached OID .1.3.6.1.2.1.1.2.0:
Using cached OID .1.3.6.1.2.1.1.2.0:
Using cached OID .1.3.6.1.2.1.1.2.0:
Using cached OID .1.3.6.1.2.1.1.2.0:
Using cached OID .1.3.6.1.2.1.1.2.0:
Using cached OID .1.3.6.1.2.1.1.2.0:
Using cached OID .1.3.6.1.2.1.1.2.0:
Using cached OID .1.3.6.1.2.1.1.2.0:
Using cached OID .1.3.6.1.2.1.1.2.0:
Using cached OID .1.3.6.1.2.1.1.2.0:
Using cached OID .1.3.6.1.2.1.1.2.0:
Using cached OID .1.3.6.1.2.1.1.2.0:
Using cached OID .1.3.6.1.2.1.1.2.0:
Using cached OID .1.3.6.1.4.1.232.2.2.4.2.0: None
Using cached OID .1.3.6.1.2.1.1.1.0:
Using cached OID .1.3.6.1.2.1.1.2.0:
Using cached OID .1.3.6.1.2.1.1.1.0:
Using cached OID .1.3.6.1.2.1.1.1.0:
Using cached OID .1.3.6.1.4.1.232.2.2.4.2.0: None
Using cached OID .1.3.6.1.2.1.1.2.0:
Using cached OID .1.3.6.1.2.1.1.2.0:
Using cached OID .1.3.6.1.2.1.1.2.0:
Using cached OID .1.3.6.1.2.1.1.2.0:
Using cached OID .1.3.6.1.2.1.1.2.0:
Using cached OID .1.3.6.1.2.1.1.2.0:
Using cached OID .1.3.6.1.2.1.1.2.0:
Using cached OID .1.3.6.1.2.1.1.2.0:
Using cached OID .1.3.6.1.2.1.1.1.0:
Using cached OID .1.3.6.1.2.1.1.2.0:
Using cached OID .1.3.6.1.2.1.1.2.0:
Using cached OID .1.3.6.1.2.1.1.1.0:
Using cached OID .1.3.6.1.2.1.1.2.0:
Using cached OID .1.3.6.1.2.1.1.2.0:
Using cached OID .1.3.6.1.2.1.1.2.0:
Using cached OID .1.3.6.1.2.1.1.2.0:
Using cached OID .1.3.6.1.2.1.1.2.0:
Using cached OID .1.3.6.1.2.1.1.2.0:
Using cached OID .1.3.6.1.2.1.1.2.0:
Using cached OID .1.3.6.1.2.1.1.2.0:
Using cached OID .1.3.6.1.2.1.1.2.0:
Using cached OID .1.3.6.1.2.1.1.2.0:
Using cached OID .1.3.6.1.2.1.1.2.0:
Using cached OID .1.3.6.1.2.1.1.2.0:
Using cached OID .1.3.6.1.2.1.1.1.0:
Using cached OID .1.3.6.1.2.1.1.2.0:
Using cached OID .1.3.6.1.2.1.1.1.0:
Using cached OID .1.3.6.1.2.1.1.1.0:
Using cached OID .1.3.6.1.2.1.1.1.0:
Using cached OID .1.3.6.1.2.1.1.2.0:
Using cached OID .1.3.6.1.2.1.1.1.0:
Using cached OID .1.3.6.1.2.1.1.2.0:
Using cached OID .1.3.6.1.2.1.1.2.0:
Using cached OID .1.3.6.1.2.1.1.1.0:
Getting OID .1.3.6.1.2.1.43.11.1.1.6.1.1: Running ‘snmpget -v2c -c public -m “” -M “” -On -OQ -Oe -Ot 192.168.24.1 .1.3.6.1.2.1.43.11.1.1.6.1.1’
ERROR: SNMP error
Timeout: No Response from 192.168.24.1.

failed.
Using cached OID .1.3.6.1.2.1.1.2.0:
Using cached OID .1.3.6.1.2.1.1.2.0:
Using cached OID .1.3.6.1.2.1.1.1.0:
Using cached OID .1.3.6.1.2.1.1.1.0:
Getting OID .1.3.6.1.4.1.14848.2.1.1.1.0: Running ‘snmpget -v2c -c public -m “” -M “” -On -OQ -Oe -Ot 192.168.24.1 .1.3.6.1.4.1.14848.2.1.1.1.0’
ERROR: SNMP error
Timeout: No Response from 192.168.24.1.

failed.
Using cached OID .1.3.6.1.2.1.1.2.0:
Using cached OID .1.3.6.1.2.1.1.1.0:
Using cached OID .1.3.6.1.2.1.1.1.0:
Using cached OID .1.3.6.1.4.1.1139.21.2.2.8.1.: None
Using cached OID .1.3.6.1.2.1.1.2.0:
Using cached OID .1.3.6.1.2.1.1.2.0:
Using cached OID .1.3.6.1.2.1.1.1.0:
Using cached OID .1.3.6.1.2.1.1.2.0:
Using cached OID .1.3.6.1.2.1.1.1.0:
Getting OID .1.3.6.1.2.1.31.1.1.1.6.
: Running ‘snmpgetnext -Cf -v2c -c p ublic -m “” -M “” -On -OQ -Oe -Ot 192.168.24.1 .1.3.6.1.2.1.31.1.1.1.6’
ERROR: SNMP error
Timeout: No Response from 192.168.24.1.

Please anyone can help why i am unable to discovery the fortigate services previous i was able to discovery the services , i have deleted and re added the devices from them on wards i cannot discovery the full services .

Hi @srkatarapu, this seems now like a duplicate of your other post? I am unable to discovery the fortigate 60D services i am using the RAW 1.6.0p7 version

If it’s the same, could you please close one of them and keep the discussion in only one place? :slight_smile:

Thanks!

1 Like