How many access points are we talking @CarlMaycock ?   It's my humble opinion that this is terrible customer support. The hardware you have clearly has an issue, they can see it themselves, but are not able to resolve it (software/config) and are unwilling to replace. At the very least they could swap out like (5) of your MR42's and replace them with something else in a corner of your building, so that they can get their hands on your hardware, and test to see what happens.   @MeredithW is there someone you can flag because this seems like the account manager is not doing his job. ... View more

Thanks for the clarification gentleman. ... View more

I'm curious myself as I might be doing something similar. I believe the key benefit of the MG lineup is that it can be placed outside, and that is probably going to be the best way to improve signal.   When I first saw the product and noticed they had an 'e' model for external antenna I wasn't sure why because the only option I could find at the time was dipole, which as far as I can tell is similar to the internal ones, both are omni. Maybe the gain is higher? Can't confirm since I can't seem to find any specs on the internal antenna.   However then I stumbled across this and now it makes sense why they have the external connection option:   https://meraki.cisco.com/product-collateral/meraki_datasheet_mg_cellular_patch_antenna/?file   Spin it around until you get the best signal, or I think there might be some websites with cell tower locations documented etc. ... View more

Joe, let me preface this by saying its nice to have someone else to talk to about this stuff. Although it seems like we might be going off on a tangent from the original topic, my response was still oriented around the uplink port being 1G or higher as a requirement.   What I am getting that currently its only in lab scenario's, or 80MHz environments (rare) where we can push over 1G, however with more clients on the AP (such as very high density VHD) your overall total AP throughput will decrease due to contention.   Also, it has been many years since I did anything close to a VHD installation, so my 200 - 500Kbps was from memory. So you forced me to dig up some old documents I referenced at the time.   I also have limited experience with Wi-Fi 6 (as I assume most do still), so I can reference this link here which covers it some:   https://divdyn.com/wi-fi-throughput/ To clarify, I'm talking VHD with tens of thousands of clients. The RF is the limiting factor at such scale, pretty much any AP vendor has the hardware to handle excessive client counts these days, but you won't be able to squeeze much when you have 100 or more clients on a radio, due to the RF itself I mean, since its a finite resource etc.   I can't imagine any scenario in a VHD setup were you would be running anything other than 20MHz, so that alone (just looking at MCS rates) will be the determining factor of total throughput per AP. Even a 3SS client (laptop only in this example, since handhelds don't go above 2x2 that I'm aware of) at MCS11 is 366Mbps, then cut that in half because wifi 😃   Example 20MHz AP with 100 1SS clients 72Mbps * 50% / 100 = 360Kbps Realistically it would likely be even lower since the 50% is more like 40% due to contention and fall off. So more like 250Kbps each.   To be fair there are a million scenario's that I'm not accounting for, so yes good TPUT can fluctuate all over the place. However when dealing with numbers at such scale, it's been my experience that math has to be performed to get a rough idea of what we are looking at to set expectation with client etc.   Some links from Aruba (which I consider the holy grail for VHD design) from people who have a thousand times more experience than I do with VHD deployments.   https://higherlogicdownload.s3.amazonaws.com/HPE/MigratedInlineFiles/7bc8710bbc014229a17041f8f5a5e6f8_Aruba_VHD_VRD_Engineering_Configuration_Guide.pdf   https://higherlogicdownload.s3.amazonaws.com/HPE/MigratedInlineFiles/7bc8710bbc014229a17041f8f5a5e6f8_Aruba_VHD_VRD_Theory_Guide.pdf   https://higherlogicdownload.s3.amazonaws.com/HPE/MigratedInlineFiles/7bc8710bbc014229a17041f8f5a5e6f8_Aruba_VHD_VRD_Scenario1_Large_Auditoriums.pdf   https://higherlogicdownload.s3.amazonaws.com/HPE/MigratedInlineFiles/7bc8710bbc014229a17041f8f5a5e6f8_Aruba_VHD_VRD_Scenario2_Large_Indoor_Arena.pdf   ... View more

Actually, in those scenario's you would be least likely to need more than 1G. More clients will reduce TPUT overall dramatically. Stadium deployments 1 client ends up with 200 to 500Kbps each when pushed to the limit. ... View more

Can't say for certain to be honest, too many AP's to monitor. The one other issue I know I ran into was on MR32/MR33 (at the time we had nothing else) the 5GHz radio would stop accepting clients, but still broadcast beacon frames, thus creating a black-hole. That was another endless 'upgrade firmware' solution. Only fix was to also change channel or reboot AP. ... View more

Mix of MR32/MR33/MR42/MR72/MR74/MR84/MR36/MR44 ... View more

  So this appears to be the exact scenario that users will run into and as much as I hate to say it, I do not think Meraki will ever be able to find a fix for this. It's been on-going for years. Support will do what they can, but at the end of the day they are going to ask you to upgrade firmware. That is the only solution they have. They never seem to be able to actually get to the root of what causes the performance to go to null, only that changing the channel on the radio, or rebooting the AP, will fix it. This is why I have automated scripts that reboot every AP in every network (at specific times) once a week. I have over 2500 AP's. This is the only solution I could find (at least for me) to be able to get in front of it so that I don't get those complaints. After a case was opened for over 1.5 years with the only solution being upgrade firmware over and over again, I had to do something.  My next step is out the door, to a land more misty. ... View more

