Have you ever encountered this error?    Combined count of Allowed VLANs and Native VLAN cannot exceed 1000 VLANs   If you have, you probably know how frustrating it is to deal with. This is a side-effect of Zero-Touch Provisioning (ZTP). Catalyst switches have to actually create VLAN objects in order for traffic to pass through those VLANs, and when you open a brand new Cloud-Managed C9300-M switch, we’ve already created VLANs from 1 to 1000 on it to increase the chances that switch will find a way to reach the Dashboard as soon as you plug it in. That’s helpful!    Once the switch is online though, all of those VLANs are still there, and you probably aren’t using 1000 VLANs. Guess how many VLANs a C9300 can run at a time? That’s right – 1000!    So when you go to configure any VLAN above 1000 on your switch, the Meraki Dashboard “helpfully” points out that you’re already maxed out and need to remove some of those unused VLANs first.     We could’ve made this easier to understand – heck, we could have made it easier to prevent – so that’s what we’ve done by bringing VLAN database management to the Dashboard.        How does it work?  VLAN database management allows you to...    ✅ Easily remove unused VLANs from one or many Catalyst switches at once    ✅ Ensure VLAN DB consistency with VLAN Profiles, making sure the VLANs that you do need are correctly provisioned on switches, at scale    ✅ Configure trunk ports to allow all VLANs, the same way MS switches do, while still only having the active VLANs created on the switch.     To try VLAN database management, visit the Organization tab in dashboard and navigate to the Early Access page, then find VLAN Database. Additionally, you can read more about how this feature works here. ... View more