WEBVTT

0:00:08.300000 --> 0:00:11.800000
 Okay, next we're going to
 talk about isotap tunnels.

0:00:11.800000 --> 0:00:16.360000
 And these are very, very similar to 6
 to 4, but much easier to configure,

0:00:16.360000 --> 0:00:18.240000
 at least I think so.

0:00:18.240000 --> 0:00:20.740000
 We'll be sticking to
 static routing again.

0:00:20.740000 --> 0:00:25.760000
 No sense in changing that up, although
 this is a little easier to get

0:00:25.760000 --> 0:00:28.500000
 your dynamic routing protocols
 to run over.

0:00:28.500000 --> 0:00:32.520000
 Also, very easy to get BGP
 to run over this one.

0:00:32.520000 --> 0:00:35.000000
 But, again, what is
 stick with static?

0:00:35.000000 --> 0:00:41.240000
 I have taken out the tunnels that we
 created earlier, but I did leave

0:00:41.240000 --> 0:00:46.500000
 in the EIGRP readers distribution
 of static routes.

0:00:46.500000 --> 0:00:53.040000
 So all we have to do is actually build
 a tunnel here, which is really

0:00:53.040000 --> 0:01:01.440000
 easy to do. We have the various
 networks through here.

0:01:01.440000 --> 0:01:04.080000
 So let's switch over
 to the command line.

0:01:04.080000 --> 0:01:08.420000
 We're on router one, and we
 say interface tunnel zero.

0:01:08.420000 --> 0:01:10.220000
 And here's the glory of this.

0:01:10.220000 --> 0:01:17.480000
 So tunnel source is, of course, F A
 00 dot 12, just like it was before.

0:01:17.480000 --> 0:01:27.280000
 Okay? Tunnel mode is IPv6,
 IP isotap this time.

0:01:27.280000 --> 0:01:36.460000
 And then we say IPv6 address, and
 here's the part that's so nice.

0:01:36.460000 --> 0:01:45.320000
 IPv6 address, just make it a subnet
 on your regular network.

0:01:45.320000 --> 0:01:47.560000
 Something like that.

0:01:47.560000 --> 0:01:55.620000
 Whoops. You don't put the
 host portion, though.

0:01:55.620000 --> 0:01:58.320000
 Because then you say EY64.

0:01:58.320000 --> 0:02:03.000000
 Now, what this is going to do for you,
 and this is the really nice part,

0:02:03.000000 --> 0:02:07.740000
 do show IPv6 interface
 tunnel zero.

0:02:07.740000 --> 0:02:21.200000
 This goes out and does that
 translation for you.

0:02:21.200000 --> 0:02:29.340000
 Okay? Now, a couple things that it does,
 and I set about running the dynamic

0:02:29.340000 --> 0:02:32.240000
 routing protocols over this.

0:02:32.240000 --> 0:02:34.400000
 This is what you would use.

0:02:34.400000 --> 0:02:36.520000
 You would just have to
 do neighbor statements.

0:02:36.520000 --> 0:02:38.180000
 That's what it comes down to.

0:02:38.180000 --> 0:02:41.780000
 And you put in that link local address
 for the neighbor statement, for

0:02:41.780000 --> 0:02:44.200000
 the other side. Okay?

0:02:44.200000 --> 0:02:47.260000
 So that's really no
 big deal there.

0:02:47.260000 --> 0:02:52.400000
 And then for your global address,
 it does the same thing.

0:02:52.400000 --> 0:03:01.660000
 So it puts in this 5EFE, which is a well
-known prefix for isotap tunnels.

0:03:01.660000 --> 0:03:09.440000
 And then once again, your IPv4 address
 translated to the other side.

0:03:09.440000 --> 0:03:12.820000
 Okay? So this is from your underlying
 source interface.

0:03:12.820000 --> 0:03:14.200000
 Now we're going to need this.

0:03:14.200000 --> 0:03:17.220000
 We are going to need this.

0:03:17.220000 --> 0:03:20.000000
 And we can do it for the
 main address as well.

0:03:20.000000 --> 0:03:21.760000
 We can just take this one.

