126 lines
8.0 KiB
HTML
126 lines
8.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="task" />
|
||
|
|
<meta name="DC.Title" content="Enabling application switchover" />
|
||
|
|
<meta name="abstract" content="Cluster resource services supports a user configured takeover IP address when configuring application CRGs." />
|
||
|
|
<meta name="description" content="Cluster resource services supports a user configured takeover IP address when configuring application CRGs." />
|
||
|
|
<meta name="DC.Relation" scheme="URI" content="rzaigconfigipaddrressapp.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="rzaigapplicationswitchover2" />
|
||
|
|
<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>Enabling application switchover </title>
|
||
|
|
</head>
|
||
|
|
<body id="rzaigapplicationswitchover2"><a name="rzaigapplicationswitchover2"><!-- --></a>
|
||
|
|
<!-- Java sync-link --><script language="Javascript" src="../rzahg/synch.js" type="text/javascript"></script>
|
||
|
|
<h1 class="topictitle1">Enabling application switchover </h1>
|
||
|
|
<div><p><span><img src="./delta.gif" alt="Start of change" />Cluster resource services supports a user configured
|
||
|
|
takeover IP address when configuring application CRGs.<img src="./deltaend.gif" alt="End of change" /></span></p>
|
||
|
|
<div class="section"><p>The following manual configuration steps are required to enable
|
||
|
|
the switchover environment. <strong>This set of instructions must be done on all
|
||
|
|
the nodes in the recovery domain, and repeated for the other nodes in the
|
||
|
|
cluster that will become nodes in the recovery domain for the given application
|
||
|
|
CRG.</strong></p>
|
||
|
|
</div>
|
||
|
|
<ol><li class="stepexpand"><span>Select a takeover IP address to be used by the application CRG.</span> <ul><li>To avoid confusion, this address should not overlap with any other existing
|
||
|
|
addresses used by the cluster nodes or routers. For example, if choosing 19.19.19.19,
|
||
|
|
ensure that 19.0.0.0 (19.19.0.0 or ...) are not routes known by the system
|
||
|
|
routing tables.</li>
|
||
|
|
<li>Add the takeover interface (for example, 19.19.19.19); create it with
|
||
|
|
a line description of *VIRTUALIP, subnet mask of 255.255.255.255 (host route),
|
||
|
|
Maximum Transmission Unit of 1500 (any number in the range 576-16388), and
|
||
|
|
Autostart of *NO. This takeover address (for example, 19.19.19.19) does must
|
||
|
|
exist as a *VIRTUALIP address before identifying it as an Associated Local
|
||
|
|
Interface in next step. It does not, however, must be active.</li>
|
||
|
|
</ul>
|
||
|
|
</li>
|
||
|
|
<li class="stepexpand"><span>Associate the intended takeover IP address with one or both of
|
||
|
|
the IP addresses specified to be used by cluster communications when you create
|
||
|
|
the cluster or add a node to the cluster.</span> <ul><li>For example, this means making the 19.19.19.19 takeover address an Associated
|
||
|
|
Local Interface on the IP address for the cluster node on the Ethernet bus
|
||
|
|
to be used locally for clustering. This must be done for each cluster address
|
||
|
|
on each cluster node.<div class="note"><span class="notetitle">Note:</span> The cluster addresses will must be ended to accomplish
|
||
|
|
this change under CFGTCP.</div>
|
||
|
|
</li>
|
||
|
|
</ul>
|
||
|
|
</li>
|
||
|
|
<li class="stepexpand"><span>Create the cluster and create any CRGs. For the application CRG
|
||
|
|
specify <kbd class="userinput">QcstUserCfgsTakeoverIpAddr</kbd> for the 'configure
|
||
|
|
takeover IP address' field. Do not start any Application CRGs.</span></li>
|
||
|
|
<li class="stepexpand"><span>Using Configure TCP/IP Applications (option 20) under CFGTCP, then
|
||
|
|
Configure RouteD (option 2), then Change RouteD attributes (option 1), ensure
|
||
|
|
Supply is set to *YES. If not, set to *YES and start or re-start ROUTED (RIP
|
||
|
|
or RIP-2) on each cluster node.</span> <ul><li>NETSTAT option 3 will show ROUTED using a Local Port if currently running.
|
||
|
|
ROUTED must be running and advertising routes (Supply = *YES) on every cluster
|
||
|
|
node in the CRG recovery domain.</li>
|
||
|
|
</ul>
|
||
|
|
</li>
|
||
|
|
<li class="stepexpand"><span>Ensure that all the commercial routers in the network interconnecting
|
||
|
|
the recovery domain LANs are accepting and advertising host routes for RIP.</span> <ul><li>This is not necessarily the default setting for routers. Language will
|
||
|
|
vary with router manufacturer but under RIP Interfaces, expect to be sending
|
||
|
|
Host Routes and receiving dynamic hosts.</li>
|
||
|
|
<li>This also applies to both the router interfaces pointing to the iSeries™ servers
|
||
|
|
as well as the router-to-router interfaces</li>
|
||
|
|
</ul>
|
||
|
|
<div class="note"><span class="notetitle">Note:</span> Do not use an iSeries server as the router in this scenario. Use
|
||
|
|
a commercial router (IBM<sup>®</sup> or otherwise) that is designed for routing purposes. iSeries routing
|
||
|
|
cannot be configured to handle this function.</div>
|
||
|
|
</li>
|
||
|
|
<li class="stepexpand"><span>You now can manually activate the takeover address on one of the
|
||
|
|
cluster nodes, allow RIP up to 5 minutes to propagate the routes, and ping
|
||
|
|
the takeover address from all nodes in the CRG recovery domain and from selected
|
||
|
|
clients on the LANs who will be using this address.</span> <ul><li>After this verification test, ensure the takeover address is ended again.</li>
|
||
|
|
<li>Clustering will start the address on the specified primary node when the
|
||
|
|
CRGs are started.</li>
|
||
|
|
</ul>
|
||
|
|
</li>
|
||
|
|
<li class="stepexpand"><span>Start the Application CRGs.</span> <ul><li>The takeover address will now be started by clustering on the specified
|
||
|
|
preferred node and RIP will advertise the routes throughout the recovery domain.
|
||
|
|
RIP may take up to 5 minutes to update routes across the domain. The RIP function
|
||
|
|
is independent from the start CRG function.</li>
|
||
|
|
</ul>
|
||
|
|
</li>
|
||
|
|
</ol>
|
||
|
|
<div class="section"><div class="note"><span class="notetitle">Important notes:</span> <ul><li>If the above procedure is not followed for all cluster nodes in the application
|
||
|
|
CRG recovery domain, the cluster will hang during the switchover process.</li>
|
||
|
|
<li>Even though we do not failover to replica nodes, it is a good idea to
|
||
|
|
perform the procedure on the replica nodes in the event that they may be changed
|
||
|
|
at a later date in time to become a backup.</li>
|
||
|
|
<li>If you want to use multiple virtual IP addresses, then each one will require
|
||
|
|
a separate application CRG and a separate IP address with which to be associated.
|
||
|
|
This address may be another logical IP address on the same physical adapter
|
||
|
|
or it may be another physical adapter altogether. Also, care must be taken
|
||
|
|
to prevent ambiguities in the routing tables. This is best achieved by doing
|
||
|
|
the following: <ul><li>Add a *DFTROUTE to the routing table for each virtual IP address.</li>
|
||
|
|
<li>This can be done under CFGTCP (option 2).</li>
|
||
|
|
<li>Set all parameters, including the next hop, the same to reach the router
|
||
|
|
of choice, but the Preferred binding interface should be set to be the local
|
||
|
|
system IP address associated with the virtual IP address that will be represented
|
||
|
|
by this route.</li>
|
||
|
|
</ul>
|
||
|
|
</li>
|
||
|
|
</ul>
|
||
|
|
</div>
|
||
|
|
</div>
|
||
|
|
</div>
|
||
|
|
<div>
|
||
|
|
<div class="familylinks">
|
||
|
|
<div class="parentlink"><strong>Parent topic:</strong> <a href="rzaigconfigipaddrressapp.htm" title="Manage application CRG takeover IP addresses using cluster resource services. You can also manage them manually.">Manage application CRG takeover IP addresses</a></div>
|
||
|
|
</div>
|
||
|
|
</div>
|
||
|
|
</body>
|
||
|
|
</html>
|