Performing a Custom JumpStart Installation (Tasks)
This chapter describes how to perform a custom JumpStart installation. You need to follow these procedures on the system on which you intend to install the Solaris 9 software.
Performing a Custom JumpStart Installation
Task Map: Setting Up a System for a Custom JumpStart Installation
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. | |
(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 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) |
Install or upgrade | Boot the system to initiate the installation or upgrade. | "To Perform an Installation or Upgrade With the Custom JumpStart Program" |
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 DVD or the Solaris 9 Software 1 of 2 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]
cdrom
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.
net
Specifies to boot from an install server on the network.
url
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
ask
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.
dhcp
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.
nowin
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.
Note - The system checks hardware and system components and your 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