WEBVTT

0:00:08.100000 --> 0:00:14.080000
 Okay, so for this next section we're
 going to take a look at MPLS and

0:00:14.080000 --> 0:00:20.060000
 a technology called 6PE, which basically
 means that we're going to be

0:00:20.060000 --> 0:00:26.620000
 running IPv6 between, in this example
 we're going to use switch 1 and

0:00:26.620000 --> 0:00:32.540000
 router 1, and then IPv6 between switch
 2 and router 4, and again we're

0:00:32.540000 --> 0:00:34.680000
 just going to do the top
 site again for this one.

0:00:34.680000 --> 0:00:39.180000
 I'm not even going to bring in router
 4 here, we don't really need to,

0:00:39.180000 --> 0:00:46.020000
 but we're going to be running IPv6 there,
 and in order to do this we have

0:00:46.020000 --> 0:00:50.660000
 to fire up some things in the core,
 and for some of this I have already

0:00:50.660000 --> 0:00:56.480000
 done it. So let me switch over here
 to a diagram that I can draw on a

0:00:56.480000 --> 0:01:03.860000
 little bit easier here, and we're going
 to be running BGP in the corner,

0:01:03.860000 --> 0:01:11.040000
 I already have this part set up, so
 I have BGP set up from R1 to R4, and

0:01:11.040000 --> 0:01:22.040000
 from R5 to R1, and in this case router
 1 is acting like a route reflector

0:01:22.040000 --> 0:01:30.880000
 for IBGP, and this multi-protocol BGP
 session is actually running address

0:01:30.880000 --> 0:01:38.760000
 families, IPv6, that's what we're going
 to use for this first part, and

0:01:38.760000 --> 0:01:52.760000
 then when we get into 6 VPE in
 the VPN, V6 address family.

0:01:52.760000 --> 0:01:56.460000
 So we're only going to be using one of
 those to start with, just the IPv6,

0:01:56.460000 --> 0:02:05.520000
 the whole thing with 6 PE is we're going
 to get IPv6 through an IPv4 core,

0:02:05.520000 --> 0:02:08.740000
 just like we've been doing with these
 other technologies, but the big

0:02:08.740000 --> 0:02:16.420000
 difference between this and 6 VPE is
 with 6 VPE we're actually going to

0:02:16.420000 --> 0:02:21.600000
 be using VRFs, and we'll be able to
 separate customer A from customer

0:02:21.600000 --> 0:02:26.040000
 B traffic, for example, and we may not
 go so far as to actually configure

0:02:26.040000 --> 0:02:32.120000
 customer B, I don't think we really need
 to, but we will run IPv6 through

0:02:32.120000 --> 0:02:35.260000
 a VRF on the PE routers.

0:02:35.260000 --> 0:02:46.640000
 Now for 6 PE, that's the one that's already
 up and running from our previous

0:02:46.640000 --> 0:02:53.340000
 lesson, OSPF between switch 1 and router
 1, OSPF between switch 2 and

0:02:53.340000 --> 0:02:58.480000
 router 4, I have already turned on
 MPLS in the core, and I'm going to

0:02:58.480000 --> 0:03:01.620000
 show you some of this stuff, and then
 we're just going to take a look

0:03:01.620000 --> 0:03:08.220000
 at how we actually get 6 PE across
 this, there's honestly one command

0:03:08.220000 --> 0:03:14.740000
 that's really sort of the magic here,
 so if we switch over to the other

0:03:14.740000 --> 0:03:21.820000
 one, let me show you the BGP stuff
 first, so do show run section BGP,

0:03:21.820000 --> 0:03:26.420000
 and I just want to show you that he
 has a neighbourship, and I used the

0:03:26.420000 --> 0:03:30.860000
 peer group here just to sort of shorten
 it up a little bit, it doesn't

0:03:30.860000 --> 0:03:34.860000
 help a whole ton when you start dealing
 with address families, because

