Managing Diskless Clients by Using the ossadm Command-Line Interface

By Juanita Heieck, April 2010

This article is for system administrators who are responsible for managing diskless clients.

The ossadm command-line interface (CLI) that is new in the upcoming Oracle Solaris 10 9/10 operating system (OS) can be used to manage diskless clients on both the SPARC and x86 platforms. This feature can be previewed prior to the official Oracle Solaris 10 9/10 release by customers who have an existing service contract. To use the feature, you must first download and install a sustaining patch by going to the SunSolve web site. For more information, see Downloading and Installing the ossadm Patch section of this article.

The following topics are covered in this article:

• Introducing the ossadm Command
• Downloading and Installing the ossadm Patch
• Preparing to Manage Diskless Clients With the ossadm Command
• Using the ossadm Command to Add OS Services for Diskless Client Support
• Using the ossadm Command to Add a Diskless Client
• Using the ossadm Command to Remove Support for OS Services and Diskless Clients
• ossadm(1M) Man Page

Introducing the ossadm Command

The new ossadm command enables you to administer OS services and diskless clients on both the SPARC and x86 platforms. This feature is being made available as a patch prior to the official release of the Oracle Solaris 10 9/10 OS. To download and the install the patch, you must have an existing service contract. Note that a similar version of the patch will also be made available to customers with service contracts when the Oracle Solaris 9/10 OS is officially released.

The ossadm command functions similarly to the two commands that have historically been used to manage diskless clients in the Solaris OS, smosservice and smdiskless. In addition, the ossadm command is interoperable with the smosservice and the smdiskless commands. The path to the binary file is the same as the existing interfaces, /usr/sadm/bin/.

Note - In the Oracle Solaris 10 9/10 OS, the ossadm command does not function as a complete replacement for the existing smosservice and smdiskless commands.

The ossadm command has two modes of operation: osservice and diskless. The osservice mode is used to administer OS instances on an OS server. The diskless mode is used to manage diskless operations on client systems. Currently, you must become superuser to administer diskless clients by using the ossadm command.

Note - Before using the ossadm command to manage diskless clients, see Known Issues When Adding OS Services and Diskless Client Support for additional information and requirements.

For overview information about managing client-server support, including the definition of a diskless client and what client support means, see Chapter 6, Managing Client-Server Support (Overview), in System Administration Guide: Basic Administration.

Supported ossadm Functionality

The following ossadm CLI functions are currently supported:

• Adding OS services
• Removing OS services
• Listing OS services
• Adding diskless clients
• Removing diskless clients
• Listing diskless clients

Note - The patching of diskless clients by using the ossadm CLI is not currently supported.

For more information, see the ossadm(1M) man page section of this article.

Known Issues When Adding OS Services and Diskless Client Support

The following are known issues:

• If you apply the initial version of the WBEM patch, note that the RUNPATH libraries that the ossadm command requires are not automatically set. Before using the ossadm command, you might need to manually set the RUNPATH libraries, as follows:

  Open a terminal window and run the following command to determine if the /usr/snadm/lib information already exists in the default library path:

  bash-3.2# crle
  

  • If the /usr/snadm/lib information already exists, there is no need to do anything further.

  • If the information does not exist, append a new path to the default library path by running the following command:

    bash-3.2# crle -l /lib:/usr/lib:/usr/snadm/lib
    

  To verify that the default library path was appended correctly, rerun the crle command without any arguments:

  bash-3.2# crle
  

• In this release, the -l locale option of the ossadm osservice add and ossadm diskless add commands does not work as expected. The locale automatically defaults to en_US, regardless of whether you use the -l option to specify another locale.

• When you add OS services by using either the ossadm osservice add command or the smosservice add command, root (/) and /usr packages with the ARCH=all type are skipped. No warning or error messages are displayed. This behavior has existed since the Solaris 2.1 OS and applies to both the SPARC and x86 platforms. Before beginning the process of adding diskless clients, you will need to locate and manually install these packages. Note that missing ARCH=all packages vary, depending on the OS that you are running. To install the appropriate packages, follow the instructions that are described in How to Locate and Install Missing ARCH=all Packages in System Administration Guide: Basic Administration.

