03-25-2013 06:53 AM - edited 03-07-2019 12:28 PM
Hello,
I am trying to see if a fibre port is at fault here, basically a user is complaining a file being transfered through this fibre link is gettign corrupted, but from the stats below they look ok to me. There seems to be late collisions and collisions (this port has had it's counters reset 2 hours ago), but I'm not sure if that is how fibre works, but I would be concerned on copper, but this is half duplex so I guess it has to happen.
CRCs are good and reliability is 255/255 so maybe it is their software creating the corruption, maybe you can see somethign I can't.
show int gig 2/0/5 transceiver properties
Diagnostic Monitoring is not implemented.
Name : Gi2/0/5
Administrative Speed: auto
Administrative Duplex: auto
Administrative Auto-MDIX: on
Administrative Power Inline: N/A
Operational Speed: 100
Operational Duplex: half
Operational Auto-MDIX: on
Media Type: 100BaseFX SFP
show udld gigabitEthernet 2/0/5
Interface Gi2/0/5
---
Port enable administrative configuration setting: Follows device default
Port enable operational state: Enabled / in aggressive mode
Current bidirectional state: Unknown
Current operational state: Advertisement
Message interval: 7
Time out interval: 5
No neighbor cache information stored
show int gig 2/0/5 controller
GigabitEthernet2/0/5 is up, line protocol is up (connected)
Hardware is Gigabit Ethernet, address is 0019.0691.0d05 (bia 0019.0691.0d05)
Description: LCD
MTU 1500 bytes, BW 100000 Kbit, DLY 100 usec,
reliability 255/255, txload 1/255, rxload 1/255
Encapsulation ARPA, loopback not set
Keepalive not set
Half-duplex, 100Mb/s, link type is auto, media type is 100BaseFX SFP
input flow-control is off, output flow-control is unsupported
ARP type: ARPA, ARP Timeout 04:00:00
Last input 10w4d, output 00:00:47, output hang never
Last clearing of "show interface" counters 01:39:49
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 61000 bits/sec, 59 packets/sec
5 minute output rate 60000 bits/sec, 60 packets/sec
255318 packets input, 37292610 bytes, 0 no buffer
Received 11620 broadcasts (48 multicasts)
0 runts, 0 giants, 0 throttles
0 input errors, 0 CRC, 0 frame, 0 overrun, 0 ignored
0 watchdog, 48 multicast, 0 pause input
0 input packets with dribble condition detected
471123 packets output, 68775081 bytes, 0 underruns
0 output errors, 650 collisions, 0 interface resets
0 babbles, 421 late collision, 0 deferred
0 lost carrier, 0 no carrier, 0 PAUSE output
0 output buffer failures, 0 output buffers swapped out
Transmit GigabitEthernet2/0/5 Receive
2724666016 Bytes 1896707999 Bytes
2537751 Unicast frames 2450415 Unicast frames
11948801 Multicast frames 15806197 Multicast frames
11876703 Broadcast frames 410331 Broadcast frames
0 Too old frames 360602656 Unicast bytes
307571 Deferred frames 1422491352 Multicast bytes
0 MTU exceeded frames 39713108 Broadcast bytes
8814 1 collision frames 0 Alignment errors
90958 2 collision frames 0 FCS errors
46096 3 collision frames 0 Oversize frames
8108 4 collision frames 0 Undersize frames
586 5 collision frames 355951 Collision fragments
37 6 collision frames
6 7 collision frames 648167 Minimum size frames
5 8 collision frames 17097347 65 to 127 byte frames
40 9 collision frames 484522 128 to 255 byte frames
64 10 collision frames 415528 256 to 511 byte frames
11 11 collision frames 10835 512 to 1023 byte frames
3 12 collision frames 10544 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 0 Symbol error frames
37182 Late collisions 0 Invalid frames, too large
0 VLAN discard frames 0 Valid frames, too large
0 Excess defer frames 355951 Invalid frames, too small
3669112 64 byte frames 0 Valid frames, too small
21772140 127 byte frames
496964 255 byte frames 0 Too old frames
276724 511 byte frames 0 Valid oversize frames
31195 1023 byte frames 0 System FCS error frames
153333 1518 byte frames 0 RxPortFifoFull drop frame
0 Too large frames
8814 Good (1 coll) frames
145914 Good (>1 coll) frames
Thanks
03-25-2013 08:36 AM
The links if they are fiber should not be at half duplex and should be corrected. Both ends should be set to full duplex.
03-25-2013 09:51 AM
Seems the remote device is a screen of some sort that is only able to run half duplex, I guess this is the reason for the collisions and late collisions?
03-25-2013 04:25 PM
Yes any port that is half duplex will have collisions, normal part of half duplex operation .
Discover and save your favorite ideas. Come back to expert answers, step-by-step guides, recent topics, and more.
New here? Get started with these tips. How to use Community New member guide