What is this?

This knowledgebase contains questions and answers about PRTG Network Monitor and network monitoring in general.

Learn more

PRTG Network Monitor

Intuitive to Use. Easy to manage.
More than 500,000 users rely on Paessler PRTG every day. Find out how you can reduce cost, increase QoS and ease planning, as well.

Free Download

Top Tags


View all Tags

Can't use SNMP to monitor Dell server

Votes:

0

I can't add the sensor SNMP Dell PowerEdge Physical Disk to monitor the HDDs in the server.

I have configured the SNMP service on the server and enabled SNMP in Dell Server Administrator software. Firewall allows SNMP-traffic...

But when I try to add the sensor, I get SNMP error: -2003. The other SNMP-sensors also give this same error.

Why can't I use SNMP and how to resolve?

prtg-network-monitor prtg13 snmp

Created on Jul 31, 2013 9:49:30 AM

Last change on Dec 11, 2015 6:18:34 AM by  Luciano Lingnau [Paessler]



Best Answer

Accepted Answer

Votes:

1

Hello m_arce, thank you for your write up.

According to the discussion below from Dell's website it is most likely not possible if the host is running ESXi. This is due to the fact that even though an SNMP agent is implemented and active on the ESXi host, it isn't able to provide the SNMP information from the MIB supported by the underlying Proliant server.

Kindly note that nowadays there are a couple of alternatives that we're able to offer to monitor ESXi hosts on Poweredge hardware:

If the server has an iDrac 7 or later, make sure that SNMP is enabled on it, add a new device to PRTG with the IP of the iDRAC interface and try to deploy the SNMP Dell PowerEdge sensors there. You will most likely succeed, if not, please perform the previously suggested tests with the SNMP Tester against the iDrac interface.


It's also possible to monitor the host's hardware status using the sensors which can query the ESXi directly over WBEM or SOAP to retrieve it's hardware's status:

The SOAP variant sensor will display any alerts that are detected by ESXi, it should warn you about any monitored object on the Hardware Status tab of the Hardware Status as reported by the vSphere client.

The WBEM variant will perform a metascan during the sensor's creation, and list the available monitoring objects, it will not only warn you about issues but also display information such as FAN Speeds, Temperatures and etc. Please note that the available information for selection varies according on the installed software and hardware.

Best Regards,

Created on Dec 11, 2015 9:50:39 AM by  Luciano Lingnau [Paessler]

Last change on Dec 11, 2015 9:52:40 AM by  Luciano Lingnau [Paessler]



13 Replies

Votes:

0

Patrick,

Have you tried using the SNMP tester to see if SNMP is enabled? You should be able to read the uptime if SNMP is working. SNMP Tester

Also, once you have confirmed that SNMP is working, you can use the tester to do a walk on the OID 1.3.6.1.4.1.674.10893.1.20.130.4.1.4 to see if it is seeing the status of the disks on the system.

If you are not getting any kind of response from the tester, then you need to look over the config of SNMP for that server.

Created on Jul 31, 2013 2:46:02 PM by  Greg Campion [Paessler Support]

Last change on Dec 11, 2015 6:17:45 AM by  Luciano Lingnau [Paessler]



Votes:

0

Thanks for your reply!

I tried the SNMP Tester and did a walk on the OID and this the response:

----------------------- New Test -----------------------
Paessler SNMP Tester 5.1
27-8-2013 10:54:50 (1 ms) : Device: ***.***.***.***
27-8-2013 10:54:50 (1 ms) : SNMP V1
27-8-2013 10:54:50 (2 ms) : Walk 1.3.6.1.4.1.674.10893.1.20.130.4.1.4
27-8-2013 10:54:52 (2005 ms) : Error: -2003

Created on Aug 27, 2013 9:03:06 AM

Last change on Dec 11, 2015 6:17:35 AM by  Luciano Lingnau [Paessler]



Votes:

0

This error means that the SNMP tester got no response from the device which could be caused by something conflicting with port 161 on the device or the server or could be that SNMP isn't set up correctly.

Setup for OMSA

Created on Aug 27, 2013 9:25:12 AM by  Greg Campion [Paessler Support]



Votes:

0

Now I'm getting this error when I run the SNMP Tester:

