WEBVTT

0:00:08.680000 --> 0:00:14.880000
 Okay, in this section we're going to take
 a look at how to manually configure

0:00:14.880000 --> 0:00:19.820000
 IPv6 addresses on your devices.

0:00:19.820000 --> 0:00:23.220000
 We're going to start off with a base
 topology I have built here and we're

0:00:23.220000 --> 0:00:26.120000
 going to use this for
 most of the course.

0:00:26.120000 --> 0:00:29.460000
 So I have some of the addressing done
 already, some of the addressing

0:00:29.460000 --> 0:00:34.540000
 designed, where we're going to be looking
 at right now is going to be

0:00:34.540000 --> 0:00:41.380000
 on the VLAN 36 interfaces between
 router 3 and router 6.

0:00:41.380000 --> 0:00:49.280000
 So it's going to mostly involve FA00
.36 on router 3 just to start with

0:00:49.280000 --> 0:00:55.120000
 for this first section and then we'll
 move on to assigning addresses to

0:00:55.120000 --> 0:00:58.240000
 router 6 and so on.

0:00:58.240000 --> 0:01:03.080000
 So we're going to start with manually
 assigning IPv6 addresses and there's

0:01:03.080000 --> 0:01:06.360000
 actually quite a few ways to do this
 which is where we're going to take

0:01:06.360000 --> 0:01:09.000000
 a minute here to do it.

0:01:09.000000 --> 0:01:15.360000
 So the first one would just to
 simply be to type IPv6 enable.

0:01:15.360000 --> 0:01:19.800000
 So if we switch over here to the command
 line and let me hop on to our

0:01:19.800000 --> 0:01:28.380000
 router 3 and we'll say interface FA00
.36 and just to start with we'll

0:01:28.380000 --> 0:01:34.460000
 just do show IPv6 interface brief and
 you can see here that as of right

0:01:34.460000 --> 0:01:41.220000
 now, FA00.36 does not have
 any IPv6 addresses on it.

0:01:41.220000 --> 0:01:46.860000
 So the first command is just to simply
 say IPv6 enable and I think a lot

0:01:46.860000 --> 0:01:51.680000
 of people misunderstand this command
 on the Cisco router that like maybe

0:01:51.680000 --> 0:01:55.860000
 you have to put it in or something
 like that and that's not the case.

0:01:55.860000 --> 0:02:02.720000
 IPv6 enable is a way of enabling IPv6
 on an interface but certainly not

0:02:02.720000 --> 0:02:09.780000
 the only one. What you get if you type
 IPv6 enable is you're going to

0:02:09.780000 --> 0:02:21.200000
 get a show IPv6 interface brief and
 you're going to end up with nothing

0:02:21.200000 --> 0:02:25.620000
 but a link local address
 on that interface.

0:02:25.620000 --> 0:02:30.400000
 That link local address is of course
 going to be based off of the client

0:02:30.400000 --> 0:02:36.000000
 ID that we discussed earlier and that
 of course comes from if I were to

0:02:36.000000 --> 0:02:46.760000
 say do show interface FA00 and look
 at the burned in MAC address on it.

0:02:46.760000 --> 0:02:55.380000
 This is that semi well known formatting,
 EY64 we're going to look at in

0:02:55.380000 --> 0:03:03.280000
 a minute, defaults to using this for
 the link local address which is you

0:03:03.280000 --> 0:03:11.260000
 take the second least significant bit
 which is right here of the first

0:03:11.260000 --> 0:03:15.400000
 byte of the MAC address and you flip
 the second least significant bit

0:03:15.400000 --> 0:03:21.380000
 to a one that's your local global bit
 indicating that this address is

0:03:21.380000 --> 0:03:26.380000
 now a global unique address and then
 of course right in the middle so

0:03:26.380000 --> 0:03:31.900000
 in this case between the D and the four
 in our MAC address so if you look

0:03:31.900000 --> 0:03:37.500000
 up here between the D and the four
 up here at this address you insert

