HP Rx2620-2, ProLiant Essentials Rapid Deployment Pack User Manual
HP ProLiant Essentials Rapid Deployment Pack
User Guide
Part number 315378-402
Eleventh edition August 2007
Product version: 3.70
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. 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.
Product version: 3.70
Contents 3
Contents
1 Configuring the Rapid Deployment Pack.......................................................................................... 5
Configuring BladeSystem enclosures........................................................................................................... 5
Configuring image installs......................................................................................................................... 6
Configuring imaging jobs .................................................................................................................... 6
Configuring Windows Sysprep jobs ...................................................................................................... 6
Configuring scripted installs ...................................................................................................................... 7
Configuring scripted install jobs ............................................................................................................ 7
Configuring SAN-attached scripted install jobs........................................................................................ 7
Configuring Boot from SAN scripted install jobs...................................................................................... 8
2 Using the Rapid Deployment Pack ..................................................................................................9
Connecting server blades.......................................................................................................................... 9
Creating a reference server and image..................................................................................................... 12
Deploying a captured image to other similar servers................................................................................... 14
Reconfiguring the new servers ................................................................................................................. 15
Maintaining server blades with rip-and-replace.......................................................................................... 17
Performing a Boot from SAN installation ................................................................................................... 18
3 Understanding the Deployment Server........................................................................................... 20
Jobs ..................................................................................................................................................... 20
Job default settings................................................................................................................................. 21
Hardware configuration settings.......................................................................................................... 21
Operating system scripted install settings.............................................................................................. 21
How a job is run on a target ................................................................................................................... 24
Deployment Server directory structure ....................................................................................................... 28
4 Customizing the ProLiant and Integrity Integration Modules..............................................................29
Getting started....................................................................................................................................... 29
Customizing jobs .............................................................................................................................. 29
Customizing files............................................................................................................................... 30
Reasons to customize the Integration Modules............................................................................................ 30
All operating systems......................................................................................................................... 30
Windows unattend text files................................................................................................................ 30
VMware ESX Server kickstart files........................................................................................................ 31
Virtual Machine jobs ......................................................................................................................... 31
Red Hat Linux kickstart files ................................................................................................................ 31
SUSE Linux control files...................................................................................................................... 31
Customization examples ......................................................................................................................... 31
Example 1—Using a specific ProLiant Support Pack version.................................................................... 31
Example 2—Modifying the Windows unattend text files......................................................................... 32
Example 3—Modifying the Red Hat Linux kickstart files.......................................................................... 32
Example 4—Modifying the Altiris Deployment Agent for Linux ................................................................32
Example 5—Modifying a Create Virtual Machine job for custom virtual values ......................................... 32
5 HP support and contact information ..............................................................................................33
Related documents ................................................................................................................................. 33
Online resources.................................................................................................................................... 33
HP contact information ........................................................................................................................... 33
HP Software Technical Support and Update Service ................................................................................... 34
Contents 4
Index ..................................................................................................................................................35
Configuring the Rapid Deployment Pack 5
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. Before you connect the first server in an enclosure to the
Deployment Server, assign the rack and enclosure with unique names to prevent conflicting database
entries.
If the BladeSystem servers are powered up before the rack name and enclosure name have been
changed, the names are recorded in the Deployment Server database and appear in the Deployment
Server Console. If the names are changed after being recorded in the Deployment Server database,
then the servers must be rebooted for the new rack name and enclosure name to be discovered. In
addition, the original default rack names and the default enclosure names must be manually deleted
from the console.
To change the rack name and enclosure name, follow the procedure specific to each server type:
• ProLiant BL p-Class servers—Place at least one server blade in each enclosure, and before
powering up the server blade, change the rack and enclosure information using the Integrated
Lights-Out (iLO) interface. For details about accessing iLO to change the rack name and
enclosure name, see the documentation shipped with your server blade.
• HP BladeSystem c-Class servers—To access the Onboard Administrator and change the rack
name and the enclosure name, see the server documentation.
Configuring the Rapid Deployment Pack 6
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. For more
information on reading the showdisk output, see the Rapid Deployment Pack Knowledge Base at
http://www.hp.com/servers/rdp/kb
.
Configuring imaging jobs
When capturing or deploying an image to a server with multiple disks, either DAS or SAN, you might
have to specify the system boot disk in the job.
To specify a particular disk:
1. In the Deployment Server Console, copy, rename, and edit the job.
2. Modify the Create Disk Image or Distribute Disk Image task.
3. In the Additional Parameteres box, add the -dx switch, where x is an integer that represents the
appropriate disk number.
When deploying Red Hat Enterprise Linux with LVM, x must be a comma-separated list of
integers representing all of the disk numbers that the LVM volume will span. For example, to
deploy an LVM image that spans the first three disks, use -d1, 2, 3.
Configuring Windows Sysprep jobs
In addition to the steps in the “Configuring imaging jobs” section, the Windows® Sysprep jobs
require a product key and cannot use the product keys entered during the Integration Module
installation.
For each Capture Windows Sysprep Image job:
1. Select the Create Disk Image task.
2. Click Modify.
3. In the Sysprep settings box, select Add new from the Operating System list.
4. On the OS Product Key screen, select the appropriate operating system.
5. Click Add to enter a new product key.
6. Enter the product key in the Product Key box, and click OK>Finish.
For each Deploy Windows Sysprep Image job:
1. Select the Distribute Disk Image task.
2. Click Modify.
3. In the Sysprep settings box, select the appropriate operating system from the Operating System
list.
4. Select the appropriate product key from the Product key list, and click Finish.
Configuring the Rapid Deployment Pack 7
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. Modify the Distribute Disk Image task.
3. In the Additional Parameteres box, add the -dx switch, where x is an integer that represents the
appropriate disk number.
Additionally, for Red Hat Linux in a multiple disk scenario, the kickstart file must specify the system
boot disk.
1. On the Deployment Server, copy and rename the kickstart file.
2. Modify the new kickstart file by replacing the autopart command with separate part command
lines and adding the ---ondisk=XXX option to each where XXX is the device label.
Example for non-LVM:
part /boot --size 75 --ondisk=cciss/c0d0
part swap –size=1000 --ondisk=cciss/c0d0
part / --size 5120 -–grow --ondisk=cciss/c0d0
Example for LVM:
part /boot --size 100 --fstype=ext3 --ondisk=cciss/c0d0
part pv.01 --size=100 --grow --ondisk=cciss/c0d0
volgroup VolGroup00 -–pesize=32768 pv.01
3. In the Deployment Server Console, copy, rename, and edit the job.
4. Edit the Run Script – Create Boot Environment task in the new job to use the new kickstart file
created in step 2.
Configuring SAN-attached scripted install jobs
In addition to the steps in the “Configuring scripted install jobs” section, some further steps might be
necessary.
For VMware ESX Server 3.0.x:
Disconnect the SAN. After the operating system install is complete, reconnect the SAN and create a
VMFS datastore on it.
Configuring the Rapid Deployment Pack 8
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. Select the LUN on which to place the core dump partition. The core dump partition cannot be
created on the local ATA drive.
c. Set the size of the core dump partition. VMware recommends 100 MB for each VMware ESX
Server. The partition size defaults to all remaining available LUN space.
5. Create the Virtual Machine File System (VMFS).
a. Select Storage Management. Available storage volumes and available space are displayed.
The VMFS cannot be created on a local ATA drive.
b. Select Create Volume/Name.
c. Select Typical or Custom. A typical volume allocates all remaining space to the VMFS.
Configuring Boot from SAN scripted install jobs
In addition to the steps in the “Configuring scripted install jobs” section, some further steps may be
necessary.
For VMware ESX Server 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 uncommetting the
export bootfromsan=yes line.
Using the Rapid Deployment Pack 9
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. Insert the server blades into the enclosure, but do not power on the server blades.
3. Change the default rack and enclosure names.
4. Power up the server blades.
5. Open the Deployment Server Console to view target servers available for deployment and
management. The following panes appear in the console:
• Computers—This pane is located on the upper-left side of the console and displays, by
default, New Computers and All Computers. Virtual Machines and Physical Devices are also
displayed (if enabled).
• Jobs—This pane is located on the lower-left side of the console and lists the jobs provided
with the Rapid Deployment Pack.
• Details—This pane is located on the right side of the console and displays details for the
selections highlighted within the Computers pane or the Jobs pane.
Using the Rapid Deployment Pack 10
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.
Table 1 Server icons
Icon Description
Indicates a grouping of physical devices
Indicates a rack
Indicates an enclosure
Indicates a single server blade in a bay
Indicates an unconfigured server blade in a waiting state designated by the user
Indicates a virtual bay
Using the Rapid Deployment Pack 11
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.
Using the Rapid Deployment Pack 12
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. Double-clicking the job in the
Details pane shows the tasks and status.
NOTE: The Windows-scripted installations perform a token-replace of the computer name from
the Deployment Server Console name. This computer name is truncated to the right-most 15
characters to comply with the NETBIOS limitation. The Linux- and VMware-scripted installs use
the Deployment Server Console display name as the server host name.
Loading...