To Allow 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:

• add_install_client command – Each time that you add a system for network installation, use the -c option with the add_install_client command. For detailed instructions, refer to Adding Systems to Be Installed From the Network With a CD Image.

• boot command – 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 NFS server, an HTTP server, or on media that the system can access locally. For detailed instructions, refer to Creating a Compressed Configuration File.

  When you boot the system to initiate the custom JumpStart installation, specify the location of the compressed file. For detailed instructions for SPARC systems, refer to Step 5 in SPARC: To Perform an Installation or Upgrade With the Custom JumpStart Program. For x86 systems, refer to Step 8 in x86: To Perform an Installation or Upgrade With the Custom JumpStart Program.

• /etc/bootparams file – Use a wildcard in the /etc/bootparams file. Use the following steps to add a wildcard in the etc/bootparams file.

The following procedure is not necessary if you save the JumpStart directory on a diskette or if you specify the location of the profile server when you boot the system.

The following procedure is valid only if you store network installation information in the /etc/bootparams file. You can also store network installation information in one of the following places:

• Name service database – If you store network installation information in the name service bootparams database, you must update the bootparams database with the entry that is shown in Step 3.

• DHCP server – If you store network installation information on a DHCP server, use the boot command to specify that the custom JumpStart program use the DHCP server. For detailed instructions for SPARC systems, refer to Step 5 in SPARC: To Perform an Installation or Upgrade With the Custom JumpStart Program. For x86 systems, refer to Step 8 in x86: To Perform an Installation or Upgrade With the Custom JumpStart Program.

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

   * install_config=sherlock:/jumpstart

   ---

   Caution –

   Use of this procedure might produce the following error message when an install 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.