Enabling Access to the JumpStart Directory

The JumpStart directory must be added to the bootparams database for successful network installation. You should use the same procedure you chose to use to "Add Client Information for a Network Install". You can also directly edit the bootparams database on the install server.

The following procedure is not necessary if you are using a diskette for the JumpStart directory.

How to Enable Access to the JumpStart Directory

Follow the same procedure that you used to set up the network servers in Chapter 7, Preparing to Install Trusted Solaris Over a Network.

Method 1: Host Manager

1. As role admin, at label admin_low, launch the Host Manager using the same naming service you did for setting up network install, and select a workstation.

   See "Add Client Information Using the Host Manager" for a description of the Host Manager interface.

2. Enter jumpstart_dir_path as the Profile Server entry and click OK.

   For example, enter stork:/jumpstart.

3. Choose File > Save Changes.

   When you save the entry, the Host Manager places the information in the bootparams database.

4. Repeat for all hosts to be installed with custom JumpStart, then exit the Host Manager.

5. As role admin, at label admin_low, launch the Database Manager using the same naming service you did for setting up network install.

6. Load the bootparams database.

7. To fully automate custom JumpStart, add an ns entry before the initial entry. Leave a space between it and the next entry.

   ns=nis+_server:nisplus(netmask)

   For example,

   ns=grebe:nisplus(255.255.255.0)

Method 2: add_install_client Command

1. As root, at label admin_low, go to "Add Client Information with the add_install_client Command".

2. Use the -c option to the add_install_client command to add JumpStart details to the local bootparams database.

   # ./add_install_client -c [server:jumpstart_dir_path] [-e ethernet_address \
   host_name platform_group 
   

   In this command,

   -c

   Specifies a JumpStart directory for custom JumpStart installations. This option and its arguments are required for custom JumpStart.

   server:jumpstart_dir_path

   server is the host name of the server on which the JumpStart directory is located. jumpstart_dir_path is the absolute path of the JumpStart directory.

   For example, issuing the following command on an install/boot server modifies the local bootparams database to look for custom JumpStart information in the stork:/jumpstart directory.:

   # ./add_install_client -e 8:0:20:17:22:a4 \ -c stork:/jumpstart \ -s heron:/export/install/ts7_sparc willet sun4m

   The result: The client willet can be installed with custom JumpStart. Its Trusted Solaris 2.5.1 image will come from heron (as will its boot information), and its custom JumpStart installation profile will come from stork.

How to Check Access to the JumpStart Directory

If you want to check the bootparams database file directly:

1. On the install server, as role admin at label admin_low, edit the bootparams database.

   For details, see "To Open and Modify a Solstice_Apps Database".

2. Scroll through a host's entry to locate the keyword=value pairs: install_server=server:install_dir_path install_config=server:jumpstart_dir_path

   For example, the following keyword=value pair in a workstation's bootparams entry would enable it to access the /jumpstart directory on the server named stork:

   install_config=stork:/jumpstart

   The following keyword=value pair in the same workstation's bootparams entry would enable it to access the Trusted Solaris installation image on heron. Together, these keyword=value pairs enable custom JumpStart:

   install_server=heron:/export/install/ts7_sparc

   All workstations can now access the JumpStart directory.

3. Continue with "Creating a Profile".