Sun Fire V445 Server Administration Guide - SCN Research
Sun Fire V445 Server Administration Guide - SCN Research
Sun Fire V445 Server Administration Guide - SCN Research
Create successful ePaper yourself
Turn your PDF publications into a flip-book with our unique Google optimized e-Paper software.
You can direct where system log messages are stored or have them sent to a remote<br />
system by setting up system message logging. For more information, see “How to<br />
Customize System Message Logging” in the System <strong>Administration</strong> <strong>Guide</strong>: Advanced<br />
<strong>Administration</strong>, which is part of the Solaris System Administrator Collection.<br />
In some failure situations, a large stream of data is sent to the system console.<br />
Because ALOM system controller log messages are written into a circular buffer that<br />
holds 64 Kbytes of data, it is possible that the output identifying the original failing<br />
component can be overwritten. Therefore, you may want to explore further system<br />
console logging options, such as SRS Net Connect or third-party vendor solutions.<br />
For more information about SRS Net Connect, see “About <strong>Sun</strong> Remote Services Net<br />
Connect” on page 213.<br />
More information about SRS Net Connect is available at:<br />
http://www.sun.com/service/support/<br />
Certain third-party vendors offer data logging terminal servers and centralized<br />
system console management solutions that monitor and log output from many<br />
systems. Depending on the number of systems you are administering, these might<br />
offer solutions for logging system console information.<br />
For more information about the system console, see Chapter 2.<br />
Predictive Self-Healing<br />
The Solaris Fault Manager daemon, fmd(1M), runs in the background on every<br />
Solaris 10 or later system and receives telemetry information about problems<br />
detected by the system software. The fault manager then uses this information to<br />
diagnose detected problems and initiate proactive self-healing activities such as<br />
disabling faulty components.<br />
fmdump(1M), fmadm(1M), and fmstat(1M) are the three core commands that<br />
administer the system generated messages produced by the Solaris Fault Manager.<br />
See “About Predictive Self-Healing” on page 172 for details. Also refer to the man<br />
pages for these commands.<br />
Core Dump Process<br />
In some failure situations, a <strong>Sun</strong> engineer might need to analyze a system core dump<br />
file to determine the root cause of a system failure. Although the core dump process<br />
is enabled by default, you should configure your system so that the core dump file is<br />
saved in a location with adequate space. You might also want to change the default<br />
216 <strong>Sun</strong> <strong>Fire</strong> <strong>V445</strong> <strong>Server</strong> <strong>Administration</strong> <strong>Guide</strong> • August 2006
Change language