System Administration Guide: Basic Administration

Procedurex86: How to Prepare for Adding Diskless Clients in a GRUB Based Boot Environment

Use this procedure to prepare for adding a diskless client. This procedure includes general information for x86 based systems.

When you use the smosservice add command to add OS services, you must specify the platform, media path, and cluster (or software group) of each diskless client platform that you want to support.

Before You Begin

Ensure that the system that is intended to be the OS service is running a supported release. Also, verify that the OS server release and diskless client release combination is supported. For more information, see OS Server and Diskless Client Support Information.

  1. Identify the diskless client platform by using this format:

    instruction-set.machine-class. Solaris-version

    For example:


    The following are the possible platform options:

    Instruction Set 

    Machine Class 

    Solaris Version 



    sun4u, sun4m, sun4d, and sun4c 

    Starting with the Solaris 10 1/06 OS 

    Oracle Solaris 10, Solaris 9, and Solaris 8 



    Oracle Solaris 10, Solaris 9, and Solaris 8 

    Note –

    The sun-4c architecture is not supported in the Solaris 8, Solaris 9, or Oracle Solaris 10. The sun-4d architecture is not supported in the Solaris 9 or Oracle Solaris 10. The sun-4m architecture is not supported in the Oracle Solaris 10 OS.

  2. Identify the media path.

    The media path is the full path to the disk image that contains the OS that you want to install for the diskless client.

    In some he Oracle Solaris releases, the OS is delivered on multiple CDs. However, you cannot use the smosservice command to load OS services from a multiple CD distribution. You must run the scripts that are found on the Oracle Solaris software CDs (and optional Language CD), or the Oracle Solaris DVD, as described in the steps that follow:.

    Note –

    In this Oracle Solaris release, the software is delivered on DVD only.

  3. Create an install image on a server.

    For information on setting up an installation server, refer to Oracle Solaris 10 9/10 Installation Guide: Network-Based Installations.

  4. Load the required OS services from the CD or DVD image.

    If you are running a release that delivers Oracle Solaris on multiple CDs, use one of the following scripts:

    • CD 1 – /cdrom/cdrom0/Solaris_10/Tools/setup_install_server

    • Additional Oracle Solaris Software CDs – /cdrom/cdrom0/Solaris_10/Tools/add_to_install_server

    • Language CD – /cdrom/cdrom0/Solaris_10/Tools/add_to_install_server

    For example, if you are using the setup_install_server script from the Oracle Solaris Software 1 CD on a locally connected CD-ROM device, the syntax looks similar to the following:

    # mkdir /export/install/sol_10_x86
    # cd /cd_mount_point/Solaris_10/Tools
    # ./setup_install_server /export/install/sol_10_x86
  5. Add the BootFile and BootSrvA DHCP options to your DHCP server configuration to enable a PXE boot.

    For example:

    Boot server IP (BootSrvA) : svr-addr
    (BootFile) : 01client-macro

    where svr-addr is the IP address of the OS server and client-macro is named by the client's Ethernet type (01) and the Media Access Control (MAC) address of the client. This number is also the name of the file that is used in the /tftpboot directory on the installation server.

    Note –

    The notation for the client-macro consists of uppercase letters. This notation should not contain any colons.

    You can add these options from the command-line, or by using DHCP Manager. See Example 7–4 for more information.

    For more information, see x86: How to Perform a GRUB Based Boot From the Network, Preconfiguring System Configuration Information With the DHCP Service (Tasks) in Oracle Solaris 10 9/10 Installation Guide: Network-Based Installations, and Part III, DHCP, in System Administration Guide: IP Services.

  6. After the Oracle Solaris image is installed on the disk, note the disk media path. For example:


    This is the disk media path that needs to be specified when you use the smosservice command.

  7. Identify the SUNWCXall cluster when you add OS services.

    You must use the same cluster for diskless clients that run the same OS on the same system.

    Note –

    Always specify SUNWCXall as the cluster.