JavaScript is required to for searching.
Skip Navigation Links
Exit Print View
Oracle Solaris 10 1/13 Installation Guide: Network-Based Installations     Oracle Solaris 10 1/13 Information Library
search filter icon
search icon

Document Information

Preface

Part I Planning to Install Over the Network

1.  Where to Find Oracle Solaris Installation Planning Information

2.  Preconfiguring System Configuration Information (Tasks)

Advantages of Preconfiguring System Configuration Information

Preconfiguring With the sysidcfg File

Syntax Rules for the sysidcfg File

sysidcfg File Keywords

auto_reg Keyword

keyboard Keyword

name_service Keyword

network_interface Keyword

nfs4_domain Keyword

root_password Keyword

security_policy Keyword

service_profile Keyword

system_locale Keyword

terminal Keyword

timezone Keyword

timeserver Keyword

SPARC: Preconfiguring Power Management Information

3.  Preconfiguring With a Naming Service or DHCP

Part II Installing Over a Local Area Network

4.  Installing From the Network (Overview)

5.  Installing From the Network With DVD Media (Tasks)

6.  Installing From the Network With CD Media (Tasks)

7.  Patching the Miniroot Image (Tasks)

8.  Installing Over the Network (Examples)

9.  Installing From the Network (Command Reference)

Part III Installing Over a Wide Area Network

10.  WAN Boot (Overview)

11.  Preparing to Install With WAN Boot (Planning)

12.  Installing With WAN Boot (Tasks)

13.  SPARC: Installing With WAN Boot (Tasks)

14.  SPARC: Installing With WAN Boot (Examples)

15.  WAN Boot (Reference)

Part IV Appendixes

A.  Troubleshooting (Tasks)

B.  Installing or Upgrading Remotely (Tasks)

Glossary

Index

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.


Note - The name_service keyword in the sysidcfg file automatically sets the naming service during installation of the Oracle 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. For example, 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 locations described in the following table.

Table 2-2 sysidcfg Locations

NFS file system
If you put the sysidcfg file in a shared NFS file system, you must use the -p option of the add_install_client(1M) command when you set up the system to install from the network. The -p option specifies where the system can find the sysidcfg file when you install the current Oracle Solaris release.
UFS or PCFS diskette
Place the sysidcfg file in the root (/) directory on the diskette.

If you are performing a JumpStart installation and you want to use a sysidcfg file on a diskette, you must place the sysidcfg file on the profile diskette. To find out how to create a profile diskette, see Creating a Profile Diskette for Stand-alone Systems in Oracle Solaris 10 1/13 Installation Guide: JumpStart Installations.

You can place only one sysidcfg file in a directory or on a diskette. If you are creating more than one sysidcfg file, you must place each file in a different directory or on a different diskette.

HTTP or HTTPS server
If you want to perform a WAN boot installation, place the sysidcfg file in the document root directory of the web server.

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

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 JumpStart installation, you need to create a profile and a rules.ok file. For more information, see Chapter 2, JumpStart (Overview), in Oracle Solaris 10 1/13 Installation Guide: JumpStart Installations.

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

Example 2-1 SPARC: sysidcfg File

This example shows 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 JumpStart profile to perform a 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

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)}
Syntax Rule
Example
Independent keywords can be listed in any order.
pointer=MS-S
display=ati {size=15-inch}
Keywords are not case sensitive.
TIMEZONE=US/Central
terminal=sun-cmd
Enclose all dependent keywords in curly braces ({}) to tie them to their associated independent keyword.
name_service=NIS 
       {domain_name=marquee.central.example.com
        name_server=connor(192.168.112.3)}
