Sun Microsystems, Inc.  Sun System Handbook - ISO 3.4 June 2011 Internal/Partner Edition
   Home | Current Systems | Former STK Products | EOL Systems | Components | General Info | Search | Feedback

Asset ID: 1-71-1018053.1
Update Date:2011-01-25
Keywords:

Solution Type  Technical Instruction Sure

Solution  1018053.1 :   Sun Fire[TM] Servers (12K/15K/E20K/E25K): POST Level  


Related Items
  • Sun Fire E25K Server
  •  
  • Sun Fire 12K Server
  •  
  • Sun Fire 15K Server
  •  
  • Sun Fire E20K Server
  •  
Related Categories
  • GCS>Sun Microsystems>Servers>High-End Servers
  •  
  • GCS>Sun Microsystems>Enterprise Computing>Systems Management
  •  

PreviouslyPublishedAs
229360


Applies to:

Sun Fire 12K Server - Version: Not Applicable and later   [Release: N/A and later ]
Sun Fire 15K Server - Version: Not Applicable and later    [Release: N/A and later]
Sun Fire E20K Server - Version: Not Applicable and later    [Release: N/A and later]
Sun Fire E25K Server - Version: Not Applicable and later    [Release: N/A and later]
All Platforms

Goal

POST (Power On Self Test) is the software that takes control of the domain hardware on a Sun Fire[TM] 12K/15K/E20K/E25K system at power-on or equivalent reset.

It probes, tests, and configures domain resources into a working system and transfers control to Open Boot Prom or Process (OBP).

Solution

A more detailed description of POST can be found in the System Management Services (SMS) 1.6 Software Administrator Guide;  See Chapter 8 Domain Control, Section Hardware Control.

POST provides support for hardware testing, hardware fault isolation and records information about failed and marginal components (facilitating diagnosis and service action).  The default POST level is 16, which requires no additional .postrc file settings.

POST is able to recognize if a domain is rebooted or reset, in which case it switches to "quick" POST. No testing takes places, all POST does is hardware probing and configuring. A quick POST be recognized in the POST log by POST being run at level 7.

For the reasons listed above it is strongly discouraged to have any .postrc files that specifiy level 7 POST. The quickly achieved gain in boot time will in most cases result in significant future downtime as a result of running a domain on untested hardware.

The stages, phases, tests, and subtests that are executed, and the amount of diagnostic testing performed in each, is dictated by the POST level. The POST level is specified either within the .postrc file or via the command line (supersedes .postrc file).

A platform-wide .postrc file can be found in:

/etc/opt/SUNWSMS/config/platform/.postrc
Syntax: level

A domain-unique .postrc file can be found in:

/etc/opt/SUNWSMS/config/[A-R]/.postrc
Syntax: level

The specified level in the .postrc file determines the amount of test performed and the thoroughness with which it is done. Higher levels result in more testing. If you want to change the level of testing, you need to change your .postrc file and run a setkeyswitch command to restart your domain.

For SMS releases 1.3 and below:
POST will first look a .postrc file in the current working directory, then in the domain unique directory for the domain post is run against, and if these locations both do not contain a usable .postrc file it will use the platform wide .postrc file.

For SMS releases 1.4 and higher this behavior has been changed to prevent inadvertently running an incorrect .postrc. The flow is now:
When checking for a local .postrc file first obtain the current working directory. If it is any of:

/etc/opt/SUNWSMS/config/[A-R]
/etc/opt/SUNWSMS/config/platform
/var/tmp

then do not attempt to open a local .postrc file. A note will be placed in the post log indicating the .postrc was ignored.

Extended POST

An extended POST run is often used to verify a service action that has taken place on the platform. In large configurations, POST times can be extensive particularly if the POST level specified is high.

The command "hpost -?level" prints a brief summary of what each level does. The output below is created by running "hpost -?level". For the latest meaning of the different POST levels, run "hpost -?level" again.

Level Description
7 The minimum level. Hardware probing and configuration, no testing.
16 Default level. Basic testing of processor, memory, and I/O.
24 Adds some additional locations for some tests (e.g. functional and memory structure testing).
32 Some CPU Functional tests added, and all locations are tested in all structures except for Memory & ECache.
64 The highest "normal" diag level. Adds all locations and patterns for all tests except extensive Memory and ECache tests. Advanced CPU functional tests, MP Testing. Error detection tests.
96 Adds all patterns/locations for Memory & ECache tests.
127 The maximum level, Memory & ECache Data Validation. ECache stress.

References


Internal References
"Starcat POST Functional Specification" at http://esp.west/starcat/post/

Document 1012012.1 hpost exit codes (ecode) Overview

The function, operation, and execution of Starcat POST at
http://pts-platform.uk/twiki/pub/Products/ProdDocumentationStarcat/post.pdf

RFE 4860765 for updated .postrc selection behavior.

SF12K, SF15K, E20K, E25K, POST, postrc, OBP, hpost, setkeyswitch
Previously Published As 78597

Attachments
This solution has no attachment
  Copyright © 2011 Sun Microsystems, Inc.  All rights reserved.
 Feedback