WEBVTT

0:00:08.320000 --> 0:00:13.520000
 In the previous video, I introduced
 you to the concept of IPv6 and why

0:00:13.520000 --> 0:00:17.300000
 it was created in the first place,
 and we did a brief look at an IPv6

0:00:17.300000 --> 0:00:22.900000
 address. And we saw that it was really
 big, it was 128 bits in binary,

0:00:22.900000 --> 0:00:26.460000
 and we saw that instead of representing
 that in dotted decimal notation

0:00:26.460000 --> 0:00:31.320000
 like we do with an IP version 4 address,
 IP version 6 addresses are represented

0:00:31.320000 --> 0:00:36.380000
 in hexadecimal, that every 4 bits in
 binary are represented by a single

0:00:36.380000 --> 0:00:41.920000
 hexadecimal character that could be
 anything from 0 to f with 0 meaning

0:00:41.920000 --> 0:00:44.540000
 0 and f meaning 15.

0:00:44.540000 --> 0:00:48.920000
 And then after 4 hexadecimal
 characters, we had the colon.

0:00:48.920000 --> 0:00:53.120000
 And those 4 hexadecimal characters
 together were called a word.

0:00:53.120000 --> 0:00:57.440000
 16 bits is called a word, so for
 every word, there was a colon.

0:00:57.440000 --> 0:01:02.740000
 So now what we're going to look at is
 normally in discussing IP addresses,

0:01:02.740000 --> 0:01:06.600000
 I would focus on the network portion
 first because that's what we did

0:01:06.600000 --> 0:01:10.560000
 with IP version 4, and we talked
 all about the network portion.

0:01:10.560000 --> 0:01:15.220000
 But in order to really talk about the
 network portion of an IPv6 address,

0:01:15.220000 --> 0:01:19.580000
 first, we actually have to understand
 the second half of the address,

0:01:19.580000 --> 0:01:21.540000
 the host portion.

0:01:21.540000 --> 0:01:25.380000
 Because the host portion, you come up
 with that in a slightly different

0:01:25.380000 --> 0:01:29.620000
 way than we do in IP version 4, and
 I'm going to be using a term called

0:01:29.620000 --> 0:01:37.640000
 EUI64. EUI64 is one of the ways that
 the host portion of an IPv6 address

0:01:37.640000 --> 0:01:42.220000
 is created. And I'm going to be referencing
 that term a lot when I'm talking

0:01:42.220000 --> 0:01:47.140000
 about various different kinds of IPv6
 addresses, and if you didn't know

0:01:47.140000 --> 0:01:51.340000
 what EUI64 meant, that would be
 kind of meaningless to you.

0:01:51.340000 --> 0:01:54.760000
 So let's talk about
 the host portion.

0:01:54.760000 --> 0:02:03.120000
 So in the world of routed protocols,
 a routed protocol by definition has

0:02:03.120000 --> 0:02:09.040000
 to provide some sort of layer 3 address
 to what is being encapsulated.

0:02:09.040000 --> 0:02:12.980000
 And we know that a routed protocol,
 whatever that address is, however

0:02:12.980000 --> 0:02:17.140000
 big or small it is, it has to be
 subdividable into two pieces.

0:02:17.140000 --> 0:02:21.940000
 Part of the address has to be the network,
 or sometimes we call the prefix.

0:02:21.940000 --> 0:02:26.060000
 The other half of the address is the
 host ID, or sort of like the serial

0:02:26.060000 --> 0:02:29.320000
 number of the individual
 host in that network.

0:02:29.320000 --> 0:02:32.620000
 So it has to be subdividable
 into two pieces.

0:02:32.620000 --> 0:02:36.220000
 So we mentioned, we talked about IP
 version 4, and we looked at how the

0:02:36.220000 --> 0:02:42.700000
 subnet mask was the tool, the comparison
 tool that we use against the

0:02:42.700000 --> 0:02:46.780000
 IP version 4 address, to determine where
 that dividing line was between

0:02:46.780000 --> 0:02:50.000000
 the network portion and
 the host portion.

0:02:50.000000 --> 0:02:54.060000
 So in an IP version 6 address, same
 rules apply, even though the address

0:02:54.060000 --> 0:02:58.960000
 is much bigger, we need a subnet mask,
 and the subnet mask tells us where

0:02:58.960000 --> 0:03:03.200000
 within those 128 bits the
 dividing line needs to be.

0:03:03.200000 --> 0:03:09.300000
 Now in IP version 6, the second portion
 of the address that is unique

0:03:09.300000 --> 0:03:15.060000
 just to your laptop, technically those
 bits, we don't call them host bits.

0:03:15.060000 --> 0:03:19.220000
 We have a different name for them,
 they're called the interface ID.

0:03:19.220000 --> 0:03:23.640000
 It means basically the same thing,
 your interface ID, your host bits,

0:03:23.640000 --> 0:03:28.000000
 same thing. It's a unique set of bits
 just for you on this particular

0:03:28.000000 --> 0:03:30.480000
 network that you're sitting
 on right now.

0:03:30.480000 --> 0:03:32.900000
 But you should be familiar with the fact
 that we no longer call them host

0:03:32.900000 --> 0:03:35.700000
 bits, they're called
 an interface ID.

0:03:35.700000 --> 0:03:39.960000
 Now, according to the internet assigned
 numbers authority, and remember

0:03:39.960000 --> 0:03:44.180000
 them, they're at the top of the food
 chain as far as governing all numbers

0:03:44.180000 --> 0:03:49.080000
 related to the internet, they really
 strongly advise that IPv6 addresses

0:03:49.080000 --> 0:03:53.760000
 be split evenly right down the middle,
 that the first 64 bits be for the

0:03:53.760000 --> 0:03:58.960000
 prefix or the network, and the second
 64 bits be for the interface ID.

