Collision [7:59590]
Dear All, My network have collision is this good sign?? Please help!!! FastEthernet0/48 is up, line protocol is up Hardware is Fast Ethernet, address is 000a.f477.662c (bia 000a.f477.662c) MTU 1500 bytes, BW 1 Kbit, DLY 1000 usec, reliability 250/255, txload 5/255, rxload 9/255 Encapsulation ARPA, loopback not set Keepalive set (10 sec) Half-duplex, 10Mb/s input flow-control is off, output flow-control is off ARP type: ARPA, ARP Timeout 04:00:00 Last input 00:00:16, output 00:00:00, output hang never Last clearing of "show interface" counters never Input queue: 0/75/0/0 (size/max/drops/flushes); Total output drops: 0 Queueing strategy: fifo Output queue :0/40 (size/max) 5 minute input rate 36 bits/sec, 73 packets/sec 5 minute output rate 227000 bits/sec, 51 packets/sec 1363328 packets input, 543353391 bytes, 0 no buffer Received 35975 broadcasts, 234208 runts, 0 giants, 0 throttles 234208 input errors, 0 CRC, 0 frame, 0 overrun, 0 ignored 0 watchdog, 9715 multicast, 0 pause input 0 input packets with dribble condition detected 19819113 packets output, 2197938874 bytes, 2308379 underruns 0 output errors, 127070 collisions, 1 interface resets 0 babbles, 0 late collision, 11950 deferred 0 lost carrier, 0 no carrier, 0 PAUSE output 2308379 output buffer failures, 0 output buffers swapped out Message Posted at: http://www.groupstudy.com/form/read.php?f=7&i=59590&t=59590 -- FAQ, list archives, and subscription info: http://www.groupstudy.com/list/cisco.html Report misconduct and Nondisclosure violations to [EMAIL PROTECTED]
RE: Collision [7:59590]
The interface is set to half duplex. Collisions are a normal part of half duplex Ethernet. However, do you really need it to be confiugred as half duplex? What does it connect to? If it connects to a single port like a router or switch port or to a single workstation or server, then you can use full duplex. In other words, if it's a point-to-point link, then you can use full duplex, and no collisions will occur. Both ends should be configured as full duplex (or to use auto negotiation). If it connects to a shared network, like a hub, then it must use half duplex and you will get collisions. They are not a problem. The Ethernet interface retransmits if there is a collision. Priscilla Steiven Poh-\(Jaring MailBox\) wrote: > > Dear All, > > My network have collision is this good sign?? Please help!!! > > FastEthernet0/48 is up, line protocol is up > Hardware is Fast Ethernet, address is 000a.f477.662c (bia > 000a.f477.662c) > MTU 1500 bytes, BW 1 Kbit, DLY 1000 usec, > reliability 250/255, txload 5/255, rxload 9/255 > Encapsulation ARPA, loopback not set > Keepalive set (10 sec) > Half-duplex, 10Mb/s > input flow-control is off, output flow-control is off > ARP type: ARPA, ARP Timeout 04:00:00 > Last input 00:00:16, output 00:00:00, output hang never > Last clearing of "show interface" counters never > Input queue: 0/75/0/0 (size/max/drops/flushes); Total output > drops: 0 > Queueing strategy: fifo > Output queue :0/40 (size/max) > 5 minute input rate 36 bits/sec, 73 packets/sec > 5 minute output rate 227000 bits/sec, 51 packets/sec > 1363328 packets input, 543353391 bytes, 0 no buffer > Received 35975 broadcasts, 234208 runts, 0 giants, 0 > throttles > 234208 input errors, 0 CRC, 0 frame, 0 overrun, 0 ignored > 0 watchdog, 9715 multicast, 0 pause input > 0 input packets with dribble condition detected > 19819113 packets output, 2197938874 bytes, 2308379 > underruns > 0 output errors, 127070 collisions, 1 interface resets > 0 babbles, 0 late collision, 11950 deferred > 0 lost carrier, 0 no carrier, 0 PAUSE output > 2308379 output buffer failures, 0 output buffers swapped out > > Message Posted at: http://www.groupstudy.com/form/read.php?f=7&i=59593&t=59590 -- FAQ, list archives, and subscription info: http://www.groupstudy.com/list/cisco.html Report misconduct and Nondisclosure violations to [EMAIL PROTECTED]
RE: Collision [7:59590]
Just another thought to consider, your counters have never been cleared. So if this router has been up for a long time who knows if it's just people running around in the LAN room playing with cables or doing other work that caused these errors 6 months ago. Otherwise you may want to look at the half-duplex as Priscilla commented on already. John -Original Message- From: [EMAIL PROTECTED] [mailto:[EMAIL PROTECTED]] On Behalf Of Steiven Poh-(Jaring MailBox) Sent: Thursday, December 19, 2002 9:29 PM To: [EMAIL PROTECTED] Subject: Collision [7:59590] Dear All, My network have collision is this good sign?? Please help!!! FastEthernet0/48 is up, line protocol is up Hardware is Fast Ethernet, address is 000a.f477.662c (bia 000a.f477.662c) MTU 1500 bytes, BW 1 Kbit, DLY 1000 usec, reliability 250/255, txload 5/255, rxload 9/255 Encapsulation ARPA, loopback not set Keepalive set (10 sec) Half-duplex, 10Mb/s input flow-control is off, output flow-control is off ARP type: ARPA, ARP Timeout 04:00:00 Last input 00:00:16, output 00:00:00, output hang never Last clearing of "show interface" counters never Input queue: 0/75/0/0 (size/max/drops/flushes); Total output drops: 0 Queueing strategy: fifo Output queue :0/40 (size/max) 5 minute input rate 36 bits/sec, 73 packets/sec 5 minute output rate 227000 bits/sec, 51 packets/sec 1363328 packets input, 543353391 bytes, 0 no buffer Received 35975 broadcasts, 234208 runts, 0 giants, 0 throttles 234208 input errors, 0 CRC, 0 frame, 0 overrun, 0 ignored 0 watchdog, 9715 multicast, 0 pause input 0 input packets with dribble condition detected 19819113 packets output, 2197938874 bytes, 2308379 underruns 0 output errors, 127070 collisions, 1 interface resets 0 babbles, 0 late collision, 11950 deferred 0 lost carrier, 0 no carrier, 0 PAUSE output 2308379 output buffer failures, 0 output buffers swapped out Message Posted at: http://www.groupstudy.com/form/read.php?f=7&i=59597&t=59590 -- FAQ, list archives, and subscription info: http://www.groupstudy.com/list/cisco.html Report misconduct and Nondisclosure violations to [EMAIL PROTECTED]
RE: Collision [7:59590]
I would clear the counters and wait a day and then post sho int again. Collisions are normal but the other errors are an indication of possible speed/duplex mismatch Stan -Original Message- From: Steiven Poh-(Jaring MailBox) [mailto:[EMAIL PROTECTED]] Sent: Thursday, December 19, 2002 8:29 PM To: [EMAIL PROTECTED] Subject: Collision [7:59590] Dear All, My network have collision is this good sign?? Please help!!! FastEthernet0/48 is up, line protocol is up Hardware is Fast Ethernet, address is 000a.f477.662c (bia 000a.f477.662c) MTU 1500 bytes, BW 1 Kbit, DLY 1000 usec, reliability 250/255, txload 5/255, rxload 9/255 Encapsulation ARPA, loopback not set Keepalive set (10 sec) Half-duplex, 10Mb/s input flow-control is off, output flow-control is off ARP type: ARPA, ARP Timeout 04:00:00 Last input 00:00:16, output 00:00:00, output hang never Last clearing of "show interface" counters never Input queue: 0/75/0/0 (size/max/drops/flushes); Total output drops: 0 Queueing strategy: fifo Output queue :0/40 (size/max) 5 minute input rate 36 bits/sec, 73 packets/sec 5 minute output rate 227000 bits/sec, 51 packets/sec 1363328 packets input, 543353391 bytes, 0 no buffer Received 35975 broadcasts, 234208 runts, 0 giants, 0 throttles 234208 input errors, 0 CRC, 0 frame, 0 overrun, 0 ignored 0 watchdog, 9715 multicast, 0 pause input 0 input packets with dribble condition detected 19819113 packets output, 2197938874 bytes, 2308379 underruns 0 output errors, 127070 collisions, 1 interface resets 0 babbles, 0 late collision, 11950 deferred 0 lost carrier, 0 no carrier, 0 PAUSE output 2308379 output buffer failures, 0 output buffers swapped out Message Posted at: http://www.groupstudy.com/form/read.php?f=7&i=59615&t=59590 -- FAQ, list archives, and subscription info: http://www.groupstudy.com/list/cisco.html Report misconduct and Nondisclosure violations to [EMAIL PROTECTED]
RE: Collision [7:59590]
A late addition to the thread... Priscilla is correct about using full duplex if it's a point to point link - as long as the other end supports full duplex - not all of the older routers do. Another point to note is that the reported reliability of this link is only 250/255. Anything less than 255/255 is usually Not A Good Thing in my experience. But yeah, as at least one other poster has said - clear your counters and have another look to see what's happening NOW. JMcL Priscilla Oppenheimer wrote: > > The interface is set to half duplex. Collisions are a normal > part of half duplex Ethernet. > > However, do you really need it to be confiugred as half duplex? > What does it connect to? If it connects to a single port like a > router or switch port or to a single workstation or server, > then you can use full duplex. In other words, if it's a > point-to-point link, then you can use full duplex, and no > collisions will occur. Both ends should be configured as full > duplex (or to use auto negotiation). > > If it connects to a shared network, like a hub, then it must > use half duplex and you will get collisions. They are not a > problem. The Ethernet interface retransmits if there is a > collision. > > Priscilla > > Steiven Poh-\(Jaring MailBox\) wrote: > > > > Dear All, > > > > My network have collision is this good sign?? Please > help!!! > > > > FastEthernet0/48 is up, line protocol is up > > Hardware is Fast Ethernet, address is 000a.f477.662c (bia > > 000a.f477.662c) > > MTU 1500 bytes, BW 1 Kbit, DLY 1000 usec, > > reliability 250/255, txload 5/255, rxload 9/255 > > Encapsulation ARPA, loopback not set > > Keepalive set (10 sec) > > Half-duplex, 10Mb/s > > input flow-control is off, output flow-control is off > > ARP type: ARPA, ARP Timeout 04:00:00 > > Last input 00:00:16, output 00:00:00, output hang never > > Last clearing of "show interface" counters never > > Input queue: 0/75/0/0 (size/max/drops/flushes); Total output > > drops: 0 > > Queueing strategy: fifo > > Output queue :0/40 (size/max) > > 5 minute input rate 36 bits/sec, 73 packets/sec > > 5 minute output rate 227000 bits/sec, 51 packets/sec > > 1363328 packets input, 543353391 bytes, 0 no buffer > > Received 35975 broadcasts, 234208 runts, 0 giants, 0 > > throttles > > 234208 input errors, 0 CRC, 0 frame, 0 overrun, 0 ignored > > 0 watchdog, 9715 multicast, 0 pause input > > 0 input packets with dribble condition detected > > 19819113 packets output, 2197938874 bytes, 2308379 > > underruns > > 0 output errors, 127070 collisions, 1 interface resets > > 0 babbles, 0 late collision, 11950 deferred > > 0 lost carrier, 0 no carrier, 0 PAUSE output > > 2308379 output buffer failures, 0 output buffers swapped > out > > > > > > Message Posted at: http://www.groupstudy.com/form/read.php?f=7&i=59940&t=59590 -- FAQ, list archives, and subscription info: http://www.groupstudy.com/list/cisco.html Report misconduct and Nondisclosure violations to [EMAIL PROTECTED]
