Dell PowerEdge R610 - Page 18

Code Text Causes Corrective action
failure will put the system at
risk of over-heating.
limits, then escalate for possible
server replacement.
Check control panel LCD for
additional scrolling messages.
E1410 CPU # IERR Specified microprocessor is
reporting an internal error.
Escalate for possible server
replacement.
E1414 CPU # Thermtrip Specified microprocessor is
out of acceptable
temperature range and has
halted operation.
Check room temperature and external
air flow. If both are within acceptable
limits, then escalate for possible
server replacement.
Note:
The LCD continues to display
this message until the system’s
power cord is disconnected and
reconnected to the AC power
source.
E1418 CPU # Presence Specified processor is
missing or bad, and the
system is in an unsupported
configuration.
Escalate for possible server
replacement.
E141C CPU Mismatch Processors are in an
unsupported configuration.
Run server diagnostics. This requires
a keyboard and monitor.
E141F CPU Protocol The system BIOS has
reported a processor protocol
error.
Escalate for possible server
replacement.
E1420 CPU Bus PERR The system BIOS has
reported a processor bus
parity error.
Escalate for possible server
replacement.
E1422 CPU Machine Chk The system BIOS has
reported a machine check
error.
Escalate for possible server
replacement.
E1610 PS # Missing No power is available from
the specified power supply;
specified power supply is
improperly installed or faulty.
Escalate for possible power supply
replacement.
E1614 PS # Status No power is available from
the specified power supply;
specified power supply is
improperly installed or faulty.
Escalate for possible power supply
replacement.
E1618 PS # Predictive Power supply voltage is out
of acceptable range;
specified power supply is
improperly installed or faulty.
Escalate for possible power supply
replacement.
Table continues…
Maintaining and Troubleshooting the Dell
™
PowerEdge
™
R610 Server
18 Maintaining and Troubleshooting the Dell
™
PowerEdge
™
R610 Server November 2010
Comments on this document? infodev@avaya.com