0:03:34.860000 --> 0:03:39.180000
 as you can see you still have to activate
 each neighbour separately per

0:03:39.180000 --> 0:03:45.280000
 address family even with peer groups,
 now what it does shorten a little

0:03:45.280000 --> 0:03:51.000000
 bit is the whole send community extended
 under the VPN V4 and VPN V6 address

0:03:51.000000 --> 0:03:59.200000
 families, as well as having the route
 reflector client for the IPv6 and

0:03:59.200000 --> 0:04:04.360000
 both VPN address families, so what
 we're going to be starting with is

0:04:04.360000 --> 0:04:10.460000
 of course the address family IPv6, like
 I said the VPN address families

0:04:10.460000 --> 0:04:15.580000
 are for later, they're just already there,
 already built, already established,

0:04:15.580000 --> 0:04:20.520000
 and the neighbourships are up, if we
 go to four and five they're going

0:04:20.520000 --> 0:04:28.880000
 to look very similar, okay so on these
 guys we have the address families,

0:04:28.880000 --> 0:04:33.820000
 the neighbours, okay, and that's pretty
 much it just to send communities

0:04:33.820000 --> 0:04:39.840000
 because they're not route reflectors,
 so the multiprotocol IBGP is already

0:04:39.840000 --> 0:04:46.400000
 set up and running, and if I said do show
 IPv6 route OSPF, we should already

0:04:46.400000 --> 0:04:53.380000
 have, in this case we have switch twos,
 routes here already, and if we

0:04:53.380000 --> 0:05:08.360000
 were to go from switch one, so for
 the most part so far everything is

0:05:08.360000 --> 0:05:14.080000
 just basic routing, so we have an IPv6,
 BGP connection, and again notice

0:05:14.080000 --> 0:05:20.460000
 that with my IPv6 address family I'm
 doing IPv4 peers, so we talked about

0:05:20.460000 --> 0:05:28.980000
 this in the BGP section about running IPv6
 routes over an IPv4 neighbourship,

0:05:28.980000 --> 0:05:35.280000
 okay, the other thing we've already
 done is do show MPLS interface, and

0:05:35.280000 --> 0:05:38.360000
 you can see, and we can go to every
 device in the middle, I'm not going

0:05:38.360000 --> 0:05:42.020000
 to show you every single one, we'll
 say you know there's one, do show

0:05:42.020000 --> 0:05:50.380000
 MPLS interface, on router 3 is running
 on its three interfaces, do show

0:05:50.380000 --> 0:05:57.840000
 MPLS, LDP neighbour, so you can see
 the neighbourships are up, so two

0:05:57.840000 --> 0:06:01.300000
 ways you can do this part, of course
 you can go to the interface and you

0:06:01.300000 --> 0:06:09.760000
 can say MPLS IP, or the way I did it,
 if you say do show run section OSPF,

0:06:09.760000 --> 0:06:18.100000
 you can actually just turn it on with
 the MPLS LDP auto config command,

0:06:18.100000 --> 0:06:24.640000
 which just turns on MPLS on all interfaces
 running that instance of OSPF,

0:06:24.640000 --> 0:06:28.780000
 and since I'm using that instance of
 OSPF for the core, then that's all

0:06:28.780000 --> 0:06:33.240000
 the interfaces in the core, okay, so
 just for a little bit of a setup

0:06:33.240000 --> 0:06:39.720000
 here, just turned on MPLS on all the
 interfaces inside the cloud in our

0:06:39.720000 --> 0:06:58.900000
 diagram, okay, so just for the in here,
 and here, here, now this is actually

0:06:58.900000 --> 0:07:02.000000
 two interfaces on router 3, but on the
 drawing, I just haven't come together

0:07:02.000000 --> 0:07:09.880000
 there, and of course on router 4, and
 router 5, so those are all running

0:07:09.880000 --> 0:07:16.580000
 MPLS, nothing more than MPLS IP, well
 I actually did auto config, but

