I don't quite understand what the goal is.
Do you want to connect the controller to another mobility conductor?
Then you need to set up the new mobility conductor in disaster recovery: conductorip x.x.x.x ipsec ****** interface vlan zzz
Do you want to manage the controller locally, without mobility conductor?
Then you have to reset it to factory default with "write erase all" and set it up again.
A reconfiguration from managed-device mode to standalone mode is not possible.
------------------------------
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, 2024 03:26 PM
From: pjg-gpg
Subject: How to disconnect controller from inaccessible Mobility Conductor
Greetings,
A site was turned over to me that was connected to a Mobility Conductor (which is no longer accessible). I'm trying to disconnect it, but so far have not been able to do so.
Running ArubaOS version 8.10.0.7. There are 2 controllers in a HA pair locally in case that changes things.
I've tried using disaster recovery mode, and while I was able to remove the secondary conductorip, removing the primary fails with an "Error: not allowed". I also tried doing it from within the mynode path.
(DEVNAME) *#disaster-recovery on
*******************************
Entering disaster recovery mode
*******************************
(DR-Mode) *[mm] #configure terminal
Enter Configuration commands, one per line. End with CNTL/Z
(DR-Mode) *[mm] (config) #no secondary conductorip
(DR-Mode) *[mm] (config) #no conductorip
Error: not allowed
(DR-Mode) *[mm] (config) #cd /mm/mynode
(DR-Mode) *[mynode] (config) #no conductorip
Config deletion will not take effect: configuration is inherited.
Not a lot of threads talk about removing a controller from a conductor and most assume you have access to the conductor to make the change.
* Disconnect from existing conductor: https://community.arubanetworks.com/discussion/removing-controller-from-mobility-conductor-cluster
* Changing conductor ip: https://community.arubanetworks.com/discussion/removing-controller-from-mobility-conductor-cluster
* Removal from existing conductor: https://community.arubanetworks.com/discussion/cannot-remove-vmc-out-of-mobility-conductor
Trying "no masterip" also returns a "Error: not allowed"
Any suggestions / guidance?
thanks.