HP Integrity rx2620 Windows Integrity Management Agents Reference - Page 63

A Machine Check Abort event means the, HP recommends contacting HP Customer - front panel

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

Page 63 highlights

The voltage in the server has gone far outside the factory set range and could damage system components. A bad component, blown fuse, poorly seated module, loose cable, or debris could Check all boards, power supplies, and modules 12 be responsible for this failure. that either supply or use this voltage rail. The server has detect that the chassis door or 26 other access panel is not securely closed. Close any open panels or chassis doors. If the drive is redundant + hot-swappable, no immediate action is needed. Otherwise, the system likely will crash. Replace + repair disk 76 One of the server's drives has been removed. drive. This alert indicates that a SCSI cable, Jumper or Duplex Connector has either been disconnected Ensure that all the required SCSI cables, jumpers or removed. This may make some SCSI devices or duplex connectors are correctly connected to 113 inaccessible. the cage, disks, and/or the controller. 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 Make a note of the failed memory bank/board written or transmitted at the time may have been number and slot number, contact HP support to 518 lost. replace the failed module. A Machine Check Abort event means the hardware detected a critical error. This event is generated whenever a system error due to When this event is generated, it is highly processor, firmware, hardware and operating advisable to consult both the operating system system is encountered. MCA events may be either and hardware event logs to find out if there are recoverable or non-recoverable. If it is other events that may help identify the cause of recoverable, the system will attempt to recover the MCA. If an MCA event occurs that causes the from the error for the purpose of maintaining system to reboot, the failing component may be high availability. An example of which is automatically disabled and the system continue automatic disabling of a failing processor. For to run but at a degraded performance level while non-recoverable errors, the system will either awaiting repair. Therefore, for an MCA event, stop or reboot to prevent data corruption and HP recommends contacting HP Customer 699 unreliable operation. Support to determine if a repair is needed. 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 Contact HP Support for best course of action. HP look at the event log for more details on the may require a reboot, reconfiguration, or reflash 700 failure. of firmware. The input voltage for the system is not sufficient Check all boards, power supplies, and modules 704 for operation. that either supply or use this voltage rail. When this condition was detected the system should have been immediately shutdown to avoid The voltage in the server has gone outside the damage. Contact your HP support representative factory set range. A bad component, blown fuse, as soon as possible to have the unit checked. poorly seated module, loose cable, or debris could Check all boards, power supplies, and modules 705 be responsible for this failure. that either supply or use this voltage rail. The voltage in the server has gone outside the factory set range. A bad component, blown fuse, poorly seated module, loose cable, or debris could Check all boards, power supplies, and modules 706 be responsible for this failure. that either supply or use this voltage rail. Platform Events - Table 2 (Windows System Log Event ID, Cause, Recommended Action) 63

  • 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
  • 113
  • 114
  • 115
  • 116
  • 117
  • 118
  • 119
  • 120
  • 121
  • 122
  • 123
  • 124
  • 125
  • 126
  • 127
  • 128
  • 129
  • 130
  • 131
  • 132
  • 133
  • 134
  • 135
  • 136
  • 137
  • 138
  • 139
  • 140
  • 141
  • 142
  • 143
  • 144
  • 145
  • 146
  • 147
  • 148
  • 149
  • 150
  • 151
Check all boards, power supplies, and modules
that either supply or use this voltage rail.
The voltage in the server has gone far outside the
factory set range and could damage system
components. A bad component, blown fuse,
poorly seated module, loose cable, or debris could
be responsible for this failure.
12
Close any open panels or chassis doors.
The server has detect that the chassis door or
other access panel is not securely closed.
26
If the drive is redundant + hot-swappable, no
immediate action is needed. Otherwise, the
system likely will crash. Replace + repair disk
drive.
One of the server's drives has been removed.
76
Ensure that all the required SCSI cables, jumpers
or duplex connectors are correctly connected to
the cage, disks, and/or the controller.
This alert indicates that a SCSI cable, Jumper or
Duplex Connector has either been disconnected
or removed. This may make some SCSI devices
inaccessible.
113
Make a note of the failed memory bank/board
number and slot number, contact HP support to
replace the failed module.
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.
518
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.
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.
699
Contact HP Support for best course of action. HP
may require a reboot, reconfiguration, or reflash
of firmware.
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.
700
Check all boards, power supplies, and modules
that either supply or use this voltage rail.
The input voltage for the system is not sufficient
for operation.
704
When this condition was detected the system
should have been immediately shutdown to avoid
damage. Contact your HP support representative
as soon as possible to have the unit checked.
Check all boards, power supplies, and modules
that either supply or use this voltage rail.
The voltage in the server has gone outside the
factory set range. A bad component, blown fuse,
poorly seated module, loose cable, or debris could
be responsible for this failure.
705
Check all boards, power supplies, and modules
that either supply or use this voltage rail.
The voltage in the server has gone outside the
factory set range. A bad component, blown fuse,
poorly seated module, loose cable, or debris could
be responsible for this failure.
706
Platform Events – Table 2 (Windows System Log Event ID, Cause, Recommended Action)
63