Part I Planning to Install Over the Network

This part describes how to plan your installation over the network.

Chapter 1 Where to Find Solaris Installation Planning Information

This book describes how to install the Solaris OS remotely over a local area network or a wide area network.

This chapter describes the preparations for completing a successful installation. Many preparatory tasks are common to all Solaris installations, and so are described in one master planning document.

Where to Find Planning and System Requirement Information

The Solaris 10 5/09 Installation Guide: Planning for Installation and Upgrade provides system requirements and high-level planning information, such as planning guidelines for file systems, and upgrade planning and much more. The following list describes the chapters in the planning book.

Chapter 2 Preconfiguring System Configuration Information (Tasks)

This chapter describes how to preconfigure system information by using the sysidcfg file. Preconfiguration can help you to avoid being prompted for this information when you install the Solaris OS. This chapter also describes how to preconfigure Power Management^TM information. This chapter contains the following sections:

• Advantages of Preconfiguring System Configuration Information

• Preconfiguring With the sysidcfg File

• SPARC: Preconfiguring Power Management Information

Advantages of Preconfiguring System Configuration Information

The installation methods require configuration information about a system, such as peripheral devices, host name, Internet Protocol (IP) address, and naming service. Before the installation tools prompt you for configuration information, they check for configuration information that is stored elsewhere.

You can choose one of the following ways to preconfigure system information.

For more detailed information about choosing a preconfiguration method, see Choosing a Naming Service.

When the Solaris installation program or the custom JumpStart^TM installation program detects preconfigured system information, the installation program does not prompt you to enter the information. For example, you have several systems and you do not want a time zone prompt every time you install the current Solaris release on one of the systems. You can specify the time zone in the sysidcfg file or the naming service databases. When you install the current Solaris release, the installation program does not prompt you to type a time zone.

Preconfiguring With the sysidcfg File

You can specify a set of keywords in the sysidcfg file to preconfigure a system. The keywords are described in sysidcfg File Keywords.

The name_service keyword in the sysidcfg file automatically sets the naming service during installation of the Solaris OS. This setting overrides SMF services previously set up for site.xml. Therefore, you might need to reset your name service after installation.

You must create a unique sysidcfg file for every system that requires different configuration information. You can use the same sysidcfg file to preconfigure the time zone on a set of systems if you want all the systems to be assigned the same time zone. However, if you want to preconfigure a different root (superuser) password for each of those systems, you need to create a unique sysidcfg file for each system.

You can place the sysidcfg file in one of the following.

You can use the naming service or DHCP to preconfigure your system. For information, see Chapter 3, Preconfiguring With a Naming Service or DHCP.

To Create a sysidcfg Configuration File

1. Create a file called sysidcfg in a text editor with the keywords you want.

2. Make the sysidcfg file available to clients by using one of the locations described at Table 2–2.

Example 2–1 SPARC: sysidcfg File

The following is an example of a sysidcfg file for a SPARC based system. The host name, IP address, and netmask of this system have been preconfigured by editing the naming service. Because all of the system configuration information is preconfigured in this file, you can use a custom JumpStart profile to perform a custom JumpStart installation. In this example, the NFSv4 domain name is automatically derived from the naming service. Because the service_profile keyword is not included in this example, configuration is not altered for the network services during installation.

keyboard=US-English
system_locale=en_US
timezone=US/Central
terminal=sun-cmd
timeserver=localhost
name_service=NIS {domain_name=marquee.central.example.com
                  name_server=nmsvr2(172.31.112.3)}
nfs4_domain=dynamic
root_password=m4QPOWNY
network_interface=hme0 {hostname=host1 
                       default_route=172.31.88.1 
                       ip_address=172.31.88.210 
                       netmask=255.255.0.0 
                       protocol_ipv6=no}
security_policy=kerberos {default_realm=example.com 
                          admin_server=krbadmin.example.com 
                          kdc=kdc1.example.com, 
                          kdc2.example.com}

Example 2–2 x86: sysidcfg File

The following sample sysidcfg file is for a group of x86 based systems. In this example, the NFSv4 domain name is specified to be example.com. This custom name overrides the default domain name. Also in this example, the network services are disabled or restricted to local connections only.

keyboard=US-English
timezone=US/Central
timeserver=timehost1
terminal=ibm-pc
service_profile=limited_net

name_service=NIS {domain_name=marquee.central.example.com
                  name_server=nmsvr2(172.25.112.3)}
