Hello again this is your host Aviva Korea. And we are starting with the with the first chapter of this course. And we will go through some of the terminologies. The first one is how do you define our distribution. Now rotary distribution is when you take a route from one routing protocol and inject it into another routing protocol. This will basically redistribute routes from from one domain that is using let's say any routing protocol to another domain that's using the same or different routing protocol.

So that's the idea of Route redistribution. As you know, by default routers on the advertise and share routes within the within the within the same domain with the other routers that are running the same protocol. But with route redistribution, you can basically advertise the routes between different different organizations. One thing I want to basically address is the problems that I have that can occur when you do route redistribution. The first problem that we need to make sure is mis configuration of Route redistribution. And and from my personal experience is that you should basically follow the guidelines for doing route redistributions.

If you miss configure route redistribution, this could lead to basically severe instability. To sub optimal routing information and it could also lead to route isolation and persistent route loops. The bigger the the number of routers that you will be that you will be putting or you'll be applying route redistribution, the more problematic it would be. But definitely when we do our topology and go through the configuration, I hope you will gain that much experience and confidence. The other point is that we need to remember is if a router receives a routing instance from one interface, it should not receive the same routing instance from another end. interface that that should be clear, I mean, it should not be done that way.

Otherwise, again, your routing table will basically remove one route and add another route with a different metric. And that will basically cause some sort of a loop every time. So let's go back to the slide here num point two or question number two says what to remember before redistribution King routes. The main aspect of of Route redistribution is to know how to work with the metrics of each routing protocol. OSPF as you know uses cost Ei GRP will use k values which the k values are basically bandwidth delay load and reliability. Rip as you know, it uses hop count.

So remember this and we will go through this in our topology as well. And in in our examples today third question is what is seed metric? So a seed metric is when we redistribute from one instance to another, we have to use a seed metric. Every routing protocol uses a different metric as you see here in my table. And we have to convert these metrics from one routing protocol to another. And this does not happen by default and it is a manual process.

So, for example, rip uses metric infinity and the way you can address this is basically let's say you advertise a route into OSPF that is coming from a rep and, and you apply the matrix 16. Now the problem here is rip only or will inject a route into its routing table. If it's below 16 Hopkins right. So 16 will be configured it will be basically will be infinity for rip and rip protocol will never put a matrix 16 route into its routing table. And it will basically ignore that metric ignore that route and you will not see it in the routing routing table after you apply the redistribution. So, these points are very important to remember.

And hopefully we will cover this these all these points in our topology, and I will try to show you step by step configuration so that we can achieve the purpose of this course. And I learn thank you very much and I hope to see you in my next chapter.