Header GIF
Site is Under Maintenance
Please come back again in...
00 Days
00 Hours
00 Minutes
00 Seconds
Home
• Networking Fundamentals Tutorial •
• Route Redistribution •

Configuring Mutual EIGRP & RIP Redistribution Tutorial

<html><head><meta charset="utf-8"></meta><title>configuring-mutual-eigrp-and-rip-redistribution.htm</title><style></style></head><body id="preview">
<h1 class="code-line" data-line-end="1" data-line-start="0"><a id="Configuring_Mutual_EIGRP__RIP_Redistribution_0"></a>Configuring Mutual EIGRP &amp; RIP Redistribution</h1>
<p class="has-line-data" data-line-end="3" data-line-start="2">Mututal redistribution is commonly done to fix architectural problems or during company acquisitions. This lab will discuss and demonstrate the configuration and verification of mutual EIGRP and RIP redistribution.</p>
<h2 class="code-line" data-line-end="5" data-line-start="4"><a id="Real_World_Application__Core_Knowledge_4"></a>Real World Application &amp; Core Knowledge</h2>
<p class="has-line-data" data-line-end="7" data-line-start="6">If you’ve completed <a href="/workbooks/ccna/configuring-mutual-ospf-and-rip-redistribution/">Lab 10-2 – Configuring Mutual OSPF and RIP Redistribution</a> and <a href="/workbooks/ccna/configuring-mutual-ospf-and-eigrp-redistribution/">Lab 10-3 – Configuring Mutual OSPF and EIGRP Redistribution</a> then you should be no stranger to mutual route redistribution.</p>
<p class="has-line-data" data-line-end="9" data-line-start="8">If you did not complete the previous labs then to summarize mutual route redistribution up in a pretty little nut shell; mutual route redistribution is the process where two dynamic routing protocols exchange their routes with each other. For example, When you redistribute EIGRP into RIP, all routes in the EIGRP Autonomous System will be injected into the RIP database and show up as regular RIP routes. The same concepts apply to EIGRP when you redistribute RIP into EIGRP, all the routes from RIP will be injected into the EIGRP topology table and advertised through out the autonomous system as an EIGRP External route. These routes are denoted as “D EX” routes in the routing table.</p>
<p class="has-line-data" data-line-end="11" data-line-start="10">Mutual route redistribution is a common remedy when companies acquire other companies that use different routing protocols. In such case Company ABC Inc. acquires Company XYZ Inc. however ABC Inc. uses EIGRP and XYZ Inc. uses RIP. After the acquisition, the CTO (Chief Technology Officer) Mandates that there be full network communication between the newly merged companies. In this case you’d need to perform mutual redistribution to ensure ABC Inc. has routes to XYZ’s network; vice-versa.</p>
<p class="has-line-data" data-line-end="13" data-line-start="12">When you configure mutual route redistribution its best practice to specify a static metric. When specifying a metric keep in mind if you have multiple routers performing mutual redistribution you may need to have a higher metric on one router then the other to prevent a routing loop; this is where packets just keep going in circles between the two autonomous systems. It’s a safe bet to specify a fairly high metric in a production network to prevent such routes from becoming looped as lower metric routes are preferred.</p>
<p class="has-line-data" data-line-end="15" data-line-start="14">To configure route redistribution you’ll use the redistribute command in router configuration mode.</p>
<p class="has-line-data" data-line-end="17" data-line-start="16">Please review the following command(s) listed below;</p>
<p class="has-line-data" data-line-end="20" data-line-start="18">| Command | Description |<br />
| redistribute &lt;i&gt;protocol&lt;/i&gt; metric &lt;i&gt;{metric info}&lt;/i&gt; | This command is executed in router configuration mode of RIP, EIGRP or OSPF to configure the routing process to redistribute routes from a different source into the configured routing process such as static into RIP or RIP into OSPF. It’s best practice to specify a metric; when specifying a metric you specify a metric to be used by the routes when they appear in the routing process. For example, RIP uses hop counts, OSPF uses cost and EIGRP uses K Values (bandwidth, load, delay, reliability, mtu) |</p>
<p class="has-line-data" data-line-end="22" data-line-start="21">The following logical topology shown below is used in this lab;</p>
<h2 class="code-line" data-line-end="24" data-line-start="23"><a id="Lab_Prerequisites_23"></a>Lab Prerequisites</h2>
<ul>
<li class="has-line-data" data-line-end="26" data-line-start="25">If you are using GNS3 than load the Free CCNA Workbook GNS3 topology than start devices; R1, R2, R3, R4, and R5</li>
<li class="has-line-data" data-line-end="28" data-line-start="26">Establish a console session with devices R1, R2, R3, R4, and R5 than load the initial configurations provided below by copying the config from the textbox and pasting it into the respected routers console.</li>
</ul>
<p class="has-line-data" data-line-end="63" data-line-start="28">!###################################################<br />
!# Free CCNA Workbook Lab 10-4 R1 Initial Config #<br />
!###################################################<br />
!<br />
enable<br />
configure terminal<br />
!<br />
hostname R1<br />
no ip domain-lookup<br />
!<br />
interface Serial0/0<br />
description ### PHYSICAL FRAME RELAY INTERFACE ###<br />
no ip address<br />
encapsulation frame-relay<br />
serial restart-delay 0<br />
no frame-relay inverse-arp<br />
no shut<br />
exit<br />
!<br />
interface Serial0/0.122 point-to-point<br />
description ### FRAME RELAY LINK TO R2 ###<br />
ip address 10.104.12.1 255.255.255.0<br />
frame-relay interface-dlci 122<br />
exit<br />
!<br />
router eigrp 10<br />
no auto-summary<br />
network 10.104.12.1 0.0.0.0<br />
exit<br />
!<br />
line con 0<br />
logging sync<br />
no exec-timeout<br />
!<br />
end</p>
<p class="has-line-data" data-line-end="103" data-line-start="64">!###################################################<br />
!# Free CCNA Workbook Lab 10-4 R2 Initial Config #<br />
!###################################################<br />
!<br />
enable<br />
configure terminal<br />
!<br />
hostname R2<br />
no ip domain-lookup<br />
!<br />
interface Serial0/0<br />
description ### PHYSICAL FRAME RELAY INTERFACE ###<br />
encapsulation frame-relay<br />
no frame-relay inverse-arp<br />
no shut<br />
!<br />
interface Serial0/0.221 point-to-point<br />
description ### FRAME RELAY LINK TO R1 ###<br />
ip address 10.104.12.2 255.255.255.0<br />
frame-relay interface-dlci 221<br />
exit<br />
!<br />
interface Serial0/0.223 point-to-point<br />
description ### FRAME RELAY LINK TO R3 ###<br />
ip address 10.104.23.2 255.255.255.0<br />
frame-relay interface-dlci 223<br />
exit<br />
!<br />
router eigrp 10<br />
no auto-summary<br />
network 10.104.12.2 0.0.0.0<br />
network 10.104.23.2 0.0.0.0<br />
exit<br />
!<br />
line con 0<br />
logging sync<br />
no exec-timeout<br />
!<br />
end</p>
<p class="has-line-data" data-line-end="148" data-line-start="104">!###################################################<br />
!# Free CCNA Workbook Lab 10-4 R3 Initial Config #<br />
!###################################################<br />
!<br />
enable<br />
configure terminal<br />
!<br />
hostname R3<br />
no ip domain-lookup<br />
!<br />
interface Serial0/0<br />
description ### PHYSICAL FRAME RELAY INTERFACE ###<br />
encapsulation frame-relay<br />
no frame-relay inverse-arp<br />
no shut<br />
exit<br />
!<br />
interface Serial0/0.322 point-to-point<br />
description ### FRAME RELAY LINK TO R2 ###<br />
ip address 10.104.23.3 255.255.255.0<br />
frame-relay interface-dlci 322<br />
exit<br />
!<br />
interface Serial0/0.324 point-to-point<br />
description ### FRAME RELAY LINK TO R4 ###<br />
ip address 172.29.34.3 255.255.255.0<br />
frame-relay interface-dlci 324<br />
no shut<br />
!<br />
router eigrp 10<br />
no auto-summary<br />
network 10.104.23.3<br />
exit<br />
!<br />
router rip<br />
no auto-summary<br />
version 2<br />
network 172.29.0.0<br />
!<br />
line con 0<br />
logging sync<br />
no exec-timeout<br />
!<br />
end</p>
<p class="has-line-data" data-line-end="188" data-line-start="149">!###################################################<br />
!# Free CCNA Workbook Lab 10-4 R4 Initial Config #<br />
!###################################################<br />
!<br />
enable<br />
configure terminal<br />
!<br />
hostname R4<br />
no ip domain-lookup<br />
!<br />
interface Serial0/0<br />
description ### PHYSICAL FRAME RELAY INTERFACE ###<br />
encapsulation frame-relay<br />
no frame-relay inverse-arp<br />
no shut<br />
!<br />
interface Serial0/0.423 point-to-point<br />
description ### FRAME RELAY LINK TO R3 ###<br />
ip address 172.29.34.4 255.255.255.0<br />
frame-relay interface-dlci 423<br />
exit<br />
!<br />
interface Serial0/0.425 point-to-point<br />
description ### FRAME RELAY LINK TO R5 ###<br />
ip address 172.29.45.4 255.255.255.0<br />
frame-relay interface-dlci 425<br />
exit<br />
!<br />
router rip<br />
version 2<br />
no auto-summary<br />
network 172.29.0.0<br />
exit<br />
!<br />
line con 0<br />
logging sync<br />
no exec-timeout<br />
!<br />
end</p>
<p class="has-line-data" data-line-end="222" data-line-start="189">!###################################################<br />
!# Free CCNA Workbook Lab 10-4 R5 Initial Config #<br />
!###################################################<br />
!<br />
enable<br />
configure terminal<br />
!<br />
hostname R5<br />
no ip domain-lookup<br />
!<br />
interface Serial0/0<br />
description ### PHYSICAL FRAME RELAY INTERFACE ###<br />
encapsulation frame-relay<br />
no frame-relay inverse-arp<br />
no shut<br />
!<br />
interface Serial0/0.524 point-to-point<br />
description ### FRAME RELAY LINK TO R5 ###<br />
ip address 172.29.45.5 255.255.255.0<br />
frame-relay interface-dlci 524<br />
exit<br />
!<br />
router rip<br />
version 2<br />
no auto-summary<br />
network 172.29.0.0<br />
exit<br />
!<br />
line con 0<br />
logging sync<br />
no exec-timeout<br />
!<br />
end</p>
<h2 class="code-line" data-line-end="224" data-line-start="223"><a id="Lab_Objectives_223"></a>Lab Objectives</h2>
<ul>
<li class="has-line-data" data-line-end="226" data-line-start="225">Create four new loopback interfaces on R1 using the 10.1.0.0/22 address allocation and configure those interfaces to participate in EIGRP Autonomous System 10.</li>
<li class="has-line-data" data-line-end="227" data-line-start="226">Create four new loopback interfaces on R5 using the 172.5.0.0/22 address allocation and configure those interfaces to participate in RIP.</li>
<li class="has-line-data" data-line-end="228" data-line-start="227">Analyze R3’s routing table and verify that the newly created loopback interfaces are being learned by R3.</li>
<li class="has-line-data" data-line-end="229" data-line-start="228">Configure R3 to redistribute EIGRP routes into RIP using a hop count of 3 then redistribute RIP routes into EIGRP using a T1 bandwidth and 20,000 microsecond delay.</li>
<li class="has-line-data" data-line-end="231" data-line-start="229">Verify on R1 and R5 that routes from the opposite autonomous system exist in their routing table.</li>
</ul>
<h2 class="code-line" data-line-end="232" data-line-start="231"><a id="Lab_Instruction_231"></a>Lab Instruction</h2>
<p class="has-line-data" data-line-end="234" data-line-start="233">Objective 1. – Create four new loopback interfaces on R1 using the 10.1.0.0/22 address allocation and configure those interfaces to participate in EIGRP Autonomous System 10.</p>
<pre><code class="has-line-data" data-line-end="257" data-line-start="236">R1#configure terminal
Enter configuration commands, one per line.  End with CNTL/Z.
R1(config)#interface loopback0
R1(config-if)#ip address 10.1.0.1 255.255.255.0
R1(config-if)#
R1(config-if)#interface loopback1
R1(config-if)#ip address 10.1.1.1 255.255.255.0
R1(config-if)#
R1(config-if)#interface loopback2
R1(config-if)#ip address 10.1.2.1 255.255.255.0
R1(config-if)#
R1(config-if)#interface loopback3
R1(config-if)#ip address 10.1.3.1 255.255.255.0
R1(config-if)#exit
R1(config)#
R1(config)#router eigrp 10
R1(config-router)#network 10.1.0.0 0.0.3.255
R1#
%SYS-5-CONFIG_I: Configured from console by console
R1#
</code></pre>
<p class="has-line-data" data-line-end="259" data-line-start="258">&lt;br&gt;</p>
<p class="has-line-data" data-line-end="261" data-line-start="260">Objective 2. – Create four new loopback interfaces on R5 using the 172.5.0.0/22 address allocation and configure those interfaces to participate in RIP.</p>
<pre><code class="has-line-data" data-line-end="284" data-line-start="263">R5#configure terminal
Enter configuration commands, one per line.  End with CNTL/Z.
R5(config)#interface loopback0
R5(config-if)#ip address 172.5.0.1 255.255.255.0
R5(config-if)#
R5(config-if)#interface loopback1
R5(config-if)#ip address 172.5.1.1 255.255.255.0
R5(config-if)#
R5(config-if)#interface loopback2
R5(config-if)#ip address 172.5.2.1 255.255.255.0
R5(config-if)#
R5(config-if)#interface loopback3
R5(config-if)#ip address 172.5.3.1 255.255.255.0
R5(config-if)#exit
R5(config)#router rip
R5(config-router)#network 172.5.0.0
R5(config-router)#end
R5#
%SYS-5-CONFIG_I: Configured from console by console
R5#
</code></pre>
<p class="has-line-data" data-line-end="286" data-line-start="285">Objective 3. – Analyze R3’s routing table and verify that the newly created loopback interfaces are being learned by R3.</p>
<pre><code class="has-line-data" data-line-end="315" data-line-start="288">R3#show ip route
Codes: C - connected, S - static, R - RIP, M - mobile, B - BGP
       D - EIGRP, EX - EIGRP external, O - OSPF, IA - OSPF inter area
       N1 - OSPF NSSA external type 1, N2 - OSPF NSSA external type 2
       E1 - OSPF external type 1, E2 - OSPF external type 2
       * - candidate default, U - per-user static route
       o - ODR, P - periodic downloaded static route

