Compaq ProLiant DL380 G2 Quick reference guide

White Paper
Help us improve our technical communication. Let us know what you think
about the technical information in this document. Your feedback is valuable
and will help us structure future communications. Please send your
comments to: ha[email protected]
October 2002
1717-0702A-WWEN
Prepared by High Availability
Compaq Computer Corporation
Contents
Introduction .............................................2
Purpose....................................................2
Assumptions and Intended
Audience..................................................2
Deployment Components.......................2
ProLiant DL380 G2 Packaged
Cluster ..................................................2
ProLiant Essentials Rapid
Deployment Pack..................................2
ProLiant DL380 G2 Packaged
Cluster Deployment ................................2
Using the Rapid Deployment Pack
V1.20 for Cluster Deployment...............2
Choosing an Operating System
Installation Path ......................................2
Scripted OS Installation ........................2
Imaged OS Installation .........................2
Building and Capturing a
Reference Configuration ........................2
Building the Reference
Configuration ........................................2
Capturing the Reference
Configuration ........................................2
Preparing the Deployment
Environment ............................................2
Directories and File Locations ..............2
Configuration Files................................2
Creating the Cluster Deployment
Events ......................................................2
Creating the Scripted OS
Deployment Event ................................2
Creating the Imaged OS
Deployment Event ................................2
Completing the Cluster
Deployment Event ................................2
Importing Nodes and Deploying
the Cluster ...............................................2
Additional Notes....................................2
Summary..................................................2
Additional Information ...........................2
Appendix A – Troubleshooting..............2
Appendix B – Sample
Configuration Files and Scripts.............2
Configuration Files................................2
Scripts...................................................2
Computer Import File ............................2
Appendix C – Hardware and
Software Configuration ..........................2
Rapid Deployment Guide for the
ProLiant DL380 G2 Packaged
Cluster Using the Rapid
Deployment Pack V1.20
Abstract: This guide details the steps required to deploy a ProLiant
DL380 G2 Packaged Cluster using the ProLiant Essentials Rapid
Deployment Pack V1.20 on Microsoft Windows 2000 Advanced
Server. This guide supplements the ProLiant Essentials Rapid
Deployment Pack, and assumes that an existing deployment
infrastructure already exists. The purpose of this guide is to provide a
turn-key cluster deployment solution for the ProLiant DL380 G2
Packaged Cluster. When the process completes, the system is ready
for a production environment.

Rapid Deployment Guide for the ProLiant DL380 G2 Packaged Cluster Using the Rapid Deployment Pack V1.20 2
1717-0702A-WWEN
Notice
1717-0702A-WWEN 2002 Compaq Information Technologies Group, L.P.
Compaq, the Compaq logo, ProLiant, ROMPaq, SANworks, SoftPaq, SmartStart, and StorageWorks are
trademarks and/or service marks of Compaq Information Technologies Group, L.P. in the U.S. and/or other
countries.
Microsoft, Windows, Windows NT, Windows NT Server and Workstation, Windows 2000, Windows 2000
Server, Windows 2000 Advanced Server, Advanced Server, Windows XP, and Windows Advanced Server
are trademarks and/or registered trademarks of Microsoft Corporation.
Intel, Pentium, Xeon, Pentium II Xeon, Pentium III Xeon, and Itanium are registered trademarks of Intel
Corporation.
NetWare, GroupWise, ManageWise, Novell Storage Services, and Novell are registered trademarks and
intraNetWare, Border Manager, Console One, Z.E.N.works, NDS, and Novell Directory Services are
trademarks of Novell, Inc.
Adobe, Acrobat, and the Acrobat logo are trademarks of Adobe Systems, Inc.
Other product names mentioned herein may be trademarks and/or registered trademarks of their respective
companies.
Compaq shall not be liable for technical or editorial errors or omissions contained herein. The information
in this document is provided “as is” without warranty of any kind and is subject to change without notice.
The warranties for Compaq products are set forth in the express limited warranty statements accompanying
such products. Nothing herein should be construed as constituting an additional warranty.
Rapid Deployment Guide for the ProLiant DL380 G2 Packaged Cluster Using the Rapid Deployment Pack
V1.20
White Paper prepared by High Availability
First Edition (October 2002)
Document Number 1717-0702A-WWEN

