No, you cannot disable Internet Hunting on a per-VLAN (or any) basis on Meraki MS switches. It is hard-coded behavior. When an MS switch loses connectivity to the Meraki Dashboard, it will: Attempt DHCP on any VLAN it can see Continue “hunting” until it gets any valid IP with internet access Prefer cloud connectivity over respecting intended VLAN roles This behavior is by design and applies globally across all VLANs. Discovered a hidden "feature" in MS125-48LP to start hunting all VLANs if Internet is lost.  Behavior during Connection Loss to Cisco Meraki Cloud    Because of this, Meraki switches are generally not recommended as WAN-facing or WAN-adjacent devices. Many customers resolve this by placing an unmanaged (dumb) switch or non-Meraki L2 device between the ISP and their HA firewalls to prevent the Meraki switch from ever seeing the WAN VLAN. ... View more

The MS210 series are on the EOL list - which is another reason to think the overall configuration/setup. Meraki End-of-Life (EOL) Products and Dates  ... View more

I would assume so based on available documentation but you can always open a support ticket if you need a support provided answer/response. > What exactly does “regular intervals” mean in this context? You asked about the intervals which is listed above for your consideration and I'm not aware of it being different whether it's PDL, co-term or subscription. > Is it possible to customize these notification intervals? It is not possible to customize the notification intervals for license expiration emails. The intervals and content of these notifications are managed by Meraki and cannot be adjusted by the customer. If you need more granular control or specific notification intervals, you may consider implementing a custom monitoring solution using the Meraki API to track license expiration dates and send alerts as needed. ... View more

Will I be notified before my license expires? Yes, administrators listed on the account will be sent Alerts and notifications outlining the steps for license extension. Additionally, email alerts will be sent out periodically to Dashboard Administrators. If the Organization is out of compliance (e.g., more devices in use than licensed), email alerts will be sent at the following intervals: 30 days, 21 days, 14 days, 7 days, and 1 day. If the Organization is in compliance, email alerts will be sent at the following intervals: 90 days, 30 days, 2 days, and 1 day   Meraki Licensing FAQs  ... View more

To retain local DNS resolution for domain resources, configure your DHCP scopes to hand out your internal DNS servers directly to clients. This allows clients to resolve internal resources while still using public DNS for Internet-bound queries.  ... View more

The WAN DNS settings are intended for public or ISP-provided DNS servers, which are required for proper MX operation, including Internet connectivity checks, Dashboard communication, and VPN registration. Using internal DNS servers on the WAN interface can disrupt these functions. ... View more

Is it only available for x86/x64? ... View more

Exciting stuff!!! Cloud EVPN Fabric: provides the simplicity of a unified layer 2 network combined with the stability, speed, and scalability of layer 3 routing, all easily managed from the cloud with minimal manual configuration. Cloud EVPN Fabric Overview Cloud EVPN Fabric Installation / Lab Guide ... View more

It would be ideal if the images depicted in the Cloud EVPN Fabric Installation / Lab Guide  were a bit larger to be able to see what is being displayed in each (or able to open them by clicking on the image). They are too small to view as published. ... View more

AI assistant suggests these troubleshooting steps: Check Umbrella Reporting Integration Replace the Umbrella Reporting API key in Secure Connect. Go to Secure Connect > License & API Keys and use the "Replace API credentials" option on the Umbrella Reporting credentials card. Follow the instructions to retrieve and apply a new key, then verify if stats appear in Secure Connect. Cisco Secure Connect - Account Setup Troubleshooting Confirm Data Storage Location Alignment Check the data storage location in both dashboards and ensure they are paired correctly (e.g., US with North America, Europe with Frankfurt). If misaligned, follow Umbrella documentation to correct the region pairing. Reserved IP Guidelines Review Firewall and Routing Configuration Ensure firewall rules in Secure Connect allow agent traffic to the Internet. Traffic to Meraki and ThousandEyes backend should be excluded from HTTPS Inspection. DNS traffic (port 53 to Umbrella resolvers 208.67.222.222 and 208.67.220.220) should be bypassed from Secure Connect tunnels to avoid policy mismatches and reporting gaps. Umbrella SDWAN Connector Deployment Guide Use Umbrella Reporting Tools for Verification Verify egress source IP addresses and traffic details in Umbrella by using the Activity Search page and filtering by egress data center. This helps confirm that traffic is being processed and reported correctly in Umbrella, even if Secure Connect is not showing stats. Umbrella Reporting Tools General Integration Checks Ensure the Umbrella and Meraki dashboards are properly linked via API. Confirm that the correct policies are assigned and that UDP 443 traffic is allowed to Umbrella endpoints. Manually Integrating Cisco Umbrella with Meraki Networks Summary of Next Steps: Replace the Umbrella Reporting API key in Secure Connect. Verify and align data storage regions between Meraki and Umbrella. Review firewall and DNS exclusion rules. Use Umbrella’s Activity Search to confirm traffic visibility. Double-check API integration and policy assignments. If these steps do not resolve the issue, please provide more details about your Secure Connect and Umbrella configuration, or contact Cisco Meraki support for further assistance. Sources: Cisco Secure Connect - Account Setup Troubleshooting Reserved IP Guidelines Umbrella SDWAN Connector Deployment Guide Manually Integrating Cisco Umbrella with Meraki Networks       ... View more

You will likely need to work with your Meraki partner and/or support. ... View more

Organizations using active legacy licensing models, such as Co-term or PDL, are unable to claim subscription license keys. Mixed licensing modes are not permitted​​​​​​.   Subscription - Licensing Claim Cloud    Subscription License keys can only be claimed by an expired organization, an organization in a grace period, or a newly created organization (this includes ones created via Organization split).  ... View more

What firmware are you currently running? Initial thoughts: this doesn't sound like a community fixable issue however you might consider opening a support ticket with engineering. Ways to Contact Meraki Support  ... View more

  Meraki Support  ... View more

Normally an indication of a client being further away from the AP.  Dense building materials could factor into that equation a bit too. ... View more

Perhaps so (kinda expensive) but it is an outdoor option. ... View more

Cisco Wireless CW9179F Access Point  ... View more

Are you an organization admin?   You can also customize this setting Organization > Configure > Settings by adding your e-mail address for licensing, hardware defects, and maintenance. ... View more

The WAN breakout switch should be in it's OWN (separate) network - not part of your downstream switches. ... View more

Give your feedback (previously Make a Wish)  ... View more

Give your feedback (previously Make a Wish)  ... View more

There is no method to delete Meraki AP connection logs or timeline logs from the Wireless > Overview section in the Meraki Dashboard. These logs are retained for network monitoring, troubleshooting, and historical analysis, and the Dashboard does not provide an option for administrators to manually clear or delete them. You can filter and view up to a month's worth of connection history, but deletion is not possible. ... View more

I'm not aware of any backend tweaks.  If this hub doesn't truly need to be full mesh hub, you could consider the idea of converting it to a spoke to reduce tunnel count and traffic.....or keep it as a hub and disable the multi-uplink with WAN2 tunnels only in a failover scenario. ... View more