Original subtitles

So let’s fix this problem between router 1 and 2950-1.

So on the router it’s currently configured to use a speed of 100.

So I’m going to set the speed to auto.

This router doesn’t give me the option to set duplex.

So show run int f/0 speed is auto sh int f/0 speed is still half duplex.

The router can’t negotiate with the switch.

So once again it moves to a full back position of 10 meg half duplex.

and this is what has cause a lot of problem in the past because the 1 side

such as the router can’t negotiate with the other side, it simply moves to the 10

lowest possible speed which is half duplex 10 Mbps where's the switch is using full duplex. 11

So on this switch sh run int f0/3, speed is 10, duplex is full 12

let’s change that to speed rather speed auto, duplex auto, sh run int f0/3 no configuration 13

sh int f0/3 notice it is now using 100 meg full duplex and on the router 14

we are getting 100 meg full duplex, so thats a lot better. 15

The router and the switch have negotiated correctly to use 100 Mbps full duplex. 16

So can we ping router 2? Yes we can. 17

Let’s do a large ping, large datagram size, pings are being sent without any problems 18

we're not seeing any late collisions at the moment because the speed and duplex have 19

negotiated properly, this may indicate a problem somewhere else in the network. 20

At the moment every things looks good, sh int f0 21

Now we still see late collisions but that’s because of the previous counters. 22

So I’m gonna clear the counters and then do the command sh int f0 again. 23

And notice you see 0 late collisions. 24

So when looking at your output be careful of the information. 25

Clear counters and we could specify a specific interface. 26

Allows us to clear the counters on that interface 27

so that we see fresh information 28

So once again if we ping 10.1.1.2 1000 pings. 29

Large packet size, we're sending some traffic on this side, sh int f0/3 30

we’ve got the input errors and CRC's 31

so clear counters f0/3 we don’t see any input errors and CRC's. 32

Obviously you need to monitor that over period of time 33

so we are seeing a certain number of packets in and certain number of packet out. 34

So traffic is definitely being sent and received on this interface. 35

We're not seeing any input errors which is better than we saw last time 36

but you just need to monitor that for a period of time 37

on the routers sh int f0 we see the number of packets input 38

number of packets output. we have no late collision at the moment. 39

So that's a lot better than what we saw previously. 40

Now on this switch we're still seeing another problem with the duplex mismatch to switch 2. 41

So this connection here has a duplex problem.