Rapid Deployment Guide for the ProLiant DL380 G2 Packaged Cluster Using the Rapid Deployment Pack V1.20 3
1717-0702A-WWEN
Introduction
Server deployment can be a time-consuming task, especially if you need to deploy hundreds of
servers quickly and reliably. As a key component of the Adaptive Infrastructure strategy, the
ProLiant Essentials Rapid Deployment Pack was developed to automate repetitive tasks such as
configuring and deploying servers. The implementation of a rapid deployment infrastructure
significantly reduces IT costs associated with server deployment and redeployment. Key benefits
include improved overall consistency of configurations across multiple servers and reduced IT
resource requirements during large-scale deployments.
This guide explains, in detail, the steps needed to deploy a ProLiant DL380 G2 Packaged Cluster
using the ProLiant Essentials Rapid Deployment Pack V1.20 for Windows 2000 Advanced
Server. These steps include deploying a hardware configuration, deploying Windows 2000
Advanced Server, configuring the Smart Array Cluster Storage enclosure, and deploying the
Microsoft Cluster Service to each node.
Note: This guide discusses sample scripts and configuration files used for cluster deployment
with the ProLiant Essentials Rapid Deployment Pack. These files are contained in SoftPaq
SP21872.EXE. The SoftPaq can be downloaded from the following locations.
www.hp.com/proliant/highavailability or www.hp.com/manage/rapiddeploy
The sample scripts and configuration files are also located on the ProLiant Essentials Rapid
Deployment Pack V1.20 distribution.
Purpose
This guide is intended to be a supplement to the ProLiant Essentials Rapid Deployment Pack. The
purpose of this guide is to provide a turn-key cluster deployment solution for the ProLiant DL380
G2 Packaged Cluster. By following the steps in this guide, a ProLiant DL380 G2 Packaged
Cluster can be deployed without any intervention, and when the process completes, the cluster is
ready for a production environment.
Assumptions and Intended Audience
This guide assumes that an existing deployment infrastructure already exists in the environment,
and is intended to complement the ProLiant Essentials Rapid Deployment Pack. This guide
covers the deployment of Microsoft Windows 2000 Advanced Server and Microsoft Cluster
Services on a ProLiant DL380 G2 Packaged Cluster using the ProLiant Essentials Rapid
Deployment Pack.
Note: For more information on correctly configuring a deployment infrastructure for use with
this guide, please refer to the Implementing a Deployment Infrastructure white paper on the
ProLiant Essentials Rapid Deployment Pack CD.

Rapid Deployment Guide for the ProLiant DL380 G2 Packaged Cluster Using the Rapid Deployment Pack V1.20 4
1717-0702A-WWEN
This paper assumes that the reader has knowledge of the following topics and products:
•Microsoft Windows 2000 Advanced Server
•Microsoft Cluster Services
•ProLiant Essentials Rapid Deployment Pack
•Dynamic Host Configuration Protocol (DHCP) or Bootstrap Protocol (BOOTP)
•Pre-Boot Execution Environment (PXE)
Please see the “Additional Information” section of this paper to find additional information
relating to these topics.
Deployment Components
Before deploying a ProLiant DL380 G2 Packaged Cluster, it is important to understand the
components involved in the deployment process. The ProLiant Essentials Rapid Deployment
Pack facilitates the deployment process through a combination of hardware and software. This
guide centers on a ProLiant DL380 G2 Packaged Cluster deployment running Microsoft
Windows 2000 Advanced Server and Cluster Services.
Additionally, Remote Insight Lights-Out Edition (RILOE) can be used to monitor the deployment
process on the target server and recover from issues that may occur during the deployment
process. For more information on RILOE, please see the “Additional Information” section in this
guide.
ProLiant DL380 G2 Packaged Cluster
The ProLiant DL380 G2 Packaged Cluster is a simple and affordable high availability solution
powered by ProLiant servers and Smart Array technology.
Its features include:
•A complete, 8U cluster package
•Industry standard ProLiant servers and Smart Array storage components
•Redundant controllers on the Smart Array Cluster Storage and redundant server features
on the ProLiant DL380 G2
Hewlett-Packard sets a new standard for performance and value in the enterprise with the
ProLiant DL380 G2 Packaged Cluster. Consisting of two ProLiant DL380 G2 server nodes and a
shared storage cabinet, pre-packaged in a cost-effective and space-efficient fixture, the ProLiant
DL380 G2 Packaged Cluster provides the most affordable clustering solution for Windows NT
Server 4.0, Enterprise Edition, Windows 2000 Advanced Server, Novell NetWare, and Linux.
The ProLiant DL380 G2 Packaged Cluster complements any IT investment by providing high
uptime for business critical applications. Specifically designed to ensure outstanding performance
and seamless integration throughout the entire enterprise, the ProLiant DL380 G2 Packaged
Cluster offers an excellent return on investment by drastically reducing downtime.

