input errors on Nexus 9300

[Stuff]

I have a couple of N9K-C93108TC-EX switches seeing about half of the packets coming from a server being errors.  I can't find any detailed counters showing what the error is.  Where should I be looking?

Thanks.

switch# sh int e 1/8
Ethernet1/8 is up
admin state is up, Dedicated Interface
  Hardware: 100/1000/10000 Ethernet, address: 4ce1.7548.677f (bia 4ce1.7548.677f)
  Description: Slot 1/Mid Left
  MTU 1500 bytes, BW 1000000 Kbit , DLY 10 usec
  reliability 211/255, txload 1/255, rxload 1/255
  Encapsulation ARPA, medium is broadcast
  Port mode is access
  full-duplex, 1000 Mb/s
  Beacon is turned off
  Auto-Negotiation is turned on  FEC mode is Auto
  Input flow-control is off, output flow-control is off
  Auto-mdix is turned on
  Switchport monitor is off
  EtherType is 0x8100
  EEE (efficient-ethernet) : n/a
    admin fec state is auto, oper fec state is off
  Last link flapped 53week(s) 6day(s)
  Last clearing of "show interface" counters 00:17:05
  0 interface resets
  Load-Interval #1: 30 seconds
    30 seconds input rate 2888 bits/sec, 3 packets/sec
    30 seconds output rate 7272 bits/sec, 7 packets/sec
    input rate 2.89 Kbps, 3 pps; output rate 7.27 Kbps, 7 pps
  Load-Interval #2: 5 minute (300 seconds)
    300 seconds input rate 2752 bits/sec, 3 packets/sec
    300 seconds output rate 6680 bits/sec, 6 packets/sec
    input rate 2.75 Kbps, 3 pps; output rate 6.68 Kbps, 6 pps
  RX
    2499 unicast packets  8 multicast packets  0 broadcast packets
    5582 input packets  416407 bytes
    0 jumbo packets  0 storm suppression bytes
    0 runts  0 giants  0 CRC  0 no buffer
    3075 input error  0 short frame  0 overrun   0 underrun  0 ignored
    0 watchdog  0 bad etype drop  0 bad proto drop  0 if down drop
    0 input with dribble  0 input discard
    0 Rx pause
  TX
    6569 unicast packets  1963 multicast packets  3588 broadcast packets
    12120 output packets  924506 bytes
    0 jumbo packets
    0 output error  0 collision  0 deferred  0 late collision
    0 lost carrier  0 no carrier  0 babble  0 output discard
    0 Tx pause
 

interface Ethernet1/8
  description Slot 1/Mid Left
  switchport
  switchport access vlan 1

[MHM Cisco World]

switch# show interface counters errors 

share output please  

[Stuff]

switch# sh interface ethernet 1/8 counters errors
 
--------------------------------------------------------------------------------
Port          Align-Err    FCS-Err   Xmit-Err    Rcv-Err  UnderSize OutDiscards
--------------------------------------------------------------------------------
Eth1/8                0          0          0      14862          0           0
 
--------------------------------------------------------------------------------
Port         Single-Col  Multi-Col   Late-Col  Exces-Col  Carri-Sen       Runts
--------------------------------------------------------------------------------
Eth1/8                0          0          0          0          0           0
 
--------------------------------------------------------------------------------
Port          Giants SQETest-Err Deferred-Tx IntMacTx-Er IntMacRx-Er Symbol-Err
--------------------------------------------------------------------------------
Eth1/8             0          --           0           0       14862          0
 
--------------------------------------------------------------------------------
Port         InDiscards
--------------------------------------------------------------------------------
Eth1/8                0
 

[MHM Cisco World]

https://bst.cloudapps.cisco.com/bugsearch/bug/CSCur72541

this is bug BUT 
"""This is a non-impacting cosmetic issue. It is due to the port receiving packets where the actual number of bytes in the payload are not equal to type length field."""

it not effect your network 
and personally not prefer upgrade if the bug is cosmetic.

[Stuff]

Thanks for the info.  That link states "Workaround: Upgrade to a fixed release version of code, such as 7.0(3)I1(1) or newer" which is from 2015.  My switches are on 9.3(5) from 2020 so would not think it can be the same bug.