nfs4_domain=example.com
root_password=URFUni9

Example 2–3 sysidcfg File for Configuring Multiple Interfaces

In the following sample sysidcfg file, configuration information is specified for both the eri0 and eri1 network interfaces. The eri0 interface is configured as the primary network interface, and eri1 is configured as a secondary network interface. In this example, the NFSv4 domain name is automatically derived from the naming service.

timezone=US/Pacific
system_locale=C
terminal=xterms
timeserver=localhost
network_interface=eri0 {primary
                        hostname=host1
                        ip_address=192.168.2.7
                        netmask=255.255.255.0
                        protocol_ipv6=no
                        default_route=192.168.2.1}

network_interface=eri1 {hostname=host1-b
                        ip_address=192.168.3.8
                        netmask=255.255.255.0
                        protocol_ipv6=no
                        default_route=NONE}
root_password=JE2C35JGZi4B2
security_policy=none
name_service=NIS {domain_name=domain.example.com
                  name_server=nis-server(192.168.2.200)}
nfs4_domain=dynamic

Continuing the Installation

If you plan to use the sysidcfg file 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 sysidcfg file in a WAN boot installation, you need to perform additional tasks. For more information, see Chapter 10, WAN Boot (Overview).

If you plan to use the sysidcfg file 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 10 5/09 Installation Guide: Custom JumpStart and Advanced Installations.

See Also

For more information about the sysidcfg file, see the man page sysidcfg(4).

Syntax Rules for the sysidcfg File

You can use two types of keywords in the sysidcfg file: independent and dependent. Dependent keywords are guaranteed to be unique only within independent keywords. A dependent keyword exists only when it is identified with its associated independent keyword.

In this example, name_service is the independent keyword, while domain_name and name_server are the dependent keywords:

name_service=NIS {domain_name=marquee.central.example.com
name_server=connor(192.168.112.3)}

pointer=MS-S
display=ati {size=15-inch}

TIMEZONE=US/Central
terminal=sun-cmd

name_service=NIS 
       {domain_name=marquee.central.example.com
        name_server=connor(192.168.112.3)}

network_interface='none'

name_service=NIS
name_service=DNS

sysidcfg File Keywords

Table 2–3 lists the keywords you can use to configure system information in the sysidcfg file.

The following sections describe the keywords that you can use in the sysidcfg file.

keyboard Keyword

The sysidkdb tool configures your USB language and its corresponding keyboard layout.

The following procedure occurs:

• If the keyboard is self-identifying, the keyboard language and layout automatically configures during installation.

• If the keyboard is not self-identifying, the sysidkdb tool provides you with a list of supported keyboard layouts during installation, so that you can select a layout for keyboard configuration.

  ---

  Note –

  PS/2 keyboards are not self-identifying. You will be asked to select the keyboard layout during the installation.

  ---

You can configure the keyboard language and its corresponding keyboard layout information by using the keyboard keyword. Each language has its own keyboard layout. Use the following syntax to select a language and its corresponding layout.

keyboard=keyboard_layout

For example, this entry sets the keyboard language and its corresponding keyboard layout for the German language:

keyboard=German

The value provided for keyboard_layout must be a valid value. Otherwise, an interactive response is required during installation. The valid keyboard_layout strings are defined in the /usr/share/lib/keytables/type_6/kbd_layouts file.

Previously, the USB keyboard assumed a self-identifying value of 1 during the installation. Therefore, all of the keyboards that were not self-identifying always configured for a U.S. English keyboard layout during installation.

If the keyboard is not self-identifying and you want to prevent being prompted during your JumpStart installation, select the keyboard language in your sysidcfg file. For JumpStart installations, the default is for the U.S. English language. To select another language and its corresponding keyboard layout, set the keyboard entry in your sysidcfg file as in the example provided above.

For further information, see the sysidcfg(4) and sysidtool(1M) man pages.

name_service Keyword

You can use the name_service keyword to configure the naming service, the domain name, and the name server for the system. The following sample shows the general syntax for the name_service keyword.

name_service=name-service {domain_name=domain-name 
                                 name_server=name-server
                                 optional-keyword=value}

Choose only one value for name_service. Include all or none of the domain_name, name_server, or optional keywords, as needed. If no keywords are used, omit the curly braces {}.

The name_service option in the sysidcfg file automatically sets the naming service during installation of the Solaris OS. This setting overrides SMF services that were previously set up for site.xml. Therefore, you might need to reset your name service after installation.

