alright, thanks. I am preparing for this change. I tested untagged vlan 400 to a little-used IAP, and after the reboot it rejoined the IAP list and two users associated with the IAP. I can not tell if they were able to browse (I am not at the location) but everything looked well from a remote standpoint.
I am concerned about losing management to the VC and would like to get a good order of changes that I should make.
I intend to leave the master IAP for last. I have one particular IAP that I would like to remain VC whenever possible and I have selected the option to force it to be VC.
I believe the order of changes after all other non-master IAPs are configured should be:
1) set master IAP addressing to DHCP provided
2) change virtual controller IP from 0.0.0.0 to 192.168.10.2
3) change uplink management to vlan 0
4) reboot master virtual controller for changes to take effect.
does this seem proper if my intentions are to allow the IAP to get an address via DHCP and still be able to access the virtual controller at 192.168.10.2?
my concern is that the virtual controller will elect to a different IAP at a different ip address and I will lose connectivity with no way to determine what the new VC address is.
I suppose in worst case scenario I can remotely shut down all IAP ports in the switch which will allow only the master IAP to come online, then reactivate all the other ports after that master IAP has rebooted and I have regained connectivity.
please let me know what you think.