Meraki to HPE network cable

[jmorphew]

We are connecting a Meraki MS425-16 to an HPE Aruba Networking CX 8100 and receiving a lot of CRC errors.    Due to lead times with Meraki cables, these are the cable being used: Cisco SFP-H10GB-CU3M to Cisco Meraki MA-CBL-TA-3M Compatible TAA Compliant 10GBase-CU SFP+ to SFP+ Direct Attach Cable (Passive Twinax, 3m)

I am not a network engineer, but I am working with one.  We thought a cable was faulty but replacing it did not resolve the issue.  We do not see the same errors over 1 Gbps copper.  I am wondering if the type cable being used is incorrect.  Any advice would be appreciated.  

[cmr · Accepted solution]

Have you tried with a Meraki transceiver in the MS425 and an Aruba one in the CX 8100 with an OM3/4 patch cable?  DACs can often cause issues, especially non OEM ones, so I would try that first.  If that fixes it, then the DAC brand is the problem.  Other DACs may work if that one fails.

[jmorphew]

Thanks.  We got some refurbished Meraki/Aruba transceivers and that resolved the issue.  Now just waiting on the new ones to arrive in a month or so.

[PhilipDAth]

Tried firmware updates on both switches?

[Brash]

Try a non-passive twinnax cable if you've got one. My experience of passive twinnax is that they're more prone to CRC's. Other than that, try fiber which is generally more reliable - especially cross vendor.

[GIdenJoe]

Switch vendors do not like when you use a DAC cable from another vendor.
I don't know if this exists but if you would have a DAC cable where each module is configured with the corresponding vendor then that should theoretically work.

However it may be a better idea in this instance to go with the more expensive option which is SFP - Fiberpatch - SFP.

[cmr]

FS.com do make up cables that mimic different vendors at each end, but of course they are not OEM cables...

This is the cable https://www.fs.com/de-en/products/49577.html

[jmorphew]

Thanks, SFP - Fiber - SFP is the route we ended up going and it seems to be working much better.