HP Integrity BL890c HP Insight Management WBEM Provider Events Reference Guide - Page 94

an Auxiliary MP AMP has been lost. Recommended Action: The management

Get HP Integrity BL890c - i2 Server PDF manuals and user guides View all HP Integrity BL890c manuals
Add to My Manuals
Save this manual to your list of manuals

Page 94 highlights

13416 Error 13417 Error 13497 Warning 13574 Warning 13575 Warning 13576 Warning 13606 Error 13621 Error The iLO peer to peer LAN communication between DMP and AMP was lost. Probable Cause: The iLO peer to peer LAN communication between a Domain MP (DMP) and an Auxiliary MP (AMP) has been lost. Recommended Action: The management system will attempt to repair itself. If the management system does not recover refer to the Service Guide to determine how to reset iLO without a user interface. WBEM EventID: 9864. WBEM ProviderName: FPL_IndicationProvider. The iLO peer to peer LAN communication between DMP and AMP was not established. Probable Cause: The iLO peer to peer LAN communication between Domain MP (DMP) and an Auxiliary MP (AMP) could not be established. Recommended Action: The management system will attempt to repair itself. If the management system does not recover refer to the Service Guide to determine how to reset iLO without a user interface. WBEM EventID: 9865. WBEM ProviderName: FPL_IndicationProvider. Virtual Connect failed to write data into a FRU storage device. Probable Cause: An error occurred in the interface between system firmware and manageability firmware. Recommended Action: Reboot the server and verify that the system board or mezz card containing this FRU is functioning properly. If not, replace the failing hardware.Check system logs to see if other errors are related to this same FRU. If so, replace the system board or mezz card containing this FRU.Verify system and manageability firmware are at their supported revisions, and if not, update firmware to the latest supported revisions.If problems persist, contact Support. WBEM EventID: 9799. WBEM ProviderName: FPL_IndicationProvider. Virtual Connect failed to save a backup of non-volatile EFI variables into NVM. Probable Cause: An error occurred in the interface between system firmware and manageability firmware. Recommended Action: Reboot the server and verify that the system board (Monarch Blade system board if a multi-blade server) is functioning properly. If not, replace the system board.Check system logs to see if other NVM errors are related to this same system board. If so, replace the system board.Verify system and manageability firmware are at their supported revisions, and if not, update firmware to the latest supported revisions.If problems persist, contact Support. WBEM EventID: 9801. WBEM ProviderName: FPL_IndicationProvider. Virtual Connect failed to save non-volatile EFI variables into NVM. Probable Cause: An error occurred in the interface between system firmware and manageability firmware. Recommended Action: Reboot the server and verify that the system board (Monarch Blade system board if a multi-blade server) is functioning properly. If not, replace the system board.Check system logs to see if other NVM errors are related to this same system board. If so, replace the system board.Verify system and manageability firmware are at their supported revisions, and if not, update firmware to the latest supported revisions.If problems persist, contact Support. WBEM EventID: 9802. WBEM ProviderName: FPL_IndicationProvider. Virtual Connect failed to erase the EFI variables backup from NVM. Probable Cause: An error occurred in the interface between system firmware and manageability firmware. Recommended Action: Reboot the server and verify that the system board (Monarch Blade system board if a multi-blade server) is functioning properly. If not, replace the system board.Check system logs to see if other NVM errors are related to this same system board. If so, replace the system board.Verify system and manageability firmware are at their supported revisions, and if not, update firmware to the latest supported revisions.If problems persist, contact Support. WBEM EventID: 9803. WBEM ProviderName: FPL_IndicationProvider. IOH persistent error condition detected. Probable Cause: A persistent error on an I/O bridge or endpoint that cannot be cleared. Recommended Action: Replace the failed component as indicated by the physical location data field. WBEM EventID: 8261. WBEM ProviderName: FPL_IndicationProvider. Generic FRU has header checksum error. Probable Cause: 1. FRU not properly programmed 2. Manageabilty FW may not be working correctly. Recommended Action: Review the event log for related MFW events to determine if there is a FRU read problem.Try a MFW reset via web or text interface. If this fails, verify all the firmware versions are at a supported revision level and do a full power cycle of the system. If this still fails, it is likely the FRU requires replacement. WBEM EventID: 8262. WBEM ProviderName: FPL_IndicationProvider. 94 WBEM Provider Event Tables

  • 1
  • 2
  • 3
  • 4
  • 5
  • 6
  • 7
  • 8
  • 9
  • 10
  • 11
  • 12
  • 13
  • 14
  • 15
  • 16
  • 17
  • 18
  • 19
  • 20
  • 21
  • 22
  • 23
  • 24
  • 25
  • 26
  • 27
  • 28
  • 29
  • 30
  • 31
  • 32
  • 33
  • 34
  • 35
  • 36
  • 37
  • 38
  • 39
  • 40
  • 41
  • 42
  • 43
  • 44
  • 45
  • 46
  • 47
  • 48
  • 49
  • 50
  • 51
  • 52
  • 53
  • 54
  • 55
  • 56
  • 57
  • 58
  • 59
  • 60
  • 61
  • 62
  • 63
  • 64
  • 65
  • 66
  • 67
  • 68
  • 69
  • 70
  • 71
  • 72
  • 73
  • 74
  • 75
  • 76
  • 77
  • 78
  • 79
  • 80
  • 81
  • 82
  • 83
  • 84
  • 85
  • 86
  • 87
  • 88
  • 89
  • 90
  • 91
  • 92
  • 93
  • 94
  • 95
  • 96
  • 97
  • 98
  • 99
  • 100
  • 101
  • 102
  • 103
  • 104
  • 105
  • 106
  • 107
  • 108
  • 109
  • 110
  • 111
  • 112
