WEBVTT

0:00:08.180000 --> 0:00:15.880000
 Okay, so let's jump in with just
 standard GRE tunnels over IPv6.

0:00:15.880000 --> 0:00:19.540000
 So for this we're going to be
 using a different topology.

0:00:19.540000 --> 0:00:25.120000
 This is also saved out there
 under IPv6 VPN topology.

0:00:25.120000 --> 0:00:32.800000
 And the basic idea here is we're going
 to use this for VPN, MPLS, really

0:00:32.800000 --> 0:00:37.760000
 for all of our tunneling
 or VPN technologies here.

0:00:37.760000 --> 0:00:40.560000
 We're going to start with GRE and we're
 not going to use all of these

0:00:40.560000 --> 0:00:44.160000
 devices for all of the sections,
 there's really no need.

0:00:44.160000 --> 0:00:48.940000
 But this is the topology that's built
 that will support everything we

0:00:48.940000 --> 0:00:51.320000
 needed to support moving forward.

0:00:51.320000 --> 0:00:59.360000
 The important thing to understand here
 is that the switches are just acting

0:00:59.360000 --> 0:01:01.220000
 like end devices.

0:01:01.220000 --> 0:01:06.420000
 They have, and we have the IPv4 address
 listed here, but it corresponds

0:01:06.420000 --> 0:01:11.600000
 with what the IPv6 address is going
 to be on that subnet as well.

0:01:11.600000 --> 0:01:14.980000
 Okay, and you'll see
 those as we go.

0:01:14.980000 --> 0:01:20.540000
 VLANs, 71, 91, 84, 65, 105.

0:01:20.540000 --> 0:01:24.300000
 These are all IPv6
 enabled already.

0:01:24.300000 --> 0:01:30.180000
 Now, our PE routers, which again, it
 may not be provider, it could of

0:01:30.180000 --> 0:01:32.800000
 course also just be
 your edge routers.

0:01:32.800000 --> 0:01:34.480000
 That's irrelevant.

0:01:34.480000 --> 0:01:36.920000
 We're just looking at
 the technologies here.

0:01:36.920000 --> 0:01:41.780000
 But those are also already configured
 with IPv6 addresses.

0:01:41.780000 --> 0:01:48.080000
 But as we move into technologies such
 as MPLS and such, we will be redoing.

0:01:48.080000 --> 0:01:53.300000
 So we're going to start with just GRE
 and we'll just build one tunnel

0:01:53.300000 --> 0:01:55.760000
 between R1 and R4.

0:01:55.760000 --> 0:02:01.700000
 So essentially, we're just going to get
 our IPv6 from switch one to switch

0:02:01.700000 --> 0:02:07.600000
 two across the top there and
 tunnel between R1 and R4.

0:02:07.600000 --> 0:02:15.720000
 The most important thing to note about
 this diagram is that the core in

0:02:15.720000 --> 0:02:21.380000
 the middle there, everything inside the
 cloud, if you will, is IPv4 only.

0:02:21.380000 --> 0:02:23.840000
 And it's going to remain
 that way the whole time.

0:02:23.840000 --> 0:02:27.540000
 There's no IPv6 in the cloud.

0:02:27.540000 --> 0:02:35.260000
 So as we move into this, let's hop over
 here to our command line, let's

0:02:35.260000 --> 0:02:42.440000
 take a look. Like on router one, for
 example, if I were to say, let's

0:02:42.440000 --> 0:02:52.300000
 say, do show IPv6 route, all he has
 is literally a route to null zero.

0:02:52.300000 --> 0:02:55.380000
 That's it. He has no IPv6 routes.

0:02:55.380000 --> 0:03:01.140000
 If I said do show IPv6 interface brief,
 he's going to have addresses,

0:03:01.140000 --> 0:03:09.120000
 like I said, on his 71 and 91 interfaces
 going out to the switches, but

0:03:09.120000 --> 0:03:10.800000
 not anything on the core.

0:03:10.800000 --> 0:03:16.780000
 His core interface is F800.12 and
 that is currently on a sign.

0:03:16.780000 --> 0:03:23.960000
 Also, if I said do show IP route, I
 want you to note that the only IPv4

0:03:23.960000 --> 0:03:31.980000
 routes he has is to either connected interfaces
 or the other devices loopbacks.

0:03:31.980000 --> 0:03:35.660000
 Now the loopback numeration,
 it's on the diagram there.