0:07:16.580000 --> 0:07:22.580000
 same thing, just enabling MPLS, and then
 our BGP session is set up, that's

0:07:22.580000 --> 0:07:28.960000
 it, and of course running OSPF out
 at the edges for IPv6, and the cool

0:07:28.960000 --> 0:07:38.920000
 thing is, with all of that setup, you're
 actually 95% of the way to 6

0:07:38.920000 --> 0:07:44.900000
 PE, we're almost there, okay, all we
 have to do is switch back over here

0:07:44.900000 --> 0:07:52.840000
 to the command line, and let's go to
 router 1, and there's really two

0:07:52.840000 --> 0:08:00.480000
 things we have to do, we have to say
 IP, V6, router, OSPF 1, and we have

0:08:00.480000 --> 0:08:07.600000
 to say to redistribute BGP 100, don't
 really have to do anything else,

0:08:07.600000 --> 0:08:21.600000
 we have to do the same thing on router
 4, there we go, and then of course,

0:08:21.600000 --> 0:08:30.540000
 under router BGP 100, you say address
 family, IPV6 unicast, redistribute

0:08:30.540000 --> 0:08:40.360000
 OSPF 1, now you don't have to do this
 part, but I usually do, to say match

0:08:40.360000 --> 0:08:49.400000
 internal, external, and NSSA, the default
 behavior, and this applies to

0:08:49.400000 --> 0:08:57.300000
 IPv4 and IPv6, the default behavior
 when you redistribute OSPF into BGP

0:08:57.300000 --> 0:09:04.220000
 is that it only gets OSPF internal
 routes, well, you know, if this is

0:09:04.220000 --> 0:09:09.240000
 our enterprise, and we have control over
 all of this, and we're controlling

0:09:09.240000 --> 0:09:14.520000
 that they're all internal, then that's
 fine, but in the case of maybe

0:09:14.520000 --> 0:09:18.800000
 this is a service provider, which I
 don't think they would be doing 6PE,

0:09:18.800000 --> 0:09:22.540000
 they would probably be doing 6VPE,
 but we'll do the same thing when we

0:09:22.540000 --> 0:09:26.700000
 get there, when I do the redistribution,
 I just include everything, if

0:09:26.700000 --> 0:09:30.620000
 it's coming in, I should pass it through
 BGP, that's sort of the way I'm

0:09:30.620000 --> 0:09:32.000000
 looking at it here.

0:09:32.000000 --> 0:09:38.720000
 So we hit enter there, and we go over
 to router 1, and we say router BGP

0:09:38.720000 --> 0:09:50.120000
 100, address family IPV6 unicast, and
 we say redistribute OSPF 1, match

0:09:50.120000 --> 0:09:52.060000
 internal, external, and NSSA.

0:09:52.060000 --> 0:09:57.840000
 Now, if we've done this correctly, we
 should be able to say do show BGP

0:09:57.840000 --> 0:10:01.640000
 IPV6 unicast, and we should have somewhere
 else coming from the other

0:10:01.640000 --> 0:10:04.200000
 side, and we do.

0:10:04.200000 --> 0:10:06.500000
 Here they are, okay?

0:10:06.500000 --> 0:10:15.840000
 So there's the 7 that we're getting
 from our local connection, and now

0:10:15.840000 --> 0:10:18.720000
 we have not selected these as best yet,
 it should though, give it a second

0:10:18.720000 --> 0:10:21.500000
 here, no, it's not going
 to yet, that's right.

0:10:21.500000 --> 0:10:24.540000
 I was trying to show you that this
 isn't quite right yet, and then I'm

0:10:24.540000 --> 0:10:27.080000
 expecting them to show up as best,
 well, they're not going to because

0:10:27.080000 --> 0:10:29.660000
 it's not quite right yet.

0:10:29.660000 --> 0:10:40.640000
 Here's the problem, is if I ask
 to see that prefix, okay?

