Wireless Access

last person joined: 15 hours ago 

Access network design for branch, remote, outdoor, and campus locations with HPE Aruba Networking access points and mobility controllers.
Back to discussions
Expand all | Collapse all

Controller and DHCP

This thread has been viewed 8 times

  • 1.  Controller and DHCP

    Posted Aug 22, 2019 11:53 AM

    Currently, we have one subnet that our controller uses to hand out IP addresses to clients.  We would like to have 2 subnets (factsaff and students) and the question is should we allow the controller to be DHCP for clients or should we use Windows server DHCP for this?  Total devices will be less than 5,000.  Pros and Cons of both?

     

    Secondly, if we do use controller for DHCP, how do we configure facstaff to get one pool and students to get the other?

     



  • 2.  RE: Controller and DHCP

    Posted Aug 22, 2019 01:18 PM

    Hi,

    According to your scnario, it better to use a windows DHCP server. Then you can use the same system for other systems as well.  if you use internal DHCP server you could able reduce to DHCP issue latency. But Check whether you Controller utilization (CPU and RAM) 

     

    Create separate DHCP pools in internal DHCP Server and mention DHCP VLAN id when creating SSID.

    if you use single SSID for both you can use dynamic VLAN assignment 

    DCHP Pool :

    https://community.arubanetworks.com/t5/Controller-Based-WLANs/How-to-configure-a-DHCP-server-on-the-Aruba-controller/ta-p/185894

     

     



  • 3.  RE: Controller and DHCP

    Posted Aug 22, 2019 01:59 PM

    Dinusha - thanks for the response.


    * So you are suggesting use controller as DHCP server and set up two Pools - one for facstaff and one for student?

    * These two new pools addresses should conincide with a VLAN being used on the network?

    * Then under role enter the VLAN to be used for each FacStaff/Student?




  • 4.  RE: Controller and DHCP

    EMPLOYEE
    Posted Aug 22, 2019 02:11 PM
    dmattox@millsaps.edu wrote:

    Currently, we have one subnet that our controller uses to hand out IP addresses to clients.  We would like to have 2 subnets (factsaff and students) and the question is should we allow the controller to be DHCP for clients or should we use Windows server DHCP for this?  Total devices will be less than 5,000.  Pros and Cons of both?

     

    Secondly, if we do use controller for DHCP, how do we configure facstaff to get one pool and students to get the other?

     

    How many controllers do you have?

    How many access points do you have?

    How many SSIDs do you have?

    Do those SSIDs all share the same VLAN or do they have different VLANS?



  • 5.  RE: Controller and DHCP

    Posted Aug 22, 2019 02:13 PM
    * One controller

    * Approx. 400

    * 1 we will be using for this scenario

    * Same now but want to change to two


  • 6.  RE: Controller and DHCP

    EMPLOYEE
    Posted Aug 22, 2019 02:21 PM

    Is your SSID a Captive Portal SSID?



  • 7.  RE: Controller and DHCP

    Posted Aug 22, 2019 02:28 PM

    No - WPA-2 Enterprise using Active Directory and Radius




  • 8.  RE: Controller and DHCP

    EMPLOYEE
    Posted Aug 22, 2019 02:48 PM

    Okay.

     

    It is much better to use an external dhcp server, because your administrators already know how to troubleshoot dhcp using that interface (I am assuming).  In addition, if you grow beyond a single controller, it will be easier to extend the dhcp capability with an external server.

     

    For your existing SSID, as long as your users in AD are in groups, you can use your radius server to place wireless users in a VLAN based on their AD group.