SNMP Error bei Alcatel Switch

Moin,

ich habe ein Problem mit der Überwachung von Alcatel-Switchen via SNMP.
Beim anlegen & Testen des Host sieht alles gut aus. Es werden mir bei SNMPv3 alle Informationen, wie in der Dokumentation beschrieben, korrekt angezeigt.

Wenn ich jedoch eine “Volständigen Scan” durchführen möchte bekomme ich folgende Fehlermeldung:

Starting job…

  • FETCHING DATA
    [snmp] Execute data source
    ERROR: SNMP error 5/1 ((genError) A general failure occured)
    [snmp] ERROR: SNMP Error on 10.135.XX.XX while walking .1.3.6.1.4.1.6486.800.1.1.1.1.1.1.1.36. Normally this is caused by a device sending invalid SNMP responses (Details: (genError) A general failure occured (5/1)).
    [piggyback] Execute data source
    No piggyback files for ‘10.135.XX.XX’. Skip processing.
    No piggyback files for ‘10.135.XX.XX’. Skip processing.
    Completed.

Vielleicht wisst Ihr mehr mit der Fehlermeldung anzufangen. Ich werde daraus nicht schlau.
Gruß Michael

PS.: IP geschwärzt

Wichtig wäre hier zuerst die Ausgabe von cmk -D hostname zu überprüfen. Ist hier alles richtig für v3 konfiguriert und zu sehen ist der nächste Schritt ein cmk --debug -vvI hostname für das Discovery.
Sollte dies auch ohne Fehler verlaufen kommt als nächstes noch ein cmk --debug -vvn hostname zur Kontrolle.
Sollte beim Discovery ein Fehler auftreten so ist hier die Ausgabe mit der kompletten Fehlermeldung relevant. Das selbe gilt bei einem Fehler beim letzten cmk Command.

Moin,

erst einmal vielen Dank für die hilfreichen Kommandos.
Jetzt verstehe ich jedoch nicht, wieso das Gerät falsche Antworten zurück gibt.
Der Switch sollte doch mindestens die Standard-SNMP Antworten geben,

OMD[MYSITE]:~$ cmk -D hostname
Addresses: 10.135.XX.XX
Tags: [address_family:ip-v4-only], [agent:special-agents], [criticality:prod], [ip-v4:ip-v4], [networking:lan], [piggyback:auto-piggyback], [site:MYSITE], [snmp:snmp], [snmp_ds:snmp-v2], [tcp:tcp]
Labels:
Host groups: check_mk
Contact groups: all
Agent mode: No Checkmk agent, all configured special agents
Type of agent:
SNMP (Credentials: ‘authPriv, md5, snmp_credentials, snmp_credentials, DES, snmp_credentials’, Bulk walk: yes, Port: 161, Inline: yes)
Process piggyback data from /omd/sites/MYSITE/tmp/check_mk/piggyback/10.135.XX.XX
Services:
checktype item params description groups


