-
Notifications
You must be signed in to change notification settings - Fork 1
/
mod2-01.html
298 lines (264 loc) · 15.9 KB
/
mod2-01.html
1
2
3
4
5
6
7
8
9
10
11
12
13
14
15
16
17
18
19
20
21
22
23
24
25
26
27
28
29
30
31
32
33
34
35
36
37
38
39
40
41
42
43
44
45
46
47
48
49
50
51
52
53
54
55
56
57
58
59
60
61
62
63
64
65
66
67
68
69
70
71
72
73
74
75
76
77
78
79
80
81
82
83
84
85
86
87
88
89
90
91
92
93
94
95
96
97
98
99
100
101
102
103
104
105
106
107
108
109
110
111
112
113
114
115
116
117
118
119
120
121
122
123
124
125
126
127
128
129
130
131
132
133
134
135
136
137
138
139
140
141
142
143
144
145
146
147
148
149
150
151
152
153
154
155
156
157
158
159
160
161
162
163
164
165
166
167
168
169
170
171
172
173
174
175
176
177
178
179
180
181
182
183
184
185
186
187
188
189
190
191
192
193
194
195
196
197
198
199
200
201
202
203
204
205
206
207
208
209
210
211
212
213
214
215
216
217
218
219
220
221
222
223
224
225
226
227
228
229
230
231
232
233
234
235
236
237
238
239
240
241
242
243
244
245
246
247
248
249
250
251
252
253
254
255
256
257
258
259
260
261
262
263
264
265
266
267
268
269
270
271
272
273
274
275
276
277
278
279
280
281
282
283
284
285
286
287
288
289
290
291
292
293
294
295
296
297
298
<!doctype html>
<html lang="en">
<head>
<meta charset="utf-8">
<title>Advanced Networking - Module 2 Chapter 1 - Introduction to Switched Networks</title>
<meta name="description" content="Abilitante alle certificazioni Cisco CCENT e CCNA">
<meta name="author" content="Hacklab Cosenza">
<meta name="apple-mobile-web-app-capable" content="yes">
<meta name="apple-mobile-web-app-status-bar-style" content="black-translucent">
<meta name="viewport" content="width=device-width, initial-scale=1.0, maximum-scale=1.0, user-scalable=no">
<link rel="stylesheet" href="css/reveal.css">
<link rel="stylesheet" href="css/theme/black.css" id="theme">
<!-- Code syntax highlighting -->
<link rel="stylesheet" href="lib/css/zenburn.css">
<!-- Printing and PDF exports -->
<script>
var link = document.createElement( 'link' );
var link = document.createElement( 'link' );
link.rel = 'stylesheet';
link.type = 'text/css';
link.href = window.location.search.match( /print-pdf/gi ) ? 'css/print/pdf.css' : 'css/print/paper.css';
document.getElementsByTagName( 'head' )[0].appendChild( link );
</script>
<!--[if lt IE 9]>
<script src="lib/js/html5shiv.js"></script>
<![endif]-->
</head>
<body>
<div class="reveal">
<!-- Any section element inside of this container is displayed as a slide -->
<div class="slides">
<section>
<h1>Advanced Networking</h1>
<h2>Routing & Switching:<h2>
<h2>Routing & Switching Essentials</h2>
<h3>Chapter 1: Introduction to Switched Networks</h3>
<p>
<small><a href="http://hlcs.it">Hacklab Cosenza</a> / Centro di Ricerca su Tecnologia e Innovazione</small>
</p>
</section>
<section>
<h2>Hyerarchical Network Design</h2>
<p>Cisco has a design guideline for network architecture called <em>Cisco Borderless Network</em>. Its principles are:</p>
<ul>
<li><strong>Hierarchy</strong> - Deploying complex systems in <u>tiers</u>, each with a clear role and structure.</li>
<li><strong>Modularity</strong> - Expansions, improvements, upgrades at any of these tiers are made as easy as possible.</li>
<li><strong>Resiliency</strong> - Network reacts well to changes, growth, faults.</li>
<li><strong>Flexibility</strong> - The network load is intelligently splitted to make the best use of resources.</li>
</ul>
<p>Time has proved that the best way to achieve the last 3 is through a <strong>hierarchical network architecture</strong>.</p>
</section>
<section>
<h2>Access, Distribution, Core</h2>
<img src="http://i.imgur.com/ugMjfRW.jpg">
<p>Tiers In a Cisco network architecture are <em><strong>Access, Distrubution and Core</strong></em>, usually deployed in a 3-tier or 2-tier (with <em>collapsed</em> Distribution/Core) framework.</p>
</section>
<section>
<h2>Access Layer</h2>
<ul>
<li>It's the network edge, where <strong>traffic enters or exits it</strong>.</li>
<li>It's also where devices that <strong>extend the network out one more level</strong> are placed - like IP phones, wireless APs, WAN connectivity.</li>
<li>It's primary function is to provide <strong>access to the network for most users</strong> (and thus generic computing devices, end stations access here).</li>
<li>This is the layer where <strong>most traffic originates</strong> from.</li>
<li>It provides the <strong>demarcation</strong> between the network infrastructure and the computing devices that leverage it.</li>
<li>The traditional focus at the access layer is <strong>minimizing <em>cost-per-port</em></strong>.</li>
</ul>
</section>
<section>
<h2>Distribution Layer</h2>
<ul>
<li>It's the most "smart" layer, <strong>implementing network foundation technologies</strong> like routing, advanced switching, filtering, QoS.</li>
<li><strong>Interface</strong> between Access and Core Layers:</li>
<ul>
<li><strong>Aggregation point for access switches</strong> (wiring closet).</li>
<li><strong>Aggregating L2 broadcast domains and L3 routing and summarization boundaries</strong> for network control plane protocols (EIGRP, OSPF, Spanning Tree).</li>
<li><strong>Demarcation and isolation</strong> between the campus distribution building block and the rest of the network.</li>
</ul>
<li><strong>Very little traffic originates</strong> directly from here.</li>
<li><strong>High availability</strong> through redundant distribution layer switches and <strong>equal cost paths to the core</strong>.</li>
</ul>
</section>
<section>
<h2>Core Layer (Backbone)</h2>
<ul>
<li>Very limited set of services, provides <u>24/7 always-on</u> (<em>Fault Isolation</em>) connectivity <u>across the entire network</u> (<em>end-to-end</em> connectivity).</li>
<li>Basically <strong>no traffic originates</strong> from here.</li>
<li>It serves as the <strong>aggregator</strong> for the other campus blocks and ties the campus together with the rest of the network.</li>
<li>Very little decisions about traffic, just <u>collects as much as possible, moves it as fast and reliably as possible</u>.</li>
<li>So: <strong>high-speed, high-redundancy forwarding</strong> services between "regions" (campus) of the network.</li>
<li>That means the <strong>most powerful switches</strong> and routers, capable of the fastest connections (e.g. 10 GiB Ethernet)</li>
</ul>
</section>
<section>
<h2>Choosing a Switch</h2>
<p>The typical parameters for choosing a switch are:</p>
<ul>
<li><strong>Cost</strong>: dependent by the trade-off involving all other parameters in function of the requirements.</li>
<li><strong>Port Density</strong>: number of ports available.</li>
<li><strong>Port Speed</strong>: network connection speed to users.</li>
<li><strong>Backplane</strong>: the maximum switching capacity.</li>
<li><strong>Power</strong>: Redundant power supply, PoE.</li>
<li><strong>Frame Buffers</strong>: the amount of frames that the switch can store before it must forward or discard them.</li>
<li><strong>Scalability</strong>: the ability of the switch to support network growth.</li>
<li><strong>Additional Features</strong>: like L3 supports, USB ports, etc.</li>
</ul>
</section>
<section>
<h2>Switch Form Factor</h2>
<p>Configuration options representing the switch <em>form factor</em>:</p>
<ul>
<li><strong>Fixed</strong> - These are switches that cannot be expanded with additional ports or port types.</li>
<li><strong>Modular</strong> - Chassis with free slots for installation of <em>modular line cards</em> that expand ports number/type.</li>
<li><strong>Stackable</strong> - <img style="float:right;" src="http://i.imgur.com/zEt76as.jpg"> Switches that can be interconnected with a high-bandwidth special cable, effectively operating as a single logical switch.</li>
<ul>
<li>Cisco Stackwise: up to 9 switches.</li>
<li>Cross-connected for fault tolerance.</li>
<li>Cisco StackPower for sharing PSUs.</li>
</ul>
</ul>
</section>
<section>
<h2>Switching Fundamentals</h2>
<p><em>Switching</em> is the process through which a device makes a decision about <strong>where to forward network traffic</strong>. It is based on the <em>ingress port</em> and the <em>destination address</em>.</p>
<p>This is true regardless of the port (technology) and address (protocol) type. Switching is a telecommunication concept.</p>
<ul>
<li><strong>Ingress</strong> - The spot where a frame enters a device.</li>
<li><strong>Egress</strong> - The spot where a frame leaves a device.</li>
<li>We'll typically talk about <em>ingress port(s)</em> and <em>egress port(s)</em>.</li>
</ul>
<p>A <em>LAN Switch</em>, the type we'll focus on, has the ability to build a table based on Ethernet MAC Addresses, called <strong>MAC Table</strong>, which we'll be used to make switching decisions.</p>
</section>
<section>
<h2>CAM Table</h2>
<img src="http://i.imgur.com/AZ06xwX.jpg" style="float: right;">
<p>Switches are made by dedicated-purposes motherboards (<em>ASICs</em>) that can internally move large amount of received frames at very high speed.</p>
<p>The switch has to build a <strong>MAC Table</strong> to make its decisions.</p>
<p>It's also called <strong>CAM table</strong> because of the specialized (<em>content addressable</em>) memory in which switches stores it.</p>
<ul>
<li>The MAC table associates each <strong>port with MAC addresses</strong>.</li>
<li>It is populated by <strong>examining source MAC adresses</strong>.</li>
</ul>
</section>
<section>
<section>
<h2>Frame Forwarding - Ingress</h2>
<ul>
<li>The MAC table is empty when the switch is first powered on.</li>
<li>When a frame is received, it looks at the <strong>source MAC address</strong>.</li>
<ul>
<li>If it's not on the table, an association is added between the source MAC and the ingress port the frame appeared on.</li>
<li>If it was already on the table, the <strong>aging timer</strong> of the association is reset. Maximum aging time is usually 5 min.</li>
</ul>
</ul>
</section>
<section>
<h2>Frame Forwarding - Egress</h2>
<ul>
<li>Then, it looks at the <strong>destination MAC address</strong></li>
<ul>
<li>If It's not on the table it <strong>forwards the frame to all ports</strong> except the ingress port. This is called <em>flooding</em>.</li>
<ul>
<li><strong>Only the destination will reply</strong> with a unicast frame. The switch can now add the missing association in the table.</li>
</ul>
<li>If It's already on the table, the switch forwards the frame to the <strong>associated egress port</strong>.</li>
</ul>
<li>Once all the associations have been learned the switch doesn't need flooding anymore.</li>
</ul>
</section>
</section>
<section>
<section>
<h2>Switching Methods</h2>
<img src="http://i.imgur.com/dMGP8Ue.gif">
<small>The figure above shows how many bytes of an incoming frame a switch needs to receive before making a forwarding decision, dependent of the switching method in use.</small>
</section>
<section>
<h2>Store & Fordward Switching</h2>
<p><em>Store and Forward Switching</em> makes a forwarding decision only <strong>after receiving the entirety of the frame</strong> and error-checking it.</p>
<p>It is the main switching method in a Cisco LAN switch.</p>
<p>After receiving the frame, the switch calculate its <em>checksum</em> (FCS). If it matches the frame's FCS value then it's forwarded through an egress port, <strong>otherwise it's dropped</strong>.</p>
<p>S&F switching could be problematic if the switch ingress and egress ports are operating at different speeds. That's why the switch automatically sets up an appropriate <strong>buffer</strong>.</p>
</section>
<section>
<h2>Cut-Through Switching</h2>
<p><em>Cut-Through Switching</em> makes a forwarding decision <strong>as soon as "enough" bytes</strong> of the frame as been received.</p>
<p>Thus with C-T switching the actual forwarding process begins <strong>before the frame has been completely received</strong>.</p>
<p>There are two variants of cut-through switching, and both of them <strong>do not perform a checksum verification</strong>:</p>
<ul>
<li><strong>Rapid Frame</strong> - The switch forwards the frame <u>as soon as the destination MAC address (first 6 bytes) is received</u>.</li>
<li><strong>Fragment Free</strong> - The switch waits for the first 64 bytes (<em>collision window</em>). <u>If no fragmentation is detected it then forwards the frame</u>.</li>
</ul>
</section>
<section>
<h2>Switching Methods Comparison</h2>
<ul>
<li>With Store & Forward switching <strong>invalid frames are never forwarded</strong>.</li>
<li>Cut-Through switching forwards <strong>almost every invalid frame</strong>.</li>
<li>Cut-through provides <strong>significantly better latencies</strong>.</li>
<li>In a network with a <strong>high error rate</strong>, C-T switching becomes counterproductive, wasting bandwidth with invalid frames.</li>
<li>Fragment-Free is usually the best <strong>compromise</strong>: a little better error checking with virtually no increase in latency.</li>
</ul>
</section>
</section>
<section>
<section>
<h2>Collision Domain</h2>
<p>A <em>collision domain</em> is a portion (<em>segment</em>) of the network where frames can physically collide if transmitted at the same time, because they <strong>share a common medium</strong> and its bandwidth.</p>
<p>Hubs constitute a single collision domain: a frame is forwarded on every port, making the medium <strong>unavailable to other transmissions in any direction</strong>.</p>
<p>A <strong>switch</strong> is capable (though <em>microsegmentation</em>) of <strong>reducing or avoiding the competition</strong> on a medium: either <strong>each port becomes its own collision domain</strong> (half-duplex links) or <strong>collisions are impossible</strong> (full-duplex).</p>
</section>
<section>
<h2>Collision Domain: Example</h2>
<img src="http://i.imgur.com/pFbYqnH.jpg" style="width: 600px; height: 600px;">
</section>
</section>
<section>
<section>
<h2>Broadcast Domain</h2>
<p>When a switch receives an <strong>Ethernet broadcast frame</strong> (all-1s source MAC), it floods it on every port. <u>Other connected switches will forward the frame in the same way</u>.</p>
<p>These behaviour allows to define the <em>broadcast domain</em>: the portion of a network in which devices <strong>can reach each other through broadcast frames at the data link layer</strong>.</p>
<p>They are said to <em>see each other at Layer 2</em>.</p>
</section>
<section>
<h2>Broadcast Domain</h2>
<p>Each interconnected switch <strong>increases the broadcast domain</strong>. A network layer/L3 device such as a <strong>router</strong> must be used to put boundaries on (<em>segment</em>) a broadcast domain.</p>
<p>Broadcast is necessary, but due to the way it propagates it can quickly produce a lot of traffic and slow-downs. A <strong>broadcast domain control</strong> strategy is essential.</p>
</section>
<section>
<h2>Broadcast Domain: Example</h2>
<img src="http://i.imgur.com/kOqSE6S.jpg" style="width: 720px; heigth: 600px;">
</section>
<section>
<h2>Broadcast Domain: Example</h2>
<img src="http://i.imgur.com/umu9uaK.jpg" style="width: 848px; heigth: 600px;">
</section>
</section>
<section>
<h1>End of Lesson</h1>
</section>
</div>
</div>
<script src="lib/js/head.min.js"></script>
<script src="js/reveal.js"></script>
<script>
// More info https://github.com/hakimel/reveal.js#configuration
Reveal.initialize({
controls: true,
progress: true,
history: true,
center: true,
transition: 'slide', // none/fade/slide/convex/concave/zoom
// More info https://github.com/hakimel/reveal.js#dependencies
dependencies: [
{ src: 'lib/js/classList.js', condition: function() { return !document.body.classList; } },
{ src: 'plugin/markdown/marked.js', condition: function() { return !!document.querySelector( '[data-markdown]' ); } },
{ src: 'plugin/markdown/markdown.js', condition: function() { return !!document.querySelector( '[data-markdown]' ); } },
{ src: 'plugin/highlight/highlight.js', async: true, callback: function() { hljs.initHighlightingOnLoad(); } },
{ src: 'plugin/zoom-js/zoom.js', async: true },
{ src: 'plugin/notes/notes.js', async: true }
]
});
</script>
</body>
</html>