HP Dl180 - G6 E5504 2X2gb 4Lff Svr Quick reference guide

Sun Solaris 10
Deployment Guide for HP ProLiant Servers
Part number 455522-003
Third edition 11/2009

Legal notices
© Copyright 2007, 2009 Hewlett-Packard Development Company, L.P.
Confidential computer software. Valid license from HP required for possession, use or copying. Consistent with FAR 12.211
and 12.212, Commercial Computer Software, Computer Software Documentation, and Technical Data for Commercial
Items are licensed to the U.S. Government under vendor's standard commercial license.
The information contained herein is subject to change without notice. The only warranties for HP products and services are
set forth in the express warranty statements accompanying such products and services. Nothing herein should be construed
as constituting an additional warranty. HP shall not be liable for technical or editorial errors or omissions contained herein.
Microsoft and Windows are U.S. registered trademarks of Microsoft Corporation. UNIX is a registered trademark of The
Open Group. Intel is a trademark of Intel Corporation in the U.S. and other countries. Java is a U.S. trademark of Sun
Microsystems, Inc. AMD is a trademark of Advanced Micro Devices, Inc.

Contents 3
Contents
Introduction .........................................................................................................................................6
Applicable servers and OS versions..............................................................................................................6
Using this guide..........................................................................................................................................7
Basic installations.................................................................................................................................8
Prerequisites ...............................................................................................................................................8
Installing Solaris interactively........................................................................................................................9
Architecture of an installation...............................................................................................................10
General process flow ................................................................................................................................10
Primary installation components..................................................................................................................10
GRUB .................................................................................................................................................10
Miniroot..............................................................................................................................................11
Configuration information .....................................................................................................................11
Packages ............................................................................................................................................11
Network deployment infrastructure..............................................................................................................11
DHCP server........................................................................................................................................12
TFTP server ..........................................................................................................................................12
JumpStart server...................................................................................................................................12
Install server ........................................................................................................................................12
Deploying ProLiant servers .........................................................................................................................12
Additional drivers ................................................................................................................................13
Miniroot..............................................................................................................................................13
JumpStart ............................................................................................................................................14
iLO virtual media .................................................................................................................................14
Rapid Deployment Pack........................................................................................................................14
Flash archives......................................................................................................................................15
Deployment resource kit........................................................................................................................15
Deployment planning..........................................................................................................................16
Selecting a deployment strategy .................................................................................................................16
Boot methods.......................................................................................................................................16
Configuration methods .........................................................................................................................17
Software delivery methods ....................................................................................................................17
Implementing a PXE boot-based deployment ................................................................................................17
Implementing an Rapid Deployment Pack -initiated deployment .....................................................................18
Implementing a custom ISO boot-based deployment .....................................................................................18
Deployment tasks ...............................................................................................................................19
Install server preparation ...........................................................................................................................19
Prerequisites for preparing an install server.............................................................................................19
Preparing the install server ....................................................................................................................20
Miniroot preparation .................................................................................................................................21
Prerequisites for preparing a miniroot ....................................................................................................21
Preparing a miniroot ............................................................................................................................21
JumpStart preparation ...............................................................................................................................23
Overview of JumpStart preparation........................................................................................................23
Prerequisites for JumpStart preparation...................................................................................................23
Example: JumpStart preparation ............................................................................................................24
DHCP/PXE preparation .............................................................................................................................26

