Cloning a node only works consistently on the Mobility Conductor where you can copy the configuration from one location to another in the hierarchy. Standalone Mobility Controllers only have two levels, /mm and /mm/mynode. To get HA via database synchronization and VRRP with standalone controllers requires all of the common configuration to be placed at the /mm level.
You can use "show configuration committed" at the mynode level to see what has been configured at the controller level and then reapply that configuration at /mm.
------------------------------
Carson Hulcher, ACEX#110
------------------------------
Original Message:
Sent: Jun 03, 2024 09:14 AM
From: Mohammad Ramadan
Subject: Aruba7205 controller configuration hirarchy change
Thank you so much, I will try it.
Original Message:
Sent: Jun 03, 2024 08:41 AM
From: cordless
Subject: Aruba7205 controller configuration hirarchy change
There is a command, where you can clone config in the hierachy
https://www.arubanetworks.com/techdocs/CLI-Bank/Content/aos8/conf-node.htm
Original Message:
Sent: Jun 02, 2024 06:25 AM
From: Mohammad Ramadan
Subject: Aruba7205 controller configuration hirarchy change
Hello,
time ago we have deployed aruba controller 7205, standalone, ArubaOS version 8.6.0.21 everything is going well so far.
Now we are deploying an HA node but the configuration previously was deployed in the hirachy as attached image says on standalone and engineer didn't apply the configuration putting in considration that we will have HA node later.
Now I knew that this configuration will have to be reconfigured such as wifi SSIDs, mac addresses radius table, vlans .. etc on the TOP mobility controller level to have it synced through both Current controller and the new one too.
Any idea how to take all the configuration one level up avoiding configuring all thigs again on the controller level to have it propagated down to the HA controllers?
TIA