Would you like to inspect the original subtitles? These are the user uploaded subtitles that are being translated:
1
00:00:00,720 --> 00:00:05,839
Welcome to Jeremy’s IT Lab. This is\xa0\n
2
00:00:06,960 --> 00:00:11,599
If you like these videos, please subscribe\xa0\n
3
00:00:11,599 --> 00:00:15,919
please like and leave a comment, and share the\xa0\n
4
00:00:16,480 --> 00:00:21,039
Thanks for your help. Also, remember to\xa0\n
5
00:00:21,039 --> 00:00:25,439
to get all of the lab files for this course, so\xa0\n
6
00:00:27,039 --> 00:00:32,479
If you want more labs like these, I highly\xa0\n
7
00:00:32,479 --> 00:00:34,879
click the link in the video\xa0\n
8
00:00:35,759 --> 00:00:40,559
It’s a network simulator like packet tracer, but\xa0\n
9
00:00:40,560 --> 00:00:45,120
guided labs to not only help you get hands-on\xa0\n
10
00:00:45,119 --> 00:00:50,559
but also deepen your understanding of the exam\xa0\n
11
00:00:50,560 --> 00:00:54,400
certifications, so I feel confident\xa0\n
12
00:00:55,119 --> 00:00:59,439
If you want to get your own copy of NetSim,\xa0\n
13
00:01:01,520 --> 00:01:05,920
In today’s video we’ll try a few\xa0\n
14
00:01:05,920 --> 00:01:11,200
as well as IPv6 static routes. We\xa0\n
15
00:01:11,200 --> 00:01:15,280
but using the context-sensitive help\xa0\n
16
00:01:16,400 --> 00:01:23,040
Step 1 says to use EUI-64 to configure the\xa0\n
17
00:01:23,040 --> 00:01:28,640
R1 and R2. But before actually configuring\xa0\n
18
00:01:28,640 --> 00:01:34,159
address of each interface and calculate the\xa0\n
19
00:01:35,280 --> 00:01:43,680
So let’s do that on R1 first. ENABLE. To\xa0\n
20
00:01:43,680 --> 00:01:50,240
use SHOW INTERFACES G0/1. Up here near the\xa0\n
21
00:01:50,959 --> 00:01:56,479
So, let’s calculate the EUI-64 interface ID,\xa0\n
22
00:01:57,760 --> 00:02:01,680
In this document I’ve written out\xa0\n
23
00:02:02,319 --> 00:02:09,039
Split it in half, and then insert FFFE in\xa0\n
24
00:02:09,039 --> 00:02:16,079
which makes the 0 a 2. That’s the EUI-64\xa0\n
25
00:02:16,080 --> 00:02:22,400
this is the IPv6 address that will be configured\xa0\n
26
00:02:26,240 --> 00:02:32,480
CONF T. Before configuring the interface, I should\xa0\n
27
00:02:32,479 --> 00:02:42,560
pings later. IPV6 UNICAST-ROUTING. Okay, now let’s\xa0\n
28
00:02:42,560 --> 00:02:52,960
ADDRESS 2001:db8::/64, that’s the network prefix.\xa0\n
29
00:02:52,960 --> 00:03:00,560
check the address that was configured. DO SHOW\xa0\n
30
00:03:00,560 --> 00:03:07,199
a link-local address was automatically configured\xa0\n
31
00:03:07,199 --> 00:03:12,399
but a different network prefix, beginning\xa0\n
32
00:03:14,240 --> 00:03:17,840
Now let’s do the same process on R2.\xa0\xa0
33
00:03:19,520 --> 00:03:27,840
ENABLE. SHOW INTERFACES G0/1. Here is the MAC\xa0\n
34
00:03:28,800 --> 00:03:36,160
Here is that same MAC address. To get the EUI-64\xa0\n
35
00:03:36,159 --> 00:03:44,000
the middle, and finally invert the 7th bit.\xa0\n
36
00:03:44,000 --> 00:03:49,439
network prefix to it, you get the IPv6 address\xa0\n
37
00:03:50,879 --> 00:03:58,400
Let’s go back to the CLI of R2. CONF T.\xa0\n
38
00:03:59,280 --> 00:04:06,159
IPV6 UNICAST-ROUTING. Now let’s\xa0\n
39
00:04:06,800 --> 00:04:19,759
IPV6 ADDRESS 2001:db8:0:1::/64 EUI-64. Okay, let’s\xa0\n
40
00:04:21,199 --> 00:04:23,920
There it is, and a link-local\xa0\naddress was configured, too.
41
00:04:25,680 --> 00:04:32,079
In step 2 we are told to configure the appropriate\xa0\n
42
00:04:33,199 --> 00:04:38,079
Since we’re already on R2, I’m going to copy the\xa0\n
43
00:04:38,079 --> 00:04:47,680
be PC2’s default gateway. Now let’s go on PC2.\xa0\n
44
00:04:48,560 --> 00:04:53,280
I’ll paste in R2’s address. Now\xa0\n
45
00:04:54,639 --> 00:05:04,800
It’s 2001:db8:0:1::2, with a /64 prefix length.\xa0\n
46
00:05:04,800 --> 00:05:09,840
based off of the MAC address which you\xa0\n
47
00:05:11,120 --> 00:05:16,879
Now I’ll return to R1. Let me copy the\xa0\n
48
00:05:18,959 --> 00:05:25,919
Now I’ll configure PC1. First, I’ll paste\xa0\n
49
00:05:27,600 --> 00:05:37,840
Next I’ll configure PC1’s address,\xa0\n
50
00:05:38,560 --> 00:05:44,160
Step 3 says to enable IPv6 on\xa0\n
51
00:05:44,160 --> 00:05:49,600
without explicitly configuring an IPv6\xa0\n
52
00:05:51,360 --> 00:05:58,400
INTERFACE G0/0. To enable IPv6 on an\xa0\n
53
00:05:59,040 --> 00:06:04,640
That’s it. That will automatically configure\xa0\n
54
00:06:04,639 --> 00:06:12,319
of IPv6 address? It’s a link-local address.\xa0\n
55
00:06:13,680 --> 00:06:17,120
There it is, and notice the EUI-64 interface ID\xa0\xa0
56
00:06:17,120 --> 00:06:21,199
is different than G0/1’s, because the\xa0\n
57
00:06:22,560 --> 00:06:32,480
Okay, next I’ll do the same on R2. INTERFACE\xa0\n
58
00:06:32,480 --> 00:06:42,160
configured. DO SHOW IPV6 INTERFACE BRIEF. There it\xa0\n
59
00:06:44,079 --> 00:06:50,319
Finally, step 4 says to configure static\xa0\n
60
00:06:51,360 --> 00:06:57,199
We’ll cover IPv6 static routes in day 33,\xa0\n
61
00:06:57,199 --> 00:07:02,079
multiple ways to configure this, for example we\xa0\n
62
00:07:02,079 --> 00:07:07,599
but I’ll just configure a route to each specific\xa0\n
63
00:07:07,600 --> 00:07:15,840
that was just configured here on R2, I’ll use it\xa0\n
64
00:07:17,439 --> 00:07:23,680
Let me EXIT back to global config mode. The\xa0\n
65
00:07:23,680 --> 00:07:29,840
IPV6 ROUTE, now I’ll use the context-sensitive\xa0\n
66
00:07:30,639 --> 00:07:39,348
Just like in IPv4 routes, we have to configure\xa0\n
67
00:07:40,240 --> 00:07:47,360
Now let’s see what’s next. So, we can configure an\xa0\n
68
00:07:47,360 --> 00:07:54,000
hop as the link-local address of R2 by pasting it\xa0\n
69
00:07:54,000 --> 00:08:01,040
an error message is displayed. Interface has to be\xa0\n
70
00:08:01,040 --> 00:08:06,000
a link-local address as a next-hop, you can’t\xa0\n
71
00:08:06,000 --> 00:08:12,079
the interface, too. If I use the context-sensitive\xa0\n
72
00:08:12,079 --> 00:08:19,519
here. So, I need to put it before the next-hop.\xa0\n
73
00:08:19,519 --> 00:08:25,839
scroll up and copy the link-local address of R1’s\xa0\n
74
00:08:27,392 --> 00:08:36,879
Now let’s configure the route on\xa0\n
75
00:08:36,879 --> 00:08:42,240
then the exit interface, G0/0. Finally\xa0\n
76
00:08:43,360 --> 00:08:47,919
Okay, that’s all. So, let’s test out\xa0\n
77
00:08:52,399 --> 00:09:02,799
PING 2001:db8:0:1::2. Okay,\xa0\nPC1 is able to reach PC2.
78
00:09:04,159 --> 00:09:12,319
So, in this lab we configured IPv6 addresses using\xa0\n
79
00:09:12,320 --> 00:09:18,960
without manually configuring an address, and then\xa0\n
80
00:09:18,960 --> 00:09:25,040
in depth about IPv6 static routing. Now let’s\xa0\n
81
00:09:27,519 --> 00:09:32,720
Okay, here's today's Boson NetSim lab preview.\xa0\n
82
00:09:32,720 --> 00:09:39,600
IPv6 1. Here's the objective. Understand and\xa0\n
83
00:09:40,159 --> 00:09:47,199
and implement RIPng to implement dynamic\xa0\n
84
00:09:47,200 --> 00:09:51,680
isn't actually in the CCNA exam topics, but\xa0\n
85
00:09:52,960 --> 00:09:57,120
All of the commands you need to know\xa0\n
86
00:09:57,120 --> 00:10:03,840
IPv6 RIP ENABLE. So you can complete this lab\xa0\n
87
00:10:06,480 --> 00:10:10,720
Here are the IP addresses currently configured.\xa0\n
88
00:10:10,720 --> 00:10:17,040
the network. We're going to add IPv6 on\xa0\n
89
00:10:17,039 --> 00:10:24,719
examine the initial network configuration.\xa0\n
90
00:10:26,799 --> 00:10:30,479
And finally task 4, verify IPv6.\xa0\n
91
00:10:31,440 --> 00:10:38,240
For this lab preview, let's just do task 3,\xa0\n
92
00:10:39,440 --> 00:10:46,400
So part A, implement IPv6 addressing, step\xa0\n
93
00:10:46,399 --> 00:10:50,959
the WAN links that connect the Tampa,\xa0\n
94
00:10:52,240 --> 00:10:56,879
Okay, so these four routers, just these\xa0\n
95
00:10:56,879 --> 00:11:00,960
addressing on the WAN link that connects the\xa0\n
96
00:11:02,000 --> 00:11:06,480
Okay, and this diagram and the table show\xa0\n
97
00:11:09,600 --> 00:11:14,720
Okay, review the commands used to assign\xa0\n
98
00:11:14,720 --> 00:11:18,960
these commands to the commands you currently\xa0\n
99
00:11:19,679 --> 00:11:24,719
So this means, the commands you\xa0\n
100
00:11:25,519 --> 00:11:32,399
And the commands are quite similar. IPv4\xa0\n
101
00:11:33,039 --> 00:11:37,599
And most commands are like that, they're\xa0\n
102
00:11:37,600 --> 00:11:46,399
but for IPv6 instead of IP you have to enter\xa0\n
103
00:11:46,399 --> 00:11:53,120
enable IPv6 routing. Okay, let's do that. Here on\xa0\n
104
00:11:53,120 --> 00:12:04,799
routers. Okay, the console password is admin, and\xa0\n
105
00:12:05,519 --> 00:12:15,919
cisco. And let's configure IPv6 routing. Okay,\xa0\n
106
00:12:22,320 --> 00:12:28,879
Okay, that's all for Orlando. We aren't\xa0\n
107
00:12:28,879 --> 00:12:42,320
Daytona next. Admin, enable, cisco. IPv6\xa0\n
108
00:12:50,159 --> 00:12:51,839
Okay, so let's see what's next.\xa0\xa0
109
00:12:54,000 --> 00:12:59,440
On Tampa, Orlando, Daytona, and Miami, assign\xa0\n
110
00:12:59,440 --> 00:13:05,840
IPv6 addresses table. Okay, so we will configure\xa0\n
111
00:13:06,480 --> 00:13:21,125
First, interface serial0/0. IPv6 address\xa0\n
112
00:13:21,125 --> 00:13:33,784
2001:0:1:2::1/64. Alright, next I'll go to\xa0\n
113
00:13:33,784 --> 00:13:56,480
2001:0:1:0::2/64. Interface serial0/1. IPv6\xa0\n
114
00:13:58,639 --> 00:14:09,840
Interface serial0/0. IPv6 address\xa0\n
115
00:14:15,679 --> 00:14:19,679
Okay, last one is Tampa. Serial0/0.\xa0\xa0
116
00:14:25,279 --> 00:14:39,839
And serial0/1. Okay, that's it.\xa0\n
117
00:14:41,519 --> 00:14:47,439
So this is what we haven't covered and it actually\xa0\n
118
00:14:47,440 --> 00:14:53,280
step 1. Updated routing protocols capable of \n
119
00:14:53,279 --> 00:14:58,319
order for IPv6 routes to be exchanged with\xa0\n
120
00:14:58,879 --> 00:15:04,240
RIP next generation, in this lab. RIPng\xa0\n
121
00:15:05,039 --> 00:15:11,519
Number 2, identify the commands you should issue\xa0\n
122
00:15:11,519 --> 00:15:16,159
these commands differ from the commands you would\xa0\n
123
00:15:18,080 --> 00:15:21,280
And then we will configure\xa0\n
124
00:15:22,720 --> 00:15:28,800
and use boson as the process identification\xa0\n
125
00:15:30,399 --> 00:15:38,079
We need to know just two commands. IPv6\xa0\n
126
00:15:38,080 --> 00:15:44,320
on the router. And the big difference\xa0\n
127
00:15:45,759 --> 00:15:50,240
you could only have one RIP process running\xa0\n
128
00:15:50,240 --> 00:15:54,480
and then you would enable RIP on the\xa0\n
129
00:15:55,519 --> 00:16:02,079
However, in RIPng, you enable RIPng\xa0\n
130
00:16:02,080 --> 00:16:07,840
followed by the process name, followed by\xa0\n
131
00:16:09,600 --> 00:16:13,920
Now, I believe that we could just\xa0\n
132
00:16:14,559 --> 00:16:17,839
and the process will be automatically\xa0\n
133
00:16:17,840 --> 00:16:25,200
IPv6 ROUTER RIP command. Let's see if I'm correct\xa0\n
134
00:16:27,679 --> 00:16:32,479
Oh, I can't use the interface range command,\xa0\n
135
00:16:32,480 --> 00:16:40,159
might be something in NetSim, I'm not sure\xa0\n
136
00:16:41,840 --> 00:16:47,680
and the process name, it said to use boson, and\xa0\n
137
00:16:50,320 --> 00:16:58,640
Use the up arrow to use the same command.\xa0\n
138
00:16:58,639 --> 00:17:09,359
by configuring it on the interfaces. SHOW\xa0\n
139
00:17:09,359 --> 00:17:13,679
IPv6 routing protocol is 'rip boson'.\xa0\n
140
00:17:15,440 --> 00:17:24,799
So, let's do that on the other routers.\xa0\n
141
00:17:26,480 --> 00:17:39,839
Interface serial0, IPv6 rip boson enable.\xa0\n
142
00:17:41,119 --> 00:17:53,519
Interface serial0/0. Ipv6 rip boson enable. And\xa0\n
143
00:17:54,160 --> 00:18:02,320
IPv6 rip boson enable. Okay, so let's see\xa0\n
144
00:18:04,799 --> 00:18:15,279
SHOW IPv6 ROUTE. Okay, looks like Tampa has\xa0\n
145
00:18:15,279 --> 00:18:20,399
time for it to learn the other routes.\xa0\n
146
00:18:21,279 --> 00:18:23,119
Yep, we're getting some RIP routes, looks good.\xa0\xa0
147
00:18:25,279 --> 00:18:34,639
How about Daytona? SHOW IPv6 ROUTE. Okay,\xa0\n
148
00:18:35,279 --> 00:18:42,319
Okay, we're getting RIP routes, looks good. Okay\xa0\n
149
00:18:42,319 --> 00:18:47,759
create the process from global config mode with\xa0\n
150
00:18:48,319 --> 00:18:53,119
and then enable it directly on interfaces\xa0\n
151
00:18:54,000 --> 00:18:58,319
However, if you enable it directly on the\xa0\n
152
00:18:58,319 --> 00:19:06,480
so you don't actually need to enter this command.\xa0\n
153
00:19:06,480 --> 00:19:13,039
we just did step 2 and step 3. We enabled RIPng\xa0\n
154
00:19:14,720 --> 00:19:19,120
Okay, next up we would verify our\xa0\n
155
00:19:19,119 --> 00:19:25,679
test the pings, but I'll leave it here for today.\xa0\n
156
00:19:25,680 --> 00:19:30,480
the link in the video description. As you can\xa0\n
157
00:19:31,680 --> 00:19:37,200
much more extensive than my packet tracer labs,\xa0\n
158
00:19:37,200 --> 00:19:40,960
Once again, if you want to get Boson NetSim,\xa0\n
159
00:19:43,039 --> 00:19:47,680
Before finishing today’s video I want\xa0\n
160
00:19:47,680 --> 00:19:50,480
To join, please click the\xa0\n
161
00:19:51,359 --> 00:19:57,919
Thank you to l33america, Brandon, Magrathea,\xa0\n
162
00:19:57,920 --> 00:20:04,240
Nil, Prakaash, Nasir, Erlison, Apogee, Wasseem,\xa0\n
163
00:20:04,240 --> 00:20:10,160
Ed, Value, John, Funnydart, Scott, Hassan,\xa0\n
164
00:20:10,160 --> 00:20:15,680
Boson Software, Charlesetta, Devin, Lito,\xa0\n
165
00:20:15,680 --> 00:20:21,440
your name incorrectly, but thank you so much for\xa0\n
166
00:20:21,440 --> 00:20:26,080
Channel failed to load, if this is you please\xa0\n
167
00:20:27,119 --> 00:20:32,799
This is the list of JCNP-level members at the\xa0\n
168
00:20:33,440 --> 00:20:38,320
if you signed up recently and your name isn’t\xa0\n
169
00:20:40,160 --> 00:20:43,200
Thank you for watching. Please\xa0\n
170
00:20:43,200 --> 00:20:47,840
like the video, leave a comment, and share the\xa0\n
171
00:20:49,039 --> 00:20:54,639
If you want to leave a tip, check the links in the\xa0\n
172
00:20:54,640 --> 00:21:01,200
and accept BAT, or Basic Attention Token, tips\xa0\n
14476
Can't find what you're looking for?
Get subtitles in any language from opensubtitles.com, and translate them here.
Afrikaans
Akan
Albanian
Amharic
Armenian
Azerbaijani
Basque
Belarusian
Bemba
Bengali
Bihari
Bosnian
Breton
Bulgarian
Cambodian
Catalan
Cebuano
Cherokee
Chichewa
Chinese (Simplified)
Chinese (Traditional)
Corsican
Croatian
Czech
Danish
Dutch
English
Esperanto
Estonian
Faroese
Finnish
Galician
Georgian
German
Greek
Guarani
Haitian Creole
Hausa
Hawaiian
Hebrew
Hmong
Hungarian
Icelandic
Indonesian
Irish
Italian
Japanese
Kazakh
Kinyarwanda
Kirundi
Kongo
Korean
Krio (Sierra Leone)
Kurdish
Kyrgyz
Laothian
Latin
Latvian
Lithuanian
Luganda
Luo
Luxembourgish
Macedonian
Malagasy
Malay
Maltese
Maori
Mauritian Creole
Moldavian
Mongolian
Myanmar (Burmese)
Montenegrin
Nepali
Norwegian
Pashto
Persian
Polish
Portuguese (Brazil)
Portuguese (Portugal)
Quechua
Romanian
Romansh
Russian
Samoan
Scots Gaelic
Serbian
Sesotho
Setswana
Seychellois Creole
Shona
Sindhi
Sinhalese
Slovak
Slovenian
Somali
Spanish
Swedish
Tajik
Thai
Tigrinya
Tonga
Turkish
Turkmen
Ukrainian
Uzbek
Vietnamese
Welsh
Wolof