The iLO peer to peer LAN communication between DMP and AMP was lost. Probable
Cause: The iLO peer to peer LAN communication between a Domain MP (DMP) and
an Auxiliary MP (AMP) has been lost. Recommended Action: The management
system will attempt to repair itself. If the management system does not recover refer
to the Service Guide to determine how to reset iLO without a user interface. WBEM
EventID: 9864. WBEM ProviderName: FPL_IndicationProvider.
Error
13416
The iLO peer to peer LAN communication between DMP and AMP was not
established. Probable Cause: The iLO peer to peer LAN communication between
Domain MP (DMP) and an Auxiliary MP (AMP) could not be established.
Recommended Action: The management system will attempt to repair itself. If the
management system does not recover refer to the Service Guide to determine how
to reset iLO without a user interface. WBEM EventID: 9865. WBEM ProviderName:
FPL_IndicationProvider.
Error
13417
Virtual Connect failed to write data into a FRU storage device. Probable Cause: An
error occurred in the interface between system firmware and manageability firmware.
Recommended Action: Reboot the server and verify that the system board or mezz
card containing this FRU is functioning properly. If not, replace the failing
hardware.Check system logs to see if other errors are related to this same FRU. If so,
replace the system board or mezz card containing this FRU.Verify system and
manageability firmware are at their supported revisions, and if not, update firmware
to the latest supported revisions.If problems persist, contact Support. WBEM EventID:
9799. WBEM ProviderName: FPL_IndicationProvider.
Warning
13497
Virtual Connect failed to save a backup of non-volatile EFI variables into NVM.
Probable Cause: An error occurred in the interface between system firmware and
manageability firmware. Recommended Action: Reboot the server and verify that
the system board (Monarch Blade system board if a multi-blade server) is functioning
properly. If not, replace the system board.Check system logs to see if other NVM
errors are related to this same system board. If so, replace the system board.Verify
system and manageability firmware are at their supported revisions, and if not,
update firmware to the latest supported revisions.If problems persist, contact Support.
WBEM EventID: 9801. WBEM ProviderName: FPL_IndicationProvider.
Warning
13574
Virtual Connect failed to save non-volatile EFI variables into NVM. Probable Cause:
An error occurred in the interface between system firmware and manageability
firmware. Recommended Action: Reboot the server and verify that the system board
(Monarch Blade system board if a multi-blade server) is functioning properly. If not,
replace the system board.Check system logs to see if other NVM errors are related
to this same system board. If so, replace the system board.Verify system and
manageability firmware are at their supported revisions, and if not, update firmware
to the latest supported revisions.If problems persist, contact Support. WBEM EventID:
9802. WBEM ProviderName: FPL_IndicationProvider.
Warning
13575
Virtual Connect failed to erase the EFI variables backup from NVM. Probable Cause:
An error occurred in the interface between system firmware and manageability
firmware. Recommended Action: Reboot the server and verify that the system board
(Monarch Blade system board if a multi-blade server) is functioning properly. If not,
replace the system board.Check system logs to see if other NVM errors are related
to this same system board. If so, replace the system board.Verify system and
manageability firmware are at their supported revisions, and if not, update firmware
to the latest supported revisions.If problems persist, contact Support. WBEM EventID:
9803. WBEM ProviderName: FPL_IndicationProvider.
Warning
13576
IOH persistent error condition detected. Probable Cause: A persistent error on an
I/O bridge or endpoint that cannot be cleared. Recommended Action: Replace the
failed component as indicated by the physical location data field. WBEM EventID:
8261. WBEM ProviderName: FPL_IndicationProvider.
Error
13606
Generic FRU has header checksum error. Probable Cause: 1. FRU not properly
programmed 2. Manageabilty FW may not be working correctly. Recommended
Action: Review the event log for related MFW events to determine if there is a FRU
read problem.Try a MFW reset via web or text interface. If this fails, verify all the
firmware versions are at a supported revision level and do a full power cycle of the
system. If this still fails, it is likely the FRU requires replacement. WBEM EventID:
8262. WBEM ProviderName: FPL_IndicationProvider.
Error
13621
94
WBEM Provider Event Tables