20.01.2013 Views

CCNA 3 Labs and Study Guide - BINARYBB.INFO – @jagalbraith

CCNA 3 Labs and Study Guide - BINARYBB.INFO – @jagalbraith

CCNA 3 Labs and Study Guide - BINARYBB.INFO – @jagalbraith

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.

Vocabulary Exercise: Completion<br />

Directions: Complete the paragraphs that follow by filling in appropriate words <strong>and</strong> phrases.<br />

IGRP <strong>and</strong> EIGRP are compatible with each other, which provides seamless interoperability between the<br />

two processes. EIGRP uses metric calculations similar to those used by IGRP, <strong>and</strong> EIGRP supports the<br />

same unequal-cost path load balancing as IGRP does.<br />

Although the metric (b<strong>and</strong>width <strong>and</strong> delay by default) is the same for both IGRP <strong>and</strong> EIGRP, the weight<br />

assigned to the metric is 256 times greater for EIGRP. That is because EIGRP uses a metric that is 32 bits<br />

long, <strong>and</strong> IGRP uses a 24-bit metric. By multiplying or dividing by 256, EIGRP can easily exchange information<br />

with IGRP.<br />

IGRP has a maximum hop count of 255. EIGRP has a maximum hop count of 224. By default, the Cisco<br />

IOS limits the hop count for EIGRP limited to 100 as displayed by the show ip protocols comm<strong>and</strong>. This<br />

is more than adequate to support the largest, properly designed internetworks.<br />

EIGRP’s convergence technology employs the Diffusing Update Algorithm (DUAL), which guarantees<br />

loop-free operation at every instant throughout a route. Routers that are not affected by topology changes<br />

are not involved in recomputations.<br />

Redistribution, the sharing of routes, is automatic between IGRP <strong>and</strong> EIGRP as long as both processes use<br />

the same autonomous system number.<br />

Like OSPF, EIGRP maintains three tables for use with its computations. These tables include the neighbor<br />

table (called the adjacency database in OSPF), the topology table (called the link-state database in OSPF),<br />

<strong>and</strong> the routing table (called the forwarding database in OSPF).<br />

The following are some additional features of EIGRP:<br />

■ EIGRP converges rapidly on network topology changes. In some situations, convergence can be<br />

almost instantaneous. EIGRP stores backup routes, called feasible successors, so that it can quickly<br />

adapt to these alternate routes if the primary route, called the successor, becomes unavailable. If no<br />

backup route exists, then EIGRP sends a query packet to its neighbors to discover an alternate route.<br />

■ During normal operations when the network topology is fully converged, only hello packets are sent<br />

to neighbors. These packets are also used to establish neighbor adjacencies.<br />

■ EIGRP supports automatic route summarization at classful network boundaries. But it can be manually<br />

configured to advertise on arbitrary network boundaries to reduce the size of routing tables.<br />

■ EIGRP uses its own Layer 4 protocol called the Reliable Transport Protocol. Because EIGRP provides<br />

support for multiple routed protocols, including AppleTalk (AT) <strong>and</strong> Internetwork Packet Exchange<br />

(IPX), it must be protocol independent. That means it cannot depend on TCP for reliability services.<br />

EIGRP Packet Type Exercise<br />

Like OSPF, EIGRP relies on different types of packets to maintain its tables <strong>and</strong> establish relationships<br />

with neighbor routers. Complete the missing elements that follow by filling in appropriate words or phrases.<br />

When given the choice, circle whether the packet is reliable or unreliable <strong>and</strong> whether it is unicast or<br />

multicast.<br />

Hello packets:<br />

■ (Reliable/Unreliable) (unicast/multicast) sent to the address 224.0.0.10 to discover <strong>and</strong> maintain<br />

neighbors; contains the router’s neighbor table<br />

■ Default hello interval depends on the b<strong>and</strong>width:<br />

— ≤ 1.544 Mbps = 60 sec. hello interval (180 sec. holdtime)<br />

— > 1.544 Mbps = 5 sec. hello interval (15 sec. holdtime)<br />

Chapter 3: EIGRP <strong>and</strong> Troubleshooting Routing Protocols 177

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

Saved successfully!

Ooh no, something went wrong!