Sun SPARC Enterprise T5220 Server
 
Sun Fire USBRDT 5240 Uniboard
 
Sun SPARC Enterprise T5120 Server
 

GCS>Sun Microsystems>Boards>Misc
 
GCS>Sun Microsystems>Servers>CMT Servers
 
GCS>Support>KM>Content>Video
 

Applies to:

Goal

Solution

Viewing system Events in the Service Processor Using ALOM

Log into the service processor as a user with an ALOM interface.

In the ALOM interface you can use the showlogs command to display the history of events logged in the ALOM CMT event buffer.

These events include server reset events and all ALOM CMT commands that change the state of the system such as reset, poweroff, and

poweron.

sc> showlogs (This is typed into the ALOM interface.)

Each event recorded in the log has the following format:

Date ID: message

Where:

   date - the time at which the event occurred

   ID - a numerical identifier for the message type.

   message - a short description of the event

If you use the showlogs command without any option, ALOM displays the last 20 lines of the RAM event log.

Next, let's look at an example showing the output of the showlogs command with the -p p option.

The screen output will not pause unless you have specified the -v option together with the -p p option.

sc> showlogs -p p (This is typed into the ALOM interface.)

The -p p option displays the persistent event log. The persistent event log is comprised of only Major and Critical severity events.

You can see that these events are only major events as opposed to before when we were also seeing minor events in the output.

There is a -g option Controls the number of lines displayed on the screen at a given time.

Next we'll take a look at the showfaults command.

You can use the showfaults command to display current valid system faults. The standard output displays the fault ID, the faulted FRU device, and the fault message. This command also displays POST results.

sc> showfaults (This is typed into the ALOM interface.)

The showfaults command uses the -v argument to supply more verbose output.

sc> showfaults -v (This is typed into the ALOM interface.)

Using the FRU ID reported in the showfaults output, you can get more information using the showfru command.

As an example, we can get information on the motherboard.

sc> showfru /SYS/MB (This is typed into the ALOM interface.)

Use the consolehistory command to display system console messages

logged in ALOM CMT buffers. You can read the following system console logs:

- boot log - which contains POST, OpenBoot PROM, and Solaris boot messages received from the host server from the most recent reset.

or the

- run log - which contains the most recent console output from POST, OpenBoot PROM, and Solaris boot messages. In addition, this log records output from the host server's operating system.

sc> consolehistory -e 50 -g 30  (This is typed into the ALOM interface.)

The syntax is:

sc> consolehistory logname options

Where logname is the name of the log you want to display (boot or run).

If you type the consolehistory command without an option, ALOM CMT

displays the last 20 lines of the run log.

The -e specifies how many lines from the end of the buffer to display.

The -g specifies how many lines to display on the screen at a time.

If you don't specify -g, the screen output will not pause.

Viewing system Events in the Service Processor Using ILOM

Log into the service processor as root. This will give you the ILOM interface.

In the ILOM CLI, in order to view logs, console messages, and faults, type:

show /SP/logs/event/list (followed by a carriage return)

The first page of events is displayed.

Notice that the header at the top of the page, has five fields.

Starting on the left. there is an ID field. Every event is assigned an ID.

The next field is the date and time that the event occurred.

The next field is Class for the class of event, followed by Type for the type of event, and the last field is Severity.

Now you'll also notice that the events are displayed a page at a time. It prompts you to "press any key to continue, or q to quit", so I'll hit any key to see nthe next page of events.

I can continue to hit any key to view events.

At any time, I can quit this output by typing "q".

This solution has no attachment