OMD[MYSITE]:~$ cmk --debug -vvI 10.135.XX.XX
Discovering services on: 10.135.XX.XX
10.135.XX.XX:
FETCHING DATA
[snmp] No persisted sections loaded
[snmp] Not using cache (Don’t try it)
[snmp] Execute data source
SNMP scan:
Getting OID .1.3.6.1.2.1.1.1.0: Executing SNMP GET of .1.3.6.1.2.1.1.1.0 on 10.135.XX.XX
=> [‘Alcatel-Lucent OS6850E-24 6.4.6.440.R01 Service Release, May 10, 2018.’] OCTETSTR
Alcatel-Lucent OS6850E-24 6.4.6.440.R01 Service Release, May 10, 2018.
Getting OID .1.3.6.1.2.1.1.2.0: Executing SNMP GET of .1.3.6.1.2.1.1.2.0 on 10.135.XX.XX
=> [’.1.3.6.1.4.1.6486.800.1.1.2.1.7.1.46’] OBJECTID
.1.3.6.1.4.1.6486.800.1.1.2.1.7.1.46
Using cached OID .1.3.6.1.2.1.1.2.0: .1.3.6.1.4.1.6486.800.1.1.2.1.7.1.46
Using cached OID .1.3.6.1.2.1.1.2.0: .1.3.6.1.4.1.6486.800.1.1.2.1.7.1.46
Using cached OID .1.3.6.1.2.1.1.1.0: Alcatel-Lucent OS6850E-24 6.4.6.440.R01 Service Release, May 10, 2018.
Using cached OID .1.3.6.1.2.1.1.1.0: Alcatel-Lucent OS6850E-24 6.4.6.440.R01 Service Release, May 10, 2018.
Using cached OID .1.3.6.1.2.1.1.1.0: Alcatel-Lucent OS6850E-24 6.4.6.440.R01 Service Release, May 10, 2018.
Using cached OID .1.3.6.1.2.1.1.1.0: Alcatel-Lucent OS6850E-24 6.4.6.440.R01 Service Release, May 10, 2018.
Using cached OID .1.3.6.1.2.1.1.2.0: .1.3.6.1.4.1.6486.800.1.1.2.1.7.1.46
Using cached OID .1.3.6.1.2.1.1.2.0: .1.3.6.1.4.1.6486.800.1.1.2.1.7.1.46
Using cached OID .1.3.6.1.2.1.1.1.0: Alcatel-Lucent OS6850E-24 6.4.6.440.R01 Service Release, May 10, 2018.
Using cached OID .1.3.6.1.2.1.1.2.0: .1.3.6.1.4.1.6486.800.1.1.2.1.7.1.46
Using cached OID .1.3.6.1.2.1.1.2.0: .1.3.6.1.4.1.6486.800.1.1.2.1.7.1.46
Getting OID .1.3.6.1.4.1.232.2.2.4.2.0: Executing SNMP GET of .1.3.6.1.4.1.232.2.2.4.2.0 on 10.135.XX.XX
=> [None] NOSUCHOBJECT
failed.
BULKWALK GEKÜRZT
Using cached OID .1.3.6.1.2.1.1.2.0: .1.3.6.1.4.1.6486.800.1.1.2.1.7.1.46
Using cached OID .1.3.6.1.2.1.1.2.0: .1.3.6.1.4.1.6486.800.1.1.2.1.7.1.46
Using cached OID .1.3.6.1.2.1.1.2.0: .1.3.6.1.4.1.6486.800.1.1.2.1.7.1.46
Using cached OID .1.3.6.1.2.1.1.1.0: Alcatel-Lucent OS6850E-24 6.4.6.440.R01 Service Release, May 10, 2018.
SNMP scan found alcatel_cpu alcatel_fans alcatel_power alcatel_temp hr_mem if64 mgmt_snmp_info mgmt_snmp_uptime snmp_info snmp_uptime
SNMP filtered check plugin names alcatel_cpu alcatel_fans alcatel_power alcatel_temp hr_mem if64 snmp_info snmp_uptime
Try aquire lock on /omd/sites/MYSITE/tmp/check_mk/snmp_scan_cache/10.135.XX.XX.10.135.XX.XX
Got lock on /omd/sites/MYSITE/tmp/check_mk/snmp_scan_cache/10.135.XX.XX.10.135.XX.XX
Releasing lock on /omd/sites/MYSITE/tmp/check_mk/snmp_scan_cache/10.135.XX.XX.10.135.XX.XX
Released lock on /omd/sites/MYSITE/tmp/check_mk/snmp_scan_cache/10.135.XX.XX.10.135.XX.XX
[snmp] alcatel_cpu: Fetching data
Executing BULKWALK of “.1.3.6.1.4.1.6486.800.1.2.1.16.1.1.1.13” on 10.135.XX.XX
.1.3.6.1.4.1.6486.800.1.2.1.16.1.1.1.13.0 => [26] ‘INTEGER’
[snmp] alcatel_fans: Fetching data
Executing BULKWALK of “.1.3.6.1.4.1.6486.800.1.1.1.3.1.1.11.1.2” on 10.135.XX.XX
.1.3.6.1.4.1.6486.800.1.1.1.3.1.1.11.1.2.569.1 => [2] ‘INTEGER’
.1.3.6.1.4.1.6486.800.1.1.1.3.1.1.11.1.2.569.2 => [2] ‘INTEGER’
.1.3.6.1.4.1.6486.800.1.1.1.3.1.1.11.1.2.569.3 => [2] ‘INTEGER’
[snmp] alcatel_power: Fetching data
Executing BULKWALK of “.1.3.6.1.4.1.6486.800.1.1.1.1.1.1.1.2” on 10.135.XX.XX
.1.3.6.1.4.1.6486.800.1.1.1.1.1.1.1.2.1 => [1] ‘INTEGER’
.1.3.6.1.4.1.6486.800.1.1.1.1.1.1.1.2.65 => [1] ‘INTEGER’
.1.3.6.1.4.1.6486.800.1.1.1.1.1.1.1.2.97 => [1] ‘INTEGER’
.1.3.6.1.4.1.6486.800.1.1.1.1.1.1.1.2.569 => [1] ‘INTEGER’
Executing BULKWALK of “.1.3.6.1.4.1.6486.800.1.1.1.1.1.1.1.36” on 10.135.XX.XX
ERROR: SNMP error 5/1 ((genError) A general failure occured)
[snmp] ERROR: SNMP Error on 10.135.XX.XX while walking .1.3.6.1.4.1.6486.800.1.1.1.1.1.1.1.36. Normally this is caused by a device sending invalid SNMP responses (Details: (genError) A general failure occured (5/1)).
Traceback (most recent call last):
File “/omd/sites/MYSITE/bin/cmk”, line 94, in
exit_status = modes.call(mode_name, mode_args, opts, args)
File “/omd/sites/MYSITE/lib/python/cmk_base/modes/init.py”, line 72, in call
return mode.handler_function(*handler_args)
File “/omd/sites/MYSITE/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/MYSITE/lib/python/cmk_base/discovery.py”, line 134, in do_discovery
multi_host_sections = _get_host_sections_for_discovery(sources, use_caches=use_caches)
File “/omd/sites/MYSITE/lib/python/cmk_base/discovery.py”, line 906, in _get_host_sections_for_discovery
return sources.get_host_sections(max_cachefile_age)
File “/omd/sites/MYSITE/lib/python/cmk_base/data_sources/init.py”, line 279, in get_host_sections
host_sections_from_source = source.run()
File “/omd/sites/MYSITE/lib/python/cmk_base/data_sources/abstract.py”, line 133, in run
raw_data, is_cached_data = self._get_raw_data()
File “/omd/sites/MYSITE/lib/python/cmk_base/data_sources/abstract.py”, line 182, in _get_raw_data
raw_data = self._execute()
File “/omd/sites/MYSITE/lib/python/cmk_base/data_sources/snmp.py”, line 233, in _execute
self._use_snmpwalk_cache)
File “/omd/sites/MYSITE/lib/python/cmk_base/snmp.py”, line 214, in get_snmp_table
use_snmpwalk_cache)
File “/omd/sites/MYSITE/lib/python/cmk_base/snmp.py”, line 538, in _get_snmpwalk
rowinfo = _perform_snmpwalk(snmp_config, check_plugin_name, oid, fetchoid)
File “/omd/sites/MYSITE/lib/python/cmk_base/snmp.py”, line 562, in _perform_snmpwalk
context_name=context_name)
File “/omd/sites/MYSITE/lib/python/cmk_base/cee/inline_snmp.py”, line 201, in walk
(snmp_config.hostname, oid, err_str, err_num, err_ind))
cmk_base.exceptions.MKSNMPError: SNMP Error on 10.135.XX.XX while walking .1.3.6.1.4.1.6486.800.1.1.1.1.1.1.1.36. Normally this is caused by a device sending invalid SNMP responses (Details: (genError) A general failure occured (5/1)).