Contents 4
Prerequisites for DHCP/PXE preparation.................................................................................................26
Preparing the DHCP/PXE server ............................................................................................................27
Rapid Deployment Pack server preparation..................................................................................................28
Overview of Rapid Deployment Pack server preparation..........................................................................29
Prerequisites for Rapid Deployment Pack server preparation.....................................................................29
Configuring the Rapid Deployment Pack deployment server .....................................................................29
GRUB preparation ....................................................................................................................................30
Overview of GRUB preparation.............................................................................................................30
Booting Solaris from GRUB ...................................................................................................................31
Examples: booting Solaris from GRUB....................................................................................................32
Custom bootable ISO image creation..........................................................................................................33
Prerequisites for creating a custom bootable ISO image...........................................................................33
Creating a custom bootable ISO image..................................................................................................33
Optional configuration tasks ................................................................................................................34
Enabling iLO virtual serial port ...................................................................................................................34
Mirroring disks with DiskSuite ....................................................................................................................34
Unmirroring disks with DiskSuite.................................................................................................................36
Troubleshooting .................................................................................................................................38
Known issues............................................................................................................................................38
Write cache not flushed on shutdown.....................................................................................................38
Solaris stops responding on HP ProLiant DL580 G5 server .......................................................................38
RAID mode not supported .....................................................................................................................39
Kernel Panic after disabling PCI devices in RBSU.....................................................................................39
Network configuration fails during interactive installation.........................................................................39
iLO boot hang .....................................................................................................................................40
AMD memory scrubber.........................................................................................................................40
SNMP master agent .............................................................................................................................40
bcme fails to attach..............................................................................................................................41
System panics and reboots during installation.........................................................................................42
Embedded Ethernet not configured ........................................................................................................42
Hard Drives not seen after CPQary3 added to Miniroot...........................................................................42
Basic troubleshooting techniques ................................................................................................................43
Shell prompt........................................................................................................................................43
Network verification.............................................................................................................................43
GRUB command line............................................................................................................................44
Kernel debugger..................................................................................................................................44
Common issues.........................................................................................................................................44
System does not boot to GRUB ..............................................................................................................44
GRUB does not display a menu .............................................................................................................44
GRUB cannot boot Solaris ....................................................................................................................45
JumpStart deployment ignores GRUB command line arguments.................................................................45
System becomes unresponsive using remote console................................................................................45
Rapid Deployment Pack job fails ...........................................................................................................45
Installation terminates prematurely .........................................................................................................46
JumpStart reverts to interactive configuration...........................................................................................46
Installation succeeds but server fails to boot ............................................................................................47
Installation succeeds but no network availability after reboot ....................................................................47
Additional documentation ...................................................................................................................48
Where to go for additional help.................................................................................................................48
HP documentation................................................................................................................................48
Free Software Foundation documentation ...............................................................................................48
Intel documentation ..............................................................................................................................48

Contents 5
Sun Microsystems documentation...........................................................................................................48
Glossary ...........................................................................................................................................50
Index................................................................................................................................................52

Introduction 6
Introduction
This guide describes requirements for Solaris installation that are specific to ProLiant, how to apply
Solaris deployment mechanisms to ProLiant servers, and how to use specific ProLiant technologies for
Solaris installation.
Applicable servers and OS versions
Information in this guide applies to the following releases of Sun Solaris:
•Solaris 10 1/06
•Solaris 10 6/06
•Solaris 10 11/06
•Solaris 10 8/07
•Solaris 10 5/08
•Solaris 10 10/08
•Solaris 10 5/09
Information in this guide applies to the ProLiant server models listed in Table 1.
Table 1 Applicable HP ProLiant servers
BL20p G4 DL140 G2 DL385
BL25p DL145 DL385 G2
BL25p G2 DL145 G2 DL385 G5
BL260c G5 DL160 G5 DL385 G5p
BL2x220c G5 DL165 G5 DL580 G3
BL35p DL180 G5 DL580 G4
BL45p DL185 G5 DL580 G5
BL45p G2 DL360 G4p SCSI DL585
BL460c DL360 G5 DL585 G2
BL460c G6 DL360 G6 DL585 G5
BL465c DL365 DL785 G5
BL480c DL365 G5 ML370 G4
BL490c G6 DL370 G6 ML370 G5
BL680c G5
DL380 G4
ML370 G6
BL685c DL380 G5 ML570 G3
BL685c G5 DL380 G6 ML570 G4
DL385 G6 DL585 G6 BL465c G6

Introduction 7
Table 1 Applicable HP ProLiant servers
BL280c G6 DL320 G5p DL320 G6
Using this guide
For effective use of this guide, follow these guidelines:
•For interactive installations using the Solaris media, see “Basic installations.”
•For an introduction to the processes and components used in advanced Solaris deployments, see
“Architecture of an installation.” For deployment information specific to ProLiant, see “Deploying
ProLiant servers.”
•For common deployment setup procedures, see “Deployment tasks.”
•To integrate ProLiant servers into an existing Solaris deployment environment, see the following
sections:
○For readers new to Solaris on ProLiant servers, see “Deploying ProLiant servers.”
○For specific examples of deployment setup tasks required for ProLiant servers, see “Miniroot
preparation” and “JumpStart preparation.”
•To plan a new deployment environment, see the following sections:
○For those new to Solaris or Solaris on ProLiant servers, see “Architecture of an installation”
and “Deploying ProLiant servers.”
○For information about deployment strategies and guidance on selecting a strategy based on
various environmental requirements, see “Deployment planning.”
○For information on various deployment setup procedures, see “Deployment tasks.”
•For troubleshooting information, see “Troubleshooting.”
•For a list of other related documentation, see “Additional documentation.”
•For a list of terms, see “Glossary.”
NOTE: In this guide, citations of pages from the Solaris reference manual appear in italics next to a
number in parentheses, for example, sysidcfg(4). The number in parentheses represents the section
of the manual where the cited page is located.
This guide focuses on initial deployment of the Solaris operating environment. Topics beyond the
scope of this guide include automated post-installation configuration, application deployment, and
operating system upgrades. For more information about these topics, see the following
documentation:
•Solaris 10 11/06 Release and Installation Collection, at
http://docs.sun.com/app/docs/coll/1236.5
•Solaris 10 11/06 Installation Guide: Custom JumpStart and Advanced Installations, at
http://docs.sun.com/app/docs/doc/819-6397
•Solaris 10 11/06 Installation Guide: Solaris Flash Archives (Creation and Installation), at
http://docs.sun.com/app/docs/doc/819-6398

