- Community Home
- >
- Servers and Operating Systems
- >
- HPE ProLiant
- >
- ProLiant Servers (ML,DL,SL)
- >
- ILO2 Failed to get sensor reading
Categories
Company
Local Language
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
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
Community
Resources
Forums
Blogs
- 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
09-02-2008 06:24 AM
09-02-2008 06:24 AM
ILO2 Failed to get sensor reading
the following HardwareFailure events generated: hwStringMatch - hpasmxld: Failed GET SENSOR READING, sensor 9 hwStringMatch - hpasmxld: iLO 2 Communications Error - Attempting synchronization!
- Tags:
- iLO
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
05-02-2012 05:01 PM
05-02-2012 05:01 PM
Re: ILO2 Failed to get sensor reading
Hi,
I've received the same error and upgraded the firmware to the latest (old iLO2 fw - 1.80; New iLO2FW - 2.05) based on the below reference.
Just upgraded and not sure whether this resolves the problem.
But, my customer is having different DL380G5 servers with same 1.80 fw, but those are working fine.
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
05-03-2012 06:36 AM
05-03-2012 06:36 AM
Re: ILO2 Failed to get sensor reading
Any time iLO2 goes unresponsive you are going to get Event IDs 1111 and sensor reading errors logged by hpqilo2.sys driver.
We have fixed several iLO2 not responding issues in the last couple of years, including the one mentioned in the support document in your link.
Besides upgrading iLO2 to the latest version 2.09 (see link below) I would also recommend to upgrade the hpqilo2.sys driver to version 1.14 and the iLO CHIF driver to version 1.15
iLO2 v2.09
iLO2 CHIF driver 1.15 Windows Server 2003/2008 32-bit
http://h20000.www2.hp.com/bizsupport/TechSupport/SoftwareDescription.jsp?swItem=MTX-3673c656eb7b47888630e39ec3
iLO2 CHIF driver 1.15 Windows Server 2003/2008 64-bit
http://h20000.www2.hp.com/bizsupport/TechSupport/SoftwareDescription.jsp?swItem=MTX-12afece9bb00404792308ee0dc
HP ProLiant iLO 2 Management Controller Driver for Windows Server 2003 32-bit
http://h20000.www2.hp.com/bizsupport/TechSupport/SoftwareDescription.jsp?swItem=MTX-d46add34974045688a70e37632
HP ProLiant iLO 2 Management Controller Driver for Windows Server 2003 x64 Editions
http://h20000.www2.hp.com/bizsupport/TechSupport/SoftwareDescription.jsp?swItem=MTX-9b3a25081dee4269a2a57b0bbe
HP ProLiant iLO 2 Management Controller Driver for Windows Server 2008 32-bit
http://bizsupport1.austin.hp.com/bizsupport/TechSupport/SoftwareDescription.jsp?swItem=MTX-70e7929717c84025bdb31745a9
HP ProLiant iLO 2 Management Controller Driver for Windows Server 2008 x64 Editions (including R2)
http://h20000.www2.hp.com/bizsupport/TechSupport/SoftwareDescription.jsp?swItem=MTX-81d3c928edde4fedaec2dd12ba
__________________________________________________
If you feel this was helpful please click the KUDOS! thumb below!