HP ProLiant DL380 G5-Storage-Server - Manual (Page 110)

Table 11 Power sequencing for cluster installation
Step Node 1
Additional
Nodes
Storage Comments
Setting up
networks
On On
Not
Presented
Verify that all storage devices on the
shared bus are not presented; Power
on all nodes.
Setting up
shared disks
(including the
Qurom disk)
On Off Presented
Shut down all nodes. Present the shared
storage, then power on the first node.
Verifying disk
configuration
Off On Presented
Shut down first node, power on next
node. Repeat this process for all cluster
nodes.
Configuring the
first node
On Off Presented
Shut down all nodes; power on the first
node.
Configuring
additional
nodes
On On Presented
Power on the next node after the
first node is successfully configured.
Complete this process for all cluster
nodes.
Post-installation On On Presented
At this point all cluster nodes should be
on.
To configure the Cluster service on the storage server, an account must have administrative permissions
on each node.
Setting up networks
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.
• 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.
110 Cluster administration