Table of Contents
Advertisement
3 In the Adapters and Bindings tab, ensure that the Private and Public connections are at the
top of the list.
To change the connection order:
Click Public or Private.
a
Click the up-arrow or down-arrow to move the connection to the top or bottom of the
b
Connections box.
Click OK.
c
Close the Network Connections window.
d
Using Dual-Port Network Adapters for the Private Network
You can configure your cluster to use the public network as a failover for private network
communications. However, dual-port network adapters are not supported in the
private network.
Verifying Cluster Network Communications
To ensure proper cluster operations, the cluster nodes must be able to communicate with each
other through the private network (cluster interconnect). This communication involves the
exchange of heartbeat messages, whereby the two cluster nodes inquire about each other's
status, or "health," and acknowledge each inquiry.
To verify network communications between the cluster nodes:
1 Open a command prompt on each cluster node.
2 At the prompt, type:
ipconfig /all
3 Press <Enter>.
All known IP addresses for each local server appear on the screen.
4 Issue the ping command from each remote system.
Ensure that each local server responds to the ping command.
Configuring the Internet Connection Firewall
The Microsoft Windows Server 2003 Enterprise x64 Edition and Windows Server 2003
Enterprise Edition operating systems with Service Pack 1 include an enhanced Internet
Connection Firewall that can be configured to block incoming network traffic to a PowerEdge
system. To prevent the Internet Connection Firewall from disrupting cluster communications,
additional configuration settings are required for PowerEdge systems that are configured as
cluster nodes in an MSCS cluster.
Preparing Your Systems for Clustering
37
Advertisement
Table of Contents
Troubleshooting
