test

System Administration Guide: Basic Administration

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

Starting with the Solaris 10 1/06 release, use this procedure to add a diskless client after you have added OS services.

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

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

    Adds the specified diskless client.

    --

    Identifies that the subcommand arguments start after this point.

    -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=time-zone

    Specifies the time-zone for the diskless client.

    -x locale=locale-name

    Specifies the locale to install for the diskless client.

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

  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 should 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.01ethernet-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 Booting an x86 Based System from the Network.

  5. Verify that the diskless clients were installed. 


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

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

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

This example shows how to add a Solaris 10 x86 based diskless client, mikey1.


rainy-01# /usr/sadm/bin/smdiskless add -H sdts-01-qfe0 -- -o sdts-01-qfe0
-n mikey1 -i 192.168.20.22 -e 00:E0:88:55:33:BC -x os=i386.i86pc.Solaris_10
-x root=/export/root/mikey1 -x swap=/export/swap/mikey1
Loading Tool: com.sun.admin.osservermgr.cli.OsServerMgrCli
from  sdts-01-qfe0
Login to rainy-01-qfe0 as user root was successful.
Download of com.sun.admin.osservermgr.cli.OsServerMgrCli from
rainy-01-qfe0 was successful.

# /usr/sadm/bin/smdiskless list -H mikey1:898 --
Loading Tool: com.sun.admin.osservermgr.cli.OsServerMgrCli from mikey1:898
Login to mikey1 as user root was successful.
Download of com.sun.admin.osservermgr.cli.OsServerMgrCli from mikey1:898 was 
successful.
Platform
--------------------------------------------------------------------------------
i386.i86pc.Solaris_10                                                           
sparc.sun4us.Solaris_10                                                         
sparc.sun4u.Solaris_10                                                          
i386.i86pc.Solaris_9
Example 7–4 x86: 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.