Gateway of last resort is not set

     172.5.0.0/24 is subnetted, 4 subnets
R       172.5.1.0 [120/2] via 172.29.34.4, 00:00:25, Serial0/0.324
R       172.5.0.0 [120/2] via 172.29.34.4, 00:00:25, Serial0/0.324
R       172.5.3.0 [120/2] via 172.29.34.4, 00:00:25, Serial0/0.324
R       172.5.2.0 [120/2] via 172.29.34.4, 00:00:25, Serial0/0.324
     172.29.0.0/24 is subnetted, 2 subnets
C       172.29.34.0 is directly connected, Serial0/0.324
R       172.29.45.0 [120/1] via 172.29.34.4, 00:00:25, Serial0/0.324
     10.0.0.0/24 is subnetted, 6 subnets
D       10.1.3.0 [90/2809856] via 10.104.23.2, 00:05:50, Serial0/0.322
D       10.1.2.0 [90/2809856] via 10.104.23.2, 00:05:50, Serial0/0.322
D       10.1.1.0 [90/2809856] via 10.104.23.2, 00:05:50, Serial0/0.322
D       10.1.0.0 [90/2809856] via 10.104.23.2, 00:05:50, Serial0/0.322
D       10.104.12.0 [90/2681856] via 10.104.23.2, 00:09:59, Serial0/0.322
C       10.104.23.0 is directly connected, Serial0/0.322
R3#
</code></pre>
<p class="has-line-data" data-line-end="317" data-line-start="316">Objective 4. – Configure R3 to redistribute EIGRP routes into RIP using a hop count of 3 then redistribute RIP routes into EIGRP using a T1 bandwidth and 20,000 microsecond delay.</p>
<pre><code class="has-line-data" data-line-end="347" data-line-start="319">R3#configure terminal
Enter configuration commands, one per line.  End with CNTL/Z.
R3(config)#router rip
R3(config-router)#redistribute eigrp 10 metric 3
R3(config-router)#exit
R3(config)#router eigrp 10
R3(config-router)#redistribute rip metric ?
    Bandwidth metric in Kbits per second