0:03:35.660000 --> 0:03:38.420000
 It's a little bit different
 than what we did before.

0:03:38.420000 --> 0:03:42.100000
 It's just the device numbers
 all the way out.

0:03:42.100000 --> 0:03:46.880000
 So just to jump in, the first thing
 we're going to do is we need to fire

0:03:46.880000 --> 0:03:51.860000
 up, well, you know, need to use
 a bad word, I suppose, right?

0:03:51.860000 --> 0:03:57.760000
 We could always do static routes, but
 we're going to fire up a routing

0:03:57.760000 --> 0:04:00.820000
 protocol over all of this.

0:04:00.820000 --> 0:04:08.600000
 So we're going to say, in this case,
 we'll say rack one, R1, we're going

0:04:08.600000 --> 0:04:17.100000
 to say interface tunnel zero, and we
 will say tunnel, well, I just said

0:04:17.100000 --> 0:04:19.160000
 about the protocol and I'm
 jumping into the tunnel.

0:04:19.160000 --> 0:04:23.300000
 Let's do our protocols first, although
 we could turn it on here as well

0:04:23.300000 --> 0:04:24.800000
 since we're already here.

0:04:24.800000 --> 0:04:30.000000
 We'll just do EIGRP, just
 to pick one to start with.

0:04:30.000000 --> 0:04:37.620000
 So, IPV6, EIGRP 100, easy
 enough, interface.

0:04:37.620000 --> 0:04:40.260000
 And like I said, this is just going
 to be the one up at the top.

0:04:40.260000 --> 0:04:51.820000
 So this is going to be interface FAA00
.71, also running EIGRP 100, and

0:04:51.820000 --> 0:04:58.660000
 then IPV6 router, EIGRP 100, that
 starts the global process.

0:04:58.660000 --> 0:05:06.300000
 Do show IPV6, EIGRP interface,
 and it's 71.

0:05:06.300000 --> 0:05:15.700000
 Perfect. Okay. We can do the exact same
 thing over on router four as well.

0:05:15.700000 --> 0:05:19.140000
 So if you take a look at the diagram
 here, remember, we're going from

0:05:19.140000 --> 0:05:22.400000
 router one to router four, okay?

0:05:22.400000 --> 0:05:26.700000
 And then of course, it can involve
 VLAN 71 and VLAN 84.

0:05:26.700000 --> 0:05:29.580000
 That's all we're going to
 work on for right now.

0:05:29.580000 --> 0:05:31.640000
 Okay? So I just want to make sure everyone
 here understands where we're

0:05:31.640000 --> 0:05:43.460000
 at. So on router four, interface tunnel
 zero, IPV6, EIGRP 100, interface

0:05:43.460000 --> 0:06:02.760000
 FAA00.84, oops. Also, in EIGRP 100
 and then router, IPV6 router, EIGRP

0:06:02.760000 --> 0:06:06.340000
 100, and then our switches.

0:06:06.340000 --> 0:06:20.480000
 So switch one, interface loopback zero,
 IPV6, EIGRP 100, loopback zero,

0:06:20.480000 --> 0:06:24.400000
 IPV6, EIGRP 100, and one by the way,
 is the one that has the, we'll call

0:06:24.400000 --> 0:06:26.420000
 it the client prefix.

0:06:26.420000 --> 0:06:28.600000
 Let me just show you
 here real quick.

0:06:28.600000 --> 0:06:32.620000
 Do show IPV6 interface brief.

0:06:32.620000 --> 0:06:40.480000
 If you look at his loopback
 one, this is a slash 64.

0:06:40.480000 --> 0:06:46.360000
 Okay? So this is sort of like the client
 subnet that this switch is presenting.

0:06:46.360000 --> 0:06:50.640000
 And then this is his like normal
 management loopback, if you will.

0:06:50.640000 --> 0:06:52.580000
 So I'm going to bring
 them both in EIGRP.

0:06:52.580000 --> 0:06:53.880000
 It doesn't really matter.

0:06:53.880000 --> 0:06:58.660000
 I really just want the loopback one,
 but we'll bring them all in.

0:06:58.660000 --> 0:07:16.940000
 Okay? And then of course router, IPV6,
 EIGRP 100, and that's backwards.

0:07:16.940000 --> 0:07:20.080000
 Okay? And then switch two.

