Controller Based WLANs

What is the max number of address that can be assign by local address pool (L2TP) and how to manage them on controller?

Environment :  In case of any typical environment like configuring RAP, VIA or any VPN clients connecting to controller.

 

  • There is no hard limit but you should better to avoid the .0 and .255 addresses and create multiple local pools.  The reason is that some software/OS may be very upset about these addresses.

  • Pool assignment from role would always trying to taken from the named address pool for “inner IP” address assignment.  If the pool has exhausted, it would automatically overflow to other pools (no control over which pool would be picked up though).

  • An address is taken from the pool when the IPCP (from the PPP) over L2TP/IPSec or PPTP or the IP address to X-auth clients.  When the associated PPP (over L2TP/IPSec or PPTP) session is terminated or the X-auth IPSec SA’s are expired without renew or due to DPD, this address would be re-inserted back to the pool.

  • The address is also picked from the next available and the “returned” address is added as the last “available”.

  • VIA is similar to any other VPN clients in term of “connectivity”, of course it also pulls the configuration from controller for other features.

 

Version history
Revision #:
1 of 1
Last update:
‎07-01-2014 04:48 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.