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

HP Proliant System Health stuck in Degraded (Warning)

Votes:

0

Environment details: HP DL380g9 OS: not installed yet, but will be Win wK8R2 1CPU 4 physical drives, not configured for an array yet monitoring through iLO4 interface

We have setup a Proliant System health sensor and it is reporting a system state of degraded (warning). The CPU fan channel is "other" since this server does not have a dedicated CPU fan (only 4 chassis fans). the IML has a single error, caused by the RAID array not being configured yet, but the overall status in iLO is OK. All other channels are in the green.

We ran the SNMP tool for 1.3.6.1.4.1.232.6.2.11.2.0 and got 4. We ran it for 1.3.6.1.4.1.232.6.2.7.1.0, but it does not exist.

Any thoughts on what is causing the perpetual degraded state? Also an thoughts on how we can use PRTG to monitor the IML for errors? We want to receive some kind of notification when a new error shows up in the log.

Thanks

hp-proliant-health iml integrated-management-log snmp warning

Created on Jan 5, 2015 8:49:04 PM



Best Answer

Accepted Answer

Votes:

0

Hi, This OID scans the HP Overall Status and the value "3" is defined as degraded. Please do have a look here. If cleaning your IML logs does not help, please consider to get in contact with HP why the server reports the status as degraded via SNMP.

Best regards

Created on Jan 8, 2015 8:35:22 AM by Felix Saure [Paessler Support]

Last change on Jun 20, 2016 7:24:12 AM by Luciano Lingnau [Paessler]



5 Replies

Votes:

0

Hi,

Please scan the OID 1.3.6.1.4.1.232.6.1.3.0 on your HP Server. Which value do you receive?

Best regards

Created on Jan 6, 2015 12:09:15 PM by Felix Saure [Paessler Support]



Votes:

0

1/6/2015 8:56:29 AM (13 ms) : SNMP V2c
1/6/2015 8:56:29 AM (17 ms) : Custom OID 1.3.6.1.4.1.232.6.1.3.0 
1/6/2015 8:56:29 AM (44 ms) : -------
1/6/2015 8:56:29 AM (48 ms) : Value: Error converting OID (SNMP error # -2007)
1/6/2015 8:56:29 AM (52 ms) : Done

Created on Jan 6, 2015 1:57:11 PM

Last change on Jan 7, 2015 1:09:37 PM by Felix Saure [Paessler Support]



Votes:

0

It looks like there is a space before / after the OID which causes this error. Please run the test again and check for blanks.

Best regards

Created on Jan 7, 2015 1:12:15 PM by Felix Saure [Paessler Support]



Votes:

0

I ran it again and removed the trailing space. The OID returned 3.

Created on Jan 7, 2015 1:39:07 PM

Last change on Jan 8, 2015 2:31:22 PM by Torsten Lindner [Paessler Support]



Accepted Answer

Votes:

0

Hi, This OID scans the HP Overall Status and the value "3" is defined as degraded. Please do have a look here. If cleaning your IML logs does not help, please consider to get in contact with HP why the server reports the status as degraded via SNMP.

Best regards

Created on Jan 8, 2015 8:35:22 AM by Felix Saure [Paessler Support]

Last change on Jun 20, 2016 7:24:12 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.