JavaScript is required to for searching.
Skip Navigation Links
Exit Print View
Oracle Solaris 11 Express Automated Installer Guide     Oracle Solaris 11 Express 11/10
search filter icon
search icon

Document Information

Preface

1.  Automated Installer Overview

2.  Setting Up an AI Install Server

3.  Customizing Installations

4.  Specifying Installation Instructions

5.  Configuring the Client System

6.  Setting Up DHCP for AI

7.  Installing Client Systems

8.  Automated Installations That Boot From Media

A.  Troubleshooting Automated Installations

B.  Automated Installer Installation Administration Commands

C.  Migrating From JumpStart to Automated Installer

Comparing JumpStart and Automated Installer

Converting JumpStart Rules to AI Criteria

Comparing Rules Keywords and Criteria Directives

Converting Rules Files to Criteria

Sample JumpStart Rules File

Equivalent AI Criteria Specifications

Converting a JumpStart Profile to an AI Manifest

Converting Profile Files to AI Manifests

Sample JumpStart Profile File

Equivalent AI Manifest Directives

Converting JumpStart Rules to AI Criteria

AI client criteria can be specified in the following two ways. The directives in the following table apply in both cases. See Chapter 3, Customizing Installations.

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 and SC (system configuration) manifest information to a particular client. JumpStart rules keywords that are not listed in this table do not have a comparable AI directive, or their functionality does not apply to AI.

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

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

Criteria file:

<ai_criteria name="cpu">
  <value>sparc</value>
</ai_criteria>
hostaddress 10.6.68.127
Command option: -c ipv4=10.6.68.127

Criteria file:

<ai_criteria name="ipv4">
  <value>10.6.68.127</value>
</ai_criteria>
hostname solaris
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>
karch i86pc
Command option: -c arch=i86pc

Criteria file:

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

Criteria file:

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

Criteria file:

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

Command option: -c ipv4=10.0.0.1-10.0.0.64

Criteria file:

<ai_criteria name="ipv4">
  <range>10.0.0.1 10.0.0.64</range>
</ai_criteria>

Converting Rules Files to Criteria

This section shows some sample JumpStart rules converted to AI criteria. The add-manifest and set-criteria subcommands associate client criteria with specified AI manifests. See Associate Client-Specific Installation Instructions With Install Services.

Sample JumpStart Rules File

In a JumpStart rules file, the first column contains rule keywords and rule values that identify client systems, the second column is the begin script, the third column is the profile, and the fourth column is the finish script.

The following sample JumpStart rules file identifies three groups of systems, and each group is assigned a different profile. In this example, no begin or finish scripts are specified for any of the three client groups. This sample rules file states the following rules:

memsize 2048-4096 && model SUNW - lx_prof -
karch i86pc - prog_prof -
any - generic_prof -
Equivalent AI Criteria Specifications

This section shows AI commands that are comparable to the three rules from the previous JumpStart sample. In these examples, the lx_prof profile has been converted to the manifest_lx.xml AI manifest and the prog_prof profile has been converted to the manifest_prog.xml AI manifest. Clients that do not match any of these specified criteria use the default AI manifest.

In the following example, any SPARC systems with a memory size between 2048 MB and 4096 MB will be installed using specifications in the manifest_lx.xml AI manifest.

# installadm add-manifest -m ./manifest_lx.xml -n s11-sparc \
-c arch="sparc" -c mem="2048-4096"

You can also put the criteria in a file and reference the file. The following command is equivalent to the preceding command if the content of the criteria_lx.xml file is as shown.

# installadm add-manifest -m ./manifest_lx.xml -n s11-sparc \
-C ./criteria_lx.xml
<ai_criteria_manifest>
  <ai_criteria name="cpu">
    <value>sparc</value>
  </ai_criteria>
  <ai_criteria name="mem">
    <range>
      2048
      4096
    </range>
  </ai_criteria>
</ai_criteria_manifest>

In the following example, any x86 systems will be installed using specifications in the manifest_prog.xml AI manifest.

# installadm set-criteria -m ./manifest_prog.xml -n s11-x86 \
-c arch="i86pc"