Maintaining an Install Server

After you have set up an AI install server, you might want to perform some of the following tasks. See also the installadm(1M) man page.

Adding, Modifying, or Deleting an Install Service
Associating Clients With Install Services
Associating Client-Specific Installation Instructions With Install Services
Associating Client-Specific Configuration Instructions With Install Services
Exporting an AI Manifest or a System Configuration Profile
Modifying Criteria for an AI Manifest or a System Configuration Profile
Listing All Install Services on the Install Server
Listing Clients Associated With Install Services
Listing All AI Manifests and System Configuration Profiles

Adding, Modifying, or Deleting an Install Service

You need a separate install service for each different client architecture that you plan to install and for each different version of the Oracle Solaris 11 OS that you plan to install on client systems.

Creating an Install Service

Use the following command to create an install service. See Creating an AI Install Service for examples.

installadm create-service [-n svcname] [-s source]
    [-p publisher=origin] [-a architecture]
    [-d imagepath] [-y] [-t aliasof]
    [-i start] [-c count]
    [-b property=value,...] [-B server]

-n svcname

The value of the svcname argument can consist of alphanumeric characters, underscores (_), and hyphens (-). The first character of svcname cannot be a hyphen. The length of the value of the svcname argument cannot exceed 63 characters. If you do not provide a name for the install service, a default name is assigned. The default name indicates the architecture and the OS version.

-s source

The source argument specifies the data source for the net image. The value of source can be one of the following:

The FMRI identifier of the IPS AI net image package, which is install-image/solaris-auto-install in the Oracle Solaris 11.1 release.
The full path name of an AI ISO net image file.

If you do not specify source, the newest available version of the install-image/solaris-auto-install package is used. The package is retrieved from the publisher specified by the -p option or from the first publisher in the install server's publisher preference list that provides an instance of the package.

To install a different version of the package, or to install the package from a different publisher, specify the version or publisher in the FMRI. For example, specify pkg://publisher/install-image/solaris-auto-install or pkg://publisher/install-image/solaris-auto-install@version. Use the -p option to specify the particular publisher origin.

-p publisher=origin

This option is used only when the net image source is an IPS package. This option specifies the IPS package repository from where you want to retrieve the install-image/solaris-auto-install package. The value of the publisher argument is the publisher name, and the origin is the URI, as in solaris=http://pkg.oracle.com/solaris/release/.

If the -p option is not specified, the publisher used is the first publisher in the install server's publisher preference list that provides an instance of the package.

-a architecture

This option is used only when the net image source is an IPS package. The architecture argument specifies the architecture of the clients to be installed with this service. You can specify either i386 or sparc. The default value is the architecture of the install server.

-d imagepath

The value of the imagepath argument is the path at which to create the net image. The install-image/solaris-auto-install package is installed to this location, or the specified ISO file is unpacked at this location. If you do not specify imagepath, the image is created in a svcname directory at the location defined by the value of the all_services/default_imagepath_basedir property. For the default value of this property, or to change the value of this property, see Configuring the Default Image Path. If you do not specify imagepath, you are prompted to confirm that you want to use the automatically generated location. Specify the -y option to suppress this prompt.

-y

Specify the -y option to suppress the prompt to confirm the use of the automatically generated image path.

-t aliasof

This option designates the new service as an alias. The new service shares the net image of the aliasof service but has its own manifests, profiles, and clients.

-i start

This option specifies the starting IP address in a range to be added to the local DHCP configuration. The number of IP addresses is provided by the -c option. If a local ISC DHCP configuration does not exist, an ISC DHCP server is started if the value of the all_services/manage_dhcp property is true. See Automatically Updating the ISC DHCP Configuration for more information about the all_services/manage_dhcp property.

-c count

Sets up a total number of IP addresses in the DHCP configuration equal to the value of the count. The first IP address is the value of start that is provided by the -i option.

-b property=value,...

For x86 services only. This option sets a property value in the service-specific grub.cfg file in the service image. Use this option to set boot properties that are specific to this service. This option can accept multiple comma-separated property=value pairs.

-B server

Use this option to provide the IP address of the boot server from which clients should request boot files. This option is required only if this IP address cannot be determined by other means.

