Dell PowerEdge R610 - Page 19

Code Text Causes Corrective action
E161C PS # Input Lost Power source for specified
power supply is unavailable,
or out of acceptable range.
Check the AC power source for the
specified power supply.
Escalate for possible power supply
replacement.
E1620 PS # Input Range Power source for specified
power supply is unavailable,
or out of acceptable range.
Escalate for possible power supply
replacement.
E1624 PS Redundancy The power supply subsystem
is no longer redundant. If the
last supply fails, the system
will go down.
Escalate for possible power supply
replacement.
E1626 Power Supply
Mismatch
The power supplies in the
system are not the same
wattage.
Ensure that power supplies with
matching wattage are installed.
E1629 Power required >
PSU wattage.
The system configuration
requires more power than the
power supplies can provide,
even with throttling.
Turn off power to the system, reduce
the hardware configuration or install
higher-wattage power supplies, and
then restart the system.
E1710 I/O Channel Chk The system BIOS has
reported an I/O channel
check.
Escalate for possible server
replacement.
E1711 PCI PERR B## D##
F##
reported a PCI parity error on
a component that resides in
PCI configuration space at
bus ##, device ##, function
##.
Escalate for possible server
replacement.
PCI PERR Slot # The system BIOS has
reported a PCI parity error on
a component that resides in
the specified PCI slot.
E1712 PCI SERR B## D##
F##
The system BIOS has
reported a PCI system error
on a component that resides
in PCI configuration space at
bus ##, device ##, function
##.
Escalate for possible server
replacement.
PCI SERR Slot # The system BIOS has
reported a PCI system error
on a component that resides
in the specified slot.
E1714 Unknown Err The system BIOS has
determined that there has
been an error in the system,
Escalate for possible server
replacement.
Table continues…
LCD status message explanations
November 2010 Maintaining and Troubleshooting the Dell
™
PowerEdge
™
R610 Server 19
Comments on this document? infodev@avaya.com