[AUDIO LOGO]
So now that we've discussed some of those details of Ethernet
over MPLS, it's of course time to jump into the command line
and get this up and running.
So as usual, we'll bring up our topology first.
We'll talk about which devices we're going to be configuring
and what we're going to be building,
and then we'll jump into the command line and get this up
and running for customer B.
So for this demonstration, we're still on MPLS topology 2.
But this time, we're going to be dealing with customer B.
So what we're going to do is we're going
to extend this time VLAN 10--
we're going to extend this between router 7 and router 10,
customer B's headquarters and customer B's remote site.
Now of course, that means our configuration
is mostly going to be on router 2 and, once again, on router 5,
but this time, interface gigabit 4.
So just like we did with VPLS, we
are going to have the default some configurations and such,
but let's just go ahead and jump in and get started on router 2,
configuring our ethernet over MPLS interfaces.
So the first thing we're going to want to do
is default that interface.
So this is going to be interface gig 0000.
We'll commit that change just to make sure all
of the configuration is off the gig 0000 interface.
Then we'll start creating our VLAN 10 interface
that we're going to use for our l2 transport.
So we're going to say interface 0000,
and we're going to make a subinterface.
So we're going to make this 10.
Of course, the subinterface doesn't have to match the VLAN,
but once again it makes sense for it to do so.
And we're going to specify that this
is for a layer 2 transport.
We're going to set this for encapsulation dot1q
for VLAN 10.
Once again, of course, this does have
to match the VLAN we want to extend.
And we're also going to go ahead and set the MTU to 1514
to handle the extra trunking encapsulation.
We'll commit that change just so the interface is ready.
And then we're going to configure our l2vpn.
So here, we go into l2vpn configuration,
and we configure this using xconnect.
So we create an xconnect group.
We can call this whatever we want.
Let's call it customer B VPN.
Then, we're going to set the P2P tag to 10 without the space,
and then we'll assign our interfaces.
So we assign our subinterface of gig 0, 0, 0, 0, dot 10.
And then we configure our remote neighbor.
So this is going to be neighbor IPv4, router 5's loopback.
And then we set up a pseudowire ID.
Once again, we'll just use 10 since it's carrying VLAN 10.
We'll commit those changes, and then we
should be able to exit configuration here on router 2.
So now, let's go over and configure router 5.
So router 5, of course, on IOS XE
is going to be a bit different.
We still, however, want to default our interface,
so this is going to be gigabit 4.
Then we'll go into interface gigabit 4.
This is mostly going to be the same way as we did VPLS.
So we're going to set up our service instance.
This time, we'll do service instance 10,
keeping in step with everything using the VLAN number.
Again, it doesn't have to.
What does have to is, when we set up
our encapsulation for dot1q, this of course
does have to be VLAN 10.
Let's go ahead and exit out of this,
and we'll set up our l2vpn connection now.
So on IOS XE, we do l2vpn.
And then, of course, there's no sub configuration mode,
so we go right to xconnect and we set our context.
Once again, this is essentially just a name,
so we'll call it tag 10 just like we did on IOS XR.
Now, we get our sub configuration mode
for xconnect.
Now, we set up our members.
So we're going to set up a member--
is going to be a pseudowire.
The pseudowire, we just have to give it a number.
Once again, we'll stick with everything sort
of being 10 here.
We'll give it our neighbor's address,
which is going to be router 2's loopback.
We give it the identifier, and then we set the encapsulation
to run over MPLS.
The other member here, of course,
is going to be the gigabit interface.
So it's going to be gigabit 4, service instance 10.
We'll exit configuration.
We see our targeted LDP neighborship
to router 2 come up.
Let's go ahead and do some verification.
So we can do show l2vpn xconnect.
Actually, that's the IOS XR command.
Let's try the IOS XE command instead.
It's show l2vpn atom vc, for virtual circuit.
So here, we can see that we have our pseudo wires up, connected
between peer 1 and peer 2.
We're, of course, focusing right now
on pseudowire 10 going to router 2.
Pseudowire 100002 is from VPLS.
So focusing on the pw10, it is currently up.
It is a point-to-point link.
And we could get some more details on that
by adding VCID 10 and detail to the end of this.
So again, looking over this, lots of information,
but we see that it's pseudowire 10, it's up.
The vc status is up.
Pseudowire type is ethernet.
We see the destination address is router 2's loopback.
Our local egress interface is gigabit 1.4.
And it also shows us the label that it's
going to be using for this--
24002 and 24009.
We can also see down here under the signaling protocol
that, of course, the peer 10.2.2.2 is up,
but that it's a targeted hello going
from 10.5.5.5 to 10.2.2.2.
As we can see, there's a lot of information in here
that you can look over, including
again local and remote labels that are going to be used
and so on.
So let's go do our verification on router 2 now.
So now would probably be a good time to do the show
l2vpn xconnect, and it'll work much better here
than it did on IOS XE.
So as you can see, this is sort of the same as looking
at the atom virtual circuit that we looked at on IOS XE.
But again, we see that this is part of the xconnect group
customer B VPN.
Its name is tag 10.
Its current status is up, and segment one
is going out our local gigabit 0, 0, 0, 0, dot 10 interface,
and segment two going to the remote side
is going to 10.5.5.5.
We can also add to this and say interface gig 0, 0, 0,
0, dot 10, detail, and this will tell us
that this is a member of the group customer B VPN.
We see the xconnect tag.
The state is currently up.
And of course, we see the attachment
circuit is in fact the gigabyte 0, 0, 0, 0 dot 10, and it's up.
We see that it's a VLAN.
It's not rewriting tags, so the VLAN range here
is going to be-- well, 10 to 10, so essentially just 10.
We also see that for the pseudowire,
the neighbor is 10.5.5.5.
The pseudowire ID is 10.
And of course, the encapsulation is
MPLS using LDP as the protocol.
Once again, a lot more information here, but we
can get a lot of good stuff out of these commands.
So now that it looks like everything's working,
let's go ahead and verify our clients.
Let's jump over to router 7.
On router 7, we're simply going to create a VLAN 10 interface.
So this will be gigabit 1.10.
Encapsulation is going to follow VLAN 10.
And we'll give it an IP address of 192.168.10.7,
again representing VLAN 10 and host ID 7.
And we'll make that a slash 24.
While we're here, let's just go ahead and set up OSPF as well.
We'll go ahead and set the router ID,
and we'll just bring in all the interfaces into area 0.
Now, let's go configure router 10.
We've done a few of these now, so we'll just
paste the configuration in here on router 10.
Once again, we're simply creating a subinterface,
giving it the IP address, and setting up
OSPF on the interface.
So we see here that OSPF does come up
with router 7, which means we should have a couple of things
we can look at.
First, we should, of course, be able to ping the other side--
192.168.10.7.
We can see that that's successful.
If we do a show IP route OSPF, we
do see that we have a network that's
reachable on the other side.
Let's go ahead and trace to that this time.
So let's go to 10.100.1.7.
And we can see that just like our VPLS,
this appears to be going directly,
and we don't see any of the devices in the middle
because they're all being encapsulated
in our ethernet over MPLS tunnel.
In this video, we took a look at how
to set up a point-to-point connection using Ethernet
over MPLS for our customer B client
going between routers 7 and 10.
We also saw how, just like VPLS, once this is done,
we don't see any of the devices in the middle when we're
doing things like tracing.
It's because it's a direct layer 2 connection.
So that pretty much covers everything
that we need to discuss in this skill.
That leaves us with just a review in the form of a quiz,
and that's exactly what we're going to do next.
Until then, I hope this has been informative for you,
and I'd like to thank you for viewing.