Rapid Deployment Guide for the ProLiant DL380 G2 Packaged Cluster Using the Rapid Deployment Pack V1.20 5
1717-0702A-WWEN
ProLiant Essentials Rapid Deployment Pack
The ProLiant Essentials Rapid Deployment Pack combines the remote deployment capabilities of
the Altiris eXpress Deployment Server with the power and flexibility of the SmartStart Scripting
Toolkit, integrated with the Altiris product through the ProLiant Integration Module (PIM) for
Altiris eXpress Deployment Server.
The Altiris eXpress Deployment Server is a GUI-based hardware deployment and software
distribution tool that provides remote console capabilities for both imaging and scripting. Altiris
has also developed enhancements within their base product for Hewlett-Packard products, such as
integration with RILOE and the new ProLiant BL servers.
The ProLiant Integration Module contains sample configuration events, batch files, support
software, and the SmartStart Scripting Toolkit enabling Hewlett-Packard customers to deploy
ProLiant servers quickly and easily. The PIM makes deployment of ProLiant servers using Altiris
eXpress Deployment Server simple. It encapsulates all the necessary steps of configuring and
deploying ProLiant servers into easy-to-use events that the user can simply drag and drop to
deploy one or many servers.
This guide provides instructions for using the ProLiant Integration Module for Altiris eXpress to
deploy ProLiant DL380 G2 Packaged Clusters using these integrated tools, custom scripts, and
configuration events.

Rapid Deployment Guide for the ProLiant DL380 G2 Packaged Cluster Using the Rapid Deployment Pack V1.20 6
1717-0702A-WWEN
ProLiant DL380 G2 Packaged Cluster
Deployment
There are three stages in the deployment of a ProLiant Cluster, depicted here in Figure 1.
Phase 1 Phase 2 Phase 3
Figure 1. Phases of cluster deployment
In Phase 1, typically each cluster node is configured separately. This includes the configuration of
the internal storage and the operating system as well as related service packs and Support Packs.
Phase 2 consists of configuring the external storage using an array configuration tool and then
creating the Windows NTFS partitions. Each partition is then formatted assigned a drive letter.
Phase 3 is the deployment of the final component, Microsoft Cluster Services, to each node.
Using the Rapid Deployment Pack V1.20 for Cluster
Deployment
The guide will demonstrate how to combine these three phases of cluster deployment into a turn-
key solution using the Rapid Deployment Pack V1.20. The next several sections in this guide
detail the steps necessary to utilize the Rapid Deployment Pack to create a drag-and-drop
deployment event for the ProLiant DL380 G2 Packaged Cluster. The following list describes the
major steps in this process using the Rapid Deployment PackV1.20:
•Choose an operating system installation path (scripted OS or imaged OS installation)
oConfigure the reference server and external storage
oCapture the reference server hardware, OS image, and external storage configuration
•Create additional directory structures and edit cluster-specific configuration files on the
deployment server
•Create the deployment event in the Altiris eXpress Console
•Import computers and deploy the events
After completing these tasks, you will have a complete deployment event for the Rapid
Deployment Pack V1.20 to deploy a ProLiant DL380 G2 Packaged Cluster.
Configure the
Hardware
and OS
Configure the
Shared
Storage
Deploy the
Cluster

Rapid Deployment Guide for the ProLiant DL380 G2 Packaged Cluster Using the Rapid Deployment Pack V1.20 7
1717-0702A-WWEN
Choosing an Operating System Installation
Path
Using the Rapid Deployment Pack provides many options for deploying ProLiant DL380 G2
Packaged Clusters. The operating system can be deployed utilizing the Windows unattended
installation feature or by using an OS image captured by the Rapid Deployment Pack.
Scripted OS Installation
Microsoft Windows 2000 supports a completely unattended installation of the operating system.
In a fully scripted operating system installation deployment scenario, the installation of the OS is
managed utilizing this capability as well as a customized Altiris deployment event provided by
the PIM. By editing the unattended installation text file and the event that deploys the operating
system, you can customize the operating system installation to your specifications including
service packs, Support Packs, Microsoft Security updates and more. See “Appendix B” in this
guide for an example of an unattended installation text file.
IMPORTANT: Scripted installations of Windows 2000 require an administrator-level
password stored in plain-text form within the answer file (unattend.txt or other similar file). There
is no way to encrypt this password for scripted installations. For this reason, we recommend that
you protect server administrator passwords in the following ways:
- Ensure that only authorized persons have access to the eXpress share, where the answer files are
located, and ensure that you have a separate user account for accessing the eXpress share than for
the rest of the deployment server.
- Immediately change the Administrator password after server installation using the appropriate
utility from the Microsoft resource kit.
Imaged OS Installation
In order to expedite the deployment process for large-scale cluster deployments, the use of
operating system images can reduce the amount of bandwidth required to transfer OS files and
the length of time taken to land the OS on each cluster node. For the ProLiant DL380 G2
Packaged Cluster, the reference configuration consists of a single DL380 G2 connected to the
Smart Array Cluster Storage. This reference configuration is then captured for use in the
deployment of ProLiant DL380 G2 Packaged Clusters.