0:10:40.640000 --> 0:10:49.040000
 What I don't have for this, okay, one available,
 no pass, best, inaccessible,

0:10:49.040000 --> 0:10:54.240000
 this is the exact same thing that we
 saw when we were doing this before.

0:10:54.240000 --> 0:11:03.600000
 At this point, there is no knowledge,
 no tie between BGP and MPLS.

0:11:03.600000 --> 0:11:06.960000
 So, oh yes, wonderful, we're running
 MPLS under all of this.

0:11:06.960000 --> 0:11:13.020000
 In fact, if I were to say do trace to
 4444, it's actually going to show

0:11:13.020000 --> 0:11:16.960000
 labels being passed through
 our environment.

0:11:16.960000 --> 0:11:22.040000
 So it's using label 18, which is a
 little hard to tell here, because I

0:11:22.040000 --> 0:11:26.000000
 didn't change label space or
 label range or anything.

0:11:26.000000 --> 0:11:30.260000
 So it's actually swapping label 18
 for label 18, that's technically a

0:11:30.260000 --> 0:11:35.100000
 label swap. But the point is, it is
 label switching through the core.

0:11:35.100000 --> 0:11:40.820000
 The problem that we have right now is
 he's still, he's using that mapped

0:11:40.820000 --> 0:11:45.380000
 IPv4 address that we saw in the previous
 lesson, but he's still saying

0:11:45.380000 --> 0:11:48.420000
 it's inaccessible just
 like he did before.

0:11:48.420000 --> 0:11:55.480000
 And the reason for this is very
 simple, there's no label.

0:11:55.480000 --> 0:11:59.280000
 We're not doing 6PE yet.

0:11:59.280000 --> 0:12:04.600000
 Right now, all we're doing is literally
 sending IPv6 routes across an

0:12:04.600000 --> 0:12:07.120000
 IPv4 BGP connection.

0:12:07.120000 --> 0:12:09.360000
 Okay, we've done that before.

0:12:09.360000 --> 0:12:12.140000
 And we saw before that
 this said inaccessible.

0:12:12.140000 --> 0:12:15.940000
 What makes this 6PE?

0:12:15.940000 --> 0:12:19.960000
 So if you want to call this the magic,
 the super command, the part that

0:12:19.960000 --> 0:12:28.180000
 makes it all work, is we have to say neighbor
 10, not 10, sorry, I'm unrodden

0:12:28.180000 --> 0:12:36.980000
 with neighbor 4444, send label.

0:12:36.980000 --> 0:12:38.840000
 And that's because
 it's a peer group.

0:12:38.840000 --> 0:12:43.800000
 So I actually need to say neighbor,
 I forget what I called it, peers I

0:12:43.800000 --> 0:12:55.120000
 think, send label.

0:12:55.120000 --> 0:12:58.520000
 And it's saying the update source does
 not loop back zero, which I thought

0:12:58.520000 --> 0:13:02.220000
 it was. So we'll go ahead
 and change that as well.

0:13:02.220000 --> 0:13:05.860000
 Up loop back zero.

0:13:05.860000 --> 0:13:10.780000
 And then hop over to router 4.

0:13:10.780000 --> 0:13:18.580000
 Neighbor 111, send label.

0:13:18.580000 --> 0:13:22.840000
 And capability changes,
 neighbor comes back up.

0:13:22.840000 --> 0:13:27.500000
 And now, let's go back and look
 at that route on router 1 again.

0:13:27.500000 --> 0:13:36.140000
 Notice now, it has an
 outgoing label of 23.

0:13:36.140000 --> 0:13:42.100000
 So now, it understands that when you're
 sending to this route, you're

0:13:42.100000 --> 0:13:44.080000
 putting a label on it.

0:13:44.080000 --> 0:13:49.640000
 So now that he knows he's no longer actually
 forwarding to this guy, he's

