Hello this is your host Habib Korea. And in this scenario, we will be talking about how to redistribute rip version two to EI GRP and Ei GRP to rip version two. So, little bit of notes here that we want to highlight is EI GRP will always need five metrics when redistributing other protocols into it. One is bandwidth The other one is delay, third is reliability, load and MTU. bandwidth is usually in in kilobits per second delay is in 10s of microseconds. Reliability is usually 255 255 and that means it's hundred percent reliability when it's at that load is usually from one to 255 and MTU is always 1500 by now, another point I would like to highlight is you can have multiple eigrp processes run on the same router.

However, having two processes on the same router will affect the memory and the CPU utilization. You can also redistribute which routes between two different AI GRP processes. And for that, basically you can always use the default metric During the redistribution on another, so that's about the eigrp those are the important points to remember. Rip again as we did in scenario two, you can it uses hop count of up to 15. After that, it will always considered an infinite metric and that will not basically basically help the route. If if it has a hop count of 16 or even more it will consider itself as infinity and it will not advertise that route in the rip domain.

So, our recommendation here is or my recommendation is always choose the lowest metric for Rep. Four, and it has to be and it should always start with one. So that's pretty much everything in terms of notes and theoretical aspect of your grps grep. So let's talk about scenario three. In scenario three, r two r one and r three are in Ei GRP domain and r two will be the basically area border router for us. And, and it will extend the domain from here, all the way from r to r four and R five. There is a loopback interface that I introduced in our five that will need to be redistricting muted across the whole network.

So let's start and and get this going okay I'm here in our to and we will start configuring the interfaces. And we will basically first configure the domain and and we will move into er GRP after that so so interface FA zero slash zero IP address 24 dot and 10 dot one Let's see what clock rate do we get here? Let's see if we can apply so it's rounding it to 13440000 which is fine I think it's the basically the version of this router and also the past clock rate that it shows is quite alright let's introduce rotor rip. Let's First check the interfaces show IP interface brief. Okay, so we have two interfaces here called t router rip, say version two. And the network that we will introduce here would be the two, the 24 dot zero dot zero.

That's our network. And we'll say no auto summary. So that's, that's our two. Let's move to our four. Okay, I'm in the console here in our floor. So interface FA zero slash zero IP address.

24 Dot 10 dot 10 dot two oh shot and we have another interface. Okay, so let's give it a higher clock rate here. IP address of 45 dot 10 dot 10 dot 125522552550 no shocked Now let's introduce the rip router here. Rip version two, no auto summary. We have two networks that we need to advertise 24 dot zero dot zero dot zero and network 45 dot zero dot zero dot zero. So let's move on to to our five and configure the interfaces.

Okay, I'm in the console here for our files and we will configure interfaces Ces interface as one slash one IP address 45. To no Sure. And we have interface loopback zero. And the IP address that we want to provide here is going to be make sure we have the IP interface brief route to rip version two no no more to summary Now network our networks are 45 00 and the network 3010 00. Show IP route. And yes, we can see, if you, if you look at the routing table here in our five, I can see the network 24 dot 10 dot 10 dot zero, which is this network.

And it has a metric of 120 with a hop count of one. So that's exactly what we see in our topology. The 45 network is a locally connected network, as you can see to our five and we do see the loopback as well. So that's the topic apology for our five and let's continue now also configure Ei GRP er GRP domain and get going so I think okay, so I'm here in the console. So let's see show IP interface before we already have that. So we already have a signed serial interface one slash to the IP address that so that's great.

Let's Let's introduce here. GRP, router GRP, hundred and network 12 dot 10 dot 10 dot two too That's all I need to do here in order to so remember we are using process hundred and it's actually 100 free a GRP OSPF uses process. Let's go to to r1. Okay, I'm here in our one assigning the first IP subnet no shut Here's another interface here. IP address 13 dot 10 dot 10 dot 1255255255 dot zero no shot I'll introduce the networks to EI GRP here. So the first one is 12 dot 10 dot 10 dot one dot 10 dot 10 dot one.

