I have a few Apple TV 4K on the network. Wireless not a hassle. Wired well they are problem children.
The wired clients, every few seconds, give me Port STP changes/Port status changes as in designated→disabled/old: 1Gfdx, new: down/ old: down, new: 1Gfdx
And these are sleeping devices.
Which also give a high proportion of CRC align errors, only on received. When the Apple TV 4K's are actively streaming, Airplaying the CRC errors disappear.
So the theory is on a wired client in order for the AppleTV to act as a HomeKit hub Apple has designed a special WOL packet that messes with Meraki Switches. And the reason the wireless clients are a bother is a) no WOL for you and b) I think Apple uses the sign into iCloud to provide that functionality.
Of course I could be way off here but has any one else seen the flapping Apple TV 4K?
I reached out to Meraki support but nothing more that, new cable, new port and new switch, all of which have not resolved.
As a short term solution could you just set the devices not to sleep?
That's too bad. My setup works 100%.
I have an Apple TV 4K 64GB plugged into my MS220-8P. It works flawlessly.
I've had the Apple TV for a year or more. I've had the MS220-8P for 3+ years. For the Apple TV there are zero events on the MS120-8P log.
My MS120-8P is running MS 10.45 firmware.
Is there anything notably different about your setup?
I'm going to take a wild stab and guess it is using something like Energy Efficient Ethernet and is downshifting its speed when idle to save power, causing a link transition.
Any diff between MS210 and MS220?
If the question was really that... the MS220 (non-compact) is EOL and didn't support stacking. MS210 is a current model and supports stacking. MS220 has the compact model mentioned in this topic, the MS210 doesn't, see below.
However I assume your question was really whether there is a difference between MS120-8FP and MS220-8P. Then the answer is that the MS120-8FP is much more compact and that there's a lower PoE budget version of it called MS120-8LP. The MS220-8P is EOL.
Apparently Meraki support had sent updates to the case I did have open regarding this issue. Of course the four updates, I never received any notification and they closed the case. So I reopened it and we'll see where this goes. It sounds like they know about this bug and it's being ignored. I have sent pcaps, as they requested, and I've asked for an update, but silence from Meraki support. Which, frankly, is pretty normal when something like this occurs. I have asked to have it escalated, but, I'm sure nothing will happen.
I'm experiencing the same issues (port constantly bouncing and high CRCs when sleeping), however I am using a Catalyst 2960S switch.
Interestingly, I bought two Apple TV 4K (32GB) units at the same time, both are running 11.3 and connected to the same switch with exactly the same switch port configuration. One experiences the issue and the other doesn't. I've tried swapping cables, switch ports etc. to no avail. Both are connected to the same iCould account and have the same sleep settings.
The only discernible difference between the two is the TV on which they're connected: Sony Bravia (no issues) vs Samsung.
I will try swapping the Apple TVs between TVs and see if the problem moves or persists.
I also have another customer who's experiencing the same issues connecting on Ubiquiti EdgeSwitches, so I would be surprised if Meraki are able to resolve this issue.
I swapped the Apple TV 4K units between TVs, leaving the power, HDMI and network cables in their original place, and the issue moved with the Apple TV 4K.
So this tells me the issue is isolated to the Apple TV, and nothing to do with the cabling, network config or TV.
Other threads suggested that the issue may be to do with HDMI "chatter", but with the problem moving to the new location on a previously OK TV (different model, HDMI specs and cable), tells me it is not related to HDMI.
Can confirm that I have the same issue on my MS120-48LP running MS 10.45.
I have 7 AppleTV 4k connected and all of the switchports reports very high amount of CRC-errors as soon as the AppleTV is not in use.
I got an answer from Meraki Support:
"We have re-created this issue in a lab environment, It appears that the Apple TV NIC tries to negotiate a half-duplex switch mode in sleep mode.
I can confirm that Cisco Meraki is currently speaking to Apple regarding this issue."
So hopefully Apple will update the firmware or Meraki figure out a workaround for this issue soon.