Add a Named VLAN Not option

[Jujubee]

I am very new to Meraki (fine with CLI on Cisco Switches).  I have inherited a switched network.  EVERYTHING is on VLAN 1 (OMG).  I went to Network->VLAN Profiles and Created a new profile.  However, inside that profile, the "Add Named VLAN" is missing?  What do I need to do to create new profiles with named VLANs?  I can create them in the Default VLAN profile only.

[ww]

Organization >early accces.

The enable vlan profiles

[Jujubee]

Thanks for the prompt reply.  Is there no other way to create VLANs?  I feel like an idot with the GUI.  I can do this in my sleep on CLI.

[ww]

There is. You just assign any vlan to the port(s). You dont need to create or name vlans like catalyst

[DarrenOC]

What’s the requirement here?  Do you need L2 or L3? What models of switches are you working with?  I get that you’re familiar with Cisco and CLI but venting here isn’t helping anyone.  The responses you receive are from people like you - engineers that give up their free time to help others.

[Jujubee]

I appreciate everyone's assistance.  I am just confused with the new GUI.  It is not intuitive to me.  I hope it will become easier as time goes by.

Can you explain something to me?  What is the point of VLAN Profiles?  If all Named VLANs get created in the default profile and then propogate to the other profiles, why bother with Profiles at all?  This confuses me.

[RWelch · Accepted solution]

As @ww indicated, you can just assign by VLAN without having to implement VLAN profiles.

To help try to answer your question:

Overview

VLAN Profiles is a new feature spanning MR and MS as a means to provide both dynamic, RADIUS based assignment of VLANs to devices/users/endpoints based on an alphanumeric name, but also as a means to abstract VLAN IDs from certain elements in Dashboard using relatable terminology instead of numbers. 

VLAN profiles can work along with 802.1X/MAB authentication to assign authenticated users and devices to specific VLANs according to a VLAN name rather than an integer. This can reduce the configuration and management burden on the RADIUS server by allowing fewer authentication policies to be used for multiple sites which may use different VLAN IDs for the same functional group of users and devices.

For example, sites A and B may both have a "guest" VLAN, which is VLAN ID 100 at site A but ID 99 at site B. Without VLAN profiles, a separate RADIUS policy or rule would normally be created on the RADIUS server for each of site A and site B. With VLAN profiles, a single policy can be created on the RADIUS server which sends the VLAN name "guest" to the switches at each site, which then can map the "guest" VLAN name to the appropriate VLAN ID. 

[Jujubee]

Awesome explanation.  Thank you. 

[Jujubee]

I enabled it but still no button to "Add Named VLAN" in new Profile.

[RWelch]

Named VLANs in MS Configurations 

[RWelch]

VLAN Profiles 

[Jujubee]

Well, that is not very intuitive.  What is the point of having VLAN profiles then if all the named vlans get propogated to all of the profiles?

[RWelch]

Give your feedback (previously Make a Wish) provides you a way (means) to give feedback if you haven't yet used it.