If you want to install the OpenSolaris operating system (OS) on multiple client systems on a network, you can use the automated installer (AI) to accomplish that task. The automated installer performs essentially “hands-free” network installations of the OpenSolaris OS. You can install the OpenSolaris OS onto x86 systems or SPARC systems in a network.If you have not used the automated installer before, review the following introduction to this tool. Then, see . If you have already set up an install server, you can go to the instructions for . The automated installer is used to automate the installation of the OpenSolaris OS on one or more SPARC and x86 systems over a network. The installations can differ in architecture, packages installed, disk capacity, and other parameters.The minimal configuration necessary to use the automated installer is to have one system as the install server and one client on which to install. On the server, you set up an installation service, which is associated with manifests, or specifications, for specific x86 installations or SPARC installations. Manifests can include information such as target device, additional packages, partition information, and other parameters. When the client boots, this boot initiates a search for a manifest that matches the client's machine specifications. When a matching manifest is found, the client is installed with the OpenSolaris release according to the specifications in the manifest files. Perform the following tasks:First, set up an install server on your network. See .This install server manages the resources needed for automated installations to client systems in a network.Use the installadm create-service command to set up an install server and create an installation service. An installation service, or install service, is a network entity that specifies the parameters for a particular type of installation. These specifications are defined in XML manifest files.The automated installer uses AI ISO images to create the install services. An AI ISO image is a collection of software in a single file. An AI ISO image is usable for installations. Once an install server and an installation service are set up, you can install the OpenSolaris release to a client on the network, per the default specifications in the service, by booting the client system. See . If you want to perform various types of installations in a network, you can create and manage additional install services tailored for each type of installation by using the installadm create-service command. For example, you can set up an install service that installs the OpenSolaris OS to x86 clients and an install service that installs the OpenSolaris OS to SPARC clients. See . If you have clients with varying machine specifications, you can manually create or modify manifests so that the manifests cover those specific machine specifications. Then, you can use the installadm add command to add your new manifests to an install service. See . If you want a specific client to use a specific install service, you can associate a service with a client by using the installadm create-client command. See . To resolve problems encountered while using the automated installer, see . The installadm utility enables you to accomplish the following tasks:Set up install services and installation images, and set up and update a DHCP server Configure your server Set up or remove custom clients Add or delete manifest files Enable or disable install services List services or list manifests for an install service For more information, see the . Once you have set up an install server with one or more install services, and you've customized the installation specifications for the install services to suit your needs, you are ready to install the OpenSolaris OS to client systems on the network. You only need to boot the client, and the process runs to completion without further input from you.The following flowchart illustrates how a client system is installed. The client browses for available install services, seeking a service where the installation criteria in the service's manifest file matches the characteristics of the client system. When a match is found, the installation is performed on the client system, using a boot image and manifest specifications provided by the install service.

Graphic illustrates the steps for client installation

