Deploying Virtual Connect Enterprise Manageron Microsoft Cluster Service

5
Configuring a Server Cluster under Windows Server 2003”) for step-by-step instructions for cluster
installation, configuration and installation testing.
Note: the maximum number of nodes supported in a cluster varies depending on operating system
version and type of storage. For details, refer to the article “Maximum number of supported nodes in
a cluster” (navigate to http://support.microsoft.com, and search for “Maximum number of supported
nodes in a cluster”).
If you are installing HP Virtual Connect Enterprise Manager into an environment without a Microsoft
SQL Server 2005 Standard Edition instance already installed, go to “Installing the Microsoft SQL
Server 2005 Standard Edition,” for steps to install a clustered named instance of Microsoft SQL
Server 2005 Standard Edition. This named instance can host the HP Virtual Connect Enterprise
Manager databases.
If an instance of Microsoft SQL Server 2005 Standard Edition already exists in your cluster, you can
go to “Installing HP Virtual Connect Enterprise Manager on the cluster” for steps to install HP Virtual
Connect Enterprise Manager and the process to make it highly available.
Target audience
It is assumed that readers of this document have an excellent understanding of the following concepts
and services:
• Basic clustering concepts
• Basic Microsoft Windows 2003 services
• Advanced TCP/IP and DNS network concepts
In addition, readers must be familiar with installing and administering these products:
• Microsoft Windows Server 2003 Enterprise Edition and MSCS
• Microsoft SQL Server 2005 Standard Edition, particularly named instances
Hardware and software requirements
This document discusses configuring and administering a cluster using the following products:
• A two-system HP ProLiant cluster with
– Each system satisfying all the hardware requirements for HP Virtual Connect Enterprise Manager
1.0
Note: For best results, each system should meet the recommended memory and processor speed
requirements.
– One free shared disk for the HP Virtual Connect Enterprise Manager 1.0 program files
– At least one free shared disk for Microsoft SQL Server 2005
– Microsoft Windows Server 2003 R2 Enterprise Edition with Service Pack 2
– Microsoft Cluster Service
– Microsoft Internet Explorer 6.0
– Simple Network Management Protocol (SNMP)
– Microsoft SQL Server 2005 Standard Edition
– HP Virtual Connect Enterprise Manager 1.0
– HP Management CD (version 7.1 or later) and related ProLiant Support Packs