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.

• Better reliability—OSPF routers construct <strong>the</strong>ir own routing<br />

table describing <strong>network</strong> reachability from <strong>the</strong>ir perspective<br />

form within <strong>the</strong> <strong>network</strong>. All <strong>network</strong> routes are s<strong>to</strong>red in <strong>the</strong><br />

<strong>to</strong>pological or link state database, where <strong>the</strong>y can be retrieved<br />

quickly in <strong>the</strong> event that a routing change must be made. RIP,<br />

as you might recall, discards all routes except <strong>the</strong> best one,<br />

making it dependent on a routing update in order <strong>to</strong> construct a<br />

new route in <strong>the</strong> event that <strong>the</strong> old route is no longer viable.<br />

• Fast convergence—After <strong>the</strong> <strong>network</strong> has converged and all <strong>the</strong><br />

routers have constructed <strong>the</strong>ir own routing tables and <strong>network</strong><br />

maps, updates are sent out only when changes in <strong>the</strong> <strong>network</strong><br />

<strong>to</strong>pology occur. When changes occur, <strong>the</strong>y are flooded across all<br />

<strong>network</strong> links so each router can adjust for <strong>the</strong> change in <strong>the</strong><br />

<strong>network</strong> <strong>to</strong>pology immediately.<br />

• Unlimited <strong>network</strong> size—No maximum hop distance is enforced<br />

with OSPF. Network size is constrained only by available router<br />

processing power and Layer 2 medium limitations.<br />

• VLSM support—OSPF provides full support for VLSM.<br />

• Type of Service routing—OSPF supports Layer 4 Quality of<br />

Service routing. ToS/QoS was part of <strong>the</strong> original TCP/IP suite,<br />

but was never compatible with RIP. This lack of support resulted<br />

in lack of implementation. ToS/QoS is experiencing something<br />

of a revival now that <strong>network</strong>-based applications are becoming<br />

more and more performance sensitive.<br />

• Low bandwidth usage—OSPF uses multicast instead of local<br />

<strong>network</strong> broadcasts <strong>to</strong> send out OSPF messages. This limits <strong>the</strong><br />

impact of OSPF messages <strong>to</strong> only OSPF-speaking hosts.<br />

• Dynamic load balancing and route selection—OSPF uses a cost<br />

metric <strong>to</strong> determine route desirability. Cost is based on <strong>the</strong> link<br />

speed. Links of equal cost are load balanced, and in cases where<br />

<strong>the</strong>re are links of unequal cost between similar destinations, <strong>the</strong><br />

lowest cost link is preferred. If <strong>the</strong> lowest cost link is down, <strong>the</strong><br />

next lowest cost link will be used.<br />

The price that must be paid for <strong>the</strong>se advantages is <strong>the</strong> requirement<br />

for more processing power and memory than is needed for distance<br />

vec<strong>to</strong>r pro<strong>to</strong>cols. OSPF is an Open Systems pro<strong>to</strong>col and an open<br />

standard (that is, in <strong>the</strong> public domain). It was introduced by <strong>the</strong><br />

Internet Engineering Task Force (IETF) in 1989 in RFC 1131 (OSPF<br />

v1), and made a standard in RFC 2328 (OSPF v2). OSPF was intended<br />

<strong>to</strong> be an updated Open Systems alternative <strong>to</strong> RIP and <strong>to</strong> provide an<br />

Open Systems alternative <strong>to</strong> Cisco's proprietary IGRP and EIGRP<br />

pro<strong>to</strong>cols.

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

Saved successfully!

Ooh no, something went wrong!