Host template for Compaq (HP) Insight Manager.

[jnojr]

Actually, removing the leading 0's doesn't quite do the trick. That last leading zero refers to the 'chassis' we are dealing with. 0 is invalid, but we do need some value there. I'm not sure which scenario would exist where you'd have multiple chassis, but setting this to 1 chooses the "first one" (only one?).

Seems to make the temp graphs work for me.

Changing them all to .1 did not work.

After getting the MIB installed, I can see what these OIDs are for:

CPQHLTH-MIB::cpqHeTemperatureChassis.1.1 = INTEGER: 1
CPQHLTH-MIB::cpqHeTemperatureChassis.1.2 = INTEGER: 1
CPQHLTH-MIB::cpqHeTemperatureChassis.1.3 = INTEGER: 1
CPQHLTH-MIB::cpqHeTemperatureChassis.1.4 = INTEGER: 1
CPQHLTH-MIB::cpqHeTemperatureChassis.1.5 = INTEGER: 1
CPQHLTH-MIB::cpqHeTemperatureIndex.1.1 = INTEGER: 1
CPQHLTH-MIB::cpqHeTemperatureIndex.1.2 = INTEGER: 2
CPQHLTH-MIB::cpqHeTemperatureIndex.1.3 = INTEGER: 3
CPQHLTH-MIB::cpqHeTemperatureIndex.1.4 = INTEGER: 4
CPQHLTH-MIB::cpqHeTemperatureIndex.1.5 = INTEGER: 5
CPQHLTH-MIB::cpqHeTemperatureLocale.1.1 = INTEGER: cpu(6)
CPQHLTH-MIB::cpqHeTemperatureLocale.1.2 = INTEGER: cpu(6)
CPQHLTH-MIB::cpqHeTemperatureLocale.1.3 = INTEGER: ioBoard(5)
CPQHLTH-MIB::cpqHeTemperatureLocale.1.4 = INTEGER: cpu(6)
CPQHLTH-MIB::cpqHeTemperatureLocale.1.5 = INTEGER: powerSupply(10)
CPQHLTH-MIB::cpqHeTemperatureCelsius.1.1 = INTEGER: 43
CPQHLTH-MIB::cpqHeTemperatureCelsius.1.2 = INTEGER: 47
CPQHLTH-MIB::cpqHeTemperatureCelsius.1.3 = INTEGER: 52
CPQHLTH-MIB::cpqHeTemperatureCelsius.1.4 = INTEGER: 43
CPQHLTH-MIB::cpqHeTemperatureCelsius.1.5 = INTEGER: 34
CPQHLTH-MIB::cpqHeTemperatureThreshold.1.1 = INTEGER: 62
CPQHLTH-MIB::cpqHeTemperatureThreshold.1.2 = INTEGER: 73
CPQHLTH-MIB::cpqHeTemperatureThreshold.1.3 = INTEGER: 68
CPQHLTH-MIB::cpqHeTemperatureThreshold.1.4 = INTEGER: 73
CPQHLTH-MIB::cpqHeTemperatureThreshold.1.5 = INTEGER: 55
CPQHLTH-MIB::cpqHeTemperatureCondition.1.1 = INTEGER: ok(2)
CPQHLTH-MIB::cpqHeTemperatureCondition.1.2 = INTEGER: ok(2)
CPQHLTH-MIB::cpqHeTemperatureCondition.1.3 = INTEGER: ok(2)
CPQHLTH-MIB::cpqHeTemperatureCondition.1.4 = INTEGER: ok(2)
CPQHLTH-MIB::cpqHeTemperatureCondition.1.5 = INTEGER: ok(2)
CPQHLTH-MIB::cpqHeTemperatureThresholdType.1.1 = INTEGER: caution(9)
CPQHLTH-MIB::cpqHeTemperatureThresholdType.1.2 = INTEGER: caution(9)
CPQHLTH-MIB::cpqHeTemperatureThresholdType.1.3 = INTEGER: caution(9)
CPQHLTH-MIB::cpqHeTemperatureThresholdType.1.4 = INTEGER: caution(9)
CPQHLTH-MIB::cpqHeTemperatureThresholdType.1.5 = INTEGER: caution(9)

