cluster configuration w2k3

8/11/2019 Cluster Configuration W2k3

1/50

Guide to Creating and Configuring a Server Clusterunder Windows Server 2003

By Elden Christensen

Microsoft Corporation

Published: November 11, 200

Abstract

This guide provides step-by-step instructions for creating and configuring a typical single quoru

device ulti-node server cluster using a shared dis! on servers running the "icrosoft# Windows#

Server 2003 $nterprise $dition and Windows Server 2003 %atacenter $dition operating systes&


2/50

Microsoft! "indo#s! $erver 200 "hite Paper

%his is a preliminary document and may be chan&ed substantially prior tofinal commercial release of the soft#are described herein'

%he information contained in this document represents the current vie# ofMicrosoft Corporation on the issues discussed as of the date of

publication' Because Microsoft must respond to chan&in& mar(etconditions, it should not be interpreted to be a commitment on the part ofMicrosoft, and Microsoft cannot &uarantee the accuracy of anyinformation presented after the date of publication'

%his document is for informational purposes only' M)C*+$+% M-.E$

N+ "-**-N%)E$, E/P*E$$ +* )MP)E, -$ %+ %E )N+*M-%)+N)N %)$ +C3MEN%'

Complyin& #ith all applicable copyri&ht la#s is the responsibility of theuser' "ithout limitin& the ri&hts under copyri&ht, no part of this documentmay be reproduced, stored in or introduced into a retrieval system, ortransmitted in any form or by any means 4electronic, mechanical,

photocopyin&, recordin&, or other#ise5, or for any purpose, #ithout thee6press #ritten permission of Microsoft Corporation'

Microsoft may have patents, patent applications, trademar(s, copyri&hts,or other intellectual property ri&hts coverin& sub7ect matter in thisdocument' E6cept as e6pressly provided in any #ritten license a&reementfrom Microsoft, the furnishin& of this document does not &ive you anylicense to these patents, trademar(s, copyri&hts, or other intellectual

property'

8 200 Microsoft Corporation' -ll ri&hts reserved'

Microsoft, "indo#s, the "indo#s lo&o, "indo#s N%, and "indo#s$erverare either re&istered trademar(s or trademar(s of MicrosoftCorporation in the 3nited $tates and9or other countries'

%he names of actual companies and products mentioned herein may bethe trademar(s of their respective o#ners'


3/50


Contents

Introduction............................................................................................................................................ 1

Checklists for Server Cluster Configuration:.......................................................................................2

Software 'equireents&&&&&&&&&&&&&&&&&&&&&&&&&&&&&&&&&&&&&&&&&&&&&&&&&&&&&&&&&&&&&&&&&&&&&&&&&&&&&&&&&&&&&&&&&&&&&&&&&&&&&&&&&&&&&&&&&&&&&&&& 2

(ardware 'equireents&&&&&&&&&&&&&&&&&&&&&&&&&&&&&&&&&&&&&&&&&&&&&&&&&&&&&&&&&&&&&&&&&&&&&&&&&&&&&&&&&&&&&&&&&&&&&&&&&&&&&&&&&&&&&&&&&&&&&&& 2

)etwor! 'equireents&&&&&&&&&&&&&&&&&&&&&&&&&&&&&&&&&&&&&&&&&&&&&&&&&&&&&&&&&&&&&&&&&&&&&&&&&&&&&&&&&&&&&&&&&&&&&&&&&&&&&&&&&&&&&&&&&&&&&&&&& 2

Shared %is! 'equireents*&&&&&&&&&&&&&&&&&&&&&&&&&&&&&&&&&&&&&&&&&&&&&&&&&&&&&&&&&&&&&&&&&&&&&&&&&&&&&&&&&&&&&&&&&&&&&&&&&&&&&&&&&&&&&&&&&&3

Cluster Installation................................................................................................................................. 5

+nstallation ,verview&&&&&&&&&&&&&&&&&&&&&&&&&&&&&&&&&&&&&&&&&&&&&&&&&&&&&&&&&&&&&&&&&&&&&&&&&&&&&&&&&&&&&&&&&&&&&&&&&&&&&&&&&&&&&&&&&&&&&&&&&&&&&

+nstalling the Windows Server 2003 ,perating Syste&&&&&&&&&&&&&&&&&&&&&&&&&&&&&&&&&&&&&&&&&&&&&&&&&&&&&&&&&&&&&&&&&&&&&&&&.

Setting /p )etwor!s&&&&&&&&&&&&&&&&&&&&&&&&&&&&&&&&&&&&&&&&&&&&&&&&&&&&&&&&&&&&&&&&&&&&&&&&&&&&&&&&&&&&&&&&&&&&&&&&&&&&&&&&&&&&&&&&&&&&&&&&&&&&& .

General )etwor! Configuration*&&&&&&&&&&&&&&&&&&&&&&&&&&&&&&&&&&&&&&&&&&&&&&&&&&&&&&&&&&&&&&&&&&&&&&&&&&&&&&&&&&&&&&&&&&&&&&&&&&&&&&&&&&&&

Configuring the 1rivate )etwor! dapter&&&&&&&&&&&&&&&&&&&&&&&&&&&&&&&&&&&&&&&&&&&&&&&&&&&&&&&&&&&&&&&&&&&&&&&&&&&&&&&&&&&&&&&&&&&&&&

Configuring the 1ublic )etwor! dapter&&&&&&&&&&&&&&&&&&&&&&&&&&&&&&&&&&&&&&&&&&&&&&&&&&&&&&&&&&&&&&&&&&&&&&&&&&&&&&&&&&&&&&&&&&&&& 42

5erifying Connectivity and )ae 'esolution&&&&&&&&&&&&&&&&&&&&&&&&&&&&&&&&&&&&&&&&&&&&&&&&&&&&&&&&&&&&&&&&&&&&&&&&&&&&&&&&&&&42

5erifying %oain "ebership&&&&&&&&&&&&&&&&&&&&&&&&&&&&&&&&&&&&&&&&&&&&&&&&&&&&&&&&&&&&&&&&&&&&&&&&&&&&&&&&&&&&&&&&&&&&&&&&&&&&&&&&&42

Setting /p a Cluster /ser ccount&&&&&&&&&&&&&&&&&&&&&&&&&&&&&&&&&&&&&&&&&&&&&&&&&&&&&&&&&&&&&&&&&&&&&&&&&&&&&&&&&&&&&&&&&&&&&&&&&& 43

Setting up Shared %is!s&&&&&&&&&&&&&&&&&&&&&&&&&&&&&&&&&&&&&&&&&&&&&&&&&&&&&&&&&&&&&&&&&&&&&&&&&&&&&&&&&&&&&&&&&&&&&&&&&&&&&&&&&&&&&&&&&&&&& 4

bout the 6uoru %is!&&&&&&&&&&&&&&&&&&&&&&&&&&&&&&&&&&&&&&&&&&&&&&&&&&&&&&&&&&&&&&&&&&&&&&&&&&&&&&&&&&&&&&&&&&&&&&&&&&&&&&&&&&&&&&&&&&& 4

Configuring the Cluster Service..........................................................................................................19

5alidating the Cluster +nstallation&&&&&&&&&&&&&&&&&&&&&&&&&&&&&&&&&&&&&&&&&&&&&&&&&&&&&&&&&&&&&&&&&&&&&&&&&&&&&&&&&&&&&&&&&&&&&&&&&&&&&&&& 2

