MR33 CRC align errors

[fabian5]

Does anyone know where crc errors can come from. the cable has already been replaced. The access point has also been replaced.

[Philip D'Ath]

Is the port that it plugs into configured for auto/auto?

[fabian5]

the port configuration is the following:

Description	Trunk port using native VLAN 1; allowed VLANs: all
Tags	none
PoE	Enabled
Link negotiation	Auto negotiate (1 Gbps)
RSTP	Forwarding
Port schedule	Unscheduled
Isolation	Disabled
Port mirroring	Not mirroring traffic

I have already tried all ports

[MilesMeraki]

Do you have a different switch available? - Try the cable and AP in another switch and see if CRC's are still reported - Could be a faulty switch.

[fabian5]

I took an MR32 from another network and this one didn't generate crosstalks.

[Philip D'Ath]

You could also try plugging it into a different switch port.

[fabian5]

update from meraki case team:

"The issue you are experiencing with your MR33 is a documented issue that our engineers are currently taking a look at."

[pjc]

I can't help you, but how do you view packet stats on an MR AP ? I cannot see this in any menu. I running 24.8 (latest stable production), is this in newer beta versions?

Thanks

[fabian5]

the status can be displayed on the MS Switch. not at the MR Access Point

[benspringael]

I am seeing the same issues on the network of a client.

At the moment it's fine again without changing anything. I'll log a support case as well with Meraki.

I'de say keep this topic up to date with any feedback you get from the support team.

I checked the firmware releases and even in Beta I don't see any fixes for this issue.

Cheers,

Ben

[Shaun Bender]

I’m seeing this issue also, with an MR33 on a Meraki MS220-24P switch. I was running 24.7, that’s when I noticed the issues show, then dropped to 24.6, still showing the same issue. The APs are now on 24.11 Stable, and showing the same issue. The MS220-24P is running 9.30 Stable, I’ll be testing with downgrading that later today to see if the issue is still shown.

But as right now, running “Stable” code and seeing the issue, once again makes me wonder what testing is actually done on the Meraki side??

[Shaun Bender]

Update: MR33 is being replaced. Moved AP code back to 25.7 and put in an MR32(as a temp in place of the 33). As of right now, odd that the AP suddenly “died”. However, 32 is not showing any issues as the 33. I have another site with a 33, will test at that location for similiar issues and post a reply.

[fabian5 · Accepted solution]

I have an update from Meraki Support

"We have released a new firmware version, 25-8, which contains a fix for the CRC error issue.

Thank you"

[BradF]

I have a new CNMA stack here in my Lab and since it has been installed I am seeing too many CRC errors between the switch and the MR33. Can I get confirmation of this new firmware it is reporting current.

I have replaced all the cables and switch ports so I am at a loss.

[GreenMan]

25-8 is the latest 'beta'. Your Dashboard may be reporting you're on the latest 'stable / GA'. If you want to try r25 (& there's lots of good stuff in it - see Help > New features) then you'll need to select Try beta firmware under Network-wide > Configure > General (under "Firmware upgrades"). In a combined network, this will, by default, affect switches and MX etc if they exist in the same Network. Dashboard will (currently) upgrade the APs in your Network to 25.8, at the next configured Upgrade window.