I haven't had the issue after 25.12 when I updated. I'm running similar hardware on a couple systems, Dells with Intel cards. Though, we have way more HP these days, so it's not a good measure to know for sure. ... View more

My sample size is much smaller, but it was limited to sites with very vocal users and one or two APs at each. Been running 25.12 without complaint.  ... View more

I'm updating my clients's APs that were having issues before. We'll see how those sites do later this week, and I'll report back if I have any issues. ... View more

@MRCUR Well, 2 of the APs are taking on very few to no clients when client load balancing is enabled. Even when they do take a client it will stay connected for about 30 seconds then disconnect. Some clients managed to stay, but then they would disconnect at 30 minutes, or 2 hours. It was weird.   I saw the basic release notes, which always contain several super vague potential issues, but didn't see anything specifically about CLB.   " Bug fixes A corner case would cause AP to stop serving clients. (MR42/52/53/84) A corner case where APs could be potentially re-flashed upon boot up (All MR’s) APs would lose connectivity dashboard and reboot (MR16/66) Performance improvements for Distributed L3 roaming (MR42/52/53/84) Erroneous DFS detection on some APs under certain conditions (MR26/32/34/72) Regulatory domain support for Curacao Outdoor APs in the IC Regulatory Domain to not broadcast channels on frequencies higher than 5.35 GHz (Channel 64) Event log Improvements Client Steering performance improvements (All MRs) BLE Performance Improvements (MR33) Tuned MCS EVM to improve rate vs range (MR42) Bridge Mode Wireless Client isolation prevents access to splash pages Known issues Condition under investigation causes 2.4GHz radios to become unresponsive (MR32/MR72) Condition under investigation causes radios to become unresponsive for 5 seconds in high-density networks (MR34/MR32/MR72/MR26) Condition under investigation causes lower than expected throughput on the 2.4GHz radio (MR26/MR34) APs lose connectivity to dashboard until reboot in certain cases (MR33/74) Other General Performance Improvements "   At any rate, I've rolled back my MS and MX, and the APs are doing the same thing. I'm not sure what triggered the issues we're seeing currently, but I've turned client load balancing back off and will update teh APs to 25.10 tonight to see if that changes anything. ... View more

Okay guys, try this on for size.   Apparently the APs were updated to 25.9 4 weeks ago. We didn't have any problems that anyone noticed until I updated our MX84 to 13.28 from 12.24. I got confused because I triggered an update for the MX and MS, and considering the issues we've had, assumed it had to do with one for the MRs as well.   This is a relatively new client for me, so it's hard to say for certain if there were issues when the update to MS 25.9 went off, but I'm putting my settings back and rolling the MX back to 12.24 to see what happens.   Weird, y'all. I'll report back tomorrow. ... View more

We're behind an MX84 here. We have an MS220-48 that the AP aren't running off of, because it's not PoE. We adopted this network, and they put in a basic HP PoE Switch in a flat config to hook up the APs.   Turning off Client Load Balancing seems to have helped the issues we're having. People are able to subscribe again, but without the load balancing, two of the APs now have 26 and 29 clients while the other two have 6 and 7. On previous versions of the firmware where client load balancing was working better, this split looked much better. I may roll back tonight just to confirm and test. ... View more

We're seeing the exact same thing you are. We have 4 AP, and two of them are trying to service all the subscribers while the other two constantly point subscribers to the overloaded pair. Very weird, Meraki support worked on it some today, but couldn't find anything wrong with the configuration.   I've disabled Client Load Balancing for now, I'll update tomorrow to see if the problem units start behaving as expected. I may also revert to pre-v25 if I'm still having issues, or maybe the 25.10 SRC. *shrug* ... View more