Evolution of tech will eventually push 1G into mGig (naturally), same way 10/100 was pushed out a while ago. My assumption is in 10 years, I don't think you'll be able to buy a 1G switch anymore lol.   As for now: Wi-Fi 6 , nah Wi-Fi 6E (still at least 3+ years away for 'large' client adoption as well) - then yeah mGig might actually be nice to have. Need is a strong word because of WAN limitations, but if your traffic is LAN based, and your rocking 160MHz on 6E, or using all 3 bands on the radio, then yeah mGig will actually come into play.   https://www.youtube.com/watch?v=8gvB5MCi9do   With 6E, 80 is going to be the new 20, with regard to MHz. If your in a country that will get all new 1200MHz, then there will be more 80MHz channels in 6GHz, than 40MHz in 5 GHz, currently. Bonus - none of them are going to be DFS, so yeah. The only scenario I can see of going below 80MHz in 6GHz space would be for stadium/LPV deployments. ... View more

You could always just use this:   https://ventevinfra.com/product/wi-fi-right-angle-wall-bracket-with-lid/ ... View more

Well it seems to have self-resolved because now its not doing it anymore, and I didn't do anything to Chrome on either computer. Both are fine now. Must have been an issue on the back-end of the mainframe on Meraki side. ... View more

No reason, just happened to be on that. I'll downgrade to 27.7.1 and test again. ... View more

I forgot to also upload the 3 different sources of reporting for channel utilization (around 80 to 85%). Might be a little more juice yet to be squeezed out of her.   ... View more

Hi all, decided to lab this myself at home and see what results I got.   See below:   As a test, I accessed the local status page of the MR44 and only got ~300Mbps running that test. I'm under the impression the local throughput test is limited and best effort, and not really able to show you what it is actually capable of. See below.   Firmare Version - 28.2 Intex AX200 Driver Version 22.50.1.1   Laptop was connected at a rate of 1201Mbps (reference here: http://mcsindex.com/ - 2x2 client at 80MHz on AX using short guard interval (0.8)).   First I made sure my MR44 was on a clean channel, set to 80MHz (14dBm, laptop is only 5 feet away).         Then I ran the iPerf test on my laptop to a hardwired computer (iPerf server). The MR44 and the server computer are connected to the same switch, both at 1Gbps connections. Test ran for 5 minutes but here is a snippet.         Laptop NIC showing same results         The MR44 AP was also showing similar results on its Summary page. I also included the spectrum analysis from an MR32 nearby.           I also pulled out my Ekahau Sidekick to get a full spectrum capture:             Interesting note, the MR32 above showed 'correct' utilization on its spectrum page. The MR44 and another MR45 nearby, did not show as much and what they did show wasn't even on the correct UNII band. Pretty sure spectrum analysis is 'broken' on the Wi-Fi 6 models.         As far as I can see, the MR44 is performing as expected given that my port is 1Gbps, half-duplex nature of 802.11, and management overhead.   I hope this helps. -Nolan ... View more

What is the client in question? Is it an Intel card? I would try updating the driver if it is.   In addition, is your throughput test 'through' the AP to a hardwired iPERF server or are you access the local status page and running the test to that?  (try the local status page if not and see what you get). What firmware version is the MR44 on and can you confirm your 80MHz channel is 'clean' or being used by other AP's nearby etc. ... View more

28.2   Known Issues MR reboots every 15-20 minutes when connection to Meraki Dashboard is unavailable (Wi-Fi 6 MRs)   Yikes ... View more

If that is the case, that sort of pokes a hole in the 'this issue was introduced with the 27.x train' comment ... View more

You could always downgrade to 26.8.1 ... View more

Another thing if you don't mind trying, is use these commands for the iPerf portion. I've seen big speed differences depending on iPerf CLI commands, and these are the ones that I use when I do my testing.   Try with both   SERVER iperf3 -s -i 1   CLIENT - TCP iperf3 -c <server ip address> -i 1 -t <seconds> -w 1000k   CLIENT - UDP iperf3 -c <server ip address> -u -b 1000M -i 1 -t <seconds> ... View more

Welp that is odd for sure. Assuming the power to the AP is ample and its not running in a low power mode?   Can you try upgrading it to 28.1 (beta) and try again, that might help determine if its a firmware issue or not. Do you have any other AP's available other than this MR56, to test with? ... View more

Try moving to UNII-2, that looks clean.   Also, what driver version is your AX201 running?  Try updating to the latest version.   Assuming the iPerf testing your doing is L2 only?   The Intel AX201 is 2x2, so according to your output, your hitting 1201Mbps which is MCS11, which is as high as it can go. With that rate, and no issues, I would imagine you should be able to hit 800-ish?  ... View more

The channel width at 80MHz is fine, if your environment supports it.   Download a free Windows 10 wireless scanner and see what your RF looks like, and pick a channel that is clean. Feel free to upload your results here for advice. I recommend this (best there is really):  https://www.tethabyte.com/download   Create a text file on your computer being used and paste the following:   :loop netsh WLAN show interfaces timeout /t 5 goto loop   Then save, then rename the file from .txt to .bat (make sure you can see extensions in your explorer settings).   Then run the .bat file and it will show you information like your RX/TX rates etc. Feel free to upload those here as well. Then you can reference this chart, and see which MCS rate your landing on: http://mcsindex.com/     ... View more