0:03:58.960000 --> 0:04:02.720000
 Now it's a recommendation,
 you don't have to do that.

0:04:02.720000 --> 0:04:06.960000
 Just like in the world of IP version
 4, if I gave you a 32 bit IP version

0:04:06.960000 --> 0:04:11.180000
 4 address, you could create whatever
 subnet mask you wanted to to put

0:04:11.180000 --> 0:04:13.180000
 that dividing line wherever
 you wanted to.

0:04:13.180000 --> 0:04:17.780000
 You could say that the first 19 bits
 are the network or the first 26 bits

0:04:17.780000 --> 0:04:19.660000
 or the first 12 bits.

0:04:19.660000 --> 0:04:21.860000
 Same thing is true
 with IP version 6.

0:04:21.860000 --> 0:04:25.900000
 Anywhere within those 128 bits, you
 could set that dividing line.

0:04:25.900000 --> 0:04:30.200000
 But the problem is, if you don't go
 with the recommendation of cutting

0:04:30.200000 --> 0:04:34.880000
 your right down the middle, then some
 of the other benefits that you have

0:04:34.880000 --> 0:04:37.140000
 of IPv6 are lost.

0:04:37.140000 --> 0:04:40.860000
 Some of the other benefits that come
 with IPv6 you cannot take advantage

0:04:40.860000 --> 0:04:44.880000
 of if you don't split your address
 right down the middle.

0:04:44.880000 --> 0:04:48.440000
 So that's why it's just really a good
 idea to do what the internet assigned

0:04:48.440000 --> 0:04:51.240000
 numbers authority recommends
 that you do.

0:04:51.240000 --> 0:04:56.320000
 Okay, so the nice thing here, one thing
 that's kind of easy, okay yeah,

0:04:56.320000 --> 0:05:00.240000
 it's kind of disappointing that when
 we're representing the IPv6 address

0:05:00.240000 --> 0:05:04.160000
 itself, it's so big, and we have to remember
 all these hexadecimal characters

0:05:04.160000 --> 0:05:05.440000
 and where the colons go.

0:05:05.440000 --> 0:05:10.700000
 So yes, an IPv6 address typing it into
 the keyboard is a lot more cumbersome

0:05:10.700000 --> 0:05:13.760000
 than typing in an IP
 version 4 address.

0:05:13.760000 --> 0:05:15.720000
 But there is a trade-off.

0:05:15.720000 --> 0:05:19.080000
 When you're typing in your IP version
 4 address, when you get to the subnet

0:05:19.080000 --> 0:05:23.940000
 mask, you had to type in the subnet mask
 as another dotted decimal number

0:05:23.940000 --> 0:05:28.760000
 255.255.255.whatever, 248.

0:05:28.760000 --> 0:05:32.500000
 In IP version 6, as you can see here
 on the slide, you can actually type

0:05:32.500000 --> 0:05:33.340000
 in the subnet mask.

0:05:33.340000 --> 0:05:35.060000
 Actually, you don't have a choice.


0:05:35.060000 --> 0:05:39.460000
 You type in the subnet mask as the shorthand
 notation, as a forward slash

0:05:39.460000 --> 0:05:44.120000
 and a number, like forward slash 64
 is what you would commonly see.

0:05:44.120000 --> 0:05:48.780000
 So like this number here that we see
 in black 2001 and then ending with

0:05:48.780000 --> 0:05:53.800000
 colon colon 3a forward slash 64, that
 is exactly how you would type an

0:05:53.800000 --> 0:05:58.340000
 IPv6 address into your router's
 interface, for example.

0:05:58.340000 --> 0:06:01.120000
 So when we get to actually configuring
 routers and switches and putting

0:06:01.120000 --> 0:06:07.160000
 addresses on them, we'll use the IP
 address command to put in IP version

0:06:07.160000 --> 0:06:14.100000
 4 address, and we'll use the IPv6 address
 command to put in IPv6 address.

0:06:14.100000 --> 0:06:17.900000
 And with the v6, we will not have to
 use dotted decimal for the subnet

0:06:17.900000 --> 0:06:19.920000
 mask. So that will
 be kind of nice.

0:06:19.920000 --> 0:06:22.940000
 Now let's do some comparing
 and contrasting here.

0:06:22.940000 --> 0:06:27.460000
 With IP version 4, which is what you're
 most familiar with right now,

0:06:27.460000 --> 0:06:31.760000
 how does a device, let's just think
 about a laptop for a moment, how can

0:06:31.760000 --> 0:06:36.080000
 a laptop obtain an IP
 version 4 address?

0:06:36.080000 --> 0:06:37.760000
 How does it get on your system?

0:06:37.760000 --> 0:06:39.560000
 What are the various ways?

0:06:39.560000 --> 0:06:44.120000
 Well, hopefully you said if you're talking
 about Microsoft Windows, specifically,

0:06:44.120000 --> 0:06:46.160000
 there are three ways, right?

0:06:46.160000 --> 0:06:51.020000
 You could get it via DHCP, and that's
 the way the vast majority of hosts

0:06:51.020000 --> 0:06:54.700000
 obtain their IP addresses via the dynamic
 host configuration protocol

0:06:54.700000 --> 0:06:59.680000
 on by default. Or if we're talking
 about a host that never moves like

0:06:59.680000 --> 0:07:03.620000
 a server that's always in one position,
 we could statically configure

0:07:03.620000 --> 0:07:07.520000
 it on that device so it always
 has the exact same IP address.

0:07:07.520000 --> 0:07:11.740000
 Or if we're talking about Microsoft
 Windows, we know that if Windows is

0:07:11.740000 --> 0:07:17.180000
 configured to try DHCP, and then DHCP
 fails, it will fall back to that

0:07:17.180000 --> 0:07:22.620000
 169.254 address, that automatically
 provisioned IP address.

