sysidcfg Conversion Using js2ai

This section shows how to use js2ai to convert a sysidcfg file to an AI system configuration profile file. For each sysidcfg file processed, js2ai creates an AI system configuration profile file named sc_profile.xml in the directory where the js2ai command was invoked. Use the –D option to specify a different directory for the sc_profile.xml file. To aid in the conversion process, make a copy of the original sysidcfg file and work from a copy. The conversion process might require that you edit and modify the sysidcfg file before it can be successfully converted.

Example 3-1  Converting a sysidcfg File That Includes Errors

This example uses the following sysidcfg file:

timezone=US/Pacific
timeserver=localhost
keyboard=US-English
system_locale=en_US.UTF-8
terminal=vt100
network_interface=primary { hostname=host1
      ip_address=192.0.2.4
      netmask=255.255.255.224
      protocol_ipv6=yes
      default_route=192.0.2.3 }
name_service=DNS{domain_name=example.com
      name_server=192.0.2.1,192.0.2.2
      search=example.com,example.org}
root_password=rJmv5LUXM1OcU
security_policy=none
nfs_domain=dynamic

Use the following command to process this sysidcfg file. In the error report, validation errors are shown as a hyphen character because the –S option suppressed validation.

# js2ai -sS
                                Process  Unsupported  Conversion  Validation
Name                  Warnings  Errors   Items        Errors      Errors
-------------------   --------  -------  -----------  ----------  ----------
sysidcfg                     1        0            0           1           -

Conversion completed. One or more failures and/or warnings occurred.
For errors see js2ai.log
# cat js2ai.log

sysidcfg:line 6:CONVERSION:  DefaultFixed network configuration enabled.
Unable to complete network  configuration, replace interface PRIMARY
with the actual interface you  wish to configure.
sysidcfg:line 17:WARNING: Oracle Solaris 11 uses roles instead of root user.
An admin user with root role privileges will need to be defined in order to 
access the system in multi-user mode. The necessary xml structures have been
added to sc_profile.xml as a comment.  Edit sc_profile.xml to perform the 
necessary modifications to define the admin user.

Example 3-2  Converting a Corrected sysidcfg File

The following modified sysidcfg file addresses the errors reported in the previous example. The PRIMARY interface specification is replaced with the interface name e1000g.

timezone=US/Pacific
timeserver=localhost
keyboard=US-English
system_locale=en_US.UTF-8
terminal=vt100
network_interface=e1000g { hostname=host1
      ip_address=192.0.2.4
      netmask=255.255.255.224
      protocol_ipv6=yes
      default_route=192.0.2.3 }
name_service=DNS{domain_name=example.com
      name_server=192.0.2.1,192.0.2.2
      search=example.com,example.org}
root_password=rJmv5LUXM1OcU
security_policy=none
nfs_domain=dynamic

# js2ai -sS

                               Process  Unsupported  Conversion  Validation
Name                 Warnings  Errors   Items        Errors      Errors
-------------------  --------  -------  -----------  ----------  ----------
sysidcfg                    2        0            0           0           -
Conversion completed. One or more failures and/or warnings occurred.
For details see /tmp/js2ai.log
# cat js2ai.log
sysidcfg:line 16:WARNING: Oracle Solaris 11 uses roles instead of root user.
An admin user with root role privileges will need to be defined in order to
access the system in multi-user mode.  The necessary xml structures have been
added to sc_profile.xml as a comment. Edit sc_profile.xml to perform the
necessary modifications to define the admin user.
sysidcfg:line 6:WARNING: In order to support the direct translation of the
sysidcfg interface 'e1000g', Oracle Solaris 11 neutral link name support will
be disabled.  If you wish to use neutral link names, change the interface
name specified in the sysidcfg file to a 'netx' style interface name or edit
the resulting sc_profile.xml file.

Although the network interface primary was replaced with an Oracle Solaris 10 interface name, you will still get a warning about neutral link names. If you want to use the old style link names then no action is required. In most instances the interfaces will map the same as they do in Oracle Solaris 10, but that outcome is not guaranteed.

If you want to use the neutral link names used by Oracle Solaris 11, you can change your network interface in the sysidcfg file to a net# style name. Typically the primary interface will get defined as net0. In order to address the user warning, edit the sc_profile.xml file as outlined in the notes for line 6 in the preceding example.