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.

outer in <strong>the</strong> process. The idea behind <strong>the</strong> default-<strong>network</strong> is <strong>to</strong> send external traffic<br />

not <strong>to</strong> a specific gateway, but ra<strong>the</strong>r <strong>to</strong> a default <strong>network</strong> where <strong>the</strong> gateway can be<br />

determined (in <strong>the</strong> case of multiple <strong>network</strong> exit points) by <strong>the</strong> locally attached<br />

router. It should be noted that a default gateway setting using <strong>the</strong> may be required on <strong>the</strong> actual outbound<br />

gateway that is attached <strong>to</strong> <strong>the</strong> default <strong>network</strong>.<br />

EIGRP Specific Configuration Options<br />

EIGRP's support of IP summary-address announcements has an impact on CIDR<br />

supernets. Although it is recommended that you disable classful summarizations or<br />

avoid classful summarization al<strong>to</strong>ge<strong>the</strong>r, if you use CIDR supernetting with a class C<br />

address space (not uncommon with sites that use small regional ISPs for Internet<br />

access), you will need <strong>to</strong> use summary announcements in order <strong>to</strong> have EIGRP<br />

announce <strong>the</strong> superset correctly. IP summarizations are configured using <strong>the</strong><br />

interface configuration subcommand . Here is an<br />

example: The ISP for <strong>the</strong> Albany <strong>network</strong> (refer <strong>to</strong> Figure 10.1) has provided four<br />

class C addresses <strong>to</strong> support a <strong>network</strong> expansion that will be attached <strong>to</strong> asbr-2a.<br />

The addresses were assigned as a single /22:<br />

192.168.4.0 /22 = 192.168.4.0, 192.168.5.0, 192.168.6.0, 192.168.7.0<br />

Moreover, we want <strong>to</strong> maintain this address provisioning. Under normal operation,<br />

EIGRP would announce each class C <strong>network</strong> as a separate route entry, even though<br />

<strong>the</strong> address block is being used as a contiguous CIDR superblock. By using an<br />

aggregate summary address, <strong>the</strong> 192.168.4.0 /22 <strong>network</strong> is announced correctly<br />

as a supernet:<br />

asbr-a2(config)#int e2/0<br />

asbr-a2(config-if)#ip address 192.168.4.1 255.255.252.0<br />

asbr-a2(config-if)#ip summary-address eigrp 99 192.168.4.1 255.255.252.0<br />

Using <strong>the</strong> command we can see <strong>the</strong> summarization listed<br />

(notice that au<strong>to</strong>-summarization has been disabled):<br />

Routing Pro<strong>to</strong>col is "eigrp 99"<br />

Outgoing update filter list for all interfaces is not set

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

Saved successfully!

Ooh no, something went wrong!