R3(config-router)#redistribute rip metric 1544 ?
    EIGRP delay metric, in 10 microsecond units

R3(config-router)#redistribute rip metric 1544 2000 ?
    EIGRP reliability metric where 255 is 100% reliable

R3(config-router)#redistribute rip metric 1544 2000 255 ?
    EIGRP Effective bandwidth metric (Loading) where 255
is 100% loaded

R3(config-router)#redistribute rip metric 1544 2000 255 1 ?
    EIGRP MTU of the path

R3(config-router)#redistribute rip metric 1544 2000 255 1 1500
R3(config-router)#end
R3#
%SYS-5-CONFIG_I: Configured from console by console
R3#
</code></pre>
<p class="has-line-data" data-line-end="349" data-line-start="348">Objective 5. – Verify on R1 and R5 that routes from the opposite autonomous system exist in their routing table.</p>
<pre><code class="has-line-data" data-line-end="378" data-line-start="351">R1#show ip route
Codes: C - connected, S - static, R - RIP, M - mobile, B - BGP
       D - EIGRP, EX - EIGRP external, O - OSPF, IA - OSPF inter area
       N1 - OSPF NSSA external type 1, N2 - OSPF NSSA external type 2
       E1 - OSPF external type 1, E2 - OSPF external type 2
       * - candidate default, U - per-user static route
       o - ODR, P - periodic downloaded static route

