Network Management

Hi All, in a previous post we were looking for a way to put APs in a folder so that the API can use them for floormap placements, see below:

https://community.arubanetworks.com/t5/Developer-Community/Airwave-8-2-8-1-API-how-to-handle-access-points-in-new-devices/m-p/630796#M488 

What we currently see is that some of the APs end up correctly in their assigned folder, but also some of them end up in the "new devices" section, and therefor are not usable by the API.

We played a lot with the settings, even by putting APs in a fixed folder. But we still see APs being placed in "new devices".

Is there any way to avoid this or change in configuration so we don't have to do this by hand?

Are the new AP's controller based AP's and for the controller added in AirWave?  As per below settings only the thin AP's will be in the respective Group and Folder. If they are IAP's or new controller, they will be in New Devices list.

Yeah, all AP's are controller based AP's. All controllers have been present for some time. We don't have any IAPs.

The situation happens for AP's on the same controller. So one of them goes to the assigned folder while another one is ending up in the new devices list.

Does controller is already authorized and move to specific group/folder? Can you set Controller / Autonomous Devices location to group where controller is added instead of new device list and check the status.

Unfortunately yes, the controllers is authorized and in the folder. We are only replacing APs and controllers have been up and running for a longer period now. 

We have tried the things you mentioned and it doesn't affect the behaviour. There are always AP's who move correctly and others which stay in the new devices list. I start to think that it might be a bug in Airwave.

Does new AP which are provisioned on existing controller have same class IP and of same subnet?

Open TAC ticket to investigate this issue.