...
There have large TX_FRM_ERROR packet under FEX HIF interface: woo> show stats 0 HI0 +----------------------+----------------------+-----------------+----------------------+----------------------+-----------------+ | TX | Current | Diff | RX | Current | Diff | +----------------------+----------------------+-----------------+----------------------+----------------------+-----------------+ | PORT CNTRS HI0 | +----------------------+----------------------+-----------------+----------------------+----------------------+-----------------+ | TX_FRM_ERROR | 7124054| 7124054| | | | <<<<<<< But those counters do not relate to "output error" under "show interface Eth111/1/1" output: N9K-C93180YC-EX# show int e111/1/1 | in Eth|CRC|RX|TX|packets|error Ethernet111/1/1 is up Hardware: 1000/10000 Ethernet, address: 5006.04ab.4e02 (bia 5006.04ab.4e02) EtherType is 0x8100 30 seconds input rate 24 bits/sec, 0 packets/sec 30 seconds output rate 395842264 bits/sec, 49283 packets/sec 300 seconds input rate 72 bits/sec, 0 packets/sec 300 seconds output rate 395912112 bits/sec, 49291 packets/sec RX 7773 unicast packets 168 multicast packets 3 broadcast packets 7944 input packets 637797 bytes 0 jumbo packets 0 storm suppression bytes 0 runts 0 giants 0 CRC 0 no buffer 0 input error 0 short frame 0 overrun 0 underrun 0 ignored 0 Stomped CRC TX 8125348 unicast packets 288 multicast packets 3 broadcast packets 155977383 output packets 156601061622 bytes 0 jumbo packets 0 output error 0 collision 0 deferred 0 late collision <<<<<<<<< 0 output error
FEX connects to N9K. Day one issue, impact all software versions.
attach to FEX and use "show stats all" command to check whether N2K HIF port sends error packets out. For CRC O/P errors use command show interface ethernet // counters detailed. Check value : "Output CRC Errors"
NA