@d0ugmac1 

Sorry for the delay in responding.

The router is an ER8411. I am using an OC300 as the controller.

I assigned VLANIDs with some gaps between them so that I can add VLANs between other VLANs in a logical order. Our use case is still new to our organization, so we make changes on a fairly regular basis, and my setup for the network was far from a perfect plan that survived first contact with reality, so my thought process has mostly been around trying to make it easier for future me to read and understand what I've already done.

I did in fact cycle power to the whole network in between changes. I do this by scheduling a network reboot in the services section and rebooting all devices on the network at once. This has proven way better at making sure everything reconnects and readopts properly than rebooting each device individually.

My switch ACLs are just a rule to allow the management VLAN to connect to any other VLAN, and my gateway ACLs are just to enforce a whitelist policy on the network while we're on a metered connection to prevent anyone from hardwiring in and bypassing the user account portal I have setup, since I can't practically prevent physical access to all of my switches. It's on my to-do list.

Traffic is isolated to different WANs by setting Policy Routing rules under the Transmission tab. Each WAN has the networks that are able to utilize it, with fail over disabled on most of them. I can get down into the details of it, but I'm not sure what that would have to do with DHCP not working based on a change in the VLAN ID.

  @d0ugmac1 It's type Interface. The only thing I change between it working and not working is changing the VLANID in the LAN configuration page from anything else to 2. All of the switches and APs on the network are controlled by the OC300. All of the profiles for all of the switch ports are left as "All". All of the ACL rules and policy routing are done by network or SSID, so the VLANID isn't called out specifically anywhere that I'd need to change it.