Remote Insight/ Integrated LightsOut Self Test Error (9005)

[Rune Darrud]

Hello,

I'm running several ESXi 4.1 and ESXi 4.1 U1 servers. I've recently done some maintenance, upgrading the ESXi servers with more ram, going through all settings etc, including making SNMP enabled with roco etc...

In HP-SIM, it has just recently begun to appear messages of this type on all the servers I've "properly" enabled SNMP on, it didnt appear prior to the reinstall:
Remote Insight/ Integrated LightsOut Self Test Error (9005)

It's an annoying error, what I've found on the net is refering to ESX 4.0 and ESX 4.0 U1 and an old HP agent, where'as I am now running "the latest and greatest" ;-)

Any ideas?


Kind Regards,
Rune "TheFlyingCorpse" Darrud

[Rune Darrud]

Bump

[TomSmithCCC]

Hi Rune,
We are seeing the same problem since we upgraded to ESX 4.1 on one of our servers. (Proliant DL380 G5 running ESX 4.1 and PSP 8.6) Were you ever able to find a solution?

Thanks,
-Tom

[sharpdb]

Same error for me at DL 360 G7 with latest iLO, latest HP agents and latest ESXi 4.1 (Update 1, Patch 2). does anyone have a solution?

[Doug Baer]

Same error here ... bl460c G7 blades.  Anyone have a fix?

For what it's worth, I decoded the error code I'm getting (1030057313 dec) = (111101011001010110110101100001 bin)

So, I'm tripping bits
1, 6, 7, 9 11 12 14 15 17 19 22 23 25 27 28 29 30

Based on the handy decoder in the error message:

Each bit has the following meaning when it is on (1):

Bit 17-31: RESERVED: Always 0.
Bit 16: I2C error.
Bit 15: EEPROM error.
Bit 14: SRAM error.
Bit 13: CPLD error.
Bit 12: Mouse interface error.
Bit 11: NIC Error
Bit 10: PCMCIA Error
Bit 9: Video Error
Bit 8: NVRAM write / read / verify error.
Bit 7: NVRAM interface error.
Bit 6: Battery interface error.
Bit 5: Keyboard interface error.
Bit 4: Serial port UART error.
Bit 3: Modem UART error.
Bit 2: Modem firmware error.
Bit 1: Memory test error.
Bit 0: Busmaster I/O read error.
NOTE: bit 31 is the most significant bit, bit 0 is the least significant.

I've either got MAJOR issues, or this is a bogus error. I'm opting for the latter since the thing works fine and there are NO ERRORS logged in the iLO device's internal log.