0:07:22.620000 --> 0:07:23.700000
 So those are the three ways.

0:07:23.700000 --> 0:07:27.420000
 And that last one, we don't
 really like to see, right?

0:07:27.420000 --> 0:07:30.520000
 When we're on a Windows device and
 we see the IP address is 169, it's

0:07:30.520000 --> 0:07:34.900000
 like, uh-oh, that's not a good
 thing, it should not be that.

0:07:34.900000 --> 0:07:40.040000
 Well, in the world of IP version 6,
 you have the first two methods are

0:07:40.040000 --> 0:07:41.100000
 exactly the same.

0:07:41.100000 --> 0:07:47.760000
 There is a DHCP version of IP, it's called
 DHCP V6, so you could certainly

0:07:47.760000 --> 0:07:52.780000
 use that. You can still statically
 configure your IPV6 address on your

0:07:52.780000 --> 0:07:55.420000
 laptop or on your router.

0:07:55.420000 --> 0:08:01.480000
 Or IPV6 actually has a totally unique
 way that IP version 4 doesn't have,

0:08:01.480000 --> 0:08:08.900000
 which is called stateless address, address,
 automatic configuration, SLAC,

0:08:08.900000 --> 0:08:14.440000
 SLAC, stateless address,
 automatic configuration.

0:08:14.440000 --> 0:08:20.780000
 And by using SLAC, an interface, a
 net card, can automatically obtain

0:08:20.780000 --> 0:08:26.880000
 a globally routable prefix, a prefix
 that actually could use to get to

0:08:26.880000 --> 0:08:30.620000
 and from the internet
 without using DHCP.

0:08:30.620000 --> 0:08:34.760000
 And towards the end of my IPV6 discussion
 videos, we'll talk a little

0:08:34.760000 --> 0:08:39.240000
 bit about that. When we talk about something
 called IPV6 neighbor discovery,

0:08:39.240000 --> 0:08:43.380000
 that is how stateless address,
 automatic configuration works.

0:08:43.380000 --> 0:08:47.100000
 But that's something that's kind of unique
 to IPV6, where it doesn't need

0:08:47.100000 --> 0:08:52.260000
 technically DHCP to get a
 useful address for itself.

0:08:52.260000 --> 0:08:57.800000
 Now, I want to focus in here in this
 presentation on the interface ID.

0:08:57.800000 --> 0:09:03.260000
 So let me bring up the whiteboard
 here and zoom in on this.

0:09:03.260000 --> 0:09:10.980000
 So let's say that I was on a router
 and I am at, I mentioned this mode

0:09:10.980000 --> 0:09:14.840000
 briefly. Do you remember what I called
 this mode in some previous videos?

0:09:14.840000 --> 0:09:17.780000
 This was called user exec mode.

0:09:17.780000 --> 0:09:20.720000
 And I said, really can't
 do much from this level.

0:09:20.720000 --> 0:09:24.860000
 So I said, we want to move up to the
 next level, which, what does the

0:09:24.860000 --> 0:09:27.300000
 prompt look like?

0:09:27.300000 --> 0:09:31.380000
 What symbol does it take
 at the next higher level?

0:09:31.380000 --> 0:09:33.520000
 It's a pound sign.

0:09:33.520000 --> 0:09:38.400000
 And what did we technically call
 this configuration mode or level?

0:09:38.400000 --> 0:09:41.720000
 This was called privileged exec.

0:09:41.720000 --> 0:09:43.080000
 Privileged exec.

0:09:43.080000 --> 0:09:48.920000
 Now, what actual iOS command did I have
 to type in when iOS at user exec

0:09:48.920000 --> 0:09:53.160000
 level to get me to
 privileged exec?

0:09:53.160000 --> 0:09:56.460000
 That was the single
 word of enable.

0:09:56.460000 --> 0:10:00.720000
 And that's why privileged exec is
 sometimes called enabled mode.

0:10:00.720000 --> 0:10:04.440000
 You'll hear that a lot, but technically
 it's called privileged exec.

0:10:04.440000 --> 0:10:09.180000
 Okay. Now from privileged exec mode,
 can I start configuring this device?

0:10:09.180000 --> 0:10:12.520000
 Can I start adding IP addresses and turning
 on routing protocols and doing

0:10:12.520000 --> 0:10:16.420000
 all of that? No, I can't.

0:10:16.420000 --> 0:10:18.960000
 So now I need to get
 to another mode.

0:10:18.960000 --> 0:10:22.220000
 What is the next mode called?

0:10:22.220000 --> 0:10:25.980000
 They will actually be the very first
 mode that allows me to do any kind

0:10:25.980000 --> 0:10:27.400000
 of configuration.

0:10:27.400000 --> 0:10:32.800000
 That mode is called global
 configuration mode.

0:10:32.800000 --> 0:10:36.900000
 And what would the prompt look like to tell
 me that I'm in global configuration

0:10:36.900000 --> 0:10:45.140000
 mode? I would see in parentheses the
 word config and then the hash symbol.

0:10:45.140000 --> 0:10:51.300000
 And review question, how do I get from privileged
 exec into global configuration

0:10:51.300000 --> 0:10:58.200000
 mode? I have to type two words,
 configure terminal.

0:10:58.200000 --> 0:11:01.320000
 Most people usually shorten
 that to config T.

0:11:01.320000 --> 0:11:06.900000
 Cisco iOS does recognize that config
 T means configure terminal.

0:11:06.900000 --> 0:11:14.120000
 Okay. So right now let's say that I
 have a router that looks like this.

0:11:14.120000 --> 0:11:17.840000
 It's got two interfaces on it.

0:11:17.840000 --> 0:11:23.140000
 And the interface where I want to apply
 my IP version 6 and my IP version

