Sun Fire[TM] 12K/15K Server: Terminating a hpost reset/recovery loop test cycle on a domain

Asset ID:	1-72-1001848.1
Update Date:	2012-01-25
Keywords:

Solution Type Problem Resolution Sure

Solution 1001848.1 : Sun Fire[TM] 12K/15K Server: Terminating a hpost reset/recovery loop test cycle on a domain

Applies to:

Sun Fire 12K Server
Sun Fire 15K Server
All Platforms

Symptoms

A failed hardware component can cause a Sun Fire[TM] 12K/15K Server (SF12K/SF15K) domain to loop in hpost as dsmd tries to identify the failed component via hpost testing.

Cause

When this happens, the hpost level is incremented to a higher level (more testing) after every unsuccessful boot attempt so that each successive hpost takes longer to complete.
Example is hpost -Q (i.e. 7), 16, 32, 64, 96, 127.

However, it is possible that a domain can appear to be looping in hpost, but the hpost level is NOT incrementing, i.e. hpost 16 is executed every time. This can be an indication of a problem during boot, rather than a hardware failure, the most common cause being an incorrect boot-device or boot path.

Solution

Following is an Example of the recommended course of action to remedy this issue.

First, keyswitch off the domain

has-sc0:sms-svc:4> setkeyswitch -d A off

Wait for all boards to power down.

Then, from the SC as the sms-svc user, change the auto-boot? param to false via the setobpparams. In the following example we are making changes to OBP params for domain A.

has-sc0:sms-svc:2> setobpparams -d A auto-boot?=false

Note: It is recommended that the setobpparams command be run even if showobpparams already shows that 'auto-boot?' is set to false.

Then check via showobpparams to see if the changes have been made.

has-sc0:sms-svc:3> showobpparams -d A
auto-boot?=false
diag-switch?=true
fcode-debug?=false
use-nvramrc?=true
security-mode=none

Now, keyswitch the domain back on.

has-sc0:sms-svc:5> setkeyswitch -d A on

After powering on, the domain may go through a quick(-Q) hpost which may fail, depending on the previous failure cause. After the next hpost, the domain will go to OBP. Standard troubleshooting practices can now be followed to determine the cause: check post logs for hardware failures, etc.

Note: Please consult the man pages for more information on showobpparams, setobpparams, and setkeyswitch.

Please also check Doc ID 1003319.1 (Sun Fire[TM] 12K/15K/E20K/E25K: POST level increments with repeated error) for further informations.

Product
Sun Fire 12K Server
Sun Fire 15K Server

Internal Section

See http://has.us.oracle.com/starcat/ for more information on hpost levels and timing.

Keywords: auto-boot, hpost, loop test, setobpparams

Previously Published As 71598

Attachments

This solution has no attachment