topic RE: Unexpected AP adoption by another controller (VC) in the same subnet in ExtremeWireless (WiNG)

Unexpected AP adoption by another controller (VC) in the same subnet

gluo — Mon, 28 Jan 2019 20:07:00 GMT

Hi,

I have a setup with a VX9000 and three 7522 APs which are adopted by the VX9000.

In the same subnet I setup two 7532 one as VC and the other as adopted AP by the VC to test stuff.

When I rebooted the VX9000, all three 7522APs got adopted by the 7532VC !

when the VX9000 was back up it re-adopted the three 7522 but things were not working well because the 7532 had a newer firmware and upgraded thet 7522 APs, resulting version missmatch when the VX9000 re-adopted them.

Is this normal? Is there any way to prevent this from happening and have two isolated controller in the same subnet?

thank you in advance.

RE: Unexpected AP adoption by another controller (VC) in the same subnet

RobertZ — Mon, 28 Jan 2019 20:46:00 GMT

yes, its normal

One way you can prevent this by configuring 'controller host IP-addresses' on the AP profile.

In current state ssh via cli to APs and run below commands:

en
self
controller host "The IP address, hostname or host alias of the controller"
com write

RE: Unexpected AP adoption by another controller (VC) in the same subnet

RobertZ — Mon, 28 Jan 2019 20:48:00 GMT

Here is the WiNG Best Practice Doc it will give more detail.

RE: Unexpected AP adoption by another controller (VC) in the same subnet

RobertZ — Mon, 28 Jan 2019 22:02:00 GMT

More importantly we do not recommend multiple WiNG systems on the same broadcast domain.

RE: Unexpected AP adoption by another controller (VC) in the same subnet

gluo — Mon, 28 Jan 2019 22:19:00 GMT

Hi Robert and thank you for your answer.

So just to confirm the only way to prevent the adopted APs going to another controller, in case their controller goes down, is to add the controller-host to all AP profiles in the controller?

The best practices guide says to add it to "Profile" instead of "self" overrides.

thank you.

RE: Unexpected AP adoption by another controller (VC) in the same subnet

RobertZ — Mon, 28 Jan 2019 22:31:00 GMT

Yes, The best practices guide says to add it to "Profile" instead of "self" overrides. But in your particular situation were APs were adopting to the wrong wlc, adding controller host to the override profile is way to direct the AP back to correct wlc.

Best way to prevent the adopted APs form adopting to another controller is to segregate them by putting them in a different broadcast domain.

RE: Unexpected AP adoption by another controller (VC) in the same subnet

gluo — Mon, 28 Jan 2019 22:44:00 GMT

One more question.

In the case of active cluster which should be the controller host? Do I just add both hosts of the cluser?