Solaris 10 5/09 Installation Guide: Custom JumpStart and Advanced Installations

Chapter 6 Performing a Custom JumpStart Installation (Tasks)

This chapter describes how to perform a custom JumpStart installation on a SPARC based or an x86 based system. You need to follow these procedures on the system on which you intend to install the Solaris software.


Note –

If you are installing a Solaris ZFS root pool, see Chapter 9, Installing a ZFS Root Pool With JumpStart for limitations and profile examples.


Limitations for a JumpStart Installation

A number of issues might cause problems during a JumpStart installation. Review the table below for specific information.

Table 6–1 JumpStart Installation Limitations

Issue 

Description 

For More Information 

The sample JumpStart script is no longer required to suppress the NFSv4 prompt 

For the Solaris 10 release, a sample JumpStart script, set_nfs4_domain, was provided on media to prevent being prompted during a JumpStart installation. This script suppressed the NFSv4 prompt during installation. This script is no longer required. Starting with the Solaris 10 8/07 release, use the sysidcfg keyword, nfs4_domain that suppresses being prompted. The set_nfs4_domain script no longer works to suppress a prompt.

If you have non-global zones installed and the new nfs4_domain keyword exists in the sysidcfg file, the first boot of a non-global zone sets the domain. Otherwise, the Solaris interactive installation program is displayed and you are prompted to provide a domain name before the boot process completes.

nfs4_domain Keyword in Solaris 10 5/09 Installation Guide: Network-Based Installations

Selecting a keyboard language in the sysidcfg file prevents a prompt

If your keyboard is not self-identifying and you want to prevent being prompted during your JumpStart installation, select the keyboard language in your sysidcfg file. For JumpStart installations, the default is for the U.S. English language. To select another language and its corresponding keyboard layout, set the keyboard keyword in your sysidcfg file.

If you have non-global zones, use Solaris Live Upgrade to upgrade 

You can upgrade a system that has non-global zones installed with JumpStart, but Solaris Live Upgrade is the recommended program to upgrade. JumpStart might require extensive upgrade time, because the time required to complete the upgrade increases linearly with the number of installed non-global zones. 

Solaris 10 5/09 Installation Guide: Solaris Live Upgrade and Upgrade Planning

A Solaris Flash archive cannot contain non-global zones 

If you use a Solaris Flash archive to install, an archive that contains non-global zones is not properly installed on your system.  

For general information about creating non-global zones, see System Administration Guide: Solaris Containers-Resource Management and Solaris Zones.

A Solaris Flash archive can only be created and installed from a UFS file system. 

You cannot create a Solaris Flash archive from a ZFS root pool. Also, you cannot install a Solaris Flash archive on a ZFS root pool. 

 

SPARC: Additional hardware requirements 

Refer to your hardware documentation for any additional requirements for your platform that might be required to complete a JumpStart installation. 

 

SPARC: Task Map: Setting Up a System for a Custom JumpStart Installation

Table 6–2 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 environment. 

Solaris Sun Hardware Platform Guide at http://docs.sun.com

Check if the system has enough disk space for the Solaris software. 

Verify that you have planned enough space to install the Solaris software on your system. 

Chapter 4, System Requirements, Guidelines, and Upgrade (Planning), in Solaris 10 5/09 Installation Guide: Planning for Installation and Upgrade

(Optional) Set system parameters. 

You can preconfigure system information to avoid being prompted for the information during the installation or upgrade. 

Chapter 2, Preconfiguring System Configuration Information (Tasks), in Solaris 10 5/09 Installation Guide: Network-Based Installations

Prepare the system for custom JumpStart installation. 

Create and validate a rules file and profile files.

Chapter 3, 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 4, Using Optional Custom JumpStart Features (Tasks) and Chapter 5, Creating Custom Rule and Probe Keywords (Tasks)

(Optional) Prepare to install the Solaris software from the network. 

To install a system from a remote Solaris Operating System DVD or Solaris Software for SPARC Platforms CD image, you need to set up the system to boot and install from an install server or a boot server. 

Chapter 5, Installing From the Network With DVD Media (Tasks), in Solaris 10 5/09 Installation Guide: Network-Based Installations

Chapter 6, Installing From the Network With CD Media (Tasks), in Solaris 10 5/09 Installation Guide: Network-Based Installations