0:03:21.760000 --> 0:03:26.080000
 And my highlighting just messed
 up a little bit there.

0:03:26.080000 --> 0:03:27.920000
 Let's try that again.

0:03:27.920000 --> 0:03:30.760000
 We can copy that because we'll
 need it on router 4.

0:03:30.760000 --> 0:03:37.380000
 As we go over to router 4 and we say
 interface tunnel zero, IPv6 address,

0:03:37.380000 --> 0:03:46.400000
 2001 DB8 colon 100, colon 200
 colon colon slash 64, EY64.

0:03:46.400000 --> 0:03:47.860000
 And by the way, this is
 what is interesting.

0:03:47.860000 --> 0:03:53.680000
 If I said do show IPv6 interface brief
 right now, it would have actually

0:03:53.680000 --> 0:04:00.780000
 pulled that address from the MAC address
 of the numerically lowest ethernet

0:04:00.780000 --> 0:04:06.780000
 interface. Just like we talked
 about EY64 addressing before.

0:04:06.780000 --> 0:04:16.500000
 But as soon as I say tunnel mode, IPv6
 IP isotap, that behavior is going

0:04:16.500000 --> 0:04:21.440000
 to change. And it's going to give it
 an address like we were just talking

0:04:21.440000 --> 0:04:27.240000
 about. Oh wait, I didn't give
 it a tunnel source yet.

0:04:27.240000 --> 0:04:30.240000
 Tunnel source, F A00 dot.

0:04:30.240000 --> 0:04:34.060000
 And that's going to be 34.

0:04:34.060000 --> 0:04:37.080000
 There you go. That's that
 tunnel source first.

0:04:37.080000 --> 0:04:42.460000
 There we go. And it went ahead and
 already translated that for you.

0:04:42.460000 --> 0:04:48.760000
 But we're not quite done because
 we still need an IPv6 route.

0:04:48.760000 --> 0:04:52.620000
 Or to run our dynamic
 routing protocol.

0:04:52.620000 --> 0:04:56.340000
 Okay. But let's do this first.

0:04:56.340000 --> 0:05:01.360000
 So IPv6 route 2001, DB8.

0:05:01.360000 --> 0:05:05.660000
 I don't know what that was.

0:05:05.660000 --> 0:05:09.040000
 DB8 colon 100 colon.

0:05:09.040000 --> 0:05:10.180000
 And we're on force.

0:05:10.180000 --> 0:05:13.800000
 We're going to go to seven
 colon colon slash 64.

0:05:13.800000 --> 0:05:16.320000
 Out tunnel zero.

0:05:16.320000 --> 0:05:18.260000
 With the next top.

0:05:18.260000 --> 0:05:28.280000
 And hopefully I still have
 this from the other side.

0:05:28.280000 --> 0:05:32.360000
 Nope. I highlighted
 something else.

0:05:32.360000 --> 0:05:44.260000
 Actually I might have been it.

0:05:44.260000 --> 0:05:45.400000
 I think I just looked at it wrong.


0:05:45.400000 --> 0:05:49.340000
 That's right. There.

0:05:49.340000 --> 0:05:58.980000
 We're going to of course need his
 address for the other side.

0:05:58.980000 --> 0:06:02.780000
 And on router one.

0:06:02.780000 --> 0:06:26.700000
 There we go. The six
 to four tunnel.

0:06:26.700000 --> 0:06:34.180000
 The difference is it did the IPv4
 decimal to hex conversion for me.

0:06:34.180000 --> 0:06:38.300000
 And it puts it in
 the host portion.

0:06:38.300000 --> 0:06:42.000000
 Which means we should be able to get
 away with, you know, like I said

0:06:42.000000 --> 0:06:46.380000
 before, running a dynamic routing
 protocol over here and so on.

0:06:46.380000 --> 0:06:48.900000
 So we can take a look at that
 here in just a minute.

0:06:48.900000 --> 0:07:00.100000
 But let's make sure this
 is working first.

0:07:00.100000 --> 0:07:01.600000
 And there you go.

0:07:01.600000 --> 0:07:03.280000
 Right through the middle.

