IPMI Forward Progress Log Monitor (Events)

Event 200

Severity: MAJOR_WARNING

Event Summary: Bad OS MCA checksum

Event Class: System

Problem Description:
The OS has registered an OS_MCA vector, but it has not passed the checksum

Cause / Action:
Cause: OS has registered a bad OS_MCA vector or the data has been lost. Action: Reboot system to allow vector to be re-registered.

Automated Recovery: None

Event Generation Threshold: 1 occurrence

Event Details:
Examples:
Event 201

Severity: MAJOR_WARNING

Event Summary: BMC interface to IPMI failed

Event Class: System

Problem Description:
The BMC has failed testing and has been disabled.

Cause / Action:
Cause: BMC firmware has locked up or the BMC is disabled. Action: Cycle system power and attempt boot again. If error re-occurs contact your HP representative for support.

Automated Recovery: None

Event Generation Threshold: 1 occurrence

Event Details:
Examples:
Event 203

Severity: CRITICAL

Event Summary: Boot cell launch EFI failure

Event Class: System

Problem Description:
SFW failed to launch EFI

Cause / Action:
Cause: The system has failed to launch EFI because of an internal error.

Automated Recovery: None

Event Generation Threshold: 1 occurrence

Event Details:
Examples:
Event 204

Severity: MAJOR_WARNING

Event Summary: Monarch selection failure

Event Class: System

Problem Description:
0x11 = Calibration Failure 0x22 = Select Code Failure

Cause / Action:
Cause: An internal error has caused monarch selection to fail. Action: Reboot system, swap processors if failure persists.

Automated Recovery: None

Event Generation Threshold: 1 occurrence

Event Details:
Examples:
Event 205

Severity: MAJOR_WARNING

Event Summary: CPU monarch collision

Event Class: System

Problem Description:
Monarch Collision has occurred

Cause / Action:
Cause: Unexpected error has occurred during monarch selection. Action: Reboot, if problem persists contact your HP representative for support.

Automated Recovery: None

Event Generation Threshold: 1 occurrence

Event Details:
Examples:
Event 207

Severity: CRITICAL

Event Summary: Boot cell virtualize EFI failure

Event Class: System

Problem Description:
SFW attempted to virtualize EFI and failed

Cause / Action:
Cause: An internal error has occurred that prevented EFI from virtualizing. Action: Reboot, if problem persists contact your HP representative for support.

Automated Recovery: None

Event Generation Threshold: 1 occurrence

Event Details:
Examples:
Event 208

Severity: CRITICAL

Event Summary: Boot cell virtualize PAL failure

Event Class: System

Problem Description:
SFW was unable to virtualize PAL

Cause / Action:
Cause: SFW was unable to virtualize PAL. Action: Reboot, if problem persists contact your HP representative for support.

Automated Recovery: None

Event Generation Threshold: 1 occurrence

Event Details:
Examples:
Event 209

Severity: CRITICAL

Event Summary: Boot cell virtualize SAL failure

Event Class: System

Problem Description:
SFW was unable to virtualize SAL

Cause / Action:
Cause: SFW was unable to virtualize SAL. Action: Reboot, if problem persists contact your HP representative for support.

Automated Recovery: None

Event Generation Threshold: 1 occurrence

Event Details:
Examples:
Event 210

Severity: CRITICAL

Event Summary: Boot cell virtualize SALPROC failure

Event Class: System

Problem Description:
SFW was unable to virtualize SALPROC

Cause / Action:
Cause: SFW was unable to virtualize SALPROC. Action: Reboot, if problem persists contact your HP representative for support.

Automated Recovery: None

Event Generation Threshold: 1 occurrence

Event Details:
Examples:
Event 211

Severity: MAJOR_WARNING

Event Summary: CPU struct init failed

Event Class: System

Problem Description:
SFW has failed initializing the CPU Struct.

Cause / Action:
Cause: A CPU has failed the configuration process. Action: Replace CPU. If problem persists contact your HP representative for support.

Automated Recovery: None

Event Generation Threshold: 1 occurrence

Event Details:
Examples:
Event 212

Severity: MAJOR_WARNING

Event Summary: CPU failed early config

Event Class: System

Problem Description:
A CPU has failed early config.

Cause / Action:
Cause: A CPU has failed the early configuration process. Action: Replace CPU. If problem persists contact your HP representative for support.

Automated Recovery: None

Event Generation Threshold: 1 occurrence

Event Details:
Examples:
Event 213

Severity: MAJOR_WARNING

Event Summary: CPU failed early selftest

Event Class: System

Problem Description:
A CPU has failed early self test. Data: PAL Test State.

Cause / Action:
Cause: A CPU has failed early self test. Action: Replace CPU. If problem persists contact your HP representative for support.

Automated Recovery: None

Event Generation Threshold: 1 occurrence

Event Details:
Examples:
Event 214

Severity: MAJOR_WARNING

Event Summary: CPU failed

Event Class: System

Problem Description:
SFW has detected that a CPU has failed. Data: the local CPU number that failed.

Cause / Action:
Cause: A CPU has failed. Action: Replace CPU. If problem persists contact your HP representative for support.

Automated Recovery: None

Event Generation Threshold: 1 occurrence

Event Details:
Examples:
Event 215

Severity: MAJOR_WARNING

Event Summary: CPU failed late selftest

Event Class: System

Problem Description:
SFW has determined a CPU or Memory has failed late test. This could be related to a CPU error or a Correctable Single Bit Memory error. See Cause/Action.

Cause / Action:
Cause 1: 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. Action 1: 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. Cause2: A CPU has failed. Action2: Replace CPU. If problem persists contact your HP representative for support.

Automated Recovery: None

Event Generation Threshold: 1 occurrence

Event Details:
Examples:
Event 216

Severity: MAJOR_WARNING

Event Summary: CPU not enough late test memory

Event Class: System

Problem Description:
The CPU late test has failed because of insufficient memory

Cause / Action:
Cause: Insufficient memory Action: Increase memory and reboot.

Automated Recovery: None

Event Generation Threshold: 1 occurrence

Event Details:
Examples:
Event 217

Severity: CRITICAL

Event Summary: Could not allocate memory for EFI image

Event Class: System

Problem Description:
Could not allocate memory for EFI image

Cause / Action:
Cause: SFW could not allocate enough memory for EFI image. Action: Replace/Add memory.

Automated Recovery: None

Event Generation Threshold: 1 occurrence

Event Details:
Examples:
Event 218

Severity: CRITICAL

Event Summary: EFI image corrupted

Event Class: System

Problem Description:
EFI image is corrupted

Cause / Action:
Cause: EFI image is corrupted. Action: Reflash ROM if applicable, if problem persists contact your HP representative for support.

Automated Recovery: None

Event Generation Threshold: 1 occurrence

Event Details:
Examples:
Event 219

Severity: CRITICAL

Event Summary: EFI not in fit table

Event Class: System

Problem Description:
EFI fit error

Cause / Action:
Cause: EFI image is not in FIT. Action: Reflash ROM if applicable, if problem persists contact your HP representative for support.

Automated Recovery: None

Event Generation Threshold: 1 occurrence

Event Details:
Examples:
Event 220

Severity: CRITICAL

Event Summary: NVRAM test fail

Event Class: System

Problem Description:
EFI NVM has failed testing. The cell will now halt.

Cause / Action:
Cause: NVM is corrupted or bad. Action: Clear NVM, if problem persists contact your HP representative for support.

Automated Recovery: None

Event Generation Threshold: 1 occurrence

Event Details:
Examples:
Event 221

Severity: CRITICAL

Event Summary: EFI Rom size bad

Event Class: System

Problem Description:
EFI Image Error

Cause / Action:
Cause: EFI image is corrupt. Action: Reflash ROM if applicable, if problem persists contact your HP representative for support.

Automated Recovery: None

Event Generation Threshold: 1 occurrence

Event Details:
Examples:
Event 222

Severity: CRITICAL

Event Summary: EFI Rom checksum error

Event Class: System

Problem Description:
EFI Image Error.

Cause / Action:
Cause: EFI image is corrupt. Action: Reflash ROM if applicable, if problem persists contact your HP representative for support.

Automated Recovery: None

Event Generation Threshold: 1 occurrence

Event Details:
Examples:
Event 223

Severity: CRITICAL

Event Summary: External interruption nest limit exceeded

Event Class: System

Problem Description:
The IVT interrupting nesting depth has been exceeded. This processor will be halted Data: Number of the offending vector

Cause / Action:
Cause: Internal FW error.

Automated Recovery: None

Event Generation Threshold: 1 occurrence

Event Details:
Examples:
Event 224

Severity: CRITICAL

Event Summary: External interrupt not serviced

Event Class: System

Problem Description:
An external interrupt has been requested and not serviced. Data: Number of the vector

Cause / Action:
Cause: Internal FW error.

Automated Recovery: None

Event Generation Threshold: 1 occurrence

Event Details:
Examples:
Event 225

Severity: CRITICAL

Event Summary: Ext int taken

Event Class: System

Problem Description:
An external interrupt has been taken. Data: Number of the vector taken.

Cause / Action:
Cause: An external interrupt has been taken Action: None

Automated Recovery: None

Event Generation Threshold: 1 occurrence

Event Details:
Examples:
Event 226

Severity: MAJOR_WARNING

Event Summary: Forward Progress Log (FPL) access failed

Event Class: System

Problem Description:
Access to the FPL has failed.

Cause / Action:
Cause: FPL access has failed.

Automated Recovery: None

Event Generation Threshold: 1 occurrence

Event Details:
Examples:
Event 227

Severity: CRITICAL

Event Summary: PSR fetch failure

Event Class: System

Problem Description:
SFW was unable to read the CPU PSR. Data: Local CPU number

Cause / Action:
Cause: SFW was unable to read the CPU PSR. Action: Replace CPU.

Automated Recovery: None

Event Generation Threshold: 1 occurrence

Event Details:
Examples:
Event 228

Severity: CRITICAL

Event Summary: Cell halt

Event Class: System

Problem Description:
SFW has halted the cell

Cause / Action:
Cause: Internal Error Action: contact your HP representative for support.

Automated Recovery: None

Event Generation Threshold: 1 occurrence

Event Details:
Examples:
Event 229

Severity: MAJOR_WARNING

Event Summary: CPU PAL incompatible with cpu

Event Class: System

Problem Description:
SFW has determined that PAL is not compatible with the current processors.

Cause / Action:
Cause: Incompatible PAL. Action: Update PAL or change processors

Automated Recovery: None

Event Generation Threshold: 1 occurrence

Event Details:
Examples:
Event 230

Severity: MAJOR_WARNING

Event Summary: Slave is incompatible with monarch

Event Class: System

Problem Description:
SFW has determined that a slave processor is incompatible with the monarch. Data: Physical location of the incompatible processor.

Cause / Action:
Cause: Incompatible processors. Action: Replace processors.

Automated Recovery: None

Event Generation Threshold: 1 occurrence

Event Details:
Examples:
Event 231

Severity: MAJOR_WARNING

Event Summary: Interrupt clear failure

Event Class: System

Problem Description:
Interrupt clear failed during cell config

Cause / Action:
Cause: Interrupt clear failed. Action: Reboot, if problem persists contact your HP representative for support.

Automated Recovery: None

Event Generation Threshold: 1 occurrence

Event Details:
Examples:
Event 232

Severity: MAJOR_WARNING

Event Summary: System Event Log (SEL) access failed

Event Class: System

Problem Description:
SFW has determined that an IPMI event failed.

Cause / Action:
Cause: An IPMI event has failed. Action: None

Automated Recovery: None

Event Generation Threshold: 1 occurrence

Event Details:
Examples:
Event 233

Severity: CRITICAL

Event Summary: Trap taken

Event Class: System

Problem Description:
Data: IVT Offset

Cause / Action:
Cause: This will follow other events indicating some type of IVT error. Action: This event is for debugging the address, other events will determine the user action.

Automated Recovery: None

Event Generation Threshold: 1 occurrence

Event Details:
Examples:
Event 234

Severity: MAJOR_WARNING

Event Summary: LDB State bad on entry

Event Class: System

Problem Description:
LDB state bad

Cause / Action:
Action: None required.

Automated Recovery: None

Event Generation Threshold: 1 occurrence

Event Details:
Examples:
Event 235

Severity: CRITICAL

Event Summary: Interrupt with ic bit clear

Event Class: System

Problem Description:
Interrupt context was lost Data: interrupt number.

Cause / Action:
Cause: Interrupt context was lost. Action: none

Automated Recovery: None

Event Generation Threshold: 1 occurrence

Event Details:
Examples:
Event 236

Severity: CRITICAL

Event Summary: Min-state registration failure

Event Class: System

Problem Description:
Registering of the processor min state save area with PAL has failed.

Cause / Action:
Cause: Registering of the processor min state save area with PAL has failed. Action: Replace processor, if problem persists contact your HP representative for support.

Automated Recovery: None

Event Generation Threshold: 1 occurrence

Event Details:
Examples:
Event 237

Severity: MAJOR_WARNING

Event Summary: CPU mismatched boot type

Event Class: System

Problem Description:
An invalid boot type has been requested.

Cause / Action:
Cause: An internal error has occurred. Action: None

Automated Recovery: None

Event Generation Threshold: 1 occurrence

Event Details:
Examples:
Event 238

Severity: MAJOR_WARNING

Event Summary: Boot monarch timed out

Event Class: System

Problem Description:
SFW has determined the monarch has timed out Data: Local CPU Number

Cause / Action:
Cause: The monarch has timed out. Action: None, Replace CPU if problem persists, system will reboot after this event.

Automated Recovery: None

Event Generation Threshold: 1 occurrence

Event Details:
Examples:
Event 239

Severity: CRITICAL

Event Summary: PAL_B not in FIT table

Event Class: System

Problem Description:
A PAL_B FIT error has occurred

Cause / Action:
Cause: Internal Error or ROM is corrupted. Action: Reflash ROM if applicable, if problem persists contact your HP representative for support.

Automated Recovery: None

Event Generation Threshold: 1 occurrence

Event Details:
Examples:
Event 240

Severity: CRITICAL

Event Summary: SAL_B not in FIT table

Event Class: System

Problem Description:
A SAL_B FIT error has occurred

Cause / Action:
Cause: Internal Error or ROM is corrupted. Action: Reflash ROM if applicable, if problem persists contact your HP representative for support.

Automated Recovery: None

Event Generation Threshold: 1 occurrence

Event Details:
Examples:
Event 241

Severity: CRITICAL

Event Summary: NVRAM test fail

Event Class: System

Problem Description:
NVM has failed test. The system will halt

Cause / Action:
Cause: NVM is corrupt or bad. Action: Reboot, if problem persists contact your HP representative for support.

Automated Recovery: None

Event Generation Threshold: 1 occurrence

Event Details:
Examples:
Event 242

Severity: CRITICAL

Event Summary: Interrupt vector out of range

Event Class: System

Problem Description:
A interrupt vector has been requested out of the acceptable range. Data: Vector Number.

Cause / Action:
Cause: An internal error has occurred

Automated Recovery: None

Event Generation Threshold: 1 occurrence

Event Details:
Examples:
Event 243

Severity: CRITICAL

Event Summary: Pal proc error getting pal copy info

Event Class: System

Problem Description:
The PAL Copy Info call has failed

Cause / Action:
Cause: An internal error has occurred.

Automated Recovery: None

Event Generation Threshold: 1 occurrence

Event Details:
Examples:
Event 244

Severity: CRITICAL

Event Summary: Pal proc error copying pal to memory

Event Class: System

Problem Description:
Error coping PAL to memory

Cause / Action:
Cause: There has been an error copying PAL to memory. Action: Reboot, if problem persists contact your HP representative for support.

Automated Recovery: None

Event Generation Threshold: 1 occurrence

Event Details:
Examples:
Event 245

Severity: MAJOR_WARNING

Event Summary: Boot pal proc failure

Event Class: System

Problem Description:
A PAL Proc has failed. This will halt the processor. Data: Local CPU Number

Cause / Action:
Cause: Internal PAL Error. Action: Reboot, if problem persists contact your HP representative for support.

Automated Recovery: None

Event Generation Threshold: 1 occurrence

Event Details:
Examples:
Event 246

Severity: MAJOR_WARNING

Event Summary: Console device failure

Event Class: System

Problem Description:
A console device has failed. Data: Physical Addr of device that failed.

Cause / Action:
Cause: A console device has failed. Action: Reset console device/system.

Automated Recovery: None

Event Generation Threshold: 1 occurrence

Event Details:
Examples:
Event 247

Severity: MAJOR_WARNING

Event Summary: Platform interface device failure

Event Class: System

Problem Description:
A console device has failed. Data: Physical Addr of device that failed.

Cause / Action:
Cause: A console device has failed. Action: Reset console device/system.

Automated Recovery: None

Event Generation Threshold: 1 occurrence

Event Details:
Examples:
Event 248

Severity: MAJOR_WARNING

Event Summary: platform scratch RAM test failed

Event Class: System

Problem Description:
Platfrom Scratch RAM has failed the test.

Cause / Action:
Cause: Bad or corrupt Scratch RAM. Action: Reboot, if problem persists contact your HP representative for support.

Automated Recovery: None

Event Generation Threshold: 1 occurrence

Event Details:
Examples:
Event 249

Severity: MAJOR_WARNING

Event Summary: CPU rendezvous failure

Event Class: System

Problem Description:
A CPU has failed to meet rendezvous. Data: Local CPU Number

Cause / Action:
Cause: Bad or slow CPU. Action: Replace CPU.

Automated Recovery: None

Event Generation Threshold: 1 occurrence

Event Details:
Examples:
Event 250

Severity: CRITICAL

Event Summary: Error extracting sal_b from rom

Event Class: System

Problem Description:
SFW could not extract SAL_B from the ROM

Cause / Action:
Cause: ROM Corrupt or unreadable. Action: Reflash ROM if applicable, if problem persists contact your HP representative for support.

Automated Recovery: None

Event Generation Threshold: 1 occurrence

Event Details:
Examples:
Event 251

Severity: CRITICAL

Event Summary: Scratch RAM bad

Event Class: System

Problem Description:
Platform Scratch RAM has failed test.

Cause / Action:
Cause: Bad or corrupt Scratch RAM. Action: Reboot, if problem persists contact your HP representative for support.

Automated Recovery: None

Event Generation Threshold: 1 occurrence

Event Details:
Examples:
Event 252

Severity: MAJOR_WARNING

Event Summary: IPMI System Event Log (SEL) is full

Event Class: System

Problem Description:
IPMI SEL full

Cause / Action:
Cause: IPMI SEL full. Action: Clear SEL through BMC or MP.

Automated Recovery: None

Event Generation Threshold: 1 occurrence

Event Details:
Examples:
Event 253

Severity: MAJOR_WARNING

Event Summary: Slave wakeup before vector registered

Event Class: System

Problem Description:
No wakeup vector registered for processor Data: Local CPU Number

Cause / Action:
Cause: No wakeup vector registered for processor. Action: Reboot, if problem persists contact your HP representative for support.

Automated Recovery: None

Event Generation Threshold: 1 occurrence

Event Details:
Examples:
Event 254

Severity: MAJOR_WARNING

Event Summary: CPU failed rendezvous handler

Event Class: System

Problem Description:
Slave Rendezvous handler has failed. Data: Local CPU Number.

Cause / Action:
Cause: Internal Error. Action: Reboot, if problem persists contact your HP representative for support.

Automated Recovery: None

Event Generation Threshold: 1 occurrence

Event Details:
Examples:
Event 255

Severity: CRITICAL

Event Summary: Error building SMBIOS Tables

Event Class: System

Problem Description:
SFW failed to build the SMBIOS tables

Cause / Action:
Cause: SFW failed to build the SMBIOS tables. Action: None, if SMBIOS is preventing functionality, reboot. If problem persists contact your HP representative for support.

Automated Recovery: None

Event Generation Threshold: 1 occurrence

Event Details:
Examples:
Event 256

Severity: CRITICAL

Event Summary: Trap nest limit exceeded

Event Class: System

Problem Description:
The trap nesting limit has been exceeded. Data: Vector Number

Cause / Action:
Cause: The trap nesting limit has been exceeded. Action: Reboot if necessary, if problem persists contact your HP representative for support.

Automated Recovery: None

Event Generation Threshold: 1 occurrence

Event Details:
Examples:
Event 257

Severity: CRITICAL

Event Summary: Trap not serviced

Event Class: System

Problem Description:
A trap has been requested and not serviced. Data: Vector Number

Cause / Action:
Cause: A invalid trap has been requested or a trap has not been installed. Action: Reboot if necessary, if problem persists contact your HP representative for support.

Automated Recovery: None

Event Generation Threshold: 1 occurrence

Event Details:
Examples:
Event 258

Severity: CRITICAL

Event Summary: Trap taken

Event Class: System

Problem Description:
A trap has been taken. Data: Number of the vector taken.

Cause / Action:
Cause: A trap has been taken Action: None

Automated Recovery: None

Event Generation Threshold: 1 occurrence

Event Details:
Examples:
Event 259

Severity: MAJOR_WARNING

Event Summary: Uncleared interrupt

Event Class: System

Problem Description:
At least one interrupt was not cleared. Data: The highest pending interrupt number

Cause / Action:
Cause: At least one interrupt was not cleared. Action: None.

Automated Recovery: None

Event Generation Threshold: 1 occurrence

Event Details:
Examples:
Event 260

Severity: CRITICAL

Event Summary: Unexpected external interrupt

Event Class: System

Problem Description:
An unexpected external interrupt has occurred. Data: External Interrupt Number

Cause / Action:
Cause: An unexpected external interrupt has occurred. Action: None.

Automated Recovery: None

Event Generation Threshold: 1 occurrence

Event Details:
Examples:
Event 261

Severity: CRITICAL

Event Summary: Interrupt before redirection table set up

Event Class: System

Problem Description:
An interrupt has occurred before setting up the IVT. Data: Interrupt Number

Cause / Action:
Cause: An interrupt has occurred before setting up the IVT. Action: None.

Automated Recovery: None

Event Generation Threshold: 1 occurrence

Event Details:
Examples:
Event 262

Severity: CRITICAL

Event Summary: CPU unexpected MCA

Event Class: System

Problem Description:
An unexpected MCA has occurred before MCA's are unmasked. Data: Local CPU Number.

Cause / Action:
Cause: Unexpected MCA Action: None

Automated Recovery: None

Event Generation Threshold: 1 occurrence

Event Details:
Examples:
Event 263

Severity: CRITICAL

Event Summary: Unexpected trap

Event Class: System

Problem Description:
An unexpected trap has occurred. The trap number is either invalid or the requested trap has not been registered. Data: Trap Number

Cause / Action:
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. Action: 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.

Automated Recovery: None

Event Generation Threshold: 1 occurrence

Event Details:
Examples:
Event 264

Severity: CRITICAL

Event Summary: CPU unknown boot error

Event Class: System

Problem Description:
SFW has detected an unknown error.

Cause / Action:
Cause: unknown error. Action: None, if problem persists contact your HP representative for support.

Automated Recovery: None

Event Generation Threshold: 1 occurrence

Event Details:
Examples:
Event 265

Severity: MAJOR_WARNING

Event Summary: CC errors PAL failure

Event Class: System

Problem Description:
SFW has detected a PAL Failure

Cause / Action:
Cause: SFW has detected a PAL Failure. Action: Reboot if necessary, if problem persists contact your HP representative for support.

Automated Recovery: None

Event Generation Threshold: 1 occurrence

Event Details:
Examples:
Event 266

Severity: MAJOR_WARNING

Event Summary: Expected MC vector unregistered

Event Class: System

Problem Description:
Expected Machine Check Vector not registered

Cause / Action:
Cause: Expected Machine Check Vector not registered at the time of an Expected Machine Check

Automated Recovery: None

Event Generation Threshold: 1 occurrence

Event Details:
Examples:
Event 267

Severity: CRITICAL

Event Summary: INIT initiated

Event Class: System

Problem Description:
This is the equivalent of a TOC event in the PA RISC Architecture. On IPF systems, this event is called an INIT. This event can be triggered by the "tc" command from the MP, or from the button labeled "TOC" :wor "Transfer of Control" on the Management card or bezel of the system. There are also other causes of an INIT generated by software. Data: Local CPU Number

Cause / Action:
Cause: Software has requested an INIT or the INIT button has been pressed. Action: None

Automated Recovery: None

Event Generation Threshold: 1 occurrence

Event Details:
Examples:
Event 268

Severity: MAJOR_WARNING

Event Summary: Expected I/O host bridge is missing

Event Class: System

Problem Description:
An I/O host bridge is missing. Firmware will continue boot and display the following EFI warning, "Unexpected hardware I/O configuration." Data Field: Physical location of the missing I/O host bridge.

Cause / Action:
Cause: I/O host bridge failure. An incorrect I/O backplane is installed. Action: Contact your HP representative to check the I/O host bridge and the I/O backplane.

Automated Recovery: None

Event Generation Threshold: 1 occurrence

Event Details:
Examples:
Event 269

Severity: MAJOR_WARNING

Event Summary: LBA has unexpected number of I/O slots

Event Class: System

Problem Description:
Firmware detected an unexpected number of I/O slots connected to an I/O host bridge. Firmware display the following EFI warning message, "Unexpected hardware I/O configuration." Data Field: Physical location of the I/O host bridge.

Cause / Action:
Cause: The firmware needs to be updated. An incorrect I/O backplane is installed. Action: Contact your HP representative to check the firmware and the I/O backplane.

Automated Recovery: None

Event Generation Threshold: 1 occurrence

Event Details:
Examples:
Event 270

Severity: MAJOR_WARNING

Event Summary: I/O rope width does not match expected value

Event Class: System

Problem Description:
Firmware found an I/O controller rope of unexpected width. Firmware will configure the I/O host bridge connected to the rope and display the following EFI warning message, "Unexpected hardware I/O configuration." Data Field: Physical location of the I/O host bridge connected to the rope.

Cause / Action:
Cause: The firmware needs to be updated. An incorrect I/O backplane is installed. Action: Contact your HP representative to check the firmware and the I/O backplane.

Automated Recovery: None

Event Generation Threshold: 1 occurrence

Event Details:
Examples:
Event 271

Severity: MAJOR_WARNING

Event Summary: Found unexpected I/O host bridge

Event Class: System

Problem Description:
Firmware found an unexpected I/O host bridge. Firmware will configure the I/O host bridge and display the following EFI warning message, "Unexpected hardware I/O configuration." Data Field: Physical location of the unexpected I/O host bridge.

Cause / Action:
Cause: The firmware needs to be updated. An incorrect I/O backplane is installed. Action: Contact your HP representative to check the firmware and the I/O backplane.

Automated Recovery: None

Event Generation Threshold: 1 occurrence

Event Details:
Examples:
Event 272

Severity: MAJOR_WARNING

Event Summary: PCI clock DLL error

Event Class: System

Problem Description:
An I/O host bridge's bus frequency DLL circuit failed. Firmware will deconfigure the failed I/O host bridge and display the following EFI warning message, "Failed I/O slot(s) deconfigured." Data Field: Physical location of the I/O host bridge.

Cause / Action:
Cause: Failed or improperly inserted I/O card. Action: Remove or reseat the I/O card. Cause: Failed I/O chipset. Failed I/O backplane. Action: Contact your HP representative to check the I/O chipset and backplane.

Automated Recovery: None

Event Generation Threshold: 1 occurrence

Event Details:
Examples:
Event 273

Severity: MAJOR_WARNING

Event Summary: PCI hot plug controller failed

Event Class: System

Problem Description:
An I/O host bridge's hot-plug controller has failed. Firmware will deconfigure the I/O host bridge and display the following EFI warning message, "Failed I/O slot(s) deconfigured." Data Field: Physical location of the I/O hostbridge.

Cause / Action:
Cause: Hot-plug controller failure. I/O host bridge failure. Action: Contact your HP representative to check the hot-plug controller and the I/O host bridge.

Automated Recovery: None

Event Generation Threshold: 1 occurrence

Event Details:
Examples:
Event 274

Severity: MAJOR_WARNING

Event Summary: Found unknown I/O rope width

Event Class: System

Problem Description:
Firmware attempts to configure an I/O controller rope to an unsupported width. Firmware will deconfigure any I/O host bridge connected to the rope. Data Field: Physical location of the failed rope.

Cause / Action:
Cause: Internal firmware error. Action: Contact your HP representative to check the firmware.

Automated Recovery: None

Event Generation Threshold: 1 occurrence

Event Details:
Examples:
Event 275

Severity: MAJOR_WARNING

Event Summary: I/O LBA clear error failed

Event Class: System

Problem Description:
During I/O host bridge configuration, firmware found a persistent error condition. Firmware will deconfigure the I/O host bridge and display the following EFI warning message, "Failed I/O slot(s) deconfigured." Data Field: Physical location of the I/O hostbridge.

Cause / Action:
Cause: A failed or improperly seated I/O card is present. Action: Replace or reseat the I/O card(s). Cause: I/O host bridge failure. Action: Contact your HP representative to check the I/O host bridge.

Automated Recovery: None

Event Generation Threshold: 1 occurrence

Event Details:
Examples:
Event 276

Severity: MAJOR_WARNING

Event Summary: I/O host bridge inaccessible because rope reset failed to complete

Event Class: System

Problem Description:
An I/O host bridge is inaccessible because an I/O controller rope reset failed to complete. Firmware will deconfigure the I/O host bridge and display the following EFI warning message, "Failed I/O slot(s) deconfigured." Data Field: Physical location of the I/O host bridge.

Cause / Action:
Cause: I/O chipset failure. Action: Contact your HP representative to check the I/O chipset.

Automated Recovery: None

Event Generation Threshold: 1 occurrence

Event Details:
Examples:
Event 277

Severity: MAJOR_WARNING

Event Summary: Insufficient power to turn on PCI slot

Event Class: System

Problem Description:
There is insufficient power. Firmware will not power on a hot-plug I/O slot. In addition, firmware will display the following EFI warning message, "Failed I/O slot(s) deconfigured." Date Field: Physical location of the I/O slot.

Cause / Action:
Cause: The power budget is exceeded. Action: Install an additional power supply on the system.

Automated Recovery: None

Event Generation Threshold: 1 occurrence

Event Details:
Examples:
Event 278

Severity: MAJOR_WARNING

Event Summary: PCI bus walk unknown error

Event Class: System

Problem Description:
Firmware encountered an unexpected error while attempting to configure an I/O host bridge's I/O devices. Firmware will continue boot but will not configure the I/O devices connected to the specified I/O host bridge. Such I/O devices will not be usable as console nor boot devices but might be usable by the O/S. Data Field: Physical location of the I/O host bridge.

Cause / Action:
Cause: Internal firmware error. Action: Contact your HP representative to check the firmware.

Automated Recovery: None

Event Generation Threshold: 1 occurrence

Event Details:
Examples:
Event 279

Severity: MAJOR_WARNING

Event Summary: PCI bus walk resources exceeded

Event Class: System

Problem Description:
The total resource requirement from the I/O devices connected to an I/O host bridge exceeds the resource limit of the I/O host bridge. Firmware will continue boot but will not configure the I/O devices connected to the specified I/O host bridge. In addition, firmware will display the following EFI warning message, "Insufficient resources to assign to one or more I/O devices." Such I/O devices will not be usable as console nor boot devices but might be usable by the O/S. Data Field: Physical location of the I/O host bridge.

Cause / Action:
Cause: Unsupported I/O configuration. Action: Remove any unsupported I/O cards. Move the I/O card to another slot.

Automated Recovery: None

Event Generation Threshold: 1 occurrence

Event Details:
Examples:
Event 280

Severity: MAJOR_WARNING

Event Summary: PCI bus unmap unknown error

Event Class: System

Problem Description:
Firmware encountered an unexpected error while attempting to clear resource allocations on an I/O host bridge's I/O devices. Data Field: Physical location of the I/O host bridge.

Cause / Action:
Cause: Internal firmware error. Action: Contact your HP representative to check the firmware.

Automated Recovery: None

Event Generation Threshold: 1 occurrence

Event Details:
Examples:
Event 281

Severity: MAJOR_WARNING

Event Summary: PCIXCAP sampling error

Event Class: System

Problem Description:
An I/O host bridge failed to determine the appropriate PCI[X] mode and frequency (PCI, PCI-X 66 MHz, PCI-X 133 MHz, etc.) for its bus. Firmware will deconfigure the I/O host bridge and display the following EFI warning message, "Failed I/O slot(s) deconfigured." Data Field: Physical location of the failed I/O host bridge.

Cause / Action:
Cause: I/O host bridge failure. Action: Contact your HP representative to check the I/O host bridge.

Automated Recovery: None

Event Generation Threshold: 1 occurrence

Event Details:
Examples:
Event 282

Severity: MAJOR_WARNING

Event Summary: Power monitor failed to respond

Event Class: System

Problem Description:
Firmware is unable to access the power monitor. Firmware will assume that there is sufficient power and proceed to power on an I/O slot. Data Field: Physical location of the I/O slot.

Cause / Action:
Cause: BMC failure. Action: Contact your HP representative to check the BMC.

Automated Recovery: None

Event Generation Threshold: 1 occurrence

Event Details:
Examples:
Event 283

Severity: MAJOR_WARNING

Event Summary: I/O rope reset failed to complete

Event Class: System

Problem Description:
An I/O controller rope reset did not complete within the expected time limit. Firmware will deconfigure the I/O host bridge attached to the rope. Data Field: Physical location of the deconfigured I/O host bridge.

Cause / Action:
Cause: I/O chipset failure. Action: Contact your HP representative to check the I/O controller.

Automated Recovery: None

Event Generation Threshold: 1 occurrence

Event Details:
Examples:
Event 284

Severity: MAJOR_WARNING

Event Summary: I/O SBA clear error failed

Event Class: System

Problem Description:
During I/O chipset configuration, firmware found a persistent error condition. Firmware will attempt to continue the boot. Data Field: Physical location of the I/O chipset.

Cause / Action:
Cause: I/O chipset failure. Action: Contact your HP representative to check the I/O chipset.

Automated Recovery: None

Event Generation Threshold: 1 occurrence

Event Details:
Examples:
Event 285

Severity: MAJOR_WARNING

Event Summary: PCI slot has incorrect default power state

Event Class: System

Problem Description:
During boot, firmware has found a hot-plug I/O slot with an incorrect default power state. The slot power should be off by default. Data Field: Physical location of the I/O slot.

Cause / Action:
Cause: A non-compliant PCI[X] card is inserted in the slot. Such cards leaks power to the PCI[X] bus, which violates the PCI Bus Specification. Action: Replace the card with a compliant card. Cause: The hot-plug controller has failed. Action: Contact your HP representative to check the hot-plug slot.

Automated Recovery: None

Event Generation Threshold: 1 occurrence

Event Details:
Examples:
Event 286

Severity: MAJOR_WARNING

Event Summary: PCI slot power on error

Event Class: System

Problem Description:
Firmware encountered an error while attempting to power on an I/O slot. Firmware will deconfigure the I/O slot and display the following EFI warning message, "Failed I/O slot(s) deconfigured." Data Field: Physical location of the I/O slot.

Cause / Action:
Cause: The I/O card is damaged or improperly inserted. Action: Replace or reseat the I/O card. Cause: The hot-plug controller has failed. Action: Contact your HP representative to check the hot-plug slot.

Automated Recovery: None

Event Generation Threshold: 1 occurrence

Event Details:
Examples:
Event 287

Severity: MAJOR_WARNING

Event Summary: PCI slot's standby power failed

Event Class: System

Problem Description:
An I/O slot's standby (Vaux) power has failed. Firmware will deconfigure the I/O slot and display the following EFI warning message, "Failed I/O slot(s) deconfigured." Data Field: Physical location of the failed I/O slot.

Cause / Action:
Cause: I/O slot failure. Action: Contact your HP representative to check the I/O slot.

Automated Recovery: None

Event Generation Threshold: 1 occurrence

Event Details:
Examples:
Event 288

Severity: MAJOR_WARNING

Event Summary: Found invalid PCIXCAP value

Event Class: System

Problem Description:
An I/O host bridge or hot-plug controller reported an illegal PCI[X] bus mode for its bus or slot, respectively. Firmware will deconfigure the I/O host bridge or I/O slot and display the following EFI warning, "Failed I/O slot(s) deconfigured." Data Field: Physical location of the failed I/O host bridge or the failed I/O slot.

Cause / Action:
Cause: The I/O card is damaged or improperly inserted. Action: Replace or reseat the I/O card. Cause: I/O host bridge failure. Hot-plug controller failure. Action: Contact your HP representative to check the I/O host bridge or the hot-plug controller.

Automated Recovery: None

Event Generation Threshold: 1 occurrence

Event Details:
Examples:
Event 289

Severity: MAJOR_WARNING

Event Summary: Unsupported rope frequency

Event Class: System

Problem Description:
Firmware attempted to configure an I/O controller rope to an unsupported frequency. Firmware will deconfigure any I/O host bridge connected to the rope and display the following EFI warning message, "Failed I/O slot(s) deconfigured." Data Field: Physical location of the failed rope.

Cause / Action:
Cause: Internal firmware error. Action: Contact your HP representative to check the firmware.

Automated Recovery: None

Event Generation Threshold: 1 occurrence

Event Details:
Examples:
Event 290

Severity: MAJOR_WARNING

Event Summary: Unsupported host bridge type

Event Class: System

Problem Description:
Firmware has found an unsupported I/O host bridge type. Firmware will deconfigure the I/O host bridge and display the following EFI warning message, "Failed I/O slot(s) deconfigured." Data Field: Physical location of the I/O host bridge.

Cause / Action:
Cause: Firmware needs to be updated. An incorrect I/O backplane is installed. Action: Contact your HP representative to check the firmware and the I/O backplane.

Automated Recovery: None

Event Generation Threshold: 1 occurrence

Event Details:
Examples:
Event 291

Severity: CRITICAL

