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 29–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. | |
(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 26, 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 27, Using Optional Custom JumpStart Features (Tasks) and Chapter 28, 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 DVD or Solaris 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 15, 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 for an initial installation or a differential archive for an update. You can use the custom JumpStart installation method or use Solaris Live Upgrade to install an archive on an inactive boot environment.
For an overview of a full or differential archive, see Chapter 20, Solaris Flash (Overview and Planning).
For procedures about installing an archive on an inactive boot environment by using Solaris Live Upgrade, see To Install a Solaris Flash Archive With a Profile (Command-Line Interface).
On the install server, create the custom JumpStart rules file.
For detailed instructions about creating custom JumpStart files, refer to Chapter 26, 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 Table 31–2, the only keywords valid when you install a Solaris Flash archive are the following:
Table 29–2 Solaris Flash Archive Keywords
Keyword |
Initial Installation |
Differential Archive |
---|---|---|
(required)archive_location |
X |
X |
fdisk (x86 only) |
X |
X |
filesys Note – You cannot set the filesys keyword to the value auto. |
X |
|
forced_deployment |
|
X |
(required) install_type |
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.
For details about the archive_location keyword, refer to 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 SPARC Platform Edition DVD or the Solaris 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]] |
Specifies to boot from a CD or a DVD.
For a system with an older EEPROM, replace cdrom with sd(0,6,2) to boot from the system's CD-ROM or DVD-ROM drive.
Specifies to boot from an install server on the network.
Specifies the location of the custom JumpStart files. You can specify a URL for files that are located in the following places:
Local hard disk
file://jumpstart_dir_path/compressed_config_file |
NFS server
nfs://server_name:IP_address/jumpstart_dir_path/compressed_config_file |
HTTP server
http://server_name:IP_address/jumpstart_dir_path/ compressed_config_file&proxy_info |
If you placed a sysidcfg file in the compressed configuration file, you must specify the IP address of the server that contains the file, as in the following example:
http://131.141.2.32/jumpstart/config.tar |
If you saved the compressed configuration file on an HTTP server that is behind a firewall, you must use a proxy specifier during boot. You do not need to specify an IP address for the server that contains the file. You must specify an IP address for the proxy server, as in the following example:
http://www.shadow.com/jumpstart/ config.tar&proxy=131.141.6.151 |
Specifies that the installation program prompt you to type the location of the compressed configuration file after the system boots and connects to the network.
If you bypass the prompt by pressing Return, the installation program interactively configures the network parameters. The installation program then prompts you for the location of the compressed configuration file. If you bypass the prompt by pressing Return, the Solaris suninstall program begins.
Specifies to use a DHCP server to obtain network installation information that is needed to boot the system.
If you do not specify to use a DHCP server, the system uses the /etc/bootparams file or the name service bootparams database.
Specifies not to begin the X program. You do not need to use the X program to perform a custom JumpStart installation, so you can reduce the installation time by using the nowin option.
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