0:03:37.500000 --> 0:03:50.980000
 FFFE to pad the 24 bit MAC address
 sorry 48 bit MAC address sorry out

0:03:50.980000 --> 0:04:00.440000
 to a 64 bit host portion for IPv6 so
 this is done automatically and this

0:04:00.440000 --> 0:04:04.760000
 is functional in fact just to show you
 that it works we can hop over to

0:04:04.760000 --> 0:04:27.560000
 outer six and say IPv6 interface brief
 it also gets an address and it's

0:04:27.560000 --> 0:04:33.700000
 fully functional the only problem is
 it's a little bit crazy of an address

0:04:33.700000 --> 0:04:37.660000
 to have to actually try to use so you
 know we can copy it we can go to

0:04:37.660000 --> 0:04:47.380000
 the other side and we can very easily
 say do ping put that address in

0:04:47.380000 --> 0:04:52.640000
 and you get the fun first problem that
 you have with using link local

0:04:52.640000 --> 0:04:57.380000
 addresses since and if you look at
 some of the other addresses we have

0:04:57.380000 --> 0:05:02.500000
 on this router already you see here
 we have a fast Ethernet 00 up 344

0:05:02.500000 --> 0:05:11.880000
 with an address F A 01 with an address
 and notice you all start FE80 colon

0:05:11.880000 --> 0:05:17.640000
 colon slash 10 as we discussed before
 so the problem is of course normally

0:05:17.640000 --> 0:05:21.880000
 a router looks at its routing table
 and says okay what interface does

0:05:21.880000 --> 0:05:27.020000
 this go out well the problem of course
 here is it doesn't have any idea

0:05:27.020000 --> 0:05:31.240000
 what the egress interface should be
 okay and this is of course this is

0:05:31.240000 --> 0:05:35.180000
 just a formatting thing on the Cisco
 router but this is another little

0:05:35.180000 --> 0:05:40.180000
 bit of a fun thing if you say that the
 outgoing interface is F A 00 dot

0:05:40.180000 --> 0:05:45.660000
 36 it'll actually yell at you here and
 say oh no no no I want the whole

0:05:45.660000 --> 0:05:55.420000
 name so fast Ethernet 00 dot 36 and
 it works so our link local address

0:05:55.420000 --> 0:06:00.860000
 in works okay and something else you
 should note it'll become important

0:06:00.860000 --> 0:06:05.620000
 as we move through some of our other
 modules coming up later such as BGP

0:06:05.620000 --> 0:06:12.460000
 I'll show you how to actually use the
 link local address to peer with

0:06:12.460000 --> 0:06:17.880000
 BGP neighbors and such problem is as
 soon as you use a link local address

0:06:17.880000 --> 0:06:22.780000
 like we did right up here it of course
 has no idea what the egress interface

0:06:22.780000 --> 0:06:29.100000
 should be as we've already discussed
 so for a lot of things if you're

0:06:29.100000 --> 0:06:33.080000
 going to use link local you need to be
 able to specify the egress interface

0:06:33.080000 --> 0:06:38.780000
 on the same line okay and you do this
 by specifying the interface index

0:06:38.780000 --> 0:06:43.740000
 number in the IPv6 address different
 operating systems do this different

0:06:43.740000 --> 0:06:50.140000
 ways if you're on a Windows machine
 and just an example and you have not

0:06:50.140000 --> 0:06:55.320000
 turned off IPv6 but if you're on that
 Windows machine and you look at

0:06:55.320000 --> 0:07:00.480000
 your IP config you'll find that it's
 usually something like a percent

0:07:00.480000 --> 0:07:05.520000
 nine something along those lines okay
 well what I'm talking about here

0:07:05.520000 --> 0:07:09.480000
 specifically is this part right here
 really just the part at the end I

0:07:09.480000 --> 0:07:14.440000
 mean we're going to use the whole address
 but this tells the router your

0:07:14.440000 --> 0:07:19.160000
 egress interface and Cisco chose to
 just use the interface name so if

