Compute Cluster Network Topology: Scenario 1
Applies To: Windows Compute Cluster Server 2003
Compute nodes isolated on private network
In this cluster topology scenario, the head node has two network interfaces, and each compute node has one. The head node is connected to both an existing public network, and to a dedicated private network between the head node and cluster compute nodes. The compute nodes access resources on the public network through the head node.
The private network carries all communication between the head node and compute nodes, including deployment, management, and MPI traffic.
.gif "Network Topology Scenario 1")
Considerations when using this topology
Improved cluster response because internal cluster network is routed onto the private network.
Network traffic between compute nodes and resources (such as databases and file servers) on the public network passes through the head node. Depending on the amount of traffic, this could impact cluster response.
Cluster compute nodes are not directly accessible by users on the public network. This has implications when developing and debugging parallel applications for use on the cluster.
Proxy servers on the public network must be specified on each compute node for internet access from the nodes.
Network Configuration
Enabling ICS on the head node is recommended for this cluster topology. Enabling ICS will provide network address translation to the cluster compute nodes so the nodes can access network services and resources on the public network. Enabling ICS also provides DNS and DHCP services to the private network interfaces of the compute nodes.