Basic installations 8
Basic installations
This chapter covers basic ProLiant deployments using the Solaris media. For more information on
other types of deployments, see “Using this guide.”
Prerequisites
To perform a basic installation of Sun Solaris on HP ProLiant servers, the following prerequisites must
be met:
•HP ProLiant Server—Use the ProLiant server support matrix for Solaris to determine which
releases of Solaris 10 are supported on your ProLiant.
•Sun Solaris 10 Distribution Media—Obtain a copy of the appropriate release of Solaris 10 from
Sun Microsystems. Both CD and DVD media are supported.
•Additional Drivers—Depending on your ProLiant model, one or more of the following additional
drivers that are not found on the Solaris media might be required. These drivers are available
from http://www.hp.com on the “Software and Drivers” page associated with each ProLiant
model.
○HP Smart Array controller driver—If you are installing to disks attached to a Smart Array
controller, the Smart Array driver cpqary3 is required during installation. For information
about additional requirements, including the use of a Driver Update diskette or CD, see the
HP Smart Array Controller Driver for Solaris 10 User Guide at
ftp://ftp.compaq.com/pub/softlib2/software1/pubsw-windows/p308167783/v40878/
HP_Smart_Array_Controller_Driver_User_Guide.pdf.The Smart Array driver is listed as “HP
Driver Update (DU) for Solaris (x86) 10” on the “Software and Drivers” page.
○Broadcom NetXtreme II driver—If you are using network interface card (NIC) models
NC370x, NC371x, NC373x, NC374x, or NC380x, the bnx driver is required. This driver
is applied post-installation.
•CD or DVD drive—A CD-ROM or DVD-ROM drive is required to load the Solaris software. A
Universal Serial Bus (USB) drive or iLO virtual media can be used if an internal drive is not
available.
•HP SmartStart CD—For advanced Smart Array configuration, HP SmartStart is required to set up
the arrays. For basic array setup, the Option ROM Configuration for Arrays (ORCA) utility can
be used instead.
•Firmware updates—HP recommends using the latest system ROM and firmware. System ROM,
Smart Array controller firmware, and iLO firmware updates should be applied when available.
•iLO client—If using iLO to perform the installation, a supported iLO client is required.
•iLO Advanced license—If using iLO to perform the installation, an iLO Advanced license is
required. This license is included with all blades.
The most efficient method to deploy Solaris on ProLiant server blades is through the network. If
network deployment is not available, a USB CD/DVD drive can be connected to the blade or iLO
virtual media can be used.
You can install Sun Solaris software using only virtual media, but it is not recommended. For best
results, verify that the iLO firmware is up-to-date. Connecting media images over HTTP using the iLO
secure shell interface can yield improved performance over the Java applet browser interface.