The following sections describe the keyword syntax to configure the system to use a specific naming service.

NIS Syntax for name_service Keyword

Use the following syntax to configure the system to use the NIS naming service.

name_service=NIS {domain_name=domain-name 
                   name_server=hostname(ip-address)}

domain-name

Specifies the domain name

hostname

Specifies the host name of the name server

ip-address

Specifies the IP address of the name server

Example 2–4 Specifying a NIS Server With the name_service Keyword

The following example specifies a NIS server with the domain name west.example.com. The server's host name is timber, and the server IP address is 192.168.2.1.

name_service=NIS {domain_name=west.example.com 
                  name_server=timber(192.168.2.1)}

For more information about the NIS name service, see System Administration Guide: Naming and Directory Services (DNS, NIS, and LDAP).

NIS+ Syntax for name_service Keyword

Use the following syntax to configure the system to use the NIS name service.

name_service=NIS+ {domain_name=domain-name 
                   name_server=hostname(ip-address)}

domain-name

Specifies the domain name

hostname

Specifies the host name of the name server

ip-address

Specifies the IP address of the name server

Example 2–5 Specifying a NIS+ Server With the name_service Keyword

The following example specifies a NIS+ server with the domain name west.example.com. The server's host name is timber, and the server IP address is 192.168.2.1.

name_service=NIS+ {domain_name=west.example.com 
                   name_server=timber(192.168.2.1)}

For more information about the NIS+ name service, see System Administration Guide: Naming and Directory Services (NIS+).

DNS Syntax for name_service Keyword

Use the following syntax to configure the system to use DNS.

name_service=DNS {domain_name=domain-name 
                  name_server=ip-address,ip-address,ip-address
                  search=domain-name,domain-name,domain-name,
                  domain-name,domain-name,domain-name} 

domain_name=domain-name

Specifies the domain name.

name_server=ip-address

Specifies the IP address of the DNS server. You can specify up to three IP addresses as values for the name_server keyword.

search=domain-name

(Optional) Specifies additional domains to search for naming service information. You can specify up to six domain names to search. The total length of each search entry cannot exceed 250 characters.

Example 2–6 Specifying a DNS Server With the name_service Keyword

The following example specifies a DNS server with the domain name west.example.com. The server IP addresses are 10.0.1.10 and 10.0.1.20. example.com and east.example.com are listed as additional domains to search for naming service information.

name_service=DNS {domain_name=west.example.com 
                  name_server=10.0.1.10,10.0.1.20 
                  search=example.com,east.example.com}

For more information about the DNS name service, see System Administration Guide: Naming and Directory Services (DNS, NIS, and LDAP).

LDAP Syntax for name_service Keyword

Use the following syntax to configure the system to use LDAP.

name_service=LDAP {domain_name=domain_name
                   profile=profile_name profile_server=ip_address 
                   proxy_dn="proxy_bind_dn" proxy_password=password}

domain_name

Specifies the domain name of the LDAP server.

profile_name

Specifies the name of the LDAP profile you want to use to configure the system.

ip_address

Specifies the IP address of the LDAP profile server.

proxy_bind_dn

(Optional) Specifies the proxy bind distinguished name. You must enclose the proxy_bind_dn value in double quotes.

password

(Optional) Specifies the client proxy password.

Example 2–7 Specifying an LDAP Server With the name_service Keyword

The following example specifies an LDAP server with the following configuration information.

• The domain name is west.example.com.

• The installation program uses the LDAP profile that is named default to configure the system.

• The IP address of the LDAP server is 172.31.2.1.

• The proxy bind distinguished name includes the following information.

  • The common name for the entry is proxyagent.

  • The organizational unit is profile.

  • The proxy domain includes the west, example, and com domain components.

• The proxy password is password.

name_service=LDAP {domain_name=west.example.com 
                   profile=default 
                   profile_server=172.31.2.1 
                   proxy_dn="cn=proxyagent,ou=profile,
                   dc=west,dc=example,dc=com" 
                   proxy_password=password}

For more information about how to use LDAP, see System Administration Guide: Naming and Directory Services (DNS, NIS, and LDAP).

network_interface Keyword

Use the network_interface keyword to perform the following tasks.

• Specify a host name

• Specify an IP address

• Specify the default router address

• Specify a netmask value

• Use DHCP to configure the network interface

