Go to main content

Automatically Installing Oracle® Solaris 11.4 Systems

Exit Print View

Updated: August 2021

Additional AI Server Configurations

The following are optional configurations of the AI server.

For examples of installadm command options, see Selected Options for Setting Up the AI Server. For more details, see the installadm(8) man page.

Setting the AI Server to Manage DHCP

The install set-server command with the following options sets the AI server to manage DHCP:

  • –m enables the AI server to manage DHCP.

  • –i sets the start of IP addresses to manage.

  • –c sets the count or range of addresses to manage.

This command syntax sets the DHCP's managed address range from to

$ installadm set-server -m -i -c 20

Configuring the AI Server's Web Server Files Directory

Note -  This section assumes that the AI server and the web server are running on the same system. This guide does not cover web server configuration. To set up a web server, consult other documentation, such as http://httpd.apache.org/docs/.

The web server's directories serve net images, AI manifests, system configuration profiles, and other files needed for installation.

The following properties of the svc:/system/install/server:default SMF service identify the locations for the web server's user files:

  • all_services/webserver_files_dir for files that do not need to be secure.

  • all_services/webserver_secure_files_dir for files that need to be secure.

To define the location of public files, use this set of commands:

$ svccfg -s svc:/system/install/server:default
svc:/system/install/server:default> setprop \
   all_services/webserver_files_dir = astring: public-location
svc:/system/install/server:default> refresh
svc:/system/install/server:default> quit

To define the location of secure files, use this set of commands:

$ svccfg -s svc:/system/install/server:default
svc:/system/install/server:default> setprop \
   all_services/webserver_secure_files_dir = astring: secure-location
svc:/system/install/server:default> refresh
svc:/system/install/server:default> quit

Tip  -  For greatest security, files in the webserver_secure_files_dir directory should be owned by user webservd and group webservd and have no world access.

To view the directories, use one of the following URLs:

  • http://AI-server:5555/files for unsecured files.

  • https://AI-server:5556/secure_files for secured files.

The AI-server can be a host name or an IP address. You can use port numbers other than the default ones. See Configuring the AI Web Server Port Number (-p Option) and Example 11, Configuring the Secure AI Web Server Port Number (P Option).

If the AI manifest specifies an IPS package repository that requires a certificate and key, you can store those publisher credentials, and then specify this URI in the AI manifest. Only clients that have security credentials assigned can access this directory.

Enabling Multicast DNS

Multiple AI servers can exist on the same subnet. To make these servers accessible to clients, enable multicast DNS (mDNS).

See also Multicast DNS and Service Discovery in Working With Oracle Solaris 11.4 Directory and Naming Services: DNS and NIS.

How to Enable Multicast DNS on the AI Server

Before You Begin

Ensure that your role has the appropriate rights profiles to perform this procedure. See Using Rights Profiles to Install Oracle Solaris.

  1. (Optional) Verify that the mDNS package is installed.
    $ pkg info dns/mdns

    If the package is absent, use the pkg install command to add it to the system.

  2. Update the name service switch information.

    Add mdns to the configuration of the config/host property.

    $ /usr/sbin/svccfg -s svc:/system/name-service/switch
    svc:/system/name-service/switch> setprop config/host = astring: "files dns mdns"
    svc:/system/name-service/switch> select system/name-service/switch:default
    svc:/system/name-service/switch:default> refresh
    svc:/system/name-service/switch> quit
  3. Enable the mDNS service.
    $ svcadm enable svc:/network/dns/multicast:default

Generating AI Telemetry Information

To enable the server to generate telemetry information about AI, use these commands:

  • installadm set-server --telemetry-enable switches on the telemetry feature.

  • installadm set-server --telemetry-frequency integer specifies the frequency in seconds that telemetry data from the client is returned to the AI server for you to monitor. A zero (0) value means data is returned immediately. By default, this frequency is set to 120 seconds.

For the two commands, you can use these options:

  • –telemetry-success specifies telemetry-related files the client feeds the AI server if the installation completes successfully.

  • –telemetry-failure specifies telemetry-related files the client feeds the AI server if the installation fails.

    For both options, specify one of the following values:

    • none – no files are returned.

    • intall_log – the /system/volatile/install_log is returned.

    • all_logs – in addition to the /system/volatile/install_log, other various SMF install logs that were created during installation are returned.

    • all_files – all the files that are listed in all_logs as well as the additional AI install files that are used to install the system are returned.

    • files – files specified by the system administrator are returned.

    • smf-fmri – the log file for the specified SMF service FMRI is returned.

For example, this command sets the server to generate all logs if failure occurs:

$ installadm set-server --telemetry-enable --telemetry-frequency 90 \
   --telemetry-failure all_logs

Set the AI server for telemetry information before you start the installation. Transmission of telemetry information begins when the client is booted with the boot_archive file.