This chapter describes procedures about preconfiguring system information with a naming service or DHCP. This chapter contains the following sections:Choosing a Naming Service Preconfiguring With the Naming Service Preconfiguring System Configuration Information With the DHCP Service (Tasks) You can choose one of the following ways to preconfigure system configuration information. You can add the system configuration information to any of the following.A sysidcfg file on a remote system or disketteThe name_service option in the sysidcfg file automatically sets the naming service during installation of the Solaris OS. This setting overrides SMF services previously setup for site.xml. Therefore, you might need to reset your name service after installation. The naming service database available at your site If your site uses DHCP, you can also preconfigure some system information in the site DHCP server. For more information about how to use a DHCP server to preconfigure system information, see Preconfiguring System Configuration Information With the DHCP Service (Tasks). Use the following table to determine whether to use a sysidcfg file or a naming service database to preconfigure system configuration information.Preconfigurable System Information Preconfigurable With the sysidcfg File? Preconfigurable With the Naming Service? Naming service Yes Yes Domain name Yes No Name server Yes No Network interface Yes No Host name YesBecause this information is system specific, edit the naming service rather than create a different sysidcfg file for each system. Yes Internet Protocol (IP) address YesBecause this information is system specific, edit the naming service rather than create a different sysidcfg file for each system. Yes Netmask Yes No DHCP Yes No IPv6 Yes No Default route Yes No Root password Yes No Security policy Yes No Language (locale) in which to display the install program and desktop Yes Yes, if NIS or NIS+No, if DNS or LDAP Terminal type Yes No Time zone Yes Yes Date and time Yes Yes Web proxy NoYou can configure this information with the Solaris installation program, but not through the sysidcfg file or the naming service. No x86: Monitor type Yes No x86: Keyboard language, keyboard layout Yes No x86: Graphics card, color depth, display resolution, screen size Yes No x86: Pointing device, number of buttons, IRQ level Yes No SPARC: Power Management (autoshutdown)You cannot preconfigure Power Management through the sysidcfg file or the naming service. Preconfiguring Power Management Information contains details. No No The following table provides a high-level overview of the naming service databases that you need to edit and populate to preconfigure system information.System Information to Preconfigure Naming Service Database Host name and Internet Protocol (IP) address hosts Date and time hosts. Specify the timehost alias next to the host name of the system that will provide the date and time for the systems that are being installed. Time zone timezone Netmask netmasks You cannot preconfigure the locale for a system with the DNS or LDAP name service. If you use the NIS or NIS+ name service, follow the procedure below to use your naming service to preconfigure the locale for a system.In order to successfully preconfigure your system locale by using NIS or NIS+, the following requirements must be met:You must boot the system from the network by using the following command:ok boot netYou can use options with this command. See details in Step 2 of theTo Install the Client Over the Network (DVD) procedure. The NIS or NIS+ server must be available to access during the installation. If these requirements are fulfilled, the installer uses the preconfigured settings and does not prompt for the locale during the installation. If either requirement is not fulfilled, the installer prompts for your locale information during the installation. To Preconfigure the Locale Using NIS To Preconfigure the Locale Using NIS+ Become superuser or assume an equivalent role on the name server. Change /var/yp/Makefile to add the locale map. Insert this shell procedure after the last variable.time shell procedure.locale.time: $(DIR)/locale -@if [ -f $(DIR)/locale ]; then \ sed -e "/^#/d" -e s/#.*$$// $(DIR)/locale \ | awk '{for (i = 2; i<=NF; i++) print $$i, $$0}' \ | $(MAKEDBM) - $(YPDBDIR)/$(DOM)/locale.byname; \ touch locale.time; \ echo "updated locale"; \ if [ ! $(NOPUSH) ]; then \ $(YPPUSH) locale.byname; \ echo "pushed locale"; \ else \ : ; \ fi \ else \ echo "couldn't find $(DIR)/locale"; \ fi Find the string all: and, at the end of the list of variables, insert the word locale.all: passwd group hosts ethers networks rpc services protocols \ netgroup bootparams aliases publickey netid netmasks c2secure \ timezone auto.master auto.home locale Near the end of the file, after the last entry of its type, insert the string locale: locale.time on a new line.passwd: passwd.time group: group.time hosts: hosts.time ethers: ethers.time networks: networks.time rpc: rpc.time services: services.time protocols: protocols.time netgroup: netgroup.time bootparams: bootparams.time aliases: aliases.time publickey: publickey.time netid: netid.time passwd.adjunct: passwd.adjunct.time group.adjunct: group.adjunct.time netmasks: netmasks.time timezone: timezone.time auto.master: auto.master.time auto.home: auto.home.time locale: locale.time Save the file. Create the file /etc/locale and make one entry for each domain or specific system: Enter locale domain_name.For example, the following entry specifies that French is the default language that is used in the example.com domain:fr example.comInternational Language Environments Guide contains a list of valid locales. Or, enter locale system_name.The following example specifies that Belgian French is the default locale that is used by a system named myhost:fr_BE myhost Locales are available on the Solaris DVD or Solaris Software - 1 CD. Make the maps:# cd /var/yp; makeSystems that are specified by domain or individually in the locale map are now set up to use the default locale. The default locale that you specified is used during installation and by the desktop after the system is rebooted. If you plan to use the NIS name service in an installation over the network, you need to set up an installation server and add the system as an installation client. For more information, see Chapter 4, Installing From the Network (Overview).If you plan to use the NIS name service in a custom JumpStart installation, you need to create a profile and a rules.ok file. For more information, see Chapter 2, Custom JumpStart (Overview), in Solaris Express Installation Guide: Custom JumpStart and Advanced Installations. For more information about the NIS name service, see Part III, NIS Setup and Administration, in System Administration Guide: Naming and Directory Services (DNS, NIS, and LDAP). The following procedure assumes the NIS+ domain is set up. Setting up the NIS+ domain is documented in the System Administration Guide: Naming and Directory Services (DNS, NIS, and LDAP). Log in to a name server as superuser or as a user in the NIS+ administration group. Create the locale table:# nistbladm -D access=og=rmcd,nw=r -c locale_tbl name=SI,nogw= locale=,nogw= comment=,nogw= locale.org_dir.`nisdefaults -d` Add needed entries to the locale.# nistbladm -a name=namelocale=locale comment=comment locale.org_dir.`nisdefaults -d`nameEither the domain name or a specific system name for which you want to preconfigure a default locale. localeThe locale you want to install on the system and use on the desktop after the system is rebooted. International Language Environments Guide contains a list of valid locales. commentThe comment field. Use double quotation marks to begin and end comments that are longer than one word. Locales are available on the Solaris DVD or Solaris Software - 1 CD. Systems that are specified by domain or individually in the locale table are now set up to use the default locale. The default locale you specified is used during installation and by the desktop after the system is rebooted. If you plan to use the NIS+ name service in an installation over the network, you need to set up an installation server and add the system as an installation client. For more information, see Chapter 4, Installing From the Network (Overview).If you plan to use the NIS+ name service in a custom JumpStart installation, you need to create a profile and a rules.ok file. For more information, see Chapter 2, Custom JumpStart (Overview), in Solaris Express Installation Guide: Custom JumpStart and Advanced Installations. For more information about the NIS+ name service, see System Administration Guide: Naming and Directory Services (NIS+). The Dynamic Host Configuration Protocol (DHCP) enables host systems in a TCP/IP network to be configured automatically for the network as they boot. DHCP uses a client and server mechanism. Servers store and manage configuration information for clients, and provide that information on a client's request. The information includes the client's IP address and information about network services available to the client.A primary benefit of DHCP is its ability to manage IP address assignments through leasing. Leasing allows IP addresses to be reclaimed when not in use and reassigned to other clients. This ability enables a site to use a smaller pool of IP address than would be needed if all clients were assigned a permanent address. You can use DHCP to install the Solaris OS on certain client systems on your network. All SPARC based systems that are supported by the Solaris OS and x86 based systems that meet the hardware requirements for running the Solaris OS can use this feature. The following task map shows the high-level tasks that must be performed to enable clients to obtain installation parameters by using DHCP.Task Description Instructions Set up an install server. Set up a Solaris server to support clients that must install the Solaris OS from the network. Chapter 4, Installing From the Network (Overview) Set up client systems for Solaris installation over the network by using DHCP. Use add_install_client -d to add DHCP network installation support for a class of client (of a certain machine type, for example) or a particular client ID. Using Solaris DVD:Adding Systems to Be Installed From the Network With a DVD ImageUsing Solaris CD:Adding Systems to Be Installed From the Network With a CD Imageadd_install_client1M Prepare your network to use the DHCP service. Decide how you want to configure your DHCP server. Chapter 15, Planning for DHCP Service (Tasks), in System Administration Guide: IP Services Configure the DHCP server. Use DHCP Manager to configure your DHCP server Chapter 16, Configuring the DHCP Service (Tasks), in System Administration Guide: IP Services Create DHCP options for installation parameters and macros that include the options. Use DHCP Manager or dhtadm to create new Vendor options and macros that the DHCP server can use to pass installation information to the clients. Creating DHCP Options and Macros for Solaris Installation Parameters When you add clients with the add_install_client -d script on the install server, the script reports DHCP configuration information to standard output. This information can be used when you create the options and macros that are needed to pass network installation information to clients.You can customize the options and macros in your DHCP service to perform the following types of installations.Class-specific installations – You can instruct the DHCP service to perform a network installation for all clients of a specific class. For example, you can define a DHCP macro that performs the same installation on all Sun Blade systems on the network. Use the output of the add_install_client -d command to set up a class-specific installation. Network-specific installations – You can instruct the DHCP service to perform a network installation for all clients in a specific network. For example, you can define a DHCP macro that performs the same installation on all systems in the 192.168.2 network. Client-specific installations –You can instruct the DHCP service to perform a network installation for a client with a specific Ethernet address. For example, you can define a DHCP macro that performs a specific installation on the client with the Ethernet address 00:07:e9:04:4a:bf. Use the output of the add_install_client -d -e ethernet_address command to set up a client-specific installation. For more information on setting up clients to use a DHCP server for a network installation, see the following procedures.For network installations that use DVD media, see Adding Systems to Be Installed From the Network With a DVD Image. For network installations that use CD media, see Adding Systems to Be Installed From the Network With a CD Image. 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. For a complete list of standard options, see dhcp_inittab4. 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.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 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.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.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 SbootURI 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.sun4uFor the WAN boot file, the format ishttp://host.domain/path-to-fileThis 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 SHTTPproxy 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.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.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 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. You can use DHCP Manager to create the options that are listed in Table 3–4 and the macros that are listed in Table 3–5.Perform the following tasks before you create DHCP macros for your installation.Add the clients that you want to install with DHCP as install clients of your network installation server. For information about how to add a client to an install server, see Chapter 4, Installing From the Network (Overview). Configure your DHCP server. If you have not configured your DHCP server, see Chapter 15, Planning for DHCP Service (Tasks), in System Administration Guide: IP Services. Become superuser or assume an equivalent role on the DHCP server system. Start the DHCP Manager.# /usr/sadm/admin/bin/dhcpmgr &The DHCP Manager window is displayed. Select the Options tab in DHCP Manager. Choose Create from the Edit menu.The Create Option panel opens. Type the option name for the first option, then type values appropriate for that option.Use the output of the add_install_client command , Table 3–3, and Table 3–4 to check the option names and values for options you must create. Notice that the vendor client classes are only suggested values. You should create classes to indicate the actual client types that need to obtain Solaris installation parameters from the DHCP service. 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. Click OK when you have entered all the values. In the Options tab, select the option you just created. Select Duplicate from the Edit menu.The Duplicate Option panel opens. Type the name of another option, then modify other values appropriately.The values for code, data type, granularity, and maximum are most likely to need modification. See Table 3–3 and Table 3–4 for the values. Repeat Step 7 through Step 9 until you have created all the options.You can now create macros to pass the options to network installation clients, as explained in the following procedure.You do not need to add these options to a Solaris client's /etc/dhcp/inittab file because they are already included in that file. Perform the following tasks before you create DHCP macros for your installation.Add the clients that you want to install with DHCP as install clients of your network installation server. For information about how to add a client to an install server, see Chapter 4, Installing From the Network (Overview). Configure your DHCP server. If you have not configured your DHCP server, see Chapter 15, Planning for DHCP Service (Tasks), in System Administration Guide: IP Services. Create the DHCP options that you want to use in your macro. For instructions about how to create DHCP options, see How to Create Options to Support Solaris Installation (DHCP Manager). Select the Macros tab in DHCP Manager. Choose Create from the Edit menu.The Create Macro panel opens. Type the name of a macro.See Table 3–5 for macro names you might use. Click the Select button.The Select Option panel opens. Select Vendor in the Category list.The Vendor options you created are listed. Select an option you want to add to the macro and click OK. Type a value for the option.See Table 3–3 and Table 3–4 for the option's data type and refer to the information that add_install_client -d reports. Repeat Step 6 through Step 7 for each option you want to include.To include another macro, type Include as the option name and type the macro name as the option value. Click OK when the macro is complete. If you plan to use DHCP in an installation over the network, you need to set up an installation server and add the system as an installation client. For more information, see Chapter 4, Installing From the Network (Overview).If you plan to use DHCP in a WAN boot installation, you need to perform additional tasks. For more information, see Chapter 9, WAN Boot (Overview).If you plan to use DHCP in a custom JumpStart installation, you need to create a profile and a rules.ok file. For more information, see Chapter 2, Custom JumpStart (Overview), in Solaris Express Installation Guide: Custom JumpStart and Advanced Installations. For more information about DHCP, see Part II, DHCP, in System Administration Guide: IP Services. You can create a Korn shell script by adapting the example in Example 3–1 to create all the options listed in Table 3–3 and Table 3–4 and some useful macros. Be sure to change all IP addresses and values contained in quotes to the correct IP addresses, server names, and paths for your network. You should also edit the Vendor= key to indicate the class of clients you have. Use the information that add_install_client -d reports to obtain the data that you need to adapt the script. # Load the Solaris vendor specific options. We'll start out supporting # the Sun-Blade-1000, Sun-Fire-880, and i86 platforms. Note that the # SUNW.i86pc option only applies for the Solaris 10 3/05 release. # Changing -A to -M would replace the current values, rather than add them. dhtadm -A -s SrootOpt -d \ 'Vendor=SUNW.Sun-Blade-1000 SUNW.Sun-Fire-880 SUNW.i86pc,1,ASCII,1,0' dhtadm -A -s SrootIP4 -d \ 'Vendor=SUNW.Sun-Blade-1000 SUNW.Sun-Fire-880 SUNW.i86pc,2,IP,1,1' dhtadm -A -s SrootNM -d \ 'Vendor=SUNW.Sun-Blade-1000 SUNW.Sun-Fire-880 SUNW.i86pc,3,ASCII,1,0' dhtadm -A -s SrootPTH -d \ 'Vendor=SUNW.Sun-Blade-1000 SUNW.Sun-Fire-880 SUNW.i86pc,4,ASCII,1,0' dhtadm -A -s SswapIP4 -d \ 'Vendor=SUNW.Sun-Blade-1000 SUNW.Sun-Fire-880 SUNW.i86pc,5,IP,1,0' dhtadm -A -s SswapPTH -d \ 'Vendor=SUNW.Sun-Blade-1000 SUNW.Sun-Fire-880 SUNW.i86pc,6,ASCII,1,0' dhtadm -A -s SbootFIL -d \ 'Vendor=SUNW.Sun-Blade-1000 SUNW.Sun-Fire-880 SUNW.i86pc,7,ASCII,1,0' dhtadm -A -s Stz -d \ 'Vendor=SUNW.Sun-Blade-1000 SUNW.Sun-Fire-880 SUNW.i86pc,8,ASCII,1,0' dhtadm -A -s SbootRS -d \ 'Vendor=SUNW.Sun-Blade-1000 SUNW.Sun-Fire-880 SUNW.i86pc,9,NUMBER,2,1' dhtadm -A -s SinstIP4 -d \ 'Vendor=SUNW.Sun-Blade-1000 SUNW.Sun-Fire-880 SUNW.i86pc,10,IP,1,1' dhtadm -A -s SinstNM -d \ 'Vendor=SUNW.Sun-Blade-1000 SUNW.Sun-Fire-880 SUNW.i86pc,11,ASCII,1,0' dhtadm -A -s SinstPTH -d \ 'Vendor=SUNW.Sun-Blade-1000 SUNW.Sun-Fire-880 SUNW.i86pc,12,ASCII,1,0' dhtadm -A -s SsysidCF -d \ 'Vendor=SUNW.Sun-Blade-1000 SUNW.Sun-Fire-880 SUNW.i86pc,13,ASCII,1,0' dhtadm -A -s SjumpsCF -d \ 'Vendor=SUNW.Sun-Blade-1000 SUNW.Sun-Fire-880 SUNW.i86pc,14,ASCII,1,0' dhtadm -A -s Sterm -d \ 'Vendor=SUNW.Sun-Blade-1000 SUNW.Sun-Fire-880 SUNW.i86pc,15,ASCII,1,0' dhtadm -A -s SbootURI -d \ 'Vendor=SUNW.Sun-Blade-1000 SUNW.Sun-Fire-880 SUNW.i86pc,16,ASCII,1,0' dhtadm -A -s SHTTPproxy -d \ 'Vendor=SUNW.Sun-Blade-1000 SUNW.Sun-Fire-880 SUNW.i86pc,17,ASCII,1,0' # Load some useful Macro definitions. # Define all Solaris-generic options under this macro named Solaris. dhtadm -A -m Solaris -d \ ':SrootIP4=10.21.0.2:SrootNM="blue2":SinstIP4=10.21.0.2:SinstNM="red5":' # Define all sparc-platform specific options under this macro named sparc. dhtadm -A -m sparc -d \ ':SrootPTH="/export/sparc/root":SinstPTH="/export/sparc/install":' # Define all sun4u architecture-specific options under this macro named sun4u. # (Includes Solaris and sparc macros.) dhtadm -A -m sun4u -d ':Include=Solaris:Include=sparc:' # Solaris on IA32-platform-specific parameters are under this macro named i86pc. # Note that this macro applies only for the Solaris 10 3/05 release. dhtadm -A -m i86pc -d \ ':Include=Solaris:SrootPTH="/export/i86pc/root":SinstPTH="/export/i86pc/install"\ :SbootFIL="/platform/i86pc/kernel/unix":' # Solaris on IA32 machines are identified by the "SUNW.i86pc" class. All # clients identifying themselves as members of this class will see these # parameters in the macro called SUNW.i86pc, which includes the i86pc macro. # Note that this class only applies for the Solaris 10 3/05 release. dhtadm -A -m SUNW.i86pc -d ':Include=i86pc:' # Sun-Blade-1000 platforms identify themselves as part of the # "SUNW.Sun-Blade-1000" class. # All clients identifying themselves as members of this class # will see these parameters. dhtadm -A -m SUNW.Sun-Blade-1000 -d \ ':SbootFIL="/platform/sun4u/kernel/sparcv9/unix":\ Include=sun4u:' # Sun-Fire-880 platforms identify themselves as part of the "SUNW.Sun-Fire-880" class. # All clients identifying themselves as members of this class will see these parameters. dhtadm -A -m SUNW.Sun-Fire-880 -d \ ':SbootFIL="/platform/sun4u/kernel/sparcv9/unix":Include=sun4u:' # Add our boot server IP to each of the network macros for our topology served by our # DHCP server. Our boot server happens to be the same machine running our DHCP server. dhtadm -M -m 10.20.64.64 -e BootSrvA=10.21.0.2 dhtadm -M -m 10.20.64.0 -e BootSrvA=10.21.0.2 dhtadm -M -m 10.20.64.128 -e BootSrvA=10.21.0.2 dhtadm -M -m 10.21.0.0 -e BootSrvA=10.21.0.2 dhtadm -M -m 10.22.0.0 -e BootSrvA=10.21.0.2 # Make sure we return host names to our clients. dhtadm -M -m DHCP-servername -e Hostname=_NULL_VALUE_ # Create a macro for PXE clients that want to boot from our boot server. # Note that this macro applies for the Solaris 10 3/05 release. dhtadm -A -m PXEClient:Arch:00000:UNDI:002001 -d \ :BootFile=nbp.i86pc:BootSrvA=10.21.0.2: # Create a macro for PXE clients that want to boot from our boot server. # Note that this macro applies for the Solaris 10 2/06 release. dhtadm -A -m PXEClient:Arch:00000:UNDI:002001 -d \ :BootFile=i86pc:BootSrvA=10.21.0.2: # Create a macro for the x86 based client with the Ethernet address 00:07:e9:04:4a:bf # to install from the network by using PXE. dhtadm -A -m 010007E9044ABF -d :BootFile=010007E9044ABF:BootSrvA=10.21.0.2: # The client with this MAC address is a diskless client. Override the root settings # which at the network scope setup for Install with our client's root directory. dhtadm -A -m 0800201AC25E -d \ ':SrootIP4=10.23.128.2:SrootNM="orange-svr-2":SrootPTH="/export/root/10.23.128.12":' As superuser, execute dhtadm in batch mode. Specify the name of the script to add the options and macros to your dhcptab. For example, if your script is named netinstalloptions, type the following command.# dhtadm -B netinstalloptionsClients that have vendor client classes that are listed in the Vendor= string can now use DHCP to install over the network.For more information about how to use the dhtadm command, see dhtadm1M. For more information about the dhcptab file, see dhcptab4.