I have opened a case on this, but Aruba engineers seem baffled.
I have a functioning network with 43 APs, a mix of IAP-305, IAP-205, and IAP-325. An IAP-305 is my preferred VC master. Roughly a month ago, I configured most of the ~80 APs that will compose our network. They all joined the existing network and showed up on the Virtual Controller web GUI. I could click on the AP in the list, click Edit, and change the AP name and IP address.
Fast-forward to today. When I connect a previously provisioned AP to the network, they join the network and show up with their manually configured IP and name. But when I add a brand new AP, it boots and connects to the existing network, showing up with a DHCP assigned IP and the generic MAC-based name. I can click on the new AP to select it, and the web-gui shows the basic information about it. However, when I click Edit, I get a spinning circle for ~20 seconds, then nothing. Clicking on Edit again does absolutely nothing until I refresh the page, at which point all I get is a spinning circle again. The only AP that gives me the Edit popup window is the unit that is the master.
Aruba support remoted into the PC with the web gui and tried several things, SSHed into the controller, but were unable to get the Edit functionality to work. I tried from a different computer with the same result. We rebooted the AP that is the preferred master, with no change. Also, the other existing, configured APs that are not the master exibit the same behavior, unable to Edit.
This means I cannot add any new APs to our network that have not already been configured, without leaving them on a DHCP assigned IP with the generic MAC name.
Has anyone run into this issue?
All APs are running 6.5.1.5-4.3.1.4_60302, which was sent by an Aruba engineer when we were initially configuring the network with instructions to use that version.