topic More MIB/OID related really... and aimed at HP programmers in Server Management - Systems Insight Manager

More MIB/OID related really... and aimed at HP programmers

samuel_34 — Fri, 24 Aug 2007 07:43:35 GMT

I use MRTG to monitor and graph server CPU and ambient temperatures as we have a history of various heat related issues at one of our sites.

Until recently I've used the OID .1.3.6.1.4.1.232.6.2.6.8.1.3.0.2 to query the ambient temperature, however we recently bought a DL320 G5 running Support Pack 7.80A, and this apparently uses the OID .1.3.6.1.4.1.232.6.2.6.8.1.3.0.4 for ambient temperature... A recently purchased DL380 G5 also running Support Pack 7.80A uses the original OID, so the change seems only to be applicable to the DL320.

Is this change a blip/mistake ? It'd be REALLY helpful if HP could stick to consistent OIDs ;)

Thanks in advance,
Sam

Re: More MIB/OID related really... and aimed at HP programmers

David Claypool — Fri, 24 Aug 2007 09:29:05 GMT

Actually, prior to the G5 (not including the 320) series and the c-Class, there is NOT an ambient temperature sensor on ProLiant servers.

Re: More MIB/OID related really... and aimed at HP programmers

samuel_34 — Fri, 24 Aug 2007 10:21:53 GMT

Hi David,

Yes, I know, and its inclusion is very useful - a big thanks for that :)

The comment is about consistency really.

When coding MRTG I cut and paste sections into the config file, however I'm now having to check that the OID I'm used to does actually refer to the same attribute. Its a minor point, but a pain in the butt all the same.

Thanks for getting back to me btw - appreciated .

All the best,
Sam