mlxlink on ConnectX-4 reports compliance code mismatch at 25G: a 10G DAC was in use
A ConnectX-4 connected by DAC to another NIC forced to 25G without auto-negotiation and without FEC passes a PRBS31 test with zero errors, yet mlxlink prints a troubleshooting hint aout a compliance code mismatch (Status Opcode 16, Group Opcode PHY FW). The device reports supported speeds 25G, 10G and 1G. What does the message mean and can the link be forced?
Comments 2
The attached DAC was a 10G SFP+ cable while the requested rate was 25G. The compliance-code warning refers to what its EEPROM declares, not just whether a PRBS pattern passes over the copper.
Repeat the test with a qualified 25G SFP28 DAC. A zero-error PRBS run is useful electrical evidence, but it does not change the cable's advertised capabilities or the firmware's module checks.