Basic installations 9
Installing Solaris interactively
The following procedure for installing Solaris on a ProLiant server might require adaptation to fit your
target environment or as recommended by the ProLiant server support matrix at
http://www.hp.com/wwsolutions/solaris, relevant HP advisories, or HP support personnel.
To install Solaris on a ProLiant server:
1. Ensure you have met all the requirements for installation and have all the necessary tools
available for installation, including a Smart Array Driver Update (DU) diskette or CD, if
necessary. For more information, see “Prerequisites.”
2. Apply system ROM and other firmware updates, as necessary.
3. If installing to disks attached to a Smart Array controller, configure the arrays as necessary. The
ORCA utility can be used to configure basic arrays. Use the array configuration utility available
on the HP SmartStart CD for a more complex array configuration.
IMPORTANT: If the ORCA utility is used to create a new array, the system continues booting after
exiting the utility. However, the system must be rebooted (for example, by pressing Ctrl+Alt+Delete)
after exiting the utility and before booting the installation media. If the system is not rebooted, the
Smart Array driver might not recognize the newly created logical volume..
4. Choose one of the following:
○Insert the first Solaris CD or DVD into the drive.
○If using virtual media, attach the CD, DVD, or ISO image using iLO, and then boot the
server.
5. If installing to disks attached to a Smart Array controller, follow the procedure described in the
HP Smart Array Controller Driver for Solaris 10 User Guide at ftp://ftp.compaq.com/pub/
softlib2/software1/pubsw-windows/p308167783/v40878/
HP_Smart_Array_Controller_Driver_User_Guide.pdf to load the driver. This step is time-sensitive
because a timeout might occur on the menu that appears shortly after boot. The root disk must be
SCSI target 0, LUN 0 (that is, cxt0d0).
6. Follow the onscreen instructions and the Solaris 10 11/06 Installation Guide: Basic Installations
at http://docs.sun.com/app/docs/doc/819-6394. The following known issues or workarounds
might apply:
○If a driver update such as the Smart Array driver was applied at the beginning of the
installation, and you are configuring the network using a static IP address, select non-
networked when prompted during the installation. Configure the network post-installation, as
described in step 7.
○If using a NIC that requires the bnx driver, select non-networked when prompted during the
installation. Install the driver and configure the network post-installation, as described in step
7.
7. If the bnx driver is required, then after installation is complete, install the bnx driver according to
the documentation that accompanies the driver distribution.
If you selected non-networked in step 6, after installation is complete, you can:
•Use sys-unconfig(1M) to clear the system identification and reboot the system. Upon restart,
Solaris prompts you for system identification, at which time you can select networked.
•Manually configure the network instead of running sys-unconfig.

Architecture of an installation 10
Architecture of an installation
This chapter describes the components, processes, and general architecture of a Solaris installation.
To successfully construct more complex Solaris deployments, review the following information.
General process flow
A Solaris deployment consists of the following phases:
•Boot—The first phase of deployment is booting a miniroot on the target system. The miniroot
contains the Solaris installation software. The system can be booted from a variety of sources,
including the Solaris media (CD or DVD), the network (PXE), a custom-built ISO image/CD, and
hard drive.
•Configuration—The second phase of deployment is configuring of the installation, which includes
system identification (hostname, network parameters, root password, and so on), target root
disk, and so on. This identification can be performed manually or automatically using JumpStart.
•Software installation—The final phase of deployment is the actual loading of the Solaris
operating environment software onto the system. The software packages can be loaded from the
Solaris media, over the network through a Network File System (NFS), or in the form of a flash
archive, which can be loaded from disk or other storage media or over the network.
•Optional configuration—After installation, make ProLiant-specific configuration updates to the
deployment.
Primary installation components
All Solaris installations follow the same flow as described previously, and are composed of the same
primary components. Deployments differ primarily in the way these components are delivered. For
example, in a CD-ROM-based interactive installation, the Administrator interactively supplies the
system configuration, and the packages that contain the Solaris operating environment are loaded
from the physical media. By contrast, for a fully automated installation, the system configuration can
be obtained from a JumpStart server, and the packages can be loaded through a NFS.
The following sections briefly describe the primary installation components, their roles, and delivery
mechanisms. A key aspect of this architecture is that the delivery mechanisms for each component are
generally independent of the others. This component independence provides a great amount of
flexibility and allows for the creation deployment scenarios to fit most environments. Other sections
discuss how various types of deployments can be constructed using these mechanisms.
GRUB
Grand Unified Bootloader (GRUB) is the default bootloader for Solaris starting with the Solaris 10
1/06 release. GRUB loads the Solaris multiboot program and the miniroot during installations or in
failsafe mode. GRUB can also be used to pass boot options and parameters to Solaris.
GRUB is loaded by the system BIOS or option ROMs (such as NICs and Fibre Channel adapters), and
can be loaded from a wide variety of devices, including CDs, DVDs, diskettes, iLO virtual media,
hard drives, USB storage, Storage Area Networks (SANs), and Preboot Execution Environment/Trivial
File Transfer Protocol (PXE/TFTP).

