HPE GreenLake Administration
- Community Home
- >
- Servers and Operating Systems
- >
- HPE ProLiant
- >
- Server Management - Systems Insight Manager
- >
- Re: More MIB/OID related really... and aimed at HP...
Server Management - Systems Insight Manager
1826062
Members
4167
Online
109690
Solutions
Forums
Categories
Company
Local Language
back
Forums
Discussions
Forums
- Data Protection and Retention
- Entry Storage Systems
- Legacy
- Midrange and Enterprise Storage
- Storage Networking
- HPE Nimble Storage
Discussions
Forums
Discussions
Discussions
Discussions
Forums
Discussions
back
Discussion Boards
Discussion Boards
Discussion Boards
Discussion Boards
- BladeSystem Infrastructure and Application Solutions
- Appliance Servers
- Alpha Servers
- BackOffice Products
- Internet Products
- HPE 9000 and HPE e3000 Servers
- Networking
- Netservers
- Secure OS Software for Linux
- Server Management (Insight Manager 7)
- Windows Server 2003
- Operating System - Tru64 Unix
- ProLiant Deployment and Provisioning
- Linux-Based Community / Regional
- Microsoft System Center Integration
Discussion Boards
Discussion Boards
Discussion Boards
Discussion Boards
Discussion Boards
Discussion Boards
Discussion Boards
Discussion Boards
Discussion Boards
Discussion Boards
Discussion Boards
Discussion Boards
Discussion Boards
Discussion Boards
Discussion Boards
Discussion Boards
Discussion Boards
Discussion Boards
Discussion Boards
Discussion Boards
Blogs
Information
Community
Resources
Community Language
Language
Forums
Blogs
Topic Options
- Subscribe to RSS Feed
- Mark Topic as New
- Mark Topic as Read
- Float this Topic for Current User
- Bookmark
- Subscribe
- Printer Friendly Page
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
08-24-2007 12:43 AM
08-24-2007 12:43 AM
More MIB/OID related really... and aimed at HP programmers
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
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
2 REPLIES 2
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
08-24-2007 02:29 AM
08-24-2007 02:29 AM
Re: More MIB/OID related really... and aimed at HP programmers
Actually, prior to the G5 (not including the 320) series and the c-Class, there is NOT an ambient temperature sensor on ProLiant servers.
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
08-24-2007 03:21 AM
08-24-2007 03:21 AM
Re: More MIB/OID related really... and aimed at HP programmers
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
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
The opinions expressed above are the personal opinions of the authors, not of Hewlett Packard Enterprise. By using this site, you accept the Terms of Use and Rules of Participation.
Company
Support
Events and news
Customer resources
© Copyright 2025 Hewlett Packard Enterprise Development LP