IPMI Forward Progress Log Monitor (Events)

Hewlett-Packard

IPMI Forward Progress Log Monitor (Events)

Event 200

Severity: MAJOR
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 201

Severity: MAJOR
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 203

Severity: FATAL
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 204

Severity: MAJOR
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 205

Severity: MAJOR
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 207

Severity: FATAL
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 208

Severity: FATAL
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 209

Severity: FATAL
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 210

Severity: FATAL
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 211

Severity: MAJOR
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 212

Severity: MAJOR
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 213

Severity: MAJOR
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 214

Severity: MAJOR
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 215

Severity: MAJOR
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 216

Severity: MAJOR
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 217

Severity: FATAL
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 218

Severity: FATAL
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 219

Severity: FATAL
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 220

Severity: FATAL
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 221

Severity: FATAL
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 222

Severity: FATAL
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 223

Severity: FATAL
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 224

Severity: FATAL
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 225

Severity: FATAL
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 226

Severity: MAJOR
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 227

Severity: FATAL
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 228

Severity: FATAL
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 229

Severity: MAJOR
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 230

Severity: MAJOR
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 231

Severity: MAJOR
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 232

Severity: MAJOR
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 233

Severity: FATAL
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 234

Severity: MAJOR
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 235

Severity: FATAL
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 236

Severity: FATAL
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 238

Severity: MAJOR
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 239

Severity: FATAL
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 240

Severity: FATAL
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 241

Severity: FATAL
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 242

Severity: FATAL
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 243

Severity: FATAL
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 244

Severity: FATAL
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 245

Severity: MAJOR
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 246

Severity: MAJOR
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 247

Severity: MAJOR
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 248

Severity: MAJOR
Event Summary: platform scratch RAM test failed
Event Class: System
Problem Description:
Platform 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 249

Severity: MAJOR
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 250

Severity: FATAL
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 251

Severity: FATAL
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 252

Severity: MAJOR
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 253

Severity: MAJOR
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 254

Severity: MAJOR
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 255

Severity: FATAL
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 256

Severity: FATAL
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 257

Severity: FATAL
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 258

Severity: FATAL
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 259

Severity: MAJOR
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 260

Severity: FATAL
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 261

Severity: FATAL
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 262

Severity: FATAL
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 263

Severity: FATAL
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 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 264

Severity: FATAL
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 265

Severity: MAJOR
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 266

Severity: MAJOR
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 267

Severity: FATAL
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 268

Severity: MAJOR
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 269

Severity: MAJOR
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 270

Severity: MAJOR
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 271

Severity: MAJOR
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 272

Severity: MAJOR
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 273

Severity: MAJOR
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 274

Severity: MAJOR
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 275

Severity: MAJOR
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 276

Severity: MAJOR
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 277

Severity: MAJOR
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 278

Severity: MAJOR
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 279

Severity: MAJOR
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 280

Severity: MAJOR
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 281

Severity: MAJOR
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 282

Severity: MAJOR
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 283

Severity: MAJOR
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 284

Severity: MAJOR
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 285

Severity: MAJOR
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 286

Severity: MAJOR
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 287

Severity: MAJOR
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 288

Severity: MAJOR
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 289

Severity: MAJOR
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 290

Severity: MAJOR
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 292

Severity: FATAL
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 293

Severity: FATAL
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 294

Severity: FATAL
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 295

Severity: FATAL
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:
Cause: Memory page 0 was slated for deallocation in the PDT. Action: 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 296

Severity: FATAL
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 297

Severity: MAJOR
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 298

Severity: MAJOR
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:
Cause: The chipset failed the register test. Action: Contact HP support to troubleshoot the problem.
Automated Recovery: None
Event Generation Threshold: 1 occurrence

Event 299

Severity: MAJOR
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:
Cause: The DIMM that maps to cache line 0 is in a chipspare condition Action: Contact HP support Cause: The DIMM that maps to address 0 is not seated properly Action: Check all of the DIMMs in the system and make sure that they are inserted fully into the slot with the retention mechanism in place Cause: System may be running at the wrong frequency. Action: Verify the system bus frequency and the memory bus frequency.
Automated Recovery: None
Event Generation Threshold: 1 occurrence

Event 300

Severity: MAJOR
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:
Cause: A required DIMM is not loaded in order to allow for proper operation of the DIMM specified in the physical location. Action: Refer to the user's manual for Memory loading instructions.
Automated Recovery: None
Event Generation Threshold: 1 occurrence

Event 301

Severity: MAJOR
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:
Cause: The DIMMs SPD EEPROM got corrupted. Action: Contact HP Support personnel to troubleshoot the problem
Automated Recovery: None
Event Generation Threshold: 1 occurrence

Event 302

Severity: MAJOR
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 303

Severity: MAJOR
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 304

Severity: MAJOR
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 305

Severity: MAJOR
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:
Cause: Too many different types of DIMMs in system Action: Reduce the number of different types of DIMMs in the system.
Automated Recovery: None
Event Generation Threshold: 1 occurrence

Event 306

Severity: MAJOR
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:
Cause: Probable internal FW error Action: Reload System Firmware Action: Contact HP Support personnel to troubleshoot the problem
Automated Recovery: None
Event Generation Threshold: 1 occurrence

Event 307

Severity: MAJOR
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 casue an MBE.
Cause / Action:
Cause: The CEC failed MBE detection. Action: Contact HP support personnel to troubleshoot the problem
Automated Recovery: None
Event Generation Threshold: 1 occurrence

Event 308

Severity: MAJOR
Event Summary: Memory ECC multiple-bit ECC error signalling failed
Event Class: System
Problem Description:
The FW selftest of CEC multi-bit error (MBE) signalling 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 casue an MBE.
Cause / Action:
Cause: The CEC failed MBE detection. Action: Contact HP support personnel to troubleshoot the problem
Automated Recovery: None
Event Generation Threshold: 1 occurrence

Event 309

Severity: MAJOR
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:
Cause: The CEC failed SBE detection. Action: Contact HP support personnel to troubleshoot the problem
Automated Recovery: None
Event Generation Threshold: 1 occurrence

Event 310

Severity: MAJOR
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:
Cause: The CEC failed SBE detection. Action: Contact HP support personnel to troubleshoot the problem
Automated Recovery: None
Event Generation Threshold: 1 occurrence

Event 311

Severity: MAJOR
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:
Cause: FW detected memory errors below 1MB. Action: 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 312

Severity: MAJOR
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:
Cause: The address logged in the CEC doesn't map to a memory rank, possibly due to a software error or NVM corruption Action: Contact HP support to trouble shoot the problem.
Automated Recovery: None
Event Generation Threshold: 1 occurrence

Event 313

Severity: MAJOR
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 data field contains the error status of the CEC.
Cause / Action:
Cause: Software Error or CEC error Action: Contact HP support to troubleshoot the problem
Automated Recovery: None
Event Generation Threshold: 1 occurrence

Event 314

Severity: MAJOR
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 data field contains the error status of the CEC.
Cause / Action:
Cause Software Error or CEC error Action: Contact HP support to troubleshoot the problem
Automated Recovery: None
Event Generation Threshold: 1 occurrence

Event 315

Severity: MAJOR
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:
Cause Software error or CEC error Action: Contact HP support to troubleshoot the problem
Automated Recovery: None
Event Generation Threshold: 1 occurrence

Event 316

Severity: MAJOR
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:
Cause A required DIMM is not loaded in order to allow for proper operation of the DIMM specified in the physical location. Action: Refer to the user's manual for Memory loading instructions.
Automated Recovery: None
Event Generation Threshold: 1 occurrence

Event 317

Severity: MAJOR
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:
Cause Corrupt NVM or System firmware failure Action: Contact HP support to troubleshoot the problem.
Automated Recovery: None
Event Generation Threshold: 1 occurrence

Event 318

Severity: FATAL
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:
Cause1: DIMM(s) that map into low memory have errors on them. Action1: Contact HP support to troubleshoot the problem. Cause2: SFW is outdated. Action2: Update SFW.
Automated Recovery: None
Event Generation Threshold: 1 occurrence

Event 319

Severity: MAJOR
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:
Cause1: The register within the chipset went bad. Action1: Contact HP support to troubleshoot the problem Cause2: Internal SFW error. Action2: Update to most recent SFW.
Automated Recovery: None
Event Generation Threshold: 1 occurrence

Event 320

Severity: FATAL
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 321

Severity: FATAL
Event Summary: No memory found
Event Class: System
Problem Description:
FW could not continue because there are no valid memory ranks loaded.
Cause / Action:
Cause FW found memory, but it could not find a correctly loaded rank. Action: Before this event is sent, FW will output which ranks it is deallocating and why. Review the preceeding events and refer to the users manual to correct the memory loading.
Automated Recovery: None
Event Generation Threshold: 1 occurrence

Event 322

Severity: FATAL
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:
Cause FW found memory errors during selftest, but could not deallocate the page because the PDT is disabled. Action: Reenable the PDT by clearing NVM
Automated Recovery: None
Event Generation Threshold: 1 occurrence

Event 323

Severity: MAJOR
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:
Cause Informational event indicating that FW will not use the PDT this boot. Action: None if user does not want to use the PDT, otherwise, clear NVM
Automated Recovery: None
Event Generation Threshold: 1 occurrence

Event 324

Severity: MAJOR
Event Summary: Error adding entry to PDT
Event Class: System
Problem Description:
Error writing entry into the PDT.
Cause / Action:
Cause NVM write error. Action: Contact HP support personnel to troubleshoot the problem.
Automated Recovery: None
Event Generation Threshold: 1 occurrence

Event 325

Severity: CRITICAL
Event Summary: Cannot add PDT entry--PDT full
Event Class: System
Problem Description:
The memory page deallocation table (PDT) is full.
Cause / Action:
Cause Excessive memory errors Action: Contact HP Support personnel to troubleshoot the problem
Automated Recovery: None
Event Generation Threshold: 1 occurrence

Event 326

Severity: MAJOR
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:
Cause Memory FW was unable to save or restore the original error configuration. Action: If this is seen, update SFW.
Automated Recovery: None
Event Generation Threshold: 1 occurrence

Event 327

Severity: MAJOR
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:
Cause The rank structure that corresponds to the rankID in the data field could not be found in the Rank table, possibly due to NVM corruption. Action: Contact HP support to troubleshoot the problem.
Automated Recovery: None
Event Generation Threshold: 1 occurrence

Event 329

Severity: MAJOR
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:
Cause: An error other than a memory error occurred during the memory test Action: Contact HP support to troubleshoot the problem
Automated Recovery: None
Event Generation Threshold: 1 occurrence

Event 330

Severity: MAJOR
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:
Cause: The forward progress bits are invalid. Action: Upgrade to latest system firmware, or contact HP support to troubleshoot the problem.
Automated Recovery: None
Event Generation Threshold: 1 occurrence

Event 331

Severity: MAJOR
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:
Cause: Non-memory errors were detected during the memory test that FW doesn't know how to handle. Action: Update to the latest SFW Action: Contact HP support to troubleshoot the problem.
Automated Recovery: None
Event Generation Threshold: 1 occurrence

Event 332

Severity: MAJOR
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:
Cause: The memory test summary word is invalid Action: Update to the latest SFW. Action: Contact HP support to troubleshoot the problem.
Automated Recovery: None
Event Generation Threshold: 1 occurrence

Event 333

Severity: MAJOR
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:
Cause: Control bit to skip DIMM distribution check is set. Action: Clear NVM Action: Update PDC Action: Contact HP support to troubleshoot the problem
Automated Recovery: None
Event Generation Threshold: 1 occurrence

Event 334

Severity: MAJOR
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:
Cause: Control bit to skip DIMM loading order check is set. Action: Clear NVM Action: Update PDC Action: Contact HP support to troubleshoot the problem
Automated Recovery: None
Event Generation Threshold: 1 occurrence

Event 335

Severity: MAJOR
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 continously. This bit should only be done in the factory and not in the field.
Cause / Action:
Cause: Control bit to loop on destructive memory test is set. Action: Clear NVM Action: Update PDC Action: Contact HP support to troubleshoot the problem
Automated Recovery: None
Event Generation Threshold: 1 occurrence

Event 336

Severity: MAJOR
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:
Cause: Control bit to skip DIMM set check is set. Action: Clear NVM Action: Update PDC Action: Contact HP support to troubleshoot the problem
Automated Recovery: None
Event Generation Threshold: 1 occurrence

Event 337

Severity: MAJOR
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:
Cause: Control bit to skip DIMM SPD check is set. Action: Clear NVM Action: Update PDC Action: Contact HP support to troubleshoot the problem
Automated Recovery: None
Event Generation Threshold: 1 occurrence

Event 340

Severity: MAJOR
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 341

Severity: MAJOR
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 342

Severity: MAJOR
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 343

Severity: FATAL
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 344

Severity: MAJOR
Event Summary: SAL_CHECK failed for an unknown reason
Event Class: System
Problem Description:
The handler for SAL_CHECK has failed for an unknow 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 345

Severity: MAJOR
Event Summary: SAL_INIT failed for an unknown reason
Event Class: System
Problem Description:
The handler for SAL_INIT has failed for an unknow 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 347

Severity: MAJOR
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 348

Severity: MAJOR
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 349

Severity: CRITICAL
Event Summary: Firmware is adding a DEGRADED cpu node to the device tree.
Event Class: System
Problem Description:
Firmware is adding a device tree node for a CPU that is degraded in functionality. The cpu should not be trused.
Cause / Action:
A CPU that is not fully functional is installed in the cell board. Replace.
Automated Recovery: None
Event Generation Threshold: 1 occurrence

Event 350

Severity: CRITICAL
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 resource is unavailable.
Automated Recovery: None
Event Generation Threshold: 1 occurrence

Event 351

Severity: CRITICAL
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 352

Severity: CRITICAL
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 353

Severity: CRITICAL
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 354

Severity: FATAL
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 355

Severity: CRITICAL
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 356

Severity: CRITICAL
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 357

Severity: FATAL
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 358

Severity: CRITICAL
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 359

Severity: CRITICAL
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 360

Severity: CRITICAL
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 361

Severity: CRITICAL
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 362

Severity: CRITICAL
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 363

Severity: FATAL
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 364

Severity: FATAL
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 365

Severity: CRITICAL
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 366

Severity: FATAL
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 367

Severity: FATAL
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 368

Severity: CRITICAL
Event Summary: A required piece of PDH bus hardware cannot be contacted.
Event Class: System
Problem Description:
A required piece 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 372

Severity: MAJOR
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 373

Severity: CRITICAL
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 374

Severity: CRITICAL
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 375

Severity: CRITICAL
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 376

Severity: FATAL
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 377

Severity: FATAL
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 378

Severity: FATAL
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 379

Severity: FATAL
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 380

Severity: CRITICAL
Event Summary: Error was encountered when initializing the LBA.
Event Class: System
Problem Description:
An error was encountered when initiating the rope number specified in the data field.
Cause / Action:
Replace the bad hardware.
Automated Recovery: None
Event Generation Threshold: 1 occurrence

Event 381

Severity: MAJOR
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 382

Severity: CRITICAL
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 383

Severity: CRITICAL
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 384

Severity: CRITICAL
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 385

Severity: FATAL
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 386

Severity: FATAL
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 387

Severity: FATAL
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 388

Severity: FATAL
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 389

Severity: FATAL
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 392

Severity: CRITICAL
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 393

Severity: MAJOR
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 394

Severity: MAJOR
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 395

Severity: CRITICAL
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 396

Severity: MAJOR
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 397

Severity: CRITICAL
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 398

Severity: CRITICAL
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 399

Severity: CRITICAL
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 400

Severity: CRITICAL
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 401

Severity: CRITICAL
Event Summary: A FATAL resource could not be found or is unusable
Event Class: System
Problem Description:
A FATAL resource that is required early in the initialization process either could not be found, or was unusable. The specific resource 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 402

Severity: FATAL
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 405

Severity: CRITICAL
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 407

Severity: MAJOR
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 408

Severity: MAJOR
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 409

Severity: MAJOR
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 410

Severity: CRITICAL
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 411

Severity: CRITICAL
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 corrpt.
Cause / Action:
Band NVRAM/ reinitialize.
Automated Recovery: None
Event Generation Threshold: 1 occurrence

Event 412

Severity: CRITICAL
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 413

Severity: CRITICAL
Event Summary: An error was encountered communicating with utilities during PD render.
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 414

Severity: FATAL
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 415

Severity: MAJOR
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 416

Severity: CRITICAL
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 417

Severity: CRITICAL
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 418

Severity: CRITICAL
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 419

Severity: MAJOR
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 420

Severity: CRITICAL
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 421

Severity: MAJOR
Event Summary: Copying memory test code failed.
Event Class: System
Problem Description:
This event is unused
Cause / Action:
Cause: Memory test code located in main memory has been corrupted Action: Contact HP support personnel to troubleshoot the problem
Automated Recovery: None
Event Generation Threshold: 1 occurrence

Event 423

Severity: CRITICAL
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 CRITICAL problem.
Cause / Action:
Verify that the complex profile is correct and reset the partition.
Automated Recovery: None
Event Generation Threshold: 1 occurrence

Event 424

Severity: CRITICAL
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 occure 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 426

Severity: CRITICAL
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 427

Severity: CRITICAL
Event Summary: This indicates that it does not have any access to the PD.
Event Class: System
Problem Description:
This chassis code indicates that thecell 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 428

Severity: CRITICAL
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 429

Severity: CRITICAL
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 434

Severity: CRITICAL
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 437

Severity: FATAL
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 439

Severity: MAJOR
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 440

Severity: MAJOR
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 441

Severity: MAJOR
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 442

Severity: MAJOR
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 443

Severity: MAJOR
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 444

Severity: MAJOR
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 445

Severity: MAJOR
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 446

Severity: MAJOR
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 447

Severity: MAJOR
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 448

Severity: MAJOR
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 449

Severity: MAJOR
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 450

Severity: MAJOR
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 451

Severity: MAJOR
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 452

Severity: MAJOR
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 453

Severity: FATAL
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 455

Severity: FATAL
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 456

Severity: FATAL
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 457

Severity: MAJOR
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 458

Severity: MAJOR
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 459

Severity: FATAL
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 461

Severity: MAJOR
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 462

Severity: FATAL
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 463

Severity: FATAL
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 464

Severity: FATAL
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 465

Severity: FATAL
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 466

Severity: FATAL
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 467

Severity: FATAL
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 468

Severity: FATAL
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 469

Severity: FATAL
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 470

Severity: MAJOR
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 471

Severity: FATAL
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 472

Severity: MAJOR
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 473

Severity: MAJOR
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 474

Severity: MAJOR
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 476

Severity: CRITICAL
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 481

Severity: FATAL
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 482

Severity: FATAL
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 483

Severity: MAJOR
Event Summary: processor steppings are not equal
Event Class: System
Problem Description:
Processors with different steppings 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 484

Severity: MAJOR
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 485

Severity: FATAL
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 487

Severity: MAJOR
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 488

Severity: MAJOR
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 489

Severity: MAJOR
Event Summary: PAL A was not executed - HALT
Event Class: System
Problem Description:
PAL_A has not been executed and control is being trasnferred back to SAL_B.
Cause / Action:
No Action.
Automated Recovery: None
Event Generation Threshold: 1 occurrence

Event 490

Severity: FATAL
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 491

Severity: MAJOR
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 492

Severity: MAJOR
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 493

Severity: MAJOR
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 494

Severity: MAJOR
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 495

Severity: MAJOR
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 496

Severity: MAJOR
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 497

Severity: MAJOR
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 498

Severity: MAJOR
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 499

Severity: FATAL
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 500

Severity: FATAL
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 501

Severity: FATAL
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 502

Severity: FATAL
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 503

Severity: MAJOR
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 504

Severity: CRITICAL
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 505

Severity: CRITICAL
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 506

Severity: CRITICAL
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 507

Severity: CRITICAL
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 508

Severity: FATAL
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 509

Severity: MAJOR
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 510

Severity: MAJOR
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 511

Severity: MAJOR
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 512

Severity: MAJOR
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 513

Severity: FATAL
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 515

Severity: CRITICAL
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 516

Severity: MAJOR
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 518

Severity: MAJOR
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 520

Severity: FATAL
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 521

Severity: CRITICAL
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 522

Severity: MAJOR
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 523

Severity: MAJOR
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 524

Severity: FATAL
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 525

Severity: MAJOR
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 526

Severity: FATAL
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 527

Severity: CRITICAL
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 528

Severity: CRITICAL
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 530

Severity: MAJOR
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 531

Severity: CRITICAL
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 532

Severity: CRITICAL
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 533

Severity: CRITICAL
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 535

Severity: CRITICAL
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 536

Severity: CRITICAL
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 537

Severity: CRITICAL
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 539

Severity: CRITICAL
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 540

Severity: CRITICAL
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 541

Severity: CRITICAL
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 542

Severity: CRITICAL
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 543

Severity: CRITICAL
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 544

Severity: FATAL
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 546

Severity: CRITICAL
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 547

Severity: MAJOR
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 548

Severity: CRITICAL
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 549

Severity: MAJOR
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 550

Severity: MAJOR
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 551

Severity: MAJOR
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 552

Severity: MAJOR
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 553

Severity: MAJOR
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 554

Severity: MAJOR
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 555

Severity: MAJOR
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 556

Severity: MAJOR
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 557

Severity: CRITICAL
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 559

Severity: CRITICAL
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 560

Severity: CRITICAL
Event Summary: This means that the PD monarch timed out.
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 563

Severity: CRITICAL
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 564

Severity: CRITICAL
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 565

Severity: CRITICAL
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 566

Severity: CRITICAL
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 570

Severity: FATAL
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 573

Severity: MAJOR
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 574

Severity: MAJOR
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 576

Severity: FATAL
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 577

Severity: MAJOR
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 578

Severity: FATAL
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 579

Severity: FATAL
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 580

Severity: MAJOR
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 581

Severity: MAJOR
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 582

Severity: MAJOR
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 583

Severity: MAJOR
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 584

Severity: MAJOR
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 585

Severity: MAJOR
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 586

Severity: MAJOR
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 587

Severity: MAJOR
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 588

Severity: MAJOR
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 589

Severity: CRITICAL
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 590

Severity: CRITICAL
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 591

Severity: MAJOR
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 592

Severity: MAJOR
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:
Cause: Memory extender and baseboard are incompatible Action: Contact HP support to troubleshoot the problem
Automated Recovery: None
Event Generation Threshold: 1 occurrence

Event 593

Severity: FATAL
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 594

Severity: CRITICAL
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 595

Severity: MAJOR
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 596

Severity: CRITICAL
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 597

Severity: MAJOR
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 598

Severity: CRITICAL
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 599

Severity: CRITICAL
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 600

Severity: MAJOR
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 601

Severity: MAJOR
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 fied: 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 602

Severity: FATAL
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 603

Severity: FATAL
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 604

Severity: FATAL
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 605

Severity: FATAL
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 606

Severity: CRITICAL
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 607

Severity: FATAL
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 608

Severity: FATAL
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 609

Severity: FATAL
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 610

Severity: MAJOR
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 611

Severity: MAJOR
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 612

Severity: MAJOR
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 613

Severity: CRITICAL
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 614

Severity: MAJOR
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 615

Severity: FATAL
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 616

Severity: CRITICAL
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 617

Severity: CRITICAL
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 618

Severity: CRITICAL
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 619

Severity: CRITICAL
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 resource 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 620

Severity: CRITICAL
Event Summary: A non-FATAL 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 622

Severity: MAJOR
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 624

Severity: CRITICAL
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 625

Severity: MAJOR
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 626

Severity: MAJOR
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 627

Severity: MAJOR
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 628

Severity: MAJOR
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 629

Severity: MAJOR
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 630

Severity: MAJOR
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 631

Severity: MAJOR
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 632

Severity: CRITICAL
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 633

Severity: MAJOR
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 Sytem 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 634

Severity: MAJOR
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 635

Severity: CRITICAL
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 636

Severity: CRITICAL
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 637

Severity: MAJOR
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 638

Severity: CRITICAL
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 639

Severity: CRITICAL
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 640

Severity: CRITICAL
Event Summary: A cpu is being over clocked
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 641

Severity: FATAL
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 642

Severity: FATAL
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 643

Severity: FATAL
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 (Managability 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 645

Severity: MAJOR
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 646

Severity: FATAL
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 preceeding the timeout for clues to the root cause of the partition bei! ng unresponsive.
Automated Recovery: None
Event Generation Threshold: 1 occurrence

Event 647

Severity: MAJOR
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 649

Severity: MAJOR
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 651

Severity: FATAL
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 652

Severity: FATAL
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 653

Severity: MAJOR
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 654

Severity: MAJOR
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 655

Severity: MAJOR
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 657

Severity: MAJOR
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 659

Severity: MAJOR
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 660

Severity: FATAL
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 661

Severity: FATAL
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 662

Severity: MAJOR
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 670

Severity: FATAL
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 671

Severity: FATAL
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 672

Severity: MAJOR
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 673

Severity: MAJOR
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 675

Severity: FATAL
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 FATAL level. Action: Shutdown and power off the system. Correct air temperature problem.
Automated Recovery: None
Event Generation Threshold: 1 occurrence

Event 676

Severity: MAJOR
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 677

Severity: MAJOR
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 678

Severity: MAJOR
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 680

Severity: MAJOR
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 681

Severity: FATAL
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 682

Severity: FATAL
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 683

Severity: MAJOR
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 684

Severity: FATAL
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 685

Severity: FATAL
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 686

Severity: MAJOR
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 687

Severity: MAJOR
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 identify 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 688

Severity: MAJOR
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 identify 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 689

Severity: MAJOR
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 identify 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 690

Severity: FATAL
Event Summary: IO Power Board Over temperature
Event Class: System
Problem Description:
The Local Power Monitor of the named IO Chassis is reporting a Power Brick over temperature condition.
Cause / Action:
Cause: The ambient air is too warm. Action: Check the Error Log for other Over tempature 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 691

Severity: FATAL
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 692

Severity: MAJOR
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 693

Severity: MAJOR
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 can't 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 694

Severity: MAJOR
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 695

Severity: MAJOR
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 can't 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 696

Severity: MAJOR
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 697

Severity: MAJOR
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 698

Severity: MAJOR
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 identify 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 procedure. 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 699

Severity: FATAL
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 700

Severity: CRITICAL
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 701

Severity: MAJOR
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 707

Severity: FATAL
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 identified in the physical location data field and discovered that it did not recognize the revision as one that it has been qualified with. This is an unsupported configuration.
Cause / Action:
Update PDHC or MP FW
Automated Recovery: None
Event Generation Threshold: 1 occurrence

Event 708

Severity: CRITICAL
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 710

Severity: MAJOR
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 711

Severity: MAJOR
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 712

Severity: CRITICAL
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 713

Severity: MAJOR
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 contol 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 714

Severity: MAJOR
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 contol 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 715

Severity: MAJOR
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 716

Severity: MAJOR
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 717

Severity: CRITICAL
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 718

Severity: FATAL
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 719

Severity: FATAL
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 720

Severity: MAJOR
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 722

Severity: CRITICAL
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 723

Severity: CRITICAL
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 724

Severity: CRITICAL
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 725

Severity: MAJOR
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 726

Severity: CRITICAL
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 727

Severity: CRITICAL
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 728

Severity: MAJOR
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 729

Severity: MAJOR
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 731

Severity: MAJOR
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 732

Severity: FATAL
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 733

Severity: CRITICAL
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 734

Severity: MAJOR
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 735

Severity: MAJOR
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 736

Severity: MAJOR
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 737

Severity: MAJOR
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 738

Severity: CRITICAL
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 strucutres.
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 742

Severity: MAJOR
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.
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 743

Severity: FATAL
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 744

Severity: CRITICAL
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 745

Severity: MAJOR
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 753

Severity: MAJOR
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 754

Severity: FATAL
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 756

Severity: CRITICAL
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 760

Severity: FATAL
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 771

Severity: CRITICAL
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 772

Severity: CRITICAL
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 773

Severity: CRITICAL
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 774

Severity: MAJOR
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 775

Severity: CRITICAL
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 776

Severity: MAJOR
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 777

Severity: MAJOR
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 778

Severity: MAJOR
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 779

Severity: CRITICAL
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 780

Severity: CRITICAL
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 781

Severity: CRITICAL
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 782

Severity: MAJOR
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 th 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 783

Severity: MAJOR
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 784

Severity: CRITICAL
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 785

Severity: MAJOR
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 786

Severity: CRITICAL
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 787

Severity: MAJOR
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 788

Severity: MAJOR
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 789

Severity: CRITICAL
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 790

Severity: CRITICAL
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 791

Severity: MAJOR
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 792

Severity: CRITICAL
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 793

Severity: CRITICAL
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 808

Severity: CRITICAL
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 810

Severity: MAJOR
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 816

Severity: MAJOR
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 817

Severity: MAJOR
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 818

Severity: MAJOR
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 822

Severity: CRITICAL
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 824

Severity: MAJOR
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 825

Severity: MAJOR
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 826

Severity: MAJOR
Event Summary: On Line Delete operation was begun but firmware could not find a cell that can be deleted.
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 827

Severity: FATAL
Event Summary: The bulk power system is above its current capacity.
Event Class: System
Problem Description:
The bulk power supply is over current
Cause / Action:
N/A
Automated Recovery: None
Event Generation Threshold: 1 occurrence

Event 828

Severity: MAJOR
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 over temperature condition
Automated Recovery: None
Event Generation Threshold: 1 occurrence

Event 829

Severity: CRITICAL
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 830

Severity: MAJOR
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 831

Severity: CRITICAL
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 832

Severity: MAJOR
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 833

Severity: CRITICAL
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 834

Severity: MAJOR
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 837

Severity: CRITICAL
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 838

Severity: MAJOR
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 resetting itself.
Automated Recovery: None
Event Generation Threshold: 1 occurrence

Event 839

Severity: MAJOR
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 840

Severity: MAJOR
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 841

Severity: MAJOR
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 842

Severity: MAJOR
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 843

Severity: MAJOR
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 844

Severity: MAJOR
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 845

Severity: CRITICAL
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 846

Severity: CRITICAL
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 848

Severity: MAJOR
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.
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 849

Severity: MAJOR
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 851

Severity: MAJOR
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 852

Severity: MAJOR
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 853

Severity: MAJOR
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 854

Severity: MAJOR
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
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 856

Severity: MAJOR
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 857

Severity: CRITICAL
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 858

Severity: MAJOR
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 860

Severity: MAJOR
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 861

Severity: CRITICAL
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 862

Severity: MAJOR
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 864

Severity: MAJOR
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.
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 865

Severity: MAJOR
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 866

Severity: CRITICAL
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 867

Severity: CRITICAL
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 868

Severity: CRITICAL
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 869

Severity: MAJOR
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 870

Severity: CRITICAL
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 871

Severity: CRITICAL
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 furthertroubleshooting.
Automated Recovery: None
Event Generation Threshold: 1 occurrence

Event 872

Severity: MAJOR
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 873

Severity: CRITICAL
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 874

Severity: CRITICAL
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 875

Severity: CRITICAL
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 876

Severity: MAJOR
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 877

Severity: MAJOR
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 878

Severity: MAJOR
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 879

Severity: MAJOR
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 880

Severity: MAJOR
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 881

Severity: MAJOR
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 882

Severity: MAJOR
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 883

Severity: CRITICAL
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 884

Severity: MAJOR
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.
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 885

Severity: MAJOR
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 886

Severity: MAJOR
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 887

Severity: MAJOR
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 incompatibility 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 888

Severity: CRITICAL
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 889

Severity: CRITICAL
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 indicate the cause of the failure, then contact the HP Support Personnel for further troubleshooting.
Automated Recovery: None
Event Generation Threshold: 1 occurrence

Event 890

Severity: MAJOR
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:
Cause: SFW detected a failing DIMM Action: Replace the DIMM flagged by SFW
Automated Recovery: None
Event Generation Threshold: 1 occurrence

Event 891

Severity: CRITICAL
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 892

Severity: CRITICAL
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 893

Severity: CRITICAL
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 894

Severity: MAJOR
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 895

Severity: MAJOR
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 896

Severity: MAJOR
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 897

Severity: MAJOR
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 898

Severity: MAJOR
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 899

Severity: MAJOR
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 900

Severity: MAJOR
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 901

Severity: MAJOR
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 902

Severity: MAJOR
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 903

Severity: MAJOR
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 904

Severity: MAJOR
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 (ie 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 905

Severity: MAJOR
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 (ie 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 906

Severity: MAJOR
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 908

Severity: MAJOR
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 909

Severity: MAJOR
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 910

Severity: MAJOR
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 911

Severity: MAJOR
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 912

Severity: MAJOR
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 913

Severity: MAJOR
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 914

Severity: CRITICAL
Event Summary: Partition about to be reset because PDC couldn't get address to a structure
Event Class: System
Problem Description:
PDC was trying to move the cell monarchs on each of the non-core cells into the Dispatcher, but in order to do that, the PD monarch needs to be able to read the CPU number of the cell monarch on each of the non-core cells, which is kept in a data structure on each of the cells. PDC was unable to get the address to the CELL_CPU_STATE structure in PDH memory in a cell in the partition. The data field is the error return status from the PDC function called PdhGetHCellStructAddr().
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 replace backplane or cells. 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 passed invalid arguments to try to get the address to the data structure. Action3: Upgrade PDC if there is a fix for this problem.
Automated Recovery: None
Event Generation Threshold: 1 occurrence

Event 915

Severity: CRITICAL
Event Summary: Resetting a partition because a CPU didn't complete the task it was awakened for
Event Class: System
Problem Description:
PDC is about to reset the partition 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 the error return status from the PDC function CheckSingleSlave().
Cause / Action:
Cause1: Hardware problem with the Mako chip, Concorde chip, or PDH flash. Action1: Troubleshoot the cell and/or replace it.
Automated Recovery: None
Event Generation Threshold: 1 occurrence

Event 916

Severity: CRITICAL
Event Summary: Resetting partition because PDC couldn't determine relocated address of code
Event Class: System
Problem Description:
PDC is about to reset the partition because it is unable to determine the GNI address for the CpuFpSet() function for one or more of the cells in the partition. The data field contains the error return status from 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 replace backplane or cells. 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: Upgrade PDC if there is a fix for this problem.
Automated Recovery: None
Event Generation Threshold: 1 occurrence

Event 917

Severity: CRITICAL
Event Summary: Resetting partition because a CPU was unable to change its CPU FP state
Event Class: System
Problem Description:
PDC is about to reset the partition because one or more of the processors were unable to successfully modify their CPU FP State (aka their PST state). The data field contains the error return status from the CpuFpSet() function.
Cause / Action:
Cause1: Hardware problem with PDH memory, Concorde chip, or the Mako chip. Action1: Troubleshoot the cell and/or replace it. Cause2: PDC bug in which passed invalid arguments. Action2: Upgrade PDC if there is a fix.
Automated Recovery: None
Event Generation Threshold: 1 occurrence

Event 918

Severity: MAJOR
Event Summary: CPU Dual Core Initialization Failed
Event Class: System
Problem Description:
CPU Dual Core Initialization Failed
Cause / Action:
Attempt Reboot, Replace Processor
Automated Recovery: None
Event Generation Threshold: 1 occurrence

Event 919

Severity: MAJOR
Event Summary: Second CPU in Pair has been disabled
Event Class: System
Problem Description:
None
Cause / Action:
The second CPU in the Dual Core has been deconfigured as a result of the first core being deconfigured. Investigate the cause of the first core being deconfigured
Automated Recovery: None
Event Generation Threshold: 1 occurrence

Event 920

Severity: MAJOR
Event Summary: Virtualzing Dual Core Registers Failed
Event Class: System
Problem Description:
None
Cause / Action:
Reboot, if problem continues, replace CPU Module.
Automated Recovery: None
Event Generation Threshold: 1 occurrence

Event 921

Severity: MAJOR
Event Summary: Virtualizing Dual Core Interposer has failed
Event Class: System
Problem Description:
None
Cause / Action:
Virtualizing the Dual Core Interposer has failed. Reboot, if problem continues, Replace CPU module.
Automated Recovery: None
Event Generation Threshold: 1 occurrence

Event 922

Severity: MAJOR
Event Summary: Install PMI Handler Failed
Event Class: System
Problem Description:
None
Cause / Action:
Reboot, if problem continues replace CPU Module
Automated Recovery: None
Event Generation Threshold: 1 occurrence

Event 923

Severity: FATAL
Event Summary: Cell failed compatibility checks.
Event Class: System
Problem Description:
Cell and or CPUs have failed compatibility checks.
Cause / Action:
Cause - CPUs are incompatible with each other, or the cell front side bus frequency is incompatible with the CPUs. Action - Correct the problem.
Automated Recovery: None
Event Generation Threshold: 1 occurrence

Event 924

Severity: FATAL
Event Summary: PDH space not available after release from reset.
Event Class: System
Problem Description:
PDH space not available after release from reset.
Cause / Action:
Cause - Hardware failure. Action - Fix the hardware, cell or PDH riser.
Automated Recovery: None
Event Generation Threshold: 1 occurrence

Event 925

Severity: FATAL
Event Summary: MPON failed to release.
Event Class: System
Problem Description:
MPON failed to release.
Cause / Action:
Cause - Hardware failure. Action - Fix the hardware, cell or pdh riser.
Automated Recovery: None
Event Generation Threshold: 1 occurrence

Event 926

Severity: FATAL
Event Summary: Dillon failed to reset.
Event Class: System
Problem Description:
Dillon failed to reset.
Cause / Action:
Cause - Hardware failure. Action - Fix the hardware, pdh riser or cell.
Automated Recovery: None
Event Generation Threshold: 1 occurrence

Event 927

Severity: FATAL
Event Summary: DMD clock is not running.
Event Class: System
Problem Description:
DMD clock is not running.
Cause / Action:
Cause - Hardware problem Action - Fix the hardware, pdh riser or cell board.
Automated Recovery: None
Event Generation Threshold: 1 occurrence

Event 928

Severity: CRITICAL
Event Summary: All cpus on the Cell are scheduled to be deconfigured
Event Class: System
Problem Description:
All possible CPUs on a cell have been scheduled for deconfiguration.
Cause / Action:
All cpus on the cell have been scheduled for deconfiguration. On the next reset, the cell will no longer be operational; system firmware will deconfigure all the cpus and this cell will not be part of a partition. This action is not recommended. To recover, the NVRAM on the PDH card must be cleared, the cell power cycled, and defaults restored from disk.
Automated Recovery: None
Event Generation Threshold: 1 occurrence

Event 929

Severity: CRITICAL
Event Summary: A read error occurred while dumping the routing registers
Event Class: System
Problem Description:
A read error occurred while dumping the XBC port routing registers during boot. This cell will attempt fabricless boot. Data field: (XBC port << 48) | (XBC num << 32) | error status reg
Cause / Action:
Cause: Fabric Read Error. Action: Check XBC, CC, links, etc.
Automated Recovery: None
Event Generation Threshold: 1 occurrence

Event 930

Severity: FATAL
Event Summary: Failed to disable the CC to CC link
Event Class: System
Problem Description:
After cell rendezvous for a 2 cell Medel, only one cell made it into the partition. Disabling the link failed. The cell will reset for reconfig. Data Field: return status
Cause / Action:
Failure to read or write Concorde CSRs.
Contact HP Support personnel to check the Check CC.
Automated Recovery: None
Event Generation Threshold: 1 occurrence

Event 931

Severity: MAJOR
Event Summary: Power has been removed from AC input A0.
Event Class: System
Problem Description:
Power is no longer being supplied to input A0 on the cabinet specified in the data field.
Cause / Action:
A power source has been removed from the chassis.
Automated Recovery: None
Event Generation Threshold: 1 occurrence

Event 932

Severity: MAJOR
Event Summary: Power has been removed from AC input A1.
Event Class: System
Problem Description:
Power is no longer being supplied to input A1 on the cabinet specified in the data field.
Cause / Action:
A power source has been removed from the chassis.
Automated Recovery: None
Event Generation Threshold: 1 occurrence

Event 933

Severity: MAJOR
Event Summary: Power has been removed from AC input B0.
Event Class: System
Problem Description:
Power is no longer being supplied to input B0 on the cabinet specified in the data field.
Cause / Action:
A power source has been removed from the chassis.
Automated Recovery: None
Event Generation Threshold: 1 occurrence

Event 934

Severity: MAJOR
Event Summary: Power has been removed from AC input B1.
Event Class: System
Problem Description:
Power is no longer being supplied to input B1 on the cabinet specified in the data field.
Cause / Action:
A power source has been removed from the chassis.
Automated Recovery: None
Event Generation Threshold: 1 occurrence

Event 935

Severity: MAJOR
Event Summary: Failed to disable the XIN link during a failed link init
Event Class: System
Problem Description:
Failed to disable the XIN link init CSR on a XBCless system. Cell will halt. Data field: return status (0 = SUCCESS, -1 = FAILURE), -1 is expected for this event.
Cause / Action:
Have your HP Support Representative check the Coherency Controller
Automated Recovery: None
Event Generation Threshold: 1 occurrence

Event 937

Severity: MAJOR
Event Summary: Error while reading the remote CC's XIN Error Mask register
Event Class: System
Problem Description:
Could not read the XIN error mask regisiter on the CC. Data Field: cell number and return status
Cause / Action:
CC access failure.
Contact HP Support personnel to check the CC.
Automated Recovery: None
Event Generation Threshold: 1 occurrence

Event 938

Severity: MAJOR
Event Summary: Error clearing the init packet received bit in the XIN error mask
Event Class: System
Problem Description:
Could not write the XIN error mask register on the CC. Data Field: cell number and return status
Cause / Action:
Cause: CC access failure.
PDC Reviewed alert level for SR - 9/6/03 CC.
Automated Recovery: None
Event Generation Threshold: 1 occurrence

Event 939

Severity: MAJOR
Event Summary: Failed to read the XBC's Port Status register
Event Class: System
Problem Description:
While testing link traveresability, a XBC CSR could not be read. Data Field: Port Number << 44 | XBC Number << 32 | return value
Cause / Action:
Cause: fabric access failure Action: Check XBC, Check CC, Check backplane
Automated Recovery: None
Event Generation Threshold: 1 occurrence

Event 941

Severity: CRITICAL
Event Summary: FW will not handoff to the OS_MCA handler for this MCA event
Event Class: System
Problem Description:
This means that the system FW MCA handler is not going to handoff to the OS_MCA handler.
Cause / Action:
The error logs should be retrieved from the EFI shell prompt.
Automated Recovery: None
Event Generation Threshold: 1 occurrence

Event 942

Severity: CRITICAL
Event Summary: The NVRAM block table maintained by System Firmware is corrupt
Event Class: System
Problem Description:
Unused
Cause / Action:
The NVRAM-based descriptor for System Firmware NVRAM blocks is corrupt.
Automated Recovery: None
Event Generation Threshold: 1 occurrence

Event 943

Severity: MAJOR
Event Summary: All CPUs were deconfigured and have now been reconfigured.
Event Class: System
Problem Description:
All CPUs have been determined to be manually deconfigured in NVM during boot. This may only happen when switching from single core CPU deconfiguration to multi-core CPU deconfiguration in product qualification testing. As a recovery, NVM settings have been changed to reconfigure all CPUs.
Cause / Action:
Cause: User test operational error. Action: Reboot system and update CPU configuration as desired.
Automated Recovery: None
Event Generation Threshold: 1 occurrence

Event 944

Severity: MAJOR
Event Summary: A failure has occurred trying to determine the number of CPU cores per module.
Event Class: System
Problem Description:
A failure has occurred trying to determine the number of CPU cores per module. Depending upon the situation, either the cell will be halted or the entire partition will be reset.
Cause / Action:
C1: Hardware failure with CPU, CC or cell board. A1: Contact HP Support to confirm the CPUs, CC, and cell board are functioning properly. Update PDC if a version is available to fix this problem.
Automated Recovery: None
Event Generation Threshold: 1 occurrence

Event 945

Severity: MAJOR
Event Summary: Couldn't read the topology from the XBC register
Event Class: System
Problem Description:
While writing the remote routing, the local XBC could not be accessed to determine the topology. Look for additional chassis codes to determine what will happen as a result of this failure. Data field: return status, either SUCCESS (0) or (-1)
Cause / Action:
Fabric Access Error
Contact HP Support personnel to check the XBC, Backplane, CC
Automated Recovery: None
Event Generation Threshold: 1 occurrence

Event 947

Severity: MAJOR
Event Summary: Failed to read the XBC CSR that contains the number of failed links
Event Class: System
Problem Description:
Could not read the XBC register that contains the number of links that are currently broken on the complex. Data Field: (XBC Num << 32) | PDC return status
Cause / Action:
Fabric Access Failure
Contact HP Support personnel to analyze the fabric.
Automated Recovery: None
Event Generation Threshold: 1 occurrence

Event 948

Severity: MAJOR
Event Summary: Failed to read the XBC CSR that contains the number of failed links
Event Class: System
Problem Description:
Could not read the XBC register that contains the number of links that are currently broken on the complex. Data Field: (XBC Num << 32) | PDC return status
Cause / Action:
Fabric Access Failure
Contact HP Support personnel to check XBC, Backplane, CC, look for additional chassis codes to describe the problem.
Automated Recovery: None
Event Generation Threshold: 1 occurrence

Event 949

Severity: MAJOR
Event Summary: Failed to write the XBC CSR that contains the number of failed links
Event Class: System
Problem Description:
Could not write the XBC register that contains the number of links that are currently broken on the complex. Data Field: (XBC Num << 32) | PDC return status
Cause / Action:
Fabric Access Failure
Contact HP Support personnel to check XBC, Backplane, CC, look for additional chassis codes to describe the problem.
Automated Recovery: None
Event Generation Threshold: 1 occurrence

Event 952

Severity: CRITICAL
Event Summary: This cell encountered too many broken crossbar links
Event Class: System
Problem Description:
Too many broken crossbar links were found. This cell will have no connectivity to other cells in the complex. It will attempt a fabricless boot, except in a few configurations. Data Field: (XBC Num << 32) | number of broken links
Cause / Action:
Cause: Broken fabric links, Action: Check XBC, Backplane, Flex Cables, look for additional chassis codes to describe the problem.
Automated Recovery: None
Event Generation Threshold: 1 occurrence

Event 958

Severity: MAJOR
Event Summary: Failed to do a broadcast write to the XBC Remote Routing registers
Event Class: System
Problem Description:
Failed to complete a broadcast write to an XBC. Data Field: (XBC Num << 32) | PDC return status
Cause / Action:
Fabric Access Failure
Contact HP Support personnel to check the XBC, Backplane, CC. Look for additional chassis codes to describe the problem.
Automated Recovery: None
Event Generation Threshold: 1 occurrence

Event 959

Severity: MAJOR
Event Summary: Failed to read a XBC Remote Routing register
Event Class: System
Problem Description:
Failed to complete a read to the built-in port of a XBC. Data Field: (XBC Num << 32) | PDC return status
Cause / Action:
Fabric Access Failure
Contact HP Support personnel to check the XBC, Backplane, CC. Look for additional chassis codes to describe the problem.
Automated Recovery: None
Event Generation Threshold: 1 occurrence

Event 960

Severity: MAJOR
Event Summary: Failed to write a XBC Remote Routing register
Event Class: System
Problem Description:
Failed to complete a write to the local cell's port of the XBC. Data Field: (XBC Port << 44) | (XBC Num << 32) | PDC return status
Cause / Action:
Cause: Fabric Access Failure, Action: Check XBC, Backplane, CC. Look for additional chassis codes to describe the problem.
Automated Recovery: None
Event Generation Threshold: 1 occurrence

Event 961

Severity: CRITICAL
Event Summary: The link between the CC and SBA failed
Event Class: System
Problem Description:
The link between the CC and SBA failed meaning that I/O is not available to the reporting cell.
Cause / Action:
See other associated events for the root cause of the failure.
Automated Recovery: None
Event Generation Threshold: 1 occurrence

Event 962

Severity: CRITICAL
Event Summary: The SBA failed and the cell has no I/O
Event Class: System
Problem Description:
An error was detected in the SBA and the reporting cell has no I/O.
Cause / Action:
See other associated events that describe the root cause.
Automated Recovery: None
Event Generation Threshold: 1 occurrence

Event 963

Severity: CRITICAL
Event Summary: The system firmware had an error with the structured error handling mechanism.
Event Class: System
Problem Description:
The structured exception handling within the system firmware failed during I/O initialization.
Cause / Action:
Cause: Either there is an error in the system firmware or the system firmware has exhausted all resources. Action: Invalidate NVM or check for newer version of system firmware.
Automated Recovery: None
Event Generation Threshold: 1 occurrence

Event 964

Severity: CRITICAL
Event Summary: Not enough malloc resources for I/O structure error handling.
Event Class: System
Problem Description:
There is not enough malloc resources for the I/O structure exception handling. I/O on the reported cell is not available.
Cause / Action:
Either invalidate NVM or check for a new version of system firmware.
Automated Recovery: None
Event Generation Threshold: 1 occurrence

Event 965

Severity: CRITICAL
Event Summary: Unable to create entry for I/O structure error handling.
Event Class: System
Problem Description:
Error creating the structure for housing the I/O structured exception handling services and data. I/O is lost on the reporting cell.
Cause / Action:
This is a system firmware error, either invalidate NVM or check for a newer version of system firmware.
Automated Recovery: None
Event Generation Threshold: 1 occurrence

Event 966

Severity: CRITICAL
Event Summary: Unable to bind services for I/O structure exception handling.
Event Class: System
Problem Description:
Unable to bind the I/O structure exception handling to the internal data structures.
Cause / Action:
This is a system firmware error. Either reset NVM or check for a newer version of system firmware.
Automated Recovery: None
Event Generation Threshold: 1 occurrence

Event 967

Severity: CRITICAL
Event Summary: Error initializing the I/O structure exception handling services.
Event Class: System
Problem Description:
Error detected while initializing the I/O structure exception handling services.
Cause / Action:
This is a system firmware error. Either reset NVM or check for a newer version of system formware.
Automated Recovery: None
Event Generation Threshold: 1 occurrence

Event 968

Severity: CRITICAL
Event Summary: Error initializing structured I/O exception data structures.
Event Class: System
Problem Description:
Error initializing the I/O structure exception handling data structures.
Cause / Action:
This is a system formware error, there is a conflict with system resources. Either reset NVM or check for a newer version of system firmware.
Automated Recovery: None
Event Generation Threshold: 1 occurrence

Event 969

Severity: CRITICAL
Event Summary: The I/O exception context has an error.
Event Class: System
Problem Description:
The structured I/O exception handling data structures have an error. All I/O on the reporting cell is not available.
Cause / Action:
This is a system firmware error. Reset the system, invalidate NVM and reset the system, or check for a newer version of the system firmware.
Automated Recovery: None
Event Generation Threshold: 1 occurrence

Event 970

Severity: CRITICAL
Event Summary: Error creating the internal data and services for the SBA.
Event Class: System
Problem Description:
While setting up the internal SBA data and service an error was detected. All I/O for the reporting cell is not available.
Cause / Action:
This is a system firmware error. Reset the system; invalidate NVM and reset the system; or check for a newer version of system firmware.
Automated Recovery: None
Event Generation Threshold: 1 occurrence

Event 971

Severity: CRITICAL
Event Summary: Error attaching the series to the SBA internal data structures.
Event Class: System
Problem Description:
An error attaching firmware services to the internal structures was detected. All I/O on the reporting cell is not available.
Cause / Action:
This is a system firmware error. Reset the partition; invalidate NVM on the reporting cell and reset the system; or check for a newer version of system firmware.
Automated Recovery: None
Event Generation Threshold: 1 occurrence

Event 972

Severity: CRITICAL
Event Summary: Error initializing the intrenal SBA data and services.
Event Class: System
Problem Description:
System firmware detected an error initializing internal SBA data structures and services. This is usually an error with unavailable resources.
Cause / Action:
This is a system formware error. Reset the partition; invalidate NVM on the reporting cell and reset the partition; or check for newer system firmware.
Automated Recovery: None
Event Generation Threshold: 1 occurrence

Event 973

Severity: CRITICAL
Event Summary: The SBA type is unknown to the system firmware
Event Class: System
Problem Description:
The SBA type is unknown to the system firmware. The I/O on the reporting cell is not available.
Cause / Action:
This is either a system firmware error, or the wrong I/O is connected to the system. Validate the system recipe both firmware and hardware.
Automated Recovery: None
Event Generation Threshold: 1 occurrence

Event 974

Severity: MAJOR
Event Summary: An embedded I/O device is missing.
Event Class: System
Problem Description:
An expected I/O device cannot be detected by the system firmware.
Cause / Action:
Replaces the I/O card specified by the physical location.
Automated Recovery: None
Event Generation Threshold: 1 occurrence

Event 975

Severity: MAJOR
Event Summary: Fabric link route around failed because the route around port was bad
Event Class: System
Problem Description:
Too many broken links! The XBC port route around failed because the route-around port was bad too. Data field: (XBC port << 44) | (XBC num << 32) | port state
Cause / Action:
Cause: 2 or more XBC links are not routable.
Contact HP Support personnel to check the XBC, Flex Cables, Backplane, CCs, etc
Automated Recovery: None
Event Generation Threshold: 1 occurrence

Event 977

Severity: MAJOR
Event Summary: (warning) Outputted in MFG, when Memory SBE Seeding is enabled
Event Class: System
Problem Description:
This is a warning that the system is running in a degregated mode. It will only be emitted in MFG mode when Memory SBE Seeding is enabled. This is only for testing of SBE seeding for LAB and possibly MFG use ONLY. It should NEVER be seen in the field.
Cause / Action:
Cause: In MFG with Memory SBE Seeding control Flag (26) Enabled. Should never be seen at a customer's machine.
Automated Recovery: None
Event Generation Threshold: 1 occurrence

Event 978

Severity: CRITICAL
Event Summary: Failed to read the fabric topology information from the XBC
Event Class: System
Problem Description:
Read failure while writing the number of failed links to the XBC. Data Field: Return Status (SUCCESS = 0, FAILURE = -1)
Cause / Action:
Fabric Access Failure.
Contact HP Support personnel to analyze the fabric.
Automated Recovery: None
Event Generation Threshold: 1 occurrence

Event 981

Severity: CRITICAL
Event Summary: Could not disable the XIN link before a fabricless boot
Event Class: System
Problem Description:
Before attempting a fabricless boot, the cell's link to the fabric should be disabled to provide isolation and stability. The link could not be disabled, so the cell will halt.
Cause / Action:
Fabric Access Error.
Contact HP Support personnel to check the CC, Check XBC
Automated Recovery: None
Event Generation Threshold: 1 occurrence

Event 985

Severity: CRITICAL
Event Summary: Manual override of fatal stop boot condition
Event Class: System
Problem Description:
The user has manually bypassed a stop boot condition (caused by a fatal error during boot) and continued to boot an O/S. The system might experience unpredictable failures.
Cause / Action:
Cause: The user has initiated manual O/S boot despite the existence of a fatal error. Action: Correct the fatal error condition (see output of "INFO WARNING" EFI shell command), reboot the system, and then initiate O/S boot.
Automated Recovery: None
Event Generation Threshold: 1 occurrence

Event 986

Severity: MAJOR
Event Summary: Firmware unable to relocate VGA BIOS
Event Class: System
Problem Description:
Firmware was unable to relocate the VGA BIOS to the hardcoded VGA BIOS region in main memory (physical address range 0xc0000 - 0xdffff). VGA routing has been disabled by firmware. No VGA device will be accessible on this boot.
Cause / Action:
Cause: Most likely there is a permanent memory error in the VGA BIOS region (physical address 0xc0000 - 0xdffff). Action: Replace the DIMM causing the permanent memory error in the VGA BIOS region. The PDT reports which DIMM is causing errors in the physical address range 0xc0000 - 0xdffff.
Automated Recovery: None
Event Generation Threshold: 1 occurrence

Event 993

Severity: MAJOR
Event Summary: PDC could not access a complex profile
Event Class: System
Problem Description:
PDC could not access a complex profile. The cell will be reset. Data field contains the return status from the function that encountered the error.
Cause / Action:
Cause1: An error occurred which prevented the complex profiles from being distributed properly. Action1: Create and distribute a new complex profile using ParMgr on a functional partition in the complex. Restore the last complex profile using the "CC" command from the MP, then use ParMgr to create a new complex profile. Generate a genesis complex profile using the "CC" command from the MP, then use ParMgr to create a new complex profile. Cause2: A hardware problem exists with MP or PDHC hardware. Action2: Contact HP Support to confirm the MP and PDHC are functioning properly.
Automated Recovery: None
Event Generation Threshold: 1 occurrence

Event 994

Severity: MAJOR
Event Summary: No possible core cells were found in the configured set
Event Class: System
Problem Description:
Could not find a potential core cell for the partition in the configured set. This cell will reset for reconfiguration. Data Field: return status from failing function
Cause / Action:
Cause: most likely a configuration problem, Action: check to ensure a valid core cell is configured to be in the partition.
Automated Recovery: None
Event Generation Threshold: 1 occurrence

Event 995

Severity: MAJOR
Event Summary: Could not find a viable core cell in the partition
Event Class: System
Problem Description:
The potential core cell was not viable (ie. no core I/O, etc). This cell will reset for reconfiguration. Data Field: bit mask of cells that made the rendezvous set
Cause / Action:
Cause: Configuration error, fabric failure; the intended core cell failed during boot. Action: check partition configuration, check for failed cells.
Automated Recovery: None
Event Generation Threshold: 1 occurrence

Event 996

Severity: MAJOR
Event Summary: Could not find a viable core cell in the partition
Event Class: System
Problem Description:
The potential core cell was not viable (ie. no core I/O, etc). This cell will reset for reconfiguration. Data Field: bit mask of cells that made the rendezvous set
Cause / Action:
Cause: Configuration error, Mainbackplane failure, The intended core cell failed during boot. Action: Check partition configuration, Check for failed cells, as indicated by high-alert level IPMI events earlier in the boot.
Automated Recovery: None
Event Generation Threshold: 1 occurrence

Event 997

Severity: MAJOR
Event Summary: The core cell selected is not in the rendezvoused partition
Event Class: System
Problem Description:
The potential core cell did not rendezvous with the rest of the partition. This cell cannot talk to the selected core cell. This cell will reset for reconfiguration. Data Field: bit mask of cells that made the rendezvous set
Cause / Action:
Cause: Configuration error, main backplane failure; the intended core cell failed during boot. Action: check partition configuration, check for failed cells, check for additional chassis codes indicating more failure detail.
Automated Recovery: None
Event Generation Threshold: 1 occurrence

Event 998

Severity: MAJOR
Event Summary: The local cell is not viable
Event Class: System
Problem Description:
The local cell is disconnected from the rest of the system due to the main backplane configuration. While the partition is only configured to contain a single cell, the local cell is not a viable core cell. The cell will reset for reconfiguration. Data Field: bit mask of cells that made the rendezvous set
Cause / Action:
Cause: Configuration error, main backplane failure; no viable core cell. Action: check partition configuration, attach core I/O to local cell, make sure a viable core cell is configured within the partition.
Automated Recovery: None
Event Generation Threshold: 1 occurrence

Event 999

Severity: MAJOR
Event Summary: cell cannot reach the fabric, partition contains 3 or more cells
Event Class: System
Problem Description:
This cell has booted without the main backplane, probably due to prior main backplane errors. The partition it is in is configured with 3 or more cells. The combination of these two configurations is not allowed. The cell will reset for reconfiguration. Data Field: configured set
Cause / Action:
Cause: configuration combined with main backplane problems. Action: Contact HP Support to confirm the main backplane is functioning properly. Change the partition configuration to only contain 1 or 2 cells.
Automated Recovery: None
Event Generation Threshold: 1 occurrence

Event 1002

Severity: CRITICAL
Event Summary: The buffer size is too small for the XBC error log
Event Class: System
Problem Description:
The buffer size passed in to the XBC error logging routine through SAL_GET_STATE_INFO, SAL_CLEAR_STATE_INFO, or MCA logging is too small for the XBC error log Data field consists of: XBC number (32:43)
Cause / Action:
Caller of SAL state info calls did not correctly set up the buffer for the error logs
Automated Recovery: None
Event Generation Threshold: 1 occurrence

Event 1003

Severity: CRITICAL
Event Summary: System firmware was unable to clear an XBC error
Event Class: System
Problem Description:
System firmware was unable to clear an XBC error. The data field contains: XBC number (32:43) port number (44:55) error type (0:31)
Cause / Action:
The particular XBC and port could have a persistent error. Check flex cables
Automated Recovery: None
Event Generation Threshold: 1 occurrence

Event 1004

Severity: MAJOR
Event Summary: Firmware detected a possible Cabinet Power Timeout
Event Class: System
Problem Description:
System Firmware detected a possible timeout waiting for the other cabinet to power on. System firmware queried the utilities system to see what cells are installed. This indicated that cells are installed in the other cabinet but none are powered on. Firmware delayed fabric routing, waiting for the other cabinet cells to power on, but eventually timed out and went on.
Cause / Action:
Cells exist in both cabinets, but one of the cabinets has no cells powered on. If a 2 cabinet configuration is desired, shutdown any active partitions and power off both cabinets and then power them both on, including at least 1 cell in each cabinet. (Note: it is possible to get this event ID and have both cabinets powered on. In this event, no action is required.
Automated Recovery: None
Event Generation Threshold: 1 occurrence

Event 1005

Severity: CRITICAL
Event Summary: Fabric is unable to route the crossbar after multiple retry attempts
Event Class: System
Problem Description:
During fabric initialization, if a crossbar is found to be in an unexpected state, the number of retries is incremented. If the number of retries exceeds the maximum, then something is wrong and there is no way to initialize the fabric. Data field: number of retries (0:31) crossbar number (32:63)
Cause / Action:
Hardware problem. Possible bad XBC or Concorde
Automated Recovery: None
Event Generation Threshold: 1 occurrence

Event Details:
Examples:

Event 1007

Severity: MAJOR
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:
Cause: Make sure the GSP is connected and reset. Action: -
Automated Recovery: None
Event Generation Threshold: 1 occurrence

Event 1008

Severity: CRITICAL
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:
Cause: Utilities may be unavailable to update the profiles. Check the connections are reset. Action: -
Automated Recovery: None
Event Generation Threshold: 1 occurrence

Event 1009

Severity: CRITICAL
Event Summary: Error creating the pdh ioconfig node or attaching the service to it.
Event Class: System
Problem Description:
Firmware encountered an error when creating the ioconfig node as a child of the pdh node.
Cause / Action:
Cause: This is likely to be a symptom of an earlier problem, or the system is out of malloc space. Action: -
Automated Recovery: None
Event Generation Threshold: 1 occurrence

Event 1010

Severity: CRITICAL
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:
Cause: This is usually a symptom of an earlier problem. Check to be sure the pdh node was initialized into the tree correctly. Action: -
Automated Recovery: None
Event Generation Threshold: 1 occurrence

Event 1016

Severity: CRITICAL
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:
Cause: Reconfigure the PD so that all cells have processors running at the same speed. Action: -
Automated Recovery: None
Event Generation Threshold: 1 occurrence

Event 1019

Severity: FATAL
Event Summary: Coherency controller (CC) registers indicate a Deadlock Recovery Reset
Event Class: System
Problem Description:
Early in bootstrap, the coherency controller (CC) registers are checked for Deadlock Recovery Reset. This chassis code indicates that CC logs will be stored to NVRAM.
Cause / Action:
Cause: Coherency controller (CC) resources are deadlocked and the CC is resetting the cell. Action: Analyze the Deadlock Recovery logs (like MCA logs) to determine the cause of the failure.
Automated Recovery: None
Event Generation Threshold: 1 occurrence

Event 1020

Severity: CRITICAL
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:
Cause: The monarch cpu will be deconfigured. Action: -
Automated Recovery: None
Event Generation Threshold: 1 occurrence

Event 1030

Severity: CRITICAL
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:
Cause: Utilities may be unavailable to update the profiles. Check the connections are reset. Action: -
Automated Recovery: None
Event Generation Threshold: 1 occurrence

Event 1031

Severity: CRITICAL
Event Summary: The XBC SBE and LPE errors were not cleared properly
Event Class: System
Problem Description:
The XBC logged a SBE or LPE after they should have been cleared. Either the clear failed, or a new error was logged immediately. Data field: XBC number (32:43), port number (44:55), port status information (0:31)
Cause / Action:
Cause: the link generated a new error Action: check CC, check link Check logs for other errors. If error is persistent, replace cell board
Automated Recovery: None
Event Generation Threshold: 1 occurrence

Event 1034

Severity: CRITICAL
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:
Cause: This will lead to a system reset. Action:-
Automated Recovery: None
Event Generation Threshold: 1 occurrence

Event 1036

Severity: CRITICAL
Event Summary: Firmware was unable to find a suitable block of main memory to relocate ROM
Event Class: System
Problem Description:
A Firmware tries to find a main memory block large enough meeting alignment requirements.
Cause / Action:
Cause: Probably caused by lots of PDT entries, or no main memory present. Action:-
Automated Recovery: None
Event Generation Threshold: 1 occurrence

Event 1037

Severity: MAJOR
Event Summary: PDHC has detected the PDH battery low warning.
Event Class: System
Problem Description:
The Battery-Low interrupt was signaled in the Interrupt Pending Register in Dillon (PDH) by the hardware. PDHC is merely reporting the problem.
Cause / Action: Cause: PDH battery power is low. Action: Replaced the PDH battery.
Automated Recovery: None
Event Generation Threshold: 1 occurrence

Event 1042

Severity: MAJOR
Event Summary: Unexpected software path has been taken
Event Class: System
Problem Description:
A software error has occurred. Data field consists of file number and line number. Lab involvement is indicated.
Cause / Action:
Cause: System Firmware design or code bug is likely. Action: Contact the Response Center to report defect Upgrade PDC firmware
Automated Recovery: None
Event Generation Threshold: 1 occurrence

Event 1043

Severity: FATAL
Event Summary: An HPMC has been encountered.
Event Class: System
Problem Description:
Each CPU will send this code early in the PDC HPMC handler, as soon as the cause of the machine check is determined to be HPMC. The data field contains the interrupt instruction address offset.
Cause / Action: Cause: HPMC has occurred. Action: Contact HP Support to analyze the HPMC PIM and Error Logs to determine the cause of the failure
Automated Recovery: None
Event Generation Threshold: 1 occurrence

Event 1044

Severity: MAJOR
Event Summary: The OS_HPMC vector in the IVA table is misaligned.
Event Class: System
Problem Description:
PDC performs a number of checks on the OS HPMC handler before branching to it. In this case, an IVA table has been installed, but the OS_HPMC vector address is misaligned. The partition will reboot rather than branch to OS_HPMC for crash-dump
Cause / Action:
Cause: IVA table has been incorrectly constructed or corrupted. Action: There will be no OS crash-dump. Contact HP Support for analysis of HPMC PIM and ErrorLogs Report event to the Response Center
Automated Recovery: None
Event Generation Threshold: 1 occurrence

Event 1045

Severity: MAJOR
Event Summary: The OS HPMC handler checksum is bad.
Event Class: System
Problem Description:
PDC performs a number of checks on the OS HPMC handler before branching to it. In this case, an IVA table has been installed but the OS HPMC handler checksum is bad. The partition will reboot rather than branch to OS_HPMC for crash-dump
Cause / Action:
Cause: There will be no OS crash-dump. Contact HP Support for analysis of HPMC PIM and ErrorLogs Report event to the Response Center Action: -
Automated Recovery: None
Event Generation Threshold: 1 occurrence

Event 1046

Severity: MAJOR
Event Summary: The HPMC handler length field in the IVA is zero.
Event Class: System
Problem Description:
PDC performs a number of checks on the OS HPMC handler before branching to it. In this case, the HPMC handler length field in the IVA determines the length for the checksum test. The length must be a multiple of 4 to cover complete code instructions. This check has failed. The parition will reboot rather than branch to OS_HPMC for crash-dump Cause / Action:
Cause: IVA table has been incorrectly constructed or corrupted. Action: There will be no OS crash-dump. Contact HP Support for analysis of HPMC PIM and ErrorLogs Report event to the Response Center
Automated Recovery: None
Event Generation Threshold: 1 occurrence

Event 1047

Severity: OTHER
Event Summary: Attempt to branch to OS HPMC handler failed.
Event Class: System
Problem Description:
Cannot branch to OS HPMC handler. Cause / Action:
Cause: Specific reason for this failure will be identified by another chassis code. There will be no OS crash-dump. Contact HP Support for analysis of HPMC PIM and ErrorLogs Action: Review previous chassis codes to determine reason for branch failure
Automated Recovery: None
Event Generation Threshold: 1 occurrence

Event 1048

Severity: MAJOR
Event Summary: Attempt to reset the cell from within the HPMC handler has failed.
Event Class: System
Problem Description:
It should not be possible for the reset to fail. Lab involvement is indicated. Cause / Action:
Cause: Indicates CRITICAL software or hardware error. Escalate. Action: Report this to the Response Center Contact HP Support personnel to troubleshoot problem
Automated Recovery: None
Event Generation Threshold: 1 occurrence

Event 1049

Severity: UNKNOWN
Event Summary: PDC has detected a nested HPMC
Event Class: System
Problem Description:
After PDC_HPMC completes and branches to OS HPMC, OS_HPMC will unmask HPMCs. If the OS_HPMC encounters an HPMC, the second entry to PDC_HPMC be caught before the orignal PIM and ErrorLogs are overwritten. PDC will restart the partition.
Cause / Action:
Cause: HPMC within OS_HPMC handler. Action: There may be no crash-dump, or an incomplete crash-dump. Contact HP Support to Analyze the HPMCs
Automated Recovery: None
Event Generation Threshold: 1 occurrence

Event 1050

Severity: MAJOR
Event Summary: NVM flag has been used to halt the cell during HPMC
Event Class: System
Problem Description:
This chassis code should only be enabled at the direction of the lab. If it is seen inadvertently, it is Equivalent to ERR_ASSERT. The lab must be notified.
Cause / Action: Cause: Cell halt during HPMC has been enabled from the BCH debug menu. Action: Contact the Response Center to have flag cleared
Automated Recovery: None
Event Generation Threshold: 1 occurrence

Event 1051

Severity: MAJOR
Event Summary: NVM flag has been used to halt the cell during HPMC
Event Class: System
Problem Description:
This chassis code should only be enabled at the direction of the lab. If it is seen inadvertently, it is Equivalent toERR_ASSERT. Lab must be notified.
Cause / Action: Cause: Cell halt during HPMC has been enabled from the BCH debug menu. Action: Contact the Response Center to have flag cleared
Automated Recovery: None
Event Generation Threshold: 1 occurrence

Event 1052

Severity: MAJOR
Event Summary: An IVA table has been installed, but the HPMC vector is zero.
Event Class: System
Problem Description:
The IVA table is expected to provide an OS HPMC handler. This event is sent if the first instruction of the handler is NULL. PDC will reboot the partition instead of branching to the OS HPMC handler.
Cause / Action: Cause: IVA table has been incorrectly constructed or corrupted. Action: There will be no OS crash-dump. Contact HP Support to Analyze HPMC Report event to the Response Center
Automated Recovery: None
Event Generation Threshold: 1 occurrence

Event 1131

Severity: MAJOR
Event Summary: ECC parity error
Event Class: System
Problem Description:
The path between the Coherency Controller (CC) and the Crossbar Chip (XBC) has failed the ECC and Parity testing. Data Field: bit index of failed bit
Cause / Action:
Cause: Link or Hardware Failure Action: Have your HP support representative heck the CC
Automated Recovery: None
Event Generation Threshold: 1 occurrence

Event 1251

Severity: CRITICAL
Event Summary: Failed to read from the XBC.
Event Class: System
Problem Description:
After an attempt to takeover the XBC Global Semaphore, a read of the same register failed. This indicates a connectivity failure.
Cause / Action: Cause: Fabric Access Error Action: Check XBC. Check Links/Flex Cables.
Automated Recovery: None
Event Generation Threshold: 1 occurrence

Event 1467

Severity: MAJOR
Event Summary: PDC is unable to determine HVERSION for the CPU module
Event Class: System
Problem Description:
PDC is unable to determine HVERSION for the CPU module and is, therefore, about to halt the cell.
Cause / Action:
Cause: Cell board or PDH riser hardware problem preventing PDC from accessing PDH memory or registers. Action: Contact HP Support to confirm the cell board and PDH riser card are functioning properly. Cause: PDC bug in which implementation has changed such that is no longer follows original design. Action: Find out if this is a known problem, and upgrade PDC if it is a problem.
Automated Recovery: None
Event Generation Threshold: 1 occurrence

Event 1468

Severity: MAJOR
Event Summary: PDC is unable to determine HVERSION for the CPU module
Event Class: System
Problem Description:
PDC is unable to determine HVERSION for the CPU module and is, therefore, about to halt the cell.
Cause / Action:
Cause: Cell board or PDH riser hardware problem preventing PDC from accessing PDH memory or registers. Action: Contact HP Support to confirm the cell board and PDH riser card are functioning properly. Cause: PDC bug in which implementation has changed such that is no longer follows original design. Action: Find out if this is a known problem, and upgrade PDC if it is a problem.
Automated Recovery: None
Event Generation Threshold: 1 occurrence

Event 1469

Severity: MAJOR
Event Summary: PDC is unable to determine HVERSION for the CPU module
Event Class: System
Problem Description:
PDC is unable to determine HVERSION for the CPU module and is, therefore, about to halt the cell.
Cause / Action:
Cause: Cell board or PDH riser hardware problem preventing PDC from accessing PDH memory or registers. Action: Contact HP Support to confirm the cell board and PDH riser card are functioning properly. Cause: PDC bug in which implementation has changed such that is no longer follows original design. Action: Find out if this is a known problem, and upgrade PDC if it is a problem.
Automated Recovery: None
Event Generation Threshold: 1 occurrence

Event 1470

Severity: MAJOR
Event Summary: PDC was unable to determine an HVERSION for this CPU even in MFG mode
Event Class: System
Problem Description:
An entry that directly corresponds to the data associated with the executing CPU was not found in the HVERSION table in PDC. However, PDC then tries to see if the complex is in MFG mode. In this case, the complex was found to be in MFG mode. Therefore, PDC proceeded to find out if there was at least a close configuration whose HVERSION could be used instead of halting.
Cause / Action: Cause: The complex was in Normal Mode and the cell or CPUs were either not part of an expected shippable configuration or the complex was in MFG Mode and the cell or CPUs were so far from an expected shippable configuration that PDC could not even find a close configuration from which to derive the HVERSION. Action: Figure out what's wrong with the configuration either through chassis logs or by verifying the configuration you have and cross-checking it against documented supported configurations. Change your hardware so that it is a supported configuration.
Automated Recovery: None
Event Generation Threshold: 1 occurrence

Event 1471

Severity: MAJOR
Event Summary: PDC was unable to find out if the complex is in MFG Mode
Event Class: System
Problem Description:
An entry that directly corresponds to the data associated with the executing CPU was not found in the HVERSION table in PDC. However, PDC then tries to see if the complex is in MFG mode. This chassis log is sent to indicate that PDC was unable to find out what the operating mode was for the complex.
Cause / Action: Cause: Cell board or PDH riser hardware problem preventing PDC from accessing PDH memory or registers. Action: Contact HP Support to confirm the cell board and PDH riser card are functioning properly.
Automated Recovery: None
Event Generation Threshold: 1 occurrence

Event 1487

Severity: MAJOR
Event Summary: PDC could not determine the CPU module's HVERSION
Event Class: System
Problem Description:
The cell is about to be halted.
Cause / Action:
Cause: The complex was in Normal Mode and the cell or CPUs were either not part of an expected shippable configuration or the complex was in MFG Mode and the cell or CPUs were so far from an expected shippable configuration that PDC could not even find a close configuration from which to derive the HVERSION. Action: Figure out what's wrong with the configuration either through chassis logs or by verifying the configuration you have and cross-checking it against documented supported configurations. Change your hardware so that it is a supported configuration.
Automated Recovery: None
Event Generation Threshold: 1 occurrence

Event 1544

Severity: FATAL
Event Summary: Partition monarch CPU cannot obtain data from a cell in its partition.
Event Class: System
Problem Description:
User attempted to return to BCH from ISL, but the the PD monarch could not access data in PDH memory of a cell in its partition, so reset PD.
Cause / Action:
Cause: CPU is on unreachable cell Defective CPU Action: Contact HP Support personnel to troubleshoot cell board Investigate for fabric problem
Automated Recovery: None
Event Generation Threshold: 1 occurrence

Event 1550

Severity: MAJOR
Event Summary: Error occurred accessing a PDC data structure
Event Class: System
Problem Description:
Error occurred accessing a PDC data structure. The cell will be halted. The data field contains the return status for the function that encountered the error.
Cause / Action:
Cause: Hardware problem with the PDH riser card. Action: Contact HP Support to confirm the PDH riser card is functioning properly. Cause: Hardware problem with the CPU or cell board. Action: Contact HP Support to confirm the CPUs and cell board are functioning properly
Automated Recovery: None
Event Generation Threshold: 1 occurrence

Event 1551

Severity: MAJOR
Event Summary: Error occurred accessing a PDC data structure
Event Class: System
Problem Description:
Error occurred accessing a PDC data structure. The cell will be halted. The data field contains the return status for the function that encountered the error.
Cause / Action:
Cause: Hardware problem with the PDH riser card. Action: Contact HP Support to confirm the PDH riser card is functioning properly. Cause: Hardware problem with the CPU or cell board. Action: Contact HP Support to confirm the CPUs and cell board are functioning properly
Automated Recovery: None
Event Generation Threshold: 1 occurrence

Event 1553

Severity: MAJOR
Event Summary: Error occurred accessing a PDC data structure
Event Class: System
Problem Description:
Error occurred accessing a PDC data structure. The cell will be halted. The data field contains the return status for the function that encountered the error.
Cause / Action:
Cause: Hardware problem with the PDH riser card. Action: Contact HP Support to confirm the PDH riser card is functioning properly. Cause: Hardware problem with the CPU or cell board. Action: Contact HP Support to confirm the CPUs and cell board are functioning properly
Automated Recovery: None
Event Generation Threshold: 1 occurrence

Event 1554

Severity: MAJOR
Event Summary: Error occurred accessing a PDC data structure
Event Class: System
Problem Description:
Error occurred accessing a PDC data structure. The cell will be halted. The data field contains the return status for the function that encountered the error.
Cause / Action:
Cause: Hardware problem with the PDH riser card. Action: Contact HP Support to confirm the PDH riser card is functioning properly. Cause: Hardware problem with the CPU or cell board. Action: Contact HP Support to confirm the CPUs and cell board are functioning properly
Automated Recovery: None
Event Generation Threshold: 1 occurrence

Event 1632

Severity: MAJOR
Event Summary: PDC was unable to check the compatibility of the CPUs
Event Class: System
Problem Description:
Around the time of early CPU selftests, PDC checks that all the CPUs within the cell are compatible with one another. However, PDC was unable to perform this check. Therefore, the cell is about to be halted.
Cause / Action:
Cause: Something is wrong with the cell that either prevents PDC from accessing PDH memory or causes PDC not to fetch and execute code properly. Action: Troubleshoot the cell hardware to determine if this is the case Cause: There is a PDC bug in which the PDC implementation has changed over time and no longer abides by the original design of CPU compatibility checking. Action: Find out if PDC has found any problems with this part of the code and if there is a new PDC image, and if so, upgrade PDC.
Automated Recovery: None
Event Generation Threshold: 1 occurrence

Event 1633

Severity: MAJOR
Event Summary: PDC was unable to successfully complete the CPU homogeneity check
Event Class: System
Problem Description:
PDC was unable to complete the task of verifying that the processors satisfy their homogeneity requirements. The cell is about to be halted.
Cause / Action:
Cause: Cell hardware failure preventing PDC from being able to complete some homogeneity check. See high-alert level chassis logs sent just prior to this one to find out exactly what data could not be accessed. Action: Contact HP Support personnel to troubleshoot problem
Automated Recovery: None
Event Generation Threshold: 1 occurrence

Event 1634

Severity: MAJOR
Event Summary: PDC has determined that the CPUs on the cell are not compatible.
Event Class: System
Problem Description:
PDC now allows for different revisions of the same processor to run together on a single cell and within a partition. PDC checks to make sure that all the CPUs on a cell are compatible with one another. In this case, the function that checks for compatibility has returned to its caller indicating the the CPUs are not compatible. This chassis log tells us that the cell is about to be halted and why.
Cause / Action:
Cause: Check the chassis logs sent following CC_BOOT_CPUS_ARE_INCOMPATIBLE to figure out why the CPUs are incompatible. There will be chassis logs with the physical location of each of the CPUs that were checked for compatibility, along with CPU type and CPU revision. Action: Figure out which CPU(s) didn't belong in the cell and replace CPUs within the cell accordingly.
Automated Recovery: None
Event Generation Threshold: 1 occurrence

Event 1635

Severity: MAJOR
Event Summary: PDC was unable to determine its operating mode (Normal or MFG)
Event Class: System
Problem Description:
PDC was unable to complete the task of determining system mode (mfg or normal). The cell is about to be halted.
Cause / Action: Cause: Cell hardware failure preventing PDC access to data in PDH memory Action: Contact HP Support personnel to troubleshoot problem
Automated Recovery: None
Event Generation Threshold: 1 occurrence

Event 1636

Severity: MAJOR
Event Summary: PDC was unable to determine whether or not processors are overclocked.
Event Class: System
Problem Description:
PDC was unable to complete the task of checking for overclocked CPUs. The cell is about to be halted.
Cause / Action:
Cause: Cell hardware failure preventing PDC from being able to complete some homogeneity check. See high-alert level chassis logs sent just prior to this one to find out exactly what data could not be accessed. Action: Contact HP Support personnel to troubleshoot problem
Automated Recovery: None
Event Generation Threshold: 1 occurrence

Event 1653

Severity: MAJOR
Event Summary: CPU frequency is greater than the maximum reliable speed for this processor
Event Class: System
Problem Description:
PDC detected that the processor is being clocked at a rate that is more than the maximum speed at which the processor is expected to run reliably. If the complex is in Normal Mode, this processor will soon be deconfigured. If the complex is in MFG Mode, this high alert level chassis log will be sent as a warning but the processor will be allowed to boot anyway. To know which processor is being over clocked, find the local CPU number for this processor in the data field of a chassis log sent just prior, called CC_BOOT_MISMATCH_CPU_CAP_SPEEDS.
Cause / Action:
Cause: The cell is programmed incorrectly such that it is lying to PDC about the frequency at which the processor is running. Action: Perform an update to the cell board so that it accurately reports the rate at which processors are being clocked Cause2: One or more CPUs are being over clocked. Action1: Contact HP Support personnel to troubleshoot the cell board Cause3: PDC error in which PDC is incorrectly calculating the CPU speed. Action3: Upgrade PDC
Automated Recovery: None
Event Generation Threshold: 1 occurrence

Event 1654

Severity: MAJOR
Event Summary: CPU frequency is greater than the maximum reliable speed for this processor
Event Class: System
Problem Description:
PDC detected that the processor is being clocked at a rate that is more than the maximum speed at which the processor is expected to run reliably. If the complex is in Normal Mode, this processor will soon be deconfigured.
Cause / Action:
Cause: The cell is programmed incorrectly such that it is lying to PDC about the frequency at which the processor is running. Action: Perform an update to the cell board so that it accurately reports the rate at which processors are being clocked Cause2: One or more CPUs are being over clocked. Action1: Contact HP Support personnel to troubleshoot the cell board Cause3: PDC error in which PDC is incorrectly calculating the CPU speed. Action3: Upgrade PDC
Automated Recovery: None
Event Generation Threshold: 1 occurrence

Event 1655

Severity: MAJOR
Event Summary: PDC is was unable to read the CPU speed rating and/or the actual CPU speed
Event Class: System
Problem Description:
PDC is was unable to read the CPU speed rating and/or the actual CPU speed. When either case fails, both are sent out.
Cause / Action:
Cause: Cell hardware failure preventing PDC from reading speed rating data from PDH. Action: Contact HP Support personnel to troubleshoot the cell board
Automated Recovery: None
Event Generation Threshold: 1 occurrence

Event 1656

Severity: MAJOR
Event Summary: PDC was unable to read the CPU speed rating and/or the actual CPU speed.
Event Class: System
Problem Description:
PDC was unable to read the CPU speed rating and/or the actual CPU speed. When either case fails, both are sent out.
Cause / Action:
Cause: Cell hardware failure preventing PDC from reading data from PDH memory Action: Contact HP Support personnel to troubleshoot the cell board
Automated Recovery: None
Event Generation Threshold: 1 occurrence

Event 1696

Severity: UNKNOWN
Event Summary: Errors signaled in coherency controller Secondary Error Mode Regs
Event Class: System
Problem Description:
PDC periodically polls the coherency controller (CC) Secondary Error Mode registers to check for errors logged there. During portions of bootstrap when some CC errors are masked, this polling can illuminate transient errors that may otherwise be missed, or can help to root cause a problem that appears later as an HPMC. These chassis codes are also used to report CC register contents during HPMC handling. The data field contains the CC block address and register address in the most significant byte (each field occupying a nibble). The remainder of the data field contains the Secondary Error Mode register contents. When errors are masked (via clear bits in the Error Enable Mask), they are still recorded in the Secondary Error Mask. This chassis code will not be output when error overflow occurs from Primary to Secondary Error Mode. In that case only the ERR_DNA_PRI_HEALTH chassis code will be output.
Cause / Action:
Cause: Errors have been detected by CC, while errors are masked from Primary Error Mode. Action: Analysis data field to determine block, register and error status
Automated Recovery: None
Event Generation Threshold: 1 occurrence

Event 1698

Severity: FATAL
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. This Check Summary is described in the return value description for CpuProcessMachineCheck in PA-8800 CPU Library Application
Cause / Action:
Cause: Contact HP Support. Save event list and Processor HPMC PIM for analysis by lab. Action: -
Automated Recovery: None
Event Generation Threshold: 1 occurrence

Event 1702

Severity: MAJOR
Event Summary: Blocking Timeout detected by Concorde PIN block.
Event Class: System
Problem Description:
A blocking timeout has been detected by Concorde PIN block. This will normally preclude branching to OS_HPMC and collection of crash dump. PIM and ErrorLogs are collected to NVM by firmware. Tombstones may be analyzed after reboot. Data field contains the physical location of the affected CC.
Cause / Action:
Cause: Blocking timeout in CC PIN block. OS crash-dump will not occur. Contact HP Support to Analyze HPMC Action: -
Automated Recovery: None
Event Generation Threshold: 1 occurrence

Event 1705

Severity: MAJOR
Event Summary: During HPMC handling, a latent HPMC has been logged while HPMCs are masked.
Event Class: System
Problem Description:
Data field contains the physical location of the CPU that has logged a latent HPMC while HPMCs are masked. This is a FATAL error, which precludes branch to OS_HPMC for dump.
Cause / Action:
Cause: PD will reboot. No operator intervention is required. Analyze HPMC cause using PIM/ErrorLogs (tombstones). There will be no OS crashdump. Action: -
Automated Recovery: None
Event Generation Threshold: 1 occurrence

Event 1706

Severity: MAJOR
Event Summary: An HPMC crash slave CPU has detected a latent HPMC while HPMCs are masked.
Event Class: System
Problem Description:
The data field specifies the physical location of the CPU that has detected a latent HPMC while HPMCs are masked. This will prevent the HPMC crash monarch from branching to OS_HPMC for dump.
Cause / Action:
Cause: The PD will reset rather than branch to OS_HPMC. There will be no OS crash-dump. The HPMC cause should be determined by analysis of PIM and ErrorLogs. Action: -
Automated Recovery: None
Event Generation Threshold: 1 occurrence

Event 1708

Severity: MAJOR
Event Summary: An HPMC has occurred during an cell Online Add or Online Delete FATAL section
Event Class: System
Problem Description:
If an HPMC occurs during Cell OL* operations, there is a short FATAL section which PDC will not be sure of Partition membership. If this section is interrupted, PDC will not branch to OS_HPMC for crash dump. The PD will be reset at completion of PDC_HPMC.
Cause / Action:
Cause: Partition will reboot rather than branch to OS_HPMC for dump. No operator action is required. Action: -
Automated Recovery: None
Event Generation Threshold: 1 occurrence

Event 1709

Severity: MAJOR
Event Summary: OAQ block of Concorde has hung due to multiple fatal timeouts.
Event Class: System
Problem Description:
OAQ block in CC has experienced multiple fatal timeouts, and has hung. The data field contains the physical location of the CC.
Cause / Action: Cause: A part of CC has hung. PDC_HPMC cannot safely branch to OS_HPMC. PDC will reset the partition, precluding memory crash dump. Action: Contact HP Support to Analyze HPMC
Automated Recovery: None
Event Generation Threshold: 1 occurrence

Event 1713

Severity: FATAL
Event Summary: PDC was unable to access a cell board hardware register
Event Class: System
Problem Description:
PDC was unable to access a cell board hardware register or a cell board hardware register did not behave as expected. The partition will be reset. The data field is the return status from the function that encountered the error.
Cause / Action:
Cause: Hardware problem with the PDH riser card. Action: Contact HP support to confirm the PDH riser card is functioning properly. Cause: Hardware problem with the CPU or cell board. Action1: Contact HP support to confirm the CPUs and cell board are functioning properly. Action: -
Automated Recovery: None
Event Generation Threshold: 1 occurrence

Event 1714

Severity: FATAL
Event Summary: PD is doing a reset for reconfiguration because of IPR clearing error
Event Class: System
Problem Description:
PDC is required to clear the IPR of all cells in the partition prior to handing off the system to the OS. To meet this requirement, the PD monarch clears the IPR on all cells in the partition as it boots to ISL. This chassis log is thrown when there are one or more cells whose IPR the PD monarch was unable to clear. This can happen for a couple of reasons, but PDC is now doing a reset for reconfiguration of the partition to get the cells to SINC_BIB so that the user/CE can address the problem. The partition will be reset.
Cause / Action:
Cause: Look for chassis logs BOOT_ERROR_CLEARING_IPR_ON_CELL and BOOT_ERROR_CLEARING_IPR_AT_LAUNCH and follow their cause actions. Action: -
Automated Recovery: None
Event Generation Threshold: 1 occurrence

Event 1715

Severity: FATAL
Event Summary: PDC was unable to access a cell board hardware register
Event Class: System
Problem Description:
PDC was unable to access a cell board hardware register or a cell board hardware register did not behave as expected. The partition will be reset. The data field is the return status from the function that encountered the error.
Cause / Action:
Cause: Hardware problem with the PDH riser card. Action: Contact HP support to confirm the PDH riser card is functioning properly. Cause: Hardware problem with the CPU or cell board. Action1: Contact HP support to confirm the CPUs and cell board are functioning properly. Action: -
Automated Recovery: None
Event Generation Threshold: 1 occurrence

Event 1716

Severity: FATAL
Event Summary: PDC was unable to clear the IPR in Dillon for unknown reason
Event Class: System
Problem Description:
Indicates an unexpected return status from a PDC function. This is a PDC bug. Data field contains the unexpected return value. The partition will be reset.
Cause / Action:
Cause: PDC bug. Action: Contact HP Support to check for PDC Upgrade.
Automated Recovery: None
Event Generation Threshold: 1 occurrence

Event 1717

Severity: MAJOR
Event Summary: PDC has detected the PDH battery low warning
Event Class: System
Problem Description:
The Battery-Low interrupt was signalled in the Interrupt Pending Register in Dillon (PDH) by the hardware. PDC is merely reporting the problem.
Cause / Action:
Cause: PDH battery power is low. Action: Replace the PDH battery.
Automated Recovery: None
Event Generation Threshold: 1 occurrence

Event 1718

Severity: FATAL
Event Summary: PDC is about to reset the partition due to one or more PDH events
Event Class: System
Problem Description:
Due to PDH events PDC found pending on one or more cells in the partition, PDC is about to do a reset for reconfiguration of the partition. The data field contains the value of the flag that is used in a PDC function. This flag value is what controls whether or not PDC enters this section of code that is now going to reset the partition.
Cause / Action:
Cause: One or more CRITICAL PDH events were found pending in one or more of the cells' Interrupt Pending Registers. Action: Look for other chassis logs sent shortly before that would indicate what PDH events were found and on which cells, and handle those PDH events according to the cause-action statements for the BOOT_PDH_EVENTS_PENDING and BOOT_PDH_BATTERY_POWER_LOW chassis logs.
Automated Recovery: None
Event Generation Threshold: 1 occurrence

Event 1719

Severity: MAJOR
Event Summary: There is at least one CPU module for which SPIROM data is unavailable
Event Class: System
Problem Description:
While trying to gather the SPIROM data for each CPU module present, PDC was unable to get SPIROM data from the Utilities for at least one CPU module and PDC does not already have cached SPIROM data for the CPU module to enable boot. So, PDC is about to deconfigure the modules for which there is no SPIROM data available.
Cause / Action:
Cause: EEPROM on the System Management Bus (accessible to Utilities) that contains the SPIROM data has invalid data or bad checksums. Action: Fix the contents of the EEPROM(s) to have valid SPIROM data for the CPU module(s). Cause: Internal PDC problem. Action: Upgrade PDC if there is a PDC ROM that fixes this particular problem. Cause: There could be a problem in USB that is preventing the PDHC and the MP from communicating to gather the SPIROM data. Action: Troubleshoot to find out if the problem is that USB was just not functioning at the time PDC requested the SPIROM data.
Automated Recovery: None
Event Generation Threshold: 1 occurrence

Event 1720

Severity: MAJOR
Event Summary: PDC received an error while communicating with the PDHC
Event Class: System
Problem Description:
PDC received an error while communicating with the PDHC. The cell will be halted. The data field contains the cell number.
Cause / Action:
Cause: Hardware problem with the MP or PDHC. Action: Contact HP Support to confirm the manageability subsystem is functioning properly. Cause: PDHC, MP, and/or PDC firmware are not compatible. Action: Upgrade PDHC, MP, and/or PDC firmware to supported and compatible revisions.
Automated Recovery: None
Event Generation Threshold: 1 occurrence

Event 1721

Severity: MAJOR
Event Summary: PDC received an unexpected return status from an internal function
Event Class: System
Problem Description:
PDC received an unexpected return status from an internal function. The cell will be halted. Data field contains the cell number.
Cause / Action:
Cause: Hardware failure with CPU, CC or cell board. Action: Contact HP Support to confirm the CPUs, CC, and cell board are functioning properly. Update PDC if a version is available to fix this problem.
Automated Recovery: None
Event Generation Threshold: 1 occurrence

Event 1724

Severity: MAJOR
Event Summary: TOC has interrupted a FATAL section of OLA/D operation.
Event Class: System
Problem Description:
If a TOC occurs during Cell OL* operations, there is a short FATAL section in which PDC will not be sure of Partition membership. If this section is interrupted, PDC will not branch to OS_TOC. The partition will reset instead.
Cause / Action:
Cause: Identify cause of TOC. Action: -
Automated Recovery: None
Event Generation Threshold: 1 occurrence

Event 1726

Severity: MAJOR
Event Summary: A write access to a scratch RAM structure failed.
Event Class: System
Problem Description:
PDC attempted to perform a write access to the data structure that contains the CPU module HVersion, but a failure occurred. The data field contains the return status from the function that writes to the data structure. The cell will be halted.
Cause / Action:
Cause: Cell hardware failure. Cause2: PDC runtime error. Action: Contact HP support to troubleshoot the cell Action: Check hardware for failures: cell Upgrade PDC if a newer version is available. Contact response center. Action: -
Automated Recovery: None
Event Generation Threshold: 1 occurrence

Event 1727

Severity: CRITICAL
Event Summary: PDC detected a failure in creating and/or passing around an argument
Event Class: System
Problem Description:
An invalid CPU number was passed into an internal PDC function. The data field contains the invalid parameter.
Cause / Action:
Cause: Hardware failure with CPU, CC or cell board. Action: Contact HP Support to confirm the CPUs, CC, and cell board are functioning properly. Update PDC if a version is available to fix this problem.
Automated Recovery: None
Event Generation Threshold: 1 occurrence

Event 1728

Severity: CRITICAL
Event Summary: PDC detected an illegal argument passed between functions
Event Class: System
Problem Description:
PDC passed a bad value between functions, specifically, an invalid number for a local CPU number. This is an internal PDC error for which the cell will be halted. Data field is the invalid local CPU number passed to a PDC function.
Cause / Action: Cause: Cell hardware failure preventing PDC from getting valid data from the hardware. Action1: Contact HP Support personnel to troubleshoot problem Cause 2: Some internal PDC error where PDC incorrectly determines the local CPU number Action2: Upgrade PDC Action: -
Automated Recovery: None
Event Generation Threshold: 1 occurrence

Event 1729

Severity: MAJOR
Event Summary: PDC detected an illegal CPU number while trying to deconfigure a CPU
Event Class: System
Problem Description:
Cell is about to be halted because an invalid CPU number was passed into an internal PDC function. The data field contains the invalid parameter.
Cause / Action:
Cause: Hardware failure with CPU, CC or cell board. Action: Contact HP Support to confirm the CPUs, CC, and cell board are functioning properly. Update PDC if a version is available to fix this problem.
Automated Recovery: None
Event Generation Threshold: 1 occurrence

Event 1730

Severity: MAJOR
Event Summary: PDC detected an illegal CPU number while trying to deconfigure a CPU
Event Class: System
Problem Description:
Cell is about to be halted because an invalid CPU number was passed into an internal PDC function. The data field contains the invalid parameter.
Cause / Action:
Cause: Hardware failure with CPU, CC or cell board. Action: Contact HP Support to confirm the CPUs, CC, and cell board are functioning properly. Update PDC if a version is available to fix this problem.
Automated Recovery: None
Event Generation Threshold: 1 occurrence

Event 1732

Severity: MAJOR
Event Summary: PDC was unable to access a local data structure.
Event Class: System
Problem Description:
PDC could not access one of its own data structures on the local cell. The cell will be halted or if a partition has been formed, the partition will be reset. The data field contains the return status from the PDC function that encountered the error.
Cause / Action:
Cause: Hardware problem with the PDH riser card. Action: Contact HP Support to confirm the PDH riser card is functioning properly. Cause: Hardware problem with the CPU or cell board. Action: Contact HP Support to confirm the CPUs and cell board are functioning properly.
Automated Recovery: None
Event Generation Threshold: 1 occurrence

Event 1733

Severity: MAJOR
Event Summary: PDC was unable to access a local data structure.
Event Class: System
Problem Description:
PDC could not access one of its own data structures on the local cell. The cell will be halted or if a partition has been formed, the partition will be reset. The data field contains the return status from the PDC function that encountered the error.
Cause / Action:
Cause: Hardware problem with the PDH riser card. Action: Contact HP Support to confirm the PDH riser card is functioning properly. Cause: Hardware problem with the CPU or cell board. Action: Contact HP Support to confirm the CPUs and cell board are functioning properly.
Automated Recovery: None
Event Generation Threshold: 1 occurrence

Event 1734

Severity: MAJOR
Event Summary: PDC was unable to access a local data structure.
Event Class: System
Problem Description:
PDC could not access one of its own data structures on the local cell. The cell will be halted or if a partition has been formed, the partition will be reset. The data field contains the return status from the PDC function that encountered the error.
Cause / Action:
Cause: Hardware problem with the PDH riser card. Action: Contact HP Support to confirm the PDH riser card is functioning properly. Cause: Hardware problem with the CPU or cell board. Action: Contact HP Support to confirm the CPUs and cell board are functioning properly.
Automated Recovery: None
Event Generation Threshold: 1 occurrence

Event 1735

Severity: MAJOR
Event Summary: PDC was unable to access a local data structure.
Event Class: System
Problem Description:
PDC could not access one of its own data structures on the local cell. The cell will be halted or if a partition has been formed, the partition will be reset. The data field contains the return status from the PDC function that encountered the error.
Cause / Action:
Cause: Hardware problem with the PDH riser card. Action: Contact HP Support to confirm the PDH riser card is functioning properly. Cause: Hardware problem with the CPU or cell board. Action: Contact HP Support to confirm the CPUs and cell board are functioning properly.
Automated Recovery: None
Event Generation Threshold: 1 occurrence

Event 1756

Severity: FATAL
Event Summary: A hardware failure with a PDH Raiser Card's "hardware" semaphore register
Event Class: System
Problem Description:
Cause / Action:
Cause: A hardware failure with a PDH Raiser Card's "hardware" semaphore register. Action: Contact HP Support personnel to troubleshoot the problem.
Automated Recovery: None
Event Generation Threshold: 1 occurrence

Event 1758

Severity: CRITICAL
Event Summary: Dumping error info. Read status of the Primary Mode 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 1760

Severity: MAJOR
Event Summary: The main backplane is reporting the LPM status as fault.
Event Class: System
Problem Description:
The main backplane is reporting the LPM status as fault.
Cause / Action:
Many possible causes, repair / replace the appropriate part.
Automated Recovery: None
Event Generation Threshold: 1 occurrence

Event 1761

Severity: MAJOR
Event Summary: PDC failed clearing the OLA steering bit in the Dillon microstatus reg.
Event Class: System
Problem Description:
PDC failed clearing the OLA steering bit in the Dillon microstatus register. Data field contains the physical location of the cell with the failure. This can only happen on an OLA cell and will cause that cell to reset and not to join the existing partition.
Cause / Action:
Cause1: Probably something wrong with the cell hardware. Action1: Try OLAing a different cell. Contact HP Support personnel to troubleshoot the problem.
Automated Recovery: None
Event Generation Threshold: 1 occurrence

Event 1762

Severity: MAJOR
Event Summary: The IO backplane is reporting a LPM status as fault.
Event Class: System
Problem Description:
The IO backplane has reported a local power monitor fault.
Cause / Action:
Service / replace the appropiate part of, or the entire backplane.
Automated Recovery: None
Event Generation Threshold: 1 occurrence

Event 1764

Severity: MAJOR
Event Summary: The System Flash Write Enable bit is incorrectly set and now clearing by PDC
Event Class: System
Problem Description:
The System Flash Write Enable bit is incorrectly set and now clearing by PDC. The Data field contains the value of PDH Miscellaneous Signal Register read before System Flash bit is cleared.
Cause / Action:
Cause: The System Flash Write Enable bit is incorrectly set by hardware and now cleared by PDC. Action: If this chassis code occurs in every boot then contact HP Support personnel to troubleshoot the problem.
Automated Recovery: None
Event Generation Threshold: 1 occurrence

Event 1765

Severity: CRITICAL
Event Summary: Error copying the routing registers to the local port
Event Class: System
Problem Description:
Error writing the XBC port's routing registers. The cell will reboot. Data Field: XBC port << 44 | XBC num << 32 | return status
Cause / Action:
Cause: XBC access failure. Action: Check XBC, check links, check backplane, check CC.
Automated Recovery: None
Event Generation Threshold: 1 occurrence

Event 1766

Severity: FATAL
Event Summary: Resetting the partition because couldn't access PDH memory
Event Class: System
Problem Description:
When returning from other software, like when returning from ISL, PDC is trying to make sure that all of the slave processors in the partition are asleep; however, this event ID indicates that we were unable to access PDH memory of a cell that is supposed to be part of our partition. The data field contains the error return status from a function called SleepAndWakeupCountersGet().
Cause / Action:
Cause: CPU is on unreachable cell Defective CPU Action: Contact HP Support personnel to troubleshoot cell board Investigate for fabric problem
Automated Recovery: None
Event Generation Threshold: 1 occurrence

Event 1767

Severity: FATAL
Event Summary: Resetting the partition because a processor was not in expected state
Event Class: System
Problem Description:
When returning to PDC from other software, like returning from ISL, PDC tries to verify that all the slave processors are in the expected state (ie that all slave processors are asleep); however, this event ID indicates that at least one processor active in the partition was not asleep. So, PDC is going to reset the partition. The data field of this Event ID is the global CPU number of the first CPU in the partition not found in the expected state.
Cause / Action:
Cause1: Software has not correctly returned all CPUs to sleep state Action1: Reset would clear this issue Cause2: CPU did not properly receive/execute sleep command Action2: Contact HP Support to troubleshoot cell board
Automated Recovery: None
Event Generation Threshold: 1 occurrence

Event 1768

Severity: MAJOR
Event Summary: PDC could not access a data structure on the local cell
Event Class: System
Problem Description:
PDC could not access one of its own data structures on the local cell. The cell will be halted. The data field contains the return status from the PDC 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 1769

Severity: MAJOR
Event Summary: Resetting cell because processor couldn't access it's own PDH memory
Event Class: System
Problem Description:
The cell will be reset because it was unable to access PDH memory on its own cell. While trying to move all the slave processors on the cell to the "late boot sleep", the monarch tried to write the sleep timeout to PDH memory on its own cell, but encountered an error in doing so. The data field contains a PDC 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 1770

Severity: MAJOR
Event Summary: Halting cell because bad parameter passing was discovered
Event Class: System
Problem Description:
PDC attempted to tell a slave CPU to execute from an unknown location. Data field contains the location id that PDC attempted to move the slave to.
Cause / Action:
Cause: PDC passed bad parameter Action: Contact HP Support
Automated Recovery: None
Event Generation Threshold: 1 occurrence

Event 1771

Severity: MAJOR
Event Summary: Halting cell because PDC was unable to determine GNI address of a function
Event Class: System
Problem Description:
Halting cell/PD because PDC was unable to determine GNI address of a function. Data field contains a status return indicating type of failure.
Cause / Action:
Cause1: If data field of chassis code = -102 or -103, cell failed in getting the address Action1: Check fabric connections Contact HP support to troubleshoot cell board(s) Cause2: if data field contains -104, PDC successfully read the address, but that address was invalid, likely was not initialized Action2: Contact HP support
Automated Recovery: None
Event Generation Threshold: 1 occurrence

Event 1772

Severity: MAJOR
Event Summary: Could not access a data structure on a cell in the partition.
Event Class: System
Problem Description:
A write attempt to a data structure on the executing cell board failed. The cell will be reset. The data field contains the return value from PDC function that detected the error.
Cause / Action:
Cause1: Hardware problem with the cell board, CPU, or PDH riser card. Action1: Contact HP Support to confirm the cell board, CPUs, and PDH riser card are functioning properly.
Automated Recovery: None
Event Generation Threshold: 1 occurrence

Event 1773

Severity: FATAL
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 1774

Severity: MAJOR
Event Summary: Error Data tied to a previous Error Assert event
Event Class: System
Problem Description:
A software error has occurred. Data field consists of data pertinent to the error. Lab involvement is indicated.
Cause / Action:
Cause: System Firmware design or code bug is likely. Action: Contact the Response Center to report defect Upgrade PDC firmware
Automated Recovery: None
Event Generation Threshold: 1 occurrence

Event 1775

Severity: MAJOR
Event Summary: The read of the Memory extender FRU failed.
Event Class: System
Problem Description:
The read of the Memory extender FRU failed.
Cause / Action:
Cause: The FRU EEPROM for the memory extender is corrupted or the EEPROM was not able to be accessed. Action: Contact HP Support to troubleshoot the problem.
Automated Recovery: None
Event Generation Threshold: 1 occurrence

Event 1776

Severity: CRITICAL
Event Summary: Attempt to update Cell Static Routing has failed
Event Class: System
Problem Description:
Failed to route around a broken link on cell reboot. Data Field: PDC return status
Cause / Action:
Fabric Access Error
Contact HP Support personnel to analyze the fabric.
Automated Recovery: None
Event Generation Threshold: 1 occurrence

Event 1777

Severity: CRITICAL
Event Summary: Failed to read the XBC CSR that containes the number of failed links
Event Class: System
Problem Description:
Could not read the XBC register that contains the number of links that are currently broken on the complex. Data Field: (XBC Num << 32) | PDC return status
Cause / Action:
Fabric Access Failure
Contact HP Support personnel to check the XBC, Backplane, CC, look for additional chassis codes to describe the problem.
Automated Recovery: None
Event Generation Threshold: 1 occurrence

Event 1778

Severity: CRITICAL
Event Summary: Failed to write the XBC CSR that containes the number of failed links
Event Class: System
Problem Description:
Could not write the XBC register that contains the number of links that are currently broken on the complex. Data Field: (XBC Num << 32) | PDC return status
Cause / Action:
Fabric Access Failure
Contact HP Support personnel to check the XBC, Backplane, CC, look for additional chassis codes to describe the problem.
Automated Recovery: None
Event Generation Threshold: 1 occurrence

Event 1779

Severity: CRITICAL
Event Summary: Failed to read the XBC CSR that containes the number of failed links
Event Class: System
Problem Description:
Could not read the XBC register that contains the number of links that are currently broken on the complex. Data Field: PDC return status
Cause / Action:
Fabric Access Failure
Contact HP Support personnel to check the XBC, Backplane, CC, look for additional chassis codes to describe the problem.
Automated Recovery: None
Event Generation Threshold: 1 occurrence

Event 1780

Severity: CRITICAL
Event Summary: Failed to write the XBC CSR that containes the number of failed links
Event Class: System
Problem Description:
Could not write the XBC register that contains the number of links that are currently broken on the complex. Data Field: (XBC Num << 32) | PDC return status
Cause / Action:
Fabric Access Failure
Contact HP Support personnel to check the XBC, Backplane, CC, look for additional chassis codes to describe the problem.
Automated Recovery: None
Event Generation Threshold: 1 occurrence

Event 1781

Severity: CRITICAL
Event Summary: Failed to read the XBC CSR that marks the port route arounds
Event Class: System
Problem Description:
Could not read the XBC register that marks the ports that have been routed around. Data Field: (XBC Num << 32) | PDC return status
Cause / Action:
Fabric Access Failure
Contact HP Support personnel to check the XBC, Backplane, CC, look for additional chassis codes to describe the problem.
Automated Recovery: None
Event Generation Threshold: 1 occurrence

Event 1782

Severity: CRITICAL
Event Summary: Could not traverse the PIOB route to the remote XBC
Event Class: System
Problem Description:
The PIOB route to the remote XBC was not traversable. The cell will halt. Data Field: (XBC Num << 32) | PDC return status
Cause / Action:
Broken Crossbar Link
Contact HP Support personnel to check the XBC, Backplane, Flex Cables. Look for additional chassis codes to provide more detail.
Automated Recovery: None
Event Generation Threshold: 1 occurrence

Event 1783

Severity: MAJOR
Event Summary: Failed to release the XBC semaphore after landmining a remote XBC port
Event Class: System
Problem Description:
Could not release the remote XBC's semaphore. Cell will halt. Data Field: (XBC Num << 32) | PDC return status
Cause / Action:
Fabric Access Failure
Contact HP Support personnel to check the XBC, Backplane, CC, look for additional chassis codes to describe the problem.
Automated Recovery: None
Event Generation Threshold: 1 occurrence

Event 1784

Severity: MAJOR
Event Summary: Windows IML: Temperature overheat condition warning
Event Class: System
Problem Description:
This error is logged when SCSI Disk Drivers or Disk Array Drivers indicate that an overheat condition has occurred.
Cause / Action:
Cause: SCSI Disk Drivers or Disk Array Drivers indicate an Overheat Condition. Action: Shutdown servers and storage box. Check room temperature of room and air flow to storage box.
Automated Recovery: None
Event Generation Threshold: 1 occurrence

Event 1785

Severity: CRITICAL
Event Summary: Windows IML: FATAL fan failure
Event Class: System
Problem Description:
This error is logged when SCSI Disk Drivers of Disk Array driver detect a FATAL Fan Failure.
Cause / Action:
Cause: SCSI Disk Drivers or Disk Array Drivers indicate a FATAL Fan Failure. This alert occurs when redundant fans have failed and the FATAL Fan Failure is imminent. Action: Replace Fan Modules as soon as possible following the Fan Module Remove and Replace Procedures.
Automated Recovery: None
Event Generation Threshold: 1 occurrence

Event 1786

Severity: MAJOR
Event Summary: Windows IML: Fan failure warning condition
Event Class: System
Problem Description:
This error is logged when SCSI Disk Drivers of Disk Array driver detect a Fan Failure.
Cause / Action:
Cause: SCSI Disk Drivers or Disk Array Drivers indicate that a redundant fan has failed or is operating in a degraded condition. Action: Replace Fan Module as soon as possible following the Fan Module Remove and Replace Procedures.
Automated Recovery: None
Event Generation Threshold: 1 occurrence

Event 1787

Severity: MAJOR
Event Summary: Windows IML: Door open event warning
Event Class: System
Problem Description:
This error is logged when SCSI Disk Drivers or Disk Array Drivers detect an open door panel.
Cause / Action:
Cause: SCSI Disk Drivers or Disk Array Drivers detects an open door panel. Action: Close any open panels.
Automated Recovery: None
Event Generation Threshold: 1 occurrence

Event 1788

Severity: MAJOR
Event Summary: Windows IML: Fans no longer redundant warning
Event Class: System
Problem Description:
This event should be logged after a fan failure that causes a fan set to be no longer redundant.
Cause / Action:
Cause: SCSI Disk Drivers or Disk Array Drivers has issued a Fans No Longer Redundant alert. This event should be logged after a fan failure that causes a fan set to be no longer redundant. Action: Replace Fan Module as soon as possible following the Fan Module Remove and Replace Procedure.
Automated Recovery: None
Event Generation Threshold: 1 occurrence

Event 1789

Severity: MAJOR
Event Summary: Windows IML: Power Supply Failure
Event Class: System
Problem Description:
This error indicates that either SCSI Disk Drivers or Disk Array Drivers have issued a Power Supply Failure alert.
Cause / Action:
Cause: SCSI Disk Drivers or Disk Array Drivers has issued a Power Supply Failure alert. Action: Replace with a proper power supply.
Automated Recovery: None
Event Generation Threshold: 1 occurrence

Event 1790

Severity: MAJOR
Event Summary: Windows IML: Power subsystem no longer redundant
Event Class: System
Problem Description:
This error is logged by Disk drivers when a loss of redundancy is detected due to a power supply failure.
Cause / Action:
Cause: Disk drivers logged a Power SubSystem No Longer Redundant alert. A loss of redundancy due to the power supply failure. Action: Replace with a proper power supply.
Automated Recovery: None
Event Generation Threshold: 1 occurrence

Event 1791

Severity: MAJOR
Event Summary: Windows IML: Network adapter check
Event Class: System
Problem Description:
Network Drivers are detecting adapter checks possibly due to a bad adapter or a bad driver.
Cause / Action:
Cause: Network Drivers log this event when adapter checks are detected. This event will never be repaired due to the possibility of a large number of adapter checks being generated by a bad adapter or bad driver. Action: No user action is required, informational only.
Automated Recovery: None
Event Generation Threshold: 1 occurrence

Event 1792

Severity: CRITICAL
Event Summary: Windows IML: Network adapter link fault
Event Class: System
Problem Description:
Network Drivers or Agents log this event when a FATAL link problem is detected.
Cause / Action:
Cause: Network Drivers or Agents log this event when a FATAL link problem is detected. Action: Check your cable connections and make sure the network cables are plugged in.
Automated Recovery: None
Event Generation Threshold: 1 occurrence

Event 1793

Severity: MAJOR
Event Summary: Windows IML: Network adapter transmit timeout
Event Class: System
Problem Description:
Network Drivers detect a transmit timeout possibly due to a bad adapter or a bad driver.
Cause / Action:
Cause: Network Drivers log this event when a transmit timeout is detected. This event will never be repaired due to the possibility of a large number of transmit timeout that may occur with a bad adapter Action: Check your network connections. If the problem remains, please contact your support provider for further assistance.
Automated Recovery: None
Event Generation Threshold: 1 occurrence

Event 1794

Severity: MAJOR
Event Summary: Windows IML: Network adapters no longer redundant
Event Class: System
Problem Description:
Network Drivers can not communicate with one of the adapters in a redundant pair due to the slot being powered off.
Cause / Action:
Cause: Network Drivers can not communicate with one of the adapters in a redundant pair due to the slot being powered off. If the power is turned off on both adapters of a pair, this event is only logged once. Action: Check if the physical adapters are connected and their network connections are working. If the problem remains, re-configure your team settings.
Automated Recovery: None
Event Generation Threshold: 1 occurrence

Event 1795

Severity: MAJOR
Event Summary: Windows IML: Network adapter redundancy reduced
Event Class: System
Problem Description:
Network Drivers or Agents can not communicate with one of the adapters in a team and at least one adapter in a team is still active.
Cause / Action:
Cause: Network Drivers or Agents can not communicate with one of the adapters in a team and at least one adapter in a team is still active. Action: Check if the physical adapters are connected and their network connections are working. If the problem remains, re-configure your team settings.
Automated Recovery: None
Event Generation Threshold: 1 occurrence

Event 1796

Severity: CRITICAL
Event Summary: Windows IML: SCSI Controller failure
Event Class: System
Problem Description:
This event is logged when SCSI Disk Drivers detect a FATAL hardware failure.
Cause / Action:
Cause: SCSI Disk Drivers detected a FATAL hardware failure. Acton: Possible controller failure. Replace SCSI controller.
Automated Recovery: None
Event Generation Threshold: 1 occurrence

Event 1797

Severity: MAJOR
Event Summary: Windows IML: SCSI Controller failure warning
Event Class: System
Problem Description:
This event is logged when SCSI Disk Drivers detect a hardware failure.
Cause / Action:
Cause: SCSI Disk Drivers detected a hardware failure. Acton: Possible controller failure. Replace SCSI controller.
Automated Recovery: None
Event Generation Threshold: 1 occurrence

Event 1798

Severity: CRITICAL
Event Summary: Windows IML: SCSI Device failure
Event Class: System
Problem Description:
This event is logged when SCSI Disk Drivers detect a FATAL disk failure.
Cause / Action:
Cause: SCSI Disk Drivers detected a FATAL disk failure. This event is never logged by the mini-port driver. Action: Replace failed drive.
Automated Recovery: None
Event Generation Threshold: 1 occurrence

Event 1799

Severity: MAJOR
Event Summary: Windows IML: SCSI Controller failure in redundant configuration
Event Class: System
Problem Description:
This event is logged when SCSI Disk Drivers detect a Controller failure event in a redundant configuration.
Cause / Action:
Cause: SCSI Disk Drivers detected a Controller failure event in a redundant configuration. Action: Identify and repair failed component.
Automated Recovery: None
Event Generation Threshold: 1 occurrence

Event 1800

Severity: CRITICAL
Event Summary: Windows IML: Disk Array Controller failure
Event Class: System
Problem Description:
This event is logged when Drive Array Subsystem Drivers detect a FATAL controller failure event.
Cause / Action:
Cause: Drive Array Subsystem Drivers detected a FATAL controller failure event. Action: Possible controller failure. Replace SCSI controller.
Automated Recovery: None
Event Generation Threshold: 1 occurrence

Event 1801

Severity: MAJOR
Event Summary: Windows IML: Disk Array Controller failure warning
Event Class: System
Problem Description:
This event is logged when Drive Array Subsystem Drivers detect a controller failure event.
Cause / Action:
Cause: Drive Array Subsystem Drivers detected a controller failure event. Action: Possible controller failure. Replace SCSI controller.
Automated Recovery: None
Event Generation Threshold: 1 occurrence

Event 1802

Severity: CRITICAL
Event Summary: Windows IML: Disk Array Controller device failure
Event Class: System
Problem Description:
This even is logged when Drive Array Subsystem Drivers detect a FATAL disk failure.
Cause / Action:
Cause: Drive Array Subsystem Drivers detected a FATAL disk failure. Action: Replace failed drive.
Automated Recovery: None
Event Generation Threshold: 1 occurrence

Event 1803

Severity: MAJOR
Event Summary: Windows IML: Disk Array Controller battery failure
Event Class: System
Problem Description:
This event is logged by Disk Array Drivers to indicate that an Accelerator Battery Failure has occurred.
Cause / Action:
Cause: Disk Array Drivers logged an Accelerator Battery Failure event. Action: Replace battery on cache module.
Automated Recovery: None
Event Generation Threshold: 1 occurrence

Event 1804

Severity: MAJOR
Event Summary: Windows IML: Disk Array Controller failure in redundant configuration
Event Class: System
Problem Description:
This event is logged when Disk Array Drivers detect that a Controller No Longer Redundant failure event has occurred in a redundant configuration.
Cause / Action:
Cause: Array Disk Drivers detected a Controller No Longer Redundant failure event in a redundant configuration. Action: Identify and repair failed component.
Automated Recovery: None
Event Generation Threshold: 1 occurrence

Event 1805

Severity: MAJOR
Event Summary: Windows: Predictive Failure in Memory
Event Class: System
Problem Description:
ECC (Error Checking and Correcting) memory is designed to detect and correct single-bit errors that occasionally occur in computer systems. This memory module is currently correcting many single bit errors.
Cause / Action:
Cause: You will receive this message if the system is correcting a lot of ECC single bit errors. It may mean that the module is about to fail, or environmental conditions in the server are causing more errors than usual. Action: If you receive this message, contact your support provider to determine if a predictive repair should be made.
Automated Recovery: None
Event Generation Threshold: 1 occurrence

Event 1806

Severity: MAJOR
Event Summary: Windows: Server Agents Management data not accessible, locked property
Event Class: System
Problem Description:
Server Agents SNMP branch is not responding due to a portion of the IPMI Management Subsystem being locked by another entity.
Cause / Action:
Cause: The installed management software has detected an unstable state of the underlying IPMI (Intelligent Platform Management Interface) subsystem and has disabled all management information from being shown by any manageability applications. The management information will become available automatically as soon as the IPMI subsystem has stabilized. Action: None.
Automated Recovery: None
Event Generation Threshold: 1 occurrence

Event 1807

Severity: FATAL
Event Summary: PDC could not access a complex profile
Event Class: System
Problem Description:
PDC could not access a complex profile. The partition will be reset because the available complex profile is not valid. Data field contains the return status from the function that encountered the error.
Cause / Action:
Cause1: An error occurred which prevented the complex profiles from being distributed properly. Action1: Create and distribute a new complex profile using ParMgr on a functional partition in the complex. Restore the last complex profile using the "CC" command from the MP, then use ParMgr to create a new complex profile. Generate a genesis complex profile using the "CC" command from the MP, then use ParMgr to create a new complex profile. Cause2: A hardware problem exists with MP or PDHC hardware. Action2: Contact HP Support to confirm the MP and PDHC are functioning properly.
Automated Recovery: None
Event Generation Threshold: 1 occurrence

Event 1808

Severity: MAJOR
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.
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 1809

Severity: FATAL
Event Summary: PDC could not access a complex profile
Event Class: System
Problem Description:
PDC could not access a complex profile. The partition will be reset. Data field contains the return status from the function that encountered the error.
Cause / Action:
Cause1: An error occurred which prevented the complex profiles from being distributed properly. Action1: Create and distribute a new complex profile using ParMgr on a functional partition in the complex. Restore the last complex profile using the "CC" command from the MP, then use ParMgr to create a new complex profile. Generate a genesis complex profile using the "CC" command from the MP, then use ParMgr to create a new complex profile. Cause2: A hardware problem exists with MP or PDHC hardware. Action2: Contact HP Support to confirm the MP and PDHC are functioning properly.
Automated Recovery: None
Event Generation Threshold: 1 occurrence

Event 1810

Severity: MAJOR
Event Summary: Configuration information on the processor was invalid
Event Class: System
Problem Description:
Configuration information on the processor was invalid. The cell will be halted. Data field contains the return value from the function that encountered the error.
Cause / Action:
Cause: Hardware problem with the CPU. Action: Contact HP Support to confirm the CPU is functioning properly.
Automated Recovery: None
Event Generation Threshold: 1 occurrence

Event 1811

Severity: FATAL
Event Summary: PDC could not read an internal CPU register
Event Class: System
Problem Description:
PDC could not read an internal CPU register. The partition will be reset. Data field is the return status from the function that encountered the error.
Cause / Action:
Cause: Hardware problem with the CPU. Action: Contact HP Support to confirm the CPU is functioning properly.
Automated Recovery: None
Event Generation Threshold: 1 occurrence

Event 1812

Severity: FATAL
Event Summary: PDC could not read an internal CPU register
Event Class: System
Problem Description:
PDC could not read an internal CPU register. The partition will be reset. Data field is the return status from the function that encountered the error.
Cause / Action:
Cause: Hardware problem with the CPU. Action: Contact HP Support to confirm the CPU is functioning properly.
Automated Recovery: None
Event Generation Threshold: 1 occurrence

Event 1813

Severity: FATAL
Event Summary: PDC failed reading a specific value from its own copy of the internal CPU regs
Event Class: System
Problem Description:
PDC failed reading a value out of its own copy of the internal CPU register settings. Data field is a status return indicating the type of failure.
Cause / Action:
Cause1: problem on cell wherein PDC could not properly access memory Action1: Contact HP support to troubleshoot cell board Cause2: a non-existent/non-accessible register was specified by software. Action2: Contact HP support for possible PDC upgrade
Automated Recovery: None
Event Generation Threshold: 1 occurrence

Event 1814

Severity: FATAL
Event Summary: PDC failed reading a specific value from its own copy of the internal CPU regs
Event Class: System
Problem Description:
PDC failed reading a value out of its own copy of the internal CPU register settings. Data field is a status return indicating the type of failure.
Cause / Action:
Cause1: problem on cell wherein PDC could not properly access memory Action1: Contact HP support to troubleshoot cell board Cause2: a non-existent/non-accessible register was specified by software. Action2: Contact HP support for possible PDC upgrade
Automated Recovery: None
Event Generation Threshold: 1 occurrence

Event 1815

Severity: FATAL
Event Summary: PDC failed attempting to update internal CPU registers
Event Class: System
Problem Description:
PDC attempted to update CPU registers to match their respective settings in the complex profile, but a failure was returned from the call to accomplish the update. Data field contains the failure.
Cause / Action:
Cause: Could not update CPU settings Action: Contact HP support to troubleshoot cell board and CPU.
Automated Recovery: None
Event Generation Threshold: 1 occurrence

Event 1816

Severity: FATAL
Event Summary: PDC could not access a complex profile
Event Class: System
Problem Description:
PDC could not access a complex profile. The partition will be reset.. Data field contains the return status from the function that encountered the error.
Cause / Action:
Cause1: An error occurred which prevented the complex profiles from being distributed properly. Action1: Create and distribute a new complex profile using ParMgr on a functional partition in the complex. Restore the last complex profile using the "CC" command from the MP, then use ParMgr to create a new complex profile. Generate a genesis complex profile using the "CC" command from the MP, then use ParMgr to create a new complex profile. Cause2: A hardware problem exists with MP or PDHC hardware. Action2: Contact HP Support to confirm the MP and PDHC are functioning properly.
Automated Recovery: None
Event Generation Threshold: 1 occurrence

Event 1817

Severity: FATAL
Event Summary: Cells in the partition have different complex profiles.
Event Class: System
Problem Description:
Cell boards in the same partition have different complex profiles. The partition will be rebooted and cannot be fully booted until the problem is resolved. The data field is a bitmap of cells where cell 0 is the least significant bit and cell 63 is the most significant bit. A one on a cell's bit indicated that the cell has a complex profile that did not match that of the core cell.
Cause / Action:
Cause1: An error occurred which prevented the complex profiles from being distributed properly. Action1: Create and distribute a new complex profile using ParMgr on a functional partition in the complex. Restore the last complex profile using the "CC" command from the MP, then use ParMgr to create a new complex profile. Generate a genesis complex profile using the "CC" command from the MP, then use ParMgr to create a new complex profile. Cause2: A hardware problem exists with MP or PDHC hardware. Action2: Contact HP Support to confirm the MP and PDHC are functioning properly.
Automated Recovery: None
Event Generation Threshold: 1 occurrence

Event 1818

Severity: FATAL
Event Summary: Cell has different Partition Config Data CRC then core cell
Event Class: System
Problem Description:
PDC checks the Complex Profile C's Extensible Header CRC of the partition configuration data for each of the cells in the partition. If they do not match, this means that the cells have different complex profiles. At this point, is unable to tell which version of the complex profile is correct. The partition cannot be booted until this problem is resolved. This chassis code indicates all of the cells that have complex profiles that do not match the core cell's. The data field is the CRC of the partition configuration data for the slave cell.
Cause / Action:
Cause: The core cell detected that a cell in its partition has a different complex profile than it does. Action: Look for a chassis code called,BOOT_CORE_CHECK_HCELL_PROFILE, to see which cell's complex profile was being checked. That cell is the cell that had the inconsistent complex profile. Make sure the utilities system is functioning and reboot the partition. If the reboot does not solve the problem, make sure PDH tests are enabled. Replace the cell with the inconsistent complex profile. Change core cells to see if the core cell is the cell that has the problem.
Automated Recovery: None
Event Generation Threshold: 1 occurrence

Event 1819

Severity: FATAL
Event Summary: PDC failed to read the processor architecture for another cell in the partition
Event Class: System
Problem Description:
PDC attempts to make sure that all of the cells in a partition are installed in the same processor architecture. PDC failed to read the architecture for another cell. PDC will reset all of the cells in the partition when this error is detected. The data field contains the physical location of the cell reporting the event.
Cause / Action:
Cause: PDC was unable to read a data structure for another cell in the partition. This should never happen unless there is an intermittent problem with the main backplane. Action: Contact HP support to confirm that the main backplane is functioning properly.
Automated Recovery: None
Event Generation Threshold: 1 occurrence

Event 1820

Severity: MAJOR
Event Summary: Windows: Predictive Failure in Memory (Warning)
Event Class: System
Problem Description:
ECC (Error Checking and Correcting) memory is designed to detect and correct single-bit errors that occasionally occur in computer systems. This memory module is currently correcting many single bit errors.
Cause / Action:
Cause: You will receive this message if the system is correcting a lot of ECC single bit errors. It may mean that the module is about to fail, or environmental conditions in the server are causing more errors than usual. This event message will be generated for one of the following conditions 1000 single-bit errors on the same address in a 48 hour time period. 50 single-bit errors on the same DIMM (not the same address) in a 24 hour time period. 100 single-bit errors on the same DIMM (not the same address) in a 1 week time period. Action: If you receive this message, contact your support provider to determine if a predictive repair should be made.
Automated Recovery: None
Event Generation Threshold: 1 occurrence

Event 1821

Severity: CRITICAL
Event Summary: Windows: Predictive Failure in Memory (FATAL)
Event Class: System
Problem Description:
ECC (Error Checking and Correcting) memory is designed to detect and correct single-bit errors that occasionally occur in computer systems. This memory module is currently correcting many single bit errors.
Cause / Action:
Cause: You will receive this message if the system is correcting a lot of ECC single bit errors. It may mean that the module is about to fail, or environmental conditions in the server are causing more errors than usual. This event message will be generated for one of the following conditions 1500 single-bit errors on the same address in a 72 hour time period. 120 single-bit errors on the same DIMM (not the same address) in a 24 hour time period. 130 single-bit errors on the same DIMM (not the same address) in a 1 week time period. Action: If you receive this message, contact your support provider to determine if a predictive repair should be made.
Automated Recovery: None
Event Generation Threshold: 1 occurrence

Event 1822

Severity: CRITICAL
Event Summary: A rope parity error occurred
Event Class: System
Problem Description:
A error occurred on the bus connecting the PCI card to the system bus.
Cause / Action:
An unexpected but random error occurred. Reboot the system. There is a problem with the system bus. Contact your HP representative to check the system bus.
Automated Recovery: None
Event Generation Threshold: 1 occurrence

Event 1823

Severity: CRITICAL
Event Summary: PCI card inaccessible due to bus error
Event Class: System
Problem Description:
A PCI card has been marked as "fatal" by the operating system due to a bus error. The LBA has been isolated by the operating system due to an error which occurred in a device(s) connected to that LBA.
Cause / Action:
Cause: An unexpected but random error occurred. Action: Reboot the system. Cause: There is a problem with the system bus. Contact your HP representative to check for faulty devices on the bus..
Automated Recovery: None
Event Generation Threshold: 1 occurrence

Event 1824

Severity: CRITICAL
Event Summary: PCI card inaccessible due to device error
Event Class: System
Problem Description:
A PCI card has been marked as "fatal" by the operating system due to a device error.
Cause / Action:
An unexpected but random error occurred. Reboot the system. There is a problem with the system bus. Contact your HP representative to check the system bus. Check the system forward progress log (available from the Management Processor) for additional information about this problem.
Automated Recovery: None
Event Generation Threshold: 1 occurrence

Event 1825

Severity: FATAL
Event Summary: error reading bmc first boot token
Event Class: System
Problem Description:
Firmware tried to read the first boot token an got a failure. The data field contains the token number that FW tried to read. This is a stop boot condition
Cause / Action:
Cause: FW tried to read the first boot token and received a failure. Action: AC power cycle the system Action: Contact HP support
Automated Recovery: None
Event Generation Threshold: 1 occurrence

Event 1826

Severity: MAJOR
Event Summary: a rendezvousing cell is non PA architecture and thus incompatible.
Event Class: System
Problem Description:
monarch PA cell has detected that a cell it is attempting to rendezvous into its PD is not a PA cell and is thus incompatible.
Cause / Action:
Cause: other cell is an IA cell Action: replace IA cell with PA cell or reconfigure partition to exclude the IA cell.
Automated Recovery: None
Event Generation Threshold: 1 occurrence

Event 1827

Severity: MAJOR
Event Summary: failed to write the XBC error log clear register
Event Class: System
Problem Description:
A XBC error could not be cleared due to a write failure. The data field indicates the type of error: (XBC Port Num << 56) | (XBC Num << 32) | error status
Cause / Action:
Fabric Access Failure. Could not write to the XBC. This could indicate a hardware problem. Include the FABRIC_ERRORS_XBC_CLEAR_WR_ADDR event log and its data in any reports.
Contact HP Support personnel to analyze the fabric.
Automated Recovery: None
Event Generation Threshold: 1 occurrence

Event 1828

Severity: MAJOR
Event Summary: Error encountered while reading the XBC CSR Error Status Register
Event Class: System
Problem Description:
Failed to read the XBC Global CSR Error Status register. Data Field: (XBC Port Num << 56) | (XBC Num << 32) | error status
Cause / Action:
Fabric Access Failure. Likely hardware problem. Look for additional chassis codes to further isolate the error.
Automated Recovery: None
Event Generation Threshold: 1 occurrence

Event 1829

Severity: MAJOR
Event Summary: The XBC CSR Low Severity error was not cleared
Event Class: System
Problem Description:
The XBC CSR Low Severity error was not cleared or more errors remain. Data Field: (XBC Port Num << 56) | (XBC Num << 32) | contents of the XBC CSR Error Status Register
Cause / Action:
This could be caused by a fabric access error or persistent CSR Low Severity errors. Check Crossbar hardware, flex cables, backplane
Contact HP Support personnel to check the Crossbar hardware, flex cables, backplane
Automated Recovery: None
Event Generation Threshold: 1 occurrence

Event 1830

Severity: MAJOR
Event Summary: The XBC CSR High Severity error was not cleared
Event Class: System
Problem Description:
The XBC CSR High Severity error was not cleared or more errors remain. Data Field: (XBC Port Num << 56) | (XBC Num << 32) | contents of the XBC CSR Error Status Register
Cause / Action:
This could be caused by a fabric access error or persistent CSR Low Severity errors. Check Crossbar hardware, flex cables, backplane
Automated Recovery: None
Event Generation Threshold: 1 occurrence

Event 1831

Severity: MAJOR
Event Summary: Error encounted while reading the XBC Port Error Status Register
Event Class: System
Problem Description:
Failed to read the XBC Port Error Status register. Data Field: (XBC Port Num << 56) | (XBC Num << 32) | error status
Cause / Action:
Fabric Access Failure. Likely hardware problem. Look for additional chassis codes to further isolate the error.
Contact HP Support personnel to analyze the fabric.
Automated Recovery: None
Event Generation Threshold: 1 occurrence

Event 1832

Severity: MAJOR
Event Summary: Failed to read the XBC CSR Error Status register
Event Class: System
Problem Description:
Failed to read the XBC Global CSR Error Status register. Data Field: (XBC Port Num << 56) | error status
Cause / Action:
Fabric Access Failure. Likely hardware problem. Look for additional chassis codes to further isolate the error.
Automated Recovery: None
Event Generation Threshold: 1 occurrence

Event 1833

Severity: MAJOR
Event Summary: Failed to copy the XBC CSR Error Symbol01 Block
Event Class: System
Problem Description:
Firmware failed to copy the XBC CSR Error symbol 01 registers into a data structure on the stack. Data Field: address where the register contents are being copied
Cause / Action:
Fabric Access Failure; Possibly an invalid destination address. Check hardware, Contact HP Support
Automated Recovery: None
Event Generation Threshold: 1 occurrence

Event 1834

Severity: MAJOR
Event Summary: Failed to copy the XBC CSR Error Symbol23 Block
Event Class: System
Problem Description:
Firmware failed to copy the XBC CSR Error symbol 23 registers into a data structure on the stack. Data Field: address where the register contents are being copied
Cause / Action:
Fabric Access Failure; Possibly an invalid destination address. Check hardware, Contact HP Support
Automated Recovery: None
Event Generation Threshold: 1 occurrence

Event 1835

Severity: MAJOR
Event Summary: Failed to reset the XBC Low Severity Error Log State
Event Class: System
Problem Description:
Firmware was unable to reset the XBC CSR Low Severity error log state. Data Field: (XBC Port Num << 56) | (XBC Num << 32) | error status
Cause / Action:
Fabric Access Failure.
Contact HP Support personnel to check the XBC, Flex Cables, Backplane
Automated Recovery: None
Event Generation Threshold: 1 occurrence

Event 1836

Severity: MAJOR
Event Summary: Failed to clear the XBC Low Severity Log Symbol 01
Event Class: System
Problem Description:
The XBC Low Severity error logs were not cleared. Data Field: (XBC Port Num << 56) | (XBC Num << 32) | number of failed clear attempts
Cause / Action:
Fabric Access Failure.
Contact HP Support personnel to check the XBC, Backplane
Automated Recovery: None
Event Generation Threshold: 1 occurrence

Event 1837

Severity: MAJOR
Event Summary: Could not determine if there is a new XBC CSR Low Severity error
Event Class: System
Problem Description:
Reading the XBC CSR Error Status register failed. Data field: (XBC Port Num << 56) | (XBC Num << 32) | error status
Cause / Action:
Fabric Access Failure.
Contact HP Support personnel to check the XBC, Flex Cables, Backplane
Automated Recovery: None
Event Generation Threshold: 1 occurrence

Event 1838

Severity: MAJOR
Event Summary: Failed to read the XBC CSR Low Severity Error Log State
Event Class: System
Problem Description:
Failed to read a XBC Global scratch register that indicates if new, unlogged errors have been encountered. Data field: (XBC Port Num << 56) | (XBC Num << 32) | error status
Cause / Action:
Fabric Access Failure.
Contact HP Support personnel to check the XBC, Flex Cables, Backplane
Automated Recovery: None
Event Generation Threshold: 1 occurrence

Event 1839

Severity: MAJOR
Event Summary: Failed to reset the XBC Low Severity Error Log State
Event Class: System
Problem Description:
Firmware was unable to reset the XBC CSR Low Severity error log state. Data Field: (XBC Port Num << 56) | (XBC Num << 32) | error status
Cause / Action:
Fabric Access Failure.
Contact HP Support personnel to check the XBC, Flex Cables, Backplane
Automated Recovery: None
Event Generation Threshold: 1 occurrence

Event 1840

Severity: MAJOR
Event Summary: Could not determine if there is a new XBC CSR High Severity error
Event Class: System
Problem Description:
Reading the XBC CSR Error Status register failed. Data field: (XBC Port Num << 56) | (XBC Num << 32) | error status
Cause / Action:
Check XBC, Flex Cables, Backplane
Contact HP Support personnel to check the XBC, Flex Cables, Backplane
Automated Recovery: None
Event Generation Threshold: 1 occurrence

Event 1841

Severity: MAJOR
Event Summary: Failed to read the XBC CSR High Severity Error Log State
Event Class: System
Problem Description:
Failed to read a XBC Global scratch register that indicates if new, unlogged errors have been encountered. Data field: (XBC Port Num << 56) | (XBC Num << 32) | error status
Cause / Action:
Fabric Access Failure.
Contact HP Support personnel to check the XBC, Flex Cables, Backplane
Automated Recovery: None
Event Generation Threshold: 1 occurrence

Event 1842

Severity: CRITICAL
Event Summary: An error occurred while enabling hashing in the platform cache
Event Class: System
Problem Description:
An error occurred while enabling hashing in the platform cache. The data field contains the status.
Cause / Action:
Cause: An error return status. This could happen if the tree was corrupted or there was an error verifying the hashing setting. Action: reset the partition
Automated Recovery: None
Event Generation Threshold: 1 occurrence

Event 1843

Severity: MAJOR
Event Summary: The XBC CSR is not a valid CSR address
Event Class: System
Problem Description:
A write to an invalid XBC CSR address was attempted. The write will not be allowed. The severity of this result will be determined by the calling function. Data Field: XBC CSR address that was attempted
Cause / Action:
Invalid CSR address, possible firmware defect.
Capture complete live logs and contact HP Support representative.
Automated Recovery: None
Event Generation Threshold: 1 occurrence

Event 1844

Severity: MAJOR
Event Summary: A failure has occurred with a CPU during early selftests
Event Class: System
Problem Description:
An error has occurred while a CPU was performing early self tests. The data field contains a 32-bit error number and 32-bits of additional error information. The CPU will be deconfigured.
Cause / Action:
Cause: internal error. Action: the CPU will be deconfigured. If the error persists after a power cycle, contact HP Support.
Automated Recovery: None
Event Generation Threshold: 1 occurrence

Event 1845

Severity: MAJOR
Event Summary: An error has occurred during CPU FSB interface initialization
Event Class: System
Problem Description:
An error has occurred during CPU FSB interface initialization. The data field contains a 32-bit error number and 32-bits of additional error information. The CPU will be deconfigured.
Cause / Action:
Cause: internal error. Action: the CPU will be deconfigured. If the error persists after a power cycle, contact HP Support.
Automated Recovery: None
Event Generation Threshold: 1 occurrence

Event 1846

Severity: MAJOR
Event Summary: An error has occurred while obtaining CPU parameters
Event Class: System
Problem Description:
An error has occurred while obtaining CPU parameters from the CPU abstraction layer. The data field contains a 32-bit error number and 32-bits of additional error information. The CPU will be deconfigured.
Cause / Action:
Cause: internal error. Action: the CPU will be deconfigured. If the error persists after a power cycle, contact HP Support.
Automated Recovery: None
Event Generation Threshold: 1 occurrence

Event 1847

Severity: MAJOR
Event Summary: An error has occurred getting CPU icache parameters
Event Class: System
Problem Description:
An error occurred while getting CPU icache parameters from the CPU abstraction layer. The datafield contains a 32-bit error number and 32-bits of additional error information. The CPU will be deconfigured if this error occurs during system boot.
Cause / Action:
Cause: internal error. Action: during system boot the CPU will be deconfigured. If the error persists after a powercycle, contact HP Support.
Automated Recovery: None
Event Generation Threshold: 1 occurrence

Event 1848

Severity: MAJOR
Event Summary: An error occurred getting CPU dcache parameters
Event Class: System
Problem Description:
An error occurred while obtaining CPU dcache parameters from the CPU abstraction layer. The data field contains a 32-bit error number and 32-bits of additional error information. The CPU will be deconfigured if error occurs during system boot.
Cause / Action:
Cause: internal error. Action: during system boot the CPU will be deconfigured. If the error persists after a power cycle, contact HP Support.
Automated Recovery: None
Event Generation Threshold: 1 occurrence

Event 1849

Severity: MAJOR
Event Summary: An error has occurred while initializing the CPU cache to a known state
Event Class: System
Problem Description:
An error occurred while initializing the CPU cache to a known state. The data field contains a 32-bit error number and 32-bits of additional error information. The CPU will be deconfigured.
Cause / Action:
Cause: internal error. Action: the CPU will be deconfigured. If the error persists after a power cycle, contact HP Support.
Automated Recovery: None
Event Generation Threshold: 1 occurrence

Event 1850

Severity: MAJOR
Event Summary: An error has occurred while enabling CPU cache error monitoring
Event Class: System
Problem Description:
An error occurred while enabling CPU cache error monitoring. The data field contains a 32-bit error number and 32-bits of additional error information. The CPU will be deconfigured.
Cause / Action:
Cause: internal error. Action: the CPU will be deconfigured. If the error persists after a power cycle, contact HP Support.
Automated Recovery: None
Event Generation Threshold: 1 occurrence

Event 1851

Severity: MAJOR
Event Summary: An error has occurred while enabling machine check traps on a CPU
Event Class: System
Problem Description:
An error occurred while enabling some machine error check traps on a CPU. The data field contains a 32-bit error number and 32-bits of additional error information. The CPU will be deconfigured.
Cause / Action:
Cause: internal error. Action: the CPU will be deconfigured. If the error persists after a power cycle, contact HP Support.
Automated Recovery: None
Event Generation Threshold: 1 occurrence

Event 1852

Severity: MAJOR
Event Summary: An error has occurred while disabling machine error check traps on a CPU
Event Class: System
Problem Description:
An error occurred while disabling matching error check traps on a CPU. The data field contains a 32-bit error number and 32-bits of additional error information. The CPU will be deconfigured.
Cause / Action:
Cause: internal error. Action: the CPU will be deconfigured. If the error persists after a power cycle, contact HP Support.
Automated Recovery: None
Event Generation Threshold: 1 occurrence

Event 1853

Severity: MAJOR
Event Summary: An error has occurred during CPU serialized late self tests
Event Class: System
Problem Description:
An error occurred during the serialized CPU late self tests. The data field contains a 32-bit error number and 32-bits of additional error information. The CPU will be deconfigured.
Cause / Action:
Cause: internal error. Action: the CPU will be deconfigured. If the error persists after a power cycle, contact HP Support.
Automated Recovery: None
Event Generation Threshold: 1 occurrence

Event 1854

Severity: MAJOR
Event Summary: An error occurred while enabling CPU L2 shared cache
Event Class: System
Problem Description:
An error occurred while enabling the CPU L2 shared cache. The data field contains a 32-bit error number and 32-bits of additional error information. The CPU will be deconfigured.
Cause / Action:
Cause: internal error. Action: the CPU will be deconfigured. If the error persists after a power cycle, contact HP Support.
Automated Recovery: None
Event Generation Threshold: 1 occurrence

Event 1855

Severity: MAJOR
Event Summary: An error occurred while getting default values for CPU internal registers
Event Class: System
Problem Description:
An error while getting default values for programmable CPU internal registers from the CPU abstraction layer. The data field contains a 32-bit error number and 32-bits of additional error information. The CPU will be deconfigured.
Cause / Action:
Cause: internal error. Action: the CPU will be deconfigured. If the error persists after a power cycle, contact HP Support.
Automated Recovery: None
Event Generation Threshold: 1 occurrence

Event 1856

Severity: MAJOR
Event Summary: An error occurred while getting an address for a CPU internal register
Event Class: System
Problem Description:
An error occurred while getting an address for a CPU internal register within a buffer from the CPU abstraction layer. The datafield contains a 32-bit error number and 32-bits of additional error information. The CPU will be deconfigured.
Cause / Action:
Cause: internal error. Action: the CPU will be deconfigured. If the error persists after a powercycle, contact HP Support.
Automated Recovery: None
Event Generation Threshold: 1 occurrence

Event 1857

Severity: MAJOR
Event Summary: An error occurred while programming CPU internal registers
Event Class: System
Problem Description:
An error occurred while programming CPU internal registers with final configuration values. The data field contains a 32-bit error number and 32-bits of additional error information. The CPU will be deconfigured.
Cause / Action:
Cause: internal error. Action: the CPU will be deconfigured. If the error persists after a power cycle, contact HP Support.
Automated Recovery: None
Event Generation Threshold: 1 occurrence

Event 1858

Severity: MAJOR
Event Summary: An error has occurred while attempting to get CPU ITLB parameters
Event Class: System
Problem Description:
An error occurred while getting CPU ITLB parameters from the CPU abstraction layer. The data field contains a 32-bit error number and 32-bits of additional error information. The CPU will be deconfigured if this error occurs during system boot.
Cause / Action:
Cause: internal error. Action: during system boot the CPU will be deconfigured. If the error persists after a power cycle, contact HP Support.
Automated Recovery: None
Event Generation Threshold: 1 occurrence

Event 1859

Severity: MAJOR
Event Summary: An error occurred while getting CPU DTLB parameters
Event Class: System
Problem Description:
An error occurred while getting CPU DTLB parameters from the CPU abstraction layer. The data field contains a 32-bit error number and 32-bits of additional error information. The CPU will be deconfigured if this error occurs during system boot.
Cause / Action:
Cause: internal error. Action: during system boot the CPU will be deconfigured. If the error persists after a power cycle, contact HP Support.
Automated Recovery: None
Event Generation Threshold: 1 occurrence

Event 1860

Severity: CRITICAL
Event Summary: There was not enough error free memory in the system to run the late self tests
Event Class: System
Problem Description:
There was not enough error free memory in the system to run the late self tests.
Cause / Action:
Due to excessive memory subsystem or DIMM errors, the late self tests could not be run. DIMMs or memory extenders have caused excessive errors and will need to be replaced. Consult the memory test events regarding memory errors or view the Page Deallocation Table from BCH.
Automated Recovery: None
Event Generation Threshold: 1 occurrence

Event 1861

Severity: MAJOR
Event Summary: A Checksum error was encountered in the dynamic profile
Event Class: System
Problem Description:
The Dynamic Complex Profile (Group B) stored checksum did not equal the calculated checksum. The Expected Data and Actual date are displayed in successive chassis codes.
Cause / Action:
Cause: Push out a new complex profile and reset. Action: -
Automated Recovery: None
Event Generation Threshold: 1 occurrence

Event 1862

Severity: MAJOR
Event Summary: A checksum error occurred on the Partition Profile.
Event Class: System
Problem Description:
The stored value of the complex profile Group C does not match the calculated value. Expected data and actual data are stored in successive chassis codes.
Cause / Action:
Cause: Push out a new complex profile and reboot. Action: -
Automated Recovery: None
Event Generation Threshold: 1 occurrence

Event 1863

Severity: MAJOR
Event Summary: Unable to clear error in coherency controller (CC).
Event Class: System
Problem Description:
An error remains in coherency controller (CC) primary error mode register after attempt to clear it. The data field contains the contents of the Primary Error Mode register, with the most-significant byte over-written with the CC block address.
Cause / Action:
Cause: During HPMC handling, when errors are masked, this would indicate a CRITICAL failure to clear an error on the local cell. At other times, it could indicate a recurring error. Action: Analyze HPMC to determine the cause of the failure If during HPMC handling, troubleshoot the cell board the cell board
Automated Recovery: None
Event Generation Threshold: 1 occurrence

Event 1865

Severity: MAJOR
Event Summary: Multiple Loss of Lockstep results in cell halt.
Event Class: System
Problem Description:
The cell identified by the data field (physical location) has detected multiple loss of lockstep events the last power-on. The cell will be halted to prevent possible spreading of fabric errors to other partitions.
Cause / Action:
Cause: Fabric problem. Action: Check HPMC PIM/ErrorLogs for cause of HPMC. Check fabric and backplane connectivity.
Automated Recovery: None
Event Generation Threshold: 1 occurrence

Event 1866

Severity: FATAL
Event Summary: PDC encountered an unexpected event and could not continue.
Event Class: System
Problem Description:
PDC called an internal utility function and that function unexpectedly reported an error.
Cause / Action:
Cause: Report the incident and the Data Contents to Hewlett-Packard. Reboot. Reinstall PDC Firmware. Contact HP Support personnel to troubleshoot the problem. Action: -
Automated Recovery: None
Event Generation Threshold: 1 occurrence

Event 1867

Severity: FATAL
Event Summary: Fatal internal error
Event Class: System
Problem Description:
The attempt to get GI range information from the Stable Complex Data failed. Data Field: PDC call status return
Cause / Action: Cause: Probable hardware error Action: Contact HP Support personnel to troubleshoot the problem
Automated Recovery: None
Event Generation Threshold: 1 occurrence

Event 1868

Severity: FATAL
Event Summary: Fatal internal error
Event Class: System
Problem Description:
The attempt to get GI resource information from the Stable Complex Data failed. Data Field: PDC call status return
Cause / Action:
Cause: Probable hardware error Action: Contact HP Support personnel to troubleshoot the problem
Automated Recovery: None
Event Generation Threshold: 1 occurrence

Event 1869

Severity: FATAL
Event Summary: Fatal internal error
Event Class: System
Problem Description:
The attempt to get the KGM value from information from Partition Configuration Data failed. Data Field: PDC call status return
Cause / Action:
Cause: Probable hardware error Action: Contact HP Support personnel to troubleshoot the problem
Automated Recovery: None
Event Generation Threshold: 1 occurrence

Event 1870

Severity: FATAL
Event Summary: Fatal internal error
Event Class: System
Problem Description:
The attempt to get the quantity of installed memory of a cell failed. Data Field: PDC call status return
Cause / Action:
Cause: Probable hardware error Action: Contact HP Support personnel to troubleshoot the problem
Automated Recovery: None
Event Generation Threshold: 1 occurrence

Event 1871

Severity: FATAL
Event Summary: Fatal internal error
Event Class: System
Problem Description:
The attempt to read the Stable Configuration Data failed. Data Field: PDC call status return
Cause / Action:
Cause: Probable hardware error Action: Contact HP Support personnel to troubleshoot the problem
Automated Recovery: None
Event Generation Threshold: 1 occurrence

Event 1872

Severity: FATAL
Event Summary: Fatal internal error
Event Class: System
Problem Description:
The attempt to get ZI range information from Stable Complex Data failed. Data Field: PDC call status return
Cause / Action:
Cause: Probable hardware error Action: Contact HP Support personnel to troubleshoot the problem
Automated Recovery: None
Event Generation Threshold: 1 occurrence

Event 1873

Severity: FATAL
Event Summary: Unexpected overflow of an internal Firmware Data Structure.
Event Class: System
Problem Description:
PDC detected the case where there were more Address Map entries than space was allowed for, AND the mechanism to safely handle this case failed.
Cause / Action:
Cause: Record the Chassis Codes, and the exact memory configuration, including Base and Floating Cells, and any Cell Local Memory. Report the data to Hewlett-Packard. Reinstall PDC Firmware. Change the memory configuration by adding or removing Floating Cells, Cell Local Memory, deallocating DIMMs, or the cells themselves from the Partition. Action: -
Automated Recovery: None
Event Generation Threshold: 1 occurrence

Event 1874

Severity: MAJOR
Event Summary: The memory configuration was adjusted to satisfy the Minimum ZI requirement.
Event Class: System
Problem Description:
PDC detected the case where too much memory was allocated to Cell Local Memory. There was not enough memory to meet the Minimum ZI requirement. PDC reduced the amount of Cell Local Memory in order to meet the Minimum ZI requirement, and continued.
Cause / Action:
Cause: Review the Chassis Codes and determine if a cell, or DIMMs within a cell, were removed from the Interleave because of an error. If so, correct the problem and reboot. If there was no such event, the Partition is probably misconfigured. Review the configuration and correct it with the Parmanager tools. Action: -
Automated Recovery: None
Event Generation Threshold: 1 occurrence

Event 1875

Severity: FATAL
Event Summary: Fatal internal error
Event Class: System
Problem Description:
The Cell Map code attempted to build a data structure describing the memory of each cell in the partition and an error was reported. Data Field: PDC call status return
Cause / Action:
Cause: Probable hardware error Action: Contact HP Support personnel to troubleshoot the problem
Automated Recovery: None
Event Generation Threshold: 1 occurrence

Event 1876

Severity: FATAL
Event Summary: Chassis code not implemented
Event Class: System
Problem Description:
This chassis code is not used in the current revision of PDC
Cause / Action:
Cause: This chassis code is not used in the current revision of PDC Action: No action is required.
Automated Recovery: None
Event Generation Threshold: 1 occurrence

Event 1877

Severity: MAJOR
Event Summary: The memory configuration was adjusted to satisfy the Minimum ZI requirement.
Event Class: System
Problem Description:
PDC detected the case where all cells in the Partition were configured as Floating cells, or there was not enough memory to satisfy the Minimum ZI requirement in the available Base cell(s). PDC converted a Floating Cell into a Base Cell in order to obtain enough memory to satisfy the Minimum ZI requirement, and continued.
Cause / Action:
Cause: Review the Chassis Codes and determine if a cell, or DIMMs within a cell, were removed from the Interleave because of an error. If so, correct the problem and reboot. If there was no such event, the Partition is probably misconfigured. Review the configuration and correct it with the Parmanager tools. Action: -
Automated Recovery: None
Event Generation Threshold: 1 occurrence

Event 1878

Severity: FATAL
Event Summary: Internal error: unexpected internal parameter value
Event Class: System
Problem Description:
An internal parameter was found to be incorrect or out of bounds.
Cause / Action:
Cause: Probable hardware problem Action: Contact HP Support personnel to troubleshoot the problem
Automated Recovery: None
Event Generation Threshold: 1 occurrence

Event 1879

Severity: FATAL
Event Summary: Internal error: unexpected internal parameter value.
Event Class: System
Problem Description:
An internal parameter was found to be incorrect or out of bounds.
Cause / Action:
Cause: Probable hardware problem Action: Contact HP Support personnel to troubleshoot the problem
Automated Recovery: None
Event Generation Threshold: 1 occurrence

Event 1880

Severity: FATAL
Event Summary: Internal error: unexpected internal parameter value.
Event Class: System
Problem Description:
An internal parameter was found to be incorrect or out of bounds.
Cause / Action:
Cause: Probable hardware problem Action: Contact HP Support personnel to troubleshoot the problem
Automated Recovery: None
Event Generation Threshold: 1 occurrence

Event 1881

Severity: FATAL
Event Summary: Internal error: unexpected internal parameter value.
Event Class: System
Problem Description:
An internal parameter was found to be incorrect or out of bounds.
Cause / Action:
Cause: Probable hardware problem Action: Contact HP Support personnel to troubleshoot the problem
Automated Recovery: None
Event Generation Threshold: 1 occurrence

Event 1882

Severity: FATAL
Event Summary: Internal error: unexpected internal parameter value.
Event Class: System
Problem Description:
An internal parameter was found to be incorrect or out of bounds.
Cause / Action:
Cause: Probable hardware problem Action: Contact HP Support personnel to troubleshoot the problem
Automated Recovery: None
Event Generation Threshold: 1 occurrence

Event 1883

Severity: FATAL
Event Summary: Internal error: unexpected internal parameter value.
Event Class: System
Problem Description:
An internal parameter was found to be incorrect or out of bounds.
Cause / Action:
Cause: Probable hardware problem Action: Contact HP Support personnel to troubleshoot the problem
Automated Recovery: None
Event Generation Threshold: 1 occurrence

Event 1884

Severity: FATAL
Event Summary: PDC encountered an unexpected event and could not continue.
Event Class: System
Problem Description:
While creating a memory-related data structure, a PDC consistency check detected an illegal condition.
Cause / Action:
Cause: Report the incident and the Data Contents to Hewlett-Packard. Reboot. Reinstall PDC Firmware. Contact HP Support personnel to troubleshoot the problem. Action: -
Automated Recovery: None
Event Generation Threshold: 1 occurrence

Event 1885

Severity: FATAL
Event Summary: PDC encountered an unexpected event and could not continue.
Event Class: System
Problem Description:
PDC called an internal utility function and that function unexpectedly reported an error.
Cause / Action:
Cause: Record the Chassis Codes, and the exact memory configuration, including Base and Floating Cells, and any Cell Local Memory. Report the data to Hewlett-Packard. Reinstall PDC Firmware. Change the memory configuration by adding or removing Floating Cells, Cell Local Memory, deallocating DIMMs, or the cells themselves from the Partition. Action: -
Automated Recovery: None
Event Generation Threshold: 1 occurrence

Event 1886

Severity: MAJOR
Event Summary: Cell Map was changed to satisfy the KGM parameter
Event Class: System
Problem Description:
A cell was excluded from interleaving because its memory had an uncorrectable (DBE) error that would otherwise be interleaved to an address below the KGM (Known Good Memory) threshold. Note that the processors of this cell are still included in the Partition, just its memory has been excluded from interleaving. Note also that the Cell Map will interleave memory correctly and the Partition will run properly. However, some memory has not been interleaved and performance will probably be reduced, possibly significantly.
Cause / Action:
Cause: An uncorrectable (DBE) error in that cell's memory Action: Check the chassis logs for the PDT entry(s) from that cell, or at BCH, issue the command "PDT" and "PDT " from the Service sub-menu. At the customer's convenience, replace the DIMM(s) containing the uncorrectable error and reboot.
Automated Recovery: None
Event Generation Threshold: 1 occurrence

Event 1887

Severity: MAJOR
Event Summary: Discrepancy in the number of overall Cell Map entries available
Event Class: System
Problem Description:
Cell Map code is reporting a discrepancy regarding the number of Cell Map entries available overall. The Cell Map discovered a discrepancy regarding these parameters. The least significant 8 bits of the parameter report how many entries are available with which to interleave the ZI region, and the next 8 bits report the total number of Cell Map entries.
Cause / Action:
Cause: Probable hardware problem Action: Contact HP Support personnel to troubleshoot the problem
Automated Recovery: None
Event Generation Threshold: 1 occurrence

Event 1888

Severity: MAJOR
Event Summary: One or more of the Cell Map entries is not initialized properly
Event Class: System
Problem Description:
Before the Cell Map code starts calculating the Cell Map entries, it checks the Cell Map data structure to which the finished Cell Map entries will be written, for proper initialization values. One or more of the Cell Map elements were not initialized properly. The parameter is a bit mask where a "1" indicates which entry(s) were not initialized properly. Entry 0 is represented by the least significant bit.
Cause / Action:
Cause: Probable hardware problem Action: Contact HP Support personnel to troubleshoot the problem
Automated Recovery: None
Event Generation Threshold: 1 occurrence

Event 1889

Severity: FATAL
Event Summary: There was a fatal error reported by the Cell Map code
Event Class: System
Problem Description:
The Cell Map code encountered a fatal condition and was unable to interleave memory. The return parameter is reported as data. Note that all possible configurations are legal and no configuration should cause this failure. The only possibility where this could occur is when the memory of every cell in the partition has been excluded from the interleave due to KGM violations MEM_CMAP_INTLV_ADJUSTED_FOR_KGM) and is extremely unlikely. If this is the case resolve the KGM problem(s.)
Cause / Action:
Cause: Probable hardware failure KGM violation on every cell in the Partition Action: Contact HP Support personnel to troubleshoot the problem
Automated Recovery: None
Event Generation Threshold: 1 occurrence

Event 1890

Severity: FATAL
Event Summary: Programming the Coherency Controller chip(s) with the Cell Map failed
Event Class: System
Problem Description:
PDC was unable to program the Cell Map into the Coherency Controller chip(s). The failure status is reported in the parameter.
Cause / Action:
Cause: Probable hardware problem. Note that the Coherency Controller chip of every cell in the partition is written with the Cell Map and one or more cells and/or the backplane may be defective. Action: Replace the cell(s) or incrementally remove cell(s) from the Partition to determine which is defective. If all cells seem good, the backplane is probably defective.
Automated Recovery: None
Event Generation Threshold: 1 occurrence

Event 1891

Severity: FATAL
Event Summary: Failure to read partition number from the Stable Complex Profile
Event Class: System
Problem Description:
The call to read the Partition number from the Complex Profile A "Cell Assignments" field failed. Note that this does not mean the Partition number was invalid, rather that it could not be obtained at all. The return status is reported as the parameter.
Cause / Action:
Cause: Probable hardware error Action: Contact HP Support personnel to troubleshoot the problem
Automated Recovery: None
Event Generation Threshold: 1 occurrence

Event 1892

Severity: MAJOR
Event Summary: PDC encountered an unexpected event and could not continue.
Event Class: System
Problem Description:
PDC detected a cell in the Partition that was not a Base or Floating Cell. Possible hardware failure, corrupted Firmware, or Firmware defect.
Cause / Action:
Cause: Check the cell assignments with the Parmanager tools. Try deleting and recreating the Partition in question. Report the incident and the DataContents to Hewlett-Packard. Reboot. Reinstall PDC Firmware. Contact HP Support personnel to troubleshoot the problem. Action: -
Automated Recovery: None
Event Generation Threshold: 1 occurrence

Event 1893

Severity: FATAL
Event Summary: Unrecognized memory type was discovered in internal PDC data structure
Event Class: System
Problem Description:
The Cell Map code, while parsing an internal data structure in order to build the Partition Memory Map, encountered an unrecognized memory descriptor type. The descriptor is reported in the parameter of this chassis code.
Cause / Action:
Cause: Probable hardware problem Action: Contact HP Support personnel to troubleshoot the problem
Automated Recovery: None
Event Generation Threshold: 1 occurrence

Event 1894

Severity: MAJOR
Event Summary: A DIMM was deallocated because the PDT was full
Event Class: System
Problem Description:
A DIMM was successfully deallocated from system for the case where the PDT was full. The system is still configured correctly and will function properly but performance my be reduced.
Cause / Action:
Cause: Deallocation for a full PDT table Action: Replace the DIMM(s) that were deallocated
Automated Recovery: None
Event Generation Threshold: 1 occurrence

Event 1895

Severity: FATAL
Event Summary: Error trying to retrieve CPU type - NOT USED
Event Class: System
Problem Description:
This chassis code is currently unused. It was to be used to indicate a failure returning the cpu type associated with support for DNA 3.0 processing.
Cause / Action:
Cause: PDC error Action: Update PDC and report error to PDC team
Automated Recovery: None
Event Generation Threshold: 1 occurrence

Event 1896

Severity: FATAL
Event Summary: Error trying to retrieve MFG Mode value- NOT USED
Event Class: System
Problem Description:
This chassis code is currently unused. It was to be used to indicate a failure returning the mfg mode associated with support for DNA 3.0 processing.
Cause / Action:
Cause: PDC error Action: Update PDC and report problem to PDC team
Automated Recovery: None
Event Generation Threshold: 1 occurrence

Event 1897

Severity: FATAL
Event Summary: Unsupported CPU Type detected - NOT USED
Event Class: System
Problem Description:
This chassis code is currently not used. It was to indicate that an unsupported cpu type was detected for the current cell for use in DNA 3.0 support. This is a fatal error and will result in the halting of the cell.
Cause / Action:
Cause: PDC error Action: Upgrade PDC and report problem to PDC team
Automated Recovery: None
Event Generation Threshold: 1 occurrence

Event 1898

Severity: FATAL
Event Summary: Cell halted for fatal error
Event Class: System
Problem Description:
Cell halted when fatal error was detected in memory
Cause / Action:
Cause: A fatal error was detected Action: Refer to previous chassis codes for more information on the nature of the problem Contact HP Support personnel to troubleshoot the problem
Automated Recovery: None
Event Generation Threshold: 1 occurrence

Event 1899

Severity: FATAL
Event Summary: Bank Select bits error in programming MBAT values
Event Class: System
Problem Description:
Bank select programming values are incorrect. The cell is halted.
Cause / Action:
Cause: Corrupt Interleaving table - Could be h/w or PDC problem Action: Report event to Response Center Update PDC
Automated Recovery: None
Event Generation Threshold: 1 occurrence

Event 1900

Severity: FATAL
Event Summary: Invalid rank number detected in cell info table
Event Class: System
Problem Description:
Physical Rank number not found in cell info table. The cell is reset.
Cause / Action:
Cause: Corrupted cell info table Action: Report event to Response Center Update PDC
Automated Recovery: None
Event Generation Threshold: 1 occurrence

Event 1901

Severity: FATAL
Event Summary: Rank Number input to Report Syndrome Function is incorrect
Event Class: System
Problem Description:
There was an error detected when verifying the input rank number. The rank number was invalid.
Cause / Action:
Cause: PDC error - contact the PDC team Action: -
Automated Recovery: None
Event Generation Threshold: 1 occurrence

Event 1902

Severity: FATAL
Event Summary: MBAT information does not match address data
Event Class: System
Problem Description:
Input rank, bank, row, and column input parameters do not match Interleaving lookup parameters associated with given GNI address.
Cause / Action:
Cause: Reverse Interleaving or Interleaving lookup translation error Action: Report event to the Response Center Update PDC
Automated Recovery: None
Event Generation Threshold: 1 occurrence

Event 1903

Severity: FATAL
Event Summary: Timeout waiting for MOQ to clear
Event Class: System
Problem Description:
The MOQ failed to clear within the given time limit. The cell is halted.
Cause / Action: Cause: Hardware failure Action: Contact HP Support personnel to troubleshoot the problem
Automated Recovery: None
Event Generation Threshold: 1 occurrence

Event 1904

Severity: FATAL
Event Summary: PDC detects no active memory on cell board - no dimms or all dimms deallocated
Event Class: System
Problem Description:
PDC detects that there is no dimms installed on cell board or all dimms on cell board have been deallocated due to operator deallocation or because of hardware problems.
Cause / Action:
Cause: Hardware problem Action: Insert good dimms into cell and/or re-allocate dimms that have been deallocated
Automated Recovery: None
Event Generation Threshold: 1 occurrence

Event 1905

Severity: FATAL
Event Summary: PDC could not mark parity error dimm for deallocation
Event Class: System
Problem Description:
PDC could not mark a DIMM for deallocation that needed to be marked for deallocation because of the presence of a memory parity error on the MID bus containing that DIMM. This is a fatal error and will result in the halting of the cell.
Cause / Action:
Cause: PDC problem Action: Upgrade PDC and report problem to PDC team
Automated Recovery: None
Event Generation Threshold: 1 occurrence

Event 1906

Severity: MAJOR
Event Summary: Cell PDT table is full
Event Class: System
Problem Description:
PDC has tried to add a new entry in the cell PDT table, but the PDT table is currently full. PDC will search the PDT table for the memory rank with the most number of entries, and deallocate that rank. PDC will than reset the cell which upon reboot will clear the PDT table of all entries related to that deallocated rank.
Cause / Action:
Cause: Bad DIMM/DIMMs/memory system Action: Contact HP Support personnel to troubleshoot the problem
Automated Recovery: None
Event Generation Threshold: 1 occurrence

Event 1907

Severity: FATAL
Event Summary: Slave attempting to execute memory write-random code
Event Class: System
Problem Description:
Slave CPU attempting to execute memory write-random code although only monarch should be executing code.
Cause / Action:
Cause: PDC error Action: Report the event to the Response Center Update PDC
Automated Recovery: None
Event Generation Threshold: 1 occurrence

Event 1908

Severity: FATAL
Event Summary: Slave failed to complete write-random code
Event Class: System
Problem Description:
Slave failed to complete write-random code. Monarch CPU should only execute code.
Cause / Action:
Cause: PDC error Action: Report the event to the Response Center Update PDC
Automated Recovery: None
Event Generation Threshold: 1 occurrence

Event 1909

Severity: FATAL
Event Summary: Slave attempting to execute memory read-random code
Event Class: System
Problem Description:
Slave CPU attempting to execute memory read-random code although only monarch should be executing code.
Cause / Action:
Cause: PDC error Action: Report the event to the Response Center Update PDC
Automated Recovery: None
Event Generation Threshold: 1 occurrence

Event 1910

Severity: FATAL
Event Summary: Slave failed to complete read-random code
Event Class: System
Problem Description:
Slave failed to complete read-random code. Monarch CPU should only execute code.
Cause / Action:
Cause: PDC error Action: Report the event to the Response Center Update PDC
Automated Recovery: None
Event Generation Threshold: 1 occurrence

Event 1911

Severity: INFORMATION
Event Summary: The Chassis Code output FIFO is full
Event Class: System
Problem Description:
While attempting to output a chassis log, PDC detected that the chassis code output FIFO is full. The current chassis log may have been lost. Future logs may be lost.
Cause / Action:
Cause: The Cell PDH Controller (PDHC) or the GSP is no longer reading logs from the FIFO or is unable to read them fast enough. Action: Check the integrity of the PDHC, GSP, and USB Contact HP Support personnel to troubleshoot the problem
Automated Recovery: None
Event Generation Threshold: 1 occurrence

Event 1912

Severity: MAJOR
Event Summary: The checksum for the Cell Info data structure is invalid
Event Class: System
Problem Description:
The Cell Info (AKA Cell Configuration) structure contains an incorrect checksum while attempting to validate the structure. The Cell Info structure may be corrupt. Data Field: Pointer to the Cell Info structure.
Cause / Action: Cause: Corruption of ICM Internal PDC error Action: Contact HP Support personnel to troubleshoot the problem
Automated Recovery: None
Event Generation Threshold: 1 occurrence

Event 1913

Severity: MAJOR
Event Summary: Cell Info data is not marked invalid while updating Core I/O Present
Event Class: System
Problem Description:
Whenever the Cell Info (AKA Cell Configuration) structure is being updated, its valid bit should be deasserted. This was not the case while updating the Core I/O Present field. Data Field: Global cell # of cell containing the target Cell Info structure.
Cause / Action:
Cause: Corruption of ICM Internal PDC error Action: Contact HP Support personnel to troubleshoot the problem
Automated Recovery: None
Event Generation Threshold: 1 occurrence

Event 1914

Severity: MAJOR
Event Summary: Value of Boot Inhibit field of the Cell Info data structure is illegal
Event Class: System
Problem Description:
The new value for the Boot Inhibit field of the Cell Info (AKA Cell Configuration) structure is found to be illegal while updating the Cell Info structure. Data Field: Illegal inhibit value
Cause / Action:
Cause: Internal PDC error Action: Contact HP Support personnel to troubleshoot the problem.
Automated Recovery: None
Event Generation Threshold: 1 occurrence

Event 1915

Severity: MAJOR
Event Summary: An error occurred during initialization of the Cell Info structure
Event Class: System
Problem Description:
An error occurred during initialization of the Cell Info (AKA Cell Configuration) structure header. The Cell Info data may be incomplete. Data Field: Return status of the internal PDC function CellInfoInitHeader().
Cause / Action: Cause: Corruption of Software semaphores Corruption of ICM Action: Locate source of corruption Contact HP Support personnel to troubleshoot the problem
Automated Recovery: None
Event Generation Threshold: 1 occurrence

Event 1916

Severity: MAJOR
Event Summary: Detected an invalid state value when updating the Cell Info structure
Event Class: System
Problem Description:
While updating the Cell_State field of the Cell Info (AKA Cell Configuration) structure in ICM, PDC detected an invalid value for the cell state value. This indicates an internal problem within PDC. Data Field: Invalid value
Cause / Action: Cause: Internal PDC error. Action: Contact HP Support personnel to troubleshoot the problem
Automated Recovery: None
Event Generation Threshold: 1 occurrence

Event 1917

Severity: FATAL
Event Summary: Unable to update the cell state field of the Cell Info structure.
Event Class: System
Problem Description:
Unable to update the Cell Info structure with the cell state for all cells within the partition. This code is issued for a number of problems including fabric problems, target cells not in partition, invalid arguments, PDC semaphore problems, and corruption of the cell info structure.
Cause / Action:
Cause: Loss of fabric connectivity. Cause: Corruption of PDH memory. Cause: Internal PDC error. Action: Action: Reset Partition. Action: Contact HP Support personnel to troubleshoot the problem.
Automated Recovery: None
Event Generation Threshold: 1 occurrence

Event 1918

Severity: FATAL
Event Summary: A hardware failure with a PDH Raiser Card
Event Class: System
Problem Description:
A hardware failure has been detected in a PDH raiser board. The previous chassis log indicates the nature of the failure. Data Field: Physical location of the cell containing the faulty Dillon
Cause / Action:
Cause: The cause is in the previously output chassis log Action: Contact HP Support personnel to troubleshoot the problem
Automated Recovery: None
Event Generation Threshold: 1 occurrence

Event 1919

Severity: FATAL
Event Summary: Unable to access remote cell's revision register.
Event Class: System
Problem Description:
The local cell is not able to access the cell board revision register on the target cell.
Cause / Action:
Cause: Fabric connectivity problem. Action: Contact HP Support personnel to troubleshoot the problem
Automated Recovery: None
Event Generation Threshold: 1 occurrence

Event 1920

Severity: FATAL
Event Summary: PDC detected an error reading PDH register
Event Class: System
Problem Description:
PDC detected an error trying to read the given PDH register. This chassis code is associated with PDH_GET_PDH_REGS_FAILED_PDH_REGISTER which identifies the PDH register that was trying to be read.
Cause / Action:
Cause: Hardware error Action: Contact HP Support personnel to troubleshoot the problem Cause: PDC error Action: Upgrade PDC
Automated Recovery: None
Event Generation Threshold: 1 occurrence

Event 1921

Severity: MAJOR
Event Summary: CPU already owns the hardware semaphore when attempting to lock it
Event Class: System
Problem Description:
The executing CPU already owns the Dillon "hardware" semaphore when attempting to lock it. This is the register located at offsets 0x5F00B0 through 0x5F04A8. Data Field: Target cell's physical location.
Cause / Action:
Cause: Corruption of the hardware semaphore Internal PDC error Action: Contact HP Support personnel to troubleshoot the problem
Automated Recovery: None
Event Generation Threshold: 1 occurrence

Event 1922

Severity: MAJOR
Event Summary: The PDH Raiser Card's "h/w" semaphore is not locked when attempting to unlock it
Event Class: System
Problem Description:
The PDH RAiser Card's "hardware" semaphore is not locked when attempting to unlock it. This is the register located at offsets 0x5F00B0 through 0x5F04A8. Data Field: Target cell's physical location
Cause / Action: Cause: Corruption of the hardware semaphore Internal PDC error Action: Contact HP Support personnel to troubleshoot the problem
Automated Recovery: None
Event Generation Threshold: 1 occurrence

Event 1923

Severity: MAJOR
Event Summary: CPU does not own PDH Raiser Card's "h/w" semaphore when attempting to unlock it
Event Class: System
Problem Description:
The executing CPU does not own the Dillon "hardware" semaphore when attempting to unlock it. Another CPU owns the semaphore. This is the register located at offsets 0x5F00B0 through 0x5F04A8. Data Field: Physical location of the current owning CPU
Cause / Action:
Cause: Corruption of the hardware semaphore Internal PDC error Action: Contact HP Support personnel to troubleshoot the problem
Automated Recovery: None
Event Generation Threshold: 1 occurrence

Event 1924

Severity: MAJOR
Event Summary: An invalid local CPU number was detected.
Event Class: System
Problem Description:
An internal PDC verification of the local CPU number detected an illegal value.
Cause / Action: Cause: Internal PDC error. Action: Contact HP Support personnel to troubleshoot the problem.
Automated Recovery: None
Event Generation Threshold: 1 occurrence

Event 1925

Severity: MAJOR
Event Summary: An invalid software semaphore ID was passed as an argument
Event Class: System
Problem Description:
An internal function within PDC passed an invalid software semaphore ID as an argument. Data Field: Invalid argument
Cause / Action:
Cause: Internal PDC error Action: Contact HP Support personnel to troubleshoot the problem.
Automated Recovery: None
Event Generation Threshold: 1 occurrence

Event 1926

Severity: MAJOR
Event Summary: An invalid software semaphore wait flag was passed as an argument
Event Class: System
Problem Description:
An internal function within PDC passed an invalid software semaphore wait flag as an argument. Data Field: Invalid argument
Cause / Action:
Cause: Internal PDC error Action: Contact HP Support personnel to troubleshoot the problem.
Automated Recovery: None
Event Generation Threshold: 1 occurrence

Event 1927

Severity: FATAL
Event Summary: A read-after-write of PDH Raiser Card's Micro General Purpose 2 register failed.
Event Class: System
Problem Description:
A read-after-write test of PDH Raiser Card's Micro General Purpose 2 register failed. This register contains PDC's Micro semaphore ownership flag.
Cause / Action: Cause: Faulty PDH Raiser Card's or CC. Action: Contact HP Support personnel to troubleshoot the problem.
Automated Recovery: None
Event Generation Threshold: 1 occurrence

Event 1928

Severity: FATAL
Event Summary: A read-after-write of PDH Raiser Card's Micro General Purpose 3 register failed.
Event Class: System
Problem Description:
A read-after-write test of Dillon's Micro General Purpose 3 register failed. This register contains the PDHC's Micro semaphore ownership flag.
Cause / Action: Cause: Faulty Dillon or path to Dillon. Action: Contact HP Support personnel to troubleshoot the problem
Automated Recovery: None
Event Generation Threshold: 1 occurrence

Event 1929

Severity: FATAL
Event Summary: A read-after-write test of a PDH Micro Status register failed
Event Class: System
Problem Description:
After writing to a PDH Raiser Card's Micro Status register, PDC reads the register to verify the write took place. This verification failed. Data Field: Physical location of the cell with the faulty Dillon
Cause / Action:
Cause: A defective PDH Raiser Card Action: Contact HP Support personnel to troubleshoot the problem
Automated Recovery: None
Event Generation Threshold: 1 occurrence

Event 1930

Severity: FATAL
Event Summary: PDC detected an error trying to write value to PDH register
Event Class: System
Problem Description:
PDC detected an error trying to write to the given PDH register. This chassis code is associated with PDH_SET_PDH_REGS_FAILED_PDH_REGISTER which identifies the PDH register that was trying to be written.
Cause / Action:
Cause: Hardware error Action: Contact HP Support personnel to troubleshoot the problem Cause: PDC error Action: Upgrade PDC
Automated Recovery: None
Event Generation Threshold: 1 occurrence

Event 1931

Severity: MAJOR
Event Summary: PDC detected a semaphore error during a Proc call
Event Class: System
Problem Description:
PDC detected a semaphore error during a Proc call. The previous chassis log indicates the nature of the error. This log indicates which Proc was being executed. The data field contains the Proc number in the upper 32 bits and the Proc option in the lower 32 bits. This log is only output when a CRITICAL condition exists and is useful for debugging. Data Field: PDC procedure call # << 32 | PDC procedure call option
Cause / Action:
Cause: See the previously emitted chassis log Action: See the previously emitted chassis log
Automated Recovery: None
Event Generation Threshold: 1 occurrence

Event 1932

Severity: MAJOR
Event Summary: PDC is unable to report the Proc number and option
Event Class: System
Problem Description:
An error was detected by PDC during a Proc call. The previous chassis log indicates the nature of the error. PDC is unable to report which Proc was executing when the error occurred. The data field contains the return status from PDC's internal function GetCurrentPdceCall(). Data Field: proc return status
Cause / Action:
Cause: Memory corruption of the Proc log Corruption of the DR_2 register Action: Locate source of corruption Contact HP Support personnel to troubleshoot the problem
Automated Recovery: None
Event Generation Threshold: 1 occurrence

Event 1933

Severity: MAJOR
Event Summary: Software semaphore already owned when attempting to lock it
Event Class: System
Problem Description:
A software semaphore is already owned by the executing CPU when attempting to lock it. Data Field: Identifier of the target software semaphore
Cause / Action:
Cause: A TOC or HPMC has interrupted a PDC procedure call. NVM corruption Internal PDC error Action: Locate the source of corruption Contact HP Support personnel to troubleshoot the problem
Automated Recovery: None
Event Generation Threshold: 1 occurrence

Event 1934

Severity: MAJOR
Event Summary: Software semaphores were not initialized when attempting to use them
Event Class: System
Problem Description:
The software semaphores are not initialized when attempting to use them. PDC should not attempt to use the software semaphores before they are initialized. Data Field: Target cell's physical location
Cause / Action: Cause: Corruption of Dillon's MP Selection 5 register Internal PDC error Action: Locate the source of the corruption Contact HP Support personnel to troubleshoot the problem
Automated Recovery: None
Event Generation Threshold: 1 occurrence

Event 1935

Severity: MAJOR
Event Summary: A Software semaphore is not locked as expected
Event Class: System
Problem Description:
During an internal verification, PDC finds a Software semaphore is not locked as expected. PDC may have been accessing a semaphore protected resource without owning the semaphore. Corruption may have resulted. The data field contains information on the target semaphore. The software semaphore ID is in the upper 32 bits and the cell's global number is in the lower 32 bits. Data Field: S/W SM4 ID << 32 | Cell #
Cause / Action:
Cause: NVM corruption Internal PDC error Action: Contact HP Support personnel to troubleshoot the problem
Automated Recovery: None
Event Generation Threshold: 1 occurrence

Event 1936

Severity: MAJOR
Event Summary: A Software semaphore is not locked when attempting to unlock it
Event Class: System
Problem Description:
While attempting to unlock a Software semaphore, PDC finds the target semaphore is not locked. PDC may have been accessing semaphore protected resources without owning the semaphore. Corruption may have resulted. The data field contains the Software semaphore ID of the target semaphore. Data Field: S/W SM4 ID
Cause / Action:
Cause: NVM corruption Internal PDC error Action: Locate the source of the corruption Contact HP Support personnel to troubleshoot the problem
Automated Recovery: None
Event Generation Threshold: 1 occurrence

Event 1937

Severity: MAJOR
Event Summary: Attempting to release a Software semaphore owned by another CPU
Event Class: System
Problem Description:
While attempting to unlock a Software semaphore, PDC finds the target semaphore is owned by another CPU. A CPU should only unlock semaphores which it owns. Corruption may have resulted. The data field contains the Software semaphore ID of the target semaphore. Data Field: S/W SM4 ID
Cause / Action:
Cause: NVM corruption Internal PDC error Action: Locate the source of the corruption Contact HP Support personnel to troubleshoot the problem
Automated Recovery: None
Event Generation Threshold: 1 occurrence

Event 1938

Severity: MAJOR
Event Summary: Attempt to lock another cell's micro SM4 before soft SM4 initialized
Event Class: System
Problem Description:
PDC was attempting to illegally lock another cell's PDH Raiser Card's Micro semaphore. By convention within PDC, a remote Micro semaphore can only be obtained if the Cell Global Software semaphore on the remote cell is owned. This chassis log indicates the remote cell's software semaphore's have not been initialized; hence the required Software semaphore is not owned. Data Field: Target cell's physical location
Cause / Action:
Cause: Corruption of Dillon's MP Selection 5 register Internal PDC error Action: Locate the source of the corruption Contact HP Support personnel to troubleshoot the problem
Automated Recovery: None
Event Generation Threshold: 1 occurrence

Event 1939

Severity: MAJOR
Event Summary: Unexpected reset of the Cell PDH Controller (PDHC) has been detected
Event Class: System
Problem Description:
During the execution of the Proc PDC_PAT_EVENT[Scan Event], the EXT_AH event is detected. This means the cell PDH controller (PDHC) has been reset. The Proc will return a -3 status to the caller. Data Field: Physical location of the cell containing the PDHC
Cause / Action:
Cause: Unknown source of cell PDH controller (PDHC) reset Action: Cause: Determine source of reset Action: Contact HP Support personnel to troubleshoot the problem
Automated Recovery: None
Event Generation Threshold: 1 occurrence

Event 1940

Severity: MAJOR
Event Summary: PDH Micro semaphore already owned by PDC when attempting to lock it
Event Class: System
Problem Description:
PDC was attempting to lock a PDH Raiser Card's Micro semaphore and finds it already owned by PDC. Data Field: Physical location of the cell containing the PDHC
Cause / Action:
Cause: Corruption of Dillon's Micro semaphore register Internal PDC error Action: Locate source of corruption Contact HP Support personnel to troubleshoot the problem
Automated Recovery: None
Event Generation Threshold: 1 occurrence

Event 1941

Severity: MAJOR
Event Summary: A PDH Raiser Card's Micro semaphore register was read from an illegal location
Event Class: System
Problem Description:
The owner field of the target Dillon Micro semaphore is neither PDC nor the Cell PDH Controller (PDHC). This indicates the PDH Raiser Card's Micro semaphore register was read from an unarchitected location. The data field contains the owner field of the target Micro semaphore register. Data Field: SM4 owner field
Cause / Action:
Cause: Corrupted Micro semaphore register Action: Find source of corruption Contact HP Support personnel to troubleshoot the problem
Automated Recovery: None
Event Generation Threshold: 1 occurrence

Event 1942

Severity: MAJOR
Event Summary: A PDH Raiser Card's Micro semaphore is not locked when expected
Event Class: System
Problem Description:
During an internal verification by PDC, the target cell's PDH Raiser Card's Micro semaphore register is not locked as expected. PDC may have been accessing a FATAL region protected by this semaphore without owning the semaphore. Corruption may have resulted. Data Field: Physical location of the cell containing the target Dillon
Cause / Action:
Cause: Corruption of Dillon's Micro semaphore register Internal PDC error Action: Locate source of corruption Contact HP Support personnel to troubleshoot the problem
Automated Recovery: None
Event Generation Threshold: 1 occurrence

Event 1943

Severity: MAJOR
Event Summary: Micro semaphore owned by both PDC and the PDHC.
Event Class: System
Problem Description:
The Micro semaphore ownership flags indicate that both PDC and the PDHC believe they own the semaphore.
Cause / Action:
Cause: Dillon's Micro General Purpose registers 2 and 3 corrupted. Action: Find source of corruption and reboot. Cause: PDC or the PDHC improperly implementing the algorithms for dealing with the Micro semaphore. Action: Contact HP Support personnel to troubleshoot the problem. Cause: Dillon hardware error concerning the Micro semaphore register or the Micro General Purpose registers 2 and 3. Action: Contact HP Support personnel to troubleshoot the problem.
Automated Recovery: None
Event Generation Threshold: 1 occurrence

Event 1944

Severity: MAJOR
Event Summary: The PDHC's Micro Semaphore ownership flag is corrupt.
Event Class: System
Problem Description:
The PDHC's Micro Semaphore ownership flag is corrupt. This flag is contained in Dillon's Micro General Purpose 3 register.
Cause / Action:
Cause: PDH's Micro General Purpose register 3 corrupted. Action: Find source of corruption and reboot. Cause: PDH hardware error with the Micro General Purpose register 3. Action: Replace cell board. Cause: PDC or the PDHC improperly implementing the algorithms for dealing with the Micro semaphore. Action: Upgrade PDC or the PDHC firmware.
Automated Recovery: None
Event Generation Threshold: 1 occurrence

Event 1945

Severity: MAJOR
Event Summary: A PDH Micro semaphore is unowned when attempting to unlock it
Event Class: System
Problem Description:
PDC is attempting to unlock a PDH Micro semaphore when it discovers the semaphore is unlocked. This internal check indicates that PDC may have been accessing a FATAL region protected by this semaphore without owning the semaphore. Corruption may have resulted. Data Field: Physical location of the cell containing the target Dillon
Cause / Action:
Cause: Corruption of PDH's Micro semaphore register Internal PDC error Action: Contact HP Support personnel to troubleshoot the problem. Action: Locate source of corruption Contact HP Support personnel to troubleshoot the problem
Automated Recovery: None
Event Generation Threshold: 1 occurrence

Event 1946

Severity: MAJOR
Event Summary: SM4 is owned by PDH Controller when PDC is attempting to unlock it
Event Class: System
Problem Description:
PDC is attempting to unlock a PDH Micro semaphore when it discovers the semaphore is owned by the Cell PDH Controller (PDHC). This internal check indicates that PDC may have been accessing a FATAL region protected by this semaphore without owning the semaphore. Corruption may have resulted. Data Field: Physical location of the cell containing the target Dillon
Cause / Action:
Cause: Illegal read of PDH's Micro semaphore register Internal PDC error Action: Find source of corruption Contact HP Support personnel to troubleshoot the problem
Automated Recovery: None
Event Generation Threshold: 1 occurrence

Event 1947

Severity: MAJOR
Event Summary: Semaphore is owned by PDH Controller when PDC is attempting to verify
Event Class: System
Problem Description:
PDC is attempting to verify that PDC owns a PDH Micro semaphore but finds the Cell PDH Controller (PDHC) currently owns the semaphore. This internal check indicates that PDC may have been accessing a FATAL region protected by this semaphore without owning the semaphore. Corruption may have resulted. Data Field: Physical location of the cell containing the target Dillon
Cause / Action:
Cause: Illegal read of PDH's Micro semaphore register Internal PDC error Action: Find source of corruption Contact HP Support personnel to troubleshoot the problem
Automated Recovery: None
Event Generation Threshold: 1 occurrence

Event 1948

Severity: MAJOR
Event Summary: Attempted access to SM4 on remote cell before SM4 is initialized
Event Class: System
Problem Description:
PDC is attempting to access a remote cell's Dillon Micro semaphore when the software semaphores are uninitialized on the remote cell. By convention, PDC must own the Cell Global Software semaphore before accessing the micro semaphore on a remote cell. Data Field: Physical location of the cell containing the target Dillon
Cause / Action:
Cause: Corruption of Dillon's MP Selection 5 register Internal PDC error Action: Locate the source of the corruption Contact HP Support personnel to troubleshoot the problem
Automated Recovery: None
Event Generation Threshold: 1 occurrence

Event 1949

Severity: MAJOR
Event Summary: Unable to lock Micro semaphore.
Event Class: System
Problem Description:
PDC has not been able to lock the Micro semaphore in PDH after repeated attempts. This is due to a bug (HD2496) in Dillon 2.0 in which read-read conflicts between PDC and the PDHC result in neither entity locking the semaphore. At this time, there is no intent to fix the bug in Dillon 2.0 so the only option is to reset the cell.
Cause / Action:
Cause: Hardware bug in PDH 2.0. Action: Reset the cell--both PDC and the PDHC.
Automated Recovery: None
Event Generation Threshold: 1 occurrence

Event 1950

Severity: MAJOR
Event Summary: Invalid address passed to TogoWriteVerify().
Event Class: System
Problem Description:
An invalid address was passed to TogoWriteVerify(). Data Field: CSR Address that passed to TogoWriteVerify()
Cause / Action:
Cause: PDC Runtime Error Possible memory corruption or misuse of functions Action: Report this error to the Response Center Reset the cell Update PDC
Automated Recovery: None
Event Generation Threshold: 1 occurrence

Event 1951

Severity: MAJOR
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.
Cause / Action:
An unanticipated error occurred. Contact HP Support personnel to analyze the IPMI FPL log. Action: -
Automated Recovery: None
Event Generation Threshold: 1 occurrence

Event 1952

Severity: MAJOR
Event Summary: Reading the XBC Global Semaphore register failed
Event Class: System
Problem Description:
While attempting to get the XBC Global Semaphore, the read to the register failed. Data Field: XBC address
Cause / Action:
Cause: XBC read failure. Action: check XBC, check link, check CC
Automated Recovery: None
Event Generation Threshold: 1 occurrence

Event 1953

Severity: CRITICAL
Event Summary: An attempted takeover of the XBC Global Semaphore has failed.
Event Class: System
Problem Description:
A failure occurred while attempting to takeover the XBC Global semaphore. This is a sign of a fabric connectivity problem. Data Field: (XBC Port Number << 44) | (XBC number << 32) | return status
Cause / Action: Cause: Fabric Access Error Action: Check XBC. Check Links/Flex Cables.
Automated Recovery: None
Event Generation Threshold: 1 occurrence

Event 1954

Severity: FATAL
Event Summary: The cabinet number for the cabinet containing the XBC is incorrect.
Event Class: System
Problem Description:
The cabinet number for the cabinet containing the XBC is incorrect. Data Field: (Expected external port << 32) | external port determined from CC
Cause / Action:
Cause: The cabinet number for the cabinet containing the XBC is incorrect. The cabinet numbering rules are: Left cabinets use even numbers, Right cabinets use odd numbers, and Left / Right cabinet pairs must be numbered sequentially. Action: Check all the cabinet numbers Have your HP Support Representative check the System Utilities
Automated Recovery: None
Event Generation Threshold: 1 occurrence

Event 1955

Severity: FATAL
Event Summary: The cabinet numbering is non-sequential.
Event Class: System
Problem Description:
The cabinet numbering is non-sequential. Data Field Value (Togo number << 32) | neighbor identification
Cause / Action:
Cause: The cabinet numbering is non-sequential. Cause: The cabinet numbering is non-sequential. The cabinet numbering rules are: Left cabinets use even numbers, Right cabinets use odd numbers, and Left / Right cabinet pairs must be numbered sequentially. Action: Check all the cabinet numbers Have your HP Support Representative check the System Utilities Action: -
Automated Recovery: None
Event Generation Threshold: 1 occurrence

Event 1956

Severity: MAJOR
Event Summary: The local cell is not connected to fabric.
Event Class: System
Problem Description:
While testing fabric route, the local cell could not read from the Coherency Controller (CC) or the CC was not connected to a XBC.
Cause / Action:
Cause: Hardware problem Action: Check CC to XBC link. Check CC.
Automated Recovery: None
Event Generation Threshold: 1 occurrence

Event 1957

Severity: MAJOR
Event Summary: The fabric link is not useable due to errors on this port.
Event Class: System
Problem Description:
While testing the route to the target cell, a port was found to be unusable.
Cause / Action:
Cause: A XBC port was found to have errors while traversing the route to the target XBC. Action: Look for additional chassis codes that provide more detailed information. Contact HP Support personnel to analyze the flex cables and crossbar chip.
Automated Recovery: None
Event Generation Threshold: 1 occurrence

Event 1958

Severity: MAJOR
Event Summary: Unexpected errors were encountered while testing the route to the target cell.
Event Class: System
Problem Description:
While testing a port on the route to the target cell, an unknown error was encountered. Data Field: (target cell << 56) | (cell port << 44) | (crossbar num << 32)
Cause / Action:
Cause: A XBC port was found to have errors while traversing the route to the target XBC. Action: Look for additional chassis codes that provide more detailed information. Contact HP Support personnel to analyze the flex cables, crossbar chip, and CC.
Automated Recovery: None
Event Generation Threshold: 1 occurrence

Event 1959

Severity: MAJOR
Event Summary: The target XBC's link to the target cell is not useable.
Event Class: System
Problem Description:
While examining the route to the target cell, an unexpected failure occurred while traversing from the target XBC to the target cell.
Cause / Action:
Cause: A XBC port was found to have errors while traversing the route to the target XBC. Action: Look for additional chassis codes that provide more detailed information. Contact HP Support personnel to analyze the flex cables, crossbar chip, and CC.
Automated Recovery: None
Event Generation Threshold: 1 occurrence

Event 1960

Severity: MAJOR
Event Summary: The target XBC's link to the the target cell is not useable.
Event Class: System
Problem Description:
The fabric route from the local cell to the target cell is being examined. A problem was encountered on the link to the target cell. Data Field: (target cell << 56) | (xbc num << 32) \
Cause / Action:
Cause: There was a problem with the target cell's link. Either an error such as LOL, FE, or one side of the link is powered off. Action: Contact HP Support personnel to analyze the cell power, XBC, CC
Automated Recovery: None
Event Generation Threshold: 1 occurrence

Event 1961

Severity: MAJOR
Event Summary: A failure occurred when testing the route from the local XBC to the target XBC.
Event Class: System
Problem Description:
While examining the route to the target cell, an unexpected failure occurred while traversing from the local XBC to the target XBC. Data Field: (target cell << 56) | (xbc num << 32)
Cause / Action:
Cause: A XBC port was found to have errors while traversing the route to the target XBC. Action: Look for additional chassis codes that provide more detailed information. Contact HP Support personnel to analyze the flex cables, crossbar chip, and CC.
Automated Recovery: None
Event Generation Threshold: 1 occurrence

Event 1962

Severity: MAJOR
Event Summary: The fabric route from the local XBC to the target XBC could not be traversed.
Event Class: System
Problem Description:
The fabric route from the local cell to the target cell is being examined. A problem was encountered on the route to the target's XBC. Data Field: (target cell << 56) | (xbc num << 32)
Cause / Action:
Cause: A link between the local XBC and the target XBC was not alive. This means the link is either not yet initialized, powered off, or a Fatal Error has been encountered preventing the link from being used. Action: Look for additional chassis codes to provide more detailed info. Contact HP Support personnel to analyze the port status registers on the XBC, flex cables, and XBC.
Automated Recovery: None
Event Generation Threshold: 1 occurrence

Event 1963

Severity: MAJOR
Event Summary: The XBC global semaphore was not locked during a PDC procedure call
Event Class: System
Problem Description:
During a PDC procedure, the XBC's global semaphore was expected to be locked, but the semaphore was found not to be locked or the lock couldn't be verified. Data Field: (cell port << 44) | (xbc num << 32) | xbc register
Cause / Action:
Cause: There was a problem accessing the XBC. Action: Contact HP Support personnel to analyze the crossbar chip, flex cables, CC, PDC.
Automated Recovery: None
Event Generation Threshold: 1 occurrence

Event 1964

Severity: MAJOR
Event Summary: Could not route across port 4 of the local XBC.
Event Class: System
Problem Description:
Couldn't get the XBC num connected to the local XBC Port 4 or port 4 is not healthy. Data Field: (port << 44) | (xbc num << 32) | ret status
Cause / Action: Cause: Local XBC port 4 link not healthy or local XBC failing. Action: Contact HP Support personnel to analyze the fabric.
Automated Recovery: None
Event Generation Threshold: 1 occurrence

Event 1965

Severity: MAJOR
Event Summary: Could not complete remote routing of the kitty-korner XBC.
Event Class: System
Problem Description:
There was a problem performing remote routing on the kitty-korner XBC. Chassis codes sent before this one may provide more details about the exact nature of the problem. The executing cell will attempt a fabricless boot. Data Field: (xbc num << 32) | return status
Cause / Action:
Cause: A failure was encountered while performing remote routing on the kitty-korner XBC, most likely due to a problem with the system backplane or local cell. Action: Contact HP Support personnel to analyze the fabric.
Automated Recovery: None
Event Generation Threshold: 1 occurrence

Event 1966

Severity: MAJOR
Event Summary: Could not complete remote routing of the mirror XBC.
Event Class: System
Problem Description:
There was a problem performing remote routing on the mirror XBC. Chassis codes sent before this one may provide more details about the exact nature of the problem. The executing cell will attempt a fabricless boot. Data Field: (xbc num << 32) | return status
Cause / Action:
Cause: A failure was encountered while performing remote routing on the mirror XBC, most likely due to a problem with the system backplane or local cell. Action: Contact HP Support personnel to analyze the fabric.
Automated Recovery: None
Event Generation Threshold: 1 occurrence

Event 1967

Severity: MAJOR
Event Summary: Could not complete remote routing of the sister XBC.
Event Class: System
Problem Description:
There was a problem performing remote routing on the sister XBC. Chassis codes sent before this one may provide more details about the exact nature of the problem. The executing cell will attempt a fabricless boot. Data Field: (xbc num << 32) | return status
Cause / Action:
Cause: A failure was encountered while performing remote routing on the sister XBC, most likely due to a problem with the system backplane or local cell. Action: Contact HP Support personnel to analyze the fabric.
Automated Recovery: None
Event Generation Threshold: 1 occurrence

Event 1968

Severity: MAJOR
Event Summary: Could not complete remote routing of the sister XBC.
Event Class: System
Problem Description:
This system is a Thinboy. There was a problem performing remote routing on the sister XBC. Chassis codes sent before this one may provide more details about the exact nature of the problem. The executing cell will attempt a fabricless boot. Data Field: (xbc num << 32) | return status
Cause / Action: Cause: A failure was encountered while performing remote routing on the sister XBC, most likely due to a problem with the system backplane or local cell. Action: Contact HP Support personnel to analyze the fabric.
Automated Recovery: None
Event Generation Threshold: 1 occurrence

Event 1969

Severity: MAJOR
Event Summary: Could not complete remote routing of the local XBC.
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 executing cell will attempt a fabricless boot. Data Field: (xbc num << 32) | return status
Cause / Action:
Cause: A failure was encountered while performing remote routing on the local XBC, most likely due to a problem with the system backplane or local cell. Action: Contact HP Support personnel to analyze the fabric.
Automated Recovery: None
Event Generation Threshold: 1 occurrence

Event 1970

Severity: MAJOR
Event Summary: Too many broken links: ports 4 & 5 not routable
Event Class: System
Problem Description:
Ports 4 and 5 of the local XBC were not routable. However, port 5 of the sister XBC was routable and connected to another XBC. Therefore, the system is a fatboy with too many broken links. The executing cell will attempt a fabricless boot. Data Field: (port << 44) | (xbc num << 32) | ret status
Cause / Action:
Cause: Ports 4 and 5 of the local XBC are not healthy. Action: Contact HP Support personnel to analyze the fabric.
Automated Recovery: None
Event Generation Threshold: 1 occurrence

Event 1971

Severity: MAJOR
Event Summary: PDC cannot determine the system's topology
Event Class: System
Problem Description:
PDC initially determines the system's topology early in fabric discovery. Later in fabric discovery PDC compares the topology found by DiscoverTopology with the topology it sees. If the two do not match this chassis code is sent. Data Field: (xbc num << 32) | topology
Cause / Action:
Cause: There is a fabric problem that causes two different XBCs to appear as if they have different topologies. Action: Contact HP Support personnel to analyze the fabric.
Automated Recovery: None
Event Generation Threshold: 1 occurrence

Event 1972

Severity: MAJOR
Event Summary: A XBC read failed due to a Multi-Bit Error
Event Class: System
Problem Description:
A XBC read failed due to a Multi-Bit Error. Data Field: return data
Cause / Action:
Cause: likely fabric hardware failure Action: Contact HP Support personnel to analyze the fabric.
Automated Recovery: None
Event Generation Threshold: 1 occurrence

Event 1973

Severity: MAJOR
Event Summary: There was a failure reading from the XBC.
Event Class: System
Problem Description:
The routing forward progress is stored in a scratch register on the XBC. A read of that register failed during an audit of the XBC Global Semaphore. This indicates a connectivity failure. Data Field: (port << 44) | (xbc num << 32) | ret status
Cause / Action:
Cause: likely fabric hardware failure Action: Contact HP Support personnel to analyze the fabric.
Automated Recovery: None
Event Generation Threshold: 1 occurrence

Event 1974

Severity: MAJOR
Event Summary: PDC failed to unlock the fabric as it tried to release the XBC Semaphore.
Event Class: System
Problem Description:
The fabric has to be unlocked for PDC to release the fabric semaphore. PDC tried to unlock the fabric and failed. Data Field: (cell << 56) | (port << 44) | (xbc << 32) | return status
Cause / Action: Cause: There was a problem reading the XBC semaphore. Or there was a problem writing the XBC key. Action: Contact HP Support personnel to analyze the fabric, crossbar, and PDC
Automated Recovery: None
Event Generation Threshold: 1 occurrence

Event 1975

Severity: MAJOR
Event Summary: PDC failed to read an XBC SM4 while trying to release it.
Event Class: System
Problem Description:
PDC checks to make sure that the cell releasing the semaphore actually owns the semaphore it is trying to release. This chassis code is sent when PDC cannot read the owner of the semaphore. Data Field: (cell << 56) | (port << 44) | (xbc << 32) | return status
Cause / Action:
Cause: There was a fabric failure reading the XBCs CSRs. Action: Look for FABRIC_READ_ERROR_xxx chassis codes or a chassis code indicating the data from the XBC slices are different. Contact HP Support personnel to analyze the fabric.
Automated Recovery: None
Event Generation Threshold: 1 occurrence

Event 1976

Severity: MAJOR
Event Summary: PDC failed while attempting to determine a SM4's current owner
Event Class: System
Problem Description:
PDC is attempting to release a SM4. After it has released the semaphore it checks to make sure that it no longer owns the semaphore. This chassis code is sent when PDC fails while reading the XBC SM4. This chassis code is also sent when PDC fails to read a SM4 as part of tracking the owner of a semaphore and the length of time the owner has held the semaphore. Data Field: (cell << 56) | (port << 44) | (xbc << 32) | return status
Cause / Action: Cause: There was a fabric failure reading the XBCs CSRs. Action: Look for FABRIC_READ_ERROR_xxx chassis codes or a chassis code indicating the data from the XBC slices are different. Contact HP Support personnel to analyze the fabric.
Automated Recovery: None
Event Generation Threshold: 1 occurrence

Event 1977

Severity: MAJOR
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: (cell << 56) | (port << 44) | (xbc << 32) | current owner
Cause / Action:
Cause: XBC Key Contention. Hardware Failure Action: Contact HP Support personnel to analyze the fabric.
Automated Recovery: None
Event Generation Threshold: 1 occurrence

Event 1978

Severity: MAJOR
Event Summary: PDC tried to write to a fabric SM4 and failed
Event Class: System
Problem Description:
PDC attempted to write the XBC SM4 register and detected a problem in doing the write. PDC was unable release the SM4. Data Field: (cell << 56) | (port << 44) | (xbc << 32) | return status
Cause / Action:
Cause: There was a problem determining if the fabric was in a writable state. Action: Contact HP Support personnel to analyze the fabric.
Automated Recovery: None
Event Generation Threshold: 1 occurrence

Event 1979

Severity: MAJOR
Event Summary: PDC failed reading an XBC SM4 while insuring the cell didn't errantly hold SM4s
Event Class: System
Problem Description:
This chassis code is sent when PDC cannot read the XBC's global port SM4.Data Field: (port << 44) | (xbc num << 32) | XBC semaphore read data
Cause / Action:
Cause: There was a fabric failure reading the XBCs CSRs. Action: Look for FABRIC_READ_ERROR_xxx chassis codes or a chassis code indicating the data from the XBC slices are different. Contact HP Support personnel to analyze the fabric.
Automated Recovery: None
Event Generation Threshold: 1 occurrence

Event 1980

Severity: MAJOR
Event Summary: PDC failed releasing a XBC SM4 while insuring the cell held no XBC SM4s
Event Class: System
Problem Description:
PDC checks to make sure that the cell on which it is running does not hold any XBC SM4s during fabric discovery and during a number of error handling conditions. The purpose behind this check is to make sure that a failure or a previous failure on this cell does not result in XBC SM4s remaining locked. This chassis code is sent when PDC detects that the cell holds a semaphore that it shouldn't hold and fails when it attempts to release the SM4. Data Field: (port << 44) | (xbc num << 32) | ret status
Cause / Action:
Cause: There was a problem determining if the fabric was in a writable state. Action: Contact HP Support personnel to analyze the fabric.
Automated Recovery: None
Event Generation Threshold: 1 occurrence

Event 1981

Severity: MAJOR
Event Summary: PDC failed reading an XBC SM4 while making sure it didn't errantly hold SM4s
Event Class: System
Problem Description:
PDC checks to make sure that the cell on which it is running does not hold any XBC SM4s during fabric discovery and during a number of error handling conditions. The purpose behind this check is to make sure that a failure or a previous failure on this cell does not result in XBC SM4s remaining locked. This chassis code is sent when PDC cannot read the owner of a port's XBC semaphore Data Field: (port << 44) | (xbc num << 32) | read data
Cause / Action:
Cause: There was a fabric failure reading the XBCs CSRs. Action: Look for FABRIC_READ_ERROR_xxx chassis codes or a chassis code indicating the data from the XBC slices are different. Contact HP Support personnel to analyze the fabric.
Automated Recovery: None
Event Generation Threshold: 1 occurrence

Event 1982

Severity: MAJOR
Event Summary: PDC failed releasing a XBC SM4 while insuring the cell held no XBC SM4s
Event Class: System
Problem Description:
PDC checks to make sure that the cell on which it is running does not hold any XBC SM4s during fabric discovery and during a number of error handling conditions. The purpose behind this check is to make sure that a failure or a previous failure on this cell does not result in XBC SM4s remaining locked. This chassis code is sent when PDC detects that the cell holds a semaphore that it shouldn't hold and fails when it attempts to release the SM4. Data Field: (port << 44) | (xbc num << 32) | return status
Cause / Action:
Cause: There was a problem determining if the fabric was in a writable state. Action: Contact HP Support personnel to analyze the fabric.
Automated Recovery: None
Event Generation Threshold: 1 occurrence

Event 1983

Severity: MAJOR
Event Summary: PDC failed while making sure the cell on which it's running didn't hold any SM4s
Event Class: System
Problem Description:
PDC checks to make sure that the cell on which it is running does not hold any XBC SM4s during fabric discovery and during a number of error handling conditions. The purpose behind this check is to make sure that a failure or a previous failure on this cell does not result in XBC SM4s remaining locked. This chassis code is sent when PDC cannot figure out which XBCs are in the system. Data Field: return status
Cause / Action:
Cause: PDC couldn't read the XBC register that contained the topology. Look for additional chassis codes that provide additional details about the problem. This is probably the result of a fabric failure, but the nature of the failure cannot be determined from this chassis code alone. Action: Contact HP Support personnel to analyze the fabric.
Automated Recovery: None
Event Generation Threshold: 1 occurrence

Event 1984

Severity: MAJOR
Event Summary: The XBC write to the remote routing register failed.
Event Class: System
Problem Description:
When a system has already been routed and a cell is reset, it's remote routing registers are setup by copying the routing from the built-in XBC port. This copy has failed. There was an error while attempting to write the register. The cell will reset and reboot, as the copy may succeed on next boot. Data Field: write address
Cause / Action:
Cause: The XBC key has been locked or the Global Semaphore is not owned, thus preventing writes from occurring. XBC write failure Action: Contact HP Support personnel to analyze the fabric.
Automated Recovery: None
Event Generation Threshold: 1 occurrence

Event 1985

Severity: MAJOR
Event Summary: A failure occurred when testing the route from the target XBC to the local XBC.
Event Class: System
Problem Description:
An unexpected failure occurred while traversing from the target XBC to the local XBC. Data Field: (target cell << 56) | (xbc num << 32)
Cause / Action:
Cause: There was a failure (most likely during a XBC read) while traversing the route to the target XBC. Action: Contact HP Support personnel to analyze the fabric, crossbar, flex cables
Automated Recovery: None
Event Generation Threshold: 1 occurrence

Event 1986

Severity: MAJOR
Event Summary: The fabric route from the target XBC is not traversable.
Event Class: System
Problem Description:
The fabric data route from the local XBC to the target XBC is being examined. A problem was encountered on the return route from the target XBC to the local XBC. Data Field: (target cell << 56) | (xbc num << 32)
Cause / Action:
Cause: A link between the target XBC and the local XBC was not useable. Since this is the return path (and the to path has already been tested), then a fabric link was probably broken during routing. This would be the second broken link. Action: Contact HP Support personnel to analyze the fabric.
Automated Recovery: None
Event Generation Threshold: 1 occurrence

Event 1987

Severity: MAJOR
Event Summary: A failure occurred when testing the route from the local XBC to the target XBC.
Event Class: System
Problem Description:
An unexpected failure occurred while traversing from the local XBC to the target XBC. Data Field: (target cell << 56) | (xbc num << 32)
Cause / Action:
Cause: There was a failure (most likely during a XBC read) while traversing the route to the target XBC. Action: Contact HP Support personnel to analyze the fabric.
Automated Recovery: None
Event Generation Threshold: 1 occurrence

Event 1988

Severity: MAJOR
Event Summary: The fabric route to the target XBC is not traversable.
Event Class: System
Problem Description:
The fabric route from the local XBC to the target XBC is being examined. A problem was encountered on the route to the target's XBC. Data Field: (target cell << 56) | (xbc num << 32)
Cause / Action: Cause: A link between the local XBC and the target XBC was not alive. This means the link is either not yet initialized, powered off, or a Fatal Error has been encountered preventing the link from being used. Action: Contact HP Support personnel to analyze the fabric.
Automated Recovery: None
Event Generation Threshold: 1 occurrence

Event 1989

Severity: MAJOR
Event Summary: The cell cannot reach the fabric. It's link is not initialized.
Event Class: System
Problem Description:
Testing the fabric link between a cell and its XBC. This chassis code indicates that a cell is no longer visible on the fabric or that the cell can no longer see the fabric. Any cells in this PD should have already HPMC'd. Data Field: (cell << 56) | (port << 44) | (xbc << 32)
Cause / Action:
Cause: Fabric link error. Hardware failure. Action: Contact HP Support personnel to analyze the fabric.
Automated Recovery: None
Event Generation Threshold: 1 occurrence

Event 1990

Severity: MAJOR
Event Summary: A failure occurred when reading an XBC's local routing table
Event Class: System
Problem Description:
While examining a cell link, a read of the XBC port's local routing register failed. Data Field: (target cell << 56) | (xbc num << 32) | return status
Cause / Action:
Cause: An XBC read failed. Possibly a new failure or an intermittent failure. Action: Contact HP Support personnel to analyze the fabric.
Automated Recovery: None
Event Generation Threshold: 1 occurrence

Event 1991

Severity: MAJOR
Event Summary: The Cell Local Semaphore was not locked.
Event Class: System
Problem Description:
The fabric walk code needs to have the Cell Local Semaphore locked in order to send chassis codes safely. This semaphore was not locked, so the fabric walk has failed. Data Field: (target cell << 56) |
Cause / Action: Cause: PDC runtime error. Action: Contact HP Support personnel to analyze the fabric and PDC
Automated Recovery: None
Event Generation Threshold: 1 occurrence

Event 1992

Severity: MAJOR
Event Summary: An unknown backplane was detected during the fabric walk.
Event Class: System
Problem Description:
During a fabric walk, the fabric code needs to know the system type. This chassis code indicates that there was an error in determining the system type. Perhaps a new type has been added. Data Field: system type
Cause / Action: Cause: Unknown system type Action: Contact HP Support personnel to analyze the backplanes and activity logs
Automated Recovery: None
Event Generation Threshold: 1 occurrence

Event 1993

Severity: MAJOR
Event Summary: Couldn't read the local XBC number from the CC.
Event Class: System
Problem Description:
An error reading the CC prevented PDC from obtaining the number of the local XBC Data Field: return status
Cause / Action:
Cause: Failed to read a CSR on the CC. Action: Contact HP Support personnel to check the CC
Automated Recovery: None
Event Generation Threshold: 1 occurrence

Event 1994

Severity: MAJOR
Event Summary: Couldn't read a XBC Global General Purpose register.
Event Class: System
Problem Description:
Attempted to read the routing state from a global general purpose register on the XBC. The read access failed. Data Field: (xbc num << 32) | return status
Cause / Action:
Cause: XBC register read failure Action: Contact HP Support personnel to analyze the crossbar chip.
Automated Recovery: None
Event Generation Threshold: 1 occurrence

Event 1995

Severity: MAJOR
Event Summary: Couldn't release the XBC's global semaphore.
Event Class: System
Problem Description:
After attempting to perform routing for the XBC, the XBC global semaphore could not be released. Data Field: (xbc num << 32) | return status
Cause / Action:
Cause: The XBC global semaphore could not be released, possibly due to a XBC read/write failure or to XBC contention. Action: Contact HP Support personnel to analyze the fabric, crossbar chip
Automated Recovery: None
Event Generation Threshold: 1 occurrence

Event 1996

Severity: MAJOR
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. Data Field: (xbc num << 32)
Cause / Action:
Cause: Another cell already attempted routing for the XBC and found an error. Action: Contact HP Support personnel to analyze the fabric.
Automated Recovery: None
Event Generation Threshold: 1 occurrence

Event 1997

Severity: MAJOR
Event Summary: A read after write of a XBC address failed to contain the expected contents.
Event Class: System
Problem Description:
When a system has already been routed and a cell is reset, it's remote routing registers are setup by copying the routing from the built-in XBC port. This copy has failed. The first register to fail a read after write triggers this chassis code. The cell will reset and reboot, as the copy may succeed on next boot. Data Field: XBC physical location
Cause / Action:
Cause: The XBC key has been locked or the Global Semaphore is not owned, thus preventing writes from occurring. This is frequently a timing/contention issue and the cell will probably succeed on next boot. Action: Contact HP Support personnel to analyze the fabric Cause: XBC write failure Action: Contact HP Support personnel to analyze the XBC, CC, and XBC to CC link
Automated Recovery: None
Event Generation Threshold: 1 occurrence

Event 1998

Severity: MAJOR
Event Summary: The Cell Local Semaphore was not locked.
Event Class: System
Problem Description:
The fabric walk code needs to have the Cell Local Semaphore locked in order to send chassis codes safely. This semaphore was not locked, so the fabric walk has failed. Data Field: (target cell << 56) | return value
Cause / Action:
Cause: The cell local semaphore was not locked Action: Contact HP Support personnel to analyze the XBC semaphores and activity logs
Automated Recovery: None
Event Generation Threshold: 1 occurrence

Event 1999

Severity: MAJOR
Event Summary: An unknown backplane was detected during the fabric call.
Event Class: System
Problem Description:
During a fabric walk, the fabric code needs to know the system type. This chassis code indicates that there was an error in determining the system type. Perhaps a new type has been added. Data Field: system type
Cause / Action:
Cause: Unknown system type Action: Contact HP Support personnel to analyze the backplanes and activity logs
Automated Recovery: None
Event Generation Threshold: 1 occurrence

Event 2000

Severity: MAJOR
Event Summary: Cell's XBC port has been marked in error
Event Class: System
Problem Description:
A cell's XBC port has been marked in error because it is in FE, has failed link to link tests or is already marked in error. Data Field: XBC number << 32 | internal port number (8-F)
Cause / Action: Cause: The XBC port is in FE, has failed link to link tests, or has already been marked in error. Action: Reset the cell Reset the system backplane Contact HP Support personnel to troubleshoot problem
Automated Recovery: None
Event Generation Threshold: 1 occurrence

Event 2001

Severity: MAJOR
Event Summary: Could not unlock the XBC Global Key.
Event Class: System
Problem Description:
During a write of a protected XBC register, the global semaphore was owned by this cell, however the global key was locked. The locked key would prevent the lock from occurring. Since the cell owns the semaphore, the key will be unlocked to allow the write. However, the write to unlock the key failed. The cell will halt. Data Field: return status
Cause / Action:
Cause: XBC write failure Action: Contact HP Support personnel to analyze the XBC, CC, and XBC to CC link
Automated Recovery: None
Event Generation Threshold: 1 occurrence

Event 2002

Severity: MAJOR
Event Summary: The XBC global semaphore was not locked.
Event Class: System
Problem Description:
The XBC's global semaphore was expected to be locked, but the semaphore was found not to be locked or the lock couldn't be verified. Data Field: (xbc num << 32) | error id
Cause / Action:
Cause: There was a problem accessing the XBC. Action: Contact HP Support personnel to analyze the crossbar chip, flex cable, CC, PDC
Automated Recovery: None
Event Generation Threshold: 1 occurrence

Event 2003

Severity: MAJOR
Event Summary: The XBC global semaphore was not locked
Event Class: System
Problem Description:
The XBC's global semaphore was expected to be locked, but the semaphore was found not to be locked or the lock couldn't be verified. Data Field: (port << 44) | (xbc num << 32) | error id
Cause / Action: Cause: There was a problem accessing the XBC. Action: Contact HP Support personnel to analyze the crossbar chip, flex cable, CC, PDC
Automated Recovery: None
Event Generation Threshold: 1 occurrence

Event 2004

Severity: CRITICAL
Event Summary: A failure occurred while releasing the XBC Global Semaphore
Event Class: System
Problem Description:
At the end of Fabric Discovery, the local XBC's Global Semaphore needs to be released. An error has occurred that prevented the release of the XBC semaphore. Data Field: return value
Cause / Action:
Cause: Fabric failure Action: Contact HP Support personnel to analyze the fabric, XBC, XBC to CC link Look for additional event ids that may indicate XBC Key Contention.
Automated Recovery: None
Event Generation Threshold: 1 occurrence

Event 2005

Severity: CRITICAL
Event Summary: Fabric Discovery did not complete correctly
Event Class: System
Problem Description:
A failure or problem was encountered in fabric state validation at the end of fabric discovery. Chassis codes sent before this one should give more details about the nature of the problem. Data Field: return status
Cause / Action:
Cause: Hardware failure or PDC runtime error. Action: Contact HP Support personnel to check the flex cables, crossbar chips, CC, and PDC.
Automated Recovery: None
Event Generation Threshold: 1 occurrence

Event 2006

Severity: CRITICAL
Event Summary: PDC failed to lock an XBC after it took over the XBC's semaphore.
Event Class: System
Problem Description:
When a cell holds a fabric semaphore for an extended period of time, PDC will attempt to takeover the semaphore so that the rest of the cells will have access to it. PDC tried to lock the fabric after taking the XBC semaphore from the hung cell and failed. Data Field: (xbc num << 32) | return status
Cause / Action:
Cause: There was a problem accessing the fabric. There could be a problem with PDC where it fails to keep track which cells owns an XBC semaphore (unlikely after PDC 32.4). Action: Look for other chassis codes providing more information about the problem. Contact HP Support personnel to analyze the fabric.
Automated Recovery: None
Event Generation Threshold: 1 occurrence

Event 2007

Severity: CRITICAL
Event Summary: In taking over a port SM4, PDC attempted to read the SM4 and failed.
Event Class: System
Problem Description:
When a cell holds a fabric semaphore for an extended period of time, PDC will attempt to takeover the semaphore so that the rest of the cells will have access to it. When this chassis code is sent, PDC cannot access the XBC semaphore and is probably unable to access anything else on the XBC. Data Field: (xbc num << 32) | return status
Cause / Action:
Cause: There was a fabric failure reading the XBCs CSRs. Action: Look for FABRIC_READ_ERROR_xxx chassis codes or a chassis code indicating the data from the XBC slices are different. Contact HP Support personnel to analyze the fabric.
Automated Recovery: None
Event Generation Threshold: 1 occurrence

Event 2008

Severity: MAJOR
Event Summary: PDC failed attempting to force an XBC to unlock as part of taking over a SM4
Event Class: System
Problem Description:
When a cell holds a fabric semaphore for an extended period of time, PDC will attempt to takeover the semaphore so that the rest of the cells will have access to it. This chassis code is sent we PDC encounters a problem in trying to enable the XBC key for the semaphore that it is trying to take over. Data Field: (xbc num << 32) | return status
Cause / Action:
Cause: This could be a hardware problem that prevents PDC from manipulating the fabric CSRs. This could be a problem with XBC key contention. Action: Look for other chassis codes that contain more specific data as to why enabling the XBC key failed. If the problem is repeatable, note the circumstances under which this event is occurring and capture complete activity logs. Contact HP Support personnel to analyze the fabric.
Automated Recovery: None
Event Generation Threshold: 1 occurrence

Event 2009

Severity: MAJOR
Event Summary: PDC is attempting to take over a fabric SM4 and had trouble reading the SM4 CSR
Event Class: System
Problem Description:
When a cell holds a fabric semaphore for an extended period of time, PDC will attempt to takeover the semaphore so that the rest of the cells will have access to it. This chassis code is sent after PDC has already tried to take over the semaphore and is reading it to see if, now that the semaphore is unlocked, another cell has taken ownership of it. PDC will perform this check for a certain period of time and will then emit a chassis code indicating that it timed out. Data Field: (xbc num << 32) | return status
Cause / Action:
Cause: There was a fabric failure reading the XBCs CSRs. Action: Look for FABRIC_READ_ERROR_xxx chassis codes or a chassis code indicating the data from the XBC slices are different. Contact HP Support personnel to analyze the fabric.
Automated Recovery: None
Event Generation Threshold: 1 occurrence

Event 2010

Severity: CRITICAL
Event Summary: PDC attempted a fabric SM4 takeover and timed out trying to unlock the SM4
Event Class: System
Problem Description:
When a cell holds a fabric semaphore for an extended period of time, PDC will attempt to takeover the semaphore so that the rest of the cells will have access to it. PDC 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 num << 32) | return status
Cause / Action:
Cause: PDC cannot takeover a fabric semaphore that has been held for a long time. Action: Look for other fabric chassis codes that explain why the current owner of the SM4 was unable to release it. Contact HP Support personnel to analyze the fabric and backplane.
Automated Recovery: None
Event Generation Threshold: 1 occurrence

Event 2011

Severity: MAJOR
Event Summary: In taking over an XBC SM4, PDC failed to write the unlocked value to the SM4
Event Class: System
Problem Description:
When a cell holds a fabric semaphore for an extended period of time, PDC will attempt to takeover the semaphore so that the rest of the cells will have access to it. This chassis code is sent when PDC attempts to write the unlocked value to the semaphore and the write fails. Data Field: (xbc num << 32) |return status
Cause / Action:
Cause: There was a problem determining if the fabric was in a writable state. Look for other chassis codes indicating a fabric problem. There may be a backplane problem. Action: Contact HP Support personnel to analyze the fabric.
Automated Recovery: None
Event Generation Threshold: 1 occurrence

Event 2012

Severity: MAJOR
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: Fabric Failure Action: Contact HP Support personnel to analyze the fabric.
Automated Recovery: None
Event Generation Threshold: 1 occurrence

Event 2013

Severity: MAJOR
Event Summary: PDC attempted to lock the fabric after not getting the SM4 and failed.
Event Class: System
Problem Description:
PDC attempted to get a fabric semaphore, but another cell got the SM4 before this cell could obtain it. PDC tried to lock the fabric and failed. Data Field: (cell << 56) | (port << 44) | (xbc << 32) | return status
Cause / Action:
Cause: PDC could not read or write the fabric SM4 to see if it was already owned. There was a problem reading the fabric. Action: Contact HP Support personnel to analyze the fabric.
Automated Recovery: None
Event Generation Threshold: 1 occurrence

Event 2014

Severity: MAJOR
Event Summary: PDC attempted to unlock the fabric and failed while trying to get the XBC SM4
Event Class: System
Problem Description:
The fabric has to be unlocked for PDC to get the fabric semaphore. PDC tried to unlock the fabric and failed. Data Field: (cell << 56) | (port << 44) | (xbc << 32) | return status
Cause / Action:
Cause: PDC could not read or write the fabric SM4 to see if it was already owned. There was a problem reading the fabric. Action: Contact HP Support personnel to analyze the fabric.
Automated Recovery: None
Event Generation Threshold: 1 occurrence

Event 2015

Severity: MAJOR
Event Summary: PDC failed while attempting to determine a SM4's current owner
Event Class: System
Problem Description:
PDC is attempting to get a SM4. As part of the attempt it checks to see who owns the SM4 and how long they have owned it. This chassis code is sent when PDC fails while reading the XBC SM4. Data Field: (cell << 56) | (port << 44) | (xbc << 32) | return status
Cause / Action:
Cause: There was a fabric failure reading the XBCs CSRs. Action: Look for FABRIC_READ_ERROR_xxx chassis codes or a chassis code indicating the data from the XBC slices are different. Contact HP Support personnel to analyze the fabric.
Automated Recovery: None
Event Generation Threshold: 1 occurrence

Event 2016

Severity: MAJOR
Event Summary: PDC failed while attempting to determine a SM4's current owner
Event Class: System
Problem Description:
PDC is attempting to get a SM4. As part of the attempt it checks to see who owns the SM4 and how long they have owned it. This chassis code is sent when PDC fails while reading the XBC SM4. Data Field: (cell << 56) | (port << 44) | (xbc << 32) | return status
Cause / Action:
Cause: There was a fabric failure reading the XBCs CSRs. Action: Look for FABRIC_READ_ERROR_xxx chassis codes or a chassis code indicating the data from the XBC slices are different. Contact HP Support personnel to analyze the fabric.
Automated Recovery: None
Event Generation Threshold: 1 occurrence

Event 2017

Severity: MAJOR
Event Summary: PDC tried to write to a fabric SM4 and failed
Event Class: System
Problem Description:
PDC attempted to write the XBC SM4 register and detected a problem in doing the write. PDC was unable obtain the SM4. Data Field: (cell << 56) | (port << 44) | (xbc << 32) | return status
Cause / Action:
Cause: There was a problem determining if the fabric was in a writable state. Look for other chassis codes indicating a fabric problem. There may be a backplane problem. Action: Contact HP Support personnel to analyze the fabric.
Automated Recovery: None
Event Generation Threshold: 1 occurrence

Event 2018

Severity: MAJOR
Event Summary: PDC could not find data for the Domelight fabric neighbor table.
Event Class: System
Problem Description:
PDC uses tables to drive the fabric code. The data in the neighbor table was empty. Data Field: address of neighbor info table
Cause / Action:
Cause: The backplane type in the PDH external backplane type register was incorrect. Action: Contact HP Support personnel to analyze the backplane and CC
Automated Recovery: None
Event Generation Threshold: 1 occurrence

Event 2019

Severity: MAJOR
Event Summary: PDC could not find data for the single-cabinet Superdome fabric neighbor table.
Event Class: System
Problem Description:
PDC uses tables to drive the fabric code. The data in the neighbor table was empty. Data Field: return status
Cause / Action:
Cause: Unknown system type Action: Contact HP Support personnel to analyze the backplanes and activity logs
Automated Recovery: None
Event Generation Threshold: 1 occurrence

Event 2020

Severity: MAJOR
Event Summary: An invalid XBC number was encountered.
Event Class: System
Problem Description:
An invalid XBC number was passed to an internal PDC function. Data Field: (port << 44) | (xbc num << 32)
Cause / Action:
Cause: PDC runtime error. Action: Contact HP Support personnel to analyze the fabric.
Automated Recovery: None
Event Generation Threshold: 1 occurrence

Event 2021

Severity: MAJOR
Event Summary: PDC could not find data for the simple crossbar topology fabric neighbor table.
Event Class: System
Problem Description:
PDC uses tables to drive the fabric code. The data in the neighbor table was empty. Data Field: return status
Cause / Action:
Cause: Unknown system type Action: Contact HP Support personnel to analyze the backplanes and activity logs
Automated Recovery: None
Event Generation Threshold: 1 occurrence

Event 2022

Severity: MAJOR
Event Summary: PDC called an XBC function on a back to back topology that is not supported.
Event Class: System
Problem Description:
PDC was searching for information about what is supposed to be connected to an XBC, but Matterhorn systems do not support XBCs. Data Field: return status
Cause / Action:
Cause: Unknown system type Action: Contact HP Support personnel to analyze the backplanes and activity logs
Automated Recovery: None
Event Generation Threshold: 1 occurrence

Event 2023

Severity: MAJOR
Event Summary: Failed to fill in the neighbor info from the table of expected values.
Event Class: System
Problem Description:
Attempted to read a table of expected neighbor information but was unable to do so. Data Field: (port << 44) | (xbc num << 32) | ret status
Cause / Action:
Cause: The table could not be accessed. PDC runtime error. Action: Contact HP Support personnel to check the CC and PDC
Automated Recovery: None
Event Generation Threshold: 1 occurrence

Event 2024

Severity: MAJOR
Event Summary: Failed to fill in the expected neighbor info because no nieghbor was expected.
Event Class: System
Problem Description:
Attempted to read a table of expected neighbor information but was unable to do so because no neighbor ws expected for the specified XBC and XBC port numbers. Data Field: system type
Cause / Action:
Cause: PDC runtime error. Action: Contact HP Support personnel to analyze the fabric and PDC
Automated Recovery: None
Event Generation Threshold: 1 occurrence

Event 2025

Severity: MAJOR
Event Summary: An invalid XBC port number was encountered.
Event Class: System
Problem Description:
An invalid XBC port number was passed to an internal PDC function. An external port number was expected, but the port number encountered was not one. Data Field: (port << 44) | (xbc num << 32)
Cause / Action:
Cause: PDC runtime error. Action: Contact HP Support personnel to analyze the fabric and PDC
Automated Recovery: None
Event Generation Threshold: 1 occurrence

Event 2026

Severity: MAJOR
Event Summary: An invalid XBC port number was encountered.
Event Class: System
Problem Description:
An invalid XBC port number was passed to an internal PDC function. An internal port number was expected, but the port number encountered was not one. Data Field: (port << 44) | (xbc num << 32)
Cause / Action:
Cause: PDC runtime error. Action: Contact HP Support personnel to analyze the fabric and PDC
Automated Recovery: None
Event Generation Threshold: 1 occurrence

Event 2027

Severity: MAJOR
Event Summary: PDC could not find data for the single-cabinet Superdome fabric neighbor table.
Event Class: System
Problem Description:
PDC uses tables to drive the fabric code. The data in the neighbor table was empty. Data Field: address of neighbor info table
Cause / Action:
Cause: Unknown system type Action: Contact HP Support personnel to analyze the backplanes and activity logs
Automated Recovery: None
Event Generation Threshold: 1 occurrence

Event 2028

Severity: MAJOR
Event Summary: An unrecognized backplane type was read from PDH.
Event Class: System
Problem Description:
The system backplane type that was read from PDH was not a recognized type. Data Field: system type
Cause / Action:
Cause: Unknown system type Action: Contact HP Support personnel to analyze the backplanes and activity logs
Automated Recovery: None
Event Generation Threshold: 1 occurrence

Event 2029

Severity: MAJOR
Event Summary: PDC did not recognize the fabric topology of the system.
Event Class: System
Problem Description:
PDC was verifying that the neighbor for an XBC port was the neighbor that was expected based on the system's topology. The topology was stored on the XBC during fabric discovery by the PDC that routed the fabric. PDC did not recognize the topology stored on the XBC or did not expect the topology it found. Data Field: topology
Cause / Action:
Cause: Unknown or unsupported topology. Perhaps the XBC information became corrupted. Action: Contact HP Support personnel to analyze the fabric.
Automated Recovery: None
Event Generation Threshold: 1 occurrence

Event 2030

Severity: MAJOR
Event Summary: PDC could not determine the fabric topology of the system
Event Class: System
Problem Description:
This chassis code is sent when PDC is trying to determine which XBCs exist in the current system's topology. PDC determines the topology during boot and stores it in an XBC CSR. This chassis code is sent when PDC cannot read that CSR. Data Field: return status
Cause / Action: Cause: The failure was probably one of the following: a multi-bit error reading a fabric CSR, unable to access an XBC, XBC bit slices returned inconsistent data. Action: Look for chassis codes that indicate a fabric read failed. These chassis codes may provide more information about the failure. Contact HP Support personnel to analyze the fabric.
Automated Recovery: None
Event Generation Threshold: 1 occurrence

Event 2031

Severity: MAJOR
Event Summary: Could not traverse to a XBC that was expected to be present in the system.
Event Class: System
Problem Description:
When collecting the fabric ICM neighbor information, the route to the first XBC (XBC 0) was not traversable. Based on the fabric topology (obtained from the XBC general purpose register on the local XBC), the first XBC was expected to be present. Data Field: (xbc num << 32)
Cause / Action:
Cause: A hardware failure prevented traversal to the XBC. Action: Contact HP Support personnel to check the flex cables, crossbar chips, PDC.
Automated Recovery: None
Event Generation Threshold: 1 occurrence

Event 2032

Severity: MAJOR
Event Summary: Could not traverse to a XBC that was expected to be present in the system.
Event Class: System
Problem Description:
When collecting the fabric ICM neighbor information, the route to the fourth XBC was not traversable. Based on the fabric topology (obtained from the XBC general purpose register on the local XBC), the first XBC was expected to be present. Data Field: (xbc num << 32)
Cause / Action:
Cause: A hardware failure prevented traversal to the XBC. Action: Contact HP Support personnel to check the flex cables, crossbar chips, PDC.
Automated Recovery: None
Event Generation Threshold: 1 occurrence

Event 2033

Severity: MAJOR
Event Summary: Could not traverse to a XBC that was expected to be present in the system.
Event Class: System
Problem Description:
When collecting the fabric ICM neighbor information, the route to the second XBC was not traversable. Based on the fabric topology (obtained from the XBC general purpose register on the local XBC), the first XBC was expected to be present. Data Field: (xbc num << 32)
Cause / Action: Cause: A hardware failure prevented traversal to the XBC. Action: Contact HP Support personnel to check the flex cables, crossbar chips, PDC.
Automated Recovery: None
Event Generation Threshold: 1 occurrence

Event 2034

Severity: MAJOR
Event Summary: Could not traverse to a XBC that was expected to be present in the system.
Event Class: System
Problem Description:
When collecting the fabric ICM neighbor information, the route to the mirror XBC was not traversable. Based on the fabric topology (obtained from the XBC general purpose register on the local XBC), the first XBC was expected to be present. Data Field: (xbc num << 32)
Cause / Action: Cause: A hardware failure prevented traversal to the XBC. Action: Contact HP Support personnel to check the flex cables, crossbar chips, PDC.
Automated Recovery: None
Event Generation Threshold: 1 occurrence

Event 2035

Severity: MAJOR
Event Summary: Invalid address passed to one a fabric functions
Event Class: System
Problem Description:
An invalid XBC address is being used Data Field: XBC #
Cause / Action: Cause: PDC runtime error. Action: Contact HP Support personnel to analyze the fabric and PDC
Automated Recovery: None
Event Generation Threshold: 1 occurrence

Event 2036

Severity: MAJOR
Event Summary: The address to write is not a fabric address
Event Class: System
Problem Description:
An attempted XBC write has failed because the address provided is not a Fabric address. Data Field: CSR address Cause / Action:
Cause: PDC runtime error. Action: Contact HP Support personnel to analyze the fabric and PDC
Automated Recovery: None
Event Generation Threshold: 1 occurrence

Event 2037

Severity: CRITICAL
Event Summary: Invalid neighbor found attached to fabric.
Event Class: System
Problem Description:
Invalid neighbor found attached to fabric. Data Field: Neighbor Type 0x00 CC 0x01 XBC 0x02 - 0xFE Reserved 0xFF No connection
Cause / Action: Cause: An invalid neighbor was found attached to the fabric. Action: Contact HP Support personnel to analyze the fabric.
Automated Recovery: None
Event Generation Threshold: 1 occurrence

Event 2038

Severity: MAJOR
Event Summary: While routing around an unhealthy port, the reroute port calculated is invalid.
Event Class: System
Problem Description:
While routing around an unhealthy port, the reroute port calculated is invalid. Data Field: (xbc num << 32) | port
Cause / Action: Cause: PDC runtime error. Action: Contact HP Support personnel to analyze the fabric and PDC
Automated Recovery: None
Event Generation Threshold: 1 occurrence

Event 2039

Severity: MAJOR
Event Summary: The fabric topology does not match a known topology.
Event Class: System
Problem Description:
The topology is unknown. The fabric information cannot be gathered. Data Field: (togo num << 32) | topology
Cause / Action: Cause: PDC runtime error. Action: Contact HP Support personnel to analyze the fabric and PDC
Automated Recovery: None
Event Generation Threshold: 1 occurrence

Event 2041

Severity: MAJOR
Event Summary: The quadrant calculated is unknown.
Event Class: System
Problem Description:
The kitty corner XBC cannot be calculated because an invalid quadrant number was calcualated. Data Field: (xbc num << 32) | xbc quadrant
Cause / Action: Cause: PDC runtime error. Action: Contact HP Support personnel to analyze the fabric and PDC
Automated Recovery: None
Event Generation Threshold: 1 occurrence

Event 2042

Severity: MAJOR
Event Summary: An error occurred while testing the CC to XBC link.
Event Class: System
Problem Description:
At the beginning of Fabric Discovery a link test is performed. After writing a few pattern tests, an SBE or LPE error was logged on the CC for this link. Data Field: (port << 44) | (xbc num << 32) | 0x1E
Cause / Action: Cause: crossbar link failure, parity error Action: Contact HP Support personnel to check link connectivity, XBC, CC
Automated Recovery: None
Event Generation Threshold: 1 occurrence

Event 2043

Severity: MAJOR
Event Summary: The link is not useable due to problems with this port.
Event Class: System
Problem Description:
While examining a fabric link, one of the ports was found to have problems that prevent its use. Data Field: (port << 44) | (xbc num << 32)
Cause / Action: Cause: A XBC port was found to have errors while traversing the route to the target XBC. Action: Contact HP Support personnel to check the flex cables, crossbar chip, etc.
Automated Recovery: None
Event Generation Threshold: 1 occurrence

Event 2044

Severity: MAJOR
Event Summary: There was a fabric access error while examining a XBC port.
Event Class: System
Problem Description:
While examining a fabric link for traversability, there was an error accessing a fabric resource. Data Field: (port << 44) | (xbc num << 32)
Cause / Action: Cause: An unknown error was encountered. This is probably due to a fabric read error or trouble accessing a fabric resource. Action: Contact HP Support personnel to check the flex cables, crossbar chip, etc.
Automated Recovery: None
Event Generation Threshold: 1 occurrence

Event 2045

Severity: MAJOR
Event Summary: An error occurred while reading the Neighbor Info register.
Event Class: System
Problem Description:
While examining a XBC link for useability, there was an error reading from the XBC. Data Field: (port << 44) | (xbc num << 32) | ret status
Cause / Action:
Cause: There was a failure performing a read while traversing a fabric link. Action: Contact HP Support personnel to check the flex cables, crossbar chip, etc.
Automated Recovery: None
Event Generation Threshold: 1 occurrence

Event 2046

Severity: MAJOR
Event Summary: An error occurred while reading the Neighbor Info register.
Event Class: System
Problem Description:
While examining a XBC link for useability, there was an error reading from the XBC. Data Field: (port << 44) | (xbc num << 32) | ret status
Cause / Action:
Cause: There was a failure performing a read while traversing a fabric link. Action: Contact HP Support personnel to check the flex cables, crossbar chip, etc.
Automated Recovery: None
Event Generation Threshold: 1 occurrence

Event 2047

Severity: MAJOR
Event Summary: The link is not useable due to problems with this port.
Event Class: System
Problem Description:
While examining a fabric link, one of the ports was found to have problems that prevent its use. Data Field: (port << 44) | (xbc num << 32)
Cause / Action: Cause: A XBC port was found to have errors while traversing the route to the target XBC. Action: Look for additional chassis codes that provide more detailed information. Contact HP Support personnel to check the flex cables, crossbar chip, etc.
Automated Recovery: None
Event Generation Threshold: 1 occurrence

Event 2048

Severity: MAJOR
Event Summary: There was a fabric access error while examining a XBC port.
Event Class: System
Problem Description:
While examining a fabric link for traversability, there was an error accessing a fabric resource. Data Field: (port << 44) | (xbc num << 32)
Cause / Action: Cause: An unknown error was encountered. This is probably due to a fabric read error or trouble accessing a fabric resource. Action: Look for additional chassis codes that provide more detailed information. Contact HP Support personnel to check the flex cables, crossbar chip, etc.
Automated Recovery: None
Event Generation Threshold: 1 occurrence

Event 2049

Severity: MAJOR
Event Summary: Failure reading XBC Port status register.
Event Class: System
Problem Description:
While initiating the CC to XBC link test, a read failure occurred. This link will now be landmined to prevent use since it is considered unreliable. Data Field: (port << 44) | (xbc num << 32)
Cause / Action: Cause: likely fabric hardware failure Action: Contact HP Support personnel to analyze the fabric.
Automated Recovery: None
Event Generation Threshold: 1 occurrence

Event 2050

Severity: MAJOR
Event Summary: The pattern 0 test failed
Event Class: System
Problem Description:
The test write of all zeroes to both slices of a XBC failed. Data Field: (port << 44) | (xbc num << 32) | pattern
Cause / Action: Cause: likely fabric hardware failure Action: Contact HP Support personnel to analyze the fabric.
Automated Recovery: None
Event Generation Threshold: 1 occurrence

Event 2051

Severity: MAJOR
Event Summary: The pattern 5 test failed
Event Class: System
Problem Description:
The test write of all 0x5's to both slices of a XBC failed. Data Field: (port << 44) | (xbc num << 32) | pattern
Cause / Action: Cause: likely fabric hardware failure Action: Contact HP Support personnel to analyze the fabric.
Automated Recovery: None
Event Generation Threshold: 1 occurrence

Event 2052

Severity: MAJOR
Event Summary: The pattern A test failed
Event Class: System
Problem Description:
The test write of all 0xA's to both slices of a XBC failed. Data Field: (port << 44) | (xbc num << 32) | pattern
Cause / Action: Cause: likely fabric hardware failure Action: Contact HP Support personnel to analyze the fabric.
Automated Recovery: None
Event Generation Threshold: 1 occurrence

Event 2053

Severity: MAJOR
Event Summary: The pattern F test failed
Event Class: System
Problem Description:
The test write of all ones to both slices of a XBC failed. Data Field: (port << 44) | (xbc num << 32) | pattern
Cause / Action: Cause: likely fabric hardware failure Action: Contact HP Support personnel to analyze the fabric.
Automated Recovery: None
Event Generation Threshold: 1 occurrence

Event 2054

Severity: MAJOR
Event Summary: The CC to XBC Link pattern test failed
Event Class: System
Problem Description:
The CC to XBC Link pattern test failed. Data Field: (port << 44) | (xbc num << 32) | (pattern & 0xf) pattern = all F's, A's, 5's, 0's pattern test (XBC # << 32) | (internal port # << 16) | (0x5BE) failed logging Togo SBE or LPE errors (XBC # << 32) | (internal port # << 16) | (0x1E) failed logging DNA SBE or LPE errors
Cause / Action: Cause: The CC to XBC Link is corrupted. Either the CC, the local XBC, or the connection is faulty Action: Contact HP Support personnel to analyze the fabric.
Automated Recovery: None
Event Generation Threshold: 1 occurrence

Event 2055

Severity: MAJOR
Event Summary: Could not read the link landmine state.
Event Class: System
Problem Description:
While testing the CC to XBC link, PDC could not determine if the link is landmined. The link will be landmined. Data Field: (port << 44) | (xbc num << 32)
Cause / Action:
Cause: Failed reading the XBC port state register Action: Contact HP Support personnel to check the XBC
Automated Recovery: None
Event Generation Threshold: 1 occurrence

Event 2056

Severity: MAJOR
Event Summary: The XBC number provided is not a valid XBC Chip Id.
Event Class: System
Problem Description:
The argument passed into the function is invalid. If this code was called from a proc, then the argument should have been checked at the proc entrance. Data Field: (port << 44) | (xbc num << 32)
Cause / Action: Cause: An invalid XBC number was provided. Action: Capture chassis logs Document events leading up to the error Contact HP Support personnel to analyze the fabric
Automated Recovery: None
Event Generation Threshold: 1 occurrence

Event 2057

Severity: MAJOR
Event Summary: The port number provided is not a valid XBC Internal Port Number
Event Class: System
Problem Description:
The argument passed into the function is invalid. If this code was called from a proc, then the argument should have been checked at the proc entrance. Data Field: (port << 44) | (xbc num << 32)
Cause / Action: Cause: An invalid XBC number was provided. Action: Capture chassis logs Document events leading up to the error Contact HP Support personnel to check the fabric
Automated Recovery: None
Event Generation Threshold: 1 occurrence

Event 2058

Severity: MAJOR
Event Summary: An SBE or LPE was logged on the XBC during the link test.
Event Class: System
Problem Description:
After completing all the pattern tests, a Single Bit Error or a Link Parity Error was logged on the XBC. The link is not good. Data Field: (port << 44) | (xbc num << 32) | 0x5BE
Cause / Action: Cause: XBC Link failure, XBC failure Action: Contact HP Support personnel to analyze the fabric.
Automated Recovery: None
Event Generation Threshold: 1 occurrence

Event 2059

Severity: MAJOR
Event Summary: The XBC global semaphore was not locked during a PDC procedure call
Event Class: System
Problem Description:
During a PDC procedure, the XBC's global semaphore was expected to be locked, but the semaphore was found not to be locked or the lock couldn't be verified. Data Field: (port << 44) | (xbc num << 32) | log
Cause / Action: Cause: There was a problem accessing the XBC. Action: Contact HP Support personnel to analyze the fabric.
Automated Recovery: None
Event Generation Threshold: 1 occurrence

Event 2060

Severity: MAJOR
Event Summary: The XBC global semaphore was not locked during a PDC procedure call
Event Class: System
Problem Description:
During a PDC procedure, the XBC's global semaphore was expected to be locked, but the semaphore was found not to be locked or the lock couldn't be verified. Data Field: (port << 44) | (xbc num << 32) | log
Cause / Action: Cause: There was a problem accessing the XBC. Action: Contact HP Support personnel to analyze the fabric.
Automated Recovery: None
Event Generation Threshold: 1 occurrence

Event 2061

Severity: FATAL
Event Summary: Exceeded max number of failed XBC links during initial fabric routing
Event Class: System
Problem Description:
The maximum number of failed crossbar links has been exceeded during initial fabric routing. The cell will halt. Data Field: (XBC # attempting to route << 32) | number of failed ports
Cause / Action: Cause: The maximum number of failed crossbar links has been exceeded during initial fabric routing. Review the previous chassis codes to determine which links have failed. The routing table could be corrupt, i.e. links marked in error when healthy but perceived as non-functional Action: Contact HP Support personnel to analyze the fabric.
Automated Recovery: None
Event Generation Threshold: 1 occurrence

Event 2062

Severity: MAJOR
Event Summary: Multi-bit error occurred in fabric function
Event Class: System
Problem Description:
A multi-bit error occurred while reading the XBC Data Field: XBC read data
Cause / Action: Cause: A multi-bit read error occurred Action: Contact HP Support personnel to analyze the fabric.
Automated Recovery: None
Event Generation Threshold: 1 occurrence

Event 2063

Severity: MAJOR
Event Summary: Could not check the neighbor port's health status
Event Class: System
Problem Description:
When routing a XBC link, the neighbor side of the link needs to be tested. This chassis code indicates that a read of that neighbor side failed. The failure prevents testing of the neighbor port and causes the link to be landmined. Data Field: (xbc num << 32) | xbc port
Cause / Action: Cause: XBC Read failure Action: Contact HP Support personnel to analyze the fabric.
Automated Recovery: None
Event Generation Threshold: 1 occurrence

Event 2064

Severity: MAJOR
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: Cause: An XBC port is not healthy. Action: Contact HP Support personnel to analyze the fabric.
Automated Recovery: None
Event Generation Threshold: 1 occurrence

Event 2065

Severity: MAJOR
Event Summary: PDC could not read the topology of the system from an XBC register.
Event Class: System
Problem Description:
The topology is stored in a XBC scratch register during FabricDiscovery(). The read of this register failed. Data Field: return status
Cause / Action: Cause: Look for chassis codes that indicate a fabric read failed. These chassis codes may provide more information about the failure. The failure was probably one of the following: a multi-bit error reading a fabric CSR, unable to access an XBC, XBC bit slices returned inconsistent data. Action: Contact HP Support personnel to analyze the fabric.
Automated Recovery: None
Event Generation Threshold: 1 occurrence

Event 2066

Severity: CRITICAL
Event Summary: No local XBC was present.
Event Class: System
Problem Description:
Could not communicate with local XBC. The cell will attempt to reboot without fabric.
Cause / Action: Cause: Could not communicate with local XBC. Action: Contact HP Support personnel to analyze the local XBC, CC, and backplane.
Automated Recovery: None
Event Generation Threshold: 1 occurrence

Event 2067

Severity: MAJOR
Event Summary: Could not clear XBC error injection register for bits [14:0]
Event Class: System
Problem Description:
Could not clear XBC error injection register for bits [14:0] Data Field: (port << 44) | (xbc num << 32) | 0x1400
Cause / Action: Cause: write to XBC failed Action: Contact HP Support personnel to check the XBC
Automated Recovery: None
Event Generation Threshold: 1 occurrence

Event 2068

Severity: MAJOR
Event Summary: Could not clear XBC error injection register for bits [29:15]
Event Class: System
Problem Description:
Could not clear XBC error injection register for bits [29:15] Data Field: (port << 44) | (xbc num << 32) | 0x2915
Cause / Action: Cause: write to XBC failed Action: Contact HP Support personnel to check the XBC
Automated Recovery: None
Event Generation Threshold: 1 occurrence

Event 2069

Severity: MAJOR
Event Summary: Could not clear XBC error injection register for bits [44:30]
Event Class: System
Problem Description:
Could not clear XBC error injection register for bits [44:30] Data Field: (port << 44) | (xbc num << 32) | 0x4430
Cause / Action: Cause: write to XBC failed Action: Contact HP Support personnel to check the XBC
Automated Recovery: None
Event Generation Threshold: 1 occurrence

Event 2070

Severity: MAJOR
Event Summary: Could not clear XBC error injection register for bits [59:45]
Event Class: System
Problem Description:
Could not clear XBC error injection register for bits [59:45] Data Field: (port << 44) | (xbc num << 32) | 0x5945
Cause / Action: Cause: write to XBC failed Action: Contact HP Support personnel to check the XBC
Automated Recovery: None
Event Generation Threshold: 1 occurrence

Event 2071

Severity: MAJOR
Event Summary: Could not clear XBC error injection register for bits [73:60]
Event Class: System
Problem Description:
Could not clear XBC error injection register for bits [73:60] Data Field: (port << 44) | (xbc num << 32) | 0x7360
Cause / Action: Cause: write to XBC failed Action: Contact HP Support personnel to check the XBC
Automated Recovery: None
Event Generation Threshold: 1 occurrence

Event 2072

Severity: MAJOR
Event Summary: Could not clear CC debug control register
Event Class: System
Problem Description:
The write to the CC debug control register failed. Data Field: (port << 44) | (xbc num << 32) | 0xDDC2
Cause / Action: Cause: write to CC failed Action: Contact HP Support personnel to check the CC.
Automated Recovery: None
Event Generation Threshold: 1 occurrence

Event 2073

Severity: MAJOR
Event Summary: Could not clear CC debug counter register
Event Class: System
Problem Description:
Could not clear CC debug counter register. Data Field: (port << 44) | (xbc num << 32) | 0xDDC1
Cause / Action: Cause: write to CC failed Action: Contact HP Support personnel to check the CC.
Automated Recovery: None
Event Generation Threshold: 1 occurrence

Event 2074

Severity: MAJOR
Event Summary: The CC SBE and LPE errors were not cleared properly
Event Class: System
Problem Description:
The CC logged a SBE or LPE after they should have been cleared. Either the clear failed, or a new error was logged immediately. Data Field: (port << 44) | (xbc num << 32) | 0x1E
Cause / Action: Cause: write to CC Debug registers failed C2: the link generated a new error A2: check CC, check link Check logs for other errors. If error is persistent, replace cell board Action: Contact HP Support personnel to check the CC Cause: the link generated a new error Action: Contact HP Support personnel to check the CC, link
Automated Recovery: None
Event Generation Threshold: 1 occurrence

Event 2075

Severity: MAJOR
Event Summary: Could not clear CC seed error register
Event Class: System
Problem Description:
Could not clear CC seed error register Data Field: (port << 44) | (xbc num << 32) | 0x5DE
Cause / Action:
Cause: write to CC failed Action: Contact HP Support personnel to check the CC.
Automated Recovery: None
Event Generation Threshold: 1 occurrence

Event 2076

Severity: MAJOR
Event Summary: The XBC SBE and LPE errors were not cleared properly
Event Class: System
Problem Description:
The XBC logged a SBE or LPE after they should have been cleared. Either the clear failed, or a new error was logged immediately. Data Field: (port << 44) | (xbc num << 32) | 0x5BE
Cause / Action: Cause: write to CC Debug registers failed C2: the link generated a new error A2: check CC, check link Check logs for other errors. If error is persistent, replace cell board Action: Contact HP Support personnel to check the CC Cause: the link generated a new error Action: Contact HP Support personnel to check the CC, link
Automated Recovery: None
Event Generation Threshold: 1 occurrence

Event 2077

Severity: MAJOR
Event Summary: Could not clear XBC link parity error logs
Event Class: System
Problem Description:
Could not clear XBC link parity error logs. Data Field: (port << 44) | (xbc num << 32) | 0xF01E Cause / Action:
Cause: write to XBC failed Action: Contact HP Support personnel to check the XBC
Automated Recovery: None
Event Generation Threshold: 1 occurrence

Event 2078

Severity: MAJOR
Event Summary: Could not clear XBC routing table error logs
Event Class: System
Problem Description:
Could not clear XBC routing table error logs. Data Field: (port << 44) | (xbc num << 32) | 0xF01F Cause / Action:
Cause: write to XBC failed Action: Contact HP Support personnel to check the XBC
Automated Recovery: None
Event Generation Threshold: 1 occurrence

Event 2079

Severity: MAJOR
Event Summary: Could not clear XBC single bit error logs
Event Class: System
Problem Description:
Could not clear XBC single bit error logs Data Field: (port << 44) | (xbc num << 32) | 0xF5DE
Cause / Action:
Cause: write to XBC failed Action: Contact HP Support personnel to check the XBC
Automated Recovery: None
Event Generation Threshold: 1 occurrence

Event 2080

Severity: MAJOR
Event Summary: Could not read the local XBC number from the CC.
Event Class: System
Problem Description:
A read to the CC's XIN_LINK_STATE register failed. As a result, the local XBC number could not be determined. There must be problems with the CC's link to the fabric. Data Field: return status
Cause / Action: Cause: likely fabric hardware failure Action: Contact HP Support personnel to analyze the fabric.
Automated Recovery: None
Event Generation Threshold: 1 occurrence

Event 2081

Severity: MAJOR
Event Summary: The XBC number provided is not a valid XBC Chip Id.
Event Class: System
Problem Description:
The argument passed into the function is invalid. If this code was called from a proc, then the argument should have been checked at the proc entrance. This is a firmware bug. Data Field: (local xbc num << 32) | target xbc
Cause / Action: Cause: An invalid XBC number was provided. Action: Contact HP Support personnel to analyze the fabric.
Automated Recovery: None
Event Generation Threshold: 1 occurrence

Event 2082

Severity: MAJOR
Event Summary: A link in the fabric PIOB route is not useable.
Event Class: System
Problem Description:
The PIOB route was found to have errors preventing its use. Data Field: (port << 44) | (xbc num << 32)
Cause / Action: Cause: Fabric Access Failure Action: Contact HP Support personnel to analyze the fabric.
Automated Recovery: None
Event Generation Threshold: 1 occurrence

Event 2083

Severity: MAJOR
Event Summary: A link in the fabric PIOB route is not useable.
Event Class: System
Problem Description:
An error was encountered while testing the PIOB route. The test could not complete. Therefore, the route is not traversable. Data Field: (port << 44) | (xbc num << 32)
Cause / Action:
Cause: Fabric Access Failure Action: Contact HP Support personnel to analyze the fabric.
Automated Recovery: None
Event Generation Threshold: 1 occurrence

Event 2084

Severity: MAJOR
Event Summary: The CC to XBC link is not initialized.
Event Class: System
Problem Description:
When testing the PIOB route to a XBC, the local cell's fabric link was found to be uninitialized. This cell cannot talk to the fabric. Data Field: XIN link state
Cause / Action:
Cause: likely fabric hardware failure Action: Contact HP Support personnel to analyze the fabric.
Automated Recovery: None
Event Generation Threshold: 1 occurrence

Event 2085

Severity: MAJOR
Event Summary: Could not read the landmine state from the XBC register.
Event Class: System
Problem Description:
Testing the fabric PIOB route to a XBC. There was a failure reading from the XBC registers. The landmine state could not be determined. Data Field: (port << 44) | (xbc num << 32) | ret status
Cause / Action: Cause: likely fabric hardware failure Action: Contact HP Support personnel to analyze the fabric.
Automated Recovery: None
Event Generation Threshold: 1 occurrence

Event 2086

Severity: MAJOR
Event Summary: Error reading the Remote Routing Register on the XBC.
Event Class: System
Problem Description:
While traversing a fabric PIOB route, a port on the neighbor XBC was found to be uninitialized or in error. This should never happen since the routing should have already been completed. Data Field: return status
Cause / Action: Cause: The remote routing register does not contain a valid, initialized value. There may have been a failure reading from the XBC. Action: Contact HP Support personnel to analyze the fabric.
Automated Recovery: None
Event Generation Threshold: 1 occurrence

Event 2087

Severity: MAJOR
Event Summary: The cell local semaphore was not locked during a fabric function call.
Event Class: System
Problem Description:
The cell local semaphore is needed to send chassis codes. This fabric traversable function found the semaphore unlocked during execution. Data Field: (xbc num << 32) | return status
Cause / Action: Cause: Firmware forgot to lock the semaphore. Or another cpu has unlocked the semaphore behind the owner's back. Action: Contact HP Support personnel to analyze the fabric.
Automated Recovery: None
Event Generation Threshold: 1 occurrence

Event 2088

Severity: MAJOR
Event Summary: A fabric call has been attempted on a back to back system
Event Class: System
Problem Description:
While testing a fabric PIOB route, the system type was determined to be a Matterhorn. Matterhorn systems do not have fabric, so it cannot be tested. Data Field: system type
Cause / Action:
Cause: The fabric function is being used on the wrong system. Firmware bug. Action: Capture Chassis Codes. Document the events that led up to the problem. Contact the PDC team.
Automated Recovery: None
Event Generation Threshold: 1 occurrence

Event 2089

Severity: MAJOR
Event Summary: Fabric could not determine the system type from the backplane.
Event Class: System
Problem Description:
While testing a fabric PIOB route, the system type could not be determined. This indicates that either a new system type has been created, or the register contains faulty data. Data Field: system type
Cause / Action: Cause: Firmware does not support this type of system. Action: Contact HP Support personnel to analyze the fabric.
Automated Recovery: None
Event Generation Threshold: 1 occurrence

Event 2090

Severity: MAJOR
Event Summary: Failed to read the port's Neighbor Information register.
Event Class: System
Problem Description:
A failure occurred while reading the XBC Port's Neighbor Information register. Data Field: (port << 44) | (xbc num << 32) | ret status
Cause / Action: Cause: Fabric Access Failure Action: Contact HP Support personnel to analyze the fabric.
Automated Recovery: None
Event Generation Threshold: 1 occurrence

Event 2091

Severity: MAJOR
Event Summary: A read of a XBC Port Status register failed.
Event Class: System
Problem Description:
A read of a XBC Port Status register failed. Data Field: (xbc num << 32) | xbc port
Cause / Action:
Cause: write to XBC failed Action: Contact HP Support personnel to check the XBC
Automated Recovery: None
Event Generation Threshold: 1 occurrence

Event 2092

Severity: MAJOR
Event Summary: This port's hardware has experienced a Fatal Error. It cannot be used.
Event Class: System
Problem Description:
While examining a XBC port for traversability, the Port Status Register was read from the XBC. The FE bit is set indicating that there was a fatal problem with the link. Data Field: (port << 44) | (xbc num << 32) | port status
Cause / Action:
Cause: The link may have experienced a Multi-Bit Error. Action: Contact HP Support personnel to analyze the fabric.
Automated Recovery: None
Event Generation Threshold: 1 occurrence

Event 2093

Severity: MAJOR
Event Summary: The port does not have the Hardware Link bit set on.
Event Class: System
Problem Description:
While examining a XBC port for traversability, the Port Status Register was read from the XBC. The HW Link bit was not set in the data read from the register. The hardware has not detected a link connected to this port. Data Field: (port << 44) | (xbc num << 32) | port status
Cause / Action: Cause: The port is not connected to another chip. Either the link is physically not attached, one side of the link is not powered, or there are problems with the hardware. Action: Contact HP Support personnel to analyze the fabric.
Automated Recovery: None
Event Generation Threshold: 1 occurrence

Event 2094

Severity: MAJOR
Event Summary: An unexpected failure occurred while checking the port landmine state.
Event Class: System
Problem Description:
While examining a fabric route between two XBCs, there was a failure reading a XBC port's landmine state from an XBC scratch register. Data Field: (port << 44) | (xbc num << 32) | ret status
Cause / Action: Cause: There was a failure performing a read while traversing the route to the target XBC. Action: Contact HP Support personnel to analyze the fabric.
Automated Recovery: None
Event Generation Threshold: 1 occurrence

Event 2095

Severity: MAJOR
Event Summary: The port's output enable bit is not set. The link has not been configured.
Event Class: System
Problem Description:
While examining a XBC port for traversability, the Port Status Register was read from the XBC. The OE bit is not set, indicating that the link was not configured during boot (Fabric Discovery). Data Field: (port << 44) | (xbc num << 32) | port status
Cause / Action: Cause: The link probably experienced errors before routing occurred. The link may also have been reset which would have cleared the OE bit. Action: Contact HP Support personnel to analyze the fabric.
Automated Recovery: None
Event Generation Threshold: 1 occurrence

Event 2096

Severity: MAJOR
Event Summary: The XBC port is not connected to its expected neighbor!
Event Class: System
Problem Description:
Each XBC port is expected to be connected in a specific configuration according to the topology. The current configuration is not appropriate for the topology being used. Data Field: (port << 44) | (xbc num << 32)
Cause / Action: Cause: The XBC link is connected wrong. The XBc link may also have been reset which would have cleared the neighbor information. The XBC link may be programmed incorrectly Action: Contact HP Support personnel to analyze the fabric.
Automated Recovery: None
Event Generation Threshold: 1 occurrence

Event 2097

Severity: MAJOR
Event Summary: The port's presence detect bit is not set. The fabric link is not connected.
Event Class: System
Problem Description:
While examining a XBC port for traversability, the Port Status Register was read from the XBC. The presence detect bit was not set in the data read from the register. Data Field: (port << 44) | (xbc num << 32) | port status
Cause / Action:
Cause: The port is not connected to another chip. Either the link is physically not attached, one side of the link is not powered, or there are problems with the hardware. Action: Contact HP Support personnel to analyze the fabric.
Automated Recovery: None
Event Generation Threshold: 1 occurrence

Event 2098

Severity: MAJOR
Event Summary: The port was found to be landmined
Event Class: System
Problem Description:
The port being examined has experienced errors and has been marked to not be used. Data Field: (port << 44) | (xbc num << 32) | ret status
Cause / Action: Cause: There was a failure performing a read while traversing the route to the target XBC. Action: Contact HP Support personnel to analyze the fabric.
Automated Recovery: None
Event Generation Threshold: 1 occurrence

Event 2099

Severity: MAJOR
Event Summary: There was an error reading from a fabric table in the PDC ROM.
Event Class: System
Problem Description:
While checking if a route is traversable, there was an error getting the address to the XBC Neighbor Info table stored in the PDC ROM. Data Field: return status
Cause / Action: Cause: PDC runtime error. Action: Contact HP Support personnel to analyze the fabric and PDC
Automated Recovery: None
Event Generation Threshold: 1 occurrence

Event 2100

Severity: MAJOR
Event Summary: There was an error reading from a fabric table in the PDC ROM.
Event Class: System
Problem Description:
While checking if a route is traversable, there was an error getting the address to the XBC Neighbor Info table stored in the PDC ROM. Data Field: return status
Cause / Action: Cause: PDC runtime error. Action: Contact HP Support personnel to analyze the fabric and PDC
Automated Recovery: None
Event Generation Threshold: 1 occurrence

Event 2101

Severity: MAJOR
Event Summary: The XBC number provided is not a valid XBC Chip Id.
Event Class: System
Problem Description:
The argument passed into the function is invalid. If this code was called from a proc, then the argument should have been checked at the proc entrance. Data Field: (port << 44) | (xbc num << 32)
Cause / Action: Cause: An invalid XBC number was provided. Action: Contact HP Support personnel to analyze the fabric.
Automated Recovery: None
Event Generation Threshold: 1 occurrence

Event 2102

Severity: MAJOR
Event Summary: The current fabric port is connected to a CC when a XBC was expected.
Event Class: System
Problem Description:
When checking if a route is traversable, each link is put through a sanity check. This test ensures that the link connects ports that are supposed to be connected. In this case the port indicates it is connected to a CC, however the topology indicates it should be connected to a XBC. Data Field: (port << 44) | (xbc num << 32)
Cause / Action: Cause: Hardware failure. Invalid topology. Action: Contact HP Support personnel to analyze the fabric.
Automated Recovery: None
Event Generation Threshold: 1 occurrence

Event 2103

Severity: MAJOR
Event Summary: The port number provided is not a valid internal port number.
Event Class: System
Problem Description:
The port number passed into this function is not an internal port number. This is a misuse of the functionality. Data Field: (port << 44) | (xbc num << 32)
Cause / Action:
Cause: PDC runtime error. Action: Contact HP Support personnel to analyze the fabric and PDC
Automated Recovery: None
Event Generation Threshold: 1 occurrence

Event 2104

Severity: MAJOR
Event Summary: The current fabric port is connected to a XBC when a CC was expected.
Event Class: System
Problem Description:
When checking if a route is traversable, each link is put through a sanity check. This test ensures that the link connects ports that are supposed to be connected. In this case the port indicates it is connected to a XBC, however the topology indicates it should be connected to a CC. Data Field: (port << 44) | (xbc num << 32)
Cause / Action: Cause: Hardware failure. Invalid topology. Action: Contact HP Support personnel to analyze the fabric.
Automated Recovery: None
Event Generation Threshold: 1 occurrence

Event 2105

Severity: MAJOR
Event Summary: The neighbor port number is not an internal port number.
Event Class: System
Problem Description:
Fabric code uses internal port numbers for XBC ports except when an external number is absolutely necessary. The port number used here breaks the convention. Data Field: (port << 44) | (xbc num << 32)
Cause / Action: Cause: Hardware failure. Invalid topology. Action: Contact HP Support personnel to analyze the fabric.
Automated Recovery: None
Event Generation Threshold: 1 occurrence

Event 2106

Severity: MAJOR
Event Summary: The neighbor fabric port was expected to be connected to a XBC.
Event Class: System
Problem Description:
When checking if a route is traversable, each link is put through a sanity check. This test ensures that the link connects ports that are supposed to be connected. In this case the port is expected to be connected to a XBC, however the topology indicates it should be connected to a CC. Data Field: neighbor port
Cause / Action:
Cause: Hardware failure. Invalid topology. Action: Contact HP Support personnel to analyze the fabric.
Automated Recovery: None
Event Generation Threshold: 1 occurrence

Event 2107

Severity: MAJOR
Event Summary: There was an error reading a XBC port status register.
Event Class: System
Problem Description:
While checking if a route is traversable, there was an error reading the port status register on a XBC. Data Field: return status
Cause / Action: Cause: Hardware problem. Intermittent XBC errors. Action: Contact HP Support personnel to analyze the fabric.
Automated Recovery: None
Event Generation Threshold: 1 occurrence

Event 2108

Severity: MAJOR
Event Summary: The neighbor chip does not indicate it is connected to the correct chip.
Event Class: System
Problem Description:
When checking if a route is traversable, each link is put through a sanity check. This test ensures that the link connects ports that are supposed to be connected. In this case the neighbor chip thinks it is connected to a chip other than the source chip. Data Field: (port << 44) | (xbc num << 32)
Cause / Action:
Cause: Hardware failure. Invalid topology. Action: Contact HP Support personnel to analyze the fabric.
Automated Recovery: None
Event Generation Threshold: 1 occurrence

Event 2109

Severity: MAJOR
Event Summary: The neighbor chip is not registering its neighbor appropriately.
Event Class: System
Problem Description:
When checking if a route is traversable, each link is put through a sanity check. This test ensures that the link connects ports that are supposed to be connected. In this case the current chip correctly identified its neighbor. However, its neighbor indicates it is connected to something different. Data Field: (expected neighbor xbc num << 32) | expected neighbor port
Cause / Action: Cause: Hardware failure. Invalid topology. Action: Contact HP Support personnel to analyze the fabric.
Automated Recovery: None
Event Generation Threshold: 1 occurrence

Event 2110

Severity: MAJOR
Event Summary: The XBC port is connected incorrectly.
Event Class: System
Problem Description:
When checking if a route is traversable, each link is put through a sanity check. This test ensures that the link connects ports that are supposed to be connected. In this case the neighbor port thinks it is connected to a port other than the source port. Data Field: (Expected neighbor port << 16) | actual neighbor port num Cause / Action:
Cause: Hardware failure. Invalid topology. Action: Contact HP Support personnel to analyze the fabric.
Automated Recovery: None
Event Generation Threshold: 1 occurrence

Event 2111

Severity: MAJOR
Event Summary: The XBC port connected is not the expected port.
Event Class: System
Problem Description:
When checking if a route is traversable, each link is put through a sanity check. This test ensures that the link connects ports that are supposed to be connected. In this case the port is connected to the right chip, but the wrong port on that chip. Data Field: (expected neighbor port << 16) | (actual neighbor port)
Cause / Action:
Cause: Hardware failure. Invalid topology. Action: Contact HP Support personnel to analyze the fabric.
Automated Recovery: None
Event Generation Threshold: 1 occurrence

Event 2112

Severity: MAJOR
Event Summary: The neighbor type read is not the type that was expected.
Event Class: System
Problem Description:
Each fabric chip is setup a specific way for its topology. This chip was found to be connected in an unexpected way. Data Field: (expected nieghbor type << 48) | (actual neighbor type)
Cause / Action: Cause: Hardware failure. Invalid topology. Action: Contact HP Support personnel to analyze the fabric.
Automated Recovery: None
Event Generation Threshold: 1 occurrence

Event 2113

Severity: MAJOR
Event Summary: The fabric chip's neighbor info indicates an unknown neighbor type.
Event Class: System
Problem Description:
When checking if a route is traversable, each link is put through a sanity check. This test ensures that the link connects ports that are supposed to be connected. In this case the neighbor info register contains invalid information. Data Field: neighbor type Cause / Action:
Cause: Hardware failure. Invalid topology. Action: Contact HP Support personnel to analyze the fabric.
Automated Recovery: None
Event Generation Threshold: 1 occurrence

Event 2114

Severity: MAJOR
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 # << 32) | external XBC port number
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. A subsequent FABRIC_REMOTE_ROUTING chassis code should indicate what the route around for the port is. Action: Contact HP Support personnel to analyze the crossbars, flex cables, backplanes, and other fabric components.
Automated Recovery: None
Event Generation Threshold: 1 occurrence

Event 2115

Severity: MAJOR
Event Summary: Could not determine health state of a XBC port.
Event Class: System
Problem Description:
During the collection of neighbor info, the health of the port could not be determined. This port was expected to be healthy. Data Field: (xbc num << 32) | xbc port
Cause / Action:
Cause: XBC register read failure Action: Contact HP Support personnel to analyze the crossbar chip.
Automated Recovery: None
Event Generation Threshold: 1 occurrence

Event 2116

Severity: MAJOR
Event Summary: Failed reading the XBC port register
Event Class: System
Problem Description:
While checking the port health, a read to the Port Status register or a Scratch Register failed. Data Field: (xbc num << 32) | xbc port
Cause / Action: Cause: XBC register read failure Action: Contact HP Support personnel to analyze the crossbar chip.
Automated Recovery: None
Event Generation Threshold: 1 occurrence

Event 2117

Severity: MAJOR
Event Summary: The XBC number provided is not a valid XBC Chip Id.
Event Class: System
Problem Description:
The argument passed into the function is invalid. If this code was called from a proc, then the argument should have been checked at the proc entrance. Data Field: (port << 44) | (xbc num << 32)
Cause / Action: Cause: PDC runtime error. Action: Contact HP Support personnel to analyze the fabric and PDC
Automated Recovery: None
Event Generation Threshold: 1 occurrence

Event 2118

Severity: MAJOR
Event Summary: The port number provided is not a valid XBC Internal Port Number
Event Class: System
Problem Description:
The argument passed into the function is invalid. If this code was called from a proc, then the argument should have been checked at the proc entrance. Data Field: (port << 44) | (xbc num << 32)
Cause / Action: Cause: PDC runtime error. Action: Contact HP Support personnel to analyze the fabric and PDC
Automated Recovery: None
Event Generation Threshold: 1 occurrence

Event 2119

Severity: MAJOR
Event Summary: PDC cannot determine the system's topology
Event Class: System
Problem Description:
PDC initially determines the system's topology early in fabric discoevery. Later in fabric discovery PDC compares the topology found by Discover Topology with the topology it sees. If the two do not match this chassis code is sent. This chassis code should only come out when port 4 is not routable and PDC sees a connection to a fabric component on port 5 that it does not expect. Data Field: (xbc num << 32) | topology
Cause / Action: Cause: There is a fabric problem that causes two different XBCs to appear as if they have different topologies. There is probably a broken link that needs to be repaired. Action: Contact HP Support personnel to analyze the fabric.
Automated Recovery: None
Event Generation Threshold: 1 occurrence

Event 2120

Severity: MAJOR
Event Summary: Could not complete routing of the kitty-korner XBC
Event Class: System
Problem Description:
Port 4 on the local XBC was broken and a route-around was attempted. During the route-around, there was a problem performing remote routing on the kitty-korner XBC. Chassis codes sent before this one may provide more details about the exact nature of the problem. The executing cell will attempt a fabricless boot. Data Field: (xbc num << 32) | return status
Cause / Action: Cause: The local XBC's port 4 is not healthy. A failure was encountered while performing remote routing on the kitty-korner XBC, most likely due to a problem with the system backplane or local cell. Action: Contact HP Support personnel to analyze the fabric.
Automated Recovery: None
Event Generation Threshold: 1 occurrence

Event 2121

Severity: MAJOR
Event Summary: Could not complete routing of the sister XBC
Event Class: System
Problem Description:
Port 4 on the local XBC was broken and a route-around was attempted. During the route-around, there was a problem performing remote routing on the sister XBC. Chassis codes sent before this one may provide more details about the exact nature of the problem. The executing cell will attempt a fabricless boot. Data Field: (xbc num << 32) | return status
Cause / Action: Cause: The local XBC's port 4 is not healthy. A failure was encountered while performing remote routing on the sister XBC, most likely due to a problem with the system backplane or local cell. Action: Contact HP Support personnel to analyze the fabric.
Automated Recovery: None
Event Generation Threshold: 1 occurrence

Event 2122

Severity: MAJOR
Event Summary: PDC cannot determine the system's topology
Event Class: System
Problem Description:
PDC initially determines the system's topology early in fabric discoevery. Later in fabric discovery PDC compares the topology found by DiscoverTopology with the topology it sees. If the two do not match this chassis code is sent. This chassis code should only come out when ports 4 and 5 are not routable. In such a case, PDC could be running in a dual-cabinet configuration with two links (to the other cabinet) being broken. Data Field: (xbc num << 32) | topology
Cause / Action:
Cause: There is a fabric problem that causes two different XBCs to appear as if they have different topologies. There is likely a broken link in the fabric. Action: Contact HP Support personnel to analyze the fabric.
Automated Recovery: None
Event Generation Threshold: 1 occurrence

Event 2123

Severity: CRITICAL
Event Summary: Remote routing failed
Event Class: System
Problem Description:
Remote routing failed. Chassis codes sent before this one may provide more details about the exact nature of the problem. The executing cell will attempt a fabricless boot. Data Field: return status
Cause / Action: Cause: Remote routing failure Action: Contact HP Support personnel to analyze the fabric.
Automated Recovery: None
Event Generation Threshold: 1 occurrence

Event 2124

Severity: MAJOR
Event Summary: This system is a Fatboy with a bad built-in port and a bad port 5
Event Class: System
Problem Description:
The system was determined to be a fatboy. The local XBC's built-in port and port 5 were both unhealthy. Therefore, too many links are borken to continue. The executing cell will attempt a fabricless boot. Data Field: (builtin port health << 48) | port 5 health
Cause / Action: Cause: The built-in port and port 5 of the local XBC are not healthy. Action: Contact HP Support personnel to analyze the crossbar and flex cables.
Automated Recovery: None
Event Generation Threshold: 1 occurrence

Event 2125

Severity: MAJOR
Event Summary: There are too many broken XBC links in the system
Event Class: System
Problem Description:
System is a fatboy. Ports 4 & 5 of the local XBC are both broken. Chassis codes sent before this one may provide more details about the exact nature of the problem. The executing cell will attempt a fabricless boot. Data Field: (xbc num << 32) Cause / Action:
Cause: Both the ports 4 and 5 of the local XBC had errors. Action: Contact HP Support personnel to analyze the fabric.
Automated Recovery: None
Event Generation Threshold: 1 occurrence

Event 2126

Severity: MAJOR
Event Summary: PDC cannot determine the system's topology.
Event Class: System
Problem Description:
PDC initially determines the system's topology early in fabric discoevery. Later in fabric discovery PDC compares the topology found by DiscoverTopology with the topology it sees. If the two do not match this chassis code is sent. Data Field: (xbc num << 32) | topology
Cause / Action: Cause: There is a fabric problem that causes two different XBCs to appear as if they have different topologies. There is likely a broken link in the fabric. Action: Contact HP Support personnel to analyze the fabric.
Automated Recovery: None
Event Generation Threshold: 1 occurrence

Event 2127

Severity: MAJOR
Event Summary: Couldn't get the XBC number connected to port 5 of the sister XBC
Event Class: System
Problem Description:
Port 5 of the sister XBC is connected to something, but the number of the XBC to which it is connected could not be determined. Could be because the link is not healthy. Data Field: (port << 44) | (xbc num << 32) | ret status
Cause / Action: Cause: A hardware problem with the sister XBC or the link connected to port 5 of the sister XBC. Action: Contact HP Support personnel to analyze the fabric.
Automated Recovery: None
Event Generation Threshold: 1 occurrence

Event 2128

Severity: MAJOR
Event Summary: Too many XBC-to-XBC were broken in the complex.
Event Class: System
Problem Description:
Both the built-in port and port 4 of the Local XBC are broken. The executing cell will halt. Data Field: (builtin port health << 32) | port 4 health
Cause / Action: Cause: Port status indicated that both the built-in port and port 4 had errors. Action: Contact HP Support personnel to analyze the fabric.
Automated Recovery: None
Event Generation Threshold: 1 occurrence

Event 2129

Severity: MAJOR
Event Summary: Error while writing the topology to the XBC general purpose register.
Event Class: System
Problem Description:
During remote routing, a failed XBC register access (read or write) prevented the fabric topology from being written to a XBC global general purpose register. Data Field: (xbc num << 32) | return status
Cause / Action: Cause: XBC register read failure Action: Contact HP Support personnel to analyze the crossbar chip.
Automated Recovery: None
Event Generation Threshold: 1 occurrence

Event 2130

Severity: CRITICAL
Event Summary: A routing error has been discovered
Event Class: System
Problem Description:
A routing error was read from a XBC's General Purpose Register 3. The cell will attempt a fabricless boot. Data Field: 0x0BADBADBADBADBAD - failed routing opposite corner XBC - must find current XBC being routed from previous chassis codes 0x0000000000000000 - cell's local XBC has been noted having a routing error.
Cause / Action:
Cause: Possibilities include (but are not limited to):: Failed link Defective XBC port Found a invalid device on the fabric System backplane error Action: Contact HP Support personnel to analyze the fabric.
Automated Recovery: None
Event Generation Threshold: 1 occurrence

Event 2131

Severity: MAJOR
Event Summary: While routing the XBC to XBC ports, a read of the XBC Forward Progess failed.
Event Class: System
Problem Description:
A read to the XBC scratch register used to store the forward progess state failed. This state indicates which port is to be routed next. Since the read failed, the state cannot be determined. The processor will indicate that it encountered routing errors. Data Field: return status
Cause / Action: Cause: XBC register read failure Action: Contact HP Support personnel to analyze the crossbar chip.
Automated Recovery: None
Event Generation Threshold: 1 occurrence

Event 2132

Severity: MAJOR
Event Summary: Fabric Discovery was stuck in a loop for 10 seconds
Event Class: System
Problem Description:
While routing a remote XBC, a cell occassionally gets stuck in a loop because the XBC's forward progress state is not updated correctly. This chassis code indicates that the cell has been in this loop for ten seconds and will now reboot. The cell should join the partition properly on the next boot. Data Field: (target cell << 56) | (xbc num << 32) | forward progress
Cause / Action: Cause: The XBC forward progress state is trashed. Upon reboot, the cell should join the PD and finish booting. Action: Contact HP Support personnel to analyze the fabric.
Automated Recovery: None
Event Generation Threshold: 1 occurrence

Event 2133

Severity: MAJOR
Event Summary: While trying to route the XBC ports, an unexpected fwd progress state was found
Event Class: System
Problem Description:
While trying to route the XBC ports, an unexpected forward progress state was found. This may cause the processor to get stuck in an endless loop. A timer will be started to prevent the processor from being assassinated. Data Field: (target cell << 56) | (xbc num << 32) | forward progress
Cause / Action: Cause: The XBC forward progress state is trashed. Upon reboot, the cell should join the PD and finish booting. Action: Contact HP Support personnel to analyze the fabric.
Automated Recovery: None
Event Generation Threshold: 1 occurrence

Event 2134

Severity: MAJOR
Event Summary: The XBC SM4 is being taken from another cell
Event Class: System
Problem Description:
A cell that owns the SM4 has not made sufficient progress in routing so another cell is attempting to take ownership. Data Field: Data Field: (cell << 56) | (port << 44) | (xbc << 32) | return status
Cause / Action: Cause: The cell which owns the SM4 has not made sufficient routing progress Action: Contact HP Support personnel to analyze the fabric.
Automated Recovery: None
Event Generation Threshold: 1 occurrence

Event 2135

Severity: MAJOR
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. Data Field: (cell << 56) | (port << 44) | (xbc << 32) | return status Cause / Action:
Cause: Another cell won the race and got the semaphore before this cell. This would be apparent in chassis codes. XBC write or read failure. Action: Contact HP Support personnel to analyze the fabric.
Automated Recovery: None
Event Generation Threshold: 1 occurrence

Event 2136

Severity: MAJOR
Event Summary: PDC attempted a fabric SM4 takeover but had a problem reading the SM4
Event Class: System
Problem Description:
When a cell holds a fabric semaphore for an extended period of time, PDC will attempt to takeover the semaphore so that the rest of the cells will have access to it. This chassis code is sent when PDC successfully releases the SM4 from the cell that hung, but then fails to read the SM4 as part of obtaining the SM4 for itself. Data Field: (cell << 56) | (port << 44) | (xbc << 32) | return status
Cause / Action: Cause: There was a fabric failure reading the XBCs CSRs. Action: Look for FABRIC_READ_ERROR_xxx chassis codes or a chassis code indicating the data from the XBC slices are different. Contact HP Support personnel to analyze the fabric.
Automated Recovery: None
Event Generation Threshold: 1 occurrence

Event 2137

Severity: CRITICAL
Event Summary: A problem occurred in routing the fabric
Event Class: System
Problem Description:
A problem occurred in routing the complex. The cell will halt. Refer to the FABRIC_ROUTING_ERROR chassis code for more information. Data Field: 0x0000000000000000
Cause / Action:
Cause: A problem occurred in routing the fabric. See the FABRIC_ROUTING_ERROR chassis code for more details Action: Contact HP Support personnel to analyze the fabric.
Automated Recovery: None
Event Generation Threshold: 1 occurrence

Event 2138

Severity: MAJOR
Event Summary: An unknown routing state was encountered
Event Class: System
Problem Description:
An unknown routing state was read from the XBC scratch register. Data Field: xbc num
Cause / Action: Cause: PDC runtime error. Action: Contact HP Support personnel to analyze the fabric and PDC
Automated Recovery: None
Event Generation Threshold: 1 occurrence

Event 2139

Severity: MAJOR
Event Summary: XBC ECC error
Event Class: System
Problem Description:
An ECC error was detected across the XBC link.
Cause / Action: Cause: An ECC error detected on the XBC Link Action: Contact HP Support personnel to analyze the fabric.
Automated Recovery: None
Event Generation Threshold: 1 occurrence

Event 2140

Severity: MAJOR
Event Summary: PDC did not recognize the fabric topology of the system.
Event Class: System
Problem Description:
PDC was determining which XBCs are expected to be present based on the system's topology. The topology was stored on the XBC during fabric discovery by the PDC that routed the fabric. PDC did not recognize the topology stored on the XBC or did not expect the topology it found. Data Field: return status
Cause / Action: Cause: PDC runtime error. Action: Contact HP Support personnel to analyze the fabric and PDC
Automated Recovery: None
Event Generation Threshold: 1 occurrence

Event 2141

Severity: MAJOR
Event Summary: PDC did not recognize the system type in the external backplane type register.
Event Class: System
Problem Description:
PDC uses the backplane type to control how it determines what parts of the fabric are present. PDC did not recognize the backplane type. Data Field: system type
Cause / Action:
Cause: Unknown system type Action: Contact HP Support personnel to analyze the backplanes and activity logs
Automated Recovery: None
Event Generation Threshold: 1 occurrence

Event 2142

Severity: MAJOR
Event Summary: PDC did not recognize the fabric topology of the system
Event Class: System
Problem Description:
PDC was verifying that a cell could exist in the fabric topology of the machine on which it is running. The topology was stored on the XBC during fabric discovery by the PDC that routed the fabric. PDC did not recognize the topology stored on the XBC. Data Field: topology
Cause / Action: Cause: Unknown system type Action: Contact HP Support personnel to analyze the backplanes and activity logs
Automated Recovery: None
Event Generation Threshold: 1 occurrence

Event 2143

Severity: MAJOR
Event Summary: PDC could not determine the fabric topology of the system
Event Class: System
Problem Description:
This chassis code is sent when PDC is trying to see if a cell exists in the current system's topology. PDC determines the topology during boot and stores it in an XBC CSR. This chassis code is sent when PDC cannot read that CSR. Data Field: return status
Cause / Action: Cause: The failure was probably one of the following: a multi-bit error reading a fabric CSR, unable to access an XBC, XBC bit slices returned inconsistent data. Look for fabric problems. Action: Contact HP Support personnel to analyze the fabric.
Automated Recovery: None
Event Generation Threshold: 1 occurrence

Event 2144

Severity: MAJOR
Event Summary: Tried all XBC links to do route around
Event Class: System
Problem Description:
Tried all XBC links while trying to route around the fabric Data Field: XBC # currently trying to route
Cause / Action:
Cause: No more links to try to route around Action: Contact HP Support personnel to analyze the fabric.
Automated Recovery: None
Event Generation Threshold: 1 occurrence

Event 2145

Severity: MAJOR
Event Summary: An unexpected fabric status error has occurred
Event Class: System
Problem Description:
Could not determine if there was a MBE, if the XBC slices are different, if address was not in range. Data Field: Status which could not be determined
Cause / Action: Cause: Error in reading / writing a XBC CSR Action: Contact HP Support personnel to analyze the fabric.
Automated Recovery: None
Event Generation Threshold: 1 occurrence

Event 2146

Severity: MAJOR
Event Summary: Error in determining the numbers of the 1st and last XBCs in the complex.
Event Class: System
Problem Description:
Failed in an attempt to determine the numbers of the first and last XBCs in the complex. A chassis code preceeding this one will give more details about the nature of the problem. The executing cell will attempt a fabricless boot. Data Field: return status
Cause / Action: Cause: A problem accessing the local XBC. Action: Contact HP Support personnel to analyze the fabric.
Automated Recovery: None
Event Generation Threshold: 1 occurrence

Event 2147

Severity: CRITICAL
Event Summary: A XBC register read access failed.
Event Class: System
Problem Description:
An attempt was made to read the landmine state from the XBC general purpose register, but the read access failed. The executing cell will attempt a fabricless boot. Data Field: (port << 44) | (xbc num << 32) | ret status
Cause / Action: Cause: A hardware failure caused an error during a XBC register read access. Action: Contact HP Support personnel to analyze the fabric.
Automated Recovery: None
Event Generation Threshold: 1 occurrence

Event 2148

Severity: CRITICAL
Event Summary: The number of landmined XBC ports is not allowed.
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 executing cell will attempt a fabricless boot due to this error. Data Field: landmine count
Cause / Action: Cause: PDC runtime error, which was probably exposed due to a hardware failure. Action: Contact HP Support personnel to analyze the fabric.
Automated Recovery: None
Event Generation Threshold: 1 occurrence

Event 2149

Severity: CRITICAL
Event Summary: The port on one side of a link was landmined, but the neighbor port was not.
Event Class: System
Problem Description:
If a link is landmined, the XBC ports on both sides of the link should indicate the landmine. The port specified in the data field of this chassis code was NOT landmined, even though the port on the other side of the link was. The executing cell will attempt a fabricless boot. Data Field: (port << 44) | (xbc num << 32) | ret status
Cause / Action: Cause: PDC runtime error, probably exposed by a hardware failure. Action: Contact HP Support personnel to analyze the fabric.
Automated Recovery: None
Event Generation Threshold: 1 occurrence

Event 2150

Severity: CRITICAL
Event Summary: A XBC register read access failed.
Event Class: System
Problem Description:
Attempted to read a neighbor XBC's port status register, but failed. The executing cell will attempt a fabricless boot. Data Field: (port << 44) | (xbc num << 32) | ret status
Cause / Action: Cause: A hardware failure caused an error during a XBC register read access. Action: Contact HP Support personnel to analyze the fabric.
Automated Recovery: None
Event Generation Threshold: 1 occurrence

Event 2151

Severity: CRITICAL
Event Summary: A XBC register read access failed.
Event Class: System
Problem Description:
An attempt was made to read the landmine state from the XBC general purpose register, but the read access failed. The executing cell will attempt a fabricless boot. Data Field: (port << 44) | (xbc num << 32) | ret status
Cause / Action: Cause: A hardware failure caused an error during a XBC register read access. Action: Contact HP Support personnel to analyze the fabric.
Automated Recovery: None
Event Generation Threshold: 1 occurrence

Event 2152

Severity: CRITICAL
Event Summary: A XBC register read access failed.
Event Class: System
Problem Description:
Attempted to read the XBC port status register, but failed. The executing cell will attempt fabricless boot. Data Field: (port << 44) | (xbc num << 32) | ret status
Cause / Action:
Cause: A hardware failure caused an error during a XBC register read access. Action: Contact HP Support personnel to analyze the fabric.
Automated Recovery: None
Event Generation Threshold: 1 occurrence

Event 2153

Severity: CRITICAL
Event Summary: A XBC register read access failed.
Event Class: System
Problem Description:
Attempted to obtain the port's neighbor information by reading the XBC port neighbor information register, but the read access failed. The executing cell will attempt fabricless boot. Data Field: (port << 44) | (xbc num << 32) | ret status
Cause / Action:
Cause: A hardware failure caused an error during a XBC register read access. Action: Contact HP Support personnel to analyze the fabric.
Automated Recovery: None
Event Generation Threshold: 1 occurrence

Event 2154

Severity: MAJOR
Event Summary: The specified XBC could not be reached via its PIOB route.
Event Class: System
Problem Description:
Could not traverse to the XBC using the PIOB route. Chassis codes sent before this one should give more details about the exact nature of the problem. The executing cell will attempt a fabricless boot. Data Field: (port << 44) | (xbc num << 32) | ret status
Cause / Action: Cause: A hardware failure caused the PIOB route to be invalid. PDC runtime error. Action: Contact HP Support personnel to analyze the fabric.
Automated Recovery: None
Event Generation Threshold: 1 occurrence

Event 2155

Severity: MAJOR
Event Summary: A XBC register read access failed.
Event Class: System
Problem Description:
There was an error reading one of the XBC routing registers. Data Field: (port << 44) | (xbc num << 32) | ret status
Cause / Action: Cause: A XBC register read access failed due to a hardware problem. Action: Contact HP Support personnel to analyze the fabric.
Automated Recovery: None
Event Generation Threshold: 1 occurrence

Event 2156

Severity: MAJOR
Event Summary: The XBC general purpose register indicates an unknown topology.
Event Class: System
Problem Description:
The fabric topology read from the XBC general purpose register was unrecognized. Data Field: (port << 44) | (xbc num << 32) | ret status
Cause / Action: Cause: XBC register read failure Action: Contact HP Support personnel to analyze the crossbar chip.
Automated Recovery: None
Event Generation Threshold: 1 occurrence

Event 2157

Severity: MAJOR
Event Summary: The routing for this XBC is not useable.
Event Class: System
Problem Description:
The routing tables for the XBC were not valid. Refer to preceeding chassis codes for details about the nature of the problem. The executing cell will attempt a fabricless boot. Data Field: (port << 44) | (xbc num << 32) | ret status
Cause / Action:
Cause: Could not access the XBC. PDC runtime error. Action: Contact HP Support personnel to analyze the fabric.
Automated Recovery: None
Event Generation Threshold: 1 occurrence

Event 2158

Severity: MAJOR
Event Summary: An internal PDC function was called for a topology not supported by that fcn.
Event Class: System
Problem Description:
At the end of fabric discovery, an internal PDC function was called to validate the fabric state. However, the function does not support the fabric topology. The executing cell will attempt a fabricless boot. Data Field: topology
Cause / Action: Cause: PDC runtime error. Action: Contact HP Support personnel to analyze the fabric and PDC
Automated Recovery: None
Event Generation Threshold: 1 occurrence

Event 2159

Severity: CRITICAL
Event Summary: PDC tried to get a fabric semaphore and detected a fatal error.
Event Class: System
Problem Description:
There was a fabric access problem when trying to grab the Global SM4. The executing cell will attempt a fabricless boot. Data Field: (port << 44) | (xbc num << 32) | ret status
Cause / Action: Cause: This is probably an intermittent hardware failure. Action: Contact HP Support personnel to analyze the fabric.
Automated Recovery: None
Event Generation Threshold: 1 occurrence

Event 2160

Severity: CRITICAL
Event Summary: Auditing the XBC Global Semaphore for ownership has failed.
Event Class: System
Problem Description:
A failure occurred while checking if the semaphore's owner is making progress. This is a sign of a fabric connectivity problem. The cell will attempt a fabricless boot! Data Field: (port << 44) | (xbc num << 32) | ret status
Cause / Action:
Cause: likely fabric hardware failure Action: Contact HP Support personnel to analyze the fabric.
Automated Recovery: None
Event Generation Threshold: 1 occurrence

Event 2161

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. As a result, the cell will reboot. Data Field: (port << 44) | (xbc num << 32) | ret status
Cause / Action: Cause: XBC Key Contention. Hardware Failure Action: Contact HP Support personnel to analyze the fabric.
Automated Recovery: None
Event Generation Threshold: 1 occurrence

Event 2162

Severity: MAJOR
Event Summary: There was a Multi-Bit Error detected during the XBC write.
Event Class: System
Problem Description:
There was a Multi-Bit Error detected during the XBC write. Data Field: xbc num
Cause / Action: Cause: likely fabric hardware failure Action: Contact HP Support personnel to analyze the fabric.
Automated Recovery: None
Event Generation Threshold: 1 occurrence

Event 2163

Severity: MAJOR
Event Summary: Fabric write did not compare
Event Class: System
Problem Description:
A read after write did not compare Data Field: (data read after write << 32) | (desired data to be written)
Cause / Action: Cause: XBC slice has failed CC to XBC link failed Action: Contact HP Support personnel to analyze the fabric.
Automated Recovery: None
Event Generation Threshold: 1 occurrence

Event 2164

Severity: MAJOR
Event Summary: Could not read the routing register for the PIOB route.
Event Class: System
Problem Description:
Testing the fabric data route between two XBCs requires testing of the PIOB route as well. During this test, a read failure occurred which prevent the read of the routing register needed for the PIOB route. Or the routing register was uninitialized. Data Field: return status
Cause / Action: Cause: XBC or Port reset prior to the read. Fabric access failure. Action: Contact HP Support personnel to analyze the fabric.
Automated Recovery: None
Event Generation Threshold: 1 occurrence

Event 2165

Severity: MAJOR
Event Summary: A link in the fabric Data route is not useable.
Event Class: System
Problem Description:
Testing the fabric data route between two XBCs. During this test, a link on the PIOB route was found to have errors preventing its use. Data Field: (port << 44) | (xbc num << 32)
Cause / Action: Cause: The Data link has errors Action: Contact HP Support personnel to analyze the fabric.
Automated Recovery: None
Event Generation Threshold: 1 occurrence

Event 2166

Severity: MAJOR
Event Summary: A link in the fabric Data route is not useable.
Event Class: System
Problem Description:
Testing the fabric data route between two XBCs. During this test, a fabric access failure occurred which prevented completion of the testing. The link is not traversable. Data Field: (port << 44) | (xbc num << 32)
Cause / Action: Cause: The Data link has errors Action: Contact HP Support personnel to analyze the fabric.
Automated Recovery: None
Event Generation Threshold: 1 occurrence

Event 2167

Severity: MAJOR
Event Summary: Couldn't get Local XBC num from CC
Event Class: System
Problem Description:
An error reading the CC prevented PDC from obtaining the number of the local XBC Data Field: return status
Cause / Action:
Cause: Failed to read a CSR on the CC. Action: Contact HP Support personnel to analyze the CC
Automated Recovery: None
Event Generation Threshold: 1 occurrence

Event 2168

Severity: MAJOR
Event Summary: The XBC number provided is not a valid XBC Chip Id.
Event Class: System
Problem Description:
The argument passed into the function is invalid. If this code was called from a proc, then the argument should have been checked at the proc entrance. Data Field: (local xbc num << 32) | target XBC
Cause / Action: Cause: An invalid XBC number was provided. Action: Contact HP Support personnel to analyze the fabric.
Automated Recovery: None
Event Generation Threshold: 1 occurrence

Event 2169

Severity: MAJOR
Event Summary: The PIOB route to the neighbor XBC is not useable.
Event Class: System
Problem Description:
The PIOB route to the neighbor XBC is no longer traversable. It can no longer be used. Data Field: (xbc num << 32)
Cause / Action: Cause: Errors have been found somewhere on the fabric route. Action: Contact HP Support personnel to analyze the fabric.
Automated Recovery: None
Event Generation Threshold: 1 occurrence

Event 2170

Severity: MAJOR
Event Summary: The PIOB route to the neighbor XBC is not useable.
Event Class: System
Problem Description:
The PIOB route to the neighbor XBC could not be fully tested. An error was encountered which prevented completion of the tests. The route is no longer useable. Data Field: (xbc num << 32)
Cause / Action: Cause: Errors have been encountered somewhere on the fabric route. Fabric access failure. Action: Contact HP Support personnel to analyze the fabric.
Automated Recovery: None
Event Generation Threshold: 1 occurrence

Event 2171

Severity: MAJOR
Event Summary: The local XBC to local cell link is bad
Event Class: System
Problem Description:
The link between the local cell and the local XBC is not healthy, as indicated by either the CC or the XBC. Data Field: (cell << 56) | (xbc num << 32)
Cause / Action:
Cause: The link between the local cell and local XBC is bad. Action: Contact HP Support personnel to analyze the fabric.
Automated Recovery: None
Event Generation Threshold: 1 occurrence

Event 2172

Severity: MAJOR
Event Summary: A failure was encountered on the cell's link to the fabric.
Event Class: System
Problem Description:
While testing the fabric route between two XBCs, an error was encountered on the link between the local cell and the local XBC. Probably a fabric access failure. Data Field: (cell << 56) | (xbc num << 32)
Cause / Action: Cause: The CC to XBC link may not be connected. There may be intermittent errors. Action: Contact HP Support personnel to analyze the fabric.
Automated Recovery: None
Event Generation Threshold: 1 occurrence

Event 2173

Severity: MAJOR
Event Summary: An invalid XBC number was passed into a fabric walk function.
Event Class: System
Problem Description:
This function is only intended to traverse routes that either start or end at the local XBC. This chassis code inidicates that this construct is not satisfied. Data Field:(target xbc << 60) | (xbc num << 32)
Cause / Action: Cause: An invalid XBC number was provided. Action: Contact HP Support personnel to analyze the fabric.
Automated Recovery: None
Event Generation Threshold: 1 occurrence

Event 2174

Severity: MAJOR
Event Summary: A link in the fabric PIOB route is not useable.
Event Class: System
Problem Description:
Testing the fabric data route between two XBCs requires testing of the PIOB route as well. During this test, a link on the PIOB route was found to have errors preventing its use. Data Field: (port << 44) | (xbc num << 32)
Cause / Action: Cause: The PIOB link has errors Action: Contact HP Support personnel to analyze the fabric.
Automated Recovery: None
Event Generation Threshold: 1 occurrence

Event 2175

Severity: MAJOR
Event Summary: A link in the fabric PIOB route is not useable.
Event Class: System
Problem Description:
Testing the fabric data route between two XBCs requires testing of the PIOB route as well. During this test, a fabric access failure occurred which prevented completion of the testing. The link is not traversable. Data Field: (port << 44) | (xbc num << 32)
Cause / Action: Cause: The PIOB link has errors Action: Contact HP Support personnel to analyze the fabric.
Automated Recovery: None
Event Generation Threshold: 1 occurrence

Event 2176

Severity: MAJOR
Event Summary: There was an error reading the XBC port's remote routing register.
Event Class: System
Problem Description:
While testing the fabric route between two XBCs, a port's remote routing register either could not be read or was found to be uninitialized. This code should not be called prior to fabric routing, so this indicates that there is a problem on the port. Data Field: return status
Cause / Action: Cause: Routing register no longer contains valid information or is no longer accessable. Action: Contact HP Support personnel to analyze the fabric.
Automated Recovery: None
Event Generation Threshold: 1 occurrence

Event 2177

Severity: MAJOR
Event Summary: Could not read the XBC Port's Neighbor Info Register
Event Class: System
Problem Description:
Testing the fabric route between two XBCs. An unexpected error occurred while reading the port's Neighbor Info register on the XBC. Data Field: (port << 44) | (xbc num << 32) | ret status
Cause / Action: Cause: Fabric access error. Action: Contact HP Support personnel to analyze the fabric.
Automated Recovery: None
Event Generation Threshold: 1 occurrence

Event 2178

Severity: MAJOR
Event Summary: The XBC Global Semaphore is not owned, yet is required to write this register.
Event Class: System
Problem Description:
During XBC writes, the CSR addresses are scanned to determine if they are protected by the Global Semaphore. If they are protected, then the semaphore must be owned in order for a write to proceed. Data Field: csr address
Cause / Action: Cause: A semaphore takeover has occurred. This cell took too long to route the fabric and now it must halt. PDC tried to write a protected CSR without the semaphore. Action: Contact HP Support personnel to analyze the fabric.
Automated Recovery: None
Event Generation Threshold: 1 occurrence

Event 2179

Severity: FATAL
Event Summary: PDC failed to read the cabinet type for another cell in the partition
Event Class: System
Problem Description:
PDC checks that all of the cells in a partition are installed in the same type of cabinet. PDC failed to read the cabinet type for another cell in the partition. PDC will reset all of the cells in the partition when this error is detected. The data field contains the physical location of the cell reporting the event.
Cause / Action:
Cause: PDC was unable to read a data structure for another cell in the partition. This should never happen unless there is an intermittent problem with the main backplane. Action: Contact HP support to confirm that the main backplane is functioning properly.
Automated Recovery: None
Event Generation Threshold: 1 occurrence

Event 2180

Severity: FATAL
Event Summary: PDC failed to read the CPU HVERSION for another cell in the partition
Event Class: System
Problem Description:
PDC attempts to insure that all of the CPUs in the partition have the same HVERSION. PDC failed to read the CPU HVERSION for another cell in the partition. PDC will reset all of the cells in the partition when this error is detected. The data field contains the physical location of the cell detected the event.
Cause / Action:
Cause: PDC was unable to read a data structure for another cell in the partition. This should never happen unless there is an intermittent problem with the main backplane. Action: Contact HP support to confirm that the main backplane is functioning properly.
Automated Recovery: None
Event Generation Threshold: 1 occurrence

Event 2181

Severity: FATAL
Event Summary: PDC failed to read the CPU speeds for another cell in the partition
Event Class: System
Problem Description:
PDC attempts to make sure that all of the CPUs in the partition run at the same speed. This chassis code is sent when PDC is unable to perform this check PDC will reset all of the cells in the partition when this error is detected. The data field contains the physical location of the cell detecting the event.
Cause / Action: Cause: PDC was unable to read a data structure for another cell in the partition. This should never happen unless there is an intermittent problem with the main backplane. Action: Contact HP support to confirm that the main backplane is functioning properly.
Automated Recovery: None
Event Generation Threshold: 1 occurrence

Event 2182

Severity: FATAL
Event Summary: Could not access local rendezvous set data in cell previously accessed
Event Class: System
Problem Description:
All of the cells create a set of cells that they could rendezvous with. This cell tried to read that set on another cell and failed. PDC will reset all of the cells in the partition when this error is detected.
Cause / Action: Cause: PDC was unable to read a data structure for another cell in the partition. This should never happen unless there is an intermittent problem with the main backplane. Action: Contact HP support to confirm that the main backplane is functioning properly.
Automated Recovery: None
Event Generation Threshold: 1 occurrence

Event 2183

Severity: FATAL
Event Summary: Unable to access the PDC version info on cell in rendezvous set
Event Class: System
Problem Description:
PDC checks to insure that all of the cells have the same version of PDC. PDC failed accessing the PDC version on another cell. PDC will reset all of the cells in the partition when this error is detected. The data field contains the physical location of the cell detecting the event.
Cause / Action: Cause: PDC was unable to read a data structure for another cell in the partition. This should never happen unless there is an intermittent problem with the main backplane. Action: Contact HP support to confirm that the main backplane is functioning properly.
Automated Recovery: None
Event Generation Threshold: 1 occurrence

Event 2184

Severity: MAJOR
Event Summary: PDC was unable to read a data structure on the local cell board.
Event Class: System
Problem Description:
PDC was unable to read a data structure on the local cell board. When this error is detected, the cell will be reset for reconfiguration and will not join the partition on this boot. The data field contains the physical location of the cell that detected the event.
Cause / Action: Cause: The cell board or PDH riser card may not be functioning correctly. Action: Contact HP support to confirm that the cell board and PDH riser card are functioning properly.
Automated Recovery: None
Event Generation Threshold: 1 occurrence

Event 2185

Severity: MAJOR
Event Summary: Boot failed because the IPL address was either zero or not 2K aligned.
Event Class: System
Problem Description:
IPL address is the byte offset from the start of the boot device to the program IPL. This chassis code comes out when a boot fails because the IPL address was either zero or not 2K aligned.
Cause / Action: Cause: Bad boot disk image or network boot image. Action: Ensure the correct boot path is being used to access the boot device. Replace boot disk image or network boot image.
Automated Recovery: None
Event Generation Threshold: 1 occurrence

Event 2186

Severity: MAJOR
Event Summary: Boot failed because the LIF image's checksum was invalid.
Event Class: System
Problem Description:
Boot failed because the LIF image's checksum was invalid. The system should return to BCH.
Cause / Action:
Cause: Bad boot disk image or network boot image. Action: Ensure the correct boot path is being used to access the boot device. Replace boot disk image or network boot image.
Automated Recovery: None
Event Generation Threshold: 1 occurrence

Event 2187

Severity: MAJOR
Event Summary: Boot failed because IPL ENTRY offset was invalid
Event Class: System
Problem Description:
IPL ENTRY is the offset into the IPL program where execution starts. A chassis codes is emitted when a boot fails because this offset is not less than the size of the IPL image or is not word aligned.
Cause / Action: Cause: Bad boot disk image or network boot image. Action: Ensure the correct boot path is being used to access the boot device. Replace boot disk image or network boot image.
Automated Recovery: None
Event Generation Threshold: 1 occurrence

Event 2188

Severity: MAJOR
Event Summary: Boot failed because size of IPL was invalid
Event Class: System
Problem Description:
IPL size is the total size (in bytes) of the IPL program. This chassis code is emitted on a failed boot due to IPL size being zero, not 2K aligned, or greater than 256 K.
Cause / Action:
Cause: Bad boot disk image or network boot image. Action: Ensure the correct boot path is being used to access the boot device. Replace boot disk image or network boot image.
Automated Recovery: None
Event Generation Threshold: 1 occurrence

Event 2189

Severity: MAJOR
Event Summary: Boot failed - LIF image had an invalid value for magic number
Event Class: System
Problem Description:
Boot failed because LIF (boot disk or network boot) image had an invalid value for the HP-architected magic number. System should return to BCH.
Cause / Action: Cause: The boot path did not specify a valid HP boot disk image or network boot image. Action: Ensure the correct boot path is being used to access the boot device. Replace boot disk image or network boot image.
Automated Recovery: None
Event Generation Threshold: 1 occurrence

Event 2190

Severity: MAJOR
Event Summary: At rendezvous, a cell is found to be incompatible with the core cell.
Event Class: System
Problem Description:
At rendezvous, a cell is found to be incompatible with the core cell. Data field contains physical location of the incompatible cell. This chassis code should be immediately preceded by a chassis code explaining the specific incompatibility, (e.g. BOOT_INCOMPATIBLE_CPU_ID)
Cause / Action: Cause: Cell is incompatible with core cell. Action: See the preceding chassis code in the log for specific incompatibility and proper action.
Automated Recovery: None
Event Generation Threshold: 1 occurrence

Event 2191

Severity: MAJOR
Event Summary: Failed to program the partition set into the CC
Event Class: System
Problem Description:
PDC could not program the CC to recognize which cells are in the partition. The cell will be reset. The data field contains the value that was attempted to program.
Cause / Action: Cause: A hardware problem with the CC or the cell board. Action: Contact HP Support to confirm the CC and cell board are functioning properly.
Automated Recovery: None
Event Generation Threshold: 1 occurrence

Event 2192

Severity: MAJOR
Event Summary: Cell did not rendezvous with the rest of the cells in the partition
Event Class: System
Problem Description:
A cell that is booting checks to determine if the other cells in the partition are ready to rendezvous with it. If the other cells in the partition have already rendezvoused, the cell cannot join the partition. PDC accommodates a relatively large skew between cells, but will eventually give up waiting on a cell. Data field is the physical location of the cell that "missed the boat".
Cause / Action:
Cause: The cell booted too slowly. It either started booting too late or has some problem that caused it to boot slowly. Action: Reboot the partition from the MP and see if the cell is able rendezvous into the partition. If the cell is still too slow, contact HP Support to confirm the cell board and CPUs are function properly.
Automated Recovery: None
Event Generation Threshold: 1 occurrence

Event 2193

Severity: MAJOR
Event Summary: Physical location of the cell from BOOT_CELL_STATE_ERROR_STATUS
Event Class: System
Problem Description:
This is an informational IPMI event used to provide the physical location of the cell board affected by an error indicated by a preceding IPMI event. The data field holds the physical location of the cell board.
Cause / Action: Cause: Refer to preceding high-alert level IPMI events for cause/action information. Action: -
Automated Recovery: None
Event Generation Threshold: 1 occurrence

Event 2194

Severity: FATAL
Event Summary: Cells in the partition have different complex profiles.
Event Class: System
Problem Description:
Cell boards in the same partition have different complex profiles. The partition will be rebooted and cannot be fully booted until the problem is resolved. The data field is a bitmap of cells where cell 0 is the least significant bit and cell 63 is the most significant bit. A one on a cell's bit indicated that the cell has a complex profile that did not match that of the core cell.
Cause / Action:
Cause: An error occurred which prevented the complex profiles from being distributed properly. Action: Create and distribute a new complex profile using ParMgr on a functional partition in the complex. Restore the last complex profile using the "CC" command from the MP, then use ParMgr to create a new complex profile. Generate a genesis complex profile using the "CC" command from the MP, then use ParMgr to create a new complex profile. Cause: A hardware problem exists with MP or PDHC hardware. Action: Contact HP Support to confirm the MP and PDHC are functioning properly.
Automated Recovery: None
Event Generation Threshold: 1 occurrence

Event 2195

Severity: FATAL
Event Summary: Cells in the partition have different complex profiles.
Event Class: System
Problem Description:
Cell boards in the same partition have different complex profiles. The partition will be rebooted and cannot be fully booted until the problem is resolved. The data field is a bitmap of cells where cell 0 is the least significant bit and cell 63 is the most significant bit. A one on a cell's bit indicated that the cell has a complex profile that did not match that of the core cell.
Cause / Action:
Cause: An error occurred which prevented the complex profiles from being distributed properly. Action: Create and distribute a new complex profile using ParMgr on a functional partition in the complex. Restore the last complex profile using the "CC" command from the MP, then use ParMgr to create a new complex profile. Generate a genesis complex profile using the "CC" command from the MP, then use ParMgr to create a new complex profile. Cause: A hardware problem exists with MP or PDHC hardware. Action: Contact HP Support to confirm the MP and PDHC are functioning properly.
Automated Recovery: None
Event Generation Threshold: 1 occurrence

Event 2196

Severity: FATAL
Event Summary: Cells in the partition have different complex profiles.
Event Class: System
Problem Description:
Cell boards in the same partition have different complex profiles. The partition will be rebooted and cannot be fully booted until the problem is resolved. The data field is a bitmap of cells where cell 0 is the least significant bit and cell 63 is the most significant bit. A one on a cell's bit indicated that the cell has a complex profile that did not match that of the core cell.
Cause / Action:
Cause: An error occurred which prevented the complex profiles from being distributed properly. Action: Create and distribute a new complex profile using ParMgr on a functional partition in the complex. Restore the last complex profile using the "CC" command from the MP, then use ParMgr to create a new complex profile. Generate a genesis complex profile using the "CC" command from the MP, then use ParMgr to create a new complex profile. Cause: A hardware problem exists with MP or PDHC hardware. Action: Contact HP Support to confirm the MP and PDHC are functioning properly.
Automated Recovery: None
Event Generation Threshold: 1 occurrence

Event 2197

Severity: FATAL
Event Summary: Cells in the partition have different complex profiles
Event Class: System
Problem Description:
Cell boards in the same partition have different complex profiles. The partition will be rebooted and cannot be fully booted until the problem is resolved. The data field is a bitmap of cells where cell 0 is the least significant bit and cell 63 is the most significant bit. A one on a cell's bit indicated that the cell has a complex profile that did not match that of the core cell.
Cause / Action:
Cause: An error occurred which prevented the complex profiles from being distributed properly. Action: Create and distribute a new complex profile using ParMgr on a functional partition in the complex. Restore the last complex profile using the "CC" command from the MP, then use ParMgr to create a new complex profile. Generate a genesis complex profile using the "CC" command from the MP, then use ParMgr to create a new complex profile. Cause: A hardware problem exists with MP or PDHC hardware. Action: Contact HP Support to confirm the MP and PDHC are functioning properly.
Automated Recovery: None
Event Generation Threshold: 1 occurrence

Event 2198

Severity: FATAL
Event Summary: Cells in the partition have different complex profiles.
Event Class: System
Problem Description:
Cell boards in the same partition have different complex profiles. The partition will be rebooted and cannot be fully booted until the problem is resolved. The data field is a bitmap of cells where cell 0 is the least significant bit and cell 63 is the most significant bit. A one on a cell's bit indicated that the cell has a complex profile that did not match that of the core cell.
Cause / Action:
Cause: An error occurred which prevented the complex profiles from being distributed properly. Action: Create and distribute a new complex profile using ParMgr on a functional partition in the complex. Restore the last complex profile using the "CC" command from the MP, then use ParMgr to create a new complex profile. Generate a genesis complex profile using the "CC" command from the MP, then use ParMgr to create a new complex profile. Cause: A hardware problem exists with MP or PDHC hardware. Action: Contact HP Support to confirm the MP and PDHC are functioning properly.
Automated Recovery: None
Event Generation Threshold: 1 occurrence

Event 2199

Severity: FATAL
Event Summary: Cells in the partition have different complex profiles.
Event Class: System
Problem Description:
Cell boards in the same partition have different complex profiles. The partition will be rebooted and cannot be fully booted until the problem is resolved. The data field is a bitmap of cells where cell 0 is the least significant bit and cell 63 is the most significant bit. A one on a cell's bit indicated that the cell has a complex profile that did not match that of the core cell.
Cause / Action:
Cause: An error occurred which prevented the complex profiles from being distributed properly. Action: Create and distribute a new complex profile using ParMgr on a functional partition in the complex. Restore the last complex profile using the "CC" command from the MP, then use ParMgr to create a new complex profile. Generate a genesis complex profile using the "CC" command from the MP, then use ParMgr to create a new complex profile. Cause: A hardware problem exists with MP or PDHC hardware. Action: Contact HP Support to confirm the MP and PDHC are functioning properly.
Automated Recovery: None
Event Generation Threshold: 1 occurrence

Event 2200

Severity: MAJOR
Event Summary: Unable to access core I/O data on a cell that rendezvoused with the partition.
Event Class: System
Problem Description:
PDC was unable to access data on another cell that rendezvoused with the partition. The executing cell will be reset. The data field contains the physical location of the cell that will be reset.
Cause / Action: Cause: Hardware problem with the main backplane. Action: Contact HP Support to confirm that the main backplane is functioning properly. Cause: Hardware problem with the cell board, CPU, or PDH riser card. Action: Contact HP Support to confirm the cell board, CPUs, and PDH riser card are functioning properly.
Automated Recovery: None
Event Generation Threshold: 1 occurrence

Event 2201

Severity: FATAL
Event Summary: Unable to read a cell board register on another cell board
Event Class: System
Problem Description:
Unable to read a cell board register on a cell board that rendezvoused with the executing cell. All the cells that have rednezvoused (i.e. the entire partition) will be reset.
Cause / Action:
Cause: Hardware problem with the main backplane. Action: Contact HP Support to confirm that the main backplane is functioning properly. Cause: Hardware problem with the cell board, CPU, or PDH riser card. Action: Contact HP Support to confirm the cell board, CPUs, and PDH riser card are functioning properly.
Automated Recovery: None
Event Generation Threshold: 1 occurrence

Event 2202

Severity: FATAL
Event Summary: The partition console device wasn't ready.
Event Class: System
Problem Description:
Before accessing the console, PDC first checked to see if the console device was ready and found that it was not. The partition will be reset for reconfiguration. The data field contains the status from the PDC function that checks the console device.
Cause / Action:
Cause: Console timed out or PDC could not read the core I/O card. Action: Make sure that the core I/O card is installed correctly. Make sure the I/O chassis is installed correctly. Contact HP Support to confirm the core I/O card and I/O chassis are functioning properly.
Automated Recovery: None
Event Generation Threshold: 1 occurrence

Event 2203

Severity: MAJOR
Event Summary: The partition console device could not be configured.
Event Class: System
Problem Description:
PDC could not map the console device path to a PCI functional address (PFA) and therefore, could not configure the console.
Cause / Action: Cause: A hardware problem with the core I/O card or I/O chassis. Action: Make sure that the core I/O card is installed correctly. Make sure the I/O chassis is installed correctly. Contact HP Support personnel to confirm the core I/O card and I/O chassis are functioning properly.
Automated Recovery: None
Event Generation Threshold: 1 occurrence

Event 2204

Severity: MAJOR
Event Summary: A write attempt to a PDC data structure failed.
Event Class: System
Problem Description:
A write attempt to a data structure failed, most likely to another cell in the partition. The data field contains number of cell whose control structure could not be written. Cause / Action:
Cause: Hardware problem with the main backplane. Action: Contact HP Support to confirm that the main backplane is functioning properly. Cause: Hardware problem with the cell board, CPU, or PDH riser card. Action: Contact HP Support to confirm the cell board, CPUs, and PDH riser card are functioning properly.
Automated Recovery: None
Event Generation Threshold: 1 occurrence

Event 2205

Severity: FATAL
Event Summary: Could not write a cell board register on a cell that has rendezvoused.
Event Class: System
Problem Description:
A write attempt to a cell board register failed for a cell that has rendezvoused into the partition. The cell that encountered the error will be reset. The data field contains the return value from PDC function that detected the error.
Cause / Action:
Cause: Hardware problem with the main backplane. Action: Contact HP Support to confirm that the main backplane is functioning properly. Cause: Hardware problem with the cell board, CPU, or PDH riser card. Note that this may be a problem on the remote cell rather than the cell that sent the chassis code. Action: Contact HP Support to confirm the cell board, CPUs, and PDH riser card are functioning properly, for both the local and remote cells.
Automated Recovery: None
Event Generation Threshold: 1 occurrence

Event 2206

Severity: MAJOR
Event Summary: A cell board register could not be accessed or register contents were invalid.
Event Class: System
Problem Description:
A cell board register could not be accessed or the register contents were invalid.
Cause / Action:
Cause: Hardware problem with the cell board, CPUs, or PDH riser card. Action: Contact HP Support to confirm the cell board, CPUs, and PDH riser card are functioning properly. Cause: The MP or PDHC are malfunctioning. Action: Check communication with the MP. Contact HP Support to confirm the MP and PDHC are functioning properly.
Automated Recovery: None
Event Generation Threshold: 1 occurrence

Event 2207

Severity: FATAL
Event Summary: The stable complex profile in this cell has an invalid sequence ID.
Event Class: System
Problem Description:
PDC detected an invalid sequence ID in the Stable complex profile on this cell. This means that the complex profile is not valid and that PDC cannot rendezvous the cells into a partition. The cell will be reset for reconfiguration, allowing another complex profile to be pushed out before it attempts to boot again.
Cause / Action: Cause: The cell did not have a valid complex profile. Action: Push a new complex profile out. Make sure that the utilities system is still functioning.
Automated Recovery: None
Event Generation Threshold: 1 occurrence

Event 2208

Severity: FATAL
Event Summary: The stable complex profile in this cell has an invalid sequence ID.
Event Class: System
Problem Description:
PDC detected an invalid checksum in the stable complex profile on this cell. This means that the complex profile is not valid and that PDC cannot rendezvous the cells into a partition. The cell will be reset for reconfiguration, allowing another complex profile to be pushed out before it attempts to boot again.
Cause / Action: Cause: The cell did not have a valid complex profile. Action: Push a new complex profile out. Make sure that the utilities system is still functioning.
Automated Recovery: None
Event Generation Threshold: 1 occurrence

Event 2209

Severity: MAJOR
Event Summary: Halting cell because PDC can't determine CPU type or revision.
Event Class: System
Problem Description:
While trying to determine whether the CPU is supported given the backplane and cell board revision, PDC couldn't access CPU type or revision, which is supposed to be available through a data structure.
Cause / Action: Cause: Hardware problem where either the PDH memory is bad or the CPU or CC corrupted the write or read to this area. Action: Contact HP Support personnel to troubleshoot the cell board
Automated Recovery: None
Event Generation Threshold: 1 occurrence

Event 2210

Severity: MAJOR
Event Summary: Halting cell because PDC was unable to determine the operating mode of the sys.
Event Class: System
Problem Description:
While trying to determine whether the CPU is supported on the backplane and cell board revision present, PDC needs to determine the operating mode of the system because PDC is more lenient if the system is in Manufacturing mode. This chassis log is sent if PDC wasn't able to determine whether or not the system is in MFG mode.
Cause / Action:
Cause: Hardware problem either with PDH memory or with the CPU or CC corrupting the read or write to the location containing the operating mode. Action: Contact HP Support personnel to troubleshoot the cell board.
Automated Recovery: None
Event Generation Threshold: 1 occurrence

Event 2212

Severity: MAJOR
Event Summary: Halting cell because PDC doesn't support the main backplane type.
Event Class: System
Problem Description:
While trying to determine whether or not the CPU is supported on the backplane and cell board revision present, PDC obtained an invalid backplane type.
Cause / Action: Cause: firmware is running on a machine with a different backplane type than it supports Action: ensure firmware version is correct for machine type and whether or not new backplane type might require new firmware C2: Hardware problem either with PDH memory or with the CPU or CC corrupting the read or write led to PDC obtaining an invalid backplane type value. A2: Contact HP Support personnel to troubleshoot the cell board. cause 2: PDC could not correctly determine the backplane type action2:
Automated Recovery: None
Event Generation Threshold: 1 occurrence

Event 2213

Severity: MAJOR
Event Summary: MBE free area of memory for late CPU selftests could not be found
Event Class: System
Problem Description:
A multi-bit error free area of memory, large enough for late CPU selftests, could not be found. The cell will be halted.
Cause / Action: Cause: Excessive errors due to defective DIMMs Coherency controller seating Action: Reseat DIMM(s) and reboot Replace DIMM(s) based on PDT entries or previous chassis codes Contact HP Support personnel to troubleshoot the Cell board
Automated Recovery: None
Event Generation Threshold: 1 occurrence

Event 2214

Severity: MAJOR
Event Summary: Couldn't find a large enough area of error free memory to load PDC
Event Class: System
Problem Description:
Couldn't find a large enough area of error free memory to load PDC into memory. The cell will be hard halted.
Cause / Action: Cause: Excessive errors in memory. Action: Reseat/troubleshoot DIMMs. Contact HP Support personnel to troubleshoot cell board
Automated Recovery: None
Event Generation Threshold: 1 occurrence

Event 2215

Severity: MAJOR
Event Summary: Couldn't find large enough area of error free memory to load PDC
Event Class: System
Problem Description:
Couldn't find a large enough area of error free memory to load PDC ROM into memory. Data field contains the ROM relocation address. Cell will halt. The cell will be halted.
Cause / Action:
Cause: Excessive errors in memory. Action: Reseat/troubleshoot DIMMs. Contact HP Support personnel to troubleshoot cell board
Automated Recovery: None
Event Generation Threshold: 1 occurrence

Event 2216

Severity: FATAL
Event Summary: More than one cell in a partition believes it is the core cell
Event Class: System
Problem Description:
More than one cell in a partition believes it is the core cell. Chassis code from one core cell will contain the physical location of the other core cell in its data field.
Cause / Action:
Cause: Cells in partition have different partition configuration data Fabric problem prevents the cells from seeing one another Action: Fix utilities problem/push out new complex profile Check fabric
Automated Recovery: None
Event Generation Threshold: 1 occurrence

Event 2217

Severity: FATAL
Event Summary: On a boot action of "Attempt next path", PDC tries invalid next path.
Event Class: System
Problem Description:
On a boot action of "Attempt next path", PDC tries invalid next path. The data field contains the invalid path. Cause / Action:
Cause: Should never happen, but it if does it would be caused by an internal PDC error. Action: Check for PDC upgrade Contact HP Support
Automated Recovery: None
Event Generation Threshold: 1 occurrence

Event 2218

Severity: MAJOR
Event Summary: Error occurred in NVM initialization
Event Class: System
Problem Description:
Error occurred in NVM initialization. Cell will reset and halt.
Cause / Action: Cause: NVM error Action: Contact HP Support personnel to troubleshoot the cell board
Automated Recovery: None
Event Generation Threshold: 1 occurrence

Event 2219

Severity: MAJOR
Event Summary: AutoBoot attempt failed, so stopping at BCH according to Boot Action
Event Class: System
Problem Description:
System was configured for AutoBoot. This chassis code indicates that the system attempted and failed to boot off a path whose Boot Action specified to attempt a boot and if the boot failed, return to BCH.
Cause / Action: Cause: No boot disk or defective boot disk. Invalid Path Action: Insert a good disk Specify a valid path from the BCH MAin menu
Automated Recovery: None
Event Generation Threshold: 1 occurrence

Event 2220

Severity: FATAL
Event Summary: Partition numbers mismatch in stable and partition configuration data
Event Class: System
Problem Description:
The stable complex profile can be used to get a cell's partition number because it contains the partition number to which the cell is assigned. The partition configuration data also holds a partition number. PDC compares the partition number in the partition configuration data with the partition to which the cell is assigned in the stable complex profile. If the two partition numbers are not the same, PDC sends this chassis code and resets the partition for reconfiguration. The data field is the partition number from the partition configuration data.
Cause / Action: Cause: The system utilities did not update ICM to contain the partition configuration data for this cell's partition. ICM is corrupted and the utilities system cannot write a corrected partition configuration data to the cell Action: Make sure the system utilities are working correctly. Make sure that PDH selftests are enabled. Try rebooting the cell. Try pushing a new complex profile to the cell Contact HP Support personnel to troubleshoot the cell board.
Automated Recovery: None
Event Generation Threshold: 1 occurrence

Event 2221

Severity: FATAL
Event Summary: Cell has been assigned to partition number not supported by MP
Event Class: System
Problem Description:
The stable complex profile has a field that tells PDC the maximum number of partitions that the system utilities will support. If PDC finds itself in a partition with a partition number greater than the maximum number of partitions supported by the system utilities, PDC will reset the cell for reconfiguration, allowing another stable complex profile to be pushed out to fix the problem.
Cause / Action:
Cause: The stable complex profile contains an illegal partition number for this cell. Action: Run SAM and remove the partition with the illegal number.
Automated Recovery: None
Event Generation Threshold: 1 occurrence

Event 2222

Severity: FATAL
Event Summary: Cell has different Stable Complex Profile sequence ID then core cell
Event Class: System
Problem Description:
PDC checks the sequence ID of the Stable complex profile for each of the cells in the partition. If they do not match, this means that the cells have different complex profiles. Since the complex profiles are used to assign resources to a partition, PDC, at this point, is unable to tell which version of the complex profile is correct. The partition cannot be booted until this problem is resolved. The data field contains the stable complex profile sequence ID from the cell that did not match the core cell.
Cause / Action: Cause: The core cell detected that a cell in its partition has a different complex profile than it does. Action: Look for a chassis code called,BOOT_CORE_CHECK_HCELL_PROFILE, to see which cell's complex profile was being checked. That cell is the cell that had the inconsistent complex profile. Make sure the utilities system is functioning and reboot the partition. If the reboot does not solve the problem, make sure PDH tests are enabled. Replace the cell with the inconsistent complex profile. Change core cells to see if the core cell is the cell that has the problem.
Automated Recovery: None
Event Generation Threshold: 1 occurrence

Event 2223

Severity: FATAL
Event Summary: Cell has different Stable Complex Profile checksum then core cell
Event Class: System
Problem Description:
PDC checks the sequence ID of the Stable complex profile for each of the cells in the partition. If they do not match, this means that the cells have different complex profiles. Since the complex profiles are used to assign resources to a Partition, PDC, at this point, is unable to tell which version of the complex profile is correct. The partition cannot be booted until this problem is resolved. The data field contains the checksum of the slave cell's stable complex profile.
Cause / Action: Cause: The core cell detected that a cell in its partition has a different complex profile than it does. Action: Look for a chassis code called,BOOT_CORE_CHECK_HCELL_PROFILE, to see which cell's complex profile was being checked. That cell is the cell that had the inconsistent complex profile. Make sure the utilities system is functioning and reboot the partition. If the reboot does not solve the problem, make sure PDH tests are enabled. Replace the cell with the inconsistent complex profile. Change core cells to see if the core cell is the cell that has the problem.
Automated Recovery: None
Event Generation Threshold: 1 occurrence

Event 2224

Severity: FATAL
Event Summary: Cell has different Dynamic Complex Profile sequence ID than core cell
Event Class: System
Problem Description:
PDC checks the sequence ID of the Dynamic complex profile for each of the cells in the partition. If they do not match, this means that the cells have different complex profiles. At this point, is unable to tell which version of the complex profile is correct. The partition cannot be booted until this problem is resolved. This chassis code indicates all of the cells that have complex profiles that do not match the core cell's. The data field is sequence ID from the dynamic complex profile for the slave cell that did not match the core cell.
Cause / Action:
Cause: The core cell detected that a cell in its partition has a different complex profile than it does. Action: Look for a chassis code called,BOOT_CORE_CHECK_HCELL_PROFILE, to see which cell's complex profile was being checked. That cell is the cell that had the inconsistent complex profile. Make sure the utilities system is functioning and reboot the partition. If the reboot does not solve the problem, make sure PDH tests are enabled. Replace the cell with the inconsistent complex profile. Change core cells to see if the core cell is the cell that has the problem.
Automated Recovery: None
Event Generation Threshold: 1 occurrence

Event 2225

Severity: FATAL
Event Summary: Cell has different Dynamic Complex Profile checksum then core cell
Event Class: System
Problem Description:
PDC checks the checksum of the Dynamic complex profile for each of the cells in the partition. If they do not match, this means that the cells have different complex profiles. At this point, is unable to tell which version of the complex profile is correct. The partition cannot be booted until this problem is resolved. This chassis code indicates all of the cells that have complex profiles that do not match the core cell's. The data field is the checksum of the slave cell's dynamic complex profile.
Cause / Action: Cause: The core cell detected that a cell in its partition has a different complex profile than it does. Action: Look for a chassis code called,BOOT_CORE_CHECK_HCELL_PROFILE, to see which cell's complex profile was being checked. That cell is the cell that had the inconsistent complex profile. Make sure the utilities system is functioning and reboot the partition. If the reboot does not solve the problem, make sure PDH tests are enabled. Replace the cell with the inconsistent complex profile. Change core cells to see if the core cell is the cell that has the problem.
Automated Recovery: None
Event Generation Threshold: 1 occurrence

Event 2226

Severity: FATAL
Event Summary: Cell has different Partition Config Data sequence ID then core cell
Event Class: System
Problem Description:
PDC checks the sequence ID of the partition configuration data for each of the cells in the partition. If they do not match, this means that the cells have different complex profiles. At this point, is unable to tell which version of the complex profile is correct. The partition cannot be booted until this problem is resolved. This chassis code indicates all of the cells that have complex profiles that do not match the core cell's. The data field is the sequence ID of the partition configuration data for the slave cell.
Cause / Action:
Cause: The core cell detected that a cell in its partition has a different complex profile than it does. Action: Look for a chassis code called,BOOT_CORE_CHECK_HCELL_PROFILE, to see which cell's complex profile was being checked. That cell is the cell that had the inconsistent complex profile. Make sure the utilities system is functioning and reboot the partition. If the reboot does not solve the problem, make sure PDH tests are enabled. Replace the cell with the inconsistent complex profile. Change core cells to see if the core cell is the cell that has the problem.
Automated Recovery: None
Event Generation Threshold: 1 occurrence

Event 2227

Severity: FATAL
Event Summary: Cell has different Partition Config Data checksum then core cell
Event Class: System
Problem Description:
PDC checks the checksum of the partition configuration data for each of the cells in the partition. If they do not match, this means that the cells have different complex profiles. At this point, is unable to tell which version of the complex profile is correct. The partition cannot be booted until this problem is resolved. This chassis code indicates all of the cells that have complex profiles that do not match the core cell's. The data field is the checksum for the PD profile of the slave cell.
Cause / Action: Cause: The core cell detected that a cell in its partition has a different complex profile than it does. Action: Look for a chassis code called,BOOT_CORE_CHECK_HCELL_PROFILE, to see which cell's complex profile was being checked. That cell is the cell that had the inconsistent complex profile. Make sure the utilities system is functioning and reboot the partition. If the reboot does not solve the problem, make sure PDH tests are enabled. Replace the cell with the inconsistent complex profile. Change core cells to see if the core cell is the cell that has the problem.
Automated Recovery: None
Event Generation Threshold: 1 occurrence

Event 2228

Severity: FATAL
Event Summary: PDC detected that cells in partition have different complex profiles
Event Class: System
Problem Description:
PDC on the core cell checks the sequence IDs and checksums for all of the complex profiles (stable, dynamic and partition data) on each of the cells in the partition. If they do not match the core cell's profiles, this means that the cells have different complex profiles. At this point, is unable to tell which version of the complex profile is correct. The partition cannot be booted until this problem is resolved. This chassis code data field contains a bitmap of all of the cells that have complex profiles that do not match the core cell's, where cell 0 is the least significant bit and cell 63 is the most significant bit. Cause / Action:
Cause: The complex profiles for the slaves cells in the partition do not match the complex profiles on the core cell. Action: Try to push out a new complex profile. Check for failures in the system utilities. As a last resort, try pushing out a genesis complex profile.
Automated Recovery: None
Event Generation Threshold: 1 occurrence

Event 2229

Severity: FATAL
Event Summary: Unable to write alive set to all coherency controllers in partition
Event Class: System
Problem Description:
Once PDC in the core cell has determined which cells are going to make it into the partition, it programs the coherency controllers on each of the slave cells and its own cell. If the write to the cell fails, PDC will send this chassis code, which contains, in the data field, the status from the function that failed to write to the coherency controllers.
Cause / Action: Cause: A Coherency controller (CC) in the partition failed a read after write test. Action: Reboot the partition. Look for chassis codes that indicate a primary or secondary CC error. Cause: Core Cell lost communication with a remote cell whose coherency controller it was attempting to write Action: Check for problems with the fabric.
Automated Recovery: None
Event Generation Threshold: 1 occurrence

Event 2230

Severity: FATAL
Event Summary: Failed while writing coherency set registers in coherency controller
Event Class: System
Problem Description:
Once PDC in the core cell has determined which cells are going to make it into the partition, it programs the coherency controllers on each of the slave cells and its own cell. If the write to the cell fails, PDC will send this chassis code, which contains, in the data field, the alive set of cells.
Cause / Action: Cause: A coherency controller (CC) in the partition failed a read after write test. Action: Reboot the partition. Look for chassis codes that indicate a primary or secondary CC error. Cause: Core Cell lost communication with a remote cell whose coherency controller it was attempting to write Action: Check for problems with the fabric.
Automated Recovery: None
Event Generation Threshold: 1 occurrence

Event 2231

Severity: MAJOR
Event Summary: PDC could not read the time of day on the RTC
Event Class: System
Problem Description:
PDC could not read the time of day (TOD) on the real time clock (RTC). Data field contains the status returned from the attempt to read the TOD.
Cause / Action: Cause: Semaphore problem. Action: Contact HP Support personnel to troubleshoot the cell board (suspect PDH) Check for PDC upgrade for possible internal software problem
Automated Recovery: None
Event Generation Threshold: 1 occurrence

Event 2232

Severity: MAJOR
Event Summary: A CPU's data area has overflowed its bounds.
Event Class: System
Problem Description:
A CPU's data area has overflowed its bounds. The data field contains the physical location of the CPU whose data area overflowed.
Cause / Action: Cause: Hardware problem with the CPU, cell board, or CC. Action: Contact HP Support to confirm the CPU, cell board and CC are function properly. Update PDC if a version is available to fix this problem.
Automated Recovery: None
Event Generation Threshold: 1 occurrence

Event 2233

Severity: MAJOR
Event Summary: A CPU is being stopped and deconfigured.
Event Class: System
Problem Description:
A CPU is being stopped and deconfigured. See the previous IPMI events to determine the reason that the CPU is being deconfigured. The data field is the physical location of the CPU being deconfigured.
Cause / Action: Cause: A CPU is being stopped and deconfigured. Action: See previous IPMI events to determine the reason that the CPU is being deconfigured. Contact HP Support personnel to confirm the CPU is functioning properly.
Automated Recovery: None
Event Generation Threshold: 1 occurrence

Event 2234

Severity: MAJOR
Event Summary: An invalid CPU number was passed to a procedure to deconfigure the CPU
Event Class: System
Problem Description:
An invalid CPU number was passed into a procedure to deconfigure the CPU. The cell will be halted. The data field is the value of the invalid CPU number. See BOOT_HALT_DUE_TO_PDC_ERROR following this chassis code for physical location of cell that has been halted.
Cause / Action: Cause: Hardware problem with the CPU, cell board, or CC. Action: Contact HP Support to confirm the CPU, cell board and CC are function properly. Update PDC if a version is available to fix this problem.
Automated Recovery: None
Event Generation Threshold: 1 occurrence

Event 2235

Severity: MAJOR
Event Summary: Invalid CPU number passed to procedure to schedule CPU deconfiguration
Event Class: System
Problem Description:
AAn invalid CPU number was passed into a procedure to deconfigure the CPU. The cell will be halted. The data field is the value of the invalid parameter.
Cause / Action: Cause: Hardware problem with the CPU, cell board, or CC. Action: Contact HP Support to confirm the CPU, cell board and CC are function properly. Update PDC if a version is available to fix this problem.
Automated Recovery: None
Event Generation Threshold: 1 occurrence

Event 2236

Severity: MAJOR
Event Summary: A CPU's stack has overflowed its allocated area
Event Class: System
Problem Description:
A CPU's stack has overflowed its allocated area. The data field contains the physical location of the CPU whose stack overflowed.
Cause / Action: Cause: Hardware problem with the CPU, cell board, or CC. Action: Contact HP Support to confirm the CPU, cell board and CC are function properly. Update PDC if a version is available to fix this problem.
Automated Recovery: None
Event Generation Threshold: 1 occurrence

Event 2237

Severity: FATAL
Event Summary: PDC encountered a fatal error after a boot device failed.
Event Class: System
Problem Description:
PDC encountered a fatal error after a boot device failed. The partition will be rebooted. The data field contains the return status from the PDC function that encountered the error.
Cause / Action:
Cause: Hardware problem with the I/O device, I/O chassis, or I/O cables between cells and I/O chassis. Action: Contact HP Support to confirm the I/O device is functioning properly. Contact HP Support to confirm the I/O chassis is functioning properly. Contact HP Support to confirm the I/O cables between cells and I/O chassis are functioning properly.
Automated Recovery: None
Event Generation Threshold: 1 occurrence

Event 2238

Severity: MAJOR
Event Summary: PDC could not access a data structure on the local cell
Event Class: System
Problem Description:
PDC could not access one of its own data structures on the local cell. The cell will be halted. The data field contains the return status from the PDC function that encountered the error.
Cause / Action: Cause: Hardware problem with the PDH riser card. Action: Contact HP Support to confirm the PDH riser card is functioning properly. Cause: Hardware problem with the CPU or cell board. Action: Contact HP Support to confirm the CPUs and cell board are functioning properly.
Automated Recovery: None
Event Generation Threshold: 1 occurrence

Event 2239

Severity: MAJOR
Event Summary: PDC could not access a data structure on the local cell
Event Class: System
Problem Description:
PDC could not access one of its own data structures on the local cell. The cell will be halted. The data field contains the return status from the PDC function that encountered the error.
Cause / Action: Cause: Hardware problem with the PDH riser card. Action: Contact HP Support to confirm the PDH riser card is functioning properly. Cause: Hardware problem with the CPU or cell board. Action: Contact HP Support to confirm the CPUs and cell board are functioning properly.
Automated Recovery: None
Event Generation Threshold: 1 occurrence

Event 2240

Severity: FATAL
Event Summary: Core cell failed to write to a PDC data structure on all cells in the partition
Event Class: System
Problem Description:
Core cell failed to write to a PDC data structure on all cells in the partition. Data field is the return status from the PDC function that encountered the error.
Cause / Action:
Cause: Hardware problem with the main backplane. Action: Contact HP Support to confirm the main backplane is functioning properly. Cause: Hardware problem with the cell board, CPU, or PDH riser card, possibly on another cell in the partition. Action: Look for IPMI events indicating errors on other cells in the partition. Contact HP Support to confirm the cell board, CPUs, and PDH riser card are functioning properly.
Automated Recovery: None
Event Generation Threshold: 1 occurrence

Event 2241

Severity: MAJOR
Event Summary: An error was detected in CC before HPMC handling was enabled.
Event Class: System
Problem Description:
An error was detected in the coherency controller (CC) before HPMC handling was enabled. The cell will be halted. The data field is a bit mask where bit numbers correspond to CC block numbers and a set bit indicates that block logged an error. The least-significant bit is bit 0.
Cause / Action: Cause: Hardware problem with the cell board, CPUs, or CC. Action: Contact HP Support personnel to confirm the cell board is functioning properly. Contact HP Support personnel to confirm the CPUs and CC are functioning properly.
Automated Recovery: None
Event Generation Threshold: 1 occurrence

Event 2242

Severity: MAJOR
Event Summary: The end marker separating two PDC data structures has been overwritten
Event Class: System
Problem Description:
The end marker separating two PDC data structures has been overwritten. Data field contains the expected value of the end marker.
Cause / Action: Cause: Hardware problem with PDH riser card Action: Contact HP Support to confirm PDH riser card is functioning properly. Upgrade PDC if a newer version is available to fix this problem. Cause: Hardware problem with CPU or cell board. Action: Contact HP Support to confirm CPUs and cell board are functioning properly. Upgrade PDC if a newer version is available to fix this problem.
Automated Recovery: None
Event Generation Threshold: 1 occurrence

Event 2243

Severity: MAJOR
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: Cause: Hardware problem with the PDH riser card. Action: Contact HP Support to confirm the PDH riser card is functioning properly. Cause: Hardware problem with the CPU or cell board. Action: Contact HP Support to confirm the CPUs and cell board are functioning properly.
Automated Recovery: None
Event Generation Threshold: 1 occurrence

Event 2244

Severity: MAJOR
Event Summary: PDC could not access a complex profile
Event Class: System
Problem Description:
PDC could not access a complex profile. Depending on when this error occurs, the local cell may be reset, the entire partition may be reset, or no action will be taken whatsoever. Data field contains the return status from the function that encountered the error.
Cause / Action: Cause: An error occurred which prevented the complex profiles from being distributed properly. Action: Create and distribute a new complex profile using ParMgr on a functional partition in the complex. Restore the last complex profile using the "CC" command from the MP, then use ParMgr to create a new complex profile. Generate a genesis complex profile using the "CC" command from the MP, then use ParMgr to create a new complex profile. Cause: A hardware problem exists with MP or PDHC hardware. Action: Contact HP Support to confirm the MP and PDHC are functioning properly.
Automated Recovery: None
Event Generation Threshold: 1 occurrence

Event 2245

Severity: MAJOR
Event Summary: PDC could not access a complex profile
Event Class: System
Problem Description:
PDC could not access a complex profile. Depending on when this error occurs, the local cell may be reset, the entire partition may be reset, or no action will be taken whatsoever. Data field contains the return status from the function that encountered the error.
Cause / Action: Cause: An error occurred which prevented the complex profiles from being distributed properly. Action: Create and distribute a new complex profile using ParMgr on a functional partition in the complex. Restore the last complex profile using the "CC" command from the MP, then use ParMgr to create a new complex profile. Generate a genesis complex profile using the "CC" command from the MP, then use ParMgr to create a new complex profile. Cause: A hardware problem exists with MP or PDHC hardware. Action: Contact HP Support to confirm the MP and PDHC are functioning properly.
Automated Recovery: None
Event Generation Threshold: 1 occurrence

Event 2246

Severity: MAJOR
Event Summary: PDC could not access a complex profile
Event Class: System
Problem Description:
PDC could not access a complex profile. Depending on when this error occurs, the local cell may be reset, the entire partition may be reset, or no action will be taken whatsoever. Data field contains the return status from the function that encountered the error.
Cause / Action: Cause: An error occurred which prevented the complex profiles from being distributed properly. Action: Create and distribute a new complex profile using ParMgr on a functional partition in the complex. Restore the last complex profile using the "CC" command from the MP, then use ParMgr to create a new complex profile. Generate a genesis complex profile using the "CC" command from the MP, then use ParMgr to create a new complex profile. Cause: A hardware problem exists with MP or PDHC hardware. Action: Contact HP Support to confirm the MP and PDHC are functioning properly.
Automated Recovery: None
Event Generation Threshold: 1 occurrence

Event 2247

Severity: FATAL
Event Summary: PDC could not access a CC hardware register.
Event Class: System
Problem Description:
PDC could not access a CC hardware register. The data field contains the physical location of the cell on which the CC hardware register could not be accessed.
Cause / Action:
Cause: Hardware problem with the CC. Action: Contact HP Support to confirm the CC is functioning properly. Cause: Hardware problem with the CPU or cell board. Action: Contact HP Support to confirm the CPU or cell board are functioning properly.
Automated Recovery: None
Event Generation Threshold: 1 occurrence

Event 2248

Severity: MAJOR
Event Summary: PDC could not access a complex profile
Event Class: System
Problem Description:
PDC could not access a complex profile. No action will be taken. Data field contains the return status from the function that encountered the error.
Cause / Action: Cause: An error occurred which prevented the complex profiles from being distributed properly. Action: Create and distribute a new complex profile using ParMgr on a functional partition in the complex. Restore the last complex profile using the "CC" command from the MP, then use ParMgr to create a new complex profile. Generate a genesis complex profile using the "CC" command from the MP, then use ParMgr to create a new complex profile. Cause: A hardware problem exists with MP or PDHC hardware. Action: Contact HP Support to confirm the MP and PDHC are functioning properly.
Automated Recovery: None
Event Generation Threshold: 1 occurrence

Event 2249

Severity: MAJOR
Event Summary: PDC could not access a complex profile
Event Class: System
Problem Description:
PDC could not access a complex profile. The cell will be reset.. Data field contains the return status from the function that encountered the error.
Cause / Action: Cause: An error occurred which prevented the complex profiles from being distributed properly. Action: Create and distribute a new complex profile using ParMgr on a functional partition in the complex. Restore the last complex profile using the "CC" command from the MP, then use ParMgr to create a new complex profile. Generate a genesis complex profile using the "CC" command from the MP, then use ParMgr to create a new complex profile. Cause: A hardware problem exists with MP or PDHC hardware. Action: Contact HP Support to confirm the MP and PDHC are functioning properly.
Automated Recovery: None
Event Generation Threshold: 1 occurrence

Event 2250

Severity: MAJOR
Event Summary: Error occurred initializing a PDC data structure
Event Class: System
Problem Description:
Error occurred initializing a PDC data structure. The cell will be reset. The data field contains the return status for the function that encountered the error.
Cause / Action:
Cause: Hardware problem with the PDH riser card. Action: Contact HP Support to confirm the PDH riser card is functioning properly. Cause: Hardware problem with the CPU or cell board. Action: Contact HP Support to confirm the CPUs and cell board are functioning properly.
Automated Recovery: None
Event Generation Threshold: 1 occurrence

Event 2251

Severity: FATAL
Event Summary: Error occurred accessing a PDC data structure
Event Class: System
Problem Description:
Error occurred accessing a PDC data structure. The partition will be reset. The data field contains the return status for the function that encountered the error.
Cause / Action:
Cause: Hardware problem with the PDH riser card. Action: Contact HP Support to confirm the PDH riser card is functioning properly. Cause: Hardware problem with the CPU or cell board. Action: Contact HP Support to confirm the CPUs and cell board are functioning properly.
Automated Recovery: None
Event Generation Threshold: 1 occurrence

Event 2252

Severity: FATAL
Event Summary: Error occurred accessing a PDC data structure
Event Class: System
Problem Description:
Error occurred accessing a PDC data structure. The partition will be reset. The data field contains the return status for the function that encountered the error.
Cause / Action:
Cause: Hardware problem with the PDH riser card. Action: Contact HP Support to confirm the PDH riser card is functioning properly. Cause: Hardware problem with the CPU or cell board. Action: Contact HP Support to confirm the CPUs and cell board are functioning properly.
Automated Recovery: None
Event Generation Threshold: 1 occurrence

Event 2253

Severity: FATAL
Event Summary: PDC could not access a complex profile
Event Class: System
Problem Description:
PDC could not access a complex profile. The partition will be reset.. Data field contains the return status from the function that encountered the error.
Cause / Action: Cause: An error occurred which prevented the complex profiles from being distributed properly. Action: Create and distribute a new complex profile using ParMgr on a functional partition in the complex. Restore the last complex profile using the "CC" command from the MP, then use ParMgr to create a new complex profile. Generate a genesis complex profile using the "CC" command from the MP, then use ParMgr to create a new complex profile. Cause: A hardware problem exists with MP or PDHC hardware. Action: Contact HP Support to confirm the MP and PDHC are functioning properly.
Automated Recovery: None
Event Generation Threshold: 1 occurrence

Event 2254

Severity: FATAL
Event Summary: PDC does not recognize CC chip revision.
Event Class: System
Problem Description:
PDC does not recognize the CC chip revision. The cell will be halted. The data field physical location of the cell that is having the CC revision problem.
Cause / Action:
Cause: Hardware problem with the CC. Action: Contact HP Support to confirm the CC is functioning properly. Upgrade PDC if a newer version is available to fix this problem. Cause: Hardware problem with the CPU or cell board. Action: Contact HP Support to confirm the CPU or cell board is functioning properly.
Automated Recovery: None
Event Generation Threshold: 1 occurrence

Event 2255

Severity: FATAL
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: Cause: Hardware problem with the PDH riser card. Action: Contact HP Support to confirm the PDH riser card is functioning properly. Cause: Hardware problem with the CPU or cell board. Action: Contact HP Support to confirm the CPUs and cell board are functioning properly.
Automated Recovery: None
Event Generation Threshold: 1 occurrence

Event 2256

Severity: MAJOR
Event Summary: Cell could not communicate with all the other cells in rendezvous set
Event Class: System
Problem Description:
PDC checks to make sure that all of the cells in the partition rendezvous set can communicate bilaterally. This cell could communicate with at least one of the other cells in the partition, but could not communicate with every cell that made the rendezvous. The cell will reset. Data field is the physical location of the cell.
Cause / Action:
Cause: This may indicate an intermittent problem with the main backplane. Action: Contact HP Support to confirm the main backplane is functioning properly. Contact HP Support to confirm the cell board is functioning properly.
Automated Recovery: None
Event Generation Threshold: 1 occurrence

Event 2257

Severity: FATAL
Event Summary: PDC could not access a complex profile
Event Class: System
Problem Description:
PDC could not access a complex profile. The partition will be reset. Data field contains the return status from the function that encountered the error.
Cause / Action: Cause: An error occurred which prevented the complex profiles from being distributed properly. Action: Create and distribute a new complex profile using ParMgr on a functional partition in the complex. Restore the last complex profile using the "CC" command from the MP, then use ParMgr to create a new complex profile. Generate a genesis complex profile using the "CC" command from the MP, then use ParMgr to create a new complex profile. Cause: A hardware problem exists with MP or PDHC hardware. Action: Contact HP Support to confirm the MP and PDHC are functioning properly.
Automated Recovery: None
Event Generation Threshold: 1 occurrence

Event 2258

Severity: FATAL
Event Summary: PDC could not access a complex profile
Event Class: System
Problem Description:
PDC could not access a complex profile. The partition will be reset. Data field contains the return status from the function that encountered the error.
Cause / Action: Cause: An error occurred which prevented the complex profiles from being distributed properly. Action: Create and distribute a new complex profile using ParMgr on a functional partition in the complex. Restore the last complex profile using the "CC" command from the MP, then use ParMgr to create a new complex profile. Generate a genesis complex profile using the "CC" command from the MP, then use ParMgr to create a new complex profile. Cause: A hardware problem exists with MP or PDHC hardware. Action: Contact HP Support to confirm the MP and PDHC are functioning properly.
Automated Recovery: None
Event Generation Threshold: 1 occurrence

Event 2259

Severity: FATAL
Event Summary: PDC_IODC failed to read information about the console
Event Class: System
Problem Description:
There was a problem attempting to use an architected PDC procedure to read information about the console. This failure in the PDC call is considered fatal, so the partition will be reset. The data field contains the return value from the function that encountered the error.
Cause / Action: Cause: PDC procedure failed. Action: Look for another error IPMI event such as BOOT_CONSOLE_PDC_IODC_HEADER_ERR that indicates that a problem occurred. Try rebooting the cell and then changing the core cell. Contact HP Support personnel to confirm the cell board is functioning properly.
Automated Recovery: None
Event Generation Threshold: 1 occurrence

Event 2260

Severity: FATAL
Event Summary: PDC detected an illegal CPU number passed to an internal function
Event Class: System
Problem Description:
An invalid CPU number was passed into an internal PDC function. The data field contains the invalid parameter. Cause / Action:
Cause: Hardware failure with CPU, CC or cell board. Action: Contact HP Support to confirm the CPUs, CC, and cell board are functioning properly. Update PDC if a version is available to fix this problem.
Automated Recovery: None
Event Generation Threshold: 1 occurrence

Event 2261

Severity: MAJOR
Event Summary: Error occurred accessing a PDC data structure
Event Class: System
Problem Description:
Error occurred accessing a PDC data structure. The executing CPU will be stopped. The data field contains the return status for the function that encountered the error.
Cause / Action:
Cause: Hardware problem with the PDH riser card. Action: Contact HP Support to confirm the PDH riser card is functioning properly. Cause: Hardware problem with the CPU or cell board. Action: Contact HP Support to confirm the CPUs and cell board are functioning properly.
Automated Recovery: None
Event Generation Threshold: 1 occurrence

Event 2262

Severity: MAJOR
Event Summary: PDC detected an illegal CPU number passed to an internal function
Event Class: System
Problem Description:
PDC detected an illegal CPU number passed to an internal function. The data field contains the invalid parameter.
Cause / Action: Cause: Hardware failure with CPU, CC or cell board. Action: Contact HP Support to confirm the CPUs, CC, and cell board are functioning properly. Update PDC if a version is available to fix this problem.
Automated Recovery: None
Event Generation Threshold: 1 occurrence

Event 2263

Severity: MAJOR
Event Summary: PDC received an error from the PDHC while trying to communicate with the MP
Event Class: System
Problem Description:
PDC received an error from the PDHC while trying to communicate with the MP. Default or cached platform configuration information will be used. Data field contains the error return value from the PDHC.
Cause / Action: Cause: Hardware problem with the MP or PDHC. Action: Contact HP Support to confirm the manageability subsystem is functioning properly. Cause: PDHC, MP, and/or PDC firmware are not compatible. Action: Upgrade PDHC, MP, and/or PDC firmware to supported and compatible revisions.
Automated Recovery: None
Event Generation Threshold: 1 occurrence

Event 2264

Severity: MAJOR
Event Summary: Error occurred accessing a PDC data structure
Event Class: System
Problem Description:
Error occurred accessing a PDC data structure. The cell will be halted. Error occurred while deconfiguring a CPU. The data field contains the physical location of the CPU.
Cause / Action:
Cause: Hardware problem with the PDH riser card. Action: Contact HP Support to confirm the PDH riser card is functioning properly. Cause: Hardware problem with the CPU or cell board. Action: Contact HP Support to confirm the CPUs and cell board are functioning properly.
Automated Recovery: None
Event Generation Threshold: 1 occurrence

Event 2265

Severity: MAJOR
Event Summary: PDC detected an illegal CPU number passed to an internal function
Event Class: System
Problem Description:
An invalid CPU number was passed into an internal PDC function. The cell will be halted. That data field contains the physical location of the cell being halted.
Cause / Action:
Cause: Hardware failure with CPU, CC or cell board. Action: Contact HP Support to confirm the CPUs, CC, and cell board are functioning properly. Update PDC if a version is available to fix this problem.
Automated Recovery: None
Event Generation Threshold: 1 occurrence

Event 2266

Severity: MAJOR
Event Summary: Cell board has a CPU with an unsupported CPU revision
Event Class: System
Problem Description:
PDC found a CPU on the cell board which has an unsupported CPU revision. The cell will be halted. The data field reports the physical location of the cell.
Cause / Action: Cause: PDC found a CPU with an unsupported CPU revision Action: Contact HP Support to confirm the cell board is functioning properly, install supported CPUs, or upgrade PDC to a version that supports the installed CPUs.
Automated Recovery: None
Event Generation Threshold: 1 occurrence

Event 2267

Severity: MAJOR
Event Summary: PDC and the manageability subsystem interface revisions do not match
Event Class: System
Problem Description:
PDC and the manageability subsystem interface revisions do not match. The cell will be halted. The data contents have the format: 0x5500PPGG5000ppgg where: PP = Utilities' PDHC/PDC revision number GG = Utilities' MP/PDC revision number pp = PDC's PDHC/PDC revision number gg = PDC's MP/PDC revision number
Cause / Action: Cause: Incorrect PDC and/or PDHC firmware installed. Action: Install compatible versions of PDC and/or PDHC firmware. Cause: Hardware problem with the PDH riser card. Action: Contact HP Support to confirm the PDH riser card is functioning properly.
Automated Recovery: None
Event Generation Threshold: 1 occurrence

Event 2268

Severity: MAJOR
Event Summary: PDC received an error from the PDHC while trying to communicate with the MP
Event Class: System
Problem Description:
PDC received an error from the PDHC while trying to communicate with the MP. The cell will be halted.
Cause / Action:
Cause: Hardware problem with the MP or PDHC. Action: Contact HP Support to confirm the manageability subsystem is functioning properly. Cause: PDHC, MP, and/or PDC firmware are not compatible. Action: Upgrade PDHC, MP, and/or PDC firmware to supported and compatible revisions.
Automated Recovery: None
Event Generation Threshold: 1 occurrence

Event 2269

Severity: MAJOR
Event Summary: PDC detected an invalid complex profile change.
Event Class: System
Problem Description:
PDC detected an invalid complex profile change. The cell will be reset. Data field contains the return status from the function that encountered the error. The data field contains the partition configuration data sequence ID.
Cause / Action: Cause: An error occurred which prevented the complex profiles from being created properly. Action: Create and distribute a new complex profile using ParMgr on a functional partition in the complex. Restore the last complex profile using the "CC" command from the MP, then use ParMgr to create a new complex profile. Generate a genesis complex profile using the "CC" command from the MP, then use ParMgr to create a new complex profile. Check for an OS patch or firmware upgrade that fixes this problem. Cause: A hardware problem exists with MP or PDHC hardware. Action: Contact HP Support to confirm the MP and PDHC are functioning properly.
Automated Recovery: None
Event Generation Threshold: 1 occurrence

Event 2270

Severity: MAJOR
Event Summary: PDC detected an illegal CPU number passed to an internal function
Event Class: System
Problem Description:
An invalid CPU number was passed into an internal PDC function. Previous IPMI events may indicate why a CPU was being deconfigured. Depending upon the situation, either the cell will be halted or the entire partition will be reset. The data field contains the invalid parameter.
Cause / Action: Cause: Hardware failure with CPU, CC or cell board. Action: Contact HP Support to confirm the CPUs, CC, and cell board are functioning properly. Update PDC if a version is available to fix this problem.
Automated Recovery: None
Event Generation Threshold: 1 occurrence

Event 2271

Severity: MAJOR
Event Summary: Cell attempting rendezvous had different main backplane type than core cell
Event Class: System
Problem Description:
A cell attempting to rendezvous in a partition had a different main backplane type than the core cell. Differing cell will be reset. The data field contains the main backplane type that differed from the core cell's.
Cause / Action: Cause: Main backplanes are misconfigured. Action: Contact HP Support to confirm main backplanes are setup and functioning properly.
Automated Recovery: None
Event Generation Threshold: 1 occurrence

Event 2272

Severity: MAJOR
Event Summary: Cell attempting rendezvous has CPU HVERSION different than core cell
Event Class: System
Problem Description:
A cell attempting to rendezvous in a partition had Processor Module HVERSION that differed from the core cell's. Differing cell will be reset. The data field contains the HVERSION that differed from the core cell.
Cause / Action: Cause: Partition was created with incompatible cell boards. Action: Reassign cells into partitions with compatible cell boards. Cause: CPU or cell board is misconfigured or not functioning properly. Action: Contact HP Support to confirm the CPUs and cell boards are configured and functioning properly.
Automated Recovery: None
Event Generation Threshold: 1 occurrence

Event 2273

Severity: MAJOR
Event Summary: Cell has CPUs with different CPU speed than core cell
Event Class: System
Problem Description:
A cell attempting to rendezvous in a partition had a different CPU speed than the core cell for that partition. Differing cell will be reset. The data field contains the speed of the CPUs in the cell that differs from the core cell.
Cause / Action:
Cause: Partition was created with incompatible cell boards. Action: Reassign cells into partitions with compatible cell boards. Cause: CPU or cell board is misconfigured or not functioning properly. Action: Contact HP Support to confirm the CPUs and cell boards are configured and functioning properly.
Automated Recovery: None
Event Generation Threshold: 1 occurrence

Event 2274

Severity: MAJOR
Event Summary: A cell had a different version of PDC than the core cell.
Event Class: System
Problem Description:
A cell attempting to rendezvous in a partition had a different PDC revision than the core cell for that partition. The cell with the PDC revision differing from the core cell's will be reset. The data field contains the PDC revision of the cell that differs.
Cause / Action: Cause: Cells in a partition have different PDC revisions Action: Upgrade PDC to the same revision on all cells in the partition. Cause: Partition was created with incompatible cell boards. Action: Reassign cells into partitions with compatible cell boards.
Automated Recovery: None
Event Generation Threshold: 1 occurrence

Event 2275

Severity: MAJOR
Event Summary: Cell(s) in the dead set could not be reset.
Event Class: System
Problem Description:
Cell(s) in the dead set could not be reset by the core cell.
Cause / Action: Cause: Fabric or PDC bug Action: If intermittent problem, check fabric. If repetitive, check for PDC upgrade.
Automated Recovery: None
Event Generation Threshold: 1 occurrence

Event 2276

Severity: MAJOR
Event Summary: The scratch RAM test failed.
Event Class: System
Problem Description:
The scratch RAM test failed. This is most likely a failure in the scratch RAM and should be replaced. The cell will be halted. Data field contains the physical location of the cell with the failure.
Cause / Action: Cause: Bad scratch RAM Action: Contact HP Support personnel to troubleshoot the cell board
Automated Recovery: None
Event Generation Threshold: 1 occurrence

Event 2277

Severity: MAJOR
Event Summary: Could not read the Complex Serial number or write it to the SCSI Parms area.
Event Class: System
Problem Description:
There was an error while writing the Complex Serial Number, during the validation of the PDC NVRAM SCSI Parms area at boot time. The cell will Reset.
Cause / Action: Cause: The local Cell Global or Cell Micro semaphores were not locked. Or the target cell global semaphore was not locked. Action: Capture logs, contact HP Support Cause: Couldn't read the Complex Serial Number from the Complex Profile. Action: : Capture logs, contact HP Support Cause: Couldn't get the address of the SCSI Parms area in PDC NVRAM. Action: : Capture logs, contact HP Support
Automated Recovery: None
Event Generation Threshold: 1 occurrence

Event 2278

Severity: MAJOR
Event Summary: Could not read the SCSI Parms Layout Version.
Event Class: System
Problem Description:
Could not access the PDC NVRAM SCSI Parms area. The cell will reset!
Cause / Action: Cause: Couldn't get the address of the SCSI Parms area in PDC NVRAM. Action: Capture logs, contact HP Support
Automated Recovery: None
Event Generation Threshold: 1 occurrence

Event 2279

Severity: MAJOR
Event Summary: Could not read the SCSI Parameters Checksum.
Event Class: System
Problem Description:
Could not access the PDC NVRAM SCSI Parms area. The cell will reset!
Cause / Action: Cause: Couldn't get the address of the SCSI Parms area in PDC NVRAM. Action: Capture logs, contact HP Support Cause: Calculation of SCSI Parms checksum failed Action: Upgrade PDC, capture logs, contact HP Support.
Automated Recovery: None
Event Generation Threshold: 1 occurrence

Event 2280

Severity: MAJOR
Event Summary: Could not get access to the SCSI Parms area of PDC NVRAM.
Event Class: System
Problem Description:
During boot, the SCSI Parameters area of PDC NVRAM was found to be unavailable. The area could not be validated. The cell will Reset. Data field contains failure from function call to access SCSI Parameters area.
Cause / Action: Cause: Couldn't get the address of the SCSI Parms area in PDC NVRAM. Action: Upgrade PDC if available, capture logs, contact HP Support.
Automated Recovery: None
Event Generation Threshold: 1 occurrence

Event 2281

Severity: MAJOR
Event Summary: Clearing the SCSI Parms area of PDC NVRAM failed.
Event Class: System
Problem Description:
Could not re-initialize the SCSI Parms area of PDC NVRAM. The area has not been cleared. The cell will reset. Cause / Action:
Cause: The appropriate semaphores were not aquired. Action: Capture logs, contact HP Support Cause: Writing the Complex Serial Number failed. Possibly couldn't access the Complex Profile. Action: Capture logs, contact PDC team. Cause: The SCSI Parms checksum algorithm failed Action: Capture logs, contact PDC team. Cause: Couldn't get the address to the SCSI NVM area. Action: Capture logs, contact HP Support
Automated Recovery: None
Event Generation Threshold: 1 occurrence

Event 2282

Severity: MAJOR
Event Summary: There was a failure while getting or releasing a semaphore.
Event Class: System
Problem Description:
The SCSI Parms proc needs 4 different semaphores: the Cell Local Semaphore, Local Cell's Global Semaphore, Target Cell's Global Semaphore, Micro Semaphore. This chassis code indicates that an unknown error occurred while either getting or releasing one of the semaphores.
Cause / Action: Cause: Error accessing a semaphore Action: Capture chassis logs. Document events that led up to the error. Contact HP Support.
Automated Recovery: None
Event Generation Threshold: 1 occurrence

Event 2283

Severity: MAJOR
Event Summary: The Cell Global Semaphore was not locked.
Event Class: System
Problem Description:
Bootstrap did not own the Cell Global Semaphore when it verified that the SCSI parms area has been initialized. The cell will reset.
Cause / Action: Cause: Could not obtain the Micro Semaphore Action: Reset. If that does not resolve issue capture Logs, contact HP Support
Automated Recovery: None
Event Generation Threshold: 1 occurrence

Event 2284

Severity: MAJOR
Event Summary: Could not release the Micro Semaphore afert initializing the SCSI Parms area.
Event Class: System
Problem Description:
Could not release the Micro Semaphore after initializing the SCSI Parms area.
Cause / Action: Cause: The semaphore is owned by another entity Action: Reset Cause: PDC bug Action: Capture logs, contact HP Support
Automated Recovery: None
Event Generation Threshold: 1 occurrence

Event 2285

Severity: FATAL
Event Summary: PDC tried to tell a slave cell monarch CPU to do something and failed.
Event Class: System
Problem Description:
The core cell send a command to the slave cells and failed.
Cause / Action: Cause: The core cell could not communicate with the slave cells. There is an intermittent problem with the fabric. Action: Check the fabric for intermittent problems.
Automated Recovery: None
Event Generation Threshold: 1 occurrence

Event 2286

Severity: MAJOR
Event Summary: Halting cell because this code shouldn't execute before monarch selection.
Event Class: System
Problem Description:
There is a per-cell flag that indicates whether or not the deconfig bytes are valid in an internal PDC data structure. The code that sets this flag should therefore be called once per boot. PDC expects the monarch CPU to be the only CPU that executes this code. This chassis log indicates that a monarch has not yet been selected. This is a PDC bug.
Cause / Action: Cause: PDC bug. Action: Contact HP Support
Automated Recovery: None
Event Generation Threshold: 1 occurrence

Event 2287

Severity: MAJOR
Event Summary: Halting cell because PDC failed a read-after-write check to a Dillon register.
Event Class: System
Problem Description:
While trying to set a flag in a cell board register to indicate that the deconfig bytes are now valid in the CELL_CPU_STATE structure, PDC failed on the read-after-write to that register. Data field contains the value PDC expected to read from the register (i.e., the value just written to it).
Cause / Action:
Cause: Hardware problem with the cell board, but could be that CC or the CPU corrupted the write or read. Action: Contact HP Support personnel to troubleshoot the cell board.
Automated Recovery: None
Event Generation Threshold: 1 occurrence

Event 2288

Severity: MAJOR
Event Summary: PDC could not set the time of day on the RTC.
Event Class: System
Problem Description:
PDC could not set the time of day on the RTC. Data field contains the status returned from the attempt to set the TOD.
Cause / Action: Cause: Semaphore problem. Action: Contact HP Support personnel to troubleshoot cell board or to check for PDC upgrade if possible software problem
Automated Recovery: None
Event Generation Threshold: 1 occurrence

Event 2289

Severity: FATAL
Event Summary: The core cell could not read the cell state of a slave cell.
Event Class: System
Problem Description:
The core cell could not read the cell state of a slave cell. The core cell is waiting for the monarch CPU on all of the slave cells to change their cell state to indicate that the slave cell has entered the slave cell rendezvous after the core cell is selected. Data field contains the physical location of the slave cell that could not be read.
Cause / Action: Cause: There is an intermittent problem with the fabric. Action: Look for problems in the fabric.
Automated Recovery: None
Event Generation Threshold: 1 occurrence

Event 2290

Severity: FATAL
Event Summary: Slave cell picked a different core cell than the one that wrote to it
Event Class: System
Problem Description:
The slave cells wait for the core cell to write its cell number to their micro general-purpose register 1. When the slaves see that the core cell has written its cell number to this register, it compares the core cell number in the micro general-purpose register 1 with the core cell that was selected by the slave cell. If the core cells don't match, then the slave cell knows that there is a split-brain problem where the cells did not rendezvous properly. Data Field: The core cell that wrote its number to this cell's micro general-purpose register 1.
Cause / Action:
Cause: There is a split brain problem. Action: Look for fabric problems. Contact HP support if this can't be resolved
Automated Recovery: None
Event Generation Threshold: 1 occurrence

Event 2291

Severity: MAJOR
Event Summary: Slave CPU has noticed the monarch CPU has failed and will deconfig it
Event Class: System
Problem Description:
A slave CPU has noticed that the monarch CPU has failed and will deconfigure it. The cell will be reset.
Cause / Action:
Cause: The monarch CPU has failed. A slave CPU has noticed this and will deconfigure the monarch CPU and reset the cell. Action: Contact HP Support personnel to troubleshoot the CPU/cell board.
Automated Recovery: None
Event Generation Threshold: 1 occurrence

Event 2292

Severity: MAJOR
Event Summary: Write to the Speedy Boot Data Structure Failed
Event Class: System
Problem Description:
Write to the Speedy Boot Data Structure Failed. The most likely reason for this failure is that a remote cell could not be reached. Data field contains the physical location of the cell that could not be written.
Cause / Action: Cause: Fabric problem. CC is defective Action: Contact HP Support personnel to troubleshoot fabric connections or the cell board
Automated Recovery: None
Event Generation Threshold: 1 occurrence

Event 2293

Severity: MAJOR
Event Summary: Halting cell because operating mode should be available by this point.
Event Class: System
Problem Description:
During boot, PDC sends a command to the Utilities to get "platform configuration info", which includes the operating mode. This chassis log is sent if the command to the Utilities completed in error and PDC doesn't have valid cached values.
Cause / Action: Cause: PDH memory problem or other cell problem in which the values previously cached were corrupted. Action: Contact HP Support personnel to troubleshoot the cell board. Cause: PDC has a bug in which it didn't write the cached values and validate them correctly or it read the cached value incorrectly. Action: Upgrade PDC if newer PDC is known to have fixed such a problem.
Automated Recovery: None
Event Generation Threshold: 1 occurrence

Event 2294

Severity: MAJOR
Event Summary: Halting cell because PDC couldn't write the cached operating mode.
Event Class: System
Problem Description:
The Utilities system tells PDC what the operating mode is (Mfg or Normal), among other things, and PDC then writes this value to a data structure in NVM to cache it. This chassis log is sent if PDC can't write the mode to the data structure. After writing the cached value, PDC does a read-after-write check. Cell will hard halt if it experiences this failure.
Cause / Action: Cause: Hardware problem like PDH memory or corrupted reads and writes. Action: Contact HP Support personnel to troubleshoot the cell board.
Automated Recovery: None
Event Generation Threshold: 1 occurrence

Event 2295

Severity: FATAL
Event Summary: PDC could not synchronize the cells' RTCs with the core cell's RTC
Event Class: System
Problem Description:
PDC synchronizes all of the Real Time Clocks (RTCs) on each cell in the PD with the core cell's RTC. If this fails, this chassis code is sent before the PD is reset.
Cause / Action:
Cause: Look for either of the following chassis codes and their cause action statements: CC_BOOT_READ_TOD_FAILED CC_BOOT_SET_TOD_FAILED These chassis codes will contain status information indicating why reading the core cell's RTC or setting the slave cells' RTCs failed. Action: -
Automated Recovery: None
Event Generation Threshold: 1 occurrence

Event 2296

Severity: MAJOR
Event Summary: Cell left another cell behind and it missed the partition rendezvous
Event Class: System
Problem Description:
Before trying to rendezvous with the other cells assigned to the PD, a cell will check to make sure that none of the other cells in the partition have left this cell behind. Data Field: The first cell that this cell noticed had left this cell behind
Cause / Action:
Cause: This cell did not boot quickly enough to rendezvous with the other cells in the PD. Action: Try to figure out why the cell that sent this chassis code booted so late. See if the cell was powered up much later than the other cells in the PD. Look for chassis codes that indicate that the cell found a problem. See if the other cell whose physical location is in the data field of this chassis code is hung. Try resetting all of the cells in the partition using the GSP commands so that the partition is reset almost simultaneously.
Automated Recovery: None
Event Generation Threshold: 1 occurrence

Event 2297

Severity: FATAL
Event Summary: Other cells in partition did not create local rendezvous set in time
Event Class: System
Problem Description:
PDC creates a rendezvous set that consists of all of the cells that can communicate bilaterally. Each cell has to do this at the same time. If some of the cells do not create their local rendezvous set and make it available to the other cells in time for them to make their rendezvous set, the cells that are waiting will timeout and send this chassis code. The data field of the chassis code contains the cells that delivered their local rendezvous set in time. The data field is a bitmap of cells where cell 0 is the least significant bit and cell 63 is the most significant bit. A one on a cell's bit indicates that the cell delivered its local rendezvous set in time.
Cause / Action: Cause: Some of the cells in the partition did not deliver their local rendezvous set in time. Action: Look at the data field of the chassis code. Find the cells that are configured to be in the PD that did not deliver their rendezvous set in time and look for problems in those cells
Automated Recovery: None
Event Generation Threshold: 1 occurrence

Event 2298

Severity: FATAL
Event Summary: A cell was unable to access data on the core cell.
Event Class: System
Problem Description:
PDC could not access data in the core cell's data structure. This chassis code is probably a result of a failed attempt to walk the fabric to the core cell.
Cause / Action: Cause: There was an intermittent problem in the fabric and a slave cell could not reach the core cell. Action: Look for problems in the fabric. Try rebooting the partition.
Automated Recovery: None
Event Generation Threshold: 1 occurrence

Event 2299

Severity: MAJOR
Event Summary: Received an unexpected interrupt during boot
Event Class: System
Problem Description:
Received an unexpected interrupt during boot. The cell or partition will be reset. Data Field: The interrupt number of the unexpected interrupt. 1-HPMC 2-Power Failure Interrupt 3-Recovery Counter Trap 4-External Interrupt 5-LPMC 6-Instruction TLB Miss Fault / Instruction Page Fault 7-Instruction Memory Protection Trap 8-Illegal Instruction Trap 9-Break Instruction Trap 10-Privileged Operation Trap 11-Privileged Register Trap 12-Overflow Trap 13-Conditional Trap 14-Assist Exception Trap 15-Data TLB Miss Fault / Data Page Fault 16-Non-Access Instruction TLB Miss Fault 17-Non-Access Data TLB Miss Fault / Non-Access Data Page Fault 18-Data Memory Protection Trap / Unaligned Data Reference Trap 19-Data Memory Break Trap 20-TLB Dirty Bit Trap 21-Page Reference Trap 22-Assist Emulation Trap 23-Higher Privilege Transfer Trap 24-Lower Privilege Transfer Trap 25 Taken Branch Trap 26-Data Memory Access Rights Trap 27-Data Memory Protection ID Trap 28-Unaligned Data Reference Trap 29-Performance Monitor Interrupt
Cause / Action: Cause: Received an unexpected interrupt during boot. The data field contains the interrupt number of the unexpected interrupt. Action: Actions taken will be dependent on the interrupt class and previous chassis codes. If the cause of the interrupt can not be determined from the previous chassis code, contact HP Support for assistance.
Automated Recovery: None
Event Generation Threshold: 1 occurrence

Event 2300

Severity: MAJOR
Event Summary: PDC read a cell state that it did not recognize on another cell.
Event Class: System
Problem Description:
PDC read a cell state that it did not recognize on another cell. Data field contains the unknown cell state. Cell will reset for reconfiguration.
Cause / Action: Cause: Bad cell hardware or fabric Action: Contact HP Support personnel to troubleshoot problem
Automated Recovery: None
Event Generation Threshold: 1 occurrence

Event 2301

Severity: FATAL
Event Summary: Data obtained from a core cell data structure was unintelligible.
Event Class: System
Problem Description:
Data obtained from a core cell data structure was unintelligible. Data field contains the data PDC could not interpret.
Cause / Action: Cause: PDC read invalid data from an internal data structure Action: Contact HP Support
Automated Recovery: None
Event Generation Threshold: 1 occurrence

Event 2302

Severity: FATAL
Event Summary: Slave cells timed out before reaching correct cell state.
Event Class: System
Problem Description:
Core Cell detected that slave cell(s) did not reach correct cell state within allocated time. Data field contains bit mask of cells present.
Cause / Action: Cause: Cell hung Action: Root cause cell hang - investigate previous chassis codes from the hung cell(s). Contact HP support for help troubleshooting the cell. Boot without cells that experienced failure, either through powering them off and rebooting and waiting for the partition to detect them as missing or through reconfiguring the complex profile not to include the failing cell(s). The latter option is faster.
Automated Recovery: None
Event Generation Threshold: 1 occurrence

Event 2303

Severity: MAJOR
Event Summary: A cell is about to be halted.
Event Class: System
Problem Description:
Whenever PDC halts a cell, this IPMI event will be sent with the physical location of the cell in the data field. One or more preceding IPMI events should indicate what has gone wrong and why the cell is being halted.
Cause / Action: Cause: Refer to preceding IPMI events for cause/action. Action: -
Automated Recovery: None
Event Generation Threshold: 1 occurrence

Event 2304

Severity: FATAL
Event Summary: No cell rendezvoused in the partition can be the core cell
Event Class: System
Problem Description:
No cell rendezvoused in the partition can be the core cell. The data field contains the physical location of the cell reporting the problem.
Cause / Action: Cause: No cell has core IO. There is an IO problem with cell(s) that does have core IO Action: Configure the partition to include cell with core IO. Check IO and IO connections (REO cables)
Automated Recovery: None
Event Generation Threshold: 1 occurrence

Event 2305

Severity: MAJOR
Event Summary: End of 10 minute waiting period for other cells to rendezvous.
Event Class: System
Problem Description:
Cells are done waiting the 10 minute period for other cells to rendezvous.
Cause / Action: Cause: Cells did not power on at same time and/or have different amounts of IO, memory, etc that affect booting time. A cell had a problem that caused it to halt or reset for reconfiguration and wait forever at SINC_BIB. Action: Do nothing, continue booting without cells that did not make rendezvous. Reboot partition. Make sure all configured cells are powered on and reset at approximately the same time. Investigate problem on that cell via its chassis logs.
Automated Recovery: None
Event Generation Threshold: 1 occurrence

Event 2306

Severity: MAJOR
Event Summary: Unknown I/O failure
Event Class: System
Problem Description:
Data is platform dependent. It might not mean anything. Indicates firmware issue.
Cause / Action: Cause: Fatal error on the IO of this cell. IO is not operational. Action: Contact HP Support.
Automated Recovery: None
Event Generation Threshold: 1 occurrence

Event 2307

Severity: MAJOR
Event Summary: (HWE) I/O cable error
Event Class: System
Problem Description:
Indicates that an I/O Cable is present on the cell, but that there is an error. Data is the status returned by the I/O cable, and can be decoded for more information on the failure.
Cause / Action:
Cause: Problem with I/O Cable or connector. I/O connected to the cell will not be initialized. Action: Reseat cable. Reseat I/O backplane or chassis. Reseat Cell. Replace I/O Cable. Replace I/O backplane or chassis. Replace System Backplane. Replace Cell.
Automated Recovery: None
Event Generation Threshold: 1 occurrence

Event 2308

Severity: MAJOR
Event Summary: (HWE) Failed to initailize the errors subsystem
Event Class: System
Problem Description:
Error subsystem is not operational. IO discovery cannot progress. IO will not be operational on this cell.
Cause / Action:
Cause: Insufficient room in SRAM SRAM access errors Action: Replace PDH riser.
Automated Recovery: None
Event Generation Threshold: 1 occurrence

Event 2309

Severity: MAJOR
Event Summary: (HWE) Failed to send reset to I/O subsystem
Event Class: System
Problem Description:
We could not reset IO subsystem. IO is not available on this cell.
Cause / Action: Cause: Bad I/O cable. Action: Check/replace I/O cable. Check/replace I/O chassis.
Automated Recovery: None
Event Generation Threshold: 1 occurrence

Event 2310

Severity: MAJOR
Event Summary: (HWE) I/O cable could not initialize
Event Class: System
Problem Description:
I/O link could not be initialized for use. I/O for the cell will not be functional.
Cause / Action: Cause: Bad hardware Action: Replace I/O cable. Replace I/O chassis.
Automated Recovery: None
Event Generation Threshold: 1 occurrence

Event 2311

Severity: MAJOR
Event Summary: (HWE) Failed to init rope units in SBA
Event Class: System
Problem Description:
All I/O rope units failed initialization. I/O for this cell will not be functional.
Cause / Action: Cause: Rope units in the SBA could not be initialized. Bad hardware. Action: Check for other failures. Replace I/O chassis
Automated Recovery: None
Event Generation Threshold: 1 occurrence

Event 2312

Severity: MAJOR
Event Summary: (HWE) Multiple failed in LBAs and Ropes, not enough IO to continue
Event Class: System
Problem Description:
All ropes or LBAs have failed initialization. I/O for this cell will not be functional.
Cause / Action:
Cause: Bad hardware. Action: Check for other failures. Replace I/O chassis.
Automated Recovery: None
Event Generation Threshold: 1 occurrence

Event 2313

Severity: MAJOR
Event Summary: (HWE) Failed to init PCI busses
Event Class: System
Problem Description:
PCI bus initailization failed.
Cause / Action:
Cause: All busses on the cell are deconfigured due to failures. IO on this cell will be non-functional. Action: Check for other errors. Replace I/O cards.
Automated Recovery: None
Event Generation Threshold: 1 occurrence

Event 2314

Severity: MAJOR
Event Summary: (HWE) Failed to map SBA to MMIO
Event Class: System
Problem Description:
See Summary.
Cause / Action:
Cause: Could not map SBA into MMIO. IO is not operational on this cell. Bad hardware. Action: Check for additional failures. Replace I/O chassis
Automated Recovery: None
Event Generation Threshold: 1 occurrence

Event 2315

Severity: MAJOR
Event Summary: (HWE) Failed to map LBAs to MMIO
Event Class: System
Problem Description:
See Summary
Cause / Action: Cause: We could not map the LBAs into MMIO. This might mean that IO is not functional on this cell. Probably caused by a hardware failure. Action: Check system for other errors. If no other errors, replace I/O chassis.
Automated Recovery: None
Event Generation Threshold: 1 occurrence

Event 2316

Severity: MAJOR
Event Summary: (Medium weight error) RIN block in CC had errors (might be correctable)
Event Class: System
Problem Description:
See Summary. Data is the value of the RIN primary error register.
Cause / Action: Cause: RIN block has a bit set. If it is a recoverable error logged during the opening of the link, the error will be cleared and initialization will continue. Otherwise, the link will be deconfigured, and I/O will not be initialized. May be caused by I/O cable issues. Action: If I/O configuration fails, check RI cable connections. If problem persists, replace RI cable. If problem still persists, replace HW in the following order: I/O chassis, Cell, System Back Plane.
Automated Recovery: None
Event Generation Threshold: 1 occurrence

Event 2317

Severity: MAJOR
Event Summary: (MWE) ROUT block in CC had errors (might be correctable)
Event Class: System
Problem Description:
See summary. The data will be the value of the ROUT primary error log.
Cause / Action: Cause: ROUT has an error set. If the error is correctable, it will be cleared and configuration will continue. If the error is not correctable, the I/O link will be deconfigured, and any I/O for this cell will be unreachable. May be caused by I/O cable problems. Action: If I/O configuration fails: Check RI cables. Reseat RI cable. If problem persists: Replace RI cable. If