Both mx need to reach the internet. So both need to connect the active router. It would be better to have two separed routers (not vrrp) with both own ip space. And then connect both mx to both routers
... View more
The api doesnt configure the mx itself. It configures the meraki dashboard (cloud) config. That will be pushed to the mx using the meraki management tunnel Or are you accessing/configuring the meraki dashboard api from behind that same mx?
... View more
If i understand correctly you building a tunnel from a lan device to a sp through your mx? Maybe it works better if you add the tunnel destination to the flow pref to go out wan1 or wan2 https://documentation.meraki.com/MX/Firewall_and_Traffic_Shaping/MX_Load_Balancing_and_Flow_Preferences#Internet_Traffic
... View more
You can choose a management vlan at Configure > Switch Settings When it matches your switch configered management vlan the warning will go away
... View more
Autovpn on a lan interface? Due to an MX 18.2 regression, MX75, MX85, MX95, MX105, MX250, and MX450 appliances will fail to form AutoVPN tunnels with other MX appliances via their LAN interfaces.
... View more
Sd internet works for traffic outside the tunnel. If you dont use a default route in your tunnel you dont need vpn exclusions If you do have a default route in the tunnel you can use vpn exclusions
... View more
If you get problems like with roaming or sticky clients you can disable the ax features. You could for example have clients prefer ax AP instead of roaming to the better ac AP.
... View more
Mx autovpn doesn't do layer2. Maybe if you connect all devices using client vpn setup. Or build gre tunnels from your devices ( not sure what devices you run) to a vpn server you host in your server subnet
... View more
You could get them using this page and then send(post) them to the other org. Or try starting with postman/tutorial that should be doable when starting with api's https://developer.cisco.com/meraki/api-v1/get-organization-policy-objects/ https://developer.cisco.com/meraki/build/meraki-postman-collection-getting-started/
... View more
Are the hub subnets in the spoke route table? Are the routes on the sub set to participate in vpn? Any vpn firewall rules that prevent this?
... View more
I have had the mx allow dhcp config options but they would not work. Then support told me not al options are supported on mx. It would be good to have a list of which work on what platform
... View more
You cant. The ms does not have source/policy based routing. Maybe you could move some layer3 vlans to one mx, and trunk them on layer2 to the switch
... View more
I think you mixing up bands and rates. The mr44 has 2x2 on the 2.4ghz And 4x4 on the 5ghz The 2.4 can only do max 287Mbps using a 20mhz channel on the 2.4ghz band https://mcsindex.com/
... View more
I think bouncing the port should work. Are you working with support on this? The document also talks about enabling radius monitoring that support can enable. https://documentation.meraki.com/MS/Access_Control/MS_Switch_Access_Policies_(802.1X)#Other_RADIUS_Features
... View more
Like @alemabrahao already said. Asuming you working on the mx route not the switch. You need to to point the route for subnet 192.168.132.0/24 to the next hop(switch ip) 192.168.128.2 (or whatever ip you gave the switch)
... View more