0:07:19.160000 --> 0:07:26.080000
 I were to review my or repeat my ping
 command but this time actually add

0:07:26.080000 --> 0:07:31.760000
 that to the end of it okay so what
 sometimes confuses people a little

0:07:31.760000 --> 0:07:36.600000
 bit is it's going to be it's still
 the remote address that I'm trying

0:07:36.600000 --> 0:07:42.300000
 to contact but then after the percent
 is the local egress interface that

0:07:42.300000 --> 0:07:48.900000
 I want to go out hit enter and it just
 works it doesn't ask me what the

0:07:48.900000 --> 0:07:55.060000
 egress interface is anymore okay the
 other thing to note here a little

0:07:55.060000 --> 0:07:59.700000
 bit unfortunate but I'm sure you probably
 almost saw this coming is it's

0:07:59.700000 --> 0:08:03.560000
 case sensitive if I lower that just
 an e to lower case e it'll tell me

0:08:03.560000 --> 0:08:07.520000
 oh I have no idea what you're talking
 about I've never heard of that address

0:08:07.520000 --> 0:08:12.080000
 or protocol whatever that is you're trying
 to say so that's just a little

0:08:12.080000 --> 0:08:18.480000
 bit of a gotcha there okay so that's
 your ipv6 enable to wrap it up all

0:08:18.480000 --> 0:08:24.480000
 you do is you get a standard link local
 address based off the MAC address

0:08:24.480000 --> 0:08:33.500000
 of the device your next choice of course
 is ipv6 link local with automatic

0:08:33.500000 --> 0:08:39.020000
 assignment that's what we just looked
 at okay which is where you just

0:08:39.020000 --> 0:08:43.620000
 do ipv6 enable okay this sort of calls
 into some of the other stuff I'm

0:08:43.620000 --> 0:08:47.460000
 going to look at so let's move through
 a couple of these okay so when

0:08:47.460000 --> 0:08:51.460000
 we're talking about automatic or static
 assignment this is talking about

0:08:51.460000 --> 0:08:56.260000
 pulling a link local address with how
 you get your address with some of

0:08:56.260000 --> 0:09:01.260000
 the other things coming up later so
 in some of the upcoming lessons we

0:09:01.260000 --> 0:09:06.400000
 will come back and look at this again
 okay basically what we're what I'm

0:09:06.400000 --> 0:09:09.120000
 just trying to get out here is you're
 going to get a link local address

0:09:09.120000 --> 0:09:14.220000
 no matter how you get your global ipv6
 address and we'll see what happens

0:09:14.220000 --> 0:09:19.880000
 with this under different scenarios as
 we move forward through these lessons

0:09:19.880000 --> 0:09:25.860000
 so the next one we're going to look at
 right now is doing a global address

0:09:25.860000 --> 0:09:30.860000
 with EUI 64 and this is sort of going
 to play back into these two points

0:09:30.860000 --> 0:09:37.100000
 above it as well okay so and this one I
 think a lot of people don't understand

0:09:37.100000 --> 0:09:41.360000
 100% what happens here so let's take
 a look at it first thing I'm going

0:09:41.360000 --> 0:09:46.340000
 to do is I'm going to say no ipv6 enable
 now we don't have to take this

0:09:46.340000 --> 0:09:52.280000
 off but just in light of what I said
 earlier that you don't need it I

0:09:52.280000 --> 0:09:56.720000
 just want to show you that you in fact
 don't need it as soon as you're

0:09:56.720000 --> 0:10:00.020000
 going to go in and start manually doing
 your own stuff then you don't

0:10:00.020000 --> 0:10:04.080000
 need the ipv6 enable anymore okay that's
 just sort of a generic way of

0:10:04.080000 --> 0:10:08.960000
 quickly throwing ipv6 on an interface
 maybe this is like a link between

0:10:08.960000 --> 0:10:12.940000
 you and your service provider and as
 I get into some more complex examples

0:10:12.940000 --> 0:10:17.180000
 later I'll probably come back and just
 use that again it can be handy