Configuring the Second )ode&&&&&&&&&&&&&&&&&&&&&&&&&&&&&&&&&&&&&&&&&&&&&&&&&&&&&&&&&&&&&&&&&&&&&&&&&&&&&&&&&&&&&&&&&&&&&&&&&&&&&&&&&&&&& 27

Post-Installation Configuration........................................................................................................... !

(eartbeat Configuration&&&&&&&&&&&&&&&&&&&&&&&&&&&&&&&&&&&&&&&&&&&&&&&&&&&&&&&&&&&&&&&&&&&&&&&&&&&&&&&&&&&&&&&&&&&&&&&&&&&&&&&&&&&&&&&&&&&&&&30

(eartbeat dapter 1rioriti8ation&&&&&&&&&&&&&&&&&&&&&&&&&&&&&&&&&&&&&&&&&&&&&&&&&&&&&&&&&&&&&&&&&&&&&&&&&&&&&&&&&&&&&&&&&&&&&&&&&&&&&&&32

Configuring Cluster %is!s&&&&&&&&&&&&&&&&&&&&&&&&&&&&&&&&&&&&&&&&&&&&&&&&&&&&&&&&&&&&&&&&&&&&&&&&&&&&&&&&&&&&&&&&&&&&&&&&&&&&&&&&&&&&&&&&&&& 32

6uoru %is! Configuration&&&&&&&&&&&&&&&&&&&&&&&&&&&&&&&&&&&&&&&&&&&&&&&&&&&&&&&&&&&&&&&&&&&&&&&&&&&&&&&&&&&&&&&&&&&&&&&&&&&&&&&&&&&&&&&&&33

Creating a 9oot %elay&&&&&&&&&&&&&&&&&&&&&&&&&&&&&&&&&&&&&&&&&&&&&&&&&&&&&&&&&&&&&&&&&&&&&&&&&&&&&&&&&&&&&&&&&&&&&&&&&&&&&&&&&&&&&&&&&&&&&&&&&3:

"est Installation.................................................................................................................................... 5

Test ;ailover&&&&&&&&&&&&&&&&&&&&&&&&&&&&&&&&&&&&&&&&&&&&&&&&&&&&&&&&&&&&&&&&&&&&&&&&&&&&&&&&&&&&&&&&&&&&&&&&&&&&&&&&&&&&&&&&&&&&&&&&&&&&&&&&&&&&& && 3

iii


4/50


A##endi$............................................................................................................................................... %

dvanced Testing&&&&&&&&&&&&&&&&&&&&&&&&&&&&&&&&&&&&&&&&&&&&&&&&&&&&&&&&&&&&&&&&&&&&&&&&&&&&&&&&&&&&&&&&&&&&&&&&&&&&&&&&&&&&&&&&&&&&&&&&&&&&&&&& 3

SCS+ %rive +nstallations&&&&&&&&&&&&&&&&&&&&&&&&&&&&&&&&&&&&&&&&&&&&&&&&&&&&&&&&&&&&&&&&&&&&&&&&&&&&&&&&&&&&&&&&&&&&&&&&&&&&&&&&&&&&&&&&&&&&&& 37

Configuring the SCS+ %evices&&&&&&&&&&&&&&&&&&&&&&&&&&&&&&&&&&&&&&&&&&&&&&&&&&&&&&&&&&&&&&&&&&&&&&&&&&&&&&&&&&&&&&&&&&&&&&&&&&&&&&&&& 37

Terinating the Shared SCS+ 9us&&&&&&&&&&&&&&&&&&&&&&&&&&&&&&&&&&&&&&&&&&&&&&&&&&&&&&&&&&&&&&&&&&&&&&&&&&&&&&&&&&&&&&&&&&&&&&&&&&&37

Storage rea )etwor! Considerations&&&&&&&&&&&&&&&&&&&&&&&&&&&&&&&&&&&&&&&&&&&&&&&&&&&&&&&&&&&&&&&&&&&&&&&&&&&&&&&&&&&&&&&&&&&&&&&&:0

/sing S)s with Server Clusters&&&&&&&&&&&&&&&&&&&&&&&&&&&&&&&&&&&&&&&&&&&&&&&&&&&&&&&&&&&&&&&&&&&&&&&&&&&&&&&&&&&&&&&&&&&&&&&&&&&&:4

&elated 'inks........................................................................................................................................ ()

iv


5/50


Introduction

server cluster is a group of independent servers wor!ing collectively and running the "icrosoft Cluster

Service


6/50


Checklists for Server Cluster Configuration:

This chec!list helps you prepare for installation& Step-by-step instructions begin after the chec!list&

Softare &e/uire0ents

"icrosoft Windows Server 2003 $nterprise $dition or Windows Server 2003 %atacenter $dition

installed on all coputers in the cluster&

nae resolution ethod such as %oain )ae Syste DNS dynamic update protocol>

