![](/images/new-backgrounds/1174813/17481359x1.webp)
Caution – Forcing the server to the ok prompt suspends all application and operating system software. After you issue firmware commands and run firmware- based tests from the ok prompt, the system might not be able to resume where it left off.
If at all possible, back up system data before starting this procedure. Also exit or stop all applications and warn users of the impending loss of service. For information about the appropriate backup and shutdown procedures, see Solaris system administration documentation.
▼To Obtain the ok Prompt
1.Decide which method you need to use to reach the ok prompt. See “OpenBoot ok Prompt” on page 12 for details.
2.Follow the appropriate instructions in TABLE
TABLE 1-2 Ways of Accessing the ok Prompt
Access Method | What to Do |
|
|
Graceful shutdown of | • From a shell or command tool window, issue an appropriate |
the Solaris OS | command (for example, the shutdown or init command) as |
| described in Solaris system administration documentation. |
|
|
Break key
•From a Sun keyboard connected to the dongle cable, press the Stop and A keys simultaneously.*
•From an alphanumeric terminal configured to access the system console, press the Break key.
ALOM system | 1. | From the sc> prompt, type the break command. The break |
controller break and |
| command should put the system in a state in which the |
console commands |
| operating system software is not running and the server is |
|
| under OpenBoot firmware control. |
| 2. | Issue the console command. |
|
|
|
Manual system reset | • | From the sc> prompt, type the reset command. |
|
|
|
*Requires the OpenBoot configuration variable