A named VLAN is an indirection layer: profiles reference the name, and the name resolves to a VLAN ID per scope. That's why it looks like one name for multiple VLANs, it's one mapping per scope, not several at once. The classic use: your WLAN or port profile says put this traffic in GUEST, headquarters resolves GUEST to 120, a branch resolves it to 20, and you never fork the profile.
For your setup, where the core and the 2540s share the same IDs, you don't need them at all. Plain VLAN profiles with real IDs are simpler and easier to read. Named VLANs earn their keep when IDs vary across sites and you want one profile to rule them all.
@Worldcom Exchange, Inc.
Original Message:
Sent: Aug 19, 2026 10:54 AM
From: WK-1c235c
Subject: Why is New Central Preventing me from Setting VLANs on AOS-S Switches?
Some links that may help you learn the new hierarchy:
- https://arubanetworking.hpe.com/techdocs/VSG/docs/002-central/central-020-config-model/ - Hierarchy explained
- https://theedge.ext.hpe.com/vsg/docs/002-central/central-030-central-config-example/ - Example
- https://arubanetworking.hpe.com/techdocs/VSG/docs/020-campus-deploy/campus-small-deploy-300/ - Full section showing how to build a small campus
- https://arubanetworking.hpe.com/techdocs/hpe-central/content/GUID-19B47A7E-5D0A-4A2C-8540-733B0A470D75.html - Tech Docs, Quick Start Guides here can be useful
VLAN Profile
The actual VLAN. This is the real Layer 2/Layer 3 object that gets pushed to a device, defined by VLAN ID plus its full configuration: switch parameters (IGMP/MLD snooping, DHCP snooping, ARP inspection), SVI/L3 settings (IP address, Active Gateway or VRRP, DHCP relay), and routing behavior. When you assign a VLAN Profile to a scope and device function, that VLAN literally exists on the device.
Named VLAN
Not a VLAN itself, just a name-to-ID mapping. It associates a human-readable name with a VLAN ID so that other things (WLAN profiles, wired port profiles, VLAN assignment rules, role derivation, RADIUS) can reference the name instead of a hardcoded number.
In the VSG example above you can see how we use the VLAN profile on the CX and Named VLAN profile on the APs
------------------------------
WillKerr
------------------------------
Original Message:
Sent: Aug 19, 2026 09:39 AM
From: DS-FkB358
Subject: Why is New Central Preventing me from Setting VLANs on AOS-S Switches?
Thank you, this helped a lot.
Last question, what are "Named VLANs" for actually? i do know that regular vlans can have a name, but those look like its one name for Multiple VLANs? why?
Original Message:
Sent: Aug 18, 2026 08:36 PM
From: DB86
Subject: Why is New Central Preventing me from Setting VLANs on AOS-S Switches?
You're fighting the profile model, not the switches. In New Central a VLAN is a profile object, and that "already exists" message means exactly what it says: the VLAN IDs your core uses are already defined as Library profiles, and Central won't let you create a duplicate definition at another scope. It doesn't need to. The fix is assign, not recreate: in the Profiles view go to Library, VLANs and Networks, hover the VLAN, hit Assign, pick the device function for your access switches, and add the scope, the site or the 2540s themselves. One definition assigned everywhere it belongs is the intended pattern, and the docs' own recommendation for VLANs shared across a site is exactly that, Library plus a Global assignment covering all device functions.
On the naming confusion: the Name field on a VLAN profile is just a switch attribute riding along with the ID, and aliases only exist to override IPs on L3 VLANs, which is why the AOS-S side shows none and why you don't need them for plain L2. Assign the existing profiles to the 2540 scope and the core and access will line up.
------------------------------
Dustin Burns
@Worldcom Exchange, Inc.
If my post was useful accept solution and/or give kudos
------------------------------