500-220 Questions and Answers

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

Table Description automatically generated with medium confidence

The error message “NotNow” is seen in the Event Log on an iOS device's details page when an action cannot be performed because the device is locked with a passcode. These actions include pushing managed apps, installing profiles, and other actions. When this occurs the device will attempt to re-connect with the MDM server as soon as the device is unlocked in order to retry the action. https://documentation.meraki.com/SM/Monitoring_and_Reporting/Status_of_%22NotNow%22_in_Systems_Manager_Event_Log

Quote from referred documentation-Link: Loss and latency will be determined over the configured IP address under Security and SD-WAN > SD-WAN and Traffic Shaping > Uplink Statistics. If no IP is configured, these values will be measured against 8.8.8.8 by default. On the WAN Health page, all the configured IP address statistics can be reviewed by changing the destination under the "Ping Destination" column.

https://documentation.meraki.com/MI/MI_WAN_Health#:~:text=Current%20loss%20and%20latency%20statistics,address%20is%20set%20to%208.8 .

Configuring a syslog server for the network is the Cisco Meraki best practice method to preserve complete historical network event logs. A syslog server can be configured to store messages for reporting purposes from MX Security Appliances, MR Access Points, and MS switches1. The syslog server can collect various types of events, such as VPN connectivity, uplink connectivity, DHCP leases, firewall rules, IDS alerts, and security events2. The syslog server can also help with troubleshooting and monitoring the network performance and security.

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://developer.cisco.com/meraki/api-v1/#!clone-organization

These are the two features and functions that are supported when using an MX appliance in Passthrough mode. According to the [MX Addressing and VLANs] article, Passthrough mode allows the MX appliance to act as a layer 2 bridge, passing traffic between its LAN and WAN ports without performing any routing or address translation. However, some features such as intrusion prevention and site-to-site VPN are still available in this mode.

The settings that will be cloned using the Cisco Meraki MS switch cloning feature are:

• port name
• interface type
• STP bridge property

The settings that will not be cloned using the Cisco Meraki MS switch cloning feature are:

• switch management IP
• switch name

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

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.

https://documentation.meraki.com/Architectures_and_Best_Practices/Auto_VPN_Hub_Deployment_Recommendations

This is the number of tunnels that each hub needs to support in a hub-and-spoke Auto VPN deployment with two NAT-mode hubs with dual uplink connections and 50 remote sites with a single uplink connection. This can be calculated by using the formula for the hub tunnel count in a hub-and-spoke topology1:

Hub Tunnel Count = (H x (H - 1) / 2 x L1) + (H x S x L1 x L2)

Where H is the number of hubs, S is the number of spokes, L1 is the number of uplinks for the hubs, and L2 is the number of uplinks for the spokes. In this case, H = 2, S = 50, L1 = 2, and L2 = 1. Therefore,

Hub Tunnel Count = (2 x (2 - 1) / 2 x 2) + (2 x 50 x 2 x 1) Hub Tunnel Count = (2 x 1 / 2 x 2) + (200 x 2) Hub Tunnel Count = (2 / 2 x 2) + (400) Hub Tunnel Count = (1 x 2) + (400) Hub Tunnel Count = 2 + 400 Hub Tunnel Count = 402

This question is related to the topic of Auto VPN Hub Deployment Recommendations in the Cisco Meraki documentation. You can find more information about this topic in the Auto VPN Hub Deployment Recommendations article or the Meraki Auto VPN General Best Practices page.