(Optional) Prepare for a Solaris Flash archive installation. 

Set up specifics for a Solaris Flash archive installation. 

To Prepare to Install a Solaris Flash Archive With a Custom JumpStart Installation

Perform an installation or upgrade. 

Boot the system to initiate the installation or upgrade. 

SPARC: To Perform an Installation or Upgrade With the Custom JumpStart Program

SPARC: Performing 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. When 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.

ProcedureTo Prepare to Install a Solaris Flash Archive With a Custom JumpStart Installation

You can install a full archive for an initial installation or if you have already installed an archive, 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. This procedure provides the instructions to install an archive with custom JumpStart.

  1. Review the following limitations.

    Description 

    Example 

    Caution: When using the archive_location keyword to install a Solaris Flash archive, the archive and the installation media must contain identical operating system versions.

    For example, if the archive is a Solaris 10 5/09 operating system and you are using DVD media, then you must use Solaris 10 5/09 DVD media to install the archive. If the operating systems versions do not match, the installation on the clone system fails. 


    Caution – Caution –

    A Solaris Flash archive cannot be properly created when a non-global zone is installed. The Solaris Flash feature is not compatible with the Solaris Zones partitioning technology. If you create a Solaris Flash archive, the resulting archive is not installed properly when the archive is deployed under these conditions:

    • The archive is created in a non-global zone

    • The archive is created in a global zone that has non-global zones installed


     

  2. On the install server, create the custom JumpStart rules file.

    For detailed instructions about creating custom JumpStart files, refer to Chapter 3, Preparing Custom JumpStart Installations (Tasks).

  3. 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 8–2, the only keywords valid when you install a Solaris Flash archive are the following:

    Keyword 

    Initial Installation 

    Differential Archive 

    (required)archive_location

    fdisk (x86 only)

    filesys


    Note –

    You cannot set the filesys keyword to the value auto.


     

    forced_deployment

     

    (required) install_type

    local_customization

    no_content_check

     

    no_master_check

     

    package

     

    root_device

    1. 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.

    2. 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.

    3. Specify the file system configuration.

      The Solaris Flash archive extraction process does not support auto-layout of partitions.

    4. (Optional) If you want to install additional packages at the same time you install an archive, use the package keyword. For more information, see package Profile Keyword (UFS and ZFS).

    5. (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.

  4. On the install server, add the clients that you are installing with the Solaris Flash archive.

    For detailed instructions, refer to the following:

  5. 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.

ProcedureSPARC: To Perform an Installation or Upgrade With the Custom JumpStart Program

  1. If the system is part of a network, ensure that an Ethernet connector or similar network adapter is attached to your system.

  2. 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.

  3. If you are using the system's DVD-ROM or CD-ROM drive to install the Solaris software, insert the Solaris Operating System for SPARC Platforms DVD or the Solaris Software for SPARC Platforms - 1 CD in the drive.

  4. If you are using a profile diskette, insert the profile diskette in the system's diskette drive.

  5. 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 appropriate options for the boot command. The syntax of the boot command is the following.


      ok boot [cd–dvd|net] - install [url|ask] options
      

      For example, if you type the following command, the OS is installed over the network by using a JumpStart profile.


      ok boot net - install http://131.141.2.32/jumpstart/config.tar
      

      For a description of the boot command options, see the following table.


    SPARC only –

    The system checks hardware and system components and your SPARC based system boots. Booting lasts several minutes.


  6. If you did not preconfigure system information in the sysidcfg file, when prompted, answer the questions about system configuration.

  7. 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

SPARC: Command Reference for the boot Command

The syntax of the boot command is the following.


ok boot [cd–dvd|net] - install [url|ask] options

The following table describes the command-line options for the boot command that are appropriate for a JumpStart installation.

Option 

Description 

[cd–dvd|net]

Specifies to boot from a CD or a DVD or to boot from an install server on the network. 

  • cd-dvd - Use cdrom to boot from a CD or a DVD.

  • net - Specifies to boot from an install server on the network.

[url| ask]

Specifies the location of the custom JumpStart files or prompts you for the location.  

  • url – Specifies the path to the files. You can specify a URL for files that are located in an HTTP or HTTPS server:

    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. The prompt happens after the system boots and connects to the network. If you use this option, you are not able to do a completely hands off JumpStart installation.

    If you bypass the prompt by pressing Return, the Solaris installation program interactively configures the network parameters. The installation program then prompts you for the location of the compressed configuration file.

options

  • dhcp – Specifies to use a DHCP server to obtain network installation information that is needed to boot the system. This option is not needed for a JumpStart installation. If you do not specify to use a DHCP server by typing dhcp, the system uses the /etc/bootparams file or the naming service bootparams database. For example, you would not specify dhcp if you wanted keep a static IP address.

  • The options nowin and text do not apply to a JumpStart installation. These options are useful with an interactive installation. For more information, see To Install or Upgrade With the Solaris Installation Program in Solaris 10 5/09 Installation Guide: Basic Installations.

x86: Task Map: Setting Up a System for a Custom JumpStart Installation

Table 6–3 x86: Task Map: Setting Up a System for a Custom JumpStart Installation

Task 

Description 

For Instructions 

Determine if you need to preserve an existing operating system and user data. 

If the existing operating system on the system uses the entire disk, you must preserve the existing operating system so it can co-exist with the Solaris 10 5/09 software. This decision determines how to specify the fdisk(1M) keyword in the system's profile.

x86: fdisk Profile Keyword (UFS and ZFS)

Check if the system is supported. 

Check the hardware documentation for system support in the Solaris environment. 

Hardware manufacturer's documentation 

Check if the system has enough disk space for the Solaris software. 

Verify that you have planned enough space to install the Solaris software on your system. 

Chapter 4, System Requirements, Guidelines, and Upgrade (Planning), in Solaris 10 5/09 Installation Guide: Planning for Installation and Upgrade

(Optional) Set system parameters. 

You can preconfigure system information to avoid being prompted for the information during the installation or upgrade. 

Chapter 2, Preconfiguring System Configuration Information (Tasks), in Solaris 10 5/09 Installation Guide: Network-Based Installations

Prepare the system for custom JumpStart installation. 

Create and validate a rules file and profile files.

Chapter 3, 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 4, Using Optional Custom JumpStart Features (Tasks) and Chapter 5, Creating Custom Rule and Probe Keywords (Tasks)

(Optional) Prepare to install the Solaris software from the network. 

To install a system from a remote Solaris Operating System for x86 Platforms DVD or Solaris Software For x86 Platforms CD image, you need to set up the system to boot and install from an install server or a boot server. 

Chapter 6, Installing From the Network With CD Media (Tasks), in Solaris 10 5/09 Installation Guide: Network-Based Installations

(Optional) Prepare for a Solaris Flash archive installation. 

Set up specifics for a Solaris Flash archive installation. 

To Prepare to Install a Solaris Flash Archive With a Custom JumpStart Installation

Perform an installation or upgrade. 

Boot the system to initiate the installation or upgrade. 

x86: To Perform an Installation or Upgrade With the Custom JumpStart Program and With GRUB

x86: Performing 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 rule. A match occurs when the system that is being installed matches all of 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.

You can install a Solaris Flash archive with custom JumpStart. For instructions, see To Prepare to Install a Solaris Flash Archive With a Custom JumpStart Installation.

Choose one of the following procedures:

Procedurex86: To Perform an Installation or Upgrade With the Custom JumpStart Program and With GRUB

Use this procedure to install the Solaris OS for an x86 based system with the GRUB menu.

  1. If the system is part of a network, ensure that an Ethernet connector or similar network adapter is attached to your system.

  2. If you want to install 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.

  3. Decide if you want to use a profile diskette.

    A profile diskette is no longer used to boot the system but, a diskette can be prepared that includes only the JumpStart directory. The diskette can then be used situations such as performing a JumpStart installation and booting off the CD-ROM.

    • If you are using a profile diskette, insert the profile diskette into the system's diskette drive.

    • If you are not using a profile diskette, continue with step Step 4.

  4. Decide how to boot the system.

    • If you boot from the Solaris Operating System DVD or the Solaris Software - 1 CD, insert the disc. Your system's BIOS must support booting from a DVD or CD.

    • If you boot from the network, use Preboot Execution Environment (PXE) network boot. The system must support PXE. Enable the system to use PXE by using the system's BIOS setup tool or the network adapter's configuration setup tool.

  5. (Optional) If you are booting from a DVD or CD, change the boot setting in your system's BIOS and set to boot from DVD or CD media. See your hardware documentation for instructions.

  6. If the system is off, turn the system on. If the system is on, reboot the system.

    The GRUB menu is displayed. This menu provides a list of boot entries.


    GNU GRUB version 0.95 (631K lower / 2095488K upper memory)
    +-------------------------------------------------------------------+
    |Solaris 10 5/09 image_directory                                      |
    |Solaris Serial Console ttya                                           |
    |Solaris Serial Console ttyb (for lx50, v60x and v65x               |
    +-------------------------------------------------------------------+
    Use the ^ and v keys to select which entry is highlighted. Press
    enter to boot the selected OS, 'e' to edit the commands before
    booting, or 'c' for a command-line.

    The image_directory is the name of the directory where the installation image is located. The path to the JumpStart files was defined with the add_install_client command and the -c option.


    Note –

    Instead of booting from the GRUB entry now, you can edit the boot entry. After editing the GRUB entry, you then perform the JumpStart installation. For instructions about how to edit the GRUB entry and a list of installation options, see x86: Performing a Custom JumpStart Installation by Editing the GRUB Boot Command.


  7. At the prompt, perform one of the following instructions:


    Select the type of installation you want to perform:
     
             1 Solaris Interactive
             2 Custom JumpStart
             3 Solaris Interactive Text (Desktop session)
             4 Solaris Interactive Text (Console session)
             5. Apply driver updates
             6. Single User Shell
    Enter the number of your choice.
    Please make a selection (1-6).

    To select the custom JumpStart method, type 2 and press Enter.

    The JumpStart installation begins.


    Note –
    • If you do not make a selection within 30 seconds, the Solaris interactive installation program begins. You can stop the timer by typing any key at the command line.

    • If you select items 1, 3, or 4, you install with an interactive installation. For information about interactive installations, see Solaris 10 5/09 Installation Guide: Basic Installations.

    • If you select item 5, you install driver updates.

    • If you select item 6, you can perform maintenance tasks.


  8. If you did not preconfigure system information in the sysidcfg file, when prompted, answer the questions about system configuration.

  9. Follow the instructions on the screen to install the software.

    When the JumpStart program finishes installing the Solaris software, the system reboots automatically. Also, the GRUB menu.lst file is automatically updated. Then the instance of Solaris that you have installed appears in the next use of the GRUB menu.

    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

x86: Performing a Custom JumpStart Installation by Editing the GRUB Boot Command

In some circumstances such as for debugging purposes, you might want to modify the GRUB boot command. The following procedure describes the steps to edit the GRUB boot command before performing the custom JumpStart installation.

Procedurex86: To Modify the GRUB Boot Command

  1. To begin the installation, proceed with Step 1 through Step 5 in the preceding procedure, x86: To Perform an Installation or Upgrade With the Custom JumpStart Program and With GRUB.

  2. If the system is off, turn the system on. If the system is on, reboot the system.

    The GRUB menu is displayed. This menu provides a list of boot entries. The entry that is provided is the Solaris instance to be installed.


    GNU GRUB version 0.95 (631K lower / 2095488K upper memory)
    +-------------------------------------------------------------------+
    |Solaris 10 5/09 image_directory                                      |
    |Solaris Serial Console ttya                                                |
    |Solaris Serial Console ttyb (lx50, v60x and v68)                  |
    +-------------------------------------------------------------------+
    Use the ^ and v keys to select which entry is highlighted. Press
    enter to boot the selected OS, 'e' to edit the commands before
    booting, or 'c' for a command-line.

    The image_directory is the name of the directory where the installation image is located.


    Note –
    • If you used the NFS to set the path to the JumpStart directory with the add_install_client command and the -c option, then you do not need to include the path in the boot entry.

    • If you are not using NFS, then you must note the path to the compressed configuration file that contains the JumpStart directory.


  3. To stop the booting process and use the menu entry editor, type e.

    The GRUB edit menu is displayed.


    kernel /I86PC.Solaris_11-8/multiboot kernel/unix -B console=ttyb,\
    install_media=131.141.2.32:/export/mary/v11 \
    module /I86PC.Solaris_11-8/x86.new
  4. Use the arrow keys to select the boot entry.

  5. To edit the selected command, type e.

    A command that is similar to the following example displays.


    grub edit>kernel /I86PC.Solaris_11-8/multiboot kernel/unix -B \
    console=ttyb,install_media=131.141.2.32:/export/mary/_\
    module /I86PC.Solaris_11-8/x86.new
  6. Edit the command by typing the options that you need.

    The syntax for a JumpStart installation is the following.


    grub edit>kernel /I86PC.Solaris_11-image_directory/multiboot kernel/unix/ \
    - install [url|ask] options -B install_media=media_type
    

    For a description of JumpStart options, see x86: Command Reference for Booting the System.

    In the following example, the OS is installed over the network with a custom JumpStart profile.


    kernel /I86PC.Solaris_11-8/multiboot kernel/unix/ - install \
    -B install_media=131.141.2.32:/export/mary/v11 \
    module /I86PC.Solaris_11-8/x86.new
  7. To accept the edits, press Enter.

    Your changes are saved and the GRUB main menu is displayed.


    Note –

    Pressing the Escape key returns you to the GRUB main menu without saving your changes.


  8. To begin the installation, type b.

x86: Command Reference for Booting the System

The following table describes the command-line options for the GRUB menu boot command. The options listed are appropriate for a JumpStart installation.

The syntax of the boot command is the following.


kernel /I86PC.Solaris_11-image_directory/multiboot kernel/unix/ - install \
[url|ask] options -B install_media=media_type
Table 6–4 GRUB Menu Boot Command Reference

Option 

Description 

- install

Performs a custom JumpStart installation. 

In the following example, the system boots from DVD media and the following options were used: 

  • - install performs a custom JumpStart

  • file://jumpstart/config.tar finds the JumpStart profile on the local disk


kernel /I86pc.Solaris_11.8/multiboot - install file://jumpstart/config.tar \
 -B install_media=dvdrom module /I86Solaris_11.8/x86.new

[url| ask]

Specifies the location of the custom JumpStart files or prompts you for the location.  

  • url – Specifies the path to the files. You can specify a URL for files that are located on an HTTP or HTTPS server:

    The syntax for an HTTP server is the following:


    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:


      kernel /I86pc.Solaris_11.8/multiboot install \
      http://192.168.2.1/jumpstart/config.tar \
       -B install_media=192.168.2.1/export/Solaris_11.8/boot \
      module /I86PC.Solaris_11.8/x86.new
    • 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:


      kernel /I86pc.Solaris_11.8/multiboot install \
      http://www.shadow.com/jumpstart/config.tar&proxy=131.141.6.151 \
       -B install_media=192.168.2.1/export/Solaris_11.8/boot \
      module /I86PC.Solaris_11.8/x86.new
  • ask – Specifies that the installation program prompt you to type the location of the compressed configuration file. You are prompted after the system boots and connects to the network. If you use this option, you are not able to do a completely hands off JumpStart installation.

    If you bypass the prompt by pressing Return, the Solaris installation program interactively configures the network parameters. The installation program then prompts you for the location of the compressed configuration file.

    The following example performs a custom JumpStart and boots from DVD media. You are prompted to type the location of the configuration file after the system connects to the network.


    kernal /boot/multiboot kernel/unix install ask -B \
    install_media=192.168.2.1:export/sol_11_x86/boot module \
    /I86PC.Solaris_11.8_

options

  • dhcp – Specifies to use a DHCP server to obtain network installation information that is needed to boot the system. This option is not needed for a JumpStart installation. If you do not specify to use a DHCP server by typing dhcp, the system uses the /etc/bootparams file or the naming service bootparams database. For example, you would not specify dhcp if you wanted keep a static IP address. For example:


    kernel /I86pc.Solaris_11.8/multiboot install \
    dhcp -B install_media=192.168.2.1:/export/Solaris_11.8/ \
    boot module /I86PC.Solaris_11.8/x86.new
  • The options nowin and text do not apply to a JumpStart installation. These options are useful with an interactive installation. For more information, see To Install or Upgrade With the Solaris Installation Program With GRUB in Solaris 10 5/09 Installation Guide: Basic Installations.