This article explains:1. Need for VLAN Pooling in IAP2. Configuring VLAN Pool in IAP4. What we cannot achieve using VLAN poolingVLAN Pooling is a new feature added in OS version 188.8.131.52_3.2.0. Any version prior to this does not have the VLAN Pooling feature.
In a single IAP cluster, there can be a large number of clients in the same VLAN. This leads to a high level of broadcasts in the same subnet. The solution to this is to partition the network into reasonably-sized subnets and use L3-mobility between those subnets, when clients roam. However, there are various situations, like simple network design considerations, where a large number of clients need to be in the same subnet. VLAN pooling provides a solution in such scenarios. Each client is randomly assigned a VLAN from a pool ofVLANs on the same SSID, thereby automatically partitioning a single broadcast domain of clients into multiple VLANs.VLAN Pooling ensures client gets the same VLAN across all APsin the cluster.NOTE: VLAN Pooling and L3 Mobility cannot be used together. Also, random VLAN assignment algorithm does not ensure even distribution of clients.
Environment : This article applies to all IAPs running OS version 184.108.40.206_3.2.0.
Navigate to New WLAN > VLAN tab > Static > Assign VLAN ID
Client VLAN assignments can be viewed in CLI and in Support UI by checking the AP association table
"Named VLAN" is not supported in Instant. As shown in the above screen shot, we can only list the VLAN ID's.
We can define a vlan pool with a pool name, and assign the pool name in the VLAN 'box', right?
At Aruba, we believe that the most dynamic customer experiences happen at the Edge. Our mission is to deliver innovative solutions that harness data at the Edge to drive powerful business outcomes.
© Copyright 2021 Hewlett Packard Enterprise Development LPAll Rights Reserved.