Event Summary: MC during INIT

Event Class: System

Problem Description:
Not Used

Cause / Action:
Not Used

Automated Recovery: None

Event Generation Threshold: 1 occurrence

Event Details:
Examples:
Event 292

Severity: CRITICAL

Event Summary: Machine Check initiated

Event Class: System

Problem Description:
A Machine Check has been initiated

Cause / Action:
Cause: A Machine Check has occurred. Action: Analyze cause of Machine Check using diag's and EFI tools.

Automated Recovery: None

Event Generation Threshold: 1 occurrence

Event Details:
Examples:
Event 293

Severity: CRITICAL

Event Summary: Error in temporary mdt area

Event Class: System

Problem Description:
There has been a problem building the MDT table.

Cause / Action:
Cause: MDT table bad. Action: Reboot if necessary, if problem persists contact your HP representative for support.

Automated Recovery: None

Event Generation Threshold: 1 occurrence

Event Details:
Examples:
Event 294

Severity: CRITICAL

Event Summary: Failed to find lmmio entry in mdt

Event Class: System

Problem Description:
There has been a problem building the MDT.

Cause / Action:
Cause: MDT table bad. Action: Reboot if necessary, if problem persists contact your HP representative for support.

Automated Recovery: None

Event Generation Threshold: 1 occurrence

Event Details:
Examples:
Event 295

Severity: CRITICAL

Event Summary: Memory page zero bad

Event Class: System

Problem Description:
Memory page 0 was slated for deallocation in the PDT. EFI cannot launch with page 0 bad, so the system will halt.

Cause / Action:
C: Memory page 0 was slated for deallocation in the PDT. A: FW is written such that this event should never be generated. If the user sees this event, please contact HP support.

Automated Recovery: None

Event Generation Threshold: 1 occurrence

Event Details:
Examples:
Event 296

Severity: CRITICAL

Event Summary: Failed to find space in mdt

Event Class: System

Problem Description:
There has been a problem building the MDT.

Cause / Action:
Cause: MDT table bad. Action: Reboot if necessary, if problem persists contact your HP representative for support.

Automated Recovery: None

Event Generation Threshold: 1 occurrence

Event Details:
Examples:
Event 297

Severity: MAJOR_WARNING

Event Summary: Media failure: info was not retrieved/logged

Event Class: System

Problem Description:
There has been a media failure.

Cause / Action:
Cause: The Error handler has failed to retrieve or log data due to a media failure. Action: Reboot if necessary, if problem persists contact your HP representative for support.

Automated Recovery: None

Event Generation Threshold: 1 occurrence

Event Details:
Examples:
Event 298

Severity: MAJOR_WARNING

Event Summary: Bus interface register test failed

Event Class: System

Problem Description:
Indicates that the chipset register test has failed. The data field contains the physical address of the failing register.

Cause / Action:
C: The chipset failed the register test. A: Contact HP support to troubleshoot the problem.

Automated Recovery: None

Event Generation Threshold: 1 occurrence

Event Details:
Examples:
Event 299

Severity: MAJOR_WARNING

Event Summary: Memory ECC normal write/read test failed

Event Class: System

Problem Description:
After FW's first access to main memory, FW detected that the CEC logged an error after reading back what was just written.

Cause / Action:
C: The DIMM that maps to cache line 0 is in a chipspare condition A: Contact HP support C: The DIMM that maps to address 0 is not seated properly A: 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 C: System may be running at the wrong frequency. A: Verify the system bus frequency and the memory bus frequency.

Automated Recovery: None

Event Generation Threshold: 1 occurrence

Event Details:
Examples:
Event 300

Severity: MAJOR_WARNING

Event Summary: DIMM loading order error: DIMM deallocated

Event Class: System

Problem Description:
A DIMM that is required to be loaded in order for this DIMM to function properly is not loaded, so FW will deallocate this DIMM. Currently, none of the platforms require any DIMMs to be loaded in order for this DIMM to work properly.

Cause / Action:
C: A required DIMM is not loaded in order to allow for proper operation of the DIMM specified in the physical location. A: Refer to the user's manual for Memory loading instructions.

Automated Recovery: None

Event Generation Threshold: 1 occurrence

Event Details:
Examples:
Event 301

Severity: MAJOR_WARNING

Event Summary: DIMM SPD checksum failed

Event Class: System

Problem Description:
The DIMM specified by the physical location has an SPD EEPROM that has a bad checksum. The Data field is the physical location of the DIMM.

Cause / Action:
C: The DIMMs SPD EEPROM got corrupted. A: Contact HP Support personnel to troubleshoot the problem

Automated Recovery: None

Event Generation Threshold: 1 occurrence

Event Details:
Examples:
Event 302

Severity: MAJOR_WARNING

Event Summary: DIMM SPD fatal error

Event Class: System

Problem Description:
Detected a fatal error in DIMM SPD

Cause / Action:
Cause: Detection of SPD fatal error type - various types Action: Contact HP Support personnel to troubleshoot the problem

Automated Recovery: None

Event Generation Threshold: 1 occurrence

Event Details:
Examples:
Event 303

Severity: MAJOR_WARNING

Event Summary: Unsupported memory DIMM type

Event Class: System

Problem Description:
A DIMM was installed whose DIMM type is not compatible with the current set of supported DIMMs for this platform.

Cause / Action:
Cause: A DIMM with an invalid DIMM type was found Action: Contact HP Support personnel to troubleshoot the problem

Automated Recovery: None

Event Generation Threshold: 1 occurrence

Event Details:
Examples:
Event 304

Severity: MAJOR_WARNING

Event Summary: The DIMM type of this DIMM doesn't match with others in the DIMM group

Event Class: System

Problem Description:
The DIMM type of this DIMM is not the same as the other DIMMs in the same group. The group of DIMMs is deallocated. If this is the last active group of DIMMs in the system, the system is halted.

Cause / Action:
Cause: The DIMMs in the rank do not have the same DIMM type Action: Contact HP Support personnel to troubleshoot the problem

Automated Recovery: None

Event Generation Threshold: 1 occurrence

Event Details:
Examples:
Event 305

Severity: MAJOR_WARNING

Event Summary: The DIMM type table is full. New DIMM type cannot be added.

Event Class: System

Problem Description:
The DIMM type table is full

Cause / Action:
C: Too many different types of DIMMs in system A: Reduce the number of different types of DIMMs in the system.

Automated Recovery: None

Event Generation Threshold: 1 occurrence

Event Details:
Examples:
Event 306

Severity: MAJOR_WARNING

Event Summary: DIMM number not found in DMT Table

Event Class: System

Problem Description:
An entry for the DIMM was not found in the DMT table. The data field contains the DMT entry that the caller wanted to find (in Dimm number format, which is 2 bytes, upper byte is the extender number, lower byte is the chipselect of the rank caller is looking for.)

Cause / Action:
C: Probable internal FW error A: Reload System Firmware A: Contact HP Support personnel to troubleshoot the problem

Automated Recovery: None

Event Generation Threshold: 1 occurrence

Event Details:
Examples:
Event 307

Severity: MAJOR_WARNING

Event Summary: Memory ECC multiple-bit data error detection failed

Event Class: System

Problem Description:
The FW selftest of CEC multi-bit error (MBE) detection has failed. The upper 32 bits of the data field contain the Dword offset within the cacheline of the failed MBE detection. The lower 32 bits are split in two, and they contain the bit numbers within the Dword that were flipped in order to cause an MBE.

Cause / Action:
C: The CEC failed MBE detection. A: Contact HP support personnel to troubleshoot the problem

Automated Recovery: None

Event Generation Threshold: 1 occurrence

Event Details:
Examples:
Event 308

Severity: MAJOR_WARNING

Event Summary: Memory ECC multiple-bit ECC error signaling failed

Event Class: System

Problem Description:
The FW selftest of CEC multi-bit error (MBE) signaling has failed. The upper 32 bits of the data field contain the Dword offset within the cacheline of the failed MBE detection. The lower 32 bits are split in two, and they contain the bit numbers within the Dword that were flipped in order to cause an MBE.

Cause / Action:
C: The CEC failed MBE detection. A: Contact HP support personnel to troubleshoot the problem

Automated Recovery: None

Event Generation Threshold: 1 occurrence

Event Details:
Examples:
Event 309

Severity: MAJOR_WARNING

Event Summary: Memory ECC single-bit data error detection failed

Event Class: System

Problem Description:
The FW selftest of CEC single-bit error (SBE) detection has failed. The data field contains the bit within the Dword that was flipped that caused the CEC to not see an SBE.

Cause / Action:
C: The CEC failed SBE detection. A: Contact HP support personnel to troubleshoot the problem

Automated Recovery: None

Event Generation Threshold: 1 occurrence

Event Details:
Examples:
Event 310

Severity: MAJOR_WARNING

Event Summary: Memory ECC single-bit ECC error detection failed

Event Class: System

Problem Description:
The FW selftest of CEC single-bit error (SBE) detection has failed. The data field contains the bit within the Dword that was flipped that caused the CEC to not see an SBE.

Cause / Action:
C: The CEC failed SBE detection. A: Contact HP support personnel to troubleshoot the problem

Automated Recovery: None

Event Generation Threshold: 1 occurrence

Event Details:
Examples:
Event 311

Severity: MAJOR_WARNING

Event Summary: Insufficient memory for operation

Event Class: System

Problem Description:
Memory FW detected errors below 1MB. FW will not allow boot in this case, so memory FW will reinterleave and retest.

Cause / Action:
C: FW detected memory errors below 1MB. A: None needed if FW recovers. If system will not boot, contact HP support to troubleshoot the problem.

Automated Recovery: None

Event Generation Threshold: 1 occurrence

Event Details:
Examples:
Event 312

Severity: MAJOR_WARNING

Event Summary: Memory address not found in MBAT

Event Class: System

Problem Description:
Memory FW could not figure out which rank maps to the physical address specified in the data field maps to.

Cause / Action:
C: The address logged in the CEC doesn't map to a memory rank, possibly due to a software error or NVM corruption A: Contact HP support to trouble shoot the problem.

Automated Recovery: None

Event Generation Threshold: 1 occurrence

Event Details:
Examples:
Event 313

Severity: MAJOR_WARNING

Event Summary: Memory Error Information not cleared

Event Class: System

Problem Description:
Memory FW was unable to clear the platform error logs on the CEC. The Datafield contains the error status of the CEC.

Cause / Action:
C: Software Error or CEC error A: Contact HP support to troubleshoot the problem

Automated Recovery: None

Event Generation Threshold: 1 occurrence

Event Details:
Examples:
Event 314

Severity: MAJOR_WARNING

Event Summary: Couldn't clear memory error logs

Event Class: System

Problem Description:
Memory FW was unable to clear the platform error logs on the CEC. The Datafield contains the error status of the CEC.

Cause / Action:
C: Software Error or CEC error A: Contact HP support to troubleshoot the problem

Automated Recovery: None

Event Generation Threshold: 1 occurrence

Event Details:
Examples:
Event 315

Severity: MAJOR_WARNING

Event Summary: Memory error clear failed

Event Class: System

Problem Description:
The Error registers in the CEC have failed to clear. The data field contains the error status of the CEC after the attempted clear.

Cause / Action:
C: Software error or CEC error A: Contact HP support to troubleshoot the problem

Automated Recovery: None

Event Generation Threshold: 1 occurrence

Event Details:
Examples:
Event 316

Severity: MAJOR_WARNING

Event Summary: DIMM loading order error: DIMM deallocated

Event Class: System

Problem Description:
A DIMM that is required to be loaded in order for this DIMM to function properly is not loaded, so FW will deallocate this DIMM. Currently, none of the platforms require any DIMMs to be loaded in order for this DIMM to work properly.

Cause / Action:
C: A required DIMM is not loaded in order to allow for proper operation of the DIMM specified in the physical location. A: Refer to the user's manual for Memory loading instructions.

Automated Recovery: None

Event Generation Threshold: 1 occurrence

Event Details:
Examples:
Event 317

Severity: MAJOR_WARNING

Event Summary: Generic memory firmware error

Event Class: System

Problem Description:
An error occurred that memory FW does not know how to handle.

Cause / Action:
C: Corrupt NVM or System firmware failure A: Contact HP support to troubleshoot the problem.

Automated Recovery: None

Event Generation Threshold: 1 occurrence

Event Details:
Examples:
Event 318

Severity: CRITICAL

Event Summary: Memory interleave generation failed

Event Class: System

Problem Description:
FW was unable to create a memory configuration with no errors in low memory to hand off to EFI.

Cause / Action:
C1: DIMM(s) that map into low memory have errors on them. A1: Contact HP support to troubleshoot the problem. C2: SFW is outdated. A2: Update SFW.

Automated Recovery: None

Event Generation Threshold: 1 occurrence

Event Details:
Examples:
Event 319

Severity: MAJOR_WARNING

Event Summary: Memory register test failed

Event Class: System

Problem Description:
The chipset's memory controller failed the register test. The data field contains the address of the register that failed selftest.

Cause / Action:
C1: The register within the chipset went bad. A1: Contact HP support to troubleshoot the problem C2: Internal SFW error. A2: Update to most recent SFW.

Automated Recovery: None

Event Generation Threshold: 1 occurrence

Event Details:
Examples:
Event 320

Severity: CRITICAL

Event Summary: SPD found no memory DIMMs

Event Class: System

Problem Description:
Memory Discovery could not detect any DIMMs installed.

Cause / Action:
Cause: No DIMMs were detected Action: Install DIMMs or Contact HP Support personnel to troubleshoot the problem

Automated Recovery: None

Event Generation Threshold: 1 occurrence

Event Details:
Examples:
Event 321

Severity: CRITICAL

Event Summary: No memory found

Event Class: System

Problem Description:
FW could not continue because there are no valid memory ranks loaded.

Cause / Action:
C: FW found memory, but it could not find a correctly loaded rank. A: 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.

Automated Recovery: None

Event Generation Threshold: 1 occurrence

Event Details:
Examples:
Event 322

Severity: CRITICAL

Event Summary: Cannot log memory error because PDT is disabled

Event Class: System

Problem Description:
The PDT has been disabled, and FW found memory errors during selftest. This is a stopboot condition. Also, the PDT will never be disabled in customer systems, so this event should never be seen in the field.

Cause / Action:
C: FW found memory errors during selftest, but could not deallocate the page because the PDT is disabled. A: Reenable the PDT by clearing NVM

Automated Recovery: None

Event Generation Threshold: 1 occurrence

Event Details:
Examples:
Event 323

Severity: MAJOR_WARNING

Event Summary: PDT is disabled

Event Class: System

Problem Description:
An event indicating that the user has the PDT disabled on this boot. The PDT will never be disabled in customer systems, so this event should never be seen in the field.

Cause / Action:
C: Informational event indicating that FW will not use the PDT this boot. A: None if user does not want to use the PDT, otherwise, clear NVM

Automated Recovery: None

Event Generation Threshold: 1 occurrence

Event Details:
Examples:
Event 324

Severity: MAJOR_WARNING

Event Summary: Error adding entry to PDT

Event Class: System

Problem Description:
Error writing entry into the PDT.

Cause / Action:
C: NVM write error. A: Contact HP support personnel to troubleshoot the problem.

Automated Recovery: None

Event Generation Threshold: 1 occurrence

Event Details:
Examples:
Event 325

Severity: SERIOUS

Event Summary: Cannot add PDT entry--PDT full

Event Class: System

Problem Description:
The memory page deallocation table (PDT) is full.

Cause / Action:
C: Excessive memory errors A: Contact HP Support personnel to troubleshoot the problem

Automated Recovery: None

Event Generation Threshold: 1 occurrence

Event Details:
Examples:
Event 326

Severity: MAJOR_WARNING

Event Summary: Memory platform data update failure

Event Class: System

Problem Description:
Memory FW was unable to save or restore the original error configuration (including CEC error log and signal enable and CPU ECC detection). This event should never be seen in the field unless there is a FW problem

Cause / Action:
C: Memory FW was unable to save or restore the original error configuration. A: If this is seen, update SFW.

Automated Recovery: None

Event Generation Threshold: 1 occurrence

Event Details:
Examples:
Event 327

Severity: MAJOR_WARNING

Event Summary: Can't find memory rank entry

Event Class: System

Problem Description:
The rank structure that corresponds to the rankID in the data field could not be found in the Rank table. The Data field is the rankID of the structure it is looking for. This error event should never be seen.

Cause / Action:
C: 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. A: Contact HP support to troubleshoot the problem.

Automated Recovery: None

Event Generation Threshold: 1 occurrence

Event Details:
Examples:
Event 329

Severity: MAJOR_WARNING

Event Summary: Memory error overflow:

Event Class: System

Problem Description:
More than one error type was detected when only one error type was expected.

Cause / Action:
C: An error other than a memory error occurred during the memory test A: Contact HP support to troubleshoot the problem

Automated Recovery: None

Event Generation Threshold: 1 occurrence

Event Details:
Examples:
Event 330

Severity: MAJOR_WARNING

Event Summary: Memory forward progress code invalid

Event Class: System

Problem Description:
The forward progress bits that memory FW uses to track state are invalid. The data field is the fwd progress field.

Cause / Action:
C: The forward progress bits are invalid. A: Upgrade to latest system firmware, or contact HP support to troubleshoot the problem.

Automated Recovery: None

Event Generation Threshold: 1 occurrence

Event Details:
Examples:
Event 331

Severity: MAJOR_WARNING

Event Summary: Memory error status invalid

Event Class: System

Problem Description:
The memory error status has bits set in it that indicate another non-memory error occurred. The data field contains the chipset's error status.

Cause / Action:
C: Non-memory errors were detected during the memory test that FW doesn't know how to handle. A: Update to the latest SFW A: Contact HP support to troubleshoot the problem.

Automated Recovery: None

Event Generation Threshold: 1 occurrence

Event Details:
Examples:
Event 332

Severity: MAJOR_WARNING

Event Summary: Memory error summary bits invalid

Event Class: System

Problem Description:
The memory test summary bits are invalid. The data field is the test summary bits.

Cause / Action:
C: The memory test summary word is invalid A: Update to the latest SFW. A: Contact HP support to troubleshoot the problem.

Automated Recovery: None

Event Generation Threshold: 1 occurrence

Event Details:
Examples:
Event 333

Severity: MAJOR_WARNING

Event Summary: The DIMM distribution check was bypassed

Event Class: System

Problem Description:
The control bit to skip the DIMM distribution check is set and the DIMM distribution check was skipped. This bit should only be done in the factory and not in the field.

Cause / Action:
C: Control bit to skip DIMM distribution check is set. A: Clear NVM A: Update PDC A: Contact HP support to troubleshoot the problem

Automated Recovery: None

Event Generation Threshold: 1 occurrence

Event Details:
Examples:
Event 334

Severity: MAJOR_WARNING

Event Summary: The DIMM Loading Order check was bypassed

Event Class: System

Problem Description:
The control bit to skip the DIMM loading order check is set and the DIMM loading order check was skipped. This bit should only be done in the factory and not in the field.

Cause / Action:
C: Control bit to skip DIMM loading order check is set. A: Clear NVM A: Update PDC A: Contact HP support to troubleshoot the problem

Automated Recovery: None

Event Generation Threshold: 1 occurrence

Event Details:
Examples:
Event 335

Severity: MAJOR_WARNING

Event Summary: Looping on destructive memory tests

Event Class: System

Problem Description:
The control bit to loop on destructive memory test is set and the destructive memory tests are run continuously. This bit should only be done in the factory and not in the field.

Cause / Action:
C: Control bit to loop on destructive memory test is set. A: Clear NVM A: Update PDC A: Contact HP support to troubleshoot the problem

Automated Recovery: None

Event Generation Threshold: 1 occurrence

Event Details:
Examples:
Event 336

Severity: MAJOR_WARNING

Event Summary: DIMM Set Check has been skipped

Event Class: System

Problem Description:
The control bit to skip the DIMM set check is set and the DIMM set check was skipped. This bit should only be done in the factory and not in the field.

Cause / Action:
C: Control bit to skip DIMM set check is set. A: Clear NVM A: Update PDC A: Contact HP support to troubleshoot the problem

Automated Recovery: None

Event Generation Threshold: 1 occurrence

Event Details:
Examples:
Event 337

Severity: MAJOR_WARNING

Event Summary: Serial Presence Detect (SPD) has been skipped

Event Class: System

Problem Description:
The control bit to skip the DIMM SPD check is set and the checking of the DIMM SPD was skipped. This bit should only be done in the factory and not in the field.

Cause / Action:
C: Control bit to skip DIMM SPD check is set. A: Clear NVM A: Update PDC A: Contact HP support to troubleshoot the problem

Automated Recovery: None

Event Generation Threshold: 1 occurrence

Event Details:
Examples:
Event 338

Severity: MAJOR_WARNING

Event Summary: An Alternate Memory Config has been loaded into the system

Event Class: System

Problem Description:
The control bit to load an alternate memory configuration is set and an alternate memory configuration has been loaded. This bit should only be set in the factory and not in the field.

Cause / Action:
C: Control bit to use an alternate memory config are set. A: Clear NVM A: Update PDC A: Contact HP support to troubleshoot the problem

Automated Recovery: None

Event Generation Threshold: 1 occurrence

Event Details:
Examples:
Event 340

Severity: MAJOR_WARNING

Event Summary: OS INIT address not registered

Event Class: System

Problem Description:
The OS_INIT vector has not been registered

Cause / Action:
Cause: The OS has not registered an OS_INIT vector. Action: None, the OS has failed to register the vector or has chosen not to.

Automated Recovery: None

Event Generation Threshold: 1 occurrence

Event Details:
Examples:
Event 341

Severity: MAJOR_WARNING

Event Summary: OS MCA address not registered

Event Class: System

Problem Description:
The OS_MCA vector has not been registered

Cause / Action:
Cause: The OS has not registered an OS_MCA vector. Action: None, the OS has failed to register the vector or has chosen not to.

Automated Recovery: None

Event Generation Threshold: 1 occurrence

Event Details:
Examples:
Event 342

Severity: MAJOR_WARNING

Event Summary: OS MCA did not correct the Machine Check

Event Class: System

Problem Description:
An Uncorrected Machine Check has occurred

Cause / Action:
Cause: Uncorrected Machine Check. Action: Analyze cause of Machine Check using diagnostic and EFI tools.

Automated Recovery: None

Event Generation Threshold: 1 occurrence

Event Details:
Examples:
Event 343

Severity: CRITICAL

Event Summary: Found bad miscellaneous register

Event Class: System

Problem Description:
A PDH register has failed.

Cause / Action:
Cause: A PDH register has failed. Action: Reboot if necessary, if problem persists contact your HP representative for support.

Automated Recovery: None

Event Generation Threshold: 1 occurrence

Event Details:
Examples:
Event 344

Severity: MAJOR_WARNING

Event Summary: SAL_CHECK failed for an unknown reason

Event Class: System

Problem Description:
The handler for SAL_CHECK has failed for an unknown reason.

Cause / Action:
Cause: The handler for SAL_CHECK has failed for an unknown reason. Action: Reboot if necessary, if problem persists contact your HP representative for support.

Automated Recovery: None

Event Generation Threshold: 1 occurrence

Event Details:
Examples:
Event 345

Severity: MAJOR_WARNING

Event Summary: SAL_INIT failed for an unknown reason

Event Class: System

Problem Description:
The handler for SAL_INIT has failed for an unknown reason.

Cause / Action:
Cause: The handler for SAL_INIT has failed for an unknown reason. Action: Reboot if necessary, if problem persists contact your HP representative for support.

Automated Recovery: None

Event Generation Threshold: 1 occurrence

Event Details:
Examples:
Event 346

Severity: MAJOR_WARNING

Event Summary: Unspecified memory interleave error

Event Class: System

Problem Description:
Indicates that FW encountered a Fatal interleaving error. The data field contains the return status from the interleaving procedure call.

Cause / Action:
C: FW encountered a fatal interleaving error. A: Update SFW A: Contact HP support to troubleshoot the problem

Automated Recovery: None

Event Generation Threshold: 1 occurrence

Event Details:
Examples:
Event 347

Severity: MAJOR_WARNING

Event Summary: Unexpected return to SAL_CHECK

Event Class: System

Problem Description:
SAL_CHECK has been unexpectedly returned to.

Cause / Action:
Cause: SAL_CHECK has been unexpectedly returned to. Action: Reboot if necessary, if problem persists contact your HP representative for support.

Automated Recovery: None

Event Generation Threshold: 1 occurrence

Event Details:
Examples:
Event 348

Severity: MAJOR_WARNING

Event Summary: Unexpected return to SAL_INIT

Event Class: System

Problem Description:
SAL_CHECK has been unexpectedly returned to.

Cause / Action:
Cause: SAL_CHECK has been unexpectedly returned to. Action: Reboot if necessary, if problem persists contact your HP representative for support.

Automated Recovery: None

Event Generation Threshold: 1 occurrence

Event Details:
Examples:

Event 350

Severity: SERIOUS

Event Summary: PD rendez will fail do to a Firmware Tree error

Event Class: System

Problem Description:
Firmware was unable to locate a required element in the device tree and cannot create a partition. The resource that cannot be located is listed as an ansii string in the data field.

Cause / Action:
Decode the ascii string in the data field to determine what resource is missing. Examine earlier chassis codes to determine why that resouse is unavailable.

Automated Recovery: None

Event Generation Threshold: 1 occurrence

Event Details:
Examples:
Event 351

Severity: SERIOUS

Event Summary: The current cell is not configured as part of the expected set

Event Class: System

Problem Description:
The currently executing cell is not configured to be part of the cell set it is attempting to rendezvous with.

Cause / Action:
A bad complex profile exists. Correct and redistribute.

Automated Recovery: None

Event Generation Threshold: 1 occurrence

Event Details:
Examples:
Event 352

Severity: SERIOUS

Event Summary: A remote CSR could not be read

Event Class: System

Problem Description:
The current cell could not read a remote cells CSR. The remote cell number is displayed in the data field. These cells will not be able to rendezvous.

Cause / Action:
Either a hardware connection problem exists, or fabric was unable to be routed. Verify hardware and reset.

Automated Recovery: None

Event Generation Threshold: 1 occurrence

Event Details:
Examples:
Event 353

Severity: SERIOUS

Event Summary: The current cell is too late to rendezvous with other cells

Event Class: System

Problem Description:
The currently executing cell arrived too late to rendezvous with the other cells described in the complex profile as cells it should rendezvous with.

Cause / Action:
This cell took to long completing previous steps to rendezvous. A bad complex profile could also cause this problem.

Automated Recovery: None

Event Generation Threshold: 1 occurrence

Event Details:
Examples:
Event 354

Severity: CRITICAL

Event Summary: The current cell detected incompatible CPUs on another cell

Event Class: System

Problem Description:
The currently executing cell detected CPUs that are incompatible with it to be installed on a cell that the current cell is trying to rendezvous with.

Cause / Action:
Mixed CPU types are installed in the same partition. Remove them.

Automated Recovery: None

Event Generation Threshold: 1 occurrence

Event Details:
Examples:
Event 355

Severity: SERIOUS

Event Summary: Current cell was too slow creating the local rendezvous set

Event Class: System

Problem Description:
The current cell was too slow creating the local rendezvous set and the other cells have left it behind. It will not be able to participate in the remainder of the rendezvous.

Cause / Action:
Cell too slow. Could be bad hardware. Check for other errors and reset

Automated Recovery: None

Event Generation Threshold: 1 occurrence

Event Details:
Examples:
Event 356

Severity: SERIOUS

Event Summary: Reporting cell was not included in the global cell set

Event Class: System

Problem Description:
The reporting cell was not included in the final global set that was agreed upon. This means that another cell either could not reach the reporting cell or the reporting cell was too late arriving to a required state.

Cause / Action:
Fabric problem, Connection problem or timing problem. Reset the PD.

Automated Recovery: None

Event Generation Threshold: 1 occurrence

Event Details:
Examples:
Event 357

Severity: CRITICAL

Event Summary: No Core Cell can be selected in the PD.

Event Class: System

Problem Description:
No cells in the PD can be a core cell. This is fatal.

Cause / Action:
No cells have a functioning core IO card. Add a core IO card to a cell in the PD and reset.

Automated Recovery: None

Event Generation Threshold: 1 occurrence

Event Details:
Examples:
Event 358

Severity: SERIOUS

Event Summary: Firmware was unable to notify utilities of the core cell number

Event Class: System

Problem Description:
System Firmware was unable to notify utilities of the selected core cell number.

Cause / Action:
Communication with utilities is broken. Check for earlier errors or NVRAM problems.

Automated Recovery: None

Event Generation Threshold: 1 occurrence

Event Details:
Examples:
Event 359

Severity: SERIOUS

Event Summary: Fabric code unable to find a needed service provider.

Event Class: System

Problem Description:
The fabric code is unable to find a service provider for a required banyan service.

Cause / Action:
The registry is corrupt or the ROM is incomplete.

Automated Recovery: None

Event Generation Threshold: 1 occurrence

Event Details:
Examples:
Event 360

Severity: SERIOUS

Event Summary: Error in a fabric Port

Event Class: System

Problem Description:
The fabric port specified in the data field had an error.

Cause / Action:
Reset.

Automated Recovery: None

Event Generation Threshold: 1 occurrence

Event Details:
Examples:
Event 361

Severity: SERIOUS

Event Summary: Parity error detected on read from fabric

Event Class: System

Problem Description:
An error occurred reading a CSR. The CSR address is displayed in the data field.

Cause / Action:
Hardware problem. Check connections and reset.

Automated Recovery: None

Event Generation Threshold: 1 occurrence

Event Details:
Examples:
Event 362

Severity: SERIOUS

Event Summary: Error writing to Fabric

Event Class: System

Problem Description:
Error writing to Fabric. CSR data in data field.

Cause / Action:
Bad hardware.

Automated Recovery: None

Event Generation Threshold: 1 occurrence

Event Details:
Examples:
Event 363

Severity: CRITICAL

Event Summary: Crossbar slices are out of rev with each other.

Event Class: System

Problem Description:
Incompatible crossbar slices are installed The data field is the two revisions reported by slice1 and slice0 of the CSR data.

Cause / Action:
Bad hardware configuration. Replace the crossbar.

Automated Recovery: None

Event Generation Threshold: 1 occurrence

Event Details:
Examples:
Event 364

Severity: CRITICAL

Event Summary: Crossbar slices are configured poorly

Event Class: System

Problem Description:
Crossbar slices are in different locations. The data field is the two locations reported by slice1 and slice0 of the CSR data.

Cause / Action:
Fatal configuration. Reconfigure the hardware.

Automated Recovery: None

Event Generation Threshold: 1 occurrence

Event Details:
Examples:
Event 365

Severity: SERIOUS

Event Summary: A CPU has taken over for the monarch CPU

Event Class: System

Problem Description:
A CPU has taken over as the monarch CPU.

Cause / Action:
The previous monarch may be suspect.

Automated Recovery: None

Event Generation Threshold: 1 occurrence

Event Details:
Examples:
Event 366

Severity: CRITICAL

Event Summary: Sram cannot be used on the cell

Event Class: System

Problem Description:
SRAM cannot be accessed on the cell board. Execution cannot continue.

Cause / Action:
SRAM cannot be located or used on the cell board. Replace the cell board.

Automated Recovery: None

Event Generation Threshold: 1 occurrence

Event Details:
Examples:
Event 367

Severity: CRITICAL

Event Summary: The dillon hardware cannot be located.

Event Class: System

Problem Description:
The dillon component/chip cannot be located or used.

Cause / Action:
ROM is corrupt. Replace the rom or reprogram flash.

Automated Recovery: None

Event Generation Threshold: 1 occurrence

Event Details:
Examples:
Event 368

Severity: SERIOUS

Event Summary: A required piece of PDH bus hardware cannot be contacted.

Event Class: System

Problem Description:
A required pice of PDH bus hardware cannot be contacted.

Cause / Action:
Verify all connections of PDH bus components or replace the cell board.

Automated Recovery: None

Event Generation Threshold: 1 occurrence

Event Details:
Examples:
Event 372

Severity: MAJOR_WARNING

Event Summary: IO Link software error was corrected.

Event Class: System

Problem Description:
IO Link Software error was corrected.

Cause / Action:
No action required.

Automated Recovery: None

Event Generation Threshold: 1 occurrence

Event Details:
Examples:
Event 373

Severity: SERIOUS

Event Summary: Bad parity data from RD Rtn FIFO on PIO Read (UNC)

Event Class: System

Problem Description:
Bad parity data from RD Rtn FIFO on PIO Read (UNC).

Cause / Action:
Replace bad hardware.

Automated Recovery: None

Event Generation Threshold: 1 occurrence

Event Details:
Examples:
Event 374

Severity: SERIOUS

Event Summary: Parity error in Reg FIFO Internal parity error.

Event Class: System

Problem Description:
Parity error in Reg FIFO Internal parity error.

Cause / Action:
Replace bad hardware.

Automated Recovery: None

Event Generation Threshold: 1 occurrence

Event Details:
Examples:
Event 375

Severity: SERIOUS

Event Summary: TLB Fetch timeout

Event Class: System

Problem Description:
TLB Fetch timeout.

Cause / Action:
Replace bad hardware.

Automated Recovery: None

Event Generation Threshold: 1 occurrence

Event Details:
Examples:
Event 376

Severity: CRITICAL

Event Summary: Link presence goes away, FE

Event Class: System

Problem Description:
Link presence goes away, FE.

Cause / Action:
Replace the link.

Automated Recovery: None

Event Generation Threshold: 1 occurrence

Event Details:
Examples:
Event 377

Severity: CRITICAL

Event Summary: LBA to SBA parity error on command, rope will go fatal

Event Class: System

Problem Description:
LBA to SBA parity error on command, rope will go fatal.

Cause / Action:
Bad hardware.
Replace I/O chassis.

Automated Recovery: None

Event Generation Threshold: 1 occurrence

Event Details:
Examples:
Event 378

Severity: CRITICAL

Event Summary: Access to invalid TLB entry Requesting rope fatal

Event Class: System

Problem Description:
Access to invalid TLB entry Requesting rope fatal.

Cause / Action:
Replace bad hardware.

Automated Recovery: None

Event Generation Threshold: 1 occurrence

Event Details:
Examples:
Event 379

Severity: CRITICAL

Event Summary: Memory fetch timeout

Event Class: System

Problem Description:
Memory Fetch Timeout.

Cause / Action:
Replace bad hardware.

Automated Recovery: None

Event Generation Threshold: 1 occurrence

Event Details:
Examples:
Event 380

Severity: SERIOUS

Event Summary: Error was encountered when Initializion the LBA.

Event Class: System

Problem Description:
An error was encountered when initing the rope number specified in the data field.

Cause / Action:
Replace the bad hardware.

Automated Recovery: None

Event Generation Threshold: 1 occurrence

Event Details:
Examples:
Event 381

Severity: MAJOR_WARNING

Event Summary: LBA correctable Timeout Error was encountered.

Event Class: System

Problem Description:
LBA correctable timeout error was encountered.

Cause / Action:
No action required.

Automated Recovery: None

Event Generation Threshold: 1 occurrence

Event Details:
Examples:
Event 382

Severity: SERIOUS

Event Summary: LBA uncorrectable Function Error was encountered.

Event Class: System

Problem Description:
LBA uncorrectable Function Error was encountered.

Cause / Action:
Replace the damaged hardware.

Automated Recovery: None

Event Generation Threshold: 1 occurrence

Event Details:
Examples:
Event 383

Severity: SERIOUS

Event Summary: LBA uncorrectable Timeout Error was encountered.

Event Class: System

Problem Description:
LBA uncorrectable Timeout Error was encountered.

Cause / Action:
Replace the damaged hardware.

Automated Recovery: None

Event Generation Threshold: 1 occurrence

Event Details:
Examples:
Event 384

Severity: SERIOUS

Event Summary: Misc. uncorrectable error discovered on LBA.

Event Class: System

Problem Description:
Misc uncorrectable error discovered on LBA.

Cause / Action:
Replace damaged hardware.

Automated Recovery: None

Event Generation Threshold: 1 occurrence

Event Details:
Examples:
Event 385

Severity: CRITICAL

Event Summary: LBA encountered an uncorrectable parity error.

Event Class: System

Problem Description:
LBA encountered an uncorrectable parity error.

Cause / Action:
Replace the damaged hardware.

Automated Recovery: None

Event Generation Threshold: 1 occurrence

Event Details:
Examples:
Event 386

Severity: CRITICAL

Event Summary: LBA Misc. Fatal Error encountered.

Event Class: System

Problem Description:
LBA misc. Fatal Error encountered.

Cause / Action:
Replace damaged hardware.

Automated Recovery: None

Event Generation Threshold: 1 occurrence

Event Details:
Examples:
Event 387

Severity: CRITICAL

Event Summary: LBA Fatal function error encountered.

Event Class: System

Problem Description:
LBA Fatal function error encountered.

Cause / Action:
Replace damaged hardware.

Automated Recovery: None

Event Generation Threshold: 1 occurrence

Event Details:
Examples:
Event 388

Severity: CRITICAL

Event Summary: LBA Fatal Parity error encountered.

Event Class: System

Problem Description:
LBA Fatal Parity error encountered.

Cause / Action:
Replace hardware, either PCI card or IO backplane.

Automated Recovery: None

Event Generation Threshold: 1 occurrence

Event Details:
Examples:
Event 389

Severity: CRITICAL

Event Summary: LBA Fatal Timeout Error Encountered.

Event Class: System

Problem Description:
LBA Fatal timeout error encountered.

Cause / Action:
Replace damaged hardware.

Automated Recovery: None

Event Generation Threshold: 1 occurrence

Event Details:
Examples:
Event 392

Severity: SERIOUS

Event Summary: DIMM SPD Extended Checksum Failure

Event Class: System

Problem Description:
The calculated and compared Checksums of the SPD EEPROM don't match.

