How to capture errors via RSC

Asset ID:	1-71-1012454.1
Update Date:	2018-02-15
Keywords:

Solution Type Technical Instruction Sure

Solution 1012454.1 : How to capture errors via RSC

Applies to:

Sun Fire V480 Server - Version All Versions and later
Sun Fire V490 Server - Version All Versions and later
Sun Fire V880 Server - Version All Versions and later
Sun Fire V880z Visualization Server - Version All Versions and later
Sun Fire V890 Server - Version All Versions and later
All Platforms
***Checked for relevance on 12-APR-2011***

Goal

Description

System console output during firmware initialization (OBP) and firmware diagnostics ( POST/Obdiag) are not captured in persistent storage, thereby lacking an ability to retrieve valuable data to help identify and isolate a faulty component when a fault occurs.

This Document describes how to view any console Errors captured by the Remote System Control (RSC) card.

Solution

Steps to Follow

Consider a scenario when Solaris traps to the firmware (OBP), resulting in either a Red State Exception, Watchdog Reset, or Fatal Reset.
Console output is not captured in the /var/adm/messages file (via syslogd), because we are no longer in the runtime environment. Indeed, the Red State Exception, Watchdog Reset, and Fatal Reset message are produced by the system firmware.

If no terminal connection exists to console port or the shell being used does not support logging (scroll), valuable service data can be inaccessible.

Volume server products have traditionally lacked an architectural design that provides persistent storage at the firmware layer, however the service processor (RSC) provides an acceptable level of temporary storage for recording console output during firmware.

Recomendation:

Ensure the service processor (RSC) is properly installed. Refer to DocID 1011888.1

Usage:

Here are a few of the commands to help you capture the state of the server and show you what errors and events have occurred.

showenvironment - Will display the status of Power supplies, fans, LEDs, RSC, and temperatures that are available for each platform.

loghistory - Displays all logins to the RSC, reboots, resets and power events in the buffer.

consolehistory boot - Will show changes to the nvram settings as well as changes to the boot PROM. Also displays output to the console up to and including commands run from Solaris. The boot buffer contains POST, OpenBoot PROM, and UNIX boot messages received from the server for the most recent boot.

consolehistory run - The run buffer contains the most recent data received from the server operating system.

consolehistory oboot - The oboot buffer contains POST, OpenBoot PROM, and UNIX boot messages for the first power-on boot, the original boot.

consolehistory orun - The orun buffer contains the data received from the server's operating system after the first reboot that follows a power-on boot (the original boot).

break - Send break to system console. Use with care on running system!

console - Connect to system console.

help - Shows you additional commands to run.

Other RSC HOWTOs:

Document: 1011888.1 Setup of RSC.
Document: 1006030.1 RSC Command Quick Reference Guide
Document: 1005997.1 Navigate between OS and RSC.
Document: 1007570.1 RSC password reset.

RSC, V880, V480, V490, V890, 280R, console output
Previously Published As
79704

Attachments

This solution has no attachment