Architecture of an installation 11
Miniroot
A Solaris miniroot is a compressed disk image of a Unix File System (UFS) root file system that is
similar to a Linux initrd file. A miniroot is a small but functional Solaris system that contains a 32-bit
kernel, device drivers, the Solaris installation program, and various tools and utilities.
GRUB loads the miniroot into memory, along with the Solaris multiboot program. GRUB passes
control to the multiboot program, which loads and executes the Solaris kernel from the in-memory
miniroot, passing along various options and parameters from GRUB. The multiboot program and
miniroot can be loaded through most media that GRUB supports, such as a local media or storage
device (through BIOS calls) and PXE/TFTP.
A Solaris miniroot also assists with recovery from various errors or failures because it contains a
comprehensive set of tools and utilities. Other important components of the miniroot include:
•Drivers—The miniroot must contain all device drivers that are required for installation, or those
drivers must be loaded before installation begins. For ProLiant servers, these drivers usually
include the Smart Array driver and network drivers for network-based deployments. For more
information about installing additional drivers into the miniroot, see “Miniroot preparation.”
•Installer—The miniroot contains the Solaris installer, which orchestrates the actual installation of
Solaris onto the target disks. Boot parameters can be used to provide the installer with
deployment configuration information. For more information, see “GRUB preparation.”
Configuration information
The configuration information necessary to complete an installation includes target disk, partition, file
system layout, packages to be installed, network configuration, root password, and so on.
This information can be supplied interactively by the Administrator at the time of installation or
automatically through NFS using a JumpStart profile and the sysidcfg(4) file.
Packages
Packages on the Solaris media contain the software, documentation, and other data that comprise the
Solaris operating environment. Some or all of these packages are loaded onto the system by the
installer according to the selected configuration.
These packages can be loaded from various storage media (CD, DVD, and hard disk) or through the
network (NFS and iLO virtual media).
Packages and other system configuration information can also be delivered in a flash archive. Flash
archives can be loaded through FTP and HTTP, in addition to the methods previously listed.
Network deployment infrastructure
Solaris network-based deployments require several services to boot the target servers, deliver
configuration information, and provide the Solaris software. The following sections briefly introduce
the required services and the role of each.

Architecture of an installation 12
DHCP server
A Dynamic Host Configuration Protocol (DHCP) server is required to provide systems with network
configuration parameters for use during network deployments. If deployments are booted through
PXE, then the DHCP server can also provide boot information. If the HP ProLiant Essentials Rapid
Deployment Pack is used, a separate DHCP server for PXE boot is not required.
TFTP server
When PXE booting is used, a TFTP server must provide the booting systems with the files that are
necessary to properly boot. For Solaris this server includes pxegrub, the GRUB menu file
menu.lst, the Solaris multiboot program, and a miniroot. The DHCP/PXE server often hosts the
TFTP server. If the Rapid Deployment Pack is used, a separate TFTP server is not required.
JumpStart server
JumpStart consists of a set of files which the Solaris installation software uses to automatically
configure a deployment. The JumpStart files included profiles and sysidcfg(4) files. A JumpStart
server is a set of directories and files on a networked system that provides JumpStart profiles and
sysidcfg(4) files to clients during network deployments. The profile and sysidcfg files can provide
the Solaris installation software with all the information necessary to perform an automatic deployment
of Solaris. JumpStart files are typically served through an NFS share. For information about setting up
a JumpStart server, see “JumpStart preparation.”
Install server
An install server is a networked system that contains a copy of the Solaris installation media that it
makes available to other systems on the network through NFS. During a network deployment, a client
obtains the Solaris operating environment software from the install server instead of from the physical
media such as a CD or DVD. For information about setting up an install server, see “Install server
preparation.”
Deploying ProLiant servers
While you can use traditional Solaris deployment mechanisms to deploy ProLiant servers, some
requirements are ProLiant-specific. In addition, you can use some HP technologies to enhance Solaris
deployments. The following sections provide an overview of these requirements and technologies.
Information in the following sections is for use with network-based or other advanced deployment
methods. For basic interactive installation information, see “Basic installations.” For more information
about the tasks, see “Deployment tasks.”