Downloading and Installing the ossadm Patch

To use the ossadm CLI to administer diskless clients, you must first download the patch that is appropriate for your system type.

Note - The sustaining patch is only available to customers with existing service contracts.

To download the patch, go to http://sunsolve.sun.com/show.do?target=patchpage and then search for the patch ID that is appropriate for your system type.

The official patch is available for download and installation for the SPARC and x86 platforms, as follows:

• SPARC platform: 119313-33 (or later revision)

• x86 platform: 119314-34 (or later revision)

For detailed installation instructions, refer to the README file that is included with the patch.

Alternatively, you can wait until the Oracle Solaris 10 9/10 OS is officially released and install a similar version of the patch at that time. Be sure to install the latest revision of the patch. Note that a valid service contract is still required to obtain the patch.

Preparing to Manage Diskless Clients With the ossadm Command

Keep the following key points in mind when managing diskless clients by using the ossadm command:

• The software installation program does not prompt you to set up diskless client support. You must manually create an /export partition to support diskless clients. You create the /export partition during or after the installation process.

• The /export partition must contain a minimum of 5 Gbytes, depending upon the number of clients supported.

• The ossadm command does not permit users to specify a name service on the command line. The default setting that is used is files.

  Caution - Regardless of whether a name service, for example a NIS server, is configured on the OS server for the purpose of resolving diskless client requests, the OS server always defaults to using files. Hence, the /etc/hosts, /etc/bootparams, and /etc/ethers files are checked for entries.

  For more information, see the ossadm(1M) man page section of this article.

• The set_nfs4_domain script that was delivered in the initial Solaris 10 OS is no longer used to set the NFSv4 domain. To set the NFSv4 domain, add the nfs4_domain keyword to the diskless client's sysidcfg file, for example, server:/export/root/client/etc/sysidcfg

  If the nfs4_domain keyword exists in the client system's sysidcfg file, the first boot of a diskless client sets the domain accordingly. Also, the OS server should be up and running, and the diskless client's NFSv4 domain setting must match the setting in the OS server's /var/run/nfs4_domain file.

  For more information, see Preconfiguring With the sysidcfg File in Oracle Solaris 10 10/09 Installation Guide: Network-Based Installations.

• The OS server and the diskless client must be on the same subnet.

• You cannot provide client services on a multiterabyte UFS file system, because OS and diskless client services cannot be added to a UFS file system that resides on an EFI-labeled disk.

  Note - Attempts to add OS and diskless client services to a UFS file system that resides on an EFI-labeled disk result in an erroneous insufficient disk space message similar to the following:

  The partition /export does not have enough free space.
  1897816 KB (1853.34 MB) additional free space required.
  Insufficient space available on
  /dev/dsk/c0t5d0s0 /export
  

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:

• /export/Solaris_version/Solaris_version-instruction-set.all (symbolic link to /export/exec/Solaris_version/Solaris_version-instruction-set.all)
• /export/Solaris_version
• /export/Solaris_version/var
• /export/Solaris_version/opt
• /export/share
• /export/root/templates/Solaris_version
• /export/root/clone
• /export/root/clone/Solaris_version
• /export/root/clone/Solaris_version/machine-class

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

• /export/root/diskless-client
• /export/swap/diskless-client
• /tftpboot/diskless-client-ipaddress-in-hex/export/dump/diskless-client (if you specify the -x dump option)

How to Prepare to Add Diskless Clients in a GRUB Based Boot Environment