0:11:23.140000 --> 0:11:26.000000
 4 address, I'm going to make
 this a dual stack device.

0:11:26.000000 --> 0:11:28.400000
 It's going to run both v4 and v6.

0:11:28.400000 --> 0:11:31.180000
 It's fast ethernet 00.

0:11:31.180000 --> 0:11:36.600000
 From right where I am right here, can
 I start configuring my IPv4 and

0:11:36.600000 --> 0:11:38.920000
 my IPv6 addresses?

0:11:38.920000 --> 0:11:42.740000
 No, I cannot. The router
 can't guess my mind.

0:11:42.740000 --> 0:11:46.520000
 It doesn't know which interface
 that any address would go on.

0:11:46.520000 --> 0:11:47.860000
 So I have to tell it.

0:11:47.860000 --> 0:11:51.900000
 So in this particular case, from global
 configuration mode, I would say,

0:11:51.900000 --> 0:11:58.440000
 okay, the interface I want to go
 to is fast ethernet 0 slash 0.

0:11:58.440000 --> 0:12:04.340000
 And now that will put me into yet another
 sub mode called config interface

0:12:04.340000 --> 0:12:10.560000
 mode. So now anything I type a relevant
 command it, it recognizes there's

0:12:10.560000 --> 0:12:12.940000
 some commands that are appropriate
 for putting on this interface.

0:12:12.940000 --> 0:12:16.540000
 And there are some commands
 that are not appropriate.

0:12:16.540000 --> 0:12:21.840000
 If I tried typing in a command here,
 for example, to change the name of

0:12:21.840000 --> 0:12:24.840000
 the router, let's say I said, oh, I
 don't want it to be called router.

0:12:24.840000 --> 0:12:27.440000
 I want to be called
 Keith's router.

0:12:27.440000 --> 0:12:31.420000
 Well, if I tried typing in the command
 to do that right here, it would

0:12:31.420000 --> 0:12:34.680000
 recognize that that command was
 not at the appropriate level.

0:12:34.680000 --> 0:12:38.060000
 And it would either get me an error
 message or it would bounce me back

0:12:38.060000 --> 0:12:39.620000
 to the level where
 I'm supposed to be.

0:12:39.620000 --> 0:12:44.180000
 But right now, I want to type
 in an IP version 4 address.

0:12:44.180000 --> 0:12:47.440000
 So let's say I want to give this thing
 the IP version 4 address of 20

0:12:47.440000 --> 0:12:51.680000
.1.1.1 with a slash 24 mask.

0:12:51.680000 --> 0:12:54.920000
 Do you remember what the
 command was to do that?

0:12:54.920000 --> 0:13:04.620000
 That command was IP address, which
 means it's an IP version 4 address,

0:13:04.620000 --> 0:13:10.800000
 20.1.1.1. And then we have to put in
 our subnet mask in dotted decimal.

0:13:10.800000 --> 0:13:16.020000
 Okay. And then as soon as I hit the
 enter key, that will take effect.

0:13:16.020000 --> 0:13:21.280000
 And it will put me right back in
 interface configuration mode.

0:13:21.280000 --> 0:13:22.320000
 I haven't left it yet.

0:13:22.320000 --> 0:13:24.500000
 It assumes I still
 want to be there.

0:13:24.500000 --> 0:13:28.960000
 Now, let's say I'm going to use an
 arrow here because an IPv6 address

0:13:28.960000 --> 0:13:36.000000
 is quite large. Let's say that on that
 same interface, I want to apply

0:13:36.000000 --> 0:13:42.700000
 an IPv6 address that is this.

0:13:42.700000 --> 0:13:47.600000
 Let's say it's 2.001
 colon 1.1.1.1.

0:13:47.600000 --> 0:13:51.800000
 colon 0 colon a a a a.

0:13:51.800000 --> 0:13:56.180000
 Okay. So right there, if we add that up,
 that's the first half of my address.

0:13:56.180000 --> 0:13:56.840000
 That's my network.

0:13:56.840000 --> 0:13:58.580000
 Because remember, this is a word.

0:13:58.580000 --> 0:14:01.960000
 2001 is a word and
 a word is 16 bits.

0:14:01.960000 --> 0:14:08.020000
 So 16 plus 16 plus 16
 plus 16 gives me 64.

0:14:08.020000 --> 0:14:09.600000
 So there's my prefix.

0:14:09.600000 --> 0:14:11.320000
 I'll put a colon there.

0:14:11.320000 --> 0:14:17.080000
 Now, the rest of this address is
 going to be my interface ID.

0:14:17.080000 --> 0:14:24.540000
 And then at the end of it, I'm going
 to put slash 64 to indicate that

0:14:24.540000 --> 0:14:27.340000
 this portion is the network.

0:14:27.340000 --> 0:14:31.800000
 Now, as far as the interface ID is concerned,
 on the router, I have two

0:14:31.800000 --> 0:14:35.040000
 choices. I could statically
 configure it.

0:14:35.040000 --> 0:14:36.860000
 Maybe I want to be like this.

0:14:36.860000 --> 0:14:43.980000
 Maybe I want the interface
 ID to be 2222 1111 0 a.

0:14:43.980000 --> 0:14:57.880000
 Well, then I would simply type IPV6
 address 2001 1111 0 a a a colon.

0:14:57.880000 --> 0:15:12.100000
 And then I would put 222 colon
 111 colon 0 colon a slash 64.

0:15:12.100000 --> 0:15:18.500000
 So by manually typing in this portion,
 I've just statically provided the

0:15:18.500000 --> 0:15:22.960000
 last 64 bits. I've told it what
 its interface ID should be.

0:15:22.960000 --> 0:15:26.980000
 Just like when I gave the IP version
 4 address, part of this was the host

0:15:26.980000 --> 0:15:29.860000
 bits. I told it what
 the host bits were.

