![HP Integrity Superdome X Скачать руководство пользователя страница 54](http://html.mh-extra.com/html/hp/integrity-superdome-x/integrity-superdome-x_service-manual_164489054.webp)
Table 15: Advanced troubleshooting
Step
Symptom/condition
Action
5
Cannot read SEL.
SEL logging has stopped (health is steady green and power
is steady green).
1.
Examine console messages for any UEFI errors or
warnings about operation or communications.
2.
Ensure that the Robust Store is functioning properly. Try to
read the FPL. If all Fans are green and reported as OK in
response to an OA CLI
SHOW ENCLOSURE FAN ALL
command, then as a test, re-seat a single fan and verify
that this has generated a FPL and SEL entry.
The issue is fixed when the SEL resumes logging.
6
OS is nonresponsive after
boot
Front panel LEDs indicate that the server blade’s power is
turned on, and it is either booting or running the OS (for
example, health is steady green and power is steady green).
Nothing can be logged for this condition.
1.
Examine the OA CLI logs for entries related to processors,
processor power modules, shared memory, and core I/O
devices. Make sure there are no indictments or any
hardware issue or known firmware issue. See
Using
event logs
on page 72.
2.
Use the OA CLI
TC
command to initiate a TOC to reset
the partition.
3.
Reboot the OS and escalate.
4.
Obtain the system software status dump for root cause
analysis.
The issue is fixed when the OS becomes responsive and the
root cause is determined and corrected.
7a
MCA occurs during partition
operation; the server blade
reboots the OS.
NOTE:
Partition reboots OS if
enabled.
Front panel LEDs indicate that the server blade detected a
fatal error that it cannot recover from through OS recovery
routines (for example, health is flashing red and power is
steady green).
1.
Capture the MCA dump with the OA CLI command,
show
errdump all
or
show errdump dir mca
, and then
show errdump bundle_ID
<id>
for the bundle of
interest.
2.
Examine the OA CLI logs for entries related to processors,
processor power modules, shared memory, and core I/O
devices (See
Using event logs
on page 72 for more
details).
The issue is fixed when the root cause is determined and
corrected.
Table Continued
54
Troubleshooting