HP ProLiant Essentials Rapid Deployment Pack User Guide Part number 315378-402 Eleventh edition August 2007 Product version: 3.
Legal notices © Copyright 2001, 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.
Contents 1 2 3 4 5 Configuring the Rapid Deployment Pack.......................................................................................... 5 Configuring BladeSystem enclosures........................................................................................................... 5 Configuring image installs......................................................................................................................... 6 Configuring imaging jobs ......................................
Index ..................................................................................................................................................
1 Configuring the Rapid Deployment Pack The following sections detail the configuration steps necessary to deploy an operating system to a server. Configuring BladeSystem enclosures The Physical Devices view in the Deployment Server Console displays the physical relationship between the racks, enclosures, and server blades using the rack name and enclosure name for each HP BladeSystem server. The display name for a new server blade is a combination of the rack name, enclosure name, and bay number.
Configuring image installs IMPORTANT: By default, the Create Disk Image and Distribute Disk Image tasks operate on the “first” disk. The disks are enumerated using a proprietary algorithm. The “first” disk might not be the system boot disk. The Altiris showdisk utility can be used to generate human-readable disk enumeration output. This utility is called in the provided Read Hardware Configuration job.
Configuring scripted installs Configuring scripted install jobs The scripted install jobs use a small image to partition and format the disk. When deploying to a server with multiple disks, either DAS or SAN, you might have to specify the system boot disk in the job for the NTFS.img or GRUB.img images. For more information, see the “Configuring image installs” section. To specify a particular disk: 1. In the Deployment Server Console, copy, rename, and edit the job. 2.
For VMware ESX 2.5.3: 1. On the Deployment Server, copy, rename, and edit the job. 2. Modify the Run Script – Create Boot Environment task in the new job by changing the default.cfg file reference in the # replacetokens statement to sanattach.cfg. 3. Execute the new job. After the operating system installation is complete, using the MUI: 4. Create the core dump partition. a. Click Reconfigure when the following warning message appears: No core dump partition is configured or none is accessible b.
2 Using the Rapid Deployment Pack This section provides information about the following topics: • • • • • • Connecting server blades Creating a reference server and image Deploying a captured image to other similar servers Reconfiguring the new servers Maintaining server blades with rip-and-replace Performing a Boot from SAN installation Connecting server blades 1. Connect the enclosure to the network that contains your Deployment Server, and power up the enclosure. 2.
6. Select View>Show Physical Devices. NOTE: The Physical Devices view is an additional view available only for BladeSystem servers in the Computers pane. A job can be executed on a server listed in this view. Table 1 lists the server icons displayed in the Physical Devices view of the Deployment Server Console.
7. From the Computers pane, right-click on a server blade. 8. Select Power Control>RILOE/iLO – Interface. This action accesses the iLO, iLO 2, or RILOE interface to enable remote viewing of the deployment.
Creating a reference server and image The initial server blade must be deployed using a scripted installation job. Subsequent server blades can be deployed by capturing and deploying the image of the initial server blade. 1. In the Jobs pane, select a Windows-scripted installation job in the Server Deployment folder. Drag the job onto the initial server blade in the Computers pane. 2. Select Run this job immediately, and click OK. NOTE: The Details pane displays the job currently running.
3. In the Jobs pane, find the Read ProLiant ML/DL/BL System and Array Configuration and Windows Image {WinPE} job in the Server Replication folder. Drag the job onto the initial server blade in the Computers pane. NOTE: The Server Replication jobs provided with the Rapid Deployment Pack create and deploy images using an image name based on the computer model names.
Deploying a captured image to other similar servers 1. In the Computers pane, select the rest of the server blades. Drag them onto the Write ProLiant ML/DL/BL System and Array Configuration and Windows Image {WinPE} job in the Server Replication folder in the Jobs pane. If you are deploying the image to all server blades in an enclosure, you can select the enclosure from the Physical Devices view. 2. Select Run this job immediately, and click OK.
Reconfiguring the new servers 1. In the Computers pane, select all the server blades, and then right-click the selection, and select Configure. 2. Click Microsoft Networking, and then enter a new workgroup or domain name (if applicable), and click Define Range. 3. Enter the fixed portion of the new server names, and click OK.
4. Click TCP/IP, enter the IP information for the first server blade, and click OK. Subsequent server blades are assigned the same information, except that the IP address increases incrementally for each server blade. 5. Select Run this job immediately, and click OK.
Maintaining server blades with rip-and-replace When a failed server blade is replaced, the Deployment Server can automatically replay the job history of the failed server blade on the new server blade. This feature is available only for BladeSystem servers. NOTE: The new server blade requires a new license. The existing license cannot be transferred to the new server blade. To enable rip-and-replace, perform the following steps for each server blade: 1.
Performing a Boot from SAN installation A Boot from SAN (BFS) installation requires several manual steps before starting the operation system installation. Be sure the following prerequisites are met: 1. • The target server is cabled in a single-path configuration (with only one channel active). You can cable both paths after the operating system installed and the multipathing software is installed. • Only one LUN is presented to the target server.
BootDeviceWWID=395442c135713a42 BootDeviceLUN=01 b. Run the appropriate platform Write HBA Configuration job from the Server Deployment Toolbox\1—Hardware Configuration\HBA job folder on the target server. c. 3. For ProLiant servers, run the Deploy ProLiant BL System Configuration (Boot From SAN) {LinuxPE} or {WinPE} job from the Server Deployment Toolbox\1—Hardware Configuration\System job folder on the target server.
3 Understanding the Deployment Server The Rapid Deployment Pack populates the Deployment Server Console with jobs and the Deployment Server directory with tools, scripts, configuration files, software drivers, and documentation files. This section explains these provided jobs and files, and the directory structure. Jobs The Rapid Deployment Pack adds four root folders into the Jobs pane.
Job default settings Unless otherwise indicated in the job name, the job uses the following default settings. For details about how to customize these default settings, see the “Customizing the ProLiant and Integrity Integration Modules” section in this guide.
The provided VMware scripted install jobs use the default configuration parameters listed in Table 5 VMware default settings. Table 5 VMware default settings Component Default setting VMware root password The root password is password. This password is stored as clear text in the kickstart file. HP recommends that you change the root password to your own password and in encrypted form within the kickstart file located in the .
Read/Write job filenames The provided Read (Capture)/Write jobs use the default input/output filenames listed in Table 7 Default Read (Capture)/Write jobs. Table 7 Default Read (Capture)/Write jobs Read(Capture)/Write Job Pair Filename Server Deployment Toolbox > 1 – Hardware Configuration ProLiant ML/DL/BL System Configuration .\lib\hwconfig\system\pl-capture.xml ProLiant ML/DL/BL Array Configuration .\lib\hwconfig\array\pl-capture.ini ProLiant ML/DL/BL HBA Configuration [server specific] .
How a job is run on a target This section provides a walkthrough of how a job is executed on a target server. The table within each step lists the state of the target server and the job action during that execution step. The term “automation environment” is used throughout this section. It is an operating system in which scripts can be run on the target independent of the target’s production operating system or the Deployment Server operating system.
4. When the Deployment Agent connects to the Deployment Server, task 1of the job begins to execute. Table 11 Step 4 Target Server WinPE Managed 32-bit, executing task Job Task 1—Deploy System Configuration {WinPE 32-bit} set inputfile=pl.xml call %altiris_share%\lib\bin32\winpe\conrep.cmd –l %inputfile% 5. Task 2 in the job is a Reboot. By looking ahead at task 3, the Deployment Server directs the Deployment Agent to set the One-Time Boot EV to PXE and then reboot.
9. The Deployment Agent begins executing task 6 of the job. Table 16 Step 9 Target Server WinPE 32-bit, executing task Job Task 6—Distribute Disk Image {WinPE 32-bit} .\lib\images\NTFS.IMG 10. Task 7 in the job is a Reboot. By looking ahead at task 8, the Deployment Server directs the Deployment Agent to set the one-time boot EV to PXE and then reboot. When the targets reboot to PXE, the PXE Server sends it the WinPE 64-bit image.
12. After completing task 12, the Deployment Server looks ahead at task 13. Task 13 runs in Windows production. Therefore, the Deployment Server directs the Deployment Agent to reboot. When the target reboots, it boots to the hard drive because it is before PXE in the default boot order. Table 19 Step 12 13. Target Server Executing Windows-scripted install Job Task 13—Install Package {Windows}, pending The Deployment Agent for Windows is installed as part of the Windows-scripted install.
Deployment Server directory structure The following table provides an overview of the Deployment Server directory as populated by the Rapid Deployment Pack. Table 22 Deployment Server directory structure Directory Description .\docs • Rapid Deployment Pack and SmartStart Scripting Toolkit documentation in Portable Document Format (.pdf) .\jobs • The .bin files for the provided jobs .
Customizing the ProLiant and Integrity Integration Modules 4 Getting started Before modifying the provided jobs, folders, and files, make a copy of the job, files, or both and use this copy for your custom work. Keeping the original job and files ensures that a working version exists. If you encounter a problem or if you select to overwrite the jobs or files during an upgrade or reinstallation of the Rapid Deployment Pack, your customized job or file is not overwritten.
To export a job or folder: 1. Right-click the job or folder. 2. Select Export. 3. On the Export Selected Job(s)/Folder(s) screen, click Browse to designate a directory and job file, or enter the path and file name in the Export to File Name field. If you want to export the subfolders of a folder, select Export subfolders. 4. Click OK. To import a job or folder: 1. Right-click within the Jobs pane. 2. Select Import. 3.
VMware ESX Server kickstart files • Change the default root password HP recommends that you do not modify the VMware ESX Server kickstart file with other modifications. For supported VMware kickstart options, see http://www.vmware.com. Virtual Machine jobs • • Change the virtual disk size Change the virtual memory size For more information, see the VMware Virtual Infrastructure SDK Reference Guide at https://www.vmware.com/pdf/SDKReferenceGuide.pdf.
b. Download and extract the support pack to the new directory. c. 2. For VMware and Linux, copy rdpinstall.sh and rdpinstall.dat from a similar support pack to the new directory. In the Deployment Server Console, copy, rename, and edit the job. a. For Windows, modify the Install Package task to reference the chosen directory. b. For VMware or Linux, modify the Copy File to task to reference the chosen directory.
5 HP support and contact information Related documents HP recommends reviewing the following documentation before reading this guide: • • • HP ProLiant Essentials Rapid Deployment Pack Planning Guide HP ProLiant Essentials Rapid Deployment Pack Installation Guide HP ProLiant Essentials Rapid Deployment Pack Knowledge Base at http://www.hp.com/servers/rdp/kb which includes the latest Deployment Support article. All PDF documents can be found at http://www.hp.
HP Software Technical Support and Update Service HP ProLiant Essentials Rapid Deployment Pack now includes one year of 24 x 7 HP Software Technical Support and Update Service. This service provides access to HP technical resources to help you resolve software implementation or operations problems. The service also provides access to software updates and reference manuals either in electronic format or on physical media, as they are made available from HP.
Index imaging, 14, 15 A Altiris Deployment Agent for Linux modifying, 32 B bay properties rule configuration, 17 BIOS settings, 21 Boot from SAN installation, 18 Boot from SAN scripted install jobs, 8 C change rule setting, 17 changing enclosure names, 5 configuring HP BladeSystem servers, 5, 9 image installs, 6 setting change rule, 17 Deployment Server directory structure, 20 Deployment Server directory structure, 28 disk partition, configuration, 21 E editing files, 30 enabling rip-and-replace, 17 en
initial deployment job, 17 ProLiant Integration Module, customizing, 29 installation settings R Red Hat Linux, 23 Windows, 21 Integrated Administrator, 5 Integrated Lights-Out, 5 rack name, 5 RAID settings, 21 Red Hat Linux customizing kickstart files, 31 J installation settings, 23 Job default settings, 21 jobs scripted install, 20 redeployment option, 17 customizing, 29 reference server, creating, 12 server deployment, 20 Related documents, 33 server deployment toolbox, 20 remote management
installation settings, 21 W wait option, 17 Windows Sysprep images, 6 Windows Windows Sysprep jobs, 6 customizing unattend text files, 30 Index 37