0:07:20.080000 --> 0:07:25.620000
 Here's a good thing we can, you know,
 we can just say, well, I had type

0:07:25.620000 --> 0:07:27.500000
 of this and it's not going to
 help us really switch two.

0:07:27.500000 --> 0:07:29.200000
 It doesn't really matter.

0:07:29.200000 --> 0:07:37.180000
 Interface loopback zero, IPV6, EIGRP
 100, interface loopback one, EIGRP

0:07:37.180000 --> 0:07:43.640000
 100, interface VLAN,
 and this is 84.

0:07:43.640000 --> 0:07:50.620000
 EIGRP 100, IPV6, router,
 EIGRP 100.

0:07:50.620000 --> 0:07:53.280000
 Neighbors should come up.

0:07:53.280000 --> 0:08:02.860000
 So two and four up, although I did not
 see, switch one and R1 never came

0:08:02.860000 --> 0:08:07.980000
 up, never did the, never
 did the VLAN interface.

0:08:07.980000 --> 0:08:10.400000
 Interface VLAN 71.

0:08:10.400000 --> 0:08:16.680000
 There we go. Neighbors
 should come up.

0:08:16.680000 --> 0:08:20.540000
 Okay. So if we've done our job correctly,
 we should be able to go to router

0:08:20.540000 --> 0:08:27.100000
 one now and say do show IPV6 route, EIGRP,
 and he should have router one's

0:08:27.100000 --> 0:08:29.020000
 information, which he does.

0:08:29.020000 --> 0:08:31.720000
 We should be able to go
 over to router four.

0:08:31.720000 --> 0:08:44.340000
 Do show IPV6 route, EIGRP, and he should
 have router fours, sorry, switch

0:08:44.340000 --> 0:08:46.940000
 two's information, which he does.

0:08:46.940000 --> 0:08:51.900000
 So that's good. So now we
 go back to our tunnel.

0:08:51.900000 --> 0:08:56.020000
 Okay. So interface tunnel zero.

0:08:56.020000 --> 0:09:04.800000
 And we say IPV6 address, I don't know,
 2001, DB8 colon 100 colon 200 colon

0:09:04.800000 --> 0:09:08.740000
 colon and he's the fore
 end of that slash 64.

0:09:08.740000 --> 0:09:13.340000
 Okay. So we put an IPV6 address on the
 tunnel and we can do that on both

0:09:13.340000 --> 0:09:35.700000
 sides. Okay. And then tunnel source
 is going to be loop back zero.

0:09:35.700000 --> 0:09:41.240000
 Tunnel destination is four,
 four, four, four.

0:09:41.240000 --> 0:09:43.340000
 That's router four's address.

0:09:43.340000 --> 0:09:46.600000
 They're going to say that it's up.


0:09:46.600000 --> 0:09:47.960000
 We know that's nonsense.

0:09:47.960000 --> 0:09:49.080000
 It's a false up.

0:09:49.080000 --> 0:09:54.720000
 If you want, you could say like keep
 two and send keep lives every two

0:09:54.720000 --> 0:09:57.340000
 seconds. Then within six seconds, it
 should tell me the tunnel's down

0:09:57.340000 --> 0:10:00.480000
 because there are no keep
 lives on the other side.

0:10:00.480000 --> 0:10:02.520000
 These are GRE keep lives.

0:10:02.520000 --> 0:10:03.260000
 Okay. There we go.

0:10:03.260000 --> 0:10:04.300000
 Tunnel goes down.

0:10:04.300000 --> 0:10:08.160000
 That's when it realizes, oh wait,
 the other end's not really up.

0:10:08.160000 --> 0:10:15.000000
 Okay. The only thing this up meant
 just like any other GRE is that you

0:10:15.000000 --> 0:10:18.500000
 have a route to get to
 the tunnel destination.

0:10:18.500000 --> 0:10:21.080000
 That's all it really means.

0:10:21.080000 --> 0:10:27.480000
 All right. So router four, tunnel source,
 loop back zero, tunnel destination

0:10:27.480000 --> 0:10:36.940000
 111. That's like IPV geometry
 or something.

0:10:36.940000 --> 0:10:38.680000
 I don't know what that was.

0:10:38.680000 --> 0:10:43.840000
 And then of course keep two and
 the tunnel should come up.

0:10:43.840000 --> 0:10:49.200000
 Router one's side should come
 up once the keeps kick in.

