SFP 26 CRC Errors

[NickOlsen]

Hey Guys, Just got 2x WS-24-400A's in. And so far I'm loving them. Loaded up 1.1.5 on them both.

Anyways, I'm running into an issue. Thankfully, This is during testing. So it's just sitting here on my desk.

I've got a MaxxWave Single Mode SFP in Port 26. This connects to another MaxxWave Single Mode SFP via singlemode fiber. The device at the other end is a Mikrotik CCR 1036-12G-4S. As I said, This is connected on my desk, ~10ft of fiber between the two devices.

Now, Leg two. I take another Mikrotik CCR 1036-12G-4S and via ethernet connect it to the switch. I assign both cloud core routers IP's and bandwidth test between them.

In order to get the Fiber based CCR to link, Auto Negotiation must be disabled on the CCR.

When the SFP is inserted into SFP 26, As soon as the link comes up. The Netonix interface starts showing errors on the port. When viewed in detail, They appear to be CRC Errors.

If I take the SFP out of 26, And move it to SFP 25 (Or any of the other four shared SFP ports) they work completely as expected with no error. Port 26 also displays packet loss and poor throughput which was expected due to the CRC errors.

I've tried different Fiber and SFP's. As well as ethernet ports on the copper cloudcore side. Remember, These same SFP's work fine in other SFP ports of the Netonix.

And finally, I've reproduced this same issue on both of our WS-24-400A's.

I'm not sure what the proper procedure is for reporting these problems. Or if there is a formal support channel. Please let me know. Thanks!

[JustJoe]

Any chance you have a lighted magnifying glass? I once caught a bit of debris stuck to one of the SFP socket's pins that was causing it to be intermittent with CRC errors on a new MT switch.

[NickOlsen]

Unfortunately not. With that being said. The number of times I've plugged/unplugged the fiber and sfp to move it to other ports on the switch, It surely would've presented itself on another port besides SFP26. I've also tried a different fiber.

[FLHSI]

Appears to be fixed in 1.2.0RC6