AP won't join to new controller pair. Stuck at old one.

[louhe]

Customer has two Ha-pairs of 2504. Now the first ones license is becoming full. I need to move some of the ap's from first HA-pair to second.

Network layout is pretty simple. HA-pair 1 is at network same network with ap's with ip 192.168.91.0/24. Second HA-pair is at network 192.168.92.0/24. Both networks has different DHCP pool. No DHCP options in use.

When i change untagged (native) vlan (network) from 91 to 92 AP gets right ip address after reboot but is assosiated to controller at .91 network. I tried to configure High Availability controllers under AP but it did nothing. Same thing, after reboot AP is back at .91 controller even if it has .92.x ip (and .92 controllers as high availability). So conclusion is that AP stores info about the controller somewhere and even high availability config does not bypass this.

Only way to get the AP to new controller is to reset it to factory defaults. This option takes long time and i wouldn't want to do the change this way.

So am I doing something wrong. Is there a way to change controller for ap just by rebooting it if it gets new ip address?

[patoberli]

In the past the IP was completely ignored (as far as I remember) and only used the SysName.

[JakeFu]

I read that doc yesterday but still didn't realize the SysName was actually important. My specific issue I was trying to get APs to move to the other controller by swapping the Primary and Secondary controllers IP's in the config. The Controller Names are just placeholders so I would just put the name of the building they were in.

The AP wouldn't budge, but if you rebooted it it happily went to the controller configured as Primary via IP and then it updated the controller Name to the correct name after it associated by its self. Odd behavior indeed.

Thank you very much!