Home/Catalog/HPIPFTRAP-MIB

HPIPFTRAP-MIB

AI MIB Summary

Standard SNMP MIB module defining data structures for HPIPFTRAP-MIB.

1186
Objects
Active
Status
4
Dependencies

Imported Objects

Objects

1186 total
Object Name
hp
OBJECT IDENTIFIER
.1.3.6.1.4.1.11
RFC1213-MIB
Unknown
.1.3.6.1.4.1.11
nm
OBJECT IDENTIFIER
.1.3.6.1.4.1.11.2
hpnsa
OBJECT IDENTIFIER
.1.3.6.1.4.1.11.2.23
hpIpfE0Events
OBJECT IDENTIFIER
.1.3.6.1.4.1.11.2.23.35
hpevtBadOsInitChecksumThe OS has registered an OS_INIT vector, but is has not passed the checksum
TRAP-TYPE
.1.3.6.1.4.1.11.2.23.35.0.5001
hpevtBadOsMcaChecksumThe OS has registered an OS_MCA vector, but it has not passed the checksum
TRAP-TYPE
.1.3.6.1.4.1.11.2.23.35.0.5002
hpevtBootBmcFailedThe BMC has failed testing and has been disabled.
TRAP-TYPE
.1.3.6.1.4.1.11.2.23.35.0.5003
hpevtBootCellLaunchEfiFailureSFW failed to launch EFI
TRAP-TYPE
.1.3.6.1.4.1.11.2.23.35.0.5010
hpevtBootCellMonSelFailureMonarch selection has failed. Data: 0x11 = Calibration Failure 0x22 = Select Code Failure
TRAP-TYPE
.1.3.6.1.4.1.11.2.23.35.0.5011
hpevtBootCellMonarchCollisionMonarch Collision has occurred
TRAP-TYPE
.1.3.6.1.4.1.11.2.23.35.0.5013
hpevtBootCellVirtualizeEfiFailureSFW attempted to virtualize EFI and failed
TRAP-TYPE
.1.3.6.1.4.1.11.2.23.35.0.5023
hpevtBootCellVirtualizePalFailureSFW was unable to virtualize PAL
TRAP-TYPE
.1.3.6.1.4.1.11.2.23.35.0.5025
hpevtBootCellVirtualizeSalFailureSFW was unable to virtualize SAL
TRAP-TYPE
.1.3.6.1.4.1.11.2.23.35.0.5027
hpevtBootCellVirtualizeSalprocFailureSFW was unable to virtualize SALPROC
TRAP-TYPE
.1.3.6.1.4.1.11.2.23.35.0.5028
hpevtBootCpuConfigFailSFW has failed initializing the CPU Struct. Data: Physical location of CPU that produced failure
TRAP-TYPE
.1.3.6.1.4.1.11.2.23.35.0.5030
hpevtBootCpuEarlyConfigFailA CPU has failed early config.
TRAP-TYPE
.1.3.6.1.4.1.11.2.23.35.0.5031
hpevtBootCpuEarlyTestFailA CPU has failed early self test. Data: PAL Test State.
TRAP-TYPE
.1.3.6.1.4.1.11.2.23.35.0.5033
hpevtBootCpuFailedSFW has detected that a CPU has failed. Data: The Physical Location of the CPU that failed
TRAP-TYPE
.1.3.6.1.4.1.11.2.23.35.0.5034
hpevtBootCpuLateTestFailSFW 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. Data: Physical location of CPU See Cause/Action.
TRAP-TYPE
.1.3.6.1.4.1.11.2.23.35.0.5036
hpevtBootCpuLateTestInsufficientMemThe CPU late test has failed because of insufficient memory
TRAP-TYPE
.1.3.6.1.4.1.11.2.23.35.0.5037
hpevtBootEfiAllocateErrorCould not allocate memory for EFI image
TRAP-TYPE
.1.3.6.1.4.1.11.2.23.35.0.5040
hpevtBootEfiImageCorruptEFI image is corrupted
TRAP-TYPE
.1.3.6.1.4.1.11.2.23.35.0.5041
hpevtBootEfiNotInFitEFI fit error
TRAP-TYPE
.1.3.6.1.4.1.11.2.23.35.0.5042
hpevtBootEfiNvmFailEFI NVM has failed testing. The cell or system will now halt.
TRAP-TYPE
.1.3.6.1.4.1.11.2.23.35.0.5045
hpevtBootEfiRomBadSizeEFI Image Error
TRAP-TYPE
.1.3.6.1.4.1.11.2.23.35.0.5048
hpevtBootEfiRomXsumErrorEFI Image Error.
TRAP-TYPE
.1.3.6.1.4.1.11.2.23.35.0.5049
hpevtBootExtIntNestLimitedExceededThe IVT interrupting nesting depth has been exceeded. This processor will be halted. Data: Number of the offending vector.
TRAP-TYPE
.1.3.6.1.4.1.11.2.23.35.0.5050
hpevtBootExtIntNotServicedAn external interrupt has been requested and not serviced. Data: Number of the vector
TRAP-TYPE
.1.3.6.1.4.1.11.2.23.35.0.5051
hpevtBootExtIntTakenAn external interrupt has been taken. Data: Number of the vector taken.
TRAP-TYPE
.1.3.6.1.4.1.11.2.23.35.0.5052
hpevtBootFplFailedAccess to the FPL has failed.
TRAP-TYPE
.1.3.6.1.4.1.11.2.23.35.0.5053
hpevtBootGetPsrFailureSFW was unable to read the CPU PSR. Data: Physical location of CPU
TRAP-TYPE
.1.3.6.1.4.1.11.2.23.35.0.5054
hpevtBootHaltCellSFW has halted the cell or system
TRAP-TYPE
.1.3.6.1.4.1.11.2.23.35.0.5055
hpevtBootIncompatiblePalSFW has determined that PAL is not compatible with the current processors.
TRAP-TYPE
.1.3.6.1.4.1.11.2.23.35.0.5056
hpevtBootIncompatibleSlaveSFW has determined that a slave processor is incompatible with the monarch. Data: Physical location of the incompatible processor.
TRAP-TYPE
.1.3.6.1.4.1.11.2.23.35.0.5057
hpevtBootIntrptClearFailureInterrupt clear failed during cell config
TRAP-TYPE
.1.3.6.1.4.1.11.2.23.35.0.5058
hpevtBootIpmiEventFailedSFW has determined that an IPMI event failed.
TRAP-TYPE
.1.3.6.1.4.1.11.2.23.35.0.5059
hpevtBootIvtOffsetData: interrupt vector table (IVT) Offset
TRAP-TYPE
.1.3.6.1.4.1.11.2.23.35.0.5060
hpevtBootLdbStateBadLDB state bad
TRAP-TYPE
.1.3.6.1.4.1.11.2.23.35.0.5063
hpevtBootLostContextIntInterrupt context was lost. Data: interrupt number.
TRAP-TYPE
.1.3.6.1.4.1.11.2.23.35.0.5064
hpevtBootMinStateRegErrorRegistering of the processor min state save area with PAL has failed.
TRAP-TYPE
.1.3.6.1.4.1.11.2.23.35.0.5065
hpevtBootMonarchTimeoutSFW has determined the monarch has timed out. SFW is deconfiguring the CPU. Data: Physical Location of CPU
TRAP-TYPE
.1.3.6.1.4.1.11.2.23.35.0.5067
hpevtBootNoPalBInFitA PAL_B FIT error has occurred
TRAP-TYPE
.1.3.6.1.4.1.11.2.23.35.0.5069
hpevtBootNoSalBInFitA SAL_B FIT error has occurred
TRAP-TYPE
.1.3.6.1.4.1.11.2.23.35.0.5070
hpevtBootNvmFailNVM has failed test. The system will halt
TRAP-TYPE
.1.3.6.1.4.1.11.2.23.35.0.5073
hpevtBootOutOfRangeVectorA interrupt vector has been requested out of the acceptable range. Data: Vector Number.
TRAP-TYPE
.1.3.6.1.4.1.11.2.23.35.0.5076
hpevtBootPalCopyInfoErrorThe PAL Copy Info call has failed.
TRAP-TYPE
.1.3.6.1.4.1.11.2.23.35.0.5077
hpevtBootPalCopyPalErrorError copying PAL to memory
TRAP-TYPE
.1.3.6.1.4.1.11.2.23.35.0.5078
hpevtBootPalProcFailureA PAL Proc has failed. This will halt the processor. Data: Physical Location of CPU
TRAP-TYPE
.1.3.6.1.4.1.11.2.23.35.0.5079
hpevtBootPlatConsoleDevFailedA console device has failed. Data: Physical Addr of device that failed.
TRAP-TYPE
.1.3.6.1.4.1.11.2.23.35.0.5080
hpevtBootPlatIntfcDevFailedA console device has failed. Data: Physical Addr of device that failed.
TRAP-TYPE
.1.3.6.1.4.1.11.2.23.35.0.5081
hpevtBootPlatScrBadPlatform Scratch RAM has failed the test.
TRAP-TYPE
.1.3.6.1.4.1.11.2.23.35.0.5082
hpevtBootRendezFailureA CPU has failed to enter rendezvous. Data: Local CPU Number
TRAP-TYPE
.1.3.6.1.4.1.11.2.23.35.0.5083
hpevtBootSalExtractErrorSFW could not extract SAL_B from the ROM
TRAP-TYPE
.1.3.6.1.4.1.11.2.23.35.0.5084
hpevtBootScrFailPlatform Scratch RAM has failed test.
TRAP-TYPE
.1.3.6.1.4.1.11.2.23.35.0.5085
hpevtBootSelFullIPMI SEL full
TRAP-TYPE
.1.3.6.1.4.1.11.2.23.35.0.5087
hpevtBootSlaveNoFinalWakeupVectorNo wakeup vector registered for processor Data: Physical location of CPU
TRAP-TYPE
.1.3.6.1.4.1.11.2.23.35.0.5091
hpevtBootSlaveRendezHandlerFailSlave Rendezvous handler has failed. Data: Physical Location of CPU
TRAP-TYPE
.1.3.6.1.4.1.11.2.23.35.0.5092
hpevtBootSmbiosBuildErrorSFW failed to build the SMBIOS tables
TRAP-TYPE
.1.3.6.1.4.1.11.2.23.35.0.5098
hpevtBootTrapNestLimitedExceededThe trap nesting limit has been exceeded. Data: Vector Number
TRAP-TYPE
.1.3.6.1.4.1.11.2.23.35.0.5100
hpevtBootTrapNotServicedA trap has been requested and not serviced. Data: Vector Number
TRAP-TYPE
.1.3.6.1.4.1.11.2.23.35.0.5101
hpevtBootTrapTakenA trap has been taken. Data: Number of the vector taken.
TRAP-TYPE
.1.3.6.1.4.1.11.2.23.35.0.5102
hpevtBootUnclearedIntAt least one interrupt was not cleared. Data: The highest pending interrupt number
TRAP-TYPE
.1.3.6.1.4.1.11.2.23.35.0.5103
hpevtBootUnexpectedExtIntPostRedirTableAn unexpected external interrupt has occurred. Data: External Interrupt Number
TRAP-TYPE
.1.3.6.1.4.1.11.2.23.35.0.5104
hpevtBootUnexpectedIntPreRedirTableAn interrupt has occurred before setting up the Interrupt Vector Table. Data: Interrupt Number
TRAP-TYPE
.1.3.6.1.4.1.11.2.23.35.0.5105
hpevtBootUnexpectedMcaAn unexpected MCA has occurred before MCAs are unmasked. Data: Local CPU Number.
TRAP-TYPE
.1.3.6.1.4.1.11.2.23.35.0.5106
hpevtBootUnexpectedTrapPostRedirTableAn unexpected trap has occurred. The trap number is either invalid or the requested trap has not been registered. Data: Trap Number
TRAP-TYPE
.1.3.6.1.4.1.11.2.23.35.0.5107
hpevtBootUnknownFailureSFW has detected an unknown error.
TRAP-TYPE
.1.3.6.1.4.1.11.2.23.35.0.5108
hpevtErrorsPalFailureSFW has detected a PAL Failure
TRAP-TYPE
.1.3.6.1.4.1.11.2.23.35.0.5118
hpevtExpMcNotRegisteredExpected Machine Check Vector not registered
TRAP-TYPE
.1.3.6.1.4.1.11.2.23.35.0.5119
hpevtInitInitiatedThis 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
TRAP-TYPE
.1.3.6.1.4.1.11.2.23.35.0.5121
hpevtIoCheckLbaMissingErrAn 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.
TRAP-TYPE
.1.3.6.1.4.1.11.2.23.35.0.5123
hpevtIoCheckNumSlotsErrFirmware 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.
TRAP-TYPE
.1.3.6.1.4.1.11.2.23.35.0.5124
hpevtIoCheckRopeWidthErrFirmware 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.
TRAP-TYPE
.1.3.6.1.4.1.11.2.23.35.0.5125
hpevtIoCheckXtraLbaFoundErrFirmware 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.
TRAP-TYPE
.1.3.6.1.4.1.11.2.23.35.0.5127
hpevtIoDllErrorAn 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.
TRAP-TYPE
.1.3.6.1.4.1.11.2.23.35.0.5130
hpevtIoHotPlugCtrlFailedAn 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 host bridge.
TRAP-TYPE
.1.3.6.1.4.1.11.2.23.35.0.5131
hpevtIoInvalidRopeBundleFirmware 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.
TRAP-TYPE
.1.3.6.1.4.1.11.2.23.35.0.5132
hpevtIoLbaClearErrFailedDuring 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 host bridge.
TRAP-TYPE
.1.3.6.1.4.1.11.2.23.35.0.5133
hpevtIoLbaResetErrorAn 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.
TRAP-TYPE
.1.3.6.1.4.1.11.2.23.35.0.5136
hpevtIoNotEnoughPowerErrorThere 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.
TRAP-TYPE
.1.3.6.1.4.1.11.2.23.35.0.5137
hpevtIoPciMappingFailedFirmware 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.
TRAP-TYPE
.1.3.6.1.4.1.11.2.23.35.0.5138
hpevtIoPciMappingTooBigThe 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.
TRAP-TYPE
.1.3.6.1.4.1.11.2.23.35.0.5139
hpevtIoPciUnmappingFailedFirmware 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.
TRAP-TYPE
.1.3.6.1.4.1.11.2.23.35.0.5140
hpevtIoPcixcapSampleErrorAn 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.
TRAP-TYPE
.1.3.6.1.4.1.11.2.23.35.0.5141
hpevtIoPmNotRespondingErrorFirmware 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.
TRAP-TYPE
.1.3.6.1.4.1.11.2.23.35.0.5142
hpevtIoRopeResetErrorAn 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.
TRAP-TYPE
.1.3.6.1.4.1.11.2.23.35.0.5143
hpevtIoSbaClearErrFailedDuring 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.
TRAP-TYPE
.1.3.6.1.4.1.11.2.23.35.0.5144
hpevtIoSlotPowerDefaultErrorDuring 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.
TRAP-TYPE
.1.3.6.1.4.1.11.2.23.35.0.5145
hpevtIoSlotPowerOnErrorFirmware 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.
TRAP-TYPE
.1.3.6.1.4.1.11.2.23.35.0.5146
hpevtIoSlotStandbyPowerErrorAn 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.
TRAP-TYPE
.1.3.6.1.4.1.11.2.23.35.0.5147
hpevtIoUnknownPcixcapValAn 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.
TRAP-TYPE
.1.3.6.1.4.1.11.2.23.35.0.5148
hpevtIoUnsupRopeFreqFirmware 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.
TRAP-TYPE
.1.3.6.1.4.1.11.2.23.35.0.5149
hpevtIoUnsupportedLbaFirmware 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.
TRAP-TYPE
.1.3.6.1.4.1.11.2.23.35.0.5150
hpevtMcInitiatedA Machine Check has been initiated
TRAP-TYPE
.1.3.6.1.4.1.11.2.23.35.0.5152
hpevtMdtConstructAreaBadThere has been a problem building the Memory Data Table (MDT).
TRAP-TYPE
.1.3.6.1.4.1.11.2.23.35.0.5155
hpevtMdtLmmioEntryNotFoundThere has been a problem building the Memory Data Table (MDT).
TRAP-TYPE
.1.3.6.1.4.1.11.2.23.35.0.5156
hpevtMdtPageZeroBadMemory page 0 was slated for deallocation in the PDT. EFI cannot launch with page 0 bad, so the system will halt.
TRAP-TYPE
.1.3.6.1.4.1.11.2.23.35.0.5157
hpevtMdtUnableToFindSpaceThere has been a problem building the Memory Data Table (MDT).
TRAP-TYPE
.1.3.6.1.4.1.11.2.23.35.0.5158
hpevtMediaFailureThere has been a media failure.
TRAP-TYPE
.1.3.6.1.4.1.11.2.23.35.0.5159
hpevtMemBibRegFailureIndicates that the chipset register test has failed. The data field contains the physical address of the failing register.
TRAP-TYPE
.1.3.6.1.4.1.11.2.23.35.0.5160
hpevtMemCacheLine0WrRdFailedAfter FW's first access to main memory, FW detected that the CEC logged an error after reading back what was just written.
TRAP-TYPE
.1.3.6.1.4.1.11.2.23.35.0.5161
hpevtMemDimmLoadOrderErrA 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.
TRAP-TYPE
.1.3.6.1.4.1.11.2.23.35.0.5171
hpevtMemDimmSpdChecksumThe 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.
TRAP-TYPE
.1.3.6.1.4.1.11.2.23.35.0.5172
hpevtMemDimmSpdFatalDetected a error in DIMM SPD
TRAP-TYPE
.1.3.6.1.4.1.11.2.23.35.0.5173
hpevtMemDimmTypeIncompatibleA DIMM was installed whose DIMM type is not compatible with the current set of supported DIMMs for this platform.
TRAP-TYPE
.1.3.6.1.4.1.11.2.23.35.0.5174
hpevtMemDimmTypeMismatchThe 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.
TRAP-TYPE
.1.3.6.1.4.1.11.2.23.35.0.5175
hpevtMemDimmTypeTableFullThe DIMM type table is full
TRAP-TYPE
.1.3.6.1.4.1.11.2.23.35.0.5176
hpevtMemDmtEntryNotFoundAn 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 chip select of the rank caller is looking for.)
TRAP-TYPE
.1.3.6.1.4.1.11.2.23.35.0.5179
hpevtMemEccMbeDataTstFailedThe FW selftest of CEC multi-bit error (MBE) detection has failed. The upper 32 bits of the data field contain the Dword offset within the cacheline of the failed MBE detection. The lower 32 bits are split in two, and they contain the bit numbers within the Dword that were flipped in order to cause an MBE.
TRAP-TYPE
.1.3.6.1.4.1.11.2.23.35.0.5180
hpevtMemEccMbeSignalTstFailedThe FW selftest of CEC multi-bit error (MBE) signaling has failed. The upper 32 bits of the data field contain the Dword offset within the cacheline of the failed MBE detection. The lower 32 bits are split in two, and they contain the bit numbers within the Dword that were flipped in order to cause an MBE.
TRAP-TYPE
.1.3.6.1.4.1.11.2.23.35.0.5181
hpevtMemEccSbeDataTstFailedThe 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.
TRAP-TYPE
.1.3.6.1.4.1.11.2.23.35.0.5182
hpevtMemEccSbeEccTstFailedThe 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.
TRAP-TYPE
.1.3.6.1.4.1.11.2.23.35.0.5183
hpevtMemEnoughMemFailedMemory FW detected errors below 1MB. FW will not allow boot in this case, so memory FW will reinterleave and retest.
TRAP-TYPE
.1.3.6.1.4.1.11.2.23.35.0.5185
hpevtMemErrAddrNotInMbatMemory FW could not figure out which rank maps to the physical address specified in the data field.
TRAP-TYPE
.1.3.6.1.4.1.11.2.23.35.0.5186
hpevtMemErrClearFailMemory FW was unable to clear the platform error logs on the CEC. The Datafield contains the error status of the CEC.
TRAP-TYPE
.1.3.6.1.4.1.11.2.23.35.0.5187
hpevtMemErrLogFailedToClearMemory FW was unable to clear the platform error logs on the CEC. The Datafield contains the error status of the CEC.
TRAP-TYPE
.1.3.6.1.4.1.11.2.23.35.0.5189
hpevtMemErrorRegClearFailureThe Error registers in the CEC have failed to clear. The data field contains the error status of the CEC after the attempted clear.
TRAP-TYPE
.1.3.6.1.4.1.11.2.23.35.0.5190
hpevtMemExtFatalLoadOrdErrA 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.
TRAP-TYPE
.1.3.6.1.4.1.11.2.23.35.0.5191
hpevtMemFirmwareProbAn error occurred that memory FW does not know how to handle.
TRAP-TYPE
.1.3.6.1.4.1.11.2.23.35.0.5193
hpevtMemInterleaveCodeFailureThe memory interleaving code failed.
TRAP-TYPE
.1.3.6.1.4.1.11.2.23.35.0.5199
hpevtMemMainMemFailedFW was unable to create a memory configuration with no errors in low memory to hand off to EFI.
TRAP-TYPE
.1.3.6.1.4.1.11.2.23.35.0.5202
hpevtMemMbeInRankA series of MEM_MBE_IN_RANK chassis code will be sent when an error is detected by firmware. The data fields will contain information on the error based on the data type as follows: Physical Location - location of dimm(s) in error; Physical Address - address affect by error; Syndrome - Firmware generated ECC syndrome that can be used to further isolate the error.
TRAP-TYPE
.1.3.6.1.4.1.11.2.23.35.0.5204
hpevtMemMcRegFailureThe chipset's memory controller failed the register test. The data field contains the address of the register that failed selftest.
TRAP-TYPE
.1.3.6.1.4.1.11.2.23.35.0.5205
hpevtMemNoDimmsInstalledMemory Discovery could not detect any DIMMs installed.
TRAP-TYPE
.1.3.6.1.4.1.11.2.23.35.0.5208
hpevtMemNoMemFoundFW could not continue because there are no valid memory ranks loaded.
TRAP-TYPE
.1.3.6.1.4.1.11.2.23.35.0.5209
hpevtMemPdtDisabledHaltThe 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.
TRAP-TYPE
.1.3.6.1.4.1.11.2.23.35.0.5211
hpevtMemPdtDisabledWarningAn 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.
TRAP-TYPE
.1.3.6.1.4.1.11.2.23.35.0.5212
hpevtMemPdtNvmErrError writing entry into the PDT.
TRAP-TYPE
.1.3.6.1.4.1.11.2.23.35.0.5214
hpevtMemPdtTableFullAn attempt was made to add an entry to a full PDT. The entry is not added, and this event is sent.
TRAP-TYPE
.1.3.6.1.4.1.11.2.23.35.0.5216
hpevtMemPlatformInitFailureMemory 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
TRAP-TYPE
.1.3.6.1.4.1.11.2.23.35.0.5218
hpevtMemRankEntryNotFoundThe 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.
TRAP-TYPE
.1.3.6.1.4.1.11.2.23.35.0.5219
hpevtMemTestExcessMcBitsMore than one error type was detected when only one error type was expected.
TRAP-TYPE
.1.3.6.1.4.1.11.2.23.35.0.5237
hpevtMemTestFwdProgBitsInvalidThe forward progress bits that memory FW uses to track state are invalid. The data field is the fwd progress field.
TRAP-TYPE
.1.3.6.1.4.1.11.2.23.35.0.5238
hpevtMemTestStatusBitsInvalidThe memory error status has bits set in it that indicate another non-memory error occurred. The data field contains the CEC's error status.
TRAP-TYPE
.1.3.6.1.4.1.11.2.23.35.0.5244
hpevtMemTestSummaryBitsInvalidThe memory test summary bits are invalid. The data field is the test summary bits.
TRAP-TYPE
.1.3.6.1.4.1.11.2.23.35.0.5245
hpevtMemUnexpectedMcaMemory rank shadowing has been selected but is not supported by the revision of the memory controller.
TRAP-TYPE
.1.3.6.1.4.1.11.2.23.35.0.5248
hpevtMemWarnDistributionCheckBypassThe 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.
TRAP-TYPE
.1.3.6.1.4.1.11.2.23.35.0.5250
hpevtMemWarnLoadingOrderBypassThe 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.
TRAP-TYPE
.1.3.6.1.4.1.11.2.23.35.0.5252
hpevtMemWarnLoopOnDestTestThe control bit to loop on destructive memory test is set and the destructive memory tests are run continuously. This bit should only be done in the factory and not in the field.
TRAP-TYPE
.1.3.6.1.4.1.11.2.23.35.0.5253
hpevtMemWarnSetCheckBypassThe 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.
TRAP-TYPE
.1.3.6.1.4.1.11.2.23.35.0.5255
hpevtMemWarnSpdBypassThe 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.
TRAP-TYPE
.1.3.6.1.4.1.11.2.23.35.0.5256
hpevtMemWarnUsingAltConfigThe 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.
TRAP-TYPE
.1.3.6.1.4.1.11.2.23.35.0.5257
hpevtOsInitNotRegisteredThe OS_INIT vector has not been registered
TRAP-TYPE
.1.3.6.1.4.1.11.2.23.35.0.5260
hpevtOsMcaNotRegisteredThe OS_MCA vector has not been registered
TRAP-TYPE
.1.3.6.1.4.1.11.2.23.35.0.5263
hpevtOsMcaUncorrectedMcAn Uncorrected Machine Check has occurred
TRAP-TYPE
.1.3.6.1.4.1.11.2.23.35.0.5264
hpevtPdhMiscRegFailA PDH register has failed.
TRAP-TYPE
.1.3.6.1.4.1.11.2.23.35.0.5266
hpevtSalCheckUnknownFailThe handler for SAL_CHECK has failed for an unknown reason.
TRAP-TYPE
.1.3.6.1.4.1.11.2.23.35.0.5268
hpevtSalInitUnknownFailThe handler for SAL_INIT has failed for an unknown reason.
TRAP-TYPE
.1.3.6.1.4.1.11.2.23.35.0.5270
hpevtUndefinedSmcInterleaveErrIndicates that FW encountered a Fatal interleaving error. The data field contains the return status from the interleaving procedure call.
TRAP-TYPE
.1.3.6.1.4.1.11.2.23.35.0.5278
hpevtUnexpectedRetToSalCheckUnexpected return to SAL_CHECK.
TRAP-TYPE
.1.3.6.1.4.1.11.2.23.35.0.5279
hpevtUnexpectedRetToSalInitThe SFW TOC vector (SAL_INIT) has been unexpectedly returned to.
TRAP-TYPE
.1.3.6.1.4.1.11.2.23.35.0.5280
hpevtFwInstalledCpuDegradedFirmware is adding a device tree node for a CPU that is degraded in functionality. The cpu should not be trusted and will not be active in the system.
TRAP-TYPE
.1.3.6.1.4.1.11.2.23.35.0.5335
hpevtPdRendezTreeErrorFirmware 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 ansi string in the data field.
TRAP-TYPE
.1.3.6.1.4.1.11.2.23.35.0.5354
hpevtPdCellConfigErrorThe currently executing cell is not configured to be part of the cell set it is attempting to rendezvous with.
TRAP-TYPE
.1.3.6.1.4.1.11.2.23.35.0.5359
hpevtPdRemoteCsrReadErrorThe 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.
TRAP-TYPE
.1.3.6.1.4.1.11.2.23.35.0.5360
hpevtPdCellLateForRendezThe currently executing cell arrived too late to rendezvous with the other cells described in the complex profile as cells it should rendezvous with.
TRAP-TYPE
.1.3.6.1.4.1.11.2.23.35.0.5361
hpevtPdIncompatibleCpuTypesThe 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.
TRAP-TYPE
.1.3.6.1.4.1.11.2.23.35.0.5365
hpevtPdCellLateLocalRendezSetThe 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. The data field is unused, but the cell emitting this event is the one too late to rendezvous.
TRAP-TYPE
.1.3.6.1.4.1.11.2.23.35.0.5366
hpevtCellNotInGlobalSetThe 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.
TRAP-TYPE
.1.3.6.1.4.1.11.2.23.35.0.5376
hpevtNoViableCoreCellInPdNo cells in the PD can be a core cell. This is fatal.
TRAP-TYPE
.1.3.6.1.4.1.11.2.23.35.0.5380
hpevtErrorPromotingCoreCellSystem Firmware was unable to notify utilities of the selected core cell number.
TRAP-TYPE
.1.3.6.1.4.1.11.2.23.35.0.5383
hpevtFabricNoServiceProvidersThe fabric code is unable to find a service provider for a required banyan service.
TRAP-TYPE
.1.3.6.1.4.1.11.2.23.35.0.5403
hpevtFabricPortErrorThe fabric port specified in the data field had an error.
TRAP-TYPE
.1.3.6.1.4.1.11.2.23.35.0.5404
hpevtFabricReadErrorAn error occurred reading a CSR. The CSR address is displayed in the data field.
TRAP-TYPE
.1.3.6.1.4.1.11.2.23.35.0.5405
hpevtFabricWriteErrorError writing to Fabric. CSR data in data field.
TRAP-TYPE
.1.3.6.1.4.1.11.2.23.35.0.5406
hpevtXbcSlicesHwVersionDifferIncompatible crossbar slices are installed The data field is the two revisions reported by slice1 and slice0 of the CSR data. Bits [31:0] slice0 revision Bits [63:32] slice1 revision
TRAP-TYPE
.1.3.6.1.4.1.11.2.23.35.0.5407
hpevtXbcSlicesInDiffLocationCrossbar slices are in different locations. The data field is the two locations reported by slice1 and slice0 of the CSR data.
TRAP-TYPE
.1.3.6.1.4.1.11.2.23.35.0.5408
hpevtMonarchTakeoverA CPU has taken over as the monarch CPU.
TRAP-TYPE
.1.3.6.1.4.1.11.2.23.35.0.5411
hpevtDeadSramSRAM cannot be accessed on the cell board. Execution cannot continue.
TRAP-TYPE
.1.3.6.1.4.1.11.2.23.35.0.5416
hpevtDeadDillonThe PDH Arbiter component/chip cannot be located or used.
TRAP-TYPE
.1.3.6.1.4.1.11.2.23.35.0.5417
hpevtDeadPdhHwA required piece of PDH bus hardware cannot be contacted.
TRAP-TYPE
.1.3.6.1.4.1.11.2.23.35.0.5418
hpevtIoPciBusMixedSpeedsThe physical location of the PCI controller with mixed speeds is displayed in the data field.
TRAP-TYPE
.1.3.6.1.4.1.11.2.23.35.0.5419
hpevtIoPciBusDepthExceededDuring walking of the IO busses, the maximum depth was exceeded. This is a hardware configuration problem. The data field contains the physical location.
TRAP-TYPE
.1.3.6.1.4.1.11.2.23.35.0.5420
hpevtlotimeoutA Timeout occurred during RI initialization. The CSR is in the data field. The alert level will vary.
TRAP-TYPE
.1.3.6.1.4.1.11.2.23.35.0.5432
hpevtIoBuswalkSuperioSuperIO has been detected in the PCI slot displayed in the data field.
TRAP-TYPE
.1.3.6.1.4.1.11.2.23.35.0.5438
hpevtIoSbaCorrDataParityErrIO Link Software error was corrected.
TRAP-TYPE
.1.3.6.1.4.1.11.2.23.35.0.5440
hpevtIoSbaFatalDataParityErrParity error in Reg FIFO Internal parity error.
TRAP-TYPE
.1.3.6.1.4.1.11.2.23.35.0.5442
hpevtIoSbaUncFunctionErrTLB Fetch timeout.
TRAP-TYPE
.1.3.6.1.4.1.11.2.23.35.0.5443
hpevtIoSbaFatalFunctionErrLink presence goes away, FE.
TRAP-TYPE
.1.3.6.1.4.1.11.2.23.35.0.5444
hpevtIoSbaFatalParityErrLBA to SBA parity error on command, rope will go fatal.
TRAP-TYPE
.1.3.6.1.4.1.11.2.23.35.0.5445
hpevtIoSbaFatalMapErrAccess to invalid TLB entry Requesting rope fatal.
TRAP-TYPE
.1.3.6.1.4.1.11.2.23.35.0.5446
hpevtIoSbaFatalTimeoutErrMemory Fetch Timeout.
TRAP-TYPE
.1.3.6.1.4.1.11.2.23.35.0.5447
hpevtIoLbaInitErrAn error was encountered when initing the rope number specified in the data field.
TRAP-TYPE
.1.3.6.1.4.1.11.2.23.35.0.5448
hpevtIoLbaCorrTimeoutErrLBA correctable timeout error was encountered.
TRAP-TYPE
.1.3.6.1.4.1.11.2.23.35.0.5449
hpevtIoLbaUncFunctionErrLBA uncorrectable Function Error was encountered.
TRAP-TYPE
.1.3.6.1.4.1.11.2.23.35.0.5450
hpevtIoLbaUncTimeoutErrLBA uncorrectable Timeout Error was encountered.
TRAP-TYPE
.1.3.6.1.4.1.11.2.23.35.0.5451
hpevtIoLbaMiscUncErrMisc uncorrectable error discovered on LBA.
TRAP-TYPE
.1.3.6.1.4.1.11.2.23.35.0.5452
hpevtIoLbaUncParityErrLBA encountered an uncorrectable parity error.
TRAP-TYPE
.1.3.6.1.4.1.11.2.23.35.0.5453
hpevtIoLbaMiscFatalErrLBA misc. Fatal Error encountered.
TRAP-TYPE
.1.3.6.1.4.1.11.2.23.35.0.5454
hpevtIoLbaFatalFunctionErrLBA Fatal function error encountered.
TRAP-TYPE
.1.3.6.1.4.1.11.2.23.35.0.5455
hpevtIoLbaFatalParityErrLBA Fatal Parity error encountered.
TRAP-TYPE
.1.3.6.1.4.1.11.2.23.35.0.5456
hpevtIoLbaFatalTimeoutErrLBA Fatal timeout error encountered.
TRAP-TYPE
.1.3.6.1.4.1.11.2.23.35.0.5457
hpevtIoDevAdapterMiscUncErrMisc Uncorrectable Error encountered on the card specified in the data field.
TRAP-TYPE
.1.3.6.1.4.1.11.2.23.35.0.5458
hpevtIoDevAdapterMiscFatalErrMisc fatal error was discovered on the PCI card specified in the data field.
TRAP-TYPE
.1.3.6.1.4.1.11.2.23.35.0.5459
hpevtMemDimmSpdExtendedChecksumThe calculated and compared Checksums of the SPD EEPROM don't match.
TRAP-TYPE
.1.3.6.1.4.1.11.2.23.35.0.5464
hpevtOptsHdrCksumErrorThe Options component encountered a header checksum error. The actual data is in the data field of the chassis code.
TRAP-TYPE
.1.3.6.1.4.1.11.2.23.35.0.5467
hpevtOptsDataCksumErrorThe Options service data had a bad checksum. Actual data is in the data field.
TRAP-TYPE
.1.3.6.1.4.1.11.2.23.35.0.5468
hpevtPdMemIntlvWaysMismatchInternal inconsistency in the interleave tables.
TRAP-TYPE
.1.3.6.1.4.1.11.2.23.35.0.5473
hpevtPdMemUnintlvdMemoryThe CellInfoList is not null and was expected to be. There has been an error in interleaving.
TRAP-TYPE
.1.3.6.1.4.1.11.2.23.35.0.5474
hpevtPdMemNoMemoryDescError in constructing the Memory Descriptor.
TRAP-TYPE
.1.3.6.1.4.1.11.2.23.35.0.5478
hpevtPdMemUpdateLocalCellFailedUnable to update the local memory layout.
TRAP-TYPE
.1.3.6.1.4.1.11.2.23.35.0.5479
hpevtPdMemPdtAddrNotFoundA required address was not found within a mapped address in the PDT.
TRAP-TYPE
.1.3.6.1.4.1.11.2.23.35.0.5483
hpevtPdMemPdtInstallFailFailure to install a partition level PDT. Errors prevented it.
TRAP-TYPE
.1.3.6.1.4.1.11.2.23.35.0.5485
hpevtUnusableResourceA critical 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 Segment not usable: 0xdead0005; bad NVRAM: 0xdead0006; PDH Arbiter unusable: 0xdead0007; SRAM unusable: 0xdead0008; CPU unusable: 0xdead0009; Options Component Unusable: 0xdead000a; Real Time Clock unusable: DEAD_RTC; Unknown: 0xdead0086
TRAP-TYPE
.1.3.6.1.4.1.11.2.23.35.0.5490
hpevtFwErrorAn 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.
TRAP-TYPE
.1.3.6.1.4.1.11.2.23.35.0.5491
hpevtNvramDataCmpErrorNVRAM failed with a data compare error. 3 chassis codes will be sent. The first one will have the expected data and the second the actual data and the third one will be the address.
TRAP-TYPE
.1.3.6.1.4.1.11.2.23.35.0.5492
hpevtNvramCrcErrorAn NVRAM CRC Error was detected. There will always be 2 chassis codes sent. The first one will give the expected data and the second the actual data.
TRAP-TYPE
.1.3.6.1.4.1.11.2.23.35.0.5493
hpevtErmGet Error Response Mode has been called. The first 8 bytes of the response mode string are displayed in the data field and must be converted to ASCII from the hex values.
TRAP-TYPE
.1.3.6.1.4.1.11.2.23.35.0.5494
hpevtErrorObtainingSemaphoreThe 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.
TRAP-TYPE
.1.3.6.1.4.1.11.2.23.35.0.5496
hpevtNvramBlockRevMismatchThe NVRAM block requested has an unexpected revision. This chassis code will be emitted in pairs. The first one will contain the expected revision number, the second will contain the actual revision number.
TRAP-TYPE
.1.3.6.1.4.1.11.2.23.35.0.5498
hpevtNvramBlockNotFoundThe requested NVRAM block was not found. The ID that was not found is displayed in the data field.
TRAP-TYPE
.1.3.6.1.4.1.11.2.23.35.0.5499
hpevtNvramBlockLockedThe block id specified in the data field is locked.
TRAP-TYPE
.1.3.6.1.4.1.11.2.23.35.0.5500
hpevtNvramBlockUnlockedFirmware tried to unlock a NVRAM block that was already unlocked. Data field contains the block ID.
TRAP-TYPE
.1.3.6.1.4.1.11.2.23.35.0.5501
hpevtNvramHeaderNotFoundThe header in the NVRAM space was not found.
TRAP-TYPE
.1.3.6.1.4.1.11.2.23.35.0.5502
hpevtNvmFreelistCorruptThe Freelist used vor Non-Volatile Memory allocation is corrpt.
TRAP-TYPE
.1.3.6.1.4.1.11.2.23.35.0.5503
hpevtResetForReconfigSystem 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.
TRAP-TYPE
.1.3.6.1.4.1.11.2.23.35.0.5505
hpevtPdRendezUtilityErrorDuring PD rendezvous, system firmware encountered a problem sending commands to the utilities system. This will prevent a fully functional PD from being created.
TRAP-TYPE
.1.3.6.1.4.1.11.2.23.35.0.5507
hpevtHaltSystem 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.
TRAP-TYPE
.1.3.6.1.4.1.11.2.23.35.0.5509
hpevtDuiNoConsoleThe DUI (Developers User Interface) was entered, but there is no console available for the interface.
TRAP-TYPE
.1.3.6.1.4.1.11.2.23.35.0.5510
hpevtErrorProcFailedDuring Error processing and reporting, an error was detected that prevented further processing of errors. The data field contains an ASCII message indicating the problem.
TRAP-TYPE
.1.3.6.1.4.1.11.2.23.35.0.5511
hpevtReconfigResetFailSystem 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.
TRAP-TYPE
.1.3.6.1.4.1.11.2.23.35.0.5514
hpevtPdErrorReachableSetThe 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.
TRAP-TYPE
.1.3.6.1.4.1.11.2.23.35.0.5515
hpevtIoBridgeDepthExceededFirmware 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)
TRAP-TYPE
.1.3.6.1.4.1.11.2.23.35.0.5518
hpevtEfiConsoleDriverErrorDebugging 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.
TRAP-TYPE
.1.3.6.1.4.1.11.2.23.35.0.5521
hpevtMemTestCodeInPage0CorruptThis event is unused
TRAP-TYPE
.1.3.6.1.4.1.11.2.23.35.0.5525
hpevtRemoteCellStateUnknownThe reporting cell read an unknown state from a remote cell. This chassis code will be emitted in pairs. The first one indicating the cell number in the data field and the second code indicating the state read in the data field.
TRAP-TYPE
.1.3.6.1.4.1.11.2.23.35.0.5527
hpevtPdMltplCoreCellsThe reporting Cell thinks that it should be the core cell but has discovered another cell in the same PD that thinks it should be the core cell. This is a serious problem.
TRAP-TYPE
.1.3.6.1.4.1.11.2.23.35.0.5528
hpevtUtilSendCommandErrorThe utilities system firmware component received an error response from the SINC in response to a command being sent. The exact error is displayed in the data field. Typically, this can occur when the SINC cannot talk to the MP.
TRAP-TYPE
.1.3.6.1.4.1.11.2.23.35.0.5529
hpevtUtilCellSlotErrorSystem 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.
TRAP-TYPE
.1.3.6.1.4.1.11.2.23.35.0.5530
hpevtMcCellRendezFailedThis denotes the fact that all the cpus in the cell did not rendezvous.
TRAP-TYPE
.1.3.6.1.4.1.11.2.23.35.0.5546
hpevtMcNoAccessToPdThis chassis code indicates that the cell does not have any access to a PD.
TRAP-TYPE
.1.3.6.1.4.1.11.2.23.35.0.5547
hpevtMcLossOfLockstepThis 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.
TRAP-TYPE
.1.3.6.1.4.1.11.2.23.35.0.5548
hpevtMcPdCellRendezFailedThis indicates that some of the cells did not show up during the PD level rendezvous.
TRAP-TYPE
.1.3.6.1.4.1.11.2.23.35.0.5550
hpevtMcProcErrHaltThis indicates that catastrophic errors have been found in the PIN block of the cell controller. The cell needs to be reset/ halt.
TRAP-TYPE
.1.3.6.1.4.1.11.2.23.35.0.5556
hpevtMcCellMonarchTimeoutThis means that the cell monach cpu has not completed the assigned task within the timeout and hence it will be deconfigured.
TRAP-TYPE
.1.3.6.1.4.1.11.2.23.35.0.5557
hpevtMcPdCellMissedRendezThis indicates that the cell is too late for the PD level rendezvous. And hence it will not join the other PD cells.
TRAP-TYPE
.1.3.6.1.4.1.11.2.23.35.0.5558
hpevtMcPdMonarchTimeoutThis indicates the state where the PD monarch was not able to complete the task within a certain time. It failed.
TRAP-TYPE
.1.3.6.1.4.1.11.2.23.35.0.5559
hpevtRemoteSetViewRootErrorSystem firmware on the Core cell was unable to update a slave cell with the location of the root of the partition tree. The CPU that was unable to be contacted is printed in the data field.
TRAP-TYPE
.1.3.6.1.4.1.11.2.23.35.0.5560
hpevtCsrTestFailureRead test on a CSR failed and the CSR contents were not updated. This chassis code will be emitted in 3's, with the CSR Address, expected data, and actual data given.
TRAP-TYPE
.1.3.6.1.4.1.11.2.23.35.0.5566
hpevtPdMemGetIcmInfoFailedThis chassis code reports the failure in collecting the ICM parameters needed for the cell interleaving.
TRAP-TYPE
.1.3.6.1.4.1.11.2.23.35.0.5567
hpevtPdMemGetCellInfoFailedThis chassis code indicates that the cell interleaving routine could not get the information on the cell memory.
TRAP-TYPE
.1.3.6.1.4.1.11.2.23.35.0.5568
hpevtPdMemUpdateCellGniFailedThis 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.
TRAP-TYPE
.1.3.6.1.4.1.11.2.23.35.0.5569
hpevtPdMemAdjustMinZiFailedThis represents the failure in adjusting the memory information with the minimum ZI requirements.
TRAP-TYPE
.1.3.6.1.4.1.11.2.23.35.0.5570
hpevtStableProfileXsumErrorComplex Profile A (Stable Profile) stored checksum does not match the calculated checksum. The expected data and actual data are displayed in the 2 reporting event Ids.
TRAP-TYPE
.1.3.6.1.4.1.11.2.23.35.0.5572
hpevtDynamicProfileXsumErrorThe 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.
TRAP-TYPE
.1.3.6.1.4.1.11.2.23.35.0.5573
hpevtPartitionProfileXsumErrorThe 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.
TRAP-TYPE
.1.3.6.1.4.1.11.2.23.35.0.5574
hpevtStableProfileSeqidInvalidThe Complex Profile Group A sequence ID is invalid. Booting cannot continue. The actual data is in the chassis code data field.
TRAP-TYPE
.1.3.6.1.4.1.11.2.23.35.0.5575
hpevtDynamicProfileSeqidInvalidThe Dynamic Complex Profile (Group B) sequence ID is invalid. The invalid Sequence ID is displayed in the data field.
TRAP-TYPE
.1.3.6.1.4.1.11.2.23.35.0.5577
hpevtPartitionProfileSeqidInvalidThe Group C Partition Complex Profile Sequence ID is invalid. The value read is displayed in the data field.
TRAP-TYPE
.1.3.6.1.4.1.11.2.23.35.0.5578
hpevtEfiFwErrorAn 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.
TRAP-TYPE
.1.3.6.1.4.1.11.2.23.35.0.5579
hpevtCmplxProfilePdNumMismatchThe Complex Profile Group A PD assignment for this cell does not match the PD or Partition number in Group C of the complex profile. This is a fatal condition for the cell. The PD number from group A will be emitted first, followed by a subsequent code for the PD assigned in group C.
TRAP-TYPE
.1.3.6.1.4.1.11.2.23.35.0.5580
hpevtCmplxProfilePdNumInvalidThe Partition (PD) assigned to this cell in the complex profile group A and C is larger than the maximum allowed number of PDs as specified by Group A.
TRAP-TYPE
.1.3.6.1.4.1.11.2.23.35.0.5581
hpevtXbcPortSm4ErrorTried 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.
TRAP-TYPE
.1.3.6.1.4.1.11.2.23.35.0.5583
hpevtXbcPortSm4NotReleasedCurrently 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.
TRAP-TYPE
.1.3.6.1.4.1.11.2.23.35.0.5584
hpevtBootBmcTokenUploadFailureThere was an error reading from the BMC token when attempting to write to SAL NVM. This is a stop boot condition. Data: Lower 32 bits, BMC Token Number. Upper 32 bits, bmc return status.
TRAP-TYPE
.1.3.6.1.4.1.11.2.23.35.0.5594
hpevtBootNvmTokenAccessFailureThe read from SAL NVM has failed. This is a stop boot condition. Data: The token number on which the read failed
TRAP-TYPE
.1.3.6.1.4.1.11.2.23.35.0.5595
hpevtBootBmcTokenDownloadErrorThere was an error when trying to write to a BMC Token. This is a boot warning condition. Data: lower 32 bits are BMC token number, upper 32 bits is the status return from the BMC.
TRAP-TYPE
.1.3.6.1.4.1.11.2.23.35.0.5596
hpevtBootErrorWritingFirstBootTokenThere has been an error writing the BMC_FIRST_BOOT token. This is a stop boot condition.
TRAP-TYPE
.1.3.6.1.4.1.11.2.23.35.0.5597
hpevtBootFruReadErrorThe read of a FRU has failed. Data: Device ID of device that failed the FRU read.
TRAP-TYPE
.1.3.6.1.4.1.11.2.23.35.0.5598
hpevtBootFruXsumErrorThe read of a FRU has failed the checksum test. Data: Device ID of device that failed the FRU read.
TRAP-TYPE
.1.3.6.1.4.1.11.2.23.35.0.5599
hpevtBootFruVersionErrorThe read of a FRU has failed due to a version problem. Data: Device ID of device that failed the FRU read.
TRAP-TYPE
.1.3.6.1.4.1.11.2.23.35.0.5600
hpevtBootRomRevToFitRevWarningA 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
TRAP-TYPE
.1.3.6.1.4.1.11.2.23.35.0.5601
hpevtBootRomRevToRevBlockWarningA 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
TRAP-TYPE
.1.3.6.1.4.1.11.2.23.35.0.5602
hpevtBootPrimaryFitBadThe FIT is bad.
TRAP-TYPE
.1.3.6.1.4.1.11.2.23.35.0.5603
hpevtBootSecondaryFitBadThe FIT is bad.
TRAP-TYPE
.1.3.6.1.4.1.11.2.23.35.0.5604
hpevtBootPalARomWarningPAL_A_ROM has generated a warning.
TRAP-TYPE
.1.3.6.1.4.1.11.2.23.35.0.5605
hpevtBootPalBRomWarningPAL_B_ROM has generated a warning.
TRAP-TYPE
.1.3.6.1.4.1.11.2.23.35.0.5606
hpevtErrorUpdatingGroupBProfileFirmware tried to default the Dynamic (Group B) complex profile and encountered an error.
TRAP-TYPE
.1.3.6.1.4.1.11.2.23.35.0.5607
hpevtIoPciPerrAn I/O device (or host bridge) detected a bus parity error. An I/O device (or host bridge) mastered a bus transaction and received a parity error response from the target. Data Field: Physical location of the I/O device (or host bridge).
TRAP-TYPE
.1.3.6.1.4.1.11.2.23.35.0.5617
hpevtIoPciSerrAn I/O device (or host bridge) detected an internal error. An I/O device (or host bridge) detected a bus error. Data Field: Physical location of the I/O device (or host bridge).
TRAP-TYPE
.1.3.6.1.4.1.11.2.23.35.0.5618
hpevtIoCheckLbaDeconfigErrFirmware has deconfigured an I/O host bridge due to an error (see earlier error event). Firmware will display the following EFI warning message, 'Failed I/O slot(s) deconfigured.' Data Field: Physical location of the deconfigured I/O host bridge.
TRAP-TYPE
.1.3.6.1.4.1.11.2.23.35.0.5619
hpevtErrorUpdatingGroupCProfileFirmware tried to default the Partition (Group C) complex profile and encountered an error.
TRAP-TYPE
.1.3.6.1.4.1.11.2.23.35.0.5621
hpevtCellNotInAPdThe Reporting Cell is not configured to be in a PD, according to Complex Profile Group A.
TRAP-TYPE
.1.3.6.1.4.1.11.2.23.35.0.5622
hpevtMemDimmThermalLoadOrderWarnDIMMs are not loaded on the extender in a thermally optimal way. Boot is still possible, but the DIMM arrangement should be changed to the loading order recommended in the users manual. The data field indicates the number of the extender with incorrectly loaded DIMMs.
TRAP-TYPE
.1.3.6.1.4.1.11.2.23.35.0.5623
hpevtCellMajorityNotPresentNot enough cells made the Rendezvous for boot to continue. The rules are listed in the cause action section.
TRAP-TYPE
.1.3.6.1.4.1.11.2.23.35.0.5626
hpevtInitRendezvousSlavesFailSFW's INIT handler failed to rendezvous the processors.
TRAP-TYPE
.1.3.6.1.4.1.11.2.23.35.0.5638
hpevtMcIoClearFailSFW's Machine Check Handler was unable to log or clear I/O error registers.
TRAP-TYPE
.1.3.6.1.4.1.11.2.23.35.0.5646
hpevtMcPalCantEscalateToBerrCannot escalate an MCA to BERR
TRAP-TYPE
.1.3.6.1.4.1.11.2.23.35.0.5655
hpevtMcPalCantEscalateToBinitCannot escalate an MCA to BINIT.
TRAP-TYPE
.1.3.6.1.4.1.11.2.23.35.0.5656
hpevtMcPalGetFeatFailSFW failed to get the feature set from PAL.
TRAP-TYPE
.1.3.6.1.4.1.11.2.23.35.0.5657
hpevtMcPalRendFailPAL Failed to rendezvous the processors during a MCA.
TRAP-TYPE
.1.3.6.1.4.1.11.2.23.35.0.5658
hpevtMcPalSetFeatFailSFW failed to get the feature set from PAL.
TRAP-TYPE
.1.3.6.1.4.1.11.2.23.35.0.5659
hpevtMcRendezvousSlavesFailSFW's MCA Handler has failed to rendezvous all the slaves Data: Return from the rendezvous call.
TRAP-TYPE
.1.3.6.1.4.1.11.2.23.35.0.5677
hpevtMcRendezBadVectRangeA bad rendezvous vector has been registered.
TRAP-TYPE
.1.3.6.1.4.1.11.2.23.35.0.5679
hpevtMcRendezNoMonarchNo Machine Check Monarch exists, exiting MC Rendezvous.
TRAP-TYPE
.1.3.6.1.4.1.11.2.23.35.0.5682
hpevtMcRendezNoWakeupThe OS has not registered a wake-up mechanism for rendezvous.
TRAP-TYPE
.1.3.6.1.4.1.11.2.23.35.0.5683
hpevtMcRendezPalCantEscalatePAL call failed to set the BINIT escalation bit
TRAP-TYPE
.1.3.6.1.4.1.11.2.23.35.0.5684
hpevtMcRendezPalGetFeatFailThe PAL call PAL_GET_FEATURES has failed.
TRAP-TYPE
.1.3.6.1.4.1.11.2.23.35.0.5685
hpevtMcRendezPalSetFeatFailThe PAL call PAL_SET_FEATURES has failed.
TRAP-TYPE
.1.3.6.1.4.1.11.2.23.35.0.5686
hpevtSalAbiFwErrorAn 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.
TRAP-TYPE
.1.3.6.1.4.1.11.2.23.35.0.5692
hpevtMemExtLoadOrdErrThe Memory extenders have not been loaded in the correct order.
TRAP-TYPE
.1.3.6.1.4.1.11.2.23.35.0.5696
hpevtEfiEsiTableLengthErrThe 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.
TRAP-TYPE
.1.3.6.1.4.1.11.2.23.35.0.5698
hpevtEfiEsiTableChecksumErrThe computed checksum for the ESI (Extensible SAL Interface) table is not zero as expected. EFI is halting. Data Field: the computed checksum.
TRAP-TYPE
.1.3.6.1.4.1.11.2.23.35.0.5700
hpevtEfiEsiTableUnsupportedEntryTypeEFI found an unsupported entry type within the ESI (Extensible SAL Interface) Table. Data Field: unknown type.
TRAP-TYPE
.1.3.6.1.4.1.11.2.23.35.0.5701
hpevtEfiGuidTooLargeEFI 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.
TRAP-TYPE
.1.3.6.1.4.1.11.2.23.35.0.5704
hpevtEfiHaltEFI is halting. Look for the cause of the halt in preceding events. Data Field: the 'halt' (0x0F) major change in system state code.
TRAP-TYPE
.1.3.6.1.4.1.11.2.23.35.0.5708
hpevtMemChipspareNotSupportedThis code will be sent when FW detects a rank installed in the system that doesn't support chipspare. The data field is used to indicate the rank that the x8 DIMMs are installed. It is in the format 0x00000000XDXCXBXA or 0x00000000YBYAXBXA where X and Y are the number of the rank.
TRAP-TYPE
.1.3.6.1.4.1.11.2.23.35.0.5711
hpevtEfiAssertErrorEFI has detected an internal error. The actual error is unspecified by this event. Examine previous events and console output for possible explanations.
TRAP-TYPE
.1.3.6.1.4.1.11.2.23.35.0.5712
hpevtEfiEfiBreakpointEFI has executed the 'break' shell command. EFI is halting. The 'break' command is currently implemented as an infinite loop to halt EFI.
TRAP-TYPE
.1.3.6.1.4.1.11.2.23.35.0.5713
hpevtEfiHcdHostHungThe EFI USB interrupt service has detected the host controller is hung. EFI is halting.
TRAP-TYPE
.1.3.6.1.4.1.11.2.23.35.0.5714
hpevtEfiSalHandoffVerMismatchThe 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.
TRAP-TYPE
.1.3.6.1.4.1.11.2.23.35.0.5715
hpevtEfiSalRtcServiceNotInitEFI 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.
TRAP-TYPE
.1.3.6.1.4.1.11.2.23.35.0.5717
hpevtEfiSalTimerServiceNotInitEFI 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.
TRAP-TYPE
.1.3.6.1.4.1.11.2.23.35.0.5718
hpevtEfiSalStarttimerServiceNotInitEFI 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.
TRAP-TYPE
.1.3.6.1.4.1.11.2.23.35.0.5719
hpevtEfiNoIoPortSpaceRegionFoundEFI did not find an I/O port space region in the MDT. EFI is halting.
TRAP-TYPE
.1.3.6.1.4.1.11.2.23.35.0.5720
hpevtEfiBreakpointEFI reached an unimplemented section of code. EFI is halting. Data Field: Unique identifier indicating the location reached within the code.
TRAP-TYPE
.1.3.6.1.4.1.11.2.23.35.0.5721
hpevtEfiSpeedyBootTokenNotReadEFI 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 boot test EFI shell command and via the OS. These other accesses will likely fail. Data Field: Return status from internal EFI function..
TRAP-TYPE
.1.3.6.1.4.1.11.2.23.35.0.5722
hpevtEfiSalCallbackAttemptedA SAL Callback was attempted. This is not permitted. EFI is halting. Data Field: index of the function that was being called.
TRAP-TYPE
.1.3.6.1.4.1.11.2.23.35.0.5723
hpevtEfiSalFreqBaseUnknownWhile attempting to calibrate the EFI stall timer, system firmware is unable to determine the frequency of the CPU interval timer. System firmware will assume 800 MHz for the purpose of the stall timer calibration and continue boot. Data Field: error status code (should be 0xFFFFFFFD).
TRAP-TYPE
.1.3.6.1.4.1.11.2.23.35.0.5724
hpevtEfiSysEventAlreadyInitThe EFI system events have already been initialized. This is unexpected. EFI is continuing. Data Field: the current value of the system event entry point.
TRAP-TYPE
.1.3.6.1.4.1.11.2.23.35.0.5725
hpevtEfiSysEventCreateEventFailEFI 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.
TRAP-TYPE
.1.3.6.1.4.1.11.2.23.35.0.5726
hpevtFpgaNodeInitErrorAn error was detected while initializing the FPGA node and services associated with the PDH.
TRAP-TYPE
.1.3.6.1.4.1.11.2.23.35.0.5728
hpevtIoconfigNodeInitErrorFirmware encountered an error when creating the ioconfig node as a child of the pdh node.
TRAP-TYPE
.1.3.6.1.4.1.11.2.23.35.0.5729
hpevtDillonPdhNodeInitErrorSystem firmware was unable to correctly set up the pdh arbiter node as a child of the pdh node, or was unable to locate and attach the pdh arbiter service to the node. The status is returned in the data field.
TRAP-TYPE
.1.3.6.1.4.1.11.2.23.35.0.5730
hpevtPdhPropertyErrorThe PDH service was unable to either get or set the property specified in the data field as an ASCII message.
TRAP-TYPE
.1.3.6.1.4.1.11.2.23.35.0.5731
hpevtPdhAcpihwNodeErrorPDH encountered an error creating the ACPI Hardware Node in the device tree or installing its properties.
TRAP-TYPE
.1.3.6.1.4.1.11.2.23.35.0.5732
hpevtPdhIpmiNodeErrorThe PDH service encountered an error while creating the ipmi node or adding properties to it. The status is in the data field.
TRAP-TYPE
.1.3.6.1.4.1.11.2.23.35.0.5733
hpevtBootCpusNotCompatibleInstalled processors are not of compatible models or families
TRAP-TYPE
.1.3.6.1.4.1.11.2.23.35.0.5734
hpevtBootCacheSizesInconsistantProcessors with different cache sizes are installed
TRAP-TYPE
.1.3.6.1.4.1.11.2.23.35.0.5735
hpevtBootSelectingNewMonarchSFW is selecting a new monarch processor due to compatibility problems.
TRAP-TYPE
.1.3.6.1.4.1.11.2.23.35.0.5737
hpevtBootMonSelSteppingsNoEqualThe monarch stepping is not equal to the lowest installed CPU stepping.
TRAP-TYPE
.1.3.6.1.4.1.11.2.23.35.0.5738
hpevtBootCpuOverClockedA CPU's FSB frequency is overclocked. Data: Local CPU Number.
TRAP-TYPE
.1.3.6.1.4.1.11.2.23.35.0.5740
hpevtBootCpuInfoRomAccessErrorThere was an error reading the info ROM area of the CPU. Data: CPU Physical location
TRAP-TYPE
.1.3.6.1.4.1.11.2.23.35.0.5741
hpevtBootPalANotExecutedPAL_A has not been executed and control has been transferred back to SAL_B.
TRAP-TYPE
.1.3.6.1.4.1.11.2.23.35.0.5742
hpevtBootPalBNotExecutedPAL_B has not been executed and control has been transferred back to SAL_B.
TRAP-TYPE
.1.3.6.1.4.1.11.2.23.35.0.5743
hpevtBootProtoTypeCpuInstalledData: Lower 32 bits have Local CPU Number
TRAP-TYPE
.1.3.6.1.4.1.11.2.23.35.0.5744
hpevtBootFinalRendezWatchdogFailData: Monarch's Local CPU Number
TRAP-TYPE
.1.3.6.1.4.1.11.2.23.35.0.5745
hpevtCpuSupplementalTestFailedSupplemental tests have been run on the cpus in the node and an error was encountered. If this event id is only emitted once, then the cpu detected that it failed on its own and the offending CPU id is in the data field. If the event is emitted three times, then the monarch CPU on the cell detected the error and the offending CPU id, expected data and actual data are reported in the data field of the three events.
TRAP-TYPE
.1.3.6.1.4.1.11.2.23.35.0.5746
hpevtFabricReadMbeErrorWhile reading a XBC CSR, a multi-bit error was found. Data field includes the CSR data that includes the error. A previous event, FABRIC_READ_ERROR, details the CSR address that failed.
TRAP-TYPE
.1.3.6.1.4.1.11.2.23.35.0.5747
hpevtFabricUnexpectedStatusThe return value from a function was an unknown value. Data field is the unknown status that was returned.
TRAP-TYPE
.1.3.6.1.4.1.11.2.23.35.0.5749
hpevtEfiSysidBmcWarningEFI 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.
TRAP-TYPE
.1.3.6.1.4.1.11.2.23.35.0.5750
hpevtEfiSysidBmcReadErrorBMC 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)
TRAP-TYPE
.1.3.6.1.4.1.11.2.23.35.0.5751
hpevtEfiSysidBmcWriteErrorFirmware 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.
TRAP-TYPE
.1.3.6.1.4.1.11.2.23.35.0.5752
hpevtEfiSysidInvalidThe 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: 64-bit value. If preceded by 0xbad00000000000 the following valid values are possible: 0000 -> valid UUID (should never see this one) 0001 -> magic UUID 0002 -> inaccessible UUID 0004 -> invalid (bad CRC) UUID If zero, then one of the following conditions occurred: Invalid combination of primary and secondary system ID values User declined copying/entering system ID values when prompted by firmware All other values indicate failure during attempt to update system IDs.
TRAP-TYPE
.1.3.6.1.4.1.11.2.23.35.0.5753
hpevtEfiRtIvtEsiTableErrEFI 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.
TRAP-TYPE
.1.3.6.1.4.1.11.2.23.35.0.5755
hpevtEfiRtIvtEsiQueryErrEFI 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.
TRAP-TYPE
.1.3.6.1.4.1.11.2.23.35.0.5756
hpevtEfiBootIvtEsiTableErrEFI 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.
TRAP-TYPE
.1.3.6.1.4.1.11.2.23.35.0.5757
hpevtEfiBootIvtEsiQueryErrEFI 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.
TRAP-TYPE
.1.3.6.1.4.1.11.2.23.35.0.5758
hpevtUtilitiesParmListTooLargeToo many parameters were passed in a request for the utilities system to perform an operation. No more data is provided.
TRAP-TYPE
.1.3.6.1.4.1.11.2.23.35.0.5760
hpevtXbcPortPresenceErrorA 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.
TRAP-TYPE
.1.3.6.1.4.1.11.2.23.35.0.5762
hpevtXbcPortHwLinkErrorA 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.
TRAP-TYPE
.1.3.6.1.4.1.11.2.23.35.0.5763
hpevtXbcPortFeErrorA 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.
TRAP-TYPE
.1.3.6.1.4.1.11.2.23.35.0.5764
hpevtXinLinkInitErrorThere was an error while initializing the Cell Controller-Xbc interface. The data field contains the address of the Cell Controller CSR for which the error occurred.
TRAP-TYPE
.1.3.6.1.4.1.11.2.23.35.0.5766
hpevtXinLinkInitFailedThe CC - XBC link failed to initialize.
TRAP-TYPE
.1.3.6.1.4.1.11.2.23.35.0.5767
hpevtEfiGetMfgModeNotInitEFI 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.
TRAP-TYPE
.1.3.6.1.4.1.11.2.23.35.0.5768
hpevtEfiBmcMfgModeInvalidThe BMC has returned an invalid system mode. Data Field: the invalid mode. Expected values are 0 or 1.
TRAP-TYPE
.1.3.6.1.4.1.11.2.23.35.0.5769
hpevtEfiEnterMfgModeNotInitEFI 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.
TRAP-TYPE
.1.3.6.1.4.1.11.2.23.35.0.5770
hpevtEfiExitMfgModeNotInitEFI 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.
TRAP-TYPE
.1.3.6.1.4.1.11.2.23.35.0.5771
hpevtEfiTaccessServiceNotInitEFI 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.
TRAP-TYPE
.1.3.6.1.4.1.11.2.23.35.0.5772
hpevtTreeNodeNotFoundA needed tree node was not found. The data field contains the ASCII name of the tree node that was not found.
TRAP-TYPE
.1.3.6.1.4.1.11.2.23.35.0.5774
hpevtEfiSystemStateRunningErrEFI is unable to modify the system state from 'booting' to 'running'. This is done as part of Exit Boot Services. The system will not be able to enter a sleep mode. Data Field: For errors, this data is zero. For warnings, this data indicates the current system state as: 0 Error 1 booting 2 running 3 attention 4 fault 5 booting + attention
TRAP-TYPE
.1.3.6.1.4.1.11.2.23.35.0.5776
hpevtPalBusConfigIncompatibleCPUBusConfigValue setting in options as been compared with what is reported by PAL as settable and CPUBusConfigValue is specifying at least one bit that is not supported by this version of PAL using the Get Processor Bus Dependent Configuration Features. This chassis code is emitted in pairs, the first data field contains the PAL expected values; the second data field contains the requested setting from options.
TRAP-TYPE
.1.3.6.1.4.1.11.2.23.35.0.5777
hpevtPalGetBusFeaturesFailedFirmware was unable to correctly issue the Get Processor Bus Dependent Configuration Features command.
TRAP-TYPE
.1.3.6.1.4.1.11.2.23.35.0.5778
hpevtMemDimmPairMismatchA pair of DIMMs installed in the system are mismatched, and that pair of DIMMs will not be used. The data field indicates which pair of DIMMs are mismatched in the format 0x000000000000XBXA where X is the number of the rank that is mismatched.
TRAP-TYPE
.1.3.6.1.4.1.11.2.23.35.0.5779
hpevtEfiPosseLibNotInitEFI is unable to initialize internal library. This collection of internal services is required for much of EFI's functionality. EFI is halting.
TRAP-TYPE
.1.3.6.1.4.1.11.2.23.35.0.5784
hpevtEfiSecurityNotInitEFI is unable to initialize the security level. 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.
TRAP-TYPE
.1.3.6.1.4.1.11.2.23.35.0.5785
hpevtEfiSecInvalidSysmodeEFI 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.
TRAP-TYPE
.1.3.6.1.4.1.11.2.23.35.0.5786
hpevtEfiSecSetPassLevelErrEFI 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.
TRAP-TYPE
.1.3.6.1.4.1.11.2.23.35.0.5787
hpevtMdtBadSFW has determined that the Memory Data Table (MDT) table is invalid.
TRAP-TYPE
.1.3.6.1.4.1.11.2.23.35.0.5788
hpevtBootCpuBadCoreFixedRatioProcessor has incompatible fixed core ratio. Data: Local CPU Number.
TRAP-TYPE
.1.3.6.1.4.1.11.2.23.35.0.5790
hpevtBootAllCpusSlatedForCompatDeconfigData: A bitmask for which CPUs are slated to be deconfigured
TRAP-TYPE
.1.3.6.1.4.1.11.2.23.35.0.5791
hpevtXbcReadRemoteRouteErrorAn 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).
TRAP-TYPE
.1.3.6.1.4.1.11.2.23.35.0.5793
hpevtXbcReadNeighborInfoErrorAn 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.
TRAP-TYPE
.1.3.6.1.4.1.11.2.23.35.0.5794
hpevtMemDimmQuadMismatchA quad of DIMMs installed in the system are mismatched, and that quad of DIMMs will not be used. The data field indicates which quad of DIMMs are mismatched in the format 0x00000000XDXCXBXA where X is the number of the rank that is mismatched.
TRAP-TYPE
.1.3.6.1.4.1.11.2.23.35.0.5795
hpevtMemDimmFailedThe DIMM at the physical location given by the data field had excessive errors and has been marked as 'FAILED' by firmware.
TRAP-TYPE
.1.3.6.1.4.1.11.2.23.35.0.5796
hpevtXbcPortOeErrorA 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).
TRAP-TYPE
.1.3.6.1.4.1.11.2.23.35.0.5797
hpevtXbcPortStatusErrorUnable 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).
TRAP-TYPE
.1.3.6.1.4.1.11.2.23.35.0.5798
hpevtXbcPortLandminedA XBC port was unexpectedly found to be landmined. The data field consists of the XBC number (32:43) and the port number (44:55).
TRAP-TYPE
.1.3.6.1.4.1.11.2.23.35.0.5799
hpevtPdIncompatibleCpuSpeedsReporting cell tried to rendezvous with a cell with processors that are running at a different speed. The data field lists the offending cell
TRAP-TYPE
.1.3.6.1.4.1.11.2.23.35.0.5800
hpevtFabricCellLinkNotInitThe link between the local CC and the local XBC is unexpectedly not initialized. The data field is the XIN_LINK_STATE CC CSR value.
TRAP-TYPE
.1.3.6.1.4.1.11.2.23.35.0.5802
hpevtFabricInvalidXbcNumA 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.
TRAP-TYPE
.1.3.6.1.4.1.11.2.23.35.0.5803
hpevtFabricInvalidXbcPortNumA 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).
TRAP-TYPE
.1.3.6.1.4.1.11.2.23.35.0.5804
hpevtUtilitiesLedParamErrorA bad parameter was passed to the utilities function that manipulates the LED on replaceable parts. The offending parameter is displayed in the data field.
TRAP-TYPE
.1.3.6.1.4.1.11.2.23.35.0.5805
hpevtFabricUnexpectedNtypeA neighbor type read from a XBC PORT_NEIGHBOR_INFO CSR was different than the expected neighbor type. This event is emitted twice, first with expected data and second with actual data. Data field 1: XBC number (43:32), XBC port number (55:44), expected type (31:0) Data field 2: XBC number (43:32), XBC port number (55:44), actual neighbor type (31:0).
TRAP-TYPE
.1.3.6.1.4.1.11.2.23.35.0.5806
hpevtFabricPortNotCcA 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).
TRAP-TYPE
.1.3.6.1.4.1.11.2.23.35.0.5807
hpevtFabricPortNotXbcA 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).
TRAP-TYPE
.1.3.6.1.4.1.11.2.23.35.0.5808
hpevtFabricUnexpectedNChipThe 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).
TRAP-TYPE
.1.3.6.1.4.1.11.2.23.35.0.5809
hpevtFabricUnexpectedNPortThe 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).
TRAP-TYPE
.1.3.6.1.4.1.11.2.23.35.0.5810
hpevtBootNvmWriteToBmcTokenFailureA write to a BMC token has failed. This is a boot warning condition. Data: Upper 32 bits, BMC failure return code. Lower 32 bits, BMC token number that failed.
TRAP-TYPE
.1.3.6.1.4.1.11.2.23.35.0.5811
hpevtUtilitiesLedErrorThe utilities system reported an error while trying to carry out the command to turn on, flash or turn off the LED. The status returned by the command is displayed in the data field.
TRAP-TYPE
.1.3.6.1.4.1.11.2.23.35.0.5812
hpevtDuplicateCpuIds2 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.
TRAP-TYPE
.1.3.6.1.4.1.11.2.23.35.0.5813
hpevtHp-uxCrashdumpStartedOS crashdump started (D700)
TRAP-TYPE
.1.3.6.1.4.1.11.2.23.35.0.5823
hpevtHp-uxHexFaultCodeOS legacy PA hex fault code (Bxxx). Possible I/O error or system panic
TRAP-TYPE
.1.3.6.1.4.1.11.2.23.35.0.5824
hpevtHp-uxDumpStatusA memory dump occurred on the system, or on one partition in a cellular system. The dump occurred due to either a non-recoverable error or by user request. EFxx is the OS dump status (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.
TRAP-TYPE
.1.3.6.1.4.1.11.2.23.35.0.5825
hpevtSettingProcTimeoutFailSFW has failed to set the processor timeout value via a PAL call. Data: PAL call return value.
TRAP-TYPE
.1.3.6.1.4.1.11.2.23.35.0.5827
hpevtEfiSecInitVerifyErrDuring 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.
TRAP-TYPE
.1.3.6.1.4.1.11.2.23.35.0.5832
hpevtEfiSecInitCloseErrAs 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.
TRAP-TYPE
.1.3.6.1.4.1.11.2.23.35.0.5833
hpevtEfiSecInitOpenErrAs 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.
TRAP-TYPE
.1.3.6.1.4.1.11.2.23.35.0.5834
hpevtEfiSecInitWriteErrAs 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.
TRAP-TYPE
.1.3.6.1.4.1.11.2.23.35.0.5836
hpevtEfiSecInitWriteDeniedAs 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.
TRAP-TYPE
.1.3.6.1.4.1.11.2.23.35.0.5837
hpevtHp-uxDumpWriteErrorOS dump, error writing image area to disk (E055)
TRAP-TYPE
.1.3.6.1.4.1.11.2.23.35.0.5853
hpevtErrDeadlockResetDetectedEarly 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.
TRAP-TYPE
.1.3.6.1.4.1.11.2.23.35.0.5896
hpevtMemParityErrSFW detected a memory address parity error. The data field contains the physical location of DIMM that saw the parity error.
TRAP-TYPE
.1.3.6.1.4.1.11.2.23.35.0.6002
hpevtMemDimmLoadOrdErrThe loading order of the DIMMs is incorrect. The cell is halted.
TRAP-TYPE
.1.3.6.1.4.1.11.2.23.35.0.6074
hpevtMemRefreshStartErrorTimeout Waiting for SDRAM parts to become ready - mem_status[0] Refresh Control Register
TRAP-TYPE
.1.3.6.1.4.1.11.2.23.35.0.6146
hpevtMemExtBaseboardIncompatibleThe version of Memory extender installed in the system has not been qualified to work with the version of the baseboard installed in the system.
TRAP-TYPE
.1.3.6.1.4.1.11.2.23.35.0.6180
hpevtFabricDifferentTopologiesThere 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
TRAP-TYPE
.1.3.6.1.4.1.11.2.23.35.0.6730
hpevtFabricInvalidXbc2XbcPortWhile 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).
TRAP-TYPE
.1.3.6.1.4.1.11.2.23.35.0.6795
hpevtFabricGetNeighborInfoErrorThe XBC could not get neighbor information. Data Field: XBC # << 32 | internal port attempting to access neighbor
TRAP-TYPE
.1.3.6.1.4.1.11.2.23.35.0.7652
hpevtXbcRoutingErrorStateFor 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)
TRAP-TYPE
.1.3.6.1.4.1.11.2.23.35.0.7653
hpevtNoNvmErrLogSpaceThis 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.
TRAP-TYPE
.1.3.6.1.4.1.11.2.23.35.0.7655
hpevtXbcPortErrorAn 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)
TRAP-TYPE
.1.3.6.1.4.1.11.2.23.35.0.7657
hpevtXbcPortRouteAroundDuring 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)
TRAP-TYPE
.1.3.6.1.4.1.11.2.23.35.0.7658
hpevtXbcUnexpectedStateData field: the unexpected forward progress state (0:31) XBC number (32:44) Cell number (56:63)
TRAP-TYPE
.1.3.6.1.4.1.11.2.23.35.0.7660
hpevtXbcRoutingStateTimeoutA 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 field: unexpected forward progress (0:31) XBC number (32:44) Cell number (56:63)
TRAP-TYPE
.1.3.6.1.4.1.11.2.23.35.0.7661
hpevtXbcNeighborPortNotRoutableAn 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.
TRAP-TYPE
.1.3.6.1.4.1.11.2.23.35.0.7663
hpevtFabricCcToXbcErrorThe CC to XBC link is not viable.
TRAP-TYPE
.1.3.6.1.4.1.11.2.23.35.0.7664
hpevtFabricRouteXbcErrorThere 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)
TRAP-TYPE
.1.3.6.1.4.1.11.2.23.35.0.7666
hpevtXbcSemaphoreTakeoverFailedAfter unlocking the XBC Global Semaphore for a takeover, this cell did not get the semaphore.
TRAP-TYPE
.1.3.6.1.4.1.11.2.23.35.0.7669
hpevtXbcForceUnlockSm4TimeoutWhen 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)
TRAP-TYPE
.1.3.6.1.4.1.11.2.23.35.0.7671
hpevtXbcGetGlobalSm4TimeoutDuring 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.
TRAP-TYPE
.1.3.6.1.4.1.11.2.23.35.0.7673
hpevtXbcReleaseSm4TimeoutThe 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)
TRAP-TYPE
.1.3.6.1.4.1.11.2.23.35.0.7674
hpevtMpBatteryFailureManagement 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.
TRAP-TYPE
.1.3.6.1.4.1.11.2.23.35.0.7684
hpevtMpSoftwareErrorManagement Processor Firmware detected a software error and is logging an event. The data represents data associated with the error seen.
TRAP-TYPE
.1.3.6.1.4.1.11.2.23.35.0.7685
hpevtMpI2cCommErrorAn I2C Communication failure with the Baseboard Management Controller was detected. Without I2C communication, the system cannot be powered on/off or reset.
TRAP-TYPE
.1.3.6.1.4.1.11.2.23.35.0.7686
hpevtRomCrcErrorA stored CRC value did not match the calculated CRC value for the specified address.
TRAP-TYPE
.1.3.6.1.4.1.11.2.23.35.0.7690
hpevtIoIdentifyIoBpFailedSee Summary.
TRAP-TYPE
.1.3.6.1.4.1.11.2.23.35.0.7718
hpevtCpuRevisionMismatch2 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.
TRAP-TYPE
.1.3.6.1.4.1.11.2.23.35.0.7732
hpevtCpuFreqMismatchThis 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.
TRAP-TYPE
.1.3.6.1.4.1.11.2.23.35.0.7733
hpevtCpuOverclockedThe rating for the cpu and the actual speed will be emitted in 2 sequential event data fields.
TRAP-TYPE
.1.3.6.1.4.1.11.2.23.35.0.7734
hpevtCmplxProfilIncoherentThe 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.
TRAP-TYPE
.1.3.6.1.4.1.11.2.23.35.0.7758
hpevtDuplicateCabinetThe MP detected 2 or more cabinets with the same cabinet number.
TRAP-TYPE
.1.3.6.1.4.1.11.2.23.35.0.7760
hpevtIdCommandRequiredThe complex identification information in group A of the complex profile is invalid. The MP (Manageability Processor) command 'ID' must be run. The SSKEY hardware is required.
TRAP-TYPE
.1.3.6.1.4.1.11.2.23.35.0.7767
hpevtNvramBatteryFailThe battery on the SBCH is below the safe threshold. The battery can be replaced online.
TRAP-TYPE
.1.3.6.1.4.1.11.2.23.35.0.7771
hpevtPartitionTimeoutResetThe partition is being reset because its watchdog timer expired and automatic restart is enabled.
TRAP-TYPE
.1.3.6.1.4.1.11.2.23.35.0.7773
hpevtPdhcWatchdogTimedOutThe 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.
TRAP-TYPE
.1.3.6.1.4.1.11.2.23.35.0.7774
hpevtAbortPowerupOthThe Cabinet Power Up request was aborted due to ambient air over temperature.
TRAP-TYPE
.1.3.6.1.4.1.11.2.23.35.0.7781
hpevtAbortPwrupBpsThe power requirements for the cabinet exceeds the capabilities of the available Bulk Power Supplies. The PM3 section of the Utilities Subsystems keeps a tally of the power requirements for all installed entities in a cabinet. The power available from the Bulk Power Supplies does not meet the requirements of the installed entities, according to the Cabinet Power Tally.
TRAP-TYPE
.1.3.6.1.4.1.11.2.23.35.0.7782
hpevtAbortStartBlowrWhen given a power up request, the cabinet had to abort the start up due to less than the required number of Cabinet Blowers installed.
TRAP-TYPE
.1.3.6.1.4.1.11.2.23.35.0.7783
hpevtAbortStartIofanWhen given a power up request, the cabinet had to abort the start up due to less than the required number of IO fans present.
TRAP-TYPE
.1.3.6.1.4.1.11.2.23.35.0.7784
hpevtAcDeletedThe 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.
TRAP-TYPE
.1.3.6.1.4.1.11.2.23.35.0.7786
hpevtBlowrFailA 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.
TRAP-TYPE
.1.3.6.1.4.1.11.2.23.35.0.7791
hpevtBpsFail48fltA 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.
TRAP-TYPE
.1.3.6.1.4.1.11.2.23.35.0.7793
hpevtBpsFailFanfltThe designated Bulk Power Supply is reporting its fan has failed.
TRAP-TYPE
.1.3.6.1.4.1.11.2.23.35.0.7795
hpevtBpsFailOtThe 48 Volt DC Converter powered by the specified PDCA in the designated Bulk Power Supply, is in over temp condition. The PDCA powering the converter on the BPS that failed can be identified by the activity status (last byte of chassis code): e = PDCA 1 f = PDCA 0
TRAP-TYPE
.1.3.6.1.4.1.11.2.23.35.0.7796
hpevtBpsNotRedundantThe 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.
TRAP-TYPE
.1.3.6.1.4.1.11.2.23.35.0.7798
hpevtBpsOvervoltageThe PM has detected the value of +48V power, as measured on the UGUY board, has exceeded an upper threshold.
TRAP-TYPE
.1.3.6.1.4.1.11.2.23.35.0.7799
hpevtBpsUndervoltageThe PM has detected the value of +48V power, as measured on the UGUY board, has fallen below a lower threshold.
TRAP-TYPE
.1.3.6.1.4.1.11.2.23.35.0.7803
hpevtCabFanFailA 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.
TRAP-TYPE
.1.3.6.1.4.1.11.2.23.35.0.7806
hpevtHkpOvervoltageHousekeeping power has exceeded expected levels.
TRAP-TYPE
.1.3.6.1.4.1.11.2.23.35.0.7822
hpevtHkpUndervoltageHousekeeping power has fallen below expected levels.
TRAP-TYPE
.1.3.6.1.4.1.11.2.23.35.0.7823
hpevtIllegalBpsCfgOrPhaseFltThrough 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:
TRAP-TYPE
.1.3.6.1.4.1.11.2.23.35.0.7824
hpevtIllegalBpsidA 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.
TRAP-TYPE
.1.3.6.1.4.1.11.2.23.35.0.7825
hpevtInletOvertempHiThe 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.
TRAP-TYPE
.1.3.6.1.4.1.11.2.23.35.0.7827
hpevtInletOvertempLoThe 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.
TRAP-TYPE
.1.3.6.1.4.1.11.2.23.35.0.7828
hpevtInletOvertempMidThe 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..
TRAP-TYPE
.1.3.6.1.4.1.11.2.23.35.0.7829
hpevtIofanFailAn 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.
TRAP-TYPE
.1.3.6.1.4.1.11.2.23.35.0.7836
hpevtPowerOverloadThis 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.
TRAP-TYPE
.1.3.6.1.4.1.11.2.23.35.0.7842
hpevtShutdownBlowrAfter a BLOWR_FAIL, there were N-1 blowers functioning. This is an illegal condition causing immediate cabinet shutdown to prevent component damage.
TRAP-TYPE
.1.3.6.1.4.1.11.2.23.35.0.7845
hpevtShutdownIofanAfter a IOFAN_FAIL, there were N-1 fans functioning. This is an illegal condition causing immediate cabinet shutdown to prevent component damage.
TRAP-TYPE
.1.3.6.1.4.1.11.2.23.35.0.7846
hpevtXucFanFailOne of two fans in the Utility chassis of the IO Expansion Cabinet has failed.
TRAP-TYPE
.1.3.6.1.4.1.11.2.23.35.0.7849
hpevtCluWatchdogResetThe 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.
TRAP-TYPE
.1.3.6.1.4.1.11.2.23.35.0.7855
hpevtEepromInvalidCksmAn 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.
TRAP-TYPE
.1.3.6.1.4.1.11.2.23.35.0.7856
hpevtHbpbBoardPowerFaultOne 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.
TRAP-TYPE
.1.3.6.1.4.1.11.2.23.35.0.7858
hpevtHiobEepromRdFailAn attempt to read the EEPROM (FRUID) on the IO Backplane Board failed.
TRAP-TYPE
.1.3.6.1.4.1.11.2.23.35.0.7863
hpevtHiopbEepromRdFailAn attempt to read the EEPROM (FRUID) on the IO Backplane Power Board failed.
TRAP-TYPE
.1.3.6.1.4.1.11.2.23.35.0.7864
hpevtHiopbLpmFltRdFailAn attempt to read the Local Power Monitor Fault register on the IO Backplane Power Board failed.
TRAP-TYPE
.1.3.6.1.4.1.11.2.23.35.0.7865
hpevtHiopbOvertempThe Local Power Monitor of the named IO Chassis is reporting a Power Brick over temperature condition.
TRAP-TYPE
.1.3.6.1.4.1.11.2.23.35.0.7866
hpevtHiopbPowerFaultThe Local Power Monitor on the named IO Chassis has reported a power fault condition.
TRAP-TYPE
.1.3.6.1.4.1.11.2.23.35.0.7867
hpevtHiopbVoltMrgnFailThe Local Power Monitor on the named IO Power Board failed to properly margin the power as commanded.
TRAP-TYPE
.1.3.6.1.4.1.11.2.23.35.0.7871
hpevtSbchEepromRdFailEither 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.
TRAP-TYPE
.1.3.6.1.4.1.11.2.23.35.0.7873
hpevtUguyEepromRdFailEither 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.
TRAP-TYPE
.1.3.6.1.4.1.11.2.23.35.0.7874
hpevtSysBkpEepromRdFailAn attempt to read the EEPROM (FRUID) on the System Backplane failed
TRAP-TYPE
.1.3.6.1.4.1.11.2.23.35.0.7875
hpevtSysBkpI2cRdFailA read command on the system backplane I2C bus failed.
TRAP-TYPE
.1.3.6.1.4.1.11.2.23.35.0.7877
hpevtSysBkpI2cWrFailA 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
TRAP-TYPE
.1.3.6.1.4.1.11.2.23.35.0.7878
hpevtSysBkpPowerFaultThe 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).
TRAP-TYPE
.1.3.6.1.4.1.11.2.23.35.0.7879
hpevtSysBkpVoltMrgnFailMargining voltage to the System Backplane has failed.
TRAP-TYPE
.1.3.6.1.4.1.11.2.23.35.0.7880
hpevtWriteFruDataFailAn 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.
TRAP-TYPE
.1.3.6.1.4.1.11.2.23.35.0.7891
hpevtCpuFanFailThe fan on a CPU is not operating in a manner that provides enough air flow to cool the processor
TRAP-TYPE
.1.3.6.1.4.1.11.2.23.35.0.7892
hpevtCpuFanSlowThe fan on a CPU is operating in a manner that provides enough air flow to cool the processor but is not at normal operation
TRAP-TYPE
.1.3.6.1.4.1.11.2.23.35.0.7893
hpevtDnaFanFailThe fan on a CC chip is not operating in a manner that provides enough air flow to cool the processor
TRAP-TYPE
.1.3.6.1.4.1.11.2.23.35.0.7894
hpevtDnaFanSlowThe fan on a CC chip is operating in a manner that provides enough air flow to cool the processor but is not at normal operation
TRAP-TYPE
.1.3.6.1.4.1.11.2.23.35.0.7895
hpevtPdhcToSysfwRevMismtchSystem FW and the PDHC have incompatible shared memory interface revisions. Data byte 0 is the PDHC's supported ICM revision number. Data byte 1 is System FW's supported ICM revision number.
TRAP-TYPE
.1.3.6.1.4.1.11.2.23.35.0.7896
hpevtPdhCtrlrFwMismatchThe 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 qualed with. This is an unsupported configuration.
TRAP-TYPE
.1.3.6.1.4.1.11.2.23.35.0.7902
hpevtCellPowerFaultThe local Power Monitor is reporting a fault with the named Cell Power Board. The data field of this event can be decoded as follows where a bit set in any of the status fields indicates a fault: data byte 0: (power_good << 1) | (power_fault) data byte 1: Cell Power Board converters status bits[0:2] - memory power bricks 0-2 status bits[3:5] - power i/f bus bricks 0-2 status bits[6:7] - JAB core power bricks 0-1 status data byte 2: Cell converters status bit 0 - clock power status bit 1 - cache power status bit 2 - link power status bit 3 - CC core power status bit 4 - FSB power status bit 5 - 48-V status data byte 3: CPU module converters status bit 0 - CPU module 0 core power status bit 2 - CPU module 1 core power status bit 4 - CPU module 2 core power status bit 6 - CPU module 3 core power status
TRAP-TYPE
.1.3.6.1.4.1.11.2.23.35.0.7903
hpevtCpuInitNodeErrorThe CPU node retuned an error when calling its initialize node function. The specific status is displayed in the data field.
TRAP-TYPE
.1.3.6.1.4.1.11.2.23.35.0.7938
hpevtCpuExecuteCmdErrorExecuteCommand 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.
TRAP-TYPE
.1.3.6.1.4.1.11.2.23.35.0.7939
hpevtCpuCmdStateInvalidA 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.
TRAP-TYPE
.1.3.6.1.4.1.11.2.23.35.0.7940
hpevtCpuPalProcErrorAn 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.
TRAP-TYPE
.1.3.6.1.4.1.11.2.23.35.0.7948
hpevtBootCpuLoadingErrorCPUs not loaded in correct order. Correct loading order is CPU 0, 1, 2, 3.
TRAP-TYPE
.1.3.6.1.4.1.11.2.23.35.0.7953
hpevtXbcPersistantErrorThe 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)
TRAP-TYPE
.1.3.6.1.4.1.11.2.23.35.0.7963
hpevtXbcLinkTestErrorThe CC to XBC Link pattern test failed. Data Field: This event will be emitted three times 1st event: XBC number (32:43), port number (44:55) 2nd event: expected pattern (0:63) 3rd event: actual data read (0:63)
TRAP-TYPE
.1.3.6.1.4.1.11.2.23.35.0.7964
hpevtPltfrmStorageReadErrSystem firmware was unable to complete a platform storage read command from the utilities system. The exact status printed in the data field.
TRAP-TYPE
.1.3.6.1.4.1.11.2.23.35.0.7965
hpevtPltfrmStorageWriteErrSystem firmware was unable to complete a platform storage write command. The actual status is returned in the data field.
TRAP-TYPE
.1.3.6.1.4.1.11.2.23.35.0.7966
hpevtTreeNodeErrorSequencerThe 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.
TRAP-TYPE
.1.3.6.1.4.1.11.2.23.35.0.7973
hpevtPartitionVariableErrorSystem 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.
TRAP-TYPE
.1.3.6.1.4.1.11.2.23.35.0.7974
hpevtCellRedundtPowerFaultOne or more power converters 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 that is specific to each platform.
TRAP-TYPE
.1.3.6.1.4.1.11.2.23.35.0.7975
hpevtPalProcConfigIncompatibleCPUProcConfigValue setting in options as been compared with what is reported by PAL as settable and CPUProcConfigValue is specifying at least one bit that is not supported by this version of PAL using the Get Processor Dependent Features. This chassis code is emitted in pairs, the first data field contains the PAL expected values; the second data field contains the requested setting from options.
TRAP-TYPE
.1.3.6.1.4.1.11.2.23.35.0.8009
hpevtPalGetProcFeaturesFailedSystem firmware was unable to successfully issue the PAL_GET_PROC_FEATURES PAL proc. The data field is unused
TRAP-TYPE
.1.3.6.1.4.1.11.2.23.35.0.8010
hpevtPdhcCriticalDebugThis event is a tool to aid in the debugging and testing of firmware.
TRAP-TYPE
.1.3.6.1.4.1.11.2.23.35.0.8127
hpevtCluUndefinedCaseThe CLU has encountered an undefined case in its control flow.
TRAP-TYPE
.1.3.6.1.4.1.11.2.23.35.0.8128
hpevtCellVoltageMarginUnknThe Cell voltage margin settings do not match the Normal, +5%, or -5% values.
TRAP-TYPE
.1.3.6.1.4.1.11.2.23.35.0.8130
hpevtPdhcAssertionFailedFor debug purposes, many assumptions made by the PDHC developer(s) are checked at run-time. If this event log is seen, it indicates that the hardware or software is in an unknown state. 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.
TRAP-TYPE
.1.3.6.1.4.1.11.2.23.35.0.8131
hpevtPdhcFirmwareUnknownErrAn 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.
TRAP-TYPE
.1.3.6.1.4.1.11.2.23.35.0.8132
hpevtPdhcI2cWriteFailedAn 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).
TRAP-TYPE
.1.3.6.1.4.1.11.2.23.35.0.8133
hpevtPdhcI2cReadFailedAn 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).
TRAP-TYPE
.1.3.6.1.4.1.11.2.23.35.0.8134
hpevtPdhcSmbusWriteFailedAn 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).
TRAP-TYPE
.1.3.6.1.4.1.11.2.23.35.0.8135
hpevtPdhcSmbusReadFailedAn 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).
TRAP-TYPE
.1.3.6.1.4.1.11.2.23.35.0.8136
hpevtFrequencyProgramFailedThe 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.
TRAP-TYPE
.1.3.6.1.4.1.11.2.23.35.0.8137
hpevtSysFwFlashUpdateErrorAn error has occurred while updating System FW. More details about the update failure may be available as displayed by the Firmware Update Utility (FWUU).
TRAP-TYPE
.1.3.6.1.4.1.11.2.23.35.0.8138
hpevtPdhcUnexpectedResetThe PDHC firmware was reset for some unknown reason.
TRAP-TYPE
.1.3.6.1.4.1.11.2.23.35.0.8139
hpevtCpuTmpSensorSetupFailA 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.
TRAP-TYPE
.1.3.6.1.4.1.11.2.23.35.0.8140
hpevtCpuModuleThermalertA 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.
TRAP-TYPE
.1.3.6.1.4.1.11.2.23.35.0.8141
hpevtPdhcFlashUpdateErrorAn 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.
TRAP-TYPE
.1.3.6.1.4.1.11.2.23.35.0.8143
hpevtCellTypMismatchWSysfwThe 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.
TRAP-TYPE
.1.3.6.1.4.1.11.2.23.35.0.8147
hpevtPdhcPdhArbiterTimeoutThis event is emitted after the PDHC has waited longer than a maximum expected time for the PDH arbiter to grant it control of the PDH bus. The PDHC will continue waiting for control of the PDH bus until the arbiter grants it control, or the Cell is powered off using the MP's PE command. While waiting for the PDH bus, the PDHC will NOT perform its normal duties such as monitoring the Cell status, and passing messages from the system to the MP, and the PDHC heartbeat will not blink.
TRAP-TYPE
.1.3.6.1.4.1.11.2.23.35.0.8149
hpevtPdhcGetSm4TimeoutThis event is emitted after the PDHC has waited longer than a maximum expected time to obtain control of the PDH bus semaphore. The PDHC will continue waiting for control of the PDH bus semaphore until System FW relinquishes control of the semaphore, or the Cell is powered off using the MP's PE command. While waiting for the PDH bus semaphore, the PDHC will NOT perform its normal duties such as monitoring the Cell status, and passing messages from the system to the MP, and the PDHC heartbeat will not blink. The data field contains debug data that may be useful for developers. Data_byte[0] = last value read from PDHC's address for the microSemaphore register. Data_byte[1] = boolean indicator (1=set,0=not_set) of whether the PDHC's flag is set. Data_byte[2] = boolean indicator (1=set,0=not_set) of whether the System FW's flag is set.
TRAP-TYPE
.1.3.6.1.4.1.11.2.23.35.0.8151
hpevtIpmiBmc2hostMsgFailureThis 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.
TRAP-TYPE
.1.3.6.1.4.1.11.2.23.35.0.8153
hpevtEfiDebugLevelTokenErrEFI 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.
TRAP-TYPE
.1.3.6.1.4.1.11.2.23.35.0.8154
hpevtXbcPortNotLandminedA 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).
TRAP-TYPE
.1.3.6.1.4.1.11.2.23.35.0.8156
hpevtFabricValidateErrorThe 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
TRAP-TYPE
.1.3.6.1.4.1.11.2.23.35.0.8159
hpevtFabricISRInvalidBkpData 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
TRAP-TYPE
.1.3.6.1.4.1.11.2.23.35.0.8184
hpevtFabricXinWrZeroErrMaskErrorPrior 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
TRAP-TYPE
.1.3.6.1.4.1.11.2.23.35.0.8186
hpevtFabricCcPriModeRegRdStatusThe 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)
TRAP-TYPE
.1.3.6.1.4.1.11.2.23.35.0.8187
hpevtFabricCcPriModeRegRdDataThe Coherency Controller's (CC) XIN link did not initialize properly. The data field contains the data read from the CC Primary Error Mode CSR.
TRAP-TYPE
.1.3.6.1.4.1.11.2.23.35.0.8188
hpevtFabricCcErrMaskRegRdStatusThe 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)
TRAP-TYPE
.1.3.6.1.4.1.11.2.23.35.0.8189
hpevtFabricCcErrMaskRegRdDataThe Coherency Controller's (CC) XIN link did not initialize properly. The data field contains the data read from the CC Error Mask CSR.
TRAP-TYPE
.1.3.6.1.4.1.11.2.23.35.0.8190
hpevtFabricXingNeighborPortBadThe 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)
TRAP-TYPE
.1.3.6.1.4.1.11.2.23.35.0.8194
hpevtFabricISRRdFwdProgErrFabric read error. Data field: (XBC number << 32 | return status)
TRAP-TYPE
.1.3.6.1.4.1.11.2.23.35.0.8195
hpevtFabricGetNeighborMaxLinksBrokenToo many crossbar links are broken. Cell cannot boot, halting. Data field: XBC number << 32
TRAP-TYPE
.1.3.6.1.4.1.11.2.23.35.0.8198
hpevtPmAssertionFailedFor 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.
TRAP-TYPE
.1.3.6.1.4.1.11.2.23.35.0.8199
hpevtPmFirmwareUnknownErrAn 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.
TRAP-TYPE
.1.3.6.1.4.1.11.2.23.35.0.8200
hpevtPmCriticalDebugThis event is a tool to aid in the debugging and testing of firmware.
TRAP-TYPE
.1.3.6.1.4.1.11.2.23.35.0.8202
hpevtFabricLinkCorErrTestFailureFailed 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)
TRAP-TYPE
.1.3.6.1.4.1.11.2.23.35.0.8205
hpevtInvalidCabinetNumberThe data field contains the cabinet number that is invalid
TRAP-TYPE
.1.3.6.1.4.1.11.2.23.35.0.8206
hpevtPdIncompatibleFwRevsThe 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.
TRAP-TYPE
.1.3.6.1.4.1.11.2.23.35.0.8207
hpevtPmI2cWriteFailedAn 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).
TRAP-TYPE
.1.3.6.1.4.1.11.2.23.35.0.8212
hpevtPmI2cReadFailedAn attempt to read from a device on the PM's I2C bus has failed. This event is only emitted when the PM is reading a BPS's. 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 (to convert to BPS slot number subtract 1 and divide by 2) Data Bytes[4-5]: Starting Word Address Data Bytes[6-7]: Size of attempted access (in bytes).
TRAP-TYPE
.1.3.6.1.4.1.11.2.23.35.0.8214
hpevtCellInfoErrorAn 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.
TRAP-TYPE
.1.3.6.1.4.1.11.2.23.35.0.8216
hpevtSlaveConsoleSetupErrorAn error was encountered establishing the slave cells use of the diva console.
TRAP-TYPE
.1.3.6.1.4.1.11.2.23.35.0.8218
hpevtRegistryMoveToCoreCellErrorAn error was encountered trying to relocate the registry on a slave cell to point to the core cells main memory structures.
TRAP-TYPE
.1.3.6.1.4.1.11.2.23.35.0.8219
hpevtProfileGroupCCrcErrorThe Calculated CRC for the group C Partition Profile did not match the stored value. The expected value and the actual value will be emitted in 2 sequential chassis codes.
TRAP-TYPE
.1.3.6.1.4.1.11.2.23.35.0.8220
hpevtMcCoreCellSelectFailNot able to find a core cell in the PD during a global MCA error processing.
TRAP-TYPE
.1.3.6.1.4.1.11.2.23.35.0.8238
hpevtFabricAssertFabricUtilsAn unexpected error occurred while initializing the fabric. The firmware is not able to analyze this error. Clues to the cause of this error may be found in the IPMI forward progress log (FPL) either shortly before or after this log entry occurred. The FPL is available from the management processor using the 'sl' command. HP-UX also saves these logs in the /var/stm/logs/os directory, and they can be viewed using the slview utility.
TRAP-TYPE
.1.3.6.1.4.1.11.2.23.35.0.8239
hpevtSalPmiFwErrorAn 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.
TRAP-TYPE
.1.3.6.1.4.1.11.2.23.35.0.8240
hpevtOlaWrongNumberCellsDuring 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.
TRAP-TYPE
.1.3.6.1.4.1.11.2.23.35.0.8243
hpevtFabricXbcRouteSourceCellPortErrAn error occurred while reading the routing from the source cell's port on the source XBC. Data Field: (source cell << 56 | source XBC << 32)
TRAP-TYPE
.1.3.6.1.4.1.11.2.23.35.0.8257
hpevtBootOlaCellIncompatibleOLA cell cannot be added because it has resources that are not compatible with those already in the partition. Data field specifies the physical location of the cell which is incompatible and on which the OLA was attempted. The preceding chassis code or codes should already have been emitted specifying what the actual incompatibility was. The OLA cell will NOT be added to the partition, and the existing partition should not be affected.
TRAP-TYPE
.1.3.6.1.4.1.11.2.23.35.0.8261
hpevtBootOlaCellDidNotReachRendezvousRoot Cell attempted to OLA a cell which hung somewhere in the OLA process - the cell released from BIB but never made it to its final rendezvous state. Data field contains physical location of the hung OLA cell. The OLA cell will NOT be added to the partition, and the existing partition should not be affected.
TRAP-TYPE
.1.3.6.1.4.1.11.2.23.35.0.8263
hpevtBootOlaCellStillAtBibRoot cell attempted to OLA a cell that was never released from BIB. Data field contains the physical location of the cell that is being OLAD.
TRAP-TYPE
.1.3.6.1.4.1.11.2.23.35.0.8264
hpevtBootOlaCellUnexpectedCellStatePartition attempted to OLA a cell in an unexpected Cell state. Data Field contains the unexpected cell state of the OLA cell. The OLA cell will NOT be added to the partition, and the existing partition should not be affected.
TRAP-TYPE
.1.3.6.1.4.1.11.2.23.35.0.8265
hpevtBootOlaCellCantReachAliveCellsRoot cell will emit this chassis code indicating the OLA cell could reach all cells in the alive set of the existing partition. Data field will contain the physical location of the OLA cell. This chassis code should immediately follow a chassis code indicating exactly which cell the OLA cell could not reach. The OLA cell will not be added to the partition and the partition will be unaffected.
TRAP-TYPE
.1.3.6.1.4.1.11.2.23.35.0.8267
hpevtBootMixedCpuCoreFreqInstalledCPU's of mixed maximum core frequencies are installed
TRAP-TYPE
.1.3.6.1.4.1.11.2.23.35.0.8269
hpevtXinInitIntermittentFailureThe Cell Controller-XBC link initialization is having an intermittent failure. The data field contains the number of initialization sequences that failed before being successful.
TRAP-TYPE
.1.3.6.1.4.1.11.2.23.35.0.8271
hpevtPdhErrClearOlaSteeringBitPDC failed clearing the OLA steering bit in the PDH FPGA 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.
TRAP-TYPE
.1.3.6.1.4.1.11.2.23.35.0.8643
hpevtBootOlaFailedUpdatePdAddrMapThe attempt to update the PD Addr Map to include OLA cell failed.
TRAP-TYPE
.1.3.6.1.4.1.11.2.23.35.0.8645
hpevtBootOlaFailedUpdatePdPdtAttempt to update the partition PDT with OLA cell PDT data has failed.
TRAP-TYPE
.1.3.6.1.4.1.11.2.23.35.0.8646
hpevtBootOlaFailedUpdateCellMapAttempt to update the cell map to include the OLA Cell failed
TRAP-TYPE
.1.3.6.1.4.1.11.2.23.35.0.8647
hpevtFabricCc2XbcLinkInitFailedFabric 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
TRAP-TYPE
.1.3.6.1.4.1.11.2.23.35.0.8648
hpevtFwVirtualMappingErrorAn 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
TRAP-TYPE
.1.3.6.1.4.1.11.2.23.35.0.8652
hpevtFabricXinInitWriteErrFailure while writing the XBC CSR containing the link status
TRAP-TYPE
.1.3.6.1.4.1.11.2.23.35.0.8676
hpevtFabricXinInitReadErrFailure while reading the XBC CSR containing the link status
TRAP-TYPE
.1.3.6.1.4.1.11.2.23.35.0.8677
hpevtFabricLinkInitIntermittentFailureFabric Discovery's attempt to initialize the local cell's CC to XBC link has failed. The link initialization sequence has an intermittent problem.
TRAP-TYPE
.1.3.6.1.4.1.11.2.23.35.0.8679
hpevtIodiscPciInitnodeErrorAn error was encountered while attempting to create and initialize a PCI device node
TRAP-TYPE
.1.3.6.1.4.1.11.2.23.35.0.8690
hpevtIodiscPciBusscanErrorAn error was encountered while scanning the PCI bus
TRAP-TYPE
.1.3.6.1.4.1.11.2.23.35.0.8691
hpevtIodiscPciInitbridgeErrorAn error was encountered while attempting to initialize a P2P bridge
TRAP-TYPE
.1.3.6.1.4.1.11.2.23.35.0.8692
hpevtIodiscPciIomapErrorInsufficient IO Port space to support the PCI card
TRAP-TYPE
.1.3.6.1.4.1.11.2.23.35.0.8693
hpevtIodiscPciMmiomapErrorInsufficient MMIO space to support the PCI card requirements
TRAP-TYPE
.1.3.6.1.4.1.11.2.23.35.0.8694
hpevtIodiscSbaInitnodeErrorAn error was encountered while attempting to initialize the SBA node
TRAP-TYPE
.1.3.6.1.4.1.11.2.23.35.0.8709
hpevtIodiscSbaDiscoverErrorAn error was encountered while attempting to discover SBA hardware
TRAP-TYPE
.1.3.6.1.4.1.11.2.23.35.0.8710
hpevtIodiscSbaResetErrorAn error was encountered while attempting to reset the SBA
TRAP-TYPE
.1.3.6.1.4.1.11.2.23.35.0.8711
hpevtIodiscIolinkErrorAn error was detected in the link between the CC and the I/O controller.
TRAP-TYPE
.1.3.6.1.4.1.11.2.23.35.0.8712
hpevtIodiscCableErrorAn SBA cable error has been detected
TRAP-TYPE
.1.3.6.1.4.1.11.2.23.35.0.8713
hpevtIodiscIoChassisPowerIdentified the cell number that is connected to the chassis.
TRAP-TYPE
.1.3.6.1.4.1.11.2.23.35.0.8714
hpevtIodiscLbaInitnodeErrorAn error occurred while attempting to create or initialize an LBA node
TRAP-TYPE
.1.3.6.1.4.1.11.2.23.35.0.8715
hpevtIodiscLbaWidthErrorAn error was encountered while attempting to configure LBA rope bundling width
TRAP-TYPE
.1.3.6.1.4.1.11.2.23.35.0.8716
hpevtIodiscLbaPhaseErrorerror code
TRAP-TYPE
.1.3.6.1.4.1.11.2.23.35.0.8717
hpevtIodiscLbaClearErrorAn error occurred while attempting to clear an LBA error log register
TRAP-TYPE
.1.3.6.1.4.1.11.2.23.35.0.8718
hpevtIodiscLbaLogErrorAn error was encountered while attempting to generate LBA error logs
TRAP-TYPE
.1.3.6.1.4.1.11.2.23.35.0.8719
hpevtIodiscLbaDiscoverErrorAn error was encountered while attempting to discover LBA hardware
TRAP-TYPE
.1.3.6.1.4.1.11.2.23.35.0.8720
hpevtIodiscLbaConfigErrorAn error occurred while attempting to configure the LBA hardware
TRAP-TYPE
.1.3.6.1.4.1.11.2.23.35.0.8721
hpevtIodiscLbaPciscanErrorAn error was encountered while attempting to scan the PCI bus
TRAP-TYPE
.1.3.6.1.4.1.11.2.23.35.0.8722
hpevtIodiscLbaPciconfigErrorAn error was encountered while attempting to configure PCI config space
TRAP-TYPE
.1.3.6.1.4.1.11.2.23.35.0.8723
hpevtBootOlaCellErrAccessCmplxProfileThe OLA cell failed accessing the complex profile. Cell will send Failed to OLA message back to partition and then reboot itself. Existing partition will not be affected.
TRAP-TYPE
.1.3.6.1.4.1.11.2.23.35.0.8745
hpevtBootFwRelocMemErrA Firmware tries to find a main memory block large enough meeting alignment requirements.
TRAP-TYPE
.1.3.6.1.4.1.11.2.23.35.0.8747
hpevtBootOlaCellNotConfigInCmplxProfileCell started OLA but is not configured in the complex profile of the partition. Cell will reboot to SINC_BIB. Existing partition will not be affected.
TRAP-TYPE
.1.3.6.1.4.1.11.2.23.35.0.8752
hpevtOptsNvmAllocErrorThe 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.
TRAP-TYPE
.1.3.6.1.4.1.11.2.23.35.0.8756
hpevtBootOlaUpdateRtcFailedOlaCellA failure occurred on the OLA cell during the attempt to synchronize its real time clock with the clock(s) in the existing partition. Data field contains physical location of OLA cell.
TRAP-TYPE
.1.3.6.1.4.1.11.2.23.35.0.8757
hpevtSalInfoTimeoutAccess 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.
TRAP-TYPE
.1.3.6.1.4.1.11.2.23.35.0.8758
hpevtPdhIprNotClearedOnCellThe PDH FPGA IPR is not cleared after a MAX_RD_CLR_IPR_TRIES on a cell. The Data Filed in the Cell number. See the next Chassis Code to see the MAX_RD_CLR_IPR_TRIES
TRAP-TYPE
.1.3.6.1.4.1.11.2.23.35.0.8761
hpevtPdhIprClearAttemptsIndicated the PDH FPGA IPR is not cleared after a number of PDC attempts. The Data Field contents the MAX_RD_CLR_IPR_TRIES. Please look at the previous Chassis Code to see the Cell number.
TRAP-TYPE
.1.3.6.1.4.1.11.2.23.35.0.8762
hpevtBootOlaUpdateRtcFailedExistingCellattempt to synchronize the Real-Time Clock of the OLA cell with the existing partition failed because the RTC on the core cell could not be read.
TRAP-TYPE
.1.3.6.1.4.1.11.2.23.35.0.8763
hpevtMemIncompleteEchelonOne 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.
TRAP-TYPE
.1.3.6.1.4.1.11.2.23.35.0.8768
hpevtFabricRdPortStatePortInvalidThe 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)
TRAP-TYPE
.1.3.6.1.4.1.11.2.23.35.0.8771
hpevtFabricWrPortStatePortInvalidThe 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)
TRAP-TYPE
.1.3.6.1.4.1.11.2.23.35.0.8772
hpevtMainBpLpmFltThe main backplane is reporting the LPM status as fault.
TRAP-TYPE
.1.3.6.1.4.1.11.2.23.35.0.8784
hpevtIoBpLpmFltThe IO backplane has reported a local power monitor fault.
TRAP-TYPE
.1.3.6.1.4.1.11.2.23.35.0.8787
hpevtCmplxProfileInitFailedSystem firmware was unable to default the complex profile
TRAP-TYPE
.1.3.6.1.4.1.11.2.23.35.0.8797
hpevtPalSetProcFeaturesFailedFirmware call to set processor feature resulted in an error.
TRAP-TYPE
.1.3.6.1.4.1.11.2.23.35.0.8798
hpevtActiveLogNotFoundThis 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
TRAP-TYPE
.1.3.6.1.4.1.11.2.23.35.0.8806
hpevtReachedMaxErrorLogsThis 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.
TRAP-TYPE
.1.3.6.1.4.1.11.2.23.35.0.8807
hpevtOldNoCellToDeleteSystem firmware has been invoked to perform a cell delete operation but no cell in the system appears to be ready for deletion.
TRAP-TYPE
.1.3.6.1.4.1.11.2.23.35.0.8814
hpevtBpsOvercurrentThe bulk power supply is overcurrent
TRAP-TYPE
.1.3.6.1.4.1.11.2.23.35.0.8817
hpevtBpsWarnOtData: Bulk location.
TRAP-TYPE
.1.3.6.1.4.1.11.2.23.35.0.8818
hpevtErmOutOfHeapError Response Mode code attempted a malloc of heap space that failed.
TRAP-TYPE
.1.3.6.1.4.1.11.2.23.35.0.8819
hpevtMemDimmUnsupportedThe 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.
TRAP-TYPE
.1.3.6.1.4.1.11.2.23.35.0.8821
hpevtOptsMallocErrorThe 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.
TRAP-TYPE
.1.3.6.1.4.1.11.2.23.35.0.8828
hpevtCellHwDegradedA 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.
TRAP-TYPE
.1.3.6.1.4.1.11.2.23.35.0.8837
hpevtNotIntegratingCellA 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. The data field is unused, but the cell that emitted this event is the one that did not get integrated.
TRAP-TYPE
.1.3.6.1.4.1.11.2.23.35.0.8839
hpevtIoContextCorruptErrThe IO error context is corrupt. This will impair IO error reporting.
TRAP-TYPE
.1.3.6.1.4.1.11.2.23.35.0.8842
hpevtIoRopeFatalA rope went fatal from the SBA to the LBA. If all the ropes go fatal the IO subsystem is dead. Any I/O below the rope will not be accessible. The data field gives the physical location of the rope that went fatal. Some ROPE_FATAL conditions will not cause the system to go down. For Example, a rope that has gone fatal during an OLAR operation will only cause warnings to the user, not bring the partition down.
TRAP-TYPE
.1.3.6.1.4.1.11.2.23.35.0.8843
hpevtIoBusFatalA PCI bus on the system is fatal. Any device on this bus is unavailable. Firmware was unable to complete card initialization due to an error. Data field contains physical location of failed bus.
TRAP-TYPE
.1.3.6.1.4.1.11.2.23.35.0.8844
hpevtIoRopeUnitFatalOne of the rope units in the SBA failed. If all of the rope units fail, then IO will not be available on this cell.
TRAP-TYPE
.1.3.6.1.4.1.11.2.23.35.0.8845
hpevtPdhFlashWriteEnableBitSetNowClearedThe 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.
TRAP-TYPE
.1.3.6.1.4.1.11.2.23.35.0.8851
hpevtFirmwareInitErrorSystem 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.
TRAP-TYPE
.1.3.6.1.4.1.11.2.23.35.0.8855
hpevtMcIncompleteCpuSetThis means that all the cpus in the cell did not show up.
TRAP-TYPE
.1.3.6.1.4.1.11.2.23.35.0.8857
hpevtMcIncompleteCellSetThis 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.
TRAP-TYPE
.1.3.6.1.4.1.11.2.23.35.0.8858
hpevtMcTreeCheckFailedThe FW tree sanity check failed during the MCA error processing.
TRAP-TYPE
.1.3.6.1.4.1.11.2.23.35.0.8859
hpevtMcRegistryCheckFailedThis means that the registry sanity check failed during MCA error handling.
TRAP-TYPE
.1.3.6.1.4.1.11.2.23.35.0.8860
hpevtMcDuringOsMcaThis means that MCA occurred while OS_MCA was performing error recovery.
TRAP-TYPE
.1.3.6.1.4.1.11.2.23.35.0.8861
hpevtMcMemDumpAbandonThis 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 Cell Controller occurs.
TRAP-TYPE
.1.3.6.1.4.1.11.2.23.35.0.8864
hpevtMcFwTreeNotCompleteThe firmware tree is not complete and hence there will be no PD rendezvous.
TRAP-TYPE
.1.3.6.1.4.1.11.2.23.35.0.8865
hpevtAcpiConfigMismatchThe firmware parameter that defines the ACPI configuration is inconsistent in at least one of the cells in the partition.
TRAP-TYPE
.1.3.6.1.4.1.11.2.23.35.0.8872
hpevtFabricXinErrOrderStatusClrFailedWriting the XIN_ERR_ORDER_STATUS register of the CC failed. This is some sort of a hardware failure. Data Field: return status
TRAP-TYPE
.1.3.6.1.4.1.11.2.23.35.0.8873
hpevtFabricAssertFabricInitAn unexpected error occurred while initializing the fabric. The firmware is not able to analyze this error. Clues to the cause of this error may be found in the IPMI forward progress log (FPL) either shortly before or after this log entry occurred. The FPL is available from the management processor using the 'sl' command. HP-UX also saves these logs in the /var/stm/logs/os directory, and they can be viewed using the slview utility.
TRAP-TYPE
.1.3.6.1.4.1.11.2.23.35.0.8876
hpevtInvalidPiromDataA value read by the PDHC from a CPU module's Processor Information ROM was not within acceptable limits.
TRAP-TYPE
.1.3.6.1.4.1.11.2.23.35.0.8877
hpevtSettingFreqRatiosErrorAn invalid parameter was specified when trying to set the cpu bus config register, cpu frequencies ratio field. Valid range is 0xe - 0x17
TRAP-TYPE
.1.3.6.1.4.1.11.2.23.35.0.8882
hpevtOptsBlockCksumErrorThe overhead structure of the OPTIONS block in NVRAM has a checksum error.
TRAP-TYPE
.1.3.6.1.4.1.11.2.23.35.0.8883
hpevtFabricColaLocalCcLinkNotInitDuring a cell OLA, the link on the local cell failed to initialize. Data Field: (my cell << 32) | XIN Link State
TRAP-TYPE
.1.3.6.1.4.1.11.2.23.35.0.8894
hpevtFabricXinInitDisableWrErrorAn attempt to disable the fabric link failed because writing the CC CSR failed. Data Field: (cell << 56) | return status
TRAP-TYPE
.1.3.6.1.4.1.11.2.23.35.0.8895
hpevtFabricXinErrMaskUnknownBkpCould not determine the system type in order to write the appropriate error mask for the fabric link. Data Field: system type
TRAP-TYPE
.1.3.6.1.4.1.11.2.23.35.0.8896
hpevtFabricXinWrErrMaskErrorFailed writing the XIN error mask for CC's fabric link. Data Field: (cell << 56) | return status
TRAP-TYPE
.1.3.6.1.4.1.11.2.23.35.0.8897
hpevtFabricXinRdErrMaskErrorCould not read the XIN Link error mask register. Data Field: (cell << 56) | return status
TRAP-TYPE
.1.3.6.1.4.1.11.2.23.35.0.8898
hpevtFabricInitCcLinkFailureThe CC to CC link initialization sequence has failed. Data Field: link init status
TRAP-TYPE
.1.3.6.1.4.1.11.2.23.35.0.8900
hpevtResetCommandErrorAn error occurred while trying to notify the MP that a reset is about to occur (QPartitionReleaseBIB command). The status is in the data field.
TRAP-TYPE
.1.3.6.1.4.1.11.2.23.35.0.8906
hpevtFabricInitCcLinkDisableErrA 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
TRAP-TYPE
.1.3.6.1.4.1.11.2.23.35.0.8926
hpevtFabricSetPortStateGetSm4ErrWhile 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)
TRAP-TYPE
.1.3.6.1.4.1.11.2.23.35.0.8930
hpevtFabricSetPortStateRlsSm4ErrWhile 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)
TRAP-TYPE
.1.3.6.1.4.1.11.2.23.35.0.8931
hpevtFabricAssertFabricErrAn unexpected error occurred while initializing the fabric. The firmware is not able to analyze this error. Clues to the cause of this error may be found in the IPMI forward progress log (FPL) either shortly before or after this log entry occurred. The FPL is available from the management processor using the 'sl' command. HP-UX also saves these logs in the /var/stm/logs/os directory, and they can be viewed using the slview utility.
TRAP-TYPE
.1.3.6.1.4.1.11.2.23.35.0.8936
hpevtFabricXinLinkAlreadyInitWhile 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.
TRAP-TYPE
.1.3.6.1.4.1.11.2.23.35.0.8939
hpevtNoCpuModulesFoundByPdhcThe PDHC FW could not detect any CPU modules on its Cell board, so it is holding the Cell in reset.
TRAP-TYPE
.1.3.6.1.4.1.11.2.23.35.0.8940
hpevtCpuModCompatMismatchThe 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.
TRAP-TYPE
.1.3.6.1.4.1.11.2.23.35.0.8941
hpevtBadCpuModScratchCksumThe 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.
TRAP-TYPE
.1.3.6.1.4.1.11.2.23.35.0.8942
hpevtPdhBatteryLowWarningThe battery voltage level is low for the cell. This indicates that the NVRAM will not be saved if the power is removed.
TRAP-TYPE
.1.3.6.1.4.1.11.2.23.35.0.8954
hpevtFabricRouteXbcCopyRoutingErrThere 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
TRAP-TYPE
.1.3.6.1.4.1.11.2.23.35.0.8959
hpevtFabricCopyRdBackFailedThe read immediately after a write while copying routing registers failed. Data: whether or not the XBC Key was enabled
TRAP-TYPE
.1.3.6.1.4.1.11.2.23.35.0.8960
hpevtFabricRtgCompleteSm4RlsErrFailed to release a XBC Semaphore while marking each XBC in the complex to indicate that routing has completed. Data: (XBC num << 32) | return value
TRAP-TYPE
.1.3.6.1.4.1.11.2.23.35.0.8962
hpevtFabricRtgCompleteWrFwdPrgErrWriting this XBC's forward progress register failed. Data: (XBC num << 32) | return value
TRAP-TYPE
.1.3.6.1.4.1.11.2.23.35.0.8964
hpevtFabricRtgCompleteSm4AccessErrFailed 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
TRAP-TYPE
.1.3.6.1.4.1.11.2.23.35.0.8965
hpevtFabricRtgCompleteTopologyErrReading this XBC's topology register failed. Data Field: (xbc num << 32) | return status
TRAP-TYPE
.1.3.6.1.4.1.11.2.23.35.0.8966
hpevtFabricRouteTraversableCc2CcErrCould not check the traversability between two cells on an XBCless platform. Data field: return status (1 = SUCCESS, 0 = FALSE, -1 = FAILURE)
TRAP-TYPE
.1.3.6.1.4.1.11.2.23.35.0.8968
hpevtFabricDataRouteTraversableCc2CcErrCould not check the traversability between two cells on an XBCless platform. Data field: return status (1 = SUCCESS, 0 = FALSE, -1 = FAILURE)
TRAP-TYPE
.1.3.6.1.4.1.11.2.23.35.0.8969
hpevtFabricCc2ccTraverseLclXinRdErrWhile 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)
TRAP-TYPE
.1.3.6.1.4.1.11.2.23.35.0.8970
hpevtFabricCc2ccTraverseRmtXinRdErrWhile 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)
TRAP-TYPE
.1.3.6.1.4.1.11.2.23.35.0.8971
hpevtFabricCc2ccTraverseLclNotInitCould 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
TRAP-TYPE
.1.3.6.1.4.1.11.2.23.35.0.8972
hpevtFabricCc2ccTraverseRmtNotInitCould 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
TRAP-TYPE
.1.3.6.1.4.1.11.2.23.35.0.8973
hpevtFabricDisableXinLinkReadErrError 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.
TRAP-TYPE
.1.3.6.1.4.1.11.2.23.35.0.8974
hpevtFabricXinInitRetryReadErrFailure 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
TRAP-TYPE
.1.3.6.1.4.1.11.2.23.35.0.8975
hpevtFabricAssertFabricCcAn unexpected error occurred while initializing the fabric. The firmware is not able to analyze this error. Clues to the cause of this error may be found in the IPMI forward progress log (FPL) either shortly before or after this log entry occurred. The FPL is available from the management processor using the 'sl' command. HP-UX also saves these logs in the /var/stm/logs/os directory, and they can be viewed using the slview utility.
TRAP-TYPE
.1.3.6.1.4.1.11.2.23.35.0.8976
hpevtCpuRestrictedThe CPU that just completed self tests is functionally or performance restricted. The data field contains the Self Test State Parameter. The 2-bit state field (bits 1..0) can have the following values when this event is displayed: 01 - Performance Restricted - cpu still functions 10 - Functionally Restricted - cpu doesn't function properly
TRAP-TYPE
.1.3.6.1.4.1.11.2.23.35.0.8979
hpevtPdhInvalidRtcClearedThe RTC was found to be invalid and has been cleared
TRAP-TYPE
.1.3.6.1.4.1.11.2.23.35.0.8981
hpevtLstNotRunSystem 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.
TRAP-TYPE
.1.3.6.1.4.1.11.2.23.35.0.8982
hpevtBootSetCellStateFabricFailureAn attempt to update the cell state has failed due to a fabric crossbar failure. The cell number being updated in bits 63:56, while the traversable cell set (those cells connected to the fabric) is returned in bits 31:0
TRAP-TYPE
.1.3.6.1.4.1.11.2.23.35.0.8983
hpevtBootResetCellStateFailureFailed 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.
TRAP-TYPE
.1.3.6.1.4.1.11.2.23.35.0.8984
hpevtMemChipspareDeallocRankSFW 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.
TRAP-TYPE
.1.3.6.1.4.1.11.2.23.35.0.9000
hpevtClockFreqErrorInternal 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.
TRAP-TYPE
.1.3.6.1.4.1.11.2.23.35.0.9019
hpevtFabricColaInitTraversableErrCould not traverse the fabric to the cell being added. Data field: (chosen cell << 56) | return status, where -1 = failure
TRAP-TYPE
.1.3.6.1.4.1.11.2.23.35.0.9020
hpevtFabricAttemptFocusedRerouteA 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.
TRAP-TYPE
.1.3.6.1.4.1.11.2.23.35.0.9021
hpevtFabricCellRerouteNinfoErrError getting the XBC port's expected neighbor from a firmware table. Data field: 0 (SUCCESS) or -1 (FAILURE)
TRAP-TYPE
.1.3.6.1.4.1.11.2.23.35.0.9022
hpevtBootWakeCpuIsCpuDeconfigErrEither 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().
TRAP-TYPE
.1.3.6.1.4.1.11.2.23.35.0.9038
hpevtBootWakeCpuGetCountersErrEither 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().
TRAP-TYPE
.1.3.6.1.4.1.11.2.23.35.0.9039
hpevtBootWakeCpuGetStructAddrErrEither 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().
TRAP-TYPE
.1.3.6.1.4.1.11.2.23.35.0.9040
hpevtBootCheckCpu4CompletionErrEither 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().
TRAP-TYPE
.1.3.6.1.4.1.11.2.23.35.0.9041
hpevtBootCheckCpuGetStructAddrErrEither 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().
TRAP-TYPE
.1.3.6.1.4.1.11.2.23.35.0.9042
hpevtReconfigResetScheduledThere 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.
TRAP-TYPE
.1.3.6.1.4.1.11.2.23.35.0.9043
hpevtProfileWrongArchTypeWhen processing the complex profile, the an unexpected 'Architecture Type' was specified in the PA/IA Arch field. The actual data found is displayed.
TRAP-TYPE
.1.3.6.1.4.1.11.2.23.35.0.9045
hpevtBootCheckCpuIsDeconfigErrWhile 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().
TRAP-TYPE
.1.3.6.1.4.1.11.2.23.35.0.9046
hpevtBootCheckCpuGetCountersErrWhile 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().
TRAP-TYPE
.1.3.6.1.4.1.11.2.23.35.0.9047
hpevtBootPdMonarchRtnFromSwSetFpErrWhile trying to determine whether or not a particular processor has completed the task for which it was awakened, PDC was unable to access the CPU's forward progress state (i.e. PST state) for the target processor. A processor should always be able to access this data in PDH memory for any processor on its own cell and for any processor on a cell that is alive in the partition. Therefore, PDC is either going to halt the cell or reset the partition because of this problem. The data field contains the PDC error return status from CpuFpSet().
TRAP-TYPE
.1.3.6.1.4.1.11.2.23.35.0.9049
hpevtBootSlaveRtnFromFwSetFpErrWhile trying to determine whether or not a particular processor has completed the task for which it was awakened, PDC was unable to access the CPU's Forward Progress State (i.e. PST state) for the target processor. A processor should always be able to access this data in PDH memory for any processor on its own cell and for any processor on a cell that is alive in the partition. Therefore, PDC is either going to halt the cell or reset the partition because of this problem. The data field contains the PDC error return status from CpuFpSet().
TRAP-TYPE
.1.3.6.1.4.1.11.2.23.35.0.9051
hpevtBootProblemBranchingToPgzLocationAt 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.
TRAP-TYPE
.1.3.6.1.4.1.11.2.23.35.0.9052
hpevtBootBadCpuOrderThe Data Field contains the value used to determine a valid order.
TRAP-TYPE
.1.3.6.1.4.1.11.2.23.35.0.9084
hpevtBootSlpWakeCntrsStructAddrErrWhile 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().
TRAP-TYPE
.1.3.6.1.4.1.11.2.23.35.0.9364
hpevtBootGetSleepTimeoutStructAddrErrError 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.
TRAP-TYPE
.1.3.6.1.4.1.11.2.23.35.0.9365
hpevtBootMoveSlavesDispatcherAddrErrPDC 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().
TRAP-TYPE
.1.3.6.1.4.1.11.2.23.35.0.9367
hpevtBootMoveSlavesCheckSlaveErrPDC 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.
TRAP-TYPE
.1.3.6.1.4.1.11.2.23.35.0.9368
hpevtBootMoveSlavesFpSetAddrErrPDC 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().
TRAP-TYPE
.1.3.6.1.4.1.11.2.23.35.0.9370
hpevtBootMoveSlavesFpSetErrPDC 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.
TRAP-TYPE
.1.3.6.1.4.1.11.2.23.35.0.9371
hpevtBootMoveCellMonarchsStructAddrErrPDC 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().
TRAP-TYPE
.1.3.6.1.4.1.11.2.23.35.0.9372
hpevtBootMoveCellMonarchsCheckSlaveErrPDC 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().
TRAP-TYPE
.1.3.6.1.4.1.11.2.23.35.0.9373
hpevtBootMoveCellMonarchsFpSetAddrErrPDC 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().
TRAP-TYPE
.1.3.6.1.4.1.11.2.23.35.0.9375
hpevtBootMoveCellMonarchsFpSetErrPDC 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.
TRAP-TYPE
.1.3.6.1.4.1.11.2.23.35.0.9376
hpevtBootDualCoreInitFailMX2 initialization failed.
TRAP-TYPE
.1.3.6.1.4.1.11.2.23.35.0.9379
hpevtBootDeconfigCpuModulePairA cpu that is attached to a cpu that is slated for deconfiguration is being deconfigured as well.
TRAP-TYPE
.1.3.6.1.4.1.11.2.23.35.0.9380
hpevtBootVirtualizeDualCoreRegistersFailFW failed to virtualize the mx2 interposer.
TRAP-TYPE
.1.3.6.1.4.1.11.2.23.35.0.9382
hpevtBootVirtualizeDualCoreInterposerFailFW has failed to virtualize the mx2 interposer.
TRAP-TYPE
.1.3.6.1.4.1.11.2.23.35.0.9383
hpevtBootInstallPmiHandlerFailedInstallation of the FW PMI handler has failed.
TRAP-TYPE
.1.3.6.1.4.1.11.2.23.35.0.9385
hpevtPdhcCellIncompatableCell and or cpus have failed compatibility checks.
TRAP-TYPE
.1.3.6.1.4.1.11.2.23.35.0.9388
hpevtPdhcPdhNotAvailablePDH space not available after release from reset.
TRAP-TYPE
.1.3.6.1.4.1.11.2.23.35.0.9389
hpevtPdhcMponFailedMPON failed to release.
TRAP-TYPE
.1.3.6.1.4.1.11.2.23.35.0.9390
hpevtPdhcDillonResetFailedDillon failed to reset.
TRAP-TYPE
.1.3.6.1.4.1.11.2.23.35.0.9391
hpevtPdhcDmdClockFailedDMD clock is not running.
TRAP-TYPE
.1.3.6.1.4.1.11.2.23.35.0.9392
hpevtAllCpusDeconfOnCellAll possible CPUs on a cell have been scheduled for deconfiguration.
TRAP-TYPE
.1.3.6.1.4.1.11.2.23.35.0.9394
hpevtFabricLogRoutingRdErrA 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
TRAP-TYPE
.1.3.6.1.4.1.11.2.23.35.0.9403
hpevtFabricLinkRendezDisableErrAfter 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
TRAP-TYPE
.1.3.6.1.4.1.11.2.23.35.0.9412
hpevtAcDeletedA0Power is no longer being supplied to input A0 on the cabinet specified in the data field.
TRAP-TYPE
.1.3.6.1.4.1.11.2.23.35.0.9417
hpevtAcDeletedA1Power is no longer being supplied to input A1 on the cabinet specified in the data field.
TRAP-TYPE
.1.3.6.1.4.1.11.2.23.35.0.9418
hpevtAcDeletedB0Power is no longer being supplied to input B0 on the cabinet specified in the data field.
TRAP-TYPE
.1.3.6.1.4.1.11.2.23.35.0.9419
hpevtAcDeletedB1Power is no longer being supplied to input B1 on the cabinet specified in the data field.
TRAP-TYPE
.1.3.6.1.4.1.11.2.23.35.0.9420
hpevtFabricCc2CcLinkDisableErrFailed 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.
TRAP-TYPE
.1.3.6.1.4.1.11.2.23.35.0.9428
hpevtFabricISREarlyCopyRoutingErrError writing the XBC port's routing registers. The cell will reboot. Data Field: XBC port << 44 | XBC num << 32 | return status
TRAP-TYPE
.1.3.6.1.4.1.11.2.23.35.0.9430
hpevtFabricClrLinkInitBitErrMaskRdCould not read the XIN error mask register on the CC. Data Field: cell number and return status
TRAP-TYPE
.1.3.6.1.4.1.11.2.23.35.0.9431
hpevtFabricClrLinkInitBitErrMaskWrCould not write the XIN error mask register on the CC. Data Field: cell number and return status
TRAP-TYPE
.1.3.6.1.4.1.11.2.23.35.0.9432
hpevtFabricPortPairRdPstatusErrWhile testing link traversability, a XBC CSR could not be read. Data Field: Port Number << 44 | XBC Number << 32 | return value
TRAP-TYPE
.1.3.6.1.4.1.11.2.23.35.0.9433
hpevtPdhBatteryPowerLowThe Battery-Low interrupt was signaled in the Interrupt Pending Register in Dillon (PDH) by the hardware. PDHC is merely reporting the problem.
TRAP-TYPE
.1.3.6.1.4.1.11.2.23.35.0.9438
hpevtNoHandoffToOsMcaThis means that the system FW MCA handler is not going to handoff to the OS_MCA handler.
TRAP-TYPE
.1.3.6.1.4.1.11.2.23.35.0.9440
hpevtBootRtnFromSwCantGetCountersWhen 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().
TRAP-TYPE
.1.3.6.1.4.1.11.2.23.35.0.9441
hpevtBootRtnFromSwCpuNotAsleepWhen returning to PDC from other software, like returning from ISL, PDC tries to verify that all the slave processors are in the expected state (i.e. 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.
TRAP-TYPE
.1.3.6.1.4.1.11.2.23.35.0.9442
hpevtBootDeconfigAbsentCantSetCpuStatePDC 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.
TRAP-TYPE
.1.3.6.1.4.1.11.2.23.35.0.9445
hpevtNvramBlockTableCorruptThe NVRAM-based descriptor for System Firmware NVRAM blocks is corrupt.
TRAP-TYPE
.1.3.6.1.4.1.11.2.23.35.0.9448
hpevtBootMoveSlavesSetTimeoutErrThe 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.
TRAP-TYPE
.1.3.6.1.4.1.11.2.23.35.0.9450
hpevtBootReconfigAllCpusAll 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.
TRAP-TYPE
.1.3.6.1.4.1.11.2.23.35.0.9460
hpevtBootGetNumcoresFailureA 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.
TRAP-TYPE
.1.3.6.1.4.1.11.2.23.35.0.9461
hpevtFabricRmtRoutePortTopoErrWhile 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)
TRAP-TYPE
.1.3.6.1.4.1.11.2.23.35.0.9465
hpevtFabricCellRerouteFailureFailed to route around a broken link on cell reboot. Data Field: PDC return status
TRAP-TYPE
.1.3.6.1.4.1.11.2.23.35.0.9466
hpevtFabricRdFailedLinksErrorCould 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
TRAP-TYPE
.1.3.6.1.4.1.11.2.23.35.0.9468
hpevtFabricWrFailedLinksRdErrorCould 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
TRAP-TYPE
.1.3.6.1.4.1.11.2.23.35.0.9469
hpevtFabricWrFailedLinksWrErrorCould 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
TRAP-TYPE
.1.3.6.1.4.1.11.2.23.35.0.9470
hpevtFabricIncFailedLinksRdErrorCould 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
TRAP-TYPE
.1.3.6.1.4.1.11.2.23.35.0.9471
hpevtFabricIncFailedLinksWrErrorCould 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
TRAP-TYPE
.1.3.6.1.4.1.11.2.23.35.0.9472
hpevtFabricIncFailedLinksHitLimitToo 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
TRAP-TYPE
.1.3.6.1.4.1.11.2.23.35.0.9473
hpevtFabricRtgCompleteRdFldLinksErrCould not read the XBC register that contains the number of links that are currently broken on the complex. Data Field: PDC return status
TRAP-TYPE
.1.3.6.1.4.1.11.2.23.35.0.9474
hpevtFabricRtgCompleteWrFldLinksErrCould 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
TRAP-TYPE
.1.3.6.1.4.1.11.2.23.35.0.9475
hpevtFabricCellRerouteRdXbcErrCould not read the XBC register that marks the ports that have been routed around. Data Field: (XBC Num << 32) | PDC return status
TRAP-TYPE
.1.3.6.1.4.1.11.2.23.35.0.9476
hpevtFabricCellRerouteNbrNotReachableThe PIOB route to the remote XBC was not traversable. The cell will halt. Data Field: (XBC Num << 32) | PDC return status
TRAP-TYPE
.1.3.6.1.4.1.11.2.23.35.0.9477
hpevtFabricCellRerouteSm4RlsErrCould not release the remote XBC's semaphore. Cell will halt. Data Field: (XBC Num << 32) | PDC return status
TRAP-TYPE
.1.3.6.1.4.1.11.2.23.35.0.9479
hpevtFabricRmtRoutePortBcastWrErrFailed to complete a broadcast write to an XBC. Data Field: (XBC Num << 32) | PDC return status
TRAP-TYPE
.1.3.6.1.4.1.11.2.23.35.0.9480
hpevtFabricRmtRoutePortRdErrFailed to complete a read to the built-in port of a XBC. Data Field: (XBC Num << 32) | PDC return status
TRAP-TYPE
.1.3.6.1.4.1.11.2.23.35.0.9481
hpevtFabricRmtRoutePortWrErrFailed to complete a write to the local cell's port of the XBC. Data Field: (XBC Port << 44) | (XBC Num << 32) | PDC return status
TRAP-TYPE
.1.3.6.1.4.1.11.2.23.35.0.9482
hpevtIoLinkSubsystemFailedThe link between the CC and SBA failed meaning that I/O is not available to the reporting cell.
TRAP-TYPE
.1.3.6.1.4.1.11.2.23.35.0.9484
hpevtIoSbaSubsystemFailedAn error was detected in the SBA and the reporting cell has no I/O.
TRAP-TYPE
.1.3.6.1.4.1.11.2.23.35.0.9485
hpevtIoErrengineErrorThe structured exception handling within the system firmware failed during I/O initialization.
TRAP-TYPE
.1.3.6.1.4.1.11.2.23.35.0.9486
hpevtIoDiscEeMallocErrThere is not enough malloc resources for the I/O structure exception handling. I/O on the reported cell is not available.
TRAP-TYPE
.1.3.6.1.4.1.11.2.23.35.0.9487
hpevtIoDiscEeCreatetreeErrError creating the structure for housing the I/O structured exception handling services and data. I/O is lost on the reporting cell.
TRAP-TYPE
.1.3.6.1.4.1.11.2.23.35.0.9488
hpevtIoDiscEeAttachserviceErrUnable to bind the I/O structure exception handling to the internal data structures.
TRAP-TYPE
.1.3.6.1.4.1.11.2.23.35.0.9489
hpevtIoDiscEeInitErrError detected while initializing the I/O structure exception handling services.
TRAP-TYPE
.1.3.6.1.4.1.11.2.23.35.0.9490
hpevtIoDiscEeInitializationErrError initializing the I/O structure exception handling data structures.
TRAP-TYPE
.1.3.6.1.4.1.11.2.23.35.0.9491
hpevtIoDiscEeContextErrThe structured I/O exception handling data structures have an error. All I/O on the reporting cell is not available.
TRAP-TYPE
.1.3.6.1.4.1.11.2.23.35.0.9492
hpevtIoDiscCreateSbaNodeErrWhile setting up the internal SBA data and service an error was detected. All I/O for the reporting cell is not available.
TRAP-TYPE
.1.3.6.1.4.1.11.2.23.35.0.9493
hpevtIoDiscSbaAttachserviceErrAn error attaching firmware services to the internal structures was detected. All I/O on the reporting cell is not available.
TRAP-TYPE
.1.3.6.1.4.1.11.2.23.35.0.9494
hpevtIoDiscSbaInitnodeErrSystem firmware detected an error initializing internal SBA data structures and services. This is usually an error with unavailable resources.
TRAP-TYPE
.1.3.6.1.4.1.11.2.23.35.0.9495
hpevtIoDiscSbaUnknownErrThe SBA type is unknown to the system firmware. The I/O on the reporting cell is not available.
TRAP-TYPE
.1.3.6.1.4.1.11.2.23.35.0.9496
hpevtIoDeviceMissingAn expected I/O device cannot be detected by the system firmware.
TRAP-TYPE
.1.3.6.1.4.1.11.2.23.35.0.9497
hpevtFabricRmtRoutePortBadRerouteToo 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
TRAP-TYPE
.1.3.6.1.4.1.11.2.23.35.0.9498
hpevtAgtPredictMemFailECC (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.
TRAP-TYPE
.1.3.6.1.4.1.11.2.23.35.0.9652
hpevtWinAgtLockedPropertyServer Agents SNMP branch is not responding due to a portion of the IPMI Management Subsystem being locked by another entity.
TRAP-TYPE
.1.3.6.1.4.1.11.2.23.35.0.9653
hpevtIoPciPowerOverloadErrA non-hot plug I/O slot's power consumption increases the total I/O power consumption beyond the supported limit. Firmware will display the following EFI error message, 'I/O configuration exceeds power limit' and disallow O/S boot. Data Field: Physical location of the I/O slot.
TRAP-TYPE
.1.3.6.1.4.1.11.2.23.35.0.9658
hpevtMemSbeSeedingEnabledThis is a warning that the system is running in a degraded 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.
TRAP-TYPE
.1.3.6.1.4.1.11.2.23.35.0.9659
hpevtFabricWrFailedLinksTopoErrRead failure while writing the number of failed links to the XBC. Data Field: Return Status (SUCCESS = 0, FAILURE = -1)
TRAP-TYPE
.1.3.6.1.4.1.11.2.23.35.0.9661
hpevtBootErrInitGroupCPaFieldsPDC 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.
TRAP-TYPE
.1.3.6.1.4.1.11.2.23.35.0.9663
hpevtFabricAssertFabricHopAn unexpected error occurred while initializing the fabric. The firmware is not able to analyze this error. Clues to the cause of this error may be found in the IPMI forward progress log (FPL) either shortly before or after this log entry occurred. The FPL is available from the management processor using the 'sl' command. HP-UX also saves these logs in the /var/stm/logs/os directory, and they can be viewed using the slview utility.
TRAP-TYPE
.1.3.6.1.4.1.11.2.23.35.0.9666
hpevtBootFailedReadingProfileCInIcmPDC could not access a complex profile. The partition will be reset. Data field contains the return status from the function that encountered the error.
TRAP-TYPE
.1.3.6.1.4.1.11.2.23.35.0.9668
hpevtFabricHaltLinkDisableErrBefore 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.
TRAP-TYPE
.1.3.6.1.4.1.11.2.23.35.0.9670
hpevtBootGetSpiromGetSiblingErrConfiguration information on the processor was invalid. The cell will be halted. Data field contains the return value from the function that encountered the error.
TRAP-TYPE
.1.3.6.1.4.1.11.2.23.35.0.9674
hpevtCpuClockRatioMismatchThe clock ratio that the processor is running at does not match the clock ratio that manageability is reporting.
TRAP-TYPE
.1.3.6.1.4.1.11.2.23.35.0.9678
hpevtBootStopBootOverrideThe user has manually bypassed a stop boot condition (caused by an error during boot) and continued to boot an O/S. The system might experience unpredictable failures.
TRAP-TYPE
.1.3.6.1.4.1.11.2.23.35.0.9681
hpevtVgaBiosRelocFailFirmware 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.
TRAP-TYPE
.1.3.6.1.4.1.11.2.23.35.0.9682
hpevtCompMatrixXsumErrorThe component compatibility matrix stored in NVRAM and used by system firmware has a checksum error. The stored value does not equal the calculated value. The data field will contain first the expected value, and the subsequent code will contain the actual data.
TRAP-TYPE
.1.3.6.1.4.1.11.2.23.35.0.9685
hpevtBootGetDefaultRdrsFailedPDC 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.
TRAP-TYPE
.1.3.6.1.4.1.11.2.23.35.0.9695
hpevtBootGetCurrentRdrsFailedPDC 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.
TRAP-TYPE
.1.3.6.1.4.1.11.2.23.35.0.9696
hpevtBootReadPrefetchFailedPDC 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.
TRAP-TYPE
.1.3.6.1.4.1.11.2.23.35.0.9697
hpevtBootReadZlcoFailedPDC 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.
TRAP-TYPE
.1.3.6.1.4.1.11.2.23.35.0.9698
hpevtBootUpdateZlcoAndPrefetchFailedPDC 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.
TRAP-TYPE
.1.3.6.1.4.1.11.2.23.35.0.9700
hpevtBootErrorReadingZlcoFlagInPdProfilePDC could not access a complex profile. The partition will be reset.. Data field contains the return status from the function that encountered the error.
TRAP-TYPE
.1.3.6.1.4.1.11.2.23.35.0.9701
hpevtBootFindCoreCellCmplxProfileAcErrPDC could not access a complex profile. The cell will be reset. Data field contains the return status from the function that encountered the error.
TRAP-TYPE
.1.3.6.1.4.1.11.2.23.35.0.9706
hpevtBootFindCoreCellConfigSelectErrCould 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
TRAP-TYPE
.1.3.6.1.4.1.11.2.23.35.0.9707
hpevtBootCellLclCantFindViableThe potential core cell was not viable (i.e. no core I/O, etc). This cell will reset for reconfiguration. Data Field: bit mask of cells that made the rendezvous set
TRAP-TYPE
.1.3.6.1.4.1.11.2.23.35.0.9708
hpevtBootCellRmtCantFindViableThe potential core cell was not viable (i.e. no core I/O, etc). This cell will reset for reconfiguration. Data Field: bit mask of cells that made the rendezvous set
TRAP-TYPE
.1.3.6.1.4.1.11.2.23.35.0.9709
hpevtBootFindCoreCellNotInRendezThe 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
TRAP-TYPE
.1.3.6.1.4.1.11.2.23.35.0.9710
hpevtBootFindCoreCellLclNotViableThe 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
TRAP-TYPE
.1.3.6.1.4.1.11.2.23.35.0.9711
hpevtBootFindCoreCellFabriclessPdErrThis 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
TRAP-TYPE
.1.3.6.1.4.1.11.2.23.35.0.9712
hpevtRtcAccessErrorWhile validating the internal RTC data the data is read twice and compared. If the comparison fails to match the read is performed again up a maximum of 50 times. If we cannot get a match in 50 retries we issue this event.
TRAP-TYPE
.1.3.6.1.4.1.11.2.23.35.0.9719
hpevtBootAccessCellArchErrPDC 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.
TRAP-TYPE
.1.3.6.1.4.1.11.2.23.35.0.9727
hpevtXbcLogSizeErrThe 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)
TRAP-TYPE
.1.3.6.1.4.1.11.2.23.35.0.9740
hpevtXbcLogClearErrSystem firmware was unable to clear an XBC error. The data field contains: XBC number (32:43) port number (44:55) error type (0:31)
TRAP-TYPE
.1.3.6.1.4.1.11.2.23.35.0.9741
hpevtIodiscPciLogErrorError encountered while collecting PCI error logs. The result is some or all PCI error logs will be unavailable.
TRAP-TYPE
.1.3.6.1.4.1.11.2.23.35.0.9744
hpevtIodiscSbaLogErrorError encountered while collecting SBA error logs. The result is some or all SBA error logs will be unavailable.
TRAP-TYPE
.1.3.6.1.4.1.11.2.23.35.0.9745
hpevtXbcInitMaxRetriesDuring 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)
TRAP-TYPE
.1.3.6.1.4.1.11.2.23.35.0.9746
hpevtWinAgtPredictMemFailWarningECC (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.
TRAP-TYPE
.1.3.6.1.4.1.11.2.23.35.0.9750
hpevtWinAgtPredictMemFailCriticalECC (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.
TRAP-TYPE
.1.3.6.1.4.1.11.2.23.35.0.9751
hpevtPciFatalRopeParityErrA error occurred on the bus connecting the PCI card to the system bus.
TRAP-TYPE
.1.3.6.1.4.1.11.2.23.35.0.9753
hpevtPciFatalBusErrorA 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.
TRAP-TYPE
.1.3.6.1.4.1.11.2.23.35.0.9754
hpevtPciFatalDeviceErrorA PCI card has been marked as 'fatal' by the operating system due to a device error.
TRAP-TYPE
.1.3.6.1.4.1.11.2.23.35.0.9755
hpevtBootErrorReadingFirstBootTokenFirmware 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
TRAP-TYPE
.1.3.6.1.4.1.11.2.23.35.0.9768
hpevtBootNonPaCellDetectedmonarch PA cell has detected that a cell it is attempting to rendezvous into its PD is not a PA cell and is thus incompatible.
TRAP-TYPE
.1.3.6.1.4.1.11.2.23.35.0.9769
hpevtFabricErrorsXbcClearWrErrA 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
TRAP-TYPE
.1.3.6.1.4.1.11.2.23.35.0.9774
hpevtFabricErrorsXbcClearRdGlblErrFailed to read the XBC Global CSR Error Status register. Data Field: (XBC Port Num << 56) | (XBC Num << 32) | error status
TRAP-TYPE
.1.3.6.1.4.1.11.2.23.35.0.9775
hpevtFabricErrorsXbcClrLoSevErrThe 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
TRAP-TYPE
.1.3.6.1.4.1.11.2.23.35.0.9776
hpevtFabricErrorsXbcClrHiSevErrThe 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
TRAP-TYPE
.1.3.6.1.4.1.11.2.23.35.0.9777
hpevtFabricErrorsXbcClearRdPortErrFailed to read the XBC Port Error Status register. Data Field: (XBC Port Num << 56) | (XBC Num << 32) | error status
TRAP-TYPE
.1.3.6.1.4.1.11.2.23.35.0.9778
hpevtFabricErrsCsrLogClrRdSlicesErrFailed to read the XBC Global CSR Error Status register. Data Field: (XBC Port Num << 56) | error status
TRAP-TYPE
.1.3.6.1.4.1.11.2.23.35.0.9780
hpevtFabricErrsCsrLogClrCopyBlk0ErrFirmware 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
TRAP-TYPE
.1.3.6.1.4.1.11.2.23.35.0.9781
hpevtFabricErrsCsrLogClrCopyBlk2ErrFirmware 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
TRAP-TYPE
.1.3.6.1.4.1.11.2.23.35.0.9782
hpevtFabricXbcLoStateResetErrFirmware was unable to reset the XBC CSR Low Severity error log state. Data Field: (XBC Port Num << 56) | (XBC Num << 32) | error status
TRAP-TYPE
.1.3.6.1.4.1.11.2.23.35.0.9783
hpevtFabricClrXbcSym01FailureThe XBC Low Severity error logs were not cleared. Data Field: (XBC Port Num << 56) | (XBC Num << 32) | number of failed clear attempts
TRAP-TYPE
.1.3.6.1.4.1.11.2.23.35.0.9784
hpevtFabricClrXbcIsLoCsrErrErrReading the XBC CSR Error Status register failed. Data field: (XBC Port Num << 56) | (XBC Num << 32) | error status
TRAP-TYPE
.1.3.6.1.4.1.11.2.23.35.0.9785
hpevtFabricClrXbcRdLoLogStateErrFailed 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
TRAP-TYPE
.1.3.6.1.4.1.11.2.23.35.0.9786
hpevtFabricXbcHiStateResetErrFirmware was unable to reset the XBC CSR Low Severity error log state. Data Field: (XBC Port Num << 56) | (XBC Num << 32) | error status
TRAP-TYPE
.1.3.6.1.4.1.11.2.23.35.0.9787
hpevtFabricClrXbcIsHiCsrErrErrReading the XBC CSR Error Status register failed. Data field: (XBC Port Num << 56) | (XBC Num << 32) | error status
TRAP-TYPE
.1.3.6.1.4.1.11.2.23.35.0.9788
hpevtFabricClrXbcRdHiLogStateErrFailed 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
TRAP-TYPE
.1.3.6.1.4.1.11.2.23.35.0.9789
hpevtPlatformCacheHashingErrorAn error occurred while enabling hashing in the platform cache. The data field contains the status.
TRAP-TYPE
.1.3.6.1.4.1.11.2.23.35.0.9801
hpevtFabricXbcWriteableInvalidCsrA 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
TRAP-TYPE
.1.3.6.1.4.1.11.2.23.35.0.9827
hpevtMcCellsLostConnectionIt indicates loss of cell connectivity in the partition during a global MCA processing.
TRAP-TYPE
.1.3.6.1.4.1.11.2.23.35.0.9832
hpevtBuildErrCellDevTreeError status of building the cell-level firmware device tree
TRAP-TYPE
.1.3.6.1.4.1.11.2.23.35.0.9849
hpevtDcnfgFsbInitAn error has occurred during CPU FSB interface initialization. The datafield contains a 32-bit error number and 32-bits of additional error information. The CPU will be deconfigured.
TRAP-TYPE
.1.3.6.1.4.1.11.2.23.35.0.9867
hpevtDcnfgCpuParamsAn error has occurred while obtaining CPU 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.
TRAP-TYPE
.1.3.6.1.4.1.11.2.23.35.0.9868
hpevtDcnfgCpuIcacheAn 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.
TRAP-TYPE
.1.3.6.1.4.1.11.2.23.35.0.9869
hpevtDcnfgCpuDcacheAn error occurred while obtaining CPU dcache 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 error occurs during system boot.
TRAP-TYPE
.1.3.6.1.4.1.11.2.23.35.0.9870
hpevtDcnfgCpuCacheStateAn error occurred while initializing the CPU cache to a known state. The datafield contains a 32-bit error number and 32-bits of additional error information. The CPU will be deconfigured.
TRAP-TYPE
.1.3.6.1.4.1.11.2.23.35.0.9871
hpevtDcnfgCpuCacheMonitorAn error occurred while enabling CPU cache error monitoring. The datafield contains a 32-bit error number and 32-bits of additional error information. The CPU will be deconfigured.
TRAP-TYPE
.1.3.6.1.4.1.11.2.23.35.0.9872
hpevtDcnfgCpuMcaAn error occurred while enabling some machine error check traps on a CPU. The datafield contains a 32-bit error number and 32-bits of additional error information. The CPU will be deconfigured.
TRAP-TYPE
.1.3.6.1.4.1.11.2.23.35.0.9873
hpevtDcnfgCpuDisableMcaAn error occurred while disabling marching error check traps on a CPU. The datafield contains a 32-bit error number and 32-bits of additional error information. The CPU will be deconfigured.
TRAP-TYPE
.1.3.6.1.4.1.11.2.23.35.0.9874
hpevtDcnfgCpuSelfTestAn error occurred during the serialized CPU late selftests. The datafield contains a 32-bit error number and 32-bits of additional error information. The CPU will be deconfigured.
TRAP-TYPE
.1.3.6.1.4.1.11.2.23.35.0.9875
hpevtDcnfgCpuL2CacheAn error occurred while enabling the CPU L2 shared cache. The datafield contains a 32-bit error number and 32-bits of additional error information. The CPU will be deconfigured.
TRAP-TYPE
.1.3.6.1.4.1.11.2.23.35.0.9876
hpevtDcnfgCpuDefValueAn error while getting default values for programmable CPU internal registers 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.
TRAP-TYPE
.1.3.6.1.4.1.11.2.23.35.0.9877
hpevtDcnfgCpuInRegAn 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.
TRAP-TYPE
.1.3.6.1.4.1.11.2.23.35.0.9878
hpevtDcnfgCpuProgRegAn error occurred while programming CPU internal registers with final configuration values. The datafield contains a 32-bit error number and 32-bits of additional error information. The CPU will be deconfigured.
TRAP-TYPE
.1.3.6.1.4.1.11.2.23.35.0.9879
hpevtNoMemSelfTestThere was not enough error free memory in the system to run the late selftests.
TRAP-TYPE
.1.3.6.1.4.1.11.2.23.35.0.9896
hpevtCellLatchOpenThe left cell ejector on the specified cell is open.
TRAP-TYPE
.1.3.6.1.4.1.11.2.23.35.0.10060
hpevtDcnfgRightCellLatchThe right ejector latch on the specified cell board is open.
TRAP-TYPE
.1.3.6.1.4.1.11.2.23.35.0.10061
hpevtCellLatchSensorBadThe optical emitters on the cell latch sensors are not functioning.
TRAP-TYPE
.1.3.6.1.4.1.11.2.23.35.0.10062
hpevtVrmVltFaultThe specified vrm is reporting a fault.
TRAP-TYPE
.1.3.6.1.4.1.11.2.23.35.0.10063
hpevtVrmTempFltThe specified vrm is reporting a fault.
TRAP-TYPE
.1.3.6.1.4.1.11.2.23.35.0.10064
hpevtVrmFltThe specified rail is reporting a fault.
TRAP-TYPE
.1.3.6.1.4.1.11.2.23.35.0.10065
hpevtVrmIoVltFltThe specified pci vrm is reporting a voltage fault.
TRAP-TYPE
.1.3.6.1.4.1.11.2.23.35.0.10068
hpevtPwrBrickVltFltThe specified pci power brick is reporting a voltage fault.
TRAP-TYPE
.1.3.6.1.4.1.11.2.23.35.0.10069
hpevtVrmBkPlaneTempFltThe specified vrm is reporting a temperature fault.
TRAP-TYPE
.1.3.6.1.4.1.11.2.23.35.0.10070
hpevtBkPlanePwrBrickTempFltThe specified pci power brick is reporting a temperature fault.
TRAP-TYPE
.1.3.6.1.4.1.11.2.23.35.0.10071
hpevtBkPlanVrmRailFltThe specified vrm rail is reporting a fault.
TRAP-TYPE
.1.3.6.1.4.1.11.2.23.35.0.10072
hpevtBkPlanePwrBrkFltThe specified pci brick is reporting a fault.
TRAP-TYPE
.1.3.6.1.4.1.11.2.23.35.0.10073
hpevtBkPlaneVrmVltFltThe specified system backplane vrm is reporting a module voltage fault.
TRAP-TYPE
.1.3.6.1.4.1.11.2.23.35.0.10103
hpevtBkPlaneVrmTempFltThe specified system backplane vrm is reporting a temperature fault.
TRAP-TYPE
.1.3.6.1.4.1.11.2.23.35.0.10104
hpevtBkPlaneFltThe specified system backplane rail is reporting a fault
TRAP-TYPE
.1.3.6.1.4.1.11.2.23.35.0.10105
hpevtMstrMpFailedThe master mp has failed. The slave has taken over management of the cabinet.
TRAP-TYPE
.1.3.6.1.4.1.11.2.23.35.0.10115
hpevtNvramAllocThe NVRAM service was unable to satisfy an NVRAM allocation request.
TRAP-TYPE
.1.3.6.1.4.1.11.2.23.35.0.10116
hpevtRtcTimeRegThe RTC seems to not be updating its internal time registers. The cell cannot boot without the RTC.
TRAP-TYPE
.1.3.6.1.4.1.11.2.23.35.0.10132
hpevtPAAFltMx2An uncorrectable Power Aware Architecture (PAA) fault has occurred on the MX2 module and PAA firmware has halted. The system will continue to run without PAA firmware.
TRAP-TYPE
.1.3.6.1.4.1.11.2.23.35.0.10159
hpevtAPIopenLnkLocCellfabric API is about to open the a link going out of the local cell
TRAP-TYPE
.1.3.6.1.4.1.11.2.23.35.0.10209
hpevtCSRreadUnsuccessTimeOutAn Arches fabric CSR read was unsuccessful because of a timeout.
TRAP-TYPE
.1.3.6.1.4.1.11.2.23.35.0.10272
hpevtCSRWriteUnsuccessAn Arches fabric CSR write was unsuccessful
TRAP-TYPE
.1.3.6.1.4.1.11.2.23.35.0.10273
hpevtDataErrEncountThe event data details the error return status from Phase3BackToBackPrep. Internal debug only, this refers to an unexpected firmware error or data corruption.
TRAP-TYPE
.1.3.6.1.4.1.11.2.23.35.0.10343
hpevtConfigMaxMemoryThe maximum memory supported by this system has been exceeded. The data field contains the amount of memory supported by the system.
TRAP-TYPE
.1.3.6.1.4.1.11.2.23.35.0.10351
hpevtFailDelBadPortFailed to delete a bad port while routing the fabric. Data field indicates return status
TRAP-TYPE
.1.3.6.1.4.1.11.2.23.35.0.10357
hpevtFailDelBadEdgefailed to delete an edge that was found to be bad during routing
TRAP-TYPE
.1.3.6.1.4.1.11.2.23.35.0.10358
hpevtCommandMemBufA command to the memory buffer chip failed to complete.
TRAP-TYPE
.1.3.6.1.4.1.11.2.23.35.0.10361
hpevtUnsupprtArflsCsrRouteTravsbleThe Arches Fabric function ArfIsCsrRouteTraversable was called for a back-to-back system. This is unsupported, ArfIsCsrRouteTraversable should only be called for systems with crossbars. No data.
TRAP-TYPE
.1.3.6.1.4.1.11.2.23.35.0.10375
hpevtInvalidPortToTravsbleAn invalid port number was given as an input to an Arches Fabric Traversability function. The port is expected to be an internal XBC num (8-15), but the actual port was not. Data field: (XBC number << 32) | (port number << 48)
TRAP-TYPE
.1.3.6.1.4.1.11.2.23.35.0.10376
hpevtUnbleRdXBCPortNghbrUnable to read XBC port neighbor information. Data field: (xbcNum << 32) | (portNum << 48)
TRAP-TYPE
.1.3.6.1.4.1.11.2.23.35.0.10377
hpevtXBCPortUnexpctNghbrChipXBC port with an unexpected neighbor chip type. Data field: (expected chip type) | (actual chip type << 16) | (xbcNum << 32) | (portNum << 48)
TRAP-TYPE
.1.3.6.1.4.1.11.2.23.35.0.10378
hpevtXBCPortHaveUnxpctNghbrIDAn XBC port was found to have an unexpected neighbor ID. Data field: (expected NID) | (actual NID << 16) | (xbcNum << 32) | (portNum << 48)
TRAP-TYPE
.1.3.6.1.4.1.11.2.23.35.0.10379
hpevtXBCHaveUnexpctNghbrPrtConnAn XBC was found to have an unexpected neighbor port connection. Data field: (expected port) | (actual port << 16) | (xbcNum << 32) | (portNum << 48)
TRAP-TYPE
.1.3.6.1.4.1.11.2.23.35.0.10380
hpevtDataNotFndEdgLstThe expected data was not found in the Arches Fabric expected edge list. Data field is unused
TRAP-TYPE
.1.3.6.1.4.1.11.2.23.35.0.10381
hpevtXBCPrtUnxpctNgbrChipAn XBC port has an unexpected neighbor chip type. Data field: neighbor type found, bits [7:0], other bits unused
TRAP-TYPE
.1.3.6.1.4.1.11.2.23.35.0.10382
hpevtXBCtoXBCLnkDwnA previously good XBC-XBC link was found to be down. Data field: (xbcNum << 32) | (portNum << 48)
TRAP-TYPE
.1.3.6.1.4.1.11.2.23.35.0.10384
hpevtXBCprtFndErrTravsblAn XBC port was found to have a Fatal Error during traversability test. Data field: (xbcNum << 32) | (portNum << 48)
TRAP-TYPE
.1.3.6.1.4.1.11.2.23.35.0.10385
hpevtUnblRdLnkCelFabCSRUnable to read the local cell's LINK_SEL_FABRIC CSR Data field: unused
TRAP-TYPE
.1.3.6.1.4.1.11.2.23.35.0.10386
hpevtUblRdXBCrouteTblUnable to read the XBC route table. Data field: (route index) | (xbcNum << 32) | (portNum << 48)
TRAP-TYPE
.1.3.6.1.4.1.11.2.23.35.0.10387
hpevtXBCLnkNotConnCSRTravsblAn XBC link was found to be not connected while testing CSR traffic traversability. Data field: (xbcNum << 32) | (portNum << 48)
TRAP-TYPE
.1.3.6.1.4.1.11.2.23.35.0.10388
hpevtErrRdAlrecAlbIdCsrError reading Skyline ALREC_ALB_ID CSR Data field: (Skyline port) | (Cell number << 56)
TRAP-TYPE
.1.3.6.1.4.1.11.2.23.35.0.10389
hpevtCirRoutFndTstXbcCsrA circular route was found while testing XBC CSR traffic traversability. Data field: (target XBC << 32) | (cellNum << 56)
TRAP-TYPE
.1.3.6.1.4.1.11.2.23.35.0.10390
hpevtXBCRdErrAlrecAlbIdCsrError reading ALREC_ALB_ID CSR for an XBC port. Data field: (xbcNum << 32) | (portNum << 48)
TRAP-TYPE
.1.3.6.1.4.1.11.2.23.35.0.10391
hpevtXBC-XBCPrtHavInvldChipCnnAn XBC-XBC port had an invalid chip type connection. Data field: (expected chip type) | (actual chip type << 32)
TRAP-TYPE
.1.3.6.1.4.1.11.2.23.35.0.10392
hpevtArflsXbcRotTravrsblCalBakToBakArfIsXbcRouteTraversable was called on a back-to-back system which is an improper use of the function. Data field: unused
TRAP-TYPE
.1.3.6.1.4.1.11.2.23.35.0.10393
hpevtXBCToXBClnkFndFatErrIn ArfIsXbcRouteTraversable, an XBC-XBC link was found to have fatal errors. Data field: (xbcNum << 32) | (portNum << 48)
TRAP-TYPE
.1.3.6.1.4.1.11.2.23.35.0.10394
hpevtUnablRdXbcRotTblEnblMskCsrUnable to read the XBC ROUTE_TABLE_ENABLE_MASK CSR. Data field: (xbcNum << 32) | (portNum << 48)
TRAP-TYPE
.1.3.6.1.4.1.11.2.23.35.0.10395
hpevtErrRdXbcRotTablCsrError reading an XBC ROUTE_TABLE CSR. Data field: route index | (xbcNum << 32) | (portNum << 48)
TRAP-TYPE
.1.3.6.1.4.1.11.2.23.35.0.10396
hpevtXbcPrtErrRdAlrecAlbIDCsrError reading ALB ALREC_ALB_ID CSR for an XBC port. Data field: (xbcNum << 32) | (portNum << 48)
TRAP-TYPE
.1.3.6.1.4.1.11.2.23.35.0.10397
hpevtXbcPrtFndUnxpctNgbrChipAn XBC port was found with an unexpected neighbor chip. Data field: expected chip type | (actual chip type << 32)
TRAP-TYPE
.1.3.6.1.4.1.11.2.23.35.0.10398
hpevtCelPrtPairNotFndGrphDatA cell/port pair was not found in the expected graph data. Data field: (cellNum << 32) | CC portNum
TRAP-TYPE
.1.3.6.1.4.1.11.2.23.35.0.10401
hpevtArchFabFndLocCelLnkNotConnArches Fabric Traversability code unexpectedly found the local cell link not connected. Data field: linkState (0 = connected, 1 = link pending, 2 = not connected, -1 = error)
TRAP-TYPE
.1.3.6.1.4.1.11.2.23.35.0.10402
hpevtXbcErrRdRoutCsrError reading the ROUTEx CSR on the XBC. Data field: route index | (xbcNum << 32) | (portNum << 48)
TRAP-TYPE
.1.3.6.1.4.1.11.2.23.35.0.10403
hpevtXbcUnablRdAlrecAlbIdCsrUnable to read the ALB ALREC_ALB_ID CSR for an XBC port. Data field: (xbcNum << 32) | (portNum << 48)
TRAP-TYPE
.1.3.6.1.4.1.11.2.23.35.0.10404
hpevtXbcPrtHasUnxpctNgbrChptypeAn XBC port has an unexpected neighbor chip type. Data field: expected neighbor chip type | (actual neighbor chip type << 32)
TRAP-TYPE
.1.3.6.1.4.1.11.2.23.35.0.10405
hpevtCelToCelLnkHasUnxpctNgbrChpTypeA Cell-Cell link has an unexpected neighbor chip type. Data field: expected neighbor chip type | (actual neighbor chip type << 32)
TRAP-TYPE
.1.3.6.1.4.1.11.2.23.35.0.10406
hpevtCelPrtPairNotExstGrphDatThe cell/port pair does not exist in the Arches Fabric expected graph data. Data field: CC port | (cellNum << 32)
TRAP-TYPE
.1.3.6.1.4.1.11.2.23.35.0.10407
hpevtCelToCelLnkConnUnxpctNgbrPrtA Cell-Cell link is connected to an unexpected neighbor port. Data field: expected neighbor port | (actual neighbor port << 32)
TRAP-TYPE
.1.3.6.1.4.1.11.2.23.35.0.10408
hpevtCelToCelLnkConnUnxpctCelA Cell-Cell link is connected to an unexpected cell. Data field: expected neighbor ID | (actual neighbor ID << 16) | (target cell << 32) | (local cell << 48)
TRAP-TYPE
.1.3.6.1.4.1.11.2.23.35.0.10409
hpevtEFIDrvrFailLoadAn EFI Driver may be corrupt.
TRAP-TYPE
.1.3.6.1.4.1.11.2.23.35.0.10412
hpevtVmRetErrNonCohTblVM_FindAllRoutes returned an unexpected error during Non-Coherent table setup. Data field: (return value) | (source cell << 32) | (target cell << 48)
TRAP-TYPE
.1.3.6.1.4.1.11.2.23.35.0.10413
hpevtNctTblWrtGlobLnkSelNonCohFailIn SetupNCTable, a write to the GLOBAL_LINK_SEL_NONCOH CSR failed. Data field: (data written to CSR) | (actual CSR data read << 32)
TRAP-TYPE
.1.3.6.1.4.1.11.2.23.35.0.10414
hpevtNctTblFailArfPhs3SetupNCTable failed in ArfPhase3. Data field: cell set passed in to SetupNCTable
TRAP-TYPE
.1.3.6.1.4.1.11.2.23.35.0.10415
hpevtPostRndevzFailPrepBckToBckSysA failure occurred while prepping a back-to-back system for post-rendezvous Arches Fabric setup. Data field: return value from Phase4BackToBackPrep
TRAP-TYPE
.1.3.6.1.4.1.11.2.23.35.0.10427
hpevtArfPhs4UnablSetNonCohLnkArfPhase4 was unable to set up the Non-Coherent link select to at least one cell in its alive/gsm sharing set. Data field: bitmap of unreachable cells
TRAP-TYPE
.1.3.6.1.4.1.11.2.23.35.0.10429
hpevtUnablSetNonCohRoutUnable to set the Non-Coherent route. Data field: (sourceCell << 32) | (cell set passed in to SetupNCTable)
TRAP-TYPE
.1.3.6.1.4.1.11.2.23.35.0.10431
hpevtUnableSetCohRoutCelUnable to setup the Coherent route table for a cell in our partition. Data field: (sourceCell << 32) | (cell set passed in to SetupCohTable)
TRAP-TYPE
.1.3.6.1.4.1.11.2.23.35.0.10432
hpevtErrWrtXbcRoutTblEnblMskCsrError writing the XBC ROUTE_TABLE_ENABLE_MASK CSR. Data field: (route set to disable) | (xbcNum << 32) | (xbc port << 48)
TRAP-TYPE
.1.3.6.1.4.1.11.2.23.35.0.10435
hpevtVertxRetUnxpctErrNonCohTblThe Arches Fabric vertex module returned an unexpected error during Non-Coherent table setup. Data field: (return value) | (sourceCell << 32) | (dest cell << 48)
TRAP-TYPE
.1.3.6.1.4.1.11.2.23.35.0.10436
hpevtWrtSkyGlobLnkSelCohFailA write to a Skyline Global LINK_SEL_COHx CSR failed. Data field: cell number of the Skyline that failed, bits [7:0]. Other bits unused
TRAP-TYPE
.1.3.6.1.4.1.11.2.23.35.0.10439
hpevtUnablWrtXbcPrtCsrUnable to write the XBC port scratch CSR with the routing state. Data field: (routing state) | (xbcNum << 32) | (portNum << 48)
TRAP-TYPE
.1.3.6.1.4.1.11.2.23.35.0.10475
hpevtSysFwUnAccesComplxProfCouldn't get the configured set during Fabric Init
TRAP-TYPE
.1.3.6.1.4.1.11.2.23.35.0.10481
hpevtSysFwDetctErrFabInitError while running the Arches Fabric API part of Fabric Init.
TRAP-TYPE
.1.3.6.1.4.1.11.2.23.35.0.10482
hpevtSysFwDetctFailFabInitFailure while running the Fabric API part of Fabric Init.
TRAP-TYPE
.1.3.6.1.4.1.11.2.23.35.0.10483
hpevtSysFwDetctErrFabOptimzAn error was encountered while running the Fabric API to optimize the fabric.
TRAP-TYPE
.1.3.6.1.4.1.11.2.23.35.0.10487
hpevtInPwrUPSFailInput power to the specified UPS has failed.
TRAP-TYPE
.1.3.6.1.4.1.11.2.23.35.0.10489
hpevtUpsRestoredInput power to the specified UPS has been restored.
TRAP-TYPE
.1.3.6.1.4.1.11.2.23.35.0.10490
hpevtUpsExhaustedThe system is being powered down as UPS power is exhausted.
TRAP-TYPE
.1.3.6.1.4.1.11.2.23.35.0.10495
hpevtSALFailRedzvsProcsDuring SAL Machine Check handling, SAL fail to round up all the processor entering SAL Machine check handler.
TRAP-TYPE
.1.3.6.1.4.1.11.2.23.35.0.10509
hpevtSALFailClrCECLogSal failed to clear the CEC logs during Machine check handling. The data field return an ASCII name of the CEC that failed to clear.
TRAP-TYPE
.1.3.6.1.4.1.11.2.23.35.0.10510
hpevtSysFwUnAccesXBCSemphrAn error occurred while getting the XBC semaphore.
TRAP-TYPE
.1.3.6.1.4.1.11.2.23.35.0.10516
hpevtSysFwDetctErrRelXBCGlobSemphrAn error occurred while releasing the XBC Global Semaphore.
TRAP-TYPE
.1.3.6.1.4.1.11.2.23.35.0.10518
hpevtSysFwDetctErrOwnXBCGlobSemphrAn error occurred while checking the owner of the XBC Global Semaphore.
TRAP-TYPE
.1.3.6.1.4.1.11.2.23.35.0.10519
hpevtErrFormXbcSemphrAddrAn error occurred while forming the XBC semaphore address. Data Field: (xbc << 32) | (cell << 56)
TRAP-TYPE
.1.3.6.1.4.1.11.2.23.35.0.10520
hpevtErrRdXbcGlobSemphrError reading the XBC Global Semaphore. Data Field: (cell num << 56) | (xbc << 32)
TRAP-TYPE
.1.3.6.1.4.1.11.2.23.35.0.10521
hpevtFailGetXbcGlobSemphrAddrFailure to get the XBC Global Semaphore address. Data Field: (cell num << 56) | (xbc << 32)
TRAP-TYPE
.1.3.6.1.4.1.11.2.23.35.0.10523
hpevtFailWrtXbcGlobSemphrFailed to write the XBC Global Semaphore. Data Field: (cell num << 56) | (xbc << 32)
TRAP-TYPE
.1.3.6.1.4.1.11.2.23.35.0.10524
hpevtFailRdXbcGlobSemphrFailed to read the XBC Global Semaphore. Data Field: (cell num << 56) | (xbc << 32)
TRAP-TYPE
.1.3.6.1.4.1.11.2.23.35.0.10528
hpevtFailGetAddrXbcGlobSemphrFailed to get the address of the XBC Global Semaphore. Data Field: (cell num << 56) | (xbc << 32)
TRAP-TYPE
.1.3.6.1.4.1.11.2.23.35.0.10529
hpevtFailWrtXbcGlobSemphrAfrRlsFailed to write the XBC Global Semaphore. Data Field: (cell num << 56) | (xbc << 32)
TRAP-TYPE
.1.3.6.1.4.1.11.2.23.35.0.10530
hpevtFailRelXbcGlobSemphrFailed to release the XBC Global Semaphore. Data Field: (cell num << 56) | (xbc << 32)
TRAP-TYPE
.1.3.6.1.4.1.11.2.23.35.0.10532
hpevtFabPhsExeInvlOrdrFabric phases have been executed in an invalid order
TRAP-TYPE
.1.3.6.1.4.1.11.2.23.35.0.10534
hpevtFabPhsExeInvlOrdrDatExpctPhsFabric phases have been executed in an invalid order. Data field indicates the expected phase.
TRAP-TYPE
.1.3.6.1.4.1.11.2.23.35.0.10535
hpevtFailGetAddrXbcToXbcLnkFailed to get an address when opening XBC to XBC links. Data field is return value from GetAlbAddrBlk function. Internal debug only.
TRAP-TYPE
.1.3.6.1.4.1.11.2.23.35.0.10558
hpevtFailOpnFabLnkFailed to open a fabric link. Data field: [31:0] - error status from OpenFabricLink [39:32] - XBC ID [51:44] - XBC port number
TRAP-TYPE
.1.3.6.1.4.1.11.2.23.35.0.10559
hpevtErrWrtXbcRetRoutError when writing the XBC return route. Data field: [31:0] - error status from WriteRouteReg [39:32] - XBC ID [51:44] - XBC port number
TRAP-TYPE
.1.3.6.1.4.1.11.2.23.35.0.10560
hpevtErrEnblXbcRetRoutError enabling the XBC return route. Data field: [31:0] - error status from WriteRouteEnable [39:32] - XBC ID [51:44] - XBC port number
TRAP-TYPE
.1.3.6.1.4.1.11.2.23.35.0.10561
hpevtFailDisprsRoutAcrssLnkfailed to disperse the routes across links. Data field: [31:0] - error status from GetDispersedOutboundPort [39:32] - XBC ID [51:44] - XBC port number
TRAP-TYPE
.1.3.6.1.4.1.11.2.23.35.0.10564
hpevtErrSetXbcToXbcLnkRoutXError setting up XBC-XBC link for routing across it. Data field: [31:0] - error status from SetupXbcToXbcLinks [39:32] - XBC ID [51:44] - XBC port number
TRAP-TYPE
.1.3.6.1.4.1.11.2.23.35.0.10565
hpevtErrRoutRemtsideError while routing the remote side of a route. Data field: [31:0] - error status from RouteRemoteXbcPort [39:32] - XBC ID [51:44] - XBC port number [59:52] - Destination cell number:
TRAP-TYPE
.1.3.6.1.4.1.11.2.23.35.0.10566
hpevtErrGetAddrRoutRemtXbcError getting address while routing the remote XBC. Data field: [31:0] - error status from GetAlbAddrBlk [39:32] - XBC ID [51:44] - XBC port number
TRAP-TYPE
.1.3.6.1.4.1.11.2.23.35.0.10567
hpevtErrGetNgbrInfoError getting the neighbor info. Data field: [31:0] - error status from AlbGetNeighborInfo [39:32] - XBC ID [51:44] - XBC port number
TRAP-TYPE
.1.3.6.1.4.1.11.2.23.35.0.10568
hpevtErrFindShrtRoutError finding the shortest route. Most likely a firmware error or data corruption. Data field: [31:0] - error status from VM_FindShortestRoute [39:32] - Destination XBC ID [59:52] - Destination Cell number
TRAP-TYPE
.1.3.6.1.4.1.11.2.23.35.0.10569
hpevtErrWrtRemtXbcRoutRegerror writing the remote XBC routing register. Data field: [31:0] - error status from WriteRouteReg [39:32] - XBC ID [51:44] - XBC port number [59:52] - Destination cell number
TRAP-TYPE
.1.3.6.1.4.1.11.2.23.35.0.10570
hpevtErrEnblRoutRemtXbcerror enabling the routes on the remote XBC. Data field: [31:0] - error status from WriteRouteEnable [39:32] - XBC ID [51:44] - XBC port number [59:52] - Destination cell number
TRAP-TYPE
.1.3.6.1.4.1.11.2.23.35.0.10571
hpevtErrWrtRoutRegLocXbcError writing the routing register on the local XBC. Data field: [31:0] - error status from WriteRouteReg [39:32] - XBC ID [51:44] - XBC port number
TRAP-TYPE
.1.3.6.1.4.1.11.2.23.35.0.10572
hpevtErrWrtLocXbcRoutRegRchRemtCelError writing the local XBC routing registers to reach a remote cell. Data field: [31:0] - error status from WriteRouteReg [39:32] - XBC ID [51:44] - XBC port number
TRAP-TYPE
.1.3.6.1.4.1.11.2.23.35.0.10573
hpevtErrEnblLocXbcRoutError enabling the local XBC routes. Data field: [31:0] - error status from WriteRouteEnable [39:32] - XBC ID [51:44] - XBC port number
TRAP-TYPE
.1.3.6.1.4.1.11.2.23.35.0.10574
hpevtSynGrphFailPhs4SynchGraphs() failed during Arches Fabric Phase 4. Data field: return value from SynchGraphs()
TRAP-TYPE
.1.3.6.1.4.1.11.2.23.35.0.10617
hpevtVmVertxFailSyncGrphVM_DeleteVertex() failed in SynchGraphs(). Data field: (vertex id << 32) | (vertex type << 56) | (return value from VM_DeleteVertex())
TRAP-TYPE
.1.3.6.1.4.1.11.2.23.35.0.10619
hpevtVmEdgFailFncSyncGrphVM_DeleteEdge() failed in the Arches Fabric function SynchGraphs(). Data field:(vertex id1 << 32) | (vertex port1 << 48) | (vertex type1 << 56) | (vertex id2 << 0) | (vertex port2 << 16) | (vertex type2 << 24)
TRAP-TYPE
.1.3.6.1.4.1.11.2.23.35.0.10620
hpevtUnexpctErrCalVertxModUnexpected error when calling an Arches Fabric vertex module function. Data field: return value from vertex module function
TRAP-TYPE
.1.3.6.1.4.1.11.2.23.35.0.10621
hpevtUnexpctRetVertxModCopCelGrphUnexpected return from an Arches Fabric vertex module function while copying a cell's graph. Data field: return value from vertex module function
TRAP-TYPE
.1.3.6.1.4.1.11.2.23.35.0.10622
hpevtChecksumPdtFailedThe checksum update for the PDT has failed.
TRAP-TYPE
.1.3.6.1.4.1.11.2.23.35.0.10623
hpevtChecksumNvmBadThe checksum in the memory area of NVM is bad. Memory NVM will be cleared.
TRAP-TYPE
.1.3.6.1.4.1.11.2.23.35.0.10625
hpevtChecksumCalcFailedChecksum calculation failed.
TRAP-TYPE
.1.3.6.1.4.1.11.2.23.35.0.10626
hpevtSalandBmcTokenBadThe BMC copy and SAL copy of the token specified in the data field has been initialized from the default value for the token due to an IPMI error and SAL NVM error.
TRAP-TYPE
.1.3.6.1.4.1.11.2.23.35.0.10628
hpevtBkPlaneCableDetected incompatibility between the cell board and the I/O backplane and/or I/O backplane cables.
TRAP-TYPE
.1.3.6.1.4.1.11.2.23.35.0.10629
hpevtFparUnusableThe fPar identified by the event detail will be unusable. Other events may preceded this event which will help to diagnose the failure. A possible cause is that the system exhausted unused NVRAM.
TRAP-TYPE
.1.3.6.1.4.1.11.2.23.35.0.10698
hpevtFWoutOfNvramFirmware is out of NVRAM and cannot built the ILM memory slice device map
TRAP-TYPE
.1.3.6.1.4.1.11.2.23.35.0.10702
hpevtNvramCPUCorruptThe NVRAM for the CPU map is corrupt and cannot be trusted. It appears that there are more CPUs in the map than the size of the map can hold.
TRAP-TYPE
.1.3.6.1.4.1.11.2.23.35.0.10703
hpevtNvramIOCorruptThe NVRAM for the IO device ownership map is corrupt and cannot be trusted. It appears that there are more IO devices in the map than the size of the map can hold.
TRAP-TYPE
.1.3.6.1.4.1.11.2.23.35.0.10704
hpevtNvramLocMemCorruptThe NVRAM for the cell local memory map is corrupt and cannot be trusted. It appears that there are more memory slices in the map than the size of the map can hold.
TRAP-TYPE
.1.3.6.1.4.1.11.2.23.35.0.10705
hpevtFWInconsistExistAn internal firmware inconsistency exists or the server exhausted its internal resources and is unable to create an fPars EFI ownership variable for a CPU device in the partition. Either of these conditions is fatal.
TRAP-TYPE
.1.3.6.1.4.1.11.2.23.35.0.10706
hpevtFWUnableCreatefParsIOAn internal firmware inconsistency exists or the server exhausted its internal resources and is unable to create an fPars EFI ownership variable for an IO device in the partition. Either of these conditions is fatal.
TRAP-TYPE
.1.3.6.1.4.1.11.2.23.35.0.10707
hpevtFWUnableCreatefParsCLMAn internal firmware inconsistency exists or the server exhausted its internal resources and is unable to create an fPars EFI ownership variable for a CLM device in the partition. Either of these conditions is fatal.
TRAP-TYPE
.1.3.6.1.4.1.11.2.23.35.0.10708
hpevtFWOutOfNvramFirmware has run out of NVRAM and cannot create the needed variable(s)
TRAP-TYPE
.1.3.6.1.4.1.11.2.23.35.0.10771
hpevtFWLbaReconfigFailThe call to the IOC firmware component method 'LbaReconfig' failed, probably a low-level hardware error. The fPar BSP is identified in bits 63..32 of the event detail, the fPar owning this CPU and LBA is identified in bits 31..16 and the number of the Rope is identified in bits 15..0.
TRAP-TYPE
.1.3.6.1.4.1.11.2.23.35.0.10772
hpevtCpuModuleBadConfigThe CPU modules have been installed in an illegal configuration on the cell board.
TRAP-TYPE
.1.3.6.1.4.1.11.2.23.35.0.10779
hpevtCpuInvalidTerminatorAn invalid CPU terminator card is installed on the cell board. The data field indicates the physical location of the offending socket.
TRAP-TYPE
.1.3.6.1.4.1.11.2.23.35.0.10780
hpevtInvocationSoftResetCodeInvocation of the soft reset code from an interrupt or similar vector, or improper locking/releasing of semaphores.
TRAP-TYPE
.1.3.6.1.4.1.11.2.23.35.0.10793
hpevtDataSm4SelfResetData field is count of cpus held by the sm4 which issues the event (and is trying to reset itself). Indicates invocation of the SoftResetCpu code from an interrupt or similar vector where the processor was modifying critical resources, or improper locking/releasing of semaphores.
TRAP-TYPE
.1.3.6.1.4.1.11.2.23.35.0.10794
hpevtfParsfailRelseResrceA reset of an fPar discovered that an fPar failed to release critical resources within a reasonable time.
TRAP-TYPE
.1.3.6.1.4.1.11.2.23.35.0.10795
hpevtPFMManyErrorsSignificant numbers of corrected memory errors have been detected on the memory subsystem
TRAP-TYPE
.1.3.6.1.4.1.11.2.23.35.0.10814
hpevtPFMOverTempProcOver-temperature condition detected on a processor
TRAP-TYPE
.1.3.6.1.4.1.11.2.23.35.0.10822
hpevtPFMCacheErrorProcCache errors detected on a processor
TRAP-TYPE
.1.3.6.1.4.1.11.2.23.35.0.10823
hpevtPFMCorrecErrorCacheCorrected errors detected in the cache portion of the memory for a processor module
TRAP-TYPE
.1.3.6.1.4.1.11.2.23.35.0.10824
hpevtPFMCorrErrSysBusCorrected errors detected on the system bus for a processor module
TRAP-TYPE
.1.3.6.1.4.1.11.2.23.35.0.10825
hpevtPFMCorrErrProcBusCorrected errors detected on the processor bus for a processor module
TRAP-TYPE
.1.3.6.1.4.1.11.2.23.35.0.10826
hpevtPFMErrTagMemProcCorrected errors detected in the tag portion of the memory for a processor module
TRAP-TYPE
.1.3.6.1.4.1.11.2.23.35.0.10827
hpevtfParsNotEnableBootfPars-mode EFI variable is set to enable fPars operation but no fPars are actually enabled to boot. So the server boots in hard partition mode.
TRAP-TYPE
.1.3.6.1.4.1.11.2.23.35.0.10830
hpevtfParsNotRecveOwnShipAn fPar was directed to reset using the ESIT DirectedfParResetAndMigrate() service but the target (recipient) fPar of the resources is in a state that cannot receive ownership of these resources.
TRAP-TYPE
.1.3.6.1.4.1.11.2.23.35.0.10832
hpevtFWErrSetNvramValFirmware error setting the NVRAM value of preferred-bsp for the vPars monitor. The partition will boot using the PD monarch, but the value of preferred-bsp may not match this CPU.
TRAP-TYPE
.1.3.6.1.4.1.11.2.23.35.0.10833
hpevtUnablWrtXbcPrtRoutTblEnblMskUnable to write to an XBC port ROUTE_TABLE_ENABLE_MASK CSR in Arches Fabric Phase3. Data field: (XBC port << 48) | (XBC ID < 32) | (route)
TRAP-TYPE
.1.3.6.1.4.1.11.2.23.35.0.10842
hpevtProcessIntrptUnRecoverbleAn unrecoverable processor interrupt occurred. IPF firmware owned the processor interrupt vector table (IVT) at the time of the interrupt.
TRAP-TYPE
.1.3.6.1.4.1.11.2.23.35.0.10853
hpevtSBASetDevMaskFailSBA call to LBA SetDeviceMask method fails.
TRAP-TYPE
.1.3.6.1.4.1.11.2.23.35.0.10871
hpevtLBASlotDevScanErrLBA slot device scan error
TRAP-TYPE
.1.3.6.1.4.1.11.2.23.35.0.10927
hpevtInadequateMemTofParThere is none (or inadequate) memory slice resource assigned to the fPar so it cannot boot its instance. The fPar will be disabled (enter a spinloop) because it cannot boot, or if in vPars mode will return control to the monitor.
TRAP-TYPE
.1.3.6.1.4.1.11.2.23.35.0.10936
hpevtFailCollVertxInfoCouldn't collect vertex information during Fabric Info call. Data Field: return status
TRAP-TYPE
.1.3.6.1.4.1.11.2.23.35.0.10937
hpevtFailCollVertxFabInfoCallCouldn't collect the vertices during the Fabric Info call. Data Field: number of vertices returned
TRAP-TYPE
.1.3.6.1.4.1.11.2.23.35.0.10938
hpevtFailFndEdgeProcCallCouldn't find all the edges during a procedure call. Data Field: return status
TRAP-TYPE
.1.3.6.1.4.1.11.2.23.35.0.10939
hpevtFailFndEdgProcCallCouldn't find an appropriate number of edges during a procedure call. Data Field: the number of edges found
TRAP-TYPE
.1.3.6.1.4.1.11.2.23.35.0.10940
hpevtManyEdgEncntProcCallToo many edges were encountered during a procedure call. Data Field: link count
TRAP-TYPE
.1.3.6.1.4.1.11.2.23.35.0.10941
hpevtFailGetAddrProcCallFailed to get an address during a procedure call. Data Field: return status
TRAP-TYPE
.1.3.6.1.4.1.11.2.23.35.0.10943
hpevtUnexpctStatEncntProcCallAn unexpected state was encountered during a procedure call. Data Field: state returned
TRAP-TYPE
.1.3.6.1.4.1.11.2.23.35.0.10944
hpevtUnablGetLnkHlthStatProcCallUnable to get the link health state during a procedure call. Data Field: (cell num << 56) | (port << 44) | (xbc << 32)
TRAP-TYPE
.1.3.6.1.4.1.11.2.23.35.0.10945
hpevtFabDatFailCrcChkThe fabric data failed a CRC check. Data Field: (xbc port << 44 ) | (xbc << 32) | return status)
TRAP-TYPE
.1.3.6.1.4.1.11.2.23.35.0.10946
hpevtVmCollVertcFailUnexpctVM_CollectVertices failed unexpectedly. Could possibly be a data corruption problem. Data field: (cell number << 56) | (return value from VM_CollectVertices)
TRAP-TYPE
.1.3.6.1.4.1.11.2.23.35.0.11032
hpevtUnablGenAlbArfSetCsrUnable to generate an ALB address in Arches Fabric ArfSetDefaultCSRs() function. Data field:(cell number << 56) | (port number << 48) | (xbc ID < 32) | (return value)
TRAP-TYPE
.1.3.6.1.4.1.11.2.23.35.0.11033
hpevtSetDefCsrFailUnexpctSetDefaultCSRs function failed unexpectedly. Arches Fabric was unable to set XBC CSRs to default values. Data field: return value from SetDefaultCSRs
TRAP-TYPE
.1.3.6.1.4.1.11.2.23.35.0.11034
hpevtEncntErrRoutA problem was encountered while routing which prevented an appropriate route from being chosen. Data Field: Destination Cell << 56 | XBC Port << 44 | XBC # << 32 | return status
TRAP-TYPE
.1.3.6.1.4.1.11.2.23.35.0.11038
hpevtEncntErrRoutFabAn error was encountered while routing the fabric. This error prevents an appropriate route from being selected. Data Field: Destination Cell << 56 | XBC Port << 44 | XBC # << 32 | return status
TRAP-TYPE
.1.3.6.1.4.1.11.2.23.35.0.11039
hpevtErrEncntRoutFabPrvntRoutSelAn error was encountered while routing the fabric. This error prevents an appropriate route from being selected. Data Field: Destination Cell << 56 | XBC Port << 44 | XBC # << 32 | return status
TRAP-TYPE
.1.3.6.1.4.1.11.2.23.35.0.11040
hpevtInvlPrtRetRoutXbcCcLnkAn invalid port number was returned when selecting a route for the XBC-CC link. Data Field: (destination cell 56) | (xbc port 44) | (xbc # 32) | port selected
TRAP-TYPE
.1.3.6.1.4.1.11.2.23.35.0.11041
hpevtErrEncntRoutFabPrvntRoutSelSwAn error was encountered while routing the fabric. This error prevents an appropriate route from being selected. Data Field: Destination Cell << 56 | XBC Port << 44 | XBC # << 32 | switch fabric
TRAP-TYPE
.1.3.6.1.4.1.11.2.23.35.0.11042
hpevtSecndFlshNotProgrmValidImgThe second flash part is not programmed with a valid image
TRAP-TYPE
.1.3.6.1.4.1.11.2.23.35.0.11052
hpevtSysBckPlnPwr1p2LDOFaultSystem backplane power has reported a 1.2v LDO fault. The data field contains the physical location of the fault.
TRAP-TYPE
.1.3.6.1.4.1.11.2.23.35.0.11452
hpevtSysBckPlnPwr2p5LDOFaultSystem backplane power has reported a 2.5v LDO fault. The data field contains the physical location of the fault.
TRAP-TYPE
.1.3.6.1.4.1.11.2.23.35.0.11454
hpevtSysBckPlnPwr3p3HseFaultSystem backplane power has reported a 3.3v house keeping power fault. The data field contains the physical location of the fault.
TRAP-TYPE
.1.3.6.1.4.1.11.2.23.35.0.11456
hpevtSysBckPlnPwr12FaultSystem backplane power has reported a 12v power fault. The data field contains the physical location of the fault.
TRAP-TYPE
.1.3.6.1.4.1.11.2.23.35.0.11459
hpevtSysBckPlnPwr3p3FaultSystem backplane power has reported a 3.3v power fault. The data field contains the physical location of the fault.
TRAP-TYPE
.1.3.6.1.4.1.11.2.23.35.0.11461
hpevtSysBckPlnPwr1p5FaultSystem backplane power has reported a 1.5v power fault. The data field contains the physical location of the fault.
TRAP-TYPE
.1.3.6.1.4.1.11.2.23.35.0.11463
hpevtSysBckPlnPwr2p5FaultSystem backplane power has reported a 2.5v power fault. The data field contains the physical location of the fault.
TRAP-TYPE
.1.3.6.1.4.1.11.2.23.35.0.11465
hpevtPwrRailPrvInsuffPwrToBckPlnOne or more power rails is providing insufficient power to the backplane.
TRAP-TYPE
.1.3.6.1.4.1.11.2.23.35.0.11467
hpevtRcsNoProvClkBckPlnClock fault for clocks supplied from the Redundant Clock Source (RCS) board to the system backplane. RCS board is no longer providing clocks to the backplane. The data field contains the physical location of the RCS.
TRAP-TYPE
.1.3.6.1.4.1.11.2.23.35.0.11468
hpevtHsoFaultOrRemvClock fault for clocks supplied from the Hot Swap Oscillator (HSO) board to the system backplane. HSO has reported a fault or has been removed. The data field contains the physical location of the HSO.
TRAP-TYPE
.1.3.6.1.4.1.11.2.23.35.0.11471
hpevtOpClkNoMtchRcsHsoThe operational clock frequencies do not match between the Redundant Clock Source (RCS) and the Hot Swap Oscillator (HSO). The data field contains the physical location of the HSO.
TRAP-TYPE
.1.3.6.1.4.1.11.2.23.35.0.11478
hpevtClkMrgnBckPlnFailThe clock margin of the system backplane failed.
TRAP-TYPE
.1.3.6.1.4.1.11.2.23.35.0.11479
hpevtHsoNoRedundSystem backplane Hot Swap Oscillator (HSO) boards are NOT redundant.
TRAP-TYPE
.1.3.6.1.4.1.11.2.23.35.0.11481
hpevtHsoInsuffSystem backplane Hot Swap Oscillator (HSO) boards are insufficient.
TRAP-TYPE
.1.3.6.1.4.1.11.2.23.35.0.11482
hpevtFailRdRcsHsoFailure reading Redundant Clock Source (RCS) or Hot Swap Oscillator HSO boards EEPROM. Data field contains the physical location of the device.
TRAP-TYPE
.1.3.6.1.4.1.11.2.23.35.0.11483
hpevtFailWrtRcsHsoFailure writing Redundant Clock Source (RCS) or Hot Swap Oscillator HSO boards EEPROM. Data field contains the physical location of the device
TRAP-TYPE
.1.3.6.1.4.1.11.2.23.35.0.11484
hpevtFailRdRpmFailure reading the Reset and Power Monitors (RPM) EEPROM. Data field contains the physical location of the device.
TRAP-TYPE
.1.3.6.1.4.1.11.2.23.35.0.11485
hpevtFailWrtRpmFailure writing the Reset and Power Monitors (RPM) EEPROM. Datafield contains the physical location of the device
TRAP-TYPE
.1.3.6.1.4.1.11.2.23.35.0.11486
hpevtFailRdOspFailure reading the Onboard System Programmers (OSP) EEPROM. Datafield contains the physical location of the device
TRAP-TYPE
.1.3.6.1.4.1.11.2.23.35.0.11487
hpevtFailWrtOspFailure writing the Onboard System Programmers (OSP) EEPROM. Datafield contains physical location of the device
TRAP-TYPE
.1.3.6.1.4.1.11.2.23.35.0.11488
hpevtSbsFaultStrtSerial Bit Stream (SBS) fault on startup. An SBS fault results in the MOAB's not being configured correctly.
TRAP-TYPE
.1.3.6.1.4.1.11.2.23.35.0.11489
hpevtFailRdIObckPlnLpmFailure reading IO backplane LPM. Datafield contains the physical location of the device.
TRAP-TYPE
.1.3.6.1.4.1.11.2.23.35.0.11495
hpevtFailWrtIOBckPlnLpmFailure writing IO backplane LPM. Datafield contains physical location of device.
TRAP-TYPE
.1.3.6.1.4.1.11.2.23.35.0.11496
hpevtSysSoftViolateWellBhaveRuleThe system software violated one of the 'well-behavedness' rules of soft partitions and tried to call a firmware procedure within the firmware instance of a sibling. This is an access violation and firmware rejects the call
TRAP-TYPE
.1.3.6.1.4.1.11.2.23.35.0.11515
hpevtAlbInitPrepUnablRdAlrecConfigAlbInitPrep was unable to read the ALREC_CONFIG CSR to determine whether the link is up or not. Data field: unused
TRAP-TYPE
.1.3.6.1.4.1.11.2.23.35.0.11521
hpevtfParIsDisbleFrmBootThe fPar whose ID is identified in the event detail is disabled from booting because it has no bootable, healthy CPU. It may not own any CPU or the CPUs it owns are Unhealthy (or deconfigured)
TRAP-TYPE
.1.3.6.1.4.1.11.2.23.35.0.11529
hpevtfParNotInstantiateFWNon-critical event announces that an fPar is enabled to boot but has inadequate memory resources to instantiate the firmware for the fPar. The configuration is modified to disable but not delete this fPar.
TRAP-TYPE
.1.3.6.1.4.1.11.2.23.35.0.11530
hpevtfParNotHaveIOResrcThe fPar has been enabled to boot, and contains at least one CPU and adequate memory but has not been given any IO resources. The soft partition (fPar) may therefore only boot as far as the EFI shell. It must be reconfigured and reset before it may boot an operating system.
TRAP-TYPE
.1.3.6.1.4.1.11.2.23.35.0.11531
hpevtCPUsDeconfigAll CPUs were scheduled to be deconfigured
TRAP-TYPE
.1.3.6.1.4.1.11.2.23.35.0.11537
hpevtCPUsReconfigAll CPUs have been auto reconfigured
TRAP-TYPE
.1.3.6.1.4.1.11.2.23.35.0.11538
hpevtIOBckPln33VFailIO Backplane 3.3V power fault
TRAP-TYPE
.1.3.6.1.4.1.11.2.23.35.0.11566
hpevtBckPln5VFailIO Backplane 5.0V power fault
TRAP-TYPE
.1.3.6.1.4.1.11.2.23.35.0.11567
hpevtIOBckPlnNeg12VFailIO Backplane -12V power fault
TRAP-TYPE
.1.3.6.1.4.1.11.2.23.35.0.11568
hpevtIOBckPln12VFailIO Backplane +12V power fault
TRAP-TYPE
.1.3.6.1.4.1.11.2.23.35.0.11569
hpevtIOBckPln15VTempFailIO Backplane 1.5V temperature fault
TRAP-TYPE
.1.3.6.1.4.1.11.2.23.35.0.11575
hpevtIOBckPln33VTempFailIO Backplane 3.3V temperature fault
TRAP-TYPE
.1.3.6.1.4.1.11.2.23.35.0.11576
hpevtIOBckPlnNeg12VTempFailIO Backplane -12.0V temperature fault
TRAP-TYPE
.1.3.6.1.4.1.11.2.23.35.0.11578
hpevtIOBckPln12VTempFailIO Backplane +12.0V temperature fault
TRAP-TYPE
.1.3.6.1.4.1.11.2.23.35.0.11579
hpevtLocCelUnablClrLnkOffBitThe local cell was unable to clear the link_off bit on at least one CC-CC link. Data field: return value of Phase3BackToBackPrep()
TRAP-TYPE
.1.3.6.1.4.1.11.2.23.35.0.11580
hpevtArfOlaPreRendezUnablRchCelArfOLAPreRendez() was unable to reach the added cell. Data field: bitmap of unreachable cells
TRAP-TYPE
.1.3.6.1.4.1.11.2.23.35.0.11581
hpevtUnexpctErrSetNctTblAn unexpected error occurred in SetupNCTable(). Data field: return value from SetupNCTable()
TRAP-TYPE
.1.3.6.1.4.1.11.2.23.35.0.11582
hpevtPhs4UnexpctFailPhase4BackToBackPrep() unexpectedly failed. Data field: return value of Phase4BackToBackPrep()
TRAP-TYPE
.1.3.6.1.4.1.11.2.23.35.0.11583
hpevtUnablSyncGrphCellData field: (master cell number << 56) | (bitmap of cells to synch)
TRAP-TYPE
.1.3.6.1.4.1.11.2.23.35.0.11584
hpevtBitMapUnrchCelData field: bitmap of unreachable cells.
TRAP-TYPE
.1.3.6.1.4.1.11.2.23.35.0.11585
hpevtRetValNctCohTblData field: return value from SetupNCTable() or SetupCohTable()
TRAP-TYPE
.1.3.6.1.4.1.11.2.23.35.0.11586
hpevtArfRoutEnblRetErrLocCelData field: (local cell number << 56) | (bitmap of routes to enable)
TRAP-TYPE
.1.3.6.1.4.1.11.2.23.35.0.11597
hpevtArfRoutDisRetErrOlaData field: (bitmap of cells << 32) | (bitmap of routes to disable)
TRAP-TYPE
.1.3.6.1.4.1.11.2.23.35.0.11598
hpevtArfRoutDisRetErrArfPhs4Data field: (bitmap of source cells << 32) | (bitmap of routes to disable)
TRAP-TYPE
.1.3.6.1.4.1.11.2.23.35.0.11599
hpevtMemAlloctFailMemory allocation failed. The data is the size of the memory block which could not be allocated.
TRAP-TYPE
.1.3.6.1.4.1.11.2.23.35.0.11603
hpevtMemLockFailMemory locking failed. The data is the size of the memory block which could not be locked.
TRAP-TYPE
.1.3.6.1.4.1.11.2.23.35.0.11604
hpevtMinProcReqMoreThanAvailThe minimum number of processors required is more than the number available. The data is the number of available processors.
TRAP-TYPE
.1.3.6.1.4.1.11.2.23.35.0.11605
hpevtVMNotHandlGuestOSPerfThe guest operating system performed an operation which could not be handled by the virtual machine. The virtual machine could not continue running the guest so it stopped.
TRAP-TYPE
.1.3.6.1.4.1.11.2.23.35.0.11607
hpevtKernlDrvFailLckMemKernel driver failed to lock memory
TRAP-TYPE
.1.3.6.1.4.1.11.2.23.35.0.11696
hpevtMMIOmapFndInfoInTbleThe code which initializes the MMIO/IOP map found that the table already contained information.
TRAP-TYPE
.1.3.6.1.4.1.11.2.23.35.0.11700
hpevtAttmptAddPCImoreThanAllowAn attempt was made to add a PCI bus with a number greater than the maximum allowed.
TRAP-TYPE
.1.3.6.1.4.1.11.2.23.35.0.11702
hpevtCPUConfigNotSupprtThe configured CPU generation is not supported
TRAP-TYPE
.1.3.6.1.4.1.11.2.23.35.0.11703
hpevtISAUARTcreatWithoutDatStrctAn ISA UART was created without a data structure. A PCI UART structure exists
TRAP-TYPE
.1.3.6.1.4.1.11.2.23.35.0.11705
hpevtTCGETorIOCTLFailA TCGETS or TCSETS IOCTL failed. The errno status will be in a subsequent event.
TRAP-TYPE
.1.3.6.1.4.1.11.2.23.35.0.11706
hpevtStatCallPMANFailA stat call on the PMAN failed. The next event contains the failure errno.
TRAP-TYPE
.1.3.6.1.4.1.11.2.23.35.0.11707
hpevtVMDrvNotOpenThe virtual machine driver could not be opened
TRAP-TYPE
.1.3.6.1.4.1.11.2.23.35.0.11708
hpevtVMDrvNotCreatVMThe virtual machine driver could not create a virtual machine
TRAP-TYPE
.1.3.6.1.4.1.11.2.23.35.0.11709
hpevtNotAbleCreatNodeForCommCould not create a file system node for communication between the vmm driver and the virtual machine. The next event contains the error from the Unix system call.
TRAP-TYPE
.1.3.6.1.4.1.11.2.23.35.0.11710
hpevtVMNotOpenThe vm device was created but cannot be opened
TRAP-TYPE
.1.3.6.1.4.1.11.2.23.35.0.11711
hpevtVMDrvNotLoadThe virtual machine driver has not been loaded
TRAP-TYPE
.1.3.6.1.4.1.11.2.23.35.0.11712
hpevtCreatThreadPMANFailAn attempt to create a thread on the PMAN has failed. The next event contains the Unix error number.
TRAP-TYPE
.1.3.6.1.4.1.11.2.23.35.0.11718
hpevtVMDrvUnableCommVMVM Driver was unable to communicate with virtual machine
TRAP-TYPE
.1.3.6.1.4.1.11.2.23.35.0.11719
hpevtConfigUnableToRdThe configuration file could not be read
TRAP-TYPE
.1.3.6.1.4.1.11.2.23.35.0.11720
hpevtMemAllocFWTblFailMemory allocation for a firmware table has failed. The data contains the name of the firmware table.
TRAP-TYPE
.1.3.6.1.4.1.11.2.23.35.0.11721
hpevtDrvUnableBldMapTblDriver was unable to build map tables
TRAP-TYPE
.1.3.6.1.4.1.11.2.23.35.0.11723
hpevtVMRebootFailReboot failed. The virtual machine will exit.
TRAP-TYPE
.1.3.6.1.4.1.11.2.23.35.0.11724
hpevtSetIntlCohTblRetErrData field: (cell set << 32) | (return value from SetupInitialCohTables())
TRAP-TYPE
.1.3.6.1.4.1.11.2.23.35.0.11775
hpBootStblStoreFlashErrStable store read or write to flash failed.
TRAP-TYPE
.1.3.6.1.4.1.11.2.23.35.0.11780
hpBootStblStoreNvMErrError reading or writing the stable store NVM area
TRAP-TYPE
.1.3.6.1.4.1.11.2.23.35.0.11783
hpevtFWDetectilleglMemConfigSFW has detected an illegal memory config using 4GB DIMMs. The system will be halted
TRAP-TYPE
.1.3.6.1.4.1.11.2.23.35.0.11784
hpevtSFWFailAllotNVMSFW component NVM space is not big enough to store all it data. Check the ASCII data field to determine which component caused the error.
TRAP-TYPE
.1.3.6.1.4.1.11.2.23.35.0.11788
hpevtSFWFailAllotSCRRAMSFW component does not allocate enough SCR ram space to store it data.
TRAP-TYPE
.1.3.6.1.4.1.11.2.23.35.0.11789
hpevtSetIntlCohRetErrArfPhs3Data field: cell set [63:32], return value [31:0]
TRAP-TYPE
.1.3.6.1.4.1.11.2.23.35.0.11797
hpevtErrWrtErrMskAlrecAlTranData field: cell ID [63:56], port num [55:44], XBC ID [43:32]
TRAP-TYPE
.1.3.6.1.4.1.11.2.23.35.0.11807
hpevtFwUnexpctIntrnlErrVertxData field: vType1 [63:56] | vPort1 [55:48] | vId1 [47:32] | vType2 [31:24] | vPort2 [23:16] | vId2 [15:0]
TRAP-TYPE
.1.3.6.1.4.1.11.2.23.35.0.11840
hpOsUnsupportedWmixedCpuRevsThe OS being booted is not supported in a partition containing a mix of processor stepping revisions.
TRAP-TYPE
.1.3.6.1.4.1.11.2.23.35.0.11850
hpevtFwUnexpctErrSetLnkData field: vType1 [63:56] | vPort1 [55:48] | vId1 [47:32] | vType2 [31:24] | vPort2 [23:16] | vId2 [15:0]
TRAP-TYPE
.1.3.6.1.4.1.11.2.23.35.0.11851
hpevtFwUnbleWrtSkyGlobLnkSelCohData field: cell num [63:56] | link sel coh CSR (0 or 1) [0:0]
TRAP-TYPE
.1.3.6.1.4.1.11.2.23.35.0.11863
hpOsBootDisabledWmixedCpuKeysThe OS suitable for booting in this mode does not support booting in the current configuration due to the existence of cpus of differing revisions.
TRAP-TYPE
.1.3.6.1.4.1.11.2.23.35.0.11870
hpevtSysFwErrUpdtLnkSystem firmware experienced an error while updating the link sel value. Data field indicates return status
TRAP-TYPE
.1.3.6.1.4.1.11.2.23.35.0.11885
hpevtFabUnablGenSkyCsrAddrFabric was unable to generate a Skyline CSR address Data field: cell number [63:56] and return value from address function [31:0]
TRAP-TYPE
.1.3.6.1.4.1.11.2.23.35.0.11904
hpevtFwUnablGenSkyCsrAdrrFirmware was unable to generate a Skyline CSR address. Data field: cell number [63:56] | return value [31:0]
TRAP-TYPE
.1.3.6.1.4.1.11.2.23.35.0.11905
hpevtNoOSBootRendezTarget CPU receives wakeup interrupt to join the OS but the OS_BOOT_RENDEZ entry point is invalid or none-existent
TRAP-TYPE
.1.3.6.1.4.1.11.2.23.35.0.11932
hpevtChksmFailOSBootRendezThe entry point for OS_BOOT_RENDEZ exists, but fails the checksum test performed by firmware
TRAP-TYPE
.1.3.6.1.4.1.11.2.23.35.0.11933
hpevtSysFWCallPalCopyInfoFailThe System Firmware call to PAL_COPY_INFO failed.
TRAP-TYPE
.1.3.6.1.4.1.11.2.23.35.0.11960
hpevtSysFWCallPalCopyPalFailThe System Firmware call to PAL_COPY_PAL failed.
TRAP-TYPE
.1.3.6.1.4.1.11.2.23.35.0.11961
hpevtSysFWCallPalCacFlusFailThe System Firmware call to PAL_CACHE_FLUSH failed.
TRAP-TYPE
.1.3.6.1.4.1.11.2.23.35.0.11962
hpevtCellNotInitCell on line add/delete is not initialized and cannot be used.
TRAP-TYPE
.1.3.6.1.4.1.11.2.23.35.0.11964
hpevtFPARsCompBrokeIn FPARs mode, cell on line add/delete depends on functionality in the FPARs component. This is either broken or missing.
TRAP-TYPE
.1.3.6.1.4.1.11.2.23.35.0.11966
hpevtFailGetFPARsSemphrCell on line add/delete in FPARs mode failed to get the FPARs semaphore.
TRAP-TYPE
.1.3.6.1.4.1.11.2.23.35.0.11967
hpevtMorThnOneProcCallCellMore than one processor from an FPAR called into cell on line add/delete
TRAP-TYPE
.1.3.6.1.4.1.11.2.23.35.0.11968
hpevtFPARsProcFailRendezAll FPARs processors failed to rendezvous during a cell on line add/delete op
TRAP-TYPE
.1.3.6.1.4.1.11.2.23.35.0.11969
hpevtEncntUnexptErrOLAUnable to setup Skyline LINK_SEL_COHx CSRs on the running partition to the newly added cell. Data field: cell set [63:32] | return val [31:0]
TRAP-TYPE
.1.3.6.1.4.1.11.2.23.35.0.11970
hpevtMCAOccPriorPreMCAThis indicates an MCA happening before a previous MCA was not completely handled.
TRAP-TYPE
.1.3.6.1.4.1.11.2.23.35.0.11971
hpevtMCAInitEvtProcThis indicates an MCA event happening before a previous INIT event was not completely processed.
TRAP-TYPE
.1.3.6.1.4.1.11.2.23.35.0.11972
hpevtUnablFndBadEdgFirmware was unable to find a bad edge in an untraversable route. Data Field: (destCell << 56 | port num < 44 | xbc num << 32 | return status)
TRAP-TYPE
.1.3.6.1.4.1.11.2.23.35.0.11974
hpevtUnknEntityDrwPwrBusSome entity that is not known to the firmware, is drawing power from the bus bars.
TRAP-TYPE
.1.3.6.1.4.1.11.2.23.35.0.11989
hpevtSoftPartNotBootRebooting the partition to nPars because a soft partition could not be booted.
TRAP-TYPE
.1.3.6.1.4.1.11.2.23.35.0.12001
hpevtUnablRotArndBrkLnkFirmware was unable to find a replacement route for the broken link. Data field contains: port << 44, chip id << 32, and number of attempts to find an alternate route
TRAP-TYPE
.1.3.6.1.4.1.11.2.23.35.0.12008
hpevtUnablSetAPERLockData field details the cell that failed to set its bit
TRAP-TYPE
.1.3.6.1.4.1.11.2.23.35.0.12013
hpevtUncorrtMemEccErrOccrIndicates that an uncorrectable ECC error has been encountered, and gives the physical location of the DIMM that had the error.
TRAP-TYPE
.1.3.6.1.4.1.11.2.23.35.0.12017
hpevtErrRetrvCrssbarLnkSystem firmware experienced an error while retrieving the expected neighbor fabric chip for distributing traffic over crossbarl inks. Data Field: (xbc port # << 44) | (xbc # << 32) | return status
TRAP-TYPE
.1.3.6.1.4.1.11.2.23.35.0.12025
hpevtUnablRdCrssbarCould not read crossbar neighbor information during routing. Data Field: (xbc port << 44) | (xbc << 32) | error status
TRAP-TYPE
.1.3.6.1.4.1.11.2.23.35.0.12028
hpevtUnablEstbshCrssbarCould not establish route for local crossbar during route around routing. Data Field: (xbc port << 44) | (xbc << 32) | error status
TRAP-TYPE
.1.3.6.1.4.1.11.2.23.35.0.12029
hpevtNoRoutLocCrssBarAn invalid TPM has been detected in the system and is being use. Security might be compromised. Data field unused.
TRAP-TYPE
.1.3.6.1.4.1.11.2.23.35.0.12047
hpevtInvalidTPMInvalid or unsupported TPM detected in the system. TPM is disabled. Data filed unused
TRAP-TYPE
.1.3.6.1.4.1.11.2.23.35.0.12048
hpevtTPMFailInitFirmware cannot initialize the TPM. TPM related security feature are disabled Data field unused
TRAP-TYPE
.1.3.6.1.4.1.11.2.23.35.0.12049
hpevtCpuTempExceedHiThresA CPU module's temperature has exceed the high temperature threshold or a CPU power module fault has occurred. As a result of this event, the CPU has been inhibited. The Cell must be powered off then on using the MP's PE command before the CPU module will be powered again.
TRAP-TYPE
.1.3.6.1.4.1.11.2.23.35.0.12050
hpevtSFWDetErrStablStorFlshAn error occurred while writing to stable store flash. Data field is unused.
TRAP-TYPE
.1.3.6.1.4.1.11.2.23.35.0.12069
hpevtInlckOpenPCIPwrPCI interlock has been opened with PCI slot power on. The datafield can be decoded as follows (where byte 0 is the rightmost byte): byte offset 2:PCI slot number byte offset 5: IO Chassis number byte offset 6: IO Bay number byte offset 7: Cabinet number
TRAP-TYPE
.1.3.6.1.4.1.11.2.23.35.0.12091
hpevtFaltDetDropRegIOThe specified low dropout regulator on the IO backplane is reporting a fault. The specified power rail is reporting a fault. The number in the slot field of the physical location is the rail number that caused the fault. Rails are: 4 = LDO 2.5v for Esca 0, 5 = LDO 2.5v for Esca 1, 1.5v, 7 = Other backplane 2.5v, 8 = Other backplane 1.2v
TRAP-TYPE
.1.3.6.1.4.1.11.2.23.35.0.12101
hpevtFaltDetDropRegManBckPlneThe specified low dropout regulator on the main backplane is reporting a fault. The number in the slot field of the physical location is the rail number that caused the fault. Rails are: 0 = SysBP xb0 1.5v, 1 = SysBp xb1 1.5v, 2 = SysBp switched 3.3v, 3 = SysBp LDO xb0 2.5v, 4 = SysBp xb1 LDO 2.5v, 5 = SysBp LDO 1.5v br0, 6 = SysBp LDO 1.5v br1
TRAP-TYPE
.1.3.6.1.4.1.11.2.23.35.0.12102
hpevtFaltDetHotswpCoreIOThe hot swap controller for the specified core IO is reporting fault.
TRAP-TYPE
.1.3.6.1.4.1.11.2.23.35.0.12103
hpevtErrRetrvCrssbarChipNmbrAn error occurred while retrieving the crossbar chip number. Data Field: cell number << 56 | port number << 44 | return status
TRAP-TYPE
.1.3.6.1.4.1.11.2.23.35.0.12109
hpevtCellNotCfgCLMModeFor most workloads, the system performance may be degraded if CLM mode is not enabled for all of the cells in a partition. Windows Server 2003 contains additional support to optimize for CLM systems, increasing the performance compared to an interleaved configuration.
TRAP-TYPE
.1.3.6.1.4.1.11.2.23.35.0.12119
hpevttDoblDramInvokeCorrected memory errors have been detected. Double DRAM chip sparing events have been invoked.
TRAP-TYPE
.1.3.6.1.4.1.11.2.23.35.0.12120
hpevtErrCrssbarCrctByHWA error occurred in the crossbar controller and was corrected by the hardware.
TRAP-TYPE
.1.3.6.1.4.1.11.2.23.35.0.12121
hpevtErrCrssChipBckPlnA platform error was detected by the firmware/hardware, and corrected by using a spare channel. The error occurred between the crossbar chips on the backplane(s).
TRAP-TYPE
.1.3.6.1.4.1.11.2.23.35.0.12127
hpevtErrCeLLIOA platform error was detected by the firmware/hardware, and corrected by using a spare channel. The error occurred between the cell controller and the IO controller.
TRAP-TYPE
.1.3.6.1.4.1.11.2.23.35.0.12128
hpevtMltPltFrmErrCellBckPlnMultiple platform errors were detected and corrected by the firmware/hardware. The errors occurred between the cell controller and the backplane.
TRAP-TYPE
.1.3.6.1.4.1.11.2.23.35.0.12129
hpevtMultPltFrmErrCrssChpBckPlnMultiple platform errors were detected and corrected by the firmware/hardware. The errors occurred between the crossbar chips on the backplane(s).
TRAP-TYPE
.1.3.6.1.4.1.11.2.23.35.0.12130
hpevtMultPltFrmErrCeLLIOMultiple platform errors were detected and corrected by the firmware/hardware. The errors occurred between the cell controller and the IO controller.
TRAP-TYPE
.1.3.6.1.4.1.11.2.23.35.0.12131
hpevtServIDNotMatchCabThe server identification information does not match the cabinet type. The server will not power on until this condition is resolved.
TRAP-TYPE
.1.3.6.1.4.1.11.2.23.35.0.12132
hpevtDupDimNumDetectDuplicate DIMM serial numbers have been detected. Data field gives physical location of DIMM. Check for other events specifying other DIMMs with same serial number.
TRAP-TYPE
.1.3.6.1.4.1.11.2.23.35.0.12135
hpevtMPLostUPSThe MP has lost communications with the UPS via SNMP over the LAN
TRAP-TYPE
.1.3.6.1.4.1.11.2.23.35.0.12143
hpevtMPGainLanCommUPSThe MP lan communications with the UPS have been restored.
TRAP-TYPE
.1.3.6.1.4.1.11.2.23.35.0.12144
hpevtUnrecovProcIFAinterptInFWAn unrecoverable processor interrupt occurred while in IPF firmware. The data value is the processor IFA.
TRAP-TYPE
.1.3.6.1.4.1.11.2.23.35.0.12149
hpevtUnrecovProcISRinterptInFWAn unrecoverable processor interrupt occurred while in IPF firmware. The event data is the processor ISR.
TRAP-TYPE
.1.3.6.1.4.1.11.2.23.35.0.12150
hpevtDblChipSpareInvokedSystem firmware has detected and corrected memory errors. Double chip sparing has been invoked to help mitigate this condition.
TRAP-TYPE
.1.3.6.1.4.1.11.2.23.35.0.12153
hpevtExtClkCablRemvFrmCPUCabExternal clock cable has been removed from the CPU cabinet. The data field contains the physical location of the cabinet.
TRAP-TYPE
.1.3.6.1.4.1.11.2.23.35.0.12155
hpevtSysFabEncntLnkErrSystem Fabric encountered a link error after opening up the fabric link
TRAP-TYPE
.1.3.6.1.4.1.11.2.23.35.0.12156
hpevtFatErrOnCelToFabPrt44I32I1Fatal errors are present on a cell's link to the fabric. Data Field: (crossbar port << 44) | (crossbar << 32) | 1
TRAP-TYPE
.1.3.6.1.4.1.11.2.23.35.0.12157
hpevtSysFWgetFabProblmSystem firmware encountered fabric problems. Data Field: (crossbar port << 44) | (crossbar << 32)
TRAP-TYPE
.1.3.6.1.4.1.11.2.23.35.0.12159
hpevtFatErrCelLnkToFabPrt44I32Fatal errors are present on a cell's link to the fabric. Data Field: (crossbar port << 44) | (crossbar << 32)
TRAP-TYPE
.1.3.6.1.4.1.11.2.23.35.0.12160
hpevtSysOSRecovFrmPCIErrL1A PCI error occurred, but the OS recovered.
TRAP-TYPE
.1.3.6.1.4.1.11.2.23.35.0.12161
hpevtSysOSRecovFrmPCIErrL2A PCI error occurred, but the operating system recovered.
TRAP-TYPE
.1.3.6.1.4.1.11.2.23.35.0.12162
hpevtSysOSRecovFrmPCIErrL5A PCI error occurred, but the operating system recovered
TRAP-TYPE
.1.3.6.1.4.1.11.2.23.35.0.12163
hpevtReqPwrOnDeniedThe request to power on, either via MP user interface, power button, or other, was denied by the Onboard Administrator.
TRAP-TYPE
.1.3.6.1.4.1.11.2.23.35.0.12164
hpevtBladeFrcPWonThe blade has been forced to power-on, either via the MP user interface or the power button. The blade did not negotiate with the Onboard Administrator to insure that there was sufficient power for this action.
TRAP-TYPE
.1.3.6.1.4.1.11.2.23.35.0.12165
hpevtMPNotRecvRespEnclMangrThe MP has repeatedly tried to communicate with the Onboard Administrator and has not received any response
TRAP-TYPE
.1.3.6.1.4.1.11.2.23.35.0.12168
hpevtIntrnlSwErr7193This is an internal SW error
TRAP-TYPE
.1.3.6.1.4.1.11.2.23.35.0.12193
hpevtIntrnlSwErr7194This is an internal SFW error
TRAP-TYPE
.1.3.6.1.4.1.11.2.23.35.0.12194
hpevtIntrnlSwErr7195This is an internal SFW error
TRAP-TYPE
.1.3.6.1.4.1.11.2.23.35.0.12195
hpevtIntrnlSwErr7196This is an internal SFW error
TRAP-TYPE
.1.3.6.1.4.1.11.2.23.35.0.12196
hpevtComplxProfNoMtchThere are miscompares in the complex profiles between cells in a partition. Data field is unused, earlier events will give more detail.
TRAP-TYPE
.1.3.6.1.4.1.11.2.23.35.0.12199
hpevtIODevMissCoreAn I/O device is missing from the Core I/O. Internal peripherals may be not accessible.
TRAP-TYPE
.1.3.6.1.4.1.11.2.23.35.0.12204
hpevtFparUnablNotiCPUAn fPar's GPE_EN bits are not set up to handle receiving a CPU migrate. This event is emitted 2 times, the Data field is different each time. 1. Data field: Address of GPE block 2. Data field: bits 31:0 Virtual GPE_EN register (lower byte) bits 63:32 Enable bits needed for successful migrate
TRAP-TYPE
.1.3.6.1.4.1.11.2.23.35.0.12207
hpevtFparUnablNotiCpuIOSAPICredirFSHWA was unable to notify the new owner of a CPU migrate. This event is emitted 2 times: 1. Data field: IOSAPIC Address 2. Data field: Virtual IOSAPIC SCI redir
TRAP-TYPE
.1.3.6.1.4.1.11.2.23.35.0.12208
hpevtOSSetWtchDogTimerToTimeOutThe operating system set the watchdog timer to time out if it was not reset within a specified time. It was not reset and has timed out. The management processor will now take the action specified when the timer was set.
TRAP-TYPE
.1.3.6.1.4.1.11.2.23.35.0.12210
hpevtOSShtDwnDueMCAAn OS is shutting down due to an MCA (Machine Check Abort) or INIT.
TRAP-TYPE
.1.3.6.1.4.1.11.2.23.35.0.12217
hpevtOSShtDwnDuePanicAn OS is shutting down due to a panic.
TRAP-TYPE
.1.3.6.1.4.1.11.2.23.35.0.12218
hpevtCLUFWIncomptblSysTypeFollowing an in-the-box system type upgrade, or after a UGUY board was replaced, the CLU FW may not have been updated to an appropriate revision for the system type.
TRAP-TYPE
.1.3.6.1.4.1.11.2.23.35.0.12222
hpevtOnlnIdentHWProbDiagnostics running under the OS have detected a problem with the identified hardware.
TRAP-TYPE
.1.3.6.1.4.1.11.2.23.35.0.12227
hpevtProcOvTempThe processor temperature has exceeded normal limits. HP's Enhanced Thermal Management (ETM) feature has been employed to cool the processor. If the temperature problem persists, this will have an adverse impact on the performance of this processor.
TRAP-TYPE
.1.3.6.1.4.1.11.2.23.35.0.12228
hpevtErrChkFabBootStatAn error occurred while checking the fabricless boot state
TRAP-TYPE
.1.3.6.1.4.1.11.2.23.35.0.12229
hpevtSysFwUnblClrLnkErrMskSystem firmware was unable to clear the link error masks
TRAP-TYPE
.1.3.6.1.4.1.11.2.23.35.0.12230
hpevtSysFwNotDetLnkAdrrSystem firmware could not determine a link's address
TRAP-TYPE
.1.3.6.1.4.1.11.2.23.35.0.12231
hpevtSysFwUnblTurnBadLnkOffSystem firmware was unable to turn a bad link off
TRAP-TYPE
.1.3.6.1.4.1.11.2.23.35.0.12232
hpevtWindWtchDogXpiredThe Wiindows watchdog timer has expired. The nPartition will either be reset or powered off. The data field contains the following information: byte 2 - cell slot number of the cell that generated the timeout event byte 3 - nPartition number (SX2000 superdome only) byte 4 - timeout action (0 = Reset, 1 = Power off) byte 7 - cabinet number
TRAP-TYPE
.1.3.6.1.4.1.11.2.23.35.0.12244
hpevtMPCtrlReprtMPBusCommFailAn MP Bus communications device is reporting a hardware revision that is known to cause MP Bus communications failures. The value in the data field indicates the physical location of the PM, CLU, or PDHC device that is failing.
TRAP-TYPE
.1.3.6.1.4.1.11.2.23.35.0.12251
hpevt12VPCIFailonIOChassMain power at the PCI slot located on the IO Chassis has faulted.
TRAP-TYPE
.1.3.6.1.4.1.11.2.23.35.0.12255
hpevtSFWDetFailOptmzFabA failure was encountered while running the Fabric API to optimize the fabric.
TRAP-TYPE
.1.3.6.1.4.1.11.2.23.35.0.12289
hpevtCritFailCellOnlineA critical failure occurred during a cell online add or delete call.
TRAP-TYPE
.1.3.6.1.4.1.11.2.23.35.0.12291
hpevtCellHasIncomptbleHwFWA cell being added is not compatible with the partition.
TRAP-TYPE
.1.3.6.1.4.1.11.2.23.35.0.12296
hpevtCellFWnotMatchPartFWThe Firmware revision of the cell being added is different from the nPar.
TRAP-TYPE
.1.3.6.1.4.1.11.2.23.35.0.12297
hpevtVMSDetctUnrecvrdEvntThe OpenVMS system has failed and will reboot
TRAP-TYPE
.1.3.6.1.4.1.11.2.23.35.0.12319
hpevtBadCellBrdOrBadProcBrdBad cell board (on cellular system), or bad processor board (on non-cellular system).
TRAP-TYPE
.1.3.6.1.4.1.11.2.23.35.0.12324
hpevtCPUDegradErrThirdCacheCPU performance degraded due to excessive errors in third level cache.
TRAP-TYPE
.1.3.6.1.4.1.11.2.23.35.0.12343
hpevtROMFailAuthentcThe alternate ROM failed to authenticate. The current (primary) ROM will continue to be used
TRAP-TYPE
.1.3.6.1.4.1.11.2.23.35.0.12352
hpevtAltrntROMUnblSwapThe alternate ROM was successfully authenticated but the primary and alternate ROM could not be swapped. The current primary will still be used
TRAP-TYPE
.1.3.6.1.4.1.11.2.23.35.0.12354
hpevtPciSlotErrDetectPCI/PCIX/PCIe card/slot error detected during IO bus scan
TRAP-TYPE
.1.3.6.1.4.1.11.2.23.35.0.12358
hpevtCCLinkDownA CC to CC link failed to train in a 2-cell system. The partition can still boot, but with less redundancy and bandwidth. Data field: Cell number [63:56] Link number [32:0]
TRAP-TYPE
.1.3.6.1.4.1.11.2.23.35.0.12394
hpevtUnrecovProcIntOccrAn unrecoverable processor interrupt occurred while in IPF firmware. The event data is the processor status register.
TRAP-TYPE
.1.3.6.1.4.1.11.2.23.35.0.12395
hpevtElectrncKeyProblmThe 'e-keying error' only occurs during the power-up if the SVB must be left off due to an electronic keying problem.
TRAP-TYPE
.1.3.6.1.4.1.11.2.23.35.0.12399
hpevtBldeInstImproperLocThe 'location error' only occurs during power-up if the SVB must be left off due to being installed in an improper location in the enclosure (SVBs must be installed in specific positions relative to fans or other components.
TRAP-TYPE
.1.3.6.1.4.1.11.2.23.35.0.12400
hpevtbldeInstViolateEnclreThe 'ccoling error' occurs during the power-up if the SVB must be left off due to insufficient cooling; more fans may be needed.
TRAP-TYPE
.1.3.6.1.4.1.11.2.23.35.0.12401
hpevtsx2000FabRprtUnexpctErrData field: return value from internal firmware function.
TRAP-TYPE
.1.3.6.1.4.1.11.2.23.35.0.12403
hpevtOANotServPwrOnReqstOA is Busy: The Powe-on request cannot be completed.
TRAP-TYPE
.1.3.6.1.4.1.11.2.23.35.0.12408
hpevtIOBckPlnReprtNonRedundncyPCIPwrThe IO backplane in the specified cabinet is reporting a non-redundant PCI power condition.
TRAP-TYPE
.1.3.6.1.4.1.11.2.23.35.0.12411
hpevtUSBStorAttchThis trap is sent when a USB storage device has been attached.
TRAP-TYPE
.1.3.6.1.4.1.11.2.23.35.0.12503
hpevtUSBStorRemovedThis trap is sent when a attached USB storage device is removed.
TRAP-TYPE
.1.3.6.1.4.1.11.2.23.35.0.12504
hpevtMigratSrcNotConntThe migration source could not connect to the target.
TRAP-TYPE
.1.3.6.1.4.1.11.2.23.35.0.12547
hpevtMigratFailA migration has failed.
TRAP-TYPE
.1.3.6.1.4.1.11.2.23.35.0.12548
hpevtMigratNotSuccessA migration was not successful. This contains the migration phase when it was terminated.
TRAP-TYPE
.1.3.6.1.4.1.11.2.23.35.0.12550
hpevtVMNotAlloctMemForIOA virtual machine was not able to obtain memory for an I/O device.
TRAP-TYPE
.1.3.6.1.4.1.11.2.23.35.0.12551
hpevtUnSupprtDimmInPartitionHP PFM service has detected HP unsupported DIMM(s) on this partition.
TRAP-TYPE
.1.3.6.1.4.1.11.2.23.35.0.12557
hpevtRuntimeCritShtDwnOS run-time critical shutdown has occurred.
TRAP-TYPE
.1.3.6.1.4.1.11.2.23.35.0.12560
hpevtPwrExptGreatrPwrBulkThe amount of power expected to be drawn by the currently operating hardware is greater than the rating of the currently operating Bulk Power Supplies (BPS). It is very likely that partitions may be powered down with no further warning to eliminate the excess power load.
TRAP-TYPE
.1.3.6.1.4.1.11.2.23.35.0.12586
hpevtBulkPwrReduncLostBulk power supply (BPS) redundancy has been lost on one or more row(s) of power supplies in the complex. The further loss of a single BPS or an AC grid will most likely result in the shutdown of partitions using the chassis that lost redundancy.
TRAP-TYPE
.1.3.6.1.4.1.11.2.23.35.0.12589
hpevtACReduncLostAC redundancy has been lost on one or more row(s) of power supplies in the complex. The further loss of a single Bulk Power Supply (BPS) or the other AC grid will most likely result in the shutdown of partitions using the chassis that have lost redundancy.
TRAP-TYPE
.1.3.6.1.4.1.11.2.23.35.0.12591
hpevtFanCoolNotReduncThe fans that cool a region of the system are not redundant. If an additional fan fails in or is removed from this cooling domain, the partitions on this system will be automatically shut down to prevent an over temperature condition.
TRAP-TYPE
.1.3.6.1.4.1.11.2.23.35.0.12593
hpevtFanInsufficientInCoolDomainAn insufficient number of fans are working in a cooling domain to permit system operation. Running partitions will be shut down immediately to prevent system damage due to excessive heat. (If the situation is corrected immediately, it is possible to prevent system shutdown).
TRAP-TYPE
.1.3.6.1.4.1.11.2.23.35.0.12595
hpevtOSNotUseAllProcsOperating system is not using all available processors for the current system.
TRAP-TYPE
.1.3.6.1.4.1.11.2.23.35.0.12627
hpevtFMPUnexpctRstHasRcvA Fabric Message Processor (FMP) has unexpectedly reset. The system has recovered from the problem.
TRAP-TYPE
.1.3.6.1.4.1.11.2.23.35.0.12863
hpIpfEvtDetailStrThis string provides a detailed description of the Event along with variable information.ro
DisplayString (SNMPv2-TC)
.1.3.6.1.4.1.11.2.23.35.1
hpIpf02Events
OBJECT IDENTIFIER
.1.3.6.1.4.1.11.2.23.45