When you use the ossadm 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 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 Chapter 6, Managing Client-Server Support (Overview), in System Administration Guide: Basic Administration.

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

   instruction-set.machine-class. Solaris_version

   For example:

   i386.i86pc.Solaris_10

   The following are the possible platform options:

   Instruction Set Machine Class Solaris Version sparc sun4v sun4u, sun4, sun4d, and sun4c Starting with the Solaris 10 1/06 OS Solaris 8, Solaris 9, and Oracle Solaris 10 i386 i86pc Solaris 8, Solaris 9, and Oracle Solaris 10

   Note - The sun-4c architecture is not supported in the Solaris 8, 9, or Oracle Solaris 10 releases. The sun-4d architecture is not supported in the Solaris 9 or Oracle Solaris 10 releases. 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.

   The Solaris OS is delivered on multiple CDs. However, you cannot use the ossadm command to load OS services from a multiple CD distribution. You must run the scripts that are found on the Solaris software CDs (and optional Language CD) to do the following:

   1. Create an install image on a server. For information on setting up an install server, refer to Oracle Solaris 10 10/09 Installation Guide: Network-Based Installations.
   2. Load the required OS services from the CD image.

      Use one of the following scripts:

      • CD 1: /cdrom/cdrom0/Solaris_10/Tools/setup_install_server
      • Additional 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 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
      

   3. 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 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 4 for more information.

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

   /net/export/install/sol_10_x86
   

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

4. 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.

How to Prepare to Add Diskless Clients in the Oracle Solaris 10 OS

This procedure describes how to prepare to add diskless clients if you are running a Solaris release that does not implement GRUB (prior to Solaris 10 1/06).

When you use the ossadm 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 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.

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

   instruction-set.machine-class.Solaris_version

   For example:

   sparc.sun4u.Solaris_10

   The following are the possible platform options:

   Instruction Set Machine Class Operating System Version sparc sun4v sun4c, sun4d, sun4m, sun4u, Starting with the Solaris 10 1/06 OS Solaris 8, Solaris 9, and Oracle Solaris 10 i386 i86pc Solaris 8, Solaris 9, and Oracle Solaris 10

   Note - The sun-4c architecture is not supported in the Solaris 8, 9, or Oracle Solaris 10 releases. The sun-4d architecture is not supported in the Solaris 9 or Oracle Solaris 10 releases. 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.

   The Solaris OS is delivered on multiple CDs. However, you cannot use the ossadm command to load OS services from a multiple CD distribution. You must run the scripts that are found on the Solaris software CDs (and optional Language CD) to do the following:

3. Create an install image on a server. For information on setting up an install server, refer to Oracle Solaris 10 10/09 Installation Guide: Network-Based Installations.
4. Load the required OS services from the CD image.

   Use one of the following scripts:

   • CD 1: /cdrom/cdrom0/Solaris_10/Tools/setup_install_server
   • Additional 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 Solaris Software 1 CD on a locally connected CD-ROM device, the syntax looks similar to the following:

   # mkdir /export/install/sparc_10
   # cd /cd_mount_point/Solaris_10/Tools
   
   # ./setup_install_server /export/install/sparc_10
   

5. After the Solaris CD image is installed on the disk, specify the disk media path. For example:

   /export/install/sparc_10
   

