I have five VLANs in my network. 1 is management, 10 is for a non-metered connection, 20 and 30 are for metered connections. I also have a fifth VLAN that is isolated from the internet, so I don't need to use any kind of AAA on it. The non-metered connection isn't always available, so I need to regulate how much internet everyone (around 500 people) use when we are on the metered connection. Omada's Local User accounts don't differentiate between internet data and data to the controller, so my admins need to be authenticated on the metered connection if I don't have a LAN Only network setup. Also, there's plenty of projects people have that don't use internet and can be on this LAN Only network, again without affecting any AAA.

That fifth VLAN doesn't assign IP addresses when I set it to VLAN 2. This is the one I'd like to set, because it just makes logical sense to me for the non-internet networks to be together, but when I do, everyone gets fall back IPs in the 169.254.XXX.XXX range on that network. When I set it to 21, it works fine. The only setting in the LAN configuration page that I change is the VLANID. Nothing else gets changed. IP range stays the same, DHCP stays the same, LAN interfaces stay the same, and I don't change any settings on any ports.

The only thing I can think of is maybe I need to restart the network hardware to refresh the port configuration profiles, but I've never had to do that in the past when changing VLANs. Request any ideas as to why this might be happening.