0:10:17.180000 --> 0:10:21.220000
 I don't want anybody to understand
 what I'm saying it's just that you

0:10:21.220000 --> 0:10:25.580000
 don't need it if you're going to set
 the address another way okay so for

0:10:25.580000 --> 0:10:32.900000
 example if I said do show ipv6 interface
 brief right now okay we're back

0:10:32.900000 --> 0:10:39.320000
 to the 36 not having any address on
 it at all and now I'm going to say

0:10:39.320000 --> 0:10:46.160000
 ipv6 address and I'm going to give
 it a global address 2001 db8 colon

0:10:46.160000 --> 0:10:54.820000
 100 colon 36 colon colon and normally
 of course in a minute we'll put

0:10:54.820000 --> 0:10:59.300000
 the host portion here but what I'm looking
 at right now is using an eui64

0:10:59.300000 --> 0:11:08.000000
 assignment at which case you simply
 say the mask and then we're going

0:11:08.000000 --> 0:11:18.400000
 to say eui64 hit enter and what you
 get now do show ipv6 interface brief

0:11:18.400000 --> 0:11:24.560000
 is you're going to get the link local
 address because that always comes

0:11:24.560000 --> 0:11:29.080000
 along have to have the link local so
 we get the link local address back

0:11:29.080000 --> 0:11:35.840000
 again and now it's taking that same
 ending host portion based on the MAC

0:11:35.840000 --> 0:11:42.720000
 address and puts it after the global
 address that we put in but I think

0:11:42.720000 --> 0:11:47.240000
 the part where a lot of people get
 misled here a little bit is to say

0:11:47.240000 --> 0:11:53.800000
 that eui64 on the global address pulls
 its address from the MAC address

0:11:53.800000 --> 0:11:58.100000
 on the Cisco router that's not specifically
 true that's what I'm going

0:11:58.100000 --> 0:12:03.120000
 to show you right now what it actually
 does is it pulls the address from

0:12:03.120000 --> 0:12:08.380000
 the client identifier the client identifier
 is pulled from the link local

0:12:08.380000 --> 0:12:14.160000
 address the link local address is defaulting
 to pulling that from the

0:12:14.160000 --> 0:12:19.380000
 MAC address now all of that said I'm sure
 you can understand how it becomes

0:12:19.380000 --> 0:12:26.440000
 very common to say that if you use eui64
 that it pulls the host portion

0:12:26.440000 --> 0:12:31.900000
 from the MAC address the problem with
 that statement is again it's not

0:12:31.900000 --> 0:12:38.400000
 completely accurate it's accurate from
 a default standpoint however if

0:12:38.400000 --> 0:12:45.480000
 I were to say ipv6 address f e eight
 zero colon colon this is router three

0:12:45.480000 --> 0:12:50.900000
 so I'll just make it colon colon three
 and then I said link local to manually

0:12:50.900000 --> 0:12:57.120000
 set the link local address hit enter
 do show ipv6 interface brief what

0:12:57.120000 --> 0:13:01.040000
 we're going to find is that not only
 did that manually set my link local

0:13:01.040000 --> 0:13:10.680000
 address it also sets the client address
 for the global address so this

0:13:10.680000 --> 0:13:14.340000
 is what I'm saying when I say you can't
 just say eui64 is based off the

0:13:14.340000 --> 0:13:19.740000
 MAC address and we'll see this later
 when you get to like isotap tunnels

0:13:19.740000 --> 0:13:24.080000
 it's not based on the MAC address anyway
 it's based on the underlying

0:13:24.080000 --> 0:13:31.820000
 ipv4 address of the egress interface
 for the tunnel so eui64 is not always

0:13:31.820000 --> 0:13:36.760000
 based on the MAC address it's actually
 based on the client id for most

0:13:36.760000 --> 0:13:43.040000
 applications so we'll again build on
 this more as we go but this is sort

