Hi Andreas,
Many thanks indeed!
I changed the code-line and did the checks via cli.
BTW: I found one config error in my setup which has lead to the [Errno 111]
I can confirm, that the check makes use of the snmp context! That’s great 
But of course I got still error in the debug output 
OMD[<SITE>]:~$ cmk --debug -vvn <HOSTNAME>
[cpu_tracking] Start with phase 'busy'
Check_MK version 1.6.0p17
Try aquire lock on /omd/sites/<SITE>/tmp/check_mk/counters/<HOSTNAME>
Got lock on /omd/sites/<SITE>/tmp/check_mk/counters/<HOSTNAME>
Releasing lock on /omd/sites/<SITE>/tmp/check_mk/counters/<HOSTNAME>
Released lock on /omd/sites/<SITE>/tmp/check_mk/counters/<HOSTNAME>
Loading autochecks from /omd/sites/<SITE>/var/check_mk/autochecks/<HOSTNAME>.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] if: Fetching data
Running 'snmpbulkwalk -Cr10 -v3 -l authPriv -a sha -u monitor -A <PASSWD> -x AES -X <PASSWD> -m "" -M "" -n Jetdirect -Cc -OQ -OU -On -Ot <IP-ADDRESS> .1.3.6.1.2.1.2.2.1.1'
Running 'snmpbulkwalk -Cr10 -v3 -l authPriv -a sha -u monitor -A <PASSWD> -x AES -X <PASSWD> -m "" -M "" -n Jetdirect -Cc -OQ -OU -On -Ot <IP-ADDRESS> .1.3.6.1.2.1.2.2.1.2'
Running 'snmpbulkwalk -Cr10 -v3 -l authPriv -a sha -u monitor -A <PASSWD> -x AES -X <PASSWD> -m "" -M "" -n Jetdirect -Cc -OQ -OU -On -Ot <IP-ADDRESS> .1.3.6.1.2.1.2.2.1.3'
Running 'snmpbulkwalk -Cr10 -v3 -l authPriv -a sha -u monitor -A <PASSWD> -x AES -X <PASSWD> -m "" -M "" -n Jetdirect -Cc -OQ -OU -On -Ot <IP-ADDRESS> .1.3.6.1.2.1.2.2.1.5'
Running 'snmpbulkwalk -Cr10 -v3 -l authPriv -a sha -u monitor -A <PASSWD> -x AES -X <PASSWD> -m "" -M "" -n Jetdirect -Cc -OQ -OU -On -Ot <IP-ADDRESS> .1.3.6.1.2.1.2.2.1.8'
Running 'snmpbulkwalk -Cr10 -v3 -l authPriv -a sha -u monitor -A <PASSWD> -x AES -X <PASSWD> -m "" -M "" -n Jetdirect -Cc -OQ -OU -On -Ot <IP-ADDRESS> .1.3.6.1.2.1.2.2.1.10'
Running 'snmpbulkwalk -Cr10 -v3 -l authPriv -a sha -u monitor -A <PASSWD> -x AES -X <PASSWD> -m "" -M "" -n Jetdirect -Cc -OQ -OU -On -Ot <IP-ADDRESS> .1.3.6.1.2.1.2.2.1.11'
Running 'snmpbulkwalk -Cr10 -v3 -l authPriv -a sha -u monitor -A <PASSWD> -x AES -X <PASSWD> -m "" -M "" -n Jetdirect -Cc -OQ -OU -On -Ot <IP-ADDRESS> .1.3.6.1.2.1.2.2.1.12'
Running 'snmpbulkwalk -Cr10 -v3 -l authPriv -a sha -u monitor -A <PASSWD> -x AES -X <PASSWD> -m "" -M "" -n Jetdirect -Cc -OQ -OU -On -Ot <IP-ADDRESS> .1.3.6.1.2.1.2.2.1.13'
Running 'snmpbulkwalk -Cr10 -v3 -l authPriv -a sha -u monitor -A <PASSWD> -x AES -X <PASSWD> -m "" -M "" -n Jetdirect -Cc -OQ -OU -On -Ot <IP-ADDRESS> .1.3.6.1.2.1.2.2.1.14'
Running 'snmpbulkwalk -Cr10 -v3 -l authPriv -a sha -u monitor -A <PASSWD> -x AES -X <PASSWD> -m "" -M "" -n Jetdirect -Cc -OQ -OU -On -Ot <IP-ADDRESS> .1.3.6.1.2.1.2.2.1.16'
Running 'snmpbulkwalk -Cr10 -v3 -l authPriv -a sha -u monitor -A <PASSWD> -x AES -X <PASSWD> -m "" -M "" -n Jetdirect -Cc -OQ -OU -On -Ot <IP-ADDRESS> .1.3.6.1.2.1.2.2.1.17'
Running 'snmpbulkwalk -Cr10 -v3 -l authPriv -a sha -u monitor -A <PASSWD> -x AES -X <PASSWD> -m "" -M "" -n Jetdirect -Cc -OQ -OU -On -Ot <IP-ADDRESS> .1.3.6.1.2.1.2.2.1.18'
Running 'snmpbulkwalk -Cr10 -v3 -l authPriv -a sha -u monitor -A <PASSWD> -x AES -X <PASSWD> -m "" -M "" -n Jetdirect -Cc -OQ -OU -On -Ot <IP-ADDRESS> .1.3.6.1.2.1.2.2.1.19'
Running 'snmpbulkwalk -Cr10 -v3 -l authPriv -a sha -u monitor -A <PASSWD> -x AES -X <PASSWD> -m "" -M "" -n Jetdirect -Cc -OQ -OU -On -Ot <IP-ADDRESS> .1.3.6.1.2.1.2.2.1.20'
Running 'snmpbulkwalk -Cr10 -v3 -l authPriv -a sha -u monitor -A <PASSWD> -x AES -X <PASSWD> -m "" -M "" -n Jetdirect -Cc -OQ -OU -On -Ot <IP-ADDRESS> .1.3.6.1.2.1.2.2.1.21'
Running 'snmpbulkwalk -Cr10 -v3 -l authPriv -a sha -u monitor -A <PASSWD> -x AES -X <PASSWD> -m "" -M "" -n Jetdirect -Cc -OQ -OU -On -Ot <IP-ADDRESS> .1.3.6.1.2.1.2.2.1.6'
[snmp] printer_alerts: Fetching data
Running 'snmpbulkwalk -Cr10 -v3 -l authPriv -a sha -u monitor -A <PASSWD> -x AES -X <PASSWD> -m "" -M "" -n Jetdirect -Cc -OQ -OU -On -Ot <IP-ADDRESS> .1.3.6.1.2.1.43.18.1.1.2'
Running 'snmpbulkwalk -Cr10 -v3 -l authPriv -a sha -u monitor -A <PASSWD> -x AES -X <PASSWD> -m "" -M "" -n Jetdirect -Cc -OQ -OU -On -Ot <IP-ADDRESS> .1.3.6.1.2.1.43.18.1.1.4'
Running 'snmpbulkwalk -Cr10 -v3 -l authPriv -a sha -u monitor -A <PASSWD> -x AES -X <PASSWD> -m "" -M "" -n Jetdirect -Cc -OQ -OU -On -Ot <IP-ADDRESS> .1.3.6.1.2.1.43.18.1.1.5'
Running 'snmpbulkwalk -Cr10 -v3 -l authPriv -a sha -u monitor -A <PASSWD> -x AES -X <PASSWD> -m "" -M "" -n Jetdirect -Cc -OQ -OU -On -Ot <IP-ADDRESS> .1.3.6.1.2.1.43.18.1.1.7'
Running 'snmpbulkwalk -Cr10 -v3 -l authPriv -a sha -u monitor -A <PASSWD> -x AES -X <PASSWD> -m "" -M "" -n Jetdirect -Cc -OQ -OU -On -Ot <IP-ADDRESS> .1.3.6.1.2.1.43.18.1.1.8'
[snmp] printer_input: Fetching data
Running 'snmpbulkwalk -Cr10 -v3 -l authPriv -a sha -u monitor -A <PASSWD> -x AES -X <PASSWD> -m "" -M "" -n Jetdirect -Cc -OQ -OU -On -Ot <IP-ADDRESS> .1.3.6.1.2.1.43.8.2.1.13'
ERROR: SNMP error: Timeout: No Response from <IP-ADDRESS>
[snmp] ERROR: SNMP Error on <IP-ADDRESS>: Timeout: No Response from <IP-ADDRESS> (Exit-Code: 1)
[cpu_tracking] Pop phase 'snmp' (Stack: ['busy', 'snmp'])
CRIT - SNMP Error on <IP-ADDRESS>: Timeout: No Response from <IP-ADDRESS> (Exit-Code: 1)
My take is, that everything good until the snmpbulkwalk hits the last OID .1.3.6.1.2.1.43.8.2.1.13.
But why in snmpbulkwlak not just ignoring the missing OID response?
Any way the exclude this OID or any other way to get this error solved?
Kind regards
Georg