Hi, Hello, this is your host Aviva Korea. And we are we are going to talk about the first scenario here, which is redistributing static route to a rip network. The reason why I chose this scenario is because a lot of the companies that are smaller in size, usually run rip network. And for that reason, I try to come up with a scenario that exactly resembles that kind of a network. And as you know, most of those small companies will, will have some sort of cloud based application somewhere with one provider and and somehow they need to reach that network within their domain. So let's start in this In this scenario, I have router one router to router three and then there is an external router.

I'm assuming that external router is somewhere outside of the rip network, but we will still try to reach this network which is L zero which is the loopback interface 10 dot 10 dot 10 dot 10 from r1. So basically the external network does not really interfere with the rip network, but it has some sort of an enum element that they will they will introduce in the external network so this IP address can reach all these routers from here. So let's start I hope you will enjoy this topology as we build it up and We continue to basically examine redistributing static routes to rip network on as a matter of fact, any any routing protocol or any network that's running any routing protocol, it's going to be pretty much the same concept. But we will continue with different scenarios. And, and hopefully we can achieve the purpose of this course.

Okay, so I'm going to start by by starting the routers here and and the routers are starting. Let me bring up the consoles and we'll move from there. Okay, so I have router one. So let's continue Good that's router. So there's one interface here. interface has a zero slash zero we'll give it an IP address.

Okay, the top one on this interface the subnet mask is a slash 30. That's 255255255252. And that is supposed to only give us two hosts. So one host is this interface here in r1. And the second host will be this one. Now make sure you apply no shut in the real world.

When you are operating In the router, most of the interfaces are always shut but because this is a simulator, the interfaces are always on but by habit I always put no shut. So show IP interface brief. I have that interface. Now let's apply the to rip protocol router rip. We will assume it's version two. That's what we use version two.

Or it's at that on top version, and we'll say no auto summary. Good Practice here. And we will apply the network 192 dot 3212 dot zero Yep. Okay, so we can see the routing table right now. There's only the connected interface right here. Okay, so I am I added the, the router rip protocol.

And I did show IP route here just to check what's in the rip which is the routing table and I only see the connected interfaces. Okay, which is great. Now let's, let's move into our two and we will do exactly Through the same steps. Okay, we are at the console. For our to let's start configuring the interfaces. Make sure you give no shot IP address 192 dot 32 dot 225 525-525-5252 Let's go with the interface and swans hash to IP address 192 dot 28 dot 23 dot one shot router rip.

It's version two, no two summary. And then we'll add the two networks here. 192 dot 32 dot two alpha zero network 192 dot 28 dot 23 dot zero. r two is configured. Now let's move move to r three. Let me bring up the console.

We are here at our tree and let's configure the interfaces I believe two or three interface IP addresses 192 dot 28 dot 23 dot 2255 255-255-2252 no shut and we also have another interface fa, zero slash zero IP address 192 dot 16 dot 30 dot one you know shut let's add the router protocol There's one more thing we need to do in our three, there's a little bit of work that our three will need to go ahead for. First of all, we have to basically give a static route from our tree all the way. First we need to make sure our tree which is our, our border router here, can reach 10 dot 10 dot 10 dot 10 slash 32. Or it should be able to at least ping this interface here. So we will come back to our tree in a bit and configure that.

That and let's move to first of all this external router and configured that interface as well. Okay Let me bring it up. Okay, so the external router console is right here. So first thing I want to make sure from are three I can ping that interface, which is actually a point to point interface. Oh, sorry about that. And yes, I can ping that interface, create another interface.

I want to create it loopback zero interface on this external router, I'm assuming that's a different network. And that's what we are looking to reach eventually, from all our other routers. Okay, let's first configure our three. We're back in our tree and the only thing we need to add is the static route. So IP route Okay. Okay.

So are three can basically reach 10 dot 10 dot 10 dot 10 network or interface. Okay. But there's one more thing I need to do in our three for that network to appear in the rip protocol in the rip routing table, so if I do show IP route okay. And I go to so as you can see, I mean in here I can see the, the subnet that's, that's appearing here, right? So in this rip table or RM Be cable, which is the routing table. I can see it's already here.

Okay. But if I go to our one if I bring up Yeah, let's let's bring up our one. As you can see in our one routing table, I don't see 10 dot 10 dot 10 dot 10 network. The reason is obviously because I can basically go to our tree here and I have to redistribute that network. To the IP routing table. So what I'll do in our tree is I'll do router rip, I'll go into the rip configuration, and I will do redistribute static.

So that's the command that we need to learn here is redistribute static, it redistribute all static routes into the routing domain. So now if I do show IP route, there you go. I can see that network here. And same would be the case if I go to r two. And I do show IP route. I do see the network here.

Now I am not able to ping from r1 Not able to ping ping 10 dot 10 dot 10 dot 10. I'm not able to ping. Even from r two, I'm not able to ping 10 dot 10 dot 10 dot 10. I'm not able to ping. There's a simple answer to that. And that is the external router.

Even though it receives the the echo messages from these routers, but it cannot send the reply back because it doesn't know how it's supposed to send it back or from which interface it can send back those. Those echo replies So one thing I need to do here in the external router is define those static routes here that want to reach this network which is loopback interface zero so what I'll do is call it, I'll do IP route. And we'll say for example, if I want to reach if I want to send a reply back from from here to our two it's going to be and if I want to send a reply all the way to r1 my IP route will be Okay, let's come back to r1. Now let's do the same ping I can ping from our one let's go to our to I campaign from our to let's go to our three.

Well, we already knew that it campaign from our three. Okay, so that's perfect. So let's examine the routing table here. The routing table here shows that this is a. This is the network you can see the metric here says one, two slash zero. If I go to our turn to show IP route, I can see this network is showing as 120 slash one, which is the hop count slash one.

The metric value for rep is 120. And if I go to r1 and I do show IP route, I can see the metric value of 122 hop count of two. So if you look at the topology we understand to get to this network I have r1 has to go to two hops one to r two has to go to one hop to get to this network over here. And the metric is basically different from our one It'll look different than r two, and r three r three is considering itself that it's locally connected to this. And the metric is always one because it's a static route from here. So the administrative distance for static route is always one.

So that's why our ones routing table is a little bit. Our threes routing table is a little bit different. It shows one as the metric. But if I go to look at our two, metric is showing 120 and one hop count. And similarly, if I go to our one, it's showing two hop counts, the metric is 120, because it's learning it to Rep. So that means that static route is basically Getting advertised into the rip routing protocol.

So, with this we conclude this scenario I hope you have gained enough information in how to redistribute static routes. In this scenario, basically we assume that this router is managed external router is managed by an outside company. And the outside company's responsibility is to make sure that the loopback interface is reachable to the internal domain. And that's what we saw basically, even though we have we have added static routes that will, that will center apply backs to these networks. But that's not something that you as engineer within within an organization need to worry about. Instead of static routes they could be, they could be working using other dynamic routing protocol within their domain.

And that's what we will learn in our next scenarios. Thank you very much.