HP Integrity rx2800 HP Insight Management WBEM Provider Events Reference Guide - Page 32

5528 5529 5530 5546 5547 5548 5550 5556 5557 5558 5559 5560 5566 5567 5568 5569 5570 Error Error Warning Error Error Error Error Error Error Error Error Error Error Error Error Error Error Multiple Core Cells have been discovered in the same PD. Probable Cause: Verify that the complex profile is correct and reset the partition. WBEM EventID: 423. WBEM ProviderName: FPL_IndicationProvider. The utilities component encountered an error when sending a command to the MP. Probable Cause: Verify the utilities system is connected correctly and reset. WBEM EventID: 424. WBEM ProviderName: FPL_IndicationProvider. Error received after issuing the Retrieve Cell Slot State command. Probable Cause: Make sure the GSP is connected and reset. WBEM EventID: 1007. WBEM ProviderName: FPL_IndicationProvider. This indicates that all the cpus in the cell did not rendezvous during the MCA. Probable Cause: When this happens the cell will step through some of the error logging code on its own and then reset itself. WBEM EventID: 426. WBEM ProviderName: FPL_IndicationProvider. This indicates that it does not have any access to the PD. Probable Cause: Forward Progress indicator; the cell will independently step through the error logging steps before it resets itself. WBEM EventID: 427. WBEM ProviderName: FPL_IndicationProvider. This indicates the loss of lockstep during the MCA path. Probable Cause: The cell will take up a few more error logging steps independently before resetting itself. WBEM EventID: 428. WBEM ProviderName: FPL_IndicationProvider. The PD level cell rendezvous failed. Probable Cause: This means that the cells will independently step through some of the error logging code and then reset themselves. WBEM EventID: 429. WBEM ProviderName: FPL_IndicationProvider. It stands for diagnosis of catastrophic errors in the PIN block of concorde. Probable Cause: This means that the cell will be reset. WBEM EventID: 557. WBEM ProviderName: FPL_IndicationProvider. The cell monarch cpu has failed. Probable Cause: The monarch cpu will be deconfigured. WBEM EventID: 1020. WBEM ProviderName: FPL_IndicationProvider. This indicates that the cell missed the rendezvous at the partition level. Probable Cause: The cell will independently step through some of the error logging steps and then finally reset itself. WBEM EventID: 559. WBEM ProviderName: FPL_IndicationProvider. This means that the PD monarch timedout. Probable Cause: The cell will be reset ; also the partition will be reset. WBEM EventID: 560. WBEM ProviderName: FPL_IndicationProvider. SetViewRoot on a remote cell failed. Probable Cause: Inter Processor interrupts failed. Be sure that the partition rendezvous was successfully completed. Reset. WBEM EventID: 2452. WBEM ProviderName: FPL_IndicationProvider. Failed to update CSR contents. Probable Cause: Coherency controller on cell sending event is suspect. Recommended Action: Provide event data to HP support center for assistance. WBEM EventID: 2431. WBEM ProviderName: FPL_IndicationProvider. This indicates the failure in collecting the Complex profile info. Probable Cause: The partition level memory interleaving cannot continue without the appropriate information. WBEM EventID: 563. WBEM ProviderName: FPL_IndicationProvider. This chassis code indicates the failure in collecting the cell info. Probable Cause: The partition level memory will fail. WBEM EventID: 564. WBEM ProviderName: FPL_IndicationProvider. This indicates the failure in updating the GNI info of the cell with CLM. Probable Cause: The partition level memory will fail at this point. WBEM EventID: 565. WBEM ProviderName: FPL_IndicationProvider. This indicates the failure in adjusting the mem info with Minimum ZI req. Probable Cause: This will cause the partition level memory to exit cell interleaving. WBEM EventID: 566. WBEM ProviderName: FPL_IndicationProvider. 32 WBEM Provider Event Tables