71 lines
4.4 KiB
HTML
71 lines
4.4 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="Dynamic routing" />
|
||
|
|
<meta name="abstract" content="Dynamic routing is a low-maintenance method that automatically reconfigures routing tables as your network changes." />
|
||
|
|
<meta name="description" content="Dynamic routing is a low-maintenance method that automatically reconfigures routing tables as your network changes." />
|
||
|
|
<meta name="DC.Relation" scheme="URI" content="rzajwrcb.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="rzajwdrwan" />
|
||
|
|
<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>Dynamic routing</title>
|
||
|
|
</head>
|
||
|
|
<body id="rzajwdrwan"><a name="rzajwdrwan"><!-- --></a>
|
||
|
|
<!-- Java sync-link --><script language="Javascript" src="../rzahg/synch.js" type="text/javascript"></script>
|
||
|
|
<h1 class="topictitle1">Dynamic routing</h1>
|
||
|
|
<div><p>Dynamic routing is a low-maintenance method that automatically
|
||
|
|
reconfigures routing tables as your network changes.</p>
|
||
|
|
<p>Dynamic routing is provided by Interior Gateway Protocols (IGPs), such
|
||
|
|
as Routing Internet Protocol (RIP). RIP allows you to configure the hosts
|
||
|
|
as part of a RIP network. This type of routing requires little maintenance
|
||
|
|
and also automatically reconfigures routing tables when your network changes
|
||
|
|
or crashes. RIPv2 was added to the iSeries™ server so you can send and receive
|
||
|
|
RIP packets to update routes throughout your network.</p>
|
||
|
|
<p>In the following figure, a static route is added to the central system
|
||
|
|
(AS1) that describes the connection to the network 10.1.1.x via AS2. This
|
||
|
|
is a static route (added by your network administrator) with route redistribution
|
||
|
|
set to yes. This setting causes this route to be shared with other routers
|
||
|
|
and systems so that when they have traffic for 10.1.1.x, they route the traffic
|
||
|
|
to your central iSeries server
|
||
|
|
(AS1). AS2 has the routed server started so that it sends and receives RIP
|
||
|
|
information. In this example, AS1 is sending the message that AS2 has a direct
|
||
|
|
connection to 10.1.2.x.</p>
|
||
|
|
<br /><img src="rzajw520.gif" alt="Example of dynamic routing" /><br /><div class="section"><h4 class="sectiontitle">What's happening in this example?</h4><ul><li>AS1 receives this RIP packet from AS2 and processes it. If AS1 does not
|
||
|
|
have a route to 10.1.2.x, it will store this route. If it does have a path
|
||
|
|
to 10.1.2.x that is the same number of hops or fewer, it will discard this
|
||
|
|
new route information. In this example, AS1 keeps the route data.</li>
|
||
|
|
<li>AS1 receives information from R1 with route information to 10.1.5.x. AS1
|
||
|
|
keeps this route information.</li>
|
||
|
|
<li>AS1 receives information from R2 with route information to 10.1.3.x. AS1
|
||
|
|
keeps this route information.</li>
|
||
|
|
<li>The next time AS1 sends RIP messages, it will send information to R1 that
|
||
|
|
describes all the connections AS1 knows about that R1 might not know about.
|
||
|
|
AS1 sends route information about 10.1.1.x, 10.1.2.x, and 10.1.3.x. AS1 does
|
||
|
|
not send information about 10.1.4.x to R1 because AS1 knows that R1 is connected
|
||
|
|
to 10.1.4.x and does not need a route. Similar information is sent to R2 and
|
||
|
|
AS3.</li>
|
||
|
|
</ul>
|
||
|
|
</div>
|
||
|
|
</div>
|
||
|
|
<div>
|
||
|
|
<div class="familylinks">
|
||
|
|
<div class="parentlink"><strong>Parent topic:</strong> <a href="rzajwrcb.htm" title="Routing deals with what path the network traffic follows from its source to its destination and how that path is connected.">Routing connectivity methods</a></div>
|
||
|
|
</div>
|
||
|
|
</div>
|
||
|
|
</body>
|
||
|
|
</html>
|