Installing and upgrading to HP Insight Software 6.2 on Windows Server 2003 R2 MSCS for high availability
10
One shared disk for
the Cluster Quorum
,
drive
U
:
One shared disk for DTC, drive T:
It is recommended that SAN storage be used for boot disks as well as the shared disks. See the
document
Booting HP ProLiant servers from a storage area network
.
W
hen
testing for this white paper, the disks for the cluster
Quorum
and
DTC
r were sized at 1 GB
each.
TIPS:
In order to allow boot disks and cluster disks to be on the same SAN,
the registry must be modified on each
system
,
before installing MSCS.
For detailed instructions, depending on the version of Windows Server
2003, see
How to add a registry value to a Windows Server 2003
-
based computer that you start from a SAN so that the sta
rtup disk, the
pagefile disks, and the cluster disks are all on the same SAN fabric
.
To
avoid improper modification of the registry, the
Boot from SAN Cluster
Registry Update utility
can be used to add the
ManageDisksOnSyste
mBuses key. The utility
BF
S
C
L
R
e
gUp
.
exe
can be
downloaded from
http://www.hp.com
.
The SAN
snapclone
feature provides a convenient way to create restore
points that can be used with backup schemes and to facilitate the
reinstallation of software if needed.
Network
MSCS
require
s
that each virtual server in a cluster have a unique static IP
address. For th
e
configuration described in this paper, four static IP addresses are required for the four virtual
servers described below.
1.
MSCS cluster virtual server IP address and name
Function:
To act as the virtual server IP address and name for the
MSCS
software.
Suggested action:
MSCS management tools use this address to get status and reconfigure the
MSCS software. In addition, HP Systems Insight Manager uses this address to recognize the
MSCS cluster.
For the examples discussed in this paper, the IP address is
1
40.110.240.62
and the name is
CMS
-
CLUSTER
.
2.
Systems Insight Manager
and Insight Software virtual server
IP address and name
Function:
To act as the virtual server IP address and name for Insight Software and HP Systems
Insight Manager. You specify this nam
e and address to connect to HP Systems Insight Manager
through your browser.
Suggested action:
All SNMP devices that report their events to
Systems Insight Manager
should
use this IP address and name for the location of the Event Consolidator, the SNMP Tra
p
Destination. The host defined for the WMI Mapper proxy should use this name and IP address
unless the WMI Mapper service runs on a system that is not a cluster member and the WMI
Mapper is not installed as part of Insight Software. For the examples discu
ssed in this white
paper, the IP address is
140.110.240.64
and the name is
CMS
-
HPSystems Insight Manager
.
3.
Microsoft SQL Server
2005 virtual server IP address and name