Filter
Top Products
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 VL AN 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 sup port 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.
Use the information in Table 16 to determine whether it is advantageous to use clustering.
Table 16 Sharing protocol cluster support
Protocol Client Variant Cluster Aware
(supports failover)
Supported
CIFS/SMB
Windows NT
Yes Yes
Windows 2000
Windows 95
Windows 98
Windows ME
NFS UNIX
Yes Yes
Linux
HTTP
Web
No
Yes
FTP
Many
Yes Yes
NCP
Novell
No
Yes
AppleTalk Apple
No No
NOTE:
AppleTalk is not supported on clustered disk resources. AppleTalk requires loca l memor y for volume
indexing. On failover events, the memory map is lost and data corruption can occur.
Preparing for cluster installation
This se
ction provides the steps necessary to cluster HP ProLi ant storage servers.
HPProLiantDL380G5StorageServer 123