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

Matching Installation Instructions With Client Characteristics

Default AI Manifest

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

Matching Installation Instructions With Client Characteristics

When you use AI, you first set up a DHCP server and an AI server. The AI server has at least one AI boot image and an AI service that is associated with that AI boot image. When a client boots, DHCP directs the client to the install server. The client is associated with a particular install service. The install service uses the methods described in this chapter to match the client with the correct installation and configuration instructions to use.

To define installations that use different AI images (a SPARC image and an x86 image, or different Oracle Solaris versions), create a separate service for each image. See Set Up the Install Image and Install Service.

To associate a client with a specific install service, add that client to the install service. See Chapter 7, Installing Client Systems. Specify the MAC address of the client and the name of the install service for this client to use. When the client with this MAC address boots, DHCP directs the client to the install server, and the client uses the specified install service.

To define more than one type of installation for one AI image, create additional AI manifests and add the new AI manifests to the AI service for that AI image. Specify criteria that define which clients should use which AI manifest. See Associate Client-Specific Installation Instructions With Install Services.

To create a custom AI manifest, start with a copy of the default manifest in net_install_image_path/auto_install/default.xml for the service. See also Default AI Manifest and Annotated AI Manifest for examples. To change installation specifications such as target disk or additional packages to install, see Chapter 4, Specifying Installation Instructions. To change configuration specifications such as user account or root role password, see Chapter 5, Configuring the Client System.

An AI manifest is selected for a client according to the following algorithm:

Table 3-1 Criteria Tags and Criteria Hierarchy

Criteria Name
Description
Examples
arch
uname -m
i86pc or sun4u or sun4v
<ai_criteria name="arch">
    <value>i86pc</value>
</ai_criteria>
mac
MAC address, or range of MAC addresses
<ai_criteria name="mac">
    <value>0:14:4F:20:53:97</value>
</ai_criteria>
<ai_criteria name="mac">
   <range>
       0:14:4F:20:53:94
       0:14:4F:20:53:A0
   </range>
</ai_criteria>
ipv4
IP address, or range of IP addresses
<ai_criteria name="ipv4">
    <value>10.6.68.127</value>
</ai_criteria>
<ai_criteria name="ipv4">
    <range>
        10.6.88.1
        10.6.68.200
    </range>
</ai_criteria>
cpu
uname -p
i386 or sparc
<ai_criteria name="cpu">
    <value>sparc</value>
</ai_criteria>
platform
uname -i
i86pc or SUNW,Sun-Fire-T200 or SUNW,Sun-Fire-880
<ai_criteria name="platform">
    <value>SUNW,Sun-Fire-T200</value>
</ai_criteria>
mem
Memory size in megabytes, or a range of memory size
This example matches clients with at least 2 Gbytes of memory. The unbounded keyword indicates no upper limit in a range.
<ai_criteria name="mem">
     <range>
        2048
        unbounded
     </range>
</ai_criteria>

Example 3-1 Matching Clients With AI Manifests

In the following example, two custom AI manifests have been added to the same install service. The client criteria associated with those manifests are as shown.

The manifest_x86.xml AI manifest was added to the service with the following criteria file that specifies client architecture:

<ai_criteria_manifest>
    <ai_criteria name="arch">
        <value>i86pc</value>
    </ai_criteria>
</ai_criteria_manifest>

The manifest_mac1.xml AI manifest was added to the service with the following criteria file that specifies a client MAC address:

<ai_criteria_manifest>
    <ai_criteria name="mac">
        <value>00:14:4f:a7:65:70</value>
    </ai_criteria>
</ai_criteria_manifest>

If an x86 client is being installed, it is assigned manifest_x86.xml.

If a SPARC client with MAC address 00:14:4f:a7:65:70 is being installed, it is assigned manifest_mac1.xml.

If a SPARC system with some other MAC address is being installed, it is assigned the default AI manifest.