6. 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.

   For example, consider the following Solaris 9 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 release (in this example, 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.

Using the ossadm Command to Add OS Services for Diskless Client Support

The following procedures and examples describe how to add OS services by using the ossadm CLI.

How to Add OS Services for Diskless Client Support by Using the ossadm Command

1. Become superuser or assume an equivalent 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/ossadm osservice ls
   

   osservice

   Specifies the mode of operation to be used by the ossadm command.

   ls

   Lists the OS instances that are added to the OS server.

3. Add the OS services.

   # /usr/sadm/bin/ossadm osservice add -p  platform -d mediapath -l locale,
   
   locale... -c metacluster
   

   osservice

   Specifies the mode of operation to be used by the ossadm command.

   add

   Adds the specified OS service.

   -p

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

   -d

   Specifies the full path to the OS installation image.

   -c metacluster

   Specifies the Solaris cluster to install.

   -l locale

   Specifies the locale to install. If not otherwise specified, the default is en_US.

   Note - The installation process can take up to 45 minutes, depending on the server speed and the OS service configuration that you choose.

   For more information, see the ossadm(1M) man page section of this article.

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/ossadm ossservice ls
   

Example 1: Adding an OS Service for Diskless Client Support on the SPARC Platform

This example shows how to add SPARC OS services on the server jupiter. The server jupiter is running the Oracle Solaris 10 OS. The CD image of the Oracle Solaris 10 SPARC OS is located on the installation server myway in the /export/s10/combined.s10s_u2wos/61 directory.

# /usr/sadm/bin/ossadm osservice add -d /net/myway/export/s10/combined.s10s_u2wos/61 \

-p sparc.sun4u.Solaris_10 -c SUNWCXall -l en_US


# /usr/sadm/bin/ossadm osservice ls

Client      Root Area
            Swap Area
            Dump Area
.
.
.
#

Example 2: Adding an OS Service for Diskless Client Support on the x86 Platform

This example shows how to add x86 OS services on the server orbit. The server orbit is running the Oracle Solaris 10 OS. The CD image of the Oracle Solaris 10 x86 OS is located on the installation server seriously in the /export/s10/combined.s10x_u2wos/03 directory.

# usr/sadm/bin/ossadam osservice add -d \
/net/seriously/export/s10u2/combined.s10x_u2wos/03 -p \
i386.i86pc.Solaris_10 -c SUNWCXall -l en_US

# /usr/sadm/bin/ossadm osservice ls.
Client          Root Area
                Swap Area
                Dump Area
--------------------------------------------------------------------------------
.
.
.
#

Next Steps

The ossadm osservice add command does not install any root (/) or /usr packages that are designated ARCH=All. After you add OS services to the OS server, you must locate and manually install these packages. For more information, see How to Locate and Install Missing ARCH=all Packages in System Administration Guide: Basic Administration.

Using the ossadm Command to Add a Diskless Client

The following two procedures describes how to add a diskless client. The first procedure describes how to add a diskless client to a system that is running an Oracle Solaris 10 release that implements GRUB based booting. The second procedure describes how to add a diskless client to a system that is running a Solaris release that does not use GRUB.

x86: How to Add a Diskless Client in the GRUB Based Boot Environment

If you are running at least the Solaris 10 1/06 OS, use the following procedure to add a diskless client on an x86 based system after you have added OS services.

1. Become superuser or assume an equivalent role.
2. Add the diskless client.

   # /usr/sadm/bin/ossadm diskless add -i ip-address -e ethernet-address -h  client-name -p
   
   instruction-set.machine-class.Solaris_version -r root-area -s swap-area -S swap-size -d dump-area
   
   -D dump-size -c sysidcfg-path -l locale
   

   diskless

   Specifies the mode of operation to be used by the ossadm command.

   add

   Adds the specified diskless client.

   -i ip-address

   Specifies the IP address of the diskless client.

   -e ethernet-address

   Specifies the Ethernet address of the diskless client.

   -h hostname

   Specifies the host name of the diskless client.

   -p instruction-set .machine-class.Solaris_version

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

   -r root-area

   Specifies the root (/) directory for the diskless client. If not otherwise specified, /export/root/client-name is used.

   -s swap-area

   Specifies the swap file for the diskless client. If not otherwise specified, /export/root/client-name is used.

   -S swap-size

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

   -d dump-area

   Specifies the dump area for the diskless client.

   -D dump-size

   Specifies the dump size for the diskless client.

   -c sysidconfig-path

   Specifies the path to the sysidconfig file for the diskless client.

   -l locale

   Specifies the locale to install for the diskless client. If not otherwise specified, the default is en_US.

   For more information, see the ossadm(1M) man page section of this article.

3. If not already created, add the BootSrva and BootFile DHCP options to your DHCP server configuration to enable a PXE boot.

   For example:

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

   where svr-addr is the IP address of the server and client-macro is named by the client's Ethernet type (01) and the 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 client-macro notation consists of uppercase letters. The notation must not contain any colons.

   The following files and directories are created in the /tftpboot directory:

   drwxr-xr-x   6 root sys     512 Dec 28 14:53 client-host-name
   
   lrwxrwxrwx   1 root root     31 Dec 28 14:53 menu.lst.01ethernet-address
   
                           -> /tftpboot/client-host-name/grub/menu.lst
   -rw-r--r--   1 root root 118672 Dec 28 14:53 01ethernet-address
   

4. If the console is on a serial port, edit the /tftpboot/menu.lst.01 ethernet-address file to uncomment the line that specifies the tty setting.

   To change the default menu.lst file that is created on the client, edit the echo lines in the /usr/sadm/lib/wbem/config_tftp file.

5. Verify that the diskless clients were installed.

   # /usr/sadm/bin/ossadm diskless ls
   

6. (Optional) Continue to use the ossadm add command to add each diskless client.

Example 3: Adding Diskless Client Support to an x86 Based System in the GRUB Boot Environment

This example shows how to add an x86 diskless client, mikey1.

rainy-01# /usr/sadm/bin/ossadm add -h mikey1 -i 192.168.20.22 \
-e 00:E0:88:55:33:BC -p i386.i86pc.Solaris_10 -r /export/root/mikey1 \
-s /export/swap/mikey1 -S 400

# /usr/sadm/bin/ossadm diskless ls
Platform
--------------------------------------------------------------------------------
i386.i86pc.Solaris_10
sparc.sun4us.Solaris_10
sparc.sun4u.Solaris_10
i386.i86pc.Solaris_9

Example 4: Adding the BootSrvA and BootFile DHCP Options to the DHCP Server Configuration

This example shows how to add the BootSrva and BootFile DHCP options that are necessary for enabling a PXE boot.

rainy-01# pntadm -A mikey1 -m 0100E0885533BC -f 'MANUAL+PERMANENT' \ -i 0100E0885533BC 192.168.0.101

rainy-01# dhtadm -A -m 0100E0885533BC -d \ ":BootSrvA=192.168.0.1:BootFile=0100E0885533BC:"

In the preceding examples, the server address is the IP address of the server, and the client macro is named by the client's Ethernet type (01) and its MAC address. This number is also the name of the file that is used in the /tftpboot directory on the installation server. Note that the notation for the client macro consists of uppercase letters and should not contain any colons.

How to Add a Diskless Client on a System That Does Not Use GRUB

Unless otherwise noted, the following procedure includes general information for both SPARC based and x86 based systems. If you have an x86 based system and are running a Solaris release that does not implement GRUB based booting (prior to Solaris 10 1/06), use this procedure to add a diskless client after you have added OS services.

1. Become superuser or assume an equivalent role.
2. Add the diskless client.

   # /usr/sadm/bin/ossadm diskless add -i ip-address -e ethernet-address -h client-name \
    -p instruction-set.machine-class.Solaris_version \
   
   -r /export/root/client-name -s /export/swap/client-name -S swap-size -l locale
   

   add

   Adds the specified diskless client.

   -i ip-address

   Specifies the IP address of the diskless client.

   -e ethernet-address

   Specifies the Ethernet address of the diskless client.

   -h client-name

   Specifies the name of the diskless client.

   -p instruction-set.machine-class.Solaris_version

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

   -r root-area

   Specifies the root (/) directory for the diskless client. If not otherwise specified, /export/root/client-name is used.

   -s swap-area

   Specifies the swap file for the diskless client. If not otherwise specified, /export/root/client-name is used.

   -S swap-size

   Specifies the size of the swap file in Mbytes. If not otherwise specified, the default is 24 Mbytes.

   -l locale

   Specifies the locale to install for the diskless client. If not otherwise specified, the default is en_US.

3. (Optional) Continue to use the ossadm add command to add each diskless client.
4. Verify that the diskless clients were installed.

   # /usr/sadm/bin/ossadm diskless ls
   

Example 5: Adding Diskless Client Support to a SPARC Based System

This example shows how to add a sun4u diskless client starlite from the server bearclaus.

# /usr/sadm/bin/ossadm diskless add \
-i 172.20.27.28 -e 8:0:20:a6:d4:5b -h starlite -p sparc.sun4u.Solaris_10 \
-r /export/root/starlite -s /export/swap/starlite -S 128 -l en_US

# /usr/sadm/bin/ossadm diskless ls
Platform
--------------------------------------------------------------------------------
i386.i86pc.Solaris_10
sparc.sun4us.Solaris_10
sparc.sun4u.Solaris_10
i386.i86pc.Solaris_9
sparc.sun4m.Solaris_9
sparc.sun4u.Solaris_9
sparc.sun4us.Solaris_9

Note that the ossadm diskless ls command output lists information for both SPARC based and x86 based systems.

Example 6: Adding Diskless Client Support to an x86 Based System

This example shows how to add an x86 diskless client mars from the server bearclaus.

# /usr/sadm/bin/ossadm diskless add \
 -i 172.20.27.176 -e 00:07:E9:23:56:48 -h mars -p i386.i86pc.Solaris_10 \
-r /export/root/mars -s /export/swap/mars -S 128 -l en_US

Using the ossadm Command to Remove Support for OS Services and Diskless Clients

The following procedures describe how to remove diskless client support and OS services for a diskless client.

How to Remove Diskless Client Support

1. Become superuser or assume an equivalent role.
2. Remove the diskless client support.

   # usr/sadm/bin/ossadm diskless del -h client-name
   

   diskless

   Specifies the mode of operation to be used by the ossadm command.

   del

   Specifies the command to delete the diskless client

   -h

   Specifies the diskless client name.

3. Verify that the diskless client support has been removed.

   # /usr/sadm/bin/ossadm diskless ls
   

Example 7: Removing Diskless Client Support

This example shows how to remove the diskless client holoship from the OS server starlite.

# /usr/sadm/bin/ossadm diskless del holoship

# /usr/sadm/bin/ossadm diskless ls

client          Root Area
                Swap Area
                Dump Area

How to Remove OS Services for Diskless Clients

1. Become superuser or assume an equivalent role.
2. Remove the OS services for the diskless clients.

   # /usr/sadm/bin/ossadm osservice del -p instruction-set.all.Solaris_version
   
   

   diskless

   Specifies the mode of operation to be used by the ossadm command.

   del

   Specifies the command to delete the diskless client

   -p

   Specifies the instruction set, machine class, and OS version of the diskless client.

   Note - Only the machine-class all is supported.

3. Verify that the OS services have been removed.

   # /usr/sadm/bin/ossadm osservice ls
   

Example 8: Removing OS Services for Diskless Clients

The following example shows how to removing the diskless client OS services (sparc.all.Solaris_10) from the server starlite.

# /usr/sadm/bin/ossadm osservice del -p sparc.all.solaris_10

# /usr/sadm/bin/ossadm osservice ls
Client          Root Area
                Swap Area
                Dump Area

Where to Find More Information About Administering Diskless Clients

For more information on other related topics, refer to the following:

ossadm Man Page

- Manage OS services and diskless clients

Synopsis

/usr/sadm/bin/ossadm osservice add -p platform -d mediapath [-l locale [,locale[...]]] -c metacluster

/usr/sadm/bin/ossadm osservice ls

/usr/sadm/bin/ossadm osservice del -p platform

/usr/sadm/bin/ossadm diskless add -p platform -h host -i ip_addr -e ethernet_addr [-r root_area][-s swap_area [-S swap_size]] [-d dump_area [-D dump_size]] -c sysidcfg_path -l locale]


