Solaris 10 10/08 Installation Guide: Custom JumpStart and Advanced Installations

Allowing All Systems Access to the Profile Server

When you create a profile server, you must ensure that systems can access the JumpStart directory on the profile server during a custom JumpStart installation. Use one of the following ways to ensure access.

Command or File 

Providing Access 

Instructions 

add_install_client command

Each time that you add a system for network installation, use the -c option with the add_install_client command to specify the profile server.


Note –

If you are not using NFS, then you must use another means to provide access.

  • For SPARC based systems, use the boot command

  • For x86 based systems, edit the GRUB menu


Specify the location of the JumpStart directory when you boot the system 

  • For SPARC based systems, use the boot command to boot the system. Specify the location of the JumpStart directory on the profile server when you boot the system. You must compress the custom JumpStart configuration files into one file. Then, save the compressed configuration file on an HTTP or HTTPS server.

  • For x86 based systems, specify the location of the JumpStart directory on the profile server when you boot the system by editing the boot entry on the GRUB menu. You must compress the custom JumpStart configuration files into one file. Then, save the compressed configuration file on an HTTP or HTTPS server.

    When you edit the GRUB menu entry, specify the location of the compressed file.

/etc/bootparams file

Add a wildcard in the /etc/bootparams file.

To Allow All Systems Access to the Profile Server

ProcedureTo Allow All Systems Access to the Profile Server

Use the following procedure only if you store network installation information in the following places:

If you use the following procedure, the systems must be of the same type, such as all SPARC systems.

Do not use this procedure under the following conditions:

If you have the above conditions, use the SPARC boot command or use the x86 GRUB menu.


Note –

You also can store network installation information on a DHCP server.


  1. On the installation or boot server, log in as superuser.

  2. Use a text editor to open /etc/bootparams.

  3. Add this entry.

    * install_config=server:jumpstart_dir_path
    
    *

    A wildcard character that specifies that all systems have access

    server

    The host name of the profile server where the JumpStart directory is located

    jumpstart_dir_path

    The absolute path of the JumpStart directory

    For example, the following entry enables all systems to access the /jumpstart directory on the profile server that is named sherlock:

    * install_config=sherlock:/jumpstart

    Caution – Caution –

    Use of this procedure might produce the following error message when an installation client is booted:

    WARNING: getfile: RPC failed: error 5: (RPC Timed out).

    Booting From the Network, Error Messages contains details about this error message.


    All systems can now access the profile server.