Modifying Install Service Properties

Use the installadm set-service command to specify a property and value to set for the svcname install service.

installadm set-service -o property=value svcname

The property=value pair must be one of the following:

aliasof=aliasof

Changes the install service that the svcname service is an alias of.

Setting this property changes the svcname service to be an alias of the aliasof service. The svcname service must already be an alias. The default-arch install services are aliases. A service created using the -t option of create-service is an alias. Use the installadm list command as shown in Listing All Install Services on the Install Server to confirm that svcname is an alias.

Manifests, profiles, and client bindings that were added to either svcname or aliasof remain the same after resetting the alias. The only change is which net image the svcname service uses.

Manifests and profiles that were added to svcname prior to setting the alias are revalidated when the alias is reset since the AI DTDs and SMF DTDs associated with the new net image could be different. This validation is the same validation that is performed by create-manifest and create-profile, described below.

default-manifest=manifest

Designates a particular manifest or derived manifests script that is already registered with the specified service to be the default manifest or script for that service. Use the following command to show a list of manifests and scripts registered with this service:

$ installadm list -n svcname -m

imagepath=newpath

Relocates the image for a service after that service has been created:

$ pfexec installadm set-service -o imagepath=/export/aiimages/solaris11_1-i386 solaris11_1-i386

Updating an Install Service

Use the following command to update the image associated with an alias of a service that was created using an IPS AI net image package.

installadm update-service [-p|--publisher publisher=origin]
    [-s|--source FMRI] svcname

This command updates the image associated with svcname, where svcname is an alias of a service that was created using an IPS AI net image package. A new service is created with the updated image, and svcname is aliased to the new service.

-p|--publisher publisher=origin

This option specifies the IPS package repository from which to update the svcname image. An example value is solaris=http://pkg.oracle.com/solaris/release/.

If the -p option is not specified, the publisher used is the publisher that was used to create the image of the service for which svcname is an alias. The following pkg publisher command shows how to display the svcname publisher:

$ installadm list
Service Name     Alias Of          Status  Arch  Image Path
------------     --------          ------  ----  ----------
default-i386     solaris11_1-i386  on      i386  /export/auto_install/solaris11_1-i386
solaris11_1-i386 -                 on      i386  /export/auto_install/solaris11_1-i386
$ pkg -R /export/auto_install/solaris11_1-i386 publisher
PUBLISHER        TYPE     STATUS   URI
solaris          origin   online   http://pkg.oracle.com/solaris/release/

-s|--source FMRI

This option specifies the FMRI of the net image package for the update.

If the -s option is not specified, the newest available version of the install-image/solaris-auto-install package is used from the publisher specified in the description of the -p option.

Renaming an Install Service

Use the following command to rename svcname to newsvcname:

installadm rename-service svcname newsvcname

The value of the newsvcname argument can consist of alphanumeric characters, underscores (_), and hyphens (-). The first character of newsvcname cannot be a hyphen. The length of the value of the newsvcname argument cannot exceed 63 characters.

Enabling or Disabling an Install Service

Use the following command to enable the svcname install service:

installadm enable svcname

Use the following command to disable the svcname install service:

installadm disable svcname

When you disable an install service, any clients associated with that install service remain associated. See Associating Clients With Install Services. This means that when you re-enable an install service, you do not need to re-associate the clients of that install service.

If you disable the default install service for an architecture or the service that the default service is aliased to, any clients of that architecture that are not associated with some other service will not boot.

Deleting an Install Service

Use the following command to delete the svcname install service:

installadm delete-service [-r] [-y] svcname

This command deletes the AI manifests and system configuration profiles, the net image, and the web server configuration for the svcname install service. If the service is a default alias and a local ISC DHCP configuration exists, the boot file associated with this service is removed from the ISC DHCP configuration if the value of the all_services/manage_dhcp property is true. See Automatically Updating the ISC DHCP Configuration for more information about the all_services/manage_dhcp property.

Use the -r option to remove any clients associated with this service and any services aliased to this service. Use the -y option to suppress confirmation prompts.

If you delete the default install service for an architecture or the service that the default service is aliased to, any clients of that architecture that are not associated with some other service will not boot. You will be prompted to confirm the operation.

