We use this sensor to monitor Proliant ILO status: https://www.paessler.com/manuals/prtg/snmp_hp_proliant_system_health_sensor

We also get the undefined status from the IML channel (like in the picture from the KB-Article). Now there is a server in our network with a log entry. But the channel keeps staying in the undefined state.

Can you give me a hint on how to make the channel work? Thanks in advance!

Article Comments

Hello there,

The OID which was used for this channel got removed in the current version of PRTG since it is already consider by HP in the Overall Status of the sensor, which can be queried via the OID 1.3.6.1.4.1.232.6.1.3.0.

If you use the free SNMP Tester Tool to perform a Scan OID against these OID, which status do you receive?

1.3.6.1.4.1.232.6.1.3.0
1.3.6.1.4.1.232.6.2.11.2.0

Best regards, Felix


Feb, 2018 - Permalink

Hello Felix,

both just return the number '4'.


Feb, 2018 - Permalink

Hi,

Please take a look at the MIB definition for the cpqHeMibCondition value and at this site for the cpqHeEventLogCondition definition. The value 4 represents the status failed. Therefore, the Overall Status channel of the HP System Health Sensor should already show an error.

If you want to explicitly want to monitor the status of the IML, you can create an SNMP Custom Sensor and use the OID 1.3.6.1.4.1.232.6.2.11.2.0. These are the values for the Custom Lookup which you can use: other(1), ok(2), degraded(3), failed(4)

You can also use the existing lookup prtg.standardlookups.hp.condition

Best regards, Felix


Feb, 2018 - Permalink

Hi,
I dont know why I wrote '4'....
It shows '2'! This means it reports 'ok' while having warnings in the IML...

Also tried this: 1.3.6.1.4.1.232.6.2.7.1 Custom OID 1.3.6.1.4.1.232.6.2.7.1

27.02.2018 12:55:37 (340 ms) : SNMP Datatype: SNMP_EXCEPTION_NOSUCHOBJECT

Feb, 2018 - Permalink

IT_wei,

The index is missing in your query, try the OID 1.3.6.1.4.1.232.6.2.7.1.0 This will return the value.

Best regards, Felix


Feb, 2018 - Permalink