@PhilipDAth There is a new "25.11" section here: https://documentation.meraki.com/MR/Firewall_and_Traffic_Shaping/Wireless_Client_Isolation ... View more

If you go to the switch status page and then select the individual port where the transceiver is plugged in, you can see what the switch believes the transceiver is.    What kind of cable are you connecting the two switches with?  ... View more

This sounds like asymmetrical routing. Are you able to view the routing table on the Draytek device to make sure it is properly receiving the routes from the MX side? Double check on your MX config that you have the correct subnets set to "Yes" for being part of the VPN.  ... View more

You cannot have an SX transceiver on one end and an SR transceiver on the other end. You must connect SX to SX and SR to SR. Fiber optics do not auto-negotiate like a traditional copper Ethernet cable does.  ... View more

Good to know that's fixed!   The SSO users are not listed anywhere in Dashboard. You need to create a SAML role which is tied to an attribute you're passing with the users. I'm not sure you can actually configure an org admin access level with this setup.  ... View more

Keep in mind that you cannot actually set the uplink speed in Dashboard higher than the MX is configured to work with. An MX64 for instance will not let you set it to higher than 250Mbps while an MX450 will not let you set it to higher than 6Gbps.  ... View more

The issue I had with this previously is that even if you delete the existing user, and then have them use SSO login, it will not work. Perhaps this has been fixed, but previously it was "expected behavior".  ... View more

Wireless Health is now rolling out in Dashboard! Really awesome tool that should make MR troubleshooting much easier. https://twitter.com/MerakiSimon/status/997154588640927744 ... View more

@RBederian What do you have the minimum bitrate configured at for your SSID showing the issue?   @AReimann Quite frankly I don't think the issue you're experience is what was being discussed in this thread.  ... View more

@cta102 wrote: It's only a suggestion as I haven't used the AP based DHCP so don't have a clue what it's default lease time is (but it's easy enough to check the least details from a connected device) You cannot configure the DHCP options for NAT based SSID's. The AP's use a /8 mask for the NAT subnet so it's very unlikely the scope is running out of addresses (although it's possible there's a hardcoded limit but I still don't believe that's the issue).  ... View more

There are no visible logs for the DHCP service when running in NAT mode. If you contact Support, they may be able to see a bit more info (or at least check AP load CPU/RAM) around the times you're having the problem.  ... View more

What are you doing 1:1 NAT with currently? Did the VoIP provider give you an on-prem device that they are asking you to forward traffic to or something else?    Do you have any traffic shaping rules defined on the MX to ensure voice traffic is giving the correct priority?  ... View more

"All Meraki Access Points support PS-Poll." - this typically means it's enabled by default and cannot be disabled. The client will need to support PS-Poll.  ... View more

Have you verified the Internet connection is up via a wired connection? Are the AP's checking in with Dashboard while this is happening?  ... View more

@Jmezo What kind of WiFi cards are in the Dell's? What driver version are you using with them? I know of at least one district that updated the WiFi driver on their machines and the issue went away. Unfortunately doing that at my district has not helped.  ... View more

I'd suggest to submit this feedback through your Meraki sales partner so they can create/add to existing feature requests. This could potentially be solved with an MV API that does not currently exist.  ... View more

Your MX needs an IP in the subnet of router A, or some link so you can create a static route. Right now you're trying to create a static route pointing to a gateway the MX doesn't have a route to. This is also why you can't ping router A from the MX as there is no L2 or L3 connectivity between those devices.  ... View more

@AReimann wrote: Same issue from here. We also applied the 25.11 release, but no luck. Windows clients running 7 or 10 has packet losses. The same machine when boot with linux OS does not have packet loss. Apple devices like iPhones and Mac Books are not having issues. Did someone fix this already?   We have a open case with Meraki, but looking further here if someone made progress.   Cheers!   Alexsandro Reimann. Have you been able to provide Meraki with monitor mode packet captures while the issue is occurring? I know from the cases that were open no one has provided useable packet caps to help diagnose the issue. This issue is seemingly very difficult to reproduce in a lab/test environment and without monitor mode packet caps it's extremely difficult to see what's happening.  ... View more

This is definitely an oddity of Meraki MS devices currently. As @PhilipDAth points out, you cannot use a L3 interface you've created on the stack as the stack's Dashboard uplink (management). While some people have reported this works, it is NOT supported so you're better off using the link between the stack and your firewall as the management interface.  ... View more

@Bovie2K The Z3 spec sheet is quite clear on its throughput - 100Mb and a further limit of 50Mb for VPN.  ... View more

@Carlos1 Your assessment is correct. The MS225 series includes a single blower style fan which runs at an almost constant (high) speed. All of the MS225 models are quite noisy because of this. There was a manufacturing issue with MS225's last year which caused the fan to prematurely die which led to switches overheating and ultimately failing. This has been resolved now but the loud fan remains.    The MS250 models have a different cooling setup which is more similar to traditional Catalyst switches (multiple smaller fans). Because of this, they are significantly quieter than the MS225 series and would be your best option to use as an edge switch where noise is a concern.  ... View more

@PhilipDAth I'm not saying it's a great fix. But it is an option today which is better than no option at all.  ... View more

If you deploy a single cert to all machines, then all you are doing is verifying any client has that single certificate which is not unique to each client. You will still need the GD cert for the NPS server as the NPS server needs to present a cert to client devices for them to verify the NPS identity. Devices will not connect if they don't trust the cert that is presented from NPS by default as you've already seen.    I am suggesting you deploy a CA and issue certificates to your devices. This way you can verify the device identity, you aren't using a shared cert on all of your devices and you can stick to a single SSID to support all of your clients.  ... View more