■You can log in directly to the system controller from a device connected to the serial management port. See “Accessing the System Controller” on page 6.
■You can log in directly to ALOM CMT on the system controller using a connection through the network management port. See “Activating the Network Management Port” on page 7.
■If you have logged in to ALOM CMT directly through the system controller and then directed the system console to the serial management and network management ports, you can return to the prior ALOM CMT session by typing the system controller escape sequence (#.).
OpenBoot ok Prompt
The server with the Solaris OS installed is capable of operating at different run levels. A synopsis of run levels follows. For a full description of run levels, refer to the Solaris system administration documentation.
Most of the time, you operate the 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
When your server 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
■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 you deliberately place the system under firmware control in order to execute
18 SPARC Enterprise T1000 Server Administration Guide • April 2007