Hoping anyone can shed some help with this…
We have an fs.com S5850 switch connected on vlan 35, subnet 10.20.35.0/24, to our Meraki stack. Port set to access mode, RSTP: enabled (forwarding). STP Loop guard.
This fs switch has several devices connected, including:
The difference between these is most likely that the linux server regularly has network traffic to the Meraki, while the HyperDeck-Studio doesn't.
Initially when the fs switch is plugged into the Meraki stack, all devices are pingable. After some time the HyperDeck-Studio cannot be pinged anymore.
A port capture on the Meraki port connected to the fs switch shows this:
1 0.000000 CiscoMer_4f:00:02 Broadcast ARP 60 Who has 10.20.35.112? Tell 10.20.35.1
2 0.007416 Blackmag_18:be:9a CiscoMer_4f:00:02 ARP 64 10.20.35.112 is at 7c:2e:0d:18:be:9a
So it seems the gateway on the Meraki stack queries and receives the mac address for HyperDeck-Studio.
We do have other issues of intermittency in the network, too. They generally involve connectivity to devices on connected non-Meraki switches, or VM hosts, eventually losing connectivity.
We have Unique client identifier (BETA — Recommended for your network) client tracking selected (as recommended by Meraki support), but I am not convinced this is correct because we do not have downstream L3 switches.
Our network roughly consists of the following:
Solved! Go to solution.
Upgrade to MS15.20+ we had the same issue where quiet devices would drop off and not come back with 15.18. 15.20 fixed it. We had the same ARP packets coming to the switch from the device and being ignored. For us this was on a four switch MS355-48X stack.
It's look like a network looping issue. Way are you connecting the Meraki switch on a access port instead a trunk port?
I suggest you to review the connections between the switches.
Upgrade to MS15.20+ we had the same issue where quiet devices would drop off and not come back with 15.18. 15.20 fixed it. We had the same ARP packets coming to the switch from the device and being ignored. For us this was on a four switch MS355-48X stack.
Thanks! We will certainly do that and update here.
The upgrade to MS15.21.1 has solved these issues. Thanks!