Go to main content

Installing Oracle® Solaris 11.3 Systems

Exit Print View

Updated: April 2019
 
 

How to Create an Install Service

Create an install service for each client architecture, SPARC or x86, and for each version of the Oracle Solaris operating system you want to be able to install.

  1. Become an administrator.

    For more information, see Using Your Assigned Administrative Rights in Securing Users and Processes in Oracle Solaris 11.3.

  2. Verify DHCP service.

    Make sure that local or remote DHCP support is set up as appropriate.

  3. Create the install service.

    See the installadm(1M) man page for all of the options that you can use. For example:

    installadm create-service -s source -y
    source

    Specifies the data source for the net image. The value can be the FMRI identifier of the IPS AI net image package, which by default is install-image/solaris-auto-install. The value can also be the full pathname of an AI ISO image file.

    –y

    Suppresses the prompt to confirm the use of the automatically generated image path

Example 17  Creating a SPARC Install Service Using an ISO File With DHCP Enabled on the AI Server

This example creates an install service for SPARC clients where the network consists of a single subnet and the AI server also acts as the DHCP server for the network. If a DHCP server is not yet configured, an ISC DHCP server is configured. If an ISC DHCP server is already configured, that DHCP server is updated.

If the AI client is not on a subnet that the AI server is directly connected to and the AI server is multihomed, use the –B option to provide the address of the boot file server (usually an IP address on this system). This option should only be necessary when multiple IP addresses are configured on the AI server and DHCP relays are employed. In other configurations, the software can determine this automatically.

The only difference in the output if this command was run with an x86 ISO file, would be the name of the ISO file, the name and architecture type of the created services, and the description of the boot files that are created. For x86 output, see Example 18, Creating an X86 Install Service Using an IPS Package.

# installadm create-service -s /var/tmp/images/sparc/sol-11_3-ai-sparc.iso -y
  0% : Service svc:/network/dns/multicast:default is not online.  Installation services will not be advertised via multicast DNS.
  0% : Creating service from: /var/tmp/images/sparc/sol-11_3-ai-sparc.iso
 36% : Transferring contents
 36% : Creating sparc service: solaris11_3-sparc
 36% : Image path: /export/auto_install/solaris11_3-sparc
 36% : Setting "solaris" publisher URL in default manifest to:
 36% :  http://pkg.oracle.com/solaris/release/
 36% : Creating default-sparc alias
 36% : Setting "solaris" publisher URL in default manifest to:
 36% :  http://pkg.oracle.com/solaris/release/
 36% : Setting the default SPARC bootfile(s) in the local DHCP configuration to:
 36% :  http://203.0.113.2:5555/cgi-bin/wanboot-cgi
100% : Created Service: 'solaris11_3-sparc'
100% : Refreshing SMF service svc:/system/install/server:default
100% : Restarting SMF service svc:/network/dhcp/server:ipv4
# installadm list
Service Name           Status Arch  Type Secure Alias Aliases Clients Profiles Manifests
------------           ------ ----  ---- ------ ----- ------- ------- -------- ---------
default-sparc          on     sparc iso  no     yes   0       0       0        1
solaris11_3-sparc      on     sparc iso  no     no    1       0       0        1
  
Example 18  Creating an X86 Install Service Using an IPS Package

This example uses an x86 AI server without a local DHCP service. it creates an install service for x86 clients using an net image from an IPS package. This command also illustrates default behavior when options are not specified. If no other information is provided when using an IPS package, the architecture for the AI client is assumed to match the architecture of the AI server. If this AI server is a SPARC system, you must supply the –a i386 option to specify that you want to create an x86 install service.

In addition to the boot file required for DHCP configuration, this command output also provides the boot server IP address required for DHCP configuration.

The only difference in the output if this command was run to create a SPARC, would be the name and architecture type of the services, and the description of the boot files that are created. For SPARC output, see Example 17, Creating a SPARC Install Service Using an ISO File With DHCP Enabled on the AI Server.

# installadm create-service -y
  0% : Creating service from: pkg:/install-image/solaris-auto-install
  0% : Using publisher(s):
  0% :     solaris: http://pkg.oracle.com/solaris/release/
  5% : Refreshing Publisher(s)
  7% : Startup Phase
 15% : Planning Phase
 61% : Download Phase
 90% : Actions Phase
 91% : Finalize Phase
 91% : Creating i386 service: solaris11_3-i386
 91% : Image path: /export/auto_install/solaris11_3-i386
 91% : Setting "solaris" publisher URL in default manifest to:
 91% :  http://pkg.oracle.com/solaris/release/
 91% : DHCP is not being managed by install server.
 91% : Creating default-i386 alias
 91% : Setting "solaris" publisher URL in default manifest to:
 91% :  http://pkg.oracle.com/solaris/release/
 91% : DHCP is not being managed by install server.
 91% :  No local DHCP configuration found. This service is the default
 91% :  alias for all PXE clients. If not already in place, the following should
 91% :  be added to the DHCP configuration:
 91% : Boot server IP: 203.0.113.2
 91% : Boot file(s):
 91% :     bios clients (arch 00:00):  default-i386/boot/grub/pxegrub2
 91% :     uefi clients (arch 00:07):  default-i386/boot/grub/grub2netx64.efi
 91% :
100% : Created Service: 'solaris11_3-i386'
100% : Refreshing SMF service svc:/system/install/server:default
# installadm list
Service Name           Status Arch  Type Secure Alias Aliases Clients Profiles Manifests
------------           ------ ----  ---- ------ ----- ------- ------- -------- ---------
default-i386           on     i386  pkg  no     yes   0       0       0        1
solaris11_3-i386       on     i386  pkg  no     no    1       0       0        1
Example 19  Creating an Install Service for a Different Architecture

By default, when an install service is created, the architecture will be the same as the AI server. If you want to create a service of another architecture, use the –a option. The following example creates an x86 service on a SPARC AI server.

# installadm create-service -n solaris11_3-i386 -a i386 -y
Example 20  Creating a Service That Automatically Installs an X86 Client

The default entry in the GRUB menu on an x86 client will not automatically start AI. To customize the GRUB menu so that the installation is started automatically, you can use the following command:

# installadm create-service -s /var/tmp/images/i386/sol-11_3-ai-x86.iso -y -b install=true