Allowing All Systems Access to the Profile Server

When you create a profile server, you must ensure that systems can access it during a custom JumpStart installation. Use one of these ways to ensure access:

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

• Every time you add a system for network installation, use the -c option with the add_install_client command.

To save time when adding systems for network installations, use the following procedure to allow all systems access to the profile server. Otherwise, see "Creating the rules 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.

This procedure is valid only if you are using the /etc/bootparams file to store network installation information. If you are using the NIS or NIS+ bootparams database for network installation information, you need to update the bootparams database with the entry shown in Step 3.

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.