0:07:03.280000 --> 0:07:10.740000
 But again you can see the network
 portion is the same on these guys.

0:07:10.740000 --> 0:07:23.860000
 All right. So let's try and do this
 with a dynamic routing protocol.

0:07:23.860000 --> 0:07:25.680000
 I'm already running EIGRP.

0:07:25.680000 --> 0:07:27.220000
 So let's see if we can
 get this to work.

0:07:27.220000 --> 0:07:29.280000
 I haven't done it with
 the EIGRP for a while.

0:07:29.280000 --> 0:07:33.100000
 But let's take out
 our static route.

0:07:33.100000 --> 0:07:37.540000
 And say router. EIGRP.

0:07:37.540000 --> 0:08:18.560000
 EIGRP. Out. And it should
 ask for the interface.

0:08:18.560000 --> 0:08:26.280000
 Tunnel zero. Router four.

0:08:26.280000 --> 0:08:37.740000
 Take the static route out.

0:08:37.740000 --> 0:08:42.000000
 And this is going to be of course
 router one's address.

0:08:42.000000 --> 0:08:53.160000
 Out. Tunnel zero.

0:08:53.160000 --> 0:09:19.940000
 Let's try this. Okay.

0:09:19.940000 --> 0:09:21.540000
 So it's working.

0:09:21.540000 --> 0:09:30.240000
 You can ping the link local.

0:09:30.240000 --> 0:09:33.560000
 EIGRP doesn't seem happy though.

0:09:33.560000 --> 0:09:56.840000
 Oops. Oh, I don't have EIGRP
 enabled on that interface.

0:09:56.840000 --> 0:09:58.600000
 That would probably help.

0:09:58.600000 --> 0:10:00.740000
 Interface tunnel zero.

0:10:00.740000 --> 0:10:06.220000
 IPV six. EIGRP 100.

0:10:06.220000 --> 0:10:08.900000
 Forgot we deleted the tunnel and brought
 it back in a couple of times

0:10:08.900000 --> 0:10:18.720000
 there. There we go.

0:10:18.720000 --> 0:10:25.660000
 Much better. See, so, you know, an
 OSPF would be similar and so on.

0:10:25.660000 --> 0:10:29.360000
 The thing is you have to do the
 neighbor statements though.

0:10:29.360000 --> 0:10:31.820000
 You're not going to dynamically
 learn the neighbors.

0:10:31.820000 --> 0:10:35.260000
 Because, I mean, if you think about
 it from the router's perspective,

0:10:35.260000 --> 0:10:38.340000
 do show run interface tunnel zero.


0:10:38.340000 --> 0:10:44.860000
 Again, the big piece missing
 is the destination.

0:10:44.860000 --> 0:10:50.320000
 So what he's getting out of this neighbor
 statement is the IPV four destination

0:10:50.320000 --> 0:10:57.860000
 of who to build the tunnel to so that
 he can bring up EIGRP, BGP, whatever.

0:10:57.860000 --> 0:11:01.640000
 The problem that comes in, you know,
 you can't have dynamic neighbors

0:11:01.640000 --> 0:11:04.480000
 here because you look at it and go,
 so what I'm supposed to build to the

0:11:04.480000 --> 0:11:09.440000
 destination of the entire planet, the
 entire IPV four address space, I'll

0:11:09.440000 --> 0:11:11.200000
 just build a tunnel to everybody.

0:11:11.200000 --> 0:11:14.580000
 He has no idea who to
 build the tunnel to.

0:11:14.580000 --> 0:11:20.480000
 So, dynamic routing or not, you're
 still going to need manual neighbor

0:11:20.480000 --> 0:11:27.180000
 statements with any of these IPV six
 tunnel solutions that we've gone

0:11:27.180000 --> 0:11:33.820000
 over so far. Now, of course, GRE point
 to point and IPV six IP, no.

0:11:33.820000 --> 0:11:38.680000
 But six to four and ISA TAP, your dynamic
 multi-point tunnels, you're

0:11:38.680000 --> 0:11:42.300000
 going to need that because it doesn't
 have any idea who to actually build

0:11:42.300000 --> 0:11:43.060000
 the neighbors to.

