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


HP Health monitoring after 14.4.12.3284+

Votes:

0

Your Vote:

Up

Down

After Upgrade, all Windows 2008/Windows 2008 R2 HP Health monitoring went down only with the message "Failed". A local upgrade of HP Service Pack (2014.09) did not resolve the issue. All servers up-to-date in term of Windows Upates. Please advise.

failed health hp

Created on Oct 23, 2014 1:49:49 PM by  Registre STQ (0) 1



Best Answer

Accepted Answer

Votes:

1

Your Vote:

Up

Down

Hi Hermanbrood,

the OID we used in the previous version did not work anymore in our labs after updating to the latest software version from HP. So we worked on the sensor and realized that we actually did not use the proper OID before. Now PRTG displays the same status as the HP software does (at least in the versions that we have in our labs).

The overall status is not something that PRTG is making up, but it is directly read and displayed from the target system.

If you don't like the status as it is you can edit your sensor to ignore the "red" status by changing the channels settings as described below. But we strongly recommend to not do so because you will be ignoring the status information that HP gives you.

To redefine the way the sensor displays the status you can edit the "lookup file" that is used for the respective sensor channel:

  • Go to the \lookups folder in your PRTG program directory and copy the file prtg.standardlookups.hp.status.ovl into the \lookups\custom folder.
  • Open your copy in an editor.
  • In the lookup definition, change state="Error" to state="Warning" and save your settings.
  • This will cause the sensor to show a yellow warning status instead of a red down status.
  • As long as your custom file exists your customizations will be handled preferably by PRTG instead of the original lookup settings.
  • For details, see PRTG Manual: Define Lookups, section "Customizing Lookups".

Hope this helps!

Dirk

Created on Oct 29, 2014 8:58:38 AM by  Dirk Paessler [Founder Paessler AG] (10,859) 3 4

Last change on Oct 29, 2014 10:35:55 AM by  Daniel Zobel [Paessler Support]



10 Replies

Votes:

0

Your Vote:

Up

Down

I have the same issue. Everything else works fine, but "SNMP HP System Health" for three different HP servers is now status "Failed" but it looks like all of the channels are good status (so no reason to show failed)

Created on Oct 23, 2014 2:38:59 PM by  Steven Honeyman (0) 1



Votes:

0

Your Vote:

Up

Down

Same for us, all "SNMP HP Proliant System Health" sensors showing as failed after the update to 14.4.12.3284.

Created on Oct 23, 2014 7:57:45 PM by  jaz (0) 1



Votes:

0

Your Vote:

Up

Down

Same for us as well. Most are working, some don't (even some probes checking 3 server, 2 are working, 1 not). Doesn't seem to be a consistency on the servers affected. Mix of 2003 and 2008. Gen5 through to Gen8.

Created on Oct 23, 2014 8:20:50 PM by  nzsabuga (0)



Votes:

0

Your Vote:

Up

Down

For issues on SNMP HP System Health Sensors after the update to version 14.4.12, please be aware that the sensor checks a different OID as of this version. Please see the details in this KB-Article: Why is my SNMP HP Proliant System Health sensor in error status after updating PRTG?

You can also change the settings for this sensor, see below.

Created on Oct 24, 2014 7:20:15 AM by  Torsten Lindner [Paessler Support]

Last change on Oct 29, 2014 9:00:21 AM by  Dirk Paessler [Founder Paessler AG] (10,859) 3 4



Votes:

0

Your Vote:

Up

Down

After following some the aforementionned advices, I did a SNMP GET on the OID .1.3.6.1.4.1.232.6.2.11.2.0 with a result of "4" which apparently points to the IML logs.

I did clear that log and the HP Health alarm in PRTG also cleared.

Follow-up question:

1. Why this new behavior after release 14.4.12.3284+ since the IML log entries were pre-dating my original PRTG installation (By a couple of years!!!). There was nothing "recent" in that log.