Rapid Deployment Guide for the ProLiant DL380 G2 Packaged Cluster Using the Rapid Deployment Pack V1.20 8
1717-0702A-WWEN
Building and Capturing a Reference
Configuration
Baseline hardware, storage, and Windows OS configurations can be captured using the ProLiant
Essentials Rapid Deployment Pack. The results of capturing a reference configuration are
hardware and storage configuration files and a Windows image. These files are then used in the
deployment event for the Rapid Deployment Pack to completely deploy a ProLiant DL380 G2
Packaged Cluster.
Building the Reference Configuration
To create the reference configuration, do the following tasks:
•Configure the server hardware and internal storage
•Install Windows 2000 Advanced Server, selecting the cluster option during component install
•Install related hot fixes and service packs for the OS
•Configure the Smart Array Cluster Storage
•Deploy the Altiris Client (AClient)
Once these tasks have been completed, the Rapid Deployment Pack provides the tools to capture
the hardware and storage configuration and a Windows OS image. The following steps provide
more detail on the requirements for configuring the reference server and storage in preparation for
capture.
1. Assemble one node and the Smart Array Cluster Storage following the cabling guide included
in the documentation for the ProLiant DL380 G2 Packaged Cluster.
IMPORTANT: The cluster documentation states that NIC 1 on each server node should be
used for the cluster interconnect (the cluster heartbeat). For capture and deployment using the
Rapid Deployment Pack, you must use NIC 1 for the public network. Failure to cable the NICs in
this way will prevent communication with the deployment server.
2. Use the Rom-Based Setup Utility (RBSU) to configure the system in preparation for
installation of the OS.
Note: Do not use the SmartStart CD to setup your reference node.
3. Install Windows 2000 Advanced Server with the requirements specified in steps 4-7 and any
others specific to your environment.
4. During the Windows portion of setup, the Windows Component Wizard appears. Select
Cluster Service. Installing this component during setup copies the cluster binaries to the
c:\winnt\cluster directory of the server. These files are necessary later in the deployment
process.
5. Choose the Typical Settings for the network interface cards (NICs) during the installation.
Maintaining the default network configuration is important to the deployment process as
changing them will prevent a successful installation of the cluster.
IMPORTANT: Do not elect to join a domain at this time.

Rapid Deployment Guide for the ProLiant DL380 G2 Packaged Cluster Using the Rapid Deployment Pack V1.20 9
1717-0702A-WWEN
6. After Windows 2000 Advanced Server has been installed, install the latest Windows 2000
service pack and security updates.
7. Install the latest Windows 2000 Support Packs.
8. Create logical drives in the Smart Array Cluster Storage enclosure using the Array
Configuration Utility (ACU).
Note: When creating logical drives, Microsoft recommends that the cluster Quorum disk drive
be at least 500MB in size. Refer to Microsoft Knowledge Base Article Q280345 for more
information.
IMPORTANT: Do not create Windows partitions on the shared storage at this time.
9. Deploy the Altiris Client to the reference server.
Deploying the Altiris Client
The final step in setting up the reference server is to deploy the Altiris Client (AClient). The
AClient is the client software that connects machines to the Altiris eXpress Deployment Server.
The AClient is essential to cluster deployment and allows for capturing the configuration of the
reference server and storage.
The following steps detail how to deploy the Altiris Client to the reference server.
1. From the Altiris eXpress Deployment Server Console, click ToolsÆRemote Client
Installer. You can also click the corresponding icon on the tool bar.
2. Click Add on the Altiris Remote Client Installer window to add the AClient software to the
deployment server. The Default Logon Credentials window opens. Supply or accept the
default administrator-level username and password for the reference server.
Note: If this is the first time that the Remote Client Installer has been used, complete steps 6-9
next and then return to step 3. These steps establish the default AClient settings used when a
Windows image is deployed and configured. If the Remote Client Installer has already been
configured previously, proceed to step 3.
3. The next window shows the computers that are seen on the network. Select the reference
server and press OK to continue.
4. The Altiris Remote Client Installer window now reflects the addition of the reference
server. Select the reference server in the Altiris Remote Client Installer window and click
Properties.
5. The Individual Logon Credentials window opens. Supply an administrator-level user name
and password for the reference server. Now click the Client Settings button to configure the
AClient properties.
6. The first screen prompts for the destination of the AClient files on the target system, and
whether or not the changing of Security IDs (SIDs) is enabled. Use the default for the AClient
file location and be sure the Enable Changing of Security ID checkbox is checked. Click
Next to continue.
7. In the next window, verify that the Use Altiris SIDgen utility to make SID changes option
is selected and click Next to continue. Using Microsoft Sysprep is also supported for
deployment.

