How to Collect Data From the ALOM Logs

Asset ID:	1-75-1007631.1
Update Date:	2017-05-23
Keywords:

Solution Type Troubleshooting Sure

Solution 1007631.1 : How to Collect Data From the ALOM Logs

Applies to:

Sun Fire V240 Server - Version All Versions and later
Sun Fire V210 Server - Version All Versions and later
Sun Fire V440 Server - Version All Versions and later
All Platforms

Purpose

This document will explain how to get the log information available through ALOM.

Troubleshooting Steps

Steps to Follow
ALOM has the ability to save log information which maybe useful in troubleshooting system problems. It captures and saves system console messages as well as ALOM event messages. There are two commands involved and they are available at the ALOM level from the sc> prompt.

The "consolehistory" command displays all output sent to the console by the
operating system. This would include all commands entered, messages from
syslog,output from Solaris[TM] commands, but not anything from POST or OBP
before the Solaris boot has started..The output would be as
if the solaris "script" command was used at the console.This output is
logged in ALOM buffers.  The "consolehistory" command displays the "boot"
and "run" logs.The "boot" log contains POST, OpenBoot PROM,and Solaris boot
messages received from the host server from the most recent reset.
The "run" log contains the most recent system console output from
POST,OpenBoot PROM, and Solaris boot messages. In addition, this log
records output from the host server's operating environment.What that means
is error messages that would normally
be driven to the console by Solaris.Each buffer can contain up to 64 Kbytes
of information. Each buffer can contain up to 64 Kbytes of information.If
ALOM senses a host server reset, it begins to write
that data into the boot log buffer. When the server senses that the Solaris
operating environment is up and running, ALOM switches the buffer to the
run log.
There are command options that vary the amount of output to the screen:

-v Displays the entire contents of the specified log.
-g Specifies the number of lines to display before pausing the output to
the screen.
-e Displays the number of lines that you specify for lines from the end of
the log buffer.
-b Displays the number of lines that you specify for lines from the
beginning of the log buffer.

Examples of running the "consolehistory" command from ALOM:

sc> consolehistory -v
sc> consolehistory boot -v
sc> consolehistory run -v
sc> consolehistory run -v -g 5
sc> consolehistory boot -b 10
sc> consolehistory run -e 15

Example output of "consolehistory -v"
sc> consolehistory -v
Contents of run buffer:
bash-2.03# ls
3510FCarray.sh
E-T_port_upgrade-downgrade_1.05.tar.Z
README_3510FCarray_script.txt
README_SFS_base_packages.txt
README_install_it.txt
bash-2.03# reboot
Mar 19 14:25:42 pts-task reboot: rebooted by root
Mar 19 14:25:42 pts-task syslogd: going down on signal 15
Mar 19 14:25:42 rpcbind: rpcbind terminating on signal.
syncing file systems... done
rebooting...

(#)OBP 4.11.4 2003/07/23 08:04 Sun Fire V210/V240,Netra 240

Clearing TLBs

Loading Configuration
.
.
.
The other command is "showlogs".Use the showlogs command to display the
history of all events logged in the ALOM event buffer.These events include
server reset events and all ALOM commands that change the state
of the system (such as reset, poweroff, and poweron).The "showlogs" command
has two stores of data. There is a persistant event log stored in NVRAM,
and a log stored in the buffer.
There are commands options that vary what data is output to the screen, as
well as how much.
-v Displays the entire contents of the buffer and the contents of NVRAM
(the persistent event log).
-b Displays the events from the beginning of the buffer
-e Displays the events from the end of the buffer
-g Controls the number of lines displayed on the screen at a given time

Examples of running the "showlogs" command from ALOM:
sc> showlogs
sc> showlogs -v  showlogs -b 100
sc> showlogs -e 10
sc> showlogs -v -g 10
Example output of "showlogs -v"
sc> showlogs -v
Persistent event log
--------------------
MAR 11 03:32:15 : 0006000b: "SC Request to send Break to host."
MAR 11 03:33:17 : 0006000b: "SC Request to send Break to host."
MAR 11 03:35:09 : 0006000b: "SC Request to send Break to host."
Log entries since MAR 16 20:00:49
----------------------------------
MAR 16 20:00:49 : 00060003: "SC System booted."
MAR 18 13:46:06 : 00060000: "SC Login: User admin Logged on."
MAR 18 13:49:25 : 00040002: "Host System has Reset"
MAR 18 13:49:26 : 0004000b: "Host System has read and cleared bootmode."
MAR 18 13:50:16 : 0004004f: "Indicator MB.ACT is now ON"
MAR 18 14:26:23 : 00040002: "Host System has Reset"
MAR 18 14:26:24 : 0004000b: "Host System has read and cleared bootmode."
MAR 18 14:26:29 : 0004004f: "Indicator MB.ACT is now OFF"
.
.
.
To summarize, in order to get the most possible data for troubleshooting
purposes, it is recommended to get the output from the following commands
run from ALOM:

sc> consolehistory -v
sc> showlogs -v

For more detailed information about using ALOM please see:

Sun™Advanced Lights Out Manager
(ALOM) 1.6 Administration Guide
Part No. 819-2445-11

Product
Sun Fire V440R Server
Sun Fire V440 Server
Sun Fire V240 Server
Sun Fire V210 Server

Attachments

This solution has no attachment