0:10:49.200000 --> 0:10:52.080000
 I'm not going to leave the keeps on
 there because as we move forward to

0:10:52.080000 --> 0:10:58.360000
 other interfaces, interface types is
 not going to work because keep lives

0:10:58.360000 --> 0:11:07.780000
 are only supported on GRE tunnels.


0:11:07.780000 --> 0:11:11.840000
 In fact, it may not work without an
 IPV four address anyway since both

0:11:11.840000 --> 0:11:13.860000
 sides just went down.

0:11:13.860000 --> 0:11:17.580000
 We're not going to keep
 them on there anyway.

0:11:17.580000 --> 0:11:25.020000
 Just do you know, we're about to
 change this off of a GRE anyway.

0:11:25.020000 --> 0:11:28.780000
 And there you can tell already it's working
 because ERP just came up over

0:11:28.780000 --> 0:11:36.720000
 the interface. So now if I said
 do show IPV six route ERRP.

0:11:36.720000 --> 0:11:39.160000
 And now we have the routes
 from both sides.

0:11:39.160000 --> 0:11:51.820000
 So if we were to go back to say switch
 one, do show IPV six route ERRP.

0:11:51.820000 --> 0:12:03.240000
 Okay. And we were to say do trace and
 let's trace to well as trace to

0:12:03.240000 --> 0:12:11.480000
 what would effectively be okay.

0:12:11.480000 --> 0:12:17.540000
 And there you can see that it hits
 the tunnel on router one comes out

0:12:17.540000 --> 0:12:20.600000
 the tunnel on the other end on router
 four and gets delivered to switch

0:12:20.600000 --> 0:12:23.880000
 to. Okay. So very, very simple.

0:12:23.880000 --> 0:12:26.960000
 Of course, you know, the glory of this
 whole thing is you go to say router

0:12:26.960000 --> 0:12:29.580000
 two, which is a device
 in the core.

0:12:29.580000 --> 0:12:36.740000
 And you say do show IPV six interface
 brief and he has nothing.

0:12:36.740000 --> 0:12:38.800000
 Unassigned, unassigned,
 unassigned.

0:12:38.800000 --> 0:12:40.780000
 Everything's unassigned.

0:12:40.780000 --> 0:12:43.680000
 Do show IPV six route.

0:12:43.680000 --> 0:12:46.980000
 He's not even running
 IPV six routing.

0:12:46.980000 --> 0:12:51.480000
 So again, this is just
 standard GRE tunnel.

0:12:51.480000 --> 0:12:56.720000
 Okay. Now if we take a look at this
 and we go over to let's go back to

0:12:56.720000 --> 0:13:10.100000
 switch one. And let's say do ping
 protocol is IPV six target.

0:13:10.100000 --> 0:13:14.060000
 We'll just ping his loop back
 just to make it easy.

0:13:14.060000 --> 0:13:18.100000
 Repeat count one.

0:13:18.100000 --> 0:13:20.220000
 Data gram size. I don't care.

0:13:20.220000 --> 0:13:23.580000
 Time out one. This is
 all fast ethernet.

0:13:23.580000 --> 0:13:25.360000
 It shouldn't take long.

0:13:25.360000 --> 0:13:26.640000
 Extended commands.

0:13:26.640000 --> 0:13:28.900000
 Yes. Source interface.

0:13:28.900000 --> 0:13:33.660000
 I don't care. UDP protocol
 is no verbose is no.

0:13:33.660000 --> 0:13:38.280000
 I don't care about changing the
 precedence or the DSCP value.

0:13:38.280000 --> 0:13:40.900000
 I don't necessarily need
 to see hop by hop.

0:13:40.900000 --> 0:13:43.440000
 We did that with a
 trace destination.

0:13:43.440000 --> 0:13:45.820000
 No sweep range of sizes.

0:13:45.820000 --> 0:13:48.780000
 Yes. Minimum sweep size.

0:13:48.780000 --> 0:13:50.920000
 I'm going to do 1401 bytes.

0:13:50.920000 --> 0:13:53.240000
 And I'm going to say the max size.


0:13:53.240000 --> 0:13:57.340000
 I don't care because I'm going to stop
 as soon as it starts failing anyway.

0:13:57.340000 --> 0:13:59.040000
 And the sweep interval is one.

