M and MSM Series
1748185 Members
4350 Online
108759 Solutions
New Discussion юеВ

Re: Differents priorities en controller teaming 760

 
TAAM
Occasional Contributor

Differents priorities en controller teaming 760

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.

 

 

6 REPLIES 6
johnk3r
Respected Contributor

Re: Differents priorities en controller teaming 760

Hi.

Controller >> Management > Device Discovery page.

**************************************
ATP FLEXNETWORK V3 | ACSA
TAAM
Occasional Contributor

Re: Differents priorities en controller teaming 760

I appreciate your help johnk3r 

johnk3r
Respected Contributor

Re: Differents priorities en controller teaming 760

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.
**************************************
ATP FLEXNETWORK V3 | ACSA
TAAM
Occasional Contributor

Re: Differents priorities en controller teaming 760

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

RamKrish
Valued Contributor

Re: Differents priorities en controller teaming 760

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.

Regards
Ram
Arimo
Respected Contributor

Re: Differents priorities en controller teaming 760

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.


HTH,

Arimo
HPE Networking Engineer