0:13:49.640000 --> 0:13:54.480000
 going to actually put a label
 on it of 23 as it goes out.

0:13:54.480000 --> 0:14:00.540000
 It also means, of course, that
 it's now got best as one.

0:14:00.540000 --> 0:14:07.160000
 So now, it's using the route,
 do show IPv6 route from BGP.

0:14:07.160000 --> 0:14:11.340000
 And you're going to see that we have
 two labels, two routes to get to

0:14:11.340000 --> 0:14:16.500000
 the other side, which means just like
 that, just by saying send label,

0:14:16.500000 --> 0:14:18.720000
 we're doing 6PE.

0:14:18.720000 --> 0:14:21.160000
 There's labels for this to
 go the whole way through.

0:14:21.160000 --> 0:14:29.300000
 If I said do show IPv6, SEF, for one
 of these prefixes, and I'll pick

0:14:29.300000 --> 0:14:31.340000
 on the 8-8 here.

0:14:31.340000 --> 0:14:41.080000
 You can see here that he's
 imposing two labels.

0:14:41.080000 --> 0:14:44.220000
 18, which is the forwarding label.


0:14:44.220000 --> 0:14:46.500000
 And we already knew that 18
 was the forwarding label.

0:14:46.500000 --> 0:14:49.580000
 When we did our trace up here,
 there it is, label 18.

0:14:49.580000 --> 0:14:53.400000
 Okay, so you can call that, let's see,
 oh goodness, can I think of all

0:14:53.400000 --> 0:14:55.060000
 the names I've heard for it?

0:14:55.060000 --> 0:14:59.860000
 Left label, top label, forwarding
 label, LDP label.

0:14:59.860000 --> 0:15:03.120000
 That's all I'm getting
 off the top of my head.

0:15:03.120000 --> 0:15:05.620000
 But that's all label 18.

0:15:05.620000 --> 0:15:10.300000
 Then the VPN label is label 23.

0:15:10.300000 --> 0:15:16.580000
 So even though this is not using VRFs,
 it's not separating the routing

0:15:16.580000 --> 0:15:19.300000
 tables on the PE routers.

0:15:19.300000 --> 0:15:23.940000
 It's still using labels because
 this is still a VPN.

0:15:23.940000 --> 0:15:30.780000
 Or again, a form of a tunnel because
 we're encapsulating our IPv6 into

0:15:30.780000 --> 0:15:37.100000
 labels. So you can see right there,
 it's going to put those two labels

0:15:37.100000 --> 0:15:41.060000
 on. And you know what, I said I wasn't
 going to bring router 6 into this,

0:15:41.060000 --> 0:15:42.460000
 but I think I am.

0:15:42.460000 --> 0:15:46.380000
 Let's go to router 5 because it
 will only take a minute anyway.

0:15:46.380000 --> 0:15:57.200000
 And on router 5, we will do IPv6 router,
 OSPF1, redistribute, BGP100,

0:15:57.200000 --> 0:16:08.620000
 router, BGP100, address family
 IP, v6, unicast, neighbor 10.

0:16:08.620000 --> 0:16:10.560000
 Oops, I keep one to do 10.

0:16:10.560000 --> 0:16:16.000000
 Neighbor 111. Send label.

0:16:16.000000 --> 0:16:24.700000
 And redistribute OSPF1, match
 internal, external NSA.

0:16:24.700000 --> 0:16:40.980000
 And if we've done everything right,
 6 should now have the routes to say

0:16:40.980000 --> 0:16:43.600000
 1. So there we go.

0:16:43.600000 --> 0:16:53.440000
 The reason I did this is I actually want
 to show you a trace from a router.

0:16:53.440000 --> 0:17:01.000000
 Okay, took it a couple seconds
 to stabilize there.

0:17:01.000000 --> 0:17:02.060000
 Let's do it again.

0:17:02.060000 --> 0:17:03.600000
 Just to get a nice clean trace.