Associating Clients With Install Services

The installadm create-client command associates a client with a specific install service. See Setting Up an Install Client for more examples and sample output.

Adding a Client To an Install Service

Use the installadm create-client command to associate the macaddr client with the svcname install service and to provide custom client settings for x86 clients.

installadm create-client [-b property=value,...]
    -e macaddr -n svcname

If the client is an x86 system and a local ISC DHCP configuration exists, the client is configured in the ISC DHCP configuration if the value of the all_services/manage_dhcp property is true. See Automatically Updating the ISC DHCP Configuration for more information about the all_services/manage_dhcp property.

To find the MAC address of a system, use the dladm command as shown in the following example. See the dladm(1M) man page for more information.

$ dladm show-linkprop -p mac-address
LINK   PROPERTY       PERM VALUE             DEFAULT POSSIBLE
net0   mac-address    rw   8:0:20:0:0:1      8:0:20:0:0:1      --
net1   mac-address    rw   0:14:4f:45:c:2d   0:14:4f:45:c:2d   --

For x86 client systems, use the -b option to set boot properties in the client-specific grub.cfg file in /etc/netboot.

The following command adds the client with MAC address 00:14:4f:a7:65:70 to the solaris11_1-sparc install service:

$ pfexec installadm create-client -e 00:14:4f:a7:65:70 -n solaris11_1-sparc

The following example adds an x86 client and redirects installation output to a serial console:

$ pfexec installadm create-client -e c0ffeec0ffee -n solaris11_1-i386 -b console=ttya

Associating a Client With a Different Install Service

A client can be associated with only one install service. If you run the installadm create-client command more than once and specify the same MAC address each time, that client is associated only with the install service that was specified last.

Deleting a Client From an Install Service

Use the installadm delete-client command to delete the macaddr client from its associated install service.

installadm delete-client macaddr

If the client is an x86 system and a local ISC DHCP configuration exists, the client is unconfigured in the ISC DHCP configuration if the value of the all_services/manage_dhcp property is true. See Automatically Updating the ISC DHCP Configuration for more information about the all_services/manage_dhcp property.

The following command deletes the client with MAC address 00:14:4f:a7:65:70. You do not need to specify the service name because a client can be associated with only one install service.

$ pfexec installadm delete-client 00:14:4f:a7:65:70

Associating Client-Specific Installation Instructions With Install Services

You can specify multiple sets of installation instructions for each install service, and you can specify which instruction set to use for each client.

Adding an AI Manifest to an Install Service

Use the installadm create-manifest command to add the manifest custom AI manifest or derived manifests script to the svcname install service.

installadm create-manifest -n svcname
    -f filename [-m manifest]
    [-c criteria=value|list|range...
    | -C criteriafile] [-d]

The value of the manifest argument can be an AI manifest XML file, or it can be a derived manifests script. See Chapter 10, Provisioning the Client System. The create-manifest subcommand validates XML manifest files before adding them to the install service. To validate derived manifests script files, use the aimanifest validate command as shown in Adding a Derived Manifests Script to an Install Service.

The value of the manifest argument is the name displayed by the installadm list command. See Listing All AI Manifests and System Configuration Profiles. If the -m option is not provided, the name of the manifest is the value of the name attribute of the ai_instance element, if present, or the base name of the filename value.

Use the -d option to make this AI manifest the default AI manifest. The default manifest is the manifest used by any clients that do not match criteria specified for any other manifests in this install service. If -d is specified, then the criteria specified by the -c and -C options are ignored for the purpose of manifest selection. The previous default AI manifest for this service becomes inactive if it has no client criteria. If the previous default manifest has criteria, it remains active and its associated criteria become effective.

If -d is not specified, then either -c or -C must be specified to define which clients should use this AI manifest to complete their installation. If -d, -c, and -C are all not specified, then this manifest is added to the service but is inactive: No clients can use it.

If you want certain clients to use this AI manifest, first make sure those clients will use the install service specified in this create-manifest command. Any client systems that have not been explicitly associated with a particular install service by using the create-client command will use the appropriate default-arch install service. You can add customized AI manifests to the default-arch install service, or you can add customized AI manifests to a different service and then use create-client to make sure clients use that service.

