System Administration Guide: Basic Administration

Managing Diskless Clients

These sections describe the procedures needed to manage diskless clients.

Keep the following key points in mind when managing diskless clients:

After you determine the platform, media path, and cluster for each diskless client, you are ready to add OS services. The following directories are created and populated for each OS service that you add:

The following default directories are created and populated on the OS server for each diskless client that you add:


Note –

You can modify the default locations of the root, /swap, and /dump directories by using the -x option. However, do not create these directories under the /export file system.


How to Prepare for Adding Diskless Clients

Make sure that the system intended to be the OS service is running a supported release. Also verify that the combination of OS server release and diskless client release is supported.

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

  1. Verify that the intended OS server and diskless client will be running a combination of Solaris releases that are supported.

    For more information, see OS Server and Diskless Client Support Information.

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

    instruction_set.machine_class.Solaris_version

    For example:

    sparc.sun4u.Solaris_9

    The following are the possible platform options:

    instruction_set

    machine_class

    Solaris_version

    sparc 

    sun4d*, sun4c*, sun4m, sun4u, 

    Solaris_9, Solaris_8, Solaris_2.7, Solaris_2.6 

    i386 

    i86pc 

    Solaris_9, Solaris_8, Solaris_2.7, Solaris_2.6 

    * The sun4c architecture is not supported in the Solaris 8 and Solaris 9 releases. The sun4d architecture is not supported in the Solaris 9 release.

  3. Identify the media path, which is the full path to the disk image that contains the operating system that you want to install for the diskless client.

    The Solaris 9 operating environment 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 Solaris 9 software CDs (and optional Language CD) to do the following:

    • Create an install image on a server. For information on setting up an install server, refer to Solaris 9 Installation Guide.

    • Load the required OS services from the CD image using one of the following scripts:

      • CD 1 of 2 – /cdrom/cdrom0/s0/Solaris_9/Tools/setup_install_server

      • CD 2 of 2 – /cdrom/cdrom0/s0/Solaris_9/Tools/add_to_install_server

      • Language CD – /cdrom/cdrom0/s0/Solaris_9/Tools/add_to_install_server

      For example, if you are using the setup_install_server script from the Solaris 9 Software 1 of 2 SPARC Platform Edition CD on a locally connected CD-ROM device, the syntax looks something like this:


      # mkdir /export/install/sparc_9
      # cd /cd_mount_point/Solaris_9/Tools
      # ./setup_install_server /export/install/sparc_9
      
    • After the Solaris CD image is installed on the disk, specify the disk image path. For example:


      /net/export/install/sparc_9
  4. Identify the SUNWCXall cluster when you add OS services.

    You must use the same cluster for diskless clients that run the same operating environment on the same system (SPARC or IA).

    For example, consider the following diskless clients:

    • sparc.sun4m.Solaris_9

    • sparc.sun4u.Solaris_9

    To set up these diskless clients, you would need to specify the SUNWCXall cluster for each diskless client because the sun4u and sun4m systems require the SUNWCXall cluster. In addition, diskless clients that run the same operating environment (in this situation, Solaris_9) on the same system must use the same cluster.


    Note –

    If you are using a sun4u system, or if you are using a system with an accelerated 8-bit color memory frame buffer (cgsix), you must specify SUNWCXall as the cluster.


How to Add OS Services For Diskless Client Support

Use this procedure to add OS services for a diskless client on the server.

  1. Become superuser or assume an equivalent role on the server.

    For more information, see How to Become Superuser (root) or Assume a Role.

  2. Verify that the Solaris Management Console server is running and that the diskless client tools are available on the system.


    # /usr/sadm/bin/smosservice list -H starbug:898 --
    Loading Tool: com.sun.admin.osservermgr.cli.OsServerMgrCli from starbug:898
    Login to starbug as user root was successful.
    Download of com.sun.admin.osservermgr.cli.OsServerMgrCli from starbug:898 
    was successful.
    Platform
    --------------------------------------------------------------------------
  3. Add the OS services.


    # /usr/sadm/bin/smosservice add -H hostname:898 -- -o hostname 
    -x mediapath=path -x platform=instruction-set.machine-class.Solaris-version 
    -x cluster=cluster-name -x locale=locale-name
    

    add

    Adds the specified OS service. 

    -H hostname:898

    Specifies the host name and port to which you want to connect. If you do not specify a port, the system connects to the default port, 898. 

    --

    Identifies that the subcommand arguments start after this point. 

    -x mediapath=path

    Specifies the full path to the Solaris image. 

    -x

    platform=instruction-set.machine-class.Solaris-version

    Specifies the instruction architecture, machine class, and the Solaris version to be added.  

    -x cluster=cluster-name

    Specifies the Solaris cluster to install. 

    -x locale=locale-name

    Specifies the locale to install. 


    Note –

    The installation process can take approximately 45 minutes, depending on the server speed and the OS service configuration you choose.


    For more information, see smosservice(1M).

  4. (Optional) Continue to add the other OS services.

  5. When you are finished adding OS services, verify that the OS services were installed.


    # /usr/sadm/bin/smosservice list -H hostname:898 --
    

Example—Adding an OS Service for Diskless Client Support

This example describes how to add Solaris 8 OS services on the server starbug. The server starbug is running the Solaris 9 release.


# /usr/sadm/bin/smosservice add -H starbug:898 -- -o starbug 
-x mediapath=/net/install/export/sparc_8 -x platform=sparc.sun4u.Solaris_8 
-x cluster=SUNWCXall -x locale=en_US
Authenticating as user: root

