-
Notifications
You must be signed in to change notification settings - Fork 1
/
mod1-11.html
563 lines (492 loc) · 26.6 KB
/
mod1-11.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
299
300
301
302
303
304
305
306
307
308
309
310
311
312
313
314
315
316
317
318
319
320
321
322
323
324
325
326
327
328
329
330
331
332
333
334
335
336
337
338
339
340
341
342
343
344
345
346
347
348
349
350
351
352
353
354
355
356
357
358
359
360
361
362
363
364
365
366
367
368
369
370
371
372
373
374
375
376
377
378
379
380
381
382
383
384
385
386
387
388
389
390
391
392
393
394
395
396
397
398
399
400
401
402
403
404
405
406
407
408
409
410
411
412
413
414
415
416
417
418
419
420
421
422
423
424
425
426
427
428
429
430
431
432
433
434
435
436
437
438
439
440
441
442
443
444
445
446
447
448
449
450
451
452
453
454
455
456
457
458
459
460
461
462
463
464
465
466
467
468
469
470
471
472
473
474
475
476
477
478
479
480
481
482
483
484
485
486
487
488
489
490
491
492
493
494
495
496
497
498
499
500
501
502
503
504
505
506
507
508
509
510
511
512
513
514
515
516
517
518
519
520
521
522
523
524
525
526
527
528
529
530
531
532
533
534
535
536
537
538
539
540
541
542
543
544
545
546
547
548
549
550
551
552
553
554
555
556
557
558
559
560
561
562
563
<!doctype html>
<html lang="en">
<head>
<meta charset="utf-8">
<title>Advanced Networking - Module 1 Chapter 11 - It's a Network</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/hlcs.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>Introduction to Networks</h2>
<h3>Chapter 11: Build a Small Network</h3>
<small><a href="http://hlcs.it">Hacklab Cosenza</a> / Centro di Ricerca su Tecnologia e Innovazione</small>
</section>
<section>
<h2>Small Business' Networks</h2>
<p>The knowledge required to run a small network is similar to the one for a larger network. It is the number of devices involved that changes.</p>
<p>Small network typically involve a single router, a single WAN connection, one or more switches and APs (often integrated in one device).</p>
<p>The management can be done by an employee or a contractor.</p>
</section>
<section>
<h2>Factors in Selecting a Device</h2>
<ul>
<li><strong>Cost</strong>: capacity, features, available ports, type of ports, backplane speed, they all influence how expensive a device is. But there are device-independent costs like:</li>
<ul>
<li><strong>Cable Runs</strong>: the devices have to be connected together.</li>
<li><strong>Redundancy</strong>: no matter which devices are selected, redundancy requires more of them.</li>
</ul>
<li><strong>Speed/Type/Number of Ports</strong>: We have to decide whether to choose based on present or future needs also.</li>
<ul>
<li><strong>Expandability</strong>: additional modules offer flexibility, but you still have to think about your needs.</li>
</ul>
<li><strong>Software Features</strong>: has the NOS every functionality I need from it? VPNs, QoS, routing protocols, NAT, etc.</li>
</ul>
</section>
<section>
<h2>Redundancy</h2>
<img src="http://i.imgur.com/xma5uuw.jpg" style="float: left;">
<p>Redundancy provides networks with <strong>reliability</strong>. It is achieved by <strong>duplicating</strong>: devices, links, power supplies, services.</p>
<p>Redundancy can be introduced progressively, starting with a second connection between multiple intermediary devices.</p>
<p>Small networks have typically one gateway to the Internet. A backup connection to a second ISP can be considered.</p>
</section>
<section>
<h2>Small Network Design Checklist</h2>
<ol>
<li>Create centralized locations for network resources and intermediary devices.</li>
<li>Secure unauthorized <em>physical</em> access.</li>
<li>Secure unauthorized <em>logical</em> access.</li>
<li>Create <em>physical</em> redundancy.</li>
<li>Create <em>logical</em> redundancy.</li>
<li>Understand the traffic flowing in the network in order to implement necessary priorities.</li>
</ol>
</section>
<section>
<h2>Software in a Small Network</h2>
<p>Software that makes use of the network can be divided in:</p>
<ul>
<li><strong>Network Applications</strong>: these are the applications that know how to use the network directly (<em>network-aware</em>) because they implement L7 protocols themselves (email clients and browsers are common examples).</li>
<li><strong>Network Services</strong>: these are stand-alone Application Layer protocols implementations that can be used by other applications that need to send data over the network. Print spooling, network file systems are good examples of L7 Services.</li>
</ul>
</section>
<section>
<h2>Real-Time Applications</h2>
<p>Real-time applications are the ones that stress the most a network design, because they rely on <strong>priority delivery</strong>.</p>
<p>Typical examples are <strong>Voice Over IP (VoIP)</strong> and <strong>IP Telephony</strong>. The difference being whether the voice-to-IP conversion is performed by the phone. However, <strong>VoIP</strong> is the go-to term.</p>
<p>Real-Time applications need protocols that supports <em><strong>delay-sensitive delivery</strong></em> and QoS, like <strong>RTP (Real-Time Transport Protocol)</strong> or <strong>RTCP (Real-Time Transport Control Protocol)</strong>.</p>
<p>Often <strong>QoS is implemented in-hardware</strong>.</p>
</section>
<section>
<section>
<h2>From Small to Larger Network</h2>
<p>Networks can grow either <em>reactively</em> (<u>responding</u> to needs) or <em>proactively</em> (<u>anticipating</u> needs). It is clearly better to grow the network alongside its needs.</p>
<p>To carefully plan the <strong><em>scaling</em></strong> of a network you need: <strong>documentation, inventory, budget, traffic analysis</strong>.</p>
</section>
<section>
<h2>From Small to Larger Network</h2>
<p><strong>Traffic/Protocol analysis</strong> allows an administrator to collect statistics about the traffic flowing in the network. With the right data, optimizations can be made. Some suggestions:</p>
<ul>
<li>Analyze the traffic in the <strong>peak hours</strong>.</li>
<li>Analyze traffic globally, but also in <strong>each specific segment</strong>.</li>
<li>Document employee-<em>snapshots</em> over time.</li>
</ul>
<p>Analysis could reveal <strong>optimization paths that are trivial</strong>, or others requiring <strong>major overhaul</strong> of the network design.</p>
</section>
</section>
<section>
<h2>Types of Network Threats</h2>
<ul>
<li><strong>Information Theft</strong>: information is obtained that was meant to be confidential and it's now out of control and can be used, sold or otherwise damage the victim.</li>
<li><strong>Identity Theft</strong>: like the above, but the information allows the attacker to assume someone else's identity in order to achieve access or other type of unauthorized usage.</li>
<li><strong>Data Loss or Tampering</strong>: computer data that is purposefully damaged to harm the owner of the data, or altered to obtain an advantage.</li>
<li><strong>Disruption of Service</strong>: even without breaking into a system, attackers can impede legitimate users of a service to access it.</li>
</ul>
</section>
<section>
<h2>Physical Security</h2>
<p>Device physical protection is as important as protecting the software stack. The Attacker can be an outsider, but <strong>we can also play our (negative) part</strong> in these categories of threats:</p>
<ul>
<li><strong>Unauthorized Access</strong>: if an attacker is right in front of your devices, many software protections are useless.</li>
<li><strong>Hardware</strong>: intentional physical damage to hosts or links.</li>
<li><strong>Environmental</strong>: making a device operate outside of its temperature window.</li>
<li><strong>Electrical</strong>: over/under-voltage, partial/unstable/total power loss, incorrect grounding, electrostatic discharge.</li>
<li><strong>Maintenance</strong>: no labeling, poor cabling, lack of spares.</li>
</ul>
</section>
<section>
<h2>Vulnerabilities</h2>
<p>Vulnerabilities can be found in:</p>
<ul>
<li><strong>Technology</strong> - Protocols, software, operating systems, they all have flaws which can be exploited.</li>
<li><strong>Configuration</strong> - Unsecured, unused user accounts; weak passwords; unused and unsecured software and services; weak default settings; general misconfigurations.</li>
<li><strong>Policy</strong> - Unwritten security policies; politics; unapplied security policies; inadequate monitoring; unauthorized and undocumented changes; lack of a recovery plan.</li>
</ul>
</section>
<section>
<section>
<h2>Malicious Code</h2>
<p>There are programs (collectively known as <strong><em>malware</em></strong>) created for the purpose of causing harm:</p>
<ul>
<li><strong>Viruses</strong> - Software included in another programs to perform malicious functions. Often human interactions is required.</li>
<li><strong>Worms</strong> - Stand-alone applications written to exploit targeted vulnerabilities. They don't need human interaction.</li>
<li><strong>Trojan Horses</strong> - Applications that are written to appear normal, while performing attacks on the system.</li>
</ul>
</section>
<section>
<h2>Malicious Code</h2>
<p>In order to be executed, malicious code attacks need:</p>
<ul>
<li>Some <strong>vulnerability to exploit</strong>, whether software or human.</li>
<li>A <strong>propagation mechanism</strong> to spread themselves.</li>
<li>The actual <strong>payload</strong> to propagate and execute.</li>
</ul>
</section>
</section>
<section>
<section>
<h2>Reconnaissance</h2>
<p><em>Reconnaissance</em> involves the <strong>search, discovery and mapping</strong> of vulnerabilities in victim's systems.</p>
<ul>
<li><strong>Queries</strong> - Tools like <code>nslookup</code> or <code>whois</code> can be used to determine the address space belonging to the victim.</li>
<li><strong>Mass Pings</strong> - The attacker uses tools to automatically ping large block of addresses to discover the active ones.</li>
<li><strong>Port Scanning</strong> - Using automated tools like <code>nmap</code> an attacker can discover the transport layer ports that are opened on a system.</li>
<li><strong>Packet Sniffing</strong> - If an attacker takes control of a system along the traffic paths, He can monitor traffic using software like Wireshark.</li>
</ul>
</section>
<section>
<h2>Reconnaisance</h2>
<pre><code class="bash">stefanauss@barney:~$ nslookup hlcs.it
Server: 127.0.1.1
Address: 127.0.1.1#53
Non-authoritative answer:
Name: hlcs.it
Address: 188.165.254.131
stefanauss@barney:~$ nslookup 188.165.254.131
Server: 127.0.1.1
Address: 127.0.1.1#53
Non-authoritative answer:
131.254.165.188.in-addr.arpa name = ks381122.kimsufi.com.
Authoritative answers can be found from:
stefanauss@barney:~$ whois hlcs.it
*********************************************************************
* Please note that the following result could be a subgroup of *
* the data contained in the database. *
* *
* Additional information can be visualized at: *
* http://www.nic.it/cgi-bin/Whois/whois.cgi *
*********************************************************************
Domain: hlcs.it
Status: ok
Created: 2012-10-02 22:07:03
Last Update: 2014-10-18 00:43:12
Expire Date: 2015-10-02
Registrant
Organization: SOCIETA' COOPERATIVA COOPYLEFT A R.L.
Admin Contact
Name: Vincenzo Bruno
Organization: SOCIETA' COOPERATIVA COOPYLEFT A R.L.
Technical Contacts
Name: Unità Tecnica Tophost
Organization: Tophost srl
Address: Piazza della Libertà 10
Roma
00192
RM
IT
Created: 2009-09-28 11:25:11
Last Update: 2011-08-18 13:47:40
Registrar
Organization: Seeweb S.r.l.
Name: TOPHOST-REG
Web: http://www.tophost.it
Nameservers
ns1.th.seeweb.it
ns2.th.seeweb.it
stefanauss@barney:~$ nmap scanme.nmap.org
Starting Nmap 6.40 ( http://nmap.org ) at 2014-12-05 01:10 CET
Nmap scan report for scanme.nmap.org (74.207.244.221)
Host is up (0.23s latency).
Not shown: 997 closed ports
PORT STATE SERVICE
22/tcp open ssh
80/tcp open http
9929/tcp open nping-echo
Nmap done: 1 IP address (1 host up) scanned in 20.66 seconds
</code></pre>
</section>
</section>
<section>
<section>
<h2>Access Attacks</h2>
<p>When <strong>unauthorized</strong> (attempted or successful) access to systems and exploitation of user privileges takes place.</p>
<ul>
<li><strong>Password Attacks</strong> - They can be performed with trojan horses, packet sniffers or as <em>brute force</em> attacks.</li>
<li><strong>Trust Exploitation</strong> - Instead of attacking a system directly, the attacker takes control of a system or service (e.g. Active Directory, or NFS) trusted by the victim.</li>
<li><strong>Port Redirection</strong> - A case of trust exploitation where an attacker compromises an host to bypass firewall rules that drops direct attacks (see the next slide).</li>
<li><strong>Man-In-The-Middle</strong> - The attacker acquires the ability to monitor an exchange, altering traffic and injecting it.</li>
</ul>
</section>
<section>
<h2>Port Redirection Attacks</h2>
<img src="http://i.imgur.com/RuDvYTo.jpg">
</section>
</section>
<section>
<section>
<h2>Denial of Service</h2>
<p>There are many types of DoS attacks. They all target the <strong>exhaustion of system and network resources</strong> to the point where it's hard or impossible to legitimately use them.</p>
<p>Some kinds of Denial of Service attacks are:</p>
<ul>
<li><strong>Ping of Death</strong> - Malformed, large (more than IP maximum size) ICMP packets that are meant to crash receiving hosts.</li>
<li><strong>SYN Flood</strong> - The attacker begins (SYN) a lot of TCP 3-Way Handshakes without ever completing them (SYN ACK).</li>
<li><strong>Distributed Denial of Service (DDoS)</strong> - When the attacker has a large number of compromised systems (<em>Handlers</em> and <em>Zombies</em>) at his disposal, simultaneously targeting a victim.</li>
</ul>
</section>
<section>
<h2>Network Attacks - Smurf</h2>
<img src="http://i.imgur.com/TvNS5xK.gif" style="width:700px;">
<ul>
<li><strong>Smurf Attack</strong> - The attacker directs large amount of traffic to a victim by using the <em>spoofed</em> address as source, and a broadcast address as destination of malformed packets.</li>
</ul>
</section>
</section>
<section>
<section>
<h2>Network Attack Mitigation</h2>
<p>If an attack is successful, administrators have to perform these steps in order to regain control:</p>
<ul>
<li><strong>Containment</strong></li>
<li><strong>Inoculation</strong> (<em>immunization</em>)</li>
<li><strong>Quarantine</strong></li>
<li><strong>Treatment</strong></li>
</ul>
<p>A central <u>patch server</u>, <u>automatic updates</u>, and a <u>standard software image</u> can be good strategies to keep systems secure.</p>
</section>
<section>
<h2>Network Attack Mitigation</h2>
<p>The <strong><em>Triple A</em></strong> governs access control by providing:</p>
<ul>
<li><strong>Authentication</strong> - Who is permitted to access the network. <em>Local</em> authentication, like authentication commands on IOS, doesn't scale. External authentication like <strong>RADIUS</strong> or <strong>TACACS+</strong>, is recommended for large networks.</li>
<li><strong>Authorization</strong> - What authorized users can or cannot do.</li>
<li><strong>Accounting</strong> - Keeping tracks (<em>logging</em>) of accessed resources and users' activity on a network.</li>
</ul>
</section>
</section>
<section>
<section>
<h2>Firewalls</h2>
<p>Firewalls are systems placed between networks, <strong>controlling the traffic flow</strong> between them using several techniques:</p>
<ul>
<li><strong>Packet Filtering</strong> based on L2 or L3 addresses.</li>
<li><strong>Application Filtering</strong> based on port numbers and associated applications.</li>
<li><strong>URL filtering</strong> targeted at specific websites or keywords.</li>
<li><strong>Stateful Packet Inspection (SPI)</strong> can recognize if incoming packets are responses or unsolicited traffic, and also alarming patterns in traffic (typical of DDoS).</li>
<li><strong>Network Address Translation</strong> is often performed by firewalls, and it allows to hide internal IP addresses.</li>
</ul>
</section>
<section>
<h2>Firewalls</h2>
<p>Firewall can take differents forms, such as:</p>
<ul>
<li><strong>appliances</strong> (dedicated hardware)</li>
<li><strong>server software</strong> (running on a full OS)</li>
<li><strong>integrated</strong> (in multi-purpose devices)</li>
<li><strong>personal firewalls</strong> (on each host)</li>
</ul>
</section>
</section>
<section>
<h2>Basic Security Practices</h2>
<ul>
<li>Don't rely on <strong>default settings</strong> being secure, review them!</li>
<li>Change default username and passwords.</li>
<li><em>Principle of Least Priviledge</em>: configure permissions to user to provide access only to the minimum extent necessary.</li>
<li><em>Least Attack Surface</em>: uninstall or disable unused services.</li>
<li>New device != up-to-date device. Patch first!</li>
<li>The longer the password, the better. Use <strong>passphrases</strong>.</li>
<li>Avoid dictionary words, common, easy to guess patterns.</li>
<li><strong>Entropy</strong> is good: <strong>mispell</strong> the passwords, <strong>mix</strong> the letter case, symbols, numbers.</li>
<li>Change the password often to reduce opportunity window and <u>do not write it down</u>.</li>
</ul>
</section>
<section>
<section>
<h2>Securing Cisco IOS - Attempts</h2>
<pre><code class="bash">Router(config)# service password-encryption
Router(config)# security password min-length 8
Router(config)# login block-for 240 attempts 3 within 60
Router(config)# line console 0
Router(config-line)# exec-timeout 10
Router(config-line)# end</code></pre>
<p><code>exec timeout</code> tells the device to automatically disconnect logged-in users after the specified number of minutes of <u>inactivy</u> (<em>idle</em>).</p>
</section>
<section>
<h2>Securing Cisco IOS - SSH</h2>
<pre><code class="bash">Router(config)# ip domain-name hlcs.it
Router(config)# crypto key generate rsa
The name for the keys will be: Router.hlcs.it
Choose the size of the key modulus in the range of 360 to 2048 for your
General Purpose Keys. Choosing a key modulus greater than 512 may take
a few minutes.
How many bits in the modulus [512]: 2048
% Generating 2048 bit RSA keys, keys will be non-exportable...[OK]
*Dec 5 03:12:52.628: %SSH-5-ENABLED: SSH 1.99 has been enabled
Router(config)# username HLCS secret cisco
Router(config)# line vty 0 15
Router(config-line)# login local
Router(config-line)# transport input ssh</code></pre>
<ul>
<li><code>crypto key generate rsa</code> uses the RSA algorhythm to generate encryption keys.</li>
<li><code>login local</code> enables password checking against a user database on the device.</li>
<li><code>transport input [protocol]</code> specifies which protocol are enabled to access a specific configuration line with.</li>
</ul>
</section>
</section>
<section>
<h2>Network Baseline</h2>
<p>Establishing a <em>network baseline</em> means detailing network performances over time to create a <strong>reference point</strong>.</p>
<p>Basic performance tests like <code>ping</code> or <code>traceroute</code> should be executed at different times of the day, days of the week, and <strong>stored as documentation for future comparisons</strong>.</p>
<p>There are integrated softwares that manage the creation and storage of large and detailed baselines.</p>
</section>
<section>
<h2>Extended Ping</h2>
<p>On Cisco IOS, by typing <code>ping</code> in privileg EXEC mode, without an address, an <strong>extended ping</strong> mode is accessed.</p>
<pre><code class="no-highlight">R2# ping
Protocol [ip]:
Target IP address: 10.87.7.1
Repeat count [5]:
Datagram size [100]:
Timeout in seconds [2]:
Extended commands [n]: y
Source address or interface: 10.87.23.1
Type of service [0]:
Set DF bit in IP header? [no]:
Validate reply data? [no]:
Data pattern [0xABCD]:
Loose, Strict, Record, Timestamp, Verbose[none]:
Sweep range of sizes [n]:
Type escape sequence to abort.
Sending 5, 100-byte ICMP Echos to 10.87.7.1, timeout is 2 seconds:
!!!!!
Success rate is 100 percent (5/5), round-trip min/avg/max = 36/97/132 ms </code></pre>
</section>
<section>
<h2>Extended Traceroute</h2>
<p>Cisco IOS <code>traceroute</code> implementation uses a different approach (as Linux does) than pure ICMP Echo Request/Reply. It sends <strong>UDP datagrams</strong>, always with incrementing TTL values.</p>
<pre><code class="no-highlight">R2#traceroute
Protocol [ip]:
Target IP address: 192.168.40.2
Source address: 172.16.23.2
Numeric display [n]:
Timeout in seconds [3]:
Probe count [3]:
Minimum Time to Live [1]:
Maximum Time to Live [30]:
Port Number [33434]:
Loose, Strict, Record, Timestamp, Verbose[none]:
Type escape sequence to abort.
Tracing the route to 192.168.40.2
1 172.31.20.2 16 msec 16 msec 16 msec
2 172.20.10.2 28 msec 28 msec 32 msec
3 192.168.40.2 32 msec 28 msec *
</code></pre>
</section>
<section>
<section>
<h2>Cisco Discovery Protocol</h2>
<p>CDP is a <strong>proprietary protocol by Cisco</strong> that allows a device to learn hardware and software information about <strong>other devices directly connected</strong> to it.</p>
<p>CDP runs at L2, so it can operate <strong>even if there is no network layer connectivity</strong> or different L3 protocols are running.</p>
<p>It provides details like <strong>Device identifiers, address list, port identifiers, capabilities, platform</strong>.</p>
<p>CDP is <strong>enabled by default</strong> on Cisco IOS, but it can represent a <strong>security risk</strong>. It can be disabled globally with the command <code>no cdp run</code>, or per-interface with the command <code>no cdp enable</code>.</p>
</section>
<section>
<h2>Cisco Discovery Protocol</h2>
<pre><code class="no-highlight" style="max-height: 250px;">Router1# show cdp neighbors
Capability Codes: R - Router, T - Trans Bridge, B - Source Route Bridge
S - Switch, H - Host, I - IGMP, r - Repeater
Device ID Local Intrfce Holdtme Capability Platform Port ID
Router2 Ser 0/0 179 R I 2621 Ser 0/1
Switch1 Fas 1/0 152 S I WS-C2924 Gig 2/2</code></pre>
<pre><code class="no-highlight" style="max-height: 250px;">Router1#show cdp neighbors detail
-------------------------
Device ID: Router2
Entry address(es):
IP address: 10.1.1.2
Platform: cisco 2621, Capabilities: Router
Interface: Serial0/0, Port ID (outgoing port): Serial0/1
Holdtime : 136 sec
Version :
Cisco Internetwork Operating System Software
IOS (tm) C2600 Software (C2600-IK9O3S-M), Version 12.2(13), RELEASE SOFTWARE (fc1)
Copyright (c) 1986-2002 by cisco Systems, Inc.
Compiled Tue 19-Nov-02 22:27 by pwade
advertisement version: 2
Device ID: Switch1
Entry address(es):
IP address: 172.25.1.4
Platform: WS-C2924, Capabilities: Trans-Bridge Switch
Interface: FastEthernet1/0, Port ID (outgoing port): FastEthernet0/12
Holdtime : 116 sec
Version :
Cisco Internetwork Operating System Software
IOS (tm) C2900XL Software (C2900XL-C3H2S-M), Version 12.0(5)WC3b, RELEASE SOFTWARE (fc1)
Copyright (c) 1986-2002 by cisco Systems, Inc.
Compiled Fri 15-Feb-02 10:14 by antonino
advertisement version: 2
Duplex: full</code></pre>
</section>
</section>
<section>
<h2>Cisco IOS Debugging</h2>
<p>Processes and protocols running on Cisco IOS <strong>generate messages</strong> during their operation the can be helpful during troubleshooting.</p>
<p>The <code>(#) debug</code> command allows these messages to <strong>appear in real-time</strong> on the console. They can be quite a lot, so <strong>debug can be activated for each single feature</strong> or area of interest.</p>
<pre><code class="no-highlight">! Enable ICMP message logging
Router# debug ip icmp
! Disable it
Router# no debug ip icmp
! Disable all debug messages of all types
Router# undebug all</code></pre>
<p>By default, Cisco IOS prints debug messages only on the console connection. To have them available over virtual terminals (SSH and Telnet connections), use <code>(#) terminal monitor</code>.</p>
</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>