The -c option specifies client selection criteria on the command line. The -C option specifies criteria in an XML file. The value of criteriafile is a full path and file name. See Chapter 9, Customizing Installations for a list of criteria keywords with command line and file examples.

The installadm create-manifest command verifies that criteria of the same type do not overlap. For example, if one criteria specification matches IP addresses from 10.0.0.0 to 10.255.255.255, installadm exits with an error if you try to add a criteria specification that matches IP address 10.10.10.10. For more information about criteria specifications, see Chapter 9, Customizing Installations.

The following command adds the manifest_t200.xml manifest to the solaris11_1-sparc install service. The -c option specifies that any clients that are using this install service and identify themselves as Sun Fire T200 servers are assigned the manifest_t200.xml installation instructions.

$ pfexec installadm create-manifest -f ./mymanifests/manifest_t200.xml \
-m t200 -n solaris11_1-sparc -c platform="SUNW,Sun-Fire-T200"

The following command is equivalent to the preceding command if the content of the criteria_t200.xml file is as shown.

$ pfexec installadm create-manifest -f ./mymanifests/manifest_t200.xml \
-m t200 -n solaris11_1-sparc -C ./mymanifests/criteria_t200.xml

Following is the content of the criteria_t200.xml file.

<ai_criteria_manifest>
    <ai_criteria name="platform">
        <value>SUNW,Sun-Fire-T200</value>
    </ai_criteria>
</ai_criteria_manifest>

Updating an AI Manifest

Use the installadm update-manifest command to replace the contents of the manifest AI manifest or derived manifests script file with the contents of the filename manifest or script file for the svcname install service. Criteria, default status, and manifest name are not changed as a result of the update.

installadm update-manifest -n svcname
    -f filename [-m manifest]

The update-manifest subcommand validates XML manifest files before adding them to the install service. To validate derived manifests script files, use the aimanifest validate command as shown in Adding a Derived Manifests Script to an Install Service.

The manifest manifest must already exist in the svcname service. Use the installadm list command to confirm. See Listing All AI Manifests and System Configuration Profiles.

If manifest is not specified, then the manifest that is replaced is identified in one of the following ways:

The name attribute of the ai_instance element in the filename manifest, if this attribute is specified and if the value of this attribute matches the manifest name of an existing manifest for this install service.
The base name of the filename value if this name matches the manifest name of an existing manifest for this install service.

The following command updates the content of the t200 manifest in the solaris11_1-sparc service with the content of ./mymanifests/manifest_newt200.xml. The name of the manifest in installadm list is still t200.

$ pfexec installadm update-manifest -n solaris11_1-sparc \
-f ./mymanifests/manifest_newt200.xml -m t200

Deleting an AI Manifest

Use the installadm delete-manifest command to remove the manifest AI manifest or derived manifests script from the svcname install service. The value of the manifest argument is the manifest name that the installadm list command returns. See Listing All AI Manifests and System Configuration Profiles.

installadm delete-manifest -m manifest -n svcname

You cannot delete the default AI manifest.

The following command removes the t200 AI manifest from the solaris11_1-sparc install service:

$ pfexec installadm delete-manifest -m t200 -n solaris11_1-sparc

Associating Client-Specific Configuration Instructions With Install Services

You can specify multiple sets of system configuration instructions for each install service. Multiple system configuration profiles can be associated with each client.

Adding a System Configuration Profile to an Install Service

Use the installadm create-profile command to add the filename system configuration profile to the svcname install service.

installadm create-profile -n svcname
    -f filename... [-p profile]
    [-c criteria=value|list|range... | -C criteriafile]

Multiple system configuration profiles can be specified in one create-profile command because a single client can use multiple configuration profiles. The same client selection criteria, or overlapping criteria, or no criteria can be specified for multiple profiles. When no criteria are specified, the profile is used by all clients that use this install service.

The create-profile subcommand validates system configuration profiles before adding them to the install service. To validate profiles under development, see the validate subcommand below.

The filename file can contain variables that are replaced with values from the client's installation environment during the installation process. See Using System Configuration Profile Templates for more information.

