Vlan Database Catalyst 9300

[IgorRoizen]

Hey to all,

I configured the VLAN database and groups and assigned them to the ports. However, ports with VLAN IDs over 1000 are not being activated - it only works if I specifically configure active VLANs.
Does anyone know why this is happening?
Could it be because "all" includes reserved VLANs?

[rwiesmann]

well as I see it...it is just limited to 1000 Vlans. See the following documentation in the section "VLAN Database"

https://documentation.meraki.com/General_Administration/Cross-Platform_Content/VLAN_Profiles#VLAN_Database

hope this helps

roger

[IgorRoizen]

Hey, for enable vlans over 1000 under Organization > Early Access, I have enabled the VLAN Database feature. You can enable it as well. Then, under Network-wide > VLAN Profiles, you can configure VLANs, groups, and the active VLANs that need to be set up.

[ww^]

You can't use more then 1000 active vlans. You can use vlans numbers over the 1000.

You cant use the reserved VLANs 1002-1005 and 4093-4094

When using "all" it applies the configured group to that switchport. Did you configure the created profile to the switch at "profile assingment"?

I didn't experience any issues

[IgorRoizen]

The issue occurs when, under the VLAN profile, I leave the "VLAN active" setting at the default value ("All"). Only when I explicitly configure specific VLANs do I see that VLANs over 1000 become active.

[ww^]

I never tryed that. But i think that should match what vlans you want to use, else it would start using "all" but limited to the first 1000

This is what the documentations says:

Active VLANs

Active VLANs are those that are actually instantiated on the switch, in the case of Catalyst switches. The Active VLAN list should match the required VLANs in order for the switch to function properly. The VLAN database function will attempt to prevent required VLANs from being removed from the Active VLANs list but cannot prevent all misconfigurations. When a misconfiguration happens, such as a switch management VLAN (a required VLAN) being removed from an Active VLAN list, the VLAN database will generate an alert on the details page for the affected switch(es).

[joey.debra]

When on a network you configure a limited active VLAN list you will be able to see those VLANs being defined on the switch itself by using the CLI. "show vlan brief"

So it is important that you include all the necessary VLANs in the comma separated list in that Active VLAN list. And after that on each switchport functioning as a trunk you can use the allow all like you could on regular MS switches.