Transitioning From Oracle Solaris 10 Jumpstart To Oracle Solaris 11.3 Automated Installer
Transitioning From Oracle Solaris 10 Jumpstart To Oracle Solaris 11.3 Automated Installer
Transitioning From Oracle Solaris 10 Jumpstart To Oracle Solaris 11.3 Automated Installer
Oracle customers that have purchased support have access to electronic support through My Oracle Support. For information, visit http://www.oracle.com/pls/topic/lookup?
ctx=acc&id=info or visit http://www.oracle.com/pls/topic/lookup?ctx=acc&id=trs if you are hearing impaired.
Rfrence: E54837
Copyright 2011, 2015, Oracle et/ou ses affilis. Tous droits rservs.
Ce logiciel et la documentation qui l'accompagne sont protgs par les lois sur la proprit intellectuelle. Ils sont concds sous licence et soumis des restrictions d'utilisation et
de divulgation. Sauf stipulation expresse de votre contrat de licence ou de la loi, vous ne pouvez pas copier, reproduire, traduire, diffuser, modifier, accorder de licence, transmettre,
distribuer, exposer, excuter, publier ou afficher le logiciel, mme partiellement, sous quelque forme et par quelque procd que ce soit. Par ailleurs, il est interdit de procder toute
ingnierie inverse du logiciel, de le dsassembler ou de le dcompiler, except des fins d'interoprabilit avec des logiciels tiers ou tel que prescrit par la loi.
Les informations fournies dans ce document sont susceptibles de modification sans pravis. Par ailleurs, Oracle Corporation ne garantit pas qu'elles soient exemptes d'erreurs et vous
invite, le cas chant, lui en faire part par crit.
Si ce logiciel, ou la documentation qui l'accompagne, est livr sous licence au Gouvernement des Etats-Unis, ou quiconque qui aurait souscrit la licence de ce logiciel pour le
compte du Gouvernement des Etats-Unis, la notice suivante s'applique :
U.S. GOVERNMENT END USERS: Oracle programs, including any operating system, integrated software, any programs installed on the hardware, and/or documentation,
delivered to U.S. Government end users are "commercial computer software" pursuant to the applicable Federal Acquisition Regulation and agency-specific supplemental
regulations. As such, use, duplication, disclosure, modification, and adaptation of the programs, including any operating system, integrated software, any programs installed on the
hardware, and/or documentation, shall be subject to license terms and license restrictions applicable to the programs. No other rights are granted to the U.S. Government.
Ce logiciel ou matriel a t dvelopp pour un usage gnral dans le cadre d'applications de gestion des informations. Ce logiciel ou matriel n'est pas conu ni n'est destin tre
utilis dans des applications risque, notamment dans des applications pouvant causer un risque de dommages corporels. Si vous utilisez ce logiciel ou ce matriel dans le cadre
d'applications dangereuses, il est de votre responsabilit de prendre toutes les mesures de secours, de sauvegarde, de redondance et autres mesures ncessaires son utilisation dans
des conditions optimales de scurit. Oracle Corporation et ses affilis dclinent toute responsabilit quant aux dommages causs par l'utilisation de ce logiciel ou matriel pour des
applications dangereuses.
Oracle et Java sont des marques dposes d'Oracle Corporation et/ou de ses affilis. Tout autre nom mentionn peut correspondre des marques appartenant d'autres propritaires
qu'Oracle.
Intel et Intel Xeon sont des marques ou des marques dposes d'Intel Corporation. Toutes les marques SPARC sont utilises sous licence et sont des marques ou des marques
dposes de SPARC International, Inc. AMD, Opteron, le logo AMD et le logo AMD Opteron sont des marques ou des marques dposes d'Advanced Micro Devices. UNIX est une
marque dpose de The Open Group.
Ce logiciel ou matriel et la documentation qui l'accompagne peuvent fournir des informations ou des liens donnant accs des contenus, des produits et des services manant de
tiers. Oracle Corporation et ses affilis dclinent toute responsabilit ou garantie expresse quant aux contenus, produits ou services manant de tiers, sauf mention contraire stipule
dans un contrat entre vous et Oracle. En aucun cas, Oracle Corporation et ses affilis ne sauraient tre tenus pour responsables des pertes subies, des cots occasionns ou des
dommages causs par l'accs des contenus, produits ou services tiers, ou leur utilisation, sauf mention contraire stipule dans un contrat entre vous et Oracle.
Accs aux services de support Oracle
Les clients Oracle qui ont souscrit un contrat de support ont accs au support lectronique via My Oracle Support. Pour plus d'informations, visitez le site http://www.oracle.com/
pls/topic/lookup?ctx=acc&id=info ou le site http://www.oracle.com/pls/topic/lookup?ctx=acc&id=trs si vous tes malentendant.
Contents
5
Contents
Index..................................................................................................................51
6 Transitioning From Oracle Solaris 10 JumpStart to Oracle Solaris 11.3 Automated Installer July 2016
Tables
7
8 Transitioning From Oracle Solaris 10 JumpStart to Oracle Solaris 11.3 Automated Installer July 2016
Using This Documentation
Overview Describes how to migrate from Oracle Solaris 10 JumpStart to Oracle Solaris
11 Automated Installer
Audience Technicians, system administrators, and authorized service providers
Required knowledge Experience administering an Oracle Solaris system
Feedback
Provide feedback about this documentation at http://www.oracle.com/goto/docfeedback.
This chapter describes the similarities and differences between JumpStart and Automated
Installer (AI). It also provides resources that can help you migrate from JumpStart to AI.
JumpStart installs the Oracle Solaris 10 OS and earlier versions of the Oracle Solaris OS. AI
installs the Oracle Solaris 11 OS and update releases.
JumpStart and AI share the following characteristics:
Provide hands-free network installation of multiple clients by storing system configurations
on an install server
Provide for different kinds of installations on different clients in one automated installation
Install both x86 and SPARC clients
JumpStart AI
Step
command to associate clients with AI manifests
and system configuration profiles.
Specify client configuration. Use finish scripts and sysidcfg files. Use SMF (Oracle Solaris Service Management
Facility) system configuration profiles. Use scripts
executed by an SMF service that runs once at first
boot.
Which path to migrate from JumpStart to AI is best for your environment depends on the
resources you have available and how completely your would like to configure the AI client. A
more complete AI client configuration can require extra steps. Some of the strategies that you
could use when migrating to use the Automated Installer include the following:
Use one server as both a JumpStart install server and an AI install server.
This configuration allows you to support JumpStart capable systems from an Oracle Solaris
11 server. For more information, see Chapter 4, Installing Oracle Solaris 10 by Using
JumpStart on an Oracle Solaris 11 Server.
Use a software package repository for AI installations.
Use an Oracle Solaris 11 package repository on the Internet, such as pkg.oracle.com.
Make a local copy of a package repository, as described in Copying and Creating
Package Repositories in Oracle Solaris 11.3.
Create a custom ISO image.
See Creating a Custom Oracle Solaris 11.3 Installation Image for information about
creating a custom installation image.
Convert JumpStart rules, profiles, and configuration files to AI criteria, AI manifests,
and SMF system configuration profiles.
The following resources provide instructions on how to convert JumpStart data to AI data:
js2ai(1M) man page
Chapter 2, Converting JumpStart rules File and Profiles
Chapter 3, Converting sysidcfg Configuration Files
Dynamically derive an AI client provisioning manifest.
JumpStart begin scripts provide the ability to dynamically manipulate installation
parameters that are passed to the installer. AI provides the ability to query client attributes
at client installation time and dynamically derive a provisioning manifest customized for
that client. Environment variables specify hardware attributes of the client, and most of
12 Transitioning From Oracle Solaris 10 JumpStart to Oracle Solaris 11.3 Automated Installer July 2016
JumpStart to AI Migration Information
these attributes are the same as environment variables used with JumpStart begin scripts.
See Creating an AI Manifest at Client Installation Time in Installing Oracle Solaris 11.3
Systems.
Provide system configuration instructions.
See Chapter 11, Configuring the Client System in Installing Oracle Solaris 11.3 Systems
for information about creating SMF profiles.
See Chapter 12, Installing and Configuring Zones in Installing Oracle Solaris 11.3
Systems for information about creating an AI manifest and SMF profiles to install non-
global zones as part of an AI client installation.
Create an SMF service that runs once at first boot and executes a user-defined script.
See Chapter 13, Running a Custom Script During First Boot in Installing Oracle Solaris
11.3 Systems.
This chapter describes how to use the js2ai command to convert JumpStart rules and profiles
to AI criteria files and AI manifests.
AI uses client criteria to select the AI manifests that client systems should use to complete their
installation. When an AI manifest is added to an AI install service, you can specify criteria on
the command line or in a file. See Chapter 9, Customizing Installations in Installing Oracle
Solaris 11.3 Systems for more information about specifying AI criteria.
The following table compares JumpStart rules file keywords with AI criteria keywords.
AI uses these criteria to apply the correct AI manifest or system configuration profile to a
particular client.
JumpStart rules AI Criteria File Keyword Command-Line Example Criteria File Example
File Keyword
selection criteria, the AI install
service provides a default AI
manifest.
arch cpu -c cpu="sparc" <ai_criteria name="cpu">
<value>sparc</value>
</ai_criteria>
disksize Unsupported. AI installs on
the target specified in the AI
manifest if that disk is at least
the minimum required size.
domainname Unsupported.
hostaddress ipv4 -c ipv4="10.6.68.127" <ai_criteria name="ipv4">
<value>10.6.68.127</value>
</ai_criteria>
hostname Unsupported. To uniquely -c mac="0:3:ba:33:9d:b6" <ai_criteria_name="mac">
identify a host in AI, use either <value>0:3:ba:33:9d:b6</value>
the IP address as described in </ai_criteria>
hostaddress or use the MAC
address.
installed Unsupported. AI installs on
the target specified in the AI
manifest if that disk is at least
the minimum required size.
karch arch -c arch="i86pc" <ai_criteria name="arch">
<value>i86pc</value>
</ai_criteria>
memsize mem -c mem="2048" <ai_criteria name="mem">
<value>2048</value>
</ai_criteria>
model platform -c platform="SUNW,Sun-Fire- <ai_criteria_name="platform">
T200" <value>SUNW,Sun-Fire-T200</value>
</ai_criteria>
network - For an individual network single network address: single network address:
for network address or a range of addresses
addresses within one network address, -c ipv4="10.6.68.127" <ai_criteria name="ipv4">
<value>10.6.68.127</value>
use ipv4
range of addresses: </ai_criteria>
<ai_criteria name="ipv4">
<range>10.0.0.1 10.0.0.64</range>
</ai_criteria>
network - for For an individual network single network number: single network number:
network numbers number or a range of network
numbers, use network -c network="10.0.0.0" <ai_criteria name="network">
<value>10.0.0.0</value>
range of networks: </ai_criteria>
16 Transitioning From Oracle Solaris 10 JumpStart to Oracle Solaris 11.3 Automated Installer July 2016
Comparing Profile Keywords and AI Manifest Elements
JumpStart rules AI Criteria File Keyword Command-Line Example Criteria File Example
File Keyword
<ai_criteria name="network">
<range>
10.0.0.0
12.0.0.0
</range>
</ai_criteria>
osname Unsupported.
probe Unsupported.
totaldisk Unsupported. AI installs on
the target specified in the AI
manifest if that disk is at least
the minimum required size.
The following table compares JumpStart profile keywords with AI manifest elements. AI uses
XML manifest files to define the client installation. For more information about AI manifests,
see Chapter 10, Provisioning the Client System in Installing Oracle Solaris 11.3 Systems and
see the ai_manifest(4) man page.
To specify values that are not known until the client installation process has started, such as
devices specified using the any keyword, consider using a derived manifests script. You can use
a derived manifests script to specify swap size based on disk size or to specify mirroring based
on available disks, for example. For information about derived manifests scripts, see Creating
an AI Manifest at Client Installation Time in Installing Oracle Solaris 11.3 Systems.
Example: <target>
<disk whole_disk="true">
boot_device c1t0d0 <disk_name name="c1t0d0" name_type="ctd"/>
</disk>
<logical nodump="true" noswap="false"/>
</target>
boot_device device eeprom The value for the eeprom keyword (update for SPARC systems and preserve
for x86 systems) is not supported in AI. In AI, the EEPROM on SPARC
The Oracle Solaris 11 OS uses group packages as defined in the pkg(5) man
page. Group packages are specified just as any other package is specified in the
manifest. The default AI manifest includes the packages needed for a standard
Oracle Solaris 11 installation. You can customize this list of packages.
cluster cluster-name delete Unsupported. The delete switch is used only with the upgrade option of
install_type. AI does not support the upgrade install type; AI supports only
initial install.
dontuse Unsupported.
fdisk disk-name type size Example:
Example: <target>
<disk>
fdisk c0t3d0 solaris all <disk_name name="c0t3d0" name_type="ctd"/>
<partition action="create" name="1" part_type="191"/>
</disk>
<logical nodump="true" noswap="false"/>
</target>
For a full list of the disk and partition attributes supported by AI, see the
ai_manifest(4) man page.
Translation by js2ai:
For js2ai translation, the value of disk-name must be a device. A device of all
is not supported. The fdisk type must be solaris. A size of 0 or delete is not
supported. If partitioning is default and the rootdisk has not been set, js2ai
sets the first fdisk solaris partition encountered as the root disk.
filesys UFS file systems are not supported. AI installs ZFS file systems.
Translation by js2ai:
If there is no other way to determine the device to be used for root, the
device from the filesys line with the / mount point is used for the root
pool.
18 Transitioning From Oracle Solaris 10 JumpStart to Oracle Solaris 11.3 Automated Installer July 2016
Comparing Profile Keywords and AI Manifest Elements
Translation by js2ai:
The js2ai command supports translations only of the root file system (/) and
swap.
Example: The following partial AI manifest is for x86 platforms. For SPARC platforms,
no partition element is specified.
filesys mirror:rpool c6t0d0s0 c6t1d0s0 60048 /
<target>
<disk>
<disk_name name="c6t1d0" name_type="ctd"/>
<partition action="create" name="1" part_type="191">
<slice action="create" force="true"
in_vdev="rpool_vdev" in_zpool="rpool" name="0">
<size val="60048mb"/>
</slice>
</partition>
</disk>
<disk>
<disk_name name="c6t0d0" name_type="ctd"/>
<partition action="create" name="1" part_type="191">
<slice action="create" force="true"
in_vdev="rpool_vdev" in_zpool="rpool" name="0">
<size val="60048mb"/>
</slice>
</partition>
</disk>
<logical nodump="true" noswap="false">
<zpool is_root="true" name="rpool">
<vdev name="rpool_vdev" redundancy="mirror"/>
</zpool>
Translation by js2ai:
<software type="IPS">
<software_data action="uninstall">
<name>pkg:/SUNWpampkcs11</name>
</software_data>
</software>
Because AI only supports initial installations, you should not need to use an AI
manifest to delete packages.
20 Transitioning From Oracle Solaris 10 JumpStart to Oracle Solaris 11.3 Automated Installer July 2016
Comparing Profile Keywords and AI Manifest Elements
Translation by js2ai:
For js2ai, partitioning must be default or explicit. For explicit, only swap
and / are supported
partitioning existing Unsupported. For js2ai, partitioning must be default or explicit.
patch Unsupported. AI supports only initial_install.
To update your system or specific packages, use the pkg update command on
the installed system.
pool newpool auto auto auto device Example:
<target>
<disk>
<disk_name name="c1t0d0" name_type="ctd"/>
<partition action="create" name="1" part_type="191">
<slice action="create" force="true"
in_vdev="rpool_vdev" in_zpool="newpool" name="0"/>
</partition>
</disk>
<logical nodump="false" noswap="false">
<zpool is_root="true" name="newpool">
<vdev name="rpool_vdev" redundancy="none"/>
</zpool>
</logical>
</target>
Translation by js2ai:
If a pool is specified in a profile, js2ai creates the ZFS root pool using the
specified devices. The pool keyword supersedes all other keywords when
js2ai determines which devices to use for the ZFS root pool.
The js2ai command does not perform any validation of the pool size, swap
size, or dump size. You might need to adjust these sizes in the resulting AI
manifest to achieve a successful installation with this manifest.
pool newpool auto auto auto any For js2ai, if you specify any instead of a physical device name, you must
provide device information prior to the specification that includes the any
parameter. For example, you could provide a root_device or usedisk
specification before this pool specification. See Example 6, Fixing
mirrorpool.profile Errors, on page 34 for an example.
root_device c1t0d0s0 Example:
<target>
<disk>
<disk_name name="c1t0d0" name_type="ctd"/>
<partition action="create" name="1" part_type="191">
<slice action="create" force="true"
in_vdev="rpool_vdev" in_zpool="rpool" name="0"/>
</partition>
Translation by js2ai:
Translation by js2ai:
The js2ai command might use the specified device or devices to resolve
subsequent any or rootdisk specifications. Devices specified that are not used
for this purpose are added to the ZFS root pool by js2ai when that pool is not
mirrored.
Use the js2ai command with the -r option to convert both JumpStart rules and their associated
profiles to AI criteria and manifests. Initially, use the -S option to skip validation. This
command performs a conversion operation on the rules file and the profiles referenced by the
rules file.
Each profile referenced in the rules file is processed against the AI client provisioning
manifest, /usr/share/auto_install/manifest/default.xml. This step creates a directory
named AI_profile-name for each profile specified in the JumpStart rules file. The AI_profile-
name directory contains an AI criteria file in the form criteria-rule-number.xml that
corresponds to the rule that referenced this profile. The AI_profile-name directory also contains
AI manifest files in the form profile-name.arch.xml that correspond to the profile-name file.
When you receive a message that the conversion completed successfully, run the js2ai
command without the -S option to validate the output AI manifests. Validation errors must be
corrected in the AI manifest files.
22 Transitioning From Oracle Solaris 10 JumpStart to Oracle Solaris 11.3 Automated Installer July 2016
Using js2ai to Convert JumpStart rules File and Profiles to AI Criteria and Manifests
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 provide 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
rules file and profiles. The log file describes the problems.
To display more information about a rule file or profile conversion, use the -v
option. For more information, see Displaying Additional Profile Conversion
Information on page 37.
To validate a specific output AI manifest against the appropriate AI DTD, use the -V option.
For more information, see Validating an Output AI Manifest on page 38.
To convert one JumpStart profile only, use the -p option. See the examples in Fixing AI
Manifest Files on page 32.
Because js2ai does not have access to the client system profile references during the profile
translation process, js2ai attempts to determine the root disk during translation using a process
that matches JumpStart as much as possible.
The js2ai command performs the following steps to determine what device to use for the root
disk:
1. If the root_device keyword is specified in the profile, js2ai sets rootdisk to the device
on which the slice resides.
2. If rootdisk is not set and the boot_device keyword is specified in the profile, js2ai sets
rootdisk to the boot device.
3. If rootdisk is not set, partitioning default is specified, and a solaris fdisk entry is
encountered, js2ai sets rootdisk to the specified disk name.
4. If rootdisk is not set and a filesys cwtxdysz size / entry is specified in the profile,
js2ai sets rootdisk to the cwtxdysz disk specified in the entry.
5. If rootdisk is not set and a usedisk disk-name entry is specified in the profile, js2ai sets
rootdisk to the disk-name disk specified in the entry.
6. If rootdisk is not set and the following specification is encountered in the profile where
size is not 0 or delete and disk-name is not all, then rootdisk is set to this disk name.
The js2ai command performs the following steps to determine what device to use when the
any keyword is specified:
1. If the device is specified with the any keyword and the keyword action specified (non-
mirrored pool, or filesys with a / mount point), the device is set to rootdisk if rootdisk
is set.
2. If the device has not been translated and a usedisk statement exists in the profile, the
device specified with the any keyword is set to the device specified by the usedisk
statement.
3. If the device has not been translated and the action where the any keyword is specified
causes the ZFS root pool to be created, AI chooses the device unless a mirrored pool is
specified.
The js2ai command performs the following steps to determine which device to use for the
ZFS root pool. Once the ZFS root pool is determined, subsequent definitions encountered are
flagged as errors if they conflict with the ZFS root pool that has already been determined.
1. If the profile specifies the pool keyword, js2ai sets the ZFS root pool to the devices
specified by the pool keyword.
24 Transitioning From Oracle Solaris 10 JumpStart to Oracle Solaris 11.3 Automated Installer July 2016
Using js2ai to Convert JumpStart rules File and Profiles to AI Criteria and Manifests
2. If the ZFS root pool has not been determined and the profile specifies a file system with a
mount point of /, the ZFS root pool is created using the devices specified.
3. If the ZFS root pool has not been determined, all keywords in the profile have been
processed, and rootdisk is set, the ZFS root pool is created using the rootdisk device.
4. If the ZFS root pool has not been determined and the partition type is default, AI chooses
the device to use for the ZFS root pool.
5. If the ZFS root pool has not been determined and no errors have occurred during
processing, AI chooses the device to use for the ZFS root pool.
6. If the ZFS root pool is not a mirrored pool and one or more usedisk devices that were
specified have not been used for a rootdisk or any device translation, those disks are added
to the ZFS root pool.
JumpStart profiles use the cluster and package keywords to install software on the system.
The cluster keyword is not supported by AI. Because in IPS the syntax to install an
incorporation or group package is the same as the syntax to install any other package, if you
simply change cluster to package in the JumpStart profile, the js2ai command creates the
correct package installation specification in the AI manifest.
Tip - Verify the package names in the AI manifests. If a package specified for installation in an
AI manifest is not available from any publisher origin specified in that AI manifest, then that
client installation fails.
IPS package names are different from SVR4 package names. For example, the SVR4 package
SUNWpampkcs11 is renamed to library/security/pam/module/pam-pkcs11 in IPS.
If an SVR4 package name exists in IPS, you can install the IPS package by using the SVR4
name. For example, if an AI manifest specifies installation of the SUNWpampkcs11 package, the
library/security/pam/module/pam-pkcs11 package is automatically installed. In these cases,
the package has been renamed.
If an SVR4 package name does not exist in IPS, you must change the package name or delete
that specification from the AI manifest. For example, the SUNWCall and SUNWCuser packages
have not been renamed in IPS. If the AI manifest specifies those packages, the installation fails.
Use the pkg list command on an Oracle Solaris 11 system to determine whether a particular
package name can be used in your AI manifest. Be sure to use the -g option to list packages
from an IPS package repository origin that is specified in the AI manifest.
This message confirms that these two packages cannot be used in this AI manifest.
You can use the pkg list command to identify packages that have been renamed.
The r in the last column indicates that this package is renamed. You can use this name in the
AI manifest but you might want to use the pkg info command to determine the new name of
the package.
See the Renamed to line in the following output. The SUNWpampkcs11 package has been
renamed to library/security/pam/module/pam-pkcs11. You might want to specify library/
security/pam/module/pam-pkcs11 in your AI manifest for greater compatibility with future
Oracle Solaris updates.
26 Transitioning From Oracle Solaris 10 JumpStart to Oracle Solaris 11.3 Automated Installer July 2016
Using js2ai to Convert JumpStart rules File and Profiles to AI Criteria and Manifests
FMRI: pkg://solaris/SUNWpampkcs11@0.6.0,5.11-0.133:20101027T185011Z
$ pkg info -r pam-pkcs11
Name: library/security/pam/module/pam-pkcs11
Summary: The OpenSC PKCS#11 PAM Login Tools
Category: System/Security
State: Not installed
Publisher: solaris
Version: 0.6.0
Build Release: 5.11
Branch: 0.175.2.0.0.27.0
Packaging Date: Mon Nov 11 17:47:35 2013
Size: 1.74 MB
FMRI: pkg://solaris/library/security/pam/module/pam-pkcs11@0...
This example shows how you would replace SUNWmysql with database/mysql-51 in your AI
manifest.
The o in the last column indicates that this package is obsolete. This package name cannot
be used in an AI manifest. Use the pkg list command with wildcards or the pkg search
command to determine whether the package is available under a different name that can be
used.
Summary:
State: Not installed (Renamed)
Renamed to: database/mysql-51@5.1.37-0.133
consolidation/sfw/sfw-incorporation
Publisher: solaris
Version: 5.1.37
Build Release: 5.11
Branch: 0.133
Packaging Date: Wed Oct 27 18:49:18 2010
Size: 0.00 B
FMRI: pkg://solaris/SUNWmysql51@5.1.37,5.11-0.133:20101027T184918Z
# The following rule matches any system that is on the 924.222.43.0 network:
install_type initial_install
system_type server
root_device c1t0d0s0
28 Transitioning From Oracle Solaris 10 JumpStart to Oracle Solaris 11.3 Automated Installer July 2016
Using js2ai to Convert JumpStart rules File and Profiles to AI Criteria and Manifests
usedisk c1t0d0
fdisk rootdisk solaris all
partitioning explicit
filesys rootdisk.s1 5000 swap
filesys rootdisk.s0 10000 /
cluster SUNWCall
install_type initial_install
partitioning default
filesys mirror c6t0d0s0 c6t1d0s0 60048 /
cluster SUNWCuser
install_type initial_install
partitioning default
pool newpool auto auto auto mirror any any
cluster SUNWCuser
install_type initial_install
partitioning explicit
filesys rootdisk.s0 15000 /
filesys rootdisk.s1 1000 swap
cluster SUNWCall
Use the following command to process the rules 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 -rS
Process Unsupported Conversion Validation
Name Warnings Errors Items Errors Errors
------------------- -------- ------- ----------- ---------- ----------
rules 0 0 1 0 -
fdisk.profile 0 0 2 0 -
mirrorfilesys.profile 0 0 2 0 -
mirrorpool.profile 0 0 1 1 -
rootdisk.profile 0 0 1 2 -
Output is stored in directories named AI_profile-filename. AI criteria files created from the
JumpStart rules are named for the position of the rule in the rules file. AI manifests are named
profile-filename.arch.xml, where arch is generic, x86, or sparc.
# ls AI_*
AI_fdisk.profile:
fdisk.profile.x86.xml
AI_mirrorfilesys.profile:
criteria-2.xml mirrorfilesys.profile.generic.xml
AI_mirrorpool.profile:
criteria-2.xml mirrorpool.profile.generic.xml
AI_rootdisk.profile:
criteria-3.xml rootdisk.profile.generic.xml
You could fix this problem by changing hostname to hostaddress in the rules file.
30 Transitioning From Oracle Solaris 10 JumpStart to Oracle Solaris 11.3 Automated Installer July 2016
Using js2ai to Convert JumpStart rules File and Profiles to AI Criteria and Manifests
You could also fix this problem by creating an AI criteria file that specifies a MAC address or
IP address to identify the hostname system. For example, the following criteria file is equivalent
to the JumpStart rule hostname sample_host if 0:14:4F:20:53:97 is the MAC address of
sample_host:
To find the MAC address of a system, use the dladm command as described in the dladm(1M)
man page.
For the JumpStart rule hostaddress 10.6.68.127, the js2ai command automatically created
the AI criteria file AI_mirrorfilesys.profile/criteria-2.xml, replacing the JumpStart
hostaddress keyword with the AI ipv4 keyword:
For the JumpStart rule network 924.222.43.0, the js2ai command automatically created the
AI criteria file AI_rootdisk.profile/criteria-3.xml, specifying a range of IP addresses
based on the given network address:
For the JumpStart rule arch i386, the js2ai command automatically created the AI criteria file
AI_mirrorpool.profile/criteria-4.xml, replacing the JumpStart arch keyword with the AI
cpu keyword:
<ai_criteria name="cpu">
<value>
i386
</value>
</ai_criteria>
</ai_criteria_manifest>
The js2ai command often creates an AI manifest for each JumpStart profile even though errors
are reported. This section describes how to address some common errors so that the output AI
manifests are more complete.
The js2ai command showed the following errors for the fdisk.profile JumpStart profile:
These two lines are ignored and do not affect the output AI manifest. You could delete these
two lines if you want the conversion to avoid the error messages. The fdisk.profile file
would then have the following content:
install_type initial_install
root_device c1t0d0s0
usedisk c1t0d0
fdisk rootdisk solaris all
partitioning explicit
filesys rootdisk.s1 5000 swap
filesys rootdisk.s0 10000 /
Use the -p option of the js2ai command to process just this profile.
# js2ai -p fdisk.profile
Successfully completed conversion
<target>
<disk whole_disk="true">
<disk_name name="c1t0d0" name_type="ctd"/>
<partition action="create" name="1" part_type="191">
<slice name="1" action="create" force="true" is_swap="true">
32 Transitioning From Oracle Solaris 10 JumpStart to Oracle Solaris 11.3 Automated Installer July 2016
Using js2ai to Convert JumpStart rules File and Profiles to AI Criteria and Manifests
<size val="5000mb"/>
</slice>
<slice name="0" action="create" force="true" in_zpool="rpool" in_vdev="
rpool_vdev">
<size val="10000mb"/>
</slice>
</partition>
</disk>
<logical noswap="false" nodump="true" >
<zpool name="rpool" is_root="true">
<vdev name="rpool_vdev" redundancy="none"/>
<filesystem name="export" mountpoint="/export"/>
<filesystem name="export/home"/>
<be name="solaris"/>
</zpool>
</logical>
</target>
The js2ai command showed the following errors for the mirrorfilesys.profile JumpStart
profile:
In a JumpStart profile, you can omit the file-system parameter in the filesys mirror
specification. In a js2ai conversion, you cannot omit the file-system parameter, which must
have one of the following two values: / or swap.
Edit the mirrorfilesys.profile file to add / at the end of the filesys specification and to
delete the cluster line. The mirrorfilesys.profile file then has the following content:
install_type initial_install
partitioning default
filesys mirror c6t0d0s0 c6t1d0s0 60048 /
# js2ai -p mirrorfilesys.profile
<target>
<disk>
<disk_name name="c6t1d0" name_type="ctd"/>
<partition action="create" name="1" part_type="191">
<slice action="create" force="true" in_vdev="rpool_vdev" in_zpool="rpool" name="
0">
<size val="60048mb"/>
</slice>
</partition>
</disk>
<disk>
<disk_name name="c6t0d0" name_type="ctd"/>
<partition action="create" name="1" part_type="191">
<slice action="create" force="true" in_vdev="rpool_vdev" in_zpool="rpool" name="
0">
<size val="60048mb"/>
</slice>
</partition>
</disk>
<logical noswap="false" nodump="false" >
<zpool name="newpool" is_root="true">
<vdev name="rpool_vdev" redundancy="mirror"/>
<filesystem name="export" mountpoint="/export"/>
<filesystem name="export/home">
<be name="solaris">
</zpool>
</logical>
</target>
The js2ai command showed the following errors for the mirrorpool.profile JumpStart
profile:
34 Transitioning From Oracle Solaris 10 JumpStart to Oracle Solaris 11.3 Automated Installer July 2016
Using js2ai to Convert JumpStart rules File and Profiles to AI Criteria and Manifests
Use either of the following two methods to fix these errors. Both of these fixes result in the
same AI manifest output. See also How the any Keyword Is Translated on page 24.
Edit the mirrorpool.profile profile, replacing both any entries with physical device
names. Also, delete the cluster line. The mirrorpool.profile file will then have content
similar to the following example:
install_type initial_install
partitioning default
pool newpool auto auto auto mirror c6t0d0s0 c6t1d0s0
If you specify any instead of a physical device name in the vdev-list list in the pool
specification, you must provide device information prior to the specification that includes
the any parameter. Edit the mirrorpool.profile profile to add a usedisk specification
before the pool specification. Also, delete the cluster line. The mirrorpool.profile file
will then have content similar to the following example:
install_type initial_install
partitioning default
usedisk c6t0d0 c6t1d0
pool newpool auto auto auto mirror any any
</partition>
</disk>
<logical noswap="false" nodump="true">
<zpool name="rpool" is_root="true">
<vdev name="rpool_vdev" redundancy="mirror"/>
<filesystem name="export" mountpoint="/export"/>
<filesystem name="export/home">
<be name="solaris">
</zpool>
</logical>
</target>
The js2ai command showed the following errors for the rootdisk.profile JumpStart profile:
Use either of the following two methods to fix these errors. Both of these fixes result in the
same AI manifest output.
Edit the rootdisk.profile profile, replacing rootdisk. with c0t0d0. Also, delete the
cluster line. The rootdisk.profile file then has the following content:
install_type initial_install
partitioning explicit
filesys c0t0d0s0 15000 /
filesys c0t0d0s1 1000 swap
Edit the rootdisk.profile profile to add a root_device specification and to delete the
cluster line. The rootdisk.profile file then has the following content:
install_type initial_install
partitioning explicit
root_device c0t0d0s0
filesys rootdisk.s0 15000 /
filesys rootdisk.s1 1000 swap
36 Transitioning From Oracle Solaris 10 JumpStart to Oracle Solaris 11.3 Automated Installer July 2016
Using js2ai to Convert JumpStart rules File and Profiles to AI Criteria and Manifests
# js2ai -p rootdisk.profile
Successfully completed conversion
# js2ai -V ./AI_rootdisk.profile/rootdisk.profile.sparc.xml
Successfully completed conversion
# js2ai -v -V ./AI_rootdisk.profile/rootdisk.profile.sparc.xml
Validating rootdisk.profile.sparc.xml
38 Transitioning From Oracle Solaris 10 JumpStart to Oracle Solaris 11.3 Automated Installer July 2016
3
C H A P T E R 3
This chapter describes how to convert a sysidcfg file to an AI system configuration profile.
Much of the conversion can be done with the js2ai command. See the js2ai(1M) man page
for more information about the js2ai command.
AI system configuration profiles are SMF XML profiles that specify system configuration. For
more information about AI system configuration profiles, see Chapter 11, Configuring the
Client System in Installing Oracle Solaris 11.3 Systems.
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 on page 43 and in Example System
Configuration Profiles in Installing Oracle Solaris 11.3 Systems.
keyboard The js2ai command does not perform any translation. Make sure the keyboard specified in the
sysidcfg file is supported in Oracle Solaris 11.
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.
For more information on core locales, see Internationalization and Localization Changes in
Transitioning From Oracle Solaris 10 to Oracle Solaris 11.3.
40 Transitioning From Oracle Solaris 10 JumpStart to Oracle Solaris 11.3 Automated Installer July 2016
Using js2ai to Convert sysidcfg Files to System Configuration Profiles
Use the js2ai command with the -s option to convert any sysidcfg files that are associated
with this JumpStart configuration to system configuration profiles. Initially, use the -S option to
skip validation.
For each sysidcfg file processed, js2ai creates an AI system configuration profile 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.
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.
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.
To display more information for a conversion use the -v option with the js2ai
command. For more information, see Displaying Additional Configuration Conversion
Information on page 45.
To validate a specific output system configuration profile, run the js2ai command
with the -V option. See the example in Validating an Output System Configuration
Profile on page 46.
# js2ai -V path/sc_profile.xml
The warning relates to the inability of the js2ai command to generate the necessary data
structure from just the root_passwd keyword. If your sysidcfg file contained the root_passwd
keyword in it, js2ai would generate a system/config-user structure like the following:
42 Transitioning From Oracle Solaris 10 JumpStart to Oracle Solaris 11.3 Automated Installer July 2016
Using js2ai to Convert sysidcfg Files to System Configuration Profiles
In XML, a comment is started with <!--. To define the user necessary to support Oracle Solaris
11, remove the XML comment markers around the user_account property group structure.
Next, modify the user_account property structure to create the user that will have root role
privileges. If no root_password keyword was specified, comment out the root_account
property group structure.
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 -
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}
44 Transitioning From Oracle Solaris 10 JumpStart to Oracle Solaris 11.3 Automated Installer July 2016
Using js2ai to Convert sysidcfg Files to System Configuration Profiles
root_password=rJmv5LUXM1OcU
security_policy=none
nfs_domain=dynamic
# js2ai -sS
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 traditional 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 netn style name. Typically the primary interface
will be defined as net0. In order to address the user warning, edit the sc_profile.xml file
accordingly as outlined in the js2ai.log file.
# js2ai -sv
Processing: sysidcfg
Performing conversion on: sysidcfg
Generating SC Profile
Validating sc_profile.xml
# js2ai -v -V ./sc_profile.xml
Validating sc_profile.xml
46 Transitioning From Oracle Solaris 10 JumpStart to Oracle Solaris 11.3 Automated Installer July 2016
4
C H A P T E R 4
You can use JumpStart to install the Oracle Solaris 10 operating system on networked SPARC
and x86 platforms, but not to install the Oracle Solaris 11 OS. However, the JumpStart install
server can be an Oracle Solaris 11 system.
Your Oracle Solaris 11 server can do two different jobs:
Serve Oracle Solaris 11 OS installations using Automated Installer. For more information,
see Part III, Installing Using an Install Server, in Installing Oracle Solaris 11.3 Systems.
Serve Oracle Solaris 10 OS installations using JumpStart. This chapter describes how to
set up a JumpStart install server on an Oracle Solaris 11 system. For more information
about JumpStart, see Oracle Solaris 10 1/13 Installation Guide: Live Upgrade and Upgrade
Planning.
For information about how to set a static IP address, see the instructions in How to Configure
an IPv4 Interface in Configuring and Managing Network Components in Oracle Solaris 11.3
and the ipadm(1M) man page.
# pkg publisher
PUBLISHER TYPE STATUS URI
solaris origin online http://pkg.oracle.com/solaris/release/
# pkg install pkg:/system/boot/network
Packages to install: 1
Variants/Facets to change: 3
Create boot environment: No
Create backup boot environment: No
Services to change: 1
PHASE ACTIONS
Install Phase 34/34
PHASE ITEMS
Package State Update Phase 1/1
Image State Update Phase 2/2
PHASE ITEMS
Reading Existing Index 8/8
Indexing Packages 1/1
# /media/SOL_10_0113_SPARC/Solaris_10/Tools/setup_install_server /export/s10u11_sparc
Verifying target directory...
Calculating the required disk space for the Solaris_10 product
Calculating space required for the installation boot image
Copying the CD image to disk...
Copying Install Boot Image hierarchy...
Copying /boot netboot hierarchy...
48 Transitioning From Oracle Solaris 10 JumpStart to Oracle Solaris 11.3 Automated Installer July 2016
How to Set Up an Oracle Solaris 11 System as an Oracle Solaris 10 JumpStart Server
If the tftp package is not installed, use the following command to install it:
# pkg install pkg:/service/network/tftp
Once you have installed the tftp package, make sure the udp6 service is available and online.
# svcs udp6
STATE STIME FMRI
disabled 8:36:55 svc:/network/tftp/udp6:default
# svcadm enable network/tftp/udp6
# svcs udp6
10. If you plan to use this server as both a JumpStart install server and an AI install
server, link the /tftpboot directory to the /etc/netboot directory.
If the /etc/netboot directory does not exist, create it.
Although JumpStart uses /tftpboot for network booting, AI uses /etc/netboot. Therefore,
/tftpboot needs to be a symbolic link to /etc/netboot so that the two tools can coexist.
Tip - If you plan to use this server as only a JumpStart install server or only an AI install server,
then this step is not required. However, doing this step avoids failed netboot errors if you
change your plan later.
# ls /etc/netboot
/etc/netboot: No such file or directory
# mkdir -m 755 /etc/netboot
# ln -s /etc/netboot /tftpboot
# ls -l /tftpboot
lrwxrwxrwx 1 root root 12 Sep 14 8:46:51 /tftpboot -> /etc/netboot
Use the following commands to verify how the /export/home file system is shared, correct the
share options if needed, and then check how the file system is shared to verify the change. In
this example, the anon=0 option has not been set.
# share
home /export/home nfs sec=sys,ro
# share -F nfs -o ro,sec=sys,anon=0 /export/home
# share
home /export/home nfs anon=0,sec=sys,ro
50 Transitioning From Oracle Solaris 10 JumpStart to Oracle Solaris 11.3 Automated Installer July 2016
Index
51
Index
J L
js2ai command layout_constraint JumpStart profile keyword, 20
conversion warning message, 42
local_customization JumpStart profile keyword, 20
converting JumpStart files, 22
locale JumpStart profile keyword, 20
-D destination option, 41
determining the root disk, 23
determining the ZFS root pool, 24
package installation and, 25 M
-S skip option, 41 mac AI criteria keyword, 16
-s sysidcfg option, 41 manifest directives See AI manifest elements
translating the any keyword, 24 manifests See AI manifests
52 Transitioning From Oracle Solaris 10 JumpStart to Oracle Solaris 11.3 Automated Installer July 2016
Index
53
Index
timezone keyword
sysidcfg file, 41
timezone service
system configuration profile, 41
totaldisk JumpStart rules file keyword, 17
U
usedisk JumpStart profile keyword, 22
V
-v option
js2ai command, 45
-V validate option
js2ai command, 38, 46
-v verbose option
js2ai command, 37
W
warning message
from js2ai command, 42
Z
ZFS root pool
js2ai command process for determining, 24
54 Transitioning From Oracle Solaris 10 JumpStart to Oracle Solaris 11.3 Automated Installer July 2016