Adding Systems to Be Installed From the Network With a CD Image

After you create an install server and, if necessary, a boot server, you must set up each system that you want to install from the network. Each system that you want to install needs to find the following:

• An install server

• A boot server if it is required

• The sysidcfg file if you use a sysidcfg file to preconfigure system information

• A name server if you use a name service to preconfigure system information

• The profile in the JumpStart directory on the profile server if you are using the custom JumpStart installation method

Use the following add_install_client procedure for setting up install servers and clients. Also, see the example procedures for the following:

• If you are using DHCP to set installation parameters, see Example 12–6.

• If your install server and client are on the same subnet, see Example 12–7.

• If your install server and your client are not on the same subnet and you are not using DHCP, see Example 12–8.

For more options to use with this command, see the man page, add_install_client(1M).

To Add Systems to Be Installed From the Network With add_install_client From a Server

If you have a boot server, make sure you have shared the install server installation image. See the procedure “To Create an Install Server,” Step 6.

1. On the install server or boot server, become superuser.

2. If you use the NIS, NIS+, DNS, or LDAP name service, verify that the following information about the system to be installed has been added to the name service:

   • Host name

   • IP address

   • Ethernet address

   For more information on name services, see System Administration Guide: Naming and Directory Services (DNS, NIS, and LDAP).

3. Change to the Tools directory on the Solaris 9 CD image on the install server:

   # cd /install_dir_path/Solaris_9/Tools

   install_dir_path

   Specifies the path to the Tools directory

4. Set up the client system to be installed from the network.

   # ./add_install_client [[-d]] [[-s install_server:install_dir_path]] \ [[-c jumpstart_server:jumpstart_dir_path]] [[-p server:path]] \ [[-t boot_image_path]] client_name platform_group

   -d	Specifies that the client is to use DHCP to obtain the network install parameters.  For IA clients, use this option to boot the systems from the network by using PXE network boot.
   -s install_server:install_dir_path	Specifies the name and path to the install server.   install_server is the host name of the install server install_dir_path is the absolute path to the Solaris 9 CD image
   -c jumpstart_server:jumpstart_dir_path	Specifies a JumpStart directory for custom JumpStart installations. jumpstart_server is the host name of the server on which the JumpStart directory is located. jumpstart_dir_path is the absolute path to the JumpStart directory.
   -p sysid_server:path	Specifies the path to the sysidcfg file for preconfiguring system information. sysid_server is either a valid host name or an IP address for the server that contains the file. path is the absolute path to the directory containing the sysidcfg file.
   -t boot_image_path	Specifies the path to an alternate boot image if you want to use a boot image other than the one in the Tools directory on the Solaris 9 net installation image, CD, or DVD.
   client_name	Is the name of the system to be installed from the network. This name is not the host name of the install server.
   platform_group	Is the platform group of the system to be installed. A detailed list of platform groups appears in Chapter 39, Platform Names and Groups (Reference).

Example 12-6 SPARC: Adding a SPARC Install Client on a SPARC Install Server When Using DHCP (CDs)

The following example illustrates how to add an install client when you are using DHCP to set installation parameters on the network. The install client is named basil, which is an Ultra^TM 5 system. The file system /export/home/s9cdsparc/Solaris_9/Tools contains the add_install_client command.

sparc_install_server# cd /export/home/s9cdsparc/Solaris_9/Tools
sparc_install_server# ./add_install_client -d basil sun4u

Example 12-7 Adding an Install Client That Is on the Same Subnet as Its Server (CDs)

The following example illustrates how to add an install client that is on the same subnet as the install server. The install client is named basil, which is an Ultra^TM 5 system. The file system /export/home/s9cdsparc/Solaris_9/Tools contains the add_install_client command.

install_server# cd /export/home/s9cdsparc/Solaris_9/Tools
install_server# ./add_install_client basil sun4u

Example 12-8 Adding an Install Client to a Boot Server (CDs)

The following example illustrates how to add an install client to a boot server. The install client is named rose, which is an Ultra^TM 5 system. Run the command on the boot server. The -s option is used to specify an install server that is named rosemary, which contains a Solaris 9 CD image in /export/home/s9cdsparc.

boot_server# cd /export/home/s9cdsparc/Solaris_9/Tools
boot_server# ./add_install_client -s rosemary:/export/home/s9cdsparc rose sun4u

Example 12-9 IA: Adding an IA Install Client On an IA Install Server When Using DHCP (CDs)

The following example illustrates how to add an IA install client to an install server when you are using DHCP to set installation parameters on the network. The -d option is used to specify that clients are to use the DHCP protocol for configuration. If you plan to use PXE network boot, you must use the DHCP protocol. The DHCP class name SUNW.i86pc indicates that this command applies to all Solaris IA network boot clients, not just a single client. The -s option is used to specify that the clients are to be installed from the install server that is named rosemary. This server contains a Solaris 9 Software 1 of 2 Intel Platform Edition CD image in /export/home/s9cdia:

install server# cd /export/boot/Solaris_9/Tools
install server# ./add_install_client -d -s rosemary:/export/home/s9cdia SUNW.\ 
i86pc i86pc