• Enable IPv6 on the network interface

The following sections describe how to use the network_interface keyword to configure the system interfaces.

Syntax for Nonnetworked Systems

To turn off networking for the system, set the network_interface value to none. For example:

network_interface=none

Syntax for Configuring a Single Interface

You can use the network_interface keyword to configure a single interface in the following ways.

• With DHCP – You can use a DHCP server on your network to configure the network interface. For more information on how to use a DHCP server during your installation, see Preconfiguring System Configuration Information With the DHCP Service (Tasks).

  To use the DHCP server to configure a single interface on the system, use the following syntax for the network_interface keyword.

  network_interface=PRIMARY or value {dhcp protocol_ipv6=yes-or-no}

  PRIMARY

  Instructs the installation program to configure the first up, non-loopback interface that is found on the system. The order is the same as the order that is displayed with the ifconfig command. If no interfaces are up, then the first non-loopback interface is used. If no non-loopback interfaces are found, then the system is nonnetworked.

  value

  Instructs the installation program to configure a specific interface, such as hme0 or eri1.

  protocol_ipv6=yes-or-no

  Instructs the installation program to configure the system to use either IPv6 or to not use IPv6.

  For WAN boot installations, you must set the value of protocol_ipv6=no.

• Without DHCP – If you do not want to use DHCP to configure the network interface, you can specify the configuration information in the sysidcfg file. To instruct the installation program to configure a single interface on the system without using DHCP, use the following syntax.

  network_interface=PRIMARY or value {hostname=host_name default_route=ip_address ip_address=ip_address netmask=netmask protocol_ipv6=yes_or_no}

  PRIMARY

  Instructs the installation program to configure the first up, non-loopback interface that is found on the system. The order is the same as the order that is displayed with the ifconfig command. If no interfaces are up, then the first non-loopback interface is used. If no non-loopback interfaces are found, then the system is not networked.

  ---

  Note –

  Do not use the PRIMARY keyword value if you want to configure multiple interfaces.

  ---

  value

  Instructs the installation program to configure a specific interface, such as hme0 or eri1.

  hostname=host_name

  (Optional) Specifies the host name of the system.

  default_route=ip_address or NONE

  (Optional) Specifies the IP address of the default router. If you want the installation program to detect the router by using the ICMP router discovery protocol, omit this keyword.

  ---

  Note –

  If the installation program cannot detect the router, you are prompted for the router information during the installation.

  ---

  ip_address=ip_address

  (Optional) Specifies the IP address of the system.

  netmask=netmask

  (Optional) Specifies the netmask value for the system.

  protocol_ipv6=yes_or_no

  (Optional) Instructs the installation program to configure the system to either use IPv6 or to not use IPv6.

  ---

  Note –

  To perform an unattended custom JumpStart installation, you must specify a value for the protocol_ipv6 keyword.

  For WAN boot installations, you must set the value of protocol_ipv6=no.

  ---

  Include any combination or none of the hostname, ip_address, and netmask keywords, as needed. If you do not use any of these keywords, omit the curly braces ({}).

Example 2–8 Configuring a Single Interface By Using DHCP With the network_interface Keyword

The following example instructs the installation program to use DHCP to configure the eri0 network interface. IPv6 support is not enabled.

network_interface=eri0 {dhcp protocol_ipv6=no}

Example 2–9 Configuring a Single Interface By Specifying Configuration Information With the network_interface Keyword

The following example configures the interface eri0 with the following settings.

• The host name is set to host1.

• The IP address is set to 172.31.88.100.

• The netmask is set to 255.255.255.0.

• IPv6 support is not enabled on the interface.

network_interface=eri0 {hostname=host1 ip_address=172.31.88.100
                        netmask=255.255.255.0 protocol_ipv6=no}

Syntax for Configuring Multiple Interfaces

You can configure multiple network interfaces in your sysidcfg file. For each interface that you want to configure, include a network_interface entry in the sysidcfg file.

You can use the network_interface keyword to configure multiple interfaces in the following ways.

• With DHCP – You can use a DHCP server on your network to configure a network interface. For more information on how to use a DHCP server during your installation, see Preconfiguring System Configuration Information With the DHCP Service (Tasks).

  To use the DHCP server to configure a network interface on the system, use the following syntax for the network_interface keyword.

  network_interface=value {primary dhcp protocol_ipv6=yes-or-no}

  value

  Instructs the installation program to configure a specific interface, such as hme0 or eri1.

  primary

  (Optional) Specifies value as the primary interface.

  protocol_ipv6=yes-or-no

  Instructs the installation program to configure the system to either use IPv6 or to not use IPv6.

  ---

  Note –

  For WAN boot installations, you must set the value of protocol_ipv6=no.

  ---

