Sun Fire V240 Server
 
Sun Fire V480 Server
 
Sun Fire V440 Server
 
Sun Fire V490 Server
 

PLA-Support>Sun Systems>SPARC>Usx/Blade/Netra>SN-SPARC: USx
 
.Old GCS Categories>Sun Microsystems>Servers>Entry-Level Servers
 

setenv diag-level max / menu

reset-all

However, this will not execute a maximum post of the system unless it is power-cycled. Don't be fooled into thinking that  full post is executed if the box is not power cycled. The output WILL change but will not be that of a full extended post.

Performing a power-cycle does not present a problem if the system is physically accessible. However, this can be a problem if the user  is connected to the machine remotely using a serial port connection, as opposed to an RSC (Remote System Control)  connection which will allow the machine to be powered off and on at will.

It is possible on several systems, although not all, to set an OBP (OpenBoot PROM) parameter which will determine the condition required to invoke a full extended post. On systems without this facility, a power cycle will still be necessary after setting diag-switch to  true and diag-level to max.

Systems that do allow this feature have one of  two new OBP parameters to support this. These are diag-trigger or post-trigger parameters, with the inclusion of each respective parameter being dependant on the revision of OBP installed.

The format of  each command is:

post-trigger <power-on-reset, error-reset, all-resets, user-reset, none>

diag-trigger <power-reset, error-reset, soft-reset, none>

Each variable, and its functionally, is explained below:

power-reset / power-on-reset (default)

Runs full firmware diagnostics only on power-on resets, including RSC-initiated power-on-resets. The system must be power-cycled for full diagnostics to be performed.

This option is useful to test system integrity if there has been a new component installed or if there has been hardware maintenance performed.

error-reset

Runs firmware diagnostics only if a system reset is triggered by hardware errors. This includes operating system panics and watchdog reset events. A full firmware diagnostics will not be executed by power cycling the system or using the reset-all command.

This is useful to test the system hardware after a catastrophic event which causes Solaris[TM] to stop execution and the system to reset. Do not use this option if you require optimum system availability as full diagnostics can take some time to complete.

all-resets (recommended)

Runs full firmware diagnostics on all reset events. The system will perform full diagnostics regardless of the circumstance behind the system reset.

This is useful to test the system in all events. Do not use this option if you require optimum system availability, as full system diagnostics can take some time to complete.

user-reset / soft-reset

Runs full firmware diagnostics only on using the reset-all command. Power-cycling the box will not produce a full diagnostics.

none

Disables the automatic triggering of firmware diagnostics by any reset event.

This option is useful to ensure system availability in the shortest time possible. However, it does not perform full diagnostics. You can still invoke firmware diagnostics manually by turning the front panel keyswitch to the Diagnostics position prior to powering on the system, if appropriate.

Once the variable post-trigger has had its variable set to one of the above options, the  the diag-switch variable is set to true and diag-level is set to max, the system will run its diagnostics according to the post-trigger variable used.

Please note that for  machines which do not support these two commands, a power-cycle will still be necessary to run full post first time around. Every subsequent full diagnostics, from this point onwards, should not require an additional power-cycle.

Place Sun Internal-Use Only content here. This content will be
published to internal SunSolve only.

This solution has no attachment