Rapid Deployment Guide for the ProLiant DL380 G2 Packaged Cluster Using the Rapid Deployment Pack V1.20 10
1717-0702A-WWEN
8. The next screen asks where to install the AClient on the target server. Accept the default and
click Next.
9. Click Finish on the next window to close the Altiris Client Service Wizard.
Note: If this was the first time to configure the Altiris Client, return to step 3 in this section to
continue.
10. Return to the Altiris Remote Client Installer window. Highlight the reference server in the
list and click Install.
11. On the Confirm Selection pop-up, select Install all items and click OK to continue.
12. Once the installation of the client has completed, close the Remote Client Installer window.
Capturing the Reference Configuration
After configuring the reference server and storage, use the ProLiant Essentials Rapid Deployment
Pack to capture this configuration. The ProLiant Integration Module for the Rapid Deployment
Pack includes events to capture the hardware, storage, and Windows image from the reference
configuration. The capture event used here creates three files, each necessary for ProLiant DL380
G2 Packaged Cluster deployment using the Rapid Deployment Pack V1.20:
•Hardware configuration file
•Array configuration file
•Windows OS image
The following steps outline how to capture these files from the reference configuration for use in
deploying ProLiant DL380 G2 Packaged Clusters.
1. In the Altiris eXpress Deployment Server Console, open the folder labeled SmartStart
Toolkit and OS Imaging Events in the Events window.
2. Double-click the Capture Hardware Configuration and Windows Image event in the
SmartStart Toolkit and OS Imaging Events folder. This opens the properties window for
the event.
3. Select Run Script under the Task heading and click Edit.
4. The Script Task Properties window opens. Under the Run this script bullet is the
embedded script to gather the system configuration from the ROM-Based Setup Utility
(RBSU) on the reference and the logical drive configuration from the Smart Array 5i and
Smart Array Cluster Storage controllers.
5. If it is present, delete the entire line starting with set osfile=... Otherwise, skip this step.
6. The script initially sets the filenames for the hardware configuration file captured from the
RBSU and the array configuration file captured from the array controller(s). Change the
default filenames to names that reflect the server configuration to be captured. For the
purposes of this guide, the filenames are 380G2-H.INI and 380G2-A.INI. The script with the
changes is:
rem Capture Hardware Configuration
rem bootwork unload
set hwrfile=380G2-H.INI
set aryfile=380G2-A.INI
call f:\deploy\tools\scripts\getcfg.bat

Rapid Deployment Guide for the ProLiant DL380 G2 Packaged Cluster Using the Rapid Deployment Pack V1.20 11
1717-0702A-WWEN
The script, getcfg.bat is part of the ProLiant Integration Module and does not require any
changes.
Note: Because this script runs in an MS-DOS environment, the 8.3 standard for all filenames
applies. For example, a valid filename would be 12345678.123.
7. Once all of the changes have been made, click OK to close the Script Task Properties
window.
8. In the Event Properties window, select Create Image under the Task heading then click
Edit.
9. The Disk Imaging Task Properties window opens. Change the default image name to
reflect the server to be imaged. For the purposes of the guide, the image is renamed to
380g2.img. The image filename should read:
.\images\380g2.img
10. After the image name is set, click OK to close the Disk Imaging Task Properties window,
then click OK to close the Event Properties Window.
11. Drag-and-drop the Capture Hardware Configuration and Windows Image event in the
Events pane onto the reference server listed in the Computers pane.
12. The next screen shows the Schedule Computers for Event window. The default is to run the
event immediately. Accept the default and click OK to run the event.
At this point, the reference server reboots to capture the Windows image, hardware, and array
information.
Note: If the reference server has never gone through a PXE boot, a message may appear on the
reference server when it is rebooted to execute the script. This message refers to the lack of a
PXE boot stamp. Simply click OK to allow the reference server to reboot; the PXE boot stamp
will be applied once the script is executed.

