Environment : This article applies to all the IAPs running OS version 18.104.22.168-22.214.171.124 and above.
Clients do not get an IP address even when a valid network range and client count is configured on the IAP.
Network range not defined keeping in mind the logic used by the IAP to calculate the starting IP address for the clients.
Configuring a correct network range resolves the problem.
Let us try to understand this with an example:
Suppose the IP-range is 10.10.10.5 – 10.10.10.30 and the client count configured on the IAP is 20. In this case we will not get any valid subnet for the branch.
This is because of the following logic that the IAP uses to calculate the starting ip address for a client using Distributed,L2:
Start IP for the branch subnet for Distributed,L2 should be a multiple of client count. Since 10.10.10.20 is the lowest IP address that is multiple of 2 0(client-count) in that given IP-range, the branch should be getting the subnet range as 10.10.10.20 – 10.10.10.40.
If we make the network range to 10.10.10.5 – 10.10.10.45, we will get a valid branch subnet for 20 clients as 10.10.10.20 – 10.10.10.40.