Hello everyone
I have a particular setup I want to discuss/get input from the community on. I have a customer in the works of moving from a VPN infrastructure to use Aruba and RAP-5. The customer have many offices geographically spread across out country. For the moment it's about 40-50 very small offices.
We now have a RAP-5 in place at all the offices, running fine with WLAN and using the Ethernet ports for printers etc.
The customer has insisted on having a separate IP subnet for WLAN and cable on each site. This totals a lot of VLAN and also wants to use Aruba as DHCP for these VLANs. The reason for using Aruba as DHCP is that the customer don't have a good infrastructure behind at the moment, but moving to a full AD, RADIUS etc.
They also want to have separate VLAN for WLAN/cable for each site, for easier troubleshooting. If a customer with the given IP is having problems they will instantly know which location the problem is at. I have told them that this is not an optimal solution, but VLAN wise and DHCP wise.
That have 2 3x00 controllers which shall be in a master-standby setup when things are up and running. But because of the sheer number of VLANs and especially DHCP scopes, I see a problem when running controllers in VRRP.
The DHCP scopes with 254 hosts is clearly an overkill at each location, but for the standby to work correctly and not having 2 DHCP servers on the same VLAN, what is the recommended setup for this.
If the master fails, the standby should have the same VLAN and same scope so that users can reach their local printer etc.
I know this is not the ideal setup and I have made that clear to the customer, but as we know the customer always is correct :D
I was thinking about splitting the scope in 2, putting the 2 parts on each controller.
The real problem is that I might need to add one VRRP instance for each DHCP scope to have a VRRP IP for each DHCP to use as gateway.
Hope anyone can brainstorm a bit with me to setup this in a somewhat sensible way.
Roar Fossen