JavaScript is required to for searching.
Skip Navigation Links
Exit Print View
Oracle Solaris 11 Express Automated Installer Guide     Oracle Solaris 11 Express 11/10
search filter icon
search icon

Document Information

Preface

1.  Automated Installer Overview

2.  Setting Up an AI Install Server

3.  Customizing Installations

4.  Specifying Installation Instructions

5.  Configuring the Client System

Creating a Custom SC Manifest

Specifying Configuration in an SC Manifest

Root and User Accounts

Configuring the Root Account

Configuring a User Account

Terminal Type and Keyboard Layout

Static IP and DNS

Example SC Manifests

Specifying Terminal Type and Keyboard Layout

Specifying Static Network Configuration

6.  Setting Up DHCP for AI

7.  Installing Client Systems

8.  Automated Installations That Boot From Media

A.  Troubleshooting Automated Installations

B.  Automated Installer Installation Administration Commands

C.  Migrating From JumpStart to Automated Installer

Specifying Configuration in an SC Manifest

You can specify configuration of anything that is configurable via smf(5) properties. For example, the SC manifest can configure a root account, an initial user, keyboard layout, terminal type, an IPv4 network interface (static or DHCP) and default route, an IPv6 network interface (static or addrconf) and default route, and DNS (nameserver list, search list, domain).

Root and User Accounts

The svc:/system/install/config SMF service configures user and root accounts. This service recognizes two property groups:


Tip - One method of generating encrypted passwords for the Oracle Solaris OS is to create a user of the intended name and password, copy the password from the /etc/shadow file between the first and second colons of the user's record, and add that information into the password values in the manifest.


Configuring the Root Account

The root_account property group can contain the following properties.

Table 5-1 root_account Property Group Properties

Property
Type
Required
Description
password
astring
yes
Encrypted root password.
type
astring
no
Account type: normal or role. The default is normal.
expire
string
no
Expiration date for login. If set to 0 (zero), the user will be forced to change the root password at the next login.

Example 5-1 Configuring the Root Account Only With Password Expired

<service name="system/install/config" version="1" type="service">
    <instance name="default" enabled="true">
        <property_group name="root_account" type="application">
            <propval name="password" type="astring" value="encrypted_password"/>
            <propval name="type" type="astring" value="normal"/>
            <propval name="expire" type="astring" value="0"/>
        </property_group>

        <property_group name="other_sc_params" type="application">
            <propval name="timezone" type="astring" value="GMT"/>
            <propval name="hostname" type="astring" value="solaris"/>
        </property_group>
    </instance>
</service>
Configuring a User Account

The user_account property group can contain the following properties.

Table 5-2 user_account Property Group Properties

Property
Type
Required
Description
login
astring
yes
User's login.
password
astring
yes
Encrypted user password.
description
astring
no
Usually the user's full name.
shell
astring
no
Full path name of the program used as the user's shell on login.
uid
count
no
UID of the new user. The default UID is 101.
gid
count
no
User's primary group membership. The default GID is 10.
type
astring
no
Account type: normal or role. The default is normal.
profiles
astring
no
One or more comma-separated execution profiles defined in prof_attr(4).
roles
astring
no
One or more comma-separated roles defined in user_attr(4).
sudoers
astring
no
Entry put along with login into the sudoers(4) file.
expire
astring
no
Expiration date for login. If set to 0 (zero), the user will be forced to change the password at the next login.
home_zfs_dataset
astring
no
User's home directory ZFS dataset. The default is root_pool/export/home/login
home_mountpoint
astring
no
User's home directory mount point. The default is /export/home/login

Terminal Type and Keyboard Layout

The svc:/system/console-login SMF service configures terminal type. See the ttymon(1M) man page for definition of related SMF properties.

Example 5-2 Configuring vt100 Terminal Type

<service name="system/console-login" version="1" type="service">
    <property_group name="ttymon" type="application">
        <propval name="terminal_type" type="astring" value="vt100"/>
    </property_group>
</service>

