So, once I've got the cluster running (and it's selected one of the 105s as the master), I've tried a couple of different things that I would expect to make it select a new master:
- telling the AP acting as master to reboot through Maintenance -> Reboot
- removing power from the AP acting as master by turning off PoE for that switch port
In both cases, it seems to reboot the whole cluster and select a new master... which is still not one of the 115s.
In short, if (as documented in the training slides) hardware capability is supposed to be a more important factor than uptime in selecting a master, I'm not seeing it happen here. It appears that whichever AP gets to a certain point in the boot process first gets to be master, regardless of hardware spec.
Am I missing something? Is there another way to trigger a master re-election that doesn't reboot the entire cluster?