The value of the profile argument is the profile name displayed by the installadm list command once the profile has been added. See Listing All AI Manifests and System Configuration Profiles. If the -p option is not provided, the name of the profile is the base name of the filename file. The -p option is not valid when more than one filename is specified.

If you want certain clients to use this system configuration profile, first make sure those clients will use the install service specified in this create-profile command. Any client systems that have not been explicitly associated with a particular install service by using the create-client command will use the appropriate default-arch install service. You can add customized system configuration profiles to the default-arch install service, or you can add customized configuration profiles to a different service and then use create-client to make sure clients use that service.

The following command adds the profile_t200.xml profile to the solaris11_1-sparc install service. The -c option specifies that any clients that are using this install service and identify themselves as Sun Fire T200 servers are assigned the profile_t200.xml system configuration instructions.

$ pfexec installadm create-profile -f ./myprofiles/profile_t200.xml \
-p t200 -n solaris11_1-sparc -c platform="SUNW,Sun-Fire-T200"

Updating a System Configuration Profile

Use the installadm update-profile command to replace the specified profile from the svcname install service with the contents of filename. Any criteria remain with the profile following the update.

installadm update-profile -n|--service svcname
    -f|--file filename
    [-p|--profile profile]

The profile to be updated is the profile profile from the svcname install service, if specified. If profile is not specified from the svcname install service, the name of the profile to be updated is the profile with the base name of profile.

The following command updates the content of the t200 profile in the solaris11_1-sparc service with the content of ./myprofiles/profile_newt200.xml.

$ pfexec installadm update-profile -n solaris11_1-sparc \
-f ./myprofiles/profile_newt200.xml -p t200

Validating a System Configuration Profile

Use the installadm validate command to validate system configuration profiles for syntactic correctness.

installadm validate -n svcname -P filename... | -p profile...

Use the -P option to validate profiles that have not been added to the install service. The value of the filename argument is a full path name to the profile file.

Use the -p option to validate profiles that have already been added to the svcname install service using the create-profile subcommand. Use the installadm list command, as shown in Listing All AI Manifests and System Configuration Profiles, to display possible values for profile. The create-profile subcommand validates system configuration profiles before adding them to the install service. The validate -p subcommand verifies that the profile has not become corrupted since it was added.

The svcname is required for both filename and profile profiles. The service name is required for profiles that have not yet been added to an install service because the service_bundle(4) DTD might be different in different versions of the OS. An install service might be defined to install a different version of the OS than the version your install server is running. The profile must be validated against the DTD that will be in use on the client being installed.

Validated profiles are output to stdout. Errors are listed to stderr.

Deleting a System Configuration Profile

Use the installadm delete-profile command to remove the profile system configuration profile from the svcname install service. The value of the profile argument is the profile name that the installadm list command returns. See Listing All AI Manifests and System Configuration Profiles.

installadm delete-profile -p profile... -n svcname

The following command removes the t200 system configuration profile from the solaris11_1-sparc install service.

$ pfexec installadm delete-profile -p t200 -n solaris11_1-sparc

Exporting an AI Manifest or a System Configuration Profile

Use the installadm export command to copy the contents of the specified AI manifests or system configuration profiles from the svcname install service to the pathname file or directory.

installadm export -n svcname
    -m manifest... -p profile...
    [-o pathname]

If the -o option is not specified, the manifest and profile contents go to stdout. If only one input file is specified, the value of the pathname argument can be a file name. If more than one input file is specified, pathname must be a directory.

The manifest can be the name of an XML AI manifest or a derived manifests script. See Chapter 10, Provisioning the Client System for information about creating manifests and derived manifests scripts.

Use the installadm export command for the following tasks:

Check the specifications in the manifests and profiles.
Modify an existing manifest or profile.
Use an existing manifest or profile as a base for creating a new manifest or profile.

Modifying Criteria for an AI Manifest or a System Configuration Profile

Use the installadm set-criteria command to update the client criteria associated with an AI manifest or with system configuration profiles that you already added to the svcname install service using create-manifest or create-profile.

installadm set-criteria -m manifest -p profile... -n svcname
    -c criteria=value|list|range... | -C criteriafile |
    -a criteria=value|list|range...

