Table Description automatically generated with medium confidence

https://documentation.meraki.com/MX/Firewall_and_Traffic_Shaping/MX_Load_Balancing_and_Flow_Preferences#Load_Balancing

https://developer.cisco.com/meraki/api-v1/#!clone-organization

A screenshot of a computer screen Description automatically generated

https://documentation.meraki.com/General_Administration/Cross-Platform_Content/Creating_and_Applying_Group_Policies

SM Sentry enrollment can be enabled on any MR network via the Splash page section of the Wireless > Configure > Access control page. https://documentation.meraki.com/MR/MR_Splash_Page/Systems_Manager_Sentry_Enrollment

When a rogue access point is contained, clients will be unable to connect to the rogue AP. Additionally, any currently associated clients will lose their connection to the rogue AP. https://documentation.meraki.com/MR/Monitoring_and_Reporting/Air_Marshal

This is because the SD-WAN policy for “All Databases & cloud services” has the following settings:

• Uplink selection policy: Prefer WAN1, Fail over if down
• Traffic filters: Custom performance classes
• Custom performance classes: Database
• Database performance criteria: Maximum latency 200 ms, Maximum jitter 20 ms, Maximum loss 1%

This means that the SD-WAN traffic will be routed via WAN1 by default, unless WAN1 is down or fails to meet the database performance criteria. In that case, the traffic will be routed via WAN2, if WAN2 meets the database performance criteria. Therefore, the condition that will cause the traffic to be routed via WAN2 is when WAN1 tunnel latency is 20 ms or more (which exceeds the maximum jitter of 20 ms), and WAN2 tunnel meets the configured performance criteria (maximum latency 200 ms, maximum jitter 20 ms, maximum loss 1%).

There are two operations in which a license can be applied, License more devices or Renew my dashboard license. This article will compare both operations and describe their behaviors. https://documentation.meraki.com/General_Administration/Licensing/Meraki_Licensing_-_License_More_Devices_vs_Renewal

These are the two operations that enable licenses to be applied in an organization that uses the Co-Termination licensing model. According to the Meraki Co-Termination Licensing Overview, there are two ways to add licenses to an organization:

• Renewing the Dashboard license: This option allows you to extend the co-termination date of your organization by purchasing new licenses for the same or longer term as your existing licenses. You can renew your Dashboard license from the Organization > Configure > License Info page or from the Meraki Dashboard homepage.
• Licensing more devices: This option allows you to add new devices to your organization by purchasing new licenses for them. You can license more devices from the Organization > Inventory page or from the Meraki Dashboard homepage.

The number of devices in an organization can not exceed the license limits. If this occurs, the organization will enter a 30-day grace period, during which the organization must be brought back into compliance, otherwise it will be shut down until proper licensing is applied to the organization. https://documentation.meraki.com/General_Administration/Licensing/Meraki_Co-Termination_Licensing_Overview

Assuming this MX has established a full tunnel with its VPN peer, the MX will route the WebEx traffic based on the SD-WAN policy configured in the exhibit. The SD-WAN policy has two performance classes: Conf and Default. The Conf performance class matches the traffic with destination port 9000, which is used by WebEx for VoIP and video RTP3. The Conf performance class has a preferred uplink of WAN 2 and a failover uplink of WAN 1. It also has thresholds for latency, jitter, and loss that determine when to switch from the preferred uplink to the failover uplink. Therefore, the WebEx traffic will prefer WAN 2 as long as it meets the thresholds in the Conf performance class. If WAN 2 exceeds the thresholds or goes down, the WebEx traffic will switch to WAN 1 as the failover uplink.

See Permissions by Network Tag section To simplify the assignment of network-level permissions in an organization with many networks, permissions can be granted to users for a given network tag. https://documentation.meraki.com/General_Administration/Managing_Dashboard_Access/Managing_Dashboard_Administrators_and_Permissions

The Organization > Configure > Manage Tags page allows Administrators to configure a combination of Network and Device specific tags to create Summary Reports filtered for specific devices across multiple networks. https://documentation.meraki.com/General_Administration/Organizations_and_Networks/Organization_Menu/Manage_Tags

IOS:

• Kiosk mode
• Single App mode
• Wallpaper
• Cisco Security Connector
• Active Sync

Android:

• Kiosk mode
• Backpack
• Wallpaper
• Active Sync

This question is related to the topic of System Manager: Getting Started in the Cisco Meraki documentation. You can find more information about this topic in the [System Manager: Getting Started] article or the [System Manager Overview] page.

https://documentation.meraki.com/SM/Profiles_and_Settings/Configuration_Settings_Payloads

https://documentation.meraki.com/MX/MX_Installation_Guides/vMX_Setup_Guide_for_Microsoft_Azure

To clarify, when an SSID is configured with Sign-On Splash page enabled, the two settings that must be configured for unauthenticated clients to have full network access and not be allow listed are:

• Controller disconnection behavior: This setting determines how the clients are treated when the Meraki cloud controller is unreachable. The options are Restricted or Unrestricted. The former option blocks all traffic from unauthenticated clients until the controller is reachable again. The latter option allows unauthenticated clients to access the network without signing on until the controller is reachable again1.
• Captive Portal strength: This setting determines how often the clients are redirected to the splash page for authentication. The options are Block all access until sign-on is complete or Allow non-HTTP traffic prior to sign-on. The latter option allows unauthenticated clients to access other protocols such as DNS, DHCP, ICMP, etc., but blocks HTTP and HTTPS traffic until they sign on. This option is recommended for compatibility with devices that do not support web-based authentication1.

https://documentation.meraki.com/Architectures_and_Best_Practices/Cisco_Meraki_Best_Practice_Design/Best_Practice_Design_-_MR_Wireless/Wireless_Layer_3_Roaming_Best_Practices

This is a feature of distributed Layer 3 roaming, which maintains layer 3 connections for end devices as they roam across layer 3 boundaries without a concentrator1. The first access point that a device connects to will become the anchor access point1.

https://documentation.meraki.com/MV/Initial_Configuration/Privacy_Windows

Implementing syslog versus SNMP can meet the design requirement of gathering information such as flows and client connectivity. Syslog can collect and report various types of events, such as VPN connectivity, uplink connectivity, DHCP leases, firewall rules, IDS alerts, and security events. Syslog can also provide detailed information about the flows and client connectivity on the network devices, such as source and destination IP addresses, ports, protocols, bytes transferred, etc. SNMP, on the other hand, can collect and report various statistics and information about the network devices, such as CPU utilization, interface status, memory usage, etc. However, SNMP does not provide as much information about the flows and client connectivity as syslog does.