Architecture of an installation 13
Additional drivers
Every new ProLiant generation is enhanced with newer device technologies, and ProLiant servers often
include some devices specific to HP. Frequently, drivers for one or more devices are not available on
the Solaris media. The following section describes the current set of drivers not available on the
Solaris media.
The following drivers are available for download from http://www.hp.com on the “Software and
Drivers” page associated with each ProLiant server model:
•Smart Array Driver—Most ProLiant servers are equipped with an HP Smart Array RAID controller.
This driver for this RAID controller is not currently included on the Solaris media. To install Solaris
to disks attached to the controller, the cpqary3 driver must be loadable at installation time. To
boot from the controller, the driver must be installed on the system during deployment. For more
information, see “Miniroot” and “JumpStart.”
NOTE: On the “Software and Drivers” load page, the cpqary3 driver is listed as “HP Driver
Update (DU) for Solaris (x86) 10.”
•Broadcom NetXtreme II driver—Current ProLiant generations use newer Broadcom NIC chipsets
for embedded NICs. The driver for these chipsets does not currently ship on the Solaris media.
To perform network deployments using these NICs, the bnx driver must be loadable at
installation time. To use the NICs after installation is complete, the driver must be installed on the
system. For more information, see “Miniroot” and “JumpStart.”
The following NIC models require the bnx driver:
○NC370x
○NC371x
○NC373x
○NC374x
○NC380x
Miniroot
All device drivers required during installation, such as the disk driver for targeted storage, must be
loaded into the miniroot. You can load the device drivers manually at run-time. Alternatively, you can
install the driver into the miniroot before booting the client for automated deployments or ease of
interactive installations.
When loading device drivers into the miniroot, follow these guidelines:
•For most ProLiant servers, the Smart Array driver, cpqary3, is installed into the miniroot so that
the Solaris software can be installed onto disks attached to a Smart Array controller.
•For network-based deployments, the miniroot must have a driver for the network interface to be
used. For current ProLiant generations, the Broadcom NetXtreme II driver, bnx, must be installed
into the miniroot.
•For network-based deployments that do not boot from the network, such as those that are
initiated by Rapid Deployment Pack, or those that boot from a custom CD ISO, the
HPQnetstrategy package must be installed into the miniroot. For more information about the
HPQnetstrategy package, see “Deployment resource kit.”
For more information about preparing a miniroot for use in deploying ProLiant server and blades, see
“Miniroot preparation.”

Architecture of an installation 14
JumpStart
JumpStart configuration for ProLiant servers is similar to configuration of other vendor platforms, with
the following requirements that are specific to ProLiant:
•Drivers—Most ProLiant servers require certain drivers that are not included with Solaris. In
addition to having these drivers in the miniroot, you must also install the drivers to the target
disks during deployment. This installation is accomplished using JumpStart.
JumpStart offers several mechanisms for installing additional packages not included with Solaris.
For more information, see Solaris 10 11/06 Installation Guide: Custom JumpStart and
Advanced Installations at http://docs.sun.com/app/docs/doc/819-6397.
•Rapid Deployment Pack—When using Rapid Deployment Pack, the boot disk is modified before
starting the operating system installation to facilitate the booting of the miniroot. After the
installation is booted, this modification is no longer necessary. When using Rapid Deployment
Pack, the JumpStart profile must be configured to remove this modification.
For more information about configuring JumpStart for ProLiant deployments, see “JumpStart
preparation.”
iLO virtual media
Virtual media support, part of the iLO Advanced feature set, provides administrators with a virtual
diskette drive, USB key drive, and a virtual CD/DVD drive that connect through the network to the
managed server, as if they were physically connected to each other.
Using a custom-built bootable ISO, a Solaris installation can be booted remotely with virtual media,
without the use of a PXE server. This ability to boot remotely can be useful in environments where PXE
cannot be used or is otherwise not available.
For more information about iLO, see http://www.hp.com/go/ilo. For more information about
creating a custom ISO image, see “Custom bootable ISO image creation.”
Rapid Deployment Pack
Rapid Deployment Pack is a server deployment solution that facilitates the installation, configuration,
and deployment of high volumes of servers through either a GUI-based or a web-based console, using
either scripting or imaging technology. Typically used to deploy Microsoft® Windows® and Linux,
Rapid Deployment Pack can also be used to initiate Solaris deployment.
Using Rapid Deployment Pack provides the following advantages:
•Rapid Deployment Pack consolidates deployment management of multiple operating systems to a
single tool.
•Rapid Deployment Pack can automatically configure the hardware, including Smart Array logical
volumes.
•Rapid Deployment Pack has a simple drag-and-drop interface that enables you to select from
multiple JumpStart profiles based on intended server usage.
For more information about Rapid Deployment Pack, see http://www.hp.com/go/rdp. For more
information about using Rapid Deployment Pack to deploy Solaris, see “Rapid Deployment Pack
server preparation.”

