09.12.2012 Views

Understanding the network.pdf - Back to Home

Understanding the network.pdf - Back to Home

Understanding the network.pdf - Back to Home

SHOW MORE
SHOW LESS

Create successful ePaper yourself

Turn your PDF publications into a flip-book with our unique Google optimized e-Paper software.

dynamic routing pro<strong>to</strong>cols are used <strong>to</strong> manage different parts of a large<br />

inter<strong>network</strong>. This condition is often found in large corporate <strong>network</strong>s where<br />

different sites (and sometimes departments) are managed individually, but need <strong>to</strong><br />

interact with <strong>the</strong> larger corporate whole. Here, two-way route redistribution is a<br />

tremendous win.<br />

Internet or private global <strong>network</strong> connections are ano<strong>the</strong>r context where distinct<br />

dynamic routing pro<strong>to</strong>cols are in use <strong>to</strong> enforce <strong>the</strong> separate routing polices of <strong>the</strong><br />

two <strong>network</strong>s. With single-point connections, static routes can be used <strong>to</strong> send<br />

packets destined <strong>to</strong> external <strong>network</strong>s <strong>to</strong> <strong>the</strong> Internet gateway. In situations where<br />

multiple Internet and private <strong>network</strong> links exist (as an alternative <strong>to</strong> using BGP), it<br />

is possible <strong>to</strong> use filtered redistribution <strong>to</strong> limit <strong>the</strong> inbound and outbound <strong>network</strong><br />

announcements between <strong>the</strong> different routing policies using distribution lists and<br />

route-maps.<br />

Static route redistribution is often used in dial-access and DDR <strong>network</strong>s where<br />

dynamic pro<strong>to</strong>cols are not always effective. Instead of adding static routes on every<br />

router on <strong>the</strong> <strong>network</strong>, a single router can redistribute a collection of static routes.<br />

Static route redistribution can also be used <strong>to</strong> limit <strong>network</strong> announcements inside<br />

internal <strong>network</strong>s. By using multiple dynamic routing processes <strong>to</strong> manage different<br />

sections of <strong>the</strong> <strong>network</strong>, and <strong>the</strong>n statically redistributing on a selective basis, you<br />

will only announce <strong>the</strong> <strong>network</strong>s that need <strong>to</strong> be announced between <strong>the</strong> separate<br />

routing processes.<br />

The "worse" is <strong>the</strong> potential for routing loops and <strong>the</strong> difficulty surrounding <strong>the</strong><br />

translation of different routing pro<strong>to</strong>col metrics and distances. Here are some<br />

guidelines <strong>to</strong> help you avoid <strong>the</strong> "worse" side of using redistribution:<br />

• Ask yourself, "What is <strong>the</strong> advantage <strong>to</strong> using redistribution (in a given<br />

situation) over using a static route?" In most cases, a static route or default<br />

route can be used <strong>to</strong> provide a <strong>network</strong> announcement. If you have only a<br />

few <strong>network</strong>s <strong>to</strong> redistribute, use static routes. Ideally, you only want <strong>to</strong> be<br />

running a single routing pro<strong>to</strong>col. In situations where legacy equipment<br />

might reduce your choices in terms of which pro<strong>to</strong>cols you can use, it might<br />

be more advantageous <strong>to</strong> use a single pro<strong>to</strong>col or static routing (<strong>to</strong> address<br />

legacy hardware issues) than <strong>to</strong> add <strong>the</strong> additional processing and <strong>network</strong><br />

traffic associated with multiple pro<strong>to</strong>col redistribution.<br />

• If possible, avoid redistributing between classless and classful pro<strong>to</strong>cols if<br />

you are using VLSM. Classful pro<strong>to</strong>cols do not include <strong>network</strong> address<br />

masks in <strong>the</strong>ir messages. Instead, <strong>the</strong>y apply <strong>the</strong> mask of <strong>the</strong> interface that<br />

receives <strong>the</strong> route announcements. Consequently, only VLSM <strong>network</strong>s that<br />

have compatible masks will be advertised, and <strong>the</strong> o<strong>the</strong>rs will not be<br />

redistributed.<br />

• When using redistribution with multigateway <strong>network</strong>s (or HSRP) it is<br />

essential that <strong>the</strong> gateway routers use metrics and distances that favor one

Hooray! Your file is uploaded and ready to be published.

Saved successfully!

Ooh no, something went wrong!