We will be undergoing scheduled maintenance on May 20th, 2013 at 02:00 GMT.
Implementing Cisco IP Routing (642-902 ROUTE) Tutorials
BGP / Lab - BGP over Multilink Connections pt. 1
Visitors to VTC.com will be able to view all introductory videos for each training course.
Free Trial Members will gain access to first three chapters for each training course.
Full Access Members have full access to VTC.com�s entire library of video tutorials.
Learn More
Subtitles of the Movie (Implementing Cisco IP Routing (642-902 ROUTE) / BGP / Lab - BGP over Multilink Connections pt. 1)
So now we're going to configure BGP over a Multi-link connection. You'll notice between Access 2 and ISP 2 we have two T1s and in the real world this might be for Redundancy or added bandwidth or something along those lines. For our purposes, it's just so we can demonstrate how this is set up. So if we look here on Access 2, we show that we have two IP addresses going to this ISP 2 Router. If I do Show CDP Neighbor, you notice that we have ISP 2 Router showing across both Serial 1.1 and Serial 1.0. So the question is, what IP address do you put in the Neighbor Statement? I mean we could set up Neighbor Relationships 151.1.1.1 and 151.1.1.5 but that would mean we'd have twice as many routes in the BGP Routing Table. You'd increase the processing and memory requirements by double just because you have two neighbors as far as the BGP process is concerned. BGP doesn't realize that, that neighbor is really the same Router. So setting this up properly requires a little bit of work on both ends. You have to work with the ISP and they have to work with you obviously to get this set up in the best way possible. Now the first thing we're going to do is set up a Loopback address, another Loopback address on the ISP 2 Router. And we'll give this a bogus address like 1.1.1.1 so we'll do Config T. We'll do Interface Loopback 1. We'll do IP address 1.1.1.1 with a Host Network Mask 255.255.255.255. That way we don't waste the entire 1. network by having bound to this Loopback address. We'll also do the same thing on Access 2. Obviously we'll use a different IP address, but we'll go over here and Config T. Interface Loopback 1, we'll give it an IP address of 2.2.2.2 with a Host Network Mask. And so now if we Exit out, we Show IP Interface Brief, we see now that we have a Loopback address with that address assigned or a Loopback Interface with that address assigned and so now we just have to make sure that we can Ping both of these addresses from each of the Routers. So what we'll have to do is, we'll have to set up a Static Route that says to get to the 2.2.2.2 network address, you go down one of these two links and obviously you'll remember, if we have two Static Routes to the same network going over two different Serial Links that have the same Bandwidth, that the Router will Load Balance across both of these T1s. So go into Config T, we'll do IP Route 1.1.1.1. I think we have to put the Net Mask in here, yes, 255.255.255.255 and the next hop will be 150.1.1.1 and we'll just hit Up Arrow and put 1.1.5 as well. So now in the Access 2 Router if we do Show IP Route we have a Static Route to the 1.1.1.1 host via both of those and both of those are actually installed in the Routing Table because again, both of these T1s are equal cost. So we do the same thing on ISP 2. We'll do IP Route 2.2.2.2 255.255.255.255 and it's next hop will be 150.1.1.2 and 1.1.6. So now if we do Show IP Route on ISP 2 we have all of our connected networks as well as the Static Route to 2.2.2.2. So now if we Ping 2.2.2.2 from this guy, we get Pings back and the same thing from Access 2 if we Ping 1.1.1.1 we get Pings back. So now all that's left to do is set up the BGP Neighbors pointing at those Loopback addresses. However when we set up this neighbor, we have to tell both the Routers that your next neighbor is more than one hop away. Now by default, when you set up EBGP Peers, the EBGP Peers have to be no more than one hop away from one another. Obviously we saw that is not the case with IBGP as Access 1 and Access 2 are two hops away from one another yet they still were able to form an IBGP Neighbor Relationship because this Multihop doesn't apply in IBGP. It's one of the few differences between EBGP and IBGP. However if you've got BGP Peers in different AS's they cannot be more than one hop away. Now in this case, you might be looking at the network diagram and saying but they're not more than hop away, they're directly connected. Well technically the Loopback Interface is seen as another hop so you send out the packet from Access 2 to ISP 2. ISP 2 says well I have to route it to this Loopback Interface where the BGP process is running and the BGP process is expecting to see the Neighbor Relationship form. However since that is seen as an extra hop, the TTL and the BGP packet decrements to zero since it defaults to one and therefore the Neighbor Relationship never sets up. Never fear, setting BGP Multihop is pretty simple it's just another argument on the Neighbor Statement. We'll finish this set up in the next video.
Tutorial Information
| Course: | Implementing Cisco IP Routing (642-902 ROUTE) |
| Author: | Greg Dickinson |
| SKU: | 34291 |
| ISBN: | 978-1-61866-028-2 |
| Release Date: | 2011-12-28 |
| Duration: | 10 hrs / 105 lessons |
| Work Files: |
Yes |
| Captions: | No |
| Compatibility: |
Vista/XP/2000, OS X, Linux QuickTime 7, Flash 8 |
VTC Sign up & Benefits
- Unlimited Access
- 81,350 Video Tutorials (14,200 free)
- Video Available as Flash or QuickTime
- Over 715 Courses
- $30 for One Month Access
- Multi-User Discounts Available