We'll come back to our one It seems like there's one of the interfaces that's still down show CDP neighbor. Yes, because one of the interfaces still showing as down. So we'll come back to it. Now we'll move to our three Okay, we are in our tree. let's configure the costing Ufi serial one slash one we only have one interface here in our three that we need to advertise IP address 13 dot 10 dot 10 dot 225-525-5255 dot zero no Sure. And network router eh GRP hundred and the network is 13 dot 10 dot 10 dot two.

Okay, so I can see our three has formed adjacency so if I do show I Piro IV Yeah GRP see, so I do see in our one I have adjacency created. So show IP route. Okay, show it. Line protocol is down So, what we find here is that the the serial interface one slash one is up, but the protocol is down that means there is there is a some sort of physical issue when the protocol is down. So this indicates that our one is okay, our three is okay, but we have a problem in our two. So let's bring up our two.

So I'm in our tools console here and if I do show IP interface brief, I do see that this interface is administratively down that means that we forgot to say no shut. So as I stated routers, think in routers Danger faces are always shut down. And this is one common mistake here. interface 01 slash 201 slash to no shot. That's to show IP interface brief. And yes, it's up now.

And I can see it created the adjacency. So that's good. So if I do show IP route I can see the rip routing protocols here. D is for Ei GRP. R is for rip. There you go.

So we do see that Our two is fully converged. Same thing it should check on one. Perfect. Let's go back to our three show IP route. And yes, we can see that the eigrp is fully converged, but one thing we noticed that the two domains are isolated are operating isolated, they are not aware of each other routes. So this is our purpose in this task is to make sure that they can the routes are fully covered verged between the two domains and and we will do that now.

So I'm back here in our two archers our a border router as you can see because it gets routes from both the both the domains so let's go ahead and do the route redistribution. So the first thing is let's do let's inject er GRP routes into rip, right. So if I do router rip, I have to go into router rip and to redistribute. Er, II hundred. And as I said, I mean when you're injecting any routes into rip, it's best to use to seed metric of one Right. So that's good.

So, we did that. Now, as you know, he he RP has uses the k values. So, in order to determine the k values we have to basically check the outbound interface properties. So, if I do show interface s one slash two, right, I can get from here to things right what I will get here is all the k values that we will be using the MTU bandwidth delay, reliability load. This is very important. Okay, so let's do that.

So, if I do So I'm going to now introduce inject rip routes into er GRP. So router here eigrp. We use this hundred, redistribute, rip metric. And let's go for the metric here. So we have we have the metric of bandwidth which is 1544 then we have to delay. me just extend this so I can see properly so the delay is 20,000 Yeah.

And we have liability to 551 that's the load and the MTU is 15. And that's all that's all we need to remember when we are distributing any, any routing protocol routes to EA GRP. So, now if I do show IP route here, I still have I, I have both the both the both the domains in here. So I have D, I have r is the same. Nothing changed here. Right?

But if I go into are three and I do show IP route. What I see here is is the new routes that have been advertised into our three which is the there you go, that's the 30, the 30, the 30 network that we have, which is in our five Let me try to pink 13 1330 dot one and yes, I can ping it. Now same situation if I basically we have successfully introduced eh rip route into Ei GRP. Now, let's go to our five bringing our five and let's do show IP route. And yes we can see the the new routes here from OSPF and those are getting introduced into it. So, we have successfully completed this topology we have achieved full convergence between the two domains and and we completed the requirements of how to redistribute rip into er GRP and er GRP into rip.

The only thing is with the eigrp is you have to basically see the out bounding interface properties and get the k values and that's how you will be able to do the route redistribution All right and with this we conclude this course I hope you have enjoyed the course. And we we actually covered three scenarios. Scenario one was redistributing static routes into the rip domain. Scenario two a was to redistribute reversion to and OSPF and scenario three is how to redistribute rip version two and here GRP I hope this was very informative to you all that have watched this course. I hope that I can bring more useful and important courses and networking. And and I hope to see you soon.

Thank you very much and have a good day.