Skip Navigation Links | |
Exit Print View | |
Oracle Solaris Administration: Common Tasks Oracle Solaris 11 Information Library |
1. Locating Information About Oracle Solaris Commands
2. Managing User Accounts and Groups (Overview)
3. Managing User Accounts and Groups (Tasks)
4. Booting and Shutting Down an Oracle Solaris System
What's New in Booting and Shutting Down a System?
Support for Administratively Provided driver.conf Files
Boot and Shutdown Progress Animation
x86: Removal of Support for 32-Bit Kernel
Booting and Shutting Down an Oracle Solaris System (Overview)
Management of Boot Services by the Service Management Facility
Booting a System to a Specified State (Task Map)
Booting a System to a Specified State (Run Level)
Determining a System's Current Run Level
SPARC: How to Boot a System to a Multiuser State (Run Level 3)
x86: How to Boot a System to a Single-User State (Run Level S)
Shutting Down a System (Task Map)
How to Shut Down a System by Using the shutdown Command
Bringing a System to a Shutdown State (Run Level 0) by Using the init Command
How to Shut Down a System by Using the init Command
Accelerating the Reboot Process (Task Map)
Accelerating the Reboot Process
How to Initiate a Fast Reboot of a SPARC Based System
How to Initiate a Fast Reboot of an x86 Based System
Changing the Default Behavior of the Fast Reboot Feature
Initiating a Standard Reboot of a System That Has Fast Reboot Enabled
Booting From a ZFS Boot Environment (Task Map)
SPARC: Booting From a ZFS Boot Environment
SPARC: How to Display a List of Available Boot Environments During the Boot Sequence
SPARC: How to Boot From a ZFS Boot Environment or Root File System
Modifying Boot Parameters (Task Map)
SPARC: How to Determine the Default Boot Device
SPARC: How to Change the Default Boot Device by Using the Boot PROM
x86: How to Modify Boot Parameters by Using the eeprom Command
x86: How to Modify Boot Parameters at Boot Time
Adding a Linux Entry to the GRUB Menu After an Installation
Keeping a System Bootable (Task Map)
Determining Whether the boot-archive SMF Service Is Running
How to Clear a Failed Automatic Boot Archive Update by Manually Updating the Boot Archive
x86: How to Clear a Failed Automatic Boot Archive Update by Using the auto-reboot-safe Property
Where to Find More Information About Booting and Shutting Down a System
5. Working With Oracle Configuration Manager
6. Managing Services (Overview)
9. Managing System Information (Tasks)
10. Managing System Processes (Tasks)
11. Monitoring System Performance (Tasks)
12. Managing Software Packages (Tasks)
14. Scheduling System Tasks (Tasks)
15. Setting Up and Administering Printers by Using CUPS (Tasks)
16. Managing the System Console, Terminal Devices, and Power Services (Tasks)
17. Managing System Crash Information (Tasks)
18. Managing Core Files (Tasks)
19. Troubleshooting System and Software Problems (Tasks)
20. Troubleshooting Miscellaneous System and Software Problems (Tasks)
You might need to boot a stand-alone system from the network for recovery purposes, if the system cannot boot from the local disk. Any system can boot from the network, if a boot server is available.
To boot a SPARC based system from the network, a DHCP server is required. Also required is a boot server that provides tftp service. The DHCP server supplies the information that the client needs to configure its network interface.
You can boot an x86 based system directly from a network that supports the PXE network boot protocol. The default network boot strategy that is used for both PXE and non-PXE devices is DHCP. If no PXE or DHCP server is available, you can load GRUB from a diskette, a CD-ROM, or local disk.
For SPARC based systems, the process of booting over a local area network (LAN) and booting over a wide area network (WAN) is slightly different. In both network boot scenarios, the PROM downloads the booter from a boot server or an install server, which is inetboot in this case.
When booting over a (LAN), the firmware uses DHCP to discover the boot or install server. TFTP is then used to download the booter, which is inetboot in this case. When booting over a WAN, the firmware uses either DHCP or NVRAM properties to discover the install server, the router, and the proxies that are required for the system to boot from the network. The protocol that is used to download the booter is HTTP. In addition, the booter's signature might be checked with a predefined private key.
For more information, see the following references:
For more information about how DHCP works in this Oracle Solaris release, see Part II, DHCP, in Oracle Solaris Administration: IP Services.
For detailed instructions on booting an x86 system from the network, see Chapter 5, Booting an x86 Based System From the Network (Tasks), in Booting and Shutting Down Oracle Solaris on x86 Platforms.
For detailed instructions on booting a SPARC based system from the network, see Chapter 5, Booting a SPARC Based System From the Network (Tasks), in Booting and Shutting Down Oracle Solaris on SPARC Platforms.
For detailed information about setting up an install server, an install client, and other installation options, see Installing Oracle Solaris 11 Systems.