6986845 Update references to documentation in man page and remove AI guide from code base
--- a/usr/src/cmd/installadm/Makefile Wed Sep 29 16:37:00 2010 +0200
+++ b/usr/src/cmd/installadm/Makefile Thu Sep 30 11:55:50 2010 -0700
@@ -18,10 +18,7 @@
#
# CDDL HEADER END
#
-
-#
-# Copyright 2010 Sun Microsystems, Inc. All rights reserved.
-# Use is subject to license terms.
+# Copyright (c) 2008, 2010, Oracle and/or its affiliates. All rights reserved.
#
include ../Makefile.cmd
@@ -32,8 +29,6 @@
install_h:= TARGET= install_h
install:= TARGET= install
-SUBDIRS = docs
-
SRCS = installadm.c \
installadm_util.c
@@ -118,15 +113,12 @@
cp $@ ${ARCH}
$(POST_PROCESS)
-$(SUBDIRS): FRC
- cd $@; pwd; echo $(TARGET); $(MAKE) $(TARGET)
-
lint: ${SRCS} ${HDRS}
${LINT.c} ${SRCS}
msgs: ${MSG_DOMAIN}.po
-clean: $(SUBDIRS)
+clean:
rm -f $(PROGS) $(SCRIPTS) *.pyc $(PYTHON_EXECS)
clobber: clean
@@ -136,9 +128,7 @@
install: all .WAIT $(ROOTPYMODULES) $(ROOTPYCMODULES) $(ROOTPYSCRIPTS) \
$(SYSMANIFESTS) $(PROGS) $(ROOTPROGS) $(ROOTSCRIPTS) $(ROOTMANSYS) \
$(ROOTLIBSVCMETHOD) $(SVCMETHODS) $(ROOTPYTHONVENDORINSTALLAI) \
- $(SYSMANIFESTS) $(VARWEB) $(SUBDIRS)
-
-FRC:
+ $(SYSMANIFESTS) $(VARWEB)
include ../Makefile.targ
--- a/usr/src/cmd/installadm/docs/Makefile Wed Sep 29 16:37:00 2010 +0200
+++ /dev/null Thu Jan 01 00:00:00 1970 +0000
@@ -1,134 +0,0 @@
-#
-# 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 2010 Sun Microsystems, Inc. All rights reserved.
-# Use is subject to license terms.
-#
-
-include ../../Makefile.cmd
-
-all:= TARGET= all
-clean:= TARGET= clean
-clobber:= TARGET= clobber
-install:= TARGET= install
-
-HTML_FILES= add.html \
- administer.html \
- advancedsetup.html \
- aimanifest.html \
- appendix.html \
- associate.html \
- autoinstall.html \
- basic.html \
- benefits.html \
- bootable.html \
- bootableclientreq.html \
- bothclient.html \
- cclient.html \
- client.html \
- clientinstall.html \
- clientreq.html \
- clients.html \
- criteria.html \
- customai.html \
- customsc.html \
- delclient.html \
- delete.html \
- docinfo.html \
- enable.html \
- faq.html \
- gentextid-45.html \
- help.html \
- howbootable.html \
- index.html \
- initial.html \
- installadm.html \
- intro.html \
- manifest.html \
- manifest1.html \
- scenario.html \
- setup.html \
- setupfaq.html \
- simple.html \
- smf.html \
- sparcclient.html \
- tasks.html \
- tasks1.html \
- trouble.html \
- use.html \
- view.html \
- whatis.html \
- whybootable.html \
- x86client.html
-
-CSS_FILES= css/advanced.css \
- css/elements.css \
- css/opensol.css
-
-FIGURES_FILES= figures/AIinstall.gif \
- figures/aiflow.gif \
- figures/bootableAI_1.gif
-
-GRAPHICS_FILES= graphics/header_gradientpart.png \
- graphics/opensolaris_logo_trans.png
-
-ROOTAI_DOC_CSS=$(ROOTAI_DOC)/css
-ROOTAI_DOC_FIGURES=$(ROOTAI_DOC)/figures
-ROOTAI_DOC_GRAPHICS=$(ROOTAI_DOC)/graphics
-
-ROOTHTML_FILES= $(HTML_FILES:%=$(ROOTAI_DOC)/%)
-ROOTCSS_FILES= $(CSS_FILES:%=$(ROOTAI_DOC)/%)
-ROOTFIGURES_FILES= $(FIGURES_FILES:%=$(ROOTAI_DOC)/%)
-ROOTGRAPHICS_FILES= $(GRAPHICS_FILES:%=$(ROOTAI_DOC)/%)
-
-$(ROOTAI_DOC):
- $(INS.dir)
-
-$(ROOTAI_DOC_CSS):
- $(INS.dir)
-
-$(ROOTAI_DOC_FIGURES):
- $(INS.dir)
-
-$(ROOTAI_DOC_GRAPHICS):
- $(INS.dir)
-
-$(ROOTAI_DOC)/%: %
- $(INS.file)
-
-all:
-
-clean:
- rm -rf $(ROOTAI_DOC)
-
-clobber: clean
-
-install: $(ROOTAI_DOC) \
- $(ROOTAI_DOC_CSS)\
- $(ROOTAI_DOC_FIGURES) \
- $(ROOTAI_DOC_GRAPHICS) \
- $(ROOTHTML_FILES) \
- $(ROOTCSS_FILES) \
- $(ROOTFIGURES_FILES) \
- $(ROOTGRAPHICS_FILES)
-
-include ../../Makefile.targ
--- a/usr/src/cmd/installadm/docs/add.html Wed Sep 29 16:37:00 2010 +0200
+++ /dev/null Thu Jan 01 00:00:00 1970 +0000
@@ -1,301 +0,0 @@
-<!DOCTYPE HTML PUBLIC "-//W3C//DTD HTML 4.01 Transitional//EN" "http://www.w3.org/TR/html4/loose.dtd">
-<html lang="en-US">
-
-<!-- -->
-<head>
-<!-- GenHTML revision 23436-->
-<meta http-equiv="Content-type" content="text/html; charset=iso-8859-1">
-<title>How to Add Install Services - OpenSolaris 2010.03 Automated Installer Guide</title>
-<meta name="robots" content="index,follow">
-<meta name="robots" content="index,follow">
-<meta name="date" content="2010-03-01">
-<meta name="collection" content="reference">
-<link rel="stylesheet" type="text/css" href="css/elements.css">
-<link rel="stylesheet" type="text/css" href="css/opensol.css">
-</head>
-
-<body>
-
-
-<div class="Masthead">
- <div class="MastheadLogo">
- <a href="http://www.opensolaris.com"><img border="0" src="graphics/opensolaris_logo_trans.png"></img></a>
- </div>
- <div class="Title">OpenSolaris 2010.03 Automated Installer Guide</div>
-</div>
-<div class="headerbar"></div>
-
-
-<table class="Layout" border="0" cellspacing="0" width="100%">
-<tbody>
-
- <tr valign="top" class="PageControls">
- <td></td>
- <td>
- <table width="100%">
- <tr>
- <td>
- <a href="administer.html">Previous</a>
- </td>
- <td align="right">
- <a href="delete.html">Next</a>
- </td>
- </tr>
- </table>
- </td>
- </tr>
-
- <tr valign="top">
- <td class="Navigation" width="200px"><p class="toc level1"><a href="docinfo.html">Document Information</a></p>
-<p class="toc level1 tocsp"><a href="index.html">1. What's New For Automated Installations</a></p>
-<p class="toc level1 tocsp"><a href="intro.html">2. Introduction to the Automated Installer</a></p>
-<p class="toc level1 tocsp"><a href="tasks.html">3. Automated Network Install Task Map</a></p>
-<p class="toc level1 tocsp"><a href="bootable.html">4. Automated Installations That Boot From Media</a></p>
-<p class="toc level1 tocsp"><a href="setup.html">5. Set up an Automated Install Server</a></p>
-<p class="toc level1 tocsp"><a href="administer.html">6. How to Administer an Automated Install Server</a></p>
-<div id="scrolltoc" class="onpage">
-<p class="toc level2"><a href="">How to Add Install Services</a></p>
-</div>
-<p class="toc level2"><a href="delete.html">How to Delete Install Services</a></p>
-<p class="toc level2"><a href="view.html">How to Review What You Have on Your Server</a></p>
-<p class="toc level2"><a href="enable.html">How to Enable and Disable Install Services</a></p>
-<p class="toc level2"><a href="smf.html">How to Administer Install Services by Using the AI SMF Service</a></p>
-<p class="toc level1 tocsp"><a href="client.html">7. How to Administer a Custom Install Client</a></p>
-<p class="toc level1 tocsp"><a href="manifest.html">8. How to Administer Manifest Files</a></p>
-<p class="toc level1 tocsp"><a href="clients.html">9. How to Manage Client Installations</a></p>
-<p class="toc level1 tocsp"><a href="trouble.html">10. Troubleshooting and FAQs for the Automated Installer</a></p>
-<p class="toc level1 tocsp"><a href="appendix.html">11. Appendix</a></p>
-</td>
- <td class="ContentPane" width="705px">
-
- <div class="MainContent">
-
-
-<a name="add"></a><h3>How to Add Install Services</h3>
-<p>Use one of the following procedures:</p>
-<ul><li><p><a href="#add1">How to Add an Install Service Correlated to IP Addresses</a></p></li>
-<li><p><a href="#additional">How to Add Install Services Without Specific IP Addresses</a></p></li></ul>
-
-
-<a name="add1"></a><h4>How to Add an Install Service Correlated to IP Addresses</h4>
-<p>You can use the <tt>installadm create-service</tt> command with <tt>-i</tt> and <tt>-c</tt> options to accomplish
-any of the following:</p>
-<ul><li><p>You want your install server to act as your DHCP server, and you want to set up the proper DHCP settings on the server.</p></li>
-<li><p>You want to correlate specific IP addresses with an install service. Using the <tt>-i</tt> and <tt>-c</tt> options, the <tt>installadm create-service</tt> command assigns a starting IP address and a total number of IP address to be made available to clients of the install service.</p></li>
-<li><p>You want to add more IP addresses that will correlate with an install service.</p></li></ul>
-<p>Use the command with the following options:</p><pre><tt>installadm create-service [<tt>-i</tt> <i>dhcp_ip_start</i> <tt>-c</tt> <i>count_of_ipaddr</i>] [<tt>-s</tt> <i>srcimage</i>] <i>targetdir</i></tt></pre>
-<ul><li><p>Using the <tt>-i</tt> option, the command sets up a new DHCP server. The IP addresses, starting from <i>dhcp_ip_start</i>, are set up.</p></li>
-<li><p>Using the <tt>-c</tt> option, the command sets up a total number of IP addresses in the DHCP table equal to the value of the <i>count_of_ipaddr</i>. The first IP address is the value of <i>dhcp_ip_start</i> that is provided by the <tt>-i</tt> option.</p></li>
-<li><p>Using the <tt>-s</tt> option, the command specifies an AI ISO image, <i>srcimage</i>, to use for setting up the install service. The command expands this image and places it in the <i>targetdir</i> location. This ISO image enables client installations.</p></li></ul>
-
-
-<a name="service"></a><h4>Example: How to Set Up a Server and Multiple x86 Clients</h4>
-<p>This example describes how the <tt>installadm create-service</tt> 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.</p><p>This example has the following conditions:</p>
-<ul><li><p>The server and clients are in the same subnet.</p></li>
-<li><p>You want to install the OpenSolaris 2010.03 release on the first disk of each client.</p></li>
-<li><p>All clients are identical systems, so no additional client customizations are needed.</p></li>
-<li><p>You need to set up a DHCP server on the install server.</p></li></ul>
-<p><b>Run the following command to set up an install service, providing the required initial image source and a target directory.</b></p><p>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.</p><pre><tt>installadm create-service [<tt>-n</tt> <i>svcname</i>] [<tt>-s</tt> <i>srcimage</i>] [<tt>-i</tt> <i>dhcp_ip_start</i></tt> \
-<tt><tt>-c</tt> <i>count_of_ipaddr</i>] <i>targetdir</i></tt></pre><p>This single command sets up an install service on your system.</p><p><b>See the following example:</b></p><pre># <tt>installadm create-service <tt>-n</tt> <i>1003x86</i> <tt>-i</tt> <i>10.6.68.201</i> <tt>-c</tt> <i>5</i></tt> \
-<tt><tt>-s</tt> <i>/export/aiimages/osol-1003-ai-x86.iso</i> <i>/export/aiserver/osol-1003-ai-x86</i></tt></pre><p>In this example, the following progress is displayed:</p><pre>Setting up the target image at /export/aiserver/osol-1003-ai-x86 ...
-Registering the service 1003x86._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</pre><p>The options in this example accomplish the following tasks.</p><a name="gikbr"></a><h6>Table 6-1 Example Components</h6><table><col width="36%"><col width="63%"><tr><th align="left" valign="top" scope="column"><p>Options</p></th>
-<th align="left" valign="top" scope="column"><p>Description</p></th>
-</tr>
-<tr><td align="left" valign="top" scope="row"><p><tt>-s</tt> <tt>/export/aiimages/osol-1003-ai-x86.iso</tt> </p></td>
-<td align="left" valign="top" scope="row"><p>Using the
-<tt>-s</tt> option, the command identifies the path to an AI ISO image, <tt>/export/aiimages/osol-1003-ai-x86.iso</tt>.
-The command unpacks the image and stores it in a target directory,
-<tt>/export/aiserver/osol-1003-ai-x86</tt>. This ISO image enables client installations.</p></td>
-</tr>
-<tr><td align="left" valign="top" scope="row"><p><tt>-n</tt> <tt>1003x86</tt></p></td>
-<td align="left" valign="top" scope="row"><p>Using the <tt>-n</tt> option, the command
-specifies a name, <tt>1003x86</tt>, for the new install service.</p></td>
-</tr>
-<tr><td align="left" valign="top" scope="row"><p><tt>-i</tt> <tt>10.6.68.201</tt> <tt>-c</tt> <tt>5</tt></p></td>
-<td align="left" valign="top" scope="row">
-<ul><li><p>Using the <tt>-i</tt> and <tt>-c</tt> options, the <tt>installadm</tt> command creates a DHCP server and macro.</p></li>
-<li><p>The <tt>-i</tt> option assigns a starting IP address of <tt>10.6.68.201</tt>.</p></li>
-<li><p>The <tt>-c</tt> option allocates 5 IP addresses for clients.</p></li>
-<li><p>The command creates a macro, <tt>dhcp_macro_1003x86</tt>.</p>
-<hr><p><b>Note - </b>You can view the DHCP configuration results in the DHCP table with the DHCP Manager by using the <tt>/usr/sadm/admin/bin/dhcpmgr</tt> utility.</p>
-<hr>
-</li></ul>
-</td>
-</tr>
-</table><p>The progress display provides additional information:</p>
-<ul><li><p>The command copies the default manifest file. Additionally, the command associates the manifest with the install service. The progress display shows that the command created an install service named <tt>1003x86</tt>.</p></li>
-<li><p>The command creates a boot file, <tt>1003x86</tt>, under <tt>/tftpboot</tt>, and creates a <tt>menu.lst</tt> file. The client searches for and locates this boot file name through DHCP.</p>
-<hr><p><b>Note - </b>You can examine the information in the <tt>menu.lst</tt> file. In this example, the file would be called <tt>/tftpboot/menu.lst.1003x86</tt>.</p>
-<hr>
-</li>
-<li><p>The command also provides an AI ISO image on a web server running on port 5555, for example, at <tt>http://<ai server>:5555/export/aiserver/osol-1003-ai-x86/1003x86</tt>.</p></li></ul>
-
-
-<a name="additional"></a><h4>How to Add Install Services Without Specific IP Addresses</h4>
-<p>If you already have the correct DHCP addresses set up on your
-network, 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.</p><p>The syntax for this minimal command is as follows:</p><pre># <tt>installadm create-service</tt> [<tt>-s</tt> <i>srcimage</i>] <i>targetdir</i></pre><p>Using the <tt>-s</tt> option, the command specifies an ISO image, <i>srcimage</i>, to
-use for setting up the install service. The command expands this image and
-places it in the <i>targetdir</i> location. This ISO image enables client installations.</p>
-<hr><p><b>Note - </b>The command displays 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 <tt>dhtadm</tt>
-commands that are provided in the command output.</p>
-<hr>
-
-
-<a name="diffsystem"></a><h4>Example: How to Set Up a Server to Install SPARC and x86 Clients</h4>
-<p>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 in this process. Then, specific examples are provided to illustrate
-this process.</p><p>This example has the following conditions:</p>
-<ul><li><p>The server and clients may or may not be on the same subnet.</p></li>
-<li><p>You want to install the OpenSolaris OS on SPARC and x86 clients.</p></li>
-<li><p>The DHCP server is remote.</p></li>
-<li><p>You want to set up individual clients and assign specific IP addresses to these clients.</p></li></ul>
-<p><b>Run the following commands to set up a SPARC install service and an x86 install service.</b></p>
-<hr><p><b>Note - </b>Because the DHCP server in this example is not set up by
-<tt>installadm</tt> commands, you should not provide a starting IP address and a total
-number of IP addresses to be made available for the clients.</p>
-<hr>
-
-<ol><li><p>Set up a SPARC install service as follows:</p><pre># <tt>installadm create-service <tt>-n</tt> <i>1003sparc</i></tt> \
-<tt><tt>-s</tt> <i>/export/aiimages/osol-1003-ai-sparc.iso</i></tt> \
-<tt><i>/export/aiserver/osol-1003-ai-sparc</i></tt></pre><p>The following is displayed:</p><pre>Setting up the target image at /export/aiserver/osol-1003-ai-sparc ...
-Registering the service 1003sparc._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_1003sparc 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 the Solaris DHCP server, use the following
-command to add the DHCP macro, dhcp_macro_1003sparc:
- /usr/sbin/dhtadm -g -A -m dhcp_macro_1003sparc \
--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 the Solaris DHCP server, run pntadm(1M)).
-Service discovery fallback mechanism set up
-Creating SPARC configuration file</pre><p>In this example, the command creates an install service named <tt>1003sparc</tt>, using the AI ISO image previously downloaded at <tt>/export/aiimages/osol-1003-ai-sparc.iso</tt>, and storing the image at <tt>/export/aiserver/osol-1003-ai-sparc</tt>.</p><p>This command displays the name and values of a macro, <tt>dhcp_macro_1003sparc</tt>, which needs to be added to the DHCP server.</p></li>
-<li><p>Set up an x86 install service as in the following example.</p><pre># <tt>installadm create-service <tt>-n</tt> <i>1003x86</i></tt> \
-<tt><tt>-s</tt> <i>/export/aiimages/osol-1003-ai-x86.iso</i></tt> \
-<tt><i>/export/aiserver/osol-1003-ai-x86</i></tt></pre><p>The following is displayed:</p><pre>Setting up the target image at /export/aiserver/osol-1003-ai-x86 ...
-Registering the service 1003x86._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_1003x86 with:
- Boot server IP (BootSrvA) : 10.6.68.29
- Boot file (BootFile) : 1003x86
- GRUB Menu (GrubMenu) : menu.lst.1003x86
-If you are running the Solaris DHCP server, use the following
-command to add the DHCP macro, dhcp_macro_1003x86:
- /usr/sbin/dhtadm -g -A -m dhcp_macro_1003x86 \
--d :BootSrvA=10.6.68.29:BootFile=1003x86:GrubMenu=menu.lst.1003x86:
-
-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 the Solaris DHCP server, run pntadm(1M)).
-copying boot file to /tftpboot/pxegrub.I86PC.OpenSolaris-1
-Service discovery fallback mechanism set up</pre><p>In this example, the command creates an install service named <tt>1003x86</tt>, using the AI ISO image previously downloaded at <tt>/export/aiimages/osol-1003-ai-x86.iso</tt>, and storing the image at <tt>/export/aiserver/osol-1003-ai-x86</tt>.</p><p>This command displays the name and values of a macro, <tt>dhcp_macro_1003x86</tt>, which needs to be added to the DHCP server.</p></li>
-<li><p>Set up two SPARC clients as follows. In this example, the SPARC clients have MAC addresses of <tt>0:e0:81:5d:bf:e0</tt> and <tt>0:14:4f:22:90:50</tt>.</p>
-<ol><li><p>Set up the first SPARC client:</p><pre># <tt>installadm create-client <tt>-e</tt> <i>0:e0:81:5d:bf:e0</i></tt> \
-<tt><tt>-n</tt> <i>1003sparc</i></tt></pre><p>The following is displayed:</p><pre>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 the Solaris 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 the Solaris DHCP server, run pntadm(1M)).</pre><p>In this example, the command creates a client-specific setup for the system with a MAC address of <tt>0:e0:81:5d:bf:e0</tt>. This client will use the install service previously setup, named <tt>1003sparc</tt>.</p><p>This command displays the name and values of a macro, <tt>0100E0815DBFE0</tt>, which needs to be added to the DHCP server.</p></li>
-<li><p>Set up the second SPARC client:</p><pre># <tt>installadm create-client <tt>-e</tt> <i>0:14:4f:22:90:50</i></tt> \
-<tt><tt>-n</tt> <i>1003sparc</i></tt></pre><p>The following is displayed:</p><pre>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 the Solaris DHCP server, use the following
-command to add the DHCP macro, 0144f229050:
- /usr/sbin/dhtadm -g -A -m 0144f229050 -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 the Solaris DHCP server, run pntadm(1M)).</pre><p>In this example, the command creates a client-specific setup for the system with MAC address of <tt>0:14:4f:22:90:50</tt>. This client will use the install service previously setup, named <tt>1003sparc</tt>.</p><p>This command displays the name and values of a macro, <tt>0144f229050</tt>, which needs to be added to the DHCP server.</p></li></ol>
-</li>
-<li><p>Create an x86 client with a MAC address as follows. In this example, the x86 client has a MAC address of <tt>0:10:18:0f:28:26</tt>.</p><pre># <tt>installadm create-client <tt>-e</tt> <i>0:10:18:0f:28:26</i> <tt>-n</tt> <i>1003x86</i></tt></pre><p>The following is displayed:</p><pre>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 the Solaris 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 the Solaris DHCP server, run pntadm(1M)).</pre><pre>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) : 01000D56F2C3DE</pre><p>In this example, the command creates a client-specific setup for the system with MAC address of <tt>0:d:56:f2:c3:de</tt>. This client will use the install service previously setup, named <tt>1003x86</tt>.</p><p>This command displays the name and values of a macro, <tt>010010180F2826</tt>, which needs to be added to the DHCP server.</p></li></ol>
-
- </div>
- </td>
- </tr>
-
- <tr class="PageControls" valign="top">
- <td></td>
- <td>
- <table width="100%">
- <tr>
- <td>
- <a href="administer.html">Previous</a>
- </td>
- <td align="right">
- <a href="delete.html">Next</a>
- </td>
- </tr>
- </table>
- </td>
- </tr>
-</tbody>
-</table>
-
-
-</body>
-</html>
-
--- a/usr/src/cmd/installadm/docs/administer.html Wed Sep 29 16:37:00 2010 +0200
+++ /dev/null Thu Jan 01 00:00:00 1970 +0000
@@ -1,106 +0,0 @@
-<!DOCTYPE HTML PUBLIC "-//W3C//DTD HTML 4.01 Transitional//EN" "http://www.w3.org/TR/html4/loose.dtd">
-<html lang="en-US">
-
-<!-- -->
-<head>
-<!-- GenHTML revision 23436-->
-<meta http-equiv="Content-type" content="text/html; charset=iso-8859-1">
-<title>How to Administer an Automated Install Server - OpenSolaris 2010.03 Automated Installer Guide</title>
-<meta name="robots" content="index,follow">
-<meta name="robots" content="index,follow">
-<meta name="date" content="2010-03-01">
-<meta name="collection" content="reference">
-<link rel="stylesheet" type="text/css" href="css/elements.css">
-<link rel="stylesheet" type="text/css" href="css/opensol.css">
-</head>
-
-<body>
-
-
-<div class="Masthead">
- <div class="MastheadLogo">
- <a href="http://www.opensolaris.com"><img border="0" src="graphics/opensolaris_logo_trans.png"></img></a>
- </div>
- <div class="Title">OpenSolaris 2010.03 Automated Installer Guide</div>
-</div>
-<div class="headerbar"></div>
-
-
-<table class="Layout" border="0" cellspacing="0" width="100%">
-<tbody>
-
- <tr valign="top" class="PageControls">
- <td></td>
- <td>
- <table width="100%">
- <tr>
- <td>
- <a href="advancedsetup.html">Previous</a>
- </td>
- <td align="right">
- <a href="add.html">Next</a>
- </td>
- </tr>
- </table>
- </td>
- </tr>
-
- <tr valign="top">
- <td class="Navigation" width="200px"><p class="toc level1"><a href="docinfo.html">Document Information</a></p>
-<p class="toc level1 tocsp"><a href="index.html">1. What's New For Automated Installations</a></p>
-<p class="toc level1 tocsp"><a href="intro.html">2. Introduction to the Automated Installer</a></p>
-<p class="toc level1 tocsp"><a href="tasks.html">3. Automated Network Install Task Map</a></p>
-<p class="toc level1 tocsp"><a href="bootable.html">4. Automated Installations That Boot From Media</a></p>
-<p class="toc level1 tocsp"><a href="setup.html">5. Set up an Automated Install Server</a></p>
-<div id="scrolltoc" class="onpage">
-<p class="toc level1 tocsp"><a href="">6. How to Administer an Automated Install Server</a></p>
-</div>
-<p class="toc level2"><a href="add.html">How to Add Install Services</a></p>
-<p class="toc level2"><a href="delete.html">How to Delete Install Services</a></p>
-<p class="toc level2"><a href="view.html">How to Review What You Have on Your Server</a></p>
-<p class="toc level2"><a href="enable.html">How to Enable and Disable Install Services</a></p>
-<p class="toc level2"><a href="smf.html">How to Administer Install Services by Using the AI SMF Service</a></p>
-<p class="toc level1 tocsp"><a href="client.html">7. How to Administer a Custom Install Client</a></p>
-<p class="toc level1 tocsp"><a href="manifest.html">8. How to Administer Manifest Files</a></p>
-<p class="toc level1 tocsp"><a href="clients.html">9. How to Manage Client Installations</a></p>
-<p class="toc level1 tocsp"><a href="trouble.html">10. Troubleshooting and FAQs for the Automated Installer</a></p>
-<p class="toc level1 tocsp"><a href="appendix.html">11. Appendix</a></p>
-</td>
- <td class="ContentPane" width="705px">
-
- <div class="MainContent">
- <a name="administer"></a>Chapter 6<h3>How to Administer an Automated Install Server</h3><p>After you have set up an automated install server, you can perform
-the following administrative tasks as needed. The basic tasks are as follows:</p>
-<ul><li><p>Set up install services and installation images, and set up and update a DHCP server</p></li>
-<li><p>Set up or remove clients</p></li>
-<li><p>Add or delete manifest files</p></li>
-<li><p>Enable or disable install services</p></li>
-<li><p>List services or list manifests for an install service</p></li>
-<li><p>Administer install services by using the AI SMF service</p></li></ul>
-<p>See the instructions and examples provided in the following sections.</p>
- </div>
- </td>
- </tr>
-
- <tr class="PageControls" valign="top">
- <td></td>
- <td>
- <table width="100%">
- <tr>
- <td>
- <a href="advancedsetup.html">Previous</a>
- </td>
- <td align="right">
- <a href="add.html">Next</a>
- </td>
- </tr>
- </table>
- </td>
- </tr>
-</tbody>
-</table>
-
-
-</body>
-</html>
-
--- a/usr/src/cmd/installadm/docs/advancedsetup.html Wed Sep 29 16:37:00 2010 +0200
+++ /dev/null Thu Jan 01 00:00:00 1970 +0000
@@ -1,225 +0,0 @@
-<!DOCTYPE HTML PUBLIC "-//W3C//DTD HTML 4.01 Transitional//EN" "http://www.w3.org/TR/html4/loose.dtd">
-<html lang="en-US">
-
-<!-- -->
-<head>
-<!-- GenHTML revision 23436-->
-<meta http-equiv="Content-type" content="text/html; charset=iso-8859-1">
-<title>How to Complete Server Setup (Advanced Instructions) - OpenSolaris 2010.03 Automated Installer Guide</title>
-<meta name="robots" content="index,follow">
-<meta name="robots" content="index,follow">
-<meta name="date" content="2010-03-01">
-<meta name="collection" content="reference">
-<link rel="stylesheet" type="text/css" href="css/elements.css">
-<link rel="stylesheet" type="text/css" href="css/opensol.css">
-</head>
-
-<body>
-
-
-<div class="Masthead">
- <div class="MastheadLogo">
- <a href="http://www.opensolaris.com"><img border="0" src="graphics/opensolaris_logo_trans.png"></img></a>
- </div>
- <div class="Title">OpenSolaris 2010.03 Automated Installer Guide</div>
-</div>
-<div class="headerbar"></div>
-
-
-<table class="Layout" border="0" cellspacing="0" width="100%">
-<tbody>
-
- <tr valign="top" class="PageControls">
- <td></td>
- <td>
- <table width="100%">
- <tr>
- <td>
- <a href="simple.html">Previous</a>
- </td>
- <td align="right">
- <a href="administer.html">Next</a>
- </td>
- </tr>
- </table>
- </td>
- </tr>
-
- <tr valign="top">
- <td class="Navigation" width="200px"><p class="toc level1"><a href="docinfo.html">Document Information</a></p>
-<p class="toc level1 tocsp"><a href="index.html">1. What's New For Automated Installations</a></p>
-<p class="toc level1 tocsp"><a href="intro.html">2. Introduction to the Automated Installer</a></p>
-<p class="toc level1 tocsp"><a href="tasks.html">3. Automated Network Install Task Map</a></p>
-<p class="toc level1 tocsp"><a href="bootable.html">4. Automated Installations That Boot From Media</a></p>
-<p class="toc level1 tocsp"><a href="setup.html">5. Set up an Automated Install Server</a></p>
-<p class="toc level2"><a href="basic.html">Server Setup</a></p>
-<p class="toc level2"><a href="initial.html">How to Set Up an Install Server (Initial Steps)</a></p>
-<p class="toc level2"><a href="simple.html">How to Complete Server Setup (Simple Instructions)</a></p>
-<div id="scrolltoc" class="onpage">
-<p class="toc level2"><a href="">How to Complete Server Setup (Advanced Instructions)</a></p>
-</div>
-<p class="toc level1 tocsp"><a href="administer.html">6. How to Administer an Automated Install Server</a></p>
-<p class="toc level1 tocsp"><a href="client.html">7. How to Administer a Custom Install Client</a></p>
-<p class="toc level1 tocsp"><a href="manifest.html">8. How to Administer Manifest Files</a></p>
-<p class="toc level1 tocsp"><a href="clients.html">9. How to Manage Client Installations</a></p>
-<p class="toc level1 tocsp"><a href="trouble.html">10. Troubleshooting and FAQs for the Automated Installer</a></p>
-<p class="toc level1 tocsp"><a href="appendix.html">11. Appendix</a></p>
-</td>
- <td class="ContentPane" width="705px">
-
- <div class="MainContent">
-
-
-<a name="advancedsetup"></a><h3>How to Complete Server Setup (Advanced Instructions)</h3>
-<p>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 previous simple instructions.</p>
-
-<a name="advancedsetup1"></a><h4>Completing Server Setup</h4><h6>Before You Begin</h6><p>Complete the initial setup instructions provided in <a href="initial.html">How to Set Up an Install Server (Initial Steps)</a>.</p><ol>
-<li><b>Create an install service by using either the following x86 or SPARC instructions:</b><ul>
-<li><b>For an x86 install service, use the <tt>installadm create-service</tt> command, as in this
-example:</b><pre># <tt>installadm create-service <tt>-n</tt> <i>1003x86</i> <tt>-s</tt> <i>/export/aiimages/osol-1003-ai-x86.iso</i></tt> \
-<tt><i>/export/aiserver/osol-1003-ai-x86</i></tt></pre><p>The following is displayed:</p><pre>Setting up the target image at /export/aiserver/osol-1003-ai-x86 ...
-Registering the service 1003x86._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_1003x86 with:
- Boot server IP (BootSrvA) : 10.6.68.29
- Boot file (BootFile) : 1003x86
- GRUB Menu (GrubMenu) : menu.lst.1003x86
-If you are running the Solaris DHCP server, use the following
-command to add the DHCP macro, dhcp_macro_1003x86:
- /usr/sbin/dhtadm -g -A -m dhcp_macro_1003x86 \
--d :BootSrvA=10.6.68.29:BootFile=1003x86:GrubMenu=menu.lst.1003x86:
-
-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 the Solaris DHCP server, run pntadm(1M)).
-copying boot file to /tftpboot/pxegrub.I86PC.OpenSolaris-1
-Service discovery fallback mechanism set up</pre><p>In this example, the command creates an install service named <tt>1003x86</tt>, using
-the AI ISO image previously downloaded at <tt>/export/aiimages/osol-1003-ai-x86.iso</tt>, and stores it at
-<tt>/export/aiserver/1003x86</tt>.</p><p>This command displays the name and values of a macro, <tt>dhcp_macro_1003x86</tt>, which
-needs to be added to the DHCP server. If you are
-using the Solaris DHCP server, you can create the macro on your DHCP
-server either by using the DHCP Manager or by running the <tt>dhtadm</tt> commands,
-provided in the above output, on your DHCP server.</p><p>If you are setting up the Solaris DHCP server and client IP
-addresses need to be assigned, you may need to use the <tt>pntadm(1M)</tt> command.
-For more information, see the <tt>pntadm(1M)</tt> man page.</p><p>On systems which support graphic interfaces, you can use the DHCP Manager,
-<tt>dhcpmgr</tt>, instead of the <tt>dhtadm</tt> and <tt>pntadm</tt> commands. For more information, see
-the <tt>dhcpmgr(1M)</tt> man page.</p>
-<hr><p><b>Note - </b>You can use the ISC DHCP server instead of the Solaris DHCP
-server. See <a href="faq.html#isc">17. How do I use ISC DHCP With the Automated Installer?</a>.</p>
-<hr>
-</li>
-<li><b>For a SPARC install service, use the <tt>installadm create-service</tt> command as in this
-example:</b><pre># <tt>installadm create-service <tt>-n</tt> <i>1003sparc</i></tt> \
-<tt><tt>-s</tt> <i>/export/aiimages/osol-1003-ai-sparc.iso</i> <i>/export/aiserver/osol-1003-ai-sparc</i></tt></pre><p>The following is displayed:</p><pre>Automated Installations will not work with the current server network setup.
-Setting up the target image at /export/aiserver/osol-1003-ai-sparc ...
-Registering the service 1003sparc._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_1003sparc 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 the Solaris DHCP server, use the following
-command to add the DHCP macro, dhcp_macro_1003sparc:
- /usr/sbin/dhtadm -g -A -m dhcp_macro_1003sparc \
--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 the Solaris DHCP server, run pntadm(1M)).
-Service discovery fallback mechanism set up
-Creating SPARC configuration file</pre><p>In this example, the command creates an install service named <tt>1003sparc</tt>, using
-the AI ISO image previously downloaded at <tt>/export/aiimages/osol-1003-ai-sparc.iso</tt>, and stores it at
-<tt>/export/aiserver/osol-1003-ai-sparc</tt>.</p><p>This command displays the name and values of a macro, <tt>dhcp_macro_1003sparc</tt>, which
-needs to be added to the DHCP server.</p>
-<hr><p><b>Note - </b>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 <tt>installadm create-client</tt> command to
-create a client-specific configuration. See <a href="client.html">Chapter 7, How to Administer a Custom Install Client</a>.</p>
-<hr>
-</li></ul></li>
-<li><b>Optional: Set up a custom install client to use the install service.</b><p>See the following x86 and SPARC examples.</p><ul>
-<li><b>To set up a custom x86 install client, run the <tt>installadm create-client</tt> command
-as shown in the following example:</b><pre># <tt>installadm create-client <tt>-e</tt> <i>0:10:18:0f:28:26</i> <tt>-n</tt> <i>1003x86</i></tt></pre><p>The following is displayed:</p><pre>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 the Solaris 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 the Solaris DHCP server, run pntadm(1M)).</pre><p>In this example, the command creates a client-specific setup for the system with
-a MAC address of <tt>0:10:18:0f:28:26</tt>. This client will use the install service previously
-setup, named <tt>1003x86</tt>.</p><p>This command displays the name and values of a macro, <tt>010010180F2826</tt>, which
-needs to be added to the DHCP server.</p></li>
-<li><b>To set up a custom SPARC install client, run the <tt>installadm create-client</tt> command
-as shown in the following example:</b><pre># <tt>installadm create-client <tt>-e</tt> <i>0:e0:81:5d:bf:e0</i></tt> \
-<tt><tt>-n</tt> <i>1003sparc</i></tt></pre><p>The following is displayed:</p><pre>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 the Solaris 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 the Solaris DHCP server, run pntadm(1M)).</pre><p>In this example, the command creates a client-specific setup for the system with
-a MAC address of <tt>0:e0:81:5d:bf:e0</tt>. This client will use the install service previously
-setup, named <tt>1003sparc</tt>.</p><p>This command displays the name and values of a macro, <tt>0100E0815DBFE0</tt>, which
-needs to be added to the DHCP server. If you are
-using the Solaris DHCP server, you can create the macro on your DHCP
-server either by using the DHCP Manager or by running the <tt>dhtadm</tt> commands,
-provided in the output, on your DHCP server.</p></li></ul></li>
-<li><b>Boot the client from the network.</b><ol style="list-style-type: lower-alpha">
-<li><b>For x86 clients, select the network device to boot from when the client
-boots.</b>
-<hr><p><b>Note - </b>It may be necessary to modify the BIOS configuration to select network booting.</p>
-<hr>
-</li>
-<li><b>For SPARC clients, boot with the following command from the open boot prompt:</b><pre>OK <tt>boot net:dhcp - install</tt></pre></li></ol></li></ol><h6>Troubleshooting</h6><p>For further information, see <a href="administer.html">Chapter 6, How to Administer an Automated Install Server</a>. See, also, <a href="trouble.html">Chapter 10, Troubleshooting and FAQs for the Automated Installer</a>.</p>
- </div>
- </td>
- </tr>
-
- <tr class="PageControls" valign="top">
- <td></td>
- <td>
- <table width="100%">
- <tr>
- <td>
- <a href="simple.html">Previous</a>
- </td>
- <td align="right">
- <a href="administer.html">Next</a>
- </td>
- </tr>
- </table>
- </td>
- </tr>
-</tbody>
-</table>
-
-
-</body>
-</html>
-
--- a/usr/src/cmd/installadm/docs/aimanifest.html Wed Sep 29 16:37:00 2010 +0200
+++ /dev/null Thu Jan 01 00:00:00 1970 +0000
@@ -1,661 +0,0 @@
-<!DOCTYPE HTML PUBLIC "-//W3C//DTD HTML 4.01 Transitional//EN" "http://www.w3.org/TR/html4/loose.dtd">
-<html lang="en-US">
-
-<!-- -->
-<head>
-<!-- GenHTML revision 23436-->
-<meta http-equiv="Content-type" content="text/html; charset=iso-8859-1">
-<title>AI Manifest Contents - OpenSolaris 2010.03 Automated Installer Guide</title>
-<meta name="robots" content="index,follow">
-<meta name="robots" content="index,follow">
-<meta name="date" content="2010-03-01">
-<meta name="collection" content="reference">
-<link rel="stylesheet" type="text/css" href="css/elements.css">
-<link rel="stylesheet" type="text/css" href="css/opensol.css">
-</head>
-
-<body>
-
-
-<div class="Masthead">
- <div class="MastheadLogo">
- <a href="http://www.opensolaris.com"><img border="0" src="graphics/opensolaris_logo_trans.png"></img></a>
- </div>
- <div class="Title">OpenSolaris 2010.03 Automated Installer Guide</div>
-</div>
-<div class="headerbar"></div>
-
-
-<table class="Layout" border="0" cellspacing="0" width="100%">
-<tbody>
-
- <tr valign="top" class="PageControls">
- <td></td>
- <td>
- <table width="100%">
- <tr>
- <td>
- <a href="appendix.html">Previous</a>
- </td>
- <td align="right">
- <a href="installadm.html">Next</a>
- </td>
- </tr>
- </table>
- </td>
- </tr>
-
- <tr valign="top">
- <td class="Navigation" width="200px"><p class="toc level1"><a href="docinfo.html">Document Information</a></p>
-<p class="toc level1 tocsp"><a href="index.html">1. What's New For Automated Installations</a></p>
-<p class="toc level1 tocsp"><a href="intro.html">2. Introduction to the Automated Installer</a></p>
-<p class="toc level1 tocsp"><a href="tasks.html">3. Automated Network Install Task Map</a></p>
-<p class="toc level1 tocsp"><a href="bootable.html">4. Automated Installations That Boot From Media</a></p>
-<p class="toc level1 tocsp"><a href="setup.html">5. Set up an Automated Install Server</a></p>
-<p class="toc level1 tocsp"><a href="administer.html">6. How to Administer an Automated Install Server</a></p>
-<p class="toc level1 tocsp"><a href="client.html">7. How to Administer a Custom Install Client</a></p>
-<p class="toc level1 tocsp"><a href="manifest.html">8. How to Administer Manifest Files</a></p>
-<p class="toc level1 tocsp"><a href="clients.html">9. How to Manage Client Installations</a></p>
-<p class="toc level1 tocsp"><a href="trouble.html">10. Troubleshooting and FAQs for the Automated Installer</a></p>
-<p class="toc level1 tocsp"><a href="appendix.html">11. Appendix</a></p>
-<div id="scrolltoc" class="onpage">
-<p class="toc level2"><a href="">AI Manifest Contents</a></p>
-</div>
-<p class="toc level2"><a href="installadm.html"><tt>installadm(1M)</tt> Man Page</a></p>
-</td>
- <td class="ContentPane" width="705px">
-
- <div class="MainContent">
-
-
-<a name="aimanifest"></a><h3>AI Manifest Contents</h3>
-<p>As described in <a href="manifest.html">Chapter 8, How to Administer Manifest Files</a>, 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:</p>
-<ul><li><p><a href="#tagtable">AI Manifest Tag Values</a></p></li>
-<li><p><a href="#aimanfull">AI Manifest Complete File</a></p></li></ul>
-
-
-<a name="tagtable"></a><h4>AI Manifest Tag Values</h4>
-<p>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.</p><a name="tagtbl"></a><h6>Table 11-1 AI Manifest Tags and Values</h6><table><col width="21%"><col width="20%"><col width="58%"><tr><th align="left" valign="top" scope="column"><p>Tag</p></th>
-<th align="left" valign="top" scope="column"><p>Element Within Tag</p></th>
-<th align="left" valign="top" scope="column"><p>Description</p></th>
-</tr>
-<tr><td align="left" valign="top" scope="row"><p><tt><ai_target_device></tt></p></td>
-<td align="left" valign="top" scope="row"></td>
-<td align="left" valign="top" scope="row"><p><tt><ai_target_device></tt> 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. To locate
-a default target, the automated installer looks for an available disk with at
-least the recommended size.</p><p>All elements of <tt><ai_target_device></tt> are optional.</p><p><b>Starting with the OpenSolaris 2010.03 release</b>, you can specify
-an iSCSI target for automated installations. With iSCSI technology, you can install to
-a disk drive hosted by another computer on the same TCP/IP network. See
-<a href="customai.html#iscsi">Using an iSCSI Target for Installations</a>.</p><p><b>Starting with the OpenSolaris 2010.03 release</b>, there are additional ways to define the target disk, as described
-below. See, also, <a href="customai.html#iediskrepo">Defining a Target for the Installation</a>.</p></td>
-</tr>
-<tr><td align="left" valign="top" scope="row"></td>
-<td align="left" valign="top" scope="row"><p><tt><target_device_name></tt></p></td>
-<td align="left" valign="top" scope="row"><p><tt><target_device_name></tt> is the name of the disk device. The device could
-be a <tt>cXtXdX</tt> value, or you can use <tt>boot_disk</tt> to select the
-current boot disk as an installation target. Be cautious while using <tt>cXtXdX</tt> values,
-since these values may change across OpenSolaris releases.</p><p> You can use multiple criteria
-to specify an installation target, but there are limitations. See <a href="customai.html#multarget">Using Multiple Parameters to Specify an Installation Target</a>.</p></td>
-</tr>
-<tr><td align="left" valign="top" scope="row"></td>
-<td align="left" valign="top" scope="row"><p><tt><target_device_type></tt></p></td>
-<td align="left" valign="top" scope="row"><p><tt><target_device_type></tt> denotes the
-type of the target disk. Possible values are iSCSI, ATA, and USB.</p></td>
-</tr>
-<tr><td align="left" valign="top" scope="row"></td>
-<td align="left" valign="top" scope="row"><p><tt><target_device_vendor></tt></p></td>
-<td align="left" valign="top" scope="row"><p><tt><target_device_vendor></tt> denotes
-the name of the manufacturer of the disk drives. Possible values include Sun,
-EMC, Seagate, Fujitsu, and others. This tag is not case sensitive. See <a href="faq.html#vendor">18. How can I Check the Vendors for my Disks?</a>.</p></td>
-</tr>
-<tr><td align="left" valign="top" scope="row"></td>
-<td align="left" valign="top" scope="row"><p><tt><target_device_size></tt></p></td>
-<td align="left" valign="top" scope="row"><p><tt><target_device_size></tt>
-denotes the disk size of the target device in sectors. One sector equals
-512 bytes. If the size of a disk is equal to the <tt><target_device_size></tt>,
-then that specific disk is chosen as the target device.</p></td>
-</tr>
-<tr><td align="left" valign="top" scope="row"></td>
-<td align="left" valign="top" scope="row"><p><tt><target_device_</tt><tt>install_slice_number></tt></p></td>
-<td align="left" valign="top" scope="row"><p><tt><target_device_install_slice_number></tt> 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 <tt><target_device_install_slice_number></tt> are 0,
-1, 3, 4, 5, 6 and 7. Specifying slice 2 is not allowed,
-since slice 2 represents the whole disk.</p></td>
-</tr>
-<tr><td align="left" valign="top" scope="row"></td>
-<td align="left" valign="top" scope="row"><p><tt><target_device_</tt><tt>select_id></tt></p></td>
-<td align="left" valign="top" scope="row"><p><b>Starting with the OpenSolaris 2010.03 release</b>, you can use the <tt><target_device_select_id></tt>
-tag to select a target disk by its device ID. See <a href="customai.html#devid">Using the Device ID to Specify an Installation Target</a>.</p></td>
-</tr>
-<tr><td align="left" valign="top" scope="row"></td>
-<td align="left" valign="top" scope="row"><p><tt><target_device_</tt><tt>select_device_path></tt></p></td>
-<td align="left" valign="top" scope="row"><p><b>Starting with the OpenSolaris 2010.03 release</b>, you
-can use the <tt><target_device_select_device_path></tt> tag to select a target disk by specifying
-the physical path in the <tt>/devices</tt> directory. See <a href="customai.html#phydevice">Using Physical Device Path to Specify an Installation Target</a>.</p></td>
-</tr>
-<tr><td align="left" valign="top" scope="row"></td>
-<td align="left" valign="top" scope="row"><p><tt><target_device_</tt><tt>select_volume_name></tt></p></td>
-<td align="left" valign="top" scope="row"><p><b>Starting with the OpenSolaris 2010.03 release</b>, you can use
-the <tt><target_device_</tt><tt>select_volume_name></tt> tag to select a target disk by specifying a volume name
-that was created using the <tt>format</tt> command. See <a href="customai.html#volname">Using Volume Name to Specify an Installation Target</a>.</p></td>
-</tr>
-<tr><td align="left" valign="top" scope="row"></td>
-<td align="left" valign="top" scope="row"><p><tt><target_device_</tt><tt>iscsi_target_name></tt></p></td>
-<td align="left" valign="top" scope="row"><p><b>Starting with the OpenSolaris 2010.03 release</b>, you can install into
-an iSCSI target using the iSCSI-specific tags. The iSCSI target name tag can
-accept mixed ASCII entries, with a maximum of about 233 characters.</p></td>
-</tr>
-<tr><td align="left" valign="top" scope="row"></td>
-<td align="left" valign="top" scope="row"><p><tt><target_device_</tt><tt>iscsi_target_ip></tt></p></td>
-<td align="left" valign="top" scope="row"><p>This tag provides
-a valid IP address for an iSCSI installation target.</p></td>
-</tr>
-<tr><td align="left" valign="top" scope="row"></td>
-<td align="left" valign="top" scope="row"><p><tt><target_device_</tt><tt>iscsi_target_port></tt></p></td>
-<td align="left" valign="top" scope="row"><p>This tag provides a
-port number for the iSCSI installation target.</p></td>
-</tr>
-<tr><td align="left" valign="top" scope="row"></td>
-<td align="left" valign="top" scope="row"><p><tt><target_device_</tt><tt>iscsi_target_lun></tt></p></td>
-<td align="left" valign="top" scope="row"><p>This tag provides a logical unit
-number (LUN) that defines an iSCSI device on the target. This number may
-be needed to distinguish between multiple boot disks on the same target. Valid
-values are an integer or integers separated by hyphens. The default is zero
-(0).</p></td>
-</tr>
-<tr><td align="left" valign="top" scope="row"></td>
-<td align="left" valign="top" scope="row"><p><tt><target_device_</tt><tt>iscsi_parameter_source></tt></p></td>
-<td align="left" valign="top" scope="row"><p>This tag specifies where the iSCSI boot parameters will be sought. The default
-is that the parameters are included in the AI manifest. Valid values include
-“manifest” or “DHCP.”</p></td>
-</tr>
-<tr><td align="left" valign="top" scope="row"><p><tt><ai_device_partitioning></tt></p></td>
-<td align="left" valign="top" scope="row"></td>
-<td align="left" valign="top" scope="row"><p><tt><ai_device_partitioning></tt> 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. <tt><ai_device_partitioning></tt> is optional and applicable
-only for x86 clients. During installation, changes specified in the partitioning tags occur
-in the order they are listed in the manifest. All of the following
-elements of <tt><ai_device_partitioning></tt> are optional.</p></td>
-</tr>
-<tr><td align="left" valign="top" scope="row"></td>
-<td align="left" valign="top" scope="row"><p><tt><partition_action></tt></p></td>
-<td align="left" valign="top" scope="row"><p><tt><partition_action></tt> denotes the type of partition-related operation to be
-performed during the client installation. The only allowed actions are <tt>create</tt> and <tt>delete</tt>.</p></td>
-</tr>
-<tr><td align="left" valign="top" scope="row"></td>
-<td align="left" valign="top" scope="row"><p><tt><partition_number></tt></p></td>
-<td align="left" valign="top" scope="row"><p><tt><partition_number></tt>
-denotes the unique partition identification in the partition table. When this element is
-combined with the <tt><partition_action></tt> of <tt>delete</tt>, then the automatic installer deletes the partition with
-the specified <tt><partition_number></tt>. When the <tt><partition_action></tt> has the value of <tt>create</tt>, <tt><partition_number></tt>
-is ignored.</p><p>For primary or extended partitions a legal partition number is 1–4. For
-logical partitions, a legal partition is 5–36.</p></td>
-</tr>
-<tr><td align="left" valign="top" scope="row"></td>
-<td align="left" valign="top" scope="row"><p><tt><partition_start_sector></tt></p></td>
-<td align="left" valign="top" scope="row"><p>If the <tt><partition_action></tt> is <tt>create</tt>, <tt><partition_start_sector></tt>
-denotes the sector where the partition should start. If the <tt><partition_action></tt> is <tt>delete</tt>,
-then the automated installer tries to delete the partition starting at this sector.</p></td>
-</tr>
-<tr><td align="left" valign="top" scope="row"></td>
-<td align="left" valign="top" scope="row"><p><tt><partition_size></tt></p></td>
-<td align="left" valign="top" scope="row"><p><tt><partition_size></tt>
-denotes the size of the partition to be created or to be deleted.
-The value of <tt><partition_size></tt> is interpreted based on the <tt><partition_size_units></tt> value. The
-default size unit is megabytes (MB). The <tt><partition_size></tt> is required for creating
-a new partition.</p><p>For the <tt>partition_size</tt> tag, you can use the special value, <tt>max_size</tt>,
-for extended partitions and for logical partitions.</p>
-<ul><li><p>When applied to extended or primary partitions, the <tt>max_size</tt> value uses the largest region of free space on the disk to create the extended or primary partition.</p></li>
-<li><p>For a logical partition in an extended partition, the <tt>max_size</tt> value uses the largest block of free space in the extended partition for the logical partition.</p></li></ul>
-</td>
-</tr>
-<tr><td align="left" valign="top" scope="row"></td>
-<td align="left" valign="top" scope="row"><p><tt><partition_type></tt></p></td>
-<td align="left" valign="top" scope="row"><p><tt><partition_type></tt> denotes the type of the partition to
-be created or deleted. If <tt><partition_type></tt> is specified in the <tt>delete</tt> action
-without any other partition elements, the automated installer deletes all the partitions of
-that type. The automated installer recognizes the values DOSEXT, SOLARIS, DOS16, DOSEXTLBA, and
-FAT32.</p></td>
-</tr>
-<tr><td align="left" valign="top" scope="row"></td>
-<td align="left" valign="top" scope="row"><p><tt><partition_size_units></tt></p></td>
-<td align="left" valign="top" scope="row"><p><tt><partition_size_units></tt> defines the units for the partition size. The default size unit is
-megabytes (MB). The possible values for <tt><partition_size_units></tt> include the following:</p>
-<ul><li><p>sectors, secs, sec, s, SECTORS, SECS, SEC, or S</p></li>
-<li><p>MB, megabytes, megabyte, mb, m, MEGABYTES, MEGABYTE, M</p></li>
-<li><p>GB, gigabytes, gigabyte, gb, g, GIGABYTES, GIGABYTE, G</p></li>
-<li><p>TB, terabytes, terabyte, tb, t, TERABYTES, TERABYTE, T</p></li></ul>
-</td>
-</tr>
-<tr><td align="left" valign="top" scope="row"></td>
-<td align="left" valign="top" scope="row"><p><tt><partition_is_logical></tt></p></td>
-<td align="left" valign="top" scope="row"><p>Use this tag to
-create a new logical partition in an extended partition. Valid values are true
-or false. See <a href="customai.html#extpart">Creating an Extended Partition (x86 Clients Only)</a>.</p></td>
-</tr>
-<tr><td align="left" valign="top" scope="row"><p><tt><ai_device_vtoc_slices></tt></p></td>
-<td align="left" valign="top" scope="row"></td>
-<td align="left" valign="top" scope="row"><p><tt><ai_device_vtoc_slices></tt> 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.</p></td>
-</tr>
-<tr><td align="left" valign="top" scope="row"></td>
-<td align="left" valign="top" scope="row"><p><tt><slice_action></tt></p></td>
-<td align="left" valign="top" scope="row"><p><tt><slice_action></tt> denotes the type of slice-related operation to be performed
-during installation. The allowed actions are <tt>create</tt>, <tt>delete</tt>, and <tt>preserve</tt>.</p></td>
-</tr>
-<tr><td align="left" valign="top" scope="row"></td>
-<td align="left" valign="top" scope="row"><p><tt><slice_number></tt></p></td>
-<td align="left" valign="top" scope="row"><p><tt><slice_number></tt> denotes the
-unique slice identification in the VTOC table. When this element is combined with
-the <tt><slice_action></tt> set to <tt>delete</tt>, then the automatic installer deletes the slice with
-the specified <tt><slice_number></tt>. If the <tt><slice_action></tt> is <tt>create</tt>, then a new slice is
-created with the specified <tt><slice_number></tt>. If the <tt><slice_action></tt> is <tt>preserve</tt>, then the
-specified slice is not touched during installation.</p></td>
-</tr>
-<tr><td align="left" valign="top" scope="row"></td>
-<td align="left" valign="top" scope="row"><p><tt><slice_size></tt></p></td>
-<td align="left" valign="top" scope="row"><p><tt><slice_size></tt> denotes the size of the slice
-to be created or deleted or preserved. The value of <tt><slice_size></tt> is interpreted
-based on the <tt><slice_size_units></tt> value. The default size unit is megabytes (MB). The
-<tt><slice_size></tt> is required for creating a new partition. You can use the
-special value, <tt>max_size</tt>, to indicate that you want the automated installer to use
-the largest free region and to create the slice with the maximum
-possible space.</p></td>
-</tr>
-<tr><td align="left" valign="top" scope="row"></td>
-<td align="left" valign="top" scope="row"><p><tt><slice_size_units></tt></p></td>
-<td align="left" valign="top" scope="row"><p><tt><slice_size_units></tt> defines the units for the slice size. The default size unit is
-megabytes (MB). The possible values for <tt><slice_size_units></tt> include the following:</p>
-<ul><li><p>sectors, secs, sec, s, SECTORS, SECS, SEC, or S</p></li>
-<li><p>MB, megabytes, megabyte, mb, m, MEGABYTES, MEGABYTE, M</p></li>
-<li><p>GB, gigabytes, gigabyte, gb, g, GIGABYTES, GIGABYTE, G</p></li>
-<li><p>TB, terabytes, terabyte, tb, t, TERABYTES, TERABYTE, T</p></li></ul>
-</td>
-</tr>
-<tr><td align="left" valign="top" scope="row"><p><tt><ai_pkg_repo_</tt><tt>default_publisher></tt></p></td>
-<td align="left" valign="top" scope="row"></td>
-<td align="left" valign="top" scope="row"><p><tt><ai_pkg_repo_default_publisher></tt> defines the
-IPS repository from which OpenSolaris installation should be performed. This element is optional. The
-default value is <tt>pkg.opensolaris.org</tt> with a publisher value of <tt>opensolaris.org</tt>.</p></td>
-</tr>
-<tr><td align="left" valign="top" scope="row"></td>
-<td align="left" valign="top" scope="row"><p><tt><main></tt></p></td>
-<td align="left" valign="top" scope="row"><p><tt><main></tt> defines the primary
-IPS repository to be used. <tt><main></tt> consists of two attributes, <tt>publisher</tt> and <tt>url</tt>.
-The <tt>publisher</tt> is the publisher name for the IPS repository. The <tt>url</tt> attribute
-points to the location of the IPS repository.</p></td>
-</tr>
-<tr><td align="left" valign="top" scope="row"></td>
-<td align="left" valign="top" scope="row"><p><tt><mirror></tt></p></td>
-<td align="left" valign="top" scope="row"><p><tt><mirror></tt> defines the location of an
-IPS repository whose contents are identical to the <tt><main></tt> element and uses the same
-<tt>publisher</tt>. The mirror element consists of one attribute, <tt>url</tt>, that points to the
-location of the IPS repository. This element is optional. There can be more
-than one mirror. IPS mirrors are repositories which can serve as a secondary
-cache for data, helping to speed IPS data transfers.</p></td>
-</tr>
-<tr><td align="left" valign="top" scope="row"><p><tt><ai_pkg_repo_</tt><tt>addl_publisher></tt></p></td>
-<td align="left" valign="top" scope="row"></td>
-<td align="left" valign="top" scope="row"><p><tt><ai_pkg_repo_addl_publisher></tt> 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.</p></td>
-</tr>
-<tr><td align="left" valign="top" scope="row"></td>
-<td align="left" valign="top" scope="row"><p><tt><main></tt></p></td>
-<td align="left" valign="top" scope="row"><p><tt><main></tt>
-defines the primary IPS repository to be used. <tt><main></tt> consists of two attributes,
-<tt>publisher</tt> and <tt>url</tt>. The <tt>publisher</tt> is the publisher name for the IPS repository.
-The <tt>url</tt> attribute points to the location of the IPS repository.</p></td>
-</tr>
-<tr><td align="left" valign="top" scope="row"></td>
-<td align="left" valign="top" scope="row"><p><tt><mirror></tt></p></td>
-<td align="left" valign="top" scope="row"><p><tt><mirror></tt> defines the
-location of a backup IPS repository whose contents are identical to the <tt><main></tt>
-element and uses the same <tt>publisher</tt>. The mirror element consists of one attribute,
-<tt>url</tt>, that points to the location of the IPS repository. This element is
-optional. There can be more than one mirror.</p></td>
-</tr>
-<tr><td align="left" valign="top" scope="row"><p><tt><ai_install_packages></tt></p></td>
-<td align="left" valign="top" scope="row"><p><tt><pkg name></tt></p></td>
-<td align="left" valign="top" scope="row"><p><tt><ai_install_packages></tt> defines the list of packages to
-be installed by automated installer during installation. <tt><ai_install_packages></tt> is mandatory. At least
-one package must be defined in this element. The tag consists of a
-single element called <tt>pkg</tt>. This element, <tt>pkg</tt>, has an attribute called <tt>name</tt>.
-The <tt>name</tt> attribute could be a simple package name, such as <tt>SUNWcs</tt>,
-or an incorporation, such as <tt>entire</tt>, or an FMRI, such as <tt>[email protected],5.11-0.101:20081119T213939Z</tt>. The
-default packages build an OpenSolaris operating system, and include packages that are required
-if you plan to use an iSCSI installation target.</p></td>
-</tr>
-<tr><td align="left" valign="top" scope="row"><p><tt><ai_uninstall_packages></tt></p></td>
-<td align="left" valign="top" scope="row"><p><tt><pkg name></tt></p></td>
-<td align="left" valign="top" scope="row"><p><tt><ai_uninstall_packages></tt> defines the list
-of packages to be removed by automated installer during installation. <tt><ai_uninstall_packages></tt> is an
-optional element. The definition of <tt><ai_uninstall_packages></tt> is similar to that of <tt><ai_install_packages></tt>.
-This tag consists of a single element called <tt>pkg</tt>. The element, <tt>pkg</tt>, has
-an attribute called <tt>name</tt>. The <tt>name</tt> attribute could be a simple package
-name, such as <tt>SUNWcs</tt>, or an incorporation, such as <tt>entire</tt>, or an FMRI,
-such as <tt>[email protected],5.11-0.101:20081119T213939Z</tt>.</p></td>
-</tr>
-<tr><td align="left" valign="top" scope="row"><p><tt><ai_http_proxy></tt></p></td>
-<td align="left" valign="top" scope="row"></td>
-<td align="left" valign="top" scope="row"><p>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. This tag can
-also be used when the AI client does not have a direct connection
-to the IPS repository server, and needs the proxy to get outside its
-network.</p><p>The element <tt><ai_http_proxy></tt> can be used to set up HTTP proxy that can
-be used for automated installations. <tt><ai_http_proxy></tt> consists of an attribute, <tt>url</tt>, that
-points to the HTTP proxy location. This element is optional.</p></td>
-</tr>
-<tr><td align="left" valign="top" scope="row"><p><tt><ai_auto_reboot></tt></p></td>
-<td align="left" valign="top" scope="row"></td>
-<td align="left" valign="top" scope="row"><p>By default, the automated
-installer does not 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, <tt><ai_auto_reboot></tt> can be set to <tt>true</tt>. The
-possible values of <tt><ai_auto_reboot></tt> are <tt>true</tt> and <tt>false</tt>.</p></td>
-</tr>
-</table>
-
-<a name="aimanfull"></a><h4>AI Manifest Complete File</h4>
-<p>The following is a complete AI manifest file with comments.</p><pre> 1 <!--
- 2 CDDL HEADER START
- 3
- 4 The contents of this file are subject to the terms of the
- 5 Common Development and Distribution License (the "License").
- 6 You may not use this file except in compliance with the License.
- 7
- 8 You can obtain a copy of the license at usr/src/OPENSOLARIS.LICENSE
- 9 or http://www.opensolaris.org/os/licensing.
- 10 See the License for the specific language governing permissions
- 11 and limitations under the License.
- 12
- 13 When distributing Covered Code, include this CDDL HEADER in each
- 14 file and include the License file at usr/src/OPENSOLARIS.LICENSE.
- 15 If applicable, add the following below this CDDL HEADER, with the
- 16 fields enclosed by brackets "[]" replaced with your own identifying
- 17 information: Portions Copyright [yyyy] [name of copyright owner]
- 18
- 19 CDDL HEADER END
- 20
- 21 ...
- 22 ...
- 23 -->
- 24
- 25 <!--
- 26 ===============================================================================
- 27 RelaxNG sample manifest for Automatic Installer input manifest specification.
- 28 ===============================================================================
- 29 -->
- 30 <ai_manifest name="sample_ai_manifest">
- 31 <!--
- 32 =======================================================================
- 33 <ai_target_device> - selections for AI target Device specification
- 34
- 35 Disk criteria are divided into two mutually exclusive groups:
- 36
- 37 G1 - deterministic disk criteria
- 38 ................................
- 39 * iscsi_target_parameters
- 40 * target_device_name (c#t#d# name or 'boot_disk')
- 41 * target_device_select_volume_name
- 42 * target_device_select_id
- 43 * target_device_select_device_path
- 44
- 45 G2 - rest of disk criteria
- 46 ..........................
- 47 * target_device_type
- 48 * target_device_vendor
- 49 * target_device_size
- 50
- 51 Schema ai_manifest.rng enforces following policy:
- 52
- 53 * criteria in group G1 are mutually exclusive - only
- 54 one can be specified at a time
- 55
- 56 * groups G1 and G2 are mutually exclusive - i.e.
- 57 if criteria from G1 is specified, no criteria
- 58 from G2 are allowed and vice versa
- 59
- 60 * multiple criteria from G2 can be specified
- 61 =======================================================================
- 62 -->
- 63 <ai_target_device>
- 64 <!-- G1 -->
- 65 <!--
- 66 c#t#d# device name like c0t0d0 or
- 67 MPXIO name like c0t2000002037CD9F72d0
- 68 or 'boot_disk' keyword to select boot disk
- 69 -->
- 70 <target_device_name>
- 71 boot_disk
- 72 </target_device_name>
- 73
- 74 <!-- volume name set for instance by means
- 75 of format(1M) command
- 76 -->
- 77 <!--
- 78 <target_device_select_volume_name>
- 79 ai-disk
- 80 </target_device_select_volume_name>
- 81 -->
- 82
- 83 <!-- device id - e.g. can be obtained by means of
- 84 iostat(1M) -iEn
- 85 -->
- 86 <!--
- 87 <target_device_select_id>
- 88 id1,cmdk@AST31000340NS=____________9QJ2LNYY
- 89 </target_device_select_id>
- 90 -->
- 91
- 92 <!-- device path under /devices directory, e.g.
- 93 /pci@1e,600000/pci@0/pci@9/pci@0/scsi@1/sd@0,0
- 94 -->
- 95 <!--
- 96 <target_device_select_device_path>
- 97 /pci@0/pci@9/pci@0/scsi@1/sd@0,0
- 98 </target_device_select_device_path>
- 99 -->
- 100
- 101 <!-- G2 -->
- 102 <!--
- 103 <target_device_type>SCSI</target_device_type>
- 104 <target_device_vendor>hitachi</target_device_vendor>
- 105 <target_device_size>20480</target_device_size>
- 106 -->
- 107
- 108 <!--
- 109 Uncomment this to force AI to find an existing Solaris
- 110 partition instead of creating a new one.
- 111 -->
- 112 <!--
- 113 <target_device_use_solaris_partition>true</target_device_use_solaris_partition>
- 114 -->
- 115
- 116 <target_device_install_slice_number>0</target_device_install_slice_number>
- 117 </ai_target_device>
- 118 <ai_device_partitioning>
- 119 <partition_action>create</partition_action>
- 120 <partition_number>1</partition_number>
- 121 <partition_start_sector>200</partition_start_sector>
- 122 <partition_size>20480</partition_size>
- 123 <partition_type>99</partition_type>
- 124 </ai_device_partitioning>
- 125 <ai_device_partitioning>
- 126 <partition_action>create</partition_action>
- 127 <partition_number>4</partition_number>
- 128 <partition_start_sector>200</partition_start_sector>
- 129 <partition_size>20480</partition_size>
- 130 <partition_size_units>mb</partition_size_units>
- 131 <partition_type>99</partition_type>
- 132 </ai_device_partitioning>
- 133 <ai_device_vtoc_slices>
- 134 <slice_action>create</slice_action>
- 135 <slice_number>4</slice_number>
- 136 <slice_size>20480</slice_size>
- 137 <slice_size_units>mb</slice_size_units>
- 138 </ai_device_vtoc_slices>
- 139 <ai_device_vtoc_slices>
- 140 <slice_action>delete</slice_action>
- 141 <slice_number>4</slice_number>
- 142 <slice_size>20480</slice_size>
- 143 </ai_device_vtoc_slices>
- 144 <ai_pkg_repo_default_publisher>
- 145 <main url="http://pkg.opensolaris.org/release" publisher="opensolaris.org"/>
- 146 <mirror url=""/>
- 147 </ai_pkg_repo_default_publisher>
- 148 <ai_pkg_repo_addl_publisher>
- 149 <main url="http://pkg.opensolaris.org/contrib" publisher="contrib.opensolaris.org"/>
- 150 <mirror url=""/>
- 151 </ai_pkg_repo_addl_publisher>
- 152
- 153 <!--
- 154 By default the latest build available, in the
- 155 specified IPS repository, is installed.
- 156 If another build is required, the build number has
- 157 to be appended to the 'entire' package in following
- 158 form:
- 159
- 160 <pkg_name="[email protected]#/">
- 161 -->
- 162 <ai_install_packages>
- 163 <pkg name="entire"/>
- 164 <pkg name="SUNWcsd"/>
- 165 <pkg name="SUNWcs"/>
- 166 <pkg name="babel_install"/>
- 167 </ai_install_packages>
- 168 <ai_uninstall_packages>
- 169 <pkg name="babel_install"/>
- 170 <pkg name="slim_install"/>
- 171 </ai_uninstall_packages>
- 172 <ai_auto_reboot>
- 173 false
- 174 </ai_auto_reboot>
- 175 </ai_manifest>
- 176 </pre>
-
-<a name="defaultcri"></a><h4>Default Manifest File, <tt>default.xml</tt></h4>
-<p>A criteria manifest file is the bridge that connects the AI manifest file
-and the SC manifest file with a client. In most cases, the
-criteria manifest contains only the path to an AI manifest and the path
-to an SC manifest, instead of including their complete contents.</p>
-<hr><p><b>Note - </b>For information about how to create and use custom criteria manifests, see <a href="criteria.html">How to Create and Use a Criteria Manifest</a>.</p>
-<hr>
-<p>However, the default manifest that is included in the AI images, <tt>default.xml</tt>,
-functions as a criteria manifest that contains the full contents for an AI
-manifest and an SC manifest. When you review the default manifest contents below,
-you can see that the file contains a <b>criteria manifest</b>, named <tt><ai_criteria_manifest></tt>. This criteria
-manifest encompasses the following two subsections:</p>
-<ul><li><p>An <b>AI manifest</b>, named <tt><ai_embedded_manifest></tt>, that specifies installation specifications.</p></li>
-<li><p>An <b>SC manifest</b>, named <tt><sc_embedded_manifest name = "AI"></tt>, that contains information for configuring the client after the installation is complete.</p></li></ul>
-<p>The contents of the default criteria manifest, <tt>default.xml</tt>, are as follows:</p><pre><ai_criteria_manifest>
- <ai_embedded_manifest>
- <ai_manifest name="default">
- <ai_pkg_repo_default_publisher>
- <main url="http://pkg.opensolaris.org/release" publisher=
-"opensolaris.org"/>
- <mirror url=""/>
- </ai_pkg_repo_default_publisher>
- <ai_pkg_repo_addl_publisher>
- <main url="http://pkg.opensolaris.org/contrib" publisher=
-"contrib.opensolaris.org"/>
- <mirror url=""/>
- </ai_pkg_repo_addl_publisher>
-
- <!--
- By default the latest build available, in the specified IPS
- repository, is installed.
- If another build is required, the build number has
- to be appended to the 'entire' package in following
- form:
-
- <pkg name="[email protected]#"/>
- -->
- <ai_install_packages>
- <!--
- Due to dependency issues, entire must be listed first
- in the package list, followed by SUNWcsd, and then SUNWcs.
- Any additional packages must be listed after SUNWcs.
- -->
- <pkg name="entire"/>
- <pkg name="SUNWcsd"/>
- <pkg name="SUNWcs"/>
- <pkg name="babel_install"/>
- <!--
- The following two packages are required by iSCSI,
- and can be deleted from this list if iSCSI is not used
- See iscsiadm(1m) man page for more information
- -->
- <pkg name="SUNWiscsi"/>
- <pkg name="SUNWiscsidm"/>
- </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"/>
- </property_group>
- </instance>
- </service>
- </service_bundle>
- -->
- </sc_embedded_manifest>
-</ai_criteria_manifest></pre>
- </div>
- </td>
- </tr>
-
- <tr class="PageControls" valign="top">
- <td></td>
- <td>
- <table width="100%">
- <tr>
- <td>
- <a href="appendix.html">Previous</a>
- </td>
- <td align="right">
- <a href="installadm.html">Next</a>
- </td>
- </tr>
- </table>
- </td>
- </tr>
-</tbody>
-</table>
-
-
-</body>
-</html>
-
--- a/usr/src/cmd/installadm/docs/appendix.html Wed Sep 29 16:37:00 2010 +0200
+++ /dev/null Thu Jan 01 00:00:00 1970 +0000
@@ -1,99 +0,0 @@
-<!DOCTYPE HTML PUBLIC "-//W3C//DTD HTML 4.01 Transitional//EN" "http://www.w3.org/TR/html4/loose.dtd">
-<html lang="en-US">
-
-<!-- -->
-<head>
-<!-- GenHTML revision 23436-->
-<meta http-equiv="Content-type" content="text/html; charset=iso-8859-1">
-<title>Appendix - OpenSolaris 2010.03 Automated Installer Guide</title>
-<meta name="robots" content="index,follow">
-<meta name="robots" content="index,follow">
-<meta name="date" content="2010-03-01">
-<meta name="collection" content="reference">
-<link rel="stylesheet" type="text/css" href="css/elements.css">
-<link rel="stylesheet" type="text/css" href="css/opensol.css">
-</head>
-
-<body>
-
-
-<div class="Masthead">
- <div class="MastheadLogo">
- <a href="http://www.opensolaris.com"><img border="0" src="graphics/opensolaris_logo_trans.png"></img></a>
- </div>
- <div class="Title">OpenSolaris 2010.03 Automated Installer Guide</div>
-</div>
-<div class="headerbar"></div>
-
-
-<table class="Layout" border="0" cellspacing="0" width="100%">
-<tbody>
-
- <tr valign="top" class="PageControls">
- <td></td>
- <td>
- <table width="100%">
- <tr>
- <td>
- <a href="help.html">Previous</a>
- </td>
- <td align="right">
- <a href="aimanifest.html">Next</a>
- </td>
- </tr>
- </table>
- </td>
- </tr>
-
- <tr valign="top">
- <td class="Navigation" width="200px"><p class="toc level1"><a href="docinfo.html">Document Information</a></p>
-<p class="toc level1 tocsp"><a href="index.html">1. What's New For Automated Installations</a></p>
-<p class="toc level1 tocsp"><a href="intro.html">2. Introduction to the Automated Installer</a></p>
-<p class="toc level1 tocsp"><a href="tasks.html">3. Automated Network Install Task Map</a></p>
-<p class="toc level1 tocsp"><a href="bootable.html">4. Automated Installations That Boot From Media</a></p>
-<p class="toc level1 tocsp"><a href="setup.html">5. Set up an Automated Install Server</a></p>
-<p class="toc level1 tocsp"><a href="administer.html">6. How to Administer an Automated Install Server</a></p>
-<p class="toc level1 tocsp"><a href="client.html">7. How to Administer a Custom Install Client</a></p>
-<p class="toc level1 tocsp"><a href="manifest.html">8. How to Administer Manifest Files</a></p>
-<p class="toc level1 tocsp"><a href="clients.html">9. How to Manage Client Installations</a></p>
-<p class="toc level1 tocsp"><a href="trouble.html">10. Troubleshooting and FAQs for the Automated Installer</a></p>
-<div id="scrolltoc" class="onpage">
-<p class="toc level1 tocsp"><a href="">11. Appendix</a></p>
-</div>
-<p class="toc level2"><a href="aimanifest.html">AI Manifest Contents</a></p>
-<p class="toc level2"><a href="installadm.html"><tt>installadm(1M)</tt> Man Page</a></p>
-</td>
- <td class="ContentPane" width="705px">
-
- <div class="MainContent">
- <a name="appendix"></a>Chapter 11<h3>Appendix</h3><p>Review the following automated installation information as needed:</p>
-<ul><li><p><a href="aimanifest.html">AI Manifest Contents</a></p></li>
-<li><p><a href="aimanifest.html#defaultcri">Default Manifest File, <tt>default.xml</tt></a></p></li>
-<li><p><a href="installadm.html"><tt>installadm(1M)</tt> Man Page</a></p></li></ul>
-
- </div>
- </td>
- </tr>
-
- <tr class="PageControls" valign="top">
- <td></td>
- <td>
- <table width="100%">
- <tr>
- <td>
- <a href="help.html">Previous</a>
- </td>
- <td align="right">
- <a href="aimanifest.html">Next</a>
- </td>
- </tr>
- </table>
- </td>
- </tr>
-</tbody>
-</table>
-
-
-</body>
-</html>
-
--- a/usr/src/cmd/installadm/docs/associate.html Wed Sep 29 16:37:00 2010 +0200
+++ /dev/null Thu Jan 01 00:00:00 1970 +0000
@@ -1,127 +0,0 @@
-<!DOCTYPE HTML PUBLIC "-//W3C//DTD HTML 4.01 Transitional//EN" "http://www.w3.org/TR/html4/loose.dtd">
-<html lang="en-US">
-
-<!-- -->
-<head>
-<!-- GenHTML revision 23436-->
-<meta http-equiv="Content-type" content="text/html; charset=iso-8859-1">
-<title>How to Assign Manifests to a Client - OpenSolaris 2010.03 Automated Installer Guide</title>
-<meta name="robots" content="index,follow">
-<meta name="robots" content="index,follow">
-<meta name="date" content="2010-03-01">
-<meta name="collection" content="reference">
-<link rel="stylesheet" type="text/css" href="css/elements.css">
-<link rel="stylesheet" type="text/css" href="css/opensol.css">
-</head>
-
-<body>
-
-
-<div class="Masthead">
- <div class="MastheadLogo">
- <a href="http://www.opensolaris.com"><img border="0" src="graphics/opensolaris_logo_trans.png"></img></a>
- </div>
- <div class="Title">OpenSolaris 2010.03 Automated Installer Guide</div>
-</div>
-<div class="headerbar"></div>
-
-
-<table class="Layout" border="0" cellspacing="0" width="100%">
-<tbody>
-
- <tr valign="top" class="PageControls">
- <td></td>
- <td>
- <table width="100%">
- <tr>
- <td>
- <a href="criteria.html">Previous</a>
- </td>
- <td align="right">
- <a href="clients.html">Next</a>
- </td>
- </tr>
- </table>
- </td>
- </tr>
-
- <tr valign="top">
- <td class="Navigation" width="200px"><p class="toc level1"><a href="docinfo.html">Document Information</a></p>
-<p class="toc level1 tocsp"><a href="index.html">1. What's New For Automated Installations</a></p>
-<p class="toc level1 tocsp"><a href="intro.html">2. Introduction to the Automated Installer</a></p>
-<p class="toc level1 tocsp"><a href="tasks.html">3. Automated Network Install Task Map</a></p>
-<p class="toc level1 tocsp"><a href="bootable.html">4. Automated Installations That Boot From Media</a></p>
-<p class="toc level1 tocsp"><a href="setup.html">5. Set up an Automated Install Server</a></p>
-<p class="toc level1 tocsp"><a href="administer.html">6. How to Administer an Automated Install Server</a></p>
-<p class="toc level1 tocsp"><a href="client.html">7. How to Administer a Custom Install Client</a></p>
-<p class="toc level1 tocsp"><a href="manifest.html">8. How to Administer Manifest Files</a></p>
-<p class="toc level2"><a href="manifest1.html">Types of Manifests</a></p>
-<p class="toc level2"><a href="customai.html">How to Create and Use a Custom AI Manifest</a></p>
-<p class="toc level2"><a href="customsc.html">How to Create Custom SC Manifest Files</a></p>
-<p class="toc level2"><a href="criteria.html">How to Create and Use a Criteria Manifest</a></p>
-<div id="scrolltoc" class="onpage">
-<p class="toc level2"><a href="">How to Assign Manifests to a Client</a></p>
-</div>
-<p class="toc level1 tocsp"><a href="clients.html">9. How to Manage Client Installations</a></p>
-<p class="toc level1 tocsp"><a href="trouble.html">10. Troubleshooting and FAQs for the Automated Installer</a></p>
-<p class="toc level1 tocsp"><a href="appendix.html">11. Appendix</a></p>
-</td>
- <td class="ContentPane" width="705px">
-
- <div class="MainContent">
-
-
-<a name="associate"></a><h3>How to Assign Manifests to a Client</h3>
-<p>Client installations can be customized by assigning different manifests to different clients' install
-services. The <tt>installadm add</tt> command assigns a specific manifest to a client. See
-the following example.</p>
-
-<a name="gentextid-2336"></a><h4>Assigning a Manifest to a Client</h4>
-
-<ol><li><p>Create a criteria manifest file, <tt>criteria_mac.xml</tt>, that connects a new AI manifest file, <tt>ai_manifest1.xml</tt>, to a client. See examples in <a href="criteria.html#criteriaie">Criteria Manifest Examples</a>.</p></li>
-<li><p>Check which install services are on your server by using by using the following command:</p><pre># <tt>installadm list</tt></pre><p>The install services running on the system are displayed, as in the following example</p><pre># installadm list
-
-Service Name Status Arch Port Image Path
------------- ------ ---- ---- ----------
-service_032509 on x86 45603 /export/images/svc1</pre><p>In this example, the install service, <tt>service_032509</tt>, is running on the system.</p></li>
-<li><p>Add the manifest files and the criteria defined by <tt>criteria_mac.xml</tt> to the install service, <tt>service_032509</tt>, by using the following command:</p><pre># <tt>installadm add <tt>-m</tt> <i>criteria_mac.xml</i> <tt>-n</tt> <i>service_032509</i></tt></pre></li>
-<li><p>Run the following command to check that the AI manifest file, <tt>ai_manifest1.xml</tt>, has been added to the install service.</p>
-<hr><p><b>Note - </b>Only the AI manifest name, from the XML <tt><ai_manifest></tt> 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</p>
-<hr>
-<pre># <tt>installadm list <tt>-n</tt> <i>service_032509</i></tt></pre><p>The following example shows that the manifest, <tt>ai_manifest1.xml</tt>, is assigned to the install service, <tt>service_032509</tt>.</p><pre># installadm -m -n service_032509
-
- Manifest Criteria
- -------- --------
- ai_manifest1.xml arch = i86pc</pre></li></ol>
-
-
-<a name="remove"></a><h4>How to Remove an AI Manifest File From an Install Service</h4>
-<p>If you want to remove an AI manifest file from an install
-service, use the following command.</p><pre># <tt>installadm remove <tt>-m</tt> <i>manifestname</i> <tt>-n</tt> <i>servicename</i></tt></pre><p>For example, to remove a manifest named <tt>ai_manifest1</tt> from the install service,
-<tt>service_032509</tt>, use the following command:</p><pre># <tt>installadm remove <tt>-m</tt> <i>ai_manifest1</i> <tt>-n</tt> <i>service_032509</i></tt></pre>
- </div>
- </td>
- </tr>
-
- <tr class="PageControls" valign="top">
- <td></td>
- <td>
- <table width="100%">
- <tr>
- <td>
- <a href="criteria.html">Previous</a>
- </td>
- <td align="right">
- <a href="clients.html">Next</a>
- </td>
- </tr>
- </table>
- </td>
- </tr>
-</tbody>
-</table>
-
-
-</body>
-</html>
-
--- a/usr/src/cmd/installadm/docs/autoinstall.html Wed Sep 29 16:37:00 2010 +0200
+++ /dev/null Thu Jan 01 00:00:00 1970 +0000
@@ -1,92 +0,0 @@
-<!DOCTYPE HTML PUBLIC "-//W3C//DTD HTML 4.01 Transitional//EN" "http://www.w3.org/TR/html4/loose.dtd">
-<html lang="en-US">
-
-<!-- -->
-<head>
-<!-- GenHTML revision 23436-->
-<meta http-equiv="Content-type" content="text/html; charset=iso-8859-1">
-<title>OpenSolaris 2010.03 Automated Installer Guide</title>
-<meta name="robots" content="index,follow">
-<meta name="robots" content="index,follow">
-<meta name="date" content="2010-03-01">
-<meta name="collection" content="reference">
-<link rel="stylesheet" type="text/css" href="css/elements.css">
-<link rel="stylesheet" type="text/css" href="css/opensol.css">
-</head>
-
-<body>
-
-
-<div class="Masthead">
- <div class="MastheadLogo">
- <a href="http://www.opensolaris.com"><img border="0" src="graphics/opensolaris_logo_trans.png"></img></a>
- </div>
- <div class="Title">OpenSolaris 2010.03 Automated Installer Guide</div>
-</div>
-<div class="headerbar"></div>
-
-
-<table class="Layout" border="0" cellspacing="0" width="100%">
-<tbody>
-
- <tr valign="top" class="PageControls">
- <td></td>
- <td>
- <table width="100%">
- <tr>
- <td>
-
- </td>
- <td align="right">
- <a href="docinfo.html">Next</a>
- </td>
- </tr>
- </table>
- </td>
- </tr>
-
- <tr valign="top">
- <td class="Navigation" width="200px"><p class="toc level1"><a href="docinfo.html">Document Information</a></p>
-<p class="toc level1 tocsp"><a href="index.html">1. What's New For Automated Installations</a></p>
-<p class="toc level1 tocsp"><a href="intro.html">2. Introduction to the Automated Installer</a></p>
-<p class="toc level1 tocsp"><a href="tasks.html">3. Automated Network Install Task Map</a></p>
-<p class="toc level1 tocsp"><a href="bootable.html">4. Automated Installations That Boot From Media</a></p>
-<p class="toc level1 tocsp"><a href="setup.html">5. Set up an Automated Install Server</a></p>
-<p class="toc level1 tocsp"><a href="administer.html">6. How to Administer an Automated Install Server</a></p>
-<p class="toc level1 tocsp"><a href="client.html">7. How to Administer a Custom Install Client</a></p>
-<p class="toc level1 tocsp"><a href="manifest.html">8. How to Administer Manifest Files</a></p>
-<p class="toc level1 tocsp"><a href="clients.html">9. How to Manage Client Installations</a></p>
-<p class="toc level1 tocsp"><a href="trouble.html">10. Troubleshooting and FAQs for the Automated Installer</a></p>
-<p class="toc level1 tocsp"><a href="appendix.html">11. Appendix</a></p>
-</td>
- <td class="ContentPane" width="705px">
-
- <div class="MainContent">
- <h1>OpenSolaris 2010.03 Automated Installer Guide</h1>
-
- </div>
- </td>
- </tr>
-
- <tr class="PageControls" valign="top">
- <td></td>
- <td>
- <table width="100%">
- <tr>
- <td>
-
- </td>
- <td align="right">
- <a href="docinfo.html">Next</a>
- </td>
- </tr>
- </table>
- </td>
- </tr>
-</tbody>
-</table>
-
-
-</body>
-</html>
-
--- a/usr/src/cmd/installadm/docs/basic.html Wed Sep 29 16:37:00 2010 +0200
+++ /dev/null Thu Jan 01 00:00:00 1970 +0000
@@ -1,127 +0,0 @@
-<!DOCTYPE HTML PUBLIC "-//W3C//DTD HTML 4.01 Transitional//EN" "http://www.w3.org/TR/html4/loose.dtd">
-<html lang="en-US">
-
-<!-- -->
-<head>
-<!-- GenHTML revision 23436-->
-<meta http-equiv="Content-type" content="text/html; charset=iso-8859-1">
-<title>Server Setup - OpenSolaris 2010.03 Automated Installer Guide</title>
-<meta name="robots" content="index,follow">
-<meta name="robots" content="index,follow">
-<meta name="date" content="2010-03-01">
-<meta name="collection" content="reference">
-<link rel="stylesheet" type="text/css" href="css/elements.css">
-<link rel="stylesheet" type="text/css" href="css/opensol.css">
-</head>
-
-<body>
-
-
-<div class="Masthead">
- <div class="MastheadLogo">
- <a href="http://www.opensolaris.com"><img border="0" src="graphics/opensolaris_logo_trans.png"></img></a>
- </div>
- <div class="Title">OpenSolaris 2010.03 Automated Installer Guide</div>
-</div>
-<div class="headerbar"></div>
-
-
-<table class="Layout" border="0" cellspacing="0" width="100%">
-<tbody>
-
- <tr valign="top" class="PageControls">
- <td></td>
- <td>
- <table width="100%">
- <tr>
- <td>
- <a href="setup.html">Previous</a>
- </td>
- <td align="right">
- <a href="initial.html">Next</a>
- </td>
- </tr>
- </table>
- </td>
- </tr>
-
- <tr valign="top">
- <td class="Navigation" width="200px"><p class="toc level1"><a href="docinfo.html">Document Information</a></p>
-<p class="toc level1 tocsp"><a href="index.html">1. What's New For Automated Installations</a></p>
-<p class="toc level1 tocsp"><a href="intro.html">2. Introduction to the Automated Installer</a></p>
-<p class="toc level1 tocsp"><a href="tasks.html">3. Automated Network Install Task Map</a></p>
-<p class="toc level1 tocsp"><a href="bootable.html">4. Automated Installations That Boot From Media</a></p>
-<p class="toc level1 tocsp"><a href="setup.html">5. Set up an Automated Install Server</a></p>
-<div id="scrolltoc" class="onpage">
-<p class="toc level2"><a href="">Server Setup</a></p>
-</div>
-<p class="toc level2"><a href="initial.html">How to Set Up an Install Server (Initial Steps)</a></p>
-<p class="toc level2"><a href="simple.html">How to Complete Server Setup (Simple Instructions)</a></p>
-<p class="toc level2"><a href="advancedsetup.html">How to Complete Server Setup (Advanced Instructions)</a></p>
-<p class="toc level1 tocsp"><a href="administer.html">6. How to Administer an Automated Install Server</a></p>
-<p class="toc level1 tocsp"><a href="client.html">7. How to Administer a Custom Install Client</a></p>
-<p class="toc level1 tocsp"><a href="manifest.html">8. How to Administer Manifest Files</a></p>
-<p class="toc level1 tocsp"><a href="clients.html">9. How to Manage Client Installations</a></p>
-<p class="toc level1 tocsp"><a href="trouble.html">10. Troubleshooting and FAQs for the Automated Installer</a></p>
-<p class="toc level1 tocsp"><a href="appendix.html">11. Appendix</a></p>
-</td>
- <td class="ContentPane" width="705px">
-
- <div class="MainContent">
-
-
-<a name="basic"></a><h3>Server Setup</h3>
-<p>Use the following instructions to set up a system as an install
-server. Note the following:</p>
-<hr><p><b>Note - </b>Any system that meets these setup requirements can be used as an automated
-install server, including laptops, desktops, virtual machines, and enterprise servers.</p>
-<hr>
-
-<ul><li><p>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.</p>
-<hr><p><b>Note - </b>You can use the ISC DHCP server instead of the Solaris DHCP server. See <a href="faq.html#isc">17. How do I use ISC DHCP With the Automated Installer?</a>.</p>
-<hr>
-</li>
-<li><p>The install server must have a static IP address.</p></li>
-<li><p>The default router should be set on the install server.</p></li>
-<li><p>The OpenSolaris 2009.06 release, or a later release, must be installed on the install server.</p>
-<hr><p><b>Note - </b>If the OpenSolaris 2010.03 release is installed on your install server, you can use AI images for either the OpenSolaris 2009.06 release or for the OpenSolaris 2010.03 release. Otherwise, the OpenSolaris release installed on your server and the OpenSolaris release for the AI images that you plan to install to client systems must be the same release.</p>
-<hr>
-</li>
-<li><p> Available disk space as follows:</p>
-<ul><li><p>Minimum of 3.6 GB to install the OpenSolaris operating system</p>
-<hr><p><b>Note - </b>Recommended size is at least 10 GB.</p>
-<hr>
-</li>
-<li><p>Minimum of an additional 4 GB to install the server tools</p></li></ul>
-</li>
-<li><p>To set up a SPARC system as your install server, first create SPARC AI media, and then use that media to install the OpenSolaris release on that system. For instructions, see <a href="bootable.html">Chapter 4, Automated Installations That Boot From Media</a>.</p></li></ul>
-<p>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.</p>
- </div>
- </td>
- </tr>
-
- <tr class="PageControls" valign="top">
- <td></td>
- <td>
- <table width="100%">
- <tr>
- <td>
- <a href="setup.html">Previous</a>
- </td>
- <td align="right">
- <a href="initial.html">Next</a>
- </td>
- </tr>
- </table>
- </td>
- </tr>
-</tbody>
-</table>
-
-
-</body>
-</html>
-
--- a/usr/src/cmd/installadm/docs/benefits.html Wed Sep 29 16:37:00 2010 +0200
+++ /dev/null Thu Jan 01 00:00:00 1970 +0000
@@ -1,107 +0,0 @@
-<!DOCTYPE HTML PUBLIC "-//W3C//DTD HTML 4.01 Transitional//EN" "http://www.w3.org/TR/html4/loose.dtd">
-<html lang="en-US">
-
-<!-- -->
-<head>
-<!-- GenHTML revision 23436-->
-<meta http-equiv="Content-type" content="text/html; charset=iso-8859-1">
-<title>Automated Installation Benefits - OpenSolaris 2010.03 Automated Installer Guide</title>
-<meta name="robots" content="index,follow">
-<meta name="robots" content="index,follow">
-<meta name="date" content="2010-03-01">
-<meta name="collection" content="reference">
-<link rel="stylesheet" type="text/css" href="css/elements.css">
-<link rel="stylesheet" type="text/css" href="css/opensol.css">
-</head>
-
-<body>
-
-
-<div class="Masthead">
- <div class="MastheadLogo">
- <a href="http://www.opensolaris.com"><img border="0" src="graphics/opensolaris_logo_trans.png"></img></a>
- </div>
- <div class="Title">OpenSolaris 2010.03 Automated Installer Guide</div>
-</div>
-<div class="headerbar"></div>
-
-
-<table class="Layout" border="0" cellspacing="0" width="100%">
-<tbody>
-
- <tr valign="top" class="PageControls">
- <td></td>
- <td>
- <table width="100%">
- <tr>
- <td>
- <a href="clientinstall.html">Previous</a>
- </td>
- <td align="right">
- <a href="tasks.html">Next</a>
- </td>
- </tr>
- </table>
- </td>
- </tr>
-
- <tr valign="top">
- <td class="Navigation" width="200px"><p class="toc level1"><a href="docinfo.html">Document Information</a></p>
-<p class="toc level1 tocsp"><a href="index.html">1. What's New For Automated Installations</a></p>
-<p class="toc level1 tocsp"><a href="intro.html">2. Introduction to the Automated Installer</a></p>
-<p class="toc level2"><a href="whatis.html">What Is an Automated Installation?</a></p>
-<p class="toc level2"><a href="use.html">How Do I Use the Automated Installer?</a></p>
-<p class="toc level2"><a href="clientinstall.html">How a Client Is Installed</a></p>
-<div id="scrolltoc" class="onpage">
-<p class="toc level2"><a href="">Automated Installation Benefits</a></p>
-</div>
-<p class="toc level1 tocsp"><a href="tasks.html">3. Automated Network Install Task Map</a></p>
-<p class="toc level1 tocsp"><a href="bootable.html">4. Automated Installations That Boot From Media</a></p>
-<p class="toc level1 tocsp"><a href="setup.html">5. Set up an Automated Install Server</a></p>
-<p class="toc level1 tocsp"><a href="administer.html">6. How to Administer an Automated Install Server</a></p>
-<p class="toc level1 tocsp"><a href="client.html">7. How to Administer a Custom Install Client</a></p>
-<p class="toc level1 tocsp"><a href="manifest.html">8. How to Administer Manifest Files</a></p>
-<p class="toc level1 tocsp"><a href="clients.html">9. How to Manage Client Installations</a></p>
-<p class="toc level1 tocsp"><a href="trouble.html">10. Troubleshooting and FAQs for the Automated Installer</a></p>
-<p class="toc level1 tocsp"><a href="appendix.html">11. Appendix</a></p>
-</td>
- <td class="ContentPane" width="705px">
-
- <div class="MainContent">
-
-
-<a name="benefits"></a><h3>Automated Installation Benefits</h3>
-<p>The automated installer provides support for network installations using an install server, where
-one installation specification can be applied to multiple systems.</p><p>The automated installer includes the following features that support multiple-client installations in a
-network:</p>
-<ul><li><p>The automated installer uses mDNS, so that, when you boot a client, the specific named service needed for that client installation can be found. No individual client configuration is necessary for clients to access install services.</p></li>
-<li><p>Installation setup is decentralized. You can maintain multiple, disparate locations for install services and for client configuration. install 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.</p></li>
-<li><p>If all of your client systems have the same hardware characteristics, the default installation specifications that you set up by using the <tt>installadm create-service</tt> 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 <tt>installadm add</tt> command, you can add the custom manifest to an install service to make it available on the network for client installations.</p></li>
-<li><p>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 <a href="setup.html">Chapter 5, Set up an Automated Install Server</a>.</p></li></ul>
-
- </div>
- </td>
- </tr>
-
- <tr class="PageControls" valign="top">
- <td></td>
- <td>
- <table width="100%">
- <tr>
- <td>
- <a href="clientinstall.html">Previous</a>
- </td>
- <td align="right">
- <a href="tasks.html">Next</a>
- </td>
- </tr>
- </table>
- </td>
- </tr>
-</tbody>
-</table>
-
-
-</body>
-</html>
-
--- a/usr/src/cmd/installadm/docs/bootable.html Wed Sep 29 16:37:00 2010 +0200
+++ /dev/null Thu Jan 01 00:00:00 1970 +0000
@@ -1,104 +0,0 @@
-<!DOCTYPE HTML PUBLIC "-//W3C//DTD HTML 4.01 Transitional//EN" "http://www.w3.org/TR/html4/loose.dtd">
-<html lang="en-US">
-
-<!-- -->
-<head>
-<!-- GenHTML revision 23436-->
-<meta http-equiv="Content-type" content="text/html; charset=iso-8859-1">
-<title>Automated Installations That Boot From Media - OpenSolaris 2010.03 Automated Installer Guide</title>
-<meta name="robots" content="index,follow">
-<meta name="robots" content="index,follow">
-<meta name="date" content="2010-03-01">
-<meta name="collection" content="reference">
-<link rel="stylesheet" type="text/css" href="css/elements.css">
-<link rel="stylesheet" type="text/css" href="css/opensol.css">
-</head>
-
-<body>
-
-
-<div class="Masthead">
- <div class="MastheadLogo">
- <a href="http://www.opensolaris.com"><img border="0" src="graphics/opensolaris_logo_trans.png"></img></a>
- </div>
- <div class="Title">OpenSolaris 2010.03 Automated Installer Guide</div>
-</div>
-<div class="headerbar"></div>
-
-
-<table class="Layout" border="0" cellspacing="0" width="100%">
-<tbody>
-
- <tr valign="top" class="PageControls">
- <td></td>
- <td>
- <table width="100%">
- <tr>
- <td>
- <a href="tasks1.html">Previous</a>
- </td>
- <td align="right">
- <a href="whybootable.html">Next</a>
- </td>
- </tr>
- </table>
- </td>
- </tr>
-
- <tr valign="top">
- <td class="Navigation" width="200px"><p class="toc level1"><a href="docinfo.html">Document Information</a></p>
-<p class="toc level1 tocsp"><a href="index.html">1. What's New For Automated Installations</a></p>
-<p class="toc level1 tocsp"><a href="intro.html">2. Introduction to the Automated Installer</a></p>
-<p class="toc level1 tocsp"><a href="tasks.html">3. Automated Network Install Task Map</a></p>
-<div id="scrolltoc" class="onpage">
-<p class="toc level1 tocsp"><a href="">4. Automated Installations That Boot From Media</a></p>
-</div>
-<p class="toc level2"><a href="whybootable.html">Why Boot From AI Media?</a></p>
-<p class="toc level2"><a href="bootableclientreq.html">System Requirements for Automated Installations Using Media</a></p>
-<p class="toc level2"><a href="howbootable.html">How to Install Using Media</a></p>
-<p class="toc level1 tocsp"><a href="setup.html">5. Set up an Automated Install Server</a></p>
-<p class="toc level1 tocsp"><a href="administer.html">6. How to Administer an Automated Install Server</a></p>
-<p class="toc level1 tocsp"><a href="client.html">7. How to Administer a Custom Install Client</a></p>
-<p class="toc level1 tocsp"><a href="manifest.html">8. How to Administer Manifest Files</a></p>
-<p class="toc level1 tocsp"><a href="clients.html">9. How to Manage Client Installations</a></p>
-<p class="toc level1 tocsp"><a href="trouble.html">10. Troubleshooting and FAQs for the Automated Installer</a></p>
-<p class="toc level1 tocsp"><a href="appendix.html">11. Appendix</a></p>
-</td>
- <td class="ContentPane" width="705px">
-
- <div class="MainContent">
- <a name="bootable"></a>Chapter 4<h3>Automated Installations That Boot From Media</h3><p><b>Starting with the OpenSolaris 2010.03 release</b>, you can create an automated install (AI) CD, DVD, or, for
-x86 installations, a USB stick. Then, you can boot the AI media directly
-to initiate an automated installation. The system will still need network access, since
-the installation process retrieves packages from a network IPS repository. Booting the media directly
-is useful for cases where an AI server hasn't yet been set
-up on your network, or if you client system is unable to boot
-over the network to initiate a network AI install. You can install the
-client using either the default installation specifications provided in the AI media, or
-you can create and use a manifest with custom specifications.</p>
- </div>
- </td>
- </tr>
-
- <tr class="PageControls" valign="top">
- <td></td>
- <td>
- <table width="100%">
- <tr>
- <td>
- <a href="tasks1.html">Previous</a>
- </td>
- <td align="right">
- <a href="whybootable.html">Next</a>
- </td>
- </tr>
- </table>
- </td>
- </tr>
-</tbody>
-</table>
-
-
-</body>
-</html>
-
--- a/usr/src/cmd/installadm/docs/bootableclientreq.html Wed Sep 29 16:37:00 2010 +0200
+++ /dev/null Thu Jan 01 00:00:00 1970 +0000
@@ -1,122 +0,0 @@
-<!DOCTYPE HTML PUBLIC "-//W3C//DTD HTML 4.01 Transitional//EN" "http://www.w3.org/TR/html4/loose.dtd">
-<html lang="en-US">
-
-<!-- -->
-<head>
-<!-- GenHTML revision 23436-->
-<meta http-equiv="Content-type" content="text/html; charset=iso-8859-1">
-<title>System Requirements for Automated Installations Using Media - OpenSolaris 2010.03 Automated Installer Guide</title>
-<meta name="robots" content="index,follow">
-<meta name="robots" content="index,follow">
-<meta name="date" content="2010-03-01">
-<meta name="collection" content="reference">
-<link rel="stylesheet" type="text/css" href="css/elements.css">
-<link rel="stylesheet" type="text/css" href="css/opensol.css">
-</head>
-
-<body>
-
-
-<div class="Masthead">
- <div class="MastheadLogo">
- <a href="http://www.opensolaris.com"><img border="0" src="graphics/opensolaris_logo_trans.png"></img></a>
- </div>
- <div class="Title">OpenSolaris 2010.03 Automated Installer Guide</div>
-</div>
-<div class="headerbar"></div>
-
-
-<table class="Layout" border="0" cellspacing="0" width="100%">
-<tbody>
-
- <tr valign="top" class="PageControls">
- <td></td>
- <td>
- <table width="100%">
- <tr>
- <td>
- <a href="whybootable.html">Previous</a>
- </td>
- <td align="right">
- <a href="howbootable.html">Next</a>
- </td>
- </tr>
- </table>
- </td>
- </tr>
-
- <tr valign="top">
- <td class="Navigation" width="200px"><p class="toc level1"><a href="docinfo.html">Document Information</a></p>
-<p class="toc level1 tocsp"><a href="index.html">1. What's New For Automated Installations</a></p>
-<p class="toc level1 tocsp"><a href="intro.html">2. Introduction to the Automated Installer</a></p>
-<p class="toc level1 tocsp"><a href="tasks.html">3. Automated Network Install Task Map</a></p>
-<p class="toc level1 tocsp"><a href="bootable.html">4. Automated Installations That Boot From Media</a></p>
-<p class="toc level2"><a href="whybootable.html">Why Boot From AI Media?</a></p>
-<div id="scrolltoc" class="onpage">
-<p class="toc level2"><a href="">System Requirements for Automated Installations Using Media</a></p>
-</div>
-<p class="toc level2"><a href="howbootable.html">How to Install Using Media</a></p>
-<p class="toc level1 tocsp"><a href="setup.html">5. Set up an Automated Install Server</a></p>
-<p class="toc level1 tocsp"><a href="administer.html">6. How to Administer an Automated Install Server</a></p>
-<p class="toc level1 tocsp"><a href="client.html">7. How to Administer a Custom Install Client</a></p>
-<p class="toc level1 tocsp"><a href="manifest.html">8. How to Administer Manifest Files</a></p>
-<p class="toc level1 tocsp"><a href="clients.html">9. How to Manage Client Installations</a></p>
-<p class="toc level1 tocsp"><a href="trouble.html">10. Troubleshooting and FAQs for the Automated Installer</a></p>
-<p class="toc level1 tocsp"><a href="appendix.html">11. Appendix</a></p>
-</td>
- <td class="ContentPane" width="705px">
-
- <div class="MainContent">
-
-
-<a name="bootableclientreq"></a><h3>System Requirements for Automated Installations Using Media</h3>
-<p>To install by booting from AI media, the client systems must meet
-the following requirements:</p>
-<hr><p><b>Note - </b>Any system that meets these requirements can be used, including laptops, desktops, virtual
-machines, and enterprise servers.</p>
-<hr>
-<a name="ginjf2"></a><h6>Table 4-1 Client Requirements</h6><table><col width="27%"><col width="72%"><tr><th align="left" valign="top" scope="column"><p>Requirement</p></th>
-<th align="left" valign="top" scope="column"><p>Specifications</p></th>
-</tr>
-<tr><td align="left" valign="top" scope="row"><p>Memory</p></td>
-<td align="left" valign="top" scope="row"><p>Minimum memory: 512 MB</p></td>
-</tr>
-<tr><td align="left" valign="top" scope="row"><p>Disk Space</p></td>
-<td align="left" valign="top" scope="row"><p>Minimum disk space: 13 GB</p></td>
-</tr>
-<tr><td align="left" valign="top" scope="row"><p>Network
-Access</p></td>
-<td align="left" valign="top" scope="row"><p>Client systems must be on a network, so that the system can
-access the following during the installation:</p>
-<ul><li><p>A DHCP server that provides network configuration information</p></li>
-<li><p>An IPS repository that contains the packages to be installed on the client system</p></li>
-<li><p>Optional: A custom manifest posted on an HTTP server</p></li></ul>
-</td>
-</tr>
-</table>
- </div>
- </td>
- </tr>
-
- <tr class="PageControls" valign="top">
- <td></td>
- <td>
- <table width="100%">
- <tr>
- <td>
- <a href="whybootable.html">Previous</a>
- </td>
- <td align="right">
- <a href="howbootable.html">Next</a>
- </td>
- </tr>
- </table>
- </td>
- </tr>
-</tbody>
-</table>
-
-
-</body>
-</html>
-
--- a/usr/src/cmd/installadm/docs/bothclient.html Wed Sep 29 16:37:00 2010 +0200
+++ /dev/null Thu Jan 01 00:00:00 1970 +0000
@@ -1,193 +0,0 @@
-<!DOCTYPE HTML PUBLIC "-//W3C//DTD HTML 4.01 Transitional//EN" "http://www.w3.org/TR/html4/loose.dtd">
-<html lang="en-US">
-
-<!-- -->
-<head>
-<!-- GenHTML revision 23436-->
-<meta http-equiv="Content-type" content="text/html; charset=iso-8859-1">
-<title>SPARC and x86 Client Installation Messages and Errors - OpenSolaris 2010.03 Automated Installer Guide</title>
-<meta name="robots" content="index,follow">
-<meta name="robots" content="index,follow">
-<meta name="date" content="2010-03-01">
-<meta name="collection" content="reference">
-<link rel="stylesheet" type="text/css" href="css/elements.css">
-<link rel="stylesheet" type="text/css" href="css/opensol.css">
-</head>
-
-<body>
-
-
-<div class="Masthead">
- <div class="MastheadLogo">
- <a href="http://www.opensolaris.com"><img border="0" src="graphics/opensolaris_logo_trans.png"></img></a>
- </div>
- <div class="Title">OpenSolaris 2010.03 Automated Installer Guide</div>
-</div>
-<div class="headerbar"></div>
-
-
-<table class="Layout" border="0" cellspacing="0" width="100%">
-<tbody>
-
- <tr valign="top" class="PageControls">
- <td></td>
- <td>
- <table width="100%">
- <tr>
- <td>
- <a href="x86client.html">Previous</a>
- </td>
- <td align="right">
- <a href="trouble.html">Next</a>
- </td>
- </tr>
- </table>
- </td>
- </tr>
-
- <tr valign="top">
- <td class="Navigation" width="200px"><p class="toc level1"><a href="docinfo.html">Document Information</a></p>
-<p class="toc level1 tocsp"><a href="index.html">1. What's New For Automated Installations</a></p>
-<p class="toc level1 tocsp"><a href="intro.html">2. Introduction to the Automated Installer</a></p>
-<p class="toc level1 tocsp"><a href="tasks.html">3. Automated Network Install Task Map</a></p>
-<p class="toc level1 tocsp"><a href="bootable.html">4. Automated Installations That Boot From Media</a></p>
-<p class="toc level1 tocsp"><a href="setup.html">5. Set up an Automated Install Server</a></p>
-<p class="toc level1 tocsp"><a href="administer.html">6. How to Administer an Automated Install Server</a></p>
-<p class="toc level1 tocsp"><a href="client.html">7. How to Administer a Custom Install Client</a></p>
-<p class="toc level1 tocsp"><a href="manifest.html">8. How to Administer Manifest Files</a></p>
-<p class="toc level1 tocsp"><a href="clients.html">9. How to Manage Client Installations</a></p>
-<p class="toc level2"><a href="clientreq.html">Client System Requirements</a></p>
-<p class="toc level2"><a href="sparcclient.html">SPARC Client Installations</a></p>
-<p class="toc level2"><a href="x86client.html">x86 Client Installations</a></p>
-<div id="scrolltoc" class="onpage">
-<p class="toc level2"><a href="">SPARC and x86 Client Installation Messages and Errors</a></p>
-</div>
-<p class="toc level1 tocsp"><a href="trouble.html">10. Troubleshooting and FAQs for the Automated Installer</a></p>
-<p class="toc level1 tocsp"><a href="appendix.html">11. Appendix</a></p>
-</td>
- <td class="ContentPane" width="705px">
-
- <div class="MainContent">
-
-
-<a name="bothclient"></a><h3>SPARC and x86 Client Installation Messages and Errors</h3>
-<p>The following situations and display messages are common to both SPARC and x86
-installations.</p><p><a href="#aistart">1. Automated Installation Started Message</a></p><p><a href="#success">2. Auto Install Succeeded Message</a></p><p><a href="#failed">3. Automated Installation Failed Message</a></p><p><a href="#valid">4. Unable to Contact Valid Package Server Message</a></p><p><a href="#missing">5. <tt>install_log</tt> Reports Missing Package</a></p><p><a href="#errfail">6. Install Fails With Error 800 Message</a></p>
-
-<a name="aistart"></a><h4>1. Automated Installation Started Message</h4>
-<p>If the client is able to successfully boot and download the install files,
-then the following is displayed:</p><pre>Automated Installation started
- The progress of the Automated Installation can be followed by viewing the
- logfile at /tmp/install_log</pre><p>You can login as “root” with the password, “opensolaris,” to monitor the <tt>install_log</tt>.
-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, <tt>/var/svc/log/application-auto-installer:default.log</tt>.</p>
-
-<a name="success"></a><h4>2. Auto Install Succeeded Message</h4>
-<p>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.</p><p>Or, if you have setup automatic reboot in the AI manifest, then
-the system reboots at this time. The manifest tag, <tt><ai_auto_reboot></tt>, can be used
-to request automatic reboot after successful installation. The default value is <tt>false</tt>, meaning
-that the client does not automatically reboot after successful installation. If this value
-is changed to <tt>true</tt>, the client automatically reboots after successful installation.</p>
-
-<a name="failed"></a><h4>3. Automated Installation Failed Message</h4>
-<p>If there is a failure during installation, then the following message is displayed:</p><pre>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)</pre>
-
-<a name="valid"></a><h4>4. Unable to Contact Valid Package Server Message</h4>
-<p>If there is a failure during installation, check the log file, <tt>/tmp/install_log</tt>.
-If the AI client could not access the package server for installing packages,
-you may see the following error messages:</p><pre>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 /a</pre><p>The problem may caused by one of the following reasons:</p>
-<ul><li><p>The <tt>pkg_server</tt> is down. Try to access the <tt>pkg_server</tt> and check status.</p></li>
-<li><p>If you are using DNS, check whether the AI client is setup with DNS:</p><pre># <tt>svcs <tt>-a</tt> | grep <i>/network/dns/client</i></tt></pre><p>If the install service is disabled, then the client is not set up 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.</p></li>
-<li><p>If you are not using DNS, add the HTTP proxy information to the AI manifest and try the installation again. See <a href="customai.html#ieproxy">Specifying an HTTP Proxy to Reach an IPS Repository</a>.</p></li></ul>
-
-
-<a name="missing"></a><h4>5. <tt>install_log</tt> Reports Missing Package</h4>
-<p>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, <tt>SUNWTestPkg</tt>, in the IPS repository. You may see the following error
-message in the <tt>install_log</tt>:</p><pre><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 failed</pre><p>Check 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, <tt><ai_pkg_repo_default_publisher></tt>.</p>
-
-<a name="errfail"></a><h4>6. Install Fails With Error 800 Message</h4>
-<p>The error, “<tt>om_perform_install_failed</tt> 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 <tt>install_log</tt> for other failures. Usually when this error is
-returned, one of Install Completion Tasks (ICTs) has failed.</p><p>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 <tt>install_log</tt> 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
-<a href="faq.html#match">5. How Do I Install a Particular OpenSolaris Development Build?</a></p><p>For further troubleshooting information, see <a href="setupfaq.html#fails">2. What if the Client Installation Fails?</a></p>
- </div>
- </td>
- </tr>
-
- <tr class="PageControls" valign="top">
- <td></td>
- <td>
- <table width="100%">
- <tr>
- <td>
- <a href="x86client.html">Previous</a>
- </td>
- <td align="right">
- <a href="trouble.html">Next</a>
- </td>
- </tr>
- </table>
- </td>
- </tr>
-</tbody>
-</table>
-
-
-</body>
-</html>
-
--- a/usr/src/cmd/installadm/docs/cclient.html Wed Sep 29 16:37:00 2010 +0200
+++ /dev/null Thu Jan 01 00:00:00 1970 +0000
@@ -1,114 +0,0 @@
-<!DOCTYPE HTML PUBLIC "-//W3C//DTD HTML 4.01 Transitional//EN" "http://www.w3.org/TR/html4/loose.dtd">
-<html lang="en-US">
-
-<!-- -->
-<head>
-<!-- GenHTML revision 23436-->
-<meta http-equiv="Content-type" content="text/html; charset=iso-8859-1">
-<title>How to Set Up an Install Client - OpenSolaris 2010.03 Automated Installer Guide</title>
-<meta name="robots" content="index,follow">
-<meta name="robots" content="index,follow">
-<meta name="date" content="2010-03-01">
-<meta name="collection" content="reference">
-<link rel="stylesheet" type="text/css" href="css/elements.css">
-<link rel="stylesheet" type="text/css" href="css/opensol.css">
-</head>
-
-<body>
-
-
-<div class="Masthead">
- <div class="MastheadLogo">
- <a href="http://www.opensolaris.com"><img border="0" src="graphics/opensolaris_logo_trans.png"></img></a>
- </div>
- <div class="Title">OpenSolaris 2010.03 Automated Installer Guide</div>
-</div>
-<div class="headerbar"></div>
-
-
-<table class="Layout" border="0" cellspacing="0" width="100%">
-<tbody>
-
- <tr valign="top" class="PageControls">
- <td></td>
- <td>
- <table width="100%">
- <tr>
- <td>
- <a href="client.html">Previous</a>
- </td>
- <td align="right">
- <a href="scenario.html">Next</a>
- </td>
- </tr>
- </table>
- </td>
- </tr>
-
- <tr valign="top">
- <td class="Navigation" width="200px"><p class="toc level1"><a href="docinfo.html">Document Information</a></p>
-<p class="toc level1 tocsp"><a href="index.html">1. What's New For Automated Installations</a></p>
-<p class="toc level1 tocsp"><a href="intro.html">2. Introduction to the Automated Installer</a></p>
-<p class="toc level1 tocsp"><a href="tasks.html">3. Automated Network Install Task Map</a></p>
-<p class="toc level1 tocsp"><a href="bootable.html">4. Automated Installations That Boot From Media</a></p>
-<p class="toc level1 tocsp"><a href="setup.html">5. Set up an Automated Install Server</a></p>
-<p class="toc level1 tocsp"><a href="administer.html">6. How to Administer an Automated Install Server</a></p>
-<p class="toc level1 tocsp"><a href="client.html">7. How to Administer a Custom Install Client</a></p>
-<div id="scrolltoc" class="onpage">
-<p class="toc level2"><a href="">How to Set Up an Install Client</a></p>
-</div>
-<p class="toc level2"><a href="scenario.html">Example: Creating a Custom Install Client</a></p>
-<p class="toc level2"><a href="delclient.html">How to Delete an Install Client</a></p>
-<p class="toc level1 tocsp"><a href="manifest.html">8. How to Administer Manifest Files</a></p>
-<p class="toc level1 tocsp"><a href="clients.html">9. How to Manage Client Installations</a></p>
-<p class="toc level1 tocsp"><a href="trouble.html">10. Troubleshooting and FAQs for the Automated Installer</a></p>
-<p class="toc level1 tocsp"><a href="appendix.html">11. Appendix</a></p>
-</td>
- <td class="ContentPane" width="705px">
-
- <div class="MainContent">
-
-
-<a name="cclient"></a><h3>How to Set Up an Install Client</h3>
-<p>You can use the <tt>installadm create-client</tt> 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.</p><p>To create custom client specifications, you need to provide the following information:</p>
-<ul><li><p>MAC address for the client.</p></li>
-<li><p>Path of the ISO image to be used by the automated installer for this client.</p></li>
-<li><p>Name of the install service for the client to use for installation.</p></li>
-<li><p>For x86 clients, you can optionally specify boot properties.</p></li></ul>
-<p><b>Use the following command to provide custom client settings.</b></p><p><tt>installadm create-client [<tt>-b</tt> <i>property=value,...</i>] [<tt>-t</tt> <i>imagepath</i>] <tt>-e</tt> <i>macaddr</i> <tt>-n</tt> <i>svcname</i></tt></p><p>This command has the following options:</p>
-<ul><li><p>For x86 systems only, the <tt>-b</tt> option may be used to set one or more property values, <i>property=value,...</i>, in the client-specific <tt>menu.lst file</tt> in <tt>/tftpboot</tt>. Use this option to set boot properties that are specific to this client. This option can accept multiple <tt>property=value</tt> pairs.</p></li>
-<li><p>Use the <tt>-t</tt> option to specify the path, <tt>imagepath</tt>, for the ISO image to be used by the automated installer.</p>
-<hr><p><b>Note - </b>This image was set up when you created the install service by using the <tt>installadm create-service</tt> command.</p>
-<hr>
-</li>
-<li><p>Use the <tt>-e</tt> option to specify the MAC address, <tt>macaddr</tt>, of the client.</p></li>
-<li><p>Use the <tt>-n</tt> option to specify an install service, <tt>svcname</tt>, for the client to use for installation.</p></li></ul>
-
- </div>
- </td>
- </tr>
-
- <tr class="PageControls" valign="top">
- <td></td>
- <td>
- <table width="100%">
- <tr>
- <td>
- <a href="client.html">Previous</a>
- </td>
- <td align="right">
- <a href="scenario.html">Next</a>
- </td>
- </tr>
- </table>
- </td>
- </tr>
-</tbody>
-</table>
-
-
-</body>
-</html>
-
--- a/usr/src/cmd/installadm/docs/client.html Wed Sep 29 16:37:00 2010 +0200
+++ /dev/null Thu Jan 01 00:00:00 1970 +0000
@@ -1,106 +0,0 @@
-<!DOCTYPE HTML PUBLIC "-//W3C//DTD HTML 4.01 Transitional//EN" "http://www.w3.org/TR/html4/loose.dtd">
-<html lang="en-US">
-
-<!-- -->
-<head>
-<!-- GenHTML revision 23436-->
-<meta http-equiv="Content-type" content="text/html; charset=iso-8859-1">
-<title>How to Administer a Custom Install Client - OpenSolaris 2010.03 Automated Installer Guide</title>
-<meta name="robots" content="index,follow">
-<meta name="robots" content="index,follow">
-<meta name="date" content="2010-03-01">
-<meta name="collection" content="reference">
-<link rel="stylesheet" type="text/css" href="css/elements.css">
-<link rel="stylesheet" type="text/css" href="css/opensol.css">
-</head>
-
-<body>
-
-
-<div class="Masthead">
- <div class="MastheadLogo">
- <a href="http://www.opensolaris.com"><img border="0" src="graphics/opensolaris_logo_trans.png"></img></a>
- </div>
- <div class="Title">OpenSolaris 2010.03 Automated Installer Guide</div>
-</div>
-<div class="headerbar"></div>
-
-
-<table class="Layout" border="0" cellspacing="0" width="100%">
-<tbody>
-
- <tr valign="top" class="PageControls">
- <td></td>
- <td>
- <table width="100%">
- <tr>
- <td>
- <a href="smf.html">Previous</a>
- </td>
- <td align="right">
- <a href="cclient.html">Next</a>
- </td>
- </tr>
- </table>
- </td>
- </tr>
-
- <tr valign="top">
- <td class="Navigation" width="200px"><p class="toc level1"><a href="docinfo.html">Document Information</a></p>
-<p class="toc level1 tocsp"><a href="index.html">1. What's New For Automated Installations</a></p>
-<p class="toc level1 tocsp"><a href="intro.html">2. Introduction to the Automated Installer</a></p>
-<p class="toc level1 tocsp"><a href="tasks.html">3. Automated Network Install Task Map</a></p>
-<p class="toc level1 tocsp"><a href="bootable.html">4. Automated Installations That Boot From Media</a></p>
-<p class="toc level1 tocsp"><a href="setup.html">5. Set up an Automated Install Server</a></p>
-<p class="toc level1 tocsp"><a href="administer.html">6. How to Administer an Automated Install Server</a></p>
-<div id="scrolltoc" class="onpage">
-<p class="toc level1 tocsp"><a href="">7. How to Administer a Custom Install Client</a></p>
-</div>
-<p class="toc level2"><a href="cclient.html">How to Set Up an Install Client</a></p>
-<p class="toc level2"><a href="scenario.html">Example: Creating a Custom Install Client</a></p>
-<p class="toc level2"><a href="delclient.html">How to Delete an Install Client</a></p>
-<p class="toc level1 tocsp"><a href="manifest.html">8. How to Administer Manifest Files</a></p>
-<p class="toc level1 tocsp"><a href="clients.html">9. How to Manage Client Installations</a></p>
-<p class="toc level1 tocsp"><a href="trouble.html">10. Troubleshooting and FAQs for the Automated Installer</a></p>
-<p class="toc level1 tocsp"><a href="appendix.html">11. Appendix</a></p>
-</td>
- <td class="ContentPane" width="705px">
-
- <div class="MainContent">
- <a name="client"></a>Chapter 7<h3>How to Administer a Custom Install Client</h3><p>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, the
-default installation specifications that you set up by using the <tt>installadm create-service</tt> 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.</p>
-<hr><p><b>Note - </b>If you plan to install to SPARC client systems, those systems must support
-WAN Boot. For more information, see <a href="faq.html#wanboot">2. Does My SPARC Client Support WAN Boot?</a></p>
-<hr>
-
- </div>
- </td>
- </tr>
-
- <tr class="PageControls" valign="top">
- <td></td>
- <td>
- <table width="100%">
- <tr>
- <td>
- <a href="smf.html">Previous</a>
- </td>
- <td align="right">
- <a href="cclient.html">Next</a>
- </td>
- </tr>
- </table>
- </td>
- </tr>
-</tbody>
-</table>
-
-
-</body>
-</html>
-
--- a/usr/src/cmd/installadm/docs/clientinstall.html Wed Sep 29 16:37:00 2010 +0200
+++ /dev/null Thu Jan 01 00:00:00 1970 +0000
@@ -1,108 +0,0 @@
-<!DOCTYPE HTML PUBLIC "-//W3C//DTD HTML 4.01 Transitional//EN" "http://www.w3.org/TR/html4/loose.dtd">
-<html lang="en-US">
-
-<!-- -->
-<head>
-<!-- GenHTML revision 23436-->
-<meta http-equiv="Content-type" content="text/html; charset=iso-8859-1">
-<title>How a Client Is Installed - OpenSolaris 2010.03 Automated Installer Guide</title>
-<meta name="robots" content="index,follow">
-<meta name="robots" content="index,follow">
-<meta name="date" content="2010-03-01">
-<meta name="collection" content="reference">
-<link rel="stylesheet" type="text/css" href="css/elements.css">
-<link rel="stylesheet" type="text/css" href="css/opensol.css">
-</head>
-
-<body>
-
-
-<div class="Masthead">
- <div class="MastheadLogo">
- <a href="http://www.opensolaris.com"><img border="0" src="graphics/opensolaris_logo_trans.png"></img></a>
- </div>
- <div class="Title">OpenSolaris 2010.03 Automated Installer Guide</div>
-</div>
-<div class="headerbar"></div>
-
-
-<table class="Layout" border="0" cellspacing="0" width="100%">
-<tbody>
-
- <tr valign="top" class="PageControls">
- <td></td>
- <td>
- <table width="100%">
- <tr>
- <td>
- <a href="use.html">Previous</a>
- </td>
- <td align="right">
- <a href="benefits.html">Next</a>
- </td>
- </tr>
- </table>
- </td>
- </tr>
-
- <tr valign="top">
- <td class="Navigation" width="200px"><p class="toc level1"><a href="docinfo.html">Document Information</a></p>
-<p class="toc level1 tocsp"><a href="index.html">1. What's New For Automated Installations</a></p>
-<p class="toc level1 tocsp"><a href="intro.html">2. Introduction to the Automated Installer</a></p>
-<p class="toc level2"><a href="whatis.html">What Is an Automated Installation?</a></p>
-<p class="toc level2"><a href="use.html">How Do I Use the Automated Installer?</a></p>
-<div id="scrolltoc" class="onpage">
-<p class="toc level2"><a href="">How a Client Is Installed</a></p>
-</div>
-<p class="toc level2"><a href="benefits.html">Automated Installation Benefits</a></p>
-<p class="toc level1 tocsp"><a href="tasks.html">3. Automated Network Install Task Map</a></p>
-<p class="toc level1 tocsp"><a href="bootable.html">4. Automated Installations That Boot From Media</a></p>
-<p class="toc level1 tocsp"><a href="setup.html">5. Set up an Automated Install Server</a></p>
-<p class="toc level1 tocsp"><a href="administer.html">6. How to Administer an Automated Install Server</a></p>
-<p class="toc level1 tocsp"><a href="client.html">7. How to Administer a Custom Install Client</a></p>
-<p class="toc level1 tocsp"><a href="manifest.html">8. How to Administer Manifest Files</a></p>
-<p class="toc level1 tocsp"><a href="clients.html">9. How to Manage Client Installations</a></p>
-<p class="toc level1 tocsp"><a href="trouble.html">10. Troubleshooting and FAQs for the Automated Installer</a></p>
-<p class="toc level1 tocsp"><a href="appendix.html">11. Appendix</a></p>
-</td>
- <td class="ContentPane" width="705px">
-
- <div class="MainContent">
-
-
-<a name="clientinstall"></a><h3>How a Client Is Installed</h3>
-<p>You're ready for network installations. You have set up an install server with
-one or more install services. You've customized the installation specifications for the install
-services to suit your needs. Now, you are ready to install the OpenSolaris
-OS to client systems by booting over the network. You need only to
-boot the client, and the process runs to completion without further input from
-you.</p><p>The following flowchart illustrates how a client system is installed. On booting, the
-client finds an install service per specifications in the boot arguments. The installation
-is performed on the client system, using a boot image and manifest specifications
-provided by the install service.</p><a name="flowchart"></a><h6>Figure 2-1 Client Installation Steps</h6><img src="figures/aiflow.gif" alt="Graphic illustrates the steps for client installation" width="618" height="696"></img><p>For further information, see <a href="clients.html">Chapter 9, How to Manage Client Installations</a>.</p>
- </div>
- </td>
- </tr>
-
- <tr class="PageControls" valign="top">
- <td></td>
- <td>
- <table width="100%">
- <tr>
- <td>
- <a href="use.html">Previous</a>
- </td>
- <td align="right">
- <a href="benefits.html">Next</a>
- </td>
- </tr>
- </table>
- </td>
- </tr>
-</tbody>
-</table>
-
-
-</body>
-</html>
-
--- a/usr/src/cmd/installadm/docs/clientreq.html Wed Sep 29 16:37:00 2010 +0200
+++ /dev/null Thu Jan 01 00:00:00 1970 +0000
@@ -1,120 +0,0 @@
-<!DOCTYPE HTML PUBLIC "-//W3C//DTD HTML 4.01 Transitional//EN" "http://www.w3.org/TR/html4/loose.dtd">
-<html lang="en-US">
-
-<!-- -->
-<head>
-<!-- GenHTML revision 23436-->
-<meta http-equiv="Content-type" content="text/html; charset=iso-8859-1">
-<title>Client System Requirements - OpenSolaris 2010.03 Automated Installer Guide</title>
-<meta name="robots" content="index,follow">
-<meta name="robots" content="index,follow">
-<meta name="date" content="2010-03-01">
-<meta name="collection" content="reference">
-<link rel="stylesheet" type="text/css" href="css/elements.css">
-<link rel="stylesheet" type="text/css" href="css/opensol.css">
-</head>
-
-<body>
-
-
-<div class="Masthead">
- <div class="MastheadLogo">
- <a href="http://www.opensolaris.com"><img border="0" src="graphics/opensolaris_logo_trans.png"></img></a>
- </div>
- <div class="Title">OpenSolaris 2010.03 Automated Installer Guide</div>
-</div>
-<div class="headerbar"></div>
-
-
-<table class="Layout" border="0" cellspacing="0" width="100%">
-<tbody>
-
- <tr valign="top" class="PageControls">
- <td></td>
- <td>
- <table width="100%">
- <tr>
- <td>
- <a href="clients.html">Previous</a>
- </td>
- <td align="right">
- <a href="sparcclient.html">Next</a>
- </td>
- </tr>
- </table>
- </td>
- </tr>
-
- <tr valign="top">
- <td class="Navigation" width="200px"><p class="toc level1"><a href="docinfo.html">Document Information</a></p>
-<p class="toc level1 tocsp"><a href="index.html">1. What's New For Automated Installations</a></p>
-<p class="toc level1 tocsp"><a href="intro.html">2. Introduction to the Automated Installer</a></p>
-<p class="toc level1 tocsp"><a href="tasks.html">3. Automated Network Install Task Map</a></p>
-<p class="toc level1 tocsp"><a href="bootable.html">4. Automated Installations That Boot From Media</a></p>
-<p class="toc level1 tocsp"><a href="setup.html">5. Set up an Automated Install Server</a></p>
-<p class="toc level1 tocsp"><a href="administer.html">6. How to Administer an Automated Install Server</a></p>
-<p class="toc level1 tocsp"><a href="client.html">7. How to Administer a Custom Install Client</a></p>
-<p class="toc level1 tocsp"><a href="manifest.html">8. How to Administer Manifest Files</a></p>
-<p class="toc level1 tocsp"><a href="clients.html">9. How to Manage Client Installations</a></p>
-<div id="scrolltoc" class="onpage">
-<p class="toc level2"><a href="">Client System Requirements</a></p>
-</div>
-<p class="toc level2"><a href="sparcclient.html">SPARC Client Installations</a></p>
-<p class="toc level2"><a href="x86client.html">x86 Client Installations</a></p>
-<p class="toc level2"><a href="bothclient.html">SPARC and x86 Client Installation Messages and Errors</a></p>
-<p class="toc level1 tocsp"><a href="trouble.html">10. Troubleshooting and FAQs for the Automated Installer</a></p>
-<p class="toc level1 tocsp"><a href="appendix.html">11. Appendix</a></p>
-</td>
- <td class="ContentPane" width="705px">
-
- <div class="MainContent">
-
-
-<a name="clientreq"></a><h3>Client System Requirements</h3>
-<p>The client systems for automated installation must meet the following requirements:</p>
-<hr><p><b>Note - </b>Any system that meets these requirements can be used as an automated install
-client, including laptops, desktops, virtual machines, and enterprise servers.</p>
-<hr>
-<a name="ginjf"></a><h6>Table 9-1 Client Requirements</h6><table><col width="27%"><col width="72%"><tr><th align="left" valign="top" scope="column"><p>Platform</p></th>
-<th align="left" valign="top" scope="column"><p>Requirement</p></th>
-</tr>
-<tr><td align="left" valign="top" scope="row"><p>SPARC Clients</p></td>
-<td align="left" valign="top" scope="row">
-<ul><li><p>For installations that boot over the network, the client system must support WAN Boot in the Open Boot Prompt.</p><p>See <a href="faq.html#wanboot">2. Does My SPARC Client Support WAN Boot?</a></p></li>
-<li><p>Minimum memory: 512 MB</p></li>
-<li><p>Minimum disk space: 13 GB</p></li></ul>
-</td>
-</tr>
-<tr><td align="left" valign="top" scope="row"><p>x86 Clients</p></td>
-<td align="left" valign="top" scope="row">
-<ul><li><p>Minimum memory: 512 MB</p></li>
-<li><p>Minimum disk space: 13 GB</p></li></ul>
-</td>
-</tr>
-</table>
- </div>
- </td>
- </tr>
-
- <tr class="PageControls" valign="top">
- <td></td>
- <td>
- <table width="100%">
- <tr>
- <td>
- <a href="clients.html">Previous</a>
- </td>
- <td align="right">
- <a href="sparcclient.html">Next</a>
- </td>
- </tr>
- </table>
- </td>
- </tr>
-</tbody>
-</table>
-
-
-</body>
-</html>
-
--- a/usr/src/cmd/installadm/docs/clients.html Wed Sep 29 16:37:00 2010 +0200
+++ /dev/null Thu Jan 01 00:00:00 1970 +0000
@@ -1,105 +0,0 @@
-<!DOCTYPE HTML PUBLIC "-//W3C//DTD HTML 4.01 Transitional//EN" "http://www.w3.org/TR/html4/loose.dtd">
-<html lang="en-US">
-
-<!-- -->
-<head>
-<!-- GenHTML revision 23436-->
-<meta http-equiv="Content-type" content="text/html; charset=iso-8859-1">
-<title>How to Manage Client Installations - OpenSolaris 2010.03 Automated Installer Guide</title>
-<meta name="robots" content="index,follow">
-<meta name="robots" content="index,follow">
-<meta name="date" content="2010-03-01">
-<meta name="collection" content="reference">
-<link rel="stylesheet" type="text/css" href="css/elements.css">
-<link rel="stylesheet" type="text/css" href="css/opensol.css">
-</head>
-
-<body>
-
-
-<div class="Masthead">
- <div class="MastheadLogo">
- <a href="http://www.opensolaris.com"><img border="0" src="graphics/opensolaris_logo_trans.png"></img></a>
- </div>
- <div class="Title">OpenSolaris 2010.03 Automated Installer Guide</div>
-</div>
-<div class="headerbar"></div>
-
-
-<table class="Layout" border="0" cellspacing="0" width="100%">
-<tbody>
-
- <tr valign="top" class="PageControls">
- <td></td>
- <td>
- <table width="100%">
- <tr>
- <td>
- <a href="associate.html">Previous</a>
- </td>
- <td align="right">
- <a href="clientreq.html">Next</a>
- </td>
- </tr>
- </table>
- </td>
- </tr>
-
- <tr valign="top">
- <td class="Navigation" width="200px"><p class="toc level1"><a href="docinfo.html">Document Information</a></p>
-<p class="toc level1 tocsp"><a href="index.html">1. What's New For Automated Installations</a></p>
-<p class="toc level1 tocsp"><a href="intro.html">2. Introduction to the Automated Installer</a></p>
-<p class="toc level1 tocsp"><a href="tasks.html">3. Automated Network Install Task Map</a></p>
-<p class="toc level1 tocsp"><a href="bootable.html">4. Automated Installations That Boot From Media</a></p>
-<p class="toc level1 tocsp"><a href="setup.html">5. Set up an Automated Install Server</a></p>
-<p class="toc level1 tocsp"><a href="administer.html">6. How to Administer an Automated Install Server</a></p>
-<p class="toc level1 tocsp"><a href="client.html">7. How to Administer a Custom Install Client</a></p>
-<p class="toc level1 tocsp"><a href="manifest.html">8. How to Administer Manifest Files</a></p>
-<div id="scrolltoc" class="onpage">
-<p class="toc level1 tocsp"><a href="">9. How to Manage Client Installations</a></p>
-</div>
-<p class="toc level2"><a href="clientreq.html">Client System Requirements</a></p>
-<p class="toc level2"><a href="sparcclient.html">SPARC Client Installations</a></p>
-<p class="toc level2"><a href="x86client.html">x86 Client Installations</a></p>
-<p class="toc level2"><a href="bothclient.html">SPARC and x86 Client Installation Messages and Errors</a></p>
-<p class="toc level1 tocsp"><a href="trouble.html">10. Troubleshooting and FAQs for the Automated Installer</a></p>
-<p class="toc level1 tocsp"><a href="appendix.html">11. Appendix</a></p>
-</td>
- <td class="ContentPane" width="705px">
-
- <div class="MainContent">
- <a name="clients"></a>Chapter 9<h3>How to Manage Client Installations</h3><p>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.</p>
-<ul><li><p><a href="clientreq.html">Client System Requirements</a></p></li>
-<li><p><a href="sparcclient.html">SPARC Client Installations</a></p></li>
-<li><p><a href="x86client.html">x86 Client Installations</a></p></li>
-<li><p><a href="bothclient.html">SPARC and x86 Client Installation Messages and Errors</a></p></li></ul>
-
- </div>
- </td>
- </tr>
-
- <tr class="PageControls" valign="top">
- <td></td>
- <td>
- <table width="100%">
- <tr>
- <td>
- <a href="associate.html">Previous</a>
- </td>
- <td align="right">
- <a href="clientreq.html">Next</a>
- </td>
- </tr>
- </table>
- </td>
- </tr>
-</tbody>
-</table>
-
-
-</body>
-</html>
-
--- a/usr/src/cmd/installadm/docs/criteria.html Wed Sep 29 16:37:00 2010 +0200
+++ /dev/null Thu Jan 01 00:00:00 1970 +0000
@@ -1,209 +0,0 @@
-<!DOCTYPE HTML PUBLIC "-//W3C//DTD HTML 4.01 Transitional//EN" "http://www.w3.org/TR/html4/loose.dtd">
-<html lang="en-US">
-
-<!-- -->
-<head>
-<!-- GenHTML revision 23436-->
-<meta http-equiv="Content-type" content="text/html; charset=iso-8859-1">
-<title>How to Create and Use a Criteria Manifest - OpenSolaris 2010.03 Automated Installer Guide</title>
-<meta name="robots" content="index,follow">
-<meta name="robots" content="index,follow">
-<meta name="date" content="2010-03-01">
-<meta name="collection" content="reference">
-<link rel="stylesheet" type="text/css" href="css/elements.css">
-<link rel="stylesheet" type="text/css" href="css/opensol.css">
-</head>
-
-<body>
-
-
-<div class="Masthead">
- <div class="MastheadLogo">
- <a href="http://www.opensolaris.com"><img border="0" src="graphics/opensolaris_logo_trans.png"></img></a>
- </div>
- <div class="Title">OpenSolaris 2010.03 Automated Installer Guide</div>
-</div>
-<div class="headerbar"></div>
-
-
-<table class="Layout" border="0" cellspacing="0" width="100%">
-<tbody>
-
- <tr valign="top" class="PageControls">
- <td></td>
- <td>
- <table width="100%">
- <tr>
- <td>
- <a href="customsc.html">Previous</a>
- </td>
- <td align="right">
- <a href="associate.html">Next</a>
- </td>
- </tr>
- </table>
- </td>
- </tr>
-
- <tr valign="top">
- <td class="Navigation" width="200px"><p class="toc level1"><a href="docinfo.html">Document Information</a></p>
-<p class="toc level1 tocsp"><a href="index.html">1. What's New For Automated Installations</a></p>
-<p class="toc level1 tocsp"><a href="intro.html">2. Introduction to the Automated Installer</a></p>
-<p class="toc level1 tocsp"><a href="tasks.html">3. Automated Network Install Task Map</a></p>
-<p class="toc level1 tocsp"><a href="bootable.html">4. Automated Installations That Boot From Media</a></p>
-<p class="toc level1 tocsp"><a href="setup.html">5. Set up an Automated Install Server</a></p>
-<p class="toc level1 tocsp"><a href="administer.html">6. How to Administer an Automated Install Server</a></p>
-<p class="toc level1 tocsp"><a href="client.html">7. How to Administer a Custom Install Client</a></p>
-<p class="toc level1 tocsp"><a href="manifest.html">8. How to Administer Manifest Files</a></p>
-<p class="toc level2"><a href="manifest1.html">Types of Manifests</a></p>
-<p class="toc level2"><a href="customai.html">How to Create and Use a Custom AI Manifest</a></p>
-<p class="toc level2"><a href="customsc.html">How to Create Custom SC Manifest Files</a></p>
-<div id="scrolltoc" class="onpage">
-<p class="toc level2"><a href="">How to Create and Use a Criteria Manifest</a></p>
-</div>
-<p class="toc level2"><a href="associate.html">How to Assign Manifests to a Client</a></p>
-<p class="toc level1 tocsp"><a href="clients.html">9. How to Manage Client Installations</a></p>
-<p class="toc level1 tocsp"><a href="trouble.html">10. Troubleshooting and FAQs for the Automated Installer</a></p>
-<p class="toc level1 tocsp"><a href="appendix.html">11. Appendix</a></p>
-</td>
- <td class="ContentPane" width="705px">
-
- <div class="MainContent">
-
-
-<a name="criteria"></a><h3>How to Create and Use a Criteria Manifest</h3>
-<p> 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 receives the criteria manifest file that
-you assigned to the service.</p>
-<hr><p><b>Note - </b>The default manifest that is included in the AI images functions as a
-criteria manifest, containing the full default contents for an AI manifest and an
-SC manifest. See the default criteria manifest at <a href="aimanifest.html#defaultcri">Default Manifest File, <tt>default.xml</tt></a>.</p>
-<hr>
-<p>To work with AI manifests and SC manifests as separate XML files,
-you need to reference their file locations in the criteria manifest. Use the
-following basic procedure:</p>
-<ol><li><p>Create your AI manifest. You can copy and use the AI manifest section from the default manifest at <a href="aimanifest.html#defaultcri">Default Manifest File, <tt>default.xml</tt></a>. Or, you can copy and use the sample AI manifest that uses all parameters at <a href="customai.html#allfields">Example: A Complete AI Manifest</a>.</p><p>Save your AI manifest in a file named <tt>ai_manifest1.xml</tt>.</p></li>
-<li><p>Create an SC manifest by copying and modifying the example in <a href="customsc.html#current">Modifying the SC Manifest</a>. </p><p>Save your SC manifest in a file named <tt>sc_manifest1.xml</tt>.</p></li>
-<li><p>Create a criteria manifest based on the specifications of the client. You can use the example in <a href="#ieipadd">Criteria Based on the Client IP Address</a> as the first draft for a new criteria manifest. Then see the other examples below to modify your draft.</p><p>These sample criteria manifests below include the file location of the AI manifest and the SC manifest inside the criteria manifest. The criteria manifest examples below refer to the AI manifest, <tt>ai_manifest1.xml</tt>, and the SC manifest, <tt>sc_manifest1.xml</tt>.</p></li>
-<li><p>Add the criteria manifest to the install service. See <a href="associate.html">How to Assign Manifests to a Client</a>.</p></li></ol>
-
-
-<a name="criteriaie"></a><h4>Criteria Manifest Examples</h4>
-<p>The following examples show options for creating a criteria manifest. Each example below
-is a complete criteria manifest, containing cross-references to an AI manifest and SC
-manifest.</p>
-<ul><li><p><a href="#ieipadd">Criteria Based on the Client IP Address</a></p></li>
-<li><p><a href="#ierange">Criteria Based on the Client IP Address Range</a></p></li>
-<li><p><a href="#iemac">Criteria Based on the Client MAC Address</a></p></li>
-<li><p><a href="#macrange">Criteria Based on the Client MAC Address Range</a></p></li>
-<li><p><a href="#iememory">Criteria Based on the Client Memory Size</a></p></li>
-<li><p><a href="#iearch">Criteria Based on the Client Architecture</a></p></li></ul>
-
-
-<a name="ieipadd"></a><h5>Criteria Based on the Client IP Address</h5>
-<p>You can use this example as the first draft of a new
-criteria manifest. Use the other examples to modify your draft.</p><p>The following example assigns <tt>ai_manifest1</tt> and <tt>sc_manifest1</tt> to the client with IP
-address <tt>10.6.68.127</tt>. </p><pre><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></pre>
-<hr><p><b>Note - </b>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, <tt>./ai_manifest1.xml</tt>.</p>
-<hr>
-
-
-<a name="ierange"></a><h5>Criteria Based on the Client IP Address Range</h5>
-<p>The following example assigns <tt>ai_manifest1</tt> and <tt>sc_manifest1</tt> to clients in the IP
-address range, <tt>10.6.68.1</tt> to <tt>10.6.68.200</tt>. Since there is more than 1 value,
-the tag, <tt><range></tt>, should be used.</p><pre><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></pre>
-
-<a name="iemac"></a><h5>Criteria Based on the Client MAC Address</h5>
-<p>The following example assigns <tt>ai_manifest1</tt> and <tt>sc_manifest1</tt> to the client with MAC
-address <tt>0:14:4f:20:53:94</tt>.</p><pre><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> </pre>
-
-<a name="macrange"></a><h5>Criteria Based on the Client MAC Address Range</h5>
-<p>The following example assigns <tt>ai_manifest1</tt> and <tt>sc_manifest1</tt> to clients in the MAC
-address range, <tt>0:14:4F:20:53:94</tt> to <tt>0:14:4F:20:53:A0</tt>. Since there is more than 1 value, the
-tag, <tt><range></tt>, should be used.</p><pre><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> </pre>
-
-<a name="iememory"></a><h5>Criteria Based on the Client Memory Size</h5>
-<p>The following example assigns <tt>ai_manifest1</tt> and <tt>sc_manifest1</tt> to clients that have at
-least 2 Gbytes memory. The <tt>unbounded</tt> keyword is used to express no
-bounding value. The value in the <tt><range></tt> tag is expressed in megabytes, in
-this case, 2048 MB.</p><pre><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></pre>
-
-<a name="iearch"></a><h5>Criteria Based on the Client Architecture</h5>
-<p>The following example assigns <tt>ai_manifest1</tt> and <tt>sc_manifest1</tt> to clients with an architecture
-of <tt>i86pc</tt>.</p><pre><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></pre>
- </div>
- </td>
- </tr>
-
- <tr class="PageControls" valign="top">
- <td></td>
- <td>
- <table width="100%">
- <tr>
- <td>
- <a href="customsc.html">Previous</a>
- </td>
- <td align="right">
- <a href="associate.html">Next</a>
- </td>
- </tr>
- </table>
- </td>
- </tr>
-</tbody>
-</table>
-
-
-</body>
-</html>
-
--- a/usr/src/cmd/installadm/docs/css/advanced.css Wed Sep 29 16:37:00 2010 +0200
+++ /dev/null Thu Jan 01 00:00:00 1970 +0000
@@ -1,575 +0,0 @@
-/* ###########################################################################
-
-# SUN ADVANCED.CSS v3.2 #
-
-COPYRIGHT SUN MICROSYSTEMS INC.
-
-IF YOU WISH TO ADD TO OR EDIT THIS CSS CONTACT webdesign -at- sun.com FIRST!
-
-NOTE: YOU *MUST* CHANGE ALL REFERENCES TO /CSS AND /IM TO REFLECT THE
- APPROPRIATE DIRECTORY.
-
-########################################################################### */
-
-/* forms */
-input.buttonblue,input.buttonred{cursor:hand;color:#FFF;font-weight:bold;font-size:11px;padding:2px 1px;margin:0px;white-space:nowrap}
-input.buttonred{background:url("bg_sunorange.gif") repeat-x left top #E76F00;border-right:1px solid #C06600;border-bottom:1px solid #C06600;border-left:1px solid #FAE2CC;border-top:1px solid #FAE2CC}
-input.buttonblue{background:url("bg_sunblue.gif") repeat-x 0px -10px #304C60;border-right:1px solid #304C60;border-bottom:1px solid #304C60;border-left:1px solid #BACDD9;border-top:1px solid #BACDD9}
-input.error, select.error, textarea.error{border:2px solid;background:#FEE;border-top-color:#C00;border-left-color:#C00;border-right-color:#F00;border-bottom-color:#F00}
-input.medium{width:120px}
-input.mediumlarge,select.rightmodule{width:130px}
-input.large{width:200px}
-
-/* hr */
-hr.light{background:#E3E3E3;color:#E3E3E3;height:2px;padding:0px;border:0px}
-hr{background:#333;color:#333;height:2px;padding:0px;border:0px}
-.pc0v5 hr,.col1 hr.light,.col2 hr.light{background:#CCC;color:#CCC;height:2px;padding:0px;border-left:0px;border-right:0px;border-top:0px;border-bottom:1px #FFF solid;margin-bottom:10px}
-td.grey3 span.sp5{line-height:2px;font-size:2px !important}
-
-/* misc */
-div.bluearrows,span.bluearrows{background:url("ar_dbl_blue.gif") no-repeat top left;padding-left:10px}
-ul.bluearrows li{margin:0px;padding:0px 0px 4px 10px;list-style-image:url("a.gif");background:url("ar_dbl_blue.gif") no-repeat left top}
-ul.bluearrows{margin:0px;padding:0px}
-.whtcopy,a.whitelink,a.whitelink:link,a.whitelink:hover,a.whitelink:visited{color:#FFF}
-td.sectiontitle1,td.sectiontitle1 a,td.sectiontitle1 div,td.sectiontitle2,td.sectiontitle2 a,td.sectiontitle2 div{font-weight:bold}
-.sunblue a.whitelink,.sunblue a.whitelink:visited{color:#FFF}
-.sunblue a.yellowlink,.sunblue a.yellowlink:visited,td.sunblue b,td.sunblue div.navtitle{color:#FFD55C}
-
-/* pad */
-div.pad2x8{padding:2px 8px}
-div.pad3x0{padding:3px 0px}
-div.pad5x10{padding:5px 10px}
-div.pad5x10x5x0{padding:5px 10px 5px 0px}
-.headerpadding{padding:1px 10px}
-.redwidgetpadding{padding:2px 0px 3px 0px}
-.gwpadding1{padding:2px 10px 7px 8px}
-
-/* table styles */
-td.tablecaption,th.tablecaption,.tablecaption a,.tablecaption div a,
-td.tablecaption2,th.tablecaption2,.tablecaption2 a,.tablecaption2 div a,
-td.tablecaption3,th.tablecaption3,.tablecaption3 a,.tablecaption3 div a,
-td.tablecaption4,th.tablecaption4,.tablecaption4 a,.tablecaption4 div a,
-td.tablecaption5,th.tablecaption5,.tablecaption5 a,.tablecaption5 div a,
-td.tablecaption6,th.tablecaption6,.tablecaption6 a,.tablecaption6 div a,
-td.tablecaption7,th.tablecaption7,.tablecaption7 a,.tablecaption7 div a{color:#FFF;font-weight:bold}
-td.redwidget{color:#FFF;vertical-align:top}
-td.redwidget b{color:#FFDE00}
-td.redwidget a:link,td.redwidget a:visited{color:#FFF}
-td.redwidget a:hover{color:#FBE249;text-decoration:none}
-td.redwidget{border-right:1px solid #C06600;border-bottom:1px solid #C06600;border-left:1px solid #FAE2CC;border-top:1px solid #FAE2CC}
-table tr td.redwidget{background:url("bg_sunorange.gif") repeat-x left top #E76F00}
-td.columncaption,th.columncaption{text-align:left;background:#C3CCD3;font-weight:bold;padding:3px}
-td.columncaption2,th.columncaption2{text-align:left;background:#CCC;font-weight:bold}
-td.columncaption3,th.columncaption3{color:#FFF;background:#666;font-weight:bold}
-td.columncaption4,th.columncaption4{background:#CCC;font-weight:bold}
-td.columncaption5,th.columncaption5{background:#CCC}
-table[bgcolor="#666699"],
-td[bgcolor="#666699"],
-table[bgcolor="#666699"] td.tablecaption,
-table[bgcolor="#000000"] td.tablecaption,
-table.black td.tablecaption,
-table.dkblue td.tablecaption,
-td.tablecaption,th.tablecaption{background:#35556B}
-td.tablecaption2,th.tablecaption2{background:#000}
-td.tablecaption3,th.tablecaption3{background:#6579A6}
-td.tablecaption4,th.tablecaption4{background:#B3B3B3}
-td.tablecaption5,th.tablecaption5{background:#993300}
-td.tablecaption6,th.tablecaption6{background:#C00}
-td.tablecaption7,th.tablecaption7{background:#A3B8CB}
-td.tablecaption div.headerpadding{background:url("a2_corner_tr.gif") no-repeat right top;padding:6px 8px 4px 15px}
-tr td.tablecaption,table tr.dkgrey td.tablecaption{background:url("bg_titlebar.gif") no-repeat left top}
-td.tablecaption2 div.headerpadding{background:url("a2_corner_tr.gif") no-repeat right top;padding:6px 8px 4px 15px}
-tr td.tablecaption2,table tr.dkgrey td.tablecaption2{background:url("bg_titlebar.gif") no-repeat left top}
-td.vatop,th.vatop,tr.vatop td,tr.vatop th,table.vatop td,table.vatop th,div.vatop{vertical-align:top}
-td.vamiddle,th.vamiddle,tr.vamiddle td,tr.vamiddle th,table.vamiddle td,table.vamiddle th,div.vamiddle{vertical-align:middle}
-td.vabottom,th.vabottom,tr.vabottom td,tr.vabottom th,table.vabottom td,table.vabottom th,div.vabottom{vertical-align:bottom}
-tr td.tablecaption,tr td.tablecaption2,tr td.tablecaption3{padding:0px;vertical-align:top}
-.d7v9 .tablecaption2{background:#A4B8CB;color:#fff}
-.d7v9 .tablecaption2 .headerpadding{background:#A4B8CB;padding-left:11px}
-
-/* table colors */
-table.dkblue{background:#35556B}
-.dkblue span.rightarrowblue{color:#fff}
-td.dkblue,th.dkblue,tr.dkblue td,tr.dkblue th,table tr td.dkblue,table tr th.dkblue{background:#35556B;color:#FFF}
-div.dkgrey1,table.dkgrey1,td.dkgrey1,th.dkgrey1,tr.dkgrey1 td,tr.dkgrey1 th,table tr td.dkgrey1,table tr th.dkgrey1{background:#BBB}
-table.grey1,td.grey1,th.grey1,tr.grey1 td,tr.grey1 th,table tr td.grey1,table tr th.grey1{background:#EEE}
-table.grey2,td.grey2,th.grey2,tr.grey2 td,tr.grey2 th,table tr td.grey2,table tr th.grey2{background:#FDFDFD}
-tr td.tablecaption2 div.headerpadding a,td.tablecaption2{background-color:transparent}
-table.yellow1,td.yellow1,th.yellow1,tr.yellow1 td,tr.yellow1 th,table tr td.yellow1,table tr th.yellow1{background:#EFEFEF}
-
-/* d1 & d2 */
-.d1,.d2{margin-bottom:10px}
-.d1,.d2,.d1 .dkgrey1,.d1 .dkgrey1 .white1,.d2 .dkgrey1,.d2 .dkgrey1 .white1{background:#EEE}
-.d1 td.grey3 span.sp5{border-bottom:#FFF solid 1px;display:block;height:1px;overflow:hidden}
-.d1 .grey1,.d2 .grey1{background:transparent}
-.d1 table.vatop,.d2 table.vatop,.d1 h5,.d2 h5{margin:0px 0px 0px 5px}
-.d2 table.dkgrey1 table.vatop{margin:0px}
-.d1 .gwpadding1 .navtitle,.d2 .gwpadding1 .navtitle,.d1 .sectiontitle1,.d2 .sectiontitle1,.d1 .sectiontitle2,.d2 .sectiontitle2{padding-left:5px}
-.d1 .gwpadding1,.d2 .gwpadding1{padding-left:20px}
-td.sectiontitle2{padding-top:2px}
-table.dkgrey1 table tr td.tablecaption2{background:url("bg_sunblue.gif") repeat-x}
-table.dkgrey1 table tr td.tablecaption2 div.headerpadding{background:transparent}
-table.dkgrey1 table.white1 tr td div.pad10{padding:0px 10px}
-td.tablecaption2 + td img[width="10"]{width:10px;height:24px;background:#FFF}
-td.tablecaption2 + td.black{background:#fff;color:#000}
-table.dkgrey1 table tr td.tablecaption3{background:url("bg_sunblue.gif")}
-table.dkgrey1 table tr td.tablecaption3 div.headerpadding{background:transparent}
-table.dkgrey1 table.white1 tr td div.pad10{padding:0px 10px}
-td.tablecaption3 div.headerpadding,td.tablecaption3 div.headerpadding2{background:url("a2_corner_tr.gif") no-repeat right top;padding:6px 8px 4px 15px}
-tr td.tablecaption3,table tr.dkgrey td.tablecaption3{background:url("bg_titlebar.gif") no-repeat left top}
-table.dkgrey1 table tr td.tablecaption{background:url("bg_sunblue.gif")}
-table.dkgrey1 table tr td.tablecaption div.headerpadding{background:transparent}
-table.dkgrey1 table.white1 tr td div.pad10{padding:0px 10px}
-td.medgrey div.headerpadding{padding:4px 8px 4px 15px}
-
-/* d7 */
-.d7 div.cornerBL{background:url("generic_bl.gif") no-repeat bottom left #EEE;border-top:none}
-.d7 div.cornerBR{background:url("generic_br.gif") no-repeat bottom right;padding:10px 6px}
-.d7 p.intro{font-size:13px;color:#666;font-weight:bold;margin-top:0px}
-.d7 hr.light,.d7 hr,.d7v4 .g2v3 hr,.d7v4 .g2v4 hr,.d7v4 .g2v5 hr,.d7v9 .g2v3 hr,.d7v9 .g2v4 hr,.d7v9 .g2v5 hr{background:#CCC;color:#CCC;height:2px;padding:0px;border-left:0px;border-right:0px;border-top:0px;border-bottom:1px #FFF solid;margin-bottom:10px}
-.d7v0{border-bottom:#507c9a solid 2px}
-.d7v0 .skip{height:0px;width:0px;overflow:hidden}
-.d7v0 td.suntab div{border-bottom:#FFF solid 2px;border-right:#FFF solid 2px}
-.d7v0 td.suntabactive div{border-right:#FFF solid 2px}
-.d7v1 div.suntabsubrow{padding:5px 7px 5px 4px}
-.d7v1 span{border-right:#FFF solid 1px;padding-right:5px;padding-left:3px}
-.d7v1 span.lastitem{border-right:#507c9a solid 0px;padding-right:5px;padding-left:3px}
-.d7v2{border-bottom:#507c9a solid 2px;border-left:#507c9a solid 2px;border-right:#507c9a solid 2px;padding:6px 6px 10px 6px}
-.d7v4{background:#FFF;margin:0px;padding:0px}
-.d7v6{padding:3px 0px}
-.d7v7{padding:0px 0px 4px 0px;margin-bottom:4px;border-bottom:#CCC 2px solid;color:#696969}
-.d7v7 b{color:#E76F00}
-.d7v7 div{padding-top:3px}
-.d7v8 .suntabsubsubrow div{padding:3px 0px 3px 10px}
-.d7v8 .suntabsubsubrow form{padding:0px 0px 4px 0px;display:block}
-.d7v8 a:visited{color:#3E6B8A}
-.d7v8{background:#CCDAE3;border-top:1px #fff solid;padding:6px 6px 6px 5px}
-.d7v8 b{color:#000}
-.d7v8 span{border-right:#507c9a solid 1px;padding-right:5px;padding-left:3px}
-.d7v8 span.lastitem,.d7v8 span.remove{border-right:0px;padding-right:5px;padding-left:3px}
-.d7v9 div.cornerBR{padding:10px 22px 22px 22px}
-.d7v10{background:#CCDAE3;border-top:1px #fff solid}
-.d7v10 td{padding:8px 4px 5px 9px}
-.d7v10 ul.bluearrows li.currentpg{font-weight:bold;list-style-image:url("a.gif");background:url("ar_single_black_bold.gif") no-repeat left top}
-td.suntabactive,table.suntabbg,td.suntabbg,th.suntabbg,tr.suntabbg td,tr.suntabbg th,table tr td.suntabbg,table tr th.suntabbg{background:#507c9a}
-td.suntabactive{background:#507c9a url("bg_titlebar.gif") no-repeat left top;border-right:1px solid #FFF;padding:0px}
-td.suntabactive div{background:url("a2_corner_tr.gif") no-repeat right top;padding:9px 7px 5px 7px}
-td.suntab{background:#CCDAE3 url("d7_tab_bg.gif") repeat-x;border-right:1px solid #FFF;border-top:3px solid #FFF}
-td.suntab div{background:url("corner_navblue_tr.gif") no-repeat right top;padding:9px 7px 5px 7px}
-td.suntab div{padding:6px 7px 3px 7px}
-td.suntab div a:visited{color:#35556B}
-div.suntabsubrow{padding:9px 7px 5px 7px;background:#507c9a}
-div.suntabsubrow,div.suntabsubrow span,td.suntabactive div{font-weight:bold;color:#FFF}
-div.suntabsubrow a{font-weight:normal;color:#CCDAE3}
-div.suntabsubrow span a:visited,div.suntabsubrow span a:visited b,div.suntabsubrow span a b{color:#FFF}
-
-/* e1 */
-.e1{margin-bottom:10px}
-.e1 .contact{margin-bottom:8px}
-.e1 a.small{color:#FFD55C}
-
-/* e2 */
-.e2{background:url("bg_navgreen.gif") repeat-x left bottom #C7CE46;margin-bottom:10px}
-.e2 table.navblue{background:url("generic_tr.gif") no-repeat top right}
-.e2 table.navblue tr td table{margin:8px 6px 8px 6px}
-.e2 table.navblue tr td table:first-child,.e2 table.navblue tr td table{background:transparent}
-* html .e2 table.navblue tr td table{background:transparent;border-top:0px}
-.e2 table.navblue .navtitle,.e2 table.navblue .rightarrowblue,.e2 table.navblue table:first-child,.e2 span.rightarrowblue{padding-left:0px}
-
-/* e4 */
-.e4v2 .pad{padding:7px}
-
-/* e5 */
-.e5{background:url("bg_navgreen.gif") repeat-x left bottom #C1C933;margin-bottom:10px}
-.e5 table.blue1,.e5 table.white1{background:transparent}
-.e5 table.blue1{background:url("generic_tr.gif") no-repeat top right;border-top:none}
-.e5 table.white1{background:url("generic_tl.gif") no-repeat top left;padding:0px}
-.e5 table.blue1 table.white1{border:none}
-
-/* e8 */
-.e8v0{background:url("bg_sunorange.gif") repeat-x left bottom #E76F00;margin-bottom:10px;width:170px}
-.e8v1{background:url("bg_dksunblue.gif") repeat-x left bottom #35556B;margin-bottom:10px;width:170px}
-.e8v0 div.cornerBL,.e8v1 div.cornerBL{width:170px;height:8px;background:url("generic_bl.gif") no-repeat bottom left;padding:0px}
-.e8v0 div.cornerBR,.e8v1 div.cornerBR{width:170px;height:8px;background:url("generic_br.gif") no-repeat bottom right;padding:0px}
-.e8v0 div.title{color:#FFF;font-weight:bold;padding:8px 8px 2px 8px}
-.e8v0 div.copy{color:#000;padding:2px 8px 4px 8px}
-.e8v1 div.copy a:link,.e8v1 div.copy a:visited{color:#FFF}
-.e8v1 div.title{color:#ED9B09;font-weight:bold;padding:8px 8px 2px 8px}
-.e8v1 div.copy{color:#FFF;padding:2px 8px 4px 8px}
-
-/* e9 */
-.e9v0{background:url("bg_sunorange.gif") repeat-x left bottom #E76F00;margin-bottom:10px;width:170px}
-.e9v1{background:url("bg_dksunblue.gif") repeat-x left bottom #35556B;margin-bottom:10px;width:170px}
-.e9 div.cornerBL{width:170px;height:8px;background:url("generic_bl.gif") no-repeat bottom left;padding:0px}
-.e9 div.cornerBR{width:170px;height:8px;background:url("generic_br.gif") no-repeat bottom right;padding:0px}
-.e9 div.cornerTL{width:170px;height:8px;background:url("generic_tl.gif") no-repeat top left;padding:0px}
-.e9 div.cornerTR{width:170px;height:8px;background:url("generic_tr.gif") no-repeat top right;padding:0px}
-.e9v0 div.title{color:#FFF;font-weight:bold;padding:2px 8px 2px 8px}
-.e9v0 div.copy{color:#000;padding:2px 8px 2px 8px}
-.e9v1 div.copy a:link,.e9v1 div.copy a:visited{color:#FFF}
-.e9v1 div.title{color:#ED9B09;font-weight:bold;padding:2px 8px 2px 8px}
-.e9v1 div.copy{color:#FFF;padding:2px 8px 4px 8px}
-
-/* e12 */
-.e12v0{margin-bottom:10px}
-
-/* e13 */
-.e13{background:#a3b8cb;margin-bottom:10px;width:170px}
-.e13 div.cornerBL{height:8px;background:url("generic_bl.gif") no-repeat bottom left;padding:0px}
-.e13 div.cornerBR{height:8px;background:url("generic_br.gif") no-repeat bottom right;padding:0px}
-.e13 div.cornerTL{height:8px;background:url("generic_tl.gif") no-repeat top left;padding:0px}
-.e13 div.cornerTR{height:8px;background:url("generic_tr.gif") no-repeat top right;padding:0px}
-.e13 div.pad{margin:0px 10px}
-.e13 h3{margin:0px;padding:0px;float:left}
-.e13 img.popup{margin:0;padding:0;float:right}
-.e13 img{margin:6px 0px 0px 0px;display:block}
-
-/* e14 */
-.e14{background:url("bg_lightyellow.gif") repeat-x left bottom #F9DD9C;margin-bottom:10px;width:170px}
-.e14 div.cornerBL{height:8px;background:url("generic_bl.gif") no-repeat bottom left;margin-top:5px}
-.e14 div.cornerBR{height:8px;background:url("generic_br.gif") no-repeat bottom right}
-.e14 div.cornerTL{height:8px;background:url("generic_tl.gif") no-repeat top left}
-.e14 div.cornerTR{height:8px;background:url("generic_tr.gif") no-repeat top right}
-.e14 div.pad{padding:0px 8px 5px 10px}
-.e14 div.small{font-weight:bold;margin:0px 0px 5px 0px;color:#434343;line-height:1.4em}
-.e14v1 a{font-weight:bold}
-.e14v1 div.bluearrows{margin:5px 0px 3px 0px}
-
-/* e15 */
-.e15{background:url("bg_navblue.gif") repeat-x bottom left #DDE6EC;margin-bottom:10px;width:170px}
-.e15 div.cornerTL{height:8px;background:url("generic_tl.gif") no-repeat top left}
-.e15 div.cornerTR{height:8px;background:url("generic_tr.gif") no-repeat top right}
-.e15 div.pad{padding:0px 8px 3px 10px}
-.e15 h5{margin-top:7px;color:#444}
-.e15 div.bluearrows{margin:5px 0px 3px 0px}
-.e15v1 a{font-weight:bold}
-
-/* g2 */
-.g2v4 .number,.g2v4 span.question{text-align:right;width:20px;float:left}
-.g2v4 span.question{font-weight:bold}
-.g2v4 div.question{text-align:left;margin:0px 0px 8px 45px;font-weight:bold;padding-bottom:0px}
-.g2v4 span.answer{text-align:right;width:40px;float:left;font-weight:bold}
-.g2v4 div.answer{text-align:left;margin:0px 0px 11px 45px;padding-bottom:0px}
-.g2v3 hr,.g2v4 hr,.g2v5 hr{background:#E3E3E3;color:#E3E3E3;height:2px;padding:0px;border:0px}
-.g2v4 h3{margin-bottom:5px;margin-top:24px}
-.g2v4 img[src*="ic_ar_up.gif"]{padding-left:32px}
-
-/* g3 */
-div.g3v3 ol{margin-top:4px}
-.d7v9 div.g3v3 .tablecaption2{background:#EEE;color:#000}
-.d7v9 div.g3v3 .tablecaption2 .headerpadding{background:#EEE;padding-left:1px;font-size:15px}
-.d7v9 div.g3v3 table.dkgrey1{background:#EEE}
-.d7v9 div.g3v3 table.dkgrey1 tr.grey1 td{background:#EEE}
-
-/* g9 */
-div.g9{background:url("bg_sunblue.gif") repeat-x left top #5382A1;margin:5px 10px 15px 10px}
-.g9 div.cornerTL{width:100%;background:url("a2_corner_tl.gif") no-repeat top left;padding:0px}
-.g9 div.cornerTR{width:100%;background:url("a2_corner_tr.gif") no-repeat top right;padding:0px}
-.g9 div.cornerBL{width:100%;background:url("a2_corner_bl.gif") no-repeat bottom left;padding:0px}
-.g9 div.cornerBR{width:100%;background:url("a2_corner_br.gif") no-repeat bottom right;padding:0px}
-.g9 table{height:40px}
-.g9 td.ques div{color:#FFF;padding:3px 5px 3px 20px}
-.g9 td.answ div{padding:3px 15px 3px 5px}
-.g9 td.sbmt div{margin:3px 20px 3px 5px}
-
-/* g12 */
-.g12{padding-bottom:10px}
-.g12 .pad{padding-top:10px}
-
-/* g14 */
-.g14v8{background:url("ar_lg_orange.gif") no-repeat top left;padding-left:18px}
-.g14v8 h5{margin:0px;padding-top:1px}
-.g14v9{margin-bottom:0px}
-
-/* g15 */
-.g15v2{background:#666}
-.g15v2 table th{background:#a3b8cb;color:#fff}
-.g15v2 table td{background:#fff}
-
-/* g17 */
-.g17{padding:10px}
-.col1 .g17,.col2 .g17{padding:0px}
-.g17 p{color:#666}
-
-/* g18 */
-.g18v0 .col1,.g18v1 .col1{padding-right:11px}
-.g18v0 .col2,.g18v1 .col2{padding-left:11px}
-.g18v0 .col2{width:50%}
-.g18v1 .col2{width:60%}
-
-/* g19 */
-.g19v0,.g19v2,.g19v4,.g19v6{margin:14px 10px 0px 0px;float:left}
-.g19v1,.g19v3,.g19v5,.g19v7{margin:14px 0px 0px 10px;float:right}
-.g19v8 table,.g19v9 table{margin-left:auto;margin-right:auto;margin-top:14px;margin-bottom:0px}
-.g19 img{position:relative;z-index:4;top:-7px;left:0px}
-.g19 div.insideTL{background:url("TL_fff.gif") no-repeat top left;height:7px;width:100%;padding:0px;position:relative;z-index:5;top:0px;left:0px}
-.g19 div.insideTR{background:url("TR_fff.gif") no-repeat top right;height:7px;width:100%;padding:0px;position:relative;z-index:5;top:0px;left:0px}
-.g19 div.insideBL{background:url("BL_fff.gif") no-repeat bottom left;height:19px;width:100%;padding:0px;position:relative;z-index:5;top:-26px;left:0px;margin-bottom:-26px}
-.g19 div.insideBR{background:url("BR_fff.gif") no-repeat bottom right;height:19px;width:100%;padding:0px;position:relative;z-index:5;top:0px;left:0px}
-.g19 span.zoomaction div.insideBL{background:url("BL_fff_zoom.gif") no-repeat bottom left}
-.g19 span.zoomaction:hover div.insideBL{background:url("BL_fff_zoomed.gif") no-repeat bottom left}
-.d7 div.cornerBL .g19 .insideTL,.pc1 div.cornerBL .g19 .insideTL{background:url("TL_eee.gif") no-repeat top left}
-.d7 div.cornerBL .g19 .insideTR,.pc1 div.cornerBL .g19 .insideTR{background:url("TR_eee.gif") no-repeat top right}
-.d7 div.cornerBL .g19 .insideBL,.pc1 div.cornerBL .g19 .insideBL{background:url("BL_eee.gif") no-repeat bottom left}
-.d7 div.cornerBL .g19 .insideBR,.pc1 div.cornerBL .g19 .insideBR{background:url("BR_eee.gif") no-repeat bottom right}
-.d7 div.cornerBL .g19 span.zoomaction div.insideBL,.pc1 div.cornerBL .g19 span.zoomaction div.insideBL{background:url("BL_eee_zoom.gif") no-repeat bottom left}
-.d7 div.cornerBL .g19 span.zoomaction:hover div.insideBL,.pc1 div.cornerBL .g19 span.zoomaction:hover div.insideBL{background:url("BL_eee_zoomed.gif") no-repeat bottom left}
-.g19v4 div.insideBL,.g19v4 div.insideBR,.g19v4 div.insideTL,.g19v4 div.insideTR,
-.g19v5 div.insideBL,.g19v5 div.insideBR,.g19v5 div.insideTL,.g19v5 div.insideTR,
-.g19v6 div.insideBL,.g19v6 div.insideBR,.g19v6 div.insideTL,.g19v6 div.insideTR,
-.g19v7 div.insideBL,.g19v7 div.insideBR,.g19v7 div.insideTL,.g19v7 div.insideTR,
-.g19v9 div.insideBL,.g19v9 div.insideBR,.g19v9 div.insideTL,.g19v9 div.insideTR{background:none !important}
-.g19v6 .g19 span.zoomaction div.insideBL,.g19v7 .g19 span.zoomaction div.insideBL{background:url("BL_zoom.gif") no-repeat bottom left !important}
-.g19v6 .g19 span.zoomaction:hover div.insideBL,.g19v7 .g19 span.zoomaction:hover div.insideBL{background:url("BL_zoomed.gif") no-repeat bottom left !important}
-/* ie/pc */
-.g19 img{_top:-22px;_margin-bottom:-40px}
-.g19 div.insideBL{_top:-4px;_margin-bottom:0px}
-.g19 div.insideBR{_top:0px}
-.g19 div.insideTL{_top:-7px}
-.g19 div.insideTR{_top:0px}
-
-/* g20 */
-.g20v0 .g20,.g20v2 .g20,.g20v4 .g20,.g20v6 .g20{margin:14px 10px 10px 0px;float:left;position:relative}
-.g20v1 .g20,.g20v3 .g20,.g20v5 .g20,.g20v7 .g20{margin:14px 0px 10px 10px;float:right;position:relative}
-.g20v8 .g20,.g20v9 .g20{margin-left:auto;margin-right:auto;margin-top:14px;margin-bottom:0px;position:relative}
-.g20 td{background:#c8c8c8;padding:0px}
-.g20 .thumb{padding:0px 8px}
-.g20 .thumb img{position:relative;z-index:3;top:-6px;left:0px}
-.g20 .small{padding:1px 8px 9px 8px;text-align:right;color:#222;position:relative;top:-4px}
-.g20 div.outsideTL{width:100%;background:url("TL_fff.gif") no-repeat top left;position:relative;height:7px;padding:0px}
-.g20 div.outsideTR{width:100%;background:url("TR_fff.gif") no-repeat top right;position:relative;height:7px;padding:0px}
-.g20 div.outsideBL{width:100%;background:url("BL_fff.gif") no-repeat bottom left;position:relative;height:7px;padding:0px}
-.g20 div.outsideBR{width:100%;background:url("BR_fff.gif") no-repeat bottom right;position:relative;height:7px;padding:0px}
-.g20 div.insideTL{width:100%;background:url("TL_c8c8c8.gif") no-repeat top left;height:7px;padding:0px;position:relative;z-index:7;top:1px;left:0px}
-.g20 div.insideTR{width:100%;background:url("TR_c8c8c8.gif") no-repeat top right;height:7px;padding:0px;position:relative;z-index:7;top:0px;left:0px}
-.g20 div.insideBL{width:100%;background:url("BL_c8c8c8.gif") no-repeat bottom left;height:19px;padding:0px;position:relative;z-index:7;top:-25px;left:0px;margin-bottom:-12px}
-.g20 div.insideBR{width:100%;background:url("BR_c8c8c8.gif") no-repeat bottom right;height:19px;padding:0px;position:relative;z-index:7;top:0px;left:0px}
-.d7 div.cornerBL .g20 div.outsideTL,.pc1 div.cornerBL .g20 div.outsideTL{background:url("TL_eee.gif") no-repeat top left}
-.d7 div.cornerBL .g20 div.outsideTR,.pc1 div.cornerBL .g20 div.outsideTR{background:url("TR_eee.gif") no-repeat top right}
-.d7 div.cornerBL .g20 div.outsideBL,.pc1 div.cornerBL .g20 div.outsideBL{background:url("BL_eee.gif") no-repeat bottom left}
-.d7 div.cornerBL .g20 div.outsideBR,.pc1 div.cornerBL .g20 div.outsideBR{background:url("BR_eee.gif") no-repeat bottom right}
-.g20v4 div.insideBL,.g20v4 div.insideBR,.g20v4 div.insideTL,.g20v4 div.insideTR,
-.g20v5 div.insideBL,.g20v5 div.insideBR,.g20v5 div.insideTL,.g20v5 div.insideTR,
-.g20v6 div.insideBL,.g20v6 div.insideBR,.g20v6 div.insideTL,.g20v6 div.insideTR,
-.g20v7 div.insideBL,.g20v7 div.insideBR,.g20v7 div.insideTL,.g20v7 div.insideTR,
-.g20v9 div.insideBL,.g20v9 div.insideBR,.g20v9 div.insideTL,.g20v9 div.insideTR{background:none !important}
-.g20 td.thumb span.zoomaction div.insideBL{background:url("BL_c8c8c8_zoom.gif") no-repeat bottom left !important}
-.g20 td.thumb span.zoomaction:hover div.insideBL{background:url("BL_c8c8c8_zoomed.gif") no-repeat bottom left !important}
-.g20v6 .g20 td.thumb span.zoomaction div.insideBL,.g20v7 .g20 td.thumb span.zoomaction div.insideBL{background:url("BL_zoom.gif") no-repeat bottom left !important}
-.g20v6 .g20 td.thumb span.zoomaction:hover div.insideBL,.g20v7 .g20 td.thumb span.zoomaction:hover div.insideBL{background:url("BL_zoomed.gif") no-repeat bottom left !important}
-/* ie/pc */
-table.g20{_margin-top:19px}
-.g20 .small{_top:12px}
-.g20 .thumb img{_top:-22px;_margin-bottom:-40px}
-.g20 td.thumb div.insideBL{_top:-4px}
-.g20 td.thumb div.insideBR{_top:0px}
-.g20 td.thumb div.insideTL{_top:-7px}
-.g20 td.thumb div.insideTR{_top:0px}
-
-/* g21 */
-.g21{background:#c8c8c8}
-.g21 .quote{padding:0px 8px 0px 8px;font-size:15px;font-weight:bold;color:#fff;font-style:oblique}
-.g21 .quote b{color:#eee}
-.g21 .small{color:#222;text-align:right;padding:4px 8px 0px 8px}
-.g21 div.insideTL{background:url("TL_fff.gif") no-repeat top left;height:7px;width:100%;padding:0px}
-.g21 div.insideTR{background:url("TR_fff.gif") no-repeat top right;height:7px;width:100%;padding:0px}
-.g21 div.insideBL{background:url("BL_fff.gif") no-repeat bottom left;height:7px;width:100%;padding:0px}
-.g21 div.insideBR{background:url("BR_fff.gif") no-repeat bottom right;height:7px;width:100%;padding:0px}
-.g21 img{position:relative;z-index:3;top:-7px;left:0px}
-.g21v0{margin:0px}
-.g21v1{margin:0px 10px 10px 0px;float:left;width:290px}
-.g21v2{margin:0px 0px 10px 10px;float:right;width:290px}
-.g21v3{margin:10px 0px}
-.g21v3 .statement{padding:0px 12px;font-size:17px;font-weight:bold;color:#fff;text-align:center}
-.d7 div.cornerBL .g21 div.insideTL,.pc1 div.cornerBL .g21 div.insideTL{width:100%;background:url("TL_eee.gif") no-repeat top left;padding:0px}
-.d7 div.cornerBL .g21 div.insideTR,.pc1 div.cornerBL .g21 div.insideTR{width:100%;background:url("TR_eee.gif") no-repeat top right;padding:0px}
-.d7 div.cornerBL .g21 div.insideBL,.pc1 div.cornerBL .g21 div.insideBL{width:100%;background:url("BL_eee.gif") no-repeat bottom left;padding:0px}
-.d7 div.cornerBL .g21 div.insideBR,.pc1 div.cornerBL .g21 div.insideBR{width:100%;background:url("BR_eee.gif") no-repeat bottom right;padding:0px}
-
-/* g22 */
-.g22 .small{color:#666}
-.g22v1{text-align:right}
-
-/* j1 */
-.j1v0 p{color:#666;font-weight:bold;margin-top:0px}
-.j1v1{margin-bottom:15px}
-.j1v1 .iconpdf{padding:5px 0px}
-.j1v2{height:80px}
-.j1{background:url("bg_white_to_grey.gif") repeat-x left top #fff}
-.j1 div.cornerBR{width:100%;background:url("generic_br.gif") no-repeat bottom right;padding:0px}
-.j1 a.morelink{font-weight:bold;white-space:nowrap}
-.j1 a.title{font-weight:bold;font-size:14px}
-.j1 div.copy{padding-top:4px}
-.j1 div.plft{background:url("ar_lg_orange.gif") no-repeat top left;padding-bottom:0px}
-.j1 .j1v2{color:#000}
-.j1 a:visited,.j1 a:link{color:#3E6B8A}
-.j1v3>div{padding-left:10px}
-
-/* l0 */
-.l0v0,.l0v1{margin:5px 10px 0px 10px;text-align:center}
-td .l0v0,td .l0v1{margin:5px 0px 0px 0px;text-align:center}
-.l0{padding:0px;width:780px;height:170px;position:relative;left:0px;top:0px;margin-left:auto;margin-right:auto;margin-top:10px}
-.l0items img{display:block;width:780px;height:170px}
-.l0items{position:absolute;top:0px;left:0px;z-index:2;opacity:.1;filter:alpha(opacity=1);-moz-opacity:.1}
-div#l0item1{opacity:1;filter:alpha(opacity=100);-moz-opacity:1;z-index:2}
-
-/* l1 */
-.l1v0{height:80px}
-.l1{background:url("bg_white_to_grey.gif") repeat-x left top #fff}
-.l1 div.cornerBR{width:100%;background:url("generic_br.gif") no-repeat bottom right;padding:0px}
-.l1 a.morelink{font-weight:bold;white-space:nowrap}
-.l1 a.title{font-weight:bold;font-size:14px}
-.l1 div.copy{padding-top:4px}
-.l1 div.plft{background:url("ar_lg_orange.gif") no-repeat top left;padding-bottom:0px}
-.l1 .l1v0{color:#000}
-.l1 a:visited,.l1 a:link{color:#3E6B8A}
-
-/* l2 */
-.l2 .l2img{float:left;height:88px;width:100px}
-.l2 .l2title{padding:10px 0px 8px 4px;font-size:15px;font-weight:bold}
-.l2 a.morelink{font-weight:bold;white-space:nowrap}
-.l2 a.title{font-weight:bold;font-size:14px}
-.l2 div.copy{padding-top:4px}
-.l2 div.plft{background:url("ar_lg_orange.gif") no-repeat top left;padding-left:18px;margin-left:106px}
-.l2v0{margin-top:15px}
-
-/* l3 */
-.l3{margin-top:15px}
-.l3 .l3img{float:left;height:88px;width:100px}
-.l3 a.morelink{font-weight:bold;white-space:nowrap}
-.l3 div.copy{padding-top:4px}
-.l3 div.plft{margin-left:113px}
-.l3 h5{margin-top:0px}
-
-/* pc0 */
-.pc0{margin-bottom:16px}
-.pc0 h3{margin-bottom:5px}
-.pc0 p{margin-bottom:4px}
-.pc0 .bluearrows,.pc0 .pad{margin-top:5px}
-.pc0v0 ul li{margin:0px;padding:0px 0px 6px 10px;list-style:none;background: url("ul_bullet.gif") no-repeat 0px .4em}
-.pc0v0 ul{margin:0px;padding:0px}
-.pc0v0 h3{margin-bottom:6px}
-.pc0v1 img{margin:6px 0px}
-.pc0v10 p{margin-top:6px}
-.pc0v10 img{margin:0px 8px 8px 0px;padding:0px;float:left}
-.pc0v5 table tr td img{margin:0px 15px 0px 10px}
-.pc0v8 img{display:block;margin:0px;padding:0px}
-.pc0v9 span.bluearrows{padding-right:5px}
-.pc0v9{margin-left:82px;min-height:85px}
-.vidthumb{text-align:center;width:124px;margin-top:8px}
-.vidthumb div{padding:0px 5px;background:#a5b8c9}
-.vidthumb img,.vidthumb a{display:block;margin:0px;padding:0px}
-
-/* pc1 */
-.pc1 div.cornerBL{background:url("generic_bl.gif") no-repeat bottom left #EEE;border-top:none}
-.pc1 div.cornerBR{background:url("generic_br.gif") no-repeat bottom right;padding:10px 22px 22px 22px}
-.pc1 div.cornerTL{background:url("a2_corner_tl.gif") no-repeat top left}
-.pc1 div.cornerTR{background:url("a2_corner_tr.gif") no-repeat top right;padding:5px}
-.pc1 .title{color:#FFF;padding-left:17px;font-weight:bold}
-.pc1 p.intro{font-size:13px;color:#666;font-weight:bold;margin-top:10px}
-.pc1v0{background:url("bg_sunblue.gif") repeat-x top left}
-
-/* pc2 */
-.pc2,.pc2 ul{margin:0px;padding:0px}
-.pc2 table{margin:0px;padding:0px;background:#fff;text-align:left;clear:both}
-.pc2 th{margin:0px;padding:8px 0px 8px 13px;background:#a3b8cb;color:#fff;font-weight:bold;vertical-align:top}
-.pc2 td.tcell,.pc2 td.intro{margin:0px;padding:8px 13px 8px 13px;font-weight:bold;vertical-align:top;color:#000}
-.pc2 td.tcell{width:220px}
-.pc2 td.dcell{margin:0px;padding:8px 16px 8px 0px;font-weight:normal;vertical-align:top;width:335px}
-.pc2 hr{margin:0px 13px 0px 13px;padding:0px;color:#c5d5a9;background:#c5d5a9;border-bottom:1px solid #c5d5a9;border-top:0px;height:1px !important}
-.pc2v3 table tr th{background:url("bg_sunblue.gif") repeat-x top left;color:#fff}
-
-/* pn0 */
-div.pn0,div.pn0 p{color:#000}
-.pn0v6 a{padding:0px 0px 0px 20px}
-.pn0v6 div a{padding:0px}
-.pn0v0,.pn0v1,.pn0v2,.pn0v3,.pn0v4 div,.pn0v7 div,.pn0v6 div,.pn0v5,.pn0v8{padding:1px 0px 0px 20px;background:url("ar_lg_orange.gif") no-repeat top left}
-.pn0v0 a,.pn0v1 a,.pn0v2 a,.pn0v3 a,.pn0v8 a,.pn0v4 div,.pn0v5 a.big,.pn0v6 div,.pn0v7 div,.pn0v6 a{display:block;margin-bottom:5px}
-.pn0v5 a,.pn0v10 a,.pn0v10 form,.pn0v11 a,.pn0v11 form,.pn0v9 a,.pn0v12 div a,.pn0v13 div a{display:block}
-.pn0v11 select,.pn0v10 input[type="text"]{width:65%}
-.pn0v11 select,.pn0v11 input,.pn0v11 form{margin-bottom:5px}
-.pn0v10 form,.pn0v9 p{padding:0px 0px 10px 0px}
-.pn0v2 b{display:block;padding:8px 0px 4px 0px}
-.pn0v2 a.big + b{display:block;padding:0px 0px 4px 0px}
-.pn0v3 p,.pn0v9 p,.pn0v8 p,.pn0v13 p{margin:4px 0px}
-.pn0v10 p.pn0v11 p{margin:8px 0px}
-.pn0v5 p{margin:4px 0px 10px 0px}
-.pn0 a.big,.pn0v4 a.big,.pn0v6 a.big,.pn0v2 b,.pn0v6 p,.pn0v9 p{font-weight:bold}
-.pn0v1,.pn0v2,.pn0v3,.pn0v5,.pn0v7{margin-left:79px}
-.pn0v9{margin-left:99px}
-.pn0v4{padding-left:79px}
-.pn0,.pn0v4,.pn0v6,.pn0v13 div{margin:10px 0px 25px 0px}
-.pn0v6 div.seelink{margin-top:15px;background:transparent}
-.pn0v12 ul li{list-style-type:none;margin:0px;padding:0px 0px 10px 0px}
-.pn0v12 ul{margin:0px}
-.pn0v12{margin:10px 0px}
-.pn0v12 div{padding:0px 0px 10px 0px}
-.pn0v14{text-align:right;padding:3px}
-* html .pn0v1,* html .pn0v2,* html .pn0v3,* html .pn0v5,* html .pn0v7.* html .pn0v9{height:85px}
-.pn0v1,.pn0v2,.pn0v3,.pn0v5,.pn0v7,.pn0v9{min-height:85px}
-
-/* pn1 */
-.pn1{background:url("bg_sunblue.gif") repeat-x top left}
-.pn1 div.cornerTL{background:url("a2_corner_tl.gif") no-repeat top left}
-.pn1 div.cornerTR{background:url("a2_corner_tr.gif") no-repeat top right;padding:5px}
-.pn1 .title{color:#FFF;padding-left:8px;font-weight:bold}
-.pn1 .seelink{padding-right:8px;float:right}
-.pn1 .seelink a:link,.pn1 .seelink a:visited{color:#FFF;font-weight:bold}
-
-/* pn2 */
-.pn2v0{width:100%;background:#EFEFEF;margin:0px 0px 10px 0px}
-.pn2v0 td.col1,.pn2v0 td.col2{padding:10px}
-.pn2v0 p.intro{margin:10px 0px 20px 0px}
-.pn2v0 td.col1{border-right:5px #EFEFEF solid}
-.pn2v0 td.col2{border-left:5px #EFEFEF solid}
-
-/* pn3 */
-.pn3v0,.pn3v1{margin:0px 0px 10px 0px}
-.pn3v0 .col1,.pn3v1 .col1,.pn3v0 .col2{background:#EFEFEF}
-.pn3v0 p.intro,.pn3v1 p.intro{margin:10px 0px 20px 0px}
-.pn3v0 div.pad,.pn3v1 div.pad{padding:10px}
-.pn3v0 td.col1,.pn3v1 td.col1{border-right:5px #fff solid}
-.pn3v0 td.col2{border-left:5px #fff solid}
-
-/* flash styles - referenced by displayFlash.js */
-.flashLoading{position:absolute;left:0;top:100;z-index:9;width:100%;text-align:center;visibility:visible}
-.flashBorder{position:relative;width:0;border:solid 1px #000;text-align :center}
-.flashsunblue,.flashsunorange,.flashsungreen,.flashsunyellow,.flashsundkblue,.flashsundkorange,.flashsundkgreen,.flashsundkyellow,.flashsunltblue,.flashsunltorange,.flashsunltgreen,.flashsunltyellow,.flashsunwhite,.flashsunblack,.flashsundkgray,.flashsunltgray,.flashsunadblue{position:absolute;left:0;top:0;z-index:10;width:100%;visibility:hidden}
-.flashsunblue{background:#5382A1}
-.flashsunorange{background:#E76F00}
-.flashsungreen{background:#B2BC00}
-.flashsunyellow{background:#FFC726}
-.flashsundkblue{background:#35556B}
-.flashsundkorange{background:#C06600}
-.flashsundkgreen{background:#7F7800}
-.flashsundkyellow{background:#C69200}
-.flashsunltblue{background:#A3B8CB}
-.flashsunltorange{background:#ED9B4F}
-.flashsunltgreen{background:#C5D5A9}
-.flashsunltyellow{background:#F8D583}
-.flashsunwhite{background:#FFF}
-.flashsunblack{background:#000}
-.flashsundkgray{background:#707277}
-.flashsunltgray{background:#BDBEC0}
-.flashsunadblue{background:#253C6E}
-
-/* print overwrite */
-@media print{
- table.dkgrey1 table tr td.tablecaption2,
- tr td.tablecaption2 div.headerpadding,
- div.a2 div.cornerTL,
- div.a2 div.cornerTR,
- div.a2 div.cornerBL,
- div.a2 div.cornerBR,
- div.vnv1 div.cornerTL,
- div.vnv1 div.cornerTR,
- div.vnv1 div.cornerBL,
- div.vnv1 div.cornerBR{background:none}
- .sunlogo,
- .a2search,
- .a2topiclinks,
- .vnv1sunlogo,
- .vnv1search,
- .vnv1topiclinks{display:none}
- div.a2,div.vnv1{height:90px}
-}
--- a/usr/src/cmd/installadm/docs/css/elements.css Wed Sep 29 16:37:00 2010 +0200
+++ /dev/null Thu Jan 01 00:00:00 1970 +0000
@@ -1,183 +0,0 @@
-/* Style properties for HTML elements based on the HTML 4.01 Specification.
-*/
-
-/* Section 7.5: The document body */
-body {
- padding: 1em;
- margin: 0;
- background-color: white;
- font-size: 75.01%; /* 12px [1] */
- line-height: 1.5em; /* 18px [2] */
- color: black;
- font-family: arial,helvetica,sans-serif
-}
-
-h1, h2, h3 {
- margin-bottom: 0.5em;
-}
-h1+p, h2+p, h3+p, h4+p, h5+p {
- margin-top: 0;
-}
-h1 {
- color: #5382A1;
-}
-h2 {
- font-size: 200%;
- color: #5382A1;
- line-height: 1em;
-}
-h3 {
- font-size: 150%;
-}
-h4 {
- font-size: 125%;
-}
-h5, h6 {
- font-size: 1em;
- margin-bottom: 0.2em;
- margin-top: 0.2em;
-}
-
-address {}
-
-/* Section 9: Text */
-em {}
-strong {}
-dfn {
- font-style: normal;
-}
-abbr[title], acronym[title], dfn[title] {
- cursor: help;
-}
-code, pre {
- color: black;
- font-family: Courier, monospace; /* [3] */
-}
-pre {
- background-color: #efefef;
- border: 1px solid #ccc;
- font-size: 100.01%;
- padding: 0.5em;
- overflow: hidden;
-}
-samp {}
-kbd {}
-var {}
-cite {}
-abbr {}
-acronym {}
-blockquote {}
-q {}
-sub {}
-sup {}
-p {}
-ins {}
-del {}
-
-/* Section 10: Lists */
-ul, ol {
- margin-left: 0;
- padding-left: 1.5em;
-}
-li {
- margin: 0;
- padding: 0;
-}
-dl {}
-dt {}
-dd {}
-
-/* Section 11: Tables */
-table {
- border-collapse: collapse;
- empty-cells: show;
- margin: 1em 0 1em 0;
-}
-caption {
- text-align: left;
- font-weight: bold;
-}
-thead {}
-tfoot {}
-tbody {}
-colgroup {}
-col {}
-th, td {
- padding: 0.3em 0.8em;
- border: 1px solid #999;
- vertical-align: top;
-}
-
-/* Section 12.2: The A element */
-a:link {}
-a:visited {}
-a:link:hover {} /* [4] */
-a:visited:hover {}
-a:active {}
-a:focus {}
-a:focus:hover {}
-
-a img {
- border-style: none;
-}
-
-
-/* Section 13: Objects, Images, and Applets */
-img {}
-object {}
-applet {}
-
-/* Section 15: Alignment, font styles, and horizontal rules */
-/* 15.2: Fonts "[...] their use is discouraged in favor of style sheets." */
-tt { font-family: Courier, monospace; }
-i {}
-b {}
-big {}
-small {}
-/* End of 15.2 */
-hr {}
-
-/* Section 16: Frames */
-iframe {}
-
-/* Section 17: Forms */
-form {}
-input {
- font-size: 0.95em;
-}
-textarea {
- font-size: 1.1em;
- overflow: auto;
-}
-textarea:focus,
-input[type=text]:focus,
-input[type=password]:focus,
-input[type=checkbox]:focus,
-input[type=radio]:focus,
-input[type=file]:focus {
- background-color: #efefff;
-}
-
-select,
-optgroup,
-option {
- font-size: 1em;
-}
-
-button {}
-button:focus {}
-select:focus {}
-label {}
-fieldset {}
-legend {}
-
-
-
-/*
- [1] All calculations are based on the assumption that 1em is 12px.
- [2] If you specify a font-size, also consider to specify a line-height property.
- [3] If you don't specify something other than monospace, mozilla will calculate
- its own font-size based on the user preferences.
- [4] "... prevents hover styles from being applied to non-hyperlink anchors."
- <http://devedge.netscape.com/viewsource/2003/arbitrary-hover/>
-*/
--- a/usr/src/cmd/installadm/docs/css/opensol.css Wed Sep 29 16:37:00 2010 +0200
+++ /dev/null Thu Jan 01 00:00:00 1970 +0000
@@ -1,84 +0,0 @@
-.Masthead{
- height: 60px;
-}
-
-.headerbar {
- width: 100%;
- height: 15px;
- background-image: url('../graphics/header_gradientpart.png');
- display: block;
- maring-top: 25px;
- maring-bottom: 25px;
-}
-
-.MastheadLogo
-{
- float: left;
- width: 300px;
-}
-
-.Title
-{
- float: right;
- margin-top: 30px;
- margin-right: 6px;
- color: rgb(116, 116, 116);
- font-family: arial,helvetica,sans-serif;
- font-size: 20px;
- font-weight: bold;
- text-align: right;
-}
-
-table.Layout
-{
- margin-top: 10px;
- padding-top: 0;
- padding-bottom: 0;
- height: auto;
-}
-
-.PageControls, .PageControls *
-{
- padding-top: 0;
- padding-bottom: 0;
- border: none;
- height: auto;
- line-height: auto;
-}
-
-.Layout td {
- border: none;
-}
-
-.MainContent td {
- padding: 0.3em 0.8em;
- border: 1px solid #999;
- vertical-align: top;
-}
-
-td.Navigation
-{
- border: none;
- border-right-width: 2px;
- border-right-style: solid;
- border-color: rgb(116, 116, 116);
- width: 200px;
-
-}
-
-
-div.embeddedtoc {margin: 2px; margin-top: 20px}
-p.toc {margin: 0px; margin-top: 6px;}
-p.level0 {margin-left:0px}
-p.level1 {margin-left:18px}
-p.level2 {margin-left:36px}
-p.level3 {margin-left:54px}
-p.level4 {margin-left:72px}
-p.level5 {margin-left:90px}
-p.tocsp {margin-top:6px}
-
-div.onpage {background-color: rgb(186, 186, 186); margin-top: 6px; margin-bottom: 6px; }
-.onpage a {color: #000000}
-
-
-a {text-decoration: none;}
--- a/usr/src/cmd/installadm/docs/customai.html Wed Sep 29 16:37:00 2010 +0200
+++ /dev/null Thu Jan 01 00:00:00 1970 +0000
@@ -1,759 +0,0 @@
-<!DOCTYPE HTML PUBLIC "-//W3C//DTD HTML 4.01 Transitional//EN" "http://www.w3.org/TR/html4/loose.dtd">
-<html lang="en-US">
-
-<!-- -->
-<head>
-<!-- GenHTML revision 23436-->
-<meta http-equiv="Content-type" content="text/html; charset=iso-8859-1">
-<title>How to Create and Use a Custom AI Manifest - OpenSolaris 2010.03 Automated Installer Guide</title>
-<meta name="robots" content="index,follow">
-<meta name="robots" content="index,follow">
-<meta name="date" content="2010-03-01">
-<meta name="collection" content="reference">
-<link rel="stylesheet" type="text/css" href="css/elements.css">
-<link rel="stylesheet" type="text/css" href="css/opensol.css">
-</head>
-
-<body>
-
-
-<div class="Masthead">
- <div class="MastheadLogo">
- <a href="http://www.opensolaris.com"><img border="0" src="graphics/opensolaris_logo_trans.png"></img></a>
- </div>
- <div class="Title">OpenSolaris 2010.03 Automated Installer Guide</div>
-</div>
-<div class="headerbar"></div>
-
-
-<table class="Layout" border="0" cellspacing="0" width="100%">
-<tbody>
-
- <tr valign="top" class="PageControls">
- <td></td>
- <td>
- <table width="100%">
- <tr>
- <td>
- <a href="manifest1.html">Previous</a>
- </td>
- <td align="right">
- <a href="customsc.html">Next</a>
- </td>
- </tr>
- </table>
- </td>
- </tr>
-
- <tr valign="top">
- <td class="Navigation" width="200px"><p class="toc level1"><a href="docinfo.html">Document Information</a></p>
-<p class="toc level1 tocsp"><a href="index.html">1. What's New For Automated Installations</a></p>
-<p class="toc level1 tocsp"><a href="intro.html">2. Introduction to the Automated Installer</a></p>
-<p class="toc level1 tocsp"><a href="tasks.html">3. Automated Network Install Task Map</a></p>
-<p class="toc level1 tocsp"><a href="bootable.html">4. Automated Installations That Boot From Media</a></p>
-<p class="toc level1 tocsp"><a href="setup.html">5. Set up an Automated Install Server</a></p>
-<p class="toc level1 tocsp"><a href="administer.html">6. How to Administer an Automated Install Server</a></p>
-<p class="toc level1 tocsp"><a href="client.html">7. How to Administer a Custom Install Client</a></p>
-<p class="toc level1 tocsp"><a href="manifest.html">8. How to Administer Manifest Files</a></p>
-<p class="toc level2"><a href="manifest1.html">Types of Manifests</a></p>
-<div id="scrolltoc" class="onpage">
-<p class="toc level2"><a href="">How to Create and Use a Custom AI Manifest</a></p>
-</div>
-<p class="toc level2"><a href="customsc.html">How to Create Custom SC Manifest Files</a></p>
-<p class="toc level2"><a href="criteria.html">How to Create and Use a Criteria Manifest</a></p>
-<p class="toc level2"><a href="associate.html">How to Assign Manifests to a Client</a></p>
-<p class="toc level1 tocsp"><a href="clients.html">9. How to Manage Client Installations</a></p>
-<p class="toc level1 tocsp"><a href="trouble.html">10. Troubleshooting and FAQs for the Automated Installer</a></p>
-<p class="toc level1 tocsp"><a href="appendix.html">11. Appendix</a></p>
-</td>
- <td class="ContentPane" width="705px">
-
- <div class="MainContent">
-
-
-<a name="customai"></a><h3>How to Create and Use a Custom AI Manifest</h3>
-<p>When you create an install service by using the <tt>installadm create-service</tt> 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 make a custom
-manifest and change the specifications in that manifest to create specific installations for
-specific clients.See the following sections.</p>
-<ul><li><p><a href="#aifields">Reviewing the AI Manifest Tags</a></p></li>
-<li><p><a href="#changeai">Replacing a Default Manifest With a Custom Manifest</a></p></li>
-<li><p><a href="#aioptions">Modifying AI Manifest Contents</a></p></li>
-<li><p><a href="#allfields">Example: A Complete AI Manifest</a></p></li></ul>
-
-
-<a name="aifields"></a><h4>Reviewing the AI Manifest Tags</h4>
-<p>The AI manifest is an XML file that contains a series of
-tags and tag values. Each tag and value is enclosed inside XML tags.</p><p>The XML tags all contain a start tag, such as <tt><ai_manifest></tt>, and
-an ending tag, such as <tt></ai_manifest></tt>. A tag is a parameter that specifies
-a piece of information about the manifest itself or about the manifest's installation
-specifications. Tags can contain values that can be edited to modify the manifest
-information or to modify the installation specifications in the manifest.</p><p>For example, see this line in the manifest:</p><pre><ai_manifest name="default"></pre><p>This <tt><ai_manifest></tt> tag assigns a name, “default,” to the manifest by specifying <tt>name="default"</tt>
-in the tag. You can change “default” to another name.</p>
-<hr><p><b>Note - </b>The <tt><ai_manifest name></tt> 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.</p>
-<hr>
-<p>Note the following information about other tags in the AI manifest:</p>
-<ul><li><p>You can use the <tt><ai_target_device></tt> tag to specify a particular target disk on which to install the OpenSolaris OS. See <a href="#iediskrepo">Defining a Target for the Installation</a>. If you do not specify a target disk, the automated installer chooses a default target for installing the OpenSolaris OS.</p>
-<ol><li><p>The installer gets the recommended size for installing the OpenSolaris OS from the AI libraries. Currently, the recommended size is 13 GB.</p></li>
-<li><p>The installer searches for available disks on the client. To determine the default target, the automated installer looks for an available disk with at least recommended size. The disks are found in the order they are reported by the <tt>libdiskmgt</tt> library.</p></li>
-<li><p>When the first disk is found, the installer checks the size of that disk.</p>
-<ul><li><p>If the size is greater than or equal to the recommended size, the installer selects the disk and returns to the installation procedure.</p></li>
-<li><p>If the size is less than the recommended size, the installer goes to the next disk to check the size.</p></li></ul>
-</li>
-<li><p>If there is no match, the automated installation fails.</p></li></ol>
-</li>
-<li><p>The tag, <tt><ai_pkg_repo_default_publisher></tt>, defines the IPS repository from which the installation will be performed. You need to provide the URL of the IPS repository and the publisher. In the default AI manifest, the IPS repository is set to <a href="http://pkg.opensolaris.org/release/">http://pkg.opensolaris.org/release/</a>, and the publisher is defined as <tt>opensolaris.org</tt>.</p></li>
-<li><p>In the tag, <tt><ai_install_packages></tt>, the default manifest instructs the automated installer to install the following packages to the client:</p>
-<ul><li><p><tt>entire</tt></p></li>
-<li><p><tt>SUNWcsd</tt></p></li>
-<li><p><tt>SUNWcs</tt></p></li>
-<li><p><tt>babel_install</tt></p></li>
-<li><p><tt>SUNWiscsi</tt></p></li>
-<li><p><tt>SUNWiscsidm</tt></p></li></ul>
-<p>To use an iSCSI target for an installation, retain the packages, <tt>SUNWiscsi</tt> and <tt>SUNWiscsidm</tt> in the <tt><ai_install_packages></tt> tag. You can remove these packages if you do not plan to use an iSCSI target.</p>
-<hr><p><b>Note - </b>Due to dependency issues, <tt>entire</tt> must be listed first in the package list, followed by <tt>SUNWcsd</tt>, and then <tt>SUNWcs</tt>. Any additional packages must be listed after <tt>SUNWcs</tt>.</p>
-<hr>
-</li>
-<li><p>The tag, <tt><ai_uninstall_packages></tt>, lists packages, <tt>babel_install</tt> and <tt>slim_install</tt>, that will be uninstalled from the client.</p>
-<hr><p><b>Note - </b>Why does the default manifest first install the <tt>babel_install</tt> package, then uninstall it?</p><p><tt>babel_install</tt> is a group package. When <tt>babel_install</tt> is installed, all the packages in the group are installed. However, you cannot uninstall packages that belong to a group package. By uninstalling the group package definition, the individual packages can be deleted later. <tt>babel_install</tt> is used for convenience to install all the required packages, but the group package definition is not needed after installation of packages are completed. The default manifest removes the definition, so that further customization of the packages can be done.</p><p><tt>slim_install</tt> is another group package. And, <tt>slim_install</tt> is part of <tt>babel_install</tt> which is installed by the default manifest. The default manifest uninstalls <tt>slim_install</tt>, in order to permit customization.</p>
-<hr>
-</li>
-<li><p>The tag, <tt><ai_auto_reboot></tt>, can be used to request automatic reboot after successful installation. The default value is <tt>false</tt>, meaning that the client does not automatically reboot after successful installation. If this value is changed to <tt>true</tt>, the client automatically reboots after successful installation.</p></li>
-<li><p>The second part of the default AI manifest is an embedded SC manifest, beginning at the line:</p><pre><sc_embedded_manifest name = "AI"></pre><p>For instructions about how to modify the SC manifest, see <a href="customsc.html">How to Create Custom SC Manifest Files</a>.</p></li></ul>
-
-<hr><p><b>Note - </b>For a summary of the AI manifest contents and possible values, see <a href="aimanifest.html">AI Manifest Contents</a>.</p>
-<hr>
-
-
-<a name="changeai"></a><h4>Replacing a Default Manifest With a Custom Manifest</h4>
-<p>You can replace the default AI manifest for an install service with a
-custom manifest that you created and revised to suit specific client specifications. Use
-the following procedure to create a custom manifest and assign it to
-an install service.</p>
-<ol><li><p>Copy the automated installer's default manifest from the target image path that is associated with the install service you plan to use.</p><p>The target image path for an install service can be determined with the following command, where <i>srvname</i> is the name of the install service.</p><pre># installadm list -n <i>srvname</i></pre><p>For example, see the following command and output:</p><pre># installadm list -n svc1
- Service Name Status Arch Port Image Path
- ------------ ------ ---- ---- ----------
- svc1 on sparc 45603 /export/aiserver/svc1</pre><p>In the above example, the install service, <tt>svc1</tt>, has an image path of <tt>/export/aiserver/svc1</tt>. The default manifest, <tt>default.xml</tt>, located in this image path is at:</p><pre><tt>/export/aiserver/svc1/auto_install/default.xml</tt></pre>
-<hr><p><b>Note - </b>For services created with images that date back prior to the OpenSolaris 2009.06 release, you can copy the <tt>default.xml</tt> manifest located on the install server at <tt>/usr/share/auto_install/default.xml</tt>.</p>
-<hr>
-</li>
-<li><p>Keep the <tt><ai_manifest_name></tt> tag in your manifest copy set to the value of <tt>default</tt>.</p></li>
-<li><p>Revise the <tt><ai_embedded_manifest></tt> and <tt><sc_embedded_manifest></tt> sections of your copy as needed.</p></li>
-<li><p>Use the <tt>installadm add</tt> command to replace the default manifest for an existing install service with your copy as follows:</p><pre># <tt>/usr/sbin/installadm add <tt>-m</tt> <i>manifest_file</i> <tt>-n</tt> <i>svc_name</i></tt></pre><p>Where <tt>manifest_file</tt> is the name of the manifest copy that you created and modified, and where <tt>svc_name</tt> is the name of the install service.</p><p>The <tt>installadm add</tt> command validates your manifest before replacing the default manifest.</p></li></ol>
-
-<hr><p><b>Note - </b>The build number or release of the OpenSolaris packages that you specify in
-the AI manifest must match the build number or release of the
-AI ISO image that you specify in the <tt>installadm create-service</tt> command with the <tt>-s</tt>
-option. </p><p>In particular, if you use an AI ISO image from an OpenSolaris development
-build to set up an install service, that AI ISO image will have
-a build number associated with it. This same build number must be specified
-in the AI manifest for the packages to be installed on the system.
-If you do not, in the manifest, specify a build number for the
-packages to be installed, the installation will use the most current version of
-the packages available in the IPS repository. If the build number for the
-packages does not match the build number for the AI ISO image, the
-installation could fail. For further information, see <a href="#version">Specifying Packages to Install a Specific Version of OpenSolaris</a>.</p>
-<hr>
-
-
-<a name="aioptions"></a><h4>Modifying AI Manifest Contents</h4>
-<p>Once you've created what will be your custom AI manifest, you can
-edit the tags in this custom file. The following examples show options for
-modifying the contents of your custom AI manifest.</p>
-<hr><p><b>Note - </b>The examples in this section are partial excerpts from AI manifest files, showing
-only the tags being discussed in that example. Only the last example shows
-a complete AI manifest.</p>
-<hr>
-
-<ul><li><p><a href="#iediskrepo">Defining a Target for the Installation</a></p></li>
-<li><p><a href="#modpart">Modifying the Partitions and Slices on the Install Client</a></p></li>
-<li><p><a href="#iereboot">Specifying an Automatic Reboot After Installation</a></p></li>
-<li><p><a href="#repo">Specifying an IPS Repository</a></p></li>
-<li><p><a href="#iepkg">Specifying Packages for Installation</a></p></li>
-<li><p><a href="#allfields">Example: A Complete AI Manifest</a></p></li></ul>
-
-<hr><p><b>Note - </b>For further information about specific AI manifest tags and valid values for these
-tags, see <a href="aimanifest.html">AI Manifest Contents</a>.</p>
-<hr>
-
-
-<a name="iediskrepo"></a><h5>Defining a Target for the Installation</h5>
-<p>You can specify a target location on a client for installing the
-OpenSolaris OS as described below.</p>
-<hr><p><b>Note - </b>If you do not specify a target disk, the automated installer chooses a
-default target for installing the OpenSolaris OS. See <a href="faq.html#targetdisk">14. How is the Default Target Disk Selected?</a>.</p>
-<hr>
-<p>There is a variety of options for specifying a target installation location. One
-option is to enter an MPXIO name or a logical device name
-in the tag, <tt><ai_target_device></tt>, as shown in these examples.</p><p>Using a logical device name:</p><pre>...
-<ai_target_device>
- <target_device_name>c0t0d0</target_device_name>
-</ai_target_device>
-...</pre><p>Using an MPXIO name:</p><pre>...
-<ai_target_device>
- <target_device_name>c0t0000002037CD9F72d0</target_device_name>
-</ai_target_device>
-...</pre><p>Or, you can specify a VTOC slice as the installation target. See
-<a href="#ievtoc">Using a VTOC Slice as the Installation Target</a>.</p><p>Alternately, <b>starting with the OpenSolaris 2010.03 release</b>, you can use the following options to specify an installation target.</p>
-<ul><li><p><a href="#bootdisk">Using the Boot Disk as the Installation Target</a></p></li>
-<li><p><a href="#devid">Using the Device ID to Specify an Installation Target</a></p></li>
-<li><p><a href="#phydevice">Using Physical Device Path to Specify an Installation Target</a></p></li>
-<li><p><a href="#volname">Using Volume Name to Specify an Installation Target</a></p></li>
-<li><p><a href="#iscsi">Using an iSCSI Target for Installations</a></p></li></ul>
-<p>You can specify multiple parameters for determining the installation target, but there are
-limitations. See <a href="#multarget">Using Multiple Parameters to Specify an Installation Target</a>.</p>
-
-<a name="bootdisk"></a><h5>Using the Boot Disk as the Installation Target</h5>
-<p>The <tt><ai_target_device></tt> tag accepts <tt>boot_disk</tt> as a keyword. This keyword can be
-used to specify the current boot disk as the installation target as follows:</p><pre>...
-<ai_target_device>
- <target_device_name>
- boot_disk
- </target_device_name>
-</ai_target_device>
-...</pre><p>Note the following limitations to the <tt>boot_disk</tt> keyword:</p>
-<ul><li><p>The <tt>boot_disk</tt> keyword does not work in xVM/PV, because information about the boot disk is not available in that environment.</p></li>
-<li><p>Some x86 BIOS's do not report the boot disk correctly. See <a href="http://bugs.opensolaris.org/bugdatabase/view_bug.do?bug_id=6831009">http://bugs.opensolaris.org/bugdatabase/view_bug.do?bug_id=6831009</a>.</p></li>
-<li><p>For SPARC clients, if the <tt>diag-switch?</tt> OBP property is set to <tt>true</tt>, information about the boot disk is not available. If you would like to utilize boot disk keyword on SPARC platforms, check that the <tt>diag-switch?</tt> is set to false.</p></li></ul>
-
-
-<a name="devid"></a><h5>Using the Device ID to Specify an Installation Target</h5>
-<p>You can use the <tt><target_device_select_id></tt> tag to select a target disk by its
-device ID.</p><p>You can get the device ID by using the <tt>iostat</tt> command as in
-this example:</p><pre>$ iostat -iEn
-
-c7d0 Soft Errors: 0 Hard Errors: 0 Transport Errors: 0
-Model: ST31000340NS Revision: Device Id:
-id1,cmdk@AST31000340NS=9QJ2LNYY
-...</pre><p>Include the <tt><target_device_select_id></tt> tag as shown in the following example:</p><pre>...
-<ai_target_device>
- <target_device_select_id>
- id1,cmdk@AST31000340NS=9QJ2LNYY
- </target_device_select_id>
-</ai_target_device>
-...</pre><p>Note the following limitations for the <tt><target_device_select_id></tt> tag:</p>
-<ul><li><p>The tag does not work in xVM/PV, because the Device ID is not available for virtual drives.</p></li>
-<li><p>The <tt>iostat</tt> command does not report the Device ID on LDOM guests. However, that information is available, and can be obtained by using the target discovery test driver which is present in the <tt>installadm</tt> test package. Use the test driver as demonstrated in this example.</p><pre># /opt/install-test/bin/tdmgtst -dv | grep ddm_disk_dev_id
-ddm_disk_dev_id=id1,vdc@f8498536e4a8ad037000bcb400001</pre></li></ul>
-
-
-<a name="phydevice"></a><h5>Using Physical Device Path to Specify an Installation Target</h5>
-<p>You can use the tag, <tt><target_device_select_device_path></tt>, to select a target disk by
-specifying the physical path in the <tt>/devices</tt> directory.</p><p>One way to find the physical path is to look at the
-related <tt>c#t#d#s#</tt> symbolic link, as in the following example.</p><pre>$ ls -l /dev/dsk/c7d0s0
-lrwxrwxrwx 1 root root 51 2009-04-03 00:20 /dev/dsk/c7d0s0 ->
-../../devices/pci@0,0/pci-ide@1f,2/ide@0/cmdk@0,0:a</pre><p>Include the <tt><target_device_select_device_path></tt> tag as shown in the following example:</p><pre>...
-<ai_target_device>
- <target_device_select_device_path>
- /pci@0,0/pci-ide@1f,2/ide@0/cmdk@0,0
- </target_device_select_device_path>
-</ai_target_device>
-...</pre>
-
-<a name="volname"></a><h5>Using Volume Name to Specify an Installation Target</h5>
-<p>You can use the tag, <tt><target_device_select_volume_name></tt>, to select a target disk by
-specifying a volume name that was created using the <tt>format</tt> command.</p><p>The following example shows how to create a volume name.</p><pre>format -d c0d0 > /dev/null 2>/dev/null - <<EOF
-volname
-"ai-disk"
-y
-quit
-EOF</pre><p>Include the <tt><target_device_select_volume_name></tt> tag as shown in the following example:</p><pre>...
-<ai_target_device>
- <target_device_select_volume_name>
- ai-disk
- </target_device_select_volume_name>
-</ai_target_device>
-...</pre>
-
-<a name="iscsi"></a><h5>Using an iSCSI Target for Installations</h5>
-<p>With iSCSI technology, you can install to a disk drive hosted by
-another computer on the same TCP/IP network. <b>Starting with the OpenSolaris 2010.03 release</b>, you can specify an iSCSI
-target for automated installations, as shown in this example.</p><pre>...
-<ai_target_device>
- <target_device_iscsi_target_name>iqn.1986-03.com.sun:02: \
-c9e1533d-2d61-c198-b4ea-a9e3c40a49dd</target_device_iscsi_target_name>
- <target_device_iscsi_target_ip>10.0.0.1</target_device_iscsi_target_ip>
- <target_device_iscsi_target_port>3260</target_device_iscsi_target_port>
- <target_device_iscsi_target_lun>0</target_device_iscsi_target_lun>
-</ai_target_device>
-...</pre><p>The following table describes each iSCSI tag.</p><a name="iscsitbl"></a><h6>Table 8-1 iSCSI Tags</h6><table><col width="25%"><col width="25%"><col width="25%"><col width="25%"><tr><th align="left" valign="top" scope="column"><p>Tag Name</p></th>
-<th align="left" valign="top" scope="column"><p>Description</p></th>
-<th align="left" valign="top" scope="column"><p>Required?</p></th>
-<th align="left" valign="top" scope="column"><p>Format</p></th>
-</tr>
-<tr><td align="left" valign="top" scope="row"><p><tt><target_device</tt></p><p><tt>_iscsi_target_name></tt></p></td>
-<td align="left" valign="top" scope="row"><p>Target name, such as IQN,
-EUI, or NAA</p></td>
-<td align="left" valign="top" scope="row"><p>Required</p></td>
-<td align="left" valign="top" scope="row"><p>Mixed ASCII, normally quite long, maximum of about 233 characters</p></td>
-</tr>
-<tr><td align="left" valign="top" scope="row"><p><tt><target_device</tt></p><p><tt>_iscsi_target_ip></tt></p></td>
-<td align="left" valign="top" scope="row"><p>IP
-address of the target</p></td>
-<td align="left" valign="top" scope="row"><p>Required</p></td>
-<td align="left" valign="top" scope="row"><p>Valid IP address</p></td>
-</tr>
-<tr><td align="left" valign="top" scope="row"><p><tt><target_device</tt></p><p><tt>_iscsi_target_port></tt></p></td>
-<td align="left" valign="top" scope="row"><p>IP port for the target</p></td>
-<td align="left" valign="top" scope="row"><p>Optional </p></td>
-<td align="left" valign="top" scope="row"><p>Integer, default=3260</p></td>
-</tr>
-<tr><td align="left" valign="top" scope="row"><p><tt><target_device</tt></p><p><tt>_iscsi_target_lun></tt></p></td>
-<td align="left" valign="top" scope="row"><p>Logical
-unit number defines an iSCSI device on the target. This may be needed
-to distinguish between multiple boot disks on the same target.</p></td>
-<td align="left" valign="top" scope="row"><p>Optional</p></td>
-<td align="left" valign="top" scope="row"><p>Integer or integers
-separated by hyphens, default=zero (0)</p></td>
-</tr>
-<tr><td align="left" valign="top" scope="row"><p><tt><target_device</tt></p><p><tt>_iscsi_parameter_source></tt></p></td>
-<td align="left" valign="top" scope="row"><p>Indicates where the iSCSI boot parameters will be
-sought.</p></td>
-<td align="left" valign="top" scope="row"><p>Optional, defaults to the AI manifest</p></td>
-<td align="left" valign="top" scope="row"><p>“manifest”, “DHCP”</p></td>
-</tr>
-</table><p>To specify an iSCSI target in the AI manifest, you must first
-create an iSCSI boot target by using the <tt>iscsitadm</tt> command. Then, use the
-<tt>iscsitadm</tt> information to complete the above iSCSI manifest tags.</p>
-<hr><p><b>Note - </b>To use an iSCSI target, the packages, <tt>SUNWiscsi</tt> and <tt>SUNWiscsidm</tt>, must be
-included in the <tt><ai_install_packages></tt> tag in the AI manifest as follows:</p><pre>...
-<ai_install_packages>
- ...
- <pkg name="SUNWiscsi"/>
- <pkg name="SUNWiscsidm"/>
-</ai_install_packages>
-...</pre><p>These packages are in the default AI manifest. Check to be sure
-you have included them in any custom manifests.</p>
-<hr>
-<p>For information, see the <a href="http://wikis.sun.com/display/OpenSolarisInfo201003/iSCSI+Boot+for+OpenSolaris+User%27s+Guide">iSCSI Boot for OpenSolaris User's Guide</a>.</p>
-
-<a name="multarget"></a><h5>Using Multiple Parameters to Specify an Installation Target</h5>
-<p>You can use multiple parameters to specify an installation target, but there are
-limitations.</p><p>Only one of the following parameters can be specified at a time.
-And, the following parameters cannot be combined with other parameters:</p>
-<ul><li><p><tt><target_device_iscsi_parameter_source></tt></p></li>
-<li><p><tt><target_device_name></tt> – Using either <tt>c#t#d#</tt> or <tt>boot_disk</tt></p></li>
-<li><p><tt><target_device_select_volume_name></tt></p></li>
-<li><p><tt><target_device_select_id></tt></p></li>
-<li><p><tt><target_device_select_device_path></tt></p></li></ul>
-<p>The following parameters can be combined with each other. But, they are invalid
-if used with any of the parameters from the previous list.</p>
-<ul><li><p><tt><target_device_type></tt></p></li>
-<li><p><tt><target_device_vendor></tt></p></li>
-<li><p><tt><target_device_size></tt></p></li></ul>
-<p>The following examples show how you could combine these parameters.</p><p>In the following example, an SCSI Hitachi disk with at least 70
-GB, expressed as 146800640 sectors, will be selected for the installation.</p><pre>...
-<ai_target_device>
- <target_device_type>
- SCSI
- </target_device_type>
- <target_device_vendor>
- HITACHI
- </target_device_vendor>
- <target_device_size>
- 146800640
- </target_device_size>
-</ai_target_device>
-...</pre><p>In the following example, an ATA disk with at least 35 GB,
-expressed as 73400320, will be selected for the installation.</p><pre>...
-<ai_target_device>
- <target_device_type>
- ATA
- </target_device_type>
- <target_device_size>
- 73400320
- </target_device_size>
-</ai_target_device>
-...</pre>
-<hr><p><b>Note - </b>If an invalid manifest is provided to the AI client, the automated installation
-aborts when validating the manifest. Error messages indicating the cause of the failed
-syntactic validation can be found in <tt>/tmp/install_log</tt> file on installation client.</p>
-<hr>
-
-
-<a name="ievtoc"></a><h5>Using a VTOC Slice as the Installation Target</h5>
-<p>If a slice is not 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 <tt><ai_target_device></tt> tag.</p><p>This example instructs the installer to install the OpenSolaris OS on slice 4.</p><pre>...
-<ai_target_device>
- <target_device_name>c0t0000002037CD9F72d0</target_device_name>
- <target_device_install_slice_number>4</target_device_install_slice_number>
-</ai_target_device>
-...</pre>
-
-<a name="modpart"></a><h5>Modifying the Partitions and Slices on the Install Client</h5>
-<p>You can modify the existing partitions and slices in the installation target. See
-the following options.</p>
-<hr><p><b>Note - </b>Partitioning changes during installation occur in the order the change is listed in
-the manifest.</p>
-<hr>
-
-<ul><li><p><a href="#iepartition">Deleting an <tt>fdisk</tt> Partition (x86 Clients Only)</a></p></li>
-<li><p><a href="#createpart">Creating an <tt>fdisk</tt> Partition (x86 Clients Only)</a></p></li>
-<li><p><a href="#extpart">Creating an Extended Partition (x86 Clients Only)</a></p></li>
-<li><p><a href="#ieslices">Deleting a VTOC Slice</a></p></li>
-<li><p><a href="#createvtoc">Creating a VTOC Slice</a></p></li>
-<li><p><a href="#iepreserve">Preserving VTOC Slices</a></p></li></ul>
-
-
-<a name="iepartition"></a><h5>Deleting an <tt>fdisk</tt> Partition (x86 Clients Only)</h5>
-
-<hr><p><b>Note - </b>Partition operations are meaningful only for x86 clients.</p>
-<hr>
-<p>You can delete existing partitions during client installation. Use the tag, <tt><ai_device_partitioning></tt>, and
-specify the <tt>delete</tt> action in the tag to delete a partition during
-installation.</p><pre>...
-<ai_device_partitioning>
- <partition_action>delete</partition_action>
- <partition_number>3</partition_number>
-</ai_device_partitioning>
-...</pre>
-
-<a name="createpart"></a><h5>Creating an <tt>fdisk</tt> Partition (x86 Clients Only)</h5>
-
-<hr><p><b>Note - </b>Partition operations are meaningful only for x86 clients.</p>
-<hr>
-<p>You can create a new partition during client installation. Use the tag,
-<tt><ai_device_partitioning></tt>, and specify the <tt>create</tt> action in the tag to create a
-partition during installation.</p><p>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. </p><pre>...
-<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>
-...</pre>
-
-<a name="extpart"></a><h5>Creating an Extended Partition (x86 Clients Only)</h5>
-<p><b>Starting with the OpenSolaris 2010.03 release</b>, you can create an extended partition in an fdisk partition table
-as part of your automated installation. An extended partition provides space for one or
-more logical partitions. Multiple logical partitions can be created in an extended partition.</p><p>You can create an extended partition, or create logical partitions in a new
-or existing extended partition, by using the <tt><ai_device_partitioning></tt> tag in the AI
-manifest. See the following examples.</p><p><b>Create an extended partition</b> by using the <tt><ai_device_partitioning></tt> tag as in the following example:</p><pre>...
-<ai_device_partitioning>
- <partition_action>create</partition_action>
- <partition_size>max_size</partition_size>
- <partition_type>DOSEXT</partition_type>
-</ai_device_partitioning>
-...</pre><p>In the example above, you are creating an extended partition. When applied to
-extended or primary partitions, the <tt>max_size</tt> value uses the largest region of free
-space on the disk to create the extended or primary partition. In the
-new extended partition, a logical partition is automatically created that uses all the
-space in the extended partition.</p><p>In this example, the partition type is set to DOSEXT. Valid text
-values for the <tt>partition_type</tt> tag include DOSEXT, SOLARIS, DOS16, FAT32, and DOSEXTLBA.</p><p><b>Create a logical partition</b> inside an existing extended partition by using the same <tt><ai_device_partitioning></tt> tag as
-in the following example:</p><pre>...
-<ai_device_partitioning>
- <partition_action>create</partition_action>
- <partition_size>max_size</partition_size>
- <partition_type>SOLARIS</partition_type>
- <partition_is_logical>true</partition_is_logical>
-</ai_device_partitioning>
-...</pre><p>In the example above, you are creating a new logical partition, of
-the type SOLARIS, within the existing extended partition, using any available free space in
-the extended partition.</p><p>The <tt>max_size</tt> value, as in the above example, specifies that the largest block
-of free space in the extended partition will be used for the logical
-partition.</p>
-<hr><p><b>Note - </b>If there are no other logical partitions, the entire extended partition is used
-for the logical partition.</p><p>If there is more than one logical partition, the total space for all
-logical partitions in an extended partition cannot exceed the total space in the
-extended partition.</p><p>If there is no available space for the logical partition because another logical
-partition is already using all the space, this installation would fail.</p>
-<hr>
-<p><b>Create an extended partition that contains two new logical partitions</b> as shown in the following example.</p><pre>...
-<!-- create an extended partition in the largest block of free space -->
-<ai_device_partitioning>
- <partition_action>create</partition_action>
- <partition_size>max_size</partition_size>
- <partition_type>DOSEXT</partition_type>
-</ai_device_partitioning>
-<!-- create a 10G FAT32 logical partition on the extended partition you just created-->
-<!-- in this example, the partition would consume the
- 1st 10G of the extended partition -->
-<ai_device_partitioning>
- <partition_action>create</partition_action>
- <partition_is_logical>true</partition_is_logical>
- <partition_size>10</partition_size>
- <partition_size_units>G</partition_size_units>
- <partition_type>FAT32</partition_type>
-</ai_device_partitioning>
-<!-- create a Solaris logical partition using the largest unused free space
- in the extended partition -->
-<!-- in this example, the partition would use the remaining space in the
- extended partition -->
-<ai_device_partitioning>
- <partition_action>create</partition_action>
- <partition_is_logical>true</partition_is_logical>
- <partition_type>SOLARIS</partition_type>
- <partition_size>max_size</partition_size>
-</ai_device_partitioning>
-...</pre><p>This example accomplishes the following:</p>
-<ul><li><p>Creates an extended partition using the largest region of free space available on the disk.</p></li>
-<li><p>Creates a FAT32 logical partition in the extended partition, using the first contiguous 10GB of the available space.</p></li>
-<li><p>Creates a Solaris logical partition using the largest remaining unused space.</p></li></ul>
-
-
-<a name="ieslices"></a><h5>Deleting a VTOC Slice</h5>
-<p>You can delete an existing VTOC slice during client installation. Use the tag,
-<tt><ai_device_vtoc_slices></tt>, and specify the <tt>delete</tt> action in the tag to delete a
-slice during installation.</p>
-<hr><p><b>Note - </b>The size element is required, but only for XML validation.</p>
-<hr>
-<pre>...
-<ai_device_vtoc_slices>
- <slice_action>delete</slice_action>
- <slice_number>0</slice_number>
- <slice_size>20</slice_size>
-</ai_device_vtoc_slices>
-...</pre>
-
-<a name="createvtoc"></a><h5>Creating a VTOC Slice</h5>
-<p>You can create a new VTOC slice during client installation. Use the tag,
-<tt><ai_device_vtoc_slices></tt>, and specify the <tt>create</tt> action in the tag to create a
-slice during installation. The following example shows how to create a new slice
-5.</p><p>This example uses GB (Gigabytes) as the unit for slice size.</p><pre>...
-<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>
-...</pre>
-
-<a name="iepreserve"></a><h5>Preserving VTOC Slices</h5>
-<p>You can preserve an existing VTOC slice during client installation. Use the tag,
-<tt><ai_device_vtoc_slices></tt>, 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.</p><pre>...
-<ai_device_vtoc_slices>
- <slice_action>preserve</slice_action>
- <slice_number>7</slice_number>
-</ai_device_vtoc_slices>
-...</pre>
-
-<a name="iereboot"></a><h5>Specifying an Automatic Reboot After Installation</h5>
-<p>By default, the automated installer does not reboot the client after a 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,
-<tt><ai_auto_reboot></tt>, in the AI manifest, and set the reboot value in that tag
-to <tt>true</tt>, as per the following snippet:</p><pre>...
-<ai_auto_reboot>
- true
-</ai_auto_reboot>
-...</pre>
-
-<a name="repo"></a><h5>Specifying an IPS Repository</h5>
-<p>The automated installer client must install packages from an IPS repository. You can
-specify an IPS repository, a repository mirror, an HTTP proxy for a repository,
-or an additional repository as follows.</p><p>The IPS repository is defined in the AI manifest by using the
-tag <tt><ai_pkg_repo_default_publisher></tt>. See the following example. This example specifies the repository located at
-<a href="http://pkg.opensolaris.org">http://pkg.opensolaris.org</a>. The name of this repository is <tt>opensolaris.org</tt>.</p><pre>...
-<ai_manifest name="ai_manifest1">
- <ai_pkg_repo_default_publisher>
- <main url="http://pkg.opensolaris.org" publisher="opensolaris.org"/>
- </ai_pkg_repo_default_publisher>
-</ai_manifest>
-...</pre>
-
-<a name="mirror"></a><h5>Specifying an IPS Repository Mirror</h5>
-<p>You can add a mirror to an IPS repository in the AI
-manifest as in this example:</p><pre>...
-<ai_manifest name="ai_manifest1">
- <ai_pkg_repo_default_publisher>
- <main url="http://pkg.opensolaris.org" publisher="opensolaris.org"/>
- <mirror url="http://example.com/ips_mirror">
- </ai_pkg_repo_default_publisher>
-</ai_manifest>
-...</pre>
-
-<a name="ieproxy"></a><h5>Specifying an HTTP Proxy to Reach an IPS Repository</h5>
-<p>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, <tt><ai_http_proxy></tt>, and value in the
-manifest can contain the URL of the proxy as follows:</p><pre>...
-<ai_manifest name="http_proxy">
- <ai_pkg_repo_default_publisher>
- <main url="http://pkg.opensolaris.org" publisher="opensolaris.org"/>
- </ai_pkg_repo_default_publisher>
- <ai_http_proxy url="http://192.168.0.101:8080"/>
-</ai_manifest>
-...</pre>
-
-<a name="iemorerepo"></a><h5>Specifying an Additional Repository</h5>
-<p>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, <tt><ai_pkg_repo_addl_publisher></tt>, to add additional repositories to the AI
-manifest.</p><pre>...
-<ai_manifest name="example1">
- <ai_pkg_repo_default_publisher>
- <main url="http://pkg.opensolaris.org" publisher="opensolaris.org"/>
- </ai_pkg_repo_default_publisher>
- <ai_pkg_repo_addl_publisher>
- <main url="http://pkg.opensolaris.org/contrib" publisher="opensolaris.org"/>
- </ai_pkg_repo_addl_publisher>
-</ai_manifest>
-...</pre>
-<hr><p><b>Note - </b>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.</p>
-<hr>
-
-
-<a name="iepkg"></a><h5>Specifying Packages for Installation</h5>
-<p>The following packages are needed for a successful installation of the OpenSolaris OS
-and are included in the AI default manifest:</p>
-<ul><li><p><tt>entire</tt></p></li>
-<li><p><tt>SUNWcsd</tt></p></li>
-<li><p><tt>SUNWcs</tt></p></li>
-<li><p><tt>babel_install</tt></p></li>
-<li><p><tt>SUNWiscsi</tt></p></li>
-<li><p><tt>SUNWiscsidm</tt></p></li></ul>
-<p>In the <tt><ai_install_packages></tt> tag, you can list more packages to be added during
-installation.</p><p>You need to retain the default packages along with the additional packages. However,
-if you are not going to use an iSCSI target for installations,
-you can remove the two iSCSI packages.</p>
-<hr><p><b>Note - </b>Due to dependency issues, <tt>entire</tt> must be listed first in the package list,
-followed by <tt>SUNWcsd</tt>, and then <tt>SUNWcs</tt>. Any additional packages must be listed
-after <tt>SUNWcs</tt>.</p>
-<hr>
-<p>In the following example, the <tt>openoffice</tt> and the <tt>SUNWTcl</tt> packages are added
-as part of the OpenSolaris installation.</p><pre><ai_manifest name="ai_packages">...
- <ai_install_packages>
- <pkg name="entire"/>
- <pkg name="SUNWcsd"/>
- <pkg name="SUNWcs"/>
- <pkg name="babel_install"/>
- <pkg name="SUNWiscsi"/>
- <pkg name="SUNWiscsidm"/>
- <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></pre>
-<hr><p><b>Note - </b>The default manifest first installs the <tt>babel_install</tt> package, then uninstalls it.
-<tt>babel_install</tt> is a group package consisting of set of packages. When <tt>babel_install</tt> is
-installed, all the packages in the group are installed. However, you cannot uninstall
-packages that belong to a group package. By uninstalling the group package definition,
-the individual packages can be deleted later. <tt>babel_install</tt> is used for convenience
-to install all the required packages, but the group package definition is not
-needed once installation of packages is completed. The default manifest removes the definition,
-so that further customization of the packages can be done.</p><p><tt>slim_install</tt> is another group package. And, <tt>slim_install</tt> is part of <tt>babel_install</tt> which
-is installed by the default manifest. The default manifest then uninstalls <tt>slim_install</tt>, in
-order to permit customization.</p>
-<hr>
-
-
-<a name="version"></a><h5>Specifying Packages to Install a Specific Version of OpenSolaris</h5>
-<p>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 <tt>entire</tt>, by using the following form:</p><pre><pkg_name="[email protected]#/></pre><p>The IPS repositories include a fault resource management identifier (FMRI) for each version
-of a package. Use the FMRI string to specify a specific version of
-the package, <tt>entire</tt>, in the AI manifest.</p><p> The following example specifies that OpenSolaris build 111 be installed to the
-client.</p><pre><ai_manifest name="ai_packages">...
- <ai_install_packages>
- <pkg name="[email protected]"/>
- <pkg name="SUNWcsd"/>
- <pkg name="SUNWcs"/>
- <pkg name="babel_install"/>
- <pkg name="SUNWiscsi"/>
- <pkg name="SUNWiscsidm"/>
- <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></pre>
-<hr><p><b>Note - </b>The build number or release of the AI ISO image that you
-specify in the <tt>installadm create-service</tt> command must be the same build number or release of
-the OpenSolaris operating system that you specify in the AI manifest.</p>
-<hr>
-
-
-<a name="allfields"></a><h4>Example: A Complete AI Manifest</h4>
-<p>The following example shows a complete AI manifest where all the primary tags
-are in use.</p><pre><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_publisher>
- <!-- IPS repository -->
- <main url="http://pkg.opensolaris.org" publisher="opensolaris.org"/>
- </ai_pkg_repo_default_publisher>
- <ai_http_proxy url="http://127.100.74.120: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="SUNWiscsi"/>
- <pkg name="SUNWiscsidm"/>
- <pkg name="SUNWTcl"/>
- </ai_install_packages> <!-- Due to dependency issues, entire must be listed first
- in the package list, followed by SUNWcsd, and then SUNWcs.
- Any additional packages must be listed after SUNWcs. -->
- <ai_uninstall_packages>
- <pkg name="babel_install"/>
- <pkg name="slim_install"/>
- </ai_uninstall_packages>
-</ai_manifest></pre>
- </div>
- </td>
- </tr>
-
- <tr class="PageControls" valign="top">
- <td></td>
- <td>
- <table width="100%">
- <tr>
- <td>
- <a href="manifest1.html">Previous</a>
- </td>
- <td align="right">
- <a href="customsc.html">Next</a>
- </td>
- </tr>
- </table>
- </td>
- </tr>
-</tbody>
-</table>
-
-
-</body>
-</html>
-
--- a/usr/src/cmd/installadm/docs/customsc.html Wed Sep 29 16:37:00 2010 +0200
+++ /dev/null Thu Jan 01 00:00:00 1970 +0000
@@ -1,133 +0,0 @@
-<!DOCTYPE HTML PUBLIC "-//W3C//DTD HTML 4.01 Transitional//EN" "http://www.w3.org/TR/html4/loose.dtd">
-<html lang="en-US">
-
-<!-- -->
-<head>
-<!-- GenHTML revision 23436-->
-<meta http-equiv="Content-type" content="text/html; charset=iso-8859-1">
-<title>How to Create Custom SC Manifest Files - OpenSolaris 2010.03 Automated Installer Guide</title>
-<meta name="robots" content="index,follow">
-<meta name="robots" content="index,follow">
-<meta name="date" content="2010-03-01">
-<meta name="collection" content="reference">
-<link rel="stylesheet" type="text/css" href="css/elements.css">
-<link rel="stylesheet" type="text/css" href="css/opensol.css">
-</head>
-
-<body>
-
-
-<div class="Masthead">
- <div class="MastheadLogo">
- <a href="http://www.opensolaris.com"><img border="0" src="graphics/opensolaris_logo_trans.png"></img></a>
- </div>
- <div class="Title">OpenSolaris 2010.03 Automated Installer Guide</div>
-</div>
-<div class="headerbar"></div>
-
-
-<table class="Layout" border="0" cellspacing="0" width="100%">
-<tbody>
-
- <tr valign="top" class="PageControls">
- <td></td>
- <td>
- <table width="100%">
- <tr>
- <td>
- <a href="customai.html">Previous</a>
- </td>
- <td align="right">
- <a href="criteria.html">Next</a>
- </td>
- </tr>
- </table>
- </td>
- </tr>
-
- <tr valign="top">
- <td class="Navigation" width="200px"><p class="toc level1"><a href="docinfo.html">Document Information</a></p>
-<p class="toc level1 tocsp"><a href="index.html">1. What's New For Automated Installations</a></p>
-<p class="toc level1 tocsp"><a href="intro.html">2. Introduction to the Automated Installer</a></p>
-<p class="toc level1 tocsp"><a href="tasks.html">3. Automated Network Install Task Map</a></p>
-<p class="toc level1 tocsp"><a href="bootable.html">4. Automated Installations That Boot From Media</a></p>
-<p class="toc level1 tocsp"><a href="setup.html">5. Set up an Automated Install Server</a></p>
-<p class="toc level1 tocsp"><a href="administer.html">6. How to Administer an Automated Install Server</a></p>
-<p class="toc level1 tocsp"><a href="client.html">7. How to Administer a Custom Install Client</a></p>
-<p class="toc level1 tocsp"><a href="manifest.html">8. How to Administer Manifest Files</a></p>
-<p class="toc level2"><a href="manifest1.html">Types of Manifests</a></p>
-<p class="toc level2"><a href="customai.html">How to Create and Use a Custom AI Manifest</a></p>
-<div id="scrolltoc" class="onpage">
-<p class="toc level2"><a href="">How to Create Custom SC Manifest Files</a></p>
-</div>
-<p class="toc level2"><a href="criteria.html">How to Create and Use a Criteria Manifest</a></p>
-<p class="toc level2"><a href="associate.html">How to Assign Manifests to a Client</a></p>
-<p class="toc level1 tocsp"><a href="clients.html">9. How to Manage Client Installations</a></p>
-<p class="toc level1 tocsp"><a href="trouble.html">10. Troubleshooting and FAQs for the Automated Installer</a></p>
-<p class="toc level1 tocsp"><a href="appendix.html">11. Appendix</a></p>
-</td>
- <td class="ContentPane" width="705px">
-
- <div class="MainContent">
-
-
-<a name="customsc"></a><h3>How to Create Custom SC Manifest Files</h3>
-<p>The SC manifest file provides system configuration specifications for the installed system. You
-can customize the configuration settings by editing the variable after <tt>value=</tt> 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 tags.</p>
-
-<a name="current"></a><h4>Modifying the SC Manifest</h4>
-<p>In the following SC manifest example, you could change the user name from
-<tt>jack</tt> to <tt>mike</tt> in the <tt>username</tt> property.</p><pre><?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></pre>
-<hr><p><b>Note - </b>Encrypted passwords are used in the manifest. In the example above, the encrypted
-password for the user is <tt>jack</tt>, and the root password is <tt>opensolaris</tt>.</p><p>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 <tt>/etc/shadow</tt> file between the 1st and 2nd colons
-of the user's record, and add that information into the <tt>userpass</tt> or <tt>rootpass</tt>
-values in the manifest.</p>
-<hr>
-
- </div>
- </td>
- </tr>
-
- <tr class="PageControls" valign="top">
- <td></td>
- <td>
- <table width="100%">
- <tr>
- <td>
- <a href="customai.html">Previous</a>
- </td>
- <td align="right">
- <a href="criteria.html">Next</a>
- </td>
- </tr>
- </table>
- </td>
- </tr>
-</tbody>
-</table>
-
-
-</body>
-</html>
-
--- a/usr/src/cmd/installadm/docs/delclient.html Wed Sep 29 16:37:00 2010 +0200
+++ /dev/null Thu Jan 01 00:00:00 1970 +0000
@@ -1,101 +0,0 @@
-<!DOCTYPE HTML PUBLIC "-//W3C//DTD HTML 4.01 Transitional//EN" "http://www.w3.org/TR/html4/loose.dtd">
-<html lang="en-US">
-
-<!-- -->
-<head>
-<!-- GenHTML revision 23436-->
-<meta http-equiv="Content-type" content="text/html; charset=iso-8859-1">
-<title>How to Delete an Install Client - OpenSolaris 2010.03 Automated Installer Guide</title>
-<meta name="robots" content="index,follow">
-<meta name="robots" content="index,follow">
-<meta name="date" content="2010-03-01">
-<meta name="collection" content="reference">
-<link rel="stylesheet" type="text/css" href="css/elements.css">
-<link rel="stylesheet" type="text/css" href="css/opensol.css">
-</head>
-
-<body>
-
-
-<div class="Masthead">
- <div class="MastheadLogo">
- <a href="http://www.opensolaris.com"><img border="0" src="graphics/opensolaris_logo_trans.png"></img></a>
- </div>
- <div class="Title">OpenSolaris 2010.03 Automated Installer Guide</div>
-</div>
-<div class="headerbar"></div>
-
-
-<table class="Layout" border="0" cellspacing="0" width="100%">
-<tbody>
-
- <tr valign="top" class="PageControls">
- <td></td>
- <td>
- <table width="100%">
- <tr>
- <td>
- <a href="scenario.html">Previous</a>
- </td>
- <td align="right">
- <a href="manifest.html">Next</a>
- </td>
- </tr>
- </table>
- </td>
- </tr>
-
- <tr valign="top">
- <td class="Navigation" width="200px"><p class="toc level1"><a href="docinfo.html">Document Information</a></p>
-<p class="toc level1 tocsp"><a href="index.html">1. What's New For Automated Installations</a></p>
-<p class="toc level1 tocsp"><a href="intro.html">2. Introduction to the Automated Installer</a></p>
-<p class="toc level1 tocsp"><a href="tasks.html">3. Automated Network Install Task Map</a></p>
-<p class="toc level1 tocsp"><a href="bootable.html">4. Automated Installations That Boot From Media</a></p>
-<p class="toc level1 tocsp"><a href="setup.html">5. Set up an Automated Install Server</a></p>
-<p class="toc level1 tocsp"><a href="administer.html">6. How to Administer an Automated Install Server</a></p>
-<p class="toc level1 tocsp"><a href="client.html">7. How to Administer a Custom Install Client</a></p>
-<p class="toc level2"><a href="cclient.html">How to Set Up an Install Client</a></p>
-<p class="toc level2"><a href="scenario.html">Example: Creating a Custom Install Client</a></p>
-<div id="scrolltoc" class="onpage">
-<p class="toc level2"><a href="">How to Delete an Install Client</a></p>
-</div>
-<p class="toc level1 tocsp"><a href="manifest.html">8. How to Administer Manifest Files</a></p>
-<p class="toc level1 tocsp"><a href="clients.html">9. How to Manage Client Installations</a></p>
-<p class="toc level1 tocsp"><a href="trouble.html">10. Troubleshooting and FAQs for the Automated Installer</a></p>
-<p class="toc level1 tocsp"><a href="appendix.html">11. Appendix</a></p>
-</td>
- <td class="ContentPane" width="705px">
-
- <div class="MainContent">
-
-
-<a name="delclient"></a><h3>How to Delete an Install Client</h3>
-<p>Use the following command to delete an existing install client.</p><pre># <tt>installadm delete-client <i>macaddr</i></tt></pre><p>This command deletes an existing client's specific service information that was previously set
-up using the <tt>installadm create-client</tt> command.</p><p>The <tt>macaddr</tt> option is required to specify the MAC address for the install
-client.</p><p>For help with client installations, see <a href="clients.html">Chapter 9, How to Manage Client Installations</a> and <a href="setupfaq.html#fails">2. What if the Client Installation Fails?</a></p>
- </div>
- </td>
- </tr>
-
- <tr class="PageControls" valign="top">
- <td></td>
- <td>
- <table width="100%">
- <tr>
- <td>
- <a href="scenario.html">Previous</a>
- </td>
- <td align="right">
- <a href="manifest.html">Next</a>
- </td>
- </tr>
- </table>
- </td>
- </tr>
-</tbody>
-</table>
-
-
-</body>
-</html>
-
--- a/usr/src/cmd/installadm/docs/delete.html Wed Sep 29 16:37:00 2010 +0200
+++ /dev/null Thu Jan 01 00:00:00 1970 +0000
@@ -1,103 +0,0 @@
-<!DOCTYPE HTML PUBLIC "-//W3C//DTD HTML 4.01 Transitional//EN" "http://www.w3.org/TR/html4/loose.dtd">
-<html lang="en-US">
-
-<!-- -->
-<head>
-<!-- GenHTML revision 23436-->
-<meta http-equiv="Content-type" content="text/html; charset=iso-8859-1">
-<title>How to Delete Install Services - OpenSolaris 2010.03 Automated Installer Guide</title>
-<meta name="robots" content="index,follow">
-<meta name="robots" content="index,follow">
-<meta name="date" content="2010-03-01">
-<meta name="collection" content="reference">
-<link rel="stylesheet" type="text/css" href="css/elements.css">
-<link rel="stylesheet" type="text/css" href="css/opensol.css">
-</head>
-
-<body>
-
-
-<div class="Masthead">
- <div class="MastheadLogo">
- <a href="http://www.opensolaris.com"><img border="0" src="graphics/opensolaris_logo_trans.png"></img></a>
- </div>
- <div class="Title">OpenSolaris 2010.03 Automated Installer Guide</div>
-</div>
-<div class="headerbar"></div>
-
-
-<table class="Layout" border="0" cellspacing="0" width="100%">
-<tbody>
-
- <tr valign="top" class="PageControls">
- <td></td>
- <td>
- <table width="100%">
- <tr>
- <td>
- <a href="add.html">Previous</a>
- </td>
- <td align="right">
- <a href="view.html">Next</a>
- </td>
- </tr>
- </table>
- </td>
- </tr>
-
- <tr valign="top">
- <td class="Navigation" width="200px"><p class="toc level1"><a href="docinfo.html">Document Information</a></p>
-<p class="toc level1 tocsp"><a href="index.html">1. What's New For Automated Installations</a></p>
-<p class="toc level1 tocsp"><a href="intro.html">2. Introduction to the Automated Installer</a></p>
-<p class="toc level1 tocsp"><a href="tasks.html">3. Automated Network Install Task Map</a></p>
-<p class="toc level1 tocsp"><a href="bootable.html">4. Automated Installations That Boot From Media</a></p>
-<p class="toc level1 tocsp"><a href="setup.html">5. Set up an Automated Install Server</a></p>
-<p class="toc level1 tocsp"><a href="administer.html">6. How to Administer an Automated Install Server</a></p>
-<p class="toc level2"><a href="add.html">How to Add Install Services</a></p>
-<div id="scrolltoc" class="onpage">
-<p class="toc level2"><a href="">How to Delete Install Services</a></p>
-</div>
-<p class="toc level2"><a href="view.html">How to Review What You Have on Your Server</a></p>
-<p class="toc level2"><a href="enable.html">How to Enable and Disable Install Services</a></p>
-<p class="toc level2"><a href="smf.html">How to Administer Install Services by Using the AI SMF Service</a></p>
-<p class="toc level1 tocsp"><a href="client.html">7. How to Administer a Custom Install Client</a></p>
-<p class="toc level1 tocsp"><a href="manifest.html">8. How to Administer Manifest Files</a></p>
-<p class="toc level1 tocsp"><a href="clients.html">9. How to Manage Client Installations</a></p>
-<p class="toc level1 tocsp"><a href="trouble.html">10. Troubleshooting and FAQs for the Automated Installer</a></p>
-<p class="toc level1 tocsp"><a href="appendix.html">11. Appendix</a></p>
-</td>
- <td class="ContentPane" width="705px">
-
- <div class="MainContent">
-
-
-<a name="delete"></a><h3>How to Delete Install Services</h3>
-<p>The following command deletes an install service from your system:</p><pre># <tt>installadm delete-service [<tt>-x</tt>] <i>svcname</i></tt></pre><p>With the <tt>-x</tt> option, this command deletes an install service and also removes
-the associated target image.</p><p>The <i>svcname</i> is a required tag that specifies the name of the install
-service to be removed.</p>
- </div>
- </td>
- </tr>
-
- <tr class="PageControls" valign="top">
- <td></td>
- <td>
- <table width="100%">
- <tr>
- <td>
- <a href="add.html">Previous</a>
- </td>
- <td align="right">
- <a href="view.html">Next</a>
- </td>
- </tr>
- </table>
- </td>
- </tr>
-</tbody>
-</table>
-
-
-</body>
-</html>
-
--- a/usr/src/cmd/installadm/docs/docinfo.html Wed Sep 29 16:37:00 2010 +0200
+++ /dev/null Thu Jan 01 00:00:00 1970 +0000
@@ -1,170 +0,0 @@
-<!DOCTYPE HTML PUBLIC "-//W3C//DTD HTML 4.01 Transitional//EN" "http://www.w3.org/TR/html4/loose.dtd">
-<html lang="en-US">
-
-<!-- -->
-<head>
-<!-- GenHTML revision 23436-->
-<meta http-equiv="Content-type" content="text/html; charset=iso-8859-1">
-<title>Document Information - OpenSolaris 2010.03 Automated Installer Guide</title>
-<meta name="robots" content="index,follow">
-<meta name="robots" content="index,follow">
-<meta name="date" content="2010-03-01">
-<meta name="collection" content="reference">
-<link rel="stylesheet" type="text/css" href="css/elements.css">
-<link rel="stylesheet" type="text/css" href="css/opensol.css">
-</head>
-
-<body>
-
-
-<div class="Masthead">
- <div class="MastheadLogo">
- <a href="http://www.opensolaris.com"><img border="0" src="graphics/opensolaris_logo_trans.png"></img></a>
- </div>
- <div class="Title">OpenSolaris 2010.03 Automated Installer Guide</div>
-</div>
-<div class="headerbar"></div>
-
-
-<table class="Layout" border="0" cellspacing="0" width="100%">
-<tbody>
-
- <tr valign="top" class="PageControls">
- <td></td>
- <td>
- <table width="100%">
- <tr>
- <td>
- <a href="autoinstall.html">Previous</a>
- </td>
- <td align="right">
- <a href="index.html">Next</a>
- </td>
- </tr>
- </table>
- </td>
- </tr>
-
- <tr valign="top">
- <td class="Navigation" width="200px"><div id="scrolltoc" class="onpage">
-<p class="toc level1"><a href="">Document Information</a></p>
-</div>
-<p class="toc level1 tocsp"><a href="index.html">1. What's New For Automated Installations</a></p>
-<p class="toc level1 tocsp"><a href="intro.html">2. Introduction to the Automated Installer</a></p>
-<p class="toc level1 tocsp"><a href="tasks.html">3. Automated Network Install Task Map</a></p>
-<p class="toc level1 tocsp"><a href="bootable.html">4. Automated Installations That Boot From Media</a></p>
-<p class="toc level1 tocsp"><a href="setup.html">5. Set up an Automated Install Server</a></p>
-<p class="toc level1 tocsp"><a href="administer.html">6. How to Administer an Automated Install Server</a></p>
-<p class="toc level1 tocsp"><a href="client.html">7. How to Administer a Custom Install Client</a></p>
-<p class="toc level1 tocsp"><a href="manifest.html">8. How to Administer Manifest Files</a></p>
-<p class="toc level1 tocsp"><a href="clients.html">9. How to Manage Client Installations</a></p>
-<p class="toc level1 tocsp"><a href="trouble.html">10. Troubleshooting and FAQs for the Automated Installer</a></p>
-<p class="toc level1 tocsp"><a href="appendix.html">11. Appendix</a></p>
-</td>
- <td class="ContentPane" width="705px">
-
- <div class="MainContent">
- <a name="documentinfo"></a><p>Part No: 820-6566-13</p><p>March 2010</p><p>4150 Network Circle<br>Santa Clara, CA 95054<br>U.S.A.</p><p>Copyright 2010 Sun Microsystems, Inc.</p><p>This
-guide provides an introduction to the OpenSolaris releases, including instructions about how to
-install the current OpenSolaris release on your system.</p><p>The contents of this Documentation are
-subject to the Public Documentation License Version 1.01 (the "License"); you may only
-use this Documentation if you comply with the terms of this License. A
-copy of the License is available at http://www.opensolaris.org/os/community/documentation/license. Third-party URLs are referenced in this
-document and provide additional, related information. Sun is not responsible for the availability
-of third-party web sites mentioned in this document. Sun does not endorse and
-is not responsible or liable for any content, advertising, products, or other materials
-that are available on or through such sites or resources. Sun will not
-be responsible or liable for any actual or alleged damage or loss caused
-or alleged to be caused by or in connection with use of or
-reliance on any such content, goods, or services that are available on or
-through such sites or resources.</p><p>Sun Microsystems, Inc. has intellectual property rights relating
-to technology embodied in the product that is described in this document. In
-particular, and without limitation, these intellectual property rights may include one or more U.S.
-patents or pending patent applications in the U.S. and in other countries.</p><p>U.S. Government
-Rights – Commercial software. Government users are subject to the Sun Microsystems,
-Inc. standard license agreement and applicable provisions of the FAR and its supplements.</p><p>This
-distribution may include materials developed by third parties.</p><p>Parts of the product may
-be derived from Berkeley BSD systems, licensed from the University of California. UNIX
-is a registered trademark in the U.S. and other countries, exclusively licensed through
-X/Open Company, Ltd.</p><p>Sun, Sun Microsystems, the Sun logo, the Solaris logo, the
-Java Coffee Cup logo, docs.sun.com, NetBeans, OpenSolaris, Sun HPC ClusterTools, VirtualBox, Solaris JumpStart,
- Java, and Solaris are trademarks or registered trademarks of Sun Microsystems, Inc.
-in the U.S. and other countries. All SPARC trademarks are used under license
-and are trademarks or registered trademarks of SPARC International, Inc. in the U.S.
-and other countries. Products bearing SPARC trademarks are based upon an architecture developed
-by Sun Microsystems, Inc. </p><p>The OPEN LOOK and Sun<sup>TM</sup> Graphical User Interface was
-developed by Sun Microsystems, Inc. for its users and licensees. Sun acknowledges the
-pioneering efforts of Xerox in researching and developing the concept of visual or
-graphical user interfaces for the computer industry. Sun holds a non-exclusive license from
-Xerox to the Xerox Graphical User Interface, which license also covers Sun's licensees
-who implement OPEN LOOK GUIs and otherwise comply with Sun's written license agreements.</p><p>Products
-covered by and information contained in this publication are controlled by U.S. Export
-Control laws and may be subject to the export or import laws in
-other countries. Nuclear, missile, chemical or biological weapons or nuclear maritime end uses
-or end users, whether direct or indirect, are strictly prohibited. Export or reexport
-to countries subject to U.S. embargo or to entities identified on U.S. export
-exclusion lists, including, but not limited to, the denied persons and specially designated
-nationals lists is strictly prohibited.</p><p>DOCUMENTATION IS PROVIDED “AS IS” AND ALL EXPRESS OR IMPLIED
-CONDITIONS, REPRESENTATIONS AND WARRANTIES, INCLUDING ANY IMPLIED WARRANTY OF MERCHANTABILITY, FITNESS FOR A
-PARTICULAR PURPOSE OR NON-INFRINGEMENT, ARE DISCLAIMED, EXCEPT TO THE EXTENT THAT SUCH DISCLAIMERS ARE
-HELD TO BE LEGALLY INVALID.</p><p></p><p>Sun Microsystems, Inc. détient les droits de propriété intellectuelle
-relatifs à la technologie incorporée dans le produit qui est décrit dans ce document.
-En particulier, et ce sans limitation, ces droits de propriété intellectuelle peuvent inclure un
-ou plusieurs brevets américains ou des applications de brevet en attente aux Etats-Unis et
-dans d'autres pays.</p><p>Cette distribution peut comprendre des composants développés par des tierces personnes.</p><p>Certaines composants
-de ce produit peuvent être dérivées du logiciel Berkeley BSD, licenciés par l'Université de Californie.
-UNIX est une marque déposée aux Etats-Unis et dans d'autres pays; elle est licenciée
-exclusivement par X/Open Company, Ltd. </p><p>Sun, Sun Microsystems, le logo Sun, le
-logo Solaris, le logo Java Coffee Cup, docs.sun.com, NetBeans, OpenSolaris, Sun HPC ClusterTools,
-VirtualBox, Solaris JumpStart, Java et Solaris sont des marques de fabrique ou
-des marques déposées de Sun Microsystems, Inc. aux Etats-Unis et dans d'autres pays.
-Toutes les marques SPARC sont utilisées sous licence et sont des marques de fabrique ou
-des marques déposées de SPARC International, Inc. aux Etats-Unis et dans d'autres pays. Les produits
-portant les marques SPARC sont basés sur une architecture développée par Sun Microsystems, Inc.</p><p>L'interface
-d'utilisation graphique OPEN LOOK et Sun a été développée par Sun Microsystems, Inc. pour
-ses utilisateurs et licenciés. Sun reconnaît les efforts de pionniers de Xerox pour la recherche et
-le développement du concept des interfaces d'utilisation visuelle ou graphique pour l'industrie de l'informatique.
-Sun détient une licence non exclusive de Xerox sur l'interface d'utilisation graphique Xerox, cette
-licence couvrant également les licenciés de Sun qui mettent en place l'interface d'utilisation graphique OPEN
-LOOK et qui, en outre, se conforment aux licences écrites de Sun.</p><p>Les produits
-qui font l'objet de cette publication et les informations qu'il contient sont régis
-par la legislation américaine en matière de contrôle des exportations et peuvent être
-soumis au droit d'autres pays dans le domaine des exportations et importations. Les
-utilisations finales, ou utilisateurs finaux, pour des armes nucléaires, des missiles, des armes chimiques
-ou biologiques ou pour le nucléaire maritime, directement ou indirectement, sont strictement interdites.
-Les exportations ou réexportations vers des pays sous embargo des Etats-Unis, ou vers
-des entités figurant sur les listes d'exclusion d'exportation américaines, y compris, mais de
-manière non exclusive, la liste de personnes qui font objet d'un ordre de
-ne pas participer, d'une façon directe ou indirecte, aux exportations des produits ou des
-services qui sont régis par la legislation américaine en matière de contrôle des exportations et
-la liste de ressortissants spécifiquement designés, sont rigoureusement interdites.</p><p>LA DOCUMENTATION EST FOURNIE "EN L'ETAT"
-ET TOUTES AUTRES CONDITIONS, DECLARATIONS ET GARANTIES EXPRESSES OU TACITES SONT FORMELLEMENT EXCLUES, DANS
-LA MESURE AUTORISEE PAR LA LOI APPLICABLE, Y COMPRIS NOTAMMENT TOUTE GARANTIE IMPLICITE
-RELATIVE A LA QUALITE MARCHANDE, A L'APTITUDE A UNE UTILISATION PARTICULIERE OU A
-L'ABSENCE DE CONTREFACON. </p>
- </div>
- </td>
- </tr>
-
- <tr class="PageControls" valign="top">
- <td></td>
- <td>
- <table width="100%">
- <tr>
- <td>
- <a href="autoinstall.html">Previous</a>
- </td>
- <td align="right">
- <a href="index.html">Next</a>
- </td>
- </tr>
- </table>
- </td>
- </tr>
-</tbody>
-</table>
-
-
-</body>
-</html>
-
--- a/usr/src/cmd/installadm/docs/enable.html Wed Sep 29 16:37:00 2010 +0200
+++ /dev/null Thu Jan 01 00:00:00 1970 +0000
@@ -1,109 +0,0 @@
-<!DOCTYPE HTML PUBLIC "-//W3C//DTD HTML 4.01 Transitional//EN" "http://www.w3.org/TR/html4/loose.dtd">
-<html lang="en-US">
-
-<!-- -->
-<head>
-<!-- GenHTML revision 23436-->
-<meta http-equiv="Content-type" content="text/html; charset=iso-8859-1">
-<title>How to Enable and Disable Install Services - OpenSolaris 2010.03 Automated Installer Guide</title>
-<meta name="robots" content="index,follow">
-<meta name="robots" content="index,follow">
-<meta name="date" content="2010-03-01">
-<meta name="collection" content="reference">
-<link rel="stylesheet" type="text/css" href="css/elements.css">
-<link rel="stylesheet" type="text/css" href="css/opensol.css">
-</head>
-
-<body>
-
-
-<div class="Masthead">
- <div class="MastheadLogo">
- <a href="http://www.opensolaris.com"><img border="0" src="graphics/opensolaris_logo_trans.png"></img></a>
- </div>
- <div class="Title">OpenSolaris 2010.03 Automated Installer Guide</div>
-</div>
-<div class="headerbar"></div>
-
-
-<table class="Layout" border="0" cellspacing="0" width="100%">
-<tbody>
-
- <tr valign="top" class="PageControls">
- <td></td>
- <td>
- <table width="100%">
- <tr>
- <td>
- <a href="view.html">Previous</a>
- </td>
- <td align="right">
- <a href="smf.html">Next</a>
- </td>
- </tr>
- </table>
- </td>
- </tr>
-
- <tr valign="top">
- <td class="Navigation" width="200px"><p class="toc level1"><a href="docinfo.html">Document Information</a></p>
-<p class="toc level1 tocsp"><a href="index.html">1. What's New For Automated Installations</a></p>
-<p class="toc level1 tocsp"><a href="intro.html">2. Introduction to the Automated Installer</a></p>
-<p class="toc level1 tocsp"><a href="tasks.html">3. Automated Network Install Task Map</a></p>
-<p class="toc level1 tocsp"><a href="bootable.html">4. Automated Installations That Boot From Media</a></p>
-<p class="toc level1 tocsp"><a href="setup.html">5. Set up an Automated Install Server</a></p>
-<p class="toc level1 tocsp"><a href="administer.html">6. How to Administer an Automated Install Server</a></p>
-<p class="toc level2"><a href="add.html">How to Add Install Services</a></p>
-<p class="toc level2"><a href="delete.html">How to Delete Install Services</a></p>
-<p class="toc level2"><a href="view.html">How to Review What You Have on Your Server</a></p>
-<div id="scrolltoc" class="onpage">
-<p class="toc level2"><a href="">How to Enable and Disable Install Services</a></p>
-</div>
-<p class="toc level2"><a href="smf.html">How to Administer Install Services by Using the AI SMF Service</a></p>
-<p class="toc level1 tocsp"><a href="client.html">7. How to Administer a Custom Install Client</a></p>
-<p class="toc level1 tocsp"><a href="manifest.html">8. How to Administer Manifest Files</a></p>
-<p class="toc level1 tocsp"><a href="clients.html">9. How to Manage Client Installations</a></p>
-<p class="toc level1 tocsp"><a href="trouble.html">10. Troubleshooting and FAQs for the Automated Installer</a></p>
-<p class="toc level1 tocsp"><a href="appendix.html">11. Appendix</a></p>
-</td>
- <td class="ContentPane" width="705px">
-
- <div class="MainContent">
-
-
-<a name="enable"></a><h3>How to Enable and Disable Install Services</h3>
-<p>You can enable and disable install services on a system as follows:</p>
-
-<a name="enable2"></a><h4>Enable an Install Service</h4>
-<p>Use the following command to enable a specified install service.</p><pre># <tt>installadm enable <i>svcname</i></tt></pre><p>The <i>svcname</i> tag is required to specify the name of the install service
-to be enabled.</p><p>This command also enables the web server associated with the service.</p>
-
-<a name="disable"></a><h4>Disable an Install Service</h4>
-<p>Use the following command to disable a specified install service.</p><pre># <tt>installadm disable <i>svcname</i></tt></pre><p>The <i>svcname</i> tag is required to specify the name of the install service
-to be disabled.</p><p>This command also disables the web server associated with the service.</p>
- </div>
- </td>
- </tr>
-
- <tr class="PageControls" valign="top">
- <td></td>
- <td>
- <table width="100%">
- <tr>
- <td>
- <a href="view.html">Previous</a>
- </td>
- <td align="right">
- <a href="smf.html">Next</a>
- </td>
- </tr>
- </table>
- </td>
- </tr>
-</tbody>
-</table>
-
-
-</body>
-</html>
-
--- a/usr/src/cmd/installadm/docs/faq.html Wed Sep 29 16:37:00 2010 +0200
+++ /dev/null Thu Jan 01 00:00:00 1970 +0000
@@ -1,355 +0,0 @@
-<!DOCTYPE HTML PUBLIC "-//W3C//DTD HTML 4.01 Transitional//EN" "http://www.w3.org/TR/html4/loose.dtd">
-<html lang="en-US">
-
-<!-- -->
-<head>
-<!-- GenHTML revision 23436-->
-<meta http-equiv="Content-type" content="text/html; charset=iso-8859-1">
-<title>Frequently Asked Questions - OpenSolaris 2010.03 Automated Installer Guide</title>
-<meta name="robots" content="index,follow">
-<meta name="robots" content="index,follow">
-<meta name="date" content="2010-03-01">
-<meta name="collection" content="reference">
-<link rel="stylesheet" type="text/css" href="css/elements.css">
-<link rel="stylesheet" type="text/css" href="css/opensol.css">
-</head>
-
-<body>
-
-
-<div class="Masthead">
- <div class="MastheadLogo">
- <a href="http://www.opensolaris.com"><img border="0" src="graphics/opensolaris_logo_trans.png"></img></a>
- </div>
- <div class="Title">OpenSolaris 2010.03 Automated Installer Guide</div>
-</div>
-<div class="headerbar"></div>
-
-
-<table class="Layout" border="0" cellspacing="0" width="100%">
-<tbody>
-
- <tr valign="top" class="PageControls">
- <td></td>
- <td>
- <table width="100%">
- <tr>
- <td>
- <a href="setupfaq.html">Previous</a>
- </td>
- <td align="right">
- <a href="help.html">Next</a>
- </td>
- </tr>
- </table>
- </td>
- </tr>
-
- <tr valign="top">
- <td class="Navigation" width="200px"><p class="toc level1"><a href="docinfo.html">Document Information</a></p>
-<p class="toc level1 tocsp"><a href="index.html">1. What's New For Automated Installations</a></p>
-<p class="toc level1 tocsp"><a href="intro.html">2. Introduction to the Automated Installer</a></p>
-<p class="toc level1 tocsp"><a href="tasks.html">3. Automated Network Install Task Map</a></p>
-<p class="toc level1 tocsp"><a href="bootable.html">4. Automated Installations That Boot From Media</a></p>
-<p class="toc level1 tocsp"><a href="setup.html">5. Set up an Automated Install Server</a></p>
-<p class="toc level1 tocsp"><a href="administer.html">6. How to Administer an Automated Install Server</a></p>
-<p class="toc level1 tocsp"><a href="client.html">7. How to Administer a Custom Install Client</a></p>
-<p class="toc level1 tocsp"><a href="manifest.html">8. How to Administer Manifest Files</a></p>
-<p class="toc level1 tocsp"><a href="clients.html">9. How to Manage Client Installations</a></p>
-<p class="toc level1 tocsp"><a href="trouble.html">10. Troubleshooting and FAQs for the Automated Installer</a></p>
-<p class="toc level2"><a href="setupfaq.html">Troubleshooting Issues</a></p>
-<div id="scrolltoc" class="onpage">
-<p class="toc level2"><a href="">Frequently Asked Questions</a></p>
-</div>
-<p class="toc level2"><a href="help.html">Additional Resources</a></p>
-<p class="toc level1 tocsp"><a href="appendix.html">11. Appendix</a></p>
-</td>
- <td class="ContentPane" width="705px">
-
- <div class="MainContent">
-
-
-<a name="faq"></a><h3>Frequently Asked Questions</h3>
-
-
-<a name="switch"></a><h4>1. If I Do Not Have Access to the Tools on the System's Desktop, How Do I Switch to a Static IP System ?</h4>
-<p>The following steps can be used to configure a wired network interface to
-have a static IP address. You may need to consult with your
-network administrator in order to correctly perform these steps.</p>
-<hr><p><b>Caution - </b>If you are on the network, note that the system may disconnect as
-you perform the following procedure, becoming unreachable.</p>
-<hr>
-
-<ol><li><p>Become root and run the following series of commands.</p><pre># <tt>svcadm disable <i>network/physical:nwam</i></tt>
-# <tt>svcadm enable <i>network/physical:default</i></tt>
-# <tt>echo <i><IP_addr> > /etc/hostname.<ifname></i></tt>
-# <tt>echo <i><hostname> > /etc/nodename</i></tt></pre></li>
-<li><p>View <tt>/etc/hosts</tt> with an editor, as in the following command:</p><pre># <tt>vi /etc/hosts</tt></pre><p>And, append this line to the file, replacing the variables with the install server's IP address, hostname and loghost.</p><pre><tt><IP_addr> <hostname> <hostname>.local loghost</tt></pre><p>Then, 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:</p><pre>::1 localhost</pre><p>And, edit the line for the <tt>127.0.0.1</tt> entry to show the following:</p><pre>127.0.0.1 localhost</pre></li>
-<li><p>View <tt>/etc/netmasks</tt> with an editor, as in the following command:</p><pre># <tt>vi /etc/netmasks</tt></pre><p>And, append this line to the file, replacing the variables with your specifics. See <tt>netmasks(4)</tt>.</p><pre><tt><network> <netmask></tt></pre></li>
-<li><p>Run the following commands:</p><pre># <tt>ifconfig <ifname> plumb</tt>
-# <tt>ifconfig <ifname> <IP_addr> netmask <netmask> up</tt></pre></li>
-<li><p>If you use DNS to resolve hostnames, perform these additional steps:</p>
-<ol><li><p>Configure the file, <tt>/etc/resolv.conf(4)</tt>, to work with the DNS servers for your network. </p><p>An example of the <tt>/etc/resolv.conf</tt> file may look like this:</p><pre>domain example.com
- nameserver 192.168.1.118
- nameserver 192.168.2.220 </pre></li>
-<li><p>Run the following command:</p><pre># <tt>cp /etc/nsswitch.dns /etc/nsswitch.conf</tt></pre></li></ol>
-</li>
-<li><p>Configure a default route:</p><p>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. </p><p>To set up a static default route, add your network's default router IP address to the <tt>/etc/defaultrouter(4)</tt> file as shown in the following commands:</p><pre># <tt>echo <default_route_IP_addr> > /etc/defaultrouter</tt>
-# <tt>route add default <default_route_IP_addr></tt></pre></li></ol>
-
-
-<a name="wanboot"></a><h4>2. Does My SPARC Client Support WAN Boot?</h4>
-<p>In order to boot over the network, the automated installer requires WAN boot
-support for SPARC clients. You can check whether your client open boot prompt
-supports WAN boot by checking if <tt>network-boot-arguments</tt> is a valid variable that
-can be set in the <tt>eeprom</tt>. If the variable <tt>network-boot-arguments</tt> is displayed, or
-if it returns the output <tt>network-boot-arguments: data not available</tt>, the open boot prompt supports WAN boot
-installations.</p><pre># <tt>eeprom | grep network-boot-arguments</tt>
-network-boot-arguments: data not available</pre><p>If the command results in no output, then WAN Boot is not
-supported.</p><p>In addition, it is recommended that you update your firmware to include the
-current version of the Open Boot PROM (OBP) containing the latest WAN Boot
-fixes. The minimum OBP version for WAN Boot is version 4.17.1. For
-information about updating your OBP, see the “Sun System Handbook” at <a href="http://sunsolve.sun.com/">http://sunsolve.sun.com/</a>.</p>
-
-<a name="image"></a><h4>3. Where Do I Find the AI ISO Image That I Need?</h4>
-<p>Download an AI ISO image for x86 clients or for SPARC clients
-from <a href="http://www.opensolaris.com/get/">http://www.opensolaris.com/get/</a>. The automated installer will use this AI ISO image to install
-the OpenSolaris OS to your client systems.</p><p>Store the AI ISO image on your local file system. For example,
-store the image at <tt>/export/aiimages/osol-1003-ai-x86.iso</tt>. </p>
-
-<a name="modifymanifest"></a><h4>4. How Do I Modify a Custom Manifest File to Point to the Repository of My Choice?</h4>
-
-<hr><p><b>Note - </b>If you want to create a custom manifest for network installations, see <a href="customai.html">How to Create and Use a Custom AI Manifest</a>.
-For booting with AI media, see <a href="howbootable.html#bootablemanifest">Creating a Custom Manifest</a>.</p>
-<hr>
-<p>In your custom manifest, you can modify the following default repository information:</p><pre>...
-<ai_pkg_repo_default_publisher>
- <main url="http://pkg.opensolaris.org" publisher="opensolaris.org"/>
-</ai_pkg_repo_default_publisher>
-...</pre><p>If your IPS repository is <tt>pkg.mycompany.com</tt> and the publisher name is <tt>mycompany.com</tt>, change
-<tt>pkg.opensolaris.org</tt> to <tt>pkg.mycompany.com</tt> and <tt>opensolaris.org</tt> to <tt>mycompany.com</tt>.</p><pre>...
-<ai_pkg_repo_default_publisher>
- <main url="http://pkg.mycompany.com" publisher="mycompany.com"/>
-</ai_pkg_repo_default_publisher>
-...</pre>
-
-<a name="match"></a><h4>5. How Do I Install a Particular OpenSolaris Development Build?</h4>
-<p>Development builds of the OpenSolaris operating system are available in-between releases. See <a href="http://www.opensolaris.org/os/downloads/">http://www.opensolaris.org/os/downloads/</a>.</p><p>The build number or release of the AI ISO image that you
-specify in the <tt>installadm create-service</tt> command with the <tt>-s</tt> option must be the same
-build number or release of the OpenSolaris operating system that you specify in
-the AI manifest.</p><p>Check the build number or release for the AI ISO image when
-you download the image.</p><p>In the AI manifest, if you want to install a specific version
-of the OpenSolaris OS, you can specify the version in the package <tt>entire</tt>.
-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,
-<tt>entire</tt>, in the AI manifest. Use the following form:</p><pre><pkg_name="[email protected]#/></pre><p>The following example specifies that OpenSolaris build 111 be installed to the client.</p><pre><ai_manifest name="ai_packages">
-...
- <ai_install_packages>
- <pkg name="[email protected]"/>
- <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></pre>
-
-<a name="pool"></a><h4>6. How Do I Locate the Default AI Manifest Provided with an Install Service?</h4>
-<p>The default AI manifest for each install service is called <tt>default.xml</tt>. This
-file is located in the AI image associated with each install service at
-the location <tt><imagepath>/auto_install/default.xml</tt>, where <tt><imagepath></tt> is the image path directory that was used
-during the creation of the install service.</p><p>For example, if you are looking for the default manifest provided with the
-install service, <tt>201003sparc</tt>, you can use the following command to locate this file:</p><pre># installadm list -n 201003sparc
-
- Service Name Status Arch Port Image Path
- ------------ ------ ---- ---- ----------
- 201003sparc on sparc 45603 /export/images/201003sparc</pre><p>In the above example output, the default manifest provided with this service can
-be found at <tt>/export/images/201003sparc/auto_install/default.xml</tt>.</p>
-<hr><p><b>Note - </b>Do not modify the default AI manifest file. You can, however, copy this
-file and create a new default manifest for an install service. For instructions,
-see <a href="customai.html#changeai">Replacing a Default Manifest With a Custom Manifest</a>.</p>
-<hr>
-
-
-<a name="cleanup"></a><h4>7. How Can I Cleanup a Failed Service?</h4>
-<p>If <tt>installadm create-service</tt> fails to create an install service, use the following procedures to
-clean up.</p>
-<ol><li><p>Run <tt>installadm delete-service</tt> to remove the failed install service:</p><pre># <tt>installadm delete-service <tt>-x</tt> <i>svcname</i></tt></pre></li>
-<li><p>If that command fails with the following message:</p><pre>Error: The specified service does not exist: <svcname></pre><p>Try the following procedure:</p>
-<ol><li><p>Check if the automated installer webserver had been started for the service.</p><p>First, search for the port number used for the webserver by finding the <tt>dns-sd</tt> process associated with webserver. An example of how to do this search by using the <tt>ps(1)</tt> command, and the resulting output, is as follows:</p><pre># <tt>ps -ef | grep dns-sd | grep " svc2 "</tt> \
-<tt>root 11216 1 0 Apr 15 pts/2 0:00</tt> \
-<tt>/usr/bin/dns-sd -R svc2 _OSInstall._tcp local</tt> \
-<tt>46502 aiwebserver=192.168.2.1</tt></pre></li>
-<li><p>Kill this process, as in this example:</p><pre># <tt>kill <tt>-9</tt> <i>11216</i></tt></pre><p>The example output shows that the webserver for the service, <tt>svc2</tt>, is being served off of port 46502.</p></li>
-<li><p>Now search for the webserver process that's associated with this port number, and kill that process. See the following example:</p><pre><tt># ps -ef | grep installadm/webserver | grep 46502</tt> \
-<tt>root 11026 1 1 Apr 15 pts/2 71:35</tt> \
-<tt>/usr/bin/python2.4</tt> \
-<tt>/usr/lib/installadm/webserver -p 46502 /var/ai/46502</tt>
-<tt># kill -9 11026</tt></pre></li>
-<li><p>Now, remove the data directory for the install service, which also has that port number found above, 46502, in its path:</p><pre># <tt>rm <tt>-rf</tt> <i>/var/ai/46502</i></tt></pre></li></ol>
-</li>
-<li><p>To delete the target image path directory that was specified for the failed install service, remove the <tt><targetdir></tt> that you use in the <tt>installadm create-service</tt> command:</p><pre># <tt>rm <tt>-rf</tt> <i>targetdir</i></tt></pre></li></ol>
-<p>As a further step, see <a href="#unconf">8. How Do I Cleanup DHCP Configurations for a SPARC Install Service?</a></p>
-
-<a name="unconf"></a><h4>8. How Do I Cleanup DHCP Configurations for a SPARC Install Service?</h4>
-<p>When you run the <tt>installadm create-service</tt> command with the <tt>-i</tt> and <tt>-c</tt> 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.</p><p>For more information, see the <tt>dhcpmgr(1M)</tt> man page.</p>
-
-<a name="verbose"></a><h4>9. How Do I Run Automated Installations in Debug Verbose Mode?</h4>
-<p>You can run the installer in verbose debug mode, in order to
-capture more information about the installation in the <tt>install_log</tt> file.</p><p><b>For SPARC systems</b>, boot the system with the <tt>install_debug</tt> boot argument as follows:</p><p>For network installations:</p><pre>ok> boot net:dhcp - install install_debug </pre><p>For installations using media:</p><pre>ok> boot cdrom - install install_debug</pre><p><b>For x86 systems</b>, edit the GRUB menu and add the <tt>install_debug=enable</tt> as a boot property
-to the kernel line of the entry you wish to boot. For example,
-</p><pre>kernel$ ... -B install_media=...,install_debug=enable</pre><p>Alternatively for x86 systems, you can preset debug mode on the AI
-server by using the <tt>-b <property=value></tt> option with the <tt>installadm create-service</tt> and <tt>installadm create-client</tt> commands. This
-option presets that boot property in the GRUB menu for that service or
-client. For example,</p><pre>installadm create-client -e <MAC_address> -n <svc> -b install_debug=enable</pre>
-
-<a name="remote"></a><h4>10. How Do I Enable Remote Access to an AI Client by Using <tt>ssh</tt>?</h4>
-<p>You can enable network access to an automated install client by using
-<tt>ssh</tt>. You can use this access to remotely observe an installation process.</p><p>Enable this access by setting the option, <tt>livessh</tt>, to <tt>enable</tt> 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”.</p>
-<ul><li><p>For x86 systems, the <tt>menu.lst</tt> configuration file is created in the <tt>/tftpboot/</tt> directory with one of the following filename formats:</p>
-<ul><li><p>If you used the <tt>installadm create-service -n <service_name></tt> command, the filename is <tt>menu.lst.<service_name></tt>.</p></li>
-<li><p>If you used the <tt>installadm create-client -e <MAC_address></tt> command, the filename is <tt>menu.lst.01<MAC_address></tt>.</p></li></ul>
-<p>In this file, the options are provided as kernel parameters, such as the following:</p><pre><tt>kernel$ ... -B install_media=...,livessh=enable,install_debug=enable</tt></pre><p>The <tt>livessh</tt> option is this excerpt is set to <tt>enable</tt>.</p></li>
-<li><p>For SPARC systems, the <tt>install.conf</tt> file is populated in the <tt>ai_image_dest</tt> directory when an install service is created by using an <tt>installadm create-service</tt> command such as the following:</p><pre># installadm create-service ...[-n <service_name>] [-s <ai_iso_image>] <ai_image_dest>...</pre><p>In the <tt>install.conf</tt> file, the options are defined as name-value pairs, such as:</p><pre>$ <tt>cat <i><ai_image_dest>/install.conf</i></tt>
-...
-<tt><i>livessh=enable</i></tt>
-...</pre><p>The <tt>livessh</tt> option is this excerpt is set to <tt>enable</tt>.</p></li></ul>
-
-
-<a name="boot1"></a><h4>11. How Do I Boot the Install Environment Without Starting an Installation?</h4>
-
-<hr><p><b>Caution - </b>The booting procedures changed for the OpenSolaris 2010.03 release. To view the booting
-instructions for the prior OpenSolaris releases, see FAQ #11 at <a href="http://dlc.sun.com/osol/docs/content/2009.06/AIinstall/faq.html">http://dlc.sun.com/osol/docs/content/2009.06/AIinstall/faq.html</a>.</p>
-<hr>
-<p>To boot the install environment without starting an installation, boot without specifying the
-<tt>install</tt> flag as a boot argument as follows.</p>
-<ul><li><p>For a SPARC system, boot using the following command:</p><pre>OK <tt>boot net:dhcp</tt></pre><p>Since you did not include the <tt>install</tt> argument in the command, the automated installation will not start.</p></li>
-<li><p>For an x86 system, boot using one the following options:</p>
-<ul><li><p>For x86 installations that boot over the network, the GRUB menu displays as follows:</p><pre>OpenSolaris 2010.03 boot image
-OpenSolaris 2010.03 Automated Install</pre><p>The default GRUB menu entry, “OpenSolaris 2010.03 boot image,” boots the image without starting a hands-free automated installation.</p>
-<hr><p><b>Note - </b>To ensure the system boots without starting the installation, make sure the entry you choose to boot does not have the <tt>install=true</tt> boot property specified in its kernel line.</p>
-<hr>
-</li>
-<li><p>If you are booting an x86 system from media, edit the GRUB menu and remove the <tt>install=true</tt> boot property from kernel line of the entry you wish to boot.</p>
-<hr><p><b>Note - </b>In general for x86 installations, if the <tt>install=true</tt> boot property is specified in the kernel line of the GRUB entry you are booting from, the installation automatically starts. If you want to boot your x86 based system without initiating an automated installation, check that the GRUB boot entry does not specify the <tt>install=true</tt> boot property. If the property is specified, edit the kernel line of boot entry and remove the property. </p>
-<hr>
-</li></ul>
-</li></ul>
-<p>See the following related information:</p><p><a href="#verbose">9. How Do I Run Automated Installations in Debug Verbose Mode?</a></p><p>SPARC Error: <a href="sparcclient.html#disabled">5. Auto-installer Disabled</a></p><p>x86 Error: <a href="x86client.html#disabledx">5. Auto-installer Disabled</a></p>
-
-<a name="encrypt"></a><h4>12. How Do I Generate Encrypted Passwords?</h4>
-<p>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 <tt>/etc/shadow</tt> 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.</p><p>See <a href="customsc.html">How to Create Custom SC Manifest Files</a>.</p>
-
-<a name="back"></a><h4>13. Is the Automated Installer Backwards Compatible?</h4>
-<p>If the OpenSolaris 2010.03 release is installed on your install server, you can
-use AI images for either the OpenSolaris 2009.06 release or for the OpenSolaris
-2010.03 release. Otherwise, the OpenSolaris release installed on your server and the OpenSolaris
-release for the AI images that you plan to install to client systems
-must be the same release.</p><p>In addition, if you use an AI ISO image from an OpenSolaris
-development build to set up an install service, that AI ISO image will
-have a build number associated with it. This same build number must be
-specified in the AI manifest for the packages to be installed on the
-system. If you do not, in the manifest, specify a build number for
-the packages to be installed, the installation will use the most current version
-of the packages available in the IPS repository. If the build number for
-the packages does not match the build number for the AI ISO image,
-the installation could fail. For further information, see <a href="customai.html#version">Specifying Packages to Install a Specific Version of OpenSolaris</a>.</p>
-
-<a name="targetdisk"></a><h4>14. How is the Default Target Disk Selected?</h4>
-<p>You can use the <tt><ai_target_device></tt> tag to specify a particular target disk on
-which to install the OpenSolaris OS. See <a href="customai.html#iediskrepo">Defining a Target for the Installation</a>. If you do not
-specify a target disk, the automated installer chooses a default target for installing
-the OpenSolaris OS.</p><p>The default target disk is selected as follows:</p>
-<ol><li><p>The installer gets the recommended size for installing the OpenSolaris OS from the AI libraries. Currently, the recommended size is 13 GB.</p></li>
-<li><p>The installer searches for available disks on the client. The disks are found in the order they are reported by the <tt>liddiskmgt</tt> library.</p></li>
-<li><p>When the first disk is found, the installer checks the size of that disk.</p>
-<ul><li><p>If the size is greater than or equal to the recommended size, the installer selects the disk and returns to the installation procedure.</p></li>
-<li><p>If the size is less than the recommended size, the installer goes to the next disk to check the size.</p></li></ul>
-</li>
-<li><p>If there is no match, the automated installation fails.</p></li></ol>
-
-
-<a name="howstart"></a><h4>15. If I Booted Into the Install Environment Without Initiating an Installation, How Do I Start the Installation?</h4>
-<p>If you selected a boot option that does not initiate an installation, then
-use the <tt>svcadm</tt> command to initiate the installation as follows.</p>
-<ol><li><p>Login as root. The root password is opensolaris.</p></li>
-<li><p>Optionally, when booting from AI media, you could copy the default manifest from the media, as shown in these sample commands.</p><pre># cp /usr/share/auto_install/default.xml /tmp/ai_combined_manifest.xml</pre><pre># vi /tmp/ai_combined_manifest.xml</pre></li>
-<li><p>Enable the auto-installer service by running the following command.</p><pre>svcadm enable auto-installer:default</pre><p>The automated installation will begin.</p></li></ol>
-
-
-<a name="rename"></a><h4>16. What is the new AI Package Name?</h4>
-<p><b>Starting with the OpenSolaris 2010.03 release</b>, the <tt>SUNWinstalladm-tools</tt> package has been renamed as the <tt>installadm</tt> package. Both the
-old and new names are usable.</p>
-
-<a name="isc"></a><h4>17. How do I use ISC DHCP With the Automated Installer?</h4>
-<p>The OpenSolaris automated installer uses DHCP to perform hands-off installations. The automated install
-client receives its IP address, subnet mask, router, DNS server, and boot file
-though DHCP. The <tt>installadm</tt> tool used to configure an install server provides the
-commands to configure the Solaris DHCP server in the command output. If you
-want to use the ISC DHCP server instead of the Solaris DHCP server,
-see the instructions at <a href="http://blogs.sun.com/clayb/entry/how_to_use_isc_dhcp">http://blogs.sun.com/clayb/entry/how_to_use_isc_dhcp</a>.</p>
-
-<a name="vendor"></a><h4>18. How can I Check the Vendors for my Disks?</h4>
-<p>In most cases, you can check the vendors for your disks by
-using the <tt>iostat(1M)</tt> command or by using the target discovery test driver that
-is available in the AI image. See the following examples.</p><pre># iostat -En
-c2t1d0 Soft Errors: 0 Hard Errors: 0 Transport Errors: 0
-Vendor: HITACHI Product: HUS10733ASUN72G Revision: PA05 Serial No: 0602RW159S
-... </pre><pre># /opt/install-test/bin/test_td -dv
-Disk discovery
-Total number of disks: 2
--------------------------------------------------------------------------------
- num | name| vendor| ctype| mtype| rem| lbl| bsize|#of blocks|size [MB]|
--------------------------------------------------------------------------------
- 1 |* c2t0d0| SEAGATE| scsi| FIXED| No| V| 512| 71132959| 34732|
- 2 | c2t1d0| HITACHI| scsi| FIXED| No| V| 512| 143374738| 70007|
-------------------------------------------------------------------------------- </pre>
-<hr><p><b>Note - </b>These searches cannot identify the vendor for ATA disks.</p>
-<hr>
-
-
-<a name="passwords"></a><h4>19. What are the Default Passwords?</h4>
-<p>The default username is “jack” and the default user password is “jack.” The
-default root password is “opensolaris.” For remote access using <tt>ssh</tt>, use “jack” for both
-the username and password.</p><p>See, also, <a href="customsc.html#current">Modifying the SC Manifest</a> and <a href="#remote">10. How Do I Enable Remote Access to an AI Client by Using <tt>ssh</tt>?</a>.</p>
- </div>
- </td>
- </tr>
-
- <tr class="PageControls" valign="top">
- <td></td>
- <td>
- <table width="100%">
- <tr>
- <td>
- <a href="setupfaq.html">Previous</a>
- </td>
- <td align="right">
- <a href="help.html">Next</a>
- </td>
- </tr>
- </table>
- </td>
- </tr>
-</tbody>
-</table>
-
-
-</body>
-</html>
-
Binary file usr/src/cmd/installadm/docs/figures/AIinstall.gif has changed
Binary file usr/src/cmd/installadm/docs/figures/aiflow.gif has changed
Binary file usr/src/cmd/installadm/docs/figures/bootableAI_1.gif has changed
--- a/usr/src/cmd/installadm/docs/gentextid-45.html Wed Sep 29 16:37:00 2010 +0200
+++ /dev/null Thu Jan 01 00:00:00 1970 +0000
@@ -1,122 +0,0 @@
-<!DOCTYPE HTML PUBLIC "-//W3C//DTD HTML 4.01 Transitional//EN" "http://www.w3.org/TR/html4/loose.dtd">
-<html lang="en-US">
-
-<!-- -->
-<head>
-<!-- GenHTML revision 23436-->
-<meta http-equiv="Content-type" content="text/html; charset=iso-8859-1">
-<title>OpenSolaris 2010.03 Enhancements - OpenSolaris 2010.03 Automated Installer Guide</title>
-<meta name="robots" content="index,follow">
-<meta name="robots" content="index,follow">
-<meta name="date" content="2010-03-01">
-<meta name="collection" content="reference">
-<link rel="stylesheet" type="text/css" href="css/elements.css">
-<link rel="stylesheet" type="text/css" href="css/opensol.css">
-</head>
-
-<body>
-
-
-<div class="Masthead">
- <div class="MastheadLogo">
- <a href="http://www.opensolaris.com"><img border="0" src="graphics/opensolaris_logo_trans.png"></img></a>
- </div>
- <div class="Title">OpenSolaris 2010.03 Automated Installer Guide</div>
-</div>
-<div class="headerbar"></div>
-
-
-<table class="Layout" border="0" cellspacing="0" width="100%">
-<tbody>
-
- <tr valign="top" class="PageControls">
- <td></td>
- <td>
- <table width="100%">
- <tr>
- <td>
- <a href="index.html">Previous</a>
- </td>
- <td align="right">
- <a href="intro.html">Next</a>
- </td>
- </tr>
- </table>
- </td>
- </tr>
-
- <tr valign="top">
- <td class="Navigation" width="200px"><p class="toc level1"><a href="docinfo.html">Document Information</a></p>
-<p class="toc level1 tocsp"><a href="index.html">1. What's New For Automated Installations</a></p>
-<div id="scrolltoc" class="onpage">
-<p class="toc level2"><a href="">OpenSolaris 2010.03 Enhancements</a></p>
-</div>
-<p class="toc level1 tocsp"><a href="intro.html">2. Introduction to the Automated Installer</a></p>
-<p class="toc level1 tocsp"><a href="tasks.html">3. Automated Network Install Task Map</a></p>
-<p class="toc level1 tocsp"><a href="bootable.html">4. Automated Installations That Boot From Media</a></p>
-<p class="toc level1 tocsp"><a href="setup.html">5. Set up an Automated Install Server</a></p>
-<p class="toc level1 tocsp"><a href="administer.html">6. How to Administer an Automated Install Server</a></p>
-<p class="toc level1 tocsp"><a href="client.html">7. How to Administer a Custom Install Client</a></p>
-<p class="toc level1 tocsp"><a href="manifest.html">8. How to Administer Manifest Files</a></p>
-<p class="toc level1 tocsp"><a href="clients.html">9. How to Manage Client Installations</a></p>
-<p class="toc level1 tocsp"><a href="trouble.html">10. Troubleshooting and FAQs for the Automated Installer</a></p>
-<p class="toc level1 tocsp"><a href="appendix.html">11. Appendix</a></p>
-</td>
- <td class="ContentPane" width="705px">
-
- <div class="MainContent">
-
-
-<a name="gentextid-45"></a><h3>OpenSolaris 2010.03 Enhancements</h3>
-
-<ul><li><p>You can create an automated install (AI) CD, DVD, or, for x86 installations, a USB stick. Then, you can boot this AI media directly to initiate an automated installation. The system will still need network access, since the installation process retrieves packages from a network IPS repository. Booting the media directly is useful for cases where an AI server hasn't yet been set up on your network, or if you client system is unable to boot over the network to initiate a network AI install, for example, SPARC systems that do not have WAN Boot capability. See <a href="bootable.html">Chapter 4, Automated Installations That Boot From Media</a>.</p></li>
-<li><p>You can create and modify extended partitions as part of your automated installations. See <a href="customai.html#extpart">Creating an Extended Partition (x86 Clients Only)</a>.</p></li>
-<li><p>You can install to an iSCSI disk target using the automated installer. See <a href="customai.html#iscsi">Using an iSCSI Target for Installations</a>. </p></li>
-<li><p>You can use the following expanded options for defining a target for an automated installation.</p>
-<ul><li><p>Boot disk</p></li>
-<li><p>Device ID</p></li>
-<li><p>Physical device path</p></li>
-<li><p>Multiple criteria</p></li></ul>
-<p>See <a href="customai.html#iediskrepo">Defining a Target for the Installation</a>.</p></li>
-<li><p>You can use the new <tt>installadm list</tt> command options to view information about your existing install services, associated install clients, and available manifests. See <a href="view.html">How to Review What You Have on Your Server</a>.</p></li>
-<li><p>The default behavior for booting SPARC and x86 systems with AI images has changed as follows:</p>
-<ul><li><p>For SPARC systems, you must include the <tt>install</tt> argument in the boot command to initiate an installation as follows.</p><p>For installations that boot over the network:</p><pre><tt>boot net:dhcp <tt>- install</tt></tt></pre><p>For installations that boot from media:</p><pre><tt>boot cdrom - install</tt></pre>
-<hr><p><b>Note - </b>If you use the command without the <tt>install</tt> argument, the install environment boots without initiating an installation.</p>
-<hr>
-</li>
-<li><p>For x86 installations that boot over the network, the GRUB menu displays as follows:</p><pre>OpenSolaris 2010.03 boot image
-OpenSolaris 2010.03 Automated Install</pre><p>The default GRUB menu entry, “OpenSolaris 2010.03 boot image,” boots the image without starting a hands-free automated installation. You must select the second entry in the GRUB menu, “OpenSolaris 2010.03 Automated Install,” to initiate a “hands-free” automated installation.</p></li>
-<li><p>For x86 installations that boot from media, the GRUB menu displays as follows:</p><pre>OpenSolaris 2010.03 Automated Install custom
-OpenSolaris 2010.03 Automated Install
-...
-..</pre><p>The default GRUB menu entry, “OpenSolaris 2010.03 Automated Install custom,” prompts you for the location of a custom manifest before proceeding with the automated installation. You must select the second entry in the GRUB boot menu, “OpenSolaris 2010.03 Automated Install,” to initiate a “hands-free” automated installation. This selection uses the manifest on the media.</p></li>
-<li><p>In general for x86 installations, if the <tt>install=true</tt> boot property is specified in the kernel line of the GRUB entry you are booting from, the installation automatically starts. If you want to boot your x86 based system without initiating an automated installation, check that the GRUB boot entry does not specify the <tt>install=true</tt> boot property. If the property is specified, edit the kernel line of boot entry and remove the property. </p></li></ul>
-</li>
-<li><p>You can use the ISC DHCP server instead of the Solaris DHCP server. See <a href="faq.html#isc">17. How do I use ISC DHCP With the Automated Installer?</a>.</p></li></ul>
-
- </div>
- </td>
- </tr>
-
- <tr class="PageControls" valign="top">
- <td></td>
- <td>
- <table width="100%">
- <tr>
- <td>
- <a href="index.html">Previous</a>
- </td>
- <td align="right">
- <a href="intro.html">Next</a>
- </td>
- </tr>
- </table>
- </td>
- </tr>
-</tbody>
-</table>
-
-
-</body>
-</html>
-
Binary file usr/src/cmd/installadm/docs/graphics/header_gradientpart.png has changed
Binary file usr/src/cmd/installadm/docs/graphics/opensolaris_logo_trans.png has changed
--- a/usr/src/cmd/installadm/docs/help.html Wed Sep 29 16:37:00 2010 +0200
+++ /dev/null Thu Jan 01 00:00:00 1970 +0000
@@ -1,108 +0,0 @@
-<!DOCTYPE HTML PUBLIC "-//W3C//DTD HTML 4.01 Transitional//EN" "http://www.w3.org/TR/html4/loose.dtd">
-<html lang="en-US">
-
-<!-- -->
-<head>
-<!-- GenHTML revision 23436-->
-<meta http-equiv="Content-type" content="text/html; charset=iso-8859-1">
-<title>Additional Resources - OpenSolaris 2010.03 Automated Installer Guide</title>
-<meta name="robots" content="index,follow">
-<meta name="robots" content="index,follow">
-<meta name="date" content="2010-03-01">
-<meta name="collection" content="reference">
-<link rel="stylesheet" type="text/css" href="css/elements.css">
-<link rel="stylesheet" type="text/css" href="css/opensol.css">
-</head>
-
-<body>
-
-
-<div class="Masthead">
- <div class="MastheadLogo">
- <a href="http://www.opensolaris.com"><img border="0" src="graphics/opensolaris_logo_trans.png"></img></a>
- </div>
- <div class="Title">OpenSolaris 2010.03 Automated Installer Guide</div>
-</div>
-<div class="headerbar"></div>
-
-
-<table class="Layout" border="0" cellspacing="0" width="100%">
-<tbody>
-
- <tr valign="top" class="PageControls">
- <td></td>
- <td>
- <table width="100%">
- <tr>
- <td>
- <a href="faq.html">Previous</a>
- </td>
- <td align="right">
- <a href="appendix.html">Next</a>
- </td>
- </tr>
- </table>
- </td>
- </tr>
-
- <tr valign="top">
- <td class="Navigation" width="200px"><p class="toc level1"><a href="docinfo.html">Document Information</a></p>
-<p class="toc level1 tocsp"><a href="index.html">1. What's New For Automated Installations</a></p>
-<p class="toc level1 tocsp"><a href="intro.html">2. Introduction to the Automated Installer</a></p>
-<p class="toc level1 tocsp"><a href="tasks.html">3. Automated Network Install Task Map</a></p>
-<p class="toc level1 tocsp"><a href="bootable.html">4. Automated Installations That Boot From Media</a></p>
-<p class="toc level1 tocsp"><a href="setup.html">5. Set up an Automated Install Server</a></p>
-<p class="toc level1 tocsp"><a href="administer.html">6. How to Administer an Automated Install Server</a></p>
-<p class="toc level1 tocsp"><a href="client.html">7. How to Administer a Custom Install Client</a></p>
-<p class="toc level1 tocsp"><a href="manifest.html">8. How to Administer Manifest Files</a></p>
-<p class="toc level1 tocsp"><a href="clients.html">9. How to Manage Client Installations</a></p>
-<p class="toc level1 tocsp"><a href="trouble.html">10. Troubleshooting and FAQs for the Automated Installer</a></p>
-<p class="toc level2"><a href="setupfaq.html">Troubleshooting Issues</a></p>
-<p class="toc level2"><a href="faq.html">Frequently Asked Questions</a></p>
-<div id="scrolltoc" class="onpage">
-<p class="toc level2"><a href="">Additional Resources</a></p>
-</div>
-<p class="toc level1 tocsp"><a href="appendix.html">11. Appendix</a></p>
-</td>
- <td class="ContentPane" width="705px">
-
- <div class="MainContent">
-
-
-<a name="help"></a><h3>Additional Resources</h3>
-<p>Additional information and resources for using the automated installer are available at the
-following sites:</p>
-<ul><li><p>For general troubleshooting help, see the Release Notes posted at <a href="http://www.opensolaris.com/use/">http://www.opensolaris.com/use/</a>.</p></li>
-<li><p>Send questions or comments about the automated installer application to <tt>[email protected]</tt>.</p></li>
-<li><p>Submit bugs or enhancement requests to <a href="http://defect.opensolaris.org">http://defect.opensolaris.org</a> with the following information:</p>
-<ul><li><p>Category – Development</p></li>
-<li><p>Project - Installer</p></li>
-<li><p>Component - autoinstaller</p></li></ul>
-</li></ul>
-
- </div>
- </td>
- </tr>
-
- <tr class="PageControls" valign="top">
- <td></td>
- <td>
- <table width="100%">
- <tr>
- <td>
- <a href="faq.html">Previous</a>
- </td>
- <td align="right">
- <a href="appendix.html">Next</a>
- </td>
- </tr>
- </table>
- </td>
- </tr>
-</tbody>
-</table>
-
-
-</body>
-</html>
-
--- a/usr/src/cmd/installadm/docs/howbootable.html Wed Sep 29 16:37:00 2010 +0200
+++ /dev/null Thu Jan 01 00:00:00 1970 +0000
@@ -1,259 +0,0 @@
-<!DOCTYPE HTML PUBLIC "-//W3C//DTD HTML 4.01 Transitional//EN" "http://www.w3.org/TR/html4/loose.dtd">
-<html lang="en-US">
-
-<!-- -->
-<head>
-<!-- GenHTML revision 23436-->
-<meta http-equiv="Content-type" content="text/html; charset=iso-8859-1">
-<title>How to Install Using Media - OpenSolaris 2010.03 Automated Installer Guide</title>
-<meta name="robots" content="index,follow">
-<meta name="robots" content="index,follow">
-<meta name="date" content="2010-03-01">
-<meta name="collection" content="reference">
-<link rel="stylesheet" type="text/css" href="css/elements.css">
-<link rel="stylesheet" type="text/css" href="css/opensol.css">
-</head>
-
-<body>
-
-
-<div class="Masthead">
- <div class="MastheadLogo">
- <a href="http://www.opensolaris.com"><img border="0" src="graphics/opensolaris_logo_trans.png"></img></a>
- </div>
- <div class="Title">OpenSolaris 2010.03 Automated Installer Guide</div>
-</div>
-<div class="headerbar"></div>
-
-
-<table class="Layout" border="0" cellspacing="0" width="100%">
-<tbody>
-
- <tr valign="top" class="PageControls">
- <td></td>
- <td>
- <table width="100%">
- <tr>
- <td>
- <a href="bootableclientreq.html">Previous</a>
- </td>
- <td align="right">
- <a href="setup.html">Next</a>
- </td>
- </tr>
- </table>
- </td>
- </tr>
-
- <tr valign="top">
- <td class="Navigation" width="200px"><p class="toc level1"><a href="docinfo.html">Document Information</a></p>
-<p class="toc level1 tocsp"><a href="index.html">1. What's New For Automated Installations</a></p>
-<p class="toc level1 tocsp"><a href="intro.html">2. Introduction to the Automated Installer</a></p>
-<p class="toc level1 tocsp"><a href="tasks.html">3. Automated Network Install Task Map</a></p>
-<p class="toc level1 tocsp"><a href="bootable.html">4. Automated Installations That Boot From Media</a></p>
-<p class="toc level2"><a href="whybootable.html">Why Boot From AI Media?</a></p>
-<p class="toc level2"><a href="bootableclientreq.html">System Requirements for Automated Installations Using Media</a></p>
-<div id="scrolltoc" class="onpage">
-<p class="toc level2"><a href="">How to Install Using Media</a></p>
-</div>
-<p class="toc level1 tocsp"><a href="setup.html">5. Set up an Automated Install Server</a></p>
-<p class="toc level1 tocsp"><a href="administer.html">6. How to Administer an Automated Install Server</a></p>
-<p class="toc level1 tocsp"><a href="client.html">7. How to Administer a Custom Install Client</a></p>
-<p class="toc level1 tocsp"><a href="manifest.html">8. How to Administer Manifest Files</a></p>
-<p class="toc level1 tocsp"><a href="clients.html">9. How to Manage Client Installations</a></p>
-<p class="toc level1 tocsp"><a href="trouble.html">10. Troubleshooting and FAQs for the Automated Installer</a></p>
-<p class="toc level1 tocsp"><a href="appendix.html">11. Appendix</a></p>
-</td>
- <td class="ContentPane" width="705px">
-
- <div class="MainContent">
-
-
-<a name="howbootable"></a><h3>How to Install Using Media</h3>
-<p>To do an automated installation by booting from AI media, you must
-perform the following steps:</p>
-<ol><li><p>Check the system requirements for the client that you want to install.</p></li>
-<li><p>Download an AI image for either SPARC systems or x86 systems, and burn that image to a CD or other media.</p></li>
-<li><p>Create a custom manifest. You can either use the default manifest that is provided in the AI image, or you can set up a custom manifest and provide the location of this manifest when the client boots and installs.</p>
-<hr><p><b>Note - </b>This step is optional for the OpenSolaris 2010.03 release. However, if you want to install an OpenSolaris developmental build either before or after the OpenSolaris 2010.03 release, this step is required. You must customize the manifest to point to the IPS repository that contains the OpenSolaris development builds. See <a href="#bootablemanifest">Creating a Custom Manifest</a>.</p>
-<hr>
-</li>
-<li><p>Insert the CD or other media in the client system, and boot the client system from the device containing the AI media. Use an x86 GRUB menu option or a SPARC command at the OBP prompt to invoke an automated installation with either the default manifest or a specified custom manifest.</p></li></ol>
-<p>For complete instructions, see the following sections.</p>
-
-<a name="getbootableimage"></a><h4>Creating AI Media</h4><h6>Before You Begin</h6><p>Check the <a href="bootableclientreq.html">System Requirements for Automated Installations Using Media</a> for the client that you want to install.</p><ol>
-<li><b>Download either a SPARC AI image or x86 AI image from <a href="http://www.opensolaris.com/get/">http://www.opensolaris.com/get/</a>.</b>
-<hr><p><b>Note - </b>The same AI images can be used to perform either installations that boot
-from an install server or installations that boot from media.</p>
-<hr>
-<p>Alternately, download an AI image from <a href="http://opensolaris.org/os/downloads/">http://opensolaris.org/os/downloads/</a>, selecting an image either for the
-current release or for a particular OpenSolaris developer build.</p>
-<hr><p><b>Note - </b>Make sure that the build number or release of the AI image
-is the same build number or release for the OpenSolaris operating system that you
-plan to install.</p>
-<hr>
-</li>
-<li><b>Store the AI image on your local file system.</b><p>The AI image is an .iso image file. When you download the image,
-you store the .iso image file on your system.</p>
-<hr><p><b>Note - </b>You can, at this point, copy the default manifest from the .iso file,
-and modify that copy to create a custom manifest, as described in
-the next section.</p>
-<hr>
-</li>
-<li><b>Burn the .iso file onto a CD or other media.</b>
-<hr><p><b>Note - </b>The AI image is only about 250–350 MB.</p>
-<hr>
-</li></ol>
-
-<a name="bootablemanifest"></a><h4>Creating a Custom Manifest</h4><p>The default manifest, <tt>default.xml</tt>, in the AI image is an XML file that
-contains specifications for an x86 or SPARC installation. If you do not want
-to use this default manifest, you can create a custom manifest and store
-it on an HTTP server. When the client boots, you can specify
-the location of this custom manifest file.</p>
-<hr><p><b>Note - </b>Creating a custom manifest is optional for the OpenSolaris 2010.03 release. However, if
-you want to install an OpenSolaris developmental build instead of the OpenSolaris 2010.03
-release, a custom manifest is required. You must edit the custom manifest to
-point to the IPS repository that contains the OpenSolaris development builds as described
-in Step 1 below.</p>
-<hr>
-<p>After you download a SPARC image or an x86 image, the manifest
-file, named <tt>default.xml</tt>, is found in the following directory within the .iso file:</p><pre><tt>/usr/share/auto-install/default.xml</tt></pre><p>Alternately, you can see the complete file <tt>default.xml</tt> at <a href="aimanifest.html#defaultcri">Default Manifest File, <tt>default.xml</tt></a>.</p>
-<hr><p><b>Note - </b>The manifest file contents are identical, by default, for both x86 installations and
-SPARC installations.</p>
-<hr>
-<ol>
-<li><b>Review the default manifest file contents and decide whether you want to customize
-the installation specifications in this file.</b><p>For example, you may decide to use a different IPS repository instead
-of the opensolaris.org repository that is specified in the default manifest. Or, you may
-decide to install a different set of packages, modifying the list of packages
-in the manifest's <tt><ai_install_packages></tt> tag.</p>
-<hr><p><b>Note - </b>The manifest specifies the default IPS repository, <a href="http://pkg.opensolaris.org/release/">http://pkg.opensolaris.org/release/</a>. You can change the
-manifest to point to another repository of your choice. For example, if you
-want to install an OpenSolaris development build instead of installing the OpenSolaris 2010.03 release,
-the manifest needs to point to an IPS repository that contains the OpenSolaris
-development builds. You can change the IPS repository listed in the manifest to
-<a href="http://pkg.opensolaris.org/dev/">http://pkg.opensolaris.org/dev/</a>, a repository that contains these developmental builds.</p>
-<hr>
-<p>If you decide to change the installation specifications, you need to create a
-custom manifest as follows.</p></li>
-<li><b>Copy the default file and save the copy on an HTTP server.</b><p>The default manifest file can be obtained from <tt>auto_install/default.xml</tt> in the .iso
-image that you have downloaded. Or, you can copy by making a copy
-the same file from <a href="aimanifest.html#defaultcri">Default Manifest File, <tt>default.xml</tt></a>.</p><p>The following commands may be used to obtain the default manifest file from
-the .iso file that you have downloaded.</p><pre>$ lofi_dev=$(pfexec /usr/sbin/lofiadm -a <path to .iso file>)
-$ pfexec /usr/sbin/mount -o ro -F hsfs ${lofi_dev} /mnt
-$ cp /mnt/auto_install/default.xml <path to your copy of AI default manifest></pre>
-<hr><p><b>Note - </b>Then, use the following commands to clean up the <tt>lofiadm</tt> device and
-mount point.</p><pre>% pfexec /usr/sbin/umount /mnt
-% pfexec /usr/sbin/lofiadm -d ${lofi_dev} </pre>
-<hr>
-<p>You could save the copy, for example, at <tt>http://example.com/myfiles/mymanifest.xml</tt>.</p><p>Note the filename and the location of the new file. You'll be
-prompted to provide that information when the client boots.</p></li>
-<li><b>Modify the installation specifications in your custom manifest by manually editing the XML
-tag contents.</b><p>When you review <a href="aimanifest.html#defaultcri">Default Manifest File, <tt>default.xml</tt></a>, you can see that the default manifest file that
-you copied contains the <tt><ai_criteria_manifest></tt> section with the following subsections:</p>
-<ul><li><p><tt><ai_embedded_manifest></tt> - Specifies installation specifications</p></li>
-<li><p><tt><sc_embedded_manifest name = "AI"></tt> - Contains information for configuring the client after the installation is complete</p></li></ul>
-<p>You can edit tags in the main <tt><ai_criteria_manifest></tt> section or in either
-of the two subsections.</p><p>For instructions about editing your custom manifest, see the following:</p>
-<ul><li><p><a href="customai.html#aifields">Reviewing the AI Manifest Tags</a></p></li>
-<li><p><a href="customai.html#aioptions">Modifying AI Manifest Contents</a></p></li>
-<li><p><a href="customsc.html#current">Modifying the SC Manifest</a></p></li>
-<li><p><a href="criteria.html#criteriaie">Criteria Manifest Examples</a></p></li></ul>
-</li></ol>
-
-<a name="installbootable"></a><h4>Installing a System By Booting From AI Media</h4><p>Once you have created your AI media and, optionally, created a custom manifest,
-you are ready to install a client by booting from the AI
-media. As shown in the following image, installing a client using AI media
-involves 3 basic steps:</p>
-<ul><li><p>Insert the media and boot the client from the device containing the media.</p></li>
-<li><p>When the client boots, make an automated installation selection from the GRUB menu for x86 systems, or type a <tt>boot cdrom</tt> command for SPARC systems. The GRUB menu selection or boot command that you use specifies whether the installation will use the default manifest on the media or a custom manifest that you have stored on an HTTP server. The manifest contains the installation specifications. See instructions below for details.</p></li>
-<li><p>The packages to be installed are copied from an IPS repository on the network. The IPS repository location and package names are specified in the manifest.</p></li></ul>
-<img src="figures/bootableAI_1.gif" alt="User inserts media into client and boots client from media, using the boot image, manifest, and packages from IPS repository.l" width="404" height="377"></img><p>The following procedure provides detailed installation instructions.</p><ol>
-<li><b>Insert the AI media in the client system. </b><p>The media includes a boot image and a default manifest for the installation.</p></li>
-<li><b>Boot the system, specifying an automated installation that uses either the default manifest
-or a custom manifest.</b><p>Use either the x86 instructions or the SPARC instructions below for this step.</p><ul>
-<li><b>For x86 clients, select either a custom manifest or default manifest option from
-the GRUB menu.</b><pre>GNU GRUB version 0.97 (639K lower / 2078660K upper memory)
-
-OpenSolaris 2010.03 Automated Install custom
-OpenSolaris 2010.03 Automated Install
-OpenSolaris 2010.03 Automated Install custom ttya
-OpenSolaris 2010.03 Automated Install custom ttyb
-OpenSolaris 2010.03 Automated Install ttya
-OpenSolaris 2010.03 Automated Install ttyb
-Boot from Hard Disk
-
-Use the arrow keys to select which entry is highlighted.
-Press enter to boot the selected OS, 'e' to edit the
-commands before booting, or 'c' for a command-line.</pre><p>The default GRUB menu entry, “OpenSolaris 2010.03 Automated Install custom,” prompts you for
-the location of a custom manifest before proceeding with the automated installation.
-You must select the second entry in the GRUB boot menu, “OpenSolaris 2010.03
-Automated Install,” to initiate a “hands-free” automated installation. This selection uses the manifest
-on the media.</p>
-<hr><p><b>Note - </b>Note the following:</p>
-<ul><li><p>The installation options that state “custom” in the GRUB menu entry will use a custom manifest that you specify.</p></li>
-<li><p>In general, if <tt>install=true</tt> is specified in the kernel line for the GRUB entry that you use, the installation automatically begins. If you want to boot the x86 system without immediately starting an automated installation, check the GRUB menu entry that you're going to use. If <tt>install=true</tt> is specified in the kernel line for that GRUB entry, remove <tt>install=true</tt>. Then, the client will boot and a login screen will display, but the installation will not begin.</p></li>
-<li><p>The <tt>ttya</tt> and <tt>ttyb</tt> options in the GRUB menu send the screen output during the installation to serial console <tt>ttya (COM1)</tt> or <tt>ttyb (COM2)</tt>.</p></li></ul>
-
-<hr>
-<ul>
-<li><b><b>To use the default manifest for the automated installation, choose one of the following options from the GRUB menu:</b></b><pre>OpenSolaris 2010.03 Automated Install
-OpenSolaris 2010.03 Automated Install ttya
-OpenSolaris 2010.03 Automated Install ttyb</pre><p>When you select one of these options, the automated installation begins.</p></li>
-<li><b><b>To specify a custom manifest for the automated installation, choose one of the following options from the GRUB menu:</b></b><pre>OpenSolaris 2010.03 Automated Install custom
-OpenSolaris 2010.03 Automated Install custom ttya
-OpenSolaris 2010.03 Automated Install custom ttyb</pre><p>When you select one of these “custom” options, the following prompt displays:</p><pre>Enter the URL for the AI manifest [HTTP, default]:</pre><ol style="list-style-type: lower-alpha">
-<li><b>Type the path to a custom criteria manifest that you have previously set
-up on an HTTP server.</b><p>For example, type <tt>http://example.com/myfiles/mymanifest.xml</tt></p><p>After you provide that information, the automated installation begins.</p></li></ol>
-<hr><p><b>Note - </b>If you choose the “Boot from Hard Disk” option in the x86 GRUB
-menu, you will not start an automated installation. Instead, the client boots from
-its hard disk.</p>
-<hr>
-</li></ul></li>
-<li><b>For SPARC clients, type a boot command at the OBP prompt, specifying either
-a default or custom manifest as follows.</b><ul>
-<li><b>To boot and install using a custom manifest, type the following command:</b><pre>boot cdrom - install prompt</pre><p>The following prompt displays:</p><pre>Enter the URL for the AI manifest [HTTP, default]:</pre><ol style="list-style-type: lower-alpha">
-<li><b>Type the path to your custom manifest.</b><p>For example, type <tt>http://example.com/myfiles/mymanifest.xml</tt></p><p>The automated installation begins, using the specifications in the custom manifest.</p></li></ol></li>
-<li><b>To boot and install using the default manifest, type the following command:</b><pre>boot cdrom - install</pre><p>The automated installation begins, using the specifications in the default manifest.</p>
-<hr><p><b>Note - </b>The following SPARC boot commands will not start an automated installation:</p>
-<ul><li><p>This command boots the client from its hard disk:</p><pre>boot disk</pre></li>
-<li><p>The following command boots the client from the cdrom, a login screen is displayed, and the automated installation does not start</p><pre>boot cdrom</pre></li></ul>
-
-<hr>
-</li></ul></li></ul><p>The automated installation begins. This is a “hands-off” installation. Packages that are needed
-for the installation are automatically pulled from the IPS repository specified in the
-manifest. When the automated installation is complete, the output states whether the installation
-succeeded or failed.</p></li>
-<li><b>After the installation, you can review the installation log as follows.</b>
-<ul><li><p>If the installation failed, you can review the installation log at <tt>/tmp/install_log</tt>.</p></li>
-<li><p>If the installation was successful, you can find the log at either <tt>/tmp/install_log</tt> before you reboot the system, or at <tt>/var/sadm/system/logs/install_log</tt> after you reboot.</p></li></ul>
-<p>For troubleshooting information, see the following:</p>
-<ul><li><p><a href="bothclient.html">SPARC and x86 Client Installation Messages and Errors</a></p></li>
-<li><p><a href="trouble.html">Chapter 10, Troubleshooting and FAQs for the Automated Installer</a></p></li></ul>
-</li></ol>
- </div>
- </td>
- </tr>
-
- <tr class="PageControls" valign="top">
- <td></td>
- <td>
- <table width="100%">
- <tr>
- <td>
- <a href="bootableclientreq.html">Previous</a>
- </td>
- <td align="right">
- <a href="setup.html">Next</a>
- </td>
- </tr>
- </table>
- </td>
- </tr>
-</tbody>
-</table>
-
-
-</body>
-</html>
-
--- a/usr/src/cmd/installadm/docs/index.html Wed Sep 29 16:37:00 2010 +0200
+++ /dev/null Thu Jan 01 00:00:00 1970 +0000
@@ -1,94 +0,0 @@
-<!DOCTYPE HTML PUBLIC "-//W3C//DTD HTML 4.01 Transitional//EN" "http://www.w3.org/TR/html4/loose.dtd">
-<html lang="en-US">
-
-<!-- -->
-<head>
-<!-- GenHTML revision 23436-->
-<meta http-equiv="Content-type" content="text/html; charset=iso-8859-1">
-<title>What's New For Automated Installations - OpenSolaris 2010.03 Automated Installer Guide</title>
-<meta name="robots" content="index,follow">
-<meta name="robots" content="index,follow">
-<meta name="date" content="2010-03-01">
-<meta name="collection" content="reference">
-<link rel="stylesheet" type="text/css" href="css/elements.css">
-<link rel="stylesheet" type="text/css" href="css/opensol.css">
-</head>
-
-<body>
-
-
-<div class="Masthead">
- <div class="MastheadLogo">
- <a href="http://www.opensolaris.com"><img border="0" src="graphics/opensolaris_logo_trans.png"></img></a>
- </div>
- <div class="Title">OpenSolaris 2010.03 Automated Installer Guide</div>
-</div>
-<div class="headerbar"></div>
-
-
-<table class="Layout" border="0" cellspacing="0" width="100%">
-<tbody>
-
- <tr valign="top" class="PageControls">
- <td></td>
- <td>
- <table width="100%">
- <tr>
- <td>
- <a href="docinfo.html">Previous</a>
- </td>
- <td align="right">
- <a href="gentextid-45.html">Next</a>
- </td>
- </tr>
- </table>
- </td>
- </tr>
-
- <tr valign="top">
- <td class="Navigation" width="200px"><p class="toc level1"><a href="docinfo.html">Document Information</a></p>
-<div id="scrolltoc" class="onpage">
-<p class="toc level1 tocsp"><a href="">1. What's New For Automated Installations</a></p>
-</div>
-<p class="toc level2"><a href="gentextid-45.html">OpenSolaris 2010.03 Enhancements</a></p>
-<p class="toc level1 tocsp"><a href="intro.html">2. Introduction to the Automated Installer</a></p>
-<p class="toc level1 tocsp"><a href="tasks.html">3. Automated Network Install Task Map</a></p>
-<p class="toc level1 tocsp"><a href="bootable.html">4. Automated Installations That Boot From Media</a></p>
-<p class="toc level1 tocsp"><a href="setup.html">5. Set up an Automated Install Server</a></p>
-<p class="toc level1 tocsp"><a href="administer.html">6. How to Administer an Automated Install Server</a></p>
-<p class="toc level1 tocsp"><a href="client.html">7. How to Administer a Custom Install Client</a></p>
-<p class="toc level1 tocsp"><a href="manifest.html">8. How to Administer Manifest Files</a></p>
-<p class="toc level1 tocsp"><a href="clients.html">9. How to Manage Client Installations</a></p>
-<p class="toc level1 tocsp"><a href="trouble.html">10. Troubleshooting and FAQs for the Automated Installer</a></p>
-<p class="toc level1 tocsp"><a href="appendix.html">11. Appendix</a></p>
-</td>
- <td class="ContentPane" width="705px">
-
- <div class="MainContent">
- <a name="index"></a>Chapter 1<h3>What's New For Automated Installations</h3><p>The OpenSolaris 2010.03 release includes the following changes to the automated installer.</p>
- </div>
- </td>
- </tr>
-
- <tr class="PageControls" valign="top">
- <td></td>
- <td>
- <table width="100%">
- <tr>
- <td>
- <a href="docinfo.html">Previous</a>
- </td>
- <td align="right">
- <a href="gentextid-45.html">Next</a>
- </td>
- </tr>
- </table>
- </td>
- </tr>
-</tbody>
-</table>
-
-
-</body>
-</html>
-
--- a/usr/src/cmd/installadm/docs/initial.html Wed Sep 29 16:37:00 2010 +0200
+++ /dev/null Thu Jan 01 00:00:00 1970 +0000
@@ -1,175 +0,0 @@
-<!DOCTYPE HTML PUBLIC "-//W3C//DTD HTML 4.01 Transitional//EN" "http://www.w3.org/TR/html4/loose.dtd">
-<html lang="en-US">
-
-<!-- -->
-<head>
-<!-- GenHTML revision 23436-->
-<meta http-equiv="Content-type" content="text/html; charset=iso-8859-1">
-<title>How to Set Up an Install Server (Initial Steps) - OpenSolaris 2010.03 Automated Installer Guide</title>
-<meta name="robots" content="index,follow">
-<meta name="robots" content="index,follow">
-<meta name="date" content="2010-03-01">
-<meta name="collection" content="reference">
-<link rel="stylesheet" type="text/css" href="css/elements.css">
-<link rel="stylesheet" type="text/css" href="css/opensol.css">
-</head>
-
-<body>
-
-
-<div class="Masthead">
- <div class="MastheadLogo">
- <a href="http://www.opensolaris.com"><img border="0" src="graphics/opensolaris_logo_trans.png"></img></a>
- </div>
- <div class="Title">OpenSolaris 2010.03 Automated Installer Guide</div>
-</div>
-<div class="headerbar"></div>
-
-
-<table class="Layout" border="0" cellspacing="0" width="100%">
-<tbody>
-
- <tr valign="top" class="PageControls">
- <td></td>
- <td>
- <table width="100%">
- <tr>
- <td>
- <a href="basic.html">Previous</a>
- </td>
- <td align="right">
- <a href="simple.html">Next</a>
- </td>
- </tr>
- </table>
- </td>
- </tr>
-
- <tr valign="top">
- <td class="Navigation" width="200px"><p class="toc level1"><a href="docinfo.html">Document Information</a></p>
-<p class="toc level1 tocsp"><a href="index.html">1. What's New For Automated Installations</a></p>
-<p class="toc level1 tocsp"><a href="intro.html">2. Introduction to the Automated Installer</a></p>
-<p class="toc level1 tocsp"><a href="tasks.html">3. Automated Network Install Task Map</a></p>
-<p class="toc level1 tocsp"><a href="bootable.html">4. Automated Installations That Boot From Media</a></p>
-<p class="toc level1 tocsp"><a href="setup.html">5. Set up an Automated Install Server</a></p>
-<p class="toc level2"><a href="basic.html">Server Setup</a></p>
-<div id="scrolltoc" class="onpage">
-<p class="toc level2"><a href="">How to Set Up an Install Server (Initial Steps)</a></p>
-</div>
-<p class="toc level2"><a href="simple.html">How to Complete Server Setup (Simple Instructions)</a></p>
-<p class="toc level2"><a href="advancedsetup.html">How to Complete Server Setup (Advanced Instructions)</a></p>
-<p class="toc level1 tocsp"><a href="administer.html">6. How to Administer an Automated Install Server</a></p>
-<p class="toc level1 tocsp"><a href="client.html">7. How to Administer a Custom Install Client</a></p>
-<p class="toc level1 tocsp"><a href="manifest.html">8. How to Administer Manifest Files</a></p>
-<p class="toc level1 tocsp"><a href="clients.html">9. How to Manage Client Installations</a></p>
-<p class="toc level1 tocsp"><a href="trouble.html">10. Troubleshooting and FAQs for the Automated Installer</a></p>
-<p class="toc level1 tocsp"><a href="appendix.html">11. Appendix</a></p>
-</td>
- <td class="ContentPane" width="705px">
-
- <div class="MainContent">
-
-
-<a name="initial"></a><h3>How to Set Up an Install Server (Initial Steps)</h3>
-
-
-<a name="initial1"></a><h4>Initial Setup</h4><ol>
-<li><b>Install the most recent OpenSolaris operating system (OS) on the system that you
-will use as your install server. Or, upgrade your OpenSolaris system to the
-current release.</b><p>Use either the following x86 instructions or SPARC instructions:</p><ul>
-<li><b>For x86 systems, download the OpenSolaris Live CD image from <a href="http://www.opensolaris.com/get/">http://www.opensolaris.com/get/</a> and
-install the OpenSolaris OS on your system.</b><p>Live CD images are also available at <a href="http://opensolaris.org/os/downloads/">http://opensolaris.org/os/downloads/</a> for the current release and for
-OpenSolaris developer builds.</p><p>For instructions about installing a Live CD image onto your system or upgrading
-an existing OpenSolaris OS, see <a href="http://dlc.sun.com/osol/docs/content/2009.06/getstart/">Getting Started With OpenSolaris</a>.</p>
-<hr><p><b>Note - </b>To use the automated installer, you must have root access on your system.</p>
-<hr>
-</li>
-<li><b>To set up a SPARC system as your install server, first create SPARC
-AI media, and then use that media to install the OpenSolaris release on
-that system. For instructions, see <a href="bootable.html">Chapter 4, Automated Installations That Boot From Media</a>.</b>
-<hr><p><b>Note - </b>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.</p>
-<hr>
-</li></ul></li>
-<li><b>If you have access to the desktop for the OpenSolaris OS, and if
-your server is not already configured to use a static IP address,
-perform the following steps:</b>
-<hr><p><b>Note - </b>Alternately, see <a href="faq.html#switch">1. If I Do Not Have Access to the Tools on the System's Desktop, How Do I Switch to a Static IP System ?</a></p>
-<hr>
-<ol style="list-style-type: lower-alpha">
-<li><b>Go to the main task bar Menu and choose System>Administration>Network to open the
-Network Administration dialog box. Then choose Manual to launch the Network Settings
-tool.</b></li>
-<li><b>In the Connections tab, complete the following steps:</b><ol style="list-style-type: lower-roman">
-<li><b>Select the interface to configure with a static IP address, and click the
-Properties button.</b></li>
-<li><b>Check the Enable box to enable this connection.</b></li>
-<li><b>Check the Activate box to activate on boot.</b></li>
-<li><b>Type the IP address, Subnet mask, and Gateway in the appropriate boxes.</b></li>
-<li><b>Click OK.</b></li></ol></li>
-<li><b>In the General tab, fill in the system's hostname and domain name.</b></li>
-<li><b>In the DNS tab, if you use DNS to resolve host names,
-add the IP addresses of the DNS servers for the network.</b></li>
-<li><b>In the Hosts tab, complete the following steps:</b><ol style="list-style-type: lower-roman">
-<li><b>Select Add to add an entry for this system's hostname.</b></li>
-<li><b>Type the IP address in the IP Address box.</b></li>
-<li><b>Type the system's host name on the first line in the Alias
-box. Then, type “<hostname>.local” on the second line in the Alias box, replacing <hostname>
-with your host name. Then, type the word, “loghost,” on the third line
-in the Alias box. Click OK.</b></li>
-<li><b>Select the IPv4 loopback IP Address entry that has the address, <tt>127.0.0.1</tt>,
-and click the Properties button. Remove all lines from the Aliases box, except
-for the line that reads “localhost.” Click OK.</b></li>
-<li><b>Select the IPv6 loopback IP address entry that has the address, <tt>::1</tt>,
-and click the Properties button. Remove all lines from the Aliases box, except
-for the line that reads “localhost.” Click OK.</b></li></ol></li>
-<li><b>Click OK to close the Network Settings dialogue box.</b></li>
-<li><b>If you use DNS to resolve host names, enable DNS in the
-name-service switch file on this system as follows:</b><pre># <tt>cp <i>/etc/nsswitch.dns</i> <i>/etc/nsswitch.conf</i></tt></pre></li>
-<li><b>Reboot your system.</b></li></ol></li>
-<li><b>Install the latest <tt>installadm</tt> package by using Package Manager, or by using the
-following command:</b><pre># <tt>pkg install <i>installadm</i></tt></pre>
-<hr><p><b>Note - </b><b>Starting with the OpenSolaris 2010.03 release</b>, the <tt>SUNWinstalladm-tools</tt> package has been renamed as the <tt>installadm</tt> package. Both the
-old and new names are usable.</p>
-<hr>
-</li>
-<li><b>Download an AI ISO image for x86 clients or for SPARC clients from
-<a href="http://www.opensolaris.com/get/">http://www.opensolaris.com/get/</a>.</b><p>The automated installer uses this AI ISO image to install the OpenSolaris OS
-to your client systems.</p>
-<hr><p><b>Note - </b>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.</p>
-<hr>
-<p>Store the AI ISO image on your local file system. For example,
-store the image at <tt>/export/aiimages/osol-1003-ai-x86.iso</tt>.</p></li></ol><h6>Next Steps</h6><p>After you have completed the initial setup just described, choose one of the
-following options for completing the install server setup:</p>
-<ul><li><p><b>Simple Instructions</b> – 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 host names. See <a href="simple.html">How to Complete Server Setup (Simple Instructions)</a>.</p></li>
-<li><p><b>Advanced Instructions</b> – 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 <a href="advancedsetup.html">How to Complete Server Setup (Advanced Instructions)</a>.</p></li></ul>
-
- </div>
- </td>
- </tr>
-
- <tr class="PageControls" valign="top">
- <td></td>
- <td>
- <table width="100%">
- <tr>
- <td>
- <a href="basic.html">Previous</a>
- </td>
- <td align="right">
- <a href="simple.html">Next</a>
- </td>
- </tr>
- </table>
- </td>
- </tr>
-</tbody>
-</table>
-
-
-</body>
-</html>
-
--- a/usr/src/cmd/installadm/docs/installadm.html Wed Sep 29 16:37:00 2010 +0200
+++ /dev/null Thu Jan 01 00:00:00 1970 +0000
@@ -1,663 +0,0 @@
-<!DOCTYPE HTML PUBLIC "-//W3C//DTD HTML 4.01 Transitional//EN" "http://www.w3.org/TR/html4/loose.dtd">
-<html lang="en-US">
-
-<!-- -->
-<head>
-<!-- GenHTML revision 23436-->
-<meta http-equiv="Content-type" content="text/html; charset=iso-8859-1">
-<title>installadm(1M) Man Page - OpenSolaris 2010.03 Automated Installer Guide</title>
-<meta name="robots" content="index,follow">
-<meta name="robots" content="index,follow">
-<meta name="date" content="2010-03-01">
-<meta name="collection" content="reference">
-<link rel="stylesheet" type="text/css" href="css/elements.css">
-<link rel="stylesheet" type="text/css" href="css/opensol.css">
-</head>
-
-<body>
-
-
-<div class="Masthead">
- <div class="MastheadLogo">
- <a href="http://www.opensolaris.com"><img border="0" src="graphics/opensolaris_logo_trans.png"></img></a>
- </div>
- <div class="Title">OpenSolaris 2010.03 Automated Installer Guide</div>
-</div>
-<div class="headerbar"></div>
-
-
-<table class="Layout" border="0" cellspacing="0" width="100%">
-<tbody>
-
- <tr valign="top" class="PageControls">
- <td></td>
- <td>
- <table width="100%">
- <tr>
- <td>
- <a href="aimanifest.html">Previous</a>
- </td>
- <td align="right">
-
- </td>
- </tr>
- </table>
- </td>
- </tr>
-
- <tr valign="top">
- <td class="Navigation" width="200px"><p class="toc level1"><a href="docinfo.html">Document Information</a></p>
-<p class="toc level1 tocsp"><a href="index.html">1. What's New For Automated Installations</a></p>
-<p class="toc level1 tocsp"><a href="intro.html">2. Introduction to the Automated Installer</a></p>
-<p class="toc level1 tocsp"><a href="tasks.html">3. Automated Network Install Task Map</a></p>
-<p class="toc level1 tocsp"><a href="bootable.html">4. Automated Installations That Boot From Media</a></p>
-<p class="toc level1 tocsp"><a href="setup.html">5. Set up an Automated Install Server</a></p>
-<p class="toc level1 tocsp"><a href="administer.html">6. How to Administer an Automated Install Server</a></p>
-<p class="toc level1 tocsp"><a href="client.html">7. How to Administer a Custom Install Client</a></p>
-<p class="toc level1 tocsp"><a href="manifest.html">8. How to Administer Manifest Files</a></p>
-<p class="toc level1 tocsp"><a href="clients.html">9. How to Manage Client Installations</a></p>
-<p class="toc level1 tocsp"><a href="trouble.html">10. Troubleshooting and FAQs for the Automated Installer</a></p>
-<p class="toc level1 tocsp"><a href="appendix.html">11. Appendix</a></p>
-<p class="toc level2"><a href="aimanifest.html">AI Manifest Contents</a></p>
-<div id="scrolltoc" class="onpage">
-<p class="toc level2"><a href=""><tt>installadm(1M)</tt> Man Page</a></p>
-</div>
-</td>
- <td class="ContentPane" width="705px">
-
- <div class="MainContent">
-
-
-<a name="installadm"></a><h3><tt>installadm(1M)</tt> Man Page</h3>
-<pre>System Administration Commands installadm(1M)
-
-NAME
- installadm - Manages automated installations on a
- network
-
-
-SYNOPSIS
- /usr/sbin/installadm
-
- installadm create-service [-b <property>=<value>,...]
- [-f <bootfile>] [-n <svcname>] [-i <dhcp_ip_start>
- -c <count_of_ipaddr>] [-s <srcimage>] <targetdir>
-
- installadm delete-service [-x] <svcname>
-
- installadm list [-n <svcname>] [-c] [-m]
-
- 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 [-b <property>=<value>,...]
- [-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.
-
- -b <property>=<value>,...
- For x86 clients only, sets a property value
- in the service-specific menu.lst file in /tftpboot.
- Use this option to set boot properties that are
- specific to this service. This option can accept
- multiple property=value pairs.
-
- -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>] [-c] [-m]
-
- Lists all enabled install services on a server.
-
- -c
- Lists the clients of the install services on a local
- server.
-
- -m
- Lists the manifests associated with the install ser-
- vices on a local server.
-
- -n <svcname>
- Lists information about the specific install service
- on a local server. Or, if the -c option is speci-
- fied, lists the client information associated with
- the specified install service. Or, if the -m option
- is specified, lists the manifests 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>
- 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 1003x86 \
- -i 10.6.68.201 -c 5 -s \
- /export/aiimages/osol-1003-ai-x86.iso \
- /export/aiserver/osol-1003-ai-x86
-
-
- In this example, the terminal displays the progress
- as follows:
-
- Setting up the target image at
- /export/aiserver/osol-1003-ai-x86 ...
- Registering the service 1003x86._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-1003-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-1003-ai-x86 target directory.
- This net image enables client installations.
-
- The progress display shows that the install service,
- named 1003x86, is created.
-
- A boot file is created, also named 1003x86,
- 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-1003-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_1003x86.
-
-
-
- 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-1003-ai-x86 -n 1003x86
-
- 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 Solaris'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 Solaris'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 1003x86, and the net image at
- /export/aiserver/osol-1003-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 Solaris 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 Solaris 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/.
-
-
- Example 4: Use the following sample command to list the
- install services on a local server:
-
- # installadm list
-
- In this example, the terminal displays the following output:
-
-
-Service Name Status Arch Port Image Path
------------- ------ ---- ---- ----------
-svc-2008-11 off x86 45602 /export/server/osol-0811-ai-x86
-svc-2009-06 on x86 45601 /export/server/osol-1003-ai-x86
-svc-bld-127 on x86 45603 /export/server/osol-b127-ai-x86
-
-
- Example 5: Use the following sample command to list the
- clients for a specific install service of a local server:
-
- # installadm list -c -n svc-2009-06
-
- In this example, the terminal displays the following output:
-
-Service Name Client Address Arch Image Path
------------- -------------- ---- ----------
-svc-2009-06 01:C2:52:E6:4B:E1 x86 /export/server/osol-1003-ai-x86
-
-
- Example 6: Use the following sample command to list the man-
- ifests associated with a specific install service on a local
- server:
-
- # installadm list -m -n svc-2009-06
-
- In this example, the terminal displays the following output:
-
-Manifest Criteria
--------- --------
-devpublisher.xml arch = i86pc
- ipv4 = 010.000.002.015
- mac = 01:C4:51:E6:4B:E6 - 01:C4:51:E6:4B:E9
- mem = 2048 MB
-
-ATTRIBUTES
- See attributes(5) for descriptions of the following attri-
- butes:
- ____________________________________________________________
- | ATTRIBUTE TYPE | ATTRIBUTE VALUE |
- |_____________________________|_____________________________|
- | Availability | SUNWinstalladm-tools |
- |_____________________________|_____________________________|
- | Interface Stability | None / Under Development |
- |_____________________________|_____________________________|
-
-
-SEE ALSO
- pntadm(1M), dhcpmgr(1M), attributes(5)
-
- 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 December 11, 2009
- </pre>
- </div>
- </td>
- </tr>
-
- <tr class="PageControls" valign="top">
- <td></td>
- <td>
- <table width="100%">
- <tr>
- <td>
- <a href="aimanifest.html">Previous</a>
- </td>
- <td align="right">
-
- </td>
- </tr>
- </table>
- </td>
- </tr>
-</tbody>
-</table>
-
-
-</body>
-</html>
-
--- a/usr/src/cmd/installadm/docs/intro.html Wed Sep 29 16:37:00 2010 +0200
+++ /dev/null Thu Jan 01 00:00:00 1970 +0000
@@ -1,115 +0,0 @@
-<!DOCTYPE HTML PUBLIC "-//W3C//DTD HTML 4.01 Transitional//EN" "http://www.w3.org/TR/html4/loose.dtd">
-<html lang="en-US">
-
-<!-- -->
-<head>
-<!-- GenHTML revision 23436-->
-<meta http-equiv="Content-type" content="text/html; charset=iso-8859-1">
-<title>Introduction to the Automated Installer - OpenSolaris 2010.03 Automated Installer Guide</title>
-<meta name="robots" content="index,follow">
-<meta name="robots" content="index,follow">
-<meta name="date" content="2010-03-01">
-<meta name="collection" content="reference">
-<link rel="stylesheet" type="text/css" href="css/elements.css">
-<link rel="stylesheet" type="text/css" href="css/opensol.css">
-</head>
-
-<body>
-
-
-<div class="Masthead">
- <div class="MastheadLogo">
- <a href="http://www.opensolaris.com"><img border="0" src="graphics/opensolaris_logo_trans.png"></img></a>
- </div>
- <div class="Title">OpenSolaris 2010.03 Automated Installer Guide</div>
-</div>
-<div class="headerbar"></div>
-
-
-<table class="Layout" border="0" cellspacing="0" width="100%">
-<tbody>
-
- <tr valign="top" class="PageControls">
- <td></td>
- <td>
- <table width="100%">
- <tr>
- <td>
- <a href="gentextid-45.html">Previous</a>
- </td>
- <td align="right">
- <a href="whatis.html">Next</a>
- </td>
- </tr>
- </table>
- </td>
- </tr>
-
- <tr valign="top">
- <td class="Navigation" width="200px"><p class="toc level1"><a href="docinfo.html">Document Information</a></p>
-<p class="toc level1 tocsp"><a href="index.html">1. What's New For Automated Installations</a></p>
-<div id="scrolltoc" class="onpage">
-<p class="toc level1 tocsp"><a href="">2. Introduction to the Automated Installer</a></p>
-</div>
-<p class="toc level2"><a href="whatis.html">What Is an Automated Installation?</a></p>
-<p class="toc level2"><a href="use.html">How Do I Use the Automated Installer?</a></p>
-<p class="toc level2"><a href="clientinstall.html">How a Client Is Installed</a></p>
-<p class="toc level2"><a href="benefits.html">Automated Installation Benefits</a></p>
-<p class="toc level1 tocsp"><a href="tasks.html">3. Automated Network Install Task Map</a></p>
-<p class="toc level1 tocsp"><a href="bootable.html">4. Automated Installations That Boot From Media</a></p>
-<p class="toc level1 tocsp"><a href="setup.html">5. Set up an Automated Install Server</a></p>
-<p class="toc level1 tocsp"><a href="administer.html">6. How to Administer an Automated Install Server</a></p>
-<p class="toc level1 tocsp"><a href="client.html">7. How to Administer a Custom Install Client</a></p>
-<p class="toc level1 tocsp"><a href="manifest.html">8. How to Administer Manifest Files</a></p>
-<p class="toc level1 tocsp"><a href="clients.html">9. How to Manage Client Installations</a></p>
-<p class="toc level1 tocsp"><a href="trouble.html">10. Troubleshooting and FAQs for the Automated Installer</a></p>
-<p class="toc level1 tocsp"><a href="appendix.html">11. Appendix</a></p>
-</td>
- <td class="ContentPane" width="705px">
-
- <div class="MainContent">
- <a name="intro"></a>Chapter 2<h3>Introduction to the Automated Installer</h3><p>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.</p><p>Alternately, <b>starting with the OpenSolaris 2010.03 release</b>, you can simply download a SPARC or x86 AI image
-and burn it to media such as a CD, DVD, or, for x86
-installations, a USB stick. Then, you can boot that AI media directly to
-initiate an automated installation. The system will still need network access, since the
-installation process retrieves packages from a network IPS repository. Booting the media directly is
-useful for cases where an AI server hasn't yet been set up
-on your network, or if you client system is unable to boot over
-the network to initiate a network AI install.</p>
-<ul><li><p>If you want to install a few client systems by booting from a CD or other media, see <a href="bootable.html">Chapter 4, Automated Installations That Boot From Media</a>.</p>
-<hr><p><b>Note - </b>If your SPARC client system does not have WANboot capability, use this method.</p>
-<hr>
-</li>
-<li><p>If you want to perform multiple installations by booting over the network, review the following introduction to this tool.</p></li>
-<li><p>If you have already set up your network to perform automated installations, you can go to the instructions for <a href="administer.html">Chapter 6, How to Administer an Automated Install Server</a>.</p></li></ul>
-
- </div>
- </td>
- </tr>
-
- <tr class="PageControls" valign="top">
- <td></td>
- <td>
- <table width="100%">
- <tr>
- <td>
- <a href="gentextid-45.html">Previous</a>
- </td>
- <td align="right">
- <a href="whatis.html">Next</a>
- </td>
- </tr>
- </table>
- </td>
- </tr>
-</tbody>
-</table>
-
-
-</body>
-</html>
-
--- a/usr/src/cmd/installadm/docs/manifest.html Wed Sep 29 16:37:00 2010 +0200
+++ /dev/null Thu Jan 01 00:00:00 1970 +0000
@@ -1,107 +0,0 @@
-<!DOCTYPE HTML PUBLIC "-//W3C//DTD HTML 4.01 Transitional//EN" "http://www.w3.org/TR/html4/loose.dtd">
-<html lang="en-US">
-
-<!-- -->
-<head>
-<!-- GenHTML revision 23436-->
-<meta http-equiv="Content-type" content="text/html; charset=iso-8859-1">
-<title>How to Administer Manifest Files - OpenSolaris 2010.03 Automated Installer Guide</title>
-<meta name="robots" content="index,follow">
-<meta name="robots" content="index,follow">
-<meta name="date" content="2010-03-01">
-<meta name="collection" content="reference">
-<link rel="stylesheet" type="text/css" href="css/elements.css">
-<link rel="stylesheet" type="text/css" href="css/opensol.css">
-</head>
-
-<body>
-
-
-<div class="Masthead">
- <div class="MastheadLogo">
- <a href="http://www.opensolaris.com"><img border="0" src="graphics/opensolaris_logo_trans.png"></img></a>
- </div>
- <div class="Title">OpenSolaris 2010.03 Automated Installer Guide</div>
-</div>
-<div class="headerbar"></div>
-
-
-<table class="Layout" border="0" cellspacing="0" width="100%">
-<tbody>
-
- <tr valign="top" class="PageControls">
- <td></td>
- <td>
- <table width="100%">
- <tr>
- <td>
- <a href="delclient.html">Previous</a>
- </td>
- <td align="right">
- <a href="manifest1.html">Next</a>
- </td>
- </tr>
- </table>
- </td>
- </tr>
-
- <tr valign="top">
- <td class="Navigation" width="200px"><p class="toc level1"><a href="docinfo.html">Document Information</a></p>
-<p class="toc level1 tocsp"><a href="index.html">1. What's New For Automated Installations</a></p>
-<p class="toc level1 tocsp"><a href="intro.html">2. Introduction to the Automated Installer</a></p>
-<p class="toc level1 tocsp"><a href="tasks.html">3. Automated Network Install Task Map</a></p>
-<p class="toc level1 tocsp"><a href="bootable.html">4. Automated Installations That Boot From Media</a></p>
-<p class="toc level1 tocsp"><a href="setup.html">5. Set up an Automated Install Server</a></p>
-<p class="toc level1 tocsp"><a href="administer.html">6. How to Administer an Automated Install Server</a></p>
-<p class="toc level1 tocsp"><a href="client.html">7. How to Administer a Custom Install Client</a></p>
-<div id="scrolltoc" class="onpage">
-<p class="toc level1 tocsp"><a href="">8. How to Administer Manifest Files</a></p>
-</div>
-<p class="toc level2"><a href="manifest1.html">Types of Manifests</a></p>
-<p class="toc level2"><a href="customai.html">How to Create and Use a Custom AI Manifest</a></p>
-<p class="toc level2"><a href="customsc.html">How to Create Custom SC Manifest Files</a></p>
-<p class="toc level2"><a href="criteria.html">How to Create and Use a Criteria Manifest</a></p>
-<p class="toc level2"><a href="associate.html">How to Assign Manifests to a Client</a></p>
-<p class="toc level1 tocsp"><a href="clients.html">9. How to Manage Client Installations</a></p>
-<p class="toc level1 tocsp"><a href="trouble.html">10. Troubleshooting and FAQs for the Automated Installer</a></p>
-<p class="toc level1 tocsp"><a href="appendix.html">11. Appendix</a></p>
-</td>
- <td class="ContentPane" width="705px">
-
- <div class="MainContent">
- <a name="manifest"></a>Chapter 8<h3>How to Administer Manifest Files</h3><p>When you create install services by using the <tt>installadm create-service</tt> command, these services
-contain XML <b>manifest files</b>. 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.</p><p>See the following sections:</p>
-<ul><li><p><a href="manifest1.html">Types of Manifests</a></p></li>
-<li><p><a href="customai.html">How to Create and Use a Custom AI Manifest</a></p></li>
-<li><p><a href="customsc.html">How to Create Custom SC Manifest Files</a></p></li>
-<li><p><a href="criteria.html">How to Create and Use a Criteria Manifest</a></p></li>
-<li><p><a href="associate.html">How to Assign Manifests to a Client</a></p></li></ul>
-
- </div>
- </td>
- </tr>
-
- <tr class="PageControls" valign="top">
- <td></td>
- <td>
- <table width="100%">
- <tr>
- <td>
- <a href="delclient.html">Previous</a>
- </td>
- <td align="right">
- <a href="manifest1.html">Next</a>
- </td>
- </tr>
- </table>
- </td>
- </tr>
-</tbody>
-</table>
-
-
-</body>
-</html>
-
--- a/usr/src/cmd/installadm/docs/manifest1.html Wed Sep 29 16:37:00 2010 +0200
+++ /dev/null Thu Jan 01 00:00:00 1970 +0000
@@ -1,109 +0,0 @@
-<!DOCTYPE HTML PUBLIC "-//W3C//DTD HTML 4.01 Transitional//EN" "http://www.w3.org/TR/html4/loose.dtd">
-<html lang="en-US">
-
-<!-- -->
-<head>
-<!-- GenHTML revision 23436-->
-<meta http-equiv="Content-type" content="text/html; charset=iso-8859-1">
-<title>Types of Manifests - OpenSolaris 2010.03 Automated Installer Guide</title>
-<meta name="robots" content="index,follow">
-<meta name="robots" content="index,follow">
-<meta name="date" content="2010-03-01">
-<meta name="collection" content="reference">
-<link rel="stylesheet" type="text/css" href="css/elements.css">
-<link rel="stylesheet" type="text/css" href="css/opensol.css">
-</head>
-
-<body>
-
-
-<div class="Masthead">
- <div class="MastheadLogo">
- <a href="http://www.opensolaris.com"><img border="0" src="graphics/opensolaris_logo_trans.png"></img></a>
- </div>
- <div class="Title">OpenSolaris 2010.03 Automated Installer Guide</div>
-</div>
-<div class="headerbar"></div>
-
-
-<table class="Layout" border="0" cellspacing="0" width="100%">
-<tbody>
-
- <tr valign="top" class="PageControls">
- <td></td>
- <td>
- <table width="100%">
- <tr>
- <td>
- <a href="manifest.html">Previous</a>
- </td>
- <td align="right">
- <a href="customai.html">Next</a>
- </td>
- </tr>
- </table>
- </td>
- </tr>
-
- <tr valign="top">
- <td class="Navigation" width="200px"><p class="toc level1"><a href="docinfo.html">Document Information</a></p>
-<p class="toc level1 tocsp"><a href="index.html">1. What's New For Automated Installations</a></p>
-<p class="toc level1 tocsp"><a href="intro.html">2. Introduction to the Automated Installer</a></p>
-<p class="toc level1 tocsp"><a href="tasks.html">3. Automated Network Install Task Map</a></p>
-<p class="toc level1 tocsp"><a href="bootable.html">4. Automated Installations That Boot From Media</a></p>
-<p class="toc level1 tocsp"><a href="setup.html">5. Set up an Automated Install Server</a></p>
-<p class="toc level1 tocsp"><a href="administer.html">6. How to Administer an Automated Install Server</a></p>
-<p class="toc level1 tocsp"><a href="client.html">7. How to Administer a Custom Install Client</a></p>
-<p class="toc level1 tocsp"><a href="manifest.html">8. How to Administer Manifest Files</a></p>
-<div id="scrolltoc" class="onpage">
-<p class="toc level2"><a href="">Types of Manifests</a></p>
-</div>
-<p class="toc level2"><a href="customai.html">How to Create and Use a Custom AI Manifest</a></p>
-<p class="toc level2"><a href="customsc.html">How to Create Custom SC Manifest Files</a></p>
-<p class="toc level2"><a href="criteria.html">How to Create and Use a Criteria Manifest</a></p>
-<p class="toc level2"><a href="associate.html">How to Assign Manifests to a Client</a></p>
-<p class="toc level1 tocsp"><a href="clients.html">9. How to Manage Client Installations</a></p>
-<p class="toc level1 tocsp"><a href="trouble.html">10. Troubleshooting and FAQs for the Automated Installer</a></p>
-<p class="toc level1 tocsp"><a href="appendix.html">11. Appendix</a></p>
-</td>
- <td class="ContentPane" width="705px">
-
- <div class="MainContent">
-
-
-<a name="manifest1"></a><h3>Types of Manifests</h3>
-<p>In the automated installer application, three kinds of manifests are provided: <b>AI manifests</b>, <b>SC manifests</b>,
-and <b>criteria manifests</b>.</p>
-<ul><li><p>The <b>AI manifest</b> 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 <tt>SUNWauto-install-common</tt> package. This package is installed automatically when you install the <tt>installadm</tt> package on the install server. A copy of the AI schema is available at <tt>/usr/share/auto_install/ai_schema.rng</tt>.</p></li>
-<li><p>The <b>SC manifest</b> 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 username. The SC manifest uses DTD syntax. A copy of the schema is available at <tt>/usr/share/lib/xml/dtd/service_bundle.dtd.1</tt>.</p></li>
-<li><p> The <b>criteria manifest</b> 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 <tt>/usr/share/auto_install/criteria_schema.rng</tt> on the install server.</p>
-<hr><p><b>Note - </b>The default manifest that is included in the AI images functions as a criteria manifest, containing the full default contents for an AI manifest and an SC manifest.</p><p>See the default manifest at <a href="aimanifest.html#defaultcri">Default Manifest File, <tt>default.xml</tt></a>.</p>
-<hr>
-</li></ul>
-<p>Each manifest is described further in the following sections.</p>
- </div>
- </td>
- </tr>
-
- <tr class="PageControls" valign="top">
- <td></td>
- <td>
- <table width="100%">
- <tr>
- <td>
- <a href="manifest.html">Previous</a>
- </td>
- <td align="right">
- <a href="customai.html">Next</a>
- </td>
- </tr>
- </table>
- </td>
- </tr>
-</tbody>
-</table>
-
-
-</body>
-</html>
-
--- a/usr/src/cmd/installadm/docs/scenario.html Wed Sep 29 16:37:00 2010 +0200
+++ /dev/null Thu Jan 01 00:00:00 1970 +0000
@@ -1,148 +0,0 @@
-<!DOCTYPE HTML PUBLIC "-//W3C//DTD HTML 4.01 Transitional//EN" "http://www.w3.org/TR/html4/loose.dtd">
-<html lang="en-US">
-
-<!-- -->
-<head>
-<!-- GenHTML revision 23436-->
-<meta http-equiv="Content-type" content="text/html; charset=iso-8859-1">
-<title>Example: Creating a Custom Install Client - OpenSolaris 2010.03 Automated Installer Guide</title>
-<meta name="robots" content="index,follow">
-<meta name="robots" content="index,follow">
-<meta name="date" content="2010-03-01">
-<meta name="collection" content="reference">
-<link rel="stylesheet" type="text/css" href="css/elements.css">
-<link rel="stylesheet" type="text/css" href="css/opensol.css">
-</head>
-
-<body>
-
-
-<div class="Masthead">
- <div class="MastheadLogo">
- <a href="http://www.opensolaris.com"><img border="0" src="graphics/opensolaris_logo_trans.png"></img></a>
- </div>
- <div class="Title">OpenSolaris 2010.03 Automated Installer Guide</div>
-</div>
-<div class="headerbar"></div>
-
-
-<table class="Layout" border="0" cellspacing="0" width="100%">
-<tbody>
-
- <tr valign="top" class="PageControls">
- <td></td>
- <td>
- <table width="100%">
- <tr>
- <td>
- <a href="cclient.html">Previous</a>
- </td>
- <td align="right">
- <a href="delclient.html">Next</a>
- </td>
- </tr>
- </table>
- </td>
- </tr>
-
- <tr valign="top">
- <td class="Navigation" width="200px"><p class="toc level1"><a href="docinfo.html">Document Information</a></p>
-<p class="toc level1 tocsp"><a href="index.html">1. What's New For Automated Installations</a></p>
-<p class="toc level1 tocsp"><a href="intro.html">2. Introduction to the Automated Installer</a></p>
-<p class="toc level1 tocsp"><a href="tasks.html">3. Automated Network Install Task Map</a></p>
-<p class="toc level1 tocsp"><a href="bootable.html">4. Automated Installations That Boot From Media</a></p>
-<p class="toc level1 tocsp"><a href="setup.html">5. Set up an Automated Install Server</a></p>
-<p class="toc level1 tocsp"><a href="administer.html">6. How to Administer an Automated Install Server</a></p>
-<p class="toc level1 tocsp"><a href="client.html">7. How to Administer a Custom Install Client</a></p>
-<p class="toc level2"><a href="cclient.html">How to Set Up an Install Client</a></p>
-<div id="scrolltoc" class="onpage">
-<p class="toc level2"><a href="">Example: Creating a Custom Install Client</a></p>
-</div>
-<p class="toc level2"><a href="delclient.html">How to Delete an Install Client</a></p>
-<p class="toc level1 tocsp"><a href="manifest.html">8. How to Administer Manifest Files</a></p>
-<p class="toc level1 tocsp"><a href="clients.html">9. How to Manage Client Installations</a></p>
-<p class="toc level1 tocsp"><a href="trouble.html">10. Troubleshooting and FAQs for the Automated Installer</a></p>
-<p class="toc level1 tocsp"><a href="appendix.html">11. Appendix</a></p>
-</td>
- <td class="ContentPane" width="705px">
-
- <div class="MainContent">
-
-
-<a name="scenario"></a><h3>Example: Creating a Custom Install Client</h3>
-<p>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.</p><p><b>Use the following example command.</b></p><pre># <tt>installadm create-client <tt>-b</tt> <i>"console=ttya"</i> <tt>-e</tt> <i>0:e0:81:5d:bf:e0</i></tt> \
-<tt><tt>-n</tt> <i>1003x86</i></tt></pre><p>The following output is displayed:</p><pre>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 the Solaris 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 the Solaris DHCP server, run pntadm(1M)).</pre>
-<ul><li><p>Using the <tt>-b</tt> option, the command sets the console value, <tt>console=ttya</tt>, in the client-specific <tt>menu.lst file</tt> in <tt>/tftpboot</tt>.</p></li>
-<li><p>Using the <tt>-e</tt> option, the command specifies the MAC address, <tt>0:e0:81:5d:bf:e0</tt>, of a particular client that you want to customize.</p></li>
-<li><p>Using the <tt>-n</tt> option, the command specifies an install service name, <tt>1003x86</tt>, that you want the client to use for installation.</p></li></ul>
-<p>You can view the DHCP configuration results in the DHCP table with
-the DHCP Manager by using the <tt>/usr/sadm/admin/bin/dhcpmgr</tt> utility.</p><p>Also, you can go to the <tt>/tftpboot</tt> directory and view the results of
-the command as follows.</p><pre># 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=1000
-title OpenSolaris 2010.03 boot image
- kernel$ /I86PC.OpenSolaris-1/platform/i86pc/kernel/$ISADIR/unix
--B install_media=http://135.134.0.10:5555/export/aiserver/osol-1003-ai-x86,
-install_service=osol-1003-ai-x86,install_svc_address=135.134.0.10:46501
- module$ /I86PC.OpenSolaris-1/platform/i86pc/$ISADIR/boot_archive
-title OpenSolaris 2010.03 Automated Install
- kernel$ /I86PC.OpenSolaris-1/platform/i86pc/kernel/$ISADIR/unix
--B install=true,install_media=http://135.134.0.10:5555/export/aiserver/osol-1003-ai-x86,
-install_service=osol-1003-ai-x86,install_svc_address=135.134.0.10:46501
- module$ /I86PC.OpenSolaris-1/platform/i86pc/$ISADIR/boot_archive</pre><p>See the following additional examples about how to set up custom x86 and
-SPARC clients:</p>
-<ul><li><p><a href="add.html#service">Example: How to Set Up a Server and Multiple x86 Clients</a></p></li>
-<li><p><a href="add.html#diffsystem">Example: How to Set Up a Server to Install SPARC and x86 Clients</a></p></li></ul>
-
- </div>
- </td>
- </tr>
-
- <tr class="PageControls" valign="top">
- <td></td>
- <td>
- <table width="100%">
- <tr>
- <td>
- <a href="cclient.html">Previous</a>
- </td>
- <td align="right">
- <a href="delclient.html">Next</a>
- </td>
- </tr>
- </table>
- </td>
- </tr>
-</tbody>
-</table>
-
-
-</body>
-</html>
-
--- a/usr/src/cmd/installadm/docs/setup.html Wed Sep 29 16:37:00 2010 +0200
+++ /dev/null Thu Jan 01 00:00:00 1970 +0000
@@ -1,99 +0,0 @@
-<!DOCTYPE HTML PUBLIC "-//W3C//DTD HTML 4.01 Transitional//EN" "http://www.w3.org/TR/html4/loose.dtd">
-<html lang="en-US">
-
-<!-- -->
-<head>
-<!-- GenHTML revision 23436-->
-<meta http-equiv="Content-type" content="text/html; charset=iso-8859-1">
-<title>Set up an Automated Install Server - OpenSolaris 2010.03 Automated Installer Guide</title>
-<meta name="robots" content="index,follow">
-<meta name="robots" content="index,follow">
-<meta name="date" content="2010-03-01">
-<meta name="collection" content="reference">
-<link rel="stylesheet" type="text/css" href="css/elements.css">
-<link rel="stylesheet" type="text/css" href="css/opensol.css">
-</head>
-
-<body>
-
-
-<div class="Masthead">
- <div class="MastheadLogo">
- <a href="http://www.opensolaris.com"><img border="0" src="graphics/opensolaris_logo_trans.png"></img></a>
- </div>
- <div class="Title">OpenSolaris 2010.03 Automated Installer Guide</div>
-</div>
-<div class="headerbar"></div>
-
-
-<table class="Layout" border="0" cellspacing="0" width="100%">
-<tbody>
-
- <tr valign="top" class="PageControls">
- <td></td>
- <td>
- <table width="100%">
- <tr>
- <td>
- <a href="howbootable.html">Previous</a>
- </td>
- <td align="right">
- <a href="basic.html">Next</a>
- </td>
- </tr>
- </table>
- </td>
- </tr>
-
- <tr valign="top">
- <td class="Navigation" width="200px"><p class="toc level1"><a href="docinfo.html">Document Information</a></p>
-<p class="toc level1 tocsp"><a href="index.html">1. What's New For Automated Installations</a></p>
-<p class="toc level1 tocsp"><a href="intro.html">2. Introduction to the Automated Installer</a></p>
-<p class="toc level1 tocsp"><a href="tasks.html">3. Automated Network Install Task Map</a></p>
-<p class="toc level1 tocsp"><a href="bootable.html">4. Automated Installations That Boot From Media</a></p>
-<div id="scrolltoc" class="onpage">
-<p class="toc level1 tocsp"><a href="">5. Set up an Automated Install Server</a></p>
-</div>
-<p class="toc level2"><a href="basic.html">Server Setup</a></p>
-<p class="toc level2"><a href="initial.html">How to Set Up an Install Server (Initial Steps)</a></p>
-<p class="toc level2"><a href="simple.html">How to Complete Server Setup (Simple Instructions)</a></p>
-<p class="toc level2"><a href="advancedsetup.html">How to Complete Server Setup (Advanced Instructions)</a></p>
-<p class="toc level1 tocsp"><a href="administer.html">6. How to Administer an Automated Install Server</a></p>
-<p class="toc level1 tocsp"><a href="client.html">7. How to Administer a Custom Install Client</a></p>
-<p class="toc level1 tocsp"><a href="manifest.html">8. How to Administer Manifest Files</a></p>
-<p class="toc level1 tocsp"><a href="clients.html">9. How to Manage Client Installations</a></p>
-<p class="toc level1 tocsp"><a href="trouble.html">10. Troubleshooting and FAQs for the Automated Installer</a></p>
-<p class="toc level1 tocsp"><a href="appendix.html">11. Appendix</a></p>
-</td>
- <td class="ContentPane" width="705px">
-
- <div class="MainContent">
- <a name="setup"></a>Chapter 5<h3>Set up an Automated Install Server</h3><p>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.</p>
- </div>
- </td>
- </tr>
-
- <tr class="PageControls" valign="top">
- <td></td>
- <td>
- <table width="100%">
- <tr>
- <td>
- <a href="howbootable.html">Previous</a>
- </td>
- <td align="right">
- <a href="basic.html">Next</a>
- </td>
- </tr>
- </table>
- </td>
- </tr>
-</tbody>
-</table>
-
-
-</body>
-</html>
-
--- a/usr/src/cmd/installadm/docs/setupfaq.html Wed Sep 29 16:37:00 2010 +0200
+++ /dev/null Thu Jan 01 00:00:00 1970 +0000
@@ -1,201 +0,0 @@
-<!DOCTYPE HTML PUBLIC "-//W3C//DTD HTML 4.01 Transitional//EN" "http://www.w3.org/TR/html4/loose.dtd">
-<html lang="en-US">
-
-<!-- -->
-<head>
-<!-- GenHTML revision 23436-->
-<meta http-equiv="Content-type" content="text/html; charset=iso-8859-1">
-<title>Troubleshooting Issues - OpenSolaris 2010.03 Automated Installer Guide</title>
-<meta name="robots" content="index,follow">
-<meta name="robots" content="index,follow">
-<meta name="date" content="2010-03-01">
-<meta name="collection" content="reference">
-<link rel="stylesheet" type="text/css" href="css/elements.css">
-<link rel="stylesheet" type="text/css" href="css/opensol.css">
-</head>
-
-<body>
-
-
-<div class="Masthead">
- <div class="MastheadLogo">
- <a href="http://www.opensolaris.com"><img border="0" src="graphics/opensolaris_logo_trans.png"></img></a>
- </div>
- <div class="Title">OpenSolaris 2010.03 Automated Installer Guide</div>
-</div>
-<div class="headerbar"></div>
-
-
-<table class="Layout" border="0" cellspacing="0" width="100%">
-<tbody>
-
- <tr valign="top" class="PageControls">
- <td></td>
- <td>
- <table width="100%">
- <tr>
- <td>
- <a href="trouble.html">Previous</a>
- </td>
- <td align="right">
- <a href="faq.html">Next</a>
- </td>
- </tr>
- </table>
- </td>
- </tr>
-
- <tr valign="top">
- <td class="Navigation" width="200px"><p class="toc level1"><a href="docinfo.html">Document Information</a></p>
-<p class="toc level1 tocsp"><a href="index.html">1. What's New For Automated Installations</a></p>
-<p class="toc level1 tocsp"><a href="intro.html">2. Introduction to the Automated Installer</a></p>
-<p class="toc level1 tocsp"><a href="tasks.html">3. Automated Network Install Task Map</a></p>
-<p class="toc level1 tocsp"><a href="bootable.html">4. Automated Installations That Boot From Media</a></p>
-<p class="toc level1 tocsp"><a href="setup.html">5. Set up an Automated Install Server</a></p>
-<p class="toc level1 tocsp"><a href="administer.html">6. How to Administer an Automated Install Server</a></p>
-<p class="toc level1 tocsp"><a href="client.html">7. How to Administer a Custom Install Client</a></p>
-<p class="toc level1 tocsp"><a href="manifest.html">8. How to Administer Manifest Files</a></p>
-<p class="toc level1 tocsp"><a href="clients.html">9. How to Manage Client Installations</a></p>
-<p class="toc level1 tocsp"><a href="trouble.html">10. Troubleshooting and FAQs for the Automated Installer</a></p>
-<div id="scrolltoc" class="onpage">
-<p class="toc level2"><a href="">Troubleshooting Issues</a></p>
-</div>
-<p class="toc level2"><a href="faq.html">Frequently Asked Questions</a></p>
-<p class="toc level2"><a href="help.html">Additional Resources</a></p>
-<p class="toc level1 tocsp"><a href="appendix.html">11. Appendix</a></p>
-</td>
- <td class="ContentPane" width="705px">
-
- <div class="MainContent">
-
-
-<a name="setupfaq"></a><h3>Troubleshooting Issues</h3>
-
-
-<a name="dhcperr"></a><h4>1. <tt>installadm create-service</tt> Fails</h4>
-<p>The following error message is displayed:</p><pre># installadm create-service -n sparc_install_service -i
-192.168.135.21 -c 2 -s /export/images/osol-1003-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.0.10 does not exist.
-pntadm: Table for 192.168.0.10 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.0.10 does not exist.
-pntadm: Table for 192.168.0.10 does not exist.
-Creating SPARC configuration file</pre><p>The <tt>installadm</tt> 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:</p>
-<ul><li><p>The SMF service, <tt>dhcp-server</tt>, might not be available on the system. Check for the <tt>dhcp-server</tt> by running the following command:</p><pre># <tt>svcs dhcp-server</tt></pre></li>
-<li><p>Check whether <tt>/etc/netmasks</tt> has the wrong netmasks for the network that is being set up.</p></li>
-<li><p>Check that the node name is set to have the loop back address of <tt>127.0.0.1</tt>.</p></li>
-<li><p>The OpenSolaris release on your install server might need to be upgraded. If the OpenSolaris 2010.03 release is installed on your install server, you can use AI images for either the OpenSolaris 2009.06 release or for the OpenSolaris 2010.03 release. Otherwise, the OpenSolaris release installed on your server and the OpenSolaris release for the AI images that you plan to install to client systems must be the same release.</p><p>In addition, if you use an AI ISO image from an OpenSolaris development build to set up an install service, that AI ISO image will have a build number associated with it. This same build number must be specified in the AI manifest for the packages to be installed on the system. If you do not, in the manifest, specify a build number for the packages to be installed, the installation will use the most current version of the packages available in the IPS repository. If the build number for the packages does not match the build number for the AI ISO image, the installation could fail. For further information, see <a href="customai.html#version">Specifying Packages to Install a Specific Version of OpenSolaris</a>.</p></li></ul>
-<p>Make any needed corrections to fix the problems that you found. Then, run
-the following command to cleanup the failed service.</p><pre><tt>installadm delete-service <tt>-x</tt></tt></pre><p>Then, you can rerun the <tt>installadm create-service</tt> command.</p>
-
-<a name="fails"></a><h4>2. What if the Client Installation Fails?</h4>
-
-
-<a name="logs"></a><h5>Check the Installation Logs</h5>
-<p>If an installation to a client system failed, you can find the
-log at <tt>/tmp/install_log</tt>.</p>
-
-<a name="ipscheck"></a><h5>Check IPS Repository</h5>
-<p>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.</p><p>A failed installation can result in an error message. See the following sample
-error message:</p><pre><OM Nov 2 06:56:32> Creating and configuring pkg(5) image area...
- <TRANSFER_MOD Nov 2 06:56:32> pkg cmd: /usr/bin/pkg image-create
--f -F -p opensolaris.org=http://pkg.opensolaris.org /a
- <TRANSFER_MOD_E Nov 2 06:56:35>
- <TRANSFER_MOD_E Nov 2 06:56:35>
- <TRANSFER_MOD_E Nov 2 06:56:35> pkg image-create: The URI
-'http://pkg.opensolaris.org' does not appear to point to a valid pkg server.
- <TRANSFER_MOD_E Nov 2 06:56:35> Please check the server's address and client's
-network configuration.
- <TRANSFER_MOD_E Nov 2 06:56:35> Additional details:
- <TRANSFER_MOD_E Nov 2 06:56:35>
- <TRANSFER_MOD_E Nov 2 06:56:35> Unable to contact valid package server
- <TRANSFER_MOD_E Nov 2 06:56:35> Encountered the following error(s):
- <TRANSFER_MOD_E Nov 2 06:56:35> Unable to contact any configured publishers.
-This is likely a network configuration problem.
- <TRANSFER_MOD_E Nov 2 06:56:35> Unable to initialize the pkg image area at /a
- ...
- <AI Nov 2 06:56:36> Automated Installation failed in Transfer module
- <AI Nov 2 06:56:36> Transferring the files from the source failed.
-Please see previous messages for more details </pre><p>This 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 <a href="http://pkg.opensolaris.org">http://pkg.opensolaris.org</a> in the AI manifest
-for this client.</p><p>Check whether the repository is “pingable” by running, for example, the following command:</p><pre><tt>ping pkg.opensolaris.org</tt></pre><p>If the command returns the following, the error may be connectivity related:</p><pre>no answer from pkg.opensolaris.org</pre><p>If the command returns the following, the error may be DNS related.</p><pre>ping: unknown host pkg.opensolaris.org</pre>
-
-<a name="dns"></a><h5>Check DNS</h5>
-<p>Check whether DNS is configured on your client. First, check whether or not
-the DNS server is reachable. Get the server IP addresses by running the
-following command:</p><pre><tt>grep ^nameserver /etc/resolve</tt></pre><p>This command outputs lines such as the following:</p><pre>nameserver 192.168.0.1</pre><p>Then, verify that the server at this IP address is reachable by
-following the ping instructions above. The output should report as follows:</p><pre>192.168.0.1 is alive</pre><p>If you do not get this response, there is a DNS issue.
-Check with your DNS or network administrator.</p><p>You can also check <tt>/etc/resolv.conf</tt>. If <tt>/etc/resolv.conf</tt> is blank, run the following
-command:</p><pre>dhcpinfo DNSServ</pre><p>The output should provide one or more IP addresses. If nothing is
-returned, DHCP is not configured correctly.</p><p>To check your DHCP configuration, ensure that your DNS server specifies at one
-least one host via the <tt>DNSserv</tt> option.</p><p>If the DNS server is alive, you can also check to see
-if correct IP address is set up for the IPS repository that the
-system is trying to contact. For example, run the following command to display
-the IP address that your system has assigned for the <tt>opensolaris.org</tt> repository.</p><pre><tt>getent hosts opensolaris.org</tt></pre><p>The command output should display the correct IP address for the repository as
-follows:</p><pre>72.5.123.5 opensolaris.org</pre><p>If no response is provided, check with your DNS network administrator.</p>
-
-<a name="useproxy"></a><h5>Use Proxy to install</h5>
-<p>In cases where DNS is not set up, an HTTP proxy can
-be used to resolve the IPS repository name to an IP address and
-complete the installation. The XML tag, <tt><ai_http_proxy></tt>, and value in the AI manifest can
-contain the URL of the proxy as follows:</p><pre><ai_manifest name="http_proxy">
- ..........
- ..........
- <ai_pkg_repo_default_publisher>
- <main url="http://pkg.opensolaris.org" publisher="opensolaris.org"/>
- </ai_pkg_repo_default_publisher>
- <ai_http_proxy url="��http://126.100.76.111:8080"��/>
-</ai_manifest></pre>
-
-<a name="more"></a><h5>Check Client Boot Errors</h5>
-<p>Review the following additional information about errors that occur when the client system
-is booting:</p>
-<ul><li><p><a href="sparcclient.html#sparcerr">SPARC Network Booting Errors and Possible Causes</a></p></li>
-<li><p><a href="x86client.html#x86err">x86 Network Booting Errors and Possible Causes</a></p></li>
-<li><p><a href="bothclient.html">SPARC and x86 Client Installation Messages and Errors</a></p></li></ul>
-
- </div>
- </td>
- </tr>
-
- <tr class="PageControls" valign="top">
- <td></td>
- <td>
- <table width="100%">
- <tr>
- <td>
- <a href="trouble.html">Previous</a>
- </td>
- <td align="right">
- <a href="faq.html">Next</a>
- </td>
- </tr>
- </table>
- </td>
- </tr>
-</tbody>
-</table>
-
-
-</body>
-</html>
-
--- a/usr/src/cmd/installadm/docs/simple.html Wed Sep 29 16:37:00 2010 +0200
+++ /dev/null Thu Jan 01 00:00:00 1970 +0000
@@ -1,150 +0,0 @@
-<!DOCTYPE HTML PUBLIC "-//W3C//DTD HTML 4.01 Transitional//EN" "http://www.w3.org/TR/html4/loose.dtd">
-<html lang="en-US">
-
-<!-- -->
-<head>
-<!-- GenHTML revision 23436-->
-<meta http-equiv="Content-type" content="text/html; charset=iso-8859-1">
-<title>How to Complete Server Setup (Simple Instructions) - OpenSolaris 2010.03 Automated Installer Guide</title>
-<meta name="robots" content="index,follow">
-<meta name="robots" content="index,follow">
-<meta name="date" content="2010-03-01">
-<meta name="collection" content="reference">
-<link rel="stylesheet" type="text/css" href="css/elements.css">
-<link rel="stylesheet" type="text/css" href="css/opensol.css">
-</head>
-
-<body>
-
-
-<div class="Masthead">
- <div class="MastheadLogo">
- <a href="http://www.opensolaris.com"><img border="0" src="graphics/opensolaris_logo_trans.png"></img></a>
- </div>
- <div class="Title">OpenSolaris 2010.03 Automated Installer Guide</div>
-</div>
-<div class="headerbar"></div>
-
-
-<table class="Layout" border="0" cellspacing="0" width="100%">
-<tbody>
-
- <tr valign="top" class="PageControls">
- <td></td>
- <td>
- <table width="100%">
- <tr>
- <td>
- <a href="initial.html">Previous</a>
- </td>
- <td align="right">
- <a href="advancedsetup.html">Next</a>
- </td>
- </tr>
- </table>
- </td>
- </tr>
-
- <tr valign="top">
- <td class="Navigation" width="200px"><p class="toc level1"><a href="docinfo.html">Document Information</a></p>
-<p class="toc level1 tocsp"><a href="index.html">1. What's New For Automated Installations</a></p>
-<p class="toc level1 tocsp"><a href="intro.html">2. Introduction to the Automated Installer</a></p>
-<p class="toc level1 tocsp"><a href="tasks.html">3. Automated Network Install Task Map</a></p>
-<p class="toc level1 tocsp"><a href="bootable.html">4. Automated Installations That Boot From Media</a></p>
-<p class="toc level1 tocsp"><a href="setup.html">5. Set up an Automated Install Server</a></p>
-<p class="toc level2"><a href="basic.html">Server Setup</a></p>
-<p class="toc level2"><a href="initial.html">How to Set Up an Install Server (Initial Steps)</a></p>
-<div id="scrolltoc" class="onpage">
-<p class="toc level2"><a href="">How to Complete Server Setup (Simple Instructions)</a></p>
-</div>
-<p class="toc level2"><a href="advancedsetup.html">How to Complete Server Setup (Advanced Instructions)</a></p>
-<p class="toc level1 tocsp"><a href="administer.html">6. How to Administer an Automated Install Server</a></p>
-<p class="toc level1 tocsp"><a href="client.html">7. How to Administer a Custom Install Client</a></p>
-<p class="toc level1 tocsp"><a href="manifest.html">8. How to Administer Manifest Files</a></p>
-<p class="toc level1 tocsp"><a href="clients.html">9. How to Manage Client Installations</a></p>
-<p class="toc level1 tocsp"><a href="trouble.html">10. Troubleshooting and FAQs for the Automated Installer</a></p>
-<p class="toc level1 tocsp"><a href="appendix.html">11. Appendix</a></p>
-</td>
- <td class="ContentPane" width="705px">
-
- <div class="MainContent">
-
-
-<a name="simple"></a><h3>How to Complete Server Setup (Simple Instructions)</h3>
-<p>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.</p>
-<hr><p><b>Note - </b>You can use the ISC DHCP server instead of the Solaris DHCP
-server. See <a href="faq.html#isc">17. How do I use ISC DHCP With the Automated Installer?</a>.</p>
-<hr>
-
-
-<a name="simple1"></a><h4>Completing Server Setup</h4><h6>Before You Begin</h6><p> Complete the initial setup instructions provided in <a href="initial.html">How to Set Up an Install Server (Initial Steps)</a>.</p><ul>
-<li><b>Set up an install service by using either the following x86 procedure or
-SPARC procedure:</b><ul>
-<li><b>To set up an install service for x86 clients, use the following procedure:</b><ol style="list-style-type: lower-alpha">
-<li><b>Create an install service by using the <tt>installadm create-service</tt> command as in the
-following example:</b><pre># <tt>installadm create-service <tt>-n</tt> <i>1003x86</i> <tt>-i</tt> <i>172.1.0.10</i> <tt>-c</tt> <i>5</i></tt> \
-<tt><tt>-s</tt> <i>/export/aiimages/osol-1003-ai-x86.iso</i> <i>/export/aiserver/osol-1003-ai-x86</i></tt></pre><p>In this example, the command sets up a new install service named
-<tt>1003x86</tt>. The command also sets up a DHCP server on this system, if
-one has not been set up yet. A new DHCP macro,
-<tt>dhcp_macro_1003x86</tt>, for the install service is created. The install service serves five
-IP addresses, starting from 172.1.0.10.</p><p>In this example, the command options perform as follows:</p>
-<ul><li><p>Using the <tt>-n</tt> option, the command specifies a name, <tt>1003x86</tt>, for the new install service.</p>
-<hr><p><b>Note - </b>If you do not supply a service name, <tt>installadm create-service</tt> creates a unique name for the install service using the format, <tt>_install_service_<port_number></tt>.</p>
-<hr>
-</li>
-<li><p>Using the <tt>-i</tt> option, the command sets up a new DHCP server. The IP addresses are set up starting from <tt>172.1.0.10</tt>.</p></li>
-<li><p>Using the <tt>-c</tt> option, the command sets up a total of five IP addresses in the DHCP table.</p></li>
-<li><p>Using the <tt>-s</tt> option and its argument, <tt>/export/aiimages/osol-1003-ai-x86.iso</tt>, the command specifies the location of an AI ISO image. In this case, the AI ISO image is an x86 image.</p></li>
-<li><p>The last command-line argument, <tt>/export/aiserver/osol-1003-ai-x86</tt>, specifies the location where the command unpacks and stores the image that was specified by the <tt>-s</tt> option. The ISO image in this location enables client installations.</p></li></ul>
-</li>
-<li><b>Boot the client from the network.</b>
-<hr><p><b>Note - </b>It may be necessary to modify the BIOS configuration to select network booting.</p>
-<hr>
-</li>
-<li><b>When the client boots, select the network device to boot from.</b></li></ol></li>
-<li><b>To set up an install service for SPARC clients, use the following procedure:</b><ol style="list-style-type: lower-alpha">
-<li><b>Create an install service by using the <tt>installadm create-service</tt> command, as in the
-following example:</b><pre># <tt>installadm create-service <tt>-n</tt> <i>1003sparc</i> <tt>-i</tt> <i>172.1.0.10</i> <tt>-c</tt> <i>5</i></tt> \
-<tt><tt>-s</tt> <i>/export/aiimages/osol-1003-ai-sparc.iso</i> <i>/export/aiserver/osol-1003-ai-sparc</i></tt></pre><p>In this example, the command sets up a new install service named
-<tt>1003sparc</tt>. The command also sets up a DHCP server on this system, if
-one has not been set up yet. A macro, <tt>dhcp_macro_1003sparc</tt>, for the
-install service is created in the DHCP server, and five IP addresses, starting
-from 172.1.0.10, are allocated to that macro.</p><p>In this example, the command options perform as follows:</p>
-<ul><li><p>Using the <tt>-n</tt> option, the command specifies a name, <tt>1003sparc</tt>, for the new install service.</p></li>
-<li><p>Using the <tt>-i</tt> option, the command sets up a new DHCP server. The IP addresses, starting from <tt>172.1.0.10</tt>, are set up.</p></li>
-<li><p>Using the <tt>-c</tt> option, the command sets up a total of five IP addresses in the DHCP table.</p></li>
-<li><p>Using the <tt>-s</tt> option, the command specifies an AI ISO image, <tt>/export/aiimages/osol-1003-ai-sparc.iso</tt>, that can be used to install the OpenSolaris OS to a client. In this case, the AI ISO image is a SPARC image.</p></li>
-<li><p>In the last tag, the command specifies a location, <tt>/export/aiserver/osol-1003-ai-sparc</tt>, where the command unpacks and stores the image that was specified by the <tt>-s</tt> option. The ISO image in this location enables client installations.</p></li></ul>
-</li>
-<li><b>For SPARC clients, boot with the following command from the open boot prompt:</b><pre>OK <tt>boot net:dhcp - install</tt></pre></li></ol></li></ul></li></ul><h6>Troubleshooting</h6><p>For further information, see <a href="administer.html">Chapter 6, How to Administer an Automated Install Server</a>. See, also, <a href="trouble.html">Chapter 10, Troubleshooting and FAQs for the Automated Installer</a>.</p>
- </div>
- </td>
- </tr>
-
- <tr class="PageControls" valign="top">
- <td></td>
- <td>
- <table width="100%">
- <tr>
- <td>
- <a href="initial.html">Previous</a>
- </td>
- <td align="right">
- <a href="advancedsetup.html">Next</a>
- </td>
- </tr>
- </table>
- </td>
- </tr>
-</tbody>
-</table>
-
-
-</body>
-</html>
-
--- a/usr/src/cmd/installadm/docs/smf.html Wed Sep 29 16:37:00 2010 +0200
+++ /dev/null Thu Jan 01 00:00:00 1970 +0000
@@ -1,116 +0,0 @@
-<!DOCTYPE HTML PUBLIC "-//W3C//DTD HTML 4.01 Transitional//EN" "http://www.w3.org/TR/html4/loose.dtd">
-<html lang="en-US">
-
-<!-- -->
-<head>
-<!-- GenHTML revision 23436-->
-<meta http-equiv="Content-type" content="text/html; charset=iso-8859-1">
-<title>How to Administer Install Services by Using the AI SMF Service - OpenSolaris 2010.03 Automated Installer Guide</title>
-<meta name="robots" content="index,follow">
-<meta name="robots" content="index,follow">
-<meta name="date" content="2010-03-01">
-<meta name="collection" content="reference">
-<link rel="stylesheet" type="text/css" href="css/elements.css">
-<link rel="stylesheet" type="text/css" href="css/opensol.css">
-</head>
-
-<body>
-
-
-<div class="Masthead">
- <div class="MastheadLogo">
- <a href="http://www.opensolaris.com"><img border="0" src="graphics/opensolaris_logo_trans.png"></img></a>
- </div>
- <div class="Title">OpenSolaris 2010.03 Automated Installer Guide</div>
-</div>
-<div class="headerbar"></div>
-
-
-<table class="Layout" border="0" cellspacing="0" width="100%">
-<tbody>
-
- <tr valign="top" class="PageControls">
- <td></td>
- <td>
- <table width="100%">
- <tr>
- <td>
- <a href="enable.html">Previous</a>
- </td>
- <td align="right">
- <a href="client.html">Next</a>
- </td>
- </tr>
- </table>
- </td>
- </tr>
-
- <tr valign="top">
- <td class="Navigation" width="200px"><p class="toc level1"><a href="docinfo.html">Document Information</a></p>
-<p class="toc level1 tocsp"><a href="index.html">1. What's New For Automated Installations</a></p>
-<p class="toc level1 tocsp"><a href="intro.html">2. Introduction to the Automated Installer</a></p>
-<p class="toc level1 tocsp"><a href="tasks.html">3. Automated Network Install Task Map</a></p>
-<p class="toc level1 tocsp"><a href="bootable.html">4. Automated Installations That Boot From Media</a></p>
-<p class="toc level1 tocsp"><a href="setup.html">5. Set up an Automated Install Server</a></p>
-<p class="toc level1 tocsp"><a href="administer.html">6. How to Administer an Automated Install Server</a></p>
-<p class="toc level2"><a href="add.html">How to Add Install Services</a></p>
-<p class="toc level2"><a href="delete.html">How to Delete Install Services</a></p>
-<p class="toc level2"><a href="view.html">How to Review What You Have on Your Server</a></p>
-<p class="toc level2"><a href="enable.html">How to Enable and Disable Install Services</a></p>
-<div id="scrolltoc" class="onpage">
-<p class="toc level2"><a href="">How to Administer Install Services by Using the AI SMF Service</a></p>
-</div>
-<p class="toc level1 tocsp"><a href="client.html">7. How to Administer a Custom Install Client</a></p>
-<p class="toc level1 tocsp"><a href="manifest.html">8. How to Administer Manifest Files</a></p>
-<p class="toc level1 tocsp"><a href="clients.html">9. How to Manage Client Installations</a></p>
-<p class="toc level1 tocsp"><a href="trouble.html">10. Troubleshooting and FAQs for the Automated Installer</a></p>
-<p class="toc level1 tocsp"><a href="appendix.html">11. Appendix</a></p>
-</td>
- <td class="ContentPane" width="705px">
-
- <div class="MainContent">
-
-
-<a name="smf"></a><h3>How to Administer Install Services by Using the AI SMF Service</h3>
-<p>The automated installer includes the SMF service, <tt>svc:/system/install/server:default</tt>. This SMF service contains
-the data specific to each install service, such as the following:</p>
-<ul><li><p>Install service name</p></li>
-<li><p>Image path</p></li>
-<li><p>Boot file</p></li>
-<li><p>Status of the install service</p></li>
-<li><p>Webserver port</p></li></ul>
-
-
-<a name="smf2"></a><h4>Using the AI SMF Service</h4>
-<p>You can perform the following tasks by using the automated installer's SMF service:</p>
-<ul><li><p>To see a list of the install services, run the following command:</p><pre># <tt>svccfg <tt>-s</tt> <i>svc:/system/install/server:default</i> <i>listpg</i></tt></pre></li>
-<li><p>Each install service is represented by an SMF property group, <tt>AI<install service name></tt>. To see the data for a specific install service, run the following command:</p><pre># <tt>svccfg <tt>-s</tt> <i>svc:/system/install/server:default listprop</i> <i>property_group_name</i></tt></pre></li>
-<li><p>The AI SMF service is enabled whenever you run the <tt>installadm create-service</tt> command. Also, the AI SMF service is enabled any time you run any of the other <tt>installadm</tt> command options that impact existing install services. Alternately, you can enable the SMF service by running the following command:</p><pre># <tt>svcadm enable <i>svc:/system/install/server:default</i></tt></pre><p>The service goes into maintenance mode if there are no install services currently enabled on the install server.</p></li>
-<li><p>You can disable the SMF service by running the following command:</p><pre># <tt>svcadm disable <i>svc:/system/install/server:default</i></tt></pre></li></ul>
-<p>For further information about administering install services, see <a href="trouble.html">Chapter 10, Troubleshooting and FAQs for the Automated Installer</a>.</p>
- </div>
- </td>
- </tr>
-
- <tr class="PageControls" valign="top">
- <td></td>
- <td>
- <table width="100%">
- <tr>
- <td>
- <a href="enable.html">Previous</a>
- </td>
- <td align="right">
- <a href="client.html">Next</a>
- </td>
- </tr>
- </table>
- </td>
- </tr>
-</tbody>
-</table>
-
-
-</body>
-</html>
-
--- a/usr/src/cmd/installadm/docs/sparcclient.html Wed Sep 29 16:37:00 2010 +0200
+++ /dev/null Thu Jan 01 00:00:00 1970 +0000
@@ -1,303 +0,0 @@
-<!DOCTYPE HTML PUBLIC "-//W3C//DTD HTML 4.01 Transitional//EN" "http://www.w3.org/TR/html4/loose.dtd">
-<html lang="en-US">
-
-<!-- -->
-<head>
-<!-- GenHTML revision 23436-->
-<meta http-equiv="Content-type" content="text/html; charset=iso-8859-1">
-<title>SPARC Client Installations - OpenSolaris 2010.03 Automated Installer Guide</title>
-<meta name="robots" content="index,follow">
-<meta name="robots" content="index,follow">
-<meta name="date" content="2010-03-01">
-<meta name="collection" content="reference">
-<link rel="stylesheet" type="text/css" href="css/elements.css">
-<link rel="stylesheet" type="text/css" href="css/opensol.css">
-</head>
-
-<body>
-
-
-<div class="Masthead">
- <div class="MastheadLogo">
- <a href="http://www.opensolaris.com"><img border="0" src="graphics/opensolaris_logo_trans.png"></img></a>
- </div>
- <div class="Title">OpenSolaris 2010.03 Automated Installer Guide</div>
-</div>
-<div class="headerbar"></div>
-
-
-<table class="Layout" border="0" cellspacing="0" width="100%">
-<tbody>
-
- <tr valign="top" class="PageControls">
- <td></td>
- <td>
- <table width="100%">
- <tr>
- <td>
- <a href="clientreq.html">Previous</a>
- </td>
- <td align="right">
- <a href="x86client.html">Next</a>
- </td>
- </tr>
- </table>
- </td>
- </tr>
-
- <tr valign="top">
- <td class="Navigation" width="200px"><p class="toc level1"><a href="docinfo.html">Document Information</a></p>
-<p class="toc level1 tocsp"><a href="index.html">1. What's New For Automated Installations</a></p>
-<p class="toc level1 tocsp"><a href="intro.html">2. Introduction to the Automated Installer</a></p>
-<p class="toc level1 tocsp"><a href="tasks.html">3. Automated Network Install Task Map</a></p>
-<p class="toc level1 tocsp"><a href="bootable.html">4. Automated Installations That Boot From Media</a></p>
-<p class="toc level1 tocsp"><a href="setup.html">5. Set up an Automated Install Server</a></p>
-<p class="toc level1 tocsp"><a href="administer.html">6. How to Administer an Automated Install Server</a></p>
-<p class="toc level1 tocsp"><a href="client.html">7. How to Administer a Custom Install Client</a></p>
-<p class="toc level1 tocsp"><a href="manifest.html">8. How to Administer Manifest Files</a></p>
-<p class="toc level1 tocsp"><a href="clients.html">9. How to Manage Client Installations</a></p>
-<p class="toc level2"><a href="clientreq.html">Client System Requirements</a></p>
-<div id="scrolltoc" class="onpage">
-<p class="toc level2"><a href="">SPARC Client Installations</a></p>
-</div>
-<p class="toc level2"><a href="x86client.html">x86 Client Installations</a></p>
-<p class="toc level2"><a href="bothclient.html">SPARC and x86 Client Installation Messages and Errors</a></p>
-<p class="toc level1 tocsp"><a href="trouble.html">10. Troubleshooting and FAQs for the Automated Installer</a></p>
-<p class="toc level1 tocsp"><a href="appendix.html">11. Appendix</a></p>
-</td>
- <td class="ContentPane" width="705px">
-
- <div class="MainContent">
-
-
-<a name="sparcclient"></a><h3>SPARC Client Installations</h3>
-<p>Review the following information about SPARC client installations:</p>
-<ul><li><p><a href="#sparcboot">What Happens During the SPARC Client Network Boot Sequence?</a></p></li>
-<li><p><a href="#sparcsee">What Should I See During the SPARC Network Boot Sequence?</a></p></li>
-<li><p><a href="#sparcerr">SPARC Network Booting Errors and Possible Causes</a></p></li></ul>
-
-
-<a name="sparcboot"></a><h4>What Happens During the SPARC Client Network Boot Sequence?</h4>
-<p>Boot the client from the network. For SPARC clients, at the open
-boot prompt, type:</p><pre>OK <tt>boot net:dhcp - install</tt></pre><p>The technical details of what occurs during the automated installer (AI) boot of
-a SPARC client are as follows:</p>
-<ol><li><p>The client boots and gets IP address and the bootfile, <tt>wanboot-cgi</tt>, from the DHCP server.</p></li>
-<li><p><tt>wanboot-cgi</tt> reads <tt>wanboot.conf</tt> and sends the location of the WAN Boot binary to the client.</p></li>
-<li><p>The WAN Boot binary is downloaded using HTTP, and the client boots the WAN Boot program.</p></li>
-<li><p>WAN Boot gets the <tt>boot_archive</tt> file, and Solaris is booted.</p></li>
-<li><p>Image archives, <tt>solaris.zlib</tt> and <tt>solarismisc.zlib</tt>, are downloaded using HTTP.</p></li>
-<li><p>The AI SMF service uses multicast DNS (mDNS) to contact the HTTP server and get the AI manifest.</p></li>
-<li><p>The AI install program is invoked with the AI manifest to perform the installation of the OpenSolaris OS to the client.</p></li></ol>
-
-
-<a name="sparcsee"></a><h4>What Should I See During the SPARC Network Boot Sequence?</h4>
-<p>The SPARC client installation is initiated by typing at the open boot prompt:</p><pre>OK <tt>boot net:dhcp - install</tt></pre><p>The following output from the boot sequence is displayed:</p><pre>{3} ok boot net:dhcp - install
-
-...
-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 - install
-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
-OpenSolarisOS Release 5.11 Version snv_111 64-bit
-...
-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-1003-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-1003-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-1003-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</pre>
-
-<a name="sparcerr"></a><h4>SPARC Network Booting Errors and Possible Causes</h4>
-<p>This section describes errors or problems you might see when booting a
-SPARC client over the network and possible causes:</p><p><a href="#timeout">1. Timed out Waiting for BOOTP/DHCP Reply</a></p><p><a href="#load">2. Boot Load Failed</a></p><p><a href="#alert">3. Internal Server Error or WAN Boot Alert</a></p><p><a href="#forbid">4. Error Message 403: Forbidden or 404 Not Found</a></p><p><a href="#disabled">5. Auto-installer Disabled</a></p>
-
-<a name="timeout"></a><h5>1. Timed out Waiting for BOOTP/DHCP Reply</h5>
-<p>If a DHCP server is not responding to a SPARC client's request,
-the following messages display:</p><pre> ...
- 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 - install
- 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 reply</pre><p>The 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.</p>
-
-<a name="load"></a><h5>2. Boot Load Failed</h5>
-<p>If the AI client starts downloading the <tt>boot_archive</tt>, but then fails with
-the error, “Boot load failed,” that indicates that the client DHCP information is
-configured incorrectly.</p><pre>Rebooting with command: boot net:dhcp - install
- 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 failed</pre><p>This 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 the Solaris DHCP server, you can run the DHCP daemon in
-debug mode with the command:</p><pre># <tt>/usr/lib/inet/in.dhcpd <tt>-dv</tt></tt></pre>
-
-<a name="alert"></a><h5>3. Internal Server Error or WAN Boot Alert</h5>
-<p>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 <tt>boot_archive</tt>.</p>
-<ul><li><p>If the client cannot find the <tt>boot_archive</tt>, the following error is displayed:</p><pre>Rebooting with command: boot net:dhcp - install
- 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)</pre></li>
-<li><p>If the AI client finds the <tt>boot_archive</tt> file but cannot access the file, then the following error is displayed:</p><pre>Rebooting with command: boot net:dhcp - install
- 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</pre></li></ul>
-<p>For both of these problems, fix the <tt>boot_archive</tt> file configured for this client.
-Check the path name and permissions of the <tt>boot_archive</tt> at <tt>$IMAGE/boot/boot_archive</tt>.</p>
-
-<a name="forbid"></a><h5>4. Error Message 403: Forbidden or 404 Not Found</h5>
-<p>These messages, “ERROR 403: Forbidden” and “ERROR 404: Not Found” can be seen
-if the AI client successfully downloads the <tt>boot_archive</tt> and boots the OpenSolaris kernel,
-but fails to get one of the image archives. An error message is
-displayed indicating which file is causing the problem. For example, in the following
-output, the <tt>solaris.zlib</tt> file does not exist or is not accessible at
-the specified location.</p><pre>Rebooting with command: boot net:dhcp - install
- 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
- OpenSolarisOS Release 5.11 Version snv_111 64-bit
- ...
- 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 run</pre><p>This problem can be caused by one of the following conditions:</p>
-<ul><li><p>The image path configured in WAN boot is not correct.</p></li>
-<li><p>The image path does not exist or is incomplete.</p></li>
-<li><p>Access is denied due to permission issues.</p></li></ul>
-<p>Check your DHCP configuration or the contents of the target directory you specified
-when you ran <tt>installadm create-service</tt>. Check your WAN boot configuration.</p>
-
-<a name="disabled"></a><h5>5. Auto-installer Disabled</h5>
-<p>When installing the OpenSolaris 2010.03 release on your client system, you need to
-include the <tt>install</tt> argument when you boot, as follows, in order to initiate
-an installation.</p><pre>OK <tt>boot net:dhcp - install</tt></pre><p>If you've booted without the <tt>install</tt> boot argument, the SPARC client boots into
-the automated installer boot image, but the installation does not start. The
-following message is displayed.</p><pre>Auto-installer disabled. Enable the auto-installer service
-by running the following command:
-svcadm enable svc:/application/auto-installer:default</pre><p>You should reboot your system, using the <tt>install</tt> argument in the boot command.</p>
-<hr><p><b>Note - </b>To boot from AI media, use the following command:</p><pre>OK <tt>boot cdrom - install</tt></pre>
-<hr>
-
-<hr><p><b>Caution - </b>If you are installing using an OpenSolaris 2009.06 AI ISO image, use the
-booting instructions for the prior OpenSolaris releases. See FAQ #11 at <a href="http://dlc.sun.com/osol/docs/content/2009.06/AIinstall/faq.html">http://dlc.sun.com/osol/docs/content/2009.06/AIinstall/faq.html</a>.</p>
-<hr>
-
- </div>
- </td>
- </tr>
-
- <tr class="PageControls" valign="top">
- <td></td>
- <td>
- <table width="100%">
- <tr>
- <td>
- <a href="clientreq.html">Previous</a>
- </td>
- <td align="right">
- <a href="x86client.html">Next</a>
- </td>
- </tr>
- </table>
- </td>
- </tr>
-</tbody>
-</table>
-
-
-</body>
-</html>
-
--- a/usr/src/cmd/installadm/docs/tasks.html Wed Sep 29 16:37:00 2010 +0200
+++ /dev/null Thu Jan 01 00:00:00 1970 +0000
@@ -1,105 +0,0 @@
-<!DOCTYPE HTML PUBLIC "-//W3C//DTD HTML 4.01 Transitional//EN" "http://www.w3.org/TR/html4/loose.dtd">
-<html lang="en-US">
-
-<!-- -->
-<head>
-<!-- GenHTML revision 23436-->
-<meta http-equiv="Content-type" content="text/html; charset=iso-8859-1">
-<title>Automated Network Install Task Map - OpenSolaris 2010.03 Automated Installer Guide</title>
-<meta name="robots" content="index,follow">
-<meta name="robots" content="index,follow">
-<meta name="date" content="2010-03-01">
-<meta name="collection" content="reference">
-<link rel="stylesheet" type="text/css" href="css/elements.css">
-<link rel="stylesheet" type="text/css" href="css/opensol.css">
-</head>
-
-<body>
-
-
-<div class="Masthead">
- <div class="MastheadLogo">
- <a href="http://www.opensolaris.com"><img border="0" src="graphics/opensolaris_logo_trans.png"></img></a>
- </div>
- <div class="Title">OpenSolaris 2010.03 Automated Installer Guide</div>
-</div>
-<div class="headerbar"></div>
-
-
-<table class="Layout" border="0" cellspacing="0" width="100%">
-<tbody>
-
- <tr valign="top" class="PageControls">
- <td></td>
- <td>
- <table width="100%">
- <tr>
- <td>
- <a href="benefits.html">Previous</a>
- </td>
- <td align="right">
- <a href="tasks1.html">Next</a>
- </td>
- </tr>
- </table>
- </td>
- </tr>
-
- <tr valign="top">
- <td class="Navigation" width="200px"><p class="toc level1"><a href="docinfo.html">Document Information</a></p>
-<p class="toc level1 tocsp"><a href="index.html">1. What's New For Automated Installations</a></p>
-<p class="toc level1 tocsp"><a href="intro.html">2. Introduction to the Automated Installer</a></p>
-<div id="scrolltoc" class="onpage">
-<p class="toc level1 tocsp"><a href="">3. Automated Network Install Task Map</a></p>
-</div>
-<p class="toc level2"><a href="tasks1.html">Automated Install (Tasks)</a></p>
-<p class="toc level1 tocsp"><a href="bootable.html">4. Automated Installations That Boot From Media</a></p>
-<p class="toc level1 tocsp"><a href="setup.html">5. Set up an Automated Install Server</a></p>
-<p class="toc level1 tocsp"><a href="administer.html">6. How to Administer an Automated Install Server</a></p>
-<p class="toc level1 tocsp"><a href="client.html">7. How to Administer a Custom Install Client</a></p>
-<p class="toc level1 tocsp"><a href="manifest.html">8. How to Administer Manifest Files</a></p>
-<p class="toc level1 tocsp"><a href="clients.html">9. How to Manage Client Installations</a></p>
-<p class="toc level1 tocsp"><a href="trouble.html">10. Troubleshooting and FAQs for the Automated Installer</a></p>
-<p class="toc level1 tocsp"><a href="appendix.html">11. Appendix</a></p>
-</td>
- <td class="ContentPane" width="705px">
-
- <div class="MainContent">
- <a name="tasks"></a>Chapter 3<h3>Automated Network Install Task Map</h3><p>The automated installer can be used to automate the installation of the OpenSolaris
-OS on one or more SPARC and x86 systems by booting from
-an install server over a network or by booting from AI media.</p><p>The following task map walks you through the overall process of setting up
-and using the automated installer by booting from an install server over the
-network. The minimal configuration necessary 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.</p>
-<hr><p><b>Note - </b>If you want to install by booting from a CD or DVD,
-instead of using this task map, go to the instructions at <a href="bootable.html">Chapter 4, Automated Installations That Boot From Media</a>.</p>
-<hr>
-
- </div>
- </td>
- </tr>
-
- <tr class="PageControls" valign="top">
- <td></td>
- <td>
- <table width="100%">
- <tr>
- <td>
- <a href="benefits.html">Previous</a>
- </td>
- <td align="right">
- <a href="tasks1.html">Next</a>
- </td>
- </tr>
- </table>
- </td>
- </tr>
-</tbody>
-</table>
-
-
-</body>
-</html>
-
--- a/usr/src/cmd/installadm/docs/tasks1.html Wed Sep 29 16:37:00 2010 +0200
+++ /dev/null Thu Jan 01 00:00:00 1970 +0000
@@ -1,184 +0,0 @@
-<!DOCTYPE HTML PUBLIC "-//W3C//DTD HTML 4.01 Transitional//EN" "http://www.w3.org/TR/html4/loose.dtd">
-<html lang="en-US">
-
-<!-- -->
-<head>
-<!-- GenHTML revision 23436-->
-<meta http-equiv="Content-type" content="text/html; charset=iso-8859-1">
-<title>Automated Install (Tasks) - OpenSolaris 2010.03 Automated Installer Guide</title>
-<meta name="robots" content="index,follow">
-<meta name="robots" content="index,follow">
-<meta name="date" content="2010-03-01">
-<meta name="collection" content="reference">
-<link rel="stylesheet" type="text/css" href="css/elements.css">
-<link rel="stylesheet" type="text/css" href="css/opensol.css">
-</head>
-
-<body>
-
-
-<div class="Masthead">
- <div class="MastheadLogo">
- <a href="http://www.opensolaris.com"><img border="0" src="graphics/opensolaris_logo_trans.png"></img></a>
- </div>
- <div class="Title">OpenSolaris 2010.03 Automated Installer Guide</div>
-</div>
-<div class="headerbar"></div>
-
-
-<table class="Layout" border="0" cellspacing="0" width="100%">
-<tbody>
-
- <tr valign="top" class="PageControls">
- <td></td>
- <td>
- <table width="100%">
- <tr>
- <td>
- <a href="tasks.html">Previous</a>
- </td>
- <td align="right">
- <a href="bootable.html">Next</a>
- </td>
- </tr>
- </table>
- </td>
- </tr>
-
- <tr valign="top">
- <td class="Navigation" width="200px"><p class="toc level1"><a href="docinfo.html">Document Information</a></p>
-<p class="toc level1 tocsp"><a href="index.html">1. What's New For Automated Installations</a></p>
-<p class="toc level1 tocsp"><a href="intro.html">2. Introduction to the Automated Installer</a></p>
-<p class="toc level1 tocsp"><a href="tasks.html">3. Automated Network Install Task Map</a></p>
-<div id="scrolltoc" class="onpage">
-<p class="toc level2"><a href="">Automated Install (Tasks)</a></p>
-</div>
-<p class="toc level1 tocsp"><a href="bootable.html">4. Automated Installations That Boot From Media</a></p>
-<p class="toc level1 tocsp"><a href="setup.html">5. Set up an Automated Install Server</a></p>
-<p class="toc level1 tocsp"><a href="administer.html">6. How to Administer an Automated Install Server</a></p>
-<p class="toc level1 tocsp"><a href="client.html">7. How to Administer a Custom Install Client</a></p>
-<p class="toc level1 tocsp"><a href="manifest.html">8. How to Administer Manifest Files</a></p>
-<p class="toc level1 tocsp"><a href="clients.html">9. How to Manage Client Installations</a></p>
-<p class="toc level1 tocsp"><a href="trouble.html">10. Troubleshooting and FAQs for the Automated Installer</a></p>
-<p class="toc level1 tocsp"><a href="appendix.html">11. Appendix</a></p>
-</td>
- <td class="ContentPane" width="705px">
-
- <div class="MainContent">
-
-
-<a name="tasks1"></a><h3>Automated Install (Tasks)</h3>
-<a name="taskstbl"></a><h6>Table 3-1 Task Map</h6><table><col width="19%"><col width="28%"><col width="51%"><tr><th align="left" valign="top" scope="column"><p>Task</p></th>
-<th align="left" valign="top" scope="column"><p>Question</p></th>
-<th align="left" valign="top" scope="column"><p>Reference</p></th>
-</tr>
-<tr><td align="left" valign="top" scope="row"><p>Check hardware.</p></td>
-<td align="left" valign="top" scope="row"><p>Do
-you have the necessary hardware for your install server and clients?</p></td>
-<td align="left" valign="top" scope="row"><p>Any system
-that meets the requirements can be used as an automated install server or
-client, including laptops, desktops, virtual machines, and enterprise servers.</p>
-<ul><li><p>See the install server requirements at <a href="basic.html">Server Setup</a>.</p></li>
-<li><p>See the client requirements at <a href="clientreq.html">Client System Requirements</a>.</p></li></ul>
-</td>
-</tr>
-<tr><td align="left" valign="top" scope="row"><p>Install the current OpenSolaris OS.</p></td>
-<td align="left" valign="top" scope="row"><p>Is
-the current OpenSolaris OS installed on your install server?</p></td>
-<td align="left" valign="top" scope="row"><p>You can use either
-a SPARC system or an x86 system as your install server.</p><p>You must
-have the current OpenSolaris release installed on the system that you plan to
-use as your install server. See Step 1 in <a href="initial.html">How to Set Up an Install Server (Initial Steps)</a>.</p>
-<hr><p><b>Note - </b>To set up
-a SPARC system as your install server, first create SPARC AI media, and
-then use that media to install the OpenSolaris release on that system. For
-instructions, see <a href="bootable.html">Chapter 4, Automated Installations That Boot From Media</a>.</p>
-<hr>
-</td>
-</tr>
-<tr><td align="left" valign="top" scope="row"><p>Set up a static IP address.</p></td>
-<td align="left" valign="top" scope="row"><p>Do you have a static
-IP address set up for your install server?</p></td>
-<td align="left" valign="top" scope="row"><p>If you do not have
-a static IP address set up for your install server, see Step 2
-in <a href="initial.html#initial1">Initial Setup</a>.</p></td>
-</tr>
-<tr><td align="left" valign="top" scope="row"><p>Get the install server tools package.</p></td>
-<td align="left" valign="top" scope="row"><p>Is the latest <tt>installadm</tt> package installed
-on your install server?</p></td>
-<td align="left" valign="top" scope="row">
-<hr><p><b>Note - </b><b>Starting with the OpenSolaris 2010.03 release</b>, the <tt>SUNWinstalladm-tools</tt> package has been renamed as the <tt>installadm</tt> package.
-Both the old and new names are usable.</p>
-<hr>
-<p>For instructions about installing the latest
-<tt>installadm</tt> package, see Step 3 in <a href="initial.html#initial1">Initial Setup</a>.</p></td>
-</tr>
-<tr><td align="left" valign="top" scope="row"><p>Get an AI ISO image.</p></td>
-<td align="left" valign="top" scope="row"><p>Do you
-have the AI ISO image you want to use as input for
-the <tt>installadm create-service</tt> command?</p></td>
-<td align="left" valign="top" scope="row"><p>For instructions about downloading the AI ISO image, see Step
-4 in <a href="initial.html#initial1">Initial Setup</a>.</p></td>
-</tr>
-<tr><td align="left" valign="top" scope="row"><p>Set up an install service.</p></td>
-<td align="left" valign="top" scope="row"><p>Have you run <tt>installadm create-service</tt> command to set
-up your install service?</p></td>
-<td align="left" valign="top" scope="row"><p>For instructions, see <a href="setup.html">Chapter 5, Set up an Automated Install Server</a> and <a href="administer.html">Chapter 6, How to Administer an Automated Install Server</a>.</p></td>
-</tr>
-<tr><td align="left" valign="top" scope="row"><p>Customize client installations.</p></td>
-<td align="left" valign="top" scope="row"><p>Do you
-need to run the <tt>installadm create-client</tt> command to customize your client installations?</p></td>
-<td align="left" valign="top" scope="row"><p>For instructions, see
-<a href="client.html">Chapter 7, How to Administer a Custom Install Client</a>.</p></td>
-</tr>
-<tr><td align="left" valign="top" scope="row"><p>Replace default manifests.</p></td>
-<td align="left" valign="top" scope="row"><p>Are the specifications in the default manifest suitable for your
-clients?</p></td>
-<td align="left" valign="top" scope="row"><p>If the default manifest specifications are not suitable for your clients, you can
-create a custom manifest. See <a href="manifest.html">Chapter 8, How to Administer Manifest Files</a>.</p></td>
-</tr>
-<tr><td align="left" valign="top" scope="row"><p>Assign custom manifests.</p></td>
-<td align="left" valign="top" scope="row"><p>Do you want to augment
-the default manifest with a custom manifest?</p></td>
-<td align="left" valign="top" scope="row"><p>If you want to assign custom
-manifests for use by specific clients, see <a href="criteria.html">How to Create and Use a Criteria Manifest</a>.</p></td>
-</tr>
-<tr><td align="left" valign="top" scope="row"><p>Start installations.</p></td>
-<td align="left" valign="top" scope="row"><p>Are you ready to start
-client installations?</p></td>
-<td align="left" valign="top" scope="row"><p>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 <tt>boot net:dhcp - install</tt>. See <a href="clients.html">Chapter 9, How to Manage Client Installations</a>.</p></td>
-</tr>
-<tr><td align="left" valign="top" scope="row"><p>Troubleshooting</p></td>
-<td align="left" valign="top" scope="row"><p>Was there a problem with your installation?</p></td>
-<td align="left" valign="top" scope="row"><p>Refer to
-<a href="trouble.html">Chapter 10, Troubleshooting and FAQs for the Automated Installer</a>. See, also, <a href="clients.html">Chapter 9, How to Manage Client Installations</a>.</p></td>
-</tr>
-</table>
- </div>
- </td>
- </tr>
-
- <tr class="PageControls" valign="top">
- <td></td>
- <td>
- <table width="100%">
- <tr>
- <td>
- <a href="tasks.html">Previous</a>
- </td>
- <td align="right">
- <a href="bootable.html">Next</a>
- </td>
- </tr>
- </table>
- </td>
- </tr>
-</tbody>
-</table>
-
-
-</body>
-</html>
-
--- a/usr/src/cmd/installadm/docs/trouble.html Wed Sep 29 16:37:00 2010 +0200
+++ /dev/null Thu Jan 01 00:00:00 1970 +0000
@@ -1,96 +0,0 @@
-<!DOCTYPE HTML PUBLIC "-//W3C//DTD HTML 4.01 Transitional//EN" "http://www.w3.org/TR/html4/loose.dtd">
-<html lang="en-US">
-
-<!-- -->
-<head>
-<!-- GenHTML revision 23436-->
-<meta http-equiv="Content-type" content="text/html; charset=iso-8859-1">
-<title>Troubleshooting and FAQs for the Automated Installer - OpenSolaris 2010.03 Automated Installer Guide</title>
-<meta name="robots" content="index,follow">
-<meta name="robots" content="index,follow">
-<meta name="date" content="2010-03-01">
-<meta name="collection" content="reference">
-<link rel="stylesheet" type="text/css" href="css/elements.css">
-<link rel="stylesheet" type="text/css" href="css/opensol.css">
-</head>
-
-<body>
-
-
-<div class="Masthead">
- <div class="MastheadLogo">
- <a href="http://www.opensolaris.com"><img border="0" src="graphics/opensolaris_logo_trans.png"></img></a>
- </div>
- <div class="Title">OpenSolaris 2010.03 Automated Installer Guide</div>
-</div>
-<div class="headerbar"></div>
-
-
-<table class="Layout" border="0" cellspacing="0" width="100%">
-<tbody>
-
- <tr valign="top" class="PageControls">
- <td></td>
- <td>
- <table width="100%">
- <tr>
- <td>
- <a href="bothclient.html">Previous</a>
- </td>
- <td align="right">
- <a href="setupfaq.html">Next</a>
- </td>
- </tr>
- </table>
- </td>
- </tr>
-
- <tr valign="top">
- <td class="Navigation" width="200px"><p class="toc level1"><a href="docinfo.html">Document Information</a></p>
-<p class="toc level1 tocsp"><a href="index.html">1. What's New For Automated Installations</a></p>
-<p class="toc level1 tocsp"><a href="intro.html">2. Introduction to the Automated Installer</a></p>
-<p class="toc level1 tocsp"><a href="tasks.html">3. Automated Network Install Task Map</a></p>
-<p class="toc level1 tocsp"><a href="bootable.html">4. Automated Installations That Boot From Media</a></p>
-<p class="toc level1 tocsp"><a href="setup.html">5. Set up an Automated Install Server</a></p>
-<p class="toc level1 tocsp"><a href="administer.html">6. How to Administer an Automated Install Server</a></p>
-<p class="toc level1 tocsp"><a href="client.html">7. How to Administer a Custom Install Client</a></p>
-<p class="toc level1 tocsp"><a href="manifest.html">8. How to Administer Manifest Files</a></p>
-<p class="toc level1 tocsp"><a href="clients.html">9. How to Manage Client Installations</a></p>
-<div id="scrolltoc" class="onpage">
-<p class="toc level1 tocsp"><a href="">10. Troubleshooting and FAQs for the Automated Installer</a></p>
-</div>
-<p class="toc level2"><a href="setupfaq.html">Troubleshooting Issues</a></p>
-<p class="toc level2"><a href="faq.html">Frequently Asked Questions</a></p>
-<p class="toc level2"><a href="help.html">Additional Resources</a></p>
-<p class="toc level1 tocsp"><a href="appendix.html">11. Appendix</a></p>
-</td>
- <td class="ContentPane" width="705px">
-
- <div class="MainContent">
- <a name="trouble"></a>Chapter 10<h3>Troubleshooting and FAQs for the Automated Installer</h3><p>The following section covers common questions and answers about the automated installer.</p><p><b>Troubleshooting:</b></p><p><a href="setupfaq.html#dhcperr">1. <tt>installadm create-service</tt> Fails</a></p><p><a href="setupfaq.html#fails">2. What if the Client Installation Fails?</a></p><p><b>Frequently Asked Questions:</b></p><p><a href="faq.html#switch">1. If I Do Not Have Access to the Tools on the System's Desktop, How Do I Switch to a Static IP System ?</a></p><p><a href="faq.html#wanboot">2. Does My SPARC Client Support WAN Boot?</a></p><p><a href="faq.html#image">3. Where Do I Find the AI ISO Image That I Need?</a></p><p><a href="faq.html#modifymanifest">4. How Do I Modify a Custom Manifest File to Point to the Repository of My Choice?</a></p><p><a href="faq.html#match">5. How Do I Install a Particular OpenSolaris Development Build?</a></p><p><a href="faq.html#pool">6. How Do I Locate the Default AI Manifest Provided with an Install Service?</a></p><p><a href="faq.html#cleanup">7. How Can I Cleanup a Failed Service?</a></p><p><a href="faq.html#unconf">8. How Do I Cleanup DHCP Configurations for a SPARC Install Service?</a></p><p><a href="faq.html#verbose">9. How Do I Run Automated Installations in Debug Verbose Mode?</a></p><p><a href="faq.html#remote">10. How Do I Enable Remote Access to an AI Client by Using <tt>ssh</tt>?</a></p><p><a href="faq.html#boot1">11. How Do I Boot the Install Environment Without Starting an Installation?</a></p><p><a href="faq.html#encrypt">12. How Do I Generate Encrypted Passwords?</a></p><p><a href="faq.html#back">13. Is the Automated Installer Backwards Compatible?</a></p><p><a href="faq.html#targetdisk">14. How is the Default Target Disk Selected?</a></p><p><a href="faq.html#howstart">15. If I Booted Into the Install Environment Without Initiating an Installation, How Do I Start the Installation?</a></p><p><a href="faq.html#rename">16. What is the new AI Package Name?</a></p><p><a href="faq.html#isc">17. How do I use ISC DHCP With the Automated Installer?</a></p><p><a href="faq.html#vendor">18. How can I Check the Vendors for my Disks?</a></p><p><a href="faq.html#passwords">19. What are the Default Passwords?</a></p>
- </div>
- </td>
- </tr>
-
- <tr class="PageControls" valign="top">
- <td></td>
- <td>
- <table width="100%">
- <tr>
- <td>
- <a href="bothclient.html">Previous</a>
- </td>
- <td align="right">
- <a href="setupfaq.html">Next</a>
- </td>
- </tr>
- </table>
- </td>
- </tr>
-</tbody>
-</table>
-
-
-</body>
-</html>
-
--- a/usr/src/cmd/installadm/docs/use.html Wed Sep 29 16:37:00 2010 +0200
+++ /dev/null Thu Jan 01 00:00:00 1970 +0000
@@ -1,124 +0,0 @@
-<!DOCTYPE HTML PUBLIC "-//W3C//DTD HTML 4.01 Transitional//EN" "http://www.w3.org/TR/html4/loose.dtd">
-<html lang="en-US">
-
-<!-- -->
-<head>
-<!-- GenHTML revision 23436-->
-<meta http-equiv="Content-type" content="text/html; charset=iso-8859-1">
-<title>How Do I Use the Automated Installer? - OpenSolaris 2010.03 Automated Installer Guide</title>
-<meta name="robots" content="index,follow">
-<meta name="robots" content="index,follow">
-<meta name="date" content="2010-03-01">
-<meta name="collection" content="reference">
-<link rel="stylesheet" type="text/css" href="css/elements.css">
-<link rel="stylesheet" type="text/css" href="css/opensol.css">
-</head>
-
-<body>
-
-
-<div class="Masthead">
- <div class="MastheadLogo">
- <a href="http://www.opensolaris.com"><img border="0" src="graphics/opensolaris_logo_trans.png"></img></a>
- </div>
- <div class="Title">OpenSolaris 2010.03 Automated Installer Guide</div>
-</div>
-<div class="headerbar"></div>
-
-
-<table class="Layout" border="0" cellspacing="0" width="100%">
-<tbody>
-
- <tr valign="top" class="PageControls">
- <td></td>
- <td>
- <table width="100%">
- <tr>
- <td>
- <a href="whatis.html">Previous</a>
- </td>
- <td align="right">
- <a href="clientinstall.html">Next</a>
- </td>
- </tr>
- </table>
- </td>
- </tr>
-
- <tr valign="top">
- <td class="Navigation" width="200px"><p class="toc level1"><a href="docinfo.html">Document Information</a></p>
-<p class="toc level1 tocsp"><a href="index.html">1. What's New For Automated Installations</a></p>
-<p class="toc level1 tocsp"><a href="intro.html">2. Introduction to the Automated Installer</a></p>
-<p class="toc level2"><a href="whatis.html">What Is an Automated Installation?</a></p>
-<div id="scrolltoc" class="onpage">
-<p class="toc level2"><a href="">How Do I Use the Automated Installer?</a></p>
-</div>
-<p class="toc level2"><a href="clientinstall.html">How a Client Is Installed</a></p>
-<p class="toc level2"><a href="benefits.html">Automated Installation Benefits</a></p>
-<p class="toc level1 tocsp"><a href="tasks.html">3. Automated Network Install Task Map</a></p>
-<p class="toc level1 tocsp"><a href="bootable.html">4. Automated Installations That Boot From Media</a></p>
-<p class="toc level1 tocsp"><a href="setup.html">5. Set up an Automated Install Server</a></p>
-<p class="toc level1 tocsp"><a href="administer.html">6. How to Administer an Automated Install Server</a></p>
-<p class="toc level1 tocsp"><a href="client.html">7. How to Administer a Custom Install Client</a></p>
-<p class="toc level1 tocsp"><a href="manifest.html">8. How to Administer Manifest Files</a></p>
-<p class="toc level1 tocsp"><a href="clients.html">9. How to Manage Client Installations</a></p>
-<p class="toc level1 tocsp"><a href="trouble.html">10. Troubleshooting and FAQs for the Automated Installer</a></p>
-<p class="toc level1 tocsp"><a href="appendix.html">11. Appendix</a></p>
-</td>
- <td class="ContentPane" width="705px">
-
- <div class="MainContent">
-
-
-<a name="use"></a><h3>How Do I Use the Automated Installer?</h3>
-<p>Perform the following tasks:</p>
-<ul><li><p>First, choose one of the following options:</p>
-<ul><li><p>If you want to install a few SPARC or x86 client systems by booting directly from an AI CD or DVD without setting up an install server, go to <a href="bootable.html">Chapter 4, Automated Installations That Boot From Media</a>. Use the instructions in that section instead of the network instructions below.</p>
-<hr><p><b>Note - </b>In particular, use this method if your SPARC systems do not have WAN Boot capability.</p>
-<hr>
-</li>
-<li><p>If you want to set up your network, so that you can perform multiple installations using an install server, continue with the following tasks:</p></li></ul>
-</li>
-<li><p>Set up an <b>install server</b> on your network. See <a href="setup.html">Chapter 5, Set up an Automated Install Server</a>.</p><p>This install server manages the resources needed for automated installations to client systems in a network.</p><p>Use the <tt>installadm create-service</tt> command to set up an install server and create an install <b>service</b>. An install service is a network entity that specifies the parameters for a particular type of installation. These specifications are defined in XML <b>manifest</b> files. Specifications include a list of packages to be installed on client systems. These packages are retrieved from an Image Packaging System (IPS) repository on the network. The repository to be used is also specified in the manifest files.</p><p>The automated installer uses <b>AI ISO images</b> to create the install services. An ISO image is an archive file, also known as a disc image, of an optical disc in a format defined by the International Organization for Standardization (ISO). ISO image files typically have a file extension of <tt>.iso</tt>. An automated installation (AI) ISO image is usable for automated installations.</p></li>
-<li><p>After an install server and an install service are set up, you can install the OpenSolaris release to a client on the network, using the default specifications in the service, by booting the client system. See <a href="clientinstall.html">How a Client Is Installed</a>.</p></li>
-<li><p>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 <tt>installadm create-service</tt> 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 <a href="administer.html">Chapter 6, How to Administer an Automated Install Server</a>.</p></li>
-<li><p>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 <tt>installadm add</tt> command to add your new manifests to an install service. See <a href="manifest.html">Chapter 8, How to Administer Manifest Files</a>.</p></li>
-<li><p>If you want a specific client to use a specific install service, you can associate a service with a client by using the <tt>installadm create-client</tt> command. See <a href="client.html">Chapter 7, How to Administer a Custom Install Client</a>.</p></li>
-<li><p>To resolve problems encountered while using the automated installer, see <a href="trouble.html">Chapter 10, Troubleshooting and FAQs for the Automated Installer</a>.</p></li></ul>
-
-
-<a name="gentextid-185"></a><h4><tt>installadm</tt> Utility</h4>
-<p>The <tt>installadm</tt> utility enables you to accomplish the following tasks:</p>
-<ul><li><p>Set up install services and installation images, and set up and update a DHCP server</p></li>
-<li><p>Configure your server</p></li>
-<li><p>Set up or remove custom clients</p></li>
-<li><p>Add or delete manifest files</p></li>
-<li><p>Enable or disable install services</p></li>
-<li><p>List services or list manifests for an install service</p></li></ul>
-<p>For more information, see the <a href="installadm.html"><tt>installadm(1M)</tt> Man Page</a>.</p>
- </div>
- </td>
- </tr>
-
- <tr class="PageControls" valign="top">
- <td></td>
- <td>
- <table width="100%">
- <tr>
- <td>
- <a href="whatis.html">Previous</a>
- </td>
- <td align="right">
- <a href="clientinstall.html">Next</a>
- </td>
- </tr>
- </table>
- </td>
- </tr>
-</tbody>
-</table>
-
-
-</body>
-</html>
-
--- a/usr/src/cmd/installadm/docs/view.html Wed Sep 29 16:37:00 2010 +0200
+++ /dev/null Thu Jan 01 00:00:00 1970 +0000
@@ -1,186 +0,0 @@
-<!DOCTYPE HTML PUBLIC "-//W3C//DTD HTML 4.01 Transitional//EN" "http://www.w3.org/TR/html4/loose.dtd">
-<html lang="en-US">
-
-<!-- -->
-<head>
-<!-- GenHTML revision 23436-->
-<meta http-equiv="Content-type" content="text/html; charset=iso-8859-1">
-<title>How to Review What You Have on Your Server - OpenSolaris 2010.03 Automated Installer Guide</title>
-<meta name="robots" content="index,follow">
-<meta name="robots" content="index,follow">
-<meta name="date" content="2010-03-01">
-<meta name="collection" content="reference">
-<link rel="stylesheet" type="text/css" href="css/elements.css">
-<link rel="stylesheet" type="text/css" href="css/opensol.css">
-</head>
-
-<body>
-
-
-<div class="Masthead">
- <div class="MastheadLogo">
- <a href="http://www.opensolaris.com"><img border="0" src="graphics/opensolaris_logo_trans.png"></img></a>
- </div>
- <div class="Title">OpenSolaris 2010.03 Automated Installer Guide</div>
-</div>
-<div class="headerbar"></div>
-
-
-<table class="Layout" border="0" cellspacing="0" width="100%">
-<tbody>
-
- <tr valign="top" class="PageControls">
- <td></td>
- <td>
- <table width="100%">
- <tr>
- <td>
- <a href="delete.html">Previous</a>
- </td>
- <td align="right">
- <a href="enable.html">Next</a>
- </td>
- </tr>
- </table>
- </td>
- </tr>
-
- <tr valign="top">
- <td class="Navigation" width="200px"><p class="toc level1"><a href="docinfo.html">Document Information</a></p>
-<p class="toc level1 tocsp"><a href="index.html">1. What's New For Automated Installations</a></p>
-<p class="toc level1 tocsp"><a href="intro.html">2. Introduction to the Automated Installer</a></p>
-<p class="toc level1 tocsp"><a href="tasks.html">3. Automated Network Install Task Map</a></p>
-<p class="toc level1 tocsp"><a href="bootable.html">4. Automated Installations That Boot From Media</a></p>
-<p class="toc level1 tocsp"><a href="setup.html">5. Set up an Automated Install Server</a></p>
-<p class="toc level1 tocsp"><a href="administer.html">6. How to Administer an Automated Install Server</a></p>
-<p class="toc level2"><a href="add.html">How to Add Install Services</a></p>
-<p class="toc level2"><a href="delete.html">How to Delete Install Services</a></p>
-<div id="scrolltoc" class="onpage">
-<p class="toc level2"><a href="">How to Review What You Have on Your Server</a></p>
-</div>
-<p class="toc level2"><a href="enable.html">How to Enable and Disable Install Services</a></p>
-<p class="toc level2"><a href="smf.html">How to Administer Install Services by Using the AI SMF Service</a></p>
-<p class="toc level1 tocsp"><a href="client.html">7. How to Administer a Custom Install Client</a></p>
-<p class="toc level1 tocsp"><a href="manifest.html">8. How to Administer Manifest Files</a></p>
-<p class="toc level1 tocsp"><a href="clients.html">9. How to Manage Client Installations</a></p>
-<p class="toc level1 tocsp"><a href="trouble.html">10. Troubleshooting and FAQs for the Automated Installer</a></p>
-<p class="toc level1 tocsp"><a href="appendix.html">11. Appendix</a></p>
-</td>
- <td class="ContentPane" width="705px">
-
- <div class="MainContent">
-
-
-<a name="view"></a><h3>How to Review What You Have on Your Server</h3>
-<p>You can use the following <tt>installadm list</tt> command options to view information about your
-existing install services, associated install clients, and available manifests.</p>
-<ul><li><p><a href="#list">How to List Install Services on the Server</a></p></li>
-<li><p><a href="#list1">How to View Information for a Specified Install Service</a></p></li>
-<li><p><a href="#listman1">How to List all Available Manifests</a></p></li>
-<li><p><a href="#listman">How to List Manifests Associated With an Install Service</a></p></li>
-<li><p><a href="#listclient">How to List Clients Added to Your Install Services</a></p></li>
-<li><p><a href="#listclient1">How to List Clients Added to a Specific Install Service</a></p></li></ul>
-
-
-<a name="list"></a><h4>How to List Install Services on the Server</h4>
-<p>The following command displays all of the enabled install services on your server.</p><pre># <tt>installadm list</tt></pre><p>In the following example, two install services, <tt>svcAI</tt> and <tt>svcAI-new</tt>, are found
-on the server.</p><pre># installadm list
-
-Service Name Status Arch Port Image Path
------------- ------ ---- ---- ----------
-svcAI on x86 46501 /server/images/osol-1002-126-ai
-svcAI-new on x86 46502 /server/images/osol-1003-111b2-ai</pre>
-
-<a name="list1"></a><h4>How to View Information for a Specified Install Service</h4>
-<p>The following command displays information about a specified install service, on your server,
-where <tt>svcname</tt> is the service name.</p><pre># <tt>installadm list <tt>-n</tt> <i>svcname</i></tt></pre><p>In the following example, information about the specified install service, <tt>svcAI</tt>, is
-displayed.</p><pre># installadm list -n svcAI
-
-Service Name Status Arch Port Image Path
------------- ------ ---- ---- ----------
-svcAI on x86 46501 /server/images/osol-1002-126-ai</pre>
-
-<a name="listman1"></a><h4>How to List all Available Manifests</h4>
-<p>The following command lists all the manifests for all install services on your
-server.</p><pre># <tt>installadm list <tt>-m</tt></tt></pre><p>In the following example, all the manifests are displayed for the 2 install
-services, <tt>svcAI</tt> and <tt>svcAI-new</tt>, found on the server.</p><pre># installadm list -m
-
-Service Name Manifest
------------- --------
-svcAI devpublisher
- devpublisher3
- devpublisher4
- devpublisher5
- devpublisher6
-svcAI-new devpublisher7</pre>
-
-<a name="listman"></a><h4>How to List Manifests Associated With an Install Service</h4>
-<p>The following command displays information about all the manifests associated with a specified
-install service, <tt>svcname</tt>.</p><pre># <tt>installadm list <tt>-m</tt> <tt>-n</tt> <i>svcname</i></tt></pre><p>In the following example, details are provided for all the manifests associated with
-the install service, <tt>svcAI-new</tt>.</p><pre># installadm list -m -n svcAI-new
-
-Manifest Criteria
--------- --------
-devpublisher arch = i86pc
- mac = 01:C2:52:E6:4B:E0
-
-devpublisher3 arch = i86pc
- mac = 01:C2:52:E6:4B:E6 - 01:C2:52:E6:4B:E9
-
-devpublisher4 arch = i86pc
- ipv4 = 192.168.168.151
-
-devpublisher5 arch = i86pc
- mac = 01:C4:52:E6:4B:E6 - 01:C4:52:E6:4B:E9
- ipv4 = 192.168.168.251
-
-devpublisher6 arch = i86pc
- mac = 01:C4:51:E6:4B:E6 - 01:C4:51:E6:4B:E9
- ipv4 = 192.168.168.012
- mem = 2048 MB</pre>
-
-<a name="listclient"></a><h4>How to List Clients Added to Your Install Services</h4>
-<p>The following command lists all the clients that have been added to the
-install services on a local server.</p><pre># <tt>installadm list <tt>-c</tt></tt></pre><p>In the following example, all the clients are listed for the two
-install services, <tt>svcAI</tt> and <tt>svcAI-new</tt>, that are found on the server.</p><pre># installadm list -c
-
-Service Name Client Address Arch Image Path
------------- -------------- ---- ----------
-svcAI 01:C2:52:E6:4B:E1 x86 /server/images/osol-1002-126-ai
-svcAI-new 08:00:27:8B:BD:71 x86 /server/images/osol-1003-111b2-ai
- 01:C2:52:E6:4B:E0 x86 /server/images/osol-1002-126-ai </pre>
-
-<a name="listclient1"></a><h4>How to List Clients Added to a Specific Install Service</h4>
-<p>The following command lists all the clients that have been added to a
-specified install service, <tt>svcname</tt>.</p><pre># <tt>installadm list <tt>-c</tt> <tt>-n</tt> <i>svcname</i></tt></pre><p>In the following example, one client has been added to the <tt>svcAI</tt>
-install service.</p><pre># installadm list -c -n svcAI
-
-Service Name Client Address Arch Image Path
------------- -------------- ---- ----------
-svcAI 01:C2:52:E6:4B:E1 x86 /server/images/osol-1002-126-ai </pre>
- </div>
- </td>
- </tr>
-
- <tr class="PageControls" valign="top">
- <td></td>
- <td>
- <table width="100%">
- <tr>
- <td>
- <a href="delete.html">Previous</a>
- </td>
- <td align="right">
- <a href="enable.html">Next</a>
- </td>
- </tr>
- </table>
- </td>
- </tr>
-</tbody>
-</table>
-
-
-</body>
-</html>
-
--- a/usr/src/cmd/installadm/docs/whatis.html Wed Sep 29 16:37:00 2010 +0200
+++ /dev/null Thu Jan 01 00:00:00 1970 +0000
@@ -1,120 +0,0 @@
-<!DOCTYPE HTML PUBLIC "-//W3C//DTD HTML 4.01 Transitional//EN" "http://www.w3.org/TR/html4/loose.dtd">
-<html lang="en-US">
-
-<!-- -->
-<head>
-<!-- GenHTML revision 23436-->
-<meta http-equiv="Content-type" content="text/html; charset=iso-8859-1">
-<title>What Is an Automated Installation? - OpenSolaris 2010.03 Automated Installer Guide</title>
-<meta name="robots" content="index,follow">
-<meta name="robots" content="index,follow">
-<meta name="date" content="2010-03-01">
-<meta name="collection" content="reference">
-<link rel="stylesheet" type="text/css" href="css/elements.css">
-<link rel="stylesheet" type="text/css" href="css/opensol.css">
-</head>
-
-<body>
-
-
-<div class="Masthead">
- <div class="MastheadLogo">
- <a href="http://www.opensolaris.com"><img border="0" src="graphics/opensolaris_logo_trans.png"></img></a>
- </div>
- <div class="Title">OpenSolaris 2010.03 Automated Installer Guide</div>
-</div>
-<div class="headerbar"></div>
-
-
-<table class="Layout" border="0" cellspacing="0" width="100%">
-<tbody>
-
- <tr valign="top" class="PageControls">
- <td></td>
- <td>
- <table width="100%">
- <tr>
- <td>
- <a href="intro.html">Previous</a>
- </td>
- <td align="right">
- <a href="use.html">Next</a>
- </td>
- </tr>
- </table>
- </td>
- </tr>
-
- <tr valign="top">
- <td class="Navigation" width="200px"><p class="toc level1"><a href="docinfo.html">Document Information</a></p>
-<p class="toc level1 tocsp"><a href="index.html">1. What's New For Automated Installations</a></p>
-<p class="toc level1 tocsp"><a href="intro.html">2. Introduction to the Automated Installer</a></p>
-<div id="scrolltoc" class="onpage">
-<p class="toc level2"><a href="">What Is an Automated Installation?</a></p>
-</div>
-<p class="toc level2"><a href="use.html">How Do I Use the Automated Installer?</a></p>
-<p class="toc level2"><a href="clientinstall.html">How a Client Is Installed</a></p>
-<p class="toc level2"><a href="benefits.html">Automated Installation Benefits</a></p>
-<p class="toc level1 tocsp"><a href="tasks.html">3. Automated Network Install Task Map</a></p>
-<p class="toc level1 tocsp"><a href="bootable.html">4. Automated Installations That Boot From Media</a></p>
-<p class="toc level1 tocsp"><a href="setup.html">5. Set up an Automated Install Server</a></p>
-<p class="toc level1 tocsp"><a href="administer.html">6. How to Administer an Automated Install Server</a></p>
-<p class="toc level1 tocsp"><a href="client.html">7. How to Administer a Custom Install Client</a></p>
-<p class="toc level1 tocsp"><a href="manifest.html">8. How to Administer Manifest Files</a></p>
-<p class="toc level1 tocsp"><a href="clients.html">9. How to Manage Client Installations</a></p>
-<p class="toc level1 tocsp"><a href="trouble.html">10. Troubleshooting and FAQs for the Automated Installer</a></p>
-<p class="toc level1 tocsp"><a href="appendix.html">11. Appendix</a></p>
-</td>
- <td class="ContentPane" width="705px">
-
- <div class="MainContent">
-
-
-<a name="whatis"></a><h3>What Is an Automated Installation?</h3>
-<p>The automated installer is used to automate the installation of the OpenSolaris OS
-on one or more SPARC and x86 systems. The installations can differ in
-architecture, packages installed, disk capacity, and other parameters.</p><p>To boot and install client systems over the network, 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 <b>install service</b>, which is associated with <b>manifests</b>, 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.</p><img src="figures/AIinstall.gif" alt="Automated installs over the network" width="404" height="377"></img><p>An automated installation over the network to a client system, as shown in
-the graphic, performs the following core steps:</p>
-<ol><li><p>A client system boots and gets IP information from the DHCP server.</p></li>
-<li><p>The client contacts an install service on the AI server, and accesses the boot image, and accesses the AI manifest containing installation specifications.</p></li>
-<li><p>The client is installed with the OpenSolaris release, pulling packages from the IPS repository specified in the AI manifest.</p></li></ol>
-<p>Alternately, <b>starting with the OpenSolaris 2010.03 release</b>, you can install the OpenSolaris OS directly on individual SPARC or
-x86 client systems by booting from AI media such as a CD,
-DVD, or a USB stick. This method provides a fast and simple way
-to install a few individual systems, without setting up an install server. You
-can use this method even if your SPARC systems do not have WAN
-Boot capability. See <a href="bootable.html">Chapter 4, Automated Installations That Boot From Media</a>.</p>
- </div>
- </td>
- </tr>
-
- <tr class="PageControls" valign="top">
- <td></td>
- <td>
- <table width="100%">
- <tr>
- <td>
- <a href="intro.html">Previous</a>
- </td>
- <td align="right">
- <a href="use.html">Next</a>
- </td>
- </tr>
- </table>
- </td>
- </tr>
-</tbody>
-</table>
-
-
-</body>
-</html>
-
--- a/usr/src/cmd/installadm/docs/whybootable.html Wed Sep 29 16:37:00 2010 +0200
+++ /dev/null Thu Jan 01 00:00:00 1970 +0000
@@ -1,108 +0,0 @@
-<!DOCTYPE HTML PUBLIC "-//W3C//DTD HTML 4.01 Transitional//EN" "http://www.w3.org/TR/html4/loose.dtd">
-<html lang="en-US">
-
-<!-- -->
-<head>
-<!-- GenHTML revision 23436-->
-<meta http-equiv="Content-type" content="text/html; charset=iso-8859-1">
-<title>Why Boot From AI Media? - OpenSolaris 2010.03 Automated Installer Guide</title>
-<meta name="robots" content="index,follow">
-<meta name="robots" content="index,follow">
-<meta name="date" content="2010-03-01">
-<meta name="collection" content="reference">
-<link rel="stylesheet" type="text/css" href="css/elements.css">
-<link rel="stylesheet" type="text/css" href="css/opensol.css">
-</head>
-
-<body>
-
-
-<div class="Masthead">
- <div class="MastheadLogo">
- <a href="http://www.opensolaris.com"><img border="0" src="graphics/opensolaris_logo_trans.png"></img></a>
- </div>
- <div class="Title">OpenSolaris 2010.03 Automated Installer Guide</div>
-</div>
-<div class="headerbar"></div>
-
-
-<table class="Layout" border="0" cellspacing="0" width="100%">
-<tbody>
-
- <tr valign="top" class="PageControls">
- <td></td>
- <td>
- <table width="100%">
- <tr>
- <td>
- <a href="bootable.html">Previous</a>
- </td>
- <td align="right">
- <a href="bootableclientreq.html">Next</a>
- </td>
- </tr>
- </table>
- </td>
- </tr>
-
- <tr valign="top">
- <td class="Navigation" width="200px"><p class="toc level1"><a href="docinfo.html">Document Information</a></p>
-<p class="toc level1 tocsp"><a href="index.html">1. What's New For Automated Installations</a></p>
-<p class="toc level1 tocsp"><a href="intro.html">2. Introduction to the Automated Installer</a></p>
-<p class="toc level1 tocsp"><a href="tasks.html">3. Automated Network Install Task Map</a></p>
-<p class="toc level1 tocsp"><a href="bootable.html">4. Automated Installations That Boot From Media</a></p>
-<div id="scrolltoc" class="onpage">
-<p class="toc level2"><a href="">Why Boot From AI Media?</a></p>
-</div>
-<p class="toc level2"><a href="bootableclientreq.html">System Requirements for Automated Installations Using Media</a></p>
-<p class="toc level2"><a href="howbootable.html">How to Install Using Media</a></p>
-<p class="toc level1 tocsp"><a href="setup.html">5. Set up an Automated Install Server</a></p>
-<p class="toc level1 tocsp"><a href="administer.html">6. How to Administer an Automated Install Server</a></p>
-<p class="toc level1 tocsp"><a href="client.html">7. How to Administer a Custom Install Client</a></p>
-<p class="toc level1 tocsp"><a href="manifest.html">8. How to Administer Manifest Files</a></p>
-<p class="toc level1 tocsp"><a href="clients.html">9. How to Manage Client Installations</a></p>
-<p class="toc level1 tocsp"><a href="trouble.html">10. Troubleshooting and FAQs for the Automated Installer</a></p>
-<p class="toc level1 tocsp"><a href="appendix.html">11. Appendix</a></p>
-</td>
- <td class="ContentPane" width="705px">
-
- <div class="MainContent">
-
-
-<a name="whybootable"></a><h3>Why Boot From AI Media?</h3>
-<p>Automated installations that boot off an automated installation (AI) CD, DVD, or USB
-stick are particularly useful for the following reasons.</p>
-<ul><li><p>Automated installations that boot off media save time, since you don't have to set up an install server or install services. The client system will boot from the AI media instead of booting from an install server.</p></li>
-<li><p>By booting off media, you can install to SPARC systems that do not have WAN Boot capability.</p></li>
-<li><p>Automated installations that boot off media provide a fast, effective way to install clients that require little or customization.</p>
-<hr><p><b>Note - </b>The installation specifications are provided in a manifest. You have the option of using the default manifest, or you could create a custom manifest.</p>
-<hr>
-</li>
-<li><p>The AI media that you create can be used as a rescue disk. Once you have created the CD, DVD, or USB stick, you can use it to perform simple “hands-off” automated installations to your x86 or SPARC client systems. The installations are non-interactive.</p></li></ul>
-
- </div>
- </td>
- </tr>
-
- <tr class="PageControls" valign="top">
- <td></td>
- <td>
- <table width="100%">
- <tr>
- <td>
- <a href="bootable.html">Previous</a>
- </td>
- <td align="right">
- <a href="bootableclientreq.html">Next</a>
- </td>
- </tr>
- </table>
- </td>
- </tr>
-</tbody>
-</table>
-
-
-</body>
-</html>
-
--- a/usr/src/cmd/installadm/docs/x86client.html Wed Sep 29 16:37:00 2010 +0200
+++ /dev/null Thu Jan 01 00:00:00 1970 +0000
@@ -1,290 +0,0 @@
-<!DOCTYPE HTML PUBLIC "-//W3C//DTD HTML 4.01 Transitional//EN" "http://www.w3.org/TR/html4/loose.dtd">
-<html lang="en-US">
-
-<!-- -->
-<head>
-<!-- GenHTML revision 23436-->
-<meta http-equiv="Content-type" content="text/html; charset=iso-8859-1">
-<title>x86 Client Installations - OpenSolaris 2010.03 Automated Installer Guide</title>
-<meta name="robots" content="index,follow">
-<meta name="robots" content="index,follow">
-<meta name="date" content="2010-03-01">
-<meta name="collection" content="reference">
-<link rel="stylesheet" type="text/css" href="css/elements.css">
-<link rel="stylesheet" type="text/css" href="css/opensol.css">
-</head>
-
-<body>
-
-
-<div class="Masthead">
- <div class="MastheadLogo">
- <a href="http://www.opensolaris.com"><img border="0" src="graphics/opensolaris_logo_trans.png"></img></a>
- </div>
- <div class="Title">OpenSolaris 2010.03 Automated Installer Guide</div>
-</div>
-<div class="headerbar"></div>
-
-
-<table class="Layout" border="0" cellspacing="0" width="100%">
-<tbody>
-
- <tr valign="top" class="PageControls">
- <td></td>
- <td>
- <table width="100%">
- <tr>
- <td>
- <a href="sparcclient.html">Previous</a>
- </td>
- <td align="right">
- <a href="bothclient.html">Next</a>
- </td>
- </tr>
- </table>
- </td>
- </tr>
-
- <tr valign="top">
- <td class="Navigation" width="200px"><p class="toc level1"><a href="docinfo.html">Document Information</a></p>
-<p class="toc level1 tocsp"><a href="index.html">1. What's New For Automated Installations</a></p>
-<p class="toc level1 tocsp"><a href="intro.html">2. Introduction to the Automated Installer</a></p>
-<p class="toc level1 tocsp"><a href="tasks.html">3. Automated Network Install Task Map</a></p>
-<p class="toc level1 tocsp"><a href="bootable.html">4. Automated Installations That Boot From Media</a></p>
-<p class="toc level1 tocsp"><a href="setup.html">5. Set up an Automated Install Server</a></p>
-<p class="toc level1 tocsp"><a href="administer.html">6. How to Administer an Automated Install Server</a></p>
-<p class="toc level1 tocsp"><a href="client.html">7. How to Administer a Custom Install Client</a></p>
-<p class="toc level1 tocsp"><a href="manifest.html">8. How to Administer Manifest Files</a></p>
-<p class="toc level1 tocsp"><a href="clients.html">9. How to Manage Client Installations</a></p>
-<p class="toc level2"><a href="clientreq.html">Client System Requirements</a></p>
-<p class="toc level2"><a href="sparcclient.html">SPARC Client Installations</a></p>
-<div id="scrolltoc" class="onpage">
-<p class="toc level2"><a href="">x86 Client Installations</a></p>
-</div>
-<p class="toc level2"><a href="bothclient.html">SPARC and x86 Client Installation Messages and Errors</a></p>
-<p class="toc level1 tocsp"><a href="trouble.html">10. Troubleshooting and FAQs for the Automated Installer</a></p>
-<p class="toc level1 tocsp"><a href="appendix.html">11. Appendix</a></p>
-</td>
- <td class="ContentPane" width="705px">
-
- <div class="MainContent">
-
-
-<a name="x86client"></a><h3>x86 Client Installations</h3>
-<p>Review the following information about x86 client installations that boot over the network.</p>
-<ul><li><p><a href="#x86boot">What Happens During the x86 Network Boot Sequence?</a></p></li>
-<li><p><a href="#x86boot2">What Should I See During the x86 Network Boot Sequence?</a></p></li>
-<li><p><a href="#x86err">x86 Network Booting Errors and Possible Causes</a></p></li></ul>
-
-
-<a name="x86boot"></a><h4>What Happens During the x86 Network Boot Sequence?</h4>
-<p>Boot the client from the network. For x86 clients, select the network device
-to boot from.</p>
-<hr><p><b>Note - </b>It may be necessary to modify the BIOS configuration to select network booting.</p>
-<hr>
-<p>The GRUB menu appears with two menu entries. Select the second
-entry for the automated installation to take place.</p>
-<hr><p><b>Note - </b><b>Starting with the OpenSolaris 2010.03 release</b>, for x86 installations that boot over the network, the GRUB menu displays
-as follows:</p><pre>OpenSolaris 2010.03 boot image
-OpenSolaris 2010.03 Automated Install</pre><p>The default GRUB menu entry, “OpenSolaris 2010.03 boot image,” boots the image without
-starting a hands-free automated installation. You must select the second entry in the
-GRUB menu, “OpenSolaris 2010.03 Automated Install,” to initiate a “hands-free” automated installation.</p>
-<hr>
-<p>The technical details of what occurs during the automated installer (AI) boot of
-an x86 client are as follows:</p>
-<ol><li><p>The client boots and gets an IP address, and the bootfile, <tt>pxegrub</tt>, is downloaded from the location provided by the DHCP server.</p></li>
-<li><p><tt>pxegrub</tt> is loaded and reads a <tt>menu.lst</tt> file.</p></li>
-<li><p><tt>pxegrub</tt> gets the <tt>boot_archive</tt> file and Solaris is booted using TFTP.</p></li>
-<li><p>The net image archives, <tt>solaris.zlib</tt> and <tt>solarismisc.zlib</tt>, are downloaded using HTTP as provided by the GRUB menu.</p></li>
-<li><p>The manifest is downloaded from an HTPP server specified in the GRUB menu or from the mDNS lookup performed by the AI SMF service.</p></li>
-<li><p>The AI install program is invoked with the AI manifest to perform the installation.</p></li></ol>
-
-
-<a name="x86boot2"></a><h4>What Should I See During the x86 Network Boot Sequence?</h4>
-<p>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.</p><p>The first screen displays the following message when the client receives the
-correct DHCP response:</p><pre>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</pre><p>Next, the display shows the GRUB menu with two menu entries for
-the AI image that will be booted. Typically, these entries look like
-this.</p><pre>OpenSolaris 2010.03 boot image
-OpenSolaris 2010.03 Automated Install </pre><p>You must select to boot the second entry for the automated installation to
-take place. The first entry boots the system into the automated install boot
-image, but the installation is not enabled.</p>
-<hr><p><b>Note - </b>The first entry is automatically selected after a timeout.</p>
-<hr>
-<p>Once the image is selected, the following messages are displayed.</p><pre>OpenSolarisOS Release 5.11 Version snv_111 64-bit
-...
-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-1003-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-1003-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-1003-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</pre>
-
-<a name="x86err"></a><h4>x86 Network Booting Errors and Possible Causes</h4>
-<p>Review the following information about x86 booting errors:</p><p><a href="#nodhcp">1. No DHCP or ProxyDHCP Offers Were Received</a></p><p><a href="#violation">2. TFTP Error or System Hangs After GATEWAY Message</a></p><p><a href="#hangs">3. System Hangs After GRUB Menu Entry is Selected</a></p><p><a href="#forbid2">4. HTTP Request Sent Results in 403 Forbidden or 404 Not Found</a></p><p><a href="#disabledx">5. Auto-installer Disabled</a></p>
-
-<a name="nodhcp"></a><h5>1. No DHCP or ProxyDHCP Offers Were Received</h5>
-<p>If a DHCP server is not responding to an x86 client's request,
-you see the following messages:</p><pre>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 Agent</pre><p>The 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.</p>
-
-<a name="violation"></a><h5>2. TFTP Error or System Hangs After GATEWAY Message</h5>
-<p>The DHCP server provides an IP address and a location of the
-initial boot program as part of the DHCP response.</p>
-<ul><li><p>If the boot program does not exist, then the AI client boot cannot proceed. The following message is displayed:</p><pre>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</pre></li>
-<li><p>If the boot program exists, but it's an incorrect program, the AI client hangs after displaying this message:</p><pre>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</pre></li></ul>
-
-
-<a name="hangs"></a><h5>3. System Hangs After GRUB Menu Entry is Selected</h5>
-<p>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.</p><p>On the install server, check whether the <tt>menu.lst</tt> 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<tt> /tftpboot</tt> directory as shown
-in this sample snippet from <tt>df -k</tt>:</p><pre><tt>/export/home/images/osol-1003-ai-x86/boot</tt> \
-<tt>60450439 21678071 38772368 36% /tftpboot/I86PC.OpenSolaris-12</tt></pre>
-<hr><p><b>Note - </b><tt>I86PC.OpenSolaris-12</tt> is a sample. The number may vary on your system.</p>
-<hr>
-<p>If you know the name of the target directory that you used
-in the <tt>installadm create-service</tt> command, then you can use that information to find out
-whether that target directory is mounted. Also, check whether you can access the
-<tt>/tftpboot/I86PC.OpenSolaris-12/boot_archive</tt> file.</p>
-
-<a name="forbid2"></a><h5>4. HTTP Request Sent Results in 403 Forbidden or 404 Not Found</h5>
-<p>On the install server, if one of the install programs is inaccessible or
-does not exist in the location specified in the<tt> menu.lst</tt> file under <tt>/tftpboot</tt>,
-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 following output, the <tt>solaris.zlib</tt> file does not
-exist at the specified location.</p><pre>OpenSolarisOS Release 5.11 Version snv_111 64-bit
- ...
- 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 run</pre><p>Check the contents of the target directory that you specified when you ran
-the <tt>installadm create-service</tt> command.</p>
-
-<a name="disabledx"></a><h5>5. Auto-installer Disabled</h5>
-<p>When installing the OpenSolaris 2010.03 release on a client system, for x86 installations
-that boot over the network, you must select the second entry in the
-GRUB boot menu to initiate an automated installation. Typically, the menu entries display
-as follows:</p><pre>OpenSolaris 2010.03 boot image
-OpenSolaris 2010.03 Automated Install</pre>
-<hr><p><b>Note - </b>The default GRUB menu entry no longer starts a “hands-free” automated installation.
-Instead, the first entry boots into the AI boot image and presents a
-console-login, but automated installation does not start.</p>
-<hr>
-<p>If you selected the first GRUB menu entry, or allowed the prompt
-to time out, the system boots into the automated install boot image, but
-the installation does not start. The following message is displayed.</p><pre>Auto-installer disabled. Enable the auto-installer service
-by running the following command:
-svcadm enable svc:/application/auto-installer:default</pre><p>You should reboot your system and select the second menu entry to
-boot and initiate the installation.</p>
-<hr><p><b>Caution - </b>If you are installing using an OpenSolaris 2009.06 AI ISO image, use the
-booting instructions for the prior OpenSolaris releases. See FAQ #11 at <a href="http://dlc.sun.com/osol/docs/content/2009.06/AIinstall/faq.html">http://dlc.sun.com/osol/docs/content/2009.06/AIinstall/faq.html</a>.</p>
-<hr>
-
- </div>
- </td>
- </tr>
-
- <tr class="PageControls" valign="top">
- <td></td>
- <td>
- <table width="100%">
- <tr>
- <td>
- <a href="sparcclient.html">Previous</a>
- </td>
- <td align="right">
- <a href="bothclient.html">Next</a>
- </td>
- </tr>
- </table>
- </td>
- </tr>
-</tbody>
-</table>
-
-
-</body>
-</html>
-
--- a/usr/src/man/installadm.1m.txt Wed Sep 29 16:37:00 2010 +0200
+++ b/usr/src/man/installadm.1m.txt Thu Sep 30 11:55:50 2010 -0700
@@ -279,8 +279,8 @@
via a criteria XML file (-C).
-m <manifest>
- Required: Specifies the path name to a criteria
- manifest.
+ Required: Specifies the path name of the manifest
+ to add.
-n <svcname>
Required: Specifies the name of the install
@@ -296,7 +296,6 @@
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."
-
-c <-c <criteria=value|range> ...>
Optional: Specifies criteria to be associated with the
@@ -569,19 +568,14 @@
information.
- Example 3: Use the following sample command
- to add a new custom manifest to an existing install
- service:
+ Example 3: Use the following sample command to replace
+ the default manifest for an existing install service,
+ service_092910, with a custom manifest, my_manifest.xml.
+ The manifest contains a name attribute, name="default",
+ which designates it as the default manifest.
- # installadm add-manifest -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/.
+ # installadm add-manifest -m my_manifest.xml \
+ -n service_092910
Example 4: Use the following sample command to list the
@@ -694,15 +688,12 @@
SEE ALSO
pntadm(1M), dhcpmgr(1M), attributes(5)
- OpenSolaris Automated Installer Guide at
- /usr/share/doc/auto_install/index.html or at
- http://dlc.sun.com/osol/docs/content/dev/
- AIinstall/
+ Oracle Solaris Automated Installer Guide on
+ http://docs.sun.com/
- Getting Started With OpenSolaris at
- http://dlc.sun.com/osol/docs/content/dev/
- getstart/
+ Getting Started with Oracle Solaris on
+ http://docs.sun.com/
- Last Changed August 17, 2010
+ Last Changed September 29, 2010
--- a/usr/src/pkg/manifests/install-installadm.mf Wed Sep 29 16:37:00 2010 +0200
+++ b/usr/src/pkg/manifests/install-installadm.mf Thu Sep 30 11:55:50 2010 -0700
@@ -54,11 +54,6 @@
dir path=usr/sbin
dir path=usr/share group=sys
dir path=usr/share/auto_install group=sys
-dir path=usr/share/doc group=other
-dir path=usr/share/doc/auto_install
-dir path=usr/share/doc/auto_install/css
-dir path=usr/share/doc/auto_install/figures
-dir path=usr/share/doc/auto_install/graphics
dir path=usr/share/man
dir path=usr/share/man/man1m
dir path=usr/share/xml
@@ -99,62 +94,6 @@
file path=usr/lib/python2.6/vendor-packages/osol_install/libaiscf.py mode=0444
file path=usr/sbin/installadm mode=0555
file path=usr/share/auto_install/criteria_schema.rng group=sys
-file path=usr/share/doc/auto_install/add.html mode=0444
-file path=usr/share/doc/auto_install/administer.html mode=0444
-file path=usr/share/doc/auto_install/advancedsetup.html mode=0444
-file path=usr/share/doc/auto_install/aimanifest.html mode=0444
-file path=usr/share/doc/auto_install/appendix.html mode=0444
-file path=usr/share/doc/auto_install/associate.html mode=0444
-file path=usr/share/doc/auto_install/autoinstall.html mode=0444
-file path=usr/share/doc/auto_install/basic.html mode=0444
-file path=usr/share/doc/auto_install/benefits.html mode=0444
-file path=usr/share/doc/auto_install/bootable.html mode=0444
-file path=usr/share/doc/auto_install/bootableclientreq.html mode=0444
-file path=usr/share/doc/auto_install/bothclient.html mode=0444
-file path=usr/share/doc/auto_install/cclient.html mode=0444
-file path=usr/share/doc/auto_install/client.html mode=0444
-file path=usr/share/doc/auto_install/clientinstall.html mode=0444
-file path=usr/share/doc/auto_install/clientreq.html mode=0444
-file path=usr/share/doc/auto_install/clients.html mode=0444
-file path=usr/share/doc/auto_install/criteria.html mode=0444
-file path=usr/share/doc/auto_install/css/advanced.css mode=0444
-file path=usr/share/doc/auto_install/css/elements.css mode=0444
-file path=usr/share/doc/auto_install/css/opensol.css mode=0444
-file path=usr/share/doc/auto_install/customai.html mode=0444
-file path=usr/share/doc/auto_install/customsc.html mode=0444
-file path=usr/share/doc/auto_install/delclient.html mode=0444
-file path=usr/share/doc/auto_install/delete.html mode=0444
-file path=usr/share/doc/auto_install/docinfo.html mode=0444
-file path=usr/share/doc/auto_install/enable.html mode=0444
-file path=usr/share/doc/auto_install/faq.html mode=0444
-file path=usr/share/doc/auto_install/figures/aiflow.gif mode=0444
-file path=usr/share/doc/auto_install/figures/AIinstall.gif mode=0444
-file path=usr/share/doc/auto_install/figures/bootableAI_1.gif mode=0444
-file path=usr/share/doc/auto_install/gentextid-45.html mode=0444
-file path=usr/share/doc/auto_install/graphics/header_gradientpart.png mode=0444
-file path=usr/share/doc/auto_install/graphics/opensolaris_logo_trans.png mode=0444
-file path=usr/share/doc/auto_install/help.html mode=0444
-file path=usr/share/doc/auto_install/howbootable.html mode=0444
-file path=usr/share/doc/auto_install/index.html mode=0444
-file path=usr/share/doc/auto_install/initial.html mode=0444
-file path=usr/share/doc/auto_install/installadm.html mode=0444
-file path=usr/share/doc/auto_install/intro.html mode=0444
-file path=usr/share/doc/auto_install/manifest.html mode=0444
-file path=usr/share/doc/auto_install/manifest1.html mode=0444
-file path=usr/share/doc/auto_install/scenario.html mode=0444
-file path=usr/share/doc/auto_install/setup.html mode=0444
-file path=usr/share/doc/auto_install/setupfaq.html mode=0444
-file path=usr/share/doc/auto_install/simple.html mode=0444
-file path=usr/share/doc/auto_install/smf.html mode=0444
-file path=usr/share/doc/auto_install/sparcclient.html mode=0444
-file path=usr/share/doc/auto_install/tasks.html mode=0444
-file path=usr/share/doc/auto_install/tasks1.html mode=0444
-file path=usr/share/doc/auto_install/trouble.html mode=0444
-file path=usr/share/doc/auto_install/use.html mode=0444
-file path=usr/share/doc/auto_install/view.html mode=0444
-file path=usr/share/doc/auto_install/whatis.html mode=0444
-file path=usr/share/doc/auto_install/whybootable.html mode=0444
-file path=usr/share/doc/auto_install/x86client.html mode=0444
file path=usr/share/man/man1m/installadm.1m mode=0444
file path=var/installadm/ai-webserver/ai-httpd.conf
file path=var/installadm/ai-webserver/AI.db
