HP Integrity rx2800 HP Insight Management WBEM Provider Events Reference Guide - Page 101
Power on failed due to an SBL Scalable Blade Link mismatch. Probable Cause: Each
View all HP Integrity rx2800 manuals
Add to My Manuals
Save this manual to your list of manuals |
Page 101 highlights
14483 Error 14485 Error 14486 Error 14487 Error 14488 Error 14495 Warning 14512 Error 14516 Error 14517 Warning Power could not turn on because CPUs in the system or SBL Domain are mismatched. Probable Cause: The system/SBL domain has CPUs of different S/SPEC and/or a delta greater than 1 in core stepping. Recommended Action: Determine which CPU part number you want to keep, and remove those that don't match. DF from the CM> menu will display S/SPEC and stepping to help identify mismatch. When the CPUs all match try to power on again. WBEM EventID: 9903. WBEM ProviderName: FPL_IndicationProvider. The installed SBL is incompatible for the enclosure type, or blade bay. Probable Cause: Each SBL2/SBL4 is constructed for the precise width of the enclosure bays. SBL2-7000, SBL2E-7000, and SBL4-7000 are designed for the c7000 enclosure. SBL2-3000, SBL2E-3000, and SBL4-3000 are designed for the c3000 enclosure. The SBL2-7000 and SBL2-3000 must be installed with the monarch blade in bay 1, 3, 5, or 7. The SBL2E-7000 and SBL2E-3000 must be installed with the monarch blade in bay 2, 4, or 6. The SBL4 must be installed with the monarch blade in bay 1 or 5. This event is being generated because the installed SBL does not match the environment. Recommended Action: Change your installation to a supported configuration. WBEM EventID: 9904. WBEM ProviderName: FPL_IndicationProvider. Power on failed due to an SBL (Scalable Blade Link) mismatch. Probable Cause: Each SBL2/SBL4 is constructed for the precise width of the enclosure bays. SBL2-7000, SBL2E-7000, and SBL4-7000 are designed for the c7000 enclosure. SBL2-3000, SBL2E-3000, and SBL4-3000 are designed for the c3000 enclosure. The SBL2-7000 and SBL2-3000 must be installed with the monarch blade in bay 1, 3, 5, or 7. The SBL2E-7000 and SBL2E-3000 must be installed with the monarch blade in bay 2, 4, or 6. The SBL4 must be installed with the monarch blade in bay 1 or 5. This event is being generated because the installed SBL does not match the environment. Recommended Action: Change your installation to a supported configuration. Then attempt power on again. WBEM EventID: 9905. WBEM ProviderName: FPL_IndicationProvider. Firmware on the system is mismatched. Probable Cause: One of the FW types within the system has a mismatch across blades. Recommended Action: Use the SR command from the CM> menu or look in the iLO web GUI to identify the mismatched FW and bring it up to date with the rest of the system. WBEM EventID: 9906. WBEM ProviderName: FPL_IndicationProvider. Power failed to turn on due to mismatched firmware. Probable Cause: The revision of one of the ROMs in the system does not match the revision of its counterparts. One of the FW types within the system has a mismatch. Recommended Action: Use the iLO SR command from the CM> menu or look in the iLO web GUI to identify the mismatched FW and bring it up to date with the rest of the system. WBEM EventID: 9907. WBEM ProviderName: FPL_IndicationProvider. The primary system variables are uninitialized. Probable Cause: The primary system variables are uninitialized. Recommended Action: The system variables must be initialized. Please run SYSSET to initialize them. WBEM EventID: 9898. WBEM ProviderName: FPL_IndicationProvider. The CPU power pod is no longer powering the CPU. Probable Cause: The CPU power pod is no longer providing power to the CPU. It may not be plugged in to the sytem board, or it may have failed. Recommended Action: If not plugged into the system board, plug it in. Check that the connector is not loose. If not then you should replace the FRU. WBEM EventID: 9908. WBEM ProviderName: FPL_IndicationProvider. This blade has failed to show signs of boot. Probable Cause: Something has caused the blade to fail to boot. No BOOT_START event was detected from this blade. Could be the result of a corrupted SFW ROM, a failing processor, or a board failure of the QPI link. Recommended Action: At the next convenient opportunity power cycle the system power to all blades that are configured as part of a system with the failed blade. Look for other errors that may have been logged. Reflash the SFW. WBEM EventID: 9909. WBEM ProviderName: FPL_IndicationProvider. ICH Mezzanine card is missing. Probable Cause: The communications to the ICH MEZZ may have failed. Otherwise the ICH MEZZ is not present. Recommended Action: The system will fail to power on if there is no ICH MEZZ on the monarch blade. Please validate proper loading of the ICH MEZZ card if a pc on fails. WBEM EventID: 9910. WBEM ProviderName: FPL_IndicationProvider. Platform Events 101