In that case disable all power saving on the wireless adapter on that laptop and make sure it has the latest drivers.  With Intel chipsets there is a (2021 from memory) update that pretty much fixed the issue for WiFi5 adapters.  Look at the Intel drivers from their site, the OEM may not have published the newer ones... ... View more

In theory it should only last about 30 seconds, but plan for a few minutes. ... View more

I'd check to see if the same happens when the client has a power adapter connected, it could be a poor driver making a mess of power saving modes. Otherwise, if you have client balancing enabled on that SSID, try disabling it. ... View more

To be honest, in my opinion, the main differences between AP models from Meraki are performance and capacity related.  A CW9166 doesn't necessarily serve a bigger area than an MR32 and if there is a difference in the two it could be that it serves a smaller area as the higher density features actually lower the maximum broadcast strength.    If the original wireless network was low density, then a modern low density model should be fairly like for like, but if they were placed to cope with a medium to high density of clients then you really would want to start again as @alemabrahao said.   Having said that, we usually do just replace in the same place as in a lot of areas we cannot damage the finishes any more.  If it doesn't quite work as expected we infill with an additional, but we hardly ever need to do that. ... View more

@CyberDingo you don't need to move any devices or do everything at once:   Step 1: Create new co-term org and network for hub, set up MX in single ended mode with default route into existing hub site. Step 2: Create network for first spoke in new org and set up new MX Step 3: Delete network of first spoke site from old PDL org and add route to existing PDL MX at hub site, pointing to new MX in co term org's hub site. Step 4: Install new MX at the first spoke site and enjoy the end of phase 1.   Repeat for each spoke and at the end you have the choice of changing the hub MX from single ended to routed, or taking another option. ... View more

If you have a hub and spoke setup, at the main hub install the new MXs behind the existing in single ended VPN concentrator mode.   Then you can migrate one spoke at a time and just change the routing between the two MXs in the hub site each time.   At the end you can rebuild the hub MX into routed mode to replace the existing MSP one.  That will involve some disruption, but if you get a move on you could do that bit on Christmas day 😉   If you don't want that disruption, you could always have another new MX at the edge of the hub site, or any vendor's firewall. ... View more

@K2_Josh from my experience you are often asked to upgrade to the latest stable or stable release candidate by support when there is an issue, if you aren't already on it.  I would always advise to go to the latest version that you feel comfortable with.  We generally only run stable versions in our main data centre, but do run release candidate and beta versions in smaller sites. ... View more

Do you see events logged on both sides and how long was the outage, the events should hint at it. ... View more

I think they are 10Gb only, but to be honest haven't tried one! ... View more

Do the MAC addresses listed also receive IP addresses from the DHCP server? ... View more

Do you have 15 current camera licenses, or if you are using the per device licensing mode, have some expired? ... View more

When converting port 2 on an MX67 we have, it rebooted each time the port was converted from WAN to LAN or LAN to WAN.  This was on firmware18.107.5.   ... View more

I'd vote for that @MeredithW , she has the second most kudos of all time 😉  ... View more

Rapid7 for us, cloud based, but with an on premise collector for logs such as these.  Pretty low cost. ... View more

This is the firmware moving from beta to stable release candidate. ... View more

Well there will be no hardware warranty on these, so the sellers price is somewhat optimistic! ... View more

MS4XX does not include MS42, that is a switch that went end of support over two years ago so it will be running an old software version. ... View more

Wireless firmware versions MR 30.5.1 changelog Important note While Meraki APs have traditionally relied on UDP port 7351 for cloud communication, and TCP ports 80 and 443 for backup communications, with MR 28+ we are beginning the transition to using TCP port 443 as the primary means for cloud connectivity. In order to ensure proper connectivity to the Meraki cloud after this upgrade, please ensure that all “Meraki cloud communication” traffic specified in the "Help" > "Firewall Info" page is allowed through any firewalls or security devices that are deployed upstream of your Meraki APs. These requirements have been updated in November of 2022, so it is important that you review them. (Wi-Fi 6 and Wi-Fi 6E APs) WEP deprecation (https://documentation.meraki.com/MR/Encryption_and_Authentication/WEP_Deprecation_on_MRs) Legacy product notice When configured for this version, MR12, MR16, MR18, MR24, MR26, MR32, MR34, MR62, MR66, and MR72 will run MR 26.8.3 Bug fixes General stability and performance improvements Known issues Sporadic packet loss & instability on Layer 3 roaming & Teleworker VPN SSID's (Wi-Fi 5 Wave 2 and Wi-Fi 6 APs) In high capacity wireless networks, APs may experience instability when the “Client Balancing” feature is enabled (Wi-Fi 5 Wave 2, Wi-Fi 6 and Wi-Fi 6E APs) ... View more

We looked to do the same with one site of 9300s, but the technical migration seems to be write down all the config on a piece of paper, factory reset the 9300s into Meraki mode, then manually reprogram everything...   So we haven't done it.  ... View more

Interestingly, it looks like the devices will still work (without management or monitoring) after the 30 day grace period when there is no active subscription:   After the 30-day grace period and the subscription is inactive all networks bound to that subscription will come to a disable management state. Disable Management Expected Behavior The following is a description of the expected behavior for the devices on networks that experience a disable management event. Devices in the network will preserve their last known license-compliant configuration prior to getting into a disabled state Administrators will lose the ability to configure the devices via Dashboard (GUI or API) Configuration data will not be displayed via Dashboard (GUI or API) Monitoring and health information  will not be displayed via Dashboard (GUI or API) Devices will not have access to customer-initiated firmware updates from Dashboard (GUI or API) Customers will not receive support for devices ... View more

I like that way the Catalyst hardware is blending with the Meraki hardware:   Thanks @GIdenJoe that looks like an excellent new licensing model, though not sure what happens when you move devices between networks, as we do that quite often... ... View more

Good luck and hope it is an amazing time for you 😊 ... View more

We have had some PoE issues and 10Mb problems with MS355s, but no issues with MS225s, they seem quite tolerant.  As for cabling, the Meraki switches seem keener to try higher speeds and do expose flaky cabling more than the Cisco 3850s, 3750s and 2960s we've been replacing. ... View more

It was @MeredithW who introduced me to the firmwarebot, @AmyReyes would you know who in Meraki developed the code and could it be modified to update us when release notes get updated? ... View more