0:13:43.040000 --> 0:13:48.840000
 of an example of what I meant when I
 was talking about you know the slides

0:13:48.840000 --> 0:13:53.240000
 you know this is link local and how
 it behaves and what you can do with

0:13:53.240000 --> 0:13:57.600000
 link local with either an automatic
 assignment which is what we just did

0:13:57.600000 --> 0:14:03.980000
 that's one way of doing automatic okay
 just so we're clear eui64 is one

0:14:03.980000 --> 0:14:09.820000
 way of doing that another way of course
 is to say you know what happens

0:14:09.820000 --> 0:14:14.640000
 when there's a static assignment to the
 link local address so that's eui64

0:14:14.640000 --> 0:14:18.560000
 let me hop back over to router 3 here
 and now we're going to do it a little

0:14:18.560000 --> 0:14:27.320000
 bit different I'm going to say no ipv6
 address fe80 colon colon 3 link

0:14:27.320000 --> 0:14:42.040000
 local and when we look back at it it'll
 be back to the MAC based addressing

0:14:42.040000 --> 0:14:47.480000
 again and now what I'm going to do is
 I'm going to hardcode a real global

0:14:47.480000 --> 0:14:53.360000
 address so we're just going to go back
 up to where we said eui64 first

0:14:53.360000 --> 0:14:57.820000
 thing we need to do is take that off
 in fact you know what before I do

0:14:57.820000 --> 0:15:04.820000
 let's look at another interesting problem
 I'm going to actually hardcode

0:15:04.820000 --> 0:15:14.200000
 it an address I believe I mentioned
 this in a previous lesson but you

0:15:14.200000 --> 0:15:18.440000
 really have to be careful with ipv6 since
 it does support multiple addresses

0:15:18.440000 --> 0:15:24.720000
 on an interface you can see here what
 I end up with is my client id based

0:15:24.720000 --> 0:15:30.840000
 address which of course is this one
 and the one I just manually typed

0:15:30.840000 --> 0:15:35.860000
 in and again there's nothing fundamentally
 wrong with that unless of course

0:15:35.860000 --> 0:15:39.840000
 that wasn't your intention to end up
 with both addresses and if that's

0:15:39.840000 --> 0:15:43.860000
 the case you have to go back up to
 the address that we did with eui64

0:15:43.860000 --> 0:15:59.560000
 and take it off so there we go and
 this goes back to and we'll wrap up

0:15:59.560000 --> 0:16:05.540000
 with this this is a static address assignment
 okay so this was our last

0:16:05.540000 --> 0:16:09.340000
 our last point over here I didn't bring
 it up there but this is an ipv6

0:16:09.340000 --> 0:16:14.220000
 global address using a static assignment
 so we're just going to manually

0:16:14.220000 --> 0:16:20.600000
 put in our global address like such
 and the default behavior see this

0:16:20.600000 --> 0:16:25.720000
 doesn't go both ways like we were looking
 at a minute ago if you manually

0:16:25.720000 --> 0:16:32.500000
 set the link local that will change
 the global address used for any form

0:16:32.500000 --> 0:16:37.040000
 of automatic assignment in the next
 in the next section we're going to

0:16:37.040000 --> 0:16:42.260000
 move into some other ways of assigning
 an address and what we'll see there

0:16:42.260000 --> 0:16:47.660000
 is we can control this through link
 local as well but if you manually

0:16:47.660000 --> 0:16:54.000000
 set the global address or statically
 set the global that does not affect

0:16:54.000000 --> 0:16:59.380000
 the link local now since we use the
 link local for so much in ipv6 just

0:16:59.380000 --> 0:17:05.000000
 to leave you with a recommendation
 here I would say ipv6 address Fe8C

0:17:05.000000 --> 0:17:17.640000
 or colon colon three link local and
 then what you end up with is both

0:17:17.640000 --> 0:17:23.180000
 of your addresses manually set the way
 you want them that's how I would

0:17:23.180000 --> 0:17:29.060000
 do it if I was going to do manual address
 configuration and we are going

