Identify the diskless client platform by using this format:

instruction-set.machine-class.Solaris_version

For example:

i386.i86pc.Solaris_11

The following are the possible platform options:

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 smosservice 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:

Create an install image on a server. For information on setting up an install server, refer to Solaris Express Installation Guide: Network-Based Installations .

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

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

# mkdir /export/install/sol_11_x86
# cd /cd_mount_point/Solaris_11/Tools
# ./setup_install_server /export/install/sol_11_x86

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.

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 How to Perform a GRUB Based Boot From the Network, Preconfiguring System Configuration Information With the DHCP Service (Tasks) in Solaris Express Installation Guide: Network-Based Installations , and Part III, DHCP, in System Administration Guide: IP Services .

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

/net/export/install/sol_11_x86_

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

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.

Identify the diskless client platform by using this format:

instruction-set.machine-class.Solaris-version

For example:

sparc.sun4u.Solaris_10

The following are the possible platform options:

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 smosservice 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:

Create an install image on a server. For information on setting up an install server, refer to Solaris Express Installation Guide: Network-Based Installations .

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

For example, if you are using the setup_install_server script from the Solaris Express 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

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

/export/install/sparc_10

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:

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.

Become superuser or assume an equivalent role.

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

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 host-name:898 --

Add the OS services.

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

For more information, see the smosservice ( 1M ) man page.

(Optional) Continue to add the other OS services.

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

# /usr/sadm/bin/smosservice list -H host-name:898 --

Become superuser or assume an equivalent role.

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

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=
time-zone -x locale=
locale-name

For more information, see the smdiskless ( 1M ) man page.

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.

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

If the console is on a serial port, edit the /tftpboot/menu.lst.01 ethernet-address file. 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.

For more information, see Performing a GRUB Based Boot From the Network.

Verify that the diskless clients were installed.

# /usr/sadm/bin/smdiskless list -H host-name:898 --

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

Become superuser or assume an equivalent role.

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

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=
time-zone -x locale=
locale-name

For more information, see the smdiskless ( 1M ) man page.

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

Verify that the diskless clients were installed.

# /usr/sadm/bin/smdiskless list -H host-name:898 --

Boot the diskless client by typing the correct keystroke combination.

The GRUB menu is displayed.

GNU GRUB  version 0.95  (631K lower / 2095488K upper memory)

 +-------------------------------------------------------------------------+
 | Solaris 10.1 ... X86                                                    |
 | Solaris failsafe                                                        |
 |                                                                         |
 |                                                                         |
 |                                                                         |
 +-------------------------------------------------------------------------+

The GRUB menu that is displayed on your system might vary from the previous example, depending on the configuration of your network installation server.

Use the arrow keys to select a boot entry, then press Enter.

If you do not make a selection, the default OS instance is automatically booted after several seconds.

• If you need to set specific boot arguments, use the arrow keys to select a boot entry, then type e to edit the entry.

      GNU GRUB  version 0.95  (631K lower / 2095488K upper memory)
  
   +-------------------------------------------------------------------------+
   | root (hd0,2,a)                                                          |
   | kernel /platform/i86pc/multiboot                                        |
   | module /platform/i86pc/boot_archive                                     |
   |                                                                         |
   |                                                                         |
   |                                                                         |
   +-------------------------------------------------------------------------+
        Use the ^ and v keys to select which entry is highlighted.
        Press 'b' to boot, 'e' to edit the selected command in the
        boot sequence, 'c' for a command-line, 'o' to open a new line
        after ('O' for before) the selected line, 'd' to remove the
        selected line, or escape to go back to the main menu.
  
  
  grub edit> kernel /platform/i86pc/multiboot

  The boot command that you want to edit is displayed in the GRUB edit screen.

• Edit the kernel command by typing the boot arguments or options that you want to use.

  • To manually redirect the console to ttyb, type:

    grub edit> kernel /platform/i86pc/multiboot -B console=ttyb
    

  • To use the input-device/output-device property, type:

    grub edit> kernel /platform/i86pc/multiboot -B input-device=ttyb,output-device=ttyb
    

  • To override the serial line speed, type:

    grub edit> kernel /platform/i86pc/multiboot -B ttyb-mode="115200,8,n,1,-"
    

  • You can also edit the /tftpboot/menu.lst.01 client-macro file, by using one of the commented out entries in the menu.lst file. For more information, see GRUB Menu.

  For more information about boot options and arguments, see Modifying the Solaris Boot Behavior by Editing the GRUB Menu.

• To save the edits and return to the GRUB menu, press Enter.

  The GRUB menu is displayed, showing the edits you made to the boot command.

• Type b or press Enter to boot the system from the network.

Become superuser or assume an equivalent role.

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

Remove the diskless client support.

# /usr/sadm/bin/smdiskless delete -- -o host-name:898 -n client-name

Verify that the diskless client support has been removed.

# /usr/sadm/bin/smosservice list -H host-name:898 --

Become superuser or assume an equivalent role.

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

Remove the OS services for the diskless clients.

# /usr/sadm/bin/smosservice delete -H $HOST:$PORT -u root -p $PASSWD -- 
-x instruction-set.all.Solaris_version

Verify that the OS services have been removed.

# /usr/sadm/bin/smosservice list -H host-name:898 --