0:17:03.600000 --> 0:17:09.080000
 Okay. So the main thing I want you to
 see is as this passes through, it

0:17:09.080000 --> 0:17:11.220000
 goes to router 5.

0:17:11.220000 --> 0:17:13.600000
 Okay, that's the first
 one here, of course.

0:17:13.600000 --> 0:17:15.620000
 Router 5 sends it to 3.

0:17:15.620000 --> 0:17:18.200000
 And it's showing you those
 mapped IPv4 addresses.

0:17:18.200000 --> 0:17:22.420000
 That's fine. But look what it's
 showing you for the labels.

0:17:22.420000 --> 0:17:25.580000
 It gets a 16 and a 23.

0:17:25.580000 --> 0:17:29.820000
 Then that gets to 23 where it
 gets a 16 and a 23 again.

0:17:29.820000 --> 0:17:35.360000
 For those of you familiar with MPLS,
 if you're not, then this is going

0:17:35.360000 --> 0:17:37.720000
 to be a little bit beyond
 the scope of this course.

0:17:37.720000 --> 0:17:42.580000
 But for those of you who are familiar
 with MPLS already, router 1 is doing

0:17:42.580000 --> 0:17:48.040000
 PHP or penultimate hot popping for his
 directly connected loopback, which

0:17:48.040000 --> 0:17:49.800000
 is the next hop.

0:17:49.800000 --> 0:17:54.420000
 Therefore, you lose the label 16, you
 deliver it to router 1 with just

0:17:54.420000 --> 0:18:00.980000
 label 23 on it. And that's how he knows
 which IPv6 route this goes to.

0:18:00.980000 --> 0:18:05.400000
 And then he delivers it
 to the IPv6 destination.

0:18:05.400000 --> 0:18:06.820000
 So it's pretty cool.

0:18:06.820000 --> 0:18:09.240000
 It's using labels switching
 through the core.

0:18:09.240000 --> 0:18:16.220000
 Now again, it's not real exciting here
 because of my labels are 16 and

0:18:16.220000 --> 0:18:18.080000
 16 and 18 and 18.

0:18:18.080000 --> 0:18:23.760000
 You'll see this a lot if you turn on
 MPLS after your core routing protocol

0:18:23.760000 --> 0:18:29.800000
 is stabilized because every router
 has the same routes in the routing

0:18:29.800000 --> 0:18:34.520000
 table and MPLS just starts
 at label 16 and goes up.

0:18:34.520000 --> 0:18:41.220000
 So in this case, if I were to say do
 show IP route, it's pretty clear.

0:18:41.220000 --> 0:18:45.160000
 And I'm on router 6, so I didn't want
 that because 6 is barely running

0:18:45.160000 --> 0:18:52.360000
 IP. I wanted to look at it
 on router 5, PE router.

0:18:52.360000 --> 0:18:56.520000
 Do you show IP route?

0:18:56.520000 --> 0:19:01.740000
 If you look at his routing table, router
 1's loopback is the first route

0:19:01.740000 --> 0:19:04.980000
 that it hits, so it gets label 16.


0:19:04.980000 --> 0:19:10.040000
 And you can see this, do
 show MPLS LDP bindings.

0:19:10.040000 --> 0:19:14.460000
 This is what you referred to as the
 lib or the label information base.

0:19:14.460000 --> 0:19:17.980000
 And this is all the labels it's
 going to be using for next hops.

0:19:17.980000 --> 0:19:23.100000
 So you can see it literally just starts
 at 1 and gives a label of 16,

0:19:23.100000 --> 0:19:26.820000
 17, 18, 19. It's really exciting.

0:19:26.820000 --> 0:19:28.820000
 It just walks the table.

0:19:28.820000 --> 0:19:33.500000
 And since everybody pretty much has
 the same routes, they're all pretty

0:19:33.500000 --> 0:19:37.840000
 much going to generate the same
 labels for the same destination.