Cause / Action:
Replace any bad dimms.

Automated Recovery: None

Event Generation Threshold: 1 occurrence

Event Details:
Examples:
Event 393

Severity: MAJOR_WARNING

Event Summary: Options header checksum error encountered.

Event Class: System

Problem Description:
The Options component encountered a header checksum error. The actual data is in the data field of the chassis code.

Cause / Action:
Reinitialize the options data.

Automated Recovery: None

Event Generation Threshold: 1 occurrence

Event Details:
Examples:
Event 394

Severity: MAJOR_WARNING

Event Summary: Options data checksum error was encountered.

Event Class: System

Problem Description:
The Options service data had a bad checksum. Actual data is in the data field.

Cause / Action:
Verify options data and reinitialize if necessary.

Automated Recovery: None

Event Generation Threshold: 1 occurrence

Event Details:
Examples:
Event 395

Severity: SERIOUS

Event Summary: Internal inconsistency in the interleave tables.

Event Class: System

Problem Description:
Internal inconsistency in the interleave tables.

Cause / Action:
Reconfigure and Reset.

Automated Recovery: None

Event Generation Threshold: 1 occurrence

Event Details:
Examples:
Event 396

Severity: MAJOR_WARNING

Event Summary: CellInfoList is not NULL.

Event Class: System

Problem Description:
The CellInfoList is not null and was expected to be. There has been an error in interleaving.

Cause / Action:
Reset.

Automated Recovery: None

Event Generation Threshold: 1 occurrence

Event Details:
Examples:
Event 397

Severity: SERIOUS

Event Summary: Error in constructing the Memory Descriptor.

Event Class: System

Problem Description:
Error in constructing the Memory Descriptor.

Cause / Action:
Reset.

Automated Recovery: None

Event Generation Threshold: 1 occurrence

Event Details:
Examples:
Event 398

Severity: SERIOUS

Event Summary: Unable to update the local memory layout

Event Class: System

Problem Description:
Unable to update the local memory layout.

Cause / Action:
Reset

Automated Recovery: None

Event Generation Threshold: 1 occurrence

Event Details:
Examples:
Event 399

Severity: SERIOUS

Event Summary: A required address was not found within a mapped address.

Event Class: System

Problem Description:
A required address was not found within a mapped address in the PDT.

Cause / Action:
Reset

Automated Recovery: None

Event Generation Threshold: 1 occurrence

Event Details:
Examples:
Event 400

Severity: SERIOUS

Event Summary: Failure to install a Partition level PDT.

Event Class: System

Problem Description:
Failure to install a partition level PDT. Errors prevented it.

Cause / Action:
Reset

Automated Recovery: None

Event Generation Threshold: 1 occurrence

Event Details:
Examples:
Event 401

Severity: SERIOUS

Event Summary: A critical resourse could not be found or is unusable

Event Class: System

Problem Description:
A critical resouse that is required early in the initialization process either could not be found, or was unusable. The specific resouse is specified in the data field as follows: Platform Parameters Component not found in FIT: 0xdead0001; SRAM_BASE not found in platform parms: 0xdead0002; SRAM_SIZE not found in Platform Parms: 0xdead0003; firmware framework not found in the fit: 0xdead0004; Framework Segmant not usable: 0xdead0005; bad NVRAM: 0xdead0006; Dillon unusable: 0xdead0007; SRAM unusable: 0xdead0008; CPU unusable: 0xdead0009; Options Component Unusable: 0xdead000a; Real Time Clock unusable: DEAD_RTC; Unknown: 0xdead0086

Cause / Action:
Determine the failing component or hardware from the data field as described and replace.

Automated Recovery: None

Event Generation Threshold: 1 occurrence

Event Details:
Examples:
Event 402

Severity: CRITICAL

Event Summary: Internal firmware programming error.

Event Class: System

Problem Description:
An internal firmware error was encountered. This is usually caused by a bad parameter passed to a function, corrupt memory, corrupt malloc tables or something similar. The data field contains the IP address of the function that encountered the error.

Cause / Action:
Report the IP to the firmware team. Reset the system. This cannot be worked around in the field.

Automated Recovery: None

Event Generation Threshold: 1 occurrence

Event Details:
Examples:
Event 405

Severity: SERIOUS

Event Summary: A semaphore could not be obtained

Event Class: System

Problem Description:
The required semaphore could not be obtained due to errors. The data field contains the IP of the routine trying to obtain the semaphore. A request was placed for more NVRAM to be allocated but NVRAM was full.

Cause / Action:
Cause: Action: Reset system to clear the semaphore Try reinitializing NVRAM. If problem persists, contact engineering.

Automated Recovery: None

Event Generation Threshold: 1 occurrence

Event Details:
Examples:
Event 407

Severity: MAJOR_WARNING

Event Summary: The requested NVRAM block was not found.

Event Class: System

Problem Description:
The requested NVRAM block was not found. The ID that was not found is displayed in the data field.

Cause / Action:
No Action Required. Firmware can allocated space for the block.

Automated Recovery: None

Event Generation Threshold: 1 occurrence

Event Details:
Examples:
Event 408

Severity: MAJOR_WARNING

Event Summary: The requested NVRAM block is locked.

Event Class: System

Problem Description:
The block id specified in the data field is locked.

Cause / Action:
Retry the operation.

Automated Recovery: None

Event Generation Threshold: 1 occurrence

Event Details:
Examples:
Event 409

Severity: MAJOR_WARNING

Event Summary: Firmware tried to unlock a NVRAM block that was already unlocked.

Event Class: System

Problem Description:
Firmware tried to unlock a NVRAM block that was already unlocked. Data field contains the block ID.v

Cause / Action:
No action required.

Automated Recovery: None

Event Generation Threshold: 1 occurrence

Event Details:
Examples:
Event 410

Severity: SERIOUS

Event Summary: The Header in NVRAM was not found

Event Class: System

Problem Description:
The header in the NVRAM space was not found.

Cause / Action:
NVRAM cannot be used. It must be initialized first. Firmware will attempt the initialization.

Automated Recovery: None

Event Generation Threshold: 1 occurrence

Event Details:
Examples:
Event 411

Severity: SERIOUS

Event Summary: The Freelist used for NVM block allocation is corrupt.

Event Class: System

Problem Description:
The Freelist used vor Non-Volatile Memory allocation is corrupt.

Cause / Action:
Band NVRAM/ reinitialize.

Automated Recovery: None

Event Generation Threshold: 1 occurrence

Event Details:
Examples:
Event 412

Severity: SERIOUS

Event Summary: Firmware is preparing to reset for reconfiguration.

Event Class: System

Problem Description:
System firmware has detected a condition that requires the cell to be reset for reconfiguration. The function has been called and is now executing. Data field contains the cell number being reset.

Cause / Action:
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.

Automated Recovery: None

Event Generation Threshold: 1 occurrence

Event Details:
Examples:
Event 413

Severity: SERIOUS

Event Summary: An error was encountered communicating with utilities during PD rendez.

Event Class: System

Problem Description:
During PD rendezvous, system firmware encountered a problem sending commands to the utilities system. This will prevent a fully functional PD from being created.

Cause / Action:
Verify communications with the utilities system.

Automated Recovery: None

Event Generation Threshold: 1 occurrence

Event Details:
Examples:
Event 414

Severity: CRITICAL

Event Summary: Forward Progress is stopping. The Cell or System will not boot further.

Event Class: System

Problem Description:
System Firmware has determined that cell or system progress must be halted. The data field contains the Instruction Pointer of the function that called for the halt. The second instance of this code being emitted indicates the major state in system change. This code must be emitted in pairs.

Cause / Action:
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 Error Response Mode is likely to have directed firmware to HALT.

Automated Recovery: None

Event Generation Threshold: 1 occurrence

Event Details:
Examples:
Event 415

Severity: MAJOR_WARNING

Event Summary: No console is available for the DUI to use.

Event Class: System

Problem Description:
The DUI (Developers User Interface) was entered, but there is no console available for the interface.

Cause / Action:
DUI was entered before the console is available. DUI will exit and processing will continue.

Automated Recovery: None

Event Generation Threshold: 1 occurrence

Event Details:
Examples:
Event 416

Severity: SERIOUS

Event Summary: Error Processing encountered an unrecoverable error

Event Class: System

Problem Description:
During Error processing and reporting, an error was detected that prevented further processing of errors. The data field contains an ASCII message indicating the problem.

Cause / Action:
Decode the ascii message and correct the problem.

Automated Recovery: None

Event Generation Threshold: 1 occurrence

Event Details:
Examples:
Event 417

Severity: SERIOUS

Event Summary: System is unable to complete the Reset For Reconfiguration request.

Event Class: System

Problem Description:
System firmware is unable to complete the request to reset the cell for reconfiguration. Typically, are required step has not been performed yet or a needed resource is unavailable.

Cause / Action:
Delay the request for reconfiguration until after the PD has been released from Sinc BIB.

Automated Recovery: None

Event Generation Threshold: 1 occurrence

Event Details:
Examples:
Event 418

Severity: SERIOUS

Event Summary: The cell is not able to reach all requested cells through the fabric.

Event Class: System

Problem Description:
The cell was not able to reach all the other cells in its configured set through the fabric. The data field contains the bitmask of actual cells that were reached.

Cause / Action:
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.

Automated Recovery: None

Event Generation Threshold: 1 occurrence

Event Details:
Examples:
Event 419

Severity: MAJOR_WARNING

Event Summary: LBA has unexpected number of I/O Slots.

Event Class: System

Problem Description:
Firmware detected a PCI-to-PCI bridge that exceeds the maximum supported bridge depth. Firmware will not configure I/O devices below the maximum bridge depth. Such I/O devices will not be usable as console nor boot devices but might be usable by the O/S. Data Field: PCI function address of the bridge that exceeded the maximum depth limit. Bits 24..31: segment number Bits 16..23: bus number Bits 11..15: device number Bits 8..10: function number Bits 0..7: reserved (0)

Cause / Action:
Cause: Unsupported I/O configuration. Action: Remove the I/O cards below the specified PCI-to-PCI bridge.

Automated Recovery: None

Event Generation Threshold: 1 occurrence

Event Details:
Examples:
Event 420

Severity: SERIOUS

Event Summary: Console device failed to connect.

Event Class: System

Problem Description:
Debugging event, not for release. This event is no longer used on Everest/xPeak systems but its event ID is still contained in the code base.

Cause / Action:
Debugging event, not for release.

Automated Recovery: None

Event Generation Threshold: 1 occurrence

Event Details:
Examples:
Event 421

Severity: MAJOR_WARNING

Event Summary: Copying memory test code failed.

Event Class: System

Problem Description:
This event is unused

Cause / Action:
C: Memory test code located in main memory has been corrupted A: Contact HP support personnel to troubleshoot the problem

Automated Recovery: None

Event Generation Threshold: 1 occurrence

Event Details:
Examples:
Event 423

Severity: SERIOUS

Event Summary: Multiple Core Cells have been discovered in the same PD

Event Class: System

Problem Description:
The reporting Cell thinks that it should be the core cell but has discovered another cell in the same PD that thinks it should be the core cell. This is a serious problem.

Cause / Action:
Verify that the complex profile is correct and reset the partition.

Automated Recovery: None

Event Generation Threshold: 1 occurrence

Event Details:
Examples:
Event 424

Severity: SERIOUS

Event Summary: The utilities component encountered an error when sending a command to the MP

Event Class: System

Problem Description:
The utilities system firmware component received an error response from the SINC in response to a command being sent. The exact error is displayed in the data field. Typically, this can occur when the SINC cannot talk to the MP.

Cause / Action:
Verify the utilities system is connected correctly and reset.

Automated Recovery: None

Event Generation Threshold: 1 occurrence

Event Details:
Examples:
Event 425

Severity: MAJOR_WARNING

Event Summary: Error received after issuing the Retrieve Cell Slot State command

Event Class: System

Problem Description:
System Firmware issued the Retrieve Cell Slot State command to the Sync and got an error back. See related chassis code or the specifics of the error.

Cause / Action:
Make sure the MP is connected and reset.

Automated Recovery: None

Event Generation Threshold: 1 occurrence

Event Details:
Examples:
Event 426

Severity: SERIOUS

Event Summary: This indicates that all the cpus in the cell did not rendezvous during the MCA.

Event Class: System

Problem Description:
This denotes the fact that all the cpus in the cell did not rendezvous.

Cause / Action:
When this happens the cell will step through some of the error logging code on its own and then reset itself.

Automated Recovery: None

Event Generation Threshold: 1 occurrence

Event Details:
Examples:
Event 427

Severity: SERIOUS

Event Summary: This indicates that it does not have any access to the PD.

Event Class: System

Problem Description:
This chassis code indicates that the cell does not have any access to a PD.

Cause / Action:
Forward Progress indicator; the cell will independently step through the error logging steps before it resets itself.

Automated Recovery: None

Event Generation Threshold: 1 occurrence

Event Details:
Examples:
Event 428

Severity: SERIOUS

Event Summary: This indicates the loss of lockstep during the MCA path.

Event Class: System

Problem Description:
This indicates the cell would not be able to join the other cells in the PD level rendezvous. The data portion represents the cell id of the cell that incurred the loss of lockstep.

Cause / Action:
The cell will take up a few more error logging steps independently before resetting itself.

Automated Recovery: None

Event Generation Threshold: 1 occurrence

Event Details:
Examples:
Event 429

Severity: SERIOUS

Event Summary: The PD level cell rendezvous failed.

Event Class: System

Problem Description:
This indicates that some of the cells did not show up during the PD level rendezvous.

Cause / Action:
This means that the cells will independently step through some of the error logging code and then reset themselves.

Automated Recovery: None

Event Generation Threshold: 1 occurrence

Event Details:
Examples:
Event 430

Severity: MAJOR_WARNING

Event Summary: PCI parity error detected.

Event Class: System

Problem Description:
An I/O device (or host bridge) detected a bus parity error. An I/O device (or host bridge) mastered a bus transaction and received a parity error response from the target. Data Field: Physical location of the I/O device (or host bridge).

Cause / Action:
Cause: I/O bus parity error. Action: Consult the error logs for additional information. Determine and replace the failed I/O device. Cause: I/O host bridge failure. Action: Contact your HP representative to check the I/O host bridge.

Automated Recovery: None

Event Generation Threshold: 1 occurrence

Event Details:
Examples:
Event 431

Severity: MAJOR_WARNING

Event Summary: PCI system error detected

Event Class: System

Problem Description:
An I/O device (or host bridge) detected an internal error. An I/O device (or host bridge) detected a bus error. Data Field: Physical location of the I/O device (or host bridge).

Cause / Action:
Cause: I/O device failure. Action: Consult the error logs for additional information. Determine and replace the failed I/O device. Cause: I/O host bridge failure. Action: Contact your HP representative to check the I/O host bridge.

Automated Recovery: None

Event Generation Threshold: 1 occurrence

Event Details:
Examples:
Event 432

Severity: MAJOR_WARNING

Event Summary: I/O host bridge is deconfigured

Event Class: System

Problem Description:
Firmware has deconfigured an I/O host bridge due to an error (see earlier error event). Firmware will display the following EFI warning message, "Failed I/O slot(s) deconfigured." Data Field: Physical location of the deconfigured I/O host bridge.

Cause / Action:
Cause: See earlier error event. Action: See earlier error event.

Automated Recovery: None

Event Generation Threshold: 1 occurrence

Event Details:
Examples:
Event 433

Severity: SERIOUS

Event Summary: Firmware was unable to publish the Partition Profile

Event Class: System

Problem Description:
Firmware tried to default the Partition (Group C) complex profile and encountered an error.

Cause / Action:
Manageability may be unavailable to update the profiles. Check the connections are reset.

Automated Recovery: None

Event Generation Threshold: 1 occurrence

Event Details:
Examples:
Event 434

Severity: SERIOUS

Event Summary: The reporting cell is not configured to be in a PD.

Event Class: System

Problem Description:
The Reporting Cell is not configured to be in a PD, according to Complex Profile Group A.

Cause / Action:
Run parmgr to configure the cell into a PD and reset the PD or add the cell.

Automated Recovery: None

Event Generation Threshold: 1 occurrence

Event Details:
Examples:
Event 435

Severity: MAJOR_WARNING

Event Summary: DIMM thermal loading order warning

Event Class: System

Problem Description:
DIMMs are not loaded on the extender in a thermally optimal way. Boot is still possible, but the DIMM arrangement should be changed to the loading order recommended in the users manual. The data field indicates the number of the extender with incorrectly loaded DIMMs.

Cause / Action:
C: The current DIMM loading order does not follow the guidelines in the user manual A: Rearrange the DIMMs to follow the loading order specified in the Maintenance and Operational Manual

Automated Recovery: None

Event Generation Threshold: 1 occurrence

Event Details:
Examples:
Event 437

Severity: CRITICAL

Event Summary: The PD cannot boot, a majority of cells did not arrive at Rendezvous

Event Class: System

Problem Description:
Not enough cells made the Rendezvous for boot to continue. The rules are listed in the cause action section.

Cause / Action:
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.

Automated Recovery: None

Event Generation Threshold: 1 occurrence

Event Details:
Examples:
Event 439

Severity: MAJOR_WARNING

Event Summary: INIT: Monarch failed in slave rendezvous

Event Class: System

Problem Description:
SFW's INIT handler has failed to rendezvoused the processors.

Cause / Action:
Cause: A processor has failed rendezvous. Action: Reboot if necessary, if problem persists contact your HP representative for support.

Automated Recovery: None

Event Generation Threshold: 1 occurrence

Event Details:
Examples:
Event 440

Severity: MAJOR_WARNING

Event Summary: MC: I/O error log/clear error

Event Class: System

Problem Description:
SFW's Machine Check Handler was unable to log or clear I/O error records.

Cause / Action:
Cause: SFW's Machine Check Handler was unable to log or clear I/O error records. Action: Reboot if necessary, if problem persists contact your HP representative for support.

Automated Recovery: None

Event Generation Threshold: 1 occurrence

Event Details:
Examples:
Event 441

Severity: MAJOR_WARNING

Event Summary: MC: MCA to BERR escalation not supported by PAL

Event Class: System

Problem Description:
Cannot escalate an MCA to BERR

Cause / Action:
Cause: Cannot escalate an MCA to BERR. Action: Analyze Machine Check Logs using diagnostic tools and EFI tools.

Automated Recovery: None

Event Generation Threshold: 1 occurrence

Event Details:
Examples:
Event 442

Severity: MAJOR_WARNING

Event Summary: MC: MCA to BINIT escalation not supported by PAL

Event Class: System

Problem Description:
Cannot escalate an MCA to BINIT.

Cause / Action:
Cause: Cannot escalate an MCA to BINIT. Action: Analyze Machine Check Logs using diagnostic tools and EFI tools.

Automated Recovery: None

Event Generation Threshold: 1 occurrence

Event Details:
Examples:
Event 443

Severity: MAJOR_WARNING

Event Summary: MC: Get PAL features failed

Event Class: System

Problem Description:
SFW failed to get the feature set from PAL.

Cause / Action:
Cause: SFW failed to get the feature set from PAL. Action: None

Automated Recovery: None

Event Generation Threshold: 1 occurrence

Event Details:
Examples:
Event 444

Severity: MAJOR_WARNING

Event Summary: MC: Previous PAL rendezvous failed; rebooting

Event Class: System

Problem Description:
PAL Failed to rendezvous the processors during a MCA.

Cause / Action:
Cause: PAL Failed to rendezvous the processors during a MCA.

Automated Recovery: None

Event Generation Threshold: 1 occurrence

Event Details:
Examples:
Event 445

Severity: MAJOR_WARNING

Event Summary: MC: Set PAL features failed

Event Class: System

Problem Description:
SFW failed to get the feature set from PAL.

Cause / Action:
Cause: SFW failed to get the feature set from PAL. Action: None

Automated Recovery: None

Event Generation Threshold: 1 occurrence

Event Details:
Examples:
Event 446

Severity: MAJOR_WARNING

Event Summary: MC: Monarch failed in slave rendezvous

Event Class: System

Problem Description:
SFW's MCA Handler has failed to rendezvous all the slaves Data: Return from the rendezvous call.

Cause / Action:
Cause: A slave failed to rendezvous. Action: Reboot if necessary, if problem persists contact your HP representative for support.

Automated Recovery: None

Event Generation Threshold: 1 occurrence

Event Details:
Examples:
Event 447

Severity: MAJOR_WARNING

Event Summary: MC_RENDEZVOUS: Rendezvous vector out of range

Event Class: System

Problem Description:
A bad rendezvous vector has been registered.

Cause / Action:
Cause: A bad rendezvous vector has been registered. Action: Reboot if necessary to re-register vector, if problem persists contact your HP representative for support.

Automated Recovery: None

Event Generation Threshold: 1 occurrence

Event Details:
Examples:
Event 448

Severity: MAJOR_WARNING

Event Summary: MC_RENDEZVOUS: No MC monarch

Event Class: System

Problem Description:
No Machine Check Monarch exists, exiting MC Rendezvous.

Cause / Action:
Forward progress, no action required

Automated Recovery: None

Event Generation Threshold: 1 occurrence

Event Details:
Examples:
Event 449

Severity: MAJOR_WARNING

Event Summary: MC_RENDEZVOUS: No wakeup registered

Event Class: System

Problem Description:
The OS has not registered a wake-up mechanism for rendezvous.

Cause / Action:
Forward progress, no action required

Automated Recovery: None

Event Generation Threshold: 1 occurrence

Event Details:
Examples:
Event 450

Severity: MAJOR_WARNING

Event Summary: MC_RENDEZVOUS: MCA escalation not supported by PAL

Event Class: System

Problem Description:
PAL call failed to set the BINIT escalation bit

Cause / Action:
No action required.

Automated Recovery: None

Event Generation Threshold: 1 occurrence

Event Details:
Examples:
Event 451

Severity: MAJOR_WARNING

Event Summary: MC_RENDEZVOUS: Get PAL features failed

Event Class: System

Problem Description:
The PAL call PAL_GET_FEATURES has failed.

Cause / Action:
No action required.

Automated Recovery: None

Event Generation Threshold: 1 occurrence

Event Details:
Examples:
Event 452

Severity: MAJOR_WARNING

Event Summary: MC_RENDEZVOUS: Set PAL features failed

Event Class: System

Problem Description:
The PAL call PAL_SET_FEATURES has failed.

Cause / Action:
No action required.

Automated Recovery: None

Event Generation Threshold: 1 occurrence

Event Details:
Examples:
Event 453

Severity: CRITICAL

Event Summary: Internal Firmware Programming Error from the EFI portion of the firmware

Event Class: System

Problem Description:
An internal SAL_ABI firmware error was encountered. This is usually caused by a bad parameter passed to a function, corrupt memory, corrupt malloc, corrupt firmware tree or something similar. The data field contains the IP address of the function that encountered the error.

Cause / Action:
Report the IP to the firmware team. Reset the system. This cannot be worked around in the field.

Automated Recovery: None

Event Generation Threshold: 1 occurrence

Event Details:
Examples:
Event 454

Severity: CRITICAL

Event Summary: memory extender loading order error

Event Class: System

Problem Description:
The Memory extenders have not been loaded in the correct order.

Cause / Action:
C: The memory extenders have not been loaded in the correct order. A: Load the Memory extenders according to the users manual.

Automated Recovery: None

Event Generation Threshold: 1 occurrence

Event Details:
Examples:
Event 455

Severity: CRITICAL

Event Summary: Inconsistency in the length of the ESI table

Event Class: System

Problem Description:
The length field within the ESI (Extensible SAL Interface) table does not agree with the product of the entry_count field and the size of each entry. Data Field: computed value of the length based on entry_count and size of the entries.

Cause / Action:
Cause: Table entries corrupted. Action: Reboot system. Cause: New table entry types added by SAL not understood by EFI. Action: Upgrade system firmware.

Automated Recovery: None

Event Generation Threshold: 1 occurrence

Event Details:
Examples:
Event 456

Severity: CRITICAL

Event Summary: The computed checksum for ESI Table incorrect.

Event Class: System

Problem Description:
The computed checksum for the ESI (Extensible SAL Interface) table is not zero as expected. EFI is halting. Data Field: the computed checksum.

Cause / Action:
Cause: Table corrupted. Action: Reboot the system. Cause: Table's checksum miscomputed. Action: Upgrade system firmware.

Automated Recovery: None

Event Generation Threshold: 1 occurrence

Event Details:
Examples:
Event 457

Severity: MAJOR_WARNING

Event Summary: ESI Table contains an unsupported entry type.

Event Class: System

Problem Description:
EFI found an unsupported entry type within the ESI (Extensible SAL Interface) Table. Data Field: unknown type.

Cause / Action:
Cause: Corrupted table. Action: Reboot system. Cause: Mismatch between SAL and EFI. Action: Upgrade system firmware.

Automated Recovery: None

Event Generation Threshold: 1 occurrence

Event Details:
Examples:
Event 458

Severity: MAJOR_WARNING

Event Summary: A GUID was larger than the expected 128 bits.

Event Class: System

Problem Description:
EFI was attempting to output a GUID in the EFI_GUID_HALF1 and EFI_GUID_HALF2 events which was larger than 128 bits. The data field contains the actual length of the GUID in bytes.

Cause / Action:
Cause: Inconsistency in EFI firmware. Action: Upgrade system firmware.

Automated Recovery: None

Event Generation Threshold: 1 occurrence

Event Details:
Examples:
Event 459

Severity: CRITICAL

Event Summary: EFI is halting

Event Class: System

Problem Description:
EFI is halting. Look for the cause of the halt in preceding events. Data Field: the "halt" (0x0F) major change in system state code.

Cause / Action:
Cause: Unknown. Action: examine preceding events for problem.

Automated Recovery: None

Event Generation Threshold: 1 occurrence

Event Details:
Examples:
Event 460

Severity: MAJOR_WARNING

Event Summary: chipspare not supported on quad

Event Class: System

Problem Description:
This code will be sent when FW detects a rank installed in the system that doesn't support chipspare. The data field is used to indicate the rank that the x8 DIMMs are installed. It is in the format 0x00000000XDXCXBXA or 0x00000000YBYAXBXA where X and Y are the number of the rank.

Cause / Action:
C: User installed a x8 DIMM in a system configured for chipspare. A: If user requires Chipspare, replace the DIMM with a x4 DIMM. If Chipspare is not required, then no action is required.

Automated Recovery: None

Event Generation Threshold: 1 occurrence

Event Details:
Examples:
Event 461

Severity: MAJOR_WARNING

Event Summary: EFI internal error detected resulting in execution of ASSERT macro

Event Class: System

Problem Description:
EFI has detected an internal error. The actual error is unspecified by this event. Examine previous events and console output for possible explanations.

Cause / Action:
The cause is unknown. See previous events and console output for causes.

Automated Recovery: None

Event Generation Threshold: 1 occurrence

Event Details:
Examples:
Event 462

Severity: CRITICAL

Event Summary: EFI has executed the "break" shell command.

Event Class: System

Problem Description:

Cause / Action:
Cause: Executing the "break command. Action: Check for user entering "break" command. Check for shell scripts using the "break" command.

Automated Recovery: None

Event Generation Threshold: 1 occurrence

Event Details:
Examples:
Event 463

Severity: CRITICAL

Event Summary: EFI USB HCD interrupt service has detected the host controller is hung

Event Class: System

Problem Description:
The EFI USB HCD interrupt service has detected the host controller is hung. EFI is halting.

Cause / Action:
Cause: Problem with USB controller. Action: Reset the card containing the USB interface to restart the controller. Contact your HP representative to check the USB interface.

Automated Recovery: None

Event Generation Threshold: 1 occurrence

Event Details:
Examples:
Event 464

Severity: CRITICAL

Event Summary: The EFI/SAL handoff structure's version does not match EFI expectations

Event Class: System

Problem Description:
The EFI/SAL handoff structure's version does not match EFI expectations. EFI is halting. Look for EFI_SAL_HANDOFF_VER_EXPECTED to provide EFI's expected value. Data Field: Actual value of the version in the structure.

Cause / Action:
Cause: EFI/SAL firmware mismatch. Action: Upgrade System Firmware.

Automated Recovery: None

Event Generation Threshold: 1 occurrence

Event Details:
Examples:
Event 465

Severity: CRITICAL

Event Summary: Unable to obtain access to all RTC SAL services

Event Class: System

Problem Description:
EFI is unable to obtain access to all the RTC (Real Time Clock) SAL services. This means that EFI is unable to fully interact with the RTC. EFI is halting. Data Field: Return status from internal EFI function.

Cause / Action:
Cause: Not all expected services are available. Mismatch between EFI and SAL versions. Internal EFI error.
Action: Upgrade system firmware. Cause: EFI unable to create internal event. EFI out of resources. Action: Reset system.

Automated Recovery: None

Event Generation Threshold: 1 occurrence

Event Details:
Examples:
Event 466

Severity: CRITICAL

Event Summary: Unable to obtain access to all SAL timer services

Event Class: System

Problem Description:
EFI is unable to obtain access to all the SAL timer services. This means that EFI is unable to fully interact with the timer. EFI is halting. Data Field: Return status from internal EFI function.

Cause / Action:
Cause: Not all expected services are available. Mismatch between EFI and SAL versions. Internal EFI error. Action: Upgrade system firmware.

Automated Recovery: None

Event Generation Threshold: 1 occurrence

Event Details:
Examples:
Event 467

Severity: CRITICAL

Event Summary: EFI unable to start the periodic timer

Event Class: System

Problem Description:
EFI is unable to start the periodic timer. This timer interrupts EFI periodically to process time sensitive events. EFI is halting. Data Field: Return status for internal EFI function.

Cause / Action:
Cause: Internal system firmware error. Action: Reset the system. Cause: Mismatch between EFI and SAL versions Action: Upgrade system firmware.

Automated Recovery: None

Event Generation Threshold: 1 occurrence

Event Details:
Examples:
Event 468

Severity: CRITICAL

Event Summary: No I/O port space region found in the MDT

Event Class: System

Problem Description:
EFI did not find an I/O port space region in the MDT. EFI is halting.

Cause / Action:
Cause: EFI/SAL handoff structure corrupted. Action: Determine source of corruption and reboot. Cause: EFI/SAL mismatch. Action: Check system firmware versions and upgrade if necessary.

Automated Recovery: None

Event Generation Threshold: 1 occurrence

Event Details:
Examples:
Event 469

Severity: CRITICAL

Event Summary: EFI reached an unimplemented section of code

Event Class: System

Problem Description:
EFI reached an unimplemented section of code. EFI is halting. Data Field: Unique identifier indicating the location reached within the code.

Cause / Action:
Cause: Reached unimplemented firmware. Action: Upgrade system firmware.

Automated Recovery: None

Event Generation Threshold: 1 occurrence

Event Details:
Examples:
Event 470

Severity: MAJOR_WARNING

Event Summary: EFI unable to read current speedy boot settings

Event Class: System

Problem Description:
EFI was unable to read the current speedy boot settings. The speedy boot settings are stored within the BMC. EFI will use a default value of 0 and continue booting. The speedy boot functionality is also accessed via the boottest EFI shell command and via the OS. These other accesses will likely fail. Data Field: Return status from internal EFI function.

Cause / Action:
Cause: BMC not functioning. Action: Reset the BMC. Contact your HP representative to check the BMC. Cause: BMC/SAL firmware mismatch. Action: Upgrade system firmware and/or BMC firmware. Cause: EFI/SAL version mismatch. Action: Upgrade system firmware.

Automated Recovery: None

Event Generation Threshold: 1 occurrence

Event Details:
Examples:
Event 471

Severity: CRITICAL

Event Summary: Unpermitted SAL callback attempted

Event Class: System

Problem Description:
A SAL Callback was attempted. This is not permitted. EFI is halting. Data Field: index of the function that was being called.

Cause / Action:
Cause: Internal EFI error. Action: Upgrade system firmware.

Automated Recovery: None

Event Generation Threshold: 1 occurrence

Event Details:
Examples:
Event 472

Severity: MAJOR_WARNING

Event Summary: EFI unable to determine frequency base of the CPU interval timer

Event Class: System

Problem Description:
EFI is unable to determine the frequency base for the Interval Timer within the CPU. The SAL procedure EFI uses to get this information returned an error. EFI uses this information to create delays within EFI based on the interval timer. EFI will assume 800 MIPS. Data Field: return status from the SAL procedure.

Cause / Action:
Cause: Invalid timer ratio. Action: Reset system. Cause: Internal system firmware error. Action: Upgrade system firmware.

Automated Recovery: None

Event Generation Threshold: 1 occurrence

Event Details:
Examples:
Event 473

Severity: MAJOR_WARNING

Event Summary: EFI system events already initialized

Event Class: System

Problem Description:
The EFI system events have already been initialized. This is unexpected. EFI is continuing. Data Field: the current value of the system event entry point.

Cause / Action:
Cause: Multiple attempts to initialize system events, EFI internal error. Action: Upgrade system firmware.

Automated Recovery: None

Event Generation Threshold: 1 occurrence

Event Details:
Examples:
Event 474

Severity: MAJOR_WARNING

Event Summary: Unable to create internal virtualization event while initializing IPMI events

Event Class: System

Problem Description:
EFI was unable to create an internal virtualization event while initializing EFI's System Events (IPMI events). This internal event is not an IPMI event; rather it serves as a trigger for EFI to virtualize the System Event facility when going virtual. EFI will likely halt. Data Field: return status from internal EFI function.

Cause / Action:
Cause: Out of resources. Internal EFI error. Action: Reboot system. Upgrade system firmware.

Automated Recovery: None

Event Generation Threshold: 1 occurrence

Event Details:
Examples:
Event 476

Severity: SERIOUS

Event Summary: There was an error creating or initializing the FPGA node in firmware

Event Class: System

Problem Description:
An error was detected while initializing the FPGA node and services associated with the PDH.

Cause / Action:
Cause: Unable to properly initialize a system firmware node Action: Check for other errors in the system first. Invalidate NVM and retry to boot. Get the latest firmware release.

Automated Recovery: None

Event Generation Threshold: 1 occurrence

Event Details:
Examples:
Event 477

Severity: SERIOUS

Event Summary: Error encountered setting up the dillon_pdh node or service.

Event Class: System

Problem Description:
System firmware was unable to correctly set up the dill_pdh node as a child of the pdh node, or was unable to locate and attach the dillon_pdh service to the node. The status is returned in the data field.

Cause / Action:
This is usually a symptom of an earlier problem. Check to be sure the pdh node was initialized into the tree correctly.

Automated Recovery: None

Event Generation Threshold: 1 occurrence

Event Details:
Examples:
Event 478

Severity: SERIOUS

Event Summary: The PDH component encountered an error dealing with a property on a node.

Event Class: System

Problem Description:
The PDH service was unable to either get or set the property specified in the data field as an ascii message.

Cause / Action:
This is usually due to a memory allocation problem. Verify that sram is usable and there is memory available.

Automated Recovery: None

Event Generation Threshold: 1 occurrence

Event Details:
Examples:
Event 479

Severity: SERIOUS

Event Summary: Error creating the acpi_hw node.

Event Class: System

Problem Description:
PDH encountered an error creating the ACPI Hardware Node in the device tree or installing its properties.

Cause / Action:
May be out of malloc space or a previous tree error prevented this from being successful. Check for earlier errors.

Automated Recovery: None

Event Generation Threshold: 1 occurrence

Event Details:
Examples:
Event 480

Severity: SERIOUS

Event Summary: Error encountered creating or initializing the ipmi node

Event Class: System

Problem Description:
The PDH service encountered an error while creating the ipmi node or adding properties to it. The status is in the data field.

Cause / Action:
Possibly out of memory or an earlier error left the tree in an unusable state.

Automated Recovery: None

Event Generation Threshold: 1 occurrence

Event Details:
Examples:
Event 481

Severity: CRITICAL

Event Summary: some processors not compatible

Event Class: System

Problem Description:
Installed processors are not of compatible models or families

Cause / Action:
Replace processors with compatible ones if all processors are to be used.

Automated Recovery: None

Event Generation Threshold: 1 occurrence

Event Details:
Examples:
Event 482

Severity: CRITICAL

Event Summary: caches sizes are inconsistent

Event Class: System

Problem Description:
Processors with different cache sizes are installed

Cause / Action:
Replace processors with compatible ones if all processors are to be used.

Automated Recovery: None

Event Generation Threshold: 1 occurrence

Event Details:
Examples:
Event 483

Severity: MAJOR_WARNING

Event Summary: processor steppings are not equal

Event Class: System

Problem Description:
Processors with different steppingss are installed

Cause / Action:
If desired, replace processors with equal stepping ones, this is a warning only.

Automated Recovery: None

Event Generation Threshold: 1 occurrence

Event Details:
Examples:
Event 484

Severity: MAJOR_WARNING

Event Summary: selecting new monarch

Event Class: System

Problem Description:
SFW is selecting a new processor due to compatibility problems.

Cause / Action:
Replace incompatible processor if desired.

Automated Recovery: None

Event Generation Threshold: 1 occurrence

Event Details:
Examples:
Event 485

Severity: CRITICAL

Event Summary: monarch not lowest stepping

Event Class: System

Problem Description:
The monarch stepping is not equal to the lowest installed CPU stepping.

Cause / Action:
Replace the processor with one that has an equal stepping to the others.

Automated Recovery: None

Event Generation Threshold: 1 occurrence

Event Details:
Examples:
Event 487

Severity: MAJOR_WARNING

Event Summary: processors are over clocked

Event Class: System

Problem Description:
A CPU's FSB frequency is overclocked. Data: Local CPU Number.

Cause / Action:
Change FSB frequency.

Automated Recovery: None

Event Generation Threshold: 1 occurrence

Event Details:
Examples:
Event 488

Severity: MAJOR_WARNING

Event Summary: cpu access error on processor info area

Event Class: System

Problem Description:
There was an error reading the info ROM area of the CPU. Data: Local CPU Number

