Hi Michael,
i think the problem is that the scan function is not using the context. The context is only used by the normal check function.
I took a look at the source and only found the context used by “snmpwalk” and “snmpwalk on suboid”.
You should report this as a bug i think if the context is already needed by the scan function.
Best regards
Andreas
···
Michael Nydegger m.nydegger@ftsystems.ch schrieb am Mo., 7. Nov. 2016 um 19:10 Uhr:
Hi Andreas
Thank you very much for this hint.
With your command (cmk --debug -vvvvvI hostname) I cloud successfully
find the source of the problem: the “-n” parameter is not added into the
snmpget command
The command line parameter is as followed: "Getting OID
.1.3.6.1.2.1.1.1.0: Running 'snmpget -v3 -l ‘authPriv’ -a ‘md5’ -u
‘[hostname]’ -A ‘[password]’ -x ‘DES’ -X ‘[password]’ -m ‘’ -M ‘’ -On
-OQ -Oe -Ot [ip address] .1.3.6.1.2.1.1.1.0’"
When I manually add the “-n” parameter and execute the command, I’ve got
an answer from the printer: snmpget -v3 -l ‘authPriv’ -a ‘md5’ -u
‘[hostname]’ -A ‘[password]’ -x ‘DES’ -X ‘[password]’ -m ‘’ -M ‘’ -On
-OQ -Oe -Ot [ip address] .1.3.6.1.2.1.1.1.0 -n Jetdirect
I’ve set the parameter “SNMPv3 contexts to use in requests” also before
I write this question. The parameter "SNMPv3 contexts to use in
requests" is also listes in the parameters of the host. As far as I know
the WATO configuration is correct.
Why does “SNMPv3 contexts to use in requests” not set the “-n Jetdirect”
parameter?
Does anyone else also has this effect?
Is this a bug?
Thanks for your help.
Greetings Michael
–
ft systems gmbh - IT Lösungen für KMU
Michael Nydegger
Bürglistrasse 61
CH-8400 Winterthur
Am 07.11.2016 um 13:08 schrieb Andreas Döhler:
Hi Michael,
this depends on the used Check_MK version - if you use the Enterprise
version with inline SNMP then i don’t know how you can view the used
commands.
If you switch to classic SNMP or use the RAW edition you see the used
SNMP commands if you try to do a “cmk --debug -vvvvvI hostname”
best regards
Andreas
