Move AP to different controller in DNAC

[Wes Schochet]

Hi All-

I am moving from Prime Infrastructure to DNA Center and have discovered lots of little challenges in my day to day activities.  Here is the latest one i cannot figure out.  I have tried going in through the inventory module or by starting with the device 360 module.  Neither seem to let me make changes to AP settings.  Is there a spot for this in DNAC or do I have to manage APs from the controller now?

Thanks!

[ammahend]

one of the benefits of tags in ios-xe controller is you can just change pri and sec controller in AP join profile and it will be pushed to all AP with tag

i haven't tried this from dnac. 

[marce1000]

           -1)  Navigate to the "Devices" tab in Cisco DNA Center.
             2)  Locate the access point you want to move, and click on its name to open its details page.
             3)  Click the "Edit" button at the top of the page.
             4)   In the "Controller" field, select the new controller you want to move the access point to.
             5)  Click the "Save" button to apply the change.

     Note that the access point may go offline briefly while it is being moved to the new controller.

 M.

[Wes Schochet]

Thank you for the very detailed response.  I am a little embarrassed to say that I still can't quite figure it out.

I assume the "Devices" tab in under Provision -> Inventory ?

When I click on the AP name, i get an info screen that doesn't seem to have anything editable. I can click on view 360 from there, but again,, nothing editable.

See attached screen shot.

I assume I am missing something quite basic here.   Thanks again for your help - sorry to be so concrete...

[wayneCmiles]

I have the same problem and I don't understand where to find the Devices tab also.

[wayneCmiles]

Can you explain what you mean by DEvices tab?

[Leo Laohoo]

Moving one or two APs using GUI is "ok". 

But moving a lot of APs around, I always use CLI because it is a lot faster and I am guaranteed that it will work.

[JPavonM]

From an administrative point of view, it's quicker and easier to perform bulk tasks from WLC's CLI using scripts. I only use DNA-C for assurance at the moment, mainly becuase I see it too buggy to be used for admin tasks at the moment, and I'd need to double check the results from the WLC side.