0:15:29.860000 --> 0:15:32.880000
 But with IPV6, there
 is an alternative.

0:15:32.880000 --> 0:15:38.180000
 Now, usually when you're talking about
 devices that have static IP addresses,

0:15:38.180000 --> 0:15:43.060000
 like routers interfaces, like servers,
 you would want to do this.

0:15:43.060000 --> 0:15:46.440000
 You would want to give it a static
 interface ID and probably something

0:15:46.440000 --> 0:15:48.160000
 that's easy to remember.

0:15:48.160000 --> 0:15:53.180000
 Like 0 0 0 0 1 or 0 0 2
 or something like that.

0:15:53.180000 --> 0:15:56.960000
 This one here is not all
 that easy to remember.

0:15:56.960000 --> 0:16:04.460000
 But on laptops and tablets and smartphones
 that are running IPV6, typically

0:16:04.460000 --> 0:16:08.880000
 they get all of their address
 information dynamically.

0:16:08.880000 --> 0:16:13.120000
 And so they will obtain their prefix,
 their network dynamically.

0:16:13.120000 --> 0:16:18.180000
 And then they will buy themselves come
 up with their interface ID without

0:16:18.180000 --> 0:16:19.860000
 any help from anybody else.

0:16:19.860000 --> 0:16:26.020000
 Now, if I wanted the router to do that
 same thing, I could type this.

0:16:26.020000 --> 0:16:34.140000
 IPV6 address 2001, 1111 0 AAAA.

0:16:34.140000 --> 0:16:38.760000
 And then I would say
 colon colon slash 64.

0:16:38.760000 --> 0:16:40.920000
 So now remember, what's
 the colon colon mean?

0:16:40.920000 --> 0:16:44.020000
 That means this covers
 a whole bunch of zeros.

0:16:44.020000 --> 0:16:48.380000
 So right now I've given him his first
 64 bits and the colon colon is saying

0:16:48.380000 --> 0:16:52.180000
 the last 64 bits are zeros.

0:16:52.180000 --> 0:16:55.340000
 But I'm going to add one additional
 element here to tell him, well, wait

0:16:55.340000 --> 0:16:58.940000
 a second. I don't want your interface
 ID to be all zeros.

0:16:58.940000 --> 0:17:06.380000
 I want you to make it up yourself
 using the EUI-64 protocol.

0:17:06.380000 --> 0:17:10.580000
 So at the end of the IP address, when
 you do not supply the interface

0:17:10.580000 --> 0:17:14.420000
 ID, you just do a colon
 colon slash 64.

0:17:14.420000 --> 0:17:17.540000
 And then you do EUI-64 as
 an additional keyword.

0:17:17.540000 --> 0:17:20.440000
 I didn't have to do that up here because
 I gave it the interface ID.

0:17:20.440000 --> 0:17:25.280000
 But down here, that says use these
 special rules, the special protocol

0:17:25.280000 --> 0:17:29.600000
 to come up with an interface
 ID yourself.

0:17:29.600000 --> 0:17:32.040000
 Now you might be wondering,
 well, how does he do that?

0:17:32.040000 --> 0:17:35.880000
 And actually we do need to talk about
 that because your CCNA exams will

0:17:35.880000 --> 0:17:41.240000
 expect you to know how an EUI
-64 interface ID is determined.

0:17:41.240000 --> 0:17:43.360000
 So let's take a look at that.

0:17:43.360000 --> 0:17:47.540000
 Now, as of the time of I'm doing this
 recording right here, we haven't

0:17:47.540000 --> 0:17:49.680000
 really talked about Ethernet.

0:17:49.680000 --> 0:17:54.500000
 I've mentioned it here and there as
 a Layer 2 data link layer protocol.

0:17:54.500000 --> 0:17:55.920000
 That's the most common.

0:17:55.920000 --> 0:17:59.660000
 I've said that if you have a wired net
 card that actually has a wire coming

0:17:59.660000 --> 0:18:05.440000
 out of it, 99.9% of the time it's
 going to be running Ethernet.

0:18:05.440000 --> 0:18:10.400000
 And I mentioned that all Layer 2 protocols
 have to have some kind of a

0:18:10.400000 --> 0:18:12.520000
 Layer 2 address.

0:18:12.520000 --> 0:18:16.520000
 You have to have some way of identifying
 yourself on this wire.

0:18:16.520000 --> 0:18:20.480000
 And in the case of Ethernet, not only
 does your net card have an identifier,

0:18:20.480000 --> 0:18:22.900000
 we remember we called that
 a burned in address.

0:18:22.900000 --> 0:18:24.460000
 Remember we talked about that?

0:18:24.460000 --> 0:18:27.940000
 Because it was burned in by the
 manufacturer when it was made.

0:18:27.940000 --> 0:18:31.740000
 Well, when I put an Ethernet frame
 on the wire, I also have to include

0:18:31.740000 --> 0:18:36.620000
 the destination address of who
 on this wire it's going to.

0:18:36.620000 --> 0:18:38.240000
 And this is a key thing.

0:18:38.240000 --> 0:18:42.080000
 When we're talking about Layer 3, the
 networking layer, I have a source

0:18:42.080000 --> 0:18:44.260000
 address, a source IP address.

0:18:44.260000 --> 0:18:50.120000
 My destination Layer 3 address may be
 somebody on my wire, but it's probably

0:18:50.120000 --> 0:18:54.300000
 not. It's probably somebody on a completely
 different network than me.

0:18:54.300000 --> 0:18:57.780000
 Could be somebody who's thousands
 of miles away from me.

0:18:57.780000 --> 0:19:03.680000
 So the source in the destination IP
 address usually are not on the same

0:19:03.680000 --> 0:19:05.280000
 subnet, on the same network.

0:19:05.280000 --> 0:19:06.800000
 Usually they're on different.

