Installation Checklist – hp ProLiant DL380 Packaged Cluster using Microsoft Windows Server 2003, Enterprise Edition
high availability
systems
engineering
December 2004
installation
checklist
hp ProLiant
DL380
Packaged
Cluster
installation checklist - ProLiant DL380 G4 Packaged Cluster with
MSA500 G2 storage using Microsoft Windows Server 2003,
Enterprise Edition
The ProLiant DL380 G4 Packaged Cluster with MSA500 G2
consists of two ProLiant servers and MSA500 G2 storage.
Pre-packaged in a cost effective, space efficient fixture, it
gives you the most affordable clustering solution for Microsoft
Windows Server 2003, Enterprise Edition.
ProLiant DL380 G4 Server Highlights
− Intel Xeon processors with EM64T, a 800MHz FSB
− PC2-3200R 400MHz DDR2 Memory
− Integrated Ultra320 Smart Array 6i Controller
− NC7782 Dual Port PCI-X Gigabit Server Adapter
− Three available 64-bit PCI-X slots
Modular Smart Array 500 G2 Storage Highlights
− Battery-Backed 256M cache, upgradeable to 512M.
− Fourteen hot-plug drive bays.
− Optional redundant MSA storage controller.
Optional 4-Port I/O module.
−
hardware
cabling scheme
1
Installation Checklist – hp ProLiant DL380 Packaged Cluster using Microsoft Windows Server 2003, Enterprise Edition
introduction
Microsoft Windows Server 2003, Enterprise Edition is an extension of the Microsoft
Windows 2000 operating system environment developed to enhance the customer
experience and to improve the overall usability and deployment.
General cluster improvements for Microsoft Windows Server 2003, Enterprise Edition
include:
• Larger cluster sizes – While Enterprise Edition now supports up to 8 nodes, the
HP ProLiant DL380 Packaged Cluster supports a maximum of 2 nodes.
• Enhanced cluster installation wizard – built-in validation and verification
function to help ensure base components are ready to be clustered.
• Installation – cluster binaries are automatically copied during the operating
system installation.
• Multi-node addition – multiple nodes can be added in a single operation instead
of one by one.
• Active Directory integration – tighter integration including a “virtual” computer
object, Kerberos authentication, and a default location for services to publish service
control points. Users can access the virtual server just like any other Windows
server.
This checklist provides step-by-step ProLiant Packaged Cluster operating system installation
and cluster configuration directions using Microsoft Windows Server 2003, Enterprise
Edition.
software and
hardware prechecks
The following table provides a checklist of the required software versions and, if applicable,
any items to execute before beginning the installation. Place a checkmark (3) in the box
after completing each step.
3
Refer to the MSCS Support Matrix for the ProLiant DL380 Packaged Cluster which is located at:
http://h18004.www1.hp.com/solutions/enterprise/highavailability/answercenter/configuration-all.html
Important: This support matrix represents the quality tested and supported ProLiant DL380 Packaged
Cluster configurations. Customers should select from the column of deliverables that are relevant to the
configuration they require.
SmartStart 7.10 or later.
Microsoft Windows Server 2003, Enterprise Edition software and documentation.
Modular Smart Array 500 G2 (MSA500 G2) Storage controller firmware. The latest firmware can be
obtained from the link above.
Smart Array 6i controller firmware. The latest firmware can be obtained from the link above.
Ensure that any shared storage configuration that may currently exist is erased.
Review and understand any Read This First (RTF) cards that were shipped with the product.
Ensure all hardware is installed and properly cabled.
Software and Hardware Pre-checks
2
Installation Checklist – hp ProLiant DL380 Packaged Cluster using Microsoft Windows Server 2003, Enterprise Edition
information
gathering
The following table provides a checklist for the required input parameters that will facilitate
the operating system and cluster installation. Write the information in the values column
next to each item. Place a checkmark (3) in the box after completing each step.
3
Name for each node Node 1: Node 2:
Item Values
Public network connection IP
address and subnet mask for
each node
Private network connection
(cluster heartbeat) IP address
and subnet mask for each node
Cluster name:
Cluster IP address and subnet
mask:
Default gateway address: IP address:
WINS server address: IP address:
DNS address: IP address:
Local machine Administrator
password (used during OS
installation):
Node 1 Node 2
IP address:
Subnet mask:
Node 1 Node 2
IP address:
Subnet mask:
IP address:
Subnet mask:
Subnet mask:
Subnet mask:
Subnet mask:
Know the Administrator password
IP address:
Subnet mask:
IP address:
Subnet mask:
Domain name:
Domain administrator user name
and password (used during OS
installation to have the machine
join the domain:
Domain account name and
password for cluster service (this
account has special privileges
on each cluster node):
Know the user name and password
Know the user name and password
3