Cloud Managed Networks

Hello,

I'm trying to an override on a named VLAN in Central CNX.  The VLAN at the global level is for a named VLAN called FCPD100-301 and has only VLAN 301 in it.  At the device level I want to override this with a vlan pool of 301-332.  But I get the error shown below.  What odd is named VLAN NLAW101-2101 has nothing at all to do with the FCPD100 vlans.  I get different mix matched errors with other named vlans if I try this on other named vlan overrides.  Like a corrupted backend database of something.

Any tips?  Anyone done a named vlan override before? 

I just tried it for you and worked fine 

------------------------------
If my post was useful accept solution and/or give kudos.
Any opinions expressed here are solely my own and not necessarily that of HPE or Aruba.
------------------------------

Thanks for testing it.  I guess I definitely have an issue then.  I will open a case.   I need this to work really bad. 

Original Message:
Sent: Jul 23, 2026 02:14 AM
From: AP-e172d8
Subject: Central CNX VLAN Pools

I just tried it for you and worked fine 

------------------------------
If my post was useful accept solution and/or give kudos.
Any opinions expressed here are solely my own and not necessarily that of HPE or Aruba.
------------------------------

I have a case open but thought I would add the below detail about why I want to do this.


The ultimate goal is to be able to have WLANs and wired roles use a named vlan.  In the named vlan at the primary cluster it may reference a single vlan like 301 or a range like 301-308 which is sized for that location but on the backup cluster we need to be sized for any failure of a primary cluster.  So it has much larger vlan pools meaning I need to overwrite the vlan name on the backup cluster to something like 301-332.

I also tried creating a new vlan and named vlan that is not associated to anything anywhere.  I push it globally and override it at the device level and I get the same error message.

Original Message:
Sent: Jul 23, 2026 02:14 AM
From: AP-e172d8
Subject: Central CNX VLAN Pools

I just tried it for you and worked fine 

------------------------------
If my post was useful accept solution and/or give kudos.
Any opinions expressed here are solely my own and not necessarily that of HPE or Aruba.
------------------------------

If I had to make some assumptions. I question if you are running into issues due to tunneled WLAN and auto clustering options set at a hierarchy level. I am not sure exactly for the reasons on the need for additional clusters to re-home tunneled WLAN's unless you were implelmenting a duel datacenter design where AP's would be at the branches and phone home to multiple datacenters. This would also extend the WLAN vlans back to datacenter vs operate locally at the site. 

When I think of the term tunnel with cluster. I would generally think a single cluster at the local site if 2 gateways is justifed. Since I do not have full visibility of the intentions and design, its hard to comment. 

Maybe considering having all of the vlans on both primary and secondary cluster so they are in sync would be a possible next step. Its probably a good idea to get ERT involved to help validate the intentions and ensure everything is fully supported. 

From my understanding of how the hierarchy works. When you create a local profile is actually another db table that the config is cloned / copied from. 

I have tried to use alias where I can. This way I am not using local configs where I want to adjust 1 setting.

Original Message:
Sent: Jul 25, 2026 11:58 AM
From: AS-e049ea
Subject: Central CNX VLAN Pools

I have a case open but thought I would add the below detail about why I want to do this.


The ultimate goal is to be able to have WLANs and wired roles use a named vlan.  In the named vlan at the primary cluster it may reference a single vlan like 301 or a range like 301-308 which is sized for that location but on the backup cluster we need to be sized for any failure of a primary cluster.  So it has much larger vlan pools meaning I need to overwrite the vlan name on the backup cluster to something like 301-332.

I also tried creating a new vlan and named vlan that is not associated to anything anywhere.  I push it globally and override it at the device level and I get the same error message.

Original Message:
Sent: Jul 23, 2026 02:14 AM
From: AP-e172d8
Subject: Central CNX VLAN Pools

I just tried it for you and worked fine 

------------------------------
If my post was useful accept solution and/or give kudos.
Any opinions expressed here are solely my own and not necessarily that of HPE or Aruba.
------------------------------

The message states the profile is applied at the site level. You are trying to update it at the device level. I would suggest using device groups if you want to override at the device level. Otherwise go back to the site level and update it. 

https://arubanetworking.hpe.com/techdocs/new-central/content/cfg/mul-lvl-hirchy/multi-lvl-heirch.htm?Highlight=hierarchy

Consideration should be made to determine the best way to overwrite settings in the hierarchy design that fits your needs. In our case we use site collections to apply the general configs, and then sites can override the site collections. 

Thanks I tried at the site and device levels.  Neither worked.  Going to open a support case.

Original Message:
Sent: Jul 23, 2026 08:16 AM
From: JK-90898a
Subject: Central CNX VLAN Pools

The message states the profile is applied at the site level. You are trying to update it at the device level. I would suggest using device groups if you want to override at the device level. Otherwise go back to the site level and update it. 

https://arubanetworking.hpe.com/techdocs/new-central/content/cfg/mul-lvl-hirchy/multi-lvl-heirch.htm?Highlight=hierarchy

Consideration should be made to determine the best way to overwrite settings in the hierarchy design that fits your needs. In our case we use site collections to apply the general configs, and then sites can override the site collections.