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.

EIGRP). In addition, like IGRP and EIGRP, it is possible <strong>to</strong> run multiple OSPF<br />

instances. This should only be done in special circumstances and generally avoided.<br />

Each OSPF process builds its own <strong>to</strong>pological database and has its own routing<br />

algorithm process, so running multiple OSPF instances adds unneeded load <strong>to</strong> <strong>the</strong><br />

router.<br />

Where OSPF differs from a configuration standpoint is in <strong>the</strong> way <strong>the</strong> <strong>network</strong><br />

announcements are entered. OSPF is a true classless pro<strong>to</strong>col. When configuring<br />

RIPv2, EIGRP, and so on, <strong>network</strong>s are entered (and listed in <strong>the</strong> configuration)<br />

using <strong>the</strong>ir natural classful boundaries. OSPF provides <strong>the</strong> capability <strong>to</strong> enter <strong>the</strong><br />

<strong>network</strong> announcements in <strong>the</strong>ir classless form, along with a <strong>network</strong> mask <strong>to</strong><br />

interpret <strong>the</strong> <strong>network</strong> address. One thing about <strong>the</strong> netmask: It is entered in reverse<br />

form, just like access lists. Also, like access lists, <strong>the</strong> same calculation formula is<br />

used <strong>to</strong> calculate <strong>the</strong> reverse mask:<br />

255.255.255.255<br />

-255.255.252.0 (Subnet mask)<br />

—————————<br />

0. 0. 3.255 (Reverse mask)<br />

The capability <strong>to</strong> enter <strong>the</strong> <strong>network</strong> and mask gives you a lot of flexibility in terms of<br />

how <strong>network</strong>s are announced. With o<strong>the</strong>r IGP pro<strong>to</strong>cols, <strong>network</strong> summarization<br />

can present problems, especially in large inter<strong>network</strong>s where classless addressing<br />

is used extensively. To address this problem, summarization is disabled with <strong>the</strong><br />

router configuration subcommand . OSPF does not summarize<br />

unless you configure it <strong>to</strong>.<br />

In large LANs where subnetting is used and <strong>the</strong> possibility of discontinuous subnets<br />

exists, au<strong>to</strong>-summarization can be a pain. In a large inter<strong>network</strong>, however,<br />

summarization is an efficiency gain, since summarization reduces <strong>the</strong> number of<br />

routes required in <strong>the</strong> routing table. On large inter<strong>network</strong>s, whenever possible, you<br />

want <strong>to</strong> deploy your <strong>network</strong> address space using classless boundaries that can be<br />

treated as CIDR supernets. This makes it easy <strong>to</strong> use CIDR addressing <strong>to</strong> summarize<br />

<strong>network</strong> announcements. Establishing an effective <strong>network</strong> addressing hierarchy is<br />

essential for OSPF <strong>to</strong> function efficiently.<br />

NOTE<br />

A situation where multiple OSPF processes might be desirable is when <strong>the</strong> router is<br />

acting as gateway between two separate inter<strong>network</strong>s. A common example would<br />

be if OSPF was being used as an EGP by a <strong>network</strong> service provider and as an IGP by<br />

a client. The client gateway router would run both an internal and external OSPF

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

Saved successfully!

Ooh no, something went wrong!