Protocol Planning - HP ProLiant 300 Series Administration Manual

• The cluster name (Unique NETBIOS Name) and IP address
• Node A's name and IP address
• Node B's name and IP address
• At least one virtual server name and IP address for Node A
• At least one virtual server name and IP address for Node B
• Cluster Interconnect static IP addresses for Node A and Node B
In multi node deployments additional network addresses are required. For each additional node, three
static IP addresses are required.
Virtual names and addresses are the only identification used by clients on the network. Because the
names and addresses are virtual, their ownership can transition from one node to the other during a
failover, preserving access to the shares on the virtual disks.
In addition, a cluster uses at least two network connections on each node:
• The cluster interconnect or "heartbeat" crossover cable connects to the first network port on
each cluster node. In more than two node deployments, a private VLAN on a switch or hub is
required for the cluster interconnect.
• The client network subnet connects to a second network port on each cluster node. The cluster
node names and virtual server names have IP addresses residing on these subnets.
NOTE:
If the share is to remain available during a failover, each cluster node must be connected to the same
network subnet. It is impossible for a cluster node to serve the data to a network to which it is not
connected.

Protocol planning

The storage servers support many file sharing protocols, including sharing protocols for Windows, UNIX,
Linux, Novell, Macintosh, Web, and FTP clients. However, not all of these protocols can take advantage
of clustering. If a protocol does not support clustering, the share is not available to the clients until
the owner cluster node is brought back online.
HP recommends placing cluster aware and non cluster aware protocols on different file shares.
HP ProLiant Storage Server administration guide
177