Rapid Deployment Guide for the ProLiant DL380 G2 Packaged Cluster Using the Rapid Deployment Pack V1.20 12
1717-0702A-WWEN
Preparing the Deployment Environment
A properly configured deployment infrastructure includes the correct directory structure and file
location on the deployment server.
Directories and File Locations
For deploying ProLiant DL380 G2 Packaged Clusters, at least four directories must be added to
the existing directory structure. Do the following to complete the directory structure configuration
needed for deploying clusters with the Rapid Deployment Pack V1.20.
1. On the deployment server, browse to c:\Program Files\Altiris\eXpress\Deployment Server.
Create a subdirectory under the deploy directory called clusters.
2. Under the clusters directory, create the subdirectories common and a directory named for
each cluster to be deployed. For this guide, a cluster folder called MYCLUS1 has been
placed under the clusters directory.
3. Under the common directory, create the subdirectories scripts and tools.
4. Download the SoftPaq and place all of the script files in the .\clusters\common\scripts\
directory. Place the executables from the SoftPaq in the .\clusters\common\tools\ directory.
Note: For each cluster being deployed, a separate directory must exist under clusters with the
same name as the that intended for the cluster.

Rapid Deployment Guide for the ProLiant DL380 G2 Packaged Cluster Using the Rapid Deployment Pack V1.20 13
1717-0702A-WWEN
The scripts called by the Rapid Deployment Pack event to be created later require that all
configuration files, OS images, and tools be located in the directories indicated in Figure 2. Each
of the files listed here are used in the deployment process.
Figure 2. Directory structure for cluster deployment with the Rapid Deployment Pack V1.20
Note: Items marked with a * must follow DOS 8.3 naming conventions.
Items marked with a + are only required for scripted Windows installations.
In the deploy directory on the deployment server, the cds, configs, and tools directories are created
and populated during the install of Rapid Deployment Pack V1.20.
The following list describes each deployment specific directory and its contents:
•cds – This directory contains the installation CDs for the operating systems when an
unattended OS deployment is used. It also contains the Support Packs from HP.
•clusters – The clusters directory created specifically for deploying ProLiant Clusters contains
a common directory for cluster-specific scripts and tools provided in SoftPaq SP21872.EXE.
The cluster name directory, here called MYCLUS1, contains the unattended installation text
files required for each node in a scripted OS installation and the shared storage configuration
file required regardless of deployment type.

Rapid Deployment Guide for the ProLiant DL380 G2 Packaged Cluster Using the Rapid Deployment Pack V1.20 14
1717-0702A-WWEN
•configs – This directory contains the configuration files captured from the reference server.
•tools – This directory has two subdirectories. The first is the scripts directory, which holds
all of the scripts used by the ProLiant Integration Module. The second subdirectory is the ssst
directory, which holds all of the SmartStart Scripting Toolkit tools.
Configuration Files
Computer Import File
Altiris eXpress Deployment Server provides a mechanism to import computers into its database
before they have been recognized on the network. Using a pre-built import file, cluster nodes can be
imported into the system and assigned events before they are ever turned on. From the perspective of
remote deployment, this feature eases the deployment process.
Use this mechanism to import each cluster node into the Altiris computer database in order to deploy
a ProLiant DL380 G2 Packaged Cluster using the Rapid Deployment Pack. Please refer to “Appendix
B” for the format of the import file to use to import each node.
Note: A template for use in importing DL380 G2 cluster nodes, called nodeimport.txt, is also
available in the SoftPaq distribution and the Rapid Deployment Pack V1.20 CD.
The computer import file must contain the following for each node imported into the database:
•Node name
•Serial number
•Logon domain for the cluster
•Cluster name to which each node will belong
•Default IP address for NIC2
•Default gateway for NIC2
The template supplies a private IP address and default gateway for the second NIC in each node.
These values are specified in the import file to avoid disabling the NICs if they are connected via a
crossover cable and use DHCP. Determine the values of the other node properties listed here and have
them available for use in the next section. If you wish to specify a static IP address for NIC1 in your
cluster nodes do so in the import file following the template on the deployment server.
Creating the Computer Import File
1. Make a copy of the sample import file, nodeimport.txt and place it on the deployment server.
2. Open this copy and edit the appropriate fields with the information for your cluster.
3. All other fields specified in the template but not listed in this section are optional. If electing not
to supply these fields during import, delete the default field data, leaving all trailing commas.
After creating the deployment event, please refer to the section “Importing Nodes and Deploying the
Cluster” in this guide for the steps to use this import file to import the cluster nodes.
Shared Storage Configuration File
For a cluster, configuration of the shared storage can only occur after the hardware and operating
system have been deployed to at least one node. The hardware and storage configuration capture

