3-44
SPARC Enterprise T1000 Server Service Manual • April 2007
3. Run the
clearfault
command with the UUID provided in the showfaults
output:
4. Clear the fault from all persistent fault records.
In some cases, even though the fault is cleared, some persistent fault information
remains and results in erroneous fault messages at boot time. To ensure that these
messages are not displayed, perform the following command:
fmadm repair
UUID
Example:
3.6
Collecting Information From Solaris OS
Files and Commands
With the Solaris OS running on the server, you have the full compliment of Solaris
OS files and commands available for collecting information and for troubleshooting.
If POST, ALOM, or the Solaris PSH features do not indicate the source of a fault,
check the message buffer and log files for notifications for faults. Hard drive faults
are usually captured by the Solaris message files.
Use the
dmesg
command to view the most recent system message. To view the
system messages log file, view the contents of the
/var/adm/messages
file.
3.6.1
Checking the Message Buffer
1. Log in as superuser.
sc>
clearfault 7ee0e46b-ea64-6565-e684-e996963f7b86
Clearing fault from all indicted FRUs...
Fault cleared.
#
fmadm repair 7ee0e46b-ea64-6565-e684-e996963f7b86
Summary of Contents for SPARC ENTERPRISE T1000
Page 1: ......
Page 2: ......
Page 6: ......
Page 11: ...Contents ix Index Index 1 ...
Page 12: ...x SPARC Enterprise T1000 Server Service Manual April 2007 ...
Page 16: ...xiv SPARC Enterprise T1000 Server Service Manual April 2007 ...
Page 25: ...Preface xxiii Reader s Comment Form ...
Page 32: ...2 4 SPARC Enterprise T1000 Server Service Manual April 2007 ...
Page 35: ...Chapter 3 Server Diagnostics 3 3 FIGURE 3 1 Diagnostic Flow Chart flow chart ...
Page 86: ...3 54 SPARC Enterprise T1000 Server Service Manual April 2007 ...
Page 126: ...A 4 SPARC Enterprise T1000 Server Service Manual April 2007 ...
Page 130: ...Index 4 SPARC Enterprise T1000 Server Service Manual April 2007 ...
Page 131: ......
Page 132: ......