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

Machine Check Initiated. Probable Cause: A Machine Check Abort event means

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

Page 10 highlights

113 Warning Hot Swap Cage: SCSI cable removed. Probable Cause: This alert indicates that a SCSI cable, Jumper or Duplex Connector has either been disconnected or removed. This may make some SCSI devices inaccessible. Recommended Action: Ensure that all the required SCSI cables, jumpers or duplex connectors are correctly connected to the cage, disks, and/or the controller. WBEM EventID: 174. WBEM ProviderName: SEL02_IndicationProvider. 518 Error Uncorrectable multi-bit ECC error has occurred. Probable Cause: There has been an ECC double-bit error in one of the server's ECC memory modules. When an ECC double-bit memory error is detected, the system generates a Non-Maskable Interrupt that halts the system to prevent errors from propagating to other subsystems. Data being written or transmitted at the time may have been lost. Recommended Action: Make a note of the failed memory bank/board number and slot number, contact HP support to replace the failed module. WBEM EventID: 159. WBEM ProviderName: SEL02_IndicationProvider. 518 Error Uncorrectable multi-bit ECC error has occurred. Probable Cause: There has been an ECC double-bit error in one of the server's ECC memory modules. When an ECC double-bit memory error is detected, the system generates a Non-Maskable Interrupt that halts the system to prevent errors from propagating to other subsystems. Data being written or transmitted at the time may have been lost. Recommended Action: Make a note of the failed memory bank/board number and slot number, contact HP support to replace the failed module. WBEM EventID: 159. WBEM ProviderName: SEL02_IndicationProvider. 699 Error Machine Check Initiated. Probable Cause: A Machine Check Abort event means the hardware detected a critical error. This event is generated whenever a system error due to processor, firmware, hardware and operating system is encountered. MCA events may be either recoverable or non-recoverable. If it is recoverable, the system will attempt to recover from the error for the purpose of maintaining high availability. An example of which is automatic disabling of a failing processor. For non-recoverable errors, the system will either stop or reboot to prevent data corruption and unreliable operation. Recommended Action: When this event is generated, it is highly advisable to consult both the operating system and hardware event logs to find out if there are other events that may help identify the cause of the MCA. If an MCA event occurs that causes the system to reboot, the failing component may be automatically disabled and the system continue to run but at a degraded performance level while awaiting repair. Therefore, for an MCA event, HP recommends contacting HP Customer Support to determine if a repair is needed. WBEM EventID: 173. WBEM ProviderName: SEL02_IndicationProvider. 699 Error Machine Check Initiated. Probable Cause: A Machine Check Abort event means the hardware detected a critical error. This event is generated whenever a system error due to processor, firmware, hardware and operating system is encountered. MCA events may be either recoverable or non-recoverable. If it is recoverable, the system will attempt to recover from the error for the purpose of maintaining high availability. An example of which is automatic disabling of a failing processor. For non-recoverable errors, the system will either stop or reboot to prevent data corruption and unreliable operation. Recommended Action: When this event is generated, it is highly advisable to consult both the operating system and hardware event logs to find out if there are other events that may help identify the cause of the MCA. If an MCA event occurs that causes the system to reboot, the failing component may be automatically disabled and the system continue to run but at a degraded performance level while awaiting repair. Therefore, for an MCA event, HP recommends contacting HP Customer Support to determine if a repair is needed. WBEM EventID: 173. WBEM ProviderName: SEL02_IndicationProvider. 700 Error Generic trap for Critical or Fatal type E0 event from system firmware. Probable Cause: This event is generated when a critical or fatal event has occurred as reported by system firmware. The server is not operational and is in a state where it cannot provide more details about the failure. To obtain more information, log into the server's Management Processor Card and look at the event log for more details on the failure. Recommended Action: Contact HP Support for best course of action. HP may require a reboot, reconfiguration, or reflash of firmware. WBEM EventID: 162. WBEM ProviderName: SEL02_IndicationProvider. 10 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
Hot Swap Cage: SCSI cable removed. Probable Cause: This alert indicates that a SCSI
cable, Jumper or Duplex Connector has either been disconnected or removed. This
may make some SCSI devices inaccessible. Recommended Action: Ensure that all
the required SCSI cables, jumpers or duplex connectors are correctly connected to
the cage, disks, and/or the controller. WBEM EventID: 174. WBEM ProviderName:
SEL02_IndicationProvider.
Warning
113
Uncorrectable multi-bit ECC error has occurred. Probable Cause: There has been an
ECC double-bit error in one of the server's ECC memory modules. When an ECC
double-bit memory error is detected, the system generates a Non-Maskable Interrupt
that halts the system to prevent errors from propagating to other subsystems. Data
being written or transmitted at the time may have been lost. Recommended Action:
Make a note of the failed memory bank/board number and slot number, contact HP
support to replace the failed module. WBEM EventID: 159. WBEM ProviderName:
SEL02_IndicationProvider.
Error
518
Uncorrectable multi-bit ECC error has occurred. Probable Cause: There has been an
ECC double-bit error in one of the server's ECC memory modules. When an ECC
double-bit memory error is detected, the system generates a Non-Maskable Interrupt
that halts the system to prevent errors from propagating to other subsystems. Data
being written or transmitted at the time may have been lost. Recommended Action:
Make a note of the failed memory bank/board number and slot number, contact HP
support to replace the failed module. WBEM EventID: 159. WBEM ProviderName:
SEL02_IndicationProvider.
Error
518
Machine Check Initiated. Probable Cause: A Machine Check Abort event means the
hardware detected a critical error. This event is generated whenever a system error
due to processor, firmware, hardware and operating system is encountered. MCA
events may be either recoverable or non-recoverable. If it is recoverable, the system
will attempt to recover from the error for the purpose of maintaining high availability.
An example of which is automatic disabling of a failing processor. For non-recoverable
errors, the system will either stop or reboot to prevent data corruption and unreliable
operation. Recommended Action: When this event is generated, it is highly advisable
to consult both the operating system and hardware event logs to find out if there are
other events that may help identify the cause of the MCA. If an MCA event occurs
that causes the system to reboot, the failing component may be automatically disabled
and the system continue to run but at a degraded performance level while awaiting
repair. Therefore, for an MCA event, HP recommends contacting HP Customer
Support to determine if a repair is needed. WBEM EventID: 173. WBEM
ProviderName: SEL02_IndicationProvider.
Error
699
Machine Check Initiated. Probable Cause: A Machine Check Abort event means the
hardware detected a critical error. This event is generated whenever a system error
due to processor, firmware, hardware and operating system is encountered. MCA
events may be either recoverable or non-recoverable. If it is recoverable, the system
will attempt to recover from the error for the purpose of maintaining high availability.
An example of which is automatic disabling of a failing processor. For non-recoverable
errors, the system will either stop or reboot to prevent data corruption and unreliable
operation. Recommended Action: When this event is generated, it is highly advisable
to consult both the operating system and hardware event logs to find out if there are
other events that may help identify the cause of the MCA. If an MCA event occurs
that causes the system to reboot, the failing component may be automatically disabled
and the system continue to run but at a degraded performance level while awaiting
repair. Therefore, for an MCA event, HP recommends contacting HP Customer
Support to determine if a repair is needed. WBEM EventID: 173. WBEM
ProviderName: SEL02_IndicationProvider.
Error
699
Generic trap for Critical or Fatal type E0 event from system firmware. Probable Cause:
This event is generated when a critical or fatal event has occurred as reported by
system firmware. The server is not operational and is in a state where it cannot
provide more details about the failure. To obtain more information, log into the
server's Management Processor Card and look at the event log for more details on
the failure. Recommended Action: Contact HP Support for best course of action. HP
may require a reboot, reconfiguration, or reflash of firmware. WBEM EventID: 162.
WBEM ProviderName: SEL02_IndicationProvider.
Error
700
10
WBEM Provider Event Tables