HP Integrity rx8620 HP Insight Manager WBEM Provider Events Reference - Page 23
If assistance is required, contact the HP Support Center. WBEM EventID: 355. WBEM
View all HP Integrity rx8620 manuals
Add to My Manuals
Save this manual to your list of manuals |
Page 23 highlights
Event ID Event Severity Event Description 5335 Warning Firmware is adding a DEGRADED cpu node to the device tree. Probable Cause: A CPU that is not fully functional is installed in the cell board. Recommended Action: Replace cpu indicated in data field of event. WBEM EventID: 349. WBEM ProviderName: FPL_IndicationProvider 5354 Error PD rendezvous will fail do to a Firmware Tree error. Probable Cause: Decode the ASCII string in the data field to determine what resource is missing. Examine earlier chassis codes to determine why that resource is unavailable. WBEM EventID: 350. WBEM ProviderName: FPL_IndicationProvider 5359 Error The current cell is not configured as part of the expected set. Probable Cause: A bad complex profile exists. Correct and redistribute. WBEM EventID: 351. WBEM ProviderName: FPL_IndicationProvider 5360 Error A remote CSR could not be read. Probable Cause: Either a hardware connection problem exists, or fabric was unable to be routed. Verify hardware and reset. WBEM EventID: 352. WBEM ProviderName: FPL_IndicationProvider 5361 Error The current cell is too late to rendezvous with other cells. Probable Cause: This cell took to long completing previous steps to rendezvous. A bad complex profile could also cause this problem. WBEM EventID: 353. WBEM ProviderName: FPL_IndicationProvider 5365 Error The current cell detected incompatible CPUs on another cell. Probable Cause: Mixed CPU types are installed in the same partition. Remove them. WBEM EventID: 354. WBEM ProviderName: FPL_IndicationProvider 5366 Error Current cell was too slow creating the local rendezvous set. Probable Cause: Cell too slow. Could be bad hardware. Check for other errors and reset. Recommended Action: If assistance is required, contact the HP Support Center. WBEM EventID: 355. WBEM ProviderName: FPL_IndicationProvider 5376 Error Reporting cell was not included in the global cell set. Probable Cause: Fabric problem, Connection problem or timing problem. Reset the PD. WBEM EventID: 356. WBEM ProviderName: FPL_IndicationProvider 5380 Error No Core Cell can be selected in the PD. Probable Cause: No cells have a functioning core IO card. Add a core IO card to a cell in the PD and reset. WBEM EventID: 357. WBEM ProviderName: FPL_IndicationProvider 5383 Error Firmware was unable to notify utilities of the core cell number. Probable Cause: Communication with utilities is broken. Check for earlier errors or NVRAM problems. WBEM EventID: 358. WBEM ProviderName: FPL_IndicationProvider 5403 Error Fabric code unable to find a needed service provider. Probable Cause: The registry is corrupt or the ROM is incomplete. WBEM EventID: 359. WBEM ProviderName: FPL_IndicationProvider 5404 Warning Error in a fabric Port. Probable Cause: Reset. WBEM EventID: 360. WBEM ProviderName: FPL_IndicationProvider 5405 Warning Parity error detected on read from fabric. Probable Cause: Hardware problem. Check connections and reset. WBEM EventID: 361. WBEM ProviderName: FPL_IndicationProvider 5406 Warning Error writing to Fabric. Probable Cause: Bad hardware. WBEM EventID: 362. WBEM ProviderName: FPL_IndicationProvider 5407 Error Crossbar slices are out of rev with each other. Probable Cause: Bad hardware configuration, different revisions of crossbars are installed. Recommended Action: Check crossbar revisions and ensure all installed crossbar revisions are the same. Replace the crossbar that is not in rev with the others. WBEM EventID: 363. WBEM ProviderName: FPL_IndicationProvider 5408 Error Crossbar slices are configured poorly. Probable Cause: Fatal configuration. Reconfigure the hardware. WBEM EventID: 364. WBEM ProviderName: FPL_IndicationProvider Platform Events 23