Loading...
Loading...
Some HPE ProLiant m750 server blades may be in a Critical (Red) health status instead of OK (Green) status after a Moonshot Chassis Manager 2.0 (CM2) reset or during normal usage.When this occurs, both of the following will also be observed:Unable to access the iLO GUI HPE ProLiant m750 server blade, for example when using HPE Integrated Lights-Out (iLO) Integrated Remote Console (IRC).Unable to access the iLO via redfish callsBelow is an example:Corresponding events will be found in the Chassis Manager 2.0 “Health” event log for the blades with a “Critical” status:2023-11-06 08:26:09: #46689 CAUTION: "Redfish communications degraded with blade #2"2023-11-06 08:26:09: #46690 CAUTION: "Redfish communications degraded with blade #4"2023-11-06 08:26:11: #46691 CAUTION: "Redfish communications degraded with blade #27"2023-11-06 08:26:12: #46692 CAUTION: "Redfish communications degraded with blade #37"2023-11-06 08:26:12: #46693 CAUTION: "Redfish communications degraded with blade #36"2023-11-06 08:26:12: #46694 CAUTION: "Redfish communications degraded with blade #38"2023-11-06 08:26:12: #46695 CAUTION: "Redfish communications degraded with blade #39"2023-11-06 08:26:46: #46696 CAUTION: "Redfish communications degraded with blade #20"2023-11-06 08:26:46: #46697 CAUTION: "Redfish communications degraded with blade #22"2023-11-06 08:29:06: #46700 CRITICAL: "Redfish communications lost with blade #2"2023-11-06 08:29:06: #46701 CRITICAL: "Redfish communications lost with blade #4"2023-11-06 08:29:07: #46702 CRITICAL: "Redfish communications lost with blade #27"2023-11-06 08:29:08: #46703 CRITICAL: "Redfish communications lost with blade #36"2023-11-06 08:29:08: #46704 CRITICAL: "Redfish communications lost with blade #37"2023-11-06 08:29:08: #46705 CRITICAL: "Redfish communications lost with blade #38"2023-11-06 08:29:08: #46706 CRITICAL: "Redfish communications lost with blade #39"2023-11-06 08:29:42: #46707 CRITICAL: "Redfish communications lost with blade #20"2023-11-06 08:29:43: #46708 CRITICAL: "Redfish communications lost with blade #22"Once the iLO on the blade is accessible, check the iLO event log on the blade for a “watchdog timeout”
Any Moonshot 2.0 chassis with HPE ProLiant m750 server blades.
Do not replace your HPE Moonshot 1500 Chassis or HPE ProLiant m750 server blades as this is not a hardware issue but a firmware issue.As a workaround, connect to the iLO via ssh and reset the iLO on the HPE ProLiant m750 server blade that displays a red status by performing the following:When the iLO SSH interface is up, connect to the iLO via SSH.Log in to the iLO.Run the command "reset /map1"The iLO will reset and communications will be restored.To reduce the recovery time for iLO to reset and communications being restored, update to HPE Integrated Lights-Out 5 (iLO 5) firmware v3.13.To download iLO 5 v3.13 (or later), perform the following steps:Click the following link:http://www.hpe.com/support/ilo5The page should refresh to display the "DRIVERS AND SOFTWARE" tab and the components that support the selected product. From the "DRIVERS AND SOFTWARE" expandable filter menus on the left side of the page:For further filtering if needed - Select the specific Operating System from the Operating Environment.Locate and select theHPE Integrated Lights-Out 5 v3.13 firmware.Click the Revision History tab to locate the latest version.For more important information, review the Release Notes tab.Click theDownloadbutton.Document VersionRelease DateDetails4June 3, 2025Updated Resolution with iLO 5 firmware v3.13 information.3February 28, 2025Updated Resolution with iLO 5 firmware v3.10 information.2September 16, 2024Updated Resolution with iLO 5 firmware v3.08 information.1July 3, 2024Original Document Release.This advisory will be updated when additional solutions become available.
Operating Systems Affected:Not Applicable
Click on a version to see all relevant bugs
Hewlett Packard Enterprise Integration
Learn more about where this data comes from
Bug Scrub Advisor
Streamline upgrades with automated vendor bug scrubs
BugZero Enterprise
Wish you caught this bug sooner? Get proactive today.