66 lines
4.8 KiB
HTML
66 lines
4.8 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="Set up IP addresses" />
|
|
<meta name="abstract" content="Because cluster resource services uses only IP to communicate with other cluster nodes, all cluster nodes must be IP-reachable." />
|
|
<meta name="description" content="Because cluster resource services uses only IP to communicate with other cluster nodes, all cluster nodes must be IP-reachable." />
|
|
<meta name="DC.Relation" scheme="URI" content="rzaigplandesignnetwork.htm" />
|
|
<meta name="DC.Relation" scheme="URI" content="rzaigconceptsreliablemessagefunction.htm" />
|
|
<meta name="DC.Relation" scheme="URI" content="rzaigconceptsheartbeatmonitor.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="rzaigplansetip" />
|
|
<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>Set up IP addresses</title>
|
|
</head>
|
|
<body id="rzaigplansetip"><a name="rzaigplansetip"><!-- --></a>
|
|
<!-- Java sync-link --><script language="Javascript" src="../rzahg/synch.js" type="text/javascript"></script>
|
|
<h1 class="topictitle1">Set up IP addresses</h1>
|
|
<div><p>Because cluster resource services uses <em>only</em> IP to communicate
|
|
with other cluster nodes, all cluster nodes must be <var class="varname">IP-reachable</var>.</p>
|
|
<p> This means that you must have IP interfaces configured to connect the
|
|
nodes in your cluster. These IP addresses must be set up either manually by
|
|
the network administrator in the TCP/IP routing tables on each cluster node
|
|
or they may be generated by routing protocols running on the routers in the
|
|
network. This TCP/IP routing table is the map that clustering uses to find
|
|
each node; therefore, each node must have its own <em>unique</em> IP address.
|
|
Each node may have up to two IP addresses assigned to it. These addresses
|
|
must not be changed in any way by other network communications applications.
|
|
Be sure when you assign each address that you take into account which address
|
|
uses which kind of communication line. If you have a preference for using
|
|
a specific type of communication media, make sure to configure the first IP
|
|
address using your preferred media. The first IP address is what is treated
|
|
preferentially by the reliable message function and heartbeat monitoring.
|
|
All IP addresses on a node must be able to reach every other IP address in
|
|
the cluster. One address can reach another address if you can ping and use
|
|
a UDP message traceroute in both directions.</p>
|
|
<div class="note"><span class="notetitle">Note:</span> You need to be sure that the loop back address (127.0.0.1) is active
|
|
for clustering. This address, which is used to send any messages back to the
|
|
local node, is normally active by default. However, if it has been ended by
|
|
mistake, cluster messaging cannot function until this address has been restarted.</div>
|
|
</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="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><a href="rzaigconceptsheartbeatmonitor.htm" title="Heartbeat monitoring is a cluster resource services function that ensures that each node is active by sending a signal from every node in the cluster to every other node in the cluster to convey that they are still active.">Heartbeat monitoring</a></div>
|
|
</div>
|
|
</div>
|
|
</body>
|
|
</html> |