Manucomp Systems
Hours of Operation

Monday to Friday:
9am - 6pm EST

Saturday & Sunday:

If you would like additional information please contact us toll-free at :


Can't find the product you are looking for?
Request a quote.
Client Setup
Back to Sun Tips

Having copied the Solaris software to the local disk and shared the JumpStart software directory, you are now prepared to setup your first client. Determine the hostname, IP address, and Ethernet address of the client. The hostname and IP address will depend on your particular environment; the Ethernet address can be determined by running the "banner" command on the ok prompt.

Add the hostname and IP address of the new client to the /etc/hosts file (to be precise, /etc/inet/hosts) on the server. Add the hostname and Ethernet address of the server to the /etc/ethers file.

Here is an example entry from /etc/hosts: myclient

And here is an example entry from /etc/ethers:

8:0:20:5:b:be myclient

In order to run JumpStart successfully without user intervention, the client will require more information than simply hostname, IP address, and Ethernet address. For example, you must specify the timezone, the language, the security policy, etc. This information can be furnished to the client either locally with the sysidcfg file or with NIS. The preferred solution is normally NIS, which we will discuss later, but for the moment we will show how to use the sysidcfg file.

The sysidcfg file should be located under the /jumpstart directory (or whatever directory you have decided to use for JumpStart). The minimal information that must be provided is system locale, timezone, name service, network interface, and security policy. If you neglect to provide all of the required information, you will be prompted to enter it manually when you run the JumpStart, which is not what we want.

The following represents an example sysidcfg file:






network_interface=le0 {hostname=myhost \ ip_address= \ netmask= protocol_ipv6=no}


Of course, replace the values here with values appropriate for your environment. For more information on the variables and values that you can use, see the Advanced Installation Guide.

The next step is to update the /etc/bootparams file with the information that the client will require to start the installation process successfully. Unless you happen to be a JumpStart guru, you will probably want to use the "add_install_client" command to that end. Assuming you have used the convention shown above, the "add_install_client" command will be located under /jumpstart/OS/Solaris_8.0_10-00/Solaris_8/Tools. The "add_install_client" command has numerous options - see the manpage for more information. As stated above, we have assumed that you have selected one server to be the install server and boot server.

To setup your client, use the command

"add_install_client -c : -p : \ ."

Below is an example:

# ./add_install_client -c myserver:/jumpstart -p myserver:/jumpstart myclient sun4m

The -c option provides the hostname of the install server and absolute pathname to the JumpStart directory. The -p option provides the hostname of the install server and the pathname to the directory where the sysidcfg file is located, presumably also the JumpStart directory. Finally, the command furnishes the hostname and platform of the client. Note that with Solaris 2.8, Sun has dropped support for the sun4c platform, so those of you with SPARCstation IPX boxes will simply have to content yourselves with Solaris 2.7, or better yet Solaris 2.6.

If you have decided to use a separate boot server, then you must run the "add_install_client" command on the boot server and add the "-s :" option to indicate the hostname of the install server.

The add_install_client script will enable tftp and start rarpd, both services required by the JumpStart client, and update /etc/bootparams. You may now proceed to setup your desired client configuration.