Cause / Action:
Cause: An early version of CPU or a bad info ROM. Action: Replace CPU.

Automated Recovery: None

Event Generation Threshold: 1 occurrence

Event Details:
Examples:
Event 489

Severity: MAJOR_WARNING

Event Summary: PAL A was not executed - HALT

Event Class: System

Problem Description:
PAL_A has not been executed and control is being transferred back to SAL_B.

Cause / Action:
No Action.

Automated Recovery: None

Event Generation Threshold: 1 occurrence

Event Details:
Examples:
Event 490

Severity: CRITICAL

Event Summary: PAL B was not executed - HALT

Event Class: System

Problem Description:
PAL_B has not been executed and control is being transferred back to SAL_B.

Cause / Action:
No Action.

Automated Recovery: None

Event Generation Threshold: 1 occurrence

Event Details:
Examples:
Event 491

Severity: MAJOR_WARNING

Event Summary: Prototype CPU installed

Event Class: System

Problem Description:
Data: Lower 32 bits have Local CPU Number

Cause / Action:
Cause: A Prototype CPU is installed. Action: Replace CPU with a production CPU.

Automated Recovery: None

Event Generation Threshold: 1 occurrence

Event Details:
Examples:
Event 492

Severity: MAJOR_WARNING

Event Summary: final boot rendezvous monarch watchdog timeout

Event Class: System

Problem Description:
Data: Monarch's Local CPU Number

Cause / Action:
Cause: A watchdog timer has expired and determined that a monarch is dead. Action: Reboot, if problem persists, replace CPU.

Automated Recovery: None

Event Generation Threshold: 1 occurrence

Event Details:
Examples:
Event 493

Severity: MAJOR_WARNING

Event Summary: A multi-bit error was found while reading a XBC CSR

Event Class: System

Problem Description:
While reading a XBC CSR, a multi-bit error was found.

Cause / Action:
None.

Automated Recovery: None

Event Generation Threshold: 1 occurrence

Event Details:
Examples:
Event 494

Severity: MAJOR_WARNING

Event Summary: The return value from a function was an unknown value.

Event Class: System

Problem Description:
The return value from a function was an unknown value. Data field is the unknown status that was returned.

Cause / Action:
None.

Automated Recovery: None

Event Generation Threshold: 1 occurrence

Event Details:
Examples:
Event 495

Severity: MAJOR_WARNING

Event Summary: Cannot get system ID status from BMC

Event Class: System

Problem Description:
EFI queries the BMC on the system board for the status of a system ID. The BMC could not complete the request successfully or on time. Data Field: Internal EFI function status.

Cause / Action:
Cause: The communication with the system ID is lost Action: Unplug power from the system for 10 seconds and try rebooting the system. Cause: Inaccessible FRU EPROM on system board and/or I/O backplane. Failure in IPMI messaging path on system board and/or I/O backplane Action: Check FRU EPROM content and accessibility on system and I/O backplane using ifru. If BMC communication is not working (no answer from BMC), flash BMC firmware. If it cannot be done or doesn't solve the problem, replace system board. If system board FRU EPROM cannot be accessed, replace system board If I/O backplane FRU EPROM cannot be accessed, replace I/O backplane

Automated Recovery: None

Event Generation Threshold: 1 occurrence

Event Details:
Examples:
Event 496

Severity: MAJOR_WARNING

Event Summary: Cannot read a system ID

Event Class: System

Problem Description:
BMC reported a system ID status as inaccessible, reported invalid status or cannot return the current value of a system ID. Data Field: uuid status or internal EFI function status. System ID status: a 1 byte value 0 extended to 64bits: 0x00 -> primary and secondary values are valid 0x01 -> primary and secondary values are magic 0x02 -> primary and secondary values are inaccessible 0x04 -> primary and secondary values are invalid 0x08 -> primary and secondary values are null (UUID only) 0x10 -> primary and secondary values are different, value (primary or secondary) is valid 0x11 -> primary and secondary values are different, value (primary or secondary) is magic 0x12 -> primary and secondary values are different, value (primary or secondary) is inaccessible 0x14 -> primary and secondary values are different, value (primary or secondary) is invalid 0x18 -> primary and secondary values are different, value (primary or secondary) is null (UUID only)

Cause / Action:
Cause: BMC failure Action: Unplug power from the system for 10 seconds and try rebooting the system. Cause: Inaccessible/corrupted FRU EPROM on system board and/or I/O backplane. Action: Check content of FRU EPROM of the system board and I/O backplane using ifru. If FRU EPROM content can be accessed on both board flash BMC firmware. If content cannot be accessed on system board replace system board. If content cannot be accessed on I/O backplane, replace I/O backplane If this cannot be done or doesn't solve the issue replace system board.

Automated Recovery: None

Event Generation Threshold: 1 occurrence

Event Details:
Examples:
Event 497

Severity: MAJOR_WARNING

Event Summary: Failed to write new system ID. BMC reported an error

Event Class: System

Problem Description:
Firmware tried to write a primary or secondary system ID as requested by the user during the boot sequence. The write failed. Data Field: Internal EFI function status.

Cause / Action:
Cause: Communication failure with the BMC. Action: Unplug power from the system for 10 seconds and try rebooting the system. Cause: Inaccessible/corrupted FRU EPROM on system board and/or I/O backplane. Inaccessible/corrupted FRU EPROM on system board and/or I/O backplane. Action: Check content of FRU EPROM of the system board and I/O backplane using ifru. If FRU EPROM content can be accessed on both board flash BMC firmware. If content cannot be accessed on system board replace system board. If content cannot be accessed on I/O backplane, replace I/O backplane If it cannot be done or doesn't solve the issue replace system board.

Automated Recovery: None

Event Generation Threshold: 1 occurrence

Event Details:
Examples:
Event 498

Severity: MAJOR_WARNING

Event Summary: The system ID(s) currently in the system is invalid

Event Class: System

Problem Description:
The system ID(s) currently in the system is either invalid or, if the EFI_SYSID_BMC_WARNING, EFI_SYSID_BMC_READ_ERROR or EFI_SYSID_BMC_WRITE_ERROR events are also present, inaccessible to the system firmware. A stop boot condition will be generated and software license will probably be invalid. Data Field: uuid: 2 byte value. If preceded by 0xbad00000000000 the following valid values are possible: 0000 -> valid (should never see his one) 0001 -> magic 0002 -> inaccessible If zero extended: 1st byte refers to primary UUID, 2nd byte to secondary 00 -> valid 10 / 01 -> magic 11 / 02 -> inaccessible 12 /

Cause / Action:
Cause: The system ID(s) is invalid and the user did not elect to fix the problem. Action: Reboot the system and follow the prompts to fix the issue. Cause: The system ID(s) cannot be accessed or the BMC is not providing the requested information. One of the following events will also be present: EFI_SYSID_BMC_WARNING, EFI_SYSID_BMC_READ_ERROR or EFI_SYSID_BMC_WRITE_ERROR Action: Fix the error indicated by the other system ID event.

Automated Recovery: None

Event Generation Threshold: 1 occurrence

Event Details:
Examples:
Event 499

Severity: CRITICAL

Event Summary: EFI unable to find the SAL services for installing interrupt handlers

Event Class: System

Problem Description:
EFI is unable to find the SAL services for installing interrupt handlers. EFI was trying to install the run-time handlers that are required for normal EFI booting. EFI will be halting. Data Field: internal EFI function status.

Cause / Action:
Cause: Mismatch between EFI and SAL. Action: Upgrade system firmware. Cause: Corrupted ESI table. Action: Reboot system.

Automated Recovery: None

Event Generation Threshold: 1 occurrence

Event Details:
Examples:
Event 500

Severity: CRITICAL

Event Summary: EFI unable to find the SAL service to install run-time interrupt handlers

Event Class: System

Problem Description:
EFI is unable to find the SAL service to install run-time interrupt handlers. These handlers are required for normal EFI booting. EFI will be halting. Data Field: internal EFI function status.

Cause / Action:
Cause: Mismatch between EFI and SAL. Action: Upgrade system firmware.

Automated Recovery: None

Event Generation Threshold: 1 occurrence

Event Details:
Examples:
Event 501

Severity: CRITICAL

Event Summary: EFI unable to find the SAL services for installing interrupt handlers

Event Class: System

Problem Description:
EFI is unable to find the SAL services for installing interrupt handlers. EFI was trying to install the boot-time handlers that are required for normal EFI booting. EFI will be halting. Data Field: internal EFI function status.

Cause / Action:
Cause: Mismatch between EFI and SAL. Action: Upgrade system firmware. Cause: Corrupted firmware table. Action: Find source of corruption and reboot.

Automated Recovery: None

Event Generation Threshold: 1 occurrence

Event Details:
Examples:
Event 502

Severity: CRITICAL

Event Summary: EFI unable to find the SAL service to install boot-time interrupt handlers

Event Class: System

Problem Description:
EFI is unable to find the SAL service to install boot-time interrupt handlers. These handlers are required for normal EFI booting. EFI will be halting. Data Field: internal EFI function status.

Cause / Action:
Cause: Mismatch between EFI and SAL. Action: Upgrade system firmware.

Automated Recovery: None

Event Generation Threshold: 1 occurrence

Event Details:
Examples:
Event 503

Severity: MAJOR_WARNING

Event Summary: Too many parameters were passed to the utilities system

Event Class: System

Problem Description:
Too many parameters were passed in a request for the utilities system to perform an operation. No more data is provided.

Cause / Action:
This is a firmware error. Contact FW engineering.

Automated Recovery: None

Event Generation Threshold: 1 occurrence

Event Details:
Examples:
Event 504

Severity: SERIOUS

Event Summary: A crossbar port is unexpectedly not present.

Event Class: System

Problem Description:
A crossbar port is expected to be present, but its presence detect bit is not set. Data field bits 32:43 contain the crossbar ID, bits 44:55 contain the port number for which the error occurred, and bits 0:31 contain the port status information.

Cause / Action:
Cause: An XBC is indicating a port failure Action: Validate all of the cells connectivity to the PD Check the TOGO chips seating reset the system replace either cells/system backplane

Automated Recovery: None

Event Generation Threshold: 1 occurrence

Event Details:
Examples:
Event 505

Severity: SERIOUS

Event Summary: A crossbar port unexpectedly has its HW_LINK_OK bit not set.

Event Class: System

Problem Description:
A crossbar port is expected to have its HW_LINK_OK bit set, but it is not. Data field bits 32:43 contain the crossbar ID, bits 44:55 contain the port number for which the error occurred, and bits 0:31 contain the port status information.

Cause / Action:
Cause: An XBC is indicating a port failure Action: Validate all of the cells connectivity to the PD Check the TOGO chips seating reset the system replace either cells/system backplane

Automated Recovery: None

Event Generation Threshold: 1 occurrence

Event Details:
Examples:
Event 506

Severity: SERIOUS

Event Summary: A connected port was found to be in FE

Event Class: System

Problem Description:
A connected crossbar port was found to have its FE bit set. Data field bits 32:43 contain the crossbar ID, bits 44:55 contain the port number for which the error occurred, and bits 0:31 contain the port status information.

Cause / Action:
Cause: An XBC is indicating a port failure Action: Validate all of the cells connectivity to the PD Check the TOGO chips seating reset the system replace either cells/system backplane

Automated Recovery: None

Event Generation Threshold: 1 occurrence

Event Details:
Examples:
Event 507

Severity: SERIOUS

Event Summary: There was an error while initializing the Concorde-Xbc interface.

Event Class: System

Problem Description:
There was an error while initializing the Concorde-Xbc interface. The data field contains the address of the Concorde CSR for which the error occurred.

Cause / Action:
Cause: An XBC is indicating a port failure Action: Validate all of the cells connectivity to the PD Check the TOGO chips seating reset the system replace either cells/system backplane

Automated Recovery: None

Event Generation Threshold: 1 occurrence

Event Details:
Examples:
Event 508

Severity: CRITICAL

Event Summary: The CC - XBC link failed to initialize.

Event Class: System

Problem Description:
The CC - XBC link failed to initialize.

Cause / Action:
Cause: An XBC is indicating a port failure Action: Validate all of the cells connectivity to the PD Check the TOGO chips seating reset the system replace either cells/system backplane

Automated Recovery: None

Event Generation Threshold: 1 occurrence

Event Details:
Examples:
Event 509

Severity: MAJOR_WARNING

Event Summary: Unable to determine system mode because EFI/SAL interface not initialized

Event Class: System

Problem Description:
EFI is unable to determine current system mode. The EFI/SAL interface is not initialized. This interface should have been initialized before now. This event indicates an internal EFI error. EFI will continue executing.

Cause / Action:
Cause: Internal EFI error. Action: Upgrade system firmware.

Automated Recovery: None

Event Generation Threshold: 1 occurrence

Event Details:
Examples:
Event 510

Severity: MAJOR_WARNING

Event Summary: BMC returned an invalid system mode

Event Class: System

Problem Description:
The BMC has returned an invalid system mode. Data Field: the invalid mode. Expected values are 0 or 1.

Cause / Action:
Cause: Mismatch between BMC and EFI firmware. Action: Upgrade system firmware or BMC firmware as necessary.

Automated Recovery: None

Event Generation Threshold: 1 occurrence

Event Details:
Examples:
Event 511

Severity: MAJOR_WARNING

Event Summary: EFI unable to specify system mode because EFI/SAL interface not initialized

Event Class: System

Problem Description:
EFI is unable to specify a new system mode. The EFI/SAL interface point is not initialized. This interface should have been initialized before now. This event indicates an internal EFI error. EFI will continue executing in the current mode.

Cause / Action:
Cause: Internal EFI error. Action: Upgrade system firmware.

Automated Recovery: None

Event Generation Threshold: 1 occurrence

Event Details:
Examples:
Event 512

Severity: MAJOR_WARNING

Event Summary: Unable to enter normal system mode because EFI/SAL interface not initialized

Event Class: System

Problem Description:
EFI is unable to enter normal system mode. The EFI/SAL interface is not initialized. This interface should have been initialized before now. This event indicates an internal EFI error. EFI will continue executing in the current mode.

Cause / Action:
Cause: Internal EFI error. Action: Upgrade system firmware.

Automated Recovery: None

Event Generation Threshold: 1 occurrence

Event Details:
Examples:
Event 513

Severity: CRITICAL

Event Summary: Unable to initialize part of the SAL/EFI interface

Event Class: System

Problem Description:
EFI is unable to initialize part of the SAL/EFI interface. This crucial service provides access to certain BMC functionality such as the security system. EFI will halt. Data Field: Return status from internal EFI function.

Cause / Action:
Cause: Incompatible versions of EFI and SAL Internal EFI error. Action: Upgrade system firmware.

Automated Recovery: None

Event Generation Threshold: 1 occurrence

Event Details:
Examples:
Event 515

Severity: SERIOUS

Event Summary: An expected tree node was not found

Event Class: System

Problem Description:
A needed tree node was not found. The data field contains the ascii name of the tree node that was not found.

Cause / Action:
This is a bug. Contact engineering.

Automated Recovery: None

Event Generation Threshold: 1 occurrence

Event Details:
Examples:
Event 516

Severity: MAJOR_WARNING

Event Summary: EFI unable to modify system state to "running"

Event Class: System

Problem Description:

Cause / Action:
Cause: BMC malfunctioning. Action: Reset BMC. Cause: BMC non functional. Action: Contact your HP representative to check the BMC.

Automated Recovery: None

Event Generation Threshold: 1 occurrence

Event Details:
Examples:
Event 518

Severity: MAJOR_WARNING

Event Summary: The Get Processor Bus Dependent Configuration Features PAL call failed.

Event Class: System

Problem Description:
Firmware was unable to correctly issue the Get Processor Bus Dependent Configuration Features command.

Cause / Action:
Contact engineering. There is a PAL compatibility problem.

Automated Recovery: None

Event Generation Threshold: 1 occurrence

Event Details:
Examples:
Event 519

Severity: MAJOR_WARNING

Event Summary: memory DIMM pair mismatch

Event Class: System

Problem Description:
A pair of DIMMs installed in the system are mismatched, and that pair of DIMMs will not be used. The data field indicates which pair of DIMMs are mismatched in the format 0x000000000000XBXA where X is the number of the rank that is mismatched.

Cause / Action:
C: The user installed a mismatched pair of DIMMs in the same rank (i.e. the DIMMs are different size or width). A: Install memory ranks in pairs of DIMMs that are the same size and width.

Automated Recovery: None

Event Generation Threshold: 1 occurrence

Event Details:
Examples:
Event 520

Severity: CRITICAL

Event Summary: EFI unable to initialize internal library

Event Class: System

Problem Description:
EFI is unable to initialize internal library. This collection of internal services is required for much of EFI's functionality. EFI is halting.

Cause / Action:
Cause: Internal EFI error. Action: Upgrade system firmware.

Automated Recovery: None

Event Generation Threshold: 1 occurrence

Event Details:
Examples:
Event 521

Severity: SERIOUS

Event Summary: EFI unable to initialize security system

Event Class: System

Problem Description:
EFI is unable to initialize the security system. The privilege level of the system may or may not be Admin. It is likely certain EFI facilities will be unavailable. EFI will continue booting but security may be compromised. Data Field: Return status from internal EFI function.

Cause / Action:
Cause: EFI out of resources. Action: Reboot system. Cause: SAL or EFI mismatch/failure. Action: Upgrade system firmware. Cause: BMC not responding properly. Action: Reset BMC. Contact your HP representative to check the BMC.

Automated Recovery: None

Event Generation Threshold: 1 occurrence

Event Details:
Examples:
Event 522

Severity: MAJOR_WARNING

Event Summary: EFI detected invalid internal privilege level

Event Class: System

Problem Description:
EFI detected an invalid value for its internal privilege level. This value is stored within SAL. EFI will continue but system security may be compromised. Data Field: The invalid privilege level.

Cause / Action:
Cause: SAL storage corrupted. Action: Reboot system. Cause: Invalid argument with EFI. Action: Upgrade system firmware.

Automated Recovery: None

Event Generation Threshold: 1 occurrence

Event Details:
Examples:
Event 523

Severity: MAJOR_WARNING

Event Summary: EFI detected invalid privilege level when setting password

Event Class: System

Problem Description:
EFI detected an invalid privilege level when setting a BMC password. Only the levels of Admin (0x30) and User (0x20) are permitted. Data Field: the invalid privilege level.

Cause / Action:
Cause: Internal EFI error. Action: Upgrade system firmware.

Automated Recovery: None

Event Generation Threshold: 1 occurrence

Event Details:
Examples:
Event 524

Severity: CRITICAL

Event Summary: EFI MDT table is bad

Event Class: System

Problem Description:
SFW has determined that the MDT table is invalid.

Cause / Action:
Cause: SFW has determined that the MDT table is invalid. Action: Reboot if necessary, if problem persists contact your HP representative for support.

Automated Recovery: None

Event Generation Threshold: 1 occurrence

Event Details:
Examples:
Event 525

Severity: MAJOR_WARNING

Event Summary: Processor has incompatible fixed core ratio

Event Class: System

Problem Description:
Data: Local CPU Number.

Cause / Action:
Cause: A CPU has a different fixed ration than the FSB frequency set in the chipset. Action: Replace CPU

Automated Recovery: None

Event Generation Threshold: 1 occurrence

Event Details:
Examples:
Event 526

Severity: CRITICAL

Event Summary: All processors slated for compatibility deconfiguration

Event Class: System

Problem Description:
Data: A bitmask for which CPUs are slated to be deconfigured

Cause / Action:
Cause: The user or SFW has set all CPUs to be deconfigured. Action: Replace bad processors, if problem persists contact your HP representative for support.

Automated Recovery: None

Event Generation Threshold: 1 occurrence

Event Details:
Examples:
Event 527

Severity: SERIOUS

Event Summary: An unexpected or invalid value was read from a crossbar remote route table.

Event Class: System

Problem Description:
An error occurred while reading a crossbar remote route table, or an unexpected/invalid value was read from the table. The data field consists of the crossbar ID (32:43), the port number of which the table was read (44:55), and the return status of the read call (0:32).

Cause / Action:
Cause: An XBC is indicating a port failure Action: Validate all of the cells connectivity to the PD Check the TOGO chips seating reset the system replace either cells/system backplane

Automated Recovery: None

Event Generation Threshold: 1 occurrence

Event Details:
Examples:
Event 528

Severity: SERIOUS

Event Summary: Error reading the PORT[n]_NEIGHBOR_INFO XBC CSR.

Event Class: System

Problem Description:
An error occurred while trying to read the PORT[n]_NEIGHBOR_INFO crossbar CSR. The data field consists of the crossbar ID (32:43) and port number (44:55) for which the CSR was read.

Cause / Action:
No action required.

Automated Recovery: None

Event Generation Threshold: 1 occurrence

Event Details:
Examples:
Event 529

Severity: MAJOR_WARNING

Event Summary: memory DIMM quad miss-match

Event Class: System

Problem Description:
A quad of DIMMs installed in the system are mismatched, and that quad of DIMMs will not be used. The data field indicates which quad of DIMMs are mismatched in the format 0x00000000XDXCXBXA where X is the number of the rank that is mismatched.

Cause / Action:
C: The user installed a mismatched quad of DIMMs in the same rank (i.e. the DIMMs are different size or width). A: Install memory ranks in quads of DIMMs that are the same size and width.

Automated Recovery: None

Event Generation Threshold: 1 occurrence

Event Details:
Examples:
Event 530

Severity: MAJOR_WARNING

Event Summary: Firmware detected excessive errors on the DIMM.

Event Class: System

Problem Description:
The DIMM at the physical location given by the data field had excessive errors and has been marked as "FAILED" by firmware.

Cause / Action:
Firmware detected excessive errors on the DIMM / Replace the specified DIMM

Automated Recovery: None

Event Generation Threshold: 1 occurrence

Event Details:
Examples:
Event 531

Severity: SERIOUS

Event Summary: The OE (output enable) bit was not set for a XBC port.

Event Class: System

Problem Description:
A XBC port was expected to be functional, but its OE bit was not set. The data field consists of the contents of the port_status CSR (0:31), the XBC number (32:43), and the port number (44:55).

Cause / Action:
No action required.

Automated Recovery: None

Event Generation Threshold: 1 occurrence

Event Details:
Examples:
Event 532

Severity: SERIOUS

Event Summary: An error occurred while trying to read the PORT_STATUS CSR for a XBC port.

Event Class: System

Problem Description:
Unable to read the PORT_STATUS CSR for a XBC port. The data field consists of the contents of the PORT_STATUS CSR (0:31), the XBC number (32:43), and the port number (44:55).

Cause / Action:
No action required.

Automated Recovery: None

Event Generation Threshold: 1 occurrence

Event Details:
Examples:
Event 533

Severity: SERIOUS

Event Summary: A XBC port was unexpectedly found to be landmined.

Event Class: System

Problem Description:
A XBC port was unexpectedly found to be landmined. The data field consists of the XBC number (32:43) and the port number (44:55).

Cause / Action:
No action required.

Automated Recovery: None

Event Generation Threshold: 1 occurrence

Event Details:
Examples:
Event 534

Severity: SERIOUS

Event Summary: CPUs running at different speeds were detected during rendezvous

Event Class: System

Problem Description:
Reporting cell tried to rendezvous with a cell with processors that are running at a different speed. The data field lists the offending cell

Cause / Action:
Reconfigure the PD so that all cells have processors running at the same speed.

Automated Recovery: None

Event Generation Threshold: 1 occurrence

Event Details:
Examples:
Event 535

Severity: SERIOUS

Event Summary: The link between the local CC and the local XBC is unexpectedly not initialized.

Event Class: System

Problem Description:
The link between the local CC and the local XBC is unexpectedly not initialized. The data field is the XIN_LINK_STATE CC CSR value.

Cause / Action:
Cause: An error initializing fabric Action: A previously reported event may provide exact details Reboot, if failure persists, then either replace the CC chip or the system backplane.

Automated Recovery: None

Event Generation Threshold: 1 occurrence

Event Details:
Examples:
Event 536

Severity: SERIOUS

Event Summary: An invalid XBC number was given.

Event Class: System

Problem Description:
A value that was expected to be a XBC number was found to be an invalid XBC number. The data field is the invalid XBC number.

Cause / Action:
A bad value was passed in as a parameter to fabric traversability functions. No action required.

Automated Recovery: None

Event Generation Threshold: 1 occurrence

Event Details:
Examples:
Event 537

Severity: SERIOUS

Event Summary: An invalid XBC port number was given.

Event Class: System

Problem Description:
A value that was expected to be a valid XBC port number was found to be invalid. The data field is the XBC number (33:44) and the invalid XBC port number (44:55).

Cause / Action:
A bad value was passed in as a parameter to fabric traversability functions. No action required.

Automated Recovery: None

Event Generation Threshold: 1 occurrence

Event Details:
Examples:
Event 538

Severity: MAJOR_WARNING

Event Summary: A bad parameter was passed to the LED function in the utilities component

Event Class: System

Problem Description:
A bad parameter was passed to the utilities function that manipulates the LED on replaceable parts. The offending parameter is displayed in the data field.

Cause / Action:
Contact FW engineering. This is a bug.

Automated Recovery: None

Event Generation Threshold: 1 occurrence

Event Details:
Examples:
Event 539

Severity: SERIOUS

Event Summary: An unexpected neighbor type was read from a XBC PORT_NEIGHBOR_INFO CSR.

Event Class: System

Problem Description:
A neighbor type read from a XBC PORT_NEIGHBOR_INFO CSR was different than the expected neighbor type. The data field contains the expected type (32:63) and the actual neighbor type (0:31).

Cause / Action:
No action required.

Automated Recovery: None

Event Generation Threshold: 1 occurrence

Event Details:
Examples:
Event 540

Severity: SERIOUS

Event Summary: A given XBC port is not a valid XBC-CC port.

Event Class: System

Problem Description:
A XBC port number was unexpectedly found to not be a valid XBC-CC port. The data field consists of the XBC number (32:43) and the port number (44:55).

Cause / Action:
No action required.

Automated Recovery: None

Event Generation Threshold: 1 occurrence

Event Details:
Examples:
Event 541

Severity: SERIOUS

Event Summary: A XBC port was unexpectedly found to be an invalid XBC-XBC port.

Event Class: System

Problem Description:
A XBC port was unexpectedly found to be an invalid XBC-XBC port. The data field consists of the XBC number (32:43) and the port number (44:55).

Cause / Action:
No action required.

Automated Recovery: None

Event Generation Threshold: 1 occurrence

Event Details:
Examples:
Event 542

Severity: SERIOUS

Event Summary: The XBC neighbor chip number does not match the expected value for this topology

Event Class: System

Problem Description:
The XBC neighbor chip number does not match the expected value for this topology. The data field contains the expected neighbor chip number (32:63) and the actual neighbor chip number (0:31).

Cause / Action:
No action required.

Automated Recovery: None

Event Generation Threshold: 1 occurrence

Event Details:
Examples:
Event 543

Severity: SERIOUS

Event Summary: The XBC neighbor port number does not match the expected value for this topology

Event Class: System

Problem Description:
The XBC neighbor port number does not match the expected value for this topology. The data field contains the expected neighbor port number (32:63) and the actual neighbor port number (0:31).

Cause / Action:
No action required.

Automated Recovery: None

Event Generation Threshold: 1 occurrence

Event Details:
Examples:
Event 544

Severity: CRITICAL

Event Summary: Write through to BMC token failed

Event Class: System

Problem Description:
Data: Upper 32 bits, BMC failure return value. This is a stop boot condition. Lower 32 bits, BMC token number that failed.

Cause / Action:
Cause: Problem accessing the BMC. Action: Reset BMC or reboot, if problem persists contact your HP representative for support.

Automated Recovery: None

Event Generation Threshold: 1 occurrence

Event Details:
Examples:
Event 545

Severity: MAJOR_WARNING

Event Summary: Utilities reported an error while trying to manipulate the LED

Event Class: System

Problem Description:
The utilities system reported an error while trying to carry out the command to turn on, flash or turn off the LED. The status returned by the command is displayed in the data field.

Cause / Action:
It is likely the MP is not present or the device specified is not present. Solve these problems and try again.

Automated Recovery: None

Event Generation Threshold: 1 occurrence

Event Details:
Examples:
Event 546

Severity: SERIOUS

Event Summary: Duplicate Cpu Ids were detected within a cell.

Event Class: System

Problem Description:
2 cpus think that they have the same ID within the cell. Typically this would mean that PAL reported the same cpu id for more than 1 cpu on a bus. The cpuid is in the data field.

Cause / Action:
Most likely cause is a bad cpu module connection on the cell board. Replace the cell board.

Automated Recovery: None

Event Generation Threshold: 1 occurrence

Event Details:
Examples:
Event 547

Severity: MAJOR_WARNING

Event Summary: OS crashdump started (D700)

Event Class: System

Problem Description:
OS crashdump started (D700)

Cause / Action:
panic occurred

Automated Recovery: None

Event Generation Threshold: 1 occurrence

Event Details:
Examples:
Event 548

Severity: SERIOUS

Event Summary: OS legacy PA hex fault code (Bxxx)

Event Class: System

Problem Description:
OS legacy PA hex fault code (Bxxx). Possible I/O error or system panic

Cause / Action:
fault/panic

Automated Recovery: None

Event Generation Threshold: 1 occurrence

Event Details:
Examples:
Event 549

Severity: MAJOR_WARNING

Event Summary: OS dump status (EFxx)

Event Class: System

Problem Description:
OS dump status (EFxx). Report on the success/failure of the writing of the dump. EF00 = success (followed by either EF0A = successful dump with sync, or EF09 = successful dump without sync), EFFF = a general error, EFFE = dump path assertion failure, EFFD = no dump was taken by default, choice or failure, EFFC = dump was aborted by user.

Cause / Action:
panic path: attempt to write out the dump is complete

Automated Recovery: None

Event Generation Threshold: 1 occurrence

Event Details:
Examples:
Event 550

Severity: MAJOR_WARNING

Event Summary: Setting processor response timeout failed

Event Class: System

Problem Description:
SFW has failed to set the processor timeout value via a PAL call. Data: PAL call return value.

Cause / Action:
Cause: A PAL call made by SFW has failed. Action: Reboot if necessary, if problem persists contact your HP representative for support.

Automated Recovery: None

Event Generation Threshold: 1 occurrence

Event Details:
Examples:
Event 551

Severity: MAJOR_WARNING

Event Summary: Unable to validate blank password during EFI security initialization

Event Class: System

Problem Description:
During EFI security initialization, the attempt to determine what privilege level a blank password provides, failed. Most likely this indicates the BMC has failed. EFI assumes that the BMC has failed and will attempt to continue booting. Some EFI functionality may be unavailable. Data Field: Return status from internal EFI function.

Cause / Action:
Cause: SAL failed. Action: Reset the system. Upgrade system firmware. Cause: BMC failed. Action: Reset the BMC. Contact your HP representative to check the BMC.

Automated Recovery: None

Event Generation Threshold: 1 occurrence

Event Details:
Examples:
Event 552

Severity: MAJOR_WARNING

Event Summary: Unable to enter Guest mode during EFI security initialization

Event Class: System

Problem Description:
As part of normal security initialization, EFI attempted to issue a close session to the BMC (I.e. force the BMC to GUEST mode). This attempt failed. EFI is unable to initialize the security system. EFI will continue but security may be compromised. Data Field: Return status from internal EFI function.

Cause / Action:
Cause: SAL failure. Action: Reset the system. Upgrade system firmware. Cause: BMC failure. Action: Reset the BMC. Contact your HP representative to check the BMC.

Automated Recovery: None

Event Generation Threshold: 1 occurrence

Event Details:
Examples:
Event 553

Severity: MAJOR_WARNING

Event Summary: Unable to increase privilege during EFI security initialization

Event Class: System

Problem Description:
As part of normal security initialization, EFI attempted to issue an open session to the BMC in order to raise the privilege level to the highest permitted by a blank password. This attempt failed. EFI is unable to initialize the security system. Data Field: Return status from internal EFI function.

Cause / Action:
Cause: SAL failure. Action: Reset the system. Upgrade system firmware. Cause: BMC failure. Action: Reset the BMC. Contact your HP representative concerning the BMC.

Automated Recovery: None

Event Generation Threshold: 1 occurrence

Event Details:
Examples:
Event 554

Severity: MAJOR_WARNING

Event Summary: EFI unable to write privilege level during security initialization

Event Class: System

Problem Description:
As part of normal security initialization, EFI attempted to record the current privilege level. This attempt failed. EFI is unable to initialize the security system. Data Field: Return status from internal EFI function.

Cause / Action:
Cause: SAL failure. Action: Reboot the system. Upgrade system firmware.

Automated Recovery: None

Event Generation Threshold: 1 occurrence

Event Details:
Examples:
Event 555

Severity: MAJOR_WARNING

Event Summary: EFI was denied permission to write the privilege level during security init

Event Class: System

Problem Description:
As part of normal security initialization, EFI attempted to record the current privilege level. This attempt failed with a privilege violation error. EFI is unable to initialize the security system. Data Field: Return status from internal EFI function.

Cause / Action:
Cause: SAL is not in ADMIN or USER mode. Action: Reboot the system. Upgrade system firmware.

Automated Recovery: None

Event Generation Threshold: 1 occurrence

Event Details:
Examples:
Event 556

Severity: MAJOR_WARNING

Event Summary: OS dump, error writing image area to disk (E055)

Event Class: System

Problem Description:
OS dump, error writing image area to disk (E055)

Cause / Action:
panic path forward progress

Automated Recovery: None

Event Generation Threshold: 1 occurrence

Event Details:
Examples:
Event 557

Severity: SERIOUS

Event Summary: It stands for diagnosis of catastrophic errors in the PIN block of concorde.

Event Class: System

Problem Description:
This indicates that catastrophic errors have been found in the PIN block of the concorde. The cell needs to be reset/ halt.

Cause / Action:
This means that the cell will be reset.

Automated Recovery: None

Event Generation Threshold: 1 occurrence

Event Details:
Examples:
Event 558

Severity: SERIOUS

Event Summary: The cell monarch cpu has failed.

Event Class: System

Problem Description:
This means that the cell monach cpu has not completed the assigned task within the timeout and hence it will be deconfigured.

Cause / Action:
The monarch cpu will be deconfigured.

Automated Recovery: None

Event Generation Threshold: 1 occurrence

Event Details:
Examples:
Event 559

Severity: SERIOUS

Event Summary: This indicates that the cell missed the rendezvous at the partition level.

Event Class: System

Problem Description:
This indicates that the cell is too late for the PD level rendezvous. And hence it will not join the other PD cells.

Cause / Action:
The cell will independently step through some of the error logging steps and then finally reset itself.

Automated Recovery: None

Event Generation Threshold: 1 occurrence

Event Details:
Examples:
Event 560

Severity: SERIOUS

Event Summary: This means that the PD monarch timedout.

Event Class: System

Problem Description:
This indicates the state where the PD monarch was not able to complete the task within a certain time. It failed.

Cause / Action:
The cell will be reset ; also the partition will be reset.

Automated Recovery: None

Event Generation Threshold: 1 occurrence

Event Details:
Examples:
Event 561

Severity: SERIOUS

Event Summary: SetViewRoot on a remote cell failed.

Event Class: System

Problem Description:
System firmware on the Core cell was unable to update a slave cell with the location of the root of the partition tree. The CPU that was unable to be contacted is printed in the data field.

Cause / Action:
Inter Processor interrupts failed. Be sure that the partition rendezvous was successfully completed. Reset.

Automated Recovery: None

Event Generation Threshold: 1 occurrence

Event Details:
Examples:
Event 563

Severity: SERIOUS

Event Summary: This indicates the failure in collecting the Complex profile info.

Event Class: System

Problem Description:
This chassis code reports the failure in collecting the ICM parameters needed for the cell interleaving.

Cause / Action:
The partition level memory interleaving cannot continue without the appropriate information.

Automated Recovery: None

Event Generation Threshold: 1 occurrence

Event Details:
Examples:
Event 564

Severity: SERIOUS

Event Summary: This chassis code indicates the failure in collecting the cell info.

Event Class: System

Problem Description:
This chassis code indicates that the cell interleaving routine could not get the information on the cell memory.

Cause / Action:
The partition level memory will fail.

Automated Recovery: None

Event Generation Threshold: 1 occurrence

Event Details:
Examples:
Event 565

Severity: SERIOUS

Event Summary: This indicates the failure in updating the GNI info of the cell with CLM.

Event Class: System

Problem Description:
This chassis code is used to represent the failure in updating the GNI information of the cell with the CLM ( cell local memory) information obtained from the Complex Profile.

Cause / Action:
The partition level memory will fail at this point.

Automated Recovery: None

Event Generation Threshold: 1 occurrence

Event Details:
Examples:
Event 566

Severity: SERIOUS

Event Summary: This indicates the failure in adjusting the mem info with Minimum ZI req.

Event Class: System

Problem Description:
This represents the failure in adjusting the memory information with the minimum ZI requirements.

Cause / Action:
This will cause the partition level memory to exit cell interleaving.

Automated Recovery: None

Event Generation Threshold: 1 occurrence

Event Details:
Examples:
Event 567

Severity: SERIOUS

Event Summary: The Stable Complex Profile Sequence Id is invalid

Event Class: System

Problem Description:
The Complex Profile Group A sequence ID is invalid. Booting cannot continue. The actual data is in the chassis code data field.

Cause / Action:
Push out a new complex profile and reset the system. The cell will be waiting for reconfiguration.

Automated Recovery: None

Event Generation Threshold: 1 occurrence

Event Details:
Examples:
Event 568

Severity: MAJOR_WARNING

Event Summary: The Dynamic Complex Profile Sequence ID is invalid

Event Class: System

Problem Description:
The Dynamic Complex Profile (Group B) sequence ID is invalid. The invalid Sequence ID is displayed in the data field.