Architecture of an installation 15
Flash archives
Flash archives can be used in ProLiant deployment. The primary consideration when using flash
archives with ProLiant servers is to ensure that all the required drivers are included in the archive.
To ensure that all required drivers are included, before creating the archive on the master system,
install all the drivers required by all the intended clone systems, even if the master system does not
have any of those devices or otherwise does not need the drivers. When the flash archive is created,
all the installed drivers (whether or not they are in use) are included.
Deployment resource kit
The Solaris on ProLiant Deployment Resource Kit contains the following tools and examples for use in
deploying Solaris on ProLiant servers:
•HPQnetstrategy—The HPQnetstrategy package enhances the miniroot to allow automatic
network configuration when the miniroot is not booted from the network. It is required for
deployments initiated by Rapid Deployment Pack and custom ISO boot.
•Example Rapid Deployment Pack job—This example of an Rapid Deployment Pack job for
deploying Solaris can be imported into a deployment server. When imported, the job must be
customized to fit the intended environment. For more information, see “Rapid Deployment Pack
server preparation.”
•JumpStart examples—Several sample JumpStart configuration files are included.
This resource kit is available from http://www.hp.com on the “Software and Drivers” page
associated with each ProLiant server model.
For more information, see the README file in the kit.

Deployment planning 16
Deployment planning
Solaris installations proceed through three phases: boot, configuration, and software installation.
Each phase offers flexibility in implementation and can be customized for a variety of environments.
This chapter describes several common methods of implementing each phase and provides guidance
on selecting strategies that meet the requirements of most organizations.
This section describes the planning of deployment strategies where none exist. If ProLiant servers are
being integrated into an existing Solaris deployment environment, see “Deploying ProLiant servers,”
“Miniroot preparation,” and “JumpStart preparation.”
Selecting a deployment strategy
For purposes of this guide, a complete deployment strategy consists of a method of booting and
delivering the configuration and software packages. Use the following sections to select a deployment
strategy for the target environment.
Boot methods
PXE-based booting:
•Can be used in Solaris-only environments because Solaris can provide all the required services
•Can also be used to deploy other x86-based platforms that are not ProLiant platforms
•Can be used with existing x86 or Scalable Processor Architecture (SPARC) deployment
environments
•Manages deployment from the DHCP server
•Requires a PXE (DHCP/TFTP) server
Rapid Deployment Pack-initiated deployment:
•Can be used in mixed-operating system ProLiant environments
•Can be used to integrate Solaris deployments into existing ProLiant Windows and Linux
deployment environments
•Can be used to automate Smart Array configuration during deployment
•Can be used with an existing x86- or SPARC-hosted JumpStart server
•Manages deployment from the Rapid Deployment Pack deployment console
•Requires an Rapid Deployment Pack deployment server
Custom ISO-based booting:
•Can be used when neither PXE nor Rapid Deployment Pack are available nor desirable
•Can be used with existing SPARC deployment environments that do not require PXE boot services
•Can be used in Solaris-only environments
•Can be performed remotely using iLO virtual media
•Manages deployment from the physical or virtual system console
•Does not require a PXE or Rapid Deployment Pack server

Deployment planning 17
Configuration methods
For Solaris deployments, use of JumpStart profiles and sysidcfg(4) files is the recommended method of
supplying installation configuration for automated deployments.
Software delivery methods
•NFS—The traditional method of delivering the Solaris software packages to clients. The
packages are provided in the same form as they appear on the Solaris media. Additional
packages that are not a part of the Solaris distribution, such as the Smart Array driver, can also
be delivered through NFS. Setting up an NFS installation image offers flexibility in the variety of
installation configurations that a single image can support.
•Flash Archive—A portable, flexible image of a reference installation. A flash archive enables
you to clone a master system to any number of additional systems. The clones can be made to
mirror not only the Solaris operating environment and configuration of the master system, but
also any additional third-party applications that might be necessary. In addition, differential
archives can be employed to simplify clone upgrades.
Flash archives are useful for environments in which a large number of systems must be almost
identically deployed, including software that is not part of the Solaris distribution. For more
information, see Solaris 10 11/06: Solaris Flash Archives (Creation and Installation) at
http://docs.sun.com/app/docs/doc/819-6398.
Flash archives can be used with any of the boot methods previously described.
Implementing a PXE boot-based deployment
PXE boot-based deployments require the following:
•Install server
•JumpStart server
•Modified miniroot
•DHCP/PXE server
Use the following procedure outline as a basis for implementing PXE boot-based deployments in the
target environment:
1. Prepare the install server as described in “Install server preparation.”
2. Prepare the miniroot as described in “Miniroot preparation.”
3. Prepare the JumpStart server as described in “JumpStart preparation.”
4. Prepare the DHCP/PXE server as described in “DHCP/PXE preparation.”
5. To deploy Solaris using PXE boot:
a. Add the client to the install server as described in “DHCP/PXE preparation.”
b. PXE boot the client by booting the server and pressing F12 when prompted during POST.

