Enabling All Systems to Access 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 enable access.

• Use the 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 edit the boot entry on the GRUB menu to enable all systems to access the profile server.

  ---

  For instructions, see How to Add Systems to Be Installed From the Network With add_install_client.

• Edit the boot entry in the GRUB menu.

  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 NFS server, an HTTP server, or on media that the system can access locally. Note that when you edit the GRUB menu entry, you must specify the location of the compressed file.

  For instructions, see To Create a Compressed Configuration File in Solaris 10 Installation Guide: Custom JumpStart and Advanced Installations and Performing a Custom JumpStart Installation by Editing the GRUB boot Command in Solaris 10 Installation Guide: Custom JumpStart and Advanced Installations.

• Add a wildcard in the /etc/bootparams file.

  For instructions, see How to Enable All Systems to Access the Profile Server.

How to Enable All Systems to Access the Profile Server

Use this procedure only if you store network installation information in the /etc/bootparams file.

To use this procedure, all systems must be of the same type, such as all x86 based systems.

Do not use this procedure under the following conditions:

• If you save the JumpStart directory on a diskette.

• If you specify the location of the profile server when you boot the system.

• If you have systems of different architectures, you must specify the location of the profile server when you boot the system.

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

Use the add_install_client command and the -d option to instruct the custom JumpStart program to use the DHCP server with PXE. In this Solaris release, you can also add the dhcp option by editing the boot entry in the GRUB menu when you boot the system.

For step-by-step instructions on editing the GRUB menu, see Performing a GRUB Based Installation From the Network in Solaris 10 Installation Guide: Custom JumpStart and Advanced Installations and How to Modify the Solaris Boot Behavior by Editing the GRUB Menu in System Administration Guide: Basic Administration.

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

2. Using a text editor, open the /etc/bootparams file.

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 allows all systems to access the /jumpstart directory on the profile server that is named sherlock:

   * install_config=sherlock:/jumpstart

   All systems can now access the profile server.

   ---

   Note –

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

   See Booting From the Network, Error Messages in Solaris 10 Installation Guide: Custom JumpStart and Advanced Installations for details about this error message.

   ---

   All systems can now access the profile server.