You can create a policy object with all the source subnets that has to be blocked and update it in the source section of this firewall rules. That will look nice and clean.    It looks good to me. ... View more

Go through this online course , this will be definitely helpful.   Online CMNA - Cisco Meraki Network Associate training module.   https://learning.meraki.net/#/curricula/4d66abb3-e850-49a9-afdf-3493921c2a07 ... View more

May be use the Meraki group policy in this case to block the vlan to vlan communication.   1. Create a group policy . Network wide - > Group policy. Mention the vlans that has to be allowed or blocked. You can also configure custom policies settings like IPS/IDS , AMP, Content filtering, L7 firewalls for this vlan using this group policy option.           2. Add the group policy to your Vlan to restrict the traffic.     This will block the inter vlan communication as desired.   ... View more

We don't the option in Meraki Dashboard. May be Meraki support can give you the uptime of the devices. ... View more

Thanks for sharing this.   We were working on doing a POC to build and test automatic failover of vMX in Azure. We took help from both Meraki and Azure support to get this automated but we were not able to do it due to lack of much documentation.    We will modify your script and give a try.     ... View more

Its a limitation of using IKEv1.  IKEv1 allows only one SA at a tunnel, secondary SA will not be formed until the primary is deleted. Use IKEv2 to fix the issue. It allows multiple SA at a tunnel and the traffic flows seamlessly.   Another Temporary workaround is it use higher prefix on the Meraki.  Instead of allowing various 10.20 segment , configure one static route with 10.20.0.0/16 and enable it on VPN.   ... View more