Zero or one manifest can be specified along with zero or any number of profiles on the same set-criteria command line. The manifest and profile names are the names that the installadm list command returns. See Listing All AI Manifests and System Configuration Profiles.

If the -m option specifies the default manifest for the service, the criteria are added or changed, but the criteria are ignored when installing clients. See Listing All AI Manifests and System Configuration Profiles.

Use the -c or -C options to replace the criteria for these existing manifests and profiles with the new criteria specified. Use the -a option to retain the existing criteria and add the specified criteria. See Chapter 9, Customizing Installations for more information about specifying criteria.

The following command adds a memory criteria specification to a manifest that was originally added to this service with a platform criteria specification:

$ pfexec installadm set-criteria -m t200 -n solaris11_1-sparc -a mem="4096-unbounded"

The result of the criteria specified with create-manifest and added with set-criteria is that the manifest is used by any client that is using this install service that is a Sun Fire T200 server and that has at least 4 Gbytes of memory.

You could achieve this same result by using the -C option instead of the -a option with the following criteria_t200.xml file.

<ai_criteria_manifest>
    <ai_criteria name="platform">
        <value>SUNW,Sun-Fire-T200</value>
    </ai_criteria>
    <ai_criteria name="mem">
        <range>
            4096
            unbounded
        </range>
    </ai_criteria>
</ai_criteria_manifest>

Showing Information About Install Services

Use the installadm list command to show information about install services.

installadm list [-n svcname] [-c] [-m] [-p]

Listing All Install Services on the Install Server

The following command displays all of the install services on this server. In this example, four enabled install services are found. Disabled services have a Status value of off.

$ installadm list

Service Name      Alias Of          Status  Arch   Image Path
------------      --------          ------  ----   ----------
default-i386      solaris11_1-i386  on      i386   /export/auto_install/solaris11_1-i386
default-sparc     solaris11_1-sparc on      sparc  /export/auto_install/solaris11_1-sparc
solaris11_1-i386  -                 on      i386   /export/auto_install/solaris11_1-i386
solaris11_1-sparc -                 on      sparc  /export/auto_install/solaris11_1-sparc

The default-i386 service was created automatically when the first i386 service was created on this server. The default-i386 service is used by any x86 client that has not been associated with the solaris11_1-i386 service by using the create-client subcommand. The default-i386 and solaris11_1-i386 services share a net image, but they have different AI manifests and system configuration profiles.

The default-sparc service was created automatically when the first sparc service was created on this server. The default-sparc service is used by any SPARC client that has not been associated with the solaris11_1-sparc service by using the create-client subcommand. The default-sparc and solaris11_1-sparc services share a net image, but they have different AI manifests and system configuration profiles.

Showing Information for a Specified Install Service

The following command displays information about the install service specified by the -n option:

$ installadm list -n solaris11_1-sparc

Service Name      Alias Of Status  Arch   Image Path
------------      -------- ------  ----   ----------
solaris11_1-sparc -        on      sparc  /export/auto_install/solaris11_1-sparc

Listing Clients Associated With Install Services

The following command lists all the clients that are associated with the install services on this install server. The clients were associated with the install services by using the installadm create-client command. See Adding a Client To an Install Service.

$ installadm list -c

Service Name      Client Address    Arch  Image Path
------------      --------------    ----  ----------
solaris11_1-sparc 00:14:4F:A7:65:70 sparc /export/auto_install/solaris11_1-sparc
solaris11_1-i386  08:00:27:8B:BD:71 i386  /export/auto_install/solaris11_1-i386
                  01:C2:52:E6:4B:E0 i386  /export/auto_install/solaris11_1-i386

Listing Clients Associated With a Specific Install Service

The following command lists all the clients that have been added to the specified install service. In the following example, one client is associated with the solaris11_1-sparc install service.

$ installadm list -c -n solaris11_1-sparc

Service Name      Client Address    Arch  Image Path
------------      --------------    ----  ----------
solaris11_1-sparc 00:14:4f:a7:65:70 sparc /export/auto_install/solaris11_1-sparc

Showing Information About Customized Installations

The commands in this section show which AI manifests and system configuration profiles are associated with a particular install service. These commands also show which client criteria are associated with each manifest and profile.