You can optionally enclosed values in single (`) or double quotes (“).
network_interface='none'
For all keywords except the network_interface keyword, only one instance of a keyword is valid. However, if you specify the keyword more than once, only the first instance of the keyword is used.
name_service=NIS
name_service=DNS

sysidcfg File Keywords

The following table lists the keywords you can use to configure system information in the sysidcfg file.

Table 2-3 Keywords to Use in sysidcfg

Configuration Information
Keyword
For More Information
Keyboard layout and language
keyboard
Naming service, domain name, name server
name_service
Network interface, host name, Internet Protocol (IP) address, netmask, DHCP, IPv6
network_interface
Domain name definition for NFSv4
nfs4_domain
Root password
root_password
Security policy
security_policy
Network security profile
service_profile
Language in which to display the install program and desktop
system_locale
Terminal type
terminal
Time zone
timezone
Date and time
timeserver
Auto Registration setup
auto_reg

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

auto_reg Keyword

Starting with the Oracle Solaris 10 9/10 release, you can use the auto_reg keyword to set up or disable Auto Registration, a feature of Oracle Solaris. Auto Registration is new in the Oracle Solaris 10 9/10 release. When you install or upgrade your system, configuration data about your system is, when you reboot, automatically communicated through the existing service tag technology to the Oracle Product Registration System. You may elect to have your configuration data sent to the Oracle Product Registration System anonymously so that the configuration data sent to Oracle has no link to the name of a customer. You also have the option to disable Auto Registration.

You can use the auto_reg keyword in the sysidcfg file prior to a hands-off installation or upgrade to provide your support credentials for Auto Registration, to choose anonymous registration, or to disable Auto Registration. If you do not set up the sysidcfg file with these keywords, you are prompted to provide your credentials or to register anonymously during the installation or upgrade.

The general syntax for the auto_reg keyword is as follows:

auto_reg=[anon |none |noproxy |all |disable ] {
oracle_user=username
oracle_pw=oracle-password
http_proxy_host=hostname
http_proxy_port=port-number
http_proxy_user=proxy-username
htty_proxy_pw=proxy-password
}

To use this keyword, first specify a basic type of registration by choosing one of the main values: anon, none, noproxy, all, or disable, as described in the following table. Then, use additional keywords to provide specific My Oracle Support credentials and to provide your proxy information for the Auto Registration.

The values that you use for the auto-reg keyword depend on the type of Auto Registration that you want to use.

Secondary keywords

You use the following keywords and values within the main auto_reg keyword to provide either your My Oracle Support credentials or your proxy information.

Oracle_user username
Provide your My Oracle Support username, for example, oracle_user=myusername.
oracle_pw oracle-password
Provide your My Oracle Support password in plain, not encrypted, text, for example, oracle_pw=j32js94jrjsW.
http_proxy_host hostname
Provide your proxy hostname, for example, http_proxy_host=sss.com.
http_proxy_port port-number
Provide your proxy port, for example, http_proxy_port=8050.
http_proxy_user proxy-username
Provide your proxy username, for example, http_proxy_user=proxyusername.
htty_proxy_pw proxy-password
Provide your proxy password in plain, not encrypted, text, for example, http_proxy_pw=sej47875WSjs.

Example 2-4 Auto Registration Examples

In this example, the anon value specifies that your service tags are anonymously registered with Oracle. The sysidcfg file, provides the proxy information.

auto_reg=anon {
http_proxy_host=sss.com
http_proxy_port=8040
http_proxy_user=myproxyusername
htty_proxy_pw=si329jehId
}

In the example, the none value specifies that your service tags are anonymously registered with Oracle, and that you do not want to include proxy information. If you do provide proxy information during an installation or upgrade, that proxy information will be ignored.

auto_reg=none

Example 2-5 Registration Using Support Credentials Examples

In this example, the all value specifies that your service tags are registered with Oracle using your My Oracle Support credentials when you reboot after installing or upgrading your system. You need to provide your My Oracle Support credentials and when prompted proxy.

auto_reg=all {
oracle_user=myusername
oracle_pw=ajsi349EKS987
http_proxy_host=sss.com
http_proxy_port=8030
http_proxy_user=myproxyusername
htty_proxy_pw=adjsi2934IEls
}

In this example, the noproxy value specifies that your service tags are registered with Oracle using your My Oracle Support credentials when you reboot after installing or upgrading your system. You need to provide your My Oracle Support credentials but do not need to provide proxy information. If you do provide proxy information during the installation or upgrade, that information is ignored.

auto_reg=noproxy {
oracle_user=myusername
oracle_pw=sie7894KEdjs2
}

keyboard Keyword

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

The following procedure occurs:

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 a language and its corresponding layout in your sysidcfg file.

keyboard=keyboard-layout

If the value provided for keyboard-layout is not a valid value, 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.


SPARC only - 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, set the keyboard language in your sysidcfg file. For JumpStart installations, the default is for the U.S. English language.

The following example, sets the keyboard language and its corresponding keyboard layout for the German language:

keyboard=German

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


Note - The name_service option in the sysidcfg file automatically sets the naming service during installation of the Oracle 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 and NIS+ Syntax for the name_service Keyword

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

name_service=NIS {domain_name=domain-name 
                   name_server=hostname(IP-address)}
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-6 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)}

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

DNS Syntax for the 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, separated by commas.

search=domain-name

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

Example 2-8 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 the 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 quotation marks.

password

(Optional) Specifies the client proxy password.

Example 2-9 Specifying an LDAP Server With the name_service Keyword

This example specifies an LDAP server with the following configuration information:

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:

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 with DHCP or without DHCP by using a sysidcfg file entry.

Example 2-10 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-11 Configuring a Single Interface by Specifying Configuration Information With the network_interface Keyword

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

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 with DHCP or without DHCP by using a sysidcfg file entry.

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-12 Configuring Multiple Interfaces With the network_interface Keyword

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

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


domain_name

This value overrides the default domain name.

This value must be a valid domain name, 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.


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

For JumpStart installations in the Oracle 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 by using 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. 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-13 Configuring the System to Use Kerberos With the security_policy Keyword

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

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.

Set service_profile=limited_net to specify that all network services except 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.

To specify that no network service changes are made during installation, set service_profile=open.

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 Oracle Solaris 10 1/13 Installation Guide: Planning for Installation and Upgrade.

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

system_locale Keyword

You can use the system_locale keyword to specify the language in which to display the install program and desktop:

system_locale=locale

locale specifies the language that you want the system to use to display the installation panels and screens.

For example,

system_locale=de_CH. UTF-8

for swiss German UTF-8

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:

terminal=terminal-type

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:

timezone=timezone

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