Messages In Each Function - Sun Microsystems Sun SPARC Enterprise M3000 User Manual

A.2

Messages in Each Function

This section explains each Solaris OS and XSCF function by which the user can
recognize status notification or fault information in the server, including messages.
Recognizing Status Notification or Fault Information by a Message on
the Domain Console
1. The user recognizes status notification or fault information in a console
message such as a syslog message and FMA message output to the domain
console. The following shows an example of the FMA message on the domain
console.
<Example> FMA Message
SUNW-MSG-ID: SUN4U-800J-C0, TYPE: Fault, VER: 1, SEVERITY: Critical
EVENT-TIME: Wed Jun 28 17:45:36 PDT 2006
PLATFORM: SUNW,SPARC-Enterprise, CSN: -, HOSTNAME: dc102
SOURCE: eft, REV: 1.5
EVENT-ID: 24fe9f8c-f302-4128-c5b8-b38a4083769f
DESC: The number of errors associated with this CHIP has exceeded acceptable
levels. Refer to http://sun.com/msg/SUN4U-800J-C0 for more information.
Refer to SUN4U-800J-C0 for more information.
AUTO-RESPONSE: An attempt will be made to remove the affected CHIP from
service.
IMPACT: The system will not be functioning at the same performance level with
the CHIP removal.
REC-ACTION: Schedule a repair procedure to replace the affected CHIP. Use
fmdump -v -u to identify the smallest CPU/Strand ID of the affected CORE on
this CHIP.
Note – The message format may change in future releases.
2. Fault information in the FMA message is stored in the log. Therefore, the log
file can be referenced on the domain console. Perform a Solaris OS command
such as the syslog reference command or fmdump(1M) command on the domain
console. For how to identify fault information by using these commands, see
the Solaris OS documentation.
Appendix A Warning and Information Messages A-3