All language subtitles for 8. Troubleshooting

ak Akan
sq Albanian
am Amharic
hy Armenian
az Azerbaijani
eu Basque
be Belarusian
bem Bemba
bh Bihari
bs Bosnian
br Breton
km Cambodian
ca Catalan
ceb Cebuano
chr Cherokee
ny Chichewa
zh-CN Chinese (Simplified)
zh-TW Chinese (Traditional)
co Corsican
hr Croatian
cs Czech
da Danish
eo Esperanto
et Estonian
ee Ewe
fo Faroese
tl Filipino
fi Finnish
fr French
fy Frisian
gaa Ga
gl Galician
ka Georgian
de German
el Greek
gn Guarani
gu Gujarati
ht Haitian Creole
ha Hausa
haw Hawaiian
iw Hebrew
hmn Hmong
hu Hungarian
is Icelandic
ig Igbo
ia Interlingua
ga Irish
it Italian
ja Japanese
jw Javanese
kn Kannada
kk Kazakh
rw Kinyarwanda
rn Kirundi
kg Kongo
ko Korean
kri Krio (Sierra Leone)
ku Kurdish
ckb Kurdish (Soranรฎ)
ky Kyrgyz
lo Laothian
la Latin
lv Latvian
ln Lingala
lt Lithuanian
loz Lozi
lg Luganda
ach Luo
lb Luxembourgish
mk Macedonian
mg Malagasy
ms Malay
mt Maltese
mi Maori
mr Marathi
mfe Mauritian Creole
mo Moldavian
mn Mongolian
my Myanmar (Burmese)
sr-ME Montenegrin
ne Nepali
pcm Nigerian Pidgin
nso Northern Sotho
no Norwegian
nn Norwegian (Nynorsk)
oc Occitan
or Oriya
om Oromo
ps Pashto
fa Persian
pl Polish
pt-BR Portuguese (Brazil) Download
pt Portuguese (Portugal) Download
pa Punjabi
qu Quechua
ro Romanian
rm Romansh
nyn Runyakitara
ru Russian
sm Samoan
gd Scots Gaelic
sr Serbian
sh Serbo-Croatian
st Sesotho
tn Setswana
crs Seychellois Creole
sn Shona
sd Sindhi
sk Slovak
sl Slovenian
so Somali
es Spanish
es-419 Spanish (Latin American)
su Sundanese
sw Swahili
sv Swedish
tg Tajik
tt Tatar
te Telugu
th Thai
ti Tigrinya
to Tonga
lua Tshiluba
tum Tumbuka
tr Turkish
tk Turkmen
tw Twi
ug Uighur
uk Ukrainian
ur Urdu
uz Uzbek
cy Welsh
wo Wolof
xh Xhosa
yi Yiddish
yo Yoruba
zu Zulu

Original subtitles

It on like section we're going to take a look to the troubleshooting

troubleshooting is the process of diagnosing a problem and if possible resolving it the troubleshooting

process is usually triggered when a person or a mentoring system reports a problem was the person reporting

the problem.

Often use clues about the symptoms of the problem.

The trouble shooter the person who is going to have the problem has to find the root cause of the problem

and the trouble shooter will be you guys most of the times.

Let's go with it the stats of the trouble shooting the trouble shooting steps are the three steps.

The first step is identifying the problem.

This second is isolating the problem and the third is implementing a correct action and fix it to identify

the problem to isolate the problem and to implement a quick action as well.

And the users are your best friend always guys.

Let's go over to troubleshooting commands.

They're playing.

Trace route S-sh Shumaker risk Thabo shoy interface breath swipe you troll on and the dieback commands

to use for trouble shooting.

We have two kinds of troubleshooting tools and there are software troubleshoot and they hardware trouble

shoot to

let's to using the overside module for troubleshooting we had some trouble shooting to skies and their

top down bottom up the word on can clear for the path Saputo differences and the move the problem and

up did go much deeper for this age solutions but I'm going to show you an example for example top down

means we need to go downward from the oversize application like for example if one of your users reported

a problem such that I can not serve on the Internet.

The first thing I'm going to focus on is the application layer of the site which is I'm going to go.

My friend please check the browser for example that you're using if you're using Chrome change it to

operate and do it try to surf again.

Then we're going to go down.

Maybe I can check the network layer in here.

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

or not.

Or maybe I can't check them they're telling clear for example.

I can't check the lead to meters of that guy's Internet.

And lastly I can say the guy for example.

Hey man please check your cables if your cables are connected or not properly.

OK.

They're still using for the or some modules for the troubleshooting as an example.

And here is how we can T-shaped the IP connectivity step by step.

For example for us we can check the layer one for errors or up or down say it's there we can check a

duplex mismatch.

We can check the MAC addresses IP addresses ARP tables we can check the ports or we can check the ACLU

or DNS as well.

Let's go to spend now spend switched ports analyzer is an efficient high performance traffic monitoring

system.

There it's all mirrors traffic from a source port to our bill and to a destination port.

This is sometimes referred to as session month or AInc span is used for troubleshooting connectivity

issues and calculating network utilization and performance among many others.

And here's the comfort here's how we can use the span for using the sperm for example if we want to

worst traffic.

If you want to mirror the traffic from Port 5 to port nine we're using a network analyzer to our ports.

And we're simply mirroring our traffic form port to the port nine.

As you can see here we have two types of spen and there are local span and the remote spare local locals

mirrors the traffic between ports in the same switch remote span is similar to span.

But it's support source ports source Whelan's and destination ports on different survey edge.

For example if you want to configure a local span on your unswitched UK is the morning session and the

session number command and you define the source and the destination interfaces.

That's pretty straightforward.

As you can see to configure it let's go with that.

I piss away I personally is a Cisco proprietary Iris feature that ellos to collect information.

For example response time latency Jinder and the of applause about network performance in the real time

and here's the configuration of the IP SLA to come for your day.

I personally for rather world for example are defining an IP of solid proof for us by tapping IP SLA

and for example a number which is one in here.

There we are defining an ICMP call.

Or rather what I'm doing is I'm sending ping packets to this interface of the tree and I'm doing this

action for aged 20 seconds.

The frequency commands shows the frequency of the ICMP packets that I'm sending for then I'm using a

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

the time range that I'm using this IP SLA to verify the silly configuration.

I can show I pixelate configuration command and I can check the target address source address and Operation

timeout and enter a number or some more informations like that.

The second method that I can find the IP Eslick configuration is using the show IP SLA statistics comments

and we can check the latest operations our time latest operation returned card number of success and

number of failures are some more information like that.

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