0:19:06.800000 --> 0:19:13.520000
 At Layer 2 though, at Layer 2, the source
 and destination Layer 2 addresses

0:19:13.520000 --> 0:19:16.920000
 have to be on the same wire.

0:19:16.920000 --> 0:19:18.700000
 They have to be on the same wire.

0:19:18.700000 --> 0:19:20.820000
 Now you might be thinking,
 well, wait a second, Keith.

0:19:20.820000 --> 0:19:26.280000
 If my laptop is trying to communicate
 to a server that's across the country,

0:19:26.280000 --> 0:19:30.460000
 I can understand how the Layer
 3 addresses would be different.

0:19:30.460000 --> 0:19:35.280000
 But how could I address my Layer 2
 frame to someone on my wire if I'm

0:19:35.280000 --> 0:19:37.560000
 not really trying to get
 to someone on my wire?

0:19:37.560000 --> 0:19:39.760000
 I'm trying to get to someone
 across the country.

0:19:39.760000 --> 0:19:43.440000
 This is where the router
 comes into play.

0:19:43.440000 --> 0:19:49.560000
 For example, if this was my PC right
 here, and let's say my PC had the

0:19:49.560000 --> 0:19:55.660000
 IP address of 1111 slash 24, and somewhere
 out there in the world, we

0:19:55.660000 --> 0:20:01.700000
 don't know where it is, is the I&E.com
 web server, and let's say it had

0:20:01.700000 --> 0:20:05.960000
 the address of 7777 slash 24.

0:20:05.960000 --> 0:20:09.960000
 Well, if I told my PC, that's
 where I need you to go.

0:20:09.960000 --> 0:20:14.280000
 The first thing any device does when
 it creates a packet, it says, OK,

0:20:14.280000 --> 0:20:15.860000
 I'm going to do a
 quick comparison.

0:20:15.860000 --> 0:20:21.660000
 I'm going to compare my address, my IP
 address, or my IPv6 address against

0:20:21.660000 --> 0:20:23.280000
 the destination address.

0:20:23.280000 --> 0:20:26.500000
 And I'm going to ask myself,
 are we in the same network?

0:20:26.500000 --> 0:20:28.080000
 Are we in the same subnet?

0:20:28.080000 --> 0:20:31.600000
 In this case, the answer
 is clearly no, we're not.

0:20:31.600000 --> 0:20:33.660000
 I'm trying to get to
 seven dot something.

0:20:33.660000 --> 0:20:35.100000
 I am one dot something.

0:20:35.100000 --> 0:20:37.140000
 We are not in the same subnet.

0:20:37.140000 --> 0:20:41.280000
 So now in this case, when the answer
 is no, the device I'm trying to reach

0:20:41.280000 --> 0:20:46.300000
 is not on my cable, it's not on my subnet,
 then the device says, OK, well,

0:20:46.300000 --> 0:20:48.080000
 how do I get my data there?

0:20:48.080000 --> 0:20:50.900000
 Oh, that's what my default
 gateway is for.

0:20:50.900000 --> 0:20:52.680000
 That's what my router is for.

0:20:52.680000 --> 0:20:54.260000
 So here's what I'll do.

0:20:54.260000 --> 0:21:00.700000
 When I create my packet, so here's my
 IP packet, I'll put a destination

0:21:00.700000 --> 0:21:03.060000
 of who I'm trying to reach.

0:21:03.060000 --> 0:21:07.100000
 I'll put a source of who I am.

0:21:07.100000 --> 0:21:11.480000
 And then when I hand that down to the
 data link layer at layer two, the

0:21:11.480000 --> 0:21:16.000000
 data link layer is going to put
 his own header on front of that.

0:21:16.000000 --> 0:21:23.880000
 Well, I have a NIC card that connects
 to this wire, and that NIC card

0:21:23.880000 --> 0:21:26.260000
 has a layer to address.

0:21:26.260000 --> 0:21:31.340000
 Now in the case of ethernet, which is
 what's used most oftenly, that address

0:21:31.340000 --> 0:21:37.200000
 is called a MAC address, media access
 control address, a MAC address.

0:21:37.200000 --> 0:21:42.720000
 And just like IPv6 addresses are represented
 in hexadecimal, MAC addresses

0:21:42.720000 --> 0:21:45.380000
 are represented in hexadecimal
 as well.

0:21:45.380000 --> 0:21:48.280000
 So it's a good thing we already know
 hexadecimal, because once we get

0:21:48.280000 --> 0:21:51.680000
 into the ethernet section, we talk
 about MAC addresses in more detail,

0:21:51.680000 --> 0:21:53.760000
 they'll make more sense.

0:21:53.760000 --> 0:21:55.840000
 So MAC address might
 look like this.

0:21:55.840000 --> 0:21:59.700000
 So that would be the MAC
 address of my NIC card.

0:21:59.700000 --> 0:22:05.000000
 So that was whoever made my NIC card
 Intel or whoever it is, stamped that

0:22:05.000000 --> 0:22:07.820000
 MAC address on it when
 they created it.

0:22:07.820000 --> 0:22:13.580000
 So anytime a layer two frame is going
 to me or coming from me, this MAC

0:22:13.580000 --> 0:22:15.200000
 address will be in it.

0:22:15.200000 --> 0:22:20.780000
 And similarly, the router has a MAC
 address on his NIC card connected

0:22:20.780000 --> 0:22:27.720000
 to that wire. Why don't we just say
 he's 0, 0, 0, 2, a-a-a-a-a-a-a-b-b

0:22:27.720000 --> 0:22:31.040000
-b, because this is hexadecimal.

0:22:31.040000 --> 0:22:36.200000
 So now in this particular case, when
 ethernet goes to put the ethernet

0:22:36.200000 --> 0:22:40.960000
 header on the front, it will say, I'm
 trying to give myself enough room

