Comparing sysidcfg Keywords to System Configuration Profile Directives - Transitioning From Oracle® Solaris 10 JumpStart to Oracle Solaris 11.3 Automated Installer

Language:

Comparing `sysidcfg` Keywords to System Configuration Profile Directives

The following table compares sysidcfg file keywords with example AI system configuration profile specifications. Different SMF property value names might apply in different cases. See the examples in sysidcfg Conversion Using js2ai and in Example System Configuration Profiles in Installing Oracle Solaris 11.3 Systems.

Table 4 Comparing sysidcfg Keywords and Configuration Profile Directives

`sysidcfg` Keyword	System Configuration Profile Directives
`keyboard`	The `js2ai` command does not perform any translation. Make sure the keyboard specified in the `sysidcfg` file is supported in Oracle Solaris 11. Service name: `system/keymap` Property group name: `keymap` Property value name: `layout`
`name_service`	AI supports DNS, NIS, and LDAP. The `js2ai` command supports values `NONE`, `DNS`, `NIS`, and `LDAP`. NIS+ name services are translated as NIS. If a name service is configured, the network must be configured as `DefaultFixed`. Service name: `system/name-service/switch` Property group name: `config` Property value name: `netgroup`
`network_interface`	AI supports configuring only a single interface as part of system installation. Because of this limitation, the `js2ai` command processes only the interface labeled `PRIMARY` or the first interface encountered in the `sysidcfg` file. The `js2ai` command sets the network to `DefaultFixed` if a `name_service` is specified. A properly configured `DefaultFixed` network needs to provide the host name, IP address, netmask, and gateway. Automated network configuration is supported only if no name service is specified. Oracle Solaris 11 by default uses the prefix `net` when assigning link names. (The older style used in Oracle Solaris 10 is available but is disabled by default.) When the `js2ai` command does a conversion of the network interface and sees an Oracle Solaris 10 style link name, the command will disable neutral link names. To use neutral link names in Oracle Solaris 11, you must change the network interface name specified in the `sysidcfg` file to an Oracle Solaris neutral link name like `net0`. For more information about neutral link names, see Network Devices and Datalink Naming in Oracle Solaris in Configuring and Managing Network Components in Oracle Solaris 11.3. Service name: `network/install` Property group name: `install_ipv4_interface` Property value name: `static_address` Property group name: `install_ipv6_interface`
`nfs4_domain`	`nfs4_domain=dynamic` is supported for Automatic and DefaultFixed networks. `networks.nfs4_domain=custom-domain-name` is only supported for DefaultFixed networks. The conversion of the `network_interface` keyword determines whether a DefaultFixed or Automatic network is configured. Service name: `network/nfs/mapid` Property group name: `nfs-props` Property value name: `nfsmapid_domain`
`root_password`	Oracle Solaris 11 uses roles instead of the `root` user. You need to define a user with `root` role privileges in order to access the system in multiuser mode. Because the necessary structure cannot completely be defined using the `root_password` keyword, you need to add the necessary structures used to define a user account with `root` role privileges to the `sc_profile.xml` file as a comment. If you do not specify the `root_password` keyword, you will also need to define the necessary datastructure for it as a comment. Service name: `system/config-user` Property group name: `root_account` Property value name: `password`
`security_policy`	The `js2ai` command supports the value `NONE`.
`service_profile`	The `js2ai` command supports the value `limited_net`.
`system_locale`	The `js2ai` command will check whether the locale specified is one of the default core locales supported and will generate a warning if the locale is not supported. The `js2ai` command will also attempt to convert non-core locales to core locales. For more information on core locales, see Internationalization and Localization Changes in Transitioning From Oracle Solaris 10 to Oracle Solaris 11.3. Service name: `system/environment` Property group name: `environment` Property value name: `LC_ALL`
`terminal`	The `js2ai` command does not perform any translation. Make sure the terminal type specified in the `sysidcfg` file is supported in Oracle Solaris 11. Service name: `system/console-login` Property group name: `ttymon` Property value name: `terminal_type`
`timeserver`	The `js2ai` command supports the value `localhost`.
`timezone`	The `js2ai` command does not perform any translation. Service name: `system/timezone` Property group name: `timezone` Property value name: `localtime`