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
fi
rst node.
Verifying disk
con
fi
guration
Off
On
Presented
Shut down
fi
rst node, power on next
node. Repeat this process for all cluster
nodes.
Con
fi
guring the
fi
rst node
On
Off
Presented
Shut down all nodes; power on the
fi
rst
node.
Con
fi
guring
additional
nodes
On
On
Presented
Power on the next node after the
fi
rst node is successfully con
fi
gured.
Complete this process for all cluster
nodes.
Post-installation
On
On
Presented
At this point all cluster nodes should be
on.
To con
fi
gure 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.
Con
fi
guring the private network adapter
The following procedures are best practices provided by Microsoft and should be con
fi
gured 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.
Con
fi
guring 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.
106
Cluster administration
Summary of Contents for DL320s - ProLiant 9TB SATA Storage Server NAS
Page 14: ...14 About this guide ...
Page 28: ...28 Installing and configuring the server ...
Page 36: ...36 Storage management overview ...
Page 68: ...68 File server management ...
Page 74: ...74 Print services ...
Page 96: ...96 Enterprise storage servers ...
Page 120: ...120 Troubleshooting servicing and maintenance ...
Page 122: ...122 System recovery ...