0:13:59.040000 --> 0:14:00.920000
 That's how much is
 going to jump by.

0:14:00.920000 --> 0:14:03.460000
 What this means by the way, if you've
 never done this, this means it's

0:14:03.460000 --> 0:14:06.120000
 going to start with
 a ping of 1401.

0:14:06.120000 --> 0:14:11.040000
 And then it'll be 1402,
 1403, 1404, and so on.

0:14:11.040000 --> 0:14:17.580000
 If I said sweep interval two,
 it would do 1401, 1403, 1405.

0:14:17.580000 --> 0:14:18.900000
 It would jump by two.

0:14:18.900000 --> 0:14:21.000000
 So that's how much it's
 going to jump each time.

0:14:21.000000 --> 0:14:22.680000
 So I'm going to start the ping.

0:14:22.680000 --> 0:14:26.920000
 And as soon as it hits, oh.

0:14:26.920000 --> 0:14:32.080000
 Let's stop that.

0:14:32.080000 --> 0:14:39.660000
 There we go. And the problem is, yeah,
 this isn't going to really do what

0:14:39.660000 --> 0:14:41.660000
 I want to do unfortunately.

0:14:41.660000 --> 0:14:45.100000
 This has to do with that whole
 packet two big thing.

0:14:45.100000 --> 0:14:50.540000
 We could count those packets right
 there to figure out what the actual

0:14:50.540000 --> 0:14:56.080000
 MTU is. But do you show
 interface tunnel zero?

0:14:56.080000 --> 0:15:05.180000
 There's unfortunately because we don't
 have the fragmentation built into

0:15:05.180000 --> 0:15:10.900000
 IPv6 like we talked about back
 in the introduction part.

0:15:10.900000 --> 0:15:15.860000
 Unfortunately, sweeping the range of
 sizes isn't quite as nice as it is

0:15:15.860000 --> 0:15:19.820000
 on IPv4 because you don't
 have a don't fragment bit.

0:15:19.820000 --> 0:15:23.520000
 The device isn't the middle
 can fragment anyway.

0:15:23.520000 --> 0:15:32.520000
 So basically what it means is that at
 1478, it should be what we managed

0:15:32.520000 --> 0:15:38.140000
 to get through here
 from a payload size.

0:15:38.140000 --> 0:15:40.220000
 But that's not entirely
 correct either.

0:15:40.220000 --> 0:15:44.460000
 Again, it's not going to be a really
 good indicator here as to what our

0:15:44.460000 --> 0:15:50.200000
 actual MTU is. Why did
 that not show me?

0:15:50.200000 --> 0:15:52.700000
 Oh, I'm on the switch.

0:15:52.700000 --> 0:16:06.540000
 Sorry. You can see that the way IPv6 handles
 the MTU is completely different

0:16:06.540000 --> 0:16:10.160000
 anyway because it uses
 the path MTU discovery.

0:16:10.160000 --> 0:16:14.540000
 But basically at the end of the day,
 what we're saying here is that right

0:16:14.540000 --> 0:16:21.640000
 now our tunnel and protocol transport
 is GRE over IP, which means we're

0:16:21.640000 --> 0:16:26.340000
 getting an extra header
 of GRE right now.

0:16:26.340000 --> 0:16:30.480000
 The only thing we're running
 over this tunnel is IPv6.

0:16:30.480000 --> 0:16:35.860000
 So there's actually no need whatsoever
 to have a GRE header.

0:16:35.860000 --> 0:16:37.540000
 But that's the default.

0:16:37.540000 --> 0:16:39.500000
 That's it. It's very simple.

0:16:39.500000 --> 0:16:48.260000
 The advantage to this of course is that
 we could actually run IPv4 over

0:16:48.260000 --> 0:16:51.120000
 this if we wanted to and so on.

0:16:51.120000 --> 0:16:53.680000
 We're going to change
 that in a minute.

0:16:53.680000 --> 0:16:56.840000
 But I just want you to note right now
 that the tunnel transport MTU is

0:16:56.840000 --> 0:17:02.820000
 1476. So we'll come back and we'll
 take a look at this tunnel again in

0:17:02.820000 --> 0:17:04.060000
 our next section.

0:17:04.060000 --> 0:17:09.160000
 And what we'll do in the next section
 is we will get rid of the GRE header

0:17:09.160000 --> 0:17:13.040000
 and we'll start moving into
 other tunnel types.

