All language subtitles for 8. Troubleshooting

af Afrikaans
sq Albanian
am Amharic
ar Arabic
hy Armenian
az Azerbaijani
eu Basque
be Belarusian
bn Bengali
bs Bosnian
bg Bulgarian Download
ca Catalan
ceb Cebuano
ny Chichewa
zh-CN Chinese (Simplified)
zh-TW Chinese (Traditional)
co Corsican
hr Croatian
cs Czech
da Danish
nl Dutch
en English Download
eo Esperanto
et Estonian
tl Filipino
fi Finnish
fr French
fy Frisian
gl Galician
ka Georgian
de German
el Greek
gu Gujarati
ht Haitian Creole
ha Hausa
haw Hawaiian
iw Hebrew
hi Hindi
hmn Hmong
hu Hungarian
is Icelandic
ig Igbo
id Indonesian
ga Irish
it Italian
ja Japanese
jw Javanese
kn Kannada
kk Kazakh
km Khmer
ko Korean
ku Kurdish (Kurmanji)
ky Kyrgyz
lo Lao
la Latin
lv Latvian
lt Lithuanian
lb Luxembourgish
mk Macedonian
mg Malagasy
ms Malay
ml Malayalam
mt Maltese
mi Maori
mr Marathi
mn Mongolian
my Myanmar (Burmese)
ne Nepali
no Norwegian
ps Pashto
fa Persian
pl Polish
pt Portuguese Download
pa Punjabi
ro Romanian
ru Russian
sm Samoan
gd Scots Gaelic
sr Serbian
st Sesotho
sn Shona
sd Sindhi
si Sinhala
sk Slovak
sl Slovenian
so Somali
es Spanish
su Sundanese
sw Swahili
sv Swedish
tg Tajik
ta Tamil
te Telugu
th Thai
tr Turkish
uk Ukrainian
ur Urdu
uz Uzbek
vi Vietnamese
cy Welsh
xh Xhosa
yi Yiddish
yo Yoruba
zu Zulu
or Odia (Oriya)
rw Kinyarwanda
tk Turkmen
tt Tatar
ug Uyghur
Would you like to inspect the original subtitles? These are the user uploaded subtitles that are being translated: 1 00:00:00,750 --> 00:00:04,160 It on like section we're going to take a look to the troubleshooting 2 00:00:07,100 --> 00:00:14,600 troubleshooting is the process of diagnosing a problem and if possible resolving it the troubleshooting 3 00:00:14,600 --> 00:00:22,910 process is usually triggered when a person or a mentoring system reports a problem was the person reporting 4 00:00:22,910 --> 00:00:23,500 the problem. 5 00:00:23,510 --> 00:00:27,780 Often use clues about the symptoms of the problem. 6 00:00:27,860 --> 00:00:34,490 The trouble shooter the person who is going to have the problem has to find the root cause of the problem 7 00:00:34,520 --> 00:00:40,640 and the trouble shooter will be you guys most of the times. 8 00:00:40,710 --> 00:00:47,750 Let's go with it the stats of the trouble shooting the trouble shooting steps are the three steps. 9 00:00:47,750 --> 00:00:51,200 The first step is identifying the problem. 10 00:00:51,200 --> 00:01:01,460 This second is isolating the problem and the third is implementing a correct action and fix it to identify 11 00:01:01,460 --> 00:01:08,610 the problem to isolate the problem and to implement a quick action as well. 12 00:01:08,720 --> 00:01:15,250 And the users are your best friend always guys. 13 00:01:15,450 --> 00:01:18,840 Let's go over to troubleshooting commands. 14 00:01:18,970 --> 00:01:20,870 They're playing. 15 00:01:21,210 --> 00:01:32,300 Trace route S-sh Shumaker risk Thabo shoy interface breath swipe you troll on and the dieback commands 16 00:01:32,680 --> 00:01:38,300 to use for trouble shooting. 17 00:01:38,670 --> 00:01:45,330 We have two kinds of troubleshooting tools and there are software troubleshoot and they hardware trouble 18 00:01:45,370 --> 00:01:46,210 shoot to 19 00:01:49,050 --> 00:01:57,270 let's to using the overside module for troubleshooting we had some trouble shooting to skies and their 20 00:01:57,660 --> 00:02:06,680 top down bottom up the word on can clear for the path Saputo differences and the move the problem and 21 00:02:06,680 --> 00:02:15,900 up did go much deeper for this age solutions but I'm going to show you an example for example top down 22 00:02:15,900 --> 00:02:25,250 means we need to go downward from the oversize application like for example if one of your users reported 23 00:02:25,250 --> 00:02:29,840 a problem such that I can not serve on the Internet. 24 00:02:29,910 --> 00:02:37,630 The first thing I'm going to focus on is the application layer of the site which is I'm going to go. 25 00:02:37,890 --> 00:02:45,360 My friend please check the browser for example that you're using if you're using Chrome change it to 26 00:02:45,360 --> 00:02:48,900 operate and do it try to surf again. 27 00:02:49,020 --> 00:02:51,680 Then we're going to go down. 28 00:02:52,020 --> 00:02:57,230 Maybe I can check the network layer in here. 29 00:02:57,420 --> 00:03:04,440 I can check the IP address of this guy and if I and I can see that if it's obtaining the right IP address 30 00:03:04,440 --> 00:03:05,490 or not. 31 00:03:05,670 --> 00:03:10,030 Or maybe I can't check them they're telling clear for example. 32 00:03:10,050 --> 00:03:14,330 I can't check the lead to meters of that guy's Internet. 33 00:03:14,520 --> 00:03:17,350 And lastly I can say the guy for example. 34 00:03:17,350 --> 00:03:24,010 Hey man please check your cables if your cables are connected or not properly. 35 00:03:24,180 --> 00:03:24,970 OK. 36 00:03:25,050 --> 00:03:31,940 They're still using for the or some modules for the troubleshooting as an example. 37 00:03:32,370 --> 00:03:36,840 And here is how we can T-shaped the IP connectivity step by step. 38 00:03:36,840 --> 00:03:45,580 For example for us we can check the layer one for errors or up or down say it's there we can check a 39 00:03:45,570 --> 00:03:47,380 duplex mismatch. 40 00:03:47,520 --> 00:03:55,140 We can check the MAC addresses IP addresses ARP tables we can check the ports or we can check the ACLU 41 00:03:55,170 --> 00:03:58,260 or DNS as well. 42 00:03:58,800 --> 00:04:09,180 Let's go to spend now spend switched ports analyzer is an efficient high performance traffic monitoring 43 00:04:09,180 --> 00:04:10,350 system. 44 00:04:10,490 --> 00:04:18,300 There it's all mirrors traffic from a source port to our bill and to a destination port. 45 00:04:18,300 --> 00:04:25,050 This is sometimes referred to as session month or AInc span is used for troubleshooting connectivity 46 00:04:25,050 --> 00:04:32,150 issues and calculating network utilization and performance among many others. 47 00:04:32,310 --> 00:04:40,170 And here's the comfort here's how we can use the span for using the sperm for example if we want to 48 00:04:40,170 --> 00:04:41,390 worst traffic. 49 00:04:41,400 --> 00:04:54,260 If you want to mirror the traffic from Port 5 to port nine we're using a network analyzer to our ports. 50 00:04:54,600 --> 00:05:01,690 And we're simply mirroring our traffic form port to the port nine. 51 00:05:01,710 --> 00:05:12,920 As you can see here we have two types of spen and there are local span and the remote spare local locals 52 00:05:12,930 --> 00:05:20,300 mirrors the traffic between ports in the same switch remote span is similar to span. 53 00:05:20,460 --> 00:05:29,220 But it's support source ports source Whelan's and destination ports on different survey edge. 54 00:05:29,250 --> 00:05:35,070 For example if you want to configure a local span on your unswitched UK is the morning session and the 55 00:05:35,070 --> 00:05:40,630 session number command and you define the source and the destination interfaces. 56 00:05:40,680 --> 00:05:42,570 That's pretty straightforward. 57 00:05:42,570 --> 00:05:45,730 As you can see to configure it let's go with that. 58 00:05:45,750 --> 00:05:54,380 I piss away I personally is a Cisco proprietary Iris feature that ellos to collect information. 59 00:05:54,420 --> 00:06:02,700 For example response time latency Jinder and the of applause about network performance in the real time 60 00:06:03,930 --> 00:06:07,570 and here's the configuration of the IP SLA to come for your day. 61 00:06:07,590 --> 00:06:17,240 I personally for rather world for example are defining an IP of solid proof for us by tapping IP SLA 62 00:06:17,270 --> 00:06:20,900 and for example a number which is one in here. 63 00:06:21,120 --> 00:06:24,520 There we are defining an ICMP call. 64 00:06:24,720 --> 00:06:33,970 Or rather what I'm doing is I'm sending ping packets to this interface of the tree and I'm doing this 65 00:06:33,970 --> 00:06:37,900 action for aged 20 seconds. 66 00:06:38,070 --> 00:06:47,880 The frequency commands shows the frequency of the ICMP packets that I'm sending for then I'm using a 67 00:06:47,880 --> 00:07:00,120 schedule for my IP SLA and I'm typing IP a KGO one stop time and now and life will be for ever and defining 68 00:07:00,120 --> 00:07:06,960 the time range that I'm using this IP SLA to verify the silly configuration. 69 00:07:06,990 --> 00:07:18,180 I can show I pixelate configuration command and I can check the target address source address and Operation 70 00:07:18,180 --> 00:07:25,230 timeout and enter a number or some more informations like that. 71 00:07:25,290 --> 00:07:34,630 The second method that I can find the IP Eslick configuration is using the show IP SLA statistics comments 72 00:07:35,040 --> 00:07:43,080 and we can check the latest operations our time latest operation returned card number of success and 73 00:07:43,080 --> 00:07:47,610 number of failures are some more information like that. 7995

Can't find what you're looking for?
Get subtitles in any language from opensubtitles.com, and translate them here.