Skip Navigation Links | |
Exit Print View | |
Installing Oracle Solaris 11.1 Systems Oracle Solaris 11.1 Information Library |
Part I Oracle Solaris 11.1 Installation Options
1. Overview of Installation Options
Part II Installing Using Installation Media
2. Preparing for the Installation
5. Automated Installations That Boot From Media
6. Unconfiguring or Reconfiguring an Oracle Solaris instance
Part III Installing Using an Install Server
7. Automated Installation of Multiple Clients
8. Setting Up an Install Server
10. Provisioning the Client System
11. Configuring the Client System
Providing Configuration Profiles
Creating System Configuration Profiles
Validating System Configuration Profiles
Adding System Configuration Profiles to an Install Service
Specifying Configuration in a System Configuration Profile
Configuring Root and User Accounts
Setting the Time Zone and Locale
Setting the Terminal Type and Keyboard Layout
Setting Up Oracle Configuration Manager and Oracle Auto Service Request
Using System Configuration Profile Templates
Example System Configuration Profiles
Sample System Configuration Profile
Specifying Static Network Configuration
Specifying Name Service Configuration
12. Installing and Configuring Zones
13. Running a Custom Script During First Boot
15. Troubleshooting Automated Installations
Part IV Performing Related Tasks
A. Working With Oracle Configuration Manager
You can specify configuration of any system characteristic that is configurable by using smf(5) properties. For example, the system configuration profile 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 name service (name server list, search list, domain). If you specify a service or property that does not apply, that specification is ignored. Do not specify any particular property more than one time.
If you are not sure which SMF properties you need to specify, you can use the describe subcommand of the svccfg command to display a description of the property groups and properties of a service, including possible settings. See “Property Inspection and Modification Subcommands” on the svccfg(1M) man page.
svccfg -s FMRI describe [-v] [-t] [propertygroup/property]
A property group or specific property can be queried by specifying either the property group name, or the property group name and property name separated by a slash (/), as an argument.
The -v option gives all information available, including descriptions for current settings, constraints, and other possible setting choices.
The -t option shows only the template data for the selection (see the smf_template(5) man page), and does not display the current settings for property groups and properties.
$ svccfg -s name-service/switch describe config config application Name service switch configuration data as described in nsswitch.conf(4). config/value_authorization astring solaris.smf.value.name-service.switch config/default astring files Default configuration database entry. config/host astring "files dns mdns" Override configuration for host database lookups. (both IPv4 and IPv6 hosts) config/printer astring "user files" Override configuration for printer database lookups. $ svccfg -s name-service/switch describe -v config config application name: config type: application required: true target: this description: Name service switch configuration data as described in nsswitch.conf(4). config/value_authorization astring solaris.smf.value.name-service.switch config/default astring files type: astring required: true Default configuration database entry. visibility: readwrite minimum number of values: 1 maximum number of values: 1 value: files ... $ svccfg -s name-service/switch describe -t config name: config type: application Name service switch configuration data as described in nsswitch.conf(4). name: default type: astring Default configuration database entry. name: host type: astring Override configuration for host database lookups. (both IPv4 and IPv6 hosts) name: password type: astring Override configuration for passwd database lookups. Also used with the shadow and user_attr databases. name: group type: astring Override configuration for group database lookups. name: network type: astring Override configuration for network database lookups. ... $ svccfg -s system/config-user describe root_account root_account application root_account/expire astring root_account/password astring root_account/read_authorization astring solaris.smf.read.system-config root_account/stability astring Evolving root_account/type astring
Enter the following sysconfig create-profile command with the users grouping to generate a valid profile that configures the root user and initial user.
# sysconfig create-profile -g users -o sc_users.xml
The svc:/system/config-user SMF service configures user and root accounts. This service recognizes two property groups:
The root_account property group includes SMF properties that configure the root account.
The user_account property group includes SMF properties that configure user accounts.
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.
The root_account property group contains the properties listed in the following table.
Table 11-1 root_account Property Group Properties
|
Example 11-1 Configuring the Root Account Only With Password Expired
<service name="system/config-user" version="1" type="service"> <instance name="default" enabled="true"> <property_group name="root_account" type="application"> <propval name="password" value="encrypted_password"/> <propval name="type" value="normal"/> <propval name="expire" value="0"/> </property_group> </instance> </service>
This section includes the following information:
By default, when initial user accounts are created, the home directories are managed by the automounter and accessed under /home/login directories. To create initial user accounts without depending on the automounter, set the user_account/autohome property to the empty string ("") in the configuration profile.
Setting the user_account/autohome property to the empty string has the following effects:
The home directory entry in the /etc/passwd file is set to the mount point of the home ZFS dataset, not to /home/login. The default mount point of the home ZFS dataset is /export/home/login.
No mapping entry is added to the /etc/auto_home file.
The user_account property group contains the properties listed in the following table.
Table 11-2 user_account Property Group Properties
|
To configure multiple users on the newly-installed system, specify the users by using the useradd(1M) command in a script. Then use a run-once SMF service to run the script at first boot. See Chapter 13, Running a Custom Script During First Boot for instructions.
Use the sysconfig create-profile command with the identity grouping to generate a valid profile that configures the system node name.
# sysconfig create-profile -g identity -o sc_identity.xml
The svc:/system/identity:node SMF service sets the system host name. The node is the instance of svc:/system/identity.
The identity property group contains the properties listed in the following table.
Table 11-3 config Property Group Properties
|
Example 11-2 Configuring the Host Name
This example sets the system host name to solaris.
<service name="system/identity" version="1" type="service"> <instance name="node" enabled="true"> <property_group name="config" type="application"> <propval name="nodename" value="solaris"/> </property_group> </instance> </service>
Example 11-3 Disabling Node Name Mapping
When you install the Oracle Solaris 11 OS or an Oracle Solaris 11 update release, by default the system node name is mapped to the loopback or to the IP address of the interface configured as part of installation. You can disable this default mapping by setting the enable_mapping property to false, as shown in the following example.
<service name="system/identity" version="1" type="service"> <instance name="node" enabled="true"> <property_group name="config" type="application"> <propval name="nodename" value="solaris"/> <propval name="enable_mapping" value="false"/> </property_group> </instance> </service>
Use the sysconfig create-profile command with the location grouping to generate a valid profile that configures the time zone and locale.
# sysconfig create-profile -g location -o sc_location.xml
The svc:/system/timezone SMF service sets the time zone for the system.
The timezone property group contains the properties listed in the following table.
Table 11-4 timezone Property Group Properties
|
Example 11-4 Configuring the Time Zone
This example sets the time zone to Central European Time/Prague, CZ.
<service name='system/timezone' version='1'> <instance name='default' enabled='true'> <property_group name='timezone'> <propval name='localtime' value='Europe/Prague'/> </property_group> </instance> </service>
The svc:/system/environment:init SMF service sets the locale for the system.
The environment property group can define the following environment variables. See the environ(5) man page for information about environment variables.
Table 11-5 environment Property Group Properties
|
Example 11-5 Configuring the Locale
This example sets the locale to Czech language (cs) and Czech Republic (CZ).
<service name='system/environment' version='1'> <instance name='init' enabled='true'> <property_group name='environment'> <propval name='LC_ALL' value='cs_CZ.UTF-8'/> </property_group> </instance> </service>
Example 11-6 Configuring Terminal Type
The svc:/system/console-login SMF service configures the terminal type. See the ttymon(1M) man page for definition of related SMF properties.
This example sets the terminal type to vt100.
<service name="system/console-login" version="1" type="service"> <instance name="default" enabled="true"> <property_group name="ttymon" type="application"> <propval name="terminal_type" value="vt100"/> </property_group> </instance> </service>
Example 11-7 Configuring Keyboard Layout
Use the sysconfig create-profile command with the kbd_layout grouping to generate a valid profile that configures the keyboard layout.
# sysconfig create-profile -g kbd_layout -o sc_kdb.xml
The svc:/system/keymap SMF service configures the keyboard layout. See the kbd(1) man page for definition of related SMF properties.
This example sets the keyboard layout to Czech.
<service name='system/keymap' version='1' type='service'> <instance name='default' enabled='true'> <property_group name='keymap' type='system'> <propval name='layout' value='Czech'/> </property_group> </instance> </service>
Use the sysconfig create-profile command with the network grouping to generate a valid profile that configures the network.
# sysconfig create-profile -g network -o sc_network.xml
The svc:/network/install SMF service configures an initial physical network interface. This service is initially disabled with property values that do not result in any system configuration.
Note - If the installation target is an iSCSI device, do not configure that network interface in any system configuration profile for that installation. For iSCSI boot, the network interface for the iSCSI device is configured early in the client boot process. If you configure that same interface again, the network/install service for the interface goes into maintenance state.
To configure multiple network interfaces, specify the configuration in a script, and use a run-once SMF service to run the script at first boot. See Chapter 13, Running a Custom Script During First Boot for instructions and a sample script.
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.
See the examples in Specifying Static Network Configuration.
The install_ipv4_interface property group contains the properties listed in the following table.
Table 11-6 install_ipv4_interface Property Group Properties
|
The install_ipv6_interface property group contains the properties listed in the following table.
Table 11-7 install_ipv6_interface Property Group Properties
|
The svc:/network/dns/client service supports the configuration of a DNS client. The service defines one property group: config. The service uses its properties to construct a DNS resolv.conf(4) file.
The config property group contains the properties listed in the following table.
Table 11-8 config Property Group Properties
|
Use the sysconfig create-profile command with the naming_services grouping to generate a valid profile that configures DNS, NIS, and LDAP clients and name service switch.
# sysconfig create-profile -g naming_services -o sc_ns.xml
The svc:/network/dns/client SMF service configures an initial DNS client configuration. This service is initially disabled with property values that do not result in any system configuration. See the examples in Specifying Name Service Configuration.
Oracle Configuration Manager enables you to log your system configurations with My Oracle Support, and Oracle Auto Service Request can automatically generate service requests for specific hardware faults.
Use the sysconfig create-profile command with the support grouping to generate a valid profile that configures Oracle Configuration Manager and Oracle Auto Service Request.
# sysconfig create-profile -g support -o sc_support.xml
The output profile sets up the first phase of registration, which is the same for all clients that match the following criteria:
The systems use the same My Oracle Support credentials to register. All client systems that use this profile register with My Oracle Support in the same way. The data from all of these clients will be associated with the same My Oracle Support account.
The systems access My Oracle Support through the same network configuration. All client systems that use this profile access My Oracle Support through the same proxy servers and aggregation hubs, for example.
If you need to create additional profiles for different groups of AI client systems, you should rerun the sysconfig create-profile command, rather than copy and edit an existing profile. If your proxy server has a user name and password, then you must rerun sysconfig create-profile since the passwords are encrypted.