Deployment tasks 22
JumpStart preparation
Solaris JumpStart is a complex topic that is beyond the scope of this guide. However, this section
describes some prerequisites for installing JumpStart that are specific to ProLiant. For more information
about Solaris JumpStart, see Solaris 10 11/06 Installation Guide: Custom JumpStart and Advanced
Installations at http://docs.sun.com/app/docs/doc/819-6397
.
This section also includes descriptions of a JumpStart configuration, requirements specific to ProLiant, and
a complete configuration example.
Overview of JumpStart preparation
JumpStart automates Solaris deployments by providing configuration information for which the Solaris
installer would ordinarily interactively prompt the user.
A basic JumpStart configuration consists of the following components:
• rules—The rules file provides instructions for selecting a JumpStart profile based on various
user-selectable criteria such as platform architecture, system model, and so on, as well as custom
criteria.
• Profile—A JumpStart profile file provides certain installation configuration information such as file
system layout, disk partitioning, and which packages are to be installed.
• sysidcfg(4)—A sysidcfg file provides the system identification information such as root password,
networking parameters, time zone, and so on.
• Begin and finish scripts—These are optional scripts that run before and immediately after installation
and can be customized to perform pre- and post-installation configuration.
The rules file, profile file, and begin and finish scripts must be in the same directory, and are
typically made available to clients through NFS.
Prerequisites for JumpStart preparation
This section describes ProLiant-specific prerequisites for installing JumpStart.
Additional required packages
Some drivers that are not included on the Solaris media are usually required for proper use of Solaris on
ProLiant servers. These drivers include the Smart Array driver and the Broadcom NetXtreme II network
driver. For automated deployments, provisions must be made for these drivers to be installed on the
system during operating system installation. To make these provisions, perform either of the following
steps:
• Use the package profile keyword to install the additional packages through NFS. See “Example:
JumpStart preparation.”
• Use a finish script to install the additional packages using pkgadd(1M). For a complete example, see
the Sun documentation.
