Interfaces Error about Rcv-Err, UnderSize and Runts Values

[Print Hello World]

On interface Gi1/0/18,23 - Gi2/0/18 connected between Storage, I found a Rcv-Err, UnderSize and Runts Values. you can see details below.

C9200#show interface counter error

Port           Align-Err     FCS-Err    Xmit-Err     Rcv-Err  UnderSize  OutDiscards

<SNIP>

Gi1/0/17               0           0           0           0          0        35858

Gi1/0/18               0           0           0   115937543     208761          371

<SNIP>

Gi1/0/22               0           0           0           0          0            0

Gi1/0/23               0           0           0     8470876      13344           35

Gi1/0/24               0           0           0           0          0            0

<SNIP>

Gi2/0/17               0           0           0           0          0        87839

Gi2/0/18               0           0           0   178753598     300454         2221

<SNIP>

Te2/1/4                0           0           0           0          0            0

Po1                      0           0           0          

-------------------------------------------------------

GigabitEthernet1/0/23 is up, line protocol is up (connected)
Hardware is Gigabit Ethernet, address is 8c94.1fed.9197 (bia 8c94.1fed.9197)
Description: Temp ### Link to IBM_9500_CT1-Data ###
MTU 1500 bytes, BW 1000000 Kbit/sec, DLY 10 usec,
reliability 255/255, txload 1/255, rxload 11/255
--More-- Encapsulation ARPA, loopback not set
Keepalive set (10 sec)
Full-duplex, 1000Mb/s, media type is 10/100/1000BaseTX
input flow-control is on, output flow-control is unsupported
ARP type: ARPA, ARP Timeout 04:00:00
Last input never, output 00:00:00, output hang never
Last clearing of "show interface" counters never
Input queue: 0/2000/0/0 (size/max/drops/flushes); Total output drops: 35
Queueing strategy: fifo
Output queue: 0/40 (size/max)
5 minute input rate 45276000 bits/sec, 4936 packets/sec
5 minute output rate 3886000 bits/sec, 3792 packets/sec
2930176688 packets input, 3341290471327 bytes, 0 no buffer
Received 197 broadcasts (114 multicasts)
13344 runts, 0 giants, 0 throttles
8483898 input errors, 0 CRC, 0 frame, 0 overrun, 0 ignored
0 watchdog, 114 multicast, 0 pause input
0 input packets with dribble condition detected
2320948556 packets output, 267130609425 bytes, 0 underruns
Output 4616358 broadcasts (0 multicasts)
0 output errors, 0 collisions, 8 interface resets
0 unknown protocol drops
0 babbles, 0 late collision, 0 deferred
0 lost carrier, 0 no carrier, 0 pause output
0 output buffer failures, 0 output buffers swapped out

----------------------------------------------------

I've tried reading in the documentation. It is described as : 

** Rcv-Err is a receive error (that is, Rcv-Err) occurs when a port's receive buffer overflows. Congestion on a switch's backplane could cause the receive buffer on a port to fill to capacity, as frames await access to the switch's backplane. However, most likely, a Rcv-Err is indicating a duplex mismatch.

*** UnderSize is  a frame with a valid checksum but a size less than 64 bytes. This issue suggests that a connected host is sourcing invalid frame sizes.

*** Runts  is a frame that is less than 64 bytes in size and has a bad CRC. A runt could result from a duplex mismatch or a Layer 1 issue.

But I don't understand size less than 64 bytes, How am I fix this, all I can think of is just checking the speed and setting the duplex to match.

Please recommend me about this case, If you have any Idea. 

[MHM Cisco World · Accepted solution]

I send you message check it

[Leo Laohoo · Accepted solution]

---

@Print Hello World wrote:
8483898 input errors

---

Post the complete output to the command "sh controll e Gi 1/0/23".

[Print Hello World]

Hi Leo Laohoo,

Thank you for your response. 

I already show commands, I see the ValidUnderSize frames and SymbolErr frames are very high values.

But MTU is 1500 match between c9200 <> Storage. Do you have anything Idea?
 

C9200#show controllers ethernet-controller GigabitEthernet 1/0/23

