[AUDIO LOGO]
So now it's time to finally jump onto the command line
and get VPLS up and running.
Now, we're going to start off by looking
at our topology, of course, and there
is going to be one change on that topology,
and we'll talk about what that is and why we needed it.
So let's go ahead and look at that topology,
and then we'll jump into the command line and get VPLS up
and running.
So for this demonstration, we're going
to be using MPLS topology 2.
Now, the reason this changes to 2 is simply because of router 1
right here.
You might notice that this is not called xr1 like I've
labeled the other routers.
That's because this router is now running iOS XE.
The reason for this is, as of the time of this recording,
iOS XR, the version that we are running, does not support VPLS.
So in order to do this, we had to swap out
router 1 with an iOS device.
Now, of course, router 3 and 4, they're
going to be fine because they're just in the transit path,
but iOS XR does not currently support the configuration
of the VPLS itself.
Now, that said, let's talk about what
we're going to be building.
We are going to take VLAN 100, and we're
going to connect router 6, router 8, and router 9--
all of customer A's sites.
So the headquarter, site 1 and site 2--
we're going to connect all of these
on the same VLAN, same subnet, and get them
so they can communicate with each other through VPLS.
So this means that the bulk of our configuration
will be on router 1 and router 5.
We'll also have the default some of these interfaces
because they do have things like IP addresses on them and such.
And we'll have to reconfigure the networks
on routers 6, 8, and 9 as well.
So let's go ahead and jump into the command line
and get started.
We'll begin on router 1.
So the first thing we want to do here on router 1
is go ahead and default interface gigabit 3 just
to wipe out any existing configuration.
And then we'll go ahead into gigabit 3
and start configuring it.
Now, the first thing we want to do
is assign a service instance.
This service instance can really use any number 1 through 8,000,
as you can see here.
But since we're doing all of this for VLAN 100,
let's just use the number 100 for it.
And we want to do this for ethernet encapsulation.
The next thing we want to do is set the encapsulation
for the trunk to be VLAN 100.
Now, this, of course, does have to be
because it's matching on the VLAN that we're trying to use.
Next, we need to make our l2vpn VFI configuration.
So we'll say l2vpn.
Again, this is vfi.
We give it a context, and this is just sort of any name.
So we'll do something like vfi100
since it's the vfi for VLAN 100 in our case.
We're going to set the VPN ID.
Now, this just has to match on both sides,
but again we'll just use 100--
just sort of make this easy to track what
we're trying to accomplish.
And then we have to set up a member.
The member is essentially the remote end,
so this is going to be router 5's loopback address.
And we want to use the encapsulation of MPLS.
So this takes care of our interface and our l2vpn vfi
configuration.
The next thing we need is a bridge domain.
Now, again, the bridge domain can pretty much
be any bridge domain ID.
Once again, it just makes sense to make everything consistent,
so we'll use bridge domain 100.
Just again, keep in mind, this does not
have to match the VLAN.
This is just a bridge domain identifier.
Now, we have to put our two members in here.
So the first member is gigabit 3--
specifically, service instance 100.
So this will tie the VLAN 100 on gigabit 3
into this bridge domain.
Keep in mind, by the way, we're doing encapsulation
for VLAN 100 right on the physical interface
of gigabit 3.
If we wanted to offer multiple services to the customer,
we could definitely do some interfaces on gigabit 3,
tie different VLANs to different subinterfaces,
and therefore, different service instances
to different subinterfaces.
That's how we would do this if we were
doing multiple emulated LANs.
So that goes ahead and ties that member.
The next thing we want to do is tie-in the vfi.
So we say member, vfi, then, of course,
we're going to put in the name of the vfi.
So we named it the vfi100, and that
should take care of the configuration here on router 1.
Notice two things here.
First, a little bit further out, but I didn't mention it
when it happened-- but we see pretty much as soon as we
created that vfi context, that line protocol on pseudo wire 0
changed to up.
And now that we have the rest of our configuration done,
notice that the status of VFI vfi100
has now changed from down to up.
Now, the next thing we have to do, of course,
is configure router 5.
Now, router 5 is going to be pretty much the same,
except we're doing two interfaces.
So in this case, we want a default interface
gigabit 2 and gigabit 3.
We'll go into our interface gigabit 2.
We'll set up our service instance of 100 for ethernet,
and we'll set up our encapsulation.
We'll do the same thing for interface gigabit 3.
So that takes care of the two physical interfaces.
Next, we'll do our l2vpn.
We'll set up our vfi.
Once again, our VPN ID will be 100.
The member will, of course, be router 1's loopback.
This is the pseudowire going back
to router 1 and, of course, it's using MPLS.
Now, we only need one vfi because we're only
going back to one other router.
And note, now that both sides are configured,
we now see that targeted LDP session come up to router 1.
Now, of course, we're still going to need our bridge domain
to link these together.
So again, we'll just use bridge domain 100 to be consistent.
We'll add our gigabit 2 interface,
we'll add our gigabit 3 interface,
and we'll add our vfi.
Once again, we see the vfi go up.
We'll exit configuration.
And let's do some verification.
Let's just go back to router 1 to do our verification.
So some good commands we can do here--
we can start with just a show bridge domain.
Things to note in the bridge domain-- it is
up and Mac learning is enabled.
And we also see that our gigabit 3 service instance 100
and our VFI vfi100 with the neighbor 10.5.5.5--
VPN ID 100 is currently up.
We can also do a show l2vpn vfi.
We see that our vfi name vfi100 is currently up.
It is a multipoint connection, and the signaling
is being done by LDP.
We saw that LDP session come up.
We also see the VPN ID of 100--
that it's attached to bridge domain 100 using
pseudo-port interface pseudowire,
and this is an automatically created number.
It just created 100001, and it's connecting interface pseudowire
100002 going over to router 5.
Another good command is if we take off the vfi
and instead say service vfi, and then
ask for the particular name vfi100,
we can get more information on this.
It's a slightly different output,
but we see both sides of the pseudowire,
so we see both of those numbers.
We see that one of them is, of course local,
and the other one is encapsulating MPLS going over
to router 5, but both of these are currently up.
Another good command to watch--
show ethernet service-- instance ID is 100 on interface gig 3,
and we can ask for detail.
Here, of course, we see the instance ID, which
is exactly what we asked for.
We see that it's associated to gigabit 3.
We see that the encapsulation is dot1q 100,
so it's going to VLAN 100.
The protocol type is 0x8100, which remember, is 802.1Q.
The status is currently up.
And we actually see that we have a couple of packets and bytes
coming in at this point.
So all of this looks like it's functioning properly.
Let's go ahead and check the actual connectivity
through our environment.
Let's go over to router 6, which is customer A's headquarters.
What we're going to do on router 6
is simply go into the interface gigabit 1--
set the IP address so that all of these
are on the same subnet.
So we'll set this to 192.168.100.6,
so just representative of VLAN 100 and host ID 6.
We'll just make that a slash 24, and exit configuration.
We'll do the same basic thing on routers 8 and 9.
And again, on router 9.
So now, let's do some testing.
We should be able to ping 192.168.100.6 and dot 8.
So we can see that after the ARP completes,
that we are, in fact, able to ping both of those devices.
Now, just for one final test, let's bring up
routing between our customers.
Now, we'll just do this a real quick, easy way.
We'll just bring up OSPF on all of the interfaces
on the customer's routers--
real simple configuration.
So let's go over to router 6.
Now, we've set this up numerous times,
so I'm just going to paste in the configuration.
Again, all we're doing is turning on OSPF,
setting the router ID, and then using the network statement
to put all interfaces into area 0.
We're going to do the same thing on routers 8 and 9.
We'll just be using a different router ID.
So that takes care of router 8 and router 9.
So we see here in the console that our neighborships
with routers 8 and 6 have both come up.
Let's go ahead and verify that.
If we do a show ip ospf neighbors,
we see that they are in fact up.
Router 6 is listed as the DR-OTHER, or the DROTHER.
Router 8 is listed as the BDR, which means router 9 here
is going to be the DR.
If we do a show IP route OSPF, we
see here that we are learning other routes
from the other routers in the customer a network.
Let's go ahead and verify that those are working.
Rather than a ping, let's go ahead and do this time.
Let's trace through that network on router 6.
Let's trace to the 10.100.1.6.
And notice that it looks like it's going directly.
We, of course, reached the destination.
That's working as it would be expected,
but we don't see any of the hops in the middle
because it's going through our l2vpn.
We can verify 8 as well.
It has an address 10.100.1.8, on it.
And this should look pretty much the same way.
We can see here that it does.
So this is working properly.
Our l2vpn is up and running, we have OSPF neighborships
between the customer routers, and we have full reachability
between the devices.
In this video, we got VPLS up and running for customer A
using VLAN 100 between all of their sites.
Now, of course, we could do different networks for them
if we wanted to.
This has just been an example of doing one,
but we could just duplicate exactly what
we did using, of course, different numbers
and subinterfaces.
So the next thing we want to look at is ethernet over MPLS,
and that's exactly what we get to look at next.
Until then, I hope this has been informative for you
and I'd like to thank you for viewing.