Windows +nternet )ae Service (,STS> and so on&

n eAisting doain odel&

ll nodes ust be ebers of the sae doain&

doain-level account that is a eber of the local adinistrators group on each node& dedicated

account is recoended&

*ardare &e/uire0ents

Clustering hardware ust be on the cluster service (ardware Copatibility Eist go to the Windows (ardware Copatibility Eistat

http*FFwww&icrosoft&coFhclF >and then search for cluster& The entire solution ust be certified on the

(CE> not Dust the individual coponents& ;or additional inforation> see the following article in the

"icrosoft nowledge 9ase*

303The "icrosoft Support 1olicy for Server Clusters and the (ardware

ote:+f you are installing this cluster on a storage area networ! the solution ust also be on the ?ClusterF"ulti-Cluster %evice@

(ardware Copatibility Eist& ;or additional inforation> see the following article in the "icrosoft nowledge

9ase*

30::4Support for "ultiple Clusters ttached to the Sae S) %evice

Two ass storage device controllersHSall Coputer Syste +nterface


7/50


ote:Server Clustering does not support the use of +1 addresses assigned fro %ynaic (ost

Configuration 1rotocol it could cause the cluster to fail& +t is recoended that you have a doain controller

on the sae local area networ! verify that you are using the

ost recent firware and drivers& Chec! with your networ! adapter anufacturer for cluster

copatibility&

Shared isk &e/uire0ents:

n (CE-approved eAternal dis! storage unit connected to all coputers& This will be used as the

clustered shared dis!& Soe type of a hardware redundant array of independent dis!s it enables you

to have ultiple dis! resources and to do ctiveFctive configurations and anual load balancing

across the nodes in the cluster&

dedicated dis! with a iniu si8e of 0 egabytes


8/50


ll shared dis!s ust be configured as aster boot record


9/50


Cluster Installation

Installation 3vervie

%uring the installation process> soe nodes will be shut down while others are being installed& This step

helps guarantee that data on dis!s attached to the shared bus is not lost or corrupted& This can happen

when ultiple nodes siultaneously try to write to a dis! that is not protected by the cluster software& The

default behavior of how new dis!s are ounted has been changed in Windows 2003 Server fro the

behavior in the "icrosoft# Windows# 2000 operating syste& +n Windows 2003> logical dis!s that are not

on the sae bus as the boot partition will not be autoatically ounted and assigned a drive letter& This

helps ensure that the server will not ount drives that could possibly belong to another server in a copleA

S) environent& lthough the drives will not be ounted> it is still recoended that you follow the

procedures below to be certain the shared dis!s will not becoe corrupted&

/se the table below to deterine which nodes and storage devices should be turned on during each step&

The steps in this guide are for a two-node cluster& (owever> if you are installing a cluster with ore than two

nodes> the )ode 2 colun lists the required state of all other nodes&

Ste#Node

1

Node

2Storage Comments

Setting up

networ!s,n ,n ,ff

5erify that all storage devices on the shared

bus are turned off& Turn on all nodes&

Setting up shared

dis!s,n ,ff ,n

Shutdown all nodes& Turn on the shared

storage> then turn on the first node&

5erifying dis!

configuration,ff ,n ,n

Turn on the first node> turn on second node&

'epeat for nodes 3 and : if necessary&

Configuring thefirst node

,n ,ff ,n Turn off all nodesI turn on the first node&

Configuring the

second node,n ,n ,n

Turn on the second node after the first node is

successfully configured& 'epeat for nodes 3

and : as necessary&

1ost-installation ,n ,n ,n ll nodes should be on&

Several steps ust be ta!en before configuring the Cluster service software& These steps are*

+nstalling Windows Server 2003 $nterprise $dition or Windows Server 2003 %atacenter $dition

operating syste on each node&

Setting up networ!s&

Setting up dis!s&

1erfor these steps on each cluster node before proceeding with the installation of cluster service on the

first node&

Guide to Creating and Configuring a Server Cluster in Windows Server 2003


10/50


To configure the cluster service> you ust be logged on with an account that has adinistrative perissions

to all nodes& $ach node ust be a eber of the sae doain& +f you choose to a!e one of the nodes a

doain controller> have another doain controller available on the sae subnet to eliinate a single point

of failure and enable aintenance on that node&

Installing the 4indos Server 2!! 3#erating S+ste0'efer to the docuentation you received with the Windows Server 2003 operating syste pac!age to install

the syste on each node in the cluster&

9efore configuring the cluster service> you ust be logged on locally with a doain account that is a

eber of the local adinistrators group&

ote* The installation will fail if you attept to Doin a node to a cluster that has a blan! password for the

local adinistrator account& ;or security reasons> Windows Server 2003 prohibits blan! adinistrator

passwords&

Setting # etorks

$ach cluster node requires at least two networ! adapters with two or ore independent networ!s> to avoid

a single point of failure& ,ne is to connect to a public networ!> and one is to connect to a private networ!

consisting of cluster nodes only& Servers with ultiple networ! adapters are referred to as ?ulti-hoed&@

9ecause ulti-hoed servers can be probleatic> it is critical that you follow the networ! configuration

recoendations outlined in this docuent&

"icrosoft requires that you have two 1eripheral Coponent +nterconnect (1C+= networ! adapters in each

node to be certified on the (ardware Copatibility Eist


11/50


in a two-node configuration or a dedicated dub hub in a configuration of ore than two nodes& %o not use

a switch> sart hub> or any other routing device for the heartbeat networ!&

ote* Cluster heartbeats cannot be forwarded through a routing device because their Tie to Eive then the latency between the nodes ust be less then 00 illiseconds in Windows Server

2003> heartbeats in Server Clustering have been changed to ulticastI therefore> you ay want to a!e a

"adcap server available to assign the ulticast addresses& ;or additional inforation> see the following

article in the "icrosoft nowledge 9ase*

30.2"ulticast Support $nabled for the Cluster (eartbeat

Figure 1 below outlines a four-node cluster configuration.

i&ure 1' Connections for a fournode cluster'

6eneral etork Configuration:

ote* This guide assues that you are running the default Startenu& The steps ay be slightly different if

you are running the Classic Startenu& lso> which networ! adapter is private and which is public depends

upon your wiring& ;or the purposes of this white paper> the first networ! adapter and the second networ! adapter


12/50


To rename the local area network icons

+t is recoended that you change the naes of the networ! connections for clarity& ;or eAaple> you

ight want to change the nae of ocal -rea Connection 2 to soething li!e Private& 'enaing will help

you identify a networ! and correctly assign its role&

1.Clic! Start> point to Control Panel> right-clic! etork Connections> and then clic!3#en

2.'ight-clic! the 'ocal Area Connection 2icon&

3.Clic! &ena0e&

4.Type Privatein the teAtboA> and then press $)T$'&

5.'epeat steps 4 through 3> and then renae the public networ! adapter as Public&

i&ure 2' *enamed icons in the Net#or( Connections #indo#'

6.The renaed icons should loo! li!e those in ;igure 2 above& Close the )etwor! Connections window&

The new connection naes will appear in Cluster dinistrator and autoatically replicate to all

other cluster nodes as they are brought online&

To configure the binding order networks on all nodes

1.Clic! Start> point to Control Panel> right-clic! etork Connections> and then clic!3#en

2.,n the Advancedenu> clic! Advanced Settings&

3. +n the ConnectionsboA> a!e sure that your bindings are in the following order> and then clic! 37*

a= 1ublic

b= 1rivate

c= 'eote ccess Connections

Guide to Creating and Configuring a Server Cluster in Windows Server 2003 7


13/50


Configuring the Private etork Ada#ter

1. 'ight-clic! the networ! connection for your heartbeat adapter> and then clic! Pro#erties&

2. ,n the 6eneraltab> a!e sure that only the Internet Protocol 8"CPIP chec! boA is selected> as

shown in ;igure 3 below& Clic! to clear the chec! boAes for all other clients> services> and protocols&

i&ure ' Clic( to select only the Internet Protocolchec( bo6 in the Private Properties dialo& bo6'

. +f you have a networ! adapter that is capable of transitting at ultiple speeds> you should

anually specify a speed and dupleA ode& %o not use an auto-select setting for speed>

because soe adapters ay drop pac!ets while deterining the speed& The speed for the

networ! adapters ust be hard set "icrosoft recoends you set all devices on that path to 1!0egab+tes

#er second


14/50


i&ure ;' $ettin& the speed and duple6 for all adaptors

ote* "icrosoft does not recoended that you use any type of fault-tolerant adapter or JTeaingJ for the

heartbeat& +f you require redundancy for your heartbeat connection> use ultiple networ! adapters set to

+nternal Counication ,nly and define their networ! priority in the Cluster configuration& +ssues seen with

early ulti-ported networ! adapters> verify that your firware and driver are at the ost current revision if

you use this technology&

Contact your networ! adapter anufacturer for inforation about copatibility on a server cluster& ;or

additional inforation> see the following article in the "icrosoft nowledge 9ase*

2:404)etwor! dapter Teaing and Server Clustering

(. Clic!Internet Protocol 8"CPIP> and then clic! Pro#erties&

5. ,n the 6eneraltab> verify that you have selected a static +1 address that is not on the sae

subnet or networ! as any other public networ! adapter& +t is recoended that you put the

private networ! adapter in one of the following private networ! ranges*

40&0&0&0 through 40&2&2&2


15/50


ote* ;or additional inforation about valid +1 addressing for a private networ!> see the following article in

the "icrosoft nowledge 9ase*

4:27.35alid +1 ddressing for a 1rivate )etwor!

i&ure


16/50


i&ure =' >erify that no values are defined on the ")N$ tab'

1!. When you close the dialog boA> you ay receive the following propt* ?%his connection has an

empty primary ")N$ address' o you #ant to continue?@ +f you receive this propt> clic!?es

11. Coplete steps 4 through 40 on all other nodes in the cluster with different static +1 addresses&

Configuring the Public etork Ada#ter

ote* +f +1 addresses are obtained via %(C1> access to cluster nodes ay be unavailable if the %(C1

server is inaccessible& ;or this reason> static +1 addresses are required for all interfaces on a server cluster&

eep in ind that cluster service will only recogni8e one networ! interface per subnet& +f you need

assistance with TC1F+1 addressing in Windows Server 2003> please see the ,nline (elp&

@erif+ing Connectivit+ and a0e &esolution

To verify that the private and public networ!s are counicating properly> ping all +1 addresses fro each

node& Bou should be able to ping all +1 addresses> locally and on the reote nodes&

To verify nae resolution> ping each node fro a client using the nodes achine nae instead of its +1

address& +t should only return the +1 address for the public networ!& Bou ay also want to try a PI6 a

coand to do a reverse loo!up on the +1 ddresses&

@erif+ing o0ain e0bershi#

ll nodes in the cluster ust be ebers of the sae doain and be able to access a doain controller

and a %)S server& They can be configured as eber servers or doain controllers& Bou should have at

least one doain controller on the sae networ! segent as the cluster& ;or high availability& another



17/50


doain controller should also be available to reove a single point of failure& +n this guide> all nodes are

configured as eber servers&

There are instances where the nodes ay be deployed in an environent where there are no pre-eAisting

"icrosoft# Windows )T# :&0 doain controllers or Windows Server 2003 doain controllers& This

scenario requires at least one of the cluster nodes to be configured as a doain controller& (owever> in a

two-node server cluster> if one node is a doain controller> then the other node also ust be a doain

controller& +n a four-node cluster ipleentation> it is not necessary to configure all four nodes as doain

controllers& (owever> when following a ?best practices@ odel and having at least one bac!up doain

controller> at least one of the reaining three nodes should be configured as a doain controller& cluster

node ust be prooted to a doain controller by using the %C1roo tool before the cluster service is

configured&

The dependence in Windows Server 2003 on the %)S further requires that every node that is a doain

controller also ust be a %)S server ifanother %)S server that supports dynaic updates andFor S'5

records is not available the other node ust be a doain

controller

There is overhead associated with running a doain controller& n idle doain controller can use

anywhere between 430 and 4:0 "9 of '"> which includes having the Clustering service running&

There is also increased networ! traffic fro replication> because these doain controllers have to

replicate with other doain controllers in the doain and across doains&

+f the cluster nodes are the only doain controllers> then each ust be a %)S server as well& They

should point to each other for priary %)S resolution and to theselves for secondary resolution&

The first doain controller in the forestFdoain will ta!e on all ,perations "aster 'oles& Bou can

redistribute these roles to any node& (owever> if a node fails> the ,perations "aster 'oles assued bythat node will be unavailable& Therefore> it is recoended that you do not run ,perations "aster

'oles on any cluster node& This includes Schee "aster> %oain )aing "aster> 'elative +% "aster>

1%C $ulator> and +nfrastructure "aster& These functions cannot be clustered for high availability with

failover&

Clustering other applications such as "icrosoft# S6E Server L or "icrosoft# $Achange Server in a

scenario where the nodes are also doain controllers ay not be optial due to resource constraints&

This configuration should be thoroughly tested in a lab environent before deployent

9ecause of the copleAity and overhead involved in a!ing cluster-nodes doain controllers> it is

recoended that all nodes should be eber servers&

Setting # a Cluster ser Account

The Cluster service requires a doain user account that is a eber of the Eocal dinistrators group on

each node> under which the Cluster service can run& 9ecause setup requires a user nae and password>

this user account ust be created before configuring the Cluster service& This user account should be

dedicated only to running the Cluster service> and should not belong to an individual&



18/50


19/50


5.Set the password settings to ser Cannot Change Passordand Passord ever B$#ires& Clic!

e$t;and then clic! ,inishto create this user&

ote* +f your adinistrative security policy does not allow the use of passwords that never eApire> you ust

renew the password and update the cluster service configuration on each node before password eApiration&

;or additional inforation> see the following article in the "icrosoft nowledge 9ase*

30743(ow to Change the Cluster Service ccount 1assword

6.'ight-clic! Clusterin the left pane of the ctive %irectory /sers and Coputers snap-in> and then

clic! Pro#ertieson the shortcut enu&

7.Clic! Add e0bers to a 6rou#&

8.Clic! Ad0inistrators; and then clic! 37& This gives the new user account adinistrative privileges

on this coputer&

9.6uit the ctive %irectory /sers and Coputers snap-in&

Setting u# Shared isks

4arning* To avoid corrupting the cluster dis!s> a!e sure that Windows Server 2003 and the Cluster

service are installed> configured> and running on at least one node before you start an operating syste on

another node& +t is critical to never have ore then one node on until the Cluster service is configured&

To proceed> turn off all nodes& Turn on the shared storage devices> and then turn on node 4&

About the uoru0 isk

The quoru dis! is used to store cluster configuration database chec!points and log files that help anage

the cluster and aintain consistency& The following quoru dis! procedures are recoended*

Create a logical drive with a iniu si8e of 0 "9 to be used as a quoru dis!> 00 "9 is optial for

)T;S&

%edicate a separate dis! as a quoru resource&

I0#ortant* quoru dis! failure could cause the entire cluster to failI therefore> it is strongly recoended

that you use a volue on a hardware '+% array& %o not use the quoru dis! for anything other than

cluster anageent&

The quoru resource plays a crucial role in the operation of the cluster& +n every cluster> a single resource is

designated as the quoru resource& quoru resource can be any 1hysical %is! resource with the

following functionality*

+t replicates the cluster registry to all other nodes in the server cluster& 9y default> the cluster

registry is stored in the following location on each node* A$ystem*ootAClusterClusdb& The

cluster registry is then replicated to the M$C$Ch(666'tmp file on the quoru drive& These files are

eAact copies of each other& The M$C$uolo&'lo&file is a transaction log that aintains a record of

all changes to the chec!point file& This eans that nodes that were offline can have these changes

appended when they reDoin the cluster&

http://support.microsoft.com/?id=305813http://support.microsoft.com/?id=305813http://support.microsoft.com/?id=305813


20/50


+f there is a loss of counication between cluster nodes> the challenge response protocol is

initiated to prevent a Jsplit brainJ scenario& +n this situation> the owner of the quoru dis! resource

becoes the only owner of the cluster and all the resources& The owner then a!es the resources

available for clients& When the node that owns the quoru dis! functions incorrectly> the surviving

nodes arbitrate to ta!e ownership of the device& ;or additional inforation> see the following article

in the "icrosoft nowledge 9ase*

3047.(ow the Cluster Service Ta!es ,wnership of a %is! on the Shared 9us

%uring the cluster service installation> you ust provide the drive letter for the quoru dis!& The letter is

coonly used as a standard> and 6 is used in the eAaple&

To configure shared disks

1."a!e sure that only one node is turned on&

2.'ight clic! + Co0#uter> clic! anage> and then eApand Storage&

3.%ouble-clic! isk anage0ent&

4. +f you connect a new drive> then it autoatically starts the Write Signature and /pgrade %is! Wi8ard&

+f this happens> clic! e$tto step through the wi8ard&

ote* The wi8ard autoatically sets the dis! to dynaic& To reset the dis! to basic> right-clic! isk n and then clic! &evert to >asic isk&

5. 'ight-clic! unallocated disk s#ace&

6. Clic! e Partition&

7. The )ew 1artition Wi8ard begins& Clic! e$t&

8. Select the Pri0ar+ Partition partition type& Clic! e$t&

9. The default is set to aAiu si8e for the partition si8e& Clic! e$t& do not assign a drive letter to the dis!& ;or

additional inforation> see the following article in the "icrosoft nowledge 9ase*

2702(ow to Configure 5olue "ount 1oints on a Clustered Server

11. ;orat the partition using )T;S& +n the @olu0e 'abel boA> type a nae for the dis!& ;or eAaple>

rive > as shown in ;igure 7 below& +t is critical to assign drive labels for shared dis!s> because

this can draatically reduce troubleshooting tie in the event of a dis! recovery situation&

Guide to Creating and Configuring a Server Cluster in Windows Server 2003 4.
http://support.microsoft.com/?id=309186http://support.microsoft.com/?id=309186http://support.microsoft.com/?id=318534http://support.microsoft.com/?id=318534http://support.microsoft.com/?id=280297http://support.microsoft.com/?id=280297http://support.microsoft.com/?id=309186http://support.microsoft.com/?id=318534http://support.microsoft.com/?id=280297


21/50


i&ure D' )t is critical to assi&n drive labels for shared dis(s'

+f you are installing a .:-bit version of Windows Server 2003> verify that all dis!s are foratted as "9'&

Global 1artition Table see the

following article in the "icrosoft nowledge 9ase*

27:43:Server Clusters %o )ot Support G1T Shared %is!s

5erify that all shared dis!s are foratted as )T;S and designated as "9' 9asic&



22/50


To verify disk access and functionality

1.Start Windows $Aplorer&

2.'ight-clic! one of the shared dis!s clic! e;and then clic! "e$t ocu0ent&

3.

5erify that you can successfully write to the dis! and that the file was created&

4.Select the file> and then press the el!ey to delete it fro the clustered dis!&

5.'epeat steps 4 through : for all clustered dis!s to verify they can be correctly accessed fro the first

node&

6.Turn off the first node> turn on the second node> and repeat steps 4 through : to verify dis! access and

functionality& ssign drive letters to atch the corresponding drive labels& 'epeat again for any

additional nodes& 5erify that all nodes can read and write fro the dis!s> turn off all nodes eAcept the

first one> and then continue with this white paper&



23/50


Configuring the Cluster Service

Bou ust supply all initial cluster configuration inforation in the first installation phase& This is

accoplished using the Cluster Configuration Wi8ard&

s seen in the flow chart> the for Credential Eogin> naly8e> and 'e-naly8e and

Start Service are the sae& There are inor differences in the following pages* Welcoe> Select Coputer>

and Cluster Service ccount& +n the neAt two sections of this lesson> you will step through the wi8ard pages

presented on each of these configuration paths& +n the third section> after you follow the step-through

sections> this white paper describes in detail the naly8e> >'e-naly8e and Start Service pages> and what

the inforation provided in these screens eans&



24/50


ote* %uring Cluster service configuration on node 4> you ust turn off all other nodes& ll shared storage

devices should be turned on&

To configure the first node1.Clic! Start> clic! AllProgra0s> clic! Ad0inistrative "ools> and then clic! Cluster Ad0inistrator&

2.When propted by the ,pen Connection to Cluster Wi8ard> clic! Create ne clusterin the Action

drop-down list> as shown in ;igure below&

i&ure ' %heActiondropdo#n list'

3.5erify that you have the necessary prerequisites to configure the cluster> as shown in ;igure 40

below& Clic! e$t&

i&ure 10' - list of prereFuisites is part of the Ne# $erver Cluster "iGard "elcome pa&e'



25/50


4.Type a unique )et9+,S nae for the cluster and then clic! e$t& +n the

eAaple shown in ;igure 44 below> the cluster is naed +Cluster&=dherence to %)S naing

rules is recoended& ;or additional inforation> see the following articles in the "icrosoft

nowledge 9ase*

4.3:0)et9+,S SuffiAes