Transmit                  GigabitEthernet1/0/23 Receive                

 330823575416 Total bytes              4093799973186 Total bytes             

   2845127328 Unicast frames              3597127716 Unicast frames          

 329817720090 Unicast bytes            4093799956746 Unicast bytes           

      4636405 Multicast frames                   140 Multicast frames        

    367848110 Multicast bytes                  10680 Multicast bytes         

      5835485 Broadcast frames                    90 Broadcast frames        

    638007216 Broadcast bytes                   5760 Broadcast bytes         

            0 System FCS error frames              0 IpgViolation frames     

            0 MacUnderrun frames                   0 MacOverrun frames       

            0 Pause frames                         0 Pause frames            

            0 Cos 0 Pause frames                   0 Cos 0 Pause frames      

            0 Cos 1 Pause frames                   0 Cos 1 Pause frames      

            0 Cos 2 Pause frames                   0 Cos 2 Pause frames       

            0 Cos 3 Pause frames                   0 Cos 3 Pause frames      

            0 Cos 4 Pause frames                   0 Cos 4 Pause frames      

            0 Cos 5 Pause frames                   0 Cos 5 Pause frames      

            0 Cos 6 Pause frames                   0 Cos 6 Pause frames      

            0 Cos 7 Pause frames                   0 Cos 7 Pause frames      

            0 Oam frames                           0 OamProcessed frames     

            0 Oam frames                           0 OamDropped frames       

      6763570 Minimum size frames              30999 Minimum size frames     

   2728887323 65 to 127 byte frames        459060175 65 to 127 byte frames   

   15424278 128 to 255 byte frames        77037288 128 to 255 byte frames  

     15117943 256 to 511 byte frames       132968730 256 to 511 byte frames  

     46688023 512 to 1023 byte frames      191390878 512 to 1023 byte frames 

     42718084 1024 to 1518 byte frames    2746642707 1024 to 1518 byte frames

            1 1519 to 2047 byte frames         62051 1519 to 2047 byte frames

            0 2048 to 4095 byte frames             0 2048 to 4095 byte frames

            0 4096 to 8191 byte frames             0 4096 to 8191 byte frames

            0 8192 to 16383 byte frames            0 8192 to 16383 byte frames

            0 16384 to 32767 byte frame            0 16384 to 32767 byte frame

            0 > 32768 byte frames                        0 > 32768 byte frames     

            0 Late collision frames                         10326504 SymbolErr frames        

           42 Excess Defer frames                        2 Collision fragments     

            0 Good (1 coll) frames                        16207 ValidUnderSize frames   

            0 Good (>1 coll) frames                     0 InvalidOverSize frames  

            0 Deferred frames                               0 ValidOverSize frames    

            0 Gold frames dropped                      0 FcsErr frames           

            0 Gold frames truncated   

            0 Gold frames successful  

            0 1 collision frames      

            0 2 collision frames      

            0 3 collision frames      

            0 4 collision frames       

            0 5 collision frames      

             0 6 collision frames      

            0 7 collision frames      

            0 8 collision frames      

            0 9 collision frames      

            0 10 collision frames     

            0 11 collision frames     

            0 12 collision frames     

            0 13 collision frames     

            0 14 collision frames     

            0 15 collision frames     

            0 Excess collision frames 

LAST UPDATE 2048 msecs AGO

[Leo Laohoo]

Get a TDR done on the line. 

Do not use the TDR function of a Catalyst 9k or 3650/3850 because it is broken and the result(s) cannot be trusted.

[Print Hello World]

Hi Leo Laohoo,

You mean using a TDR tester, right?

Not use the commands  test cable-diagnostics tdr { interface{interface-number} }

Many Thanks.

[Leo Laohoo]

---

@Print Hello World wrote:
You mean using a TDR tester, right?

---

Correct.  Fluke TDR. 

---

@Print Hello World wrote:
Not use the commands  test cable-diagnostics tdr { interface{interface-number} }

---

Correct.  Do not use the IOS-XE TDR function because it is broken:  CSCwd97177 & CSCvw97924