topic RE: Rx CRC and Rx Jabber in ExtremeSwitching (Other)

Rx CRC and Rx Jabber

Ian_Broadway — Tue, 21 Feb 2017 18:01:00 GMT

Hello,

We're experiencing infrequent CRC/Jabber errors on a particular interface between 2 670v-48x switches. Switches are running code version 15.3.1.4 patch 1-18 at the moment. They run our iSCSI network.

Both ports connected together, 49-49 on each switch experience the errors, connected via pre terminated copper cable, Q+CR4_3m.

I have checked that the cable is not in the vicinity of electrical cables to try to rule out interference.

Would it simply be a bad cable/module on the cable that causes this? We've had to change this before so I'm concerned it may be the slot(s) in the switch(es) itself?

Any thoughts welcome 🙂

Ian

RE: Rx CRC and Rx Jabber

Karthik_Mohando — Tue, 21 Feb 2017 18:13:00 GMT

Hi Ian, I would suggest the first and easy step is to swap the DAC cable and see if the RX-errors are changes to the other end.

RE: Rx CRC and Rx Jabber

Drew_C — Sat, 04 Mar 2017 03:42:00 GMT

Hello Ian, are you still having trouble with CRC errors?

RE: Rx CRC and Rx Jabber

Bnoba_CEO — Mon, 21 May 2018 16:33:00 GMT

I have a similar issue. Can someone give a hint on resolution.

RE: Rx CRC and Rx Jabber

Sushruth_Sathya — Tue, 22 May 2018 08:56:00 GMT

Rx Jabber can increment under the following situations -
* packet data length exceeds configured MTU (1518 for non-jumbo and 9018 for jumbo) and/or
* has a bad CRC.

Most likely, it will be a Layer 1 related problem and as a first step as Karthik suggested, it would be best to replace the cable.