Cause / Action:
Push out a new complex profile.

Automated Recovery: None

Event Generation Threshold: 1 occurrence

Event Details:
Examples:
Event 569

Severity: SERIOUS

Event Summary: The Partition Profile Sequence ID is invalid

Event Class: System

Problem Description:
The Group C Partition Complex Profile Sequence ID is invalid. The value read is displayed in the data field.

Cause / Action:
Push out a new complex profile and reset. The cell will be waiting for reconfiguration.

Automated Recovery: None

Event Generation Threshold: 1 occurrence

Event Details:
Examples:
Event 570

Severity: CRITICAL

Event Summary: Internal Firmware Programming Error from the EFI portion of the firmware

Event Class: System

Problem Description:
An internal EFI firmware error was encountered. This is usually caused by a bad parameter passed to a function, corrupt memory, corrupt malloc, corrupt firmware tree or something similar. The data field contains the IP address of the function that encountered the error.

Cause / Action:
Report the IPF to the firmware team. Reset the system. This cannot be worked around in the field.

Automated Recovery: None

Event Generation Threshold: 1 occurrence

Event Details:
Examples:
Event 571

Severity: SERIOUS

Event Summary: The PD numbers in Group A and Group C of the complex profile are inconsistent.

Event Class: System

Problem Description:
The Complex Profile Group A PD assignment for this cell does not match the PD or Partition number in Group C of the complex profile. This is a fatal condition for the cell. The PD number from group A will be emitted first, followed by a subsequent code for the PD assigned in group C.

Cause / Action:
Push out consistent Complex profiles and reset the system. The cell will be waiting for reconfiguration.

Automated Recovery: None

Event Generation Threshold: 1 occurrence

Event Details:
Examples:
Event 572

Severity: SERIOUS

Event Summary: The PD number specified in the complex profile is out of range.

Event Class: System

Problem Description:
The Partition (PD) assigned to this cell in the complex profile group A and C is larger than the maximum allowed number of PDs as specified by Group A.

Cause / Action:
Reconfigure the partition number, push out a new profile and reset.

Automated Recovery: None

Event Generation Threshold: 1 occurrence

Event Details:
Examples:
Event 573

Severity: MAJOR_WARNING

Event Summary: Could not obtain the crossbar port semaphore

Event Class: System

Problem Description:
Tried to obtain the port semaphore but GetPortSemaphore returned an ERROR. Could be a failed write to the port semaphore crossbar CSR or another cell owned the semaphore. Data field bits 32:63 contain the crossbar ID and bits 0:31 contain the port number for which the semaphore was being obtained.

Cause / Action:
No action required.

Automated Recovery: None

Event Generation Threshold: 1 occurrence

Event Details:
Examples:
Event 574

Severity: MAJOR_WARNING

Event Summary: Could not release the crossbar port semaphore.

Event Class: System

Problem Description:
Currently owned the port semaphore but could not release the semaphore. Data field bits 32:63 contain the crossbar ID and bits 0:32 contain the port number.

Cause / Action:
No action required.

Automated Recovery: None

Event Generation Threshold: 1 occurrence

Event Details:
Examples:
Event 576

Severity: CRITICAL

Event Summary: BMC token upload failure

Event Class: System

Problem Description:
There was an error reading from the BMC token when attempting to write to SAL NVM. This is a stop boot condition. Data: BMC Token Number.

Cause / Action:
Cause: A read from the BMC failed. Action: AC power cycle if necessary, if problem persists contact your HP representative for support.

Automated Recovery: None

Event Generation Threshold: 1 occurrence

Event Details:
Examples:
Event 577

Severity: MAJOR_WARNING

Event Summary: NVM token access failure

Event Class: System

Problem Description:
The read from SAL NVM has failed. This is a stop boot condition. Data: The token number on which the write failed

Cause / Action:
Cause: NVM Error, or incorrect permissions to read token. Action: Retry, AC power cycle if necessary, if problem persists contact your HP representative for support.

Automated Recovery: None

Event Generation Threshold: 1 occurrence

Event Details:
Examples:
Event 578

Severity: CRITICAL

Event Summary: BMC token download failure

Event Class: System

Problem Description:
There was an error when trying to write to the BMC Tokens. This is a stop boot condition Data: lower 32 bits are BMC token number, upper 32 bits is the status return from the BMC.

Cause / Action:
Cause: BMC Error. Action: AC power cycle if necessary, if problem persists contact your HP representative for support.

Automated Recovery: None

Event Generation Threshold: 1 occurrence

Event Details:
Examples:
Event 579

Severity: CRITICAL

Event Summary: Error Writing BMC first boot token

Event Class: System

Problem Description:
There has been an error writing the BMC_FIRST_BOOT token. This is a stop boot condition.

Cause / Action:
Cause: BMC Error. Action: AC power cycle if necessary, if problem persists contact your HP representative for support.

Automated Recovery: None

Event Generation Threshold: 1 occurrence

Event Details:
Examples:
Event 580

Severity: MAJOR_WARNING

Event Summary: Fru Id read error

Event Class: System

Problem Description:
The read of the motherboard FRU has failed. Data: Device ID of device that failed the FRU read.

Cause / Action:
Cause: Error reading the motherboard FRU. Action: Reboot if necessary, if problem persists contact your HP representative for support.

Automated Recovery: None

Event Generation Threshold: 1 occurrence

Event Details:
Examples:
Event 581

Severity: MAJOR_WARNING

Event Summary: Fru Id checksum error

Event Class: System

Problem Description:
The read of the motherboard FRU has failed a checksum. Data: Device ID of device that failed the FRU read.

Cause / Action:
Cause: Error reading the motherboard FRU. Action: Reboot if necessary, if problem persists contact your HP representative for support.

Automated Recovery: None

Event Generation Threshold: 1 occurrence

Event Details:
Examples:
Event 582

Severity: MAJOR_WARNING

Event Summary: Fru Id version error

Event Class: System

Problem Description:
The read of the motherboard FRU has failed due to a version problem. Data: Device ID of device that failed the FRU read.

Cause / Action:
Cause: Error reading the motherboard FRU. Action: Reboot if necessary, if problem persists contact your HP representative for support.

Automated Recovery: None

Event Generation Threshold: 1 occurrence

Event Details:
Examples:
Event 583

Severity: MAJOR_WARNING

Event Summary: Rom revision not equal to FIT revision

Event Class: System

Problem Description:
A ROM Rev and FIT Rev do not match. Data: Code for what didn't match: 0x1 = PAL_A, 0x2 = PAL_B, 0x4 = SAL_A, 0x8 = ACPI, 0xA = EFI

Cause / Action:
Cause: A ROM Rev and FIT Rev do not match. Action: Update ROM, , if problem persists contact your HP representative for support.

Automated Recovery: None

Event Generation Threshold: 1 occurrence

Event Details:
Examples:
Event 584

Severity: MAJOR_WARNING

Event Summary: ROM revision not equal to Rev block

Event Class: System

Problem Description:
A ROM Rev and Rev Block do not match. Data: Code for what didn't match: 0x3 = PAL, 0x5 = SAL_A, 0x7 = SAL_B, 0x9 = ACPI, 0xB = EFI, 0xC = BMC

Cause / Action:
Cause: A ROM Rev and Rev Block do not match. Action: Update ROM, , if problem persists contact your HP representative for support.

Automated Recovery: None

Event Generation Threshold: 1 occurrence

Event Details:
Examples:
Event 585

Severity: MAJOR_WARNING

Event Summary: Primary Fit bad

Event Class: System

Problem Description:
The FIT is bad.

Cause / Action:
Cause: The FIT is bad. Action: Reboot, update ROM if necessary, if problem persists contact your HP representative for support.

Automated Recovery: None

Event Generation Threshold: 1 occurrence

Event Details:
Examples:
Event 586

Severity: MAJOR_WARNING

Event Summary: Secondary Fit bad

Event Class: System

Problem Description:
The FIT is bad.

Cause / Action:
Cause: The FIT is bad. Action: Reboot, update ROM if necessary, if problem persists contact your HP representative for support.

Automated Recovery: None

Event Generation Threshold: 1 occurrence

Event Details:
Examples:
Event 587

Severity: MAJOR_WARNING

Event Summary: PAL A execution rom warning

Event Class: System

Problem Description:
PAL_A_ROM has generated a warning.

Cause / Action:
Cause: PAL_A_ROM has generated a warning. Action: Reboot, update ROM if necessary, if problem persists contact your HP representative for support.

Automated Recovery: None

Event Generation Threshold: 1 occurrence

Event Details:
Examples:
Event 588

Severity: MAJOR_WARNING

Event Summary: PAL B execution rom warning

Event Class: System

Problem Description:
PAL_B_ROM has generated a warning.

Cause / Action:
Cause: PAL_B_ROM has generated a warning. Action: Reboot, update ROM if necessary, if problem persists contact your HP representative for support.

Automated Recovery: None

Event Generation Threshold: 1 occurrence

Event Details:
Examples:
Event 589

Severity: SERIOUS

Event Summary: An error was encountered when firmware tried to update the Group B Profile

Event Class: System

Problem Description:
Firmware tried to default the Dynamic (Group B) complex profile and encountered an error.

Cause / Action:
Manageability may be unavailable to update the profiles. Check the connections are reset.

Automated Recovery: None

Event Generation Threshold: 1 occurrence

Event Details:
Examples:
Event 590

Severity: SERIOUS

Event Summary: A DIMM loading order error has occurred

Event Class: System

Problem Description:
The loading order of the DIMMs is incorrect. The cell is halted.

Cause / Action:
Cause: Incorrect loading of the DIMMs on the cell 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.

Automated Recovery: None

Event Generation Threshold: 1 occurrence

Event Details:
Examples:
Event 591

Severity: MAJOR_WARNING

Event Summary: Refresh Control Error Timeout

Event Class: System

Problem Description:
Timeout Waiting for SDRAM parts to become ready - mem_status[0] Refresh Control Register

Cause / Action:
Cause: At start of memory refresh, timing out waiting for ready bit to be set Action: Contact HP Support personnel to troubleshoot the problem

Automated Recovery: None

Event Generation Threshold: 1 occurrence

Event Details:
Examples:
Event 592

Severity: MAJOR_WARNING

Event Summary: memory extender/baseboard FRU mismatch

Event Class: System

Problem Description:
The version of Memory extender installed in the system has not been qualified to work with the version of the baseboard installed in the system.

Cause / Action:
C: Memory extender and baseboard are incompatible A: Contact HP support to troubleshoot the problem

Automated Recovery: None

Event Generation Threshold: 1 occurrence

Event Details:
Examples:
Event 593

Severity: CRITICAL

Event Summary: Fabric topology mismatch with XBCs in complex

Event Class: System

Problem Description:
There is a fabric topology mismatch with the XBCs in the complex. Data Field: (Topology of XBC << 32) | Topology of destination XBC 0x00 Topology not yet determined 0x30 Domelight 0x40 U-Turn (Left cabinet) 0x41 U-Turn (Right cabinet) 0x42 Cross-Flex 0x43 U-Turn

Cause / Action:
There is a fabric topology mismatch with XBC in complex.
Contact HP Support personnel to analyze the cell, XBC flex cables, system backplane

Automated Recovery: None

Event Generation Threshold: 1 occurrence

Event Details:
Examples:
Event 594

Severity: SERIOUS

Event Summary: An invalid XBC to XBC port was found.

Event Class: System

Problem Description:
While routing the XBC to XBC ports, an invalid port was encountered. The data field is the crossbar number (32:43) and the port number (44:55).

Cause / Action:
Cause: Loss of Lockstep Action: Reset

Automated Recovery: None

Event Generation Threshold: 1 occurrence

Event Details:
Examples:
Event 595

Severity: MAJOR_WARNING

Event Summary: Could not get neighbor information.

Event Class: System

Problem Description:
The XBC could not get neighbor information. Data Field: XBC # << 32 | internal port attempting to access neighbor

Cause / Action:
Cause: Defective XBC link Defective XBC Action: Check XBC link connections Reset the system backplane Contact HP Support personnel to troubleshoot problem

Automated Recovery: None

Event Generation Threshold: 1 occurrence

Event Details:
Examples:
Event 596

Severity: SERIOUS

Event Summary: The XBC's routing state was marked as in ERROR

Event Class: System

Problem Description:
For the XBC being routed, routing has already been attempted, but an error occurred. Inspect chassis codes from other cells for more details regarding the nature of the problem. The data field consists of the XBC number (32:63)

Cause / Action:
Another cell already attempted routing for the XBC and found an error. Action: Check for hardware failure: flex cables, crossbar chip, etc.

Automated Recovery: None

Event Generation Threshold: 1 occurrence

Event Details:
Examples:
Event 597

Severity: MAJOR_WARNING

Event Summary: It indicates that there is no NVM error space left for logging an Error Event.

Event Class: System

Problem Description:
This means that the error event log cannot be logged to the persistent storage. The data field gives the event type that was supposed to be logged.

Cause / Action:
The error event will not be logged.

Automated Recovery: None

Event Generation Threshold: 1 occurrence

Event Details:
Examples:
Event 598

Severity: SERIOUS

Event Summary: An XBC port found to have an unexpected error.

Event Class: System

Problem Description:
An XBC port was found to have an unexpected error. The data field consists of the crossbar number (32:63) and the current port errors (0:31)

Cause / Action:
Cause: A port was landmined so it had to be routed around. Action: Check flex cables

Automated Recovery: None

Event Generation Threshold: 1 occurrence

Event Details:
Examples:
Event 599

Severity: SERIOUS

Event Summary: A XBC port route around has occurred

Event Class: System

Problem Description:
During fabric routing a port on a XBC was found in error or had been previously marked as in error. PDC will route around this XBC port. Data Field: XBC number (32:63) and external XBC port number (0:31)

Cause / Action:
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. 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.

Automated Recovery: None

Event Generation Threshold: 1 occurrence

Event Details:
Examples:
Event 600

Severity: MAJOR_WARNING

Event Summary: During routing a crossbar is found to be in an uexpected routing state.

Event Class: System

Problem Description:
Data field: the unexpected forward progress state (0:31) XBC number (32:44) Cell number (56:63)

Cause / Action:
Cause: An XBC is indicating a port failure Action: Validate all of the cells connectivity to the PD Check the TOGO chips seating reset the system replace either cells/system backplane

Automated Recovery: None

Event Generation Threshold: 1 occurrence

Event Details:
Examples:
Event 601

Severity: MAJOR_WARNING

Event Summary: An unexpected XBC forward progress state was continually found until timing out.

Event Class: System

Problem Description:
A crossbar was found to be in an unexpected forward progress state during fabric routing. This crossbar stayed in the unexpected state until Fabric Discovery timed out. Data filed: unexpected forward progress (0:31) XBC number (32:44) Cell number (56:63)

Cause / Action:
Cause: An XBC is indicating a port failure Action: Validate all of the cells connectivity to the PD Check the TOGO chips seating reset the system replace either cells/system backplane

Automated Recovery: None

Event Generation Threshold: 1 occurrence

Event Details:
Examples:
Event 602

Severity: CRITICAL

Event Summary: During remote routing, the current port's neighbor is not healthy.

Event Class: System

Problem Description:
An XBC port was found that is not healthy. This indicates at least one of the following about the port: - Hardware link is not okay - Presence detect is false - Fatal error detected - SBE detected - LPE detected - Port landmined The data field of the chassis code indicates which port is unhealthy, as well as the fabric routing state before the problem was encountered.

Cause / Action:
An XBC port is not healthy. Action: Check for hardware failure: flex cables, crossbar chips, etc.

Automated Recovery: None

Event Generation Threshold: 1 occurrence

Event Details:
Examples:
Event 603

Severity: CRITICAL

Event Summary: The CC to XBC link is not viable.

Event Class: System

Problem Description:
The CC to XBC link is not viable.

Cause / Action:
Cause: The CC to XBC link is not operational. Action: Reset the cell Reset the system backplane Contact HP Support personnel to troubleshoot problem

Automated Recovery: None

Event Generation Threshold: 1 occurrence

Event Details:
Examples:
Event 604

Severity: CRITICAL

Event Summary: Remote routing a crossbar failed.

Event Class: System

Problem Description:
There was a problem performing remote routing on the local XBC. Chassis codes sent before this one may provide more details about the exact nature of the problem. The data field consists of the XBC number that failed routing (32:63)

Cause / Action:
A failure was encountered while performing remote routing on an XBC, most likely due to a problem with the system backplane or local cell. Action: Check for hardware failure: CC, XBC to CC link, flex cables, crossbar chip, etc.

Automated Recovery: None

Event Generation Threshold: 1 occurrence

Event Details:
Examples:
Event 605

Severity: CRITICAL

Event Summary: Too many XBC-to-XBC were broken in the complex.

Event Class: System

Problem Description:
Two or more XBC-XBC links were found to be broken. The data field is the XBC number (32:63) and a bit map of the ports broken (0:31)

Cause / Action:
Port status indicated that two or more ports on a XBC had errors. Action: Check for hardware failure: flex cables, crossbar chip, etc.

Automated Recovery: None

Event Generation Threshold: 1 occurrence

Event Details:
Examples:
Event 606

Severity: SERIOUS

Event Summary: This cell did not get the XBC Global Semaphore.

Event Class: System

Problem Description:
After unlocking the XBC Global Semaphore for a takeover, this cell did not get the semaphore.

Cause / Action:
C1: Another cell won the race and got the semaphore before this cell. This would be apparent in chassis codes. A1: None. C2: XBC write or read failure. A2: check XBC, check link, check CC

Automated Recovery: None

Event Generation Threshold: 1 occurrence

Event Details:
Examples:
Event 607

Severity: CRITICAL

Event Summary: Attempted an XBC SM4 takeover and timed out trying to unlock the SM4.

Event Class: System

Problem Description:
When a cell holds an XBC semaphore for an extended period of time, fabric will attempt to takeover the semaphore so that the rest of the cells will have access to it. Fabric will attempt to take the SM4 for a period of time. If it is unable to unlock the SM4 within the timeout period, it will send this chassis code and halt the cell. Data field: XBC number (32:63) and current owner (cell) of the semaphore (0:31)

Cause / Action:
Cannot takeover an XBC semaphore that has been held for a long time. 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.

Automated Recovery: None

Event Generation Threshold: 1 occurrence

Event Details:
Examples:
Event 608

Severity: CRITICAL

Event Summary: Waiting for the XBC Global Semaphore has timed out.

Event Class: System

Problem Description:
During Fabric Discovery, the cell will wait until it gets the XBC's Global Semaphore. It waits for a very long time. This chassis code indicates that the wait has timed out.

Cause / Action:
XBC Key Contention. Hardware Failure Action: Look for other chassis codes that indicate XBC Key contention Check XBC Check Links/Flex Cables

Automated Recovery: None

Event Generation Threshold: 1 occurrence

Event Details:
Examples:
Event 609

Severity: CRITICAL

Event Summary: A timeout occurred while attempting to release the XBC semaphore.

Event Class: System

Problem Description:
The XBC Release Semaphore timeout is designed to fail last. The semaphore could not be released. Any other cell (even outside the PD) may be blocked because the XBC is a global resource. Data field: current semaphore owner (0:31) XBC number (32:43) port number (44:55) cell number (56:63)

Cause / Action:
XBC Key Contention. Hardware Failure Action: Look for additional chassis codes that would explain the failure Check XBC Check Link/Flex Cables

Automated Recovery: None

Event Generation Threshold: 1 occurrence

Event Details:
Examples:
Event 610

Severity: MAJOR_WARNING

Event Summary: Management Processor Firmware Battery Failure or NVRAM change

Event Class: System

Problem Description:
Management Processor Firmware detected improper data in NVRAM (bad checksums.) Either the NVRAM layout changed, or the Management Processor Battery may not be maintaining the data through A/C power cycles.

Cause / Action:
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.

Automated Recovery: None

Event Generation Threshold: 1 occurrence

Event Details:
Examples:
Event 611

Severity: MAJOR_WARNING

Event Summary: Management Processor Firmware Software Error

Event Class: System

Problem Description:
Management Processor Firmware detected a software error and is logging an event. The data represents data associated with the error seen.

Cause / Action:
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.

Automated Recovery: None

Event Generation Threshold: 1 occurrence

Event Details:
Examples:
Event 612

Severity: MAJOR_WARNING

Event Summary: Management Processor detected an I2C Communication Error with BMC.

Event Class: System

Problem Description:
An I2C Communication failure with the Baseboard Management Controller was detected. Without I2C communication, the system cannot be powered on/off or reset.

Cause / Action:
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.

Automated Recovery: None

Event Generation Threshold: 1 occurrence

Event Details:
Examples:
Event 613

Severity: SERIOUS

Event Summary: A CRC error was discovered when verifying the ROM

Event Class: System

Problem Description:
A stored CRC value did not match the calculated CRC value for the specified address.

Cause / Action:
Either the ROM was programmed incorrectly or has gone bad. Reprogram the Flash on the cell board.

Automated Recovery: None

Event Generation Threshold: 1 occurrence

Event Details:
Examples:
Event 614

Severity: MAJOR_WARNING

Event Summary: An error was encountered when executing a PAL_PROC

Event Class: System

Problem Description:
An error was encountered when executing a PAL_PROC. This code will be emitted in pairs. The Proc INDEX will be in the data of the first chassis code. The status is in the second data field.

Cause / Action:
PAL was unable to be successfully called. See other event ids to determine if action needs to be taken.

Automated Recovery: None

Event Generation Threshold: 1 occurrence

Event Details:
Examples:
Event 615

Severity: CRITICAL

Event Summary: CPUs (and or termination) loaded in wrong order

Event Class: System

Problem Description:
CPUs not loaded in correct order. Correct loading order is CPU 0, 1, 2, 3.

Cause / Action:
Cause: CPUs not loaded in correct order. Action: Load CPUs in order 0, 1, 2, 3.

Automated Recovery: None

Event Generation Threshold: 1 occurrence

Event Details:
Examples:
Event 616

Severity: SERIOUS

Event Summary: Error Reading a platform storage variable from the PDHC/MP

Event Class: System

Problem Description:
System firmware was unable to complete a platform storage read command from the utilities system. The exact status printed in the data field.

Cause / Action:
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.

Automated Recovery: None

Event Generation Threshold: 1 occurrence

Event Details:
Examples:
Event 617

Severity: SERIOUS

Event Summary: An error was returned on a Platform Storage Write Command to the PDHC/MP

Event Class: System

Problem Description:
System firmware was unable to complete a platform storage write command. The actual status is returned in the data field.

Cause / Action:
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.

Automated Recovery: None

Event Generation Threshold: 1 occurrence

Event Details:
Examples:
Event 618

Severity: SERIOUS

Event Summary: The Sequencer was unable to find/use a needed tree node

Event Class: System

Problem Description:
The Sequencer was unable to find the tree node it needed to complete an operation. The tree node is in the ascii in the data field.

Cause / Action:
This is a bug, contact engineering

Automated Recovery: None

Event Generation Threshold: 1 occurrence

Event Details:
Examples:
Event 619

Severity: SERIOUS

Event Summary: Firmware encountered an error in processing the partition variables

Event Class: System

Problem Description:
System firmware attempted to read a partition variable from the GSP and store it in options. An error was encountered during this process. The data field contains the partition variable element ID that was being processed.

Cause / Action:
Either the GSP was not present or there was a resourse problem storing the variable. There should be other clues in the event id log to indicate which is the case. Restore the GSP.

Automated Recovery: None

Event Generation Threshold: 1 occurrence

Event Details:
Examples:
Event 620

Severity: SERIOUS

Event Summary: A non-critical cell power fault has occurred

Event Class: System

Problem Description:
One or more power converter on the Cell or Cell Power Board has reported a fault. However, because of redundancy in the power system, the power to the Cell is still good. The data field contains detailed power fault location information (see Cell ERS for more information). Data Byte[0]: bit0 - Power_Fault status, bit1 - Power_Good status Data Byte[1]: Contents of Power Board Converter Status register. Data Byte[2]: Contents of Cell Converter Status register. Data Byte[3]: Contents of CPU Module Power Status register.

Cause / Action:
Cause(1): A power converter has failed. Cause(2): A CPU Power Module has been disabled following a thermal warning reported by that CPU Module.
Action: Contact HP Support personnel to troubleshoot the problem

Automated Recovery: None

Event Generation Threshold: 1 occurrence

Event Details:
Examples:
Event 622

Severity: MAJOR_WARNING

Event Summary: Firmware was unable to determine the Processor Dependent Features

Event Class: System

Problem Description:
System firmware was unable to successfully issue the PAL_GET_PROC_FEATURES PAL proc. The data field is unused

Cause / Action:
Contact Engineering, This is a bug.

Automated Recovery: None

Event Generation Threshold: 1 occurrence

Event Details:
Examples:
Event 624

Severity: SERIOUS

Event Summary: The CLU has encountered an undefined case

Event Class: System

Problem Description:
The CLU has encountered an undefined case in its control flow.

Cause / Action:
Cause: CLU firmware on the UGUY has gotten into an unexpected execution path, most likely due to a hardware issue on the UGUY. 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

Automated Recovery: None

Event Generation Threshold: 1 occurrence

Event Details:
Examples:
Event 625

Severity: MAJOR_WARNING

Event Summary: An unknown Cell voltage margin has been detected.

Event Class: System

Problem Description:
The Cell voltage margin settings do not match the Normal, +5%, or -5% values.

Cause / Action:
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.

Automated Recovery: None

Event Generation Threshold: 1 occurrence

Event Details:
Examples:
Event 626

Severity: MAJOR_WARNING

Event Summary: The run-time verification of a programming assumption has failed.

Event Class: System

Problem Description:
For debug purposes, many assumptions made by the PDHC developer(s) are checked at run-time. If this event log is seen, it will either indicate that the hardware is in a unknown state that is not handled by the PDHC, or that a programming bug has been found. For developer debug purposes, the data field describes where in the code that the error was detected. Data Bytes[0-1]: The line number within the source code file where the error was detected. Data Bytes[2-7]: The first 6 characters of the source code file name.

Cause / Action:
Cause: Hardware in unknown state, or programming bug found.
Action: Upgrade PDHC firmware to latest revision. If already at current revision, contact HP Support personnel to troubleshoot the problem.

Automated Recovery: None

Event Generation Threshold: 1 occurrence

Event Details:
Examples:
Event 627

Severity: MAJOR_WARNING

Event Summary: An unknown error has been detected by the PDHC firmware.

Event Class: System

Problem Description:
An unknown error has been detected by the PDHC firmware. For developer debug purposes, the data field describes where in the code that the error was detected. Data Bytes[0-1]: The line number within the source code file where the error was detected. Data Bytes[2-7]: The first 6 characters of the source code file name.

Cause / Action:
Cause: Hardware in unknown state, or programming bug found.
Action: Upgrade PDHC firmware to latest revision. If already at current revision, contact HP support personnel to troubleshoot the problem.

Automated Recovery: None

Event Generation Threshold: 1 occurrence

Event Details:
Examples:
Event 628

Severity: MAJOR_WARNING

Event Summary: An attempt to write to a device on the PDHCs I2C bus has failed.

Event Class: System

Problem Description:
An attempt to write to a device on the PDHC's I2C bus has failed. The devices on the I2C bus are the Cell's FRU EEPROM, the Cell Power Board's FRU EEPROM, the voltage margining D-to-A converters, and, if they are accessible, the CPU Module Power Pods' FRU EEPROMs. The Data field information contains information that can identify the exact device that has failed. Refer to the Cell ERS for a mapping of I2C device addresses to devices. Data Bytes[0-1]: Reserved Data Bytes[2-3]: I2C Device Address Data Bytes[4-5]: Starting Word Address Data Bytes[6-7]: Size of attempted access (in bytes).

Cause / Action:
Cause: A hardware fault has occurred.
Action: Contact HP Support personnel to troubleshoot the Cell Board, Cell Power Board, and/or PDH Daughtercard.

Automated Recovery: None

Event Generation Threshold: 1 occurrence

Event Details:
Examples:
Event 629

Severity: MAJOR_WARNING

Event Summary: An attempt to read from a device on the PDHC's I2C bus has failed.

Event Class: System

Problem Description:
An attempt to read from a device on the PDHC's I2C bus has failed. The devices on the I2C bus are the Cell's FRU EEPROM, the Cell Power Board's FRU EEPROM, the voltage margining D-to-A converters, and, if they are accessible, the CPU Module Power Pods' FRU EEPROMs. The Data field information contains information that can identify the exact device that has failed. Refer to the Cell ERS for a mapping of I2C device addresses to devices. Data Bytes[0-1]: Reserved Data Bytes[2-3]: I2C Device Address Data Bytes[4-5]: Starting Word Address Data Bytes[6-7]: Size of attempted access (in bytes).

Cause / Action:
Cause: A hardware fault has occurred.
Action: Contact HP Support personnel to troubleshoot the Cell Board, Cell Power Board, and/or PDH Daughtercard.

Automated Recovery: None

Event Generation Threshold: 1 occurrence

Event Details:
Examples:
Event 630

Severity: MAJOR_WARNING

Event Summary: An attempt to write to a device on the PDHC's SM bus has failed.

Event Class: System

Problem Description:
An attempt to write to a device on the PDHC's SM bus has failed. The devices on the SM bus are the CPU modules' FRU EEPROMs, the CPU modules' Processor Information ROMs, and the CPU modules' thermal sensors. The Data field information contains information that can identify the exact device that has failed. Refer to the Cell ERS for a mapping of SM Bus device addresses to devices. Data Bytes[0-1]: Reserved Data Bytes[2-3]: SM bus Device Address Data Bytes[4-5]: Starting Word Address Data Bytes[6-7]: Size of attempted access (in bytes).

Cause / Action:
Cause: A hardware fault has occurred.
Action: Contact HP Support personnel to troubleshoot the Cell Board, Cell Power Board, and/or PDH Daughtercard.

Automated Recovery: None

Event Generation Threshold: 1 occurrence

Event Details:
Examples:
Event 631

Severity: MAJOR_WARNING

Event Summary: An attempt to read from a device on the PDHC's SM bus has failed.

Event Class: System

Problem Description:
An attempt to read from a device on the PDHC's SM bus has failed. The devices on the SM bus are the CPU modules' FRU EEPROMs, the CPU modules' Processor Information ROMs, and the CPU modules' thermal sensors. The Data field information contains information that can identify the exact device that has failed. Refer to the Cell ERS for a mapping of SM Bus device addresses to devices. Data Bytes[0-1]: Reserved Data Bytes[2-3]: SM bus Device Address Data Bytes[4-5]: Starting Word Address Data Bytes[6-7]: Size of attempted access (in bytes).

Cause / Action:
Cause: A hardware fault has occurred.
Action: Contact HP Support personnel to troubleshoot the Cell Board, Cell Power Board, and PDH Daughtercard.

Automated Recovery: None

Event Generation Threshold: 1 occurrence

Event Details:
Examples:
Event 632

Severity: SERIOUS

Event Summary: Cell boot has been disabled due to a failure setting the frequency registers.

Event Class: System

Problem Description:
The PDHC did not read valid frequency information from the CPU modules' or Cell's FRU EEPROMs, or the frequency registers would not update properly. Following this event, the Cell will not boot until the problem is corrected and Cell Power has been turned off, then on again, using the PE command.

Cause / Action:
Cause(1, probable): Invalid data programmed in the Cell's FRU EEPROM or a CPU module's Scratch/FRU EEPROM. Action (1): If in manufacturing, program correct data in partition specific field of the Cell or CPU Module's FRU EEPROM. Otherwise, contact HP support personnel to troubleshoot the problem. Cause(2): A hardware fault has occurred. Action(2): Contact HP Support personnel to troubleshoot the problem.

Automated Recovery: None

Event Generation Threshold: 1 occurrence

Event Details:
Examples:
Event 633

Severity: MAJOR_WARNING

Event Summary: An error has occurred while updating System FW.

Event Class: System

Problem Description:
An error has occurred while updating System FW. More details about the update failure may be available as displayed by the Firmware Update Utility (FWUU).

Cause / Action:
Cause(1): Obsolete version of FWUU. Action(1): If you are not using the latest revision of FWUU, obtain and use the latest version of FWUU to retry the update. Cause(2): MP firmware not at a revision that supports the current version of PDHC FW or System FW. Action(2): If MP is not at a compatible revision, update the MP firmware to a compatible revision and repeat the firmware update. Cause(3): Other error indicated by FWUU. Action(3): Exit from FWUU, reset the MP using the XD command, then attempt to update System FW. If repeated attempts to update the System FW fail, contact HP support personnel to troubleshoot the problem.

Automated Recovery: None

Event Generation Threshold: 1 occurrence

Event Details:
Examples:
Event 634

Severity: MAJOR_WARNING

Event Summary: The PDHC firmware was reset for some unknown reason.

Event Class: System

Problem Description:
The PDHC firmware was reset for some unknown reason.

Cause / Action:
Cause(1): System FW has reset the PDHC because it suspects the PDHC of corrupting shared memory. Cause(2): A PDHC watchdog timer timeout has occurred because the PDHC was stuck in some unknown state. Cause(3): An unknown hardware fault has caused the PDHC to reset.
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.

Automated Recovery: None

Event Generation Threshold: 1 occurrence

Event Details:
Examples:
Event 635

Severity: SERIOUS

Event Summary: Cell boot has been disabled because setup of a CPU thermal sensor failed.

Event Class: System

Problem Description:
A hardware fault prevented the PDHC from configuring the thermal sensor(s) on one or more of the CPU modules. Following detection of this fault condition, the Cell will be prevented from booting until the Cell is powered "off", then "on", using the PE command.

Cause / Action:
Cause(1): A hardware fault exists in the communication path to a CPU module's thermal sensor, or in the thermal sensor itself. Cause(2): A hardware fault prevents access to a CPU module's Processor Information ROM.
Action: Contact HP support personnel to troubleshoot the Cell Board, the PDH Daughtercard, and/or the offending CPU module.

Automated Recovery: None

Event Generation Threshold: 1 occurrence

Event Details:
Examples:
Event 636

Severity: SERIOUS

Event Summary: A CPU module has reported overtemp, so will be powered off in 2 minutes.

Event Class: System

Problem Description:
A CPU module's temperature has exceed the high temperature threshold. As a result of this event, an irrevocable 2 minute timer will begin. At the end of 2 minutes, the offending CPU module will be powered off by the Cell hardware. The Cell must be powered off then on using the MP's PE command before the CPU module will be powered again.

Cause / Action:
Cause(1): Excessive heat in the data center has caused the CPU module to heat up beyond the programmed temperature threshold. Action(1): Resolve the environmental problem, shut down the partition, then PE the Cell off, then on again. Cause(2): A hardware fault has caused the CPU module to heat up beyond the programmed temperature threshold. Cause(3): The Processor Information ROM on the processor module is unprogrammed or programmed with invalid temperature thresholds. Action(2,3): Contact HP support personnel to troubleshoot the problem.
Cause(1): Excessive heat in the data center has caused the CPU module to heat up beyond the programmed temperature threshold. Action(1): Resolve the environmental problem, shut down the partition, then PE the Cell off, then on again. Cause(2): A hardware fault has caused the CPU module to heat up beyond the programmed temperature threshold. Cause(3): The Processor Information ROM on the processor module is unprogrammed or programmed ! with invalid temperature thresholds. Action(2,3): Contact HP support personnel to troubleshoot the problem

Automated Recovery: None

Event Generation Threshold: 1 occurrence

Event Details:
Examples:
Event 637

Severity: MAJOR_WARNING

Event Summary: An error occurred while updating the PDHC firmware.

Event Class: System

Problem Description:
An error occurred while updating the PDHC firmware. More specific details of the update error may be displayed by the Firmware Update utility running on the MP.

Cause / Action:
Cause(1): MP firmware not at a revision that supports that version of PDHC firmware. Action(1): If MP is not at a compatible revision, update the MP firmware to a compatible revision and repeat PDHC firmware update. Cause(2): Other error indicated by Firmware Update. Action(2): Exit from Firmware Update, reset the MP using the XD command, then attempt to update PDHC firmware again. If repeated attempts to update the PDHC firmware fail, contact HP support personnel to troubleshoot the problem
Cause(1): MP firmware not at a revision that supports that version of PDHC firmware. Action(1): If MP is not at a compatible revision, update the MP firmware to a compatible revision and repeat PDHC firmware update. Cause(2): Other error indicated by Firmware Update. Action(2): Exit from Firmware Update, reset the MP using the XD command, then attempt to update PDHC firmware again. If repeated attempts to update the PDHC firmware fail, contact HP support personnel to troubleshoot ! the problem.

Automated Recovery: None

Event Generation Threshold: 1 occurrence

Event Details:
Examples:
Event 638

Severity: SERIOUS

Event Summary: CPU Revisions did not match

Event Class: System

Problem Description:
2 cpus in the system are reporting different revisions. This event will be emitted in groups of 3 with the two revisions reported in the first 2 data fields and the cpu number in the 3rd data field.

Cause / Action:
2 cpus are at different revisions. Replace incompatible cpu.

Automated Recovery: None

Event Generation Threshold: 1 occurrence

Event Details:
Examples:
Event 639

Severity: SERIOUS

Event Summary: 2 cpus are running at mismatched frequencies.

Event Class: System

Problem Description:
This chassis code will be emitted in pairs. 2 cpus are reporting that they are running at different frequencies. The two frequencies are reported in the data fields.

Cause / Action:
There is a CPU or Cell compatibility problem. Verify that all cpus are clocked at the same frequency and have the same ratios set.

Automated Recovery: None

Event Generation Threshold: 1 occurrence

Event Details:
Examples:
Event 640

Severity: SERIOUS

Event Summary: A cpu is being overclocked

Event Class: System

Problem Description:
The rating for the cpu and the actual speed will be emitted in 2 sequential event data fields.

Cause / Action:
A cpu is being clocked at a rate higher than it is rated for. Replace the cpu or cell board.

