All language subtitles for 4. Speed & Duplex Demo Fix Issue between router and switch

af Afrikaans
sq Albanian
am Amharic
ar Arabic
hy Armenian
az Azerbaijani
eu Basque
be Belarusian
bn Bengali
bs Bosnian
bg Bulgarian
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
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,000 --> 00:00:08,000 So let’s fix this problem between router 1 and 2950-1. 2 00:00:08,000 --> 00:00:13,000 So on the router it’s currently configured to use a speed of 100. 3 00:00:13,000 --> 00:00:18,000 So I’m going to set the speed to auto. 4 00:00:18,000 --> 00:00:22,000 This router doesn’t give me the option to set duplex. 5 00:00:22,000 --> 00:00:35,000 So show run int f/0 speed is auto sh int f/0 speed is still half duplex. 6 00:00:35,000 --> 00:00:39,000 The router can’t negotiate with the switch. 7 00:00:39,000 --> 00:00:44,000 So once again it moves to a full back position of 10 meg half duplex. 8 00:00:44,000 --> 00:00:49,000 and this is what has cause a lot of problem in the past because the 1 side 9 00:00:49,000 --> 00:00:54,000 such as the router can’t negotiate with the other side, it simply moves to the 10 10 00:00:54,000 --> 00:01:01,000 lowest possible speed which is half duplex 10 Mbps where's the switch is using full duplex. 11 11 00:01:01,000 --> 00:01:09,000 So on this switch sh run int f0/3, speed is 10, duplex is full 12 12 00:01:09,000 --> 00:01:35,000 let’s change that to speed rather speed auto, duplex auto, sh run int f0/3 no configuration 13 13 00:01:35,000 --> 00:01:46,000 sh int f0/3 notice it is now using 100 meg full duplex and on the router 14 14 00:01:46,000 --> 00:01:53,000 we are getting 100 meg full duplex, so thats a lot better. 15 15 00:01:53,000 --> 00:02:01,000 The router and the switch have negotiated correctly to use 100 Mbps full duplex. 16 16 00:02:01,000 --> 00:02:06,000 So can we ping router 2? Yes we can. 17 17 00:02:06,000 --> 00:02:21,000 Let’s do a large ping, large datagram size, pings are being sent without any problems 18 18 00:02:21,000 --> 00:02:29,000 we're not seeing any late collisions at the moment because the speed and duplex have 19 19 00:02:29,000 --> 00:02:34,000 negotiated properly, this may indicate a problem somewhere else in the network. 20 20 00:02:34,000 --> 00:02:42,000 At the moment every things looks good, sh int f0 21 21 00:02:42,000 --> 00:02:50,000 Now we still see late collisions but that’s because of the previous counters. 22 22 00:02:50,000 --> 00:02:57,000 So I’m gonna clear the counters and then do the command sh int f0 again. 23 23 00:02:57,000 --> 00:03:00,000 And notice you see 0 late collisions. 24 24 00:03:00,000 --> 00:03:07,000 So when looking at your output be careful of the information. 25 25 00:03:07,000 --> 00:03:14,000 Clear counters and we could specify a specific interface. 26 26 00:03:14,000 --> 00:03:18,000 Allows us to clear the counters on that interface 27 27 00:03:18,000 --> 00:03:21,000 so that we see fresh information 28 28 00:03:21,000 --> 00:03:32,000 So once again if we ping 10.1.1.2 1000 pings. 29 29 00:03:32,000 --> 00:03:42,000 Large packet size, we're sending some traffic on this side, sh int f0/3 30 30 00:03:42,000 --> 00:03:46,000 we’ve got the input errors and CRC's 31 31 00:03:46,000 --> 00:03:55,000 so clear counters f0/3 we don’t see any input errors and CRC's. 32 32 00:03:55,000 --> 00:04:01,000 Obviously you need to monitor that over period of time 33 33 00:04:01,000 --> 00:04:05,000 so we are seeing a certain number of packets in and certain number of packet out. 34 34 00:04:05,000 --> 00:04:10,000 So traffic is definitely being sent and received on this interface. 35 35 00:04:10,000 --> 00:04:15,000 We're not seeing any input errors which is better than we saw last time 36 36 00:04:15,000 --> 00:04:18,000 but you just need to monitor that for a period of time 37 37 00:04:18,000 --> 00:04:24,000 on the routers sh int f0 we see the number of packets input 38 38 00:04:24,000 --> 00:04:29,000 number of packets output. we have no late collision at the moment. 39 39 00:04:29,000 --> 00:04:33,000 So that's a lot better than what we saw previously. 40 40 00:04:33,000 --> 00:04:45,000 Now on this switch we're still seeing another problem with the duplex mismatch to switch 2. 41 41 00:04:45,000 --> 00:04:50,000 So this connection here has a duplex problem. 4313

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