Through the CLI on the new MCR, at the relevant configuration node.
------------------------------
Carson Hulcher, ACEX#110
------------------------------
Original Message:
Sent: Oct 09, 2024 12:01 PM
From: Ronin101
Subject: Controllers moving to new Mobility Conductors
thanks Carson,
What is the best way of re-applying this configuration taken through show configuration committed
Original Message:
Sent: 10/9/2024 9:52:00 AM
From: chulcher
Subject: RE: Controllers moving to new Mobility Conductors
- Factory default the controllers to be moved by performing a
write erase
. - Run through the setup script and point the controllers at the new Mobility Conductor environment.
If there is existing configuration that needs to be brought over, record that configuration (show configuration committed
is very useful here) and re-apply in the new setup.
------------------------------
Carson Hulcher, ACEX#110
Original Message:
Sent: Oct 09, 2024 08:39 AM
From: Ronin101
Subject: Controllers moving to new Mobility Conductors
Dear Experts,
I have 3 controllers as managed node connected to 2xMobility Conductors (version 8.10). Now due to some issues customer is asking to deploy 2 new Mobility conductors and join the controllers to new MCRs. Can someone advise
1) If we keep the IP of MCRs same, will it help retain the configuration of controllers? what shall be the recommended way of migrating these controllers to new MCRs with same old IPs
2) If we change the IP of MCRs, do we need to factory reset the controllers or can we join them as managed node to new MCRs (with new IPs)? what is the best way of doing it?