Creating an Install Server With DVD Media

The install server contains the installation image needed to install systems from the network. You must create an install server to install the Solaris software on a system from the network. You do not always need to set up a boot server.

• If you are using DHCP to set installation parameters or your install server and client are on the same subnet, you do not need a boot server.

• If your install server and your client are not on the same subnet and you are not using DHCP, you must create separate boot servers for each subnet. You could create an install server for each subnet. However, install servers require more disk space.

To Create an Install Server With SPARC or x86 DVD Media

1. On the system that is to become the install server, become superuser or assume an equivalent role.

   ---

   Note - Roles contain authorizations and privileged commands. For more information about roles, see Configuring RBAC (Task Map) in System Administration Guide: Security Services.

   ---

   The system must include a DVD-ROM drive and be part of the site's network and naming service. If you use a naming service, the system must already be in a service, such as NIS, NIS+, DNS, or LDAP. If you do not use a naming service, you must distribute information about this system by following your site's policies.

2. Insert the Solaris DVD in the system's drive.
3. Create a directory to contain the DVD image.

   # mkdir -p install_dir_path

   install_dir_path specifies the directory where the DVD image is to be copied.

4. Change to the Tools directory on the mounted disc.

   # cd /cdrom/cdrom0/Solaris_10/Tools

5. Copy the DVD image in the drive to the install server's hard disk.

   # ./setup_install_server install_dir_path

   install_dir_path

   Specifies the directory where the DVD image is to be copied

   ---

   Note - The setup_install_server command indicates whether you have enough disk space available for the Solaris Software disc images. To determine available disk space, use the df -kl command.

   ---

6. Decide if you need to make the install server available for mounting.
   • If the install server is on the same subnet as the system to be installed or you are using DHCP, you do not need to create a boot server. Proceed to Step 7.
   • If the install server is not on the same subnet as the system to be installed and you are not using DHCP, complete the following steps.
     1. Verify that the path to the install server's image is shared appropriately.

        # share | grep install_dir_path

        install_dir_path

        Specifies the path to the installation image where the DVD image was copied

        • If the path to the install server's directory is displayed and anon=0 is displayed in the options, proceed to Step 7.
        • If the path to the install server's directory is not displayed or you do not have anon=0 in the options, continue.
     2. Make the install server available to the boot server.

        Using the share command, add this entry to the /etc/dfs/dfstab file.

        share -F nfs -o ro,anon=0 -d "install server directory" install_dir_path

     3. Verify that the nfsd daemon is running.
        • If the install server is running the current Solaris release, or compatible version, type the following command.

          # svcs -l svc:/network/nfs/server:default

          If the nfsd daemon is online, continue to Step d. If the nfsd daemon is not online, start it.

          # svcadm enable svc:/network/nfs/server

        • If the install server is running the Solaris 9 OS, or compatible version, type the following command.

          # ps -ef | grep nfsd

          If the nfsd daemon is running, continue to Step d. If the nfsd daemon is not running, start it.

          # /etc/init.d/nfs.server start

     4. Share the install server.

        # shareall

7. Change directories to root (/).

   # cd /

8. Eject the Solaris DVD.
9. (Optional) Patch the files that are located in the miniroot on the net install image that was created by setup_install_server.

   Patching a file might be necessary if a boot image has problems. For step-by-step procedures, see Chapter 7, Patching the Miniroot Image (Tasks).

10. Decide if you need to create a boot server.
    • If you are using DHCP or the install server is on the same subnet as the system to be installed, you do not need to create a boot server. Proceed to Adding Systems to Be Installed From the Network With a DVD Image.
    • If you are not using DHCP and the install server and the client are on a different subnet, you must create a boot server. Proceed to Creating a Boot Server on a Subnet With a DVD Image.

Example 5-1 SPARC: Creating an Install Server With a DVD

The following example illustrates how to create an install server by copying the Solaris DVD to the install server's /export/home/dvd directory. This example assumes that the install server is running the current Solaris release.

# mkdir -p /export/home/dvd
# cd /cdrom/cdrom0/Solaris_10/Tools
# ./setup_install_server /export/home/dvd

If you need a separate boot server, make the install server available to the boot server.

Using the share command, add this entry to the /etc/dfs/dfstab file.

share -F nfs -o ro,anon=0 -d "install server directory" /export/home/dvdsparc

Check if the nfsd daemon is online. If the nfsd daemon is not online, start it and share it.

# svcs -l svc:/network/nfs/server:default
# svcadm enable svc:/network/nfs/server
# shareall 
# cd /

Continuing the Installation

After you set up the install server, you must add the client as an installation client. For information about how to add client systems to install over the network, see To Add Systems to Be Installed From the Network With add_install_client (DVD).

If you are not using DHCP, and your client system is on a different subnet than your install server, you must create a boot server. For more information, see Creating a Boot Server on a Subnet With a DVD Image.

See Also

For additional information about the setup_install_server and the add_to_install_server commands, see install_scripts(1M).