Automated Recovery: None

Event Generation Threshold: 1 occurrence

Event Details:
Examples:
Event 641

Severity: CRITICAL

Event Summary: Copy of complex profile on sub and cells don't match

Event Class: System

Problem Description:
The complex profile is stored in NVRAM on the MP and each cell. All copies must match. For this error to be generated, not only is the MP's copy of the complex profile invalid, but not all of the cell's copies match.

Cause / Action:
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". 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.

Automated Recovery: None

Event Generation Threshold: 1 occurrence

Event Details:
Examples:
Event 642

Severity: CRITICAL

Event Summary: Duplicate cabinet number detected

Event Class: System

Problem Description:
The MP detected 2 or more cabinets with the same cabinet number.

Cause / Action:
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. 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).

Automated Recovery: None

Event Generation Threshold: 1 occurrence

Event Details:
Examples:
Event 643

Severity: CRITICAL

Event Summary: MP ID command must be run

Event Class: System

Problem Description:
The complex identification information in group A of the complex profile is invalid. The MP (Manageability Processor) command "ID" must be run. The SSKEY hardware is required.

Cause / Action:
Cause: This is the first time the machine has been powered on and there is no valid complex profile anywhere. Action: Run "CC" command and generate genesis profile. 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. 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.

Automated Recovery: None

Event Generation Threshold: 1 occurrence

Event Details:
Examples:
Event 645

Severity: MAJOR_WARNING

Event Summary: MP Battery is low

Event Class: System

Problem Description:
The battery on the SBCH is below the safe threshold. The battery can be replaced online.

Cause / Action:
Cause: MP was running on battery for too long. Someone didn't set "NVRAM Save" switch to "off". Action: Replace battery as per MP Battery Remove and Replace procedures.

Automated Recovery: None

Event Generation Threshold: 1 occurrence

Event Details:
Examples:
Event 646

Severity: CRITICAL

Event Summary: Partition being reset due to watchdog timeout expiring

Event Class: System

Problem Description:
The partition is being reset because its watchdog timer expired and automatic restart is enabled.

Cause / Action:
Cause: There are 2 watchdog mechanisms, both of which trigger 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 fields specifies the desired timeout. This timer can be disabled with the MP AR command. IPF systems refresh the watchdog timer using the IPMI clear watchdog command. The AR command does not affect the IPMI watchdog timer. Regardless of which timer was in use, the MP emits this event when timer expiration triggers resetting the partition. 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 bei! ng unresponsive.

Automated Recovery: None

Event Generation Threshold: 1 occurrence

Event Details:
Examples:
Event 647

Severity: MAJOR_WARNING

Event Summary: PDHC FW was reset by hardware due to firmware inactivity.

Event Class: System

Problem Description:
The processor dependent hardware controller (PDHC) on the cell board had its watchdog timer expire. The PDHC will reset the watchdog as the main program runs. If the watchdog does not get reset within 7 seconds the timer will expire, resetting the PDHC.

Cause / Action:
Cause: Processor dependent hardware controller (PDHC) Hardware Failed; causing inactivity. PDHC Firmware hung; causing inactivity.
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.

Automated Recovery: None

Event Generation Threshold: 1 occurrence

Event Details:
Examples:
Event 649

Severity: MAJOR_WARNING

Event Summary: Power Up Aborted, Over Temp

Event Class: System

Problem Description:
The Cabinet Power Up request was aborted due to ambient air over temperature.

Cause / Action:
Cause: Computer Room over temp Action: Cool Computer Room Cause: Environment immediately surrounding cabinet. Action: Correct local environmental problem Cause: Reporting Error Action: Troubleshoot ambient air sensor/cable/PM3.

Automated Recovery: None

Event Generation Threshold: 1 occurrence

Event Details:
Examples:
Event 651

Severity: CRITICAL

Event Summary: No Cabinet Start, Insufficient Blowers

Event Class: System

Problem Description:
When given a power up request, the cabinet had to abort the start up due to less than the required number of Cabinet Blowers installed.

Cause / Action:
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. Action: Install missing Cabinet Blowers. If proper number of blowers are installed, troubleshoot blower presence detection.

Automated Recovery: None

Event Generation Threshold: 1 occurrence

Event Details:
Examples:
Event 652

Severity: CRITICAL

Event Summary: No Cabinet Start, Insufficient IO Fans

Event Class: System

Problem Description:
When given a power up request, the cabinet had to abort the start up due to less than the required number of IO fans present.

Cause / Action:
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. Action: Install missing IO fans, or if proper number installed, troubleshoot IO fan presence detection.

Automated Recovery: None

Event Generation Threshold: 1 occurrence

Event Details:
Examples:
Event 653

Severity: MAJOR_WARNING

Event Summary: AC power to the PDCA was removed. Data Byte 3 specifies PDCA number.

Event Class: System

Problem Description:
The AC power connected to the PDCA (Power Distribution Control Assembly) was removed. The data field contains the physical location of the PDCA. The PDCA source that was deleted can be identified by the implementation dependent field (data byte 3) of the physical location: data byte[3]: 0 for PDCA 0, 1 for PDCA 1.

Cause / Action:
Cause: Circuit breakers on the PDCA are open. Action: Close the PDCA circuit breakers. Cause: Power source supplying AC to the PDCA has failed. Action: Troubleshoot AC power problem. Cause: PDCA (Power Distribution Control Assembly) has failed. Action: Replace the PDCA with proper type (4-wire or 5-wire) PDCA following power distribution control assembly Remove and Replace procedures. Cause: AC Detection and monitoring circuitry failed. Action: Troubleshoot and replace failed Field Replaceable Units.

Automated Recovery: None

Event Generation Threshold: 1 occurrence

Event Details:
Examples:
Event 654

Severity: MAJOR_WARNING

Event Summary: Cabinet Main Blower Failed

Event Class: System

Problem Description:
A cabinet main blower has failed. Depending on the number of blowers still operating, the cabinet may or may not shut down. View the Error Log entries to determine if the cabinet is operating. If many log entries call out entities powering off during the same time frame as this BLOWR_FAIL, the cabinet has probably shutdown. Carefully review the log for the first few events within the same time frame for the root cause of the problem. The GSP command, PS, will show a detailed power status for a cabinet. If the +48V LED on the Front Panel Board is not lit, power is not enabled to the cabinet. This is an indication the cabinet blowers have probably gone from N to N - 1 status requiring an immediate cabinet shutdown.

Cause / Action:
Cause: Cabinet Blower Failed Action: Replace failed blower module as soon as possible following the Blower Module Remove and Replace Procedures.

Automated Recovery: None

Event Generation Threshold: 1 occurrence

Event Details:
Examples:
Event 655

Severity: MAJOR_WARNING

Event Summary: 48 Volt Converter Failed. Data Byte 3 specifies PDCA number.

Event Class: System

Problem Description:
A 48 Volt DC Converter powered by the specified PDCA failed on the designated Bulk Power Supply. The PDCA powering the converter on the BPS that failed can be identified by the implementation dependent field (data byte 3) of the BPS' physical location: data byte[3]: 0 for PDCA 0, 1 for PDCA 1.

Cause / Action:
Cause: The 48 Volt DC Converter powered by the PDCA identified failed in the named Bulk Power Supply. Action: Contact HP Support personnel to troubleshoot problem Cause: The PDCA identified has failed. This will be evident by many BPS_FAIL codes and probably a AC_DELETED code in the Event Log. Action: Contact HP Support personnel to troubleshoot problem

Automated Recovery: None

Event Generation Threshold: 1 occurrence

Event Details:
Examples:
Event 657

Severity: MAJOR_WARNING

Event Summary: Fan failed in designated Bulk Power Supply

Event Class: System

Problem Description:
The designated Bulk Power Supply is reporting its fan has failed.

Cause / Action:
Cause: Fan failure or fan obstructed Action: If fan is obstructed, remove obstruction. If no obstruction, Contact HP Support personnel to troubleshoot problem.

Automated Recovery: None

Event Generation Threshold: 1 occurrence

Event Details:
Examples:
Event 659

Severity: MAJOR_WARNING

Event Summary: Bulk Power Supplies are not Redundant.

Event Class: System

Problem Description:
The number of functioning Bulk Power Supplies has decreased to where the Cabinet Power supplied (number of available Bulk Power Supplies times power output per each) minus the estimated Cabinet Power consumed is greater than 0, but less than the output of one Bulk Power Supply.

Cause / Action:
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. Action: Purchase and install a Bulk Power Supply, if redundancy is desired. Cause: Bulk Power Supply failed. Action: Contact HP Support personnel to troubleshoot problem.

Automated Recovery: None

Event Generation Threshold: 1 occurrence

Event Details:
Examples:
Event 660

Severity: CRITICAL

Event Summary: +48V DC has exceeded its upper limit

Event Class: System

Problem Description:
The PM has detected the value of +48V power, as measured on the UGUY board, has exceeded an upper threshold.

Cause / Action:
Cause: The cabinet's 48V power has exceeded an acceptable upper threshold. Action: Contact HP Support personnel to troubleshoot problem.

Automated Recovery: None

Event Generation Threshold: 1 occurrence

Event Details:
Examples:
Event 661

Severity: CRITICAL

Event Summary: +48V DC has fallen below its lower limit

Event Class: System

Problem Description:
The PM has detected the value of +48V power, as measured on the UGUY board, has fallen below a lower threshold.

Cause / Action:
Cause: The cabinet's 48V power has fallen below an acceptable lower threshold. Action: Contact HP Support personnel to troubleshoot problem.

Automated Recovery: None

Event Generation Threshold: 1 occurrence

Event Details:
Examples:
Event 662

Severity: MAJOR_WARNING

Event Summary: Cabinet Fan Failed

Event Class: System

Problem Description:
A cabinet fan has failed. Depending on the number of cabinet fans still operating, the cabinet may or may not shut down. View the Error Log entries to determine if the cabinet is operating.

Cause / Action:
Cause: Cabinet Fan Failed Action: Replace failed cabinet fan module as soon as possible following the Cabinet Fan Module Remove and Replace Procedures.

Automated Recovery: None

Event Generation Threshold: 1 occurrence

Event Details:
Examples:
Event 670

Severity: CRITICAL

Event Summary: Housekeeping power has exceeded expected levels.

Event Class: System

Problem Description:
Housekeeping power has exceeded expected levels.

Cause / Action:
Cause: The cabinet's housekeeping power has risen above an acceptable upper threshold. Action: Contact HP Support personnel to troubleshoot problem.

Automated Recovery: None

Event Generation Threshold: 1 occurrence

Event Details:
Examples:
Event 671

Severity: CRITICAL

Event Summary: Housekeeping power has fallen below expected levels.

Event Class: System

Problem Description:
Housekeeping power has fallen below expected levels.

Cause / Action:
Cause: The cabinet's housekeeping power has fallen below an acceptable upper threshold. Action: Contact HP Support personnel to troubleshoot problem.

Automated Recovery: None

Event Generation Threshold: 1 occurrence

Event Details:
Examples:
Event 672

Severity: MAJOR_WARNING

Event Summary: The BPSs for the cabinet are illegally configured. Data Byte 3 = PDCA number.

Event Class: System

Problem Description:
Through failures or reconfiguration, the BPS for the cabinet named are illegally configured. There must be a BPS connected to each phase of the power. Phase 1 feeds BPS slots 0 & 1, phase 2 feeds slots 2 & 3, and phase 3 feeds 4 & 5. There must be a BPS connected to each phase. If 4 BPS are installed in a cabinet in slots 0 - 3 and 4 & 5 were empty, this would be an illegal configuration. They should be installed in 0,1,2,and 4 or 0,1,3,and 5 or some combination thereof. The PDCA physical location determines which phase is configured incorrectly. Data Byte 3 (implementation dependent field) indicates the PDCA number used when the configuration error occurred:

Cause / Action:
Cause: The BPS are installed in an illegal configuration. Action: Re-configure the BPS in a manner consistent with the explanation in the Problem Description statement

Automated Recovery: None

Event Generation Threshold: 1 occurrence

Event Details:
Examples:
Event 673

Severity: MAJOR_WARNING

Event Summary: BPS ID received from installed Bulk Power Supply was unknown

Event Class: System

Problem Description:
A Bulk Power Supply is reporting an unknown BPS ID. The Bulk Power Supply will not be powered up and added to the Power Available tally. If cabinet is not powered up, it will refuse to power up until this fault is corrected.

Cause / Action:
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. Action: Replace this Bulk Power Supply with a proper one. Cause: A new revision of Power Supply that requires a PM3 firmware upgrade was attempting install. Action: Check service notes for firmware revisions and compatibility charts.

Automated Recovery: None

Event Generation Threshold: 1 occurrence

Event Details:
Examples:
Event 675

Severity: CRITICAL

Event Summary: Ambient Air Sensor Overtemp Warning

Event Class: System

Problem Description:
The cabinet's Ambient Air Sensor detected a change in air temperature entering the over-temp-high range. The Cabinet will be shutting itself down to prevent component damage.

Cause / Action:
Cause: Room Temperature has risen to a critical level. Action: Shutdown and power off the system. Correct air temperature problem.

Automated Recovery: None

Event Generation Threshold: 1 occurrence

Event Details:
Examples:
Event 676

Severity: MAJOR_WARNING

Event Summary: Ambient Air Sensor Overtemp Warning

Event Class: System

Problem Description:
The cabinet's Ambient Air Sensor detected a change in air temperature crossing to the low range. The air temperature may be rising or falling. This is just a reporting of entering the over-temp-low range.

Cause / Action:
Cause: Room Temperature is rising or falling. 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.

Automated Recovery: None

Event Generation Threshold: 1 occurrence

Event Details:
Examples:
Event 677

Severity: MAJOR_WARNING

Event Summary: Ambient Air Sensor Overtemp Warning

Event Class: System

Problem Description:
The cabinet's Ambient Air Sensor detected a change in air temperature crossing to the mid range. The air temperature may be rising or falling. This is just a reporting of entering the over-temp-mid range.

Cause / Action:
Cause: Room Temperature is rising or falling. 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.

Automated Recovery: None

Event Generation Threshold: 1 occurrence

Event Details:
Examples:
Event 678

Severity: MAJOR_WARNING

Event Summary: IO Fan Failed

Event Class: System

Problem Description:
An IO Chassis cooling fan has failed. Depending on the number of fans still operating, the cabinet may or may not shut down. View Error Log entries to determine if the cabinet is operating. If many log entries call out entities powering off during the same time frame as this IOFAN_FAIL, the cabinet has probably shutdown. Carefully review the log for the first few events within the same time frame for the root cause of the problem. The Guardian Service Processor command, PS, will show a detailed power status for a cabinet. The +48V LED on the Front Panel Board not lit, power is not enabled to the cabinet, indicating the cabinet IO Chassis fans have probably gone from N to N - 1 status requiring an immediate cabinet shutdown.

Cause / Action:
Cause: IO Cooling Fan Failed Action: Replace IO Fan Module as soon as possible following the IO Fan Module Remove and Replace Procedures.

Automated Recovery: None

Event Generation Threshold: 1 occurrence

Event Details:
Examples:
Event 680

Severity: MAJOR_WARNING

Event Summary: Cabinet Power System is in overload.

Event Class: System

Problem Description:
This code is issued when the Cabinet Power supplied (number of Bulk Power Supplies times power output per each) minus the estimated Cabinet Power consumed drops below 0. Utilities firmware will not allow a cabinet in this state to power up (see ABORT_PWRUP_BPS). Utilities firmware will not shut down a cabinet in this state. However, there is a possibility of a cabinet brownout, making the cabinet unreliable.

Cause / Action:
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. Action: Contact HP Support personnel to troubleshoot the problem.

Automated Recovery: None

Event Generation Threshold: 1 occurrence

Event Details:
Examples:
Event 681

Severity: CRITICAL

Event Summary: Cabinet Shutdown - Insufficient Blowers

Event Class: System

Problem Description:
After a BLOWR_FAIL, there were N-1 blowers functioning. This is an illegal condition causing immediate cabinet shutdown to prevent component damage.

Cause / Action:
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. Action: Contact HP Support personnel to troubleshoot the problem

Automated Recovery: None

Event Generation Threshold: 1 occurrence

Event Details:
Examples:
Event 682

Severity: CRITICAL

Event Summary: Cabinet Shutdown - Insufficient IO Fans

Event Class: System

Problem Description:
After a IOFAN_FAIL, there were N-1 fans functioning. This is an illegal condition causing immediate cabinet shutdown to prevent component damage.

Cause / Action:
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. Action: Contact HP Support personnel to troubleshoot the problem

Automated Recovery: None

Event Generation Threshold: 1 occurrence

Event Details:
Examples:
Event 683

Severity: MAJOR_WARNING

Event Summary: IO Expansion Utility Cabinet Fan Failed

Event Class: System

Problem Description:
One of two fans in the Utility chassis of the IO Expansion Cabinet has failed.

Cause / Action:
Cause: IO Expansion Utility Fan or Fan sensor failure PM failure Action: Contact HP Support personnel to troubleshoot the problem

Automated Recovery: None

Event Generation Threshold: 1 occurrence

Event Details:
Examples:
Event 684

Severity: CRITICAL

Event Summary: Watchdog Timer Expired

Event Class: System

Problem Description:
The Watchdog Timer checks for inactivity, or hung state, of the Cabinet Level Utilities (CLU) portion of the UGUY. During activity, the timer is continually reset. If the timer expires, it will automatically reset the CLU microprocessor. This will not affect running partitions.

Cause / Action:
Cause: CLU has been reset after a firmware update. Action: None. Cause: The CLU firmware has been reset by the MFG MP command RU. Action: None. Cause: Hardware or firmware failure on the UGUY. 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.

Automated Recovery: None

Event Generation Threshold: 1 occurrence

Event Details:
Examples:
Event 685

Severity: CRITICAL

Event Summary: Invalid checksum from EEPROM

Event Class: System

Problem Description:
An invalid checksum was received when reading the FRUID EEPROM for the device named in the chassis code. If this is a single error, the fault lies with the named FRU. If there are many INVALID_CKSM entries in the Event Log, there is probably a problem with the I2C bus.

Cause / Action:
Cause: Data corrupted in the named EEPROM. Action: If this is a single entry, replace the FRU. Cause: Problem with I2C bus. 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.

Automated Recovery: None

Event Generation Threshold: 1 occurrence

Event Details:
Examples:
Event 686

Severity: MAJOR_WARNING

Event Summary: System Backplane Power Board Fault

Event Class: System

Problem Description:
One or more of the System Backplane Power Boards is reporting a DC Fault through the System Backplane Local Power Monitor. The physical location of the failing power board is in the Data Field of the event.

Cause / Action:
Cause: A DC-DC converter on the named power board failed. 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.

Automated Recovery: None

Event Generation Threshold: 1 occurrence

Event Details:
Examples:
Event 687

Severity: MAJOR_WARNING

Event Summary: Read of EEPROM failed

Event Class: System

Problem Description:
An attempt to read the EEPROM (FRUID) on the IO Backplane Board failed.

Cause / Action:
Cause: The I2C controller on the Utilities Board (CLU section) is bad. This will be shown by many I2C failure codes in the Error Log. These codes should indentify entities on both the System Backplane and the Master IO Backplane. Action: Contact HP Support personnel to troubleshoot the problem. Cause: The cable from the Utilities Backplane to the Master IO Backplane is bad, or is not properly connected. Action: Check and reseat the Master IO Backplane Utilities cable. If no help, contact HP Support personnel to troubleshoot the problem. Cause: The I2C bus into the IO Backplane EEPROM is bad. Action: Could possibly be a bent pin on the Master IO Backplane Utilities cable connectors. Check the connectors at each end of the cable for bent or broken pins. If the connectors and cable are good, contact HP Support personnel to troubleshoot the problem.

Automated Recovery: None

Event Generation Threshold: 1 occurrence

Event Details:
Examples:
Event 688

Severity: MAJOR_WARNING

Event Summary: Read of EEPROM failed

Event Class: System

Problem Description:
An attempt to read the EEPROM (FRUID) on the IO Backplane Power Board failed.

Cause / Action:
Cause: The I2C controller on the Utilities Board (CLU section) is bad. This will be shown by many I2C failure codes in the Error Log. These codes should indentify entities on both the System Backplane and the Master IO Backplane. Action: Contact HP Support personnel to troubleshoot the problem. Cause: The cable from the Utilities Backplane to the Master IO Backplane is bad, or is not properly connected. Action: Check and reseat the Master IO Backplane Utilities cable. If no help, contact HP Support personnel to troubleshoot the problem. Cause: The I2C bus into the IO Power Board EEPROM is bad. Action: Could possibly be a bent pin on the Master IO Backplane Utilities cable connectors. Check the connectors at each end of the cable for bent or broken pins. Or, it could be a bent pin on the Master IO Backplane where the PCI Cardcage connects. If the MIOB, connectors and cable are good, contact HP Support personnel to troubleshoot the problem.

Automated Recovery: None

Event Generation Threshold: 1 occurrence

Event Details:
Examples:
Event 689

Severity: MAJOR_WARNING

Event Summary: Read of LPM Fault failed

Event Class: System

Problem Description:
An attempt to read the Local Power Monitor Fault register on the IO Backplane Power Board failed.

Cause / Action:
Cause: The I2C controller on the Utilities Board (CLU section) is bad. This will be shown by many I2C failure codes in the Error Log. These codes should indentify entities on both the System Backplane and the Master IO Backplane. Action: Contact HP Support personnel to troubleshoot the problem. Cause: The cable from the Utilities Backplane to the Master IO Backplane is bad, or is not properly connected. Action: Check and reseat the Master IO Backplane Utilities cable. If no help, contact HP Support personnel to troubleshoot the problem. Cause: The IO Backplane Power Board is bad. Action: Contact HP Support personnel to troubleshoot the problem. Cause: The I2C bus into the IO Power Board EEPROM is bad. Action: Could possibly be a bent pin on the Master IO Backplane Utilities cable connectors. Check the connectors at each end of the cable for bent or broken pins. Or, it could be a bent pin on the Master IO Backplane where the PCI Cardcage connects. If the MIOB, connectors ! and cable are good, contact HP Support personnel to troubleshoot the problem.

Automated Recovery: None

Event Generation Threshold: 1 occurrence

Event Details:
Examples:
Event 690

Severity: CRITICAL

Event Summary: IO Power Board Overtemperature

Event Class: System

Problem Description:
The Local Power Monitor of the named IO Chassis is reporting a Power Brick overtemperature condition.

Cause / Action:
Cause: The ambient air is too warm. Action: Check the Error Log for other Overtemp Warnings to confirm the environmental problem. Cause: The specified Power Brick, or the Local Power Monitor, has failed in such a manner as to report this error. Action: Contact HP Support personnel to troubleshoot the problem.

Automated Recovery: None

Event Generation Threshold: 1 occurrence

Event Details:
Examples:
Event 691

Severity: CRITICAL

Event Summary: IO Power Board Fault

Event Class: System

Problem Description:
The Local Power Monitor on the named IO Chassis has reported a power fault condition.

Cause / Action:
Cause: The named power brick on the named IO Chassis has failed. Action: Contact HP Support personnel to troubleshoot the problem. Cause: Input power has created some fault conditions. This will be evident by the presence of several chassis codes in the Error Log within the same time frame. Action: The Error 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.

Automated Recovery: None

Event Generation Threshold: 1 occurrence

Event Details:
Examples:
Event 692

Severity: MAJOR_WARNING

Event Summary: Voltage Margin on IO Power Board failed

Event Class: System

Problem Description:
The Local Power Monitor on the named IO Power Board failed to properly margin the power as commanded.

Cause / Action:
Cause: The IO Power Board LPM is not communicating with the CLU. Action: Some troubleshooting will be involved here. Is it the IO Power Board LPM, or the CLU. You'll have to check the Error Log for other entries related to either CLU communications problems or the IO Power Board LPM. If there are messages about other HIOPB_VOLT_MRGN_FAIL entries as well as SYS_BKP_VOLT_MRGN_FAIL, it is pointing to the CLU. Cause: The MP is not communicating with the CLU. Action: The MP bus (USB) is not functioning. There should be many entries in the Error 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.

Automated Recovery: None

Event Generation Threshold: 1 occurrence

Event Details:
Examples:
Event 693

Severity: MAJOR_WARNING

Event Summary: Failure to read data from a FRUID EEPROM

Event Class: System

Problem Description:
Either by command or as part of initialization, the data from a FRUID EEPROM failed a read command. This does not necessarily mean the FRU has failed, just that the FRUID cannot be read. The specific FRU Handle of the failing FRUID is embedded in the two uppermost bytes of the data field.

Cause / Action:
Cause: The CLU can't read the data from a FRUID EEPROM. Action: Contact HP Support personnel to troubleshoot the problem.

Automated Recovery: None

Event Generation Threshold: 1 occurrence

Event Details:
Examples:
Event 694

Severity: MAJOR_WARNING

Event Summary: Failure to read data from a SBCH FRUID EEPROM

Event Class: System

Problem Description:
Either by command or as part of initialization, the data from a FRUID EEPROM failed a read command. This does not necessarily mean the FRU has failed, just that the FRUID data cannot be read.

Cause / Action:
Cause: The CLU cannot read the data contained in the EEPROM on the SBCH board in the same cabinet. 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 and 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.

Automated Recovery: None

Event Generation Threshold: 1 occurrence

Event Details:
Examples:
Event 695

Severity: MAJOR_WARNING

Event Summary: Failure to read data from a UGUY FRUID EEPROM

Event Class: System

Problem Description:
Either by command or as part of initialization, the data from a FRUID EEPROM failed a read command. This does not necessarily mean the FRU has failed, just that the FRUID cannot be read.

Cause / Action:
Cause: Attempted access to read the UGUY FRUID EEPROM failed. 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.

Automated Recovery: None

Event Generation Threshold: 1 occurrence

Event Details:
Examples:
Event 696

Severity: MAJOR_WARNING

Event Summary: Read EEPROM failed

Event Class: System

Problem Description:
An attempt to read the EEPROM (FRUID) on the System Backplane failed

Cause / Action:
Cause: The I2C controller on the Utilities Board (CLU section) is bad. This will be shown by many I2C failure codes in the Error Log. These codes should indentify entities on both the System Backplane and the Master IO Backplane. Action: Replace the Utilities board (UGUY) following the Utilities Board Remove and Replace procedures. Cause: The 100 pin cable from the Utilities Backplane to the System Backplane is bad, or is not properly connected. Action: Check and reseat the System Backplane Utilities cable. If this does not resolve the issue, replace the System Backplane utilities cable following the Backplane Utilities Cable Remove and Replace procedures. Cause: The I2C bus into the System Backplane EEPROM is bad. Action: Could possibly be a bent pin on the System Backplane Utilities cable connectors. Check the connectors at each end of the cable for bent or broken pins. If the connectors and cable are good, replace the System Backplane following the System Backplane Re! move and Replace procedures. NOTE: System Backplane replacement is a major undertaking. Ensure all other possibilities have been explored before replacing the backplane. You should have WTEC approval before replacing the backplane.

Automated Recovery: None

Event Generation Threshold: 1 occurrence

Event Details:
Examples:
Event 697

Severity: MAJOR_WARNING

Event Summary: Read command on System Backplane I2C bus failed

Event Class: System

Problem Description:
A read command on the system backplane I2C bus failed.

Cause / Action:
Cause: The I2C controller on the Utilities Board (CLU section) is bad. This will be shown by many I2C failure codes in the Error Log. These codes should indentify entities on both the System Backplane and the Master IO Backplane. Action: Replace the Utilities board (UGUY) following the Utilities Board Remove and Replace procedures. Cause: The 100 pin cable from the Utilities Backplane to the System Backplane is bad, or is not properly connected. 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. Cause: The I2C bus into the System Backplane EEPROM is bad. Action: Could possibly be a bent pin on the System Backplane Utilities cable connectors. Check the connectors at each end of the cable for bent or broken pins. If the connectors and cable are good, replace the System Backplane following the System Backplane Remove and Replace procedures. NOTE: System Backplane replacement is a major undertaking. Ensure all other possibilities have been explored before replacing the backplane. You should have WTEC approval before replacing the backplane.

Automated Recovery: None

Event Generation Threshold: 1 occurrence

Event Details:
Examples:
Event 698

Severity: MAJOR_WARNING

Event Summary: Write command on System Backplane I2C bus failed

Event Class: System

Problem Description:
A write command on the system backplane I2C bus failed. The type of command that failed can be identified by the activity status field (last byte) of the encoded field. B = RC Cable Configuration Register write C = Backplane Voltage Margin Register write 9 = Flex circuit configuration register write

Cause / Action:
Cause: The I2C controller on the Utilities Board (CLU section) is bad. This will be shown by many I2C failure codes in the Error Log. These codes should indentify entities on both the System Backplane and the Master IO Backplane. Action: Replace the Utilities board (UGUY) following the Utilities Board Remove and Replace procedures. Cause: The 100 pin cable from the Utilities Backplane to the System Backplane is bad, or is not properly connected. 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. Cause: The I2C bus into the System Backplane EEPROM is bad. Action: Could possibly be a bent pin on the System Backplane Utilities cable connectors. Check the connectors at each end of the cable for bent or broken pins. If the connectors and cable are good, replace the System Backplane following the System Backplane Remove and Replace procedures. NOTE: System Backplane replacement is a major undertaking. Ensure all other possibilities have been explored before replacing the backplane. You should have WTEC approval before replacing the backplane.

Automated Recovery: None

Event Generation Threshold: 1 occurrence

Event Details:
Examples:
Event 699

Severity: CRITICAL

Event Summary: System Backplane Power Fault

Event Class: System

Problem Description:
The Local Power Monitor on the named System Backplane has detected a power fault. The failing Backplane Power Board status is read from the Backplane LPM I2C interface register and the value is placed in the data field of the event (bits 15-8).

Cause / Action:
Cause: While running normally, the CLU microcontroller detected a fault on the I2C Bus from the system Backplane LPM. 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.

Automated Recovery: None

Event Generation Threshold: 1 occurrence

Event Details:
Examples:
Event 700

Severity: SERIOUS

Event Summary: System Backplane voltage margin failed

Event Class: System

Problem Description:
Margining voltage to the System Backplane has failed.

Cause / Action:
Cause: The CLU was unable to write to the voltage margin register on the System backplane. Action: Try re-margining the system backplane and check connections. If many I2C access events are occurring inspect the UGUY utilities board.

Automated Recovery: None

Event Generation Threshold: 1 occurrence

Event Details:
Examples:
Event 701

Severity: MAJOR_WARNING

Event Summary: Failure to write data to FRUID EEPROM

Event Class: System

Problem Description:
An attempt to write data to the FRUID EEPROM by the MFG level MP command WF failed. The FRU handle of the failing FRUID is embedded in the two uppermost bytes of the data field.

Cause / Action:
Cause: The entity being written to is not powered up. Action: Power the entity with the PE command. Cause: The entity being written to has failed. Action: Replace the entity with the failed FRUID. Cause: The I2C bus has failed. Look for other entries in the Error Log to confirm this. If there are a lot of entries in this timeframe about I2C failures, analyze errors the errors to see if they are all within a cabinet, or the entire complex. Action: Each cabinet's Utilities Board (CLU and PM) is responsible for the query over I2C for the FRUID, LPM status, and other information. If there are other entries in the Error Log and they are all within a cabinet, replace the Utilities Board following the Utilities Board Remove and Replace Procedures.

Automated Recovery: None

Event Generation Threshold: 1 occurrence

Event Details:
Examples:
Event 707

Severity: CRITICAL

Event Summary: PDH Controller firmware version is not supported with this version of MP FW

Event Class: System

Problem Description:
The MP checked the FW revision of the PDHC identifyied in the physical location data field and discovered that it did not recognize the revision as one that it has been quailed with. This is an unsupported configuration.

Cause / Action:
Update PDHC or MP FW

Automated Recovery: None

Event Generation Threshold: 1 occurrence

Event Details:
Examples:
Event 708

Severity: SERIOUS

Event Summary: Power fault on cell board

Event Class: System

Problem Description:
The local Power Monitor is reporting a fault with the named Cell Power Board.

Cause / Action:
Cause: One or more of the DC to DC power converters on the Cell Power Board is displaying a fault condition. Action: Contact HP Support personnel to troubleshoot the problem.

Automated Recovery: None

Event Generation Threshold: 1 occurrence

Event Details:
Examples:
Event 710

Severity: MAJOR_WARNING

Event Summary: The ExecuteCommand function failed on a CPU.

Event Class: System

Problem Description:
ExecuteCommand issues commands that execute on remote CPUs via IPI interrupts. If the command failed to execute, this event is printed and the data field contains the status.

Cause / Action:
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.

Automated Recovery: None

Event Generation Threshold: 1 occurrence

Event Details:
Examples:
Event 711

Severity: MAJOR_WARNING

Event Summary: A remote CPU is not prepared to receive a command

Event Class: System

Problem Description:
A remote CPU is in a state where it cannot receive and execute a new command. The current status of the CPU is provided in the data field.

Cause / Action:
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.

Automated Recovery: None

Event Generation Threshold: 1 occurrence

Event Details:
Examples:
Event 712

Severity: SERIOUS

Event Summary: Boot is disabled because the cell type does not match the System FW ROM type.

Event Class: System

Problem Description:
The cell type (IPF or PA) does not match System FW type. The cell type is detected based on information stored in CPU modules' FRUID EEPROMs. The System FW type is determined based on data that is embedded in the System FW ROM image. This is checked each time Cell power transitions from off to on, and each time the System FW is updated. Following the detection of this mismatch, the Cell will not be allowed to boot until the problem has been resolved.

Cause / Action:
Cause(1): The System FW ROM in unprogrammed, or an invalid System FW ROM image is programmed in the System FW flash. Action(1): Update the System FW using Firmware Update from the MP. Cause(2): The Cell's installed CPU modules do not all have the same type, frequency and partition compatibility, so the Cell type cannot be accurately determined. In this case, a CPU_MOD_COMPAT_MISMATCH event should also be emitted. Action(2): Contact HP support personnel to troubleshoot the mismatched CPU module Cause(3): A CPU module's FRU data is programmed incorrectly. Action(3): If this is in manufacturing, re-program the FRU specific field of the FRU data for the CPU module. Otherwise, contact HP support personnel to troubleshoot the mismatched CPU module..
Cause(1): The System FW ROM in unprogrammed, or an invalid System FW ROM image is programmed in the System FW flash. Action(1): Update the System FW using Firmware Update from the MP. Cause(2): The Cell's installed CPU modules d! o not all have the same type, frequency and partition compatibility, so the Cell type cannot be accurately determined. In this case, a CPU_MOD_COMPAT_MISMATCH event should also be emitted. Action(2): Contact HP support personnel to troubleshoot the mismatched CPU module. Cause(3): A CPU module's FRU data is programmed incorrectly. Action(3): If this is in manufacturing, re-program the FRU specific field of the FRU data for the CPU module. Otherwise, contact HP support personnel to troubleshoot the mismatched CPU module.

Automated Recovery: None

Event Generation Threshold: 1 occurrence

Event Details:
Examples:
Event 713

Severity: MAJOR_WARNING

Event Summary: The PDHC has waited an abnormally long time for PDH bus access.

Event Class: System

Problem Description:
This event is emitted after the PDHC has waited longer than a maximum expected time for the PDH arbiter to grant it control of the PDH bus. The PDHC will continue waiting for control of the PDH bus until the arbiter grants it control, or the Cell is powered off using the MP's PE command. While waiting for the PDH bus, the PDHC will NOT perform its normal duties such as monitoring the Cell status, and passing messages from the system to the MP, and the PDHC heartbeat will not blink.

Cause / Action:
Cause (probable): A hardware fault is preventing the PDH arbiter from granting the PDHC control of the bus. Action: Contact HP support personnel to troubleshoot the cell board and/or PDH daughtercard. Cause: Bad connection on UGUY clock cable. Action: Check UGUY clock cable connection.
Cause (probable): A hardware fault is preventing the PDH arbiter from granting the PDHC control of the bus. Action: Contact HP support personnel to troubleshoot the Cell Board and/or PDH Daughtercard. Cause: Bad connection on UGUY clock cable. Action: Check UGUY clock cable connection.

Automated Recovery: None

Event Generation Threshold: 1 occurrence

Event Details:
Examples:
Event 714

Severity: MAJOR_WARNING

Event Summary: The PDHC has waited an abnormally long time to obtain the PDH semaphore.

Event Class: System

Problem Description:
This event is emitted after the PDHC has waited longer than a maximum expected time to obtain control of the PDH bus semaphore. The PDHC will continue waiting for control of the PDH bus semaphore until System FW relinquishes control of the semaphore, or the Cell is powered off using the MP's PE command. While waiting for the PDH bus semaphore, the PDHC will NOT perform its normal duties such as monitoring the Cell status, and passing messages from the system to the MP, and the PDHC heartbeat will not blink. The data field contains debug data that may be useful for developers. Data_byte[0] = last value read from PDHC's address for the microSemaphore register. Data_byte[1] = boolean indicator (1=set,0=not_set) of whether the PDHC's flag is set. Data_byte[2] = boolean indicator (1=set,0=not_set) of whether the System FW's flag is set.

Cause / Action:
Cause(1): System FW has control of the PDH bus semaphore, and has failed to relinquish control of it. Action(1): Update the System FW revision to the latest version of System FW using the Firmware Update Utility. Cause(2): A hardware fault is preventing the PDH bus semaphore from being taken/released as expected. Action(2): Contact HP support personnel to troubleshoot the Cell Board and/or PDH Daughtercard

Automated Recovery: None

Event Generation Threshold: 1 occurrence

Event Details:
Examples:
Event 715

Severity: MAJOR_WARNING

Event Summary: An error occurred while transmitting an IPMI message in the BMC2HOST direction.

Event Class: System

