Finally fixes ARP entry timing out when still in use:
Solved! Go to Solution.
That one was knocking out a clients Wifi network on a legacy Cisco WLC cluster
Could you place a Cisco WLC on your network and let me know if it kills the wifi every 24 hours
What issue were you hitting @sebas ?
We use a MS250 stack with MS250 access switches.
The stack is connected to a pair of ASR routers and a HA pair of MX's.
It was a long time ago, but we had some strange issues when on a occasion switches rebooted cause of a power failure. The stack remained up due to a connected UPS but the clients could not get connectivity once the access switches finished booting,
Can't give the details anymore but i remember support pointing out to this issue.
So we've stayed at 10.45.
@sebas in Meraki world there is always* only one stable firmware version, up to one stable release candidate and one beta. Hence with 14.5 arriving as beta and neither 12.29 not 12.30 having been popular enough to make it to stable release candidate, they both disappear.
* If there are different currently supported hardware models that do not all support the same firmware train then you may see two in one section. A current case in point is the MR firmware where 802.11ac wave 2 and newer devices use 27.x, whereas older devices use 26.x
tnx for the explanation.
I do find this hard to accept, i want to run stable only and 12.30 contained the fix we wanted.
New versions with features always contain bugs and now we have to wait longer until we get a stable version with the fix we want.
Does anyone know if Loop detection and MAC Flap Detection only detects (and log, does it log this events, right ?) or can also mitigate/prevent such actions ?