26/50


i&ure 12' %he Ne# $erver Cluster "iGard prompts you to specify an account'

6.9ecause it is possible to configure clusters reotely> you ust verify or type the nae of the server

that is going to be used as the first node to create the cluster> as shown in ;igure 43 below& Clic!

e$t&

i&ure 1' $elect the name of the computer that #ill be the first node in the cluster'



27/50


ote* The +nstall wi8ard verifies that all nodes can see the shared dis!s the sae& +n a copleA storage

area networ! the target identifiers and the Setup progra

ay incorrectly detect that the dis! configuration is not valid for Setup& To wor! around this issue you can

clic! the Advancedbutton> and then clic!Advanced 80ini0u0 configuration& ;or additional

inforation> see the following article in the "icrosoft nowledge 9ase*

334704Cluster Setup "ay )ot Wor! When Bou dd )odes

7.;igure 4: below illustrates that the Setup process will now analy8e the node for possible hardware or

software probles that ay cause probles with the installation& 'eview any warnings or error

essages& Bou can also clic! the etailsbutton to get detailed inforation about each one&

i&ure 1;' %he $etup process analyGes the node for possible hard#are or soft#are problems'



28/50


8.Type the unique cluster +1 address and then clic! e$t&

s shown in ;igure 4 below> the )ew Server Cluster Wi8ard autoatically associates the cluster +1

