HP ProLiant Storage Server User Guide (440584-001, February 2007)

Table 11 Power sequencing for c luster 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 t
he
Qurom disk)
On
Off
Presented Shut down all n
odes. 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 t
his process for all cluster
nodes.
Post-installation
On On
Presented At this point all cluster nodes should be
on.
To configuretheClusterserviceonthestorageserver,anaccountmusthaveadministrativepermissions
on each node.
Setting u
pnetworks
Verify t
hat all network connections are correct, with private network adapters c onnected to other private
network ad apters only, and public network adapters connected to the public n etwork.
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 net work adapter, ensure that only TCP/IP is selected.
• Ensure that the Register t his connection's address in DNS is not selected in the DNS tab under
advanced settings for Internet Protocol (TCP/IP) Proper ties.
• 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 recommende d for cluster nodes. H P strongly recommends setting static IP a ddresses
for all network adapters in the cluster, both private and public. If I P a ddresses are obtained though DHCP,
access to cluster nodes could become unavailable if the DHCP server goes down. If DHC P 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 m ind that Cluster service
rec
ognizes 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