Set up the marketing systems for installation.

Systems cannot boot from an install server on a different subnet, so the administrator sets up a boot server on the marketing group's subnet. On a server on the marketing subnet, the administrator inserts a Trusted Solaris CD. The administrator in the role root at the label ADMIN_LOW then uses the setup_install_server(1M) command to copy the boot software from the CD to the marketing server.

# cd /cdrom/cdrom0/s0
# ./setup_install_server -b /marketing/boot-dir sun4c

In the setup_install_server command,

-b

Specifies that setup_install_server will copy the boot information from the Trusted Solaris CD to the directory named /marketing/boot-dir.

sun4c

Specifies the platform of the systems that will use this boot server. (This is the proper platform name for Sun IPX systems.)

Next, an administrator in the role root sets up the marketing systems to boot from the local boot server and install Trusted Solaris from the remote install server. At the label admin_low, the administrator uses the add_install_client command on the marketing group's boot server:

# cd /marketing/boot-dir
# ./add_install_client -s server_1:/export/install \
-c server_1:/jumpstart host_mkt1 sun4c
# ./add_install_client -s server_1:/export/install \
-c server_1:/jumpstart host_mkt2 sun4c	...

In the add_install_client command,

-s

Specifies the install server (server_1) and the path to the Trusted Solaris software (/export/install).

-c

Specifies the server (server_1) and path (/jumpstart) to the JumpStart directory.

host_mkt1

Is the name of a system in the marketing group.

host_mkt2

Is the name of another system in the marketing group.

sun4c

Specifies the platform of the systems that will use this boot server. (This is the proper platform name for Sun IPX systems.)