address with one of the public networ!s by using the subnet as! to select the correct networ!& The cluster

+1 address should be used for adinistrative purposes only> and not for client connections&

i&ure 1 and then clic! e$t&

t this point> the Cluster ConfigurationWi8ard validates the user account and password&

Guide to Creating and Configuring a Server Cluster in Windows Server 2003 2:


29/50


i&ure 1=' %he #iGard prompts you to provide the account that #as created durin& preinstallation'

10. 'eview the Su00ar+page> shown in ;igure 4 below> to verify that all the inforation that is about

to be used to create the cluster is correct& +f desired> you can use the quoru button to change the

quoru dis! designation fro the default auto-selected dis!&

The suary inforation displayed on this screen can be used to reconfigure the cluster in the event of

a disaster recovery situation& +t is recoended that you save and print a hard copy to !eep with the

change anageent log at the server&

ote* The uoru0button can also be used to specify a "aDority )ode Set


30/50


i&ure 1@' %he Proposed Cluster Confi&uration pa&e'

11. 'eview any warnings or errors encountered during cluster creation& To do this> clic! the plus signs

to see ore> and then clic! e$t& Warnings and errors appear in the Creating the Cluster page as

shown in ;igure 47&

i&ure 1D' "arnin&s and errors appear on the Creatin& the Cluster pa&e'



31/50


12. Clic! ,inishto coplete the installation& ;igure 4 below illustrates the final step&

i&ure 1' %he final step in settin& up a ne# server cluster'

ote* To view a detailed suary> clic! the@ie 'ogbutton or view the teAt file stored in the following