/usr/sadm/bin/ossadm diskless ls

/usr/sadm/bin/ossadm diskless del -h host

Description

The ossadm command operates in two modes: osservice and diskless. The osservice mode is used to manage OS Services. The diskless mode is used to manage OS diskless clients.

Subcommands

The osservice and diskless modes have three subcommands:

add

Adds the specified OS Service or Diskless Client.

ls

Lists all of the installed OS Services and the configured diskless clients on the system.

del

Deletes the specified OS service and diskless client from the system.

Options

The ls subcommand for both modes does not expect any options.

For mode and subcommand osservice add, the following options are supported:

-p platform

Specifies the OS Service to add.

The instruction set architecture, machine class, OS, and version are given in the following format:

instruction_set.machine_class.Solaris_version

For example, sparc.sun4u.Solaris_10

-d mediapath

Specifies the full path of Solaris CD image or net install image.

-c

Specifies the Solaris cluster to install.

-l locale[,locale[...]]

Specifies the locales to install from the specified cluster. A comma-delimited list of locales can be specified. If not otherwise specified, the default is en_US.

For mode and subcommand osservice del, the following options are supported:

-p platform

Specifies the OS Service to delete. The format is same as the add subcommand, with the exception that all is substituted for machine class.

For example, sparc.all.Solaris_10

