I now about symbols errors a gbics problem.
But I have PC connected to medai converters connected to ethenet ports fo/1 2 3 4 etc with sybols errors
what does that mean when I am getting symbol errors cat5 ports
Solved! Go to Solution.
I read this however it is not clear
Small amounts of symbol errors can be ignored. what would be considered small %
Large amounts of symbol errors can indicate a bad device, cable, or hardware== BAD device meaning switch or attached device
>sh controllers eth f0/11
Transmit FastEthernet0/11 Receive
1309854685 Bytes 3033939523 Bytes
110284581 Unicast frames 79758877 Unicast frames
52467486 Multicast frames 393493 Multicast frames
21875517 Broadcast frames 794561 Broadcast frames
0 Discarded frames 1 No dest, unicast
0 Too old frames 0 No dest, multicast
588022 Deferred frames 0 No dest, broadcast
3336954 1 collision frames
1342151 2 collision frames 1942 FCS errors
230640 3 collision frames 0 Oversize frames
17168 4 collision frames 0 Undersize frames
1534 5 collision frames 6802891 Collision fragments
773 6 collision frames
706 7 collision frames 68985261 Minimum size frames
670 8 collision frames 4198958 65 to 127 byte frames
578 9 collision frames 5201087 128 to 255 byte frames
300 10 collision frames 1259740 256 to 511 byte frames
69 11 collision frames 1013496 512 to 1023 byte frames
7 12 collision frames 306208 1024 to 1518 byte frames
1 13 collision frames
1 14 collision frames 0 Flooded frames
0 15 collision frames 0 Overrun frames
0 Excessive collisions 2 VLAN filtered frames
0 Late collisions 0 Source routed frames
3336954 Good (1 coll) frames 0 Valid oversize frames
1594598 Good(>1 coll) frames 0 Pause frames
0 Pause frames 64998 Symbol error frames
0 VLAN discard frames 0 Invalid frames, too large
0 Excess defer frames 0 Valid frames, too large
0 Too large frames 6852013 Invalid frames, too small
94125348 64 byte frames 0 Valid frames, too small
59822793 127 byte frames
4585668 255 byte frames
1805489 511 byte frames
622757 1023 byte frames
23665529 1518 byte frames
the cables were changed this is happening on several ports There is no network issues howerver these errors keep going up.
I am used symbol errors being a Gbic problem and after gbic is replace there going howerver these are happening on ethernet ports not fiber ports.
I am using media converter so PC cat5--media converter---------fiberrun--------------media converter--------cat5 to switch
tried auto auto and also hard code ports to 10 half
They have never cleared switch has been up for 39 weeks
port is set at auto auto neg @10 half
13 input errors, 13 CRC, 0 frame, 0 overrun, 0 ignored
0 watchdog, 3492 multicast, 0 pause input
0 input packets with dribble condition detected
2498211 packets output, 1295703829 bytes, 0 underruns
0 output errors, 172082 collisions, 0 interface resets
The media converter are passthrough so what comes in goes out there is now way to set them Only way is to hard code PC and switch.
Now when I get duplex mismatch I usally see Late collisions but without having access to PC different dept...
Not sure what there settings are They should be auto atuo
The symbol error are happening on several ports not just this one so I was wondering what can cause a symbol error besides bad hardware
I think the duplex mismatch is between the switch port and the nearest media converter. You may want to check the dip switch of the the m/c because sometimes they are shipped with half duplex.
these media converters Have no dip switches I know for a fact I have talked to there tech support to see if I could get the to neg at 10 full.
On way to have a duplex mismatch it The pc nic was hard coded at 10 full and my switch is at auto auto which it will neg at 10 half.
These media converter Do Not support Auto Negotiation
Also, since you are using a media converter to go from copper to fiber, check the fiber side, if possible pull the connectors out, clean them and put them back(on both sides). Some times the fiber connector get dirty and can cause issues.
Cabling is not the issue Db loss from patch to patch is under 2.0 and we did run new fiber just to make sure This symbol errors happens on more then 1 port it is on several.