In The First Part Of This Free CCNP BSCI Tutorial, We Looked At How Leaving One Simple Word Out Of Our Route Redistribution Configuration - "subnets" - Resulted In An Incomplete Routing Table When Redistributing Routes From RIP To OSPF. (If You Missed That Part Of The Tutorial, Visit My Website's "Free Tutorials" Section.) Today, We'll Look At Redistributing OSPF Routes Into RIP And Identify Another Common Redistribution Error.We Are Using A Three-router Network. R5 Is Running RIP, R1 Is Serving As A Hub Between R5 And R3 And Is Running RIP And OSPF, And R3 Is Running OSPF. To Begin This Lab, We'll Add Three Loopbacks To R3 And Advertise Them To R1 Via OSPF.R3(config)int Loopback33R3(config-if)ip Address 33.3.3.3 255.255.255.255R3(config-if)int Loopback34R3(config-if)ip Address 34.3.3.3 255.255.255.255R3(config-if)int Loopback35R3(config-if)ip Address 35.3.3.3 255.255.255.255R3(config-if)router Ospf 1R3(config-router)network 33.3.3.3 0.0.0.0 Area 1R3(config-router)network 34.3.3.3 0.0.0.0 Area 1R3(config-router)network 35.3.3.3 0.0.0.0 Area 1R1 Sees All Three Of These Routes In Its Routing Table.R1show Ip Route Ospf 34.0.0.032 Is Subnetted, 1 SubnetsO IA 34.3.3.3 11065 Via 172.12.123.3, 00:00:55, Serial0 35.0.0.032 Is Subnetted, 1 SubnetsO IA 35.3.3.3 11065 Via 172.12.123.3, 00:00:45, Serial0 33.0.0.032 Is Subnetted, 1 SubnetsO IA 33.3.3.3 11065 Via 172.12.123.3, 00:00:55, Serial0We'll Now Redistribute These Routes Into RIP On R1. Remember The "subnets" Option We Talked About In The First Part Of This Tutorial? There Is No Such Option When Redistributing OSPF Routes Into RIP, As IOS Help Shows Us.R1(config)router RipR1(config-router)redistribute Ospf 1 ? Match Redistribution Of OSPF Routes Metric Metric For Redistributed Routes Route-map Route Map Reference Vrf VPN RoutingForwarding Instance CrR1(config-router)redistribute Ospf 1The Routes Have Been Redistributed Into RIP With The Redistribute Ospf 1 Command. (The "1" Is The OSPF Process Number.) Let's Look At R5 And See The Results.R5show Ip Route RipR5The Routes Aren't There, But We Didn't Get A Warning From The Router That We Needed To Do Anything Else. What Is The Problem?The Problem Is That RIP Requires A Seed Metric To Be Specified When Redistributing Routes Into That Protocol. A Seed Metric Is A "starter Metric" That Gives The RIP Process A Metric It Can Work With. The OSPF Metric Of Cost Is Incomprehensible To RIP, Since RIP's Sole Metric Is Hop Count. We've Got To Give RIP A Metric It Understands When Redistributing Routes Into That Protocol, So Let's Go Back To R1 And Do So.R1(config)router RipR1(config-router)no Redistribute Ospf 1R1(config-router)redistribute Ospf 1 Metric 2R5 Now Sees The Routes. Note That The Metric Contained In The Brackets Is The Seed Metric.R5show Ip Route Rip 34.0.0.032 Is Subnetted, 1 SubnetsR 34.3.3.3 1202 Via 100.1.1.1, 00:00:24, Ethernet0 35.0.0.032 Is Subnetted, 1 SubnetsR 35.3.3.3 1202 Via 100.1.1.1, 00:00:24, Ethernet0 33.0.0.032 Is Subnetted, 1 SubnetsR 33.3.3.3 1202 Via 100.1.1.1, 00:00:24, Ethernet0If You Read The Previous Tutorial, You May Have Noticed That We Did Not Specify A Seed Metric For OSPF. OSPF Does Not Require A Seed Metric To Be Set During Redistribution. You Also Noticed That The Router Did Tell Us That There Might Be A Problem When We Left The "subnets" Option Out Of RIPOSPF Redistribution, But The Router Didn't Tell Us Anything About A Seed Metric When We Performed OSPFRIP Redistribution. This Is A Detail You Must Know By Heart In Order To Make Your Route Redistribution Successful!