Problem Description:
This event indicates that an error occurred while transmitting an IPMI message in the BMC2HOST direction. The data field contains more detailed information about the source of the error. Data Bytes 0 & 1 form a 16-bit IPMI error indicator that has the following values and meanings: 1 - IPMI_HOST_BUSY_TIMEOUT - The PDHC could not put a message in the BMC2HOST hardware message queue for over 10 seconds, so the pending message(s) were dropped. 2 - IPMI_INVALID_MSG_SIZE - The MP sent an IPMI message response that has an embedded size indicator that is less than 4 bytes or greater than the size of the message data. The poorly formed message response will be dropped. 3 - IPMI_BMC2HOST_Q_FULL - The BMC2HOST message queue in the PDHC is full, so a message response from the MP has been dropped.

Cause / Action:
Cause(1): An unknown OS IPMI driver or Utilities FW bug has occurred. Action(1): Update PDHC FW, MP FW, System FW and the OS IPMI driver to the latest revisions. Cause(2): A hardware fault is preventing the BMC2HOST queue from working. Action(2): Contact HP support personnel to troubleshoot the PDH Daughtercard.

Automated Recovery: None

Event Generation Threshold: 1 occurrence

Event Details:
Examples:
Event 716

Severity: MAJOR_WARNING

Event Summary: EFI unable to read initial debug level from the BMC

Event Class: System

Problem Description:
EFI was unable to read the initial debug level from the BMC token. EFI will continue with an unknown value for the debug level. Data Field: Return status from internal EFI function.

Cause / Action:
Cause: BMC not functioning properly. Action: Reset the BMC. Contact your HP representative to check the BMC. Cause: SAL service to read tokens not functioning properly. Action: Reset the system. Clear NVM. Upgrade system firmware.

Automated Recovery: None

Event Generation Threshold: 1 occurrence

Event Details:
Examples:
Event 717

Severity: SERIOUS

Event Summary: A XBC port was unexpectedly found to not be landmined.

Event Class: System

Problem Description:
A XBC port was unexpectedly found to not be landmined. The data field consists of the XBC number (32:43) and the port number (44:55).

Cause / Action:
Cause: An XBC is indicating a port failure Action: Validate all of the cells connectivity to the PD Check the TOGO chips seating reset the system replace either cells/system backplane

Automated Recovery: None

Event Generation Threshold: 1 occurrence

Event Details:
Examples:
Event 718

Severity: CRITICAL

Event Summary: An invalid number of XBC ports were landmined in the system.

Event Class: System

Problem Description:
The number of landmined XBC ports was not within the allowable range. There is a minimum number of landmined ports because some ports are always unused. There is a maximum number of landmined ports because there is a limit to the number of broken links allowed in a system. The data field shows the number of landmined ports found

Cause / Action:
Check for hardware failures: crossbar chips, etc.

Automated Recovery: None

Event Generation Threshold: 1 occurrence

Event Details:
Examples:
Event 719

Severity: CRITICAL

Event Summary: The backplane was not recognized as one that contains fabric

Event Class: System

Problem Description:
Data field contains the backplane type found. During Intra SKD Routing, the backplane type detected was either a Medel backplane or was unrecognized. The backplane could therefore not be routed. This is a firmware sanity check. Data Field: system type

Cause / Action:
Cause: An unrecognized backplane is installed. Action: Contact HP Support Personnel to determine why the backplane was unrecognized.

Automated Recovery: None

Event Generation Threshold: 1 occurrence

Event Details:
Examples:
Event 720

Severity: MAJOR_WARNING

Event Summary: Writing the XIN Error Mask Register to zero failed

Event Class: System

Problem Description:
Prior to initializing the CC to XBC link, the XIN error mask should be zeroed out to prevent spurious errors from interfering with the link initialization. This write to zero out the error mask failed. Data Field: (cell << 56) | return status

Cause / Action:
CC Write Failure.
Contact HP Support personnel to analyze the fabric.

Automated Recovery: None

Event Generation Threshold: 1 occurrence

Event Details:
Examples:
Event 722

Severity: SERIOUS

Event Summary: Data read from the CC Primary Mode CSR

Event Class: System

Problem Description:
The Coherency Controller's (CC) XIN link did not initialize properly. The data field contains the data read from the CC Primary Error Mode CSR.

Cause / Action:
CC to XBC link init failure. Contact your HP service representative to check the CC to XBC link

Automated Recovery: None

Event Generation Threshold: 1 occurrence

Event Details:
Examples:
Event 723

Severity: SERIOUS

Event Summary: Dumping error info. Read status of the CC Error Mask Register

Event Class: System

Problem Description:
The Coherency Controller's (CC) XIN link did not initialize properly. The data field contains the return status from an attempted read of the CC Primary Error Mode CSR. (0 = SUCCESS)

Cause / Action:
CC to XBC link init failure. Contact your HP service representative to check the CC to XBC link

Automated Recovery: None

Event Generation Threshold: 1 occurrence

Event Details:
Examples:
Event 724

Severity: SERIOUS

Event Summary: Data read from the CC Error Mask CSR

Event Class: System

Problem Description:
The Coherency Controller's (CC) XIN link did not initialize properly. The data field contains the data read from the CC Error Mask CSR.

Cause / Action:
CC to XBC link init failure. Contact your HP service representative to check the CC to XBC link

Automated Recovery: None

Event Generation Threshold: 1 occurrence

Event Details:
Examples:
Event 725

Severity: MAJOR_WARNING

Event Summary: The link could not be crossed upon first attempt

Event Class: System

Problem Description:
The neighbor's port connected to the link being crossed is not routable. This was the first attempt to cross the link, PDC will now look for another link it can cross. DATA: (xbcNum << 32 ) | (port << 44)

Cause / Action:
The neighbor port is not routable. The port is either: not connected, landmined, in FE, or contains an SBE or LPE.
Contact HP Support personnel to analyze the fabric.

Automated Recovery: None

Event Generation Threshold: 1 occurrence

Event Details:
Examples:
Event 726

Severity: SERIOUS

Event Summary: Failed reading an XBC forward progress register

Event Class: System

Problem Description:
Fabric read error. Data field: (XBC number << 32 | return status)

Cause / Action:
Fabric access error
Contact HP Support personnel to analyze the fabric.

Automated Recovery: None

Event Generation Threshold: 1 occurrence

Event Details:
Examples:
Event 727

Severity: SERIOUS

Event Summary: Could not find an adjacent XBC due to broken fabric links

Event Class: System

Problem Description:
Too many crossbar links are broken. Cell cannot boot, halting. Data field: XBC number << 32

Cause / Action:
Possible crossbar failure
Contact HP Support personnel to analyze the crossbar.

Automated Recovery: None

Event Generation Threshold: 1 occurrence

Event Details:
Examples:
Event 728

Severity: MAJOR_WARNING

Event Summary: The run-time verification of a programming assumption has failed.

Event Class: System

Problem Description:
For debug purposes, many assumptions made by the PM developer(s) are checked at run-time. If this event log is seen, it will either indicate that the hardware is in a unknown state that is not handled by the PM, or that a programming bug has been found. For developer debug purposes, the data field describes where in the code that the error was detected. Data Bytes[0-1]: The line number within the source code file where the error was detected. Data Bytes[2-7]: The first 6 characters of the source code file name.

Cause / Action:
Cause: Hardware in unknown state, or programming bug found. Action: Upgrade PM firmware to latest revision. If already at current revision, replace UGUY board.

Automated Recovery: None

Event Generation Threshold: 1 occurrence

Event Details:
Examples:
Event 729

Severity: MAJOR_WARNING

Event Summary: An unknown error has been detected by the PDHC firmware.

Event Class: System

Problem Description:
An unknown error has been detected by the PM firmware. For developer debug purposes, the data field describes where in the code that the error was detected. Data Bytes[0-1]: The line number within the source code file where the error was detected. Data Bytes[2-7]: The first 6 characters of the source code file name.

Cause / Action:
Cause: Hardware in unknown state, or programming bug found. Action: Upgrade PM firmware to latest revision. If already at current revision, replace UGUY board.

Automated Recovery: None

Event Generation Threshold: 1 occurrence

Event Details:
Examples:
Event 731

Severity: MAJOR_WARNING

Event Summary: Testing of correctable errors injected from the CC has failed

Event Class: System

Problem Description:
Failed link testing to ensure that SBE and LPE errors are detected properly by the XBC. The XBC did not detect any errors. Data field indicates the return status: (1 = err detected, 0 = no err detected, -1 = XBC accesses failed)

Cause / Action:
Cause: Either the CC failed to inject the errors, the XBC failed to detect them, or PDC could not access the XBC CSR. Action: Check results from other cells connected to the same XBC. Check CC, Check XBC, Contact HP Support Personnel.

Automated Recovery: None

Event Generation Threshold: 1 occurrence

Event Details:
Examples:
Event 732

Severity: CRITICAL

Event Summary: A cabinet has been configured using an invalid cabinet number

Event Class: System

Problem Description:
The data field contains the cabinet number that is invalid

Cause / Action:
Re-configure cabinet to use a valid cabinet number

Automated Recovery: None

Event Generation Threshold: 1 occurrence

Event Details:
Examples:
Event 733

Severity: SERIOUS

Event Summary: Cells trying to join a PD are at incompatible firmware revisions

Event Class: System

Problem Description:
The cell indicated in the data field is at a different firmware revision than the reporting cell. This is determined by evaluating the checksums of the 2 rom images.

Cause / Action:
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.

Automated Recovery: None

Event Generation Threshold: 1 occurrence

Event Details:
Examples:
Event 734

Severity: MAJOR_WARNING

Event Summary: An attempt to write to a device on the PM's I2C bus has failed.

Event Class: System

Problem Description:
An attempt to write to a device on the PM's I2C bus has failed. The Data field contains information that can identify the exact device that has failed. Refer to the UGUY ERS for a mapping of I2C device addresses to devices. Data Bytes[0-1]: Reserved Data Bytes[2-3]: I2C Device Address Data Bytes[4-5]: Starting Word Address Data Bytes[6-7]: Size of attempted access (in bytes).

Cause / Action:
Cause: A hardware error has occurred. Action: Replace the UGUY board.

Automated Recovery: None

Event Generation Threshold: 1 occurrence

Event Details:
Examples:
Event 735

Severity: MAJOR_WARNING

Event Summary: An attempt to read from a device on the PM's I2C bus has failed.

Event Class: System

Problem Description:
An attempt to read from a device on the PM's I2C bus has failed. The Data field contains information that can identify the exact device that has failed. Refer to the UGUY ERS for a mapping of I2C device addresses to devices. Data Bytes[0-1]: Reserved Data Bytes[2-3]: I2C Device Address Data Bytes[4-5]: Starting Word Address Data Bytes[6-7]: Size of attempted access (in bytes).

Cause / Action:
Cause: A hardware error has occurred. Action: Replace the UGUY board.

Automated Recovery: None

Event Generation Threshold: 1 occurrence

Event Details:
Examples:
Event 736

Severity: MAJOR_WARNING

Event Summary: An error was encountered updating the cell info structure in ICM

Event Class: System

Problem Description:
An error was encountered trying to obtain the data required for the cell information structure in ICM. The data field is an ASCII message that indicates the information that was not found.

Cause / Action:
This should not happen. Contact engineering to diagnose the problem.

Automated Recovery: None

Event Generation Threshold: 1 occurrence

Event Details:
Examples:
Event 737

Severity: MAJOR_WARNING

Event Summary: An error was encountered pointing the slave cell consoles to the diva

Event Class: System

Problem Description:
An error was encountered establishing the slave cells use of the diva console.

Cause / Action:
A CPU on the slave cell could not process an interrupt in time or establish the diva console.

Automated Recovery: None

Event Generation Threshold: 1 occurrence

Event Details:
Examples:
Event 738

Severity: SERIOUS

Event Summary: An error was encountered trying to relocate a slave cells registry

Event Class: System

Problem Description:
An error was encountered trying to relocate the registry on a slave cell to point to the core cells main memory structures.

Cause / Action:
There could be a PD rendezvous error or a processor on the slave cell failed to respond to an interrupt in time.

Automated Recovery: None

Event Generation Threshold: 1 occurrence

Event Details:
Examples:
Event 740

Severity: CRITICAL

Event Summary: Machine check type could not be determined.

Event Class: System

Problem Description:
The Reporting Entity CPU experienced a trap that has caused an asynchronous branch to the machine check handler, but CPU logs do not indicate that an HPMC, LPMC or TOC has occurred. The data field will contain the CPU Check Summary Word. This Check Summary Word is described in the return value description for CpuProcessMachineCheck in PA-8800 CPU Library Application Programming Interface Reference.

Cause / Action:
Save event list and Processor HPMC PIM for analysis by lab.

Automated Recovery: None

Event Generation Threshold: 1 occurrence

Event Details:
Examples:
Event 741

Severity: SERIOUS

Event Summary: Failure to identify a core cell during Global MCA.

Event Class: System

Problem Description:
Not able to find a core cell in the PD during a global MCA error processing.

Cause / Action:
This will lead to a system reset.

Automated Recovery: None

Event Generation Threshold: 1 occurrence

Event Details:
Examples:
Event 742

Severity: MAJOR_WARNING

Event Summary: Unexpected fabric firmware error

Event Class: System

Problem Description:
An unexpected error occurred while initializing the fabric. The firmware is not able to analyze this error. Clues to the cause of this error may be found in the IPMI forward progress log (FPL) either shortly before or after this log entry occurred. The FPL is available from the management processor using the "sl" command. HP-UX also saves these logs in the /var/stm/logs/os directory, and they can be viewed using the slview utility. For more details on the slview utility, refer to the slview web page at http://docs.hp.com/hpux/onlinedocs/diag/st/st_event_viewer.htm

Cause / Action:
An unanticipated error occurred. Contact HP Support personnel to analyze the IPMI FPL log.

Automated Recovery: None

Event Generation Threshold: 1 occurrence

Event Details:
Examples:
Event 743

Severity: CRITICAL

Event Summary: Internal firmware programming error in the PMI handler.

Event Class: System

Problem Description:
An internal firmware error was encountered. This is usually caused by a bad parameter passed to a function, corrupt memory, corrupt malloc tables or something similar. The data field contains the IP address of the function that encountered the error.

Cause / Action:
Report the IP to the firmware team. Reset the system. This cannot be worked around in the field.

Automated Recovery: None

Event Generation Threshold: 1 occurrence

Event Details:
Examples:
Event 744

Severity: SERIOUS

Event Summary: During a Cell On Line Add inconsistent number of cells discovered

Event Class: System

Problem Description:
During the on line addition of a cell the partition adding the cell has determined inconsistent data as to which cell is being added. The cell addition will be aborted and the partition will resume execution without the new cell.

Cause / Action:
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.

Automated Recovery: None

Event Generation Threshold: 1 occurrence

Event Details:
Examples:
Event 745

Severity: MAJOR_WARNING

Event Summary: Error reading source cell port on XBC during data traversability test

Event Class: System

Problem Description:
An error occurred while reading the routing from the source cell's port on the source XBC. Data Field: (source cell << 56 | source XBC << 32)

Cause / Action:
A read error most likely occurred. Look for preceding chassis codes to determine exact cause.

Automated Recovery: None

Event Generation Threshold: 1 occurrence

Event Details:
Examples:
Event 753

Severity: MAJOR_WARNING

Event Summary: CPUs of different maximum core frequencies are installed

Event Class: System

Problem Description:
CPU's of mixed maximum core frequencies are installed

Cause / Action:
Cause: CPU's of mixed maximum core frequencies are installed. Action: If operating at the slowest of the maximum core frequency of installed CPU's is acceptable, no action is necessary. If not, replace the slower core frequency CPU's to match the faster CPU's. This will enable all CPU's to work at their maximum frequency.

Automated Recovery: None

Event Generation Threshold: 1 occurrence

Event Details:
Examples:
Event 754

Severity: CRITICAL

Event Summary: The RVL CC-Togo link initialization workaround (PS221) failed

Event Class: System

Problem Description:
The Concorde-Togo link initialization is having an intermittent failure. The data field contains the number of initialization sequences that failed before being successful.

Cause / Action:
Cause: The link initialization failed at least once and then subsequently was successful.

Automated Recovery: None

Event Generation Threshold: 1 occurrence

Event Details:
Examples:
Event 756

Severity: SERIOUS

Event Summary: Fabric Discovery could not initialize the local cell's XBC link

Event Class: System

Problem Description:
Fabric Discovery's final attempt to initialize the local cell's CC to Crossbar Chip (XBC) link has failed. This cell cannot talk to the fabric. Data: link init state bit read from the CC Link State register

Cause / Action:
Cause: CC to XBC link init failure. Action: check CC, XBC, reset cell, reset backplane

Automated Recovery: None

Event Generation Threshold: 1 occurrence

Event Details:
Examples:
Event 760

Severity: CRITICAL

Event Summary: Internal firmware programming error

Event Class: System

Problem Description:
An internal firmware error was encountered. This is usually caused by a bad parameter passed to a function, corrupt memory, corrupt malloc tables or something similar. The data field contains the physical address that failed mapping to a virtual address

Cause / Action:
Report the IP to the firmware team. Reset the system. This cannot be worked around in the field.

Automated Recovery: None

Event Generation Threshold: 1 occurrence

Event Details:
Examples:
Event 771

Severity: SERIOUS

Event Summary: Error writing the XIN init disable register.

Event Class: System

Problem Description:
Failure while writing the XBC CSR containing the link status

Cause / Action:
Check XBC, CC, backplane

Automated Recovery: None

Event Generation Threshold: 1 occurrence

Event Details:
Examples:
Event 772

Severity: SERIOUS

Event Summary: Error reading the XIN init state register.

Event Class: System

Problem Description:
Failure while reading the XBC CSR containing the link status

Cause / Action:
Check XBC, CC, backplane

Automated Recovery: None

Event Generation Threshold: 1 occurrence

Event Details:
Examples:
Event 773

Severity: SERIOUS

Event Summary: intermittent failure while retrying the CC to XBC link init

Event Class: System

Problem Description:
Fabric Discovery's attempt to initialize the local cell's CC to XBC link has failed. The link initialization sequence has an intermittent problem.

Cause / Action:
contact your HP service representative

Automated Recovery: None

Event Generation Threshold: 1 occurrence

Event Details:
Examples:
Event 774

Severity: MAJOR_WARNING

Event Summary: Initialization of a PCI node in the firmware device tree failed

Event Class: System

Problem Description:
error code

Cause / Action:
Cause: A firmware error setting up data storage to allow PCI bus bridge processing to occur. Action: Correct any previous errors reset the system clear NVM and reset the system Update to the latest recipe Replace the cell board.

Automated Recovery: None

Event Generation Threshold: 1 occurrence

Event Details:
Examples:
Event 775

Severity: SERIOUS

Event Summary: An error was encountered while scanning the PCI bus.

Event Class: System

Problem Description:
error code

Cause / Action:
Cause: A firmware error setting up data storage to allow PCI bus scanning to occur. Action: Correct any previous errors reset the system clear NVM and reset the system Update to the latest recipe Replace the cell board.

Automated Recovery: None

Event Generation Threshold: 1 occurrence

Event Details:
Examples:
Event 776

Severity: MAJOR_WARNING

Event Summary: An error was encountered initializing the PCI bridge

Event Class: System

Problem Description:
error code

Cause / Action:
Cause: A firmware error setting up data storage to allow PCI bus bridge processing to occur. Action: Correct any previous errors reset the system clear NVM and reset the system Update to the latest recipe Replace the cell board.

Automated Recovery: None

Event Generation Threshold: 1 occurrence

Event Details:
Examples:
Event 777

Severity: MAJOR_WARNING

Event Summary: An error was encountered initializing the PCI IO map.

Event Class: System

Problem Description:
pfa

Cause / Action:
Cause: PCI requested I/O port size larger than system can handle Action: Correct any previous errors Remove cards that are requesting too much memory space or move a card to a dual rope slot (PCI slots 1-7).

Automated Recovery: None

Event Generation Threshold: 1 occurrence

Event Details:
Examples:
Event 778

Severity: MAJOR_WARNING

Event Summary: An error was encountered creating the PCI MMIO map

Event Class: System

Problem Description:
pfa

Cause / Action:
Cause: PCI requested memory map size larger than system can handle Action: Correct any previous errors Remove cards that are requesting too much memory space or move a card to a dual rope slot (PCI slots 1-7).

Automated Recovery: None

Event Generation Threshold: 1 occurrence

Event Details:
Examples:
Event 779

Severity: SERIOUS

Event Summary: There was an error initializing the SBA node

Event Class: System

Problem Description:
error code

Cause / Action:
Cause: An error was while initializing the SBA firmware structures Action: Correct any previous errors Invalidate NVM and reset replace the cell board

Automated Recovery: None

Event Generation Threshold: 1 occurrence

Event Details:
Examples:
Event 780

Severity: SERIOUS

Event Summary: There was an error discovering the SBA

Event Class: System

Problem Description:
error code

Cause / Action:
Cause: An error was discovered with the SBA during discovery Action: Correct any previous errors Replace the I/O backplane

Automated Recovery: None

Event Generation Threshold: 1 occurrence

Event Details:
Examples:
Event 781

Severity: SERIOUS

Event Summary: An error was encountered while resetting the SBA

Event Class: System

Problem Description:
error code

Cause / Action:
Cause: An error was detected while resetting the ropes Action: replace the I/O backplane

Automated Recovery: None

Event Generation Threshold: 1 occurrence

Event Details:
Examples:
Event 782

Severity: MAJOR_WARNING

Event Summary: There was an error initializing the IO link

Event Class: System

Problem Description:
An error was detected in the link between the CC and the I/O controller.

Cause / Action:
Cause: Unable to establish the link between the CC and IOC. Action: Validate power to the I/O chassis Reset the system A/C power cycle Replace the I/O backplane, cell, and system backplane to resolve the issue.

Automated Recovery: None

Event Generation Threshold: 1 occurrence

Event Details:
Examples:
Event 783

Severity: MAJOR_WARNING

Event Summary: There is a problem initializing the REO cable

Event Class: System

Problem Description:
cable status

Cause / Action:
Check the REO cable connection

Automated Recovery: None

Event Generation Threshold: 1 occurrence

Event Details:
Examples:
Event 784

Severity: SERIOUS

Event Summary: The IO chassis discovered was powered off

Event Class: System

Problem Description:
Identified the cell number that is connected to the chassis.

Cause / Action:
No action required.

Automated Recovery: None

Event Generation Threshold: 1 occurrence

Event Details:
Examples:
Event 785

Severity: MAJOR_WARNING

Event Summary: There was an error initializing the LBA

Event Class: System

Problem Description:
error code

Cause / Action:
Cause: Error initializing the LBA node and services Action: Validate that there is not another error causing this error invalidate NVM and reset or replace the cell board

Automated Recovery: None

Event Generation Threshold: 1 occurrence

Event Details:
Examples:
Event 786

Severity: SERIOUS

Event Summary: There was an error querying the LBA width

Event Class: System

Problem Description:
error code

Cause / Action:
Cause: Error while writing the LBA phase data Action: Replace the I/O backplane

Automated Recovery: None

Event Generation Threshold: 1 occurrence

Event Details:
Examples:
Event 787

Severity: MAJOR_WARNING

Event Summary: There was an error with the LBA phase

Event Class: System

Problem Description:
error code

Cause / Action:
Cause: Error while writing the LBA phase data Action: Replace the I/O backplane

Automated Recovery: None

Event Generation Threshold: 1 occurrence

Event Details:
Examples:
Event 788

Severity: MAJOR_WARNING

Event Summary: There was an error clearing the LBA

Event Class: System

Problem Description:
error code

Cause / Action:
Cause: Unable to clear an error in the LBA Action: Check other events for the error being generated replace either the PCI card or the I/O backplane

Automated Recovery: None

Event Generation Threshold: 1 occurrence

Event Details:
Examples:
Event 789

Severity: SERIOUS

Event Summary: There was an error with the LBA log

Event Class: System

Problem Description:
error code

Cause / Action:
Cause: Error log is corrupt Action: Clear errors and continue

Automated Recovery: None

Event Generation Threshold: 1 occurrence

Event Details:
Examples:
Event 790

Severity: SERIOUS

Event Summary: There was an error discovering the LBA

Event Class: System

Problem Description:
error code

Cause / Action:
Cause: The wrong backplane type was detected Action: replace I/O backplane

Automated Recovery: None

Event Generation Threshold: 1 occurrence

Event Details:
Examples:
Event 791

Severity: MAJOR_WARNING

Event Summary: There was an error configuring the LBA

Event Class: System

Problem Description:
error code

Cause / Action:
Cause: Unable to configure the LBA Action: replace I/O backplane

Automated Recovery: None

Event Generation Threshold: 1 occurrence

Event Details:
Examples:
Event 792

Severity: SERIOUS

Event Summary: There was an error scanning the PCI bus

Event Class: System

Problem Description:
An error was encountered while attempting to scan the PCI bus

Cause / Action:
Cause: ld not scan the card in a populated slot. Typically caused by an improperly installed or faulty PCI card.
Action: Reseat or replace the faulty card.

Automated Recovery: None

Event Generation Threshold: 1 occurrence

Event Details:
Examples:
Event 793

Severity: SERIOUS

Event Summary: There was an error configuring PCI space through the LBA

Event Class: System

Problem Description:
error code

Cause / Action:
Cause: Unable to obtain semaphore Action: reset Update to latest recipe

Automated Recovery: None

Event Generation Threshold: 1 occurrence

Event Details:
Examples:
Event 806

Severity: SERIOUS

Event Summary: Firmware was unable to find a suitable block of main memory to relocate ROM

Event Class: System

Problem Description:
IA Firmware tries to find a main memory block large enough meeting alignment requirements.

Cause / Action:
Probably caused by lots of PDT entries, or no main memory present.

Automated Recovery: None

Event Generation Threshold: 1 occurrence

Event Details:
Examples:
Event 808

Severity: SERIOUS

Event Summary: The Options service received an NVRAM allocation error.

Event Class: System

Problem Description:
The Options service received an error when attempting to allocate an NVRAM storage block. Either an error was returned from the call, or the call returned successfully yet an invalid address was returned.

Cause / Action:
Invalidate NVRAM and reset.

Automated Recovery: None

Event Generation Threshold: 1 occurrence

Event Details:
Examples:
Event 810

Severity: MAJOR_WARNING

Event Summary: SAL errlog access timeout

Event Class: System

Problem Description:
Access to SAL error log procedure timed out because the log facility was busy processing a request from another CPU. Data field indicates the SAL procedure ID.

Cause / Action:
Firmware is taking too long to process requests.

Automated Recovery: None

Event Generation Threshold: 1 occurrence

Event Details:
Examples:
Event 816

Severity: MAJOR_WARNING

Event Summary: The echelon given in the data field is not fully populated.

Event Class: System

Problem Description:
One or more dimms are missing from the echelon given in the data field. The dimms may not be installed or firmware was not able to detect the dimms.

Cause / Action:
cause - the specified echelon is not fully populated and is not usable action - add or replace dimms in the specified echelon

Automated Recovery: None

Event Generation Threshold: 1 occurrence

Event Details:
Examples:
Event 817

Severity: MAJOR_WARNING

Event Summary: Attempted to read the port state from an illegal port number

Event Class: System

Problem Description:
The code that reads the port state (landmine vs. healthy) expects a XBC internal port number, it received bogus data. The port state cannot be read. Data Field: (port << 44) | (xbc num << 32)

Cause / Action:
An invalid port number has been provided. The port number will be converted to an internal port and processing should continue.
Contact HP Support personnel to analyze the fabric.

Automated Recovery: None

Event Generation Threshold: 1 occurrence

Event Details:
Examples:
Event 818

Severity: MAJOR_WARNING

Event Summary: Attempted to write the port state for an illegal port

Event Class: System

Problem Description:
The code that writes the port state (landmine vs. healthy) expects a XBC internal port number, it received bogus data. The port state cannot be read. Data Field: (port << 44) | (xbc num << 32)

Cause / Action:
An invalid port number has been provided. The port number will be converted to an internal port and processing should continue.
Contact HP Support personnel to analyze the fabric.

Automated Recovery: None

Event Generation Threshold: 1 occurrence

Event Details:
Examples:
Event 822

Severity: SERIOUS

Event Summary: System firmware was unable to default the complex profile

Event Class: System

Problem Description:
System firmware was unable to default the complex profile

Cause / Action:
Needed information could not be obtained. Reset the MP.

Automated Recovery: None

Event Generation Threshold: 1 occurrence

Event Details:
Examples:
Event 824

Severity: MAJOR_WARNING

Event Summary: Means that the error log space in the Nvram has not been allocated.

Event Class: System

Problem Description:
This chassis code shows that the error log space in the NVRAM has not been allocated for the current error event. This will be emitted out whenever a error section is attempted to be logged without allocation of log space in NVRAM

Cause / Action:
This happens because of the NVRAM is full with unconsumed error logs. Clear the error logs.

Automated Recovery: None

Event Generation Threshold: 1 occurrence

Event Details:
Examples:
Event 825

Severity: MAJOR_WARNING

Event Summary: This indicates the maximum number of logs for the event.

Event Class: System

Problem Description:
This indicates that the error logs for a particular event type have reached the maximum allowed to be stored in the NVRAM. The event type is indicated in the data field.

Cause / Action:
This shouldn't be occur. But in case it does than clear the error logs of this event type from the nvram.

Automated Recovery: None

Event Generation Threshold: 1 occurrence

Event Details:
Examples:
Event 826

Severity: MAJOR_WARNING

Event Summary: On Line Delete operation was begun but firmware couldn't find a deletable cell

Event Class: System

Problem Description:
System firmware has been invoked to perform a cell delete operation but no cell in the system appears to be ready for deletion.

Cause / Action:
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.

Automated Recovery: None

Event Generation Threshold: 1 occurrence

Event Details:
Examples:
Event 827

Severity: CRITICAL

Event Summary: The bulk power system is above its current capacity.

Event Class: System

Problem Description:
The bulk power supply is overcurrent

Cause / Action:
N/A

Automated Recovery: None

Event Generation Threshold: 1 occurrence

Event Details:
Examples:
Event 828

Severity: MAJOR_WARNING

Event Summary: The bulk specified is warning of a potential thermal problem.

Event Class: System

Problem Description:
Data: Bulk location.

Cause / Action:
The bulk power supply is warning of an overtemperature condition

Automated Recovery: None

Event Generation Threshold: 1 occurrence

Event Details:
Examples:
Event 829

Severity: SERIOUS

Event Summary: Malloc failed while trying to process and ERM

Event Class: System

Problem Description:
Error Response Mode code attempted a malloc of heap space that failed.

Cause / Action:
Heap space is completely used or corrupt. Contact Product Engineering.

Automated Recovery: None

Event Generation Threshold: 1 occurrence

Event Details:
Examples:
Event 830

Severity: MAJOR_WARNING

Event Summary: Dimm at physical location in data field is not supported on this platform.

Event Class: System

Problem Description:
The dimm in the physical location given by the data field is not supported on this platform. The dimm may not be supported by the hardware, or the dimm may not have been properly qualified for this platform.

Cause / Action:
Cause: Unsupported dimm in specified slot Action: Replace dimm with supported dimm.

Automated Recovery: None

Event Generation Threshold: 1 occurrence

Event Details:
Examples:
Event 831

Severity: SERIOUS

Event Summary: The OPTIONS component received a memory allocation error.

Event Class: System

Problem Description:
The OPTIONS component was unable to allocate NVRAM memory in order to store a non-volatile variable. The storage area for NVRAM options may be full, or there may be undetected corruption.

Cause / Action:
Invalidate NVRAM and reset.

Automated Recovery: None

Event Generation Threshold: 1 occurrence

Event Details:
Examples:
Event 832

Severity: MAJOR_WARNING

Event Summary: A dimm or CPU has is deconfigured or failed testing

Event Class: System

Problem Description:
A dimm or CPU has failed and is not operational for the system. This event is emitted prior to determining if the cell should be integrated into the Partition.

Cause / Action:
A deconfigured dimm or cpu has been detected. Examine earlier events to isolate the problem.

Automated Recovery: None

Event Generation Threshold: 1 occurrence

Event Details:
Examples:
Event 833

Severity: SERIOUS

Event Summary: The cell will not join the PD

Event Class: System

Problem Description:
A cpu or dimm error has been detected, and the Complex Profile, Cell Integration Table, Cell integration policy says to not integrate the cell into the PD.

Cause / Action:
Broken hardware was detected and the cell integration policy combined to cause the cell to not join the PD. Fix the broken hardware or change the policy using parmgr.

Automated Recovery: None

Event Generation Threshold: 1 occurrence

Event Details:
Examples:
Event 834

Severity: MAJOR_WARNING

Event Summary: The error context in NVM was corrupt

Event Class: System

Problem Description:
The IO error context is corrupt. This will impair IO error reporting.

Cause / Action:
NVM is corrupted.
Check for other errors in the system first. Invalidate NVM and retry boot. Get the latest firmware release.

Automated Recovery: None

Event Generation Threshold: 1 occurrence

Event Details:
Examples:
Event 835

Severity: MAJOR_WARNING

Event Summary: A rope went fatal from the SBA

Event Class: System

Problem Description:
A rope went fatal from the SBA to the LBA. If all the ropes go fatal the IO subsystem is dead. Any I/O below the rope will not be accessible. The data field gives the number of the rope that went fatal.

Cause / Action:
Mainly a hardware problem causes this problem.
Replace I/O chassis.

Automated Recovery: None

Event Generation Threshold: 1 occurrence

Event Details:
Examples:
Event 836

Severity: MAJOR_WARNING

Event Summary: One of the rope units in the SBA is dead.

Event Class: System

Problem Description:
One of the rope units in the SBA failed. If all of the rope units fail, then IO will not be available on this cell.

Cause / Action:
Usually hardware.

Automated Recovery: None

Event Generation Threshold: 1 occurrence

Event Details:
Examples:
Event 837

Severity: SERIOUS

Event Summary: Firmware encountered a problem trying to initialize

Event Class: System

Problem Description:
System firmware encountered an error while trying to perform an operation during system initialization. This event ID will always be emitted before an event ID that describes the status of the operation that failed.

Cause / Action:
Examine the related event that failed and correct that problem.

Automated Recovery: None

Event Generation Threshold: 1 occurrence

Event Details:
Examples:
Event 838

Severity: MAJOR_WARNING

Event Summary: This means that all the cpus in the cell did not show up.

Event Class: System

Problem Description:
This means that all the cpus in the cell did not show up.

Cause / Action:
This will result in the cell stepping independently to collect its logs and restting itself.

Automated Recovery: None

Event Generation Threshold: 1 occurrence

Event Details:
Examples:
Event 839

Severity: MAJOR_WARNING

Event Summary: This means that all the cells did not rendezvous during the PD rendezvous.

Event Class: System

Problem Description:
This means that all the cells did not rendezvous during the PD rendezvous. The data part will contain the Expected data and the actual mask of the cells that rendezvoused.

Cause / Action:
The cells will reset themselves.

Automated Recovery: None

Event Generation Threshold: 1 occurrence

Event Details:
Examples:
Event 840

Severity: MAJOR_WARNING

Event Summary: The FW tree sanity check failed during the MCA error processing.

Event Class: System

Problem Description:
The FW tree sanity check failed during the MCA error processing.

Cause / Action:
The cells will independently log errors and reset.

Automated Recovery: None

Event Generation Threshold: 1 occurrence

Event Details:
Examples:
Event 841

Severity: MAJOR_WARNING

Event Summary: This means that the registry sanity check failed during MCA error handling.

Event Class: System

Problem Description:
This means that the registry sanity check failed during MCA error handling.

Cause / Action:
The cells will independently log errors and reset.

Automated Recovery: None

Event Generation Threshold: 1 occurrence

Event Details:
Examples:
Event 842

Severity: MAJOR_WARNING

Event Summary: This means that MCA occurred while OS_MCA was performing error recovery.

Event Class: System

Problem Description:
This means that MCA occurred while OS_MCA was performing error recovery.

Cause / Action:
The cells will log information and reset.

Automated Recovery: None

Event Generation Threshold: 1 occurrence

Event Details:
Examples:
Event 843

Severity: MAJOR_WARNING

Event Summary: One of the BT errors occurred that results in abandoning memory dump.

Event Class: System

Problem Description:
This means that memory dump will be abandoned due to work-around for CN2272. This happens when one of the Blocking timeout in the Processor input block of the concorde occurs.

Cause / Action:
Cause: A machine check has occurred and cells have not rendezvoused. Action: Cells will reset themselves.

Automated Recovery: None

Event Generation Threshold: 1 occurrence

Event Details:
Examples:
Event 844

Severity: MAJOR_WARNING

Event Summary: The firmware tree is not complete and hence there will be no PD rendezvous.

Event Class: System

Problem Description:
The firmware tree is not complete and hence there will be no PD rendezvous.

Cause / Action:
The cell will log errors and reset

Automated Recovery: None

Event Generation Threshold: 1 occurrence

Event Details:
Examples:
Event 845

Severity: SERIOUS

Event Summary: ACPI configuration mismatch across cells in the partition

Event Class: System

Problem Description:
The firmware parameter that defines the ACPI configuration is inconsistent in at least one of the cells in the partition.

Cause / Action:
Set the ACPI configuration parameter again to ensure that all cells have a consistent value.

Automated Recovery: None

Event Generation Threshold: 1 occurrence

Event Details:
Examples:
Event 846

Severity: SERIOUS

Event Summary: Failed clearing of the XIN_ERR_ORDER_STATUS CSR

Event Class: System

Problem Description:
Writing the XIN_ERR_ORDER_STATUS register of the CC failed. This is some sort of a hardware failure. Data Field: return status

Cause / Action:
Failure to access the register or the write did not work.
Contact HP Support personnel to check the CC.

Automated Recovery: None

Event Generation Threshold: 1 occurrence

Event Details:
Examples:
Event 847

Severity: MAJOR_WARNING

