HP Dl180 - G6 E5504 2X2gb 4Lff Svr Deployment Manual

Sun solaris 10 deployment guide for hp proliant servers
Hide thumbs


Table of Contents

Sun Solaris 10

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


Table of Contents

  Related Manuals for HP Dl180 - G6 E5504 2X2gb 4Lff Svr

  Summary of Contents for HP Dl180 - G6 E5504 2X2gb 4Lff Svr

  • Page 1: Sun Solaris

    Sun Solaris 10 Deployment Guide for HP ProLiant Servers Part number 455522-003 Third edition 11/2009...
  • Page 2 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.
  • Page 3: Table Of Contents

    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 ..............................
  • Page 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 ............................
  • Page 5 Sun Microsystems documentation......................48 Glossary ............................50 Index ..............................52 Contents 5...
  • Page 6: Introduction

    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: •...
  • Page 7: Using This Guide

    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.”...
  • Page 8: Basic Installations

    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: •...
  • Page 9: Installing Solaris Interactively

    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: 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.
  • Page 10: Architecture Of An Installation

    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.
  • Page 11: Miniroot

    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.
  • Page 12: Dhcp Server

    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.
  • Page 13: Additional Drivers

    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.
  • Page 14: Jumpstart

    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.
  • Page 15: Flash Archives

    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.
  • Page 16: Deployment Planning

    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.
  • Page 17: Configuration Methods

    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.
  • Page 18: Implementing An Rapid Deployment Pack -Initiated Deployment

    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: Prepare the install server as described in “Install server preparation.”...
  • Page 19: Deployment Tasks

    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.
  • Page 20: Preparing The Install Server

    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. Ensure you have met all the requirements for installation and have all the necessary tools available for installation.
  • Page 21: Miniroot Preparation

    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: •...
  • Page 22 NOTE: For Solaris 5/09, a known issue prevents drivers from being installed in the miniroot. If disks attached to a HP Smart Array Controller are not available during installation, see the procedure outlined in the Troubleshooting section “Hard Drives Not Seen After CPQary3 Added to Miniroot”...
  • Page 23: Jumpstart Preparation

    JumpStart preparation This section describes some prerequisites for preparing JumpStart that are specific to ProLiant. For more information about Solaris JumpStart, see Solaris 10 11/06 Installation Guide: Custom JumpStart and Advanced Installations at http://docs.sun.com/app/docs/doc/819-6397. This section also includes descriptions of a JumpStart configuration, requirements specific to ProLiant, and a complete configuration example.
  • Page 24: Example: Jumpstart Preparation

    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. This deletion can be accomplished using the fdisk profile keyword to delete all type 0x83 partitions.
  • Page 25 ○ Contents of the sysidcfg file: system_locale=en_US.UTF-8 name_service=none network_interface=if {dhcp protocol_ipv6=no} security_policy=none terminal=ibm-pc timezone=US/Central timeserver=localhost nfs4_domain=dynamic root_password=9E417cFYuXjIY service_profile=limited_net where if is the network interface to configure, such as bnx0 or bge0. You can also use the keyword value ‘primary’. In this example, the password for user root is root. Prepare additional packages using pkgtrans(1): # mkdir /jumpstart/pkg # pkgtrans .../CPQary3-x.y-solaris10-i386/CPQary3.pkg \...
  • Page 26: Dhcp/Pxe Preparation

    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 network clients. For more information, see System Administration Guide: IP Services at http://docs.sun.com/app/docs/doc/816-4554 add_install_client(1M).
  • Page 27: Preparing The Dhcp/Pxe Server

    Preparing the DHCP/PXE server Configure the DHCP server as follows: Start the DHCP Manager by entering the following command: # /usr/sadm/admin/bin/dhcpmgr NOTE: If the DHCP Manager crashes during setup, the manager might be missing network device configuration. You can configure the network devices using sys-unconfig. If starting with no configuration, dhcpmgr prompts you for the type of configuration, either DHCP server or BOOTP relay.
  • Page 28: Rapid Deployment Pack Server Preparation

    − ethmac is the Ethernet MAC address of the client, in the form aa:bb:cc:dd:ee − installpath is the NFS path to the Installation Server, such as: − jsnfspath is the NFS path to the JumpStart configuration directory, such as: −...
  • Page 29: Overview Of Rapid Deployment Pack Server Preparation

    Overview of Rapid Deployment Pack server preparation Deployments of Solaris based on Rapid Deployment Pack are modeled after Rapid Deployment Pack deployments of Linux. For Linux deployments, the target server PXE boots from the Rapid Deployment Pack deployment server to the Linux preinstall environment. This environment is used for pre-installation configuration of the hardware, such as updating BIOS settings and creating Smart Array logical volumes.
  • Page 30: Grub Preparation

    Import the example job included in the resource kit (examples/rdp/deploy-sol.bin) to the deployment server console. Modify the script in the Create Boot Environment task in the newly imported example job to match the target environment. GRUB preparation This section describes GRUB menu configuration file preparation for use in deploying Solaris. For more information about GRUB, see GRUB and the Solaris 10 1/06: The New Bootloader for x86 Platforms and GNU GRUB Manual 0.97 at http://www.gnu.org/software/grub/manual/html_node/index.html.
  • Page 31: Booting Solaris From Grub

    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 boot media, either CD or network (TFTP).
  • Page 32: Examples: Booting Solaris From Grub

    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.
  • Page 33: Custom Bootable Iso Image Creation

    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 ISO image To create and use a custom bootable ISO image, the following prerequisites must be met: •...
  • Page 34: Optional Configuration Tasks

    Optional configuration tasks This chapter details optional configuration tasks specific to ProLiant servers. Enabling iLO virtual serial port By default, Solaris does not recognize the iLO virtual serial port. If enabled, this virtual serial port can be used as a serial console (by appending "-B console=ttya" to the GRUB kernel line). The procedure to enable the virtual serial port can potentially cause configuration issues with Solaris.
  • Page 35 # metainit d0 -m d10 # metaroot d0 Use the metaroot d0 command only on the root slice. Mirror the swap slice. # metainit -f d11 1 1 c0t0d0s1 # metainit -f d21 1 1 c0t1d0s1 # metainit d1 -m d11 Mirror the var slice.
  • Page 36: Unmirroring Disks With Disksuite

    /dev/md/dsk/d6 /dev/md/rdsk/d6 /opt ufs 2 yes nosuid,logging swap - /tmp tmpfs - yes - Reboot the system. # lockfs -fa # init 6 Attach the second submirror to the mirror. This causes the data from the boot disk to be synchronized with the mirrored drive.
  • Page 37 Detach the mirror: metadetach Optional configuration tasks 37...
  • Page 38: Troubleshooting

    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. If none of the known issues apply, see “Common ” for issue diagnosis.
  • Page 39: Raid Mode Not Supported

    information, please refer to advisory http://h20000.www2.hp.com/bizsupport/TechSupport/Document.jsp?lang=en&cc=us&taskId=1 10&prodSeriesId=3454575&prodTypeId=15351&prodSeriesId=3454575&objectID=c01479945 • Workaround—Edit /platform/i86pc/kernel/drv/pcie_pci.conf and add the entry "pci-hotplug-type=0", then reboot the server. • For Solaris 10 5/08, the issue is fixed with patch 137122-04. • This issue is fixed in Solaris 10 10/08. RAID mode not supported Solaris 10 operating system will not deploy on an HP ProLiant BL260c G5 or BL280c G6 blade server when the SATA controller is configured in RAID mode.
  • Page 40: Ilo Boot Hang

    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. •...
  • Page 41: Bcme Fails To Attach

    # svcadm disable sma # perl -pi -e 's/\/usr\/sfw\/sbin\/snmpd/\/usr\/sfw\/sbin\/i86\/snmpd/' > /lib/svc/method/svc-sma # svcadm enable sma bcme fails to attach Broadcom gigabit Ethernet NIC fails to attach. • OS releases affected—Solaris 10 8/07, 5/08, 10/08 • Servers affected—HP ProLiant BL685c, BL685c G5, BL680c, BL480c, BL260c G5 •...
  • Page 42: System Panics And Reboots During Installation

    System panics and reboots during installation • OS releases affected—Solaris 10 10/08, 5/09 • Servers affected—HP ProLiant DL485 G1, DL585 G1 • Description—System panics and reboots during the OS installation of Solaris 10 10/08 and Solaris 10 5/09 on HP ProLiant DL385 G1 and DL585 G1. •...
  • Page 43: Basic Troubleshooting Techniques

    • Workaround—Remove file /tmp/AdDrEm.lck file from the miniroot before adding the CPQary3 driver package, or any other driver package. Unpack the PXE miniroot to some temporary location such as /var/tmp/mr # /boot/solaris/bin/root_archive unpack <SUN Solaris 10 5/09_PXE_image_path>/boot/x86.miniroot /var/tmp/mr Remove /tmp/AdDrEm.lck from the PXE miniroot # rm /var/tmp/mr/tmp/AdDrEm.lck Add the CPQary3 driver package # pkgadd -d CPQary3.pkg -R /var/tmp/mr...
  • Page 44: Grub Command Line

    For example, ifconfig(1M) can be used to verify network parameters and ping(1M) can be used to test network connectivity to an install server. Utilities such as df(1M) or mount(1M) can be used to determine which NFS filesystems have been mounted. If an NFS share is unexpectedly not mounted, an attempt to manually mount it can be used to determine why the mount is failing.
  • Page 45: Grub Cannot Boot Solaris

    If booting from PXE, verify add_install_client(1M) and dhtadm(1M) usage. The Ethernet MAC address given to add_install_client is significant. For more information, see “DHCP/PXE preparation.” If booting from a custom ISO, verify that the configuration file is in the proper location on the media (such as /boot/grub/menu.lst).
  • Page 46: Installation Terminates Prematurely

    • 252—The sol.sh script was unable to copy multiboot and/or x86.miniroot to the temporary disk partition. • 253—The sol.sh script was unable to mount the temporary disk partition. • 254—The $dist parameter was not specified in the Create Boot Environment task script. Verify the setting in the task script.
  • Page 47: Installation Succeeds But Server Fails To Boot

    Installation succeeds but server fails to boot If the system is not booting to GRUB, verify the standard boot order and boot controller order in RBSU. If booting from Smart Array, the Solaris root disk must be SCSI target 0, LUN 0 (that is, cxt0d0).
  • Page 48: Additional Documentation

    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. The following sections list this documentation.
  • Page 49 • GRUB and the Solaris Operating System on x86 Platforms – A Guide to Creating a Customized Boot DVD, at http://www.sun.com/blueprints/0806/819-7546.pdf Additional documentation 49...
  • Page 50 Glossary Deployment server The component of an Rapid Deployment Pack environment that provides the foundation for deploying and managing servers using Rapid Deployment Pack. Flash archive From flar(1M), A flash archive is an easily transportable version of a reference configuration of the Solaris operating environment, plus other optional software.
  • Page 51 Sysidcfg(4) A file that provides the system identification information such as root password, networking parameters, time zone, and so on, during an automated installation. For more information, see sysidcfg(4). Trivial File Transfer A protocol used during a PXE-based boot to transfer the network boot program from the Protocol (TFTP) server to the boot system.
  • Page 52 Index miniroot, 11 overview, 10 about this guide, 6 packages, 11 additional drivers, 13 configuration information, 11 AMD memory scrubber, 40 configuration methods, 17 applicable OS versions, 6 custom bootable ISO image creation applicable servers, 6 prerequisites, 33 procedure, 33 basic installation interactive, 9 deploying ProLiant servers, 12...
  • Page 53 DiskSuite, 34 drivers JumpStart, 14 additional ProLiant, 13 JumpStart preparation example, 24 overview, 23 Embedded Ethernet not configured, 42 prerequisites, 23 Enabling iLO virtual serial port JumpStart preparation prerequisites Optional configuration tasks, 34 additional required packages, 23 Rapid Deployment Pack, 24 flash JumpStart reverts to interactive configuration, 46 archives, 15...
  • Page 54 general process flow, 10 network deployment infrastructure, 11 Rapid Deployment Pack (RDP), 14 overview, 10 Rapid Deployment Pack job fails, 45 Solaris media packages, 11 Rapid Deployment Pack preparation system becomes unresponsive using remote console, 45 overview, 29 system does not boot to GRUB, 44 prerequisites, 29 procedure, 29 RDP, 14...

Table of Contents