Service Provider - Intra AS L2VPN 002 - Local Switching, Local Bridge Domain

[Music] how's it going everybody in this video we're going to go ahead and start diving into some of the basics to layer 2 VPN we're gonna start off with one of the easiest things to understand in terms of how the router actually does its job in terms of bridging so without having to create any connections between multiple routers we're going to allow R 2 and R 3 to communicate with each other through CS r 3 and the way we're going to do this is what they call local bridging or local switching so if you're familiar with the VLAN creation on a switch or you created a VLAN and you place two ports in a VLAN and then whatever's attached to those ports is able to communicate with each other same concept applies here the only thing we're doing is we're going globally kind of like you would have with frame relay I'm doing add LC to port mapping here we're just mapping a port to a port so we're basically passing through the data transparently between the routers so let's go ahead and take a look at the config it's pretty straightforward we're going to go out router 2 and we're gonna go ahead and get him configured so I'm going to jump up here and hostname oops hostname will be we'll be are to an interface gig 0/0 I'm gonna go ahead and don't shut that interface and bring it online I'm gonna do the same thing for CSR 3 whether this case here is gonna be our three we wrote up interface gate 1 and type in no shut as I've been host name is going to be our 3 in this case and what we're gonna do is a interface gate one IP address of 10.2 3.3 slash 24 and I'm router - we're gonna do a IP address of 10.2.32 slash 24 ok now let's see us are three this configuration is actually very very simple go to global config and we have to make sure that we enable interfaces gig 4 and 5 so interface gig for no shut and gig 5 no shut so pretty straightforward self that from that perspective what we're going to go do now is road type of meet connect command we're gonna give it a name we're gonna type in layer 2 VPN and then we're gonna say from gigabit for two gigabit five and that's it all you're doing okay there's nothing really in here to do on the shutdown the connection which we're not going to do if we do a show connect we can see that the connection is up so if I go to router 2 and I do ping 10.22 3-3 after it Arps I should have paint reach ability do show ARP and I have connectivity which is verified that this MAC address matches on CSUN router 3 so do show interface gig 1 and if you looking up here at the top we have 5 0 0 0 0 0 1 2 0 0 0 0 guess what that matched that matches the MAC address than the ARP so that ladies and gentlemen is how simple layer to bridging can be so that's pretty much the basics to that now there's a couple of other variations that come into play as well so pretty straightforward stuff as you can tell the ping worked and everything else is good there's another variation of this known as the bridge domain so we'll get more familiar with bridge domains in a upcoming set of videos so the concept of the bridge domain is really no different than that of a VLAN where you go and you create the bridge domain and then you play sports in side of the bridge domain and then go from there so let's go ahead and take a look at exactly how that's gonna look so we'll go in here and type in bridge - domain and we're gonna give it a name a number we'll give it 23 4 routers 2 & 3 and underneath here you just need to specify the member so I'll type in member and then we'll specify gigabit and then we'll say 1 or gigabit 4 and then a service instance of 23 and we'll do gigabit five service instance 23 so that means that they're in the same service instance and they'll be in good shape there so that's pretty much all that that really requires there is not much more to it than that and then what we just have to go to do is interface range gig for 305 and type in service in service - instance service although it doesn't want one let me do it in range mode so interface gig for service instance will type in 23 eat is Ethernet and the encapsulation will be just default so we won't care what the actual the VLAN ID is that is being sent to us we're just going to go in here and take whatever was the same thing for Jake 5 hit the up arrow a couple times service instance 23 and then encapsulation is defaults so by doing that show bridge - domain we have both ports or should be up and running and we might have to do some manipulation but we should be okay so if I go back to router - when I try to do that ping again it should work relatively easily and if I go back to CS r3i you can see that there is communication between them so we're learning the Associated MAC addresses on those specific devices so basically what's happening here is the bridge domain has been created right so let's go ahead and let's do a show or on section bridge domain and all we're doing is we're creating basically a VLAN and then we go underneath this guy and we map who's gonna connect to us we're in a VLAN you would create the VLAN and then you go underneath the interface and say I'm gonna join this particularly LAN very simple concept so once you've done that and you can create the bridge domain you've gone and pulled in the member interfaces and then you go underneath the member interfaces so she'll run interface gig for and you do gig 5 you can as you can see the configuration is very straightforward but we can be more granular now what's cool about this is now you've had a basic exposure to a bridge domain right so now you know the concept theme of the bridge domain and I know the content of the VLAN so they're they're basically one of the same right they work together very very well the difference the thing that you'll supply it with bridge domains later on is we when we get into technologies like VPLS virtual private LAN service where bridge domains are used to do mac address learning and propagation and things like that so that's the only other thing that comes into play here that's a little bit unusual is how that's bridged together we'll talk about that more when we actually get into VPLS but this is one of those concepts that once you understand what actually happening it's very very easy to work with so the bridge domain is actually very very popular so the way I'm showing you is the new configuration there is an older configuration but I'll show you that in a later point in time but right now this is where the majority of your newer service writers are going at least in my experience most urban spreaders that I've worked with that's the contract that they use for doing any type of layer 2 VPN type of operation so it does work the cool thing is is now unlike the connect capability here you actually get to see what MAC addresses are being learned now this is locally significant right if I had pseudo wires configured to other routers and I was doing like a manually configured VPLS type of the design then you would see pseudo wire connections to other connections so the so the other routers that are learning in MAC address information and then using pseudo wires to pipe that information from one router to another I'll talk about that more in detail later but one of the one of the capabilities here that I want to talk about briefly is the Ethernet flow point or ESP now basically that is going to be a construct that was made up a number of years ago and the idea is to move away from the X Connect mindset where actually Connect was very limiting you didn't have a ton of feature capabilities and things like that Ethernet flow point allows a lot of additional capabilities like specific VLAN tagging longest match tagging so on and so forth so and I could bring in a specific tag and swap out for a different tag so there's a lot of different capabilities as you come into play with how all this stuff works we're going to be diving down those rabbit holes as we proceed and but the main thing that I want you guys to understand in particularly from this is that whether you're using the connect command or you or you're using the bridge command it really doesn't make much of a difference so the idea here that I want to just touch briefly on it every gig for and you have the service instance command service instance then you type in you know 23 and you say Ethernet come underneath here there's a number of different ways that you can do this so you notice how down here bridge domain I found this type in bridge domain and I could type in 23 and do the command this way as well so if I was to actually get out of here and do show run section bridge and remove the bridge domain configuration so this this specific command right here with the then tighten the member interfaces to the bridge domain globally makes it more modular it's like it kind of mix and matches on going along where now I'm going globally and I'm tying the interface to the global construct versus going to the interface level and tying the bridge domain to the interface so this one here makes it more modular where the interface level is more specific right so it's definitely more complicated to troubleshoot and things like that so I'm just gonna go ahead and here and delete the bridge domain I'm gonna go into an interface gig for and type in service instance 23 either net and then bridge domain will type in 23 and then there's a split horizon option here we don't really need to worry about that too much now if I go to gate 5 into the exact same thing and do this and do show run interface gig for you can see a different configuration right now if I come on here and I do a show bridge - domain same concept applies really nothing has changed so I go back to router 2 when I hit the up arrow on that ping I go back to router 3 and I hit the up arrow you look at you can see it the same look and feel it's just two different ways of configuring it right so one way you create the bridge domain globally and then you go to the interface level and then you tie the service instance to it where you and you can really call whatever service instance you want the bridge domain the server systems are kind of they don't have to match but it makes it easier to correlate down the road it's like you know for example if you're dealing with I've just started diving into a little bit of voice where if you don't tie things correctly to your directory numbers things get a little hard to troubleshoot so here it makes it easier to work with when you have a scenario where you're tying things together the way they need to be tied so for an example of this would be this interface gig for word type in let's go ahead and interface gig for and we'll type in no service instance 23 Ethernet right and then we're gonna type in service instance we'll type in for Ethernet and then we're type in bridge underneath here it would be the encapsulation we have to call is going to be default and then underneath year we'll be able to specify the bridge domain down the road there's also the X Connect down here as well but we're not really going to dive into that right now so bridge bash domain and we can call 23 and then we go to interface gig 5 for example so interface gig 5 do show run interface gig 5 and we can pull this guy off and that we've had been service instance 5 Ethernet excuse me and then encapsulation default and then Bridge domain 23 and hit the enter key and then if we jump out a global config into a show bridge - domain it's there right the 23 is is there but we have EFP 4 and if we go back to 2 and we hit the up arrow the ping is gonna work we go back to see sr3 we can see that EFP 5 but because the fact we've used two different service instances and we can see that service instance for server senses 5 is tied to Bridget on May 23 it doesn't really make much of a difference how you configure it as long as you type the logic the bridge domain is the is the the big deal here as long as that's there then you'll be in really good so we'll talk more about so many other capabilities to come that work with this later on down the road but for right now that's basically what I wanted you guys to see so until next time guys thanks so much for stopping by and we'll catch you guys in the next video [Music]

Channel: Rob Riker's Tech Channel

Views: 1,985

Rating: 5 out of 5

Keywords: ccnp, ccie, service provider, mpls, layer 2 vpn, l2vpn, intra as

Id: EfFeNVhjSXs

Length: 15min 2sec (902 seconds)

Published: Sat Jun 13 2020