1

2
3
4
5
Public network: An organizational network connected to one or more cluster
nodes. This is often a preexisting Ethernet network, which most users log onto
to perform their work. If there is no dedicated private network in the cluster,
then all intra-cluster management and deployment traffic is carried on the
public network which affects the performance of the cluster.

Private network: A dedicated cluster network that carries intra-cluster

communication between nodes. This network carries management,
deployment, and MPI traffic (if no MPI network exists) between nodes in the
cluster.

MPI network: A dedicated high-speed network that carries parallel application

communication between compute nodes in a cluster. If no MPI network exists,
then MPI communication is carried by the private network. If a private network
does not exist, MPI traffic is carried by the external public network.

6
In this case the head node has two network interfaces. One interface is
connected to the existing public network and the other interface is connected
to a private cluster network that connects the head node to the compute
nodes. The private network carries all communication between the head node
and compute nodes, including deployment, management, and MPI traffic.

Here, only the head node has a public network interface; all traffic between the
compute cluster and the public network flows through the head node. Users on
the public network can access only the head node.

Windows Compute Cluster Server uses Internet Connection Sharing (ICS) to

provide Network Address Translation (NAT) between the private and public
networks, as well as DHCP and DNS services to the private network.

Services Configuration
Internet Connection Sharing : If Configure Network Address Translation
using Internet Connection Sharing (ICS) is selected during the installation,
the private network of the head node is assigned a static IP address. The ICS
hotfix must be installed on the head node.

DHCP : The public interface of the head node can be assigned a static IP
address or it can obtain an IP address from DHCP servers on the public
network. 7
In this case, both the head node and all compute nodes have two network
interface cards. Communications between nodes, including deployment,
management, and MPI traffic, are all carried on the private network, but the
public network is attached to each compute node as well as the head node.

Each node of the compute cluster will obtain an IP address from DHCP
servers on the public network. This arrangement increases accessibility from
the public network.

Services Configuration
Internet Connection Sharing : In this case, Configure Network Address
Translation using Internet Connection Sharing (ICS) check box is optional.
If the head node has ICS enabled, the compute nodes of the cluster can obtain
IP addresses for their private network. The ICS hotfix must be installed for ICS
network address translation to be enabled. If the ICS is not enabled on the
head node, then ICS can be enabled on the public network. In either case, ICS
allows the compute nodes on the private network to access resources on the
public network.

DHCP : If ICS is enabled during Compute Cluster Pack installation on the

head node, the private interface of the head node is assigned a static IP
address. When ICS is not enabled on the head node ,and Remote Installation
Services is used to install nodes, DHCP should be configured on the private
network so that compute nodes can get IP addresses dynamically when they 8
Here the public network is attached only to the head node, which acts as a
gateway between the compute nodes on the private network and resources
and users on the public network. The second network is the MPI network is
used to isolate the MPI traffic.

Services Configuration
Internet Connection Sharing : If Configure Network Address Translation
using Internet Connection Sharing (ICS) is selected, the private interface of the
head node is assigned a static IP address. The ICS hotfix must be installed for
network address translation to be enabled.

DHCP : ICS on the head node provides limited DHCP and DNS services to
compute nodes on the private network. The head node can obtain an IP
address on the public network from DHCP servers on the public network or
can be assigned a static address.

DNS : Compute nodes obtain DNS services from the head node which is
running ICS. The public interface of the head node registers with DNS servers
on the public network.

9
In t
h i
s c
ase,allthen odes ha v
e 3 NIC ’
s .As al
lthe n ode s ar
e d i
re ct
ly conn ect
edt
o the p ub l
ic
network, users can access the cluster resources directly. The intracluster communication i.e.
node management and monitoring is done through the private network and the MPI
communications by the dedicated MPI network. This case is an ideal case for a compute
cluste.

Services Configuration
Internet Connection Sharing : Enabling Configure Network Address Translation using
Internet Connection Sharing is optional in this case. If the head node has ICS NAT enabled,
the compute nodes of the cluster can obtain dynamic IP addresses for their private network
interfaces. If ICS is not enabled on the head node, then ICS can be enabled on the public
network. In any case ICS allows the compute nodes on the private network to access
resources on the public network.

DHCP : If Internet Connection Sharing is enabled, the private interface of the head node is
assigned a static IP address. If Internet Connection Sharing is not enabled and Remote
Installation Services is used to install nodes, DHCP should be configured on the private
network so that compute nodes can get dynamic IP addresses when rebooted for RIS image
installation. As all the nodes are connected to the public network, the DHCP servers on the
public network can also be used to get IP addresses on the compute nodes.

