Would you like to inspect the original subtitles? These are the user uploaded subtitles that are being translated:
1
00:00:01,280 --> 00:00:07,680
Welcome to Jeremy’s IT Lab. This is a free,\xa0\n
2
00:00:07,679 --> 00:00:13,599
videos, please subscribe to follow along with the\xa0\n
3
00:00:13,599 --> 00:00:17,439
and share the video to help spread this\xa0\n
4
00:00:18,559 --> 00:00:23,679
In this video we will continue our\xa0\n
5
00:00:23,679 --> 00:00:31,039
these are the specific exam topics relevant to\xa0\n
6
00:00:31,039 --> 00:00:38,079
learning about various IPv6 address types. In Day\xa0\n
7
00:00:38,079 --> 00:00:43,839
local IPv6 addresses, but this time let’s go more\xa0\n
8
00:00:45,679 --> 00:00:50,880
Here’s what we’ll cover. First up, we’ll\xa0\n
9
00:00:50,880 --> 00:00:56,240
configuration. I’ll show you one more way to\xa0\n
10
00:00:56,799 --> 00:01:02,319
specifically using something called ‘modified\xa0\n
11
00:01:02,320 --> 00:01:09,439
you might have noticed is exam topic 1.9.f.\xa0\n
12
00:01:10,159 --> 00:01:15,439
Global unicast, unique local, link\xa0\n
13
00:01:16,959 --> 00:01:22,159
This is going to be a very information-dense\xa0\n
14
00:01:22,159 --> 00:01:28,640
take your time, use the flashcards, and make sure\xa0\n
15
00:01:28,640 --> 00:01:34,079
sure to watch until the end of the video for a\xa0\n
16
00:01:35,200 --> 00:01:40,480
ExSim, made by Boson Software, is the best and\xa0\n
17
00:01:41,280 --> 00:01:46,560
In my experience they simulate the style\xa0\n
18
00:01:46,560 --> 00:01:53,840
exams very well. If you want to check out Boson\xa0\n
19
00:01:54,400 --> 00:01:59,920
Let’s get right into the topic. First up is\xa0\n
20
00:01:59,920 --> 00:02:08,879
called EUI-64. EUI stands for Extended Unique\xa0\n
21
00:02:08,879 --> 00:02:16,000
the technically correct term is ‘modified’ EUI-64,\xa0\n
22
00:02:17,840 --> 00:02:22,080
This topic can actually go quite deep and it’s\xa0\n
23
00:02:22,080 --> 00:02:27,440
for the CCNA, so just be aware that you\xa0\n
24
00:02:27,439 --> 00:02:36,000
or just ‘EUI-64’. For our purpose, they are the\xa0\n
25
00:02:36,000 --> 00:02:42,560
MAC address into a 64-bit interface identifier,\xa0\n
26
00:02:42,560 --> 00:02:50,560
the ‘host portion’ of a /64 IPv6 address.\xa0\n
27
00:02:51,199 --> 00:02:57,919
so /64 means 64 bits are the network portion\xa0\n
28
00:02:59,280 --> 00:03:03,840
Let’s walk through how to convert the MAC\xa0\n
29
00:03:05,199 --> 00:03:08,799
When you actually configure this on the\xa0\n
30
00:03:08,800 --> 00:03:14,480
but you should know how to do it. The first step\xa0\n
31
00:03:14,479 --> 00:03:24,079
the interface, in half. For example, if the MAC\xa0\n
32
00:03:24,080 --> 00:03:30,960
in between 6 and 7. Now we have the two halves\xa0\n
33
00:03:30,960 --> 00:03:39,600
hexadecimal FFFE in the middle. So, in between\xa0\n
34
00:03:40,240 --> 00:03:47,680
Invert the 7th bit. If the 7th bit is a 0, make\xa0\n
35
00:03:48,560 --> 00:03:53,280
This is trickier than the first two steps, but\xa0\n
36
00:03:53,280 --> 00:03:59,840
working with hexadecimal and binary. So, where\xa0\n
37
00:04:00,879 --> 00:04:05,519
It’s the 3rd bit of this ‘2’. Remember,\xa0\n
38
00:04:06,080 --> 00:04:14,640
so the ‘1’ is bits 1, 2, 3, and 4. Then the\xa0\n
39
00:04:14,639 --> 00:04:20,719
the 3rd bit of the hexadecimal 2, is the\xa0\n
40
00:04:21,600 --> 00:04:27,840
Convert it back to hexadecimal, and now the\xa0\n
41
00:04:27,839 --> 00:04:34,000
it’s 64 bits. It will simply be added on to the\xa0\n
42
00:04:35,839 --> 00:04:41,759
Before I move on to explain more, here are a few\xa0\n
43
00:04:41,759 --> 00:04:50,560
an EUI-64 interface identifier. Remember the three\xa0\n
44
00:04:50,560 --> 00:04:58,079
FFFE in the middle. And 3, invert the 7th bit.\xa0\n
45
00:05:02,560 --> 00:05:05,920
Okay, here are the answers. If\xa0\n
46
00:05:05,920 --> 00:05:10,960
try writing out some random MAC addresses\xa0\n
47
00:05:12,639 --> 00:05:20,560
Here’s how to configure an interface using EUI-64.\xa0\n
48
00:05:21,199 --> 00:05:28,560
followed by the network prefix,\xa0\n
49
00:05:29,360 --> 00:05:35,439
That’s it. That tells the router to use this\xa0\n
50
00:05:35,439 --> 00:05:40,639
to generate an IPv6 address.\xa0\n
51
00:05:40,639 --> 00:05:45,919
and G0/2. So, let’s check the actual\xa0\n
52
00:05:47,759 --> 00:05:51,839
First up, I used SHOW INTERFACES to\xa0\n
53
00:05:52,639 --> 00:05:57,039
Here they are. Note that the MAC address\xa0\n
54
00:05:57,040 --> 00:06:03,520
only the last digit is different. So, their EUI-64\xa0\n
55
00:06:04,480 --> 00:06:08,560
If you want, try pausing the video here\xa0\n
56
00:06:08,560 --> 00:06:15,600
was generated on each interface. But let’s\xa0\n
57
00:06:16,480 --> 00:06:24,240
And here’s G0/0’s IPv6 address. Notice that\xa0\n
58
00:06:25,199 --> 00:06:30,719
And here’s the FFFE inserted in the middle of\xa0\n
59
00:06:32,000 --> 00:06:38,319
And here are the addresses of G0/1 and G0/2. As\xa0\n
60
00:06:38,319 --> 00:06:44,800
addresses used to generate the IPv6 addresses\xa0\n
61
00:06:44,800 --> 00:06:51,280
EUI-64 allows routers to automatically generate an\xa0\n
62
00:06:51,279 --> 00:06:56,959
64-bit interface ID, which is then combined\xa0\n
63
00:06:59,040 --> 00:07:03,920
Before moving on, let me briefly explain something\xa0\n
64
00:07:03,920 --> 00:07:08,480
to know this for the CCNA, but I’m sure I’ll\xa0\n
65
00:07:08,480 --> 00:07:15,840
why the 7th bit is inverted from 1 to 0 or 0 to\xa0\n
66
00:07:17,120 --> 00:07:21,920
UAAs, universally administered addresses,\xa0\n
67
00:07:21,920 --> 00:07:28,960
to the device by the manufacturer. There are\xa0\n
68
00:07:29,600 --> 00:07:33,360
These are MAC addresses which are manually\xa0\n
69
00:07:34,399 --> 00:07:39,279
In Cisco IOS you can manually configure a\xa0\n
70
00:07:39,279 --> 00:07:47,359
an interface. These MAC addresses don’t have to\xa0\n
71
00:07:47,360 --> 00:07:54,960
by the 7th bit of the MAC address, which is called\xa0\n
72
00:07:54,959 --> 00:08:03,919
is set to 0, it’s a UAA. If the U/L bit is set to\xa0\n
73
00:08:03,920 --> 00:08:11,280
addresses and EUI-64, the meaning of the U/L\xa0\n
74
00:08:11,279 --> 00:08:19,279
it means that the MAC address the EUI-64 interface\xa0\n
75
00:08:19,279 --> 00:08:25,359
it means that the MAC address the EUI-64\xa0\n
76
00:08:25,360 --> 00:08:31,280
that this doesn’t actually effect the function of\xa0\n
77
00:08:31,279 --> 00:08:36,799
address is universal or local. If you want\xa0\n
78
00:08:36,799 --> 00:08:44,240
do a Google search for ‘eui-64 packetlife.net’,\xa0\n
79
00:08:44,240 --> 00:08:49,519
get into the details, but we’re moving outside of\xa0\n
80
00:08:51,840 --> 00:08:57,840
So, ‘EUI-64’ isn’t really a ‘type’ of IPv6\xa0\n
81
00:08:57,840 --> 00:09:02,560
generating an IPv6 address using a\xa0\n
82
00:09:03,679 --> 00:09:06,799
Now let’s talk about an actual\xa0\ndefined type of IPv6 address.
83
00:09:07,440 --> 00:09:14,560
That is the global unicast address, exam topic\xa0\n
84
00:09:15,679 --> 00:09:22,079
Global unicast IPv6 addresses are public\xa0\n
85
00:09:22,080 --> 00:09:27,280
We haven’t talked about public and private IPv4\xa0\n
86
00:09:28,480 --> 00:09:34,800
You must register to use global unicast addresses.\xa0\n
87
00:09:34,799 --> 00:09:40,079
that they are globally unique. If two companies\xa0\n
88
00:09:40,080 --> 00:09:44,560
there are going to be problems, like two\xa0\n
89
00:09:46,480 --> 00:09:51,519
The range of addresses to be used for global\xa0\n
90
00:09:51,519 --> 00:10:02,000
2000::/3, which includes all addresses from\xa0\n
91
00:10:02,000 --> 00:10:08,159
followed by seven quartets of Fs. That’s a lot of\xa0\n
92
00:10:08,159 --> 00:10:14,000
many more addresses. Now all addresses which\xa0\n
93
00:10:14,000 --> 00:10:20,159
unicast addresses. Here’s an example of a global\xa0\n
94
00:10:20,159 --> 00:10:26,879
let’s go over it again. This blue part is the\xa0\n
95
00:10:26,879 --> 00:10:33,120
to the company by the ISP. The company is free to\xa0\n
96
00:10:33,919 --> 00:10:40,639
However, because IPv6 addresses usually use a /64\xa0\n
97
00:10:40,639 --> 00:10:45,840
bits in the prefix are the ‘subnet identifier’,\xa0\n
98
00:10:47,039 --> 00:10:52,240
16 bits allows for over 65,000 subnets,\xa0\n
99
00:10:54,080 --> 00:10:57,680
These two parts together make\xa0\n
100
00:10:59,200 --> 00:11:04,000
Finally, the second half of the address,\xa0\n
101
00:11:04,000 --> 00:11:11,600
is called the ‘interface identifier’ in IPv6.\xa0\n
102
00:11:11,600 --> 00:11:16,639
or manually configured however you want.\xa0\n
103
00:11:16,639 --> 00:11:23,199
global unicast address. Global routing prefix,\xa0\n
104
00:11:24,879 --> 00:11:28,799
Next up we’ll look at unique\xa0\n
105
00:11:30,080 --> 00:11:35,040
Unique local IPv6 addresses are private\xa0\n
106
00:11:35,759 --> 00:11:40,639
These are like private IPv4 addresses. Again,\xa0\n
107
00:11:40,639 --> 00:11:47,279
up soon. You do not need to register to use them.\xa0\n
108
00:11:47,279 --> 00:11:52,480
and don’t need to be globally unique. I put\xa0\n
109
00:11:52,480 --> 00:11:58,320
you’ll see soon, you should still try to make the\xa0\n
110
00:11:58,320 --> 00:12:03,920
be routed over the Internet, your ISP will simply\xa0\n
111
00:12:06,000 --> 00:12:14,399
The address block FC00::/7 is reserved for unique\xa0\n
112
00:12:14,399 --> 00:12:19,519
that the 8th bit be set to 1, so really all\xa0\n
113
00:12:20,960 --> 00:12:27,280
Here’s an example of a unique local address.\xa0\n
114
00:12:27,279 --> 00:12:32,319
simply indicates that this is a unique local\xa0\n
115
00:12:33,440 --> 00:12:39,360
The next 40 bits are called the ‘global ID’.\xa0\n
116
00:12:39,360 --> 00:12:45,039
be randomly generated. Why randomly generated\xa0\n
117
00:12:46,159 --> 00:12:50,480
The global ID should be unique so that\xa0\n
118
00:12:51,279 --> 00:12:56,799
If all companies use the simple global ID of\xa0\n
119
00:12:56,799 --> 00:13:01,039
their networks they might have the same subnet\xa0\n
120
00:13:01,039 --> 00:13:06,639
cause a lot of problems. By randomly generating\xa0\n
121
00:13:06,639 --> 00:13:12,720
subnets are very low. So, even though these unique\xa0\n
122
00:13:12,720 --> 00:13:17,360
it’s still a good idea to randomly generate the\xa0\n
123
00:13:18,720 --> 00:13:23,600
Okay, the next part of the address is the subnet\xa0\n
124
00:13:25,200 --> 00:13:29,360
And these first 64 bits make up\xa0\n
125
00:13:29,360 --> 00:13:34,720
you don’t have to use a /64 prefix length, but\xa0\n
126
00:13:35,840 --> 00:13:40,639
Then the last 64 bits are the interface\xa0\n
127
00:13:43,759 --> 00:13:51,679
Next up, link local addresses, topic 1.9.c on\xa0\n
128
00:13:51,679 --> 00:13:57,679
are automatically generated on IPv6-enabled\xa0\n
129
00:13:57,679 --> 00:14:03,279
that you can use the command IPV6 ENABLE to\xa0\n
130
00:14:03,279 --> 00:14:09,919
configuring an IPv6 address on it. It will then\xa0\n
131
00:14:09,919 --> 00:14:16,159
and that will be the only IPv6 address on the\xa0\n
132
00:14:16,159 --> 00:14:26,240
block FE80::/10. However, the standard states\xa0\n
133
00:14:26,240 --> 00:14:33,039
so you won’t actually see any link local addresses\xa0\n
134
00:14:34,320 --> 00:14:38,000
Then, the interface ID is\xa0\n
135
00:14:39,039 --> 00:14:45,199
Here’s the same output of SHOW IPV6 INTERFACE\xa0\n
136
00:14:45,200 --> 00:14:51,440
link local address uses the same interface ID as\xa0\n
137
00:14:51,440 --> 00:14:58,160
because both used EUI-64 to generate the interface\xa0\n
138
00:14:58,159 --> 00:15:04,079
used for communication within a single link, a\xa0\n
139
00:15:04,080 --> 00:15:09,120
with a link-local destination IPv6 address, they\xa0\n
140
00:15:10,320 --> 00:15:15,760
So, what are some actual uses of link-local\xa0\n
141
00:15:15,759 --> 00:15:23,919
peerings. OSPFv3, used for IPv6, uses link-local\xa0\n
142
00:15:23,919 --> 00:15:31,039
etc. They can also be used as the next-hop\xa0\n
143
00:15:31,039 --> 00:15:36,959
protocol, NDP, which is IPv6’s replacement for\xa0\n
144
00:15:37,919 --> 00:15:43,599
I’ll talk about NDP as well as IPv6 routing in\xa0\n
145
00:15:45,840 --> 00:15:54,960
This is just an example of one use for link-local\xa0\n
146
00:15:54,960 --> 00:16:04,400
subnet wants to send this packet to PC2 in the\xa0\n
147
00:16:04,399 --> 00:16:15,519
to its default gateway 2001:DB8:0:1::1, which is\xa0\n
148
00:16:15,519 --> 00:16:23,759
in its routing table, and the next hop is FE80::3,\xa0\n
149
00:16:23,759 --> 00:16:32,559
destination 2001:DB8:0:2::2 in its routing table\xa0\n
150
00:16:32,559 --> 00:16:41,039
the packet to R3. R3 looks up the destination\xa0\n
151
00:16:41,039 --> 00:16:48,079
a next hop address of FE80::7, so it forwards\xa0\n
152
00:16:49,200 --> 00:16:55,759
Notice that in this part of the network, the\xa0\n
153
00:16:55,759 --> 00:17:04,400
example, couldn’t send a ping to R3. If R1 tried\xa0\n
154
00:17:04,400 --> 00:17:10,880
be dropped because the destination is a link-local\xa0\n
155
00:17:10,880 --> 00:17:16,160
addresses these link-local addresses work just\xa0\n
156
00:17:16,160 --> 00:17:22,800
local addresses on these interfaces. Anyway, as I\xa0\n
157
00:17:23,440 --> 00:17:26,320
I just wanted to show you one\xa0\nuse for link-local addresses.
158
00:17:28,720 --> 00:17:33,680
Next up let’s look at multicast\xa0\n
159
00:17:35,039 --> 00:17:38,960
For review, unicast addresses are\xa0\n
160
00:17:40,000 --> 00:17:45,839
A unicast packet is from one source to\xa0\n
161
00:17:45,839 --> 00:17:51,519
used for ‘one-to-all’ communication. From one\xa0\n
162
00:17:52,720 --> 00:17:58,480
Multicast addresses are used for ‘one-to-many’\xa0\n
163
00:17:58,480 --> 00:18:02,319
destinations, those hosts that have\xa0\n
164
00:18:03,680 --> 00:18:11,600
IPv6 uses the range FF00::/8 for multicast. In\xa0\n
165
00:18:11,599 --> 00:18:16,879
multicast addresses, but let me tell you one\xa0\n
166
00:18:17,680 --> 00:18:24,640
IPv6 doesn’t use broadcast. There is no\xa0\n
167
00:18:24,640 --> 00:18:29,360
to send a message to all hosts in the subnet using\xa0\n
168
00:18:31,200 --> 00:18:36,640
Here’s a chart of some important multicast\xa0\n
169
00:18:37,519 --> 00:18:42,720
You should know all of these multicast addresses\xa0\n
170
00:18:42,720 --> 00:18:48,799
you remember them. Notice that the IPv4\xa0\n
171
00:18:49,680 --> 00:19:00,000
For example, the all OSPF routers multicast\xa0\n
172
00:19:00,960 --> 00:19:10,079
The all EIGRP routers multicast address is FF02::A\xa0\n
173
00:19:10,079 --> 00:19:17,039
and it’s 224.0.0.10 in IPv4. Now let\xa0\n
174
00:19:17,039 --> 00:19:24,079
the all nodes multicast address. You also might\xa0\n
175
00:19:24,079 --> 00:19:30,399
Basically, it functions like a broadcast, since\xa0\n
176
00:19:30,400 --> 00:19:35,360
that’s how IPv6 can perform broadcasts, by\xa0\n
177
00:19:37,680 --> 00:19:44,000
Here’s another aspect of IPv6 multicast\xa0\n
178
00:19:44,000 --> 00:19:49,279
multiple multicast ‘scopes’ which indicate how\xa0\n
179
00:19:50,480 --> 00:19:55,200
By the way, the addresses in the previous\xa0\n
180
00:19:55,200 --> 00:20:01,759
stays in the local subnet. Note that this is a\xa0\n
181
00:20:01,759 --> 00:20:07,519
which begins with FE80. These are IPv6\xa0\n
182
00:20:07,519 --> 00:20:14,879
scope. Here are a few of the IPv6 multicast\xa0\n
183
00:20:14,880 --> 00:20:21,520
addresses begin with FF01. These multicast\xa0\n
184
00:20:22,559 --> 00:20:26,159
It can be used to send traffic to a\xa0\n
185
00:20:26,160 --> 00:20:31,200
but the router won’t actually send traffic out\xa0\n
186
00:20:31,200 --> 00:20:39,759
‘node-local’ used for this scope also. Next is the\xa0\n
187
00:20:39,759 --> 00:20:44,640
these multicast addresses stay within the local\xa0\n
188
00:20:46,000 --> 00:20:51,599
Okay, the next few scopes are a little less\xa0\n
189
00:20:51,599 --> 00:20:57,519
clearly defined and don’t need any special\xa0\n
190
00:20:57,519 --> 00:21:04,000
beginning with FF05, can actually be forwarded by\xa0\n
191
00:21:04,000 --> 00:21:09,519
a single physical location and not forwarded\xa0\n
192
00:21:09,519 --> 00:21:14,319
engineer to configure the actual scope, how far\xa0\n
193
00:21:15,599 --> 00:21:20,399
This is way beyond the scope of the CCNA, so\xa0\n
194
00:21:20,400 --> 00:21:27,040
multicasts begin with FF05. Same for the\xa0\n
195
00:21:27,039 --> 00:21:33,039
which begin with FF08. These are intended to\xa0\n
196
00:21:33,920 --> 00:21:37,600
For example, the scope might be to all\xa0\n
197
00:21:38,400 --> 00:21:42,080
Once again, it’s up to the network engineers\xa0\n
198
00:21:43,440 --> 00:21:50,160
One more scope you should be aware of is global,\xa0\n
199
00:21:50,160 --> 00:21:55,120
organization-local, and these multicast messages\xa0\n
200
00:21:56,240 --> 00:22:00,960
They are defined as having ‘no boundaries’, but\xa0\n
201
00:22:00,960 --> 00:22:06,960
actually be sent to every destination all over the\xa0\n
202
00:22:06,960 --> 00:22:12,480
the CCNA, but Cisco expects you to be aware\xa0\n
203
00:22:12,480 --> 00:22:16,559
and know how to identify them using the\xa0\n
204
00:22:18,000 --> 00:22:24,240
To help you visualize those different scopes,\xa0\n
205
00:22:24,240 --> 00:22:29,519
if it sends a link-local multicast it would\xa0\n
206
00:22:30,720 --> 00:22:33,519
A site-local multicast might reach these devices.\xa0\xa0
207
00:22:34,240 --> 00:22:40,559
Wider than link-local, but not being sent over\xa0\n
208
00:22:40,559 --> 00:22:46,079
organization-local multicast might reach these\xa0\n
209
00:22:46,079 --> 00:22:51,919
connected with a WAN link. Finally, the global\xa0\n
210
00:22:53,039 --> 00:22:58,000
Again, aside from interface-local and link-local\xa0\n
211
00:22:58,000 --> 00:23:03,200
to be defined by the network engineer, and\xa0\n
212
00:23:04,160 --> 00:23:08,720
So, that brief introduction to IPv6\xa0\n
213
00:23:10,720 --> 00:23:14,880
Before moving on to the next address type, I\xa0\n
214
00:23:14,880 --> 00:23:21,920
of SHOW IPV6 INTERFACE. This is the same router\xa0\n
215
00:23:21,920 --> 00:23:28,320
and we’re looking at its G0/0 interface. Here’s\xa0\n
216
00:23:29,039 --> 00:23:32,639
These are the multicast groups that\xa0\n
217
00:23:33,599 --> 00:23:42,079
FF02::1, which multicast address is this? It’s\xa0\n
218
00:23:42,720 --> 00:23:51,360
and notice that the scope is link-local. R1’s\xa0\n
219
00:23:51,920 --> 00:23:55,759
so it joins the ‘all hosts’ multicast\xa0\n
220
00:23:56,720 --> 00:24:04,000
It also joined multicast group FF02::2. What’s\xa0\n
221
00:24:04,000 --> 00:24:10,319
group. R1 is a router, so it joins this\xa0\n
222
00:24:10,319 --> 00:24:15,119
also joins this multicast group. This is\xa0\n
223
00:24:15,119 --> 00:24:20,719
of multicast address in Day 33. Now let’s\xa0\n
224
00:24:22,480 --> 00:24:29,920
The next kind of address is anycast, which is\xa0\n
225
00:24:29,920 --> 00:24:37,360
is a new feature of IPv6. Anycast messaging is\xa0\n
226
00:24:37,359 --> 00:24:44,079
here are some helpful diagrams from Wikipedia.\xa0\n
227
00:24:44,079 --> 00:24:50,480
is one-to-one. Broadcast is one-to-all.\xa0\n
228
00:24:51,279 --> 00:24:55,359
And anycast is one-to-one-of-many,\xa0\n
229
00:24:56,480 --> 00:25:02,559
There are multiple possible destinations, but the\xa0\n
230
00:25:03,519 --> 00:25:08,559
Multiple routers are configured with the same\xa0\n
231
00:25:08,559 --> 00:25:13,279
to advertise the address. So, when hosts\xa0\n
232
00:25:13,839 --> 00:25:17,439
other routers will forward it to the nearest\xa0\n
233
00:25:18,559 --> 00:25:21,279
‘Nearest’ refers to the smallest\xa0\n
234
00:25:22,640 --> 00:25:27,840
Unlike the other address types I introduced today,\xa0\n
235
00:25:28,799 --> 00:25:33,759
Use a regular unicast address, for example\xa0\n
236
00:25:34,400 --> 00:25:41,360
and specify it as an anycast address. Here’s\xa0\n
237
00:25:41,359 --> 00:25:48,399
which is like a /32 IPv4 address. So, if I\xa0\n
238
00:25:48,400 --> 00:25:52,720
a host route to this specific address\xa0\n
239
00:25:54,079 --> 00:26:00,720
Here’s that example in the CLI. Configure it like\xa0\n
240
00:26:00,720 --> 00:26:08,160
to the end of the command. Looking at SHOW IPV6\xa0\n
241
00:26:09,359 --> 00:26:15,599
On top is the EUI-64 address we configured\xa0\n
242
00:26:16,720 --> 00:26:20,720
Under it is the anycast address we\xa0\n
243
00:26:20,720 --> 00:26:26,319
at the end. Note that, even though this is\xa0\n
244
00:26:26,319 --> 00:26:31,919
‘global unicast addresses’ in this command,\xa0\n
245
00:26:33,599 --> 00:26:41,839
To finish up, here are two other IPv6 addresses.\xa0\n
246
00:26:41,839 --> 00:26:46,399
usually just written as a double colon.\xa0\n
247
00:26:46,400 --> 00:26:54,320
its IPv6 address yet. IPv6 default routes are\xa0\n
248
00:26:55,440 --> 00:26:59,200
The IPv4 equivalent of this address is 0.0.0.0.\xa0\xa0
249
00:27:00,400 --> 00:27:08,240
The last IPv6 address I want to introduce is\xa0\n
250
00:27:09,279 --> 00:27:14,879
This is the IPv6 loopback address. It’s used\xa0\n
251
00:27:16,000 --> 00:27:21,440
Messages sent to this address are processed within\xa0\n
252
00:27:22,720 --> 00:27:30,000
The IPv4 equivalent is the 127.0.0.0/8\xa0\n
253
00:27:30,000 --> 00:27:35,920
block of addresses for loopbacks, IPv6 uses just\xa0\n
254
00:27:38,319 --> 00:27:42,079
That was a lot of information, I’m\xa0\n
255
00:27:43,039 --> 00:27:47,839
I showed you another way of configuring IPv6\xa0\n
256
00:27:47,839 --> 00:27:54,720
generate an interface ID using EUI-64.\xa0\n
257
00:27:55,680 --> 00:28:02,480
Global unicast addresses are public IPv6 addresses\xa0\n
258
00:28:02,480 --> 00:28:08,960
the three sections of a global unicast address.\xa0\n
259
00:28:08,960 --> 00:28:16,000
and the interface identifier. Then we looked at\xa0\n
260
00:28:16,000 --> 00:28:21,680
to use IPv6 addresses in this range. You’re free\xa0\n
261
00:28:21,680 --> 00:28:27,600
addresses aren’t routed over the Internet.\xa0\n
262
00:28:28,400 --> 00:28:33,600
These are automatically configured when you\xa0\n
263
00:28:33,599 --> 00:28:38,319
by configuring another IPv6 address such as\xa0\n
264
00:28:39,039 --> 00:28:45,440
or you can just use the IPV6 ENABLE command on the\xa0\n
265
00:28:45,440 --> 00:28:52,799
and automatically configure a link-local address.\xa0\n
266
00:28:52,799 --> 00:28:58,319
including some common reserved multicast\xa0\n
267
00:28:59,440 --> 00:29:04,960
We also covered the different multicast scopes.\xa0\n
268
00:29:04,960 --> 00:29:12,079
but be familiar with the concept. We looked at a\xa0\n
269
00:29:12,079 --> 00:29:16,399
which are used to send traffic to one destination\xa0\n
270
00:29:18,160 --> 00:29:23,920
Also, the unspecified IPv6 address which is all\xa0\n
271
00:29:24,559 --> 00:29:28,799
and the IPv6 loopback address,\xa0\n
272
00:29:30,079 --> 00:29:35,279
This lesson had a lot of information, so go back\xa0\n
273
00:29:36,319 --> 00:29:41,439
If you have any questions, feel free to ask.\xa0\n
274
00:29:41,440 --> 00:29:47,920
these topics beyond the scope of the CCNA. If you\xa0\n
275
00:29:49,119 --> 00:29:54,719
As always, watch until the end of today’s quiz\xa0\n
276
00:29:55,279 --> 00:30:01,200
the best practice exams for the CCNA. Okay,\xa0\n
277
00:30:04,000 --> 00:30:14,640
R1’s G0/1 interface has a MAC address of\xa0\n
278
00:30:14,640 --> 00:30:24,400
be after issuing the following command?\xa0\n
279
00:30:25,279 --> 00:30:29,359
Here are the options. Pause the video\xa0\n
280
00:30:34,400 --> 00:30:39,840
The answer is D. The 7th bit of the\xa0\n
281
00:30:39,839 --> 00:30:46,720
changing the D in the MAC address to an F.\xa0\n
282
00:30:46,720 --> 00:30:52,160
the middle of the MAC address to expand it\xa0\n
283
00:30:54,160 --> 00:30:57,680
Which portion of the IPv6\xa0\n
284
00:30:58,640 --> 00:31:01,759
Here are the options, the\xa0\n
285
00:31:02,640 --> 00:31:06,480
So, which option is correct? Pause\xa0\n
286
00:31:10,960 --> 00:31:15,519
Okay, the correct answer is B. This\xa0\n
287
00:31:16,400 --> 00:31:20,960
After FD, the next 40 bits,\xa0\n
288
00:31:20,960 --> 00:31:25,600
form the global ID. This portion of the\xa0\n
289
00:31:25,599 --> 00:31:31,839
so that subnets don’t overlap in the case that\xa0\n
290
00:31:34,160 --> 00:31:38,880
R3 sent an IPv6 multicast message to\xa0\n
291
00:31:39,759 --> 00:31:45,920
What was the destination IPv6 address of\xa0\n
292
00:31:45,920 --> 00:31:59,840
FF01::1. B, FF01::2. C, FF02::1. Or D, FF02::2.\xa0\n
293
00:32:03,839 --> 00:32:11,759
The answer is D, FF02::2. First, look\xa0\n
294
00:32:11,759 --> 00:32:17,680
as in A and B, is for interface-local, also\xa0\n
295
00:32:18,880 --> 00:32:21,200
Those won’t be sent to\xa0\ndevices on the local subnet.\xa0\xa0
296
00:32:21,920 --> 00:32:29,680
For that, a link-local multicast message like\xa0\n
297
00:32:30,400 --> 00:32:37,840
is a message to ALL hosts on the local subnet,\xa0\n
298
00:32:39,039 --> 00:32:44,079
is the link-local multicast address for\xa0\n
299
00:32:46,559 --> 00:32:51,279
What kind of IPv6 address is automatically\xa0\n
300
00:32:51,279 --> 00:32:59,519
command is used? Select the best answer. The\xa0\n
301
00:32:59,519 --> 00:33:09,839
node-local. C, link-local. Or D, EUI-64.\xa0\n
302
00:33:11,039 --> 00:33:17,839
The answer is C, link-local. IPV6 ENABLE\xa0\n
303
00:33:17,839 --> 00:33:23,599
a link-local address to be automatically\xa0\n
304
00:33:23,599 --> 00:33:28,799
have a link-local address, in addition to whatever\xa0\n
305
00:33:30,240 --> 00:33:34,880
In creating the link-local address the\xa0\n
306
00:33:35,440 --> 00:33:39,360
so some of you might have selected\xa0\n
307
00:33:39,359 --> 00:33:44,879
name of the type of address, so D is not\xa0\n
308
00:33:47,519 --> 00:33:51,839
The diagrams on the right visualize\xa0\n
309
00:33:52,480 --> 00:33:56,400
Match them with the correct message type.\n
310
00:33:56,960 --> 00:34:05,840
Unicast, broadcast, multicast, and anycast.\xa0\n
311
00:34:07,039 --> 00:34:12,800
Let’s check the answers. Unicast is 3. From\xa0\n
312
00:34:14,000 --> 00:34:21,199
Broadcast is 2, from the source to all possible\xa0\n
313
00:34:21,199 --> 00:34:27,919
multiple destinations. And anycast is 1, from the\xa0\n
314
00:34:29,039 --> 00:34:34,639
Okay, that’s all for the quiz. Let’s move on\xa0\n
315
00:34:38,400 --> 00:34:43,440
Okay, here's today's Boson ExSim practice\xa0\n
316
00:34:43,440 --> 00:34:49,440
address prefixes are not routable? Select 2\xa0\n
317
00:34:50,079 --> 00:34:55,920
It means if a router receives a packet and the\xa0\n
318
00:34:55,920 --> 00:34:59,039
the router will not forward the\xa0\n
319
00:35:00,960 --> 00:35:10,960
So how about A? 2000::/3. This is not one of\xa0\n
320
00:35:10,960 --> 00:35:21,760
unicast range, and global unicast addresses are\xa0\n
321
00:35:21,760 --> 00:35:28,160
one of the correct answers. This address prefix\xa0\n
322
00:35:28,159 --> 00:35:36,480
prefix range, and link-local addresses can only\xa0\n
323
00:35:36,480 --> 00:35:43,760
next C and D. These are both in the unique local\xa0\n
324
00:35:43,760 --> 00:35:48,880
They cannot be routed over the public Internet,\xa0\n
325
00:35:48,880 --> 00:35:53,840
internal networks these addresses can be used\xa0\n
326
00:35:56,079 --> 00:36:01,840
And then E and F. These are both multicast\xa0\n
327
00:36:01,840 --> 00:36:11,760
beginning. But look at the scope, FF05 for E. That\xa0\n
328
00:36:12,880 --> 00:36:16,720
Site-local multicasts can be\xa0\n
329
00:36:16,719 --> 00:36:23,679
so E is not one of the answers. However F,\xa0\n
330
00:36:24,960 --> 00:36:29,280
Much like the link-local address,\xa0\n
331
00:36:29,280 --> 00:36:34,880
address also is not routable outside of\xa0\n
332
00:36:34,880 --> 00:36:41,039
so let's see if my answers are correct. Down here\xa0\n
333
00:36:42,159 --> 00:36:48,639
So, I will scroll down. And you can pause\xa0\n
334
00:36:52,880 --> 00:36:53,840
And there's more down here.\xa0\xa0
335
00:36:57,199 --> 00:37:02,559
So, as you can see the explanation is quite\xa0\n
336
00:37:02,559 --> 00:37:07,360
are really one of the great things about Boson\xa0\n
337
00:37:07,360 --> 00:37:12,480
of the practice exams in Boson ExSim, read the\xa0\n
338
00:37:12,480 --> 00:37:16,800
ones you get right and the wrongs you get wrong.\xa0\n
339
00:37:16,800 --> 00:37:23,760
of the topics and feel comfortable when you take\xa0\n
340
00:37:23,760 --> 00:37:29,120
CCNA. If you want to get Boson ExSim for yourself,\xa0\n
341
00:37:32,639 --> 00:37:38,159
There are supplementary materials for this video.\xa0\n
342
00:37:38,159 --> 00:37:45,759
‘Anki’. Note that I have added the tag ‘ipv6’ to\xa0\n
343
00:37:45,760 --> 00:37:50,880
so you can use Anki to specifically review\xa0\n
344
00:37:51,840 --> 00:37:56,079
There was a lot to memorize in this video, so\xa0\n
345
00:37:57,599 --> 00:38:01,679
There will also be a packet tracer practice\xa0\n
346
00:38:02,239 --> 00:38:07,599
That will be in the next video. Sign up for my\xa0\n
347
00:38:07,599 --> 00:38:11,279
and I’ll send you all of the flashcards\xa0\n
348
00:38:12,960 --> 00:38:17,199
Before finishing today’s video I want\xa0\n
349
00:38:17,760 --> 00:38:20,480
To join, please click the\xa0\n
350
00:38:21,760 --> 00:38:27,840
Thank you to Brandon, Magrathea, Njabulo,\xa0\n
351
00:38:27,840 --> 00:38:34,880
Nasir, Erlison, Apogee, Wasseem, Marko, Florian,\xa0\n
352
00:38:35,519 --> 00:38:42,159
John, Funnydart, Scott, Hassan, Gerrard, Marek,\xa0\n
353
00:38:42,159 --> 00:38:47,519
Boson Software, Charlesetta, Devin, Lito,\xa0\n
354
00:38:47,519 --> 00:38:53,119
your name incorrectly, but thank you so much for\xa0\n
355
00:38:53,119 --> 00:38:57,599
Channel failed to load, if this is you please\xa0\n
356
00:38:58,719 --> 00:39:04,399
This is the list of JCNP-level members at the\xa0\n
357
00:39:05,119 --> 00:39:09,759
if you signed up recently and your name isn’t\xa0\n
358
00:39:11,519 --> 00:39:14,639
Thank you for watching. Please\xa0\n
359
00:39:14,639 --> 00:39:19,359
like the video, leave a comment, and share the\xa0\n
360
00:39:20,400 --> 00:39:26,000
If you want to leave a tip, check the links in the\xa0\n
361
00:39:26,000 --> 00:39:32,639
and accept BAT, or Basic Attention Token, tips\xa0\n
30975
Can't find what you're looking for?
Get subtitles in any language from opensubtitles.com, and translate them here.
Afrikaans
Albanian
Amharic
Armenian
Azerbaijani
Basque
Belarusian
Bengali
Bosnian
Bulgarian
Catalan
Cebuano
Chichewa
Chinese (Simplified)
Chinese (Traditional)
Corsican
Croatian
Czech
Danish
Dutch
English
Esperanto
Estonian
Finnish
French
Frisian
Galician
Georgian
German
Greek
Gujarati
Haitian Creole
Hawaiian
Hungarian
Icelandic
Indonesian
Irish
Italian
Japanese
Kazakh
Khmer
Korean
Kurdish (Kurmanji)
Kyrgyz
Lao
Latvian
Lithuanian
Luxembourgish
Macedonian
Malagasy
Malay
Maltese
Maori
Mongolian
Myanmar (Burmese)
Nepali
Norwegian
Pashto
Polish
Portuguese
Romanian
Russian
Samoan
Serbian
Sesotho
Shona
Sinhala
Slovak
Slovenian
Somali
Spanish
Swahili
Swedish
Tajik
Thai
Turkish
Ukrainian
Urdu
Uzbek
Vietnamese