Gateway of last resort is not set

     172.5.0.0/24 is subnetted, 4 subnets
D EX    172.5.1.0 [170/3193856] via 10.104.12.2, 00:00:09, Serial0/0.122
D EX    172.5.0.0 [170/3193856] via 10.104.12.2, 00:00:09, Serial0/0.122
D EX    172.5.3.0 [170/3193856] via 10.104.12.2, 00:00:09, Serial0/0.122
D EX    172.5.2.0 [170/3193856] via 10.104.12.2, 00:00:09, Serial0/0.122
     172.29.0.0/24 is subnetted, 2 subnets
D EX    172.29.34.0 [170/3193856] via 10.104.12.2, 00:00:09, Serial0/0.122
D EX    172.29.45.0 [170/3193856] via 10.104.12.2, 00:00:09, Serial0/0.122
     10.0.0.0/24 is subnetted, 6 subnets
C       10.1.3.0 is directly connected, Loopback3
C       10.1.2.0 is directly connected, Loopback2
C       10.1.1.0 is directly connected, Loopback1
C       10.1.0.0 is directly connected, Loopback0
C       10.104.12.0 is directly connected, Serial0/0.122
D       10.104.23.0 [90/2681856] via 10.104.12.2, 00:11:13, Serial0/0.122
R1#
</code></pre>
<p class="has-line-data" data-line-end="380" data-line-start="379">You can see from R1’s routing table shown above that the RIP routes redistributed into EIGRP at R3 are being propagated throughout the EIGRP Autonomous System as EIGRP External routes.</p>
<pre><code class="has-line-data" data-line-end="409" data-line-start="382">R5#show ip route
Codes: C - connected, S - static, R - RIP, M - mobile, B - BGP
       D - EIGRP, EX - EIGRP external, O - OSPF, IA - OSPF inter area
       N1 - OSPF NSSA external type 1, N2 - OSPF NSSA external type 2
       E1 - OSPF external type 1, E2 - OSPF external type 2
       * - candidate default, U - per-user static route
       o - ODR, P - periodic downloaded static route

