Event 200
Event Details:
- Severity: MAJOR_WARNING
- Event Summary: Bad OS MCA checksum
- Event Class: System
- Problem Description:
The OS has registered an OS_MCA vector, but it has not passed the checksum- Cause / Action:
Cause: OS has registered a bad OS_MCA vector or the data has been lost. Action: Reboot system to allow vector to be re-registered.- Automated Recovery: None
- Event Generation Threshold: 1 occurrence
Examples:
Event 201
Event Details:
- Severity: MAJOR_WARNING
- Event Summary: BMC interface to IPMI failed
- Event Class: System
- Problem Description:
The BMC has failed testing and has been disabled.- Cause / Action:
Cause: BMC firmware has locked up or the BMC is disabled. Action: Cycle system power and attempt boot again. If error re-occurs contact your HP representative for support.- Automated Recovery: None
- Event Generation Threshold: 1 occurrence
Examples:
Event 203
Event Details:
- Severity: CRITICAL
- Event Summary: Boot cell launch EFI failure
- Event Class: System
- Problem Description:
SFW failed to launch EFI- Cause / Action:
Cause: The system has failed to launch EFI because of an internal error.- Automated Recovery: None
- Event Generation Threshold: 1 occurrence
Examples:
Event 204
Event Details:
- Severity: MAJOR_WARNING
- Event Summary: Monarch selection failure
- Event Class: System
- Problem Description:
0x11 = Calibration Failure 0x22 = Select Code Failure- Cause / Action:
Cause: An internal error has caused monarch selection to fail. Action: Reboot system, swap processors if failure persists.- Automated Recovery: None
- Event Generation Threshold: 1 occurrence
Examples:
Event 205
Event Details:
- Severity: MAJOR_WARNING
- Event Summary: CPU monarch collision
- Event Class: System
- Problem Description:
Monarch Collision has occurred- Cause / Action:
Cause: Unexpected error has occurred during monarch selection. Action: Reboot, if problem persists contact your HP representative for support.- Automated Recovery: None
- Event Generation Threshold: 1 occurrence
Examples:
Event 207
Event Details:
- Severity: CRITICAL
- Event Summary: Boot cell virtualize EFI failure
- Event Class: System
- Problem Description:
SFW attempted to virtualize EFI and failed- Cause / Action:
Cause: An internal error has occurred that prevented EFI from virtualizing. Action: Reboot, if problem persists contact your HP representative for support.- Automated Recovery: None
- Event Generation Threshold: 1 occurrence
Examples:
Event 208
Event Details:
- Severity: CRITICAL
- Event Summary: Boot cell virtualize PAL failure
- Event Class: System
- Problem Description:
SFW was unable to virtualize PAL- Cause / Action:
Cause: SFW was unable to virtualize PAL. Action: Reboot, if problem persists contact your HP representative for support.- Automated Recovery: None
- Event Generation Threshold: 1 occurrence
Examples:
Event 209
Event Details:
- Severity: CRITICAL
- Event Summary: Boot cell virtualize SAL failure
- Event Class: System
- Problem Description:
SFW was unable to virtualize SAL- Cause / Action:
Cause: SFW was unable to virtualize SAL. Action: Reboot, if problem persists contact your HP representative for support.- Automated Recovery: None
- Event Generation Threshold: 1 occurrence
Examples:
Event 210
Event Details:
- Severity: CRITICAL
- Event Summary: Boot cell virtualize SALPROC failure
- Event Class: System
- Problem Description:
SFW was unable to virtualize SALPROC- Cause / Action:
Cause: SFW was unable to virtualize SALPROC. Action: Reboot, if problem persists contact your HP representative for support.- Automated Recovery: None
- Event Generation Threshold: 1 occurrence
Examples:
Event 211
Event Details:
- Severity: MAJOR_WARNING
- Event Summary: CPU struct init failed
- Event Class: System
- Problem Description:
SFW has failed initializing the CPU Struct.- Cause / Action:
Cause: A CPU has failed the configuration process. Action: Replace CPU. If problem persists contact your HP representative for support.- Automated Recovery: None
- Event Generation Threshold: 1 occurrence
Examples:
Event 212
Event Details:
- Severity: MAJOR_WARNING
- Event Summary: CPU failed early config
- Event Class: System
- Problem Description:
A CPU has failed early config.- Cause / Action:
Cause: A CPU has failed the early configuration process. Action: Replace CPU. If problem persists contact your HP representative for support.- Automated Recovery: None
- Event Generation Threshold: 1 occurrence
Examples:
Event 213
Event Details:
- Severity: MAJOR_WARNING
- Event Summary: CPU failed early selftest
- Event Class: System
- Problem Description:
A CPU has failed early self test. Data: PAL Test State.- Cause / Action:
Cause: A CPU has failed early self test. Action: Replace CPU. If problem persists contact your HP representative for support.- Automated Recovery: None
- Event Generation Threshold: 1 occurrence
Examples:
Event 214
Event Details:
- Severity: MAJOR_WARNING
- Event Summary: CPU failed
- Event Class: System
- Problem Description:
SFW has detected that a CPU has failed. Data: the local cpu number that failed.- Cause / Action:
Cause: A CPU has failed. Action: Replace CPU. If problem persists contact your HP representative for support.- Automated Recovery: None
- Event Generation Threshold: 1 occurrence
Examples:
Event 215
Event Details:
- Severity: MAJOR_WARNING
- Event Summary: CPU failed late selftest
- Event Class: System
- Problem Description:
SFW has determined a CPU or Memory has failed late test. This could be related to a CPU error or a Correctable Single Bit Memory error. See Cause/Action.- Cause / Action:
Cause 1: A Correctable Single Bit Memory error has caused CPU late self test to fail. It is possible the CPU is not faulty in this case. Action 1: Look for the event "MEM_CORR_ERR" from the last time the system was running. If you find these events, replace that DIMM(s) before replacing the CPU's. Replace DIMMs with excessive "MEM_CORR_ERR" first. If after replacing all suspect DIMMs this event is still seen, replace the CPU. Cause2: A CPU has failed. Action2: Replace CPU. If problem persists contact your HP representative for support.- Automated Recovery: None
- Event Generation Threshold: 1 occurrence
Examples:
Event 216
Event Details:
- Severity: MAJOR_WARNING
- Event Summary: CPU not enough late test memory
- Event Class: System
- Problem Description:
The CPU late test has failed because of insufficient memory- Cause / Action:
Cause: Insufficient memory Action: Increase memory and reboot.- Automated Recovery: None
- Event Generation Threshold: 1 occurrence
Examples:
Event 217
Event Details:
- Severity: CRITICAL
- Event Summary: Could not allocate memory for EFI image
- Event Class: System
- Problem Description:
Could not allocate memory for EFI image- Cause / Action:
Cause: SFW could not allocate enough memory for EFI image. Action: Replace/Add memory.- Automated Recovery: None
- Event Generation Threshold: 1 occurrence
Examples:
Event 218
Event Details:
- Severity: CRITICAL
- Event Summary: EFI image corrupted
- Event Class: System
- Problem Description:
EFI image is corrupted- Cause / Action:
Cause: EFI image is corrupted. Action: Reflash ROM if applicable, if problem persists contact your HP representative for support.- Automated Recovery: None
- Event Generation Threshold: 1 occurrence
Examples:
Event 219
Event Details:
- Severity: CRITICAL
- Event Summary: EFI not in fit table
- Event Class: System
- Problem Description:
EFI fit error- Cause / Action:
Cause: EFI image is not in FIT. Action: Reflash ROM if applicable, if problem persists contact your HP representative for support.- Automated Recovery: None
- Event Generation Threshold: 1 occurrence
Examples:
Event 220
Event Details:
- Severity: CRITICAL
- Event Summary: NVRAM test fail
- Event Class: System
- Problem Description:
EFI NVM has failed testing. The cell will now halt.- Cause / Action:
Cause: NVM is corrupted or bad. Action: Clear NVM, if problem persists contact your HP representative for support.- Automated Recovery: None
- Event Generation Threshold: 1 occurrence
Examples:
Event 221
Event Details:
- Severity: CRITICAL
- Event Summary: EFI Rom size bad
- Event Class: System
- Problem Description:
EFI Image Error- Cause / Action:
Cause: EFI image is corrupt. Action: Reflash ROM if applicable, if problem persists contact your HP representative for support.- Automated Recovery: None
- Event Generation Threshold: 1 occurrence
Examples:
Event 222
Event Details:
- Severity: CRITICAL
- Event Summary: EFI Rom checksum error
- Event Class: System
- Problem Description:
EFI Image Error.- Cause / Action:
Cause: EFI image is corrupt. Action: Reflash ROM if applicable, if problem persists contact your HP representative for support.- Automated Recovery: None
- Event Generation Threshold: 1 occurrence
Examples:
Event 223
Event Details:
- Severity: CRITICAL
- Event Summary: External interruption nest limit exceeded
- Event Class: System
- Problem Description:
The IVT interrupting nesting depth has been exceeded. This processor will be halted Data: Number of the offending vector- Cause / Action:
Cause: Internal FW error.- Automated Recovery: None
- Event Generation Threshold: 1 occurrence
Examples:
Event 224
Event Details:
- Severity: CRITICAL
- Event Summary: External interrupt not serviced
- Event Class: System
- Problem Description:
An external interrupt has been requested and not serviced. Data: Number of the vector- Cause / Action:
Cause: Internal FW error.- Automated Recovery: None
- Event Generation Threshold: 1 occurrence
Examples:
Event 225
Event Details:
- Severity: CRITICAL
- Event Summary: Ext int taken
- Event Class: System
- Problem Description:
An external interrupt has been taken. Data: Number of the vector taken.- Cause / Action:
Cause: An external interrupt has been taken Action: None- Automated Recovery: None
- Event Generation Threshold: 1 occurrence
Examples:
Event 226
Event Details:
- Severity: MAJOR_WARNING
- Event Summary: Forward Progress Log (FPL) access failed
- Event Class: System
- Problem Description:
Access to the FPL has failed.- Cause / Action:
Cause: FPL access has failed.- Automated Recovery: None
- Event Generation Threshold: 1 occurrence
Examples:
Event 227
Event Details:
- Severity: CRITICAL
- Event Summary: PSR fetch failure
- Event Class: System
- Problem Description:
SFW was unable to read the CPU PSR. Data: Local CPU number- Cause / Action:
Cause: SFW was unable to read the CPU PSR. Action: Replace CPU.- Automated Recovery: None
- Event Generation Threshold: 1 occurrence
Examples:
Event 228
Event Details:
- Severity: CRITICAL
- Event Summary: Cell halt
- Event Class: System
- Problem Description:
SFW has halted the cell- Cause / Action:
Cause: Internal Error Action: contact your HP representative for support.- Automated Recovery: None
- Event Generation Threshold: 1 occurrence
Examples:
Event 229
Event Details:
- Severity: MAJOR_WARNING
- Event Summary: CPU PAL incompatible with cpu
- Event Class: System
- Problem Description:
SFW has determined that PAL is not compatible with the current processors.- Cause / Action:
Cause: Incompatible PAL. Action: Update PAL or change processors- Automated Recovery: None
- Event Generation Threshold: 1 occurrence
Examples:
Event 230
Event Details:
- Severity: MAJOR_WARNING
- Event Summary: Slave is incompatible with monarch
- Event Class: System
- Problem Description:
SFW has determined that a slave processor is incompatible with the monarch. Data: Physical location of the incompatible processor.- Cause / Action:
Cause: Incompatible processors. Action: Replace processors.- Automated Recovery: None
- Event Generation Threshold: 1 occurrence
Examples:
Event 231
Event Details:
- Severity: MAJOR_WARNING
- Event Summary: Interrupt clear failure
- Event Class: System
- Problem Description:
Interrupt clear failed during cell config- Cause / Action:
Cause: Interrupt clear failed. Action: Reboot, if problem persists contact your HP representative for support.- Automated Recovery: None
- Event Generation Threshold: 1 occurrence
Examples:
Event 232
Event Details:
- Severity: MAJOR_WARNING
- Event Summary: System Event Log (SEL) access failed
- Event Class: System
- Problem Description:
SFW has determined that an IPMI event failed.- Cause / Action:
Cause: An IPMI event has failed. Action: None- Automated Recovery: None
- Event Generation Threshold: 1 occurrence
Examples:
Event 233
Event Details:
- Severity: CRITICAL
- Event Summary: Trap taken
- Event Class: System
- Problem Description:
Data: IVT Offset- Cause / Action:
Cause: This will follow other events indicating some type of IVT error. Action: This event is for debugging the address, other events will determine the user action.- Automated Recovery: None
- Event Generation Threshold: 1 occurrence
Examples:
Event 234
Event Details:
- Severity: MAJOR_WARNING
- Event Summary: LDB State bad on entry
- Event Class: System
- Problem Description:
LDB state bad- Cause / Action:
Action: None required.- Automated Recovery: None
- Event Generation Threshold: 1 occurrence
Examples:
Event 235
Event Details:
- Severity: CRITICAL
- Event Summary: Interrupt with ic bit clear
- Event Class: System
- Problem Description:
Interrupt context was lost Data: interrupt number.- Cause / Action:
Cause: Interrupt context was lost. Action: none- Automated Recovery: None
- Event Generation Threshold: 1 occurrence
Examples:
Event 236
Event Details:
- Severity: CRITICAL
- Event Summary: Min-state registration failure
- Event Class: System
- Problem Description:
Registering of the processor min state save area with PAL has failed.- Cause / Action:
Cause: Registering of the processor min state save area with PAL has failed. Action: Replace processor, if problem persists contact your HP representative for support.- Automated Recovery: None
- Event Generation Threshold: 1 occurrence
Examples:
Event 237
Event Details:
- Severity: MAJOR_WARNING
- Event Summary: CPU mismatched boot type
- Event Class: System
- Problem Description:
An invalid boot type has been requested.- Cause / Action:
Cause: An internal error has occurred. Action: None- Automated Recovery: None
- Event Generation Threshold: 1 occurrence
Examples:
Event 238
Event Details:
- Severity: MAJOR_WARNING
- Event Summary: Boot monarch timed out
- Event Class: System
- Problem Description:
SFW has determined the monarch has timed out Data: Local CPU Number- Cause / Action:
Cause: The monarch has timed out. Action: None, Replace CPU if problem persists, system will reboot after this event.- Automated Recovery: None
- Event Generation Threshold: 1 occurrence
Examples:
Event 239
Event Details:
- Severity: CRITICAL
- Event Summary: PAL_B not in FIT table
- Event Class: System
- Problem Description:
A PAL_B FIT error has occurred- Cause / Action:
Cause: Internal Error or ROM is corrupted. Action: Reflash ROM if applicable, if problem persists contact your HP representative for support.- Automated Recovery: None
- Event Generation Threshold: 1 occurrence
Examples:
Event 240
Event Details:
- Severity: CRITICAL
- Event Summary: SAL_B not in FIT table
- Event Class: System
- Problem Description:
A SAL_B FIT error has occurred- Cause / Action:
Cause: Internal Error or ROM is corrupted. Action: Reflash ROM if applicable, if problem persists contact your HP representative for support.- Automated Recovery: None
- Event Generation Threshold: 1 occurrence
Examples:
Event 241
Event Details:
- Severity: CRITICAL
- Event Summary: NVRAM test fail
- Event Class: System
- Problem Description:
NVM has failed test. The system will halt- Cause / Action:
Cause: NVM is corrupt or bad. Action: Reboot, if problem persists contact your HP representative for support.- Automated Recovery: None
- Event Generation Threshold: 1 occurrence
Examples:
Event 242
Event Details:
- Severity: CRITICAL
- Event Summary: Interrupt vector out of range
- Event Class: System
- Problem Description:
A interrupt vector has been requested out of the acceptible range. Data: Vector Number.- Cause / Action:
Cause: An internal error has occurred- Automated Recovery: None
- Event Generation Threshold: 1 occurrence
Examples:
Event 243
Event Details:
- Severity: CRITICAL
- Event Summary: Pal proc error getting pal copy info
- Event Class: System
- Problem Description:
The PAL Copy Info call has failed- Cause / Action:
Cause: An internal error has occurred.- Automated Recovery: None
- Event Generation Threshold: 1 occurrence
Examples:
Event 244
Event Details:
- Severity: CRITICAL
- Event Summary: Pal proc error copying pal to memory
- Event Class: System
- Problem Description:
Error coping PAL to memory- Cause / Action:
Cause: There has been an error copying PAL to memory. Action: Reboot, if problem persists contact your HP representative for support.- Automated Recovery: None
- Event Generation Threshold: 1 occurrence
Examples:
Event 245
Event Details:
- Severity: MAJOR_WARNING
- Event Summary: Boot pal proc failure
- Event Class: System
- Problem Description:
A PAL Proc has failed. This will halt the processor. Data: Local CPU Number- Cause / Action:
Cause: Internal PAL Error. Action: Reboot, if problem persists contact your HP representative for support.- Automated Recovery: None
- Event Generation Threshold: 1 occurrence
Examples:
Event 246
Event Details:
- Severity: MAJOR_WARNING
- Event Summary: Console device failure
- Event Class: System
- Problem Description:
A console device has failed. Data: Physical Addr of device that failed.- Cause / Action:
Cause: A console device has failed. Action: Reset console device/system.- Automated Recovery: None
- Event Generation Threshold: 1 occurrence
Examples:
Event 247
Event Details:
- Severity: MAJOR_WARNING
- Event Summary: Platform interface device failure
- Event Class: System
- Problem Description:
A console device has failed. Data: Physical Addr of device that failed.- Cause / Action:
Cause: A console device has failed. Action: Reset console device/system.- Automated Recovery: None
- Event Generation Threshold: 1 occurrence
Examples:
Event 248
Event Details:
- Severity: MAJOR_WARNING
- Event Summary: platform scratch RAM test failed
- Event Class: System
- Problem Description:
Platfrom Scratch RAM has failed the test.- Cause / Action:
Cause: Bad or corrupt Scratch RAM. Action: Reboot, if problem persists contact your HP representative for support.- Automated Recovery: None
- Event Generation Threshold: 1 occurrence
Examples:
Event 249
Event Details:
- Severity: MAJOR_WARNING
- Event Summary: CPU rendezvous failure
- Event Class: System
- Problem Description:
A CPU has failed to meeet rendezvous. Data: Local CPU Number- Cause / Action:
Cause: Bad or slow CPU. Action: Replace CPU.- Automated Recovery: None
- Event Generation Threshold: 1 occurrence
Examples:
Event 250
Event Details:
- Severity: CRITICAL
- Event Summary: Error extracting sal_b from rom
- Event Class: System
- Problem Description:
SFW could not extract SAL_B from the ROM- Cause / Action:
Cause: ROM Corrupt or unreadable. Action: Reflash ROM if applicable, if problem persists contact your HP representative for support.- Automated Recovery: None
- Event Generation Threshold: 1 occurrence
Examples:
Event 251
Event Details:
- Severity: CRITICAL
- Event Summary: Scratch RAM bad
- Event Class: System
- Problem Description:
Platform Scratch RAM has failed test.- Cause / Action:
Cause: Bad or corrupt Scratch RAM. Action: Reboot, if problem persists contact your HP representative for support.- Automated Recovery: None
- Event Generation Threshold: 1 occurrence
Examples:
Event 252
Event Details:
- Severity: MAJOR_WARNING
- Event Summary: IPMI System Event Log (SEL) is full
- Event Class: System
- Problem Description:
IPMI SEL full- Cause / Action:
Cause: IPMI SEL full. Action: Clear SEL through BMC or MP.- Automated Recovery: None
- Event Generation Threshold: 1 occurrence
Examples:
Event 253
Event Details:
- Severity: MAJOR_WARNING
- Event Summary: Slave wakeup before vector registered
- Event Class: System
- Problem Description:
No wakeup vector registered for processor Data: Local CPU Number- Cause / Action:
Cause: No wakeup vector registered for processor. Action: Reboot, if problem persists contact your HP representative for support.- Automated Recovery: None
- Event Generation Threshold: 1 occurrence
Examples:
Event 254
Event Details:
- Severity: MAJOR_WARNING
- Event Summary: CPU failed rendezvous handler
- Event Class: System
- Problem Description:
Slave Rendezvous handler has failed. Data: Local CPU Number.- Cause / Action:
Cause: Internal Error. Action: Reboot, if problem persists contact your HP representative for support.- Automated Recovery: None
- Event Generation Threshold: 1 occurrence
Examples:
Event 255
Event Details:
- Severity: CRITICAL
- Event Summary: Error building SMBIOS Tables
- Event Class: System
- Problem Description:
SFW failed to build the SMBIOS tables- Cause / Action:
Cause: SFW failed to build the SMBIOS tables. Action: None, if SMBIOS is preventing functionality, reboot. If problem persists contact your HP representative for support.- Automated Recovery: None
- Event Generation Threshold: 1 occurrence
Examples:
Event 256
Event Details:
- Severity: CRITICAL
- Event Summary: Trap nest limit exceeded
- Event Class: System
- Problem Description:
The trap nesting limit has been exceeded. Data: Vector Number- Cause / Action:
Cause: The trap nesting limit has been exceeded. Action: Reboot if necessary, if problem persists contact your HP representative for support.- Automated Recovery: None
- Event Generation Threshold: 1 occurrence
Examples:
Event 257
Event Details:
- Severity: CRITICAL
- Event Summary: Trap not serviced
- Event Class: System
- Problem Description:
A trap has been requested and not serviced. Data: Vector Number- Cause / Action:
Cause: A invalid trap has been requested or a trap has not been installed. Action: Reboot if necessary, if problem persists contact your HP representative for support.- Automated Recovery: None
- Event Generation Threshold: 1 occurrence
Examples:
Event 258
Event Details:
- Severity: CRITICAL
- Event Summary: Trap taken
- Event Class: System
- Problem Description:
A trap has been taken. Data: Number of the vector taken.- Cause / Action:
Cause: A trap has been taken Action: None- Automated Recovery: None
- Event Generation Threshold: 1 occurrence
Examples:
Event 259
Event Details:
- Severity: MAJOR_WARNING
- Event Summary: Uncleared interrupt
- Event Class: System
- Problem Description:
At least one interrupt was not cleared. Data: The highest pending interrupt number- Cause / Action:
Cause: At least one interrupt was not cleared. Action: None.- Automated Recovery: None
- Event Generation Threshold: 1 occurrence
Examples:
Event 260
Event Details:
- Severity: CRITICAL
- Event Summary: Unexpected external interrupt
- Event Class: System
- Problem Description:
An unexpected external interrupt has occurred. Data: External Interrupt Number- Cause / Action:
Cause: An unexpected external interrupt has occurred. Action: None.- Automated Recovery: None
- Event Generation Threshold: 1 occurrence
Examples:
Event 261
Event Details:
- Severity: CRITICAL
- Event Summary: Interrupt before redirection table set up
- Event Class: System
- Problem Description:
An interrupt has occurred before setting up the IVT. Data: Interrupt Number- Cause / Action:
Cause: An interrupt has occurred before setting up the IVT. Action: None.- Automated Recovery: None
- Event Generation Threshold: 1 occurrence
Examples:
Event 262
Event Details:
- Severity: CRITICAL
- Event Summary: CPU unexpected MCA
- Event Class: System
- Problem Description:
An unexpected MCA has occurred before MCA's are unmasked. Data: Local CPU Number.- Cause / Action:
Cause: Unexpected MCA Action: None- Automated Recovery: None
- Event Generation Threshold: 1 occurrence
Examples:
Event 263
Event Details:
- Severity: CRITICAL
- Event Summary: Unexpected trap
- Event Class: System
- Problem Description:
An unexpected trap has occurred. The trap number is either invalid or the requested trap has not been registered. Data: Trap Number- Cause / Action:
Cause: An unexpected trap has occurred. During System Firmware boot time this indicates the system has requested a trap that firmware has not registered. During OS run time it indicates the system has requested a trap that is not recognized in the OS's trap table. Action: If at OS run time, verify that the OS has properly installed its trap handler, and that only valid traps are caused. Investigate what could cause the trap that is signaled by the event or why the OS has not properly installed the trap handler.- Automated Recovery: None
- Event Generation Threshold: 1 occurrence
Examples:
Event 264
Event Details:
- Severity: CRITICAL
- Event Summary: CPU unknown boot error
- Event Class: System
- Problem Description:
SFW has detected an unknown error.- Cause / Action:
Cause: unknown error. Action: None, if problem persists contact your HP representative for support.- Automated Recovery: None
- Event Generation Threshold: 1 occurrence
Examples:
Event 265
Event Details:
- Severity: MAJOR_WARNING
- Event Summary: CC errors PAL failure
- Event Class: System
- Problem Description:
SFW has detected a PAL Failure- Cause / Action:
Cause: SFW has detected a PAL Failure. Action: Reboot if necessary, if problem persists contact your HP representative for support.- Automated Recovery: None
- Event Generation Threshold: 1 occurrence
Examples:
Event 266
Event Details:
- Severity: MAJOR_WARNING
- Event Summary: Expected MC vector unregistered
- Event Class: System
- Problem Description:
Expected Machine Check Vector not registered- Cause / Action:
Cause: Expected Machine Check Vector not registered at the time of an Expected Machine Check- Automated Recovery: None
- Event Generation Threshold: 1 occurrence
Examples:
Event 267
Event Details:
- Severity: CRITICAL
- Event Summary: INIT initiated
- Event Class: System
- Problem Description:
This is the equivalent of a TOC event in the PA RISC Architecture. On IPF systems, this event is called an INIT. This event can be triggered by the "tc" command from the MP, or from the button labeled "TOC" :wor "Transfer of Control" on the Management card or bezel of the system. There are also other causes of an INIT generated by software. Data: Local CPU Number- Cause / Action:
Cause: Software has requested an INIT or the INIT button has been pressed. Action: None- Automated Recovery: None
- Event Generation Threshold: 1 occurrence
Examples:
Event 268
Event Details:
- Severity: MAJOR_WARNING
- Event Summary: Expected I/O host bridge is missing
- Event Class: System
- Problem Description:
An I/O host bridge is missing. Firmware will continue boot and display the following EFI warning, "Unexpected hardware I/O configuration." Data Field: Physical location of the missing I/O host bridge.- Cause / Action:
Cause: I/O host bridge failure. An incorrect I/O backplane is installed. Action: Contact your HP representative to check the I/O host bridge and the I/O backplane.- Automated Recovery: None
- Event Generation Threshold: 1 occurrence
Examples:
Event 269
Event Details:
- Severity: MAJOR_WARNING
- Event Summary: LBA has unexpected number of I/O slots
- Event Class: System
- Problem Description:
Firmware detected an unexpected number of I/O slots connected to an I/O host bridge. Firmware display the following EFI warning message, "Unexpected hardware I/O configuration." Data Field: Physical location of the I/O host bridge.- Cause / Action:
Cause: The firmware needs to be updated. An incorrect I/O backplane is installed. Action: Contact your HP representative to check the firmware and the I/O backplane.- Automated Recovery: None
- Event Generation Threshold: 1 occurrence
Examples:
Event 270
Event Details:
- Severity: MAJOR_WARNING
- Event Summary: I/O rope width does not match expected value
- Event Class: System
- Problem Description:
Firmware found an I/O controller rope of unexpected width. Firmware will configure the I/O host bridge connected to the rope and display the following EFI warning message, "Unexpected hardware I/O configuration." Data Field: Physical location of the I/O host bridge connected to the rope.- Cause / Action:
Cause: The firmware needs to be updated. An incorrect I/O backplane is installed. Action: Contact your HP representative to check the firmware and the I/O backplane.- Automated Recovery: None
- Event Generation Threshold: 1 occurrence
Examples:
Event 271
Event Details:
- Severity: MAJOR_WARNING
- Event Summary: Found unexpected I/O host bridge
- Event Class: System
- Problem Description:
Firmware found an unexpected I/O host bridge. Firmware will configure the I/O host bridge and display the following EFI warning message, "Unexpected hardware I/O configuration." Data Field: Physical location of the unexpected I/O host bridge.- Cause / Action:
Cause: The firmware needs to be updated. An incorrect I/O backplane is installed. Action: Contact your HP representative to check the firmware and the I/O backplane.- Automated Recovery: None
- Event Generation Threshold: 1 occurrence
Examples:
Event 272
Event Details:
- Severity: MAJOR_WARNING
- Event Summary: PCI clock DLL error
- Event Class: System
- Problem Description:
An I/O host bridge's bus frequency DLL circuit failed. Firmware will deconfigure the failed I/O host bridge and display the following EFI warning message, "Failed I/O slot(s) deconfigured." Data Field: Physical location of the I/O host bridge.- Cause / Action:
Cause: Failed or improperly inserted I/O card. Action: Remove or reseat the I/O card. Cause: Failed I/O chipset. Failed I/O backplane. Action: Contact your HP representative to check the I/O chipset and backplane.- Automated Recovery: None
- Event Generation Threshold: 1 occurrence
Examples:
Event 273
Event Details:
- Severity: MAJOR_WARNING
- Event Summary: PCI hot plug controller failed
- Event Class: System
- Problem Description:
An I/O host bridge's hot-plug controller has failed. Firmware will deconfigure the I/O host bridge and display the following EFI warning message, "Failed I/O slot(s) deconfigured." Data Field: Physical location of the I/O hostbridge.- Cause / Action:
Cause: Hot-plug controller failure. I/O host bridge failure. Action: Contact your HP representative to check the hot-plug controller and the I/O host bridge.- Automated Recovery: None
- Event Generation Threshold: 1 occurrence
Examples:
Event 274
Event Details:
- Severity: MAJOR_WARNING
- Event Summary: Found unknown I/O rope width
- Event Class: System
- Problem Description:
Firmware attempts to configure an I/O controller rope to an unsupported width. Firmware will deconfigure any I/O host bridge connected to the rope. Data Field: Physical location of the failed rope.- Cause / Action:
Cause: Internal firmware error. Action: Contact your HP representative to check the firmware.- Automated Recovery: None
- Event Generation Threshold: 1 occurrence
Examples:
Event 275
Event Details:
- Severity: MAJOR_WARNING
- Event Summary: I/O LBA clear error failed
- Event Class: System
- Problem Description:
During I/O host bridge configuration, firmware found a persistent error condition. Firmware will deconfigure the I/O host bridge and display the following EFI warning message, "Failed I/O slot(s) deconfigured." Data Field: Physical location of the I/O hostbridge.- Cause / Action:
Cause: A failed or improperly seated I/O card is present. Action: Replace or reseat the I/O card(s). Cause: I/O host bridge failure. Action: Contact your HP representative to check the I/O host bridge.- Automated Recovery: None
- Event Generation Threshold: 1 occurrence
Examples:
Event 276
Event Details:
- Severity: MAJOR_WARNING
- Event Summary: I/O host bridge inaccessible because rope reset failed to complete
- Event Class: System
- Problem Description:
An I/O host bridge is inaccessible because an I/O controller rope reset failed to complete. Firmware will deconfigure the I/O host bridge and display the following EFI warning message, "Failed I/O slot(s) deconfigured." Data Field: Physical location of the I/O host bridge.- Cause / Action:
Cause: I/O chipset failure. Action: Contact your HP representative to check the I/O chipset.- Automated Recovery: None
- Event Generation Threshold: 1 occurrence
Examples:
Event 277
Event Details:
- Severity: MAJOR_WARNING
- Event Summary: Insufficient power to turn on PCI slot
- Event Class: System
- Problem Description:
There is insufficient power. Firmware will not power on a hot-plug I/O slot. In addition, firmware will display the following EFI warning message, "Failed I/O slot(s) deconfigured." Date Field: Physical location of the I/O slot.- Cause / Action:
Cause: The power budget is exceeded. Action: Install an additional power supply on the system.- Automated Recovery: None
- Event Generation Threshold: 1 occurrence
Examples:
Event 278
Event Details:
- Severity: MAJOR_WARNING
- Event Summary: PCI bus walk unknown error
- Event Class: System
- Problem Description:
Firmware encountered an unexpected error while attempting to configure an I/O host bridge's I/O devices. Firmware will continue boot but will not configure the I/O devices connected to the specified I/O host bridge. Such I/O devices will not be usable as console nor boot devices but might be usable by the O/S. Data Field: Physical location of the I/O host bridge.- Cause / Action:
Cause: Internal firmware error. Action: Contact your HP representative to check the firmware.- Automated Recovery: None
- Event Generation Threshold: 1 occurrence
Examples:
Event 279
Event Details:
- Severity: MAJOR_WARNING
- Event Summary: PCI bus walk resources exceeded
- Event Class: System
- Problem Description:
The total resource requirement from the I/O devices connected to an I/O host bridge exceeds the resource limit of the I/O host bridge. Firmware will continue boot but will not configure the I/O devices connected to the specified I/O host bridge. In addition, firmware will display the following EFI warning message, "Insufficient resources to assign to one or more I/O devices." Such I/O devices will not be usable as console nor boot devices but might be usable by the O/S. Data Field: Physical location of the I/O host bridge.- Cause / Action:
Cause: Unsupported I/O configuration. Action: Remove any unsupported I/O cards. Move the I/O card to another slot.- Automated Recovery: None
- Event Generation Threshold: 1 occurrence
Examples:
Event 280
Event Details:
- Severity: MAJOR_WARNING
- Event Summary: PCI bus unmap unknown error
- Event Class: System
- Problem Description:
Firmware encountered an unexpected error while attempting to clear resource allocations on an I/O host bridge's I/O devices. Data Field: Physical location of the I/O host bridge.- Cause / Action:
Cause: Internal firmware error. Action: Contact your HP representative to check the firmware.- Automated Recovery: None
- Event Generation Threshold: 1 occurrence
Examples:
Event 281
Event Details:
- Severity: MAJOR_WARNING
- Event Summary: PCIXCAP sampling error
- Event Class: System
- Problem Description:
An I/O host bridge failed to determine the appropriate PCI[X] mode and frequency (PCI, PCI-X 66 MHz, PCI-X 133 MHz, etc.) for its bus. Firmware will deconfigure the I/O host bridge and display the following EFI warning message, "Failed I/O slot(s) deconfigured." Data Field: Physical location of the failed I/O host bridge.- Cause / Action:
Cause: I/O host bridge failure. Action: Contact your HP representative to check the I/O host bridge.- Automated Recovery: None
- Event Generation Threshold: 1 occurrence
Examples:
Event 282
Event Details:
- Severity: MAJOR_WARNING
- Event Summary: Power monitor failed to respond
- Event Class: System
- Problem Description:
Firmware is unable to access the power monitor. Firmware will assume that there is sufficient power and proceed to power on an I/O slot. Data Field: Physical location of the I/O slot.- Cause / Action:
Cause: BMC failure. Action: Contact your HP representative to check the BMC.- Automated Recovery: None
- Event Generation Threshold: 1 occurrence
Examples:
Event 283
Event Details:
- Severity: MAJOR_WARNING
- Event Summary: I/O rope reset failed to complete
- Event Class: System
- Problem Description:
An I/O controller rope reset did not complete within the expected time limit. Firmware will deconfigure the I/O host bridge attached to the rope. Data Field: Physical location of the deconfigured I/O host bridge.- Cause / Action:
Cause: I/O chipset failure. Action: Contact your HP representative to check the I/O controller.- Automated Recovery: None
- Event Generation Threshold: 1 occurrence
Examples:
Event 284
Event Details:
- Severity: MAJOR_WARNING
- Event Summary: I/O SBA clear error failed
- Event Class: System
- Problem Description:
During I/O chipset configuration, firmware found a persistent error condition. Firmware will attempt to continue the boot. Data Field: Physical location of the I/O chipset.- Cause / Action:
Cause: I/O chipset failure. Action: Contact your HP representative to check the I/O chipset.- Automated Recovery: None
- Event Generation Threshold: 1 occurrence
Examples:
Event 285
Event Details:
- Severity: MAJOR_WARNING
- Event Summary: PCI slot has incorrect default power state
- Event Class: System
- Problem Description:
During boot, firmware has found a hot-plug I/O slot with an incorrect default power state. The slot power should be off by default. Data Field: Physical location of the I/O slot.- Cause / Action:
Cause: A non-compliant PCI[X] card is inserted in the slot. Such cards leaks power to the PCI[X] bus, which violates the PCI Bus Specification. Action: Replace the card with a compliant card. Cause: The hot-plug controller has failed. Action: Contact your HP representative to check the hot-plug slot.- Automated Recovery: None
- Event Generation Threshold: 1 occurrence
Examples:
Event 286
Event Details:
- Severity: MAJOR_WARNING
- Event Summary: PCI slot power on error
- Event Class: System
- Problem Description:
Firmware encountered an error while attempting to power on an I/O slot. Firmware will deconfigure the I/O slot and display the following EFI warning message, "Failed I/O slot(s) deconfigured." Data Field: Physical location of the I/O slot.- Cause / Action:
Cause: The I/O card is damaged or improperly inserted. Action: Replace or reseat the I/O card. Cause: The hot-plug controller has failed. Action: Contact your HP representative to check the hot-plug slot.- Automated Recovery: None
- Event Generation Threshold: 1 occurrence
Examples:
Event 287
Event Details:
- Severity: MAJOR_WARNING
- Event Summary: PCI slot's standby power failed
- Event Class: System
- Problem Description:
An I/O slot's standby (Vaux) power has failed. Firmware will deconfigure the I/O slot and display the following EFI warning message, "Failed I/O slot(s) deconfigured." Data Field: Physical location of the failed I/O slot.- Cause / Action:
Cause: I/O slot failure. Action: Contact your HP representative to check the I/O slot.- Automated Recovery: None
- Event Generation Threshold: 1 occurrence
Examples:
Event 288
Event Details:
- Severity: MAJOR_WARNING
- Event Summary: Found invalid PCIXCAP value
- Event Class: System
- Problem Description:
An I/O host bridge or hot-plug controller reported an illegal PCI[X] bus mode for its bus or slot, respectively. Firmware will deconfigure the I/O host bridge or I/O slot and display the following EFI warning, "Failed I/O slot(s) deconfigured." Data Field: Physical location of the failed I/O host bridge or the failed I/O slot.- Cause / Action:
Cause: The I/O card is damaged or improperly inserted. Action: Replace or reseat the I/O card. Cause: I/O host bridge failure. Hot-plug controller failure. Action: Contact your HP representative to check the I/O host bridge or the hot-plug controller.- Automated Recovery: None
- Event Generation Threshold: 1 occurrence
Examples:
Event 289
Event Details:
- Severity: MAJOR_WARNING
- Event Summary: Unsupported rope frequency
- Event Class: System
- Problem Description:
Firmware attempted to configure an I/O controller rope to an unsupported frequency. Firmware will deconfigure any I/O host bridge connected to the rope and display the following EFI warning message, "Failed I/O slot(s) deconfigured." Data Field: Physical location of the failed rope.- Cause / Action:
Cause: Internal firmware error. Action: Contact your HP representative to check the firmware.- Automated Recovery: None
- Event Generation Threshold: 1 occurrence
Examples:
Event 290
Event Details:
- Severity: MAJOR_WARNING
- Event Summary: Unsupported host bridge type
- Event Class: System
- Problem Description:
Firmware has found an unsupported I/O host bridge type. Firmware will deconfigure the I/O host bridge and display the following EFI warning message, "Failed I/O slot(s) deconfigured." Data Field: Physical location of the I/O host bridge.- Cause / Action:
Cause: Firmware needs to be updated. An incorrect I/O backplane is installed. Action: Contact your HP representative to check the firmware and the I/O backplane.- Automated Recovery: None
- Event Generation Threshold: 1 occurrence
Examples:
Event 291
Event Details:
- Severity: CRITICAL
- Event Summary: MC during INIT
- Event Class: System
- Problem Description:
Not Used- Cause / Action:
Not Used- Automated Recovery: None
- Event Generation Threshold: 1 occurrence
Examples:
Event 292
Event Details:
- Severity: CRITICAL
- Event Summary: Machine Check initiated
- Event Class: System
- Problem Description:
A Machine Check has been initiated- Cause / Action:
Cause: A Machine Check has occurred. Action: Analyze cause of Machine Check using diag's and EFI tools.- Automated Recovery: None
- Event Generation Threshold: 1 occurrence
Examples:
Event 293
Event Details:
- Severity: CRITICAL
- Event Summary: Error in temporary mdt area
- Event Class: System
- Problem Description:
There has been a problem building the MDT table.- Cause / Action:
Cause: MDT table bad. Action: Reboot if necessary, if problem persists contact your HP representative for support.- Automated Recovery: None
- Event Generation Threshold: 1 occurrence
Examples:
Event 294
Event Details:
- Severity: CRITICAL
- Event Summary: Failed to find lmmio entry in mdt
- Event Class: System
- Problem Description:
There has been a problem building the MDT.- Cause / Action:
Cause: MDT table bad. Action: Reboot if necessary, if problem persists contact your HP representative for support.- Automated Recovery: None
- Event Generation Threshold: 1 occurrence
Examples:
Event 295
Event Details:
- Severity: CRITICAL
- Event Summary: Memory page zero bad
- Event Class: System
- Problem Description:
Memory page 0 was slated for deallocation in the PDT. EFI cannot launch with page 0 bad, so the system will halt.- Cause / Action:
C: Memory page 0 was slated for deallocation in the PDT. A: FW is written such that this event should never be generated. If the user sees this event, please contact HP support.- Automated Recovery: None
- Event Generation Threshold: 1 occurrence
Examples:
Event 296
Event Details:
- Severity: CRITICAL
- Event Summary: Failed to find space in mdt
- Event Class: System
- Problem Description:
There has been a problem building the MDT.- Cause / Action:
Cause: MDT table bad. Action: Reboot if necessary, if problem persists contact your HP representative for support.- Automated Recovery: None
- Event Generation Threshold: 1 occurrence
Examples:
Event 297
Event Details:
- Severity: MAJOR_WARNING
- Event Summary: Media failure: info was not retrieved/logged
- Event Class: System
- Problem Description:
There has been a media failure.- Cause / Action:
Cause: The Error handler has failed to retrieve or log data due to a media failure. Action: Reboot if necessary, if problem persists contact your HP representative for support.- Automated Recovery: None
- Event Generation Threshold: 1 occurrence
Examples:
Event 298
Event Details:
- Severity: MAJOR_WARNING
- Event Summary: Bus interface register test failed
- Event Class: System
- Problem Description:
Indicates that the chipset register test has failed. The data field contains the physical address of the failing register.- Cause / Action:
C: The chipset failed the register test. A: Contact HP support to troubleshoot the problem.- Automated Recovery: None
- Event Generation Threshold: 1 occurrence
Examples:
Event 299
Event Details:
- Severity: MAJOR_WARNING
- Event Summary: Memory ECC normal write/read test failed
- Event Class: System
- Problem Description:
After FW's first access to main memory, FW detected that the CEC logged an error after reading back what was just written.- Cause / Action:
C: The DIMM that maps to cache line 0 is in a chipspare condition A: Contact HP support C: The DIMM that maps to address 0 is not seated properly A: Check all of the DIMMs in the system and make sure that they are inserted fully into the slot with the retention mechanism in place C: System may be running at the wrong frequency. A: Verify the system bus frequency and the memory bus frequency.- Automated Recovery: None
- Event Generation Threshold: 1 occurrence
Examples:
Event 300
Event Details:
- Severity: MAJOR_WARNING
- Event Summary: DIMM loading order error: DIMM deallocated
- Event Class: System
- Problem Description:
A DIMM that is required to be loaded in order for this DIMM to function properly is not loaded, so FW will deallocate this DIMM. Currently, none of the platforms require any DIMMs to be loaded in order for this DIMM to work properly.- Cause / Action:
C: A required DIMM is not loaded in order to allow for proper operation of the DIMM specified in the physical location. A: Refer to the user's manual for Memory loading instructions.- Automated Recovery: None
- Event Generation Threshold: 1 occurrence
Examples:
Event 301
Event Details:
- Severity: MAJOR_WARNING
- Event Summary: DIMM SPD checksum failed
- Event Class: System
- Problem Description:
The DIMM specified by the physical location has an SPD EEPROM that has a bad checksum. The Data field is the physical location of the DIMM.- Cause / Action:
C: The DIMMs SPD EEPROM got corrupted. A: Contact HP Support personnel to troubleshoot the problem- Automated Recovery: None
- Event Generation Threshold: 1 occurrence
Examples:
Event 302
Event Details:
- Severity: MAJOR_WARNING
- Event Summary: DIMM SPD fatal error
- Event Class: System
- Problem Description:
Detected a fatal error in DIMM SPD- Cause / Action:
Cause: Detection of SPD fatal error type - various types Action: Contact HP Support personnel to troubleshoot the problem- Automated Recovery: None
- Event Generation Threshold: 1 occurrence
Examples:
Event 303
Event Details:
- Severity: MAJOR_WARNING
- Event Summary: Unsupported memory DIMM type
- Event Class: System
- Problem Description:
A DIMM was installed whose DIMM type is not compatible with the current set of supported DIMMs for this platform.- Cause / Action:
Cause: A DIMM with an invalid DIMM type was found Action: Contact HP Support personnel to troubleshoot the problem- Automated Recovery: None
- Event Generation Threshold: 1 occurrence
Examples:
Event 304
Event Details:
- Severity: MAJOR_WARNING
- Event Summary: The DIMM type of this DIMM doesn't match with others in the DIMM group
- Event Class: System
- Problem Description:
The DIMM type of this DIMM is not the same as the other DIMMs in the same group. The group of DIMMs is deallocated. If this is the last active group of DIMMs in the system, the system is halted.- Cause / Action:
Cause: The DIMMs in the rank do not have the same DIMM type Action: Contact HP Support personnel to troubleshoot the problem- Automated Recovery: None
- Event Generation Threshold: 1 occurrence
Examples:
Event 305
Event Details:
- Severity: MAJOR_WARNING
- Event Summary: The DIMM type table is full. New DIMM type cannot be added.
- Event Class: System
- Problem Description:
The DIMM type table is full- Cause / Action:
C: Too many different types of DIMMs in system A: Reduce the number of different types of DIMMs in the system.
- Automated Recovery: None
- Event Generation Threshold: 1 occurrence
Examples:
Event 306
Event Details:
- Severity: MAJOR_WARNING
- Event Summary: DIMM number not found in DMT Table
- Event Class: System
- Problem Description:
An entry for the DIMM was not found in the DMT table. The data field contains the DMT entry that the caller wanted to find (in Dimm number format, which is 2 bytes, upper byte is the extender number, lower byte is the chipselect of the rank caller is looking for.)- Cause / Action:
C: Probable internal FW error A: Reload System Firmware A: Contact HP Support personnel to troubleshoot the problem- Automated Recovery: None
- Event Generation Threshold: 1 occurrence
Examples:
Event 307
Event Details:
- Severity: MAJOR_WARNING
- Event Summary: Memory ECC multiple-bit data error detection failed
- Event Class: System
- Problem Description:
The FW selftest of CEC multi-bit error (MBE) detection has failed. The upper 32 bits of the data field contain the Dword offset within the cacheline of the failed MBE detection. The lower 32 bits are split in two, and they contain the bit numbers within the Dword that were flipped in order to casue an MBE.- Cause / Action:
C: The CEC failed MBE detection. A: Contact HP support personnel to troubleshoot the problem- Automated Recovery: None
- Event Generation Threshold: 1 occurrence
Examples:
Event 308
Event Details:
- Severity: MAJOR_WARNING
- 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:
C: The CEC failed MBE detection. A: Contact HP support personnel to troubleshoot the problem- Automated Recovery: None
- Event Generation Threshold: 1 occurrence
Examples:
Event 309
Event Details:
- Severity: MAJOR_WARNING
- Event Summary: Memory ECC single-bit data error detection failed
- Event Class: System
- Problem Description:
The FW selftest of CEC single-bit error (SBE) detection has failed. The data field contains the bit within the Dword that was flipped that caused the CEC to not see an SBE.- Cause / Action:
C: The CEC failed SBE detection. A: Contact HP support personnel to troubleshoot the problem- Automated Recovery: None
- Event Generation Threshold: 1 occurrence
Examples:
Event 310
Event Details:
- Severity: MAJOR_WARNING
- Event Summary: Memory ECC single-bit ECC error detection failed
- Event Class: System
- Problem Description:
The FW selftest of CEC single-bit error (SBE) detection has failed. The data field contains the bit within the Dword that was flipped that caused the CEC to not see an SBE.- Cause / Action:
C: The CEC failed SBE detection. A: Contact HP support personnel to troubleshoot the problem- Automated Recovery: None
- Event Generation Threshold: 1 occurrence
Examples:
Event 311
Event Details:
- Severity: MAJOR_WARNING
- Event Summary: Insufficient memory for operation
- Event Class: System
- Problem Description:
Memory FW detected errors below 1MB. FW will not allow boot in this case, so memory FW will reinterleave and retest.- Cause / Action:
C: FW detected memory errors below 1MB. A: None needed if FW recovers. If system will not boot, contact HP support to troubleshoot the problem.- Automated Recovery: None
- Event Generation Threshold: 1 occurrence
Examples:
Event 312
Event Details:
- Severity: MAJOR_WARNING
- Event Summary: Memory address not found in MBAT
- Event Class: System
- Problem Description:
Memory FW could not figure out which rank maps to the physical address specified in the data field maps to.- Cause / Action:
C: The address logged in the CEC doesn't map to a memory rank, possibly due to a software error or NVM corruption A: Contact HP support to trouble shoot the problem.- Automated Recovery: None
- Event Generation Threshold: 1 occurrence
Examples:
Event 313
Event Details:
- Severity: MAJOR_WARNING
- Event Summary: Memory Error Information not cleared
- Event Class: System
- Problem Description:
Memory FW was unable to clear the platform error logs on the CEC. The Datafield contains the error status of the CEC.- Cause / Action:
C: Software Error or CEC error A: Contact HP support to troubleshoot the problem- Automated Recovery: None
- Event Generation Threshold: 1 occurrence
Examples:
Event 314
Event Details:
- Severity: MAJOR_WARNING
- Event Summary: Couldn't clear memory error logs
- Event Class: System
- Problem Description:
Memory FW was unable to clear the platform error logs on the CEC. The Datafield contains the error status of the CEC.- Cause / Action:
C: Software Error or CEC error A: Contact HP support to troubleshoot the problem- Automated Recovery: None
- Event Generation Threshold: 1 occurrence
Examples:
Event 315
Event Details:
- Severity: MAJOR_WARNING
- Event Summary: Memory error clear failed
- Event Class: System
- Problem Description:
The Error registers in the CEC have failed to clear. The data field contains the error status of the CEC after the attempted clear.- Cause / Action:
C: Software error or CEC error A: Contact HP support to troubleshoot the problem- Automated Recovery: None
- Event Generation Threshold: 1 occurrence
Examples:
Event 316
Event Details:
- Severity: MAJOR_WARNING
- Event Summary: DIMM loading order error: DIMM deallocated
- Event Class: System
- Problem Description:
A DIMM that is required to be loaded in order for this DIMM to function properly is not loaded, so FW will deallocate this DIMM. Currently, none of the platforms require any DIMMs to be loaded in order for this DIMM to work properly.- Cause / Action:
C: A required DIMM is not loaded in order to allow for proper operation of the DIMM specified in the physical location. A: Refer to the user's manual for Memory loading instructions.- Automated Recovery: None
- Event Generation Threshold: 1 occurrence
Examples:
Event 317
Event Details:
- Severity: MAJOR_WARNING
- Event Summary: Generic memory firmware error
- Event Class: System
- Problem Description:
An error occurred that memory FW does not know how to handle.- Cause / Action:
C: Corrupt NVM or System firmware failure A: Contact HP support to troubleshoot the problem.- Automated Recovery: None
- Event Generation Threshold: 1 occurrence
Examples:
Event 318
Event Details:
- Severity: CRITICAL
- Event Summary: Memory interleave generation failed
- Event Class: System
- Problem Description:
FW was unable to create a memory configuration with no errors in low memory to hand off to EFI.- Cause / Action:
C1: DIMM(s) that map into low memory have errors on them. A1: Contact HP support to troubleshoot the problem. C2: SFW is outdated. A2: Update SFW.- Automated Recovery: None
- Event Generation Threshold: 1 occurrence
Examples:
Event 319
Event Details:
- Severity: MAJOR_WARNING
- Event Summary: Memory register test failed
- Event Class: System
- Problem Description:
The chipset's memory controller failed the register test. The data field contains the address of the register that failed selftest.- Cause / Action:
C1: The register within the chipset went bad. A1: Contact HP support to troubleshoot the problem C2: Internal SFW error. A2: Update to most recent SFW.- Automated Recovery: None
- Event Generation Threshold: 1 occurrence
Examples:
Event 320
Event Details:
- Severity: CRITICAL
- Event Summary: SPD found no memory DIMMs
- Event Class: System
- Problem Description:
Memory Discovery could not detect any DIMMs installed.- Cause / Action:
Cause: No DIMMs were detected Action: Install DIMMs or Contact HP Support personnel to troubleshoot the problem- Automated Recovery: None
- Event Generation Threshold: 1 occurrence
Examples:
Event 321
Event Details:
- Severity: CRITICAL
- Event Summary: No memory found
- Event Class: System
- Problem Description:
FW could not continue because there are no valid memory ranks loaded.- Cause / Action:
C: FW found memory, but it could not find a correctly loaded rank. A: Before this event is sent, FW will output which ranks it is deallocating and why. Review the preceeding events and refer to the users manual to correct the memory loading.- Automated Recovery: None
- Event Generation Threshold: 1 occurrence
Examples:
Event 322
Event Details:
- Severity: CRITICAL
- Event Summary: Cannot log memory error because PDT is disabled
- Event Class: System
- Problem Description:
The PDT has been disabled, and FW found memory errors during selftest. This is a stopboot condition. Also, the PDT will never be disabled in customer systems, so this event should never be seen in the field.- Cause / Action:
C: FW found memory errors during selftest, but could not deallocate the page because the PDT is disabled. A: Reenable the PDT by clearing NVM- Automated Recovery: None
- Event Generation Threshold: 1 occurrence
Examples:
Event 323
Event Details:
- Severity: MAJOR_WARNING
- Event Summary: PDT is disabled
- Event Class: System
- Problem Description:
An event indicating that the user has the PDT disabled on this boot. The PDT will never be disabled in customer systems, so this event should never be seen in the field.- Cause / Action:
C: Informational event indicating that FW will not use the PDT this boot. A: None if user does not want to use the PDT, otherwise, clear NVM- Automated Recovery: None
- Event Generation Threshold: 1 occurrence
Examples:
Event 324
Event Details:
- Severity: MAJOR_WARNING
- Event Summary: Error adding entry to PDT
- Event Class: System
- Problem Description:
Error writing entry into the PDT.- Cause / Action:
C: NVM write error. A: Contact HP support personnel to troubleshoot the problem.- Automated Recovery: None
- Event Generation Threshold: 1 occurrence
Examples:
Event 325
Event Details:
- Severity: SERIOUS
- Event Summary: Cannot add PDT entry--PDT full
- Event Class: System
- Problem Description:
The memory page deallocation table (PDT) is full.- Cause / Action:
C: Excessive memory errors A: Contact HP Support personnel to troubleshoot the problem- Automated Recovery: None
- Event Generation Threshold: 1 occurrence
Examples:
Event 326
Event Details:
- Severity: MAJOR_WARNING
- Event Summary: Memory platform data update failure
- Event Class: System
- Problem Description:
Memory FW was unable to save or restore the original error configuration (including CEC error log and signal enable and CPU ECC detection). This event should never be seen in the field unless there is a FW problem- Cause / Action:
C: Memory FW was unable to save or restore the original error configuration. A: If this is seen, update SFW.- Automated Recovery: None
- Event Generation Threshold: 1 occurrence
Examples:
Event 327
Event Details:
- Severity: MAJOR_WARNING
- Event Summary: Can't find memory rank entry
- Event Class: System
- Problem Description:
The rank structure that corresponds to the rankID in the data field could not be found in the Rank table. The Data field is the rankID of the structure it is looking for. This error event should never be seen.- Cause / Action:
C: The rank structure that corresponds to the rankID in the data field could not be found in the Rank table, possibly due to NVM corruption. A: Contact HP support to troubleshoot the problem.- Automated Recovery: None
- Event Generation Threshold: 1 occurrence
Examples:
Event 329
Event Details:
- Severity: MAJOR_WARNING
- Event Summary: Memory error overflow:
- Event Class: System
- Problem Description:
More than one error type was detected when only one error type was expected.- Cause / Action:
C: An error other than a memory error occurred during the memory test A: Contact HP support to troubleshoot the problem- Automated Recovery: None
- Event Generation Threshold: 1 occurrence
Examples:
Event 330
Event Details:
- Severity: MAJOR_WARNING
- Event Summary: Memory forward progress code invalid
- Event Class: System
- Problem Description:
The forward progress bits that memory FW uses to track state are invalid. The data field is the fwd progress field.- Cause / Action:
C: The forward progress bits are invalid. A: Upgrade to latest system firmware, or contact HP support to troubleshoot the problem.- Automated Recovery: None
- Event Generation Threshold: 1 occurrence
Examples:
Event 331
Event Details:
- Severity: MAJOR_WARNING
- Event Summary: Memory error status invalid
- Event Class: System
- Problem Description:
The memory error status has bits set in it that indicate another non-memory error occurred. The data field contains the chipset's error status.- Cause / Action:
C: Non-memory errors were detected during the memory test that FW doesn't know how to handle. A: Update to the latest SFW A: Contact HP support to troubleshoot the problem.- Automated Recovery: None
- Event Generation Threshold: 1 occurrence
Examples:
Event 332
Event Details:
- Severity: MAJOR_WARNING
- Event Summary: Memory error summary bits invalid
- Event Class: System
- Problem Description:
The memory test summary bits are invalid. The data field is the test summary bits.- Cause / Action:
C: The memory test summary word is invalid A: Update to the latest SFW. A: Contact HP support to troubleshoot the problem.- Automated Recovery: None
- Event Generation Threshold: 1 occurrence
Examples:
Event 333
Event Details:
- Severity: MAJOR_WARNING
- Event Summary: The DIMM distribution check was bypassed
- Event Class: System
- Problem Description:
The control bit to skip the DIMM distribution check is set and the DIMM distribution check was skipped. This bit should only be done in the factory and not in the field.- Cause / Action:
C: Control bit to skip DIMM distribution check is set. A: Clear NVM A: Update PDC A: Contact HP support to troubleshoot the problem- Automated Recovery: None
- Event Generation Threshold: 1 occurrence
Examples:
Event 334
Event Details:
- Severity: MAJOR_WARNING
- Event Summary: The DIMM Loading Order check was bypassed
- Event Class: System
- Problem Description:
The control bit to skip the DIMM loading order check is set and the DIMM loading order check was skipped. This bit should only be done in the factory and not in the field.- Cause / Action:
C: Control bit to skip DIMM loading order check is set. A: Clear NVM A: Update PDC A: Contact HP support to troubleshoot the problem- Automated Recovery: None
- Event Generation Threshold: 1 occurrence
Examples:
Event 335
Event Details:
- Severity: MAJOR_WARNING
- Event Summary: Looping on destructive memory tests
- Event Class: System
- Problem Description:
The control bit to loop on destructive memory test is set and the destructive memory tests are run continously. This bit should only be done in the factory and not in the field.- Cause / Action:
C: Control bit to loop on destructive memory test is set. A: Clear NVM A: Update PDC A: Contact HP support to troubleshoot the problem- Automated Recovery: None
- Event Generation Threshold: 1 occurrence
Examples:
Event 336
Event Details:
- Severity: MAJOR_WARNING
- Event Summary: DIMM Set Check has been skipped
- Event Class: System
- Problem Description:
The control bit to skip the DIMM set check is set and the DIMM set check was skipped. This bit should only be done in the factory and not in the field.- Cause / Action:
C: Control bit to skip DIMM set check is set. A: Clear NVM A: Update PDC A: Contact HP support to troubleshoot the problem- Automated Recovery: None
- Event Generation Threshold: 1 occurrence
Examples:
Event 337
Event Details:
- Severity: MAJOR_WARNING
- Event Summary: Serial Presence Detect (SPD) has been skipped
- Event Class: System
- Problem Description:
The control bit to skip the DIMM SPD check is set and the checking of the DIMM SPD was skipped. This bit should only be done in the factory and not in the field.- Cause / Action:
C: Control bit to skip DIMM SPD check is set. A: Clear NVM A: Update PDC A: Contact HP support to troubleshoot the problem- Automated Recovery: None
- Event Generation Threshold: 1 occurrence
Examples:
Event 338
Event Details:
- Severity: MAJOR_WARNING
- Event Summary: An Alternate Memory Config has been loaded into the system
- Event Class: System
- Problem Description:
The control bit to load an alternate memory configuration is set and an alternate memory configuration has been loaded. This bit should only be set in the factory and not in the field.- Cause / Action:
C: Control bit to use an alternate memory config are set. A: Clear NVM A: Update PDC A: Contact HP support to troubleshoot the problem- Automated Recovery: None
- Event Generation Threshold: 1 occurrence
Examples:
Event 340
Event Details:
- Severity: MAJOR_WARNING
- Event Summary: OS INIT address not registered
- Event Class: System
- Problem Description:
The OS_INIT vector has not been registered- Cause / Action:
Cause: The OS has not registered an OS_INIT vector. Action: None, the OS has failed to register the vector or has chosen not to.- Automated Recovery: None
- Event Generation Threshold: 1 occurrence
Examples:
Event 341
Event Details:
- Severity: MAJOR_WARNING
- Event Summary: OS MCA address not registered
- Event Class: System
- Problem Description:
The OS_MCA vector has not been registered- Cause / Action:
Cause: The OS has not registered an OS_MCA vector. Action: None, the OS has failed to register the vector or has chosen not to.- Automated Recovery: None
- Event Generation Threshold: 1 occurrence
Examples:
Event 342
Event Details:
- Severity: MAJOR_WARNING
- Event Summary: OS MCA did not correct the Machine Check
- Event Class: System
- Problem Description:
An Uncorrected Machine Check has occurred- Cause / Action:
Cause: Uncorrected Machine Check. Action: Analyze cause of Machine Check using diagnostic and EFI tools.- Automated Recovery: None
- Event Generation Threshold: 1 occurrence
Examples:
Event 343
Event Details:
- Severity: CRITICAL
- Event Summary: Found bad miscellaneous register
- Event Class: System
- Problem Description:
A PDH register has failed.- Cause / Action:
Cause: A PDH register has failed. Action: Reboot if necessary, if problem persists contact your HP representative for support.- Automated Recovery: None
- Event Generation Threshold: 1 occurrence
Examples:
Event 344
Event Details:
- Severity: MAJOR_WARNING
- Event Summary: SAL_CHECK failed for an unknown reason
- Event Class: System
- Problem Description:
The handler for SAL_CHECK has failed for an 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
Examples:
Event 345
Event Details:
- Severity: MAJOR_WARNING
- Event Summary: SAL_INIT failed for an unknown reason
- Event Class: System
- Problem Description:
The handler for SAL_INIT has failed for an 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
Examples:
Event 346
Event Details:
- Severity: MAJOR_WARNING
- Event Summary: Unspecified memory interleave error
- Event Class: System
- Problem Description:
Indicates that FW encountered a Fatal interleaving error. The data field contains the return status from the interleaving procedure call.- Cause / Action:
C: FW encountered a fatal interleaving error. A: Update SFW A: Contact HP support to troubleshoot the problem
- Automated Recovery: None
- Event Generation Threshold: 1 occurrence
Examples:
Event 347
Event Details:
- Severity: MAJOR_WARNING
- Event Summary: Unexpected return to SAL_CHECK
- Event Class: System
- Problem Description:
SAL_CHECK has been unexpectedly returned to.- Cause / Action:
Cause: SAL_CHECK has been unexpectedly returned to. Action: Reboot if necessary, if problem persists contact your HP representative for support.- Automated Recovery: None
- Event Generation Threshold: 1 occurrence
Examples:
Event 348
Event Details:
- Severity: MAJOR_WARNING
- Event Summary: Unexpected return to SAL_INIT
- Event Class: System
- Problem Description:
SAL_CHECK has been unexpectedly returned to.- Cause / Action:
Cause: SAL_CHECK has been unexpectedly returned to. Action: Reboot if necessary, if problem persists contact your HP representative for support.- Automated Recovery: None
- Event Generation Threshold: 1 occurrence
Examples:
Event 349
Event Details:
- Severity: SERIOUS
- 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
Examples:
Event 350
Event Details:
- Severity: SERIOUS
- Event Summary: PD rendez will fail do to a Firmware Tree error
- Event Class: System
- Problem Description:
Firmware was unable to locate a required element in the device tree and cannot create a partition. The resource that cannot be located is listed as an ansii string in the data field.- Cause / Action:
Decode the ascii string in the data field to determine what resource is missing. Examine earlier chassis codes to determine why that resouse is unavailable.- Automated Recovery: None
- Event Generation Threshold: 1 occurrence
Examples:
Event 351
Event Details:
- Severity: SERIOUS
- Event Summary: The current cell is not configured as part of the expected set
- Event Class: System
- Problem Description:
The currently executing cell is not configured to be part of the cell set it is attempting to rendezvous with.- Cause / Action:
A bad complex profile exists. Correct and redistribute.- Automated Recovery: None
- Event Generation Threshold: 1 occurrence
Examples:
Event 352
Event Details:
- Severity: SERIOUS
- Event Summary: A remote CSR could not be read
- Event Class: System
- Problem Description:
The current cell could not read a remote cells CSR. The remote cell number is displayed in the data field. These cells will not be able to rendezvous.- Cause / Action:
Either a hardware connection problem exists, or fabric was unable to be routed. Verify hardware and reset.- Automated Recovery: None
- Event Generation Threshold: 1 occurrence
Examples:
Event 353
Event Details:
- Severity: SERIOUS
- Event Summary: The current cell is too late to rendezvous with other cells
- Event Class: System
- Problem Description:
The currently executing cell arrived too late to rendezvous with the other cells described in the complex profile as cells it should rendezvous with.- Cause / Action:
This cell took to long completing previous steps to rendezvous. A bad complex profile could also cause this problem.- Automated Recovery: None
- Event Generation Threshold: 1 occurrence
Examples:
Event 354
Event Details:
- Severity: CRITICAL
- Event Summary: The current cell detected incompatible CPUs on another cell
- Event Class: System
- Problem Description:
The currently executing cell detected CPUs that are incompatible with it to be installed on a cell that the current cell is trying to rendezvous with.- Cause / Action:
Mixed CPU types are installed in the same partition. Remove them.- Automated Recovery: None
- Event Generation Threshold: 1 occurrence
Examples:
Event 355
Event Details:
- Severity: SERIOUS
- Event Summary: Current cell was too slow creating the local rendezvous set
- Event Class: System
- Problem Description:
The current cell was too slow creating the local rendezvous set and the other cells have left it behind. It will not be able to participate in the remainder of the rendezvous.- Cause / Action:
Cell too slow. Could be bad hardware. Check for other errors and reset- Automated Recovery: None
- Event Generation Threshold: 1 occurrence
Examples:
Event 356
Event Details:
- Severity: SERIOUS
- Event Summary: Reporting cell was not included in the global cell set
- Event Class: System
- Problem Description:
The reporting cell was not included in the final global set that was agreed upon. This means that another cell either could not reach the reporting cell or the reporting cell was too late ariving to a required state.- Cause / Action:
Fabric problem, Connection problem or timing problem. Reset the PD.- Automated Recovery: None
- Event Generation Threshold: 1 occurrence
Examples:
Event 357
Event Details:
- Severity: CRITICAL
- Event Summary: No Core Cell can be selected in the PD.
- Event Class: System
- Problem Description:
No cells in the PD can be a core cell. This is fatal.- Cause / Action:
No cells have a functioning core IO card. Add a core IO card to a cell in the PD and reset.- Automated Recovery: None
- Event Generation Threshold: 1 occurrence
Examples:
Event 358
Event Details:
- Severity: SERIOUS
- Event Summary: Firmware was unable to notify utilities of the core cell number
- Event Class: System
- Problem Description:
System Firmware was unable to notify utilities of the selected core cell number.- Cause / Action:
Communication with utilities is broken. Check for earlier errors or NVRAM problems.- Automated Recovery: None
- Event Generation Threshold: 1 occurrence
Examples:
Event 359
Event Details:
- Severity: SERIOUS
- Event Summary: Fabric code unable to find a needed service provider.
- Event Class: System
- Problem Description:
The fabric code is unable to find a service provider for a required banyan service.- Cause / Action:
The registry is corrupt or the ROM is incomplete.- Automated Recovery: None
- Event Generation Threshold: 1 occurrence
Examples:
Event 360
Event Details:
- Severity: SERIOUS
- Event Summary: Error in a fabric Port
- Event Class: System
- Problem Description:
The fabric port specified in the data field had an error.- Cause / Action:
Reset.- Automated Recovery: None
- Event Generation Threshold: 1 occurrence
Examples:
Event 361
Event Details:
- Severity: SERIOUS
- Event Summary: Parity error detected on read from fabric
- Event Class: System
- Problem Description:
An error occurred reading a CSR. The CSR address is displayed in the data field.- Cause / Action:
Hardware problem. Check connections and reset.- Automated Recovery: None
- Event Generation Threshold: 1 occurrence
Examples:
Event 362
Event Details:
- Severity: SERIOUS
- Event Summary: Error writing to Fabric
- Event Class: System
- Problem Description:
Error writing to Fabric. CSR data in data field.- Cause / Action:
Bad hardware.- Automated Recovery: None
- Event Generation Threshold: 1 occurrence
Examples:
Event 363
Event Details:
- Severity: CRITICAL
- Event Summary: Crossbar slices are out of rev with each other.
- Event Class: System
- Problem Description:
Incompatible crossbar slices are installed The data field is the two revisions reported by slice1 and slice0 of the CSR data.- Cause / Action:
Bad hardware configuration. Replace the crossbar.- Automated Recovery: None
- Event Generation Threshold: 1 occurrence
Examples:
Event 364
Event Details:
- Severity: CRITICAL
- Event Summary: Crossbar slices are configured poorly
- Event Class: System
- Problem Description:
Crossbar slices are in different locations. The data field is the two locations reported by slice1 and slice0 of the CSR data.- Cause / Action:
Fatal configuration. Reconfigure the hardware.- Automated Recovery: None
- Event Generation Threshold: 1 occurrence
Examples:
Event 365
Event Details:
- Severity: SERIOUS
- Event Summary: A CPU has taken over for the monarch CPU
- Event Class: System
- Problem Description:
A CPU has taken over as the monarch CPU.- Cause / Action:
The previous monarch may be suspect.- Automated Recovery: None
- Event Generation Threshold: 1 occurrence
Examples:
Event 366
Event Details:
- Severity: CRITICAL
- Event Summary: Sram cannot be used on the cell
- Event Class: System
- Problem Description:
SRAM cannot be accessed on the cell board. Execution cannot continue.- Cause / Action:
SRAM cannot be located or used on the cell board. Replace the cell board.- Automated Recovery: None
- Event Generation Threshold: 1 occurrence
Examples:
Event 367
Event Details:
- Severity: CRITICAL
- Event Summary: The dillon hardware cannot be located.
- Event Class: System
- Problem Description:
The dillon component/chip cannot be located or used.- Cause / Action:
ROM is corrupt. Replace the rom or reprogram flash.- Automated Recovery: None
- Event Generation Threshold: 1 occurrence
Examples:
Event 368
Event Details:
- Severity: SERIOUS
- Event Summary: A required piece of PDH bus hardware cannot be contacted.
- Event Class: System
- Problem Description:
A required pice of PDH bus hardware cannot be contacted.- Cause / Action:
Verify all connections of PDH bus componets or replace the cell board.- Automated Recovery: None
- Event Generation Threshold: 1 occurrence
Examples:
Event 372
Event Details:
- Severity: MAJOR_WARNING
- Event Summary: IO Link software error was corrected.
- Event Class: System
- Problem Description:
IO Link Software error was corrected.- Cause / Action:
No action required.- Automated Recovery: None
- Event Generation Threshold: 1 occurrence
Examples:
Event 373
Event Details:
- Severity: SERIOUS
- Event Summary: Bad parity data from RD Rtn FIFO on PIO Read (UNC)
- Event Class: System
- Problem Description:
Bad parity data from RD Rtn FIFO on PIO Read (UNC).- Cause / Action:
Replace bad hardware.- Automated Recovery: None
- Event Generation Threshold: 1 occurrence
Examples:
Event 374
Event Details:
- Severity: SERIOUS
- Event Summary: Parity error in Reg FIFO Internal parity error.
- Event Class: System
- Problem Description:
Parity error in Reg FIFO Internal parity error.- Cause / Action:
Replace bad hardware.- Automated Recovery: None
- Event Generation Threshold: 1 occurrence
Examples:
Event 375
Event Details:
- Severity: SERIOUS
- Event Summary: TLB Fetch timeout
- Event Class: System
- Problem Description:
TLB Fetch timeout.- Cause / Action:
Replace bad hardware.- Automated Recovery: None
- Event Generation Threshold: 1 occurrence
Examples:
Event 376
Event Details:
- Severity: CRITICAL
- Event Summary: Link presence goes away, FE
- Event Class: System
- Problem Description:
Link presence goes away, FE.- Cause / Action:
Replace the link.- Automated Recovery: None
- Event Generation Threshold: 1 occurrence
Examples:
Event 377
Event Details:
- Severity: CRITICAL
- Event Summary: LBA to SBA parity error on command, rope will go fatal
- Event Class: System
- Problem Description:
LBA to SBA parity error on command, rope will go fatal.- Cause / Action:
Bad hardware.
Repace I/O chassis.- Automated Recovery: None
- Event Generation Threshold: 1 occurrence
Examples:
Event 378
Event Details:
- Severity: CRITICAL
- Event Summary: Access to invalid TLB entry Requesting rope fatal
- Event Class: System
- Problem Description:
Access to invalid TLB entry Requesting rope fatal.- Cause / Action:
Replace bad hardware.- Automated Recovery: None
- Event Generation Threshold: 1 occurrence
Examples:
Event 379
Event Details:
- Severity: CRITICAL
- Event Summary: Memory fetch timeout
- Event Class: System
- Problem Description:
Memory Fetch Timeout.- Cause / Action:
Replace bad hardware.- Automated Recovery: None
- Event Generation Threshold: 1 occurrence
Examples:
Event 380
Event Details:
- Severity: SERIOUS
- Event Summary: Error was encountered when Initializion the LBA.
- Event Class: System
- Problem Description:
An error was encountered when initing the rope number specified in the data field.- Cause / Action:
Replace the bad hardware.- Automated Recovery: None
- Event Generation Threshold: 1 occurrence
Examples: