Resumen del contenido incluido en la página 1
Sun Solaris 10
Deployment Guide for HP ProLiant Servers
Part number 455522-001
First edition August 2007
Resumen del contenido incluido en la página 2
Legal notices © Copyright 2007 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 prod
Resumen del contenido incluido en la página 3
Contents Introduction ...........................................................................................................................................5 Applicable servers and OS versions ........................................................................................................... 5 Using this guide....................................................................................................................................... 6 Basic installations...........
Resumen del contenido incluido en la página 4
DHCP/PXE preparation .......................................................................................................................... 25 Prerequisites for DHCP/PXE preparation .............................................................................................. 25 Preparing the DHCP/PXE server.......................................................................................................... 26 RDP server preparation................................................
Resumen del contenido incluido en la página 5
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.
Resumen del contenido incluido en la página 6
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 S
Resumen del contenido incluido en la página 7
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 cop
Resumen del contenido incluido en la página 8
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
Resumen del contenido incluido en la página 9
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 sourc
Resumen del contenido incluido en la página 10
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-memo
Resumen del contenido incluido en la página 11
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 boo
Resumen del contenido incluido en la página 12
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: •
Resumen del contenido incluido en la página 13
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 installi
Resumen del contenido incluido en la página 14
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 f
Resumen del contenido incluido en la página 15
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 ar
Resumen del contenido incluido en la página 16
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 b
Resumen del contenido incluido en la página 17
Implementing an RDP-initiated deployment RDP-initiated deployments require the following components: • Install server • JumpStart server • Modified miniroot • RDP deployment server Use the following procedure outline as a basis for implementing RDP-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
Resumen del contenido incluido en la página 18
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 th
Resumen del contenido incluido en la página 19
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 o
Resumen del contenido incluido en la página 20
Miniroot preparation This section describes the procedure for customizing a miniroot and provides an example set of modifications that are typically required for ProLiant servers. Prerequisites for preparing a miniroot To prepare a miniroot for ProLiant server deployments, the following prerequisites must be met: • System must be running Solaris 10 1/06 or higher—An x86-based system running Solaris is required for use as the staging system. • Disk space on the staging system—Disk spac