Gateway of last resort is not set

     172.5.0.0/24 is subnetted, 4 subnets
C       172.5.1.0 is directly connected, Loopback1
C       172.5.0.0 is directly connected, Loopback0
C       172.5.3.0 is directly connected, Loopback3
C       172.5.2.0 is directly connected, Loopback2
     172.29.0.0/24 is subnetted, 2 subnets
R       172.29.34.0 [120/1] via 172.29.45.4, 00:00:20, Serial0/0.524
C       172.29.45.0 is directly connected, Serial0/0.524
     10.0.0.0/24 is subnetted, 6 subnets
R       10.1.3.0 [120/4] via 172.29.45.4, 00:00:21, Serial0/0.524
R       10.1.2.0 [120/4] via 172.29.45.4, 00:00:21, Serial0/0.524
R       10.1.1.0 [120/4] via 172.29.45.4, 00:00:21, Serial0/0.524
R       10.1.0.0 [120/4] via 172.29.45.4, 00:00:21, Serial0/0.524
R       10.104.12.0 [120/4] via 172.29.45.4, 00:00:22, Serial0/0.524
R       10.104.23.0 [120/4] via 172.29.45.4, 00:00:22, Serial0/0.524
R5#
</code></pre>
<p class="has-line-data" data-line-end="411" data-line-start="410">You can see from R5’s routing table shown above that the EIGRP routes redistributed into RIP at R3 are now RIP routes on R5 with a metric of 4 (1 hop to R4 + 3 from R3’s added metric).</p>
</body></html>
configuring-mutual-eigrp-and-rip-redistribution.htm

Configuring Mutual EIGRP & RIP Redistribution

Mututal redistribution is commonly done to fix architectural problems or during company acquisitions. This lab will discuss and demonstrate the configuration and verification of mutual EIGRP and RIP redistribution.

Real World Application & Core Knowledge

If you’ve completed Lab 10-2 – Configuring Mutual OSPF and RIP Redistribution and Lab 10-3 – Configuring Mutual OSPF and EIGRP Redistribution then you should be no stranger to mutual route redistribution.

If you did not complete the previous labs then to summarize mutual route redistribution up in a pretty little nut shell; mutual route redistribution is the process where two dynamic routing protocols exchange their routes with each other. For example, When you redistribute EIGRP into RIP, all routes in the EIGRP Autonomous System will be injected into the RIP database and show up as regular RIP routes. The same concepts apply to EIGRP when you redistribute RIP into EIGRP, all the routes from RIP will be injected into the EIGRP topology table and advertised through out the autonomous system as an EIGRP External route. These routes are denoted as “D EX” routes in the routing table.

Mutual route redistribution is a common remedy when companies acquire other companies that use different routing protocols. In such case Company ABC Inc. acquires Company XYZ Inc. however ABC Inc. uses EIGRP and XYZ Inc. uses RIP. After the acquisition, the CTO (Chief Technology Officer) Mandates that there be full network communication between the newly merged companies. In this case you’d need to perform mutual redistribution to ensure ABC Inc. has routes to XYZ’s network; vice-versa.

When you configure mutual route redistribution its best practice to specify a static metric. When specifying a metric keep in mind if you have multiple routers performing mutual redistribution you may need to have a higher metric on one router then the other to prevent a routing loop; this is where packets just keep going in circles between the two autonomous systems. It’s a safe bet to specify a fairly high metric in a production network to prevent such routes from becoming looped as lower metric routes are preferred.

To configure route redistribution you’ll use the redistribute command in router configuration mode.

Please review the following command(s) listed below;

| Command | Description |
| redistribute <i>protocol</i> metric <i>{metric info}</i> | This command is executed in router configuration mode of RIP, EIGRP or OSPF to configure the routing process to redistribute routes from a different source into the configured routing process such as static into RIP or RIP into OSPF. It’s best practice to specify a metric; when specifying a metric you specify a metric to be used by the routes when they appear in the routing process. For example, RIP uses hop counts, OSPF uses cost and EIGRP uses K Values (bandwidth, load, delay, reliability, mtu) |

The following logical topology shown below is used in this lab;

