I had a lab set up as the standard Mini ACI Fabric and Virtual APICs as per the official document.
But because I had a "spare" physical APIC, last time I built the lab I thought I'd try Two physical and one vAPIC.
But the vAPIC just doesn't seem to want to join, and I'm at a loss as how to troubleshoot exactly what is going on. I'm beginning to think that perhaps the system is geared to determining whether the setup is a Standard 3 Physical APIC topology or a Mini ACI Fabric topology is based on whether APIC#2 is physical or virtual.
Most of the troubleshooting documents I've found talk about making sure the Infra VLAN and LLD are configured correctly - LLDP is irrelevant in this situation because the stubborn APIC is a vAPIC
FWIW - this is the situation:
So my initial question is:
But implied is also:
Note: Being Lab equipment it is not under any support contract, so callingTAC is not an option.
Hi @ecsnnsls ,
I'm not sure if enabling/disabling LLDP on the VICs of the physical APICs would have anything to do with the situation. Both physical APICs have joined the cluster - quite happily except they can't find APIC3
I really can't find any troubleshooting info about the processes that a vAPIC goes through to join a cluster.
Yes, that's true. There's very little documentation available. For some reason I was thinking APIC2 didn't join the cluster. My bad!
Couple of things off the checklist,
- Did you check the time synchronization on all three apics and the esxi?
- Also, if you had deployed the VM using OVA, did it take more than 60 mins for the VM to get deployed. In this case we need to use a new passphrase.
Sorry, this is all I could scavenge from the document. Perhaps someone with more experience in vAPIC has the solution!
Hi @ecsnnsls ,
Good points - and I forgot to mention these in the original:
Thanks for trying.