Using js2ai to Convert sysidcfg Files to System Configuration Profiles

Use the js2ai utility with the -s option to convert any sysidcfg files that are associated with this JumpStart configuration to system configuration profile files. Initially use the -S option to skip validation.

/usr/sbin/js2ai -sS [-d sysidcfg_dir] [-D destination_dir]

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.

If you do not see a message that the conversion was successfully completed, examine the error report and the js2ai.log file. The error report and the log file report warnings, process errors, unsupported items, conversion errors, and validation errors. The error report is a table output to stdout that shows the number of each type of error that was encountered in converting the sysidcfg file. The log file describes the problems.

1. Correct any process errors.

2. Remove any lines from the sysidcfg file that are listed as unsupported items.

3. Examine the conversion errors and correct the errors if possible. Otherwise, remove the lines that are causing the errors.

4. Examine any warning messages and make sure no corrections are necessary.

When you receive a message that the conversion completed successfully, run the js2ai command without the -S option to validate the output sc_profile.xml file. Validation errors must be corrected in the sc_profile.xml file.

To validate a specific output system configuration profile, run the js2ai command with the -V option:

# js2ai -V path/sc_profile.xml

System configuration profiles are also validated when you add them to an AI install service or when you run the following command on your AI install server:

# installadm validate -n install_service_name sc_profile.xml

See Validating a System Configuration Profile in Installing Oracle Solaris 11.1 Systems for more information about the installadm validate command.

Example sysidcfg Conversion Using js2ai

This section shows using 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.

Sample sysidcfg File

This example uses the following sysidcfg file:

timezone=US/Pacific
terminal=xterms
timeserver=localhost
network_interface=primary {
                        hostname=host1
                        ip_address=10.80.127.35
                        netmask=255.255.255.224
                        protocol_ipv6=no
                        default_route=10.80.127.33}
root_password=rJmv5LUXM1OcU
security_policy=none

Using js2ai With the sysidcfg File Option

Use the following command to process this sysidcfg file. In the error report, validation errors are shown as a hyphen character because validation was not done. Validation is suppressed by the -S option.

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

Conversion completed. One or more failures occurred.
For errors see js2ai.log
# cat js2ai.log
sysidcfg:line 4:CONVERSION: when the PRIMARY interface is specified, by default the
system will be configured for both IPv4 and IPv6 via automatic network configuration.
The options specified will be ignored. If you wish to configure the interface with
the specified options replace PRIMARY with the name of the interface that should be
configured.

Equivalent System Configuration Profile File

The following modified sysidcfg file addresses the error reported in the js2ai.log file. The PRIMARY interface specification is replaced with the interface name e1000g.

timezone=US/Pacific
terminal=xterms
timeserver=localhost
network_interface=e1000g {
                        hostname=host1
                        ip_address=10.80.127.35
                        netmask=255.255.255.224
                        protocol_ipv6=no
                        default_route=10.80.127.33}
root_password=rJmv5LUXM1OcU
security_policy=none

# js2ai -sS
Successfully completed conversion

This time no error report is output and the js2ai.log file is empty.

The following sc_profile.xml file is produced.

<?xml version="1.0" encoding="utf-8"?>
<!DOCTYPE service_bundle
  SYSTEM '/usr/share/lib/xml/dtd/service_bundle.dtd.1'>
<service_bundle name="system configuration" type="profile">
  <service name="system/timezone" type="service" version="1">
    <instance enabled="true" name="default">
      <property_group name="timezone" type="application">
        <propval name="localtime" type="astring" value="US/Pacific"/>
      </property_group>
    </instance>
  </service>
  <service name="system/console-login" type="service" version="1">
    <instance enabled="true" name="default">
      <property_group name="ttymon" type="application">
        <propval name="terminal_type" type="astring" value="xterms"/>
      </property_group>
    </instance>
  </service>
  <service name="system/config-user" type="service" version="1">
    <instance enabled="true" name="default">
      <property_group name="root_account" type="application">
        <propval name="password" type="astring" value="rJmv5LUXM1OcU"/>
      </property_group>
    </instance>
  </service>
  <service name="system/identity" type="service" version="1">
    <instance enabled="true" name="node">
      <property_group name="config" type="application">
        <propval name="nodename" type="astring" value="host1"/>
      </property_group>
    </instance>
  </service>
  <service name="network/install" type="service" version="1">
    <instance enabled="true" name="default">
      <property_group name="install_ipv4_interface" type="application">
        <propval name="name" type="astring" value="e1000g/v4"/>
        <propval name="address_type" type="astring" value="static"/>
        <propval name="static_address" type="net_address_v4" value="10.80.127.35/27"/>
        <propval name="default_route" type="net_address_v4" value="10.80.127.33"/>
      </property_group>
    </instance>
  </service>
  <service name="network/physical" type="service" version="1">
    <instance enabled="true" name="default">
      <property_group name="netcfg" type="application">
        <propval name="active_ncp" type="astring" value="DefaultFixed"/>
      </property_group>
    </instance>
  </service>
</service_bundle>

Displaying More Configuration Conversion Information

If you want to see more information for a sysidcfg file conversion or system configuration profile validation, specify the -v option in the js2ai command. When you specify the -v option, processing steps are displayed, and the error report displays zeroes if no errors occurred instead of omitting the error report.

# js2ai -sv
Processing: sysidcfg
Performing conversion on: sysidcfg
Generating SC Profile
Validating sc_profile.xml

                                Process  Unsupported  Conversion  Validation
Name                  Warnings  Errors   Items        Errors      Errors
-------------------   --------  -------  -----------  ----------  ----------
sysidcfg                     0        0            0           0           0
Successfully completed conversion

Validating an Output System Configuration Profile

Use the -V option to validate the resulting system configuration profile:

# js2ai -v -V ./sc_profile.xml
Validating sc_profile.xml

                                Process  Unsupported  Conversion  Validation
Name                  Warnings  Errors   Items        Errors      Errors
-------------------   --------  -------  -----------  ----------  ----------
sc_profile                   -        -            -           -           0
Successfully completed conversion