Description

These commands are located on slice 0 of the Solaris Software and
Solaris Installer CDs or DVDs. (The terms “CD” and “DVD” are hereafter
referred to as “installation media”.) If the Solaris installation media has been
copied to a local disk, media_mnt_pt is the path to the copied Solaris
installation media. They can be used for a variety of installation tasks.

The XX in Solaris_XX is the version number of the Solaris release
being used.

There are three versions of the add_install_client command. See SYNOPSIS.

Use the following version of the add_install_client command to add clients for
network installation (these commands update the bootparams(4) file). The add_install_client command must be
run from the install server's Solaris installation image (a mounted Solaris installation
media or a Solaris installation media copied to disk) or the boot
server's boot directory (if a boot server is required). The Solaris installation image
or the boot directory must be the same Solaris release that you
want installed on the client.

Use the following version of the add_install_client command to add support for
instances of a platform within a platform group to the install server.
This group is booted and configured using DHCP. The script performs the
necessary configuration steps on the server, and prints the data that the user
needs to add to the DHCP server for the group.

Use the following version of the add_install_client command to add a single
client to the install server. This client is booted and configured using
DHCP. The script performs the necessary configuration steps on the server, and
prints the data that the user needs to add to the DHCP server
for the client. The -f flag used above needs to be added
to the existing usage as well. -f allows the user to specify
a boot file name to be used for a given client.

Always use the -d option when registering x86 Architecture Pre-boot eXecution Environment
(PXE) clients. These clients use DHCP for their configuration.

Use add_to_install_server to merge other Solaris installation media with an existing image
on a Net Install Server. Each installation media that can be merged
(each OS CD or DVD, and the Language CD or DVD) has
its own add_to_install_server script. Do not use add_to_install_server scripts with installation media other
than the ones with which they were delivered.

Use check to validate the rules in a rules file (this is
only necessary if a custom JumpStart installation is being set up).

Use setup_install_server to copy the Solaris installation media to a disk (to
set up an install server), to build a WANboot miniroot image (to
set up a WANboot install server), or to copy just the boot
software of the Solaris installation media to a disk (to set up
a boot server). An install server is required to install clients over the
network. A boot server is also required for network installations if the
install server and clients to be installed are on different subnets (the
boot server must be located on the client's subnet).

Options

The add_install_client supports the following options:

-bproperty=value

Set a property value in the client-specific menu.lst file located on the boot server's TFTP directory, /tftpboot by default. Use this option to set boot properties that are specific to this client.

Use this option only with an x86 client an only in conjunction with the -d and -e options.

-cserver_name:path

This option is required only to specify a JumpStart directory for a custom JumpStart installation. server_name is the host name of the server with a JumpStart directory. path is the absolute path to the JumpStart directory.

-d

Specify as a DHCP client.

-eEthernet_address

Specify the Ethernet address of the system to be installed.

-f

Specify the boot_file_name of the client to be installed.

-iIP_address

Specify the IP address of the client to be installed.

-n [server]:name_service[(netmask)]

This option specifies which name service should be used during system configuration. This sets the ns keyword in the bootparams(4) file.

name_service

Valid entries are nis, nisplus, and none.

netmask

A series of four numbers separated by periods, specifying which portion of an IP address is the network part, and which is the host part.

server

The name of the server or IP address of the specified name service. If the server specified is on a different subnet, then the netmask may be needed to enable the client to contact the server.

-pserver_name: path

This option is used to specify the NFS or ZFS shared directory that contains the user-defined sysidcfg file. When a client is booted, it attempts to read a file specifically named sysidcfg in this directory to obtain answers to the system and network identification questions. server_name is either a valid host name or IP address. path is the absolute pathname of the directory on the file server that contains the sysidcfg file.

-sserver_name:path

This option is required only when using add_install_client from a boot server. Specify the name of the server and the absolute path of the Solaris installation image that is used for this installation. path is either the path to a mounted Solaris installation media or a path to a directory with a copy of the Solaris installation media.

-t [server:]path

-tserver:[path]

path

Allows you to specify an alternate miniroot.

server

The name or IP address of the boot server. This can be used on boot servers with multiple network interfaces to specify the particular IP address from which clients should be booted.

The add_to_install_server command supports the following options:

-p

Specifies the location of the installation media (containing the supplemental products) to be copied.

-s

Allows users to select from a list only the products needing installation.

The check command supports the following options:

-pinstall_dir_path

Validates the rules file by using the check script from a specified Solaris installation image, instead of the check script from the system you are using. install_dir_path is the path to a Solaris installation image on a local disk or a mounted Solaris installation media.

Use this option to run the most recent version of check if your system is running a previous version of Solaris.

-rrulesfile

Specifies a rules file other than the one named rules. Using this option, the validity of a rule can be tested before integrating it into the rules file. check reports whether or not the rule is valid, but it does not create the rules.ok file necessary for a custom JumpStart installation.

The following add_install_client commands add clients for network installation from a mounted
Solaris installation media on an install server. The -c option specifies a
server and path to a JumpStart directory that has a rules file
and a profile file for performing a custom JumpStart installation. Also, the Solaris
installation media has been copied to the /export/install directory:

Example 12 x86: Specifying a Serial Console to Use During a Network Installation (from Installation Media)

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 occurs 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.

For a complete description of the boot property variables and values you
can use with the -b option, see eeprom(1M).

Example 13 Specifying a Boot Device to Use During a Network Installation (from Installation Media)

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 occurs 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.