The svc:/system/keymap SMF service configures keyboard layout. See the kbd(1) man page for definition of related SMF properties.

Example 5-3 Configuring Czech Keyboard Layout

<service name='system/keymap' version='1' type='service'>
    <instance name='default' enabled='true'>
        <property_group name='keymap' type='system'>
            <propval name='layout' type='astring' value='Czech'/>
        </property_group>
    </instance>
</service>

Static IP and DNS

Networking can be configured automatically or manually on an Oracle Solaris 11 Express system. Configurations that you can do manually can also be specified in an SC manifest.

Automated network configuration (NWAM) is activated by enabling svc:/network/physical:nwam and disabling svc:/network/physical:default. The NWAM framework handles configuration of the network.

Manual network configuration is activated when svc:/network/physical:nwam is disabled and svc:/network/physical:default is enabled. In manual mode, the following networking parameters can be configured:

The svc:/network/install and svc:/network/dns/install SMF services contain properties that can be used by the services to configure an initial physical network interface or an initial DNS client configuration. These services are initially disabled with property values that do not result in any system configuration. These services can be enabled and appropriate properties configured in the SC manifest.

The svc:/network/install service supports configuring one IPv4 interface and one IPv6 interface and, optionally, a default route reachable by these interfaces. The service defines two property groups: one property group for an IPv4 interface and one for an IPv6 interface. The service uses its properties and ipadm(1M) to configure the network interfaces. Similarly, the service uses its properties and route(1M) to define a default route.

The install_ipv4_interface property group contains the following properties.

Table 5-3 install_ipv4_interface Property Group Properties

Property
Type
Required
Description
name
astring
yes
Name of network interface.
address_type
astring
yes
Value used to construct the -T option for the ipadm(1M) create-addr subcommand. Valid values are static or dhcp.
static_address
net_address_v4
no
Only required with an address_type of static. Used to construct the local address for the ipadm(1M) create-addr subcommand.
dhcp_wait
astring
no
Only applies with an address_type of dhcp. If defined, this property is used to construct the -w seconds (or forever) portion of the ipadm(1M) create-addr subcommand.
default_route
net_address_v4
no
Used to define a default route using route(1M).
# /usr/sbin/route \
-p add default default-route \
-ifp ifname

The value of ifname is the interface name portion of the name property.

The install_ipv6_interface property group contains the following properties.

Table 5-4 install_ipv6_interface Property Group Properties

Property
Type
Required
Description
name
astring
yes
Name of network interface.
address_type
astring
yes
Value used to construct the -T option for the ipadm(1M) create-addr subcommand. Valid values are static or addrconf.
static_address
net_address_v6
no
Only required with an address_type of static. Used to construct the local address for the ipadm(1M) create-addr subcommand.
interface_id
net_address_v6
no
Only applies with an address_type of addrconf. Used to construct the -i interface_id portion of the ipadm(1M) create-addr subcommand.
stateless
astring
no
Only applies with an address_type of addrconf. Used to construct the -p stateless=yes|no portion of the ipadm(1M) create-addr subcommand.
stateful
astring
no
Only applies with an address_type of addrconf. Used to construct the -p stateful=yes|no portion of the ipadm(1M) create-addr subcommand.
default_route
net_address_v6
no
Used to define a default route using route(1M).
# /usr/sbin/route \
-p add default default-route \
-ifp ifname

The value of ifname is the interface name portion of the name property.

The svc:/network/dns/install service supports the configuration of a DNS client. The service defines one property group: install_props. The service uses its properties to construct a DNS resolv.conf(4) file.

The install_props property group contains the following properties.

Table 5-5 install_props Property Group Properties

Property
Type
Required
Description
domain
astring
no
Local domain name. Used to construct the domain directive in resolv.conf(4).
nameserver
net_address
yes
Used to construct the nameserver directives in resolv.conf(4). The net_address_list should contain IPv4 and IPv6 addresses.
search
astring
no
A value for the search order host name lookup. This value is used to construct the search directive in resolv.conf(4). The astring_list should contain domain values.