For further information, see . The automated installer provides support for network installations, where one installation specification can be applied to multiple systems.The automated installer includes the following features that support multiple client installations in a network:The automated installer uses DNS services, so that, when you boot a client, any new install services that were added to the network before the client booted are automatically available to the client. No individual client configuration is necessary for clients to access install services. Installation setup is decentralized. You can maintain multiple, disparate locations for installation services and for client configuration. Installation services can be created on several machines, enabling you to make available multiple install services of the same type and release. The client is notified of all available install services on the network when the client boots. If all of your client systems have the same hardware characteristics, then the default installation specifications that you setup using the installadm create-service command can be used for all client installations. If you want to install the OpenSolaris OS on clients with varying hardware characteristics, you can create custom manifests tailored for specific hardware characteristics. Then, using the installadm add command, you can add the custom manifest to an install service to make it available on the network for client installations. Depending on your network configuration, basic setup of an install server and an initial install service can be a straightforward process. For further information about simple setup and advanced setup options, see . The automated installer is used to automate the installation of the OpenSolaris OS on one or more SPARC and x86 systems over a network. The minimal configuration necessary to use the automated installer is to have one system as an install server and one client on which to install. On the install server, you set up install services with associated manifests that provide specifications for client installations. Client installations can differ in architecture, packages installed, disk capacity, and other parameters.The following task map walks you through the overall process of setting up and using the automated installer. Task Question Reference Check hardware. Do you have the necessary hardware for your install server and clients? Any system that meets the requirements can be used as an automated install server or client, including laptops, desktops, virtual machines, and enterprise servers.See the install server requirements at . See the client requirements at . Install OpenSolaris 2009.06 OS. Is the OpenSolaris 2009.06 OS installed on your install server? You can use either a SPARC system or an x86 system as your install server.You can set up an x86 install server to install to x86 clients and to SPARC clients. Or, you can use a SPARC install server to install to x86 clients and to SPARC clients. But, you must first set up an x86 install server, in order to be able to set up a SPARC install server. You must have the OpenSolaris 2009.06 release installed on the system that you plan to use as your install server. See Step 1 in . Set up a static IP address. Do you have a static IP address set up for your install server? If you don't have a static IP address set up for your install server, see Step 2 in . Get the install server tools package. Is the latest SUNWinstalladm-tools package installed on your install server? For instructions about installing the latest SUNWinstalladm package, see Step 3 in . Get an AI ISO image. Do you have the AI ISO image you want to use as input for the installadm create-service command? For instructions about downloading the AI ISO image, see Step 4 in . Set up an install service. Have you run installadm create-service command to set up your install service? For instructions, see and . Customize client installations. Do you need to run the installadm create-client command to customize your client installations? For instructions, see . Replace default manifests. Are the specifications in the default manifest suitable for your clients? If the default manifest specifications are not suitable for your clients, you can create a custom manifest. See . Assign custom manifests. Do you want to replace the default manifest with a custom manifest? If you want to assign custom manifests for use by specific clients, see . Start installations. Are you ready to start client installations? Boot the client from the network. For x86 clients, select the network device to boot from. For SPARC clients, at the OK open boot prompt, type boot net:dhcp. See . Troubleshooting Was there a problem with your installation? Refer to . See, also, . The automated installer enables you to set up an install server on your system. Then, you can use this install server to install the OpenSolaris OS on multiple client systems. Use the following instructions to set up a system as an install server. Note the following:Any system that meets these setup requirements can be used as an automated install server, including laptops, desktops, virtual machines, and enterprise servers. You need a DHCP server in order to set up automated installations. The install server can be set up as a DHCP server. Or, if you already have a DHCP server in your network, you can use that DHCP server to provide initial configuration to the install clients. The install server must have a static IP address. The default router should be set on the install server. The OpenSolaris 2009.06 release must be installed on the install server. 4 GB of free disk space is recommended on the install server after the OpenSolaris 2009.06 release has been installed. If you plan to perform automated installations on SPARC client systems, those systems must support WAN boot. Your SPARC server must first be set up as a SPARC client, therefore, that SPARC system must support WAN boot. For more SPARC information, see Step 1 below and see Complete the following initial steps to prepare your system to be an automated install server. After performing these initial steps, complete the setup by using either simple instructions or advanced instructions, depending on your system configuration. The simple and advanced instructions are described after the initial steps.The OpenSolaris 2009.06 automated installer is not backward compatible with ISO images or automated installer tools from earlier OpenSolaris releases. Use OpenSolaris 2009.06 automated installer tools and procedures with the OpenSolaris 2009.06 operating system and 2009.06 ISO images only. Install the OpenSolaris 2009.06 operating system (OS) on the system that you will use as your install server. Or, upgrade your OpenSolaris system to the 2009.06 release.Use either the following x86 instructions or SPARC instructions:For x86 systems, download the OpenSolaris Live CD image from and install the OpenSolaris OS on your system.Live CD images are also available at for the current release and for OpenSolaris developer builds.For instructions about installing a Live CD image onto your system or upgrading an existing OpenSolaris OS, see Getting Started With OpenSolaris.To use the automated installer, you must have root access on your system. No Live CD images are available for SPARC systems. Use the following alternate procedure to install the OpenSolaris OS on a SPARC system and set up a SPARC install server:If you plan to install to SPARC client systems, those systems must support WAN boot. For more information, see Download an x86 Live CD image and install the OpenSolaris OS on an x86 system. Download a SPARC AI ISO image to the x86 system as described in step 4. Set up the x86 system as an install server by using the instructions below. Reference the SPARC AI ISO image in the installadm create-service command as a source image, so that SPARC clients can install the OpenSolaris OS by using this image. Boot your SPARC client as follows:OK boot net:dhcpThe SPARC client boots and install the OpenSolaris OS. Continue to step 2 and set up the SPARC system as an install server. If your server is not already configured to use a static IP address, perform the following steps:Alternately, see Go to the main task bar Menu and select System>Administration>Network to launch the Network Administration dialog box. And, select Manual to launch the Network Settings tool. In the Connections tab, complete the following steps:Highlight the interface to configure with a static IP address, and select the Properties button. Check the Enable box to enable this connection. Check the Activate box to activate on boot. Enter the IP address, Subnet mask, and Gateway in the appropriate boxes. Select OK. In the General tab, fill in the system's hostname and domain name. In the DNS tab, if you use DNS to resolve hostnames, add the IP addresses of the DNS servers for the network. In the Hosts tab, complete the following steps:Select Add to add an entry for this system's hostname. Enter the IP address in the IP Address box. Type the system's hostname on the first line in the Alias box. Then, type “<hostname>.local” on the second line in the Alias box, replacing <hostname> with your hostname. Then, type the word, “loghost,” on the third line in the Alias box. Select OK. Highlight the IPv4 loopback IP Address entry that has the address, 127.0.0.1, and select the Properties button. Remove all lines from the Aliases box, except for the line that reads “localhost.” Select OK. Highlight the IPv6 loopback IP address entry that has the address, ::1, and select the Properties button. Remove all lines from the Aliases box, except for the line that reads “localhost.” Select OK. Select OK to close the Network Settings dialogue box. If you use DNS to resolve hostnames, enable DNS in the name service switch file on this system as follows:# cp /etc/nsswitch.dns /etc/nsswitch.conf Reboot your system. Install the latest SUNWinstalladm-tools package by using Package Manager, or by using the following command:# pkg install SUNWinstalladm-tools Download an AI ISO image for x86 clients or for SPARC clients from .The automated installer will use this AI ISO image to install the OpenSolaris OS to your client systems.The build number or release of the AI ISO image must be the same build number or release of the OpenSolaris operating system that you plan to install. Store the AI ISO image on your local file system. For example, store the image at /export/aiimages/osol-0906-ai-x86.iso. After you have completed the initial setup described above, choose one of the following options for completing the install server setup:Simple Instructions – If you want to set up one server and only one type of client, use the simple instructions. Or, if this is your first experience setting up an install server, use these simple instructions. These instructions assume an extremely simple network setup where the network consists of a single subnet, and the install server also acts as the DHCP server for the network and uses DNS to resolve hostnames. See How to Complete Server Setup (Simple Instructions). Advanced Instructions – If you already have a DHCP server set up, use the advanced instructions. For networks where the DHCP server is a separate system from the install server, additional administration tasks on the DHCP server are required to properly set up the automated install environment. The DHCP server is expected to be able to provide DNS information to the install clients. See How to Complete Server Setup (Advanced Instructions). If you want to set up one server and only one type of client, use the following simple instructions. Or, if this is your first experience setting up an install server, use these simple instructions. These instructions assume an extremely simple network setup where the network consists of a single subnet, and the install server also acts as the DHCP server for the network and uses DNS to resolve hostnames. Complete the initial setup instructions provided in . Set up an install service by using either the following x86 procedure or SPARC procedure:To set up an install service for x86 clients, use the following procedure:Create an install service by using the installadm create-service command as in the following example:# installadm create-service n 0906x86 i 172.1.0.10 c 5 \ s /export/aiimages/osol-0906-ai-x86.iso /export/aiserver/osol-0906-ai-x86In this example, the command sets up a new install service named 0906x86. The command also sets up a DHCP server on this system, if one hasn't been set up yet. A new DHCP macro, dhcp_macro_0906x86, for the install service will be created. The install service will serve 5 IP addresses, starting from 172.1.0.10.In this example, the command options perform as follows:Using the n option, the command specifies a name, 0906x86, for the new install service.If you do not supply a service name, installadm create-service creates a unique name for the install service using the format, _install_service_<port_number>. Using the i option, the command sets up a new DHCP server. The IP addresses are set up starting from 172.1.0.10. Using the c option, the command sets up a total number of 5 IP addresses in the DHCP table. Using the s option and its argument, /export/aiimages/osol-0906-ai-x86.iso, the command specifies the location of an AI ISO image. In this case, the AI ISO image is an x86 image. This AI ISO image, however, is compacted and is not ready for client installations. The last command-line argument, /export/aiserver/osol-0906-ai-x86, specifies the location where the command unpacks and stores the image that was specified by the s option. The resulting net image in this location enables client installations. Boot the client from the network.It may be necessary to modify the BIOS configuration to select network booting. When the client boots, select the network device to boot from. To set up an install service for SPARC clients, use the following procedure:Create an install service by using the installadm create-service command, as in the following example:# installadm create-service n 0906sparc i 172.1.0.10 c 5 \ s /export/aiimages/osol-0906-ai-sparc.iso /export/aiserver/osol-0906-ai-sparcIn this example, the command sets up a new install service named 0906sparc. The command also sets up a DHCP server on this system, if one hasn't been set up yet. A macro, dhcp_macro_0906sparc, for the install service will be created in the DHCP server, and 5 IP addresses, starting from 172.1.0.10, will be allocated to that macro.In this example, the command options perform as follows:Using the n option, the command specifies a name, 0906sparc, for the new install service. Using the i option, the command sets up a new DHCP server. The IP addresses, starting from 172.1.0.10, are set up. Using the c option, the command sets up a total number of 5 IP addresses in the DHCP table. Using the s option, the command specifies an AI ISO image, /export/aiimages/osol-0906-ai-sparc.iso, that can be used to install the OpenSolaris OS to a client. In this case, the AI ISO image is a SPARC image. This AI ISO image, however, is compacted and is not ready for client installations. In the last field, the command specifies a location, /export/aiserver/osol-0906-ai-sparc, where the command unpacks and stores the image that was specified by the s option . The net image in this location enables client installations. For SPARC clients, boot with the following command from the open boot prompt:OK boot net:dhcp For further information, see . See, also, . If you already have DHCP server set up, use the following advanced instructions. For networks where the DHCP server is a separate system from the install server, additional administration tasks on the DHCP server are required to properly set up the automated install environment. In these cases, the following advanced instructions for completing setup replaces the simple instructions above.Complete the initial setup instructions provided in . Create an install service using either the following x86 or SPARC instructions:For an x86 install service, use the installadm create-service command, as in this example:# installadm create-service n 0906x86 s /export/aiimages/osol-0906-ai-x86.iso \ /export/aiserver/osol-0906-ai-x86The following displays:Setting up the target image at /export/aiserver/osol-0906-ai-x86 ... Registering the service 0906x86._OSInstall._tcp.local Detected that DHCP is not set up on this server. If not already configured, please create a DHCP macro named dhcp_macro_0906x86 with: Boot server IP (BootSrvA) : 10.6.68.29 Boot file (BootFile) : 0906x86 GRUB Menu (GrubMenu) : menu.lst.0906x86 If you are running Sun's DHCP server, use the following command to add the DHCP macro, dhcp_macro_0906x86: /usr/sbin/dhtadm -g -A -m dhcp_macro_0906x86 \ -d :BootSrvA=10.6.68.29:BootFile=0906x86:GrubMenu=menu.lst.0906x86: Additionally, if the site specific symbol GrubMenu is not present, please add it as follows: /usr/sbin/dhtadm -g -A -s GrubMenu -d Site,150,ASCII,1,0 Note: Be sure to assign client IP address(es) if needed (e.g., if running Sun's DHCP server, run pntadm(1M)). copying boot file to /tftpboot/pxegrub.I86PC.OpenSolaris-1 Service discovery fallback mechanism set upIn this example, the command creates an install service named 0906x86, using the AI ISO image previously downloaded at /export/aiimages/osol-0906-ai-x86.iso, and stores the resultant net image at /export/aiserver/0906x86.As shown above, this command outputs the name and values of a macro, dhcp_macro_0906x86, which needs to be added to the DHCP server. If you are using a Sun DHCP server, you can create the above macro on your DHCP server either by using the DHCP Manager or by running the dhtadm commands, provided in the above output, on your DHCP server.If you are setting up a Sun DHCP server and client IP addresses need to be assigned, you may need to use the pntadm(1M) command. For more information, see the pntadm(1M) man page.On systems which support graphic interfaces, you can use the DHCP Manager, dhcpmgr, instead of the dhtadm and pntadm commands. For more information, see the dhcpmgr(1M) man page. For a SPARC install service, use the installadm create-service command as in this example:# installadm create-service n 0906sparc \ s /export/aiimages/osol-0906-ai-sparc.iso /export/aiserver/osol-0906-ai-sparcThe following displays:Automated Installations will not work with the current server network setup. Setting up the target image at /export/aiserver/osol-0906-ai-sparc ... Registering the service 0906sparc._OSInstall._tcp.local Detected that DHCP is not set up on this server. If not already configured, please create a DHCP macro named dhcp_macro_0906sparc with: Boot server IP (BootSrvA) : 10.6.68.29 Boot file (BootFile) : http://10.6.68.29:5555/cgi-bin/wanboot-cgi If you are running Sun's DHCP server, use the following command to add the DHCP macro, dhcp_macro_0906sparc: /usr/sbin/dhtadm -g -A -m dhcp_macro_0906sparc \ -d :BootSrvA=10.6.68.29:BootFile=\"http://10.6.68.29:5555/cgi-bin/wanboot-cgi\": Note: Be sure to assign client IP address(es) if needed (e.g., if running Sun's DHCP server, run pntadm(1M)). Service discovery fallback mechanism set up Creating SPARC configuration fileIn this example, the command creates an install service named 0906sparc, using the AI ISO image previously downloaded at /export/aiimages/osol-0906-ai-sparc.iso, and stores the resultant net image at /export/aiserver/osol-0906-ai-sparc.As shown above, this command outputs the name and values of a macro, dhcp_macro_0906sparc, which needs to be added to the DHCP server. If you are using a Sun DHCP server, you can create the above macro on your DHCP server either by using the DHCP Manager or by running the dhtadm commands, provided in the above output, on your DHCP server.If you are setting up a Sun DHCP server and client IP addresses need to be assigned, you may need to use the pntadm(1M) command. For more information, see the pntadm(1M) man page.On systems which support graphic interfaces, you can use the DHCP Manager, dhcpmgr, instead of the dhtadm and pntadm commands. For more information, see the dhcpmgr(1M) man page.For SPARC install services, the first install service created on an install server is the service that will be used for all client installations that use the install server. If you want a client to use a different install service from this install server, you must use the installadm create-client command to create a client-specific configuration. See . Optional: Set up a custom install client to use the install service.See the following x86 and SPARC examples.To set up a custom x86 install client, run the installadm create-client command as shown in the following example:# installadm create-client e 0:10:18:0f:28:26 n 0906x86 \ t /export/aiserver/osol-0906-ai-x86The following displays:Setting up X86 client... Service discovery fallback mechanism set up Detected that DHCP is not set up on this server. If not already configured, please create a DHCP macro named 010010180F2826 with: Boot server IP (BootSrvA) : 10.6.68.29 Boot file (BootFile) : 010010180F2826 If you are running Sun's DHCP server, use the following command to add the DHCP macro, 010010180F2826: /usr/sbin/dhtadm -g -A -m 010010180F2826 \ -d :BootSrvA=10.6.68.29:BootFile=010010180F2826:GrubMenu=menu.lst.010010180F2826: Note: Be sure to assign client IP address(es) if needed (e.g., if running Sun's DHCP server, run pntadm(1M)).In this example, the command creates a client-specific setup for the system with a MAC address of 0:10:18:0f:28:26. This client will use the install service previously setup, named 0906x86, and the install image at /export/aiserver/osol-0906-ai-x86.As shown above, this command outputs the name and values of a macro, 010010180F2826, which needs to be added to the DHCP server. If you are using a Sun DHCP server, you can create the above macro on your DHCP server either by using the DHCP Manager or by running the dhtadm commands, provided in the above output, on your DHCP server:If you are setting up a Sun DHCP server and client IP addresses need to be assigned, you may need to use the pntadm(1M) command. For more information, see the pntadm(1M) man page.On systems which support graphic interfaces, you can use the DHCP Manager, dhcpmgr, instead of the dhtadm and pntadm commands. For more information, see the dhcpmgr(1M) man page. To set up a custom SPARC install client, run the installadm create-client command as shown in the following example:# installadm create-client e 0:e0:81:5d:bf:e0 \ t /export/aiserver/osol-0906-ai-sparc n 0906sparcThe following displays:Setting up SPARC client... Creating SPARC configuration file Detected that DHCP is not set up on this server. If not already configured, please create a DHCP macro named 0100E0815DBFE0 with: Boot server IP (BootSrvA) : 10.6.68.29 Boot file (BootFile) : http://10.6.68.29:5555/cgi-bin/wanboot-cgi If you are running Sun's DHCP server, use the following command to add the DHCP macro, 0100E0815DBFE0: /usr/sbin/dhtadm -g -A -m 0100E0815DBFE0 \ -d :BootSrvA=10.6.68.29:BootFile=\"http://10.6.68.29:5555/cgi-bin/wanboot-cgi\": Note: Be sure to assign client IP address(es) if needed (e.g., if running Sun's DHCP server, run pntadm(1M)).In this example, the command creates a client-specific setup for the system with a MAC address of 0:e0:81:5d:bf:e0. This client will use the install service previously setup, named 0906sparc, and the install image at /export/aiserver/osol-0906-ai-sparc.As shown above, this command outputs the name and values of a macro, dhcp_macro_0906x86, which needs to be added to the DHCP server. If you are using a Sun DHCP server, you can create the above macro on your DHCP server either by using the DHCP Manager or by running the dhtadm commands, provided in the above output, on your DHCP server:If you are setting up a Sun DHCP server and client IP addresses need to be assigned, you may need to use the pntadm(1M) command. For more information, see the pntadm(1M) man page.On systems which support graphic interfaces, you can use the DHCP Manager, dhcpmgr, instead of the dhtadm and pntadm commands. For more information, see the dhcpmgr(1M) man page. man page. Boot the client from the network.For x86 clients, select the network device to boot from when the client boots.It may be necessary to modify the BIOS configuration to select network booting. For SPARC clients, boot with the following command from the open boot prompt:OK boot net:dhcp For further information, see . See, also, . Once you have set up an automated install server, you are ready to perform the following administrative tasks when needed. The basic tasks are as follows:Set up install services and installation images, and set up and update a DHCP server Set up or remove clients Add or delete manifest files Enable or disable install services List services or list manifests for an install service Administer install services by using the AI SMF service See the instructions and examples provided in the following sections. Use one of the following procedures: You can use the installadm create-service command with i and c options to accomplish any of the following:You want your install server to act as your DHCP server, and you want to set up the proper DHCP settings on the server. You want to correlate specific IP addresses with an install service. Using the i and c options, the installadm create-service command assigns a starting IP address and a total number of IP address to be made available to clients of the install service. You want to add more IP addresses that will correlate with an install service. Use the command with the following options:installadm create-service [i dhcp_ip_start c count_of_ipaddr] [s srcimage] targetdirUsing the i option, the command sets up a new DHCP server. The IP addresses, starting from dhcp_ip_start, are set up. Using the c option, the command sets up a total number of IP addresses in the DHCP table equal to the value of the count_of_ipaddr. The first IP address is the value of dhcp_ip_start that is provided by the i option. Using the s option, the command specifies an AI ISO image, srcimage, to use for setting up the install service. The source image is compacted and not ready for use in installations. The command expands this image and places the resultant net image in the targetdir location. This net image enables client installations. This example describes how the installadm create-service command can be used to set up one server that can install five x86 clients in, for example, a classroom setting. The following describes the general steps to this process. Then, specific command details are provided to illustrate this process.This example has the following conditions:The server and clients are in the same subnet. You want to install the OpenSolaris 2009.06 release on the first disk of each client. All clients are identical systems, so no additional client customizations are needed. You need to set up a DHCP server on the installation server. Run the following command to set up an install service, providing the required initial image source and a target directory.Because this is the first install service created on this system, you also must provide a starting IP address and a total number of IP addresses to be made available for the clients.installadm create-service [n svcname] [s srcimage] [i dhcp_ip_start \ c count_of_ipaddr] targetdirThis single command sets up an install service on your system.See the following example:# installadm create-service n 0906x86 i 10.6.68.201 c 5 \ s /export/aiimages/osol-0906-ai-x86.iso /export/aiserver/osol-0906-ai-x86In this example, the terminal displays the progress as follows:Setting up the target image at /export/aiserver/osol-0906-ai-x86 ... Registering the service 0906x86._OSInstall._tcp.local Creating DHCP Server Created DHCP configuration file. Created dhcptab. Added "Locale" macro to dhcptab. Added server macro to dhcptab - line1-x4100. DHCP server started. Added network macro to dhcptab - 10.0.0.0. Created network table. copying boot file to /tftpboot/pxegrub.I86PC.OpenSolaris-1 Service discovery fallback mechanism set upThe options in this example accomplish the following:Options Description s export/aiimages/osol-0906-ai-x86.iso Using the s option, the command identifies the path to an AI ISO image, export/aiimages/osol-0906-ai-x86.iso. This image is compacted and not usable for installations. The command unpacks the image and stores the resultant net image in a target directory, /export/aiserver/osol-0906-ai-x86. This net image enables client installations. n 0906x86 Using the n option, the command specifies a name, 0906x86, for the new install service. i 10.6.68.201 c 5 Using the i and c options, the installadm command creates a DHCP server and macro. The i option assigns a starting IP address of 10.6.68.201. The c option allocates 5 IP addresses for clients. The command creates a macro, dhcp_macro_0906x86.You can view the DHCP configuration results in the DHCP table in the DHCP Manager by using the /usr/sadm/admin/bin/dhcpmgr utility. The progress displays provides additional information:The command creates default manifest files that are based on the installation image. Additionally, the command associates the manifest files with the install service. The progress display shows that the command created an install service named 0906x86. The command creates a boot file, 0906x86, under /tftpboot, and creates a menu.lst file. The client searches for and locates this boot file name through DHCP.You can examine this information in the menu.lst file. In this example, the file would be called /tftpboot/menu.lst.0906x86. The command also creates a link from the net image at /export/aiserver/osol-0906-ai-x86 to a web server that is running on port 5555. If you already have the correct DHCP settings on your system, and you do not want to specify additional IP addresses for clients, only a source image and a target directory are required to set up an additional install service. For example, if you want to have multiple install services on an install server, you do not always need to add more IP addresses when you add more services.The syntax for this minimal command is as follows:# installadm create-service [s srcimage] targetdirUsing the s option, the command specifies an ISO image, srcimage, to use for setting up the install service. The source image is compacted and not ready for use in installations. The command expands this image and places the resultant net image in the targetdir location. This net image enables client installations.The command outputs the name of a client-specific macro and its values. You need to add this information to the DHCP server. To create the macro on your DHCP server, use the DHCP Manager or run the dhtadm commands that are provided in the command output. This example describes how to set up one server that can install both SPARC and x86 clients in, for example, a lab setting. The following describes the general steps to this process. Then, specific examples are provided to illustrate this process.This example has the following conditions:The server and clients may not be on the same subnet. You want to install the OpenSolaris OS on SPARC and x86 clients. The DHCP server is remote. You want to set up individual clients and assign specific IP addresses to these clients. Run the following commands to set up a SPARC install service and an x86 install service.Because the DHCP server in this example is not set up by installadm commands, you should not provide a starting IP address and a total number of IP addresses to be made available for the clients. Set up a SPARC install service as follows:# installadm create-service n 0906sparc \ s /export/aiimages/osol-0906-ai-sparc.iso \ /export/aiserver/osol-0906-ai-sparcThe following displays:Setting up the target image at /export/aiserver/osol-0906-ai-sparc ... Registering the service 0906sparc._OSInstall._tcp.local Detected that DHCP is not set up on this server. If not already configured, please create a DHCP macro named dhcp_macro_0906sparc with: Boot server IP (BootSrvA) : 10.6.68.29 Boot file (BootFile) : http://10.6.68.29:5555/cgi-bin/wanboot-cgi If you are running Sun's DHCP server, use the following command to add the DHCP macro, dhcp_macro_0906sparc: /usr/sbin/dhtadm -g -A -m dhcp_macro_0906sparc \ -d :BootSrvA=10.6.68.29:BootFile=\"http://10.6.68.29:5555/cgi-bin/wanboot-cgi\": Note: Be sure to assign client IP address(es) if needed (e.g., if running Sun's DHCP server, run pntadm(1M)). Service discovery fallback mechanism set up Creating SPARC configuration fileIn this example, the command creates an install service named 0906sparc, using the AI ISO image previously downloaded at /export/aiimages/osol-0906-ai-sparc.iso, and storing the resultant net image at /export/aiserver/osol-0906-ai-sparc.As shown above, this command outputs the name and values of a macro, dhcp_macro_0906sparc, which needs to be added to the DHCP server. If you are using a Sun DHCP server, you can create the above macro on your DHCP server either by using the DHCP Manager or by running the dhtadm commands, provided in the above output, on your DHCP server:On systems which support graphic interfaces, you can use the DHCP Manager, dhcpmgr, instead of the dhtadm command. For more information, see the dhcpmgr(1M) man page. Set up an x86 install service as follows:# installadm create-service n 0906x86 \ s /export/aiimages/osol-0906-ai-x86.iso \ /export/aiserver/osol-0906-ai-x86The following displays:Setting up the target image at /export/aiserver/osol-0906-ai-x86 ... Registering the service 0906x86._OSInstall._tcp.local Detected that DHCP is not set up on this server. If not already configured, please create a DHCP macro named dhcp_macro_0906x86 with: Boot server IP (BootSrvA) : 10.6.68.29 Boot file (BootFile) : 0906x86 GRUB Menu (GrubMenu) : menu.lst.0906x86 If you are running Sun's DHCP server, use the following command to add the DHCP macro, dhcp_macro_0906x86: /usr/sbin/dhtadm -g -A -m dhcp_macro_0906x86 \ -d :BootSrvA=10.6.68.29:BootFile=0906x86:GrubMenu=menu.lst.0906x86: Additionally, if the site specific symbol GrubMenu is not present, please add it as follows: /usr/sbin/dhtadm -g -A -s GrubMenu -d Site,150,ASCII,1,0 Note: Be sure to assign client IP address(es) if needed (e.g., if running Sun's DHCP server, run pntadm(1M)). copying boot file to /tftpboot/pxegrub.I86PC.OpenSolaris-1 Service discovery fallback mechanism set upIn this example, the command creates an install service named 0906x86, using the AI ISO image previously downloaded at /export/aiimages/osol-0906-ai-x86.iso, and storing the resultant net image at /export/aiserver/osol-0906-ai-x86.As shown above, this command outputs the name and values of a macro, dhcp_macro_0906x86, which needs to be added to the DHCP server. If you are using a Sun DHCP server, you can create the above macro on your DHCP server either by using the DHCP Manager or by running the dhtadm commands, provided in the above output, on your DHCP server:On systems which support graphic interfaces, you can use the DHCP Manager, dhcpmgr, instead of the dhtadm command. For more information, see the dhcpmgr(1M) man page. Set up two SPARC clients with MAC addresses of 0:14:4f:1d:b9:14 and 0:14:4f:22:90:50 as follows:Set up the first SPARC client:# installadm create-client e 0:e0:81:5d:bf:e0 \ t /export/aiserver/osol-0906-ai-sparc n 0906sparcThe following displays:Setting up SPARC client... Creating SPARC configuration file Detected that DHCP is not set up on this server. If not already configured, please create a DHCP macro named 0100E0815DBFE0 with: Boot server IP (BootSrvA) : 10.6.68.29 Boot file (BootFile) : http://10.6.68.29:5555/cgi-bin/wanboot-cgi If you are running Sun's DHCP server, use the following command to add the DHCP macro, 0100E0815DBFE0: /usr/sbin/dhtadm -g -A -m 0100E0815DBFE0 -d \ :BootSrvA=10.6.68.29:BootFile=\"http://10.6.68.29:5555/cgi-bin/wanboot-cgi\": Note: Be sure to assign client IP address(es) if needed (e.g., if running Sun's DHCP server, run pntadm(1M)).In this example, the command creates a client-specific setup for the system with a MAC address of 0:e0:81:5d:bf:e0. This client will use the install service previously setup, named 0906sparc, and the install image at /export/aiserver/osol-0906-ai-sparc.As shown above, this command outputs the name and values of a macro, dhcp_macro_0906sparc, which needs to be added to the DHCP server. If you are using a Sun DHCP server, you can create the above macro on your DHCP server either by using the DHCP Manager or by running the dhtadm commands, provided in the above output, on your DHCP server:On systems which support graphic interfaces, you can use the DHCP Manager, dhcpmgr, instead of the dhtadm command. For more information, see the dhcpmgr(1M) man page. Set up the second SPARC client:# installadm create-client e 0:e0:81:5d:bf:e0 \ t /export/aiserver/osol-0906-ai-sparc n 0906sparcThe following displays:Setting up SPARC client... Creating SPARC configuration file Detected that DHCP is not set up on this server. If not already configured, please create a DHCP macro named 0100E0815DBFE0 with: Boot server IP (BootSrvA) : 10.6.68.29 Boot file (BootFile) : http://10.6.68.29:5555/cgi-bin/wanboot-cgi If you are running Sun's DHCP server, use the following command to add the DHCP macro, 0100E0815DBFE0: /usr/sbin/dhtadm -g -A -m 0100E0815DBFE0 -d \ :BootSrvA=10.6.68.29:BootFile=\"http://10.6.68.29:5555/cgi-bin/wanboot-cgi\": Note: Be sure to assign client IP address(es) if needed (e.g., if running Sun's DHCP server, run pntadm(1M)).In this example, the command creates a client-specific setup for the system with MAC address of 0:e0:81:5d:bf:e0. This client will use the install service previously setup, named 0906sparc, and the install image at /export/aiserver/osol-0906-ai-sparc.As shown above, this command outputs the name and values of a macro, dhcp_macro_0906sparc, which needs to be added to the DHCP server. If you are using a Sun DHCP server, you can create the above macro on your DHCP server either by using the DHCP Manager or by running the dhtadm commands, provided in the above output, on your DHCP server:On systems which support graphic interfaces, you can use the DHCP Manager, dhcpmgr, instead of the dhtadm command. For more information, see the dhcpmgr(1M) man page. Create the x86 client with a MAC address of 0:d:56:f2:c3:de as follows:# installadm create-client e 0:10:18:0f:28:26 n 0906x86 \ t /export/aiserver/osol-0906-ai-x86The following displays:Setting up X86 client... Service discovery fallback mechanism set up Detected that DHCP is not set up on this server. If not already configured, please create a DHCP macro named 010010180F2826 with: Boot server IP (BootSrvA) : 10.6.68.29 Boot file (BootFile) : 010010180F2826 If you are running Sun's DHCP server, use the following command to add the DHCP macro, 010010180F2826: /usr/sbin/dhtadm -g -A -m 010010180F2826 -d \ :BootSrvA=10.6.68.29:BootFile=010010180F2826:GrubMenu=menu.lst.010010180F2826: Note: Be sure to assign client IP address(es) if needed (e.g., if running Sun's DHCP server, run pntadm(1M)).If not already configured, enable network boot by creating a macro named 01000D56F2C3DE with: Boot server IP (BootSrvA) : 10.6.35.226 Boot file (BootFile) : 01000D56F2C3DEIn this example, the command creates a client-specific setup for the system with MAC address of 0:d:56:f2:c3:de. This client will use the install service previously setup, named 0906x86, and the install image at /export/aiserver/osol-0906-ai-x86.As shown above, this command outputs the name and values of a macro, dhcp_macro_0906x86, which needs to be added to the DHCP server. If you are using a Sun DHCP server, you can create the above macro on your DHCP server either by using the DHCP Manager or by running the dhtadm commands, provided in the above output, on your DHCP server:On systems which support graphic interfaces, you can use the DHCP Manager, dhcpmgr, instead of the dhtadm command. For more information, see the dhcpmgr(1M) man page. The following command deletes an install service from your system:# installadm delete-service [x] svcnameWith the x option, this command deletes an install service and also removes the associated target image.The svcname is a required field that specifies the name of the install service to be removed. The following command displays a list of all enabled install services on your subnet.# installadm list [n svcname]Using the n option, the command displays the names of any manifests that are associated with the specified install service, svcname. You can enable and disable install services on a system as follows:Use the following command to enable a specified install service.# installadm enable svcnameThe svcname field is required to specify the name of the install service to be enabled.This command also enables the web server associated with the service. Use the following command to disable a specified install service.# installadm disable svcnameThe svcname field is required to specify the name of the install service to be disabled.This command also disables the web server associated with the service. The automated installer includes the SMF service, svc:/system/install/server:default. This SMF service contains the data specific to each install service, such as the following:Install service name Image path Boot file Status of the install service Webserver port You can perform the following tasks by using the automated installer's SMF service:To see a list of the install services, run the following command:# svccfg s svc:/system/install/server:default listpg Each install service is represented by an SMF property group, AI<install service name>. To see the data for a specific install service, run the following command:# svccfg s svc:/system/install/server:default listprop property_group_name The AI SMF service is enabled whenever you run the installadm create-service command. Also, the AI SMF service is enabled anytime you run any of the other installadm command options that impact existing install services. Alternately, you can enable the SMF service by running the following command:# svcadm enable svc:/system/install/server:defaultThe service goes into maintenance mode if there are no install services currently enabled on the install server. You can disable the SMF service by running the following command:# svcadm disable svc:/system/install/server:default For further information about administering install services, see . You can install the OpenSolaris OS to multiple client systems by using your install server. If all your client systems have the same hardware characteristics, then the default installation specifications that you setup by using the installadm create-service command can be used for all client installations. However, client setup is required if you want to install the OpenSolaris OS to clients with varying hardware characteristics. For example, if you want to install to both x86 clients and to SPARC clients, client setup is required.If you plan to install to SPARC client systems, those systems must support WAN boot. For more information, see You can use the installadm create-client command to create specific client configurations and to limit the install services, or to explicitly specify an install service name and image path, that a particular type of client can discover.In order to create custom client specifications, you need to provide the following information:MAC address for the client. Path of the net image to be used by the automated installer for this client. Name of the install service for the client to use for installation. For x86 clients, you can optionally specify boot properties. Use the following command to provide custom client settings.installadm create-client [b property=value,...] e macaddr t imagepath n svcnameThis command has the following options:Use the e option to specify the MAC address, macaddr , of the client. Use the t option to specify the path, imagepath, for the net image to be used with the automated installer.This net image was created when you set up an install service by using the installadm create-service command. Use the n option to specify an install service, svcname, for the client to use for installation. For x86 systems only, the b option may be used to set one or more property values, property=value,..., in the client-specific menu.lst file in /tftpboot. Use this option to set boot properties that are specific to this client. This option can accept multiple property=value pairs. The following example illustrates a specific case where you set up an x86 client that references a specific install service name and a specific source image location.Use the following example command.# installadm create-client b "console=ttya" e 0:e0:81:5d:bf:e0 \ t /export/aiserver/osol-0906-ai-x86 n 0906x86The terminal displays the following output:Setting up X86 client... Service discovery fallback mechanism set up Detected that DHCP is not set up on this server. If not already configured, please create a DHCP macro named 0100E0815DBFE0 with: Boot server IP (BootSrvA) : 10.6.68.29 Boot file (BootFile) : 0100E0815DBFE0 If you are running Sun's DHCP server, use the following command to add the DHCP macro, 0100E0815DBFE0: /usr/sbin/dhtadm -g -A -m 0100E0815DBFE0 -d \ :BootSrvA=10.6.68.29:BootFile=0100E0815DBFE0:GrubMenu=menu.lst.0100E0815DBFE0: Note: Be sure to assign client IP address(es) if needed (e.g., if running Sun's DHCP server, run pntadm(1M)).Using the b option, the command sets the console value, console=ttya, in the client-specific menu.lst file in /tftpboot. Using the e option, the command specifies the MAC address, 0:e0:81:5d:bf:e0, of a particular client that you want to customize. Using the n option, the command specifies an install service name, 0906x86, that you want the client to use for installation. Using the t option, the command specifies the path, /export/aiserver/osol-0906-ai-x86, for a net image that you want to be used for the installation.This net image was created when you set up an install service by using the installadm create-service command. You can view the DHCP configuration results in the DHCP table in the DHCP Manager by using the /usr/sadm/admin/bin/dhcpmgr utility.Go to the /tftpboot directory and view the results of the command as follows.# cd /tftpboot # ls -l lrwxrwxrwx 13:23 0100E0815DBFE0 -> pxegrub.I86PC.OpenSolaris-1 drwxr-xr-x 13:26 I86PC.OpenSolaris-1 -rw-r--r-- 13:23 menu.lst.0100E0815DBFE0 -rwxr-xr-x 13:23 pxegrub.I86PC.OpenSolaris-1 -rw-r--r-- 13:23 rm.0100E0815DBFE0 # cat menu.lst.0100E0815DBFE0 default=0 timeout=30 min_mem64=1536 title OpenSolaris 0906x86 kernel /I86PC.OpenSolaris-1/platform/i86pc/kernel/unix -B console=ttya,install_media=http://135.134.0.10.:5555:/export/aiserver/osol-0906-ai-x86, install_boot=http://135.134.0.10.:555:/export/aiserver/osol-0906-ai-x86/boot, install_service=0906x86,livemode=text module /I86PC.OpenSolaris-1/x86.microrootSee the following additional examples about how to set up custom x86 and SPARC clients: Use the following command to delete an existing install client.# installadm delete-client macaddrThis command deletes an existing client's specific service information that was previously set up using the installadm create-client command.The macaddr field is required to specify the MAC address for the install client.For help with client installations, see and When you create install services by using the installadm create-service command, these services contain XML manifest files. These XML manifest files contain default specifications for installing the OpenSolaris OS to client systems. You can copy the default manifest files and manually edit the copies to create custom installation specifications for particular client systems. In the automated installer application, three kinds of manifests are provided in each install service; AI manifests, SC manifests, and criteria manifests.The AI manifest is an XML document that defines the client installation. Some of the parameters defined are disk target, disk partitions and an Image Packaging System (IPS) repository. The AI manifest schema is based on Relax NG syntax and is installed on the install server as part of the SUNWauto-install-common package. This package is installed automatically when you install the SUNWinstalladm-tools package on the install server. A copy of the AI schema is available at /usr/share/auto_install/ai_schema.rng. The SC manifest or System Configuration manifest contains the information needed to configure the system after installation is completed. Some of the configuration parameters supported are timezone, root password, and adding a user to the installed system. The SC manifest uses DTD syntax. A copy of the schema is available at /usr/share/lib/xml/dtd/service_bundle.dtd.1. The criteria manifest encompasses the AI manifest file and the SC manifest file and associates them with a client. The client sends its hardware characteristics to the install service and gets the criteria manifest file that matches those characteristics. Then the client is installed using the specifications from the criteria manifest. The criteria manifest schema can be found at /usr/share/auto_install/criteria_schema.rng on the install server. When you create an install service by using the installadm create-service command, an AI manifest is automatically copied to the install service. This manifest has default settings that are sufficient for client installations. However, you can change the specifications in an existing manifest to create specific installations for specific clients.The default AI manifest that is provided with install services is as follows:<ai_criteria_manifest> <ai_embedded_manifest> <ai_manifest name="default"> <ai_pkg_repo_default_authority> <main url="http://pkg.opensolaris.org/release" authname="opensolaris.org"/> <mirror url=""/> </ai_pkg_repo_default_authority> <ai_install_packages> <pkg name="entire"/> <pkg name="SUNWcsd"/> <pkg name="SUNWcs"/> <pkg name="babel_install"/> </ai_install_packages> <ai_uninstall_packages> <pkg name="babel_install"/> <pkg name="slim_install"/> </ai_uninstall_packages> <ai_auto_reboot> false </ai_auto_reboot> </ai_manifest> </ai_embedded_manifest> <sc_embedded_manifest name = "AI"> <!-- <"xml version='1.0'"> <!DOCTYPE service_bundle SYSTEM "/usr/share/lib/xml/dtd/service_bundle.dtd.1"> <service_bundle type="profile" name="name"> <service name="ai_properties" version="1" type="service"> <instance name="default" enabled="true"> <property_group name="ai" type="application"> <propval name="username" type="astring" value="jack"/> <propval name="userpass" type="astring" value="9Nd/cwBcNWFZg"/> <propval name="description" type="astring" value="default_user"/> <propval name="rootpass" type="astring" \ value="$5$VgppCOxA$ycFmYW4ObRRHhtsGEygDdexk5bugqgSiaSR9niNCouC"/> <propval name="timezone" type="astring" value="US/Pacific"/> <propval name="hostname" type="astring" value="opensolaris"/> </property_group> </instance> </service> </service_bundle> --> </sc_embedded_manifest> </ai_criteria_manifest> The AI manifest is an XML file that contains a series of fields and field values. Each field and value is enclosed inside XML tags.The XML tags all contain a start tag, such as <name>, and an ending tag, such as </name>. Within each tag, a tag name is given, then that tag's value is given. A tag is a parameter that specifies a piece of information about the manifest itself or about the manifest's installation specifications. Each tag has a value that can be edited to modify the manifest information or to modify the installation specifications in the manifest.For example, see this line in the manifest:<ai_manifest name="default">This <ai_manifest name> tag assigns a name to the manifest. The value that is given for this tag is “default.” You can change this value.The <ai_manifest name> tag with the value, “default,” indicates that the manifest is the default manifest. There can be only one default manifest per install service. You can modify or replace the default manifest. Note the following information about other fields in the AI manifest:You can use the <ai_target_device> tag to specify a particular target disk on which to install the OpenSolaris OS. See . If you do not specify a target disk, the automated installer chooses a default target for installing the OpenSolaris OS.The default target disk is selected as follows:The installer gets the recommended size for installing the OpenSolaris OS from the AI libraries. Currently, the recommended size is 12 GB. The installer searches for available disks on the client.The installer selects only the following types of disks:For SPARC clients, the installer searches for disks with a VTOC label. For x86 clients, the installer searches for Solaris partitions. When the first disk is found, the installer checks the size of that disk.If the size is greater than or equal to the recommended size, the installer selects the disk and returns to the installation procedure. If the size is less than the recommended size, the installer goes to the next disk to check the size. If there is no match, the automated installation fails. The tag, <ai_pkg_repo_default_authority>, defines the IPS repository from which the installation will be performed. You need to provide the URL of the IPS repository and the authority. In the default AI manifest, the IPS repository is set to , and the authority is defined as opensolaris.org. In the tag, <ai_install_packages>, the default manifest instructs the automated installer to install the following packages to the client:entire SUNWcsd SUNWcs babel_install The tag, <ai_uninstall_packages>, lists packages, babel_install and slim_install, that will be uninstalled from the client.Why does the default manifest first install the babel_install package, then uninstall it?babel_install is a cluster consisting of a set of packages. When the babel_install cluster is installed, all the packages in the cluster are installed. However, you cannot uninstall packages that belong to a cluster. By uninstalling the cluster definition, the individual packages can be deleted later. babel_install is used for convenience to install all the required packages, but the cluster definition is not needed after installation of packages are completed. The default manifest removes the cluster definition, so that further customization of the packages can be done.slim_install is another cluster. And, slim_install is part of babel_install which is installed by the default manifest. The default manifest uninstalls slim_install, in order to permit customization. The tag, <ai_auto_reboot>, can be used to request automatic reboot after successful installation. The default value is false, meaning that the client doesn't automatically reboot after successful installation. If this value is changed to true, the client automatically reboots after successful installation. The second part of the default AI manifest is an embedded SC manifest, beginning at the line:<sc_embedded_manifest name = "AI">For instructions about how to modify the SC manifest, see . For a complete summary of the AI manifest contents and possible values, see . You can replace the default AI manifest for an install service with a manifest that you created and revised to suit specific client specifications. Use the following procedure:Copy the automated installer's default manifest from the target image path that is associated with the install service you plan to use.The target image path can be determined with the following command:# svccfg s svc:/system/install/server:default listprop AI<svcname>/image_pathFor example, see the following command and output:# svccfg s svc:/system/install/server:default listprop AIsvc1/image_path \ AIsvc1/image_path astring /export/aiserver/svc1In the above example, the install service, svc1, has an image path of /export/aiserver/svc1. The default manifest, default.xml, located in this image path is at:/export/aiserver/svc1/auto_install/default.xmlOnly install services that were created with OpenSolaris 2009.06 images contain the default.xml manifest file in the image path. For services created with older images, you can copy the default.xml manifest located on the install server at /usr/share/auto_install/default.xml. Keep the <ai_manifest name> tag in your manifest copy set to the value of default. Revise the <ai_embedded_manifest> and <sc_embedded_manifest> sections of your copy as needed. Use the installadm add command to replace the default manifest for an existing install service with your copy as follows:# /usr/sbin/installadm add m manifest_file n svc_nameWhere manifest_file is the name of the manifest copy that you created and modified, and where svc_name is the name of the install service.The installadm add command validates your manifest before replacing the default manifest. The build number or release of the OpenSolaris operating system that you specify in the AI manifest must match the build number or release of the AI ISO image that you specify in the installadm create-service command with the s option. For further information, see . The following examples show other options for modifying the contents of AI manifests.The examples in this section are partial excerpts from AI manifest files, showing only the fields being discussed in that example. Only the last example shows a complete AI manifest. For a complete list of the AI manifest contents and possible values, see . To specify a target on a client for installing the OpenSolaris OS, use the tag, <ai_target_device>, as follows:<ai_target_device> <target_device_name>c0t0d0</target_device_name> </ai_target_device>If you do not specify a target disk, the automated installer chooses a default target for installing the OpenSolaris OS. See . An MPXIO name, such as c0t0000002037CD9F72d0, can be used instead of cXtXdX since the MPXIO name for the device doesn't change between releases. To use the MPXIO device name as the target device, use the MPXIO name, as per the following snippet:<ai_target_device> <target_device_name>c0t0000002037CD9F72d0</target_device_name> </ai_target_device> If a slice isn't specified, the automated installer, by default, selects slice 0 on the client to install the OpenSolaris OS. If you would like to install the OpenSolaris OS on a different slice, you can specify the slice in the AI manifest in the <ai_target_device> tag.This example instructs the installer to install the OpenSolaris OS on slice 4.<ai_target_device> <target_device_name>c0t0000002037CD9F72d0</target_device_name> <target_device_install_slice_number>4</target_device_install_slice_number> </ai_target_device> By default, the automated installer doesn't reboot the client after successful installation of an OpenSolaris OS. However, if you want the client to automatically reboot after a successful installation of the OpenSolaris OS, add the XML tag, <ai_auto_reboot>, in the AI manifest, and set the reboot value in that tag to true, as per the following snippet:<ai_auto_reboot> true </ai_auto_reboot> Partition operations are meaningful only for X86 clients. You can delete existing partitions during client installation. Use the tag, <ai_device_partitioning>, and specify the delete action in the tag to delete a partition during installation.<ai_device_partitioning> <partition_action>delete</partition_action> <partition_number>3</partition_number> </ai_device_partitioning> Partition operations are meaningful only for X86 clients. You can create a new partition during client installation. Use the tag, <ai_device_partitioning>, and specify the create action in the tag to create a partition during installation.The following example creates a Solaris partition. This example uses Gigabytes (GB) as the unit for partition size. You could use megabytes (MB), terabytes (TB), or sectors to define a partition. <ai_device_partitioning> <partition_action>create</partition_action> <partition_type>SOLARIS</partition_type> <partition_size>30</partition_size> <partition_size_units>GB</partition_size_units> </ai_device_partitioning> You can delete an existing VTOC slice during client installation. Use the tag, <ai_device_vtoc_slices>, and specify the delete action in the tag to delete a slice during installation.The size element is required, but only for XML validation. <ai_device_vtoc_slices> <slice_action>delete</slice_action> <slice_number>0</slice_number> <slice_size>20</slice_size> </ai_device_vtoc_slices> You can create a new VTOC slice during client installation. Use the tag, <ai_device_vtoc_slices>, and specify the create action in the tag to create a slice during installation. The following example shows how to create a new slice 5.This example uses GB (Gigabytes) as the unit for slice size.<ai_device_vtoc_slices> <slice_action>create</slice_action> <slice_number>5</slice_number> <slice_size>20</slice_size> <slice_size_units>GB</slice_size_units> </ai_device_vtoc_slices> You can preserve an existing VTOC slice during client installation. Use the tag, <ai_device_vtoc_slices>, and specify the “preserve” action in the tag to preserve an existing slice during installation. The following example shows how to preserve VTOC slice 7.<ai_device_vtoc_slices> <slice_action>preserve</slice_action> <slice_number>7</slice_number> </ai_device_vtoc_slices> The automated installer client must install packages from an IPS repository. The IPS repository can be defined in the AI manifest by using the tag <ai_pkg_repo_default_authority>. This example specifies the repository located at . The name of this repository is opensolaris.org.<ai_manifest name="ai_manifest1"> <ai_pkg_repo_default_authority> <main url="http://pkg.opensolaris.org" authname="opensolaris.org"/> </ai_pkg_repo_default_authority> </ai_manifest> You can add a mirror to an IPS repository in the AI manifest as in this example:<ai_manifest name="ai_manifest1"> <ai_pkg_repo_default_authority> <main url="http://pkg.opensolaris.org" authname="opensolaris.org"/> <mirror url="http://mymirror.test"> </ai_pkg_repo_default_authority> </ai_manifest> The client needs to reach the IPS repository defined in the AI manifest to install the OpenSolaris OS. In a normal configuration, the DHCP server sends DNS information to the client. This information is used to resolve the IPS repository name to an IP address. In cases where DNS is not set up, an HTTP proxy can be used to resolve the IPS repository name and complete the client installation. The XML tag, <ai_http_proxy>, and value in the manifest can contain the URL of the proxy as follows:<ai_manifest name="http_proxy"> <ai_pkg_repo_default_authority> <main url="http://pkg.opensolaris.org" authname="opensolaris.org"/> </ai_pkg_repo_default_authority> <ai_http_proxy url="http://129.101.77.121:8080"/> </ai_manifest> The following packages are needed for a successful installation of the OpenSolaris OS and are included in the AI default manifest:entire SUNWcsd SUNWcs babel_install In the <ai_install_packages> tag, you can additional packages to be added during installation. However, you need to retain the default packages along with the additional packages.In the following example, the openoffice and the SUNWTcl packages are added as part of the OpenSolaris installation.<ai_manifest name="ai_packages"> <ai_install_packages> <pkg name="entire"/> <pkg name="SUNWcsd"/> <pkg name="SUNWcs"/> <pkg name="babel_install"/> <pkg name="openoffice"/> <pkg name="SUNWTcl"/> </ai_install_packages> <ai_uninstall_packages> <pkg name="babel_install"/> <pkg name="slim_install"/> </ai_uninstall_packages> </ai_manifest>The default manifest first installs the babel_install package, then uninstalls it. babel_install is a cluster consisting of set of packages. When the babel_install cluster is installed, all the packages in the cluster are installed. However, you cannot uninstall packages that belong to a cluster. By uninstalling the cluster definition, the individual packages can be deleted later. babel_install is used for convenience to install all the required packages, but the cluster definition is not needed once installation of packages is completed. The default manifest removes the cluster definition, so that further customization of the packages can be done.slim_install is another cluster. And, slim_install is part of babel_install which is installed by the default manifest. The default manifest then uninstalls slim_install, in order to permit customization. If the packages are specified as package names in the manifest without a version noted, the automated installer installs the latest version of the packages. If you want to install a specific version of the OpenSolaris OS, you can specify the version in the package entire.The IPS repositories include the full FMRI for each version of a package. Use the FMRI string to specify a specific version of the package, entire, in the AI manifest. The following example specifies that OpenSolaris build 111 be installed to the client.<ai_manifest name="ai_packages"> <ai_install_packages> <pkg name="entire@0.5.11-0.111"/> <pkg name="SUNWcsd"/> <pkg name="SUNWcs"/> <pkg name="babel_install"/> <pkg name="openoffice"/> <pkg name="SUNWTcl"/> </ai_install_packages> <ai_uninstall_packages> <pkg name="babel_install"/> <pkg name="slim_install"/> </ai_uninstall_packages> </ai_manifest>The build number or release of the AI ISO image that you specify in the installadm create-service command must be the same build number or release of the OpenSolaris operating system that you specify in the AI manifest. You can install custom packages from an IPS repository other than the repository that was used for installation by specifying additional IPS repositories in the AI manifest. Use the tag, <ai_pkg_repo_additional_authority>, to add additional repositories to the AI manifest.<ai_manifest name="example1"> <ai_pkg_repo_default_authority> <main url="http://pkg.opensolaris.org" authname="opensolaris.org"/> </ai_pkg_repo_default_authority> <ai_pkg_repo_additional_authority> <main url="http://pkg.mydomain" authname="mydomain"/> </ai_pkg_repo_additional_authority> </ai_manifest>Sometimes a package might be included in more than one repository. IPS searches for that package in the repositories according to the order of the repository in the manifest. When a package match that includes version number is found, then IPS stops the search and installs that package. The following example shows a complete AI manifest where all the primary fields are in use.<ai_manifest name="ai_manifest1"> <ai_target_device> <target_device_name>c0t0d0</target_device_name> </ai_target_device> <!-- delete partition 3 --> <ai_device_partitioning> <partition_action>delete</partition_action> <partition_number>3</partition_number> </ai_device_partitioning> <ai_device_partitioning> <!-- Create solaris partition --> <partition_action>create</partition_action> <partition_size>30</partition_size> <partition_size_units>GB</partition_size_units> <partition_type>SOLARIS</partition_type> </ai_device_partitioning> <ai_device_vtoc_slices> <!-- Create VTOC slice 4 --> <slice_action>create</slice_action> <slice_number>0</slice_number> <slice_size>30</slice_size> <slice_size_units>GB</slice_size_units> </ai_device_vtoc_slices> <ai_pkg_repo_default_authority> <!-- IPS repository --> <main url="http://pkg.opensolaris.org" authname="opensolaris.org"/> </ai_pkg_repo_default_authority> <ai_http_proxy url="http://129.101.77.121:8080"/> <!-- Use http proxy to install pkgs from IPS --> <ai_auto_reboot>true</ai_auto_reboot> <!-- Automatic reboot after successful installation --> <ai_install_packages> <pkg name="entire" <pkg name="SUNWcsd"/> <pkg name="SUNWcs"/> <pkg name="babel_install"/> <pkg name="SUNWTcl"/> </ai_install_packages> <ai_uninstall_packages> <pkg name="babel_install"/> <pkg name="slim_install"/> </ai_uninstall_packages> </ai_manifest> The SC manifest file provides system configuration specifications for the installed system. You can customize the configuration settings by editing the variable after value= for each of the properties. Below is a complete SC manifest file. Just copy this file and make changes to the attributes to edit the user/password, root password, and timezone fields.For the OpenSolaris 2009.06 release, encrypted passwords are used in the manifest. In the example below, the encrypted user password is “jack”, and the root password is “opensolaris”.One method of generating encrypted passwords for the OpenSolaris OS is to create a user of the intended name and password on the OpenSolaris OS, copy the password from the /etc/shadow file between the 1st and 2nd colons of the user's record, and add that information into the 'userpass' or 'rootpass' values in the manifest. In the following SC manifest example, you could change the user name from “jack” to “mike” in the username property.<?xml version='1.0'?> <!DOCTYPE service_bundle SYSTEM '/usr/share/lib/xml/dtd/service_bundle.dtd.1'> <service_bundle type='profile' name='name'> <service name='ai_properties' version='1' type='service'> <instance name='default' enabled='false'> <property_group name='ai' type='application'> <propval name='username' type='astring' value='jack' /> <propval name='description' type='astring' value='default user' /> <propval name='userpass' type='astring' value='9Nd/cwBcNWFZg' /> <propval name='rootpass' type='astring' \ value='$5$VgppCOxA$ycFmYW4ObRRHhtsGEygDdexk5bugqgSiaSR9niNCouC' /> <propval name='timezone' type='astring' value='US/Pacific' /> <propval name='hostname' type='astring' value='opensolaris' /> </property_group> </instance> </service> </service_bundle> If you want to create new AI manifests and SC manifests, you need to assign the manifests for use with a particular client. Use the following basic procedure:Create your AI manifest. You can copy and use the default manifest that is provided in . Or, you can copy and use the sample manifest that uses all parameters in .Save your AI manifest in a file named ai_manifest1.xml. Create an SC manifest by copying and modifying the example in . Save your SC manifest in a file named sc_mainfest1.xml. Create a criteria manifest based on the specifications of the client. You can use the example in as the first draft for a new criteria manifest. Then see the other examples below to modify your draft. The criteria manifest file is the bridge that connects the AI manifest file and the SC manifest file with a client. Use the criteria manifest file to add the manifests to an install service. The client sends its hardware characteristics to the install service and gets the manifest file that you assigned to the service.The criteria manifest includes the file location of your AI manifest and your SC manifest inside the criteria manifest. See the criteria manifest examples below that refer to the AI manifest, ai_manifest1.xml, and the SC manifest, sc_mainfest1.xml. Add the criteria manifest to the install service by running the following command:# installadm add m manifest.xml n svcnameWhere manifest.xml file is the name of your criteria manifest, and that manifest is being assigned to the install service named svcname. The following examples show options for creating a criteria manifest. Each example below is a complete criteria manifest. You can use this example as the first draft of a new criteria manifest. Use the other examples to modify your draft.The following example assigns ai_manifest1 and sc_manifest1 to the client with IP address, 10.6.68.127. <ai_criteria_manifest> <ai_criteria name="IPV4"> <value>10.6.68.127</value> </ai_criteria> <ai_manifest_file URI="./ai_manifest1.xml"/> <sc_manifest_file name="AI" URI="./sc_manifest1.xml"/> </ai_criteria_manifest>In criteria manifests, include the full path for any manifest file names that are referenced. In the examples in this section, the referenced manifest files reside in the current directory. The path for a manifest file in the current directory uses the format, ./ai_manifest1.xml. The following example assigns ai_manifest1 and sc_manifest1 to the client with MAC address 0:14:4f:20:53:94.<ai_criteria_manifest> <ai_criteria name="MAC"> <value>0:14:4F:20:53:94</value> </ai_criteria> <ai_manifest_file URI="./ai_manifest1.xml"/> <sc_manifest_file name="AI" URI="./sc_manifest1.xml"/> </ai_criteria_manifest> The following example assigns ai_manifest1 and sc_manifest1 to clients in the IP address range, 10.6.68.1 to 10.6.68.200. Since there is more than 1 value, the tag, <range>, should be used.<ai_criteria_manifest> <ai_criteria name="IPV4"> <range> 10.6.88.1 10.6.68.200 </range> </ai_criteria> <ai_manifest_file URI="./ai_manifest1.xml"/> <sc_manifest_file name="AI" URI="./sc_manifest1.xml"/> </ai_criteria_manifest> The following example assigns ai_manifest1 and sc_manifest1 to clients in the MAC address range, 0:14:4F:20:53:94 to 0:14:4F:20:53:A0. Since there is more than 1 value, the tag, <range>, should be used.<ai_criteria_manifest> <ai_criteria name="MAC"> <range> 0:14:4F:20:53:94 0:14:4F:20:53:A0 </range> </ai_criteria> <ai_manifest_file URI="./ai_manifest1.xml"/> <sc_manifest_file name="AI" URI="./sc_manifest1.xml"/> </ai_criteria_manifest> The following example assigns ai_manifest1 and sc_manifest1 to clients that have at least 2 Gbytes memory. The None keyword is used to express no bounding value. The value in the <range> tag is expressed in megabytes, in this case, 2048 MB.<ai_criteria_manifest> <ai_criteria name="MEM"> <range> 2048 unbounded </range> </ai_criteria> <ai_manifest_file URI="./ai_manifest1.xml"/> <sc_manifest_file name="AI" URI="./sc_manifest1.xml"/> </ai_criteria_manifest> The following example assigns ai_manifest1 and sc_manifest1 to clients with an architecture of i86pc.<ai_criteria_manifest> <ai_criteria name="ARCH"> <value>i86pc</value> </ai_criteria> <ai_manifest_file URI="./ai_manifest1.xml"/> <sc_manifest_file name="AI" URI="./sc_manifest1.xml"/> </ai_criteria_manifest> Client installations can be customized by assigning different manifests to different clients' install services. The installadm add command assigns a specific manifest to a client. See the following example.Create a criteria manifest file, criteria_mac.xml, that connects a new AI manifest file, ai_manifest1.xml, to a client. See examples in . Check which install services are running on the subnet by using the following command:# installadm listThe install services running on the system are displayed:service_032509In this example, service_032509 is running on the system. Add the manifest files and the criteria defined by criteria_mac.xml to the install service, service_032509, by using the following command:# installadm add m criteria_mac.xml n service_032509 Run the following command to see that the AI manifest file, ai_manifest1.xml, has been added to the install service.Only the AI manifest name, from the XML <ai_manifest> tag, is registered with the automated installer's database. The criteria manifest's name is not stored in this database. And, the SC manifest is part of the AI manifest. Therefore, the following command output displays only the AI manifest name # installadm list n service_032509The following output shows that the manifest is assigned to the install service.Manifest -------- ai_manifest1.xml If you want to remove an AI manifest file from an install service, use the following command.# installadm remove m manifestname n servicenameFor example, to remove a manifest named ai_manifest1 from the install service, service_032509, use the following command:# installadm remove m ai_manifest1 n service_032509 After you have set up an install server and an install service, and, if desired, modified the manifests for the install service, you are ready to install the OpenSolaris OS to your client systems. Review the following information about automated installations to client systems and what problems might be seen. The client systems for automated installation must meet the following requirements:Any system that meets these requirements can be used as an automated install client, including laptops, desktops, virtual machines, and enterprise servers. Platform Requirement SPARC Clients Supports WAN Boot in the Open Boot PromptSee Minimum memory: 1 GB Minimum disk space: 12 GB x86 Clients Minimum memory: 512 MB Minimum disk space: 12 GB Review the following information about SPARC client installations: Boot the client from the network. For SPARC clients, at the open boot prompt, type:OK boot net:dhcpThe technical details of what occurs during the automated installer (AI) boot of a SPARC client are as follows:The client boots and gets IP address and the bootfile, wanboot-cgi, from the DHCP server. wanboot-cgi reads wanboot.conf and sends the location of the WAN Boot binary to the client. The WAN Boot binary is downloaded using HTTP, and the client boots the WAN Boot program. WAN Boot gets the boot_archive file, and Solaris is booted. Net image archives, solaris.zlib and solarismisc.zlib, are downloaded using HTTP. The AI SMF service does the client discovery and gets the install service by using multicast DNS, a DNS service. The client contacts the server, http server, by using the information in the install service, and gets the AI manifest. The AI install program is invoked with the AI manifest to perform the installation of the OpenSolaris OS to the client. The SPARC client installation is initiated by typing at the open boot prompt:OK boot net:dhcpThe output from the boot sequence displays as follows:{3} ok boot net:dhcp Sun Fire(TM) T1000, No Keyboard Copyright 2006 Sun Microsystems, Inc. All rights reserved. OpenBoot 4.23.4, 8184 MB memory available, Serial #69329298. Ethernet address 0:14:4f:21:e1:92, Host ID: 8421e192. Rebooting with command: boot net:dhcp Boot device: /pci@7c0/pci@0/network@4:dhcp File and args: 1000 Mbps FDX Link up 1000 Mbps FDX Link up <time unavailable> wanboot info: WAN boot messages->console <time unavailable> wanboot info: Starting DHCP configuration <time unavailable> wanboot info: DHCP configuration succeeded <time unavailable> wanboot progress: wanbootfs: Read 366 of 366 kB (100%) <time unavailable> wanboot info: wanbootfs: Download complete Tue Aug 5 17:12:09 wanboot progress: miniroot: Read 165251 of 165251 kB (100%) Tue Aug 5 17:12:09 wanboot info: miniroot: Download complete SunOS Release 5.11 Version snv_111 64-bit Copyright 1983-2009 Sun Microsystems, Inc. All rights reserved. Use is subject to license terms. Hostname: opensolaris Remounting root read/write Probing for device nodes ... Preparing automated install image for use Downloading solaris.zlib archive --11:09:11-- http://10.6.35.226:5555//export/home \ /images/osol-0906-ai-sparc//solaris.zlib => `/tmp/solaris.zlib' Connecting to 10.6.35.226:5555... connected. HTTP request sent, awaiting response... 200 OK Length: 82,679,296 (79M) [text/plain] 100%[====================================>] 82,679,296 33.39M/s 11:09:13 (33.36 MB/s) - `/tmp/solaris.zlib' saved [82679296/82679296] Downloading solarismisc.zlib archive --11:09:13-- http://10.6.35.226:5555//export/home/images \ /osol-0906-ai-sparc//solarismisc.zlib => `/tmp/solarismisc.zlib' Connecting to 10.6.35.226:5555... connected. HTTP request sent, awaiting response... 200 OK Length: 620,032 (606K) [text/plain] 100%[====================================>] 620,032 --.--K/s 11:09:13 (36.48 MB/s) - `/tmp/solarismisc.zlib' saved [620032/620032] --11:09:13-- http://10.6.35.226:5555//export/home/images/ \ osol-0906-ai-sparc//install.conf => `/tmp/install.conf' Connecting to 10.6.35.226:5555... connected. HTTP request sent, awaiting response... 200 OK Length: 39 [text/plain] 100%[====================================>] 39 --.--K/s 11:09:13 (953.58 KB/s) - `/tmp/install.conf' saved [39/39] Done mounting automated install image Configuring devices. Reading ZFS config: done. Automated Installation started The progress of the Automated Installation can be followed by viewing the logfile at /tmp/install_log This section describes errors or problems you might see when booting a SPARC client and possible causes:If a DHCP server is not responding to a SPARC client's request, the following messages display:Sun Fire(TM) T1000, No Keyboard Copyright 2006 Sun Microsystems, Inc. All rights reserved. OpenBoot 4.23.4, 8184 MB memory available, Serial #69329298. Ethernet address 0:14:4f:21:e1:92, Host ID: 8421e192. Rebooting with command: boot net:dhcp Boot device: /pci@7c0/pci@0/network@4:dhcp File and args: 1000 Mbps FDX Link up Timed out waiting for BOOTP/DHCP reply Timed out waiting for BOOTP/DHCP reply Timed out waiting for BOOTP/DHCP reply Timed out waiting for BOOTP/DHCP replyThe timeout message indicates that the client is sending a DHCP request, and no response has been made to that request. This error is probably caused by a DHCP configuration problem. Check whether your client is configured correctly in the DHCP server. If the AI client starts downloading the boot_archive, but then fails with the error, “Boot load failed,” as shown below, that indicates that the client DHCP information is configured incorrectly.Rebooting with command: boot net:dhcp Boot device: /pci@7c0/pci@0/network@4:dhcp File and args: 1000 Mbps FDX Link up HTTP: Bad Response: 500 Internal Server Error Evaluating: Boot load failedThis error could happen if another DHCP server is responding to the client. Check the DHCP configuration for this client. If the configuration appears to be correct, determine whether there is another DHCP server in the subnet. If you are running Sun's DHCP server, you can run the DHCP daemon in debug mode with the command:# /usr/lib/inet/in.dhcpd dv After the AI client has obtained the IP address and initial parameters to start downloading the boot archive, the client might be unable to find or download the boot_archive.If the client cannot find the boot_archive, the following error displays:Rebooting with command: boot net:dhcp Boot device: /pci@7c0/pci@0/network@4:dhcp File and args: 1000 Mbps FDX Link up <time unavailable> wanboot info: WAN boot messages->console <time unavailable> wanboot info: Starting DHCP configuration <time unavailable> wanboot info: DHCP configuration succeeded <time unavailable> wanboot progress: wanbootfs: Read 366 of 366 kB (100%) <time unavailable> wanboot info: wanbootfs: Download complete Tue Aug 5 20:46:43 wanboot alert: miniinfo: Request returned code 500 Tue Aug 5 20:46:44 wanboot alert: Internal Server Error \ (root filesystem image missing) If the AI client finds the boot_archive file but cannot access the file, then the following error is displayed:Rebooting with command: boot net:dhcp Boot device: /pci@7c0/pci@0/network@4:dhcp File and args: 1000 Mbps FDX Link up <time unavailable> wanboot info: WAN boot messages->console <time unavailable> wanboot info: Starting DHCP configuration <time unavailable> wanboot info: DHCP configuration succeeded <time unavailable> wanboot progress: wanbootfs: Read 366 of 366 kB (100%) <time unavailable> wanboot info: wanbootfs: Download complete Tue Aug 5 20:53:02 wanboot alert: miniroot: Request returned code 403 Tue Aug 5 20:53:03 wanboot alert: Forbidden For both of these problems, fix the boot_archive file configured for this client. Check the path name and permissions of the boot_archive at $IMAGE/boot/boot_archive. This message, “ERROR 403: Forbidden,” can be seen if the AI client successfully downloads the boot_archive and boots the OpenSolaris kernel, but fails to get one of the net image archives. An error message is displayed indicating which file is causing the problem. For example, in the output below, the solaris.zlib file does not exist at the specified location.Rebooting with command: boot net:dhcp Boot device: /pci@7c0/pci@0/network@4:dhcp File and args: 1000 Mbps FDX Link up 1000 Mbps FDX Link up <time unavailable> wanboot info: WAN boot messages->console <time unavailable> wanboot info: Starting DHCP configuration <time unavailable> wanboot info: DHCP configuration succeeded <time unavailable> wanboot progress: wanbootfs: Read 366 of 366 kB (100%) <time unavailable> wanboot info: wanbootfs: Download complete Tue Aug 5 21:43:37 wanboot progress: miniroot: Read 165251 of 165251 kB (100%) Tue Aug 5 21:43:38 wanboot info: miniroot: Download complete SunOS Release 5.11 Version snv_111 64-bit Copyright 1983-2009 Sun Microsystems, Inc. All rights reserved. Use is subject to license terms. Hostname: opensolaris Remounting root read/write Probing for device nodes ... Preparing automated install image for use Downloading solaris.zlib archive --15:40:37-- http://10.6.35.226:5555//export/home/images/ai_sparc_111/solaris.zlib => `/tmp/solaris.zlib' Connecting to 10.6.35.226:5555... connected. HTTP request sent, awaiting response... 403 Forbidden 15:40:37 ERROR 403: Forbidden. FAILED Requesting System Maintenance Mode (See /lib/svc/share/README for more information.) Console login service(s) cannot runThis problem can be caused by one of the following conditions:The image path configured in WAN boot is not correct. The image path doesn't exist or is incomplete. Access is denied due to permission issues. Check your DHCP configuration or the contents of the target directory you specified when you ran installadm create-service. Check your WAN boot configuration. If the Sun DHCP server is not used, for example, if an ISC DHCP server is used, then the image path is not sent to the client unless the client asks for the path. If the client does not ask for the path, the following sample output displays:Rebooting with command: boot net:dhcp Boot device: /pci@1e,600000/pci@0/pci@1/pci@0/network@4:dhcp File and args: 1000 Mbps FDX Link up Timed out waiting for BOOTP/DHCP reply 1000 Mbps FDX Link up <time unavailable> wanboot info: WAN boot messages->console <time unavailable> wanboot info: Starting DHCP configuration <time unavailable> wanboot info: DHCP configuration succeeded <time unavailable> wanboot progress: wanbootfs: Read 366 of 366 kB (100%) <time unavailable> wanboot info: wanbootfs: Download complete Thu Mar 26 07:48:13 wanboot progress: miniroot: Read 171484 of 171484 kB (100%) Thu Mar 26 07:48:13 wanboot info: miniroot: Download complete SunOS Release 5.11 Version snv_111 64-bit Copyright 1983-2009 Sun Microsystems, Inc. All rights reserved. Use is subject to license terms. Hostname: opensolaris Remounting root read/write Probing for device nodes ... Preparing automated install image for use Couldn't determine source of automated install image Requesting System Maintenance Mode (See /lib/svc/share/README for more information.) Console login service(s) cannot run Review the following information about x86 client installations: Boot the client from the network. For x86 clients, select the network device to boot from.It may be necessary to modify the BIOS configuration to select network booting. The technical details of what occurs during the automated installer (AI) boot of an x86 client are as follows:The client boots and gets an IP address and the bootfile, pxegrub, from the DHCP server. pxegrub is loaded and reads menu.lst file by using TFTP. pxegrub gets the boot_archive file and Solaris is booted by using TFTP. The net image archives, solaris.zlib and solarismisc.zlib, are downloaded using HTTP. The client contacts the install service through the AI HTTP server, and gets the install service by using multicast DNS, a DNS service. The client contacts the server, http server, by using the information in the install service and gets the AI manifest. The AI install program is invoked with the AI manifest to perform the installation. The x86 client installation is initiated by booting from the network, either by pressing the appropriate function key, for example, some systems use F12 to boot from the network, or by changing the boot order in the BIOS.The first screen displays the following message when the client receives the correct DHCP response:Intel(R) Boot Agent PXE Base Code (PXE-2.1 build 0.86) Copyright(C) 1997-2007, Intel Corporation CLIENT MAC ADDR 00 14 4F 29 04 12 GUID FF2000008 FFFF FFFF FFFF 7BDA264F1400 CLIENT IP: 10.6.68.29 MASK: 255.255.255.0 DHCP IP: 10.6.68.49 GATEWAY: 10.6.68.1Next, the display shows the AI image that will be booted. Typically, there should be only one entry such as:OpenSolaris 2009.06 snv_111 X86Once the image is selected, the following messages are displayed.The image is selected automatically after a timeout. SunOS Release 5.11 Version snv_111 64-bit Copyright 1983-2009 Sun Microsystems, Inc. All rights reserved. Use is subject to license terms. Hostname: opensolaris Remounting root read/write Probing for device nodes ... Preparing automated install image for use Downloading solaris.zlib archive --11:09:11-- http://10.6.35.226:5555//export/home \ /images/osol-0906-ai-x86//solaris.zlib => `/tmp/solaris.zlib' Connecting to 10.6.35.226:5555... connected. HTTP request sent, awaiting response... 200 OK Length: 82,679,296 (79M) [text/plain] 100%[====================================>] 82,679,296 33.39M/s 11:09:13 (33.36 MB/s) - `/tmp/solaris.zlib' saved [82679296/82679296] Downloading solarismisc.zlib archive --11:09:13-- http://10.6.35.226:5555//export/home/images \ /osol-0906-ai-x86//solarismisc.zlib => `/tmp/solarismisc.zlib' Connecting to 10.6.35.226:5555... connected. HTTP request sent, awaiting response... 200 OK Length: 620,032 (606K) [text/plain] 100%[====================================>] 620,032 --.--K/s 11:09:13 (36.48 MB/s) - `/tmp/solarismisc.zlib' saved [620032/620032] --11:09:13-- http://10.6.35.226:5555//export/home/images/ \ osol-0906-ai-x86//install.conf => `/tmp/install.conf' Connecting to 10.6.35.226:5555... connected. HTTP request sent, awaiting response... 200 OK Length: 39 [text/plain] 100%[====================================>] 39 --.--K/s 11:09:13 (953.58 KB/s) - `/tmp/install.conf' saved [39/39] Done mounting automated install image Configuring devices. Reading ZFS config: done. Automated Installation started The progress of the Automated Installation can be followed by viewing the logfile at /tmp/install_log Review the following information about x86 booting errors:If a DHCP server is not responding to an x86 client's request, you see the following messages:Intel(R) Boot Agent PXE Base Code (PXE-2.1 build 0.86) Copyright(C) 1997-2007, Intel Corporation CLIENT MAC ADDR 00 14 4F 29 04 12 GUID FF2000008 FFFF FFFF FFFF 7BDA264F1400 DHCP......... No DHCP or ProxyDHCP offers were received PXE-MOF: Exiting Intel Boot AgentThe timeout message indicates that the client is sending a DHCP request and not getting a response. This issue is probably due to an error in the DHCP configuration. Check to see if your client is configured correctly in the DHCP server. The DHCP server provides an IP address and a location of the initial boot program as part of the DHCP response.If the boot program doesn't exist, then the AI client boot cannot proceed. The following message displays:Intel(R) Boot Agent PXE Base Code (PXE-2.1 build 0.86) Copyright(C) 1997-2007, Intel Corporation CLIENT MAC ADDR 00 14 4F 29 04 12 GUID FF2000008 FFFF FFFF FFFF 7BDA264F1400 CLIENT IP: 10.6.68.29 MASK: 255.255.255.0 DHCP IP: 10.6.68.49 GATEWAY: 10.6.68.1 TFTP. PXE-T02: Access Violation PXE-E3C: TFTP Error - Access violation PXE-MOF: Exiting Intel Boot Agent If the boot program exists, but it's an incorrect program, the AI client hangs after displaying this message:Intel(R) Boot Agent PXE Base Code (PXE-2.1 build 0.86) Copyright(C) 1997-2007, Intel Corporation CLIENT MAC ADDR 00 14 4F 29 04 12 GUID FF2000008 FFFF FFFF FFFF 7BDA264F1400 CLIENT IP: 10.6.68.29 MASK: 255.255.255.0 DHCP IP: 10.6.68.49 GATEWAY: 10.6.68.1 If the client is able to do the initial boot, but the OpenSolaris kernel cannot be booted, the system hangs after the user selects the entry from the GRUB menu.On the install server, check whether the menu.lst file for this client is pointing to a valid boot archive. The boot directory of the image on the server should be loop‐back mounted under the /tftpboot directory as shown in this snippet from df -k:/export/home/images/osol-0906-ai-x86/boot \ 60450439 21678071 38772368 36% /tftpboot/I86PC.OpenSolaris-12If you know the name of the target directory that you used in the installadm create-service command, then you can use that information to find out whether that target directory is mounted. Also, check whether you can access the /tftpboot/I86PC.OpenSolaris-12/boot_archive file. On the install server, if one of the install programs doesn't exist in the location specified in the menu.lst file under /tftpboot, then the client is able to boot, but is not able to download that file. An error message is displayed indicating which file is causing the problem. For example, in the output below, the solaris.zlib file does not exist at the specified location.SunOS Release 5.11 Version snv_111 64-bit Copyright 1983-2009 Sun Microsystems, Inc. All rights reserved. Use is subject to license terms. Hostname: opensolaris Remounting root read/write Probing for device nodes ... Preparing automated install image for use Downloading solaris.zlib archive --15:40:37-- http://10.6.35.226:5555//export/home/images/ai_x86_111/solaris.zlib => `/tmp/solaris.zlib' Connecting to 10.6.35.226:5555... connected. HTTP request sent, awaiting response... 403 Forbidden 15:40:37 ERROR 403: Forbidden. FAILED Requesting System Maintenance Mode (See /lib/svc/share/README for more information.) Console login service(s) cannot runCheck the contents of the target directory that you specified when you ran the installadm create-service command. The following situations and display messages are common to both SPARC and X86 installations.If the client is able to successfully boot and download the install files, then the following displays:Automated Installation started The progress of the Automated Installation can be followed by viewing the logfile at /tmp/install_logYou can login as root with the password, “opensolaris,” to monitor the install_log. Once the installation of packages from IPS has started, there may not be updates to this log file for an extended period. You can continue to monitor progress by following the IPS updates in the log file, /var/svc/log/application-auto-installer:default.log. If you see the message, “Auto install succeeded. You may wish to reboot the system at this time,” then the installation is successful. You can manually reboot., Or, if you have setup automatic reboot in the AI manifest, then the system reboots at this time. If there is a failure during installation, then the following message displays:Automated Installation failed. Please refer to /tmp/install_log file for details Apr 9 14:28:09 opensolaris svc.startd[7]: application/auto-installer:default failed fatally: transitioned to maintenance (see 'svcs -xv' for details) If there is a failure during installation, check the log file, /tmp/install_log. If the AI client could not access the package server for installing packages, you may see the following error messages:installation will be performed from http://pkg.opensolaris.org (opensolaris.org) list of packages to be installed is: entire SUNWcsd SUNWcs babel_install pkg: The URL 'http://pkg.opensolaris.org' does not appear to point to a valid pkg server. Please check the server's address and client's network configuration. Additional details: Unable to contact valid package server: http://pkg.opensolaris.org/ Encountered the following error(s): Transport errors encountered when trying to contact depot server. Reported the following errors: Could not retrieve versions from 'opensolaris.org' URLError, reason: (8, 'node name or service name not known') Unable to initialize the pkg image area at /aThe problem may caused by one of the following reasons:The pkg_server is down. Try to access the pkg_server and check status. If you are using DNS, check whether the AI client is setup with DNS:# svcs a | grep /network/dns/clientIf the install service is disabled, then the client is not setup with DNS. Check your DHCP server configuration to see whether DNS information is sent with the DHCP offer. If not, add the DNS information to the client's DHCP macro. If you are not using DNS, add the HTTP proxy information to the AI manifest and try the installation again. See . If one of the packages specified in the AI manifest cannot be located in the IPS repositories, then the installer fails before installing any packages on the disk. In the following example, the installer could not find the package, SUNWTestPkg, in the IPS repository. You may see the following error message in the install_log:<AI Feb 12 20:15:40> installation will be performed from http://pkg.opensolaris.org/dev (opensolaris.org) <AI Feb 12 20:15:40> list of packages to be installed is: <AI Feb 12 20:15:40> entire SUNWcsd SUNWcs babel_install <AI Feb 12 20:15:40> SUNWTestPkg <OM Feb 12 20:15:40> Set zfs root pool device <OM Feb 12 20:15:40> creating zpool <OM Feb 12 20:15:43> /usr/sbin/zfs get -Hp -o value available rpool <OM Feb 12 20:15:43> Creating swap and dump on ZFS volumes <OM Feb 12 20:16:00> TI process completed successfully <OM Feb 12 20:16:00> Transfer process initiated <TRANSFERMOD Feb 12 20:16:59> IPS initilization finished <TRANSFER_MOD Feb 12 20:52:33> pkg missing <TRANSFERMOD Feb 12 20:52:33> IPS transfer failed <TRANSFERMOD Feb 12 20:52:33> IPS transfer finished <OM Feb 12 20:52:33> Transfer failed with error 15 <AI Feb 12 20:52:42> om_perform_install failed with error 114 <AI Feb 12 20:52:42> Auto install failedCheck whether the package in question is a valid package. If this package is available on a different IPS repository, add that IPS repository in the AI manifest by using the tag, <ai_pkg_repo_default_authority>. The error, “om_perform_install_failed with error 800,” indicates that the installer successfully installed all the packages, but one of installer tasks that prepares the system prior to reboot has failed. Scan the install_log for other failures. Usually when this error is returned, one of Install Completion Tasks (ICTs) has failed.This error can also indicate that the version of the AI ISO image that is used for the automated installation is different from the version of the OpenSolaris OS being installed. The AI ISO image version must match the OpenSolaris OS version. Check the install_log to see whether there is any message indicating that the version of the AI ISO image is different from the OpenSolaris OS version being installed. If so, change the AI ISO image to correspond to the OpenSolaris version you are trying to install. For instructions, see For further troubleshooting information, see The following section covers common questions and answers about the automated installer.Troubleshooting Issues:Frequently Asked Questions: Error message displays as follows:# installadm create-service -n sparc_install_service -i 192.168.135.21 -c 2 -s /export/images/osol-0906-109-ai-sparc.iso /data/AI/sparc/snv_109 Setting up the target image at /data/AI/sparc/snv_109 ... Registering the service sparc_install_service._OSInstall._tcp.local Creating DHCP Server Created DHCP configuration file. Dhcptab already exists. Added server macro to dhcptab - sms1. dhcpconfig: Error - starting the DHCP server. entity not found dhtadm: GrubMenu already exists. pntadm: Table for 192.168.135.0 does not exist. pntadm: Table for 192.168.135.0 does not exist. Could not retrieve DHCP information from dhcp server Please create a DHCP macro named dhcp_macro_sparc_install_service with: Boot server IP (BootSrvA) : 192.168.135.10 Boot file (BootFile) : http://192.168.135.10:5555/cgi-bin/wanboot-cgi Failed to assign DHCP macro to IP address. Please assign manually. pntadm: Table for 192.168.135.0 does not exist. pntadm: Table for 192.168.135.0 does not exist. Creating SPARC configuration fileThe installadm command was not able to set up the network table for the addresses. Check to see if this problem is due to one of the following issues:Check whether the SMF service, dhcp-server, is available on the system. Run the following command:# svcs a | grep dhcp-server Check whether /etc/netmasks has the wrong netmasks for the network that is being setup, in the above output, 192.168.135.0. Check that the node name is set to have the loopback address of 127.0.0.1.. Check which OpenSolaris release is installed on your install server. The install server must have the OpenSolaris 2009.06 release. Make any needed corrections to fix the problems that you found. Then, run the following command to cleanup the failed service.installadm delete-service xThen, you can rerun the installadm create-service command. Check whether DNS is configured on your client. You could use the nslookup utility to resolve pkg.opensolaris.org. If your DNS is not working, your DHCP setup for this is not correct. On the DHCP server, check whether DNS information is passed to the client.You must ensure that the DHCP server contains a macro providing a valid DNS domain and DNS servers to the clients. This macro will typically be named with the DHCP server's hostname, and provide the following options: DNSdmain and DNSserv. The install client needs to reach the IPS repository defined in the AI manifest in order to install the OpenSolaris OS. In a normal configuration, the DHCP server sends the DNS information to the client. This DNS information is used to resolve the IPS repository name to an IP address.In cases where DNS is not setup, an HTTP proxy can be used to resolve the IPS repository name to an IP address and complete the installation. The XML tag, <ai_http_proxy>, and value in the AI manifest can contain the URL of the proxy as follows:<ai_manifest name="http_proxy"> .......... .......... <ai_pkg_repo_default_authority> <main url="http://pkg.opensolaris.org" authname="opensolaris.org"/> </ai_pkg_repo_default_authority> <ai_http_proxy url="€�http://129.101.77.121:8080"€�/> </ai_manifest>The error message in the failed installation displays as follows:<OM Oct 28 13:54:08> Transfer process initiated <TRANSFER_MOD_E Oct 28 13:54:10> Unable to initialize the pkg image area at /a <TRANSFER_MOD Oct 28 13:54:10> TValueError or TABort <TRANSFERMOD Oct 28 13:54:10> IPS initialization failedThis error indicates that the client could not resolve the name of the IPS repository. On the failed machine, try to reach the IPS repository you have set up. The default repository is in the AI manifest for this client. You can review the installation log at one of the following locations:If the installation failed, you can find the log at /tmp/install_log. If the installation was successful, you can find the log at /var/sadm/system/logs/install_log after you reboot the client. Review the following additional information about errors that occur when the client system is booting: The following steps can be used to configure a wired network interface to have a static IP address.Run the following series of commands:# svcadm disable network/physical:nwam # svcadm enable network/physical:default # echo <IP_addr> > /etc/hostname.<ifname> # echo <hostname> > /etc/nodename Run the following command:# vi /etc/hostsAnd, append this line to the file:<IP_addr> <hostname> <hostname>.local loghostThen, edit the entries for the loopback addresses, so that these entries contain only 'localhost' as the alias. In other words, edit the line for the '::1' entry to show the following:::1 localhostAnd, edit the line for the 127.0.0.1 entry to show the following:127.0.0.1 localhost Run the following command:# vi /etc/netmasksAnd, append this line to the file:<network> <netmask> Run the following commands:# ifconfig <ifname> plumb # ifconfig <ifname> <IP_addr> netmask <netmask> up If you use DNS to resolve hostnames, perform these additional steps:Configure the file, /etc/resolv.conf(4), to work with the DNS servers for your network. You may need to consult your network administrator for this information.An example of the /etc/resolv.conf file may look like this:domain mycompany.com nameserver 192.168.1.118 nameserver 192.168.2.220 Run the following command:# cp /etc/nsswitch.dns /etc/nsswitch.conf Configure a default route:If your network does not have a discoverable default router, you need to set a static default route on your system. You may need to consult your network administrator for this information. To set up a static default route, add your network's default router IP address to the /etc/defaultrouter(4) file as shown in the following commands:# echo <default_route_IP_addr> >> /etc/defaultrouter # route add default <default_route_IP_addr> The automated installer requires WAN boot support for SPARC clients. You can check whether your client open boot prompt supports WAN boot by checking whether network-boot-arguments is a valid variable that can be set in the eeprom. If the variable network-boot-arguments is displayed, or if it returns the output network-boot-arguments: data not available, the open boot prompt supports WAN boot installations.# eeprom | grep network-boot-arguments network-boot-arguments: data not availableIf there is no output to the above command, then WAN Boot is not supported. Download an AI ISO image for x86 clients or for SPARC clients from . The automated installer will use this AI ISO image to install the OpenSolaris OS to your client systems.Store the AI ISO image on your local file system. For example, store the image at /export/aiimages/osol-0906-ai-x86.iso. You can modify the following default repository information in the manifest file:<ai_pkg_repo_default_authority> <main url="http://pkg.opensolaris.org" authname="opensolaris.org"/> </ai_pkg_repo_default_authority>If your IPS repository is pkg.mycompany.com and the authorization is mycompany.com, change pkg.opensolaris.org to pkg.mycompany.com and opensolaris.org to mycompany.com.<ai_pkg_repo_default_authority> <main url="http://pkg.mycompany.com" authname="mycompany.com"/> </ai_pkg_repo_default_authority> Development builds of the OpenSolaris operating system are available in-between releases. See .The build number or release of the AI ISO image that you specify in the installadm create-service command with the s option must be the same build number or release of the OpenSolaris operating system that you specify in the AI manifest.Check the build number or release for the AI ISO image when you download the image.In the AI manifest, if you want to install a specific version of the OpenSolaris OS, you can specify the version in the package entire. The IPS repositories include the full FMRI for each version of a package. Use the FMRI string to specify a specific version of the package, entire, in the AI manifest.The following example specifies that OpenSolaris build 111 be installed to the client.<ai_manifest name="ai_packages"> <ai_install_packages> <pkg name="entire@0.5.11-0.111"/> <pkg name="SUNWcsd"/> <pkg name="SUNWcs"/> <pkg name="babel_install"/> <pkg name="openoffice"/> <pkg name="SUNWTcl"/> </ai_install_packages> <ai_uninstall_packages> <pkg name="babel_install"/> <pkg name="slim_install"/> </ai_uninstall_packages> </ai_manifest> The default AI manifest for each install service is called default.xml. This file is located at /var/ai/<port>/AI_data, where <port> is the port number of the install service. You can use the following procedure to locate this file.Find the name of the install service that has the default manifest that you want to modify.The name of the install service is the name that you provided in the installadm create-service command when you created the install service. If you didn't provide an install service name, the installadm create-service assigned a service name for your service.You can view a the list of enabled install services on your subnet by using the following command:# /usr/sbin/installadm list Find the port number where this install service is running. You can get your port number using the following command, where <svc_name> is the service name.# svccfg svc:/system/install/server:default listprop AI<svc_name>For example, if the service name is 0906sparc, you can run the following command to get the properties of the 0906sparc:# svccfg svc:/system/install/server:default listprop AI0906sparcExtract the port number from the value, txt_record. Do not modify the default AI manifest file. You can, however, copy this file and create a new default manifest for an install ervice. For instructions, see . If installadm create-service fails to create an install service, use the following procedures to clean up.Run installadm delete-service to remove the failed install service:# installadm delete-service [x] svcname If that command fails with the following message:The specified service does not exist: <svcname>Try the following procedure:Check if the automated installer webserver had been started for the service.First, search for the port number used for the webserver by finding the dns-sd process associated with webserver. An example of how to do this search by using the ps(1) command, and the resulting output, is as follows:# ps -ef | grep dns-sd | grep " svc2 " \ root 11216 1 0 Apr 15 pts/2 0:00 \ /usr/bin/dns-sd -R svc2 _OSInstall._tcp local \ 46502 aiwebserver=192.168.2.1 Kill this process, as in this example:# kill 9 11216The example output shows that the webserver for the serivce, svc2, is being served off of port 46502. Now search for the webserver process that's associated with this port number, and kill that process. See the following example:# ps -ef | grep installadm/webserver | grep 46502 \ root 11026 1 1 Apr 15 pts/2 71:35 \ /usr/bin/python2.4 \ /usr/lib/installadm/webserver -p 46502 /var/ai/46502 # kill -9 11026 Now, remove the data directory for the install service, which also has that port number found above, 4652, it its path:# rm rf /var/ai/46502 If you want to delete the target image path directory that was specified for the failed install service, remove the <targetdir> that you use in the installadm create-service command:# rm rf targetdir As a further step, see When you run the installadm create-service command with the i and c options, the DHCP server is configured . To cleanup the DHCP configurations for a failed or deleted SPARC install service, log into the DHCP Manager and manually remove the DHCP macros for the install service. And, remove any IP addresses that were configured when you created the install service.For more information, see the dhcpmgr(1M) man page. You can run the installer in verbose debug mode, in order to capture more information about the installation in the install_log file.When you use the installadm create-service command to create an install service, or you use the installadm create-client command to set up a custom client, these commands populate the install configuration file. For x86 systems, this file is the GRUB menu.lst file. For SPARC systems, this file is the install.conf file. In order to enable debug mode, you need to set the install_debug option to enable in this install configuration file, as per the following instructions.For x86 systems, the menu.lst configuration file is created in the /tftpboot/ directory with one of the following filename formats:If you used the installadm create-service -n <service_name> command, the filename is menu.lst.<service_name>. If you used the installadm create-client -e <mac> command, the filename is menu.lst.01<mac>. In this file, the options are provided as kernel parameters, such as the following:kernel$ ... -B install_media=...,livessh=enable,install_debug=enableSince the install_debug option in the above example is set to enable, the installer will run in verbose debug mode. For SPARC systems, the install.conf file is populated in the ai_image_dest directory when an install service is created by using an installadm create-service command, such as the following:# installadm create-service [n svc_name] [s ai_iso_image] ai_image_destIn the install.conf file, the options are defined as name-value pairs, such as the following:$ cat <ai_image_dest>/install.conf ... install_debug=enable ...Since the install_debug option in the above example is set to enable, the installer will run in verbose debug mode. You can enable network access to an automated install client by using ssh. You can use this access to remotely observe an installation process.Enable this access by setting the option, livessh, to enable in the installation configuration file. When this access is enabled, you can log in to the AI client by using the username and password, “jack/jack”.For x86 systems, the menu.lst configuration file is created in the /tftpboot/ directory with one of the following filename formats:If you used the installadm create-service -n <service_name> command, the filename is menu.lst.<service_name>. If you used the installadm create-client -e <mac> command, the filename is menu.lst.01<mac>. In this file, the options are provided as kernel parameters, such as the following:kernel$ ... -B install_media=...,livessh=enable,install_debug=enableThe livessh option is this excerpt is set to enable. For SPARC systems, the install.conf file is populated in the ai_image_dest directory when an install service is created by using an installadm create-service command such as the following:# installadm create-service [-n <service_name>] [-s <ai_iso_image>] <ai_image_dest>In the install.conf file, the options are defined as name-value pairs, such as:$ cat <ai_image_dest>/install.conf ... livessh=enable ...The livessh option is this excerpt is set to enable. You can boot to single-user mode using s as an option to the kernel. Use the following instructions:Make sure to use the s option so that an installation will not begin. Specify the s option as follows:For a SPARC system, use the following command:OK boot net:dhcp s For an x86 system, edit the GRUB menu and add the s option to the kernel line. Login as root and run the following command:svcadm disable auto-installer One method of generating encrypted passwords for the OpenSolaris OS is to create a user of the intended name and password on the OpenSolaris OS, copy the password from the /etc/shadow file between the 1st and 2nd colons of the user's record, and add that information into the 'userpass' or 'rootpass' values in the SC manifest.See . No, the OpenSolaris 2009.06 automated installer is not backward compatible with ISO images or automated installer tools from earlier OpenSolaris releases. Use OpenSolaris 2009.06 automated installer tools and procedures with the OpenSolaris 2009.06 operating system and 2009.06 ISO images only. You can use the <ai_target_device> tag to specify a particular target disk on which to install the OpenSolaris OS. See . If you do not specify a target disk, the automated installer chooses a default target for installing the OpenSolaris OS.The default target disk is selected as follows:The installer gets the recommended size for installing the OpenSolaris OS from the AI libraries. Currently, the recommended size is 12 GB. The installer searches for available disks on the client.The installer selects only the following types of disks:For SPARC clients, the installer searches for disks with a VTOC label. For x86 clients, the installer searches for Solaris partitions. When the first disk is found, the installer checks the size of that disk.If the size is greater than or equal to the recommended size, the installer selects the disk and returns to the installation procedure. If the size is less than the recommended size, the installer goes to the next disk to check the size. If there is no match, the automated installation fails. Additional information and resources for using the automated installer are available at the following sites:For general troubleshooting help, see the Release Notes posted at . Send questions or comments about the automated installer application to caiman-discuss@opensolaris.org. Submit bugs or enhancement requests to . For reference, see the following:AI Manifest File Parameters As described in , you can replace the default AI manifest for an install service with a manifest that contains specifications for particular clients. See the following detailed summaries of AI manifest contents and possible values: The following table describes each tag in the AI manifest and elements within each tag, and the values that can be entered for each tag and element.Tag Element Within Tag Description <ai_target_device> <ai_target_device> describes the client target to install the OpenSolaris OS. This parameter is optional. If this information is not provided, the automated installer finds a target on the client and installs the OpenSolaris OS. For finding the default target in the case of X86 client, the automated installer looks for an available fdisk partition of the type, “Solaris” with a size greater than the recommended size. In the case of SPARC systems, the installer looks for a VTOC‐labeled disk of the greater than recommended size.The <ai_target_size> can be defined either by the device name, such as c0t0d0, or by the MPXIO name, such as c0t2000002037CD9F72d0. The <ai_target_size> can also be defined by a combination of <target_device_type>, <target_device_vendor>, and <target_device_size>.All elements of <ai_target_device> are optional. <target_device_name> <target_device_name> is the name of the disk device. The device could be a cXtXdX value or an MPXIO name. If the <target_device_name> is specified, all other <ai_target_device> specification parameters, such as <target_device_type>, <target_device_vendor>, and <target_device_size> are ignored. Be cautious while using cXtXdX values, since these values may change across OpenSolaris releases. <target_device_type> <target_device_type> denotes the type of the target disk. Possible values are SCSI, SATA, PATA, and USB. <target_device_vendor> <target_device_vendor> denotes the name of the manufacturer of the disk drives. Possible values include Sun, EMC, Seagate, Fujitsu, and others. <target_device_size> <target_device_size> denotes the disk size of the target device in megabytes (MB). If the size of a disk is equal to the <target_device_size>, then that specific disk is chosen as the target device. <target_device_install_slice_number> <target_device_install_slice_number> denotes the slice where the OpenSolaris OS should be installed. By default, the automated installer installs the OpenSolaris OS on slice 0. The valid values of <target_device_install_slice_number> are 0, 1, 3, 4, 5, 6 and 7. Specifying slice 2 is not allowed, since slice 2 represents the whole disk. <ai_device_partitioning> <ai_device_partitioning> describes the specification for a partition action to be performed during the automated installation of the OpenSolaris OS. You can delete an existing partition or create a new partition during installation. <ai_device_partitioning> is optional and applicable only for X86 clients.All of the following elements of <ai_device_partitioning> are optional. <partition_action> <partition_action> denotes the type of partition‐related operation to be performed during the client installation. The only allowed actions are create and delete. <partition_number> <partition_number> denotes the unique partition identification in the partition table. When this element is combined with the <partition_action> of delete, then the automatic installer deletes the partition with the specified <partition_number>. When the <partition_action> has the value of create, <partition_number> is ignored. <partition_start_sector> If the <partition_action> is create, <partition_start_sector> denotes the sector where the partition should start. If the <partition_action> is delete, then the automated installer tries to delete the partition starting at this sector. <partition_size> <partition_size> denotes the size of the partition to be created or to be deleted. The value of <partition_size> is interpreted based on the <partition_size_units> value. The default size unit is megabytes (MB). The <partition_size> is required for creating a new partition. You can use the special value, max_size, to indicate that you want the automated installer to use the largest free region, and to create the partition with the maximum possible space. <partition_type> <partition_type> denotes the type of the partition to be created or deleted. If <partition_type> is specified in the delete action without any other partition elements, the automated installer deletes all the partitions of that type. The value of <partition_type> could be any integer representing a valid partition type. The automated installer recognizes the values SOLARIS, DOS16, and FAT32. <partition_size_units> <partition_size_units> defines the units for the partition size. The default size unit is megabytes (MB). The possible values for <partition_size_units> include the following:sectors, secs, sec, s, SECTORS, SECS, SEC, or S MB, megabytes, megabyte, mb, m, MEGABYTES, MEGABYTE, M GB, gigabytes, gigabyte, gb, g, GIGABYTES, GIGABYTE, G TB, terabytes, terabyte, tb, t, TERABYTES, TERABYTE, T <ai_device_vtoc_slices> <ai_device_vtoc_slices> specifies VTOC slice‐related operations to be performed during automated installation of the OpenSolaris OS. You can delete an existing slice or create a new slice during installation. You can also choose to preserve an existing VTOC slice during installation. <slice_action> <slice_action> denotes the type of slice‐related operation to be performed during installation. The allowed actions are create, delete, and preserve. <slice_number> <slice_number> denotes the unique slice identification in the VTOC table. When this element is combined with the <slice_action> set to delete, then the automatic installer deletes the slice with the specified <slice_number>. If the <slice_action> is create, then a new slice is created with the specified <slice_number>. If the <slice_action> is preserve, then the specified slice is not touched during installation. <slice_size> <slice_size> denotes the size of the slice to be created or deleted or preserved. The value of <slice_size> is interpreted based on the <slice_size_units> value. The default size unit is megabytes (MB). The <slice_size> is required for creating a new partition. You can use the special value, max_size, to indicate that you want the automated installer to use the largest free region and to create the partition with the maximum possible space. <slice_size_units> <slice_size_units> defines the units for the slice size. The default size unit is megabytes (MB). The possible values for <slice_size_units> include the following:sectors, secs, sec, s, SECTORS, SECS, SEC, or S MB, megabytes, megabyte, mb, m, MEGABYTES, MEGABYTE, M GB, gigabytes, gigabyte, gb, g, GIGABYTES, GIGABYTE, G TB, terabytes, terabyte, tb, t, TERABYTES, TERABYTE, T <ai_pkg_repo_default_authority> <ai_pkg_repo_default_authority> defines the IPS repository from which OpenSolaris installation should be performed. This element is optional. The default value is pkg.opensolaris.org with an authority value of opensolaris.org. <main> <main> defines the primary IPS repository to be used. <main> consists of two attributes, authname and url. The authname is the authority name for the IPS repository. The url attribute points to the location of the IPS repository. <mirror> <mirror> defines the location of a backup IPS repository whose contents are identical to the <main> element and uses the same authname. The mirror element consists of one attribute, url, that points to the location of the IPS repository. This element is optional. There can be more than one mirror. <ai_pkg_repo_addl_authority> <ai_pkg_repo_addl_authority> defines the additional IPS repositories from which installations can be performed. This element is optional. This element can be used to install packages which are not in your default repository. <main> <main> defines the primary IPS repository to be used. <main> consists of two attributes, authname and url. The authname is the authority name for the IPS repository. The url attribute points to the location of the IPS repository. <mirror> <mirror> defines the location of a backup IPS repository whose contents are identical to the <main> element and uses the same authname. The mirror element consists of one attribute, url, that points to the location of the IPS repository. This element is optional. There can be more than one mirror. <ai_install_packages> <ai_install_packages> defines the list of packages to be installed by automated installer during installation. <ai_install_packages> is mandatory. At least one package must be defined in this element. This tag consists of a single element called pkg. This element, pkg, has an attribute called name. The name attribute could be a simple package name, such as SUNWcs, or an incorporation, such as entire, or an FMRI, such as SUNWPython@2.4.4,5.11-0.101:20081119T213939Z. <ai_uninstall_packages> <ai_uninstall_packages> defines the list of packages to be removed by automated installer during installation. <ai_uninstall_packages> is an optional element. The definition of <ai_uninstall_packages> is similar to that of <ai_install_packages>. This tag consists of a single element called pkg. The element, pkg, has an attribute called name. The name attribute could be a simple package name, such as SUNWcs, or an incorporation, such as entire, or an FMRI, such as SUNWPython@2.4.4,5.11-0.101:20081119T213939Z. <ai_http_proxy> The client needs to reach the IPS repository defined in the AI manifest in order to install the OpenSolaris OS. In a normal configuration, the DHCP server sends DNS information to the client. This information is used to resolve the IPS repository name to an IP address. In cases where DNS is not set up, a HTTP proxy can be used to resolve the IPS repository name and complete the client installation.The element <ai_http_proxy> can be used to setup HTTP proxy that can be used for automated installations. <ai_http_proxy> consists of an attribute, url, that points to the HTTP proxy location. This element is optional. <ai_auto_reboot> By default, the automated installer doesn't automatically reboot the client after a successful installation of an OpenSolaris OS. However, if you want the client to reboot automatically after a successful installation of the OpenSolaris OS, <ai_auto_reboot> can be set to true. The possible values of <ai_auto_reboot> are true and false. The following is a complete AI manifest file with comments.<?xml version="1.0" encoding="UTF-8"?> <!-- CDDL HEADER START The contents of this file are subject to the terms of the Common Development and Distribution License (the "License"). You may not use this file except in compliance with the License. You can obtain a copy of the license at usr/src/OPENSOLARIS.LICENSE or http://www.opensolaris.org/os/licensing. See the License for the specific language governing permissions and limitations under the License. When distributing Covered Code, include this CDDL HEADER in each file and include the License file at usr/src/OPENSOLARIS.LICENSE. If applicable, add the following below this CDDL HEADER, with the fields enclosed by brackets "[]" replaced with your own identifying information: Portions Copyright [yyyy] [name of copyright owner] CDDL HEADER END Copyright 2009 Sun Microsystems, Inc. All rights reserved. Use is subject to license terms. --> <!-- =============================================================================== RelaxNG schema for Automatic Installer input manifest specification. Contains schema rules and content specification for AI manifest. =============================================================================== --> <grammar xmlns="http://relaxng.org/ns/structure/1.0" datatypeLibrary="http://www.w3.org/2001/XMLSchema-datatypes"> <start> <element name="ai_manifest"> <attribute name="name"/> <!-- General automatic Installation parameters --> <ref name="auto_installation_manifest"/> </element> </start> <!-- ======================================================================= Parameters used for Automatic installation ======================================================================= --> <define name="auto_installation_manifest"> <interleave> <!-- Any element order is OK. --> <optional> <element name="ai_target_device"> <ref name="ai_target_device_contents"/> </element> </optional> <zeroOrMore> <element name="ai_device_partitioning"> <ref name="ai_device_partitioning_contents"/> </element> </zeroOrMore> <zeroOrMore> <element name="ai_device_vtoc_slices"> <ref name="ai_device_vtoc_slices_contents"/> </element> </zeroOrMore> <optional> <element name="ai_device_zfs_root_pool"> <ref name="ai_zfs_root_pool_contents"/> </element> </optional> <optional> <element name="ai_device_swap"> <ref name="ai_device_swap_contents"/> </element> </optional> <optional> <element name="ai_pkg_repo_default_authority"> <ref name="ai_pkg_repo_contents"/> </element> </optional> <zeroOrMore> <element name="ai_pkg_repo_addl_authority"> <ref name="ai_pkg_repo_contents"/> </element> </zeroOrMore> <!-- ======================================================== Define AI packages ======================================================== --> <choice> <element name="ai_packages"> <zeroOrMore> <element name="package_name"> <text/> </element> </zeroOrMore> </element> <element name="ai_install_packages"> <oneOrMore> <element name="pkg"> <attribute name="name"> <text/> </attribute> </element> </oneOrMore> </element> </choice> <optional> <element name="ai_uninstall_packages"> <oneOrMore> <element name="pkg"> <attribute name="name"> <text/> </attribute> </element> </oneOrMore> </element> </optional> <optional> <element name="ai_http_proxy"> <ref name="ai_http_proxy_contents"/> </element> </optional> <optional> <element name="ai_auto_reboot"> <data type="boolean"/> </element> </optional> </interleave> </define> <!-- ======================================================================= Selections for AI target Device specification ======================================================================= --> <define name="ai_target_device_contents"> <interleave> <optional> <!-- device name like c0t0d0 or MPXIO name like c0t2000002037CD9F72d0 --> <element name="target_device_name"> <text/> </element> </optional> <optional> <element name="target_device_type"> <text/> </element> </optional> <optional> <element name="target_device_vendor"> <text/> </element> </optional> <optional> <element name="target_device_size"> <text/> </element> </optional> <optional> <element name="target_device_install_slice_number"> <choice> <value>0</value> <value>1</value> <value>2</value> <value>3</value> <value>4</value> <value>5</value> <value>6</value> <value>7</value> </choice> </element> </optional> <optional> <element name="target_device_use_solaris_partition"> <data type="boolean"/> </element> </optional> <optional> <element name="target_device_overwrite_root_zfs_pool"> <data type="boolean"/> </element> </optional> </interleave> </define> <!-- ======================================================================= Selections for AI target device partitions specification ======================================================================= --> <define name="ai_device_partitioning_contents"> <interleave> <element name="partition_action"> <choice> <value>create</value> <value>delete</value> </choice> </element> <optional> <element name="partition_number"> <data type="unsignedByte"/> </element> </optional> <optional> <element name="partition_start_sector"> <data type="long"/> </element> </optional> <element name="partition_size"> <text/> <!-- number of "max_size" to use largest free region --> </element> <element name="partition_type"> <text/> </element> <optional> <element name="partition_size_units"> <ref name="disk_space_size_units"/> </element> </optional> </interleave> </define> <!-- ======================================================================= Selections for AI target device vtoc slices specification ======================================================================= --> <define name="ai_device_vtoc_slices_contents"> <interleave> <element name="slice_action"> <choice> <value>create</value> <value>delete</value> <value>preserve</value> </choice> </element> <element name="slice_number"> <data type="unsignedByte"/> </element> <element name="slice_size"> <text/> <!-- number of "max_size" to use largest free region --> </element> <optional> <element name="slice_size_units"> <ref name="disk_space_size_units"/> </element> </optional> </interleave> </define> <!-- ======================================================================= Selections for AI ZFS Root Pool specification ======================================================================= --> <define name="ai_zfs_root_pool_contents"> <interleave> <optional> <element name="enable_mirrored_root"> <data type="boolean"/> </element> </optional> <optional> <element name="zfs_options"> <text/> </element> </optional> </interleave> </define> <!-- ======================================================================= Selections for AI swap specification The target device will be used as swap device ======================================================================= --> <define name="ai_device_swap_contents"> <element name="ai_swap_size"> <data type="unsignedLong"/> </element> </define> <!-- ======================================================================= Define an authority and its mirror backups. ======================================================================= --> <define name="ai_pkg_repo_contents"> <element name="main"> <ref name="ai_repo_name"/> </element> <zeroOrMore> <element name="mirror"> <ref name="ai_mirror_name"/> </element> </zeroOrMore> </define> <define name="ai_repo_name"> <attribute name="authname"> <text/> </attribute> <attribute name="url"> <text/> </attribute> </define> <define name="ai_mirror_name"> <attribute name="url"> <text/> </attribute> </define> <!-- ======================================================================= Define AI proxy ======================================================================= --> <define name="ai_http_proxy_contents"> <attribute name="url"> <text/> </attribute> </define> <!-- ======================================================================= General definitions ======================================================================= --> <!-- ======================================================================= Units measuring sizable regions of space on disk drives ======================================================================= --> <define name="disk_space_size_units"> <choice> <value>sectors</value> <value>secs</value> <!-- disk space sectors (512 bytes) --> <value>sec</value> <!-- disk space sectors (512 bytes) --> <value>s</value> <value>megabytes</value> <value>megabyte</value> <value>mb</value> <value>m</value> <value>gigabytes</value> <value>gigabyte</value> <value>gb</value> <value>g</value> <value>terabytes</value> <value>terabyte</value> <value>tb</value> <value>t</value> <value>SECTORS</value> <value>SECS</value> <!-- disk space sectors (512 bytes) --> <value>SEC</value> <!-- disk space sectors (512 bytes) --> <value>S</value> <value>MEGABYTES</value> <value>MEGABYTE</value> <value>MB</value> <value>M</value> <value>GIGABYTES</value> <value>GIGABYTE</value> <value>GB</value> <value>G</value> <value>TERABYTES</value> <value>TERABYTE</value> <value>TB</value> <value>T</value> </choice> </define> </grammar> System Administration Commands installadm(1M) NAME installadm - Manages automated installations on a network SYNOPSIS /usr/sbin/installadm installadm create-service [-f <bootfile>] [-n <svcname>] [-i <dhcp_ip_start> -c <count_of_ipaddr>] [-s <srcimage>] <targetdir> installadm delete-service [-x] <svcname> installadm list [-n <svcname>] installadm enable <svcname> installadm disable <svcname> installadm add -m <manifest> -n <svcname> installadm remove -m <manifest> -n <svcname> installadm create-client [-b <property>=<value>,...] -t <imagepath> -e <macaddr> -n <svcname> installadm delete-client <macaddr> installadm help [<subcommand>] DESCRIPTION The automated installer (AI) is used to automate the installation of the OpenSolaris OS on one or more SPARC and x86 systems over a network. The installations can differ in architecture, packages installed, disk capacity, and other parameters. The minimal configuration necessary to use the automated installer is to have one system as the server and one client on which to install. On the server, you set up an installation service, which is associated with manifests, or specifications, for specific x86 installations or SPARC installations. Manifests can include information such as a target device, additional packages, partition information, and other parameters. When the client boots, this boot initiates a search for a manifest that matches the client's machine specifications. When a matching manifest is found, the client is installed with the OpenSolaris release according to the specifications in the manifest files. Use the installadm create-service command to set up an install server and create an install service. An install service is a network entity that specifies the parameters for a particular type of installation. These specifications are defined in XML manifest files. The automated installer uses AI ISO images to create the install services. An AI ISO image is a collection of software in a single file. This image is unpacked when an install service is created and used to create a net image that enables client installations. Once an install server and an installation service are set up, you can install the OpenSolaris release to a client on the network, per the default specifications in the install service, by booting the client system. If you want to perform various types of installations in a network, you can create and manage additional install services tailored for each type of installation by using the installadm create-service command. For example, you can set up an install service that installs the OpenSolaris OS to x86 clients and a service that installs the OpenSolaris OS to SPARC clients. If you have clients with varying machine specifications, you can manually create or modify manifests so that the manifests cover those specific machine specifications. Then, you can use the installadm add command to add your new manifests to an install service. If you want a specific client to use a specific install service, you can associate a service to a client by using the installadm create-client command. The installadm utility can be used to accomplish the following tasks: - Set up install services - Set up installation images - Set up or remove clients - Add or delete manifests - Enable or disable install services - List install services - List manifests for an install service SUBCOMMANDS AND OPTIONS The installadm command has the subcommands and options listed below. Also, see EXAMPLES below. installadm Displays command usage. installadm create-service [-f <bootfile>] [-n <svcname>] [-i <dhcp_ip_start> -c <count_of_ipaddr>] [-s <srcimage>] <targetdir> Creates an install service. The command provides the following functionality: - Takes an AI ISO image (<srcimage>), unpacks it, and sets up a net image in a target directory (<targetdir>. The net image enables client installations. - Creates an install service and makes it available on the network. Note the following specifications: - For SPARC install services, the first install service created on an install server is the service that will be used for all client installations that use the install server. If you want a client to use a different install service from this install server, you must use the installadm create-client command to create a client-specific configuration. - By default, both a net image and an install service are created. - If an existing install service name is provided, that existing service is used. - If the -s option is not used, and the <targetdir> contains a valid net image, then a new install service is created with the existing net image. - If the -i option and the -c option are used, and a DHCP server is not yet configured, a DHCP server is configured. - If an already-configured DHCP server exists, that DHCP server is updated. - If DHCP is running on a remote system, updates can happen through secure shell. User must provide authentication. -f <bootfile> Uses this boot file for the install service. If boot file doesn't exist, it is created. If this option is not specified, a boot file is created with a default name. -n <svcname> Uses this install service name instead of default service name. -i <dhcp_ip_start> Sets up a new DHCP server. The IP addresses, starting from dhcp_address_start, are set up. -c <count_of_ipaddr> Sets up a total number of IP addresses in the DHCP table equal to the value of the count_of_ipaddr. The first IP address is the value of dhcp_ip_start that is provided by the -i option. -s <srcimage> Specifies location of AI ISO image to use for setting up the install service. <targetdir> Required: Specifies location to set up net image. installadm delete-service [-x] <svcname> Deletes an install service. Accomplishes the following: - Removes install service from the network. - Stops the web server that is running for this install service. - Removes the manifest files and web server configuration for this install service. -x Deletes the install service and also removes the associated target net image. <svcname> Required: Specifies the install service name. installadm list [-n <svcname>] Lists all enabled install services on a subnet. Or, with -n option, lists manifests associated with a specified install service. -n <svcname> Lists all manifest files associated with the specified install service. installadm enable <svcname> Enables a specified install service. Also, enables the web server associated with the service. <svcname> Required: Specifies the name of the install service to be enabled. installadm disable <svcname> Disables a specified install service. Also, disables the web server associated with the service. <svcname> Required: Specifies the name of the install service to be disabled. installadm add -m <manifest> -n <svcname> Associates manifests with a specific install service, thus making the manifests available on the network, independently from creating a service. -m <manifest> Required: Specifies the path name to a criteria manifest. -n <svcname> Required: Specifies the name of the install service this manifest is to be associated with. Note: If the -n option is not used, a unique name for the install service is automatically assigned using the format, "_install_service_<port_number>". For example, if the port number that installadm selected for an install service is 46510, and the -n option was not used to provide a custom name for the install service, then the install service name will be "_install_service_46510." installadm remove -m <manifest> -n <svcname> Remove a manifest that was published with a specific install service. -m <manifest> Required: Specifies the name of an AI manifest as output by installadm list with -n option. -n <svcname> Required: Specifies the name of the install service this manifest is associated with. installadm create-client [-b <property>=<value>,...] -t <imagepath> -e <macaddr> -n <svcname> Accomplishes optional setup tasks for a specified client, in order to provide custom client settings that vary from the default settings used by the installadm create-service command. Enables user to specify a non-default service name and image path for a client: - Specifies installation service for that client. - Sets up DHCP macro, if it doesn't exist. -b <property>=<value>,... For x86 clients only, sets a property value in the client-specific menu.lst file in /tftpboot. Use this option to set boot properties that are specific to this client. This option can accept multiple property=value pairs. -e <macaddr> Required: Specifies a MAC address for the client. -n <svcname> Required: Specifies the install service for client installation. -t <imagepath> Required: Specifies the path of the net image to be used with automated installer. installadm delete-client <macaddr> Deletes an existing client's specific service information that was previously set up using the installadm create-client command. <macaddr> Required: Specifies a MAC address for the client. installadm help [<subcommand>] Displays the syntax for the installadm utility. <subcommand> If subcommand is provided, the command provides the syntax for that subcommand. EXAMPLES Example 1: Set up an install server and an install service for the first time. The command includes a starting IP address and total count of IP addresses, in order to configure the DHCP server. Example% # installadm create-service -n 0906x86 \ -i 10.6.68.201 -c 5 -s \ /export/aiimages/osol-0906-ai-x86.iso \ /export/aiserver/osol-0906-ai-x86 In this example, the terminal displays the progress as follows: Setting up the target image at /export/aiserver/osol-0906-ai-x86 ... Registering the service 0906x86._OSInstall._tcp.local Creating DHCP Server Created DHCP configuration file. Created dhcptab. Added "Locale" macro to dhcptab. Added server macro to dhcptab - line1-x4100. DHCP server started. Added network macro to dhcptab - 10.0.0.0. Created network table. copying boot file to /tftpboot/pxegrub.I86PC.OpenSolaris-1 Service discovery fallback mechanism set up The AI ISO image is at /export/aiimages/osol-0906-ai-x86.iso. The command sets up a net image and an install service that is based on the AI ISO image. The installation net image is created in the /export/aiserver/osol-0906-ai-x86 target directory. This net image enables client installations. The progress display shows that the install service, named 0906x86, is created. A boot file is created, also named 0906x86, under /tftpboot. The client will get this file name through DHCP. The command also creates a link from the net image at /export/aiserver/osol-0906-ai-x86 to a web server that is running on port 5555. The DHCP server and macro is created. The starting IP address is 0.6.68.201. Five IP addresses are allocated for clients. The command results identify the macro as dhcp_macro_0906x86. Example 2: Use the following sample command to set up a client that references a specific install service and a specific net image location. The install service and net image should already exist. # installadm create-client -b "console=ttya" \ -e 0:e0:81:5d:bf:e0 -t \ /export/aiserver/osol-0906-ai-x86 -n 0906x86 In this example, the terminal displays the following output: --- Setting up X86 client... Service discovery fallback mechanism set up Detected that DHCP is not set up on this server. If not already configured, please create a DHCP macro named 0100E0815DBFE0 with: Boot server IP (BootSrvA) : 10.6.68.29 Boot file (BootFile) : 0100E0815DBFE0 If you are running Sun's DHCP server, use the following command to add the DHCP macro, 0100E0815DBFE0: /usr/sbin/dhtadm -g -A -m 0100E0815DBFE0 -d \ :BootSrvA=10.6.68.29:BootFile=0100E0815DBFE0:\ GrubMenu=menu.lst.0100E0815DBFE0: Note: Be sure to assign client IP address(es) if needed (e.g., if running Sun's DHCP server, run pntadm(1M)). ---- In this example, the command creates a client-specific setup for the system with MAC address of 0:e0:81:5d:bf:e0. This client will use the install service previously set up, named 0906x86, and the net image at /export/aiserver/osol-0906-ai-x86. Using the -b option, the command sets the console value, <console=ttya>, in the client-specific menu.lst file in /tftpboot. As shown above, this command outputs the name of the client-specific macro, 0100E0815DBFE0, and its values that need to be added to the DHCP server. If you have a Sun DHCP server, create the above macro on your DHCP server by running the dhtadm command from the output on your DHCP server. The pntadm(1M) command may need to be called if you set up a Sun DHCP server and client IP addresses need to be assigned. See the pntadm(1M) manpage for more information. On systems which support graphic interfaces, the DHCP Manager may be used instead of the dhtadm or pntadm commands. See the dhcpmgr(1M) manpage for more information. Example 3: Use the following sample command to add a new custom manifest to an existing install service: # installadm add -m criteria_mac.xml \ -n service_032509 The command assigns the manifest, criteria_mac.xml to the install service, service_032509. For further information about creating and using new manifests, see http://dlc.sun.com/osol/docs/content /dev/AIinstall/. ATTRIBUTES SUNWinstalladm-tools package /usr/man/man1m/installadm.1m Package is in development. /usr/sbin/installadm ATTRIBUTE TYPE ATTRIBUTE VALUE Availability SUNWinstalladm-tools Interface Stability In Development SEE ALSO OpenSolaris Automated Installer Guide at /usr/share/doc/auto_install/index.html or at http://dlc.sun.com/osol/docs/content/dev/ AIinstall/ Getting Started With OpenSolaris at http://dlc.sun.com/osol/docs/content/dev/ getstart/ OpenSolaris 2009.06 Last Changed April 30, 2009