Note - For Oracle Solaris 10 or 11, JumpStart can help you eliminate some or most of the manual tasks of setting up the Oracle Solaris Operating System for the first time on multiple servers. For more information about using a JumpStart image, see the Oracle Solaris 10 8/11 Installation Guide: Custom JumpStart and Advanced Installations.
Before You Begin
The following requirements must be met prior to starting the Oracle Solaris 10 or 11 PXE boot installation.
To use PXE to boot the installation media over the network, you should have completed the following tasks:
For Oracle Solaris 10, ensure that the PXE/boot JumpStart install server is properly setup and accessible to your server on the network.
For Oracle Solaris 11, ensure that the Automated Installation (AI) image install server is setup and accessible to your server over the network.
Ensure that the Oracle Solaris 10 or 11 installation media is available for PXE boot. For details, see one of the following documents:
For Oracle Solaris 10 8/11, see “Planning to Install Over the Network” in the Oracle Solaris 10 8/11 Installation Guide: Network-Base Installations at: http://docs.oracle.com/cd/E23823_01/index.html
For Oracle Solaris 11 11/11, see Creating a Custom Oracle Solaris 11 Installation Image at: http://docs.oracle.com/cd/E23824_01/index.html.
For Oracle Solaris 11.1, see Creating a Custom Oracle Solaris 11.1 Installation Image at: http://docs.oracle.com/cd/E26502_01/index.html.
Ensure that the Automated Installation install server has the MAC address of the network interface from which the system will PXE boot. As an example, if you want to PXE boot from NET0, you can obtain its MAC address by logging in to the Oracle ILOM SP as root, and typing:
-> show /SYS/MB/NET0 fru_macaddress /SYS/MB/NET0 Properties: fru_macaddress = 00:21:28:e7:77:24
Ensure that the BIOS mode configured on your system is compatible with the Oracle Solaris Operating System you are installing. For more details refer to Switch Between Legacy BIOS and UEFI BIOS Mode.
From the local server, press the Power button (approximately 1 second) on the front panel of the server to turn the server off, then press the Power button again to power on the server.
From the Oracle ILOM web interface, click Host Management > Power Control and select Reset from the Select Action list box.
From the Oracle ILOM CLI on server SP, type: reset /System
The BIOS screen appears.
Note - The next events occur very quickly; therefore, focused attention is needed for the following steps. Please watch carefully for these messages as they appear on the screen for a brief time.
Note - PXE boot is enabled by default, however, this step directs you to verify that PXE boot is enabled just in case it was disabled. Once you have verified that PXE boot is enabled, you can omit this step on subsequent PXE boots.
The BIOS Setup Utility appears.
This causes the server to reset. After resetting, the BIOS screen appears again.
The Please Select Boot Device menu appears, listing the available boot devices. The screen that appears will be different depending on whether you have BIOS configured for legacy BIOS mode or UEFI mode.
For legacy BIOS, the following screen appears:
For UEFI mode, the following screen appears:
Note - Your Please Select Boot Device menu options might differ depending on the type of disk controller installed in your server.
The PXE boot port is the physical network port configured to communicate with your network install server.
The GRUB menu appears.
For instructions for completing the PXE installation, refer to the following documents:
For Oracle Solaris 10 8/11, see “Planning to Install Over the Network” in the Oracle Solaris 10 8/11 Installation Guide: Network-Base Installations at: http://docs.oracle.com/cd/E23823_01/index.html.
For Oracle Solaris 11 11/11, refer to the Creating a Custom Oracle Solaris 11 Installation Image at: http://docs.oracle.com/cd/E23824_01/index.html.
For Oracle Solaris 11.1, refer to the Creating a Custom Oracle Solaris 11.1 Installation Image at: http://docs.oracle.com/cd/E26502_01/index.html.