0:22:40.960000 --> 0:22:48.180000
 here, that the destination is 0, 0,
 0, 0, 2, a-a-a-a-a-b-b-b-b, and it

0:22:48.180000 --> 0:22:57.080000
 will say the source is 0, 0, 0, 0, 2,
 1, 1, 1, 2, 2, 2, kind of ran out

0:22:57.080000 --> 0:23:00.540000
 of room here, but
 you get the idea.

0:23:00.540000 --> 0:23:04.680000
 So you can see the way this works is
 that everything that's put on the

0:23:04.680000 --> 0:23:09.400000
 wire at layer two has to be sourced
 from the MAC address of the NIC card

0:23:09.400000 --> 0:23:15.440000
 that created it, and it has to be going
 to a NIC card that's on this wire.

0:23:15.440000 --> 0:23:17.580000
 So that's what we see here.

0:23:17.580000 --> 0:23:21.720000
 It's coming from my MAC address, going
 to the MAC address of the router.

0:23:21.720000 --> 0:23:25.240000
 So initially, when the router sees
 this ethernet frame coming in, he's

0:23:25.240000 --> 0:23:27.300000
 going to say, oh, somebody's
 trying to talk to me.

0:23:27.300000 --> 0:23:32.600000
 Okay. But then when he strips off this
 blue section, he says, okay, it

0:23:32.600000 --> 0:23:33.880000
 looks like it's me at layer two.

0:23:33.880000 --> 0:23:36.820000
 Now let's pass it up the
 OSI model to layer three.

0:23:36.820000 --> 0:23:41.860000
 When he strips that off, he'll say,
 oh, the destination is not me, it's

0:23:41.860000 --> 0:23:44.460000
 somebody else, 7777.

0:23:44.460000 --> 0:23:50.360000
 Okay, as a router, I guess my job is
 to route that packet and send it

0:23:50.360000 --> 0:23:56.080000
 on its way. Now, why am I talking about
 MAC addresses in the context of

0:23:56.080000 --> 0:24:00.520000
 a video, where we're talking
 about IPv6 interface IDs?

0:24:00.520000 --> 0:24:06.480000
 Because when you use the EUI64 keyword
 to dynamically come up with your

0:24:06.480000 --> 0:24:12.020000
 interface ID, the MAC address of your
 NIC card is going to be a critical

0:24:12.020000 --> 0:24:14.460000
 component of that.

0:24:14.460000 --> 0:24:17.880000
 So let's go back to this.

0:24:17.880000 --> 0:24:25.740000
 Given the fact that your network prefix
 in IPv6 is 64 bits long, the other

0:24:25.740000 --> 0:24:30.700000
 half of the address, the interface
 ID, is also 64 bits long.

0:24:30.700000 --> 0:24:35.300000
 But if you remember hexadecimal, each
 one of these characters was equal

0:24:35.300000 --> 0:24:37.840000
 to 4 bits. Right?

0:24:37.840000 --> 0:24:39.900000
 So I'll just write out
 the first part of it.

0:24:39.900000 --> 0:24:44.740000
 0, 0, 0, 0, 0, 0, 0, 0, 0, 0,
 0, 0, 0, 0, 0, 0, 0, 1, 0.

0:24:44.740000 --> 0:24:51.660000
 So that right there
 encompasses this.

0:24:51.660000 --> 0:24:54.640000
 So that is a word, right?

0:24:54.640000 --> 0:24:59.420000
 That's 16 bits. 16 times 3 is 48.

0:24:59.420000 --> 0:25:02.820000
 48. Now think about
 this for a second.

0:25:02.820000 --> 0:25:08.560000
 If I say EUI64, what I'm telling him
 is, take your MAC address and turn

0:25:08.560000 --> 0:25:12.560000
 it into a 64-bit interface ID.

0:25:12.560000 --> 0:25:16.960000
 But he says, but the number you're
 giving me is not a 64-bit number.

0:25:16.960000 --> 0:25:19.040000
 It's a 48-bit number.

0:25:19.040000 --> 0:25:25.800000
 It's too short. So one of the things
 that EUI64 does is it expands that

0:25:25.800000 --> 0:25:29.100000
 MAC address by putting in some
 characters in the middle.

0:25:29.100000 --> 0:25:31.800000
 So it says, OK, here's
 what I'm going to do.

0:25:31.800000 --> 0:25:36.720000
 0, 0, 0, 2, colon, AA.

0:25:36.720000 --> 0:25:40.380000
 That's the first half
 of the MAC address.

0:25:40.380000 --> 0:25:47.540000
 A, A. He says, OK, here's
 what I'm going to do.

0:25:47.540000 --> 0:25:53.700000
 Now that I've split it up in order to
 expand this out into a 64-bit number,

0:25:53.700000 --> 0:25:58.960000
 I'm going to put it in the
 middle here, F, F, F, E.

0:25:58.960000 --> 0:26:02.320000
 We're not done yet, but
 we're almost there.

0:26:02.320000 --> 0:26:04.980000
 So this is part of
 what EUI64 does.

0:26:04.980000 --> 0:26:08.280000
 To dynamically create an interface
 ID, it takes the MAC address, cuts

0:26:08.280000 --> 0:26:12.380000
 it in half, and puts F,
 F, F, E in the middle.

0:26:12.380000 --> 0:26:15.700000
 So look, we've just taken a 48
-bit number, and what did we do?

0:26:15.700000 --> 0:26:21.360000
 We added another 16 bits to it, because
 each one of these characters is

0:26:21.360000 --> 0:26:28.160000
 4 bits. So now 48 plus 16, now we've
 got ourselves a 64-bit number, but

0:26:28.160000 --> 0:26:31.240000
 we're not quite done.

