Header Only - DO NOT REMOVE - Extreme Networks

Wing AP Migration and Controller Adoption


Userlevel 1
Do APs in the same control vlan influence each other regarding controller adoption?

I just tried to give specific option 191 to just 1 AP and for some reason it was stuck adopting on my old controller cluster

And then out of the blue not only that on adopted according to the new option 191 but another one which did not get the dhcp option decided to adopt on the new controller as well ¬¬

I'm just trying to plan how I will migrate the APs to the new controller on a per AP basis but if this is the case I could have issues

Is there some procedure or included in documentation AP migration?

Thanks in advance

Regards,
Bruno

12 replies

Userlevel 2
Hi Bruno,
Local controller available on L2 would be always preferred. Check with "show mint known-adopters" on AP and make sure there is only one provided with the option 191 is there.

Misha
Userlevel 3
Yes The rfdm will try and manage the aps in the rfd In the rfd on the controller that you are moving from select controller managed Repeat this step for the new controller Then you can move the aps over to the new controller by changing the dhcp option and each ap will move one at a time to the new controller When you have finish set the control vlan again. Finally make sure there is a single mint link from each site Using show mint links on the controller
Userlevel 1
Thanks for the replies

There's no local controller available, the rfdm is also not configured to be a controller, the APs are moving between the old RFS6000 and the new VX9000 (both not onsite)

unless is the RFDM that is sending them back to the RFS6000? Is that what you mean?

So if I set both RFDs to controller managed they will disregard the RFDM and just use option 191?
Userlevel 3
The rfdm job is the manage the access points. Only the rfdm has a connection to the control all other aps link to the rfdm via layer 2 links So to move the aps from one controller to another controller you need to stop aps talking to each other When you set controller managed each ap will talk to the controller If you now change the option 191 and reboot the ap, it will link to the new controller When you have all the aps cut over, you can then disable controller managed The rfdm will be re-elected and the site will be on the VX
Userlevel 1
Understood thanks, it makes sense now,

I just thought the option 191 would be enough to steer the APs to the desired controller but the rfdm is still seeing the AP on the same control vlan and causing the issue
Userlevel 3
If you reboot all the aps at the same time , just changing the option 191 will work. But if you try and do it one by one you will have this trouble.
Userlevel 1
Make sure of the following:

Same fw version on AP/VX/VX9000;
Simple point the AP to the new controller "controller host XX.XXX.XXX / controller vlan X.
Make sure there are no auto-provisioning policy on the controllers that blocks the adoption.

Hugs
Userlevel 1
Carlos Assunção wrote:

Make sure of the following:

Same fw version on AP/VX/VX9000;
Simple point the AP to the new controller "controller host XX.XXX.XXX / controller vlan X.
Make sure there are no auto-provisioning policy on the controllers that blocks the adoption.

Hugs

I have tried this but still noticed the behavior above.
Userlevel 2
I would highly recommend to make a separate vlan for migrated APs. MINT area id is another option but it's too complicated for just a migration.
Userlevel 1
vanelm wrote:

I would highly recommend to make a separate vlan for migrated APs. MINT area id is another option but it's too complicated for just a migration.

I think the controller managed option seems more practical as I would not need to create a new vlan modify the trunk interfaces for the new vlan etc
Userlevel 2
vanelm wrote:

I would highly recommend to make a separate vlan for migrated APs. MINT area id is another option but it's too complicated for just a migration.

Bruno,
Controller-managed is not practical at all. This actually means that your controller would be your rf-domain manager. If it far enough that clients will experience latency in roaming.
Also "redirect" should work in old controller's auto-provisioning policy.
Userlevel 1
vanelm wrote:

I would highly recommend to make a separate vlan for migrated APs. MINT area id is another option but it's too complicated for just a migration.

Thanks vanelm I will consider this,

Just to control the migration I would not mind to suffer a bit of performance plus our site to site latency in this case is not too bad, but it's good to know what my options are

we haven't used the auto provisioning policy so I'm not really familiar with it

I may end up rebooting them all at the same time and let them join the new controller via option 191

Reply