Gracefully shutting down the system prevents data loss, enables you to warn users beforehand, and causes minimal disruption. You can usually perform a graceful shutdown, provided the Solaris OS is running and the hardware has not experienced serious failure.
ALOM System Controller break or console Command
Typing break from the sc> prompt forces a running server to drop into OpenBoot firmware control. If the operating system is already halted, you can use the console command instead of break to reach the ok prompt.
Caution – After forcing the system into OpenBoot firmware control, be aware that issuing certain OpenBoot commands (such as
L1-A (Stop-A) Keys or Break Key
When it is impossible or impractical to shut down the system gracefully, you can get to the ok prompt by typing the
Caution – After forcing the system into OpenBoot firmware control, be aware that issuing certain OpenBoot commands (such as
Manual System Reset
This section explains how to execute a manual reset and what happens when a manual reset occurs.
Caution – Forcing a manual system reset results in loss of system state data, and should be attempted only as a last resort. After a manual system reset, all state information is lost, which inhibits troubleshooting the cause of the problem until the problem reoccurs.
Use the ALOM system controller reset command, or poweron and poweroff commands, to reset the server. Reaching the ok prompt by performing a manual system reset or by
