93 lines
5.8 KiB
HTML
93 lines
5.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 xmlns="http://www.w3.org/1999/xhtml" lang="en-US" xml:lang="en-us">
|
||
|
|
<head>
|
||
|
|
<meta http-equiv="Content-Type" content="text/html; charset=utf-8" />
|
||
|
|
<meta name="dc.language" scheme="rfc1766" 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. -->
|
||
|
|
<meta name="dc.date" scheme="iso8601" content="2005-10-03" />
|
||
|
|
<meta name="copyright" content="(C) Copyright IBM Corporation 1998, 2006" />
|
||
|
|
<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))' />
|
||
|
|
<title>Design an APPN and HPR network to optimize communications performance</title>
|
||
|
|
<link rel="stylesheet" type="text/css" href="ibmidwb.css" />
|
||
|
|
<link rel="stylesheet" type="text/css" href="ic.css" />
|
||
|
|
</head>
|
||
|
|
<body>
|
||
|
|
<a id="Top_Of_Page" name="Top_Of_Page"></a><!-- Java sync-link -->
|
||
|
|
<script language = "Javascript" src = "../rzahg/synch.js" type="text/javascript"></script>
|
||
|
|
|
||
|
|
|
||
|
|
<a name="rzahjper-netdesinsts"></a>
|
||
|
|
<h3 id="rzahjper-netdesinsts">Design an APPN and HPR network to optimize communications performance</h3>
|
||
|
|
<p>The following list is a selection of tasks that are aimed at getting better
|
||
|
|
performance from a network.</p>
|
||
|
|
<p>To optimize performance when designing your network, consider the following:</p>
|
||
|
|
<ul>
|
||
|
|
<li><span class="bold">Avoid mesh connectivity</span>
|
||
|
|
<p>The number of control
|
||
|
|
program-to-control program (CP-CP) sessions that are configured for each network
|
||
|
|
node (NN) has a direct impact on the performance of a network. Network control
|
||
|
|
information such as topology updates and location searches flow over CP-CP
|
||
|
|
sessions. A consequence of too many CP-CP sessions is that information is
|
||
|
|
sent out to more nodes and the same node multiple times. This increases the
|
||
|
|
network processing that is done. In a mesh-connected network, every NN has
|
||
|
|
a CP-CP session with every other NN, increasing the number of CP sessions
|
||
|
|
in this network. The number of CP-CP sessions in the network should be kept
|
||
|
|
to a minimum while still providing necessary connectivity.</p>
|
||
|
|
<div class="mmobj">
|
||
|
|
<img src="rv4t202.gif" alt="A mesh-connected network." /></div></li>
|
||
|
|
<li><span class="bold">Consider backup CP-CP sessions where appropriate</span>
|
||
|
|
<p>A CP-CP spanning tree is a term that is used to describe the contiguous path
|
||
|
|
of CP-CP sessions between nodes throughout the network. CP-CP sessions carry
|
||
|
|
necessary control information and are required between NNs in order to participate
|
||
|
|
in the APPN network. Careful analysis to determine the minimal set of links,
|
||
|
|
that support CP-CP sessions, is important. Once these links are identified,
|
||
|
|
it is recommended that back-up links providing alternate CP-CP sessions are
|
||
|
|
added to the network. These backup links ensure availability of the CP-CP
|
||
|
|
spanning tree and are needed if the critical links fail.</p></li>
|
||
|
|
<li><span class="bold">Consider using border nodes</span>
|
||
|
|
<p>APPN architecture
|
||
|
|
does not allow two adjacent APPN NNs to connect and establish CP-CP sessions
|
||
|
|
when they do not share the same network identifier (NETID). Border nodes overcome
|
||
|
|
this restriction. Border nodes enable NNs with different NETIDs to connect
|
||
|
|
and allow session establishment between logical units (LU) in different NETID
|
||
|
|
subnetworks. Border nodes prevent topology information from flowing across
|
||
|
|
different NETID subnetworks. Use border nodes to subdivide a large APPN network
|
||
|
|
into smaller and more manageable subnetworks. iSeries provides this border node
|
||
|
|
capability for only adjacent networks.</p></li>
|
||
|
|
<li><span class="bold">Processing reduction for an EN and low-entry networking
|
||
|
|
(LEN) node</span>
|
||
|
|
<p>The amount of processing is reduced when the iSeries is an
|
||
|
|
end node or LEN node, as opposed to an NN for the following reasons: </p>
|
||
|
|
<ul>
|
||
|
|
<li>All network topology, and directory search information flows to every
|
||
|
|
attached network node.</li>
|
||
|
|
<li>End nodes and LEN nodes do not receive most of these information flows.</li></ul><p class="indatacontent">The network nodes (NN) perform route calculation for themselves and other
|
||
|
|
ENs and LEN nodes. (This function flows from the EN or LEN node to the NN.)</p></li>
|
||
|
|
<li><span class="bold">Reduction of network flows resulting from fewer network
|
||
|
|
nodes</span>
|
||
|
|
<p>In addition, topology information about ENs and LEN nodes does
|
||
|
|
not flow through the network. NN topology does flow to the entire network
|
||
|
|
that causes the other network nodes to process information about every other
|
||
|
|
network node.</p></li>
|
||
|
|
<li><span class="bold">Use Branch Extender</span>
|
||
|
|
<p>Branch Extender is an extension
|
||
|
|
to the APPN network architecture. It appears as a network node (NN) to the
|
||
|
|
Local Area Network (LAN), and as an end node (EN) to the Wide Area Network
|
||
|
|
(WAN). This reduces topology flows about resources in the LAN from being disconnected
|
||
|
|
from the WAN. The only topology flows necessary are for network management
|
||
|
|
that identify the types of links.</p>
|
||
|
|
<p>For more information about setting
|
||
|
|
up Branch Extender, see the page <a href="rzahjnetattpi.htm#rzahjnetatt-pi">Changing network
|
||
|
|
attributes</a>.</p></li></ul>
|
||
|
|
<p>For help in getting optimal performance from you network, see the page <a href="rzahjrzahjperf.htm#rzahjperf">Optimizing APPN and HPR communication performance</a>.</p>
|
||
|
|
<a id="Bot_Of_Page" name="Bot_Of_Page"></a>
|
||
|
|
</body>
|
||
|
|
</html>
|