Register or Sign in
Turn on suggestions
Auto-suggest helps you quickly narrow down your search results by suggesting possible matches as you type.
- About luhiadmin
luhiadmin
Comes here often
Member since Sep 7, 2017
3 weeks ago
Community Record
10
Posts
0
Kudos
0
Solutions
Badges
3 weeks ago
Thanks for the response. I'm not running into any issues with subnets running out of IP addresses to assign. All APs broadcast the same two SSIDs (staff wifi, and general wifi), so roaming between APs does not trigger a new DHCP lease. I looked around in wifi settings more and have made some changes to Meraki's Wireless Access control -> 802.11r settings for the "reduced overhead when a client roams from one AP to another".
... View more
3 weeks ago
I work in the IT department at a medium size high school (about 1000 students). During passing periods the wifi mostly stops working. My theory is that this is due to the huge number of devices that are all on the move simultaneously (roughly 2000 devices) and connecting/disconnecting from many APs over the course of the passing period. Are there settings that could be adjusted to help with this issue? Does anyone else have this issue? If so, have you found a solution? Thanks.
... View more
Labels:
- Labels:
-
Other
12-15-2017
10:52 AM
We tried most/all of the suggestions here - thanks - and someone's suggestion to reduce MTU size, but nothing had an effect. In an attempt to generate outgoing traffic, we found a way to easily browse to thousands of webs (Chrome extension + list of top 1M sites); it sort of worked but mostly we just locked up laptops. Comcast tier 2 tech could have been more helpful. Anyway, we bailed, cancelling this service; so we'll never know why...
... View more
12-05-2017
08:45 AM
We throttled to 750/35 (and earlier 500/25), didn't help. Barring new clues from iperf, another continuous ping, etc. tests, we're giving up. Comcast is convinced it's not their problem, despite a failure when our net was disconnected. Only happens under load. Oh well. I'll summarize when we're done.
... View more
12-05-2017
08:44 AM
We throttled to 750/35 (and earlier 500/25), didn't help. Barring new clues from iperf, another continuous ping, etc. tests, we're giving up. Comcast is convinced it's not their problem, despite a failure when our net was disconnected. Only happens under load. Oh well. I'll summarize when we're done.
... View more
11-29-2017
03:07 PM
For posterity I'll document what we've done here the last 3 weeks: Comcast has tested Everything, short of replacing modem (new, no spares). We've tested Everything - swapped internal connections, lots of tests. The behavior: after ~20 minutes we see high packet loss / high latency, the router can go comatose for a few minutes, and even Comcast's modem can spontaneously reset. A 250 Mbps circuit has no problems. We disconnected the 250, no change. We're back to wondering if the router really can handle a gigabit circuit (at its 750 Mbps max). The 20 minute buildup to problems makes me (newbie) wonder. On the other hand, it seems someone's suggestion here to throttle the router at 500/25 would have circumvented a router issue. I'll call tech support again, we may get a replacement modem, we plan to do an iperf test at the modem, and may do a load test with pingplotter running at the modem.
... View more
11-22-2017
11:42 AM
We thought it might be the fiber conversion boxes on "forced" instead of "auto", but that made it worse. Comcast thought it might be an incorrect duplex setting on their end, but that also made it worse. I'll swap misc. parts, they'll swap modem, and we're done - it either works or it doesn't and we bail.
... View more
11-22-2017
11:41 AM
We thought it might be the fiber conversion boxes on "forced" instead of "auto", but that made it worse. Comcast thought it might be an incorrect duplex setting on their end, but that also made it worse. I'll swap misc. parts, they'll swap modem, and we're done - it either works or it doesn't and we bail
... View more
11-22-2017
08:11 AM
Good advice. We reset the gigabit from 1000/40 to 500/25, but unfortunately no change in errors. Over Thanksgiving we will swap all parts (one at a time) and test under load. If Meraki or Comcast have no more ideas, we're going to cancel Comcast's gigabit coax service. We're the first to try it in this area; their own tier 2 has no experience with it, so it could be anything - the modem, who knows. Thanks.
... View more
11-21-2017
09:40 AM
I realize an MX100 maxes at ~750 Mbps, but we have one on Comcast's new gigabit coax service (along with a 250 Mbps coax circuit, in fail-over) and it just isn't working. The 250 Mbps works, the gigabit has high (25%-100%) packet loss and high latency, it fails over for one minute several times a day, and occasionally throughput goes to zero without failing over. Comcast thinks their end is OK (one pingplotter and continuous ping test at modem didn't reveal anything); they do think we're maxing the gig's up speed, 35 Mbps, but the 250's up speed, 25 Mbps, doesn't cause issues). The only other factors I can think of: the 250 Mbps circuit is extended from demarc to server room with coax (modem by router), the gigabit by fiber (modem at demarc) we have high internal traffic from security cameras, but it is VLANed off we're having other recent problems like computers not consistently finding printers, AD server, or wifi APs all of this - router, gigabit circuit, VLANing, cameras - are new. We don't have the skills to properly debug this, so we're going to swap parts, circuits, etc. to isolate the issue.
... View more
