50 lines
3.3 KiB
HTML
50 lines
3.3 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="Considerations for using clusters with firewalls" />
|
||
|
|
<meta name="abstract" content="If you are using clustering in a network that uses firewalls, you should be aware of some limitations and requirements." />
|
||
|
|
<meta name="description" content="If you are using clustering in a network that uses firewalls, you should be aware of some limitations and requirements." />
|
||
|
|
<meta name="DC.Relation" scheme="URI" content="rzaigconfigsecure.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="rzaigfirewalls" />
|
||
|
|
<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>Considerations for using clusters with firewalls</title>
|
||
|
|
</head>
|
||
|
|
<body id="rzaigfirewalls"><a name="rzaigfirewalls"><!-- --></a>
|
||
|
|
<img src="./delta.gif" alt="Start of change" /><!-- Java sync-link --><script language="Javascript" src="../rzahg/synch.js" type="text/javascript"></script>
|
||
|
|
<h1 class="topictitle1">Considerations for using clusters with firewalls</h1>
|
||
|
|
<div><p>If you are using clustering in a network that uses firewalls, you
|
||
|
|
should be aware of some limitations and requirements.</p>
|
||
|
|
<p>If you are using clustering with a firewall, you need to allow each node
|
||
|
|
the ability to send outbound messages to and receive inbound messages from
|
||
|
|
other cluster nodes. An opening in the firewall must exist for
|
||
|
|
each cluster address on each node to communicate with every cluster address
|
||
|
|
on every other node. IP packets traveling across a network can be of various
|
||
|
|
types of traffic. Clustering uses ping, which is type ICMP, and also uses
|
||
|
|
UDP and TCP. When a user configures a firewall, they can filter traffic based
|
||
|
|
on the type. For clustering to work the firewall needs to allow traffic of
|
||
|
|
ICMP, UDP and TCP. Outbound traffic can be sent on any port and inbound traffic
|
||
|
|
is received on ports 5550 and 5551.</p>
|
||
|
|
</div>
|
||
|
|
<div>
|
||
|
|
<div class="familylinks">
|
||
|
|
<div class="parentlink"><strong>Parent topic:</strong> <a href="rzaigconfigsecure.htm" title="Consider some of the security issues you need to consider when you plan to use clustering on your systems.">Cluster security</a></div>
|
||
|
|
</div>
|
||
|
|
</div>
|
||
|
|
<img src="./deltaend.gif" alt="End of change" /></body>
|
||
|
|
</html>
|