I can also confirm that the issue is solved. THX ... View more

Happiest Birthday one of the greatest communities !!  ... View more

On regular MS switches all the possible VLAN numbers are created automatically (1 - 1001, 1006-4094).  So you can just use the VLANs on your ports.  This however can be seen as a waste of TCAM space. On a Catalyst switch the TCAM allowed for VLAN definitions is smaller on C9300 and C9200 switches.  This is why by default the Catalyst switches create vlans 1-1000 (and now 1-995).  If you run IOS-XE native you can actually see the VLANs that are created by using the Cloud CLI. However if you want to use VLAN's above the 1000 number you should use the VLAN database feature @Slayton already explained.  In fact if you can always use the VLAN database and only create the VLANs you actually need.  Then you are sure to not run out of space if you like to put your management SVI in VLAN 2002 like I do 😉 ... View more

Happy Birthday Meraki Community...outstanding 8 years! ✨ ... View more

Just be aware there's a difference between the CS and IOS-XE Native versions of the firmware with how static addressing is handled.   Starting with 17.15 firmware, all statically assigned addresses are done with the Layer 3 interfaces modules. I say this because I was going to statically assign address to my Catalyst stacks in Meraki, but then found out you're enabling L3 routing, and I don't want my switches to be able to perform routing for connected clients.  I'm waiting for VRF support coming later and hoping* this might bring some kind of management VRF support.  https://documentation.meraki.com/MS/Cloud-Native_IOS_XE/Cloud-Native_IOS_XE_Overview#Changes_in_Behavior ... View more