location*

%SystemRoot%\System32\LogFiles\Cluster\ClCfgSrv.Log

@alidating the Cluster Installation

/se the Cluster dinistrator clic! Progra0s> clic! Ad0inistrative "ools> and then clic! Cluster Ad0inistrator&

2.5erify that all resources cae online successfully> as shown in ;igure 20 below&



32/50


i&ure 20' %he Cluster -dminister verifies that all resources came online successfully'

otes general rules> do not put anything in the cluster group> do not ta!e anything out of the cluster

group> and do not use anything in the cluster group for anything other than cluster adinistration&

Configuring the Second ode

+nstalling the cluster service on the other nodes requires less tie than on the first node& Setup configures

the cluster service networ! settings on the second node based on the configuration of the first node& Bou

can also add ultiple nodes to the cluster at the sae tie> and reotely&

ote* ;or this section> leave node 4 and all shared dis!s turned on& Then turn on all other nodes& The

cluster service will control access to the shared dis!s at this point to eliinate any chance of corrupting thevolue&

1.,pen Cluster Ad0inistratoron )ode 4&

2.Clic! ,ile> clic! e> and then clic! ode&

3.The dd Cluster Coputers Wi8ard will start& Clic! e$t&

4. +f you are not logged on with appropriate credentials> you will be as!ed to specify a doain account

that has adinistrative rights over all nodes in the cluster&

5.$nter the achine nae for the node you want to add to the cluster& Clic! Add& 'epeat this step>

shown in ;igure 24 below> to add all other nodes that you want& When you have added all nodes>clic! e$t&



33/50


i&ure 21' -ddin& nodes to the cluster'

6.The Setup wi8ard will perfor an analysis of all the nodes to verify that they are configured properly&

7.Type the password for the account used to start the cluster service&

8.'eview the suary inforation that is displayed for accuracy& The suary inforation will be

used to configure the other nodes when they Doin the cluster&

9.'eview any warnings or errors encountered during cluster creation> and then clic! e$t&

10. Clic! ,inishto coplete the installation&



34/50


35/50


i&ure 22' 3sin& Cluster -dministrator to confi&ure the heartbeat'

4.Clic! 37&

5.'ight-clic! Public; and then clic!Pro#erties and then clic! 37&

i&ure 2' %he Public Properties dialo& bo6'



36/50


*eartbeat Ada#ter PrioritiEation

fter configuring the role of how the cluster service will use the networ! adapters> the neAt step is to

prioriti8e the order in which they will be used for intra-cluster counication& This is applicable only if two or

ore networ!s were configured for node-to-node counication& 1riority arrows on the right side of thescreen specify the order in which the cluster service will use the networ! adapters for counication

between nodes& The cluster service always attepts to use the first networ! adapter listed for reote

procedure call and will be clustered& Therefore> if the node has ultiple buses> soe dis!s

ay be listed that will not be used as shared storage> for eAaple> an internal SCS+ drive& Such dis!s



37/50


should be reoved fro the cluster configuration& +f you plan to ipleent 5olue "ount points for soe

dis!s> you ay want to delete the current dis! resources for those dis!s> delete the drive letters> and then

create a new dis! resource without a drive letter assignent&

uoru0 isk Configuration

The Cluster Configuration Wi8ard autoatically selects the drive that is to be used as the quoru device& +t

will use the sallest partition that is larger then 0 "9& Bou ay want to change the autoatically selected

dis! to a dedicated dis! that you have designated for use as the quoru&

To configure the quorum disk

1.Start Cluster dinistrator


38/50


Creating a >oot ela+

+n a situation where all the cluster nodes boot up and attept to attach to the quoru resource at the sae

tie> the Cluster service ay fail to start& ;or eAaple> this ay occur when power is restored to all nodes

at the eAact sae tie after a power failure& To avoid such a situation> increase or decrease the "i0e to

is#la+ list of o#erating s+ste0ssetting& To find this setting> clic! Start> point to + Co0#uter> right-

clic! + Co0#uter> and then clic! Pro#erties& Clic! the Advancedtab> and then clic! SettingsunderStartu# And &ecover+&

Guide to Creating and Configuring a Server Cluster in Windows Server 2003 3:


39/50


"est Installation

There are several ethods for verifying a cluster service installation after the Setup process is coplete&

These include*

Cluster Ad0inistrator:+f installation was copleted only on node 4> start Cluster dinistrator> and

then attept to connect to the cluster& +f a second node was installed> start Cluster dinistrator on

either node> connect to the cluster> and then verify that the second node is listed&

Services A##let:/se the services snap-in to verify that the cluster service is listed and started&

Bvent 'og:/se the $vent 5iewer to chec! for ClusSvcentries in the syste log& Bou should see

entries confiring that the cluster service successfully fored or Doined a cluster&

Cluster service registr+ entries:5erify that the cluster service installation process wrote the correct

entries to the registry& Bou can find any of the registry settings under HKEY_LOCAL_ACH!"E\Cluster

Clic! Start> clic! &un> and then type the 5irtual Server nae& 5erify that you can connect and see

resources&

"est ,ailover

To verify that resources will failover

1.Clic! Start> clic! Progra0s> clic! Ad0inistrative "ools> and then clic! Cluster Ad0inistrator> as

shown in ;igure 2. below&

i&ure 2=' %he Cluster -dministrator #indo#'

2.'ight-clic! the isk 6rou# 1 group> and then clic! ove 6rou#& The group and all its resources will

be oved to another node& fter a short period of tie> the isk ,: 6:will be brought online on the

second node& Watch the window to see this shift& 6uit Cluster dinistrator&



40/50


CongratulationsO Bou have copleted the configuration of the cluster service on all nodes& The server

cluster is fully operational& Bou are now ready to install cluster resources such as file shares> printer

spoolers> cluster aware services li!e %istributed Transaction Coordinator> %(C1> W+)S> or cluster-aware

progras such as $Achange Server or S6E Server&



41/50


A##endi$

Advanced "esting

)ow that you have configured your cluster and verified basic functionality and failover> you ay want to

conduct a series of failure scenario tests that will deonstrate eApected results and ensure the cluster will

respond correctly when a failure occurs& This level of testing is not required for every ipleentation> but

ay be insightful if you are new to clustering technology and are unfailiar how the cluster will respond or if

you are ipleenting a new hardware platfor in your environent& The eApected results listed are for a

clean configuration of the cluster with default settings> this does not ta!e into consideration any user

custoi8ation of the failover logic& This is not a coplete list of all tests> nor should successfully copleting

these tests be considered ?certified@ or ready for production& This is siply a saple list of soe tests that

can be conducted& ;or additional inforation> see the following article in the "icrosoft nowledge 9ase*

40:;ailoverF;ailbac! 1olicies on "icrosoft Cluster Server

Test: Start Cluster dinistrator> right-clic! a resource> and then clic! ?Initiate ,ailure@& The resource

should go into an failed state> and then it will be restarted and brought bac! into an online state on that

node&

E6pected *esult: 'esources should coe bac! online on the sae node

Test: Conduct the above ?Initiate ,ailure@ test three ore ties on that sae resource& ,n the fourth

failure> the resources should all failover to another node in the cluster&

E6pected *esult: 'esources should failover to another node in the cluster

Test: "ove all resources to one node& Start Coputer "anageent> and then clic! Servicesunder

