Controllerless Networks

Reply
Occasional Contributor II

Preventing IAP from electing a new master

Hello, we have encountered a situation where replacing an IAP with a spare unit that is on older firmware and is in a default state can cause the existing IAP cluster to reassociate with this "new" AP and thus cause them to downgrade and wipe their config. We have had this happen in different scenarios, but it has happened during a refresh or scenario when the normal VC is offline.

 

Is there a way to configure the cluser to not re-home to another VC that is not part of the existing cluster and same firmware level? I am not sure if setting the preferred master option would accompish this or not. All of our IAP are managed by Airware as well.

 

IAP are on 6.5.1 code and Airwave is on 8.2.3.1.

Guru Elite

Re: Preventing IAP from electing a new master

If the older unit has "Preferred Master" enabled, that will happen:  http://www.arubanetworks.com/techdocs/Instant_423_WebHelp/InstantWebHelp.htm#UG_files/CustomizeIAPParams/Master_Election_Protocol.htm

 

If you don't want that to happen, you need to enable Preferred master on one IAP on your existing cluster.



Colin Joseph
Aruba Customer Engineering

Looking for an Answer? Search the Community Knowledge Base Here: Community Knowledge Base

Occasional Contributor II

Re: Preventing IAP from electing a new master

Thanks Colin, 

 

Since these are managed by Airwave would I need to do that via CLI or is there an option in the Instant Config for that?

Guru Elite

Re: Preventing IAP from electing a new master

There should be an option in IGC for that.



Colin Joseph
Aruba Customer Engineering

Looking for an Answer? Search the Community Knowledge Base Here: Community Knowledge Base

Search Airheads
cancel
Showing results for 
Search instead for 
Did you mean: