SNMP V3 on snmp walk
SNMP V3 on snmp walk
We were not able to find an SNMP v3 snmp walk. Is this feature coming, or can this be added to the snmp walk feature?
-
sreinhardt
- -fno-stack-protector
- Posts: 4366
- Joined: Mon Nov 19, 2012 12:10 pm
Re: SNMP V3 on snmp walk
The built in snmpwalk wizard should work with v3 just fine. What issues are you having? Also what version of XI are you using, and are there any updates for your wizards?
Nagios-Plugins maintainer exclusively, unless you have other C language bugs with open-source nagios projects, then I am happy to help! Please pm or use other communication to alert me to issues as I no longer track the forum.
Re: SNMP V3 on snmp walk
If we attempt to run snmp walk without a v2 community string, it fails, even though I have v3 selected. I can select SHA for auth protocol, but where can I select AES encryption?
The generic monitoring wizard is also having the same issue.
Nagios verion: Nagios XI 2012R1.6
The generic monitoring wizard is also having the same issue.
Nagios verion: Nagios XI 2012R1.6
-
scottwilkerson
- DevOps Engineer
- Posts: 19396
- Joined: Tue Nov 15, 2011 3:11 pm
- Location: Nagios Enterprises
- Contact:
Re: SNMP V3 on snmp walk
Looks like there was a bit of missing functionality in these wizards. Attached is a corrected snmpwalk.zip you can install through Admin -> Manage Config Wizards
You do not have the required permissions to view the files attached to this post.
-
scottwilkerson
- DevOps Engineer
- Posts: 19396
- Joined: Tue Nov 15, 2011 3:11 pm
- Location: Nagios Enterprises
- Contact:
Re: SNMP V3 on snmp walk
And an updated SNMP wizard
You do not have the required permissions to view the files attached to this post.
-
msbensonstk
- Posts: 34
- Joined: Wed Apr 11, 2012 1:01 pm
Re: SNMP V3 on snmp walk
Looks like there is some command check logic missing from the updated snmpwalk.zip you posted.
Setting up a check with the snmpwalk wizard using version 3 authNoPriv settings on hrSWRunPath.1 produces the following error and output:
data_label problem - No data received from host
/usr/bin/snmpget -t 1 -r 5 -m HOST-RESOURCES-MIB -v 3 [authpriv] <host address omitted>:161 hrSWRunPath.1
Looking at the snmpget documentation, there are several flags missing to correctly execute a snmpget command using the version 3 protocol. The following command does produce output:
/usr/bin/snmpget -t 1 -r 5 -m HOST-RESOURCES-MIB -v 3 -l authpriv -u nagiosxi -a SHA -A <password omitted> -x AES -X <password omitted> <host address omitted>:161 hrSWRunPath.1
Setting up a check with the snmpwalk wizard using version 3 authNoPriv settings on hrSWRunPath.1 produces the following error and output:
data_label problem - No data received from host
/usr/bin/snmpget -t 1 -r 5 -m HOST-RESOURCES-MIB -v 3 [authpriv] <host address omitted>:161 hrSWRunPath.1
Looking at the snmpget documentation, there are several flags missing to correctly execute a snmpget command using the version 3 protocol. The following command does produce output:
/usr/bin/snmpget -t 1 -r 5 -m HOST-RESOURCES-MIB -v 3 -l authpriv -u nagiosxi -a SHA -A <password omitted> -x AES -X <password omitted> <host address omitted>:161 hrSWRunPath.1
-
scottwilkerson
- DevOps Engineer
- Posts: 19396
- Joined: Tue Nov 15, 2011 3:11 pm
- Location: Nagios Enterprises
- Contact:
Re: SNMP V3 on snmp walk
Can you take the $ARG1$ value for the check and the $HOSTADDRESS$ to populate the following line and try to run the fillowing from the commandline
Then post the output (obfuscating sensitive details)
Thanks
Code: Select all
/check_snmp -H $HOSTADDRESS$ $ARG1$Thanks
-
msbensonstk
- Posts: 34
- Joined: Wed Apr 11, 2012 1:01 pm
Re: SNMP V3 on snmp walk
Sorry I lost track of this post.
We have found a differnt way to do the monitoring we were trying to accomplish with the SNMP walk check. So, unless you want to try and troubleshoot this further for your benifit, we can problaby end this thread here.
We have found a differnt way to do the monitoring we were trying to accomplish with the SNMP walk check. So, unless you want to try and troubleshoot this further for your benifit, we can problaby end this thread here.