Wireless Access

last person joined: an hour ago 

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

Controller discovery via DHCP or DNS

This thread has been viewed 2 times
  • 1.  Controller discovery via DHCP or DNS

    Posted May 23, 2012 03:58 PM

    I have controllers in California and New York that are configured in a master local topology and the AP

    s are able to locate the master via a DNS lookup. I'm now building a master controller for EMEA where I use the same DNS domain so I want to provide controller info via DHCP instead of DNS.

     

    I've configured options 43 and 60 with their appropriate values but the AP's are still registering to the master in California. How can I force the EMEA AP's to register to the controller provided by DHCP and ignore the DNS name?



  • 2.  RE: Controller discovery via DHCP or DNS

    Posted May 23, 2012 08:30 PM

    I've now changed the domain suffix so aruba-master is no longer resolvable so the AP's won't reach the California controller but they still aren't showing up on the in-region master. I've set up the following in DHCP

     

    Option 43 = <IP of the controller VLAN interface>

    Option 60 = ArubaAP

     

    Is there anything else needed beyond the normal network, mask, and gateway?



  • 3.  RE: Controller discovery via DHCP or DNS

    Posted May 23, 2012 09:14 PM
      |   view attached

    What type of dhcp server are you using?  Here are the instructions for Microsoft's DHCP server.

    Attachment(s)