Skip to main content

EIGRP Concept / Comparing EIGRP and IGRP

EIGRP Concept 
Comparing EIGRP and IGRP
3.1.1

Cisco released EIGRP in 1994 as a scalable and improved version of its proprietary distance vector routing protocol, IGRP. This page will explain how EIGRP and IGRP compare to each other. The distance vector technology and distance information found in IGRP is also used in EIGRP.
EIGRP has improved convergence properties and operates more efficiently over IGRP. This allows a network to have improved architecture as well as retain the current investment in IGRP.
The comparisons between EIGRP and IGRP fall into the following major categories:
  • Compatibility mode
  • Metric calculation
  • Hop count
  • Automatic protocol redistribution
  • Route tagging
IGRP and EIGRP are compatible with each other. This compatibility provides seamless interoperability with IGRP routers. This is important as users can take advantage of the benefits of both protocols. EIGRP offers multiprotocol support, but IGRP does not.
EIGRP and IGRP use different metric calculations. EIGRP scales the metric of IGRP by a factor of 256. That is because EIGRP uses a metric that is 32 bits long, and IGRP uses a 24-bit metric. EIGRP can multiply or divide by 256 to easily exchange information with IGRP.
IGRP has a maximum hop count of 255. EIGRP has a maximum hop count limit of 224. This is more than adequate to support large, properly designed internetworks.
To enable dissimilar routing protocols such as OSPF and RIP to share information requires advanced configuration. Redistribution, or route sharing, is automatic between IGRP and EIGRP as long as both processes use the same AS number. In Figure , RTB automatically redistributes routes learned from EIGRP to the IGRP AS, and vice versa.
EIGRP tags routes learned from IGRP or any outside source as external because they did not originate from EIGRP routers. IGRP cannot differentiate between internal and external routes.
Notice that in the show ip route command output for the routers in Figure , EIGRP routes are flagged with D, and external routes are denoted by EX. RTA identifies the difference between the 172.16.0.0 network, which was learned through EIGRP, and the 192.168.1.0 network that was redistributed from IGRP. In the RTC table, the IGRP protocol makes no such distinction. RTC, which uses IGRP only, just sees IGRP routes, despite the fact that both 10.1.1.0 and 172.16.0.0 were redistributed from EIGRP.
The Interactive Media Activity will help students recognize the characteristics of IGRP and EIGRP.
The next page will explain EIGRP in greater detail.

Comments

Popular posts from this blog

OSI layers / Peer-to-peer communications / TCP/IP model

OSI layers 2.3.4 This page discusses the seven layers of the OSI model. The OSI reference model is a framework that is used to understand how information travels throughout a network. The OSI reference model explains how packets travel through the various layers to another device on a network, even if the sender and destination have different types of network media. In the OSI reference model, there are seven numbered layers, each of which illustrates a particular network function. - Dividing the network into seven layers provides the following advantages: • It breaks network communication into smaller, more manageable parts. • It standardizes network components to allow multiple vendor development and support. • It allows different types of network hardware and software to communicate with each other. • It prevents changes in one layer from affecting other layers. • It divides network communication into smaller parts to make learning it easier to understand. In the foll...

Advantages and disadvantages of link-state routing

Advantages and disadvantages of link-state routing 2.1.5  This page lists the advantages and disadvantages of link-state routing protocols. The following are advantages of link-state routing protocols:  Link-state protocols use cost metrics to choose paths through the network. The cost metric reflects the capacity of the links on those paths. Link-state protocols use triggered updates and LSA floods to immediately report changes in the network topology to all routers in the network. This leads to fast convergence times. Each router has a complete and synchronized picture of the network. Therefore, it is very difficult for routing loops to occur. Routers use the latest information to make the best routing decisions. The link-state database sizes can be minimized with careful network design. This leads to smaller Dijkstra calculations and faster convergence. Every router, at the very least, maps the topology of it...

Ports for services

Ports for services 10.2.2  Services running on hosts must have a port number assigned to them so communication can occur. A remote host attempting to connect to a service expects that service to use specific transport layer protocols and ports. Some ports, which are defined in RFC 1700, are known as the well-known ports. These ports are reserved in both TCP and UDP.  These well-known ports define applications that run above the transport layer protocols. For example, a server that runs FTP will use ports 20 and 21 to forward TCP connections from clients to its FTP application. This allows the server to determine which service a client requests. TCP and UDP use port numbers to determine the correct service to which requests are forwarded. The next page will discuss ports in greater detail.