Would you like to inspect the original subtitles? These are the user uploaded subtitles that are being translated:
1
00:00:03,399 --> 00:00:06,620
This is a free, complete course for the CCNA.
2
00:00:06,620 --> 00:00:10,339
If you like these videos, please subscribe\n
3
00:00:10,339 --> 00:00:15,120
Also, please like and leave a comment, and\n
4
00:00:18,350 --> 00:00:21,800
In this video we will look at another topic,\nEtherChannel.
5
00:00:21,800 --> 00:00:27,300
EtherChannel allows you to group multiple\n
6
00:00:27,300 --> 00:00:33,299
as a single logical interface, so they behave\n
7
00:00:33,299 --> 00:00:37,259
There are many benefits to this, and I’ll\n
8
00:00:37,259 --> 00:00:42,748
By the way, this video covers topic 2.4 of\n
9
00:00:42,749 --> 00:00:48,588
that you must be able to configure and verify\n
10
00:00:48,588 --> 00:00:53,358
called LACP, Link Aggregation Control Protocol.
11
00:00:53,359 --> 00:00:57,370
So, what will we cover in this video?
12
00:00:57,369 --> 00:01:01,378
First off, I’ll show you what EtherChannel\n
13
00:01:01,378 --> 00:01:05,469
Here’s a hint, spanning tree protocol is\nthe big problem.
14
00:01:05,469 --> 00:01:11,730
We will also look at multiple methods of configuring\n
15
00:01:11,730 --> 00:01:17,260
A Layer 2 etherchannel is a group of switch\n
16
00:01:17,260 --> 00:01:22,580
and a Layer 3 etherchannel is a group of routed\n
17
00:01:22,579 --> 00:01:26,980
which you assign an IP address to, because\nit’s Layer 3.
18
00:01:26,980 --> 00:01:31,530
Make sure you watch until the end of the video\n
19
00:01:31,530 --> 00:01:35,590
ExSim, the best practice exams for the CCNA.
20
00:01:35,590 --> 00:01:41,420
I used Boson ExSim to help me prepare for\n
21
00:01:41,420 --> 00:01:45,159
it was the key that allowed me to pass\n
22
00:01:45,159 --> 00:01:48,340
Okay, let’s get started with the video.
23
00:01:48,340 --> 00:01:51,870
So, let me demonstrate a problem.
24
00:01:51,870 --> 00:01:55,359
We have two switches here, ASW1 and DSW1.
25
00:01:55,359 --> 00:02:03,408
I will talk about basic network design later\n
26
00:02:03,409 --> 00:02:07,630
which is a switch that end hosts like PCs\n
27
00:02:07,629 --> 00:02:13,150
DSW stands for distribution layer switch,\n
28
00:02:15,009 --> 00:02:20,158
For this demonstration, let’s say there\n
29
00:02:20,158 --> 00:02:25,578
say 40 hosts, and they are all trying to access\n
30
00:02:25,579 --> 00:02:31,120
The network administrator notices that the\n
31
00:02:31,120 --> 00:02:35,408
that he should add another link to increase\n
32
00:02:36,879 --> 00:02:42,128
So, the network admin adds another link, and\n
33
00:02:42,128 --> 00:02:45,719
However, the additional link doesn’t seem\nto help.
34
00:02:45,719 --> 00:02:52,419
The connection between ASW1 and DSW1 is still\n
35
00:02:52,419 --> 00:02:58,888
So, the admin decides to add another link\nbetween ASW1 and DSW1.
36
00:02:58,889 --> 00:03:02,939
He adds another link to the connection between\nASW1 and DSW1.
37
00:03:02,938 --> 00:03:05,889
Surely, this will be sufficient.
38
00:03:05,889 --> 00:03:09,759
The total bandwidth of the connections to\n
39
00:03:09,759 --> 00:03:15,328
of the connection to DSW1, but that’s okay,\n
40
00:03:15,329 --> 00:03:18,519
a constant state of sending and receiving\nInternet traffic.
41
00:03:18,519 --> 00:03:24,069
I will talk more about this later in the course,\n
42
00:03:24,068 --> 00:03:29,539
to end hosts is greater than the bandwidth\n
43
00:03:29,539 --> 00:03:32,729
this is called oversubscription.
44
00:03:32,729 --> 00:03:37,488
Some oversubscription is acceptable, but too\n
45
00:03:37,489 --> 00:03:43,730
However, even with three links to DSW1 the\n
46
00:03:43,729 --> 00:03:49,798
network admin once again decides to add another\n
47
00:03:49,799 --> 00:03:55,419
So, now there are four links between ASW1\nand DSW1.
48
00:03:55,419 --> 00:03:56,870
Do you think things have improved?
49
00:03:56,870 --> 00:04:03,139
Well, they haven’t, the connection between\n
50
00:04:04,680 --> 00:04:06,580
You should be able to figure out the answer.
51
00:04:06,580 --> 00:04:13,419
Here’s a hint, think about what you just\n
52
00:04:13,419 --> 00:04:17,660
If you know the answer, well done, if not\n
53
00:04:17,660 --> 00:04:23,750
Let’s say the administrator went to physically\n
54
00:04:23,750 --> 00:04:25,220
What color do you think they were?
55
00:04:25,220 --> 00:04:30,740
Well, the network admin checks DSW1 and all\n
56
00:04:32,389 --> 00:04:38,849
However, when he checks ASW1 he notices that,\n
57
00:04:38,850 --> 00:04:41,320
is green, and the others are orange.
58
00:04:42,410 --> 00:04:48,530
It’s because of what we studied in the past\n
59
00:04:48,529 --> 00:04:53,419
If you connect two switches together with\n
60
00:04:56,730 --> 00:05:02,900
Well, if all of ASW1’s interfaces were forwarding,\n
61
00:05:02,899 --> 00:05:07,219
DSW1, leading to broadcast storms.
62
00:05:07,220 --> 00:05:10,700
Other links will be unused unless the active\nlink fails.
63
00:05:10,699 --> 00:05:13,949
In that case, one of the inactive links will\nstart forwarding.
64
00:05:13,949 --> 00:05:19,000
So, although having backup links is a good\n
65
00:05:19,000 --> 00:05:23,939
reasons, it’s a waste of bandwidth to have\n
66
00:05:25,379 --> 00:05:31,259
However, by forming these four physical interfaces\n
67
00:05:31,259 --> 00:05:38,550
solve this problem, giving us both redundancy\n
68
00:05:38,550 --> 00:05:43,170
An EtherChannel is represented in network\n
69
00:05:43,170 --> 00:05:45,460
that are grouped together, like this.
70
00:05:45,459 --> 00:05:51,389
EtherChannel groups multiple interfaces together\n
71
00:05:51,389 --> 00:05:55,120
STP will treat this group as a single interface.
72
00:05:55,120 --> 00:05:59,769
So, after grouping these interfaces into an\n
73
00:06:03,589 --> 00:06:06,769
Won’t this cause a Layer 2 loop?
74
00:06:06,769 --> 00:06:13,419
Actually no, because this group of four links\n
75
00:06:13,420 --> 00:06:17,160
For example, let’s say a PC sends a broadcast\nframe.
76
00:06:17,160 --> 00:06:22,080
So, it is flooded out all interfaces on ASW1.
77
00:06:22,079 --> 00:06:26,000
All of the PCs connected to ASW1 will receive\n
78
00:06:26,000 --> 00:06:29,920
Now, how many copies of the frame will DSW1\nreceive?
79
00:06:29,920 --> 00:06:36,500
Remember, although there are four physical\n
80
00:06:36,500 --> 00:06:41,009
The answer is, DSW1 will only receive one\ncopy.
81
00:06:41,009 --> 00:06:46,659
This EtherChannel makes these four physical\n
82
00:06:46,660 --> 00:06:52,340
won’t sent four copies of the same broadcast\n
83
00:06:52,339 --> 00:06:56,030
Traffic using the EtherChannel will be load\n
84
00:06:57,480 --> 00:07:01,400
An algorithm is used to determine which traffic\n
85
00:07:01,399 --> 00:07:04,389
I will give you more details on this later.
86
00:07:04,389 --> 00:07:08,339
So, DSW1 received the broadcast frame.
87
00:07:10,060 --> 00:07:14,269
It will flood the broadcast frame out of all\n
88
00:07:15,810 --> 00:07:19,300
So let’s say DSW1 has these two other links\nhere.
89
00:07:19,300 --> 00:07:23,300
Which interfaces will DSW1 forward the frame\nout of?
90
00:07:25,259 --> 00:07:29,230
Why didn’t it forward the frame out of the\n
91
00:07:29,230 --> 00:07:34,810
I’ll repeat it once more, although this\n
92
00:07:34,810 --> 00:07:37,959
interfaces, they behave as a single interface.
93
00:07:37,959 --> 00:07:42,370
DSW1 won’t send the broadcast frame back\n
94
00:07:43,370 --> 00:07:48,160
So it isn’t forwarded back to ASW1, and\n
95
00:07:48,160 --> 00:07:54,600
It’s kind of like this, instead of four\n
96
00:07:54,600 --> 00:08:00,129
interfaces, connecting ASW1 to DSW1, it’s\n
97
00:08:01,740 --> 00:08:06,939
The bandwidth of the four separate interfaces\n
98
00:08:06,939 --> 00:08:10,779
a virtual four-gigabit interface.
99
00:08:10,779 --> 00:08:15,679
The difference between the physical characteristics\n
100
00:08:15,680 --> 00:08:20,420
of a network are something you need to understand\n
101
00:08:23,350 --> 00:08:29,129
Multiple PCs can all be connected to the same\n
102
00:08:29,129 --> 00:08:35,189
VLANs virtually divide these PCs into separate\n
103
00:08:36,679 --> 00:08:43,089
Likewise, these interfaces exist as four separate\n
104
00:08:45,690 --> 00:08:51,230
Some other names for an EtherChannel are a\n
105
00:08:52,759 --> 00:08:58,389
You’ll see that, to configure an etherchannel\n
106
00:09:00,870 --> 00:09:04,500
Now let’s take a look at how etherchannel\nload balances.
107
00:09:04,500 --> 00:09:07,450
It load balances based on ‘flows’.
108
00:09:08,820 --> 00:09:12,830
A flow is a communication between two nodes\nin the network.
109
00:09:12,830 --> 00:09:16,879
So for example, between PC1 and SRV1.
110
00:09:16,879 --> 00:09:21,210
By the way, you usually won’t see a server\n
111
00:09:21,210 --> 00:09:27,810
layer switch, these are also end hosts which\n
112
00:09:27,809 --> 00:09:31,059
Just to simplify this network diagram I’ll\n
113
00:09:31,059 --> 00:09:36,959
So, let’s say PC1 initiates an exchange\n
114
00:09:38,809 --> 00:09:44,759
The frame is received by ASW1, and assuming\n
115
00:09:44,759 --> 00:09:48,169
it will forward the frame out of the port\nchannel to DSW1.
116
00:09:48,169 --> 00:09:51,849
However, which physical interface will it\nuse?
117
00:09:51,850 --> 00:09:56,300
Well, there is an algorithm it uses to calculate\n
118
00:09:56,299 --> 00:10:01,139
actually be sent on, let’s say it determines\n
119
00:10:01,139 --> 00:10:07,330
Now, when PC1 sends the next frame in the\n
120
00:10:07,330 --> 00:10:11,879
SRV1, the same interface will be used to forward\n
121
00:10:11,879 --> 00:10:17,259
So, the point is that frames in the same flow\n
122
00:10:18,620 --> 00:10:22,791
If frames in the same flow were forwarded\n
123
00:10:22,791 --> 00:10:28,230
frames may arrive at the destination out of\n
124
00:10:28,230 --> 00:10:32,950
Some applications can deal with frames arriving\n
125
00:10:32,950 --> 00:10:40,800
Now, if PC1 wants to print something and initiates\n
126
00:10:40,799 --> 00:10:44,889
will once again forward the frame using its\n
127
00:10:44,889 --> 00:10:49,199
However, it will make a separate calculation\n
128
00:10:51,269 --> 00:10:55,870
For example, it might determine that this\n
129
00:10:55,870 --> 00:11:00,990
Just like before, when PC1 sends another frame\n
130
00:11:00,990 --> 00:11:04,220
the etherchannel will be used to forward it.
131
00:11:04,220 --> 00:11:07,649
How about if PC2 also wants to print something?
132
00:11:07,649 --> 00:11:12,459
It sends the first frame in the flow to ASW1,\n
133
00:11:12,460 --> 00:11:15,650
which physical interface in the etherchannel\nwill be used.
134
00:11:17,539 --> 00:11:23,338
So, this is how EtherChannel performs load\n
135
00:11:23,339 --> 00:11:26,380
in the etherchannel for different flows.
136
00:11:26,379 --> 00:11:30,480
The calculation that is done to determine\n
137
00:11:32,299 --> 00:11:37,809
Actually, you can change the inputs used in\n
138
00:11:37,809 --> 00:11:40,169
Here are the inputs that can be used.
139
00:11:41,769 --> 00:11:46,799
So, all frames with the same source MAC address\n
140
00:11:51,278 --> 00:11:56,519
In this case, all frames with the same destination\n
141
00:11:57,980 --> 00:12:02,159
You can also use both the source AND destination\nMAC addresses.
142
00:12:02,159 --> 00:12:08,519
So for example, frames from PC1 to SRV1 will\n
143
00:12:08,519 --> 00:12:14,149
from PC2 to SRV1 will always use a certain\n
144
00:12:14,149 --> 00:12:20,500
than the one used for traffic from PC1 to\n
145
00:12:23,049 --> 00:12:28,949
The calculation is done based on both the\n
146
00:12:28,950 --> 00:12:34,230
You can also configure etherchannel to select\n
147
00:12:34,230 --> 00:12:40,269
destination IP address, or both source AND\n
148
00:12:40,269 --> 00:12:46,509
Some switches also support load-balancing\n
149
00:12:46,509 --> 00:12:49,049
but those are a topic for another lesson.
150
00:12:49,049 --> 00:12:54,939
Also, which methods the switch can use depends\n
151
00:12:54,940 --> 00:13:00,620
using the MAC addresses, some may support\n
152
00:13:02,360 --> 00:13:08,019
So, we haven’t actually configured an etherchannel\n
153
00:13:08,019 --> 00:13:12,850
take a look at how to check and configure\n
154
00:13:12,850 --> 00:13:19,440
Use the command SHOW ETHERCHANNEL LOAD-BALANCE\n
155
00:13:19,440 --> 00:13:23,890
You can see the default for this model of\n
156
00:13:25,870 --> 00:13:34,230
So, for example, all traffic from 10.0.0.1\n
157
00:13:34,230 --> 00:13:38,460
use a certain physical interface within the\netherchannel.
158
00:13:38,460 --> 00:13:41,660
Down here you can see a more specific breakdown.
159
00:13:41,659 --> 00:13:47,829
Frames which encapsulate IP packets, whether\n
160
00:13:47,830 --> 00:13:50,810
on the source and destination IP addresses.
161
00:13:50,809 --> 00:13:56,809
However, notice at the top it says non-IP\n
162
00:13:56,809 --> 00:14:02,149
Well, that’s because if an IP packet isn’t\n
163
00:14:02,149 --> 00:14:07,179
is no IP address that can be used to determine\n
164
00:14:08,830 --> 00:14:14,230
Now, as for how to change the load-balancing\n
165
00:14:16,289 --> 00:14:20,860
PORT-CHANNEL LOAD-BALANCE, followed by the\nmethod.
166
00:14:20,860 --> 00:14:26,340
In this case I changed it to use the source\n
167
00:14:26,340 --> 00:14:30,470
Then I confirmed once more, and you can see\n
168
00:14:32,909 --> 00:14:36,299
By the way, here are the choices available\non this device.
169
00:14:36,299 --> 00:14:41,609
It can load-balance based on MAC or IP addresses,\n
170
00:14:41,610 --> 00:14:47,550
on either the source, the destination, or\n
171
00:14:47,549 --> 00:14:52,419
Now, I want to point out one thing which is\n
172
00:14:55,110 --> 00:14:59,139
What keyword do you use to configure the load-balancing method?
173
00:15:00,840 --> 00:15:05,019
And what keyword do you use to view the load-balancing\nmethod?
174
00:15:06,580 --> 00:15:10,500
Different words are used for the same thing,\n
175
00:15:10,500 --> 00:15:15,169
Actually, later you’ll find that there is\n
176
00:15:15,169 --> 00:15:19,419
So, these are the first two commands to remember\nfor this video.
177
00:15:19,419 --> 00:15:23,860
SHOW ETHERCHANNEL LOAD-BALANCE, to check the\n
178
00:15:23,860 --> 00:15:29,330
And, PORT-CHANNEL LOAD-BALANCE, followed by\n
179
00:15:32,360 --> 00:15:36,560
Now let’s get into actually creating an\n
180
00:15:36,559 --> 00:15:40,239
There are three methods of EtherChannel configuration.
181
00:15:40,240 --> 00:15:45,680
First up is PAgP, which stands for Port Aggregation\nProtocol.
182
00:15:45,679 --> 00:15:51,439
It is a Cisco proprietary protocol, so it\n
183
00:15:51,440 --> 00:15:55,480
If you’re trying to form an EtherChannel\n
184
00:15:59,879 --> 00:16:05,110
It dynamically negotiates the creation and\n
185
00:16:05,110 --> 00:16:11,169
Just a few days ago we covered DTP, which\n
186
00:16:11,169 --> 00:16:15,539
Frames are sent to the neighboring switch\n
187
00:16:15,539 --> 00:16:19,629
and then the switches agree upon either forming\n
188
00:16:19,629 --> 00:16:26,139
Okay, the next method of configuration is\n
189
00:16:27,690 --> 00:16:32,610
It is an industry standard protocol, once\n
190
00:16:34,789 --> 00:16:39,429
Basically, it does the same thing as PAgP.
191
00:16:39,429 --> 00:16:44,019
It dynamically negotiates the creation and\n
192
00:16:46,528 --> 00:16:51,850
Because it is an industry standard protocol,\n
193
00:16:51,850 --> 00:16:56,519
it can be used to form EtherChannels with\n
194
00:16:56,519 --> 00:17:01,149
Because of this, LACP is the preferred method\n
195
00:17:01,149 --> 00:17:05,509
Actually, the exam topics list only states\nLACP.
196
00:17:05,509 --> 00:17:10,470
However, for the test you really should be\n
197
00:17:10,470 --> 00:17:14,959
reason Cisco’s exam topics lists aren’t\nvery reliable.
198
00:17:14,959 --> 00:17:19,049
So, the last method is static EtherChannel.
199
00:17:19,049 --> 00:17:24,129
In this case a protocol isn’t used to determine\n
200
00:17:24,130 --> 00:17:28,830
Instead, interfaces are statically configured\n
201
00:17:28,829 --> 00:17:34,259
This is usually avoided, because you want\n
202
00:17:34,259 --> 00:17:38,039
for example you want the switch to remove\n
203
00:17:38,039 --> 00:17:40,659
is some sort of problem on the interface.
204
00:17:40,660 --> 00:17:46,509
Okay, finally, up to 8 interfaces can be formed\n
205
00:17:46,509 --> 00:17:53,808
Actually, LACP allows up to 16, but only 8\n
206
00:17:53,808 --> 00:17:58,149
mode, waiting for an active interface to fail.
207
00:17:58,150 --> 00:18:01,330
So let’s look into how to configure each\nmethod.
208
00:18:01,329 --> 00:18:07,159
The configuration for each is almost identical,\n
209
00:18:07,160 --> 00:18:11,320
First I used the interface range command to\n
210
00:18:12,920 --> 00:18:17,000
This is a good idea for EtherChannel, because\n
211
00:18:17,000 --> 00:18:21,299
must match, so if you configure them all at\n
212
00:18:21,299 --> 00:18:24,960
I’ll talk more about that after I show you\nthe configurations.
213
00:18:24,960 --> 00:18:31,500
Anyway, to actually configure the EtherChannel\n
214
00:18:31,500 --> 00:18:37,849
CHANNEL-GROUP, followed by a number that identifies\n
215
00:18:37,849 --> 00:18:41,719
can see I used the question mark to see what\noptions there are.
216
00:18:41,720 --> 00:18:48,809
There are five options, two of them are used\n
217
00:18:53,779 --> 00:18:57,700
Do you recognize these names from another\n
218
00:18:57,700 --> 00:19:03,509
DTP used the same modes to form trunks, and\n
219
00:19:05,349 --> 00:19:10,889
Desirable mode actively tries to form an EtherChannel,\n
220
00:19:10,890 --> 00:19:16,710
if the other side is set to desirable, but\n
221
00:19:18,480 --> 00:19:23,380
If both sides of the connection are set to\n
222
00:19:23,380 --> 00:19:29,390
However, auto and desirable, or desirable\n
223
00:19:29,390 --> 00:19:33,720
Anyway, I decided to configure this side as\ndesirable.
224
00:19:33,720 --> 00:19:38,000
You can see that the virtual port-channel\n
225
00:19:38,000 --> 00:19:40,960
used in the channel-group command.
226
00:19:40,960 --> 00:19:46,450
You can see it here in the output of the SHOW\n
227
00:19:46,450 --> 00:19:52,120
So, remember that the CHANNEL-GROUP command\n
228
00:19:52,119 --> 00:19:56,889
the name of the virtual interface that is\n
229
00:19:56,890 --> 00:20:02,350
By the way, this channel group number has\n
230
00:20:02,349 --> 00:20:06,869
however it DOESN’T have to match the channel-group\n
231
00:20:06,869 --> 00:20:14,469
For example, channel-group 1 on ASW1 can form\n
232
00:20:14,470 --> 00:20:20,110
The number is just used to identify the virtual\n
233
00:20:20,109 --> 00:20:23,959
Because you can have multiple etherchannels\n
234
00:20:27,269 --> 00:20:31,000
Next let’s look at LACP configuration.
235
00:20:31,000 --> 00:20:36,109
After explaining all of that, there’s not\n
236
00:20:36,109 --> 00:20:39,019
Just notice that mode names are different.
237
00:20:39,019 --> 00:20:43,170
Instead of desirable, LACP uses active mode.
238
00:20:43,170 --> 00:20:46,690
And instead of auto, LACP uses passive mode.
239
00:20:46,690 --> 00:20:52,130
So, if both ends are configured in passive\n
240
00:20:52,130 --> 00:20:58,400
However, active and passive, or active and\n
241
00:20:58,400 --> 00:21:02,240
In this case, I configured this side as active.
242
00:21:02,240 --> 00:21:05,620
Once again, the port-channel interface is\ncreated.
243
00:21:05,619 --> 00:21:10,089
Note that, even if you configure both sides\n
244
00:21:12,289 --> 00:21:16,928
However, it won’t actually be functioning\n
245
00:21:18,160 --> 00:21:24,160
So, as you can see the command is basically\n
246
00:21:24,160 --> 00:21:28,460
Once again, the channel-group number has to\n
247
00:21:28,460 --> 00:21:32,590
switch, but it doesn’t have to match the\n
248
00:21:32,589 --> 00:21:37,459
Finally, let’s see how static EtherChannel\nis configured.
249
00:21:37,460 --> 00:21:42,370
There aren’t two separate modes, just one,\n
250
00:21:45,049 --> 00:21:48,879
This will create a port-channel interface,\njust like before.
251
00:21:48,880 --> 00:21:52,470
By the way, on mode only works with on mode.
252
00:21:52,470 --> 00:21:59,829
On and desirable, or on and active will not\n
253
00:21:59,829 --> 00:22:03,399
Another command you should know is the CHANNEL-PROTOCOL command.
254
00:22:03,400 --> 00:22:07,940
This manually configures the EtherChannel\n
255
00:22:09,309 --> 00:22:14,789
This actually isn’t a very useful command,\n
256
00:22:14,789 --> 00:22:20,129
If you configure CHANNEL-GROUP 1 MODE DESIRABLE\n
257
00:22:20,130 --> 00:22:27,250
use PAgP, or if you configure CHANNEL-GROUP\n
258
00:22:29,069 --> 00:22:32,629
So, there isn’t really a point in using\nthis command.
259
00:22:32,630 --> 00:22:38,130
However, I think you should know it for the\n
260
00:22:38,130 --> 00:22:45,650
Of course there are two options, LACP and\n
261
00:22:45,650 --> 00:22:50,820
Then I tried the CHANNEL-GROUP 1 MODE DESIRABLE\n
262
00:22:52,160 --> 00:22:59,050
I manually configured these interfaces to\n
263
00:23:01,569 --> 00:23:06,579
If I try CHANNEL-GROUP 1 MODE ON it is rejected\nas well.
264
00:23:06,579 --> 00:23:11,799
Then I do CHANNEL-GROUP 1 MODE ACTIVE, and\n
265
00:23:13,450 --> 00:23:21,059
So, after configuring the EtherChannel, in\n
266
00:23:21,059 --> 00:23:24,849
can then configure the port-channel interface\nitself.
267
00:23:24,849 --> 00:23:29,109
Note that I’m just using the LACP example\n
268
00:23:29,109 --> 00:23:32,119
same regardless of which method you use.
269
00:23:32,119 --> 00:23:38,779
I also did the same configurations over on\n
270
00:23:38,779 --> 00:23:46,160
I entered interface config mode for the port-channel\n
271
00:23:46,160 --> 00:23:52,240
Now in the output of SHOW INTERFACES TRUNK,\n
272
00:23:54,359 --> 00:23:59,149
Notice that the individual physical interfaces\n
273
00:24:00,150 --> 00:24:04,009
Here’s a section of the output of SHOW RUNNING-CONFIG.
274
00:24:04,009 --> 00:24:06,929
There’s something interesting to notice\nhere.
275
00:24:06,929 --> 00:24:11,890
The trunk configurations that I configured\n
276
00:24:11,890 --> 00:24:17,750
to the physical interfaces, I didn’t manually\n
277
00:24:17,750 --> 00:24:23,220
Now, one more important point about EtherChannel\nconfiguration.
278
00:24:23,220 --> 00:24:29,690
Member interfaces, the physical interfaces\n
279
00:24:31,650 --> 00:24:33,850
They must have the same duplex setting.
280
00:24:33,849 --> 00:24:36,839
They must have the same speed.
281
00:24:36,839 --> 00:24:41,038
They must have the same switchport mode, meaning\n
282
00:24:41,038 --> 00:24:45,839
If they are a trunk, they must have the same\n
283
00:24:45,839 --> 00:24:50,879
If an individual interface’s configurations\n
284
00:24:54,099 --> 00:24:58,549
When it comes to verifying the status of an\n
285
00:24:58,549 --> 00:25:02,339
useful command is SHOW ETHERCHANNEL SUMMARY.
286
00:25:02,339 --> 00:25:06,759
Down here is a list of the port-channel interfaces\n
287
00:25:06,759 --> 00:25:13,359
Next to port-channel 1 it has two flags, an\n
288
00:25:13,359 --> 00:25:16,869
To check the meaning of these, look at the\nlegend up top.
289
00:25:16,869 --> 00:25:20,079
S means it is a Layer 2 etherchannel.
290
00:25:20,079 --> 00:25:23,419
S stands for switchport, by the way.
291
00:25:23,420 --> 00:25:29,029
U means in use, meaning the EtherChannel is\n
292
00:25:29,029 --> 00:25:32,629
Next to the physical ports there is the flag\n‘P’.
293
00:25:32,630 --> 00:25:36,620
This means that these ports are properly bundled\n
294
00:25:36,619 --> 00:25:40,369
These are the flags you want to see in an\n
295
00:25:40,369 --> 00:25:45,789
Now, let’s take a look at a couple situations\n
296
00:25:45,789 --> 00:25:49,899
So, I shutdown the port-channel 1 interface.
297
00:25:49,900 --> 00:25:54,810
Now next to both the port-channel interface\n
298
00:25:57,569 --> 00:26:04,279
Okay, I’ll enable the interface again and\n
299
00:26:04,279 --> 00:26:08,470
Now I changed one of the member interfaces\nto access mode.
300
00:26:08,470 --> 00:26:11,620
Now it has the lower-case ‘s’ flag.
301
00:26:11,619 --> 00:26:14,529
Note that this is different than the upper-case\nS flag.
302
00:26:15,910 --> 00:26:22,980
So, only G0/0 is suspended, but the EtherChannel\n
303
00:26:27,609 --> 00:26:31,619
Another command you can use is SHOW ETHERCHANNEL PORT-CHANNEL.
304
00:26:31,619 --> 00:26:37,289
You can see the number of ports in the port-channel,\n
305
00:26:37,289 --> 00:26:41,808
One important bit of information that you\n
306
00:26:41,808 --> 00:26:47,599
but is displayed in this command is the channel-group\n
307
00:26:47,599 --> 00:26:50,859
the CHANNEL-GROUP 1 MODE ACTIVE command earlier.
308
00:26:50,859 --> 00:26:55,869
However, for EtherChannel the most common\n
309
00:26:57,339 --> 00:27:01,869
I just wanted to show you one other option.
310
00:27:01,869 --> 00:27:05,668
Because I started this video talking about\n
311
00:27:05,669 --> 00:27:08,460
when EtherChannel is configured.
312
00:27:08,460 --> 00:27:13,279
As you can see, only the port-channel interface\n
313
00:27:13,279 --> 00:27:15,690
appear in the output of this command at all.
314
00:27:15,690 --> 00:27:21,000
So, as I said earlier, spanning-tree is treating\n
315
00:27:23,529 --> 00:27:27,750
Instead of blocking three of them, they can\n
316
00:27:30,940 --> 00:27:35,509
To close off this lecture, let’s take a\n
317
00:27:35,509 --> 00:27:40,900
I’ve replaced ASW1 and DSW1 with multilayer\nswitches.
318
00:27:40,900 --> 00:27:45,950
Instead of a Layer 2 connection between them,\n
319
00:27:45,950 --> 00:27:50,970
Modern network design often leans toward using\n
320
00:27:50,970 --> 00:27:54,909
that way spanning-tree won’t be an issue\n
321
00:27:54,909 --> 00:27:59,059
We could have four switches interconnected\n
322
00:27:59,058 --> 00:28:04,220
with Layer 3 routed ports, all interfaces\n
323
00:28:04,220 --> 00:28:07,190
to be disabled due to spanning tree.
324
00:28:07,190 --> 00:28:11,169
Now you may be thinking, didn’t you just\n
325
00:28:11,169 --> 00:28:12,870
doesn’t have to block any ports?
326
00:28:12,869 --> 00:28:17,178
Well, we’re just looking at a connection\nbetween two switches.
327
00:28:17,179 --> 00:28:21,220
Even if we’re using EtherChannel, Layer\n
328
00:28:21,220 --> 00:28:24,038
are connected together in a loop.
329
00:28:24,038 --> 00:28:26,669
For example, look at this diagram.
330
00:28:26,669 --> 00:28:30,890
All of the connections between switches are\n
331
00:28:30,890 --> 00:28:36,059
any of the port-channel interfaces, broadcasts\n
332
00:28:36,058 --> 00:28:38,309
and cause a broadcast storm.
333
00:28:38,309 --> 00:28:42,308
So, spanning-tree will block one of these\n
334
00:28:42,308 --> 00:28:47,058
However, if all of these connections between\n
335
00:28:47,058 --> 00:28:52,058
Layer 2 switchports, there is no need to run\n
336
00:28:52,058 --> 00:28:57,960
Routed ports don’t forward Layer 2 broadcasts,\n
337
00:28:57,960 --> 00:29:01,548
You already know how to configure routed ports\n
338
00:29:01,548 --> 00:29:05,548
Let’s see how to configure a Layer 3 EtherChannel.
339
00:29:05,548 --> 00:29:10,190
So, starting from a clean configuration, no\n
340
00:29:11,349 --> 00:29:17,329
I enter interface range config mode for the\n
341
00:29:17,329 --> 00:29:24,199
the CHANNEL-GROUP command, I use the NO SWITCHPORT\n
342
00:29:24,200 --> 00:29:31,720
Then, after using the CHANNEL-GROUP command,\n
343
00:29:31,720 --> 00:29:35,620
Notice that the port-channel interface that\n
344
00:29:37,400 --> 00:29:43,000
Now, since we’re making a Layer 3 etherchannel,\n
345
00:29:43,000 --> 00:29:45,529
Where do you think it should be configured?
346
00:29:45,529 --> 00:29:48,230
It should be configured on the port-channel\ninterface.
347
00:29:49,679 --> 00:29:54,280
Now, let’s check the SHOW ETHERCHANNEL SUMMARY\n
348
00:29:54,279 --> 00:29:59,670
So, the only difference in the output is that\n
349
00:30:02,779 --> 00:30:08,730
It means it is a Layer 3 EtherChannel, R stands\nfor routed port.
350
00:30:08,730 --> 00:30:14,360
In the output of SHOW IP INTERFACE BRIEF,\n
351
00:30:15,359 --> 00:30:19,959
So, now ASW1 and DSW1 are like two routers\nconnected together.
352
00:30:19,960 --> 00:30:26,058
They are connected at Layer 3 and spanning-tree\n
353
00:30:26,058 --> 00:30:31,220
However, just like with the Layer 2 EtherChannel,\n
354
00:30:33,409 --> 00:30:38,309
Okay let’s quickly review the commands we\ncovered.
355
00:30:38,308 --> 00:30:43,240
First is PORT-CHANNEL LOAD-BALANCE, followed\n
356
00:30:43,240 --> 00:30:49,839
model, can involve MAC addresses, IP addresses,\n
357
00:30:49,839 --> 00:30:56,019
source, destination, or both source and destination\n
358
00:30:56,019 --> 00:31:00,519
interface is used to forward any specific\nflow of traffic.
359
00:31:00,519 --> 00:31:07,639
To view the current EtherChannel load-balancing\n
360
00:31:07,640 --> 00:31:12,220
To configure an interface to be part of an\n
361
00:31:12,220 --> 00:31:18,569
followed by the port-channel number, MODE,\n
362
00:31:22,349 --> 00:31:27,480
The most useful show command for EtherChannel\n
363
00:31:27,480 --> 00:31:32,230
summary of all of the EtherChannels on the\n
364
00:31:32,230 --> 00:31:36,870
One more show command you can use is SHOW\n
365
00:31:36,869 --> 00:31:42,379
some more detailed information about the port-channel\n
366
00:31:42,380 --> 00:31:44,670
Those are all of the commands we learned today.
367
00:31:44,670 --> 00:31:48,380
Of course, there are many more commands that\n
368
00:31:48,380 --> 00:31:51,630
deeper into the concept of EtherChannels.
369
00:31:51,630 --> 00:31:56,260
As long as you understand their basic purpose\n
370
00:31:56,259 --> 00:31:58,269
you should be good for the CCNA.
371
00:31:58,269 --> 00:32:02,668
Okay let’s go to today’s quiz.
372
00:32:02,669 --> 00:32:07,679
Watch until the end of the quiz for a bonus\n
373
00:32:07,679 --> 00:32:13,048
a doubt the best practice exams for the CCNA,\n
374
00:32:15,419 --> 00:32:19,940
Let’s go to question 1 of the quiz.
375
00:32:19,940 --> 00:32:24,410
Which of the following channel-group mode\n
376
00:32:43,990 --> 00:32:50,140
Pause the video to think about your answer.
377
00:32:53,440 --> 00:33:01,120
A, on – on, creates a static EtherChannel,\n
378
00:33:02,529 --> 00:33:07,028
C, desirable – auto, creates an EtherChannel\nusing PAgP.
379
00:33:07,028 --> 00:33:11,130
G, active – active, creates an EtherChannel\nusing LACP.
380
00:33:11,130 --> 00:33:15,299
So, A, C, and G are the correct answers.
381
00:33:15,298 --> 00:33:21,500
B, passive - passive won’t create an etherchannel\n
382
00:33:23,730 --> 00:33:28,610
Same for D, PAgP auto mode doesn’t actively\n
383
00:33:28,609 --> 00:33:35,199
E, active – desirable, and F, on – desirable,\n
384
00:33:35,200 --> 00:33:38,080
won’t result in a valid EtherChannel configuration.
385
00:33:41,829 --> 00:33:46,839
In the output of the show etherchannel summary\n
386
00:33:46,839 --> 00:33:50,720
in the EtherChannel you configured have the\n
387
00:33:52,019 --> 00:33:56,230
A, the interfaces are in LACP passive mode.
388
00:33:56,230 --> 00:33:59,900
B, the interfaces are bundled in the port-channel.
389
00:33:59,900 --> 00:34:05,570
C, the interfaces are paused until the other\n
390
00:34:05,569 --> 00:34:09,319
Or D, the etherchannel is a Layer 2 EtherChannel.
391
00:34:09,320 --> 00:34:14,700
Pause the video to think about your answer.
392
00:34:14,699 --> 00:34:19,230
The answer is B, the interfaces are bundled\nin the port-channel.
393
00:34:19,230 --> 00:34:23,369
This is the flag you want to see next to the\n
394
00:34:23,369 --> 00:34:27,619
Here’s some sample output of SHOW ETHERCHANNEL\nSUMMARY.
395
00:34:27,619 --> 00:34:31,160
As you can see, P means the port is bundled\nin the port-channel.
396
00:34:35,230 --> 00:34:40,030
Which of the following member interface parameters\n
397
00:34:49,250 --> 00:34:53,148
Or D, switchport mode, access or trunk.
398
00:34:53,148 --> 00:34:58,989
Pause the video to think about your answer.
399
00:34:58,989 --> 00:35:03,459
The answers are C, interface speed, and D,\nswitchport mode.
400
00:35:03,460 --> 00:35:08,240
These are two of the settings that have to\n
401
00:35:08,239 --> 00:35:13,889
A, interface ID, is unique to each interface,\n
402
00:35:13,889 --> 00:35:18,369
And even if you’re configuring a Layer 3\n
403
00:35:18,369 --> 00:35:24,069
have IP addresses, the IP address must be\n
404
00:35:24,070 --> 00:35:26,960
So B, IP address, is also incorrect.
405
00:35:26,960 --> 00:35:33,659
Okay, next let’s take a look at a question\n
406
00:35:33,659 --> 00:35:40,059
Okay, for today's Boson ExSim practice question\n
407
00:35:40,059 --> 00:35:42,759
And this is a really good question, quite\nchallenging.
408
00:35:44,760 --> 00:35:49,920
You issue the following commands on SwitchA\n
409
00:35:51,269 --> 00:35:53,349
First, INTERFACE PORT-CHANNEL 1.
410
00:35:53,349 --> 00:35:58,699
So, this isn't necessary but it creates the\n
411
00:36:00,409 --> 00:36:07,000
So this virtual port-channel exists, the interface\n
412
00:36:07,000 --> 00:36:10,210
made members of that virtual interface.
413
00:36:10,210 --> 00:36:16,809
Okay, then we enter the INTERFACE RANGE command\n
414
00:36:16,809 --> 00:36:22,608
We manually configure the channel protocol,\n
415
00:36:22,608 --> 00:36:25,559
And then finally we use the CHANNEL-GROUP\n1 MODE ON command.
416
00:36:25,559 --> 00:36:30,338
Now normally, as I showed you in this video,\n
417
00:36:30,338 --> 00:36:34,349
port-channel interface is automatically created,\n
418
00:36:37,639 --> 00:36:40,338
CHANNEL-PROTOCOL LACP, CHANNEL-GROUP 1 MODE\nON.
419
00:36:42,440 --> 00:36:46,619
Again, we create the virtual port-channel\ninterface beforehand.
420
00:36:46,619 --> 00:36:53,250
Enter interface range config mode for FastEthernet0/5 and 6, this
421
00:36:53,250 --> 00:36:58,420
protocol as PAgP, before once again doing\n
422
00:36:58,420 --> 00:37:02,800
So, which of the following statements is true\n
423
00:37:06,420 --> 00:37:12,389
A, a link is formed using LACP because it\n
424
00:37:12,389 --> 00:37:15,980
As you can see here, LACP was configured first.
425
00:37:18,679 --> 00:37:24,399
Okay, C, a link is formed using PAgP because\n
426
00:37:24,400 --> 00:37:28,050
So, it was configured here on SwitchB.
427
00:37:28,050 --> 00:37:31,800
And then D, a link is formed without an aggregation\nprotocol.
428
00:37:31,800 --> 00:37:36,450
So you see both of these switches used the\n
429
00:37:36,449 --> 00:37:40,599
This configure static protocol (*EtherChannel),\n
430
00:37:40,599 --> 00:37:43,079
So, what do you think is the answer?
431
00:37:43,079 --> 00:37:48,639
Pause the video here to think about it.
432
00:37:48,639 --> 00:37:50,519
Okay, hopefully you got the answer.
433
00:37:50,519 --> 00:37:54,039
I think the correct answer is B, no link is\nformed.
434
00:37:55,980 --> 00:37:58,659
So, first you create the port-channel interface.
435
00:37:58,659 --> 00:38:02,649
So it does exist, the virtual interface.
436
00:38:02,650 --> 00:38:08,000
Then you manually configure the channel protocol\n
437
00:38:08,000 --> 00:38:12,579
But when you use the command CHANNEL-GROUP\n
438
00:38:12,579 --> 00:38:18,869
to join this port-channel interface, to join\n
439
00:38:18,869 --> 00:38:21,329
The CHANNEL-GROUP 1 MODE ON command.
440
00:38:21,329 --> 00:38:27,429
Because we already manually configured LACP,\n
441
00:38:29,789 --> 00:38:33,489
MODE ON will not work, the command will be\nrejected.
442
00:38:33,489 --> 00:38:34,779
And then same thing on SwitchB.
443
00:38:34,780 --> 00:38:38,530
This time instead of LACP it's PAgP.
444
00:38:38,530 --> 00:38:43,580
So you manually configured the channel-protocol\n
445
00:38:43,579 --> 00:38:49,909
exists, these interfaces won't actually join\n
446
00:38:50,909 --> 00:38:53,349
So, I think B is the correct answer.
447
00:38:56,900 --> 00:39:02,180
So here is Boson's explanation, quite a lengthy,\n
448
00:39:02,179 --> 00:39:05,889
And this is something really great about ExSim.
449
00:39:05,889 --> 00:39:12,379
If you're ever unsure about why B is correct,\n
450
00:39:12,380 --> 00:39:17,900
all of these great, in-detail explanations\nhelping you out.
451
00:39:17,900 --> 00:39:20,480
And then finally, at the end there are references.
452
00:39:20,480 --> 00:39:26,838
This is to the official cert guide, EtherChannel\n
453
00:39:26,838 --> 00:39:32,579
And then also two links to Cisco documentation,\n
454
00:39:34,949 --> 00:39:37,989
Okay, so that's today's Boson ExSim practice\nquestion.
455
00:39:37,989 --> 00:39:42,838
If you want to get a copy of Boson ExSim,\n
456
00:39:42,838 --> 00:39:44,900
I really like these practice exams.
457
00:39:44,900 --> 00:39:49,838
I used them myself for my CCNA and CCNP, so\n
458
00:39:50,949 --> 00:39:57,769
So once again, follow the link in the video\n
459
00:39:57,769 --> 00:40:00,599
There are supplementary materials for this\nvideo.
460
00:40:00,599 --> 00:40:04,480
There is a flashcard deck to use with the\nsoftware ‘Anki’.
461
00:40:04,480 --> 00:40:09,240
There will also be a packet tracer practice\n
462
00:40:09,239 --> 00:40:11,689
That will be in the next video.
463
00:40:11,690 --> 00:40:15,480
Sign up for my mailing list via the link in\n
464
00:40:15,480 --> 00:40:20,829
the flashcards and packet tracer lab files\nfor the course.
465
00:40:20,829 --> 00:40:25,900
Before finishing today’s video I want to\n
466
00:40:25,900 --> 00:40:31,180
Thank you to funnydart, Joshua, Scott, Aleksa,\n
467
00:40:31,179 --> 00:40:38,710
Samil, Velvijaykum, C Mohd, Johan, Mark, Miguel,\n
468
00:40:38,710 --> 00:40:45,250
of ExSim, Sidi, Magrathea, Devin, Charlsetta,\n
469
00:40:45,250 --> 00:40:50,000
Sorry if I pronounced your name incorrectly,\n
470
00:40:50,000 --> 00:40:55,900
One of you is still displaying as Channel\n
471
00:40:55,900 --> 00:40:59,070
me know and I’ll see if YouTube can fix\nit.
472
00:40:59,070 --> 00:41:04,650
This is the list of JCNP-level members at\n
473
00:41:04,650 --> 00:41:08,840
2020, if you signed up recently and your name\n
474
00:41:12,880 --> 00:41:17,360
Please subscribe to the channel, like the\n
475
00:41:17,360 --> 00:41:20,630
with anyone else studying for the CCNA.
476
00:41:20,630 --> 00:41:23,320
If you want to leave a tip, check the links\nin the description.
477
00:41:23,320 --> 00:41:29,910
I'm also a Brave verified publisher and accept\n
39435
Can't find what you're looking for?
Get subtitles in any language from opensubtitles.com, and translate them here.