About The Ok Prompt - Sun Microsystems Sun Fire V440 Diagnostics And Troubleshooting Manual

You can log in directly to the ALOM system controller from a device connected to
the serial management port. See "How to Use the Serial Management Port" on
page 178.
You can log in directly to the ALOM system controller using a connection through
the network management port. See "How to Activate the Network Management
Port" on page 179.

About the ok Prompt

A Sun Fire V440 server with the Solaris operating environment installed is capable
of operating at different run levels. A synopsis of run levels follows. For a full
description, see the Solaris system administration documentation.
Most of the time, you operate a Sun Fire V440 server 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. At this
state, it is safe to turn off power to the system.
When a Sun Fire V440 system 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 in which OpenBoot firmware control can happen.
By default, the system comes up under OpenBoot firmware control before the
operating environment is installed.
The system boots to the ok prompt when the auto-boot? OpenBoot
configuration variable is set to false.
The system transitions to run level 0 in an orderly way when the operating
environment is halted.
The system reverts to OpenBoot firmware control when the operating
environment crashes.
During the boot process, when there is a serious hardware problem that prevents
the operating environment from running, the system reverts to OpenBoot
firmware control.
When a serious hardware problem develops while the system is running, the
operating environment transitions smoothly to run level 0.
You deliberately place the system under firmware control in order to execute
firmware-based commands or to run diagnostic tests.
Appendix A Configuring the System Console 171