@ITConnect, good to know that the only switch clients view works for you too. 👍 ... View more

Good news , I received today the replacement . :-)))   Hope that they are not defective, I will install when I can. We close the premises due to COVID-19.   I had to fight hard and after 30 emails to the support they finally push the right button.     ... View more

We have an MX HA pair at each site and a stack of physical switches that they connect to.  We cable one MX to one switch and the other MX to one of the other switches.  Therefore if either MX fails you still have a connection to the switch stack.  Equally if the switch connected to the active MX fails, the other MX takes over and as it is linked to a remaining working switch, you still have a connection.  Worst case where you get a partial failure on a switch, as the MXs are connected to the dashboard via the WAN ports, you can force a failover. ... View more

Very helpful. Similar to the help I received from Meraki support. ... View more

I also use Fiberstore SFP modules in my MS350 switches as well as my MX250 firewalls. No problems. ... View more

Thanks for getting back so quickly.   Yep, F/W attaches to VLAN 1.  I'll double check NAT for VLAN 2 and 3 and will get back, but I'm sure this is in place. ... View more

Thanks CJ for the links as well as @BHC_RESORTS and @Fruju for your advice I think the deployment should go well I have been trying to bone up on my overall wireless knowedlege and the Meraki wireless products as well  ... View more

So you are looking for client-to-site/remote access VPN connection using MX. No you can't do it, it supports site-to-site VPN only.   You don't need UserID or Username for a site-to-site VPN scenario. Preshared key with encryption methods in phases should suffice. You can ask your VPN provider to provide required site-to-site VPN parameters, if they allow.   I dont see any standard firewall also supports it. Only option left is using DD-WRT, Tomatoe firmware, etc. Cisco ISR can be used as well. ... View more

As earlier said; The roaming choice is decided on the client device itself which mainly is based on beacon frames and probe requests. Refer to the following document which outlines this in more detail and recommendations to weak these settings on a client device -decision https://documentation.meraki.com/MR/WiFi_Basics_and_Best_Practices/Client_roaming_and_connectivity_decisions_explained  ... View more

I would also suggest getting a professional wireless site survey performed.  It's not just the interference from your own devices that needs to be considered, but also that coming from neighbouring AP's in nearby building/office floors.     I have found in the past that the Meraki auto ordering of channels does not always work as well as it should, and manually setting them can prove more successful.     As always proper planning prior to deployment can aleviate problems further down the line. ... View more