Loss of RSC console input/output on Sun Fire[TM] V480/V880 post upgrading OBP to 4.15.x

Asset ID:	1-72-1009167.1
Update Date:	2011-05-12
Keywords:

Solution Type Problem Resolution Sure

Solution 1009167.1 : Loss of RSC console input/output on Sun Fire[TM] V480/V880 post upgrading OBP to 4.15.x

Applies to:

Sun Fire 280R Server
Sun Fire V480 Server
Sun Fire V490 Server
Sun Fire V880 Server
Sun Fire V890 Server
All Platforms

Symptoms

After successfully upgrading either a Sun Fire[TM] V480 or Sun Fire[TM] V880 OBP to version 4.15.x while using the RSC console, it is possible, under certain circumstances and post the subsequent reboot, that any input/output via the RSC interface ceases.

The following is a "cut down" output example from a Sun Fire V480 that had its OBP upgraded to version 4.15.1 using the RSC as the input/output device:

{2} ok boot disk /flash-update-SunFire480-latest
Boot device: /pci@9,600000/SUNW,qlc@2/fp@0,0/disk@0,0 File and args: /flash-update-SunFire480-latest
Loading ufs-file-system package 1.4 04 Aug 1995 13:02:54.
FCode UFS Reader 1.12 00/07/17 15:48:16.
Loading: /platform/SUNW,Sun-Fire-480R/ufsboot
Loading: /platform/sun4u/ufsboot
.
.
.
Firmware Release(s) Firmware Release(s)
Currently Existing in the System Available for Installation / Install?
---------------------------------- -------------------------------------------
OBP 4.13.2 2004/03/29 10:08 OBP 4.15.1 2004/06/02 16:06 YES
POST 4.13.0 2004/02/12 19:17 POST 4.15.0 2004/05/27 13:25 YES
.
.
.
Type h for help, q to quit, Return or Enter to continue: cont

Erasing the top half of the Flash PROM.
Programming OBP into the top half of the Flash PROM.
Verifying OBP in the top half of the Flash PROM.

Erasing the bottom half of the Flash PROM.
Programming OBP into the bottom half of Flash PROM.
Verifying OBP in the bottom half of the Flash PROM.

Erasing the top half of the Flash PROM.
Programming POST into the top half of Flash PROM.
Verifying POST in the top half of the Flash PROM.

Programming was successful.

Resetting ...

RSC Alert: Host System has Reset
OpenBoot Re-Configuration Reset

OpenBoot internal data format/version changed (4 to 7)
This may be expected if the system firmware has been updated.

****************************************************************

NOTICE: Updating OpenBoot NVRAM diagnostic configuration variables
setenv service-mode? false
setenv diag-switch? false
setenv diag-trigger power-on-reset error-reset
setenv diag-level max
setenv verbosity normal
setenv diag-script normal
setenv fcode-debug? false

OpenBoot Re-Configuration Reset

@(#)OBP 4.15.1 2004/06/02 16:06 Sun Fire 4XX
Front Panel Keyswitch is in Diagnostic position.
System is initializing in Service Mode.
.
.
.
0:0> POST Passed all devices.
0:0>POST: Return to OBP.

CPU0: System POST Completed
Pass/Fail Status = 0000.0000.0000.0000
ESB Overall Status = ffff.ffff.ffff.ffff
.
.
.
Probing /pci@8,700000 Device 6 ide disk cdrom
Probing /pci@9,600000 Device 1 network
Probing /pci@9,600000 Device 2 SUNW,qlc fp disk
Probing /pci@9,700000 Device 1 usb
Probing /pci@9,700000 Device 2 network

<<-- NO FURTHER INPUT OR OUTPUT TO THE RSC CONSOLE AFTER THIS -->>

Cause

The most likely cause of this situation is that the server's keyswitch was in the "DIAG" position when the OBP upgrade was performed.

Solution

OBP version 4.15.x introduces new functionality called "Service Mode" intended to be used by a local service engineer, that facilitates fault isolation and recovery of systems that appear to be non-functional. When initiated, service mode overrides the settings of key OpenBoot configuration variables:

auto-boot? = false
diag-level = max
diag-trigger = power-on-reset error-reset user reset
input-device = Factory default
output-device = Factory default
verbosity = max
diag-script = normal
test-args = subtests,verbose

where "Factory default" equals 'ttya' on Sun Fire server systems.

Service Mode is enabled by either setting the 'service-mode' variable manually ('setenv') or by putting the keyswitch in the "DIAG" position. Either of these options will result in the 'input-device' and 'output-device' variables being set to 'ttya', which explains why on the reboot we lose the RSC console.

The documentation that is provided in OpenBoot PROM Enhancements for Diagnostic Operation provides extensive details of the "Service Mode" functionality and how to return the server to "Normal Mode" but the basic steps are:

1. Set the keyswitch to the "Normal" or "Lock" position.

2. Set the 'service-mode' variable to false:

ok> setenv service-mode? false

3. Reset the server:

ok> reset-all

The documentation provided with the patch and/or systems that already shipped with OBP 4.15.x or later, also includes details of how to use the RSC to override "Normal Mode" diagnostics when it is required by remote administrators.

Relief/Workaround
1. Confirm if the system has booted to Solaris[TM] ('auto-boot?=true') by either using 'ping' or 'telnet'.

2. If the server is accessible then login and perform a graceful shutdown and power-off:

# init 5

If the server is not accessible then use the RSC 'poweroff' command:


rsc> poweroff
Are you sure you want to turn your system power off (Yes/No)?  y

3. Once the RSC interface has confirmed that the server is powered down enter the following to set the next boot to "Normal Mode":

RSC Alert: Host system has shut down.

rsc> bootmode -u normal

The RSC bootmode interface always overrides the local setting of the keyswitch, so all bootmode commands such as "skip_diag" or "diag" will also force "Normal Mode" can be used as alternatives to the above command. For further details, see the documentation (817-6957) provided with the patch in PDF format, or OpenBoot PROM Enhancements for Diagnostic Operation

4. Now power-on the server and the 'input-device' and 'output-device' will return to the RSC interface until the next reboot:


rsc> poweron
Are you sure you want to turn your system power on (Yes/No)? y

These steps will need to be repeated each time the server is rebooted until you disable "Service Mode" as detailed above.

Additional Information
To prevent future server OBP upgrades falling into the same trap ensure that the keyswitch (either visually or by using 'prtdiag -v') is set to the "NORMAL" position prior to performing the upgrade.

OBP, 4.15.1, rsc, v480, v880, 480, 880, v490, v890, 490, 890, 280R, diagnostics, console
Previously Published As
79449

Change History
Date: 2009-12-01
User name: Dencho Kojucharov
Action: Updated
Comments: Currency check, audited by Dencho Kojucharov, Entry-Level SPARC Content Lead
Date: 2004-12-20

Attachments

This solution has no attachment