This counts the number of times the bytes in a received FCIP Special Frame response did not match what was expected on this link. A mismatch here, rather than a missing response entirely, suggests data corruption or an inconsistency in the handshake parameters between the two ends, a more subtle problem than a simple non-response that might point to a version or configuration mismatch between the local and remote FCIP implementations. A steadily incrementing count here, with responses actually arriving but failing the byte match, would push an admin to check for a firmware or configuration version mismatch between the two FCIP entities rather than assuming a pure connectivity issue.