Event Summary: Invalid Real Time Clock Cleared

Event Class: System

Problem Description:
The Real Time Clock is invalid. System Firmware is clearing the invalid state and setting it back to default.

Cause / Action:
Cause: Corrupted RTC contents Action: Replace battery on System Board.

Automated Recovery: None

Event Generation Threshold: 1 occurrence

Event Details:
Examples:
Event 848

Severity: MAJOR_WARNING

Event Summary: Unexpected fabric firmware error

Event Class: System

Problem Description:
An unexpected error occurred while initializing the fabric. The firmware is not able to analyze this error. Clues to the cause of this error may be found in the IPMI forward progress log (FPL) either shortly before or after this log entry occurred. The FPL is available from the management processor using the "sl" command. HP-UX also saves these logs in the /var/stm/logs/os directory, and they can be viewed using the slview utility. For more details on the slview utility, refer to the slview web page at http://docs.hp.com/hpux/onlinedocs/diag/st/st_event_viewer.htm

Cause / Action:
An unanticipated error occurred. Contact HP Support personnel to analyze the IPMI FPL log.

Automated Recovery: None

Event Generation Threshold: 1 occurrence

Event Details:
Examples:
Event 849

Severity: MAJOR_WARNING

Event Summary: Invalid data read from a CPU module's Processor Information ROM.

Event Class: System

Problem Description:
A value read by the PDHC from a CPU module's Processor Information ROM was not within acceptable limits.

Cause / Action:
Cause (probable): The CPU module's Processor Information ROM is unprogrammed. Action: Contact HP support personnel to troubleshoot the CPU module pointed to by the physical location portion of this event. Cause: The CPU module's Processor Information ROM contains invalid data. Action: Contact HP support personnel to troubleshoot the CPU module pointed to by the physical location portion of this event.

Automated Recovery: None

Event Generation Threshold: 1 occurrence

Event Details:
Examples:
Event 851

Severity: MAJOR_WARNING

Event Summary: Option block in nvram has a checksum error

Event Class: System

Problem Description:
The overhead structure of the OPTIONS block in NVRAM has a checksum error.

Cause / Action:
Clear NVRAM.

Automated Recovery: None

Event Generation Threshold: 1 occurrence

Event Details:
Examples:
Event 852

Severity: MAJOR_WARNING

Event Summary: CC to CC link did not initialize on the local cell

Event Class: System

Problem Description:
During a cell OLA, the link on the local cell failed to initialize. Data Field: (my cell << 32) | XIN Link State

Cause / Action:
link failure between the XBC and the CC
Check CC.

Automated Recovery: None

Event Generation Threshold: 1 occurrence

Event Details:
Examples:
Event 853

Severity: MAJOR_WARNING

Event Summary: Failed to write the CC link disable register

Event Class: System

Problem Description:
An attempt to disable the fabric link failed because writing the CC CSR failed. Data Field: (cell << 56) | return status

Cause / Action:
Fabric Access Failure.
Contact HP Support personnel to analyze the fabric.

Automated Recovery: None

Event Generation Threshold: 1 occurrence

Event Details:
Examples:
Event 854

Severity: MAJOR_WARNING

Event Summary: An unknown backplane type was found

Event Class: System

Problem Description:
Could not determine the system type in order to write the appropriate error mask for the fabric link. Data Field: system type

Cause / Action:
CSR Read/Write error
Contact HP Support personnel to analyze the fabric.

Automated Recovery: None

Event Generation Threshold: 1 occurrence

Event Details:
Examples:
Event 855

Severity: MAJOR_WARNING

Event Summary: Error writing the CC link error mask

Event Class: System

Problem Description:
Failed writing the XIN error mask for CC's fabric link. Data Field: (cell << 56) | return status

Cause / Action:
Fabric Access Error.
Contact HP Support personnel to analyze the fabric.

Automated Recovery: None

Event Generation Threshold: 1 occurrence

Event Details:
Examples:
Event 856

Severity: MAJOR_WARNING

Event Summary: Failed to read the CC's fabric link error mask

Event Class: System

Problem Description:
Could not read the XIN Link error mask register. Data Field: (cell << 56) | return status

Cause / Action:
CC CSR access failure.
Contact HP Support personnel to analyze the fabric.

Automated Recovery: None

Event Generation Threshold: 1 occurrence

Event Details:
Examples:
Event 857

Severity: SERIOUS

Event Summary: Could not initialize the CC to CC link upon boot.

Event Class: System

Problem Description:
The CC to CC link initialization sequence has failed. Data Field: link init status

Cause / Action:
CC CSR Access Failure.
Contact HP Support personnel to analyze the fabric.

Automated Recovery: None

Event Generation Threshold: 1 occurrence

Event Details:
Examples:
Event 858

Severity: MAJOR_WARNING

Event Summary: An Error occurred trying to notify the MP of the attempted reset.

Event Class: System

Problem Description:
An error occurred while trying to notify the MP that a reset is about to occur (QPartitionReleaseBIB command). The status is in the data field.

Cause / Action:
The MP is not functioning or the PDHC cannot communicate with it. Reset the MP.

Automated Recovery: None

Event Generation Threshold: 1 occurrence

Event Details:
Examples:
Event 860

Severity: MAJOR_WARNING

Event Summary: Failed disabling the XIN link for a single cell medel

Event Class: System

Problem Description:
A fabric access error occurred while trying to disable the CC to CC link on a single cell Medel system. This cell will halt. Data field: error status

Cause / Action:
Fabric Access Error.
Contact HP Support personnel to analyze the fabric.

Automated Recovery: None

Event Generation Threshold: 1 occurrence

Event Details:
Examples:
Event 861

Severity: SERIOUS

Event Summary: Error while getting the XBC Semaphore

Event Class: System

Problem Description:
While updating the Port State register, the cell could not get the XBC semaphore. Data field is: (Port Num << 44 | XBC num << 32 | return status). Where return status is: (0 Success; -1 Access Failure; -2 Semaphore Owned By Another, -3 Semaphore Already Owned; -4 XBC Key Contention)

Cause / Action:
Most likely a hardware problem, but confirm the cause by looking at the return status. Action: Check XBC, Backplane, Flex Cables, Contact HP Support Personnel for further troubleshooting.

Automated Recovery: None

Event Generation Threshold: 1 occurrence

Event Details:
Examples:
Event 862

Severity: MAJOR_WARNING

Event Summary: Error releasing the XBC Semaphore

Event Class: System

Problem Description:
While updating the Port State register, the cell could not get the XBC semaphore. Data field is: (Port Num << 44 | XBC num << 32 | return status). Where return status is: (0 Success; -1 Generic Failure)

Cause / Action:
Cause: Fabric Access problem. Either an error reading the hardware or XBC Key contention. Action: Look for additional chassis codes to provide detail. Check XBC, Backplane, Flex Cables, Contact HP Support Personnel.

Automated Recovery: None

Event Generation Threshold: 1 occurrence

Event Details:
Examples:
Event 864

Severity: MAJOR_WARNING

Event Summary: Unexpected fabric firmware error

Event Class: System

Problem Description:
An unexpected error occurred while initializing the fabric. The firmware is not able to analyze this error. Clues to the cause of this error may be found in the IPMI forward progress log (FPL) either shortly before or after this log entry occurred. The FPL is available from the management processor using the "sl" command. HP-UX also saves these logs in the /var/stm/logs/os directory, and they can be viewed using the slview utility. For more details on the slview utility, refer to the slview web page at http://docs.hp.com/hpux/onlinedocs/diag/st/st_event_viewer.htm

Cause / Action:
An unanticipated error occurred. Contact HP Support personnel to analyze the IPMI FPL log.

Automated Recovery: None

Event Generation Threshold: 1 occurrence

Event Details:
Examples:
Event 865

Severity: MAJOR_WARNING

Event Summary: The CC's XIN link was found to be already initialized

Event Class: System

Problem Description:
While attempting to initialize the XIN link, it was found to already be initialized. A firmware assertion has failed. The link will not be re-initialized and processing should continue as normal. However, the system could be confused at this point.

Cause / Action:
Firmware problem. Contact HP Support Personnel.

Automated Recovery: None

Event Generation Threshold: 1 occurrence

Event Details:
Examples:
Event 866

Severity: SERIOUS

Event Summary: Cell has been disabled by the PDHC because no CPU modules were found.

Event Class: System

Problem Description:
The PDHC FW could not detect any CPU modules on its Cell board, so it is holding the Cell in reset.

Cause / Action:
Cause(1, probable): No CPU modules are installed. Action(1): Install CPU modules on the Cell. Cause(2): A Cell or PDH Daughtercard error is causing the presence of CPU modules to be reported incorrectly to the PDHC. Action(2): Contact HP support personnel to troubleshoot the PDH Daughtercard and/or Cell board. Cause(3): The CPU module(s) that are installed have invalid data stored in the partition specific field of the FRU EEPROM. Action(3): 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.

Automated Recovery: None

Event Generation Threshold: 1 occurrence

Event Details:
Examples:
Event 867

Severity: SERIOUS

Event Summary: Cell has been disabled by PDHC FW because the CPU modules are not compatible.

Event Class: System

Problem Description:
The Cell has been disabled by PDHC FW because the CPU modules are not compatible. Compatibility is determined based on data stored in the Scratch/FRUID EEPROM on each CPU module. The CPU module partition compatibility byte for each CPU module must be identical.

Cause / Action:
Cause(1): At least one of the installed CPU modules are incompatible with at least one other CPU module. Action(1): Contact HP support personnel to troubleshoot the CPU modules on the Cell. Cause(2): The FRUID data stored in a CPU Module's Scratch/FRUID EEPROM is incorrectly programmed. Action(1): Reprogram the FRUID data (manufacturing only) or contact HP support personnel to troubleshoot the CPU module on the Cell.
Cause(1): At least one of the installed CPU modules are incompatible with at least one other CPU module. Action(1): Contact HP support personnel to troubleshoot one or more CPU modules on the Cell. Cause(2): The FRUID data stored in a CPU Module's Scratch/FRUID EEPROM is incorrectly programmed. Action(1): Reprogram the FRUID data (manufacturing only) or contact HP support personnel to troubleshoot the CPU module on the Cell.

Automated Recovery: None

Event Generation Threshold: 1 occurrence

Event Details:
Examples:
Event 868

Severity: SERIOUS

Event Summary: Cell has been disabled because of invalid data in a CPU module Scratch EEPROM.

Event Class: System

Problem Description:
The Cell has been disabled because of invalid data in a CPU module Scratch EEPROM. PDHC FW checksums the FRUID data stored in each CPU module's Scratch EEPROM. If a checksum fails, the Cell is held in reset and will not boot. The data field identifies the CPU module that failed.

Cause / Action:
Cause: The CPU module is not an HP CPU module, or the FRUID data for this CPU module has not been programmed.
Action: Contact HP support personnel to troubleshoot the CPU module.

Automated Recovery: None

Event Generation Threshold: 1 occurrence

Event Details:
Examples:
Event 869

Severity: MAJOR_WARNING

Event Summary: The Cell Battery voltage level low warning

Event Class: System

Problem Description:
The battery voltage level is low for the cell. This indicates that the NVRAM will not be saved if the power is removed.

Cause / Action:
Cause1: The Cell Battery is low. Action1: It needed to be replaced.

Automated Recovery: None

Event Generation Threshold: 1 occurrence

Event Details:
Examples:
Event 870

Severity: SERIOUS

Event Summary: Error while copying the XBC routing to the local port

Event Class: System

Problem Description:
There was an error while copying the routing for the XBC to the local XBC port. The cell will reset. Data: (XBC port << 44) | (XBC num << 32) | return status

Cause / Action:
Error accessing XBC CSRs.
Contact HP Support personnel to analyze the fabric.

Automated Recovery: None

Event Generation Threshold: 1 occurrence

Event Details:
Examples:
Event 871

Severity: SERIOUS

Event Summary: A read after write of a XBC CSR failed

Event Class: System

Problem Description:
The read immediately after a write while copying routing registers failed. Data: whether or not the XBC Key was enabled

Cause / Action:
Fabric Access Error, XBC Key Disabled. Check XBC, links, backplane, Contact HP Support Personnel for further troubleshooting.

Automated Recovery: None

Event Generation Threshold: 1 occurrence

Event Details:
Examples:
Event 872

Severity: MAJOR_WARNING

Event Summary: Couldn't release the Semaphore while writing routing states.

Event Class: System

Problem Description:
Failed to release a XBC Semaphore while marking each XBC in the complex to indicate that routing has completed. Data: (XBC num << 32) | return value

Cause / Action:
Fabric Access Error. Check XBC, Check links.

Automated Recovery: None

Event Generation Threshold: 1 occurrence

Event Details:
Examples:
Event 873

Severity: SERIOUS

Event Summary: Couldn't write the XBC's forward progress register

Event Class: System

Problem Description:
Writing this XBC's forward progress register failed. Data: (XBC num << 32) | return value

Cause / Action:
Fabric Access Error. Couldn't write this XBC.
Contact HP Support personnel to analyze the fabric.

Automated Recovery: None

Event Generation Threshold: 1 occurrence

Event Details:
Examples:
Event 874

Severity: SERIOUS

Event Summary: Couldn't access the XBC semaphore registers.

Event Class: System

Problem Description:
Failed to get a XBC Semaphore while marking each XBC in the complex to indicate that routing has completed. Skipping this XBC. Data: (XBC num << 32) | return value

Cause / Action:
Fabric Access Error. Couldn't read or write this XBC.
Contact HP Support personnel to analyze the fabric.

Automated Recovery: None

Event Generation Threshold: 1 occurrence

Event Details:
Examples:
Event 875

Severity: SERIOUS

Event Summary: Couldn't determine the complex fabric topology

Event Class: System

Problem Description:
Reading this XBC's topology register failed. Data Field: (xbc num << 32) | return status

Cause / Action:
Fabric Access Error. Couldn't write this XBC.
Contact HP Support personnel to analyze the fabric.

Automated Recovery: None

Event Generation Threshold: 1 occurrence

Event Details:
Examples:
Event 876

Severity: MAJOR_WARNING

Event Summary: Error checking a cell to cell link during traversability tests

Event Class: System

Problem Description:
Could not check the traversability between two cells on an XBCless platform. Data field: return status (1 = SUCCESS, 0 = FALSE, -1 = FAILURE)

Cause / Action:
Probably an error reading the XIN. Look for additional descriptive chassis codes.
Contact HP Support personnel to check the CC

Automated Recovery: None

Event Generation Threshold: 1 occurrence

Event Details:
Examples:
Event 877

Severity: MAJOR_WARNING

Event Summary: An error occurred while traversing the cell to cell link.

Event Class: System

Problem Description:
Could not check the traversability between two cells on an XBCless platform. Data field: return status (1 = SUCCESS, 0 = FALSE, -1 = FAILURE)

Cause / Action:
Probably an error reading the XIN. Look for additional descriptive chassis codes.
Contact HP Support personnel to check the CC

Automated Recovery: None

Event Generation Threshold: 1 occurrence

Event Details:
Examples:
Event 878

Severity: MAJOR_WARNING

Event Summary: Error reading the local cell's XIN link state

Event Class: System

Problem Description:
While checking traversability of a 2 cell back to back system, there was an error reading the local cell's XIN block. Data Field: return status (1 or -1)

Cause / Action:
Hardware Access Error. Have your HP support representative check the Coherency Controller (CC).

Automated Recovery: None

Event Generation Threshold: 1 occurrence

Event Details:
Examples:
Event 879

Severity: MAJOR_WARNING

Event Summary: Error reading the remote cell's XIN link state register

Event Class: System

Problem Description:
While checking traversability of a 2 cell back to back system, there was an error reading the local cell's XIN block. Data Field: return status (1 or -1)

Cause / Action:
Hardware Access Error. Have your HP support representative check the backplane and Coherency Controller (CC).

Automated Recovery: None

Event Generation Threshold: 1 occurrence

Event Details:
Examples:
Event 880

Severity: MAJOR_WARNING

Event Summary: The XIN link is not connected to the target cell.

Event Class: System

Problem Description:
Could not traverse to the target cell. The XIN link is either not initialized, or is not connected to the target cell. However, the target cell is designated to be within the partition. Data Field: target cell << 56 | XIN link state register

Cause / Action:
Ensure the cells are connected. Check historical chassis codes from most recent boot to see if the link had ever initialized. Have your HP support representative check the backplane and Coherency Controller (CC).

Automated Recovery: None

Event Generation Threshold: 1 occurrence

Event Details:
Examples:
Event 881

Severity: MAJOR_WARNING

Event Summary: The XIN link is not connected to the target cell.

Event Class: System

Problem Description:
Could not traverse to the target cell. The XIN link is either not initialized, or is not connected to the target cell. However, the target cell is designated to be within the partition. Data Field: target cell << 56 | XIN link state register

Cause / Action:
Ensure the cells are connected. Check historical chassis codes from most recent boot to see if the link had ever initialized. Have your HP support representative check the backplane and Coherency Controller (CC).

Automated Recovery: None

Event Generation Threshold: 1 occurrence

Event Details:
Examples:
Event 882

Severity: MAJOR_WARNING

Event Summary: Error reading the XIN_LINK_STATE register while disabling the link

Event Class: System

Problem Description:
Error reading the XIN_LINK_STATE register of the CC. This occurred while verifying that the link had been disabled. Data Field: cell being read << 56 | return status from the CSR read.

Cause / Action:
Hardware Access Error.
Contact HP Support personnel to analyze the fabric, CC, Backplane.

Automated Recovery: None

Event Generation Threshold: 1 occurrence

Event Details:
Examples:
Event 883

Severity: SERIOUS

Event Summary: Error reading the XIN_LINK_STATE register

Event Class: System

Problem Description:
Failure while reading the XBC CSR containing the link status. This occurred while attempting the retry process to get XBC to CC link initialized. Data Field: link init status

Cause / Action:
link init problem
Contact HP Support personnel to check the XBC, CC, backplane

Automated Recovery: None

Event Generation Threshold: 1 occurrence

Event Details:
Examples:
Event 884

Severity: MAJOR_WARNING

Event Summary: Unexpected fabric firmware error

Event Class: System

Problem Description:
An unexpected error occurred while initializing the fabric. The firmware is not able to analyze this error. Clues to the cause of this error may be found in the IPMI forward progress log (FPL) either shortly before or after this log entry occurred. The FPL is available from the management processor using the "sl" command. HP-UX also saves these logs in the /var/stm/logs/os directory, and they can be viewed using the slview utility. For more details on the slview utility, refer to the slview web page at http://docs.hp.com/hpux/onlinedocs/diag/st/st_event_viewer.htm

Cause / Action:
An unanticipated error occurred. Contact HP Support personnel to analyze the IPMI FPL log.

Automated Recovery: None

Event Generation Threshold: 1 occurrence

Event Details:
Examples:
Event 885

Severity: MAJOR_WARNING

Event Summary: The CPU is performance or functionally restricted

Event Class: System

Problem Description:
The CPU that just completed self tests is functionally or performance restricted. The data field contains the self-test state word.

Cause / Action:
A CPU is broken. Replace it.

Automated Recovery: None

Event Generation Threshold: 1 occurrence

Event Details:
Examples:
Event 886

Severity: MAJOR_WARNING

Event Summary: The RTC was found to be invalid and has been cleared

Event Class: System

Problem Description:
The RTC was found to be invalid and has been cleared

Cause / Action:
Cause: The RTC was invalid Action: None, the problem has been corrected by SFW.

Automated Recovery: None

Event Generation Threshold: 1 occurrence

Event Details:
Examples:
Event 887

Severity: MAJOR_WARNING

Event Summary: Status indicates that the Late Self Tests did not actually run

Event Class: System

Problem Description:
System firmware requested that Late Self Tests be run by PAL, but PAL returned that the tests did not actually run on the processor. The data field indicates the status word returned by PAL.

Cause / Action:
This could be caused by an incompatibity problem between PAL and the CPUs. Check that PAL supports all the CPUs installed on the system.

Automated Recovery: None

Event Generation Threshold: 1 occurrence

Event Details:
Examples:
Event 888

Severity: SERIOUS

Event Summary: A fabric walk failed while updating the cell state

Event Class: System

Problem Description:
An attempt to update the cell state has failed due to a fabric crossbar failure. The cell number being updated in in bits 63:56, while the traversable cell set (those cells connected to the fabric) is returned in bits 31:0

Cause / Action:
Look for adjacent chassis codes to determine the cause of FabricWalk failure. Check the backplane and fabric connectivity. Contact the HP Support Personnel for further troubleshooting.

Automated Recovery: None

Event Generation Threshold: 1 occurrence

Event Details:
Examples:
Event 889

Severity: SERIOUS

Event Summary: Could not reset the cell due to failure updating cell state

Event Class: System

Problem Description:
Failed to reset a cell due to an error setting the cell's state. The cell will not be reset with the other cells in the PD. The cell number is reported in the data field.

Cause / Action:
Most likely a failure on the fabric or on the CC. Fabric failures should produce additional chassis codes. If no additional chassis codes inidicate the cause of the failure, then contact the HP Support Personnel for further troubleshooting.

Automated Recovery: None

Event Generation Threshold: 1 occurrence

Event Details:
Examples:
Event 890

Severity: MAJOR_WARNING

Event Summary: DRAM failure on DIMM XX, deallocte rank

Event Class: System

Problem Description:
SFW has detected that a DRAM is failing on the DIMM specified by the physical location. The rank the failing DIMM is part of will be deallocated.

Cause / Action:
C: SFW detected a failing DIMM A: Replace the DIMM flagged by SFW

Automated Recovery: None

Event Generation Threshold: 1 occurrence

Event Details:
Examples:
Event 891

Severity: SERIOUS

Event Summary: System Clocks are not valid

Event Class: System

Problem Description:
Internal CPU clocks are not valid when compared with the real time clock. The data field contains the hex value of the elapsed time. If this value is off a small percentage from the expected value (which is given in the next chassis code), the event is emitted.

Cause / Action:
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.

Automated Recovery: None

Event Generation Threshold: 1 occurrence

Event Details:
Examples:
Event 892

Severity: SERIOUS

Event Summary: Cell Online Addition failed due to fabric access error

Event Class: System

Problem Description:
Could not traverse the fabric to the cell being added. Data field: (chosen cell << 56) | return status, where -1 = failure

Cause / Action:
Cause: Fabric Access Failure, Action: Check CC to CC link. Look for additional failure chassis codes to provide more detail.

Automated Recovery: None

Event Generation Threshold: 1 occurrence

Event Details:
Examples:
Event 893

Severity: SERIOUS

Event Summary: Fabric found a bad XBC port on a reboot. Attempting to route around it.

Event Class: System

Problem Description:
A XBC port was found to be unhealthy on this reboot. This cell will attempt to route around it. Data field: (local Cell << 56) | (local internal Port << 44) | (local XBC << 32) | XBC internal port number being routed around.

Cause / Action:
Cause: link errors. Action: Run DC Connectivity test. Check flex cables, XBCs, and CCs.

Automated Recovery: None

Event Generation Threshold: 1 occurrence

Event Details:
Examples:
Event 894

Severity: MAJOR_WARNING

Event Summary: Could not access an internal firmware table while rerouting XBC port

Event Class: System

Problem Description:
Error getting the XBC port's expected neighbor from a firmware table. Data field: 0 (SUCCESS) or -1 (FAILURE)

Cause / Action:
Cause: Firmware Error. Action: Capture chassis codes and contact HP Support.

Automated Recovery: None

Event Generation Threshold: 1 occurrence

Event Details:
Examples:
Event 895

Severity: MAJOR_WARNING

Event Summary: Cell/Partition to be reset because PDC couldn't read PDH memory

Event Class: System

Problem Description:
Either PDC is going to halt the cell or reset the partition because PDC was unable to access the PDH memory of either its local cell or another cell in the partition. The data field contains the error return value from PDC function IsHCellCpuDeconfig().

Cause / Action:
Cause1: Cell hardware problem like PDH memory itself, the coherency controller, the executing CPU or interaction between any of these cell components. Action1: Contact HP Support to troubleshoot the cell and either fix it or replace it. Cause2: PDC bug in which PDC thinks it was unable to safely access PDH memory when maybe it really could have. Action2: Contact HP Support to see if a new PDC image is available.

Automated Recovery: None

Event Generation Threshold: 1 occurrence

Event Details:
Examples:
Event 896

Severity: MAJOR_WARNING

Event Summary: Cell/Partition to be reset because PDC couldn't read PDH memory

Event Class: System

Problem Description:
Either PDC is going to halt the cell or reset the partition because PDC was unable to access the PDH memory of either its local cell or another cell in the partition. The data field contains the error return value from PDC function SleepAndWakeupCountersGet().

Cause / Action:
Cause1: Cell hardware problem like PDH memory itself, the Concorde chip, the executing Mako or interaction between any of these cell components. Action1: Troubleshoot the cell and either fix it or replace it. Cause2: PDC bug in which PDC has passed an invalid argument from one PDC function to another. Action2: Upgrade PDC if this is found to be the problem and a new PDC image is available.

Automated Recovery: None

Event Generation Threshold: 1 occurrence

Event Details:
Examples:
Event 897

Severity: MAJOR_WARNING

Event Summary: Cell/Partition to be reset because PDC couldn't read PDH memory

Event Class: System

Problem Description:
Either PDC is going to halt the cell or reset the partition because PDC was unable to access the PDH memory of either its local cell or another cell in the partition. The data field contains the error return value from PDC function PdhGetHCellStructAddr().

Cause / Action:
Cause1: Cell hardware problem like PDH memory itself, the Concorde chip, the executing Mako or interaction between any of these cell components. Action1: Troubleshoot the cell and either fix it or replace it. Cause2: PDC bug in which PDC thinks it was unable to safely access PDH memory when maybe it really could have. Action2: Upgrade PDC if this is found to be the problem and a new PDC image is available.

Automated Recovery: None

Event Generation Threshold: 1 occurrence

Event Details:
Examples:
Event 898

Severity: MAJOR_WARNING

Event Summary: Cell/Partition to be reset because PDC couldn't read PDH memory

Event Class: System

Problem Description:
Either PDC is going to halt the cell or reset the partition because PDC was unable to access the PDH memory of either its local cell or another cell in the partition. The data field contains the error return value from PDC function HasCpuCompletedWakeupTask().

Cause / Action:
Cause1: Cell hardware problem like PDH memory itself, the Concorde chip, the executing Mako or interaction between any of these cell components. Action1: Troubleshoot the cell and either fix it or replace it. Cause2: PDC bug in which PDC thinks it was unable to safely access PDH memory when maybe it really could have. Action2: Upgrade PDC if this is found to be the problem and a new PDC image is available.

Automated Recovery: None

Event Generation Threshold: 1 occurrence

Event Details:
Examples:
Event 899

Severity: MAJOR_WARNING

Event Summary: Cell/Partition to be reset because PDC couldn't read PDH memory

Event Class: System

Problem Description:
Either PDC is going to halt the cell or reset the partition because PDC was unable to access the PDH memory of either its local cell or another cell in the partition. The data field contains the error return value from PDC function PdhGetHCellStructAddr().

Cause / Action:
Cause1: Cell hardware problem like PDH memory itself, the Concorde chip, the executing Mako or interaction between any of these cell components. Action1: Troubleshoot the cell and either fix it or replace it. Cause2: PDC bug in which PDC thinks it was unable to safely access PDH memory when maybe it really could have. Action2: Upgrade PDC if this is found to be the problem and a new PDC image is available.

Automated Recovery: None

Event Generation Threshold: 1 occurrence

Event Details:
Examples:
Event 900

Severity: MAJOR_WARNING

Event Summary: A reset for reconfiguration will be performed soon on the cell.

Event Class: System

Problem Description:
There is a need to reset the cell for reconfiguration, but it cannot be done yet because the cell has not reported at BIB. The Reset is being scheduled to be performed later.

Cause / Action:
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.

Automated Recovery: None

Event Generation Threshold: 1 occurrence

Event Details:
Examples:
Event 901

Severity: MAJOR_WARNING

Event Summary: The Partition Profile specifies the wrong architecture type

Event Class: System

Problem Description:
When processing the complex profile, the an unexpected "Architecture Type" was specified in the PA/IA Arch field. The actual data found is displayed.

Cause / Action:
This is caused by the wrong type of complex profile being loaded. System firmware will default a new partition profile and continue on.

Automated Recovery: None

Event Generation Threshold: 1 occurrence

Event Details:
Examples:
Event 902

Severity: MAJOR_WARNING

Event Summary: Cell/Partition is about to be reset because PDC is unable to access CPU data

Event Class: System

Problem Description:
While trying to determine whether or not a particular processor has completed the task for which it was awakened, PDC was unable to access the deconfig byte information about the target processor. A processor should always be able to access this data in PDH memory for any processor on its own cell and for any processor on a cell that is alive in the partition. Therefore, PDC is either going to halt the cell or reset the partition because of this problem. The data field contains the PDC error return status from IsHCellCpuDeconfig().

Cause / Action:
Cause1: Cell hardware problem, like a problem with PDH registers or PDH memory, or a problem with the concorde or Mako chips. Action1: Troubleshoot the cell and either fix cell or replace the cell board. Cause2: PDC problem such that PDC is passing bad data from one function to another. Action2: Upgrade PDC.

Automated Recovery: None

Event Generation Threshold: 1 occurrence

Event Details:
Examples:
Event 903

Severity: MAJOR_WARNING

Event Summary: Cell/Partition is about to be reset because PDC is unable to access CPU data

Event Class: System

Problem Description:
While trying to determine whether or not a particular processor has completed the task for which it was awakened, PDC was unable to access the CPU's sleep and wakeup counters for the target processor. A processor should always be able to access this data in PDH memory for any processor on its own cell and for any processor on a cell that is alive in the partition. Therefore, PDC is either going to halt the cell or reset the partition because of this problem. The data field contains the PDC error return status from SleepAndWakeupCountersGet().

Cause / Action:
Cause1: Cell hardware problem, like a problem with PDH registers or PDH memory, or a problem with the concorde or Mako chips. Action1: Troubleshoot the cell and either fix cell or replace the cell board. Cause2: PDC problem such that PDC is passing bad data from one function to another. Action2: Upgrade PDC.

Automated Recovery: None

Event Generation Threshold: 1 occurrence

Event Details:
Examples:
Event 904

Severity: MAJOR_WARNING

Event Summary: Cell/Partition about to be reset because PDC is unable to access CPU data

Event Class: System

Problem Description:
While trying to determine whether or not a particular processor has completed the task for which it was awakened, PDC was unable to access the CPU's forward progress state (i.e. PST state) for the target processor. A processor should always be able to access this data in PDH memory for any processor on its own cell and for any processor on a cell that is alive in the partition. Therefore, PDC is either going to halt the cell or reset the partition because of this problem. The data field contains the PDC error return status from CpuFpSet().

Cause / Action:
Cause1: Cell hardware problem, like a problem with PDH registers or PDH memory, or a problem with the concorde or Mako chips. Action1: Troubleshoot the cell and either fix cell or replace the cell board. Cause2: PDC problem such that PDC is passing bad data from one function to another. Action2: Upgrade PDC.

Automated Recovery: None

Event Generation Threshold: 1 occurrence

Event Details:
Examples:
Event 905

Severity: MAJOR_WARNING

Event Summary: Cell/Partition is about to be reset because PDC is unable to access CPU data

Event Class: System

Problem Description:
While trying to determine whether or not a particular processor has completed the task for which it was awakened, PDC was unable to access the CPU's Forward Progress State (i.e. PST state) for the target processor. A processor should always be able to access this data in PDH memory for any processor on its own cell and for any processor on a cell that is alive in the partition. Therefore, PDC is either going to halt the cell or reset the partition because of this problem. The data field contains the PDC error return status from CpuFpSet().

Cause / Action:
Cause1: Cell hardware problem, like a problem with PDH registers or PDH memory, or a problem with the concorde or Mako chips. Action1: Troubleshoot the cell and either fix cell or replace the cell board. Cause2: PDC problem such that PDC is passing bad data from one function to another. Action2: Upgrade PDC.

Automated Recovery: None

Event Generation Threshold: 1 occurrence

Event Details:
Examples:
Event 906

Severity: MAJOR_WARNING

Event Summary: PDC is unable to branch to other software via the Page Zero location

Event Class: System

Problem Description:
At a certain point in PDC boot, all of the processors in the partition except the PD monarch are put into a sleep, and they remain there until they are awakened by the PD monarch, at which time they read an architected location in Page Zero to find out where to branch to. This gives the OS a mechanism by which to bring processors under its control and have it executing OS code. This chassis log is sent if and when a problem is detected by PDC regarding the contents in the Page Zero location. This means that PDC cannot branch to the location logged in the Page Zero location. So, PDC sends this chassis log and then the processor returns to sleep. The data field is unused.

Cause / Action:
Cause1: The MEM_RENDEZ fields of Page Zero were programmed incorrectly. Action1: Upgrade or patch the OS. Cause2: Cell Hardware or memory problem that PDC didn't catch. Action2: Troubleshoot the cell to find out if page zero contents are screwed up or if hardware is just failed to do the OS write or failed to do the PDC read. Verify that memory is properly written and holds contents at the page zero locations. Perhaps replace the cell board or replace the memory. Cause3: PDC is not doing the appropriate verification of the page zero contents and is treating it like its invalid even though maybe its not. Action3: Upgrade PDC.

Automated Recovery: None

Event Generation Threshold: 1 occurrence

Event Details:
Examples:
Event 908

Severity: MAJOR_WARNING

Event Summary: PDC couldn't access a data structure in PDH memory

Event Class: System

Problem Description:
While trying to get the sleep counter and the wakeup counter for a particular processor, which is kept in a data structure in PDH memory, PDC was unable to determine the address to the data structure on the remote cell. PDC is supposed to be able to calculate addresses to anything in PDH memory on other cells in the partition. The data field contains the PDC error return status from a function called PdhGetHCellStructAddr().

Cause / Action:
Cause1: Cell hardware problem with the PDH memory, the Concorde chip, or the Mako processor itself. Action1: Troubleshoot/Replace the cell. Cause2: PDC bug in which PDC is trying to access PDH memory of a cell not in its partition. Action2: Upgrade PDC if there is a version of PDC that fixes such a problem.

Automated Recovery: None

Event Generation Threshold: 1 occurrence

Event Details:
Examples:
Event 909

Severity: MAJOR_WARNING

Event Summary: Error occurred accessing a PDC data structure

Event Class: System

Problem Description:
Error occurred accessing a PDC data structure. Depending upon the situation the cell or entire partition will be reset. The data field contains the return status for the function that encountered the error.

Cause / Action:
Cause1: Hardware problem with the PDH riser card. Action1: Contact HP Support to confirm the PDH riser card is functioning properly. Cause2: Hardware problem with the CPU or cell board. Action2: Contact HP Support to confirm the CPUs and cell board are functioning properly.

Automated Recovery: None

Event Generation Threshold: 1 occurrence

Event Details:
Examples:
Event 910

Severity: MAJOR_WARNING

Event Summary: Cell about to be halted because PDC couldn't determine relocated address of code

Event Class: System

Problem Description:
PDC is about to halt the cell because PDC was unable to determine the GNI address of the SlaveDispatcher function of PDC relocated to memory by PDC. The data field contains the error return value from the function GetGniCodeAddrFromRomCodeAddr().

Cause / Action:
Cause1: Hardware connecting cells in the partition experienced a problem such that cells in the partition together can no longer communicate. Action1: Troubleshoot the fabric and reseat/replace the cells or cables or backplane if necessary. Cause2: Cell was unable to access its own PDH memory. Action2: Troubleshoot the cell board and replace it if necessary. Cause3: PDC bug such that PDC didn't log the relocation address. Action3: Check for PDC upgrade

Automated Recovery: None

Event Generation Threshold: 1 occurrence

Event Details:
Examples:
Event 911

Severity: MAJOR_WARNING

Event Summary: Halting cell because a CPU didn't complete the task for which it was awakened

Event Class: System

Problem Description:
PDC is about to halt the cell because at least one of the processors didn't complete the task for which they were awakened and then return to sleep. The data field contains an error return status.

Cause / Action:
Cause1: Hardware problem with the CPU, CC, or PDH flash. Action1: Troubleshoot the cell and/or replace it.

Automated Recovery: None

Event Generation Threshold: 1 occurrence

Event Details:
Examples:
Event 912

Severity: MAJOR_WARNING

Event Summary: Cell about to be halted because PDC couldn't determine relocated address of code

Event Class: System

Problem Description:
PDC is about to halt the cell because PDC was unable to determine the GNI address of the CpuFpSet() function of PDC relocated to memory by PDC. The data field contains the error return value from the function GetGniCodeAddrFromRomCodeAddr().

Cause / Action:
Cause1: Hardware connecting cells in the partition experienced a problem such that cells in the partition together can no longer communicate. Action1: Troubleshoot the fabric and reseat/replace the cells or cables or backplane if necessary. Cause2: Cell was unable to access its own PDH memory. Action2: Troubleshoot the cell board and replace it if necessary. Cause3: PDC bug such that PDC didn't log the relocation address. Action3: Check for PDC upgrade

Automated Recovery: None

Event Generation Threshold: 1 occurrence

Event Details:
Examples:
Event 913

Severity: MAJOR_WARNING

Event Summary: Cell about to be halted because CPU couldn't change its CPU FP (PST) state

Event Class: System

Problem Description:
PDC is about to halt the cell because one or more of the slaves were unable to change their CPU FP state in PDH memory on the local cell. The data field contains an error return status.

Cause / Action:
Cause1: Hardware problem with the cell (like PDH memory) or the CC or CPU. Action1: Contact HP support to troubleshoot or replace the cell board. Cause2: PDC bug. Action2: Contact HP Support to check for PDC upgrade.

Automated Recovery: None

Event Generation Threshold: 1 occurrence

Event Details:
Examples:
Event 914

Se