nagios ver 5.6.8
RHEL 6.10
Target - Windows 2012 R2
SNMP authentication enabled/configured
Firewall UDP confirmed inbound and outbound rules
Snmpwalk command from Nagios host to target "no response from [servername]"
It's got to be something I'm missing, right?
server does not have snmpwalk permission on the target host
-
seaward1983
- Posts: 69
- Joined: Wed Jul 17, 2019 2:09 pm
Re: server does not have snmpwalk permission on the target h
Let's make sure that we can get to the Windows server.
If possible, it may be worth temporarily turning off the Windows firewall, and running the snmpwalk just to test.
Code: Select all
nmap -sU <remoteIPaddress> -p 161,162As of May 25th, 2018, all communications with Nagios Enterprises and its employees are covered under our new Privacy Policy.
Be sure to check out our Knowledgebase for helpful articles and solutions!
Be sure to check out our Knowledgebase for helpful articles and solutions!
-
seaward1983
- Posts: 69
- Joined: Wed Jul 17, 2019 2:09 pm
Re: server does not have snmpwalk permission on the target h
Here's the results -
Starting Nmap 6.47 ( http://nmap.org ) at 2019-12-10 16:02 CST
Nmap scan report for 638579-DWASQL01.rsp.medecision.com (172.21.57.66)
Host is up (0.00028s latency).
PORT STATE SERVICE
161/udp open|filtered snmp
Nmap done: 1 IP address (1 host up) scanned in 0.28 seconds
Starting Nmap 6.47 ( http://nmap.org ) at 2019-12-10 16:02 CST
Nmap scan report for 638579-DWASQL01.rsp.medecision.com (172.21.57.66)
Host is up (0.00028s latency).
PORT STATE SERVICE
161/udp open|filtered snmp
Nmap done: 1 IP address (1 host up) scanned in 0.28 seconds
- Box293
- Too Basu
- Posts: 5126
- Joined: Sun Feb 07, 2010 10:55 pm
- Location: Deniliquin, Australia
- Contact:
Re: server does not have snmpwalk permission on the target h
That output indicates that the firewall ports are correctly open.
This sounds like a security issue. What type of SNMP security did you define on the windows server?
Here is an example command you can execute on your Nagios XI server in a terminal session:
This example uses SNMP v2c security. Replace public with the name of the community you defined on the server.
Replace xxx.xxx.xxx.xxx with the address of the server.
What output do you get?
This sounds like a security issue. What type of SNMP security did you define on the windows server?
Here is an example command you can execute on your Nagios XI server in a terminal session:
Code: Select all
snmpwalk -v 2c -c public xxx.xxx.xxx.xxx -m all 1.3.6.1.4.1Replace xxx.xxx.xxx.xxx with the address of the server.
What output do you get?
As of May 25th, 2018, all communications with Nagios Enterprises and its employees are covered under our new Privacy Policy.
-
seaward1983
- Posts: 69
- Joined: Wed Jul 17, 2019 2:09 pm
Re: server does not have snmpwalk permission on the target h
Okay - it's resolved. This server vmotioned to another hypervisor that didn't have a VLAN configured correctly. I now can do a SNMPwalk and get all sorts of funness.
T-RESOURCES-MIB::hrSWRunStatus.2356 = INTEGER: running(1)
HOST-RESOURCES-MIB::hrSWRunStatus.2532 = INTEGER: running(1)
HOST-RESOURCES-MIB::hrSWRunStatus.2600 = INTEGER: running(1)
HOST-RESOURCES-MIB::hrSWRunStatus.2740 = INTEGER: running(1)
HOST-RESOURCES-MIB::hrSWRunStatus.2760 = INTEGER: running(1)
HOST-RESOURCES-MIB::hrSWRunStatus.2784 = INTEGER: running(1)
HOST-RESOURCES-MIB::hrSWRunStatus.2984 = INTEGER: running(1)
HOST-RESOURCES-MIB::hrSWRunStatus.3084 = INTEGER: running(1)
HOST-RESOURCES-MIB::hrSWRunStatus.3184 = INTEGER: running(1)
HOST-RESOURCES-MIB::hrSWRunStatus.3224 = INTEGER: running(1)
HOST-RESOURCES-MIB::hrSWRunStatus.3324 = INTEGER: running(1)
HOST-RESOURCES-MIB::hrSWRunStatus.3476 = INTEGER: running(1)
HOST-RESOURCES-MIB::hrSWRunStatus.3528 = INTEGER: running(1)
HOST-RESOURCES-MIB::hrSWRunStatus.3536 = INTEGER: running(1)
HOST-RESOURCES-MIB::hrSWRunStatus.3640 = INTEGER: running(1)
HOST-RESOURCES-MIB::hrSWRunStatus.3644 = INTEGER: running(1)
HOST-RESOURCES-MIB::hrSWRunStatus.3816 = INTEGER: running(1)
HOST-RESOURCES-MIB::hrSWRunStatus.3840 = INTEGER: running(1)
HOST-RESOURCES-MIB::hrSWRunStatus.4284 = INTEGER: running(1)
HOST-RESOURCES-MIB::hrSWRunStatus.4820 = INTEGER: running(1)
HOST-RESOURCES-MIB::hrSWRunStatus.5248 = INTEGER: running(1)
HOST-RESOURCES-MIB::hrSWRunStatus.5256 = INTEGER: running(1)
HOST-RESOURCES-MIB::hrSWRunStatus.5392 = INTEGER: running(1)
HOST-RESOURCES-MIB::hrSWRunStatus.5508 = INTEGER: running(1)
HOST-RESOURCES-MIB::hrSWRunStatus.5528 = INTEGER: running(1)
HOST-RESOURCES-MIB::hrSWRunStatus.5536 = INTEGER: running(1)
T-RESOURCES-MIB::hrSWRunStatus.2356 = INTEGER: running(1)
HOST-RESOURCES-MIB::hrSWRunStatus.2532 = INTEGER: running(1)
HOST-RESOURCES-MIB::hrSWRunStatus.2600 = INTEGER: running(1)
HOST-RESOURCES-MIB::hrSWRunStatus.2740 = INTEGER: running(1)
HOST-RESOURCES-MIB::hrSWRunStatus.2760 = INTEGER: running(1)
HOST-RESOURCES-MIB::hrSWRunStatus.2784 = INTEGER: running(1)
HOST-RESOURCES-MIB::hrSWRunStatus.2984 = INTEGER: running(1)
HOST-RESOURCES-MIB::hrSWRunStatus.3084 = INTEGER: running(1)
HOST-RESOURCES-MIB::hrSWRunStatus.3184 = INTEGER: running(1)
HOST-RESOURCES-MIB::hrSWRunStatus.3224 = INTEGER: running(1)
HOST-RESOURCES-MIB::hrSWRunStatus.3324 = INTEGER: running(1)
HOST-RESOURCES-MIB::hrSWRunStatus.3476 = INTEGER: running(1)
HOST-RESOURCES-MIB::hrSWRunStatus.3528 = INTEGER: running(1)
HOST-RESOURCES-MIB::hrSWRunStatus.3536 = INTEGER: running(1)
HOST-RESOURCES-MIB::hrSWRunStatus.3640 = INTEGER: running(1)
HOST-RESOURCES-MIB::hrSWRunStatus.3644 = INTEGER: running(1)
HOST-RESOURCES-MIB::hrSWRunStatus.3816 = INTEGER: running(1)
HOST-RESOURCES-MIB::hrSWRunStatus.3840 = INTEGER: running(1)
HOST-RESOURCES-MIB::hrSWRunStatus.4284 = INTEGER: running(1)
HOST-RESOURCES-MIB::hrSWRunStatus.4820 = INTEGER: running(1)
HOST-RESOURCES-MIB::hrSWRunStatus.5248 = INTEGER: running(1)
HOST-RESOURCES-MIB::hrSWRunStatus.5256 = INTEGER: running(1)
HOST-RESOURCES-MIB::hrSWRunStatus.5392 = INTEGER: running(1)
HOST-RESOURCES-MIB::hrSWRunStatus.5508 = INTEGER: running(1)
HOST-RESOURCES-MIB::hrSWRunStatus.5528 = INTEGER: running(1)
HOST-RESOURCES-MIB::hrSWRunStatus.5536 = INTEGER: running(1)
-
seaward1983
- Posts: 69
- Joined: Wed Jul 17, 2019 2:09 pm
Re: server does not have snmpwalk permission on the target h
This thread can be closed.
Re: server does not have snmpwalk permission on the target h
Excellent! Glad you were able to get it resolved. Also thank you for posting the result back here. I'll go ahead and close this.
As of May 25th, 2018, all communications with Nagios Enterprises and its employees are covered under our new Privacy Policy.
Be sure to check out our Knowledgebase for helpful articles and solutions!
Be sure to check out our Knowledgebase for helpful articles and solutions!