Cisco 2960 errors on ethernet port

quezon_carlo12 · ‎01-17-2017

Hi everyone,

Can anyone explain to me what this error means, its a port gig 1/0/1 on a 2960 switch with a cisco IP phone connected to that port.

Transmit GigabitEthernet1/0/1 Receive
687849087 Bytes 188908754 Bytes
2005532 Unicast frames 1299490 Unicast frames
311005 Multicast frames 8421 Multicast frames
198592 Broadcast frames 11826 Broadcast frames
0 Too old frames 184151318 Unicast bytes
158 Deferred frames 1281140 Multicast bytes
0 MTU exceeded frames 1932740 Broadcast bytes
122 1 collision frames 0 Alignment errors
10 2 collision frames 4 FCS errors
3 3 collision frames 0 Oversize frames
2 4 collision frames 0 Undersize frames
0 5 collision frames 0 Collision fragments
1 6 collision frames
0 7 collision frames 529963 Minimum size frames
0 8 collision frames 267019 65 to 127 byte frames
0 9 collision frames 481001 128 to 255 byte frames
0 10 collision frames 13914 256 to 511 byte frames
0 11 collision frames 14328 512 to 1023 byte frames
0 12 collision frames 13407 1024 to 1518 byte frames
0 13 collision frames 0 Overrun frames
0 14 collision frames 0 Pause frames
0 15 collision frames
0 Excessive collisions 7 Symbol error frames
842 Late collisions 0 Invalid frames, too large
0 VLAN discard frames 116 Valid frames, too large
0 Excess defer frames 0 Invalid frames, too small
207355 64 byte frames 0 Valid frames, too small
483157 127 byte frames
781197 255 byte frames 0 Too old frames
50456 511 byte frames 0 Valid oversize frames
67773 1023 byte frames 0 System FCS error frames
925834 1518 byte frames 0 RxPortFifoFull drop frame
190 Too large frames
118 Good (1 coll) frames
12 Good (>1 coll) frames

Leo Laohoo · ‎01-18-2017

Post the complete output to the following commands:

1. sh interface Gi 1/0/1; and

2. sh run interface Gi 1/0/1

quezon_carlo12 · ‎01-18-2017

here are info

1. sh interface Gi 1/0/1

GigabitEthernet1/0/1 is up, line protocol is up (connected)
Hardware is Gigabit Ethernet, address is 00da.55fc.5901 (bia 00da.55fc.5901)
MTU 1500 bytes, BW 100000 Kbit/sec, DLY 100 usec,
reliability 255/255, txload 1/255, rxload 1/255
Encapsulation ARPA, loopback not set
Keepalive set (10 sec)
Full-duplex, 100Mb/s, media type is 10/100/1000BaseTX
input flow-control is off, output flow-control is unsupported
ARP type: ARPA, ARP Timeout 04:00:00
Last input 00:00:12, 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
Quee ueing strategy: fifo
Output queue: 0/40 (size/max)
5 minute input rate 1000 bits/sec, 2 packets/sec
5 minute output rate 8000 bits/sec, 6 packets/sec
1691740 packets input, 238328325 bytes, 0 no buffer
Received 28239 broadcasts (10839 multicasts)
0 runts, 0 giants, 0 throttles
124 input errors, 117 CRC, 0 frame, 0 overrun, 0 ignored
0 watchdog, 10839 multicast, 0 pause input
0 input packets with dribble condition detected
3530961 packets output, 2441036049 bytes, 0 underruns
0 output errors, 138 collisions, 1 interface resets
0 unknown protocol drops
0 babbles, 842 late collision, 0 deferred
0 lost carrier, 0 no carrier, 0 pause output
0 output buffer failures, 0 output buffers swapped out

2. sh run interface Gi 1/0/1

Building configuration...

Current configuration : 163 bytes
!
interface GigabitEthernet1/0/1
switchport access vlan 8
switchport mode access
switchport voice vlan 110
speed 100
duplex full
spanning-tree portfast
end

Leo Laohoo · ‎01-18-2017

speed 100
duplex full

The line errors caused by Collisions are because someone decided to hard-code speed and duplex settings.

This practice is an "old school" method that has no benefit whatsoever.

Remove the offending lines and the collision errors should stop.

quezon_carlo12 · ‎01-18-2017

Thanks for the info Leo..

I had it hard code due to that gi 1/0/1 is connected to a VOIP phone.. and most of the time the switch makes the port settings to half duplex..

Leo Laohoo · ‎01-18-2017

Cisco phones don't go "half duplex" if the switch ports are set to auto/auto. I've never seen one.

quezon_carlo12 · ‎01-18-2017

thanks for the info..

Joseph W. Doherty · ‎01-18-2017

You might want to check whether your VoIP phones support speed/duplex settings. If so, ideally, they too support auto/auto. If not, if they only support full duplex hard coded, you would need to hard code the Cisco port to match.

What you want to avoid is a duplex mismatch.