• Without DHCP – If you do not want to use DHCP to configure the network interface, you can specify the configuration information in the sysidcfg file. To instruct the installation program to configure multiple interfaces without using DHCP, use the following syntax.

  network_interface=value {primary hostname=host_name default_route=ip_address or NONE ip_address=ip_address netmask=netmask protocol_ipv6=yes_or_no}

  value

  Instructs the installation program to configure a specific interface, such as hme0 or eri1.

  primary

  (Optional) Specifies value as the primary interface.

  hostname=host_name

  (Optional) Specifies the host name of the system.

  default_route=ip_address or NONE

  (Optional) Specifies the IP address of the default router. If you want the installation program to detect the router by using the ICMP router discovery protocol, omit this keyword.

  If you configure multiple interfaces in the sysidcfg file, set default_route=NONE for each secondary interface that does not use a static default route.

  ---

  Note –

  If the installation program cannot detect the router, you are prompted for the router information during the installation.

  ---

  ip_address=ip_address

  (Optional) Specifies the IP address of the system.

  netmask=netmask

  (Optional) Specifies the netmask value for the system.

  protocol_ipv6=yes_or_no

  (Optional) Instructs the installation program to configure the system to either use IPv6 or to not use IPv6.

  ---

  Note –

  To perform an unattended custom JumpStart installation, you must specify a value for the protocol_ipv6 keyword.

  For WAN boot installations, you must set the value of protocol_ipv6=no.

  ---

  Include any combination or none of the hostname, ip_address, and netmask keywords, as needed. If you do not use any of these keywords, omit the curly braces ({}).

In the same sysidcfg file, you can use DHCP to configure certain interfaces, while also specifying the configuration information for other interfaces in the sysidcfg file.

Example 2–10 Configuring Multiple Interfaces With the network_interface Keyword

In the following example, the network interfaces eri0 and eri1 are configured in the following way.

• eri0 is configured by using the DHCP server. IPv6 support is not enabled on eri0.

• eri1 is the primary network interface. The host name is set to host1, and the IP address is set to 172.31.88.100. The netmask is set to 255.255.255.0. IPv6 support is not enabled on eri1.

network_interface=eri0 {dhcp protocol_ipv6=no}
network_interface=eri1 {primary hostname=host1 
                        ip_address=172.146.88.100
                        netmask=255.255.255.0 
                        protocol_ipv6=no}

nfs4_domain Keyword

To prevent being asked to specify an NFSv4 domain name during installation, use the nfs4_domain keyword in the sysidcfg file. This keyword suppresses selection of a domain name during the installation process. Use the following syntax:

nfs4_domain=dynamic or custom_domain_name

dynamic

This reserved keyword dynamically derives the NFSv4 domain name, based on naming services configuration. For example:

nfs4_domain=dynamic

This example enables the domain name to be derived by the naming service.

The reserved keyword, dynamic, is not case sensitive.

---

Note –

By default, NFSv4 uses a domain name that is automatically derived from the system's naming services. This domain name is sufficient for most configurations. In a few cases, mount points that cross domain boundaries can cause files to appear to be owned by “nobody” because no common domain name exists. To prevent this situation, you can override the default domain name and select a custom domain name.

---

custom_domain_name

This value overrides the default domain name.

This value must be a valid custom domain name. A valid domain name is composed of a combination of alphanumeric characters, dots, underscores, and dashes only. The first character must be an alphabetical character. For example:

nfs4_domain=example.com

This example sets the value that is used by the nfsmapid daemon to be example.com. This selection overrides the default domain name.

In previous releases, scripts enabled users to avoid being prompted for the NFSv4 domain name during installation.

For JumpStart installations in the Solaris 10 OS, you could use the workaround JumpStart sample script, set_nfs4_domain, to suppress the NFSv4 prompt during installation. This script is no longer required. Use the sysidcfg keyword, nfs4_domain, instead.

In prior releases, the /etc/.NFS4inst_state.domain file was created by the sysidnfs4 program. This file would suppress the prompt for an NFSv4 domain name during installation. This file is no longer created. Use the sysidcfg keyword, nfs4_domain, instead.