DNS : As all the public interfaces receive IP addresses from public DHCP servers they register
with DNS servers on the public network.

10
No private intra-cluster network. All traffic, including intra-cluster, MPI, and
public traffic, is carried over the public network. This maximizes accessibility,
but degrades the network performance. This case works well for debugging
applications running on the cluster, as all the compute nodes are directly
connected to the public network.

SERVICES CONFIGURATION
Internet Connection Sharing : ICS is not required.
DHCP : As all the nodes are attached to a public network, DHCP servers on
the public network can be used to provide dynamic IP addresses to the cluster
nodes.
DNS : DNS servers are used from the public network only.

11
12
13
14
15
16
In this lesson one will be able to learn about setting up a cluster based on
Windows Compute Cluster Server which includes installation and configuration
of the Head node and Compute node.
The key focus on this lesson would be

Steps involved in configuration of the head node

Setting up the network

Active Directory Installation

Configuring DHCP

Setting up a file share

Installing Compute Cluster Pack


Steps involved in configuration of the compute node

Setting up the network

Adding to the Domain controller

Installing Compute Cluster Pack

17
18
Setting up the network includes giving a static IP address to the network
interfaces.

For giving a static IP address to a network interface,


Right click on My Network Places

Right click on Local Area Connection

Select Internet Protocol (TCP/IP)

19

Select Use the Following IP address

Give a static IP to the interface e.g. 192.168.1.3

Give the Subnet mask e.g. 255.255.255.0

Default Gateway e.g. 192.168.1.5

Preferred DNS server.

Click Ok to save the settings.

20
Windows Compute Cluster Server uses Active Directory for the authentication
and authorization. Before installing the head node, there must be a Domain
Controller to which the cluster is joined.

To set up a domain controller:


Go to Start Menu -> Run

Type dcpromo.exe and press enter
One will get the Active Directory installation wizard

21
This is Active Directory installation wizard i.e. making the server as a domain
controller
Click Next to continue

22
This screen checks the Operating System compatibility

Domain controllers running Windows Server 2003 implement security settings

that require clients and other servers to communicate with those domain
controllers in a more secure way.
Some older versions of Windows, including Windows 95 and Windows NT 4.0
SP# or earlier, do not meet these requirements. In the same way non windows
systems, including Apple Mac OS X and SAMBA clients might not meet theses
requirements.

Click Next to continue

23
Domain Controller Type
Specify the role One wants this server to have. It might be either Domain
controller for a new domain or Additional domain controller for the existing
domain

Select Domain controller for new domain

Click next to continue

24
Create New Domain
Select which type of domain to create
It can be either :
1)Domain in a new forest –
If one wants the new domain to be completely
independent.
2)Child domain in an existing domain tree –
If you want new domain to be a
child of existing domain.
3)Domain tree in an existing forest –
I
fy
ou
do
n
’t
w
an
tt
h
en
ew
do
ma
i
nt
ob
e
child of an existing domain.

Click Next to continue

25
Install or Configure DNS
You can install or configure DNS on this computer

If you do not have a DNS in your network and you want this server to be the
DNS, select
No, just install and configure DNS on this computer else
Yes, I will configure the DNS client

Click Next to continue

26
New Domain name.
Specify the name for your new domain.

It should be full DNS name. e.g. cluster.com

Click Next to continue.

27
Database and log folders.
Specify that contains Active Directory database and log file.s

Click Next to continue.

28
Shared system volume
Specify the folder to be shared as the system volume.

T
h
is
f
ol
d
er
s
ha
r
es
t
he
se
r
ve
r
sc
op
y
of
do
ma
i
n’
s
pu
b
li
c
f
il
e
s.
This folder must be located on the NTFS volume.

Click Next to continue.

29
Permissions
Select default permissions of user and group objects.
For better security select Permissions compatible only with Windows 2000 or
Windows 2003 operating systems as only authenticated users can read the
information on this domain

Click next to continue

30
Directory services Restore mode administrator password
This password is used when you start the computer in Directory Services
Restore Mode

Click next to continue

31
Summary
Review and confirm the inputs given
To change any input click Back

Click Next to continue

32
This screen shows the starting on the Active Directory installation

This may take several minutes

At any point to cancel the installation, Click cancel

33
DNS Installation
If you had selected the option to install DNS on this computer, it will ask for the
original operating system CD-Rom.

Insert the CD-ROM and click OK.

34
DNS Configuration

This will configure DNS on this computer

To cancel the DNS configuration, Click Skip DNS Installation