Lab Prerequisites

  • If you are using GNS3 than load the Free CCNA Workbook GNS3 topology than start devices; R1, R2, R3, R4, and R5
  • Establish a console session with devices R1, R2, R3, R4, and R5 than load the initial configurations provided below by copying the config from the textbox and pasting it into the respected routers console.

!###################################################
!# Free CCNA Workbook Lab 10-4 R1 Initial Config #
!###################################################
!
enable
configure terminal
!
hostname R1
no ip domain-lookup
!
interface Serial0/0
description ### PHYSICAL FRAME RELAY INTERFACE ###
no ip address
encapsulation frame-relay
serial restart-delay 0
no frame-relay inverse-arp
no shut
exit
!
interface Serial0/0.122 point-to-point
description ### FRAME RELAY LINK TO R2 ###
ip address 10.104.12.1 255.255.255.0
frame-relay interface-dlci 122
exit
!
router eigrp 10
no auto-summary
network 10.104.12.1 0.0.0.0
exit
!
line con 0
logging sync
no exec-timeout
!
end

!###################################################
!# Free CCNA Workbook Lab 10-4 R2 Initial Config #
!###################################################
!
enable
configure terminal
!
hostname R2
no ip domain-lookup
!
interface Serial0/0
description ### PHYSICAL FRAME RELAY INTERFACE ###
encapsulation frame-relay
no frame-relay inverse-arp
no shut
!
interface Serial0/0.221 point-to-point
description ### FRAME RELAY LINK TO R1 ###
ip address 10.104.12.2 255.255.255.0
frame-relay interface-dlci 221
exit
!
interface Serial0/0.223 point-to-point
description ### FRAME RELAY LINK TO R3 ###
ip address 10.104.23.2 255.255.255.0
frame-relay interface-dlci 223
exit
!
router eigrp 10
no auto-summary
network 10.104.12.2 0.0.0.0
network 10.104.23.2 0.0.0.0
exit
!
line con 0
logging sync
no exec-timeout
!
end

!###################################################
!# Free CCNA Workbook Lab 10-4 R3 Initial Config #
!###################################################
!
enable
configure terminal
!
hostname R3
no ip domain-lookup
!
interface Serial0/0
description ### PHYSICAL FRAME RELAY INTERFACE ###
encapsulation frame-relay
no frame-relay inverse-arp
no shut
exit
!
interface Serial0/0.322 point-to-point
description ### FRAME RELAY LINK TO R2 ###
ip address 10.104.23.3 255.255.255.0
frame-relay interface-dlci 322
exit
!
interface Serial0/0.324 point-to-point
description ### FRAME RELAY LINK TO R4 ###
ip address 172.29.34.3 255.255.255.0
frame-relay interface-dlci 324
no shut
!
router eigrp 10
no auto-summary
network 10.104.23.3
exit
!
router rip
no auto-summary
version 2
network 172.29.0.0
!
line con 0
logging sync
no exec-timeout
!
end

!###################################################
!# Free CCNA Workbook Lab 10-4 R4 Initial Config #
!###################################################
!
enable
configure terminal
!
hostname R4
no ip domain-lookup
!
interface Serial0/0
description ### PHYSICAL FRAME RELAY INTERFACE ###
encapsulation frame-relay
no frame-relay inverse-arp
no shut
!
interface Serial0/0.423 point-to-point
description ### FRAME RELAY LINK TO R3 ###
ip address 172.29.34.4 255.255.255.0
frame-relay interface-dlci 423
exit
!
interface Serial0/0.425 point-to-point
description ### FRAME RELAY LINK TO R5 ###
ip address 172.29.45.4 255.255.255.0
frame-relay interface-dlci 425
exit
!
router rip
version 2
no auto-summary
network 172.29.0.0
exit
!
line con 0
logging sync
no exec-timeout
!
end

!###################################################
!# Free CCNA Workbook Lab 10-4 R5 Initial Config #
!###################################################
!
enable
configure terminal
!
hostname R5
no ip domain-lookup
!
interface Serial0/0
description ### PHYSICAL FRAME RELAY INTERFACE ###
encapsulation frame-relay
no frame-relay inverse-arp
no shut
!
interface Serial0/0.524 point-to-point
description ### FRAME RELAY LINK TO R5 ###
ip address 172.29.45.5 255.255.255.0
frame-relay interface-dlci 524
exit
!
router rip
version 2
no auto-summary
network 172.29.0.0
exit
!
line con 0
logging sync
no exec-timeout
!
end

Lab Objectives

  • Create four new loopback interfaces on R1 using the 10.1.0.0/22 address allocation and configure those interfaces to participate in EIGRP Autonomous System 10.
  • Create four new loopback interfaces on R5 using the 172.5.0.0/22 address allocation and configure those interfaces to participate in RIP.
  • Analyze R3’s routing table and verify that the newly created loopback interfaces are being learned by R3.
  • Configure R3 to redistribute EIGRP routes into RIP using a hop count of 3 then redistribute RIP routes into EIGRP using a T1 bandwidth and 20,000 microsecond delay.
  • Verify on R1 and R5 that routes from the opposite autonomous system exist in their routing table.

