unable to add static routes to networks w different / per-VLAN Next hop IPs

[MrHardwick]

We are currently running Meraki side-by-side with another vendor's solution.  Networks in another data center are accessible by routing it to a next hop on each VLAN.  For example in the screenshot the 160 Main VLAN below we can reach those other networks via 10.10.51.1 and in the 163 Training WiFi VLAN we can reach those other networks via 172.27.51.2 just fine.

Here are some static routes entered in Addressing & VLANs currently.

This works fine for hosts on VLAN 160 but does not work for hosts on other VLANs.  If I change the Next hop IP for these three networks to be the gateway required for example for VLAN 163 (172.27.51.2) that VLAN can reach the remote network, but the other VLANs cannot. 

What I would hope to see would be ability to set a per-VLAN static route with its own Next hop IP.  Any workarounds or someplace I am not looking?

I did find in the API a this endpoint https://developer.cisco.com/meraki/api-v1/create-network-appliance-static-route/ which allows you to specify a VLAN when creating a static route but when doing so it returns an error

[Mloraditch]

It sounds like the device on the other end doesn't know to route back.

The meraki can route traffic to any device it can reach from it's locally defined interfaces.

But if you are routing Subnet A to 10.10.51.1 and Subnet B to 172.28.51.1 and Subnet B can't reach VLAN 160, that's because 172.28.51.1 doesn't have a route back (or if it's a firewall there may be firewall rules in play).

[GIdenJoe]

The MX at this time does not support ECMP so you can only enter 1 route for each destination.
However in your example you might run into an issue where you try to add an aggregated subnet 10.10.0.0/16 for where you already have a local VLAN 10.10.51.0/24 which is more specific.

Normally you can have routes to less specific subnets and routes via several local subnets.
But I would try to add a more specific route than the 10.10.0.0/16 first or remove the 10.10.51.0/24 subnets just as a test and see if you can add the aggregate route then.  Usually you can also see the error in a red banner on the top of the dashboard page.  But sometimes these can be hidden and show themselves when you push via API,