Type /? for help, pressing enter accepts the default denoted by [ ]
Please enter a string value for: password :: xxx
Loading Tool: com.sun.admin.osservermgr.cli.OsServerMgrCli from starbug:898
Login to starbug as user root was successful.
Download of com.sun.admin.osservermgr.cli.OsServerMgrCli from starbug:898 
was successful.

How to Add a Diskless Client

Use this procedure to add a diskless client after you have added OS services.

  1. Become superuser or assume an equivalent role.

    For more information, see How to Become Superuser (root) or Assume a Role.

  2. Add the diskless client.


    # /usr/sadm/bin/smdiskless add -- -i ip-address -e ethernet-address 
    -n client-name -x os=instruction-set.machine-class.Solaris-version 
    -x root=/export/root/client-name -x swap=/export/swap/client-name 
    -x swapsize=size -x tz=timezone -x locale=locale-name
    

    add

    Adds the specified diskless client. 

    --

    Identifies that the subcommand arguments start after this pont. 

    -i ip-address

    Identifies the IP address of the diskless client. 

    -e ethernet-address

    Identifies the Ethernet address of the diskless client. 

    -n client-name

    Specifies the name of the diskless client. 

    -x os=instruction-set.machine-class.Solaris-version

    Specifies the instruction architecture, machine class, OS, and the Solaris version for the diskless client. 

    -x root=root=/export/root/client-name

    Identifies the root directory for the diskless client. 

    -x swap=root=/export/root/client-name

    Identifies the swap file for the diskless client. 

    -x swapsize=size

    Specifies the size of the swap file in Mbytes. The default is 24 Mbytes. 

    -x tz=timezone

    Specifies the timezone for the diskless client. 

    -x locale=locale-name

    Specifies the locale to install for the diskless client. 

    For more information, see smdiskless(1M).

  3. (Optional) Continue to use the smdiskless add command to add each diskless client.

  4. Verify that the diskless clients were installed.


    # /usr/sadm/bin/smosservice list -H hostname:898 --
    

Examples—Adding a Diskless Client

This example shows how to add a Solaris 8 client, earth, from the server starbug.


# /usr/sadm/bin/smdiskless add -- -i 172.20.27.27 -e 8:0:20:1f:33:9e 
-n earth -x os=sparc.sun4m.Solaris_8 -x root=/export/root/earth 
-x swap=/export/swap/earth -x swapsize=64 -x tz=US/Mountain -x locale=en_US

This example shows how to add a Solaris 7 client, earth2, from the server starbug.


# /usr/sadm/bin/smdiskless add -- -i 172.20.27.26 -e 8:0:20:1f:32:be
-n earth2 -x os=sparc.sun4m.Solaris_2.7 -x root=/export/root/earth2 
-x swap=/export/swap/earth2 -x swapsize=64 -x tz=US/Mountain

How to Boot a Diskless Client

  1. Verify the following prerequisites on the OS server:

    • Confirm that the name service used to add the diskless client and the OS services matches the primary name in the server's /etc/nsswitch.conf file.

      Otherwise, the diskless client won't boot.

    • Confirm that the rpc.bootparamd daemon is running. If it is not running, start it.

  2. Boot the diskless client.


    ok boot net
    

How to Delete Diskless Client Support

  1. Become superuser or assume an equivalent role.

    For more information, see How to Become Superuser (root) or Assume a Role.

  2. Remove the diskless client support.


    # /usr/sadm/bin/smdiskless delete -- -o hostname:898 -n client-name
    
  3. Verify that the diskless client support is removed.


    # /usr/sadm/bin/smosservice list -H hostname:898 --
    

Example—Deleting Diskless Client Support

This example shows how to delete the diskless client earth from the OS server starbug.


# /usr/sadm/bin/smdiskless delete -- -o starbug -n earth
Authenticating as user: root

Type /? for help, pressing enter accepts the default denoted by [ ]
Please enter a string value for: password :: 
Starting SMC server version 2.0.0.
endpoint created: :898
SMC server is ready.
Loading Tool: com.sun.admin.osservermgr.cli.OsServerMgrCli from starbug
Login to starbug as user root was successful.
Download of com.sun.admin.osservermgr.cli.OsServerMgrCli from starbug
was successful.

How to Delete OS Services for Diskless Clients

  1. Become superuser or assume an equivalent role.

    For more information, see How to Become Superuser (root) or Assume a Role.

  2. Remove the OS services for the diskless clients.


    # /usr/sadm/bin/smosservice delete -H hostname:898 -- 
    -x rmplatform=instruction-set.machine-class.Solaris-version
    
  3. Verify that the OS services are removed.


    # /usr/sadm/bin/smosservice list -H hostname:898 --
    

Example—Deleting OS Services for Diskless Clients

The following example shows how to delete the diskless client OS services (sparc.all.Solaris_9) from the server starbug.


# /usr/sadm/bin/smosservice delete -H starbug:898 -- 
-x rmplatform=sparc.all.Solaris_9
Authenticating as user: root
Type /? for help, pressing enter accepts the default denoted by [ ]
Please enter a string value for: password :: 
Loading Tool: com.sun.admin.osservermgr.cli.OsServerMgrCli from starbug:898
Login to starbug as user root was successful.
Download of com.sun.admin.osservermgr.cli.OsServerMgrCli from starbug:898
was successful.