Posted by: Joshua Wood
Hello, I work for an ISP. As one of the tasks that I have deploying tech that isn`t necessarily new but is new to my company is part of my job. One of the exciting techs that I get to test and deploy is called MPLS or Multi-Protocol Label Switching. And it is awesome. When I was looking at deploying it for the company that I work for one of the frustrations that I had was getting a very basic pseudo-wire configuration off of the Internet. It seemed like I was mining for a needle in a haystack that that seemed like it should have been made of needles. It was bizarre.
Over the next few posts I am going to attempt to show you a very basic pseudo-wire MPLS configuration that I used in my labs. Before I do that though, let me outline what a pseudo-wire is. Pseudo-wire in the context of MPLS is typically a layer 2 tunnel between two endpoints that runs over a layer 3 network and uses the routing protocols of that network. Now of course it gets more complicated than that but in a very basic sense it is like taking a cable from one switch and running it virtually over a part of the internet to a switch in another building or city. Pretty cool stuff!!!
Now before I go too far, here is the design and layout that I am going to use. The configs and explanations will come later. This is a basic setup where the CE devices are the customer routers or switches and the P devices are anything the provider or core network. CE could also be branch devices in a large network.
Until next time,