35
Completing Active Directory installation wizard
Click Finish to complete the installation

36
Restart Windows
Windows needs a restart to take the changes made by the Active Directory
installation
Click Restart Now

37
Setting up DHCP
DHCP is required on the Head Node to dynamically assign the IP address to
Compute Nodes if they are not directly connected to the public network.
To start with DHCP configuration

Start Menu -> Control Panel

Select Add and Remove Programs

38
Windows Add and Remove Components
Select Networking Services
Select Networking Services

39
To add and remove any component click the check box
Check Dynamic Host Configuration Protocol (DHCP)
Click OK

40
41
42
To configure the DHCP server on the machine,
Go to
Start Menu -> Programs -> Administrative Tools -> DHCP
Right Click on Machine name -> New Scope

43
New Scope wizard
This wizard helps to set up a scope for distributing IP addresses to computers
on the network.

Click next to continue.

44
New Scope name and discription
You have to provide an identifying scope name. You can also provide
discription.

Click next to continue

45
IP Address Range
You can define the scope address range by identifying a set of consecutive IP
address

Enter Start IP address of the range

E.g. 192.168.1.6
Enter End IP address of the range
E.g. 192.168.1.10
Enter Length i.e. Bits of an IP address used for the network
Enter the Subnet Mask

Click next to continue

46
Add Exclusions
Exclusions are the address range that are not distributed by the server

To exclude a particular address range, type the range to be excluded

Click next to continue

47
Lease Duration
The lease duration specifies how long a client can use an IP address from this
scope

Lease duration should typically be equal to the average time the computer is
connected to the physical network

Set the duration of the scope leases when distributed by this server
Limited to
e.g. 8 Days

Click next to continue

48
Configure DHCP Options
You have to configure the most common DHCP options before clients can use
the scope.

You can either do it now or later

49
Completing the New Scope wizard

Before clients can receive you need to do the following

1) Add any specific options (Optional)
2) Activate the added scope

Click Finish

50
Installing Windows Compute Cluster Pack
Insert the Windows Compute Cluster Pack CD-ROM
You can read the release notes and installation instructions

Click Next to continue

51
52
Select the installation options as per the requirement
To install the head node utilities, select

Create a new compute cluster with this server as head node
If it is to be used as compute node, check Use this head node also as a
compute node

Click Next to continue

53
This screen shows the components to be installed on the head node

Click Install

These components will get installed one by one

54
Installation of Microsoft SQL Server Desktop Engine
installation click Cancel

55
Microsoft SQL Server 2000 Desktop Engine installation successfully
completed
Starting .NET framework 2.0 installation
Click Install to begin the installation

56
Installing .NET Framework 2.0
To cancel the installation click Cancel

57
Click Install to install the RIS
This will be installed by RIS Hotfix downloaded from :
http://go.microsoft.com/fwlink/?linkid=55167

58
Installing the updates
This may take several minutes

59
Completing the Hotfix installation
To apply changes of the update restart the machine

Click Finish

60
Microsoft Management Console installation
Click Install

You need to download this component form the link :

http://go.microsoft.com/fwlink/?linkid=55165

61
Installation of Microsoft Management Console 3.0
Click Next

62
License Agreement for MMC 3.0
Read the license agreement and select
I Agree

Click Next to continue

63
Installing MMC 3.0
To cancel the installation click Cancel

64
Completing the MMC 3.0 installation
Click Finish to complete the installation

65
Installation of Microsoft Compute Cluster Pack
Click Install to begin the installation

66
Installing Microsoft Compute Cluster Pack
Click cancel to cancel the installation

67
Completing Microsoft Compute Cluster Pack Installation
Click Finish to complete the installation

68
You need to configure parameters like Networking Topology, Remote
Installation Services, Node Management and Cluster Users before using the
cluster.

Go to Start Menu -> Programs -> Microsoft Compute Cluster Pack ->
Compute Cluster Administrator

Select To Do List

Go to Define Network Topology
The network topology depends upon the number of network interfaces you
have.

69
Assign Network Wizard
You can configure public, private and MPI network
Configure Network Address Translation

Ensure that the networks are operational i.e. you are able to ping all the
interfaces

Click Next to continue

70
This is the wizard to configure Public Network

Select Public Network Adapter from the drop down list

Verify the Properties
Click Next to continue

71
This is the wizard to configure Private Network

Select Private Network Adapter from the drop down list

Verify the Properties
Click Next to continue

72
This is the wizard to configure MPI Network

Select MPI Network Adapter from the drop down list

Verify the Properties
Click Next to continue

73
Enable Network Address Translation using ICS

