To install DHCP clients from the network, you must create Vendor category options to pass information that is needed to install the Solaris OS. The following tables describe common DHCP options that you can use to install a DHCP client.
You can use the standard DHCP options that are listed in Table 3–3 to configure and install x86 based systems. These options are not platform specific, and can be used to install the Solaris OS on a variety of x86 based systems. Use these options to install the Solaris 10 release on x86 based systems by using DHCP. For a complete list of standard options, see dhcp_inittab(4).
Table 3–4 lists options that you can use to install Sun client systems. The vendor client classes that are listed in this table determine what classes of client can use the option. Vendor client classes that are listed here are examples only. You should specify client classes that indicate the actual clients in your network that you need to install from the network. See Working With DHCP Options (Task Map) in System Administration Guide: IP Services for information about how to determine a client's vendor client class.
For detailed information on DHCP options, see DHCP Option Information in System Administration Guide: IP Services.
Table 3–3 Values for Standard DHCP Options
Option Name |
Code |
Data Type |
Granularity |
Maximum |
Description |
---|---|---|---|---|---|
BootFile |
N/A |
ASCII |
1 |
1 |
Path to the client's boot file |
BootSrvA |
N/A |
IP address |
1 |
1 |
IP address of boot server |
DNSdmain |
15 |
ASCII |
1 |
0 |
DNS domain name |
DNSserv |
6 |
IP address |
1 |
0 |
List of DNS name servers |
NISdmain |
40 |
ASCII |
1 |
0 |
NIS domain name |
NISservs |
41 |
IP address |
1 |
0 |
IP address of NIS server |
NIS+dom |
64 |
ASCII |
1 |
0 |
NIS+ domain name |
NIS+serv |
65 |
IP address |
1 |
0 |
IP address of NIS+ server |
Router |
3 |
IP address |
1 |
0 |
IP addresses of network routers |
Table 3–4 Values for Creating Vendor Category Options for Solaris Clients
Name |
Code |
Data Type |
Granularity |
Maximum |
Vendor Client Classes * |
Description |
---|---|---|---|---|---|---|
The following Vendor category options are required to enable a DHCP server to support Solaris installation clients. The options are used in the Solaris client's startup scripts. Note – Vendor client classes that are listed here are examples only. You should specify client classes that indicate the actual clients in your network that you need to install from the network. |
||||||
SrootIP4 |
2 |
IP address |
1 |
1 |
SUNW.Sun-Blade-1000, SUNW.Sun-Fire-880, SUNW.i86pc |
IP address of root server |
SrootNM |
3 |
ASCII text |
1 |
0 |
SUNW.Sun-Blade-1000, SUNW.Sun-Fire-880, SUNW.i86pc |
Host name of root server |
SrootPTH |
4 |
ASCII text |
1 |
0 |
SUNW.Sun-Blade-1000, SUNW.Sun-Fire-880, SUNW.i86pc |
Path to the client's root directory on the root server |
SinstIP4 |
10 |
IP address |
1 |
1 |
SUNW.Sun-Blade-1000, SUNW.Sun-Fire-880, SUNW.i86pc |
IP address of JumpStart install server |
SinstNM |
11 |
ASCII text |
1 |
0 |
SUNW.Sun-Blade-1000, SUNW.Sun-Fire-880, SUNW.i86pc |
Host name of install server |
SinstPTH |
12 |
ASCII text |
1 |
0 |
SUNW.Sun-Blade-1000, SUNW.Sun-Fire-880, SUNW.i86pc |
Path to installation image on install server |
The following options can be used by the client startup scripts, but are not required by the scripts. Note – Vendor client classes that are listed here are examples only. You should specify client classes that indicate the actual clients in your network that you need to install from the network. |
||||||
SrootOpt |
1 |
ASCII text |
1 |
0 |
SUNW.Sun-Blade-1000, SUNW.Sun-Fire-880, SUNW.i86pc |
NFS mount options for the client's root file system |
SbootFIL |
7 |
ASCII text |
1 |
0 |
SUNW.Sun-Blade-1000, SUNW.Sun-Fire-880, SUNW.i86pc |
Path to the client's boot file |
SbootRS |
9 |
NUMBER |
2 |
1 |
SUNW.Sun-Blade-1000, SUNW.Sun-Fire-880, SUNW.i86pc |
NFS read size used by standalone boot program when loading the kernel |
SsysidCF |
13 |
ASCII text |
1 |
0 |
SUNW.Sun-Blade-1000, SUNW.Sun-Fire-880, SUNW.i86pc |
Path to sysidcfg file, in the format server:/path |
SjumpsCF |
14 |
ASCII text |
1 |
0 |
SUNW.Sun-Blade-1000, SUNW.Sun-Fire-880, SUNW.i86pc |
Path to JumpStart configuration file in the format server:/path |
16 |
ASCII text |
1 |
0 |
SUNW.Sun-Blade-1000, SUNW.Sun-Fire-880, SUNW.i86pc |
Path to the standalone boot file or path to the WAN boot file. For the standalone boot file, use the following format. tftp://inetboot.sun4u For the WAN boot file, the format is http://host.domain/path-to-file This option can be used to override BootFile and siaddr settings in order to retrieve a standalone boot file. Supported protocols: tftp (inetboot), http (wanboot). For example, use the following format. tftp://inetboot.sun4u |
|
17 |
ASCII text |
1 |
0 |
SUNW.Sun-Blade-1000, SUNW.Sun-Fire-880, SUNW.i86pc |
IP address and port number of the proxy server that is used on your network. This option is needed only when a client is booting across a WAN, and the local network uses a proxy server. For example, use the following format: 198.162.10.5:8080 |
|
The following options are not currently used by the Solaris client startup scripts. You can use them only if you edit the startup scripts. Note – Vendor client classes that are listed here are examples only. You should specify client classes that indicate the actual clients in your network that you need to install from the network. |
||||||
SswapIP4 |
5 |
IP address |
1 |
0 |
SUNW.Sun-Blade-1000, SUNW.Sun-Fire-880, SUNW.i86pc |
IP address of swap server |
SswapPTH |
6 |
ASCII text |
1 |
0 |
SUNW.Sun-Blade-1000, SUNW.Sun-Fire-880, SUNW.i86pc |
Path to the client's swap file on the swap server |
Stz |
8 |
ASCII text |
1 |
0 |
SUNW.Sun-Blade-1000, SUNW.Sun-Fire-880, SUNW.i86pc |
Time zone for client |
Sterm |
15 |
ASCII text |
1 |
0 |
SUNW.Sun-Blade-1000, SUNW.Sun-Fire-880, SUNW.i86pc |
Terminal type |
When you have created the options, you can create macros that include those options. The following table lists sample macros you can create to support Solaris installation for clients.
Table 3–5 Sample Macros to Support Network Installation Clients
Macro Name |
Contains These Options and Macros |
---|---|
Solaris |
SrootIP4, SrootNM, SinstIP4, SinstNM |
sparc |
SrootPTH, SinstPTH |
sun4u |
Solaris and sparc macros |
sun4v |
Solaris and sparc macros |
i86pc |
Solaris macro, SrootPTH, SinstPTH, SbootFIL |
SUNW.i86pc |
i86pc macro Note – The SUNW.i86pc vendor client class is only valid for the Solaris 10 3/05 release and compatible versions. |
SUNW.Sun-Blade-1000 |
sun4u macro, SbootFIL |
SUNW.Sun-Fire-880 |
sun4u macro, SbootFIL |
PXEClient:Arch:00000:UNDI:002001 |
BootSrvA, BootFile |
xxx.xxx.xxx.xxx network address macros |
BootSrvA option could be added to existing network address macros. The value of BootSrvA should indicate the tftboot server. |
01client-MAC-address client-specific macros (for example, 010007E9044ABF) |
BootSrvA, BootFile |
The macro names that are listed in the previous table match the Vendor client classes of the clients that must install from the network. These names are examples of clients you might have on your network. See Working With DHCP Options (Task Map) in System Administration Guide: IP Services for information about determining a client's vendor client class.
You can create these options and macros by using the following methods.
Create the options and macros in DHCP Manager. See Using DHCP Manager to Create Install Options and Macros for instructions about how to create options and macros in DHCP Manager.
Write a script that creates the options and macros by using the dhtadm command. See Writing a Script That Uses dhtadm to Create Options and Macros for information about how to write scripts that create these options and macros.
Note that the total size of the vendor options that are provided to a particular client must not exceed 255 bytes, including the option codes and length information. This is a limitation of the current Solaris DHCP protocol implementation. Generally, you should pass the minimum amount of vendor information needed. You should use short path names in options that require path names. If you create symbolic links to long paths, you can use the shorter link names.