Okay, so we will start with the topology configuration right now and I decided to put everything from the start and bring up the interfaces and put the interfaces so we'll start with router three first show IP interface brief just to see if there's any configuration on the interfaces there's none. So interface loopback address 10 dot 10 dot 10 dot 10 255 cuts here dot zero dot zero interface serial one slash one and we'll provide the IP address of this interface to be dot one of this network which is 192 168 dot 10 dot one subnet mask will make this to the side of the router to be a DC router. So we will have to put a clock rate for serial interfaces and no shutdown interface 01 slash two IP address 192 168 dot 11 dot 1255255255 to zero clock rate 64,000 no shut save the configuration show IP interface brief just to confirm or deny faces are saved here.
Will bring up our to now. Okay we're configuring the interfaces in our two. Okay we are giving in to on this side of the router perfect Send no shot. Make sure we save the configuration. And we can see all the interfaces are up here. Now next step is to actually add the enable a BGP on the router, so router BGP, and the autonomous system of this router is 65511.
That's the autonomous system it's part of. And now we will add the neighboring information. And the purpose of this lab is to make sure the neighboring is happening. The neighbor relationship is happening using the loopback address. All routers in here we'll add remote as 65512 and then neighbor Come on 20 2020 update source loopback zero. Now the reason we are putting update source loopback zero as I said it's because we are not using the actual physical interfaces to create this neighbor ship.
So that's the reason this command is really important when you do ebgp relationships neighbor ebgp multi hop too, now to the reason why putting too is that we're increasing the TTL value of the BGP. It's usually one by default but we are putting too just to increase the TTL value. Our threes configuration is done now we will go to our two and we will also enable BGP and R 265512. That's perfect. Neighbor will choose 10 dot 10 dot 10 dot 10 remote as that's a remote as for our three which is 65511. neighbor 10 dot 10 dot 10 dot 10 update source loopback zero neighbor ebgp multi hop to. So it's exactly the same commands on the other side on this side of the router as well.
So let's save our configuration. The one thing we will do now is the static routing between the two devices. And as you can see we have redundant So we will have to add two static routes here, one with the administrative distance, which is the default administrative distance of one, we don't have to mention that. So IP route 20 dot zero dot zero dot zero to five five dot zero dot zero dot 01 92 168 dot 10 dot two, and the other route is there. We'll come back to that I think we missed the second route should be 192 168 dot 11 dot two. We'll fix that in a bit.
Let's go to our three and apply the same thing. But in the opposite direction, of course 10 dot zero dot zero dot 0255 dot zero dot zero dot 01 92 168 dot 10 dot one dot 11 dot one administrative distance of 10 exit. Let's save it. Now let's fix the arteries. Second IP route statement here. It should be 192 168 dot 11 talk to Shai p BGP summary just to verify the neighbor ship is done and it is it's working.
Definitely we can ping both sides from either ends should be show IP BGP summary. That's good. Now if we shut down one of the interfaces, which is s one slash one, we will still continue to have the peering relationship between the two routers. And this is what I'm trying to verify here we shut down one interface and we will still be able to ping. So be able to have the BGP relationship between the two routers. Now because they are point to point the relationship still exists.
This is The purpose of our lab I hope you have enjoyed this lab and we will continue with our next lab. So please stay tuned. Thank you again. This is great