To delete an OS service for a specific platform, there must not be an existing diskless client that uses this OS service.

For the mode and subcommand diskless add, the following options are supported:

-i ip_addr

Specifies the IP address to be used by the diskless client.

-e ethernet_addr

Specifies the Ethernet address to be used by the diskless client.

-h hostname

Specifies the host name of the diskless client that is to be added.

-p platform

Specifies the existing OS Service that is associated with the platform intended for use by the diskless client.

The format that is used is the same as the osservice add command:

instruction_set.machine_class.Solaris_version

-r root_loc

Specifies where the root (/) file system for the client should be created on the server. If not otherwise specified, the default location is /export/root/client_hostname.

-s swap_loc

Specifies where the swap file system for the client should be created on the server. If not otherwise specified, the default location is /export/swap/client_hostname.

-S swap_size

Specifies the size of the swap file. If not otherwise specified, the default is 24 Mbytes.

-d dump_area

Specifies the dump area for the diskless client.

-D dump_size

Specifies the dump size for the diskless client.

-c sysidcfg_path

Specifies the path to the sysidcfg(4) file. If the path is specified, the client system is configured accordingly during the first boot. Otherwise, the command creates a default sysidcfg(4) file for the client. The parsing of the sysidcfg file is done during the first boot as part of the sysidtool(1M) program.

