Professional Documents
Culture Documents
16
00:00:55,266 --> 00:00:56,166
Did you get that?
17
00:00:56,316 --> 00:01:00,206
So we'll look at the different devices, kind of
the evolutions that switches have gone through.
18
00:01:00,396 --> 00:01:02,696
A big one for your understanding
19
00:01:02,696 --> 00:01:05,686
and certification purpose is
collision and broadcast domains.
20
00:01:05,686 --> 00:01:06,896
And then I want to walk you
21
00:01:06,896 --> 00:01:10,076
through an end-to-end scenario,
a day in the life of a switch.
22
00:01:11,676 --> 00:01:17,276
So the realm is 1980s' timeframe, Bengals
are singing Walk Like an Egyptian,
23
00:01:17,276 --> 00:01:21,266
big hair is the norm, and network
hubs are hitting the market.
24
00:01:21,576 --> 00:01:25,906
10 megabits per second speed is
screaming, this is life-changing events,
25
00:01:25,906 --> 00:01:28,986
where we now can have computers sharing data
26
00:01:28,986 --> 00:01:32,396
without people walking floppy disks
back and forth down the aisles.
27
00:01:32,396 --> 00:01:34,736
I mean, that's the kind of
timeframe that we're in.
28
00:01:34,736 --> 00:01:38,776
Ethernet is developing the standard of carrier
sense -- I should say it is developed --
29
00:01:38,896 --> 00:01:44,116
carrier sense multiple access collision
detection, meaning we have this competition
30
00:01:44,116 --> 00:01:49,296
between token ring, which is still a valid
competition back in the '80s, token ring
31
00:01:49,296 --> 00:01:55,616
and Ethernet, where Ethernet
uses this kind of environment,
32
00:01:55,816 --> 00:01:58,686
multiple people are accessing
the network at a time.
33
00:01:59,306 --> 00:02:00,496
They're all listening.
34
00:02:00,496 --> 00:02:04,896
They're all trying to sense if there's
anything being sent on the network.
35
00:02:04,896 --> 00:02:08,086
If they don't hear anything, because
only, and here's a key point,
36
00:02:08,206 --> 00:02:12,526
only one of them can send data
or receive data at a time.
37
00:02:12,986 --> 00:02:16,926
Only one. And so they're all listening, they're
like, "Okay, is anybody sending any data?
38
00:02:16,926 --> 00:02:21,036
No, I don't hear anything, so I will go ahead
and send it," and that works most of the time.
39
00:02:21,286 --> 00:02:26,356
However, there is a chance that two
people are listening at the same time.
40
00:02:26,356 --> 00:02:31,396
What if two computers are listening at the same
time, they both hear a clear, they both send.
41
00:02:31,396 --> 00:02:33,186
That's where we have a collision.
42
00:02:33,186 --> 00:02:39,436
And that is collision detection, that's the
ability for the devices to be like, "Oh,
43
00:02:39,436 --> 00:02:43,496
we both sent at the same time,
our data is scrambled, my bad."
44
00:02:43,496 --> 00:02:48,816
They run a back-off algorithm that they both
back off and then wait a certain amount of time
45
00:02:48,816 --> 00:02:52,186
to send again and then they both send and
hope they don't collide a second time.
46
00:02:52,516 --> 00:02:55,186
Because collisions are really taking
down their network performance.
47
00:02:55,186 --> 00:02:57,376
And that was one of the things with token ring.
48
00:02:57,516 --> 00:03:01,216
Token ring said we're going to send
this little ring around the network.
49
00:03:01,376 --> 00:03:02,436
I shouldn't say send a ring.
50
00:03:02,436 --> 00:03:06,646
Send this token around the network
that all the computers are plugged into
51
00:03:06,856 --> 00:03:10,476
and only whoever has the
token can send at a time.
52
00:03:10,566 --> 00:03:13,926
So this token is going bzz, bzz, bzz,
you know, flying at the speed of light
53
00:03:13,926 --> 00:03:17,736
around this ring network, the devices
67
00:03:57,616 --> 00:04:01,316
That is short for one-collision domain.
68
00:04:02,796 --> 00:04:08,926
Key topic to know: a hub, no matter how many
ports it has -- it could have, what is that,
69
00:04:08,926 --> 00:04:14,026
eight ports like I'm staring at,
or 20 or 950,000 ports on a hub...
70
00:04:14,026 --> 00:04:17,816
it would not have that, but it
would all be one-collision domain
71
00:04:17,956 --> 00:04:24,096
which in rough English would just be how
many people can send or receive at a time.
72
00:04:24,526 --> 00:04:26,916
Now, I also want to emphasize the "or" there.
73
00:04:27,706 --> 00:04:30,946
"Or receive" means you are
in a half-duplex world.
74
00:04:31,266 --> 00:04:33,746
Send or receive, so I'm pretty
much saying, "Well,
75
00:04:33,746 --> 00:04:35,906
I can send something or I can receive something.
76
00:04:35,906 --> 00:04:36,706
I cannot do both."
77
00:04:36,706 --> 00:04:37,996
It's like a walkie-talkie.
78
00:04:38,616 --> 00:04:43,366
Now, that was the world of the hub: one
person sending or receiving at a time.
79
00:04:43,606 --> 00:04:48,166
So the larger and larger your network group,
the more and more collisions you would have
80
00:04:48,166 --> 00:04:51,776
because there's more of a chance that people are
sending and receiving, or sending or receiving,
81
00:04:51,776 --> 00:04:55,706
at the same time and you're getting collisions,
your network performance is going down.
82
00:04:56,976 --> 00:05:04,606
Likewise, you run into challenges with security,
meaning a hub, if you bring up the OSI model.
83
00:05:04,606 --> 00:05:06,736
You know, you've got your seven layers,
dut, dut, dut, dut, dut, dut, dut.
84
00:05:06,956 --> 00:05:11,526
Down here is the physical layer,
which is where the hub resides.
85
00:05:11,596 --> 00:05:14,936
Physical layer devices have
no intelligence at all.
86
00:05:15,276 --> 00:05:18,836
They receive electric signals
and they send electric signals,
87
00:05:18,836 --> 00:05:20,216
and that's exactly what this does.
88
00:05:20,216 --> 00:05:25,176
When this guy sends a packet -- let's
say it's destined for this guy -89
00:05:25,416 --> 00:05:28,626
what the hub does is receive it and
say, "Well, I just got some data.
90
00:05:28,906 --> 00:05:32,006
I'm going to send it out
all of the network ports."
91
00:05:32,786 --> 00:05:36,266
This guy will get it, but so will
this guy, and so will this guy,
92
157
00:09:39,056 --> 00:09:42,786
well it looks like that was sent to this
MAC address," we'll call it MAC One.
158
00:09:43,676 --> 00:09:45,986
"That was sent to this MAC address over here.
159
00:09:46,256 --> 00:09:49,276
So I'm not going to forward that
on to this side of the network.
160
00:09:49,276 --> 00:09:49,886
They don't need it."
161
00:09:51,006 --> 00:09:54,046
So that's where our filtering came into play.
162
00:09:54,046 --> 00:09:56,406
So now, if you sent to the
other side of the network -163
00:09:56,406 --> 00:10:00,326
let's say we sent from the left side of
the network here over to the right -164
00:10:00,326 --> 00:10:02,626
as soon as it hits this hub, it
explodes and goes everywhere,
165
00:10:02,626 --> 00:10:04,416
so you're not really getting much filtering
166
00:10:04,416 --> 00:10:07,186
since we still have these layer
one devices, but it was good.
167
00:10:07,186 --> 00:10:09,226
I mean, this was a good step.
168
00:10:09,226 --> 00:10:12,196
Now, here is the big Achilles
heel of the bridges.
169
00:10:12,606 --> 00:10:14,136
They were software-based.
170
184
00:10:56,486 --> 00:10:59,466
We buy RAID controller cards,"
which are now common everywhere.
185
00:10:59,716 --> 00:11:02,356
RAID controller cards that offload that,
186
00:11:02,356 --> 00:11:04,736
so Windows doesn't have to
worry about mirroring those.
187
00:11:04,736 --> 00:11:09,996
Well, in the same sense, Windows would slow down
a lot if you actually tried to do RAID with it
188
00:11:09,996 --> 00:11:12,246
because it's having to keep
up with hard drive functions.
189
00:11:12,246 --> 00:11:13,226
Same thing here.
190
00:11:13,226 --> 00:11:17,536
The bridge is learning all these
MAC addresses in the software.
191
00:11:17,536 --> 00:11:22,106
It's processing them in the software, so
as stuff goes from one side of the network
192
00:11:22,106 --> 00:11:26,796
to the other, it slows down because of the
processing that's taking place on that device.
193
00:11:28,136 --> 00:11:31,936
And now we make the turn
into the new millennium.
194
00:11:31,936 --> 00:11:36,316
Around year 2000, you start seeing network
switches becoming a commonplace thing.
195
00:11:36,506 --> 00:11:37,316
And it's funny.
196
00:11:37,316 --> 00:11:39,606
I'm thinking "Okay, we had
210
00:12:17,596 --> 00:12:23,076
Because everything that I said about bridges
is the same when it comes to switches; however,
211
00:12:23,246 --> 00:12:25,646
we now have a very high port density.
212
00:12:25,716 --> 00:12:27,666
Like a lot of devices can plug into these.
213
00:12:27,666 --> 00:12:30,106
We're no longer limited to
two or three or four ports.
214
00:12:30,106 --> 00:12:34,156
But the biggest thing that
changed was the creation of ASICs.
215
00:12:34,596 --> 00:12:35,366
What are those?
216
00:12:35,826 --> 00:12:39,536
Application-specific integrated circuitry.
217
00:12:39,966 --> 00:12:45,146
Such a huge concept for our
network devices, because this moved
218
00:12:45,516 --> 00:12:49,586
that software-based processing
of the bridge into the hardware.
219
00:12:49,836 --> 00:12:52,396
And you're going to see this topic
come up again and again and again.
220
00:12:52,766 --> 00:12:55,256
All ASICs are is somebody engineered a chip.
221
00:12:55,376 --> 00:12:59,276
Here's my little chip, a little chip with wires
and connections and all that kind of stuff
222
00:12:59,276 --> 00:13:04,246
to where in the hardware the intelligence
of the device, it's able to handle it
223
00:13:04,246 --> 00:13:06,026
without relying on any kind of software.
224
00:13:06,026 --> 00:13:12,146
And any time you introduce ASICs into
the picture, you introduce a lot of speed
225
00:13:12,146 --> 00:13:14,976
because you have it all being
processed in hardware.
226
00:13:15,216 --> 00:13:16,866
No longer does the software
have to get involved.
227
00:13:16,866 --> 00:13:21,086
ASICS has changed the world of
switching or bridging, I should say,
228
00:13:21,086 --> 00:13:22,786
to where now switching is commonplace.
229
00:13:22,786 --> 00:13:25,146
ASICs changed the world of VPNs.
230
00:13:25,816 --> 00:13:29,426
We would no longer be able to
scale virtual private networks,
231
00:13:29,426 --> 00:13:33,816
which is encrypted tunnels running across
the internet, if we didn't have these ASICs,
232
00:13:33,816 --> 00:13:35,966
these chips that handle a lot of the encryption,
233
00:13:35,966 --> 00:13:39,396
because the encryption alone would
bury the software of the device.
234
00:13:39,816 --> 00:13:43,456
So ASICS are a world-changing event.
235
00:13:43,456 --> 00:13:47,176
They cause a lot of these
devices to just move a lot faster.
236
00:13:47,176 --> 00:13:54,556
Now we have switches where it's able to move
as fast as the hubs were, which is wire speed.
237
00:13:54,556 --> 00:13:58,506
As electric signals are coming in,
it's processing and sending them out.
238
00:13:58,506 --> 00:14:01,226
Every port on a switch is
its own collision domain.
239
00:14:01,606 --> 00:14:06,556
So when you come to a switch, you
look at how many ports there are.
240
00:14:06,556 --> 00:14:09,806
Let's say it's a 24-port switch
or this one looks like a 20...
241
00:14:09,966 --> 00:14:12,836
they got these two weird ports,
so maybe a 26-port switch,
242
00:14:12,836 --> 00:14:15,816
so you've got 26-collision domains.
243
00:14:15,926 --> 00:14:21,976
And again, going back to our simple definition,
26 people, 26 devices plugged in there can send
244
00:14:22,456 --> 00:14:26,926
and -- ooh, there's a big change
-- and receive at the same time.
245
00:14:27,276 --> 00:14:31,806
We've gone full duplex to where now instead
of a walkie-talkie, you're like a telephone
246
00:14:31,806 --> 00:14:34,836
to where both people can talk on top
of each other and still understand,
247
00:14:34,836 --> 00:14:37,416
at least in the computer world,
still understand each other.
248
00:14:37,416 --> 00:14:44,006
So when you say this is a 100-megabit per
second switch, or 100-megabit per second port,
249
00:14:44,216 --> 00:14:48,326
really you're getting 200 megabits per
second if you're running it at full duplex
250
00:14:48,326 --> 00:14:54,166
because you get 100 send and 100 receive
that you can do at the same time.
251
00:14:54,166 --> 00:14:59,746
Now, all network speeds are rated at
half duplex, so when you see a gigabit252
00:14:59,746 --> 00:15:04,986
or a 100-megabit per second port, it's
being rated at half duplex, so I mean,
253
00:15:04,986 --> 00:15:07,446
you truly can never go above that speed.
254
00:15:07,606 --> 00:15:09,806
It's just now you can do send
and receive at the same time.
255
00:15:09,806 --> 00:15:12,126
Totally kind of life-changing event there.
256
00:15:12,416 --> 00:15:14,296
You also support varying port speeds.
257
00:15:14,296 --> 00:15:17,726
A hub had to have all the same speed.
258
00:15:17,926 --> 00:15:22,936
If it was a 10-megabit per second port, every
port on that hub, a 10-megabit per second hub,
259
00:15:22,936 --> 00:15:24,906
every port on the hub would
be 10-megabits per second.
260
00:15:24,906 --> 00:15:28,196
But with switches you could have, for
instance, these guys, and this is common,
261
00:15:28,436 --> 00:15:34,696
over on the left being 100-megabit per
second connection and these two guys
262
00:15:34,696 --> 00:15:40,456
over on the right might be 1,000 megabits per
second or a gigabit, or as technology continues
263
00:15:40,456 --> 00:15:43,106
to evolve, we're going to
see these being common,
264
00:15:43,296 --> 00:15:49,176
1,000-megabit per second ports is
normal customer plug-ins and normal use
265
00:15:49,176 --> 00:15:53,866
and then maybe these uplinks are
10,000 megabits per second, or 10 gig,
266
00:15:53,866 --> 00:15:59,526
or now 40,000 megabits per second or 40
gigabits per second uplinks that you can have.
267
00:15:59,526 --> 00:16:04,806
So that way you can have switches that are
daisy-chained together to where, you know,
268
00:16:04,806 --> 00:16:08,096
you've got all these guys that
are all 100 and this is 1,000,
269
00:16:08,096 --> 00:16:11,946
so that way this doesn't become a bottleneck
and all these guys are 100 and this is 1,000,
270
00:16:11,946 --> 00:16:17,076
so that way you can link these together
without bottlenecking them on these speeds.
271
00:16:17,226 --> 00:16:22,916
These switches are managed and intelligent
to where -- and I'll flip that term.
272
00:16:22,916 --> 00:16:25,696
They're intelligent in the sense
that they have the same capabilities
273
00:16:25,696 --> 00:16:28,306
of the bridge to learn MAC addresses.
274
00:16:28,306 --> 00:16:32,836
So as these switches power on, they will learn
all the different devices that are on there.
275
00:16:32,836 --> 00:16:40,296
So now when this guy sends a packet into the
switch, it will be able to send it out to just
276
00:16:40,296 --> 00:16:43,476
that guy because he knows
where the MAC address is at.
277
00:16:44,056 --> 00:16:45,256
He's located all of it.
278
00:16:45,256 --> 00:16:48,536
He will even learn, for instance, if
you start daisy-chaining them like this,
279
00:16:48,536 --> 00:16:51,876
you've got 20 MAC addresses down
here, we'll say, that it's learned.
280
00:16:51,876 --> 00:16:56,526
This switch will learn that all 20 of those
MAC addresses are accessible on this one port.
281
00:16:57,556 --> 00:17:02,066
So it's not uncommon to see one port with
20 MAC addresses, which tells you, "Okay,
282
00:17:02,066 --> 00:17:04,396
that port must be daisy-chained
to another device
283
00:17:04,396 --> 00:17:07,226
that has all kinds of devices plugged into it."
284
00:17:07,226 --> 00:17:10,656
So that's the intelligent side.
285
00:17:10,876 --> 00:17:13,966
The managed side is going to be
312
00:18:27,966 --> 00:18:29,086
Where is it?"
313
00:18:29,346 --> 00:18:31,926
So it smells good and it is smooth to touch.
314
00:18:31,926 --> 00:18:35,926
It is. You install these into racks -- you know,
I'm kind of tongue-in-cheek on saying that.
315
00:18:36,186 --> 00:18:40,776
But this is the core of what our
networks use to connect devices.
316
00:18:42,356 --> 00:18:46,526
One more piece that I want to add on
here, because it was on the title slide,
317
00:18:46,526 --> 00:18:50,006
I didn't add it in my bullets, is
the concept of a broadcast domain.
318
00:18:51,256 --> 00:18:54,916
A broadcast domain essentially means,
319
00:18:54,916 --> 00:19:00,116
how far will a broadcast message
go before it's stopped, okay?
320
00:19:00,116 --> 00:19:03,906
So a broadcast, broadcasts just
happen in the network world.
321
00:19:03,906 --> 00:19:05,596
They're partially how computers work.
322
00:19:05,806 --> 00:19:10,966
Like when this computer boots up, if it's
using DHCP, it doesn't have an IP address,
323
00:19:11,016 --> 00:19:14,976
so it will send a broadcast message
saying, "Hello, anybody out there?
324
00:19:15,116 --> 00:19:18,716
I don't have an address,"
an IP address, I should say,
325
00:19:18,716 --> 00:19:20,946
"but if somebody could give
me one that would be great."
326
00:19:21,326 --> 00:19:22,986
It's looking for a DHCP server.
327
00:19:23,356 --> 00:19:28,956
Now, on a switch, just like a hub,
broadcasts will go to all ports.
328
00:19:29,416 --> 00:19:31,376
That's one of our scalability concerns.
329
00:19:31,376 --> 00:19:34,426
A hub you can only scale to
a few devices, I mean, 30,
330
00:19:34,426 --> 00:19:36,946
40 devices you're starting
to really hit the max.
331
00:19:37,196 --> 00:19:39,956
Switches you can get into
the hundreds of devices.
332
00:19:40,126 --> 00:19:45,496
You know, 200, 300, 400 devices, but eventually
you're going to reach a point where you get
333
00:19:45,496 --> 00:19:48,396
so many broadcasts because
everybody's kind of chitter-chattering
334
00:19:48,396 --> 00:19:51,616
around that you're impacting your
computer and network performance.
335
00:19:51,616 --> 00:19:55,166
So you start dividing it up
into more broadcast domains,
336
00:19:55,166 --> 00:19:58,006
and we'll talk about how that's possible, but
I just wanted to throw that term out there
337
364
00:21:30,626 --> 00:21:34,846
Now, on fiber you always have two,
I guess you could call them wires -365
00:21:34,846 --> 00:21:38,026
they're not really wires; they're
glass or plastic -- that are in there.
366
00:21:38,026 --> 00:21:41,016
One is going to be a send and
one is going to be a receive.
367
00:21:41,016 --> 00:21:45,446
So you kind of go click, click and plug it into
that, and then that fiber, depending on the kind
368
00:21:45,446 --> 00:21:50,606
of fiber it is, you can, I mean you can
go 500 meters away, you could go miles or,
369
00:21:50,606 --> 00:21:53,576
depending on what, where you
are in the world, kilometers,
370
00:21:53,826 --> 00:21:58,376
depending on what currency you use for distance.
371
00:21:58,376 --> 00:22:01,766
So you can span these things way
apart and connect them just the same.
372
00:22:01,816 --> 00:22:07,996
So a lot of times on the switches you will see
these ports that are kind of dual-purpose ports
373
00:22:07,996 --> 00:22:14,336
to where you can either, this is like a CAT
5 connection or CAT 6 copper connection,
374
00:22:14,756 --> 00:22:20,616
and then below it will be an SFP where you
can plug in one of these fiber-optic modules.
375
00:22:20,616 --> 00:22:24,496
Or you might see one, I think this is one of
them, I don't think these are dual purpose,
376
00:22:24,496 --> 00:22:27,686
where you have four slots
where you can plug in SFPs.
377
00:22:27,686 --> 00:22:30,196
Now you might say, "Why do
you have them changeable?"
378
00:22:30,356 --> 00:22:32,376
Well, there's different kinds
of fiber you can get.
379
00:22:32,376 --> 00:22:36,316
There's multi-mode fiber, which
is really easy to work with
380
00:22:36,316 --> 00:22:39,176
and a lot cheaper to make because it's plastic.
381
00:22:39,176 --> 00:22:43,966
And so multi-mode fiber has the ability of
being really easy to work with and really cheap,
382
00:22:44,146 --> 00:22:46,846
but it doesn't go as far as single-mode fiber.
383
00:22:47,136 --> 00:22:51,486
And single-mode fiber is always glass
that, you know, if you were to open this
384
00:22:51,486 --> 00:22:55,236
up with a little razor, you would see
really, really thin glass that it's using
385
00:22:55,426 --> 00:22:57,626
and a lot more difficult to work
with and a lot more expensive.
386
00:22:57,626 --> 00:23:02,406
So based on what your needs are, you can buy
single-mode or multi-mode fiber interfaces
387
00:23:02,406 --> 00:23:04,816
and then you just have to -- you've just
got to make sure they're compatible.
388
00:23:04,816 --> 00:23:07,676
415
00:24:45,336 --> 00:24:50,346
So this guy, let's say the guy on the
left, the happy computer is talking
416
00:24:50,346 --> 00:24:52,446
to the straight-faced computer in the middle.
417
00:24:53,036 --> 00:24:57,066
So he's going to send a frame,
let's just say I ping...
418
00:24:57,526 --> 00:25:03,486
let's see, I'm trying to think
of how far back I'll go here.
419
00:25:03,486 --> 00:25:08,786
Okay. So let's just say IP
address-wise, this guy is 10.1.1.1;
420
00:25:08,986 --> 00:25:11,636
this guy is 10.1.1.2 on an IP address.
421
00:25:11,636 --> 00:25:17,026
So on this computer I type
in ping 10.1.1.2, right?
422
00:25:17,316 --> 00:25:21,466
What's the first message
that's going to be sent?
423
00:25:21,466 --> 00:25:24,096
An ARP -- address resolution protocol -424
00:25:24,096 --> 00:25:28,826
saying, "Okay, great, I see that you're pinging
10.1.1.2, but I've got to create a frame.
425
00:25:28,826 --> 00:25:32,666
I've got to have source and destination IP
addresses, source and destination MAC address.
426
00:25:32,706 --> 00:25:38,026
I don't have the MAC address for
10.1.1.2," so ARP is a broadcast message.
427
00:25:38,116 --> 00:25:40,276
441
00:26:17,736 --> 00:26:22,776
As soon as this broadcast came into the
switch, I mean, if we were to grab that
442
00:26:22,776 --> 00:26:26,016
and use Wire Shark and look at it, we
would say, "Okay, it's an ARP message.
443
00:26:26,016 --> 00:26:27,336
It's trying to find a MAC address.
444
00:26:27,336 --> 00:26:32,256
It's coming from the source
IP address of 10.1.1.1.
445
00:26:32,506 --> 00:26:36,576
It's looking for the destination
IP address of 10.1.1.2.
446
00:26:36,576 --> 00:26:42,436
It's coming from the source MAC address
of 11;11, you know, this guy right here.
447
00:26:42,796 --> 00:26:47,376
And it's going to the destination
MAC address of, I don't know.
448
00:26:47,626 --> 00:26:51,296
Now, you might say, "Well, wait a
second; it doesn't know this MAC address.
449
00:26:51,296 --> 00:26:52,286
It has to have something in there."
450
00:26:52,536 --> 00:26:53,776
Well, it absolutely does.
451
00:26:54,146 --> 00:26:56,536
It's destination MAC address is FFFFFF.
452
00:26:56,536 --> 00:27:02,606
Remember, MAC addresses are hexadecimal,
so A through F are valid characters.
453
00:27:02,606 --> 00:27:08,406
And the very, very last possible MAC address
in all the scheme, FFFFFF, means a broadcast.
454
00:27:08,746 --> 00:27:09,436
That's what that means.
455
00:27:09,436 --> 00:27:13,516
So the switch receives it destined to
this MAC address that it will never learn
456
00:27:13,516 --> 00:27:18,736
on any individual port and it says, "Okay,
well, that MAC address, it says go everywhere.
457
00:27:18,736 --> 00:27:20,466
But I just learned something."
458
00:27:21,276 --> 00:27:25,996
By seeing this broadcast message come into
the switch it goes, "Oh, oh, oh, wait a sec.
459
00:27:26,126 --> 00:27:30,056
On port -- " let's just say this is port 0/2.
460
00:27:30,056 --> 00:27:31,946
You know, this one up here was 0/1.
461
00:27:31,946 --> 00:27:39,166
So it says "Okay, 0/2 is really 1111:1111:1111."
462
00:27:39,166 --> 00:27:43,426
So now the switch has become
one MAC address smarter.
463
00:27:44,646 --> 00:27:50,516
Now this guy comes back and says, "Oh,
that's me, let me send my ARP reply."
464
00:27:50,516 --> 00:27:52,156
Here's his ARP message.
465
00:27:52,156 --> 00:27:55,476
"I'm coming from the source IP
address going to this destination,
466
00:27:55,686 --> 00:27:59,386
coming from this source MAC
address, going to this destination."
467
00:27:59,386 --> 00:28:00,706
Let me just zoom in on that.
468
00:28:00,706 --> 00:28:01,886
You know if I were to break that packet down,
469
00:28:01,886 --> 00:28:05,216
it would say the destination
MAC address is the ones.
470
00:28:05,216 --> 00:28:08,986
The source MAC address is the
twos and it will come into switch.
471
00:28:08,986 --> 00:28:10,446
Now, two things happen here.
472
00:28:11,086 --> 00:28:13,296
One is, let's say the switch is looking at,
473
00:28:13,296 --> 00:28:17,676
let's just say that is port
0/12, or let's say 0/11.
474
00:28:17,796 --> 00:28:20,636
I'm trying to be accurate looking at the switch.
475
00:28:20,636 --> 00:28:21,646
Let's say 0/15.
476
00:28:21,646 --> 00:28:24,766
So it's going to say, "Okay, I
just learned another MAC address
477
00:28:24,766 --> 00:28:26,106
because I just saw a frame come in there.
478
00:28:26,106 --> 00:28:28,006
It is 2222.
479
00:28:28,396 --> 00:28:33,016
So I now know that that computer
is available on port 0/15."
480
00:28:33,016 --> 00:28:34,096
Now, this is all in the CAM.
481
00:28:34,096 --> 00:28:39,766
All in the memory of the switch, so if I
pull the plug on this switch at any time,
482
00:28:39,946 --> 00:28:43,656
all of this goes away and it has to
relearn all of these MAC addresses.
483
00:28:43,656 --> 00:28:47,606
So that's the first thing it does is it
learns that MAC address is on that port.
484
00:28:47,606 --> 00:28:49,566
But now it's become smarter.
485
00:28:50,056 --> 00:28:52,456
It goes, "Oh, it looks like you're
trying to go to the destination
486
00:28:52,456 --> 00:28:55,786
of 111111, you know, all the ones.
487
00:28:55,786 --> 00:28:56,626
I know where that guy is.
488
00:28:56,726 --> 00:28:58,016
He's on port 0/2."
489
00:28:58,016 --> 00:29:02,966
So now instead of sending the reply to all
ports, the switch is just going to say, "Okay,
490
00:29:02,966 --> 00:29:08,706
let me switch you right over here down to
this device" and only those two get it.
491
00:29:08,706 --> 00:29:12,726
And now point-to-point communication
can happen between those guys
492
00:29:12,726 --> 00:29:16,896
without disturbing anybody else because
the switch has learned their MAC address.
493
00:29:17,206 --> 00:29:19,406
Now, let's talk of real world.
494
00:29:19,546 --> 00:29:20,856
Okay, a switch powers on.
495
00:29:21,156 --> 00:29:26,496
How long is it going to take before
it learns all of the MAC addresses
496
00:29:26,496 --> 00:29:28,146
on the network, or the ones that it needs?
497
00:29:28,766 --> 00:29:31,396
I would say five to 10 seconds.
498
00:29:31,896 --> 00:29:34,266
I know. Really, that fast?
499
00:29:34,266 --> 00:29:38,056
Yeah. I mean hundreds of devices it can
learn in five to 10 seconds because all
500
00:29:38,056 --> 00:29:41,356
of these guys are talking, and if you're
talking about powering on a switch, well,
501
00:29:41,466 --> 00:29:45,116
as that switch is powering on, the devices
are chatting They need IP addresses.
502
00:29:45,116 --> 00:29:46,036
They want to communicate.
503
00:29:46,036 --> 00:29:51,416
So the switch is gaining knowledge essentially
right after it boots and is ready to do that.
504
00:29:51,416 --> 00:29:54,976
It's ready to go, so it does not take
long for these guys to learn at all.
505
00:29:55,516 --> 00:30:01,646
Also keep in mind these entries
have a life span of five minutes,
506
00:30:02,446 --> 00:30:06,436
meaning if the device goes
quiet for five minutes --
507
00:30:06,436 --> 00:30:11,576
and this is by default, you can change it -- the
switch will forget where that MAC address is.
508
00:30:11,906 --> 00:30:13,796
So this guy goes quiet.
509
00:30:13,936 --> 00:30:15,446
He disappears from the table.
510
00:30:15,446 --> 00:30:16,276
Now, no big deal.
511
00:30:16,276 --> 00:30:20,536
That just means the next time somebody has to
communicate with him, the switch will treat it
512
00:30:20,536 --> 00:30:25,716
like a broadcast, because it's going
to say, "I don't know where 111111 is."
513
00:30:25,716 --> 00:30:28,086
So it will send it everywhere
and then relearn that.
514
00:30:28,086 --> 00:30:30,796
The reason it does that is
because MAC addresses can change.
515
00:30:30,796 --> 00:30:33,756
Now, it's rare, really rare
for a MAC address to change.
516
00:30:33,756 --> 00:30:36,616
But somebody could replace a network card.
517
00:30:37,086 --> 00:30:40,126
You could be doing strange
things with virtualization.
518
00:30:40,126 --> 00:30:41,546
We'll talk about that later on.
519
00:30:41,736 --> 00:30:46,356
But I mean, there's times where the MAC address
can change, so this guarantees you that device
520
00:30:46,356 --> 00:30:49,986
within five minutes will be able to
communicate or be learned or, you know,
521
00:30:49,986 --> 00:30:52,776
that MAC address will be replaced
on that switch if it stops talking.
522
00:30:53,956 --> 00:30:56,546
Welcome to the world of switching indeed.
523
00:30:56,906 --> 00:30:59,206
That is how a switch functions.
524
00:30:59,206 --> 00:31:02,016
That is its goal, is to bring
together all the devices
525
00:31:02,016 --> 00:31:05,896
into a local area network and
allow them to communicate.
526
00:31:06,386 --> 00:31:08,776
So what do we see, and what
do I want you to do with it?
527
00:31:08,776 --> 00:31:10,076
You see the bullets on the screen.
528
00:31:10,076 --> 00:31:11,936
Those are the major points that we hit.
529
00:31:11,936 --> 00:31:18,206
First thing I would like you to do is grab a
piece of paper and in your own words write down,
530
00:31:18,576 --> 00:31:25,606
"A hub is this" or if maybe you're not a
writer, you know, go to a friend, go to a spouse
531
00:31:25,606 --> 00:31:27,906
and explain to them, "A hub is this.
532
00:31:27,906 --> 00:31:30,846
This is the difference between
a hub and a switch."
533
00:31:31,036 --> 00:31:39,776
Or, I do this sometimes: I'll be in Best Buy
or one of the places where you just go and...
534
00:31:40,156 --> 00:31:44,216
waste money on nonsense, but you'll
be in Best Buy and talk to one
535
00:31:44,216 --> 00:31:48,016
of the employees and see
their perspective on it.
536
00:31:48,016 --> 00:31:52,366
I've got some very interesting results from
my surveys where you just go in and say, "Hey,
537
00:31:52,366 --> 00:31:54,836
I'm looking for a switch, just a small one.
538
00:31:54,836 --> 00:31:55,646
Where are those at?"
539
00:31:55,646 --> 00:31:56,746
"Oh, they're over here.
540
00:31:56,746 --> 00:31:57,576
Here's the box."
541
00:31:57,576 --> 00:32:02,096
And then throw this kind of question out
there, just say, "Actually somebody told me
542
00:32:02,096 --> 00:32:04,246
to get a hub, and someone
told me to get a switch,
543
00:32:04,246 --> 00:32:06,156
and then someone else said
they're the same thing.
544
00:32:06,836 --> 00:32:07,666
What do you say?
545
00:32:07,666 --> 00:32:08,986
What's best?"
546
00:32:09,586 --> 00:32:10,346
And see what they say.
547
00:32:10,766 --> 00:32:14,806
That is one of the most fun -- now,
don't throw them under the bus.
548
00:32:14,806 --> 00:32:17,476
Don't be like okay, "No,
this is really how it works."
549
00:32:17,476 --> 00:32:21,416
But sometimes you'll get people who are like
ninjas, that are like -- they know exactly.
550
00:32:21,706 --> 00:32:23,056
Other people will just say I don't know.
551
00:32:23,056 --> 00:32:27,696
Other people will just make up the most creative
and unique answers that you've ever seen.
552
00:32:27,696 --> 00:32:29,766
Sometimes they'll look at the
box and see if it says something.
553
00:32:29,766 --> 00:32:30,716
But it's fun.
554
00:32:30,716 --> 00:32:31,906
It's a fun survey to take.
555
00:32:32,336 --> 00:32:35,586
The second thing I want you
to do is look at some devices
556
00:32:35,586 --> 00:32:37,976
and identify how many collision domains,
557
00:32:37,976 --> 00:32:40,316
how many broadcast domains
exist on each one of those.
558
00:32:40,316 --> 00:32:44,306
Now, if these are all daisy-chained
together, if I take some cables and go clink,
559
00:32:44,306 --> 00:32:48,326
clink and link all these together,
how many broadcast domains?
560
00:32:49,146 --> 00:32:52,416
One. A broadcast will go
everywhere on those switches.
561
00:32:52,416 --> 00:32:53,856
How many collision domains?
562
00:32:53,856 --> 00:32:54,926
Well, start counting.
563
00:32:55,116 --> 00:32:57,526
One, two, and that's the console
board, so don't count that one,
564
00:32:57,526 --> 00:32:58,696
you know, start counting those up.
565
00:32:58,696 --> 00:33:03,846
So if you're preparing for certification,
be ready to answer those kinds of questions.
566
00:33:03,846 --> 00:33:07,576
You know, just based on these devices and
how they're connected, how many, you know,
567
00:33:07,576 --> 00:33:09,276
you'll see some hubs mixed in with switches.
568
00:33:09,276 --> 00:33:11,256
How many collision domains exist and all that.
569
00:33:11,256 --> 00:33:12,056
Now, there's a question.
570
00:33:12,316 --> 00:33:16,136
What if I take a hub and plug
it into that switch port?
571
00:33:16,456 --> 00:33:20,316
Okay, now how many collision domains do I have?
572
00:33:20,706 --> 00:33:24,096