Configuring The Private Network Adapter; Configuring The Public Network Adapter; Renaming The Local Area Connection Icons; Verifying Connectivity And Name Resolution - HP ProLiant DL380 G5 Administration Manual

The private network adapter establishes node-to-node communication, cluster status signals, and cluster
management. Each node's public network adapter connects the cluster to the public network where
clients reside.
Verify that all network connections are correct, with private network adapters connected to other private
network adapters only, and public network adapters connected to the public network.
Configuring the private network adapter
The following procedures are Best Practices provided by Microsoft and should be configured on the
private network adapter.
• On the General tab of the private network adapter, ensure that only TCP/IP is selected.
• Ensure that the Register this connection's address in DNS is not selected in the DNS tab under
advanced settings for Internet Protocol (TCP/IP) Properties.
• Ensure that the Link Speed and Duplex is set to 100Mps/Full Duplex under the Advanced tab for
the Ethernet card used for the private network adapter.
• In all cases, set static IP addresses for the private network connector.
Configuring the public network adapter
While the public network adapter's IP address can be automatically obtained if a DHCP server is
available, this is not recommended for cluster nodes. HP strongly recommends setting static IP addresses
for all network adapters in the cluster, both private and public. If IP addresses are obtained though DHCP,
access to cluster nodes could become unavailable if the DHCP server goes down. If DHCP must be used
for the public network adapter, use long lease periods to assure that the dynamically assigned lease
address remains valid even if the DHCP service is temporarily lost. Keep in mind that Cluster service
recognizes only one network interface per subnet.

Renaming the local area connection icons

HP recommends changing the names of the network connections for clarity. The naming helps identify
a network and correctly assign its role. For example, "Cluster interconnect" for the private network
and "Public connection" for the public network.

Verifying connectivity and name resolution

To verify name resolution, ping each node from a client using the node's machine name instead of its
IP number.

Verifying domain membership

All nodes in the cluster must be members of the same domain and able to access a domain controller
and a DNS Server.

Setting up a cluster account

The Cluster service requires a domain user account under which the Cluster service can run. This user
account must be created before installing Cluster service, because setup requires a user name and
password. This user account should not belong to a user on the domain. This user account will need to
be granted administrator privileges.

About the Quorum disk

When configuring the Quorum disk only one node should be powered on. All other potential cluster
nodes must be powered off.
The Quorum disk is used to store cluster configuration database checkpoints and log files that help
manage the cluster. The Quorum disk must be a shared disk resource. HP makes the following Quorum
disk recommendations:
128
Cluster administration