Documentation Digest: October 17th-October 23rd, 2025

Hannah-C
Meraki Employee
Meraki Employee

Documentation Digest: October 17th-October 23rd, 2025

DocumentationDigest_banner.png

 

📣Announcement:

Meraki support is currently reorganizing the documentation site to improve navigation. You may notice some changes to content topics and the home page. Existing URLs and bookmarks will automatically redirect to their new locations.

 

 

New articles:

Change: New article.
 
Change: New article.
 
Change: New article.
 
 
Workflows:
Change: Added release notes for the "October 20, 2025" release.
 
 
Secure Connect:
Change: Added section "Manage Your ZTNA Logs".
 
Change: Added section "Removing User Groups and Policy".
 
 
Security & SD-WAN:
Change: Added "As long as the FQDN matches what is configured in VPN Exclusions, the MX will exclude the traffic accordingly, regardless of whether the resolved IP is public or private."
 
Change: Added "Wildcard certificates are not supported."
 
Change: Added "Misconfigured VPN settings".
 
Change: Added "Password: A password required for Azure deployment. This is required for the managed app on Azure as a mandatory input variable, the vMX firmware doesn't use this password and is ignored. Please, feel free to use any default value, ex: MerakivMX1234!@"
 
Change: Added "Content Filtering cannot inspect and block QUIC connections. We recommend blocking UDP ports 80 and 443 using the Layer 3 firewall."
 
Change: Added "The option to configure an exclusion rule is not available if a default route is learned over a Non-Meraki VPN tunnel with a BGP peering."; added "To set a wildcard that includes all subdomains of a domain, for example, all subdomains of 'google.com,' simply enter 'google.com' in the DNS Hostname text box. If you want to exclude a specific subdomain, enter only that specific subdomain, such as 'mail.google.com.'"
 
Change: Added section "Note on Certificates".
 
Change: Added section "AnyConnect VPN".
 
 
Switching:
Change: Added "Due to hardware limitations some C9300 models are unable to run firmware lower than CS16.9."
 
Change: Added section "Voice Auth"; updated "Disable port bounce".
 
Change: Added section "Replacing a Stack Member for Device Configuration Source".
 
Change: Added note that rackmount screws are included with the MS130-24, 24P. 24X, 48, 48P, 48X models.
 
Change: Added "The configuration of routed ports is only available on the New Version of the UI".
 
 
Wireless:
Change: Added Wi-Fi 7 access points.
 
Change: Added "Splash Pages".
 
Change: Added section "Ultra Wide Band Enhancements".
 
Change: Added "Local Auth is not currently supported with WPA3".
 
Change: Added "MR 30 firmware has added support for 802.11r (excluding 802.11r Adaptive mode) to work with most WPA3 encryption options. Network administrators can now configure fast roaming on the network by navigating to Wireless > Configure > Access control > WPA encryption. Cisco Meraki supports Fast Transition with the following WPA3 modes: WPA3 Personal: WPA3 only. WPA3 Transition Mode: WPA3 Enterprise, WPA3 only."
 
 
General Administration:
Change: Added FAQ "How would I bring my MXs and/or Zs that have been sitting on the shelf since we bought them years ago?"
 
Change: Added "'Usage over time' and 'Clients per day”'will display data according to the timeframe specified unless Network-Wide > Configure > General > Client privacy has been configured for a shorter timeframe. The Client Privacy feature is only available for organizations hosted in the Europe region of Meraki Cloud."
 
Change: Added "If a peer has a reduced MTU, the AutoVPN MTU will automatically propagate across the AutoVPN environment and adjust to match the lowest detected value among all peers. Some examples of possible reasons for a reduced MTU include: Primary cellular uplink, PPPoE connection, ISP-assigned DHCP MTU."
 
Change: Added "Workflows" to "Unsupported Solutions/Features".
 
Change: Added section "Automated Workflows".
 
Change: Added release notes for the "Oct 22, 2025" release.
 
Change: Added "MX acts as a NTP Server on each one of its VLAN Interfaces."
 
Change: Added "Systems Manager and vMX licenses can be configured in Dashboard if you have the appropriate suite."
1 Reply 1
RaphaelL
Kind of a big deal
Kind of a big deal

Change: Added "If a peer has a reduced MTU, the AutoVPN MTU will automatically propagate across the AutoVPN environment and adjust to match the lowest detected value among all peers. Some examples of possible reasons for a reduced MTU include: Primary cellular uplink, PPPoE connection, ISP-assigned DHCP MTU."
 
This is partially true. I can't test without the NFO that disables Hub-To-Hub meshing.
 
Other parts of that documentation are also partially true from my tests done in the past year. 69 bytes overhead I haven't seen that and I don't understand how it is possible. In reality it is 68 bytes. 
Get notified when there are additional replies to this discussion.