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.
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 |
Specifies the path to the Tools directory
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 sysid_server:path]] \ [[-t boot_image_path]] [[-b "network_boot_variable=value"]] \ [[-e ethernet_address]] client_name platform_group |
Specifies that the client is to use DHCP to obtain the network install parameters. If you use the -d only, the add_install_client command sets up the installation information for client systems of the same class, for example, all SPARC client machines. To set up the installation information for a specific client, use the -d with the -e option.
For x86 clients, use this option to boot the systems from the network by using PXE network boot.
For more information about class-specific installations by using DHCP, see Creating DHCP Options and Macros for Solaris Installation Parameters.
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.
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.
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.
x86 based systems only: Enables you to set the value of a boot property variable that you want to use to boot the client from the network. The -b must be used with the -e option.
See the eeprom(1M) man page for descriptions of boot properties.
Specifies the ethernet address of the client that you want to install. This option enables you to set up the installation information to use for a specific client.
For more information about client-specific installations by using DHCP, see Creating DHCP Options and Macros for Solaris Installation Parameters.
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 Appendix C, Platform Names and Groups (Reference).
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/cdsparc/Solaris_9/Tools contains the add_install_client command.
For more information on how to use DHCP to set installation parameters for network installations, see “Supporting Solaris Network Installation with the DHCP Service (Task Map)” in System Administration Guide: IP Services.
sparc_install_server# cd /export/home/cdsparc/Solaris_9/Tools sparc_install_server# ./add_install_client -d basil sun4u |
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 5 system. The file system /export/home/cdsparc/Solaris_9/Tools contains the add_install_client command.
install_server# cd /export/home/cdsparc/Solaris_9/Tools install_server# ./add_install_client basil sun4u |
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 an install server that is named rosemary, which contains a Solaris 9 CD image in /export/home/cdsparc.
boot_server# cd /export/home/cdsparc/Solaris_9/Tools boot_server# ./add_install_client -s rosemary:/export/home/cdsparc rose sun4u |
The following example illustrates how to add an x86 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 x86 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 Software 1 of 2 x86 Platform Edition CD image in /export/home/cdx86.
For more information on how to use DHCP to set installation parameters for network installations, see “Supporting Solaris Network Installation with the DHCP Service (Task Map)” in System Administration Guide: IP Services.
install server# cd /export/boot/Solaris_9/Tools install server# ./add_install_client -d -s rosemary:/export/home/cdx86 SUNW.\ i86pc i86pc |
The following example illustrates how to add an x86 install client to an install server and specify a serial console to use during the installation. This example sets up the install client in the following manner.
The -d option indicates that the client is set up to use DHCP to set installation parameters.
The -e option indicates that this installation will occur only on the client with the ethernet address 00:07:e9:04:4a:bf.
The first and second uses of the -b option instruct the installation program to use the serial port ttya as an input and an output device.
install server# cd /export/boot/Solaris_9/Tools install server# ./add_install_client -d -e "00:07:e9:04:4a:bf" \ -b "input-device=ttya" -b "output-device=ttya" i86pc |
For a complete description of the boot property variables and values you can use with the -b option, see the eeprom(1M) man page.
The following example illustrates how to add an x86 install client to an install server and specify a boot device to use during the installation. If you specify the boot device when you set up the install client, you are not prompted for this information by the Device Configuration Assistant during the installation.
This example sets up the install client in the following manner.
The -d option indicates that the client is set up to use DHCP to set installation parameters.
The -e option indicates that this installation will occur only on the client with the ethernet address 00:07:e9:04:4a:bf.
The first and second uses of the -b option instruct the installation program to use the serial port ttya as an input and an output device.
The third use of the -b option instructs the installation program to use a specific boot device during the installation.
The value of the boot device path varies based on your hardware.
The i86pc platform name indicates that the client is an x86-based system.
install server# cd /export/boot/Solaris_9/Tools install server# ./add_install_client -d -e "00:07:e9:04:4a:bf" \ -b "input-device=ttya" -b "output-device=ttya" \ -b "bootpath=/pci@0,0/pci108e,16a8@8" i86pc |
For a complete description of the boot property variables and values you can use with the -b option, see the eeprom(1M) man page.