Cisco+ Secure Connect:
Cisco+ Secure Connect - Meraki SD-WAN Integration (Regions)
Change: Added note to not change any configuration and also any traffic shaping configurations in Security & SD-WAN > SD-WAN Traffic Shaping page, as it doesn't have any effect on the traffic passing through that Secure Connect regional Hub.
MG:
Cellular Gateway (MG) Firmware Features Directory
Change: Clarified that Passthrough mode is not supported on MG21.
MX/Z:
Meraki Auto VPN - Configuration and Troubleshooting
Change: Updated IP ranges for China cloud (meraki.cn).
Change: Added note that MX supports the use of /31 subnets for WAN uplinks on firmware versions 14.24 or higher.
Change: Added note that the rule for HTTP hostname does not require a catch-all "*" (asterisk) to be prefixed to include subdomains.
Product Firmware Version Restrictions
Change: Added Z4C.
Configuring DHCP Services on the MX and MS
Change: Added additional description for "Mandatory DHCP (only applicable for security appliances)".
Meraki MX/Z Security and SD-WAN Licensing
Change: Added "What is Per Device SD-WAN+ license?" to FAQ.
MS:
Change: Added sections "Licensing" and "MTBF Rating".
MR:
Change: Added Spanish hardware install guides.
Change: Updated pre-splash page behavior "All users will now receive this pre-splash info page. [...] Chromebook and Windows users will also have to open a full browser to http://escapessl.com and provide their Google credentials there".
MV:
Change: Updated power injector SKU MA-INJ-4.
MT:
Change: Added table when a sensor is being marked as offline and offline alerts are sent.
Change: Added Spanish hardware install guide for MT30.
SM:
Change: Added detailed description about the Systems Manger Sentry Policies logic.
General Administration:
Next-gen Traffic Analytics - Network-Based Application Recognition (NBAR) Integration
Change: Updated section "Disabling NBAR Validation Logic".
Change: Updated idle time behavior for MSP accounts to "MSP accounts with multiple organizations having different idle timeouts configured, will follow idle timeout on a per-organization basis. Users are subjected to the minimum idle timeout across the organizations they are currently visiting".
