Wireless Access

Hi all, I found some articles that are similar to my issue but not quite what I need.

I need a single SSID and single Clearpass service that would round robin to 3-4 vlans for the sole reason to keep one network from having 1000s of users on it at one time.

In theory in Mobility under interfaces I can create a Vlan that has multiple IDs, then I can use that vlan in my role to point to all of the IDs (picture attached).  

Would that effectively use all of the IDs in that "vlan group" and balance them across?

In the past we have been using AD to assign one of the 4 vlans, breaking that out through Clearpass, then assign the role based on the Clearpass ID to pass to Mobility, but our AD integrator isn't able to complete this. So the vlans are already there- tagged on all of my controllers, and switches, etc, I just need to dynamically assign them when they get back to the controller for their vlan ID.

Sorry if my wording is unclear. Thanks all.

-------------------------------------------

A Named VLAN is basicly a VLAN pool. Yes you can do that but don't recommend it. Its totally fine to have 1 VLAN with 1000 clients (or more) as long you enabled broadcast supspression and Broadcast ARP translate to Unicast.

------------------------------
Marcel Koedijk | MVP Expert 2024 | ACEP | ACMP | ACCP | ACDP | Ekahau ECSE | Not an HPE Employee | Opinions are my own
------------------------------

check this VLAN pooling support note on best practices 

------------------------------
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.
------------------------------

Original Message:
Sent: Oct 28, 2025 01:17 PM
From: mkk
Subject: Wireless (MM) to round robbin vlans for network balancing

A Named VLAN is basicly a VLAN pool. Yes you can do that but don't recommend it. Its totally fine to have 1 VLAN with 1000 clients (or more) as long you enabled broadcast supspression and Broadcast ARP translate to Unicast.

Why it's usually not recommended

 

• Named VLANs (VLAN pools) are mostly intended for segmenting clients dynamically, but they add extra complexity:

 

• DHCP must exist for all VLANs in the pool.

 

• Role and policy management becomes slightly harder.

 

• Some features (like certain firewall or QoS policies) may not work consistently across the pool.

 

If your only goal is to prevent a single VLAN from having too many clients, there's an easier, more reliable approach.

------------------------------
Marcel Koedijk | MVP Expert 2024 | ACEP | ACMP | ACCP | ACDP | Ekahau ECSE | Not an HPE Employee | Opinions are my own
------------------------------