Hello,
Can anybody explain how an APIC deploys a VLAN configuration for existing port-groups from dynamic VLAN pool?
The question is for particular case when a vCenter already have:
- folder and VDS/DVS that exactly matches what APIC is going to deploy;
- port-group names matches corresponding tenant-application-EPG;
- VLAN ID for port-groups are in dynamic VLAN pool block ranges.
Case 1
An APIC cluster boots up from complete shutdown (all three nodes), while there are not any other APIC connected to a vCenter.
Does APIC take into account existing VLAN ID assignments or, conversely, it could randomly overwrite different VLAN ID for port-groups?
If it does overwrite, what possible reason for such behavior could be?
Please, do not elaborate on consequences of running a fabric without controlling APIC cluster, it's well documented.
If to overwrite is intendent behavior, then please explain following.
Case 2
One APIC cluster 1 is connected to the vCenter and is operating. At the same time another standalone APIC 2, having exactly the same configuration cloned from cluster 1, connects to the vCenter over in-band interface, but with different source IP address (no common infra for overlay-1 VRF).
Whether should the APIC 1 keep the connection, watch and fix any discrepancy reported from vCenter (event-driven by installed web hook).
If the APIC 1 falls into failed state, keeping connection or not, will it try to recover that state eventually?
What timings are for these FSMs?
Is there any way to force APIC fix connections and VLAN ID mismatches in one or few steps, without need to remove and add back VMM domain for every EPG?
Than you in advance.
