IGRP

Interior Gateway Routing Protocol is a Cisco-proprietary distance vector routing protocol. This means that to use IGRP in your network, all your routers must be Cisco Routers. Cisco created this routing protocol to overcome the problems associated with RIP.

IGRP has a maximum hop count of 255 with the default of 100 (same as EIGRP). This enables IGRP to be used in larger networks and is not limited to smaller networks with 15 hops as in the case of RIP.

The metric used by IGRP is also different from RIP. IGRP uses a combination of path characteristics, such as bandwidth and delay by default to calculate the metric. This type of metric is called composite metric. IGRP can also be use reliability, load and maximum transmission unit (MTU).

IGRP also provides various timers such as Update timers, Invalid timers, hold-down timers, flush timers to control performance. These are explained below:

(i) Update Timers

Update timer specifies how frequently routing update messages should be sent to the neighboring routers. Its default value is 90 seconds.

(ii) Invalid Timers

Invalid timer specifies how long a router should wait before declaring a route as invalid if it doesn’t receive an update about that route. Its default value is three times the update period. That means if the update timer is 90 seconds then the value of invalid timer will be sent to 270 seconds.

(iii) Hold-down timers

Hold-down timer specifies the hold-down period. Its default value is three times the update timer period plus 10 seconds. The hold-down timer will be 270 seconds plus 10 seconds that is 280 seconds.

(iv) Flush Timers

Flush timer specifies how much time should pass before a route should be deleted from the routing table. Its default value is seven times the update times. Therefore, the value of flush timer will be set to 630 seconds.

Difference between IGRP Vs RIP

Lab Practice:

Procedure:

1. Configuring and Assigning the IP addresses on the Router R! and R2.

2. Check the routing table on both the routers.

3. Enable the IGRP protocol on both routers so that hosts on the both routers can communicate with each other.

4. Verifying the Routing protocols on the Router.

5. Check the routing table on both the routers after enabling the IGRP on both routers after enabling the IGRP on both sides.

6. Verifying the connection of both hosts.

Configuration:


Step1 (A): Assigning the IP addresses on the Ethernet and Serial Interfaces of Router R1 as shown in the figure.

Step1 (B): Assigning the IP addresses on the Ethernet and Serial Interfaces of Router R2 as shown in the figure.

Step2(A): Check the Routing table of the router R1.
                 R1#sh ip route

             C 10.0.0.0/8 is directly connected, Ethernet 0
             C 15.0.0.0/8 is directly connected, Serial 0

Step2 (B):Check the routing table of router R2.
                 R2#sh ip route


             C 20.0.0.0/8 is directly connected, Ethernet 0
             C 15.0.0.0/8 is directly connected, Serial 0

Step3 (A): Enable the IGRP protocol on the Router R1.
                R1(config)#router igrp 10
                R1(config-router)#network 10.0.0.0
                R1(config-router)#network 15.0.0.0

Step3 (B): Enable the IGRP on the router R2.
                R2(config)#router igrp 10
                R2(config-router)#network 20.0.0.0
                R2(config-router)#network 15.0.0.0

Step 4(A): Check the routing protocol on the router R1.
               R1#show ip protocols

Routing protocol is “IGRP 10”
Sending updates every 90 seconds, next due in 38 seconds, Invalid after 270 seconds, hold down 280 seconds, flush after 630 seconds.

IGRP metric weight K1=1, K2=0, K3=1, K4=0, K5=0

IGRP maximum hop count 100

IGRP maximum metric variance 1

Step4 (B): Check the routing protocols on the router R2.
                R2#show ip protocols

      Routing protocol is “IGRP 10”

Sending updates every 90 seconds, next due in 38 seconds, Invalid after 270 seconds, hold down 280 seconds, flush after 630 seconds.

IGRP metric weight K1=1, K2=0, K3=1, K4=0, K5=0

IGRP maximum hop count 100

IGRP maximum metric variance 1

Step5 (A): Check the Routing table after enabling the IGRP on router R1.
                 R1#sh ip route
         I 20.0.0.0/8[100/8576]via 15.0.0.2, 00:01:09, serial 0
        C 10.0.0.0/8 is directly connected, Ethernet 0
        C 15.0.0.0/8 is directly connected, Serial 0

Step5 (B): Check the Routing table after enabling the IGRP on router R2.
                 R2#sh ip route
          I 10.0.0.0/8[100/8576]via 15.0.0.1, 00:01:09, serial 0
         C 20.0.0.0/8 is directly connected, Ethernet 0
         C 15.0.0.0/8 is directly connected, Serial 0

Step 6: Verifying the connection of Host ‘A’ & Host ‘B’

C:\> ping 20.0.0.1

Routing Information Protocol (RIP)

RIP is an Open Standard Protocol based on a version that was developed at the University of California at Berkeley and was officially defined in June 1988 under Request for Comment (RFC) 1058. RIP is relatively simple distance routing protocol categorized under the family if IGP’s meaning that it performs routing within a single Autonomous System.

RIP uses hop counts as its metric to calculate the distance between the source and the destination network. Each router in a RIP network is counted as one hop. RIP implements a maximum hop count of 15. This means that a packet will never pass through more than 15 routers, because it will be discarded by the sixteenth. By using a maximum hop count, a packet will never be used in an environment that has 2 segments separated by more than 15 routers.

RIP operates by automatically sending routing updates every 30 seconds and whenever the routing table changes. A RIP update contains an entire copy of the router’s routing table. When a router receives a routing update it updates its routing table to reflect the changes.

RIP works well in small networks, but it is inefficient on large networks with slow WAN links or on networks with a large numbers of routers installed.

RIP Timers


• Routing update timer
The routing update timer is defined as the time between which routing table updates are sent to neighboring routers. A RIP routing table update sends a copy of the entire routing table to its neighbors and not just the table changes. The routing update timer is set to happen every 30 seconds.

• Route timeout timer
The router maintains a timeout timer for each entry in the routing table, which is 90 seconds by default. If a router has an entry for a particular destination network and it has not received an update about this network in a specified amount of time, the router will assume that this route has become invalid. When this expires, the router will send an update to its neighbors letting them know that this route has timed out.

• Route flush timer
After a route for a destination network is timed out from the routing table it is not removed from the routing table immediately. Instead the router waits till the flush timer (its default value is 240 seconds), which is the amount of time between when a route has become invalid and the time it’s actually removed from the routing table.