When you create a profile server, you must make sure systems can access it during a custom JumpStart installation. There are two ways to do this:
Every time you add a system for network installation, you have to use the -c option of the add_install_client command or specify the profile server in Host Manager.
or
Enable all systems to access the profile server by using a wildcard in the /etc/bootparams file.
To save you time when adding systems for network installations, use the following procedure to enable all systems to access the profile server. Otherwise, see "Creating the rules File".
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 in Step 2.
This procedure is not necessary if you are using a diskette for the JumpStart directory.
On the install server or boot server, log in as root.
Edit the /etc/bootparams file. Add the following entry.
* install_config=server:jumpstart_dir_path |
* |
Is a wildcard character specifying all systems. |
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 would enable all systems to access the /jumpstart directory on the profile server named sherlock:
* install_config=sherlock:/jumpstart |
Using this procedure may produce the following error message when an install client is booted: WARNING: getfile: RPC failed: error 5: (RPC Timed out). See "Booting a System Over the Network" for more details on this error message.
All systems can now access the profile server. You no longer need to specify the profile server in Host Manager or use the -c option of the add_install_client command when adding systems for network installations. To continue, go to "Creating the rules File".