So, .1, .2, and .4 are for CPUs (stringe, system has two CPUS...), .3 is IO Board, and .5 is Power Supply.

Can anyone use that info to fix that XML file?

[jnojr]

Any more insight into how to make this work?

[fogster]

I'm feeling kind of foolish for not being able to make this work. I don't understand what the XML file is doing so I haven't had any luck changing it.

.1.3.6.1.4.1.232.6.2.6.8.1.4.1 is the OID you want for temperatures, at least on my DL380 G3.

It maps up nicely:

SNMPv2-SMI::enterprises.232.6.2.6.8.1.4.1.1 = INTEGER: 35
SNMPv2-SMI::enterprises.232.6.2.6.8.1.4.1.2 = INTEGER: 34
SNMPv2-SMI::enterprises.232.6.2.6.8.1.4.1.3 = INTEGER: 47
SNMPv2-SMI::enterprises.232.6.2.6.8.1.4.1.4 = INTEGER: 35
SNMPv2-SMI::enterprises.232.6.2.6.8.1.4.1.5 = INTEGER: 28

With:

hpasmcli> show temp
Sensor Location Temp Threshold
------ -------- ---- ---------
#1 PROCESSOR_ZONE 35C/95F 62C/143F
#2 CPU#1 34C/93F 73C/163F
#3 I/O_ZONE 47C/116F 68C/154F
#4 CPU#2 36C/96F 73C/163F
#5 POWER_SUPPLY_BAY 28C/82F 53C/127F

(CPU #2 has apparently gone up a degree in hpasm from when I ran the SNMP query.)

.1.3.6.1.4.1.232.6.2.6.8.1.5.1 has the "threshold" values if someone feels they're necessary:

SNMPv2-SMI::enterprises.232.6.2.6.8.1.5.1.1 = INTEGER: 62
SNMPv2-SMI::enterprises.232.6.2.6.8.1.5.1.2 = INTEGER: 73
SNMPv2-SMI::enterprises.232.6.2.6.8.1.5.1.3 = INTEGER: 68
SNMPv2-SMI::enterprises.232.6.2.6.8.1.5.1.4 = INTEGER: 73
SNMPv2-SMI::enterprises.232.6.2.6.8.1.5.1.5 = INTEGER: 53

The data is in Celsius. I'm not sure SNMP exports the data in Fahrenheit, but it's easy enough to change, if only I could get the query to work.

[eschoeller]

This may be hardware specific, but to summarize, the changes I made to get my DL320s working ...

Code: Select all

<oid_index>.1.3.6.1.4.1.232.6.2.6.8.1.2</oid_index>
....
<cpqHeTemperatureIndex>
    <name>Index</name>
    <method>walk</method>
    <source>value</source>
    <direction>input</direction>
    <oid>.1.3.6.1.4.1.232.6.2.6.8.1.2</oid>
</cpqHeTemperatureIndex>
...
<cpqHeTemperatureCelsius>
    <name>Temperature</name>
    <method>walk</method>
    <source>value</source>
    <direction>output</direction>
    <oid>.1.3.6.1.4.1.232.6.2.6.8.1.4.1</oid>
</cpqHeTemperatureCelsius>

I am also trying to figure out if I can use a VALUE/REGEX to change the TemperatureLocale type from an integer to an actual value (ie. 6 = CPU) but it's a bit over my head.

I've made a lot of other minor changes to this template and I'll post the whole set when I'm done.

[mgb]

Glad that someone improves on my template. I don't have use for it anymore but it's nice to see it evolving so it might span the future.

Michael

[9Nails]

This may be hardware specific, but to summarize, the changes I made to get my DL320s working ...

I am also trying to figure out if I can use a VALUE/REGEX to change the TemperatureLocale type from an integer to an actual value (ie. 6 = CPU) but it's a bit over my head.

I've made a lot of other minor changes to this template and I'll post the whole set when I'm done.

Have you had any time to get the sensor locations to use a real name instead of the number?