Sun Microsystems CP3260 manual OpenBoot Firmware, Post Diagnostic and Error Message Format

4.2.2POST Diagnostic and Error Message Format

POST diagnostic and error messages are displayed on a console. The format of the these messages is the following:

Core-ID:Strand-ID ERROR: TEST = test-name

Core-ID:Strand-ID H/W under test = description

Core-ID:Strand-IDRepair Instruction

Core-ID:Strand-ID MSG = error-message-body

Core-ID:Strand-ID END_ERROR

The following is an example of a POST error message

3:2>ERROR: TEST = L2-Cache Functional 3:2>H/W under test = Core l2 Cache

3:2>Repair Instructions: Replace items in order listed by ’H/W under test’ above.

3:2>MSG = No way found to match tag address 00000000.00600000, state 3

3:2>END_ERROR

4.3OpenBoot Firmware

The Solaris OS installed operates at different run levels. For a full description of run levels, refer to the Solaris system administration documentation.

Most of the time, the OS operates at run level 2 or run level 3, which are multiuser states with access to full system and network resources. Occasionally, you might operate the system at run level 1, which is a single-user administrative state. However, the lowest operational state is run level 0.

When the OS is at run level 0, the ok prompt appears. This prompt indicates that the OpenBoot firmware is in control of the system.

There are a number of scenarios under which OpenBoot firmware control can occur.

By default, before the operating system is installed, the system comes up under OpenBoot firmware control.

■When the auto-boot? OpenBoot configuration variable is set to false, the system boots to the ok prompt.

■When the operating system is halted, the system transitions to run level 0 in an orderly way.

4-4Netra CP3260 Blade Server User’s Guide • April 2009