Getting To The Ok Prompt - Sun Microsystems Netra CP3060 User Manual

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.
When the operating system crashes, the system reverts to OpenBoot firmware
■
control.
During the boot process, when there is a serious hardware problem that prevents
■
the operating system from running, the system reverts to OpenBoot firmware
control.
When a serious hardware problem develops while the system is running, the
■
operating system transitions smoothly to run level 0.
When the OS is deliberately placed under the OpenBoot firmware control in order
■
to execute firmware-based commands.
4.3.1

Getting to the ok Prompt

There are different ways of reaching the ok prompt. The methods are not equally
desirable. See
TABLE 4-2
Access Method
Graceful shutdown of
the Solaris OS
Manual system reset
4-4 Netra CP3060 Board User's Guide • April 2009
for details.
TABLE 4-2
Ways of Accessing the ok Prompt
What to Do
From a shell or command tool window, issue an appropriate
command (for example, the shutdown or init command) as
described in Solaris system administration documentation.
Setting the OBP auto-boot variable to false causes the system
to stop at the ok? prompt the next time the blade server is reset.