New Question
 
 
PRTG Network Monitor

Intuitive to Use.
Easy to manage.

200.000 administrators have chosen PRTG to monitor their network. Find out how you can reduce cost, increase QoS and ease planning, as well.

Free PRTG
Download >>

 

What is this?

This knowledgebase contains questions and answers about PRTG Network Monitor and network monitoring in general. You are invited to get involved by asking and answering questions!

Learn more

 

Top Tags


View all Tags


Adding HP Proliant disk sensor fails

Votes:

0

Your Vote:

Up

Down

When attempting to add HP Proliant disk sensor it fails. Other sensors on the same device are working fine.

  • It has the latest HP Management Agents and HP Insight Management WBEM Provider installed/enabled as well and SNMP on the target server.
  • Also, the SNMP service has IPs for the PRTG probes added under the Security Tab on the SNMP service under "Accept SNMP packets from these hosts". and is active.
  • The firewall is not turned on. The server is the same ProLiant ML310e Gen8 as the one that has the sensors installed.
  • I tried uninstalling the HP software and reinstalling it.-no luck.
  • I also tried adding the server device as it IP versus it FQDN and adding the disk sethe sensors.--no luck.
  • Also tried moving the target server from one Probe to another within the console --no luck.

When I try to use the SNMP tester tool from the probe that this device is monitored by I get the following results:
..The 1st three tests below were against the three SNMP types from the Probe associated with the problem server to that server.

..The second set were run from a different probe against a server that has the HP Proliant disk sensor's installed. In both cases I still get back a error.

So either the OID I pulled from another question posted on the forums. Or I am missing something. I have spent hours trying to find out what the issue is. I have went through the following troubleshooting steps.

----------------------- New Test -----------------------
Paessler SNMP Tester 5.2.3 Computername: Probe3 Interface: (192.168.225.73)
7/11/2018 2:15:04 PM (1 ms) : Device: 192.168.211.2
7/11/2018 2:15:04 PM (2 ms) : SNMP V3
7/11/2018 2:15:04 PM (3 ms) : Walk 1.3.6.1.4.1.232.3.2.5.1
7/11/2018 2:15:08 PM (4026 ms) : Error: -2003

----------------------- New Test -----------------------
Paessler SNMP Tester 5.2.3 Computername: Probe3 Interface: (192.168.225.73)
7/11/2018 2:15:14 PM (2 ms) : Device: 192.168.211.2
7/11/2018 2:15:14 PM (4 ms) : SNMP V2c
7/11/2018 2:15:14 PM (5 ms) : Walk 1.3.6.1.4.1.232.3.2.5.1
7/11/2018 2:15:16 PM (2019 ms) : Error: -2003

----------------------- New Test -----------------------
Paessler SNMP Tester 5.2.3 Computername: Probe3 Interface: (192.168.225.73)
7/11/2018 2:15:22 PM (3 ms) : Device: 192.168.211.2
7/11/2018 2:15:22 PM (5 ms) : SNMP V1
7/11/2018 2:15:22 PM (6 ms) : Walk 1.3.6.1.4.1.232.3.2.5.1
7/11/2018 2:15:24 PM (2010 ms) : Error: -2003

----------------------- New Test -----------------------
Paessler SNMP Tester 5.2.3 Computername: Probe4 Interface: (192.168.225.73)
7/11/2018 2:16:24 PM (3 ms) : Device: 192.168.71.2
7/11/2018 2:16:24 PM (5 ms) : SNMP V1
7/11/2018 2:16:24 PM (7 ms) : Walk 1.3.6.1.4.1.232.3.2.5.1
7/11/2018 2:16:26 PM (2014 ms) : Error: -2003

----------------------- New Test -----------------------
Paessler SNMP Tester 5.2.3 Computername: Probe4 Interface: (192.168.225.73)
7/11/2018 2:16:31 PM (4 ms) : Device: 192.168.71.2
7/11/2018 2:16:31 PM (6 ms) : SNMP V2c
7/11/2018 2:16:31 PM (8 ms) : Walk 1.3.6.1.4.1.232.3.2.5.1
7/11/2018 2:16:33 PM (2021 ms) : Error: -2003

----------------------- New Test -----------------------
Paessler SNMP Tester 5.2.3 Computername: Probe4 Interface: (192.168.225.73)
7/11/2018 2:16:36 PM (5 ms) : Device: 192.168.71.2
7/11/2018 2:16:36 PM (7 ms) : SNMP V3
7/11/2018 2:16:36 PM (10 ms) : Walk 1.3.6.1.4.1.232.3.2.5.1
7/11/2018 2:16:40 PM (4032 ms) : Error: -2003