Services and A##lications& Stop the Cluster service& Start Cluster dinistrator on another node and

verify that all resources failover and coe online on another node correctly&


Test: "ove all resources to one node& ,n that node> clic! Start;and then clic! Shutdon& This will

turn off that node& Start Cluster dinistrator on another node> and then verify that all resources

failover and coe online on another node correctly&


Test: "ove all resources to one node> and then press the power button on the front of that server to

turn it off& +f you have an C1+ copliant server> the server will perfor an ?$ergency Shutdown@ and

turn off the server& Start Cluster dinistrator on another node and verify that all resources failover and

coe online on another node correctly& ;or additional inforation about an $ergency Shutdown> see

the following articles in the "icrosoft nowledge 9ase*

323:3(,W T,* 1erfor an $ergency Shutdown in Windows Server 2003

2401ower 9utton on C1+ Coputer "ay ;orce an $ergency Shutdown


4arning* 1erforing the $ergency Shutdown test ay cause data corruption and data loss& %o not

conduct this test on a production server



42/50


Test: "ove all resources to one node> and then pull the power cables fro that server to siulate a

hard failure& Start Cluster dinistrator on another node> and then verify that all resources failover and

coe online on another node correctly


4arning* 1erforing the hard failure test ay cause data corruption and data loss& This is an eAtree test&"a!e sure you have a bac!up of all critical data> and then conduct the test at your own ris!& %o notconduct

this test on a production server

Test: "ove all resources to one node> and then reove the public networ! cable fro that node& The

+1 ddress resources should fail> and the groups will all failover to another node in the cluster& ;or

additional inforation > see the following articles in the "icrosoft nowledge 9ase*

27.3:2)etwor! ;ailure %etection and 'ecovery in Windows Server 2003 Clusters


Test: 'eove the networ! cable for the 1rivate heartbeat networ!& The heartbeat traffic will failover to

the public networ!> and no failover should occur& +f failover occurs> please see the ?Configuring the1rivate )etwor! daptor@ section in earlier in this docuent

E6pected *esult: There should be no failures or resource failovers

SCSI rive Installations

This appendiA is provided as a generic set of instructions for SCS+ drive installations& +f the SCS+ hard dis!

vendors instructions conflict with the instructions here> always follow the instructions supplied by the

vendor&

The SCS+ bus listed in the hardware requireents ust be configured prior to cluster service installation&

Configuration applies to*

The SCS+ devices&

The SCS+ controllers and the hard dis!s so that they wor! properly on a shared SCS+ bus&

1roperly terinating the bus& The shared SCS+ bus ust have a terinator at each end of the bus& +t is

possible to have ultiple shared SCS+ buses between the nodes of a cluster&

+n addition to the inforation on the following pages> refer to docuentation fro the anufacturer of your

SCS+ device or to the SCS+ specifications> which can be ordered fro the erican )ational Standards

+nstitute configuring the shared SCS+ bus includes changing the SCS+ +% nuber on

one controller to a different nuber> such as SCS+ +% .& +f there is ore than one dis! that will be on the

shared SCS+ bus> each dis! ust have a unique SCS+ +% nuber&

"er0inating the Shared SCSI >us

There are several ethods for terinating the shared SCS+ bus& They include*

SCSI controllers

http://support.microsoft.com/?id=286342http://support.microsoft.com/?id=286342http://www.ansi.org/http://support.microsoft.com/?id=286342http://www.ansi.org/


43/50


SCS+ controllers have internal soft terination that can be used to terinate the bus> however this ethod

is not recoended with the cluster server& +f a node is turned off with this configuration> the SCS+ bus will

be terinated iproperly and will not operate correctly&

Storage enclosures

Storage enclosures also have internal terination> which can be used to terinate the SCS+ bus if theenclosure is at the end of the SCS+ bus& This should be turned off&

? cables

B cables can be connected to devices if the device is at the end of the SCS+ bus& n eAternal active

terinator can then be attached to one branch of the B cable in order to terinate the SCS+ bus& This

ethod of terination requires either disabling or reoving any internal terinators that the device ay

have&

;igure 2 outlines how a SCS+ cluster should be physically connected&

i&ure 2@' - dia&ram of a $C$) cluster hard#are confi&uration'



44/50


ote:ny devices that are not at the end of the shared bus ust have their internal terination disabled& B

cables and active terinator connectors are the recoended terination ethods because they will

provide terination even when a node is not online&

Storage Area etork Considerations

There are two supported ethods of ;ibre Channel-based storage in a Windows Server 2003 server

cluster* arbitrated loops and switched fabric&

I0#ortant* When evaluating both types of ;ibre Channel ipleentation> read the vendors docuentation

and be sure you understand the specific features and restrictions of each&

lthough the ter ibre Channeliplies the use of fiber-optic technology> copper coaAial cable is also

allowed for interconnects&

Arbitrated 'oo#s 8,C-A'

;ibre Channel arbitrated loop a aAiu

of two nodes is supported in an ;C-E server cluster configured with a hub& n ;C-E is illustrated in

;igure&

Figure Error# Refere$e soure $ot fou$&.' FC(AL Co$$etio$

;C-Es provide a solution for two nodes and a sall nuber of devices in relatively static configurations& ll

devices on the loop share the edia> and any pac!et traveling fro one device to another ust pass

through all interediate devices&

+f your high-availability needs can be et with a two-node server cluster> an ;C-E deployent has several

advantages*

The cost is relatively low&

Eoops can be eApanded to add storage


45/50


The disadvantage is that loops can be difficult to deploy in an organi8ation& 9ecause every device on the

loop shares the edia> overall bandwidth in the cluster is lowered& Soe organi8ations ight also be

unduly restricted by the 42.-device liit&

Sitched ,abric 8,C-S4

;or any cluster larger than two nodes> a switched ;ibre Channel switched fabric devices are connected in a any-to-any topology using

;ibre Channel switches


46/50


ote* 5endors that provide S) fabric coponents and software anageent tools have a wide range of

tools for setting up> configuring> onitoring> and anaging the S) fabric& Contact your S) vendor for

details about your particular S) solution&

SCSI &esets

$arlier versions of Windows server clusters presued that all counications to the shared dis! should be

treated as an isolated SCS+ bus& This behavior ay be soewhat disruptive> and it does not ta!e

advantage of the ore advanced features of ;ibre Channel to both iprove arbitration perforance and

reduce disruption&

,ne !ey enhanceent in Windows Server 2003 is that the Cluster service issues a coand to brea! a

'$S$'5T+,)> and the Stor1ort driver can do a targeted or device reset for dis!s that are on a ;ibre

Channel topology& +n Windows 2000 server clusters> an entire bus-wide SCS+ '$S$T is issued& This causes

all devices on the bus to be disconnected& When a SCS+ '$S$T is issued> a lot of tie is spent resetting

devices that ay not need to be reset> such as dis!s that the C(EE$)G$' node ay already own&

'esets in Windows 2003 occur in the following order*

4& Targeted logical unit nuber


47/50


H!s

