Solaris Express Installation Guide: Network-Based Installations

ProcedureSPARC: To Create a SPARC Install Server With SPARC or x86 DVD Media


Note –

This procedure assumes that the system is running the Volume Manager. If you are not using the Volume Manager to manage media, refer to System Administration Guide: Devices and File Systems.


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

    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 SPARC system's drive.

  3. Create a directory to contain the DVD image.


    # mkdir -p install_dir_path
    
  4. Change to the Tools directory on the mounted disc.

    • For SPARC DVD media, type:


      # cd /cdrom/cdrom0/s0/Solaris_11/Tools
      
    • For x86 DVD media, type:


      # cd /cdrom/cdrom0/Solaris_11/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.

        Use either the share command or the new sharemgr utility to complete the verification.


        # share | grep install_dir_path
        

        # # sharemgr show -v | grep install_dir_path
        

        Note –

        Starting with the 5/07 Developer release, the sharemgr utility introduces the concept of share groups. See sharemgr Command in System Administration Guide: Network Services.


        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 by using either the share command or the sharemgr utility.

        • 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
          
        • Using the sharemgr utility, enter the following commands:

          # sharemgr add-share -d “install server directory” -s install_dir_path default

          # sharemgr set -P nfs -S sys -p ro="*" -s install_dir_path default

          # sharemgr set -P nfs -p anon=0 -s install_dir_path default

      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. If you are using the share command instead of the sharemgr utility, 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 SPARC based installation images, use the patchadd-c command to patch the files that are located in the miniroot.


      # patchadd -C install_dir_path path-to-patch/patch-id
      
      install_dir_path

      Specifies the path to the network installation miniroot.

      path-to-patch

      Specifies the path to the patch that you want to add, for example, /var/sadm/spool.

      patch-id

      Specifies the patch ID that you want to apply.


      Caution – Caution –

      Don't use the patchadd -C command unless you have read the Patch README instructions or have contacted your local Sun support office.


    • For x86 based installation images, follow these steps to patch an x86 network installation miniroot.


      Note –

      These steps assume that you have a system on your network that is running the current Solaris release for x86 platforms, and that system is accessible over the network.


      1. On a system that is running the current Solaris release for x86 platforms, log in as superuser or assume an equivalent role.

      2. Change to the Tools directory of the installation image you created in Step 5.


        # cd install-server-path/install-dir-path/Solaris_11/Tools
        
        install-server-path

        Specifies the path to the install server system on your network, for example, /net/installserver-1.

      3. Create a new installation image, and place that image on the system that is running the current Solaris release for x86 platforms.


        # ./setup_install_server remote_install_dir_path
        
        remote_install_dir_path

        Specifies the path on the current Solaris release for x86 systems in which to create the new installation image.

        This command creates a new installation image on the current Solaris release for x86 systems. In order to patch this image, you must temporarily place this image on a system that is running the current Solaris release for x86 systems.

      4. On the current Solaris release for x86 systems, unpack the network installation boot archive.


        # /boot/solaris/bin/root_archive unpackmedia remote_install_dir_path \
          destination_dir
        
        remote_install_dir_path

        Specifies the path to the x86 network installation image on the current Solaris release for x86 systems.

        destination_dir

        Specifies the path to the directory to contain the unpacked boot archive.

      5. On the current Solaris release for x86 systems, patch the unpacked boot archive.


        # patchadd -C destination_dir path-to-patch/patch-id
        
        path-to-patch

        Specifies the path to the patch that you want to add, for example, /var/sadm/spool.

        patch-id

        Specifies the patch ID that you want to apply.

        You can specify multiple patches with the patchadd -M option. For more information, see patchadd(1M).


        Caution – Caution –

        Don't use the patchadd -C command unless you have read the Patch README instructions or have contacted your local Sun support office.


      6. On the current Solaris release for x86 systems, pack the x86 boot archive.


        # /boot/solaris/bin/root_archive packmedia destination_dir \
          remote_install_dir_path
        
      7. Copy the patched miniroot to the installation image on the install server.


        # cp remote_install_dir_path/boot/x86.miniroot \
          install-server-path/install_dir_path/boot/x86.miniroot
        
  10. Decide if you need to create a boot server.


Example 5–1 SPARC: Creating a SPARC Install Server With a SPARC DVD

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


# mkdir -p /export/home/dvdsparc
# cd /cdrom/cdrom0/s0/Solaris_11/Tools
# ./setup_install_server /export/home/dvdsparc

If you need a separate boot server, type these commands:

Make the install server available to the boot server by using either the share command or the sharemgr utility.

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

If you are using sharemgr utility, omit shareall.


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


Example 5–2 x86: Creating a SPARC Install Server With an x86 DVD

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


# mkdir -p /export/home/dvdx86
# cd /cdrom/cdrom0/Solaris_11/Tools
# ./setup_install_server /export/home/dvdx86

Make the install server available to the boot server by using either the share command or the sharemgr utility.

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

If you are using sharemgr utility, omit shareall.


# 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).