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:

• /etc/bootparams file – Use a wildcard in the /etc/bootparams file. For detailed instructions, refer to To Allow All Systems Access to the Profile Server.

• add_install_client command – Each time 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.

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

To Allow All Systems Access to the Profile Server

This procedure is not necessary if you intend to use a diskette with the JumpStart directory on it or if you specify the location of the profile server when you boot the system.

This 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 the name service bootparams database, you must update the bootparams database with the entry 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 6 in SPARC: To Perform a Custom JumpStart Installation and for IA systems refer to Step 8 in x86: To Perform a Custom JumpStart Installation.

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

2. Using a text editor of your choice, open /etc/bootparams.

3. Add this entry:

   * install_config=server:jumpstart_dir_path

   where:

   *	Is a wildcard character that specifies that all systems have access.
   server	Is the host name of the profile server where the JumpStart directory is located.
   jumpstart_dir_path	Is the absolute path of the JumpStart directory.

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

   * install_config=sherlock:/jumpstart

   ---

   Caution –

   Using this procedure might produce the following error message when an install client is booted:

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

   Booting a System Over the Network contains details about this error message.

   ---

   All systems can now access the profile server. You no longer need to use the -c option with the add_install_client command when adding systems for network installations.