-l locale

Specifies the locale to install the diskless client. If not otherwise specified, the default is en_US.

Exit Status

The following exit values are returned:

0

Successful completion.

>0

An error occurred.

Examples

Example 9: Creating a New OS Service

The following command adds an Oracle Solaris 10 OS service for the sun4u machine class:

bash-3.00# ossadm osservice add -p sparc.sun4u.Solaris_10 -d \

/export/images/s10u6/ -c SUNWCXall Clone area /export/root/clone/Solaris_10/sun4u created.
Creating clone area /export/root/clone/Solaris_10/sun4u.

bash-3.00# ossadm osservice ls
Platform
sparc.sun4u.Solaris_10

Example 10: Adding a Diskless Client

The following command adds the diskless client dltest-3 for the sun4u machine class:

bash-3.00# ossadm diskless add -p sparc.sun4u.Solaris_10 \
-h dltest-3 -i 200.200.200.3 -e 00:03:ba:4e:3c:51
-r /export/root/dltest-3 -s /export/swap/dltest-3 -S 240

Example 11: Removing a Diskless Client

The following command removes the diskless client dltest-3 from the server:

bash-3.00# ossadm diskless del -h dltest-3

Example 12: Removing OS Services

The following command removes Oracle Solaris 10 OS services from the server:

bash-3.00# ossadm osservice del -p sparc.all.Solaris_10

Done removing OS Service "sparc.all.Solaris_10".
Removing any empty directories in /export.
Removing empty network boot directory: /rplboot.
Removing empty network boot directory: /tftpboot.
Removing network boot file.
Removing OS Service file: /var/sadm/system/admin/services/Solaris_10.
Removing all of /export/share/.copyofSolaris_10.
Removing all of /export/share/Solaris_10.
Removing all of /export/root/templates/Solaris_10.
Removing all of /export/exec/kvm/Solaris_10_sparc.*.
Removing all of /export/exec/.copyofSolaris_10_sparc.all.
Removing all of /export/exec/Solaris_10_sparc.all.
Removing all of /export/.copyofSolaris_10.
Removing all of /export/Solaris_10.
Removing "/export/exec/Solaris_10_sparc.all/usr" from /etc/dfs/dfstab.
Unsharing directory: /export/exec/Solaris_10_sparc.all/usr.

Removing OS Service "sparc.all.Solaris_10".
Remove service starting at Wed Mar 24 15:35:12 2010

Example 13: Listing OS Services

The following command lists the OS services that have been added to the system:

bash-3.00# ossadm osservice ls
Platform
sparc.sun4u.Solaris_10

Example 14: Listing Diskless Clients

The following command lists the diskless clients on the system:

bash-3.00# ossadm diskless ls
Client          Root Area
                Swap Area
                Dump Area
dltest-3        dlsrv:/export/root/dltest-3
                dlsrv:/export/swap/dltest-3

Attributes

See the attributes(5) man page for descriptions of the following attributes:

See Also

smosservice(1M), smdiskless(1M), sysidtool(1M), sysidcfg(4)