0:19:37.840000 --> 0:19:41.680000
 So it's a little bit tricky to see, okay,
 label 16 is swapping with label

0:19:41.680000 --> 0:19:46.220000
 16, but label 23 stays end to end.


0:19:46.220000 --> 0:19:48.680000
 But that is in fact
 what's happening.

0:19:48.680000 --> 0:19:55.760000
 All right. And by the way, if we go
 to say router 1 and see how this all

0:19:55.760000 --> 0:20:05.300000
 ends, you can also look at the ELFIB,
 which is do show MPLS forwarding

0:20:05.300000 --> 0:20:09.360000
 table. And you can see he's
 got the IPv6 entries.

0:20:09.360000 --> 0:20:13.700000
 And right there, you can see where he
 ties that label 23 to the destination

0:20:13.700000 --> 0:20:15.220000
 that we trace to.

0:20:15.220000 --> 0:20:19.340000
 That means that if we went to the actual
 loop back, then we should see

0:20:19.340000 --> 0:20:24.880000
 label 24. So if we go back to six and
 instead of tracing to that client

0:20:24.880000 --> 0:20:29.980000
 network, if we trace to his loop
 back, it should be label 24.

0:20:29.980000 --> 0:20:33.840000
 See, there you go, 24, 24,
 24, the whole way through.

0:20:33.840000 --> 0:20:40.360000
 So as it comes in on router five, router
 five is imposing or pushing two

0:20:40.360000 --> 0:20:43.820000
 labels onto it, 16 and 24.

0:20:43.820000 --> 0:20:49.000000
 The 16 is to get to the next
 hop or router ones loop back.

0:20:49.000000 --> 0:20:55.220000
 24 is to ultimately tell us once it
 gets to router one to actually tell

0:20:55.220000 --> 0:21:00.800000
 us which route to follow and out which
 egress interface and next hop.

0:21:00.800000 --> 0:21:06.600000
 So all of this put together, all you're
 really doing is enabling MPLS

0:21:06.600000 --> 0:21:09.160000
 in the core. So that's a given.

0:21:09.160000 --> 0:21:13.600000
 And then the real trick
 is two fold, right?

0:21:13.600000 --> 0:21:17.760000
 Well, really, really sorted
 as one fold, honestly.

0:21:17.760000 --> 0:21:21.320000
 Two fold because you're redistributing
 two ways, but really, it's just

0:21:21.320000 --> 0:21:25.660000
 to do show run section router.

0:21:25.660000 --> 0:21:29.540000
 The real magic to this whole thing,
 of course, the really, really big

0:21:29.540000 --> 0:21:35.700000
 piece is this one right
 here, the send label.

0:21:35.700000 --> 0:21:41.160000
 If you don't send that label, then
 he doesn't generate the label.

0:21:41.160000 --> 0:21:43.560000
 He doesn't send the label
 to the other side.

0:21:43.560000 --> 0:21:47.880000
 And then it's going to be trying to
 forward IPv6 packets across IPv4,

0:21:47.880000 --> 0:21:50.380000
 and that's not going to work.

0:21:50.380000 --> 0:21:54.480000
 So this is how we do it for
 an MPLS enabled network.

0:21:54.480000 --> 0:21:58.960000
 If we don't want to use VRFs, this is
 going to be very, very, very similar

0:21:58.960000 --> 0:22:07.100000
 to 6 VPE. The only real difference is
 we're going to be doing VRFs rather

0:22:07.100000 --> 0:22:18.300000
 than just in this case, it's just straight
 routing VPE is simply bringing

0:22:18.300000 --> 0:22:21.040000
 VRFs to this equation.

0:22:21.040000 --> 0:22:24.120000
 So that's where we're going
 to hit in our next lesson.

0:22:24.120000 --> 0:22:26.780000
 And I'm going to clean up a little
 bit of what we have here before we

0:22:26.780000 --> 0:22:32.320000
 jump into that. So we'll
 see 6 VPE coming up next.

