Hi @Adrian ,   Are you looking for a way to extend the wireless medium with a mesh link?    If so, does something like this implementation suffice?    https://documentation.meraki.com/MR/Wi-Fi_Basics_and_Best_Practices/Extending_the_LAN_with_a_Wireless_Mesh_Link ... View more

Correct, you will need to contact Meraki Support in this instance.    The general Support number is +1 (415) 937-6671. A full list of region-specific phone numbers can be found in the Dashboard under "?" > Get help > Still need help? > Call the Meraki Support team > View regional phone numbers.   ... View more

You could consider adding the ISP gateway IP address under the Uplink statistics tests configured under SD-WAN & Traffic shaping. Clicking the Add Your Destination option allows you to add a custom destination for the MX to continually test ICMP connectivity for monitoring latency and packet loss. At least this way, there can be historical empirical evidence of any latency/packet loss from the WAN of the MX appliance to the ISP device.    The results for these tests will be visible at Security & SD-WAN > Monitor > Appliance status > Uplink > Historical data. ... View more

Correct, you will notice that the MultiWAN backup document does talks about those pairs you've brought up here. MultiWAN backup uplink is a newer feature as well and is designed for having 3 WAN connections.  ... View more

Since there is not a widespread reported issue, in this type of scenario it would be best to contact Meraki Support to conduct live troubleshooting of the behavior to determine what may have occurred during that time frame.    The general Support number is +1 (415) 937-6671. A full list of region-specific phone numbers can be found in the Dashboard under "?" > Get help > Still need help? > Call the Meraki Support team > View regional phone numbers. ... View more

This document will cover the STP guard settings in detail and when they would be recommended: https://documentation.meraki.com/MS/Port_and_VLAN_Configuration/Configuring_Spanning_Tree_on_Meraki_Switches_(MS)   In this case I believe your current configuration follows best practice using Loop guard with UDLD on any of the physically redundant links.  ... View more

Hi @Vlad_Ghimboasa ,   For the MX appliance where you are attempting to utilize WAN3 as a Backup Uplink, are you able to confirm the firmware is on 18.2 or greater?    In order for the MultiWAN Backup Uplink feature to function as expected it does require the appliance be on firmware 18.2 or higher.    For more information regarding this feature, you can reference this doc as well: https://documentation.meraki.com/MX/MultiWAN_Backup_Uplink ... View more

That is correct and expected, with the API call it is pulling from a time range of data. Reviewing the API documentation yes you can define a range however the default is one day.     API Doc: https://developer.cisco.com/meraki/api-v1/get-network-network-health-channel-utilization/ ... View more

The following are the factors that impact the Utilization reporting:    Other wireless networks. Users associated on that channel. Radio frequency being used. Overlapping vs. non-overlapping channels.   Document for reference can be found here: https://documentation.meraki.com/MR/Wi-Fi_Basics_and_Best_Practices/Understanding_Wireless_Performance_and_Coverage ... View more

Org idle timeout is ignored if viewing live footage via the video wall and there is no idle timeout in the full-screen view. Otherwise, the user will follow the idle timeout defined for the Organization.    More information on Vision Portal Behavior and idle timeout can be found here: https://documentation.meraki.com/MV/Viewing_Video/Vision_Portal%3A_Introduction ... View more

Seamless roaming will only occur between APs on the same Meraki network. When roaming between APs in different Meraki Networks, the IP address, policy, and PMK for each client is not shared, resulting in a hard roam where the client devices must fully reauthenticate.    In fact, if you have APs in the same physical proximity, using the same SSIDs but on separate Meraki networks, Air Marshal may trigger an SSID spoofing alert.    For a more in-depth explanation of Roaming Domains and the behavior with Meraki APs along with general Best Practices for Wireless Enterprise deployments with Meraki, I would highly recommend giving this document some time:    https://documentation.meraki.com/Architectures_and_Best_Practices/Meraki_Wireless_for_Enterprise_Best_Practices_-_Architecture   ... View more

That is correct, security inspection such as Content Filtering and Threat Protection is done locally on the MX. The hub/concentrator MX will not inspect traffic from the remote VPN subnets.   You can find this information referenced here: https://documentation.meraki.com/MX/Content_Filtering_and_Threat_Protection/Content_Filtering_and_Threat_Protection_over_Full-tunnel_Site-to-site_VPN     ... View more