Manage DHCP on MX Static Routes via Dashboard API

[RvR]

Hello community!

I'm working on a script that manages the DHCP settings on MX Static Routes. The configuration in the dashboard includes many settings:

However, the API endpoints for Appliance Static Routes only include the last two items:

• fixedIpAssignments
• reservedIpRanges

https://developer.cisco.com/meraki/api-v1/update-network-appliance-static-route/

So I'm missing most DHCP settings:

• DHCP handling (Run a DHCP Server/Do not respond to DHCP requests)
• DHCP Lease time
• DNS nameservers and list of custom servers
• DHCP Boot options mode, server and filename
• DHCP options

I've been looking through other appliance API endpoints, but didn't find any that include these settings for Static Routes. The VLANs API endpoints, both for appliance and switches, do include all the DHCP settings, but for MX Static Routes these seem to be missing...?

So my questions are:

1. Is there an API endpoint that allows me to control all DHCP settings for MX Static Routes (like there is for VLANs)?
2. If not, is completing the Static Routes API endpoints with all DHCP settings on the roadmap?

Many thanks!

Ron

[GIdenJoe · Accepted solution]

I have checked and indeed I could not find those settings either.
I also changed a static route to contain a DHCP scope with some other settings and did not get any different output when GET'ting the static route.  Strange oversight.

[NicolasRen]

Hi,

Had the same when I tried to configure source-based static routes on MX, you can't find any request managing theses routes... Some of config seems to be missing or hidden...

[alemabrahao]

Hi,

Unfortunately, there is no Meraki API endpoint that allows full control over all DHCP settings for MX Static Routes, similar to what is available for VLANs.

[RvR]

Thank you all for confirming I didn't overlook any API endpoint, and that I'm not the only one who misses this! How can we get this on the roadmap and solve this omission?

[alemabrahao]

I suggest you submit a feature request to Cisco.

[RvR]

According to our Cisco representative this feature is already on the roadmap... let's hope that this attention to it helps to get it implemented soon 😉