Controller-less WLANs

How to configure static subnet allocation at branches IAP-VPN deployment?

This article explains a new feature introduced in IAP OS version 6.2.1.0-3.3.0.0 where we can assign static subnets to the branch offices in an IAP-VPN deployment for Distributed DHCP allocations. The Aruba Controller terminating the IAP VPN should be running on OS version 6.3.0.0 or above. Controllers running any older version do not support this enhancement.

 

 Let us consider a scenario to understand the need for static subnet allocation -

We already have a branch that is up and the devices have received IP address from the global pool and there are a few new branches that are coming up. In case we want the existing branch to retain the same old subnet, we can configure that branch subnet as static subnet while the new branches will be assigned different subnets automatically using BID (Branch ID) allocation algorithm. Also, we can configure another Distributed DHCP scope and allocate static subnets to the new branches as well.

 

Environment : This article applies to all the IAPs running a minimum OS version of 6.2.1.0-3.3.0.0 and Aruba Controller running a minimum OS version of 6.3.0.0.

 

 

  1. Navigate to “more” and click “DHCP Server”.

rtaImage (3).png

 

2. Create a new Distributed DHCP scope and mentioned the static subnet as shown below.

 

rtaImage (4).png

 

Please note, we can create 4 discontinuous IP address ranges for static subnet allocation by clicking the + sign after the IP address range.

 

 

 

Version History
Revision #:
1 of 1
Last update:
‎07-04-2014 04:11 PM
Updated by:
 
Labels (1)
Contributors
Search Airheads
Showing results for 
Search instead for 
Did you mean: 
Is this a frequent problem?

Request an official Aruba knowledge base article to be written by our experts.