Sun Microsystems V490 Manual Do Utilizador
Chapter 4
Network Interfaces and System Firmware
49
To help maximize system availability, make sure that any redundant network
interfaces reside on separate PCI buses, supported by separate PCI bridges. For
additional details, see “About the PCI Cards and Buses” on page 31.
interfaces reside on separate PCI buses, supported by separate PCI bridges. For
additional details, see “About the PCI Cards and Buses” on page 31.
About the ok Prompt
A Sun Fire V490 system with Solaris OS software is capable of operating at different
run levels. A synopsis of run levels follows; for a full description, see the Solaris
system administration documentation.
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 V490 system at run level 2, or run level 3,
which are multiuser states with access to full system and network resources.
Occasionally, you may operate the system at run level 1, which is a single-user
administrative state. However, the most basic state is run level 0. At this state, it is
safe to turn off power to the system.
which are multiuser states with access to full system and network resources.
Occasionally, you may operate the system at run level 1, which is a single-user
administrative state. However, the most basic state is run level 0. At this state, it is
safe to turn off power to the system.
When a Sun Fire V490 system is at run level 0, the ok prompt appears. This prompt
indicates that the OpenBoot firmware is in control of the system.
indicates that the OpenBoot firmware is in control of the system.
There are a number of scenarios in which this can happen.
■
The system comes up under OpenBoot firmware control before the Solaris OS
software is installed, or whenever the auto-boot? OpenBoot configuration
variable is set to false.
software is installed, or whenever the auto-boot? OpenBoot configuration
variable is set to false.
■
The system transitions to run level 0 in an orderly way when the Solaris OS
software is halted.
software is halted.
■
The system reverts to OpenBoot firmware control when the Solaris OS software
crashes.
crashes.
■
During the boot process, there is a serious hardware problem that prevents the
Solaris OS software from running, and the system reverts to OpenBoot firmware
control.
Solaris OS software from running, and the system reverts to OpenBoot firmware
control.
■
A serious hardware problem develops while the system is running, and the
Solaris OS software transitions smoothly to run level 0.
Solaris OS software transitions smoothly to run level 0.
■
You deliberately place the Sun Fire V490 system under firmware control in order
to execute firmware-based commands or run diagnostic tests.
to execute firmware-based commands or run diagnostic tests.
It is the last of these scenarios that most often concerns you as an administrator,
since there will be times when you need to reach the ok prompt. The several ways to
do this are outlined in “Ways of Reaching the ok Prompt” on page 50. For detailed
instructions, see “How to Get to the ok Prompt” on page 126.
since there will be times when you need to reach the ok prompt. The several ways to
do this are outlined in “Ways of Reaching the ok Prompt” on page 50. For detailed
instructions, see “How to Get to the ok Prompt” on page 126.