FUJITSU SPARC T5440 - Manual (Page 63)

Managing Faults 37
Detecting Faults Using the ILOM Event Log
Certain problems are recorded in the ILOM event log but not posted to the list of
faults displayed by the ILOM show faulty command. Inspect the ILOM event log
if you suspect a problem, but no entry appears in the ILOM show faulty command
output.
Related Information
■ “Diagnostic Flowchart” on page 11
■ “View ILOM Event Log” on page 37
■ “ILOM-to-ALOM CMT Command Reference” on page 53
■ SPARC Enterprise T5440 Server Installation and Setup Guide
■ SPARC Enterprise T5440 Server Administration Guide
■ Integrated Lights Out Manager 3.0 Supplement for SPARC Enterprise T5440 Server
▼ View ILOM Event Log
● Type the following command:
Note – The ILOM event log can also be viewed through the ILOM BUI or the ALOM
CMT CLI.
If a “major” or “critical” event is found that was not expected and not included
under ILOM show faulty than it may indicate a system fault. The following is an
example of unexpected major events in the log.
-> show /SP/logs/event/list
-> show /sp/logs/event/list
1626 Fri Feb 15 18:57:29 2008 Chassis Log major
Feb 15 18:57:29 ERROR: [CMP0 ] Only 4 cores, up to 32 cpus are
configured because some L2_BANKS are unusable
1625 Fri Feb 15 18:57:28 2008 Chassis Log major
Feb 15 18:57:28 ERROR: System DRAM Available: 004096 MB
1624 Fri Feb 15 18:57:28 2008 Chassis Log major
Feb 15 18:57:28 ERROR: [CMP1 ] memc_1_1 unused because associated
L2 banks on CMP0 cannot be used