HP 10 - Manual

Basic installations 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 prerequisit...

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

Architecture of an installation 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 deploym...

Architecture of an installation 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 p...

Architecture of an installation 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. I...

Architecture of an installation 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 de...

Architecture of an installation 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. ...

Architecture of an installation 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, bef...

Deployment planning 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 impleme...

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

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

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

Deployment tasks 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 me...

Deployment tasks 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 fo...

Deployment tasks 21 Example: miniroot preparation The following procedure is an example of a miniroot preparation for ProLiant servers. 1. Unpack the stock Solaris miniroot: # /boot/solaris/bin/root_archive unpack .../boot/x86.miniroot \ > /var/tmp/mr The miniroot is expanded under /var/tmp/mr . ...

Deployment tasks 22 JumpStart preparation Solaris JumpStart is a complex topic that is beyond the scope of this guide. However, this section describes some prerequisites for installing JumpStart that are specific to ProLiant. For more information about Solaris JumpStart, see Solaris 10 11/06 Install...

Deployment tasks 23 Rapid Deployment Pack When deploying Solaris using Rapid Deployment Pack, a small, non-Solaris partition is created on the boot volume to facilitate booting the installation. By default, Solaris avoids disks with existing partitions, so this temporary partition must be deleted. T...

Deployment tasks 25 DHCP/PXE preparation DHCP administration is a complex subject, much of which is beyond the scope of this guide. However, PXE booting is an effective means of deploying Solaris. This section provides instructions for the quick setup of a Solaris DHCP server for use in PXE-booting ...

Deployment tasks 26 Preparing the DHCP/PXE server 1. Configure the DHCP server as follows: a. Start the DHCP Manager: # /usr/sadm/admin/bin/dhcpmgr b. If starting with no configuration, dhcpmgr prompts you for the type of configuration, either DHCP server or BOOTP relay. Select DHCP server to start ...

Deployment tasks 27 2. After adding the installation client, add_install_client prints the modifications that must be made to the DHCP server configuration to PXE boot the client. For the Solaris 10 1/06 release and later, only the BootFile and BootSrvA options are required. Use dhtadm(1M) to config...

Deployment tasks 28 Preparing the RDP deployment server To configure the RDP deployment server: 1. Copy the example script examples/rdp/sol.sh from the resource kit to ...\lib\bin32\linux\ on the deployment server. This script is called by the Create Boot Environment task script in the Solaris RDP j...

Deployment tasks 29 Booting Solaris from GRUB This section provides an overview of and describes the options for booting Solaris from GRUB. Synopsis kernel pathtomultiboot kerneltoboot [ options ] module pathtominiroot • pathtomultiboot —Path to the multiboot program. This path is relative to the bo...

Deployment tasks 30 Examples: booting Solaris from GRUB NOTE: In the following examples, the kernel line is shown broken into multiple lines. In practice, the parameters must all be on the same line, and there must not be any spaces in the comma-separated -B parameter list. • For a JumpStart install...

Deployment tasks 31 Custom bootable ISO image creation This section describes a procedure for creating a custom bootable ISO image with a modified miniroot for use in booting a ProLiant server to a network-based, possibly automated Solaris installation. Prerequisites for creating a custom bootable I...

Troubleshooting 32 Troubleshooting This chapter describes common problems and probable causes, known issues, and provides general troubleshooting advice. To begin troubleshooting deployment problems, review the list of Known Issues below first to see if any issues match the environment and symptoms....

Troubleshooting 33 iLO boot hang Solaris becomes unresponsive intermittently, but frequently at boot, just after the Solaris copyright banner appears. If the console is viewed from iLO, the virtual console goes blank. A power cycle or reset is required to restore the system. • OS releases affected—S...

Troubleshooting 34 • Workaround—Manually stop the 64-bit master agent and start the 32-bit version as follows: # /etc/init.d/init.sma stop # /usr/sfw/sbin/i86/snmpd Then, restart the agents. The agents’ status might have to be cleared with SMF if they have entered the maintenance state: # svcadm dis...

Troubleshooting 35 To enable the Solaris debugger, add -k to the GRUB kernel line. When the debugger has assumed control following the occurrence of a significant error, the ::msgbuf command displays the kernel message buffer, the end of which contains the panic string, if any. The ::quit command re...

Troubleshooting 36 System becomes unresponsive using remote console Check for applicability of known issue iLO Boot Hang. For more information, see “iLO boot hang.” If using a serial console (physical or virtual) and GRUB is not seen, verify that a splashimage is not specified in menu.lst . If using...

Troubleshooting 37 JumpStart reverts to interactive configuration If a JumpStart profile and a sysidcfg(4) file are provided, but the Solaris installation begins prompting you for information, then it either cannot find one of the files, one of the files has a syntax error, or the configuration is i...

Additional documentation 38 Additional documentation This section provides technical support information. Where to go for additional help While this guide provides guidance about Solaris installation on ProLiant servers, it is not a replacement for the appropriate documentation from HP and others. T...

Glossary 39 Glossary Deployment server The component of an RDP environment that provides the foundation for deploying and managing servers using Rapid Deployment Pack (RDP). Flash archive From flar(1M) , A flash archive is an easily transportable version of a reference configuration of the Solaris o...

Index 41 Index A about this guide, 5 additional drivers, 12 AMD memory scrubber, 33 applicable OS versions, 5 applicable servers, 5 B basic installation interactive, 8 overview, 7 prerequisites, 7 basic troubleshooting techniques GRUB command line, 34 kernel debugger, 34 network verification, 34 she...