HP Sun Solaris 10 User Manual

Sun Solaris 10

Deployment Guide for HP ProLiant Servers

Part number 455522-001 First edition August 2007

Legal notices

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. 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.

Introduction ...........................................................................................................................................5

Applicable servers and OS versions ........................................................................................................... 5

Using this guide....................................................................................................................................... 6

Basic installations...................................................................................................................................7

Prerequisites............................................................................................................................................ 7

Installing Solaris interactively..................................................................................................................... 8

Architecture of an installation................................................................................................................... 9

General process flow ............................................................................................................................... 9

Primary installation components ................................................................................................................. 9

GRUB................................................................................................................................................ 9

Miniroot........................................................................................................................................... 10

Configuration information .................................................................................................................. 10

Packages ......................................................................................................................................... 10

Network deployment infrastructure ........................................................................................................... 10

DHCP server..................................................................................................................................... 11

TFTP server....................................................................................................................................... 11

JumpStart server................................................................................................................................ 11

Install server ..................................................................................................................................... 11

Deploying ProLiant servers ...................................................................................................................... 11

Additional drivers ............................................................................................................................. 12

Miniroot........................................................................................................................................... 12

JumpStart......................................................................................................................................... 13

iLO virtual media .............................................................................................................................. 13

Rapid Deployment Pack ..................................................................................................................... 13

Flash archives................................................................................................................................... 14

Deployment resource kit..................................................................................................................... 14

Deployment planning............................................................................................................................ 15

Selecting a deployment strategy............................................................................................................... 15

Boot methods ................................................................................................................................... 15

Configuration methods....................................................................................................................... 16

Software delivery methods ................................................................................................................. 16

Implementing a PXE boot-based deployment.............................................................................................. 16

Implementing an RDP-initiated deployment ................................................................................................ 17

Implementing a custom ISO boot-based deployment ................................................................................... 17

Deployment tasks .................................................................................................................................18

Install server preparation......................................................................................................................... 18

Prerequisites for preparing an install server........................................................................................... 18

Preparing the install server ................................................................................................................. 19

Miniroot preparation .............................................................................................................................. 20

Prerequisites for preparing a miniroot .................................................................................................. 20

Preparing a miniroot ......................................................................................................................... 20

Example: miniroot preparation............................................................................................................ 21

JumpStart preparation ............................................................................................................................ 22

Overview of JumpStart preparation ..................................................................................................... 22

Prerequisites for JumpStart preparation ................................................................................................ 22

Example: JumpStart preparation.......................................................................................................... 23

Contents 3

DHCP/PXE preparation .......................................................................................................................... 25

Prerequisites for DHCP/PXE preparation .............................................................................................. 25

Preparing the DHCP/PXE server.......................................................................................................... 26

RDP server preparation........................................................................................................................... 27

Overview of RDP server preparation.................................................................................................... 27

Prerequisites for RDP server preparation............................................................................................... 27

Preparing the RDP deployment server................................................................................................... 28

GRUB preparation ................................................................................................................................. 28

Overview of GRUB preparation .......................................................................................................... 28

Booting Solaris from GRUB................................................................................................................. 29

Examples: booting Solaris from GRUB ................................................................................................. 30

Custom bootable ISO image creation ....................................................................................................... 31

Prerequisites for creating a custom bootable ISO image......................................................................... 31

Creating a custom bootable ISO image ............................................................................................... 31

Troubleshooting ...................................................................................................................................32

Known issues......................................................................................................................................... 32

Disabled PCI devices......................................................................................................................... 32

Network configuration fails during interactive installation ....................................................................... 32

iLO boot hang .................................................................................................................................. 33

AMD memory scrubber...................................................................................................................... 33

SNMP master agent .......................................................................................................................... 33

Basic troubleshooting techniques.............................................................................................................. 34

Shell prompt..................................................................................................................................... 34

Network verification.......................................................................................................................... 34

GRUB command line ......................................................................................................................... 34

Kernel debugger............................................................................................................................... 34

Common problems................................................................................................................................. 35

System does not boot to GRUB ........................................................................................................... 35

GRUB does not display a menu........................................................................................................... 35

GRUB cannot boot Solaris.................................................................................................................. 35

System becomes unresponsive using remote console.............................................................................. 36

Rapid Deployment Pack job fails......................................................................................................... 36

Installation terminates prematurely....................................................................................................... 36

JumpStart reverts to interactive configuration......................................................................................... 37

Installation succeeds but server fails to boot.......................................................................................... 37

Installation succeeds but no network availability after reboot ..................................................................37

Additional documentation .....................................................................................................................38

Where to go for additional help .............................................................................................................. 38

HP documentation............................................................................................................................. 38

Free Software Foundation documentation............................................................................................. 38

Intel documentation ........................................................................................................................... 38

Sun Microsystems documentation ........................................................................................................ 38

Glossary .............................................................................................................................................39

Index ..................................................................................................................................................41

Contents 4

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

Information in this guide applies to the ProLiant server models listed in Table 1.

Table 1

BL20p G4 BL480c DL385 G2

BL25p BL685c DL580 G4

BL25p G2 DL360 G4 DL585

BL35p DL360 G5 DL585 G2

BL45p DL365 ML370 G4

BL45p G2 DL380 G4 ML370 G5

BL460c DL380 G5 ML570 G4

BL465c DL385 —

Applicable HP ProLiant servers

Introduction 5

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

Introduction 6

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

○ 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

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.

on the “Software and Drivers” page associated with each ProLiant model.

. The Smart Array driver is listed as “HP

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 7

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

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. The array configuration utility available on the HP SmartStart CD should be used 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.

, relevant HP advisories, or HP support personnel.

4. Insert the first Solaris CD or DVD into the drive. Alternatively, 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 can occur on the menu that appears shortly after boot. If installing to disks attached to a Smart Array controller, the root disk must be SCSI target 0, LUN 0 (that is, cxt0d0).

6. To complete the installation, 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 8.

○ 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 steps 7 and 8.

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.

8. 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. Alternatively, you can manually configure the network instead of running sys-unconfig.

Basic installations 8

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.

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 9

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

• Installer—The miniroot contains the Solaris installer, which orchestrates the actual installation of

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.”

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 listed above.

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 10

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 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

A JumpStart server is a networked system that provides JumpStart profiles and sysidcfg(4) files to clients during network deployments. A profile and sysidcfg file provide all the system configuration information necessary to complete an installation, reducing the amount of interaction required.

Profiles and sysidcfg files are typically exchanged through NFS. 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 11

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 page associated with each ProLiant server model:

on the “Software and Drivers”

• 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, should be installed into the miniroot so

• For network-based deployments, the miniroot must have a driver for the network interface to be used.

• For network-based deployments that do not boot from the network, such as those that are initiated by

For more information about preparing a miniroot for use in deploying ProLiant server and blades, see “Miniroot preparation.”

that the Solaris software can be installed onto disks attached to a Smart Array controller.

For current ProLiant generations, the Broadcom NetXtreme II driver, bnx, must be installed into the miniroot.

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.”

Architecture of an installation 12

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 (RDP)—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 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 information about using Rapid Deployment Pack to deploy Solaris, see “RDP server preparation.”

. For more information about creating a

. For more

Architecture of an installation 13

+ 30 hidden pages