error--2003 prtg sensor smnp

Created on Jul 11, 2018 6:52:49 PM by  acewarner (20) 1

Last change on Jul 16, 2018 6:30:13 AM by  Luciano Lingnau [Paessler Support]



8 Replies

Votes:

0

Your Vote:

Up

Down

Hello,

Does this device have any kind of whitelist that the PRTG server needs to be added to?

The error 2003 means we were not able to connect. Most of the time it's a community string issue or some kind of config on the device to allow the PRTG host to query for SNMP.

Benjamin Day
Paessler Support

Created on Jul 11, 2018 11:34:24 PM by  Benjamin Day [Paessler Support]



Votes:

0

Your Vote:

Up

Down

Hello, Thanks for the quick reply. No it does not have a whitelist or access list. I don't have a community string on the SNMP service on the server. Would adding one help? The other servers that have the same setup and have the HP Physical Disk Sensors don't have one either. Just to clarify I have over 50 HP Ml310e Gen 8 servers and only about 7 won't add these sensors. All of the other sensors work fine. They also are using iLo version 4.0 if that helps.

Created on Jul 12, 2018 12:16:15 PM by  acewarner (20) 1



Votes:

0

Your Vote:

Up

Down

Yes, please add the community string. I don't know how the others are working, but without the matching community string on both sides, this error will come up.

Benjamin Day
Paessler Support

Created on Jul 14, 2018 12:22:02 AM by  Benjamin Day [Paessler Support]



Votes:

0

Your Vote:

Up

Down

Okay so I checked and the default on our PRTG core and the community string is set to the default "public". None of the working SNMP sensors on the servers that have actively working SNMP HP Physical Disk sensors have the "public" setting on the SNMP service on the servers that they monitor. Maybe the public is considered set to public to default on windows servers? I honestly don't know.

Created on Jul 16, 2018 4:02:35 PM by  acewarner (20) 1



Votes:

0

Your Vote:

Up

Down

Hold on, let me clarify something I should have clarified earlier. Are you polling the OS, or iLO?

If iLO, which version of iLO? If Windows, did adding the community string make any impact?

Benjamin Day
Paessler Support

Created on Jul 17, 2018 6:37:47 PM by  Benjamin Day [Paessler Support]



Votes:

0

Your Vote:

Up

Down

Sorry for the late reply. The iLo is version 4. And we are using the OS. I did try the community string and the results were pretty much the same. I am trying to use the SNMP tool to test whether or not SNMP is working or not. I am not too familiar with it but I am running it from the PRTG probe that the problem server resides on. I have reviewed the documentation but am still unsure the correct OID to use for the HP Proliant Physical disk (SNMP) testing. Also I am not sure exactly which test would be best to run in this instance. Any help would be appreciated. Thanks!

Created on Jul 19, 2018 5:05:58 PM by  acewarner (20) 1



Votes:

0

Your Vote:

Up

Down

We have iLo 4.0 but are using OS polling. Adding the community string had no effect. I am trying to use the SNMP testing tool to troubleshoot this. I have reviewed the documentation but I am still unsure if I am using the correct OID for testing the HP Proliant Physical Disk sensor (SNMP) and if I am even using the correct test. I am running the tester from the probe that the problem server is monitored by. Besides checking to ensure the SNMP service is running on the actual server itself is there anything else I can do to troubleshoot this? Any help would be appreciated. Thanks!

Created on Jul 19, 2018 5:10:57 PM by  acewarner (20) 1



Votes:

0

Your Vote:

Up

Down

Take the following text, and save it as a txt file.

-------------------------
HP Proliant Physical Disk
-------------------------
hrSystemUptime
walk=1.3.6.1.2.1.25.1.1
--------
MIB-2 System
walk=1.3.6.1.2.1.1
----------
Status
----------
get=1.3.6.1.4.1.232.3.1.3.0
----------
Controller
----------
walk=1.3.6.1.4.1.232.3.2.2.1
----------
PhDrvData
----------
walk=1.3.6.1.4.1.232.3.2.5.1.1

There is an option in the SNMP Tester to use a script. Select that option, and tell it to run the script you just made. Send me the results.

Benjamin Day
Paessler Support

Created on Jul 20, 2018 1:18:02 AM by  Benjamin Day [Paessler Support]



Please log in or register to enter your reply.


Disclaimer: The information in the Paessler Knowledge Base comes without warranty of any kind. Use at your own risk. Before applying any instructions please exercise proper system administrator housekeeping. You must make sure that a proper backup of all your data is available.