(ost bus adapters siilar to the way

that a networ! adapter connects a server to a typical $thernet networ!& (9s> however> are ore difficult to

configure than networ! adapters or storage entity> it

is iportant to control which hosts have access to specific devices& Poning allows adinistrators to partition

devices in logical volues and thereby reserve the devices in a volue for a server cluster& That eans

that all interactions between cluster nodes and devices in the logical storage volues are isolated within the

boundaries of the 8oneI other noncluster ebers of the S) are not affected by cluster activity&

;igure $rror* 'eference source not found&3is a logical depiction of two S) 8ones

each containing a storage controller respectively=&

Figure Error# Refere$e soure $ot fou$&.3 +o$i$g

+n this ipleentation> )ode and )ode 9 can access data fro the storage controller S4> but )ode C

cannot& )ode C can access data fro storage controller S2&

Poning needs to be ipleented at the hardware level because

Guide to Creating and Configuring a Server Cluster in Windows Server 2003 :3


48/50


unauthori8ed servers cannot access devices inside the 8one so a host adapter cannot gain access to a device for which it has not been

configured=& With software 8oning> the cluster would be left unsecured if the software coponent failed&

+n addition to providing cluster security> 8oning also liits the traffic flow within a given S) environent&

Traffic between ports is routed only to segents of the fabric that are in the sae 8one&

!N "asking

E/) is a logical dis! defined within a S)& Server clusters see E/)s and thin! they are physical dis!s&

E/) as!ing> perfored at the controller level> allows you to define relationships between E/)s and

cluster nodes& Storage controllers usually provide the eans for creating E/)-level access controls that

allow access to a given E/) to one or ore hosts& 9y providing this access control at the storage controller>

the controller itself can enforce access policies to the devices&

E/) as!ing provides ore granular security than 8oning> because E/)s provide a eans for 8oning at

the port level& ;or eAaple> any S) switches allow overlapping 8ones> which enable a storage controller

to reside in ultiple 8ones& "ultiple clusters in ultiple 8ones can share the data on those controllers&

;igure $rror* 'eference source not found&:illustrates such a scenario&Figure Error# Refere$e soure $ot fou$&., Stor-ge Co$troller i$ ultile +o$es

E/)s used by Cluster can be as!ed> or hidden> fro Cluster 9 so that only authori8ed users can access

data on a shared storage controller&

&equirements for 'eploying S!Ns with (indows Server 2))* Clusters

The following list highlights the deployent requireents you need to follow when using a S) storage

solution with your server cluster& ;or a white paper that provides ore coplete inforation about using

S)s with server clusters> see the Windows Clustering* Storage rea )etwor!s lin! on the Web 'esources

pageat http*FFwww&icrosoft&coFwindowsFres!itsFwebresources&

Guide to Creating and Configuring a Server Cluster in Windows Server 2003 ::


49/50


$ach cluster on a S) ust be deployed in its own 8one& The echanis the cluster uses to protect

access to the dis!s can have an adverse effect on other clusters that are in the sae 8one& 9y using 8oning

to separate the cluster traffic fro other cluster or noncluster traffic> there is no chance of interference&

ll (9s in a single cluster ust be the sae type and have the sae firware version& "any storage and

switch vendors require that all (9s on the sae 8oneHand> in soe cases> the sae fabricHshare these

characteristics&

ll storage device drivers and (9 device drivers in a cluster ust have the sae software version&

)ever allow ultiple nodes access to the sae storage devices unless they are in the sae cluster&

)ever put tape devices into the sae 8one as cluster dis! storage devices& tape device could isinterpret

a bus rest and rewind at inappropriate ties> such as during a large bac!up&

+uidelines for 'eploying S!Ns with (indows Server 2))* Server Clusters

+n addition to the S) requireents discussed in the previous section> the following practices are highly

recoended for server cluster deployent*

+n a highly available storage fabric> you need to deploy clustered servers with ultiple (9s& +n thesecases> always load the ultipath driver software& +f the +F, subsyste sees two (9s> it assues they are

different buses and enuerates all the devices as though they were different devices on each bus& The

host> eanwhile> is seeing ultiple paths to the sae dis!s& ;ailure to load the ultipath driver will disable

the second device because the operating syste sees what it thin!s are two independent dis!s with the

sae signature&

%o not eApose a hardware snapshot of a clustered dis! bac! to a node in the sae cluster& (ardware

snapshots ust go to a server outside the server cluster& "any controllers provide snapshots at the

controller level that can be eAposed to the cluster as a copletely separate E/)& Cluster perforance is

degraded when ultiple devices have the sae signature& +f the snapshot is eAposed bac! to the node with

the original dis! online> the +F, subsyste attepts to rewrite the signature& (owever> if the snapshot is

eAposed to another node in the cluster> the Cluster service does not recogni8e it as a different dis! and the

result could be data corruption& lthough this is not specifically a S) issue> the controllers that provide this

functionality are typically deployed in a S) environent&

;or additional inforation> see the following articles in the "icrosoft nowledge 9ase*

304.:Cluster Service +proveents for Storage rea )etwor!s

30::4Support for "ultiple Clusters ttached to the Sae S) %evice

270:3Windows Clustering and Geographically Separate Sites

Guide to Creating and Configuring a Server Cluster in Windows Server 2003 :


50/50


&elated 'inks

See the following resources for further inforation*

"icrosoft Cluster Service +nstallation 'esources

at http*FFsupport&icrosoft&coFQidR22.

6uoru %rive Configuration +nforation

at http*FFsupport&icrosoft&coFQidR2703:

'ecoended 1rivate J(eartbeatJ Configuration on Cluster Server

at http*FFsupport&icrosoft&coFQidR270

)etwor! ;ailure %etection and 'ecovery in a Server Cluster

at http*FFsupport&icrosoft&coFQidR2:2.00

(ow to Change 6uoru %is! %esignation

at http*FFsupport&icrosoft&coFQidR27033

"icrosoft Windows Clustering* Storage rea )etwor!s

at http*FFwww&icrosoft&coFwindows&netserverFtechinfoFoverviewFsan&spA

Geographically %ispersed Clusters in Windows Server 2003

at http*FFwww&icrosoft&coFwindows&netserverFtechinfoFoverviewFclustergeo&spA

Server Cluster )etwor! 'equireents and 9est 1ractices

at http*FFwww&icrosoft&coFtechnetFtreeviewFdefault&aspQ

urlRFtechnetFprodtechnolFwindowsserver2003FaintainFoperateFclstntbp&asp

;or the latest inforation about Windows Server 2003> see the Windows 2003 Server Web site at

http*FFwww&icrosoft&coFwindowsserver2003Fdefault&spA
http://support.microsoft.com/?id=259267http://support.microsoft.com/?id=280345http://support.microsoft.com/?id=258750http://support.microsoft.com/?id=242600http://support.microsoft.com/?id=280353http://www.microsoft.com/windows.netserver/techinfo/overview/san.mspxhttp://www.microsoft.com/windows.netserver/techinfo/overview/clustergeo.mspxhttp://www.microsoft.com/windowsserver2003/default.mspxhttp://support.microsoft.com/?id=259267http://support.microsoft.com/?id=280345http://support.microsoft.com/?id=258750http://support.microsoft.com/?id=242600http://support.microsoft.com/?id=280353http://www.microsoft.com/windows.netserver/techinfo/overview/san.mspxhttp://www.microsoft.com/windows.netserver/techinfo/overview/clustergeo.mspxhttp://www.microsoft.com/windowsserver2003/default.mspx

cluster configuration w2k3

Documents