Deployment planning 18
Implementing an Rapid Deployment Pack -initiated
deployment
Rapid Deployment Pack -initiated deployments require the following components:
•Install server
•JumpStart server
•Modified miniroot
•Rapid Deployment Pack deployment server
Use the following procedure outline as a basis for implementing Rapid Deployment Pack-initiated
deployments in the target environment:
1. Prepare the install server as described in “Install server preparation.”
2. Prepare the miniroot as described in “Miniroot preparation.”
3. Prepare the JumpStart server as described in “JumpStart preparation.”
4. Prepare the Rapid Deployment Pack deployment server as described in “Rapid Deployment Pack
server preparation.”
5. To deploy Solaris using Rapid Deployment Pack, drag-and-drop the Solaris deployment job onto
the target client.
Implementing a custom ISO boot-based deployment
Custom ISO boot-based deployments require the following components:
•Install server
•JumpStart server
•Modified miniroot
•Custom ISO image
Use the following procedure outline as a basis for implementing custom ISO boot based deployments
in the target environment:
1. Prepare the install server as described in “Install server preparation.”
2. Prepare the miniroot as described in “Miniroot preparation.”
3. Prepare the JumpStart server as described in “JumpStart preparation.”
4. Prepare the GRUB menu as described in “GRUB preparation.”
5. Prepare the custom ISO image as described in “Custom bootable ISO image creation.”
6. To deploy Solaris using a custom ISO, boot the client from the ISO through either physical media
or iLO virtual media.

Deployment tasks 19
Deployment tasks
This chapter describes common deployment tasks. For information about using one or more of these
tasks to construct a complete deployment environment, see “Deployment planning.”
In the examples and instructions that follow, file path references often end with .../subpath.
Replace the ellipsis (...) with the correct path for the current environment. For example, in the
following path:
.../sol-10-u3-ga-x86-v1.iso
replace the ellipsis (...) with a path to the directory that contains the ISO images for the Solaris 10
11/06 installation media.
Install server preparation
This section describes a procedure for preparing an install server, which provides the Solaris
installation media to installing clients as part of a network-based deployment.
This procedure is also described in Solaris 10 11/06 Installation Guide: Network-Based Installations
at http://docs.sun.com/app/docs/doc/819-6395, and Solaris man pages (for example,
setup_install_server(1M)).
Prerequisites for preparing an install server
To prepare a Solaris install server, the following prerequisites must be met:
•Solaris 10 media—This media is available from Sun. The install server can be prepared from the
ISO images; they do not need to be burned to physical media.
•System running Solaris—The install server must be a system running Solaris.
•Disk space—Enough disk space must be available on the install server to store the contents of the
installation media (approximately 3 GB to 5 GB).

Deployment tasks 20
Preparing the install server
In the following procedure, the installation media is assumed to be mounted at /mnt, and the
installation media root directory is /export/home/install. Substitute the installation media as
necessary to fit the target environment.
1. Ensure you have met all the requirements for installation and have all the necessary tools
available for installation. For more information, see “Prerequisites for preparing an install
server.”
2. Mount the DVD or the first CD on the install server.
○If using physical media (or iLO virtual media), insert or connect the media. Solaris
automatically mounts the disc. The autoselected mount point can be determined from the
output of, for example, df(1). If Solaris does not automatically mount the disc, it can be
manually mounted using mount(1M). To gather more information regarding your media
drive, you can enter the following:
# rmformat -l
○If using ISO images, mount the DVD or the first CD by entering the following:
# lofiadm -a .../sol-10-u3-ga-x86-v1.iso
/dev/lofi/1
# mount -F hsfs /dev/lofi/1 /mnt
3. Copy the contents of the DVD or the first CD to disk by entering the following:
# cd /mnt/Solaris_10/Tools
# ./setup_install_server /export/home/install
4. Unmount the DVD or the first CD.
○If using physical or iLO virtual media, unmount the media using eject(1) (if automounted) or
umount(1M) (if manually mounted).
○If using ISO images, unmount the DVD or the first CD by entering the following:
# umount /mnt
# lofiadm -d /dev/lofi/1
5. If using CD media, copy the remaining CDs. For each additional CD:
a. Mount the next CD or ISO image.
b. Copy the contents of the CD to disk by entering the following:
# cd /mnt/Solaris_10/Tools
# ./add_to_install_server /export/home/install
c. Unmount the CD.
6. If necessary, share the installation media root directory through NFS for client access.
a. Verify that the directory is shared:
# share | grep /export/home/install
b. If the installation media root directory is not listed, or if it is not shared with anon=0, then:
iAdd the following line to /etc/dfs/dfstab:
share -F nfs -o ro,anon=0 /export/home/install
ii Activate the NFS share:
# shareall