HP Integrity Servers with Windows Server 2008 SP2 and Windows Server 2008 R2 SP1 HP Insight Management WBEM Provider Events Reference Guide

Transcription

1 HP Integrity Servers with Windows Server 2008 SP2 and Windows Server 2008 R2 SP1 HP Insight Management WBEM Provider Events Reference Guide HP Part Number: T Published: April 2011

2 Copyright 2011 Hewlett-Packard Development Company, L.P. Legal Notices Confidential computer software. Valid license from HP required for possession, use or copying. Consistent with FAR and , Commercial Computer Software, Computer Software Documentation, and Technical Data for Commercial Items are licensed to the U.S. Government under vendor's standard commercial license. The information contained herein is subject to change without notice. The only warranties for HP products and services are set forth in the express warranty statements accompanying such products and services. Nothing herein should be construed as constituting an additional warranty. HP shall not be liable for technical or editorial errors or omissions contained herein. Microsoft and Windows are U.S. registered trademarks of Microsoft Corporation. Intel and Itanium are trademarks of Intel Corporation in the U.S. and other countries. Java is a US trademark of Sun Microsystems, Inc. UNIX is a registered trademark of The Open Group.

3 Table of Contents About This Document...5 Intended Audience...5 New and Changed Information in This Edition...5 Document Organization...5 Typographic Conventions...5 Related Information...6 Publishing History...6 HP Encourages Your Comments WBEM Provider Event Tables...7 Introduction...7 Platform Events...7 HP Ethernet Events HP Fiber Channel Events HP SAS Events HP SCSI Events HP Smart Array Events Server Provider (SysEvt) Events HP System Management Homepage Events HP Event Sync Events HP BMC IPMI Driver Events PFM Events hpwbemdump Events Table of Contents 3

4 4

5 About This Document This document describes the Windows System Log Event ID number, severity, and description of events generated by the Web-Based Enterprise Management (WBEM) providers on HP Integrity servers running Microsoft Windows Server 2008 with Service Pack 2 (SP2) and Windows Server 2008 R2 with Service Pack 1 (SP1). The document printing date and part number indicate the document s current edition. The printing date changes when a new edition is printed. Minor changes may be made at reprint without changing the printing date. The document part number changes when extensive changes are made. Document updates may be issued between editions to correct errors or document product changes. To ensure that you receive the updated or new editions, you should subscribe to the appropriate product support service. See your HP sales representative for details. For the latest version of this document, see the HP Technical Documentation website: Intended Audience This document is intended for system administrators and HP support personnel responsible for installing, configuring, and managing HP Integrity servers. This document is not a tutorial. New and Changed Information in This Edition This is the fifth release of this document. All event tables have been updated to reflect HP Insight Foundation suite for Integrity with Windows Release 7.1. Document Organization This document is organized as follows: WBEM Provider Event Tables (page 7) Describes the Windows System Log Event ID number, severity, and description of events generated by the Web-Based Enterprise Management (WBEM) providers. Typographic Conventions This document uses the following typographical conventions: WARNING CAUTION IMPORTANT NOTE KeyCap Computer output User input A warning calls attention to important information that if not understood or followed will result in personal injury or nonrecoverable system problems. A caution calls attention to important information that if not understood or followed will result in data loss, data corruption, or damage to hardware or software. This alert provides essential information to explain a concept or to complete a task A note contains additional information to emphasize or supplement important points of the main text. The name of a keyboard key or graphical interface item (such as buttons, tabs, and menu items). Note that Return and Enter both refer to the same key. Text displayed by the computer. Commands and other text that you type. Intended Audience 5

6 Command Ctrl+x A command name or qualified command phrase. A key sequence. A sequence such as Ctrl+x indicates that you must hold down the key labeled Ctrl while you press another key or mouse button. Related Information You can find more information about HP Integrity servers, server management, and software in the following locations: For an overview of Windows on HP Integrity servers: For other documents supporting Windows Server 2008 SP2 and Windows Server 2008 R2 on HP Integrity Servers: to locate documents by operating system: to locate documents by server model number: For technical support resources (drivers, patches, upgrades, migration issues, to sign up for alerts, and so on): Publishing History The publishing history below identifies the edition dates of this manual. Updates are made to this publication on an unscheduled, as needed, basis. The updates will consist of a complete replacement manual and pertinent online or CD documentation. Manufacturing Part Number Supported Operating Systems Supported Smart Setup Version Supported Products (Servers) Publication Date T Microsoft Windows Server 2008 with Service Pack 2 (SP2) for Itanium-based Systems Microsoft Windows Server 2008 R2 with Service Pack 1 (SP1) Itanium Edition Version 7.1 BL860c BL870c BL860c i2 BL870c i2 BL890c i2 rx2800 i2 rx2660 rx3600 rx6600 rx7640 rx8640 Superdome sx2000 April, 2011 HP Encourages Your Comments HP encourages your comments concerning this document. We are committed to providing documentation that meets your needs. Send any errors found, suggestions for improvement, or compliments to: [email protected] Please include the document title, manufacturing part number, and any comment, error found, or suggestion for improvement you have concerning this document. 6

7 1 WBEM Provider Event Tables Introduction This reference guide describes the Windows System Log Event ID number, severity, and description of events generated by HP Integrity WBEM provider software. The WBEM providers are a group of services that run continuously in the background on HP Integrity servers and report the status of system components. Each WBEM provider has its own unique table in this document. Each row in the Platform Events table includes the following information about the event: ID number in the Windows System Log (the table is sorted on this field, in ascending order) Severity ( or ) Description, which includes the following information: a short description of the event probable cause of the event the recommended course of action the. WBEM EventID that generated the event the WBEM provider name Each row in the remaining WBEM provider event tables includes the following information about the event: ID number in the Windows System Log (the table is sorted on this field, in ascending order) Severity (Informational,, or ) Description Platform Events Table #1 Event ID numbers 0 through 6,999 Event ID 4 5 Event Severity Event Description A temperature inside the server has gone outside the factory specified range. Probable Cause: The temperature inside the server has gone outside the factory specified range for normal operation. Shutdown the system. This event may indicate one of the following conditions: a failed fan blocked air vents or poor ventilation around the server open server chassis cover, or missing drive slot covers high temperature in the room where the server resides an unusually hot hardware component located near one of the server's temperature sensors. Recommended Action: You should quit applications and shutdown the system. Find cause of temperature anomaly and fix it. WBEM EventID: 185. WBEM ProviderName: SEL02_IndicationProvider. A temperature inside the server has gone far outside the factory specified range. Probable Cause: The temperature inside the server has gone far outside the factory specified range for normal operation. To avoid permanent damage to your server hardware, go and turn off the server immediately. This event may indicate one of the following conditions: a failed fan blocked air vents or poor ventilation around the server open server chassis cover, or missing drive slot covers high temperature in the room where the server resides an unusually hot hardware component located near one of the server's temperature sensors. Recommended Action: Shutdown the system immediately. Find cause of temperature anomaly and fix it. WBEM EventID: 104. WBEM ProviderName: SEL02_IndicationProvider. Introduction 7

8 Event ID Event Severity Event Description Temperature sensor crossed upper non-recoverable threshold. Probable Cause: The temperature inside the server has gone far outside the factory specified range for normal operation. To avoid permanent damage to your server hardware, go and turn off the server immediately. This event may indicate one of the following conditions: a failed fan blocked air vents or poor ventilation around the server open server chassis cover, or missing drive slot covers high temperature in the room where the server resides an unusually hot hardware component located near one of the server's temperature sensors. Recommended Action: Shutdown the system immediately. Find cause of temperature anomaly and fix it. WBEM EventID: 105. WBEM ProviderName: SEL02_IndicationProvider. A measured voltage in the server has gone far outside the factory specified lower voltage range. Probable Cause: The voltage in the server has gone outside the factory set range. A bad component, blown fuse, poorly seated module, loose cable, or debris could be responsible for this failure. Recommended Action: Check all boards, power supplies, and modules that either supply or use this voltage rail. WBEM EventID: 113. WBEM ProviderName: SEL02_IndicationProvider. Voltage sensor crossed lower non-recoverable threshold. Probable Cause: The voltage in the server has gone far outside the factory set range and could damage system components. A bad component, blown fuse, poorly seated module, loose cable, or debris could be responsible for this failure. Recommended Action: Check all boards, power supplies, and modules that either supply or use this voltage rail. WBEM EventID: 114. WBEM ProviderName: SEL02_IndicationProvider. A measured voltage in the server has gone outside the factory specified upper voltage range. Probable Cause: The voltage in the server has gone outside the factory set range. A bad component, blown fuse, poorly seated module, loose cable, or debris could be responsible for this failure. Recommended Action: Check all boards, power supplies, and modules that either supply or use this voltage rail. WBEM EventID: 115. WBEM ProviderName: SEL02_IndicationProvider. Voltage sensor crossed upper non-recoverable threshold. Probable Cause: The voltage in the server has gone far outside the factory set range and could damage system components. A bad component, blown fuse, poorly seated module, loose cable, or debris could be responsible for this failure. Recommended Action: Check all boards, power supplies, and modules that either supply or use this voltage rail. WBEM EventID: 116. WBEM ProviderName: SEL02_IndicationProvider. The server's built-in sensors have detected an open chassis door. Probable Cause: The server has detect that the chassis door or other access panel is not securely closed. Recommended Action: Close any open panels or chassis doors. WBEM EventID: 127. WBEM ProviderName: SEL02_IndicationProvider. Power supply subsystem redundancy lost. Probable Cause: The Power Supply Subsystem now has only the minimum number of working power supply units required to maintain normal operation. There is no redundant (backup) power supply unit if one fails. Recommended Action: Since your server still has the minimum number of operational power supply modules, no immediate action is required. However, you should inspect the server for any bad power supply modules and replace them as soon as possible. WBEM EventID: 153. WBEM ProviderName: SEL02_IndicationProvider. Hot Swap Cage: SCSI cable removed. Probable Cause: This alert indicates that a SCSI cable, Jumper or Duplex Connector has either been disconnected or removed. This may make some SCSI devices inaccessible. Recommended Action: Ensure that all the required SCSI cables, jumpers or duplex connectors are correctly connected to the cage, disks, and/or the controller. WBEM EventID: 174. WBEM ProviderName: SEL02_IndicationProvider. 8 WBEM Provider Event Tables

9 Event ID Event Severity Event Description Uncorrectable multi-bit ECC error has occurred. Probable Cause: There has been an ECC double-bit error in one of the server's ECC memory modules. When an ECC double-bit memory error is detected, the system generates a Non-Maskable Interrupt that halts the system to prevent errors from propagating to other subsystems. Data being written or transmitted at the time may have been lost. Recommended Action: Make a note of the failed memory bank/board number and slot number, contact HP support to replace the failed module. WBEM EventID: 159. WBEM ProviderName: SEL02_IndicationProvider. Machine Check Initiated. Probable Cause: A Machine Check Abort event means the hardware detected a critical error. This event is generated whenever a system error due to processor, firmware, hardware and operating system is encountered. MCA events may be either recoverable or non-recoverable. If it is recoverable, the system will attempt to recover from the error for the purpose of maintaining high availability. An example of which is automatic disabling of a failing processor. For non-recoverable errors, the system will either stop or reboot to prevent data corruption and unreliable operation. Recommended Action: When this event is generated, it is highly advisable to consult both the operating system and hardware event logs to find out if there are other events that may help identify the cause of the MCA. If an MCA event occurs that causes the system to reboot, the failing component may be automatically disabled and the system continue to run but at a degraded performance level while awaiting repair. Therefore, for an MCA event, HP recommends contacting HP Customer Support to determine if a repair is needed. WBEM EventID: 173. WBEM ProviderName: SEL02_IndicationProvider. Generic trap for Critical or Fatal type E0 event from system firmware. Probable Cause: This event is generated when a critical or fatal event has occurred as reported by system firmware. The server is not operational and is in a state where it cannot provide more details about the failure. To obtain more information, log into the server's Management Processor Card and look at the event log for more details on the failure. Recommended Action: Contact HP Support for best course of action. HP may require a reboot, reconfiguration, or reflash of firmware. WBEM EventID: 162. WBEM ProviderName: SEL02_IndicationProvider. Voltage insufficient. Probable Cause: The input voltage for the system is not sufficient for operation. Recommended Action: Check all boards, power supplies, and modules that either supply or use this voltage rail. WBEM EventID: 118. WBEM ProviderName: SEL02_IndicationProvider. Voltage reached critical level. Probable Cause: The voltage in the server has gone outside the factory set range. A bad component, blown fuse, poorly seated module, loose cable, or debris could be responsible for this failure. Recommended Action: When this condition was detected the system should have been immediately shutdown to avoid damage. Contact your HP support representative as soon as possible to have the unit checked. Check all boards, power supplies, and modules that either supply or use this voltage rail. WBEM EventID: 120. WBEM ProviderName: SEL02_IndicationProvider. Power Pod Voltage Fault. Probable Cause: The voltage in the server has gone outside the factory set range. A bad component, blown fuse, poorly seated module, loose cable, or debris could be responsible for this failure. Recommended Action: Check all boards, power supplies, and modules that either supply or use this voltage rail. WBEM EventID: 121. WBEM ProviderName: SEL02_IndicationProvider. Voltage absent. Probable Cause: There is either a missing or failed power component. This may be a normal message when a system is not loaded to capacity and power components are purposefully left out of the system. Recommended Action: If this is unexpected, then check all boards, power supplies, and modules that either supply or use this voltage rail. WBEM EventID: 122. WBEM ProviderName: SEL02_IndicationProvider. Fan speed lags. Probable Cause: Possibly, the specified fan is beginning to lose performance. Recommended Action: If these errors continue to be reported, the fan should be replaced. WBEM EventID: 126. WBEM ProviderName: SEL02_IndicationProvider. Platform Events 9

10 Event ID Event Severity Event Description Power supply failure. Probable Cause: The system has detected that one of the power supplies has failed. Recommended Action: The power cable has been disconnected. Reconnect, or The power supply has failed. Contact your HP support representative to check the power supply. WBEM EventID: 137. WBEM ProviderName: SEL02_IndicationProvider. Power supply AC lost. Probable Cause: The power supply has lost its A/C source. The power supply is not connected to a working A/C power source. Recommended Action: Verify that the plug is connected to the power supply, and to a working power source. WBEM EventID: 139. WBEM ProviderName: SEL02_IndicationProvider. Power failure in power supply. Probable Cause: Indicates a failure with the AC power source that is connected to one of the redundant power supply units. Recommended Action: Check the power cord or source voltage. WBEM EventID: 155. WBEM ProviderName: SEL02_IndicationProvider. Voltage reached critical level. Probable Cause: The voltage in the server has gone outside the factory set range. A bad component, blown fuse, poorly seated module, loose cable, or debris could be responsible for this failure. Recommended Action: Check all boards, power supplies, and modules that either supply or use this voltage rail. WBEM EventID: 119. WBEM ProviderName: SEL02_IndicationProvider. System shut-down or reset caused by sensor reading. Probable Cause: A sensor reading in the system was determined to be non-recoverable and the system was shut down or reset. Recommended Action: Read the system logs to find which sensor was out of range. WBEM EventID: 167. WBEM ProviderName: SEL02_IndicationProvider. The BMC firmware did not detect the system firmware boot. Probable Cause: Possible Causes: 1. Bad System Firmware image in ROM 2. Power not reaching processors 3. Processor is in reset or is not properly seated in system 4. An unsupported processor was inserted in system 5. Communication with BMC is impaired. Recommended Action: To correct the problem, try the following: 1. Validate that processors are supported in this system. 2. Verify that processors are seated properly in system. 3. Check if system has booted (only a communication problem. - future events will also be lost.) 4. Attempt a system reset, INIT, and/or A/C cycle to clear the problem. 5. Update system firmware again if necessary. WBEM EventID: 132. WBEM ProviderName: SEL02_IndicationProvider. A/C Power failed, disconnected, or out of range. Probable Cause: The input power to the supply has failed or gone out of range. Or the input cord has been disconnected. Recommended Action: Check the power cord or source voltage. WBEM EventID: 154. WBEM ProviderName: SEL02_IndicationProvider. The power supply sensors detect a possible problem. Probable Cause: The power supply fan(s) is slowing. Recommended Action: Check power supply fan(s). WBEM EventID: 138. WBEM ProviderName: SEL02_IndicationProvider. Cooling unit warning. Probable Cause: The Cooling Unit may be running properly now, but it was detected in a degraded state. It may need to be replaced in the future. Recommended Action: Continue to monitor unit and contact HP support to determine appropriate action. WBEM EventID: 157. WBEM ProviderName: SEL02_IndicationProvider. Cooling unit failure. Probable Cause: A cooling unit has failed. Recommended Action: Replace the indicated cooling unit. WBEM EventID: 158. WBEM ProviderName: SEL02_IndicationProvider. BMC entering special mode. Probable Cause: BMC entering special mode. The system is not operating in a normal configuration. Some protection features may be disabled in this mode. Recommended Action: The Special Mode must be exited to ensure proper operation of the server. WBEM EventID: 166. WBEM ProviderName: SEL02_IndicationProvider. 10 WBEM Provider Event Tables

11 Event ID Event Severity Event Description Watchdog timer expired - hard reset. Probable Cause: Watchdog timer expired, and a hard reset of the system occurred. Recommended Action: Some process took longer than it should. Identify that process and contact the vendor of that application. WBEM EventID: 178. WBEM ProviderName: SEL02_IndicationProvider. Watchdog timer expired - power-off. Probable Cause: Watchdog timer expired, and the system was powered-off. Recommended Action: Some process took longer than it should. Identify that process and contact the vendor of that application. WBEM EventID: 179. WBEM ProviderName: SEL02_IndicationProvider. Watchdog timer expired - power-cycle. Probable Cause: Watchdog timer expired, and the system was power-cycled. Recommended Action: Some process took longer than it should. Identify that process and contact the vendor of that application. WBEM EventID: 180. WBEM ProviderName: SEL02_IndicationProvider. Missing FRU device. Probable Cause: A required device was not detected. See the System Event Log (SEL). Recommended Action: Install missing, required device. WBEM EventID: 182. WBEM ProviderName: SEL02_IndicationProvider. Missing Entity. Probable Cause: A required device was not detected. Recommended Action: Install missing, required device. WBEM EventID: 183. WBEM ProviderName: SEL02_IndicationProvider. System event log almost full. Probable Cause: The System Event Log is almost full. Recommended Action: Review the log for any important events, then clear it. WBEM EventID: 163. WBEM ProviderName: SEL02_IndicationProvider. TOC interrupt (crash dump). Probable Cause: The critical interrupt sensor has detected that there was a Diagnostic Interrupt initiated by IPMI command. Either the Transfer Of Control (TOC) button was pressed or the interrupt was initiated remotely. The system will reboot after the interrupt processing is finished. Recommended Action: If this is unexpected behavior, then check logs for events that would have caused an INIT, TOC, or RESET. WBEM EventID: 169. WBEM ProviderName: SEL02_IndicationProvider. INIT Initiated. Probable Cause: The critical interrupt sensor has detected that there was a Diagnostic Interrupt initiated by IPMI command. Either the Transfer Of Control (TOC) button was pressed or the interrupt was initiated remotely. The system will reboot after the interrupt processing is finished. Recommended Action: If this is unexpected behavior, then check logs for events that would have caused an INIT, TOC, or RESET. WBEM EventID: 170. WBEM ProviderName: SEL02_IndicationProvider. PCI system error detected. Probable Cause: An I/O device (or host bridge) detected an internal error. OR An I/O device (or host bridge) detected a bus error. Recommended Action: For an I/O device failure, consult the error logs for additional information. Determine and replace the failed I/O device. For an I/O host bridge failure, contact your HP representative to check the I/O host bridge. WBEM EventID: 172. WBEM ProviderName: SEL02_IndicationProvider. OS run-time critical shutdown. Probable Cause: The OS caused the system to shut down. Recommended Action: Look at OS logs and crash data to determine why the system shut down. WBEM EventID: 175. WBEM ProviderName: SEL02_IndicationProvider. ACPI state S5 (soft-off, entered by override). Probable Cause: The system has been powered OFF with a hard power-down. Recommended Action: HP recommends that when you powered down the system you use the normal shutdown procedure to properly shut down the operating system. Otherwise, data-loss and/or hardware failure can occur. WBEM EventID: 176. WBEM ProviderName: SEL02_IndicationProvider. Platform Events 11

12 Event ID Event Severity Event Description PCI parity error detected. Probable Cause: An I/O device (or host bridge) detected a bus parity error, OR An I/O device (or host bridge) mastered a bus transaction and received a parity error response from the target. Recommended Action: For an I/O bus parity error, consult the error logs for additional information. Determine and replace the failed I/O device. For an I/O host bridge failure, contact your HP representative to check the I/O host bridge. WBEM EventID: 171. WBEM ProviderName: SEL02_IndicationProvider. Temperature sensor crossed upper non-critical threshold. Probable Cause: The temperature inside the server has gone outside the factory specified range for normal operation. You should quit applications and power down the server to protect its hardware from damage. This event may indicate one of the following conditions: A failed fan, blocked air vents or poor ventilation around the server, open server chassis cover, or missing drive slot covers, high temperature in the room where the server resides, an unusually hot hardware component located near one of the server's temperature sensors. Recommended Action: You should quit applications and shutdown the system. Find cause of temperature anomaly and fix it. WBEM EventID: 100. WBEM ProviderName: SEL02_IndicationProvider. A temperature inside the server went far outside the factory specified range. Probable Cause: The temperature inside the server has gone far outside the factory specified range for normal operation. To avoid permanent damage to your server hardware, go and turn off the server immediately. This event may indicate one of the following conditions: a failed fan blocked air vents or poor ventilation around the server open server chassis cover, or missing drive slot covers high temperature in the room where the server resides an unusually hot hardware component located near one of the server's temperature sensors. Recommended Action: Shutdown the system immediately. Find cause of temperature anomaly and fix it. WBEM EventID: 101. WBEM ProviderName: SEL02_IndicationProvider. Temperature sensor crossed upper non-recoverable threshold. Probable Cause: The temperature inside the server has gone far outside the factory specified range for normal operation. To avoid permanent damage to your server hardware, go and turn off the server immediately. This event may indicate one of the following conditions: a failed fan blocked air vents or poor ventilation around the server open server chassis cover, or missing drive slot covers high temperature in the room where the server resides an unusually hot hardware component located near one of the server's temperature sensors. Recommended Action: Shutdown the system immediately. Find cause of temperature anomaly and fix it. WBEM EventID: 102. WBEM ProviderName: SEL02_IndicationProvider. One of the temperature sensors crossed its upper non-critical threshold. Probable Cause: The temperature inside the server has gone outside the factory specified range for normal operation. This event may indicate one of the following conditions: a failed fan blocked air vents or poor ventilation around the server open server chassis cover, or missing drive slot covers high temperature in the room where the server resides an unusually hot hardware component located near one of the server's temperature sensors. Recommended Action: You should quit applications and shutdown the system.find cause of temperature anomaly and fix it. WBEM EventID: 107. WBEM ProviderName: SEL02_IndicationProvider. A temperature inside the server went far outside the factory specified range. Probable Cause: The temperature inside the server has gone far outside the factory specified range for normal operation. To avoid permanent damage to your server hardware, go and turn off the server immediately. This event may indicate one of the following conditions: a failed fan blocked air vents or poor ventilation around the server open server chassis cover, or missing drive slot covers high temperature in the room where the server resides an unusually hot hardware component located near one of the server's temperature sensors. Recommended Action: Shutdown the system immediately. Find cause of temperature anomaly and fix it. WBEM EventID: 108. WBEM ProviderName: SEL02_IndicationProvider. 12 WBEM Provider Event Tables

13 Event ID Event Severity Event Description The AC voltage to the power supply was lost or is out of range. Probable Cause: The AC voltage was lost, or is the wrong range for the system. Recommended Action: Verify the power supply is plugged in to the proper voltage for the system. WBEM EventID: 140. WBEM ProviderName: SEL02_IndicationProvider. The power supply AC voltage is out of range. Probable Cause: The AC voltage is connected to the power supply, but it is not the voltage range required for the system. Recommended Action: Connect the power supply to the proper voltage range. WBEM EventID: 141. WBEM ProviderName: SEL02_IndicationProvider. Invalid OS INIT checksum. Probable Cause: OS has registered a bad OS_INIT vector or the data has been lost. Recommended Action: Reboot system to allow vector to be re-registered. WBEM EventID: WBEM ProviderName: Bad OS MCA checksum. Probable Cause: OS has registered a bad OS_MCA vector or the data has been lost. Recommended Action: Reboot system to allow vector to be re-registered. WBEM EventID: 200. WBEM ProviderName: BMC interface to IPMI failed. Probable Cause: BMC firmware has locked up or the BMC is disabled. Recommended Action: Cycle system power and attempt boot again. If error re-occurs contact your HP representative for support. WBEM EventID: 201. WBEM ProviderName: Boot cell launch EFI failure. Probable Cause: The system has failed to launch EFI because of an internal error. Recommended Action: Reboot or update System FW. If problem persists contact your HP representative for support. WBEM EventID: 203. WBEM ProviderName: Monarch selection failure. Probable Cause: An internal error has caused monarch selection to fail. Recommended Action: Reboot. If problem persists contact your HP representative for support. WBEM EventID: 204. WBEM ProviderName: CPU monarch collision. Probable Cause: Unexpected error has occurred during monarch selection. Recommended Action: Reboot, if problem persists contact your HP representative for support. WBEM EventID: 205. WBEM ProviderName: Boot cell virtualize EFI failure. Probable Cause: An internal error has occurred that prevented EFI from virtualizing. Recommended Action: Reboot, if problem persists contact your HP representative for support. WBEM EventID: 207. WBEM ProviderName: Boot cell virtualize PAL failure. Probable Cause: SFW was unable to virtualize PAL. Recommended Action: Reboot, if problem persists contact your HP representative for support. WBEM EventID: 208. WBEM ProviderName: Boot cell virtualize SAL failure. Probable Cause: SFW was unable to virtualize SAL. Recommended Action: Reboot, if problem persists contact your HP representative for support. WBEM EventID: 209. WBEM ProviderName: Boot cell virtualize SALPROC failure. Probable Cause: SFW was unable to virtualize SALPROC. Recommended Action: Reboot, if problem persists contact your HP representative for support. WBEM EventID: 210. WBEM ProviderName: CPU struct init failed. Probable Cause: A CPU has failed the configuration process. Recommended Action: Replace CPU. If problem persists contact your HP representative for support. WBEM EventID: 211. WBEM ProviderName: CPU failed early config. Probable Cause: A CPU has failed the early configuration process. Recommended Action: Reboot. If problem persists contact your HP representative for support. WBEM EventID: 212. WBEM ProviderName: Platform Events 13

14 Event ID Event Severity Event Description CPU failed early selftest. Probable Cause: A CPU has failed early self test. Recommended Action: Replace CPU. If problem persists contact your HP representative for support. WBEM EventID: 213. WBEM ProviderName: CPU failed. Probable Cause: A CPU has failed. Recommended Action: Replace CPU. If problem persists contact your HP representative for support. WBEM EventID: 214. WBEM ProviderName: CPU failed late selftest. Probable Cause: For ZX1 systems, a Correctable Single Bit Memory error has caused CPU late self test to fail. It is possible the CPU is not faulty in this case. For zx2 systems, the CPU has failed selftest. Recommended Action: Look for the event 'MEM_CORR_ERR' from the last time the system was running. If you find these events, replace that DIMM(s) before replacing the CPU's. Replace DIMMs with excessive 'MEM_CORR_ERR' first. If after replacing all suspect DIMMs this event is still seen, replace the CPU. Probable Cause: A CPU has failed. Recommended Action: Replace CPU. If problem persists contact your HP representative for support. WBEM EventID: 215. WBEM ProviderName: CPU not enough late test memory. Probable Cause: Insufficient memory. Recommended Action: Increase memory and reboot. WBEM EventID: 216. WBEM ProviderName: Could not allocate memory for EFI image. Probable Cause: SFW could not allocate enough memory for EFI image. Recommended Action: Reboot. If problem persists contact your HP representative for support. WBEM EventID: 217. WBEM ProviderName: EFI image corrupted. Probable Cause: EFI image is corrupted. Recommended Action: Reboot, if problem persists contact your HP representative for support. WBEM EventID: 218. WBEM ProviderName: EFI not in fit table. Probable Cause: EFI image is not in FIT. Recommended Action: Reboot, if problem persists contact your HP representative for support. WBEM EventID: 219. WBEM ProviderName: NVRAM test fail. Probable Cause: NVM is corrupted or bad. Recommended Action: Clear NVM, if problem persists contact your HP representative for support. WBEM EventID: 220. WBEM ProviderName: EFI Rom size bad. Probable Cause: EFI image is corrupt. Recommended Action: Reboot, if problem persists contact your HP representative for support. WBEM EventID: 221. WBEM ProviderName: EFI Rom checksum error. Probable Cause: EFI image is corrupt. Recommended Action: Reboot, if problem persists contact your HP representative for support. WBEM EventID: 222. WBEM ProviderName: External interruption nest limit exceeded. Probable Cause: Internal FW error. Recommended Action: Reboot, if problem persists contact your HP representative for support. WBEM EventID: 223. WBEM ProviderName: External interrupt not serviced. Probable Cause: Internal FW error. Recommended Action: Reboot, if problem persists contact your HP representative for support. WBEM EventID: 224. WBEM ProviderName: Ext int taken. Probable Cause: An external interrupt has been taken. Recommended Action: Reboot. If problem persists contact your HP representative for support. WBEM EventID: 225. WBEM ProviderName: Forward Progress Log (FPL) access failed. Probable Cause: FPL access has failed, possibly due to BMC communication interruption. SFW will not send any events to the FPL until the system is rebooted. Recommended Action: Reboot or update System and BMC FW. If problem persists contact your HP representative for support. WBEM EventID: 226. WBEM ProviderName: 14 WBEM Provider Event Tables

15 Event ID Event Severity Event Description PSR fetch failure. Probable Cause: SFW tried to read the Processor Status Register before the CPU data structure has been setup. Recommended Action: Reboot, if problem persists contact your HP representative for support. WBEM EventID: 227. WBEM ProviderName: Cell halt. Probable Cause: Internal. Recommended Action: contact your HP representative for support. WBEM EventID: 228. WBEM ProviderName: CPU PAL incompatible with cpu. Probable Cause: Incompatible PAL. Recommended Action: Update SFW or change processors. WBEM EventID: 229. WBEM ProviderName: Slave is incompatible with monarch. Probable Cause: Incompatible processors. Recommended Action: Replace processors. WBEM EventID: 230. WBEM ProviderName: Interrupt clear failure. Probable Cause: Interrupt clear failed. Recommended Action: Reboot, if problem persists contact your HP representative for support. WBEM EventID: 231. WBEM ProviderName: System Event Log (SEL) access failed. Probable Cause: An IPMI event has failed. Recommended Action: Reset the BMC and reboot. If problem persists, contact HP support to troubleshoot the problem. WBEM EventID: 232. WBEM ProviderName: Trap taken. Probable Cause: This will follow other events indicating some type of IVT error. Recommended Action: This event is for debugging the address, other events will determine the user action. WBEM EventID: 233. WBEM ProviderName: LDB State bad on entry. Probable Cause: No action is required. WBEM EventID: 234. WBEM ProviderName: Interrupt with ic bit clear. Probable Cause: Interrupt context was lost because the ic bit was cleared. Recommended Action: Reboot, if problem persists contact your HP representative for support. WBEM EventID: 235. WBEM ProviderName: Min-state registration failure. Probable Cause: Registering of the processor min state save area with PAL has failed. Recommended Action: Reboot, if problem persists contact your HP representative for support. WBEM EventID: 236. WBEM ProviderName: Boot monarch timed out. Probable Cause: The monarch has timed out. Recommended Action: No action is required. Replace CPU if problem persists, system will reboot after this event. WBEM EventID: 238. WBEM ProviderName: PAL_B not in FIT table. Probable Cause: Internal or ROM is corrupted. Recommended Action: Reboot, if problem persists contact your HP representative for support. WBEM EventID: 239. WBEM ProviderName: SAL_B not in FIT table. Probable Cause: Internal or ROM is corrupted. Recommended Action: Reboot, if problem persists contact your HP representative for support. WBEM EventID: 240. WBEM ProviderName: NVRAM test fail. Probable Cause: NVM is corrupt or bad. Recommended Action: Reboot, if problem persists contact your HP representative for support. WBEM EventID: 241. WBEM ProviderName: Interrupt vector out of range. Probable Cause: An internal error has occurred. Recommended Action: Reboot, if problem persists contact your HP representative for support. WBEM EventID: 242. WBEM ProviderName: Platform Events 15

16 Event ID Event Severity Event Description Pal proc error getting pal copy info. Probable Cause: PAL_COPY_PAL_INFO call returned a failure. Recommended Action: Reboot, if problem persists contact your HP representative for support. WBEM EventID: 243. WBEM ProviderName: Pal proc error copying pal to memory. Probable Cause: There has been an error copying PAL to memory. Recommended Action: Reboot, if problem persists contact your HP representative for support. WBEM EventID: 244. WBEM ProviderName: Boot pal proc failure. Probable Cause: Internal PAL. Recommended Action: Reboot, if problem persists contact your HP representative for support. WBEM EventID: 245. WBEM ProviderName: Console device failure. Probable Cause: A console device has failed. Recommended Action: Reset console device/system. WBEM EventID: 246. WBEM ProviderName: Platform interface device failure. Probable Cause: A console device has failed. Recommended Action: Reset console device/system. If problem persists contact your HP representative for support. WBEM EventID: 247. WBEM ProviderName: platform scratch RAM test failed. Probable Cause: Bad or corrupt Scratch RAM. Recommended Action: Reboot, if problem persists contact your HP representative for support. WBEM EventID: 248. WBEM ProviderName: CPU rendezvous failure. Probable Cause: Bad or slow CPU. Recommended Action: Replace CPU. WBEM EventID: 249. WBEM ProviderName: extracting sal_b from rom. Probable Cause: ROM Corrupt or unreadable. Recommended Action: Reboot, if problem persists contact your HP representative for support. WBEM EventID: 250. WBEM ProviderName: Scratch RAM bad. Probable Cause: Bad or corrupt Scratch RAM. Recommended Action: Reboot, if problem persists contact your HP representative for support. WBEM EventID: 251. WBEM ProviderName: IPMI System Event Log (SEL) is full. Probable Cause: IPMI SEL full. Recommended Action: Clear SEL through BMC or MP. WBEM EventID: 252. WBEM ProviderName: Slave wakeup before vector registered. Probable Cause: No wakeup vector registered for processor. Recommended Action: Reboot, if problem persists contact your HP representative for support. WBEM EventID: 253. WBEM ProviderName: CPU failed rendezvous handler. Probable Cause: SFW is unable to determine the FSB speed. Recommended Action: Reboot, if problem persists contact your HP representative for support. WBEM EventID: 254. WBEM ProviderName: building SMBIOS Tables. Probable Cause: SFW failed to build the SMBIOS tables. Recommended Action: If SMBIOS is preventing functionality, reboot. If problem persists contact your HP representative for support. WBEM EventID: 255. WBEM ProviderName: Trap nest limit exceeded. Probable Cause: The trap nesting limit has been exceeded. Recommended Action: Reboot if necessary, if problem persists contact your HP representative for support. WBEM EventID: 256. WBEM ProviderName: Trap not serviced. Probable Cause: A invalid trap has been requested or a trap has not been installed. Recommended Action: Reboot if necessary, if problem persists contact your HP representative for support. WBEM EventID: 257. WBEM ProviderName: 16 WBEM Provider Event Tables

17 Event ID Event Severity Event Description Trap taken. Probable Cause: A trap has been taken. Recommended Action: Reboot or update System FW. If problem persists contact your HP representative for support. WBEM EventID: 258. WBEM ProviderName: Uncleared interrupt. Probable Cause: At least one interrupt was not cleared. Recommended Action: No action is required. WBEM EventID: 259. WBEM ProviderName: Unexpected external interrupt. Probable Cause: An unexpected external interrupt has occurred. Recommended Action: Reboot or update System FW. If problem persists contact your HP representative for support. WBEM EventID: 260. WBEM ProviderName: Interrupt before redirection table set up. Probable Cause: An interrupt has occurred before setting up the Interrupt Vector Table. Recommended Action: Reboot, if problem persists contact your HP representative for support. WBEM EventID: 261. WBEM ProviderName: CPU unexpected MCA. Probable Cause: Unexpected MCA. Recommended Action: Reboot or update System FW. If problem persists contact your HP representative for support. WBEM EventID: 262. WBEM ProviderName: Unexpected trap. Probable Cause: An unexpected trap has occurred. During System Firmware boot time this indicates the system has requested a trap that firmware has not registered. During OS run time it indicates the system has requested a trap that is not recognized in the OS's trap table. Recommended Action: If at FW boot time, reboot or upgrade System FW. If problem persists contact your HP representative for support. If at OS run time, verify that the OS has properly installed its trap handler, and that only valid traps are caused. Investigate what could cause the trap that is signaled by the event or why the OS has not properly installed the trap handler. If problem persists contact your HP representative for support. WBEM EventID: 263. WBEM ProviderName: CPU unknown boot error. Probable Cause: Unknown error. Recommended Action: Reboot or update System FW. If problem persists contact your HP representative for support. WBEM EventID: 264. WBEM ProviderName: CC errors PAL failure. Probable Cause: SFW has detected a PAL Failure. Recommended Action: Reboot, update SFW if necessary, if problem persists contact your HP representative for support. WBEM EventID: 265. WBEM ProviderName: Expected MC vector unregistered. Probable Cause: Expected Machine Check Vector not registered at the time of an Expected Machine Check. Recommended Action: Contact HP support to troubleshoot the problem. WBEM EventID: 266. WBEM ProviderName: INIT initiated. Probable Cause: Software has requested an INIT or the INIT button has been pressed. Recommended Action: No action is required. WBEM EventID: 267. WBEM ProviderName: Expected I/O host bridge is missing. Probable Cause: I/O host bridge failure. An incorrect I/O backplane is installed. Recommended Action: Contact your HP representative to check the I/O host bridge and the I/O backplane. WBEM EventID: 268. WBEM ProviderName: LBA has unexpected number of I/O slots. Probable Cause: The firmware needs to be updated. An incorrect I/O backplane is installed. Recommended Action: Contact your HP representative to check the firmware and the I/O backplane. WBEM EventID: 269. WBEM ProviderName: I/O rope width does not match expected value. Probable Cause: The firmware needs to be updated. An incorrect I/O backplane is installed. Recommended Action: Update SFW. If problem persists, contact your HP representative to check the I/O backplane. WBEM EventID: 270. WBEM ProviderName: Platform Events 17

18 Event ID Event Severity Event Description Found unexpected I/O host bridge. Probable Cause: The firmware needs to be updated. An incorrect I/O backplane is installed. Recommended Action: Update SFW. If problem persists, contact your HP representative to check the I/O backplane. WBEM EventID: 271. WBEM ProviderName: PCI clock DLL error. Probable Cause: Failed I/O chipset. Failed I/O backplane. Recommended Action: Contact your HP representative to check the I/O chipset and backplane. WBEM EventID: 272. WBEM ProviderName: PCI hot plug controller failed. Probable Cause: Hot-plug controller failure. I/O host bridge failure. Recommended Action: Contact your HP representative to check the hot-plug controller and the I/O host bridge. WBEM EventID: 273. WBEM ProviderName: Found unknown I/O rope width. Probable Cause: Internal firmware error. Recommended Action: Contact your HP representative to check the firmware. WBEM EventID: 274. WBEM ProviderName: I/O LBA clear error failed. Probable Cause: A failed or improperly seated I/O card is present. Recommended Action: Replace or reseat the I/O card(s). WBEM EventID: 275. WBEM ProviderName: I/O host bridge inaccessible because rope reset failed to complete. Probable Cause: I/O CEC failure. Recommended Action: Contact your HP representative to check the I/O CEC. WBEM EventID: 276. WBEM ProviderName: Insufficient power to turn on PCI slot. Probable Cause: The power budget for the IO subsystem has been exceeded. Recommended Action: The IO config in the system is unsupported. Verify that the IO config installed in the system is one that is supported. If problem persists contact your HP representative for support. WBEM EventID: 277. WBEM ProviderName: PCI bus walk unknown error. Probable Cause: Internal firmware error. Recommended Action: Contact your HP representative to check the firmware. WBEM EventID: 278. WBEM ProviderName: PCI bus walk resources exceeded. Probable Cause: Unsupported I/O configuration. Recommended Action: Remove any unsupported I/O cards. Move the I/O card to another slot. WBEM EventID: 279. WBEM ProviderName: PCI bus unmap unknown error. Probable Cause: Internal firmware error. Recommended Action: Contact your HP representative to check the firmware. WBEM EventID: 280. WBEM ProviderName: PCIXCAP sampling error. Probable Cause: I/O host bridge failure. Recommended Action: Contact your HP representative to check the I/O host bridge. WBEM EventID: 281. WBEM ProviderName: Power monitor failed to respond. Probable Cause: BMC failure. Recommended Action: Contact your HP representative to check the BMC. WBEM EventID: 282. WBEM ProviderName: I/O rope reset failed to complete. Probable Cause: I/O CEC failure. Recommended Action: Reboot. If problem persists, contact your HP representative to check the I/O controller. WBEM EventID: 283. WBEM ProviderName: I/O SBA clear error failed. Probable Cause: I/O chipset failure. Recommended Action: Contact your HP representative to check the I/O chipset. WBEM EventID: 284. WBEM ProviderName: PCI slot has incorrect default power state. Probable Cause: The hot-plug controller has failed. Recommended Action: Contact your HP representative to check the hot-plug slot. WBEM EventID: 285. WBEM ProviderName: PCI slot power on error. Probable Cause: The I/O card is damaged or improperly inserted. Recommended Action: Replace or reseat the I/O card. WBEM EventID: 286. WBEM ProviderName: 18 WBEM Provider Event Tables

19 Event ID Event Severity Event Description PCI slot's standby power failed. Probable Cause: I/O slot failure. Recommended Action: Reseat IO card. Replace IO card. If problem persists, contact your HP representative to check the I/O slot. WBEM EventID: 287. WBEM ProviderName: Found invalid PCIXCAP value. Probable Cause: I/O host bridge failure. Hot-plug controller failure. Recommended Action: Contact your HP representative to check the I/O host bridge or the hot-plug controller. WBEM EventID: 288. WBEM ProviderName: Unsupported rope frequency. Probable Cause: Internal firmware error. Recommended Action: Contact your HP representative to check the firmware. WBEM EventID: 289. WBEM ProviderName: Unsupported host bridge type. Probable Cause: Firmware needs to be updated. An incorrect I/O backplane is installed. Recommended Action: Contact your HP representative to check the firmware and the I/O backplane. WBEM EventID: 290. WBEM ProviderName: Machine Check initiated. Probable Cause: A Machine Check has occurred. Recommended Action: Analyze cause of Machine Check using diag's and EFI tools. WBEM EventID: 292. WBEM ProviderName: in temporary mdt area. Probable Cause: The memory area where the MDT is supposed to be built has an error in it, so the MDT cannot be built there. Recommended Action: Reboot, if problem persists contact your HP representative for support. WBEM EventID: 293. WBEM ProviderName: Failed to find lmmio entry in mdt. Probable Cause: The MDT table is bad because it did not have an LMMIO entry in it. Recommended Action: Reboot, if problem persists contact your HP representative for support. WBEM EventID: 294. WBEM ProviderName: Memory page zero bad. Probable Cause: Memory page 0 was slated for deallocation in the PDT. Recommended Action: FW is written such that this event should never be generated. If the user sees this event, please contact HP support. WBEM EventID: 295. WBEM ProviderName: Failed to find space in mdt. Probable Cause: FW requested an entry in the MDT, and there wasn't a large enough chunk of contiguous memory for the requested size. Recommended Action: Reboot, if problem persists contact your HP representative for support. WBEM EventID: 296. WBEM ProviderName: Media failure: info was not retrieved/logged. Probable Cause: The handler has failed to retrieve or log data due to a media failure. Recommended Action: Reboot if necessary, if problem persists contact your HP representative for support. WBEM EventID: 297. WBEM ProviderName: Bus interface register test failed. Probable Cause: The CEC failed the register test. Recommended Action: Contact HP support to troubleshoot the problem. WBEM EventID: 298. WBEM ProviderName: Memory ECC normal write/read test failed. Probable Cause: The DIMM that maps to address 0 is not seated properly. Recommended Action: Check all of the DIMMs in the system and make sure that they are inserted fully into the slot with the retention mechanism in place. WBEM EventID: 299. WBEM ProviderName: DIMM loading order error: DIMM deallocated. Probable Cause: A required DIMM is not loaded in order to allow for proper operation of the DIMM specified in the physical location. Recommended Action: Refer to the user's manual for Memory loading instructions. WBEM EventID: 300. WBEM ProviderName: DIMM SPD checksum failed. Probable Cause: The DIMMs SPD EEPROM got corrupted. Recommended Action: Contact HP Support personnel to troubleshoot the problem. WBEM EventID: 301. WBEM ProviderName: Platform Events 19

20 Event ID Event Severity Event Description DIMM SPD fatal error. Probable Cause: Detection of SPD error type - various types. Recommended Action: Reseat or replace the DIMM. If problem persists, contact HP Support personnel to troubleshoot the problem. WBEM EventID: 302. WBEM ProviderName: Unsupported memory DIMM type. Probable Cause: A DIMM with an invalid DIMM type was found. Recommended Action: Contact HP Support personnel to troubleshoot the problem. WBEM EventID: 303. WBEM ProviderName: The DIMM type of this DIMM doesn't match with others in the DIMM group. Probable Cause: The DIMMs in the rank do not have the same DIMM type. Recommended Action: Contact HP Support personnel to troubleshoot the problem. WBEM EventID: 304. WBEM ProviderName: The DIMM type table is full. New DIMM type cannot be added. Probable Cause: Too many different types of DIMMs in system. Recommended Action: Reduce the number of different types of DIMMs in the system. WBEM EventID: 305. WBEM ProviderName: DIMM number not found in DMT Table. Probable Cause: Probable internal FW error. Recommended Action: Reload System Firmware. Recommended Action: Contact HP Support personnel to troubleshoot the problem. WBEM EventID: 306. WBEM ProviderName: Memory ECC multiple-bit data error detection failed. Probable Cause: The CEC failed MBE detection. Recommended Action: Contact HP support personnel to troubleshoot the problem. WBEM EventID: 307. WBEM ProviderName: Memory ECC multiple-bit ECC error signalling failed. Probable Cause: The CEC failed MBE detection. Recommended Action: Contact HP support personnel to troubleshoot the problem. WBEM EventID: 308. WBEM ProviderName: Memory ECC single-bit data error detection failed. Probable Cause: The CEC failed SBE detection. Recommended Action: Contact HP support personnel to troubleshoot the problem. WBEM EventID: 309. WBEM ProviderName: Memory ECC single-bit ECC error detection failed. Probable Cause: The CEC failed SBE detection. Recommended Action: Contact HP support personnel to troubleshoot the problem. WBEM EventID: 310. WBEM ProviderName: Memory address not found in MBAT. Probable Cause: The address logged in the CEC doesn't map to a memory rank, possibly due to a SFW error or NVM corruption. Recommended Action: Contact HP support to troubleshoot the problem. WBEM EventID: 312. WBEM ProviderName: Memory Information not cleared. Probable Cause: Software or CEC error. Recommended Action: Contact HP support to troubleshoot the problem. WBEM EventID: 313. WBEM ProviderName: Couldn't clear memory error logs. Probable Cause: SFW or CEC error. Recommended Action: Contact HP support to troubleshoot the problem. WBEM EventID: 314. WBEM ProviderName: Memory error clear failed. Probable Cause: SFW error or CEC error. Recommended Action: Contact HP support to troubleshoot the problem. WBEM EventID: 315. WBEM ProviderName: DIMM loading order error: DIMM deallocated. Probable Cause: A required DIMM is not loaded in order to allow for proper operation of the DIMM specified in the physical location. Recommended Action: Refer to the user's manual for Memory loading instructions. WBEM EventID: 316. WBEM ProviderName: Generic memory firmware error. Probable Cause: Corrupt NVM or System firmware failure. Recommended Action: Contact HP support to troubleshoot the problem. WBEM EventID: 317. WBEM ProviderName: 20 WBEM Provider Event Tables

21 Event ID Event Severity Event Description Memory interleaving algorithm failed. Probable Cause: Unspecified. WBEM EventID: WBEM ProviderName: Memory interleave generation failed. Probable Cause: DIMM(s) that map into low memory have errors on them. Recommended Action: Contact HP support to troubleshoot the problem. WBEM EventID: 318. WBEM ProviderName: Uncorrectable (multiple-bit) ECC error in DIMM. Probable Cause: Multiple bit error in DIMM. Recommended Action: Contact HP Support personnel to troubleshoot the problem. WBEM EventID: WBEM ProviderName: Memory register test failed. Probable Cause: Internal SFW error. Recommended Action: Update to most recent SFW. WBEM EventID: 319. WBEM ProviderName: SPD found no memory DIMMs. Probable Cause: No DIMMs were detected. Recommended Action: Install DIMMs or Contact HP Support personnel to troubleshoot the problem. WBEM EventID: 320. WBEM ProviderName: No memory found. Probable Cause: FW found memory, but it could not find a correctly loaded rank. Recommended Action: Before this event is sent, FW will output which ranks it is deallocating and why. Review the preceding events and refer to the users manual to correct the memory loading. WBEM EventID: 321. WBEM ProviderName: Cannot log memory error because PDT is disabled. Probable Cause: FW found memory errors during selftest, but could not deallocate the page because the PDT is disabled. Recommended Action: Re-enable the PDT by clearing NVM. WBEM EventID: 322. WBEM ProviderName: PDT is disabled. Probable Cause: Informational event indicating that FW will not use the PDT this boot. Recommended Action: No action is needed if user does not want to use the PDT, otherwise, clear NVM. WBEM EventID: 323. WBEM ProviderName: adding entry to PDT. Probable Cause: NVM write error. Recommended Action: Contact HP support personnel to troubleshoot the problem. WBEM EventID: 324. WBEM ProviderName: Cannot add PDT entry-pdt full. Probable Cause: An attempt was made to add an entry to a full PDT. Recommended Action: Run the 'pdt' command from the EFI shell and remove/replace the DIMM that has the most PDT entries. If that doesn't work, contact HP support. WBEM EventID: WBEM ProviderName: Memory platform data update failure. Probable Cause: Memory FW was unable to save or restore the original error configuration. Recommended Action: If this is seen, update SFW. WBEM EventID: 326. WBEM ProviderName: Can't find memory rank entry. Probable Cause: The rank structure that corresponds to the rankid in the data field could not be found in the Rank table, possibly due to NVM corruption. Recommended Action: Contact HP support to troubleshoot the problem. WBEM EventID: 327. WBEM ProviderName: Memory error overflow:. Probable Cause: An error other than a memory error occurred during the memory test. Recommended Action: Contact HP support to troubleshoot the problem. WBEM EventID: 329. WBEM ProviderName: Memory forward progress code invalid. Probable Cause: The forward progress bits are invalid. Recommended Action: Upgrade to latest system firmware, or contact HP support to troubleshoot the problem. WBEM EventID: 330. WBEM ProviderName: Platform Events 21

22 Event ID Event Severity Event Description Memory error status invalid. Probable Cause: Non-memory errors were detected during the memory test that FW doesn't know how to handle. Recommended Action: Update to the latest SFW. Recommended Action: Contact HP support to troubleshoot the problem. WBEM EventID: 331. WBEM ProviderName: Memory error summary bits invalid. Probable Cause: The memory test summary word is invalid. Recommended Action: Update to the latest SFW. Recommended Action: Contact HP support to troubleshoot the problem. WBEM EventID: 332. WBEM ProviderName: Unexpected machine check during memory code. Probable Cause: Incompatible memory controller and memory DIMM. Recommended Action: Update system board with current memory controller. WBEM EventID: WBEM ProviderName: Serial Presence Detect (SPD) has been skipped. Probable Cause: Control bit to skip DIMM SPD check is set. Recommended Action: Clear NVM. Recommended Action: Update PDC. Recommended Action: Contact HP support to troubleshoot the problem. WBEM EventID: 337. WBEM ProviderName: An Alternate Memory Config has been loaded into the system. Probable Cause: Control bit to use an alternate memory config are set. Recommended Action: Clear NVM Update SFW Contact HP support to troubleshoot the problem. WBEM EventID: 338. WBEM ProviderName: Nested Machine Checks. Probable Cause: A second machine check occurred while the system was processing a machine check. Recommended Action: If automated analysis has not occurred, use diagnostics or the MCA analyzer to determine the cause. WBEM EventID: WBEM ProviderName: OS INIT address not registered. Probable Cause: The OS has not registered an OS_INIT vector. Recommended Action: No action is required. The OS has failed to register the vector or has chosen not to. WBEM EventID: 340. WBEM ProviderName: OS MCA address not registered. Probable Cause: The OS has not registered an OS_MCA vector. Recommended Action: None, the OS has failed to register the vector or has chosen not to. WBEM EventID: 341. WBEM ProviderName: OS MCA did not correct the Machine Check. Probable Cause: Uncorrected Machine Check. Recommended Action: Analyze cause of Machine Check using diagnostic and EFI tools. WBEM EventID: 342. WBEM ProviderName: Found bad miscellaneous register. Probable Cause: A PDH register has failed. Recommended Action: Reboot if necessary, if problem persists contact your HP representative for support. WBEM EventID: 343. WBEM ProviderName: SAL_CHECK failed for an unknown reason. Probable Cause: The handler for SAL_CHECK has failed for an unknown reason. Recommended Action: Reboot if necessary, if problem persists contact your HP representative for support. WBEM EventID: 344. WBEM ProviderName: SAL_INIT failed for an unknown reason. Probable Cause: The handler for SAL_INIT has failed for an unknown reason. Recommended Action: Reboot if necessary, if problem persists contact your HP representative for support. WBEM EventID: 345. WBEM ProviderName: Unspecified memory interleave error. Probable Cause: FW encountered a fatal interleaving error. Recommended Action: Update SFW. Recommended Action: Contact HP support to troubleshoot the problem. WBEM EventID: 346. WBEM ProviderName: 22 WBEM Provider Event Tables

23 Event ID Event Severity Event Description Unexpected return to SAL_CHECK. Probable Cause: Unexpected return to SAL_CHECK. Recommended Action: Reboot if necessary, if problem persists contact your HP representative for support. WBEM EventID: 347. WBEM ProviderName: Unexpected return to SAL_INIT. Probable Cause: SAL_INIT has been unexpectedly returned to. Recommended Action: Reboot if necessary, if problem persists contact your HP representative for support. WBEM EventID: 348. WBEM ProviderName: Firmware is adding a DEGRADED cpu node to the device tree. Probable Cause: A CPU that is not fully functional is installed in the cell board. Recommended Action: Replace cpu indicated in data field of event. WBEM EventID: 349. WBEM ProviderName: PD rendezvous will fail do to a Firmware Tree error. Probable Cause: Decode the ASCII string in the data field to determine what resource is missing. Examine earlier chassis codes to determine why that resource is unavailable. WBEM EventID: 350. WBEM ProviderName: The current cell is not configured as part of the expected set. Probable Cause: A bad complex profile exists. Correct and redistribute. WBEM EventID: 351. WBEM ProviderName: A remote CSR could not be read. Probable Cause: Either a hardware connection problem exists, or fabric was unable to be routed. Verify hardware and reset. WBEM EventID: 352. WBEM ProviderName: The current cell is too late to rendezvous with other cells. Probable Cause: This cell took to long completing previous steps to rendezvous. A bad complex profile could also cause this problem. WBEM EventID: 353. WBEM ProviderName: The current cell detected incompatible CPUs on another cell. Probable Cause: Mixed CPU types are installed in the same partition. Remove them. WBEM EventID: 354. WBEM ProviderName: Current cell was too slow creating the local rendezvous set. Probable Cause: Cell too slow. Could be bad hardware. Check for other errors and reset. Recommended Action: If assistance is required, contact the HP Support Center. WBEM EventID: 355. WBEM ProviderName: Reporting cell was not included in the global cell set. Probable Cause: Fabric problem, Connection problem or timing problem. Reset the PD. WBEM EventID: 356. WBEM ProviderName: No Core Cell can be selected in the PD. Probable Cause: No cells have a functioning core IO card. Add a core IO card to a cell in the PD and reset. WBEM EventID: 357. WBEM ProviderName: Firmware was unable to notify utilities of the core cell number. Probable Cause: Communication with utilities is broken. Check for earlier errors or NVRAM problems. WBEM EventID: 358. WBEM ProviderName: Fabric code unable to find a needed service provider. Probable Cause: The registry is corrupt or the ROM is incomplete. WBEM EventID: 359. WBEM ProviderName: in a fabric Port. Probable Cause: Reset. WBEM EventID: 360. WBEM ProviderName: Parity error detected on read from fabric. Probable Cause: Hardware problem. Check connections and reset. WBEM EventID: 361. WBEM ProviderName: writing to Fabric. Probable Cause: Bad hardware. WBEM EventID: 362. WBEM ProviderName: Platform Events 23

24 Event ID Event Severity Event Description Crossbar slices are out of rev with each other. Probable Cause: Bad hardware configuration, different revisions of crossbars are installed. Recommended Action: Check crossbar revisions and ensure all installed crossbar revisions are the same. Replace the crossbar that is not in rev with the others. WBEM EventID: 363. WBEM ProviderName: Crossbar slices are configured poorly. Probable Cause: Fatal configuration. Reconfigure the hardware. WBEM EventID: 364. WBEM ProviderName: A CPU has taken over for the monarch CPU. Probable Cause: The previous monarch may be suspect. WBEM EventID: 365. WBEM ProviderName: Sram cannot be used on the cell. Probable Cause: SRAM cannot be located or used on the cell board. Replace the cell board. WBEM EventID: 366. WBEM ProviderName: The dillon hardware cannot be located. Probable Cause: ROM is corrupt. Replace the rom or reprogram flash. WBEM EventID: 367. WBEM ProviderName: A required piece of PDH bus hardware cannot be contacted. Probable Cause: Verify all connections of PDH bus components or replace the cell board. WBEM EventID: 368. WBEM ProviderName: : PCI Buses are configured for multiple speeds. Probable Cause: A PCI card is configured with mixed speeds. Recommended Action: Correct the configuration problem. WBEM EventID: WBEM ProviderName: The bus depth was exceeded during IO probing. Probable Cause: Too many PCI bridge cards are configured in single PCI segment mode. Recommended Action: Reconfigure PCI cards and remove some of the bridge devices. WBEM EventID: WBEM ProviderName: A Timeout occurred during RI initialization. The CSR is in the data field. The alert level will vary. Probable Cause: Hardware problem such as cable connect error or bad cables. Recommended Action: Correct the hardware problem and re-boot. WBEM EventID: WBEM ProviderName: SuperIO has been detected in slot. Probable Cause: SuperIO has been detected in the PCI slot. Recommended Action: No action required, information only. WBEM EventID: WBEM ProviderName: IO Link software error was corrected. Probable Cause: IO link error was detected and corrected. Recommended Action: No action required, information only. WBEM EventID: 372. WBEM ProviderName: Parity error in Reg FIFO Internal parity error. Probable Cause: Parity error in Reg FIFO. Recommended Action: Replace bad hardware. WBEM EventID: 374. WBEM ProviderName: TLB Fetch timeout. Probable Cause: SBA TLB fetch timeout error. Recommended Action: Replace faulty hardware. WBEM EventID: 375. WBEM ProviderName: Link presence goes away, FE. Probable Cause: Link presence lost on SBA interface. Recommended Action: Replace faulty hardware. WBEM EventID: 376. WBEM ProviderName: Elroy to REO parity error on command, rope will go fatal. Probable Cause: Bad hardware. Recommended Action: Replace I/O chassis. WBEM EventID: 377. WBEM ProviderName: Access to invalid TLB entry Requesting rope fatal. Probable Cause: An IO device is requesting access to an invalid TLB entry. Recommended Action: Driver problem - debug driver. WBEM EventID: 378. WBEM ProviderName: 24 WBEM Provider Event Tables

25 Event ID Event Severity Event Description Memory fetch timeout. Probable Cause: SBA memory fetch timeout error. Recommended Action: repair faulty hardware. WBEM EventID: 379. WBEM ProviderName: was encountered when Initializing the LBA. Probable Cause: LBA firmware initialization failed. Recommended Action: Review additional error logs to determine exact cause of failure. WBEM EventID: 380. WBEM ProviderName: LBA correctable Timeout was encountered. Probable Cause: An LBA correctable timeout error occurred. Recommended Action: No action necessary, the error was corrected. Information only. WBEM EventID: 381. WBEM ProviderName: LBA uncorrectable Function was encountered. Probable Cause: An LBA uncorrectable function error was encountered. Recommended Action: Replace/repair faulty hardware. WBEM EventID: 382. WBEM ProviderName: LBA uncorrectable Timeout was encountered. Probable Cause: LBA uncorrectable timeout error encountered. Recommended Action: Repair/replace faulty hardware. WBEM EventID: 383. WBEM ProviderName: Misc. uncorrectable error discovered on LBA. Probable Cause: LBA uncorrectable error encountered. Recommended Action: Repair/replace faulty hardware. WBEM EventID: 384. WBEM ProviderName: LBA encountered an uncorrectable parity error. Probable Cause: LBA encountered an uncorrectable parity error. Recommended Action: Repair/replace faulty hardware. WBEM EventID: 385. WBEM ProviderName: LBA Misc. Fatal encountered. Probable Cause: LBA fatal error encountered. Recommended Action: Repair/replace the faulty hardware. WBEM EventID: 386. WBEM ProviderName: LBA Fatal function error encountered. Probable Cause: An LBA fatal function error was encountered. Recommended Action: Repair/replace the faulty hardware. WBEM EventID: 387. WBEM ProviderName: LBA Fatal Parity error encountered. Probable Cause: An LBA fatal parity error encountered. Recommended Action: Repair/replace the faulty hardware. WBEM EventID: 388. WBEM ProviderName: LBA Fatal Timeout Encountered. Probable Cause: LBA fatal timeout error encountered. Recommended Action: Repair/replace the faulty hardware. WBEM EventID: 389. WBEM ProviderName: Misc Uncorrectable encountered. Probable Cause: A PCI card uncorrectable error was encountered. Recommended Action: Replace the faulty PCI card. WBEM EventID: WBEM ProviderName: Misc fatal error discovered on PCI card. Probable Cause: A fatal error was detected on a PCI card. Recommended Action: Repair/replace the faulty PCI card. WBEM EventID: WBEM ProviderName: DIMM SPD Extended Checksum Failure. Probable Cause: Replace any bad dimms. WBEM EventID: 392. WBEM ProviderName: The DIMM has been hardware deallocated. Probable Cause: Memory error occurred in main memory. Recommended Action: Replace all DIMMs as specified by physical location, followed by the Extended Memory Buffer (EMB). WBEM EventID: WBEM ProviderName: Options header checksum error encountered. Probable Cause: Reinitialize the options data. WBEM EventID: 393. WBEM ProviderName: Platform Events 25

26 Event ID Event Severity Event Description Options data checksum error was encountered. Probable Cause: Verify options data and reinitialize if necessary. WBEM EventID: 394. WBEM ProviderName: Internal inconsistency in the interleave tables. Probable Cause: Reconfigure and Reset. WBEM EventID: 395. WBEM ProviderName: CellInfoList is not NULL. Probable Cause: Reset. WBEM EventID: 396. WBEM ProviderName: in constructing the Memory Descriptor. Probable Cause: Reset. WBEM EventID: 397. WBEM ProviderName: Unable to update the local memory layout. Probable Cause: Reset. WBEM EventID: 398. WBEM ProviderName: A required address was not found within a mapped address. Probable Cause: Reset. WBEM EventID: 399. WBEM ProviderName: Failure to install a Partition level PDT. Probable Cause: Reset. WBEM EventID: 400. WBEM ProviderName: A critical resource could not be found or is unusable. Probable Cause: Determine the failing component or hardware from the data field as described and replace. WBEM EventID: 401. WBEM ProviderName: Internal firmware programming error. Probable Cause: Report the IP to the firmware team. Reset the system. This cannot be worked around in the field. WBEM EventID: 402. WBEM ProviderName: NVRam test failed with a data compare error. Probable Cause: Bad NVRam, replace the bad chip. WBEM EventID: WBEM ProviderName: An NVRam CRC was detected. Probable Cause: Firmware/software error. Recommended Action: Check for new version of firmware/os Contact HP Support. WBEM EventID: WBEM ProviderName: The Response Mode has been determined. Probable Cause: Decode the hex vales to ASCII to determine the mode. Other errors will determine action. WBEM EventID: WBEM ProviderName: A semaphore could not be obtained. Probable Cause: Semaphore error. Recommended Action: Reset system to clear the semaphore Try reinitializing NVRAM. If problem persists, contact engineering. WBEM EventID: 405. WBEM ProviderName: The BLOCK requested in NVRAM has the wrong revision. Probable Cause: Clear NVRAM and reset. WBEM EventID: WBEM ProviderName: The requested NVRAM block was not found. Probable Cause: No Action Required. Firmware can allocated space for the block. WBEM EventID: 407. WBEM ProviderName: The requested NVRAM block is locked. Probable Cause: Retry the operation. WBEM EventID: 408. WBEM ProviderName: Firmware tried to unlock a NVRAM block that was already unlocked. Probable Cause: No action required. WBEM EventID: 409. WBEM ProviderName: The Header in NVRAM was not found. Probable Cause: NVRAM cannot be used. It must be initialized first. Firmware will attempt the initialization. WBEM EventID: 410. WBEM ProviderName: The Freelist used for NVM block allocation is corrupt. Probable Cause: Bad NVRAM/ reinitialize. WBEM EventID: 411. WBEM ProviderName: 26 WBEM Provider Event Tables

27 Event ID Event Severity Event Description Firmware is preparing to reset for reconfiguration. Probable Cause: This can be caused by many conditions including a bad complex profile, a bad hardware configuration, a cell arriving late to the rendezvous point. A cell not being able to rendezvous. Reconfiguration from partition manager is recommended. WBEM EventID: 412. WBEM ProviderName: An error was encountered communicating with utilities during PD rendez. Probable Cause: Verify communications with the utilities system. WBEM EventID: 413. WBEM ProviderName: Forward Progress is stopping. The Cell or System will not boot further. Probable Cause: An error occurred which triggered system firmware to cease making forward progress. The CPU is put into a spin loop so that external debugging can take place. See earlier event ids to help determine the cause of the error. Also note that the Response Mode is likely to have directed firmware to HALT. WBEM EventID: 414. WBEM ProviderName: No console is available for the DUI to use. Probable Cause: DUI was entered before the console is available. DUI will exit and processing will continue. WBEM EventID: 415. WBEM ProviderName: Processing encountered an unrecoverable error. Probable Cause: Decode the ASCII message and correct the problem. WBEM EventID: 416. WBEM ProviderName: System is unable to complete the Reset For Reconfiguration request. Probable Cause: Delay the request for reconfiguration until after the PD has been released from Sinc BIB. WBEM EventID: 417. WBEM ProviderName: The cell is not able to reach all requested cells through the fabric. Probable Cause: Fabric wasn't able to route to all cells described in the complex profile correctly due to a hardware problem. Some of the cells are unreachable. Update the complex profile or correct the hardware problem. WBEM EventID: 418. WBEM ProviderName: LBA has unexpected number of I/O Slots. Probable Cause: Unsupported I/O configuration. Recommended Action: Remove the I/O cards below the specified PCI-to-PCI bridge. WBEM EventID: 419. WBEM ProviderName: Console device failed to connect. Probable Cause: Debugging event, not for release. WBEM EventID: 420. WBEM ProviderName: Copying memory test code failed. Probable Cause: Memory test code located in main memory has been corrupted. Recommended Action: Contact HP support personnel to troubleshoot the problem. WBEM EventID: 421. WBEM ProviderName: A remote cell is in an unknown state of PD rendezvous. Probable Cause: Reset the PD. WBEM EventID: WBEM ProviderName: Multiple Core Cells have been discovered in the same PD. Probable Cause: Verify that the complex profile is correct and reset the partition. WBEM EventID: 423. WBEM ProviderName: The utilities component encountered an error when sending a command to the MP. Probable Cause: Verify the utilities system is connected correctly and reset. WBEM EventID: 424. WBEM ProviderName: received after issuing the Retrieve Cell Slot State command. Probable Cause: Make sure the GSP is connected and reset. WBEM EventID: WBEM ProviderName: This indicates that all the cpus in the cell did not rendezvous during the MCA. Probable Cause: When this happens the cell will step through some of the error logging code on its own and then reset itself. WBEM EventID: 426. WBEM ProviderName: Platform Events 27

28 Event ID Event Severity Event Description This indicates that it does not have any access to the PD. Probable Cause: Forward Progress indicator; the cell will independently step through the error logging steps before it resets itself. WBEM EventID: 427. WBEM ProviderName: This indicates the loss of lockstep during the MCA path. Probable Cause: The cell will take up a few more error logging steps independently before resetting itself. WBEM EventID: 428. WBEM ProviderName: The PD level cell rendezvous failed. Probable Cause: This means that the cells will independently step through some of the error logging code and then reset themselves. WBEM EventID: 429. WBEM ProviderName: It stands for diagnosis of catastrophic errors in the PIN block of concorde. Probable Cause: This means that the cell will be reset. WBEM EventID: 557. WBEM ProviderName: The cell monarch cpu has failed. Probable Cause: The monarch cpu will be deconfigured. WBEM EventID: WBEM ProviderName: This indicates that the cell missed the rendezvous at the partition level. Probable Cause: The cell will independently step through some of the error logging steps and then finally reset itself. WBEM EventID: 559. WBEM ProviderName: This means that the PD monarch timedout. Probable Cause: The cell will be reset ; also the partition will be reset. WBEM EventID: 560. WBEM ProviderName: SetViewRoot on a remote cell failed. Probable Cause: Inter Processor interrupts failed. Be sure that the partition rendezvous was successfully completed. Reset. WBEM EventID: WBEM ProviderName: Failed to update CSR contents. Probable Cause: Coherency controller on cell sending event is suspect. Recommended Action: Provide event data to HP support center for assistance. WBEM EventID: WBEM ProviderName: This indicates the failure in collecting the Complex profile info. Probable Cause: The partition level memory interleaving cannot continue without the appropriate information. WBEM EventID: 563. WBEM ProviderName: This chassis code indicates the failure in collecting the cell info. Probable Cause: The partition level memory will fail. WBEM EventID: 564. WBEM ProviderName: This indicates the failure in updating the GNI info of the cell with CLM. Probable Cause: The partition level memory will fail at this point. WBEM EventID: 565. WBEM ProviderName: This indicates the failure in adjusting the mem info with Minimum ZI req. Probable Cause: This will cause the partition level memory to exit cell interleaving. WBEM EventID: 566. WBEM ProviderName: Complex Profile A has a checksum error. Probable Cause: Reconfigure the system get a new complex profile distributed and reset. WBEM EventID: WBEM ProviderName: A Checksum error was encountered in the dynamic profile. Probable Cause: Push out a new complex profile and reset. WBEM EventID: WBEM ProviderName: A checksum error occurred on the Partition Profile. Probable Cause: Push out a new complex profile and reboot. WBEM EventID: WBEM ProviderName: The Stable Complex Profile Sequence Id is invalid. Probable Cause: Push out a new complex profile and reset the system. The cell will be waiting for reconfiguration. WBEM EventID: WBEM ProviderName: 28 WBEM Provider Event Tables

29 Event ID Event Severity Event Description The Dynamic Complex Profile Sequence ID is invalid. Probable Cause: Push out a new complex profile. WBEM EventID: WBEM ProviderName: The Partition Profile Sequence ID is invalid. Probable Cause: Push out a new complex profile and reset. The cell will be waiting for reconfiguration. WBEM EventID: WBEM ProviderName: Internal Firmware Programming from the EFI portion of the firmware. Probable Cause: Internal system firmware error. Recommended Action: Verify the latest supported firmware is installed on the system. WBEM EventID: 570. WBEM ProviderName: The PD numbers in Group A and Group C of the complex profile are inconsistent. Probable Cause: Push out consistent Complex profiles and reset the system. The cell will be waiting for reconfiguration. WBEM EventID: WBEM ProviderName: The PD number specified in the complex profile is out of range. Probable Cause: Reconfigure the partition number, push out a new profile and reset. WBEM EventID: WBEM ProviderName: Could not obtain the crossbar port semaphore. Probable Cause: No action required. WBEM EventID: 573. WBEM ProviderName: Could not release the crossbar port semaphore. Probable Cause: No action required. WBEM EventID: 574. WBEM ProviderName: BMC token upload failure. Probable Cause: Problem accessing the BMC. Recommended Action: AC power cycle or update BMC and System FW. If problem persists contact your HP representative for support. WBEM EventID: 576. WBEM ProviderName: NVM token access failure. Probable Cause: NVM, or incorrect permissions to read token. Recommended Action: Retry, AC power cycle if necessary, if problem persists contact your HP representative for support. WBEM EventID: 577. WBEM ProviderName: BMC token download failure. Probable Cause: Problem accessing the BMC. Recommended Action: AC power cycle or update BMC and System FW. If problem persists contact your HP representative for support. WBEM EventID: 578. WBEM ProviderName: Writing BMC first boot token. Probable Cause: Problem accessing the BMC. Recommended Action: AC power cycle or upgrade BMC and System FW. If problem persists contact your HP representative for support. WBEM EventID: 579. WBEM ProviderName: Fru Id read error. Probable Cause: reading a FRU. Recommended Action: Reboot if necessary, if problem persists contact your HP representative for support. WBEM EventID: 580. WBEM ProviderName: Fru Id checksum error. Probable Cause: reading the a FRU. Recommended Action: Reboot if necessary, if problem persists contact your HP representative for support. WBEM EventID: 581. WBEM ProviderName: Fru Id version error. Probable Cause: reading a FRU. Recommended Action: Reboot if necessary, if problem persists contact your HP representative for support. WBEM EventID: 582. WBEM ProviderName: Rom revision not equal to FIT revision. Probable Cause: A ROM Rev and FIT Rev do not match. Recommended Action: Update SFW, if problem persists contact your HP representative for support. WBEM EventID: 583. WBEM ProviderName: Platform Events 29

30 Event ID Event Severity Event Description ROM revision not equal to Rev block. Probable Cause: A ROM Rev and Rev Block do not match. Recommended Action: Update SFW, if problem persists contact your HP representative for support. WBEM EventID: 584. WBEM ProviderName: Primary Fit bad. Probable Cause: The FIT is bad. Recommended Action: Reboot, update SFW if necessary, if problem persists contact your HP representative for support. WBEM EventID: 585. WBEM ProviderName: Secondary Fit bad. Probable Cause: The FIT is bad. Recommended Action: Reboot, update SFW if necessary, if problem persists contact your HP representative for support. WBEM EventID: 586. WBEM ProviderName: PAL A execution rom warning. Probable Cause: PAL_A_ROM has generated a warning. Recommended Action: Reboot, update SFW if necessary, if problem persists contact your HP representative for support. WBEM EventID: 587. WBEM ProviderName: PAL B execution rom warning. Probable Cause: PAL_B_ROM has generated a warning. Recommended Action: Reboot, update SFW if necessary, if problem persists contact your HP representative for support. WBEM EventID: 588. WBEM ProviderName: An error was encountered when firmware tried to update the Group B Profile. Probable Cause: Utilities may be unavailable to update the profiles. Check the connections are reset. WBEM EventID: WBEM ProviderName: PCI parity error detected. Probable Cause: I/O host bridge failure. Recommended Action: Contact your HP representative to check the I/O host bridge. WBEM EventID: 430. WBEM ProviderName: PCI system error detected. Probable Cause: I/O device failure. Recommended Action: Consult the error logs for additional information. Determine and replace the failed I/O device. WBEM EventID: 431. WBEM ProviderName: I/O host bridge is deconfigured. Probable Cause: See earlier error event. Recommended Action: See earlier error event. WBEM EventID: 432. WBEM ProviderName: Firmware was unable to publish the Partition Profile. Probable Cause: Utilities may be unavailable to update the profiles. Check the connections are reset. WBEM EventID: WBEM ProviderName: The reporting cell is not configured to be in a PD. Probable Cause: Run parmgr to configure the cell into a PD and reset the PD or add the cell. WBEM EventID: 434. WBEM ProviderName: DIMM thermal loading order warning. Probable Cause: The current DIMM loading order does not follow the guidelines in the user manual. Recommended Action: Rearrange the DIMMs to follow the loading order specified in the Maintenance and Operation Manual. WBEM EventID: 435. WBEM ProviderName: The PD cannot boot, a majority of cells did not arrive at Rendezvous. Probable Cause: PD Rendezvous Boot Rules: If greater than 50% of the assigned cells are rendezvoused, we will boot. If less than 50% of the assigned cells are rendezvoused, don't boot. If exactly 50% of the assigned cells are rendezvoused, including all of the preferred core cells, we will boot. If exactly 50% have rendezvoused, and there is a specified preferred core cell not rendezvoused, don't boot. If exactly 50% have rendezvoused, and there are no preferred core cells, don't boot. If any of the above apply in preventing the boot. Reconfigure the PD and reboot. WBEM EventID: 437. WBEM ProviderName: 30 WBEM Provider Event Tables

31 Event ID Event Severity Event Description INIT: Monarch failed in slave rendezvous. Probable Cause: A processor has failed rendezvous. Recommended Action: Reboot if necessary, if problem persists contact your HP representative for support. WBEM EventID: 439. WBEM ProviderName: MC: I/O error log/clear error. Probable Cause: SFW's Machine Check Handler was unable to log or clear I/O error registers. Recommended Action: Reboot if necessary, if problem persists contact your HP representative for support. WBEM EventID: 440. WBEM ProviderName: MC: MCA to BERR escalation not supported by PAL. Probable Cause: Cannot escalate an MCA to BERR. Recommended Action: Analyze Machine Check Logs using diagnostic tools and EFI tools. WBEM EventID: 441. WBEM ProviderName: MC: MCA to BINIT escalation not supported by PAL. Probable Cause: Cannot escalate an MCA to BINIT. Recommended Action: Analyze Machine Check Logs using diagnostic tools and EFI tools. WBEM EventID: 442. WBEM ProviderName: MC: Get PAL features failed. Probable Cause: SFW failed to get the feature set from PAL. Recommended Action: Update firmware to get newer PAL that support the PAL_GET_FEATUREs call. WBEM EventID: 443. WBEM ProviderName: MC: Previous PAL rendezvous failed; rebooting. Probable Cause: PAL Failed to rendezvous the processors during a MCA. Recommended Action: Review error logs to determine cause of MCA. If problem persists, contact HP support to troubleshoot the problem. WBEM EventID: 444. WBEM ProviderName: MC: Set PAL features failed. Probable Cause: SFW failed to set the feature set from PAL. Recommended Action: update newer system firmware with the new PAL that support the PAL_SET_FEATURES call. WBEM EventID: 445. WBEM ProviderName: MC: Monarch failed in slave rendezvous. Probable Cause: A slave failed to rendezvous. Recommended Action: Reboot if necessary, if problem persists contact your HP representative for support. WBEM EventID: 446. WBEM ProviderName: MC_RENDEZVOUS: Rendezvous vector out of range. Probable Cause: A bad rendezvous vector has been registered. Recommended Action: Reboot if necessary to re-register vector, if problem persists contact your HP representative for support. WBEM EventID: 447. WBEM ProviderName: MC_RENDEZVOUS: No MC monarch. Probable Cause: Software is making a SAL_MC_RENDEZVOUS call when it shouldn't. Recommended Action: Just a warning that software or OS is making a call when it shouldn't. SFW will ignore the call when this happen. Need to fix OS or software to not make the SAL_MC_RENDEZVOUS when there is no monarch processor chosen. WBEM EventID: 448. WBEM ProviderName: MC_RENDEZVOUS: No wakeup registered. Probable Cause: OS or Software is calling SAL_MC_RENDEZ without registering a method to wake-up the processor. Recommended Action: OS or Software needs to be fixed to register a wake-up mechanism before calling SAL_MC_RENDEZ. WBEM EventID: 449. WBEM ProviderName: MC_RENDEZVOUS: MCA escalation not supported by PAL. Probable Cause: PAL does not support the call to escalate further local MCA to global MCA. Recommended Action: Update SFW with contain a new PAL that support this feature. If no new PAL that support this feature, no action should be taken further. WBEM EventID: 450. WBEM ProviderName: Platform Events 31

32 Event ID Event Severity Event Description MC_RENDEZVOUS: Get PAL features failed. Probable Cause: PAL does not support call to get the processor feature set during processor rendezvous. Recommended Action: Update system firmware with a new PAL that support the PAL_GET_FEATURES call. WBEM EventID: 451. WBEM ProviderName: MC_RENDEZVOUS: Set PAL features failed. Probable Cause: PAL does not support call to set the processor feature set during processor rendezvous. Recommended Action: update system firmware with new PAL that support the PAL_SET_FEATURE call. WBEM EventID: 452. WBEM ProviderName: Internal Firmware Programming from the EFI portion of the firmware. Probable Cause: Report the IP to the firmware team. Reset the system. This cannot be worked around in the field. WBEM EventID: 453. WBEM ProviderName: memory extender loading order error. Probable Cause: The memory extenders have not been loaded in the correct order. Recommended Action: Load the Memory extenders according to the users manual. WBEM EventID: 454. WBEM ProviderName: Inconsistency in the length of the ESI table. Probable Cause: Table entries corrupted. Recommended Action: Reboot. If problem persists contact your HP representative for support. WBEM EventID: 455. WBEM ProviderName: The computed checksum for ESI Table incorrect. Probable Cause: Table corrupted. Recommended Action: Reboot. If problem persists contact your HP representative for support. WBEM EventID: 456. WBEM ProviderName: ESI Table contains an unsupported entry type. Probable Cause: Corrupted table. Recommended Action: Reboot system. If problem persists, contact HP support to troubleshoot the problem. WBEM EventID: 457. WBEM ProviderName: A GUID was larger than the expected 128 bits. Probable Cause: Inconsistency in EFI firmware. Recommended Action: Upgrade system firmware. If problem persists, contact HP support to troubleshoot the problem. WBEM EventID: 458. WBEM ProviderName: EFI is halting. Probable Cause: Unknown. Recommended Action: examine preceding events for problem. WBEM EventID: 459. WBEM ProviderName: chipspare not supported on quad. Probable Cause: User installed a x8 DIMM in a system configured for chipspare. Recommended Action: If user requires Chipspare, replace the DIMM with a x4 DIMM. If Chipspare is not required, then no action is required. WBEM EventID: 460. WBEM ProviderName: EFI internal error detected resulting in execution of ASSERT macro. Probable Cause: The cause is unknown. Recommended Action: Look at previous events and ASCII information in this event for more information. If problem persists, contact HP support to troubleshoot the problem. WBEM EventID: 461. WBEM ProviderName: EFI has executed the 'break' shell command. Probable Cause: Executing the 'break' command. Recommended Action: Check for user entering 'break' command. Check for shell scripts using the 'break' command. WBEM EventID: 462. WBEM ProviderName: EFI USB HCD interrupt service has detected the host controller is hung. Probable Cause: Problem with USB controller. Recommended Action: Reset the card containing the USB interface to restart the controller. Contact your HP representative to check the USB interface. WBEM EventID: 463. WBEM ProviderName: 32 WBEM Provider Event Tables

33 Event ID Event Severity Event Description The EFI/SAL handoff structure's version does not match EFI expectations. Probable Cause: EFI/SAL firmware mismatch. Recommended Action: Reboot. If problem persists contact your HP representative for support. WBEM EventID: 464. WBEM ProviderName: Unable to obtain access to all RTC SAL services. Probable Cause: EFI unable to create internal event. EFI out of resources. Recommended Action: Reboot. If problem persists contact your HP representative for support. WBEM EventID: 465. WBEM ProviderName: Unable to obtain access to all SAL timer services. Probable Cause: Not all expected services are available. Mismatch between EFI and SAL versions. Internal EFI error. Recommended Action: Reboot. If problem persists contact your HP representative for support. WBEM EventID: 466. WBEM ProviderName: EFI unable to start the periodic timer. Probable Cause: Internal system firmware error. Recommended Action: Reboot. If problem persists contact your HP representative for support. WBEM EventID: 467. WBEM ProviderName: No I/O port space region found in the MDT. Probable Cause: EFI/SAL mismatch. Recommended Action: Reboot. If problem persists contact your HP representative for support. WBEM EventID: 468. WBEM ProviderName: EFI reached an unimplemented section of code. Probable Cause: Reached unimplemented firmware. Recommended Action: Upgrade system firmware. WBEM EventID: 469. WBEM ProviderName: EFI unable to read current speedy boot settings. Probable Cause: BMC not functioning properly. Recommended Action: Reset the BMC. Contact your HP representative to check the BMC. WBEM EventID: 470. WBEM ProviderName: Unpermitted SAL callback attempted. Probable Cause: Internal EFI error. Recommended Action: Reboot. If problem persists contact your HP representative for support. WBEM EventID: 471. WBEM ProviderName: EFI unable to determine frequency base of the CPU interval timer. Probable Cause: Internal system firmware error. Recommended Action: Upgrade system firmware. WBEM EventID: 472. WBEM ProviderName: EFI system events already initialized. Probable Cause: Multiple attempts to initialize system events, EFI internal error. Recommended Action: Upgrade system firmware. If problem persists, contact HP support to troubleshoot the problem. WBEM EventID: 473. WBEM ProviderName: Unable to create internal virtualization event while initializing IPMI events. Probable Cause: Out of resources. Internal EFI error. Recommended Action: Reboot system. Upgrade system firmware. WBEM EventID: 474. WBEM ProviderName: There was an error creating or initializing the FPGA node in firmware. Probable Cause: Unable to properly initialize a system firmware node. Recommended Action: Check for other errors in the system first. Invalidate NVM and retry to boot. Get the latest firmware release. WBEM EventID: 476. WBEM ProviderName: creating the pdh ioconfig node or attaching the service to it. Probable Cause: This is likely to be a symptom of an earlier problem, or the system is out of malloc space. Recommended Action: Contact system firmware team. WBEM EventID: WBEM ProviderName: encountered setting up the dillon_pdh node or service. Probable Cause: This is usually a symptom of an earlier problem. Check to be sure the pdh node was initialized into the tree correctly. WBEM EventID: WBEM ProviderName: Platform Events 33

34 Event ID Event Severity Event Description The PDH component encountered an error dealing with a property on a node. Probable Cause: This is usually due to a memory allocation problem. Verify that sram is usable and there is memory available. WBEM EventID: WBEM ProviderName: creating the acpi_hw node. Probable Cause: May be out of malloc space or a previous tree error prevented this from being successful. Check for earlier errors. WBEM EventID: WBEM ProviderName: encountered creating or initializing the ipmi node. Probable Cause: Possibly out of memory or an earlier error left the tree in an unusable state. WBEM EventID: WBEM ProviderName: some processors not compatible. Probable Cause: Installed processors are not of compatible models or families. Recommended Action: Replace processors with compatible ones if all processors are to be used. WBEM EventID: 481. WBEM ProviderName: caches sizes are inconsistent. Probable Cause: Processors with different cache sizes are installed in the system. Recommended Action: Replace processors with compatible ones if all processors are to be used. WBEM EventID: 482. WBEM ProviderName: selecting new monarch. Probable Cause: The monarch processor was not the lowest stepping processor installed within the cell. Recommended Action: No action is required. FW takes action automatically. To avoid this event, be sure that the monarch processor is the lowest stepping of processor in the system. WBEM EventID: 484. WBEM ProviderName: monarch not lowest stepping. Probable Cause: The monarch processor has a stepping that is greater than a slave processor installed in the system. Recommended Action: No action is needed. If problem persists, update System FW or contact your HP representative for support. WBEM EventID: 485. WBEM ProviderName: processors are over clocked. Probable Cause: FSB speed faster than the capabilities of the processors. Recommended Action: If multiple CPU's report this issue, check the BMC. If only one reports this issue, replace the CPU. If problem persists, contact HP support. WBEM EventID: 487. WBEM ProviderName: cpu access error on processor info area. Probable Cause: An early version of CPU or a bad info ROM. Recommended Action: Reboot. If problem persists contact your HP representative for support. WBEM EventID: 488. WBEM ProviderName: PAL A was not executed - HALT. Probable Cause: PAL_A has not been executed. Recommended Action: Contact your HP representative for support. WBEM EventID: 489. WBEM ProviderName: PAL B was not executed - HALT. Probable Cause: PAL_B has not been executed. Recommended Action: Contact your HP representative for support. WBEM EventID: 490. WBEM ProviderName: Prototype CPU installed. Probable Cause: A Prototype CPU is installed. Recommended Action: Replace CPU with a production CPU. WBEM EventID: 491. WBEM ProviderName: final boot rendezvous monarch watchdog timeout. Probable Cause: A watchdog timer has expired and determined that a monarch is dead. Recommended Action: Reboot, if problem persists, replace CPU. WBEM EventID: 492. WBEM ProviderName: Supplemental cpu tests generated an unexpected result. Probable Cause: A CPU failed supplemental selftests. Replace the offending CPU. WBEM EventID: WBEM ProviderName: 34 WBEM Provider Event Tables

35 Event ID Event Severity Event Description A multi-bit error was found while reading a XBC CSR. Probable Cause: Possibly bad link or cell connection. Recommended Action: Reset partition, and check hardware associated with event data. WBEM EventID: 493. WBEM ProviderName: The return value from a function was an unknown value. Probable Cause: Firmware error. Recommended Action: Reset cell. WBEM EventID: 494. WBEM ProviderName: Cannot get system ID status from BMC. Probable Cause: The communication with the system ID is lost. Recommended Action: Reset the BMC using the 'rb' command from the MP. If this doesn't work (or no MP available), unplug power from the system for 10 seconds and try rebooting the system. WBEM EventID: 495. WBEM ProviderName: Cannot read a system ID. Probable Cause: BMC failure. Recommended Action: Unplug power from the system for 10 seconds and try rebooting the system. WBEM EventID: 496. WBEM ProviderName: Failed to write new system ID. BMC reported an error. Probable Cause: Communication failure with the BMC. Recommended Action: Unplug power from the system for 10 seconds and try rebooting the system. WBEM EventID: 497. WBEM ProviderName: The system ID(s) currently in the system is invalid. Probable Cause: The system ID(s) is invalid and the user did not elect to fix the problem. Recommended Action: Reboot the system and follow the prompts to fix the issue. WBEM EventID: 498. WBEM ProviderName: EFI unable to find the SAL services for installing interrupt handlers. Probable Cause: Mismatch between EFI and SAL. Recommended Action: Upgrade system firmware. WBEM EventID: 499. WBEM ProviderName: EFI unable to find the SAL service to install run-time interrupt handlers. Probable Cause: Mismatch between EFI and SAL. Recommended Action: Upgrade system firmware. WBEM EventID: 500. WBEM ProviderName: EFI unable to find the SAL services for installing interrupt handlers. Probable Cause: Mismatch between EFI and SAL portions of the system firmware. Recommended Action: Reboot, if problem persists, contact your HP representative for support. WBEM EventID: 501. WBEM ProviderName: EFI unable to find the SAL service to install boot-time interrupt handlers. Probable Cause: Mismatch between EFI and SAL. Recommended Action: Reboot or upgrade system firmware. If problem persists contact your HP representative for support. WBEM EventID: 502. WBEM ProviderName: Too many parameters were passed to the utilities system. Probable Cause: This is a firmware error. Contact FW engineering. WBEM EventID: WBEM ProviderName: A crossbar port is unexpectedly not present. Probable Cause: An XBC is indicating a port failure. Recommended Action: Validate all of the cells connectivity to the PD Check the XBC chips seating reset the system replace either cells/system backplane. WBEM EventID: 504. WBEM ProviderName: A crossbar port unexpectedly has its HW_LINK_OK bit not set. Probable Cause: An XBC is indicating a port failure. Recommended Action: Validate all of the cells connectivity to the PD. Check the XBC chips seating. Reset the system. Replace either cells/system backplane. WBEM EventID: 505. WBEM ProviderName: A connected port was found to be in FE. Probable Cause: An XBC is indicating a port failure. Recommended Action: Validate all of the cells connectivity to the PD. Check the XBC chips seating reset the system replace either cells/system backplane. WBEM EventID: 506. WBEM ProviderName: Platform Events 35

36 Event ID Event Severity Event Description There was an error while initializing the Concorde-Xbc interface. Probable Cause: An XBC is indicating a port failure. Recommended Action: Validate all of the cells connectivity to the PD. Check the XBC chips seating reset the system replace either cells/system backplane. WBEM EventID: 507. WBEM ProviderName: The CC - XBC link failed to initialize. Probable Cause: An XBC is indicating a port failure. Recommended Action: Validate all of the cells connectivity to the PDCheck the XBC chips seating reset the system replace either cells/system backplane. WBEM EventID: 508. WBEM ProviderName: Unable to determine system mode because EFI/SAL interface not initialized. Probable Cause: Internal EFI error. Recommended Action: Upgrade system firmware. If problem persists, contact HP support to troubleshoot the problem. WBEM EventID: 509. WBEM ProviderName: BMC returned an invalid system mode. Probable Cause: Mismatch between BMC and EFI firmware. Recommended Action: Upgrade system firmware or BMC firmware as necessary. If problem persists, contact HP support to troubleshoot the problem. WBEM EventID: 510. WBEM ProviderName: EFI unable to specify system mode because EFI/SAL interface not initialized. Probable Cause: Internal EFI error. Recommended Action: Upgrade system firmware. If problem persists, contact HP support to troubleshoot the problem. WBEM EventID: 511. WBEM ProviderName: Unable to enter normal system mode because EFI/SAL interface not initialized. Probable Cause: Internal EFI error. Recommended Action: Upgrade system firmware. If problem persists, contact HP support to troubleshoot the problem. WBEM EventID: 512. WBEM ProviderName: Unable to initialize part of the SAL/EFI interface. Probable Cause: Incompatible versions of EFI and SAL, Internal EFI error. Recommended Action: Reboot. If problem persists contact your HP representative for support. WBEM EventID: 513. WBEM ProviderName: An expected tree node was not found. Probable Cause: This is a bug. Contact engineering. WBEM EventID: 515. WBEM ProviderName: EFI unable to modify system state to 'running'. Probable Cause: BMC malfunctioning. Recommended Action: Reset BMC. WBEM EventID: 516. WBEM ProviderName: /options settings for CPUBusConfigValue aren't compatible with PAL. Probable Cause: Update the /options value to comply with the desired features and what is supported. WBEM EventID: WBEM ProviderName: The Get Processor Bus Dependent Configuration Features PAL call failed. Probable Cause: Contact engineering. There is a PAL compatibility problem. WBEM EventID: 518. WBEM ProviderName: memory DIMM pair mismatch. Probable Cause: The user installed a mismatched pair of DIMMs in the same rank (i.e. the DIMMs are different size or DRAM width). Recommended Action: Install memory ranks in pairs of DIMMs that are the same size and DRAM width. WBEM EventID: 519. WBEM ProviderName: EFI unable to initialize internal library. Probable Cause: Internal EFI error. Recommended Action: Reboot. If problem persists contact your HP representative for support. WBEM EventID: 520. WBEM ProviderName: EFI unable to initialize security system. Probable Cause: BMC not responding properly. Recommended Action: Reset BMC. Contact your HP representative if problem persists. WBEM EventID: 521. WBEM ProviderName: 36 WBEM Provider Event Tables

37 Event ID Event Severity Event Description EFI detected invalid internal privilege level. Probable Cause: Invalid argument with EFI. Recommended Action: Upgrade system firmware. If problem persists, contact HP support to troubleshoot the problem. WBEM EventID: 522. WBEM ProviderName: EFI detected invalid privilege level when setting password. Probable Cause: Internal EFI error. Recommended Action: Upgrade system firmware. If problem persists, contact HP support to troubleshoot the problem. WBEM EventID: 523. WBEM ProviderName: EFI MDT table is bad. Probable Cause: SFW has determined that the MDT table is invalid. Recommended Action: Reboot or update System FW. If problem persists contact your HP representative for support. WBEM EventID: 524. WBEM ProviderName: Processor has incompatible fixed core ratio. Probable Cause: A CPU has a fixed ratio that is incompatible with the FSB frequency set in the chipset. Recommended Action: Contact your HP representative for support. WBEM EventID: 525. WBEM ProviderName: All processors slated for compatibility deconfiguration. Probable Cause: The user or SFW has set all CPUs to be deconfigured. Recommended Action: Look for events indicating incompatible or bad CPUs and replace them. If problem persists contact your HP representative for support. WBEM EventID: 526. WBEM ProviderName: An unexpected or invalid value was read from a crossbar remote route table. Probable Cause: An XBC is indicating a port failure. Recommended Action: Validate all of the cells connectivity to the PDCheck the XBC chips seating reset the system replace either cells/system backplane. WBEM EventID: 527. WBEM ProviderName: reading the PORT[n]_NEIGHBOR_INFO XBC CSR. Probable Cause: Possible bad link, crossbar, or cell connection. Recommended Action: Check crossbar and link specified in the event data. Reset cell. WBEM EventID: 528. WBEM ProviderName: memory DIMM quad mis-match. Probable Cause: The user installed a mismatched quad of DIMMs in the same rank (i.e. the DIMMs are different size or DRAM width). Recommended Action: Install memory ranks in quads of DIMMs that are the same size and DRAM width. WBEM EventID: 529. WBEM ProviderName: Firmware detected excessive errors on the DIMM. Probable Cause: Firmware detected excessive errors on the DIMM / Replace the specified DIMM. WBEM EventID: 530. WBEM ProviderName: The OE (output enable) bit was not set for a XBC port. Probable Cause: Possible firmware or link error. Recommended Action: Check XBC and port specified by event data. WBEM EventID: 531. WBEM ProviderName: An error occurred while trying to read the PORT_STATUS CSR for a XBC port. Probable Cause: Possible bad connection between cell and backplane. Recommended Action: Check for hardware errors. Reset cell. WBEM EventID: 532. WBEM ProviderName: A XBC port was unexpectedly found to be landmined. Probable Cause: No action required. WBEM EventID: 533. WBEM ProviderName: CPUs running at different speeds were detected during rendezvous. Probable Cause: Reconfigure the PD so that all cells have processors running at the same speed. WBEM EventID: WBEM ProviderName: Platform Events 37

38 Event ID Event Severity Event Description The link between the local CC and the local XBC is unexpectedly not initialized. Probable Cause: An error initializing fabric. Recommended Action: A previously reported event may provide exact detailsreboot, if failure persists, then either replace the CC chip or the system backplane. WBEM EventID: 535. WBEM ProviderName: An invalid XBC number was given. Probable Cause: Firmware error. Recommended Action: Reset cell. WBEM EventID: 536. WBEM ProviderName: An invalid XBC port number was given. Probable Cause: Firmware error. Recommended Action: Reset cell. WBEM EventID: 537. WBEM ProviderName: A bad parameter was passed to the LED function in the utilities component. Probable Cause: Contact FW engineering. This is a bug. WBEM EventID: WBEM ProviderName: An unexpected neighbor type was read from a XBC PORT_NEIGHBOR_INFO CSR. Probable Cause: Bad connection between XBC and cell. Recommended Action: Reset cell. WBEM EventID: 539. WBEM ProviderName: A given XBC port is not a valid XBC-CC port. Probable Cause: Firmware error. Recommended Action: Reset cell. WBEM EventID: 540. WBEM ProviderName: A XBC port was unexpectedly found to be an invalid XBC-XBC port. Probable Cause: Firmware error. Recommended Action: Reset cell. WBEM EventID: 541. WBEM ProviderName: The XBC neighbor chip number does not match the expected value for this topology. Probable Cause: Bad connection between XBC and cell. Recommended Action: Reset cell. WBEM EventID: 542. WBEM ProviderName: The XBC neighbor port number does not match the expected value for this topology. Probable Cause: Bad connection between XBC and cell. Recommended Action: Reset cell. WBEM EventID: 543. WBEM ProviderName: Write through to BMC token failed. Probable Cause: Problem accessing the BMC. Recommended Action: Reset BMC or reboot. Upgrade BMC FW and System FW. If problem persists, contact your HP representative for support. WBEM EventID: 544. WBEM ProviderName: Utilities reported an error while trying to manipulate the LED. Probable Cause: It is likely the GSP is not present or the device specified is not present. Solve these problems and try again. WBEM EventID: WBEM ProviderName: Duplicate Cpu Ids were detected within a cell. Probable Cause: Most likely cause is a bad CPU module connection on the cell board. Replace the cell board. Recommended Action: Replace the cell board. WBEM EventID: 546. WBEM ProviderName: OS crashdump started (D700). Probable Cause: panic occurred. WBEM EventID: 547. WBEM ProviderName: OS legacy PA hex fault code (Bxxx). Probable Cause: fault/panic. WBEM EventID: 548. WBEM ProviderName: Setting processor response timeout failed. Probable Cause: A PAL call made by SFW has failed. Recommended Action: Reboot if necessary, if problem persists contact your HP representative for support. WBEM EventID: 550. WBEM ProviderName: 38 WBEM Provider Event Tables

39 Event ID Event Severity Event Description Unable to validate blank password during EFI security initialization. Probable Cause: BMC failed. Recommended Action: Reset the BMC. Update BMC FW. Contact your HP representative to check the BMC. WBEM EventID: 551. WBEM ProviderName: Unable to enter Guest mode during EFI security initialization. Probable Cause: BMC failure. Recommended Action: Reset the BMC. Update BMC FW. Contact your HP representative to check the BMC. WBEM EventID: 552. WBEM ProviderName: Unable to increase privilege during EFI security initialization. Probable Cause: BMC failure. Recommended Action: Reset the BMC. Update BMC FW. Contact your HP representative concerning the BMC. WBEM EventID: 553. WBEM ProviderName: EFI unable to write privilege level during security initialization. Probable Cause: SAL failure. Recommended Action: Reboot the system. Update SFW. If problem persists, contact HP support to troubleshoot the problem. WBEM EventID: 554. WBEM ProviderName: EFI was denied permission to write the privilege level during security init. Probable Cause: SAL is not in ADMIN or USER mode. Recommended Action: Reboot the system. Upgrade system firmware. If problem persists, contact HP support to troubleshoot the problem. WBEM EventID: 555. WBEM ProviderName: OS dump, error writing image area to disk (E055). Probable Cause: panic path forward progress. WBEM EventID: 556. WBEM ProviderName: Coherency controller (CC) registers indicate a Deadlock Recovery Reset. Probable Cause: Coherency controller (CC) resources are deadlocked and the CC is resetting the cell. Recommended Action: Analyze the Deadlock Recovery logs (like MCA logs) to determine the cause of the failure. WBEM EventID: WBEM ProviderName: A memory address parity error has been detected. The physical location can be located in the data field. Probable Cause: Poorly seated memory extender. Recommended Action: Reseat memory extender. WBEM EventID: WBEM ProviderName: A DIMM loading order error has occurred. Probable Cause: Incorrect loading of the DIMMs on the cell. Recommended Action: Install the DIMMs in the correct order. DIMMs are installed in ranks of DIMMs, starting with DIMM 0A, 0B, etc. Subsequent ranks are loaded in ascending order, i.e., rank 1, 2, 3, 4, 5, 6 and 7. WBEM EventID: 590. WBEM ProviderName: Refresh Control Timeout. Probable Cause: At start of memory refresh, timing out waiting for ready bit to be set. Recommended Action: Contact HP Support personnel to troubleshoot the problem. WBEM EventID: 591. WBEM ProviderName: memory extender/baseboard FRU mismatch. Probable Cause: Memory extender and baseboard are incompatible. Recommended Action: Contact HP support to troubleshoot the problem. WBEM EventID: 592. WBEM ProviderName: Fabric topology mismatch with XBCs in complex. Probable Cause: There is a fabric topology mismatch with XBC in complex. Recommended Action: Contact HP Support personnel to analyze the cell, XBC flex cables, system backplane. WBEM EventID: 593. WBEM ProviderName: An invalid XBC to XBC port was found. Probable Cause: Loss of Lockstep. Recommended Action: Reset. WBEM EventID: 594. WBEM ProviderName: Platform Events 39

40 Table #2 Event ID numbers 7,000 through 15,738 Event ID Event Severity Event Description Could not get neighbor information. Probable Cause: Defective XBC link Defective XBC. Recommended Action: Check XBC link connections Reset the system backplane Contact HP Support personnel to troubleshoot problem. WBEM EventID: 595. WBEM ProviderName: The XBC's routing state was marked as in ERROR. Probable Cause: Another cell already attempted routing for the XBC and found an error. Recommended Action: Check for hardware failure: flex cables, crossbar chip, etc. WBEM EventID: 596. WBEM ProviderName: It indicates that there is no NVM error space left for logging an Event. Probable Cause: The error event will not be logged. WBEM EventID: 597. WBEM ProviderName: An XBC port found to have an unexpected error. Probable Cause: A port was landmined so it had to be routed around. Recommended Action: Check flex cables. WBEM EventID: 598. WBEM ProviderName: A XBC port route around has occurred. Probable Cause: During routing, when a XBC to XBC port is found to be in error, or was previously marked in error, it is routed around. This chassis code indicates that which XBC port was routed around. Recommended Action: Reset the system backplane to clear the error If the suspect XBC port uses a flex cable, check / replace the flex cable and then the system backplane(s) involved. If the suspect XBC port uses the hardwire link built into the system backplane, replace the system backplane involved. WBEM EventID: 599. WBEM ProviderName: During routing a crossbar is found to be in an unexpected routing state. Probable Cause: An XBC is indicating a port failure. Recommended Action: Validate all of the cells connectivity to the PD. Check the XBC chips seating reset the system replace either cells/system backplane. WBEM EventID: 600. WBEM ProviderName: An unexpected XBC forward progress state was continually found until timing out. Probable Cause: An XBC is indicating a port failure. Recommended Action: Validate all of the cells connectivity to the PDCheck the XBC chips seating reset the system replace either cells/system backplane. WBEM EventID: 601. WBEM ProviderName: During remote routing, the current port's neighbor is not healthy. Probable Cause: An XBC port is not healthy. Recommended Action: Check for hardware failure: flex cables, crossbar chips, etc. WBEM EventID: 602. WBEM ProviderName: The CC to XBC link is not viable. Probable Cause: The CC to XBC link is not operational. Recommended Action: Reset the cell Reset the system backplane Contact HP Support personnel to troubleshoot problem. WBEM EventID: 603. WBEM ProviderName: Remote routing a crossbar failed. Probable Cause: A failure was encountered while performing remote routing on an XBC, most likely due to a problem with the system backplane or local cell. Recommended Action: Check for hardware failure: CC, XBC to CC link, flex cables, crossbar chip, etc. WBEM EventID: 604. WBEM ProviderName: Too many XBC-to-XBC were broken in the complex. Probable Cause: Port status indicated that two or more ports on a XBC had errors. Recommended Action: Check for hardware failure: flex cables, crossbar chip, etc. WBEM EventID: 605. WBEM ProviderName: This cell did not get the XBC Global Semaphore. Probable Cause: XBC write or read failure. Recommended Action: check XBC, check link, check CC. WBEM EventID: 606. WBEM ProviderName: 40 WBEM Provider Event Tables

41 Attempted an XBC SM4 takeover and timed out trying to unlock the SM4. Probable Cause: Cannot takeover an XBC semaphore that has been held for a long time. Recommended Action: Try forcing firmware to reroute the fabric by cycling 48V power on the cabinets. Look for other fabric chassis codes that explain why the current owner of the SM4 was unable to release it. Look for fabric problems on the backplane. WBEM EventID: 607. WBEM ProviderName: Waiting for the XBC Global Semaphore has timed out. Probable Cause: XBC Key Contention. Hardware Failure. Recommended Action: Look for other chassis codes that indicate XBC Key contention. Check XBC. Check Links/Flex Cables. WBEM EventID: 608. WBEM ProviderName: A timeout occurred while attempting to release the XBC semaphore. Probable Cause: XBC Key Contention. Hardware Failure. Recommended Action: Look for additional chassis codes that would explain the failure. Check XBC. Check Link/Flex Cables. WBEM EventID: 609. WBEM ProviderName: Management Processor Firmware Battery Failure or NVRAM change. Probable Cause: Determine if the firmware was recently upgraded. This is often the reason for the NVRAM to change. If not, and the A/C power has been removed, than it's possible the battery is indeed going bad and would need to be replaced. WBEM EventID: 610. WBEM ProviderName: Management Processor Firmware Software. Probable Cause: A software error was detected and is being logged. The internal data is connected to the location and module where the error occurred. The Forward Progress Log will receive additional (lower alert level) event entries with more data associated with this event. WBEM EventID: WBEM ProviderName: Management Processor detected an I2C Communication with BMC. Probable Cause: An I2C Communication failure with the Baseboard Management Controller was detected. Without I2C communication, the system cannot be powered on/off or reset. Check the I2C communication via the 'SR' command or the 'PS' command. If it is indeed down, look for hardware reasons. It's possible resetting the Management Processor firmware ('XD' command option 'r') or completely cycling AC power of the system will restore the communication. WBEM EventID: WBEM ProviderName: A CRC error was discovered when verifying the ROM. Probable Cause: Either the ROM was programmed incorrectly or has gone bad. Reprogram the Flash on the cell board. WBEM EventID: 613. WBEM ProviderName: CPU Revisions did not match. Probable Cause: 2 cpus are at different revisions. Replace incompatible cpu. WBEM EventID: 638. WBEM ProviderName: 2 cpus are running at mismatched frequencies. Probable Cause: There is a CPU or Cell compatibility problem. Verify that all cpus are clocked at the same frequency and have the same ratios set. WBEM EventID: 639. WBEM ProviderName: A cpu is being overclocked. Probable Cause: A cpu is being clocked at a rate higher than it is rated for. Replace the cpu or cell board. WBEM EventID: 640. WBEM ProviderName: Copy of complex profile on sub and cells don't match. Probable Cause: MP NVRAM was erased by removing MP from system without setting 'NVRAM SAVE' switch to on. MP was replaced with cabinet's AC Breakers 'off'. Either of first two causes and replacing or installing a cell board with cabinet's AC Breakers 'off'. Recommended Action: Remove cell board causing problem. Power complex on and allow cells to distribute their copy of complex profile to MP, then add new cell following proper OLA procedures. Remove improper cell board. Execute MP Handler 'CC' command and choose 'Last Profile'. This will load the sub with what should be the same copy as the cells. Then add new cell board. WBEM EventID: 641. WBEM ProviderName: Platform Events 41

42 Duplicate cabinet number detected. Probable Cause: When adding a new cabinet to the complex or replacing the UGUY, the cabinet number switch was set to a number already in use. Recommended Action: Turn off AC breakers to cabinet with duplicate number. Check all other cabinet numbers in the complex for validity. Set cabinet number switch on UGUY-PCB in new cabinet (s) to proper cabinet number. Turn on AC breakers for cabinet(s). WBEM EventID: 642. WBEM ProviderName: MP ID command must be run. Probable Cause: MP lost its profile by being replaced with power off,or, 'NVRAM save' switch was not enabled and MP was removed and replaced. Also, at the same time, a cell was replaced or added while power was off. Both scenarios are violations of OL* Rules. A complex_profile_incoherent code was issued. The 'cc' command was run and genesis profile was selected. Recommended Action: If 'cc' command is selected, choose 'last good profile' instead of genesis profile, or remove illegal cell(s), power up and follow OL* Rules. WBEM EventID: 643. WBEM ProviderName: MP Battery is low. Probable Cause: MP was running on battery for too long. Someone didn't set 'NVRAM Save' switch to 'off'. Recommended Action: Replace battery as per MP Battery Remove and Replace procedures. WBEM EventID: 645. WBEM ProviderName: Partition being reset due to watchdog timeout expiring. Probable Cause: The watchdog mechanism triggers the MP to reset a partition if its OS becomes unresponsive. An unresponsive OS is detected when the OS fails to refresh the watchdog timer before it expires. PA systems refresh the watchdog timer by emitting an event with data field set to activity level/timeout, and the timeout field specifies the desired timeout. IPF systems refresh the watchdog timer using the IPMI clear watchdog command. The MP emits this event when timer expiration triggers resetting the partition. OS-specific and platform-specific procedures are used to enable/disable the watchdog timer from resetting the partition. See platform and OS documentation for details. Recommended Action: Find out why the partition's OS had hung. The cause could be bad HW that crashed the partition, or in rare cases, a combination of events that caused the OS to be unable to refresh the watchdog timer. Look for other events preceding the timeout for clues to the root cause of the partition being unresponsive. WBEM EventID: 646. WBEM ProviderName: PDHC FW was reset by hardware due to firmware inactivity. Probable Cause: PDHC Firmware hung; causing inactivity. Recommended Action: Even though the PDHC will reset itself without interrupting the cell, HP Support personnel should be contacted to troubleshoot the PDH daughtercard and/or cell board as soon as possible. WBEM EventID: 647. WBEM ProviderName: Power Up Aborted, Over Temp. Probable Cause: Computer Room over temp. Recommended Action: Cool Computer Room. WBEM EventID: 649. WBEM ProviderName: Too Few Bulk Power Supplies Available. Probable Cause: Too many entities installed in the cabinet for the Power Available. Recommended Action: Remove entities until Power Requirements are met. Add Bulk Power Supplies, if under populated. WBEM EventID: WBEM ProviderName: No Cabinet Start, Insufficient Blowers. Probable Cause: The number of blowers required is a hard number. It is not dependent upon the number of entities installed in a Cabinet. The Utilities Subsystem is not allowing the Cabinet to power up due to an insufficient number of installed blowers. Recommended Action: Install missing Cabinet Blowers. If proper number of blowers are installed, troubleshoot blower presence detection. WBEM EventID: 651. WBEM ProviderName: No Cabinet Start, Insufficient IO Fans. Probable Cause: The number of IO fans required is a hard number. It is not dependent upon the number of entities installed in a Cabinet. The Utilities Subsystem is not allowing the cabinet to power up due to an insufficient number of installed IO fans. Recommended Action: Install missing IO fans, or if proper number installed, troubleshoot IO fan presence detection. WBEM EventID: 652. WBEM ProviderName: 42 WBEM Provider Event Tables

43 AC power to the PDCA was removed. Data Byte 3 specifies PDCA number. Probable Cause: Circuit breakers on the PDCA are open. Recommended Action: Close the PDCA circuit breakers. WBEM EventID: 653. WBEM ProviderName: Cabinet Main Blower Failed. Probable Cause: Cabinet Blower Failed. Recommended Action: Replace failed blower module as soon as possible following the Blower Module Remove and Replace Procedures. WBEM EventID: 654. WBEM ProviderName: 48 Volt Converter Failed. Data Byte 3 specifies PDCA number. Probable Cause: The 48 Volt DC Converter powered by the PDCA identified failed in the named Bulk Power Supply. Recommended Action: Contact HP Support personnel to troubleshoot problem. WBEM EventID: 655. WBEM ProviderName: Fan failed in designated Bulk Power Supply. Probable Cause: Fan failure or fan obstructed. Recommended Action: If fan is obstructed, remove obstruction. If no obstruction, Contact HP Support personnel to troubleshoot problem. WBEM EventID: 657. WBEM ProviderName: 1 Side Converter Over Temp. Probable Cause: If there are chassis codes indicating an elevated ambient air temperature, other chassis codes will be generated and system shutdown will be necessary. Recommended Action: Resolve the elevated ambient air temperature problem as quickly as possible. If the air temperature gets too high, the complex must be shutdown to avoid damage. WBEM EventID: WBEM ProviderName: Bulk Power Supplies are not Redundant. Probable Cause: Entities were added to the cabinet, increasing the estimated Power Consumption. Or, a non-functional GSP bus entity has become functional, providing previously missing power consumption information. Recommended Action: Purchase and install a Bulk Power Supply, if redundancy is desired. WBEM EventID: 659. WBEM ProviderName: +48V DC has exceeded its upper limit. Probable Cause: The cabinet's 48V power has exceeded an acceptable upper threshold. Recommended Action: Contact HP Support personnel to troubleshoot problem. WBEM EventID: 660. WBEM ProviderName: FPL_IndicationProv +48V DC has fallen below its lower limit. Probable Cause: The cabinet's 48V power has fallen below an acceptable lower threshold. Recommended Action: Contact HP Support personnel to troubleshoot problem. WBEM EventID: 661. WBEM ProviderName: FPL_Indica Cabinet Fan Failed. Probable Cause: Cabinet Fan Failed. Recommended Action: Replace failed cabinet fan module as soon as possible following the Cabinet Fan Module Remove and Replace Procedures. WBEM EventID: 662. WBEM ProviderName: Housekeeping power has exceeded expected levels. Probable Cause: The cabinet's housekeeping power has risen above an acceptable upper threshold. Recommended Action: Contact HP Support personnel to troubleshoot problem. WBEM EventID: 670. WBEM ProviderName: Housekeeping power has fallen below expected levels. Probable Cause: The cabinet's housekeeping power has fallen below an acceptable upper threshold. Recommended Action: Contact HP Support personnel to troubleshoot problem. WBEM EventID: 671. WBEM ProviderName: The BPSs for the cabinet are illegally configured. Data Byte 3 = PDCA number. Probable Cause: The BPS are installed in an illegal configuration. Recommended Action: Re-configure the BPS in a manner consistent with the explanation in the Problem Description statement. WBEM EventID: 672. WBEM ProviderName: Platform Events 43

44 BPS ID received from installed Bulk Power Supply was unknown. Probable Cause: The designated power supply is responding with an illegal BPS ID. It could be a faulty supply, a different revision, or a wrong supply in the wrong box. Recommended Action: Replace this Bulk Power Supply with a proper one. WBEM EventID: 673. WBEM ProviderName: Ambient Air Sensor Overtemp. Probable Cause: Room Temperature has risen to a critical level. Recommended Action: Shutdown and power off the system. Correct air temperature problem. WBEM EventID: 675. WBEM ProviderName: Ambient Air Sensor Overtemp. Probable Cause: Room Temperature is rising or falling. Recommended Action: Check the error log's previous entries within a logical time frame. If temperature is rising, prepare for system shutdown. If temperature is dropping, then problem is probably resolved. WBEM EventID: 676. WBEM ProviderName: Ambient Air Sensor Overtemp. Probable Cause: Room Temperature is rising or falling. Recommended Action: Check the error log's previous entries within a logical time frame. If temperature is rising, prepare for system shutdown. If temperature is dropping, then problem is probably resolved. WBEM EventID: 677. WBEM ProviderName: IO Fan Failed. Probable Cause: IO Cooling Fan Failed. Recommended Action: Replace IO Fan Module as soon as possible following the IO Fan Module Remove and Replace Procedures. WBEM EventID: 678. WBEM ProviderName: Cabinet Power System is in overload. Probable Cause: A Bulk Power Supply has failed, or, entities were added. Look for one or more BPS_Fail Chassis Codes preceding this one for the actual failures. This code is a warning of possible cabinet unreliability. Recommended Action: Contact HP Support personnel to troubleshoot the problem. WBEM EventID: 680. WBEM ProviderName: Cabinet Shutdown - Insufficient Blowers. Probable Cause: One blower has failed creating condition N. Before condition N was corrected, another blower in the same cabinet was declared failed. This created the illegal condition of N-1. Recommended Action: Contact HP Support personnel to troubleshoot the problem. WBEM EventID: 681. WBEM ProviderName: Cabinet Shutdown - Insufficient IO Fans. Probable Cause: One IO fan has failed creating condition N. Before condition N was corrected, another IO fan in the same cabinet failed. This created the illegal condition of N-1. Recommended Action: Contact HP Support personnel to troubleshoot the problem. WBEM EventID: 682. WBEM ProviderName: IO Expansion Utility Cabinet Fan Failed. Probable Cause: IO Expansion Utility Fan or Fan sensor failure PM failure. Recommended Action: Contact HP Support personnel to troubleshoot the problem. WBEM EventID: 683. WBEM ProviderName: Watchdog Timer Expired. Probable Cause: Hardware or firmware failure on the UGUY. Recommended Action: Check revision of CLU firmware. If out of date, or known bad revision, use FWUU to update CLU firmware. Contact HP Support personnel to troubleshoot problem. WBEM EventID: 684. WBEM ProviderName: Invalid checksum from EEPROM. Probable Cause: Problem with I2C bus. Recommended Action: If every entity with a FRUID logs an error, the problem is probably with the CLU portion of the Utilities Board. Replace the Utilities Board following the Utilities Board Remove and Replace Procedures. If there are a few entities reporting checksum errors, but several have reported in properly, chances are one device is causing the problem with the I2C bus. This will take a more concerted effort to find and correct that problem. Probably wish to take the bus to a minimum configuration and test, add, test until the failure is verified. WBEM EventID: 685. WBEM ProviderName: 44 WBEM Provider Event Tables

45 System Backplane Power Board Fault. Probable Cause: A DC-DC converter on the named power board failed. Recommended Action: Contact HP Support personnel to troubleshoot the problem Caution: The 1.8 volt converters are N+1. The 3.3 volt converters are N+2. If there is a situation where a 1.8 fails at the same time as a 3.3 on a different power board, replace the failed 1.8 board first. WBEM EventID: 686. WBEM ProviderName: Read of EEPROM failed. Probable Cause: The I2C controller on the Utilities Board (CLU section) is bad. This will be shown by many I2C failure codes in the Log. These codes should identify entities on both the System Backplane and the Master IO Backplane. Recommended Action: Contact HP Support personnel to troubleshoot the problem. WBEM EventID: 687. WBEM ProviderName: Read of EEPROM failed. Probable Cause: The I2C controller on the Utilities Board (CLU section) is bad. This will be shown by many I2C failure codes in the Log. These codes should identify entities on both the System Backplane and the Master IO Backplane. Recommended Action: Contact HP Support personnel to troubleshoot the problem. WBEM EventID: 688. WBEM ProviderName: Read of LPM Fault failed. Probable Cause: The I2C controller on the Utilities Board (CLU section) is bad. This will be shown by many I2C failure codes in the Log. These codes should identify entities on both the System Backplane and the Master IO Backplane. Recommended Action: Contact HP Support personnel to troubleshoot the problem. WBEM EventID: 689. WBEM ProviderName: IO Power Board Over temperature. Probable Cause: The ambient air is too warm. Recommended Action: Check the Log for other Overtemp s to confirm the environmental problem. WBEM EventID: 690. WBEM ProviderName: IO Power Board Fault. Probable Cause: Input power has created some fault conditions. This will be evident by the presence of several chassis codes in the Log within the same time frame. Recommended Action: The Log must be reviewed carefully for the root cause of the errors. There is almost always a single cause, even if many events are reported. WBEM EventID: 691. WBEM ProviderName: Voltage Margin on IO Power Board failed. Probable Cause: The MP is not communicating with the CLU. Recommended Action: The MP bus (USB) is not functioning. There should be many entries in the Log with the same type of error message. They will point to MP bus errors. Also, try the GSP 'PS' command. This will display status of entities within a cabinet. WBEM EventID: 692. WBEM ProviderName: Failure to read data from a SBCH FRUID EEPROM. Probable Cause: The CLU cannot read the data contained in the EEPROM on the SBCH board in the same cabinet. Recommended Action: Contact HP Support personnel to troubleshoot the problem. If this is the only READ failure in this timeframe, replace the SBCH board following the SBCH Board Remove + Replace Procedures as soon as possible. If there are other READ failures in this same cabinet, replace the Utilities Board following the Utilities Board Remove and Replace Procedures. WBEM EventID: 694. WBEM ProviderName: Failure to read data from a UGUY FRUID EEPROM. Probable Cause: Attempted access to read the UGUY FRUID EEPROM failed. Recommended Action: If there is only one FRUID that can't be read, replace that FRU as soon as possible. If there are a lot of log entries for different FRUs, suspect the Utilities Board or the Utilities cable to those FRUs. For example, if the failures are all associated with a Master IO Backplane, the failing FRU is probably the Utilities cable to that backplane. WBEM EventID: 695. WBEM ProviderName: Read EEPROM failed. Probable Cause: The I2C controller on the Utilities Board (CLU section) is bad. This will be shown by many I2C failure codes in the Log. These codes should identify entities on both the System Backplane and the Master IO Backplane. Recommended Action: Replace the Utilities board (UGUY) following the Utilities Board Remove and Replace procedures. WBEM EventID: 696. WBEM ProviderName: Platform Events 45

46 Read command on System Backplane I2C bus failed. Probable Cause: The 100 pin cable from the Utilities Backplane to the System Backplane is bad, or is not properly connected. Recommended Action: Check and reseat the System Backplane Utilities cable. If no help, replace the System Backplane utilities cable following the Backplane Utilities Cable Remove and Replace procedures. WBEM EventID: 697. WBEM ProviderName: Write command on System Backplane I2C bus failed. Probable Cause: The 100 pin cable from the Utilities Backplane to the System Backplane is bad, or is not properly connected. Recommended Action: Check and reseat the System Backplane Utilities cable. If no help, replace the System Backplane utilities cable following the Backplane Utilities Cable Remove and Replace procedures. WBEM EventID: 698. WBEM ProviderName: System Backplane Power Fault. Probable Cause: While running normally, the CLU microcontroller detected a fault on the I2C Bus from the system Backplane LPM. Recommended Action: Check other log entries around this time for other events. If there are other events, analyze for best troubleshooting approach. Check the log carefully as a shorted ASIC could cause many errors to occur. These errors will not necessarily point to the ASIC. If none, replace failed Backplane Power Board. WBEM EventID: 699. WBEM ProviderName: System Backplane voltage margin failed. Probable Cause: The CLU was unable to write to the voltage margin register on the System backplane. Recommended Action: Try re-margining the system backplane and check connections. If many I2C access events are occurring inspect the UGUY utilities board. WBEM EventID: 700. WBEM ProviderName: Failure to write data to FRUID EEPROM. Probable Cause: The entity being written to is not powered up. Recommended Action: Power the entity with the PE command. WBEM EventID: 701. WBEM ProviderName: CPU fan failed. Probable Cause: The CPU fan identified by the attached physical location has failed. Recommended Action: Contact HP Support personnel to troubleshoot problem. WBEM EventID: WBEM ProviderName: CPU fan failing. Probable Cause: The CPU fan identified by the attached physical location is not operating at expected speed. Recommended Action: Contact HP Support personnel to troubleshoot problem. WBEM EventID: WBEM ProviderName: CC chip fan failed. Probable Cause: The CC chip fan identified by the attached physical location has failed. Recommended Action: Contact HP Support personnel to troubleshoot problem. WBEM EventID: WBEM ProviderName: CC chip fan failing. Probable Cause: The CC chip fan identified by the attached physical location is not operating at expected speed. Recommended Action: Contact HP Support personnel to troubleshoot problem. WBEM EventID: WBEM ProviderName: System FW and the PDHC have incompatible shared memory interface revisions. Probable Cause: (Probable) Either System firmware or PDHC Firmware on the named cell was upgraded to a new major revision number and not the other. The major numbers must match when checked by the PDHC or else the cell will not be allowed to boot. Recommended Action: Use FWUU (Firmware Update Utility) to check the revision numbers of PDHC and PDC Firmware on the cell(s) called out in the event log. Compare to other cells in the complex, or, if single cell, check firmware revs. available to FWUU. WBEM EventID: WBEM ProviderName: PDH Controller firmware version is not supported with this version of MP FW. Probable Cause: PDH Controller firmware version is not supported with this version of MP FW. Recommended Action: Update PDHC or MP firmware. WBEM EventID: 707. WBEM ProviderName: 46 WBEM Provider Event Tables

47 Power fault on cell board. Probable Cause: One or more of the DC to DC power converters on the Cell Power Board is displaying a fault condition. Recommended Action: Contact HP Support personnel to troubleshoot the problem. WBEM EventID: 708. WBEM ProviderName: The CPU Node reported a problem initializing its node in the device tree. Probable Cause: See additional logs in determine why initialize node failed. There could be a hardware or PAL problem. WBEM EventID: WBEM ProviderName: The ExecuteCommand function failed on a CPU. Probable Cause: Inter-Processor-Interrupts may not be working, or the command may have timed out. This could be a firmware bug or hardware problem. Look for other clues in the event log. WBEM EventID: 710. WBEM ProviderName: A remote CPU is not prepared to receive a command. Probable Cause: The CPU may be stuck waiting for a previous command or may not be healthy. This could also be caused by a system resource contention problem. WBEM EventID: 711. WBEM ProviderName: An error was encountered when executing a PAL_PROC. Probable Cause: PAL was unable to be successfully called. See other event ids to determine if action needs to be taken. WBEM EventID: 614. WBEM ProviderName: CPUs loaded in wrong order. Probable Cause: CPUs not loaded in correct order. Recommended Action: Load CPUs in order 0, 1, 2, 3. WBEM EventID: 615. WBEM ProviderName: The XBC SBE and LPE errors were not cleared properly. Probable Cause: the link generated a new error. Recommended Action: check CC, check link Check logs for other errors. If error is persistent, replace cell board. WBEM EventID: WBEM ProviderName: The CC to XBC link pattern test failed. Probable Cause: Unspecified. WBEM EventID: WBEM ProviderName: Reading a platform storage variable from the PDHC/MP. Probable Cause: Either the MP is not present, or the requested information does not exist. Ensure that the MP is functioning and that the proper data is being requested. WBEM EventID: 616. WBEM ProviderName: An error was returned on a Platform Storage Write Command to the PDHC/MP. Probable Cause: The MP is not present, may be out of space, or the command was badly formatted. Ensure that the MP has enough space and try again. If the problem persists, contact engineering. WBEM EventID: 617. WBEM ProviderName: The Sequencer was unable to find/use a needed tree node. Probable Cause: This is a bug, contact engineering. WBEM EventID: 618. WBEM ProviderName: Firmware encountered an error in processing the partition variables. Probable Cause: Either the GSP was not present or there was a resource problem storing the variable. There should be other clues in the event id log to indicate which is the case. Restore the GSP. WBEM EventID: 619. WBEM ProviderName: A non-critical cell power fault has occurred. Probable Cause: A CPU Power Module has been disabled following a thermal warning reported by that CPU Module. Recommended Action: Contact HP Support personnel to troubleshoot the problem. WBEM EventID: 620. WBEM ProviderName: CPUProcConfigValue in /options is not compatible with the current PAL/CPU. Probable Cause: Modify CPUProcConfigValue in /options to set the correct bits. WBEM EventID: WBEM ProviderName: Firmware was unable to determine the Processor Dependent Features. Probable Cause: Contact Engineering, This is a bug. WBEM EventID: 622. WBEM ProviderName: Platform Events 47

48 Data field contains data meant for firmware debug only. Probable Cause: Debug event. Recommended Action: Contact your hp support representative. WBEM EventID: WBEM ProviderName: The CLU has encountered an undefined case. Probable Cause: CLU firmware on the UGUY has gotten into an unexpected execution path, most likely due to a hardware issue on the UGUY. Recommended Action: Check revision of CLU firmware. If out of date, or known bad revision, use FWUU to update CLU firmware. Contact HP Support personnel to troubleshoot problem. WBEM EventID: 624. WBEM ProviderName: An unknown Cell voltage margin has been detected. Probable Cause: A user has manually, using back-door debugging methods, altered the voltage margin setting of one or more Cell Board or Cell Power Board converters. WBEM EventID: 625. WBEM ProviderName: The run-time verification of a programming assumption has failed. Probable Cause: Hardware or software in unknown state. Recommended Action: Upgrade PDHC firmware to latest revision. If already at current revision, contact HP Support personnel to troubleshoot the problem. WBEM EventID: 626. WBEM ProviderName: An unknown error has been detected by the PDHC firmware. Probable Cause: Hardware in unknown state, or programming bug found. Recommended Action:. Recommended Action: Upgrade PDHC firmware to latest revision. If already at current revision, contact HP support personnel to troubleshoot the problem. WBEM EventID: 627. WBEM ProviderName: An attempt to write to a device on the PDHCs I2C bus has failed. Probable Cause: A hardware fault has occurred. Recommended Action: Contact HP Support personnel to troubleshoot the Cell Board, Cell Power Board, and/or PDH Daughtercard. WBEM EventID: 628. WBEM ProviderName: An attempt to read from a device on the PDHC's I2C bus has failed. Probable Cause: A hardware fault has occurred. Recommended Action: Contact HP Support personnel to troubleshoot the Cell Board, Cell Power Board, and/or PDH Daughtercard. WBEM EventID: 629. WBEM ProviderName: An attempt to write to a device on the PDHC's SM bus has failed. Probable Cause: A hardware fault has occurred. Recommended Action: Contact HP Support personnel to troubleshoot the Cell Board, Cell Power Board, and/or PDH Daughtercard. WBEM EventID: 630. WBEM ProviderName: An attempt to read from a device on the PDHC's SM bus has failed. Probable Cause: A hardware fault has occurred. Recommended Action: Contact HP Support personnel to troubleshoot the Cell Board, Cell Power Board, and PDH Daughtercard. WBEM EventID: 631. WBEM ProviderName: Cell boot has been disabled due to a failure setting the frequency registers. Probable Cause: A hardware fault has occurred. Recommended Action: Contact HP Support personnel to troubleshoot the problem. WBEM EventID: 632. WBEM ProviderName: An error has occurred while updating System FW. Probable Cause: Obsolete version of FWUU. Recommended Action: If you are not using the latest revision of FWUU, obtain and use the latest version of FWUU to retry the update. WBEM EventID: 633. WBEM ProviderName: The PDHC firmware was reset for some unknown reason. Probable Cause: An unknown hardware fault has caused the PDHC to reset. Recommended Action: Upgrade PDHC firmware to the latest revision. If the error continues, contact HP support personnel to troubleshoot the PDH Daughtercard and/or Cell Board. WBEM EventID: 634. WBEM ProviderName: Cell boot has been disabled because setup of a CPU thermal sensor failed. Probable Cause: A hardware fault prevents access to a CPU module's Processor Information ROM. Recommended Action: Contact HP support personnel to troubleshoot the Cell Board, the PDH Daughtercard, and/or the offending CPU module. WBEM EventID: 635. WBEM ProviderName: 48 WBEM Provider Event Tables

49 A CPU module has reported overtemp, so will be powered off in 1 minute. Probable Cause: The Processor Information ROM on the processor module is unprogrammed or programmed with invalid temperature thresholds. Recommended Action: Contact HP support personnel to troubleshoot the problem. WBEM EventID: 636. WBEM ProviderName: An error occurred while updating the PDHC firmware. Probable Cause: MP firmware not at a revision that supports that version of PDHC firmware. Recommended Action: If MP is not at a compatible revision, update the MP firmware to a compatible revision and repeat PDHC firmware update. WBEM EventID: 637. WBEM ProviderName: Boot is disabled because the cell type does not match the System FW ROM type. Probable Cause: The System FW ROM in unprogrammed, or an invalid System FW ROM image is programmed in the System FW flash. Recommended Action: Update the System FW using Firmware Update from the MP. WBEM EventID: 712. WBEM ProviderName: The PDHC has waited an abnormally long time for PDH bus access. Probable Cause: A hardware fault is preventing the PDH arbiter from granting the PDHC control of the bus. Recommended Action: Contact HP support personnel to troubleshoot the cell board and/or PDH daughtercard. WBEM EventID: 713. WBEM ProviderName: The PDHC has waited an abnormally long time to obtain the PDH semaphore. Probable Cause: A hardware fault is preventing the PDH bus semaphore from being taken/released as expected. Recommended Action: Contact HP support personnel to troubleshoot the Cell Board and/or PDH Daughtercard. WBEM EventID: 714. WBEM ProviderName: An error occurred while transmitting an IPMI message in the BMC2HOST direction. Probable Cause: A hardware fault is preventing the BMC2HOST queue from working. Recommended Action: Contact HP support personnel to troubleshoot the PDH Daughtercard. WBEM EventID: 715. WBEM ProviderName: EFI unable to read initial debug level from the BMC. Probable Cause: BMC not functioning properly. Recommended Action: Reset the BMC. Contact your HP representative to check the BMC. WBEM EventID: 716. WBEM ProviderName: A XBC port was unexpectedly found to not be landmined. Probable Cause: An XBC is indicating a port failure. Recommended Action: Validate all of the cells connectivity to the PD Check the XBC chips seating reset the system replace either cells/system backplane. WBEM EventID: 717. WBEM ProviderName: An invalid number of XBC ports were landmined in the system. Probable Cause: Hardware failure: link, crossbar chip, or cell. Recommended Action: Check for hardware failures. Reset backplane to re-initialize fabric. WBEM EventID: WBEM ProviderName: The run-time verification of a programming assumption has failed. Probable Cause: Hardware in unknown state, or programming bug found. Recommended Action: Upgrade PM firmware to latest revision. If already at current revision, replace UGUY board. WBEM EventID: 728. WBEM ProviderName: An unknown error has been detected by the PDHC firmware. Probable Cause: Hardware in unknown state, or programming bug found. Recommended Action: Upgrade PM firmware to latest revision. If already at current revision, replace UGUY board. WBEM EventID: 729. WBEM ProviderName: Data field contains data meant for firmware debug only. Probable Cause: Debug event. Recommended Action: Contact your hp support representative. WBEM EventID: WBEM ProviderName: A cabinet has been configured using an invalid cabinet number. Probable Cause: Re-configure cabinet to use a valid cabinet number. WBEM EventID: 732. WBEM ProviderName: Platform Events 49

50 Cells trying to join a PD are at incompatible firmware revisions. Probable Cause: The reporting cell is at a different firmware revision than the cell reported in the data field. A PD cannot be established. Please reprogram the 2 cells to the same firmware revision. WBEM EventID: 733. WBEM ProviderName: An attempt to write to a device on the PM's I2C bus has failed. Probable Cause: A hardware error has occurred. Recommended Action: Replace the UGUY board. WBEM EventID: 734. WBEM ProviderName: An attempt to read from a device on the PM's I2C bus has failed. Probable Cause: A hardware error has occurred. Recommended Action: Replace the UGUY board. WBEM EventID: 735. WBEM ProviderName: An error was encountered updating the cell info structure in ICM. Probable Cause: This should not happen. Contact engineering to diagnose the problem. WBEM EventID: 736. WBEM ProviderName: An error was encountered pointing the slave cell consoles to the diva. Probable Cause: A CPU on the slave cell could not process an interrupt in time or establish the diva console. WBEM EventID: 737. WBEM ProviderName: An error was encountered trying to relocate a slave cells registry. Probable Cause: There could be a PD rendezvous error or a processor on the slave cell failed to respond to an interrupt in time. WBEM EventID: 738. WBEM ProviderName: Complex Profile Group C CRC didn't match the expected value. Probable Cause: Push out a new Group C complex profile. WBEM EventID: WBEM ProviderName: Failure to identify a core cell during Global MCA. Probable Cause: This will lead to a system reset. WBEM EventID: WBEM ProviderName: Internal firmware programming error in the PMI handler. Probable Cause: Report the IP to the firmware team. Reset the system. This cannot be worked around in the field. WBEM EventID: 743. WBEM ProviderName: During a Cell On Line Add inconsistent number of cells discovered. Probable Cause: This can be caused by inconsistent profile information. This can also occur when an expected cell did not make the original boot of the partition. Update the complex profile to all the cells with a correct view of the system and try to add the cell again. WBEM EventID: 744. WBEM ProviderName: CPUs of different maximum core frequencies are installed. Probable Cause: CPU's of mixed maximum core frequencies are installed. Recommended Action: Install CPU's with the same speed and cache size. WBEM EventID: 753. WBEM ProviderName: The RVL CC-Togo link initialization workaround (PS221) failed. Probable Cause: Hardware link initialization failed. Recommended Action: Contact HP support. Reset cell. WBEM EventID: WBEM ProviderName: Internal firmware programming error. Probable Cause: Report the IP to the firmware team. Reset the system. This cannot be worked around in the field. WBEM EventID: 760. WBEM ProviderName: Initialization of a PCI node in the firmware device tree failed. Probable Cause: The PCI component could not create a device tree node. Recommended Action: This is an internal system firmware error. Update system firmware or contact a system firmware representative. WBEM EventID: 774. WBEM ProviderName: An error was encountered while scanning the PCI bus. Probable Cause: The PCI component experienced an internal system firmware error while scanning the PCI bus. Recommended Action: This is an internal system firmware error. Update system firmware or contact a system firmware representative. WBEM EventID: 775. WBEM ProviderName: 50 WBEM Provider Event Tables

51 An error was encountered initializing the PCI bridge. Probable Cause: The PCI component could not initialize a P2P bridge registers, probably due to faulty hardware. Recommended Action: Reseat or replace the PCI bridge card. WBEM EventID: 776. WBEM ProviderName: An error was encountered initializing the PCI IO map. Probable Cause: The PCI component had insufficient IO port space resources to support the installed PCI cards. Recommended Action: Remove one or more PCI cards to reduce resource requirements; check for faulty cards that are requesting more resources than they need. WBEM EventID: 777. WBEM ProviderName: An error was encountered creating the PCI MMIO map. Probable Cause: The PCI component had insufficient MMIO space to support the installed cards. Recommended Action: Remove one or more PCI cards to reduce the MMIO requirements; check for a PCI card requesting more MMIO resources than it needs. WBEM EventID: 778. WBEM ProviderName: There was an error initializing the SBA node. Probable Cause: An error was while initializing the SBA firmware structures. Recommended Action: Correct any previous errors Invalidate NVM and reset replace the cell board. WBEM EventID: 779. WBEM ProviderName: There was an error discovering the SBA. Probable Cause: An error was discovered with the SBA during discovery. Recommended Action: Correct any previous errors Replace the I/O backplane. WBEM EventID: 780. WBEM ProviderName: An error was encountered while resetting the SBA. Probable Cause: The SBA component could not reset one or more LBA ropes, probably due to faulty hardware. Recommended Action: Replace the failed IO backplane. WBEM EventID: 781. WBEM ProviderName: There was an error initializing the IO link. Probable Cause: The SBA IO link could not be initialized, probably due to cable installation errors or faulty hardware. Recommended Action: Re-install or replace the cables; replace the IO backplane. WBEM EventID: 782. WBEM ProviderName: There is a problem initializing the REO cable. Probable Cause: An SBA IO cable error has been detected. Recommended Action: Verify proper cable connection, repair/replace the cables. WBEM EventID: 783. WBEM ProviderName: The IO chassis discovered was powered off. Probable Cause: Connected IO chassis is powered off. Recommended Action: Either power on the IO chassis or ignore the error if it is powered off by design. WBEM EventID: 784. WBEM ProviderName: There was an error initializing the LBA. Probable Cause: The LBA component initialization routine failed. Recommended Action: This is an internal system firmware error. Update system firmware or contact a system firmware representative. WBEM EventID: 785. WBEM ProviderName: There was an error querying the LBA width. Probable Cause: while writing the LBA phase data. Recommended Action: Replace the I/O backplane. WBEM EventID: 786. WBEM ProviderName: There was an error with the LBA phase. Probable Cause: while writing the LBA phase data. Recommended Action: Replace the I/O backplane. WBEM EventID: 787. WBEM ProviderName: There was an error clearing the LBA. Probable Cause: Unable to clear an error in the LBA. Recommended Action: Check other events for the error being generated replace either the PCI card or the I/O backplane. WBEM EventID: 788. WBEM ProviderName: There was an error with the LBA log. Probable Cause: The LBA component could not generate error logs. Recommended Action: This is an internal system firmware error. Update system firmware or contact a system firmware representative. WBEM EventID: 789. WBEM ProviderName: Platform Events 51

52 There was an error discovering the LBA. Probable Cause: The wrong backplane type was detected. Recommended Action: replace I/O backplane. WBEM EventID: 790. WBEM ProviderName: There was an error configuring the LBA. Probable Cause: Unable to configure the LBA. Recommended Action: replace I/O backplane. WBEM EventID: 791. WBEM ProviderName: There was an error scanning the PCI bus. Probable Cause: Could not scan the card in a populated slot. Typically caused by an improperly installed or faulty PCI card. Recommended Action: Reseat or replace the faulty card. WBEM EventID: 792. WBEM ProviderName: There was an error configuring PCI space through the LBA. Probable Cause: Unable to obtain semaphore. Recommended Action: reset Update to latest recipe. WBEM EventID: 793. WBEM ProviderName: Firmware was unable to find a suitable block of main memory to relocate ROM. Probable Cause: Probably caused by lots of PDT entries, or no main memory present. WBEM EventID: WBEM ProviderName: The Options service received an NVRAM allocation error. Probable Cause: Invalidate NVRAM and reset. WBEM EventID: 808. WBEM ProviderName: SAL errlog access timeout. Probable Cause: Firmware is taking too long to process requests. WBEM EventID: 810. WBEM ProviderName: The echelon given in the data field is not fully populated. Probable Cause: the specified echelon is not fully populated and is not usable. Recommended Action: add or replace dimms in the specified echelon. WBEM EventID: 816. WBEM ProviderName: The main backplane is reporting the LPM status as fault. Probable Cause: Many possible causes, repair / replace the appropriate part. WBEM EventID: WBEM ProviderName: The IO backplane is reporting a LPM status as fault. Probable Cause: Service / replace the appropriate part of, or the entire backplane. WBEM EventID: WBEM ProviderName: System firmware was unable to default the complex profile. Probable Cause: Needed information could not be obtained. Reset the MP. WBEM EventID: 822. WBEM ProviderName: Firmware could not set Pal Proc features. Probable Cause: FW MCA code uses this PAL_SET_PROC_FEATURES to escalate future MCA to BINIT. This event id when emitted during an MCA processing means that any subsequent global MCA would not cause all the processors in the PD to MCA again. WBEM EventID: WBEM ProviderName: Means that the error log space in the Nvram has not been allocated. Probable Cause: This happens because of the NVRAM is full with unconsumed error logs. Clear the error logs. WBEM EventID: 824. WBEM ProviderName: This indicates the maximum number of logs for the event. Probable Cause: This shouldn't be occur. But in case it does than clear the error logs of this event type from the nvram. WBEM EventID: 825. WBEM ProviderName: On Line Delete operation was begun but firmware couldn't find a deleteable cell. Probable Cause: This can occur if the OS has not returned all the CPUs to firmware or if a cell is not marked correctly in the complex profile to allow its deletion. WBEM EventID: 826. WBEM ProviderName: The bulk power system is above its current capacity. Probable Cause: N/A. WBEM EventID: 827. WBEM ProviderName: The bulk specified is warning of a potential thermal problem. Probable Cause: The bulk power supply is warning of an over temperature condition. WBEM EventID: 828. WBEM ProviderName: 52 WBEM Provider Event Tables

53 Malloc failed while trying to process and ERM. Probable Cause: Heap space is completely used or corrupt. Contact Product Engineering. WBEM EventID: 829. WBEM ProviderName: Dimm at physical location in data field is not supported on this platform. Probable Cause: Unsupported dimm in specified slot. Recommended Action: Replace dimm with supported dimm. WBEM EventID: 830. WBEM ProviderName: The OPTIONS component received a memory allocation error. Probable Cause: Invalidate NVRAM and reset. WBEM EventID: 831. WBEM ProviderName: A dimm or CPU has been deconfigured or failed testing. Probable Cause: A deconfigured dimm or cpu has been detected. Examine earlier events to isolate the problem. WBEM EventID: 832. WBEM ProviderName: The cell will not join the PD. Probable Cause: Broken hardware was detected and the cell integration policy combined to cause the cell to not join the PD. Recommended Action: Fix the broken hardware or change the policy using parmgr. If assistance is required, contact the HP Support Center. WBEM EventID: 833. WBEM ProviderName: The error context in NVM was corrupt. Probable Cause: NVM is corrupted. Recommended Action: Check for other errors in the system first. Invalidate NVM and retry boot. Get the latest firmware release. WBEM EventID: 834. WBEM ProviderName: Firmware encountered a problem trying to initialize. Probable Cause: System firmware encountered an initialization error. Recommended Action: Examine detailed event logs to determine the cause. WBEM EventID: 837. WBEM ProviderName: This means that all the cpus in the cell did not show up. Probable Cause: This will result in the cell stepping independently to collect its logs and resting itself. WBEM EventID: 838. WBEM ProviderName: This means that all the cells did not rendezvous during the PD rendezvous. Probable Cause: The cells will reset themselves. WBEM EventID: 839. WBEM ProviderName: The FW tree sanity check failed during the MCA error processing. Probable Cause: The cells will independently log errors and reset. WBEM EventID: 840. WBEM ProviderName: This means that the registry sanity check failed during MCA error handling. Probable Cause: The cells will independently log errors and reset. WBEM EventID: 841. WBEM ProviderName: This means that MCA occurred while OS_MCA was performing error recovery. Probable Cause: The cells will log information and reset. WBEM EventID: 842. WBEM ProviderName: One of the BT errors occurred that results in abandoning memory dump. Probable Cause: A machine check has occurred and cells have not rendezvoused. Recommended Action: Cells will reset themselves. WBEM EventID: 843. WBEM ProviderName: The firmware tree is not complete and hence there will be no PD rendezvous. Probable Cause: The cell will log errors and reset. WBEM EventID: 844. WBEM ProviderName: ACPI configuration mismatch across cells in the partition. Probable Cause: Set the ACPI configuration parameter again to ensure that all cells have a consistent value. WBEM EventID: 845. WBEM ProviderName: Platform Events 53

54 Invalid data read from a CPU module's Processor Information ROM. Probable Cause: The CPU module's Processor Information ROM is unprogrammed. Recommended Action: Contact HP support personnel to troubleshoot the CPU module pointed to by the physical location portion of this event. WBEM EventID: 849. WBEM ProviderName: Invalid parameter when setting cpu frequency ratios. Probable Cause: Specify a valid parameter. WBEM EventID: WBEM ProviderName: Option block in nvram has a checksum error. Probable Cause: Clear NVRAM. WBEM EventID: 851. WBEM ProviderName: An occurred trying to notify the MP of the attempted reset. Probable Cause: The MP is not functioning or the PDHC cannot communicate with it. Reset the MP. WBEM EventID: 858. WBEM ProviderName: Cell has been disabled by the PDHC because no CPU modules were found. Probable Cause: The CPU module(s) that are installed have invalid data stored in the partition specific field of the FRU EEPROM. Recommended Action: If in manufacturing, reprogram the partition specific field of the CPU module(s) FRU EEPROM. Otherwise, contact HP support personnel to troubleshoot the unreported CPU module. WBEM EventID: 866. WBEM ProviderName: Cell has been disabled by PDHC FW because the CPU modules are not compatible. Probable Cause: At least one of the installed CPU modules are incompatible with at least one other CPU module. Recommended Action: Contact HP support personnel to troubleshoot the CPU modules on the Cell. WBEM EventID: 867. WBEM ProviderName: Cell has been disabled because of invalid data in a CPU module Scratch EEPROM. Probable Cause: The CPU module is not an HP CPU module, or the FRUID data for this CPU module has not been programmed. Recommended Action: Contact HP support personnel to troubleshoot the CPU module. WBEM EventID: 868. WBEM ProviderName: The Cell Battery voltage level low warning. Probable Cause: The Cell Battery is low. Recommended Action: It needed to be replaced. WBEM EventID: 869. WBEM ProviderName: The CPU is performance or functionally restricted. Probable Cause: A CPU is broken. Replace it. WBEM EventID: 885. WBEM ProviderName: The RTC was found to be invalid and has been cleared. Probable Cause: The RTC was invalid. Recommended Action: No action is required. The problem has been corrected by SFW. WBEM EventID: 886. WBEM ProviderName: Status indicates that the Late Self Tests did not actually run. Probable Cause: This could be caused by an incompatibility problem between PAL and the CPUs. Check that PAL supports all the CPUs installed on the system. WBEM EventID: 887. WBEM ProviderName: DRAM failure on DIMM XX, deallocate rank. Probable Cause: SFW detected a failing DIMM. Recommended Action: Replace the DIMM flagged by SFW. WBEM EventID: 890. WBEM ProviderName: System Clocks are not valid. Probable Cause: The Cell board has a problem. Either the Real Time Clock is not working properly or the system is not being clocked at the value it thinks it is. WBEM EventID: 891. WBEM ProviderName: A reset for reconfiguration will be performed soon on the cell. Probable Cause: An error during cell initialization occurred and the cell will not be able to join the partition. Look for other errors in the event log that articulate the exact problem. WBEM EventID: 900. WBEM ProviderName: The Partition Profile specifies the wrong architecture type. Probable Cause: This is caused by the wrong type of complex profile being loaded. System firmware will default a new partition profile and continue on. WBEM EventID: 901. WBEM ProviderName: 54 WBEM Provider Event Tables

55 CPU Dual Core Initialization Failed. Probable Cause: MX2 initialization failed. Recommended Action: Reboot. If problem persists contact your HP representative for support. WBEM EventID: 918. WBEM ProviderName: Second CPU in Pair has been disabled. Probable Cause: The second CPU in the Dual Core has been deconfigured as a result of the first core being deconfigured. Recommended Action: Investigate the cause of the first core being deconfigured. WBEM EventID: 919. WBEM ProviderName: Virtualzing Dual Core Registers Failed. Probable Cause: FW failed to virtualize the mx2 interposer. Recommended Action: Reboot. If problem persists contact your HP representative for support. WBEM EventID: 920. WBEM ProviderName: Virtualizing Dual Core Interposer has failed. Probable Cause: Virtualizing the Dual Core Interposer has failed. Recommended Action: Reboot. If problem persists contact your HP representative for support. WBEM EventID: 921. WBEM ProviderName: Install PMI Handler Failed. Probable Cause: Installation of the FW PMI handler has failed. Recommended Action: Reboot. If problem persists contact your HP representative for support. WBEM EventID: 922. WBEM ProviderName: Cell failed compatibility checks. Probable Cause: CPUs are incompatible with each other. Recommended Action: Contact HP Support personnel to troubleshoot the problem. WBEM EventID: 923. WBEM ProviderName: PDH space not available after release from reset. Probable Cause: A hardware fault has occurred. Recommended Action: Contact HP Support personnel to troubleshoot the Cell Board, Cell Power Board and PDH Daughtercard. WBEM EventID: 924. WBEM ProviderName: MPON failed to release. Probable Cause: A hardware fault has occurred. Recommended Action: Contact HP Support personnel to troubleshoot the Cell Board, Cell Power Board and PDH Daughtercard. WBEM EventID: 925. WBEM ProviderName: Dillon failed to reset. Probable Cause: Hardware failure. Recommended Action: Fix the hardware, pdh riser or cell. WBEM EventID: 926. WBEM ProviderName: DMD clock is not running. Probable Cause: A hardware fault has occurred. Recommended Action: Contact HP Support personnel to troubleshoot the Cell Board, Cell Power Board and PDH Daughtercard. WBEM EventID: 927. WBEM ProviderName: All cpus on the Cell are scheduled to be deconfigured. Probable Cause: All cpus on the cell have been scheduled for deconfiguration. On the next reset, the cell will no longer be operational; system firmware will deconfigure all the cpus and this cell will not be part of a partition. This action is not recommended. To recover, the NVRAM on the PDH card must be cleared, the cell power cycled, and defaults restored from disk. WBEM EventID: 928. WBEM ProviderName: Power has been removed from AC input A0. Probable Cause: A power source has been removed from the chassis. WBEM EventID: 931. WBEM ProviderName: Power has been removed from AC input A1. Probable Cause: A power source has been removed from the chassis. WBEM EventID: 932. WBEM ProviderName: Power has been removed from AC input B0. Probable Cause: A power source has been removed from the chassis. WBEM EventID: 933. WBEM ProviderName: Power has been removed from AC input B1. Probable Cause: A power source has been removed from the chassis. WBEM EventID: 934. WBEM ProviderName: Platform Events 55

56 PDHC has detected the PDH battery low warning. Probable Cause: PDH battery power is low. Recommended Action: Replaced the PDH battery. WBEM EventID: WBEM ProviderName: FW will not handoff to the OS_MCA handler for this MCA event. Probable Cause: The error logs should be retrieved from the EFI shell prompt. WBEM EventID: 941. WBEM ProviderName: The NVRAM block table maintained by System Firmware is corrupt. Probable Cause: The NVRAM-based descriptor for System Firmware NVRAM blocks is corrupt. WBEM EventID: 942. WBEM ProviderName: The link between the CC and SBA failed. Probable Cause: See other associated events for the root cause of the failure. WBEM EventID: 961. WBEM ProviderName: The SBA failed and the cell has no I/O. Probable Cause: Cannot configure IO on the cell, probably due to previous errors. Recommended Action: Correct the hardware/software problem indicated by previous errors. WBEM EventID: 962. WBEM ProviderName: The system firmware had an error with the structured error handling mechanism. Probable Cause: Either there is an error in the system firmware or the system firmware has exhausted all resources. Recommended Action: Invalidate NVM or check for newer version of system firmware. WBEM EventID: 963. WBEM ProviderName: Not enough malloc resources for I/O structure error handling. Probable Cause: Either invalidate NVM or check for a new version of system firmware. WBEM EventID: 964. WBEM ProviderName: Unable to create entry for I/O structure error handling. Probable Cause: This is a system firmware error, either invalidate NVM or check for a newer version of system firmware. WBEM EventID: 965. WBEM ProviderName: Unable to bind services for I/O structure exception handling. Probable Cause: This is a system firmware error. Either reset NVM or check for a newer version of system firmware. WBEM EventID: 966. WBEM ProviderName: initializing the I/O structure exception handling services. Probable Cause: This is a system firmware error. Either reset NVM or check for a newer version of system firmware. WBEM EventID: 967. WBEM ProviderName: initializing structured I/O exception data structures. Probable Cause: This is a system firmware error, there is a conflict with system resources. Either reset NVM or check for a newer version of system firmware. WBEM EventID: 968. WBEM ProviderName: The I/O exception context has an error. Probable Cause: This is a system firmware error. Reset the system, invalidate NVM and reset the system, or check for a newer version of the system firmware. WBEM EventID: 969. WBEM ProviderName: creating the internal data and services for the SBA. Probable Cause: This is a system firmware error. Reset the system; invalidate NVM and reset the system; or check for a newer version of system firmware. WBEM EventID: 970. WBEM ProviderName: attaching the services to the SBA internal data structures. Probable Cause: This is a system firmware error. Reset the partition; invalidate NVM on the reporting cell and reset the system; or check for a newer version of system firmware. WBEM EventID: 971. WBEM ProviderName: initializing the internal SBA data and services. Probable Cause: This is a system firmware error. Reset the partition; invalidate NVM on the reporting cell and reset the partition; or check for newer system firmware. WBEM EventID: 972. WBEM ProviderName: 56 WBEM Provider Event Tables

57 The SBA type is unknown to the system firmware. Probable Cause: This is either a system firmware error, or the wrong I/O is connected to the system. Validate the system recipe both firmware and hardware. WBEM EventID: 973. WBEM ProviderName: An embedded I/O device is missing. Probable Cause: Replaces the I/O card specified by the physical location. WBEM EventID: 974. WBEM ProviderName: Predictive Failure in Memory. Probable Cause: You will receive this message if the memory system is observing a lot of corrected ECC errors from a DIMM. The specified DIMM may need to be serviced. Recommended Action: Contact your HP support representative to check the affected hardware. WBEM EventID: WBEM ProviderName: Windows: Server Agents Management data not accessible, locked property. Probable Cause: The installed management software has detected an unstable state of the underlying IPMI (Intelligent Platform Management Interface) subsystem and has disabled all management information from being shown by any manageability applications. The management information will become available automatically as soon as the IPMI subsystem has stabilized. Recommended Action: No action is required. WBEM EventID: WBEM ProviderName: PCI slot exceeds power limit. Probable Cause: The I/O configuration's power consumption exceeds the supported limit. Recommended Action: Remove the I/O card from each slot indicated by an IO_PCI_POWER_OVERLOAD_ERR event. WBEM EventID: 976. WBEM ProviderName: The clock ratio reported by manageability does not match the actual clock ratio. Probable Cause: This is a hardware error and it is fatal. WBEM EventID: WBEM ProviderName: Manual override of fatal stop boot condition. Probable Cause: The user has initiated manual O/S boot despite the existence of a error. Recommended Action: Correct the error condition (see output of 'INFO WARNING' EFI shell command), reboot the system, and then initiate O/S boot. WBEM EventID: 985. WBEM ProviderName: Firmware unable to relocate VGA BIOS. Probable Cause: Most likely there is a permanent memory error in the VGA BIOS region (physical address 0xc0000-0xdffff). Recommended Action: Replace the DIMM causing the permanent memory error in the VGA BIOS region. The PDT reports which DIMM is causing errors in the physical address range 0xc0000-0xdffff. WBEM EventID: 986. WBEM ProviderName: The Compatibility Matrix stored in NVRAM has a checksum error. Probable Cause: NVRAM has become corrupt. Restore from a backup. WBEM EventID: 987. WBEM ProviderName: The buffer size is too small for the XBC error log. Probable Cause: Firmware error. Recommended Action: Reset cell. WBEM EventID: WBEM ProviderName: System firmware was unable to clear an XBC error. Probable Cause: The particular XBC and port could have a persistent error. Recommended Action: Check flex cable indicated by event data. WBEM EventID: WBEM ProviderName: encountered while collecting PCI error logs. Probable Cause: An error occurred while collecting the PCI error logs. Recommended Action: No action can be taken. The result is some or all PCI error logs will be unavailable. WBEM EventID: WBEM ProviderName: encountered while collecting SBA error logs. Probable Cause: An error occurred while collecting the SBA error logs. Recommended Action: No action can be taken. The result is some or all SBA error logs will be unavailable. WBEM EventID: WBEM ProviderName: Platform Events 57

58 Fabric is unable to route the crossbar after multiple retry attempts. Probable Cause: Hardware problem. Possible bad XBC or Cell Controller. Recommended Action: Check for hardware failures. Reset backplane to re-initialize fabric. WBEM EventID: WBEM ProviderName: Windows: Predictive Failure in Memory (). Probable Cause: You will receive this message if the system is correcting a lot of ECC single bit errors. It may mean that the module is about to fail, or environmental conditions in the server are causing more errors than usual. This event message will be generated for one of the following conditions 1000 single-bit errors on the same address in a 48 hour time period. 50 single-bit errors on the same DIMM (not the same address) in a 24 hour time period. 100 single-bit errors on the same DIMM (not the same address) in a 1 week time period. Recommended Action: If you receive this message, contact your support provider to determine if a predictive repair should be made. WBEM EventID: WBEM ProviderName: Windows: Predictive Failure in Memory (Critical). Probable Cause: You will receive this message if the system is correcting a lot of ECC single bit errors. It may mean that the module is about to fail, or environmental conditions in the server are causing more errors than usual. This event message will be generated for one of the following conditions 1500 single-bit errors on the same address in a 72 hour time period. 120 single-bit errors on the same DIMM (not the same address) in a 24 hour time period. 130 single-bit errors on the same DIMM (not the same address) in a 1 week time period. Recommended Action: If you receive this message, contact your support provider to determine if a predictive repair should be made. WBEM EventID: WBEM ProviderName: A rope parity error occurred. Probable Cause: An unexpected but random error occurred. Reboot the system. There is a problem with the system bus. Contact your HP representative to check the system bus. WBEM EventID: WBEM ProviderName: PCI card inaccessible due to bus error. Probable Cause: There is a problem with the system bus. Contact your HP representative to check for faulty devices on the bus.. WBEM EventID: WBEM ProviderName: PCI card inaccessible due to device error. Probable Cause: An unexpected but random error occurred. Reboot the system. There is a problem with the system bus. Contact your HP representative to check the system bus. Check the system forward progress log (available from the Management Processor) for additional information about this problem. WBEM EventID: WBEM ProviderName: error reading bmc first boot token. Probable Cause: FW tried to read the first boot token and received a failure. Recommended Action: AC power cycle the system. If this doesn't work, contact HP support. WBEM EventID: WBEM ProviderName: An error occurred while enabling hashing in the platform cache. Probable Cause: An error return status. This could happen if the tree was corrupted or there was an error verifying the hashing setting. Recommended Action: reset the partition. WBEM EventID: WBEM ProviderName: It indicates loss of cell connectivity in the partition. Probable Cause: It will lead to cells performing RESET_FOR_RECONFIG after getting the error logs. WBEM EventID: WBEM ProviderName: building cell-level FW device tree. Probable Cause: Data field displays the status of creating the cell level device tree for use by firmware. See previous errors already reported. WBEM EventID: WBEM ProviderName: The NVRAM service was unable to satisfy an NVRAM allocation request. Probable Cause: NVRAM is full. This is extremely unlikely. Recommended Action: Clear NVRAM and reset. WBEM EventID: WBEM ProviderName: 58 WBEM Provider Event Tables

59 The OS has registered an OS_INIT vector, but it has not passed the checksum. Probable Cause: The OS has registered an OS_INIT vector and checksum, but the checksum did not match the calculated value. Recommended Action: Reboot. If problem persists, contact support. WBEM EventID: WBEM ProviderName: The RTC not updating its internal time registers. Probable Cause: Bad RTC chip on the PDH daughtercard. Recommended Action: Replace PDH daughtercard. WBEM EventID: WBEM ProviderName: Uncorrectable PAA fault on MX2. Probable Cause: An uncorrectable PAA fault has occurred on the MX2 module and PAA firmware has halted. Recommended Action: Contact your HP support personnel. WBEM EventID: WBEM ProviderName: fabric API is about to open the a link going out of the local cell. Probable Cause: An error prevented the use of a fabric link. Recommended Action: Collect IPMI event logs for more information regarding the failure. Contact your HP Support Representative to investigate the fabric subsystem. WBEM EventID: WBEM ProviderName: One or more of the blades in the domain could not communicate. Probable Cause: Connection problem between blade and the enclosure. Recommended Action: ilo will attempt to correct communication issues. If this fails verify FW is at a supported revision and matached across the blades. Consider cycling stby power to the affected blades. WBEM EventID: WBEM ProviderName: An Arches fabric CSR read was unsuccessful because of a timeout. Probable Cause: An error occurred while reading a hardware register. Other events should detail the error. Recommended Action: Contact your HP Support Representative to investigate the fabric and firmware vertex modules. WBEM EventID: WBEM ProviderName: An Arches fabric CSR write was unsuccessful. Probable Cause: An error occurred while writing a hardware register. Other events should detail the error. Recommended Action: Contact your HP Support Representative to investigate the fabric and firmware vertex modules. WBEM EventID: WBEM ProviderName: The event data details the error that was encountered. Probable Cause: A fabric error occurred while preparing for rendezvous. Recommended Action: Contact your HP Support Representative to investigate the fabric and firmware vertex modules. WBEM EventID: WBEM ProviderName: The maximum memory supported by this system has been exceeded. Probable Cause: Too much memory has been installed in the system. Recommended Action: Remove DIMMs to get the total memory size below the amount of memory returned in the data field. WBEM EventID: WBEM ProviderName: Failed to delete a bad port while routing the fabric. Data field indicates return status. Probable Cause: Experienced an error while routing the fabric. Recommended Action: Contact your HP Support Representative to investigate the fabric and firmware vertex modules. WBEM EventID: WBEM ProviderName: Failed to delete an edge that was found to be bad during routing. Probable Cause: Experienced an error while routing the fabric. Recommended Action: Contact your HP Support Representative to investigate the fabric and firmware vertex modules. WBEM EventID: WBEM ProviderName: A command to the memory buffer chip failed to complete. Probable Cause: System firmware did not get a completion status from a command to a memory buffer chip. Recommended Action: Contact HP support. WBEM EventID: WBEM ProviderName: Platform Events 59

60 The Arches Fabric function ArfIsCsrRouteTraversable was called for a back-to-back system. This is unsupported, ArfIsCsrRouteTraversable should only be called for systems with crossbars. No data. Probable Cause: An unsupported fabric call was made. Recommended Action: Contact your HP Support Representative to investigate the fabric and firmware vertex modules. WBEM EventID: WBEM ProviderName: An invalid port number was given as an input to an Arches Fabric Traversability function. The port is expected to be an internal XBC num (8-15), but the actual port was not. Data field: (XBC number 32) (port number 48). Probable Cause: Internal firmware error. Recommended Action: Contact your HP Support Representative to investigate the fabric and firmware vertex modules. WBEM EventID: WBEM ProviderName: Unable to read XBC port neighbor information. Data field: (xbcnum 32) (portnum 48). Probable Cause: System firmware was unable to read a fabric hardware register. Recommended Action: Capture IPMI event logs, look for additional errors. Contact your HP Support Representative to analyze the fabric. WBEM EventID: WBEM ProviderName: XBC port with an unexpected neighbor chip type. Data field: (expected chip type) (actual chip type 16) (xbcnum 32) (portnum 48). Probable Cause: System firmware noticed a discrepancy from the expected topology of the system. Recommended Action: Capture IPMI event logs, look for additional errors. Contact your HP Support Representative to analyze the fabric. WBEM EventID: WBEM ProviderName: An XBC port was found to have an unexpected neighbor ID. Data field: (expected NID) (actual NID 16) (xbcnum 32) (portnum 48). Probable Cause: System firmware found a discrepancy in the expected topology of the system. Recommended Action: Capture IPMI event logs, look for additional errors. Contact your HP Support Representative to analyze the fabric. WBEM EventID: WBEM ProviderName: An XBC was found to have an unexpected neighbor port connection. Data field: (expected port) (actual port 16) (xbcnum 32) (portnum 48). Probable Cause: System firmware found a discrepancy in the expected topology of the system. Recommended Action: Capture IPMI event logs, look for additional errors. Contact your HP Support Representative to analyze the fabric. WBEM EventID: WBEM ProviderName: The expected data was not found in the Arches Fabric expected edge list. Data field is unused. Probable Cause: Internal system firmware error or data corruption. Recommended Action: Capture IPMI event logs, look for additional errors. Contact your HP Support Representative to analyze the fabric. WBEM EventID: WBEM ProviderName: An XBC port has an unexpected neighbor chip type. Data field: neighbor type found. Probable Cause: System firmware found an unexpected chip in the system. Recommended Action: Capture IPMI event logs, look for additional errors. Contact your HP Support Representative to analyze the fabric. WBEM EventID: WBEM ProviderName: A previously good XBC-XBC link was found to be down. Data field: (xbcnum 32) (portnum 48). Probable Cause: A link that was previously healthy was found to be down. Recommended Action: Capture IPMI event logs, look for additional errors. Contact your HP Support Representative to analyze the fabric. WBEM EventID: WBEM ProviderName: An XBC port was found to have a Fatal during traversability test. Data field: (xbcnum 32) (portnum 48). Probable Cause: A link was found to have fatal errors, possible bad link/connection. Recommended Action: Capture IPMI event logs, look for additional errors. Contact your HP Support Representative to analyze the fabric. WBEM EventID: WBEM ProviderName: 60 WBEM Provider Event Tables

61 Unable to read the local cell's LINK_SEL_FABRIC CSR. Data field: unused. Probable Cause: System firmware was unable to read a hardware register. Recommended Action: Capture IPMI event logs, look for additional errors. Contact your HP Support Representative to analyze the fabric. WBEM EventID: WBEM ProviderName: Unable to read the XBC route table. Data field: (route index) (xbcnum 32) (portnum 48). Probable Cause: System firmware was unable to read a fabric hardware register. Recommended Action: Capture IPMI event logs, look for additional errors. Contact your HP Support Representative to analyze the fabric. WBEM EventID: WBEM ProviderName: An XBC link was found to be not connected while testing CSR traffic traversability. Data field: (xbcnum 32) (portnum 48). Probable Cause: A previously healthy link was found to be down. Possible bad cable/connection. Recommended Action: Capture IPMI event logs, look for additional errors. Contact your HP Support Representative to analyze the fabric. WBEM EventID: WBEM ProviderName: reading Skyline ALREC_ALB_ID CSR. Data field: (Skyline port) (Cell number 56). Probable Cause: System firmware was unable to read a fabric hardware register. Recommended Action: Capture IPMI event logs, look for additional errors. Contact your HP Support Representative to analyze the fabric. WBEM EventID: WBEM ProviderName: A circular route was found while testing XBC CSR traffic traversability. Data field: (target XBC 32) (cellnum 56). Probable Cause: Internal firmware error, fabric was routed incorrectly. Recommended Action: Capture IPMI event logs, look for additional errors. Contact your HP Support Representative to analyze the fabric. WBEM EventID: WBEM ProviderName: reading ALREC_ALB_ID CSR for an XBC port. Data field: (xbcnum 32) (portnum 48). Probable Cause: System firmware was unable to read a fabric hardware register. Recommended Action: Capture IPMI event logs, look for additional errors. Contact your HP Support Representative to analyze the fabric. WBEM EventID: WBEM ProviderName: An XBC-XBC port had an invalid chip type connection. Data field: (expected chip type) (actual chip type 32). Probable Cause: System firmware found a discrepancy in the system topology. Recommended Action: Capture IPMI event logs, look for additional errors. Contact your HP Support Representative to analyze the fabric. WBEM EventID: WBEM ProviderName: ArfIsXbcRouteTraversable was called on a back-to-back system which is an improper use of the function. Data field: unused. Probable Cause: Internal firmware error. Recommended Action: Capture IPMI event logs, look for additional errors. Contact your HP Support Representative to analyze the fabric. WBEM EventID: WBEM ProviderName: In ArfIsXbcRouteTraversable, an XBC-XBC link was found to have fatal errors. Data field: (xbcnum 32) (portnum 48). Probable Cause: A previously healthy link was found to have fatal errors. Recommended Action: Capture IPMI event logs, look for additional errors. Contact your HP Support Representative to analyze the fabric. WBEM EventID: WBEM ProviderName: Unable to read the XBC ROUTE_TABLE_ENABLE_MASK CSR. Data field: (xbcnum 32) (portnum 48). Probable Cause: System firmware was unable to read a fabric hardware register. Recommended Action: Capture IPMI event logs, look for additional errors. Contact your HP Support Representative to analyze the fabric. WBEM EventID: WBEM ProviderName: reading an XBC ROUTE_TABLE CSR. Data field: route index (xbcnum 32) (portnum 48). Probable Cause: System firmware was unable to read a fabric hardware register. Recommended Action: Capture IPMI event logs, look for additional errors. Contact your HP Support Representative to analyze the fabric. WBEM EventID: WBEM ProviderName: Platform Events 61

62 reading ALB ALREC_ALB_ID CSR for an XBC port. Data field: (xbcnum 32) (portnum 48). Probable Cause: System firmware was unable to read a fabric hardware register. Recommended Action: Capture IPMI event logs, look for additional errors. Contact your HP Support Representative to analyze the fabric. WBEM EventID: WBEM ProviderName: An XBC port was found with an unexpected neighbor chip. Data field: expected chip type (actual chip type 32). Probable Cause: System firmware found a discrepancy in the expected system topology. Recommended Action: Capture IPMI event logs, look for additional errors. Contact your HP Support Representative to analyze the fabric. WBEM EventID: WBEM ProviderName: A cell/port pair was not found in the expected graph data. Data field: (cellnum 32) CC portnum. Probable Cause: Internal firmware error or data corruption. Recommended Action: Capture IPMI event logs, look for additional errors. Contact your HP Support Representative to analyze the fabric. WBEM EventID: WBEM ProviderName: Arches Fabric Traversability code unexpectedly found the local cell link not connected. Data field: linkstate (0 = connected, 1 = link pending, 2 = not connected, -1 = error). Probable Cause: A previously healthy link was found to have fatal errors. Recommended Action: Capture IPMI event logs, look for additional errors. Contact your HP Support Representative to analyze the fabric. WBEM EventID: WBEM ProviderName: reading the ROUTEx CSR on the XBC. Data field: route index (xbcnum 32) (portnum 48). Probable Cause: System firmware was unable to read a fabric hardware register. Recommended Action: Capture IPMI event logs, look for additional errors. Contact your HP Support Representative to analyze the fabric. WBEM EventID: WBEM ProviderName: Unable to read the ALB ALREC_ALB_ID CSR for an XBC port. Data field: (xbcnum 32) (portnum 48). Probable Cause: System firmware was unable to read a fabric hardware register. Recommended Action: Capture IPMI event logs, look for additional errors. Contact your HP Support Representative to analyze the fabric. WBEM EventID: WBEM ProviderName: An XBC port has an unexpected neighbor chip type. Data field: expected neighbor chip type (actual neighbor chip type 32). Probable Cause: System firmware found a discrepancy in the expected system topology. Recommended Action: Capture IPMI event logs, look for additional errors. Contact your HP Support Representative to analyze the fabric. WBEM EventID: WBEM ProviderName: A Cell-Cell link has an unexpected neighbor chip type. Data field: expected neighbor chip type (actual neighbor chip type 32). Probable Cause: System firmware has found a discrepancy in the expected system topology. Recommended Action: Capture IPMI event logs, look for additional errors. Contact your HP Support Representative to analyze the fabric. WBEM EventID: WBEM ProviderName: The cell/port pair does not exist in the Arches Fabric expected graph data. Data field: CC port (cellnum 32). Probable Cause: System firmware was unable to read a fabric hardware register. Recommended Action: Capture IPMI event logs, look for additional errors. Contact your HP Support Representative to analyze the fabric. WBEM EventID: WBEM ProviderName: A Cell-Cell link is connected to an unexpected neighbor port. Data field: expected neighbor port (actual neighbor port 32). Probable Cause: System firmware found a discrepancy in the expected system topology. Recommended Action: Capture IPMI event logs, look for additional errors. Contact your HP Support Representative to analyze the fabric. WBEM EventID: WBEM ProviderName: 62 WBEM Provider Event Tables

63 A Cell-Cell link is connected to an unexpected cell. Data field: expected neighbor ID (actual neighbor ID 16) (target cell 32) (local cell 48). Probable Cause: System firmware found a discrepancy in the expected system topology. Recommended Action: Capture IPMI event logs, look for additional errors. Contact your HP Support Representative to analyze the fabric. WBEM EventID: WBEM ProviderName: An EFI driver failed to load. Probable Cause: A reflashable EFI Driver has failed a checksum test. Recommended Action: Reflash the system firmware to correct this error. WBEM EventID: WBEM ProviderName: VM_FindAllRoutes returned an unexpected error during Non-Coherent table setup. Data field: (return value) (source cell 32) (target cell 48). Probable Cause: Internal firmware error or data corruption. Recommended Action: Capture IPMI event logs, look for additional errors. Contact your HP Support Representative to analyze the fabric. WBEM EventID: WBEM ProviderName: In SetupNCTable, a write to the GLOBAL_LINK_SEL_NONCOH CSR failed. Data field: (data written to CSR) (actual CSR data read 32). Probable Cause: System firmware was unable to write a fabric hardware register. Recommended Action: Capture IPMI event logs, look for additional errors. Contact your HP Support Representative to analyze the fabric. WBEM EventID: WBEM ProviderName: SetupNCTable failed in ArfPhase3. Data field: cell set passed in to SetupNCTable. Probable Cause: System firmware was unable to write some fabric hardware registers. Recommended Action: Capture IPMI event logs, look for additional errors. Contact your HP Support Representative to analyze the fabric. WBEM EventID: WBEM ProviderName: A failure occurred while prepping a back-to-back system for post-rendezvous Arches Fabric setup. Data field: return value from Phase4BackToBackPrep. Probable Cause: System firmware was unable to write various fabric hardware registers. Recommended Action: Capture IPMI event logs, look for additional errors. Contact your HP Support Representative to analyze the fabric. WBEM EventID: WBEM ProviderName: ArfPhase4 was unable to set up the Non-Coherent link select to at least one cell in its alive/gsm sharing set. Data field: bitmap of unreachable cells. Probable Cause: System firmware was unable to find valid routes to each cell in a previously good partition. Possible cable/connection problems. Recommended Action: Capture IPMI event logs, look for additional errors. Contact your HP Support Representative to analyze the fabric. WBEM EventID: WBEM ProviderName: Unable to set the Non-Coherent route. Data field: (sourcecell 32) (cell set passed in to SetupNCTable). Probable Cause: System firmware was unable to write various fabric hardware registers. Recommended Action: Capture IPMI event logs, look for additional errors. Contact your HP Support Representative to analyze the fabric. WBEM EventID: WBEM ProviderName: Unable to setup the Coherent route table for a cell in our partition. Data field: (sourcecell 32) (cell set passed in to SetupCohTable). Probable Cause: System firmware was unable to write various fabric hardware registers. Recommended Action: Capture IPMI event logs, look for additional errors. Contact your HP Support Representative to analyze the fabric. WBEM EventID: WBEM ProviderName: writing the XBC ROUTE_TABLE_ENABLE_MASK CSR. Data field: (route set to disable) (xbcnum 32) (xbc port 48). Probable Cause: System firmware was unable to write various fabric hardware registers. Recommended Action: Capture IPMI event logs, look for additional errors. Contact your HP Support Representative to analyze the fabric. WBEM EventID: WBEM ProviderName: Platform Events 63

64 The Arches Fabric vertex module returned an unexpected error during Non-Coherent table setup. Data field: (return value) (sourcecell 32) (dest cell 48). Probable Cause: Internal firmware error or data corruption. Recommended Action: Capture IPMI event logs, look for additional errors. Contact your HP Support Representative to analyze the fabric. WBEM EventID: WBEM ProviderName: A write to a Skyline Global LINK_SEL_COHx CSR failed. Data field: cell number of the Skyline that failed. Probable Cause: System firmware was unable to write a fabric hardware register. Recommended Action: Capture IPMI event logs, look for additional errors. Contact your HP Support Representative to analyze the fabric. WBEM EventID: WBEM ProviderName: Unable to write the XBC port scratch CSR with the routing state. Data field: (routing state) (xbcnum 32) (portnum 48). Probable Cause: System firmware was unable to write a fabric hardware register. Recommended Action: Capture IPMI event logs, look for additional errors. Contact your HP Support Representative to analyze the fabric. WBEM EventID: WBEM ProviderName: System Firmware was unable to access the configured set stored in the complex profile. Probable Cause: SFW was unable to access the configured set stored in the complex profile. Recommended Action: Collect IPMI events and contact your HP Support Representative. WBEM EventID: WBEM ProviderName: System Firmware detected an error during Fabric Init. Probable Cause: detected by SFW during Fabric Init. Recommended Action: Collect IMPI events and contact your HP Support Representative for assistance. WBEM EventID: WBEM ProviderName: System Firmware detected a failure during Fabric Init. Probable Cause: Failure detected by SFW during Fabric Init. Recommended Action: Collect IPMI events and contact your HP Support Representative for assistance. WBEM EventID: WBEM ProviderName: System Firmware detected an error during Fabric Optimize. Probable Cause: detected by SFW during Fabric Optimize. Recommended Action: Collect IMPI events and contact your HP Support Representative for assistance. WBEM EventID: WBEM ProviderName: Input power to the specified UPS has failed. WBEM EventID: WBEM ProviderName: Input power to the specified UPS has been restored. WBEM EventID: WBEM ProviderName: UPS power exhausted. The system is being powered down. WBEM EventID: WBEM ProviderName: During Machine Check handling, SAL failed to rendezvous all the processors. Probable Cause: System firmware cannot roundup the processors during the machine check handler. Recommended Action: Check for faulty processor, possibly the one(s) that failed to rendezvous. Contact your HP representative for support. WBEM EventID: WBEM ProviderName: SAL failed to clear the CEC logs during Machine check handling. Probable Cause: System firmware failed to clear the CEC logs. Recommended Action: Check for multiple errors or bad CEC. Contact your HP representative for support. WBEM EventID: WBEM ProviderName: SAL INIT failed to roundup the processors entering the SAL INIT handler. Probable Cause: System firmware failed to roundup the processor during the INIT handler. Recommended Action: Check for faulty processor, possibly the one(s) that failed to rendezvous. Contact your HP representative for support. WBEM EventID: WBEM ProviderName: System FW was unable to access the XBC semaphore. Probable Cause: System FW was unable to access the XBC semaphore. Recommended Action: Collect IPMI events, look for additional errors events, and contact HP support for assistance. WBEM EventID: WBEM ProviderName: 64 WBEM Provider Event Tables

65 System Firmware detected an error while trying to release the XBC Global Semaphore. Probable Cause: detected by SFW while trying to release the XBC Global Semaphore. Recommended Action: Collect IPMI events and contact your HP Support Representative. WBEM EventID: WBEM ProviderName: System Firmware detected an while checking the owner of the XBC Global Semaphore. Probable Cause: detected by SFW while checking the owner of the XBC Global Semaphore. Recommended Action: Collect IMPI events and contact your HP Support Representative. WBEM EventID: WBEM ProviderName: An error occurred while forming the XBC semaphore address. Probable Cause: Couldn't determine the proper address of the XBC semaphore. Recommended Action: Save IPMI event codes, contact HP Support Representative to analyze the fabric. WBEM EventID: WBEM ProviderName: reading the XBC Global Semaphore. Probable Cause: Couldn't read the XBC semaphore. Recommended Action: Look for additional IPMI event logs, contact your HP support representative to analyze the fabric. WBEM EventID: WBEM ProviderName: Failure to get the XBC Global Semaphore address. Probable Cause: Failed to get a fabric address. Recommended Action: Look for additional IPMI event logs. Contact your HP Support Representative to analyze the fabric. WBEM EventID: WBEM ProviderName: Failed to write the XBC Global Semaphore. Probable Cause: write to XBC failed. Recommended Action: Contact HP Support personnel to check the XBC. WBEM EventID: WBEM ProviderName: Failed to read the XBC Global Semaphore. Probable Cause: System Firmware was unable to release a XBC semaphore. Recommended Action: Collect IPMI Event Logs. Contact HP Support Representative to investigate the fabric. WBEM EventID: WBEM ProviderName: Failed to get the address of the XBC Global Semaphore. Probable Cause: Failed to get a fabric address. Recommended Action: Look for additional IPMI event logs. Contact your HP Support Representative to analyze the fabric. WBEM EventID: WBEM ProviderName: Failed to write the XBC Global Semaphore. Probable Cause: System Firmware was unable to release a XBC semaphore. Recommended Action: Collect IPMI Event Logs. Contact HP Support Representative to investigate the fabric. WBEM EventID: WBEM ProviderName: Failed to release the XBC Global Semaphore. Probable Cause: System Firmware was unable to release a XBC semaphore. Recommended Action: Collect IPMI Event Logs. Contact HP Support Representative to investigate the fabric. WBEM EventID: WBEM ProviderName: Fabric phases have been executed in an invalid order. Probable Cause: System firmware failed a validation check on its routing progress. Recommended Action: Collect all IPMI event logs, preferably live logs. Contact you HP Support Representative. WBEM EventID: WBEM ProviderName: Fabric phases have been executed in an invalid order. Data field indicates the expected phase. Probable Cause: System firmware failed a validation check on its routing progress. Recommended Action: Collect all IPMI event logs, preferably live logs. Contact you HP Support Representative. WBEM EventID: WBEM ProviderName: Failed to get an address when opening XBC to XBC links. Probable Cause: Failed to get a fabric address. Recommended Action: Look for additional IPMI event logs. Contact your HP Support Representative to analyze the fabric. WBEM EventID: WBEM ProviderName: Platform Events 65

66 Failed to open a fabric link. Probable Cause: System Firmware was unable to open the crossbar link. Recommended Action: Collect IPMI Event Logs. Contact your HP Support Representative to analyze the fabric. WBEM EventID: WBEM ProviderName: when writing the XBC return route. Probable Cause: write to XBC failed. Recommended Action: Contact HP Support personnel to check the XBC. WBEM EventID: WBEM ProviderName: enabling the XBC return route. Probable Cause: write to XBC failed. Recommended Action: Contact HP Support personnel to check the XBC. WBEM EventID: WBEM ProviderName: Failed to disperse the routes across links. Probable Cause: System Firmware was unable to route the crossbar fabric. Recommended Action: Collect IPMI Event logs. Contact your HP Support Representative to troubleshoot the fabric and/or backplane subsystem. WBEM EventID: WBEM ProviderName: setting up XBC-XBC link for routing across it. Probable Cause: System Firmware was unable to route the crossbar fabric. Recommended Action: Collect IPMI Event logs. Contact your HP Support Representative to troubleshoot the fabric and/or backplane subsystem. WBEM EventID: WBEM ProviderName: while routing the remote side of a route. Probable Cause: System Firmware was unable to route the crossbar fabric. Recommended Action: Collect IPMI Event logs. Contact your HP Support Representative to troubleshoot the fabric and/or backplane subsystem. WBEM EventID: WBEM ProviderName: getting address while routing the remote XBC. Probable Cause: Failed to get a fabric address. Recommended Action: Look for additional IPMI event logs. Contact your HP Support Representative to analyze the fabric. WBEM EventID: WBEM ProviderName: getting the neighbor info. Probable Cause: XBC register read failure. Recommended Action: Contact HP Support personnel to analyze the crossbar chip. WBEM EventID: WBEM ProviderName: finding the shortest route. Probable Cause: System Firmware encountered a problem while processing the crossbar fabric graphs. Recommended Action: Collect IPMI event logs. Contact your HP Support Representative to analyze the fabric. WBEM EventID: WBEM ProviderName: writing the remote XBC routing register. Probable Cause: write to XBC failed. Recommended Action: Contact HP Support personnel to check the XBC. WBEM EventID: WBEM ProviderName: enabling the routes on the remote XBC. Probable Cause: write to XBC failed. Recommended Action: Contact HP Support personnel to check the XBC. WBEM EventID: WBEM ProviderName: writing the routing register on the local XBC. Probable Cause: write to XBC failed. Recommended Action: Contact HP Support personnel to check the XBC. WBEM EventID: WBEM ProviderName: writing the local XBC routing registers to reach a remote cell. Probable Cause: write to XBC failed. Recommended Action: Contact HP Support personnel to check the XBC. WBEM EventID: WBEM ProviderName: enabling the local XBC routes. Probable Cause: write to XBC failed. Recommended Action: Contact HP Support personnel to check the XBC. WBEM EventID: WBEM ProviderName: SynchGraphs() failed during Arches Fabric Phase 4. Data field: return value from SynchGraphs(). Probable Cause: Internal firmware error or data corruption. Recommended Action: Capture IPMI event logs, look for additional errors. Contact your HP Support Representative to analyze the fabric. WBEM EventID: WBEM ProviderName: 66 WBEM Provider Event Tables

67 VM_DeleteVertex() failed in SynchGraphs(). Data field: (vertex id 32) (vertex type 56) (return value from VM_DeleteVertex()). Probable Cause: Internal firmware error or data corruption. Recommended Action: Capture IPMI event logs, look for additional errors. Contact your HP Support Representative to analyze the fabric. WBEM EventID: WBEM ProviderName: VM_DeleteEdge() failed in the Arches Fabric function SynchGraphs(). Data field:(vertex id1 32) (vertex port1 48) (vertex type1 56) (vertex id2 0) (vertex port2 16) (vertex type2 24). Probable Cause: Internal firmware error or data corruption. Recommended Action: Capture IPMI event logs, look for additional errors. Contact your HP Support Representative to analyze the fabric. WBEM EventID: WBEM ProviderName: Unexpected error when calling an Arches Fabric vertex module function. Data field: return value from vertex module function. Probable Cause: Internal firmware error or data corruption. Recommended Action: Capture IPMI event logs, look for additional errors. Contact your HP Support Representative to analyze the fabric. WBEM EventID: WBEM ProviderName: Unexpected return from an Arches Fabric vertex module function while copying a cell's graph. Data field: return value from vertex module function. Probable Cause: Internal firmware error or data corruption. Recommended Action: Capture IPMI event logs, look for additional errors. Contact your HP Support Representative to analyze the fabric. WBEM EventID: WBEM ProviderName: The checksum update for the PDT has failed. Probable Cause: The call to update the checksum for the PDT failed. The PDT will most likely be cleared upon reboot. Recommended Action: Reboot Upgrade SFW Contact HP support. WBEM EventID: WBEM ProviderName: The checksum in the memory area of NVM is bad. Probable Cause: The checksum in the memory area of NVM is bad. Recommended Action: Upgrade SFW Contact HP support. WBEM EventID: WBEM ProviderName: Checksum calculation failed. Probable Cause: The checksum calculation failed. The data field contains the address that the checksum calculation was attempted on. Recommended Action: Upgrade SFW Contact HP support. WBEM EventID: WBEM ProviderName: Both SAL's copy and BMC copy of the token specified in the data field is bad. Probable Cause: Both SAL's copy and BMC copy of the token specified in the data field is bad. SFW is reinitializing that token to it's default value. Recommended Action: Verify that the default settings are appropriate. For example, run the EFI baud and boot test command. WBEM EventID: WBEM ProviderName: Incompatible I/O Backplane or I/O cables installed. Probable Cause: Incorrect I/O backplane and/or I/O backplane cables are connected to the cell board. The cell board is not compatible with I/O backplane and/or I/O backplane cables. Recommended Action: Remove I/O backplane and/or I/O backplane cables and replace with compatible I/O backplane and/or I/O backplane cables. WBEM EventID: WBEM ProviderName: The fpar identified by the event detail will be unusable. Probable Cause: Firmware ran out of NVRAM before the server completed cold boot initialization. Recommended Action: Initialize the NVRAM to the factory defaults and reset the server. Soft partitions will have to be recreated from scratch before they are available. WBEM EventID: WBEM ProviderName: Firmware is out of NVRAM and cannot built the ILM memory slice device map. Probable Cause: Firmware ran out of NVRAM before the server completed cold boot initialization. Recommended Action: Initialize the NVRAM to the factory defaults and reset the server. Soft partitions will have to be recreated from scratch before they are available. WBEM EventID: WBEM ProviderName: The NVRAM for the CPU map is corrupt and cannot be trusted. It appears that there are more CPUs in the map than the size of the map can hold. Probable Cause: This should not show up and Firmware should have resolved this. WBEM EventID: WBEM ProviderName: Platform Events 67

68 The NVRAM for the IO device ownership map is corrupt and cannot be trusted. It appears that there are more IO devices in the map than the size of the map can hold. Probable Cause: NVRAM corruption of fpars specific database. Recommended Action: Restore NVRAM to factory defaults. Reset server and reconfigure soft partitions. WBEM EventID: WBEM ProviderName: The NVRAM for the cell local memory map is corrupt and cannot be trusted. It appears that there are more memory slices in the map than the size of the map can hold. Probable Cause: NVRAM corruption of fpars specific database. Recommended Action: Restore NVRAM to factory defaults. Reset server and reconfigure soft partitions. WBEM EventID: WBEM ProviderName: An internal firmware inconsistency exists or the server exhausted its internal resources and is unable to create an fpars EFI ownership variable for a CPU device in the partition. Either of these conditions is fatal. Probable Cause: NVRAM corruption of fpars specific database. Recommended Action: Restore NVRAM to factory defaults. Reset server and reconfigure soft partitions. WBEM EventID: WBEM ProviderName: An internal firmware inconsistency exists or the server exhausted its internal resources and is unable to create an fpars EFI ownership variable for an IO device in the partition. Either of these conditions is fatal. Probable Cause: NVRAM corruption of fpars specific database. Recommended Action: Restore NVRAM to factory defaults. Reset server and reconfigure soft partitions. WBEM EventID: WBEM ProviderName: An internal firmware inconsistency exists or the server exhausted its internal resources and is unable to create an fpars EFI ownership variable for a CLM device in the partition. Either of these conditions is fatal. Probable Cause: NVRAM corruption of fpars specific database. Recommended Action: Restore NVRAM to factory defaults. Reset server and reconfigure soft partitions. WBEM EventID: WBEM ProviderName: Firmware has run out of NVRAM and cannot create the needed variable(s). Probable Cause: NVRAM is too full for operation. Recommended Action: Delete some EFI variables in existing fpars or boot in npars mode and delete some variables. (E.g., too many boot paths in the boot manager can cause this). Clear NVRAM and reconfigure system. WBEM EventID: WBEM ProviderName: The call to the IOC firmware component method 'LbaReconfig' failed, probably a low-level hardware error. The fpar BSP is identified in bits of the event detail, the fpar owning this CPU and LBA is identified in bits Probable Cause: Low level IO hw initialization of an LBA by the firmware failed during an fpar reset. Recommended Action: Try booting npars mode. Power cycle the hardware. replace the LBA. WBEM EventID: WBEM ProviderName: Invocation of the soft reset code from an interrupt or similar vector,. Probable Cause: An error in the system firmware. Recommended Action: Reset the npar. WBEM EventID: WBEM ProviderName: Data field is count of cpus held by the sm4 which issues the event (and is trying to reset itself). Indicates invocation of the SoftResetCpu code from an interrupt or similar vector. Probable Cause: An error in the system firmware. Recommended Action: Reset the npar. WBEM EventID: WBEM ProviderName: A reset of an fpar discovered that an fpar failed to release critical resources within a reasonable time. Probable Cause: Fpar reset to an Fpar which failed to release critical resources within a reasonable time. Recommended Action: No action is required. The npar will be rebooted. WBEM EventID: WBEM ProviderName: Significant numbers of corrected memory errors have been detected on the memory subsystem. Probable Cause: You will receive this message if the system is observing a lot of corrected ECC errors in memory. This could be caused by problems with the system's memory or by unexpected environmental conditions inside the server. Recommended Action: Contact your HP support representative to check your memory system. WBEM EventID: WBEM ProviderName: 68 WBEM Provider Event Tables

69 Over-temperature condition detected on a processor. Probable Cause: The processor temperature is above the operating range. The processor's performance is throttled by the firmware to reduce the temperature. Recommended Action: The firmware has already taken necessary action. Once the temperature comes down, the firmware will restore the processor's performance to normal. WBEM EventID: WBEM ProviderName: Cache errors detected on a processor. Probable Cause: Threshold parity errors have been detected in the Instruction or Data Cache Memory (I-Cache or D-Cache). The operating system has recovered from the errors, but this is an abnormally high failure rate. Recommended Action: Contact your HP support representative to check the processor. WBEM EventID: WBEM ProviderName: Corrected errors detected in the cache portion of the memory for a processor module. Probable Cause: Threshold corrected platform errors have been detected in the cache portion of the memory for the processor module. The operating system has recovered from the errors, but this is an abnormally high failure rate. Recommended Action: Contact your HP support representative to check the processor. WBEM EventID: WBEM ProviderName: Corrected errors detected on the system bus for a processor module. Probable Cause: Threshold corrected platform errors have been detected on the system bus for the processor module. The operating system has recovered from the errors, but this is an abnormally high failure rate. Recommended Action: Contact your HP support representative to check the processor module or the system bus for the processor if an excessive number of these errors are generated. WBEM EventID: WBEM ProviderName: Corrected errors detected on the processor bus for a processor module. Probable Cause: Threshold corrected platform errors have been detected on the processor bus for the processor module. The operating system has recovered from the errors, but this is an abnormally high failure rate. Recommended Action: Contact your HP support representative to check the processor module or the system bus for the processor if an excessive number of these errors are generated. WBEM EventID: WBEM ProviderName: Corrected errors detected in the tag portion of the memory for a processor module. Probable Cause: Threshold corrected platform errors have been detected in the tag portion of the memory for the processor module. The operating system has recovered from the errors, but this is an abnormally high failure rate. Recommended Action: Contact your HP support representative to check the processor module if an excessive number of these errors are generated. WBEM EventID: WBEM ProviderName: fpars-mode EFI variable is set to enable fpars operation but no fpars are actually enabled to boot. So the server boots in hard partition mode. Probable Cause: fpars-mode EFI variable is set to enable fpars operation but no fpars are actually enabled to boot. So the server boots in hard partition mode. This is a configuration usage problem, possibly a user error such as might occur if a previously bootable config was made unbootable by setting the enabled fpar existence variables, e.g., 'fpar0', 'fpar1',... 'fparn' to 0x00 (disabled) and then rebooting. Recommended Action: Use the configuration tool released with the OS to disable fpars mode or to configure and enable bootable fpars. WBEM EventID: WBEM ProviderName: An fpar was directed to reset using the ESIT DirectedfParResetAndMigrate() service but the target (recipient) fpar of the resources is in a state that cannot receive ownership of these resources. Probable Cause: An fpar was directed to reset using the ESIT DirectedfParResetAndMigrate() service but the target (recipient) fpar of the resources is in a state that cannot receive ownership of these resources. Recommended Action: Use the configuration tool released with the OS to correctly assign these resources to an fpar and reset that fpar so they will be claimed. WBEM EventID: WBEM ProviderName: Platform Events 69

70 Firmware error setting the NVRAM value of preferred-bsp for the vpars monitor. The partition will boot using the PD monarch, but the value of preferred-bsp may not match this CPU. Probable Cause: Firmware could not store to the NVRAM holding the EFI preferred-bsp variable. Recommended Action: Reset the server, restore factory default NVRAM and reconfigure soft partitions. WBEM EventID: WBEM ProviderName: Unable to write to an XBC port ROUTE_TABLE_ENABLE_MASK CSR in Arches Fabric Phase3. Data field: (XBC port 48) (XBC ID 32) (route). Probable Cause: System firmware was unable to write a fabric hardware register. Recommended Action: Capture IPMI event logs, look for additional errors. Contact your HP Support Representative to analyze the fabric. WBEM EventID: WBEM ProviderName: An unrecoverable processor interrupt occurred. IPF firmware owned the processor interrupt vector table (IVT) at the time of the interrupt. Probable Cause: Probable bug in System Firmware, EFI driver, EFI app or OS loader (prior to OS launch). The event data field contains the IVT offset applicable to the interrupt. See table 5-7 (Interruption Vector Table) in the Intel ASDM Volume 2. Recommended Action: Provide console log containing register dump to HP Customer Engineer. WBEM EventID: WBEM ProviderName: SBA call to LBA SetDeviceMask method fails. Probable Cause: SBA call to LBA SetDeviceMask method fails. Recommended Action: Disable rope in non-mca path, error exit in MCA path. WBEM EventID: WBEM ProviderName: LBA slot device scan error. Probable Cause: The LBA component detected a card in a PCI slot, but got no response from config register requests to the card. Recommended Action: Reseat or replace the PCI card. WBEM EventID: WBEM ProviderName: There is none (or inadequate) memory slice resource assigned to the fpar so it cannot boot its instance. The fpar will be disabled (enter a spinloop) because it cannot boot, or if in vpars mode will return control to the monitor. Probable Cause: There is no Memory owned by the soft partition (fpar) whose CPU emitted this event. Recommended Action: Reconfigure the soft partition containing the CPU that emitted this event and be sure to give memory resources to that soft partition before reset of that partition. Until doing so, this soft partition will be unbootable and emit this event on each attempt. WBEM EventID: WBEM ProviderName: Couldn't collect vertex information during Fabric Info call. Data Field: return status. Probable Cause: There was a problem while collecting a list of fabric link info. Recommended Action: Look for additional IPMI event logs. Contact your HP Support Representative to analyze the fabric. WBEM EventID: WBEM ProviderName: Couldn't collect the vertices during the Fabric Info call. Data Field: number of vertices returned. Probable Cause: An invalid number of fabric vertices was found while collecting fabric information. Recommended Action: Fabric information cannot be reported properly. Collect IPMI Event logs and contact your HP Support Representative. WBEM EventID: WBEM ProviderName: Couldn't find all the edges during a procedure call. Data Field: return status. Probable Cause: There was a problem while collecting a list of fabric link info. Recommended Action: Look for additional IPMI event logs. Contact your HP Support Representative to analyze the fabric. WBEM EventID: WBEM ProviderName: Couldn't find an appropriate number of edges during a procedure call. Data Field: the number of edges found. Probable Cause: There was a problem while collecting a list of fabric link info. Recommended Action: Look for additional IPMI event logs. Contact your HP Support Representative to analyze the fabric. WBEM EventID: WBEM ProviderName: 70 WBEM Provider Event Tables

71 Too many edges were encountered during a procedure call. Data Field: link count. Probable Cause: There was a problem while collecting a list of fabric link info. Recommended Action: Look for additional IPMI event logs. Contact your HP Support Representative to analyze the fabric. WBEM EventID: WBEM ProviderName: Failed to get an address during a procedure call. Data Field: return status. Probable Cause: Failed to get a fabric address. Recommended Action: Look for additional IPMI event logs. Contact your HP Support Representative to analyze the fabric. WBEM EventID: WBEM ProviderName: An unexpected state was encountered during a procedure call. Data Field: state returned. Probable Cause: System Firmware encountered an unknown fabric link state. Recommended Action: Capture IPMI event logs. Contact your HP Support Representative to analyze the fabric link. WBEM EventID: WBEM ProviderName: Unable to get the link health state during a procedure call. Data Field: return status. Probable Cause: System Firmware was unable to read the fabric port's Fatal state. The link may or may not be in error. Recommended Action: Collect IPMI event logs for further details. Contact your HP Support Representative to analyze the fabric. WBEM EventID: WBEM ProviderName: The fabric data failed a CRC check. Data Field: (xbc port 44 ) (xbc 32) return status). Probable Cause: The fabric data structure may have been corrupted. Recommended Action: Collect IPMI event logs. Contact your HP support representative to investigate the health of the system. WBEM EventID: WBEM ProviderName: VM_CollectVertices failed unexpectedly. Could possibly be a data corruption problem. Data field: (cell number 56) (return value from VM_CollectVertices). Probable Cause: An error occurred while routing the fabric, possible data corruption or firmware error. Recommended Action: Contact your HP support representative to inspect the fabric and system firmware. WBEM EventID: WBEM ProviderName: Unable to generate an ALB address in Arches Fabric ArfSetDefaultCSRs() function. Data field:(cell number 56) (port number 48) (xbc ID 32) (return value). Probable Cause: An error occurred while routing the fabric, possible data corruption or firmware error. Recommended Action: Contact your HP support representative to inspect the fabric and system firmware. WBEM EventID: WBEM ProviderName: SetDefaultCSRs function failed unexpectedly. Arches Fabric was unable to set XBC CSRs to default values. Data field: return value from SetDefaultCSRs. Probable Cause: An error occurred while routing the fabric. Recommended Action: Collect IPMI event logs, and contact your HP support representative to inspect the fabric and system firmware. WBEM EventID: WBEM ProviderName: A problem was encountered while routing which prevented an appropriate route from being chosen. Data Field: Destination Cell 56 XBC Port 44 XBC # 32 return status. Probable Cause: An error occurred while routing the fabric. Recommended Action: Contact your HP support representative to inspect the fabric and system firmware. WBEM EventID: WBEM ProviderName: An error was encountered while routing the fabric. This error prevents an appropriate route from being selected. Data Field: Destination Cell 56 XBC Port 44 XBC # 32 return status. Probable Cause: An error occurred while routing the fabric. Recommended Action: Contact your HP support representative to inspect the fabric and system firmware. WBEM EventID: WBEM ProviderName: An error was encountered while routing the fabric. This error prevents an appropriate route from being selected. Data Field: Destination Cell 56 XBC Port 44 XBC # 32 return status. Probable Cause: An error occurred while routing the fabric. Recommended Action: Contact your HP support representative to inspect the fabric and system firmware. WBEM EventID: WBEM ProviderName: Platform Events 71

72 An invalid port number was returned when selecting a route for the XBC-CC link. Data Field: (destination cell 56) (xbc port 44) (xbc # 32) port selected. Probable Cause: An error occurred while routing the fabric. Recommended Action: Contact your HP support representative to inspect the fabric and system firmware. An error was encountered while routing the fabric. This error prevents an appropriate route from being selected. Data Field: Destination Cell 56 XBC Port 44 XBC # 32 switch fabric. Probable Cause: An error occurred while routing the fabric. Recommended Action: Contact your HP support representative to inspect the fabric and system firmware. WBEM EventID: WBEM ProviderName: The second flash part is not programmed with a valid image. WBEM EventID: WBEM ProviderName: System backplane power has reported a 1.2v LDO fault. The data field contains the physical location of the fault. Probable Cause: System backplane power board has reported a 1.2v LDO fault. Recommended Action: Check system backplane. WBEM EventID: WBEM ProviderName: System backplane power has reported a 2.5v LDO fault. The data field contains the physical location of the fault. Probable Cause: System backplane power board has reported a 2.5v LDO fault. Recommended Action: Check system backplane. WBEM EventID: WBEM ProviderName: System backplane power has reported a 3.3v house keeping power fault. The data field contains the physical location of the fault. Probable Cause: System backplane power board has reported a 3.3v house keeping fault. Recommended Action: Check system backplane power board. WBEM EventID: WBEM ProviderName: System backplane power has reported a 12v power fault. The data field contains the physical location of the fault. Probable Cause: System backplane power board has reported a 12v fault. Recommended Action: Check system backplane power board. WBEM EventID: WBEM ProviderName: System backplane power has reported a 3.3v power fault. The data field contains the physical location of the fault. Probable Cause: System backplane power board has reported a 3.3v fault. Recommended Action: Check system backplane power board. WBEM EventID: WBEM ProviderName: System backplane power has reported a 1.5v power fault. The data field contains the physical location of the fault. Probable Cause: System backplane power board has reported a 1.5v fault. Recommended Action: Check system backplane power board. WBEM EventID: WBEM ProviderName: System backplane power has reported a 2.5v power fault. The data field contains the physical location of the fault. Probable Cause: System backplane power board has reported a 2.5v fault. Recommended Action: Check system backplane power board. WBEM EventID: WBEM ProviderName: One or more power rails is providing insufficient power to the backplane. Probable Cause: There has been multiple faults on the same power rail. Recommended Action: look for additional events describing action to take. WBEM EventID: WBEM ProviderName: Clock fault for clocks supplied from the Redundant Clock Source (RCS) board to the system backplane. RCS board is no longer providing clocks to the backplane. The data field contains the physical location of the RCS. Probable Cause: RCS assembly has reported a fault. Recommended Action: Check RCS assembly. WBEM EventID: WBEM ProviderName: Clock fault for clocks supplied from the Hot Swap Oscillator (HSO) board to the system backplane. HSO has reported a fault or has been removed. The data field contains the physical location of the HSO. Probable Cause: HSO assembly has reported a fault or has been removed. Recommended Action: Check HSO assembly. WBEM EventID: WBEM ProviderName: 72 WBEM Provider Event Tables

73 The operational clock frequencies do not match between the Redundant Clock Source (RCS) and the Hot Swap Oscillator (HSO). The data field contains the physical location of the HSO. Probable Cause: Operating frequency of the HSO does not match that of the RCS. Recommended Action: Check HSO assembly. WBEM EventID: WBEM ProviderName: The clock margin of the system backplane failed. WBEM EventID: WBEM ProviderName: System backplane Hot Swap Oscillator (HSO) boards are NOT redundant. Probable Cause: HSO assembly has been removed or has a fault condition. Recommended Action: look for additional events describing action to take. WBEM EventID: WBEM ProviderName: System backplane Hot Swap Oscillator (HSO) boards are insufficient. Probable Cause: There are no HSO present or all clock sources have faulted. Recommended Action: Look for additional events describing action to take. WBEM EventID: WBEM ProviderName: Failure reading Redundant Clock Source (RCS) or Hot Swap Oscillator HSO boards EEPROM. Probable Cause: device is not accessible over i2c. Recommended Action: check HSO + RCS boards. WBEM EventID: WBEM ProviderName: Failure writing Redundant Clock Source (RCS) or Hot Swap Oscillator HSO boards EEPROM. Probable Cause: device is not accessible over i2c. Recommended Action: check HSO and RCS boards. WBEM EventID: WBEM ProviderName: Failure reading the Reset and Power Monitors (RPM) EEPROM. Probable Cause: device is not accessible over i2c. Recommended Action: check backplane power. WBEM EventID: WBEM ProviderName: Failure writing the Reset and Power Monitors (RPM) EEPROM. Probable Cause: device is not accessible over i2c. Recommended Action: check backplane power. WBEM EventID: WBEM ProviderName: Failure reading the Onboard System Programmers (OSP) EEPROM. Probable Cause: device is not accessible over i2c. Recommended Action: check backplane power. WBEM EventID: WBEM ProviderName: Failure writing the Onboard System Programmers (OSP) EEPROM. Probable Cause: device is not accessible over i2c. Recommended Action: check backplane power. WBEM EventID: WBEM ProviderName: SBS fault on startup. Probable Cause: SBS block for one of the MOAB's has reported an error on startup. Recommended Action: check backplane power. The physical location of the MOAB reporting the error is provided by data field. 0xFFFFXXFFFFFFFFFF where XX is: XX = 0x00 - Moab 0x00 XX = 0x01 - Moab 0x01 XX = 0x02 - Moab 0x02 XX = 0x10 - Moab 0x40 XX = 0x11 - Moab 0x41 XX = 0x12 - Moab 0x42. WBEM EventID: WBEM ProviderName: Failure reading IO backplane LPM. Probable Cause: IO backplane LPM is not accessible over i2c. Recommended Action: Check power status of IO backplane. WBEM EventID: WBEM ProviderName: Failure writing IO backplane LPM. Probable Cause: IO Backplane LPM is not accessible over i2c. Recommended Action: Check power status of IO backplane. WBEM EventID: WBEM ProviderName: The system software violated one of the 'well-behavedness' rules of soft partitions and tried to call a firmware procedure within the firmware instance of a sibling. This is an access violation and firmware rejects the call. Probable Cause: System Software Defect - using the wrong entry address for the owner of the CPU. Recommended Action: Update the system software. WBEM EventID: WBEM ProviderName: Platform Events 73

74 AlbInitPrep was unable to read the ALREC_CONFIG CSR to determine whether the link is up or not. Data field: unused. Probable Cause: An error occurred while routing the fabric. Recommended Action: Collect IPMI event logs, and contact your HP support representative to inspect the fabric and system firmware. WBEM EventID: WBEM ProviderName: The fpar whose ID is identified in the event detail is disabled from booting because it has no bootable, healthy CPU. It may not own any CPU or the CPUs it owns are Unhealthy (or deconfigured). Probable Cause: The fpar whose ID is identified in the event detail is disabled from booting because it has no bootable, healthy CPU. It may not own any CPU or the CPUs it owns are Unhealthy (or deconfigured). Recommended Action: Use the soft partitioning configuration tool released with the OS product to reconfigure the fpar and reboot the partition. A cold reset of the hard partition may be required. WBEM EventID: WBEM ProviderName: Non-critical event announces that an fpar is enabled to boot but has inadequate memory resources to instantiate the firmware for the fpar. The configuration is modified to disable but not delete this fpar. Probable Cause: The user has configured an fpar to be booted with inadequate memory resources to instantiate the firmware image for this fpar. The fpar is software deconfigured (disabled) from booting. Recommended Action: Reconfigure the fpar, giving it at least instance-size (an fpars EFI variable) amount of physically contiguous RAM. Then re-enable and reset the fpar. WBEM EventID: WBEM ProviderName: The fpar has been enabled to boot, and contains at least one CPU and adequate memory but has not been given any IO resources. It must be reconfigured and reset before it may boot an operating system. Probable Cause: The fpar has been enabled to boot, and contains at least one CPU and adequate memory but has not been given any IO resources. The soft partition (fpar) may therefore only boot as far as the EFI shell. It must be reconfigured and reset before it may boot an operating system. Recommended Action: Reconfigure the soft partition using an Operating-system-specific utility then reset the soft partition. WBEM EventID: WBEM ProviderName: All processors are scheduled for deconfiguration. Probable Cause: All CPUs were scheduled to be deconfigured through a combination of user deconfigures and/or failures. Recommended Action: No action is required. WBEM EventID: WBEM ProviderName: Processors have been reconfigured due to installation of a new processor type, or SFW revision change. Probable Cause: Either all CPUs were slated for deconfiguration, or NVM has been cleared, or a new CPU type has been installed. Recommended Action: No action is required. WBEM EventID: WBEM ProviderName: IO Backplane 1.5V power fault. Probable Cause: One of the 1.5v VRM's is reporting a fault, one failure and power state is N, after two power state will be N-. Recommended Action: Check IO backplane power board faulted VRM is give by PS command. WBEM EventID: WBEM ProviderName: IO Backplane 3.3V power fault. Probable Cause: One of the 3.3v VRM's is reporting a fault, one failure and power state is N, after two power state will be N-. Recommended Action: Check IO backplane power board faulted VRM is give by PS command. WBEM EventID: WBEM ProviderName: IO Backplane 5.0V power fault. Probable Cause: One of the 5.0v VRM's is reporting a fault, one failure and power state is N, after two power state will be N-. Recommended Action: check IO backplane power board faulted VRM is give by PS command. WBEM EventID: WBEM ProviderName: IO Backplane -12V power fault. Probable Cause: One of the -12v VRM's is reporting a fault, one failure and power state is N, after two power state will be N-. Recommended Action: Check IO backplane power board faulted VRM is give by PS command. WBEM EventID: WBEM ProviderName: 74 WBEM Provider Event Tables

75 IO Backplane +12V power fault. Probable Cause: One of the +12v VRM's is reporting a fault. One failure and power state is N, after two power state will be N-. Recommended Action: Check IO backplane power board. Faulted VRM is given by PS command. WBEM EventID: WBEM ProviderName: IO Backplane 1.5V temperature fault. Probable Cause: One of the 1.5v VRM's is over temp. Recommended Action: Check IO backplane power board faulted VRM is give by PS command. WBEM EventID: WBEM ProviderName: IO Backplane 3.3V temperature fault. Probable Cause: One of the 3.3v VRM's is over temp. Recommended Action: Check IO backplane power board faulted VRM is give by PS command. WBEM EventID: WBEM ProviderName: IO Backplane 5.0V temperature fault. Probable Cause: One of the 5.0v VRM's is over temp. Recommended Action: Check IO backplane power board faulted VRM is give by PS command. WBEM EventID: WBEM ProviderName: IO Backplane -12.0V temperature fault. Probable Cause: One of the -12v VRM's is over temp. Recommended Action: Check IO backplane power board faulted VRM is give by PS command. WBEM EventID: WBEM ProviderName: IO Backplane +12.0V temperature fault. Probable Cause: One of the +12v VRM's is over temp and has shutdown. One failure and the Redundancy state is 'not redundant', after two power faults the redundancy state is 'insufficient'. Recommended Action: Check IO backplane power board. Faulted VRM is given by PS command. WBEM EventID: WBEM ProviderName: The local cell was unable to clear the link_off bit on at least one CC-CC link. Data field: return value of Phase3BackToBackPrep(). Probable Cause: An error occurred while routing the fabric. Recommended Action: Collect IPMI event logs, and contact your HP support representative to inspect the fabric and system firmware. WBEM EventID: WBEM ProviderName: ArfOLAPreRendez() was unable to reach the added cell. Data field: bitmap of unreachable cells. Probable Cause: Firmware was unable to find a valid route to a cell being added by OLA. Recommended Action: Collect IPMI event logs, and contact your HP support representative to inspect the fabric and system firmware. WBEM EventID: WBEM ProviderName: An unexpected error occurred in SetupNCTable(). Data field: return value from SetupNCTable(). Probable Cause: An error occurred while routing the fabric. Recommended Action: Collect IPMI event logs, and contact your HP support representative to inspect the fabric and system firmware. WBEM EventID: WBEM ProviderName: Phase4BackToBackPrep() unexpectedly failed. Data field: return value of Phase4BackToBackPrep(). Probable Cause: An error occurred while routing the fabric. Recommended Action: Collect IPMI event logs, and contact your HP support representative to inspect the fabric and system firmware. WBEM EventID: WBEM ProviderName: Unable to synch graphs between all cells in the partition after an OLA. Data field: (master cell number 56) (bitmap of cells to synch). Probable Cause: An error occurred while routing the fabric. Recommended Action: Collect IPMI event logs, and contact your HP support representative to inspect the fabric and system firmware. WBEM EventID: WBEM ProviderName: Data field: bitmap of unreachable cells. Probable Cause: An error occurred while routing the fabric. Recommended Action: Collect IPMI event logs, and contact your HP support representative to inspect the fabric and system firmware. WBEM EventID: WBEM ProviderName: Platform Events 75

76 An unexpected error occurred while setting up the Non-Coherent or Coherent tables after an OLA. Data field: return value from SetupNCTable() or SetupCohTable(). Probable Cause: An error occurred while routing the fabric. Recommended Action: Collect IPMI event logs, and contact your HP support representative to inspect the fabric and system firmware. WBEM EventID: WBEM ProviderName: ArfRouteEnable() returned an unexpected error while enabling routes to the local cell. Data field: (local cell number 56) (bitmap of routes to enable). Probable Cause: An error occurred while routing the fabric. Recommended Action: Collect IPMI event logs, and contact your HP support representative to inspect the fabric and system firmware. WBEM EventID: WBEM ProviderName: ArfRouteDiable() returned an unexpected error while disabling routes during an OLA operation. Data field: (bitmap of cells 32) (bitmap of routes to disable). Probable Cause: An error occurred while routing the fabric. Recommended Action: Collect IPMI event logs, and contact your HP support representative to inspect the fabric and system firmware. WBEM EventID: WBEM ProviderName: ArfRouteDiable() returned an unexpected error while disabling routes in ArfPhase4. Data field: (bitmap of source cells 32) (bitmap of routes to disable). Probable Cause: An error occurred while routing the fabric. Recommended Action: Collect IPMI event logs, and contact your HP support representative to inspect the fabric and system firmware. WBEM EventID: WBEM ProviderName: SetupInitialCohTables() returned an error. Data field: (cell set 32) (return value from SetupInitialCohTables()). Probable Cause: An error occurred while routing the fabric. Recommended Action: Collect IPMI event logs, and contact your HP support representative to inspect the fabric and system firmware. WBEM EventID: WBEM ProviderName: Stable store read or write to flash failed. Probable Cause: Soft error Flash part Failure. Recommended Action: Reboot, if problem persists, contact HP support. WBEM EventID: WBEM ProviderName: reading or writing the stable store NVM area. Probable Cause: A read/write to the NVM stable storage area failed. Recommended Action: Reboot, if problem persists, contact HP support. WBEM EventID: WBEM ProviderName: FW has detected an illegal memory config using 4GB DIMMs. The system will be halted. Probable Cause: An unsupported memory configuration with 4GB DIMMs is installed in the system. Recommended Action: Refer to the user documentation to determine the supported memory configurations with 4GB DIMMs. WBEM EventID: WBEM ProviderName: SFW failed to allocate enough NVM to store all required data. Probable Cause: Not enough space allocated to store all required data in NVM. Recommended Action: Upgrade FW Contact HP support. WBEM EventID: WBEM ProviderName: SFW failed to allocate enough SCR RAM to store all required data. Probable Cause: SFW component does not allocate enough space in the SCR RAM for store it data. Recommended Action: Update SFW. Contact your HP representative for support. WBEM EventID: WBEM ProviderName: SetupIntialCohTables() returned an error in ArfPhase3. Data field: cell set [63:32], return value [31:0]. Probable Cause: An error occurred while routing the fabric. Recommended Action: Collect IPMI event logs, and contact your HP support representative to inspect the fabric and system firmware. WBEM EventID: WBEM ProviderName: writing the error masks for ALREC and ALTRAN. Data field: cell ID [63:56], port num [55:44], XBC ID [43:32]. Probable Cause: An error occurred while routing the fabric. Recommended Action: Collect IPMI event logs, and contact your HP support representative to inspect the fabric and system firmware. WBEM EventID: WBEM ProviderName: 76 WBEM Provider Event Tables

77 The allocation of the ACPI memory buffer failed. Probable Cause: SFW was unable to allocate the needed memory space for ACPI tables. Recommended Action: In fpars/vpars mode, the memory slice size may need to be increased. In npars mode, SFW has an error causing there to not be enough memory. WBEM EventID: WBEM ProviderName: Firmware had an unexpected internal error from the vertex module.. Data field: vtype1 [63:56] vport1 [55:48] vid1 [47:32] vtype2 [31:24] vport2 [23:16] vid2 [15:0]. Probable Cause: An error occurred while routing the fabric, possible data corruption of firmware error. Recommended Action: Collect IPMI event logs, and contact your HP support representative to inspect the fabric and system firmware. WBEM EventID: WBEM ProviderName: The OS being booted is not supported in a partition containing a mix of processor stepping revisions. Probable Cause: The OS being booted is not supported in a partition containing a mix of processor stepping revisions. Recommended Action: Failed processors should be replaced with like processors. Reconfigure the hardware to avoid configurations with mixed steppings. WBEM EventID: WBEM ProviderName: Firmware had an unexpected error while setting up links. Data field: vtype1 [63:56] vport1 [55:48] vid1 [47:32] vtype2 [31:24] vport2 [23:16] vid2 [15:0]. Probable Cause: An error occurred while routing the fabric, possible data corruption or firmware error. Recommended Action: Collect IPMI event logs, and contact your HP support representative to inspect the fabric and system firmware. WBEM EventID: WBEM ProviderName: Firmware was unable to write the Skyline global LINK_SEL_COHx CSR. Data field: cell num [63:56] link sel coh CSR (0 or 1) [0:0]. Probable Cause: An error occurred while routing the fabric. Recommended Action: Collect IPMI event logs, and contact your HP support representative to inspect the fabric and system firmware. WBEM EventID: WBEM ProviderName: The requested OS does not support booting with mixed CPU revisions. Probable Cause: Mixed CPU revisions exist in a mixed-cpu stepping configuration. Recommended Action: Replace cells to match cpu stepping revisions or deconfigure the unmatched processors. WBEM EventID: WBEM ProviderName: System firmware experienced an error while updating the link sel value. Data field indicates return status. Probable Cause: updating the global link select fabric value. Recommended Action: Contact your HP Support Representative to investigate the fabric subsystem. WBEM EventID: WBEM ProviderName: Fabric was unable to generate a Skyline CSR address. Data field: cell number [63:56] and return value from address function [31:0]. Probable Cause: An error occurred while routing the fabric, possible data corruption or firmware error. Recommended Action: Collect IPMI event logs, and contact your HP support representative to inspect the fabric and system firmware. WBEM EventID: WBEM ProviderName: Firmware was unable to generate a Skyline CSR address. Data field: cell number [63:56] return value [31:0]. Probable Cause: An error occurred while routing the fabric, possible data corruption or firmware error. Recommended Action: Collect IPMI event logs, and contact your HP support representative to inspect the fabric and system firmware. WBEM EventID: WBEM ProviderName: Invalid or no OS boot rendezvous entry point for target CPU. Probable Cause: OS or firmware bugs. Recommended Action: Call HP support. WBEM EventID: WBEM ProviderName: Checksum verification failed for OS_BOOT_RENDEZ entry point. Probable Cause: Software data corruption. Recommended Action: Call HP support. WBEM EventID: WBEM ProviderName: Platform Events 77

78 The System Firmware call to PAL_COPY_INFO failed. Probable Cause: Contact Engineering, This is a bug. WBEM EventID: WBEM ProviderName: The System Firmware call to PAL_COPY_PAL failed. Probable Cause: Contact Engineering, This is a bug. WBEM EventID: WBEM ProviderName: The System Firmware call to PAL_CACHE_FLUSH failed. Probable Cause: Contact Engineering, This is a bug. WBEM EventID: WBEM ProviderName: Cell on line add/delete is not initialized. Probable Cause: Cell online add/delete was attempted but the colad subsystem failed to initialize. Recommended Action: Contact HP support. When this event is emitted, cell online add/delete is not usable. WBEM EventID: WBEM ProviderName: An FPARs component on which cell on-line add/delete depends is broken or missing. Probable Cause: FPARs component on which cell on line add/delete depends is broken or missing. Recommended Action: Do not use COLAD is FPARs mode. WBEM EventID: WBEM ProviderName: Cell on-line add/delete in FPARs mode failed to get the FPARs semaphore. Probable Cause: Cell on line add/delete in FPARs mode failed to get the FPARs semaphore. Recommended Action: Do not use cell on line add/delete in FPARs mode. WBEM EventID: WBEM ProviderName: More than one processor from an FPAR called into cell on-line add/delete. Probable Cause: More than one processor from an FPAR called into cell on line add/delete. Recommended Action: Do not use cell on line add/delete in FPARs mode. WBEM EventID: WBEM ProviderName: All FPARs processors failed to rendezvous during a cell on line add/delete operation. Probable Cause: All FPARs processors failed to rendezvous during a cell on line add/delete operation. Recommended Action: Do not use cell on line add/delete in FPARs mode. WBEM EventID: WBEM ProviderName: Encountered unexpected error during cell OLA activity. Probable Cause: New cell cannot communicate with existing partition. Cell OLA failed. Recommended Action: Existing partition can continue to run, new cell cannot be added to the partition. WBEM EventID: WBEM ProviderName: MCA occurred prior to completion of previous MCA. Probable Cause: An MCA happened before a previous MCA event did not complete. Recommended Action: For Fpars/Vpars, system FW will reset the hard partition. For npars, system FW will still attempt to hand off to the OS_MCA handler, if OS_MCA handoff fails, the hard partition will get reset. WBEM EventID: WBEM ProviderName: MCA during init event processing. Probable Cause: An MCA event happening before a previous INIT event was not completely processed. Recommended Action: For Fpars/Vpars, system FW will reset the hard partition. In Npars mode, MCA handler will attempt to hand off to OS_MCA handler. If handoff fails, the hard partition will be reset. WBEM EventID: WBEM ProviderName: unable to find a bad edge in an untraversable route. Probable Cause: The bad edge could not be found. Recommended Action: Check for intermittent link errors. Capture IPMI event logs and look for additional error events. Contact your HP Support Representative to investigate the fabric. WBEM EventID: WBEM ProviderName: Unknown entity drawing power from bus bars. WBEM EventID: WBEM ProviderName: Soft partition could not be booted, reverting to npars. Probable Cause: A soft partition could not be booted. Please refer to previous events for the complete details. Recommended Action: The partition is rebooted to npars to allow the soft partition to be re-configured. WBEM EventID: WBEM ProviderName: 78 WBEM Provider Event Tables

79 Unable to route around broken link. Probable Cause: A traversable route between the local cell and the specified destination crossbar could not be found. Recommended Action: Capture IPMI event logs. Contact your HP Support Representative to investigate the fabric subsystem. WBEM EventID: WBEM ProviderName: Unable to set the APER 'fabric lockdown' bit. Probable Cause: Internal FW error. Recommended Action: Reset partition. WBEM EventID: WBEM ProviderName: An uncorrectable memory ECC error has occurred. The data field gives the physical location of the DIMM that had the error. Probable Cause: An uncorrectable memory ECC error has occurred. Recommended Action: Replace all DIMMs in the memory rank specified in the physical location info. If problem persists, contact HP support to troubleshoot the problem. WBEM EventID: WBEM ProviderName: An error encountered while retrieving the expected neighbor fabric chip for distributing traffic over crossbar links. Probable Cause: Unexpected error retrieving information from the fabric graph. Recommended Action: Collect IPMI event logs and contact your HP Support Representative to investigate the fabric system firmware subsystem. WBEM EventID: WBEM ProviderName: Could not read crossbar neighbor information during routing. Probable Cause: System Firmware encountered an error while reading a fabric crossbar chip. Recommended Action: Collect IPMI Event Logs and contact your HP Service Representative to investigate the fabric subsystem. WBEM EventID: WBEM ProviderName: Could not establish route for local crossbar during route around routing. Probable Cause: System Firmware could not establish routing from the local crossbar that would be needed to complete the route around routing. Recommended Action: Collect IPMI Event Logs and contact your HP Support Representative to investigate the fabric subsystem. WBEM EventID: WBEM ProviderName: An invalid or non-supported TPM (Trusted Platform Module) has been detected. Ensure that the TPM is fully seated into the system board and verify the operating system is TPM capable. Probable Cause: An invalid, non supported TPM is being used in the system. Recommended Action: Contact HP for support. WBEM EventID: WBEM ProviderName: Invalid or unsupported TPM detected in the system. TPM is disabled. Probable Cause: An invalid or unsupported TPM has been detected in the system. TPM is disabled. Recommended Action: Contact HP support. WBEM EventID: WBEM ProviderName: TPM failed initialization. Security features disabled. Probable Cause: Bad TPM chip. Recommended Action: contact HP support. WBEM EventID: WBEM ProviderName: A CPU module's temperature has exceed the high temperature threshold or a CPU power module fault has occurred. As a result of this event, the CPU has been inhibited. The Cell must be powered off then on using the MP's PE command to clear. Probable Cause: A CPU module's temperature has exceed the high temperature threshold or a CPU power module fault has occurred. Recommended Action: Contact HP support personnel to troubleshoot the problem. WBEM EventID: WBEM ProviderName: SFW detected an error while writing to stable store flash. Probable Cause: Cosmic radiation Bad flash part. Recommended Action: Reboot, if problem persists, contact HP support. WBEM EventID: WBEM ProviderName: Stable Store data is uninitialized or invalid. Probable Cause: Bad checksum on the stable store area. Cosmic radiation Bad flash part. Recommended Action: Reboot, if problem persists, contact HP support. WBEM EventID: WBEM ProviderName: Platform Events 79

80 Windows crash dump file has not been enabled. Probable Cause: The system has not been configured to save debugging information in the event of a system crash. Recommended Action: Configure writing debugging information using Windows Control Panel>System>Advance>Startup and Recovery. WBEM EventID: WBEM ProviderName: Windows paging file size or the free space of the memory dump target volume is too small. Probable Cause: The paging file or the free space of the memory dump target volume is not large enough to store the crash dump information in the event of a system crash. Recommended Action: Check the crash dump settings for the recommended Paging File size using the HP System Management Home Page or use Startup and Recovery under Windows System Properties. Also execute the disk cleanup to free some space on the target volume of the memory dump file. WBEM EventID: WBEM ProviderName: PCI interlock open with PCI power applied. Probable Cause: PCI interlock has been opened with PCI slot power on. Recommended Action: power down slot attempting to remove PCI card. WBEM EventID: WBEM ProviderName: Fault detected on low drop out regulator on I/O backplane. Probable Cause: A defective component could cause this fault. Recommended Action: Check the backplane. WBEM EventID: WBEM ProviderName: Fault detected on low drop out regulator on main backplane. Probable Cause: The specified low dropout regulator on the main backplane is reporting a fault. Recommended Action: Check the main backplane. WBEM EventID: WBEM ProviderName: Fault detected hot swap controller of specified core IO. Probable Cause: The hot swap controller for the specified core IO is reporting fault. Recommended Action: Check the specified core IO. WBEM EventID: WBEM ProviderName: An error occurred while retrieving the crossbar chip number. Probable Cause: System firmware had difficulty determining the crossbar number from the graph data structure. Recommended Action: Capture IPMI event logs, look for additional errors. Contact your HP Support Representative to analyze the fabric. WBEM EventID: WBEM ProviderName: One or more of the cells are not configured for Cell-Local Memory (CLM) mode. Probable Cause: The initial partition configuration may have not specified 100% Cell-Local Memory or may have been reconfigured incorrectly. Recommended Action: Reconfigure the partition or reset the CLM setting on one or more cells in your partition using the Partition Manager or ParCLI tools. WBEM EventID: WBEM ProviderName: Double DRAM chip sparing events have been invoked. Probable Cause: System firmware has detected and corrected memory errors. Double DRAM chip sparing events have been invoked to help mitigate this condition. On the next reboot, system firmware will test the specified memory components, and may take them offline if the errors persist. Recommended Action: Contact your HP support representative to check the specified memory. WBEM EventID: WBEM ProviderName: A platform error was detected by the firmware/hardware, and corrected by using a spare channel. Probable Cause: Hardware has detected many link retries on one of its channels and has switched to a spare one. Recommended Action: Monitor the situation and contact your HP support representative to check the affected hardware. WBEM EventID: WBEM ProviderName: System Firmware detected an internal deadlock in the firmware tree. Probable Cause: Internal System Firmware bug. Recommended Action: Notify HP support. WBEM EventID: WBEM ProviderName: 80 WBEM Provider Event Tables

81 A platform error was detected by the firmware/hardware, and corrected by using a spare channel. Probable Cause: The error occurred between the crossbar chips on the backplane(s). Recommended Action: Contact your support representative to have the backplane and / or connections between backplanes checked. WBEM EventID: WBEM ProviderName: A platform error was detected by the firmware/hardware, and corrected by using a spare channel. Probable Cause: The error occurred between the cell controller and the IO controller. Recommended Action: Contact your support representative to have the Cell Controller to IO Interface checked. Check these FRUs: Cell-IO cable, IO chassis, IO backplane, cell, or system backplane. WBEM EventID: WBEM ProviderName: Multiple platform errors were detected and corrected by the firmware/hardware. Probable Cause: The errors occurred between the cell controller and the backplane. Recommended Action: Contact your support representative to have the Cell Controller to backplane Interface checked. WBEM EventID: WBEM ProviderName: Multiple platform errors were detected and corrected by the firmware/hardware. Probable Cause: The errors occurred between the crossbar chips on the backplane(s). Recommended Action: Contact your support representative to have the backplane and / or connections between backplanes checked. WBEM EventID: WBEM ProviderName: Multiple platform errors were detected and corrected by the firmware/hardware. Probable Cause: The errors occurred between the cell controller and the IO controller. Recommended Action: Contact your support representative to have the Cell Controller to IO Interface checked. Check these FRUs: Cell-IO cable, IO chassis, IO backplane, cell, or system backplane. WBEM EventID: WBEM ProviderName: The server ID does not match the cabinet type. Probable Cause: The cabinet type is not in agreement with the server identification information. The server identification information is viewable using the ID command from the MP's command menu. The cabinet type is displayed in the top line of the cabinet status shown when the PS command from the MP's command menu is used to target a compute cabinet. Recommended Action: Contact your support representative to have the server identification information and cabinet type checked. WBEM EventID: WBEM ProviderName: Duplicate DIMM serial numbers have been detected. Data field gives physical location of DIMM. Check for other events specifying other DIMMs with same serial number. Probable Cause: Multiple DIMMs have the same serial number. Recommended Action: Replace DIMMs with duplicate serial numbers. Ensure new DIMMs have unique serial numbers. WBEM EventID: WBEM ProviderName: The MP has lost lan communication with the UPS. Probable Cause: The UPS has been disconnected or has failed. Recommended Action: Insure the UPS is connected properly and use the UPS command to verify that it can communicate with the MP. If not, try replacing the UPS. WBEM EventID: WBEM ProviderName: The MP has re-gained lan communication with the UPS. Probable Cause: The UPS has been connected and can communicate with the MP. Recommended Action: Use the UPS command to set/verify the desired settings. WBEM EventID: WBEM ProviderName: An unrecoverable processor interrupt occurred while in IPF firmware. The data value is the processor IFA. Probable Cause: Probable bug in System Firmware, EFI driver, EFI app or OS loader (prior to OS launch). The event data field contains the IVT offset applicable to the interrupt. See table 5-7 (Interruption Vector Table) in the Intel ASDM Volume 2. Recommended Action: Provide console log containing register dump to HP Customer Engineer. WBEM EventID: WBEM ProviderName: Platform Events 81

82 An unrecoverable processor interrupt occurred while in IPF firmware. The event data is the processor ISR. Probable Cause: Probable bug in System Firmware, EFI driver, EFI app or OS loader (prior to OS launch). The event data field contains the IVT offset applicable to the interrupt. See table 5-7 (Interruption Vector Table) in the Intel ASDM Volume 2. Recommended Action: Provide console log containing register dump to HP Customer Engineer. WBEM EventID: WBEM ProviderName: Double chip sparing has been invoked. Probable Cause: System firmware has detected and corrected memory errors. Double chip sparing has been invoked to help mitigate this condition. Recommended Action: On the next reboot, system firmware will test the specified memory components, and may take them offline if the errors persist. contact your HP support representative to check the specified memory components at your next scheduled downtime. WBEM EventID: WBEM ProviderName: External clock cable has been removed from the CPU cabinet. The data field contains the physical location of the cabinet. Probable Cause: External clock cable has been removed from the CPU cabinet. Recommended Action: Check external clock cable. WBEM EventID: WBEM ProviderName: System Fabric encountered a link error after opening up the fabric link. Probable Cause: Fabric link errors were encountered. Recommended Action: Collect IPMI event logs. Contact your HP Support Representative to check the health of the system fabric. WBEM EventID: WBEM ProviderName: Fatal errors are present on a cell's link to the fabric. Data Field: (crossbar port 44) (crossbar 32) 1. Probable Cause: Fatal errors are present on the cell to crossbar links. Recommended Action: Collect IPMI Event logs. Contact your HP Support Representative to check the fabric subsystem health. WBEM EventID: WBEM ProviderName: System firmware encountered fabric problems. Data Field: (crossbar port 44) (crossbar 32). Probable Cause: s occurred while collecting error data from a fabric link. Recommended Action: Collect IPMI Event logs. Contact your HP Support Representative to check the fabric subsystem health. WBEM EventID: WBEM ProviderName: Fatal errors are present on a cell's link to the fabric. Data Field: (crossbar port 44) (crossbar 32). Probable Cause: Fatal errors are present on a cell to crossbar link. Recommended Action: Collect IPMI Event logs. Contact your HP Support Representative to check the fabric subsystem health. WBEM EventID: WBEM ProviderName: The operating system has recovered from a PCI error. Probable Cause: If the data word is not 0x , then the problem is most likely with the PCI card. If the value of the data word is 0x , then check event log with keyword PCI_ERROR_STATUS. If PCI_ERROR_STATUS > 1, then the problem is in the connection between System Bus Adapter and Lower Bus Adapter. If PCI_ERROR_STATUS = 1, then the problem is in the Lower Bus Adapter. WBEM EventID: WBEM ProviderName: The operating system has recovered from a PCI error. Probable Cause: See event with keyword PCI_LBA_DEV_SPEC_1. WBEM EventID: WBEM ProviderName: The operating system has recovered from a PCI error. Probable Cause: See log with keyword PCI_LBA_DEV_SPEC_1 for more information. WBEM EventID: WBEM ProviderName: The request to power on, either via MP user interface, power button, or other, was denied by the Enclosure Manager. Probable Cause: The enclosure may not have sufficient power for the new blade. Recommended Action: Make sure enclosure has the appropriate number and configuration of power supplies. Reduce power required by the blade (for instance, remove some memory or a CPU.) Or, if there are powered-on blades that are not in use, power them off. WBEM EventID: WBEM ProviderName: 82 WBEM Provider Event Tables

83 The blade has been forced to power-on, either via the MP user interface or the power button. The blade did not negotiate with the enclosure to insure that there was sufficient power for this action. Probable Cause: A forced power on occurred. Usually this is performed when a normal power on request is denied. The Onboard Administrator may now be running in a non-redundant or over-budget power configuration. Recommended Action: Make sure Onboard Administator has the appropriate number and configuration of power supplies. Reduce power required by the blade (for instance, remove some memory or a CPU.) Or, if there are powered-on blades that are not in use, power them off. WBEM EventID: WBEM ProviderName: The MP has repeatedly tried to communicate with the enclosure manager and has not received any response. Probable Cause: The MP has repeatedly requested communication with the Onboard Administrator and has not received a response. This may be because the EM has a fault condition, or is busy, being reset, or removed. Recommended Action: The communication loss may have been temporary and nothing needs to be done if the communication is now working. Check the Fault LED on the enclosure manager. Reset the enclosure manager. Reset the management processor. Replace the enclosure manager. WBEM EventID: WBEM ProviderName: This is an internal SW error. See Cause/Action. Probable Cause: A CPU has tried to acquired the same semaphore twice which resulted in a deadlock. This is an internal SFW error and is not recoverable. Recommended Action: Collect the entire FPL, SEL, console logs and forward them to the SFW team. Also note all activities around the time of this event. The entire logs must analyzed by the SFW team before further actions can be taken. The system must be cold reset to resume normal operation. WBEM EventID: WBEM ProviderName: This is an internal SW error. See Cause/Action. Probable Cause: A CPU has tried to acquired the same semaphore twice which resulted in a deadlock. This is an internal SFW error and is not recoverable. Recommended Action: Collect the entire FPL, SEL, console logs and forward them to the SFW team. Also note all activities around the time of this event. The entire logs must analyzed by the SFW team before further actions can be taken. The system must be cold reset to resume normal operation. WBEM EventID: WBEM ProviderName: This is an internal SW error. See Cause/Action. Probable Cause: A CPU has tried to acquired the same semaphore twice which resulted in a deadlock. This is an internal SFW error and is not recoverable. Recommended Action: Collect the entire FPL, SEL, console logs and forward them to the SFW team. Also note all activities around the time of this event. The entire logs must analyzed by the SFW team before further actions can be taken. The system must be cold reset to resume normal operation. WBEM EventID: WBEM ProviderName: This is an internal SW error. See Cause/Action. Probable Cause: A CPU has tried to acquired the same semaphore twice which resulted in a deadlock. This is an internal SFW error and is not recoverable. Recommended Action: Collect the entire FPL, SEL, console logs and forward them to the SFW team. Also note all activities around the time of this event. The entire logs must analyzed by the SFW team before further actions can be taken. The system must be cold reset to resume normal operation. WBEM EventID: WBEM ProviderName: The complex profiles between cells in a partition do not match. Data field is unused, earlier events will give more detail. Probable Cause: The Group A or Group C complex profiles didn't match on all cells in the partition. Recommended Action: Push out new complex profiles and reset. WBEM EventID: WBEM ProviderName: An I/O device is missing from the Core I/O. Probable Cause: Either an I/O device on the Core I/O has failed or the wrong card is plugged into the location of the expected Core I/O. Recommended Action: Replace the specified location with the supported Core I/O card. WBEM EventID: WBEM ProviderName: fpars PMI handler was unable to Notify a CPU's new owner after a migrate. Probable Cause: OS has not fully set up GPE enable bits with the FSHWA interface. Recommended Action: Contact HP support. WBEM EventID: WBEM ProviderName: Platform Events 83

84 fpars PMI handler was unable to Notify a CPU's new owner after a migrate. Probable Cause: OS incorrectly set up the IOSAPIC redirection entry through the FSHWA interface. Recommended Action: Contact HP support. WBEM EventID: WBEM ProviderName: An OS is shutting down due to an MCA (Machine Check Abort) or INIT. Probable Cause: An MCA or INIT occurred. Recommended Action: Analyze the dump + logs for cause. If necessary contact HP Support for assistance. WBEM EventID: WBEM ProviderName: An OS is shutting down due to a panic. Probable Cause: An OS has panicked. Recommended Action: Analyze the dump + logs for cause. If necessary contact HP Support for assistance. WBEM EventID: WBEM ProviderName: An instance of CLU FW has an installed firmware revision that is incompatible with the system type. Many system operations will fail until this condition is resolved. Probable Cause: Following an in-the-box system type upgrade, or after a UGUY board was replaced, the CLU FW may not have been updated to an appropriate revision for the system type. Recommended Action: Contact your HP Customer Support Representative to update all firmware entities to revisions that are appropriate for the system type. WBEM EventID: WBEM ProviderName: The online diagnostics have identified a hardware problem. Probable Cause: OS based diagnostics discovered a hardware problem. Recommended Action: Consult the OS diagnostics logs for details about the problem. WBEM EventID: WBEM ProviderName: Over-Temperature or power condition detected for processor. Probable Cause: The processor temperature or power has exceeded normal limits. The Enhanced Thermal Management (ETM) feature of the processor has been employed to reduce the chip power to allow operation within normal limits. If this condition persists, this will have an adverse impact on the performance of this processor. Recommended Action: Check that there are no issues with the cooling, and if the problem persists contact HP service. WBEM EventID: WBEM ProviderName: An error occurred while checking the fabricless boot state. Probable Cause: System firmware was unable to access the fabric graph or the expected vertex was not found. Recommended Action: This is a symptom of a problem, not the cause. Look for additional IPMI event logs that more accurately describe the problem. Contact your HP Support Representative to investigate the fabric. WBEM EventID: WBEM ProviderName: System firmware was unable to clear the link error masks. Probable Cause: This event does not indicate the original cause. This is a problem encountered while handling a fabric link error. Recommended Action: Collect IPMI event logs to determine the original cause of the error. Contact your HP Support Representative to troubleshoot the fabric. WBEM EventID: WBEM ProviderName: System firmware could not determine a link's address. Probable Cause: This event does not indicate the original cause. This is a problem encountered while handling a fabric link error. Recommended Action: Collect IPMI event logs to determine the original cause of the error. Contact your HP Support Representative to troubleshoot the fabric. WBEM EventID: WBEM ProviderName: System firmware was unable to turn a bad link off. Probable Cause: This event does not indicate the original cause. This is a problem encountered while handling a fabric link error. Recommended Action: Collect IPMI event logs to determine the original cause of the error. Contact your HP Support Representative to troubleshoot the fabric. WBEM EventID: WBEM ProviderName: 84 WBEM Provider Event Tables

85 The windows watchdog timer has expired. The partition associated with the cell with the expired timer will be reset. Probable Cause: Windows had configured the Windows watchdog timer to either reset or power off the npartition on a timeout and the Windows watchdog timer has expired without being refreshed. The npartition will either be reset or powered off. Recommended Action: Investigate the operating system, drivers, Windows applications and event logs for possible causes. If hardware is suspected, contact HP customer support. WBEM EventID: WBEM ProviderName: An entity's MP Bus communications controller is reporting a hardware revision that is known to cause MP Bus communications failures. Probable Cause: An entity's MP Bus communications controller is reporting a hardware revision that is known to cause MP Bus communications failures. Recommended Action: Contact your HP Service Representative to investigate the failing hardware. WBEM EventID: WBEM ProviderName: 12v power to a PCI slot located on the IO Chassis has power faulted. Probable Cause: Main power at the PCI slot located on the IO Chassis has faulted. Recommended Action: contact HP support. WBEM EventID: WBEM ProviderName: SFW detected a failure while optimizing the fabric. Probable Cause: Failure detected by SFW while the optimizing fabric. Recommended Action: Collect IPMI events and contact your HP Support Representative for assistance. WBEM EventID: WBEM ProviderName: A critical failure occurred during a cell online add or delete. Probable Cause: A critical failure occurred during a cell online add or delete. Recommended Action: This event should not happen. Please contact HP. WBEM EventID: WBEM ProviderName: The cell being added has incompatible hardware or firmware revision with the partition. Probable Cause: The cell being added has incompatible hardware or firmware revision with the partition. Recommended Action: Previous events will give a description of the error that led to this event. These need to be corrected before the cell can be added. WBEM EventID: WBEM ProviderName: The System Firmware revision on the cell being added does not match the partition firmware revision. Probable Cause: The System Firmware revision on the cell being added does not match the partition firmware revision. Recommended Action: Update the System Firmware revision on the cell to be added. WBEM EventID: WBEM ProviderName: OpenVMS has detected an unrecoverable event and will reboot. Probable Cause: This event has been generated because OpenVMS has detected an unrecoverable failure - software inconsitency or hardware-generated MCA. Recommended Action: OpenVMS will reboot upon this failure. WBEM EventID: WBEM ProviderName: Bad cell board (on cellular system), or bad processor board (on non-cellular system). Probable Cause: Bad cell board (on cellular system), or bad processor board (on non-cellular system). Recommended Action: Contact your HP support representative to check the cell board (on cellular systems), or the processor board (on non-cellular systems) which the specified processor module is located in. WBEM EventID: WBEM ProviderName: CPU performance degraded due to excessive errors in third level cache. Probable Cause: The processor has experienced an excessive number of persistent correctable errors in its third level cache and as a result performance has degraded. Normally the processor can dynamically deal with this type of error with no impact on performance. However, if too many such errors occur then they begin to impact performance. The processor is still able to operate correctly but its performance is degraded so it should be replaced. Recommended Action: Contact HP Service for assistance. WBEM EventID: WBEM ProviderName: Platform Events 85

86 The alternate ROM failed to authenticate. The current (primary) ROM will continue to be used. Probable Cause: The alternate ROM does not contains a valid signature. It is not a supported ROM for this system or it does not come from HP. Recommended Action: Flash a new alternate ROM supported by the platform. WBEM EventID: WBEM ProviderName: The alternate ROM was successfully authenticated but the primary and alternate ROM could not be swapped. The current primary will still be used. Probable Cause: The BMC did not respond to the ROM swap command. Recommended Action: Check the BMC firmware, flash a new BMC firmware. If problem persists, contact HP support to troubleshoot the problem. WBEM EventID: WBEM ProviderName: PCI/PCIX/PCIe card/slot error detected during IO bus scan. Probable Cause: PCI/PCIx/PCIe card/slot hardware failure caused error during IO bus scan Additional data may be available via EFI 'info io' command. Recommended Action: Replace the faulty card. WBEM EventID: WBEM ProviderName: A coherency controller to coherency controller link has broken possibly due to a bad connection. Check the backplane connectors between the 2 cell boards and/or reseat both cells. If the problem persists, notify the Call Center for assistance. Probable Cause: Possible bad connection between cell and backplane. Recommended Action: Check that the two cell boards are firmly seated in the backplane.if problem persists, notify the Call Center for assistance. WBEM EventID: WBEM ProviderName: An unrecoverable processor interrupt occurred while in IPF firmware. The event data is the processor status register. If assistance is required, notify the Call Center and provide them with the console log containing the register dump. Probable Cause: Probable bug in System Firmware, EFI driver, EFI app or OS loader (prior to OS launch). Recommended Action: Provide console log containing register dump to HP Customer Engineer. WBEM EventID: WBEM ProviderName: An electronic keying problem has been detected. Probable Cause: The 'e-keying error' only occurs during the power-up if the SVB must be left off due to an electronic keying problem. Recommended Action: Try installing SVB in a different location. WBEM EventID: WBEM ProviderName: A Blade was installed in an improper location in the enclosure in violation of enclosure configuration rules. Review the installation documentation for additional information. Check the OA for additional related events. Probable Cause: SVB inserted in an improper location. Recommended Action: SVB must be installed in specific positions relative to fans or other components. WBEM EventID: WBEM ProviderName: A Blade was installed in the enclosure in violation of enclosure cooling configuration rules. Review the installation documentation for additional information. Check the OA for additional related events. Probable Cause: The 'cooling error' occurs during the power-up if the SVB must be left off due to insufficient cooling. Recommended Action: More fans may be needed for sufficient cooling. WBEM EventID: WBEM ProviderName: The sx2000 fabric reported an unexpected error. Try reseating the cell that reported the error. If assistance is required, notify the Call Center. Probable Cause: Firmware internal data corruption. Recommended Action: Reset cell that emitted the event. WBEM EventID: WBEM ProviderName: The OA was unable to service a power-on request. Try re-issuing the power-on request. If the problem reoccurs after subsequent requests, notify the Call Center for assistance. Probable Cause: If Onboard Administrator is busy in processing another requests, then it sends BUSY response for any requests that cannot be processed in time. Recommended Action: Try issuing the requests after some time. If the problem exists even after subsequent requests, please contact the HP representative. WBEM EventID: WBEM ProviderName: 86 WBEM Provider Event Tables

87 The IO backplane in the specified cabinet is reporting a non-redundant PCI power condition. It is possible that one of the PCI bricks is not present or not functioning properly. Check for PCI brick fault events. Probable Cause: One of the PCI bricks is not present or not functioning properly. Recommended Action: Check for PCI brick fault events. WBEM EventID: WBEM ProviderName: The Root Port initialization detected a PCI express link training failure. Probable Cause: The RP component detected a PCIe link training error, probably due to failed hardware. Recommended Action: Reseat or replace the PCIe card; update system firmware; replace the I/O riser if applicable; replace the motherboard. WBEM EventID: WBEM ProviderName: The Root Port component had insufficient GMMIO to support the PCIe request. Probable Cause: The RP component had insufficient GMMIO resources to support a board request. Recommended Action: Replace the faulty card, or remove one or more PCIe cards to reduce GMMIO requirements. WBEM EventID: WBEM ProviderName: HP unsupported DIMM(s) has been detected on this partition. Probable Cause: HP PFM service has detected one or more HP unsupported DIMMs on this partition. Recommended Action: Make sure to have HP supported DIMMs installed. WBEM EventID: WBEM ProviderName: OS run-time critical shutdown occurred. Probable Cause: The OS has caused the system to shut down. Recommended Action: Look at OS logs and crash data to determine why the system shut down. WBEM EventID: WBEM ProviderName: The amount of power expected to be drawn by the currently operating hardware is greater than the rating of the currently operating Bulk Power Supplies (BPS). Probable Cause: A bulk power supply has failed or was removed when the system had the minimal number of required bulk power supplies. Recommended Action: Replace the failed or removed bulk power supply. WBEM EventID: WBEM ProviderName: Bulk power supply (BPS) redundancy has been lost on one or more row(s) of power supplies in the complex. The further loss of a single BPS or an AC grid will most likely result in the shutdown of partitions. Probable Cause: A change has occurred in the number of properly operating bulk power supplies installed in the system. Recommended Action: Replace missing or failed bulk power supplies. WBEM EventID: WBEM ProviderName: AC redundancy has been lost on one or more power supplies in the complex. The further loss of a single Bulk Power Supply (BPS) or the other AC grid will most likely result in the shutdown of partitions. Probable Cause: A configuration change has been made to the system that changes the amount of power used. Recommended Action: Relook at the configuration changes. WBEM EventID: WBEM ProviderName: The fans that cool a region of the system are not redundant. If an additional fan fails or is removed from this cooling domain, the partitions on this system will be shut down to prevent damage. Probable Cause: One or more fans in the cooling domain have been removed or are not functioning properly. Recommended Action: Removed failed fan (if any) and insert working fan. WBEM EventID: WBEM ProviderName: An insufficient number of fans are working in a cooling domain to permit system operation. Running partitions will be shut down immediately to prevent damage due to excessive heat. Probable Cause: More than one fan in a cooling domain have been removed or are not functioning properly. Recommended Action: Remove failed fan(s), if any, and insert working fans. WBEM EventID: WBEM ProviderName: Operating system is not using all available processors for the current system. Probable Cause: Operating system license doesn't allow all processors to be used, or some processors are disabled / deconfigured. Recommended Action: Verify the correct operating system license to be used; Verify if all processors are enabled. WBEM EventID: WBEM ProviderName: Platform Events 87

88 A Fabric Message Processor (FMP) has unexpectedly reset. The system has recovered from the problem. Probable Cause: There is a firmware problem. Recommended Action: Verify that the most recent firmware is installed on the system. WBEM EventID: WBEM ProviderName: SMI training has failed. Probable Cause: SMI (Scalable Memory Interconnect) link training has failed. Recommended Action: If seating is not an issue, replace the EMB (Extended Memory Buffer), followed by the CPU. If not resolved, call support. WBEM EventID: WBEM ProviderName: DIMM at field location has been previously deallocated and remains deallocated. Probable Cause: A DIMM has been deallocated due to failure during memory init sequence. The most probable cause is a faulty DIMM. Other possible causes could be due to SMI failure, DDR3 training failure, or bad SMB (Scalable Memory Buffer) initialization. Recommended Action: The first action will be to replace the DIMM. If that does not solve the issue, replace CPU. If problem still continues to exist, replace the system board. WBEM EventID: WBEM ProviderName: Multi-blade conjoined rendezvous has failed. Probable Cause: Event occurs when rendezous among all known logical processors does not occur. All processors need to checkin with the monarch processor. Recommended Action: Check if the SBL (Scalable Blade Link) connector is damaged. Replace if damaged. If not, check, then replace processor. If problem persists, contact Support. WBEM EventID: WBEM ProviderName: Expected blades failed to rendezvous at memory checkpoint. Probable Cause: Processors failed to rendezvous at memory checkpoint. Recommended Action: Reboot. If problem persists, replace SBL (Scalable Blade Link), if applicable. If this does not resolve, then replace processor, then contact Support. WBEM EventID: WBEM ProviderName: Expected blades failed to rendezvous at memory test checkpoint. Probable Cause: Expected processors failed to rendezvous at memory test checkpoint. Recommended Action: Reseat the SBL and Reboot. If problem still exists, then replace the processor belonging to the missing thread (see event description for data mask). If problem persists, then contact Support. WBEM EventID: WBEM ProviderName: System topology (CPUs and IOHs) discovered is not a supported topology. Probable Cause: A QPI hardware error may have occurred. Recommended Action: Try rebooting the server. If problem persists contact support. WBEM EventID: WBEM ProviderName: Could not find default QPI data. Probable Cause: A hardware error may have occurred. Recommended Action: Try rebooting the server. If problem persists contact support. WBEM EventID: WBEM ProviderName: Detected a CPU QPI link's operation is degraded. Probable Cause: QPI link hardware has been detected operating with degraded performance. Recommended Action: Reboot. If problem persists contact support. WBEM EventID: WBEM ProviderName: Nested Interrupt occurred. Probable Cause: Firmware issue. Recommended Action: Contact your HP support representative. WBEM EventID: WBEM ProviderName: The CPUs across the system or SBL domain must all be the same type. Probable Cause: The part number of CPUs in the system/sbl domain are not the same. Recommended Action: The CPUs in the system or SBL domain must be the same part number. Check the FRU data using the DF command at the CM> menu. The S/SPEC should match and the core stepping should have a delta no greater than 1 across all CPUs. WBEM EventID: WBEM ProviderName: The Mezzanine IO Cards must be the same in all blades. Probable Cause: The Mezzanine IO Cards in all blades of the Domain are different. Recommended Action: The Mezzanine IO Cards must be the same in all blades of the Domain. WBEM EventID: WBEM ProviderName: 88 WBEM Provider Event Tables

89 This event was orginated as a Framework Assert Status Code. Probable Cause: System firmware has detected an internal error. Recommended Action: Look at previous events and ASCII information in this event for more information. If problem persists, contact support. WBEM EventID: WBEM ProviderName: System firmware protocol failed while executing ACPI subsystem code. Probable Cause: The failure is possibly related to using a corrupted System Firmware binary. Recommended Action: Ensure SFW component is at supported level. WBEM EventID: WBEM ProviderName: Failed to acquire platform specific data in ACPI. Probable Cause: ACPI received an invalid pointer to platform data. Possible causes for this are a corrupted System Firmware image or an error in the memory subsystem. Recommended Action: Ensure SFW component is at supported level. Check for errors in the memory subsystem if the problem persists. WBEM EventID: WBEM ProviderName: The ACPI subsystem encountered an unknown platform type. Probable Cause: ACPI failed to recognize the platform type of the server. This is likely due to corrupted NVM data. Recommended Action: Verify that Firmware is at the current supported revision. WBEM EventID: WBEM ProviderName: Invalid partition size encoutered by the ACPI subsystem. Probable Cause: Possible data corruption in non-volatile memory subsystem. Recommended Action: Reset the system. Verify that Firmware is at the current supported revision. WBEM EventID: WBEM ProviderName: ACPI parser error due to a missing platform AML identifier. Probable Cause: The ACPI subsystem could not find the Platfrom AML identifier while parsing the DSDT table. Recommended Action: Ensure SFW component is at supported level. WBEM EventID: WBEM ProviderName: ACPI parser error due to a missing AML identifier. Probable Cause: The ACPI subsystem could not find the Server AML identifier while parsing the DSDT table. Recommended Action: Ensure SFW component is at supported level. WBEM EventID: WBEM ProviderName: ACPI parser error due to a missing AML identifier. Probable Cause: The ACPI subsystem could not find the Serial Port AML identifier while parsing the DSDT table. Recommended Action: Ensure SFW component is at supported level. WBEM EventID: WBEM ProviderName: ACPI parser error due to a missing AML identifier. Probable Cause: The ACPI subsystem could not find the root-complex AML identifier while parsing the DSDT table. Recommended Action: Ensure SFW component is at supported level. WBEM EventID: WBEM ProviderName: ACPI parser error due to a missing AML identifier. Probable Cause: The ACPI subsystem could not find the ICH AML identifier while parsing the DSDT table. Recommended Action: Ensure SFW component is at supported level. WBEM EventID: WBEM ProviderName: ACPI parser error due to a missing AML identifier. Probable Cause: The ACPI subsystem could not find the root-port AML identifier while parsing the DSDT table. Recommended Action: Ensure SFW component is at supported level. WBEM EventID: WBEM ProviderName: ACPI parser error due to a missing AML identifier. Probable Cause: The ACPI subsystem could not find the slot AML identifier while parsing the DSDT table. Recommended Action: Ensure SFW component is at supported level. WBEM EventID: WBEM ProviderName: ACPI parser error due to a missing AML identifier. Probable Cause: The ACPI subsystem could not find the Platfrom AML identifier while parsing the DSDT table. Recommended Action: Ensure SFW component is at supported level. WBEM EventID: WBEM ProviderName: Platform Events 89

90 ACPI parser error due to a missing AML identifier. Probable Cause: The ACPI subsystem could not find the HPET AML identifier while parsing the DSDT table. Recommended Action: Ensure SFW component is at supported level. WBEM EventID: WBEM ProviderName: ACPI parser error due to a missing AML identifier. Probable Cause: The ACPI subsystem could not find the IPMI AML identifier while parsing the DSDT table. Recommended Action: Ensure SFW component is at supported level. WBEM EventID: WBEM ProviderName: ACPI parser error due to a missing AML identifier. Probable Cause: The ACPI subsystem could not find the Power Management AML identifier while parsing the DSDT table. Recommended Action: Ensure SFW component is at supported level. WBEM EventID: WBEM ProviderName: ACPI parser error due to a missing AML identifier. Probable Cause: The ACPI subsystem could not find the CPU AML identifier while parsing the DSDT table. Recommended Action: Ensure SFW component is at supported level. WBEM EventID: WBEM ProviderName: ACPI parser error due to a missing AML identifier. Probable Cause: The ACPI subsystem could not find the memory AML identifier while parsing the DSDT table. Recommended Action: Ensure SFW component is at supported level. WBEM EventID: WBEM ProviderName: ACPI failed to set its tables. Probable Cause: The ACPI driver in firmware failed to set the tables. Recommended Action: Ensure SFW component is at supported level. WBEM EventID: WBEM ProviderName: The ACPI subsystem failed to load the DSDT table from flash device. Probable Cause: The ACPI subsystem failed to load the DSDT table from flash device. Recommended Action: Ensure SFW component is at supported level. WBEM EventID: WBEM ProviderName: The ACPI subsystem failed to load the SSDT table from the flash device. Probable Cause: The ACPI could not load the SSDT table from the flash device. Recommended Action: Ensure SFW component is at supported level. WBEM EventID: WBEM ProviderName: SFW ROM versions across the partition are mismatched. Probable Cause: One or more processor System Firmware ROM version is mismatched with the Monarch CPU. Recommended Action: Update SFW. If the failure persists on the same CPU, replace the system board. WBEM EventID: WBEM ProviderName: The ilo peer to peer LAN communication between MMP and AMP was lost. Probable Cause: The ilo peer to peer LAN communication between a Monarch MP (MMP) and an Auxilary MP (AMP) has been lost. Recommended Action: The management system will attempt to repair itself. If the management system does not recover refer to the Service Guide to determine how to reset ilo without a user interface. WBEM EventID: WBEM ProviderName: The ilo peer to peer LAN communication between MMP and AMP was not established. Probable Cause: The ilo peer to peer LAN communication between Monarch MP (MMP) and an Auxilarly MP (AMP) could not be established. Recommended Action: The management system will attempt to repair itself. If the management system does not recover refer to the Service Guide to determine how to reset ilo without a user interface. WBEM EventID: WBEM ProviderName: The ilo peer to peer LAN communication between DMP and AMP was lost. Probable Cause: The ilo peer to peer LAN communication between a Domain MP (DMP) and an Auxiliary MP (AMP) has been lost. Recommended Action: The management system will attempt to repair itself. If the management system does not recover refer to the Service Guide to determine how to reset ilo without a user interface. WBEM EventID: WBEM ProviderName: 90 WBEM Provider Event Tables

91 The ilo peer to peer LAN communication between DMP and AMP was not established. Probable Cause: The ilo peer to peer LAN communication between Domain MP (DMP) and an Auxiliary MP (AMP) could not be established. Recommended Action: The management system will attempt to repair itself. If the management system does not recover refer to the Service Guide to determine how to reset ilo without a user interface. WBEM EventID: WBEM ProviderName: Virtual Connect failed to write data into a FRU storage device. Probable Cause: An error occurred in the interface between system firmware and manageability firmware while updating FRU data. Recommended Action: Reboot the server and verify that the system board or mezz card containing this FRU is functioning properly. If not, replace the failing hardware.check system logs to see if other NVM errors are related to this same board / card. If so, replace the board / card containing this FRU.Verify system and manageability firmware are at their currently supported revisions.if problems persist, contact Support. WBEM EventID: WBEM ProviderName: Virtual Connect failed to save a backup of non-volatile EFI variables into NVM. Probable Cause: An error occurred in the interface between system firmware and manageability firmware while saving persistent data. ilo may have been temporarily busy and may have missed an update. Recommended Action: Verify system and manageability firmware are at their currently supported revisions. If problems persist, contact Support. WBEM EventID: WBEM ProviderName: Virtual Connect failed to save non-volatile EFI variables into NVM. Probable Cause: An error occurred in the interface between system firmware and manageability firmware while saving persistent data. ilo may have been temporarily busy and may have missed an update. Recommended Action: Verify system and manageability firmware are at their currently supported revisions. If problems persist, contact Support. WBEM EventID: WBEM ProviderName: Virtual Connect failed to erase the EFI variables backup from NVM. Probable Cause: An error occurred in the interface between system firmware and manageability firmware while saving persistent data. ilo may have been temporarily busy and may have missed an update. Recommended Action: Verify system and manageability firmware are at their currently supported revisions. If problems persist, contact Support. WBEM EventID: WBEM ProviderName: IOH persistent error condition detected. Probable Cause: A persistent error on an I/O bridge or endpoint that cannot be cleared. Recommended Action: Replace the failed component as indicated by the physical location data field. WBEM EventID: WBEM ProviderName: Generic FRU has header checksum error. Probable Cause: 1. FRU not properly programmed 2. Manageabilty FW may not be working correctly. Recommended Action: Review the event log for related MFW events to determine if there is a FRU read problem.try a MFW reset via web or text interface. If this fails, verify all the firmware versions are at a supported revision level and do a full power cycle of the system. If this still fails, it is likely the FRU requires replacement. WBEM EventID: WBEM ProviderName: MFW is posting a Data Object Table which is one revision below what SFW expects. Probable Cause: Manageability FW is not at the current supported revision for this SFW. Recommended Action: Update Manageability FW. WBEM EventID: WBEM ProviderName: System Firmware will not work correctly with the shared memory table loaded. Probable Cause: The System Firmware has detected that Manageability FW has loaded an incompatible shared memory table. Recommended Action: Ensure the system FW versions are at a supported revision level.reset MFW via text or Web Interface. WBEM EventID: WBEM ProviderName: CPU Late Test failed due to PAL Test Info call failed. Probable Cause: A SFW or CPU error may have occurred. Recommended Action: If the problem persists replace the processor. WBEM EventID: WBEM ProviderName: Platform Events 91

92 One or more processor threads failed to start boot. Probable Cause: A CPU error occurred. It could have failed early self-test catrastrophically and is not handed back to SAL (SFW) from PAL (which performs the early self-test). Recommended Action: Replace the failed CPU. Search in the FPL for BOOT_CPU_THREAD_FAIL, then look at the next event which should be EVN_CPU_PHYSICAL_LOCATION to obtain the CPU physical location of the CPU with the thread/threads that failed to boot. WBEM EventID: WBEM ProviderName: Failed to save non-volatile EFI variables into NVM. Probable Cause: An error occurred in the interface between system firmware and manageability firmware while saving persistent data. ilo may have been temporarily busy and may have missed an update. Recommended Action: Verify system and manageability firmware are at their currently supported revisions. If problems persist, contact Support. WBEM EventID: WBEM ProviderName: The system reset failed when the TPM code attempted to change its status. Probable Cause: The reset command failed to reset the system. Recommended Action: Reboot the system. Verify that the system is at the latest firmware revision. WBEM EventID: WBEM ProviderName: The TPM related information could not be written to the Non-Volatile Memory. Probable Cause: The system could not save the TPM configuration to NVM (Non-Volatile Memory) This can be caused by manageability firmware/hardware. Recommended Action: Review the event log for related MFW events to determine if there is an NVM (Non-Volatile Memory) problem.try a MFW reset via web or text interface. If this fails, verify all the firmware versions are at a supported revision level and do a full power cycle of the system. WBEM EventID: WBEM ProviderName: The TPM DOT table could not initialize the TPM mode at next boot element. Probable Cause: The system could not initialized the value of TPM state at next boot in NVM (Non-Volatile Memory). This can be caused by manageability firmware/hardware. Recommended Action: Review the event log for related MFW events to determine if there is an NVM (Non-Volatile Memory) problem.try a MFW reset via web or text interface. If this fails, verify all the firmware versions are at a supported revision level and do a full power cycle of the system. WBEM EventID: WBEM ProviderName: The TPM DOT information does not appear to be initialized or is corrupted. Probable Cause: The System Firmware detected that Manageability FW has loaded an invalid shared memory table for the TPM. Recommended Action: Review the event log for related MFW events to determine if there is an NVM (Non-Volatile Memory) problem.try a MFW reset via web or text interface. If this fails, verify all the firmware versions are at a supported revision level and do a full power cycle of the system. WBEM EventID: WBEM ProviderName: The TPM DOT information has a bad checksum. Probable Cause: The System Firmware has detected a bad checksum in the TPM shared memory table. Recommended Action: Review the event log for related MFW events to determine if there is an NVM (Non-Volatile Memory) problem.try a MFW reset via web or text interface. If this fails, verify all the firmware versions are at a supported revision level and do a full power cycle of the system. WBEM EventID: WBEM ProviderName: The TPM DOT checksum could not be recalculated. Probable Cause: The System Firmware has detected a bad checksum in the TPM shared memory table and failed to fix the checksum in Non-Volatile Memory. Manageability may not be able to update NVM. Recommended Action: Review the event log for related MFW events to determine if there is an NVM (Non-Volatile Memory) problem.try a MFW reset via web or text interface. If this fails, verify all the firmware versions are at a supported revision level and do a full power cycle of the system. WBEM EventID: WBEM ProviderName: 92 WBEM Provider Event Tables

93 The TPM DOT information is not initialized. Probable Cause: The System Firmware has detected an uninitialized shared memory table for the TPM. This can be caused by manageability firmware/hardware. Recommended Action: The system will try to initialize the memory table. If the error persists, review the event log for related MFW events to determine if there is an NVM (Non-Volatile Memory) problem.try a MFW reset via web or text interface. If this fails, verify all the firmware versions are at a supported revision level and do a full power cycle of the system.replace the battery. WBEM EventID: WBEM ProviderName: The TPM DOT information could not be initialized successfully. Probable Cause: The System Firmware has detected an uninitialized shared memory table for the TPM and failed to initialize it. This can be caused by an error with Manageability firmware/hardware. Recommended Action: Review the event log for related MFW events to determine if there is an NVM (Non-Volatile Memory) problem.try a MFW reset via web or text interface. If this fails, verify all the firmware versions are at a supported revision level and do a full power cycle of the system. WBEM EventID: WBEM ProviderName: The TPM DOT information could not be updated with the TPM presence indication. Probable Cause: The system could not initialize the value of the TPM presence flag in NVM (Non-Volatile Memory) possibly due to an error on manageability. Recommended Action: Review the event log for related MFW events to determine if there is an NVM (Non-Volatile Memory) problem.try a MFW reset via web or text interface. If this fails, verify all the firmware versions are at a supported revision level and do a full power cycle of the system. WBEM EventID: WBEM ProviderName: The TPM DOT could not be updated with the TPM absent flag. Probable Cause: The system could not initialize the value of the TPM presence flag to Absent in NVM (Non-Volatile Memory) possibly due to an error on Manageability. Recommended Action: Review the event log for related MFW events to determine if there is an NVM (Non-Volatile Memory) problem.try a MFW reset via web or text interface. If this fails, verify all the firmware versions are at a supported revision level and do a full power cycle of the system. WBEM EventID: WBEM ProviderName: The TPM mode at next boot command could not be cleared in the TPM DOT table. Probable Cause: The system could not clear the command to change the TPM state at next boot in the NVM (Non-Volatile Memory) possibly due to an error on manageability firmware/hardware. Recommended Action: Review the event log for related MFW events to determine if there is an NVM (Non-Volatile Memory) problem.try a MFW reset via web or text interface. If this fails, verify all the firmware versions are at a supported revision level and do a full power cycle of the system. WBEM EventID: WBEM ProviderName: The command to change the TPM state has failed. Probable Cause: The request to change the TPM state has failed. An error occurred with the TPM. Recommended Action: Review the event log for TPM related messages. Reboot the system. Replace the TPM board. WBEM EventID: WBEM ProviderName: Failed to acquire platform specific data in ACPI. Probable Cause: Corrupted SFW image. Recommended Action: Ensure SFW component is at supported level. WBEM EventID: WBEM ProviderName: Failed to acquire platform specific data in ACPI. Probable Cause: Corrupted SFW image. Recommended Action: Ensure SFW component is at supported level. WBEM EventID: WBEM ProviderName: Failed to acquire platform specific data in ACPI. Probable Cause: Invalid SFW image. Recommended Action: Ensure SFW component is at supported level. WBEM EventID: WBEM ProviderName: Failed to acquire platform specific data in ACPI. Probable Cause: Invalid SFW image. Recommended Action: Ensure SFW component is at supported level. WBEM EventID: WBEM ProviderName: Platform Events 93

94 System Hive size exceeds warning threshold. Probable Cause: This system has exceeded the threshold for the System Hive size within the Registry. Recommended Action: Please refer to HP Document 'Managing the System Registry Hive for Windows 2003 and Windows 2008 Integrity Systems' for information on how to proactively manage this event type. This document can be found on or at the following FTP location: ftp://ftp.hp.com/pub/servers/software/windowsintegrity/managingwindowsregistry.pdf. WBEM EventID: WBEM ProviderName: System Hive size exceeds critical threshold. Probable Cause: This system has exceeded the Upper threshold for the System Hive size within the Registry. Urgent action is required in order to mitigate a potential failure to boot, should the System Hive exceed 32Mb. Recommended Action: Refer to HP Document 'Managing the System Registry Hive for Windows 2003 and Windows 2008 Integrity Systems' for information on how to reduce the System Hive size and minimize risk of boot failure. This document can be found on or at the following FTP location: ftp://ftp.hp.com/pub/servers/software/windowsintegrity/managingwindowsregistry.pdf. WBEM EventID: WBEM ProviderName: Detected a IOH QPI link's operation is degraded. Probable Cause: QPI link hardware has been detected operating with degraded performance. Recommended Action: Reboot. If problem persists contact support. WBEM EventID: WBEM ProviderName: The system has been issued an INIT. All activity will be halted. Probable Cause: A user has issued an INIT interrupt to the system. Recommended Action: None. The system will restart on its own. WBEM EventID: WBEM ProviderName: Insufficient power; more power supplies may be needed. Probable Cause: Power request to OA denied with the reason insufficient power. Either not enough BPS, or too much power draw from other blades installed in enclosure. Consult OA to determine if there is enough room to add BPS. Recommended Action: Install more power supply units, or reduce the current draw on the power system. Power Cap is one method that could be used to reduce current draw. You may want to verify that none of your BPS have failed. WBEM EventID: WBEM ProviderName: The EM has determined that power must be shed and has asserted Power Alert. Probable Cause: Typically caused by a power supply failure reducing the power pool available to the EM to distribute to the blades. Recommended Action: Identify any failed power supplies and replace them. WBEM EventID: WBEM ProviderName: ilo entering special mode. Probable Cause: ilo entering special mode. The system is not operating in a normal mode. Some protection features may be disabled in this mode. Recommended Action: The special mode must be exited to ensure proper operation of the server. WBEM EventID: WBEM ProviderName: A firmware update has failed. Probable Cause: An attempted firmware update has failed with an error. Recommended Action: Check to make sure that the bits are accessible and system power is off. Try the update again. WBEM EventID: WBEM ProviderName: A failure has occurred while attempting to update the ilo ROM. Probable Cause: Something has interfered with firmware update while it attempted to update the bits in the ilo ROM. Recommended Action: DO NOT REMOVE POWER FROM THE SYSTEM. DO NOT RESET ilo. Attempt the update again or attempt update to original version. Refer to recipe notes to verify no procedural issues. WBEM EventID: WBEM ProviderName: A failure has occurred while attempting to update the SFW ROM. Probable Cause: Something has interfered with firmware update while it attempted to update the bits in the SFW ROM. The Aux ROM and either of the direct attach SFW ROMs or any combination there of may be affected. Recommended Action: Attempt the update again. If this fails you may want to reset ilo or remove stby power from the system and try the update again. WBEM EventID: WBEM ProviderName: 94 WBEM Provider Event Tables

95 A failure has occurred while attempting to update the FPGA ROM. Probable Cause: Something has interfered with firmware update while it attempted to update the bits in the FPGA ROM. Recommended Action: Do not remove power from the system. Do not reset ilo. Attempt the update again. WBEM EventID: WBEM ProviderName: A failure has occurred while attempting to update the Power Monitor PIC. Probable Cause: Something has interfered with firmware update while it attempted to update the bits in the Power Monitor PIC. Recommended Action: Attempt the update again. If this fails try resetting ilo or removing stand by power and attempt the update again. WBEM EventID: WBEM ProviderName: The system has been placed in security override mode. Probable Cause: A user has asserted the physical presence button for a duration greater than 8 seconds and less than 12 seconds. Recommended Action: This mode will timeout in 15 minutes or less. To manually exit this mode go to the Access Settings web page. You can also press the physical presence button for less than 4 seconds to reset ilo and clear this mode. WBEM EventID: WBEM ProviderName: The system is entering TPM physical presence mode. Probable Cause: A user has asserted the TPM physical presence button for a duration of greater than 4 seconds and less than 8 seconds. Recommended Action: No action is required. This event indicates that the system was placed in a mode where restricted commands can now be executed by the TPM. Asserting the physical presence button for less than 4 seconds will reset ilo and clear the TPM physical presence mode. WBEM EventID: WBEM ProviderName: The TPM did not accept the start-up request. Probable Cause: The TPM can be defective or has detected a tampering attempt. Recommended Action: Verify for possible tampering. Replace the board hosting the TPM chip. WBEM EventID: WBEM ProviderName: The thread has received an interruption during boot. Probable Cause: Firmware, EFI applications, OS boot, or Hardware s caused unexpected interruptions. Recommended Action: Review the following interruption events in the FPL. Reboot the system. If problem persists, contact support. WBEM EventID: WBEM ProviderName: Fans are entering blowout mode. Probable Cause: A sensor may have been unreadable or the lid to the system may be detected as open. See the datafield for the sensor that caused the error forcing fans into blowout mode. Recommended Action: Investigate the sensor implicated in the datafield to determine the cause of failure. If a temp sensor can't be read try AC cycling the box; if a fan sensor can't be read try reseating the fan and AC cycling the box; if the lid latch is detected as open, place lid on the box, or if it is already there; reseat it. If none of this helps try replacing the FRU associated with sensor. WBEM EventID: WBEM ProviderName: Core Analysis Engine DB threw an exception. WBEM EventID: WBEM ProviderName: A Socket Monarch Thread has stopped making forward progress. Probable Cause: Unexpected Firmware or Hardware s. Recommended Action: Verify that the firmware is at the current supported revision. Replace the processor. WBEM EventID: WBEM ProviderName: The Partition Monarch Thread has stopped making forward progress. Probable Cause: Unexpected Firmware or Hardware s. Recommended Action: Verify that the firmware is at the current supported revision. Replace the processor. WBEM EventID: WBEM ProviderName: The processor module that contains the Monarch Thread was deconfigured. Probable Cause: Unexpected Firmware or Hardware has been encountered. Recommended Action: Verify that the system is at the current supported revision. Replace the processor. WBEM EventID: WBEM ProviderName: Core Analysis Engine failed to get SAL error data. WBEM EventID: WBEM ProviderName: Platform Events 95

96 Core Analysis Engine received an unknown error log. WBEM EventID: WBEM ProviderName: Core Analysis Engine failed to get error log bundle status. WBEM EventID: WBEM ProviderName: Core Analysis Engine failed to get next error log bundle. WBEM EventID: WBEM ProviderName: Core Analysis Engine failed to get the last processed bundle. WBEM EventID: WBEM ProviderName: Core Analysis Engine failed to get the error log bundle status. WBEM EventID: WBEM ProviderName: Invalid count reported for number of supported CPU p-states. Probable Cause: The processor is reporting invalid data about its power management information. Recommended Action: Verify that Firmware is at the current supported revision. Replace the processor module. WBEM EventID: WBEM ProviderName: Indicates an error has occurred while trying to reset SAS controllers. Probable Cause: An error has occurred while trying to reset the SAS controller after a GMCA, during I/O discovery or during early IOH Init. Recommended Action: Verify card is properly seated. Update firmware on SAS controller. Verify that the system firmware is at a supported revision. If problem persists, contact support. WBEM EventID: WBEM ProviderName: System firmware failed to publish ACPI tables. Probable Cause: The ACPI subsystem could not publish ACPI tables due to a System Firmware error. Recommended Action: Verify that Firmware is at the current supported revision. WBEM EventID: WBEM ProviderName: Indicates an inconstency in bus numbering has been discovered. Probable Cause: The busnumber returned by GetSystemSocketsInfo() does not match what is expected. Recommended Action: Ensure all systems in the enclosure are conjoined as required and functioning. Verify the SBL is installed and seated properly. Verify that MFW and SFW on each blade is up-to-date. If problem persists, contact support. WBEM EventID: WBEM ProviderName: software memory test failed. Probable Cause: Unexpected data accessed from the memory address during firmware memory test. Recommended Action: Check for de-allocated DIMM(s). Reseat the DIMM(s). If the problem persists, then replace the DIMM(s) with supported DIMM(s) - See Service Guide. WBEM EventID: WBEM ProviderName: Scalable memory buffer (SMB) link initialization failed. Probable Cause: Scalable Memory Buffer (SMB) link initialization failed. Recommended Action: Replace the CPU. If problem still continues to exist, replace the system board. WBEM EventID: WBEM ProviderName: Scalable memory buffer (SMB) channel training failed. Probable Cause: Scalable Memory Buffer (SMB) channel training failed. Recommended Action: The first action will be to reset the CPU. If that does not solve the issue, replace CPU. If problem still continues to exist, replace the system board. WBEM EventID: WBEM ProviderName: Memory build-in self test (MBIST) failed. Probable Cause: Memory Build-in self test failed. Recommended Action: The first action will be to check the SEL for the de-allocated DIMM(s). Next, reseat the failing DIMM(s). If that does not solve the issue, replace the DIMM(s) with supported DIMM(s) - See Service Guide. If problem still continues to exist, replace the system board. WBEM EventID: WBEM ProviderName: Memory build-in self test failed with timeout. Probable Cause: Memory built-in self test failed with timeout. Recommended Action: The first action will be to check the SEL for the de-allocated DIMM(s). Next, reseat the failing DIMM(s). If that does not solve the issue, replace the DIMM(s) with supported DIMM(s) - See Service Guide. If problem still continues to exist, replace the system board. WBEM EventID: WBEM ProviderName: 96 WBEM Provider Event Tables

97 DIMM rank mismatch or rank not found during memory initialization. Probable Cause: The DIMM rank data is invalid or does not match with the other DIMM pair. The DIMM FRU data is invalid and FW cannot initialize DIMMs based on invalid data. Recommended Action: Reseat the DIMM. If problem persists, replace DIMM with supported DIMM type (see Service Guide). WBEM EventID: WBEM ProviderName: Unable to aquire communications link to scalable memory buffer (SMB). Probable Cause: Failed to acquire communication link to scalable memory buffer (SMB). Recommended Action: Reseat and/or replace the CPU. If problem still continues to exist, replace the system board. WBEM EventID: WBEM ProviderName: Failed outband read access to scalable memory buffer (SMB) due to timeout. Probable Cause: Failed outband read access to Scalable Memory Buffer (SMB) due to timeout. Recommended Action: Reseat/ replace the CPU. If problem still continues to exist, replace the system board. WBEM EventID: WBEM ProviderName: Failed outband write access to scalable memory buffer (SMB) due to timeout. Probable Cause: Failed outband write access to Scalable Memory Buffer (SMB) due to timeout. Recommended Action: Reseat and/or replace the CPU. If problem still continues to exist, replace the system board. WBEM EventID: WBEM ProviderName: Inband access to memory controller timed out. Probable Cause: Failed inband access to Scalable Memory Buffer (SMB) due to timeout. Recommended Action: The first action will be to reseat and/or replace the CPU. If problem still continues to exist, replace the system board. WBEM EventID: WBEM ProviderName: Frequency ratio for DIMM is incompatible. Probable Cause: Memory frequency ratio is not supported by system platform. Recommended Action: The first action will be to verify the suspect DIMM via ilo. Replace the DIMM with supported DIMM type (see Service Guide). WBEM EventID: WBEM ProviderName: Reached unexpected code paths in memory initialization code. Probable Cause: Reached unexpected code paths in memory initialization code. Recommended Action: Ensure FW is at the current supported revision. WBEM EventID: WBEM ProviderName: LAI expander detected. Probable Cause: Unsupported memory Logical Analyzer Interface (LAI) expander detected. Recommended Action: Contact support. WBEM EventID: WBEM ProviderName: Invalid DIMM detected. Probable Cause: Invalid DIMM data found. Recommended Action: Verify DIMM is supported type (See Service Guide). Reseat the DIMM. If that does not solve the issue, replace DIMM. WBEM EventID: WBEM ProviderName: DDR calibration for commands failed. Probable Cause: DDR calibration of command failed. Recommended Action: The first action will be to check SEL for de-allocated DIMM(s). Reseat and/or replace the DIMM(s). If that does not solve the issue, reseat and/or replace CPU. If problem still continues to exist, replace the system board. WBEM EventID: WBEM ProviderName: DDR channel training failed. Probable Cause: DDR training failure. Recommended Action: The first action will be to check SEL for de-allocated DIMM(s). Reseat and/or replace the DIMM(s). If that does not solve the issue, reseat and/or replace CPU. If problem still continues to exist, replace system board. WBEM EventID: WBEM ProviderName: Pre-initialization of memory controller failed. Probable Cause: Failed to initialize internal communications engine on CPU. Recommended Action: The first action will be to check SEL for de-allocated DIMM(s). Reseat and/or replace the DIMM(s). If that does not solve the issue, reseat and/or replace CPU. WBEM EventID: WBEM ProviderName: Platform Events 97

98 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: WBEM ProviderName: 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 SBL are designed for the c7000 enclosure. SBL2-3000, SBL2E-3000, and SBL are designed for the c3000 enclosure. The SBL and SBL 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: WBEM ProviderName: 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 SBL are designed for the c7000 enclosure. SBL2-3000, SBL2E-3000, and SBL are designed for the c3000 enclosure. The SBL and SBL 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: WBEM ProviderName: 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: WBEM ProviderName: 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: WBEM ProviderName: 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: WBEM ProviderName: 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: WBEM ProviderName: 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: WBEM ProviderName: 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: WBEM ProviderName: 98 WBEM Provider Event Tables

99 System failed power on because one or more auxiliary blades failed to power on. Probable Cause: Power on was denied because there was a failure in the power on sequence. This probably points towards HW or communication synchronization issues. Recommended Action: Reset ilo and try again. If this doesn't work remove STBY power and try again. WBEM EventID: WBEM ProviderName: A blade failed to power on. Probable Cause: A blade has failed to power on. WBEM EventID: WBEM ProviderName: System failed to power on because the monarch bladed failed to power on. Probable Cause: A failure on the Monarch has resulted in a failure to power on. As a result the system will be powered off. Recommended Action: Try power on again. Reset ilo and try power on again. Remove STBY power and then try power on again. WBEM EventID: WBEM ProviderName: A previously powered on blade has lost power. Probable Cause: The blade indicated by the event has unexpectedly lost power. Recommended Action: At the next available opportunity power off the system and power on again. Monitor the blade to make sure this event doesn't happen again. WBEM EventID: WBEM ProviderName: The system has been powered off due to a power failure. Probable Cause: One or more blades had a power failure. As a result the system control is powering off the entire partition. Recommended Action: Try power on again. If it fails try with a reset to ilo and a removal of STBY power. If system powers back on properly monitor to make sure this doesn't occur again. WBEM EventID: WBEM ProviderName: The system variables are mismatched. Probable Cause: The contents in the system variables EEPROMs don't match. This indicates that the system variables have been programmed, but they don't match. Recommended Action: Run the SYSSET command to bring the system variables EERPOMs into allignment. WBEM EventID: WBEM ProviderName: The Power Monitor is in programming mode. Probable Cause: The most likely cause is that the stby power was removed while in the middle of updating the power monitory PIC. In this mode power protection is not enabled. Recommended Action: Update the Power Monitor immediately to return it to its normal state and re-enable power protection features. WBEM EventID: WBEM ProviderName: Power failed to turn on because there is no SBL (Scalable Blade Link) attached. Probable Cause: Power can not be turned on without an attached SBL. Recommended Action: Attach an appropriate SBL if you want to power on. If an SBL is already attached remove and inspect its pins. Also, inspect the blade side connector. If there are no bent pins and the connector looks ok reseat the SBL and try again. WBEM EventID: WBEM ProviderName: Power on denied by the OA with an UNKNOWN error code. Probable Cause: ilo was denied power by the OA with an errorcode that was unknown to ilo. Recommended Action: Refer to the recipe documentation to make sure that your OA version is compatible with the ilo FW you are using. Try resetting OA. WBEM EventID: WBEM ProviderName: A power supply has failed. Physical Location is included in datafield. Probable Cause: A power supply has failed. The connection could be loose or there could be a hardware failure. Recommended Action: Identify the failing supply from the physical location included in the alert. Check connections. If no loose connections are found replace the power supply. WBEM EventID: WBEM ProviderName: A fan has failed. Probable Cause: A connection may be bad. Otherwise a fan has probably failed. Recommended Action: Identify the Physical Location idicated in the datafield. Check connections and fan health. If connections are ok replace failed fan. WBEM EventID: WBEM ProviderName: Platform Events 99

100 Power not turned on. The ilo peer to peer LAN communication is not functional. Probable Cause: The ilo peer to peer LAN communication is not fully functioning. Could be caused by issues with the internal LAN or ilo code. Recommended Action: Review the logs to determine details of failure. The management system will attempt to repair itself. If the management system does not recover refer to the Service Guide to determine how to reset ilo without a user interface. WBEM EventID: WBEM ProviderName: Virtual Connect failed to save FRU data into NVM. Probable Cause: An error occurred in the interface between system firmware and manageability firmware while saving persistent data. ilo may have been temporarily busy and may have missed an update. Recommended Action: Reboot the server and verify that the system board or mezz card containing this FRU is functioning properly. If not, replace the mezz card or system board containing this FRU.Check system logs to see if other NVM errors are related to this same board / card. If so, replace the board / card containing this FRU.Verify system and manageability firmware are at their currently supported revisions.if problems persist, contact Support. WBEM EventID: WBEM ProviderName: The system will experience a hard reset as a result of a watchdog timeout. Probable Cause: The OS Watchdog has timed out. Recommended Action: System will be reset. Determine why the OS did not reset the watchdog. Consider changing the action to 'no action' for debug. Look for other unusual OS activity. WBEM EventID: WBEM ProviderName: The system will power down as a result of a watchdog timeout. Probable Cause: The OS Watchdog has timed out. Recommended Action: Review logs and power system back on if no concerning events are observed.determine why OS failed to reset the watchdog. Consider changing action to 'no action' for debug. Look for other unusual OS activity. WBEM EventID: WBEM ProviderName: The system will power cycle as a result of a watchdog timeout. Probable Cause: The OS Watchdog has timed out. Recommended Action: None. System will power back on in a moment. WBEM EventID: WBEM ProviderName: Unable to retrieve error information after a fatal error. Probable Cause: A fatal error has occurred. In attempting to configure hardware for error information recovery the valid signature wasnt found in the fatal error registers. Recommended Action: Review logs for indicators of what might have happened, and monitor system health. WBEM EventID: WBEM ProviderName: Failed to initialize shared memory. Probable Cause: Either the hardware (RAM) did not respond to the initialization requests, or there was a FW issue during setup of the shared memory task. Recommended Action: Try resetting ilo with an xd->r command from the ilo CM> prompt. WBEM EventID: WBEM ProviderName: The Display Board is not responding and may be missing. Probable Cause: The Display Board is not responding. It is either missing or loose. This board includes sensors such as the altimeter and a thermal sensor so operation may be altered. Recommended Action: Check if the board is present. If not replace it. If it is, remove it and re-insert it to ensure proper connectivity. WBEM EventID: WBEM ProviderName: integrated Lights Out firmware battery failure of NVRAM state change. Probable Cause: Determine if the firmware was recently upgraded. This is often the reason for the NVRAM to change. If not, and the A/C power has been removed, than it's possible the battery is indeed going bad and would need to be replaced. Recommended Action: If battery is suspected change the battery. WBEM EventID: WBEM ProviderName: integrated Light Out firmware software error. Probable Cause: A software error was detected and is being logged. The internal data is connected to the location and module where the error occurred. The Forward Progress Log may receive additional (lower alert level) event entries with more data associated with this event. Recommended Action: Review logs, and monitor system health. WBEM EventID: WBEM ProviderName: 100 WBEM Provider Event Tables

101 Power was forced to ON without permission from the Onboard Administrator. Probable Cause: A forced power on occurred. Usually this is performed when a normal power on request is denied. The Onboard Administrator may now be running in a non-redundant or over-budget power configuration. Recommended Action: Make sure Onboard Administrator has the appropriate number and configuration of power supplies. Reduce power required by the blade (for instance, remove some memory or a CPU.) Or, if there are powered-on blades that are not in use, power them off. WBEM EventID: WBEM ProviderName: Integrated Lights Out unable to communicate with OA after multiple retries. Probable Cause: ilo has repeatedly requested communication with the Onboard Administrator and has not received a response. This may be because the EM has a fault condition, or is busy, being reset, or removed. Recommended Action: The communication loss may have been temporary and nothing needs to be done if the communication is now working. Check the Fault LED on the enclosure manager. Reset the enclosure manager. Reset ilo. Replace the enclosure manager. WBEM EventID: WBEM ProviderName: System Firmware internal error detected resulting in execution of ASSERT macro. Probable Cause: The cause is unknown. Recommended Action: Examine previous events and ASCII information following this event for more information. Ensure firmware is at the current supported revision. If problem persists, contact support. WBEM EventID: WBEM ProviderName: System Firmware internal error detected resulting in execution of ASSERT macro. Probable Cause: The cause is unknown. Recommended Action: Examine previous events and ASCII information following this event for more information. If problem persists, contact support. WBEM EventID: WBEM ProviderName: System Firmware internal ASSERT source code line number. WBEM EventID: WBEM ProviderName: System Firmware internal ASSERT module name. Probable Cause: Assert has been encountered. Recommended Action: Assemble the module name and line information. Contact support with this information. WBEM EventID: WBEM ProviderName: Thread has failed Early Self-test and is now operating with degraded performance. Probable Cause: Thread has failed early self-test. Recommended Action: Reboot the system. If the problem persists, contact support for help to replace the CPU. WBEM EventID: WBEM ProviderName: The PDH Controller has experienced an unexpected reboot. Probable Cause: The PDHC kernel detected a HW or SW error that causes the PDHC kernel to crash. Recommended Action: Decode the event payload for specific crash reason. WBEM EventID: WBEM ProviderName: Failed to notify manageability of a change to the real-time-clock device. Probable Cause: The EFI subsystem could not notify manageability of a change to the real-time-clock device. Recommended Action: Verify Firmware is at the current supported revision. Reset the system. WBEM EventID: WBEM ProviderName: ACPI parser error due to a missing AML identifier. Probable Cause: The ACPI subsystem could not find the doorbell AML identifier while parsing the DSDT table. Recommended Action: Ensure FW is at the current supported revison. WBEM EventID: WBEM ProviderName: Memory Configuration rendevous failed. Probable Cause: Read from non-volatile memory failed. Recommended Action: Verify the FW is at current supported revision. Reset the system and attempt to reboot again. If problem persists, contact support. WBEM EventID: WBEM ProviderName: Platform Events 101

102 ilo was unable to initialize user accounts. Probable Cause: ilo was unable to read the default user account data from EEPROM. The default user data contained in the EEPROM was likely bad, or the checksum failed. Recommended Action: There is no factory default password at this point- all passwords will be refused. Use the physical presence button to force ilo into security override mode. This will allow you to log into ilo without a user account. Use the UC command or web GUI to setup ilo user account(s) again. WBEM EventID: WBEM ProviderName: SFW discarded one or more in progress SFW events before they got logged by ilo. Probable Cause: The SFW event queue overflowed and remained that way for a duration of time. This could result from poor ilo queue draining (logging) performance, or could be related to the number of event being issued by SFW in a short period of time. Recommended Action: None. WBEM EventID: WBEM ProviderName: The ilo config was unexpectedly defaulted. Settings may need to be re-entered. Probable Cause: Some bad data in the ilo config area of NVRAM was detected and as a result config was defaulted. It is not believe that this was caused by a battery failure or user action. Recommended Action: Re-enter any lost configuration data. WBEM EventID: WBEM ProviderName: The local blade failed to power off upon request. Probable Cause: This blade has failed to power off. Recommended Action: Try resetting ilo and attempting power off again. WBEM EventID: WBEM ProviderName: The system has failed to power off upon request. Probable Cause: the rack or one or more blades have failed to power off. The overall power off action has failed as a result. Recommended Action: reset ilo and attempt power off again. WBEM EventID: WBEM ProviderName: A data table stored in non-volatile RAM is invalid. Probable Cause: Manageability or System FW revisions are out of date or corrupted. Recommended Action: Ensure that all firmware is at the correct supported version. WBEM EventID: WBEM ProviderName: The system has lost AC power. Probable Cause: Most likely cause is removal of an AC power cord, or a bulk power supply failure. Recommended Action: Make sure that the AC Power cord is properly installed, and the bulk power supply is functional. WBEM EventID: WBEM ProviderName: The chassis has been open for an extended period of time. Probable Cause: The chassis dorr or top cover is open. More specifically it has been open for an extended period of time. Recommended Action: Close the door or top cover. WBEM EventID: WBEM ProviderName: The Power Button was asserted prior to changing the system power. Probable Cause: The power button must be released before remotely controlling system power. The button may be stuck. Recommended Action: Inspect the power button and correct anything which may affect its proper operation. WBEM EventID: WBEM ProviderName: ICH failed to respond to an i2c query. Probable Cause: The ICH device failed to respond to an i2c request. It is probable that the ICH device is in a failed state. Recommended Action: Investigate the ICH MEZZ card to determine if there has been a failure. WBEM EventID: WBEM ProviderName: Hardware configuration exceeds available power. Probable Cause: Power supply has limited capability and detected hardware configuration exceeds the power capability. Recommended Action: Reduce the hardware configuration, or connect power supplies to higher voltage. WBEM EventID: WBEM ProviderName: Excessive processor corrected errors. Probable Cause: Processor module is failing or failed. Recommended Action: Replace the processor module. WBEM EventID: WBEM ProviderName: 102 WBEM Provider Event Tables

103 A processor has mapped out all spare cache lines. Probable Cause: The processor is not functioning properly due to excessive cache errors. Recommended Action: Replace the processor. The processor is at physical location. WBEM EventID: WBEM ProviderName: A measured voltage in the server has gone far outside the factory specified lower voltage range. Probable Cause: The voltage in the server has gone outside the factory set range. A bad component, blown fuse, poorly seated module, loose cable, or debris could be responsible for this failure. Recommended Action: Check all boards, power supplies, and modules that either supply or use this voltage rail. WBEM EventID: 113. WBEM ProviderName: SEL02_IndicationProvider. Voltage sensor crossed lower non-recoverable threshold. Probable Cause: The voltage in the server has gone far outside the factory set range and could damage system components. A bad component, blown fuse, poorly seated module, loose cable, or debris could be responsible for this failure. Recommended Action: Check all boards, power supplies, and modules that either supply or use this voltage rail. WBEM EventID: 114. WBEM ProviderName: SEL02_IndicationProvider. A measured voltage in the server has gone outside the factory specified upper voltage range. Probable Cause: The voltage in the server has gone outside the factory set range. A bad component, blown fuse, poorly seated module, loose cable, or debris could be responsible for this failure. Recommended Action: Check all boards, power supplies, and modules that either supply or use this voltage rail. WBEM EventID: 115. WBEM ProviderName: SEL02_IndicationProvider. Voltage sensor crossed upper non-recoverable threshold. Probable Cause: The voltage in the server has gone far outside the factory set range and could damage system components. A bad component, blown fuse, poorly seated module, loose cable, or debris could be responsible for this failure. Recommended Action: Check all boards, power supplies, and modules that either supply or use this voltage rail. WBEM EventID: 116. WBEM ProviderName: SEL02_IndicationProvider. The server's built-in sensors have detected an open chassis door. Probable Cause: The server has detect that the chassis door or other access panel is not securely closed. Recommended Action: Close any open panels or chassis doors. WBEM EventID: 127. WBEM ProviderName: SEL02_IndicationProvider. Hot Swap Cage: SCSI cable removed. Probable Cause: This alert indicates that a SCSI cable, Jumper or Duplex Connector has either been disconnected or removed. This may make some SCSI devices inaccessible. Recommended Action: Ensure that all the required SCSI cables, jumpers or duplex connectors are correctly connected to the cage, disks, and/or the controller. WBEM EventID: 174. WBEM ProviderName: SEL02_IndicationProvider. Power Pod Voltage Fault. Probable Cause: The voltage in the server has gone outside the factory set range. A bad component, blown fuse, poorly seated module, loose cable, or debris could be responsible for this failure. Recommended Action: Check all boards, power supplies, and modules that either supply or use this voltage rail. WBEM EventID: 121. WBEM ProviderName: SEL02_IndicationProvider. Machine Check Initiated. Probable Cause: A Machine Check Abort event means the hardware detected a critical error. This event is generated whenever a system error due to processor, firmware, hardware and operating system is encountered. MCA events may be either recoverable or non-recoverable. If it is recoverable, the system will attempt to recover from the error for the purpose of maintaining high availability. An example of which is automatic disabling of a failing processor. For non-recoverable errors, the system will either stop or reboot to prevent data corruption and unreliable operation. Recommended Action: When this event is generated, it is highly advisable to consult both the operating system and hardware event logs to find out if there are other events that may help identify the cause of the MCA. If an MCA event occurs that causes the system to reboot, the failing component may be automatically disabled and the system continue to run but at a degraded performance level while awaiting repair. Therefore, for an MCA event, HP recommends contacting HP Customer Support to determine if a repair is needed. WBEM EventID: 173. WBEM ProviderName: SEL02_IndicationProvider. Platform Events 103

104 Generic trap for Critical or Fatal type E0 event from system firmware. Probable Cause: This event is generated when a critical or fatal event has occurred as reported by system firmware. The server is not operational and is in a state where it cannot provide more details about the failure. To obtain more information, log into the server's Management Processor Card and look at the event log for more details on the failure. Recommended Action: Contact HP Support for best course of action. HP may require a reboot, reconfiguration, or reflash of firmware. WBEM EventID: 162. WBEM ProviderName: SEL02_IndicationProvider. INIT Initiated. Probable Cause: The critical interrupt sensor has detected that there was a Diagnostic Interrupt initiated by IPMI command. Either the Transfer Of Control (TOC) button was pressed or the interrupt was initiated remotely. The system will reboot after the interrupt processing is finished. Recommended Action: If this is unexpected behavior, then check logs for events that would have caused an INIT, TOC, or RESET. WBEM EventID: 170. WBEM ProviderName: SEL02_IndicationProvider. Voltage insufficient. Probable Cause: The input voltage for the system is not sufficient for operation. Recommended Action: Check all boards, power supplies, and modules that either supply or use this voltage rail. WBEM EventID: 118. WBEM ProviderName: SEL02_IndicationProvider. Voltage reached critical level. Probable Cause: The voltage in the server has gone outside the factory set range. A bad component, blown fuse, poorly seated module, loose cable, or debris could be responsible for this failure. Recommended Action: When this condition was detected the system should have been immediately shutdown to avoid damage. Contact your HP support representative as soon as possible to have the unit checked. Check all boards, power supplies, and modules that either supply or use this voltage rail. WBEM EventID: 120. WBEM ProviderName: SEL02_IndicationProvider. Voltage absent. Probable Cause: There is either a missing or failed power component. This may be a normal message when a system is not loaded to capacity and power components are purposefully left out of the system. Recommended Action: If this is unexpected, then check all boards, power supplies, and modules that either supply or use this voltage rail. WBEM EventID: 122. WBEM ProviderName: SEL02_IndicationProvider. Fan speed lags. Probable Cause: Possibly, the specified fan is beginning to lose performance. Recommended Action: If these errors continue to be reported, the fan should be replaced. WBEM EventID: 126. WBEM ProviderName: SEL02_IndicationProvider. OS run-time critical shutdown. Probable Cause: The OS caused the system to shut down. Recommended Action: Look at OS logs and crash data to determine why the system shut down. WBEM EventID: 175. WBEM ProviderName: SEL02_IndicationProvider. Power supply failure. Probable Cause: The system has detected that one of the power supplies has failed. Recommended Action: The power cable has been disconnected. Reconnect, or The power supply has failed. Contact your HP support representative to check the power supply. WBEM EventID: 137. WBEM ProviderName: SEL02_IndicationProvider. Power supply AC lost. Probable Cause: The power supply has lost its A/C source. The power supply is not connected to a working A/C power source. Recommended Action: Verify that the plug is connected to the power supply, and to a working power source. WBEM EventID: 139. WBEM ProviderName: SEL02_IndicationProvider. Cooling unit warning. Probable Cause: The Cooling Unit may be running properly now, but it was detected in a degraded state. It may need to be replaced in the future. Recommended Action: Continue to monitor unit and contact HP support to determine appropriate action. WBEM EventID: 157. WBEM ProviderName: SEL02_IndicationProvider. Cooling unit failure. Probable Cause: A cooling unit has failed. Recommended Action: Replace the indicated cooling unit. WBEM EventID: 158. WBEM ProviderName: SEL02_IndicationProvider. 104 WBEM Provider Event Tables

105 System event log almost full. Probable Cause: The System Event Log is almost full. Recommended Action: Review the log for any important events, then clear it. WBEM EventID: 163. WBEM ProviderName: SEL02_IndicationProvider. BMC entering special mode. Probable Cause: BMC entering special mode. The system is not operating in a normal configuration. Some protection features may be disabled in this mode. Recommended Action: The Special Mode must be exited to ensure proper operation of the server. WBEM EventID: 166. WBEM ProviderName: SEL02_IndicationProvider. TOC interrupt (crash dump). Probable Cause: The critical interrupt sensor has detected that there was a Diagnostic Interrupt initiated by IPMI command. Either the Transfer Of Control (TOC) button was pressed or the interrupt was initiated remotely. The system will reboot after the interrupt processing is finished. Recommended Action: If this is unexpected behavior, then check logs for events that would have caused an INIT, TOC, or RESET. WBEM EventID: 169. WBEM ProviderName: SEL02_IndicationProvider. ACPI state S5 (soft-off, entered by override). Probable Cause: The system has been powered OFF with a hard power-down. Recommended Action: HP recommends that when you powered down the system you use the normal shutdown procedure to properly shut down the operating system. Otherwise, data-loss and/or hardware failure can occur. WBEM EventID: 176. WBEM ProviderName: SEL02_IndicationProvider. Watchdog timer expired - hard reset. Probable Cause: Watchdog timer expired, and a hard reset of the system occurred. Recommended Action: Some process took longer than it should. Identify that process and contact the vendor of that application. WBEM EventID: 178. WBEM ProviderName: SEL02_IndicationProvider. Watchdog timer expired - power-off. Probable Cause: Watchdog timer expired, and the system was powered-off. Recommended Action: Some process took longer than it should. Identify that process and contact the vendor of that application. WBEM EventID: 179. WBEM ProviderName: SEL02_IndicationProvider. Watchdog timer expired - power-cycle. Probable Cause: Watchdog timer expired, and the system was power-cycled. Recommended Action: Some process took longer than it should. Identify that process and contact the vendor of that application. WBEM EventID: 180. WBEM ProviderName: SEL02_IndicationProvider. Missing FRU device. Probable Cause: A required device was not detected. See the System Event Log (SEL). Recommended Action: Install missing, required device. WBEM EventID: 182. WBEM ProviderName: SEL02_IndicationProvider. Missing Entity. Probable Cause: A required device was not detected. Recommended Action: Install missing, required device. WBEM EventID: 183. WBEM ProviderName: SEL02_IndicationProvider. PCI parity error detected. Probable Cause: An I/O device (or host bridge) detected a bus parity error, OR An I/O device (or host bridge) mastered a bus transaction and received a parity error response from the target. Recommended Action: For an I/O bus parity error, consult the error logs for additional information. Determine and replace the failed I/O device. For an I/O host bridge failure, contact your HP representative to check the I/O host bridge. WBEM EventID: 171. WBEM ProviderName: SEL02_IndicationProvider. PCI system error detected. Probable Cause: An I/O device (or host bridge) detected an internal error. OR An I/O device (or host bridge) detected a bus error. Recommended Action: For an I/O device failure, consult the error logs for additional information. Determine and replace the failed I/O device. For an I/O host bridge failure, contact your HP representative to check the I/O host bridge. WBEM EventID: 172. WBEM ProviderName: SEL02_IndicationProvider. Power failure in power supply. Probable Cause: Indicates a failure with the AC power source that is connected to one of the redundant power supply units. Recommended Action: Check the power cord or source voltage. WBEM EventID: 155. WBEM ProviderName: SEL02_IndicationProvider. Platform Events 105

106 Voltage reached critical level. Probable Cause: The voltage in the server has gone outside the factory set range. A bad component, blown fuse, poorly seated module, loose cable, or debris could be responsible for this failure. Recommended Action: Check all boards, power supplies, and modules that either supply or use this voltage rail. WBEM EventID: 119. WBEM ProviderName: SEL02_IndicationProvider. System shut-down or reset caused by sensor reading. Probable Cause: A sensor reading in the system was determined to be non-recoverable and the system was shut down or reset. Recommended Action: Read the system logs to find which sensor was out of range. WBEM EventID: 167. WBEM ProviderName: SEL02_IndicationProvider. The BMC firmware did not detect the system firmware boot. Probable Cause: Possible Causes: 1. Bad System Firmware image in ROM 2. Power not reaching processors 3. Processor is in reset or is not properly seated in system 4. An unsupported processor was inserted in system 5. Communication with BMC is impaired. Recommended Action: To correct the problem, try the following: 1. Validate that processors are supported in this system. 2. Verify that processors are seated properly in system. 3. Check if system has booted (only a communication problem. - future events will also be lost.) 4. Attempt a system reset, INIT, and/or A/C cycle to clear the problem. 5. Update system firmware again if necessary. WBEM EventID: 132. WBEM ProviderName: SEL02_IndicationProvider. A/C Power failed, disconnected, or out of range. Probable Cause: The input power to the supply has failed or gone out of range. Or the input cord has been disconnected. Recommended Action: Check the power cord or source voltage. WBEM EventID: 154. WBEM ProviderName: SEL02_IndicationProvider. The power supply sensors detect a possible problem. Probable Cause: The power supply fan(s) is slowing. Recommended Action: Check power supply fan(s). WBEM EventID: 138. WBEM ProviderName: SEL02_IndicationProvider. Uncorrectable multi-bit ECC error has occurred. Probable Cause: There has been an ECC double-bit error in one of the server's ECC memory modules. When an ECC double-bit memory error is detected, the system generates a Non-Maskable Interrupt that halts the system to prevent errors from propagating to other subsystems. Data being written or transmitted at the time may have been lost. Recommended Action: Make a note of the failed memory bank/board number and slot number, contact HP support to replace the failed module. WBEM EventID: 159. WBEM ProviderName: SEL02_IndicationProvider. Temperature sensor crossed upper non-critical threshold. Probable Cause: The temperature inside the server has gone outside the factory specified range for normal operation. You should quit applications and power down the server to protect its hardware from damage. This event may indicate one of the following conditions: A failed fan, blocked air vents or poor ventilation around the server, open server chassis cover, or missing drive slot covers, high temperature in the room where the server resides, an unusually hot hardware component located near one of the server's temperature sensors. Recommended Action: You should quit applications and shutdown the system. Find cause of temperature anomaly and fix it. WBEM EventID: 100. WBEM ProviderName: SEL02_IndicationProvider. A temperature inside the server went far outside the factory specified range. Probable Cause: The temperature inside the server has gone far outside the factory specified range for normal operation. To avoid permanent damage to your server hardware, go and turn off the server immediately. This event may indicate one of the following conditions: a failed fan blocked air vents or poor ventilation around the server open server chassis cover, or missing drive slot covers high temperature in the room where the server resides an unusually hot hardware component located near one of the server's temperature sensors. Recommended Action: Shutdown the system immediately. Find cause of temperature anomaly and fix it. WBEM EventID: 101. WBEM ProviderName: SEL02_IndicationProvider. 106 WBEM Provider Event Tables

107 Temperature sensor crossed upper non-recoverable threshold. Probable Cause: The temperature inside the server has gone far outside the factory specified range for normal operation. To avoid permanent damage to your server hardware, go and turn off the server immediately. This event may indicate one of the following conditions: a failed fan blocked air vents or poor ventilation around the server open server chassis cover, or missing drive slot covers high temperature in the room where the server resides an unusually hot hardware component located near one of the server's temperature sensors. Recommended Action: Shutdown the system immediately. Find cause of temperature anomaly and fix it. WBEM EventID: 102. WBEM ProviderName: SEL02_IndicationProvider. One of the temperature sensors crossed its upper non-critical threshold. Probable Cause: The temperature inside the server has gone outside the factory specified range for normal operation. This event may indicate one of the following conditions: a failed fan blocked air vents or poor ventilation around the server open server chassis cover, or missing drive slot covers high temperature in the room where the server resides an unusually hot hardware component located near one of the server's temperature sensors. Recommended Action: You should quit applications and shutdown the system.find cause of temperature anomaly and fix it. WBEM EventID: 107. WBEM ProviderName: SEL02_IndicationProvider. A temperature inside the server went far outside the factory specified range. Probable Cause: The temperature inside the server has gone far outside the factory specified range for normal operation. To avoid permanent damage to your server hardware, go and turn off the server immediately. This event may indicate one of the following conditions: a failed fan blocked air vents or poor ventilation around the server open server chassis cover, or missing drive slot covers high temperature in the room where the server resides an unusually hot hardware component located near one of the server's temperature sensors. Recommended Action: Shutdown the system immediately. Find cause of temperature anomaly and fix it. WBEM EventID: 108. WBEM ProviderName: SEL02_IndicationProvider. The AC voltage to the power supply was lost or is out of range. Probable Cause: The AC voltage was lost, or is the wrong range for the system. Recommended Action: Verify the power supply is plugged in to the proper voltage for the system. WBEM EventID: 140. WBEM ProviderName: SEL02_IndicationProvider. The power supply AC voltage is out of range. Probable Cause: The AC voltage is connected to the power supply, but it is not the voltage range required for the system. Recommended Action: Connect the power supply to the proper voltage range. WBEM EventID: 141. WBEM ProviderName: SEL02_IndicationProvider. HP Ethernet Events Source in Windows Event Log: HP Ethernet Event ID Event Severity Information Information Event Description An Ethernet provider encountered an unrecoverable error. A network interface has failed. An Ethernet adapter's status changed from OK to, or an Ethernet team's status changed to from another state. A failed network interface was restored. An Ethernet port's status changed from an state to a non- state. An Ethernet team's redundancy has decreased. A team member has changed to failed or degraded state. An Ethernet team's redundancy status changed to Redundancy Lost. All members of an Ethernet team, except one, are failed. An Ethernet team's redundancy has increased. A team member recovered from a failed or degraded state. HP Ethernet Events 107

108 Information Information Information Information Information Information Information A new team member has been added to an Ethernet team via the HP Network Configuration Utility (NCU). This is an optional indication that can be disabled via the Ethernet Event Provider settings. A team member was dropped from the team via the HP Network Configuration Utility (NCU). This is an optional indication that can be disabled via the Ethernet Event Provider settings. An Ethernet Team member's role has changed. This is an optional indication that can be disabled via the Ethernet Event Provider settings. An Ethernet team member's status has changed. This is an optional indication that can be disabled via the Ethernet Event Provider settings. A new network interface is available. An Ethernet adapter has been added or an Ethernet team or VLAN has been created. This is an optional indication that can be disabled via the Ethernet Event Provider settings. A network interface is no longer available. An Ethernet adapter was removed or an Ethernet team or VLAN was removed via the HP Network Configuration Utility (NCU). The number of active adapters in an Ethernet team has changed. This is an optional indication that can be disabled via the Ethernet Event Provider settings. The event provider encountered a non-fatal error. Some information may not be available. An Ethernet team's redundancy status changed to Fully Redundant. An Ethernet team member status changed from or Degraded to OK. HP Fiber Channel Events Source in Windows Event Log: HP Fiber Channel Event ID 2 6 Event Severity Information Event Description This fiber channel HBA port has returned to a status of OK. A fiber channel HBA port has changed to a state of link down. HP SAS Events Source in Windows Event Log: HP SAS Event ID Event Severity Information Information Information Information Event Description A SAS/SATA HBA status has changed from non-ok to OK. A SAS/SATA HBA status has changed to. A logical drive status has changed from non-ok to OK. A logical drive status has changed to. A logical drive is in a degraded state. Device is still servicing I/O, but redundancy may be degraded or lost. A physical drive status has changed from non-ok to OK. A physical drive status has changed to. A physical drive status has changed to Rebuilding. Data is now being rebuilt onto this drive from the RAID set. A physical drive status has changed to Predictive Failure. 108 WBEM Provider Event Tables

109 Information Information Information A Storage Enclosure Power Subsystem status has changed to non-redundant. A Storage Enclosure Power Supply has changed to Fully Redundant. A Storage Enclosure Power Supply status has changed to Degraded Redundancy. A Storage Enclosure Fan status has changed from a non-ok state to OK. A Storage Enclosure Fan status has changed to Degraded. An enclosure has detected there may a problem with one or more of the fans. A Storage Enclosure Fan status changed to Failure. An enclosure has detected a failure in the fan subsystem and there is insufficient fan capability to ensure normal operation. A Storage Enclosure Temperature sensor status changed from non-ok to OK. A Storage Enclosure Temperature sensor status changed to Condition. This indicates the enclosure temperature is above normal, otherwise enclosure is still operating normally. A Storage Enclosure Temperature sensor status has changed to Critical. An enclosure temperature is reaching the maximum allowed temperature for normal operation. A shutdown is imminent. Action is required before loss of data occurs. HP SCSI Events Source in Windows Event Log: HP SCSI Event ID Event Severity Information Information Information Information Information Information Information Information Information Event Description A SCSI device status has changed to Unknown. This SCSI HBA status has changed from non-ok to OK. A SCSI HBA status has changed to. A SCSI physical drive status has changed from non-ok to OK. A SCSI physical drive has a status of. A SCSI physical drive with a status of OK that was located in the system has been removed. A SCSI physical drive with a status of that was located in the system has been removed. A SCSI physical drive status is now set to Predictive Failure. A SCSI physical drive with a status of Predictive Failure that was located in the system has been removed. A SCSI physical drive is offline and can no longer return data. No further status is available. A SCSI physical drive that was located in the system and had a status of offline has been removed. A Storage Enclosure Power Supply status has changed to non-redundant. A Storage Enclosure Power Supply has changed to Fully Redundant. A Storage Enclosure Power Supply status has changed to Degraded Redundancy. The storage enclosure fan subsystem is operating properly. A fan has failed, but there are enough fans in the fan subsystem to keep the enclosure cool. HP SCSI Events 109

110 Information A fan has failed and there are not enough fans in the fan subsystem to keep the enclosure cool. A Storage Enclosure Temperature sensor status changed from non-ok to OK. A Storage Enclosure Temperature sensor Status changed to Condition. This indicates the enclosure temperature is above normal, otherwise enclosure is still operating normally. A Storage Enclosure Temperature sensor status has changed to Critical. An enclosure temperature is reaching the maximum allowed temperature for normal operation. A shutdown is imminent. Action is required before loss of data occurs. HP Smart Array Events Source in Windows Event Log: HP Smart Array Event ID Event Severity Information Information Information Information Information Information Information Information Information Event Description A Smart Array controller status has changed from non-ok to OK. A Smart Array controller status has changed to. A Smart Array controller redundancy state has changed from Standby to Active. A Smart Array controller has detected that redundancy has been lost due to failure or loss of communication with partner controller. Controller has detected that Redundancy has been restored and can communicate with partner controller. A Smart Array controller Battery status has changed from non-ok to OK. A Smart Array controller Battery status has changed to Not Fully Charged. A Smart Array controller battery status changed to Failed. A Smart Array controller Cache status has changed from non-ok to OK. A Smart Array controller Cache status has changed to Temporarily Disabled. This may be caused by a rebuild or configuration change. Normal operation will return after background operations have completed. A Smart Array controller Cache status has changed to Permanently Disabled. The controller has detected a problem with the cache and has disabled the cache permanently. A logical drive status has changed from a non-ok state to OK. A logical drive status has changed to. A logical drive is in a degraded state. Device is still servicing I/O but redundancy may be degraded or lost. A physical drive status has changed from a non-ok state to OK. A physical drive status has changed to. A physical drive status has changed to Rebuilding. Data is now being rebuilt onto this drive from the RAID set. A physical drive status has changed to Predictive Failure. A Storage Enclosure Power Subsystem status has changed to non-redundant. A Storage Enclosure Power Supply has changed to Fully Redundant. A Storage Enclosure Power Supply status has changed to Degraded Redundancy. A Storage Enclosure Fan status has changed from a non-ok state to OK. 110 WBEM Provider Event Tables

111 Information A Storage Enclosure Fan status has changed to Degraded. An enclosure has detected there may a problem with one or more of the fans. A Storage Enclosure Fan status changed to Failure. An enclosure has detected a failure in the fan subsystem and there is insufficient fan capability to ensure normal operation. A Storage Enclosure Temperature sensor status changed from non-ok to OK. A Storage Enclosure Temperature sensor status changed to Condition. This indicates the enclosure temperature is above normal, otherwise enclosure is still operating normally. A Storage Enclosure Temperature sensor status has changed to Critical. An enclosure temperature is reaching the maximum allowed temperature for normal operation. A shutdown is imminent. Action is required before loss of data occurs. Server Provider (SysEvt) Events Source in Windows Event Log: HP System Event ID 2001 Event Severity Information Event Description HP Insight Management WBEM Providers have started. HP System Management Homepage Events Source in Windows Event Log: HP System Management Homepage Event ID Event Severity Information Information Event Description The HP System Management Homepage Win32 service has been started successfully. The HP System Management Homepage Win32 service has been stopped successfully. The HP System Management Homepage Win32 service could not be started successfully. The HP System Management Homepage Win32 service could not be stopped successfully HP Event Sync Events Source in Windows Event Log: HpInsightMgmtProvs Event ID Event Severity Success Information Event Description %1 The service version %2 has started. %3%1 - "[component name]"%2 - "version"%3 - "See [log file] for details." %1 The service has stopped. %2%1 - "[component name]"%2 - "See [log file] for details." %1 Could not start %2 sub-service. %3%1 - "[component name]"%2 - "sub-service name"%3 - "See [log file] for details. %1 Failed to initialize service: %2. %3%1 - "[component name]"%2 - "error code"%3 - "See [log file] for details." %1 Failed to initialize API: %2. %3%1 - "[component name]"%2 - "EventApi"%3 - "See [log file] for details." Server Provider (SysEvt) Events 111

112 Event ID Event Severity Event Description %1 An exception occurred: %2. %3%1 - "[component name]"%2 - "exception error message"%3 - "See [log file] for details." %1 The %2 service was finished unexpectedly. %3%1 - "[component name]"%2 - "service name"%3 - "See [log file] for details. %1 Could not register with the Service Control Manager. %2%1 - "[component name]"%2 - "See [log file] for details. %1 Could not set the service status with the Service Control Manager. %2%1 - "[component name]"%2 - "See [log file] for details. %1 File access failure: %2. %3%1 - "[component name]"%2 - " reading from softlog file"%3 - "See [log file] for details. %1 IPMI initialization failure. %2%1 - "[component name]"%2 - "See [log file] for details." %1 An IPMI communication error occurred: %2. %3%1 - "[component name]"%2 - "error code"%3 - "See [log file] for details. %1 WMI usage error. %2%1 - "[component name]"%2 - "See [log file] for details. %1 processing notified %2 event. %3%1 - "[component name]"%2 - "FPL"%3 - "See [log file] for details." %1 processing notified %2 event. %3%1 - "[component name]"%2 - "SEL"%3 - "See [log file] for details." HP BMC IPMI Driver Events Source in Windows Event Log: hpipmi Event ID Event Severity Information Event Description During communication with the IPMI BMC device, the system detected that the BMC entered an error state. The driver attempted to set the BMC state to a working state but failed to do so. After 20 successive attempts, the driver has set the IPMI device to a non working state. It is recommended that you seek assistance from Hewlett-Packard. You can return the device instance to the working state by disabling and enabling the IPMI device instance labeled Hewlett-Packard IPMI Device. You can locate the IPMI device instance within the Device Manager user interface. A IPMI device was not recognized or detected, the IPMI device driver was not loaded. The IPMI driver read a registry parameter that was invalid, the driver used a default value for the registry parameter HKLM\SYSTEM\CurrentControlSet\Control\IPMI\%2. The IPMI device driver attempted to communicate with the IPMI BMC device during device creation. However the communication failed due to a timeout. Either the configured timeouts are too small and the IPMI BMC device responses take longer than the timeouts or the BMC has a technical fault. You can increase the timeouts associated with the IPMI device driver. The IPMI device driver attempted to communicate with the IPMI BMC device during normal operation. However the communication failed due to a timeout. You can try increasing the timeouts associated with the IPMI device driver located in the registry at HKLM\SYSTEM\CurrentControlSet\Control\IPMI\CommandWaitTimeoutPeriod, between (5 seconds) to (30 seconds), the default is 10 seconds. \Device\CpqHlth, The Hewlett Packard IPMI device driver was loaded. 112 WBEM Provider Event Tables

113 Event ID Event Severity Event Description The Hewlett Packard IPMI device driver could not load. NTSTATUS return code is shown in data field. Make sure you have the latest version of the driver. The IPMI device driver could not open the IML soft log in the windows registry: %2. Make sure HP Insight Management Agents or HP Insight Management WBEM Providers are installed. PFM Events Source in Windows Event Log: HpPfmSvcEx Event ID Event Severity Information Information Information Information Information Information Information Information Information Information Event Description A Corrected Machine Check (or Corrected Platform ) error of an unknown variety was observed by the PreFail Monitor. This error was corrected and no action is necessary, but if this condition repeats contact HP for support guidance. HP PFM has detected an invalid HP PFM rules file. As the result, default monitoring threshold values are being used. Please contact HP support team to solve this problem. HP PFM service detected the DIMM module in %s has been added. HP PFM service detected the DIMM module in %s has been removed. HP PFM service detected the DIMM module in %s has been replaced. HP PFM has detected a module replacement: The DIMM %s has been replaced. The serial number of the older module was %s and the serial number of the newer is %s. HP PFM service detected the CPU module in %s has been added. HP PFM service detected the CPU module in %s has been removed. HP PFM service detected the CPU module in %s has been replaced. HP PFM has detected a module replacement: The CPU %s has been replaced. The serial number of the older module was %s and the serial number of the newer is %s. The Predictive Failure Monitor sub-service version %s has started. The Predictive Failure Monitor sub-service has stopped. PFM cannot initialize WMI interface. Please check WMI service status. hpwbemdump Events Source in Windows Event Log: hpwbemdump Event ID Event Severity Information Event Description HP WBEM data was captured and compressed as a raw data format.%noriginal Size=%1, Compressed Size=%2, WMI Queries=%3, WMI Instances=%4, WMI Properties=%5, Num Entries=%6, Entry=%7, Date=%8, Time=%9.%nAll succeeded. HP WBEM data was captured and compressed as a raw data format.%noriginal Size=%1, Compressed Size=%2, WMI Queries=%3, WMI Instances=%4, WMI Properties=%5, Num Entries=%6, Entry=%7, Date=%8, Time=%9.%nFailed class List:%n%10 PFM Events 113