During a custom JumpStart installation, the JumpStart program attempts to match the system that is being installed to the rules in the rules.ok file. The JumpStart program reads the rules from the first rule through the last. A match occurs when the system that is being installed matches all the system attributes that are defined in the rule. As soon as a system matches a rule, the JumpStart program stops reading the rules.ok file and begins to install the system, based on the matched rule's profile.
Table 26–1 Task Map: Setting Up a System for a Custom JumpStart Installation
Task |
Description |
For Instructions |
---|---|---|
Check if the system is supported |
Check the hardware documentation for system support in the Solaris 9 environment. |
Solaris 9 Sun Hardware Platform Guide |
Check if the system has enough disk space for the Solaris 9 software |
Verify that you have planned enough space to install the Solaris software on your system. |
Chapter 5, Guidelines for Allocating Disk Space and Swap Space (Planning) |
(Optional) Preconfigure system configuration information |
You can use the sysidcfg file or the name service to preconfigure installation information for a system. If you preconfigure system information, the installation program does not prompt you to supply the information during the installation. |
Chapter 7, Preconfiguring System Configuration Information (Tasks) |
Prepare the system for custom JumpStart installation |
Create and validate a rules file and profile files. |
Chapter 23, Preparing Custom JumpStart Installations (Tasks) |
(Optional) Prepare optional custom JumpStart features |
If you are using begin scripts, finish scripts, or other optional features, prepare the scripts or files. |
Chapter 24, Using Optional Custom JumpStart Features (Tasks) and Chapter 25, Creating Custom Rule and Probe Keywords (Tasks) |
(Optional) Set up the system to install over the network |
To install a system from a remote Solaris 9 DVD or Solaris 9 Software SPARC Platform Edition CD image, you need to set up the system to boot and install from an install server or a boot server. |
Chapter 12, Preparing to Install From the Network With CD Media (Tasks) |
(Optional) Prepare for a Solaris Flash archive installation |
Before installing a Solaris Flash archive, you need to follow specific steps. |
To Prepare to Install a Solaris Flash Archive With a Custom JumpStart Installation |
Install or upgrade |
Boot the system to initiate the installation or upgrade. |
SPARC: To Perform an Installation or Upgrade With the Custom JumpStart Program |
You can install a full archive or a differential archive using custom JumpStart. For an overview of a full or differential archive, see Chapter 17, Solaris Flash (Overview and Planning).
On the install server, create the custom JumpStart rules file.
For detailed instructions about creating custom JumpStart files, refer to Chapter 23, Preparing Custom JumpStart Installations (Tasks).
On the install server, create the custom JumpStart profile file.
For examples of Solaris Flash archive profiles, see Profile Examples.
From the existing list of custom JumpStart keywords in Chapter 23, Preparing Custom JumpStart Installations (Tasks), the only keywords valid when you install a Solaris Flash archive are the following:
Keyword |
Initial installation |
Update |
---|---|---|
archive_location |
X |
X |
fdisk (x86 only) |
X |
X |
filesys – You cannot set the filesys keyword to the value auto |
X |
|
forced_deployment |
|
X |
install_type — required |
X |
X |
local_customization |
X |
X |
no_content_check |
|
X |
no_master_check |
|
X |
root_device |
X |
X |
Set the value of the keyword install_type to one of the following types.
For a full archive installation, set the value to flash_install
For a differential archive installation, set the value to flash_update
Add the path to the Solaris Flash archive by using the archive_location keyword.
Refer to archive_location Keyword for details about the archive_location keyword.
Specify the file system configuration.
The Solaris Flash archive extraction process does not support auto-layout of partitions.
(Optional) If you want to install an additional Solaris Flash archive on the clone system, add one archive_location line for each archive that you want to install.
On the install server, add the clients that you are installing with the Solaris Flash archive.
For detailed instructions, refer to Adding Systems to Be Installed From the Network With a DVD Image or Adding Systems to Be Installed From the Network With a CD Image.
Perform the custom JumpStart installation on the clone systems.
For detailed instructions, refer to SPARC: To Perform an Installation or Upgrade With the Custom JumpStart Program.
If the system is part of a network, ensure that an Ethernet connector or similar network adapter is attached to your system.
If you are installing a system that is connected through a tip(1) line, ensure that your window display is at least 80 columns wide and 24 rows long.
To determine the current dimensions of your tip window, use the stty(1) command.
If you are using the system's DVD-ROM or CD-ROM drive to install the Solaris 9 software, insert the Solaris 9 SPARC Platform Edition DVD or the Solaris 9 Software 1 of 2 SPARC Platform Edition CD in the drive.
If you are using a profile diskette, insert the profile diskette in the system's diskette drive.
Boot the system.
If the system is new, out–of–the–box, turn on the system.
If you want to install or upgrade an existing system, shut down the system. At the ok prompt, type the following command:
ok boot cdrom:net - install [[url:ask]] [[dhcp]] [[nowin]] |
SPARC: The system checks hardware and system components and your SPARC system boots. Booting lasts several minutes.
If you did not preconfigure system information in the sysidcfg file, when prompted, answer the questions about system configuration.
Follow the instructions on the screen to install the software.
When the JumpStart program finishes installing the Solaris software, the system reboots automatically.
After the installation is finished, installation logs are saved in a file. You can find the installation logs in the following directories:
/var/sadm/system/logs
/var/sadm/install/logs