root_password Keyword

You can specify the root password to the system in the sysidcfg file. To specify the root password, use the root_password keyword with the following syntax.

root_password=encrypted-password

encrypted-password is the encrypted password as it appears in the /etc/shadow file.

security_policy Keyword

You can use the security_policy keyword in your sysidcfg file to configure your system to use the Kerberos network authentication protocol. If you want to configure the system to use Kerberos, use the following syntax.

security_policy=kerberos {default_realm=FQDN 
                          admin_server=FQDN kdc=FQDN1, FQDN2, FQDN3}

FQDN specifies the fully qualified domain name of the Kerberos default realm, the administration server, or key distribution center (KDC). You must specify at least one, but no more than three, key distribution centers.

If you do not want to set the security policy for the system, set security_policy=NONE.

For more information about the Kerberos network authentication protocol, see System Administration Guide: Security Services.

Example 2–11 Configuring the System to Use Kerberos With the security_policy Keyword

This example configures the system to use Kerberos with the following information.

• The Kerberos default realm is example.com.

• The Kerberos administration server is krbadmin.example.com.

• The two key distribution centers are kdc1.example.com and kdc2.example.com.

security_policy=kerberos 
                {default_realm=example.COM 
                 admin_server=krbadmin.example.com 
                 kdc=kdc1.example.com, 
                 kdc2.example.com}

service_profile Keyword

You can use the service_profile keyword to install a more secure system by restricting network services. This security option is available only for initial installations. An upgrade maintains all previously set services.

Use one of the following syntaxes to set this keyword.

service_profile=limited_net

service_profile=open

limited_net specifies that all network services, except for Secure Shell, are either disabled or constrained to respond to local requests only. After installation, any individual network service can be enabled by using the svcadm and svccfg commands.

open specifies that no network service changes are made during installation.

If the service_profile keyword is not present in the sysidcfg file, no changes are made to the status of the network services during installation.

The network services can be enabled after installation by using the netservices open command or by enabling individual services by using SMF commands. See Revising Security Settings After Installation in Solaris 10 5/09 Installation Guide: Planning for Installation and Upgrade.

For further information about limiting network security during installation, see Planning Network Security in Solaris 10 5/09 Installation Guide: Planning for Installation and Upgrade. See also the following man pages.

• netservices(1M)

• svcadm(1M)

• svccfg(1M) commands

system_locale Keyword

You can use the system_locale keyword to specify the language in which to display the install program and desktop. Use the following syntax to specify a locale.

system_locale=locale

locale specifies the language that you want the system to use to display the installation panels and screens. For a list of valid locale values, see the /usr/lib/locale directory or International Language Environments Guide.

terminal Keyword

You can use the terminal keyword to specify the terminal type for the system. Use the following syntax to specify the terminal type.

terminal=terminal_type

terminal_type specifies the terminal type for the system. For a list of valid terminal values, see the subdirectories in the /usr/share/lib/terminfo directory.

timezone Keyword

You can set the time zone for the system with the timezone keyword. Use the following syntax.

timezone=timezone

In the previous example, timezone specifies the time zone value for the system. The directories and files in the /usr/share/lib/zoneinfo directory provide the valid time zone values. The timezone value is the name of the path relative to the /usr/share/lib/zoneinfo directory. You can also specify any valid Olson time zone.

Example 2–12 Configuring the System Time Zone With the timezone Keyword

In the following example, the system time zone is set to mountain standard time in the United States.

timezone=US/Mountain

The installation program configures the system to use the time zone information in /usr/share/lib/zoneinfo/US/Mountain.

timeserver Keyword

You can use the timeserver keyword to specify the system that sets the date and time on the system you want to install.

Choose one of the following methods to set the timeserver keyword.

• To configure the system to serve as its own time server, set timeserver=localhost. If you specify localhost as the time server, the system's time is assumed to be correct.

• To specify another system as the time server, specify either the host name or the IP address of the time server with the timeserver keyword. Use the following syntax.

  timeserver=hostname or ip-address

  hostname is the host name of the time server system. ip-address specifies the IP address of the time server.

SPARC: Preconfiguring Power Management Information

You can use the Power Management software that is provided in the Solaris OS to automatically save the state of a system and turn it off after it is idle for 30 minutes. When you install the current Solaris release on a system that complies with version 2 of the EPA's Energy Star guidelines, for example a Sun4U^TM system, the Power Management software is installed by default. If you install with the Solaris installation program GUI, the installation program prompts you to enable or disable the Power Management software. The Solaris text installer prompts you to enable or disable the Power Management software after the installation is complete and the system reboots.

