ILO - Slot 255 is not responsive.

[GaryHe]

Hello

I hope this is not a stupid question since I am new to this formum and ILO in general but I am getting these errors (a lot of them) and it does not give me much informaiton as to what it is or where to look to fix it.    I am hoping the experts here can help me

thanks 

The iLO health monitoring status of the device / adapter located in Slot 255 is not responsive.

Initial Update 12/07/2020 12:35:26 Event Class 0x23 Event Code 0x484

Gary

[Ash_1711]

Hi Gary,

              These alerts are captured from The iLO health monitoring status & are false caution messages.

Solution:

>ILO5 firmware 2.30 fixed the issue.

Advisory: HPE Integrated Lights-Out 5 (iLO 5) - False Caution Message, "The iLO Health Monitoring Status of the Device / Adapter Located In Embedded Is Not Responsive" May Display Constantly In the iLO 5 Event Log
https://internal.support.hpe.com/hpesc/public/docDisplay?docId=emr_na-a00102190en_us\

Regards

HPE

[Anand1202]

I am running iLO5 firmware version 2.55 and 2.60 and also see this event approx. once a day in the iLO Event Log:

"The iLO health monitoring status of the device / adapter located in Slot 255 is not responsive."

[JoseAlves]

I am also with this problem in 3 HPE DL 380 Gen10 with ILO 2.55 and ILO 2.60 ( i i had upgraded from 2.55 to 2.60 to see if this issue goes away but no results). on a server I downgraded from ILO 2.60 to 2.48, and this error occurred once in about 24h... any help?

[bjcabraatz]

This is occuring for use as well. HP GEN 10 DL380. ESXi 6.7

The iLO health monitoring status of the device / adapter located in Slot 255 is not responsive.

Fiber Channel HBA

• Product Name
  ProLiant DL380 Gen10
• System ROM
  U30 v2.54 (09/03/2021)
• System ROM Date
  09/03/2021
• Redundant System ROM
  U30 v2.36 (07/16/2020)

[eYc]

Hello,

I also got this Message "The iLO health monitoring status of the device / adapter ... is not responsive" on an DL380 Gen10 with iLO 2.55, BIOS 2.36, Intelligent Provisioning 3.46 running Red Hat Enterprise Linux 7.9, for four devices, all at once, at the same time & date.

Event Log said at 04/04/22, 10:17:

5037 The iLO health monitoring status of the device / adapter located in Slot 4 is not responsive.
5036 The iLO health monitoring status of the device / adapter located in Embedded Ethernet 05 is not responsive.
5035 The iLO health monitoring status of the device / adapter located in Slot 6 is not responsive.
5034 The iLO health monitoring status of the device / adapter located in Slot 1 is not responsive.

 The server crashed once, five days before these events were logged, and we don't know if it has anything to do with it.

I updated BIOS and Firmware with SPP 2021-10, Intelligent Prov.  3.70, disabled MCTP followed by MCTP-Reset and iLO Reboot (so MCTP was enabled again in iLO-Devices/Discovery), and i hope that solved the issue.

[Lori69]

---

@GaryHe wrote:  Hello

I hope this is not a stupid question since I am new to this formum and ILO in general but I am getting these errors (a lot of them) and it does not give me much informaiton as to what it is or where to look to fix it.    I am hoping the experts here can help me

thanks 

The iLO health monitoring status of the device / adapter located in Slot 255 is not responsive.

Initial Update 12/07/2020 12:35:26 Event Class 0x23 Event Code 0x484

Gary

---

To avoid the false caution messages, update to iLO 5 v2.30. As a workaround, if the system is functioning as expected, ignore the caution messages.

[RLAG-IT]

I have the same problem after updating to ilo 2.55.

Every day at this time, the fans are running with 100% for some seconds.
Customer is not happy about the noise.

Is there any solution now?

[Bob Curnock]

I am seeing this after upgrading to ilo 2.48 firmware - can't upgrade any higher due to the OneView/ilo firmware issue which is not yet fixed

[tunguyenamj]

Same issue with my DL360 gen10 server.

iLO 5 v2.55p23

ROM U32 v2.54

"The iLO health monitoring status of the device / adapter located in Slot 255 is not responsive" happen once every two days at fixed time 7:00 AM