Hello,
I want to know how switch generates symbol data in frames and what is possible reasons behind symbol error frames? I know it is basically related to port or cable is not working properly but how switch generates symbol data in frame? why it needs to generate symbol data in each frame? Is it related to Ethernet or Fiber cable? Does symbol error frames has any relation with input errors? If yes, please explain. Please post any good book or reference guide to understand Layer 1 errors and how switch generates symbol data in frames.
S1#sh controllers ethernet-controller fastEthernet 0/5
Transmit FastEthernet0/5 Receive
92953 Bytes 125537 Bytes
446 Unicast frames 548 Unicast frames
511 Multicast frames 296 Multicast frames
0 Broadcast frames 84 Broadcast frames
0 Too old frames 35101 Unicast bytes
0 Deferred frames 79080 Multicast bytes
0 MTU exceeded frames 11356 Broadcast bytes
0 1 collision frames 0 Alignment errors
0 2 collision frames 0 FCS errors
0 3 collision frames 0 Oversize frames
0 4 collision frames 0 Undersize frames
0 5 collision frames 0 Collision fragments
0 6 collision frames
0 7 collision frames 559 Minimum size frames
0 8 collision frames 126 65 to 127 byte frames
0 9 collision frames 161 128 to 255 byte frames
0 10 collision frames 24 256 to 511 byte frames
0 11 collision frames 54 512 to 1023 byte frames
0 12 collision frames 4 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
0 Late collisions 0 Invalid frames, too large
0 VLAN discard frames 0 Valid frames, too large
0 Excess defer frames 0 Invalid frames, too small
318 64 byte frames 0 Valid frames, too small
580 127 byte frames
11 255 byte frames 0 Too old frames
11 511 byte frames 0 Valid oversize frames
37 1023 byte frames 0 System FCS error frames
0 1518 byte frames 0 RxPortFifoFull drop frame
0 Too large frames
0 Good (1 coll) frames
0 Good (>1 coll) frames
S1#
Thanks for your help.

gah, Airpo Extremes similarly hurl 802.1Q frames around just as they do multicast packets. so much for that plan(love yr tweets!)
gah, Airpo Extremes similarly hurl 802.1Q frames around just as they do multicast packets. so much for that plan(love yr tweets!)
gah, Airpo Extremes similarly hurl 802.1Q frames around just as they do multicast packets. so much for that plan(love yr tweets!)
gah, Airpo Extremes similarly hurl 802.1Q frames around just as they do multicast packets. so much for that plan(love yr tweets!)
gah, Airpo Extremes similarly hurl 802.1Q frames around just as they do multicast packets. so much for that plan(love yr tweets!)
gah, Airpo Extremes similarly hurl 802.1Q frames around just as they do multicast packets. so much for that plan(love yr tweets!)
gah, Airpo Extremes similarly hurl 802.1Q frames around just as they do multicast packets. so much for that plan(love yr tweets!)
gah, Airpo Extremes similarly hurl 802.1Q frames around just as they do multicast packets. so much for that plan(love yr tweets!)
gah, Airpo Extremes similarly hurl 802.1Q frames around just as they do multicast packets. so much for that plan(love yr tweets!)
gah, Airpo Extremes similarly hurl 802.1Q frames around just as they do multicast packets. so much for that plan(love yr tweets!)