1 00:00:00,980 --> 00:00:07,860 So let's fix this problem between Rotto one and twenty 951. 2 00:00:07,990 --> 00:00:13,330 So on the router it's currently configured to use a speed of 100. 3 00:00:13,930 --> 00:00:22,690 So I'm going to set the speed to auto this the router doesn't give me the option to set duplex. 4 00:00:23,180 --> 00:00:34,780 So show run interface if a zero speed is auto show interface if zero speed is still half duplex. 5 00:00:35,020 --> 00:00:38,550 The router can't negotiate with the switch. 6 00:00:38,560 --> 00:00:45,820 So once again it moves to a fallback position of 10 make half duplex and this is what has caused a lot 7 00:00:45,820 --> 00:00:52,680 of problem in the past because the one side such as the Rodda can't negotiate with the other side. 8 00:00:52,810 --> 00:00:59,680 It simply moves to the lowest possible speed which is half duplex 10 megabits per second whereas the 9 00:00:59,680 --> 00:01:05,310 switch is using full duplex so on the switch show run interface. 10 00:01:05,330 --> 00:01:17,520 If a zero slash three speed is 10 duplexes is full Let's change that to speed Rod Speed auto 11 00:01:20,390 --> 00:01:21,050 duplex 12 00:01:24,560 --> 00:01:24,910 water 13 00:01:29,920 --> 00:01:35,560 show run interface if Zeerust three no configuration show interface. 14 00:01:35,630 --> 00:01:38,650 Is there a slash 3 notice. 15 00:01:38,730 --> 00:01:51,060 It is now using 100 meg full duplex and on the router we are getting 100 make full duplex. 16 00:01:51,060 --> 00:01:53,010 So thats a lot better. 17 00:01:53,170 --> 00:02:00,730 The router and the switch have negotiated correctly to use 100 megabits per second full duplex. 18 00:02:01,330 --> 00:02:09,360 So you can be paying probably two yes we can do a launch paying 19 00:02:13,840 --> 00:02:15,100 large datagram size 20 00:02:17,980 --> 00:02:21,220 pings are being sent without any problems. 21 00:02:23,230 --> 00:02:30,790 We're not seeing any late collisions at the moment because the speed and duplex have negotiated properly. 22 00:02:30,790 --> 00:02:34,450 This may indicate a problem somewhere else in the network. 23 00:02:36,920 --> 00:02:39,370 At the moment everything looks good. 24 00:02:39,380 --> 00:02:42,950 Show interface if the 0. 25 00:02:43,350 --> 00:02:49,480 Now we still see late collisions but that's because of the previous counters. 26 00:02:49,710 --> 00:02:57,610 So I'm going to clear the town counters and then do the command show interface 0 again and notice we 27 00:02:57,600 --> 00:03:01,010 see zero late collisions. 28 00:03:01,050 --> 00:03:12,870 So when looking at your output be careful of the information Klea counters and we could specify a specific 29 00:03:12,870 --> 00:03:21,430 interface allows us to clear the counters on that interface so that we see fresh information. 30 00:03:21,440 --> 00:03:23,090 So once again if we're paying 31 00:03:26,220 --> 00:03:32,530 10 women to Hausen pings large packet size 32 00:03:35,230 --> 00:03:45,280 we're sending some traffic on the site show interface if 0 three we've got the input errors and CRC 33 00:03:45,280 --> 00:03:51,790 so clear count is 0 3. 34 00:03:51,880 --> 00:04:00,910 We don't see any input errors and CRC is obviously you need to monitor that over a period of time. 35 00:04:00,970 --> 00:04:06,310 So we are seeing a certain number of packets in a certain number of packets out so traffic is definitely 36 00:04:06,310 --> 00:04:13,510 being sent and received and the interface we're not seeing any input errors which is better than what 37 00:04:13,510 --> 00:04:14,960 we saw last time. 38 00:04:15,070 --> 00:04:22,650 But you just need to monitor that for a period of time on the router show interface if zero we see the 39 00:04:22,650 --> 00:04:29,170 number of packets input number of packets output we have no late collisions at the moment. 40 00:04:29,220 --> 00:04:32,960 So that's a lot better than what we saw previously. 41 00:04:32,970 --> 00:04:45,500 Now on this switch we still seeing another problem with a duplex mismatch to switch to. 42 00:04:45,550 --> 00:04:47,950 So this connection here has a duplex problem.