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.

To Allow All Systems Access to the Profile Server

Use the following procedure only if you store network installation information in the following places:

• In the /etc/bootparams file.

• In the naming service bootparams database. To update the bootparams database, add the entry that is shown in Step 3.

If you use the following procedure, the systems must be of the same type, such as all SPARC 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

If you have the above conditions, use the SPARC boot command or use the x86 GRUB menu.

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

• For SPARC based systems, you use the add_install_client command and the -d option to specify that the custom JumpStart program use the DHCP server. Or you use the boot command with the dhcp option to specify that the custom JumpStart program use the DHCP server. For instructions about using this option, see SPARC: Command Reference for the boot Command.

• For x86 based systems, you use dhcp in one of the following ways:

  • If you use an install server, use the add_install_client command and the -d option to specify that the custom JumpStart program use the DHCP server with PXE.

  • You can edit the GRUB entry on the GRUB menu and add the dhcp option. For instructions about editing the GRUB entry, see x86: Performing a Custom JumpStart Installation by Editing the GRUB Boot Command

1. On the installation 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 enables 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 installation 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.