That's exactly what I meant. Configure, then save, then change the level. If you do change the level without saving, you can display all unsaved configuration nodes using the following command: show configuration unsaved-nodes
.
Original Message:
Sent: Apr 14, 2025 10:11 AM
From: mvanoverbeek
Subject: AOS8 standalone to conductor migration Question
Hi Waldemar,
Thanks for taking the time and answer my question. I had to read the second part a few times and test it out but I think I understand it now. I think what you mean is:
I think you mean: Always Save your configuration at the level you work at. Don't configure something at the controller level, switch to another level and then save it. In other words always save your work at the level you work at.
Thanks!
------------------------------
Martijn van Overbeek
Architect, Netcraftsmen a BlueAlly Company
Original Message:
Sent: Apr 12, 2025 03:03 PM
From: Lord
Subject: AOS8 standalone to conductor migration Question
Hi Martijn,
yes that works, it's the same syntax.
You create the configuration nodes, then the configuration. You have to create the objects in the right order, first netdestinations, then the ACLs, then the user roles and so on.
I always create the VLANs first, tag them to the correct ports. Then I look at the AP groups and create all the profiles that are used there. Then the user roles with all the corresponding ACLs etc.
In the CLI, you only ever save the config in the current level with write mem. This means that if you configure something on the controller level, then switch to a higher level and save the config, the configuration change is not saved in the controller.
------------------------------
Regards,
Waldemar
ACCX # 1377, ACEP, ACX - Network Security
If you find my answer useful, consider giving kudos and/or mark as solution
Original Message:
Sent: Apr 11, 2025 03:59 PM
From: mvanoverbeek
Subject: AOS8 standalone to conductor migration Question
Hello,
I am planning a migration of a standalone controller pair to an AOS8 conductor managed solution. The current solution has a lot of netdestinations, access-lists, roles with the associated acls, etcetera.
How can I avoid having to recreate all these settings through the GUI. Is it possible to copy all these settings through CLI at the level: Managed Devices > RegionX > CityY for example?
I would hate having to point-and-click for hours restoring the rules. The software versions are identical (8.10.0.x)
Hope someone have some experience with that and what to look out for.
Thanks!
------------------------------
Martijn van Overbeek
Architect, Netcraftsmen a BlueAlly Company
------------------------------