Network Address Translation allows the compute nodes on the the private
network to access resources on the public network.
For enabling NAT you should have a public and private networks configured
Check Enable Network Address Translation using ICS
Click Next to continue

74
Update Summary

This shows the network configuration that will be enabled on the cluster
To accept the configurations click Finish

75
Update Complete
The summary of the networks configured

Click finish to exit the network configuration wizard

76
77
78
79
80
Setting up the network includes giving a static IP address to the network
interfaces.
For giving a static IP address to a network interface,

Right click on My network places

Right click on Local Area Connection

Select Internet Protocol (TCP/IP)

81

Select Use the Following IP address

Give a static IP to the interface e.g. 192.168.1.3

Give the Subnet mask e.g. 255.255.255.0

Default Gateway e.g. 192.168.1.5

Preferred DNS server

Click Ok to save the settings

82
Adding a compute node to Domain Controller

All the nodes in the Windows Compute Cluster Server should be in a same
domain
To join a node to a specific domain,

Right Click My Computer -> Properties

Change the workgroup to a specific domain -> Change

83
Add the Domain Name
Select Domain
Give the Domain Name

Click OK to continue

84
Windows will ask you to enter the name and password of the account with
permission to join the domain

Give the name and password

Click OK

Windows will join this node in the specified domain

Click OK

85
Windows needs restart to apply the changes
Click OK

86
Installing Windows Compute Cluster Pack
Insert the Windows Compute Cluster Pack CD-ROM
You can read the release notes and installation instructions

Click Next to continue

87
88
Select the installation option
To install compute node utilities,
select Join this server to an existing compute cluster as compute node
Enter the name of head node
E.g. Node3
Check Install client utilities also if this node is used to submit and manage jobs

Click Next to continue

89
90
Installation of Microsoft Management Console 3.0
Click Next

91
Installing MMC 3.0
To cancel the installation click Cancel

92
Completing the MMC 3.0 installation
Click Finish to complete the installation

93
Installation of Microsoft Compute Cluster Pack
Click Install to begin the installation

94
Installing Microsoft Compute Cluster Pack
Click cancel to cancel the installation

95
Completing Microsoft Compute Cluster Pack Installation
Click Finish to complete the installation

96
97
98
99
100
101
102
Windows Compute Cluster Server provides a GUI to monitor the setup of the
cluster

Go to Start Menu -> Programs -> Microsoft Compute Cluster Pack -> Compute
Cluster Administrator
You will be able to see the following items:
Total no. of nodes
Total no. of OK nodes
Total no. of paused nodes
Total no of unreachable nodes
Total no. of nodes pending for approval

103
Go to Node Management:
Here you will be able to see all the nodes in a cluster with OK sign

104
105
Sample Code
This code is a sample code used to demonstrate how MPI processes
communicates between themselves. This code will execute only if the MPI
communication size is three. Process with rank 0 behaves as a master
process and waits for messages from the other process, while the other
processes sends messages to the process with rank 0. Master process and
the program quits upon receipt of message

106
Windows Compute Cluster Server provides a GUI tool for job submission and
monitoring

To submit a job go to
Start Menu Programs Microsoft Compute Cluster Pack Job
Submission and Monitoring Console

File Select

107
Job Properties
You can give the job properties like
Job name
Project name
Priority

108
Job Properties
You can give the job properties like
1) Processors required by the job –
minimum and maximum required
2) Estimate runtime for the job –
Check this box to estimate run time
required for the job
3) Do not end job even if all tasks are completed – Check this box if you
need to run extra task after running all the tasks listed in the job if there is
time limit

109
Job Properties
You can give the job properties like
1) Command line argument –
Command line argument required by the job
to run
2) Standard input –
input file required by the job if any
3) Standard output –
output file for directing the job output
4) Standard error –
error file for directing errors occurred during jon
execution
5) Work directory –
the directory for job location
6) CPU –
minimum and maximum required
7) Job runtime –
to limit the runtime task

Click Apply and OK

110
Job Properties
After verifying the job properties, click Submit to submit the job.

111
You can see the status of the job submitted from the monitoring console.
Here the sample code is in Running status.
You can see all the properties related to the job form here like:
1) ID
2) Name
3) Priority
4) Submitted by
5) Status
6) Requested CPU
7) Submit time
8) Tasks

112
113
114
A quick recap of what has been discussed in this module. We briefly went
through the overview of a Cluster based on Windows Compute Cluster Server.
Steps required to configure a Cluster based on Windows Compute Cluster
Server.
Last, how to run a sample code on a Windows Compute Cluster.

115