Setting the locator lights in ALOM and ILOM

Setting the locator lights in ALOM and ILOM

If you want to turn on or off the white locate lights on a Sun machine that uses the ALOM service processor firmware (entry level SPARC and CMT servers) it is simple, use:

setlocator on

or

setlocator off

If you want to do the same for servers that use ILOM service processor firmware (AMD based), use:

set /SYS/LOCATE value=Fast_Blink

or

set /SYS/LOCATE value=off

from the SP or if you are using ipmitool, send the "chassis identify" or "chassis identify off" commands.

Reset NVRAM (OBP) with the Double Pump method

To reset nvram if for some reason you can’t get to the console or run eeprom from the OS

1. Press the power button to power up the system.

2. Once the maintenance LED starts to flash rapidly, immediately press the Power button twice (similar to double-clicking a mouse, but leave a short gap of around 1 second between presses, to have the action reliably registered.) The actual time when you do the double press of the power button is the point in POST when the maintenance LED (wrench light) rapidly flashes.

NOTE:

If you double press too late or too soon, the system will power off. Do not get confused with the earlier occurrences of the maintenance and OK to remove LEDs flashing together. This is a part of the system test to make sure the LEDs are functional.

If you’re running POST even in MIN level, it will be several minutes depending upon your configuration, before the maintenance LED flashes rapidly.

A screen similar to the following is displayed to indicate that you have successfully reset the OpenBoot NVRAM configuration variables to their default values:

Sun Fire xxx (8 X UltraSPARC-III), Keyboard Present

OpenBoot x.x, 256 MB memory installed, Serial #xxxxxxxx.

Ethernet address xx:xx:xx:xx:xx:xx, Host ID: xxxxxxxx.

Safe NVRAM mode, the following nvram configuration variables have been
overridden:

diag-switch? is true
use-nvramrc? is false
input-device , output-device are defaulted
ttya-mode , ttyb-mode are defaulted

These changes are temporary and the original values will be restored after the next hardware or software reset. Once you are at the OK prompt, it is at this point you make your changes to the OBP parameters, or use set-defaults to reset all parameters to factory default settings.

OK (PROM) commands

OK (PROM) commands Function
================== =======================
.registers displays CPU contents
.speed number & speed of processors/bus
banner display some sysinfo
boot boot system with default option from default device
boot -a interactive boot mode
boot device -arguments boot to device with arguments
boot -r reconstructs the path_to_inst file
boot -s single user (maintenance) boot mode
boot -v verbose boot mode
cd path change to specified path
device-end exit device tree
go resume normal SOE ops
help command for the most part…useless
input-device keyboard set input device to keyboard
input-device ttya set input device to ttya
ls displays contents; unavailable in leaf mode
mfg-mode off disables manufacturing mode
mfg-mode on enables manufacturing mode
nvalias ‘alias-name’ dev-path aliases device-path to alias-name
obdiag enter menu-driven diags
output-device monitor set output device to monitor
output-device ttya set output device to ttya
power-off turn off system power
printenv displays environment settings
printenv nvramrc displays current alias informatoin
probe-ide probes IDE devices
probe-scsi probe devices on primary SCSI controller
probe-scsi-all probe all SCSI devices
pwd shows location in the device tree
reest-all soft reboot of the machine
set-defaults resets NVRAM
setenv auto-boot? false boot to PROM not SOE
setenv diag-switch? true enable full POST
show-disks shows all disks preset
show-sbus shows cards and slots in SBUS systems
show-tapes shows internal tape drives
sifting string shows commands containing string
wathc-net-all puts all eth devs in promiscuous mode
watch-net puts eth0 into promicuous mode
words shows available OBP commands

Rolling Red State Exception

Sun Fire V480, V880, 280R With 900 MHz CPUs May Panic or "Red State" Due to Incorrect L2 SRAM Parameter Settings in Firmware

Sun Alert ID: 55480

To recover from a "Red State" loop, turn the keyswitch to diagnostic mode which should break the loop and fail out a module. The system should be power cycled next and POST rerun to verify if there is a hard failure or not. If the item does not fail on the rerun of POST, you should contact Sun Services support to confirm whether you have experienced this issue.

This is fixed by updating firmware to 4.10.7 or better

How to update OBP

download the patch from SunSolve
Unzip the patch
copy the patch to the upload directory

# cp /home/test/116056-03/flash*latest /
# chmod 755 /flash-update*
# ls -al /flash*
-rwxr-xr-x 1 root other 2529836 Aug 27 09:10 flash-update-SunFire240-latest

Bring the system down

# init 0

from OBP

***************************************************************************
System now needs to be booted to run the Flash Update utility. Please note
this systems "boot-device" parameter is "disk".If system being updated has a
different parameter then that is what should be used in the following boot command.
Using the "printenv" command from the ok> prompt, and checking the "boot-device"
parameter will confirm what should be used.The Flash Update utility will then
be run.It will require four responses.I have indicated the the correct reponses
by putting them in double quotes.
***************************************************************************

{0} ok boot disk /flash-update-SunFire240-latest

answer OBP questions

How to update OBP

download the patch from SunSolve
Unzip the patch
copy the patch to the upload directory

# cp /home/test/116056-03/flash*latest /
# chmod 755 /flash-update*
# ls -al /flash*
-rwxr-xr-x 1 root other 2529836 Aug 27 09:10 flash-update-SunFire240-latest

Bring the system down

# init 0

from OBP

***************************************************************************
System now needs to be booted to run the Flash Update utility. Please note
this systems "boot-device" parameter is "disk".If system being updated has a
different parameter then that is what should be used in the following boot command.
Using the "printenv" command from the ok> prompt, and checking the "boot-device"
parameter will confirm what should be used.The Flash Update utility will then
be run.It will require four responses.I have indicated the the correct reponses
by putting them in double quotes.
***************************************************************************

{0} ok boot disk /flash-update-SunFire240-latest

answer OBP questions

Rolling Red State Exception

Sun Fire V480, V880, 280R With 900 MHz CPUs May Panic or "Red State" Due to Incorrect L2 SRAM Parameter Settings in Firmware

Sun Alert ID: 55480

To recover from a "Red State" loop, turn the keyswitch to diagnostic mode which should break the loop and fail out a module. The system should be power cycled next and POST rerun to verify if there is a hard failure or not. If the item does not fail on the rerun of POST, you should contact Sun Services support to confirm whether you have experienced this issue.

This is fixed by updating firmware to 4.10.7 or better