Rapid Deployment Guide for the ProLiant DL380 G2 Packaged Cluster Using the Rapid Deployment Pack V1.20 15
1717-0702A-WWEN
process captures both the internal and the external storage array information of a reference server. To
satisfy the requirements for cluster deployment, a separate file containing the shared storage array
information must be created.
Creating the Shared Storage Configuration File
The capture process completed in “Capturing the Reference Configuration” will have created an array
configuration file with the internal and external array configurations. Because of cluster deployment
requirements (discussed in “ProLiant DL380 G2 Packaged Cluster Deployment” in this guide) the
internal array must be configured first. Then after configuring the server, the Smart Array Cluster
Storage can be configured. Two separate array configuration files are necessary to accomplish this.
1. Make a copy of the captured array configuration file in the configs directory on the deployment
server. In this guide, this file is called 380G2-A.INI.
2. Rename the copied file to indicate its use as for the shared storage. This guide uses SHARED.INI
as the name of the shared storage configuration file.
3. Open the original array file (here called 380G2-A.INI), and remove everything in the section
starting with:
;Controller specifications
;Smart Array Cluster Storage Ext 1 Connected to
Be sure to only remove the information pertaining to the external storage.
4. Save and close the internal array configuration file (380G2-A.INI).
5. Open the shared storage array configuration file (here called SHARED.INI), and remove
everything following the section starting with:
;Controller specifications
;Controller Compaq Smart Array 5i
Be sure to only remove the information pertaining to the internal storage.
6. Save and close the external array configuration file (380G2-A.INI).
7. Now move this file from the configs directory and place it in the cluster directory in clusters on
the deployment server. This directory is called MYCLUS1 in this guide.
Please see “Appendix B” for examples of the internal and shared storage array configuration files.
Unattended Text File for Scripted Windows Installations
If using scripted Windows installations for OS deployment, each node needs its own unattended
installation text file. This file must have the same name as the computer name specified in the import
file with the .txt file extension. For example, a node in the cluster deployed in this paper is named
CLUS1N1. Its corresponding unattended installation file is called CLUS1N1.txt. This file must be in
the clusters directory for your cluster on the deployment server.
Note: Unattended installation text files are only for scripted OS deployments.
The configs directory on the Altiris Deployment Server contains a base Windows 2000 unattended
installation text file. The file is divided into sections demarcated by brackets [ ]. Execute the
following steps to customize the unattended installation text files for cluster deployment.
1. Make two copies of this text file and place them in the directory named for the cluster to be
deployed in the clusters directory on the deployment server.

Rapid Deployment Guide for the ProLiant DL380 G2 Packaged Cluster Using the Rapid Deployment Pack V1.20 16
1717-0702A-WWEN
2. Rename each text file to the node name specified in the import file. In this guide, the files are
called CLUS1N1.txt and CLUS1N2.txt and they reside in the MYCLUS1 directory.
3. Once these files are in the correct directory, open each and add or update the following sections
listed here. Please update each section noted by [ ] with information specific to your deployment
configuration.
[GuiUnattended]
AdminPassword=*
[Identification]
DomainAdmin=*
DomainAdminPassword=*
JoinDomain=*
[UserData]
ComputerName=*
FullName=*
OrgName=*
[Components]
Cluster=On
4. Fields marked with an * need to be updated with information specific to your cluster deployment
scenario.
5. SNMP trap destinations and community strings can be set at this time in the unattended
installation text file.

Rapid Deployment Guide for the ProLiant DL380 G2 Packaged Cluster Using the Rapid Deployment Pack V1.20 17
1717-0702A-WWEN
Creating the Cluster Deployment Events
This section details the steps to create both a Scripted and Imaged OS Deployment Event. Each
subsection represents a task in the event for deploying a ProLiant DL380 G2 Packaged Cluster. Every
task in the deployment event that calls a Rapid Deployment Pack provided script has an embedded
script. These embedded scripts usually contain variables whose values must be customized for each
cluster deployment. However, the scripts provided with the Rapid Deployment Pack do not require
any changes after being called by these embedded scripts.
Where indicated, make the necessary changes to filenames, paths, and variables and the deployment
event will be ready for use to deploy a cluster.
Note: Each of the scripts described in this section are listed in their entirety in “Appendix B”.
1. In the Altiris eXpress Deployment Server Console , right-click on the white space in the Events
pane shown here in Figure 3. Select New Folder.
2. Change the name of this event folder to Packaged Cluster Deployment Events. This folder will
contain any events to deploy ProLiant DL380 G2 Packaged Clusters.
Figure 3. Events pane in the Altiris eXpress Server console
3. If using scripted OS installations during cluster deployment, proceed to the next section,
“Creating the Scripted OS Deployment Event”. If imaged OS installations will be used during
cluster deployment, proceed to “Creating the Imaged OS Deployment Event” in this guide.

