JavaScript is required to for searching.
Skip Navigation Links
Exit Print View
Transitioning From Oracle Solaris 10 JumpStart to Oracle Solaris 11.1 Automated Installer     Oracle Solaris 11.1 Information Library
search filter icon
search icon

Document Information

Preface

1.  Comparing JumpStart and Automated Installer

2.  Converting Rules and Profile Files

Comparing Rules Keywords and Criteria Directives

Comparing Profile Keywords and AI Manifest Directives

Using js2ai To Convert JumpStart Rules and Profiles to AI Criteria and Manifests

How js2ai Converts JumpStart Device Specifications

How the System's Root Disk is Determined

How the any Device Is Translated

How the ZFS Root Pool is Determined

Converting Software Packages

Example Rules and Profiles Conversion Using js2ai

Sample JumpStart Rules File and Profile Files

Using js2ai With the Rules File Option

Equivalent AI Criteria Files

Equivalent AI Manifest Files

Fix the fdisk.profile Errors

Fix the mirrorfilesys.profile Errors

Fix the mirrorpool.profile Errors

Fix the rootdisk.profile Errors

Displaying More Profile Conversion Information

Validating an Output AI Manifest

3.  Converting Configuration Files

4.  Installing Oracle Solaris 10 Using JumpStart on an Oracle Solaris 11 Server

Comparing Rules Keywords and Criteria Directives

The following table compares JumpStart rules keywords with AI criteria directives. AI uses these criteria to apply the correct AI manifest or system configuration profile to a particular client.

Table 2-1 Comparing JumpStart Rules File Keywords and AI Criteria Directives

JumpStart Rules File Keyword
AI Criteria File Directives
any
Unsupported. For client systems that do not match any selection criteria, the AI install service provides a default AI manifest.
arch
cpu
Command option: -c cpu=sparc

Criteria file:

<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
Command option: -c ipv4=10.6.68.127

Criteria file:

<ai_criteria name="ipv4">
  <value>10.6.68.127</value>
</ai_criteria>
hostname
Unsupported. To uniquely identify a host in AI, use either the IP address as shown above, or use the MAC address.

Command option: -c mac=0:3:ba:33:9d:b6

Criteria file:

<ai_criteria_name="mac">
  <value>0:3:ba:33:9d:b6</value>
</ai_criteria>
installed
Unsupported. AI installs on the target specified in the AI manifest if that disk is at least the minimum required size.
karch
arch
Command option: -c arch=i86pc

Criteria file:

<ai_criteria name="arch">
  <value>i86pc</value>
</ai_criteria>
memsize
mem
Command option: -c mem=2048

Criteria file:

<ai_criteria name="mem">
  <value>2048</value>
</ai_criteria>
model
platform
Command option: -c platform=SUNW,Sun-Fire-T200

Criteria file:

<ai_criteria_name="platform">
  <value>SUNW,Sun-Fire-T200</value>
</ai_criteria>
network
Use network, network with a range, or ipv4 with a range.

Command option, single network value: -c network="10.0.0.0"

Criteria file, single network value:

<ai_criteria name="network">
  <value>10.0.0.0</value>
</ai_criteria>

Command option, ipv4 range: -c ipv4=10.0.0.1-10.0.0.64

Criteria file, ipv4 range:

<ai_criteria name="ipv4">
  <range>10.0.0.1 10.0.0.64</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.