10-06-2020 10:16 AM - edited 10-06-2020 10:08 PM
Hello,
for a customer we enhanced a current ACI Fabric (single Pod) to a multi-pod solution. After adding the new Pod the discovery process works fine and at the end all spines and leaf switches are shown in the topology.
Also we want to move the third controller (APIC-3) from the first pod to the second pod. Because of this I decommissioned APIC-3. Also delete the config and start with the initial setup script after the APIC was moved to Pod2.
This was because the name of the third APIC changed.
The problem now is that the third APIC does not join the cluster.
I noticed the following:
Any solution for that?
Thanks
Udo
10-07-2020 12:48 AM
Hi @udo.konstantin ,
You'd better change the hostname before Decommission/Recommission.
Try the following:
- Decommission the APIC
- Rebuild the APIC with the old name
- Add it to the cluster
- Change the APIC name (System>Controllers>apic-X>General)
- Reboot the APIC
- If necessary, run again the Deco/Reco process
10-07-2020 01:39 AM
Hi @Remi-Astruc ,
thank you for this information.
We already moved the APIC to the second pod. So when I understand you correctly, we should move the APIC back to Pod 1, configure it with the old values and bring it back again.
Then change the name to the appropriate?!
Or is it also possible to bring it back on the second pod with the old name and commission it? I don't think this works because it's in Pod 2.
Any help?
Thanks
Udo
10-08-2020 01:28 AM
Hi @udo.konstantin ,
You should be able to do it in Pod 2, as if you'd move it without changing the hostname.
When rebuilding the APIC, run the commands acidiag touch clean, acidiag touch setup, and reboot the APIC. In the setup script, keep all values the same as it was when in Pod 1, but change the Pod ID into 2.
Discover and save your favorite ideas. Come back to expert answers, step-by-step guides, recent topics, and more.
New here? Get started with these tips. How to use Community New member guide