Paessler SNMP Tester 5.1
4-9-2013 9:55:59 (7 ms) : Device: *.*.*.*
4-9-2013 9:55:59 (10 ms) : SNMP V1
4-9-2013 9:55:59 (15 ms) : Custom OID 1.3.6.1.4.1.674.10893.1.20.130.4.1.4
4-9-2013 9:55:59 (100 ms) : -------
4-9-2013 9:55:59 (102 ms) : Value: No Such Name (SNMP error # 2)
4-9-2013 9:55:59 (108 ms) : Done

and Walk gives me this:

----------------------- New Test -----------------------
Paessler SNMP Tester 5.1
4-9-2013 9:57:53 (3 ms) : Device: *.*.*.*
4-9-2013 9:57:53 (4 ms) : SNMP V1
4-9-2013 9:57:53 (5 ms) : Walk 1.3.6.1.4.1.674.10893.1.20.130.4.1.4

Created on Sep 4, 2013 7:58:27 AM

Last change on Dec 11, 2015 6:17:25 AM by  Luciano Lingnau [Paessler]



Votes:

0

When I walk that OID now, I get this message:

----------------------- New Test -----------------------
Paessler SNMP Tester 5.1
5-9-2013 9:26:24 (24 ms) : Device: *.*.*.*
5-9-2013 9:26:24 (40 ms) : SNMP V1
5-9-2013 9:26:25 (46 ms) : Walk 1.3.6.1.4.1.674.10893.1.20.130.4.1.4

But I still can't add the sensor SNMP Dell PowerEdge Physical Disk.

Created on Sep 5, 2013 7:27:51 AM

Last change on Dec 11, 2015 9:12:51 AM by  Luciano Lingnau [Paessler]



Votes:

0

When you have SNMP enabled and configured properly it should show a message like this:

----------------------- New Test -----------------------
Paessler SNMP Tester 5.0 (Beta11)
05-Sep-13 15:05:42 (2 ms) : Device: devicename
05-Sep-13 15:05:42 (3 ms) : SNMP V2c
05-Sep-13 15:05:42 (4 ms) : Walk 1.3.6.1.4.1.674.10893.1.20.130.4.1.4
05-Sep-13 15:05:42 (10 ms) : 1.3.6.1.4.1.674.10893.1.20.130.4.1.4.1 = "3"
05-Sep-13 15:05:42 (15 ms) : 1.3.6.1.4.1.674.10893.1.20.130.4.1.4.2 = "3"
05-Sep-13 15:05:42 (19 ms) : 1.3.6.1.4.1.674.10893.1.20.130.4.1.4.3 = "3"
05-Sep-13 15:05:42 (23 ms) : 1.3.6.1.4.1.674.10893.1.20.130.4.1.4.4 = "3"
05-Sep-13 15:05:42 (27 ms) : 1.3.6.1.4.1.674.10893.1.20.130.4.1.4.5 = "3"
05-Sep-13 15:05:42 (32 ms) : 1.3.6.1.4.1.674.10893.1.20.130.4.1.4.6 = "3"
05-Sep-13 15:05:42 (36 ms) : 1.3.6.1.4.1.674.10893.1.20.130.4.1.4.7 = "3"
05-Sep-13 15:05:42 (41 ms) : 1.3.6.1.4.1.674.10893.1.20.130.4.1.4.8 = "3"

The numbers there correspond to these values: ready ( 1 ) , failed ( 2 ) , online ( 3 ) , offline ( 4 ) , degraded ( 6 ) , recovering ( 7 ) , removed ( 11 ) , resynching ( 15 ) , rebuild ( 24 ) , noMedia ( 25 ) , formatting ( 26 ) , diagnostics ( 28 ) , predictiveFailure ( 34 ) , initializing ( 35 ) , foreign ( 39 ) , clear ( 40 ) , unsupported ( 41 ) , incompatible ( 53 ) .

Created on Sep 5, 2013 1:18:01 PM by  Greg Campion [Paessler Support]

Last change on Dec 11, 2015 9:13:26 AM by  Luciano Lingnau [Paessler]



Votes:

0

What does it mean if I am not getting any response from the walk? I am not getting of the previous errors, so I believe that means the SNMP is enabled...

Created on Sep 10, 2013 8:06:55 AM



Votes:

0

If this is not giving you an error and there are drives attached but not reporting on the OID's this is something that you would need to contact dell about since it would seem their software is not working as it should. You can also try walking the OID 1.3.6.1.4.1.674.10893.1.20.130.4.1 since this tree is where most of the information for the sensor comes from.

1.3.6.1.4.1.674.10893.1.20.130.4.1.4.index DiskState 
1.3.6.1.4.1.674.10893.1.20.130.4.1.23.index DiskRollUpStatus
1.3.6.1.4.1.674.10893.1.20.130.4.1.24.index DiskComponentStatus DellStatus
1.3.6.1.4.1.674.10893.1.20.130.4.1.31.index DiskSMARTWarning

Created on Sep 10, 2013 8:27:21 AM by  Greg Campion [Paessler Support]

Last change on Dec 11, 2015 9:14:40 AM by  Luciano Lingnau [Paessler]



Votes:

0

As soon as I am adding the sensor type SNMP Dell PowerEdge Physical Disk, I am getting this error:

No response (check: firewalls, routing, snmp settings of device, IPs, SNMP version, community, passwords etc) (SNMP error # -2003)

But in the SNMP Tester I don't get any errors, so I'm confused!

Created on Sep 10, 2013 8:56:53 AM

Last change on Dec 11, 2015 9:14:53 AM by  Luciano Lingnau [Paessler]



Votes:

0

Sometimes the SNMP tester will not throw an error if it hangs or times out for other reasons but if walking that OID does not work with it, then it has to be something with the server not allowing the connection over port 161 for SNMP or with the configuration of the software or the possibility of the server software not working correctly. I would recommend asking Dell with assistance on the issue if you cannot get those OID's to work.

You may also want to start troubleshooting with trying to read the uptime of the server via SNMP to see if you have configured the SNMP service properly as shown in the guide that I linked above.

Created on Sep 11, 2013 11:40:42 AM by  Greg Campion [Paessler Support]



Votes:

0

When trying to read the uptime, I get this (seems to work):

----------------------- New Test -----------------------
Paessler SNMP Tester 5.1
17-9-2013 10:54:54 (11 ms) : Device: *.*.*.*
17-9-2013 10:54:54 (12 ms) : SNMP V2c
17-9-2013 10:54:54 (13 ms) : Uptime
17-9-2013 10:54:54 (107 ms) : -------
17-9-2013 10:54:54 (108 ms) : Value: 120330850
17-9-2013 10:54:54 (109 ms) : Done

I will contact Dell with this issue and I hope they can solve this problem...

Created on Sep 17, 2013 8:59:31 AM

Last change on Dec 11, 2015 6:16:55 AM by  Luciano Lingnau [Paessler]



Votes:

0

Hello, I know this thread is 2years "cold". Has anyone made any progress on this?

I have several Windows Dell PE servers and can monitor with Dell PowerEdge System Health and Dell PowerEdge Physical Disk sensors (natively). No issues there. But, when I try to monitor VMware ESXi 5.5 server with OM installed (Dell Open Manage VIB) I don't get to connect the sensor. It complains about OM missing.

Now, I have attempted the above recommendations with the SNMP Tester. When I do a walk on 1.3.6.1.4.1.674.10893.1.20.130.4.1 I don't get the drive iterations response with integer codes (no errors) after the first walk response. (See below)

I tried disabling the snmp service through the ESXi console and confirmed it stopped working (Error: -2003) and then re-enabling with the same result. When testing the walk on a Windows server I get the full response with drive states as per the support samples. (See below)

When changing SNMP versions (V1 and V2C) no change is perceived.

Also, I found other threads referring to Dell stating that an SNMP WALK was not possible due to an ESXi limitation. Is this correct? Has anyone been able to figure out a work around? I need hardware specific monitoring.

Thanks!

Mario

Dell PE ESXi 5.5

----------------------- New Test -----------------------
Paessler SNMP Tester 5.0 (Beta11)
12/10/2015 3:32:20 PM (11 ms) : Device: 10.10.17.24
12/10/2015 3:32:20 PM (17 ms) : SNMP V2c
12/10/2015 3:32:20 PM (22 ms) : Walk 1.3.6.1.4.1.674.10893.1.20.130.4.1.4

Dell PE Windows

----------------------- New Test -----------------------
Paessler SNMP Tester 5.0 (Beta11)
12/10/2015 3:12:52 PM (15 ms) : Device: 10.10.17.21
12/10/2015 3:12:52 PM (22 ms) : SNMP V2c
12/10/2015 3:12:52 PM (29 ms) : Walk 1.3.6.1.4.1.674.10893.1.20.130.4.1.4
12/10/2015 3:12:52 PM (42 ms) : 1.3.6.1.4.1.674.10893.1.20.130.4.1.4.1 = "3"
12/10/2015 3:12:52 PM (53 ms) : 1.3.6.1.4.1.674.10893.1.20.130.4.1.4.2 = "3"

Created on Dec 10, 2015 8:44:07 PM

Last change on Dec 11, 2015 9:16:50 AM by  Luciano Lingnau [Paessler]



Accepted Answer

Votes:

1

Hello m_arce, thank you for your write up.

According to the discussion below from Dell's website it is most likely not possible if the host is running ESXi. This is due to the fact that even though an SNMP agent is implemented and active on the ESXi host, it isn't able to provide the SNMP information from the MIB supported by the underlying Proliant server.

Kindly note that nowadays there are a couple of alternatives that we're able to offer to monitor ESXi hosts on Poweredge hardware:

If the server has an iDrac 7 or later, make sure that SNMP is enabled on it, add a new device to PRTG with the IP of the iDRAC interface and try to deploy the SNMP Dell PowerEdge sensors there. You will most likely succeed, if not, please perform the previously suggested tests with the SNMP Tester against the iDrac interface.


It's also possible to monitor the host's hardware status using the sensors which can query the ESXi directly over WBEM or SOAP to retrieve it's hardware's status:

The SOAP variant sensor will display any alerts that are detected by ESXi, it should warn you about any monitored object on the Hardware Status tab of the Hardware Status as reported by the vSphere client.

The WBEM variant will perform a metascan during the sensor's creation, and list the available monitoring objects, it will not only warn you about issues but also display information such as FAN Speeds, Temperatures and etc. Please note that the available information for selection varies according on the installed software and hardware.

Best Regards,

Created on Dec 11, 2015 9:50:39 AM by  Luciano Lingnau [Paessler]

Last change on Dec 11, 2015 9:52:40 AM by  Luciano Lingnau [Paessler]




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.