Rapid Deployment Guide for the ProLiant DL380 G2 Packaged Cluster Using the Rapid Deployment Pack V1.20 18
1717-0702A-WWEN
Creating the Scripted OS Deployment Event
1. In the Altiris eXpress Deployment Server Console, expand the events folder named Microsoft
Windows 2000 Scripted Install Events.
2. Right-click on ProLiant ML/DL Scripted Install for Microsoft Windows 2000 event and
select Copy.
3. Right-click on the Packaged Cluster Deployment Events folder and select Paste.
4. In the Packaged Cluster Deployment Events folder, right-click on ProLiant ML/DL Scripted
Install for Microsoft Windows 2000 event and select Rename. For this guide, the event is
named Scripted OS Packaged Cluster Deployment.
Deploying the Hardware Configuration
1. Double-click on the Scripted OS Packaged Cluster Deployment Event to open the Event
Properties window shown here in Figure 4.
Figure 4. Event Properties window
2. This window shows all the tasks in this event. Click on the first task, Run Script and select Edit.

Rapid Deployment Guide for the ProLiant DL380 G2 Packaged Cluster Using the Rapid Deployment Pack V1.20 19
1717-0702A-WWEN
3. This opens the Script Task Properties window shown here in Figure 5.
Figure 5. Set hardware configuration Script Task Properties window
4. Under the Run this script bullet is the embedded script to deploy the system configuration to the
RBSU and the logical drive configuration to the Smart Array 5i array controller on the cluster
node. In this script, change the default values for hwrfile and aryfile to the names of the hardware
and internal storage configuration files for your cluster deployment. For this guide, the filenames
are 380G2-H.INI and 380G2-A.INI.
5. If it is present, delete the entire line starting with set osfile=... The script with changes is:
rem Deploy Hardware Configuration
rem bootwork unload
rem deployment start
set hwrfile=380G2-H.ini
set aryfile=380G2-A.ini
call f:\deploy\tools\scripts\setcfg.bat
Please note the call to setcfg.bat. This script is part of the ProLiant Integration Module and does
not require any changes.
Note: Make sure that the filename specified for the aryfile is the file that contains only the local
drive array configuration.
6. Click OK to close the Script Task Properties window.
Set Disk Partition
The Rapid Deployment Pack comes with a partition file that specifies a 2 GB partition for the boot
drive on a target server. Once the OS is installed to this partition, the partition is expanded to span the
full size of the drive. No changes need to be made to this task.

Rapid Deployment Guide for the ProLiant DL380 G2 Packaged Cluster Using the Rapid Deployment Pack V1.20 20
1717-0702A-WWEN
Install OS
1. In the Event Properties window for the Scripted OS Packaged Cluster Deployment Event
click on the next task, Run Script (Install OS) and select Edit.
2. This opens the Script Task Properties window. Under the Run this script bullet is the embedded
script to specify the unattended installation file for the node being deployed. First, add a variable
called ClusterName to specify the name of the cluster being deployed, in this case, MYCLUS1.
3. Change the value for the variable unattendfile to the following:
..\clusters\%ClusterName%\%NODENAME%.txt
Using the Altiris provided environment variable NODENAME specifies the unattended
installation text file for the node in the cluster directory on the deployment server.
4. The embedded script should now look similar to this:
rem Install OS
rem bootwork unload
set ss=ss.550
set os=w2k
set ClusterName=MYCLUS1
set unattendfile=..\clusters\%ClusterName%\%NODENAME%.txt
call f:\deploy\tools\scripts\w2k.bat
5. Click OK to close the Script Task Properties window.
Install OS (Part 2)
This task calls winnt.exe and supplies the unattended installation file to the application so that it can
install Windows 2000 on each node. No changes need to be made to this task.
Complete the Cluster Deployment Event
Install OS (Part 2) is the last task specific to a scripted OS deployment. Proceed to “Completing the
Cluster Deployment Event” in this guide to complete the Packaged Cluster Deployment Event for a
scripted OS installation.