If you haven't already, I'd suggest you read this document carefully:   https://documentation.meraki.com/MX/Site-to-site_VPN/China_Auto_VPN Also this one, at a higher level:   https://documentation.meraki.com/General_Administration/Support/Information_for_Users_in_China   Basically, in China you are recommended to deploy Meraki devices into an Organization within the China cloud.    Doing this precludes forming AutoVPN (SD-WAN) tunnels to an MX in a different Organization, of course. If you choose not to follow the recommendation and physically deploy an MX in China, but as part of a non-China Org, while you may or may not get VPN to come up, to other locations, there would be no guarantees around whether it would stay working, nor around its performance . ... View more

Are the devices communicating via bluetooth or WiFi?   To my knowledge both of these technologies leave any roaming decisions to the client device itself  (so check documentation and config / firmware options for those)    If it's WiFi, check to see if there are any AutoRF-related reconfigs of the APs, at the times in question - changing channels or Tx power, that might affect the client's decisions.   You could consider fixing those WiFi parameters through an RF Profile:    https://documentation.meraki.com/MR/Radio_Settings/Manual_Channel_Selection%2C_Transmit_Power_Adjustment%2C_and_Antenna_Configuration ... View more

You could maybe use a script to monitor network usage, in some way, to trigger automated reconfiguration of the shaping settings..   all via the Dashboard API? https://developer.cisco.com/meraki/api-v1/#!get-network-appliance-uplinks-usage-history     https://developer.cisco.com/meraki/api-v1/#!update-network-appliance-traffic-shaping Or - maybe simpler - have the script just change the settings on different days and at different times, to reflect your busy periods? ... View more

Meraki APs have TAM too... ... View more

If you have an existing MX84 and want to add a second device, running warm spare, you have to have a second MX84.   You cannot run warm spare between dissimilar MX models (this includes, for example, MX67 and MX67C). https://documentation.meraki.com/MX/Deployment_Guides/MX_Warm_Spare_-_High_Availability_Pair   If you are routing between your three sites (i.e. you have a different IP subnet or group of subnets per site) then you will have a challenge here, from using MS225 switches;  while they support IP routing at layer-3, they do not support a dynamic routing protocol such as OSPF, which is supported by MS250 and higher.  If this were a green-field deployment I'd recommend a pair of MS250 switches (at least) per site, with each operating as a stack and OSPF then running between the three stacks.   You'd then have a static default route on the Site 1 stack pointing at the Virtual IP address of the upstream MX warm spare pair. If you are running the three sites as a flat subnet you would use Spanning Tree, with the Site 1 stack as the STP Root bridge.  You may need to check that the VPLS service will carry STP frames (BPDUs) to ensure this works properly.  This would, in principle, work with MS225.   Note that such a setup would block one of the links, meaning Site 2 <-> Site 3 traffic would hairpin via Site 1. https://documentation.meraki.com/MS/Port_and_VLAN_Configuration/Spanning_Tree_Protocol_(STP)_Overview ... View more

I think this should be possible.   While an MR can only live within one Network in Dashboard and 'Users' are a Network-wide function, you have the ability to control authorization for each SSID separately.   On the User management portal, under Access policy:  select each SSID in turn and check the 'Authorized for SSID' tickbox for the right group of users in each. https://documentation.meraki.com/General_Administration/Cross-Platform_Content/Managing_User_Accounts_using_Meraki_Cloud_Authentication ... View more

In terms of tools to query data from the Dashboard, I would say that the REST API is a much bigger thing than SNMP.   I doubt any further functionality will be added to SNMP in the future, whereas the power of the API solution continues to grow at great pace:  https://developer.cisco.com/meraki/   Try this rather neat documentation / basic API query page, for a flavour:  https://developer.cisco.com/meraki/api-v1/#!introduction/whats-new-in-v1 Just look for the info you're after in the search window, top left ... View more

For co-term Orgs, I'd claim licences (or orders / serials) using https://developer.cisco.com/meraki/api-v1/#!claim-into-organization  ... View more

As @ww said - they should work fine, but you'll need to configure your existing networking gear to allow the MV cameras access to the necessary Meraki resources in the cloud   (PoE,  DHCP & routing, DNS etc. )  Plus any firewall rules necessary - shown under Help > Firewall info in the Meraki Dashboard. ... View more