Wireless Access

 View Only
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.
Expand all | Collapse all

AirGroup Domains deployment practices

This thread has been viewed 1 times
  • 1.  AirGroup Domains deployment practices

    Posted Apr 22, 2016 02:48 PM

    There's some nice information about AirGroup domains and clusters, but little on practical deployment cases.  Here's one that others may have.

     

    Multiple controllers, master and some number of locals.

    Same vlans on all controllers, but set of vlans in use (per ap-group/vap) unique to each.

    No AirGroup sharing expected between any two controllers. 

     

    The question is, can I leverage domains (unique domain per controller) to isolate the mDNS queries/responses to a single controller and thereby reduce the overable bonjour traffic?

     

    Does this increase my overall AirGroups limits, or does the fact that all vlans terminate on each controller negate that?

     

    Thanks,

     

     

     

     



  • 2.  RE: AirGroup Domains deployment practices

    EMPLOYEE
    Posted Apr 23, 2016 05:09 AM

    Airgroup domains are a way to allow multiple controllers to share the same airgroup information without having to necessarily trunk all VLANs to all controllers.  You cannot circumvent the platform limits listed here:  http://www.arubanetworks.com/techdocs/ArubaOS_6.4.4.x_WebHelp/Web_Help_Index.htm#ArubaFrameStyles/AirGroup/Best_Practices_Limitations.htm%3FTocPath%3DAirGroup%7C_____1 by configuring domains.

     

    If your controllers do not share VLANS, they will not share any airgroup information.  Typically you only want to present Airgroup devices when your users are near to them.  90% of administrators can accomplish that simply by using Autoassociation:  http://community.arubanetworks.com/t5/Controller-Based-WLANs/How-to-configure-Controller-based-AirGroup-Policies-amp-Auto/ta-p/239934