Wireless Access

 View Only
last person joined: 2 days ago 

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

Differents priorities en controller teaming 760

This thread has been viewed 0 times
  • 1.  Differents priorities en controller teaming 760

    Posted Dec 04, 2015 04:11 PM

    Anybody can aswering this How can change the priority of controller msm760 if they are in teaming, specially to help AP 430 to discover the controller with the hightes priority.

     

     


    #teaming
    #teaming760
    #priorityteaming
    #discoveryteaming
    #760


  • 2.  RE: Differents priorities en controller teaming 760

    Posted Dec 07, 2015 08:09 AM

    Hi.

    Controller >> Management > Device Discovery page.



  • 3.  RE: Differents priorities en controller teaming 760

    Posted Dec 07, 2015 05:21 PM

    I appreciate your help johnk3r 



  • 4.  RE: Differents priorities en controller teaming 760

    Posted Dec 16, 2015 07:24 PM
    You're right.

    I not found any information in the manual about it. But I think how they are grouped, not have the possibility of setting the highest priority.


  • 5.  RE: Differents priorities en controller teaming 760

    Posted Jan 07, 2016 03:51 PM

    Thank you so much for your time...!!



  • 6.  RE: Differents priorities en controller teaming 760

    Posted Jan 11, 2016 07:51 PM

    You cant have priority configured when in Teaming.  But if you are interested to have certain APs managed by specific controller out of the team, then either static provisioning or using DHCP option 43 based on the subnet will be the other way to manually force APs to sync with specific controller.



  • 7.  RE: Differents priorities en controller teaming 760

    Posted Jan 12, 2016 09:52 AM

    Adding a bit to Ram's.

    When provisioned for L3 discovery, the APs will always try to connect to the controllers in the provisioning order. For example you provision APs in group A to associate with manager and APs in group B to associate with member, you'd configure the provisioning for group A in order

    10.0.0.1

    10.0.0.2

    For group B you'd configure

    10.0.0.2

    10.0.0.1

     

    Please note that even when configured this way, the APs may in certain circumstances end up managed by the "wrong" controller. An example; an AP in group A is coming up but there's a disruption in the connection towards the manager but the member responds, the AP will associate with the member. Once connection to manager is restored, it will not migrate to the manager. However which controller is managing the APs seldom matters.