19.07.2013 Views

CCNA Complete Guide 2nd Edition.pdf - Cisco Learning Home

CCNA Complete Guide 2nd Edition.pdf - Cisco Learning Home

CCNA Complete Guide 2nd Edition.pdf - Cisco Learning 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.

- The only limitation of EIGRP is that it is <strong>Cisco</strong>-proprietary, which means it cannot be<br />

implemented in environments with routers from various vendors. Anyway, a possible solution is<br />

route redistribution, where a router exchanges routes between 2 routing protocols.<br />

- EIGRP is suitable for very large networks. These networks are normally divided into multiple<br />

EIGRP autonomous systems (ASs). Route information can be shared among different ASs via<br />

redistribution. Internal EIGRP routes (AD = 90), are routes that originated by EIGRP routers<br />

within an AS. Another type of routes – external EIGRP routes (AD = 170), are routes that<br />

originated from another EIGRP AS, or redistributed from another routing protocol, eg: OSPF.<br />

Note: The maximum hop count for EIGRP (and IGRP) is 255, with the default value 100. The<br />

metric maximum-hops {hop-count} router subcommand can be used to change this value.<br />

- IGRP, OSPF, and EIGRP features comparison chart:<br />

Feature IGRP OSPF EIGRP<br />

Discover neighbors before exchanging routing information No Yes Yes<br />

Build some form of topology table besides the routing table No Yes Yes<br />

Converge quickly No Yes Yes<br />

Calculate metric based on bandwidth and delay (by default) Yes No. Cost Yes<br />

Send full routing information on every routing update cycle Yes No No<br />

Implement distance-vector loop-avoidance features Yes No No<br />

Public standard No Yes No<br />

- RIPv2, OSPF, and EIGRP support variable length subnet mask and discontiguous networks.<br />

When selecting the suitable routing protocol to be implemented on a network environment, the<br />

simplest routing protocol that meets the requirements should be selected.<br />

Type of Network Suitable Routing Protocol<br />

- No redundant links or parallel paths.<br />

RIPv1<br />

- Not requires VLSM or discontiguous subnets.<br />

- Has redundant links or parallel paths.<br />

- Not requires VLSM or discontiguous subnets.<br />

- No redundant links or parallel paths.<br />

- Requires VLSM and/or support of discontiguous subnets.<br />

- Has redundant links or parallel paths.<br />

- Requires VLSM and/or support of discontiguous subnets.<br />

97<br />

IGRP<br />

RIPv2<br />

OSPF or EIGRP<br />

- Discontiguous networks are networks that have subnets of a major network separated by a<br />

different major network. Figure 13-3A shows a typical discontiguous network where subnets<br />

172.16.10.0 and 172.16.20.0 are connected together with (or separated by) a 10.1.1.0 network.<br />

Discontiguous networks won’t ever work with RIPv1 and IGRP; and they don’t work by default<br />

with RIPv2 and EIGRP as well, as they perform autosummarization by default.<br />

172.16.10.0/24 172.16.20.0/24<br />

10.1.1.0/24<br />

172.16.10.0/24 172.16.20.0/24<br />

172.17.10.0/24<br />

Figure 13-3: Sample Discontiguous Networks<br />

192.168.1.0/26 192.168.1.64/26<br />

192.168.2.0/24<br />

Figure 13-3A Figure 13-3B Figure 13-3C<br />

Copyright © 2008 Yap Chin Hoong<br />

yapchinhoong@hotmail.com

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

Saved successfully!

Ooh no, something went wrong!