3/30/2024 0 Comments Ilo 2 firmware ipmi bugs![]() Look for, or call HP and ask for, a firmware update and apply that. In our case, HP denied there was a known problem even though both of our chassis exhibited the issue.ĭepending on when this chassis was shipped, you may be in this boat. I will admit we didn't try the downloadable iLO configuration application a couple of these blades run ESX, which makes the tool rather academic anyways. Removing and reseating individual modules didn't work. The only way to get everything talking together again was to power-cycle the whole chassis - shutdown all blades, then pull the power inputs. This was repeatable, and all blade iLOs would go unresponsive within about an hour of each other, 30 to 90 days after being started. With an older firmware, the iLO on the blades would become non-responsive both to the chassis and to the rest of the network (the iLOs were IP-enabled for IP-KVM purposes). One of my customers has a couple of C3000 chassis. ![]() If the OA can't talk to the iLOs on the blades, you have a problem. You should be able to apply iLO configuration values to the iLO via the OA. ![]() The chassis OA has the ability to over-ride existing iLO configurations and talk to the blades no matter what the previous admin did. ![]()
0 Comments
Leave a Reply. |
AuthorWrite something about yourself. No need to be fancy, just an overview. ArchivesCategories |