Ok so here's what I tried:
Changed the system profile to be default (no LMS IP)
Removed the provisioning profile completely
Moved the AP into the test group
Went to the controller URL, found the AP and provisioned it with:
Host controller name: aruba-master-65
Master Controller IP Address/DNS name: 131.111.1.7
...And booted it.
It looked like it was going to work, the AP appeared on the test controller briefly, got as far as 'Configuring Logging' and then silently switched back to the original controller.
Subsequently if I try repeating that process (of provisioning the test controller details via the GUI) it reboots but doesn't even seem to touch the test controller any more. But the provisioning parameters for it on the controller that it _does_ appear on are showing correctly, ie with the test controller details:
AP "18:64:72:c7:3b:0e" Provisioning Parameters
----------------------------------------------
Item Value
---- -----
AP Name 18:64:72:c7:3b:0e
AP Group maths-master-65_aps
Location name N/A
SNMP sysLocation N/A
Master 131.111.1.7
Gateway N/A
IPv6 Gateway N/A
Netmask N/A
IP Addr N/A
IPv6 Addr N/A
IPv6 Prefix 64
DNS IP N/A
DNS IPv6 N/A
Domain Name N/A
Server Name aruba-master-65
Server IP N/A
And during bootup the console shows:
Running ADP...Done. Master is 131.111.1.7
But then later reverts to:
Using saved lms 131.111.1.22 as the master directly
I'm a little confused! We do use DHCP otion 43, but that wouldn't supply 131.111.1.22.