topic Differents priorities en controller teaming 760 in M and MSM Series

Differents priorities en controller teaming 760

TAAM — Fri, 04 Dec 2015 21:10:57 GMT

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.

Re: Differents priorities en controller teaming 760

johnk3r — Mon, 07 Dec 2015 13:09:23 GMT

Hi.

Controller >> Management > Device Discovery page.

Re: Differents priorities en controller teaming 760

TAAM — Mon, 07 Dec 2015 22:21:07 GMT

I appreciate your help johnk3r but I can't solve it because my specific scene is that I have two MSM760 in teaming so when the Manager Controller fails my APs go on the second controller and that's the way that teaming could be work the problem is when I recovery the First Controller my APs doesn't change to the first controller they still continue with the second controller I would like my Aps change to the first controller

Re: Differents priorities en controller teaming 760

johnk3r — Thu, 17 Dec 2015 00:24:12 GMT

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.

Re: Differents priorities en controller teaming 760

TAAM — Thu, 07 Jan 2016 20:50:51 GMT

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

Re: Differents priorities en controller teaming 760

RamKrish — Tue, 12 Jan 2016 00:51:17 GMT

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.

Re: Differents priorities en controller teaming 760

Arimo — Tue, 12 Jan 2016 14:52:01 GMT

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.