Eric,
Based on your description, you might be treating the ESXi hosts as a physical domain with static paths.
Can you confirm how you plan to go this route?
or
Do you plan to integrate these ESXi hosts via VMM domain?
If you're going through with static bindings (physical domain), there is a new configuration option in 2.0 (and later) code.
After creating your access policies, go to the AEP under Fabric -> Access Policies -> Global Policies -> Attachable Access Entity Profile. Choose your AAEP look at the bottom of the right pane. You should see an 'Application EPG' box. From there you can deploy a VLAN on an EPG. APIC will review all interfaces associated to the AEP and program that EPG/VLAN onto all of those interfaces. Much quicker than creating individual static bindings. Be sure that you do not forget to go to the EPG domains tab (Tenant -> App Profile -> EPG -> Domains) and associate the appropriate physical domain just as you would with a static binding. Without doing this, you should expect VLANs failing to program and fault code F0467 to raise. Example of VLAN deployment via AAEP shown below.
If you plan to do VMM, then the VLAN programming will be performed dynamically. No need to create any static bindings. One important note about VMM integration (specifically DVS) is the resolution immediacy configured in the Tenant -> EPG -> Domains tab. Three options are On-Demand, Immediate, and Pre-provision. The best practice is to choose pre-provision. The other two options rely on APIC <> VMM controller communication. If miscommunication happens, such as ESXi host failing to report CDP/LLDP to VMM controller, then VLANs will be removed from leaf interfaces thus potentially leading to an outage on that EPG. With pre-provision, APIC will program VLANs on leaf interfaces based strictly on configured access policies. No need to worry about communication with external VMM controller. Example of pre-provision configuration shown below.
-Jason