OMD[MYSITE]:~$ cmk --debug -vvn 10.135.XX.XX
[cpu_tracking] Start with phase ‘busy’
Check_MK version 1.6.0p12
Try aquire lock on /omd/sites/MYSITE/tmp/check_mk/counters/10.135.XX.XX
Got lock on /omd/sites/MYSITE/tmp/check_mk/counters/10.135.XX.XX
Releasing lock on /omd/sites/MYSITE/tmp/check_mk/counters/10.135.XX.XX
Released lock on /omd/sites/MYSITE/tmp/check_mk/counters/10.135.XX.XX
Loading autochecks from /omd/sites/MYSITE/var/check_mk/autochecks/10.135.XX.XX.mk
FETCHING DATA
[cpu_tracking] Push phase ‘snmp’ (Stack: [‘busy’])
[snmp] No persisted sections loaded
[snmp] Not using cache (Don’t try it)
[snmp] Execute data source
[snmp] Write data to cache file /omd/sites/MYSITE/tmp/check_mk/data_source_cache/snmp/10.135.XX.XX
Try aquire lock on /omd/sites/MYSITE/tmp/check_mk/data_source_cache/snmp/10.135.XX.XX
Got lock on /omd/sites/MYSITE/tmp/check_mk/data_source_cache/snmp/10.135.XX.XX
Releasing lock on /omd/sites/MYSITE/tmp/check_mk/data_source_cache/snmp/10.135.XX.XX
Released lock on /omd/sites/MYSITE/tmp/check_mk/data_source_cache/snmp/10.135.XX.XX
[cpu_tracking] Pop phase ‘snmp’ (Stack: [‘busy’, ‘snmp’])
[cpu_tracking] Push phase ‘agent’ (Stack: [‘busy’])
[piggyback] No persisted sections loaded
[piggyback] Execute data source
No piggyback files for ‘10.135.XX.XX’. Skip processing.
No piggyback files for ‘10.135.XX.XX’. Skip processing.
[cpu_tracking] Pop phase ‘agent’ (Stack: [‘busy’, ‘agent’])
[cpu_tracking] End
OK - [snmp] Success, execution time 0.0 sec | execution_time=0.006 user_time=0.000 system_time=0.000 children_user_time=0.000 children_system_time=0.000 cmk_time_snmp=0.002 cmk_time_agent=0.001

Was passiert wenn du die angegebene OID selbst manuell mittels snmpwalk abholst?
Dabei kannst probieren ob das Verhalten dich unterscheidet bei der Benutzung von snmpwalk und snmpbulkwalk.
Falls hier auch schon Fehler kommen wäre das ja ein Firmware Bug beim Switch.

This topic was automatically closed 30 days after the last reply. New replies are no longer allowed.