Go to main content

Installing Oracle® Solaris 11.3 Systems

Exit Print View

Updated: April 2019
 
 

What Happens When an Install Service Is Created?

When an install service is created, the AI SMF service, system/install/server, is enabled if it was not already enabled. The install service image is mounted at /etc/netboot/svcname. For SPARC install services, the wanboot.conf file is at the root of the install service image. For x86 install services, the GRUB menu is at the root of the install service image.

When the first install service for a particular architecture is created on an AI server, an alias of that service, default-i386 or default-sparc, is automatically created. This default service is a complete service with its own manifests and profiles, but this default service shares a net image with the explicitly created service. This default service is used for all installations on AI clients of that architecture that are not explicitly associated with a different install service with the create-client subcommand.

To change the service that default-arch service aliases, set the aliasof property using the set-service subcommand. Manifests and profiles that were added to either service remain the same after resetting an alias. The only change is the net image that the service uses. See Managing Install Services for more information about setting the aliasof property. To update the net image of the service for which the default-arch service is an alias, use the update-service subcommand as shown in Updating an Existing Install Service.

If a default-arch alias is changed to a new install service and a local ISC DHCP configuration is found, this default alias boot file is set as the default DHCP server-wide boot file for that architecture if the value of the all_services/manage_dhcp property is true. See Example 15, Disabling Automatic Updates of the Local DHCP Service on an AI Server for more information about the all_services/manage_dhcp property.

The installadm create-service command also provides a net image on a web server running on port 5555. For example, the web server address might be http://203.0.113.5:5555/solaris11_3-i386. See Example 11, Configuring the AI Web Server Port Number to use a different port.

    The following operations are performed as a result of executing the installadm create-service command:

  1. If you don't define an install service name, a name will be generated for you. You can specify the service name by including the –n option in the command line when you create the install service.

  2. If no net image source option is specified, the newest version of the install-image/solaris-auto-install package is retrieved from the first publisher in the AI server publisher list that provides this package.

  3. The default install service net image directory is created. The directory name includes the service name, such as /export/auto_install/solaris11_3-sparc or /export/auto_install/solaris11_3-i386. To suppress confirmation prompts, specify the –y option.

  4. Depending on the source for the net image, one of these two operations occur:

    1. If no net image source option is specified, the install-image/solaris-auto-install package is installed into the net image directory.

      By default, the variant of the install-image/solaris-auto-install package that is installed matches the architecture of the AI server. If the AI server is an x86 system and you want to create a SPARC install service on this server, you would need to use the –a option. See Example 19, Creating an Install Service for a Different Architecture for information about the –a option.

    2. If a net image source option is specified, the image file is unpacked or installed into the net image directory.

  5. Files are created according to the install service architecture.

    • For SPARC clients: The wanboot.conf file for this service is generated at /etc/netboot/wanboot.conf

    • For x86 clients: The GRUB menu is mounted at /etc/netboot/solaris11_3-i386/grub.cfg.

  6. The AI SMF service, system/install/server, is refreshed to mount /export/auto_install/service-name as /etc/netboot/service-name.

  7. If this is the first SPARC install service created on this AI server, the default-sparc service alias is automatically created. Also, the /export/auto_install/service-name is mounted as /etc/netboot/default-sparc.

    For the first x86 install service, the default-i386 service alias is created and the /etc/netboot/default-i386 mount point would be created.

  8. For SPARC clients, the configuration file /etc/netboot/wanboot.conf is symbolically linked to /etc/netboot/default-sparc/wanboot.conf. Also, the configuration file /etc/netboot/system.conf is symbolically linked to /etc/netboot/default-sparc/system.conf.

  9. A DHCP service is created if necessary, and IP addresses are provisioned. If DHCP service is already set up on this server, the –i and –c options update the DHCP server with new IP addresses for this service. The svc:/network/dhcp/server service is online.

  10. For configurations that do not use a local DHCP service:

    • For SPARC clients: The boot file required for DHCP configuration, http://203.0.113.5:5555/cgi-bin/wanboot-cgi, is provided.

    • For x86 clients: The boot server IP address required for DHCP configuration is provided. The boot files required for DHCP configuration, default-i386/boot/grub/pxegrub2 and default-i386/boot/grub/grub2netx64.efi, are also provided.

  11. If a local ISC DHCP server is already configured, the boot file of the new default-sparc or default-i386 alias is set as the default boot file for all matching AI clients. This assignment occurs regardless of whether the –i and –c options are used.