If your system has Energy Star version 3 or later, you are not prompted for this information.

If you are performing interactive installations, you cannot preconfigure the Power Management information and avoid the prompt. However, by using a custom JumpStart installation, you can preconfigure the Power Management information by using a finish script to create an /autoshutdown or /noautoshutdown file on the system. When the system reboots, the /autoshutdown file enables Power Management and the /noautoshutdown file disables Power Management.

For example, the following line in a finish script enables the Power Management software and prevents the display of the prompt after the system reboots.

touch /a/autoshutdown

Finish scripts are described in Creating Finish Scripts in Solaris 10 5/09 Installation Guide: Custom JumpStart and Advanced Installations.

Chapter 3 Preconfiguring With a Naming Service or DHCP

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)

Choosing a Naming Service

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 diskette

  ---

  Note –

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

Preconfiguring With the Naming Service

The following table provides a high-level overview of the naming service databases that you need to edit and populate to preconfigure system information.

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 net

  You can use options with this command. See details in Step 2 of theSPARC: To 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+

To Preconfigure the Locale Using NIS

1. Become superuser or assume an equivalent role on the name server.

2. Change /var/yp/Makefile to add the locale map.

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

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

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

   4. Save the file.

3. 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.com

     ---

     Note –

     International 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

   ---

   Note –

   Locales are available on the Solaris DVD or Solaris Software - 1 CD.

   ---

4. Make the maps:

   # cd /var/yp; make

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

Continuing the Installation

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 10 5/09 Installation Guide: Custom JumpStart and Advanced Installations.

See Also

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

To Preconfigure the Locale Using NIS+

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

1. Log in to a name server as superuser or as a user in the NIS+ administration group.

2. 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`

3. Add needed entries to the locale.

   # nistbladm -a name=namelocale=locale comment=comment locale.org_dir.`nisdefaults -d`

   name

   Either the domain name or a specific system name for which you want to preconfigure a default locale.

   locale

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

   comment

   The comment field. Use double quotation marks to begin and end comments that are longer than one word.

   ---

   Note –

   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.

Continuing the Installation

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 10 5/09 Installation Guide: Custom JumpStart and Advanced Installations.

See Also

For more information about the NIS+ name service, see System Administration Guide: Naming and Directory Services (NIS+).

Preconfiguring System Configuration Information With the DHCP Service (Tasks)

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.

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.

DHCP Options and Macro Values

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.

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.

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.

Using DHCP Manager to Create Install Options and Macros

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.

How to Create Options to Support Solaris Installation (DHCP Manager)

Before You Begin

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 13, Planning for DHCP Service (Tasks), in System Administration Guide: IP Services.

1. Become superuser or assume an equivalent role on the DHCP server system.

2. Start the DHCP Manager.

   # /usr/sadm/admin/bin/dhcpmgr &

   The DHCP Manager window is displayed.

3. Select the Options tab in DHCP Manager.

4. Choose Create from the Edit menu.

   The Create Option panel opens.

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

6. Click OK when you have entered all the values.

7. In the Options tab, select the option you just created.

8. Select Duplicate from the Edit menu.

   The Duplicate Option panel opens.

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

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

    ---

    Note –

    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.

    ---

How to Create Macros to Support Solaris Installation (DHCP Manager)

Before You Begin

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 13, 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).

1. Select the Macros tab in DHCP Manager.

2. Choose Create from the Edit menu.

   The Create Macro panel opens.

3. Type the name of a macro.

   See Table 3–5 for macro names you might use.

4. Click the Select button.

   The Select Option panel opens.

5. Select Vendor in the Category list.

   The Vendor options you created are listed.

6. Select an option you want to add to the macro and click OK.

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

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

9. Click OK when the macro is complete.

Continuing the Installation

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 10, 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 10 5/09 Installation Guide: Custom JumpStart and Advanced Installations.

See Also

For more information about DHCP, see Part III, DHCP, in System Administration Guide: IP Services.

Writing a Script That Uses dhtadm to Create Options and Macros

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.

Example 3–1 Sample Script to Support Network Installation

# 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 netinstalloptions

Clients 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 dhtadm(1M). For more information about the dhcptab file, see dhcptab(4).