Listing All AI Manifests and System Configuration Profiles

The following command lists all AI manifests, derived manifests scripts, and system configuration profiles for all install services on this install server. The Service/Manifest Name and Service/Profile Name columns display the internal names of the manifests, scripts, or profiles. The Status column identifies the default manifest for each service and any inactive manifests. A manifest is inactive if it does not have any associated criteria and also is not the default. The Criteria column shows the associated client criteria.

The orig_default manifest is the original default AI manifest that was part of the install service when the install service was created. The mem1 manifest was created with memory criteria and also with the -d option to make it the new default manifest for this service. Because mem1 is the default manifest, its criteria are ignored. If another manifest is created as the default manifest, then the mem1 criteria are used to select clients to use the mem1 manifest. The original default manifest is inactive because it has no associated criteria to determine which clients should use it. Only the default manifest can have no associated criteria. A client that does not match the criteria to use any other manifest uses the default manifest. See Chapter 9, Customizing Installations for more information about selecting an AI manifest.

$ installadm list -m -p
Service/Manifest Name  Status    Criteria
---------------------  ------    --------
default-i386
   orig_default        Default   None

default-sparc
   orig_default        Default   None

solaris11_1-i386
   ipv4                          ipv4     = 10.6.68.1 - 10.6.68.200
   mem1                Default   (Ignored: mem      = 2048 MB - 4095 MB)
   orig_default        Inactive  None

solaris11_1-sparc
   t200                          mem      = 4096 MB - unbounded
                                 platform = SUNWSun-Fire-T200
   mem1                Default   (Ignored: mem      = 2048 MB - 4095 MB)
   orig_default        Inactive  None

Service/Profile Name  Criteria
--------------------  --------
solaris11_1-i386
   mac2               mac      = 08:00:27:8B:BD:71
                      hostname = server2
   mac3               mac      = 01:C2:52:E6:4B:E0
                      hostname = server3
   ipv4               ipv4     = 10.0.2.100 - 10.0.2.199
   mem1               mem      = 2048 MB - 4095 MB

solaris11_1-sparc
   mac1               mac      = 01:C2:52:E6:4B:E0
                      hostname = server1
                      ipv4     = 192.168.168.251
   t200               platform = SUNWSun-Fire-T200
                      mem      = 4096-unbounded

Listing Manifests and Profiles Associated With a Specified Install Service

The following example shows all AI manifests, derived manifests scripts, and system configuration profiles associated with the install service solaris11_1-sparc.

$ installadm list -m -p -n solaris11_1-sparc
Service/Manifest Name  Status   Criteria
---------------------  ------   --------
solaris11_1-sparc
   t200                         mem      = 4096 MB - unbounded
                                platform = SUNWSun-Fire-T200
   mem1                Default  (Ignored: mem      = 2048 MB - 4095 MB)
   orig_default        Inactive None

Service/Profile Name  Criteria
--------------------  --------
solaris11_1-sparc
   mac1               mac  = 01:C2:52:E6:4B:E0
                      hostname = server1
                      ipv4 = 192.168.168.251
   t200               platform = SUNWSun-Fire-T200
                      mem = 4096-unbounded

Administering the AI SMF Service

On the AI server, the SMF service svc:/system/install/server:default is the service that represents the overall state of the AI server application and all install services.

Example 8-1 Enabling the AI SMF Service

The AI SMF service is enabled when you run the installadm create-service command. The AI SMF service also is enabled when you run any other installadm command that affects existing install services. To manually enable the AI SMF service, run the following command:

$ svcadm enable svc:/system/install/server:default

The AI SMF service goes into maintenance mode if no install services are currently enabled on the install server or if a problem occurs that requires attention.

Example 8-2 Disabling the AI SMF Service

To disable the AI SMF service, run the following command:

$ svcadm disable svc:/system/install/server:default

Do not disable the AI SMF service if any AI install service is still enabled. See Listing All Install Services on the Install Server for information about how to see whether any install services are enabled.

Skip Navigation Links
Exit Print View
	Installing Oracle Solaris 11.1 Systems Oracle Solaris 11.1 Information Library