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: docsfeedback@hp.com 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