87 lines
6.0 KiB
HTML
87 lines
6.0 KiB
HTML
|
<?xml version="1.0" encoding="UTF-8"?>
|
||
|
|
<!DOCTYPE html
|
||
|
|
PUBLIC "-//W3C//DTD XHTML 1.0 Transitional//EN" "http://www.w3.org/TR/xhtml1/DTD/xhtml1-transitional.dtd">
|
||
|
|
<html lang="en-us" xml:lang="en-us">
|
||
|
|
<head>
|
||
|
|
<meta http-equiv="Content-Type" content="text/html; charset=utf-8" />
|
||
|
|
<meta name="security" content="public" />
|
||
|
|
<meta name="Robots" content="index,follow" />
|
||
|
|
<meta http-equiv="PICS-Label" content='(PICS-1.1 "http://www.icra.org/ratingsv02.html" l gen true r (cz 1 lz 1 nz 1 oz 1 vz 1) "http://www.rsac.org/ratingsv01.html" l gen true r (n 0 s 0 v 0 l 0) "http://www.classify.org/safesurf/" l gen true r (SS~~000 1))' />
|
||
|
|
<meta name="DC.Type" content="concept" />
|
||
|
|
<meta name="DC.Title" content="Tips: Cluster communications" />
|
||
|
|
<meta name="abstract" content="Consider these tips when you set up your communications paths." />
|
||
|
|
<meta name="description" content="Consider these tips when you set up your communications paths." />
|
||
|
|
<meta name="DC.Relation" scheme="URI" content="rzaigplandesignnetwork.htm" />
|
||
|
|
<meta name="DC.Relation" scheme="URI" content="rzaigplanreplication.htm" />
|
||
|
|
<meta name="DC.Relation" scheme="URI" content="rzaigconceptsreliablemessagefunction.htm" />
|
||
|
|
<meta name="DC.Relation" scheme="URI" content="../rzai2/rzai2kickoff.htm" />
|
||
|
|
<meta name="copyright" content="(C) Copyright IBM Corporation 1998, 2006" />
|
||
|
|
<meta name="DC.Rights.Owner" content="(C) Copyright IBM Corporation 1998, 2006" />
|
||
|
|
<meta name="DC.Format" content="XHTML" />
|
||
|
|
<meta name="DC.Identifier" content="rzaigconfigcommtips" />
|
||
|
|
<meta name="DC.Language" content="en-us" />
|
||
|
|
<!-- All rights reserved. Licensed Materials Property of IBM -->
|
||
|
|
<!-- US Government Users Restricted Rights -->
|
||
|
|
<!-- Use, duplication or disclosure restricted by -->
|
||
|
|
<!-- GSA ADP Schedule Contract with IBM Corp. -->
|
||
|
|
<link rel="stylesheet" type="text/css" href="./ibmdita.css" />
|
||
|
|
<link rel="stylesheet" type="text/css" href="./ic.css" />
|
||
|
|
<title>Tips: Cluster communications</title>
|
||
|
|
</head>
|
||
|
|
<body id="rzaigconfigcommtips"><a name="rzaigconfigcommtips"><!-- --></a>
|
||
|
|
<!-- Java sync-link --><script language="Javascript" src="../rzahg/synch.js" type="text/javascript"></script>
|
||
|
|
<h1 class="topictitle1">Tips: Cluster communications</h1>
|
||
|
|
<div><p>Consider these tips when you set up your communications paths.</p>
|
||
|
|
<ul><li>Be sure you have adequate bandwidth on your communication lines to handle
|
||
|
|
the non-cluster activity along with the clustering heartbeating function and
|
||
|
|
continue to monitor for increased activity. </li>
|
||
|
|
<li>For best reliability, do not configure a single communication path linking
|
||
|
|
one or more nodes.</li>
|
||
|
|
<li>Do not overburden the line that is responsible for ensuring that you are
|
||
|
|
still communicating with a node.</li>
|
||
|
|
<li>Eliminate as many single points of failure as possible such as having
|
||
|
|
two communication lines coming into a single adapter, same input-output processor
|
||
|
|
(IOP), or same tower.</li>
|
||
|
|
<li>If you have an extremely high volume of data being passed over your communication
|
||
|
|
lines, you may want to consider putting data replication and heartbeat monitoring
|
||
|
|
on separate networks.</li>
|
||
|
|
<li>If you are using Internet Protocol (IP) multicast, you should see the
|
||
|
|
TCP/IP Configuration and Reference for multicast restrictions that may apply
|
||
|
|
to different types of physical media.</li>
|
||
|
|
<li>User Datagram Protocol (UDP) multicast is the preferred protocol that
|
||
|
|
the cluster communications infrastructure uses to send cluster management
|
||
|
|
information between nodes in a cluster. When the physical media supports multicast
|
||
|
|
capabilities, cluster communications utilizes the UDP multicast to send management
|
||
|
|
messaging from a given node to all local cluster nodes that support the same
|
||
|
|
subnet address. Messages that are sent to nodes on remote networks are always
|
||
|
|
sent using UDP point-to-point capabilities. Cluster communications does not
|
||
|
|
rely on routing capability for multicast messages.</li>
|
||
|
|
<li>The multicast traffic that supports cluster management messaging tends
|
||
|
|
to fluctuate by nature. Depending on the number of nodes on a given LAN (that
|
||
|
|
supports a common subnet address) and the complexity of the cluster management
|
||
|
|
structure that is chosen by the cluster administrator, cluster related multicast
|
||
|
|
packets can easily exceed 40 packets per second. Fluctuations of this nature
|
||
|
|
can have a negative impact on older networking equipment. One example is
|
||
|
|
congestion problems on devices on the LAN that serve as Simple Network
|
||
|
|
Management Protocol (SNMP) agents that need to evaluate every UDP multicast
|
||
|
|
packet. Some of the earlier networking equipment does not have adequate bandwidth
|
||
|
|
to keep up with this type of traffic. You need to ensure that you or the network
|
||
|
|
administrator has reviewed the capacity of the networks to handle UDP multicast
|
||
|
|
traffic to make certain that clustering does not have a negative impact on
|
||
|
|
the performance of the networks.</li>
|
||
|
|
</ul>
|
||
|
|
</div>
|
||
|
|
<div>
|
||
|
|
<div class="familylinks">
|
||
|
|
<div class="parentlink"><strong>Parent topic:</strong> <a href="rzaigplandesignnetwork.htm" title="Before you configure your networks for clustering, you need to plan carefully and do some initial pre-cluster configuration involving TCP/IP.">Design your network for clusters</a></div>
|
||
|
|
</div>
|
||
|
|
<div class="relconcepts"><strong>Related concepts</strong><br />
|
||
|
|
<div><a href="rzaigplanreplication.htm" title="Multiple copies of the data are maintained with logical replication. Data is replicated, or copied, from the primary node in the cluster to the backup nodes designated in the recovery domain. When an outage occurs on the primary node, the data remains available as a designated backup node takes over as the primary point of access.">Plan for logical replication</a></div>
|
||
|
|
<div><a href="rzaigconceptsreliablemessagefunction.htm" title="The reliable message function of cluster resource services keeps track of each node in a cluster and ensures that all nodes have consistent information about the state of cluster resources.">Reliable message function</a></div>
|
||
|
|
</div>
|
||
|
|
<div class="relinfo"><strong>Related information</strong><br />
|
||
|
|
<div><a href="../rzai2/rzai2kickoff.htm">TCP/IP setup</a></div>
|
||
|
|
</div>
|
||
|
|
</div>
|
||
|
|
</body>
|
||
|
|
</html>
|