Hi,
had to perform an upgrade from 8.6.0.4 to 8.6.0.6 yesterday evening on a MM/2xMD configuration, no cluster
I upgraded the first controller ending with ip 251. No issues.
I upgraded the second controller ending with ip 248. I remarked all ap's migrating to controller with ip 251 and upgrading.
Then they remained down, until controller with ip 248 started again. Did not expect that...
Question is : why did they only come up after controller with ip 248 started again...
I checked ap config, there it says static controller discovery, controller with ip 248.
For the group where the controller belongs to, the LMS settings are primary controller with ip 248, secondary controller with ip 251.
I did not have the time to perform another reboot on controller with ip 248 to find out if i could reproduce the issue.
Is this expected? I believe the LMS settings are stored in an ap's config. Maybe they get deleted during an upgrade process? Does this thus only happen with an upgrade because an ap does work on controller with ip 251?