A P P E N D I X B |
XSCF Log Information |
This appendix explains the following XSCF log information that can be referenced using the XSCF Shell showlogs(8) command on the XSCF console.
The log types that can be referenced by the showlogs(8) command are shown below. See TABLE 8-3 for an outline of each log, its size, and generation number.
The logs that can be referenced by the showaudit(8), showad(8), and showldapssl(8) commands are shown below.
To reference the log related to a status notification or a fault information that occurred in the server, use these two commands:
The showlogs(8) error option displays fault information in a format specific to the platform. Conversely, the fmdump command displays fault information in a format compatible with the Oracle Solaris OS. This latter command is provided for users who are familiar with the Oracle Solaris OS. When the log is referenced by these two commands, there is a difference in display format but little difference in the information. Use these commands in the following cases:
1. Specify the error option on the XSCF Shell and perform the showlogs(8) command to reference the XSCF error log.
(The layout of the command example is subject to change without previous notice for functional improvement.)
In the example above, the following items are displayed:
Some subcomponents in the relevant component failed or degraded. |
|
The following explains cases where "FRU :" is displayed.
(a) "PSU#1, PSU#2" is displayed.
The above indicates the following: PSU#1 and PSU#2 were detected as the first and second suspect components, respectively. It might be necessary to replace the respective components as circumstances require.
(b) "PSU#1, PSU#2,*" is displayed.
The above indicates the following: PSU#1 and PSU#2 were detected as the first and second suspect components, respectively, with other components also detected. It might be necessary to replace the respective components.
(c) "IOU#0/PCI#3" is displayed.
The above indicates the following: IOU#0/PCI#3 was detected as the suspect component, and PCI slot No.3 of I/O unit No.0 is problematic. It might be necessary to replace the device connected to PCI slot No.3 as circumstances require.
(d) "MBU_A/MEMB#0/(MEM#02A)" is displayed.
The above indicates the following: MBU_A/MEMB#0/MEM#02A was detected as the suspect component, and memory slot No.02A of memory board No.0 on the MBU is problematic. It may be necessary to replace memory slot No.02A as circumstances require.
(e) "CMU#0/MEM#02A" is displayed.
The above indicates the following: CMU#0/MEM#02A was detected as the suspect component, and memory slot No.02A of CMU 0 is problematic. It may be necessary to replace memory slot No.02A as circumstances require.
(f) "CMU#0/MEM#02A-02B" is displayed.
The above indicates the following: CMU#0/MEM#02A-02B was detected as the suspect component, and memory slot No.02A and No.02B of CMU 0 are problematic. It may be necessary to replace the memory as pairs in memory slots No.02A and No.02B as circumstances require.
2. Use the message ID for accessing the specified URL to acquire detailed information corresponding to this problem. For the specified URL, see the web site information about the messages described in the Product Notes for your server.
For the message ID, the following information can be confirmed at the web site.
3. Repair the fault according to the recommended processing.
For details of the showlogs(8) command, see the XSCF Reference Manual or the man page.Use the fmdump(8) command to confirm the XSCF error log in a display format that is compatible with the Oracle Solaris OS.
1. Perform the fmdump(8) command on the XSCF Shell and reference the log.
(The layout of the command example is subject to change without previous notice for functional improvement.)
In the example above, the following items are displayed:
2. Use the message ID for accessing the specified URL to acquire detailed information corresponding to this problem. For the specified URL, see the web site information about the messages described in the Product Notes for your server. The information that can be referenced for the message ID is the same as that described in the item of showlogs(8) error.
3. After confirming the problem, repair the fault according to the recommended processing.
For details of the fmdump(8) command, see the XSCF Reference Manual or the main page.
When a power operation or resetting is performed in the server or domain, the XSCF firmware collects a power log. This section explains how to reference the power log. See TABLE 8-3 for the size and generation number of a power log.
Specify the power option on the XSCF Shell and perform the showlogs(8) command to reference power logs.
(The examples are subject to change without previous notice for functional improvement.)
In the examples above, the following items are displayed:
The power supply of the server common section was turned on. |
|
The power supply of the server common section was turned off. |
|
Factor by which the power event was instructed (Cause). The causes and their meanings are as follows:
Operating a switch on the operator panel caused a power event. |
|
The server environment or a hardware fault caused a power event. |
|
When an event occurs in the server, such as when the system status changes, the configuration is changed, the operator panel operated, or an event was sent to the Oracle Solaris OS in the server or domain, the XSCF firmware collects an XSCF event log. The field engineer and authorized service personnel use the XSCF event logs to analyze a fault that occurs, investigate the server operation status, or reference the history of maintenance operation. This section explains how to reference XSCF event logs. See TABLE 8-3 for the size and generation numbers of XSCF event logs.
Specify the event option on the XSCF Shell and perform the showlogs(8) command to reference XSCF event logs.
<Example> XSCF event logs are displayed as a list. XSCF> showlogs event Date Message Mar 30 17:45:31 JST 2005 System power on Mar 30 17:55:31 JST 2005 System power off |
(The example is subject to change without previous notice for functional improvement.)
In the example above, the following items are displayed:
This section explains how to reference the other main logs by using showlogs(8) command. For details of each log option of showlogs(8), see the XSCF Reference Manual or the main page. See TABLE 8-3 for the size and generation number of each log.
An event that occurred in the server is displayed as a monitoring message in real time for the user who logged in the XSCF. The XSCF firmware collects this message in a monitor message log. Specify the monitor option on the XSCF Shell and perform the showlogs(8) command to reference the monitor message log. The following items are displayed:
The XSCF firmware collects the environment and temperature and humidity history regarding the server in a temperature and humidity log. The temperature and humidity history log is displayed at ten-minute intervals. Specify the env option on the XSCF Shell and perform the showlogs(8) command to reference temperature and humidity history logs. The following items are displayed:
The XSCF firmware collects the domain console messages output through the XSCF in a console log. A console log is collected as one entry for each line feed code. In some cases, console logs may be called console message logs. Specify the console option on the XSCF Shell and perform the showlogs(8) command to reference console logs. The following items are displayed:
In case of panic, a console message is output to the domain console. This console message is collected by the XSCF firmware in a panic log. In some cases, panic logs may be called panic message logs. Specify the panic option on the XSCF Shell and perform the showlogs(8) command to reference panic logs. The following items are displayed:
After the domain power supply is turned on, console messages are output to the domain console until the running status is set. These console messages are collected by the XSCF firmware in an IPL log. In some cases, IPL logs may be called IPL message logs. Specify the ipl option on the XSCF Shell and perform the showlogs(8) command to reference IPL logs. The following items are displayed:
This section explains how to reference the audit logs by using the viewaudit(8) command. For details of each log option, audit class, and audit event of viewaudit(8), see the XSCF Reference Manual or the main page. See TABLE 8-3 for the size and generation number of each log.
Perform the viewaudit(8) command on the XSCF Shell.
In the example above, By default records are displayed in text format, one token per line, with a comma as the field separator.
The following list displays the Token types and their data (in display order):
Label, version, time, filename
Label, record byte count, version, event type, machine address, time (event recorded)
Label, audit session ID, UID, mode of operation, terminal type, remote IP address, remote port
Label, success/failure, privilege name, domain1, ... , domainN
Label, command name, argument1, ... , argumentN
Label, authentication result, user name, message, terminal type, remote IP address, remote port
Note - Some fields might not be output according to the environment. |
The following lists the principal audit events and Tokens:
Note - Some Tokens might not be output according to the environment. Also, it might be changed because of the function improvement without notice. |
This section explains how to reference the Active Directory logs by using the showad(8) command. For details of each log option of showad(8), see the XSCF Reference Manual or the main page. See TABLE 8-3 for the size and generation number of each log.
Perform the showad(8) command on the XSCF Shell.
When the Active Directory authentication and authorization for users, the diagnostic messages are logged. This log is for use in troubleshooting and is cleared on XSCF reset. Specify the log option on the XSCF Shell and perform the showad(8) command to reference Active Directory logs. The following items are displayed:
This section explains how to reference the LDAP/SSL logs by using the showldapssl(8) command. For details of each log option of showldapssl(8), see the XSCF Reference Manual or the main page. See TABLE 8-3 for the size and generation number of each log.
Perform the showldapssl(8) command on the XSCF Shell.
When the LDAP/SSL authentication and authorization for users, the diagnostic messages are logged. This log is for use in troubleshooting and is cleared on XSCF reset. Specify the log option on the XSCF Shell and perform the showad(8) command to reference LDAP/SSL logs. The following items are displayed:
Copyright © 2010, Oracle and/or its affiliates. All rights reserved.