Hi Hello again, this is your host Habib Korea. And in Scenario number two, we are looking at an example here where we will basically redistribute routes from OSPF to rip and rip to OSPF. The few things that we need to remember about rip is that the maximum valid metric is O is 15. Anything that is above 15 will be considered as an infinite metric. And if that happens, that route basically becomes isolated and it does not appear anymore in the routing table. So, when you actually redistribute into rip protocol or into rip routing table it's best to use the metric Have one.

So, the way I can explain it is let's say if you provided a metric of 10, you will only get a chance to get that route out to another five routers, which is another five more hops. And then for when it comes to the sixth router, it will basically ignore that route because the hop count will reach 16 and it will not be advertised anymore. So the lower the metric within rep is better. And this way you get more chance to maximize the number of hops in the rep domain. So that's the that's the most important aspect of this scenario. The other thing is basically, when you have a lot of redistribution points, that will basically lead to a lot of routing loops.

And we have to basically minimize that by choosing the minimum number of routers that will redistribute those routes. And hence, that's why this topology is important. And I'm showing a minimum number of routers that we will be using to redistribute those routes basically are two is our point here of is our border router, you could say and that one will basically act as our redistribution point. So let's start first talking about Scenario number two. In Scenario number two, we have our one that's connected to our multi layers which which is s w one and r two is connected to the same switch. I'm assuming this is going to be the, our, our OSPF domain, and then the, the the routers within the yellow area.

Those are our basically within the rip domain. Okay, so let's start by configuring the switch first. f one f1 slash one and f1 slash two are in the same VLAN. So let's start doing that configuration. So I'm already brought up the console for the switch and let's do interface. switchport mode Access switch port access VLAN 12.

So as you know in multi layer switches if there is no VLAN defined it will create that VLAN and the interfaces for the for for in most of the switches the most of the interfaces are always on. So, but out of habit I always usually do the no show interface FA one slash two I believe that's all we need to do in the inside the switch. Let's move on to r1 and start configuring the router. Okay, so I'm back here at r1 and I'm on the console here. Let's start configuring the interface. Now let's just go ahead and add the OSPF protocol and we will give it a router ID And the network that we introduced is 12 dot one dot one dot one, area zero.

Perfect. We are going now and log into our to and configure exactly the same, the same configuration as well as we'll make sure those interfaces are given IP addresses. Okay, I'm here in our to let's configure those interfaces. interface FA zero slash zero IP address. What we will do is we'll give this interface an IP address of 32 dot one dot one dot one and we will introduce clock right here okay Yeah, that's fine. The clock rate is best fitted to, to that rate.

No shut. Let me just check the IP interface brief the interfaces are here. And so we are advertising FA zero slash zero into the OSP TF routing domain so that's done and let's introduce rip router protocol. route to rip version two and network. Actually let's do not auto summary. We could have done it after we have entered that but out of habit and 32 dot zero dot zero dot zero that's our network.

Okay, so we are moving on now next to our three and we will configure our trees in interfaces. I'm here in our threes console. let's configure the interface now. interface s one slash three. And I believe we give it an IP. give it an IP address of 101 dot 225522552255 to zero, no shot.

And there's another interface here which is the loopback. Zero IP address of 230 to 30 thought 30 00 yeah We have to fix this part. It's actually, we're trying to give an interface and network IP address. Well, there we go. And let's now add the rip router. Now let's do first of all, show IP interface brief just to make sure that we have the interfaces and yes, we have the loopback interface, we have the serial interface that's connecting to our two.

Let's ping 32 dot one dot one dot one and yes, we can ping it. Let's go ahead and add our rip protocol here version two, network and we have to network which is two 32 dot zero dot zero dot zero. And then there will be another network here which is 30 dot zero dot zero dot zero. And no auto summary. Show IP route. Perfect.

Most of the networks here are anyway directly connected to r two. r three has l zero which is anyway locally connected. So let's examine the our choose. Route table. And yes, we can see that within our two I can see the rep network. And we can also see here there's an OSPF network here, but because those networks are directly connected, that's fine.

Now if you can see here like first thing I need to basically examine is now both the domains are basically not able to see each other's routes, right? But they can basically like our one can only see whatever is connected within to it. And it can reach our two but our three cannot really see anything other than the networks that it's it's seeing from its neighboring device or from what is directly connected to it right. So right now, we have built a topology and configured the interfaces we have assigned over pf area 02 r one and r two. And we have assigned the rip routing protocol to our twos. interface facing r three and as well as our threes interface facing r two and the loopback interface just to make sure I mean in our two we can do show IP route rip.

And those are the networks it's learning through the rip routing protocol. Now the second thing we need to do here is basically our task which is first thing we will advertise OSPF into the rip domain okay. So and we will introduce the seed metric and also we will introduce the metric We will be using. So follow the steps here. And let's start so so router rip so we have to go into the rip configuration and redistribute, redistribute OSPF one. That's our process for the OSPF.

And if you if you look here we have to add some sort of a metric for right. And as we said, the lower the metric for rip the better. This way we give more chances for this route to basically reach the maximum number of hops which is going to be 15. So we are going to put metric one metric of one Okay, so that's good. Now, also within because this is our ABR router right and it's basically it's it has its it knows about both domains somehow and it interconnects between the two. So now the other step is redistribute, rip into OSPF.

So I will go into router OSPF one and I will say redistribute. Rip subnets. That's it. Right. And I'm hoping that right now I'll go into r1. I should be able to see this network which is elzar loopback, interface 3230 to 30 dot zero network into in our ones routing tables.

As well as as well as I would be able to see within our trees routing table our wants information. So let's jump to r1. And let me do show IP route. And yes, I can see that network. Correct. And I'm seeing it as eat to eat to means it's an external network, which is fine.

It's perfectly fine. Right? It's perfectly fine. Here is the metric for OSPF as you know it's 110. And 20 is the default default seed metric for 20 for OSPF right that's what I was showing you in the first slide or for the introduction, that it's fine to use to cheat metric, and as long as as long as it's, it's its default, it's fine. As long as it's one router that's doing the redistribution, the default metrics can be applied and there will be no problems.

Now let's go to our tree. And let's look at the routing table show IP route. And yes, I can see. I can see the map. I can see the network here. That is advertised to r1 and I can see the metric of 120 and a hop count of one.

And this shows me it's a rip routing protocol. Okay, From r1 I should be able to ping our threes loopback interface so let's ping it pink. I think it's 30 dot 30 dot dot one I believe and yes I can ping. So this is perfect. This is this is the perfect example of how to redistribute OSPF into rip and rip into OSPF. Another point that I want to bring up about this example is I personally have have worked on a similar project where my company was a large company about few years back and they acquired A small company that was running a rip protocol and we had to do full convergence between the two networks.

And this is what exactly I did for for them. And it was a perfect scenario to present in this course and I hope you have learned from from this scenario, and we will continue to our next scenario and, and and talk more about how to do redistribution in that scenario as well. Thank you very much and I hope to see you in my next scenario.