Unless I'm mistaken, these alarms should have shown themselves the very first time I would have polled these devices? No ? Anyhow, all is good now. BTW, there is usually a link to "Cpqimlv.exe" called "HP ProLiant Integrated MAnagement Log Viewer" that gives access to clearing the log without the CLI.

Created on Oct 24, 2014 11:21:37 AM by  Registre STQ (0) 1



Votes:

0

Your Vote:

Up

Down

We implemented this based on the HP recommendation though and we hope that you will understand, that we had to decide it like this.
HP provides several different "state variables" and also one for the "overall state". This overall state shows the "worst" of the other states and does not take into account which one it is. The Overall State would switch to "failed" if for example a fan or power supply failed or a temperature was too high.
You can edit the status in case by changing the respective entry in the lookup file used by the sensor. For detailed information, please have a look at http://www.paessler.com/manuals/prtg/define_lookups.htm

Created on Oct 24, 2014 11:52:38 AM by  Torsten Lindner [Paessler Support]



Votes:

0

Your Vote:

Up

Down

Ok the change in functionality is good, i checked a few of our servers and sure enough there were uncleared events in the IML. After clearning the events from IML the status returned to normal. Perhaps the error message could be updated to be more descriptive. The current message "Error in Overall Status: 'Failed'" has no clues.

Created on Oct 24, 2014 9:38:09 PM by  jaz (0) 1



Votes:

0

Your Vote:

Up

Down

We're sorry but changing the error message is not possible because it is generated by the value lookup system of PRTG.

Created on Oct 27, 2014 11:55:53 AM by  Johannes Herrmann [Paessler Support] (1,320) 2 2

Last change on Oct 27, 2014 4:06:32 PM by  Johannes Herrmann [Paessler Support] (1,320) 2 2



Votes:

0

Your Vote:

Up

Down

The noise this sensor now generates, not based on the current state of the system, but based on OLD information in de Integrated Management Logs made us decide to not monitor the HP ProLiant Health using PRTG any more.

What's next, overall failed status for Windows machines because I did not cleanup the system event logs??

I totally do not understand why Paessler made this move, a sensor based on logs? No!! A sensor needs to be based on live status information of a system. That's exactly why we chose to use PRTG, because of the live info.

This is a bad decision, it's forcing us to use other monitoring software to do the trick PRTG did until now.

Bottom line: If the overall status in HP Integrated Management is ok, then PRTG should be also, and that is currently not the case!

Created on Oct 28, 2014 1:05:02 PM by  hermanbrood (7) 1



Accepted Answer

Votes:

1

Your Vote:

Up

Down

Hi Hermanbrood,

the OID we used in the previous version did not work anymore in our labs after updating to the latest software version from HP. So we worked on the sensor and realized that we actually did not use the proper OID before. Now PRTG displays the same status as the HP software does (at least in the versions that we have in our labs).

The overall status is not something that PRTG is making up, but it is directly read and displayed from the target system.

If you don't like the status as it is you can edit your sensor to ignore the "red" status by changing the channels settings as described below. But we strongly recommend to not do so because you will be ignoring the status information that HP gives you.

To redefine the way the sensor displays the status you can edit the "lookup file" that is used for the respective sensor channel:

  • Go to the \lookups folder in your PRTG program directory and copy the file prtg.standardlookups.hp.status.ovl into the \lookups\custom folder.
  • Open your copy in an editor.
  • In the lookup definition, change state="Error" to state="Warning" and save your settings.
  • This will cause the sensor to show a yellow warning status instead of a red down status.
  • As long as your custom file exists your customizations will be handled preferably by PRTG instead of the original lookup settings.
  • For details, see PRTG Manual: Define Lookups, section "Customizing Lookups".

Hope this helps!

Dirk

Created on Oct 29, 2014 8:58:38 AM by  Dirk Paessler [Founder Paessler AG] (10,859) 3 4

Last change on Oct 29, 2014 10:35:55 AM by  Daniel Zobel [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.