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

You also want an ePaper? Increase the reach of your titles

YUMPU automatically turns print PDFs into web optimized ePapers that Google loves.

All routers on <strong>the</strong> <strong>network</strong> keep track of <strong>the</strong>ir update times and <strong>the</strong><br />

ages of<strong>the</strong> routes in <strong>the</strong>ir tables. If a router has not received an<br />

update message from a particular <strong>network</strong> after 180 seconds, <strong>the</strong><br />

route is marked as invalid. After <strong>the</strong> route has been marked as invalid,<br />

it is in a hold-down state. While <strong>the</strong> route is in this state, <strong>the</strong> router<br />

continues <strong>to</strong> forward traffic using that route. During this period, <strong>the</strong><br />

router is also trying <strong>to</strong> find a route with a higher metric <strong>to</strong> use as an<br />

alternative. If a higher metric alternative is not found, and <strong>the</strong>re still<br />

has not been an update from <strong>the</strong> router, <strong>the</strong> route is flushed from <strong>the</strong><br />

table and users are notified by Internet Control Message Pro<strong>to</strong>col<br />

(ICMP) that <strong>the</strong>ir datagrams cannot be delivered.<br />

Route Poisoning<br />

To prevent routing <strong>the</strong> routing loops that are endemic <strong>to</strong> DVPs, RIP<br />

employs route poisoning. Route poisoning is a method of inflating<br />

route metrics contained in <strong>the</strong> update messages that are sent <strong>to</strong><br />

neighbor routers. This is done so <strong>the</strong> routes that are exchanged<br />

between locally connected routers are not interpreted as alternative<br />

routes. If this were allowed <strong>to</strong> happen, routing loops would occur in<br />

<strong>the</strong> event of a router failure. RIP uses two types of route poisoning:<br />

• Split horizon<br />

• Poison reverse<br />

In Figure 8.9, <strong>the</strong> Fast E<strong>the</strong>rnet hub that Router E is attached <strong>to</strong> has<br />

just died. Router E has <strong>the</strong> route <strong>to</strong> 192.124.39.0 in hold-down mode<br />

and is looking for an alternative route. Router C has just sent its<br />

update and says that it can reach 192.124.39.0 with a hop count of 2.<br />

Router E is happy; it changes its routing table and starts sending from<br />

<strong>the</strong> 192.124.38.0 <strong>network</strong> that is destined for <strong>the</strong> 192.124.39.0 <strong>to</strong><br />

Router C, and Router C starts sending it back <strong>to</strong> Router E. This starts<br />

<strong>the</strong> beginning of a routing loop that continues until both routers have<br />

raised <strong>the</strong> hop count for <strong>the</strong> route <strong>to</strong> 16, known as <strong>the</strong> Count <strong>to</strong><br />

Infinity.

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

Saved successfully!

Ooh no, something went wrong!