Would you like to inspect the original subtitles? These are the user uploaded subtitles that are being translated:
1
00:00:03,528 --> 00:00:06,949
This is a free, complete course for the CCNA.
2
00:00:06,950 --> 00:00:10,940
If you like these videos, please subscribe\n
3
00:00:10,939 --> 00:00:15,800
Also, please like and leave a comment, and\n
4
00:00:18,349 --> 00:00:22,660
Also, remember to download this practice lab\n
5
00:00:25,800 --> 00:00:30,199
If you want more labs like these, I highly\n
6
00:00:30,199 --> 00:00:34,030
the CCNA, click the link in the video description\n
7
00:00:34,030 --> 00:00:39,219
It’s a network simulator like packet tracer,\n
8
00:00:39,219 --> 00:00:44,308
of these guided labs to not only help you\n
9
00:00:44,308 --> 00:00:47,320
but also deepen your understanding of the\nexam topics.
10
00:00:47,320 --> 00:00:52,850
I used it myself when studying for my certifications,\n
11
00:00:54,479 --> 00:00:59,338
Watch until the end of this video, we’ll\n
12
00:00:59,338 --> 00:01:05,429
If you want to get your own copy of NetSim,\n
13
00:01:05,430 --> 00:01:10,110
In this lab we’ll analyze rapid spanning\n
14
00:01:11,978 --> 00:01:17,099
I hope this lab will help you test and improve\n
15
00:01:17,099 --> 00:01:19,750
such as the different port roles and link\ntypes.
16
00:01:19,750 --> 00:01:23,439
Let’s get right into it with step 1.
17
00:01:23,439 --> 00:01:26,799
First we are asked which switch is the root\nbridge.
18
00:01:26,799 --> 00:01:35,939
Each switch has a priority of 32769, which\n
19
00:01:35,939 --> 00:01:41,478
for VLAN1, we will only be dealing with one\nVLAN in this lab.
20
00:01:41,478 --> 00:01:46,170
Of course, if there are multiple VLANs, the\n
21
00:01:46,170 --> 00:01:51,019
in each VLAN, because can we choose a different\n
22
00:01:51,019 --> 00:01:56,340
So, because each switch has the same priority,\n
23
00:01:56,340 --> 00:01:59,750
SW1’s MAC address is the lowest.
24
00:01:59,750 --> 00:02:07,019
Both SW1’s and SW3’s MAC addresses start\n
25
00:02:07,019 --> 00:02:11,259
5, and in SW3’s it’s C, which is equivalent\nto 12.
26
00:02:11,259 --> 00:02:14,560
So, SW1’s is the lowest, and it’s the\nroot bridge.
27
00:02:14,560 --> 00:02:20,180
Now let’s examine the port role and state\n
28
00:02:20,180 --> 00:02:23,900
different than what we have learned so far\n
29
00:02:23,900 --> 00:02:26,629
Enter privileged exec mode with ENABLE.
30
00:02:30,020 --> 00:02:37,900
Okay, F0/2, F0/1, and F0/24 are designated\n
31
00:02:37,900 --> 00:02:42,939
backup port in a discarding state, although\n
32
00:02:43,939 --> 00:02:48,128
I’m going to take these labels I have made\n
33
00:02:48,128 --> 00:02:52,469
So, what is different than what we have learned\n
34
00:02:52,469 --> 00:02:58,050
Well, I have repeated multiple times that\n
35
00:02:58,050 --> 00:03:02,710
ports, however in this case F0/3 is a backup port.
36
00:03:02,710 --> 00:03:06,439
So actually, the more accurate statement is\n
37
00:03:06,439 --> 00:03:09,969
in each collision domain it is connected to.
38
00:03:09,969 --> 00:03:14,419
In modern networks, hubs aren’t really used,\n
39
00:03:16,259 --> 00:03:20,030
However if the root bridge has two interfaces\n
40
00:03:20,030 --> 00:03:24,509
both connect to the same hub, the rule that\n
41
00:03:24,509 --> 00:03:29,818
collision domain applies, and the other interface\n
42
00:03:29,818 --> 00:03:34,399
If this was classic spanning tree, F0/3 would\n
43
00:03:34,400 --> 00:03:39,150
So, that’s step 1, although I have said\n
44
00:03:39,150 --> 00:03:45,200
bridge is designated, in this case F0/3 isn’t\n
45
00:03:47,860 --> 00:03:52,640
Step 2 asks us to determine the port role\n
46
00:03:55,408 --> 00:03:57,449
First let’s place the root ports.
47
00:03:57,449 --> 00:04:02,689
SW2’s root port is F0/1, with a root cost\nof 19.
48
00:04:05,039 --> 00:04:08,158
Does this hub add any spanning tree cost to\nthe BPDU?
49
00:04:08,158 --> 00:04:16,639
No, it doesn’t, so SW3’s F0/2 also has\n
50
00:04:16,639 --> 00:04:22,620
SW4’s interfaces have the same root cost,\n
51
00:04:22,620 --> 00:04:31,699
It’s SW3, because its MAC address is lower,\n
52
00:04:33,410 --> 00:04:39,090
SW3’s F0/1, across from SW4’s root port,\n
53
00:04:39,089 --> 00:04:46,159
Now, for the gigabitethernet link between\n
54
00:04:46,160 --> 00:04:53,350
They both have the same root cost, 19, but\n
55
00:04:59,149 --> 00:05:04,539
In this case, SW2 has the lower root cost,\n
56
00:05:04,540 --> 00:05:12,410
So, SW2’s G0/1 and SW4’s F0/2 will be\n
57
00:05:12,410 --> 00:05:16,580
These ports connected to the end hosts should\n
58
00:05:19,459 --> 00:05:22,419
Now let’s quickly confirm on each switch.
59
00:05:22,420 --> 00:05:26,890
We already saw SW1, so I’ll go on SW2.
60
00:05:31,420 --> 00:05:40,900
F0/1 is the root, F0/2 is designated, G0/1\n
61
00:05:49,439 --> 00:05:55,269
F0/2 is the root port, G0/1 is designated,\nand so is F0/1.
62
00:05:55,269 --> 00:05:58,870
F0/24, connected to the PC, is also designated.
63
00:06:08,560 --> 00:06:14,100
F0/1 is the root port, F0/2 is alternate,\n
64
00:06:14,100 --> 00:06:16,879
Okay, looks like we got it all correct.
65
00:06:16,879 --> 00:06:23,629
Finally, let’s manually configure the appropriate\n
66
00:06:23,629 --> 00:06:28,740
The one I really want to show is SW1’s F0/24,\n
67
00:06:30,970 --> 00:06:38,500
CONF T. Let’s configure F0/1 and 2 as point-to-point\n
68
00:06:38,500 --> 00:06:43,199
to switches, they are operating in full duplex\nmode.
69
00:06:47,240 --> 00:06:50,699
SPANNING-TREE LINK-TYPE POINT-TO-POINT.
70
00:06:50,699 --> 00:06:56,319
Next, I’ll configure F0/24 as an edge port\nby enabling portfast.
71
00:07:05,360 --> 00:07:09,860
Okay, F0/1 and 2 are point to point, which\nis correct.
72
00:07:09,860 --> 00:07:14,050
Actually, they were already point to point\n
73
00:07:18,829 --> 00:07:21,180
It still has the default type of point to\npoint.
74
00:07:21,180 --> 00:07:25,610
Well, this is something I didn’t explain\nin the lecture.
75
00:07:25,610 --> 00:07:30,180
Edge ports connected to an end host like this\n
76
00:07:32,339 --> 00:07:37,500
There is no hub here, therefore the link is\n
77
00:07:40,620 --> 00:07:44,720
It doesn’t work in packet tracer, but if\n
78
00:07:44,720 --> 00:07:50,800
on a port on a real switch, it will display\n
79
00:07:52,529 --> 00:07:57,339
Point to point means it is full duplex, edge\n
80
00:07:57,339 --> 00:08:01,569
So, it’s both an edge port and a point to\npoint port.
81
00:08:05,680 --> 00:08:12,280
F0/1, and G0/1 should be point to point, however\n
82
00:08:13,279 --> 00:08:16,529
Actually, let’s check before we configure\nit.
83
00:08:19,259 --> 00:08:23,500
As you can see, the switch automatically sets\n
84
00:08:23,500 --> 00:08:28,389
So really, the only one we HAVE to configure\n
85
00:08:30,129 --> 00:08:33,299
For the sake of time, let’s just do that.
86
00:08:42,759 --> 00:08:48,080
Let’s check first again, all ports are using\n
87
00:08:52,230 --> 00:08:55,180
Indeed, all ports are point to point.
88
00:08:55,179 --> 00:09:00,899
Again, for time, I’ll just enable portfast\non F0/23 and 24.
89
00:09:00,899 --> 00:09:06,769
CONF T. INTERFACE RANGE F0/23 to 24.
90
00:09:12,190 --> 00:09:15,180
In this case, it has three ports connected\nto a hub.
91
00:09:15,179 --> 00:09:18,089
These should all be shared by default.
92
00:09:18,090 --> 00:09:20,330
Only F0/1 should be point to point.
93
00:09:24,649 --> 00:09:28,740
As expected, F0/2, 3, and 24 are shared.
94
00:09:28,740 --> 00:09:34,529
So, F0/24 is connected to a hub, but there\n
95
00:09:36,639 --> 00:09:41,899
The answer is yes, the hub basically doesn’t\n
96
00:09:41,899 --> 00:09:44,470
than if it were connected to a switch here.
97
00:09:44,470 --> 00:09:50,690
So, F0/24 is an edge port, AND a shared port,\n
98
00:09:50,690 --> 00:09:54,280
to point links connected to end hosts on the\nother switches.
99
00:10:07,179 --> 00:10:12,839
Okay, so just like before, in packet tracer\n
100
00:10:12,840 --> 00:10:19,080
it will display both edge and shared here\n
101
00:10:19,080 --> 00:10:24,110
Point to point and shared distinguish between\n
102
00:10:25,600 --> 00:10:30,570
Okay, that’s all for this lab, I hoped this\n
103
00:10:31,580 --> 00:10:36,680
Next, let’s take a look at a lab in Boson\nNetSim.
104
00:10:36,679 --> 00:10:43,429
Okay, for today's Boson NetSim lab preview\n
105
00:10:44,659 --> 00:10:50,329
I said this before, but that's because spanning\n
106
00:10:50,330 --> 00:10:55,430
exam topics list so Boson doesn't include\nit in NetSim for CCNA.
107
00:10:55,429 --> 00:11:00,500
But I just want to show you one of the spanning\n
108
00:11:02,299 --> 00:11:05,309
I've already loaded the lab so click on 'lab\ninstructions'.
109
00:11:07,740 --> 00:11:14,210
So, there is one router and three switches\nand two PCs.
110
00:11:14,210 --> 00:11:18,480
Here's a list of the commands you need to\n
111
00:11:18,480 --> 00:11:23,200
IP addresses on the device, and the lab tasks\nthemselves.
112
00:11:23,200 --> 00:11:27,290
So, this lab demonstrates something I really\n
113
00:11:27,289 --> 00:11:31,759
Although this is a lab focused on spanning\n
114
00:11:34,960 --> 00:11:42,629
Task 1 is configure VLANs, so you'll be configuring\n
115
00:11:46,159 --> 00:11:51,100
Task 2 is configure the router, so configure\n
116
00:11:51,100 --> 00:11:59,240
VLAN 3, verify connectivity, and then finally\n
117
00:11:59,240 --> 00:12:03,820
So I think this is great because you not only\n
118
00:12:03,820 --> 00:12:09,379
but also review things you've already studied\n
119
00:12:12,528 --> 00:12:16,399
This isn't actually about spanning tree, but\n
120
00:12:16,399 --> 00:12:22,220
So, verify that the current IP configurations\n
121
00:12:22,220 --> 00:12:25,820
listed in the IP addresses table.
122
00:12:25,820 --> 00:12:28,800
Here is the table, PC1 and PC2.
123
00:12:28,799 --> 00:12:32,729
They are in the same subnet, they should have\n
124
00:12:38,940 --> 00:12:45,390
So, to get to the CLI of these PCs, click\n
125
00:12:45,389 --> 00:12:48,809
Alright, so I have PC1 and PC2.
126
00:12:50,370 --> 00:12:54,539
How do you check the IP address on a PC, or\n
127
00:12:58,259 --> 00:13:05,220
Okay, IP address .101 looks good, /24 mask,\n
128
00:13:10,799 --> 00:13:15,219
.102, /24, default gateway is .1.
129
00:13:15,220 --> 00:13:22,080
Okay, so both PC1 and PC2 have the correct\nconfiguration.
130
00:13:22,080 --> 00:13:26,020
Task 2, verify the connectivity by pinging\nfrom PC1 to PC2.
131
00:13:35,340 --> 00:13:38,440
Okay, looks good, the ping goes through.
132
00:13:38,440 --> 00:13:44,600
Okay, so step 3, configure Switch1 with the\n
133
00:13:44,600 --> 00:13:50,110
Okay, so I'll open up the CLI of Switch1.
134
00:13:54,460 --> 00:13:57,660
There we go, the host name has changed.
135
00:13:57,659 --> 00:14:07,350
Next, configure FastEthernet ports 0/1, 2,\n
136
00:14:10,710 --> 00:14:16,269
Okay, so all three of these are trunk ports,\n
137
00:14:16,269 --> 00:14:21,399
And we have to manually create VLAN 3 because\n
138
00:14:22,860 --> 00:14:27,539
It won't be manually, or sorry not manually,\n
139
00:14:30,070 --> 00:14:32,550
So first let's make those trunk ports.
140
00:14:36,690 --> 00:14:41,050
Now I don't know if on this switch model I\n
141
00:14:44,240 --> 00:14:46,278
Let's just try to set it to a trunk first.
142
00:14:46,278 --> 00:14:51,789
Okay, we don't, so this switch only supports\n
143
00:14:51,789 --> 00:14:55,009
common on most switches these days.
144
00:14:55,009 --> 00:14:59,870
Okay, next, right, create VLAN 3.
145
00:15:02,169 --> 00:15:03,469
And let's check that it was created.
146
00:15:13,580 --> 00:15:20,370
Configure Switch2 with the appropriate host\n
147
00:15:22,919 --> 00:15:28,409
And then FastEthernet ports 1 and 2, we must\n
148
00:15:32,529 --> 00:15:39,209
So, I'm going to just assign FastEthernet4\n
149
00:15:44,690 --> 00:15:49,910
DO SHOW...Oh, I am on Switch1 at the moment,\nthat's the problem.
150
00:15:49,909 --> 00:15:54,789
So, we do not need this configuration, I'll\n
151
00:15:54,789 --> 00:15:59,740
So let's go on to the CLI of Switch2 and let's\ntry that again.
152
00:15:59,740 --> 00:16:03,100
CONF T. Ah right, first the host name.
153
00:16:21,720 --> 00:16:27,879
Okay, so VLAN 3 was created and FastEthernet0/4\n
154
00:16:27,889 --> 00:16:32,059
Okay, next let's make these two interfaces\ntrunk ports.
155
00:16:40,490 --> 00:16:43,549
So I'm guessing the next step is Switch3.
156
00:16:47,100 --> 00:16:55,360
Okay, configure Switch3 with the appropriate\n
157
00:16:56,389 --> 00:17:00,600
And configure FastEthernet0/1 and 0/3 as trunk\nports.
158
00:17:00,600 --> 00:17:05,360
And then try another ping from PC1 to PC2,\nokay.
159
00:17:05,359 --> 00:17:09,479
So first I will assign this interface to VLAN\n3.
160
00:17:09,480 --> 00:17:11,440
Let's open the CLI of Switch3.
161
00:17:19,259 --> 00:17:20,439
Let's check that it was created.
162
00:17:24,900 --> 00:17:32,480
Next, so this time it's not FastEthernet0/1\n
163
00:17:32,480 --> 00:17:36,059
So I have to enter the INTERFACE RANGE command\n
164
00:17:36,059 --> 00:17:42,899
INTERFACE RANGE f0/1 comma f0/3.
165
00:17:43,900 --> 00:17:50,610
If I did like I did before, 0/1 to 0/3, that\n
166
00:17:56,029 --> 00:18:00,809
Okay, so now all of these interfaces between\n
167
00:18:02,849 --> 00:18:09,889
The interface going to the router is a trunk\n
168
00:18:10,890 --> 00:18:12,650
So, the ping should go through.
169
00:18:20,039 --> 00:18:25,379
As we saw before, task 2 you would configure\n
170
00:18:25,380 --> 00:18:27,100
what's going on with spanning tree.
171
00:18:27,099 --> 00:18:34,990
So, when you have completed the lab, I haven't\n
172
00:18:34,990 --> 00:18:36,500
your work using the grading function.
173
00:18:38,380 --> 00:18:42,840
Click on it and it evaluates how you did on\nthe lab.
174
00:18:42,839 --> 00:18:46,799
So, as you can see I missed one or more commands\n
175
00:18:47,799 --> 00:18:52,279
However, notice Switch1 has a checkmark, so\n
176
00:18:54,440 --> 00:19:00,200
These three interfaces are trunks, and VLAN\n3 was created.
177
00:19:00,200 --> 00:19:04,860
If you ever have any trouble during the lab\n
178
00:19:04,859 --> 00:19:11,469
gives you sample outputs, shows you all the\n
179
00:19:11,470 --> 00:19:14,360
detailed explanations like this.
180
00:19:14,359 --> 00:19:19,599
So I really think Boson's NetSim is a great\n
181
00:19:19,599 --> 00:19:22,869
If you want to get a copy, please follow the\n
182
00:19:23,920 --> 00:19:28,380
I used it for my certifications and it really\nis a great tool.
183
00:19:29,960 --> 00:19:33,860
Please subscribe to the channel, like the\n
184
00:19:33,859 --> 00:19:37,199
with anyone else studying for the CCNA.
185
00:19:37,200 --> 00:19:40,410
If you want to leave a tip, check the links\nin the description.
186
00:19:40,410 --> 00:19:45,759
I'm also a Brave verified publisher and accept\n
15197
Can't find what you're looking for?
Get subtitles in any language from opensubtitles.com, and translate them here.