Lab Instruction

Objective 1. – Create four new loopback interfaces on R1 using the 10.1.0.0/22 address allocation and configure those interfaces to participate in EIGRP Autonomous System 10.

R1#configure terminal
Enter configuration commands, one per line.  End with CNTL/Z.
R1(config)#interface loopback0
R1(config-if)#ip address 10.1.0.1 255.255.255.0
R1(config-if)#
R1(config-if)#interface loopback1
R1(config-if)#ip address 10.1.1.1 255.255.255.0
R1(config-if)#
R1(config-if)#interface loopback2
R1(config-if)#ip address 10.1.2.1 255.255.255.0
R1(config-if)#
R1(config-if)#interface loopback3
R1(config-if)#ip address 10.1.3.1 255.255.255.0
R1(config-if)#exit
R1(config)#
R1(config)#router eigrp 10
R1(config-router)#network 10.1.0.0 0.0.3.255
R1#
%SYS-5-CONFIG_I: Configured from console by console
R1#

<br>

Objective 2. – Create four new loopback interfaces on R5 using the 172.5.0.0/22 address allocation and configure those interfaces to participate in RIP.

R5#configure terminal
Enter configuration commands, one per line.  End with CNTL/Z.
R5(config)#interface loopback0
R5(config-if)#ip address 172.5.0.1 255.255.255.0
R5(config-if)#
R5(config-if)#interface loopback1
R5(config-if)#ip address 172.5.1.1 255.255.255.0
R5(config-if)#
R5(config-if)#interface loopback2
R5(config-if)#ip address 172.5.2.1 255.255.255.0
R5(config-if)#
R5(config-if)#interface loopback3
R5(config-if)#ip address 172.5.3.1 255.255.255.0
R5(config-if)#exit
R5(config)#router rip
R5(config-router)#network 172.5.0.0
R5(config-router)#end
R5#
%SYS-5-CONFIG_I: Configured from console by console
R5#

Objective 3. – Analyze R3’s routing table and verify that the newly created loopback interfaces are being learned by R3.

R3#show ip route
Codes: C - connected, S - static, R - RIP, M - mobile, B - BGP
       D - EIGRP, EX - EIGRP external, O - OSPF, IA - OSPF inter area
       N1 - OSPF NSSA external type 1, N2 - OSPF NSSA external type 2
       E1 - OSPF external type 1, E2 - OSPF external type 2
       * - candidate default, U - per-user static route
       o - ODR, P - periodic downloaded static route

Gateway of last resort is not set

     172.5.0.0/24 is subnetted, 4 subnets
R       172.5.1.0 [120/2] via 172.29.34.4, 00:00:25, Serial0/0.324
R       172.5.0.0 [120/2] via 172.29.34.4, 00:00:25, Serial0/0.324
R       172.5.3.0 [120/2] via 172.29.34.4, 00:00:25, Serial0/0.324
R       172.5.2.0 [120/2] via 172.29.34.4, 00:00:25, Serial0/0.324
     172.29.0.0/24 is subnetted, 2 subnets
C       172.29.34.0 is directly connected, Serial0/0.324
R       172.29.45.0 [120/1] via 172.29.34.4, 00:00:25, Serial0/0.324
     10.0.0.0/24 is subnetted, 6 subnets
D       10.1.3.0 [90/2809856] via 10.104.23.2, 00:05:50, Serial0/0.322
D       10.1.2.0 [90/2809856] via 10.104.23.2, 00:05:50, Serial0/0.322
D       10.1.1.0 [90/2809856] via 10.104.23.2, 00:05:50, Serial0/0.322
D       10.1.0.0 [90/2809856] via 10.104.23.2, 00:05:50, Serial0/0.322
D       10.104.12.0 [90/2681856] via 10.104.23.2, 00:09:59, Serial0/0.322
C       10.104.23.0 is directly connected, Serial0/0.322
R3#

Objective 4. – Configure R3 to redistribute EIGRP routes into RIP using a hop count of 3 then redistribute RIP routes into EIGRP using a T1 bandwidth and 20,000 microsecond delay.

R3#configure terminal
Enter configuration commands, one per line.  End with CNTL/Z.
R3(config)#router rip
R3(config-router)#redistribute eigrp 10 metric 3
R3(config-router)#exit
R3(config)#router eigrp 10
R3(config-router)#redistribute rip metric ?
    Bandwidth metric in Kbits per second

R3(config-router)#redistribute rip metric 1544 ?
    EIGRP delay metric, in 10 microsecond units

R3(config-router)#redistribute rip metric 1544 2000 ?
    EIGRP reliability metric where 255 is 100% reliable

R3(config-router)#redistribute rip metric 1544 2000 255 ?
    EIGRP Effective bandwidth metric (Loading) where 255
is 100% loaded

