02-04-2015 04:40 PM
Getting a little farther with configuring our two new 7210 controllers to take traffic. I am now at the point when I need to settle DHCP for wireless clients. ArubaOS 6.4 limits the number of IPv4 addresses it will serve in its DHCP server to 5210 (or something close to that). But, that is insufficient. We have enough subnetworks to exceed that number of addresses.
Our routing scheme is such that the gateway router interface for each of the wireless client VLANs is not either of the controllers, but is an ASA.
So, we've decided to use a dedicated DHCP server. Now, I finally get to the question:
We have redundant controllers, as I said. I don't foresee a problem with adding, for example, the identical IP helper command on the VLAN 403 in each redundant controller. When a client comes up on that subnetwork, one of those two controller VLAN interfaces is going to hear the DHCP request broadcast first, and get an address from the DHCP server. I think the DHCP server will simply ignore the second DHCP request for that host.
At least, this is what I think will happen.
Does anyone here see a potential problem with this configuration?
Solved! Go to Solution.
02-04-2015 04:42 PM
02-04-2015 04:44 PM
If so ,are you using the same segment/VLAN on each controller ?
Lead Mobility Engineer @ Integration Partners
AMFX | ACMX | ACDX | ACCX | CWAP | CWDP | CWNA
02-04-2015 04:51 PM
I've been mulling that over, too. I will only have a single DHCP sever, as well as that single ASA acting as the gateway router for the user VLANs. So, there will already be single points of failure. This configuration is only for guest users, though. However, since there are single points of failure on the way to the internet, perhaps it is probably simpler to put that DHCP forwarding command on that ASA.