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 Step 6.
On the install server or boot server, become superuser.
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).
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
Set up a system to be installed from the network. the system can be an install server or boot server.
# ./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
Specifies that the client is to use DHCP to obtain the network install parameters.
-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
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.
Is the name of the system to be installed from the network. This name is not the host name of the install server.
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-3 Adding an Install Client on an 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 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 -d basil sun4u |
Example 12-4 Adding an Install Client That Is On the Same Subnet as Its Server to the Network (CDs)
The following example illustrates how to add an install client that is on the same subnet as the install server. The install server is named basil, which is an Ultra 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-5 Adding an Install Client on a Network With Only 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 5 system. Run the command on the boot server. The -s option is used to specify install server that is named basil, which contains a Solaris 9CD image in /export/home/s9cdsparc.
boot_server# cd /export/home/s9cdsparc/Solaris_9/Tools boot_server# ./add_install_client -s basil:/export/home/s9cdsparc rose sun4u |