APIC Data Layer Partially Diverged

After trying to join APICs from a secondary POD, I got the APIC Data Layer Partially Diverged Error:

APIC Data Layer Partially Diverged

In my case this was because I had the “Contract Viewer” app installed on the primary APICs. When the secondary site APICs tried to join the cluster, the 3rd party APP caused this error. I had to remove the APP and reinstall it to allow the secondary POD APICs to join properly.

Multi-Pod 4.2 Issues

Recently I deployed a Cisco ACI 4.2 Multi-Pod deployment, or let’s say I added a secondary POD to a Cisco ACI 4.2 deployment. One of the things I noticed is that you now have to click on Add a Pod under Fabric Inventory and its all wizard based which is a pain, especially if you already have GOLF configured and you want to use the same MPOD L3OUT.

The reason you have to use the wizard is because there is no way to add the secondary POD Spine information (RID/Interface and IP, etc) into the existing GOLF L3OUT. You can try typing it in manually but it still won’t allow you to to apply it properly.

Why is this secondary POD Spine information important? Well because if you do not enter the secondary POD Spine information into the L3OUT and Fabric External Connection Policies, when you register the Spine under Fabric membership, the switch will be stuck in the Discovering stage and will will never be assigned a Infra TEP IP. It will look like its working but the spine will be stuck in Discovery. If you troubleshoot, you will notice discoveryissues on the switch, APIC DHCP does not issue DHCP IPs and it is stuck discovering.


Hopefully Cisco makes adding a POD with existing GOLF configuration easier to manipulate.