R3(config-router)#redistribute rip metric 1544 2000 255 1 ?
    EIGRP MTU of the path

R3(config-router)#redistribute rip metric 1544 2000 255 1 1500
R3(config-router)#end
R3#
%SYS-5-CONFIG_I: Configured from console by console
R3#

Objective 5. – Verify on R1 and R5 that routes from the opposite autonomous system exist in their routing table.

R1#show ip route
Codes: C - connected, S - static, R - RIP, M - mobile, B - BGP
       D - EIGRP, EX - EIGRP external, O - OSPF, IA - OSPF inter area
       N1 - OSPF NSSA external type 1, N2 - OSPF NSSA external type 2
       E1 - OSPF external type 1, E2 - OSPF external type 2
       * - candidate default, U - per-user static route
       o - ODR, P - periodic downloaded static route

Gateway of last resort is not set

     172.5.0.0/24 is subnetted, 4 subnets
D EX    172.5.1.0 [170/3193856] via 10.104.12.2, 00:00:09, Serial0/0.122
D EX    172.5.0.0 [170/3193856] via 10.104.12.2, 00:00:09, Serial0/0.122
D EX    172.5.3.0 [170/3193856] via 10.104.12.2, 00:00:09, Serial0/0.122
D EX    172.5.2.0 [170/3193856] via 10.104.12.2, 00:00:09, Serial0/0.122
     172.29.0.0/24 is subnetted, 2 subnets
D EX    172.29.34.0 [170/3193856] via 10.104.12.2, 00:00:09, Serial0/0.122
D EX    172.29.45.0 [170/3193856] via 10.104.12.2, 00:00:09, Serial0/0.122
     10.0.0.0/24 is subnetted, 6 subnets
C       10.1.3.0 is directly connected, Loopback3
C       10.1.2.0 is directly connected, Loopback2
C       10.1.1.0 is directly connected, Loopback1
C       10.1.0.0 is directly connected, Loopback0
C       10.104.12.0 is directly connected, Serial0/0.122
D       10.104.23.0 [90/2681856] via 10.104.12.2, 00:11:13, Serial0/0.122
R1#

You can see from R1’s routing table shown above that the RIP routes redistributed into EIGRP at R3 are being propagated throughout the EIGRP Autonomous System as EIGRP External routes.

R5#show ip route
Codes: C - connected, S - static, R - RIP, M - mobile, B - BGP
       D - EIGRP, EX - EIGRP external, O - OSPF, IA - OSPF inter area
       N1 - OSPF NSSA external type 1, N2 - OSPF NSSA external type 2
       E1 - OSPF external type 1, E2 - OSPF external type 2
       * - candidate default, U - per-user static route
       o - ODR, P - periodic downloaded static route

Gateway of last resort is not set

     172.5.0.0/24 is subnetted, 4 subnets
C       172.5.1.0 is directly connected, Loopback1
C       172.5.0.0 is directly connected, Loopback0
C       172.5.3.0 is directly connected, Loopback3
C       172.5.2.0 is directly connected, Loopback2
     172.29.0.0/24 is subnetted, 2 subnets
R       172.29.34.0 [120/1] via 172.29.45.4, 00:00:20, Serial0/0.524
C       172.29.45.0 is directly connected, Serial0/0.524
     10.0.0.0/24 is subnetted, 6 subnets
R       10.1.3.0 [120/4] via 172.29.45.4, 00:00:21, Serial0/0.524
R       10.1.2.0 [120/4] via 172.29.45.4, 00:00:21, Serial0/0.524
R       10.1.1.0 [120/4] via 172.29.45.4, 00:00:21, Serial0/0.524
R       10.1.0.0 [120/4] via 172.29.45.4, 00:00:21, Serial0/0.524
R       10.104.12.0 [120/4] via 172.29.45.4, 00:00:22, Serial0/0.524
R       10.104.23.0 [120/4] via 172.29.45.4, 00:00:22, Serial0/0.524
R5#

You can see from R5’s routing table shown above that the EIGRP routes redistributed into RIP at R3 are now RIP routes on R5 with a metric of 4 (1 hop to R4 + 3 from R3’s added metric).

Rate This Article

Thanks for reading: Configuring Mutual EIGRP & RIP Redistribution Tutorial, Sorry, my English is bad:)

Getting Info...

About the Author

I'm Aevon...Just a gal with an insane passion for all things cybersecurity. 17 years in the industry and still love what I'm doing.
#• Networking Fundamentals Tutorial • #• Route Redistribution •

Post a Comment

Cookie Consent
We serve cookies on this site to analyze traffic, remember your preferences, and optimize your experience.
More Details
Oops!
It seems there is something wrong with your internet connection. Please connect to the internet and start browsing again.
AdBlock Detected!
We have detected that you are using adblocking plugin in your browser.
The revenue we earn by the advertisements is used to manage this website, we request you to whitelist our website in your adblocking plugin.
Site is Blocked
Sorry! This site is not available in your country.