0:26:31.240000 --> 0:26:35.660000
 In the world of Ethernet, and we'll
 talk more about this when we talk

0:26:35.660000 --> 0:26:41.000000
 about Ethernet, but 0, 0.

0:26:41.000000 --> 0:26:47.740000
 This bit right here
 has a special name.

0:26:47.740000 --> 0:26:53.140000
 That bit is called the individual group,
 that's called the universal local

0:26:53.140000 --> 0:26:57.460000
 bit, or sometimes called
 the global local bit.

0:26:57.460000 --> 0:27:02.260000
 And that'll be explained more
 in the Ethernet section.

0:27:02.260000 --> 0:27:04.580000
 It's also sometimes
 called universal.

0:27:04.580000 --> 0:27:10.720000
 Universal, slash local bit.

0:27:10.720000 --> 0:27:15.180000
 And I'm not really going to explain
 right now why it's important in the

0:27:15.180000 --> 0:27:18.300000
 context of global local, universal,
 local, but what I am going to say

0:27:18.300000 --> 0:27:22.340000
 is when you're talking about an interface,
 when you're talking about EUI64,

0:27:22.340000 --> 0:27:27.580000
 whatever that bit was in the original
 MAC address, it gets changed to

0:27:27.580000 --> 0:27:29.080000
 just the opposite.

0:27:29.080000 --> 0:27:36.220000
 So what would end up happening here is
 we would have I'll do it down here.

0:27:36.220000 --> 0:27:42.540000
 So this was the original 0, 0, 0, 0,
 0, 0, 0, 0, 0, 0, 0, 0, 0, 0, 0,

0:27:42.540000 --> 0:27:47.540000
 0, 1, 0. And then we had
 AA, AA, AA, BB, BB.

0:27:47.540000 --> 0:27:49.100000
 So that's what we had.

0:27:49.100000 --> 0:27:55.200000
 So now what we're going to do is we're
 going to take this bit, and we're

0:27:55.200000 --> 0:27:58.200000
 going to flip it to
 just the opposite.

0:27:58.200000 --> 0:28:05.400000
 One little bit change, which will
 give us 0, 0, 0, 0, 0, 0, 1, 0.

0:28:05.400000 --> 0:28:12.680000
 0, 0, 0, 0, 0, 0, 0, 0, 0,
 AA, AA, baby, baby stolen.

0:28:12.680000 --> 0:28:18.000000
 And so if I convert this word back into
 hexadecimal, that would give me

0:28:18.000000 --> 0:28:28.220000
 the numbers of 0, 2, 0,2,
 colon, AA, AA, colon, BBB.

0:28:28.220000 --> 0:28:35.120000
 So now when we go back up to our EUI64,
 not only does it have to split

0:28:35.120000 --> 0:28:38.940000
 this address in half and put FFFE in
 it, but now that we've flipped the

0:28:38.940000 --> 0:28:49.440000
 bit, our EUI64 interface ID becomes
 0, 2, 0, 2, colon, AA, FF, colon,

0:28:49.440000 --> 0:28:54.220000
 FEAA, colon, BBB.

0:28:54.220000 --> 0:28:58.880000
 And that is the, that's what would
 be applied to the second portion of

0:28:58.880000 --> 0:29:03.580000
 the IPv6 address as the, what we used
 to call host bits, but we now call

0:29:03.580000 --> 0:29:05.560000
 the interface ID.

0:29:05.560000 --> 0:29:07.840000
 So let's do an example of this.

0:29:07.840000 --> 0:29:11.860000
 Let me give you an exercise and
 see if you can figure this out.

0:29:11.860000 --> 0:29:16.540000
 You might want to take a screenshot
 of this real quick.

0:29:16.540000 --> 0:29:28.260000
 All right. So here is a laptop, let's
 say, and its MAC address is equal

0:29:28.260000 --> 0:29:44.580000
 to 0, 2, 1, A, 555, 667, 7.

0:29:44.580000 --> 0:29:56.820000
 2001, 2222, 333, 444, colon, colon,
 slash 64, and then you say EUI64.

0:29:56.820000 --> 0:30:02.700000
 So now my question to you is what will
 the full address be when it creates

0:30:02.700000 --> 0:30:08.060000
 the interface ID, what will
 be the full address?

0:30:08.060000 --> 0:30:14.020000
 Pause the video and then press play
 when you think you figured it out.

0:30:14.020000 --> 0:30:18.240000
 All right. So it doesn't really matter
 which order we take and I'm going

0:30:18.240000 --> 0:30:19.680000
 to do the bit flipping first.

0:30:19.680000 --> 0:30:22.580000
 So it's going to be
 flipped right here.

0:30:22.580000 --> 0:30:29.120000
 So we know that 0, 2 is 0, 0, 0, 0,
 0, 1, 0, and we know that it's this

0:30:29.120000 --> 0:30:35.380000
 bit, the universal local bit
 that's going to be changed.

0:30:35.380000 --> 0:30:42.800000
 So that will be changed to
 0, 0, 0, 0, 0, 0, 0, 0, 0.

0:30:42.800000 --> 0:30:44.780000
 That's going to be the change.

0:30:44.780000 --> 0:30:55.360000
 Okay. So now we've gone to 0, 0, 1,
 A instead of 0, 2, 1, A, it's been

0:30:55.360000 --> 0:31:02.500000
 now changed to 0, 0, 1, A, colon, 5,
 5, and now we've got to put the FFFE

0:31:02.500000 --> 0:31:11.820000
 in there. FFFE, and then we put the
 remainder of the MAC address.

0:31:11.820000 --> 0:31:16.340000
 5, 5, 6, 6, 7, 7.

0:31:16.340000 --> 0:31:19.320000
 So that is the answer.

0:31:19.320000 --> 0:31:25.100000
 By using EUI64, this is the interface
 ID that it comes up with.

