DHCP Reservations on Network with No VLANs

[Jason-907]

Normally I can do the call:

myvlans = meraki.getvlans(apikey, networkid, suppressprint=False)

And then I can modify DHCP reservations to my heart's content. Today I needed to have my script do this for a small branch office with a flat network. It's small enough that I'm not using VLANs, so my getvlans call is returning ['VLANs are not enabled for this network']

So, is there a workaround? How do I get to the DHCP info for this network? Do I have to enable VLANs to access this information through the API?

Sorry if I've totally missed something that has developed recently. I split my time between firewall, LAN, and server admin. Sometimes I can go for months without touching the meraki API.

[CptnCrnch]

Seems like there are several areas you need VLANs enabled, even if they‘re not needed:

https://community.meraki.com/t5/Developers-APIs/Getting-LAN-Config-via-API-when-VLANs-are-disabled/m...

[PhilipDAth]

This API call lets you turn VLANs on and off.

https://dashboard.meraki.com/api_docs#enable/disable-vlans-for-the-given-network 

[rhbirkelund]

I am in no way experienced in the Meraki API.

However, I've found this.

You can check if vlans are enabled by using this endpoint;

HTTP REQUEST
GET /networks/{networkId}/vlansEnabledState

If that returns true, then go ahead using your  getvlans()-call

If false, you can maybe you can use 

HTTP REQUEST
GET /networks/{networkId}/vlans/{vlanId}

and then return for vlan 1 or 0? I'm not sure if this would work...

[rhbirkelund]

What's returned if you call this?

HTTP REQUEST
GET /networks/{networkId}/appliancePorts

[Charlotte]

The '/networks/{networkId}/appliancePorts' only works if VLANs are enabled. But it doesn't have DHCP information, just says what VLANs are on the MX ports.

[Jason-907]

Thanks guys. I hit the easy button--enabled the VLANs and hoped that didn't break anything. It doesn't seem like it should break anything, but right after I did that our monitoring software stopped being able to ping the device. It was only after digging through the dashboard for a while that we figured out that the change broke the VPN mesh. I had to enable it for VLAN 1.