Sun Microsystems Sun Fire V440 Diagnostics And Troubleshooting Manual page 105

consolehistory run -v Command Output (Continued)
CODE EXAMPLE 4-9
syslog service starting.
Print services started.
volume management starting.
The system is ready.
Sun-SFV440-a console login: May
keyswitch change event - state = UNKNOWN
May 9 14:52:57 Sun-SFV440-a rmclomv: Keyswitch Position has changed to Unknown
state.
May 9 14:52:58 Sun-SFV440-a rmclomv: NOTICE: keyswitch change event - state =
LOCKED
May 9 14:52:58 Sun-SFV440-a rmclomv: KeySwitch Position has changed to Locked
State.
May 9 14:53:00 Sun-SFV440-a rmclomv: NOTICE: keyswitch change event - state =
NORMAL
May 9 14:53:01 Sun-SFV440-a rmclomv: KeySwitch Position has changed to On State.
sc>
7. Examine the ALOM boot log. Type:
sc> consolehistory boot -v
The ALOM boot log contains boot messages from POST, OpenBoot firmware, and
Solaris software from the host server's most recent reset.
The following sample output shows the boot messages from POST.
consolehistory boot -v Command Output (Boot Messages
CODE EXAMPLE 4-10
From POST)
Keyswitch set to diagnostic position.
@(#)OBP 4.10.3 2003/05/02 20:25 Sun Fire V440
Clearing TLBs
Power-On Reset
Executing Power On SelfTest
0>@(#) Sun Fire[TM] V440 POST 4.10.3 2003/05/04 22:08
/export/work/staff/firmware_re/post/post-build-
4.10.3/Fiesta/chalupa/integrated
0>Hard Powerup RST thru SW
0>CPUs present in system: 0 1
9 14:52:57 Sun-SFV440-a rmclomv: NOTICE:
(firmware_re)
Chapter 4 Monitoring the System 87