[EMAIL PROTECTED] wrote: > > These errors are probably occurring simply because you are > running half-duplex. > If you can bring the lines up to 100/full I believe it will > clean up.
I agree. > Are these > errors happening continuously or in spurts during heavy traffic > (that would be > my guess)? If they are happening continuously, it may be a bad > cable(s) or > duplex mismatch between the two sides. > > Input and output errors are bad packets. Runts are (if I > remember correctly) > packets that are smaller than 64bytes and I believe they are > counted in the > error counts. Yes, runts are packets that are smaller than 64 bytes. They are almost always the result of a collision. The sender started sending, noticed someone else sending, and backed off, leaving behind a little runt. Runts are one of the many errors that are counted as input errors. Sometimes, you can add up all your errors and get the same number that you see for the generic "input error counter." But as Cisco says in their documentation (without enough details), some additional errors get counted as generic input errors. Also, frames can have more than one error. So the sum doesn't always work out. Runts, collisions, and CRC errors that result from collisions are all normal in shared (half dupex) Ethernet, especially under high traffic conditions. The real question to figure out is why your Gigabit Ethernet ports are running at 10 Mbps half duplex? Can't you get them to run at Gigabit Full Duplex? Priscilla > > Mark > > > I am getting many output and input errors between 2 brand new > 4006s (version > > 12.1(8a)EW1) and 3640 routers. First of all what exactly are > output and > > input errors (please give more than what it says on the Cisco > site) and why > > are they caused? How do I fix them or do I need to??? > > > > Here is the "show int" between the Cat4K and the 3640's. > Note 10Mb half > > duplex setting. > > > > Do the runts have anything to do with the input errors?? > > > > Also, I see no corresponding errors on the 3640 ports. > > > > > > thanks, > > Mary > > > > First 3640: > > > > sho int gig3/10 > > GigabitEthernet3/10 is up, line protocol is up > > Hardware is Gigabit Ethernet Port, address is > 0008.e3a9.1139 (bia > > 0008.e3a9.1139) > > Description: > > MTU 1500 bytes, BW 10000 Kbit, DLY 10 usec, > > reliability 249/255, txload 12/255, rxload 1/255 > > Encapsulation ARPA, loopback not set > > Keepalive set (10 sec) > > Half-duplex, 10Mb/s > > ARP type: ARPA, ARP Timeout 04:00:00 > > Last input 00:00:23, output never, output hang never > > Last clearing of "show interface" counters 1d19h > > Input queue: 0/2000/0/0 (size/max/drops/flushes); Total > output drops: 0 > > Queueing strategy: fifo > > Output queue: 0/40 (size/max) > > 5 minute input rate 40000 bits/sec, 34 packets/sec > > 5 minute output rate 472000 bits/sec, 59 packets/sec > > 3800050 packets input, 668905159 bytes, 0 no buffer > > Received 41421 broadcasts, 142835 runts, 0 giants, 0 > throttles > > 143481 input errors, 0 CRC, 0 frame, 0 overrun, 0 ignored > > 0 input packets with dribble condition detected > > 6267861 packets output, 3015668941 bytes, 0 underruns > > 259635 output errors, 97281 collisions, 0 interface > resets > > 0 babbles, 0 late collision, 0 deferred > > 0 lost carrier, 0 no carrier > > 0 output buffer failures, 0 output buffers swapped out > > > > Seconf 3640: > > > > GigabitEthernet3/2 is up, line protocol is up > > Hardware is Gigabit Ethernet Port, address is > 0008.e3a9.1ec9 (bia > > 0008.e3a9.1ec9) > > Description: > > MTU 1500 bytes, BW 10000 Kbit, DLY 10 usec, > > reliability 244/255, txload 1/255, rxload 1/255 > > Encapsulation ARPA, loopback not set > > Keepalive set (10 sec) > > Half-duplex, 10Mb/s > > ARP type: ARPA, ARP Timeout 04:00:00 > > Last input never, output never, output hang never > > Last clearing of "show interface" counters 1d23h > > Input queue: 79/2000/0/0 (size/max/drops/flushes); Total > output drops: 0 > > Queueing strategy: fifo > > Output queue: 0/40 (size/max) > > 5 minute input rate 0 bits/sec, 0 packets/sec > > 5 minute output rate 0 bits/sec, 0 packets/sec > > 2307393 packets input, 974229114 bytes, 0 no buffer > > Received 1816 broadcasts, 61458 runts, 0 giants, 0 > throttles > > 61462 input errors, 0 CRC, 0 frame, 0 overrun, 0 ignored > > 0 input packets with dribble condition detected > > 3796884 packets output, 1389904066 bytes, 0 underruns > > 227519 output errors, 43183 collisions, 0 interface > resets > > 0 babbles, 0 late collision, 0 deferred > > 0 lost carrier, 0 no carrier > > 0 output buffer failures, 0 output buffers swapped out > > Message Posted at: http://www.groupstudy.com/form/read.php?f=7&i=59188&t=59171 -------------------------------------------------- FAQ, list archives, and subscription info: http://www.groupstudy.com/list/cisco.html Report misconduct and Nondisclosure violations to [EMAIL PROTECTED]
